dev-db/pgagent: new revision adding more upstream patches.
authorMichael Orlitzky <mjo@gentoo.org>
Sat, 19 Aug 2017 14:24:40 +0000 (10:24 -0400)
committerMichael Orlitzky <mjo@gentoo.org>
Sat, 19 Aug 2017 14:24:56 +0000 (10:24 -0400)
commitbb260f1b282cd12d863daf8b2898733b35334b95
tree7d6a1c37c0e572049c0321b8bbeca16157286962
parentf28d2aff162a4ebfa0507482820f718a7843523e
dev-db/pgagent: new revision adding more upstream patches.

There's a bug you can hit with pgAgent after an upgrade (like from
postgres-9.5 to postgres-9.6) that causes your jobs to get stuck in
a "Running" state. Since pgAgent thinks the job is running, it won't
start the job again the next time it's scheduled, even though the
job has actually completed successfully. To fix that issue, we apply
four new patches that add recent improvements from upstream:

  * Fix a crash from DBconn:GetLastError().
  * Save the stderr output in the jobstep log.
  * Add timestamps to the pgAgent logs.
  * And finally, fix the "job succeeded" check.

The intermediate patches are not strictly necessary, but they are
helpful, and most importantly, let us apply the upstream patches
cleanly without having to re-roll them.

Package-Manager: Portage-2.3.6, Repoman-2.3.1
dev-db/pgagent/files/add-log-timestamps.patch [new file with mode: 0644]
dev-db/pgagent/files/fix-dbconn-getlasterror-crash.patch [new file with mode: 0644]
dev-db/pgagent/files/fix-job-success-test.patch [new file with mode: 0644]
dev-db/pgagent/files/save-stderr-jobstep-output.patch [new file with mode: 0644]
dev-db/pgagent/pgagent-3.4.0-r3.ebuild [moved from dev-db/pgagent/pgagent-3.4.0-r2.ebuild with 88% similarity]