On Tue, Aug 30, 2016 at 12:58:47PM -0700, Larry Dighera wrote: > > This page <https://www.debian.org/releases/stable/errata> states: > > "If you use APT, add the following line to /etc/apt/sources.list to be > able > to access the latest security updates: > > deb http://security.debian.org/ jessie/updates main contrib non-free > > After that, run apt-get update followed by apt-get upgrade." > > Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running Debian > Jessie results in an error message indicating that the public key is not > found. > It also finds two libraries that require updating that are not found when the > above mentioned /etc/apt/sources.list entry is removed. > > 1. What do I need to do to prevent the error message? > > 2. As there are other security related URLs (doubtless, as > distributed/released) that are checked during apt-get update, is the > recommended additional entry advisable/useful for this platform?
Debian or Raspbian? If Raspbian - that's based very closely on Debian but isn't strictly Debian. Mixing the two might not be a good idea since there will probably be incompatibilities at some level. There is a port of pure Debian to the Pi 2 - look on the Debian wiki - but no one has yet done this for the Pi 3 as far as I know. [The original Pi required different compilation options to cope with floating point "stuff" which rendered Debian incompatible: Raspbian is a re-compilation to suit the Raspberry Pi. Pi 2 is ARM v7 with hardware floating point. Pi 3 is 64 bit core (so arm64 would work if the Pi folk hadn't put in 32 bit glue logic or thereabouts). There are also issues with the way of loading the operating system, initialising video and non-free firmware which can cause problems.] All the best, AndyC
