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 >> in the file system. >> >> If you have a configure script (or similar) you can tell it to use >> /usr/lib(64) instead: > > The configure script has the default for the libexecdir as > /usr/libexec but that was also the case for the existing version of > lvm2 (2.03.16) > > That older version was released in May 2022 so maybe the FHS checks > have been updated/improved from when lvm2 was built in IPFire-3 > previously. > > I will re-try the update of lvm2 with adding a definition into > configure for the libexecdir as you suggest. > It turns out that the default macros in pakfire already define libexecdir=/usr/lib but in the lvm2 configure there is an additional --with-libexecdir='dir' that has to be added otherwise configure forces the lvresize helper scripts into /usr/libexec So I did not add --libexecdir='dir' so the pakfire default was taken but I added --with-libexecdir=/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 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 with PID 1 Dec 06 16:17:13 laptop pakfire[30051]: Waiting for signal... Dec 06 16:17:13 laptop pakfire[30051]: UID: 0 (effective 0) Dec 06 16:17:13 laptop pakfire[30051]: 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 /var/tmp/pakfire-root-wK3wJ5 Dec 06 16:17:13 laptop pakfire[30051]: Mounting /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 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 file descriptor Dec 06 16:17:13 laptop pakfire[30051]: Could not destroy cgroup: Device or resource busy Dec 06 16:17:13 laptop pakfire[30051]: Script 'find-prerequires' failed with status -1 Dec 06 16:17:13 laptop pakfire[30051]: Could not add scriptlet requirements: Device or resource busy Dec 06 16:17:13 laptop pakfire[30051]: Could not create packages: Device 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 or resource busy Dec 06 16:17:13 laptop pakfire[30051]: Removing 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 /var/tmp/pakfire-root-wK3wJ5 Not sure if these slightly different error messages from my Arch Linux logs help or not in trying to figure out what is occurring. Regards Adolf > Regards, > Adolf. > > >> >> https://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=acl/acl.nm;hb=5652c2fd3711c1de47ad1e754e7fd28929e21c16#l30 >> >> -Michael >> >>> On 4 Dec 2023, at 18:09, Adolf Belka <adolf.belka(a)ipfire.org> wrote: >>> >>> Hi Michael, >>> >>> The error is >>> >>> Dec 03 18:00:59 desktop pakfire[54234]: File Issues: >>> Dec 03 18:00:59 desktop pakfire[54234]: drwxr-xr-x root/root >>> 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 <adolf.belka(a)ipfire.org> wrote: >>>>> >>>>> Hi Michael + all, >>>>> >>>>> I was running an update build of lvm2 and the build failed near >>>>> 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 >>>>> to look through the built file structure that there was a command >>>>> to add into the .nm file to cause the build to exit without >>>>> clearing all the build files away. >>>>> >>>>> Unfortunately >>>>> >>>>> 1) I can't remember what the command to add into the .nm file is. >>>>> I tried exit but pakfire just said that it couldn't understand the >>>>> .nm file with that included. >>>>> >>>>> 2) Even if I could cause pakfire to stop, while leaving the build >>>>> file structure in place, I also can't remember where the build >>>>> structure in IPFire-3.x is located. >>>>> >>>>> Any help would be gratefully accepted and welcomed. >>>>> >>>>> Regards, >>>>> >>>>> Adolf. >>>>> >>> >>> -- >>> Sent from my laptop >> > -- Sent from my laptop