Today I got an error “OSMC Update Error: Error installing: Please report this on the OSMC forum”.
I have uploaded my kodi.log with debug enabled here http://paste.osmc.io/urukanifup
Any help would be appreciated
Regards Neil
1 Like
There’s this other thread with the same issue: Kodi Update error
I’m unable to get the September update because of this. 
Hi Monchote,
Thank you for the link to your fix. I tried both the suggestions
sudo apt-get update
sudo apt-get dist-upgrade
and
sudo rm -r /var/lib/apt/lists/*
sudo mkdir /var/lib/apt/lists/partial
sudo apt-get update
This resulted in the following output
osmc@osmc:~$ sudo rm -r /var/lib/apt/lists/*
osmc@osmc:~$ sudo mkdir /var/lib/apt/lists/partial
osmc@osmc:~$ sudo apt-get update
Ign http://staging.apt.osmc.tv jessie InRelease
Err http://staging.apt.osmc.tv jessie Release.gpg
Something wicked happened resolving 'staging.apt.osmc.tv:http' (-5 - No address associated with hostname)
Ign http://staging.apt.osmc.tv jessie Release
Get:1 http://mirrordirector.raspbian.org jessie InRelease [14.9 kB]
Get:2 http://mirrordirector.raspbian.org jessie/main armhf Packages [8981 kB]
Err http://staging.apt.osmc.tv jessie/main armhf Packages
Something wicked happened resolving 'staging.apt.osmc.tv:http' (-5 - No address associated with hostname)
Err http://staging.apt.osmc.tv jessie/main Translation-en
Something wicked happened resolving 'staging.apt.osmc.tv:http' (-5 - No address associated with hostname)
Get:3 http://mirrordirector.raspbian.org jessie/contrib armhf Packages [37.5 kB]
Get:4 http://mirrordirector.raspbian.org jessie/non-free armhf Packages [70.3 kB]
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en
Ign http://mirrordirector.raspbian.org jessie/main Translation-en
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en
Fetched 9104 kB in 1min 29s (101 kB/s)
W: Failed to fetch http://staging.apt.osmc.tv/dists/jessie/Release.gpg Something wicked happened resolving 'staging.apt.osmc.tv:http' (-5 - No address associated with hostname)
W: Failed to fetch http://staging.apt.osmc.tv/dists/jessie/main/binary-armhf/Packages Something wicked happened resolving 'staging.apt.osmc.tv:http' (-5 - No address associated with hostname)
W: Failed to fetch http://staging.apt.osmc.tv/dists/jessie/main/i18n/Translation-en Something wicked happened resolving 'staging.apt.osmc.tv:http' (-5 - No address associated with hostname)
E: Some index files failed to download. They have been ignored, or old ones used instead.
osmc@osmc:~$ more /etc/ap
apm/ apt/
osmc@osmc:~$ more /etc/apt/sources.list
deb http://mirrordirector.raspbian.org/raspbian jessie main contrib non-free
deb http://staging.apt.osmc.tv jessie main
But I didn’t get very far and I still get the error “OSMC Update Error: Error installing: Please report this on the OSMC forum” when I restart my rpi2 and try the update again. The “sudo apt-get dist-upgrade” did update a bunch of things but I didn’t capture what it said It had updated. But I guess that worked because if I try and run it again it just says that there is nothing to update anymore
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I am far from an expert with linux but it does seem to me that it is having trouble connecting to “staging.apt.osmc.tv”
I tried from my windows machine to reach that address but it failed.
C:\Users\Neil>tracert staging.apt.osmc.tv
Unable to resolve target system name staging.apt.osmc.tv.
I have uploaded all the logs this time here http://paste.osmc.io/nabeviwuja in the hope that it might shine some light on my problem.
Thanks in advanace to anyone who helps out…
Regards
Neil.
You have put yourself on the old staging repo (now defunct) some time ago…
In /etc/apt/sources.list change deb http://staging.apt.osmc.tv jessie main
back to deb http://apt.osmc.tv jessie main
Correct. Fix that, and the issue should go away. I will restore the old A Record in the interim to fix this for other users who may be using this hostname.
Thank you both that has solved the issue.
However I am curious how I would have managed to do that as I don’t normally play with the OSMC setup via ssh at all as it normally just works without any issues. I normally only do the update via the automatic or manual update which has been working flawlessly for as long as I can remember. I can definatly say its not somthing that I have directly manually editied.
Regards
Neil
I can defiantly say this can only be done by a manually editing of a file. 
Thats the impression I got from ActionA’s initial response. However I have definatly not edited the file by hand and the update process has never shown an error before that I have seen. Hence why I was wondering how it could have happened. I guess it is almost impossible to know how it was set to an old repo. My only thought is that it has been set that way for a much longer period of time and it only just stopped working because the A Record reference that Sam mentioned was just removed recently.
Have you already changed the file? Otherwise please show the output of stat /etc/apt/sources.list
Also once more you not only have been on a old repo but you had been on a staging/testing repo which may indicate that at one point you want to try something that was still under testing at that time.
I have already changed the file so any evidence of when it was last modified has gone. It is possable that used to be on some kind of testing branch a long time ago I just can’t remember now. It seems like this is just going to remain a bit of a mystery.
Thank you again for helping solve my problem.
Exactly. The staging repo was an old testing branch.
This isn’t quite correct.
Between September and November 2015, there were installations which would have had staging.apt.osmc.tv in the sources.list instead of the normal apt.osmc.tv URL. This is because during filesystem generation, we wanted to use the most live mirror, but restoring the sources.list post-build did not work properly. If the user installed during this time, then it explains why the sources.list is not as expected.
The staging URL itself will not bring in staging packages; it is just a more real time server than some of our mirrors. Only if the jessie-devel suite is used will it use testing packages, and in turn, likely cause problems.
Sam
I stand now corrected 
Me too
That does sound like the most likely reason. I just double checked and the installer I used and it has the time stamp of 3rd Nov 2015 on it.
Again thank you all for the help.
Neil