Bug 2009117

Summary: python-cryptography-35.0.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: python-cryptographyAssignee: Jeremy Cline <jeremy>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cheimes, jeremy, nick, npmccallum, terrycwk1994
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-cryptography-36.0.0-1.fc36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-23 10:06:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2007661, 2010061    
Bug Blocks:    

Description Upstream Release Monitoring 2021-09-30 02:06:40 UTC
Latest upstream release: 35.0.0
Current version/release in rawhide: 3.4.7-5.fc35
URL: http://cryptography.io/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/5532/

Comment 1 Upstream Release Monitoring 2021-09-30 02:06:49 UTC
Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-3qq4t8m9/python-cryptography.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1632960000\nerror: Bad file: ./cryptography-35.0.0-vendor.tar.bz2: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./cryptography-35.0.0-vendor.tar.bz2: No such file or directory\n'

Comment 2 Fedora Update System 2021-09-30 08:23:33 UTC
FEDORA-2021-e0dbdf0744 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2021-09-30 11:58:38 UTC
FEDORA-2021-122248d76a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-122248d76a

Comment 4 Fedora Update System 2021-10-01 01:38:57 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 5 Fedora Update System 2021-10-04 17:57:06 UTC
FEDORA-2021-122248d76a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-122248d76a

Comment 6 Fedora Update System 2021-10-05 15:16:02 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 7 Fedora Update System 2021-11-23 10:06:20 UTC
FEDORA-2021-b27ebacc47 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.