From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: python packages
Date: Thu, 21 Jan 2021 17:06:32 +0000 [thread overview]
Message-ID: <DB7PR02MB3996A164E37B0E5A02B70288E7A10@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <21a9a54c-7433-caa0-0b66-b49a81e3cc6e@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2199 bytes --]
On 21/01/2021 16:52, Marco Atzeri via Cygwin wrote:
> On 21.01.2021 17:37, Hamish McIntyre-Bhatty via Cygwin wrote:
>> On 21/01/2021 16:27, Marco Atzeri via Cygwin wrote:
>>> On 21.01.2021 17:18, Hamish McIntyre-Bhatty via Cygwin wrote:
>>>> On 19/01/2021 21:08, Marco Atzeri via Cygwin-announce via Cygwin
>>>> wrote:
>>>>> Several python packages have been uploaded as test
>>>
>
>>>
>>> it should pull python38-pylint
>>>
>>> $ cygcheck -l python38-pylint | grep bin
>>> /usr/bin/pylint3.8
>>> /usr/bin/epylint3.8
>>> /usr/bin/pyreverse3.8
>>> /usr/bin/symilar3.8
>>> /usr/bin/pylint
>>> /usr/bin/epylint
>>> /usr/bin/pyreverse
>>> /usr/bin/symilar
>>
>> Okay, just realised I was wrong about the shortcut, as I do have
>> /usr/bin/pylint3.6. My bad.
>>
>> However, it didn't pull python38-pylint in for me. An interesting thing
>> just happened when I opened setup again though: it says pending
>> operations are to remove "pylint" and install "python38-pylint". When I
>> told it I wanted to keep "pylint" I got a dependency issue, see attached
>> screenshot.
>>
>> In case it's helpful to know, I had the old "pylint" package installed
>> already and upgraded it to your test version.
>>
>> Hamish
>>
>
> on the setup.ini you can see
>
> -----------------------------------
> @ python38-pylint
> sdesc: "python code static checker"
> ...
> [test]
> version: 2.6.0-1
> ...
> depends2: python38, python38-astroid, python38-isort, python38-mccabe,
> python38-pytest, python38-toml
>
> obsoletes: pylint <<<<<<
>
> build-depends: cygport
> --------------------------------
>
> 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
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-21 17: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 [this message]
2021-01-21 19:06 ` Marco Atzeri
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=DB7PR02MB3996A164E37B0E5A02B70288E7A10@DB7PR02MB3996.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.uk \
--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).