all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: 24192@debbugs.gnu.org, Alex Kost <alezost@gmail.com>
Subject: bug#24192: Gajim fails with locale.Error
Date: Fri, 12 Aug 2016 13:33:57 -0400	[thread overview]
Message-ID: <20160812173357.GA10010@jasmine> (raw)
In-Reply-To: <CAEwRq=qVaO+EZff2rZ=g6eXUh6Xck4bSjC3WGz=-SKTahm+=iQ@mail.gmail.com>

On Fri, Aug 12, 2016 at 09:19:23AM +0200, Vincent Legoll wrote:
> >>> Isn't there a more automated way to handle these environment variables?
> >>
> >> I don't think so: if you are not on GuixSD, you have to set these
> >> variables yourself.
> >
> > Actually, I am on GuixSD. Does that mean there is some automated to do
> > this? If I have to set them manually, how do I find out what values to
> > set?
> 
> I too, am on guixsd, and I think setting some of those variables by myself
> solved a problem running things, but I may misremember...
> 
> So is this actually needed on guixsd or not ? Is there a bug somewhere
> making it required when it should not ? How can we be sure, how can we
> know which variables should be set ?

Regarding GUIX_LOCPATH, there is a bug with our current glibc/linux
package and how it finds locales, mentioned here:

http://lists.gnu.org/archive/html/guix-devel/2016-08/msg00165.html

  reply	other threads:[~2016-08-12 17:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09  5:26 bug#24192: Gajim fails with locale.Error Arun Isaac
2016-08-09  7:09 ` Danny Milosavljevic
2016-08-10  9:53   ` Arun Isaac
2016-08-11 14:05     ` Alex Kost
2016-08-12  6:04       ` Arun Isaac
2016-08-12  7:19         ` Vincent Legoll
2016-08-12 17:33           ` Leo Famulari [this message]
2016-08-12  8:42         ` Alex Kost
2016-08-09 16:40 ` Leo Famulari
2016-08-09 17:28   ` Daniel Pimentel
2016-08-09 18:58     ` Ricardo Wurmus
2016-08-09 20:53     ` Alex Kost
2016-08-29  8:52   ` Ludovic Courtès
2018-09-05  7:08     ` Arun Isaac

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=20160812173357.GA10010@jasmine \
    --to=leo@famulari.name \
    --cc=24192@debbugs.gnu.org \
    --cc=alezost@gmail.com \
    --cc=vincent.legoll@gmail.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 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.