[ISSUE] pinfo bash: Tag table is corrupt

[ISSUE] pinfo bash: Tag table is corrupt

[tornaria]

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

New issue by tornaria on void-packages repository

https://github.com/void-linux/void-packages/issues/33849

Description:
Steps to reproduce:
 - install `pinfo`
 - run `pinfo bash`
 - move down to some menu entry and hit `<enter>`
 - The status bar reads "Tag table is corrupt, trying to fix... (press a key to continue)"

I've no idea of the format for info files, but looking at the tag table at the end of `/usr/share/info/bash.info` it seems the byte address for a given node is incorrect. Example:
```
Node: What is Bash?^?3029
```
which I take to mean this node starts at byte address 3029, but in fact it starts at byte address 3020 or 3021 (definitely not 3029).

All the tag table seems to be wrong in this sense, the offset from the "right" byte address seems to be more for later entries.

I compared the tag table for other info files (e.g. `gzip.info`) and they seem to match perfectly in contrast to `bash.info` so I guess my understanding is not incorrect and `bash.info` seems wrong for some reason.

Re: pinfo bash: Tag table is corrupt

[tornaria]

[-- 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

Re: pinfo bash: Tag table is corrupt

[tornaria]

[-- Attachment #1: Type: text/plain, Size: 315 bytes --]

New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/issues/33849#issuecomment-963344628

Comment:
https://savannah.gnu.org/support/?110557#comment1:
> Thanks for the report. I fixed this in a different way in the devel branch; the fix will be in the next bash release.

Re: pinfo bash: Tag table is corrupt

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/33849#issuecomment-1151841495

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: [ISSUE] [CLOSED] pinfo bash: Tag table is corrupt

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

Closed issue by tornaria on void-packages repository

https://github.com/void-linux/void-packages/issues/33849

Description:
Steps to reproduce:
 - install `pinfo`
 - run `pinfo bash`
 - move down to some menu entry and hit `<enter>`
 - The status bar reads "Tag table is corrupt, trying to fix... (press a key to continue)"

I've no idea of the format for info files, but looking at the tag table at the end of `/usr/share/info/bash.info` it seems the byte address for a given node is incorrect. Example:
```
Node: What is Bash?^?3029
```
which I take to mean this node starts at byte address 3029, but in fact it starts at byte address 3020 or 3021 (definitely not 3029).

All the tag table seems to be wrong in this sense, the offset from the "right" byte address seems to be more for later entries.

I compared the tag table for other info files (e.g. `gzip.info`) and they seem to match perfectly in contrast to `bash.info` so I guess my understanding is not incorrect and `bash.info` seems wrong for some reason.