[opensuse-buildservice] maintenance, osc branch/mbranch
Hi, I have to prepare some updates once again and tried to follow the process which used to be described here: http://en.opensuse.org/Maintenance This one points to here now: http://wiki.opensuse.org/openSUSE:Maintenance The latter is inconsistent while the first seem to be consistent but not matching OBS' osc behaviour anymore when it comes to osc branch usage. osc branch openSUSE:11.2 perl-Bootloader this will print what you need to check out, either: home:jreidinger:branches:openSUSE:11.2/perl-Bootloader or if there already was an update of perl-Bootloader: home:jreidinger:branches:openSUSE:11.2:Update:Test/perl-Bootloader So according to this I should get the latest (update) package for my branch but this isn't the case (anymore?). I always get the exact GA version of the package branched instead. The new page http://wiki.opensuse.org/openSUSE:Maintenance/Packager is telling me to use :Update but then the pasted osc output makes no sense: "Note: The branch has been created of a different project" So parts of that description still implies the old behaviour (but apparently someone found that and added the "Update" string in the command above? But also this is apparently broken because if there is no updated package the branch command fails and doesn't use the base project to branch from there. So now you could say I should fix the documentation but actually I'm not sure where the issue is. I would say that OBS (or osc?) changed its behaviour but absolutely unsure if intentionally or not. If osc branch doesn"t do automatically the right thing anymore it's probably useless to recommend or describe that usage? If it's a bug in OBS I'm completely right in posting here though. Please tell me what the supposed behaviour is. Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Jun 23, 2010 at 05:28:27PM +0200, Wolfgang Rosenauer wrote:
Hi,
I have to prepare some updates once again and tried to follow the process which used to be described here: http://en.opensuse.org/Maintenance This one points to here now: http://wiki.opensuse.org/openSUSE:Maintenance
The latter is inconsistent while the first seem to be consistent but not matching OBS' osc behaviour anymore when it comes to osc branch usage.
osc branch openSUSE:11.2 perl-Bootloader
this will print what you need to check out, either:
home:jreidinger:branches:openSUSE:11.2/perl-Bootloader
or if there already was an update of perl-Bootloader:
home:jreidinger:branches:openSUSE:11.2:Update:Test/perl-Bootloader
So according to this I should get the latest (update) package for my branch but this isn't the case (anymore?). I always get the exact GA version of the package branched instead. The new page http://wiki.opensuse.org/openSUSE:Maintenance/Packager is telling me to use :Update but then the pasted osc output makes no sense: "Note: The branch has been created of a different project"
So parts of that description still implies the old behaviour (but apparently someone found that and added the "Update" string in the command above? But also this is apparently broken because if there is no updated package the branch command fails and doesn't use the base project to branch from there.
This seems to be a OBS 2.0 bug then, it did fell back from openSUSE:11.2 to openSUSE:11.2:Update previously...
So now you could say I should fix the documentation but actually I'm not sure where the issue is. I would say that OBS (or osc?) changed its behaviour but absolutely unsure if intentionally or not.
Probably an OBS bug. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Wolfgang Rosenauer wrote:
So now you could say I should fix the documentation but actually I'm not sure where the issue is. I would say that OBS (or osc?) changed its behaviour but absolutely unsure if intentionally or not.
If osc branch doesn"t do automatically the right thing anymore it's probably useless to recommend or describe that usage? If it's a bug in OBS I'm completely right in posting here though.
Please tell me what the supposed behaviour is.
osc/obs should automatically do the right thing :-) The wiki page was wrong. I've fixed that. It's actually a bug in obs if it doesn't work as described. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thursday 24 June 2010 09:04:24 Ludwig Nussel wrote:
Wolfgang Rosenauer wrote:
So now you could say I should fix the documentation but actually I'm not sure where the issue is. I would say that OBS (or osc?) changed its behaviour but absolutely unsure if intentionally or not.
If osc branch doesn"t do automatically the right thing anymore it's probably useless to recommend or describe that usage? If it's a bug in OBS I'm completely right in posting here though.
Please tell me what the supposed behaviour is.
osc/obs should automatically do the right thing :-) The wiki page was wrong. I've fixed that. It's actually a bug in obs if it doesn't work as described.
Which is fixed now on api.opensuse.org. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (4)
-
Adrian Schröter -
Ludwig Nussel -
Marcus Meissner -
Wolfgang Rosenauer