severity 1024589 serious
thanks
Hi. I can reproduce this, and I believe everybody who will try
to build the package using sbuild right now in unstable should also
be able to reproduce it.
(If you still can't reproduce it and need a test machine,
please contact me privately, I can offer ssh access to a machine
where it always happens).
Regarding the bug itself. this seems to happen because
dh_install now puts the stuff in debian/tmp/lib64 while
debian/rules does this:
dh_install
mv $(TEMPDEB)/usr/lib/libdislocker* \
$(DESTDIRLIB)/usr/lib/
i.e. expecting stuff to be in usr/lib/libdislocker*,
but it's no longer there. Maybe because of ruby3.1,
maybe because usr-merge, I don't know. Both of them
are now the default so we'll have to cope with that.
Instead of using "mv" after dh_install, I would probably
try to refactor this using debian/foo.install files,
which allow wilcards.
Those debian/*.install files would tell dh_install where
to put things, without having to move them ourselves in debian/rules.
Thanks.
