From: CMB <CMB@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: brltty: file /etc/brlapi.key should be created upon package install with random contents
Date: Fri, 05 Feb 2021 15:45:26 +0100 [thread overview]
Message-ID: <20210205144526._LSjbjJEzPgTWF8NtXhd-sbszPISPV5eYTrwl7UiEhw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12173@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
New comment by CMB on void-packages repository
https://github.com/void-linux/void-packages/issues/12173#issuecomment-774075582
Comment:
@ericonr Yes, this ticket is still applicable.
BTW here's how you can test for the problem locally.
Install brltty and python3-brlapi. Start the runit service. It should
start even if you don't have a braille display and haven't done any
configuration. Run:
python3 -c 'import brlapi ; brlapi.Connection()'
If there's no readable /etc/brlapi.key file, you'll get a traceback
complaining about it.
Probably we want to do what Arch does here: a brlapi group owning that
file, with 0640 permissionss.
next prev parent reply other threads:[~2021-02-05 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 20:07 [ISSUE] " voidlinux-github
2019-06-06 7:51 ` voidlinux-github
2021-02-05 14:45 ` CMB [this message]
2022-04-15 2:12 ` github-actions
2022-04-29 2:13 ` [ISSUE] [CLOSED] " github-actions
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=20210205144526._LSjbjJEzPgTWF8NtXhd-sbszPISPV5eYTrwl7UiEhw@z \
--to=cmb@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).