summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* dev-db/pgagent: remove "unused" pgagent-3.4.0-r1.ebuild.Michael Orlitzky2018-02-061-24/+0
| | | | Package-Manager: Portage-2.3.19, Repoman-2.3.6
* dev-db/pgagent: new revision adding more upstream patches.Michael Orlitzky2017-08-194-0/+676
| | | | | | | | | | | | | | | | | | | | 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: new patch to fix building against postgres-10.x.Michael Orlitzky2017-08-161-0/+52
| | | | | | | | | | | | The pgAgent build system didn't support a two-digit version of postgres, so pgagent failed to build against (for example) dev-db/postgresql-10_beta3. This has been fixed upstream but not yet released, so this commit cherry-picks that upstream commit as a patch and adds it (in-place) to the latest pgagent-3.4.0-r2.ebuild. Gentoo-Bug: 625878 Package-Manager: Portage-2.3.6, Repoman-2.3.1
* dev-db/pgagent: new revision with a dedicated "pgagent" user.Michael Orlitzky2017-08-161-0/+31
| | | | | | | | | | | | | | The pgagent daemon used to run as root, which can be dangerous. That system user is used to execute the database jobs, meaning that a non-root user with permission to schedule pgagent jobs could gain root. This new revision creates a dedicated "pgagent" system user, and the new init script launches the daemon as that user. An ewarn lets users know that some migration work may be needed. Gentoo-Bug: 537264 Package-Manager: Portage-2.3.6, Repoman-2.3.1
* Drop remaining $Id$ and $Header$ from files.Ulrich Müller2017-02-281-1/+0
| | | | Bug: 611234
* dev-db/pgagent: use #!/sbin/openrc-run instead of #!/sbin/runscriptAustin English2016-05-181-1/+1
|
* proj/gentoo: Initial commitRobin H. Johnson2015-08-082-0/+47
This commit represents a new era for Gentoo: Storing the gentoo-x86 tree in Git, as converted from CVS. This commit is the start of the NEW history. Any historical data is intended to be grafted onto this point. Creation process: 1. Take final CVS checkout snapshot 2. Remove ALL ChangeLog* files 3. Transform all Manifests to thin 4. Remove empty Manifests 5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$ 5.1. Do not touch files with -kb/-ko keyword flags. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration tests X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this project X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo developer, wrote Git features for the migration X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve cvs2svn X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014 work in migration X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed