Latest upstream release: 2.5.3 Current version/release in rawhide: 2.3.2-19.fc24 URL: http://gqrx.dk/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.
Failed to kick off scratch build. cmd: spectool -g /var/tmp/thn-NTWPCV/gqrx.spec return code: 22 stdout: Getting http://downloads.sourceforge.net/gqrx/gqrx-2.5.3.tar.xz to ./gqrx-2.5.3.tar.xz stderr: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found
It seems they have switched to github: https://github.com/csete/gqrx
Created attachment 1131305 [details] Patch for spec file I have attached a patch, apply this patch simply by running: git apply <file> This patch has been tested by running "fedpkg --dist f23 mockbuild" since gnuradio was broken in rawhide at the time
*** Bug 1297041 has been marked as a duplicate of this bug. ***
daveo's gqrx-2.5.3-1.fc25 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=748586
gqrx-2.5.3-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-f00be7f01e
daveo's gqrx-2.5.3-2.fc25 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=748673
gqrx-2.5.3-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e62495ce64
gqrx-2.5.3-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-8309ca56ba
Is there going to be also F22 update?
(In reply to Adam Pribyl from comment #10) > Is there going to be also F22 update? I will see what I can do. May I ask why you are still on f22?
gqrx-2.5.3-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e62495ce64
(In reply to Dave Olsthoorn from comment #11) > (In reply to Adam Pribyl from comment #10) > > Is there going to be also F22 update? > > I will see what I can do. > > May I ask why you are still on f22? Gives Fedora we use a half year of extra "testing".
gqrx-2.5.3-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8309ca56ba
gqrx-2.5.3-2.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-a4059d6c83
gqrx-2.5.3-2.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-a4059d6c83
gqrx-2.5.3-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
gqrx-2.5.3-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
gqrx-2.5.3-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.