public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: hwoarang@gentoo.org, gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-sound/umurmur: metadata.xml ChangeLog
Date: Sat, 28 Dec 2013 17:35:02 +0100	[thread overview]
Message-ID: <20131228173502.224c9f96@TOMWIJ-GENTOO> (raw)
In-Reply-To: <52BEEA2D.2020103@gentoo.org>

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

On Sat, 28 Dec 2013 15:11:41 +0000
Markos Chandras <hwoarang@gentoo.org> wrote:

> I feel that this thread is a sign that
> there is a problem on how the new QA communicates problems with the
> developers that cause them.

This thread can also be perceived as the results of intentionally
introducing and reintroducing a repoman warning; while some will read
this as an accusation, others read this as a regression. And while you
mention us, we're not alone in this happening; but let's not blame...

There are always two sides to this, and we should focus on neither.

Two problems can be seen here, both are very clear; the first is a
repoman warning (which is QA communication), the second are multiple
reverts. The former has been communicated before this ML thread by
Patrick; the latter has been communicated in my very first answer, which
package.use.mask solution has been implemented later by Lars.

> I read the entire thread and I still don't
> think there is an agreement on who broke the tree and why.

The discussion is based on some questions that are hard to agree on:

1. How much of a problem is an unused USE flag in metadata.xml? 

2. Should such repoman warnings be fixed? By whom? When? How?

3. Can USE flags actually be removed from stable ebuilds?

4. ...

Because this can yield quite some bike-shedding; the alternative "out of
the box thinking" package.use.mask solution satisfies both parties,
which renders that discussion unnecessary. Nobody has objected this.

> Would a
> private discussion be better before going publicly with accusations?

Yes, people can join #gentoo-qa or mail us and we're happy to discuss.

- -- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJSvv27AAoJEJWyH81tNOV9ytoIALxo84RfrvER1x8q7rJX7wxP
DcLp50YPWoxngvdrVmw9+ejIakNqlRXujXx2QTt8EHoFu+2YSm1Ww1b4QhWiDk0P
Gsbw7deIfFE8GIG5l624roIDG7+434ACvIJF5WwoMuo199wRJMM7RurIOiDrEyI4
VWg3S83bU9gAcO1qsL0PxR1HK0aDuzqB2MXqbyBpqeX653kkxFn4JWBESp8XFvY0
lDZhQJuucbNYWeO5ir106rtXFTP75D7CkYFH5RYZ3MmuD1eDLRZW/ep4EAa+1j0V
3gm4L/AL4ol+SbBOYsoL9/nn3AB/J9fNDsQFoer7azDjxOzmNm5/5FeBiix/A/I=
=Mxd1
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2013-12-28 16:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131225095020.A91BE2004C@flycatcher.gentoo.org>
2013-12-25 12:26 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-sound/umurmur: metadata.xml ChangeLog hasufell
2013-12-25 12:42   ` Tom Wijsman
2013-12-25 13:16   ` Patrick Lauer
2013-12-25 13:30     ` Kent Fredric
2013-12-26 13:25     ` hasufell
2013-12-26 13:27       ` Ciaran McCreesh
2013-12-26 13:29         ` hasufell
2013-12-26 13:53           ` Patrick Lauer
2013-12-27  0:52         ` vivo75
2013-12-28 15:11         ` Markos Chandras
2013-12-28 15:44           ` Andreas K. Huettel
2013-12-28 15:44             ` Markos Chandras
2013-12-28 16:50               ` Tom Wijsman
2013-12-28 18:35               ` hasufell
2013-12-28 16:35           ` Tom Wijsman [this message]
2013-12-28 17:26             ` Patrick Lauer
2013-12-28 18:12               ` Tom Wijsman
2013-12-26 17:20     ` Lars Wendler
2013-12-25 17:37   ` Patrick Lauer
2013-12-26 18:59     ` Ryan Hill

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=20131228173502.224c9f96@TOMWIJ-GENTOO \
    --to=tomwij@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=hwoarang@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