beta of V5.1.0 is available

[Tom Keffer]

New features

The biggest new feature is the ability for each report to use a separate locale. This allows you to produce a report tailored for, say, US English, with periods as decimal separators, and another report for German, with commas as separators.

In addition, there are a bunch of small bug fixes.

See the V5.1.0 change list for a complete list.

pip

To install the beta, you must use the pypi "test" repository:

# Activate your virtual environment:

source ~/weewx-venv/bin/activate

# Upgrade from the test repository:

python3 -m pip install weewx --upgrade -i https://test.pypi.org/simple

Note that a different repository has been specified with the "-i" option.

Debian

For Debian package installs, modify /etc/apt/sources.list as follows:

echo "deb [arch=all] https://weewx.com/apt-test/python3 buster main" | sudo tee /etc/apt/sources.list.d/weewx.list

Note the "apt-test". This tells apt to look there for the beta release, instead of the normal repository. You may want to change it back when you're done.

Red Hat

For Red Hat package installs, put this in /etc/yum.repos.d/weewx.repo

[weewx]
name=weewx
baseurl=http://weewx.com/yum-test/weewx/el9
enabled=1

Note the "yum-test". This tells yum to look there for the beta release, instead of the normal repository. Again, you may want to change things back when you're done.

OpenSUSE

For OpenSUSE installs, put this in /etc/zypp/repos.d/weewx.repo:

[weewx]
name=weewx
baseurl=http://weewx.com/suse-test/weewx/suse$releasever_major
enabled=1
gpgcheck=1

Note the "suse-test". This tells zypper to look there for the beta release, instead of the normal repository. Again, you may want to change things back when you're done.

Documentation

See https://www.weewx.com/docs/5.1/

What we're looking for

We are interested in your upgrade experience. 

• Did the installers get your configuration file right? 
• Skins? 
• Is the daemon configured correctly? 
• How about udev permissions?

It would also be nice if someone exercised the multiple locales feature. See the section Changing languages in the documentation.

[Ian Millard]

Tom,

With a pip install, a big tick in the box for the 4 four bullet points. Everything executed perfectly as far as I can see. The journal log is clean with no errors. Language options not tested,

Skins, Seasons and weewx-DivumWX Alpha (replacement for weewx-Weather34)

Hardware, Various Ecowitt  and Ecowitt 2000 Hub

Driver weewx-gw1000

Server Debian 12, Apache2 running on a re-purposed Apple MacMini

URLs, https://claydonsweather.org.uk and 

           https://claydonsweather.org.uk/seasons

IM

[vince]

Couple things.   In my case I'm upgrading 5.0.2 pip multi but I 'did' have a hand-patched weewxd.py to fix the loop_on_init not working issue.

First - I had to stop all weewx instances before forcing a pip upgrade to get the weewxd.py file to actually upgrade by adding the --force-reinstall switch to the pip command.  Can't explain that at all unless pip has some misfeature under the hood that won't change a file later hand-edited in version X that is upgraded in X+1.  Odd.

Second - what branch is the 5.1.0 beta off of ?  I know there are frequently changes made on master and not on development (ugh),  so wondering if there's some kind of backmerge massacre or the like that happened.   I guess I'm uncertain the changes you 'think' are in the beta code are really in there.  Might be worth a check.

Some examples:

• no loop_on_init messages are logged (pr 935)
• no listing of user groups is logged  (pr 934)

Best guess is you had a refactor massacre or merge massacre in https://github.com/weewx/weewx/commit/301872148163052e8860eb371fc7f8627a3ba881#diff-d4000f2ead6f89d7e914b2afed472744a1327c53978ab97a114fb79d7fdfac3a but at this point I can't follow which (believed to be in there) changes are actually in the current code on any branch.

[Tom Keffer]

The logging of loop_on_init and group ownerships both worked for me.

Make sure you're actually running v5.1.0. I had some issues doing a clean install, which, long story short, ended up with me installing v5.0.2. I then upgraded.

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/f652f376-0eb1-450c-988b-197d744c2dc6n%40googlegroups.com.

[vince]

Thanks.  As I mentioned in email, I had issues there too.  I wound up doing a force (re)install of 5.0.2 then an install (not a --upgrade) which picked up 5.1.0b4 that time.  Pretty odd.

Glad to see logging via syslog shows what version is actually starting...

pi@pi4:/var/log/weewx$ grep "Initializing" weewxd-vp2.log
May 26 10:17:51 pi4 weewxd-vp2[32270]: INFO __main__: Initializing weewxd version 5.0.2
May 26 10:25:59 pi4 weewxd-vp2[32469]: INFO __main__: Initializing weewxd version 5.0.2
May 26 12:08:31 pi4 weewxd-vp2[1217]: INFO __main__: Initializing weewxd-vp2 version 5.1.0b4

The first two are after attempts to upgrade that didn't upgrade for some reason.  The last one was after specifying a version ala "pip install -i https://test.pypi.org/simple/ weewx==5.1.0b4"

[Tom Keffer]

