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.
Cesar
* 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/o
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
m
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 machi
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.
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 pu
6 matches
Mail list logo
