{"push_id":1429440980,"size":12,"distinct_size":0,"ref":"refs/heads/master","head":"97506e85e2cf8c726939a872239698d5279a1cfc","before":"920ec31b5ffeb8695bef68e0dc082c0fc22965d3","commits":[{"sha":"2b656050b624312a472cc5df6870999745bd8ad5","author":{"name":"Zbigniew Jędrzejewski-Szmek","email":"77dc704bc81310147658033dcc63fa6fb3a4d704@in.waw.pl"},"message":"man: update the description of offline updates\n\n- use \"service\" instead of \"script\", because various offline updaters that we have\n  aren't really scripts, e.g. dnf-plugin-system-upgrade, packagekit-offline-update,\n fwupd-offline-update.\n- strongly recommend After=sysinit.target, Wants=sysinit.target\n- clarify a bit what should happen when multiple update services are started\n- replace links to the wiki with refs to the man page that replaced it.","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/2b656050b624312a472cc5df6870999745bd8ad5"},{"sha":"953bf4604f5ce02d1bd8abb09e82ea80e101c8a3","author":{"name":"Zbigniew Jędrzejewski-Szmek","email":"77dc704bc81310147658033dcc63fa6fb3a4d704@in.waw.pl"},"message":"units: add system-update-cleanup.service to guard against offline-update loops\n\nNote: the name is \"system-update-cleanup.service\" rather than\n\"system-update-done.service\", because it should not run normally, and also\nbecause there's already \"systemd-update-done.service\", and having them named\nso similarly would be confusing.\n\nIn https://bugzilla.redhat.com/show_bug.cgi?id=1395686 the system repeatedly\nentered system-update.target on boot. Because of a packaging issue, the tool\nthat created the /system-update symlink could be installed without the service\nunit that was supposed to perform the upgrade (and remove the symlink). In\nfact, if there are no units in system-update.target, and /system-update symlink\nis created, systemd always \"hangs\" in system-update.target. This is confusing\nfor users, because there's no feedback what is happening, and fixing this\nrequires starting an emergency shell somehow, and also knowing that the symlink\nmust be removed. We should be more resilient in this case, and remove the\nsymlink automatically ourselves, if there are no upgrade service to handle it.\n\nThis adds a service which is started after system-update.target is reached and\nthe symlink still exists. It nukes the symlink and reboots the machine. It\nshould subsequently boot into the default default.target.\n\nThis is a more general fix for\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1395686 (the packaging issue was\nalready fixed).","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/953bf4604f5ce02d1bd8abb09e82ea80e101c8a3"},{"sha":"71e529fcf18c00e4dd51fb46f7f289dc5eb11fbd","author":{"name":"Jouke Witteveen","email":"3d504b3bcc89ccb789b82672c752bf4b42c66b0d@gmail.com"},"message":"service: only fail notify services on empty cgroup during start\n\nWe stay in the SERVICE_START while no READY=1 notification message has\nbeen received. When we are in the SERVICE_START_POST state, we have\nalready received a ready notification. Hence we should not fail when the\ncgroup becomes empty in that state.","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/71e529fcf18c00e4dd51fb46f7f289dc5eb11fbd"},{"sha":"3c9512c71d49d42513755cfa4329275c0360f397","author":{"name":"Jouke Witteveen","email":"3d504b3bcc89ccb789b82672c752bf4b42c66b0d@gmail.com"},"message":"service: prevent registering control pids as the main pid\n\nWe assume a process can be only one of the two in service_sigchld_event.","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/3c9512c71d49d42513755cfa4329275c0360f397"},{"sha":"664e7984f8a96c1962961fcc1ebe6bd4a0c58c5f","author":{"name":"Lennart Poettering","email":"2baa8fca698523d252842633f852b9ab3cfeddbc@poettering.net"},"message":"Merge pull request #4763 from keszybz/offline-update-loop\n\nA fix for offline update loop","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/664e7984f8a96c1962961fcc1ebe6bd4a0c58c5f"},{"sha":"e8e42b31c5a950a7b43d64f4a531ec59750e823e","author":{"name":"Stefan Berger","email":"f054f8a086e76b8d7078542ccea10b031321dea3@us.ibm.com"},"message":"ima: Write the policy filename into IMA's sysfs policy file (#4766)\n\nIMA validates file signatures based on the security.ima xattr. As of\r\nLinux-4.7, instead of copying the IMA policy into the securityfs policy,\r\nthe IMA policy pathname can be written, allowing the IMA policy file\r\nsignature to be validated.\r\n\r\nThis patch modifies the existing code to first attempt to write the\r\npathname, but on failure falls back to copying the IMA policy contents.","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/e8e42b31c5a950a7b43d64f4a531ec59750e823e"},{"sha":"a9d2d40dbabd241354f62b57f407fb23c20d7860","author":{"name":"Gabriel Rauter","email":"8001a6b936056384c5dc7088ee6f7ccc705fa20d@gmail.com"},"message":"networkctl: install zsh completion from #3062 (#4767)\n\nzsh autocompletion provided by #3062 will be installed when networkd is\r\nenabled.","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/a9d2d40dbabd241354f62b57f407fb23c20d7860"},{"sha":"e7330dfe14b1965fe8a2e25df248f45d46cfb26d","author":{"name":"Dongsu Park","email":"05027982863758b025583251fb48dd2be12881c1@endocode.com"},"message":"cgroup: support prefix \"-\" in cgroups whitelisting entries (#4687)\n\nSo far systemd-nspawn container has been creating files under\r\n/run/systemd/inaccessible, no matter whether it's running in user\r\nnamespace or not. That's fine for regular files, dirs, socks, fifos.\r\nHowever, it's not for block and character devices, because kernel\r\ndoesn't allow them to be created under user namespace. It results\r\nin warnings at booting like that:\r\n\r\n====\r\n  Couldn't stat device /run/systemd/inaccessible/chr\r\n  Couldn't stat device /run/systemd/inaccessible/blk\r\n====\r\n\r\nThus we need to have the cgroups whitelisting handler to silently ignore\r\na file, when the device path is prefixed with \"-\". That's exactly the\r\nsame convention used in directives like ReadOnlyPaths=. Also insert the\r\nprefix \"-\" to inaccessible entries.","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/e7330dfe14b1965fe8a2e25df248f45d46cfb26d"},{"sha":"7ed0a4c537d405544d1dd772ed08ea20143cf2d6","author":{"name":"Jouke Witteveen","email":"3d504b3bcc89ccb789b82672c752bf4b42c66b0d@gmail.com"},"message":"bus-util: add protocol error type explanation","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/7ed0a4c537d405544d1dd772ed08ea20143cf2d6"},{"sha":"8e458bfe4e2aa36c939db62561b2a59206d78577","author":{"name":"Jouke Witteveen","email":"3d504b3bcc89ccb789b82672c752bf4b42c66b0d@gmail.com"},"message":"NEWS: mention more aggressive failing of notify services","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/8e458bfe4e2aa36c939db62561b2a59206d78577"},{"sha":"6375bd2007412b401e8aa528d70d5866057f6fe5","author":{"name":"Jouke Witteveen","email":"3d504b3bcc89ccb789b82672c752bf4b42c66b0d@gmail.com"},"message":"service: new NotifyAccess= value for control processes (#4212)\n\nSetting NotifyAccess=exec allows notifications coming directly from any\ncontrol process.","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/6375bd2007412b401e8aa528d70d5866057f6fe5"},{"sha":"97506e85e2cf8c726939a872239698d5279a1cfc","author":{"name":"Evgeny Vereshchagin","email":"4a767b4b963a80bc9d1bd30cc2caffd18c892fb5@ya.ru"},"message":"Merge pull request #4745 from joukewitteveen/notify\n\nImprovements for notify services (including #4212)","distinct":false,"url":"https://api.github.com/repos/ssahani/systemd/commits/97506e85e2cf8c726939a872239698d5279a1cfc"}]}
{"actor":{"display_login":"ssahani"}}