Re: [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016
I hope this isn't a stupid question...but can we safely assume that all such google code SRC_URI's have *already* been mirrored? If I understand the mirrors correctly, they serve as a sort of cache of sorts of upstream distfile sources. Is there such a thing as a "cache miss" that could lead to a 404 if the mirrors themselves have to fetch from a dead upstream they've never fetched from before? On Wed, Dec 21, 2016 at 12:54 PM, Andreas K. Huettel wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Am Dienstag, 20. Dezember 2016, 23:57:10 schrieb Jonas Stein: > > > > > The shutdown is in two weeks. > > One can see clearly a drop of broken ebuilds after the first mail on the > > mailinglist and after the personal mail on 2016-11-24. [1] Thank you all > > for fixing so many ebuilds already. > > But still 400 ebuilds use googlecode. > > > > 56 of these do not have a maintainer. > > > > How should we proceed now? > > > > There's absolutely no reason to panic. The Gentoo mirror system preserves > all > distfiles referenced in the Gentoo repository, even if the original source > becomes unavailable. > > It's not nice that the original SRC_URI is gone, it's kind of a QA > violation, > but nothing breaks. > > So let's just keep fixing packages. At some point all will be gone. > > - -- > > Andreas K. Huettel > Gentoo Linux developer > dilfri...@gentoo.org > http://www.akhuettel.de/ > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQKTBAEBCgB9FiEEwo/LD3vtE3qssC2JpEzzc+fumeQFAlha6/NfFIAALgAo > aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMy > OEZDQjBGN0JFRDEzN0FBQ0IwMkQ4OUE0NENGMzczRTdFRTk5RTQACgkQpEzzc+fu > meStkA/+NGss26A4nR1bFTSuQaLuTNC/kqJnf57neEsY3k2Sx1jtA7/sAzWaxps+ > UoG8MrnyTN2yn/H0KyFRb5SpUeW/QMG5kyXoif21A+s2n1TBFslU/dDL9GWI2o/U > Mcv0viJOAtox7rKd7TwwIhYIAGXy4wAwuWgPeSMfYrl7xke/yGl+I2fBbCLkh69+ > /a7GZvu8aYQebiX+gYxmXdoroMZxSXW8sSiCmfyFiOgGf/mydar3jIiH7E2HJwSb > womD2V4vggYUeNv07DJ29Tc7LYGiVNZGatHjLLg1jxn9wyNFmG+s74MXUG1OD0lj > x2/fE1ffbCYnfPpQT96ETU1X2/Ddc4C1RTMyeplbK89ETCUQvoYmSxsU2Y8J6ZvU > ToEmWlZjLlX//KNLcJyAVPZAiYdPO5cR1QG1MPXVTAIhPxIgcQuibct8UgVvHbL6 > rvKExZ0ohCz59Vaks9VDJqN61+jkQix9+TioMBFRmoS07QADcxyEKa7IrhDJzLZA > 4rSxWblr3fdDhnb6TMCZqH2KpMYH4zdM2TbUHtxiKHFz5MsKeijMn3LVdSApNd6W > iyicxYN1jqx11szZSzsvY+DY/KmG3fPnT0Q9zEvwkIjFKVvKYbSG41vHydSCL9aV > qrtLuyECAYYyjdDfIUjqVW/6Zg1zfqe3ahO02fq1GfwOFxYJ86c= > =r5jA > -END PGP SIGNATURE- > >
Re: [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016
Ühel kenal päeval, L, 24.12.2016 kell 02:29, kirjutas Raymond Jennings: > I hope this isn't a stupid question...but can we safely assume that > all such google code SRC_URI's have *already* been mirrored? > > If I understand the mirrors correctly, they serve as a sort of cache > of sorts of upstream distfile sources. Is there such a thing as a > "cache miss" that could lead to a 404 if the mirrors themselves have > to fetch from a dead upstream they've never fetched from before? https://devmanual.gentoo.org/general-concepts/mirrors/
Re: [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016
On 11/04/2016 09:36 PM, Jonas Stein wrote: >>> If you maintain one of these packages, please fix the SRC_URI >>> and HOMEPAGE variables. > >> It would probably be better if the output included the >> maintainer. > > Yes, that is a good idea. > > cat googlecode-shutdown.txt | cut -f1 -d":" | xargs equery meta -mH > | grep "\@" | sort | uniq | sed "s/@/__/g" > > I prefer to protect the list at least by substitution. It will not > help much, but makes me happier ;-) > I've hacked up a portageq-like script [0] to list ebuilds/packages/maintainers for anyone who is interested. [0] https://github.com/gktrk/gentoo-scripts/blob/master/googlecode-uri.py -- gokturk signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016
On 12/24/2016 05:13 PM, Gokturk Yuksek wrote: > On 11/04/2016 09:36 PM, Jonas Stein wrote: If you maintain one of these packages, please fix the SRC_URI and HOMEPAGE variables. >> >>> It would probably be better if the output included the >>> maintainer. >> >> Yes, that is a good idea. >> >> cat googlecode-shutdown.txt | cut -f1 -d":" | xargs equery meta -mH >> | grep "\@" | sort | uniq | sed "s/@/__/g" >> >> I prefer to protect the list at least by substitution. It will not >> help much, but makes me happier ;-) >> > > I've hacked up a portageq-like script [0] to list > ebuilds/packages/maintainers for anyone who is interested. > > [0] https://github.com/gktrk/gentoo-scripts/blob/master/googlecode-uri.py > > -- > gokturk > > Hey, thanks for that script; it helped me find the one package I needed to sort out my gcode stuff. I had a feeling there was at least one I needed to take care of. -- Daniel Campbell - Gentoo Developer OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 signature.asc Description: OpenPGP digital signature
