Arch Linux

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!
Tasklist

FS#15044 - [subversion] Python 2.6 compatibility warning fix

Attached to Project: Arch Linux
Opened by Andrzej Giniewicz (Giniu) - Wednesday, 10 June 2009, 13:35 GMT
Last edited by Paul Mattal (paul) - Monday, 08 February 2010, 13:24 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Paul Mattal (paul)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

When using Mercurial, especially hg-svn or similar conversion tools, it produces annoying

/usr/lib/python2.6/site-packages/svn/core.py:47: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
self.message = message

and also breaks some test suites that rely on clean char-to-char-correct output from commands.

Unfortunately upstream decided to not count breaking test suites of other apps as bug and delayed fix for svn 1.7 (or later!)... There is patch for it in comment 6 in this bug report for Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=487732#c6 - looking at it, it just filters out deprecation warning and thus fixes svn-python test suites and makes it good looking again - would be cool to integrate it in next subversion package, keeping such deprecation warnings not dealt with can be bad for distro that is as current as arch is, and who knows - maybe we would have python 3 here actually before subversion 1.7, 1.8, 5.2 or whenever they decide to fix this? :)
This task depends upon

Closed by  Paul Mattal (paul)
Monday, 08 February 2010, 13:24 GMT
Reason for closing:  Implemented
Additional comments about closing:  Patch added for 1.6.9-1, soon to be in extra.
Comment by Andrzej Giniewicz (Giniu) - Wednesday, 10 June 2009, 13:41 GMT
well, maybe I didn't stated it too well, I mean that it still makes test suites for many python apps using svn fail, and will be making it fail for long time unless warning will be filtrated or fixed. Filtration seems enough in that case, this by no means fixes python 3 compatibility. Last sentence was just my comment on the situation :)
Comment by Paul Mattal (paul) - Sunday, 07 February 2010, 22:07 GMT
Hmm. I see your point.

It probably makes sense here. Will add for 1.6.9-1.

It bothers me a little to be suppressing deprecation warnings, but since they're just deprecation warnings, and svn doesn't plan to fix them, I'm okay with it.

Loading...