Issues after a try to upgrade

This is not how you upgrade Ubuntu. You needed to upgrade to 19.04 first and then to 19.10. Leapfrogging versions isn't advertised and I will be contacting the website.

The only supported way you can miss versions in an upgrade is from LTS to LTS release upgrades which, if you'd waited until next month, you could have done and been on the latest version of Ubuntu which would also be LTS

Hi Andrew,

I received your email, and I will make my statement here.

Firstly, the OP didn't have a working sources.list file before following my tutorial. His repositories are:

deb http://ports.ubuntu.com/ubuntu-ports/ bionic main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ bionic main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ bionic-updates main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ bionic-updates main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ bionic-security main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ bionic-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ bionic-backports main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ bionic-backports main restricted universe multiverse

This is wrong, there's no Ubuntu repository at the ports.ubuntu.com address. I didn't tell the OP to use the http://port.ubuntu.com address.

OP should put the following lines in the /etc/apt/sources.list file.

deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse

Then update.

sudo apt update

And follow my upgrade tutorial again.

So many people think you should never skip releases, unless you are upgrading LTS to LTS. They are wrong.

 If you open the "software & update" app on Ubuntu and set "Notify me of a new Ubuntu version" to "For any new version", then open the "software updater" app to update software package, it will tell you that Ubuntu 19.10 is available to upgrade. If you click the "Upgrade" button, then it will guide you to upgrade Ubuntu 18.04 to 19.10. This is the current official way to upgrade from Ubuntu 18.04 to 19.10.

Andrew, you said to me "Why do you think the do-release-upgrade command is used to upgrade releases? " I'm confused. If you check the man page (man do-release-upgrade), it tells that do-release-upgrade is used to upgrade the operating system to the latest release from the command-line. So I want to ask why do think do-release-upgrade" is not used to upgrade releases?

Conclusion:
1.) The OP didn't have a working repository file in the first place. If he/she did, the upgrade would have been successful.
2.) Ubuntu officially supports upgrading from Ubuntu 18.04 to 19.10, skipping 18.10 and 19.04. Please stop telling me that I can not skip releases.

You are advising (on your page) users a way to upgrade that is not advised by Canonical and is not how you upgrade Ubuntu. This is my point

That is how the Ubuntu upgrade procedure works under the hood. And I did say "After Ubuntu 19.04 reaches end-of-life in January 2020, Ubuntu 18.04 users can upgrade to 19.10 directly, following the standard upgrade procedure."

If an intermediate release is EOL, the install media for the release which you NEED to upgrade to should be used for the upgrade, you don't just leapfrog releases. This is not how you upgrade Ubuntu.

Then why Ubuntu officially allows users to upgrade from 18.04 to 19.10 directly?

Please convince Canonical to change the upgrade path, never allow users to upgrade from Ubuntu 18.04 to 19.10, before you make an attempt to convince me.

They can. I have shown how as well. Your guide is not how upgrades are done. The upgrade path is 18.04 -> 18.10 -> 19.04 then finally to 19.10

This is how Canonical say to upgrade their OS. You can't just jump between any two releases you like using your guide. It is not how this is done. The only supported upgrade paths are to the next LTS from the previous LTS (Ubuntu 18.04 to Ubuntu 20.04 and similar) or to the next normal release (Ubuntu 18.04 to Ubuntu 18.10 and similar). Anything else is not supported.

If you open the "software & update" app on Ubuntu and set "Notify me of a new Ubuntu version" to "For any new version", then open the "software updater" app to update software package, it will tell you that Ubuntu 19.10 is available to upgrade. If you click the "Upgrade" button, then it will guide you to upgrade Ubuntu 18.04 to 19.10. This is the current official way to upgrade from Ubuntu 18.04 to 19.10.

The software updater utility on the Ubuntu desktop tells users to upgrade from 18.04 to 19.10. Why Canonical make it this way for millions of Ubuntu users?

Can you not understand this?

Stop telling me that I can not skip releases.

As I said, convince Canonical to change the upgrade path, before trying to convince me.

