From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: 40803@debbugs.gnu.org
Cc: operator.name@protonmail.com
Subject: bug#40803: One page HTML cookbooks are 404
Date: Sat, 2 May 2020 13:34:23 +0200 [thread overview]
Message-ID: <20200502133423.2ef6120a@alma-ubu> (raw)
In-Reply-To: <Q2DhdKE2ITA30H0H8zHi7FV_yR237yvzUZmHG0gWQer68Eo1cy_hg2v3aqTBOpC9TxcnByNx9zCdvdA_VAmRHkmc2qwL2bPL1cQDs4mKn8g=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
On Thu, 23 Apr 2020 22:17:13 +0000
"operator.name" via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
> As of now these following pages 404:
>
> https://guix.gnu.org/cookbook/de/guix-cookbook.de.html
> https://guix.gnu.org/cookbook/en/guix-cookbook.html
> https://guix.gnu.org/cookbook/es/guix-cookbook.es.html
> https://guix.gnu.org/cookbook/fr/guix-cookbook.fr.html
> https://guix.gnu.org/cookbook/ru/guix-cookbook.ru.html
> https://guix.gnu.org/cookbook/zh-cn/guix-cookbook.zh_CN.html
I commited a patch at the guix main repository with commit-id
7c65fc378cf68b598965fd977f5844050435ac97.
It will take a night until berlin will rebuild the documentation and
then it should be fixed on the web-site.
The translations in es, fr, ru, zh are not available for the cookbook
and the links to them will be removed.
I will control the success in 1 or 2 days and then close this bug.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-05-02 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 22:17 bug#40803: One page HTML cookbooks are 404 operator.name via Bug reports for GNU Guix
2020-04-27 23:01 ` Björn Höfling
2020-04-27 23:36 ` pelzflorian (Florian Pelz)
2020-05-02 11:34 ` Björn Höfling [this message]
2020-05-22 7:03 ` Björn Höfling
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=20200502133423.2ef6120a@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=40803@debbugs.gnu.org \
--cc=operator.name@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 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.