Launchpad itself

Too many update errors

Asked by Alistair Fitchie

Have you had a big cleanout?
I've just done a clean install to 16.04 (with MATE), previously having ubuntu 14.04
Every update gives the following result

E: Failed to fetch http://ppa.launchpad.net/adamwolf/kicad-trusty-backports/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/adamwolf/kicad-trusty-backports/ubuntu/dists/xenial/main/binary-i386/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/ferramroberto/java/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/ferramroberto/java/ubuntu/dists/xenial/main/binary-i386/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/george-edison55/nitroshare/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/george-edison55/nitroshare/ubuntu/dists/xenial/main/binary-i386/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/ubuntu-mate-dev/ppa/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/ubuntu-mate-dev/ppa/ubuntu/dists/xenial/main/binary-i386/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/ubuntu-mate-dev/trusty-mate/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch http://ppa.launchpad.net/ubuntu-mate-dev/trusty-mate/ubuntu/dists/xenial/main/binary-i386/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.

Do I get rid of them, or is there a chance I can get updates from a place other than Launchpad?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Colin Watson
Solved:
Last query:
Last reply:
Revision history for this message
Best Colin Watson (cjwatson) said : 		#1

That probably means that those PPA owners haven't published anything in the respective PPAs for xenial. Given that some of them have "trusty" in the archive names, that seems quite understandable.

You can always replace "xenial" with "trusty" in the relevant apt sources and hope that the trusty packages will still work, which is quite possible. You might be able to simply get rid of the trusty-specific archives, as you probably don't need them any more. For any other questions, you should ask the people who own the archives in question; Launchpad just provides the hosting for those.

Revision history for this message
Alistair Fitchie (alistair-fitchie) said : 		#2

Thanks Colin Watson, that solved my question.

Revision history for this message
Alistair Fitchie (alistair-fitchie) said : 		#3

I won't be changing the names to trusty. I did experiment with the idea and got an unmet dependancies warning.