Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-libs/boost: boost-1.46.1-r1.ebuild metadata.xml boost-1.49.0-r1.ebuild boost-1.51.0-r1.ebuild ChangeLog boost-1.47.0.ebuild boost-1.35.0-r2.ebuild boost-1.47.0-r1.ebuild boost-1.39.0.ebuild boost-1.50.0-r2.ebuild boost-1.42.0-r1.ebuild boost-1.51.0.ebuild boost-1.37.0-r1.ebuild boost-1.42.0-r2.ebuild boost-1.50.0.ebuild boost-1.48.0-r2.ebuild boost-1.42.0.ebuild boost-1.35.0-r5.ebuild boost-1.41.0-r3.ebuild boost-1.45.0.ebuild

["Michał Górny" <mgorny@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 2232 bytes --]

On Wed, 31 Oct 2012 11:58:16 -0700
Diego Elio Pettenò <flameeyes@flameeyes.eu> wrote:

> On 31/10/2012 11:49, Michał Górny wrote:
> > In other words, you have thrown a big, destructive change to live,
> > stable systems without prior testing (and don't say you were able to
> > test it thoroughly in one day's time) and you have left them for other
> > people to maintain and fix.
> > 
> > I am really getting tired of those 'senior developers' who believe that
> > Gentoo is their private playground where they can do whatever comes
> > into their mind and ignore package maintainers.
> 
> Given the kind of destructive behaviour that boost has been having,
> given that everybody else _beside you_ don't see any reason to keep that
> slotted boost, given that you've been acting for the most part as a
> sockpuppet for a developer who's been kicked out of Gentoo, I think it's
> obvious why I went the way I went.

If you have a personal vendetta against Arfrever, then take it to him.
As far as I'm concerned, Arfrever is a very knowledgeable person and I
doubt that you can compete with him in the area of Python
(and the Python counterpart of boost, effectively).

And even if that, you have no right to remove maintainers
from a package or unCC them from bugs just because you don't like them
or disagree with their opinion. Especially that you are not
a maintainer of this package.

> Here's the deal: I've stated clearly what the situation was going to be;
> Tiziano has been the primary maintainer (first in the list) and he's
> okay with the move, he _is_ in the cpp herd that will take care of it,
> and as I said I'll make sure to help out because I have a number of
> packages depending on boost (but not on other C++ libraries).

Sorry, I didn't notice his reply. That's my mistake.

> You had a month while Mike delayed glibc-2.16 stable, among other things
> because of boost-1.50, and you did _squat_ to handle it. So it's time
> that people who've been there before step up and fix it the way that it
> has to be fixed.

Is this something like 'people didn't fix issues yet, so let's throw
the issues at users to motivate them'?

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]