going ahead of Debian with a dfsg orig tarball

[Colin Watson]

On Tue, Mar 19, 2019 at 02:19:00PM -0300, Andreas Hasenack wrote:
> I find myself in the situation where we want to go ahead of debian for
> a package (samba), but it's a dfsg tarball. Debian doesn't have it
> anywhere yet, so I produced the tarball according to the exclude rules
> in debian/gbp.conf.
> 
> I'm wondering, however, if some mistake happens, or something else,
> and the tarball I produce has a different hash than the tarball that
> Debian will eventually produce. Since my upload will be in Ubuntu
> already, what will happen when Launchpad will try to ingest Debian's
> upload, and finds out the orig tarball has a different md5, but the
> same name as the Ubuntu one?

If that happens, then it won't be possible to sync the Debian package,
and you'll have to use "syncpackage -F" to work around that (assuming
there are no other Ubuntu changes; if there are, then you can just merge
manually instead).

> To avoid that, I previously mangled the name of our orig tarball to
> use ...+dfsg~ubuntu-0ubuntu1 (i.e., I added the ~ubuntu bit after
> +dfsg), but that looks ugly.

I suppose that works well enough.  It wouldn't be the first package
version to have multiple "ubuntu" substrings.

> Is there some recommended way of handling this, or am I just planning
> too much for something that won't be an issue?

I'd recommend talking to your Debian counterpart(s) to see if it's
possible to agree in advance on a particular orig tarball representation
of this upstream release.

-- 
Colin Watson                                       [cjwatson at ubuntu.com]