public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] Last rites: obsolete acct-* packages
Date: Tue, 18 Jul 2023 14:15:42 +0100	[thread overview]
Message-ID: <87pm4pnyuu.fsf@gentoo.org> (raw)
In-Reply-To: <87wmyxnz5m.fsf@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1959 bytes --]


Sam James <sam@gentoo.org> writes:

> [[PGP Signed Part:Undecided]]
>
> Florian Schmaus <flow@gentoo.org> writes:
>
>> [[PGP Signed Part:Undecided]]
>> On 18/07/2023 11.56, Sam James wrote:
>>> Mike Gilbert <floppym@gentoo.org> writes:
>>> 
>>>> 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.
>>> Pinging someone rather than "forcing the issue" as a first-step is
>>> customary.
>>
>> I am sorry, but it seems that I have to clarify something.
>>
>> First, I have "pinged someone."
>
> Ping on IRC (in #gentoo-qa, or could PM me), or again on the bug?
>
> Someone asked the QA team to make a decision. We haven't yet, as I'd
> forgot about it. It seems wrong to then just pretend that didn't happen.
>
> At least try to get it resolved on that end by pinging again / asking us?

Just to be super duper clear: it's fine with me if we just move on and
don't keep the packages, but I think a quick /msg #gentoo-qa "hey guys,
nothing seems to be happening with the bug, do you mind if we just close
it?" wouldn't have gone amiss.

That is _all_ I'm asking for here.

And then when we get onto talk of "incentives" and "illegitimate shadow
policies", I become very confused indeed.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

      reply	other threads:[~2023-07-18 13:17 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
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 [this message]

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=87pm4pnyuu.fsf@gentoo.org \
    --to=sam@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