From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: python packages
Date: Thu, 21 Jan 2021 20:06:40 +0100 [thread overview]
Message-ID: <8c52b0fa-1e15-daa9-4007-91c3a59ac557@gmail.com> (raw)
In-Reply-To: <DB7PR02MB3996A164E37B0E5A02B70288E7A10@DB7PR02MB3996.eurprd02.prod.outlook.com>
On 21.01.2021 18:06, Hamish McIntyre-Bhatty via Cygwin wrote:
>>
>> install one and it will remove the other, also as they have
>> the same content in this case
>
> That makes sense, but that's not what happened here - it prompted to
> remove "pylint" itself and install "python38-plint" but only after
> running setup again after installing the new test "pylint" package.
> Maybe I'm being a bit stupid but this seems like weird behaviour in
> setup.exe - I would have expected it to do this when I asked to upgrade
> "pylint" in the first place, or to automatically install
> "python38-pylint" when I selected "pylint".
>
> Hamish
>
probably a consequence of being still test classified packages
Marco
next prev parent reply other threads:[~2021-01-21 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 21:08 Marco Atzeri via Cygwin-announce
2021-01-21 16:18 ` Hamish McIntyre-Bhatty
2021-01-21 16:27 ` Marco Atzeri
2021-01-21 16:37 ` Hamish McIntyre-Bhatty
2021-01-21 16:52 ` Marco Atzeri
2021-01-21 17:06 ` Hamish McIntyre-Bhatty
2021-01-21 19:06 ` Marco Atzeri [this message]
2021-01-22 9:29 ` Hamish McIntyre-Bhatty
-- strict thread matches above, loose matches on Subject: below --
2021-01-13 12:03 Marco Atzeri via Cygwin-announce
2021-01-02 11:48 Marco Atzeri via Cygwin-announce
2020-12-31 7:31 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=8c52b0fa-1e15-daa9-4007-91c3a59ac557@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).