Bug#519514: openoffice.org: Vcs-* control fields incorrect
Hi,
Ben Finney wrote:
> > > The other is just the upstream Subversion respository,
> > > ‘svn://svn.gnome.org/svn/ooo-build/branches/ooo-build-3-0-1’. That
> > > is not the Debian package management branch, so should not be in
> > > the ‘Vcs-Foo’ control field.
> >
> > This is not exactly true. debian/ is useless without the ooo-build
> > checkout. This will be fixed when we ever switch back to vanilla OOo
> > and thus will have all our patches in debian/patches, but until that
> > we need debian/ AND ooo-build, and those are in different repos...
>
> The ‘Vcs-Foo’ field can point to a branch that is the Debian packaging
> only, that's fine. I presume you're using ‘bzr-buildpackage’ or the
> like, to merge the original source archive with the Debian packaging?
Actually, no :) I create a orig, extract it and add ooo-build and debian.
(or simply extract the new orig over the old tree and remove the old tarballs)
ooo-build and debian both are in the .diff.gz (currently)
> That just needs to be in a ‘get-orig-source’ target, to get the
> upstream VCS version to an original source archive. Documenting the
Well, the .orig.tar.gz just contains the original source :). No business
of ooo-build and debian in there (well, one can argue that ooo-build shuld
be in there, though, but unless we stick to go-oo releases we then can't
easily svn up it :) )
Grüße/Regards,
René
--
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' rene@debian.org | GnuPG-Key ID: 248AEB73
`- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
Reply to: