GNU bug report logs - #38256
Packages sources in '.tar.lz' archives

Previous Next

To reply to this bug, email your comments to 38256 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Guillaume Le Vaillant <glv <at> posteo.net>
To: bug-guix <at> gnu.org
Subject: Packages sources in '.tar.lz' archives
Date: Mon, 18 Nov 2019 14:29:44 +0100

Hi,

Currently, when package sources are in a '.tar.lz' archive (e.g. ed,
wget, ddrescue, etc.), the 'lzip' package must be explicitly put into
the 'native-inputs' of the package definition, or building the package
fails.

Would it be possible to make the 'lzip' package available by default in
the build process, like 'gzip', 'bzip2' and 'xz'?

Message #8 received at 38256 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Guillaume Le Vaillant <glv <at> posteo.net>
Cc: 38256 <at> debbugs.gnu.org
Subject: Re: bug#38256: Packages sources in '.tar.lz' archives
Date: Sat, 23 Nov 2019 18:37:20 +0100

Hi Guillaume,

Guillaume Le Vaillant <glv <at> posteo.net> skribis:

> Currently, when package sources are in a '.tar.lz' archive (e.g. ed,
> wget, ddrescue, etc.), the 'lzip' package must be explicitly put into
> the 'native-inputs' of the package definition, or building the package
> fails.
>
> Would it be possible to make the 'lzip' package available by default in
> the build process, like 'gzip', 'bzip2' and 'xz'?

Yes.  There’s not a strong incentive because there are relatively few
packages distributed as lz files, but we could do that in
‘core-updates’.

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.