On 23/01/2019 01:00, Douglas R. Reno via blfs-dev wrote: > > On 1/22/19 1:51 PM, Douglas R. Reno via blfs-dev wrote: >> Hi Guys, >> >> >> It seems that NetworkManager needs the 'gi' Python 2 module from >> PyGObject-3.30.4. Checking the file mentioned in the error below shows that >> it's a python2 file. >> >> >> [365/879] Generating nm-property-docs.xml with a custom command. >> FAILED: libnm/nm-property-docs.xml >> env -i >> GI_TYPELIB_PATH=/sources/NetworkManager-1.14.4/NetworkManager-1.14.4/buil >> d/libnm >> LD_LIBRARY_PATH=/sources/NetworkManager-1.14.4/NetworkManager-1.14.4/bui >> ld/libnm >> /sources/NetworkManager-1.14.4/NetworkManager-1.14.4/libnm/generate-set >> ting-docs.py --lib-path >> /sources/NetworkManager-1.14.4/NetworkManager-1.14.4/bui >> ld/libnm --gir libnm/NM-1.0.gir --output libnm/nm-property-docs.xml >> Traceback (most recent call last): >> File >> "/sources/NetworkManager-1.14.4/NetworkManager-1.14.4/libnm/generate-sett >> ing-docs.py", line 22, in <module> >> import gi >> ImportError: No module named gi >> ninja: build stopped: subcommand failed. >> 227.5 Elasped Time - NetworkManager-1.14.4 >> >> Pierre, can you restore the Python 2 module please? Otherwise I suppose we >> could try porting the python scripts in NetworkManager to Python3 instead... >> >> Thank you, >> >> Douglas R. Reno >> > Note that this seems to affect libpeas as well. libpeas needs BOTH modules / > versions to be present.
I'd rather try to have generate-setting-docs.py use python3. Of course, if it is not possible, I'll revert to build the python2 module for pygobject3. In this case, python2 should be recommended for nm too. I understand the changes I have made to the python modules can lead to some instability and I hope it is not too much an inconvenience. I think it is worth it to get rid as much as possible of P2. Regards Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
