* 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 * What is the exact name (or names) of the systemd unit files to be enabled? snapd.socket snapd.refresh.timer * Is this request for all Fedora deliverables or only for some Editions (list them)? For all of them
https://pagure.io/fedora-release/pull-request/56 https://pagure.io/fedora-release/pull-request/57 https://pagure.io/fedora-release/pull-request/58
So, what's the status here? Are we waiting for some body's approval?
(In reply to Zbigniew Jędrzejewski-Szmek from comment #2) > So, what's the status here? Are we waiting for some body's approval? I don't remember what approval we were waiting for, but looking at it again I think it's good to go. Very sorry for the delay.
I just remembered what the approval was; we were waiting for the snapd package review to actually be completed before we merged that. I think I referenced the wrong BZ in that comment to Pagure.
Ah, OK. And that is stalled. I guess this has to wait then.
The snapd package has been approved.
generic-release-25-1 fedora-release-25-1 fedora-repos-25-1 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-7b70ad9b8e
fedora-release-25-1, fedora-repos-25-1, generic-release-25-1 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-7b70ad9b8e
fedora-release-25-1, fedora-repos-25-1, generic-release-25-1 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.