[opensuse-buildservice] osc mbranch might lead to a strange setup/ result
Hi, we have several bug fixes in the Samba queue and thefore I used the following 'osc mbranch' commands: osc mbranch samba home:lmuelle:bnc815994etal osc co home:lmuelle:bnc815994etal Next I feeded samba.openSUSE_12.3_Update and called osc commit. The very same steps I repeated for samba.openSUSE_12.2_Update and samba.openSUSE_12.1_Update. Surprisingly for each samba.openSUSE_12.* the build service caused independent builds of openSUSE 12.1, 12.2, and 12.3. See for example https://build.opensuse.org/package/show?package=samba.openSUSE_12.1_Update&project=home%3Almuelle%3Abnc815994etal Next I gave 'osc mbranch -c samba' a try, got home:lmuelle:branches:OBS_Maintained:samba and fed it with the same package sources. Here the build jobs look as expected. https://build.opensuse.org/package/show?package=samba.openSUSE_12.3_Update&project=home%3Almuelle%3Abranches%3AOBS_Maintained%3Asamba is limited to 12.3 only. Did I used 'osc mbranch' the wrong way or is this a bug? Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
The described symptoms I see on an openSUSE 12.3 x86_64 system. osc is installed in version 0.139.1-1.1.1. -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Fri, Apr 19, 2013 at 08:48:41PM +0200, Lars Müller wrote:
we have several bug fixes in the Samba queue and thefore I used the following 'osc mbranch' commands:
osc mbranch samba home:lmuelle:bnc815994etal osc co home:lmuelle:bnc815994etal
Next I feeded samba.openSUSE_12.3_Update and called osc commit. The very same steps I repeated for samba.openSUSE_12.2_Update and samba.openSUSE_12.1_Update.
Surprisingly for each samba.openSUSE_12.* the build service caused independent builds of openSUSE 12.1, 12.2, and 12.3.
See for example https://build.opensuse.org/package/show?package=samba.openSUSE_12.1_Update&project=home%3Almuelle%3Abnc815994etal
Next I gave 'osc mbranch -c samba' a try, got home:lmuelle:branches:OBS_Maintained:samba and fed it with the same package sources. Here the build jobs look as expected.
https://build.opensuse.org/package/show?package=samba.openSUSE_12.3_Update&project=home%3Almuelle%3Abranches%3AOBS_Maintained%3Asamba is limited to 12.3 only.
Did I used 'osc mbranch' the wrong way or is this a bug?
It looks like this behaviour is intentional. By default build and publish are disabled on the prj level. Publishing in this particular cas was required as I'd like the reporter to test the current code. To get the intended result for 12.3 for example I disabled build for the 12.1 and 12.2 repository manually for now. But is this the way how it is intended? Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Friday 2013-04-19 20:48, Lars Müller wrote:
we have several bug fixes in the Samba queue and thefore I used the following 'osc mbranch' commands:
osc mbranch samba home:lmuelle:bnc815994etal osc co home:lmuelle:bnc815994etal
Surprisingly for each samba.openSUSE_12.* the build service caused independent builds of openSUSE 12.1, 12.2, and 12.3.
To create multiple packages is the point of mbranch. All of openSUSE:12.{1,2,3}:Update/samba may have different code and may thus require different patches, creating three packages is the only sensible action for mbranch. If you want to publish the same version to multiple releases, mbranch is just a hell of an indirection. The short route: cd network/samba/STABLE/samba/ <commit update> sosc sr --no-cleanup openSUSE:12.3:Update sosc sr --no-cleanup openSUSE:12.2:Update sosc sr --no-cleanup openSUSE:12.1:Update -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sun, Apr 21, 2013 at 08:17:46AM +0200, Jan Engelhardt wrote:
On Friday 2013-04-19 20:48, Lars Müller wrote:
we have several bug fixes in the Samba queue and thefore I used the following 'osc mbranch' commands:
osc mbranch samba home:lmuelle:bnc815994etal osc co home:lmuelle:bnc815994etal
Surprisingly for each samba.openSUSE_12.* the build service caused independent builds of openSUSE 12.1, 12.2, and 12.3.
To create multiple packages is the point of mbranch.
Yes. And that was my intention. But I expected to get in samba.openSUSE_12.1_Update only openSUSE_12.1 targets enabled to build and not 12.2 and 12.3 too. https://build.opensuse.org/package/repositories?package=samba.openSUSE_12.1_Update&project=home%3Almuelle%3Abranches%3AOBS_Maintained%3Asamba For 12.2 only 12.2 builds and no 12.1 and 12.3 too. https://build.opensuse.org/package/repositories?package=samba.openSUSE_12.2_Update&project=home%3Almuelle%3Abranches%3AOBS_Maintained%3Asamba For 12.3 only 12.3 builds and no 12.1 and 12.2 too. https://build.opensuse.org/package/repositories?package=samba.openSUSE_12.3_Update&project=home%3Almuelle%3Abranches%3AOBS_Maintained%3Asamba For the usual OBS_Maintained workflow users might not need to publish the results. I guess that's why publishing is disabled by default. Here we intended to get some feedback before we start the maintenance workflow and therefore enabled building and publishing on the project level: osc meta prj home:lmuelle:branches:OBS_Maintained:samba First had by default when created: <build> <disable/> </build> <publish> <disable/> </publish> To gather feedback got modified to: <build> <enable/> </build> <publish> <enable/> </publish> Soon after I noticed that more than the intended builds started. That's why I had to define on the meta pkg level for: home:lmuelle:branches:OBS_Maintained:samba samba.openSUSE_12.1_Update <build> <enable repository="openSUSE_12.1_Update"/> <disable repository="openSUSE_12.2_Update"/> <disable repository="openSUSE_12.3_Update_ports"/> <disable repository="openSUSE_12.3_Update_standard"/> </build> home:lmuelle:branches:OBS_Maintained:samba samba.openSUSE_12.2_Update <build> <enable repository="openSUSE_12.2_Update"/> <disable repository="openSUSE_12.1_Update"/> <disable repository="openSUSE_12.3_Update_ports"/> <disable repository="openSUSE_12.3_Update_standard"/> </build> home:lmuelle:branches:OBS_Maintained:samba samba.openSUSE_12.3_Update <build> <enable repository="openSUSE_12.3_Update_ports"/> <enable repository="openSUSE_12.3_Update_standard"/> <disable repository="openSUSE_12.1_Update"/> <disable repository="openSUSE_12.2_Update"/> </build> This looks unintended to me. But we here might use the osc mbranch feature the wrong way.
All of openSUSE:12.{1,2,3}:Update/samba may have different code and may thus require different patches, creating three packages is the only sensible action for mbranch.
If you want to publish the same version to multiple releases, mbranch is just a hell of an indirection. The short route:
cd network/samba/STABLE/samba/ <commit update> sosc sr --no-cleanup openSUSE:12.3:Update sosc sr --no-cleanup openSUSE:12.2:Update sosc sr --no-cleanup openSUSE:12.1:Update
Yes, that would have been the preferred approach. And it would break sssd builds again. That's why we patch all version to the same code level. BTW network:samba:STABLE/samba is on the same patch level as well. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Sonntag, 21. April 2013, 15:26:49 wrote Lars Müller:
On Sun, Apr 21, 2013 at 08:17:46AM +0200, Jan Engelhardt wrote:
On Friday 2013-04-19 20:48, Lars Müller wrote:
we have several bug fixes in the Samba queue and thefore I used the following 'osc mbranch' commands:
osc mbranch samba home:lmuelle:bnc815994etal osc co home:lmuelle:bnc815994etal
Surprisingly for each samba.openSUSE_12.* the build service caused independent builds of openSUSE 12.1, 12.2, and 12.3.
To create multiple packages is the point of mbranch.
Yes. And that was my intention. But I expected to get in samba.openSUSE_12.1_Update only openSUSE_12.1 targets enabled to build and not 12.2 and 12.3 too.
And that is default ....
For 12.2 only 12.2 builds and no 12.1 and 12.3 too.
For 12.3 only 12.3 builds and no 12.1 and 12.2 too.
For the usual OBS_Maintained workflow users might not need to publish the results. I guess that's why publishing is disabled by default.
Here we intended to get some feedback before we start the maintenance workflow and therefore enabled building and publishing on the project level:
osc meta prj home:lmuelle:branches:OBS_Maintained:samba
First had by default when created:
<build> <disable/> </build> <publish> <disable/> </publish>
right ..
To gather feedback got modified to:
<build> <enable/> </build>
No, just do not do that. The packages which are needed got enabled on package level. There is zero need to fiddel around with build flags.
<publish> <enable/> </publish>
You may do this, if you really want to publish it. However, usually people do anyway just "osc getbinaries" to get the result ASAP. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Adrian Schröter -
Jan Engelhardt -
Lars Müller