Bug 2181444 - pyOpenSSL-23.2.0 is available
Summary: pyOpenSSL-23.2.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pyOpenSSL
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2023-38325 2211237 2231274
TreeView+ depends on / blocked
 
Reported: 2023-03-24 06:34 UTC by Upstream Release Monitoring
Modified: 2023-08-12 04:43 UTC (History)
5 users (show)

Fixed In Version: pyOpenSSL-23.2.0-1.fc40 pyOpenSSL-23.2.0-1.fc39
Clone Of:
Environment:
Last Closed: 2023-08-11 20:03:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 23.1.0 (#2181444) (1.00 KB, patch)
2023-03-24 06:34 UTC, Upstream Release Monitoring
no flags Details | Diff
Update to 23.1.1 (#2181444) (1.00 KB, patch)
2023-03-28 03:11 UTC, Upstream Release Monitoring
no flags Details | Diff
Update to 23.2.0 (#2181444) (1019 bytes, patch)
2023-05-31 03:22 UTC, Upstream Release Monitoring
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Fedora Package Sources pyOpenSSL pull-request 10 0 None None None 2023-08-10 11:06:23 UTC
Red Hat Issue Tracker FC-793 0 None None None 2023-03-24 06:46:50 UTC

Description Upstream Release Monitoring 2023-03-24 06:34:35 UTC
Releases retrieved: 23.1.0
Upstream release that is considered latest: 23.1.0
Current version/release in rawhide: 23.0.0-1.fc39
URL: https://pyopenssl.readthedocs.org/

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://docs.fedoraproject.org/en-US/package-maintainers/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/5535/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/pyOpenSSL

Comment 1 Upstream Release Monitoring 2023-03-24 06:34:41 UTC
Created attachment 1953329 [details]
Update to 23.1.0 (#2181444)

Comment 2 Upstream Release Monitoring 2023-03-24 06:39:44 UTC
the-new-hotness/release-monitoring.org's scratch build of pyOpenSSL-23.1.0-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=99075395

Comment 3 Upstream Release Monitoring 2023-03-28 03:11:25 UTC
Releases retrieved: 23.1.1
Upstream release that is considered latest: 23.1.1
Current version/release in rawhide: 23.0.0-1.fc39
URL: https://pyopenssl.readthedocs.org/

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://docs.fedoraproject.org/en-US/package-maintainers/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/5535/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/pyOpenSSL

Comment 4 Upstream Release Monitoring 2023-03-28 03:11:29 UTC
Created attachment 1954059 [details]
Update to 23.1.1 (#2181444)

Comment 5 Upstream Release Monitoring 2023-03-28 03:15:05 UTC
the-new-hotness/release-monitoring.org's scratch build of pyOpenSSL-23.1.1-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=99216469

Comment 6 Upstream Release Monitoring 2023-05-31 03:22:19 UTC
Releases retrieved: 23.2.0
Upstream release that is considered latest: 23.2.0
Current version/release in rawhide: 23.1.1-1.fc39
URL: https://pyopenssl.readthedocs.org/

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://docs.fedoraproject.org/en-US/package-maintainers/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/5535/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/pyOpenSSL

Comment 7 Upstream Release Monitoring 2023-05-31 03:22:23 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-2r88ktlf/pyOpenSSL.spec']' returned non-zero exit status 1.

StdOut:
setting SOURCE_DATE_EPOCH=1685491200
error: Bad file: ./pyOpenSSL-23.2.0.tar.gz: No such file or directory

RPM build errors:
    Bad file: ./pyOpenSSL-23.2.0.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 229, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Comment 8 Upstream Release Monitoring 2023-05-31 03:22:25 UTC
Created attachment 1967994 [details]
Update to 23.2.0 (#2181444)

Comment 9 Christian Heimes 2023-08-10 08:13:22 UTC
python-cryptography update #2211237 is blocked. pyOpenSSL 23.1.0 has a version pin that makes it incompatible with python-cryptography 41.0. 23.2.0 requires 41.0.

Could you please update to 23.2.0 and add your build to my side tag f40-build-side-71372 ?

Comment 10 Fedora Update System 2023-08-11 18:24:01 UTC
FEDORA-2023-3c0f3ce86d has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3c0f3ce86d

Comment 11 Fedora Update System 2023-08-11 20:03:37 UTC
FEDORA-2023-3c0f3ce86d has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2023-08-11 20:14:47 UTC
FEDORA-2023-3823080dc8 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3823080dc8

Comment 13 Fedora Update System 2023-08-11 20:25:05 UTC
FEDORA-2023-6fc894ef59 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6fc894ef59

Comment 14 Fedora Update System 2023-08-11 22:06:37 UTC
FEDORA-2023-3823080dc8 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2023-08-12 04:43:38 UTC
FEDORA-2023-6fc894ef59 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-6fc894ef59`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-6fc894ef59

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


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