| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: https://bugs.gentoo.org/786699
Signed-off-by: Lars Wendler <polynomial-c@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/786699
Signed-off-by: Lars Wendler <polynomial-c@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/767172
Package-Manager: Portage-3.0.13, Repoman-3.0.2
Signed-off-by: David Michael <fedora.dm0@gmail.com>
Signed-off-by: Lars Wendler <polynomial-c@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
m68k and ~m68k trees are inconsistent. Let's drop keywords
down to ~m68k only. Profiles already accept both keywords:
ACCEPT_KEYWORDS="m68k ~m68k"
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
Remove USE=rpc support for all 4.x releases. Upstream removed RPC
support in the 4.8 series, but it was still present in older releases.
The upstream RPC server component (berkeley_db_svc) is single-threaded,
has no security, and other limitations that make it not suited for many
uses.
It could be revived by porting to use libtirpc, see
net-analyzer/argus/files/argus-3.0.8.2-rpc.patch as an example of some
of the required changes.
Fixes: https://bugs.gentoo.org/699750
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|