Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

2023-02-27 Thread Eriberto Mota
Em seg., 27 de fev. de 2023 às 06:42, Santiago Vila escreveu: > > El 26/2/23 a las 0:04, Adrian Bunk escribió: > > The Ubuntu diff has a fix for this issue caused by merged /usr > > (untested). > > Note: Such diff was actually already in #1017937. I've just merged > both bugs. Also, I've tested

Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

2023-02-27 Thread Santiago Vila
El 26/2/23 a las 0:04, Adrian Bunk escribió: The Ubuntu diff has a fix for this issue caused by merged /usr (untested). Note: Such diff was actually already in #1017937. I've just merged both bugs. Also, I've tested the diff and confirm that it works. Thanks.

Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

2023-02-25 Thread Adrian Bunk
On Tue, Feb 07, 2023 at 03:10:27PM +0100, Santiago Vila wrote: > 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

Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

2023-02-07 Thread Santiago Vila
Hi. I said: 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. I attach a proof of

Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

2023-02-07 Thread Santiago Vila
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

Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

2022-11-29 Thread Lucas Kanashiro
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, |

Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

2022-11-25 Thread Michael Prokop
* 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

Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

2022-11-21 Thread Lucas Kanashiro
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.