While emerging xcdroast-0.98_alpha15-r3 it can't download xcdroast-0.98_alpha15_new_configure.tar.gz from anywhere Reproducible: Always Steps to Reproduce: 1.emerge xcdroast Actual Results: Download xcdroast-0.98alpha15.tar.gz correctly. Try to get xcdroast-0.98_alpha15_new_configure.tar.gz from diferent portage mirrors, but it seems doesn't exists.
Created attachment 64459 [details] output about the bug Output of the command: emerge xcdroast
Right. Somehow the file is missing. I'm investigating...
Yes, I'm seeing this also. Thanks for looking at it. dragonfly ~ # emerge xcdroast Calculating dependencies ...done! >>> emerge (1 of 1) app-cdr/xcdroast-0.98_alpha15-r3 to / >>> Downloading ftp://gentoo.mirrored.ca/distfiles/xcdroast-0.98_alpha15_new_configure.tar.gz --06:59:51-- ftp://gentoo.mirrored.ca/distfiles/xcdroast-0.98_alpha15_new_configure.tar.gz => `/usr/portage/distfiles/xcdroast-0.98_alpha15_new_configure.tar.gz' Resolving gentoo.mirrored.ca... 142.77.49.225 Connecting to gentoo.mirrored.ca[142.77.49.225]:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /distfiles ... done. ==> PASV ... done. ==> RETR xcdroast-0.98_alpha15_new_configure.tar.gz ... No such file `xcdroast-0.98_alpha15_new_configure.tar.gz'.
the file is available at the following dist mirror: http://gentoo.mirror.sdv.fr/distfiles/xcdroast-0.98_alpha15_new_configure.tar.gz
I notice that http://distfiles.gentoo.org still don't have xcdroast-0.98_alpha15_new_configure.tar.gz . Lars maybe we should place again the file in the mirrors.
Although I still don't know the source of this disappearing, I re-added it to the distfiles in the hope it will be available soon.
*** Bug 104880 has been marked as a duplicate of this bug. ***
*** Bug 105491 has been marked as a duplicate of this bug. ***
Reopened, the file is still/again MIA. CCing mirror-admin as well.
lance, is the distfiles grabber script not working?
the more the marrier. brian, any ideas on if the script isnt working?
Ok, this is what I see... In the ebuild, its set to nomirror, which means it shouldn't be put on our mirrors. On osprey, the logs state: general.log:app-cdr/xcdroast-0.98_alpha15-r3: skipping, fetch restriction Brian will have to explain how that works, but I'm thinking that since its set nomirror in the ebuild, the mirror-dist script deletes it.
mirror-dist does cleansing... the file in question, since it's marked as nomirror, means it shouldn't be on our mirrors (moreso portage downloads from src_uri rather then mirror). So... going by the ebuild's restrict, it doesn't belong on the mirror, so mirror-dist waxes it after a set period of time.
optical media herd, it's your move... this isn't an infra issue, the scripts in question are doing what the ebuild requests, so y'all need to yay/nay why the ebuild has the restriction.
ok Restriction removed from the ebuild now it should work fine. Reopen if something goes wrong.
