| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
Closes: https://github.com/gentoo/gentoo/pull/2180
Signed-off-by: Patrice Clement <monsieurp@gentoo.org>
|
| |
|
| |
|
|
|
|
|
|
| |
tarballs
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
|
|
| |
Fixes cross-compilation problems with mysql/postgesql plugins.
Also convert ebuild to EAPI=6 and cleanup slightly.
Closes: https://github.com/gentoo/gentoo/pull/2152
Package-Manager: portage-2.3.0
Signed-off-by: Patrice Clement <monsieurp@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
Recently upstream switched to a new HTTPS certificate by Let's Encrypt,
which has trust issues with currently stable app-misc/ca-certificates.
Package-Manager: portage-2.3.0
Signed-off-by: Patrice Clement <monsieurp@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
Signed-off-by: Patrice Clement <monsieurp@gentoo.org>
|
|
|
|
| |
Package-Manager: portage-2.3.0_p22
|
|
|
|
|
|
|
|
|
| |
>=app-admin/rsyslog-8.19.0 builds against dev-libs/libfastjson instead of dev-libs/json-c like
previous versions. To avoid runtime errors when mixing with depedencies which were build
against dev-libs/json-c we are now enforcing >=dev-libs/liblognorm-2.0.1 (first liblognorm
version in repository which requires dev-libs/libfastjson) dependency.
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While this version builds against =dev-libs/libfastjson-0.99.2 it does not
build against >dev-libs/libfastjson-0.99.2.
Additional, if you build rsyslog against dev-libs/json-c but build also against
dev-libs/liblognorm which was build against >dev-libs/libfastjson-0.99.2
you will get runtime errors.
To solve this problem we are restricting rsyslog-8.16.0 to build only against
dev-libs/json-c and also restricting to =dev-libs/liblognorm-1.1.2* (last
version which builds against dev-libs/json-c).
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
| |
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
| |
Thanks to Perfect Gentleman for the report.
Package-Manager: portage-2.2.28
|
|
|
|
|
|
|
|
|
| |
It's a new file that didn't match their previous naming scheme. Without it,
running ghe-backup/restore fails:
$ ghe-backup
/usr/bin/../share/github-backup-utils/ghe-backup-config: line 26: /usr/share/github-backup-utils/bm.sh: No such file or directory
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The output of qfile is used by checkrestart to get a list of programs
owning certain files. A feature of qfile is that its output is dependent
on the current working directory. Some of the files in its output aren't
programs and checkrestart crashed. This patch sets the cwd to / for the
qfile subprocess, so its output is as expected.
Thanks to Karl <karlc@keckec.com> for investigating the issue, providing
patch and explanation above.
This not a final soluation for the problem, but it's a good workaround
given there are not so many processes named after any directory in /.
Gentoo-Bug: 548920
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
| |
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- New upstream release (Fixes CVE-2016-6254)
- Dependency on sys-fs/xfsprogs atom can now be controlled using the
new "xfs" USE flag.
If you don't enable "xfs" USE flag the df plugin will be unable to
filter on XFS partitions.
- Fixes build issues with sys-fs/xfsprogs-4.7.0 (#590998)
- Cherry-picked patches for upstream issue "network plugin causes core
dumps" (#1870)
Gentoo-Bug: https://bugs.gentoo.org/590998
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
|
| |
Requiring <sci-libs/libsigrok-0.4 when building sigrok plugin because
plugin doesn't build against recent sci-libs/libsigrok.
Bug: https://github.com/collectd/collectd/issues/1574
Package-Manager: portage-2.3.0
|