Your message dated Sat, 11 Apr 2020 12:32:22 +0200
with message-id <20200411103222.ga1614...@ramacher.at>
and subject line Re: Bug#956442: nmu:
python-mapnik_1:0.0~20200224-7da019cf9-1+b1
has caused the Debian Bug report #956442,
regarding nmu: python-mapnik_1:0.0~20200224-7da019cf9-1+b1
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.)
--
956442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: binnmu
nmu python-mapnik_1:0.0~20200224-7da019cf9-1+b1 . ANY . unstable . -m "Rebuild
with libboost-python1.67.0 (>= 1.67.0-17+b1)"
python-mapnik was rebuilt to drop Python 3.7 before libboost-python1.67.0,
hence it still depends on libboost-python1.67.0-py37 instead of
libboost-python1.67.0-py38.
Kind Regards,
Bas
--- End Message ---
--- Begin Message ---
On 2020-04-11 11:52:43 +0200, Bas Couwenberg wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian....@packages.debian.org
> Usertags: binnmu
>
> nmu python-mapnik_1:0.0~20200224-7da019cf9-1+b1 . ANY . unstable . -m
> "Rebuild with libboost-python1.67.0 (>= 1.67.0-17+b1)"
>
> python-mapnik was rebuilt to drop Python 3.7 before libboost-python1.67.0,
> hence it still depends on libboost-python1.67.0-py37 instead of
> libboost-python1.67.0-py38.
Scheduled.
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
