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

[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.
>>
>> 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

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

[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":" | 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

[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 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

[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?

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

[Andreas K. Huettel]

-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

[Kent Fredric]

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 use googlecode.

Double checking here, but surely, packages which have newer google code versions
don't need the old versions killed prematurely.

For instance, dev-perl/Google-Ads-AdWords-Client had[1] version 2.xxx from 
GoogleCode,
but has a version 4.xxx now from CPAN/Github.

I don't think I *need* to kill the 2.xxx version, and I'm no hurry to force
everyone who was using 2.xxx to make a radical major version shift and break 
their
code.

So I think as long as: 

1. No mirror restrictions
2. Its mirrored
3. There is a clear succession away from google code in newer versions.

We're not harming anyone by keeping old versions from googlecode.

So:

> But still 400 ebuilds use googlecode.

There may be significantly less here to worry about.


1: When writing this email I realised they might have mirrored a SHA-identical 
version
  of the old 2.xxx series to CPAN, and lo and behold, they did!, so this email 
now becomes
  a purely theoretical exercise :)


pgp1QOurDz6Za.pgp
Description: OpenPGP digital signature

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

[Gokturk Yuksek]

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 -> sourceforge crap
>> repeated. If software is dead-dead, we should lastrite it or revive it,
>> not point to some dead copy by malware hosting provider.
> 
> 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.
> 

I think it's misleading to do the calculation based on ebuilds. It's 293
packages.

> 56 of these do not have a maintainer.
> 

Likewise 39 packages with a total of 54 ebuilds.

> How should we proceed now?
> 
> Should we lastrite all unmaintained packages and generate bugtickets for
> the maintained ebuilds?
> 

I'll take a look at maintainer-needed and see if I can update some of them.

> Who has experience with automatic generation of bugtickets and could
> write a script for this? The tickets should block the main ticket [2].
> 
> 
> [1] http://www.akhuettel.de/~huettel/plots/googlecode.php
> [2] https://bugs.gentoo.org/show_bug.cgi?id=544092
> 




signature.asc
Description: OpenPGP digital signature

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

[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 -> sourceforge crap
> repeated. If software is dead-dead, we should lastrite it or revive it,
> not point to some dead copy by malware hosting provider.

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?

Should we lastrite all unmaintained packages and generate bugtickets for
the maintained ebuilds?

Who has experience with automatic generation of bugtickets and could
write a script for this? The tickets should block the main ticket [2].


[1] http://www.akhuettel.de/~huettel/plots/googlecode.php
[2] https://bugs.gentoo.org/show_bug.cgi?id=544092

-- 
Best,
Jonas

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

[Jonas Stein]

>> 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, thank you for your suggestion.
It is part of the worklist [1] and has a ticket [2] now.

[1] https://wiki.gentoo.org/wiki/Shutdown_of_google_code#Worklist
[2] https://bugs.gentoo.org/show_bug.cgi?id=601476

Best,
Jonas

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

[Robin H. Johnson]

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, but is removed now
anyway.

> dev-util/rats-2.3: robbat2gentoo.org 
I emailed the original upstream to see about it.

> net-misc/memcached-1.2.8-r1: robbat2gentoo.org 
> prometheanfiregentoo.org 
> net-misc/memcached-1.3.3-r5: robbat2gentoo.org 
> prometheanfiregentoo.org 
Upstream contacted.

-- 
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Trustee & Treasurer
E-Mail   : robb...@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136


signature.asc
Description: Digital signature

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

[Sergei Trofimovich]

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] 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


pgpch6caZPdKz.pgp
Description: Цифровая подпись OpenPGP

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

[Michał Górny]

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  
> 
> The wiki page seems to indicate some sense of urgency. I'm not sure how
> much of that is needed.
> 
> Brainstorming mentions just cloning the URLs, but don't existing Gentoo
> Mirrors have the same effect? My understanding is fetching will not
> break even if original URLs go down.

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'.

> I'm also not fully convinced by the manpower argument. It seems the same
> work needs to be done, one way or another.
> 
> For the parts that can be automated and done in batch, this is indeed
> more effective than 500 individual bugs.
> 
> However, I'm not sure if finding the new homepage and download URL can
> be that easily automated. In fact, users may do some work for us and
> help point to the right page.

Also, it would be nice not to have the berlios -> sourceforge crap
repeated. If software is dead-dead, we should lastrite it or revive it,
not point to some dead copy by malware hosting provider.

-- 
Best regards,
Michał Górny



pgphIkyAzZUIj.pgp
Description: OpenPGP digital signature

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

[Paweł Hajdan , Jr .]

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
much of that is needed.

Brainstorming mentions just cloning the URLs, but don't existing Gentoo
Mirrors have the same effect? My understanding is fetching will not
break even if original URLs go down.

I'm also not fully convinced by the manpower argument. It seems the same
work needs to be done, one way or another.

For the parts that can be automated and done in batch, this is indeed
more effective than 500 individual bugs.

However, I'm not sure if finding the new homepage and download URL can
be that easily automated. In fact, users may do some work for us and
help point to the right page.

HTH

Paweł



signature.asc
Description: OpenPGP digital signature

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

[M. J. Everitt]

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 |
>>> 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 ;-)  
>> Let me know which of the packages I maintain, and I will attempt to
>> update them. I have touched too many packages over the last few years
>> to know them on site.
>>
>> Your sorted list of obfuscated emails does not help at all.
>>
> ( curl http://dev.gentoo.org/~jstein/googlecode-shutdown.txt |  cut -f1 -d":" 
> | while IFS="" read -r arg; do echo -n "$arg: " ; equery meta -mH $arg 
> 2>/dev/null | tr "\n" " "; echo ; done ) | tee /tmp/package_owners.txt
>
> sed 's/:\s*$/: maintainer-needed/;s/\@//g' < /tmp/package_owners.txt > 
> /tmp/owners_obfu.txt
>
> cut -d" " -f 2-  < /tmp/owners_obfu.txt | tr " " "\n" | grep "^\w" | sort | 
> uniq -c | sort -n -k 1  > /tmp/owner_histogram.txt
> ( Attached )
>
> sort -k 2 < /tmp/owners_obfu.txt > /tmp/packages_by_owner.txt
> ( Attached )
>
> grep floppym /tmp/packages_by_owner.txt
> # dev-util/open-vcdiff-0.8.3: floppymgentoo.org 
> # sys-fs/fuse-exfat-1.0.1: floppymgentoo.org base-systemgentoo.org 
> # net-misc/ps3mediaserver-1.82.0: floppymgentoo.org vapiergentoo.org 
>
> tail -n 5 /tmp/owner_historgram.txt
> # 25 javagentoo.org
> # 38 pythongentoo.org
> # 43 proxy-maintgentoo.org
> # 56 maintainer-needed
> # 60 cjkgentoo.org
>
>
Kent+++

I'll have a look-see at the maintainer-needed@ set and see how bad it is.



signature.asc
Description: OpenPGP digital signature

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

[Kent Fredric]

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"
> >
> > I prefer to protect the list at least by substitution. It will not help
> > much, but makes me happier ;-)  
> 
> Let me know which of the packages I maintain, and I will attempt to
> update them. I have touched too many packages over the last few years
> to know them on site.
> 
> Your sorted list of obfuscated emails does not help at all.
> 

( curl http://dev.gentoo.org/~jstein/googlecode-shutdown.txt |  cut -f1 -d":" | 
while IFS="" read -r arg; do echo -n "$arg: " ; equery meta -mH $arg 
2>/dev/null | tr "\n" " "; echo ; done ) | tee /tmp/package_owners.txt

sed 's/:\s*$/: maintainer-needed/;s/\@//g' < /tmp/package_owners.txt > 
/tmp/owners_obfu.txt

cut -d" " -f 2-  < /tmp/owners_obfu.txt | tr " " "\n" | grep "^\w" | sort | 
uniq -c | sort -n -k 1  > /tmp/owner_histogram.txt
( Attached )

sort -k 2 < /tmp/owners_obfu.txt > /tmp/packages_by_owner.txt
( Attached )

grep floppym /tmp/packages_by_owner.txt
# dev-util/open-vcdiff-0.8.3: floppymgentoo.org 
# sys-fs/fuse-exfat-1.0.1: floppymgentoo.org base-systemgentoo.org 
# net-misc/ps3mediaserver-1.82.0: floppymgentoo.org vapiergentoo.org 

tail -n 5 /tmp/owner_historgram.txt
# 25 javagentoo.org
# 38 pythongentoo.org
# 43 proxy-maintgentoo.org
# 56 maintainer-needed
# 60 cjkgentoo.org


dev-libs/liblouis-2.5.3: accessibilitygentoo.org 
app-accessibility/emacspeak-39.0-r2: accessibilitygentoo.org 
gnu-emacsgentoo.org 
dev-python/platinfo-0.15.0-r1: aidecoegentoo.org pythongentoo.org 
sci-mathematics/geogebra-4.1.120.0: amynkagentoo.org 
x11-misc/tint2-0.11-r2: amynkagentoo.org 
media-libs/lib3ds-1.3.0-r1: amynkagentoo.org gamesgentoo.org 
3dprintgentoo.org 
media-libs/lib3ds-2.0.0_rc1: amynkagentoo.org gamesgentoo.org 
3dprintgentoo.org 
dev-python/ipaddr-2.1.10-r1: andreis.vinogradovsgmail.com 
maksbotangentoo.org proxy-maintgentoo.org pythongentoo.org 
net-misc/linux-eoip-0.5: andreis.vinogradovsgmail.com 
pinkbytegentoo.org proxy-maintgentoo.org 
games-misc/fortune-mod-gentoo-ru-0.25: andreis.vinogradovsgmail.com 
proxy-maintgentoo.org 
games-misc/fortune-mod-gentoo-ru-0.26: andreis.vinogradovsgmail.com 
proxy-maintgentoo.org 
dev-util/plan9port-20140306: andy753421gmail.com bluenessgentoo.org 
proxy-maintgentoo.org 
dev-util/plan9port-20140306-r1: andy753421gmail.com bluenessgentoo.org 
proxy-maintgentoo.org 
dev-util/plan9port-20140306-r2: andy753421gmail.com bluenessgentoo.org 
proxy-maintgentoo.org 
app-i18n/fcitx-anthy-0.1.1: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/fcitx-chewing-0.2.0: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/fcitx-cloudpinyin-0.3.1: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/fcitx-configtool-0.4.6: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/fcitx-hangul-0.2.1: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/fcitx-libpinyin-0.2.1: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/fcitx-sunpinyin-0.4.0: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/fcitx-table-extra-0.3.3: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/fcitx-unikey-0.2.0: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/mozc-1.10.1390.102-r1: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/mozc-1.13.1651.102: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/mozc-2.16.2037.102: arfrever.ftagmail.com cjkgentoo.org 
app-i18n/fcitx-rime-0.2.0: arfrever.ftagmail.com dlangentoo.org 
cjkgentoo.org 
net-libs/serf-1.3.8: arfrever.ftagmail.com proxy-maintgentoo.org 
net-libs/serf-1.3.8-r1: arfrever.ftagmail.com proxy-maintgentoo.org 
dev-games/aseprite-0.9.5-r1: azamat.hackimovgmail.com 
proxy-maintgentoo.org 
sys-apps/mtree-1.0.1: base-systemgentoo.org 
sys-apps/mtree-1.0: base-systemgentoo.org 
net-libs/pacparser-1.3.1: bicataligentoo.org 
net-proxy/torsocks-1.2-r2: bluenessgentoo.org 
dev-libs/leveldb-1.10.0-r1: bugsbergstroem.nu patrickgentoo.org 
proxy-maintgentoo.org 
dev-libs/leveldb-1.11.0-r1: bugsbergstroem.nu patrickgentoo.org 
proxy-maintgentoo.org 
dev-libs/leveldb-1.12.0-r1: bugsbergstroem.nu patrickgentoo.org 
proxy-maintgentoo.org 
dev-libs/leveldb-1.13.0-r1: bugsbergstroem.nu patrickgentoo.org 
proxy-maintgentoo.org 
dev-libs/leveldb-1.14.0: bugsbergstroem.nu patrickgentoo.org 
proxy-maintgentoo.org 
dev-libs/leveldb-1.15.0: bugsbergstroem.nu patrickgentoo.org 
proxy-maintgentoo.org 
dev-libs/leveldb-1.15.0-r1: bugsbergstroem.nu patrickgentoo.org 
proxy-maintgentoo.org 
dev-libs/leveldb-1.9.0-r5: bugsbergstroem.nu patrickgentoo.org 
proxy-maintgentoo.org 
dev-libs/leveldb-1.9.0-r6: bugsbergstroem.nu patrickgentoo.org 
proxy-maintgentoo.org 
net-misc/openr2-1.3.0: chainsawgentoo.org 
app-benchmarks/i7z-0.27.2: chewigentoo.org 
dev-libs/re2-0_p20130115: chromiumgentoo.org 
dev-libs/re2-0_p20130115-r1: chromiumgentoo.org 
dev-libs/re2-0_p20130

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

[Mike Gilbert]

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":" | 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 ;-)

