Description of problem: koji-download-scratch uses hardcoded Koji hub URL: 'http://kojipkgs.fedoraproject.org/work/' This makes it unusable with other Koji instances. Please make Koji hub URL configurable, preferably on command line. Version-Release number of selected component (if applicable): 0.5.0-3
(In reply to Mikolaj Izdebski from comment #0) > Description of problem: > koji-download-scratch uses hardcoded Koji hub URL: > 'http://kojipkgs.fedoraproject.org/work/' I should clarify that both hub URL and workspace URL are hardcoded and both should be configurable.
Commited upstream in commit afe1746
fedora-review-0.5.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fedora-review-0.5.1-1.fc18
fedora-review-0.5.1-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/fedora-review-0.5.1-1.el6
fedora-review-0.5.1-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/fedora-review-0.5.1-1.fc19
Package fedora-review-0.5.1-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedora-review-0.5.1-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-23340/fedora-review-0.5.1-1.fc20 then log in and leave karma (feedback).
fedora-review-0.5.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.
fedora-review-0.5.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
fedora-review-0.5.1-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
fedora-review-0.5.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.