Ubuntu16.04: Bad lsb_release file











up vote
1
down vote

favorite












I have a VM with:
OS: Ubuntu 16.04.1 LTS
Kernel: Linux 4.4.0-59-generic
Architecture: x86-64



In this system, there were 2 versions of python: 2.7.12 and 3.5. Pip was also installed. Pip version is:



pip 9.0.1 from /usr/local/lib/python2.7/dist-packages (python 2.7)


Every time pip install <package> was run, I got error. The main error was because lsb_release -a returned error. I ran lsb_release -a from console and I got invalid syntax error:



File "/usr/bin/lsb_release", line 64
print("No LSB modules are available.", file=sys.stderr)
^


The header of lsb_release file has the following:



#!/usr/bin/python3 -Es


But the system does not seem to know how to get to python3, even though the symbolic link was set for python3 to python3.5, using the following command:



sudo ln -s /usr/bin/python3.5 /usr/bin/python3


The output of command ls -l /usr/bin/python* is the following:



lrwxrwxrwx 1 root root       9 Dec  9  2015 /usr/bin/python -> python2.7
lrwxrwxrwx 1 root root 9 Dec 9 2015 /usr/bin/python2 -> python2.7
-rwxr-xr-x 1 root root 3546104 Nov 19 01:35 /usr/bin/python2.7
lrwxrwxrwx 1 root root 33 Nov 19 01:35 /usr/bin/python2.7-config -> x86_64-linux-gnu-python2.7-config
lrwxrwxrwx 1 root root 16 Dec 9 2015 /usr/bin/python2-config -> python2.7-config
lrwxrwxrwx 1 root root 9 Jan 26 09:07 /usr/bin/python3 -> python3.5
-rwxr-xr-x 2 root root 3546104 Jan 19 14:23 /usr/bin/python3.5
lrwxrwxrwx 1 root root 33 Nov 17 11:23 /usr/bin/python3.5-config -> x86_64-linux-gnu-python3.5-config
-rwxr-xr-x 2 root root 3546104 Jan 19 14:23 /usr/bin/python3.5m
lrwxrwxrwx 1 root root 34 Nov 17 11:23 /usr/bin/python3.5m-config -> x86_64-linux-gnu-python3.5m-config
lrwxrwxrwx 1 root root 16 Mar 23 2016 /usr/bin/python3-config -> python3.5-config
lrwxrwxrwx 1 root root 10 Jun 6 2016 /usr/bin/python3m -> python3.5m
lrwxrwxrwx 1 root root 17 Mar 23 2016 /usr/bin/python3m-config -> python3.5m-config
lrwxrwxrwx 1 root root 16 Dec 9 2015 /usr/bin/python-config -> python2.7-config


Checking the version of python3.5, I got back the version of 2.7:



$ /usr/bin/python3.5 --version
Python 2.7.12


Something does not look right from my system, when I execute
ll -a /usr/share/man/man1 | grep python. The output is:



-rw-r--r--  1 root root   3367 Dec  9  2015 dh_python2.1.gz
-rw-r--r-- 1 root root 3280 May 18 2016 dh_python3.1.gz
lrwxrwxrwx 1 root root 14 Dec 9 2015 python.1.gz -> python2.7.1.gz
lrwxrwxrwx 1 root root 14 Dec 9 2015 python2.1.gz -> python2.7.1.gz
-rw-r--r-- 1 root root 5640 Nov 19 01:32 python2.7.1.gz
lrwxrwxrwx 1 root root 38 Nov 19 01:35 python2.7-config.1.gz -> x86_64-linux-gnu-python2.7-config.1.gz
lrwxrwxrwx 1 root root 21 Dec 9 2015 python2-config.1.gz -> python2.7-config.1.gz
lrwxrwxrwx 1 root root 14 Jun 6 2016 python3.1.gz -> python3.5.1.gz
-rw-r--r-- 1 root root 5174 Nov 17 10:43 python3.5.1.gz
lrwxrwxrwx 1 root root 38 Nov 17 11:23 python3.5-config.1.gz -> x86_64-linux-gnu-python3.5-config.1.gz
lrwxrwxrwx 1 root root 14 Nov 17 11:23 python3.5m.1.gz -> python3.5.1.gz
lrwxrwxrwx 1 root root 39 Nov 17 11:23 python3.5m-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 21 Mar 23 2016 python3-config.1.gz -> python3.5-config.1.gz
lrwxrwxrwx 1 root root 15 Jun 6 2016 python3m.1.gz -> python3.5m.1.gz
lrwxrwxrwx 1 root root 22 Mar 23 2016 python3m-config.1.gz -> python3.5m-config.1.gz
lrwxrwxrwx 1 root root 21 Dec 9 2015 python-config.1.gz -> python2.7-config.1.gz
-rw-r--r-- 1 root root 921 Nov 19 00:15 x86_64-linux-gnu-python2.7-config.1.gz
lrwxrwxrwx 1 root root 39 Nov 17 11:23 x86_64-linux-gnu-python3.5-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
-rw-r--r-- 1 root root 907 Nov 23 2013 x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 38 Mar 23 2016 x86_64-linux-gnu-python3-config.1.gz -> x86_64-linux-gnu-python3.5-config.1.gz
lrwxrwxrwx 1 root root 39 Mar 23 2016 x86_64-linux-gnu-python3m-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 38 Dec 9 2015 x86_64-linux-gnu-python-config.1.gz -> x86_64-linux-gnu-python2.7-config.1.gz


