From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Build fails at cdrom stage
Date: Tue, 06 Aug 2024 15:56:23 +0100 [thread overview]
Message-ID: <7840594E-B781-4291-A577-9E0583E7B571@ipfire.org> (raw)
In-Reply-To: <452b9490-77c8-4864-9cdf-23ba181241b8@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
Hello,
Just pull, I fixes this already:
https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=41bc16ac0b18d19e9c34854890fb6e920a6c5584
-Michael
> On 6 Aug 2024, at 15:55, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi All,
>
> My CU188 build is failing at the cdrom stage. The message it comes up with is
>
>
> BUILD_ARCH="x86_64" BUILDTARGET="x86_64-pc-linux-gnu" KVER="6.6.32" /usr/src/src/scripts/archive.files x86_64 /usr/src/config/rootfiles/common | tee | tar --create --format=pax --acls --xattrs --xattrs-include='*' --sparse --directory=/ --exclude="dev/pts/*" --exclude="proc/*" --exclude="tmp/*" --exclude="__pycache__" --files-from=- | tar --extract --format=pax --acls --xattrs --xattrs-include='*' --sparse --directory=/tmp/root
> tar: usr/bin/br2684ctl: Cannot stat: No such file or directory
> tar: Exiting with failure status due to previous errors
>
> For some reason it is looking for br2684ctl in /usr/bin/ but that file is located in /usr/sbin/
>
> I can't figure out why it is looking in bin rather than in sbin but that seems to be the reason for the failure
>
>
> Regards,
>
> Adolf.
>
next prev parent reply other threads:[~2024-08-06 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 14:55 Adolf Belka
2024-08-06 14:56 ` Michael Tremer [this message]
2024-08-06 17:31 ` Adolf Belka
2024-08-07 9:31 ` Michael Tremer
2024-08-07 10:14 ` Adolf Belka
2024-08-07 12:03 ` 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=7840594E-B781-4291-A577-9E0583E7B571@ipfire.org \
--to=michael.tremer@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