Bug#874663: Document +dfsg as extenson when repacking upstream sources
Package: debian-policy
Version: 4.1.0.0
Severity: wishlist
Hi,
when upstream tarballs need to be repacked because they contain non-dfsg
free data appending '+dfsg' to the upstream version seems common
practice. However some packages append '.dfsg', others use
+dfsg<number> and there are more formats around.
It would be great if policy could recommend +dfsg as the default
(falling back to +dfsg<number> if there was a packaging error (i.e. some
files slip through and the package was rejected by ftp-masters).
This would make it simpler for tools like lintian or gbp to detect repacked
tarballs (in this case we don't want to attach the upstream signature to
the chages file).
Cheers,
-- Guido
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages debian-policy depends on:
ii libjs-sphinxdoc 1.5.6-2
debian-policy recommends no packages.
Versions of packages debian-policy suggests:
pn doc-base <none>
-- no debconf information
Reply to: