public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [Bug 488318] media-video/mpv[luajit] - Keyword request on alpha, arm, ppc, ppc64, sparc
Date: Sun, 20 Oct 2013 14:23:57 +0200	[thread overview]
Message-ID: <20131020142357.4b31184e@TOMWIJ-GENTOO> (raw)
In-Reply-To: <5263ADEC.9000000@gentoo.org>

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

On Sun, 20 Oct 2013 11:18:20 +0100
Markos Chandras <hwoarang@gentoo.org> wrote:

> > P.S.: It is interesting to see the effects of AutoRepoman beating 
> > people to filing bugs, maybe I should write AutoNotifyman as a
> > response to not having the chance to file the bug in a reasonable
> > time frame.
> > 
> The AutoRepoman script is there just for convenience. You shouldn't
> take it too seriously and go filing bugs like crazy. The affected
> packages can slowly be fixed. It's not like they are totally broken
> but it's more like of another way to tell you that a few QA problems
> exist and that it would be nice to fix them whenever you find some
> time.

Sorry, I was trying to refer to automating that I am currently manually
filing a bug when committing, because its contents are usually the same.

When committing a package I could have repoman ask to "File a bug?" and
then it would drop the keywords or package.use.mask them (it kind of
depends on what we decide we consistently want to do) and then make a
KEYWORDREQ bug based on the list of keywords that it warned about.

That way deferring it to other persons or delaying it for later in the
day won't happen as side effects.

These kind of dropped keywords happen frequently with Java packages;
version bumps usually bring in new and/or rare dependencies that are
only keyworded for amd64, whereas the package itself has multiple.

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

iQEcBAEBAgAGBQJSY8thAAoJEJWyH81tNOV9PgsH/1MCH0VbDKgkoPhN854plaUZ
/O5uYz6YeodkBo1q+1Ipc0/vz/+V/+sCgrXlthwKOyWwmecBk6TOLngBt4z5zDfs
CnG5tsBUYyoATYbtVopCBkcZDVY9vjSGn5nbZOVHO3MFjIbw/ODe2R2stIZ72ur8
2wZMEUlUDoSVvKF/HWSGHOdHXP0AM647h3bWlHD6MZ13l4nP8P0Mbo1ZXzxJMxZa
9UYoiKQ9tf9hHa05ez6fsBZOZ0z0jMblCjz2B2FzOkJziB5zQAkV2qIu8q4aIZIm
Hx2uaFkABz1Msv7Q/okwT9bMrSqNzbSlQ8OxwAmKHOkErCeNO/Nfw/2i1DRQo7M=
=xVxd
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2013-10-20 12:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-488318-23709@http.bugs.gentoo.org/>
     [not found] ` <bug-488318-23709-Ghdn7p7FCs@http.bugs.gentoo.org/>
2013-10-19 17:01   ` [gentoo-dev] Re: [Bug 488318] media-video/mpv[luajit] - Keyword request on alpha, arm, ppc, ppc64, sparc Jeroen Roovers
2013-10-19 17:43     ` Tom Wijsman
2013-10-20 10:18       ` Markos Chandras
2013-10-20 10:40         ` Patrick Lauer
2013-10-20 11:41           ` Markos Chandras
2013-10-20 12:30             ` Tom Wijsman
2013-10-21 13:50               ` Jeroen Roovers
2013-10-21 15:32                 ` Tom Wijsman
2013-10-21 16:31                   ` Jeroen Roovers
2013-10-21 17:03                     ` Tom Wijsman
2013-10-20 14:05             ` Patrick Lauer
2013-10-21 13:32             ` Jeroen Roovers
2013-10-21 16:19               ` Tom Wijsman
2013-10-21 19:16               ` Markos Chandras
2013-11-02 21:22                 ` [Bug 304435] Developer Handbook should document how/when to touch arch profiles' files (was: Re: [gentoo-dev] Re: [Bug 488318] media-video/mpv[luajit] - Keyword request on alpha, arm, ppc, ppc64, sparc) Tom Wijsman
2013-10-20 12:23         ` Tom Wijsman [this message]

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=20131020142357.4b31184e@TOMWIJ-GENTOO \
    --to=tomwij@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