From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] glib-or-gtk-build-system: new build-system
Date: Sat, 11 Oct 2014 20:31:55 +0200 [thread overview]
Message-ID: <CAKrPhPMr2ZnAj8eskjc43Y315KdS2YObE75dbULz=A-0HpXHkA@mail.gmail.com> (raw)
In-Reply-To: <87ppdy9ans.fsf@gnu.org>
On Sat, Oct 11, 2014 at 12:13 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> (Adding guix-devel, which I think was dropped by mistake.)
> Did these libcanberra issues appear after you switched Evince and
> Inkscape to ‘glib-or-gtk-build-system’?
No, it was the same before. If anything, with
glib-or-gtk-build-system, if I add
libcanberra as an input to the packages, the warning disappears.
>
> Did you browse /etc for things related to GTK+ modules? Or maybe did
> you check your user account’s GSettings database (I believe there’s a
> graphical editor to do that)?
Yes, I've looked in various places, including /etc and using the
dconf-editor, but could not
find anything useful. However, I do not really understand how gdm3 and
gnome are started
up and configured on Debian. So, I may have messed the right spot.
Fede
next prev parent reply other threads:[~2014-10-11 18:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 16:43 [PATCH] glib-or-gtk-build-system: new build-system Federico Beffa
2014-10-06 21:32 ` Ludovic Courtès
2014-10-08 7:28 ` Federico Beffa
2014-10-08 7:32 ` Federico Beffa
2014-10-08 9:49 ` Ludovic Courtès
2014-10-08 10:04 ` Ludovic Courtès
2014-10-08 11:47 ` Federico Beffa
2014-10-08 19:28 ` Ludovic Courtès
2014-10-09 20:33 ` Federico Beffa
2014-10-10 20:29 ` Ludovic Courtès
[not found] ` <CAKrPhPMURz=a3j7PMYiVTFB9QiF9-i6M_qmRj3Z9DwPDcX_wKQ@mail.gmail.com>
2014-10-11 10:13 ` Ludovic Courtès
2014-10-11 18:31 ` Federico Beffa [this message]
[not found] ` <CAKrPhPPXvgVM9XasFNQ6hVCr-79Z8yBVgEFbCjd__GuZtrM+wg@mail.gmail.com>
2014-10-09 21:10 ` Ludovic Courtès
2014-10-10 7:15 ` Federico Beffa
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='CAKrPhPMr2ZnAj8eskjc43Y315KdS2YObE75dbULz=A-0HpXHkA@mail.gmail.com' \
--to=beffa@ieee.org \
--cc=guix-devel@gnu.org \
--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 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.