sys-cluster/ceph: remove unused patche/files.

Closes: https://github.com/gentoo/gentoo/pull/6014

sys-cluster/maui: remove unused patches.

Closes: https://github.com/gentoo/gentoo/pull/6014

app-misc/elasticsearch: use /run/elasticsearch for tmpfiles.d.

Package-Manager: Portage-2.3.12, Repoman-2.3.3
Closes: https://github.com/gentoo/gentoo/pull/6048

app-misc/elasticsearch: use openrc-run variables.

Package-Manager: Portage-2.3.12, Repoman-2.3.3
Closes: https://github.com/gentoo/gentoo/pull/6048

net-analyzer/goaccess: version bump to 1.2.

1. Added geoipv2 USE-flag to support MaxMind's GeoIP.
2. Updated REQUIRED_USE.

Package-Manager: Portage-2.3.8, Repoman-2.3.2
Closes: https://github.com/gentoo/gentoo/pull/6064

net-misc/streamlink: version bump to 0.8.1.

Closes: https://github.com/gentoo/gentoo/pull/6118

net-misc/trackma: version bump to 0.7.4.

Closes: https://github.com/gentoo/gentoo/pull/6117

profiles: mask >=dev-util/scons-3.0.0

Bug: https://bugs.gentoo.org/635934

www-client/chromium: depend on >=net-libs/nodejs-6.9.4

Closes: https://bugs.gentoo.org/636586
Package-Manager: Portage-2.3.13_p1, Repoman-2.3.3_p81

package.mask: Improve audacious mask message

sys-libs/kpmcore: 3.2.1 version bump

Just a tiny fix for 'device not ready' error.

Package-Manager: Portage-2.3.13, Repoman-2.3.4

profiles: Mask Java 7

Java 7 is old and we are no longer able to support it. The ability to
build against Java 7 may return when we update the eclasses for Java 9
but the runtime will not return. If you need it then source ebuilds
will continue to be maintained by gnu_andrew in java-overlay for a few
years. Removal in 30 days.

profiles: Mask app-text/jmupdf

Upstream dead, bundles a vulnerable mupdf, nothing depends on it, and
blocks the removal of Java 7. Removal in 30 days.

Bug: https://bugs.gentoo.org/472832

dev-java/guava: Drop all pre-20 versions

These are unneeded now and this allows Java 7 to be removed.

Package-Manager: Portage-2.3.8, Repoman-2.3.2

dev-java/netbeans-enterprise: Remove old 8.2

Package-Manager: Portage-2.3.8, Repoman-2.3.2

dev-java/netbeans-enterprise: 8.2-r1 stable on amd64

Package-Manager: Portage-2.3.8, Repoman-2.3.2

dev-util/visualvm: Remove old 1.3.8-r1

Package-Manager: Portage-2.3.13, Repoman-2.3.2

dev-lang/scala: Drop all pre-2.11 versions

These require Java 7, which is going away.

Package-Manager: Portage-2.3.13, Repoman-2.3.2

dev-java/sbt: Drop old versions requiring Java 7

Package-Manager: Portage-2.3.8, Repoman-2.3.2

app-backup/tsm: Drop all old versions

Package-Manager: Portage-2.3.8, Repoman-2.3.2

app-backup/tsm: 7.1.2.1 and above supports Java 8

Package-Manager: Portage-2.3.8, Repoman-2.3.2

dev-java/netbeans-*, dev-util/netbeans: Drop NetBeans 8.1

dev-java/netbeans-*, dev-util/netbeans: Drop NetBeans 8.0

sec-policy: add blank line to silence repoman header warning

Package-Manager: Portage-2.3.8, Repoman-2.3.3

sec-policy: Release of SELinux policies 2.20170805-r3

Package-Manager: Portage-2.3.8, Repoman-2.3.3

media-gfx/exiv2: Fix exiv2-0.26-tools-optional.patch

Package-Manager: Portage-2.3.13, Repoman-2.3.4

net-print/hplip: Explicit install new hpps filter implementation in C

Package-Manager: Portage-2.3.8, Repoman-2.3.3

