yes.  Maybe I cause my own problems by too much "cleaning up"

On Sunday, 1 November 2020 at 10:39:10 am UTC+10 alessandr...@gmail.com 
wrote:

> From the log of my upgrade below, you can clearly see that it says " *merging 
> previous and distribution into /etc/weewx/weewx.conf*".
> If I answer NO to replace my weewx.conf I expect the previous version's 
> weewx.conf to be used, *untouched*. Instead, I found the station_type 
> changed to simulator, all the rest was exactly the same.
>
> Configuration file '/etc/weewx/weewx.conf'
>  ==> Modified (by you or by a script) since installation.
>  ==> Package distributor has shipped an updated version.
>    What would you like to do about it ?  Your options are:
>     Y or I  : install the package maintainer's version
>     N or O  : keep your currently-installed version
>       D     : show the differences between the versions
>       Z     : start a shell to examine the situation
>  The default action is to keep your current version.
> *** weewx.conf (Y/I/N/O/D/Z) [default=N] ? N
> Installing new version of config file /etc/weewx/weewx.conf.dist ...
> saving previous config file as /etc/weewx/weewx.conf-4.1.1
> saving distribution config file as /etc/weewx/weewx.conf-4.2.0
> *merging previous and distribution into /etc/weewx/weewx.conf*
> Using configuration file /etc/weewx/weewx.conf-4.1.1
>
> On Sunday, November 1, 2020 at 1:28:54 AM UTC+1 Cameron D wrote:
>
>> There may be a bit of confusion in this thread about "merging".  My 
>> understanding and experience is that  with .DEB upgrades  there is no 
>> automatic merging of config file changes.
>> You run either with your old config or the new one.
>>
>> Every upgrade I do a manual check for changes and merge anything myself.
>> One case is weewx.conf, which contains a version number, with the comment 
>> "*do not modify this*".
>> So I modify it - such that my old config file matches the new version 
>> number.
>>
>> Cameron.
>>
>> On Saturday, 31 October 2020 at 11:49:44 am UTC+10 alessandr...@gmail.com 
>> wrote:
>>
>>> Hi Tom,
>>>
>>> I use ubuntu on an Intel NUC, with systemd, weewx 4.1 was installed as 
>>> package.
>>> I followed the upgrade guide, here was the result:
>>>
>>> The following packages will be upgraded:
>>>   weewx
>>> 1 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
>>> Need to get 1.207 kB of archives.
>>> After this operation, 47,1 kB of additional disk space will be used.
>>> Get:1 http://weewx.com/apt/python3 buster/main all weewx all 4.2.0-1 
>>> [1.207 kB]
>>> Fetched 1.207 kB in 6s (195 kB/s)
>>> Requesting to save current system state
>>> Successfully saved as "autozsys_sgety6"
>>> Preconfiguring packages ...
>>> (Reading database ... 245196 files and directories currently installed.)
>>> Preparing to unpack .../archives/weewx_4.2.0-1_all.deb ...
>>> Unpacking weewx (4.2.0-1) over (4.1.1-1) ...
>>> Setting up weewx (4.2.0-1) ...
>>> Installing new version of config file 
>>> /etc/weewx/skins/Seasons/current.inc ...
>>> Installing new version of config file 
>>> /etc/weewx/skins/Seasons/rss.xml.tmpl ...
>>> Installing new version of config file 
>>> /etc/weewx/skins/Seasons/seasons.js ...
>>> Installing new version of config file 
>>> /etc/weewx/skins/Standard/index.html.tmpl ...
>>>
>>> Configuration file '/etc/weewx/weewx.conf'
>>>  ==> Modified (by you or by a script) since installation.
>>>  ==> Package distributor has shipped an updated version.
>>>    What would you like to do about it ?  Your options are:
>>>     Y or I  : install the package maintainer's version
>>>     N or O  : keep your currently-installed version
>>>       D     : show the differences between the versions
>>>       Z     : start a shell to examine the situation
>>>  The default action is to keep your current version.
>>> **** weewx.conf (Y/I/N/O/D/Z) [default=N] ? N*
>>> Installing new version of config file /etc/weewx/weewx.conf.dist ...
>>> saving previous config file as /etc/weewx/weewx.conf-4.1.1
>>> saving distribution config file as /etc/weewx/weewx.conf-4.2.0
>>> merging previous and distribution into /etc/weewx/weewx.conf
>>> Using configuration file /etc/weewx/weewx.conf-4.1.1
>>> *update-rc.d: error: unable to read /etc/init.d/weewx*
>>> *dpkg: error processing package weewx (--configure):*
>>> * installed weewx package post-installation script subprocess returned 
>>> error exit status 1*
>>> Processing triggers for systemd (245.4-4ubuntu3.2) ...
>>> Errors were encountered while processing:
>>>  weewx
>>> ZSys is adding automatic system snapshot to GRUB menu
>>> *E: Sub-process /usr/bin/dpkg returned an error code (1)*
>>>
>>> No big issue regarding the missing /etc/init.d/weewx I guessed, the big 
>>> problem is that when weewx restarted I noticed totally wrong data.
>>>
>>> I quickly checked and compared the conf files, and I found out that 
>>> *station_type 
>>> = WeatherFlowUDP* was changed to *station_type = Simulator.*
>>> I reverted it to the original value, but unfortunately I have 3-4 
>>> minutes of bad data in the db now, and I also sent it to some weather 
>>> networks.
>>>
>>> Could this be due to the merging process of the conf files?
>>> Is there a way I can fix the database removing those bad records?
>>>
>>> Thanks for any help on this.
>>>
>>> Alessandro
>>>
>>> On Tuesday, October 27, 2020 at 1:14:04 PM UTC+1 tke...@gmail.com wrote:
>>>
>>>> Some new features, fixes some bugs.
>>>>
>>>> See the *Upgrade Guide <http://www.weewx.com/docs/upgrading.htm>* for 
>>>> instructions on how to upgrade.
>>>>
>>>> CHANGE LOG
>>>>
>>>> CHANGES COMING! This is the last release that will support the LaCrosse 
>>>> WS23xx,
>>>> Oregon WMR200 and WMR300 stations. In the future, they will be published as
>>>> unsupported extensions.
>>>>
>>>> Made it easier to add new, derived types via StdWXCalculate. Fixes issue 
>>>> #491.
>>>>
>>>> Changed the tag system slightly in order to make it possible for the XTypes
>>>> system to add new aggregations that take an argument.
>>>>
>>>> Added the new data types in the extended_wview schema to the WeeWX types
>>>> system. Fixes issue #613.
>>>>
>>>> Added ability to label left, right or both y-axes of graphs.  PR#610.
>>>> Fixes issue #609. Thanks to user Brent Fraser!
>>>>
>>>> Added units and labels for the lightning data types.
>>>>
>>>> Fixed problem where threads attempt to access non-existent database. Fixes
>>>> issue #579.
>>>>
>>>> Fixed problem that caused reporting units to revert to US if they were in a
>>>> mixed unit system. Fixes issue #576.
>>>>
>>>> Fixed problem that could cause the station registry to fail if given a 
>>>> location
>>>> with a non-ASCII location name.
>>>>
>>>> Changed TE923 bucket size from 0.02589 inches to 1/36 of an inch
>>>> (0.02777778 in). PR #575. Fixes issue #574. Thanks to user Timothy!
>>>>
>>>> Undocumented option retry_certificate has been renamed to retry_ssl, and 
>>>> now
>>>> covers all SSL errors (not just certificate errors). Fixes issue #569. 
>>>> Thanks
>>>> to user Eric!
>>>>
>>>> Fixed problem caused by specifying a [Logging]/[[formatters]] section in
>>>> weewx.conf that uses interpolated variables.
>>>>
>>>> Fixed problem in the Vantage driver that resulted in incorrect 
>>>> sunrise/sunset
>>>> being included in loop packets when run under Python 3. Thanks to users 
>>>> Constantine and Jacques!
>>>>
>>>> Improved auto-scaling of plot axes.
>>>>
>>>> Fixed problem where aggregates of windvec and windgustvec returned the 
>>>> aggregate
>>>> since start of day, not the start of the aggregation period. Fixes issue 
>>>> #590.
>>>>
>>>> New unit "beaufort", included in "group_speed". Treating beaufort as a 
>>>> separate
>>>> type has been deprecated. Fixes issue #591.
>>>>
>>>> New unit "kPa", included in "group_pressure". Fixes issue #596.
>>>>
>>>> Fixed bug in the simulator. Made it easier to subclass class Simulator.
>>>>
>>>> Expressions in StdCalibration are now ordered. Later corrections can 
>>>> depend on
>>>> earlier corrections.
>>>>
>>>> Fixed problem under Python 2, where option 'none' could cause exception.
>>>> PR #597. Thanks to user Clément!
>>>>
>>>> Fixed problem with ws23xx driver under Python 3 that caused it to crash.
>>>>
>>>> Use a more modern formula for heat index. Fixes issue #601. Thanks to
>>>> user Peter Q!
>>>>
>>>> Allow overriding the data binding when using iterators. Fixes issue #580.
>>>>
>>>> Fixed problem where old daily summaries may not have a version number.
>>>>
>>>> Fixed problem in WMR200 driver where missing UV reports as index 255.
>>>>
>>>> Added option 'force_direction' for working around a WU bug. Fixes issue 
>>>> #614.
>>>>
>>>>

-- 
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/4afa0953-db4b-4cc4-98b6-4dcf6cbdd749n%40googlegroups.com.

Reply via email to