commit 03ccc3cbd869b898ea11e85dc69f4ca07da8ea8b Author: Cédric Krier <cedk@gentoo.org> AuthorDate: 2020-11-08 22:40:43 +0100 Commit: Cédric Krier <cedk@gentoo.org> CommitDate: 2020-11-08 22:41:09 +0100 dev-python/braintree: new ebuild Package-Manager: Portage-3.0.8, Repoman-3.0.2 Signed-off-by: Cédric Krier <cedk@gentoo.org> The ebuild is missing tests while upstream's repository clearly has tests. cedk is not on the Python team. The package doesn't mean quality requirements set by the Python team. Nevertheless, he has dumped the package on Python team.
Ping.
I do not understand what you are expecting from me?
Enabling tests in the package. Bumping it. Doing what maintainer is supposed to do.
But there is no test in the package.
And that large 'tests' directory is a misnomer, right?
There is no tests directory in the package.
You might have not looked at the upstream repo: https://github.com/braintree/braintree_python/blob/master/tests
I can not run tests that are not in the package. And I do not want to maintain my own packaging.
The GitHub repository provides archives that you can use.
Those archive are not stable. It is better to use the official packages distributed on PyPI.
No, they are not. Tests are very important. Also, please do not repeatedly close bugs where QA is involved.
(In reply to Cédric Krier from comment #10) > Those archive are not stable. It is better to use the official packages > distributed on PyPI. If you close this issue one more time, we will push for a ban from QA. Do not close QA issues.
(In reply to David Seifert from comment #12) > (In reply to Cédric Krier from comment #10) > > Those archive are not stable. It is better to use the official packages > > distributed on PyPI. > > If you close this issue one more time, we will push for a ban from QA. Do > not close QA issues. Please do not assign to me issue that I'm not allowed to close them.
(In reply to Cédric Krier from comment #13) > (In reply to David Seifert from comment #12) > > (In reply to Cédric Krier from comment #10) > > > Those archive are not stable. It is better to use the official packages > > > distributed on PyPI. > > > > If you close this issue one more time, we will push for a ban from QA. Do > > not close QA issues. > > Please do not assign to me issue that I'm not allowed to close them. Sure, I will just last-rite it, seeing it has no revdeps, and we generally have a policy of not packaging random python libraries.
Ping. What's the status here? Upstream has made another release.
Upstream confirmed that tests are not included because they can not pass with released code because it runs against the development API server: https://github.com/braintree/braintree_python/pull/136
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=46b6136c9a682e4d6a80b4b44f67cd1cf1f6eccd commit 46b6136c9a682e4d6a80b4b44f67cd1cf1f6eccd Author: Cédric Krier <cedk@gentoo.org> AuthorDate: 2021-09-05 22:02:00 +0000 Commit: Cédric Krier <cedk@gentoo.org> CommitDate: 2021-09-05 22:02:22 +0000 dev-python/braintree: version bumps Closes: https://bugs.gentoo.org/802567 Closes: https://bugs.gentoo.org/767256 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Cédric Krier <cedk@gentoo.org> dev-python/braintree/Manifest | 2 +- .../braintree/{braintree-4.9.0.ebuild => braintree-4.12.0.ebuild} | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
