From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Petr Vorel <pevik@seznam.cz>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/debianutils: bump version to 5.7-0.2
Date: Tue, 26 Jul 2022 22:04:05 +0200 [thread overview]
Message-ID: <20220726220405.4fbd3e0c@windsurf> (raw)
In-Reply-To: <20220726193810.43817-1-pevik@seznam.cz>
Hello Petr,
On Tue, 26 Jul 2022 21:38:10 +0200
Petr Vorel <pevik@seznam.cz> wrote:
> From: Petr Vorel <petr.vorel@gmail.com>
>
> debian/copyright has been moved to a different tarball
> (debianutils_5.7-0.2.debian.tar.xz) which does not contain the source
> code, thus build from salsa git instead of tarball from
> https://snapshot.debian.org/.
>
> Add patch to disable po4a (unnecessary dependency just to get
> translations).
>
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> ---
> package/debianutils/0001-Disable-po4a.patch | 25 +++++++++++++++++++++
> package/debianutils/debianutils.hash | 6 ++---
> package/debianutils/debianutils.mk | 7 +++---
> 3 files changed, 32 insertions(+), 6 deletions(-)
> create mode 100644 package/debianutils/0001-Disable-po4a.patch
>
> diff --git a/package/debianutils/0001-Disable-po4a.patch b/package/debianutils/0001-Disable-po4a.patch
> new file mode 100644
> index 0000000000..2af9a93279
> --- /dev/null
> +++ b/package/debianutils/0001-Disable-po4a.patch
> @@ -0,0 +1,25 @@
> +From 7134952f97ad5afb208e270571afbfe12670cc14 Mon Sep 17 00:00:00 2001
> +From: Petr Vorel <petr.vorel@gmail.com>
> +Date: Mon, 25 Jul 2022 12:59:45 +0200
> +Subject: [PATCH] Disable po4a
> +
> +Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> +---
> + Makefile.am | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/Makefile.am b/Makefile.am
> +index 86ac499..7c61896 100644
> +--- a/Makefile.am
> ++++ b/Makefile.am
> +@@ -1,6 +1,6 @@
> + AUTOMAKE_OPTIONS = foreign
> +
> +-SUBDIRS = po4a
> ++# SUBDIRS = po4a
We already have a po4a directory in the current version of debianutils.
Why suddenly do we have to remove this?
I'm also a bit annoyed by patches like this that we cannot upstream
(and therefore have to keep forever), and that require AUTORECONF :-/
Do we have a better solution?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-26 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 19:38 [Buildroot] [PATCH 1/1] package/debianutils: bump version to 5.7-0.2 Petr Vorel
2022-07-26 20:04 ` Thomas Petazzoni via buildroot [this message]
2022-07-29 18:36 ` Petr Vorel
2022-08-03 21:57 ` Thomas Petazzoni via buildroot
2022-08-04 21:27 ` Petr Vorel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220726220405.4fbd3e0c@windsurf \
--to=buildroot@buildroot.org \
--cc=pevik@seznam.cz \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox