[Bash-completion-devel] Processed: Re: Bug#501479: bash-completion: Many incorrect assumptions based on uname

Debian Bug Tracking System owner at bugs.debian.org
Fri Oct 10 20:48:46 UTC 2008


Processing commands for control at bugs.debian.org:

> retitle 501479 don't assume sed being GNU sed on Linux systems
Bug#501479: bash-completion: Many incorrect assumptions based on uname
Changed Bug title to `don't assume sed being GNU sed on Linux systems' from `bash-completion: Many incorrect assumptions based on uname'.

> clone 501479 -1
Bug#501479: don't assume sed being GNU sed on Linux systems
Bug 501479 cloned as bug 501835.

> retitle -1 check for the use of `uname` within man, apropos, whatis completions
Bug#501835: don't assume sed being GNU sed on Linux systems
Changed Bug title to `check for the use of `uname` within man, apropos, whatis completions' from `don't assume sed being GNU sed on Linux systems'.

> priority -1 minor
Bug#501835: check for the use of `uname` within man, apropos, whatis completions
Severity set to `minor' from `normal'

> clone 501479 -2
Bug#501479: don't assume sed being GNU sed on Linux systems
Bug 501479 cloned as bug 501836.

> retitle -2 check for conflicts with killall5 (killall on SysV) for killall, pkill and pgrep completions
Bug#501836: don't assume sed being GNU sed on Linux systems
Changed Bug title to `check for conflicts with killall5 (killall on SysV) for killall, pkill and pgrep completions' from `don't assume sed being GNU sed on Linux systems'.

> clone 501479 -3
Bug#501479: don't assume sed being GNU sed on Linux systems
Bug 501479 cloned as bug 501837.

> retitle -3 don't use uname for pidof completion, just check for its presence
Bug#501837: don't assume sed being GNU sed on Linux systems
Changed Bug title to `don't use uname for pidof completion, just check for its presence' from `don't assume sed being GNU sed on Linux systems'.

> block -3 by -2
Bug#501836: check for conflicts with killall5 (killall on SysV) for killall, pkill and pgrep completions
Bug#501837: don't use uname for pidof completion, just check for its presence
Was not blocked by any bugs.
Blocking bugs of 501837 added: 501836

> priority -3 minor
Bug#501837: don't use uname for pidof completion, just check for its presence
Severity set to `minor' from `normal'

> clone 501479 -4
Bug#501479: don't assume sed being GNU sed on Linux systems
Bug 501479 cloned as bug 501838.

> retitle -4 don't use uname for if{up,down,status}, just check for their presence
Bug#501838: don't assume sed being GNU sed on Linux systems
Changed Bug title to `don't use uname for if{up,down,status}, just check for their presence' from `don't assume sed being GNU sed on Linux systems'.

> priority -4 minor
Bug#501838: don't use uname for if{up,down,status}, just check for their presence
Severity set to `minor' from `normal'

> clone 501479 -5
Bug#501479: don't assume sed being GNU sed on Linux systems
Bug 501479 cloned as bug 501839.

> retitle -5 don't use uname for iw{config,list,spy,priv}, just check for their presence
Bug#501839: don't assume sed being GNU sed on Linux systems
Changed Bug title to `don't use uname for iw{config,list,spy,priv}, just check for their presence' from `don't assume sed being GNU sed on Linux systems'.

> priority -5 minor
Bug#501839: don't use uname for iw{config,list,spy,priv}, just check for their presence
Severity set to `minor' from `normal'

> clone 501479 -6
Bug#501479: don't assume sed being GNU sed on Linux systems
Bug 501479 cloned as bug 501840.

> retitle -6 don't use uname for ipsec, just check for its presence
Bug#501840: don't assume sed being GNU sed on Linux systems
Changed Bug title to `don't use uname for ipsec, just check for its presence' from `don't assume sed being GNU sed on Linux systems'.

> priority -6 minor
Bug#501840: don't use uname for ipsec, just check for its presence
Severity set to `minor' from `normal'

> clone 501479 -7
Bug#501479: don't assume sed being GNU sed on Linux systems
Bug 501479 cloned as bug 501841.

> retitle -7 don't use uname for route, just check for its presence
Bug#501841: don't assume sed being GNU sed on Linux systems
Changed Bug title to `don't use uname for route, just check for its presence' from `don't assume sed being GNU sed on Linux systems'.

> priority -7 minor
Bug#501841: don't use uname for route, just check for its presence
Severity set to `minor' from `normal'

> clone 501479 -8
Bug#501479: don't assume sed being GNU sed on Linux systems
Bug 501479 cloned as bug 501842.

> retitle -8 complete for 'cc' also on !GNU, !Linux and !Cygwin
Bug#501842: don't assume sed being GNU sed on Linux systems
Changed Bug title to `complete for 'cc' also on !GNU, !Linux and !Cygwin' from `don't assume sed being GNU sed on Linux systems'.

> priority -8 minor
Bug#501842: complete for 'cc' also on !GNU, !Linux and !Cygwin
Severity set to `minor' from `normal'

> clone 501479 -9
Bug#501479: don't assume sed being GNU sed on Linux systems
Bug 501479 cloned as bug 501843.

> retitle -9 unused local variable UNAME in _info()
Bug#501843: don't assume sed being GNU sed on Linux systems
Changed Bug title to `unused local variable UNAME in _info()' from `don't assume sed being GNU sed on Linux systems'.

> priority -9 minor
Bug#501843: unused local variable UNAME in _info()
Severity set to `minor' from `normal'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




More information about the Bash-completion-devel mailing list