Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1032588
| Summary: | python-warlock-1.3.0 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | python-warlock | Assignee: | Alan Pevec (Fedora) <apevec> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | apevec, cstratak, lbalhar, mhroncok, mrunge, p, torsava |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-warlock-1.3.0-1.fc26, python-warlock-1.3.0-1.fc25 | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-29 09:56:27 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1285816, 1333770 | ||
| Attachments: | |||
|
Description
Upstream Release Monitoring
2013-11-20 12:41:22 UTC
Latest upstream release: 1.2.0 Current version/release in rawhide: 1.0.1-3.fc23 URL: https://pypi.python.org/pypi/warlock 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. spectool was unable to grab new sources old source: warlock-1.0.1-460080e.tar.gz old sha256: 7af204c6b57f5c6c1184e1cee964ec48a926f27cee57a30ca864b686a4b09e81 new source: ./warlock-1.2.0-460080e.tar.gz new sha256: 7af204c6b57f5c6c1184e1cee964ec48a926f27cee57a30ca864b686a4b09e81 Upstream, this software supports Python 3. Please provide a Python 3 package for Fedora. According to the Python packaging guidelines [0], software must be packaged for Python 3 if upstream supports it. The guidelines give detailed information on how to do this, and even provide an example spec file [1]. The current best practice is to provide subpackages for the two Python versions (called "Common SRPM" in the guidelines). Alternatively, if nothing depends on your Python2 package, you can just switch to Python 3 entirely. It's ok to do this in Rawhide only, however, it would be greatly appreciated if you could push it to Fedora 24 as well. If anything is unclear, or if you need any kind of assistance with the porting, you can ask on IRC (#fedora-python on Freenode), or reply here. We'll be happy to help! [0] https://fedoraproject.org/wiki/Packaging:Python [1] https://fedoraproject.org/wiki/Packaging:Python#Example_common_spec_file Created attachment 1165255 [details]
Update to 1.2.0 and Python 3 support
Scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=14394942 Also tested in mock. Latest upstream release: 1.3.0 Current version/release in rawhide: 1.0.1-4.fc24 URL: https://pypi.python.org/pypi/warlock 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. Based on the information from anitya: https://release-monitoring.org/project/4086/ Patching or scratch build for python-warlock-1.0.1 failed. Created attachment 1176047 [details] Rebase-helper rebase-helper-debug.log log file. See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues. Patches were not touched. All were applied properly Hello Charalampos. You have some mess in subpackages summary: "WTForms integration for peewee models". Also, could you please rebase this patch and try to build this package with the newest version 1.3.0? Yep that was a mistake from my part. Changing it. Created attachment 1184550 [details]
python 3 subpackage
Applying: Update to 1.3.0, provide a python 3 subpackage and modernize SPEC error: patch failed: python-warlock.spec:3 error: python-warlock.spec: patch does not apply Patch failed at 0001 Update to 1.3.0, provide a python 3 subpackage and modernize SPEC The copy of the patch that failed is found in: .git/rebase-apply/patch When you have resolved this problem, run "git am --continue". If you prefer to skip this patch, run "git am --skip" instead. To restore the original branch and stop patching, run "git am --abort". Created attachment 1184581 [details]
rebased patch
http://koji.fedoraproject.org/koji/taskinfo?taskID=15033753 http://koji.fedoraproject.org/koji/taskinfo?taskID=15033763 churchyard's python-warlock-1.3.0-1.fc26 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=785776 Thanks for the patch and build, is targeting f25 enough or f24 backport is required? Hi Alan, f25 is enough. Repos are synched so did some more testing in mock. Everything works correct. |