Bug 2242749

Summary:	m1n1-1.4.2 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	m1n1	Assignee:	Davide Cavalca <davide>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	asahi-sig, awilliam, davide, michel, ngompa13
Target Milestone:	---	Keywords:	FutureFeature, Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	AcceptedFreezeException
Fixed In Version:	m1n1-1.4.2-1.fc40 m1n1-1.4.2-1.fc38 m1n1-1.4.2-1.fc39	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-10-10 22:16:07 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:
Bug Blocks:	2143447

Description Upstream Release Monitoring 2023-10-08 17:42:36 UTC

Releases retrieved: 1.4.1, 1.4.2
Upstream release that is considered latest: 1.4.2
Current version/release in rawhide: 1.4.1-1.fc40
URL: https://github.com/AsahiLinux/m1n1

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


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

Comment 1 Fedora Update System 2023-10-09 04:33:32 UTC

FEDORA-2023-901a02301c has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-901a02301c

Comment 2 Fedora Update System 2023-10-09 04:34:11 UTC

FEDORA-2023-901a02301c has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2023-10-09 04:50:01 UTC

FEDORA-2023-2d8db7f5f6 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-2d8db7f5f6

Comment 4 Fedora Update System 2023-10-09 05:02:06 UTC

FEDORA-2023-d214105fcd has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d214105fcd

Comment 5 Fedora Update System 2023-10-10 01:36:19 UTC

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

Comment 6 Fedora Update System 2023-10-10 01:48:10 UTC

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

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

Comment 7 Fedora Blocker Bugs Application 2023-10-10 15:54:42 UTC

Proposed as a Freeze Exception for 39-final by Fedora user dcavalca using the blocker tracking app because:

 This m1n1 update fixes several issues and is required for M2 device support and to enable webcam support on Apple Silicon devices

Comment 8 Adam Williamson 2023-10-10 21:36:31 UTC

+3 in https://pagure.io/fedora-qa/blocker-review/issue/1401 , marking accepted.

Comment 9 Fedora Update System 2023-10-10 22:16:07 UTC

FEDORA-2023-2d8db7f5f6 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.