Debian Bug report logs - #623479
bash-completion: p4 completion yields "bash: _get_comp_words_by_ref(): `preprev': unknown argument"

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Mike Crowe <mac@mcrowe.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: bash-completion: p4 completion yields "bash: _get_comp_words_by_ref(): `preprev': unknown argument"

Date: Wed, 20 Apr 2011 16:43:48 +0100

Package: bash-completion
Version: 1:1.2-3
Severity: normal

With the Perforce command line client "p4" and bash-completion installed if I type:

  p4 edit <TAB>

I get the following error:

  bash: _get_comp_words_by_ref(): `preprev': unknown argument

It appears that this has been fixed in
http://git.debian.org/?p=bash-completion/bash-completion.git;a=commitdiff;h=5eead0ebeecf7d3212df3fea9cfe0fa88b6d0274
but the fix didn't make it into squeeze.

-- System Information:
Debian Release: 6.0.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bash-completion depends on:
ii  bash                          4.1-3      The GNU Bourne Again SHell

bash-completion recommends no packages.

bash-completion suggests no packages.

-- no debconf information

Message #10 received at 623479@bugs.debian.org (full text, mbox, reply):

From: David Paleino <dapal@debian.org>

To: Mike Crowe <mac@mcrowe.com>

Cc: 623479@bugs.debian.org

Subject: Re: Bug#623479: bash-completion: p4 completion yields "bash: _get_comp_words_by_ref(): `preprev': unknown argument"

Date: Wed, 20 Apr 2011 18:53:31 +0200

[Message part 1 (text/plain, inline)]

fixed 623479 1:1.3-1
tags 623479 squeeze
thanks

Hello Mike,

On Wed, 20 Apr 2011 16:43:48 +0100, Mike Crowe wrote:

> With the Perforce command line client "p4" and bash-completion installed if I
> type:
> 
>   p4 edit <TAB>
> 
> I get the following error:
> 
>   bash: _get_comp_words_by_ref(): `preprev': unknown argument
> 
> It appears that this has been fixed in
> http://git.debian.org/?p=bash-completion/bash-completion.git;a=commitdiff;h=5eead0ebeecf7d3212df3fea9cfe0fa88b6d0274
> but the fix didn't make it into squeeze.

I fear the release team won't accept non-security-uploads to stable.

However, I can try to provide backports, yes. That seems the best thing I
can do, with current stable update policies. Would that be ok to you?

Kindly,
David

-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://deb.li/dapal
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

[signature.asc (application/pgp-signature, attachment)]

Message #19 received at 623479@bugs.debian.org (full text, mbox, reply):

From: Mike Crowe <mac@mcrowe.com>

To: David Paleino <dapal@debian.org>

Subject: Re: Bug#623479: bash-completion: p4 completion yields "bash: _get_comp_words_by_ref(): `preprev': unknown argument"

Date: Wed, 20 Apr 2011 18:07:00 +0100

On Wed, 20 Apr 2011 16:43:48 +0100, Mike Crowe wrote:
>> With the Perforce command line client "p4" and bash-completion installed if I
>> type:
>> 
>>   p4 edit <TAB>
>> 
>> I get the following error:
>> 
>>   bash: _get_comp_words_by_ref(): `preprev': unknown argument
>> 
>> It appears that this has been fixed in
>> http://git.debian.org/?p=bash-completion/bash-completion.git;a=commitdiff;h=5eead0ebeecf7d3212df3fea9cfe0fa88b6d0274
>> but the fix didn't make it into squeeze.
 
On Wed, Apr 20, 2011 at 06:53:31PM +0200, David Paleino wrote:
> I fear the release team won't accept non-security-uploads to stable.

Ah yes. I thought that the fact that this one file plainly didn't work
at all was sufficient reason for them to accept it but it appears that
the entire package has to be unusable which is clearly not the
case. :(
 
> However, I can try to provide backports, yes. That seems the best thing I
> can do, with current stable update policies. Would that be ok to you?

I have generated my own package for the squeeze version+patch which
should be fine for the time being.

Thanks.

Mike.

Send a report that this bug log contains spam.