Rich Freeman posted on Wed, 20 May 2015 07:22:39 -0400 as excerpted: > So, you can't use 219 because it lacks fixes to some bugs. Systemd-220 > will probably fix those, and change who-knows-what else.
FWIW, systemd-220 is out upstream now, but there's not an in-tree gentoo ebuild for it yet (well, as of a bit under a day ago when I last updated). Here's a link to the article where I found out about it (it was on the lxer feed I subscribe to via claws-mail's feed-reader addon, but that was just a redirect to the below article, which I'm linking directly instead): http://www.itrunsonlinux.com/desktopos/systemd-v220-released/ The article pastes in the 220 changelog, apparently verbatim (minus the "contributors to this version" paragraph systemd normally puts at the end of each version's changelog). That should have the patch for my btrfs tmpfiles.d "v" vs. "d" bug, as it was committed before the 220 release, tho I've obviously not tested it yet. And while there's still no developer comment on the upstream IPv4 bug I'm CCed on, and as stated, no gentoo 220 yet, there's a patch from upstream for me to try on the gentoo IPv4 only bug I filed. Presumably, if it's from upstream, that should be in 220 as well, and if it works... Off for a 1 AM sync and some testing, now... if I don't get too sleepy to think straight first. Still 219 with those patches applied if 220 isn't in-tree yet when I sync. I'll post back when I have some results. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
