X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3C693386F82A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cante.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=jari DOT aalto AT cante DOT net Date: Sat, 6 Mar 2021 16:45:39 +0200 From: Jari Aalto To: Marco Atzeri Subject: Re: Cygwin now on Python 3? What about Mercurial? Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: cygwin AT cygwin DOT com Content-Type: text/plain; charset="utf-8" Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 126EjosF005372 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 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple