Re: [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016

2016-12-24 Thread Daniel Campbell
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. >>

Re: [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016

2016-12-24 Thread Gokturk Yuksek
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":" | xarg

Re: [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016

2016-12-24 Thread Mart Raudsepp
Ü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 upstre

Re: [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016

2016-12-24 Thread 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