public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Zac Medico <zmedico@gentoo.org>
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] repoman: Make LIVEVCS.* checks fatal
Date: Thu, 30 Jun 2016 07:54:45 +0200	[thread overview]
Message-ID: <20160630075445.6183cd7a.mgorny@gentoo.org> (raw)
In-Reply-To: <5772D297.3080500@gentoo.org>

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

On Tue, 28 Jun 2016 12:40:07 -0700
Zac Medico <zmedico@gentoo.org> wrote:

> On 06/28/2016 11:30 AM, Michał Górny wrote:
> > Make LIVEVCS.* checks fatal to prevent people from committing ebuilds
> > using live eclasses instead of package.masking them afterwards by QA.
> > ---
> >  repoman/pym/repoman/qa_data.py | 2 --
> >  1 file changed, 2 deletions(-)
> > 
> > diff --git a/repoman/pym/repoman/qa_data.py b/repoman/pym/repoman/qa_data.py
> > index 48ab389..738368e 100644
> > --- a/repoman/pym/repoman/qa_data.py
> > +++ b/repoman/pym/repoman/qa_data.py
> > @@ -270,8 +270,6 @@ qawarnings = set((
> >  	"repo.eapi.deprecated",
> >  	"usage.obsolete",
> >  	"upstream.workaround",
> > -	"LIVEVCS.stable",
> > -	"LIVEVCS.unmasked",
> >  	"IUSE.rubydeprecated",
> >  ))
> >  
> >   
> 
> Looks good.

Signed and pushed!

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

      reply	other threads:[~2016-06-30  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 18:30 [gentoo-portage-dev] [PATCH] repoman: Make LIVEVCS.* checks fatal Michał Górny
2016-06-28 19:40 ` Zac Medico
2016-06-30  5:54   ` Michał Górny [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=20160630075445.6183cd7a.mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    --cc=zmedico@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