Bug 735135 - osc mbranch broken for 12.1
Summary: osc mbranch broken for 12.1
Status: NEW
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: BuildService (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Adrian Schröter
QA Contact: Adrian Schröter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-06 18:47 UTC by Marcus Rückert
Modified: 2012-01-19 14:14 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Rückert 2011-12-06 18:47:16 UTC
i basically followed:

http://en.opensuse.org/openSUSE:Build_Service_Concept_Maintenance#Create_your_branch_project_to_prepare_your_submission

in the OBS:
$ osc mbranch -c rubygems
# fix rubygems
$ osc sr
Submitting package  rubygems.openSUSE_11.3
Submitting package  rubygems.openSUSE_11.4
Submitting package  rubygems.openSUSE_12.1

Everything fine? Can we create the requests ? (y/n) y
Server returned an error: HTTP Error 400: Bad Request
The target project openSUSE:12.1:Update is a maintenance release project, please use the maintenance workflow instead.

Dirk pointed out that the more official documentation is:
http://en.opensuse.org/openSUSE:Package_maintenance

but that one shows osc mbranch *aswell*. imho wrapping the whole osc search ... + osc branch for the packager into mbranch is a good idea. in the past we had the internal script "checkout_for_sec_update", which also kept the packager from having to worry about "for which distros do i have to fix this?". if 12.1 require some kind of special handling there. osc mbranch should be enhanced to do that automatically.
Comment 1 Adrian Schröter 2011-12-07 08:20:46 UTC
mbranch is complete fine, but you need to submit with "osc maintenancerequest" as written in the official OBS documentation.

The wiki page is still documenting the old way.
Comment 2 Marcus Rückert 2011-12-07 10:31:07 UTC
ok so could you make osc submitrequest work transparently in this case?
so the user dont get scared with a message?
Comment 3 Adrian Schröter 2011-12-07 10:51:38 UTC
I will change osc to show the two options the user has.

1) Submit request entire project to an existing incident (sr behaviour needs to be changed)
2) Request to create a new maintenance incident