Is any special action required when updating to qubes-core-agent-networking (4.0.47-1+deb10u1) in Whonix templates?

29 views
Skip to first unread message

Andrew David Wong

unread,
Sep 2, 2019, 1:35:57 PM9/2/19
to qubes...@googlegroups.com, Marek Marczykowski-Górecki, Patrick Schleizer
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

When recently updating to qubes-core-agent-networking
(4.0.47-1+deb10u1) in whonix-gw-15 and whonix-ws-15, I noticed the
following output, which I don't recall ever seeing before:

```
Setting up qubes-core-agent-networking (4.0.47-1+deb10u1) ...
Installing new version of config file /etc/udev/rules.d/99-qubes-network.rules ...
[qubes-core-agent-linux.conf:1] Line references path below legacy directory /var/run/, updating /var/run/tinyproxy-updates → /run/tinyproxy-updates; please update the tmpfiles.d/ drop-in file accordingly.
Warning: The unit file, source configuration file or drop-ins of qubes-network.service changed on disk. Run 'systemctl daemon-reload' to reload units.
```

I'm being instructed to do two things:

(1) "update the tmpfiles.d/ drop-in file accordingly"
(2) "Run 'systemctl daemon-reload' to reload units"

I had no idea what (1) meant, so I searched online and found that it
appears to be an upstream issue. [1][2] However, I still don't know
whether I, as a Qubes user, should take any action here. What, if
anything, should I do?

I also wasn't sure about (2). I knew I could simply execute that
command as instructed, but I'm not sure if I should. After searching
online, (2) appears to be a pretty general mechanism that also isn't
Qubes-specific. [3] In this case, I'm wondering whether simply
restarting the TemplateVM once is enough, or whether any further
action is required (or recommended) on my part here. Any thoughts?


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902413
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1658487
[3] https://unix.stackexchange.com/q/364782

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl1tUtYACgkQ203TvDlQ
MDCOzxAAqrjIybQmRsaCyOz28+xHcVGeO1vC2wv8854dqHM4BNgMAEzODqqdPc/v
zXaYqJyPrG9jTmERLDKBf+/YovcSfPfrMU7hMXK/OwIhVKymp0byKmO+EjQv74GU
SDrE+S0zbGjWYP5Na6RlXvEx8zHMShGdA2hMLDm2X3ZPEYE13N+KKe8RNUc2XLAf
iCaBMVuwdum18/bvX903huX7jZJ1i/wa7rvkVSJ9BMGeJpP+YMLtL22palANym+E
JUeGySX4mZLe7rZXiaiqkHC3jKun3eSpRqrKx2yB/ryLTIZo34oogMwVWJztHNSq
mXppcANUF9UdyCz2X7y6gZGNlX3QS+oQPobTQ0GgLd0R7K9uJhxHnDbDqU50C7vE
QHsSyoKKX0vUA8hOoeIUg1JUSgSeGAtxqbLC7D8eDcQIxv1JLsG7hzfqNWUzcik0
ARxA7aklJgc8wlg/zobN6Q8MZaN7scbHAol7dH8hY+8PjsACi7mzyybhIkbXGSkJ
kBOWNoLP7HJPK9RyVsgmuf6/RnJnTN/7HmLMJBw1GSXecgtSYLRfDeHPkQY+m63A
2t0qi1IFRRlpLeHTjMAsvhKs9GltFtLunH/VHOLUdWLQgCDWR/79nloBYx/5HbOJ
xafZKTZR6A46JsnlTCSZKVkNzff9+xllLSGazh+hUEaRX65+gd4=
=CtX7
-----END PGP SIGNATURE-----


Reply all
Reply to author
Forward
0 new messages