From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Build fails at cdrom stage Date: Tue, 06 Aug 2024 15:56:23 +0100 Message-ID: <7840594E-B781-4291-A577-9E0583E7B571@ipfire.org> In-Reply-To: <452b9490-77c8-4864-9cdf-23ba181241b8@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5916875552364867619==" List-Id: --===============5916875552364867619== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, Just pull, I fixes this already: https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3D41bc16ac0b18d= 19e9c34854890fb6e920a6c5584 -Michael > On 6 Aug 2024, at 15:55, Adolf Belka wrote: >=20 > Hi All, >=20 > My CU188 build is failing at the cdrom stage. The message it comes up with = is >=20 >=20 > BUILD_ARCH=3D"x86_64" BUILDTARGET=3D"x86_64-pc-linux-gnu" KVER=3D"6.6.3= 2" /usr/src/src/scripts/archive.files x86_64 /usr/src/config/rootfiles/common= | tee | tar --create --format=3Dpax --acls --xattrs --xattrs-include=3D'*'= --sparse --directory=3D/ --exclude=3D"dev/pts/*" --exclude=3D"proc/*" --excl= ude=3D"tmp/*" --exclude=3D"__pycache__" --files-from=3D- | tar --extract --fo= rmat=3Dpax --acls --xattrs --xattrs-include=3D'*' --sparse --directory=3D/tmp= /root > tar: usr/bin/br2684ctl: Cannot stat: No such file or directory > tar: Exiting with failure status due to previous errors >=20 > For some reason it is looking for br2684ctl in /usr/bin/ but that file is l= ocated in /usr/sbin/ >=20 > I can't figure out why it is looking in bin rather than in sbin but that se= ems to be the reason for the failure >=20 >=20 > Regards, >=20 > Adolf. >=20 --===============5916875552364867619==--