build-from-branch into the primary archive

[Clint Byrum]

On Tue, 2011-02-22 at 10:41 -0500, Barry Warsaw wrote:
> On Feb 19, 2011, at 08:21 PM, Loïc Minier wrote:
> 
> > (We usually don't but lp:ubuntu URLs in Vcs-Bzr because it's kind of
> > implicit that we have this branch in every package, but there is not
> > way to tell whether the UDD branch is in use or not; listing it
> > explicitly when it's used solves this)
> 
> One other quick note.  With bzr 2.3, lp:ubuntu branches can also be referenced
> by ubuntu:<series>/<package> urls.  <series> can be 'maverick' or 'm' and can
> be omitted for the latest series.  E.g. to get Natty's version of
> python-numpy, just say:
> 
> % bzr branch ubuntu:python-numpy
> 
> Maverick's version via:
> 
> % bzr branch ubuntu:m/python-numpy
> 

Cool! I didn't know about that.

Forgive me for not digging through the docs, but I am curious about one
thing.

At the moment, if a Vcs-Bzr tag does exist and one is using UDD, is one
ever told about this?

My workflow right now is:

First I check to make sure the package is in sync in UDD (anybody have a
good one liner for this? I just look at the package overview right now
which is not very efficient)

mkdir ~/pkg/$package && cd ~/pkg/$package && bzr init-repo bzr && cd bzr
bzr branch lp:ubuntu/series/$package series && cd series
-- make changes --
bzr bd -S
dput ppa:whatever file.dsc
sbuild -A -d series-arch file.dsc

If all of that works I debcommit, push, and propose merging.. but I'm
wondering at what point I might have been reminded of the Vcs-Bzr tag so
I can go look there. I'm always reminded of it by 'apt-get source'. I
know I've missed the existence of a branch before by not noting this
very fact. Ideally bzr branch ubuntu:something would do the check and
remind me at that point if the branch is different.