In agreement with him, honouring his regular and timely version updates
to this package.
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Andrey Utkin <andrey_utkin@gentoo.org>
Cloned from 9999 ebuild verbatim.
Version caps on few deps, which have been added by Whissi in
botocore-1.12.251.ebuild, are thus abandoned, which has been agreed with
Whissi.
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Andrey Utkin <andrey_utkin@gentoo.org>
To avoid extra diff hunk after cloning into release ebuilds.
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Andrey Utkin <andrey_utkin@gentoo.org>
Since 1.11.0 botocore depends on `urllib3`. Before, it used bundled
patched versions of `requests` and `urllib3`.
Package-Manager: Portage-2.3.48, Repoman-2.3.10
Drop version range requirements, as all requirements are satisfied by
all ebuilds currently present in Gentoo tree.
The ranges originally come from upstream's requirements.txt and
setup.{cfg,py}, but upstream developers don't tend to update these
ranges, which makes them irrelevant and even harmful to Gentoo (e.g. by
blocking removal of outdated version of dependencies).
Package-Manager: Portage-2.3.36, Repoman-2.3.9
botocore is released very often - 1.8.0 to 1.8.20 in one month. So it
makes sense to allow users to opt in to being up to date, free from
ebuild bumps delay. Git master branch is always at latest release, so
should be reasonably safe to use.
Package-Manager: Portage-2.3.17, Repoman-2.3.6
Functional tests suite, recently added to src_test phase, ended up using
library files already installed, and not what is to be installed.
This is handled now by passing custom PYTHONPATH, and patching tests
suite to not discard custom PYTHONPATH when launching child processes.
"nosetests" invocation for unit and functional test suites was split
into two as it doesn't work correctly when given two directory paths. It
looks like PYTHONPATH is not properly passed in that case. The reason is
unknown.
Fixes: e1fabdbdb95d ("dev-python/botocore: run also functional tests")
Bug: https://bugs.gentoo.org/640726
Package-Manager: Portage-2.3.17, Repoman-2.3.6
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
