On Tue, Nov 08, 2005 at 11:37:48AM -0500, Cyber Dog wrote: > On 11/8/05, Alberto Gonzalez Iniesta <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 08, 2005 at 10:56:02AM -0500, Cyber Dog wrote: > > > There is a simple fix for this: > > > > > > > This problem has long been fixed and it's only present in Sarge. > > The solucion was using rm -rf to delete the status file. > > I'll try to get the fix in sarge's next point release. > > > > > > > > -- > > Alberto Gonzalez Iniesta | Formación, consultoría y soporte técnico > > agi@(inittab.org|debian.org)| en GNU/Linux y software libre > > Encrypted mail preferred | http://inittab.com > > > > Key fingerprint = 9782 04E7 2B75 405C F5E9 0C81 C514 AF8E 4BA4 01C3 > > > > Thanks, you can ignore my last email then. The bug tracker still > shows the bug as open so I didn't know. > > I should point out this seems to be a big problem now, because apt-get > is trying to call cond-restart with the recent security releases, only > the update fails due to the restart function failing.
I know, that's why 'I'll try to get the fix in sarge's next point release.' We weren't lucky with this bug. -- Alberto Gonzalez Iniesta | Formación, consultoría y soporte técnico agi@(inittab.org|debian.org)| en GNU/Linux y software libre Encrypted mail preferred | http://inittab.com Key fingerprint = 9782 04E7 2B75 405C F5E9 0C81 C514 AF8E 4BA4 01C3
