| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
|
|
| |
0.26 branch now contains all of my downstream backports.
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Generate the caches in compile phase since they are needed for tests.
Closes: https://bugs.gentoo.org/636490
|
| |
|
|
|
|
| |
The pypy executable has $ORIGIN-based rpath.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
RepoMan-Options: --include-arches="ia64"
|
|
|
|
| |
Closes: https://bugs.gentoo.org/629236
|
|
|
|
|
| |
Signed-off-by: Justin Lecher <jlec@gentoo.org>
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/show_bug.cgi?id=635222
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/show_bug.cgi?id=635222
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
|
| |
Reported-By: Robert Walker <bob.mt.wya@gmail.com>
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/show_bug.cgi?id=635222
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/show_bug.cgi?id=635928
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/show_bug.cgi?id=635222
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
|
|
| |
New dependency for www-apps/nanoc
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.4
|
|
|
|
|
|
| |
This is by agreement with current maintainer, alunduil.
Package-Manager: Portage-2.3.12, Repoman-2.3.3
|
|
|
|
|
|
| |
This is by agreement with current maintainer, alunduil.
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 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
|