do-release-upgrade complains no module namedd aptWhy is medibuntu.org still offered as a package source if it...

What's a good word to describe a public place that looks like it wouldn't be rough?

Cookies - Should the toggles be on?

Digits in an algebraic irrational number

How can I get my players to come to the game session after agreeing to a date?

Can I string the D&D Starter Set campaign into another module, keeping the same characters?

Why avoid shared user accounts?

MAC Address learning process

Who is this Ant Woman character in this image alongside the Wasp?

How to say "Brexit" in Latin?

Does paint affect EMI ability of enclosure?

Am I a Rude Number?

Vertical alignment of rbrace

Roman Numerals equation 1

Advice for a new journal editor

Why isn't there a non-conducting core wire for high-frequency coil applications

Finding a mistake using Mayer-Vietoris

Caruana vs Carlsen game 10 (WCC) why not 18...Nxb6?

Why did the villain in the first Men in Black movie care about Earth's Cockroaches?

Can placing a counter on a creature after it has been assigned as an attacker remove it from combat

Can we use the stored gravitational potential energy of a building to produce power?

One Half of Ten; A Riddle

Is my visa status for all destinations in a flight with connections checked in the beginning or before each flight?

what does しにみえてる mean?

How would an AI self awareness kill switch work?



do-release-upgrade complains no module namedd apt


Why is medibuntu.org still offered as a package source if it has been shutdown since 2010?Where does CHEESE store its images?dependency error on libc6-amd64 even if it's already installedbroken packages with PgAdmin3 version 1.20 in Ubuntu 14 LTSCan't install libpng-devPackage system is broken (16.04)E: The repository 'https://download.01.org/gfx/ubuntu/17.04/main zesty Release' does no longer have a Release fileUnable to install postgreSQL 9.6 in Ubuntu 18.0418.04.1 Server keeps creating /var/lib/dpkg/lock and /var/cache/apt/archives/lock. What now?apt does not want to clear updated packages













1















Been searching for a while and couldn't find the relevant questions/solutions.



My system is running 14.04, every time when I logon the system, a message pops up saying 14.10 available, run do-release-upgrade.



Before hit with do-release-upgrade, I ran apt-get update & apt-get upgrade to make sure nothing is pending to update. Here are the errors I got



root@ubuntu:~# do-release-upgrade
Checking for a new ubuntu release
Get:1 Upgrade tool signature [198 B]
Get:2 Upgrade tool [1147 kB]
Fetched 1148 kB in 6s (109 kB/s)
authenticate 'utopic.tar.gz' against 'utopic.tar.gz.gpg'
extracting 'utopic.tar.gz'
Traceback (most recent call last):
File "/tmp/update-manager-J0y7tt/utopic", line 3, in <module>
from DistUpgrade.DistUpgradeMain import main
File "/tmp/update-manager-J0y7tt/DistUpgrade/DistUpgradeMain.py", line 22, in <module>
import apt
ImportError: No module named 'apt'
root@ubuntu:~#


Although apt and python are both installed properly.



root@ubuntu:~# apt-cache policy apt
apt:
Installed: 1.0.1ubuntu2.18
Candidate: 1.0.1ubuntu2.18
Version table:
*** 1.0.1ubuntu2.18 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
1.0.1ubuntu2.17 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1.0.1ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
root@ubuntu:~# apt-cache policy python
python:
Installed: 2.7.5-5ubuntu3
Candidate: 2.7.5-5ubuntu3
Version table:
*** 2.7.5-5ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
root@ubuntu:~#


python-apt is also installed.



root@ubuntu:~# apt-cache policy python-apt
python-apt:
Installed: 0.9.3.5ubuntu2
Candidate: 0.9.3.5ubuntu2
Version table:
*** 0.9.3.5ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
0.9.3.5 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
root@ubuntu:~#


Did anyone know how to get around this so I can go to 14.10?



Thanks,



The problem here appeared to be with python-apt package, although the right version is showing installed but somehow python script was complaining apt module cannot be recognized, after re-installed the package python-apt, do-release-upgrade worked.










share|improve this question




















  • 1





    last update, after fixing python-apt package. The running of do-release-upgrade worked like a charm, the system was smoothly upgrade from 14.04 (14.04.5) to 16.04 (16.04.4).

    – Denistone
    Jun 29 '18 at 3:58
















1















Been searching for a while and couldn't find the relevant questions/solutions.



