From: Jari Aalto <jari.aalto@cante.net>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: Ken Brown <kbrown@cornell.edu>, cygwin@cygwin.com
Subject: Re: Cygwin now on Python 3? What about Mercurial?
Date: Sat, 6 Mar 2021 16:45:39 +0200 [thread overview]
Message-ID: <YEOVk+qe+WcJOFfT@congo.cante.net> (raw)
In-Reply-To: <b36b971e-e5a1-c5e9-40be-031158ea6b48@gmail.com>
On 2021-03-04 19:32, Marco Atzeri wrote:
> On 04.03.2021 16:19, Ken Brown via Cygwin wrote:
> > On 3/4/2021 6:05 AM, marco atzeri via Cygwin wrote:
> > > On Thu, Mar 4, 2021 at 10:27 AM Russell VT via Cygwin wrote:
> > > >
> > > > Cygwin Enthusiasts!
> > > >
> > > > Well, I was going to hold back on this one, but having now
> > > > watched the list
> > > > for a bit, I think this is a fair question (feel free to smack me if I'm
> > > > feeling too entitled, albeit maybe a bit on the rambling side).
> > > >
> > > > TLDR; Cygwin 64 Mercurial (5.5.1) blows chunks with default
> > > > Python install.
> > > > I'm still not sure if this is a package dependency error, given
> > > > the recent
> > > > Python 2.7 Deprecation "worldwide," or the way that Mercurial is
> > > > packaged,
> > > > or even if the package installation order on-down the line
> > > > screwed me up at
> > > > some point in the past.
> > > >
> > > > TLDR2; Am I really the "only" one on Cygwin still using Mercurial in a
> > > > Complex Python Environment?
> > > >
> > > > Here;s my primary operating environment, devoid of whatever tricks I may
> > > > try to play with Python Development environments (read: Path to /usr/bin
> > > > with no funny stuff getting in the way)
> > > > .
> > >
> > > Hi Russel,
> > >
> > > short term solution is the same mentioned here
> > > https://sourceware.org/pipermail/cygwin/2021-January/247657.html
> > >
> > > It seems the current package maintainer for Mercurial is not
> > > available for
> > > the upgrade from 2.7 to 3.8.
> > > We need to decide how to proceed
> >
> > The Mercurial maintainer (Jari) doesn't always follow the mailing list.
> > I've added him to the CC.
>
> I already tried that route on Cygwin-apps
> I am afraid he is out of reach, hoping nothing serious happened.
>
> https://sourceware.org/pipermail/cygwin-apps/2021-February/041088.html
I regret for the delay. Busy and some Python 3 problems.
Now uploaded,
Jari
next prev parent reply other threads:[~2021-03-06 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 8:45 Russell VT
2021-03-04 11:05 ` marco atzeri
2021-03-04 15:19 ` Ken Brown
2021-03-04 18:32 ` Marco Atzeri
2021-03-06 14:45 ` Jari Aalto [this message]
2021-03-06 14:49 ` Marco Atzeri
2021-03-07 9:32 ` Russell VT
2021-03-07 11:58 ` Marco Atzeri
2021-04-02 13:27 ` Oleksandr Gavenko
2021-03-11 11:57 ` Jari Aalto
2021-03-04 13:30 ` Stephen John Smoogen
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=YEOVk+qe+WcJOFfT@congo.cante.net \
--to=jari.aalto@cante.net \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
--cc=marco.atzeri@gmail.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).