From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFE] calm needs to know about ZStandard compressed archives
Date: Sun, 3 Jan 2021 16:30:09 +0100 [thread overview]
Message-ID: <afc893b1-4e30-5cef-0b33-cf56523f4877@gmail.com> (raw)
In-Reply-To: <53032d89-0aff-b533-6e0f-3057def38c68@dronecode.org.uk>
On 03.01.2021 16:19, Jon Turney wrote:
> On 31/12/2020 17:08, Jon Turney wrote:
>> On 31/12/2020 16:01, Marco Atzeri via Cygwin-apps wrote:
>>> On 31.12.2020 16:52, Achim Gratz wrote:
>>>> Marco Atzeri via Cygwin-apps writes:
>>>>> On 31.12.2020 16:47, Achim Gratz wrote:
>>>>>> Jon Turney writes:
>>>>>>> This isn't totally straightforward as calm uses the python tar
>>>>>>> module
>>>>>>> to validate the upload archives, but that doesn't (yet) support zstd
>>>>>>> compression.
>
> I can arrange to install it on sourceware, but it would be nice if
> python-xtarfile was packaged so it can be made a prerequisite of the
> calm package.
I will do it, but I will appreciate if package maintainers
can validate the python/pip test release I recently uploaded.
As I am rebuiling/adding python packages using latest test
and going backward is not so nice.
We will also need to modify cygport to stop automatically add
OBSOLETES as most of this packages never existed
eg python3-pytest
>>> python36-pytest requires: python36 python36-attrs
python36-iniconfig python36-pluggy python36-py python36-packaging
python36-toml
>>> python36-pytest OBSOLETES: python3-pytest
>>> python37-pytest requires: python37 python37-attrs
python37-iniconfig python37-pluggy python37-py python37-packaging
python37-toml
>>> python38-pytest requires: python38 python38-attrs
python38-iniconfig python38-pluggy python38-py python38-packaging
python38-toml
an overall cleaning of obsoletes package may be useful in the
near future. I need to work on it.
regards
Marco
next prev parent reply other threads:[~2021-01-03 15:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 19:59 Achim Gratz
2020-12-31 15:25 ` Jon Turney
2020-12-31 15:47 ` Achim Gratz
2020-12-31 15:51 ` Marco Atzeri
2020-12-31 15:52 ` Achim Gratz
2020-12-31 16:01 ` Marco Atzeri
2020-12-31 17:08 ` Jon Turney
2020-12-31 18:33 ` Achim Gratz
2020-12-31 19:05 ` Brian Inglis
2020-12-31 19:18 ` Achim Gratz
2020-12-31 19:29 ` Brian Inglis
2020-12-31 20:03 ` Achim Gratz
2021-01-03 15:19 ` Jon Turney
2021-01-03 15:30 ` Marco Atzeri [this message]
2021-01-03 15:57 ` Achim Gratz
2021-01-03 16:22 ` Marco Atzeri
2021-01-04 14:30 ` Jon Turney
2021-01-04 18:35 ` Achim Gratz
2021-01-03 21:55 ` Marco Atzeri
2021-01-10 15:03 ` Jon Turney
2021-01-10 18:32 ` Achim Gratz
2021-01-24 9:35 ` Achim Gratz
2021-02-07 14:05 ` Jon Turney
2021-01-31 17:13 ` Achim Gratz
2021-02-07 14:07 ` Jon Turney
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=afc893b1-4e30-5cef-0b33-cf56523f4877@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).