Description of problem: I installed gdb-doc from yum. After installing, 'info gdb' brought up the 'gdbm' node. Only after running: sudo /sbin/install-info /usr/share/info/gdb.info-1.gz /usr/share/info/dir did 'info gdb' bring up the correct GDB node. The gdb.spec has the 'install-info' command, so not sure what is happening. Maybe some side effect from the recent gdb-doc sub-package changes? Version-Release number of selected component (if applicable): rpm -q gdb-doc gdb-doc-7.2.90.20110525-38.fc15.noarch rpm -q gdb gdb-7.2.90.20110525-38.fc15.x86_64 How reproducible: On install Steps to Reproduce: 1. yum install gdb-doc 2. info gdb 3. Actual results: GDB info nodes are not searchable from 'info'. Expected results: 'info gdb', and 'info' searches should find GDB nodes, not GDBM Additional info:
gdb-7.2.90.20110525-39.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/gdb-7.2.90.20110525-39.fc15
Package gdb-7.2.90.20110525-39.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gdb-7.2.90.20110525-39.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/gdb-7.2.90.20110525-39.fc15 then log in and leave karma (feedback).
(In reply to comment #2) > Package gdb-7.2.90.20110525-39.fc15: > * should fix your issue, > * was pushed to the Fedora 15 testing repository, > * should be available at your local mirror within two days. > Update it with: > # su -c 'yum update --enablerepo=updates-testing gdb-7.2.90.20110525-39.fc15' > as soon as you are able to. > Please go to the following url: > https://admin.fedoraproject.org/updates/gdb-7.2.90.20110525-39.fc15 > then log in and leave karma (feedback). Proventester found that package above fixed this issue karma added also
gdb-7.2.90.20110525-39.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.