Let me know which of the packages I maintain, and I will attempt to
update them. I have touched too many packages over the last few years
to know them on site.

Your sorted list of obfuscated emails does not help at all.

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

[Jonas Stein]

>> 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 ;-)

Best,
Jonas

=

3dprint__gentoo.org
accessibility__gentoo.org
aidecoe__gentoo.org
amynka__gentoo.org
andreis.vinogradovs__gmail.com
andy753421__gmail.com
arfrever.fta__gmail.com
azamat.hackimov__gmail.com
base-system__gentoo.org
bicatali__gentoo.org
blueness__gentoo.org
chainsaw__gentoo.org
chewi__gentoo.org
chromium__gentoo.org
chutzpah__gentoo.org
cjk__gentoo.org
cluster__gentoo.org
cpp__gentoo.org
crypto__gentoo.org
desktop-misc__gentoo.org
dev-zero__gentoo.org
dirk.vdb__gmail.com
dlan__gentoo.org
dominik.kriegner+gentoo__gmail.com
dotnet__gentoo.org
DuPol__gmx.de
embedded__gentoo.org
ercpe__gentoo.org
floppym__gentoo.org
fonts__gentoo.org
forensics__gentoo.org
freedesktop-bugs__gentoo.org
games__gentoo.org
gienah__gentoo.org
givi-zurabovich__mail.ru
gnu-emacs__gentoo.org
god__politeia.in
graphics__gentoo.org
grozin__gentoo.org
hanno__gentoo.org
haskell__gentoo.org
hwoarang__gentoo.org
hypnos75__gmail.com
idl0r__gentoo.org
ikelos__gentoo.org
java__gentoo.org
jlec__gentoo.org
johu__gentoo.org
jstein__gentoo.org
kde__gentoo.org
kensington__gentoo.org
leechcraft__gentoo.org
maksbotan__gentoo.org
matthias__dsx.at
media-video__gentoo.org
mgorny__gentoo.org
ml__gentoo.org
monsieurp__gentoo.org
mrueg__gentoo.org
mysql-bugs__gentoo.org
naota__gentoo.org
net-mail__gentoo.org
netmon__gentoo.org
nikoli__gmx.us
nils__nils-andresen.de
office__gentoo.org
oleg__kaa.org.ua
ottxor__gentoo.org
pacho__gentoo.org
patrick__gentoo.org
perl__gentoo.org
phajdan.jr__gentoo.org
php-bugs__gentoo.org
pinkbyte__gentoo.org
polynomial-c__gentoo.org
proaudio__gentoo.org
prometheanfire__gentoo.org
proxy-maint__gentoo.org
python__gentoo.org
qt__gentoo.org
radhermit__gentoo.org
rafaelmartins__gentoo.org
rhill__gentoo.org
rini17__gmail.com
robbat2__gentoo.org
sautier.louis__gmail.com
scheme__gentoo.org
sci-biology__gentoo.org
sci-chemistry__gentoo.org
sci__gentoo.org
sci-mathematics__gentoo.org
sergio.rodriguez.inclan__gmail.com
shell-tools__gentoo.org
slawomir.nizio__sabayon.org
slis__gentoo.org
slyfox__gentoo.org
sound__gentoo.org
spiderx__spiderx.dp.ua
tcltk__gentoo.org
tex__gentoo.org
tomboy64__sina.cn
tomka__gentoo.org
vapier__gentoo.org
vikraman__gentoo.org
vim__gentoo.org
virtualization__gentoo.org
volkris__gmail.com
web-apps__gentoo.org
williamh__gentoo.org
xfce__gentoo.org
xmw__gentoo.org
zerochaos__gentoo.org
ziapannocchia__gmail.com
zlg__gentoo.org

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

