Description of problem: Attempting to install octave-dicom on Fedora 28 returns an error due to unmet dependencies. At least one of these dependencies is not available on Fedora 28. Version-Release number of selected component (if applicable): 0.2.0-1.fc28 How reproducible: always Steps to Reproduce: 1. Attempt to install octave-dicom using dnf install. Actual results: An error saying that "nothing provides libgdcmCommon.so.2.6()(64bit)" prints. octave-dicom is not installed. Expected results: octave-dicom is installed. Additional info: libgdcmCommon.so.2.6 is provided by gdcm-2.6.5-13.fc27.x86_64.rpm and older versions available on fc26 and fc25. It is not provided by a package for fc28. The other libgdcm shared object files required by octave-dicom also depend on fc25/fc26/fc27 versions of gdcm. These are: dependency: libgdcmDICT.so.2.6()(64bit) dependency: libgdcmDSED.so.2.6()(64bit) dependency: libgdcmIOD.so.2.6()(64bit) dependency: libgdcmMSFF.so.2.6()(64bit)
It just needs to be recompiled against gdcm 2.8.x. Confirmed with dgoerger/workstation-extras COPR for F28: https://copr.fedorainfracloud.org/coprs/dgoerger/workstation-extras/build/787497/ All I did was rebuild the F29 SRPM for F28. Can someone with build privileges in Koji push a rebuild of octave-dicom for the F28 branch, to build against gdcm 2.8? Thanks! === original error $ sudo dnf install -y octave-dicom Error: Problem: conflicting requests - nothing provides libgdcmCommon.so.2.6()(64bit) needed by octave-dicom-0.2.0-1.fc28.x86_64 === with COPR dgoerger/workstation-extras $ sudo dnf install -y octave-dicom Last metadata expiration check: 0:00:00 ago on Mon 13 Aug 2018 09:45:41 AM EDT. Dependencies resolved. =========================================================================== Package Arch Version Repository Size =========================================================================== Installing: octave-dicom x86_64 0.2.0-2.fc28 dgoerger-workstation-extras 189 k Transaction Summary =========================================================================== Install 1 Package Total download size: 189 k Installed size: 1.0 M Downloading Packages: octave-dicom-0.2.0-2.fc28.x86_64.rpm 370 kB/s | 189 kB 00:00 --------------------------------------------------------------------------- Total 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : octave-dicom-0.2.0-2.fc28.x86_64 1/1 Running scriptlet: octave-dicom-0.2.0-2.fc28.x86_64 1/1 Verifying : octave-dicom-0.2.0-2.fc28.x86_64 1/1 Installed: octave-dicom.x86_64 0.2.0-2.fc28 Complete!
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.