* Lucas Kanashiro [Mon Nov 21, 2022 at 05:11:55PM -0300]: > Source: dislocker > Version: 0.7.3-2.1 > Severity: important > Justification: FTBFS > Tags: bookworm sid ftbfs > User:debian-r...@lists.debian.org > Usertags: ruby3.1 > > We are about to start the ruby3.1 transition in unstable. While trying to > rebuild dislocker with ruby3.1 enabled, the build failed.
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. > Relevant part of the build log (hopefully): > > 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 > make[1]: *** [debian/rules:16: override_dh_install-arch] Error 1 > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > make: *** [debian/rules:12: binary] Error 2 > > The full build log is available from: > > https://people.debian.org/~kanashiro/ruby3.1/20/dislocker/dislocker_0.7.3-2.1+rebuild1667925374_amd64-2022-11-08T16:36:15Z.build 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? regards -mika-
signature.asc
Description: PGP signature
