From: "Leo Famulari" <leo@famulari.name>
To: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"Sharlatan Hellseher" <sharlatanus@gmail.com>
Cc: "Christopher Baines via Development of GNU Guix and the GNU
System distribution." <guix-devel@gnu.org>
Subject: Re: Question on the process of packge withdrawal
Date: Mon, 27 Feb 2023 14:55:50 -0500 [thread overview]
Message-ID: <3c70b3bb-911f-44c9-8bbc-319acd90cbb9@app.fastmail.com> (raw)
In-Reply-To: <87v8jnjam5.fsf@gmail.com>
On Mon, Feb 27, 2023, at 12:12, Maxim Cournoyer wrote:
> I think packages removal should go to the patch tracker, with a CC to
> guix-devel to give more visibility to let time for all parties to
> comment or find a solution (perhaps a maintained fork exists, etc.)
I agree that removal should go through the patch tracker. However, for a case like this one, I don't think there's any reason to wait very long before pushing
From the users' point of view, the package is effectively already gone, because it does not build.
It's confusing and frustrating for the list of available packages in the UI to include broken packages, so I suggest that speedy removal is best.
next prev parent reply other threads:[~2023-02-27 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 20:11 Question on the process of packge withdrawal Sharlatan Hellseher
2023-02-27 17:12 ` Maxim Cournoyer
2023-02-27 19:55 ` Leo Famulari [this message]
2023-02-28 10:30 ` Simon Tournier
2023-02-28 16:26 ` bokr
2023-02-28 17:16 ` Simon Tournier
2023-03-01 9:40 ` Bengt Richter
2023-02-28 14:57 ` Andreas Enge
2023-02-28 17:10 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c70b3bb-911f-44c9-8bbc-319acd90cbb9@app.fastmail.com \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=sharlatanus@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).