The distfiles used by the tree on the last release medium should be available on the mirrors, and relevant ebuilds should also probably stay in the current portage tree as well. What brought this up specifically was gentoo-sources-2.6.17 being removed from portage -- someone who performs LiveCD (networkless) install would be unable to emerge gentoo-sources to tweak their kernel, without doing a --sync (which means upgrading the whole system),because gentoo-sources-2.6.17-r5 (specifically the patch tarball) is no longer available on the mirrors. (ref: bug 155798, bug 156836#5) [note, keeping the distfiles for the current stable gentoo-sources on the LiveCD media would solve this particular issue too, however it seems the release team is unwilling to do that -- ref: bug 169159] Similar issues may also present themselves for other packages that need to be rebuilt, especially when a --sync and world-update are not (yet) feasible.. I'm wondering if this might be a cause for failures of non-networkless GLI installs? A quick discussion in #gentoo-userrel mentioned that the functionality for whitelisting distfiles on the mirrors is already there, and doing this would fix the issue.
Infra: Do we have some easier way to do the whitelisting? I surely don't want to have to locate and whitelist thousands of distfiles manually each release.
wolf31o2: how about using the metadata/ from your portage snapshot to generate your additions to the whitelist? make a file named whitelist-2007.0, and then we can get that into the distfiles mirroring process? that would also provide good seperation as to why the distfiles in question are whitelisted.
I'm fine with that. Is there a simple method of using the metadata that you're already aware of before I go investigating?
Created attachment 115397 [details] list distfiles for latest stable versions This script will list distfiles for the latest stable versions in all slots. It will take a list of keywords on the command line (or use those listed in arch.list if none are given). This doesn't pay any attention to profiles or package.mask, it only looks at keywords. That's probably a good approximation for what you want though.
Created attachment 115399 [details] list distfiles for latest stable versions (bug fix)
wolf31o2: do you have a generated whitelist file I can put into place?
Not at this time. I was going to generate one, but haven't had the time. The actual portage tree made to make the snapshot for the release exists on poseidon at /release/portage-official, if you can run it. Otherwise, I'll have to generate it when I find some time.
I have the script running to generate them for 200{6.{0,1},7.0} now, and I'll stick those whitelists up to start. When 2008.0 is close to ready, we need to run it again to generate a whitelist for that.
Ok, the 2007.0 ones are whitelisted now.
zmedico: just wondering about trimming the list down some. rather than printing every single distfile, can we trim it down and only print the distfile if the ebuild is stable on ANY arch (so exclude distfiles where the ebuild is unstable only).
Final version at this URL: http://dev.gentoo.org/~zmedico/portage/branches/2.2/bin/distfiles-whitelist.py 2008.0 whitelist is in place now.
