Bug 1161959 - Devhelp function search broken by incompatible gtk-doc
Summary: Devhelp function search broken by incompatible gtk-doc
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: devhelp
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-09 20:47 UTC by David Nečas
Modified: 2015-06-29 23:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 23:13:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description David Nečas 2014-11-09 20:47:20 UTC
Description of problem:
Search in devhelp became useless for gtk2, gtk3, ... because the HTL documentation of these packages is generated with an incompatible gtk-doc version.  Hence devehelp does not understand the foo.devehelp2 files.


Version-Release number of selected component (if applicable):
gtk-doc-1.19-4.fc20
devhelp-3.10.2-1.fc20
gtk2-devel-docs-2.24.24-2.fc20


How reproducible:
Always.


Steps to Reproduce:
1. Run devhelp.
2. Type Ctrl-K to get to the search bar.
3. Type gtk_tree_view_new.
4. Press Enter.


Actual results:
Function is not found.


Expected results:
Function is found and its documentation displayed.


Additional info:
The same problems is, of course, encountered also in the live list of matching symbols when you type a partial name such as gtk_tree_.  But typing the exact function name makes the reproduction clearer.

I am not sure which package this should be reported to because:

- develp actually works, it only gets documentation in format this version does
  not understand yet

- gtk-doc 1.19 *in Fedora* produces usable documentation -- but gtk-doc 1.19
  from Fedora is NOT what the documentation is generated with

So maybe the problem is that the build process of gtk2, gtk3, ... does not ensure HTML documentation is re-generated with a compatible gtk-doc version.

This is similar to bug 1090204.  In fact, I predicted these things would happen...

Comment 1 David Nečas 2014-11-09 20:50:52 UTC
The difference between the good and bad .devhelp2 files seems that one uses space between function_name and (), while the other uses U+00A0.

Comment 2 Fedora End Of Life 2015-05-29 13:15:37 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-29 23:13:41 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.