|
Bugzilla – Full Text Bug Listing |
| Summary: | osc don't branch particular project | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE.org | Reporter: | Petr Gajdos <pgajdos> |
| Component: | BuildService | Assignee: | Marcus Hüwe <suse-tux> |
| Status: | RESOLVED FIXED | QA Contact: | Adrian Schröter <adrian.schroeter> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jsmeix, suse-tux |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Update:test get picked because it is configured as update project for :Update. (this is independent of devel project mechanism). So, this seems to be wanted in this case. Do you have any problems with using Update:Test ? (In reply to comment #1) > (this is independent of devel project mechanism). Ok, I see. > > So, this seems to be wanted in this case. Do you have any problems with using > Update:Test ? No, but then the Note is misleading in this case I think. pgajdos@laura:~/osc> osc ls openSUSE:11.1:Update:Test pgajdos@laura:~/osc> osc ls openSUSE:11.1:Update:Test php5-pear-mail Mail-1.1.14.tgz php5-pear-mail.changes php5-pear-mail.spec ready pgajdos@laura:~/osc> As stated above, osc branches php5-pear-mail from :Update:Test, that is confusing as well. Even worse: compare osc cat openSUSE:11.1:Update xpdf xpdf.changes | head against osc cat openSUSE:11.1:Update:Test xpdf xpdf.changes | head or osc cat home:pgajdos:branches:openSUSE:11.1:Update:Test/xpdf xpdf.changes | head It seems to me, that's openSUSE:11.1's xpdf what get branched, not openSUSE:11.1:Update's xpdf. (In reply to comment #2) > (In reply to comment #1) > > So, this seems to be wanted in this case. Do you have any problems with using > > Update:Test ? > > No, but then the Note is misleading in this case I think. I just pushed a fix to git master. Now osc will print that it created the branch from the configured update project. Seems like the issue was solved. |
pgajdos@laura:~/osc> osc branch openSUSE:11.1:Update php5 --nodevelproject Note: The branch has been created of a different project, openSUSE:11.1:Update:Test, which is the primary location of where development for that package takes place. That's also where you would normally make changes against. A direct branch of the specified package can be forced with the --nodevelproject option. A working copy of the branched package can be checked out with: osc co home:pgajdos:branches:openSUSE:11.1:Update:Test/php5 pgajdos@laura:~/osc>