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?
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.
Is there some recommended way of handling this, or am I just planning
too much for something that won't be an issue?
Thanks!
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
