Failed updates

[nikki1066]

I have had the below message after updates failed. It suggests I post here.


I am currently on 3.6 but considering moving to 5 but not sure if I have to move through the different versions one by one. I am concerned that I may lose all my opera bookmark settings in the order they are displayed if I change?


Many thanks in advance for any help given


Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Hit:2 http://ppa.launchpad.net/nemh/systemback/ubuntu xenial InRelease
Hit:3 http://ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu xenial InRelease
Hit:4 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu xenial InRelease
Hit:5 http://repository.spotify.com stable InRelease
Hit:6 http://archive.canonical.com xenial InRelease
Hit:7 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Get:8 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:9 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Hit:10 https://deb.opera.com/opera-stable stable InRelease
Get:11 http://repo.linuxliteos.com/linuxlite citrine InRelease [2,107 B]
Get:12 http://repo.linuxliteos.com/linuxlite citrine/main amd64 Packages [19.2 kB]
Ign:13 https://repo.skype.com/deb stable InRelease
Ign:14 https://repo.skype.com/deb stable Release
Ign:15 https://repo.skype.com/deb stable/main amd64 Packages.diff/Index
Ign:16 https://repo.skype.com/deb stable/main all Packages
Ign:17 https://repo.skype.com/deb stable/main Translation-en_US
Ign:18 https://repo.skype.com/deb stable/main Translation-en
Ign:19 https://repo.skype.com/deb stable/main amd64 Packages
Ign:16 https://repo.skype.com/deb stable/main all Packages
Ign:17 https://repo.skype.com/deb stable/main Translation-en_US
Ign:18 https://repo.skype.com/deb stable/main Translation-en
Ign:19 https://repo.skype.com/deb stable/main amd64 Packages
Ign:16 https://repo.skype.com/deb stable/main all Packages
Ign:17 https://repo.skype.com/deb stable/main Translation-en_US
Ign:18 https://repo.skype.com/deb stable/main Translation-en
Ign:19 https://repo.skype.com/deb stable/main amd64 Packages
Ign:16 https://repo.skype.com/deb stable/main all Packages
Ign:17 https://repo.skype.com/deb stable/main Translation-en_US
Ign:18 https://repo.skype.com/deb stable/main Translation-en
Ign:19 https://repo.skype.com/deb stable/main amd64 Packages
Ign:16 https://repo.skype.com/deb stable/main all Packages
Ign:17 https://repo.skype.com/deb stable/main Translation-en_US
Ign:18 https://repo.skype.com/deb stable/main Translation-en
Ign:19 https://repo.skype.com/deb stable/main amd64 Packages
Ign:16 https://repo.skype.com/deb stable/main all Packages
Ign:17 https://repo.skype.com/deb stable/main Translation-en_US
Ign:18 https://repo.skype.com/deb stable/main Translation-en
Err:19 https://repo.skype.com/deb stable/main amd64 Packages
  504  Gateway Time-out
Fetched 347 kB in 14min 32s (397 B/s)
Reading package lists...
W: The repository 'https://repo.skype.com/deb stable Release' does not have a Release file.
E: Failed to fetch https://repo.skype.com/deb/dists/stable/...4/Packages  504  Gateway Time-out
E: Some index files failed to download. They have been ignored, or old ones used instead.

[firenice03]

[member=6906]nikki1066[/member]
There looks like an issue with skype..
https://www.freecinema2022.gq/forums/on-to...n#msg51984

You maybe able to remove that repo, uncheck it and try re running updates.

[nikki1066]

Thank you for your reply firenice03

I am a novice with much of this.
Where would I do this with repo?

[nikki1066]

[member=5414]firenice03[/member]

I have tried updating Lite sources to England, not sure if this is what you were suggesting.

I got this message...

Lite Sources was unable to update the cache.
This may just be a temporary connectivity issues with the update server.

[Valtam]

Please read the link he sent you, all the instructions are there within. Cheers.

[nikki1066]

Sorry I did not spot the link.

Thank you for pointing it out to me.

[nikki1066]

Many thanks [member=5414]firenice03[/member]  and [member=2]Jerry[/member] this is solved now.

[firenice03]

[member=6906]nikki1066[/member]
No worries and glad to hear to got it sorted out.