From: zimoun <zimon.toutoune@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: Does Guix provide security support for Python2? For how long?
Date: Fri, 15 Jan 2021 21:06:05 +0100 [thread overview]
Message-ID: <CAJ3okZ0mKMFz03gU_e5Wfd2AMH-nGWFEKTDnd5QbVybAHkHBzQ@mail.gmail.com> (raw)
In-Reply-To: <87czy65dbi.fsf@disroot.org>
Hi,
On Fri, 15 Jan 2021 at 18:18, Jorge P. de Morais Neto
<jorge+list@disroot.org> wrote:
> Em [2021-01-15 sex 18:07:40+0100], zimoun escreveu:
>
> > As far as I know, Guix provides the security support that upstream
> > releases.
>
> I too suppose so in general. But I would like a more authoritative
> answer for the specific case of Python2. And, in fact, this should be
> publicly documented---in the manual or in the website, as well as the
> description of the python2 package and maybe also in the description of
> all python2-.* packages.
As far I know, Python 2 is End Of Life and not supported upstream.
Therefore, if your question is: will Guix people fix Python 2
security? Then the answer is no.
However, please indicate if an organization is still maintaining
Python 2 and maybe Guix could package their release.
> > Using the Guix time-machine, the code that works now should work
> > exactly the same in the future, even if Python 2 is removed in the
> > future Guix releases. Does it make sense?
>
> The problem is that OfflineIMAP is Internet software, and therefore, I
> believe, it is important to have security support for it (including its
> dependencies).
In this case, please consider to switch from OfflineIMAP to something else.
Guix is about packaging, not supporting security from deprecated upstream.
All the best,
simon
prev parent reply other threads:[~2021-01-15 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 16:00 Does Guix provide security support for Python2? For how long? Jorge P. de Morais Neto
2021-01-15 17:07 ` zimoun
2021-01-15 17:18 ` Jorge P. de Morais Neto
2021-01-15 18:17 ` dario
2021-01-15 18:28 ` Jorge P. de Morais Neto
2021-01-15 19:56 ` Leo Famulari
2021-01-15 20:06 ` zimoun [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
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=CAJ3okZ0mKMFz03gU_e5Wfd2AMH-nGWFEKTDnd5QbVybAHkHBzQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@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.
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).