Update error vero4k

So just running the update manually (currently have the jan 2023 update) I noticed it flashes an error too quick to read. Tried updating from ssh and it looks like I have a sources problem

osmc@osmc:~$ sudo apt update && sudo apt full-upgrade
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.debian.org/debian bullseye InRelease                                                                  
Hit:3 http://ftp.debian.org/debian bullseye-updates InRelease                                                          
Ign:4 https://wagnerch.github.io/ppa/buster ./ InRelease                                                               
Err:5 https://wagnerch.github.io/ppa/buster ./ Release                                           
  404  Not Found [IP: 443]
Hit:6 https://ftp.fau.de/osmc/osmc/apt bullseye InRelease
Reading package lists... Done
E: The repository 'https://wagnerch.github.io/ppa/buster ./ Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Seems to be a relic of the old debian 11 testing? What changes should I make?

Here is my sources.list

osmc@osmc:/etc/apt$ cat sources.list
deb http://ftp.debian.org/debian bullseye main contrib non-free

deb http://ftp.debian.org/debian/ bullseye-updates main contrib non-free

deb http://security.debian.org/ bullseye-security main contrib non-free

deb http://apt.osmc.tv bullseye main

But this is in /etc/apt/sources.list.d

osmc@osmc:/etc/apt$ cd sources.list.d
osmc@osmc:/etc/apt/sources.list.d$ ls
osmc@osmc:/etc/apt/sources.list.d$ cat wagnerch-buster-ppa.list 
deb https://wagnerch.github.io/ppa/buster ./

Should I just delete wagnerch-buster-ppa.list ?

I would delete it. I’m pretty sure that’s not an OSMC source (I don’t have it in my list), so I wonder if you (or someone anyway) added it at some point in the past for some reason.


it was added when I enabled beta testing for Debian 11 I am sure. I deleted it and all seems well…

You would’ve used that repository to install a modified glibc to install Widevine support.
We never added this repository.

1 Like

Well that would explain it. Widevine must have installed it when it updated. Anyway it’s gone now so if it needs it or similar I’m sure it will add again…

It didn’t – but there were suggestions in the thread at the time to install that repository (not by me).

No big deal – just removing it should do the trick and you won’t need to add that repository again as we incorporated the changes from that developer in to our repository



I definitely didn’t add it myself…

We definitely didn’t add it

Perhaps you followed a script / tutorial somewhere to add Widevine support and it did it for you. Anyway as stated above, safe to remove and no longer needed.