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: Mon, 17 Sep 2012 09:22:50 -0300 [thread overview]
Message-ID: <20120917092250.61d9f75a@gentoo.org> (raw)
In-Reply-To: <201209162206.19807.vapier@gentoo.org>
On Sun, 16 Sep 2012 22:06:19 -0400
Mike Frysinger <vapier@gentoo.org> wrote:
> On Sunday 16 September 2012 11:01:00 Alexis Ballier wrote:
> > 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...
>
> wrong. if i'm version bumping a package and i see broken amd64-fbsd
> deps, that is not my problem. sounds like i'll simply de-keyword it
> in the future and let someone else pick up the pieces.
why do you want to treat amd64-fbsd different than other arches ?
just to make the work of those that want to maintain that arch a pain ?
you know, standard procedure is to drop keywords and file a bug when a
new dep comes in a new version. deps that are _already_ broken should
not happen because, heh, the profile is marked stable... in case this
happens there's nothing sane to do, better use repoman --force and file
an urgent bug to the arch team.
> do a repoman on the tree. there are multiple packages coming back
> right now with broken amd64-fbsd deps.
if people do not file bugs and think it's fine to commit packages with
broken deps, or silently dekeyword just because they can like you
suggested in the first paragraph, this will not change anytime soon.
and no thanks, i wont be doing repoman checks on the tree, i had been
doing this for x86-fbsd, spending hours fixing the mess i could, and had
to re-do it every couple of months because every other dev was
committing packages with broken deps.
now, would you please file bugs when you see such broken packages and
let the keywording level be sanitized ? thanks
next prev parent reply other threads:[~2012-09-17 12:24 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
2012-09-17 2:06 ` Mike Frysinger
2012-09-17 12:22 ` Alexis Ballier [this message]
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=20120917092250.61d9f75a@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