On Fri 05 Aug 2022 at 18:30:16 +0000, Andy Smith wrote: > Hello, > > On Fri, Aug 05, 2022 at 12:27:19PM -0400, Timothy M Butterworth wrote: > > On Fri, Aug 5, 2022 at 8:20 AM Brian <[email protected]> wrote: > > > W: GPG error: http://archive.debian.org/debian wheezy Release: The > > > following signatures couldn't be verified because the public key is not > > > available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY > > > 6FB2A1C265FFB764 > > > E: The repository 'http://archive.debian.org/debian wheezy Release' is > > > not signed. > > > N: Updating from such a repository can't be done securely, and is > > > therefore disabled by default. > > > N: See apt-secure(8) manpage for repository creation and user > > > configuration details. > > > root@test: > > > > > > According to the error messages you are missing the public signing key so > > the repos are being disabled. You will need to download and install the key. > > Just to be clear, you aren't replying to the OP. The OP has a > different problem. They need to work out why they are forbidden > (403) from browsing the wheezy repository. They can test if it works > in a regular web browser.
Unfortunately, the OP has not subscribed to -user. He is possibly sitting back awaiting replies in his personal mailbox > In Brian's case it is expected that the wheezy repository on > archive.debian.org gives these errors as the key has expired and > there is no valid key anywhere at this point, so as already > mentioned if one wants to use archive,debian.org for wheezy one > needs to override these errors, not search for a working key. Exactly. I tested. It was hardly rocket science. -- Brian.
