Your message dated Sun, 21 Apr 2013 11:17:31 +0000
with message-id <[email protected]>
and subject line Bug#705854: fixed in pgreplay 1.2.0-2
has caused the Debian Bug report #705854,
regarding pgreplay: FTBFS: cannot connect to database
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 [email protected]
immediately.)
--
705854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705854
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pgreplay
Version: 1.2.0-1
Severity: serious
Justification: fails to build from source
Builds of pgreplay in minimal environments (as on the autobuilders)
have been failing:
cd test && ./runtest.sh
Testing stderr log parsing ...
ok
Testing CSV log parsing ...
ok
Testing replay ...
skipped, cannot connect to database
To run this test, configure your environment so that this command succeeds:
"psql" -U postgres -d postgres -l
make[1]: *** [test] Error 1
Please fix runtest.sh to give pgreplay the benefit of the doubt if no
server is running.
Thanks!
--- End Message ---
--- Begin Message ---
Source: pgreplay
Source-Version: 1.2.0-2
We believe that the bug you reported is fixed in the latest version of
pgreplay, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Cyril Bouthors <[email protected]> (supplier of updated pgreplay 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sun, 21 Apr 2013 11:14:36 +0200
Source: pgreplay
Binary: pgreplay
Architecture: source amd64
Version: 1.2.0-2
Distribution: unstable
Urgency: low
Maintainer: Cyril Bouthors <[email protected]>
Changed-By: Cyril Bouthors <[email protected]>
Description:
pgreplay - replay PostgreSQL log files
Closes: 705854
Changes:
pgreplay (1.2.0-2) unstable; urgency=low
.
* test/runtest.sh.in: give the benefit of the doubt if no PostgreSQL
server is running because Debian does not allow unprivileged
PostgreSQL connections by default (closes: #705854).
Checksums-Sha1:
064803f3d93583b622726ac6f6a7f5740f442746 1114 pgreplay_1.2.0-2.dsc
ef7481b94c3130bdccc33bc4a1afa468aed28ba4 2098 pgreplay_1.2.0-2.diff.gz
51927a050c11dcb0f937cea2c313a50bdf32a29e 33566 pgreplay_1.2.0-2_amd64.deb
Checksums-Sha256:
440b6ab13288e246d71037a2d0cc45fb17db0799e6c4cc511ab8a960437f811e 1114
pgreplay_1.2.0-2.dsc
a9b31c45520c64612affc1846bba1be5a02675aa320ebf2be8daac2736b881cc 2098
pgreplay_1.2.0-2.diff.gz
ac77b039cd86b64fd2a4a7257d1792c9e46491a7cfbe8635399f47aea5d289b8 33566
pgreplay_1.2.0-2_amd64.deb
Files:
25f8ca2467f7889aa471d685be524727 1114 admin optional pgreplay_1.2.0-2.dsc
5eb82e46e718c55b9c3a5701f10d901c 2098 admin optional pgreplay_1.2.0-2.diff.gz
76b033fb8211a0ffbf68897650700571 33566 admin optional
pgreplay_1.2.0-2_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iD8DBQFRc8kNZ1SJHeqsYt8RAmWgAJ9QT/fZv8zd4wjOZX210I5h93QrrwCeK3um
4M9UisWXgj3IEkBU+oLieEk=
=JQSQ
-----END PGP SIGNATURE-----
--- End Message ---
