> get rid of pkgos_postrm and use "yours" as a replacement?
No, absolutely not. I'm asking merely asking that pkgos_postrm, or the framework that insert it in the build also speak the same simplistic "wire protocol" as dh_cruft: that means writing in the resulting .deb a compliant /usr/share/cruft/<package> listing /var/lib<package-or-something>/ as volatile files not known to dpkg. The purge action is already correctly handled as required by Policy. It is a similar situation as this: I have a big python machinery that does RPC using python3-pika and marshalling of requests using python annotations. There's a reference python annotation. My DotNet colleague will just talk to RabbitMQ without using my Python library, just using the correct wire protocol. You can have a look at snake4, it is a tiny game that uses dh-cruft and build in a few seconds. I know it somewhat not easy to "sell" this idea at large, I m only asking here because I feel that 5 lines of code somewhere will fix this at once for all OpenStack packages then you ll never have to think about it again. Greetings Alexandre Le mar. 19 mai 2026, 08:44, Thomas Goirand <[email protected]> a écrit : > On 5/16/26 12:23 PM, Alexandre Detiste wrote: > > Package: openstack-pkg-tools > > > So each /usr/share/cruft/rules/${PKPRM_TEMPLATE_PREFIX} would contains: > > /var/lib/${PKPRM_TEMPLATE_PREFIX}/ > > /var/log/${PKPRM_TEMPLATE_PREFIX}/ > > > > /var/lock is on a tmpfs an as such out of scope. > > > > > > Greetings > > > > > > Alexandre > > Hi Alexander, > > Thanks for your bug report, however, I'm not sure what action you're > calling for. Are you asking that I get rid of pkgos_postrm and use > "yours" as a replacement? > > Cheers, > > Thomas Goirand (zigo) > >
