Summary: | Errors in dynamically generated package list | ||
---|---|---|---|
Product: | Gentoo Infrastructure | Reporter: | webmaster |
Component: | [OLD] gpackages | Assignee: | Lance Albertson (RETIRED) <ramereth> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | blackace |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.gentoo.org/dyn/gentoo_pkglist_X86.txt | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
webmaster
2004-02-16 11:31:08 UTC
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... |