Your message dated Sat, 29 Aug 2020 15:51:00 +0000 with message-id <[email protected]> and subject line Bug#968612: fixed in systemd 246.2-2 has caused the Debian Bug report #968612, regarding New ConditionEnable feature inop to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 968612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968612 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: systemd Version: 246.1-1 Severity: normal Systemd 246 introduces ConditionEnviornment=/AssertEnvironment [1] in the [Unit] configuration (see systemd.unit(5)). This feature does not appear to work. The first evidence of this is neither ConditionEnvironment or AssertEnvironment get parsed by `systemd-analyze` which other conditions are parsed (even when empty): $ systemd-analyze condition \ 'ConditionKernelVersion=' \ 'ConditionKernelVersion=' \ 'ConditionACPower=' \ 'ConditionArchitecture=' \ 'AssertPathExists=' \ 'AssertEnvironment=' Cannot parse "AssertEnvironment=". The second evidence is that targets can be reached when conditions are not met: $ systemctl --user cat i3-session-pre.target # /home/stew/.config/systemd/user/i3-session-pre.target [Unit] Description=i3 session BindsTo=graphical-session-pre.target ConditionEnvironment=THIS_ENV_DOESNT_EXIST=1 $ systemctl --user start i3-session-pre.target $ systemctl --user status i3-session-pre.target ● i3-session-pre.target - i3 session Loaded: loaded (/home/stew/.config/systemd/user/i3-session- pre.target; static) Active: active since Tue 2020-08-18 17:29:36 CEST; 6s ago Aug 18 17:29:36 stewbian systemd[1717]: Reached target i3 session. The same behaviour was observed for (1) non-existent environment variables (2) environment variables with incorrect data (3) matching environment variables. I can confirm that the pull request related to this [2] appears to be integrated. I confirmed that with `apt source systemd` and inspecting the sources. I suspect the problem lies upstream. [1]: https://raw.githubusercontent.com/systemd/systemd/master/NEWS [2]: https://github.com/systemd/systemd/pull/15817
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---Source: systemd Source-Version: 246.2-2 Done: Michael Biebl <[email protected]> We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl <[email protected]> (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sat, 29 Aug 2020 16:24:49 +0200 Source: systemd Architecture: source Version: 246.2-2 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <[email protected]> Changed-By: Michael Biebl <[email protected]> Closes: 954312 968589 968612 969006 Changes: systemd (246.2-2) unstable; urgency=medium . [ Balint Reczey ] * debian/systemd.postinst: Restart systemd-networkd.socket on incompatible change. PassCredentials=yes is replaced with PassPacketInfo=yes and extra padding is dropped, too. (Closes: #968589, LP: #1891716) . [ Michael Biebl ] * Fix restart of systemd-networkd.socket. We can't restart the socket while systemd-networkd.service is still active. Instead we stop the socket and ensure, that a try-restart of systemd-networkd.service also starts the socket. * seccomp: Add support for riscv64 (Closes: #954312) * Support missing conditions/asserts everywhere (Closes: #968612) * path: Skip directories when finalising $PATH search (Closes: #969006) Checksums-Sha1: 7f41e258b69bd1bd3639668c2d2ef5ccb3fa3dc6 5141 systemd_246.2-2.dsc 664667c20bfc6443a54d24668c3abbd9df5da459 156780 systemd_246.2-2.debian.tar.xz 984ce4e138260de1f2f2fdb7d96c2acb0905503b 9310 systemd_246.2-2_source.buildinfo Checksums-Sha256: 1793e781da1ae9a780925634bdac740cc6475e542857d8f72e66099e80778e78 5141 systemd_246.2-2.dsc 8d271d23880505ee8bfaf0bac7f79570607eb6737230514f01d8f89d92df40cc 156780 systemd_246.2-2.debian.tar.xz 737c674ebcfd243762c26931185c1e5311252b86c747416148d84370e30b648d 9310 systemd_246.2-2_source.buildinfo Files: 378a1a78de32550497942e46644955d5 5141 admin optional systemd_246.2-2.dsc 7be29d57dd9e26fef4d85233c5afb264 156780 admin optional systemd_246.2-2.debian.tar.xz 01d7be574c42af23c07f443e6282ac14 9310 admin optional systemd_246.2-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAl9KdGMACgkQauHfDWCP ItyEmxAAi7XsVS3LnKJTxiOp8jtq8dhcHT63rJ5xKWBXA8WYT1QsS04/yHUBu6ci kdUQVqaNE2a0YRTuh/7Cimop0E4+tqg3jiRkw8O8oyS91RqfRbfrYkUs3m5qNjYb qzEXVSwLYZSr57tqvtORLTMROtozdq2VuwTKfepFlLeNt67BrV1lJFOmVYme5Hm0 B9gCtQfM7dw7LzmNt9fxUz7y3PZQh01kqA60vIp/u/l0s94xlNU4tPgBaVqJ4/h4 Uwt5AAdfbZTYrc7YAZEa/TpCsV3caCpJEyvyTkTXyl6m0jAfL3TWI12J/grRtK/B eWSkY4IqrLUWmbtnTzkHPHeOCnnWCIaepyPxgYmcDk1aRLmsganmq0S1EllzYQJd PieeLe259nJdl11PPSHtG0IrZpnLVrIacRcP608VHbzcZTgU9S3aAbZK/l/1Esv4 y9EB/lsatY4RxyREFo56dxCnnU1sf0zTHEbS73pLj33w4E7HV0D4eUvScvOUb9jr aLFdo8KzOedYFQUbKbSvSMBsX2UzqvWDDTnmf0pE5JZzuJIgZ6lXAR0YSJxX1KNB R0+FIFv+aD5ObXYZjlCSkEZoHD5a6nOwrmmOYqTlAJHV/8T+lCLbQBSDir0mKY/W TWlBsFC1UlH3gqbfrEaYxyTvMmS7C9aHACJXbeMGr5f6V1OHc2w= =+Ojc -----END PGP SIGNATURE-----
--- End Message ---
