out-of-the-box monodoc-http fails to show documentation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mono-tools (Debian) |
Fix Released
|
Unknown
|
|||
mono-tools (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The out-of-the-box configuration for monodoc-http, which is pulled by installing mono-complete, does not find any documentation. It is configured to look for documentation at /mono/lib/
----
System.
basedir
Parameter name: Base documentation directory at '/mono/
Description: HTTP 500.Error processing request.
Details: Non-web exception. Exception origin (name of application or object): monodoc.
Exception stack trace:
at Monodoc.
at Mono.Website.
at (wrapper managed-to-native) System.
at System.
----
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?
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: monodoc-http 4.2-2.2
ProcVersionSign
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 11 17:06:25 2019
InstallationDate: Installed on 2018-12-13 (28 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitec
SourcePackage: mono-tools
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in mono-tools (Debian): | |
status: | Unknown → New |
Changed in mono-tools (Debian): | |
status: | New → Fix Released |
Also affects xenial, though mono-complete does not install the monodoc-http package as a dependency. I needed to manually install monodoc-http after mono-complete to test whether it failed.