Control: reassign 1.21.22 debconf On Fri, Aug 11, 2023 at 04:07:11PM +0000, t3atwv+9rzw960a1ydj0@cs.email wrote: > Dear Maintainer, > > It doesn't matter which package you try to install, I'm using 'hello' as an > example of a very simple package with no dependencies. > > If you try to run an `apt install` command while you are in a directory that > has been deleted, you will get error messages. > > Example command: > $ mkdir /tmp/hello; cd /tmp/hello; rmdir /tmp/hello; sudo apt install hello > > You get an output that includes these lines: > sh: 0: getcwd() failed: No such file or directory > sh: 0: getcwd() failed: No such file or directory > sh: 0: getcwd() failed: No such file or directory > sh: 0: getcwd() failed: No such file or directory > sh: 0: getcwd() failed: No such file or directory > cannot fetch initial working directory: No such file or directory at > /usr/sbin/dpkg-preconfigure line 73. > cannot fetch initial working directory: No such file or directory at > /usr/sbin/dpkg-preconfigure line 159. > > The package installs successfully, but the messages are still not something > the user should see.
This is actually a debconf bug as the warnings/errors are emitted by /usr/sbin/dpkg-preconfigure. I don't fully agree that this is a bug but I'll let the debconf folks decide over that. I think it is quite useful to have this information in case things would go wrong because being in a non-existent directory might not be a normal situation. The reproduction path can be slightly adjusted to: mkdir /tmp/hello; cd /tmp/hello; rmdir /tmp/hello; sudo /usr/sbin/dpkg-preconfigure hello I can verify that the behavior is present on bookworm and unstable. Cheers, Wesley
