No Tom. As you can see from the log, I upgraded the package as per upgrade instructions. In fact the only change I noticed in the weewx.conf file was the statyon_type, all the rest of the configuration was ok.
I didn't install a separate version. That's why I posted the log. You will also notice in the log that I answered No when asked about replacing the .conf file. Two problems encountered: no /etc/init.d/weewx script found, because I'm using systemd probably, and the second was the changing of the station_stype during the merge. On Saturday, October 31, 2020 at 3:00:25 PM UTC+1 [email protected] wrote: > Perhaps we are misunderstanding each other. As I understand it, you > originally installed V4.1 as a package. Later, you installed V4.2 using > setup.py. As I keep saying, package installs and setup.py are completely > different and share nothing in common. > > So, you didn't merge. You installed a completely new version in > /home/weewx. That is why it is using the simulator. > > In general, if you do a package install, then upgrade using a package > install. If you use a setup.py install, the upgrade using a setup.py > install. You mixed the two methods. > > Or, maybe I am misunderstanding something... > > -tk > > On Sat, Oct 31, 2020 at 6:54 AM Alessandro Del Prete < > [email protected]> wrote: > >> Thanks Tom. >> >> Is it normal that while upgrading, the merging process changed the >> station type in that way? I ask for next time I'll try the upgrade. >> >> On Saturday, October 31, 2020 at 12:32:21 PM UTC+1 [email protected] >> wrote: >> >>> See the Wiki article *Cleaning up old 'bad' data >>> <https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data>* for >>> an example of deleting unwanted records. In your case, you will need to >>> determine the starting and ending records of the simulator data, then >>> delete them. >>> >>> -tk >>> >>> On Fri, Oct 30, 2020 at 6:49 PM Alessandro Del Prete < >>> [email protected]> 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 [email protected] >>>> 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 [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-user/30a167cc-7a3a-48d1-870e-7a948cb679can%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/weewx-user/30a167cc-7a3a-48d1-870e-7a948cb679can%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> 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 [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/b8a574bc-6de5-4cf1-9156-6ed28f28a713n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/b8a574bc-6de5-4cf1-9156-6ed28f28a713n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/dc527774-e528-45ba-a560-a6e7610eb620n%40googlegroups.com.
