Re: [gentoo-dev] Cross Post due to technical component - Thanks for all the fish

[Kristian Fiskerstrand]

> On 12/21/2016 11:23 PM, i...@gentoo.org wrote:
Why is this email sent using an invalid email addresse in FROM?

As for the rest of the email content itself, please consider the
appropriate forum for any discussion, and I strongly recommend staying
away from personal attacks.

-- 
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-dev] Cross Post due to technical component - Thanks for all the fish

[Delaney]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Tue, 06 Dec 2016 23:39:00 +
Gokturk Yuksek  wrote:

> Hi,
> 
   
Lo

> 
> The mailing list for proxy-maint was created 5 months ago [0], can be
> reached by emailing gentoo-proxy-ma...@lists.gentoo.org after
> subscribing, and the archive is located at [1].

Factual undisputed statement of factual undisputable fact. What else
to expect form a gokturk.

> 
> Regarding your comment on working with individual developers, I have
> not seen anything related to that in the project alias.

In the project alias. So *** what. The project alias is now dev
only I think I would no longer know, however, that might be a
misunderstanding on the part of the user who told me the devs made the
alias list devs only. Either way, he missed that clanger of an email
from gokturk regarding the pending return of the most 'awkward' and
menacing devs in the history of g-p-m, in late November; its former
lead who in respect of good tsate shall remain nameless. 

h yes, the project to this day has a lead developer "no-lead", the
most recent of the string of farce and embarrassment in the history of
that most tainted of gentoo projects, gentoo-proxy-maint.  It is I
would also say a fine project that deserved and deserves FAR better
than the string of dishonour that now taints it.

Regarding working with individual developers. you can talk  Was
it not you who made a targeted barrage of both bugs to QA to the
'legitimate' forum, 'per protocol' putting members of g-p-m at the
time under unwanted un-needed and most importantly undeserved  pressure
and scrutiny of commits from that 'dreadful and dishonourable' source
gentoo-proxy-maint, COMBINED with forwarding logs from PRIVATE message
source complete with breach of trust of use of PRIVATE message to the
honourable hard working radical right wing group comrel (comedy relief)
charged with upholding all that is right, desirable and clinically
impersonally piously 'perfectly' professional of the community, The
community that gave cause to one xayto to forward an email to the ML
sub entitled "Thanks for all the fish".

Also, to fill the missing key point about that email, that 'clanger'.
This fine sterile developer took it upon himself to both negatively
critique the behaviour and morals of that former lead whoever he was in
times past, then submitted a motion to extend the ban placed upon the
lead who shall remain nameless, by another 6 months, on the premiss of,
well there wasn't one really, other than that of prejudice and the
mentality of a lynch mob.

And guess who seconded the motion ... Anyone ???

> I would be more than happy 

oh what a gay chappy, in the original and traditional use of the
word, of course. One does NOT wish to offend anyone of any warped 
orientation here.

> to personally help you out with proxy-maintainership.
> 
> Thanks,
> 

keep it.

> --
> gokturk
> 
> [0] https://bugs.gentoo.org/show_bug.cgi?id=581370
> [1] https://archives.gentoo.org/gentoo-proxy-maint/
> 
> 

P.S. ya'll might care to respond but if you do it will not be me
reading the retorts rebuttals and more butts. I came across this by
chance and boredom

- -- 
most kind regards

Ian Delaney
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.1

