Bug 2010061 - F35FailsToInstall: python3-jwt+crypto
Summary: F35FailsToInstall: python3-jwt+crypto
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-jwt
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Infrastructure SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F35FinalFreezeException 2009117
TreeView+ depends on / blocked
 
Reported: 2021-10-03 11:30 UTC by Otto Liljalaakso
Modified: 2021-10-06 19:58 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-06 19:58:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Otto Liljalaakso 2021-10-03 11:30:35 UTC
Description of problem:

Package python3-jwt+crypto fails to install on Fedora Linux 35:

  $ sudo dnf install python3-jwt+crypto
  Last metadata expiration check: 0:00:48 ago on Sun Oct  3 14:21:31 2021.
  Error: 
   Problem: conflicting requests
    - nothing provides (python3.10dist(cryptography) < 4 with python3.10dist(cryptography) >= 3.3.1) needed by python3-jwt+crypto-2.1.0-2.fc35.noarch
  (try to add '--skip-broken' to skip uninstallable packages)

Fedora 35 stable seems to have compatible python3-cryptography-3.4.7,
but testing is already at 35.0.0.

Version-Release number of selected component (if applicable):
2.1.0-2.fc35

How reproducible:
Always

Steps to Reproduce:
1. Run: $ sudo dnf install python3-jwt+crypto

Actual results:
Error as given in description

Expected results:
Compatible provide for python3.10dist(cryptography) is found,
installation succeeds.

Additional info:

Comment 1 Otto Liljalaakso 2021-10-03 11:33:30 UTC
Bodhi already has negative karma
and related discussion
for the python-cryptography update that caused this:

https://bodhi.fedoraproject.org/updates/FEDORA-2021-122248d76a

Comment 2 Kevin Fenzi 2021-10-03 21:28:58 UTC
I've pushed a rawhide build with the upper requirement removed for now. 

This can be merged into f35, built and attached to the update. 

Let me know if you I should do that.

Comment 3 Otto Liljalaakso 2021-10-04 06:31:40 UTC
Thanks!
I can confirm that the new rpms available in Koji
fix the issue I had.

Regarding the question of building and attaching to the update,
I will let the update owners make the decisions there.

Comment 4 Fedora Update System 2021-10-04 17:56:45 UTC
FEDORA-2021-122248d76a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-122248d76a

Comment 5 Fedora Update System 2021-10-04 17:57:09 UTC
FEDORA-2021-122248d76a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-122248d76a

Comment 6 Fedora Blocker Bugs Application 2021-10-05 08:44:19 UTC
Proposed as a Blocker for 35-final by Fedora user zbyszek using the blocker tracking app because:

 Break upgrades, violating:
> For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from a fully updated, clean default installation of each of the last two stable Fedora releases with that package set installed.

Comment 7 Fedora Update System 2021-10-05 15:16:04 UTC
FEDORA-2021-122248d76a has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-122248d76a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-122248d76a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Kamil Páral 2021-10-06 06:49:36 UTC
Switching to a freeze exception request per discussion in https://pagure.io/fedora-qa/blocker-review/issue/496

Comment 9 Geraldo Simião 2021-10-06 14:25:41 UTC
well, this update has been obsoleted at 05/10/21, (https://bodhi.fedoraproject.org/updates/FEDORA-2021-122248d76a)

Comment 10 Otto Liljalaakso 2021-10-06 19:58:55 UTC
Yes, obsoleting the update has fixed that.
Closing the issue now.


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