Sunday, April 28, 2024
 Popular · Latest · Hot · Upcoming
0
rated 0 times [  0] [ 0]  / answers: 1 / hits: 1933  / 1 Year ago, sun, december 25, 2022, 9:01:23

I upgraded to 11.10 yesterday, and since then the hgsubversion extension of mercurial no longer find the python bindings.



abort: no compatible bindings available:

Subversion 1.5.0 or later required, but no bindings were found
Subvertpy 0.7.4 or later required, but not found

Please install either Subvertpy or the Subversion Python SWIG bindings!


However, both this packages are currently installed (version 1.6.12dfsg-4ubuntu5 for python-subversion and version 0.8.3-1 for python-subvertpy).



Initially I was using hgsubversion pulled from their mercurial repository, which I had to update following mercurial update, so I'm now at revision 836 (October 12th). As I saw there was now a package for hgsubversion in the repository (don't know when it has been added), I tried with that version as well, but to no avail.



So far, here's what I tried to fix the problem or help diagnose:




  1. I reinstalled subversion, mercurial, python and both bindings package.

  2. I noticed I had python 2.6 and python 2.7, so I removed python 2.6.

  3. Forcing the use of Subvertpy with HGSUBVERSION_BINDINGS="Subvertpy": abort: Subvertpy 0.7.4 or later required, but not found!

  4. Forcing the use of SWIG bindings with HGSUBVEERSION_BINDINGS="SWIG": abort: Subversion 1.5.0 or later required, but no bindings were found!

  5. Tried using alternatively both the Ubuntu package version of hgsubversion (1.2.1-2.1) and the latest version pulled from hgsbuversion repository.



Does anyone know why would that happen and what should I have to do to fix it?



Thank you.



Edit: forgot a few version informations



python --version
Python 2.7.2+


package version: 2.7.2-5ubuntu1



hg version
Mercurial Distributed SCM (version 1.9.1)


package version: 1.9.1-1ubuntu0.1


More From » 11.10

 Answers
4

Finally found the cause: it was coming from the line in my hgrc defining the use of the hgview extension.



After the upgrade, my old hgview= line to activate failed (it wouldn't find the extension), and I had replaced it with hgext.hgview=/usr/share/pyshared/hgext/hgview.py after having located it.



As there was no longer any hgview related error in the log afterwards, I didn't think much about it. However that was the cause of my hgsubversion not finding the bindings, though I still don't know why.



Thus, removing that line in my .hgrc file solved the problem.


[#42790] Sunday, December 25, 2022, 1 Year  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
whoppinolo

Total Points: 93
Total Questions: 113
Total Answers: 107

Location: Cyprus
Member since Mon, Oct 24, 2022
2 Years ago
whoppinolo questions
Tue, Feb 14, 23, 08:30, 1 Year ago
Wed, Sep 28, 22, 06:56, 2 Years ago
Fri, May 27, 22, 01:55, 2 Years ago
Tue, Oct 12, 21, 09:33, 3 Years ago
;