The 3.5 package, x86_64-linux-gnu-python3.5-config.1.gz, has a symbolic link to 3.5m. Is it odd?



The problem now is how to correct the python3 point to the correct version. Is there a way to do so?



Thank you










share|improve this question
























  • Please edit this question to include the output of ls -l /usr/bin/python*.
    – Eliah Kagan
    Jan 26 '17 at 4:25










  • Check this question.
    – Alfabravo
    Jan 26 '17 at 5:37















up vote
1
down vote

favorite












I have a VM with:
OS: Ubuntu 16.04.1 LTS
Kernel: Linux 4.4.0-59-generic
Architecture: x86-64



In this system, there were 2 versions of python: 2.7.12 and 3.5. Pip was also installed. Pip version is:



pip 9.0.1 from /usr/local/lib/python2.7/dist-packages (python 2.7)


Every time pip install <package> was run, I got error. The main error was because lsb_release -a returned error. I ran lsb_release -a from console and I got invalid syntax error:



File "/usr/bin/lsb_release", line 64
print("No LSB modules are available.", file=sys.stderr)
^


The header of lsb_release file has the following:



#!/usr/bin/python3 -Es


But the system does not seem to know how to get to python3, even though the symbolic link was set for python3 to python3.5, using the following command:



sudo ln -s /usr/bin/python3.5 /usr/bin/python3


The output of command ls -l /usr/bin/python* is the following:



lrwxrwxrwx 1 root root       9 Dec  9  2015 /usr/bin/python -> python2.7
lrwxrwxrwx 1 root root 9 Dec 9 2015 /usr/bin/python2 -> python2.7
-rwxr-xr-x 1 root root 3546104 Nov 19 01:35 /usr/bin/python2.7
lrwxrwxrwx 1 root root 33 Nov 19 01:35 /usr/bin/python2.7-config -> x86_64-linux-gnu-python2.7-config
lrwxrwxrwx 1 root root 16 Dec 9 2015 /usr/bin/python2-config -> python2.7-config
lrwxrwxrwx 1 root root 9 Jan 26 09:07 /usr/bin/python3 -> python3.5
-rwxr-xr-x 2 root root 3546104 Jan 19 14:23 /usr/bin/python3.5
lrwxrwxrwx 1 root root 33 Nov 17 11:23 /usr/bin/python3.5-config -> x86_64-linux-gnu-python3.5-config
-rwxr-xr-x 2 root root 3546104 Jan 19 14:23 /usr/bin/python3.5m
lrwxrwxrwx 1 root root 34 Nov 17 11:23 /usr/bin/python3.5m-config -> x86_64-linux-gnu-python3.5m-config
lrwxrwxrwx 1 root root 16 Mar 23 2016 /usr/bin/python3-config -> python3.5-config
lrwxrwxrwx 1 root root 10 Jun 6 2016 /usr/bin/python3m -> python3.5m
lrwxrwxrwx 1 root root 17 Mar 23 2016 /usr/bin/python3m-config -> python3.5m-config
lrwxrwxrwx 1 root root 16 Dec 9 2015 /usr/bin/python-config -> python2.7-config


Checking the version of python3.5, I got back the version of 2.7:



$ /usr/bin/python3.5 --version
Python 2.7.12


Something does not look right from my system, when I execute
ll -a /usr/share/man/man1 | grep python. The output is:



