Recipes: failed to build after altering series branch

Bug #703202 reported by Neil Wilson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

Looks like the recipe system isn't picking up changes quite corrrectly.

With this recipe: https://code.launchpad.net/~brightbox/+recipe/ruby-stomp-edge

Changed the target of the series lp:ruby-stomp from lp:~brightbox/ruby-stomp/trunk to lp:~brightbox/ruby-stomp/github-trunk
edited the recipe to point at the new branch (which then immediately replaced the entry with lp:ruby-stomp as expected).

Then renamed the old branch from lp:~brightbox/ruby-stomp/trunk to lp:~brightbox/ruby-stomp/gitorious-trunk

The auto-build then produced the following error: (http://launchpadlibrarian.net/62247046/buildlog.txt.gz)

Building recipe:
# bzr-builder format 0.2 deb-version 1.1.7+{revno}-0ubuntu0+{revno:packaging}+{time}
lp:ruby-stomp
nest packaging lp:~brightbox/ruby-stomp/packaging debian

You have not informed bzr of your Launchpad ID, and you must do this to
write to Launchpad or access private data. See "bzr help launchpad-login".
You have not informed bzr of your Launchpad ID, and you must do this to
write to Launchpad or access private data. See "bzr help launchpad-login".
bzr: ERROR: Not a branch: "http://bazaar.launchpad.net/~brightbox/ruby-stomp/trunk/".

Tags: recipe
tags: added: recipe
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Tim Penhey (thumper) wrote :

I'm pretty sure that the underlying problem here has more to do with the renaming of a branch that is being stacked on.

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.