| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
RepoMan-Options: --include-arches="ia64"
|
|
|
|
|
|
| |
This reverts commit 8c98c95b939c0b40e9c061e7a5840db03bb2a652.
The patch is still used by 2.1.8-r1
|
|
|
|
|
|
|
|
| |
Thanks to Chris Mayo for getting this started.
Gentoo-Bug: 595378
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
|
|
| |
Remove 2.2.0 through 2.2.5.
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
|
|
| |
2.2.6 brings with it support for PostgreSQL 10.
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/show_bug.cgi?id=629906
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
|
|
|
| |
- Add missing build-time dependency dev-qt/qtconcurrent:5
Gentoo-Bug: 590028
Closes: https://github.com/gentoo/gentoo/pull/5613
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
Signed-off-by: Ettore Di Giacinto <mudler@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
Signed-off-by: Ettore Di Giacinto <mudler@gentoo.org>
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Gentoo-Bug: 627486
|
|
|
|
| |
Gentoo-Bug: 627486
|
|
|
|
| |
Gentoo-Bug: 627462
|
|
|
|
| |
Gentoo-Bug: 627462
|
|
|
|
| |
Gentoo-Bug: 627462
|
|
|
|
| |
Gentoo-Bug: 627462
|
|
|
|
| |
Gentoo-Bug: 627462
|
|
|
|
|
|
|
|
|
|
| |
- Dropped kde5-functions eclass
- Added l10n support
- Migrated fdo-mime to xdg eclass
- Improved overall ebuild quality.
Gentoo-Bug: 629322
Closes: https://github.com/gentoo/gentoo/pull/5557
|
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/5565
Package-Manager: Portage-2.3.2, Repoman-2.3.3
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|