From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: python3 packages
Date: Mon, 27 Dec 2021 17:48:23 +0100 [thread overview]
Message-ID: <851182e1-f6d1-238a-479f-0c7c886ef732@gmail.com> (raw)
In-Reply-To: <CAAWYfq2+F=zvETe4=gTXdsOSoOOcpNRMUdwWPS0DOkRB93d3KA@mail.gmail.com>
On 27.12.2021 13:53, Dima Pasechnik wrote:
> There are python3* cygiwin packages obsoleted by python36* packages, e.g.
> python36-numpy. As python36* is basically obsolete itself now, it
> creates an impression
> that there are no python39* etc available.
Hi Dima,
I suggest to follow the Cygwin Announce list.
https://sourceware.org/pipermail/cygwin-announce/2021-December/010365.html
The 36 is a residual of old settings in the tool (cygport) we use
to build and package the Cygwin programs.
I am planning to change it to 39 in the near future.
> Also, I noticed that python-numpy-1.21.4-1.src/python-numpy.cygport
> from python-numpy-src/python-numpy-1.21.4-1-src
> is not it the source git repo
> https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/python-numpy.git;a=summary,
> is this a bug?
No, just that building the package and uploading to the git
repository are two different steps.
I am a bit behind on the second one, as I am also moving
my packages and their history from the old personal repository
to the current shared one.
You can use the Cygwin Setup to download the source package,
or download from any mirror the file as:
http://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin/x86_64/release/python-numpy/python-numpy-1.21.4-1-src.tar.xz
its content is
$ tar -tf python-numpy-1.21.4-1-src.tar.xz
python-numpy-1.21.4-1.src/
python-numpy-1.21.4-1.src/numpy-1.21.4.zip
python-numpy-1.21.4-1.src/python-numpy.cygport
> Dmitrii
Regards
Marco
prev parent reply other threads:[~2021-12-27 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 12:53 Dima Pasechnik
2021-12-27 16:48 ` Marco Atzeri [this message]
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=851182e1-f6d1-238a-479f-0c7c886ef732@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).