My system is running 14.04, every time when I logon the system, a message pops up saying 14.10 available, run do-release-upgrade.



Before hit with do-release-upgrade, I ran apt-get update & apt-get upgrade to make sure nothing is pending to update. Here are the errors I got



root@ubuntu:~# do-release-upgrade
Checking for a new ubuntu release
Get:1 Upgrade tool signature [198 B]
Get:2 Upgrade tool [1147 kB]
Fetched 1148 kB in 6s (109 kB/s)
authenticate 'utopic.tar.gz' against 'utopic.tar.gz.gpg'
extracting 'utopic.tar.gz'
Traceback (most recent call last):
File "/tmp/update-manager-J0y7tt/utopic", line 3, in <module>
from DistUpgrade.DistUpgradeMain import main
File "/tmp/update-manager-J0y7tt/DistUpgrade/DistUpgradeMain.py", line 22, in <module>
import apt
ImportError: No module named 'apt'
root@ubuntu:~#


Although apt and python are both installed properly.



root@ubuntu:~# apt-cache policy apt
apt:
Installed: 1.0.1ubuntu2.18
Candidate: 1.0.1ubuntu2.18
Version table:
*** 1.0.1ubuntu2.18 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
1.0.1ubuntu2.17 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1.0.1ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
root@ubuntu:~# apt-cache policy python
python:
Installed: 2.7.5-5ubuntu3
Candidate: 2.7.5-5ubuntu3
Version table:
*** 2.7.5-5ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
root@ubuntu:~#


python-apt is also installed.



root@ubuntu:~# apt-cache policy python-apt
python-apt:
Installed: 0.9.3.5ubuntu2
Candidate: 0.9.3.5ubuntu2
Version table:
*** 0.9.3.5ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
0.9.3.5 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
root@ubuntu:~#


Did anyone know how to get around this so I can go to 14.10?



Thanks,



The problem here appeared to be with python-apt package, although the right version is showing installed but somehow python script was complaining apt module cannot be recognized, after re-installed the package python-apt, do-release-upgrade worked.










share|improve this question




















  • 1





    last update, after fixing python-apt package. The running of do-release-upgrade worked like a charm, the system was smoothly upgrade from 14.04 (14.04.5) to 16.04 (16.04.4).

    – Denistone
    Jun 29 '18 at 3:58














1












1








1








Been searching for a while and couldn't find the relevant questions/solutions.



My system is running 14.04, every time when I logon the system, a message pops up saying 14.10 available, run do-release-upgrade.



Before hit with do-release-upgrade, I ran apt-get update & apt-get upgrade to make sure nothing is pending to update. Here are the errors I got



root@ubuntu:~# do-release-upgrade
Checking for a new ubuntu release
Get:1 Upgrade tool signature [198 B]
Get:2 Upgrade tool [1147 kB]
Fetched 1148 kB in 6s (109 kB/s)
authenticate 'utopic.tar.gz' against 'utopic.tar.gz.gpg'
extracting 'utopic.tar.gz'
Traceback (most recent call last):
File "/tmp/update-manager-J0y7tt/utopic", line 3, in <module>
from DistUpgrade.DistUpgradeMain import main
File "/tmp/update-manager-J0y7tt/DistUpgrade/DistUpgradeMain.py", line 22, in <module>
import apt
ImportError: No module named 'apt'
root@ubuntu:~#


Although apt and python are both installed properly.



root@ubuntu:~# apt-cache policy apt
apt:
Installed: 1.0.1ubuntu2.18
Candidate: 1.0.1ubuntu2.18
Version table:
*** 1.0.1ubuntu2.18 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
1.0.1ubuntu2.17 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1.0.1ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
root@ubuntu:~# apt-cache policy python
python:
Installed: 2.7.5-5ubuntu3
Candidate: 2.7.5-5ubuntu3
Version table:
*** 2.7.5-5ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
root@ubuntu:~#


python-apt is also installed.



root@ubuntu:~# apt-cache policy python-apt
python-apt:
Installed: 0.9.3.5ubuntu2
Candidate: 0.9.3.5ubuntu2
Version table:
*** 0.9.3.5ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
0.9.3.5 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
root@ubuntu:~#


Did anyone know how to get around this so I can go to 14.10?



Thanks,



The problem here appeared to be with python-apt package, although the right version is showing installed but somehow python script was complaining apt module cannot be recognized, after re-installed the package python-apt, do-release-upgrade worked.










