Mailinglist Archive: zypp-devel (58 mails)

< Previous Next >
Re: [zypp-devel] where to maintaining zypp pacakges
  • From: Jano Kupec <jkupec@xxxxxxx>
  • Date: Tue, 30 Jun 2009 11:46:52 +0200
  • Message-id: <4A49DF0C.10303@xxxxxxx>
Michael Andres wrote:
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.

Of course, that's what i meant. I also meant, that if you submit
manually, you can expect that package be overwritten by hudson any time
soon.

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.

Yes, but that does not solve my case and it sounds to me as the same
effort as having separate zypp:Factory project and doing:

$ osc copypac zypp:Head foo zypp:Factory

in case zypp:Head has the desired version, and create your own source
package and 'osc ci' it to zypp:Factory in case there are problems with
Hudson. And always submit to factory from zypp:Factory, leaving
zypp:Head to live it's own life undisturbed.

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.

Sure

--
cheers,
jano


Ján Kupec
YaST team
---------------------------------------------------------(PGP)---
Key ID: 637EE901
Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901
---------------------------------------------------------(IRC)---
Server: irc.freenode.net
Nick: jniq
Channels: #zypp #yast #suse #susecz
---------------------------------------------------------(EOF)---

< Previous Next >
Follow Ups