| Age | Commit message (Collapse) | Author |
|
Instead of using a separate `tmpfiles.d` definition to create
`/run/postgresql`, let the service unit take care of it on its
own. This prevents situations where the postgresql service can't
start because `systemd-tmpfiles` wasn't run yet.
Bug: https://bugs.gentoo.org/show_bug.cgi?id=563122
Package-Manager: portage-2.2.23
|
|
Package-Manager: portage-2.2.20.1
RepoMan-Options: --include-arches="alpha"
|
|
Package-Manager: portage-2.2.20.1
RepoMan-Options: --include-arches="arm"
|
|
Package-Manager: portage-2.2.20.1
|
|
Package-Manager: portage-2.2.20.1
RepoMan-Options: --include-arches="ia64"
|
|
Package-Manager: portage-2.2.20.1
RepoMan-Options: --include-arches="ppc"
|
|
Package-Manager: portage-2.2.22
RepoMan-Options: --ignore-arches
|
|
Package-Manager: portage-2.2.20.1
RepoMan-Options: --include-arches="x86"
|
|
Package-Manager: portage-2.2.20.1
RepoMan-Options: --include-arches="amd64"
|
|
Package-Manager: portage-2.2.22
RepoMan-Options: --ignore-arches
|
|
Security update fixes issues:
1. CVE-2015-5288: The crypt() function included with the optional
pgCrypto extension could be exploited to read a few additional bytes
of memory. No working exploit for this issue has been developed.
2. CVE-2015-5289: json or jsonb input values constructed from
arbitrary user input can crash the PostgreSQL server and cause a
denial of service.
Also added note for new installations that re-sourcing /etc/profile is
reuiqred to pick up environment changes, like MANPATH so man can find
pages installed in non-standard locations.
Package-Manager: portage-2.2.20.1
|