-rw-r--r--  1 root root   3367 Dec  9  2015 dh_python2.1.gz
-rw-r--r-- 1 root root 3280 May 18 2016 dh_python3.1.gz
lrwxrwxrwx 1 root root 14 Dec 9 2015 python.1.gz -> python2.7.1.gz
lrwxrwxrwx 1 root root 14 Dec 9 2015 python2.1.gz -> python2.7.1.gz
-rw-r--r-- 1 root root 5640 Nov 19 01:32 python2.7.1.gz
lrwxrwxrwx 1 root root 38 Nov 19 01:35 python2.7-config.1.gz -> x86_64-linux-gnu-python2.7-config.1.gz
lrwxrwxrwx 1 root root 21 Dec 9 2015 python2-config.1.gz -> python2.7-config.1.gz
lrwxrwxrwx 1 root root 14 Jun 6 2016 python3.1.gz -> python3.5.1.gz
-rw-r--r-- 1 root root 5174 Nov 17 10:43 python3.5.1.gz
lrwxrwxrwx 1 root root 38 Nov 17 11:23 python3.5-config.1.gz -> x86_64-linux-gnu-python3.5-config.1.gz
lrwxrwxrwx 1 root root 14 Nov 17 11:23 python3.5m.1.gz -> python3.5.1.gz
lrwxrwxrwx 1 root root 39 Nov 17 11:23 python3.5m-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 21 Mar 23 2016 python3-config.1.gz -> python3.5-config.1.gz
lrwxrwxrwx 1 root root 15 Jun 6 2016 python3m.1.gz -> python3.5m.1.gz
lrwxrwxrwx 1 root root 22 Mar 23 2016 python3m-config.1.gz -> python3.5m-config.1.gz
lrwxrwxrwx 1 root root 21 Dec 9 2015 python-config.1.gz -> python2.7-config.1.gz
-rw-r--r-- 1 root root 921 Nov 19 00:15 x86_64-linux-gnu-python2.7-config.1.gz
lrwxrwxrwx 1 root root 39 Nov 17 11:23 x86_64-linux-gnu-python3.5-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
-rw-r--r-- 1 root root 907 Nov 23 2013 x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 38 Mar 23 2016 x86_64-linux-gnu-python3-config.1.gz -> x86_64-linux-gnu-python3.5-config.1.gz
lrwxrwxrwx 1 root root 39 Mar 23 2016 x86_64-linux-gnu-python3m-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 38 Dec 9 2015 x86_64-linux-gnu-python-config.1.gz -> x86_64-linux-gnu-python2.7-config.1.gz


The 3.5 package, x86_64-linux-gnu-python3.5-config.1.gz, has a symbolic link to 3.5m. Is it odd?



The problem now is how to correct the python3 point to the correct version. Is there a way to do so?



Thank you










share|improve this question
























  • Please edit this question to include the output of ls -l /usr/bin/python*.
    – Eliah Kagan
    Jan 26 '17 at 4:25










  • Check this question.
    – Alfabravo
    Jan 26 '17 at 5:37













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have a VM with:
OS: Ubuntu 16.04.1 LTS
Kernel: Linux 4.4.0-59-generic
Architecture: x86-64



In this system, there were 2 versions of python: 2.7.12 and 3.5. Pip was also installed. Pip version is:



pip 9.0.1 from /usr/local/lib/python2.7/dist-packages (python 2.7)


Every time pip install <package> was run, I got error. The main error was because lsb_release -a returned error. I ran lsb_release -a from console and I got invalid syntax error:



File "/usr/bin/lsb_release", line 64
print("No LSB modules are available.", file=sys.stderr)
^


The header of lsb_release file has the following:



#!/usr/bin/python3 -Es


But the system does not seem to know how to get to python3, even though the symbolic link was set for python3 to python3.5, using the following command:



sudo ln -s /usr/bin/python3.5 /usr/bin/python3


The output of command ls -l /usr/bin/python* is the following:



