Bug 1231812
Summary: | git-cola-2.3 is available | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
Component: | git-cola | Assignee: | Kevin Kofler <kevin> | ||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rawhide | CC: | davvid, kevin, morckman | ||||
Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | 2.3-1.fc21 | Doc Type: | Enhancement | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-08-22 22:50:09 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Upstream Release Monitoring
2015-06-15 12:43:55 UTC
Failed to kick off scratch build. cmd: spectool -g /var/tmp/thn-6wUVXu/git-cola.spec return code: 22 stdout: Getting https://github.com/git-cola/git-cola/archive/vv2.2/git-cola-v2.2.tar.gz to ./git-cola-v2.2.tar.gz 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 100 138 0 138 0 0 254 0 --:--:-- --:--:-- --:--:-- 253 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found Latest upstream release: v2.2.1 Current version/release in rawhide: 2.1.2-1.fc23 URL: https://github.com/git-cola/git-cola 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-tvC9yN/git-cola.spec return code: 22 stdout: Getting https://github.com/git-cola/git-cola/archive/vv2.2.1/git-cola-v2.2.1.tar.gz to ./git-cola-v2.2.1.tar.gz 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 100 142 0 142 0 0 272 0 --:--:-- --:--:-- --:--:-- 272 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found Created attachment 1052580 [details]
patch for spec file
Tested on FC21, builds and runs fine.
Latest upstream release: v2.3 Current version/release in rawhide: 2.1.2-2.fc23 URL: https://github.com/git-cola/git-cola 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-xFermX/git-cola.spec return code: 22 stdout: Getting https://github.com/git-cola/git-cola/archive/vv2.3/git-cola-v2.3.tar.gz to ./git-cola-v2.3.tar.gz 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 100 138 0 138 0 0 271 0 --:--:-- --:--:-- --:--:-- 271 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found Unlike earlier releases, this one has a two-part (not three-part) version number. v2.3 instead of v2.1.2 like the previous one. Is that tripping up the downloader? It seems to be trying to grab ".../archive/vv2.3/..." -- it has two v's in the URL for some reason. Maybe the watch URL regex needs to be adjusted? The vv thing has been there all the time, see the previous bug comments. So it's not the version number that's causing the problem. Latest upstream release: 2.3 Current version/release in rawhide: 2.1.2-2.fc23 URL: https://github.com/git-cola/git-cola 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: sha256sum /var/tmp/thn-Sx_6Sf/100.0% return code: 1 stdout: stderr: sha256sum: /var/tmp/thn-Sx_6Sf/100.0%: No such file or directory The problem is that the default regex on Anitya (the upstream release monitoring system) assumes tags that are ONLY the version number, whereas you use v + version number. I fixed the regex on Anitya (I manually entered one that works) and flagged the package for an admin to delete the bogus version numbers with the "v". kkofler's git-cola-2.3-1.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=676607 Hi davvid,
the build.log shows these warnings during documentation generation:
> loading intersphinx inventory from http://docs.python.org/objects.inv...
> WARNING: intersphinx inventory 'http://docs.python.org/objects.inv' not fetchable due to <class 'urllib.error.URLError'>: <urlopen error [Errno -5] No address associated with hostname>
This is because Koji does not allow the builds to connect to the Internet. (It is also generally a bad idea to depend on online resources during the build.)
git-cola-2.3-1.fc23 has been submitted as an update for Fedora 23. https://admin.fedoraproject.org/updates/git-cola-2.3-1.fc23 git-cola-2.3-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/git-cola-2.3-1.fc22 git-cola-2.3-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/git-cola-2.3-1.fc21 Package git-cola-2.3-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing git-cola-2.3-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-13400/git-cola-2.3-1.fc22 then log in and leave karma (feedback). Thanks for the heads up, Kevin. I'll remove the intersphinx directives in the next release. It should be okay to ignore them for now, if possible. Does that fail the koji build, or just warn? In any case, it'll be fixed upstream shortly. It's just a warning. I did the builds and submitted the updates anyway. git-cola-2.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. git-cola-2.3-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. git-cola-2.3-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. |