The link you gave me (https://help.ubuntu.com/community/UpgradeNotes) is a community wiki. It's not in the official documentation.

I'm really angry at how you just keeping playing words. Is it so hard to admit you are wrong?

You said to me "Why do you think the do-release-upgrade command is used to upgrade releases? " Oh, you think do-release-upgrade is not used to upgrade to a newer release? Please tell me why!

Lets do it another way. He's used your guide and screwed his system. Can you please dig him out. I'm very sure the packages were fine before he stumbled upon your page.

Fuck you. His repository was broken before following my tutorial.

There's not any mention of ports.ubuntu.com in my tutorial.

As your name suggest, your head is made up of woods, so you have such low IQ.

I have already suggested a way to fix OP's problem.

Firstly, the OP didn't have a working sources.list file before following my tutorial. His repositories are:

deb http://ports.ubuntu.com/ubuntu-ports/ bionic main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ bionic main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ bionic-updates main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ bionic-updates main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ bionic-security main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ bionic-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ bionic-backports main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ bionic-backports main restricted universe multiverse

This is wrong, there's no Ubuntu repository at the ports.ubuntu.com address. I didn't tell the OP to use the http://port.ubuntu.com address.

OP should put the following lines in the /etc/apt/sources.list file.

deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse

Then update.

sudo apt update

And follow my upgrade tutorial again. If there's error later, post the error message on my web page, instead of asking this low IQ person.

@linuxbabe: Warning from Launchpad staff: comment #11 is not acceptable conduct on Launchpad. Please stop.

@cjwatson: I will be polite to those who can talk to me with normal logic. And I'm more than happy to help people fix problems.

I'll leave you to it. Note the OP states "Issues after a try to upgrade"

All yours

Yes, there are so many users who failed to install Ubuntu on their computer after trying, so Ubuntu must be faulty, right?

Ok lets dig you out. Xiao doesn't sound too useful.

If you run:

cat -n /etc/apt/sources.list

What is the full output please?

do-release-upgrade is more than just sed on the sources:

It performs some package transitions:
https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/data/DistUpgrade.cfg.xenial?h=ubuntu/focal-devel

It prevents people from moving from supported releases to unsupported releases if they are on legacy hardware:
https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeQuirks.py?h=ubuntu/eoan-devel#n297

Prevents the screenlocker from locking, potentially when the system configuration may not allow unlocking:
https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeQuirks.py?h=ubuntu/eoan-devel#n403

Makes sure there's sufficient disk space to start:

https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeQuirks.py?h=ubuntu/eoan-devel#n475

Handles the kernel HWE packages:
https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeQuirks.py?h=ubuntu/eoan-devel#n737

Makes sure desktops have their recommended packages installed:
https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeQuirks.py?h=ubuntu/eoan-devel#n807

And as some packages are moving from deb to snap distribution, makes sure those replacements are installed:
https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeQuirks.py?h=ubuntu/eoan-devel#n818

The sed approach may appear to work okay but the end result is a system that may be missing a lot of the transitions.

Thanks

Thanks for that. Explains a lot. This is the trouble with so called "guides" by people who don't fully understand the OS. They think they know a lot but actually know very little. This is far worse and dangerous than someone who knows very little but knows they have limited knowledge and so asks, so to not cause issues for themselves and others.

I suggest you revise or remove the page I emailed you about CORRECLY pointing out that it was wrong.

You still don't get it.

I'm not denying do-release-upgrade should be preferred. I did say in my article that "After Ubuntu 19.04 reaches end-of-life in January 2020, Ubuntu 18.04 users can upgrade to 19.10 directly, following the standard upgrade procedure." Standard upgrade procedure refers to do-release-upgrade or the software updater desktop app.

Now here is my question:

Andrew said to me in the email that " Why do you think the do-release-upgrade command is used to upgrade releases? " So Andrew think that do-release-upgrade is not used to upgrade to a newer release. That's wierd. Can you explain this to me, Andrew?

And here's how to solve OP's problem.

OP posted that his/her system architecure is amd64, as shown by the following two lines.

dpkg --print-architecture
amd64

However, OP is using ports.ubuntu.com repository, which is the repository for arm64,armhf,ppc64el,s390x. It's not for amd64.

 If OP is really using amd64 architecture, then the /etc/apt/sources.list file should contains the following line instead.

deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse

If OP is using ARM machine, then the /etc/apt/sources.list file should contains the following line instead.

deb [arch=arm64,armhf,ppc64el,s390x] http://ports.ubuntu.com/ eoan main restricted universe multiverse
deb [arch=arm64,armhf,ppc64el,s390x] http://ports.ubuntu.com/ eoan-security main restricted universe multiverse
deb [arch=arm64,armhf,ppc64el,s390x] http://ports.ubuntu.com/ eoan-backports main restricted universe multiverse

Note that OP's original sources.list file doesn't specify [arch=arm64,armhf,ppc64el,s390x] in the lines, so his/her repository is broken.

Conclusion:
1.) OP's repository file is broken before following my tutorial. And I found the solution.
2.) Andrew is so afraid to answer question: Why did he think that do-release-upgrade is not used to upgrade to a newer release. And he's so afraid to admit that he is wrong.

