From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: dbus-elogind: remove package, migrate to regular dbus
Date: Mon, 17 Jul 2023 18:15:08 +0200 [thread overview]
Message-ID: <20230717161508.xVZjjl8AvZwcrqjNHzuakZpdDiUD9nvQwiXwrR4YEq0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45026@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
There's a closed pull request on the void-packages repository
dbus-elogind: remove package, migrate to regular dbus
https://github.com/void-linux/void-packages/pull/45026
Description:
`dbus-elogind` adds a patch that enabled `dbus` to query elogind to determine whether the current user is seated at a physical console. Without this, there are a few fallbacks that seem not to be enabled or supported in our `dbus` package, so `dbus` just assumes that no user is "at the console".
It seems the only consumer of this is a `connman` policy at `/usr/share/dbus-1/systemd/connman-nmcompat.conf` that, based on the file name, allows connman to respond to messages for `org.freedesktop.NetworkManager` originating from users physically at the console.
This package adds maintenance burden (we have to keep this in sync with `dbus` and have to duplicate services and `INSTALL` scripts) and, in at least one case a few years ago, a user was bitten when a newer `dbus-libs` was somehow installed alongside a `dbus-elogind` package that hadn't been updated, breaking the installation. There is too much confusion for essentially zero benefit, so let's just drop this version and push people to the standard packages.
I still need to test the upgrade path with the elimination of `provides` and `replaces` and the addition of `depends`.
prev parent reply other threads:[~2023-07-17 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 0:54 [PR PATCH] " ahesford
2023-07-14 17:47 ` Duncaen
2023-07-14 19:37 ` ahesford
2023-07-15 15:20 ` ahesford
2023-07-15 15:37 ` [PR PATCH] [Updated] " ahesford
2023-07-15 15:39 ` ahesford
2023-07-17 16:15 ` ahesford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230717161508.xVZjjl8AvZwcrqjNHzuakZpdDiUD9nvQwiXwrR4YEq0@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).