Comment 2 for bug 91845

While Feisty may be nearing the end of its support lifetime, the problem still persists in newer releases. Did you actually test the bug before marking it invalid?

I just tried installing python-subversion-dbgsym_1.5.1dfsg1-1ubuntu2_amd64.ddeb on my machine (running Intrepid), and could easily reproduce the problem. I set a break point on svn_wc_version function and then ran the equivalent Python function. The back trace started with:

  #0 0x00007f2743c624e0 in svn_wc_version () from /usr/lib/libsvn_wc-1.so.1
  #1 0x00007f2745f45b6a in ?? ()
     from /var/lib/python-support/python2.5/libsvn/_wc.so

After adding a symlink as described in the original description (although for Python 2.5 rather than 2.4), I got the following back trace:

  #0 0x00007f6ab301e4e0 in svn_wc_version () from /usr/lib/libsvn_wc-1.so.1
  #1 0x00007f6ab5301b6a in _wrap_svn_wc_version (self=<value optimized out>,
      args=0x7f6ab6f25050) at subversion/bindings/swig/python/svn_wc.c:3123

(Note the difference in the second stack frame).