On 08/18/11 10:50, Diego Elio Pettenò wrote: > Hello everybody, > > I have already said this before, but it looks like nobody cared. We have > a problem for what concerns Gentoo-generated distfiles.
People being quiet doesn't imply they don't care - just that it gets really frustrating to repeat the same thing every week ;) > This includes custom snapshots, custom packages, patches, patchsets, and > so on so forth. While it was infra that (back when I joined at least) > asked not to use dev.gentoo.org for hosting said fails and rather prefer > to use mirror://gentoo/, they already stated that it's not a problem to > do so until we have a proper system in place (system that has been > considered and worked on for quite a bit already and yet is not > available). So - what needs to be done to finally make it happen? > Unfortunately, as long as the mirror://gentoo/ option is still > maintained, we'll end up with situations like today's gnuconfig that > couldn't be fetched, That's not the only one - if you want to recreate a year-old system you'll have trouble finding those patches because the ebuilds were removed and the distfiles removed from the mirrors > causing all ~arch users to see the same failure, > because the distfile wasn't uploaded to the staging area. Of course the > same could happen with a stable SRC_URI, but then it would fail after > hitting that, rather than going through half the gentoo mirrors trying > to find a file that is not there. > > So, anybody has reasons beside laziness, or concern for infra's disk > usage (that argument is allowed to come only from infra members!), to > not go this route? I'll even donate two 2TB disks to kill the disk space argument ;) Hardware is cheap, the maintenance and planning is most likely more of a bottleneck - but then there's enough smart people around if anyone needs help.