lrwxrwxrwx 1 root root       9 Dec  9  2015 /usr/bin/python -> python2.7
lrwxrwxrwx 1 root root 9 Dec 9 2015 /usr/bin/python2 -> python2.7
-rwxr-xr-x 1 root root 3546104 Nov 19 01:35 /usr/bin/python2.7
lrwxrwxrwx 1 root root 33 Nov 19 01:35 /usr/bin/python2.7-config -> x86_64-linux-gnu-python2.7-config
lrwxrwxrwx 1 root root 16 Dec 9 2015 /usr/bin/python2-config -> python2.7-config
lrwxrwxrwx 1 root root 9 Jan 26 09:07 /usr/bin/python3 -> python3.5
-rwxr-xr-x 2 root root 3546104 Jan 19 14:23 /usr/bin/python3.5
lrwxrwxrwx 1 root root 33 Nov 17 11:23 /usr/bin/python3.5-config -> x86_64-linux-gnu-python3.5-config
-rwxr-xr-x 2 root root 3546104 Jan 19 14:23 /usr/bin/python3.5m
lrwxrwxrwx 1 root root 34 Nov 17 11:23 /usr/bin/python3.5m-config -> x86_64-linux-gnu-python3.5m-config
lrwxrwxrwx 1 root root 16 Mar 23 2016 /usr/bin/python3-config -> python3.5-config
lrwxrwxrwx 1 root root 10 Jun 6 2016 /usr/bin/python3m -> python3.5m
lrwxrwxrwx 1 root root 17 Mar 23 2016 /usr/bin/python3m-config -> python3.5m-config
lrwxrwxrwx 1 root root 16 Dec 9 2015 /usr/bin/python-config -> python2.7-config


Checking the version of python3.5, I got back the version of 2.7:



$ /usr/bin/python3.5 --version
Python 2.7.12


Something does not look right from my system, when I execute
ll -a /usr/share/man/man1 | grep python. The output is:



-rw-r--r--  1 root root   3367 Dec  9  2015 dh_python2.1.gz
-rw-r--r-- 1 root root 3280 May 18 2016 dh_python3.1.gz
lrwxrwxrwx 1 root root 14 Dec 9 2015 python.1.gz -> python2.7.1.gz
lrwxrwxrwx 1 root root 14 Dec 9 2015 python2.1.gz -> python2.7.1.gz
-rw-r--r-- 1 root root 5640 Nov 19 01:32 python2.7.1.gz
lrwxrwxrwx 1 root root 38 Nov 19 01:35 python2.7-config.1.gz -> x86_64-linux-gnu-python2.7-config.1.gz
lrwxrwxrwx 1 root root 21 Dec 9 2015 python2-config.1.gz -> python2.7-config.1.gz
lrwxrwxrwx 1 root root 14 Jun 6 2016 python3.1.gz -> python3.5.1.gz
-rw-r--r-- 1 root root 5174 Nov 17 10:43 python3.5.1.gz
lrwxrwxrwx 1 root root 38 Nov 17 11:23 python3.5-config.1.gz -> x86_64-linux-gnu-python3.5-config.1.gz
lrwxrwxrwx 1 root root 14 Nov 17 11:23 python3.5m.1.gz -> python3.5.1.gz
lrwxrwxrwx 1 root root 39 Nov 17 11:23 python3.5m-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 21 Mar 23 2016 python3-config.1.gz -> python3.5-config.1.gz
lrwxrwxrwx 1 root root 15 Jun 6 2016 python3m.1.gz -> python3.5m.1.gz
lrwxrwxrwx 1 root root 22 Mar 23 2016 python3m-config.1.gz -> python3.5m-config.1.gz
lrwxrwxrwx 1 root root 21 Dec 9 2015 python-config.1.gz -> python2.7-config.1.gz
-rw-r--r-- 1 root root 921 Nov 19 00:15 x86_64-linux-gnu-python2.7-config.1.gz
lrwxrwxrwx 1 root root 39 Nov 17 11:23 x86_64-linux-gnu-python3.5-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
-rw-r--r-- 1 root root 907 Nov 23 2013 x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 38 Mar 23 2016 x86_64-linux-gnu-python3-config.1.gz -> x86_64-linux-gnu-python3.5-config.1.gz
lrwxrwxrwx 1 root root 39 Mar 23 2016 x86_64-linux-gnu-python3m-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 38 Dec 9 2015 x86_64-linux-gnu-python-config.1.gz -> x86_64-linux-gnu-python2.7-config.1.gz


The 3.5 package, x86_64-linux-gnu-python3.5-config.1.gz, has a symbolic link to 3.5m. Is it odd?



The problem now is how to correct the python3 point to the correct version. Is there a way to do so?



Thank you










share|improve this question















I have a VM with:
OS: Ubuntu 16.04.1 LTS
Kernel: Linux 4.4.0-59-generic
Architecture: x86-64



