From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: 72840@debbugs.gnu.org
Subject: [bug#72840] Orphaned packages
Date: Tue, 17 Sep 2024 14:21:15 +0200 [thread overview]
Message-ID: <m1r09izd1g.fsf@fastmail.net> (raw)
In-Reply-To: <80f8b603ecd73cb9f46b1ea43797e143f16d2f17.1724785788.git.ludo@gnu.org>
Hi Andreas (et al.),
Debian has the status of "orphaned" packages for the situations that you
describe. Maybe Guix should have that as well? The main interest I see
is keeping a list of "software we had but can't handle any more",
ideally with a pointer to the last working state in Guix, e.g. the last
commit for which CI could build the package. I'd even like such packages
to show up in answers to "guix search", so that I know the difference
between "not packaged yet" and "tough case we gave up on".
> if during one month nobody steps in to carry out the update, that is
> telling.
I don't know on which time scales other Guix users live, but for me, one
month is the average delay between two "guix pull". In other words, one
month is my notion of "immediately" when it comes to Guix.
Cheers,
Konrad.
next prev parent reply other threads:[~2024-09-17 12:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 19:13 [bug#72839] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section Ludovic Courtès
2024-09-02 11:53 ` [bug#72840] " pelzflorian (Florian Pelz)
2024-09-05 21:26 ` bug#72840: " Ludovic Courtès
2024-09-05 21:31 ` [bug#72840] [PATCH RFC v2] " Ludovic Courtès
2024-09-11 7:04 ` Maxim Cournoyer
2024-09-11 10:11 ` [bug#72840] [PATCH RFC v3] " Ludovic Courtès
2024-09-12 0:40 ` Maxim Cournoyer
2024-09-23 22:11 ` [bug#72840] [PATCH RFC v4] " Ludovic Courtès
2024-09-24 16:32 ` Greg Hogan
2024-09-25 8:47 ` Andreas Enge
2024-10-02 16:20 ` [bug#72840] [PATCH RFC] DRAFT " Ludovic Courtès
2024-10-12 17:54 ` bug#72840: " Ludovic Courtès
2024-09-11 10:11 ` [bug#72840] " Ludovic Courtès
2024-09-11 18:30 ` Noé Lopez via Guix-patches via
2024-09-13 17:23 ` Ludovic Courtès
2024-09-11 19:49 ` [bug#72840] Deprecation policy Konrad Hinsen
2024-09-13 17:32 ` [bug#72840] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section Ludovic Courtès
2024-09-15 8:22 ` Konrad Hinsen
[not found] ` <66e1e26e.050a0220.2c8e9.9533SMTPIN_ADDED_BROKEN@mx.google.com>
2024-09-12 15:39 ` Greg Hogan
2024-09-13 16:41 ` [bug#72839] Using RFC process? (was Re: [bug#72839] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section.) Simon Tournier
2024-09-13 17:38 ` [bug#72840] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section Ludovic Courtès
2024-09-13 18:11 ` [bug#72839] bug#72840: " Simon Tournier
2024-09-13 20:57 ` [bug#72840] " indieterminacy
2024-09-23 21:44 ` Ludovic Courtès
2024-09-17 12:21 ` Konrad Hinsen [this message]
2024-09-23 21:47 ` Ludovic Courtès
2024-09-24 5:21 ` Konrad Hinsen
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=m1r09izd1g.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=72840@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.