Hi Everyone,
Thank you all for trying to help me,
First I must say that Ubuntu first asks me to upgrade my version directly to 19.10 from version 18.04,
Second my sources.list:
deb http://archive.ubuntu.com/ubuntu/ bionic restricted main universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse

This is the output when I'm running sudo apt update:
Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
  Connection failed [IP: 91.189.88.162 80]
Err:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
  Connection failed [IP: 91.189.88.149 80]
Err:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease
  Connection failed [IP: 91.189.88.24 80]
Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
  Connection failed [IP: 91.189.88.162 80]
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Connection failed [IP: 91.189.88.162 80]
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Connection failed [IP: 91.189.88.149 80]
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-security/InRelease Connection failed [IP: 91.189.88.24 80]
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Connection failed [IP: 91.189.88.162 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

I must to admit that I have done something stupid and when I saw that my version was still 18.04 I uninstalled the "software updater".
So now I know that I didn't needed to mess with the APT system packages.

Now the situation is that I don't have the "software updater" installed, and my source.lists looks fine I think, and the errors that I get when I run the update command.

Many Thanks,
Jonathan

I'm using the same sources.list lines and I can update the repository without any problem. So you have a network problem. First, you should check the your computer's Internet connection is fine.

If Internet connection is not broken, but you still face this error, you can try other Ubuntu mirrors like us.archive.ubuntu.com. To change to this mirror, simple run the following command:

sudo sed -i 's/archive.ubuntu.com/us.archive.ubuntu.com/g' /etc/apt/sources.list

Then update.

sudo apt update

If it still doesn't work, you might want to use a proxy server or VPN to solve the connection problem.

To recap:

1.) OP said that his Ubuntu system prompted he to upgrade from 18.04 to 19.10 directly in the "software updater" app.
      Andrew's opinion: Never skip releases. Wrong. Ubuntu system prompted users to skip 18.10 and 19.04.

2.) OP tried to upgrade in the "software updater" app, but his computer had a network problem in the first place, so the upgrade failed and he didn't know why. He removed the "software updater", which OP admitted is stupid.

Then OP wants to try upgrade from command line, so he found my web page. However, the network problem wasn't solved when he was following tutorial. Andrew are so sure that my tutorial led to OP's problem. Wrong!

I'm sick and tired of Andrew's behavior. He really likes to accuse other people without concrete evidence. Andrew still are afraid to answer me this question: why did he think that do-release-upgrade is not used to upgrade to a newer release?

Lets help the user rather than some mud slinging nonsense. Editing the sources.list is only part of the steps that do-release-upgrade completes (as shown). This is also not how the official documentation on how to upgrade says to upgrade to a newer release.

For example
https://askubuntu.com/questions/34430/can-i-skip-over-releases-when-upgrading

Jon, do you use a proxy for web access at all?

Its the same error reported here. Please try the link in comment #3
https://answers.launchpad.net/ubuntu/+question/673653

By linking to this page (https://answers.launchpad.net/ubuntu/+question/673653), So you admit OP's problem is a common problem. It's not because of my tutorial, right?

Don't steal my answer, Andrew. OP should change to another mirror or use proxy server/VPN, as described in comment #22.

You really shouldn't link to such old post (https://askubuntu.com/questions/34430/can-i-skip-over-releases-when-upgrading), Andrew. What's right in the past might be not right now.

Didn't you see there are people who support the idea of skipping releases, Andrew?
https://askubuntu.com/questions/34430/can-i-skip-over-releases-when-upgrading#answer-1161354

Yes yourself....well done. Its not to be done. Lets help the user huh?

Stop stealing my answer. Don't make OP confused by your words.

"Yes yourself....well done. "

Yet another example of accusing other people without concrete evidence. Stop this, Andrew.