Your message dated Thu, 13 Mar 2025 21:13:18 +0100
with message-id <z9m8xjfawlhhu...@ramacher.at>
and subject line Re: Bug#1100424: RM: python-mapnik/1:0.0~20240222-5ab32f020-3
has caused the Debian Bug report #1100424,
regarding RM: python-mapnik/1:0.0~20240222-5ab32f020-3
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 ow...@bugs.debian.org
immediately.)
--
1100424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: python-map...@packages.debian.org
Control: affects -1 + src:python-mapnik
User: release.debian....@packages.debian.org
Usertags: rm
Please remove python-mapnik (and its nik4 rdep) from testing.
This only needs to happen from s390x, where both have already been removed in
unstable (via #1099637 & #1100041), but this has not resulted in britney
removing python-mapnik from s390x in testing.
Once mapnik migrates to testing, python-mapnik and nik4 should follow.
Kind Regards,
Bas
--- End Message ---
--- Begin Message ---
On 2025-03-13 19:33:44 +0100, Bas Couwenberg wrote:
> Package: release.debian.org
> Severity: normal
> X-Debbugs-Cc: python-map...@packages.debian.org
> Control: affects -1 + src:python-mapnik
> User: release.debian....@packages.debian.org
> Usertags: rm
>
> Please remove python-mapnik (and its nik4 rdep) from testing.
>
> This only needs to happen from s390x, where both have already been removed in
> unstable (via #1099637 & #1100041), but this has not resulted in britney
> removing python-mapnik from s390x in testing.
We can't do arch specific removals in testing. If python-mapnik would
have had the same version in testing and unstable, removal from unstable
would cause removal from testing. Since this is not the case, the
removal of the binaries on s390x only happens when python-mapnik
migrates to testing.
What is needed here is a skiptest hint for mapnik. It should migrate in
the next britney run.
Cheers
>
> Once mapnik migrates to testing, python-mapnik and nik4 should follow.
>
> Kind Regards,
>
> Bas
>
--
Sebastian Ramacher
--- End Message ---
