Re: [systemd-devel] systemd prerelease 242-rc2
fwiw, in Debian we added https://salsa.debian.org/systemd-team/systemd/commit/b274b4ad5a4ba543c8c013fb71dacf2467030ddc Am Do., 4. Apr. 2019 um 21:39 Uhr schrieb Mike Gilbert : > > On Thu, Apr 4, 2019 at 3:38 PM Mike Gilbert wrote: > > > > On Thu, Apr 4, 2019 at 11:23 AM Lennart Poettering > > wrote: > > > > > > On Do, 04.04.19 10:06, Mike Gilbert (flop...@gentoo.org) wrote: > > > > > > > I pushed this out to our unstable testers yesterday, and received a > > > > couple bug reports this morning. I have requested that they be > > > > forwarded upstream, but wanted to point them out in case that doesn't > > > > happen promptly. > > > > > > > > https://bugs.gentoo.org/682492 > > > > sys-apps/systemd-242_rc2 boot fails: sd-passwd takes no arguments > > > > > > Most likely fixed by > > > https://github.com/systemd/systemd/commit/65e5d6934ec85febb6eb64e18ce829ddc9dee497 > > > already. > > > > > > > https://bugs.gentoo.org/682488 > > > > sys-apps/systemd-242_rc2: systemd-timesyncd.service: Failed to set up > > > > special execution directory in /var/lib: Not a directory > > > > > > Smells like a belated result of us dropping DynamicUser=1 from > > > timesyncd. > > > > > > Right now, systemd will automatically migrate the state directory for > > > services that have DynamicUser=0 to a newer version that has > > > DynamicUser=1, but not back. We should probably add that too. > > > > > > Anyway, it was systemd v240 where we dropped the DynamicUser=1 thing > > > already, hence not precisely a v242 regression... > > > > These users probably upgraded from v239 to v241 to v242-rc2 over the > > course of a few months. We never shipped v240. > > Sorry, I am mistaken; we did ship v240, but never marked it "stable". > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd prerelease 242-rc2
On Thu, Apr 4, 2019 at 3:38 PM Mike Gilbert wrote: > > On Thu, Apr 4, 2019 at 11:23 AM Lennart Poettering > wrote: > > > > On Do, 04.04.19 10:06, Mike Gilbert (flop...@gentoo.org) wrote: > > > > > I pushed this out to our unstable testers yesterday, and received a > > > couple bug reports this morning. I have requested that they be > > > forwarded upstream, but wanted to point them out in case that doesn't > > > happen promptly. > > > > > > https://bugs.gentoo.org/682492 > > > sys-apps/systemd-242_rc2 boot fails: sd-passwd takes no arguments > > > > Most likely fixed by > > https://github.com/systemd/systemd/commit/65e5d6934ec85febb6eb64e18ce829ddc9dee497 > > already. > > > > > https://bugs.gentoo.org/682488 > > > sys-apps/systemd-242_rc2: systemd-timesyncd.service: Failed to set up > > > special execution directory in /var/lib: Not a directory > > > > Smells like a belated result of us dropping DynamicUser=1 from > > timesyncd. > > > > Right now, systemd will automatically migrate the state directory for > > services that have DynamicUser=0 to a newer version that has > > DynamicUser=1, but not back. We should probably add that too. > > > > Anyway, it was systemd v240 where we dropped the DynamicUser=1 thing > > already, hence not precisely a v242 regression... > > These users probably upgraded from v239 to v241 to v242-rc2 over the > course of a few months. We never shipped v240. Sorry, I am mistaken; we did ship v240, but never marked it "stable". ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd prerelease 242-rc2
On Thu, Apr 4, 2019 at 11:23 AM Lennart Poettering wrote: > > On Do, 04.04.19 10:06, Mike Gilbert (flop...@gentoo.org) wrote: > > > I pushed this out to our unstable testers yesterday, and received a > > couple bug reports this morning. I have requested that they be > > forwarded upstream, but wanted to point them out in case that doesn't > > happen promptly. > > > > https://bugs.gentoo.org/682492 > > sys-apps/systemd-242_rc2 boot fails: sd-passwd takes no arguments > > Most likely fixed by > https://github.com/systemd/systemd/commit/65e5d6934ec85febb6eb64e18ce829ddc9dee497 > already. > > > https://bugs.gentoo.org/682488 > > sys-apps/systemd-242_rc2: systemd-timesyncd.service: Failed to set up > > special execution directory in /var/lib: Not a directory > > Smells like a belated result of us dropping DynamicUser=1 from > timesyncd. > > Right now, systemd will automatically migrate the state directory for > services that have DynamicUser=0 to a newer version that has > DynamicUser=1, but not back. We should probably add that too. > > Anyway, it was systemd v240 where we dropped the DynamicUser=1 thing > already, hence not precisely a v242 regression... These users probably upgraded from v239 to v241 to v242-rc2 over the course of a few months. We never shipped v240. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd prerelease 242-rc2
On Do, 04.04.19 10:06, Mike Gilbert (flop...@gentoo.org) wrote: > I pushed this out to our unstable testers yesterday, and received a > couple bug reports this morning. I have requested that they be > forwarded upstream, but wanted to point them out in case that doesn't > happen promptly. > > https://bugs.gentoo.org/682492 > sys-apps/systemd-242_rc2 boot fails: sd-passwd takes no arguments Most likely fixed by https://github.com/systemd/systemd/commit/65e5d6934ec85febb6eb64e18ce829ddc9dee497 already. > https://bugs.gentoo.org/682488 > sys-apps/systemd-242_rc2: systemd-timesyncd.service: Failed to set up > special execution directory in /var/lib: Not a directory Smells like a belated result of us dropping DynamicUser=1 from timesyncd. Right now, systemd will automatically migrate the state directory for services that have DynamicUser=0 to a newer version that has DynamicUser=1, but not back. We should probably add that too. Anyway, it was systemd v240 where we dropped the DynamicUser=1 thing already, hence not precisely a v242 regression... Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd prerelease 242-rc2
Latter issue may be: https://github.com/systemd/systemd/issues/12131 -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/ On Thu, Apr 4, 2019, 9:07 AM Mike Gilbert wrote: > I pushed this out to our unstable testers yesterday, and received a > couple bug reports this morning. I have requested that they be > forwarded upstream, but wanted to point them out in case that doesn't > happen promptly. > > https://bugs.gentoo.org/682492 > sys-apps/systemd-242_rc2 boot fails: sd-passwd takes no arguments > > https://bugs.gentoo.org/682488 > sys-apps/systemd-242_rc2: systemd-timesyncd.service: Failed to set up > special execution directory in /var/lib: Not a directory > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd prerelease 242-rc2
I pushed this out to our unstable testers yesterday, and received a couple bug reports this morning. I have requested that they be forwarded upstream, but wanted to point them out in case that doesn't happen promptly. https://bugs.gentoo.org/682492 sys-apps/systemd-242_rc2 boot fails: sd-passwd takes no arguments https://bugs.gentoo.org/682488 sys-apps/systemd-242_rc2: systemd-timesyncd.service: Failed to set up special execution directory in /var/lib: Not a directory ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd prerelease 242-rc2
A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the tarball here: https://github.com/systemd/systemd/archive/v242-rc2.tar.gz NOTE: This is ☠️ pre-release☠️ software. Do not run this on production systems, but please test this and report any issues you find to GitHub: https://github.com/systemd/systemd/issues/new?template=Bug_report.md Changes since the previous release: * In .link files, MACAddressPolicy=persistent (the default) is changed to cover more devices. For devices like bridges, tun, tap, bond, and similar interfaces that do not have other identifying information, the interface name is used as the basis for persistent seed for MAC and IPv4LL addresses. The way that devices that were handled previously is not changed, and this change is about covering more devices then previously by the "persistent" policy. MACAddressPolicy=random may be used to force randomized MACs and IPv4LL addresses for a device if desired. Hint: the log output from udev (at debug level) was enhanced to clarify what policy is followed and which attributes are used. `SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link /sys/class/net/` may be used to view this. * The .device units generated by systemd-fstab-generator and other generators do not automatically pull in the corresponding .mount unit as a Wants= dependency. This means that simply plugging in the device will not cause the mount unit to be started automatically. But please note that the mount unit may be started for other reasons, in particular if it is part of local-fs.target, and any unit which (transitively) depends on local-fs.target is started. * networkctl list/status/lldp now accept globbing wildcards for network interface names to match against all existing interfaces. * The $PIDFILE environment variable is set to point the absolute path configured with PIDFile= for processes of that service. * The fallback DNS server list was augmented with Cloudflare public DNS servers. Use `-Ddns-servers=` to set a different fallback. * A new special target usb-gadget.target will be started automatically when a USB Device Controller is detected (which means that the system is a USB peripheral). * A new unit setting CPUQuotaPeriodSec= assigns the time period relatively to which the CPU time quota specified by CPUQuota= is measured. * A new unit setting ProtectHostname= may be used to prevent services from modifying hostname information (even if they otherwise would have privileges to do so). * A new unit setting NetworkNamespacePath= may be used to specify a namespace for service or socket units through a path referring to a Linux network namespace pseudo-file. * The PrivateNetwork= setting and JoinsNamespaceOf= dependencies now have an effect on .socket units: when used the listening socket is created within the configured network namespace instead of the host namespace. * ExecStart= command lines in unit files may now be prefixed with ':' in which case environment variable substitution is disabled. (Supported for the other ExecXYZ= settings, too.) * .timer units gained two new boolean settings OnClockChange= and OnTimezoneChange= which may be used to also trigger a unit when the system clock is changed or the local timezone is modified. systemd-run has been updated to make these options easily accessible from the command line for transient timers. * Two new conditions for units have been added: ConditionMemory= may be used to conditionalize a unit based on installed system RAM. ConditionCPUs= may be used to conditionalize a unit based on install CPU cores. * The @default system call filter group understood by SystemCallFilter= has been updated to include the new rseq() system call introduced in kernel 4.15. * "systemctl start" (and related commands) learnt a new --show-transaction option. If specified brief information about all jobs queued because of the requested operation is shown. * systemd-networkd recognizes a new operation state 'enslaved', used (instead of 'degraded' or 'carrier') for interfaces which form a bridge, bond, or similar, and an new 'degraded-carrier' operational state used for the bond or bridge master interface when one of the enslaved devices is not operational. * .network files learnt the new IgnoreCarrierLoss= option for leaving networks configured even i
