Fedora Account System
Red Hat Associate
Red Hat Customer
* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)? No * Does the service listen on a network socket for connections originating on a separate physical or virtual machine? No * Is the service non-persistent (i.e. run once at startup and exit)? No, it runs all the time * What is the exact name (or names) of the systemd unit files to be enabled? gpio-manager.service * Is this request for all Fedora deliverables or only for some Editions (list them)? All. There's a number of uses for this so if the gpio-manager package is installed it would be expected that it's running. Reproducible: Always
Looks reasonable, but before proceeding with this, please merge the patch to fix scriptlets: https://src.fedoraproject.org/rpms/libgpiod/pull-request/5.
That's merged and built for F-42+ if it wasn't noticed.
Sorry, indeed I missed that. I've been traveling. I'll get this together for F42+, though it missed the GA which was declared GO yesterday.
https://src.fedoraproject.org/rpms/fedora-release/pull-request/380 (Rawhide/F43) https://src.fedoraproject.org/rpms/fedora-release/pull-request/379 (F42)
FEDORA-2025-5117a28464 (fedora-release-42-26) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-5117a28464
FEDORA-2025-5117a28464 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-5117a28464` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5117a28464 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
> Sorry, indeed I missed that. I've been traveling. No stress, I know who to bother if it was urgent :) > I'll get this together for F42+, though it missed the GA which was declared > GO yesterday. Yup, I was aware, it's not a problem.
FEDORA-2025-5117a28464 (fedora-release-42-26) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.