Updates policy exception request for thermald #3673
Labels
No labels
document it
fast track
meeting
next release
nonresponsive maintainer
packager revocation
pending announcement
provenpackager
python 2 exception
self contained change
stalled
Status
Accepted
Status
Duplicate
Status
Insufficient data
Status
Invalid
Status
Rejected
system wide change
updates policy exception
vote-in-progress
No milestone
No project
No assignees
7 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fesco/tickets#3673
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I would like to request a one-time exception for
thermaldacross all Fedora branches.This is required to fix power management control on Intel-based machines that rely on
thermaldfor this functionality, as many newer laptops released in the last couple of years have poorly working or completely non-functional support at the moment.Ordinarily, this would be a regular, compatible update, but the need for the exception comes from the removal of the unmaintained Qt 5 application for monitoring
thermaldthat was shipped as a subpackage. It was deleted upstream, and I do not believe anyone used it, so I think nobody will notice.Additionally, I'm not yet the main admin for this package, but I expect that will change once #3672 is completed. I would like to use my provenpackager powers in the meantime to get this through as we have urgent requests through Fedora Ready that necessitate this update.
I believe the scope is very small and it should be very safe to allow this exception.
+1
+1
+1
+1
+1, but do you have a link to the issues? would be good to know what they are....
Unfortunately no, these were privately disclosed under NDA by a Fedora Ready vendor.
+1
+1
This is APPROVED (+7, 0, -0)
This still needs to be announced with the next meeting schedule, reopening to keep track.