share|improve this question
















Been searching for a while and couldn't find the relevant questions/solutions.



My system is running 14.04, every time when I logon the system, a message pops up saying 14.10 available, run do-release-upgrade.



Before hit with do-release-upgrade, I ran apt-get update & apt-get upgrade to make sure nothing is pending to update. Here are the errors I got



root@ubuntu:~# do-release-upgrade
Checking for a new ubuntu release
Get:1 Upgrade tool signature [198 B]
Get:2 Upgrade tool [1147 kB]
Fetched 1148 kB in 6s (109 kB/s)
authenticate 'utopic.tar.gz' against 'utopic.tar.gz.gpg'
extracting 'utopic.tar.gz'
Traceback (most recent call last):
File "/tmp/update-manager-J0y7tt/utopic", line 3, in <module>
from DistUpgrade.DistUpgradeMain import main
File "/tmp/update-manager-J0y7tt/DistUpgrade/DistUpgradeMain.py", line 22, in <module>
import apt
ImportError: No module named 'apt'
root@ubuntu:~#


Although apt and python are both installed properly.



root@ubuntu:~# apt-cache policy apt
apt:
Installed: 1.0.1ubuntu2.18
Candidate: 1.0.1ubuntu2.18
Version table:
*** 1.0.1ubuntu2.18 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
1.0.1ubuntu2.17 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1.0.1ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
root@ubuntu:~# apt-cache policy python
python:
Installed: 2.7.5-5ubuntu3
Candidate: 2.7.5-5ubuntu3
Version table:
*** 2.7.5-5ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
root@ubuntu:~#


python-apt is also installed.



root@ubuntu:~# apt-cache policy python-apt
python-apt:
Installed: 0.9.3.5ubuntu2
Candidate: 0.9.3.5ubuntu2
Version table:
*** 0.9.3.5ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
0.9.3.5 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
root@ubuntu:~#


Did anyone know how to get around this so I can go to 14.10?



Thanks,



The problem here appeared to be with python-apt package, although the right version is showing installed but somehow python script was complaining apt module cannot be recognized, after re-installed the package python-apt, do-release-upgrade worked.







14.04 apt upgrade 14.10






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 7 mins ago









Elder Geek

27.3k954127




27.3k954127










asked Jun 27 '18 at 8:09









DenistoneDenistone

214




214








  • 1





    last update, after fixing python-apt package. The running of do-release-upgrade worked like a charm, the system was smoothly upgrade from 14.04 (14.04.5) to 16.04 (16.04.4).

    – Denistone
    Jun 29 '18 at 3:58














  • 1





    last update, after fixing python-apt package. The running of do-release-upgrade worked like a charm, the system was smoothly upgrade from 14.04 (14.04.5) to 16.04 (16.04.4).

    – Denistone
    Jun 29 '18 at 3:58








1




1





last update, after fixing python-apt package. The running of do-release-upgrade worked like a charm, the system was smoothly upgrade from 14.04 (14.04.5) to 16.04 (16.04.4).

– Denistone
Jun 29 '18 at 3:58





last update, after fixing python-apt package. The running of do-release-upgrade worked like a charm, the system was smoothly upgrade from 14.04 (14.04.5) to 16.04 (16.04.4).

– Denistone
Jun 29 '18 at 3:58










2 Answers
2






active

oldest

votes


















1














Ubuntu 14.10 has been EOL since July 23, 2015 so it is not possible to update to this version. It should be possible to update to 16.04 which is also a LTS version.



Check settings in Update Manager is set to only inform on new LTS versions, and there should be a button saying New release 16.04 is available.






