[weewx-user] Re: Weewx 5.0 with Rpi4 bookworm 64bit

2024-01-25 Thread Paul L. McCord Jr.
Wow! I stared at this all day and it went right over my head. I did it and 
it worked. Thank you you both,

On Thursday, January 25, 2024 at 4:43:19 PM UTC-6 vince wrote:

> Again - please read Matthew's reply.  When you see that specific message 
> just import the keys-old.html file and it'll work.  Really.
>
> On Thursday, January 25, 2024 at 1:42:11 PM UTC-8 Paul L. McCord Jr. wrote:
>
>> I am also having this issue...
>>
>> weewx@weewx:~ $ sudo apt update
>> Hit:1 http://deb.debian.org/debian bookworm InRelease
>> Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease 
>>   
>> Hit:3 http://deb.debian.org/debian bookworm-updates InRelease   
>>   
>> Get:4 https://weewx.com/apt/python3 buster InRelease [3,614 B]   
>>
>> Hit:5 http://archive.raspberrypi.com/debian bookworm InRelease   
>>  
>> Err:4 https://weewx.com/apt/python3 buster InRelease
>>
>>   The following signatures couldn't be verified because the public key is 
>> not available: NO_PUBKEY ED444FCCF0E2B09E
>> Reading package lists... Done
>> W: GPG error: https://weewx.com/apt/python3 buster InRelease: The 
>> following signatures couldn't be verified because the public key is not 
>> available: NO_PUBKEY ED444FCCF0E2B09E
>> E: The repository 'https://weewx.com/apt/python3 buster InRelease' 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.
>>
>> On Wednesday, January 24, 2024 at 8:32:05 PM UTC-6 matthew wall wrote:
>>
>>> On Wednesday, January 24, 2024 at 12:48:33 PM UTC-5 
>>> stefanos...@gmail.com wrote:
>>>
>>>   The following signatures couldn't be verified because the public key 
>>> is not available: NO_PUBKEY ED444FCCF0E2B09E
>>> Reading package lists... Done
>>> W: GPG error: https://weewx.com/apt/python3 buster InRelease: The 
>>> following signatures couldn't be verified because the public key is not 
>>> available: NO_PUBKEY ED444FCCF0E2B09E
>>>
>>>
>>> sorry about that.  i rearranged the key files before i finished the rest 
>>> of the release.  keys have been restored.
>>>
>>> for future reference: the current keys will always be in 
>>> https://weewx.com/keys.html, while all of the keys (current and all 
>>> previous keys) will be in https://weewx.com/keys-old.html.  if you need 
>>> to install an older deb/rpm that was signed by an older key, use keys-old.  
>>> use keys.html for recent systems, since they will probably reject the older 
>>> keys we used to sign things before 2024.
>>>
>>> m
>>>
>>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fe745d1c-882d-4ac7-85bd-2f9642800f32n%40googlegroups.com.


[weewx-user] Re: Weewx 5.0 with Rpi4 bookworm 64bit

2024-01-25 Thread Paul L. McCord Jr.
I am also having this issue...

weewx@weewx:~ $ sudo apt update
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease 
  
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease   
  
Get:4 https://weewx.com/apt/python3 buster InRelease [3,614 B] 
 
Hit:5 http://archive.raspberrypi.com/debian bookworm InRelease 
   
Err:4 https://weewx.com/apt/python3 buster InRelease
  The following signatures couldn't be verified because the public key is 
not available: NO_PUBKEY ED444FCCF0E2B09E
Reading package lists... Done
W: GPG error: https://weewx.com/apt/python3 buster InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY ED444FCCF0E2B09E
E: The repository 'https://weewx.com/apt/python3 buster InRelease' 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.

On Wednesday, January 24, 2024 at 8:32:05 PM UTC-6 matthew wall wrote:

> On Wednesday, January 24, 2024 at 12:48:33 PM UTC-5 stefanos...@gmail.com 
> wrote:
>
>   The following signatures couldn't be verified because the public key is 
> not available: NO_PUBKEY ED444FCCF0E2B09E
> Reading package lists... Done
> W: GPG error: https://weewx.com/apt/python3 buster InRelease: The 
> following signatures couldn't be verified because the public key is not 
> available: NO_PUBKEY ED444FCCF0E2B09E
>
>
> sorry about that.  i rearranged the key files before i finished the rest 
> of the release.  keys have been restored.
>
> for future reference: the current keys will always be in 
> https://weewx.com/keys.html, while all of the keys (current and all 
> previous keys) will be in https://weewx.com/keys-old.html.  if you need 
> to install an older deb/rpm that was signed by an older key, use keys-old.  
> use keys.html for recent systems, since they will probably reject the older 
> keys we used to sign things before 2024.
>
> m
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6a32a898-fd8f-4f47-9492-7497546b9ab8n%40googlegroups.com.