Message-ID: <email address hidden>
Message-ID: <email address hidden>
Date: Tue, 03 Jan 2006 22:35:08 -0500
From: Jean-Marc Ranger <email address hidden>
To: Sven Luther <email address hidden>
CC: <email address hidden>
Subject: Re: This bug should be fixed with both 2.6.14-7 and upcoming 2.6.15-1,
...
Sven Luther wrote:
> Can you please confirm that this issue should be closed, so that we
> can close the bug report ?
Hi Sven,
Confirmed. No longer visible on my side.
However, I can't confirm what exactly fixed it, but in the last days
before Christmas IIRC, 2.6.14-5 finally purged correctly.
Just upgraded today from 2.6.14-6 to -7 without problem.
(I'd still be interessed in hints on how to recover from this kind of
problem, and/or hints on how to rollback to prior version of a package,
but this is now way off-topic.)
Message-ID: <email address hidden>
Message-ID: <email address hidden>
Date: Tue, 03 Jan 2006 22:35:08 -0500
From: Jean-Marc Ranger <email address hidden>
To: Sven Luther <email address hidden>
CC: <email address hidden>
Subject: Re: This bug should be fixed with both 2.6.14-7 and upcoming 2.6.15-1,
...
Sven Luther wrote:
> Can you please confirm that this issue should be closed, so that we
> can close the bug report ?
Hi Sven,
Confirmed. No longer visible on my side.
However, I can't confirm what exactly fixed it, but in the last days
before Christmas IIRC, 2.6.14-5 finally purged correctly.
Just upgraded today from 2.6.14-6 to -7 without problem.
(I'd still be interessed in hints on how to recover from this kind of
problem, and/or hints on how to rollback to prior version of a package,
but this is now way off-topic.)
Jean-Marc