From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] --depclean and openrc
Date: Tue, 24 Sep 2024 18:15:38 +0000 [thread overview]
Message-ID: <ZvMBymZTSXNuYMZ0@MAC.fritz.box> (raw)
In-Reply-To: <3ae127a4-9aa0-4289-a6f8-e211277fa53c@gentoo.org>
Hello, Eli.
On Tue, Sep 24, 2024 at 11:24:14 -0400, Eli Schwartz wrote:
> On 9/24/24 8:34 AM, Alan Mackenzie wrote:
> >>> The context of this discussion was an implication that the Gentoo
> >>> maintainers wouldn't make a change "that made everyone's systems
> >>> suddenly break". I submitted a bug report about --depclean back in
> >>> the summer of 2021 (though I can't find that bug any more). I think
> >>> it was closed as not-a-bug.
> >> Whoever closed it was wrong, frankly.
> > I've found the bug. It was 803878. The developer who responded treated
> > my bug as though it were a request for personal support, and he
> > completely evaded my point that it was a bug in portage which should be
> > fixed. It was actually closed as TEST-REQUEST, whatever that means. The
> > bug was never addressed.
> The bug was confused about the issue at hand and lacking the full
> explanation of why it's an issue it could be understood why it was
> assumed to be a personal support request.
Whenever I get a confused bug report, the first thing I do is work out
what the problem really is, which often involves getting in touch with
the OP. That didn't happen with 803878 - the response to my initial
bug report occurred with 17 minutes of it being raised.
> It is not a bug in portage, which is part of the confusion here. It is a
> bug in virtual/service-manager.
That is clear now, it wasn't clear in 2021-06 when the bug was raised.
It is surely not the submitter's job to work out where in a system a bug
is caused, rather it's the job of the specialist handling the bug.
> I reopened the bug report, corrected the description, and assigned it.
Thanks! That's appreciated. It's looking like it's now going to get
fixed. :-)
> https://bugs.gentoo.org/803878
> --
> Eli Schwartz
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2024-09-24 18:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 20:14 [gentoo-user] Wayland! Beware of! Alan Mackenzie
2024-09-23 21:11 ` Eli Schwartz
2024-09-23 22:08 ` Alan Mackenzie
2024-09-23 22:54 ` Eli Schwartz
2024-09-24 11:30 ` [gentoo-user] --depclean and openrc [Was: Wayland! Beware of!] Alan Mackenzie
2024-09-24 11:40 ` Arsen Arsenović
2024-09-24 12:34 ` [gentoo-user] --depclean and openrc Alan Mackenzie
2024-09-24 15:24 ` Eli Schwartz
2024-09-24 18:15 ` Alan Mackenzie [this message]
2024-09-27 0:09 ` [gentoo-user] --depclean and openrc [Was: Wayland! Beware of!] Mitchell Dorrell
2024-09-24 15:15 ` Eli Schwartz
2024-09-24 18:53 ` Alan Mackenzie
2024-09-24 19:36 ` Eli Schwartz
2024-10-25 19:22 ` Alan Mackenzie
2024-10-26 3:10 ` Walter Dnes
2024-10-27 1:53 ` Eli Schwartz
2024-10-27 22:52 ` Alan Mackenzie
2024-10-27 23:14 ` Eli Schwartz
2024-09-25 0:32 ` Matt Jolly
2024-09-24 0:43 ` [gentoo-user] Wayland! Beware of! Michael Orlitzky
2024-09-24 0:52 ` Mitchell Dorrell
2024-09-24 1:13 ` Matt Jolly
2024-09-24 1:52 ` Eli Schwartz
2024-09-24 9:46 ` Mitchell Dorrell
2024-09-25 0:14 ` Matt Jolly
2024-09-24 10:05 ` Dr Rainer Woitok
2024-09-24 22:00 ` Walter Dnes
2024-09-25 1:42 ` Eli Schwartz
2024-09-25 10:00 ` Walter Dnes
2024-09-25 11:53 ` Arsen Arsenović
2024-09-25 22:21 ` Walter Dnes
2024-09-26 0:25 ` Eli Schwartz
2024-09-26 5:08 ` Walter Dnes
2024-09-26 19:18 ` James Cloos
2024-09-25 14:26 ` Eli Schwartz
2024-09-25 14:40 ` jay
2024-09-26 0:19 ` Michael Orlitzky
2024-09-23 21:12 ` Arsen Arsenović
2024-09-23 21:20 ` Wol
2024-09-23 22:53 ` karl
2024-09-24 7:10 ` Wols Lists
2024-09-24 18:32 ` What is what (Re: [gentoo-user] Wayland! Beware of!) karl
2024-09-24 23:44 ` Wols Lists
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=ZvMBymZTSXNuYMZ0@MAC.fritz.box \
--to=acm@muc.de \
--cc=gentoo-user@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