Source package recipes prefer Bazaar when lp:$foo alias is VCS-ambiguous

Bug #1623924 reported by Robie Basak
74
This bug affects 12 people
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-recipe..." header is replaced with a "# bzr-builder..." header, and the "Base source" link on the recipe page points to the bzr branch instead.

Workaround: from https://code.launchpad.net/<project>/+configure-code, empty the Branch box from Bazaar settings -> Link to a Bazaar branch already on Launchpad, then delete and recreate the recipe. This stops lp:<project> working from bzr, and then the recipe creation finds the git branch instead.

More at: https://irclogs.ubuntu.com/2016/09/15/%23launchpad.html#t11:57

Related branches

William Grant (wgrant)
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
William Grant (wgrant)
Changed in launchpad:
importance: Undecided → High
status: New → Triaged
tags: added: easy git recipe
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

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. :)

Colin Watson (cjwatson)
Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Colin Watson (cjwatson)
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Colin Watson (cjwatson)
tags: added: qa-ok
removed: qa-needstesting
Colin Watson (cjwatson)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.