Source package recipes prefer Bazaar when lp:$foo alias is VCS-ambiguous
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Colin Watson |
Bug Description
If lp:<project> works for both git and bzr, then creating a source build recipe against the git branch doesn't work. Instead, it is interpreted as a bzr-based recipe, the "# git-build-
Workaround: from https:/
More at: https:/
Related branches
- William Grant (community): Approve (code)
-
Diff: 290 lines (+92/-35)6 files modifiedlib/lp/code/browser/tests/test_sourcepackagerecipe.py (+2/-5)
lib/lp/code/interfaces/sourcepackagerecipe.py (+17/-2)
lib/lp/code/model/sourcepackagerecipe.py (+6/-5)
lib/lp/code/model/sourcepackagerecipebuild.py (+3/-2)
lib/lp/code/model/sourcepackagerecipedata.py (+25/-19)
lib/lp/code/model/tests/test_sourcepackagerecipe.py (+39/-2)
summary: |
- git-based source build recipes are sometimes interpreted as bzr recipes - instead + Source package recipes prefer Bazaar when lp:$foo alias is VCS-ambiguous |
Changed in launchpad: | |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: easy git recipe |
Changed in launchpad: | |
status: | Triaged → In Progress |
assignee: | nobody → Colin Watson (cjwatson) |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
I too am affected by this, and I worked around it by specifying the full path every time I edited the recipe, e.g. lp:~ts.sch.gr/sch-scripts/+git/sch-scripts instead of lp:sch-scripts.
The workaround that Robie mentioned is better though, doing so now. :)