% build.py --tag-release should just figure out whether or not you want a
% minor or major release. It became apparent that for any given
% sub-project we only really allow one type (major or minor) so the code
% now will figure out which to do based on some metadata in
% build.py.props. (if it's required, if not specified we assume make
% tag-release)
$ ~/rhn/spacewalk/rel-eng/bin/build.py --tag-release
Traceback (most recent call last):
File "/home/michael/rhn/spacewalk/rel-eng/bin/build.py", line 26, in ?
CLI().main()
File
"/home/michael/rhn/spacewalk/rel-eng/bin/../lib/spacewalk/releng/cli.py",
line 136, in main
tagger.run(options)
File
"/home/michael/rhn/spacewalk/rel-eng/bin/../lib/spacewalk/releng/tagger.py",
line 57, in run
self._tag_release()
File
"/home/michael/rhn/spacewalk/rel-eng/bin/../lib/spacewalk/releng/tagger.py",
line 63, in _tag_release
self._check_today_in_changelog()
File
"/home/michael/rhn/spacewalk/rel-eng/bin/../lib/spacewalk/releng/tagger.py",
line 88, in _check_today_in_changelog
raise Exception("No changelog entry found: '* %s %s <%s>'" % (
Exception: No changelog entry found: '* Tue Dec 16 2008 Michael Mraka
<[email protected]>'
Well, the exception is self-explanatory.
But the traceback makes bad look and feel :).
--
Michael Mráka
Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
