update - if you haven't reflashed your system yet and it's still hosed up,
can you try one thing for me ?
wget -qO - https://weewx.com/keys.html | sudo gpg --dearmor >
/etc/apt/trusted.gpg.d/weewx.gpg
Then if you run 'sudo apt-key list' it should show:
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d
instead (see apt-key(8)).
/etc/apt/trusted.gpg
--------------------
pub rsa2048 2012-04-01 [SC]
A0DA 38D0 D76E 8B5D 6388 7281 9165 938D 90FD DD2E
uid [ unknown] Mike Thompson (Raspberry Pi Debian armhf
ARMv6+VFP) <[email protected]>
sub rsa2048 2012-04-01 [E]
pub rsa2048 2012-06-17 [SC]
CF8A 1AF5 02A2 AA2D 763B AE7E 82B1 2992 7FA3 303E
uid [ unknown] Raspberry Pi Archive Signing Key
sub rsa2048 2012-06-17 [E]
/etc/apt/trusted.gpg.d/weewx.gpg
--------------------------------
pub rsa2048 2014-11-15 [SC]
EAC2 0711 8C0B D050 B835 9313 A0CB 255B 75BF 977C
uid [ unknown] Thomas Keffer (Author of weewx) <[email protected]>
sub rsa2048 2014-11-15 [E]
pub dsa1024 2014-01-28 [SC]
1E9F F20B 86EF 78AB 3B45 4944 ED44 4FCC F0E2 B09E
uid [ unknown] Matthew Wall (weewx) <[email protected]>
sub elg1024 2014-01-28 [E]
On Thursday, November 11, 2021 at 3:24:23 PM UTC-8 [email protected] wrote:
> I will re-flash the image and try again.
>
> Thank you Vince.
>
> On Thursday, November 11, 2021 at 3:16:09 PM UTC-8 vince wrote:
>
>> FWIW - I just tried another newly reflashed SD card and the commands
>> worked fine this time. The only difference I can think of is perhaps
>> there's some kind of timing issue under the hood. This time I did the
>> first command manually, then the second command manually.
>>
>> When I did them by cutting+pasting the two lines at once, that's when I
>> saw oddities occasionally.
>>
>> No explanation.
>>
>> On Thursday, November 11, 2021 at 3:03:34 PM UTC-8 vince wrote:
>>
>>> 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/7fb806c8-8705-4761-ac0e-90054f080c71n%40googlegroups.com.
