Bug#1086615: nmu: python-mapnik_1:0.0~20240222-5ab32f020-2

[Adrian Bunk <bunk@debian.org>]

On Sat, Nov 02, 2024 at 08:26:35AM +0100, Bas Couwenberg wrote:
> Package: release.debian.org
> Severity: normal
> X-Debbugs-Cc: python-mapnik@packages.debian.org
> Control: affects -1 + src:python-mapnik
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> 
> nmu python-mapnik_1:0.0~20240222-5ab32f020-2 . riscv64 . unstable . -m "Rebuild with libmapnik-dev (>= 4.0.3)"
> 
> mapnik 4.0.3 was not yet installed on riscv64 with python-mapnik got built unlike the other architectures.
> 
> This should resolve the autopkgtest failure:
> 
>  https://qa.debian.org/excuses.php?package=mapnik

This is caused by:
/usr/lib/python3/dist-packages/mapnik/paths.py:inputpluginspath = '/usr/lib/x86_64-linux-gnu/mapnik/4.0.2/input'

In bookworm the path matches the soname:
/usr/lib/mapnik/3.1/input

This can be fixed in mapnik with something like:
-MAPNIK_SO_VERSION = $(shell echo $(UPSTREAM_VERSION) | sed -e 's/~.*//')
+MAPNIK_SO_VERSION = $(shell echo $(UPSTREAM_VERSION) | sed -e 's/~.*//' | cut -d. -f-2)

After that python-mapnik will still need a one-time binNMU,
but future mapnik uploads will no longer break python-mapnik.

> Kind Regards,
> 
> Bas

cu
Adrian