Re: List of Python 2 packages to be removed mid-November (= in a week)
No idea what to do with pdf-stapler and what can happen in future from upstream. At least, they are aware of python3. Am 07.11.19 um 13:01 schrieb Petr Viktorin: raphgro pdf-stapler (→ PY2) python2-staplelib (→ PY2) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
On Thu, Nov 7, 2019 at 7:02 AM Petr Viktorin wrote: > jsmith >asterisk > (→ PY2) > asterisk-* (→ asterisk → PY2) > Asterisk has very few dependencies on Python (just some contributed scripts for use in debugging reference counters in the code, if I recall correctly). That being said, I'd love an extension to work with the Asterisk developers to get their scripts moved over to Python 3. -Jared ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
On 11/7/19 2:34 PM, Miro Hrončok wrote: On 07. 11. 19 13:59, Felix Schwarz wrote: Am 07.11.19 um 13:01 schrieb Petr Viktorin: If this took you by surprise, don't panic. It's possible to change the default. Let us know and we'll work things out. Somehow I feel like I don't understand the report – or we are approaching an (almost) unmitigated disaster here: There are so many "high profile" packages which are slated for removal that we might wipe out half of our Python packaging eco system. What are the high profile packages you are talking about? Fedora - Combined wiht the modules insanity, you guys seem to be keen on shifting Fedora into non-usability and into non-importance. Ralf ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
On Thu, Nov 07, 2019 at 01:01:09PM +0100, Petr Viktorin wrote: > Dear maintainers, > here is an updated list of packages that (transitively, at build or run > time) require Python 2 and have not yet got a FESCo exception to do so. > If you were bcced on this e-mail, it affects one or more of your packages. ...snip... > kevin > pylibacl > (→ PY2) ...snip... > pyxattr > python2-pyxattr (→ PY2) > rdiff-backup > (→ PY2) We requested an exception here for these: https://pagure.io/fesco/issue/2262 kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
On 07. 11. 19 14:59, Felix Schwarz wrote: Am 07.11.19 um 14:57 schrieb Felix Schwarz: Is there some automation to remove "python2-" subpackages or do you plan some "single hero"-style changes? If neither what is the plan for maintainers who just don't do anything? I should do more reading before replying to emails :-/ Change description says: "The package removal will be executed in an automated fashion." However, there are some things that still need to be considered here. 1. Automation is not 100 % accurate (some packages are very custom), there is a great deal of single-hero-style adapting of the automation results. I've been doing this for a ~year. I use Zbyszek's https://pagure.io/pyrenamer/blob/master/f/depython2ize.py and adapt the package by hand. 2. Some maintainers prefer a singlespec with %ifs and our automation just deletes stuff. 3. Some packages FTBFS for unrelated reasons. 4. Some packagers will be angry if we touch their packages. They will say we are militant, hostile or that we haven't warned them enough. They will say that they were working on porting. Unfortunately, this is an arguably controversial change and we anticipate push back after it gets done. What **I think** we'll do is that once the deadline passes, we'll say "remove your Python 2 packages from this list and don't care about the dependencies". A great amount of packages is maintained by the SIG and we can handle it. Another great amount is maintained by maintainer who actually want to do this. For the rest, we might create bugzillas like we do here: https://bugzilla.redhat.com/showdependencytree.cgi?id=PY2REMOVAL_resolved=1 Note that this is not the current plan, but just my rough thoughts. The truth is, the "execution" of this change is still not fully figured out. We'll keep devel@ informed. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
Am 07.11.19 um 14:57 schrieb Felix Schwarz: > Is there some automation to remove "python2-" subpackages or do you plan some > "single hero"-style changes? If neither what is the plan for maintainers who > just don't do anything? I should do more reading before replying to emails :-/ Change description says: "The package removal will be executed in an automated fashion." sorry for the noise Felix ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
Am 07.11.19 um 14:47 schrieb Miro Hrončok: > On 07. 11. 19 14:41, Felix Schwarz wrote: >> However the wiki page says: >> "All packages depending on any python2 package will be removed." > > All "binary" packages. (...) >> So maybe I just misunderstood the change. What happens when a package like >> python-six still produces a Python 2 subpackage after $CUTOFF_DATE ? > > We'll remove python2-six and keep python3-six. Thank you very much for the clarification. But how exactly will you ensure that the python2 subpackage is going away? (not just python-six but regarding all the other python packages) Is there some automation to remove "python2-" subpackages or do you plan some "single hero"-style changes? If neither what is the plan for maintainers who just don't do anything? > Sorry for the confusion. Thank you for your explanation + all the preparation leading to this step. Felix ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
On 07. 11. 19 14:41, Felix Schwarz wrote: Hi Miro, Am 07.11.19 um 14:34 schrieb Miro Hrončok: We actually are wiping out the entire Python 2 ecosystem here, that is the point. Ok, maybe I misunderstood the change. Just to be clear: I'm fine with the Python 2 package removal (though I expect I'll continue to develop Python 2 code outside of Fedora for many years to come). However the wiki page says: "All packages depending on any python2 package will be removed." All "binary" packages. To me this means if there is a python2-six subpackage after a certain cutoff date we also remove the actual Fedora "python-six" package because it produces a Python 2 subpackage which can not be built any longer. In that sense I feel like "python3-six" is a high-profile package because its removal would cause quite a lot of dependent packages to be removed. So maybe I just misunderstood the change. What happens when a package like python-six still produces a Python 2 subpackage after $CUTOFF_DATE ? We'll remove python2-six and keep python3-six. Sorry for the confusion. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
Hi Miro, Am 07.11.19 um 14:34 schrieb Miro Hrončok: > We actually are wiping out the entire Python 2 ecosystem here, that is the > point. Ok, maybe I misunderstood the change. Just to be clear: I'm fine with the Python 2 package removal (though I expect I'll continue to develop Python 2 code outside of Fedora for many years to come). However the wiki page says: "All packages depending on any python2 package will be removed." To me this means if there is a python2-six subpackage after a certain cutoff date we also remove the actual Fedora "python-six" package because it produces a Python 2 subpackage which can not be built any longer. In that sense I feel like "python3-six" is a high-profile package because its removal would cause quite a lot of dependent packages to be removed. So maybe I just misunderstood the change. What happens when a package like python-six still produces a Python 2 subpackage after $CUTOFF_DATE ? Felix ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
On 07. 11. 19 13:59, Felix Schwarz wrote: Am 07.11.19 um 13:01 schrieb Petr Viktorin: If this took you by surprise, don't panic. It's possible to change the default. Let us know and we'll work things out. Somehow I feel like I don't understand the report – or we are approaching an (almost) unmitigated disaster here: There are so many "high profile" packages which are slated for removal that we might wipe out half of our Python packaging eco system. What are the high profile packages you are talking about? We actually are wiping out the entire Python 2 ecosystem here, that is the point. However I hope that I might misinterpret the report: pviktori python-six python2-six (→ PY2) The spec file says: # python2 is enabled by default, Fedora 32+ exception is anticipated %bcond_without python2 However when I check the fesco tracker I don't find any issue to request the exception: https://pagure.io/fesco/issues?status=all_pattern=six It was expected, but so far no package with an exception request needed it. There are many, many more packages like python-mako and python-sqlalchemy and it would be *very* painful if they went away (as we'd have to remove *a lot* of dependent packages). All the dependent packages are listed in this report. What listed packages would be painful to remove? Note that I don't recognize libraries as high profile, unless they are needed by high profile software. If you disagree and consider a library high profile by itself, you can request an exception for that library, but unless you make a very strong case, I'd vote against. I could probably fix a few packages myself but right now I don't have any "extra powers" besides being a regular maintainer. Requesting the necessary permissions would take quite a while as I am trying to get in touch with some maintainers basically for months (without success). What packages you need to fix? The problem seems to be that even packages maintained by the Python SIG still require python2 (without fesco exception). Some of mine as well. I'm waiting for the deadline to drop them, if not other package with exception drags them in. What can I do to cut down the number of Python 2 subpackages? Wait. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
On 07. 11. 19 14:04, Jun Aruga wrote: ## What exactly is happening? The formal change proposal is here: https://fedoraproject.org/wiki/Changes/RetirePython2 Packages requiring Python 2 will be removed starting November 15 (unless they have an exception). Components with all essential subpackages removed will be retired. The removal will be (semi-)automated. Source packages only BuildRequiring removed packages will fail to build, and will be removed according to the regular FTBFS policy. Will this happen only for rawhide? How about f31, f30, f29 branch? This is a Fedora 32 change. This will only happen in rawhide. We cannot remove packages from released Fedoras anyway. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
> ## What exactly is happening? > > The formal change proposal is here: > https://fedoraproject.org/wiki/Changes/RetirePython2 > > Packages requiring Python 2 will be removed starting November 15 (unless > they have an exception). > Components with all essential subpackages removed will be retired. > The removal will be (semi-)automated. > > Source packages only BuildRequiring removed packages will fail to build, > and will be removed according to the regular FTBFS policy. Will this happen only for rawhide? How about f31, f30, f29 branch? -- Jun | He - His - Him ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November (= in a week)
Am 07.11.19 um 13:01 schrieb Petr Viktorin: > If this took you by surprise, don't panic. It's possible to change the > default. Let us know and we'll work things out. Somehow I feel like I don't understand the report – or we are approaching an (almost) unmitigated disaster here: There are so many "high profile" packages which are slated for removal that we might wipe out half of our Python packaging eco system. However I hope that I might misinterpret the report: > pviktori > python-six > python2-six (→ PY2) The spec file says: > # python2 is enabled by default, Fedora 32+ exception is anticipated > %bcond_without python2 However when I check the fesco tracker I don't find any issue to request the exception: https://pagure.io/fesco/issues?status=all_pattern=six There are many, many more packages like python-mako and python-sqlalchemy and it would be *very* painful if they went away (as we'd have to remove *a lot* of dependent packages). I could probably fix a few packages myself but right now I don't have any "extra powers" besides being a regular maintainer. Requesting the necessary permissions would take quite a while as I am trying to get in touch with some maintainers basically for months (without success). The problem seems to be that even packages maintained by the Python SIG still require python2 (without fesco exception). To be clear: This is a about packages with active upstream, which support Python 3 and just happen to have a Python 2 subpackage in Fedora rawhide. What can I do to cut down the number of Python 2 subpackages? Felix ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
List of Python 2 packages to be removed mid-November (= in a week)
Dear maintainers, here is an updated list of packages that (transitively, at build or run time) require Python 2 and have not yet got a FESCo exception to do so. If you were bcced on this e-mail, it affects one or more of your packages. The default action will be to remove such packages starting November 15. If this took you by surprise, don't panic. It's possible to change the default. Let us know and we'll work things out. The mid-November deadline is not for removing *all* of Python 2, but for getting exceptions. If you are already working to port to Python 3, sorry for the spam! But, time is running out. Consider getting an exception so the package isn't removed in November. Or remove the package (if nothing depends on it) and re-introduce it when it's ported. (We'll be happy to help, with reviews or otherwise.) If you want to remove the Python 2 package, but you're waiting for something that depends on it, please make sure you know what the maintainer(s) of the dependent package are planning to do. (Hopefully you have fewer dependents than "python27" or "python2-setuptools", and your questions can be more targeted than this e-mail.) If you want to continue using Python 2, please let us know ASAP. We can guide you through filing the FESCo exception. If you talked to us (on e-mail or Bugzilla) and think your package is fine as it is, but you don't have a FESCo exception (or a request for one), then there was a misunderstanding. We're sorry for our side of it. Please get a FESCo exception for your package. Note: Packages that BuildRequire python27, and have no other Python 2 dependencies, have a blanket exception for Fedora 32: https://pagure.io/fesco/issue/2250 They aren't listed below. Also note: Orphaned Python 2 packages also aren't listed below, but will be removed unless someone adopts them and gets an exception. ## Why the FESCo exception? It's a bit of process meant to ensure all the relevant people know that a package *and its dependencies* will stay in Fedora, despite using an (upstream-)unmaintained interpreter. With hundreds of packages, all different, we unfortunately do need a bit of bureaucracy. Due to the volume, the Python 2 removal will be *automated*, so if you have an "obvious exception", it's still important to let *humans* know, so they can adapt their automation. ## Why now? The current maintainers of python27 don't want to maintain it forever, without upstream support. But we also don't want to just drop it and let everything burn, hence all this fuss. The policy and messaging around deprecating and removing Python 2 has been getting stronger and stronger ever since the Python 3.0 release in 2008. If you still need more time, please let us know. ## What exactly is happening? The formal change proposal is here: https://fedoraproject.org/wiki/Changes/RetirePython2 Packages requiring Python 2 will be removed starting November 15 (unless they have an exception). Components with all essential subpackages removed will be retired. The removal will be (semi-)automated. Source packages only BuildRequiring removed packages will fail to build, and will be removed according to the regular FTBFS policy. https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ ## The list Here is the package breakdown sorted by maintainers. The list contains the shortest dependency path to Python 2. The arrow means "depends on". The data is based on the latest rawhide compose, so it might be a bit out of date. If you find a bogus dependency, such as a dependency that can be resolved in a non-Python 2 way, please let us know, so we can blacklist it. aarem pdf-stapler (→ PY2) python2-staplelib (→ PY2) python-PyPDF2 python2-PyPDF2 (→ PY2) python2-more-itertools (→ PY2) abbot protobuf python2-protobuf (→ PY2) abompard python-coverage python2-coverage (→ PY2) python-mako python2-mako (→ PY2) python-pysocks python2-pysocks (→ PY2) python-urllib3 python2-urllib3 (→ PY2) ajmitchell NFStest (→ PY2) alexl dbus (BuildRequires: python2-gobject → PY2) dbus-python python2-dbus (→ PY2) gnome-python2 gnome-python2-canvas (→ PY2) gnome-python2-devel (→ PY2) gnome-python2-gconf (→ PY2) gnome-python2-gnome (→ PY2) gnome-python2-gnomevfs (→ PY2) gnome-python2-desktop (→ gnome-python2-canvas → PY2) gnome-python2-gnomekeyring (→ PY2) gnome-python2-libwnck (→ PY2) gnome-python2-rsvg (→ PY2) alsadi dumb-init (BuildRequires: python2-mock → PY2) amigadave dbus (BuildRequires: python2-gobject → PY2) amluto python-musicbrainzngs python2-musicbrainzngs (→ PY2) anishpatil gnome-transliteration (→ python2-gobject → PY2) aperezbios sugar (→ PY2) sugar-cp-* (→ sugar → PY2) telepathy-salut (BuildRequires: python2-dbus → PY2) apevec pyparsing python2-pyparsing (→ PY2) python-distutils-extra
