summaryrefslogtreecommitdiff
path: root/dev-util/kdevelop-python/kdevelop-python-5.1.1.ebuild
diff options
context:
space:
mode:
authorMichael Orlitzky <mjo@gentoo.org>2017-08-19 10:24:40 -0400
committerMichael Orlitzky <mjo@gentoo.org>2017-08-19 10:24:56 -0400
commitbb260f1b282cd12d863daf8b2898733b35334b95 (patch)
tree7d6a1c37c0e572049c0321b8bbeca16157286962 /dev-util/kdevelop-python/kdevelop-python-5.1.1.ebuild
parentf28d2aff162a4ebfa0507482820f718a7843523e (diff)
downloadgentoo-bb260f1b282cd12d863daf8b2898733b35334b95.tar.gz
gentoo-bb260f1b282cd12d863daf8b2898733b35334b95.tar.bz2
gentoo-bb260f1b282cd12d863daf8b2898733b35334b95.zip
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
Diffstat (limited to 'dev-util/kdevelop-python/kdevelop-python-5.1.1.ebuild')
0 files changed, 0 insertions, 0 deletions