On Sat, 15 Sep 2012 18:47:56 -0400 Mike Frysinger <vap...@gentoo.org> wrote:
> On Tuesday 11 September 2012 14:06:30 Alexis Ballier wrote: > > On Tue, 28 Aug 2012 00:23:11 +0000 (UTC) Mike Frysinger wrote: > > > vapier 12/08/28 00:23:11 > > > > > > Modified: ChangeLog profiles.desc > > > Log: > > > add new s390x profile #345421 > > > > [...] > > > > > @@ -152,7 +153,7 @@ > > > > > > x86 default/linux/x86/10.0/server > > > > > > stable > > > > > > # Gentoo/FreeBSD Profiles > > > > > > -amd64-fbsd default/bsd/fbsd/amd64/9.0 stable > > > +amd64-fbsd default/bsd/fbsd/amd64/9.0 dev > > > sparc-fbsd default/bsd/fbsd/sparc/8.2 exp > > > x86-fbsd default/bsd/fbsd/x86/8.2 dev > > > x86-fbsd default/bsd/fbsd/x86/9.0 dev > > > > please be more careful, it is good practice to review the cvs diff > > output before hitting ci when committing to the profiles or eclass > > directories. > > that was only partially an accident. amd64-fbsd has no business > being in stable since it has broken deps and has no stable keywords. search the archives as for why its stable. profile not being stable is the cause for broken deps, not the consequence... also, where does your idea stable profile == stable keywords come from ? if you want them to be the same, you need to invent something that would make repoman checks fatals for broken deps rather than displaying non fatal warnings that nobody ever reads because it needs -d. also, you are missing some bug # for the 'broken deps' part. packages that have gained broken deps when the profile was marked 'dev', or that you committed with your profile.desc locally modified, do not count and are your fault actually...
