[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#527200: marked as done (apt-key fails if GREP_OPTIONS isn't defined)



Your message dated Thu, 07 May 2009 19:08:47 +0100
with message-id <1241719727.16566.93.camel@kaa.jungle.aubergine.my-net-space.net>
and subject line Re: Bug#527200: apt-key fails if GREP_OPTIONS isn't defined
has caused the Debian Bug report #527200,
regarding apt-key fails if GREP_OPTIONS isn't defined
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 owner@bugs.debian.org
immediately.)


-- 
527200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527200
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 0.7.20.2+lenny1
Severity: important

Hi!

apt-key fails if GREP_OPTIONS is not defined. The guilty lines are:

set -e
unset GREP_OPTIONS

and, if apt-key fails, updating apt fails too (it's called on postinst)

way to reproduce it:

$ unset GREP_OPTIONS;apt-key update || echo fails
fails
$ GREP_OPTIONS=a apt-key update || echo fails
(it works)

I think that changing the order of that lines to:

unset GREP_OPTIONS
set -e

should fix the problem.

Thanks!
Horacio J. Peña



--- End Message ---
--- Begin Message ---
On Wed, 2009-05-06 at 19:25 -0300, Horacio J.Peña wrote:
> Hola!
> 
> > Which shell are you using? I can't reproduce this, and SuSv3 makes it
> > clear that the above should not occur:
> 
> ii  bash       2.05a-11	The GNU Bourne Again SHell
> 
> $ sh --version
> GNU bash, version 2.05a.0(1)-release (i386-pc-linux-gnu)
> Copyright 2001 Free Software Foundation, Inc.
> $ unset A || echo buh
> buh
> 
> Well, it seems i'm using a too old version of bash. I've checked on
> another machine and it works as you said.
> 
> Please close the bug.

Thanks; doing so with this message.

Regards,

Adam


--- End Message ---

Reply to: