apidocs page seems broken

Ben Cooksley bcooksley at kde.org
Mon Feb 8 09:45:54 UTC 2016

On Mon, Feb 8, 2016 at 1:29 PM, Valorie Zimmerman
<valorie.zimmerman at gmail.com> wrote:
> On Sun, Feb 7, 2016 at 2:56 PM, Albert Astals Cid <aacid at kde.org> wrote:
>> Someone on irc said
>> <david_ka> All the links on http://api.kde.org/frameworks-api/frameworks5-apidocs/ are failing for me with a "Not Found" error
>> Cheers,
>>   Albert
> I can confirm that the links are all broken.

>From the server:

22:08:31 INFO Generating dependency diagram
Traceback (most recent call last):
  File "/home/api/kapidox/src/kgenframeworksapidox", line 411, in <module>
  File "/home/api/kapidox/src/kgenframeworksapidox", line 384, in main
    ok = generate_diagram(png_path, fwinfo['fancyname'], t, dot_files, tmp_dir)
  File "/home/api/kapidox/src/kgenframeworksapidox", line 181, in
    ok = depdiagram.generate(f, dot_files, framework=fancyname, with_qt=with_qt)
  File "/home/api/kapidox/src/kapidox/depdiagram/generate.py", line
157, in generate
    db.populate(dot_files, with_qt=with_qt)
  File "/home/api/kapidox/src/kapidox/depdiagram/frameworkdb.py", line
166, in populate
    with open(yaml_file) as f:
IOError: [Errno 2] No such file or directory:

Someone fix KDeclarative please (something in the CMake magic
generates that file), and kapidox needs hardening against improper
setup of Frameworks.
This should also have been caught in the review process!

This is far from the first time that improper metadata has broken the
API Documentation generation requiring sysadmin to look into this.

> Valorie


> _______________________________________________
> kde-www mailing list
> kde-www at kde.org
> https://mail.kde.org/mailman/listinfo/kde-www

More information about the Plasma-devel mailing list