share|improve this answer
























  • Thanks for the reply, but do you think the issue I am having "python complaining missing apt module" is because 14.10 is EOL? or some package needs to be fixed? I understand my 14.04 is old, given that this do-release-upgrade from 14.04 to 14.10 is reporting these errors, I guess to 16.04 will fail too.

    – Denistone
    Jun 27 '18 at 8:38











  • It's because 14.10 is eol. Those messages with 'utopic' in them are issued because the utopic repos don't exist in their former locations any more. in 'software and updates' change the setting to the next lts version.

    – Organic Marble
    Jun 27 '18 at 11:08











  • Thanks, the key problem here seems with "ImportError: No module named 'apt'", I just removed python-apt and re-installed it. Afterwards do-release-upgrade did move forward. Since I am running this through ssh session, at the warning of ssh session, I chose to stop at this point. Don't want to get up and walk into the garage at this hour, Sydney is freezing code. I will run this tomorrow from the console.

    – Denistone
    Jun 27 '18 at 11:47











  • Just double checked my version, it is 14.04.5 which will be supported up to April 2019. root@ubuntu:/etc# more lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS" root@ubuntu:/etc#

    – Denistone
    Jun 27 '18 at 12:11











  • after fixing python-apt package, when I logon the system, it is properly reporting 16.04 available, looks to be a 14.04 LTS to 16.04LTS normal upgrade. Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-149-generic x86_64) * Documentation: help.ubuntu.com New release '16.04.4 LTS' available. Run 'do-release-upgrade' to upgrade to it.

    – Denistone
    Jun 28 '18 at 0:08



















1














The problem is that python-apt somehow was playing up. The DistUpgradeMain.py simply failed at the first line
import apt



