On 8/3/26 3:53 PM, Marcos Dione wrote:
On Mon, Aug 03, 2026 at 12:17:33PM +0200, Sebastiaan Couwenberg wrote:
Is there anything I can do to help this move forward?
Make the pybind11 build work, I managed to make it build successfully but it
would segfault on use.
python-mapnik would be served well by more active upstream developers, tagging
releases, and getting the package on PyPI.
On Fri, 07 Nov 2025 17:24:23 +0100, Bas Couwenberg wrote[1]
it still doesn't have upstream releases
There have been a couple of releases this year:
https://github.com/mapnik/python-mapnik/tags
Looks like the package on PyPI finally got updated too:
https://pypi.org/project/mapnik/#history
Long after the package was removed from Debian, though.
I just cloned the salsa repo, I'll see what can be done.
Cheers,
-- Marcos.
PS: I have never interactedas this level of involvement with Debian.
PLease let me know if I should use other methods.
For contribution to the Debian GIS team, you consult our team policy:
https://debian-gis-team.pages.debian.net/policy/
But I think you're better off maintaining the python-mapnik package in the
Python team.
Reintroducing the package should be easier when continuing from the last state
of the git repo, you can push a new copy to the python-team namespace when you
get added to the team.
Also read the relevant sections of the Developers Reference:
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#reintroducing-packages
Kind Regards,
Bas
--
PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
