Description of problem: current package URL information contains broken link (it probably changed and now points to "nothing") "URL : http://qt.digia.com/Product/Qt-Core-Features--Functions/Developer-Tools/" I tried to file this bug report using rekonq and it failed ... (not related), and now I noticed that this URL has two '-' in one place, looked interesting, I tried without one, and it works! BROKEN! http://qt.digia.com/Product/Qt-Core-Features--Functions/Developer-Tools/" WORKS! http://qt.digia.com/Product/Qt-Core-Features-Functions/Developer-Tools/ Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.yum info qt-creator or go to https://apps.fedoraproject.org/packages/qt-creator ... 2. go to URL/Homepage 3. Actual results: "Ooops! Content not found The content you were looking for was not found." Expected results: Additional info:
Thanks for reporting this, fixed in git [1]. Will be part of the next update. [1] http://pkgs.fedoraproject.org/cgit/qt-creator.git/commit/?id=0ba6ed54138d1533690299bc3cc4ee750e56bb85
qt-creator-3.0.1-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/qt-creator-3.0.1-1.fc20
qt-creator-3.0.1-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/qt-creator-3.0.1-1.fc19
Package qt-creator-3.0.1-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing qt-creator-3.0.1-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-2124/qt-creator-3.0.1-1.fc19 then log in and leave karma (feedback).
qt-creator-3.0.1-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
qt-creator-3.0.1-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.