From: Jon Turney <jon.turney@dronecode.org.uk>
To: Jari Aalto <jari.aalto@cante.net>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [Attn: mercurial maintainer] hg fails with python3.9
Date: Sat, 30 Apr 2022 15:16:42 +0100 [thread overview]
Message-ID: <36f6073a-0714-00fb-6542-a0f339937ffb@dronecode.org.uk> (raw)
In-Reply-To: <YmvyJY6hllVWvG/v@congo.cante.net>
On 29/04/2022 15:11, Jari Aalto wrote:
> On 2022-04-29 12:23, Jon Turney wrote:
>>>> libdir = '../lib/python3.8/site-packages'
>>>>
>>>> This causes hg to fail as follows if /usr/bin/python3 points to python3.9:
>>>
>>> ERROR: package 'mercurial' version '5.7-3' is most recent non-test version, but version '6.0-1' is curr
>>
>> This error is trying to tell you "version 6.0-1 exists, so the version you
>> are uploading won't be installed for anyone who already has that higher
>> version number installed, so maybe this isn't what you want to do".
>>
>> mercurial version 6.0-1 does exist, for x86_64 only, dated 2021-11-25.
>
> My mistake. I had the development environment in wrong server, so only 5.7
> was in there and I forgot to check the latest in Cygwin.
>
> 6.1.1-1 uploaded
No problem. I'll see if I can improve that error message sometime.
I notice that mercurial appears to be pure python, so maybe we can
upload it as noarch in future?
next prev parent reply other threads:[~2022-04-30 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 14:27 Ken Brown
2022-04-29 9:46 ` Jari Aalto
[not found] ` <4615caa2-972c-6f9e-1fc0-3d2bfbe3083c@dronecode.org.uk>
2022-04-29 14:11 ` Jari Aalto
2022-04-30 14:16 ` Jon Turney [this message]
2022-05-02 14:57 ` Jari Aalto
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=36f6073a-0714-00fb-6542-a0f339937ffb@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=jari.aalto@cante.net \
/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).