On Tue, Nov 17, 2026 at 12:27:34AM +0100, Andrea Pappacoda wrote:

Note: I agreed with Md's suggestion of splitting trust anchors from
other other system datasets; here I'd like to focus on the latter.

> 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.

I had a quick look. Would it in theory be possible to, say, ship tzdb2nx
in /usr/lib, and build it on the user's system?

This looks to me like a case for a tzdata dpkg trigger


> 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

This seems to go on the direction of prescribing that packages that need
to maintain a copy of a system-wide dataset should take actions to keep
their copy up to date when the system version changes.


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini <[email protected]>

Reply via email to