unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Omar Polo <op@omarpolo.com>
To: 64271@debbugs.gnu.org
Subject: bug#64271: libasr is unmaintained upstream
Date: Sat, 24 Jun 2023 17:26:33 +0200	[thread overview]
Message-ID: <2JVPWGAPCL8FY.21UF0GAMAQ1YV@venera> (raw)

Hello,

I'm not a guix user so can't send patches, hope this is the correct
way to report issues however.

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.

The configure script still looks for `libasr' so that it continues to
build on OpenBSD, but on other systems it should use the bundled
libasr.  There's a configure flag --with-bundled-libasr to force the
usage of the bundled version.

Thanks,

Omar Polo


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




             reply	other threads:[~2023-06-25  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 15:26 Omar Polo [this message]
2023-06-30 17:17 ` bug#64271: libasr is unmaintained upstream Tobias Geerinckx-Rice via Bug reports for GNU Guix
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

  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=2JVPWGAPCL8FY.21UF0GAMAQ1YV@venera \
    --to=op@omarpolo.com \
    --cc=64271@debbugs.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. 
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).