Hi Michael, First of all, thanks for taking a look at this bug.
Em 25/11/2022 14:06, Michael Prokop escreveu:
Thanks for doing this! I tried to reproduce it with only the following change applied: | --- debian/control | +++ debian/control | @@ -7,7 +7,7 @@ Build-Depends: cmake, | debhelper-compat (=13), | libfuse-dev | libfuse-hurd-dev, | libmbedtls-dev, | - ruby-dev | + ruby-dev (>= 1:3.1~0) But it works fine for me when building this in a cowbuilder experimental environment on amd64.
I got the build failure using sbuild, in a unstable chroot with experimental enabled. To check if this is not an issue with my build environment, I also tried to build it inside an unstable lxd container with experimental enabled and I got the same build failure.
So quoting from your *full* build log: | Install the project... | /usr/bin/cmake -P cmake_install.cmake | -- Install configuration: "None" | -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/lib64/libdislocker.so.0.7.2 | -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/lib64/libdislocker.so.0.7 | -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/lib64/libdislocker.so | -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/bin/dislocker-fuse | -- Set runtime path of "/<<PKGBUILDDIR>>/debian/tmp/usr/bin/dislocker-fuse" to "" | -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/man/man1/dislocker-fuse.1.gz | -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/bin/dislocker-file | -- Set runtime path of "/<<PKGBUILDDIR>>/debian/tmp/usr/bin/dislocker-file" to "" | -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/man/man1/dislocker-file.1.gz | -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/bin/dislocker-metadata | -- Set runtime path of "/<<PKGBUILDDIR>>/debian/tmp/usr/bin/dislocker-metadata" to "" | -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/bin/dislocker-bek | -- Set runtime path of "/<<PKGBUILDDIR>>/debian/tmp/usr/bin/dislocker-bek" to "" | -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/bin/dislocker-find | -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/man/man1/dislocker-find.1.gz | make[1]: Leaving directory '/<<PKGBUILDDIR>>' | debian/rules override_dh_install-arch | make[1]: Entering directory '/<<PKGBUILDDIR>>' | dh_install | mv /<<PKGBUILDDIR>>/debian/tmp/usr/lib/libdislocker* \ | /<<PKGBUILDDIR>>/debian/libdislocker0.7/usr/lib/ | mv: cannot stat '/<<PKGBUILDDIR>>/debian/tmp/usr/lib/libdislocker*': No such file or directory So that feels like a problem between /usr/lib64 vs /usr/lib on your system? My experimental environment has merged-usr layout: | # ls -la /var/cache/pbuilder/base-exp-amd64.cow/ | total 300 | drwxr-xr-x 18 root root 4096 Nov 25 17:02 . | drwxr-xr-x 24 root root 4096 Nov 25 17:03 .. | -rw-r--r-- 1 root root 232304 Nov 25 17:02 .ilist | lrwxrwxrwx 1 root root 7 Sep 19 08:53 bin -> usr/bin | drwxr-xr-x 2 root root 4096 Jan 14 2018 boot | drwxr-xr-x 2 root root 4096 Jul 13 2018 build | drwxr-xr-x 4 root root 4096 Nov 25 17:02 dev | drwxr-xr-x 32 root root 4096 Nov 25 17:02 etc | drwxr-xr-x 2 root root 4096 Jan 14 2018 home | lrwxrwxrwx 1 root root 7 Sep 19 08:53 lib -> usr/lib | lrwxrwxrwx 1 root root 9 Sep 19 08:53 lib32 -> usr/lib32 | lrwxrwxrwx 1 root root 9 Sep 19 08:53 lib64 -> usr/lib64 | lrwxrwxrwx 1 root root 10 Sep 19 08:53 libx32 -> usr/libx32 | [...] Might this be related?
In my lxd container I have a similar layout: # ls -la / total 68 drwxr-xr-x 17 root root 4096 Nov 21 06:15 . drwxr-xr-x 17 root root 4096 Nov 21 06:15 .. lrwxrwxrwx 1 root root 7 Nov 21 06:06 bin -> usr/bin drwxr-xr-x 2 root root 4096 Oct 3 21:30 boot drwxr-xr-x 8 root root 500 Nov 21 20:01 dev drwxr-xr-x 79 root root 4096 Nov 21 21:00 etc drwxr-xr-x 3 root root 4096 Nov 21 20:39 home lrwxrwxrwx 1 root root 7 Nov 21 06:06 lib -> usr/lib lrwxrwxrwx 1 root root 9 Nov 21 06:06 lib32 -> usr/lib32 lrwxrwxrwx 1 root root 9 Nov 21 06:06 lib64 -> usr/lib64 lrwxrwxrwx 1 root root 10 Nov 21 06:06 libx32 -> usr/libx32 drwxr-xr-x 2 root root 4096 Nov 21 06:06 media drwxr-xr-x 2 root root 4096 Nov 21 06:06 mnt drwxr-xr-x 2 root root 4096 Nov 21 06:06 opt dr-xr-xr-x 1264 nobody nogroup 0 Nov 21 20:01 proc drwx------ 7 root root 12288 Nov 29 20:26 root drwxr-xr-x 11 root root 320 Nov 21 20:20 run lrwxrwxrwx 1 root root 8 Nov 21 06:06 sbin -> usr/sbin drwxr-xr-x 2 root root 4096 Nov 21 06:06 srv dr-xr-xr-x 13 nobody nogroup 0 Nov 21 20:01 sys drwxrwxrwt 11 root root 12288 Nov 29 20:26 tmp drwxr-xr-x 14 root root 4096 Nov 21 06:06 usr drwxr-xr-x 11 root root 4096 Nov 21 06:06 var I am not sure if this is the cause of the build failure. -- Lucas Kanashiro