In this system, there were 2 versions of python: 2.7.12 and 3.5. Pip was also installed. Pip version is:



pip 9.0.1 from /usr/local/lib/python2.7/dist-packages (python 2.7)


Every time pip install <package> was run, I got error. The main error was because lsb_release -a returned error. I ran lsb_release -a from console and I got invalid syntax error:



File "/usr/bin/lsb_release", line 64
print("No LSB modules are available.", file=sys.stderr)
^


The header of lsb_release file has the following:



#!/usr/bin/python3 -Es


But the system does not seem to know how to get to python3, even though the symbolic link was set for python3 to python3.5, using the following command:



sudo ln -s /usr/bin/python3.5 /usr/bin/python3


The output of command ls -l /usr/bin/python* is the following:



lrwxrwxrwx 1 root root       9 Dec  9  2015 /usr/bin/python -> python2.7
lrwxrwxrwx 1 root root 9 Dec 9 2015 /usr/bin/python2 -> python2.7
-rwxr-xr-x 1 root root 3546104 Nov 19 01:35 /usr/bin/python2.7
lrwxrwxrwx 1 root root 33 Nov 19 01:35 /usr/bin/python2.7-config -> x86_64-linux-gnu-python2.7-config
lrwxrwxrwx 1 root root 16 Dec 9 2015 /usr/bin/python2-config -> python2.7-config
lrwxrwxrwx 1 root root 9 Jan 26 09:07 /usr/bin/python3 -> python3.5
-rwxr-xr-x 2 root root 3546104 Jan 19 14:23 /usr/bin/python3.5
lrwxrwxrwx 1 root root 33 Nov 17 11:23 /usr/bin/python3.5-config -> x86_64-linux-gnu-python3.5-config
-rwxr-xr-x 2 root root 3546104 Jan 19 14:23 /usr/bin/python3.5m
lrwxrwxrwx 1 root root 34 Nov 17 11:23 /usr/bin/python3.5m-config -> x86_64-linux-gnu-python3.5m-config
lrwxrwxrwx 1 root root 16 Mar 23 2016 /usr/bin/python3-config -> python3.5-config
lrwxrwxrwx 1 root root 10 Jun 6 2016 /usr/bin/python3m -> python3.5m
lrwxrwxrwx 1 root root 17 Mar 23 2016 /usr/bin/python3m-config -> python3.5m-config
lrwxrwxrwx 1 root root 16 Dec 9 2015 /usr/bin/python-config -> python2.7-config


Checking the version of python3.5, I got back the version of 2.7:



$ /usr/bin/python3.5 --version
Python 2.7.12


Something does not look right from my system, when I execute
ll -a /usr/share/man/man1 | grep python. The output is:



-rw-r--r--  1 root root   3367 Dec  9  2015 dh_python2.1.gz
-rw-r--r-- 1 root root 3280 May 18 2016 dh_python3.1.gz
lrwxrwxrwx 1 root root 14 Dec 9 2015 python.1.gz -> python2.7.1.gz
lrwxrwxrwx 1 root root 14 Dec 9 2015 python2.1.gz -> python2.7.1.gz
-rw-r--r-- 1 root root 5640 Nov 19 01:32 python2.7.1.gz
lrwxrwxrwx 1 root root 38 Nov 19 01:35 python2.7-config.1.gz -> x86_64-linux-gnu-python2.7-config.1.gz
lrwxrwxrwx 1 root root 21 Dec 9 2015 python2-config.1.gz -> python2.7-config.1.gz
lrwxrwxrwx 1 root root 14 Jun 6 2016 python3.1.gz -> python3.5.1.gz
-rw-r--r-- 1 root root 5174 Nov 17 10:43 python3.5.1.gz
lrwxrwxrwx 1 root root 38 Nov 17 11:23 python3.5-config.1.gz -> x86_64-linux-gnu-python3.5-config.1.gz
lrwxrwxrwx 1 root root 14 Nov 17 11:23 python3.5m.1.gz -> python3.5.1.gz
lrwxrwxrwx 1 root root 39 Nov 17 11:23 python3.5m-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 21 Mar 23 2016 python3-config.1.gz -> python3.5-config.1.gz
lrwxrwxrwx 1 root root 15 Jun 6 2016 python3m.1.gz -> python3.5m.1.gz
lrwxrwxrwx 1 root root 22 Mar 23 2016 python3m-config.1.gz -> python3.5m-config.1.gz
lrwxrwxrwx 1 root root 21 Dec 9 2015 python-config.1.gz -> python2.7-config.1.gz
-rw-r--r-- 1 root root 921 Nov 19 00:15 x86_64-linux-gnu-python2.7-config.1.gz
lrwxrwxrwx 1 root root 39 Nov 17 11:23 x86_64-linux-gnu-python3.5-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
-rw-r--r-- 1 root root 907 Nov 23 2013 x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 38 Mar 23 2016 x86_64-linux-gnu-python3-config.1.gz -> x86_64-linux-gnu-python3.5-config.1.gz
lrwxrwxrwx 1 root root 39 Mar 23 2016 x86_64-linux-gnu-python3m-config.1.gz -> x86_64-linux-gnu-python3.5m-config.1.gz
lrwxrwxrwx 1 root root 38 Dec 9 2015 x86_64-linux-gnu-python-config.1.gz -> x86_64-linux-gnu-python2.7-config.1.gz


