Bug 2350925 - mingw-libidn2-2.3.8 is available
Summary: mingw-libidn2-2.3.8 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mingw-libidn2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-03-09 00:55 UTC by Upstream Release Monitoring
Modified: 2025-03-18 03:01 UTC (History)
1 user (show)

Fixed In Version: mingw-libidn2-2.3.8-1.fc42 mingw-libidn2-2.3.8-1.fc41 mingw-libidn2-2.3.8-1.fc40 mingw-libidn2-2.3.8-1.el10_1 mingw-libidn2-2.3.8-1.el10_0 mingw-libidn2-2.3.8-1.el9 mingw-libidn2-2.3.8-1.el8
Clone Of:
Environment:
Last Closed: 2025-03-18 00:16:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2025-03-09 00:55:57 UTC
Releases retrieved: 2.3.8
Upstream release that is considered latest: 2.3.8
Current version/release in rawhide: 2.3.7-3.fc42
URL: https://www.gnu.org/software/libidn/#libidn2

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/5597/


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

Comment 1 Fedora Update System 2025-03-09 13:13:07 UTC
FEDORA-EPEL-2025-fe1e9d42a5 (mingw-libidn2-2.3.8-1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-fe1e9d42a5

Comment 2 Fedora Update System 2025-03-09 13:13:07 UTC
FEDORA-EPEL-2025-c21afc4df4 (mingw-libidn2-2.3.8-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c21afc4df4

Comment 3 Fedora Update System 2025-03-09 13:13:08 UTC
FEDORA-2025-ffd6bb5347 (mingw-libidn2-2.3.8-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-ffd6bb5347

Comment 4 Fedora Update System 2025-03-09 13:13:08 UTC
FEDORA-2025-51dfa8595c (mingw-libidn2-2.3.8-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-51dfa8595c

Comment 5 Fedora Update System 2025-03-09 13:13:09 UTC
FEDORA-2025-b851d61155 (mingw-libidn2-2.3.8-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-b851d61155

Comment 6 Fedora Update System 2025-03-09 16:45:41 UTC
FEDORA-EPEL-2025-732d53ca57 (mingw-libidn2-2.3.8-1.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-732d53ca57

Comment 7 Fedora Update System 2025-03-09 16:45:42 UTC
FEDORA-EPEL-2025-ade64b7f80 (mingw-libidn2-2.3.8-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-ade64b7f80

Comment 8 Fedora Update System 2025-03-10 01:56:35 UTC
FEDORA-2025-51dfa8595c has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-51dfa8595c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-51dfa8595c

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

Comment 9 Fedora Update System 2025-03-10 02:10:05 UTC
FEDORA-EPEL-2025-c21afc4df4 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c21afc4df4

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

Comment 10 Fedora Update System 2025-03-10 02:20:45 UTC
FEDORA-2025-ffd6bb5347 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-ffd6bb5347`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ffd6bb5347

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

Comment 11 Fedora Update System 2025-03-10 02:37:45 UTC
FEDORA-EPEL-2025-732d53ca57 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-732d53ca57

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

Comment 12 Fedora Update System 2025-03-10 02:46:29 UTC
FEDORA-EPEL-2025-ade64b7f80 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-ade64b7f80

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

Comment 13 Fedora Update System 2025-03-10 02:47:38 UTC
FEDORA-EPEL-2025-fe1e9d42a5 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-fe1e9d42a5

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

Comment 14 Fedora Update System 2025-03-10 02:48:28 UTC
FEDORA-2025-b851d61155 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-b851d61155`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-b851d61155

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

Comment 15 Fedora Update System 2025-03-18 00:16:03 UTC
FEDORA-2025-51dfa8595c (mingw-libidn2-2.3.8-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2025-03-18 01:11:17 UTC
FEDORA-2025-b851d61155 (mingw-libidn2-2.3.8-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2025-03-18 02:03:10 UTC
FEDORA-2025-ffd6bb5347 (mingw-libidn2-2.3.8-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 18 Fedora Update System 2025-03-18 02:24:40 UTC
FEDORA-EPEL-2025-ade64b7f80 (mingw-libidn2-2.3.8-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 19 Fedora Update System 2025-03-18 02:41:15 UTC
FEDORA-EPEL-2025-732d53ca57 (mingw-libidn2-2.3.8-1.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 20 Fedora Update System 2025-03-18 02:43:30 UTC
FEDORA-EPEL-2025-c21afc4df4 (mingw-libidn2-2.3.8-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 21 Fedora Update System 2025-03-18 03:01:13 UTC
FEDORA-EPEL-2025-fe1e9d42a5 (mingw-libidn2-2.3.8-1.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.


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