Your message dated Fri, 06 Sep 2024 12:22:43 +0000
with message-id <e1smxz9-00cemw...@fasolo.debian.org>
and subject line Bug#1080959: fixed in pygresql 1:6.0.1-2
has caused the Debian Bug report #1080959,
regarding Does not support PostgreSQL 17
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.)
--
1080959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygresql
Version: 1:6.0.1-1
Severity: serious
Please port pygresql to PostgreSQL 17. 17.0 will be released in 3
weeks, and 17rc1 is already in unstable. pygresql is the only package
holding back the testing migration of postgresql-17.
67s ======================================================================
67s FAIL: test_pqlib_version
(tests.test_classic_functions.TestHasConnect.test_pqlib_version)
67s ----------------------------------------------------------------------
67s Traceback (most recent call last):
67s File
"/tmp/autopkgtest-lxc.yghnd19b/downtmp/autopkgtest_tmp/tests/test_classic_functions.py",
line 128, in test_pqlib_version
67s self.assertLess(v, 170000)
67s AssertionError: 170000 not less than 170000
67s
67s ----------------------------------------------------------------------
67s Ran 808 tests in 26.560s
https://ci.debian.net/packages/p/pygresql/testing/s390x/51277442/
This artificial version check seems to be the only test that is
failing, which is pretty silly when the package otherwise does work as
proved by all the other tests. Perhaps just remove it?
Christoph
--- End Message ---
--- Begin Message ---
Source: pygresql
Source-Version: 1:6.0.1-2
Done: Christoph Berg <m...@debian.org>
We believe that the bug you reported is fixed in the latest version of
pygresql, 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 1080...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Berg <m...@debian.org> (supplier of updated pygresql 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: SHA256
Format: 1.8
Date: Fri, 06 Sep 2024 11:45:22 +0000
Source: pygresql
Architecture: source
Version: 1:6.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Christoph Berg <m...@debian.org>
Closes: 1080959
Changes:
pygresql (1:6.0.1-2) unstable; urgency=medium
.
* Team upload.
* Disable server version checks. All other tests work, so there's no point
in insisting that the PG version is less than 17 or any other constant.
(Closes: #1080959)
Checksums-Sha1:
a543c68b69f678e94faa0bebfb24685085314a0a 2216 pygresql_6.0.1-2.dsc
b79b39e24db05b4630d7fa12f9e695920e26b629 7480 pygresql_6.0.1-2.debian.tar.xz
Checksums-Sha256:
ee76fc661fa9aaedff44087f36adce37818af499fe1d2444d4cf0528489531e1 2216
pygresql_6.0.1-2.dsc
9d157baa9d3b451eb7f319e21a8b4e89fdc364d58f49b2542ac382539d6e056b 7480
pygresql_6.0.1-2.debian.tar.xz
Files:
2e84e67a506df89b12a3af121439a00a 2216 python optional pygresql_6.0.1-2.dsc
25e00ec8efb115c2d62e286bbf007138 7480 python optional
pygresql_6.0.1-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmba8IEACgkQTFprqxLS
p66l0Q//eYqi69t7E8QHLlhJ/k81h0x8T/WoCMKS6BUYOSer8aezId7mqT9rbmTd
YC1PCUsijjRhnWRfAJQHJ8OAhXqHto66Ah3tcXyolb3j5+0XoDhn9iBknB2pu//l
g6gm3BN1rTUnnpGKWl3+Yq57VLEL1lNU5uIM6lYR8le+hrG+KXTGYJT2YZlptzEk
jFqjNbMToCUTVg8rGBPaAbReyTIc9s4uGsq2NB/toKEJLsaa+gmOwADOshCByvcG
qatgMo2ZFkwuCAXGlLWvInKVxU463qoqC2RaEDWNKqnuILLSv2BlG3cHIyiIAIkd
yv7Ka/C7dighwGJ41PRrHxJE+5hYQiOJCtTfFgN8MlwKYTkfPFnKUF7z5s51DCju
LuLw7EVIuZYFtx3mEzEBx1DIJ34PhsOEaqLEwnsWcnh4SuuurQYEXb4dxvoplBso
wG/g8HaFGcbh1lInt8IokpqFSgDB2+6sm1qjrOLLmX/rAUI3ErWsb7xVDtVk6Q9S
EGPdp5mdBK+uCuWiHTe3YUuFau27I49YxVM+RlxVi+vxSefN0svtNi60PWOMP1BL
TsrCUvLw+o6ThtYluJcumMUMMMa4qTUQwQYsmM7TQnysWNOEkS4OrYXNXzITb/Kg
frkOOu4D9ur2da6qtaSleZdMhmWTUMBTmNy7DKqKwDDq4I0Ma7M=
=s/4x
-----END PGP SIGNATURE-----
pgpfIVaG_YtFy.pgp
Description: PGP signature
--- End Message ---
