From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Omar Polo <op@omarpolo.com>
Cc: 64271@debbugs.gnu.org, 64271-done@debbugs.gnu.org
Subject: bug#64271: libasr is unmaintained upstream
Date: Fri, 30 Jun 2023 19:17:13 +0200 [thread overview]
Message-ID: <87cz1c7to4.fsf@nckx> (raw)
In-Reply-To: <2JVPWGAPCL8FY.21UF0GAMAQ1YV@venera>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
Omar Polo 写道:
> I'm not a guix user so can't send patches, hope this is the
> correct
> way to report issues however.
Yep.
> The upstream libasr-portable repository was archived, as the
> project
> was unmaintained (and unmaintenable in some sense) for some
> time:
>
> https://github.com/OpenSMTPD/libasr/
>
> OpenSMTPD (its only consumer I guess) doesn't depend on it
> anymore, it
> should be built with the bundled version that was updated.
Removed libasr in commit 902a48e0d3ce4a1983a6d3f71472639a8e59c48f.
> P.S.: looking at the recipe for OpenSMTPD I noticed the comment
> "reccomended, and supports e.g. ECDSA". While it's true
> that
> it's reccomended to build with LibreSSL, ec keys should
> work
> just as fine with OpenSSL. The only issue is the combo
> OpenSSL
> 3.x + LibreTLS 3.7.0 due to a known regression that will
> be
> fixed in a upcoming release (I hope) since LibreSSL' tls
> did it:
> https://github.com/libressl/openbsd/commit/318ad8e73e
OpenSMTPd temporarily(…) builds with openssl with commit
023ff651462f70004c7a92b19fd072ee3138e5a2, so the comment is gone.
Thanks!
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2023-06-30 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 15:26 bug#64271: libasr is unmaintained upstream Omar Polo
2023-06-30 17:17 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2023-06-30 17:32 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-07-01 8:26 ` Omar Polo
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=87cz1c7to4.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=64271-done@debbugs.gnu.org \
--cc=64271@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=op@omarpolo.com \
/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.