From: Nils Gillmann <niasterisk@grrlz.net>
To: Leo Famulari <leo@famulari.name>
Cc: 22543@debbugs.gnu.org, Alex Kost <alezost@gmail.com>
Subject: bug#22543: 404 in Manualpage
Date: Tue, 16 Feb 2016 10:56:05 +0100 [thread overview]
Message-ID: <87k2m5vv0q.fsf@grrlz.net> (raw)
In-Reply-To: <20160213002628.GB10770@jasmine> (Leo Famulari's message of "Fri, 12 Feb 2016 19:26:28 -0500")
Leo Famulari <leo@famulari.name> writes:
> On Wed, Feb 03, 2016 at 02:41:04PM +0100, Nils Gillmann wrote:
>> The manual page
>> https://www.gnu.org/software/guix/manual/html_node/Requirements.html#Requirements
>>
>> contains a link to
>>
>> https://www.gnu.org/software/guix/manual/gnutls-guile/Guile-Preparations.html#Guile-Preparations
>>
>> which give a 404. I am not familiar with what's supposed to be there, a
>> quick search for "gnutls-guile/Guile-Preparations.html" in duckduckgo gives me
>> http://www.gnutls.org/manual/gnutls-guile/Guile-Preparations.html as one
>> of 2 results.
>>
>> Should I fix the link to this one and send in a patch?
>
> Yes, please!
So you think I should (and can?) fix it, while alex replies:
>> I don't think you can send a patch for this. According to
>> <https://www.gnu.org/software/guix/manual/>:
>>
>> (This page generated by the gendocs.sh¹ script.)
>> This "gendocs.sh" uses "texi2html" to convert our texinfo documentation
>> (see "doc/guix.texi" in the guix git repo) to the html page. In
>> "guix.texi" the link you are talking about is a usual link to the
>> "gnutls-guile" manual. I didn't look at "texi2html" but I believe by
>> default it just assumes that all the manuals are placed at
>> "www.gnu.org/software/<package>/manual/", so for "external" manuals the
>> generated links are false. For example, there are also wrong links to
>> Geiser and Magit-Popup manuals.
>>
>> So I think it's a general thing for all generated manuals that are
>> placed on "gnu.org".
>>
>> ¹ http://git.savannah.gnu.org/cgit/gnulib.git/plain/build-aux/gendocs.sh
>>
>> --
>> Alex
Okay, so I guess it's related to #22651 and it#s not fixable the
way I want to (edit the source), or at least what I would want to
do is not optimal and it should be fixed in some other way.
Didn't look into it yet, but should we follow #22651 for the 404s?
--
ng
next prev parent reply other threads:[~2016-02-16 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 13:41 bug#22543: 404 in Manualpage Nils Gillmann
2016-02-13 0:26 ` Leo Famulari
2016-02-16 9:56 ` Nils Gillmann [this message]
2016-02-17 9:29 ` Alex Kost
2016-02-14 11:15 ` Alex Kost
2016-02-21 21:30 ` Ludovic Courtès
2016-02-22 11:31 ` Alex Kost
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=87k2m5vv0q.fsf@grrlz.net \
--to=niasterisk@grrlz.net \
--cc=22543@debbugs.gnu.org \
--cc=alezost@gmail.com \
--cc=leo@famulari.name \
/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).