Subject: Avoid hardcoding depends on specific lzip implementations
Date: Mon, 13 Dec 2021 20:32:30 +0100
Package: lintian
Version: 2.114.0
Severity: wishlist
Hi,
in #967083, someone requested that the lintian depends on lzip should be
changed into an alternative depends on 'lzip | clzip' with the
justification, that the submitter prefered clzip as his
lzip-implementation-of-choice (for memory footprint reasons).
I'm maintaining all lzip related packages in Debian and there's a set of
provides by all lzip compressors/decompressors packages since the jessie
release in place.
May I therefore ask to have the current 'lzip | clzip' depends to be
changed into either one of these:
if only decompression is used:
'lzip | lzip-decompressor'
if only compression is used:
'lzip | lzip-compressor'
if both copmression and decompression is used:
'lzip | lzip-alternative'
This will smoothly allow using any of the packages of the lzip family to
be used, most notably the one I prefer: plzip (fully parallel version)
Regards,
Daniel
Acknowledgement sent
to Felix Lechner <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Lintian Maintainers <[email protected]>.
(Mon, 13 Dec 2021 20:45:03 GMT) (full text, mbox, link).
Subject: Re: Bug#1001655: Avoid hardcoding depends on specific lzip
implementations
Date: Mon, 13 Dec 2021 22:59:52 +0100
Hi Felix
On 12/13/21 21:18, Felix Lechner wrote:
> We only use the '--test' functionality. Is that implemented by all
> alternatives?
all of them, except lzd, do implement --test.
> Also, do we still need to determine the proper name of the executable,
> as introduced in this commit?
there are alternatives in place since jessie,
you can just call /usr/bin/lzip:
$ update-alternatives --list lzip
/usr/bin/lzip.clzip
/usr/bin/lzip.lunzip
/usr/bin/lzip.lzd
/usr/bin/lzip.lzip
/usr/bin/lzip.lziprecover
/usr/bin/lzip.minilzip
/usr/bin/lzip.pdlzip
/usr/bin/lzip.plzip
$
Regards,
Daniel
Acknowledgement sent
to Felix Lechner <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Lintian Maintainers <[email protected]>.
(Mon, 13 Dec 2021 22:48:03 GMT) (full text, mbox, link).
Subject: Re: Bug#1001655: Avoid hardcoding depends on specific lzip implementations
Date: Mon, 13 Dec 2021 14:45:03 -0800
Hi Daniel,
On Mon, Dec 13, 2021 at 2:00 PM Daniel Baumann
<[email protected]> wrote:
>
> all of them, except lzd, do implement --test.
Looking at your documentation [1] does that mean Lintian can only
offer the alternatives except lzd?
Or, is there another way to assess the actual nature or integrity of a
file named like *.lz? Thanks!
Kind regards
Felix Lechner
[1] https://sources.debian.org/src/lzip/1.22-4/debian/lzip.README.Debian/
Subject: Re: Avoid hardcoding depends on specific lzip implementations
Date: Wed, 29 Dec 2021 04:05:14 +0100
Hi Felix,
> Looking at your documentation [1] does that mean Lintian can only
> offer the alternatives except lzd?
yes; to make that easier.. given that lzd is the only one that doesn't
support '--test', I've dropped it from the alternatives handling and
updated README.Debian accordingly:
https://git.progress-linux.org/users/daniel.baumann/debian/packages/lzip/commit/?id=aa00b3c1e8eb3ce2dbe4425a492240c2d54e5153
means.. you can now safely depend on "lzip | lzip-decompressor"
(or even better: "plzip | lzip-decompressor").
any of the lzip packages providing lzip-decompressor will support
'--test' and work for that lintian use-case. I'm keeping it that way as
a base-line, so any potential further lzip decompressor that woudn't
support '--test' will not get the lzip-alternative handling.
> Or, is there another way to assess the actual nature or integrity of a
> file named like *.lz?
using '--test' is the proper way to do it.
Regards,
Daniel
Acknowledgement sent
to Felix Lechner <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Lintian Maintainers <[email protected]>.
(Wed, 29 Dec 2021 04:45:05 GMT) (full text, mbox, link).
Subject: Re: Bug#1001655: Avoid hardcoding depends on specific lzip implementations
Date: Tue, 28 Dec 2021 20:41:08 -0800
Hi Daniel,
On Tue, Dec 28, 2021 at 7:09 PM Daniel Baumann
<[email protected]> wrote:
>
> you can now safely depend on ... "plzip | lzip-decompressor"
Great, thanks! Will that work for backports, too?
Kind regards
Felix Lechner
Subject: Re: Bug#1001655: Avoid hardcoding depends on specific lzip
implementations
Date: Wed, 29 Dec 2021 07:34:15 +0100
On 12/29/21 05:41, Felix Lechner wrote:
> Will that work for backports, too?
all the alternatives are in place, unchanged (apart from the lzd
alternative removal), since jessie and newer; so.. that's perfectly fine
to use for backports back up to jessie.
the niche-case where someone would install lzd in bullseye or older, and
then have a lintian backport from bookworm that would depends on the
lzip-decompressor which lzd from bullseye will satisfies without
providing '--test'.. could be avoided by adding a 'Conflicts: lzd (<<
1.2-3~)'.
Regards,
Daniel
Control: tag -1 pending
Hello,
Bug #1001655 in lintian reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/lintian/lintian/-/commit/87be0b748dfae67d4a1035efd9cf9b64d888bd84
------------------------------------------------------------------------
Do not depend on any particular Lzip implementation. (Closes: #1001655)
Thanks to Daniel Baumann, who maintains all Lzip related packages in Debian,
for bringing this matter to our attention!
------------------------------------------------------------------------
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1001655
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.