On Sat, 16 Dec 2017 at 10:53:22 +0000, Holger Levsen wrote: > On Sat, Dec 16, 2017 at 10:21:40AM +0000, Chris Lamb wrote: > > [Adding Holger, the original submitter, to the CC - please see the last two > > messages for some more context] > > Wow, thank you so much for the detailed explanation! > > indeed & thank you too for keeping me in the loop. > > This is great news as I'd like to get rid of these issues in > src:debian-edu-config for buster and it seems there's now enough > documentation that we'll be able to do so.
Sending this specifically to you in case you missed it, since you weren't in Cc at the time: for debian-edu-config, you don't need documentation for how to replace /etc/dbus-1/system.d/hal-debian-edu.conf because I'm fairly sure it already has no practical effect: In this specific case: you should probably drop the file (preferably into a bonfire), since HAL is very, very obsolete, and I very much hope debian-edu no longer uses or ships it. The parts of HAL where high-level APIs made sense were replaced by the DeviceKit services, which were later renamed to or replaced by udisks, upower and possibly others; lower-level device enumeration and change-notification were superseded by using udev directly. hal was most recently in Debian as part of wheezy (oldoldstable), so the file triggering the lintian warning in debian-edu-config is useless and can safely be removed, unless debian-edu has some lookaside package repository with packages that are no longer in Debian (in which case I would still recommend dropping hal as soon as possible, because it hasn't been maintained for years). If you want to configure access control for the services that replaced hal, you'll need to write polkit policies (but if nobody has noticed a problem with them, their defaults might well be fine for your use case). smcv