Bug 2299504

Summary:	libre-3.14.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	libre	Assignee:	Robert Scheck <redhat-bugzilla>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	redhat-bugzilla
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libre-3.14.0-1.fc41 libre-3.14.0-1.fc39 libre-3.14.0-1.el8 libre-3.14.0-1.el9 libre-3.14.0-1.fc40	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-07-23 21:27:32 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:

Description Upstream Release Monitoring 2024-07-23 17:57:47 UTC

Releases retrieved: 3.14.0
Upstream release that is considered latest: 3.14.0
Current version/release in rawhide: 3.13.0-2.fc41
URL: https://github.com/baresip/re

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


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

Comment 1 Fedora Update System 2024-07-23 21:23:37 UTC

FEDORA-2024-b82ff19320 (baresip-3.14.0-1.fc41 and libre-3.14.0-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-b82ff19320

Comment 2 Fedora Update System 2024-07-23 21:23:55 UTC

FEDORA-2024-139af963c2 (baresip-3.14.0-1.fc40 and libre-3.14.0-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-139af963c2

Comment 3 Fedora Update System 2024-07-23 21:24:16 UTC

FEDORA-2024-ae29b7d5e9 (baresip-3.14.0-1.fc39 and libre-3.14.0-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-ae29b7d5e9

Comment 4 Fedora Update System 2024-07-23 21:24:32 UTC

FEDORA-EPEL-2024-c9322d5e49 (baresip-3.14.0-1.el9 and libre-3.14.0-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-c9322d5e49

Comment 5 Fedora Update System 2024-07-23 21:24:49 UTC

FEDORA-EPEL-2024-33d22e33e5 (baresip-3.14.0-1.el8 and libre-3.14.0-1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-33d22e33e5

Comment 6 Fedora Update System 2024-07-23 21:27:32 UTC

FEDORA-2024-b82ff19320 (baresip-3.14.0-1.fc41 and libre-3.14.0-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 7 Fedora Update System 2024-07-24 01:11:50 UTC

FEDORA-EPEL-2024-33d22e33e5 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-2024-33d22e33e5

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

Comment 8 Fedora Update System 2024-07-24 03:52:01 UTC

FEDORA-2024-139af963c2 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-2024-139af963c2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-139af963c2

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

Comment 9 Fedora Update System 2024-07-24 04:03:44 UTC

FEDORA-EPEL-2024-c9322d5e49 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-2024-c9322d5e49

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

Comment 10 Fedora Update System 2024-07-24 04:18:11 UTC

FEDORA-2024-ae29b7d5e9 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ae29b7d5e9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ae29b7d5e9

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

Comment 11 Fedora Update System 2024-08-01 01:25:18 UTC

FEDORA-2024-ae29b7d5e9 (baresip-3.14.0-1.fc39 and libre-3.14.0-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2024-08-01 02:03:01 UTC

FEDORA-EPEL-2024-33d22e33e5 (baresip-3.14.0-1.el8 and libre-3.14.0-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.

Comment 13 Fedora Update System 2024-08-01 02:23:13 UTC

FEDORA-EPEL-2024-c9322d5e49 (baresip-3.14.0-1.el9 and libre-3.14.0-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 14 Fedora Update System 2024-08-01 02:52:37 UTC

FEDORA-2024-139af963c2 (baresip-3.14.0-1.fc40 and libre-3.14.0-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.