The page says that it was recently generated, but there are packages in MDV 2010.2/updates, some relatively new (for example, icedtea-web) and some very old (for example, libglpng), that are older in Mageia 1 and not reflected on that page. It is possible that the script that generates this page just isn't looking in 2010.2's updates at all, but I am not certain that is the issue.
Upon further examination and discussion on IRC, the contents of this page are total nonsense. Furthermore, I checked by hand for all of the packages that are newer in MDV 2010.2 than in Mageia 1 and reported bugs on all of them, so we do not need this page anymore.
There have been some improvements to the page, but there are still issues. 1) Some packages are still missing. Ex: tolua++ (Bug 4341), mozilla-thunderbird (Bug 4512), firefox (Bug 4405) 2) Some packages listed there shouldn't be, because the script isn't checking epochs. Ex: bash-completion, castor, gnome-js-common, mondo, perl-Net-Netmask, perl-XML-RSS-LibXML, qimageblitz, task-xfce 3) Some packages listed there shouldn't be, because we *have* provided updates for them. Ex: clamav, networkmanager-pptp, icedtea-web, phpmyadmin
CC: (none) => pterjan
URL: http://check.mageia.org/updates_mandriva_2010_2.html => http://check.mageia.org/1/updates_mandriva_2010_2.html
For 2), yes the ones with known epoch had been added to the config file as exceptions. There is no plan to support epoch (or release) as this is using the "Updates" code which was designed to compare versions with upstream. For 3), I don't know how to fix it with current code either. There is a higher version. We also have another package in another media with a higher version but there is no way to know it when we are analysing release. Maybe we should just drop this (which was a hack before releasing 1) and write some dedicated code.
(In reply to comment #3) > For 2), yes the ones with known epoch had been added to the config file as > exceptions. There is no plan to support epoch (or release) as this is using the > "Updates" code which was designed to compare versions with upstream. Yes, I figured you would say that. Checking epochs would only make sense for this page, and not others whose main concern is looking for newer *software* versions in other distros, rather than package versions. So this one is no big deal. > For 3), I don't know how to fix it with current code either. There is a higher > version. We also have another package in another media with a higher version > but there is no way to know it when we are analysing release. Sorry, I don't follow... > Maybe we should just drop this (which was a hack before releasing 1) and write > some dedicated code. Well this whole page could be dropped, as I mentioned in Comment 1. I had already checked MDV 2010.2 by hand (although I had missed avalon-framework and jsr-305 that were newer in 2010.1/release than mga1, rather than updates) and filed bug reports for everything that was newer in MDV, and I continue to monitor that.
No longer important now that Mageia 1 is EOL.
Status: NEW => RESOLVEDResolution: (none) => OLD