media-gfx/exiv2: Drop old

Package-Manager: Portage-2.3.13, Repoman-2.3.4

media-gfx/exiv2: Add 0.26_p20171104 snapshot

0.26 branch now contains all of my downstream backports.

Package-Manager: Portage-2.3.13, Repoman-2.3.4

dev-util/cmake: 3.9.5 version bump

Package-Manager: Portage-2.3.13, Repoman-2.3.4

x11-themes/audacious-themes: Modernise ebuild to EAPI 6

Package-Manager: Portage-2.3.13, Repoman-2.3.4

media-sound/audacious: Fix broken manifest

Package-Manager: Portage-2.3.13, Repoman-2.3.4

dev-cpp/catch: Bump to 2.0.1

dev-cpp/catch: Install using CMake

dev-cpp/catch: Update git branches

net-libs/miniupnpc: Drop old

dev-python/miniupnpc: Drop old

dev-python/miniupnpc: Bump to 2.0.20171102

net-libs/miniupnpc: Bump to 2.0.20171102

dev-python/pypy: Generate caches earlier, in compile

Generate the caches in compile phase since they are needed for tests.

Closes: https://bugs.gentoo.org/636490

dev-python/pypy: Remove incorrect pytest dep

dev-python/pypy: Remove unnecessary LD_LIBRARY_PATH

The pypy executable has $ORIGIN-based rpath.

profiles: unmask latest audacious 3.9 series

media-plugins/audacious-plugins: Version bump to 3.9

Closes: https://bugs.gentoo.org/564466
Closes: https://bugs.gentoo.org/572334
Closes: https://bugs.gentoo.org/572796
Closes: https://bugs.gentoo.org/573886
Closes: https://bugs.gentoo.org/573888
Closes: https://bugs.gentoo.org/590008
Closes: https://bugs.gentoo.org/611106
Closes: https://bugs.gentoo.org/636318
Closes: https://bugs.gentoo.org/636320
Package-Manager: Portage-2.3.13, Repoman-2.3.4

media-sound/audacious: Version bump to 3.9

* USE='gtk3' removed, seeing that upstream wants to
  remove GTK+3 support anyways.
* Remove all the minor arches, they are just pose a
  maintenance burden.

Closes: https://bugs.gentoo.org/556700
Closes: https://bugs.gentoo.org/629374
Package-Manager: Portage-2.3.13, Repoman-2.3.4

sys-devel/autogen: stable 5.18.4-r1 for ia64, bug #615008

Package-Manager: Portage-2.3.13, Repoman-2.3.4
RepoMan-Options: --include-arches="ia64"

x11-libs/compizconfig-backend-kconfig4: Remove last-rited package

Closes: https://bugs.gentoo.org/629236

dev-python/pynacl: Version Bump

Signed-off-by: Justin Lecher <jlec@gentoo.org>
Package-Manager: Portage-2.3.13, Repoman-2.3.4

dev-ruby/gherkin: cleanup; this slot was never used

Package-Manager: Portage-2.3.8, Repoman-2.3.3

app-emulation/wine-any: Bump to 2.19

Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-emulation/wine-any: Bump to 2.18

Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-emulation/wine-any: Refactor to dynamically add patchbin dep

Closes: https://bugs.gentoo.org/show_bug.cgi?id=635222
Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-emulation/wine-d3d9:  Bump to 2.19

Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-emulation/wine-d3d9: Bump to 2.18

Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-emulation/wine-d3d9: Refactor to dynamically add patchbin dep

Bug: https://bugs.gentoo.org/show_bug.cgi?id=635222
Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-emulation/wine-staging: Bump to 2.19

Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-emulation/wine-staging: add missing xfixes handling

Reported-By: Robert Walker <bob.mt.wya@gmail.com>
Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-emulation/wine-staging: Refactor to dynamically add patchbin dep

Bug: https://bugs.gentoo.org/show_bug.cgi?id=635222
Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-emulation/wine-vanilla: Bump to 2.0.3

