Created attachment 1739728 [details] meld SVN fix. Description of problem: Post upgrade to Fedora 33, meld/svn combo no longer works due to Python API deprecation. See: https://gitlab.gnome.org/GNOME/meld/-/issues/526 For some odd reason I couldn't clean patch meld using the supplied fix so I simply manually created a new patch. As far as I can see, it works cleanly. Version-Release number of selected component (if applicable): meld-3.21.0-5.fc33.noarch How reproducible: Always Steps to Reproduce: Run meld in SVN root directory. Actual results: Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/meld/task.py", line 110, in iteration ret = task() File "/usr/lib/python3.9/site-packages/meld/vc/_vc.py", line 277, in refresh_vc_state self._update_tree_state_cache(path) File "/usr/lib/python3.9/site-packages/meld/vc/svn.py", line 188, in _update_tree_state_cache for entry in target.iter(tag="entry"): AttributeError: 'xml.etree.ElementTree.Element' object has no attribute 'getchildren'
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
FEDORA-2022-00e2dd59f2 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-00e2dd59f2
FEDORA-2022-d4813ab9e3 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d4813ab9e3
FEDORA-2022-d4813ab9e3 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-d4813ab9e3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d4813ab9e3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-00e2dd59f2 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-00e2dd59f2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-00e2dd59f2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-00e2dd59f2 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-d4813ab9e3 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
Thanks. - Gilboa