Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: "Paweł Hajdan, Jr." <phajdan.jr@g.o>
Subject: Re: repoman not complaining when going straight to stable
Date: Tue, 29 Nov 2011 13:11:47 +0100
On 11/26/11 11:29 AM, Sergei Trofimovich wrote:
> On Sat, 26 Nov 2011 10:15:53 +0100
> ""Paweł Hajdan, Jr."" <phajdan.jr@g.o> 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:
signature.asc (OpenPGP digital signature)
Replies:
Re: repoman not complaining when going straight to stable
-- Zac Medico
References:
repoman not complaining when going straight to stable
-- Paweł Hajdan, Jr.
Re: repoman not complaining when going straight to stable
-- Sergei Trofimovich
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: repoman not complaining when going straight to stable
Next by thread:
Re: repoman not complaining when going straight to stable
Previous by date:
Re: [gentoo-commits] gentoo-x86 commit in eclass: vim.eclass
Next by date:
Re: making the stable tree more up-to-date


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.