Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#23185 - [meld] can not compare svn copy
Attached to Project:
Arch Linux
Opened by Lincoln Zhang (CrazyPandar) - Tuesday, 08 March 2011, 10:56 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 30 April 2011, 14:39 GMT
Opened by Lincoln Zhang (CrazyPandar) - Tuesday, 08 March 2011, 10:56 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 30 April 2011, 14:39 GMT
|
DetailsDescription:
meld can not compare svn copy Additional info: * meld 1.4.0-3 Steps to reproduce: meld-->[File]-->[New...]->[Version Control Browser] -->Browse to my svn copy-->[OK] Nothing happens. |
This task depends upon
Can you be more specific as to what you expect and take a screenshot of what actually happens?
meld-1.png shows 'svn diff' result.
meld-2.png and meld-3.png show meld diff result.
In meld-3.png the result shows nothing.
And I found another thing, If I change working directory to the svn copy and then excute meld, it works.
But it should display the path to your VC directory anyhow...
Have you tried using meld on the same directory but on another computer?
Also it should be noted that version control comparison does work as correctly when starting meld from the cli with a singular file or directory. e.g:
meld some-file.lisp
meld my-project/
I'll be happy to actually respond to any questions and assist with getting this resolved.
Unfortunately, I will have no time to investigate this the upcoming week.
Since this sounds very much like an upstream issue, could you trying reporting it there and post the link of your report here?
On my office workstation, SVN's version is 1.6.15, python's version is 2.7.
Maybe it is caused by python upgrade.
The issue happens for me with Subversion and Git repositories, however, opening up a mercurial repository via the UI works just fine. Strange...
I'll post again if I get any hits from an upstream bug report.
Lincoln: will a mercurial repository work for you as well?
Then I will close this bug as there is apparently not much we can do from a packaging viewpoint.