public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] util-linux: Do not ship broken symlink "/usr/bin/x86_64"
Date: Mon, 11 Jul 2022 13:02:04 +0000	[thread overview]
Message-ID: <c6000ba5-7f65-b52c-e15a-6a46ca25949f@ipfire.org> (raw)
In-Reply-To: <37c1ca96-bffb-5b2c-baee-f8862e1f8b74@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]

Hello *,

for the records, this causes a rather ugly warning at the end of the distributions'
build procedure:

> Checking Logfiles for new Files                                                                                                                                                                                                       
> Error! '/x86_64' in rootfiles files found!
> ./config/rootfiles/core/170/update.sh:	/usr/bin/x86_64 \
> Replace by xxxMACHINExxx !

Can be safely ignored, but may cause some confusion at the first glance.

Thanks, and best regards,
Peter Müller


> This file points to /usr/bin/setarch, which we do not ship on any
> architecture. As it serves no obvious purpose on IPFire installations,
> we may as well not ship it entirely.
> 
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
>  config/rootfiles/common/x86_64/util-linux | 2 +-
>  config/rootfiles/core/170/update.sh       | 1 +
>  2 files changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/config/rootfiles/common/x86_64/util-linux b/config/rootfiles/common/x86_64/util-linux
> index bd862b557..de78f65c2 100644
> --- a/config/rootfiles/common/x86_64/util-linux
> +++ b/config/rootfiles/common/x86_64/util-linux
> @@ -103,7 +103,7 @@ usr/bin/uclampset
>  usr/bin/uuidgen
>  usr/bin/uuidparse
>  #usr/bin/whereis
> -usr/bin/x86_64
> +#usr/bin/x86_64
>  #usr/include/blkid
>  #usr/include/blkid/blkid.h
>  #usr/include/libfdisk
> diff --git a/config/rootfiles/core/170/update.sh b/config/rootfiles/core/170/update.sh
> index e3f93df57..5d8903189 100644
> --- a/config/rootfiles/core/170/update.sh
> +++ b/config/rootfiles/core/170/update.sh
> @@ -57,6 +57,7 @@ rm -rvf \
>  	/sbin/ifcfg \
>  	/sbin/routef \
>  	/sbin/rtpr \
> +	/usr/bin/x86_64 \
>  	/usr/lib/libbfd-2.36.* \
>  	/usr/lib/libbind9-9.16.2* \
>  	/usr/lib/libdnet* \

  parent reply	other threads:[~2022-07-11 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 12:37 Peter Müller
2022-07-09 14:30 ` Adolf Belka
2022-07-11 13:02 ` Peter Müller [this message]
2022-07-11 17:02 ` Michael Tremer
2022-07-12  9:44   ` Peter Müller
2022-07-12 10:00     ` Michael Tremer
2022-07-12 10:42       ` Peter Müller
2022-07-12 11:21         ` Michael Tremer

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=c6000ba5-7f65-b52c-e15a-6a46ca25949f@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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