Closes: https://bugs.gentoo.org/show_bug.cgi?id=635928
Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-emulation/wine-vanilla: Bump to 2.20, add krb5 support

Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-emulation/wine-vanilla: Refactor to dynamically add patchbin dep

Bug: https://bugs.gentoo.org/show_bug.cgi?id=635222
Package-Manager: Portage-2.3.13, Repoman-2.3.4

dev-ruby/slow_enumerator_tools: initial import of 1.0.0

New dependency for www-apps/nanoc

Package-Manager: Portage-2.3.8, Repoman-2.3.3

www-apps/nanoc: cleanup

Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-misc/memcached: 1.5.3 bup

Package-Manager: Portage-2.3.8, Repoman-2.3.4

sys-cluster/cinder: 11.0.1 bup

Package-Manager: Portage-2.3.8, Repoman-2.3.4

dev-python/botocore: add myself as maintainer

This is by agreement with current maintainer, alunduil.

Package-Manager: Portage-2.3.12, Repoman-2.3.3

dev-python/boto3: add myself as maintainer

This is by agreement with current maintainer, alunduil.

Package-Manager: Portage-2.3.12, Repoman-2.3.3

dev-python/boto3: allow recent Sphinx versions

Bump upper boundary of allowed version of Shpinx to 1.7 in new,
non-stabilized boto3 ebuilds.

Dependency on Sphinx has versions range. Declaration of this range comes
from requirements-docs.txt in boto3 sources, but that file hasn't been
updated since 2015. Latest Sphinx, version 1.6.5, builds boto3 docs
successfully.

Sphinx versions range bump has been suggested to boto3 maintainers, but
there's nothing preventing newer Sphinx from working on already released
versions.

Link: https://github.com/boto/boto3/pull/1337
Acked-by: Alex Brandt <alunduil@gentoo.org>
Package-Manager: Portage-2.3.12, Repoman-2.3.3

dev-python/boto3: add 1.4.7 ebuild

Copied from 1.4.4 ebuild with such changes:

* stable keywords downgraded to testing
* dev-python/botocore dependency versions range updated to require 1.7.*
  in accordance with upstream setup.{cfg,py}

Acked-by: Alex Brandt <alunduil@gentoo.org>
Package-Manager: Portage-2.3.12, Repoman-2.3.3

dev-python/boto3: add 1.4.6 ebuild

This version is not the latest one, but it is the only one expecting
botocore of version 1.6.*.

Copied from 1.4.4 ebuild with such changes:

* stable keywords downgraded to testing
* dev-python/botocore dependency versions range updated to require 1.6.*
  in accordance with upstream setup.{cfg,py}

Acked-by: Alex Brandt <alunduil@gentoo.org>
Package-Manager: Portage-2.3.12, Repoman-2.3.3

dev-python/botocore: allow recent Sphinx versions

Bump upper boundary of allowed version of Shpinx to 1.7 in new,
non-stabilized botocore ebuilds.

Dependency on Sphinx has versions range. Declaration of this range comes
from requirements-docs.txt in botocore sources, but that file hasn't
been updated since 2015. Latest Sphinx, version 1.6.5, builds botocore
docs successfully.

Sphinx versions range bump has been suggested to botocore maintainers,
but there's nothing preventing newer Sphinx from working on already
released botocore versions.

Link: https://github.com/boto/botocore/pull/1306
Acked-by: Alex Brandt <alunduil@gentoo.org>
Package-Manager: Portage-2.3.12, Repoman-2.3.3

dev-python/botocore: add 1.7.39 ebuild

This is currently the latest upstream release.

Ebuild copied from 1.5.90 with stable keywords downgraded to testing.

Acked-by: Alex Brandt <alunduil@gentoo.org>
Package-Manager: Portage-2.3.12, Repoman-2.3.3

dev-python/botocore: add 1.6.8 ebuild

This is the last release in 1.6.x series.

Ebuild copied from 1.5.90 with stable keywords downgraded to testing.

Acked-by: Alex Brandt <alunduil@gentoo.org>
Package-Manager: Portage-2.3.12, Repoman-2.3.3

dev-python/botocore: add 1.5.95 ebuild

