From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Help with an IPFire-3.x pakfire build failure Date: Wed, 06 Dec 2023 16:32:54 +0100 Message-ID: In-Reply-To: <24507e18-7098-4a03-ba0f-138ae9bf1cbc@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0819278142804696081==" List-Id: --===============0819278142804696081== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 06/12/2023 15:32, Adolf Belka wrote: > Hi Michael, > > On 06/12/2023 13:35, Michael Tremer wrote: >> Hello Adolf, >> >> This quite likely is a legitimate error. You cannot have /usr/libexec=20 >> in the file system. >> >> If you have a configure script (or similar) you can tell it to use=20 >> /usr/lib(64) instead: > > The configure script has the default for the libexecdir as=20 > /usr/libexec but that was also the case for the existing version of=20 > lvm2 (2.03.16) > > That older version was released in May 2022 so maybe the FHS checks=20 > have been updated/improved from when lvm2 was built in IPFire-3=20 > previously. > > I will re-try the update of lvm2 with adding a definition into=20 > configure for the libexecdir as you suggest. > It turns out that the default macros in pakfire already define=20 libexecdir=3D/usr/lib but in the lvm2 configure there is an additional=20 --with-libexecdir=3D'dir' that has to be added otherwise configure forces=20 the lvresize helper scripts into /usr/libexec So I did not add --libexecdir=3D'dir'=C2=A0 so the pakfire default was taken = but I added --with-libexecdir=3D/usr/lib and that then solved the FHS error. However then it still had a bad file descriptor error but right at the end. Here are the error messages that occurred. Dec 06 16:17:13 laptop pakfire[30051]: Executing jail... Dec 06 16:17:13 laptop pakfire[30051]: Parent has finished initialization Dec 06 16:17:13 laptop pakfire[30051]: Sending signal... Dec 06 16:17:13 laptop pakfire[30051]: Waiting for PID 38859 to finish=20 its work Dec 06 16:17:13 laptop pakfire[30051]: Streaming standard input... Dec 06 16:17:13 laptop pakfire[30051]: Standard input callback finished: -1 Dec 06 16:17:13 laptop pakfire[30051]: Closing standard input pipe Dec 06 16:17:13 laptop pakfire[30051]: Launched child process in jail=20 with PID 1 Dec 06 16:17:13 laptop pakfire[30051]: Waiting for signal... Dec 06 16:17:13 laptop pakfire[30051]:=C2=A0=C2=A0 UID: 0 (effective 0) Dec 06 16:17:13 laptop pakfire[30051]:=C2=A0=C2=A0 GID: 0 (effective 0) Dec 06 16:17:13 laptop pakfire[30051]: Changing mount propagation on / Dec 06 16:17:13 laptop pakfire[30051]: Changing mount propagation on=20 /var/tmp/pakfire-root-wK3wJ5 Dec 06 16:17:13 laptop pakfire[30051]: Mounting=20 /var/tmp/pakfire-root-wK3wJ5/proc from pakfire_proc (proc - (null)) Dec 06 16:17:13 laptop pakfire[30051]: Streaming standard input... Dec 06 16:17:13 laptop pakfire[30051]: Could not send scriptlet: Bad=20 file descriptor Dec 06 16:17:13 laptop pakfire[30051]: Standard input callback finished: 1 Dec 06 16:17:13 laptop pakfire[30051]: Could not write to stdin: Bad=20 file descriptor Dec 06 16:17:13 laptop pakfire[30051]: Could not destroy cgroup: Device=20 or resource busy Dec 06 16:17:13 laptop pakfire[30051]: Script 'find-prerequires' failed=20 with status -1 Dec 06 16:17:13 laptop pakfire[30051]: Could not add scriptlet=20 requirements: Device or resource busy Dec 06 16:17:13 laptop pakfire[30051]: Could not create packages: Device=20 or resource busy Dec 06 16:17:13 laptop pakfire[30051]: Freeing jail at 0x56221483e610 Dec 06 16:17:13 laptop pakfire[30051]: Could not destroy cgroup: Device=20 or resource busy Dec 06 16:17:13 laptop pakfire[30051]: Removing=20 lvm2-2.03.23-1.ipfire3.src at /var/tmp/lvm2-2.03.23-1.ipfire3.src.pfm Dec 06 16:17:13 laptop pakfire[30051]: Destroying=20 /var/tmp/pakfire-root-wK3wJ5 Not sure if these slightly different error messages from my Arch Linux=20 logs help or not in trying to figure out what is occurring. Regards Adolf > Regards, > Adolf. > > >> >> https://git.ipfire.org/?p=3Dipfire-3.x.git;a=3Dblob;f=3Dacl/acl.nm;hb=3D56= 52c2fd3711c1de47ad1e754e7fd28929e21c16#l30 >> >> -Michael >> >>> On 4 Dec 2023, at 18:09, Adolf Belka wrote: >>> >>> Hi Michael, >>> >>> The error is >>> >>> Dec 03 18:00:59 desktop pakfire[54234]: File Issues: >>> Dec 03 18:00:59 desktop pakfire[54234]:=C2=A0 drwxr-xr-x root/root=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=20 >>> 60 2023-12-03 17:00 /usr/libexec [FHS-ERROR] >>> Dec 03 18:00:59 desktop pakfire[54234]: Post build checks failed >>> >>> Regards, >>> Adolf. >>> >>> On 04/12/2023 18:38, Michael Tremer wrote: >>>> What is the error that you are getting? >>>>> On 3 Dec 2023, at 17:18, Adolf Belka wrote: >>>>> >>>>> Hi Michael + all, >>>>> >>>>> I was running an update build of lvm2 and the build failed near=20 >>>>> the end. >>>>> >>>>> I looked through the logs and found that there was an FHS error. >>>>> >>>>> I remember from the weekend on IPFire3 that we held that if I want=20 >>>>> to look through the built file structure that there was a command=20 >>>>> to add into the .nm file to cause the build to exit without=20 >>>>> clearing all the build files away. >>>>> >>>>> Unfortunately >>>>> >>>>> 1) I can't remember what the command to add into the .nm file is.=20 >>>>> I tried exit but pakfire just said that it couldn't understand the=20 >>>>> .nm file with that included. >>>>> >>>>> 2) Even if I could cause pakfire to stop, while leaving the build=20 >>>>> file structure in place, I also can't remember where the build=20 >>>>> structure in IPFire-3.x is located. >>>>> >>>>> Any help would be gratefully accepted and welcomed. >>>>> >>>>> Regards, >>>>> >>>>> Adolf. >>>>> >>> >>> --=20 >>> Sent from my laptop >> > --=20 Sent from my laptop --===============0819278142804696081==--