Build fails at cdrom stage

Build fails at cdrom stage

[Adolf Belka]

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

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.

Re: Build fails at cdrom stage

[Michael Tremer]

[-- 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.
> 

Re: Build fails at cdrom stage

[Adolf Belka]

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

I pulled but now it stops with postfix saying that it can't find any active network interfaces

Re: Build fails at cdrom stage

[Michael Tremer]

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

Please pull again. I fixed this already yesterday…

I cut the build environment off of any network, but it seems that Postfix wants at least something there…

The change that broke it:

  https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=91942800f96fbac354eba56714814831badfc88e

The fix:

  https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=f5160566b202677ffee1423aadc2ce7d87c03114

> On 6 Aug 2024, at 18:31, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> I pulled but now it stops with postfix saying that it can't find any active network interfaces

Re: Build fails at cdrom stage

[Adolf Belka]

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



On 07/08/2024 11:31, Michael Tremer wrote:
> Please pull again. I fixed this already yesterday…
Yes, it is working now.

I think for future issues I will wait for the following day and do a pull to see if things have already been fixed.

Regards,
Adolf.

> 
> I cut the build environment off of any network, but it seems that Postfix wants at least something there…
> 
> The change that broke it:
> 
>    https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=91942800f96fbac354eba56714814831badfc88e
> 
> The fix:
> 
>    https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=f5160566b202677ffee1423aadc2ce7d87c03114
> 
>> On 6 Aug 2024, at 18:31, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> I pulled but now it stops with postfix saying that it can't find any active network interfaces
> 

Re: Build fails at cdrom stage

[Michael Tremer]

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

Hello,

Always try to pull :) But it is not wrong to complain to me on the list. I want to know what I am breaking to hopefully learn from it.

-Michael

> On 7 Aug 2024, at 11:14, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> 
> 
> On 07/08/2024 11:31, Michael Tremer wrote:
>> Please pull again. I fixed this already yesterday…
> Yes, it is working now.
> 
> I think for future issues I will wait for the following day and do a pull to see if things have already been fixed.
> 
> Regards,
> Adolf.
> 
>> I cut the build environment off of any network, but it seems that Postfix wants at least something there…
>> The change that broke it:
>>   https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=91942800f96fbac354eba56714814831badfc88e
>> The fix:
>>   https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=f5160566b202677ffee1423aadc2ce7d87c03114
>>> On 6 Aug 2024, at 18:31, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>> 
>>> I pulled but now it stops with postfix saying that it can't find any active network interfaces