Bug#1001655: Avoid hardcoding depends on specific lzip implementations

To: 1001655@bugs.debian.org
Cc: daniel.baumann@progress-linux.org
Subject: Bug#1001655: Avoid hardcoding depends on specific lzip implementations
From: Felix Lechner <felix.lechner@lease-up.com>
Date: Mon, 13 Dec 2021 12:18:56 -0800
Message-id: <[🔎] CAFHYt55SCtDe5a_zXfg+fa-SFrE3O8WO7qCjtqdven+SHp8a7g@mail.gmail.com>
Reply-to: Felix Lechner <felix.lechner@lease-up.com>, 1001655@bugs.debian.org
In-reply-to: <[🔎] bd4a8435-7bfb-6bc8-2523-e1a48020e53b@progress-linux.org>
References: <[🔎] bd4a8435-7bfb-6bc8-2523-e1a48020e53b@progress-linux.org> <[🔎] bd4a8435-7bfb-6bc8-2523-e1a48020e53b@progress-linux.org>

Hi Daniel,

On Mon, Dec 13, 2021 at 11:36 AM Daniel Baumann
<daniel.baumann@progress-linux.org> 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 introduced in this commit? [2] Thanks!

Kind regards
Felix Lechner

[1] https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/Files/Compressed/Lz.pm#L61
[2] https://salsa.debian.org/lintian/lintian/-/commit/bc64d63c4ecd293687524086b6966e30e9c48ae0

Reply to:

Follow-Ups:
- Bug#1001655: Avoid hardcoding depends on specific lzip implementations
  - From: Daniel Baumann <daniel.baumann@progress-linux.org>

References:
- Bug#1001655: Avoid hardcoding depends on specific lzip implementations
  - From: Daniel Baumann <daniel.baumann@progress-linux.org>

Prev by Date: Bug#1001655: Avoid hardcoding depends on specific lzip implementations
Next by Date: Processed: retitle 941656 to lintian: changelog-file-missing-explicit-entry not working properly
Previous by thread: Bug#1001655: Avoid hardcoding depends on specific lzip implementations
Next by thread: Bug#1001655: Avoid hardcoding depends on specific lzip implementations
Index(es):
- Date
- Thread