Your message dated Tue, 10 Mar 2020 01:22:33 +0000
with message-id <e1jbtbn-0004rn...@fasolo.debian.org>
and subject line Bug#951842: fixed in gringo 5.3.0-11
has caused the Debian Bug report #951842,
regarding gringo needs a new upstream, and fixes for python3.8
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.)
--
951842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gringo
Version: 5.3.0-10
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8
gringo needs a new upstream, and fixes for python3.8. An example packaging can
be found at
https://launchpad.net/ubuntu/+source/gringo/5.4.0-0ubuntu1
Please note that I didn't address the GCC 8 -> GCC 9 move, which will also be
required for Debian.
--- End Message ---
--- Begin Message ---
Source: gringo
Source-Version: 5.3.0-11
Done: Thomas Krennwallner <tk...@kr.tuwien.ac.at>
We believe that the bug you reported is fixed in the latest version of
gringo, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Krennwallner <tk...@kr.tuwien.ac.at> (supplier of updated gringo package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 09 Mar 2020 13:31:25 +0100
Source: gringo
Architecture: source
Version: 5.3.0-11
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Thomas Krennwallner <tk...@kr.tuwien.ac.at>
Closes: 944178 951707 951842
Changes:
gringo (5.3.0-11) experimental; urgency=medium
.
* add support for python3.8, thanks to Steve Langasek
* compile with gcc-9 and g++-9
* debian/control: bump Standards-Version to 4.5.0 (no changes required)
* renamed debian/{NEWS,TODO}.Debian to debian/{NEWS,TODO}
Lintian tag incorrect-packaging-filename
* setup debhelper-compat 12.
Lintian tag package-uses-old-debhelper-compat-version
* debian/control: set Rules-Requires-Root to no
* debian/symbols: fix symbols for g++-9 >= 9.2.0
* Bug fix: "gringo needs a new upstream, and fixes for python3.8",
thanks to Matthias Klose (Closes: #951842).
* Bug fix: "gringo ftbfs with Python 3.8", thanks to Matthias Klose
(Closes: #951707).
* Bug fix: "non-standard gcc/g++ used for build (gcc-8)", thanks to
Matthias Klose (Closes: #944178).
Checksums-Sha1:
049d1e4e99c7f338491b6e826a5a6ae04f3a6a62 2149 gringo_5.3.0-11.dsc
d226549353f88f58b74a82225fab1327cbab5355 19088 gringo_5.3.0-11.debian.tar.xz
381933f70b79d2aa33f55f9dc97442095410699e 8299 gringo_5.3.0-11_amd64.buildinfo
Checksums-Sha256:
356ad44f21cd4513e1264f18da8505ab50f0c26ba581e8b8c572a39aedfff347 2149
gringo_5.3.0-11.dsc
cc602a18480ae47fa2f7d704010c7df4912fa9e621163da80bfc875f6dca917d 19088
gringo_5.3.0-11.debian.tar.xz
a62ae7b03763ba01aaec02d15a72908b041ccbcb82e6e6c1a5b18e22088fbfe1 8299
gringo_5.3.0-11_amd64.buildinfo
Files:
6bb4605d56eeb3f02ba2c0dd6cb97950 2149 interpreters optional gringo_5.3.0-11.dsc
b03752c3b8c15155ca09ae3200ed5041 19088 interpreters optional
gringo_5.3.0-11.debian.tar.xz
49fa00d68747adaa9f34e0e4fb72f0a7 8299 interpreters optional
gringo_5.3.0-11_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEzH7vLECGZFUde0TKJ5ffdKZmmqkFAl5m5Y0ACgkQJ5ffdKZm
mqm5JQ/+LDN22urZQoiaNUmd/YPCQmb1HalTnr2ZMrLzpyGKmR2Uu7Ah5spn0RRD
s6WgDUUuUkHgFn4l4zUIeB3RzXic8GWrsgXSe04zw9PnoHz1tji0goeuzvGAJDgm
peLTg++fzUIIYFVW+i1/eWfnPiamW6Af/d9FmjvHtOafQjBTvEoquXS2fauDXOqU
VXZDE0JaGOONfkIHFZotxbK+7fzGNp5kWT/Kp89RwgGhfF6oUGYV3HK1+aQpcJBi
lsfQCRmNPXV0uYyVwaSrXOOWe5WWmCaFgOkUjaBCeba9FjB4k5MB0TN07HiHwtc3
SXULbbYUeIWh4WiqNVVJ1/XZtXvOehV9dDd5cmmvlUFTLz39xn9Ayg+FrAEC3hvd
apOWf+fB2w7AIFVf7w92VB29DYS7b1MHKmWPWN8Q0eCz89xII7ADslQV3SJoZpSO
xvlHxWFlqK1b2T0Sczi1xu+/yTn7jA0yC5ZwMR0ajum7MuM0s+vkFDOhotPIhZ2X
dsxW8EagHMkaM+m7FY0JRRBemqomhtmizEOvdQkXUoDcTT1ED/vGZz65eEBgp+8l
188bPr9scRNaJIc7U8B3CTHz7Z8a8XQU0by4604rhst0pJ6vFXFQi0fzH8d7FbSs
irw8n8XpstOyopFUHchQoCFZR24SxoXXlLbkIbClB7HhEF9nn+o=
=J+1p
-----END PGP SIGNATURE-----
--- End Message ---