“Please report this on the forum”
The last update attemptnin your log is 4th November. Is that when you got the error?
Have you tried rebooting and retriggering the update?
Hello
No : this error and message happened yesterday (17th).
I just done a reboot and received the same message and…
another one, saying: “there is no update available”.
???
Update error normally indicates that there is a problem with downloading the updates.
Would be interesting what sudo apt-get update gives you
sudo apt-get dist-upgrade
gives :
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... The following package was automatically installed and is no longer required:
rbp2-image-4.4.16-6-osmc
Use 'apt-get autoremove' to remove it.
Done
The following packages will be upgraded:
libmysqlclient18 libxslt1.1 mysql-common tzdata
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1099 kB of archives.
After this operation, 3072 B of additional disk space will be used.
Do you want to continue? [Y/n] y
WARNING: The following packages cannot be authenticated!
mysql-common libmysqlclient18 libxslt1.1 tzdata
Install these packages without verification? [y/N] y
Get:1 http://security.debian.org/ jessie/updates/main mysql-common all 5.5.53-0+deb8u1 [75.5 kB]
Get:2 http://ftp.debian.org/debian/ jessie-updates/main tzdata all 2016i-0+deb8u1 [186 kB]
Get:3 http://security.debian.org/ jessie/updates/main libmysqlclient18 armhf 5.5.53-0+deb8u1 [622 kB]
Get:4 http://security.debian.org/ jessie/updates/main libxslt1.1 armhf 1.1.28-2+deb8u2 [215 kB]
Fetched 1099 kB in 1s (584 kB/s)
Preconfiguring packages ...
(Reading database ... 26466 files and directories currently installed.)
Preparing to unpack .../mysql-common_5.5.53-0+deb8u1_all.deb ...
Unpacking mysql-common (5.5.53-0+deb8u1) over (5.5.52-0+deb8u1) ...
Preparing to unpack .../libmysqlclient18_5.5.53-0+deb8u1_armhf.deb ...
Unpacking libmysqlclient18:armhf (5.5.53-0+deb8u1) over (5.5.52-0+deb8u1) ...
Preparing to unpack .../libxslt1.1_1.1.28-2+deb8u2_armhf.deb ...
Unpacking libxslt1.1:armhf (1.1.28-2+deb8u2) over (1.1.28-2+deb8u1) ...
Preparing to unpack .../tzdata_2016i-0+deb8u1_all.deb ...
Unpacking tzdata (2016i-0+deb8u1) over (2016h-0+deb8u1) ...
Setting up tzdata (2016i-0+deb8u1) ...
Current default time zone: 'Europe/Paris'
Local time is now: Fri Nov 18 15:00:27 CET 2016.
Universal Time is now: Fri Nov 18 14:00:27 UTC 2016.
Run 'dpkg-reconfigure tzdata' if you wish to change it.
Setting up mysql-common (5.5.53-0+deb8u1) ...
Setting up libmysqlclient18:armhf (5.5.53-0+deb8u1) ...
Setting up libxslt1.1:armhf (1.1.28-2+deb8u2) ...
Processing triggers for libc-bin (2.19-18+deb8u6) ...
And then I’ve done apt-get autoremove to trash rbp2-image-4.4.16-6-osmc.
But I still have the same message…
This is your problem.
What’s apt-key list show?
gpg --keyserver subkeys.pgp.net --recv-keys 55BE302B will probably do it.
gives
/etc/apt/trusted.gpg
--------------------
pub 2048R/66C762CC 2014-06-06
uid Sam G Nazarko <email@samnazarko.co.uk>
sub 2048R/3965ED2E 2014-06-06
pub 2048R/00654A3E 2014-12-29
uid Syncthing Release Management <release@syncthing.net>
sub 2048R/F614F575 2014-12-29
sub 4096R/37C86D31 2015-05-11 [expires: 2025-05-08]
/etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg
----------------------------------------------------------
pub 4096R/2B90D010 2014-11-21 [expires: 2022-11-19]
uid Debian Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>
/etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg
-------------------------------------------------------------------
pub 4096R/C857C906 2014-11-21 [expires: 2022-11-19]
uid Debian Security Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>
/etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg
-------------------------------------------------------
pub 4096R/518E17E1 2013-08-17 [expires: 2021-08-15]
uid Jessie Stable Release Key <debian-release@lists.debian.org>
/etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg
-----------------------------------------------------------
pub 4096R/473041FA 2010-08-27 [expires: 2018-03-05]
uid Debian Archive Automatic Signing Key (6.0/squeeze) <ftpmaster@debian.org>
/etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg
--------------------------------------------------------
pub 4096R/B98321F9 2010-08-07 [expires: 2017-08-05]
uid Squeeze Stable Release Key <debian-release@lists.debian.org>
/etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg
----------------------------------------------------------
pub 4096R/46925553 2012-04-27 [expires: 2020-04-25]
uid Debian Archive Automatic Signing Key (7.0/wheezy) <ftpmaster@debian.org>
/etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg
-------------------------------------------------------
pub 4096R/65FFB764 2012-05-08 [expires: 2019-05-07]
uid Wheezy Stable Release Key <debian-release@lists.debian.org>
Should I use the command you gave?
Check your sources.list and make sure that you have added a key for any additional repositories that you have.
If the packages cannot be verified we will consider it a failed update for security reasons. It looks like you may have added new repositories but not added the keys. My key and the Debian keys are there, so that should be OK.
Sam, I did not add any new repository and the command line gives:
“gpg: keyserver receive failed: keyserver error”.
You appear to have added at least one repository: SyncThing; so you’ve definitely changes /etc/apt/sources.list.d.
Try removing the SyncThing repo.
Oh oh!
My bad 
. Sorry.
I don’t know how to do that but I’ll look tomorrow.
No problem
We are continually working on improving things. If the issues persists a log will be greatly appreciated
Best
Sam
Hello.
I have a directory called “syncthing.list.d” with, in it, a file called “syncthing.list”
which contains “deb http://apt.syncthing.net/ syncthing release”
1/ how can I remove it?
2/ will Syncthing still be working?
Did you import the key when you added the repository?
Run curl -s https://syncthing.net/release-key.txt | sudo apt-key add -
So did the key install return Ok?
Yes.
Then another key/repository seems to cause your problems
Maybe. But which one? And what should I do?
The latest update can’t be installed (my log) so, I am stuck…
Check your sources.list.d and sources.list