* Niels Thykier <[email protected]> [260126 04:24]:
I have written some simple end-to-end build tests in e86b3cb2009a82403ffc28815215f896e5852008 with the aim of having a test case for this problem. Unfortunately, none of my 4 cases trigger the bug you filed. I can reproduce it on `shadow`, but I am missing something to distill a minimal case. If you have any ideas what I might have over looked, I would be very happy to get input.
I wonder if the -rrr test correctly invokes dh. I tried to add a second binary package, and a dh .install file for it, but then still got debputy to complain about missing install rules.
diff --git i/e2e-tests/arch-any-test-rrr/debian/control w/e2e-tests/arch-any-test-rrr/debian/control index 1dc8185..4a4cdca 100644 --- i/e2e-tests/arch-any-test-rrr/debian/control +++ w/e2e-tests/arch-any-test-rrr/debian/control @@ -9,3 +9,10 @@ Description: Test case This is a binary from a test case. . Installation is not recommended. + +Package: test-package2 +Architecture: any +Description: Test case + This is a binary from a test case. + . + Installation is not recommended. diff --git i/e2e-tests/arch-any-test-rrr/debian/test-package2.install w/e2e-tests/arch-any-test-rrr/debian/test-package2.install new file mode 100644 index 0000000..241f075 --- /dev/null +++ w/e2e-tests/arch-any-test-rrr/debian/test-package2.install @@ -0,0 +1 @@ +usr/bin/test-elf % e2e-tests/run-tests /home/ch/Debian/debputy/debputy.sh Running end-to-end build tests make -j1 INSTALL="install --strip-program=true" cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/tmp/tmp.HI4ea8oU9O/arch-any-test-rrr/unpacked-source=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wl,-z,relro -mbranch-protection=standard test-elf.c -o test-elf make -j1 install DESTDIR=/tmp/tmp.HI4ea8oU9O/arch-any-test-rrr/unpacked-source/debian/tmp AM_UPDATE_INFO_DIR=no INSTALL="install --strip-program=true" install -m0755 -Dt/tmp/tmp.HI4ea8oU9O/arch-any-test-rrr/unpacked-source/debian/tmp/usr/bin test-elf debputy: info: Upstream builds completed successfully debputy: error: The build system appears to have provided the output of upstream build system's install in debian/tmp. However, these are no provisions for debputy to install any of that into any of the debian packages listed in debian/control. To avoid accidentally creating empty packages, debputy will insist that you explicitly define an empty installation definition if you did not want to install any of those files even though they have been provided. Example: "installations: []" ERROR: arch-any-test-rrr. Test dir at /tmp/tmp.HI4ea8oU9O/arch-any-test-rrr/unpacked-source for debugging (full output in /tmp/tmp.HI4ea8oU9O/arch-any-test-rrr/unpacked-source/../output.log) In any case I'm wondering if the problem only occurs with a multi-binary package. Chris
