From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: 46602@debbugs.gnu.org
Subject: bug#46602: Removing OpenSSL 1.0
Date: Tue, 20 Jul 2021 21:55:45 +0300 [thread overview]
Message-ID: <YPccMSqkLO0N4exj@3900XT> (raw)
In-Reply-To: <YO3FK55jKaZc3g75@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Tue, Jul 13, 2021 at 12:54:03PM -0400, Leo Famulari wrote:
> Here are my notes on the users of the openssl-1.0 package:
>
> > File: web-browsers.scm
>
> dillo:
> Does not build with current OpenSSL
> Status? https://www.dillo.org/Plans.html
> No dependents
This one confuses me. I was able to build dillo with both openssl and
openssl-1.0, but I was unable to open that page with either version.
> > File: rust.scm
> > File: crates-io.scm
>
> For the Rust bootstrap, we can keep openssl-1.0 as a hidden-package.
> Help wanted dealing with the crates that depend on openssl-1.0.
>
I can poke those I guess, see what we can drop openssl-1.0 as an input
for and see if anything breaks.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-07-20 18:57 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 [this message]
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
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=YPccMSqkLO0N4exj@3900XT \
--to=efraim@flashner.co.il \
--cc=46602@debbugs.gnu.org \
--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).