Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

19.04 -> 19.10 pop_os upgrade fails with error 101 #50

Closed
FelixZangerl opened this issue Oct 22, 2019 · 3 comments
Closed

19.04 -> 19.10 pop_os upgrade fails with error 101 #50

FelixZangerl opened this issue Oct 22, 2019 · 3 comments

Comments

@FelixZangerl
Copy link

For me the official upgrade manuals also don't work. i get the message: failed to upgrade os: failed status: fetch of package x (where x is every time a different library). error trying to connect: network is unreachable. although i have a stable internet connection.

on my other devices where i have ubuntu everything worked via the command line. unfortunately not for pop-os.

none of the other terminal commands worked, these are:

apt full upgrade and
pop-upgrade release upgrade

@mmstick
Copy link
Member

mmstick commented Oct 22, 2019

As the error indicates, you aren't able to reach the server which has the package. The server is either offline, or that repository no longer exists.

@FelixZangerl
Copy link
Author

but it's a different package each time. no idea how to fix this.

via pop-upgrade release upgrade systemd:

release upgrade aborted: fetch of package 'firefox-locale-en_69.0.3+build1-0ubuntu1_amd64.deb' at http://us.archive.ubuntu.com/ubuntu/pool/main/f/firefox/firefox-locale-en_69.0.3+build1-0ubuntu1_amd64.deb failed: async fetch for "/var/cache/apt/archives/partial/firefox-locale-en_69.0.3+build1-0ubuntu1_amd64.deb" failed: http://us.archive.ubuntu.com/ubuntu/pool/main/f/firefox/firefox-locale-en_69.0.3+build1-0ubuntu1_amd64.deb: error trying to connect: Network is unreachable (os error 101)
pop-upgrade: dbus client error: calling ReleaseUpgradeFinalize method failed

@FelixZangerl
Copy link
Author

everything worked out fine now. i guess you were right @mmstick and the problem was just not reaching the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants