Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1043465: reportbug: apt install produces errors when run from a non-existing directory
67 views
Skip to first unread message
t3atwv+9rz...@cs.email
Aug 11, 2023, 12:10:05 PM8/11/23
to
Package: apt
Version: 2.6.1
Severity: normal
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.
I discovered this when I wanted to install some package, and I grabbed the nearest terminal window I had open without realizing the current working directory in that terminal has already been deleted from a different terminal window.
-- System Information:
Debian Release: 12.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-10-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages apt depends on:
ii adduser 3.134
ii debian-archive-keyring 2023.3
ii gpgv 2.2.40-1.1
ii libapt-pkg6.0 2.6.1
ii libc6 2.36-9+deb12u1
ii libgcc-s1 12.2.0-14
ii libgnutls30 3.7.9-2
ii libseccomp2 2.5.4-1+b3
ii libstdc++6 12.2.0-14
ii libsystemd0 252.12-1~deb12u1
Versions of packages apt recommends:
ii ca-certificates 20230311
Versions of packages apt suggests:
pn apt-doc <none>
pn aptitude | synaptic | wajig <none>
ii dpkg-dev 1.21.22
ii gnupg 2.2.40-1.1
pn powermgmt-base <none>
-- no debconf information
Version: 2.6.1
Severity: normal
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.
I discovered this when I wanted to install some package, and I grabbed the nearest terminal window I had open without realizing the current working directory in that terminal has already been deleted from a different terminal window.
-- System Information:
Debian Release: 12.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-10-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages apt depends on:
ii adduser 3.134
ii debian-archive-keyring 2023.3
ii gpgv 2.2.40-1.1
ii libapt-pkg6.0 2.6.1
ii libc6 2.36-9+deb12u1
ii libgcc-s1 12.2.0-14
ii libgnutls30 3.7.9-2
ii libseccomp2 2.5.4-1+b3
ii libstdc++6 12.2.0-14
ii libsystemd0 252.12-1~deb12u1
Versions of packages apt recommends:
ii ca-certificates 20230311
Versions of packages apt suggests:
pn apt-doc <none>
pn aptitude | synaptic | wajig <none>
ii dpkg-dev 1.21.22
ii gnupg 2.2.40-1.1
pn powermgmt-base <none>
-- no debconf information
0 new messages