Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Snapper complains about locale and fails upon dbus fatal exception
Date: Wed, 09 Dec 2020 15:59:06 +0100	[thread overview]
Message-ID: <20201209145906.jzVTpc8J9mEHqP3zYdSGR-oEJOCUjFpVqITvsUl2OBk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27047@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/27047#issuecomment-741825993

Comment:
Making `snapper` depend on `dbus` sounds reasonable to me. Could you open a PR for it?

Having documentation in the install message is a bit complicated, though. Few people read them, and accessing them isn't something most people remember how to do, so if they miss it during installation they are unlikely to ever read them.

Void doesn't have dbus enabled by default and leaves that as something the user can choose to enable or not. Therefore, it's expected that a fatal error about dbus would prompt the user to try and enable the service. Information about dbus is covered in https://docs.voidlinux.org/config/session-management.html

  parent reply	other threads:[~2020-12-09 14:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 14:27 [ISSUE] " Mek101
2020-12-09 14:48 ` ericonr
2020-12-09 14:51 ` Mek101
2020-12-09 14:59 ` ericonr [this message]
2020-12-09 15:06 ` Mek101
2020-12-09 15:08 ` Mek101
2020-12-09 15:31 ` ericonr
2020-12-09 16:24 ` loreb
2020-12-09 16:48 ` Mek101
2020-12-09 16:54 ` loreb
2020-12-09 17:36 ` ericonr
2020-12-10 13:36 ` ericonr
2020-12-10 13:36 ` [ISSUE] [CLOSED] " ericonr

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=20201209145906.jzVTpc8J9mEHqP3zYdSGR-oEJOCUjFpVqITvsUl2OBk@z \
    --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).