Bug 2140263

Summary:	mimalloc-2.0.7 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	mimalloc	Assignee:	Vasiliy Glazov <vascom2>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	vascom2
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	mimalloc-2.0.7-1.fc37 mimalloc-2.0.7-1.fc36 mimalloc-2.0.7-1.fc35 mimalloc-2.0.7-1.el9 mimalloc-2.0.7-1.el8	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-23 01:16:09 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 2022-11-05 03:02:14 UTC

Releases retrieved: 1.7.7, 2.0.7
Upstream release that is considered latest: 2.0.7
Current version/release in rawhide: 2.0.6-2.fc37
URL: https://github.com/microsoft/mimalloc

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


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

Comment 1 Fedora Update System 2022-11-14 08:12:38 UTC

FEDORA-2022-7f0a665520 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7f0a665520

Comment 2 Fedora Update System 2022-11-14 08:12:39 UTC

FEDORA-2022-325bbeb422 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-325bbeb422

Comment 3 Fedora Update System 2022-11-14 08:12:40 UTC

FEDORA-EPEL-2022-5b2bb2d6e6 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-5b2bb2d6e6

Comment 4 Fedora Update System 2022-11-14 08:12:40 UTC

FEDORA-EPEL-2022-f3ef4605ad has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f3ef4605ad

Comment 5 Fedora Update System 2022-11-14 08:12:42 UTC

FEDORA-2022-c0208bcb63 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c0208bcb63

Comment 6 Fedora Update System 2022-11-15 02:22:49 UTC

FEDORA-2022-c0208bcb63 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 --refresh --advisory=FEDORA-2022-c0208bcb63`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c0208bcb63

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

Comment 7 Fedora Update System 2022-11-15 02:35:05 UTC

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

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

Comment 8 Fedora Update System 2022-11-15 02:36:23 UTC

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

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

Comment 9 Fedora Update System 2022-11-15 02:59:32 UTC

FEDORA-EPEL-2022-5b2bb2d6e6 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-2022-5b2bb2d6e6

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

Comment 10 Fedora Update System 2022-11-15 03:10:03 UTC

FEDORA-EPEL-2022-f3ef4605ad 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-2022-f3ef4605ad

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

Comment 11 Fedora Update System 2022-11-23 01:16:09 UTC

FEDORA-2022-325bbeb422 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2022-11-23 01:19:18 UTC

FEDORA-2022-7f0a665520 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2022-11-23 01:19:48 UTC

FEDORA-2022-c0208bcb63 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2022-11-23 01:44:59 UTC

FEDORA-EPEL-2022-5b2bb2d6e6 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2022-11-23 02:44:50 UTC

FEDORA-EPEL-2022-f3ef4605ad has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.