Re: [weewx-user] beta of V5.1.0 is available

[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*



On Sun, May 26, 2024 at 4:26 PM vince  wrote:

> 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"
>
>
>
> On Sunday, May 26, 2024 at 4:06:05 PM UTC-7 Tom Keffer wrote:
>
>> 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.
>>
>> On Sun, May 26, 2024 at 10:51 AM vince  wrote:
>>
>>> 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.
>>>
>>> On Saturday, May 25, 2024 at 4:05:02 PM UTC-7 Ian Millard wrote:
>>>
 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


 On 25 May 2024, at 23:06, Tom Keffer  wrote:

 python3 -m pip install weewx --upgrade -i


 --
>>> 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
>>> 
>>> .
>>>
>> --
> 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/4d268924-5eb0-4232-b685-2364fe4fef81n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group a

Re: [weewx-user] beta of V5.1.0 is available

[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"



On Sunday, May 26, 2024 at 4:06:05 PM UTC-7 Tom Keffer wrote:

> 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.
>
> On Sun, May 26, 2024 at 10:51 AM vince  wrote:
>
>> 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.
>>
>> On Saturday, May 25, 2024 at 4:05:02 PM UTC-7 Ian Millard wrote:
>>
>>> 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
>>>
>>>
>>> On 25 May 2024, at 23:06, Tom Keffer  wrote:
>>>
>>> python3 -m pip install weewx --upgrade -i 
>>>
>>>
>>> -- 
>> 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
>>  
>> 
>> .
>>
>

-- 
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/4d268924-5eb0-4232-b685-2364fe4fef81n%40googlegroups.com.

Re: [weewx-user] beta of V5.1.0 is available

[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.

On Sun, May 26, 2024 at 10:51 AM vince  wrote:

> 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.
>
> On Saturday, May 25, 2024 at 4:05:02 PM UTC-7 Ian Millard wrote:
>
>> 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
>>
>>
>> On 25 May 2024, at 23:06, Tom Keffer  wrote:
>>
>> python3 -m pip install weewx --upgrade -i
>>
>>
>> --
> 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/f652f376-0eb1-450c-988b-197d744c2dc6n%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zEDD6qGjF%3DBLhSH%3DresWaaqp-%3Dyjq0FEK1Wx61qOh51m9w%40mail.gmail.com.

[weewx-user] Rsync - how to prevent directory from deletion

['Tomasz Lewicki' via weewx-user]

Dear Weewx users.

I'd like to ask how can I prevent Rsync called by Weewx from deleting a 
directory or file on a remote server when refreshing the site with weather 
observations?

The problem is: I wrote short documentation for people visiting my PWS 
site. It is in directory called 'docs'. I put it manually to the main 
directory of remote WWW server (public_html). When my Weewx updates files 
and is sending them by Rsync, 'docs' directory is being deleted from 
server. I can't protect it by 'chatrr +i' in Linux because this is hosted 
server and I can't use all normal Linux system tools.

Some hints...? 

-- 
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/64c3f516-d468-4957-ad16-4810ee735b3fn%40googlegroups.com.

Re: [weewx-user] beta of V5.1.0 is available

[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.

On Saturday, May 25, 2024 at 4:05:02 PM UTC-7 Ian Millard wrote:

> 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
>
>
> On 25 May 2024, at 23:06, Tom Keffer  wrote:
>
> python3 -m pip install weewx --upgrade -i 
>
>
>

-- 
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/f652f376-0eb1-450c-988b-197d744c2dc6n%40googlegroups.com.