I just removed python-apt and re-installed it again, do-release-upgrade now worked.






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',
    autoActivateHeartbeat: false,
    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%2f1050087%2fdo-release-upgrade-complains-no-module-namedd-apt%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









    1














    Ubuntu 14.10 has been EOL since July 23, 2015 so it is not possible to update to this version. It should be possible to update to 16.04 which is also a LTS version.



    Check settings in Update Manager is set to only inform on new LTS versions, and there should be a button saying New release 16.04 is available.






    share|improve this answer
























    • Thanks for the reply, but do you think the issue I am having "python complaining missing apt module" is because 14.10 is EOL? or some package needs to be fixed? I understand my 14.04 is old, given that this do-release-upgrade from 14.04 to 14.10 is reporting these errors, I guess to 16.04 will fail too.

      – Denistone
      Jun 27 '18 at 8:38











    • It's because 14.10 is eol. Those messages with 'utopic' in them are issued because the utopic repos don't exist in their former locations any more. in 'software and updates' change the setting to the next lts version.

      – Organic Marble
      Jun 27 '18 at 11:08











    • Thanks, the key problem here seems with "ImportError: No module named 'apt'", I just removed python-apt and re-installed it. Afterwards do-release-upgrade did move forward. Since I am running this through ssh session, at the warning of ssh session, I chose to stop at this point. Don't want to get up and walk into the garage at this hour, Sydney is freezing code. I will run this tomorrow from the console.

      – Denistone
      Jun 27 '18 at 11:47











    • Just double checked my version, it is 14.04.5 which will be supported up to April 2019. root@ubuntu:/etc# more lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS" root@ubuntu:/etc#

      – Denistone
      Jun 27 '18 at 12:11











    • after fixing python-apt package, when I logon the system, it is properly reporting 16.04 available, looks to be a 14.04 LTS to 16.04LTS normal upgrade. Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-149-generic x86_64) * Documentation: help.ubuntu.com New release '16.04.4 LTS' available. Run 'do-release-upgrade' to upgrade to it.

      – Denistone
      Jun 28 '18 at 0:08
















    1














    Ubuntu 14.10 has been EOL since July 23, 2015 so it is not possible to update to this version. It should be possible to update to 16.04 which is also a LTS version.



    Check settings in Update Manager is set to only inform on new LTS versions, and there should be a button saying New release 16.04 is available.






    share|improve this answer
























    • Thanks for the reply, but do you think the issue I am having "python complaining missing apt module" is because 14.10 is EOL? or some package needs to be fixed? I understand my 14.04 is old, given that this do-release-upgrade from 14.04 to 14.10 is reporting these errors, I guess to 16.04 will fail too.

      – Denistone
      Jun 27 '18 at 8:38











    • It's because 14.10 is eol. Those messages with 'utopic' in them are issued because the utopic repos don't exist in their former locations any more. in 'software and updates' change the setting to the next lts version.

      – Organic Marble
      Jun 27 '18 at 11:08











    • Thanks, the key problem here seems with "ImportError: No module named 'apt'", I just removed python-apt and re-installed it. Afterwards do-release-upgrade did move forward. Since I am running this through ssh session, at the warning of ssh session, I chose to stop at this point. Don't want to get up and walk into the garage at this hour, Sydney is freezing code. I will run this tomorrow from the console.

      – Denistone
      Jun 27 '18 at 11:47











    • Just double checked my version, it is 14.04.5 which will be supported up to April 2019. root@ubuntu:/etc# more lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS" root@ubuntu:/etc#

      – Denistone
      Jun 27 '18 at 12:11











    • after fixing python-apt package, when I logon the system, it is properly reporting 16.04 available, looks to be a 14.04 LTS to 16.04LTS normal upgrade. Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-149-generic x86_64) * Documentation: help.ubuntu.com New release '16.04.4 LTS' available. Run 'do-release-upgrade' to upgrade to it.

      – Denistone
      Jun 28 '18 at 0:08














    1












    1








    1







    Ubuntu 14.10 has been EOL since July 23, 2015 so it is not possible to update to this version. It should be possible to update to 16.04 which is also a LTS version.



    Check settings in Update Manager is set to only inform on new LTS versions, and there should be a button saying New release 16.04 is available.






    share|improve this answer













    Ubuntu 14.10 has been EOL since July 23, 2015 so it is not possible to update to this version. It should be possible to update to 16.04 which is also a LTS version.



    Check settings in Update Manager is set to only inform on new LTS versions, and there should be a button saying New release 16.04 is available.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jun 27 '18 at 8:30









    Soren ASoren A

    3,4681924




    3,4681924













    • Thanks for the reply, but do you think the issue I am having "python complaining missing apt module" is because 14.10 is EOL? or some package needs to be fixed? I understand my 14.04 is old, given that this do-release-upgrade from 14.04 to 14.10 is reporting these errors, I guess to 16.04 will fail too.

      – Denistone
      Jun 27 '18 at 8:38











    • It's because 14.10 is eol. Those messages with 'utopic' in them are issued because the utopic repos don't exist in their former locations any more. in 'software and updates' change the setting to the next lts version.

      – Organic Marble
      Jun 27 '18 at 11:08











    • Thanks, the key problem here seems with "ImportError: No module named 'apt'", I just removed python-apt and re-installed it. Afterwards do-release-upgrade did move forward. Since I am running this through ssh session, at the warning of ssh session, I chose to stop at this point. Don't want to get up and walk into the garage at this hour, Sydney is freezing code. I will run this tomorrow from the console.

      – Denistone
      Jun 27 '18 at 11:47











    • Just double checked my version, it is 14.04.5 which will be supported up to April 2019. root@ubuntu:/etc# more lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS" root@ubuntu:/etc#

      – Denistone
      Jun 27 '18 at 12:11











    • after fixing python-apt package, when I logon the system, it is properly reporting 16.04 available, looks to be a 14.04 LTS to 16.04LTS normal upgrade. Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-149-generic x86_64) * Documentation: help.ubuntu.com New release '16.04.4 LTS' available. Run 'do-release-upgrade' to upgrade to it.

      – Denistone
      Jun 28 '18 at 0:08



















    • Thanks for the reply, but do you think the issue I am having "python complaining missing apt module" is because 14.10 is EOL? or some package needs to be fixed? I understand my 14.04 is old, given that this do-release-upgrade from 14.04 to 14.10 is reporting these errors, I guess to 16.04 will fail too.

      – Denistone
      Jun 27 '18 at 8:38











    • It's because 14.10 is eol. Those messages with 'utopic' in them are issued because the utopic repos don't exist in their former locations any more. in 'software and updates' change the setting to the next lts version.

      – Organic Marble
      Jun 27 '18 at 11:08











    • Thanks, the key problem here seems with "ImportError: No module named 'apt'", I just removed python-apt and re-installed it. Afterwards do-release-upgrade did move forward. Since I am running this through ssh session, at the warning of ssh session, I chose to stop at this point. Don't want to get up and walk into the garage at this hour, Sydney is freezing code. I will run this tomorrow from the console.

      – Denistone
      Jun 27 '18 at 11:47











    • Just double checked my version, it is 14.04.5 which will be supported up to April 2019. root@ubuntu:/etc# more lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS" root@ubuntu:/etc#

      – Denistone
      Jun 27 '18 at 12:11











    • after fixing python-apt package, when I logon the system, it is properly reporting 16.04 available, looks to be a 14.04 LTS to 16.04LTS normal upgrade. Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-149-generic x86_64) * Documentation: help.ubuntu.com New release '16.04.4 LTS' available. Run 'do-release-upgrade' to upgrade to it.

      – Denistone
      Jun 28 '18 at 0:08

















    Thanks for the reply, but do you think the issue I am having "python complaining missing apt module" is because 14.10 is EOL? or some package needs to be fixed? I understand my 14.04 is old, given that this do-release-upgrade from 14.04 to 14.10 is reporting these errors, I guess to 16.04 will fail too.

    – Denistone
    Jun 27 '18 at 8:38





    Thanks for the reply, but do you think the issue I am having "python complaining missing apt module" is because 14.10 is EOL? or some package needs to be fixed? I understand my 14.04 is old, given that this do-release-upgrade from 14.04 to 14.10 is reporting these errors, I guess to 16.04 will fail too.

    – Denistone
    Jun 27 '18 at 8:38













    It's because 14.10 is eol. Those messages with 'utopic' in them are issued because the utopic repos don't exist in their former locations any more. in 'software and updates' change the setting to the next lts version.

    – Organic Marble
    Jun 27 '18 at 11:08





    It's because 14.10 is eol. Those messages with 'utopic' in them are issued because the utopic repos don't exist in their former locations any more. in 'software and updates' change the setting to the next lts version.

    – Organic Marble
    Jun 27 '18 at 11:08













    Thanks, the key problem here seems with "ImportError: No module named 'apt'", I just removed python-apt and re-installed it. Afterwards do-release-upgrade did move forward. Since I am running this through ssh session, at the warning of ssh session, I chose to stop at this point. Don't want to get up and walk into the garage at this hour, Sydney is freezing code. I will run this tomorrow from the console.

    – Denistone
    Jun 27 '18 at 11:47





    Thanks, the key problem here seems with "ImportError: No module named 'apt'", I just removed python-apt and re-installed it. Afterwards do-release-upgrade did move forward. Since I am running this through ssh session, at the warning of ssh session, I chose to stop at this point. Don't want to get up and walk into the garage at this hour, Sydney is freezing code. I will run this tomorrow from the console.

    – Denistone
    Jun 27 '18 at 11:47













    Just double checked my version, it is 14.04.5 which will be supported up to April 2019. root@ubuntu:/etc# more lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS" root@ubuntu:/etc#

    – Denistone
    Jun 27 '18 at 12:11





    Just double checked my version, it is 14.04.5 which will be supported up to April 2019. root@ubuntu:/etc# more lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS" root@ubuntu:/etc#

    – Denistone
    Jun 27 '18 at 12:11













    after fixing python-apt package, when I logon the system, it is properly reporting 16.04 available, looks to be a 14.04 LTS to 16.04LTS normal upgrade. Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-149-generic x86_64) * Documentation: help.ubuntu.com New release '16.04.4 LTS' available. Run 'do-release-upgrade' to upgrade to it.

    – Denistone
    Jun 28 '18 at 0:08





    after fixing python-apt package, when I logon the system, it is properly reporting 16.04 available, looks to be a 14.04 LTS to 16.04LTS normal upgrade. Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-149-generic x86_64) * Documentation: help.ubuntu.com New release '16.04.4 LTS' available. Run 'do-release-upgrade' to upgrade to it.

    – Denistone
    Jun 28 '18 at 0:08













    1














    The problem is that python-apt somehow was playing up. The DistUpgradeMain.py simply failed at the first line
    import apt



    I just removed python-apt and re-installed it again, do-release-upgrade now worked.






    share|improve this answer




























      1














      The problem is that python-apt somehow was playing up. The DistUpgradeMain.py simply failed at the first line
      import apt



      I just removed python-apt and re-installed it again, do-release-upgrade now worked.






      share|improve this answer


























        1












        1








        1







        The problem is that python-apt somehow was playing up. The DistUpgradeMain.py simply failed at the first line
        import apt



        I just removed python-apt and re-installed it again, do-release-upgrade now worked.






        share|improve this answer













        The problem is that python-apt somehow was playing up. The DistUpgradeMain.py simply failed at the first line
        import apt



        I just removed python-apt and re-installed it again, do-release-upgrade now worked.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 27 '18 at 12:15









        DenistoneDenistone

        214




        214






























            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1050087%2fdo-release-upgrade-complains-no-module-namedd-apt%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

            List of shipwrecks in 1808...

            Is there a lightweight tool to crop images quickly?Cropping Images using Command Line Tools OnlyHow to crop...

            Unit packagekit.service is masked Announcing the arrival of Valued Associate #679: Cesar...