Bug 1958657 - python-bravado-core is not installable on Fedora 32
Summary: python-bravado-core is not installable on Fedora 32
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: python-bravado-core
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aurelien Bompard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1958656
TreeView+ depends on / blocked
 
Reported: 2021-05-09 15:39 UTC by Davide Cavalca
Modified: 2021-05-25 17:08 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:08:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Davide Cavalca 2021-05-09 15:39:44 UTC
This fails with:

$ sudo dnf install python3-bravado-core
Last metadata expiration check: 0:06:36 ago on Sun May  9 08:29:13 2021.
Error: 
 Problem: conflicting requests
  - nothing provides python3.8dist(jsonpointer) > 1.13 needed by python3-bravado-core-5.17.0-1.fc32.1.noarch
(try to add '--skip-broken' to skip uninstallable packages)

And indeed:
$ dnf repoquery --provides python3-jsonpointer
python-jsonpointer = 1.10-19.fc32
python-jsonpointer = 1.13-1.fc32
python3-jsonpointer = 1.10-19.fc32
python3-jsonpointer = 1.13-1.fc32
python3.8dist(jsonpointer) = 1.10
python3.8dist(jsonpointer) = 1.13
python3dist(jsonpointer) = 1.10
python3dist(jsonpointer) = 1.13

So I think the dependency onto jsonpointer needs to be changed to ">=" instead of ">".

Comment 1 Davide Cavalca 2021-05-09 15:43:42 UTC
Put up https://src.fedoraproject.org/rpms/python-bravado-core/pull-request/2 for this

Comment 2 Ben Cotton 2021-05-25 17:08:07 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.