My fault with the instructions. If you're doing a clean installation, the problem is that the test PyPi repository has just V5.1.0, but none of its requirements, such as Pillow, CT3, etc. To get those, you need the main repository.

So, the instructions for a clean install become:

python -m pip install -i https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple weewx

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4d268924-5eb0-4232-b685-2364fe4fef81n%40googlegroups.com.

[michael.k...@gmx.at]

I did a pip upgrade on my test system, which runs reports in different languages, results:

lang = de_AT.utf8: https://kainzbauer.net/weather/Test/Rif/de/index.html => no difference

lang = en_US.utf8: https://kainzbauer.net/weather/Test/Rif/en/index.html => now displaying number with "." as decimal separator, etc. Hooray!

So the main feature seems to work :)

The version in my weewx.conf wasn't updated an still reads 5.0.2, the log is telling me:

2024-05-27 21:28:36 weewxd[14272] INFO weewxd: Initializing weewxd version 5.1.0b4
2024-05-27 21:28:36 weewxd[14272] INFO weewxd: Locale:       'de_AT.UTF-8'

[michael.k...@gmx.at]

Lol, the JS parts of my skin doesn't seem to be compatible with the new locale feature. Gotta work that out.

[Tom Keffer]

Thanks, Michael, for checking the locale feature!

The version number in the configuration file is the version of weewx that created it, not the installed version.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/93147e71-1b1f-42dc-a7f6-66e2967463d8n%40googlegroups.com.

[michael.k...@gmx.at]

Ah! I see.

An I think I've fixed the issue my skin had with the locale. It's late here, I'll keep you posted.

[michael.k...@gmx.at]

I've done the fixes in the skin (fuzzy-archer a.k.a. "bootstrap skin") and tested the following scenarios (system default locale on the test system: de_AT.utf8)

Compare base:

[StdReport]

   [[Bootstrap]]

        lang = de

=> generates a consistent German-Austria localisation web page.

Case 1:

[StdReport]

   [[Bootstrap]]

        lang = de_AT.utf8

=> no change in locale specific presentation, as expected, because the system default locale is the same as configured for the report

Case 2:

[StdReport]

   [[Bootstrap]]

        lang = en

=> the site is translated to english, but no change in locale specific presentation, as expected. Kind of ugly, a weird mix of en_US and de_AT localisation, especially since the page content generated with javascript uses the en_US locale when configured so. Weewx report generated content uses the default system locale.

Case 3:

[StdReport]

   [[Bootstrap]]

        lang = en_US.utf8

=> the site is translated to english, also locale specific presentation fot the weewx report generated content is changed, as expected. You guys from over the pond will have a smooth user experience when setting the language to english on my test site.

Bottom line: working as expected. Thank you for implementing this feature.

[Tom Keffer]

Nice!

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/452de36b-e5e9-4967-9419-574cf2d304a8n%40googlegroups.com.

[Ben Cotton]

On Sat, May 25, 2024 at 6:06 PM Tom Keffer <tke...@gmail.com> wrote:
>
> We are interested in your upgrade experience.

It fixed #940, which is nice. I did notice that the service didn't
restart, which I'd have expected from
https://github.com/weewx/weewx/blob/development/pkg/weewx.spec.in#L411-L413
After a manual `systemctl restart weewx`, everything seems fine. I
don't remember if that's worked in the past or not.

> Did the installers get your configuration file right?

I guess I didn't look closely when I upgraded to 5.0.0rc3, but it
looks like I've been using my 4.10.2 config file since May 15, 2023. I
suspect what's going on there is that since I have my config file in
Ansible, RPM noticed that it's not the same as in the package
(although in the past I'd typically copy the updated config file back
into Ansible after an upgrade, so it might just be that the timestamp
didn't match what RPM expected) and didn't overwrite the file. FWIW,
there is a /etc/weewx/weewx.conf-4.10.2-5.1.0b4 that is correct (and
runs fine once I copy it into /etc/weewx/weewx.conf)

> Skins?
> Is the daemon configured correctly?
> How about udev permissions?

Yes to all of the above.

--
Ben Cotton (he/him)
TZ=America/Indiana/Indianapolis

[Tom Keffer]

I'll look for a restart problem.

The config file is 100% upwards compatible, so when you upgrade to V5 the installer doesn't touch it unless you tell it to.

I don't know anything about Ansible, so I don't know how it would interact with it.

--
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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAJox117edsn3SYHPaczwSS_pw8O-7pgTTza%3DQJh%2B5ng%2B0swUww%40mail.gmail.com.

[vince]

For whatever you're doing with ansible.....if you are overwriting or editing weewx.conf then you need to trigger a sudo restart of weewx in your playbook.  Similarly if you have a playbook that does a version upgrade or the like.

[Tom Keffer]

I can confirm that weewxd did not restart after a v5.0.3 to v5.1.0 upgrade. We'll look into it. Thanks for the report, Ben!

-tk

On Tue, May 28, 2024 at 12:47 PM Ben Cotton <bco...@funnelfiasco.com> wrote: