From: Alex Kost <alezost@gmail.com>
To: myglc2 <myglc2@gmail.com>
Cc: 22651@debbugs.gnu.org
Subject: bug#22651: Up: GNU Guix doc produces 404 page not found
Date: Mon, 15 Feb 2016 22:49:45 +0300 [thread overview]
Message-ID: <87fuwt3g9y.fsf@gmail.com> (raw)
In-Reply-To: <87si0wmte9.fsf@gmail.com> (myglc2@gmail.com's message of "Sat, 13 Feb 2016 12:06:54 -0500")
myglc2 (2016-02-13 20:06 +0300) wrote:
> Start on https://www.gnu.org/software/guix/download/
> click 'Installation instructions.' and 'Up' 3 times
> lands on 'https://www.gnu.org/software/guix/manual/dir/index.html'
> which produces '404 - Page Not Found' error
This is not a Guix bug. It happens with any html manual on gnu.org.
For example, try to press "Up (dir)" here:
https://www.gnu.org/software/guile/manual/html_node/index.html
or here:
https://www.gnu.org/software/emacs/manual/html_node/erc/index.html
You'll get the same 404. These pages are automatically generated from
texinfo manuals. See also a similar issue at
<https://debbugs.gnu.org/22543>.
--
Alex
next prev parent reply other threads:[~2016-02-15 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 17:06 bug#22651: Up: GNU Guix doc produces 404 page not found myglc2
2016-02-15 19:49 ` Alex Kost [this message]
2016-02-15 20:06 ` carl hansen
2016-02-15 23:10 ` Thompson, David
2016-02-16 0:59 ` carl hansen
2016-02-16 1:22 ` Leo Famulari
2016-05-03 20:54 ` bug#22651: "Up (dir)" HTML link is 404 Ludovic Courtès
[not found] ` <877ffaj20x.fsf_-_@gnu.org>
2016-05-04 18:07 ` Gavin Smith
[not found] ` <CAKPWYQ3muG3nLo8yQJVhe9ueLQPohSUn9it3vq6s8JvWLfgSKw@mail.gmail.com>
2016-05-05 12:47 ` Ludovic Courtès
[not found] ` <87h9ecekn5.fsf@gnu.org>
2016-05-05 14:44 ` Gavin Smith
2016-05-07 17:25 ` bug#22651: [PATCH] gendocs.sh: Fix "dir" link in HTML output Ludovic Courtès
2016-09-27 16:53 ` bug#22651: fixed, please close ng0
2016-09-30 16:12 ` Ludovic Courtès
2016-09-27 18:51 ` bug#22651: ng0
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=87fuwt3g9y.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=22651@debbugs.gnu.org \
--cc=myglc2@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 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).