Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#76434 - [nim] nimble requires OpenSSL 1.1.1

Attached to Project: Community Packages
Opened by Ho-Yon Mak (hoyon) - Saturday, 05 November 2022, 16:26 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 02 May 2023, 01:31 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After the system wide upgrade to OpenSSL 3, nimble no longer works and immediately fails with this error:

$ nimble
could not import: SSL_get_peer_certificate

Although it builds successfully with OpenSSL 3, it is non-functional and still requires OpenSSL 1.1.1 to work.

Installing the openssl-1.1 package makes nimble work again. Can this be added as a package dependency?

See also: https://github.com/nim-lang/Nim/issues/19604

Thanks!
This task depends upon

Closed by  Toolybird (Toolybird)
Tuesday, 02 May 2023, 01:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  nim 1.6.10-2
Comment by loqs (loqs) - Saturday, 05 November 2022, 16:43 GMT
If you rebuild nim with the attached diff applied which updates nim to 1.6.8 and applies changes queued for 1.6.9 including full OpenSSL 3 support does that resolve the issue?
   PKGBUILD.diff (1.6 KiB)
Comment by Ho-Yon Mak (hoyon) - Saturday, 05 November 2022, 17:06 GMT
Yes applying the patch seems to work with OpenSSL 3 correctly even after uninstalling the openssl-1.1 package. Thanks!
Comment by Ho-Yon Mak (hoyon) - Wednesday, 23 November 2022, 12:55 GMT
Nim 1.6.10 has been released which adds support for OpenSSL 3 https://nim-lang.org/blog/2022/11/23/version-1610-released.html

Bumping this package to 1.6.10 will resolve this bug.

Loading...