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 ins
Hi Daniel,
On Tue, Dec 28, 2021 at 7:09 PM Daniel Baumann
wrote:
>
> you can now safely depend on ... "plzip | lzip-decompressor"
Great, thanks! Will that work for backports, too?
Kind regards
Felix Lechner
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:
ht
Hi Daniel,
On Mon, Dec 13, 2021 at 2:00 PM Daniel Baumann
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 nam
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 alt
Hi Daniel,
On Mon, Dec 13, 2021 at 11:36 AM Daniel Baumann
wrote:
>
>if only decompression is used:
>'lzip | lzip-decompressor'
We only use the '--test' functionality. [1] Is that implemented by all
alternatives?
Also, do we still need to determine the proper name of the executable,
as
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 fo
7 matches
Mail list logo
