From: Uladzimir Bely <ubely@ilbers.de>
To: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] dpkg: Fix failure with the latest coreutils
Date: Thu, 14 Dec 2023 10:15:58 +0300 [thread overview]
Message-ID: <13ba0e8e1ffac24bc4c03b95eab30236a8c55d38.camel@ilbers.de> (raw)
In-Reply-To: <20231208160557.108706-1-amikan@ilbers.de>
On Fri, 2023-12-08 at 18:05 +0200, Anton Mikanovich wrote:
> Starting from coreutils 9.2 commands 'cp -n' and 'mv -n' exit with
> nonzero status if they skip their action because the destination
> exists.
> This results in packages building failures on Debian Sid targets.
> To keep old behavior '--update=none' was added since 9.3.
> This patch introduce choosing the right option syntax based on distro
> and override it for Sid.
> In case of backporting coreutils > 9.2 into testing and/or stable we
> should add overrides for them also.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> meta/classes/dpkg.bbclass | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
Applied to next.
prev parent reply other threads:[~2023-12-14 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 16:05 Anton Mikanovich
2023-12-14 7:15 ` Uladzimir Bely [this message]
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=13ba0e8e1ffac24bc4c03b95eab30236a8c55d38.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.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