iQJ8BAEBCgBmBQJYWwDiXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCRUI4RjAxNzRGRTVDMjI4RjcxNkRFNzIw
QzQzN0NCNDcxRTlEMzNBAAoJEAxDfLRx6dM6TU0P/0kXX8uoshksCMrCMfGcBwxT
yrWcbSM1Z41aXs7yel03ysy0mzwxJ+Aj3aWNEP8HjXJY1Cvfkz+UskOmr4w+F3q+
sNN75rr4wvwd0Yh7zFFHEBiHFYK3lapNOKeIOTKyrpv7IZs8vhv8r29Y0FxuWDn/
pPb9D9rlVUDA+DHL9NRFm4Lppap1Y7WkU79AVMjFq2lBW2znrAJJ5T9OZy4RBiPu
MFGq9uzjczEAmZzcUVoX4H9YqispsO1c3c2sFzHgaR22bb6zfmiJGdf1jBpRShim
3g8q0J+Cs+1ZfzfcDOdf3U3eRhUBjkFqI/ItsE0AQHUmImHlvPS2oNvi+oavBv+k
byiEw/qEPgrR7LqCGvOXJWb8ZXrqva/F1dg4hMWFQWTcQV9zcaBJt45TSjFv5CuI
DgeVuuNu67uu7Xim74snJhlMOPkSbhkmRMAsSSv7m0l2oNQA+x39k3C8A84Hfb0/
QGUdor9BMAJy2PvObeSkyFb53NBIjSriBAAvfuC2oH+tvAeV3ex6sPjZaNyOE/7J
NkhV6CxzqB0d+sj9onDfr6Q/sMxwSXPMncmfva//TnTtCujvkgOOBLvLmH5T0Iql
rymGdt4sbLSZkX1kncbnAxYV/4eA+WrtqZNzta9PcCQIJqO9W5h85uRlaWvEMhiZ
8MqvsV1u/W+ltOwnFTe2
=6uyd
-END PGP SIGNATURE-

[gentoo-dev] Changes in toolchain.eclass to enable Ada

[Alfredo Tupone]

I would like to revive the Ada support in gentoo.

One ada compiler is produced by AdaCore and is provided in three
versions, in the order starting from the best supported :

1) GnatPro, available with a contract support.

2) Gnat-GPL that can only build GPL-3 product

3) The gnat included in the gcc tree that is GPL-3 with exception.

Gnat-GPL is very like the gnat in the gcc-tree so it can be built in
the same way of sys-devel/gcc

To be compiled from source the gcc compiler needs a C, C++, and Ada
Compiler. I will provide one with the gnat-gpl-bin tar that could be
installed under /opt . When the gcc is properly compiled we don't need
it any more.

I would like to start including, in the gentoo tree, GNAT-GPL
built in the same way as sys-devel-gcc and selectable with gcc-config

As for instance gnat-gpl-2014 is based on gcc-4.7.4 they cannot coexist
and gnat-gpl-2014 will block sys-devel/gcc-4.7.4

As a reference I have my overlay on https://github.com/atupone/overlay
and a pull request at https://github.com/gentoo/gentoo/pull/3186

To start I need to change the toolchain.eclass 

-   tc_version_is_at_least 4.7 && IUSE+=" go"
+   tc_version_is_at_least 4.7 && IUSE+=" go ada"

-   # We do NOT want 'ADA support' in here!
-   # is_ada && GCC_LANG+=",ada"
+   # We do want 'ADA support' here!
+   is_ada && GCC_LANG+=",ada" 

-   for x in cpp gcc g++ c++ gcov g77 gcj gcjh gfortran gccgo ; do
+   for x in cpp gcc g++ c++ gcov g77 gcj gcjh gfortran gccgo gnatbind; do 

Thats all for that.

Then, to not change the behaviour of the gcc-compiler, we could mask the
ada use flag for sys-devel/gcc, at least temporarily

-

I would like to have comments on that, particularly because:
a) it is going to add a use flag to sys-devel/gcc that will bring gcc
to be rebuilt on most system, 
b) the gnat-gpl, if selected with gcc-config, can be used to recompile
all the system, and maybe is not so good ?

Alfredo

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

[gentoo-dev] Packages up for grabs

[Tomas Mozes]

These packages are now up for grabs:

dev-python/httmock
dev-python/jenkins-autojobs
dev-python/jenkins-webapi
dev-python/jenkinsapi

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