The 3.5 package, x86_64-linux-gnu-python3.5-config.1.gz, has a symbolic link to 3.5m. Is it odd?



The problem now is how to correct the python3 point to the correct version. Is there a way to do so?



Thank you







python python3






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 26 '17 at 19:18

























asked Jan 26 '17 at 2:10









Thuy

63




63












  • Please edit this question to include the output of ls -l /usr/bin/python*.
    – Eliah Kagan
    Jan 26 '17 at 4:25










  • Check this question.
    – Alfabravo
    Jan 26 '17 at 5:37


















  • Please edit this question to include the output of ls -l /usr/bin/python*.
    – Eliah Kagan
    Jan 26 '17 at 4:25










  • Check this question.
    – Alfabravo
    Jan 26 '17 at 5:37
















Please edit this question to include the output of ls -l /usr/bin/python*.
– Eliah Kagan
Jan 26 '17 at 4:25




Please edit this question to include the output of ls -l /usr/bin/python*.
– Eliah Kagan
Jan 26 '17 at 4:25












Check this question.
– Alfabravo
Jan 26 '17 at 5:37




Check this question.
– Alfabravo
Jan 26 '17 at 5:37










2 Answers
2






active

oldest

votes

















up vote
0
down vote













The problem was the python versions 2.7.12 and 3.5.2 have messed up on the VM. A quick solution is just to purge the VM and create another one. This resolved my problem.






share|improve this answer




























    up vote
    0
    down vote













    You just purge lsb-release package and install again it will solve your problem.



     $ sudo apt purge lsb-release
    $ sudo apt install lsb-release





    share|improve this answer





















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f876310%2fubuntu16-04-bad-lsb-release-file%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      0
      down vote













      The problem was the python versions 2.7.12 and 3.5.2 have messed up on the VM. A quick solution is just to purge the VM and create another one. This resolved my problem.






      share|improve this answer

























        up vote
        0
        down vote













        The problem was the python versions 2.7.12 and 3.5.2 have messed up on the VM. A quick solution is just to purge the VM and create another one. This resolved my problem.






        share|improve this answer























          up vote
          0
          down vote










          up vote
          0
          down vote









          The problem was the python versions 2.7.12 and 3.5.2 have messed up on the VM. A quick solution is just to purge the VM and create another one. This resolved my problem.






          share|improve this answer












          The problem was the python versions 2.7.12 and 3.5.2 have messed up on the VM. A quick solution is just to purge the VM and create another one. This resolved my problem.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 3 '17 at 0:39









          Thuy

          63




          63
























              up vote
              0
              down vote













              You just purge lsb-release package and install again it will solve your problem.



               $ sudo apt purge lsb-release
              $ sudo apt install lsb-release





              share|improve this answer

























                up vote
                0
                down vote













                You just purge lsb-release package and install again it will solve your problem.



                 $ sudo apt purge lsb-release
                $ sudo apt install lsb-release





                share|improve this answer























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  You just purge lsb-release package and install again it will solve your problem.



                   $ sudo apt purge lsb-release
                  $ sudo apt install lsb-release





                  share|improve this answer












                  You just purge lsb-release package and install again it will solve your problem.



                   $ sudo apt purge lsb-release
                  $ sudo apt install lsb-release






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 20 at 10:28









                  Rakib

                  1011




                  1011






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f876310%2fubuntu16-04-bad-lsb-release-file%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

                      ComboBox Display Member on multiple fields

                      Is it possible to collect Nectar points via Trainline?