| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| shebang | no | |||||
| no-tests-on-clean | prevent test cleanup on clean (this would need DBI in the Build-Depends) | Christoph Berg <myon@debian.org> | no | |||
| deprecate-which | commit 6fb2c997dd7bcbdc6f36dced60ccc82fb01a6d2f Debian deprecates `which`, use POSIX standard `command -v` instead debianutils (5.3-1) unstable; urgency=medium * The 'which' utility will be removed in the future. Shell scripts often use it to check whether a command is available. A more standard way to do this is with 'command -v'; for example: if command -v update-icon-caches >/dev/null; then update-icon-caches /usr/share/icons/... fi '2>/dev/null' is unnecessary when using 'command': POSIX says "no output shall be written" if the command isn't found. It's also unnecessary for the debianutils version of 'which', and hides the deprecation warning. -- Clint Adams <clint@debian.org> Fri, 20 Aug 2021 07:22:18 -0400 diff --git a/check_postgres.pl b/check_postgres.pl index ba28f27..be5ccdb 100755 |
Christoph Berg <christoph.berg@credativ.de> | no | 2021-09-09 | ||
| pg14-error | commit 5ca17990b26648d17c44741817d2c9654604d2c0 t/02_connection.t: Update for error message changed in PG14 diff --git a/t/02_connection.t b/t/02_connection.t index c298c40..958a4f5 100644 |
Christoph Berg <christoph.berg@credativ.de> | no | 2021-09-09 | ||
| 81e53fcdce88ddb1027872c6271edc5b8ab72fe8 | commit 81e53fcdce88ddb1027872c6271edc5b8ab72fe8 t/02_txn_time.t: Allow yet more time for longest transaction time This keeps failing on the apt.postgresql.org ppc64el buildd. diff --git a/t/02_txn_time.t b/t/02_txn_time.t index 78af814..cbd2af4 100644 |
Christoph Berg <myon@debian.org> | no | 2021-12-06 | ||
| fc7df276fce43678df291eef2dd79520f0bb2df9 | commit fc7df276fce43678df291eef2dd79520f0bb2df9 t/02_connection.t: Accept "statement timeout" in test The --timeout argument is racy, it sets an alarm() timer in check_postgres, but also statement_timeout on the PG server side. Usually the alarm() will hit first, but sometimes the statement_timeout hits as well. Seen on the slowish ppc64el buildd for apt.postgresql.org. diff --git a/t/02_connection.t b/t/02_connection.t index 958a4f5..5beb74e 100644 |
Christoph Berg <myon@debian.org> | no | 2021-12-06 | ||
| b2a8b98373c0c3d9787ef3ba477ca6a450aa890b | commit b2a8b98373c0c3d9787ef3ba477ca6a450aa890b t/04_timeout.t: Use longer timeouts to make test less racy The actual test runtime isn't affected, both tests should still finish after one second in normal circumstances. diff --git a/t/04_timeout.t b/t/04_timeout.t index 62d068c..7c9b000 100644 |
Christoph Berg <myon@debian.org> | no | 2021-12-06 |