Bug#648632: uscan(1) says that archive requires .gz

James McCoy jamessan at debian.org
Sun Aug 4 14:08:03 UTC 2013


Control: severity -1 wishlist
Control: retitle -1 Determine which tarballs are repacked based on debian/source/format

On Sun, Nov 13, 2011 at 08:49:50AM -0800, Matt Kraai wrote:
> The documentation of the --repack option on the uscan(1) manual page
> says
> 
>  After  having downloaded an lzma tar, xz tar, bzip tar or zip
>  archive, repack it to a gzip tar archive, which is still currently
>  required as a member of a Debian source package.
> 
> There are source packages in the Debian archive that use other
> compression methods (e.g., 7kaa).

Different compression methods are only allowed for non-1.0 sources
(c.f., dpkg-source(1)).  Repacking to .gz is a conservative measure,
since we may not always be able to determine the source format being
used.

If one knows that they are using a 3.0 source package and the upstream
tarball is in a valid format, then there's no need to use --repack.

If we can determine that the package is using a non-1.0 source format,
then it would be ok to reduce the set of extensions that get repacked.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20130804/799e1359/attachment.sig>


More information about the devscripts-devel mailing list