2014-04-26 11:00 Vincent Bernat:
❦ 26 avril 2014 01:31 CEST, Manuel A. Fernandez Montecelo
<manuel.montez...@gmail.com> :
Compared to that amount of work, stripping a few files from a tarball
using uscan is utterly trivial and I don't see why it is a problem.
It's quite a bit harder to do the right thing and persuade upstream to
not include them.
How to handle this with gbp?
I guess that one of the best things that you can do is to filter the files, like
other cruft in the tarball coming from upstream, example:
http://anonscm.debian.org/gitweb/?p=pkg-sdl/packages/libsdl2.git;a=blob;f=debian/gbp.conf;h=b3a5a0939feff4f6578c8d617059ac7e740b778b;hb=HEAD
Good to know. I was using a dedicated "dfsg" branch, but the workflow is
crappy in this case. But currently, nothing we can do with
debian/copyright?
I am not sure of what you mean.
If you don't have it in the repackaged .orig.tar, you don't have to document it
in debian/copyright (you can document somewhere why you removed them from
orig.tar, though).
Other people mentioned other methods of solving these cases with uscan and other
tools, but I am not familiar with those so I don't know if there are better
methods.
--
Manuel
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140426143419.gc9...@lugh.itsari.org
