Hi, Quoting Chris Hofstaedtler (2024-12-17 22:09:58) > Please test this scenario, and see if that works for you / what happens: > > cd /var/tmp > apt source hello > cd hello-2.10 > sbuild --chroot-mode=unshare --no-run-lintian > test -e hello_*changes && echo "whoops, wrote to wrong dir"
thank you. This is because of the convenience feature that sbuild gained in 2011 with commit 601af3d6f3a7028b88e1b88e7e3afeeeef4877bb. If you run sbuild inside an unpacked source directory, then sbuild will automatically run "dpkg-source -b ." for you and place the build artifacts in the parent. It does so by changing the working directory of the process to the parent and setting the *default* of BUILD_DIR to that directory. But at that point, the ~/.sbuildrc has long since been evaluated. And at the point where it got evaluated, the working directory was still the unpacked source directory and not its parent. The patch in this bug report sets the value of BUILD_DIR to the unpacked source dir and thus, changing the default of BUILD_DIR later on has no effect anymore because the value was already set to the default from back then... The fix is not trivial considering that we don't want the fix to this to break more things... Thanks! cheers, josch
signature.asc
Description: signature
