Package: monodoc-http
Version: 4.2-2
Tags: stretch, buster
This bug affects at least stretch and buster. I've not tested sid yet.
Quoting from my similar bug in Ubuntu's Launchpad Issue Tracker
(https://bugs.launchpad.net/ubuntu/+source/mono-tools/+bug/1811444):
The out-of-the-box configuration for monodoc-http does not find any
documentation. It is configured to look for documentation at
/mono/lib/monodoc-ios/ and reports an HTTP 500 error when trying to
navigate to http://localhost:8084/monodoc.
----
System.ArgumentException
basedir
Parameter name: Base documentation directory at '/mono/lib/monodoc-ios/'
doesn't exist
Description: HTTP 500.Error processing request.
Details: Non-web exception. Exception origin (name of application or
object): monodoc.
Exception stack trace:
at Monodoc.RootTree.LoadTree (System.String basedir, System.Boolean
includeExternal) [0x00031] in <496c0b0510da4601a8fa1704154167ef>:0
at Mono.Website.Global.Application_Start () [0x0002d] in
<b585f8eef00841eab80ae6a6ea48bfd2>:0
at (wrapper managed-to-native)
System.Reflection.MonoMethod:InternalInvoke
(System.Reflection.MonoMethod,object,object[],System.Exception&)
at System.Reflection.MonoMethod.Invoke (System.Object obj,
System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder
binder, System.Object[] parameters, System.Globalization.CultureInfo
culture) [0x00038] in <8f2c484307284b51944a1a13a14c0266>:0
----
Should the documentation path be changed? what to? Should we change
monodoc-http to ensure it depends upon an appropriate documentation
package to provide the path that the server is configured to serve? Or
should we do both?
