From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Should ConsoleKit2 be removed?
Date: Thu, 02 Apr 2020 18:08:14 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20577@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
New issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/20577
Description:
[ConsoleKit2](https://github.com/ConsoleKit2/ConsoleKit2) hasn't received any updates since 2017, which is quite worrying for a piece of software with that big of a scope. Its functionality has been superseded by elogind, and the only docs page that still refers to it is the one for session management under Xorg (which can be updated).
Running `xbps-query -RX ConsoleKit2` on armv6l-musl returned only `ConsoleKit2-devel` and `ulatencyd` (which hasn't been updated in a while either), so it shouldn't be a dependency for anything.
next reply other threads:[~2020-04-02 16:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 16:08 ericonr [this message]
2020-04-02 16:15 ` xtraeme
2020-04-02 16:22 ` xtraeme
2020-04-02 16:24 ` ericonr
2020-04-02 16:27 ` Duncaen
2020-04-02 16:29 ` xtraeme
2020-04-02 16:30 ` xtraeme
2020-04-02 16:31 ` xtraeme
2020-04-02 16:32 ` xtraeme
2020-04-02 16:32 ` Duncaen
2020-04-02 16:32 ` xtraeme
2020-04-02 16:33 ` Duncaen
2020-04-02 16:34 ` xtraeme
2020-04-02 16:35 ` xtraeme
2020-04-02 16:40 ` xtraeme
2020-04-02 16:42 ` xtraeme
2020-04-02 16:42 ` Duncaen
2020-04-02 16:42 ` xtraeme
2020-04-02 16:54 ` xtraeme
2020-04-02 17:00 ` the-maldridge
2020-04-02 17:02 ` xtraeme
2020-04-02 17:06 ` xtraeme
2020-04-02 17:12 ` the-maldridge
2020-04-02 17:16 ` xtraeme
2020-04-02 17:25 ` xtraeme
2020-04-12 0:00 ` ericonr
2020-07-14 18:40 ` Chocimier
2020-07-14 18:40 ` [ISSUE] [CLOSED] " Chocimier
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20577@inbox.vuxu.org \
--to=ericonr@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).