unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Tissevert <tissevert+guix@marvid.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: website: A little help running the website locally
Date: Fri, 21 May 2021 17:36:25 +0000	[thread overview]
Message-ID: <MIVaGRDlzRuhZ0Asrjq_2rM3tJtbF_k__UD2gNLCjwhQpE7lNb8ngIKBQvAJ-pWi2rUAtU7lFtzGDQu8pWwrKgISGZ2KrbQYL4rdvr4Jye8=@protonmail.com> (raw)
In-Reply-To: <YKfZ3MkHP48DafYh@hellebore>

Hey :)


On Friday, May 21, 2021 4:04 PM, Tissevert <tissevert+guix@marvid.fr> wrote:

> Hi !
>
> I'm afraid I saw your message too late because I have exactly the same problems
> you describe in https://issues.guix.gnu.org/47623 which you've just closed.

It can be reopened if necessary, though.


> I too have no ~/.guix-profile/lib/locale but ~/.guix-profile/lib/locales exists
> and allows the build to complete. So I don't know but could this
> ~/.guix-profile/lib/locale with no trailing 's' be a left-over from a previous
> version of some software that used to build it at that location or something ?

I don't feel alone anymore :)


> My install of guix is pretty recent (~3 months).

My Guix System is more than a year old.


> From what I understood from the original issue, I checked $GUIX_LOCPATH and saw
> it contained only my current system's, /run/current-system/locale, which, when
> shared in place of this hypothetical `locales?` in $HOME/.guix-profile also
> allows haunt to build the site correctly (it produces something, reports
> success, and browsing what it serves looks like the official website).
>
> Hope that helps : )


I'm going to Guix pull, try without GUIX_LOCPATH as Julien suggests and without sharing the locales directory as you suggest, and then report back.


      parent reply	other threads:[~2021-05-21 17:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 13:53 website: A little help running the website locally Luis Felipe
2021-05-21 16:04 ` Tissevert
2021-05-21 16:38   ` Julien Lepiller
2021-05-21 16:48     ` Tissevert
2021-05-21 18:12       ` Luis Felipe
2021-05-21 18:17         ` Julien Lepiller
2021-05-21 18:33           ` Luis Felipe
2021-05-21 18:43             ` Luis Felipe
2021-05-21 18:55               ` Luis Felipe
2021-05-21 18:52             ` Julien Lepiller
2021-05-21 19:02               ` Luis Felipe
2021-05-21 19:24                 ` Julien Lepiller
2021-05-21 19:28                   ` Luis Felipe
2021-05-22 15:46                     ` Julien Lepiller
2021-05-22 18:04                       ` Luis Felipe
2021-05-26 13:46                       ` gauthier
2021-05-27 19:38                         ` Luis Felipe
2021-05-21 17:36   ` Luis Felipe [this message]

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='MIVaGRDlzRuhZ0Asrjq_2rM3tJtbF_k__UD2gNLCjwhQpE7lNb8ngIKBQvAJ-pWi2rUAtU7lFtzGDQu8pWwrKgISGZ2KrbQYL4rdvr4Jye8=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=tissevert+guix@marvid.fr \
    /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).