Bug 1998399 - Symlink essential to -guile subpackage distributed in -guile-devel subpackage
Summary: Symlink essential to -guile subpackage distributed in -guile-devel subpackage
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: maildir-utils
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jani Juhani Sinervo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-27 04:01 UTC by bob
Modified: 2022-11-10 22:28 UTC (History)
2 users (show)

Fixed In Version: maildir-utils-1.8.11-1.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-10 22:28:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description bob 2021-08-27 04:01:16 UTC
Description of problem:
The Guile bindings for mu search for a shared library named "libguile-mu.so" in the system ld path(s). The binary itself is distributed as part of maildir-utils-guile, but the symlink with the required name is distributed in maildir-utils-guile-devel (which contains no other files).

Version-Release number of selected component (if applicable):
maildir-utils-guile-1.4.15-1.fc34.x86_64, although looking at src.fp.o this appears to be an issue in Rawhide, too.

How reproducible:
Always.

Steps to Reproduce:
1. `dnf install maildir-utils-guile'
2. Set up mu.
3. `guile2.2 -c '(use-modules (mu))'

Actual results:
In mu.scm:
     87:0  1 (_)
In unknown file:
           0 (load-extension "libguile-mu" "mu_guile_init")

ERROR: In procedure load-extension:
In procedure dynamic-link: file: "libguile-mu", message: "file not found"

Expected results:
No output, indicating the import ran without failure.

Comment 1 Ben Cotton 2022-05-12 15:32:40 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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 '34'.

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 34 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.

Comment 2 Ben Cotton 2022-08-09 13:37:51 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 3 Fedora Update System 2022-10-29 21:24:50 UTC
FEDORA-2022-274c37f67d has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-274c37f67d

Comment 4 Fedora Update System 2022-10-30 19:22:22 UTC
FEDORA-2022-274c37f67d has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-274c37f67d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-274c37f67d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2022-11-10 22:28:06 UTC
FEDORA-2022-274c37f67d has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


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