Hi,
Yes indeed, from my DebianCodeSearch infused survey;
it is something that about 90% of packages do.
The only thinks accepted nowadays is to leak old disused
systemd user ids because recycling these id's is worse
from a security point of view.
The other 10% are like this one; I filed individual bugs yesterday.
The Policy has a word on this:
https://www.debian.org/doc/debian-policy/ch-files.html#log-files
10.8. Log Files
Log files should be removed when the package is purged (but not
when it is only removed).
This should be done by the postrm script when it is called with the
argument purge
I think the discussion is more valuable than this particular package
so any hint on how to improve dh-cruft is appreciated.
... of course we can also wait for native dpkg support;
but this machine-parsable data could easily be later
on translated into something else under debian/ directory
https://lists.debian.org/debian-policy/1998/04/msg00089.html
Greetings
Alexandre
Le mer. 17 juin 2026 à 15:57, Steinar H. Gunderson <[email protected]> a écrit :
>
> On Wed, Jun 17, 2026 at 03:11:30PM +0200, Alexandre Detiste wrote:
> > This makes it piuparts compliant;
> > because piuparts does not actualy run the packages;
> > but I guess that after some real world usage of
> > this package there would be some files in this directory.
> >
> > Please ensure that this directory is cleansed on purge.
>
> Hi,
>
> While I can understand the reasoning behind this, do you know if this is
> actually something other packages do? Does Policy say anything about logs?
>
> /* Steinar */
