unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: "Bonface Munyoki K." <me@bonfacemunyoki.com>,
	help-guix@gnu.org, Pjotr Prins <pjotr2020@thebird.nl>
Subject: Re: What to do when a package is removed upstream
Date: Tue, 20 Apr 2021 12:24:05 -0400	[thread overview]
Message-ID: <YH8AJRb1W3e6f1Tb@jasmine.lan> (raw)
In-Reply-To: <8735vle4ld.fsf@nckx>

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

On Tue, Apr 20, 2021 at 10:35:10AM +0200, Tobias Geerinckx-Rice wrote:
> You can use an ‘inferior’[0] Guix if you don't mind the entire closure of
> python2-flask* being frozen in the past -- possibly including
> incompatibilities or known security vulnerabilities.
> 
> I don't know what their inclusion & maintenance criteria are, but another
> approach is to add the removed packages to the guix-past[1] channel.

It might be nice to document these options somehow.

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

  reply	other threads:[~2021-04-20 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  8:24 What to do when a package is removed upstream Bonface Munyoki K.
2021-04-20  8:35 ` Tobias Geerinckx-Rice
2021-04-20 16:24   ` Leo Famulari [this message]
2021-04-23  9:53   ` Bonface Munyoki K.
2021-04-23 12:06     ` Ricardo Wurmus
2021-04-23 13:26       ` Bonface Munyoki K.

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=YH8AJRb1W3e6f1Tb@jasmine.lan \
    --to=leo@famulari.name \
    --cc=help-guix@gnu.org \
    --cc=me@bonfacemunyoki.com \
    --cc=me@tobias.gr \
    --cc=pjotr2020@thebird.nl \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).