Received: from mx1.tetrasec.net (mx1.tetrasec.net [66.245.176.36]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id E476D782B73 for ; Fri, 3 Apr 2020 16:54:00 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id CA50E6A2BD; Fri, 3 Apr 2020 16:53:59 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id E7CC76A2BC; Fri, 3 Apr 2020 16:53:58 +0000 (UTC) Date: Fri, 3 Apr 2020 18:53:52 +0200 From: Natanael Copa To: "Ludovic Chabant" Cc: alpine-aports@lists.alpinelinux.org, "Drew DeVault" Subject: Re: [PATCH] Add hotfix for running `hg archive` with gzip files on python 3.8.2+ Message-ID: <20200403185352.70ca07f9@ncopa-desktop.copa.dup.pw> In-Reply-To: <775dd995-47b1-4853-9e26-9f37d87f5d39@www.fastmail.com> References: <20200310204748.28104-1-ludovic@chabant.com> <775dd995-47b1-4853-9e26-9f37d87f5d39@www.fastmail.com> X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; x86_64-alpine-linux-musl) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi! On Fri, 03 Apr 2020 09:42:14 -0700 "Ludovic Chabant" wrote: > Hey Natanael, this is a gentle ping about this patch. > > The `hg archive` command is currently broken on Alpine edge without > this fix (or until the next Mercurial release). It's blocking us on > sourcehut at the moment because our deployments rely on that command. > > Thanks! Sorry, the patch drowned in my inbox and I missed it completely. The commit message should be something like: main/mercurial: hotfix for running `hg archive` with gzip files on python 3.8.2+ It would also be good with a reference to upstream bug report or upstream commit in the commit message. I can clean up the message this time (but for the future to minimize risk that I confuse it with other mailing lists). Second, the patch needs to be rebased since mercurial was updated to 5.3.2 - unless this fixes the issue ofc. Thanks!