[M. J. Everitt]

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 a command line utility if you're doing things the shell way.
>
> But, from that python script I linked the relevant part is:
>
> from portage.xml.metadata import MetaDataXML
>
> metxml = path+"/"+category+"/"+pkgname+"/metadata.xml"
> maints=[]
> try:
>   pkg_md = MetaDataXML(metxml,"/usr/portage/metadata/herds.xml")
>   for maint in pkg_md.maintainers():
>   maints.append(maint.email)
> except IOError: pass
>
> Just feed that api call with a metadata.xml.  Hopefuly it works with
> the projects.xml syntax as herds.xml is of course defunct.I'd
> check the portage API docs as there might be some improvements there.
>
> The portage api is actually fairly powerful and far superior to a lot
> of stuff that gets done with grep.  It just needs a bit of time
> getting used to it since there aren't a lot of docs/examples/etc
> floating around.  The script that came out of was designed to find
> packages that depend on packages that expose subslots but which don't
> define slot operator deps.  Granted, not everything in that list
> should be using them, and by now I imagine it is almost entirely false
> positives, but it shows the sort of thing you can do with a couple of
> lines of python that would be an incredible pain to do any other way.
> I believe paludis also exposes some APIs that probably could also be
> used.
>
Bit beyond my python-fu .. but I get where you're going with that. If I
wasn't banging my head against cups/hplip, I might give it a shot ... :P !!



