From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: python packages
Date: Sun, 7 Mar 2021 20:34:14 +0100 [thread overview]
Message-ID: <b9f45241-2ac4-cb6d-0a47-6ace97e41193@gmail.com> (raw)
In-Reply-To: <459f09e0-1b87-cf8f-7ab4-81950e80b353@cornell.edu>
On 07.03.2021 17:58, Ken Brown via Cygwin wrote:
>> I have a CI job which runs 'setup -q -P python3,python3-lxml'. It's
>> nice if that gets me something where "python3 -c 'import lxml'" works,
>> and doesn't require changing every time the default python version is
>> updated.
>
> Currently python3 is a meta-package whose main purpose is to require the
> default python version (currently python38). Marco, couldn't you just
> make python3-foo a meta-package that requires the corresponding
> python*-foo (currently python38-foo)?
>
> Ken
the issue is that Cygport creates the "obsolete" python3-foo
that is replaced by python36-foo automatically.
we should change cygport to use python38 instead
---------------------------------------------------
$ cat python3-lxml/python3-lxml-4.6.2-1.hint
category: _obsolete
requires: python36-lxml
sdesc: "Obsoleted by python36-lxml"
ldesc: "The python3-lxml package is obsolete. Selecting this package for
installation will cause the python36-lxml package, which replaces this
one, to be installed instead."
external-source: python-lxml
---------------------------------------------------
next prev parent reply other threads:[~2021-03-07 19:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 21:37 Marco Atzeri via Cygwin-announce
2021-01-22 23:49 ` Ken Brown
2021-02-09 21:31 ` Jon Turney
2021-02-10 2:29 ` Yaakov Selkowitz
2021-02-10 8:19 ` Marco Atzeri
2021-03-07 15:37 ` Jon Turney
2021-03-07 16:58 ` Ken Brown
2021-03-07 19:34 ` Marco Atzeri [this message]
2021-03-07 20:44 ` Ken Brown
2021-03-07 21:20 ` Brian Inglis
2021-05-04 17:04 ` Jon Turney
-- strict thread matches above, loose matches on Subject: below --
2021-11-24 15:01 Marco Atzeri via Cygwin-announce
2021-05-05 16:21 Marco Atzeri via Cygwin-announce
2021-05-05 2:39 Marco Atzeri via Cygwin-announce
2021-04-25 6:41 Marco Atzeri via Cygwin-announce
2021-02-17 5:26 Marco Atzeri via Cygwin-announce
2021-02-14 19:49 Marco Atzeri via Cygwin-announce
2021-02-14 8:34 Marco Atzeri via Cygwin-announce
2021-02-02 15:10 Marco Atzeri via Cygwin-announce
2021-02-01 9:57 Marco Atzeri via Cygwin-announce
2021-01-31 5:09 Marco Atzeri via Cygwin-announce
2021-01-30 15:29 Marco Atzeri via Cygwin-announce
2020-08-16 12:46 Marco Atzeri via Cygwin-announce
2020-08-12 7:43 Marco Atzeri via Cygwin-announce
2020-08-10 8:08 Marco Atzeri via Cygwin-announce
2020-08-09 15:44 Marco Atzeri via Cygwin-announce
2020-08-06 20:35 Marco Atzeri via Cygwin-announce
2020-08-02 10:49 Marco Atzeri via Cygwin-announce
2020-07-26 19:58 Marco Atzeri via Cygwin-announce
2020-07-23 17:59 Marco Atzeri via Cygwin-announce
2020-07-19 17:05 Marco Atzeri via Cygwin-announce
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=b9f45241-2ac4-cb6d-0a47-6ace97e41193@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).