{"push_id":916956230,"size":356,"distinct_size":356,"ref":"refs/heads/master","head":"9ba7f2cef52a93b9543816e27cff14bb9714ed60","before":"6a24501f6a568d6576c2564b1eb65be71fd71549","commits":[{"sha":"287a0de4ad4d2f7510f914a5f1be65430df8561c","author":{"email":"abfa460c174214ee9735cd8e667f1f70a0b261ec@axis.com","name":"Umut Tezduyar Lindskog"},"message":"downgrade warning if setting preset failed","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/287a0de4ad4d2f7510f914a5f1be65430df8561c"},{"sha":"1c36b4a73b876258fbe01fbe9bc9b750b7dcc9ce","author":{"email":"a3fde40985401a03951ec31e42775b52b1593ad5@ya.ru","name":"Evgeny Vereshchagin"},"message":"tests: add basic journal test","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/1c36b4a73b876258fbe01fbe9bc9b750b7dcc9ce"},{"sha":"6f526243e6a638c2ea7bbdd07b963f57e110d120","author":{"email":"a3fde40985401a03951ec31e42775b52b1593ad5@ya.ru","name":"Evgeny Vereshchagin"},"message":"journal: drop empty lines after level_prefix removing","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/6f526243e6a638c2ea7bbdd07b963f57e110d120"},{"sha":"45d39b4f81c6c92bfd9dd45c9d6ac0c68a477633","author":{"email":"a3fde40985401a03951ec31e42775b52b1593ad5@ya.ru","name":"Evgeny Vereshchagin"},"message":"tests: journal-stdout-stream: add cases for leading and trailing spaces","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/45d39b4f81c6c92bfd9dd45c9d6ac0c68a477633"},{"sha":"cfa1b98e832026b0fa5f1ca2f8f5f65bddf12a31","author":{"email":"a3fde40985401a03951ec31e42775b52b1593ad5@ya.ru","name":"Evgeny Vereshchagin"},"message":"journal: don't remove leading spaces","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/cfa1b98e832026b0fa5f1ca2f8f5f65bddf12a31"},{"sha":"000a996dc46c187f803b67b0b0d51ad4d0bc1658","author":{"email":"fbe8394d55af4c077cac5399865f6c6522347c3c@suse.com","name":"Franck Bui"},"message":"Introduce bus_unit_check_load_state() helper\n\nThis function is used to check that a previous unit load succeed and\nreturns 0 in this case.\n\nIn the case the load failed, the function setup a bus error\naccordingly and returns -errno.","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/000a996dc46c187f803b67b0b0d51ad4d0bc1658"},{"sha":"e9fd88f2e9a2effb7bcc1541a66263a5f97ce0a6","author":{"email":"fbe8394d55af4c077cac5399865f6c6522347c3c@suse.com","name":"Franck Bui"},"message":"core: allow 'SetUnitProperties()' to run on inactive units too\n\n'set-property' has been primarly designed to change some properties of\n*active* units.\n\nHowever it can easily work on inactive units as well. In that case\nchanges are only saved in a drop-in for futur uses and changes will be\neffective when unit will be started.\n\nActually it already works on inactive units but that was not\ndocumented and not fully supported. Indeed the inactive units had to\nbe known by the manager otherwise it was reported as not loaded:\n\n $ systemctl status my-test.service\n * my-test.service - My Testing Unit\n    Loaded: loaded (/etc/systemd/system/my-test.service; static; vendor preset: disabled)\n   Drop-In: /etc/systemd/system/my-test.service.d\n    Active: inactive (dead)\n\n $ systemctl set-property my-test.service MemoryLimit=1000000\n Failed to set unit properties on my-test.service: Unit my-test.service is not loaded.\n\n[ Note: that the unit load state reported by the 'status' command\n  might be confusing since it claimed the unit as loaded but\n  'set-property' reported the contrary. ]\n\nOne can possibily workaround this by making the unit a dependency of\nanother active unit so the manager will keep it around:\n\n $ systemctl add-wants multi-user.target my-test.service\n Created symlink from /etc/systemd/system/multi-user.target.wants/my-test.service to /etc/systemd/system/my-test.service.\n\n $ systemctl set-property my-test.service MemoryLimit=1000000\n\n $ systemctl status my-test.service\n * my-test.service - My Testing Unit\n    Loaded: loaded (/etc/systemd/system/my-test.service; enabled; vendor preset: disabled)\n   Drop-In: /etc/systemd/system/my-test.service.d\n            `-50-MemoryLimit.conf\n    Active: inactive (dead)\n\nThis patch simply forces 'SetUnitProperties()' to load the unit if\nit's not already the case.\n\nIt also documents the fact that 'set-property' can be used on inactive\nunits.","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/e9fd88f2e9a2effb7bcc1541a66263a5f97ce0a6"},{"sha":"b7cf9ac00afb10b5a2f63446babcf8d97111a636","author":{"email":"1a002461b1932d3892b64879e6e8987274fa7074@in.waw.pl","name":"Zbigniew Jędrzejewski-Szmek"},"message":"Rework file trigger scripts to fire at the right time\n\nThis turns out to be more complicated than it looked initially...\n%transfiletriggerun is called early, while %transfiletriggerin is\ncalled late, and neither satifisfies the requirement to call\ndaemon-reload after new unit files have been installed, but before\n%postun scripts in packages get to fire.\n\nIt seems that the only solution is to use %filetriggerun (which\nis called once per package) to do the reload, and keep state in\n/var/lib/rpm-state/systemd/ to avoid calling the reload multiple\ntimes.\n\nhttps://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Saving_state_between_scriptlets\nsays that /var/lib/rpm-state/systemd/ is the right dir.","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/b7cf9ac00afb10b5a2f63446babcf8d97111a636"},{"sha":"12dde791d519bc80d5cca4ab6f088763cd481015","author":{"email":"1a002461b1932d3892b64879e6e8987274fa7074@in.waw.pl","name":"Zbigniew Jędrzejewski-Szmek"},"message":"Convert file trigger scripts to lua\n\nAt least the %filetriggerpostun script can be invoked hundreds of\ntimes during an upgrade, so it makes sense to optimize it a bit.\n\nassert(exec(...)) is used because of https://bugzilla.redhat.com/show_bug.cgi?id=1094072.\n\nAdd -P (--priority) to have %filetriggerpostun run as early as\npossible (before any reload/stop actions), and %transfiletriggerin as\nlate as possible (after any enable/disable/preset actions).","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/12dde791d519bc80d5cca4ab6f088763cd481015"},{"sha":"9d06297e262966de71095debd1537fc223f940a3","author":{"email":"6a87ec066d10085110091ca2bb5009603cd7b6c7@redhat.com","name":"Harald Hoyer"},"message":"core: Do not bind a mount unit to a device, if it was from mountinfo\n\nIf a mount unit is bound to a device, systemd tries to umount the\nmount point, if it thinks the device has gone away.\n\nDue to the uevent queue and inotify of /proc/self/mountinfo being two\ndifferent sources, systemd can never get the ordering reliably correct.\n\nIt can happen, that in the uevent queue ADD,REMOVE,ADD is queued\nand an inotify of mountinfo (or libmount event) happend with the\ndevice in question.\n\nsystemd cannot know, at which point of time the mount happend in the\nADD,REMOVE,ADD sequence.\n\nThe real ordering might have been ADD,REMOVE,ADD,mount\nand systemd might think ADD,mount,REMOVE,ADD and would umount the\nmountpoint.\n\nA test script which triggered this behaviour is:\nrm -f test-efi-disk.img\ndd if=/dev/null of=test-efi-disk.img bs=1M seek=512 count=1\nparted --script test-efi-disk.img \\\n  \"mklabel gpt\" \\\n  \"mkpart ESP fat32 1MiB 511MiB\" \\\n  \"set 1 boot on\"\nLOOP=$(losetup --show -f -P test-efi-disk.img)\nudevadm settle\nmkfs.vfat -F32 ${LOOP}p1\nmkdir -p mnt\nmount ${LOOP}p1 mnt\n... <dostuffwith mnt>\n\nWithout the \"udevadm settle\" systemd unmounted mnt while the script was\noperating on mnt.\n\nOf course the question is, why there was a REMOVE in the first place,\nbut this is not part of this patch.","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/9d06297e262966de71095debd1537fc223f940a3"},{"sha":"cd949ee7348982d90fb8bdf4a37128928b82925f","author":{"email":"a3fde40985401a03951ec31e42775b52b1593ad5@ya.ru","name":"Evgeny Vereshchagin"},"message":"tests: don't run tests on incomplete setup","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/cd949ee7348982d90fb8bdf4a37128928b82925f"},{"sha":"6f5d79986a9c98b9cacc83f865fed957e4e6e4e6","author":{"email":"1a002461b1932d3892b64879e6e8987274fa7074@in.waw.pl","name":"Zbigniew Jędrzejewski-Szmek"},"message":"core: rename Random* to RandomizedDelay*\n\nThe name RandomSec is too generic: \"Sec\" just specifies the default\nunit type, and \"Random\" by itself is not enough. Rename to something\nthat should give the user general idea what the setting does without\nlooking at documentation.","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/6f5d79986a9c98b9cacc83f865fed957e4e6e4e6"},{"sha":"20cc0ac7a036babd3bc9ff87e41dc937a7942931","author":{"email":"1a002461b1932d3892b64879e6e8987274fa7074@in.waw.pl","name":"Zbigniew Jędrzejewski-Szmek"},"message":"man: remove repeated words in description of RandomizedDelay","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/20cc0ac7a036babd3bc9ff87e41dc937a7942931"},{"sha":"be808ea083fa07271116b4519c3c27fd20c5f077","author":{"email":"7c8224529a7c718e876cb2496c973509fde1e50e@jklm.no","name":"Tom Gundersen"},"message":"resolved: fallback to TCP if UDP fails\n\nThis is inspired by the logic in BIND [0], follow-up patches\nwill implement the reset of that scheme.\n\nIf we get a server error back, or if after several attempts we don't\nget a reply at all, we switch from UDP to TCP for the given\nserver for the current and all subsequent requests. However, if\nwe ever successfully received a reply over UDP, we never fall\nback to TCP, and once a grace-period has passed, we try to upgrade\nagain to using UDP. The grace-period starts off at five minutes\nafter the current feature level was verified and then grows\nexponentially to six hours. This is to mitigate problems due\nto temporary lack of network connectivity, but at the same time\navoid flooding the network with retries when the feature attempted\nfeature level genuinely does not work.\n\nNote that UDP is likely much more commonly supported than TCP,\nbut depending on the path between the client and the server, we\nmay have more luck with TCP in case something is wrong. We really\ndo prefer UDP though, as that is much more lightweight, that is\nwhy TCP is only the last resort.\n\n[0]: <https://kb.isc.org/article/AA-01219/0/Refinements-to-EDNS-fallback-behavior-can-cause-different-outcomes-in-Recursive-Servers.html>","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/be808ea083fa07271116b4519c3c27fd20c5f077"},{"sha":"4e0b8b17a7465653f4e7b819dad5f8e30d64c0c4","author":{"email":"7c8224529a7c718e876cb2496c973509fde1e50e@jklm.no","name":"Tom Gundersen"},"message":"resolved: degrade the feature level on explicit failure\n\nPreviously, we would only degrade on packet loss, but when adding EDNS0 support,\nwe also have to handle the case where the server replies with an explicit error.","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/4e0b8b17a7465653f4e7b819dad5f8e30d64c0c4"},{"sha":"dc913c9a1f243bca291d47b1a5d8e270c471d113","author":{"email":"7c8224529a7c718e876cb2496c973509fde1e50e@jklm.no","name":"Tom Gundersen"},"message":"resolved: rr - add OPT pseudo-rr support\n\nNeeded for EDNS0.","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/dc913c9a1f243bca291d47b1a5d8e270c471d113"},{"sha":"9c5e12a4314e7192e834e1b855e5e80111e636a6","author":{"email":"7c8224529a7c718e876cb2496c973509fde1e50e@jklm.no","name":"Tom Gundersen"},"message":"resolved: implement minimal EDNS0 support\n\nThis is a minimal implementation of RFC6891. Only default values\nare used, so in reality this will be a noop.\n\nEDNS0 support is dependent on the current server's feature level,\nso appending the OPT pseudo RR is done when the packet is emitted,\nrather than when it is assembled. To handle different feature\nlevels on retransmission, we strip off the OPT RR again after\nsending the packet.\n\nSimilarly, to how we fall back to TCP if UDP fails, we fall back\nto plain UDP if EDNS0 fails (but if EDNS0 ever succeeded we never\nfall back again, and after a timeout we will retry EDNS0).","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/9c5e12a4314e7192e834e1b855e5e80111e636a6"},{"sha":"7586f4d172dd9c3ccc3126fc47dca9e49adec132","author":{"email":"7c8224529a7c718e876cb2496c973509fde1e50e@jklm.no","name":"Tom Gundersen"},"message":"resolved: set the DNSSEC OK (DO) flag\n\nThis indicates that we can handle DNSSEC records (per RFC3225), even if\nall we do is silently drop them. This feature requires EDNS0 support.\n\nAs we do not yet support larger UDP packets, this feature increases the\nrisk of getting truncated packets.\n\nSimilarly to how we fall back to plain UDP if EDNS0 fails, we will fall\nback to plain EDNS0 if EDNS0+DO fails (with the same logic of remembering\nsuccess and retrying after a grace period after failure).","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/7586f4d172dd9c3ccc3126fc47dca9e49adec132"},{"sha":"d74fb368b18f0fbd9a4fe6f15691bbea7f3c4a01","author":{"email":"7c8224529a7c718e876cb2496c973509fde1e50e@jklm.no","name":"Tom Gundersen"},"message":"resolved: announce support for large UDP packets\n\nThis is often needed for proper DNSSEC support, and even to handle AAAA records\nwithout falling back to TCP.\n\nIf the path between the client and server is fully compliant, this should always\nwork, however, that is not the case, and overlarge packets will get mysteriously\nlost in some cases.\n\nFor that reason, we use a similar fallback mechanism as we do for palin EDNS0,\nEDNS0+DO, etc.:\n\nThe large UDP size feature is different from the other supported feature, as we\ncannot simply verify that it works based on receiving a reply (as the server\nwill usually send us much smaller packets than what we claim to support, so\nsimply receiving a reply does not mean much).\n\nFor that reason, we keep track of the largest UDP packet we ever received, as this\nis the smallest known good size (defaulting to the standard 512 bytes). If\nannouncing the default large size of 4096 fails (in the same way as the other\nfeatures), we fall back to the known good size. The same logic of retrying after a\ngrace-period applies.","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/d74fb368b18f0fbd9a4fe6f15691bbea7f3c4a01"},{"sha":"c9ff64f7256d86e521cccef9c9a077b278b7a946","author":{"email":"64b2b6d12bfe4baae7dad3d018f8cbf6b0e7a044@zonque.org","name":"Daniel Mack"},"message":"Merge pull request #2030 from evverx/dont-run-tests-on-incomplete-setup\n\ntests: don't run tests on incomplete setup","distinct":true,"url":"https://api.github.com/repos/martinpitt/systemd/commits/c9ff64f7256d86e521cccef9c9a077b278b7a946"}]}