Description of problem: when running $ tito release --all I get following result Will release to the following targets: koji Checking for tag [spacewalk-reports-1.9.1-1] in git repo [ssh://tkasparek.org/git/spacewalk.git/] Releasing to target: koji Working in: /tmp/tito/release-spacewalk-reports-bf3bb2b426a8fcb1830b48f121c0f019895156afNDeNbX Traceback (most recent call last): File "/usr/bin/tito", line 23, in <module> CLI().main(sys.argv[1:]) File "/usr/lib/python2.7/site-packages/tito/cli.py", line 94, in main return module.main(argv) File "/usr/lib/python2.7/site-packages/tito/cli.py", line 623, in main no_build=self.options.no_build) TypeError: release() got an unexpected keyword argument 'no_build' Version-Release number of selected component (if applicable): tito-0.4.10-1.fc17.noarch How reproducible: deterministic Steps to Reproduce: 1. $ tito release --all Actual results: traceback Expected results: normal functionality
Same for me in Fedora16. tito-0.4.9-1.fc16.noarch works fine, while tito-0.4.10-1.fc16 fails with the same traceback as in #Description.
0.4.11 on it's way to Koji and http://repos.fedorapeople.org/repos/dgoodwin/tito/
tito-0.4.11-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/tito-0.4.11-1.fc17
tito-0.4.11-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/tito-0.4.11-1.el6
tito-0.4.11-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/tito-0.4.11-1.fc18
tito-0.4.11-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/tito-0.4.11-1.fc16
Reopening, since NEXTRELEASE, the issue is fixed in rawhide.
tito-0.4.11-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
tito-0.4.11-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
tito-0.4.11-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.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.