> One possibility to handle the "conflict" might be making it an argument to
> --enable-bdb (eg --enable-bdb=readonly), which then skips the other variants.
> In that case it could technically be called "bdb" and avoid all the
> "configured to blabla, using blabla" warnings from backend
This will break a lot of packages in Fedora indeed.
For some of my packages I even rely on the behavior, such as here:
https://src.fedoraproject.org/rpms/python-xmlschema/blob/a11ca456b41794af7aec847af66f1e7974a698ff/f/python-xmlschema.spec#_59
--
You are receiving this because you are
Merged #996 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/996#event-2920694906___
Rpm-maint mailing list
Closed #995 via #996.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/995#event-2920694911___
Rpm-maint mailing list
I think the translation to rpm deps is not correct in some of these cases, but
the patch definitely fixes the original problem.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
It will definitely break something, probably a lot of things. OTOH, it would
probably make the things more consistent, e.g. it would avoid issues such as
[[1]], because one would need to delete the file instead of excluding it.
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=878863
--
You
Conan-Kudo approved this pull request.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/996#pullrequestreview-338018708___
Given `pip~=19.3`, this would generate:
```
python3.8dist(pip) >= 19.3
with
python3.8dist(pip) < 20
```
However, https://github.com/rpm-software-management/rpm/pull/996 fixes that.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Fixes https://github.com/rpm-software-management/rpm/issues/995
For this input: pyparsing=2.0.1,!=2.0.4,!=2.1.2,!=2.1.6
Instead of (invalid):
(python3.8dist(pyparsing) = 2.0.1 with
python3.8dist(pyparsing) 2.1.2 or python3.8dist(pyparsing) = 2.1.2.0
with
python3.8dist(pyparsing) 2.1.6 or
https://github.com/rpm-software-management/rpm/pull/996
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
My fix does this:
```
(python3.8dist(pyparsing) >= 2.0.1 with (python3.8dist(pyparsing) < 2.1.2 or
python3.8dist(pyparsing) >= 2.1.2.0) with (python3.8dist(pyparsing) < 2.0.4 or
python3.8dist(pyparsing) >= 2.0.4.0) with (python3.8dist(pyparsing) < 2.1.6 or
python3.8dist(pyparsing) >= 2.1.6.0))
I'm testing a fix. If it works, will submit a PR.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
We would need to put the or pairs into parenthesis, correct?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
The new version of Python requires generator fails with complicated expressions.
cc @gordonmessmer @Conan-Kudo @ignatenkobrain
Examples:
## Matplotlib
https://koschei.fedoraproject.org/package/python-matplotlib?collection=f32
Requirement: `pyparsing>=2.0.1,!=2.0.4,!=2.1.2,!=2.1.6`
```
14 matches
Mail list logo
