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.
>>
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
Ü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
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
-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
>
On Tue, 20 Dec 2016 23:57:10 +0100
Jonas Stein wrote:
> 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
Jonas Stein:
> On 2016-11-05 08:47, Michał Górny wrote:
>> Thou shalt not rely on the mirrors! Though mirrors as a temporary
>> solution are acceptable. As long as you don't turn it into 'wrong
>> SRC_URI is fine, the file is on the mirrors'.
>
>> Also, it would be nice not to have the berlios ->
On 2016-11-05 08:47, Michał Górny wrote:
> Thou shalt not rely on the mirrors! Though mirrors as a temporary
> solution are acceptable. As long as you don't turn it into 'wrong
> SRC_URI is fine, the file is on the mirrors'.
> Also, it would be nice not to have the berlios -> sourceforge crap
> re
>> Today we have still 524 ebuilds with SRC_URI=*googlecode* in the tree
>> [2] and should get these fixed before end of 2016.
>
> Thanks!
>
> I suggest adding repoman check for those ebuilds
> if it does not already exist. It will allow users spot
> ticking bombs in their overlays.
Sergei, than
On Sat, Nov 05, 2016 at 05:45:06PM +1300, Kent Fredric wrote:
> dev-python/google-api-python-client-1.1: robbat2gentoo.org
> net-nds/nsscache-0.23*: robbat2gentoo.org
Old ebuilds removed.
> dev-vcs/git-2*: robbat2gentoo.org polynomial-cgentoo.org
gcode was already a backup to the other SRC_URI,
On Sat, 5 Nov 2016 00:54:25 +0100
Jonas Stein wrote:
> Dear all,
>
> Google announced in 2015 to close the "Google Code" repositories [1].
>
> They will provide the repositories in read only state till end of 2016.
>
> Today we have still 524 ebuilds with SRC_URI=*googlecode* in the tree
> [2]
On Sat, 5 Nov 2016 08:38:22 +0100
"Paweł Hajdan, Jr." wrote:
> On 05/11/2016 00:54, Jonas Stein wrote:
> > Today we have still 524 ebuilds with SRC_URI=*googlecode* in the tree
> > [2] and should get these fixed before end of 2016.
> >
> > [3] https://wiki.gentoo.org/wiki/Shutdown_of_google_code
On 05/11/2016 00:54, Jonas Stein wrote:
> Today we have still 524 ebuilds with SRC_URI=*googlecode* in the tree
> [2] and should get these fixed before end of 2016.
>
> [3] https://wiki.gentoo.org/wiki/Shutdown_of_google_code
The wiki page seems to indicate some sense of urgency. I'm not sure how
On 05/11/16 04:45, Kent Fredric wrote:
> On Fri, 4 Nov 2016 23:09:07 -0400
> Mike Gilbert wrote:
>
>> On Fri, Nov 4, 2016 at 9:36 PM, Jonas Stein wrote:
>> [...]
>>>
>> [...]
>>> Yes, that is a good idea.
>>>
>>> cat googlecode-shutdown.txt | cut -f1 -d":" | xargs equery meta -mH |
>>> gr
On Fri, 4 Nov 2016 23:09:07 -0400
Mike Gilbert wrote:
> On Fri, Nov 4, 2016 at 9:36 PM, Jonas Stein wrote:
> [...]
> >
> [...]
> >
> > Yes, that is a good idea.
> >
> > cat googlecode-shutdown.txt | cut -f1 -d":" | xargs equery meta -mH |
> > grep "\@" | sort | uniq | sed "s/@/__/g"
> >
On Fri, Nov 4, 2016 at 9: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":" | x
>> 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
On 05/11/16 01:20, Rich Freeman wrote:
> On Fri, Nov 4, 2016 at 8:30 PM, M. J. Everitt wrote:
>> Apologies, getting ahead of myself here .. there must be a portage
>> utility, but I've forgotten which one interrogates metadata .. I'll
>> defer to a more authoritative source ...
>>
> There might be
> Apologies, getting ahead of myself here .. there must be a portage
> utility, but I've forgotten which one interrogates metadata .. I'll
> defer to a more authoritative source ...
You can try to fetch the maintainers per package with
equery meta -mH foo/bar
Best,
--
Jonas
On Fri, Nov 4, 2016 at 8:30 PM, M. J. Everitt wrote:
> Apologies, getting ahead of myself here .. there must be a portage
> utility, but I've forgotten which one interrogates metadata .. I'll
> defer to a more authoritative source ...
>
There might be a command line utility if you're doing things
On 05/11/16 00:23, M. J. Everitt wrote:
> On 05/11/16 00:20, Rich Freeman wrote:
>> On Fri, Nov 4, 2016 at 7:54 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 maintai
On 05/11/16 00:20, Rich Freeman wrote:
> On Fri, Nov 4, 2016 at 7:54 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.
> Hopefully this isn't using anything depr
On Fri, Nov 4, 2016 at 7:54 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.
Hopefully this isn't using anything deprecated, but you should be able
to steal from
Dear all,
Google announced in 2015 to close the "Google Code" repositories [1].
They will provide the repositories in read only state till end of 2016.
Today we have still 524 ebuilds with SRC_URI=*googlecode* in the tree
[2] and should get these fixed before end of 2016.
If you maintain one of
24 matches
Mail list logo
