FS#42625 - [mono-tools] monodoc.xml file not found.

Attached to Project: Arch Linux
Opened by William McKIE (VIPRIP) - Thursday, 30 October 2014, 16:31 GMT
Last edited by Isenmann Daniel (ise) - Sunday, 18 January 2015, 16:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Isenmann Daniel (ise)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
Hello,

When I launch monodoc executable an exception is thrown. Because it can't find monodoc.xml inside the /usr/lib/monodoc directory.

Additional info:
mono-tools 2.11-1

Unhandled Exception:
System.IO.FileNotFoundException: Could not find file "/usr/lib/monodoc/monodoc.xml".
File name: '/usr/lib/monodoc/monodoc.xml'
...

Steps to reproduce:
Just simply launch monodoc executable.
This task depends upon

Closed by  Isenmann Daniel (ise)
Sunday, 18 January 2015, 16:38 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed this in package release 2. Should be available on your mirror soon. The mixing of the provide flags will be fixed in the next release.
Comment by smmilut (smmilut) - Wednesday, 03 December 2014, 19:58 GMT
Hello,

I confirm have had this problem for a few months with previous versions, and still today with mono-tools 3.10-1 (reinstalling all mono-related packages did not help).

The full exception text is at http://pastie.org/9758846 (thrown when calling "monodoc"). Essentially, the file "/usr/lib/monodoc/monodoc.xml" is missing.
Directly calling "/usr/bin/mono /usr/lib/monodoc/browser.exe" throws the same exception.

The upstream tarball as of today ( http://download.mono-project.com/sources/mono/mono-3.10.0.tar.bz2 ) does contain a file named "mono-3.10.0/mcs/docs/monodoc.xml".
Sadly, my lack of knowledge of the mechanisms involved prevents me from analysing why our package doesn't contain or generate such a file.

Thanks for any help
Comment by lenidh (lenidh) - Thursday, 04 December 2014, 11:02 GMT
Hi,

the tarball of "mono-tools" repository used to build this package doesn't contain monodoc.xml. monodoc.xml is part of the "mono" repository (https://github.com/mono/mono/blob/master/mcs/docs/monodoc.xml).
Comment by smmilut (smmilut) - Saturday, 06 December 2014, 09:22 GMT
Hi,

The PKGBUILD for mono 3.10.0 says it provides monodoc, but does not contain the monodoc binary. The tarball it uses as a source does contain a "monodoc.xml" file (probably the one we miss).
The PKGBUILD for mono-tools 3.10 doesn't contain provides=('monodoc'), but does contain the /usr/bin/monodoc binary. The tarball it uses as a source does not contain the "monodoc.xml" file.

Something seems wrong in the way the packages are split, but i'm too ignorant of the build process and the making of a package to provide a solution.

Thanks for any further help
Comment by Isenmann Daniel (ise) - Saturday, 06 December 2014, 15:53 GMT
Thanks for the information. I will have a look into that these days. Maybe they have changed their source packages.
Comment by ResXaoC (ResXaoC) - Monday, 05 January 2015, 01:17 GMT
You may create it manualy, with these content:

<?xml version="1.0"?>
<node label="Mono Documentation" name="libraries">
<node label="Commands and Files" name="man" />
<node label="Languages" name="languages" />
<node label="Tools" name="tools" />
<node label="Various" name="various" />
</node>

Loading...