Control: severity -1 important Control: retitle -1 wtmpdb: provides no way to prune rotated logs (§10.8) Control: clone -1 -2 Control: retitle -2 wtmpdb: uses state directory for logs (§10.8, §9.11[FHS]) Control: notfixed -2 wtmpdb/0.74.0-1 Control: notfixed -2 wtmpdb/0.74.0-2 Control: fixed -2 wtmpdb/0.75.0-1 Control: tags -2 fixed-in-experimental
On Thu, Oct 09, 2025 at 08:04:29PM +0200, Thorsten Glaser wrote: > On Sat, 4 Oct 2025, Debian FTP Masters wrote: > > > * Rotate logs annually with logrotate (Closes: #1094965) > > 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. Based on user feedback and the fact this violates §10.8 by allowing indefinite growth, I am raising to 'important', initially, since apparently slow sqlite3 log growth rate over distro lifetime mitigates impact but please feel free to adjust the severity further if you see fit. > As things stands, the last(1) situation in trixie is unfortunate > in all directions. > > (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.) I am creating a new bug for this FHS violation (§9.11) and §10.8 for the purpose of the proposed stable update because it has different fix versions to the pruning issue. While I agree that /var/lib is the wrong place, it is at least arguable that it has similarity with other usages of the state directory, hence only 'important' initially. We can bundle failure to purge with the pruning issue.
