For ages (since woody, IIRC), I have been administering(=install some packages) all my servers with the use of a private Debian repository.
Recently, I switched from jessie to stretch. Ever since then, Release.gpg has not been accepted any more.
Before, the following was working very well:
sudo apt-key adv --keyserver keys.gnupg.net--search-keys C9384E910F2B8604
On https://wiki.debian.org/DebianRepository/UseThirdParty I read that this approach MUST NOT be used anymore -- why?
Hence, I tried the approach mentioned there:
Architectures: i386 amd64
I get then the following error messages:
Ign:1 http://debian.consecom.org/debian64 consecom InRelease
Get:2 http://debian.consecom.org/debian64 consecom Release [3,365 B]
Get:3 http://debian.consecom.org/debian64 consecom Release.gpg [836 B]
Get:4 http://security.debian.org stretch/updates InRelease [62.9 kB]
Err:3 http://debian.consecom.org/debian64 consecom Release.gpg
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C9384E910F2B8604
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://debian.consecom.org/debian64 consecom Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C9384E910F2B8604
W: Failed to fetch http://debian.consecom.org/debian64/dists/consecom/Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C9384E910F2B8604
W: Some index files failed to download. They have been ignored, or old ones used instead.
Without success (pleaes note: I do not make use of httpS and I put my settings in /etc/consecom).
Hence my question: What is the easiest way of migrating a private repository from jessie to stretch? Moreover, since the packages do not contain binaries and are debian release independent, I'd need to serve jessie and stretch from one repository.