[zypp-devel] where to maintaining zypp pacakges
Hi there, since we are opening Factory and should maintain our packages in joint OBS project, i'd like to bring up the following issue. We've been using zypp:Head to automatically submit packages from master HEADs of our git repos, after each commit (or in some regular intervals? i don't know exactly) if they pass some validation. We don't use it to submit manually. This seems to me that this particular project is not suitable for submitting packages to Factory and we should keep it this way. Having said that, we should create a new project for this purpose, and create the zypp packages as links from openSUSE:Factory project, and mark them as 'devel'. How about doing this in the 'zypp' project (there are no packages currently), or create new 'zypp:Factory' project? BTW: is the zypp:svn project still used? If not, we can delete it. -- 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)---
On Friday 19 June 2009 11:29:57 Jano Kupec wrote:
Hi there,
since we are opening Factory and should maintain our packages in joint OBS project, i'd like to bring up the following issue.
We've been using zypp:Head to automatically submit packages from master HEADs of our git repos, after each commit (or in some regular intervals?
Yes, after each commit a build and testsuite are triggered. If they pass, the package is auto-submitted to zypp::Head.
i don't know exactly) if they pass some validation. We don't use it to submit manually.
This seems to me that this particular project is not suitable for submitting packages to Factory and we should keep it this way. Having
This project is, and IMO should stay, the only source for submission to Factory. It serves as a cache, and we submitt to Factory if the update stack is in sync. I.e. we file an osc submitreqest from zypp::Head to openSUSE:Factory. Somewhat special is just the case that the OBS project is automatically fed by submissions to the git repos. But that's fine, isn't it?
BTW: is the zypp:svn project still used? If not, we can delete it.
AFAIK it's no longer used. yast:svn used to build against this, but that's probably history. So we could delete it. -- 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
Michael Andres wrote:
On Friday 19 June 2009 11:29:57 Jano Kupec wrote:
Hi there,
since we are opening Factory and should maintain our packages in joint OBS project, i'd like to bring up the following issue.
We've been using zypp:Head to automatically submit packages from master HEADs of our git repos, after each commit (or in some regular intervals?
Yes, after each commit a build and testsuite are triggered. If they pass, the package is auto-submitted to zypp::Head.
i don't know exactly) if they pass some validation. We don't use it to submit manually.
This seems to me that this particular project is not suitable for submitting packages to Factory and we should keep it this way. Having
This project is, and IMO should stay, the only source for submission to Factory. It serves as a cache, and we submitt to Factory if the update stack is in sync. I.e. we file an osc submitreqest from zypp::Head to openSUSE:Factory.
Somewhat special is just the case that the OBS project is automatically fed by submissions to the git repos. But that's fine, isn't it?
Exactly. The problem is that in one point you can have a set of packages that you want to submit to Factory, but in the next minute a change from git master HEAD can appear there in some of the packages that you did not want there. Or is this not a problem? Don't we care what will go to Factory as long as it passes the tests? One (not so big) problem i see with this is for example with versioning. This way we will often submit packages having changes but without increasing the version, or packages with changes made after the version was increased. If user reports a bug against particular libzypp version, you can't be sure if the bug is still in that version (maybe a few commits fixing this are already included in that version, but _after_ it the version was changed). Other than this, i don't see any problems with zypp:Head. Just that we'll never submit packages there via 'osc ci', but in fact via git (at least those automatically submitted). But that's ok with me. Any external contributions must finally go via git anyway, since we are the upstream.
BTW: is the zypp:svn project still used? If not, we can delete it.
AFAIK it's no longer used. yast:svn used to build against this, but that's probably history. So we could delete it.
Let's do it (we'll someone please do it, i don't have the rights IIRC). -- 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)---
On Friday 19 June 2009 13:25:45 Jano Kupec wrote:
Exactly. The problem is that in one point you can have a set of packages that you want to submit to Factory, but in the next minute a change from git master HEAD can appear there in some of the packages that you did not want there. Or is this not a problem? Don't we care what will go to Factory as long as it passes the tests?
Well, we should not submitt to git:master, if our change isn't a candidate for Factory. And if more than one package is affected, we usually talk to each other.
One (not so big) problem i see with this is for example with versioning. This way we will often submit packages having changes but without increasing the version, or packages with changes made after the version was increased.
This depends on how we maintain the version number when checking into git:master. Actually there are several people using zypp::Head to test new features (even on openSuSE-11.1). So we should try to maintain reasonable version numbers. Basically you are of course right. But as long as just we 4 are involved, I don't feel urgent need. But let's wait until Duncan is back from vacation. Maybe we can tune Hudson to feed zypp::Head with each commit and do snapshots for zypp::Factory on demand. Maybe we find some (half) automated solution, that also gives feedback to the git repo (e.g by tagging versions scheduled and accepted for factory).
AFAIK it's no longer used. yast:svn used to build against this, but that's probably history. So we could delete it.
Let's do it (we'll someone please do it, i don't have the rights IIRC).
Duncan? Stano? Coolo? (delete obs yast:svn) -- 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
Dne pátek 19 Červen 2009 15:28:16 Michael Andres napsal(a):
On Friday 19 June 2009 13:25:45 Jano Kupec wrote:
Exactly. The problem is that in one point you can have a set of packages that you want to submit to Factory, but in the next minute a change from git master HEAD can appear there in some of the packages that you did not want there. Or is this not a problem? Don't we care what will go to Factory as long as it passes the tests?
Well, we should not submitt to git:master, if our change isn't a candidate for Factory. And if more than one package is affected, we usually talk to each other.
One (not so big) problem i see with this is for example with versioning. This way we will often submit packages having changes but without increasing the version, or packages with changes made after the version was increased.
This depends on how we maintain the version number when checking into git:master. Actually there are several people using zypp::Head to test new features (even on openSuSE-11.1). So we should try to maintain reasonable version numbers.
Basically you are of course right. But as long as just we 4 are involved, I don't feel urgent need. But let's wait until Duncan is back from vacation.
Maybe we can tune Hudson to feed zypp::Head with each commit and do snapshots for zypp::Factory on demand. Maybe we find some (half) automated solution, that also gives feedback to the git repo (e.g by tagging versions scheduled and accepted for factory).
AFAIK it's no longer used. yast:svn used to build against this, but that's probably history. So we could delete it.
Let's do it (we'll someone please do it, i don't have the rights IIRC).
Duncan? Stano? Coolo? (delete obs yast:svn)
Why? YaST:Head is the devel project we submit to, and one needs to submit manually. YaST:Svn is being submitted to automatically and thus contains more unstable code. YaST is a little bigger project than ZYPP and I don't think that the ZYPP approach can work well (at least not as long as we submit directly to trunk). Instead it can make sense to build YaST against zypp:Head? Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Friday 19 June 2009 15:37:00 Jiri Srain wrote:
Dne pátek 19 Červen 2009 15:28:16 Michael Andres napsal(a):
On Friday 19 June 2009 13:25:45 Jano Kupec wrote:
Exactly. The problem is that in one point you can have a set of packages that you want to submit to Factory, but in the next minute a change from git master HEAD can appear there in some of the packages that you did not want there. Or is this not a problem? Don't we care what will go to Factory as long as it passes the tests?
Well, we should not submitt to git:master, if our change isn't a candidate for Factory. And if more than one package is affected, we usually talk to each other.
One (not so big) problem i see with this is for example with versioning. This way we will often submit packages having changes but without increasing the version, or packages with changes made after the version was increased.
This depends on how we maintain the version number when checking into git:master. Actually there are several people using zypp::Head to test new features (even on openSuSE-11.1). So we should try to maintain reasonable version numbers.
Basically you are of course right. But as long as just we 4 are involved, I don't feel urgent need. But let's wait until Duncan is back from vacation.
Maybe we can tune Hudson to feed zypp::Head with each commit and do snapshots for zypp::Factory on demand. Maybe we find some (half) automated solution, that also gives feedback to the git repo (e.g by tagging versions scheduled and accepted for factory).
AFAIK it's no longer used. yast:svn used to build against this, but that's probably history. So we could delete it.
Let's do it (we'll someone please do it, i don't have the rights IIRC).
Duncan? Stano? Coolo? (delete obs yast:svn)
Why?
!!! Sorry zypp:svn is the one to be deleted! -- 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
On Fri, Jun 19, 2009 at 03:37:00PM +0200, Jiri Srain wrote:
Dne pátek 19 Červen 2009 15:28:16 Michael Andres napsal(a):
Duncan? Stano? Coolo? (delete obs yast:svn)
Why?
YaST:Head is the devel project we submit to, and one needs to submit manually. YaST:Svn is being submitted to automatically and thus contains more unstable code.
BTW, YaST:SVN is NOT automated and so is a little stale now. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Jano Kupec wrote:
Or is this not a problem? Don't we care what will go to Factory as long as it passes the tests?
In theory that should encourage us to trust our tests and make them reliable. However, in the case you need to submit to factory something that is not the last thing in the obs project, IIRC the build service also has revisions, so one can submit an older revision to factory. Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Duncan Mac-Vicar P. wrote:
Jano Kupec wrote:
Or is this not a problem? Don't we care what will go to Factory as long as it passes the tests?
In theory that should encourage us to trust our tests and make them reliable.
However, in the case you need to submit to factory something that is not the last thing in the obs project, IIRC the build service also has revisions, so one can submit an older revision to factory.
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... 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 zypp:Head, and if somebody decides now to submit zypper to Factory from zypp:Head he might end up overwriting the newer zypper with an older one. -- 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)---
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
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)---
On Tuesday 30 June 2009 11:46:52 Jano Kupec wrote:
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.
Maybe we have slightly different scenarios in mind. If I'd actually need to submitt omitting Hudson, then I'd upload and submitt the package. I don't mind if Hudson later overwrites it. If Hudson uploads, it passed all the tests and is a candidate for the next submission. But as I said, if you feel that more comfortable with an additional repo, convince Duncan and Michael(mls). We all should agree on how to submitt. for P in $PACKS; do - osc sr create zypp:Head $P openSUSE:Factory + osc copypac zypp:Head $P zypp:Factory + osc sr create zypp:Factory $P openSUSE:Factory done -- 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
participants (5)
-
Duncan Mac-Vicar P. -
Jano Kupec -
Jiri Srain -
Martin Vidner -
Michael Andres