Red Hat Bugzilla – Bug 510100
Revision number cannot be set (Feat. req. "Set a new revision #")
Last modified: 2010-05-05 10:56:58 EDT
It is currently not possible to set a revision number on a configuration file
Instead the revision number always increases by one (which is harcoded within
Having more than one spacewalk server brings up questions about how to let
configuration files run through the different development stages (simple
scenario: having development spacewalk and production spacewalk).
d = development
p = production
file a has revision 20 in spacewalk d
file a moves to spacewalk p with revision 1
I'd like to be able to set revision 20 on that file a on spacewalk p to provide
a certain grade of consistency between the spacewalks concerning the revision
of the file and the content of the file.
added to master
This bug has been fixed in Spacewalk 1.0.