public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] Last rites: obsolete acct-* packages
Date: Mon, 17 Jul 2023 17:07:53 -0400	[thread overview]
Message-ID: <CAJ0EP43hJ79y2gYYRkS7RNrso0JkWpiT694AmjP6ofLUfbCpPg@mail.gmail.com> (raw)
In-Reply-To: <87sf9m9ta5.fsf@gentoo.org>

On Mon, Jul 17, 2023 at 4:27 PM Sam James <sam@gentoo.org> wrote:
> > Haven't we been keeping these because we still need to decide on a
> > policy about what to do with dead acct-*/* packages?
>
> Right. https://bugs.gentoo.org/781881 is still open. Flow could ping
> the QA team and ask if it should be closed, given the opinion there
> seems to be that there's no need to keep them, but I think it's wrong
> to do this pre-empting a policy decision, given it essentially forces
> the "don't keep them" path.

The bug has been open for several months without comment. If a policy
were going to materialize, I think it would have happened by now.

Forcing the issue by sending this last rites notice seems acceptable to me.


  reply	other threads:[~2023-07-17 21:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 19:43 [gentoo-dev] Last rites: obsolete acct-* packages Florian Schmaus
2023-07-17 20:21 ` [gentoo-dev] Re: [gentoo-dev-announce] " Matt Turner
2023-07-17 20:27   ` Sam James
2023-07-17 21:07     ` Mike Gilbert [this message]
2023-07-18  6:39       ` Ulrich Mueller
2023-07-18  8:22         ` Pacho Ramos
2023-07-18  8:42           ` Зураб Квачадзе
2023-07-18  8:54             ` Florian Schmaus
2023-07-18  8:59               ` Зураб Квачадзе
2023-07-18  9:05             ` Fabian Groffen
2023-07-18  9:56       ` Sam James
2023-07-18 11:58         ` Florian Schmaus
2023-07-18 13:08           ` Sam James
2023-07-18 13:15             ` Sam James

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