Something obviously went wrong sometime with my GNU info pages directory. Now emerge suggests me after emerging some random package to run use "emerge --verbose" to see what went wrong. However just typing "emerge --verbose" just displays the help. Trying to reemerge the same package with --verbose doesn't help either since the gnu info pages cache isn't updated then Reproducible: Always Steps to Reproduce: 1. "break gnu info packages" 2. emerge foo 3. emerge --verbose # as suggested Actual Results: shows help Expected Results: shows what went wrong with the info pages
Created attachment 24981 [details, diff] patch to disable the --verbose check Many users get confused by this message, so I think we should always show the error message or never (as most people don't use them anyway).
IMO, if we do this fix we need changing to always do "print myso" and display "post it to bugzilla" as well. What do you think?
Yes on the "print myso", not so sure about the bugzilla hint as it could be portage related, package related or texinfo related.
Fixed in CVS
Created attachment 27401 [details, diff] Fixes most (all on my system) 'error'-counts for info-files by suppressing a specific warning Info files with an INFO-DIR-SECTION produce a warning when install-info is run (see /usr/bin/emerge def post_emerge): install-info: warning: no info dir entry in $infofile This warning is harmless and this patch suppreses them. The infofiles are created and $info $infofile will work. The only drawback is that $infofile isn't included in the default 'dir'-file. To fix this the info-files should be patched upstream I guess...
Created attachment 27689 [details] Testprogram to (re)generate the infofile with the patch from the previous entry. You can run this file to see the 'errors' produced by regenerating the infofiles. You can also run it with the -p option to include the patch in the test to see the difference. It is the same source as 'emerge' but stripped of everything not related to the infofiles. In addition it prints a comment for every infodir that is being processed and it removes duplicates that don't normally occur (is taken care of by some code I took). On my system this produces: bash-2.05b# python infotest.py * Processing infodir: /usr/share/info . install-info: warning: no info dir entry in `/usr/share/info/jed.1in.gz' install-info: warning: no info dir entry in `/usr/share/info/jed.2in.gz' install-info: warning: no info dir entry in `/usr/share/info/jed.3in.gz' install-info: warning: no info dir entry in `/usr/share/info/libcdio.info.gz' * Processing infodir: /usr/share/gcc-data/i686-pc-linux-gnu/3.3/info . * Processed 278 info files; 4 errors. bash-2.05b# python infotest.py -p * Processing infodir: /usr/share/info . * Processing infodir: /usr/share/gcc-data/i686-pc-linux-gnu/3.3/info . * Processed 278 info files. bash-2.05b#
Fixed again.
Bug has been fixed and released in stable portages on or before 2.0.51-r2
