public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Lastrite: games-fps/openarena
Date: Wed, 3 Mar 2010 11:56:20 -0800	[thread overview]
Message-ID: <b41005391003031156q22567ef4p878329a516d6c0d@mail.gmail.com> (raw)
In-Reply-To: <201003031859.59939.hwoarang@gentoo.org>

On Wed, Mar 3, 2010 at 8:59 AM, Markos Chandras <hwoarang@gentoo.org> wrote:
> On Wednesday 03 March 2010 18:29:13 Mark Loeser wrote:
>> Michael Sterrett <mr_bones_@gentoo.org> said:
>> > I've remove the mask for games-fps/openarena.
>> >
>> > The mask was done without consulting the games team.
>>
>> This is no reason to remove the mask.  The games team had more than
>> enough time to fix the package.  I'll be adding the mask back as the
>> package is vulnerable via multiple bundled libs and therefore shouldn't
>> be in the tree.  You can apply the patches if you want to keep it and
>> remove the mask at that time.
>>
>> Thanks,
> This thread is yet another proof that we need to introduce a "Upcoming
> masking" for unmaintained packages.

<sarcasm>

Shall I file those forms in triplicate and fax them to the main office sir?

</sarcasm>

Since amazingly I actually started the Treecleaners project; the
intent was actually to fix problems with packages.  Part of the
problem is that there are hundreds of packages in the tree and the
fixes vary in complexity so it is difficult to create hard-and-fast
rules on when to keep a package versus when to toss it.  One of the
things I like about masking is that it quickly gets people who
actually care about the package up to bat to fix it instead of leaving
it broken for months.  I realize maintainers do not exactly enjoy this
kind of poking, however when things have been left for long enough I
believe our options become a bit more limited (in this case, masking
for removal due to unfixed sec bugs.)

>
> Instead of first masking a package and then announce it, we can simply announce
> that we are gonna mask the package in 10days if there is no activity on the
> respective bug
> --
> Markos Chandras (hwoarang)
> Gentoo Linux Developer
> Web: http://hwoarang.silverarrow.org
>



  reply	other threads:[~2010-03-03 19:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 11:35 [gentoo-dev] Lastrite: games-fps/openarena Samuli Suominen
2010-03-03 11:32 ` Joshua Saddler
2010-03-03 11:55   ` Tomáš Chvátal
2010-03-03 12:58     ` [gentoo-dev] " Ryan Hill
2010-03-03 13:09       ` Samuli Suominen
2010-03-03 16:03         ` Michael Sterrett
2010-03-03 16:29           ` Mark Loeser
2010-03-03 16:59             ` Markos Chandras
2010-03-03 19:56               ` Alec Warner [this message]
2010-03-04 18:17 ` [gentoo-dev] Re: [gentoo-dev-announce] " Victor Ostorga
2010-03-05 13:17   ` Ben de Groot
2010-03-05 14:22     ` Markos Chandras
2010-03-05 15:06       ` Ben de Groot
2010-03-05 15:23         ` Markos Chandras
2010-03-05 16:38           ` Ben de Groot

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=b41005391003031156q22567ef4p878329a516d6c0d@mail.gmail.com \
    --to=antarus@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