libasr is unmaintained upstream

  • Done
  • quality assurance status badge
Details
2 participants
  • Tobias Geerinckx-Rice
  • Omar Polo
Owner
unassigned
Submitted by
Omar Polo
Severity
normal
O
O
Omar Polo wrote on 24 Jun 2023 17:26
(address . bug-guix@gnu.org)
2JVPWGAPCL8FY.21UF0GAMAQ1YV@venera
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:


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:
T
T
Tobias Geerinckx-Rice wrote on 30 Jun 2023 19:17
(name . Omar Polo)(address . op@omarpolo.com)
87cz1c7to4.fsf@nckx
Omar Polo ???
Toggle quote (4 lines)
> I'm not a guix user so can't send patches, hope this is the
> correct
> way to report issues however.

Yep.

Toggle quote (11 lines)
> 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.

Toggle quote (13 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCZJ8PCw0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15AWgBAOETa41vPHSZj/zF6UnXfJom8DqHPaHwx5wxBkIT
6gaaAQDxMCRpoHRwjYV5NIV26PQ5hpJ6JeWIWw+5ItFi1tzjAQ==
=SKsP
-----END PGP SIGNATURE-----

T
T
Tobias Geerinckx-Rice wrote on 30 Jun 2023 19:32
878rc07t1h.fsf@nckx
Tobias Geerinckx-Rice via Bug reports for GNU Guix ???
Toggle quote (4 lines)
> OpenSMTPd temporarily(…) builds with openssl with commit
> 023ff651462f70004c7a92b19fd072ee3138e5a2, so the comment is
> gone.

Heh. I see you released -p1 literally while I was typing that :-)

Thanks!

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCZJ8SOg0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15D1YBAJHRzHn9JnFzXZdwBcxue/QbvVwLWWMDndsXdZ5s
F9P+AP9k0cfXLPy0DR3LJE3zs+sp3qsKxNMpIRTVawVjkKHbCQ==
=oDEC
-----END PGP SIGNATURE-----

O
O
Omar Polo wrote on 1 Jul 2023 10:26
(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)
353B9INOR9WTE.24SM7AVOLZ4HG@venera
On 2023/06/30 19:32:57 +0200, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
Toggle quote (7 lines)
> Tobias Geerinckx-Rice via Bug reports for GNU Guix ???
> > OpenSMTPd temporarily(…) builds with openssl with commit
> > 023ff651462f70004c7a92b19fd072ee3138e5a2, so the comment is
> > gone.
>
> Heh. I see you released -p1 literally while I was typing that :-)

thanks for taking care of removing asr and updating opensmtpd!

Toggle quote (3 lines)
> Thanks!
>
> T G-R
?
Your comment

This issue is archived.

To comment on this conversation send an email to 64271@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 64271
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch