There are errors in the dynamically generated package list: http://www.gentoo.org/dyn/gentoo_pkglist_X86.txt Problem is some packages, in particular apache, are not current. Here is the apache entry in gentoo_pkglist_X86.txt: apache 1.3.29 net-www/apache-1.3.29-r1 Apache 2.0.48-r1 is correctly returned as latest package when using the web-based online package database. http://packages.gentoo.org/packages/?category=net-www;name=apache This package list is used by sites like DistroWatch and is causing a lot of complaints at those websites. Reproducible: Always Steps to Reproduce: 1. Search for apache in http://www.gentoo.org/dyn/gentoo_pkglist_X86.txt 2. Compare to online package database at http://packages.gentoo.org/packages/?category=net-www;name=apache 3. Observe they are not synchronized. Actual Results: One list claims apache 1.3.29 is latest, the other claims 2.0.48-r1 is latest. The web-based online package database is correct.
Neysx: same help on this one too :)
Back to you, Lance. I know absolutely nothing of the portage api that is used to generate that list. It looks very trivial for someone from the portage team.
Where is the code for this (please say it's not Perl!)
In cvs and no, it's python, but what it is doing is a bestmatch-visible, so in my estimation this is not a bug, it is the fact that the www nodes don't have apache2 in USE and packages.g.o does. To generate a consistent list we would have to concur on a set of USE flags and other settings to use to fake an environment for both that script and packages.g.o's script to run in. Up to you where we go from here Lance, sorry I forgot about this bug completely, thanks for the reminder marduk.
Is this bug even remotely relevant after 2 1/2 years?
Zzzzzzz...
