Bug 23416 - libgnutls does not include the ssl libraries. This makes it impossible to for exmaple compile slrn with ssl
Summary: libgnutls does not include the ssl libraries. This makes it impossible to for...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-09 20:38 CEST by w unruh
Modified: 2018-08-28 14:52 CEST (History)
2 users (show)

See Also:
Source RPM: gnutls-3.5.13-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description w unruh 2018-08-09 20:38:37 CEST
Description of problem:
The packaging of the libgnutls* libraries does not include the ssl or openssl libraries. This seems to have been a deliberate decision since Mga5. Could the ssl libraries of gnutls be reinstated? They are needed for example in using the ssl/secure option in slrn for example. 


Version-Release number of selected component (if applicable):3.5.13-1


How reproducible: Always. /lib64/libgnutls-openssl.so* does not exist and no attempt on my part at recompiling seems to help this. 


Steps to Reproduce:
1.
2.
3.
Comment 1 Marja Van Waes 2018-08-09 22:33:33 CEST
* Mon Jan 11 2016 luigiwalser <luigiwalser> 3.4.8-1.mga6
+ Revision: 921784
<snip>
- disable openssl compatibility library by default

I don't remember why that was, CC'ing David Walser.

CC: (none) => luigiwalser, marja11

Comment 2 David Walser 2018-08-09 23:15:20 CEST
They are not built anymore as of 3.4.0 (when I made that change, please quote the whole changelog entry) according to the upstream changelog.  It's no different in Fedora (in fact they had it disabled even before that).

Maybe slrn can use openssl instead?  I found a similar issue in different software:
https://github.com/suleman1971/boinctui/issues/13
Comment 3 Marja Van Waes 2018-08-28 14:52:47 CEST
OK, thx David.

Closing as invalid then, since this is an upstream change.

@ w unruh

I hope David Walser's suggestion (using openssl instead) works for you.

Resolution: (none) => INVALID
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.