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