Bug#568317: linux-image-* postinst did not correctly run lilo

To: 568317@bugs.debian.org, max@stro.at
Cc: ben@decadent.org.uk
Subject: Bug#568317: linux-image-* postinst did not correctly run lilo
From: paul.szabo@sydney.edu.au
Date: Mon, 8 Feb 2010 09:01:01 +1100
Message-id: <201002072201.o17M11Re029348@bari.maths.usyd.edu.au>
Reply-to: paul.szabo@sydney.edu.au, 568317@bugs.debian.org
In-reply-to: <20100207214113.GR9624@baikonur.stro.at>

Dear Maks,

> ... saw your old patch and can do that later tomorrow.

Thanks. Please also fix current Debian stable, do not make us wait until
2.6.32 trickles down.

>> Should this bug somehow be "given" to kernel-package also (clone and
>> reassign?): would you be able to do that?
> don't know kernel-package is in slow maintenance,

What does "slow maintenance" mean? They seem more up-to-date that
linux-2.6 in Debian stable. Anyway please arrange for kernel-package to
be fixed also.

Cheers, Paul

Paul Szabo   psz@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of Sydney    Australia

Reply to:

Follow-Ups:
- Bug#568317: linux-image-* postinst did not correctly run lilo
  - From: Ben Hutchings <ben@decadent.org.uk>

References:
- Bug#568317: linux-image-* postinst did not correctly run lilo
  - From: maximilian attems <max@stro.at>

Prev by Date: Bug#564114: marked as done (e1000: Potential packet filtering bypass)
Next by Date: Processed: reassign 568679 to src:linux-2.6, forcibly merging 568416 568679
Previous by thread: Bug#568317: linux-image-* postinst did not correctly run lilo
Next by thread: Bug#568317: linux-image-* postinst did not correctly run lilo
Index(es):
- Date
- Thread