From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: ChangeLog profiles.desc
Date: Sun, 16 Sep 2012 12:01:00 -0300 [thread overview]
Message-ID: <20120916120100.670c0578@gentoo.org> (raw)
In-Reply-To: <201209151848.03566.vapier@gentoo.org>
On Sat, 15 Sep 2012 18:47:56 -0400
Mike Frysinger <vapier@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...
next prev parent reply other threads:[~2012-09-16 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120828002311.815E120987@flycatcher.gentoo.org>
2012-09-11 18:06 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: ChangeLog profiles.desc Alexis Ballier
2012-09-15 22:47 ` Mike Frysinger
2012-09-16 15:01 ` Alexis Ballier [this message]
2012-09-17 2:06 ` Mike Frysinger
2012-09-17 12:22 ` Alexis Ballier
2012-09-19 5:38 ` Mike Frysinger
2012-09-19 12:14 ` Alexis Ballier
2012-09-17 14:57 ` Alexis Ballier
2012-09-19 5:40 ` Mike Frysinger
2012-09-19 12:07 ` Alexis Ballier
[not found] <20130107000233.12D482171D@flycatcher.gentoo.org>
2013-02-19 15:19 ` Alexis Ballier
2013-02-19 19:22 ` Matt Turner
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=20120916120100.670c0578@gentoo.org \
--to=aballier@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