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
Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild dislocker with ruby3.1 enabled, the build failed. 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 To reproduce this, you need ruby-all-dev >= 1:3.1~0. Depending on when you read this, this might mean installing ruby-all-dev from experimental, or if the transition has already started in unstable, a normal build on unstable should do it. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. Seehttps://www.debian.org/Bugs/server-control#affects -- Lucas Kanashiro
