Apt update source for weewx.

[Peter Fletcher]

The installation instructions add 'http://weewx.com/apt/python3 buster InRelease' to apt's list of sources for Debian installs, and this works. However, Debian and Raspbian have been up to bullseye for long enough that I have recently upgraded my main Pi (!) and weewx appears to run perfectly happily under bullseye. Has the old repository specification been retained to avoid confusion and because weewx is equally happy under the two recent versions of Debian, or does the wget installation source need to be updated?

[matthew wall]

On Saturday, July 2, 2022 at 4:14:37 PM UTC-4 Peter Fletcher wrote:

The installation instructions add 'http://weewx.com/apt/python3 buster InRelease' to apt's list of sources for Debian installs, and this works.

you can replace 'buster' with whatever you want.

we do not track specific debian (or ubuntu, or mint, or whatever) releases.  basically we target two debian releases: squeeze (for python2) and buster (for python3).

the weewx python2 deb package first worked with debian 6 (squeeze), and works with every subsequent debian release until the python2 packages are no longer provided.

the weewx python3 deb package first worked with debian 10 (buster) and will continue to work with every subsequent debian release until debian breaks the python3 packages.

m

 

[Peter Fletcher]

Thanks!

[didier....@gmail.com]

Hi

I have upgrade debian 10 to debian 11 bullseye, and I have changed /etc/apt/sources.list.d/weewx.list  with:

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

instead of deb [arch=all] http://weewx.com/apt/python3 bullseye main

But after apt update I have a warning/error about a control of sign in due to a no available public key (NO_PUBKEY E788768B9CB16E10)

Where is my mistake?

Thanks a lot

[didier....@gmail.com]

Hi again

Problem solved 

We need to re-import keys by this command:

curl -sSf 'https://weewx.com/keys.html' | sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/weewx.gpg --yes