Bug#937009: [Python-apps-team] Bug#937009: mercurial: Python2 removal in sid/bullseye
> > > 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
Bug#937009: [Python-apps-team] Bug#937009: mercurial: Python2 removal in sid/bullseye
> Yeah basically fixing the RC bug in sid took priority and then I ran out > of steam before merging back to experimental. I also want to figure out > how to deal with #961245 there going forward. I've merged debian/master into debian/experimental, merged the changes done in 5.4-1+exp1 and uploaded the result to experimental > > 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 -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#937009: [Python-apps-team] Bug#937009: mercurial: Python2 removal in sid/bullseye
On Sat, Jun 27, 2020 at 22:13:10 -0400, Sandro Tosi wrote: > Hey Julien, > > On Thu, Apr 9, 2020 at 5:47 AM Julien Cristau wrote: > > > > On Thu, Apr 9, 2020 at 01:17:06 -0400, Sandro Tosi wrote: > > > > > Hello Julien, > > > > > > On Tue, Feb 18, 2020 at 12:33 PM Julien Cristau > > > wrote: > > > > Before switching in sid I'd want to: > > > > - be able to use the python3 version myself > > > > - give extensions some time to figure out their own switch > > > > - ideally not regress significant functionality; e.g. python-subversion > > > > is still not available for python3 > > > > > > > > I don't know what that means in terms of timeframe, it may or may not > > > > happen in time for bullseye, but I'm also not in a rush and I'd rather > > > > not break stuff by switching too early. > > > > > > I see that python3-enabled mercurial has been in experimental for a 3 > > > weeks now, how's it going? it would greatly help progress with the > > > overall py2removal effort if we could start planning to upload that > > > mercurial release to sid. > > > > > > Can you share with us your plans here? > > > > > Still need to coordinate with packaged extensions. > > what happened to the python3 port that was uploaded in experimental as > part of 5.4-1+exp1 ? it seems it got lost when 5.4-2 was uploaded to > unstable? (btw debian/experimental in git doesnt seem to be up-to-date > with what reached the archived) > Yeah basically fixing the RC bug in sid took priority and then I ran out of steam before merging back to experimental. I also want to figure out how to deal with #961245 there going forward. > 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. Cheers, Julien
Bug#937009: [Python-apps-team] Bug#937009: mercurial: Python2 removal in sid/bullseye
Hey Julien, On Thu, Apr 9, 2020 at 5:47 AM Julien Cristau wrote: > > On Thu, Apr 9, 2020 at 01:17:06 -0400, Sandro Tosi wrote: > > > Hello Julien, > > > > On Tue, Feb 18, 2020 at 12:33 PM Julien Cristau wrote: > > > Before switching in sid I'd want to: > > > - be able to use the python3 version myself > > > - give extensions some time to figure out their own switch > > > - ideally not regress significant functionality; e.g. python-subversion > > > is still not available for python3 > > > > > > I don't know what that means in terms of timeframe, it may or may not > > > happen in time for bullseye, but I'm also not in a rush and I'd rather > > > not break stuff by switching too early. > > > > I see that python3-enabled mercurial has been in experimental for a 3 > > weeks now, how's it going? it would greatly help progress with the > > overall py2removal effort if we could start planning to upload that > > mercurial release to sid. > > > > Can you share with us your plans here? > > > Still need to coordinate with packaged extensions. what happened to the python3 port that was uploaded in experimental as part of 5.4-1+exp1 ? it seems it got lost when 5.4-2 was uploaded to unstable? (btw debian/experimental in git doesnt seem to be up-to-date with what reached the archived) 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. We're here to help and assist, just let us know how. Cheers, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#937009: mercurial: Python2 removal in sid/bullseye - reopen 937009
Control: reopen -1 This bug was closed, but the package has still some dependencies towards Python2 packages, in details: (source:mercurial)Build-Depends->python-all-dev (source:mercurial)Build-Depends->python-docutils (source:mercurial)Build-Depends->python-roman (source:mercurial)Testsuite-Triggers->python-docutils (source:mercurial)Testsuite-Triggers->python-pygments (source:mercurial)Testsuite-Triggers->python-subversion (source:mercurial)Testsuite-Triggers->python2.7-dev (binary:mercurial-common)Depends->python2:any (binary:mercurial-common)Depends->python2:any (binary:mercurial)Depends->python2 (binary:mercurial)Depends->python2 (binary:mercurial)Depends->python2:any (binary:mercurial)Depends->python2:any Re-opening, so that they can be taken care of.
Bug#937009: [Python-apps-team] Bug#937009: mercurial: Python2 removal in sid/bullseye
On Thu, Apr 9, 2020 at 01:17:06 -0400, Sandro Tosi wrote: > Hello Julien, > > On Tue, Feb 18, 2020 at 12:33 PM Julien Cristau wrote: > > Before switching in sid I'd want to: > > - be able to use the python3 version myself > > - give extensions some time to figure out their own switch > > - ideally not regress significant functionality; e.g. python-subversion > > is still not available for python3 > > > > I don't know what that means in terms of timeframe, it may or may not > > happen in time for bullseye, but I'm also not in a rush and I'd rather > > not break stuff by switching too early. > > I see that python3-enabled mercurial has been in experimental for a 3 > weeks now, how's it going? it would greatly help progress with the > overall py2removal effort if we could start planning to upload that > mercurial release to sid. > > Can you share with us your plans here? > Still need to coordinate with packaged extensions. Cheers, Julien
Bug#937009: [Python-apps-team] Bug#937009: mercurial: Python2 removal in sid/bullseye
Hello Julien, On Tue, Feb 18, 2020 at 12:33 PM Julien Cristau wrote: > Before switching in sid I'd want to: > - be able to use the python3 version myself > - give extensions some time to figure out their own switch > - ideally not regress significant functionality; e.g. python-subversion > is still not available for python3 > > I don't know what that means in terms of timeframe, it may or may not > happen in time for bullseye, but I'm also not in a rush and I'd rather > not break stuff by switching too early. I see that python3-enabled mercurial has been in experimental for a 3 weeks now, how's it going? it would greatly help progress with the overall py2removal effort if we could start planning to upload that mercurial release to sid. Can you share with us your plans here? I understand and agree (in general) with your desire to now break anything, but we're also at the tail end of the py2removal process, so we are at a point where something may be broken, for some period of time. Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#937009: mercurial: Python2 removal in sid/bullseye
On Tue, 18 Feb 2020 18:31:50 +0100 Julien Cristau wrote: > On Thu, Oct 31, 2019 at 02:25:22PM +0100, Matthias Klose wrote: > > Julian, you added the py2keep tag. Reading the upstream mail for the 5.2 > > release, it looks like the release will happen next month. So why keeping > > it as Python2 version for the bullseye release? > > Before switching in sid I'd want to: > - be able to use the python3 version myself > - give extensions some time to figure out their own switch > - ideally not regress significant functionality; e.g. python-subversion > is still not available for python3 > > I don't know what that means in terms of timeframe, it may or may not > happen in time for bullseye, but I'm also not in a rush and I'd rather > not break stuff by switching too early. I would be great if you could ship Mercurial as dual Python 2 + Python 3 package but with /usr/bin/hg being Python 2, so that users can try the Python 3 version and extensions can be used with either. As it is now, it’s not possible e.g. to ship TortoiseHg at all since it needs core Mercurial modules in Python 3 (since Python 2 dependencies it might use have already been removed). -- Cheers, Andrej
Bug#937009: mercurial: Python2 removal in sid/bullseye
On Thu, Oct 31, 2019 at 02:25:22PM +0100, Matthias Klose wrote: > Julian, you added the py2keep tag. Reading the upstream mail for the 5.2 > release, it looks like the release will happen next month. So why keeping > it as Python2 version for the bullseye release? Before switching in sid I'd want to: - be able to use the python3 version myself - give extensions some time to figure out their own switch - ideally not regress significant functionality; e.g. python-subversion is still not available for python3 I don't know what that means in terms of timeframe, it may or may not happen in time for bullseye, but I'm also not in a rush and I'd rather not break stuff by switching too early. Cheers, Julien
Bug#937009: mercurial: Python2 removal in sid/bullseye
Julian, you added the py2keep tag. Reading the upstream mail for the 5.2 release, it looks like the release will happen next month. So why keeping it as Python2 version for the bullseye release?
