[Bash-completion-devel] Bug#813767: bash-completion: dpkg -P completion of unconfigured packages
Kevin Ryde
user42_kevin at yahoo.com.au
Fri Feb 5 05:09:07 UTC 2016
Package: bash-completion
Version: 1:2.1-4.2
Severity: normal
File: /usr/share/bash-completion/completions/dpkg
If a package is installed but unconfigured then it is not offered as a
completion for "dpkg -P", whereas I hoped it would.
I struck this on an arch "all" perl package installed by "dpkg -i" but
which was missing a dependency,
...
dependency problems - leaving unconfigured
The status line was
Status: install ok unpacked
I never remember the subtle stages a package with problems may go
through. Perhaps almost any installed-ness is a candidate to purge.
-- System Information:
Debian Release: stretch/sid
Architecture: i386 (i686)
Kernel: Linux 4.3.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages bash-completion depends on:
ii bash 4.3-14+b1
ii dpkg 1.18.4
bash-completion recommends no packages.
bash-completion suggests no packages.
-- no debconf information
More information about the Bash-completion-devel
mailing list