Re: Adding support for LZIP to dpkg, using that instead of xz, archive wide
On Wed, Jun 17, 2015 at 12:58:55AM +0200, Guillem Jover wrote:
> From where I'm sitting it all pretty much looks like a self-inflicted
> problem. Upstream does not believe in releasing source tarballs (so
> each user has to generate them from git-archive, which should be
> considered inherently non-reproducible across different versions), and
> then for packaging you want to use a pristine-tar workflow w/o using
> pristine-tar, nor by creating a single common upstream source tarball,
> nor by communicating/coordinating the creation of the first upstream
> source tarball and reusing that on the other distro.
No, in this particular case, upstream IS releasing source tarballs and
the packagers are refusing to use them for reasons I find
incomprehensible.
Reply to:
- References:
- Adding support for LZIP to dpkg, using that instead of xz, archive wide
- From: Thomas Goirand <zigo@debian.org>
- Re: Adding support for LZIP to dpkg, using that instead of xz, archive wide
- From: Paul Wise <pabs@debian.org>
- Re: Adding support for LZIP to dpkg, using that instead of xz, archive wide
- From: Thomas Goirand <zigo@debian.org>
- Re: Adding support for LZIP to dpkg, using that instead of xz, archive wide
- From: Guillem Jover <guillem@debian.org>
- Re: Adding support for LZIP to dpkg, using that instead of xz, archive wide
- From: Thomas Goirand <zigo@debian.org>
- Re: Adding support for LZIP to dpkg, using that instead of xz, archive wide
- From: Guillem Jover <guillem@debian.org>