On Fri, Mar 17, 2023 at 03:42:59PM +0100, Diederik de Haas wrote: > Are there any new developments/insights after 5 years? > It would be great if this bug could be resolved.
Not much. Due to the M-A:interpreter problem python3-mako really cannot be M-A:foreign (as it depends on python3-markupsafe and technically exposes its architecture). However, python3-mako could be split into a package containing the module and a package containing the script. The package containing the script could plausibly become M-A:foreign. The module could plausibly become M-A:same (i.e. "M-A interpreter workaround"). We've done such a split for similar situations and it tends to be a 90% solution. Possible transition path: * Have python3-mako provide a virtual package mako-render. * Perform a MBF asking those packages that use mako-render to change their dependency on python3-mako to mako-render. * Wait for 90% of the bugs to be fixed. * NMU the rest. * Split mako-render out of python3-mako and set mako-render M-A:foreign. Do not dare asking whether this can be done for bookworm. Though the first step could be done to ease backporting. Helmut
