* 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
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
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
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
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
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
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
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
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
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
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
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
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