incorrect merge rules don't cause validation errors

Bug #592821 reported by Aaron Bentley
6
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.

Tags: lp-code recipe
Aaron Bentley (abentley)
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → Low
tags: added: recipe
Revision history for this message
Tim Penhey (thumper) wrote :

Aaron, do you think this is a bug in bzr-builder? Or just how we are using it?

Revision history for this message
Aaron Bentley (abentley) wrote :

I would say a bug in bzr-builder, but revision specs are tricky to validate, so I'm not surprised that it doesn't.

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.