On Monday 29 June 2009 18:38:47 Jano Kupec wrote:
Duncan Mac-Vicar P. wrote:
True. But it's no good, since i just discovered another case :O) satsolver has submit deadline on Friday before the milestone release. zypper has the deadline the next Monday. Now, during the Monday mls decides to break the build :O) and since zypper can't be submitted manually to zypp:Head, it probably won't make it to the milestone.
Who said that zypper can't be submitted manually? AFAIK you can, you just should not under normal circumstances. If Hudson breaks, or someone breaks the build on Hudson like in the above scenario, you can submitt manually. All we have to do is to take care that our actions and Hudsons automated actions fit together. It might be possible to 'tell' Hudson to stay with a specific version; maybe by tagging a specific revision as frozen in git. Hudson could use the frozen revision instead of matser:HEAD then. And/or we ivnent a lock file in zypp:Head that prevents Hudson from uploading new versions of a package, if the package is locked.
Of course i can submit from my own home project (that's what i'm gonna do now), but then we have an inconsistency between Factory and
We should IMO head for a solution, not for some workaround. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org