public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] repoman not complaining when going straight to stable
Date: Tue, 29 Nov 2011 13:11:47 +0100	[thread overview]
Message-ID: <4ED4CC03.4040501@gentoo.org> (raw)
In-Reply-To: <20111126133000.0d487bb0@sf.home>

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

On 11/26/11 11:29 AM, Sergei Trofimovich wrote:
> On Sat, 26 Nov 2011 10:15:53 +0100
> ""Paweł Hajdan, Jr."" <phajdan.jr@gentoo.org> wrote:
> 
>> This shouldn't be allowed, should it? The package is keyworded only
>> ~x86, and I'm adding amd64 stable keyword, and repoman doesn't complain.
> 
> It would need to fetch latest CVS file from server to check against previous state.
> I don't think repoman does any network IO safe updating metadata.dtd.

Why does it warn about going straight to stable for _new_ ebuilds? Is it
because it knows locally that it's a new file, and because of that
doesn't need to connect to network? That'd make sense.

Would it be possible to add repoman checks (possibly behind a special
flag) that could use "cvs diff" results?


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

  reply	other threads:[~2011-11-29 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26  9:15 [gentoo-dev] repoman not complaining when going straight to stable "Paweł Hajdan, Jr."
2011-11-26 10:29 ` Sergei Trofimovich
2011-11-29 12:11   ` "Paweł Hajdan, Jr." [this message]
2011-11-29 16:09     ` Zac Medico

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=4ED4CC03.4040501@gentoo.org \
    --to=phajdan.jr@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