From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
Date: Sun, 27 Mar 2011 12:18:14 -0400 [thread overview]
Message-ID: <AANLkTikLssB6WnJtRKUh3Gv6vrfos5hj=er=aaPSjd-z@mail.gmail.com> (raw)
In-Reply-To: <4D8F4F93.6030507@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On Mar 27, 2011 11:01 AM, "Tomáš Chvátal" <scarabeus@gentoo.org> wrote:
> And how exactly you want to track the level of failure for the package?
> Since nobody is watching them already we usually don't know how much
> they fail until somebody tries to emerge them from dev team or notify QA
> by adding as CC to bug...
If a tree falls in the forest...does anybody care?
Broken packages that nobody notices don't cost us much. A tinderbox sweep
will id and tag them for cleaning eventually.
All I'm saying is that the problem is broken packages, so address those, m-n
or otherwise.
By all means be proactive about finding maintainers, but let's not go
purging working packages.
As far as how broken is too broken - if it causes the distro headaches,
address it. That could be blockers, or tons of bug reports, or whatever...
Rich
[-- Attachment #2: Type: text/html, Size: 1000 bytes --]
next prev parent reply other threads:[~2011-03-27 16:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110326055210.E906D20054@flycatcher.gentoo.org>
2011-03-27 4:45 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml Jeremy Olexa
2011-03-27 7:47 ` Nirbheek Chauhan
2011-03-27 10:29 ` Markos Chandras
2011-03-27 9:39 ` Nirbheek Chauhan
2011-03-27 13:04 ` Treeclean all maintainer-needed packages, was: " Chí-Thanh Christopher Nguyễn
2011-03-27 15:37 ` Ryan Hill
2011-03-27 13:30 ` Jeremy Olexa
2011-03-27 13:43 ` Nirbheek Chauhan
2011-03-27 19:17 ` Alec Warner
2011-03-27 19:40 ` Nirbheek Chauhan
2011-03-27 20:17 ` Alec Warner
2011-03-27 21:25 ` Nirbheek Chauhan
2011-03-27 23:34 ` Ryan Hill
2011-03-28 1:59 ` Donnie Berkholz
2011-03-27 20:44 ` Rich Freeman
2011-03-27 21:09 ` Nirbheek Chauhan
2011-03-28 1:58 ` Donnie Berkholz
2011-03-27 21:28 ` René 'Necoro' Neumann
2011-04-05 4:26 ` Jeroen Roovers
2011-04-05 10:58 ` Alec Warner
2011-04-05 15:08 ` Jeroen Roovers
2011-04-18 17:56 ` Andreas K. Huettel
2011-03-27 13:44 ` Rich Freeman
2011-03-27 14:54 ` Tomáš Chvátal
2011-03-27 16:18 ` Rich Freeman [this message]
2011-03-27 14:08 ` Maintainership offering; was: " René 'Necoro' Neumann
2011-03-27 19:05 ` Jeremy Olexa
2011-03-27 20:20 ` Proxy maintainership of app-misc/pwsafe, was " Christopher Head
2011-03-27 20:47 ` Nirbheek Chauhan
2011-03-27 20:55 ` René 'Necoro' Neumann
2011-03-27 20:55 ` David Abbott
2011-03-27 21:32 ` Nirbheek Chauhan
2011-03-29 17:50 ` Dirkjan Ochtman
2011-03-29 13:33 ` Jeroen Roovers
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='AANLkTikLssB6WnJtRKUh3Gv6vrfos5hj=er=aaPSjd-z@mail.gmail.com' \
--to=rich0@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