[opensuse-packaging] New Source Service mode actived!
build.opensuse.org is running now with the new source service mode. We recommend to upgrade to osc 0.132 version as available in openSUSE:Tools project if you work with source services. The difference to the old way source service were handled is that with the new mode, no "source service" commits are generated. This means, the history just contains the commits done by the user, which makes things like revision diffs much easier. The source service result is handled as an internal commit, like with source links. Builds are still done with those internal commits. A manual service run trigger is handled as commit by the user, so it is part of the history. This solves also the blocking of commits (403 errors) during a service run. Michael and Adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
On Thu, Jun 09, 2011 at 06:11:48PM +0200, Adrian Schröter wrote:
build.opensuse.org is running now with the new source service mode.
We recommend to upgrade to osc 0.132 version as available in openSUSE:Tools project if you work with source services.
The difference to the old way source service were handled is that with the new mode, no "source service" commits are generated. This means, the history just contains the commits done by the user, which makes things like revision diffs much easier. The source service result is handled as an internal commit, like with source links. Builds are still done with those internal commits.
A manual service run trigger is handled as commit by the user, so it is part of the history.
This solves also the blocking of commits (403 errors) during a service run.
Nice job. But I'm getting the build system error "services only work on branches" when trying to link in a package that contains a branch (i.e. the osc package itself into openSUSE:Tumbleweed). Is this just a side-affect of a package link that I shouldn't do for source packages, or a bug somewhere else? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thu, Jun 09, 2011 at 10:19:42AM -0700, Greg KH wrote:
But I'm getting the build system error "services only work on branches" when trying to link in a package that contains a branch (i.e. the osc package itself into openSUSE:Tumbleweed).
Is this just a side-affect of a package link that I shouldn't do for source packages, or a bug somewhere else?
That's a limitation of the way source services are implemented currently. Source services run on the commited files. Unlike branches with contain the complete filelist, links just contain the _link element and some patches. That's not enough to run a source service, so they are forbidden for links. This limitation existed since source services were added, it has nothing to do with the recent change. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Thursday, 9. June 2011, 10:19:42 schrieb Greg KH:
On Thu, Jun 09, 2011 at 06:11:48PM +0200, Adrian Schröter wrote:
build.opensuse.org is running now with the new source service mode.
We recommend to upgrade to osc 0.132 version as available in openSUSE:Tools project if you work with source services.
The difference to the old way source service were handled is that with the new mode, no "source service" commits are generated. This means, the history just contains the commits done by the user, which makes things like revision diffs much easier. The source service result is handled as an internal commit, like with source links. Builds are still done with those internal commits.
A manual service run trigger is handled as commit by the user, so it is part of the history.
This solves also the blocking of commits (403 errors) during a service run.
Nice job.
But I'm getting the build system error "services only work on branches" when trying to link in a package that contains a branch (i.e. the osc package itself into openSUSE:Tumbleweed).
This has nothing todo with this change, it was always not supported. But I enabled project wide services in openSUSE:Tools to validate all sources, like we plan to do for Factory.
Is this just a side-affect of a package link that I shouldn't do for source packages, or a bug somewhere else?
A not yet supported case. Michael is just about to add code to support also this situation.
thanks,
greg k-h
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
Am Friday, 10. June 2011, 10:24:58 schrieb Adrian Schröter:
Am Thursday, 9. June 2011, 10:19:42 schrieb Greg KH:
On Thu, Jun 09, 2011 at 06:11:48PM +0200, Adrian Schröter wrote:
build.opensuse.org is running now with the new source service mode.
We recommend to upgrade to osc 0.132 version as available in openSUSE:Tools project if you work with source services.
The difference to the old way source service were handled is that with the new mode, no "source service" commits are generated. This means, the history just contains the commits done by the user, which makes things like revision diffs much easier. The source service result is handled as an internal commit, like with source links. Builds are still done with those internal commits.
A manual service run trigger is handled as commit by the user, so it is part of the history.
This solves also the blocking of commits (403 errors) during a service run.
Nice job.
But I'm getting the build system error "services only work on branches" when trying to link in a package that contains a branch (i.e. the osc package itself into openSUSE:Tumbleweed).
This has nothing todo with this change, it was always not supported.
But I enabled project wide services in openSUSE:Tools to validate all sources, like we plan to do for Factory.
Is this just a side-affect of a package link that I shouldn't do for source packages, or a bug somewhere else?
A not yet supported case.
Michael is just about to add code to support also this situation.
This is now active. However, you osc package in openSUSE:Tumbleweed is currently a wild mix of a simple link (not using a branch) plus manual committed files of an old version of osc. Either remove everything in the package beside the _link file or make it a branch. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fri, Jun 10, 2011 at 12:02:28PM +0200, Adrian Schröter wrote:
Am Friday, 10. June 2011, 10:24:58 schrieb Adrian Schröter:
Am Thursday, 9. June 2011, 10:19:42 schrieb Greg KH:
On Thu, Jun 09, 2011 at 06:11:48PM +0200, Adrian Schröter wrote:
build.opensuse.org is running now with the new source service mode.
We recommend to upgrade to osc 0.132 version as available in openSUSE:Tools project if you work with source services.
The difference to the old way source service were handled is that with the new mode, no "source service" commits are generated. This means, the history just contains the commits done by the user, which makes things like revision diffs much easier. The source service result is handled as an internal commit, like with source links. Builds are still done with those internal commits.
A manual service run trigger is handled as commit by the user, so it is part of the history.
This solves also the blocking of commits (403 errors) during a service run.
Nice job.
But I'm getting the build system error "services only work on branches" when trying to link in a package that contains a branch (i.e. the osc package itself into openSUSE:Tumbleweed).
This has nothing todo with this change, it was always not supported.
But I enabled project wide services in openSUSE:Tools to validate all sources, like we plan to do for Factory.
Is this just a side-affect of a package link that I shouldn't do for source packages, or a bug somewhere else?
A not yet supported case.
Michael is just about to add code to support also this situation.
This is now active.
However, you osc package in openSUSE:Tumbleweed is currently a wild mix of a simple link (not using a branch) plus manual committed files of an old version of osc.
It is? Wierd, I don't know what happened, I'll go fix that up...
Either remove everything in the package beside the _link file or make it a branch.
I've removed everything and started over and there is only a _link file there now, hopefully that works. thanks for looking at it, greg k-h -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fri, Jun 10, 2011 at 03:42:32PM -0700, Greg KH wrote:
On Fri, Jun 10, 2011 at 12:02:28PM +0200, Adrian Schröter wrote:
Am Friday, 10. June 2011, 10:24:58 schrieb Adrian Schröter:
Am Thursday, 9. June 2011, 10:19:42 schrieb Greg KH:
On Thu, Jun 09, 2011 at 06:11:48PM +0200, Adrian Schröter wrote:
build.opensuse.org is running now with the new source service mode.
We recommend to upgrade to osc 0.132 version as available in openSUSE:Tools project if you work with source services.
The difference to the old way source service were handled is that with the new mode, no "source service" commits are generated. This means, the history just contains the commits done by the user, which makes things like revision diffs much easier. The source service result is handled as an internal commit, like with source links. Builds are still done with those internal commits.
A manual service run trigger is handled as commit by the user, so it is part of the history.
This solves also the blocking of commits (403 errors) during a service run.
Nice job.
But I'm getting the build system error "services only work on branches" when trying to link in a package that contains a branch (i.e. the osc package itself into openSUSE:Tumbleweed).
This has nothing todo with this change, it was always not supported.
But I enabled project wide services in openSUSE:Tools to validate all sources, like we plan to do for Factory.
Is this just a side-affect of a package link that I shouldn't do for source packages, or a bug somewhere else?
A not yet supported case.
Michael is just about to add code to support also this situation.
This is now active.
However, you osc package in openSUSE:Tumbleweed is currently a wild mix of a simple link (not using a branch) plus manual committed files of an old version of osc.
It is? Wierd, I don't know what happened, I'll go fix that up...
Either remove everything in the package beside the _link file or make it a branch.
I've removed everything and started over and there is only a _link file there now, hopefully that works.
Hm, nope, I'm now getting the error: openSUSE:Tools/osc: conflict in file osc-0.132.3.tar.gz How can there be a conflict when all that is there is a _link file? I created that link by doing: osc linkpac -f -r 7a54e058bcc918a53ac55b8d4159a08a openSUSE:Tools osc openSUSE:Tumbleweed was that not correct? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
When I click on "diff and submit these changes back." in a branch, I see the changes that I have made plus a file _service:format_spec_file:phpMyAdmin.spec which contains the complete original file as diff. Is this correct? You can see it at home:weberho:server/phpMyAdmin . Johannes Am 11.06.11 00:46, schrieb Greg KH:
On Fri, Jun 10, 2011 at 03:42:32PM -0700, Greg KH wrote:
On Fri, Jun 10, 2011 at 12:02:28PM +0200, Adrian Schröter wrote:
Am Friday, 10. June 2011, 10:24:58 schrieb Adrian Schröter:
Am Thursday, 9. June 2011, 10:19:42 schrieb Greg KH:
On Thu, Jun 09, 2011 at 06:11:48PM +0200, Adrian Schröter wrote:
build.opensuse.org is running now with the new source service mode.
We recommend to upgrade to osc 0.132 version as available in openSUSE:Tools project if you work with source services.
The difference to the old way source service were handled is that with the new mode, no "source service" commits are generated. This means, the history just contains the commits done by the user, which makes things like revision diffs much easier. The source service result is handled as an internal commit, like with source links. Builds are still done with those internal commits.
A manual service run trigger is handled as commit by the user, so it is part of the history.
This solves also the blocking of commits (403 errors) during a service run.
Nice job.
But I'm getting the build system error "services only work on branches" when trying to link in a package that contains a branch (i.e. the osc package itself into openSUSE:Tumbleweed).
This has nothing todo with this change, it was always not supported.
But I enabled project wide services in openSUSE:Tools to validate all sources, like we plan to do for Factory.
Is this just a side-affect of a package link that I shouldn't do for source packages, or a bug somewhere else?
A not yet supported case.
Michael is just about to add code to support also this situation.
This is now active.
However, you osc package in openSUSE:Tumbleweed is currently a wild mix of a simple link (not using a branch) plus manual committed files of an old version of osc.
It is? Wierd, I don't know what happened, I'll go fix that up...
Either remove everything in the package beside the _link file or make it a branch.
I've removed everything and started over and there is only a _link file there now, hopefully that works.
Hm, nope, I'm now getting the error: openSUSE:Tools/osc: conflict in file osc-0.132.3.tar.gz
How can there be a conflict when all that is there is a _link file?
I created that link by doing: osc linkpac -f -r 7a54e058bcc918a53ac55b8d4159a08a openSUSE:Tools osc openSUSE:Tumbleweed was that not correct?
thanks,
greg k-h
-- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Friday, 10. June 2011, 15:46:01 schrieb Greg KH:
On Fri, Jun 10, 2011 at 03:42:32PM -0700, Greg KH wrote:
On Fri, Jun 10, 2011 at 12:02:28PM +0200, Adrian Schröter wrote:
Am Friday, 10. June 2011, 10:24:58 schrieb Adrian Schröter:
Am Thursday, 9. June 2011, 10:19:42 schrieb Greg KH:
On Thu, Jun 09, 2011 at 06:11:48PM +0200, Adrian Schröter wrote:
build.opensuse.org is running now with the new source service mode.
We recommend to upgrade to osc 0.132 version as available in openSUSE:Tools project if you work with source services.
The difference to the old way source service were handled is that with the new mode, no "source service" commits are generated. This means, the history just contains the commits done by the user, which makes things like revision diffs much easier. The source service result is handled as an internal commit, like with source links. Builds are still done with those internal commits.
A manual service run trigger is handled as commit by the user, so it is part of the history.
This solves also the blocking of commits (403 errors) during a service run.
Nice job.
But I'm getting the build system error "services only work on branches" when trying to link in a package that contains a branch (i.e. the osc package itself into openSUSE:Tumbleweed).
This has nothing todo with this change, it was always not supported.
But I enabled project wide services in openSUSE:Tools to validate all sources, like we plan to do for Factory.
Is this just a side-affect of a package link that I shouldn't do for source packages, or a bug somewhere else?
A not yet supported case.
Michael is just about to add code to support also this situation.
This is now active.
However, you osc package in openSUSE:Tumbleweed is currently a wild mix of a simple link (not using a branch) plus manual committed files of an old version of osc.
It is? Wierd, I don't know what happened, I'll go fix that up...
Either remove everything in the package beside the _link file or make it a branch.
I've removed everything and started over and there is only a _link file there now, hopefully that works.
Hm, nope, I'm now getting the error: openSUSE:Tools/osc: conflict in file osc-0.132.3.tar.gz
How can there be a conflict when all that is there is a _link file?
This conflict is in the old revision you specify inside of the openSUSE:Tools project. You used an old srcmd5 revision which meanwhile conflicts with the latest version of osc in openSUSE:Factory (where openSUSE:Tools is linking to in this revision).
I created that link by doing: osc linkpac -f -r 7a54e058bcc918a53ac55b8d4159a08a openSUSE:Tools osc openSUSE:Tumbleweed was that not correct?
except for using the not working revision, yes. I think you can solve by updating to current revision: osc setlinkrev openSUSE:Tumbleweed osc -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Tuesday, 14. June 2011, 11:57:07 schrieb Adrian Schröter: ...
This conflict is in the old revision you specify inside of the openSUSE:Tools project. You used an old srcmd5 revision which meanwhile conflicts with the latest version of osc in openSUSE:Factory (where openSUSE:Tools is linking to in this revision).
I created that link by doing: osc linkpac -f -r 7a54e058bcc918a53ac55b8d4159a08a openSUSE:Tools osc openSUSE:Tumbleweed was that not correct?
except for using the not working revision, yes.
I think you can solve by updating to current revision:
osc setlinkrev openSUSE:Tumbleweed osc
JFYI, setlinkrev is using current xsrcmd5, that means the merged sources, so this link will not break if the linked package instances are changing (except they get removed, but we could even that support later on ...) -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thursday, June 09, 2011 06:11:48 PM Adrian Schröter wrote:
build.opensuse.org is running now with the new source service mode.
We recommend to upgrade to osc 0.132 version as available in openSUSE:Tools project if you work with source services.
The difference to the old way source service were handled is that with the new mode, no "source service" commits are generated. This means, the history just contains the commits done by the user, which makes things like revision diffs much easier. The source service result is handled as an internal commit, like with source links. Builds are still done with those internal commits.
A manual service run trigger is handled as commit by the user, so it is part of the history.
This solves also the blocking of commits (403 errors) during a service run.
Michael and Adrian
Adrian, Michael, do we have any documentatoin in the wiki for this? I only found http://en.opensuse.org/openSUSE:Build_Service_Concept_SourceService and that is too broad. Andreas -- Andreas Jaeger, Program Manager openSUSE aj@{novell.com,suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (5)
-
Adrian Schröter -
Andreas Jaeger -
Greg KH -
Johannes Weberhofer -
Michael Schroeder