[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#801253: how to handle not much used feature which depends on a deprecated technology



Hey.

i want to fix this https://lintian.debian.org/tags/dbus-policy-at-console.html report in the wicd package.

the concerning lines in the wicd source dir are
(https://anonscm.debian.org/cgit/collab-maint/wicd.git/tree/other/wicd.conf)
----------------------------------------------------------------------

<!-- Comment the block below if you do not want all users logged in
    locally to have permission to use wicd-client.  This ignores the
    group based permission model defined above for the "netdev"
    group. Note that this only applies if you are using ConsoleKit -
    if you do not have ConsoleKit installed and in use, then this
    block makes no difference either way.  -->

<policy at_console="true">
    <allow send_destination="org.wicd.daemon"/>
    <allow send_interface="org.wicd.daemon"/>
    <allow send_destination="org.wicd.daemon.wireless"/>
    <allow send_interface="org.wicd.daemon.wireless"/>
    <allow send_destination="org.wicd.daemon.wired"/>
    <allow send_interface="org.wicd.daemon.wired"/>
    <allow send_interface="org.freedesktop.DBus.Introspectable"/>
</policy>

----------------------------------------------------------------------


the situation is this: the above feature is depending on consolekit, which is not actively maintained. Consolekit was, according to the git history of d/control never a dependency of wicd (at least in debian).

I don't have much evidence on this, but i doubt this feature was much consciously used. I mean, neither the manpages of wicd, nor anything else than the actual code are mentioning this feature. At least i didn't found anything else. And generally, that block is not very "beautiful" in my eyes, beacause it changes the behavior of wicd in relation of consolekit - without notifying the user about that.

So basically, i think i have 2 options:

1) remove that block in debian completely and ask upstream to do the same.

2) because of the lintian warning and the obsolescence of consolekit, converting that part to systemd-logind and send that to upstream.


what do you think about that? Am i missing sth?


Reply to: