public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tomáš Chvátal" <scarabeus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-libs/libva: ChangeLog libva-1.0.10.ebuild
Date: Wed, 09 Mar 2011 14:13:50 +0100	[thread overview]
Message-ID: <4D777D0E.5090107@gentoo.org> (raw)
In-Reply-To: <201103090908.33359.aballier@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dne 9.3.2011 13:08, Alexis Ballier napsal(a):
> On Tuesday, March 08, 2011 12:23:03 PM Tomáš Chvátal wrote:
>> Dne 8.3.2011 15:51, Alexis Ballier napsal(a):
>>> On Tuesday, March 08, 2011 09:28:13 AM Tomas Chvatal (scarabeus) wrote:
>>>> scarabeus    11/03/08 12:28:13
>>>>
>>>>   Modified:             ChangeLog
>>>>   Added:                libva-1.0.10.ebuild
>>>>   Log:
>>>>   Update to libva shipped by freedesktop. So we do the same as debian or
>>>>
>>>> archlinux. Fixes bug #336854.
>>>
>>> Please read metadata.xml before committing...
>>
>> I did, x11 is the herd last time i looked.
> 
> x11 is the herd because when I added it I thought that it was low level enough 
> that x11 may help from time to time. This never gave the right to anyone to 
> break and hijack it without discussion nor notice like you did.
> Since it seems to be more a burden than a help, I'll remove x11 herd from 
> metadata too when removing the fdo version.
> 
> Maybe something you didn't understand: herd/maintainership isn't about 
> territoriality and giving the right to commit crap, it's about area of 
> responsability.
> 
>>
>>> How comes I'm supposed to be the maintainer and have not seen any single
>>> discussion about it ? Why is it better, etc ? Being a "mouton de Panurge"
>>> is not a reason [1] :)
>>> The only "better" thing I see is a greater version number. May I suggest
>>> you to run a diff and explain me why such a change was needed ?
>>
>> ok lovely list:
>> 1) it has freedesktop web page, and we should preffer fdo alternatives
>> anyway
> 
> yes, didnt you think that maybe there's a reason I've been using the sds 
> version for almost one year ?
You never named them anywhere.
> 
>> 2) it has existing git repo (could not find repo for the va you use)
> 
> you clearly didnt run a diff... its the fdo version + a debian/patches dir 
> with, heh, some fixes and improvements I'm using...
I did run a diff, what am I supposed to trust some weird patches not
signed or commited to some repo...
> 
>> 3) debian/archlinux/fedora use this one I commited, not former one.
> 
> so what?
We have this tendency to use what others do so...
> 
>> 4) the bug was reported to you with x11 CC and you had 6 months already
>> to at least reply to it why/if you don't agree with the switch.
>> Suprisingly we try to close long-open bugs with no-maintainer reply.
> 
> There was no reply because I didn't see the point, for now, to flame users by 
> telling them that a version number doesnt necessarily bring them more code nor 
> features. I thought gentoo developers were aware of that. I was wrong.
> I left it open because I thought, at some point, that we will not need the sds 
> version. I don't think it's the case now.
So first you say you was not aware of the discussion, now you say you
just didn't feel the need to reply.
I did see that you commited copied version of older one, given the fancy
amount of people just doing cp a b for version bumps and not bothering
by any bugs I just went ahead and looked what other guys does and made
it same. I would commit the update even if it would be libva-0.0.1 I
didn't do it for sake of the version.
> 
> Seeing that I bumped it ~1 week ago, did you really expect that it was an 
> abandonned package and that you were saving it ? Were you trying to hijack it? 
> Or maybe just piss me off ?
> 

Just consider I tried to piss you off if you have this attitude. I could
not care less about some libva if i would not be looking on that bug for
some time without any damn reply from maintainer and x11 in CC.

I usually ask on irc, but given the fact you don't bother with the
media... just remove x11 from herds and enjoy your package.

You might also consider dropping x11 from x11-libs/vdpau-video

Cheerios
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk13fQ4ACgkQHB6c3gNBRYe7uQCfYDna/Scn7UHhic5V6shuk70p
PvUAn2ijeJeu0qdwyvT3avR48k1tXJ/m
=xp8D
-----END PGP SIGNATURE-----



  reply	other threads:[~2011-03-09 13:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110308122813.BD46320054@flycatcher.gentoo.org>
2011-03-08 14:51 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-libs/libva: ChangeLog libva-1.0.10.ebuild Alexis Ballier
2011-03-08 15:23   ` Tomáš Chvátal
2011-03-09  3:52     ` Ryan Hill
2011-03-09 12:08     ` Alexis Ballier
2011-03-09 13:13       ` Tomáš Chvátal [this message]
2011-03-09 13:53         ` Alexis Ballier
2011-04-29 19:17           ` Matt Turner
2011-05-09 16:25             ` Matt Turner
2011-05-09 22:38               ` Alexis Ballier
2011-05-09 23:00                 ` Matt Turner
2011-05-09 23:44                   ` Alexis Ballier
2011-03-09 13:48       ` Jeremy Olexa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D777D0E.5090107@gentoo.org \
    --to=scarabeus@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox