Summary: | dev-python/pyxdg-0.20_rc1 unfetchable | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tman <cornicx> |
Component: | New packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | marienz, qa |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | /var/log/portage/dev-python:pyxdg-0.20_rc1:20120620-153153.log |
Description
tman
2012-06-20 13:36:06 UTC
Created attachment 315855 [details]
/var/log/portage/dev-python:pyxdg-0.20_rc1:20120620-153153.log
This original issue was "fixed" by using the gentoo mirrors — but the mirrors never actually fetched the file because the md5 never matched. Can somebody please put this in _their devspace_ so that we don't lose it the moment the ebuild is removed from the tree? I renamed the tarball and put it in /space/distfiles-local before adjusting the ebuild. I've put another copy of it in my devspace to make sure we don't lose it accidentally. I'd expect the mirror system to take care of things from here on: please explain what's still broken once pyxdg-0.20_rc1-snapshot.tar.gz has actually mirrored out. It's just that it hasn't hit the mirrors yet and since you only added mirror://gentoo/ we had an ebuild that was still unfixed. I've said this to gentoo-dev before as well: relying solely on mirror://gentoo/ is not a good idea, just put it onto http://dev.gentoo.org/~marienz/ and let the mirroring take care of it, and use that as SRC_URI for this kind of stuff. Looks like my memory of acceptable use of dev.g.o for this kind of thing was a few years out of date. I've updated SRC_URI, and I'll just use that right away in the future. FWIW infra used not to accept this use, but when it was clear that the distarchive was years overdue and still to come, we agreed on allowing this and dealing with an eventual fallout when we reach critical. I could have fixed this since I've caused it but I was never CCd in the bug, instead qa@ was -- how silly is that? :-) Samuli I thought you were in python@. And for the rest of qa@ I am using the alias for those bugs I want to keep an eye upon, but don't want mixed with the one I'm filing with the tinderbox, sorry. |