After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 789017 - Glibmm 2.54.1 API docs are empty
Glibmm 2.54.1 API docs are empty
Status: RESOLVED OBSOLETE
Product: website
Classification: Infrastructure
Component: developer.gnome.org
current
Other All
: Normal normal
: ---
Assigned To: GNOME Web maintainers
GNOME Web maintainers
Depends on:
Blocks: 788082 793891
 
 
Reported: 2017-10-15 14:36 UTC by Kjell Ahlstedt
Modified: 2018-09-24 10:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kjell Ahlstedt 2017-10-15 14:36:13 UTC
https://developer.gnome.org/glibmm/2.54/ and .../stable/ show only a header and
a footer, but no information from the index.html file in glibmm-2.54.1.tar.xz.

Bug 787630 reports a similar problem with gedit's documentation, but there is an
important difference: The documentation in gedit-3.22.1.tar.xz is affected in
the same way as the information at https://developer.gnome.org/gedit/3.22/, i.e.
https://developer.gnome.org/gedit/3.22/ reflects what's in gedit-3.22.1.tar.xz.
On the other hand, the documentation in glibmm-2.54.1.tar.xz is complete, but
it's not shown at https://developer.gnome.org/glibmm/2.54/.

See also glibmm bug 788082, especially comment 3 where I have speculated on a
possible cause.
Comment 1 Kjell Ahlstedt 2018-03-04 08:10:16 UTC
Now the same issue has occurred with
https://developer.gnome.org/glibmm/2.55/
https://developer.gnome.org/gtkmm/3.93/
https://developer.gnome.org/libsigc++/2.99/

The documentation for glibmm 2.54.1. glibmm 2.55.2, gtkmm 3.93.0 and
libsigc++ 2.99.10 have all been generated with Doxygen 1.8.13.
Comment 2 Kjell Ahlstedt 2018-03-07 18:27:24 UTC
pangomm 2.41.5 at https://developer.gnome.org/pangomm/2.41/ is also affected.

atkmm 2.27.1 at https://developer.gnome.org/atkmm/2.27/ is interesting.
Its documentatiom is also generated with Doxygen 1.8.13, but it looks different.
It looks ugly, but the information that should be there, is there. There's a
difference in the CSS files between atkmm 2.27.1 and the other mentioned
modules. Atkmm 2.27.1 does not contain Doxygen's ordinary doxygen.css file. It
has (by mistake, I would say) been replaced by a file that comes from mm-common
and resembles the doxygen-extra.css file in the other modules.

Interestingly, the html files at for example
https://developer.gnome.org/glibmm/2.55/ link to a doxygen.css file at
https://developer.gnome.org/skin/doxygen.css, which differs from Doxygen's
doxygen.css file. The html files at https://developer.gnome.org/atkmm/2.27/
don't link to this file.
Is it possible that https://developer.gnome.org/skin/doxygen.css is
incompatible with the html files that Doxygen 1.8.13 generate?
Comment 3 Tobias Schmidl 2018-07-10 19:11:30 UTC
This also affects gstreamermm: https://developer.gnome.org/gstreamermm/ , for all versions.
Comment 4 GNOME Infrastructure Team 2018-09-24 10:58:23 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/Infrastructure/Websites/issues/236.