Description of problem: There is now a (long anticipated!) Guile 3.0 package in Fedora, however with the gnutls-guile package being built only against Guile 2.2 the network libraries are somewhat hobbled. Version-Release number of selected component (if applicable): gnutls-guile-3.7.2-2.fc35.x86_64 How reproducible: Always Steps to Reproduce: 1. dnf install gnutls-guile guile30 2. guile3.0 -c '(use-modules (gnutls))' Actual results: Backtrace: ... 3329:6 0 (resolve-interface (gnutls) #:select _ #:hide _ #:prefix …) ice-9/boot-9.scm:3329:6: In procedure resolve-interface: no code for module (gnutls) Expected results: No output (indicating the one-liner executed without throwing an error) Additional info:
@bob Is it necessary to provide gnutls_guile built with guile3.0 for Fedora35? I would prefer to not do this for f35 as I would have to create a new subpackage for it in order to not break the compatibility and maintain both versions of gnutls_guile (one built with guile2.2 and another built with guile3.0). The prefered way would be to not provide gnutls_guile built with guile3.0 on f35 and rather introduce gnutls_guile_v3 on new release of fedora. That way we would avoid a lot of friction.
Well, 'necessary' is a bit of a moving target. Anything TLS-related in Guile 3.0 is broken at the moment (including using any of the built-in libraries for e.g. HTTPS), but given that Guile seems to have a relatively small user base it may well be an acceptable trade-off to keep it that way until the next release (after all, Guile 3.0 in Fedora was a long time coming, too!). This probably isn't very helpful, but I think necessity in this instance really boils down to what level of functionality the maintainers are satisfied to provide. I would point out, though, that from what I've observed from the other Guile major version discussions (see [1] etc for instance) it seems that the intention is Guile 2.2 won't be disappearing from the Fedora distribution anytime soon. I would have thought that might necessitate supporting GnuTLS for multiple Guile versions in parallel. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1828124#c4
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Gnutls guile bindings have been moved to a separate package. Changing the component field.
It should be easier to build for multiple Guile versions now that the bindings have been split out of the GnuTLS tree, right?
Created attachment 1972398 [details] dual-build.patch If it helps at all, I've thrown together a rough diff for guile-gnutls.spec based on the setup I use for building other Guile stuff for multiple versions. I'm sure there's much better ways of doing this, but it's a start. (For future reference, the provided diff applies to git revision 0c93be24f7238e5d07efe1b61ac15f598fe23b36)