From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: scallywag / cygport not pulling lzip
Date: Fri, 8 Jan 2021 14:58:17 +0100 [thread overview]
Message-ID: <cfdd1d59-896e-7d93-d252-beebed185067@gmail.com> (raw)
In-Reply-To: <87wnwnk1er.fsf@Otto.invalid>
On 08.01.2021 14:23, ASSI wrote:
> Marco Atzeri via Cygwin-apps writes:
>> it seems that cygport is not pulling the decompressor
>> that is supposed to recognise:
>>
>> https://ci.appveyor.com/project/cygwin/scallywag/builds/37134000/job/0m9h56ptrwwyg3hc
>>
>>>> Unpacking source flex-2.6.4.tar.lz
>> tar (child): lzip: Cannot exec: No such file or directory
>> tar (child): Error is not recoverable: exiting now
>> tar: Child returned status 2
>> tar: Error is not recoverable: exiting now
>> *** ERROR: tar xf flex-2.6.4.tar.lz failed
>
> Since tar is a Base package it doesn't require lzip (which would
> effectively make it a Base install). You have to add lzip to
> BUILD_REQUIRES or switch to the GZip archive.
>
>
> Regards,
> Achim.
>
Hi Achim,
this is an upstream source package.
IMHO cygport should pull tar and all the decompressor that
is supposed to manage.
$ grep SRC_URI NEWS
...
* SRC_URI supports .tar.lz archives.
* SRC_URI accepts .tar.xz archives.
* SRC_URI accepts .tar.lzo archives.
...
next prev parent reply other threads:[~2021-01-08 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 7:38 Marco Atzeri
2021-01-08 13:23 ` ASSI
2021-01-08 13:58 ` Marco Atzeri [this message]
2021-01-08 14:21 ` Jon Turney
2021-01-08 16:52 ` Brian Inglis
2021-01-08 17:13 ` Achim Gratz
2021-01-08 18:09 ` Brian Inglis
2021-01-08 19:11 ` Achim Gratz
2021-01-11 22:05 ` Brian Inglis
2021-01-12 16:28 ` Brian Inglis
2021-01-12 19:46 ` ASSI
2021-01-09 19:08 ` Achim Gratz
2022-08-14 19:07 Hannes Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cfdd1d59-896e-7d93-d252-beebed185067@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).