This is the last release in 1.5.x series.

Ebuild copied from 1.5.90 with stable keywords downgraded to testing.

Acked-by: Alex Brandt <alunduil@gentoo.org>
Package-Manager: Portage-2.3.12, Repoman-2.3.3

app-office/texstudio: Bump to 2.12.6 and xdg-utils

Version bump to 2.12.6, we use now a fixed copy of the tar ball.
Had to migrate from 'fdo-mime' to 'xdg-utils' to make repoman happy.

Bug: https://bugs.gentoo.org/627062
Closes: https://bugs.gentoo.org/626130
Package-Manager: Portage-2.3.13, Repoman-2.3.4

sys-fs/zfs and friends: version bump to 0.7.3

Package-Manager: Portage-2.3.12, Repoman-2.3.3

sys-libs/timezone-data: Version bump

To be stabled in a few days if nothing bad happens.

Bug: https://bugs.gentoo.org/636464
Package-Manager: Portage-2.3.13, Repoman-2.3.4

media-libs/libsdl2: --enable-loadso on windows

For opengl to work on windows (at least via a mingw-w64 cross-compile)
--enable-loadso is required, as they dlopen opengl32.dll to get a
handle.

Bug: https://bugs.gentoo.org/636542
Signed-off-by: Marty E. Plummer <hanetzer@protonmail.com>
Closes: https://github.com/gentoo/gentoo/pull/4649

sys-apps/inxi: Drop old versions

Drop two of the old ebuilds

Package-Manager: Portage-2.3.13, Repoman-2.3.4

net-analyzer/pnp4nagios: use group permissions for writable directories.

The past few revisions have made some directories owned by the "nagios
user" so that the nagios/icinga daemon can write stuff there. Instead
of giving ownership of those directories to the nagios user, it's a
little bit more secure to give group-rwx permissions to the "nagios
group." This new revision does that instead.

Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-analyzer/pnp4nagios: drop USE=icinga2 in a new revision.

Now that pnp4nagios doesn't rely on the localstatedir of Nagios or
Icinga, the two implementations of Icinga are actually suitable for an
"or" dependency. We therefore do away with USE=icinga2, and let
USE=icinga mean "either icinga or icinga2."

Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-analyzer/pnp4nagios: tighten permissions on process_perfdata.cfg.

With USE=apache2, we used to set the group of process_perfdata.cfg to
"apache2", but that appears unnecessary. This revision doesn't do it.

Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-analyzer/pnp4nagios: fix the default stats directory.

The process_perfdata.cfg file refers to a STATS_DIR that is set to
"@localstatedir@/stats" at build-time. However, the build system
doesn't create that directory nor ensure that it is writable. This
latest revision passes --localstatedir to econf, and then creates the
associated directory with the desired permissions. The "bulk mode"
without NPCD now works out-of-the-box!

Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-analyzer/pnp4nagios: use consistent perfdata directories.

Past revisions have stored the RRDtool data and the process_perdata.pl
logs in (for example) /var/nagios or /var/icinga, depending on whether
or you had Nagios or Icinga installed. That's silly: the data format
doesn't change, so it makes more sense to choose one location (now:
/var/lib/pnp) and stick with it.

Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-analyzer/pnp4nagios: new revision to fix apache2 conf file.

The last few revisions have done,

  insinto "${APACHE_MODULES_CONFDIR}"

but the depend.apache eclass was removed in pnp4nagios-0.6.25-r3,
which means that the conf file wound up installed to ${ROOT}. The
new revision specifies the path explicitly without using the eclass
variable.

Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-analyzer/pnp4nagios: drop pointless rrdtool lower bound.

Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-analyzer/pnp4nagios: change "-DPHP5" to "-DPHP" in pkg_postinst().

The apache "define" changed a while ago from "PHP5" to simply "PHP".
This commit fixes the latest revision, in place, to output the correct
instructions.

Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-analyzer/pnp4nagios: new revision to fix insecure config permissions.

