Hi,
On Mon Nov 16, 2026 at 9:31 PM CET, Enrico Zini wrote:
On Sun, Nov 15, 2026 at 09:05:55PM +0100, Marco d'Itri wrote:
Is there a volunteer to draft the policy?
Here's my attempt at a draft. Can anyone see fundamental flaws?
Thank you!
+Similarly, Debian maintains system-wide datasets such as CA certificates or
+timezone information, which is kept current during the lifetime of a release.
+
+Packages should not ship or embed a copy of such databases without a good
+reason
Does this refer to similar databases which are part of the source
package, or to copies embedded into the binary at build-time starting
from the system db? (I assume the former, as this is in the "Source
packages" section)
This is because the yuzu package needs to ship with a custom time zone
database format into the binary, and it is generated from the tzdata
package while building.
Such scenario is still not ideal, but can be easily dealt with through
a binNMU. Having a source package ship its own database instead is way
more problematic in my opinion.
If we want to only disallow "custom" database shipped in source package,
then wording of the policy should be clearer about that. Something like:
Packages should not make use of their own version of such databases
without a good reason
Which:
- Allows packages to ship their own copies, but not use them
- Does not explicitly disallow copies of the system-wide datasets
(Postfix's chroot also comes to mind), unless they are different from
the system ones
Bye :)