On 19 Jan 2009, at 23:50, Martin wrote:
IIRC this is because some of the repository signing keys have expired.
If you check back throught the archives you will find a load of posts
about this from when it first became a problem. The answer is to
I couldn't remember the error message off-hand,
On Mon, 2009-01-19 at 22:16 +, gavin duley wrote:
> On 17 Jan 2009, at 22:37, Chris Andrew wrote:
>
> > Hi, all.
> >
> > I'm trying to do a dist-upgrade from sarge to etch on my SS20. Sadly,
> > I am getting a gpg error when apt and other apt utilities try to
> > configure. Does anyone know
On 17 Jan 2009, at 22:37, Chris Andrew wrote:
Hi, all.
I'm trying to do a dist-upgrade from sarge to etch on my SS20. Sadly,
I am getting a gpg error when apt and other apt utilities try to
configure. Does anyone know how I can overcome this?
I'm not a Debian developer, but: I've had a simi
Hi, all.
I'm trying to do a dist-upgrade from sarge to etch on my SS20. Sadly,
I am getting a gpg error when apt and other apt utilities try to
configure. Does anyone know how I can overcome this?
Installing something may be a problem, so it would be better if I
could apt-get and force the syst
4 matches
Mail list logo