Previous revisions of pnp4nagios install /etc/pnp owned by the "nagios
user," and the npcd daemon also runs as that user. That configuration
is insecure: the unprivileged user can edit /etc/pnp/npcd.cfg, and
escalate his own privileges by setting "user = root". To avoid the
problem, we set INSTALL_OPTS="" while running "emake install". That
leaves all of /etc/pnp with the default (root:root) ownership.

Bug: https://github.com/lingej/pnp4nagios/issues/140
Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-analyzer/pnp4nagios: new revision with a better fix for CVE-2012-3457.

In CVE-2012-3457, it was reported that one particular file should not
be world-readable. To fix that, our ebuild made all of /etc/pnp
unreadable; that made other permissions issues difficult to work
around. This r2 sets o-rwx only on /etc/pnp/process_perfdata.cfg.

Bug: https://bugs.gentoo.org/430358
Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-analyzer/pnp4nagios: new revision to fix nagios/icinga "or" dependency.

Previous revisions of pnp4nagios have an "or" dependency on either
Nagios or Icinga,

  || ( net-analyzer/nagios-core net-analyzer/icinga ...

The way "or" dependencies work is that they are considered satisfied
if any elements of the associated group are installed. Thus the above
stanza allows Nagios and Icinga to be swapped out without rebuilding
pnp4nagios. That is incorrect, since later in the ebuild, nagios-
or icinga-specific paths are compiled into pnp4nagios.

The usual solution to that problem is to choose a default package that
satisfies the "one of these" dependency, but to allow the user to
specify one with a USE flag. This new revision adds three USE flags:
icinga, icinga2, and nagios. The "nagios" flag is enabled by default,
and builds pnp4nagios against net-analyzer/nagios. The other flags
build against the associated package.

In the process, the dependency on nagios-3.x was loosened to accept
nagios-4.x as well. The nagios-3.x series has been end-of-life'd, and
has multiple open security bugs.

Bug: https://bugs.gentoo.org/628086
Bug: https://bugs.gentoo.org/629380
Bug: https://bugs.gentoo.org/636234
Closes: https://bugs.gentoo.org/600424
Package-Manager: Portage-2.3.8, Repoman-2.3.3

net-analyzer/pnp4nagios: new version 0.6.26.

Package-Manager: Portage-2.3.8, Repoman-2.3.3

www-client/qutebrowser: remove old

Package-Manager: Portage-2.3.8, Repoman-2.3.3

www-client/qutebrowser: bump 1.0.3

Note that SRC_URI is a one-off due to a bad pack initially:
https://lists.schokokeks.org/pipermail/qutebrowser-announce/2017-November/000029.html

Package-Manager: Portage-2.3.8, Repoman-2.3.3

app-vim/pfsyntax: new ebuild.

Plugin to add Packet Filter syntax file highlighting to Vim.

Closes: https://bugs.gentoo.org/279943
Package-Manager: Portage-2.3.8, Repoman-2.3.3

sys-apps/inxi: Bump to 2.3.43 and add use flags

Version bump to 2.3.43
Support the global use flags bluetooth, hddtemp and opengl.

Package-Manager: Portage-2.3.13, Repoman-2.3.4

www-client/chromium: dev channel bump (64.0.3253.3)

Package-Manager: Portage-2.3.13_p1, Repoman-2.3.3_p81

app-backup/tsm: Retirement of proxied maintainer

Retirement of proxied maintainer as requested per bug.

Closes: https://bugs.gentoo.org/633162
Package-Manager: Portage-2.3.13, Repoman-2.3.4

app-crypt/libscrypt: stable 1.21 for sparc, bug #623388 (thanks to Rolf Eike Beer)

Package-Manager: Portage-2.3.13, Repoman-2.3.4
RepoMan-Options: --include-arches="sparc"

app-text/ps2pkm: stable 1.8_p20170524 for sparc, bug #624440 (thanks to Rolf Eike Beer)

Package-Manager: Portage-2.3.13, Repoman-2.3.4
RepoMan-Options: --include-arches="sparc"

dev-util/mingw64-runtime: version bump

Package-Manager: Portage-2.3.8, Repoman-2.3.3