From: Vivien Kraus via Guix-patches via <guix-patches@gnu.org>
To: Dariqq <dariqq@posteo.net>, 68937@debbugs.gnu.org
Cc: Raghav Gururajan <rg@raghavgururajan.name>,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#68937] [PATCH 0/3] Orca fixes
Date: Mon, 05 Feb 2024 17:50:10 +0100 [thread overview]
Message-ID: <a942802370c7cabb330972c3c7ba5fbe6009b89c.camel@planete-kraus.eu> (raw)
In-Reply-To: <cover.1707146219.git.dariqq@posteo.net>
Hello!
Le lundi 05 février 2024 à 15:44 +0000, Dariqq a écrit :
> As reported in https://issues.guix.gnu.org/64357 orca currently fails
> to run.
I believe this specific issue does not arise anymore with orca 44.2 on
gnome-team: it does some screen reading. Does it fix your issue?
Otherwise, could you rebase your work on top of gnome-team ?
Best regards,
Vivien
next prev parent reply other threads:[~2024-02-05 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 15:44 [bug#68937] [PATCH 0/3] Orca fixes Dariqq
2024-02-05 15:48 ` [bug#68937] [PATCH 1/3] gnu: orca: Fix invocation errors Dariqq
2024-02-05 15:48 ` [bug#68937] [PATCH 2/3] gnu: brltty: Fix python package install Dariqq
2024-02-05 15:48 ` [bug#68937] [PATCH 3/3] gnu: orca: Add more optional dependencies Dariqq
2024-02-05 16:50 ` Vivien Kraus via Guix-patches via [this message]
2024-02-05 18:32 ` [bug#68937] [PATCH 0/3] Orca fixes Dariqq
2024-02-05 18:49 ` [bug#68937] [PATCH gnome-team v2 1/2] gnu: brltty: Fix python package install Dariqq
2024-02-05 18:49 ` [bug#68937] [PATCH gnome-team v2 2/2] gnu: orca: Add optional dependencies Dariqq
2024-02-16 19:49 ` Maxim Cournoyer
2024-02-10 8:12 ` [bug#68937] QA review for 68937 Vivien Kraus via Guix-patches via
2024-02-10 11:11 ` Christopher Baines
2024-02-10 11:15 ` bug#68937: " Christopher Baines
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=a942802370c7cabb330972c3c7ba5fbe6009b89c.camel@planete-kraus.eu \
--to=guix-patches@gnu.org \
--cc=68937@debbugs.gnu.org \
--cc=dariqq@posteo.net \
--cc=liliana.prikler@gmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=rg@raghavgururajan.name \
--cc=vivien@planete-kraus.eu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.