Comment 17 for bug 27912

Revision history for this message
In , Sven Luther (sven-luther) wrote : Re: This bug should be fixed with both 2.6.14-7 and upcoming 2.6.15-1, ...

On Tue, Jan 03, 2006 at 10:35:08PM -0500, Jean-Marc Ranger wrote:
> 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.

Cool, closing this bug report then.

> (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.)

well, this is a tricky issue, and needs some playing with the installation
scripts, which can be found in both /var/lib/dpkg/info/<package>.* and
/etc/kernel/* for the kernel packages. Thos scripts may do important things,
or they may not, so just putting an exit 0 at the start of them may be a
solution or it may not, you would need to look at the individual scripts to
decide, especially since it may hose the system in a worse manner if not done
right.

Another trick is copying over the scripts that fail from an older or newer
version of the package.

In any case, it has to be a cautious and informed process, and i believe this
kind of bugs are the worse.

Friendly,

Sven Luther