You can force it with the --allow-unauthenticated flag if needed....
https://askubuntu.com/questions/732985/force-update-from-unsigned-repository

There does seem to be some difference in debian11 re: apt-key (which now 
shows as deprecated) but I didn't get too far trying to work it.

"sudo apt-key list" should show you which keys you have imported currently. 
 You should have two keys there, one from Matthew and one from Tom, in 
addition to your normal os repo keys

On Thursday, November 11, 2021 at 2:48:25 PM UTC-8 [email protected] wrote:

> Thank you for the reply.
>
> Same result.
>
> Here is an an additional error that I did not notice before:
> The repository 'http://weewx.com/apt/python3 buster InRelease' is not 
> signed.
>
>
>
>
> On Thursday, November 11, 2021 at 2:28:07 PM UTC-8 vince wrote:
>
>> No, just try adding the key one more time than run apt-get update again.
>>
>> Same thing happened to me this morning setting up a new pi.
>>
>> On Thursday, November 11, 2021 at 1:29:33 PM UTC-8 [email protected] 
>> wrote:
>>
>>> On a fresh installation of Raspbian Bullseye (11.1)
>>>
>>> Following the instructions at https://weewx.com/docs/debian.htm
>>>
>>> wget -qO - https://weewx.com/keys.html | sudo apt-key add -
>>> wget -qO - https://weewx.com/apt/weewx-python3.list | sudo tee 
>>> /etc/apt/sources.list.d/weewx.list
>>>
>>> sudo apt-get update yields the following:
>>> The following signatures couldn't be verified because the public key is 
>>> not available: NO_PUBKEY [long string of alphanumeric characters]
>>>
>>> As a, probable, result 
>>> sudo apt-get install yields the following:
>>> Unable to locate package weewx
>>>
>>> What am I doing incorrectly?
>>> Should I revert to Buster?
>>>
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/788f20d8-3d3b-4f72-8253-3ae11d2a65a4n%40googlegroups.com.

Reply via email to