Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime. Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2 To help planning, we'd like to know the plans for bzr's future. Specifically: - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) - What are the upstream/community plans/timelines regarding Python 3? - What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) This bug is filed semi-automatically, and might not have all the context specific to bzr. If you need anything from us, or something is unclear, please mention it here. Thank you.
It looks like the "breezy" project is the way forward. https://en.wikipedia.org/wiki/Breezy_(software) https://www.breezy-vcs.org/ https://www.phoronix.com/scan.php?page=news_item&px=GNU-Bazaar-Breezy It is claimed that breezy works with Python3; I have not tested or verified this.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Do you have a plan to package breezy as a replacement of bzr package? Or is it fully compatible so the new package is not needed?
What is the plan? Can I help you somehow?
Since the recent retirement of python-pwntools and dpm-contrib-admintools, bzr is now the last remaining dependent package of python2-paramiko, which is already uninstallable in rawhide due to the removal of python2-ipaddress. I would like to drop the python2-paramiko package from both f31 and rawhide. I'll do rawhide today as that won't make anything any more broken. Obviously I'd like to do f31 before its release. Any comments/objections?
OK, so python2-ipaddress came back but I'd still like to drop python2-paramiko. Holding off for now though.
Paul, you can follow https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Process_for_abandoning_Python_2_subpackages
Miro, thanks for that. I'll bear that in mind if this package lingers around much longer.
https://bugs.launchpad.net/bzr/+bug/1696545 Jelmer Vernooij (jelmer) wrote on 2018-09-14: Full Python 3 support has now landed in trunk.
I'm looking into packaging brz (breezy), but I have no interest in maintaining it.
Created attachment 1611475 [details] Spec file for breezy, a replacement of bzr Here is a spec file for breeze. It needs python3-sphinx-epytext (not yet packaged, i can do that if needed), but otherwise appears to work. I don't have any bzr projects, so I have not done much testing. Anybody interested in maintaining breeze?
Maybe you, Petr? You seem to be the latest maintainer who committed to bzr (arguably not recently).
I've asked on the devel mailing list for volunteers: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/OUMBR2LWRMWWXRWU4S4DREVHNVKYQGJV/
Hi guys. I apologize for my late response. I wanted already remove myself from maintainers of this rpm but the system doesn't allow me to do that as I am not admin of this component - just committer (isn't that bug?). To be honest, I am not interested about bzr and related rpms. I plan to orphan some additional rpms - git-remote-bzr especially. I am now spending all my extra free time I can around mercurial, so I cannot do anything here anyway.
(In reply to pstodulk from comment #14) > Hi guys. I apologize for my late response. I wanted already remove myself > from maintainers of this rpm but the system doesn't allow me to do that as I > am not admin of this component - just committer (isn't that bug?). See https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/7NLZTF4GUFBYXCFCQVFJWIXGHSQ44EDR/ I can remove you, shall I?
Yes, remove me please. Thanks for that and for the info.
(In reply to pstodulk from comment #14) > Hi guys. I apologize for my late response. I wanted already remove myself > from maintainers of this rpm but the system doesn't allow me to do that as I > am not admin of this component - just committer (isn't that bug?). To be > honest, I am not interested about bzr and related rpms. I plan to orphan > some additional rpms - git-remote-bzr especially. I am now spending all my > extra free time I can around mercurial, so I cannot do anything here anyway. The breezy package provides a git-remote-bzr implementation.
I have taken a look at the spec and successfully attempted to build it in a rawhide container. As I already maintain bzr in RHEL, I think it would be quite logical for me to take the new brz package in Fedora. I have tested breezy against the official bazaar repository and checking out into a branch gives this error: [root@b396e406a2ce bzr]# brz branch lp:bzr bzr.dev brz: ERROR: launchpadlib is required for Launchpad API access. Please install the launchpadlib package. Can be reproduced as follows: $ bzr init-repo bzr $ cd bzr $ bzr branch lp:bzr bzr.dev Should I start with packaging python3-sphinx-epytext?
And apparently also https://pypi.org/project/launchpadlib/
(In reply to Marcel Plch from comment #18) > I have taken a look at the spec and successfully attempted to build it in a > rawhide container. > As I already maintain bzr in RHEL, I think it would be quite logical for me > to take the new brz package in Fedora. > > I have tested breezy against the official bazaar repository and checking out > into a branch gives this error: > > [root@b396e406a2ce bzr]# brz branch lp:bzr bzr.dev > brz: ERROR: launchpadlib is required for Launchpad API access. Please > install the launchpadlib package. > > Can be reproduced as follows: > $ bzr init-repo bzr > $ cd bzr > $ bzr branch lp:bzr bzr.dev > > Should I start with packaging python3-sphinx-epytext? You could try install launchpadlib using pip3 and see which other dependencies it drags in. And then take it from there. more launchpadlib-1.10.7-py3.7.egg-info/requires.txt :::::::::::::: launchpadlib-1.10.7-py3.7.egg-info/requires.txt :::::::::::::: httplib2 keyring lazr.restfulclient>=0.9.19 lazr.uri setuptools testresources wadllib
wadllib is only used in launchpadlib.testing (Testing API allows fake data to be used in unit tests.) testresources is only used in launchpadlib.tests (actual tests)
All new packages approved.
$ bzr branch lp:bzr bzr.dev You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See "bzr help launchpad-login". brz: ERROR: The branch lp:bzr has no revision None. I have checked and it should proceed https://stackoverflow.com/questions/21146888/how-can-i-clone-a-public-launchpad-repository-without-login Not sure what does the "brz: ERROR: The branch lp:bzr has no revision None" mean. I've only found https://bugs.launchpad.net/bzr/+bug/578005 so far :(
$ bzr init-repo brz Shared repository with trees (format: 2a) Location: shared repository: brz $ cd brz/ $ bzr branch lp:brz brz.dev You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See "bzr help launchpad-login". (shows progressbar for a while) brz: ERROR: The branch lp:brz has no revision None.
I've reproduced the problem with pip-installed breezy as well, reported upstream: https://bugs.launchpad.net/brz/+bug/1844684
(In reply to Miro Hrončok from comment #24) > $ bzr init-repo brz > Shared repository with trees (format: 2a) > Location: > shared repository: brz > $ cd brz/ > $ bzr branch lp:brz brz.dev > You have not informed bzr of your Launchpad ID, and you must do this to > write to Launchpad or access private data. See "bzr help launchpad-login". > (shows progressbar for a while) > brz: ERROR: The branch lp:brz has no revision None. Should be "brz branch lp:bzr" "brz" is the breezy command and "bzr" is the bazaar command. [vek@mybox xxx]$ brz branch lp:bzr You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See "bzr help launchpad-login". Branched 6622 revisions.
The specfile attached adds a backwards compatibility symbolic link, so both bzr and brz means breezy. Where is your example from? Does it run on Python 3.8?
(In reply to Miro Hrončok from comment #27) > The specfile attached adds a backwards compatibility symbolic link, so both > bzr and brz means breezy. > > > Where is your example from? Does it run on Python 3.8? No; 3.7 on Fedora 30. "brz branch lp:brz" works as well, by the way.
Automation has figured out the package is retired in rawhide. If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement