Your message dated Tue, 18 Oct 2016 12:00:11 +0000
with message-id <e1bwt3z-0007rb...@franck.debian.org>
and subject line Bug#838589: fixed in pg8000 1.10.6-1
has caused the Debian Bug report #838589,
regarding pg8000: please provide Python 3 package
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.)


-- 
838589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pg8000
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

The package does not seem to build a python3-pg8000 package, although,
according to upstream, pg8000 works with Python 3.

I am currently packaging the testing.postgresql package for unit testing
database applications, and it uses the pg8000 interface.

Could you please enable the build for Python 3 (and, if necessary for
doing so, package the latest upstream version beforehand)?

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: systemd (via /run/systemd/system)

-----BEGIN PGP SIGNATURE-----

iQJhBAEBCABLBQJX5A/9MRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MSHG5pa0BuYXR1cmFsbmV0LmRlAAoJELeaPBagxPKW
CKEP/34JRg9TEbmJR7vCmnhCkfQj629ybEWK5QTrhFCO5Cfv+xAu/mdA/izC2U2U
4uTXMhS3JoU+dwEVIwFtXXE8llIgvpDf4JvNjJt/BEVjjL/yMoF4t56QAmk9yD80
fFWEMWijXqDC0uvmqjGSCCwV3zR3ycXn1A0uB0Nh9IKbvcph1igTUhlLDlRJ1zMW
v09N5Ln2FL0oXlNEncqSa9Z9bmToyG7yCrFNrXTyE0uhgD4zpFLEZAjRfy1qbAco
rJXP3c4jzXj2rey2HplcgTaTDu03T1WjsECLitVv7aB4ugQeOWTFqgP2Cx1ONIRp
37iBu+mRVrTh1sPqTXAaYpkJFmroU7Fk9UG1PAB8dOaFX4qBTi6KYWgYtA6sabER
6I97Vj4ADhyqZFOGypoK0sUQaSi/iUFskwEVa9G0rW4Ln7RlKUXeRtlEs8JQllyg
t+OqHSLp9sUI6X2Kj9EsDF6ImYDW49GESpMIVnaahpEQEtA/Yv99xGsCN4GufR8O
v6SQEIbNUZG0UxOYhAWPHEQcbJD7Kw8hr5/tKuPlVE/f6gUg8eAvGvVgYNDjYCJv
WoUsibNhzwAnNmvsswQetgL5GbWXcBGsn/sBEtHdxYV/W0MTSa+25/QinQYTlfeQ
lQUQ3aKOCUGPRGk93r6c0neY187WmeiowI91woBLdIuud7r6
=VjWb
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
Source: pg8000
Source-Version: 1.10.6-1

We believe that the bug you reported is fixed in the latest version of
pg8000, 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 838...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominik George <n...@naturalnet.de> (supplier of updated pg8000 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: Thu, 13 Oct 2016 11:15:09 +0200
Source: pg8000
Binary: python-pg8000 python3-pg8000 python-pg8000-doc
Architecture: source all
Version: 1.10.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 
<python-modules-t...@lists.alioth.debian.org>
Changed-By: Dominik George <n...@naturalnet.de>
Description:
 python-pg8000 - Pure-Python PostgreSQL Driver (Python 2)
 python-pg8000-doc - Pure-Python PostgreSQL Driver (documentation)
 python3-pg8000 - Pure-Python PostgreSQL Driver (Python 3)
Closes: 838589
Changes:
 pg8000 (1.10.6-1) unstable; urgency=medium
 .
   * New upstream version.
   * Enable build for Python 3. (Closes: #838589)
     + Use pybuild build system.
   * Update packaging.
     + Raise compat level to 10.
     + Bump Standards-Version (no changes needed).
   * Move to team maintenance under DPMT.
   * Add myself to Uploaders.
   * Enable sphinxdoc and build -doc package.
Checksums-Sha1:
 095b48e544108d519c36ad2afe3f13ec21d5ea16 2267 pg8000_1.10.6-1.dsc
 eacf43a2a3d15c5172bc64714dee2223204fd59b 55130 pg8000_1.10.6.orig.tar.gz
 c4f3288df35b8bb4b5ffd511d0e6536297980458 3704 pg8000_1.10.6-1.debian.tar.xz
 201c7895275c56ede6a39eaf67036cae34093d18 44988 
python-pg8000-doc_1.10.6-1_all.deb
 4f0312fe5993df4c87fcbc83fdf52e1842f2fe05 31280 python-pg8000_1.10.6-1_all.deb
 86eeef123a8192cb23d2ce22f8fbbca74c80436c 31366 python3-pg8000_1.10.6-1_all.deb
Checksums-Sha256:
 73f72e0b8038f1b4b5e9451cf2849dc02da2f9b4c32d31093824e428c5212b9f 2267 
pg8000_1.10.6-1.dsc
 5b65b5c579255ddd3ab279eb84c1e86fb30a46e8835fc4be469f9c019de7cb4c 55130 
pg8000_1.10.6.orig.tar.gz
 bd4c5f0b301f6f26a78c9d4022ea995808b77843c159adcffbd4b8ca75b44b09 3704 
pg8000_1.10.6-1.debian.tar.xz
 79ebe3a74adb7cad111d1ed8531ce40b82522f1221e154ef4f512df44a9f56e9 44988 
python-pg8000-doc_1.10.6-1_all.deb
 29e5916330005e4b82f1b7d82c23e93c85f73b3a7c8aa6bdeaea36f03b0308fd 31280 
python-pg8000_1.10.6-1_all.deb
 3cb245c4cd9633c2f31326b18fa380278949ba8334922da88fd90557210dd662 31366 
python3-pg8000_1.10.6-1_all.deb
Files:
 f848bed394adfb0219bd9ffc8a318260 2267 python optional pg8000_1.10.6-1.dsc
 70051294ad70ddf3018e2b7e9989ba71 55130 python optional 
pg8000_1.10.6.orig.tar.gz
 414394b4f80421c14b631cbb49ee3142 3704 python optional 
pg8000_1.10.6-1.debian.tar.xz
 8fd31e71fbaef621febf47ca825aaf43 44988 doc optional 
python-pg8000-doc_1.10.6-1_all.deb
 b03bcf6998ee8037d529c71c5d17042c 31280 python optional 
python-pg8000_1.10.6-1_all.deb
 65be5d5b0dc3cc8d9e9c9b52c6898780 31366 python optional 
python3-pg8000_1.10.6-1_all.deb

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYBJG4AAoJEAgWueGMdiutam8P/jtkPzqbJZa1X/l+NFD7BVG8
9aMGDt1tbPg5ut6aH+3+8yl5juURzHlNTljKpyhzPp7SrZRkav5BADelitjpQXW3
JOi1SPTLV3gd9L1cDu9ph8Auo3L+0iXjfAg5YwE7GyHg5MW/bvNbyJxeBPXCK5W+
uXVGIePQMyf8dxvhJFd/mrKvTje8XxAQgx1yfVMADG+rHWqFW191oEi81PNfJ0Cp
sGSqS/TwDe3nSjBXwqTG4CU+OTfjZOelBYZ7jZRSh48f23L2kEVaJY09FijXWZTD
nj9c5P63VexZL0AgjL4aSwgKehSI42enUlalPiu/fFJx76rKOegyF9YOm0BzhVSL
+CYuR5Xu6BofgZD5vEvYfj/VGLRyeUpQBQJ3Fz1feFkTi/bCmMrTL5HlsfWSSRB3
i3+0GIA/zLjMMG7gBujSVkGwXJYA2Kk4MZXNuOryjw3rXo6/BoJStYYWGnBzZ93/
5m7VkWpUiSsf5iaMbTFSCj9cSsHqiq2DgU5Y7Q8BA7QaJJbEF6H5HGSaYLKdF566
g2Q5B21nzUZAXltKDQtj3H2flA0yCSMz+SZPaM8hLMMwPgeYYXl5woo5bRKcHEHO
TNyM4/AroBTv80Th9XHelH+YXCoCKJK16u8JCDpCTI4oFe1nhtNETQEgNt3/fBVW
WDzZFctryJCPKc1jdFVb
=uQ6u
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to