> On Nov 17, 2025, at 02:53, John Smith <[email protected]> wrote: > > On Mon, 17 Nov 2025 at 18:42, 'Cameron D' via weewx-user > <[email protected]> wrote: > " The weeWX Debian package has pre/post scripts that install the service > files during updates... I can't ever remember being prompted to approve/deny > SystemD service files..." > Because unlike config files, the user-modified unit files should be placed in > dirs like /etc/systemd/system where they simply override any unit file that > is installed/updated in the default locations assigned to packages. > I don't think apt/dpkg does any checks for such situations. > > That is straying beyond the scope of PR I filed, by all means file a feature > request, but let's stick to the topic at hand... > > SystemD or Python or anything else upgraded has changed somehow and people > expect weeWX will start on boot up, but that stopped happening with Debian > Trixie for me at least...
on the contrary, cameron's comment is exactly on point. systemd unit files are *not* conf files, so they may be replaced when you update/upgrade the weewx package. the pattern for customizing systemd units is the .d pattern. adding a dependency in systemd is a hack, not a real fix, for a number of reasons: 1) it does not fix the problem for every operating system and init system 2) it is a dependency that does not apply to every installation, 3) it is a dependency that is not part of weewx and that could change depending on a non-weewx component of the system we can provide examples, but each file that is actually activated on a user's system is a potential support problem for us. just as we have to minimize python module and os dependencies, we have to minimize init dependencies. otherwise long-term support and robustness suffer. a lot. we could take the route of not having any deb/rpm packages for weewx, and let someone else create those to include in debian or redhat or whatever. but some time ago we chose to do them, to make life easier for users and so that users could have weewx updates more frequently (if they choose) than the os releases. we have been fairly successful in keeping weewx packages robust wrt to the changes between os releases, and consistent across multiple operating systems (and their different uses of systemd, for that specific init system) is not the fix to make weewx retry mysql/maria/postgres connections and do nothing else until that connection is successful? m -- 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 visit https://groups.google.com/d/msgid/weewx-user/1BED7620-F00C-46D8-823B-5F34ACC77C59%40gmail.com.
