Description of problem: When trying to install "gqrx" in Fedora 36, the installation fails with: Error: Problem: package gqrx-2.15.8-4.fc36.x86_64 requires libgnuradio-osmosdr.so.0.2.0()(64bit), but none of the providers can be installed - conflicting requests - nothing provides libgnuradio-funcube.so.3.10.0()(64bit) needed by gr-osmosdr-0.2.3-18.20210217gita100eb02.fc36.x86_64 Version-Release number of selected component (if applicable): gqrx-2.15.8-4.fc36.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Use latest Fedora 36 compose. 2. Run: sudo dnf install gqrx
Proposed as a Freeze Exception for 36-final by Fedora user asciiwolf using the blocker tracking app because: This issue prevents gqrx from being installed and also blocks system upgrade to F36.
Discussed in ticket: https://pagure.io/fedora-qa/blocker-review/issue/758 The decision to classify this bug as an AcceptedFreezeException was made: "We usually accept FTBFS/FTI fixes in during the Freeze."
Has this been already handled? I cannot reproduce the issue on latest F36: [lruzicka@vseved Hudba]$ LANG=en_US.utf-8 sudo dnf install gqrx --setopt tsflags=test Last metadata expiration check: 2:39:06 ago on Thu 14 Apr 2022 11:42:41 AM CEST. Dependencies resolved. =============================================================================================================================== Package Architecture Version Repository Size =============================================================================================================================== Installing: gqrx x86_64 2.15.8-4.fc36 fedora 663 k Installing dependencies: SoapySDR x86_64 0.8.1-3.fc36 fedora 159 k airspyone_host x86_64 1.0.9-13.20180615gitbfb66708.fc36 fedora 65 k boost-program-options x86_64 1.76.0-9.fc36 fedora 108 k boost-serialization x86_64 1.76.0-9.fc36 fedora 132 k codec2 x86_64 1.0.1-2.fc36 fedora 639 k gnuradio x86_64 3.10.1.0-1.fc36 fedora 3.2 M gr-funcube x86_64 1.0.0-11.20220130gitbf71b979.fc36 updates-testing 169 k gr-iqbal x86_64 0.38.2-11.20210210gitfbee239a.fc36 fedora 103 k gr-osmosdr x86_64 0.2.3-21.20210217gita100eb02.fc36 updates-testing 356 k hackrf x86_64 2018.01.1-11.fc36 fedora 60 k hidapi x86_64 0.11.2-2.fc36 fedora 46 k libosmo-dsp x86_64 0.3-17.fc36 fedora 25 k lpcnetfreedv x86_64 0.2-11.fc36 fedora 7.3 M python3-gnuradio x86_64 3.10.1.0-1.fc36 fedora 3.0 M python3-numpy-f2py x86_64 1:1.22.0-2.fc36 fedora 261 k python3-pyopengl x86_64 3.1.5-8.fc36 fedora 2.6 M python3-pyqtgraph noarch 0.12.3-2.fc36 fedora 1.0 M python3-scipy x86_64 1.8.0-3.fc36 fedora 18 M python3-thrift x86_64 0.14.0-6.fc36 fedora 143 k qwt-qt5 x86_64 6.1.5-6.fc36 fedora 574 k spdlog x86_64 1.9.2-3.fc36 fedora 133 k thrift x86_64 0.14.0-6.fc36 fedora 1.6 M uhd x86_64 4.1.0.5-5.fc36 fedora 4.7 M volk x86_64 2.5.0-3.fc36 fedora 494 k Transaction Summary =============================================================================================================================== Install 25 Packages Total size: 45 M Installed size: 164 M DNF will only download packages, install gpg keys, and check the transaction. Is this ok [y/N]: y Downloading Packages: [SKIPPED] SoapySDR-0.8.1-3.fc36.x86_64.rpm: Already downloaded [SKIPPED] airspyone_host-1.0.9-13.20180615gitbfb66708.fc36.x86_64.rpm: Already downloaded [SKIPPED] boost-program-options-1.76.0-9.fc36.x86_64.rpm: Already downloaded [SKIPPED] boost-serialization-1.76.0-9.fc36.x86_64.rpm: Already downloaded [SKIPPED] codec2-1.0.1-2.fc36.x86_64.rpm: Already downloaded [SKIPPED] gnuradio-3.10.1.0-1.fc36.x86_64.rpm: Already downloaded [SKIPPED] gqrx-2.15.8-4.fc36.x86_64.rpm: Already downloaded [SKIPPED] gr-iqbal-0.38.2-11.20210210gitfbee239a.fc36.x86_64.rpm: Already downloaded [SKIPPED] hackrf-2018.01.1-11.fc36.x86_64.rpm: Already downloaded [SKIPPED] hidapi-0.11.2-2.fc36.x86_64.rpm: Already downloaded [SKIPPED] libosmo-dsp-0.3-17.fc36.x86_64.rpm: Already downloaded [SKIPPED] lpcnetfreedv-0.2-11.fc36.x86_64.rpm: Already downloaded [SKIPPED] python3-gnuradio-3.10.1.0-1.fc36.x86_64.rpm: Already downloaded [SKIPPED] python3-numpy-f2py-1.22.0-2.fc36.x86_64.rpm: Already downloaded [SKIPPED] python3-pyopengl-3.1.5-8.fc36.x86_64.rpm: Already downloaded [SKIPPED] python3-pyqtgraph-0.12.3-2.fc36.noarch.rpm: Already downloaded [SKIPPED] python3-scipy-1.8.0-3.fc36.x86_64.rpm: Already downloaded [SKIPPED] python3-thrift-0.14.0-6.fc36.x86_64.rpm: Already downloaded [SKIPPED] qwt-qt5-6.1.5-6.fc36.x86_64.rpm: Already downloaded [SKIPPED] spdlog-1.9.2-3.fc36.x86_64.rpm: Already downloaded [SKIPPED] thrift-0.14.0-6.fc36.x86_64.rpm: Already downloaded [SKIPPED] uhd-4.1.0.5-5.fc36.x86_64.rpm: Already downloaded [SKIPPED] volk-2.5.0-3.fc36.x86_64.rpm: Already downloaded [SKIPPED] gr-funcube-1.0.0-11.20220130gitbf71b979.fc36.x86_64.rpm: Already downloaded [SKIPPED] gr-osmosdr-0.2.3-21.20210217gita100eb02.fc36.x86_64.rpm: Already downloaded Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Complete! The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'.
It also did work fine for me on my Fedora 36 clean installation from latest compose iso, but once I upgraded the system to latest packages, the same error started happening. I will try looking into this later today when I have more time.
This should be resolved once the https://bodhi.fedoraproject.org/updates/FEDORA-2022-0c1e340840 get into the stable. Sorry for problems, I haven't counted with the freeze :). It's specialized software targeting specific group of users (usually very technically skilled). I think it should be minor annoyance with easy workaround (e.g. by installation of the update) so I think it shouldn't block the f36 release.
Thanks! I can confirm that it fixes the issue. P.S. Don't worry, this bz was not proposed as a Blocker, just FreezeException.
How long will it take for the update to go into stable? I see that it has already been submitted for stable by bodhi two weeks ago.
(In reply to Daniel Rusek from comment #7) > How long will it take for the update to go into stable? I see that it has > already been submitted for stable by bodhi two weeks ago. No idea, it seems there is f36 freeze now which should help stabilize the release.
>No idea, it seems there is f36 freeze now which should help stabilize the release. That's true, but this bz was accepted as a FreezeException.
(In reply to Daniel Rusek from comment #9) > >No idea, it seems there is f36 freeze now which should help stabilize the release. > > That's true, but this bz was accepted as a FreezeException. It seems I cannot do anything about it at the moment, the update is proposed to the stable.
Jardo, you have to mark the bodhi update as fixing this bug, otherwise our QA tooling is not aware of it and therefore we don't know that that particular update should be pushed through freeze.
FEDORA-2022-0c1e340840 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0c1e340840
(In reply to Kamil Páral from comment #11) > Jardo, you have to mark the bodhi update as fixing this bug, otherwise our > QA tooling is not aware of it and therefore we don't know that that > particular update should be pushed through freeze. Sorry, this makes sense, fixed :)
Setting VERIFIED per Bodhi comments.
FEDORA-2022-0c1e340840 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.