Bug 1891329 - libOpenMS.so is not in search path, but needed
Summary: libOpenMS.so is not in search path, but needed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openms
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Antonio T. sagitter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-25 18:07 UTC by david08741
Modified: 2020-11-03 01:29 UTC (History)
1 user (show)

Fixed In Version: openms-2.6.0-2.fc33 openms-2.6.0-2.fc31 openms-2.6.0-2.fc32
Clone Of:
Environment:
Last Closed: 2020-11-03 00:59:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description david08741 2020-10-25 18:07:31 UTC
Description of problem:
libOpenMS.so is not in search path, but needed

Version-Release number of selected component (if applicable):
openms-2.5.0-2.fc31.x86_64

How reproducible:
always

Steps to Reproduce:
1.run FileConverter

Actual results:
FileConverter: error while loading shared libraries: libOpenMS.so: cannot open shared object file: No such file or directory


Expected results:
FileConverter runs

Additional info:
same issue in f32
workaround:
LD_LIBRARY_PATH=/usr/lib64/OpenMS/ FileConverter

Comment 1 Antonio T. sagitter 2020-10-25 18:23:50 UTC
Thank you for reporting.
I'm fixing now...

Comment 2 Fedora Update System 2020-10-25 22:09:35 UTC
FEDORA-2020-ef40d045f2 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ef40d045f2

Comment 3 Fedora Update System 2020-10-25 22:09:35 UTC
FEDORA-2020-709b8ffa38 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-709b8ffa38

Comment 4 Fedora Update System 2020-10-25 22:09:36 UTC
FEDORA-2020-503e8b3e58 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-503e8b3e58

Comment 5 Fedora Update System 2020-10-26 01:18:39 UTC
FEDORA-2020-709b8ffa38 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-709b8ffa38`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-709b8ffa38

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

Comment 6 Fedora Update System 2020-10-26 01:37:38 UTC
FEDORA-2020-503e8b3e58 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-503e8b3e58`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-503e8b3e58

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

Comment 7 Fedora Update System 2020-10-26 01:45:10 UTC
FEDORA-2020-ef40d045f2 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ef40d045f2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ef40d045f2

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

Comment 8 Fedora Update System 2020-11-03 00:59:02 UTC
FEDORA-2020-709b8ffa38 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2020-11-03 01:21:03 UTC
FEDORA-2020-ef40d045f2 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2020-11-03 01:29:41 UTC
FEDORA-2020-503e8b3e58 has been pushed to the Fedora 32 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.