Since I upgrade to the 5.0.1 version : NO_PUBKEY E788768B9CB16E10

[Valerian Mezieres]

Hello

I Have been using Weewx on a raspberry pi 3 model B rev 1.2 for several years, and it works well for me.

But since I upgraded to version 5.0.1, I got an error message when I try to update the raspberry.

 "sudo apt update" returns Err :3 http://weewx.com/apt/python3 buster InRelease
  .../... : NO_PUBKEY E788768B9CB16E10

My Pi works under Raspbian Bullseye but in weewx.list there is

"deb [arch=all] http://weewx.com/apt/python3 buster main"

Does somebody know how to fix this ?

[Mario Wesolek]

https://weewx.com/docs/4.10/debian.htm

Reimport the Key 

[Valerian Mezieres]

Thank you. That solves my problem.

I'm not sure I could go on this post or if I have to open another discussion :

I did the upgrade of weewx to 5.0.2-1 and at the end of the upgrade I read :

"The following files might interfere with the init configuration:
  /etc/init.d/weewx
  /etc/systemd/system/weewx.service"

Is it a problem, and if so how could I fix it ?

[matthew wall]

On Monday, February 19, 2024 at 5:32:21 AM UTC-5 valerian...@gmail.com wrote:

Thank you. That solves my problem.

I'm not sure I could go on this post or if I have to open another discussion :

I did the upgrade of weewx to 5.0.2-1 and at the end of the upgrade I read :

"The following files might interfere with the init configuration:
  /etc/init.d/weewx
  /etc/systemd/system/weewx.service"

Is it a problem, and if so how could I fix it ?

it should not be a problem, but it might complicate the management of your system later.

the file /etc/init.d/weewx *should* be ignored, since your system uses systemd.

the file /etc/systemd/system/weewx.service will override the systemd unit that was installed by 5.0.2 at /usr/lib/systemd/system/weewx.service

that may or may not be what you want.

i would suggest that you stop weewx, move aside both files, then start weewx.  something like this:

sudo systemctl stop weewx

sudo mv /etc/init.d/weewx ~/weewx.rc-old

sudo mv /etc/systemd/system/weewx.service ~/weewx.service-old

sudo systemctl daemon-reload

sudo systemctl start weewx

if there are changes in the old systemd unit that you want to keep, then apply them using the .d pattern for overriding a systemd unit.  or just leave the /etc/systemd/system/weewx.service file in place.

m

[Valerian Mezieres]

Thanks.

Well I tried to disable the 2 files as you suggest, but I have some special changes in my old weewx.service and it did'nt work.

So I move back my weewx.service