problem with recipe build

[Scott Moser]

On Sat, 3 Mar 2012, Jelmer Vernooij wrote:

> On Fri, 2012-03-02 at 22:02 -0500, Scott Moser wrote:
> > > > Which seems sane to me.  The upstream source doesn't have tags named
> > > > 'upstream-<version>', but only 'release-<version>'.
> > > >
> > > > Help?
> > >
> > > [...]
> > >
> > > > bzr: ERROR: Unable to find the upstream source. Import it as tag upstream-0.9.4+r4177 or build with --allow-fallback-to-native.
> > >
> > > Your version number is saying this is a non-native package, which
> > > requires an upstream tarball to build against.
> >
> > Well, its not a native package, so it makes sense (to me) that the
> > version number would reflect that.
> Non-native packages require a .orig.tar.gz. bzr-builder tries to
> retrieve the contents of that tarball by taking the contents of the tree
> at that particular tag.

That does make sense.  I just was expecting that the daily build code for
a non-native version string would essentially do:
  $ bzr branch $UPSTREAM_BRANCH upstream
  $ ( cd upstream && bzr export \
     --root ${PKG_NAME}-${UPSTREAM_VERSION_PART} > \
     ../${PKG_NAME}_${UPSTREAM_VERSION_PART}.orig.tar.gz )
Where UPSTREAM_VERSION_PART in this case would be '0.9.4+r4177'.

And the error message does suggest the right path, but it just seemed
wrong.

> > The full output can be seen at http://paste.ubuntu.com/866071/ .
> >
> > >   * Changing the version number to have no "-", making it a native
> > >     version number.
> > >   * Or build with --allow-fallback-to-native, which will ignore all of
> > >     this and build the native package despite the version number
> What is the source format the package uses? Is it "3.0 (quilt)" perhaps?

It is quilt 3.0.

> > I did verify that '--allow-fallback-to-native' worked, but it is just
> > confusing to me, as this is clearly not a native package, and somehow the
> > recipe above works, and works on launchpad.
> This makes sense, as Launchpad has --allow-fallback-to-native enabled by
> default.

That makes sense as to why it builds.

Is the following basic form for an upstream build sane:
| # bzr-builder format 0.3 deb-version
| # 2.0.0~bzr{revno}~{revno:packaging}-0ubuntu2
| lp:euca2ools
| nest-part packaging lp:~smoser/ubuntu/oneiric/euca2ools/upstream-pkg debian debian