From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: phodina <phodina@protonmail.com>,
"44400@debbugs.gnu.org" <44400@debbugs.gnu.org>
Subject: [bug#44400] [PATCH v2 4/4] WIP: gnu: Add phosh.
Date: Wed, 17 Nov 2021 11:26:14 +0100 [thread overview]
Message-ID: <ed0f57d0-64a2-43b5-8e79-76162d0657b1@web.de> (raw)
In-Reply-To: <rM5Gi-SukHuqhKGHQNNoM2f1zA7KZ7HBwGMoPWpG0ATsdgjCn0Q01iReHK0ABNjz24YMIUxE1Cm395TjzYie5GjpNbq8WT8D5fiuHPzH9Vc=@protonmail.com>
On 17.11.21 11:19, phodina via Guix-patches via wrote:
> * gnu/packages/gnome.scm (phosh): New variable.
Does phosh work for you? I only got phoc running, phosh "refused" to
start...
next prev parent reply other threads:[~2021-11-17 10:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 22:13 [bug#44400] [PATCH 0/2] WIP: Add phosh Jonathan Brielmaier
2020-11-02 22:28 ` [bug#44400] [PATCH 1/2] WIP: gnu: Add phoc Jonathan Brielmaier
2020-11-02 22:28 ` [bug#44400] [PATCH 2/2] WIP: gnu: Add phosh Jonathan Brielmaier
2021-02-08 11:02 ` Jonathan Brielmaier
2021-11-17 10:16 ` [bug#44400] [PATCH v2 1/4] gnu: Add phoc phodina via Guix-patches via
2021-11-17 10:17 ` [bug#44400] [PATCH v2 2/4] gnu: libhandy: Update to 1.5.0 phodina via Guix-patches via
2021-11-17 10:18 ` [bug#44400] [PATCH v2 3/4] gnu: Add callaudiod phodina via Guix-patches via
2021-11-17 10:19 ` [bug#44400] [PATCH v2 4/4] WIP: gnu: Add phosh phodina via Guix-patches via
2021-11-17 10:26 ` Jonathan Brielmaier [this message]
2021-11-17 10:32 ` phodina via Guix-patches via
2021-11-28 10:46 ` phodina via Guix-patches via
2022-03-24 13:32 ` [bug#44400] [PATCH v3 1/5] " phodina via Guix-patches via
2021-11-17 10:26 ` [bug#44400] Phosh v2 patches comments phodina via Guix-patches via
2022-03-04 17:40 ` [bug#44400] [PATCH 0/2] WIP: Add phosh Jonathan Brielmaier
2022-08-14 20:00 ` [bug#44400] [PATCH v4]: gnu: " phodina via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ed0f57d0-64a2-43b5-8e79-76162d0657b1@web.de \
--to=jonathan.brielmaier@web.de \
--cc=44400@debbugs.gnu.org \
--cc=phodina@protonmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).