Your message dated Sat, 11 Jan 2025 21:49:20 -0800
with message-id <20250111214920.1c80f9ea@tigre>
and subject line
has caused the Debian Bug report #551707,
regarding handle move of dlocate completion between packages
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
551707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551707
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash-completion
Version: 1:1.1-1
Severity: normal
Hi David,
again me
dlocate /usr/sh<TAB><TAB> ...nothing
Again, that would be solved by what I have reported in another bug, namely
that bash-completion defaults to path completion if nothing else can be
found ....
uaaaa, sorry, but this will probably the last bug I report, I am killing
this package from my disk, it is more in my way then helping.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-rc5 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bash-completion depends on:
ii bash 4.0-7 The GNU Bourne Again SHell
bash-completion recommends no packages.
bash-completion suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Upstream completion from dlocate works as expected and there seems to
be no intent to migrate the completion file to bash-completion. Closing.
--- End Message ---
