Your message dated Mon, 4 Nov 2024 10:44:23 +0100 with message-id <102db8bf-b354-4751-83f8-606461bd4829@xs4all.nl> and subject line Re: Bug#1086615: nmu: python-mapnik_1:0.0~20240222-5ab32f020-2 has caused the Debian Bug report #1086615, regarding nmu: python-mapnik_1:0.0~20240222-5ab32f020-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1086615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086615 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nmu: python-mapnik_1:0.0~20240222-5ab32f020-2
- From: Bas Couwenberg <sebastic@xs4all.nl>
- Date: Sat, 02 Nov 2024 08:26:35 +0100
- Message-id: <[🔎] 173053239505.1682960.11648289826132636235.reportbug@osiris.linuxminded.xs4all.nl>
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 Kind Regards, Bas
--- End Message ---
--- Begin Message ---
- To: Adrian Bunk <bunk@debian.org>, 1086615-done@bugs.debian.org
- Subject: Re: Bug#1086615: nmu: python-mapnik_1:0.0~20240222-5ab32f020-2
- From: Sebastiaan Couwenberg <sebastic@xs4all.nl>
- Date: Mon, 4 Nov 2024 10:44:23 +0100
- Message-id: <102db8bf-b354-4751-83f8-606461bd4829@xs4all.nl>
- In-reply-to: <[🔎] ZyiP0quSzKWA9IiD@localhost>
- References: <[🔎] 173053239505.1682960.11648289826132636235.reportbug@osiris.linuxminded.xs4all.nl> <[🔎] 173053239505.1682960.11648289826132636235.reportbug@osiris.linuxminded.xs4all.nl> <[🔎] ZyiP0quSzKWA9IiD@localhost>
On 11/4/24 10:11 AM, Adrian Bunk wrote:On Sat, Nov 02, 2024 at 08:26:35AM +0100, Bas Couwenberg wrote: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=mapnikThis 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/inputMapnik 4.0.2 reverted the SONAME back to 4.0, I see that I didn't update the input plugin path for that.After that python-mapnik will still need a one-time binNMU, but future mapnik uploads will no longer break python-mapnik.That was the intention of the changes in 4.0.2. The fixed mapnik will be uploaded soon, once that's built & installed on all release architectures, I'll file a new binNMU bugreport for python-mapnik on all architectures. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---