unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Leo Prikler <leo.prikler@student.tugraz.at>, 47097@debbugs.gnu.org
Subject: bug#47097: eolie broken => unworking example from manual
Date: Wed, 24 Mar 2021 04:14:00 +0100	[thread overview]
Message-ID: <868s6di6pz.fsf@gmail.com> (raw)
In-Reply-To: <87czvwkx8e.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Thu, 18 Mar 2021 21:44:49 +0100")

Hi,

On Thu, 18 Mar 2021 at 21:44, Ludovic Courtès <ludo@gnu.org> wrote:
> Leo Prikler <leo.prikler@student.tugraz.at> skribis:
>
>> This fixes errors observed directly at launch of Eolie inside pure
>> environments.  (See <https://bugs.gnu.org/47097> for more information.)
>> It is still not possible to launch Eolie inside a container, however.
>> (See also <https://bugs.gnu.org/47106>.)
>>
>> * gnu/packages/gnome.scm (eolie)[inputs]: Add libhandy and
>> gnome-settings-daemon.
>
> LGTM, thanks!

I could have missed the commit, I guess this patch is not pushed.  It
seems nice to have for the next release.  Since it fixes an example from
the manual. :-)


Cheers,
simon




  reply	other threads:[~2021-03-24  3:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 10:56 bug#47097: eolie broken => unworking example from manual zimoun
2021-03-12 11:44 ` Martin via Bug reports for GNU Guix
2021-03-12 17:55 ` bug#47097: [PATCH] gnu: eolie: Add missing inputs Leo Prikler
2021-03-18 20:44   ` bug#47097: eolie broken => unworking example from manual Ludovic Courtès
2021-03-24  3:14     ` zimoun [this message]
2021-03-24  8:07       ` Leo Prikler
2021-03-24 16:17         ` Ludovic Courtès
2021-03-26 12:32           ` Leo Prikler
2021-04-10 18:40         ` Leo Famulari
2021-04-10 20:24           ` Leo Prikler
2021-04-10 20:31             ` Leo Famulari
2021-04-14 20:03               ` Leo Famulari

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=868s6di6pz.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=47097@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    --cc=ludo@gnu.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.
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).