Overview
Request 841500 accepted
- Upper limit pytest 6.1 -- gh#bitprophet/pytest-relaxed#12
Resolve Staging:H blocker
- Created by bnavigator
- In state accepted
Loading...
Request History
bnavigator created request
- Upper limit pytest 6.1 -- gh#bitprophet/pytest-relaxed#12
Resolve Staging:H blocker
mimi_vx accepted request
We should probably rather work on killing this pkg.
All depending packages come from the same author, who has not been responsive in this regard. https://github.com/paramiko/paramiko/pull/1665
Except for paramiko, I only see the possibility to completely disable the unit tests (which is the case for 1 of 3 packages already)
BuildRequires
“Banned from Gentoo”? It sounds like we really should get rid of it. BTW, https://wiki.gentoo.org/wiki/Project:Python/Tests seems generally rather sensible set of rules.
Yeah, could we similarly patch out pytest-relaxed from Fabric, invocations, and invoke, without disabling tests completely?
Paramiko was apparently easy because it uses the standard
test_*.py
anddef test*
naming convention. The other packages don't. If you can find a way to discover all the right tests and remove the used pytest-relaxed API, okay. But I fear it won't be as easy. And Staging:H has been blocked for way too long.BTW, Gentoo users build everything from scratch using their real system. So an installed pytest-relaxed affects all other packages, even if they don't require it. We don't suffer from this as much as we have the isolated build environment.
So, what's the verdict?
Now that this has been accepted: https://build.opensuse.org/request/show/842108