NEMS Linux Community Forum

Good Evening,

I know I don't NEED to run "sudo nems-update", but I am.....and it gets through the initial check and updates just fine, but when it hits the apt-get update and apt update, it is choking on a few of the servers all of a sudden.  


This is what just started acting up over the past few days.


===============
Running updates and fixes... Please wait for apt tasks to complete...
Done.
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://download.webmin.com/download/repository sarge InRelease
Hit:3 http://download.webmin.com/download/repository sarge Release
Hit:4 http://www.deb-multimedia.org stretch InRelease
Ign:5 http://webmin.mirror.somersettechsoluti ... repository sarge InRelease
Ign:6 http://ftp.debian.org/debian stretch InRelease
Hit:7 http://webmin.mirror.somersettechsoluti ... repository sarge Release
Hit:8 http://ftp.debian.org/debian stretch-updates InRelease
Hit:9 http://ftp.debian.org/debian stretch-backports InRelease
Hit:10 http://ftp.debian.org/debian stretch Release
Get:11 https://packages.sury.org/php stretch InRelease [6,760 B]
Err:11 https://packages.sury.org/php stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
Err:15 https://oph.mdrjr.net/meveric all InRelease
  Connection timed out after 120000 milliseconds
Err:16 https://oph.mdrjr.net/meveric stretch InRelease
  Connection timed out after 120001 milliseconds
Fetched 6,760 B in 4min 0s (28 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.sury.org/php stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
W: Failed to fetch https://oph.mdrjr.net/meveric/dists/all/InRelease  Connection timed out after 120000 milliseconds
W: Failed to fetch https://oph.mdrjr.net/meveric/dists/stretch/InRelease  Connection timed out after 120001 milliseconds
W: Failed to fetch https://packages.sury.org/php/dists/stretch/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
W: Some index files failed to download. They have been ignored, or old ones used instead.
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://download.webmin.com/download/repository sarge InRelease
Hit:3 http://download.webmin.com/download/repository sarge Release
Ign:4 http://webmin.mirror.somersettechsoluti ... repository sarge InRelease
Ign:5 http://ftp.debian.org/debian stretch InRelease
Hit:6 http://www.deb-multimedia.org stretch InRelease
Hit:7 http://webmin.mirror.somersettechsoluti ... repository sarge Release
Hit:8 http://ftp.debian.org/debian stretch-updates InRelease
Hit:9 http://ftp.debian.org/debian stretch-backports InRelease
Hit:10 http://ftp.debian.org/debian stretch Release
Err:11 https://packages.sury.org/php stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
0% [Working]

================




It has always, since day 1 given me this error:

*******
Err:11 https://packages.sury.org/php stretch InRelease
The following signatures couldn't be verified because the public key is not available:
NO_PUBKEY B188E2B695BD4743
*******

But it would always just skip and keep going....not hang for a few minutes.

Not a show stopper, just an FYI.

Thanks

Tony

I had the same problem I just googled the issue, and fixed it.

http://bfy.tw/NBYq

I suggest against "fixing" this - sury was purged from modern NEMS Linux. Are you certain you are on a current build? Sounds like you're on an old version (which means you also have the old versions of the check commands, and are on Stretch instead of Buster).