Path: csiph.com!weretis.net!feeder7.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Sandro Tosi Newsgroups: linux.debian.maint.python,linux.debian.bugs.dist Subject: Re: [Python-apps-team] Bug#937009: mercurial: Python2 removal in sid/bullseye Date: Sun, 05 Jul 2020 07:00:02 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Jul 5 04:52:43 2020 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.82 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SARE_MLH_Stock10=1.66] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-qv1-f45.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0V/TOajQX/urff/9FOfGBj48LIGUsHwj0PAiuj5E1hM=; b=R7osttBQ8/F4z/6NBd3c6iyhENOna72wrIEM5Nv+4bzV6ZEha4g7iYVI/B/kPOhSaT m+Ck6xRu17d7tvbG7XIsjMVvs01PaC5cXjY9BnCmQs91HJhWP3Uo5jnSkJ1sHOsHWLIx mnMUykgcNRKZ6QF6xgkchrRVdMiddq+1xaOD7P4XaOrnZbbrqSV70/o1mtOokUhyS2D8 UYbS7l+5kYDAlqZURRtHH8jz3aLE8bopG8y1JJ4RxdrHBekgMLR0QG9add/FtbMBNQow CHph9NBc4Kav/wqsOOkFELr5BDoPPCws7/+n8RCDSafSeACWAUNm91Cooii7MFLkA5Vn FE7w== X-Gm-Message-State: AOAM531cymcNvNH2SB+/92SdcX2kR5ZfR4FSyocT7+KSCO3LVUjVpPK2 JFs2p6chvetSnZprNddpYMPwDSlv55JSegCWr9Y= X-Google-SMTP-Source: ABdhPJy0udV1VFMiQ3x2xtPVIXn4KspKl9rl41LoFmN5td0MnvCXyj0bjPwJTbfCO/hJiv75R5YcqhvKju2ui9lWJhk= X-Received: by 2002:a0c:b88d:: with SMTP id y13mr36263491qvf.82.1593924746800; Sat, 04 Jul 2020 21:52:26 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailing-List: archive/latest/18439 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAB4XWXzVf2Jrh5v33HOvW46zrhSrM4U7KL61rMavUPbRyJTvAA@mail.gmail.com Approved: robomod@news.nic.it Lines: 69 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: 937009@bugs.debian.org X-Original-Date: Sun, 5 Jul 2020 00:52:00 -0400 X-Original-Message-ID: X-Original-References: <3c6e8475-4405-8762-9f8d-37ac7f972e38@debian.org> <20200218173150.GA636415@jcristau-z4> <20200409094721.GY22937@topinambour.cristau.org> <20200701163303.GP1984@topinambour.cristau.org> Xref: csiph.com linux.debian.maint.python:12713 linux.debian.bugs.dist:1016544 > > > Do you need any help in coordinating with the packaged extensions, > > > testing changes, preparing patches? a lot of time has passed since we > > > started asking about mercurial and python3 and it is becoming the only > > > reverse-dependency of several packages that could be removed if > > > mercurial switched to py3k. > > > > > Getting an uptodate list of extensions and their status wrt porting both > > upstream and in Debian would be useful. I've spent some time looking at > > hgsubversion a few weeks ago but there's a ton of work and I don't > > actually use it so I've kind of given up on that; I forget what the > > status is on others. > > will look into the rdeps of mercurial once 5.4.1-1+exp1 hits the archive I've rebuilt all rdeps of mercurial against the python3 version uploaded to unstable; results are: 2020/07/05 00:28:22 Build results: 2020/07/05 00:28:22 PASSED: salt 2020/07/05 00:28:22 PASSED: golang-github-masterminds-vcs-dev 2020/07/05 00:28:22 PASSED: pepper 2020/07/05 00:28:22 PASSED: python-hglib 2020/07/05 00:28:22 PASSED: git-remote-hg 2020/07/05 00:28:22 PASSED: haskell-filestore 2020/07/05 00:28:22 PASSED: composer 2020/07/05 00:28:22 PASSED: yotta 2020/07/05 00:28:22 PASSED: ros-rosinstall 2020/07/05 00:28:22 PASSED: check-manifest 2020/07/05 00:28:22 PASSED: jags 2020/07/05 00:28:22 PASSED: setuptools-scm 2020/07/05 00:28:22 PASSED: reposurgeon 2020/07/05 00:28:22 PASSED: devpi-common 2020/07/05 00:28:22 PASSED: firmware-microbit-micropython 2020/07/05 00:28:22 PASSED: python-hgapi 2020/07/05 00:28:22 PASSED: hgsubversion 2020/07/05 00:28:22 PASSED: ros-wstool 2020/07/05 00:28:22 PASSED: ros-vcstools 2020/07/05 00:28:22 FAILED: hg-git (see buildlogs/hg-git_0.8.12-1.2) 2020/07/05 00:28:22 FAILED: meson (see buildlogs/meson_0.54.3-1) (build logs and artifacts are at https://people.debian.org/~morph/mercurial_python3/ ) hg-git is RC and not in testing since mid-December, and meson is i think a real error, since without mercurial depending on python2 now the build fails to find that executable Tbh, i think it's time to just rip the bandaid and upload mercurial python3 to unstable, and deal with the consequences there (i volunteer to do so); you mentioned hgsubversion as a potential blocker: that package are popcon on 56, i dont believe such a minor package should hold progress with the py2removal effort (I've added debian-python@ to gather their input on this). I do understand the rebuild results are not conclusive on the python3 migration (after all hgsubversion rebuilds fine with py3k mercurial, which also raises the questions of why it b-d on it since it clearly doesnt use it, but i'm digressing), but i think it's better to just go ahead and upload the experimental version to unstable and see what's the impact there What do people think about this? Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi