On Sat, Jul 29, 2017 at 12:23:33AM +0100, Ken Moffat wrote: > I'm just flagging this up here, in the hope that somebody can help > me understand what the hell changed. > > I'm doing a fresh build of svn on one of my test machines - I've > built this same version of gimp-help several times this year, last > time used packages from late May including Python-2.7.13 which is > what I've got on this build. > > Today it decided to fail: > make[1]: Entering directory > '/scratch/working/gimp-help-2.8.2/quickreference' > /bin/mkdir -p xml > ../tools/xml2po.py -p po/de.po ./gimp-keys.xml > > xml/gimp-keys-de.xml > Traceback (most recent call last): > File "../tools/xml2po.py", line 190, in <module> > main(sys.argv[1:]) > File "../tools/xml2po.py", line 87, in main > from xml2po import Main > File "/scratch/working/gimp-help-2.8.2/tools/xml2po/__init__.py", > line 27, in <module> > import libxml2 > ImportError: No module named libxml2 > [snip]
And then itstool similarly failed to configure - it too needs Python module libxml2, but this time it was explicitly looking in the 2.7 site-packages. I've found what changed in my scripts (I didn't remember anything changing in this area, but fortunately in my git commit messages I now try to give some details) - I had decided to pick up ALL of the optional switches in libxml2, in particular using python3. And that caused the libxml2.py module to be in /usr/lib/python3.6/site-packages/ whereas both gimp-help and itstool need the Python2 module (and I guess a lot of other gtk packages will be in the same position. And when I said I'd not had libxml2.py I obviously didn't look at my libxml2 logs. So, sorted. Thanks for listening. ĸen -- I live in a city. I know sparrows from starlings. After that everything is a duck as far as I'm concerned. -- Monstrous Regiment -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
