From: zimoun <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>,
Efraim Flashner <efraim@flashner.co.il>,
46602-done@debbugs.gnu.org
Subject: bug#46602: Removing OpenSSL 1.0
Date: Tue, 31 Aug 2021 11:27:45 +0200 [thread overview]
Message-ID: <865yvmotf2.fsf@gmail.com> (raw)
In-Reply-To: <YRmRP3NlC2jULask@jasmine.lan>
Hi Leo,
On Sun, 15 Aug 2021 at 18:12, Leo Famulari <leo@famulari.name> wrote:
> With commit 12099eac1b161d364be923451d27d7d739d0f14d, nothing is using
> openssl-1.0 except for the Rust bootstrap.
>
> If I understand correctly, the plan is to "upgrade" that bootstrap path,
> and eventually we won't need a package of openssl-1.0 at all.
>
> I'm marking this bug as done.
Cool! Thanks for the work.
On a side sad note, I point that 168 packages not named ’rust’ depends
somehow on ’rust’.
$ guix refresh -l -e '(@@ (gnu packages tls) openssl-1.0)' \
| sed 's/ /\n/g' | grep '@' \
| grep -v rust | wc -l
168
And I am surprised that ’mplayer’ or ’guile-gnunet’ appears there.
Well, I am also surprised that “guix graph” does not report it.
--8<---------------cut here---------------start------------->8---
$ guix graph --path guile-gnunet -e '(@@ (gnu packages tls) openssl-1.0)'
guix graph: erreur : pas de chemin de « guile-gnunet@0.0-1.d12167a » à « openssl@1.0.2u »
--8<---------------cut here---------------end--------------->8---
Maybe I miss something somewhere.
Cheers,
simon
next prev parent reply other threads:[~2021-08-31 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 21:26 bug#46602: Removing OpenSSL 1.0 Leo Famulari
2021-02-25 19:01 ` zimoun
2021-07-13 16:54 ` Leo Famulari
2021-07-13 23:03 ` Leo Famulari
2021-07-20 18:55 ` Efraim Flashner
2021-07-20 19:06 ` Efraim Flashner
2021-08-04 1:04 ` Leo Famulari
2021-08-04 1:10 ` Leo Famulari
2021-08-04 1:27 ` Leo Famulari
2021-08-15 22:12 ` Leo Famulari
2021-08-31 9:27 ` zimoun [this message]
2021-08-31 9:57 ` Efraim Flashner
2021-08-31 10:31 ` zimoun
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=865yvmotf2.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=46602-done@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=leo@famulari.name \
/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).