Question

3

Ubuntu 22.04 upgrade from 21.10 error

rated 0 times [ 3] [ 0] / answers: 1 / hits: 3933 / 2 Years ago, tue, july 26, 2022, 6:42:20

I tried to upgrade my Ubuntu from 21.10 to 22.04 with:

sudo do-release-upgrade -c

do-release-upgrade

but I always get an error:

Hit http://sk.archive.ubuntu.com/ubuntu jammy InRelease                        

Hit http://sk.archive.ubuntu.com/ubuntu jammy-updates InRelease                

Hit https://deb.nodesource.com/node_14.x hirsute InRelease                     

Hit http://sk.archive.ubuntu.com/ubuntu jammy-backports InRelease              

Hit http://security.ubuntu.com/ubuntu jammy-security InRelease                 

Ign https://packagecloud.io/ookla/speedtest-cli/ubuntu impish InRelease        

Err https://packagecloud.io/ookla/speedtest-cli/ubuntu impish Release          

  404  Not Found [IP: 50.18.207.89 443]                                        

Fetched 0 B in 0s (0 B/s)                                                      

Hit http://sk.archive.ubuntu.com/ubuntu jammy InRelease                        

Hit http://sk.archive.ubuntu.com/ubuntu jammy-updates InRelease                

Hit http://sk.archive.ubuntu.com/ubuntu jammy-backports InRelease              

Hit https://deb.nodesource.com/node_14.x hirsute InRelease                     

Hit http://security.ubuntu.com/ubuntu jammy-security InRelease                 

Ign https://packagecloud.io/ookla/speedtest-cli/ubuntu impish InRelease        

Err https://packagecloud.io/ookla/speedtest-cli/ubuntu impish Release          

  404  Not Found [IP: 184.72.30.82 443]                                        

Fetched 0 B in 0s (0 B/s)                                                      

Hit http://sk.archive.ubuntu.com/ubuntu jammy InRelease                        

Hit http://sk.archive.ubuntu.com/ubuntu jammy-updates InRelease                

Hit http://sk.archive.ubuntu.com/ubuntu jammy-backports InRelease              

Hit https://deb.nodesource.com/node_14.x hirsute InRelease                     

Hit http://security.ubuntu.com/ubuntu jammy-security InRelease                 

Ign https://packagecloud.io/ookla/speedtest-cli/ubuntu impish InRelease        

Err https://packagecloud.io/ookla/speedtest-cli/ubuntu impish Release          

  404  Not Found [IP: 50.18.207.89 443]                                        

Fetched 0 B in 0s (0 B/s)                                                      



Error during update 



A problem occurred during the update. This is usually some sort of 

network problem, please check your network connection and retry. 



W:Updating from such a repository can't be done securely, and is 

therefore disabled by default., W:See apt-secure(8) manpage for 

repository creation and user configuration details., E:The repository 

'https://packagecloud.io/ookla/speedtest-cli/ubuntu impish Release' 

does not have a Release file.

I tried to remove speedtest-cli, remove snap of speedtest, but nothing helped. Any idea what could I do?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

bjecterless

Add To Favorites

Follow

Total Points: 59

Total Questions: 96

Total Answers: 105

Location: Argentina

Member since Thu, Mar 18, 2021

3 Years ago

bjecterless questions

1 Ubuntu Studio automounts NTFS partition - how to disable?

Sun, Feb 5, 23, 17:04, 1 Year ago

1 Opened imagemagick using terminal, not sure how to close it now

Fri, Dec 16, 22, 13:24, 1 Year ago

1 In short i accidentally typed sudo rm /* and now my system doesnt boot as something is deleted in /

Sat, Sep 4, 21, 17:37, 3 Years ago

1 Display the contents of an HTML file on my desktop

Mon, May 9, 22, 00:28, 2 Years ago

1 Does the Ubuntu Newsletter still get sent over email?

Tue, Sep 21, 21, 04:00, 3 Years ago

View All

answered 2 Years ago trousransla · Accepted Answer

You should comment out the unofficial repositories before upgrading. This can normally be done in 2 ways:

Commenting out the relevant line from /etc/apt/sources.list

Renaming the relevant files inside the directory /etc/apt/sources.list.d

When you have performed the upgrade, check your old repos/files, and update them accordingly to the latest version. After that you can uncomment and/or rename the files back to activate the repositories.

For solution 1:

Find the lines containing https://deb.nodesource.com/node_14.x hirsute and https://packagecloud.io/ookla/speedtest-cli/ubuntu impish and put a # in front of the line.

For solution 2:

Find the files inside /etc/apt/sources.list.d that contains the above repositories. Rename those files, so they don't end with a .list extension (for instance, rename them to filename.list.old).