|
Home > Archive > Debian Developers > January 2006 > How to purge linux-image-2.6.14
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
How to purge linux-image-2.6.14
|
|
| Cesare Leonardi 2006-01-29, 9:38 pm |
| Hi all.
I would ask a question i've already posted in the #344767 bug report.
Recently i've talked with someone else that cannot purge the 2.6.14
kernel, due to bug #344767. It's a known problem, already solved for
2.6.15, but for people that still use 2.6.14 or have used it, the
problem of purging it completely still exist.
For example on my machine, the various kernel images i've installed in
the past, are now uninstalled but marked as "c" and if i try to purge
them, the lock described in the bug report arise. Then i have to press
CTRL+C to exit.
After upgrading to 2.6.15 and have seen that the bug was corrected,
i've forgotten about this and the not clean (but innocuous) situation
left by the 2.6.14 uninstall procedure. And so now i am curious to know
it there is an hack to circumvent the bug and completely purge the
linux-image-2.6.14 packages.
It's my intention to put one or more responses into the bug report, to
help the others that will fall in this bug.
As suggested in the bug report, i've tryed to look at the postrm scripts
in "/var/lib/dpkg/info/" but i cannot understand them adequately (i
don't know perl).
Regards.
Cesare.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Edward Shornock 2006-01-29, 9:38 pm |
| On Thu, Jan 26, 2006 at 02:53:57AM +0100, Cesare Leonardi wrote:
> Hi all.
> I would ask a question i've already posted in the #344767 bug report.
>
> Recently i've talked with someone else that cannot purge the 2.6.14
> kernel, due to bug #344767. It's a known problem, already solved for
> 2.6.15, but for people that still use 2.6.14 or have used it, the
> problem of purging it completely still exist.
> For example on my machine, the various kernel images i've installed in
> the past, are now uninstalled but marked as "c" and if i try to purge
> them, the lock described in the bug report arise. Then i have to press
> CTRL+C to exit.
> After upgrading to 2.6.15 and have seen that the bug was corrected,
> i've forgotten about this and the not clean (but innocuous) situation
> left by the 2.6.14 uninstall procedure. And so now i am curious to know
> it there is an hack to circumvent the bug and completely purge the
> linux-image-2.6.14 packages.
> It's my intention to put one or more responses into the bug report, to
> help the others that will fall in this bug.
>
> As suggested in the bug report, i've tryed to look at the postrm scripts
> in "/var/lib/dpkg/info/" but i cannot understand them adequately (i
> don't know perl).
I don't know PERL either, but maybe this would work (try at your own
risk though):
1) edit /var/lib/dpkg/info/linux-image-2.6.14-*.postrm
2) Search for do_bootloader in the file. Change any of the YES's to
NO's.
3) Try to purge the package.
4) run update-grub.
I've not tried this so I don't know if this will even fix the problem
but it *might* work.
| |
| Sam Morris 2006-01-29, 9:38 pm |
| Cesare Leonardi wrote:
> Recently i've talked with someone else that cannot purge the 2.6.14
> kernel, due to bug #344767. It's a known problem, already solved for
> 2.6.15, but for people that still use 2.6.14 or have used it, the
> problem of purging it completely still exist.
> For example on my machine, the various kernel images i've installed in
> the past, are now uninstalled but marked as "c" and if i try to purge
> them, the lock described in the bug report arise. Then i have to press
> CTRL+C to exit.
>
> [snip]
>
> As suggested in the bug report, i've tryed to look at the postrm scripts
> in "/var/lib/dpkg/info/" but i cannot understand them adequately (i
> don't know perl).
You need to edit "/var/lib/dpkg/info/linux-image-2.6.14-2-k7.postrm".
Comment out line 268, which reads: "$ret = stop ();". Then purge the
package.
> Regards.
>
> Cesare.
PS - why do packages without any config files get into the config-files
state in the first place? 
--
Sam Morris
http://robots.org.uk/
PGP key id 5EA01078
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Anthony DeRobertis 2006-01-29, 9:38 pm |
| Sam Morris wrote:
> PS - why do packages without any config files get into the config-files
> state in the first place?
Possibly, because dpkg can only know if a package has conffiles, and not
configuration files in general?
Look up the details in policy, but not all configuration files are
managed by dpkg. Packages may manage their own (using, e.g., ucf) as
long as they follow the rules laid out by policy.
BTW: I think sometimes packages do go strait from installed to purged on
just remove... Not 100% sure if it even happens, but maybe its if there
is no postrm script and no conffiles.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Adeodato Simó 2006-01-29, 9:38 pm |
| * Anthony DeRobertis [Thu, 26 Jan 2006 08:51:06 -0500]:
> BTW: I think sometimes packages do go strait from installed to purged on
> just remove... Not 100% sure if it even happens, but maybe its if there
> is no postrm script and no conffiles.
Yes. From policy:
6.7. Details of removal and/or configuration purging
----------------------------------------------------
[...]
3. <postrm> remove
4. All the maintainer scripts except the `postrm' are removed.
If we aren't purging the package we stop here. Note that
packages which have no `postrm' and no `conffile's are
automatically purged when removed, as there is no difference
except for the `dpkg' status.
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
There may be no I in TEAM, but a M and an E.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Cesare Leonardi 2006-01-29, 9:38 pm |
| Sam Morris wrote:
> You need to edit "/var/lib/dpkg/info/linux-image-2.6.14-2-k7.postrm".
> Comment out line 268, which reads: "$ret = stop ();". Then purge the
> package.
Thank you very much for the precise information: it works.
And thanks also to have CC'ed your reply to #344767.
Regards.
Cesare.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|