Bug 1908453

Summary: meld: svn broken due to python API changes. Patch attached.
Product: [Fedora] Fedora Reporter: Gilboa Davara <gilboad>
Component: meldAssignee: Dominic Hopf <dmaphy>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: bdpepple, christoph.wickert, dmaphy, lkundrak, oliver
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: meld-3.21.2-1.fc36 meld-3.21.2-1.fc35 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-09 01:23:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
meld SVN fix. none

Description Gilboa Davara 2020-12-16 17:57:00 UTC 
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'
Comment 1 Ben Cotton 2021-11-04 14:04:24 UTC 
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.
Comment 2 Ben Cotton 2021-11-04 14:33:26 UTC 
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.
Comment 3 Ben Cotton 2021-11-04 15:31:13 UTC 
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.
Comment 4 Ben Cotton 2021-11-30 18:44:00 UTC 
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.
Comment 5 Fedora Update System 2022-06-30 07:37:12 UTC 
FEDORA-2022-00e2dd59f2 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-00e2dd59f2
Comment 6 Fedora Update System 2022-06-30 07:37:13 UTC 
FEDORA-2022-d4813ab9e3 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d4813ab9e3
Comment 7 Fedora Update System 2022-07-01 02:01:37 UTC 
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.
Comment 8 Fedora Update System 2022-07-01 02:09:57 UTC 
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.
Comment 9 Fedora Update System 2022-07-09 01:23:13 UTC 
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.
Comment 10 Fedora Update System 2022-07-09 01:39:59 UTC 
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.
Comment 11 Gilboa Davara 2022-07-13 13:57:38 UTC 
Thanks.

- Gilboa