In systemd: backport of bunch of patches from the v242 release. Most important:
In grub2:
No need to log out or reboot.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2019-616045ca76Please login to add feedback.
| 0 | 0 | Test Case Services start |
| 0 | 0 | Test Case base service manipulation |
| 0 | 1 | Test Case base services start |
| 0 | 0 | Test Case base shutdown/reboot |
| 0 | 0 | Test Case User:Tablepc/Draft testcase reboot |
This update has been submitted for testing by zbyszek.
systemdalways enables previously manually disabled systemd-resolved and systemd-networkd services.This update has been pushed to testing.
@bluepencil: those two issues don't seem related in any way to this upgrade. Please file a bug for the selinux issue.
I can reproduce the enablement issue locally. I'll investigate.
Works
works for me
This update has been submitted for batched by bodhi.
@zbyszek
Thanks for future investigation. I understand that preventing systemd-resolved more related to selinux issues, but somehow even so related 'cause appearing after this update :)
I can no longer reproduce the memory leak from #1685286 with this build. :)
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
@bluepencil: https://github.com/systemd/systemd/pull/12164 for the enablement thing.
Yes, it's really good that things about systemd scripting no longer at an impasse.
To clarify a bit about attribution of issues to a specific updates. I think, that it would be more productive to take care about informing other maintainers when their packages need upgrade too. Otherwise all the work done makes no sense.
*Nothing personal here. It's just often not easy for ordinary users to figure out what exactly requires correction and how.
error: ../../grub-core/fs/fat.c:447:not a FAT filesystem