Bug#493389: update-grub: uses wrong ordering algorithm (sorts 1.2.3-foo before 1.2.3.1-foo)

[Robert Millan]

severity 493389 wishlist
tag 493389 wontfix
thanks

On Sun, Aug 03, 2008 at 01:37:07PM +0300, Teodor wrote:
> On Sun, Aug 3, 2008 at 12:43 AM, Robert Millan <rmh at aybabtu.com> wrote:
> > Please could you try previous versions of update-grub (using either our SVN
> > or packages from http://snapshot.debian.net/) and determine when was this
> > problem introduced?
> 
> The change seems to be introduced in v0.97-29 since up to v0.97-28 has
> the same ordering.
> I've written "change" not "bug" since I'm not sure it is a problem.
> That is because `update-grub' is supposed to create a list with a
> descending ordering. This means that there is a "char" comparison and
> the one with a higher value should go first, for example -openvz-amd64
> would go before -amd64 ('a' char vs 'o' char). The same way
> -2.6.26-1-amd64 has precedence over -2.6.25-2-amd64 (25 vs 26).

Thanks Teodor.  This seems to come from #422759, which didn't make it to etch.
That explains why people are surprised about the change.

I'm tagging this bug wontfix unless someone can convince me otherwise.

For now I'd like to keep it open untill after the lenny release, since (I
expect) a number of users might run into this during the lenny upgrade.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."