On Thu, Oct 09, 2025 at 10:23:15PM +0200, Thorsten Glaser wrote: > On Thu, 9 Oct 2025, Andrew Bower wrote: > > >> Will you please also provide this in trixie-backports, if not > >> in a stable update (via point release), might be useful to ask > >> the SRM if they think this could go in. > > > >On the basis of your suggestion, I am inclined to do so! > > Thanks!
Excellent. Hope I can count on your backup if/as needed! > >> (And yes, I’m all for moving the “live” logfile to /var/log/ as > >> well; it exists for a reason, e.g. I put it on tmpfs on certain > >> (not work-related, please ignore the footer for this) systems, > >> and having PII outside, in /var/lib/, can be bad.) > > > >If we do this, I think best done before the backport or stable release > >update to minimise conffile churn for users (the logrotate definition). > > Agreed. > > >g1pi above had the idea of a symlink. Potentially fragile but I think it > >works. Both might be best. > > I’d also say both. Don’t change it in the installed header, so > upstream won’t complain, but patch the library to use the > location under /var/log/ and install the symlink nevertheless. > This way, the upstream location will also work, but nothing in > Debian should normally touch it, so the symlink will work (it > can break if logrotated). How does https://salsa.debian.org/debian/wtmpdb/-/merge_requests/3 look to you?
