Control: tags -1 - moreinfo unreproducible Hi Christopher,
thanks for confirming my hypothesis is correct. On Sun, 12 Mar 2017 10:20:43 Christopher Swingley wrote: > FYI, this procedure allowed for the install: > > $ mkdir -p ~/tmp/local_python/bin > $ mkdir -p ~/tmp/local_python/lib > $ sudo mv /usr/local/bin/* ~/tmp/local_python/bin > $ sudo mv /usr/local/lib/python* ~/tmp/local_python/lib > $ sudo mv /usr/local/lib/libpython* ~/tmp/local_python/lib > > $ sudo apt --fix-broken install > > Then I copying everything back to /usr/local. I'd encourage you not to have that locally built python in /usr/local. It has the capacity to keep breaking upgrades and possibly also any other python- using package in Debian -- basically, anything that runs "python3". You've seen the sort of fragility that can result from it. /usr/local is designed to let the local admin override system tools but when things break, the admin keeps both pieces. Keeping that locally built python out of root's PATH is a good idea. Tools like virtualenv are good at keeping the locally built tools separate or you could compile into /opt and only put that in users' PATHs. There's also a reasonable chance you don't need it at all with stretch/sid since python3.5 is the default Python 3 there. cheers Stuart -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
