On 04-Mar-2009, Jelmer Vernooij wrote: > Vcs-Bzr shouldn't be used by get-orig-source, as it is intended for > the branch with the packaging, not for the upstream branch. > get-orig-source, otoh is intended for the upstream source. > get-orig-source should also retrieve the most recent version of > upstream rather than the last on in debian/changelog, as policy > mentions.
Okay. I presumed from the contents of the branch that it was also serving as the upstream branch. Since that's not the case, what is the upstream branch public URL? > Some of the other bzr-* packages already implement this by utilizing > bzr-builddeb and a much more trivial get-orig-source target. Unless they produce a “pristine source” tarball, which AFAIK isn't what ‘bzr-builddeb’ does, they're not correctly implementing the ‘get-orig-source’ target. > > The patch bundle is against the Alioth branch > > bzr+ssh://bzr.debian.org/bzr/pkg-bazaar/bzr-loom/experimental/ > > which is accessible to me only because I have an account there. > You should also be able to use nosmart+http://... As it turns out, the plain ‘http://foo’ URL works fine once bug#518098 is addressed on the client side. -- \ “A politician is an animal which can sit on a fence and yet | `\ keep both ears to the ground.” —Henry L. Mencken | _o__) | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