signature.asc
Description: OpenPGP digital signature

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

[Jonas Stein]

> 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

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

[Rich Freeman]

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 the shell way.

But, from that python script I linked the relevant part is:

from portage.xml.metadata import MetaDataXML

metxml = path+"/"+category+"/"+pkgname+"/metadata.xml"
maints=[]
try:
  pkg_md = MetaDataXML(metxml,"/usr/portage/metadata/herds.xml")
  for maint in pkg_md.maintainers():
  maints.append(maint.email)
except IOError: pass

Just feed that api call with a metadata.xml.  Hopefuly it works with
the projects.xml syntax as herds.xml is of course defunct.I'd
check the portage API docs as there might be some improvements there.

The portage api is actually fairly powerful and far superior to a lot
of stuff that gets done with grep.  It just needs a bit of time
getting used to it since there aren't a lot of docs/examples/etc
floating around.  The script that came out of was designed to find
packages that depend on packages that expose subslots but which don't
define slot operator deps.  Granted, not everything in that list
should be using them, and by now I imagine it is almost entirely false
positives, but it shows the sort of thing you can do with a couple of
lines of python that would be an incredible pain to do any other way.
I believe paludis also exposes some APIs that probably could also be
used.

-- 
Rich

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

[M. J. Everitt]

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 maintainer.
>> Hopefully this isn't using anything deprecated, but you should be able
>> to steal from this:
>> https://github.com/rich0/finddepslotops/blob/master/finddepslotops.py
>>
>> Somebody else might have something more up-to-date to use.
>>
> Yeah that's not the best qgrep output for this target ... ;P
>
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 ...



signature.asc
Description: OpenPGP digital signature

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

[M. J. Everitt]

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 deprecated, but you should be able
> to steal from this:
> https://github.com/rich0/finddepslotops/blob/master/finddepslotops.py
>
> Somebody else might have something more up-to-date to use.
>
Yeah that's not the best qgrep output for this target ... ;P



signature.asc
Description: OpenPGP digital signature

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

[Rich Freeman]

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 this:
https://github.com/rich0/finddepslotops/blob/master/finddepslotops.py

Somebody else might have something more up-to-date to use.

-- 
Rich

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

[Jonas Stein]

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 these packages, please fix the SRC_URI and
HOMEPAGE variables.

We have also a wiki page [3] and thanks to Andreas Huettel we can
monitor our daily effort in a plot [4].

[1]
http://google-opensource.blogspot.de/2015/03/farewell-to-google-code.html
[2] http://dev.gentoo.org/~jstein/googlecode-shutdown.txt
[3] https://wiki.gentoo.org/wiki/Shutdown_of_google_code
[4] http://www.akhuettel.de/~huettel/plots/googlecode.php

-- 
Best,
Jonas