Debian Bug report logs -
#497597
bash-completion: gdb argument completions returns error
Reported by: Kevin Mitchell <kevmitch@gmail.com>
Date: Tue, 2 Sep 2008 23:06:01 UTC
Severity: normal
Tags: confirmed, moreinfo
Found in version bash-completion/20080705
Fixed in version bash-completion/1:1.0-1
Done: David Paleino <d.paleino@gmail.com>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded to debian-bugs-dist@lists.debian.org, Bash Completion Maintainers <bash-completion-devel@lists.alioth.debian.org>:
Bug#497597; Package bash-completion.
(full text, mbox, link).
Acknowledgement sent to Kevin Mitchell <kevmitch@gmail.com>:
New Bug report received and forwarded. Copy sent to Bash Completion Maintainers <bash-completion-devel@lists.alioth.debian.org>.
(full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: bash-completion
Version: 20080705
Severity: normal
$ gdb <tab>
find: cannot search `': No such file or directory
Kevin
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'testing'), (400, 'stable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.27-rc5-amd64.010 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to en_GB)
Shell: /bin/sh linked to /bin/dash
Versions of packages bash-completion depends on:
ii bash 3.2-4 The GNU Bourne Again SHell
bash-completion recommends no packages.
bash-completion suggests no packages.
-- no debconf information
Tags added: unreproducible, moreinfo
Request was from David Paleino <d.paleino@gmail.com>
to control@bugs.debian.org.
(Sat, 06 Sep 2008 14:18:06 GMT) (full text, mbox, link).
Acknowledgement sent to David Paleino <d.paleino@gmail.com>:
Extra info received and filed, but not forwarded.
(full text, mbox, link).
Message #12 received at 497597-quiet@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
tags 497597 unreproducible moreinfo
thanks
Hi Kevin,
Kevin Mitchell wrote:
> Package: bash-completion
> Version: 20080705
> [..]
>
> $ gdb <tab>
> find: cannot search `': No such file or directory
I'm sorry I can't reproduce this with our current development version --
probably we already fixed it with some other bug.
Would you please try the attached bash_completion, and see if it works for you
as well? Please, backup your old bash_completion, and be warned that what I'm
attaching is not ready to be released. Keep it at your own risk! :)
Kindly,
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
[bash_completion.gz (application/x-gzip, attachment)]
[signature.asc (application/pgp-signature, attachment)]
Acknowledgement sent to "Kevin Mitchell" <kevmitch@gmail.com>:
Extra info received and filed, but not forwarded.
(full text, mbox, link).
Message #17 received at 497597-quiet@bugs.debian.org (full text, mbox, reply):
It seems to do the same thing. I tried picking things apart a little
more this time by just entering parts of the gdb entry in the shell.
Now I'm really confused:
$ IFS=":"
$ path_array=( $(echo "$PATH") )
$ IFS=$'\n'
$ find "${path_array[@]}" . -mindepth 1 -maxdepth 1 -not -type d
-executable -printf "%f\\n" > /dev/null
find: cannot search `': No such file or directory
$ echo find "${path_array[@]}" . -mindepth 1 -maxdepth 1 -not -type d
-executable -printf "%f\\n"
find /home/kevmitch/bin /usr/local/bin /usr/bin /bin /usr/games .
-mindepth 1 -maxdepth 1 -not -type d -executable -printf %f\n
$ find /home/kevmitch/bin /usr/local/bin /usr/bin /bin /usr/games .
-mindepth 1 -maxdepth 1 -not -type d -executable -printf %f\n >
/dev/null
$ wtf?
bash: wtf?: command not found
$ ls -l /bin/sh
lrwxrwxrwx 1 root root 4 2008-08-21 14:44 /bin/sh -> bash
$ apt-cache policy findutils
findutils:
Installed: 4.4.0-2
Candidate: 4.4.0-2
Version table:
*** 4.4.0-2 0
500 http://debian.yorku.ca testing/main Packages
600 http://debian.yorku.ca unstable/main Packages
100 /var/lib/dpkg/status
4.2.28-1etch1 0
400 http://debian.yorku.ca stable/main Packages
Kevin
On Sat, Sep 6, 2008 at 7:15 AM, David Paleino <d.paleino@gmail.com> wrote:
> tags 497597 unreproducible moreinfo
> thanks
>
> Hi Kevin,
>
> Kevin Mitchell wrote:
>> Package: bash-completion
>> Version: 20080705
>> [..]
>>
>> $ gdb <tab>
>> find: cannot search `': No such file or directory
>
> I'm sorry I can't reproduce this with our current development version --
> probably we already fixed it with some other bug.
>
> Would you please try the attached bash_completion, and see if it works for you
> as well? Please, backup your old bash_completion, and be warned that what I'm
> attaching is not ready to be released. Keep it at your own risk! :)
>
> Kindly,
> David
>
> --
> . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
> : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
> `. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
> `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
>
Acknowledgement sent to David Paleino <d.paleino@gmail.com>:
Extra info received and filed, but not forwarded.
(full text, mbox, link).
Message #22 received at 497597-quiet@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On Sat, 6 Sep 2008 14:02:40 -0700, Kevin Mitchell wrote:
> It seems to do the same thing. I tried picking things apart a little
> more this time by just entering parts of the gdb entry in the shell.
> Now I'm really confused:
>
> $ IFS=":"
> $ path_array=( $(echo "$PATH") )
> $ IFS=$'\n'
> $ find "${path_array[@]}" . -mindepth 1 -maxdepth 1 -not -type d
> -executable -printf "%f\\n" > /dev/null
> find: cannot search `': No such file or directory
I can't reproduce all this, sorry.
$ IFS=":"
$ path_array=( $(echo "$PATH") )
$ IFS=$'\n'
$ find "${path_array[@]}" . -mindepth 1 -maxdepth 1 -not -type d -executable \
> -printf "%f\\n" > /dev/null
$
Could this be a find(1) bug? But, well, it should happen here as well.
Do you have any "strange" configuration? LVM, ...?
> $ echo find "${path_array[@]}" . -mindepth 1 -maxdepth 1 -not -type d
> -executable -printf "%f\\n"
find /home/neo/bin /usr/local/bin /usr/bin /bin /usr/games /home/neo/bin /sbin /usr/sbin /usr/local/sbin /home/neo/bin /sbin /usr/sbin /usr/local/sbin .
-mindepth 1 -maxdepth 1 -not -type d -executable -printf %f\n
> $ find /home/kevmitch/bin /usr/local/bin /usr/bin /bin /usr/games .
> -mindepth 1 -maxdepth 1 -not -type d -executable -printf %f\n >
> /dev/null
$
Ok, the same result I had above.
> $ wtf?
> bash: wtf?: command not found
Oh, well :)
> $ ls -l /bin/sh
> lrwxrwxrwx 1 root root 4 2008-08-21 14:44 /bin/sh -> bash
$ ls -l /bin/sh
lrwxrwxrwx 1 root root 4 16 mag 14:53 /bin/sh -> bash
> $ apt-cache policy findutils
> findutils:
> Installed: 4.4.0-2
> Candidate: 4.4.0-2
> Version table:
> *** 4.4.0-2 0
> 500 http://debian.yorku.ca testing/main Packages
> 600 http://debian.yorku.ca unstable/main Packages
> 100 /var/lib/dpkg/status
> 4.2.28-1etch1 0
> 400 http://debian.yorku.ca stable/main Packages
$ LANG=C apt-cache policy findutils
findutils:
Installed: 4.4.0-2
Candidate: 4.4.0-2
Version table:
*** 4.4.0-2 0
500 http://ftp.de.debian.org unstable/main Packages
100 /var/lib/dpkg/status
$
I can't really see anything different, apart from the very first part I quoted.
Are you sure you aren't typing any strange-non-printable character? :)
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
[signature.asc (application/pgp-signature, attachment)]
Acknowledgement sent to "Kevin Mitchell" <kevmitch@gmail.com>:
Extra info received and filed, but not forwarded.
(full text, mbox, link).
Message #27 received at 497597-quiet@bugs.debian.org (full text, mbox, reply):
Ok, well it probably should have occured to me to actually include my
$PATH variable:
$ echo $PATH
:/home/kevmitch/bin:/usr/local/bin:/usr/bin:/bin:/usr/games
Note the preceding ":" which should include the current directory in
accordance with bash(1):
PATH The search path for commands. It is a colon-separated
list of directories in which the
shell looks for commands (see COMMAND EXECUTION below).
A zero-length (null) directory
name in the value of PATH indicates the current
directory. A null directory name may
appear as two adjacent colons, or as an initial or
trailing colon. . .
If I turn that into
$PATH=.$PATH
$IFS=":"
$path_array=( $(echo "$PATH") )
$IFS=$'\n'
$find "${path_array[@]}" . -mindepth 1 -maxdepth 1 -not -type d
-executable -printf "%f\\n" > /dev/null
$
then we're good to go. I still can't say I completely understand this,
I guess because I don't really understand what's happening in 'find
"${path_array[@]}"'. I guess I would have expected this bug to show up
as find not searching the current directory. Is there a
straightforward way to search and replace an empty field with "." for
find's benefit other than a for/sed?
Kevin
On Sat, Sep 6, 2008 at 2:27 PM, David Paleino <d.paleino@gmail.com> wrote:
> On Sat, 6 Sep 2008 14:02:40 -0700, Kevin Mitchell wrote:
>
>> It seems to do the same thing. I tried picking things apart a little
>> more this time by just entering parts of the gdb entry in the shell.
>> Now I'm really confused:
>>
>> $ IFS=":"
>> $ path_array=( $(echo "$PATH") )
>> $ IFS=$'\n'
>> $ find "${path_array[@]}" . -mindepth 1 -maxdepth 1 -not -type d
>> -executable -printf "%f\\n" > /dev/null
>> find: cannot search `': No such file or directory
>
> I can't reproduce all this, sorry.
>
> $ IFS=":"
> $ path_array=( $(echo "$PATH") )
> $ IFS=$'\n'
> $ find "${path_array[@]}" . -mindepth 1 -maxdepth 1 -not -type d -executable \
>> -printf "%f\\n" > /dev/null
> $
>
> Could this be a find(1) bug? But, well, it should happen here as well.
> Do you have any "strange" configuration? LVM, ...?
>
>> $ echo find "${path_array[@]}" . -mindepth 1 -maxdepth 1 -not -type d
>> -executable -printf "%f\\n"
>
> find /home/neo/bin /usr/local/bin /usr/bin /bin /usr/games /home/neo/bin /sbin /usr/sbin /usr/local/sbin /home/neo/bin /sbin /usr/sbin /usr/local/sbin .
> -mindepth 1 -maxdepth 1 -not -type d -executable -printf %f\n
>
>> $ find /home/kevmitch/bin /usr/local/bin /usr/bin /bin /usr/games .
>> -mindepth 1 -maxdepth 1 -not -type d -executable -printf %f\n >
>> /dev/null
> $
>
> Ok, the same result I had above.
>
>> $ wtf?
>> bash: wtf?: command not found
>
> Oh, well :)
>
>> $ ls -l /bin/sh
>> lrwxrwxrwx 1 root root 4 2008-08-21 14:44 /bin/sh -> bash
>
> $ ls -l /bin/sh
> lrwxrwxrwx 1 root root 4 16 mag 14:53 /bin/sh -> bash
>
>> $ apt-cache policy findutils
>> findutils:
>> Installed: 4.4.0-2
>> Candidate: 4.4.0-2
>> Version table:
>> *** 4.4.0-2 0
>> 500 http://debian.yorku.ca testing/main Packages
>> 600 http://debian.yorku.ca unstable/main Packages
>> 100 /var/lib/dpkg/status
>> 4.2.28-1etch1 0
>> 400 http://debian.yorku.ca stable/main Packages
>
> $ LANG=C apt-cache policy findutils
> findutils:
> Installed: 4.4.0-2
> Candidate: 4.4.0-2
> Version table:
> *** 4.4.0-2 0
> 500 http://ftp.de.debian.org unstable/main Packages
> 100 /var/lib/dpkg/status
> $
>
>
> I can't really see anything different, apart from the very first part I quoted.
>
> Are you sure you aren't typing any strange-non-printable character? :)
>
> David
>
> --
> . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
> : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
> `. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
> `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
>
Acknowledgement sent to Morita Sho <morita-pub-en-debian@inz.sakura.ne.jp>:
Extra info received and filed, but not forwarded.
(full text, mbox, link).
Message #32 received at 497597-quiet@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Hi,
On 09/07/2008 01:05 PM, Kevin Mitchell wrote:
> Ok, well it probably should have occured to me to actually include my
> $PATH variable:
>
> $ echo $PATH
> :/home/kevmitch/bin:/usr/local/bin:/usr/bin:/bin:/usr/games
>
> Note the preceding ":" which should include the current directory in
> accordance with bash(1):
>
> PATH The search path for commands. It is a colon-separated
> list of directories in which the
> shell looks for commands (see COMMAND EXECUTION below).
> A zero-length (null) directory
> name in the value of PATH indicates the current
> directory. A null directory name may
> appear as two adjacent colons, or as an initial or
> trailing colon. . .
>
> If I turn that into
> $PATH=.$PATH
> $IFS=":"
> $path_array=( $(echo "$PATH") )
> $IFS=$'\n'
> $find "${path_array[@]}" . -mindepth 1 -maxdepth 1 -not -type d
> -executable -printf "%f\\n" > /dev/null
> $
> then we're good to go. I still can't say I completely understand this,
> I guess because I don't really understand what's happening in 'find
> "${path_array[@]}"'. I guess I would have expected this bug to show up
> as find not searching the current directory. Is there a
> straightforward way to search and replace an empty field with "." for
> find's benefit other than a for/sed?
I guess removing any zero-length directory name before splitting the PATH
variable solves the problem.
A patch is attached.
I hope this helps,
--
Morita Sho <morita-pub-en-debian@inz.sakura.ne.jp>
[remove-zero-length-directory-name.patch (text/x-patch, inline)]
--- bash_completion.orig 2008-09-07 12:57:43.000000000 +0900
+++ bash_completion 2008-09-07 13:01:43.000000000 +0900
@@ -4055,7 +4055,7 @@
# functions and aliases. Thus we need to retrieve the program
# names manually.
IFS=":"
- local path_array=( $(echo "$PATH") )
+ local path_array=( $(echo "$PATH" | sed 's/::\+/:/g;s/^:\|:$//g') )
IFS=$'\n'
COMPREPLY=( $( compgen -d -W '$(find "${path_array[@]}" . \
-mindepth 1 -maxdepth 1 -not -type d -executable -printf "%f\\n")' \
Tags added: confirmed, pending
Request was from David Paleino <d.paleino@gmail.com>
to control@bugs.debian.org.
(Sun, 07 Sep 2008 08:39:07 GMT) (full text, mbox, link).
Tags removed: unreproducible
Request was from David Paleino <d.paleino@gmail.com>
to control@bugs.debian.org.
(Sun, 07 Sep 2008 08:39:07 GMT) (full text, mbox, link).
Acknowledgement sent to David Paleino <d.paleino@gmail.com>:
Extra info received and filed, but not forwarded.
(full text, mbox, link).
Message #41 received at 497597-quiet@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On Sun, 07 Sep 2008 13:56:35 +0900, Morita Sho wrote:
> Hi,
Hello,
> On 09/07/2008 01:05 PM, Kevin Mitchell wrote:
> > Ok, well it probably should have occured to me to actually include my
> > $PATH variable:
> >
> > $ echo $PATH
> > :/home/kevmitch/bin:/usr/local/bin:/usr/bin:/bin:/usr/games
> >
> > Note the preceding ":" which should include the current directory in
> > accordance with bash(1):
> > [..]
> > Is there a
> > straightforward way to search and replace an empty field with "." for
> > find's benefit other than a for/sed?
>
> I guess removing any zero-length directory name before splitting the PATH
> variable solves the problem.
Yes, probably.
> A patch is attached.
Great, thanks :)
Fixed in rev1178
Kindly,
David
P.S.: however, I read somewhere (can't remember where, sorry), that adding "."
to $PATH is a bad habit...
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
[signature.asc (application/pgp-signature, attachment)]
Acknowledgement sent to David Paleino <d.paleino@gmail.com>:
Extra info received and filed, but not forwarded.
(full text, mbox, link).
Message #46 received at 497597-quiet@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On Sun, 7 Sep 2008 10:38:17 +0200, David Paleino wrote:
> On Sun, 07 Sep 2008 13:56:35 +0900, Morita Sho wrote:
>
> > On 09/07/2008 01:05 PM, Kevin Mitchell wrote:
> > > Ok, well it probably should have occured to me to actually include my
> > > $PATH variable:
> > >
> > > $ echo $PATH
> > > :/home/kevmitch/bin:/usr/local/bin:/usr/bin:/bin:/usr/games
> > >
> > > Note the preceding ":" which should include the current directory in
> > > accordance with bash(1):
>
> [..]
>
> P.S.: however, I read somewhere (can't remember where, sorry), that adding "."
> to $PATH is a bad habit...
Imagine you write a script and call it "ls", then save it in a directory where
you have access, /tmp/ for example. Now if you get another user to run "ls"
in /tmp/ as root and have "." in the PATH, that will run your script instead of
running the real "ls". This way you can do some nasty tricks. :)
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
[signature.asc (application/pgp-signature, attachment)]
Reply sent
to David Paleino <d.paleino@gmail.com>:
You have taken responsibility.
(Sat, 04 Apr 2009 14:12:19 GMT) (full text, mbox, link).
Notification sent
to Kevin Mitchell <kevmitch@gmail.com>:
Bug acknowledged by developer.
(Sat, 04 Apr 2009 14:12:19 GMT) (full text, mbox, link).
Message #51 received at 497597-close@bugs.debian.org (full text, mbox, reply):
Source: bash-completion
Source-Version: 1:1.0-1
We believe that the bug you reported is fixed in the latest version of
bash-completion, which is due to be installed in the Debian FTP archive:
bash-completion_1.0-1.diff.gz
to pool/main/b/bash-completion/bash-completion_1.0-1.diff.gz
bash-completion_1.0-1.dsc
to pool/main/b/bash-completion/bash-completion_1.0-1.dsc
bash-completion_1.0-1_all.deb
to pool/main/b/bash-completion/bash-completion_1.0-1_all.deb
bash-completion_1.0.orig.tar.gz
to pool/main/b/bash-completion/bash-completion_1.0.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 497597@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
David Paleino <d.paleino@gmail.com> (supplier of updated bash-completion package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Fri, 03 Apr 2009 14:21:43 +0200
Source: bash-completion
Binary: bash-completion
Architecture: source all
Version: 1:1.0-1
Distribution: unstable
Urgency: low
Maintainer: Bash Completion Maintainers <bash-completion-devel@lists.alioth.debian.org>
Changed-By: David Paleino <d.paleino@gmail.com>
Description:
bash-completion - programmable completion for the bash shell
Closes: 272660 322238 360628 361535 489927 491856 492328 492476 494292 495142 495883 496162 496828 497074 497597 498105 499780 500316 501473 501843 502664 502804 502885 503317 503317 504141 504547 504650 506560 511789 511790 512556 512823 512917 516614 521041
Changes:
bash-completion (1:1.0-1) unstable; urgency=low
.
* New upstream release:
- also see /usr/share/doc/bash-completion/CHANGES.gz
- fix man -l completing filenames (Closes: #497074)
- (Partly) fixed java classes completion (Closes: #496828). Look for
FIXME in source.
- dump to /dev/null error message from look(1) with no arguments
(Closes: #495142)
- set ssh as default for rsync (was rsh) (Closes: #492328)
- added .oga, .ogv, .ogx to mplayer completion (Closes: #496162)
- added .epub to unzip|zipinfo completion (Closes: #492476)
- added ssh-copy-id completion (Closes: #491856)
- moved ssh completion to separate file (Closes: #360628)
- bogus completion when mounting subdirs fixed (Closes: #322238)
- fix `apt-cache showsrc` completing only on source package names
(Closes: #361535)
- fixed bugs with gdb completion:
- when an empty directory is in $PATH (thanks to Morita Sho)
(Closes: #497597)
- when a non-existing directory is in $PATH (Closes: #499780)
- fix missing completion for "-n" and "-e" (we were using echo, now
using printf) (thanks to Morita Sho) (Closes: #498105)
- fixed gpg completion --@(export|@(?(l|nr|nrl)sign|edit)-key))
(Closes: #500316)
- fixed .cb[rz] completion for evince (Closes: #502885)
- added gpg2 completion (Closes: #489927)
- fixed mplayer -skin completion (Closes: #501473)
- fixed errors with POSIX enabled (Closes: #502804)
- fixed dpkg-source wrong exit() with return() (Closes: #503317)
- added --schedule-only to aptitude's completion (Closes: #502664)
- added build-dep to aptitude's completion (Closes: #495883)
- added support for `-F configfile' to _known_hosts(), ssh, scp and
sftp, thanks to Freddy Vulto (Closes: #504141)
- fixed sed quoting bug in _known_hosts(), thanks to Freddy Vulto
(Closes: #504650)
- allow for comments in known_hosts files (Closes: #511789)
- fixed perl -I/-x completion, thanks to Freddy Vulto
(Closes: #504547)
- README updated: explain how to use bash-completion correctly.
(Closes: #506560)
- added qdbus completion, thanks to Terence Simpson (LP: #257903)
- fixed completion of environment variables, thanks to Morita Sho
(Closes: #272660)
- fix dpkg completion bug: it listed only non-Essential packages
(Closes: #511790)
- fixed _dpkg_source completion (Closes: #503317)
- remove unused UNAME local variable in _info() (Closes: #501843)
- added .zip to jar completions (Closes: #521041)
- Merge from Ubuntu:
+ consume error messages in configure completion (LP: #223882)
(Mika Fischer)
+ quote $xspec in _filedir_xspec in case it is empty, which would
cause errors if there was no match under failglob. (LP: #194419)
(Mika Fischer)
- Ville Skyttä:
+ remove duplicate cpio completion, thanks to Freddy Vulto
(Closes: #512823)
+ fix awk error in "modprobe -r /" completion (Closes: #512556)
- Jakob Unterwurzacher:
+ ps2pdf can run on .pdf files as well.
(Closes: #516614, LP: #316943)
* debian/links fixed (Closes: #494292)
* debian/control:
- fixed typo in the long description
- added Vcs-* fields
- Standards-Version to 3.8.1
- DMUA set
- removed Luk Claes from Uploaders
- Homepage added
* debian/install:
- correctly install contrib/* under /etc/bash_completion.d/
* debian/copyright updated
* debian/extra/dh_bash-completion:
- updated to support a list of files in debian/<package>.bash-completion
(Closes: #512917)
* debian/rules:
- install upstream CHANGES and AUTHORS too
Checksums-Sha1:
977d1414ca3556a4ad46aa2b48b9ca8e6e86a603 1308 bash-completion_1.0-1.dsc
61040795731f5ff509c46e818a1edf0a7a93e11d 143578 bash-completion_1.0.orig.tar.gz
49c583802082e3aa9a761fb0da0d5ec257f257bb 9002 bash-completion_1.0-1.diff.gz
cb38e807d9b23e84b866e6e9d24814991a61836a 103010 bash-completion_1.0-1_all.deb
Checksums-Sha256:
d369f9436c02262d3de898564cd9b5269ace760cf6b7e0632e3b251ac431f2b5 1308 bash-completion_1.0-1.dsc
bd96e7d2858f02783046908a984993736f1189d07d82e9ce4b465068dd7187ef 143578 bash-completion_1.0.orig.tar.gz
04c46eff31bf9dfb9e79f417bd79706b6dc67888461ab05128b29cff78c9556b 9002 bash-completion_1.0-1.diff.gz
81ab4b27a2158e787ea39c7da34619858a5df6b6251ba24d8bda6592feed46f4 103010 bash-completion_1.0-1_all.deb
Files:
6cb01d355c4519f911820b2b7c0feb53 1308 shells standard bash-completion_1.0-1.dsc
cd1c5648272917fbe0eef4ba30bb93f4 143578 shells standard bash-completion_1.0.orig.tar.gz
e78d5e31ed66fb5e97c77ea7c9f1b343 9002 shells standard bash-completion_1.0-1.diff.gz
aefc9e1c8db0f4f2b61557c2e207ca0c 103010 shells standard bash-completion_1.0-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAknXYZAACgkQ5UTeB5t8Mo0jGACfQVygJmdQ3v4i/dymRnZSVnhA
qHoAnjcS99HMQgFHzQ2NnNAY1OPvlPK6
=6i7t
-----END PGP SIGNATURE-----
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Wed, 13 May 2009 07:33:59 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Sun Jul 2 10:03:57 2023;
Machine Name:
buxtehude
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.