problems when upgrading to qubes-core-agent_3.2.25-1+deb9u1

[Holger Levsen]

hi,

I just upgraded my 3.2 installation and on Debian 9 templates I saw
this:

Preparing to unpack .../qubes-core-agent_3.2.25-1+deb9u1_amd64.deb ...
Unpacking qubes-core-agent (3.2.25-1+deb9u1) over (3.2.22-1+deb9u1) ...
dpkg: warning: unable to delete old directory '/var/run/qubes': Directory not empty
dpkg: warning: unable to delete old directory '/rw': Device or resource busy
dpkg: warning: unable to delete old directory '/home_volatile/user': Directory not empty
dpkg: warning: unable to delete old directory '/home_volatile': Directory not empty
Setting up qubes-core-agent (3.2.25-1+deb9u1) ...
Installing new version of config file /etc/qubes-rpc/qubes.GetImageRGBA ...
Installing new version of config file /etc/qubes-suspend-module-blacklist ...
Removed /etc/systemd/system/multi-user.target.wants/haveged.service.
Created symlink /etc/systemd/system/multi-user.target.wants/haveged.service → /etc/systemd/system/haveged.service.
Leaving 'diversion of /etc/init/plymouth-shutdown.conf to /etc/init/plymouth-shutdown.conf.qubes-disabled by qubes-core-agent'
Leaving 'diversion of /etc/init/prefdm.conf to /etc/init/prefdm.conf.qubes-disabled by qubes-core-agent'
Leaving 'diversion of /etc/init/splash-manager.conf to /etc/init/splash-manager.conf.qubes-disabled by qubes-core-agent'
Leaving 'diversion of /etc/init/start-ttys.conf to /etc/init/start-ttys.conf.qubes-disabled by qubes-core-agent'
Leaving 'diversion of /etc/init/tty.conf to /etc/init/tty.conf.qubes-disabled by qubes-core-agent'
Leaving 'diversion of /etc/init/serial.conf to /etc/init/serial.conf.qubes-orig by qubes-core-agent'
/var/lib/dpkg/info/qubes-core-agent.postinst: line 192: dconf: command not found


the attempted removal of those directories seems bad (how bad is it, can I reboot?)
and the missing dconf commands feels like a missing depends...


--
cheers,
Holger

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hmm, indeed something is not right. But since the removal failed, it
should be safe...

What was your previous qubes-core-agent package version?

> and the missing dconf commands feels like a missing depends...

Should be ok - means you don't need any gnome stuff the configuration is
shipped for. dconf should be called automatically as soon as you install
anything using it.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqgX5gACgkQ24/THMrX
1yyJhwf/QDstmFmK72yFQUL6I8DJrm7WtHqiKpGCYaD88YQzowJ9PO93UvXI0Uq8
+UjXNCFIXiNEqKIG+kqsEvCXoPqZGohZ8h2s4GJ3LWklGcNSwRzW7tLURKZaQpWT
aOu0PiLa3LpVX/ceRf7DvJjmaXXc1fB/nF6TkLIM2mfrV2S+Qy4/DGG3UeRPPXPN
ycgJwsAKtAbuR7jGRSFeD4HewcHSZ33/i81oY6PSexFExCZoesk7z/pWzKJMLc4m
pYyf3cNXhdJN8v7qEr/ea3k6hRqswfmnnUcewESILaVlBz7gOf4vbYMNaDK9QGNN
MBlh1+X4MUptq/T8/bnxmo5JC5Wskw==
=oaSv
-----END PGP SIGNATURE-----

[Holger Levsen]

On Mon, Mar 12, 2018 at 08:43:47PM +0100, Marek Marczykowski-Górecki wrote:
> Hmm, indeed something is not right. But since the removal failed, it
> should be safe...

"should"...

> What was your previous qubes-core-agent package version?

3.2.22-1+deb9u1

> > and the missing dconf commands feels like a missing depends...
> Should be ok - means you don't need any gnome stuff the configuration is
> shipped for. dconf should be called automatically as soon as you install
> anything using it.

then why not use

if [ -x /usr/bin/dconf ] ; then
$use-dconf
fi

? :)


--
cheers,
Holger

[Ilpo Järvinen]

The code [1] is using:
dconf update || true
...or similar pattern so it's not a sign of a real problem but triggering
that error message is still somewhat annoying.

--
i.

[1] https://github.com/QubesOS/qubes-core-agent-linux/commit/ab8028475997e5046d0ba96a361dc41c95fb993e