| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Versions added:
10_beta4
9.2.23
9.3.19
9.4.14
9.5.9
9.6.5
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
|
|
| |
Installed files are unchanged
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.2
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/5522
|
| |
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
|
|
|
| |
MariaDB 10.2 no longer includes MARIADB_BASE_VERSION but uses
MARIADB_VERSION_ID instead.
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
RepoMan-Options: --include-arches="arm"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
RepoMan-Options: --include-arches="arm"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
RepoMan-Options: --include-arches="arm"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
RepoMan-Options: --include-arches="arm"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
RepoMan-Options: --include-arches="arm"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
RepoMan-Options: --include-arches="arm"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
RepoMan-Options: --include-arches="arm"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
RepoMan-Options: --include-arches="arm"
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
|
|
|
|
| |
Bug 628484 - Add USE flag numa to pull in sys-process/numactl for build/runtime
Bug 628458 - Fix systemd case sensitivity in configure merged from 10.1 branch
Bug 628458 - Fix multilib header file changes that lead to build failure
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
|
|
|
|
|
|
|
|
| |
The flags USE=iodbc and USE=odbc are actually mutually exclusive. The
upstream build system doesn't crash at the moment, but will instead
select only one of them if both are specified -- probably not what you
want! This new revision adds an at-most-one-of constraint for those
flags, so that you must explicitly choose (only) the one you want.
Future versions of FreeTDS will throw an error if you ask for both.
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
RepoMan-Options: --include-arches="ppc ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
RepoMan-Options: --include-arches="ppc ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
RepoMan-Options: --include-arches="ppc ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
RepoMan-Options: --include-arches="ppc ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
RepoMan-Options: --include-arches="ppc ppc64"
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
|
| |
Package-Manager: Portage-2.3.7, Repoman-2.3.3
RepoMan-Options: --include-arches="ia64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.3
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
|
|
|
|
|
| |
Fixes: https://github.com/gentoo/gentoo/pull/5429
Package-Manager: Portage-2.3.7, Repoman-2.3.2
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This minor update includes a QA warning fix, and drops the
"--with-tdsver=7.4" from econf. The upstream default TDS version is
now "auto" and not the old "5.0".
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.2
Closes: https://github.com/gentoo/gentoo/pull/5354
|
|
|
|
|
|
| |
Gentoo-Bug: 585592
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
|
|
|
|
|
|
| |
The versions between 0.91 and 1.00.41 were all unstable on every arch,
so I removed them in favor of v1.00.41. The old v0.91 is only still
required because it's stable on hppa (where v1.00.41 is not). The one
patch in the files directory was obsolete after the cleanup, so it too
has been removed.
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.3
RepoMan-Options: --include-arches="ia64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.3
RepoMan-Options: --include-arches="ia64"
|