Bug#494158: [grub2] update-grub: uses wrong ordering algorithm (sorts 1.2.3-foo before 1.2.3.1-foo)

[Felix Zielcke]

I really should have sticked with my easy debugging method I already
mentioned in the report (that echo >> /tmp/x thingy)
I thought removing the greedy g on the regexps would just solve the
problem for us, but it doestn't:

fz:/etc/grub.d# dpkg --compare-versions 2.6.26-1-amd64~rc1-git1 gt 2.6.26-1-amd64; echo $?
0
fz:/etc/grub.d# dpkg --compare-versions 2.6.26-1-amd64~rc1~git1 gt 2.6.26-1-amd64; echo $?
1

This looks for me more then a dpkg issue.
~x-y should be like ~x~y i.e. that the above one returns the same.

Maybe I just think again too difficult.
There's no need to solve this problem with just one regexp on the 2 versions supplied
and then comparing these 2 with just one dpkg call.

About these --mm kernels:
(probable more for Robert)

I forgot we probable should ignore them, i.e. have them above the normal ones as right now

2.6.26-mm1 is higher/newer then 2.6.26
-mm patches contain the things which should go into the next kernel releases.
But there's again this double problem i.e. -rc1-mm1:

Found linux image: /boot/vmlinuz-2.6.26-1-amd64-mm1
Found linux image: /boot/vmlinuz-2.6.26-1-amd64-rc1-mm1
Found linux image: /boot/vmlinuz-2.6.26-1-amd64