From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinfo bash: Tag table is corrupt
Date: Sun, 31 Oct 2021 23:33:11 +0100 [thread overview]
Message-ID: <20211031223311.RC9OagOviWoQ7zrJhNWajwha-XT4SQxX0Vj9O2c3FIU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33849@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/33849#issuecomment-955803491
Comment:
After a quick look, it seems to be an upstream bug. The file `bash.info` is an identical copy with the one shipped in distfiles (void doesn't even compile `bash.info`, rather it uses the shipped copy as-is).
As for the bug: it turns out that `bashref.info` is compiled from the documentation, and this is later piped through `sed -e 's|bashref.info|bash.info|g'` to create `bash.info`. That obviously modifies byte addresses all over the place, rendering the tag table incorrect.
I've reported this upstream at https://savannah.gnu.org/support/index.php?110557.
My suggestion there is to recreate bash.info from bashref.info with
```
sed -e 's|bashref.info,|bash.info, |g'
```
@Gottox: I could:
a. make a PR doing that for the void package as (I guess) a `pre_install()` step.
b. include the suggested fix as a patch.
c. do nothing and just wait for this to be fixed upstream.
In fact (b) seems a simple solution, patch here: https://gist.github.com/tornaria/dcf5b0682be0cef99442adc8c8b23dba
next prev parent reply other threads:[~2021-10-31 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 16:01 [ISSUE] " tornaria
2021-10-31 22:33 ` tornaria [this message]
2021-11-08 16:35 ` tornaria
2022-06-10 2:14 ` github-actions
2022-06-24 2:15 ` [ISSUE] [CLOSED] " github-actions
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=20211031223311.RC9OagOviWoQ7zrJhNWajwha-XT4SQxX0Vj9O2c3FIU@z \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).