incorrect merge rules don't cause validation errors
Bug #592821 reported by
Aaron Bentley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
I accidentally created a recipe with a merge rule like this:
merge packaging lp:~bzr/bzr-pipeline/lucid-packaging debian
When I attempted to build the recipe, it failed with this error:
bzr: ERROR: No namespace registered for string: 'debian'
I assume the third parameter to a merge rule is meant to be a revision spec. If so, we should check it for validity when the user creates the recipe.
Changed in launchpad-code: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: recipe |
To post a comment you must log in.
Aaron, do you think this is a bug in bzr-builder? Or just how we are using it?