Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#1885 - monodoc update problem
Attached to Project:
Arch Linux
Opened by Viktor Peters (Mythoz) - Friday, 10 December 2004, 08:53 GMT
Last edited by Dale Blount (dale) - Friday, 10 December 2004, 13:11 GMT
Opened by Viktor Peters (Mythoz) - Friday, 10 December 2004, 08:53 GMT
Last edited by Dale Blount (dale) - Friday, 10 December 2004, 13:11 GMT
|
Details[...]
upgrading monodoc... done. creating index ... this could take a while... /bin/sh: line 3: monodoc: command not found update desktop mime database... |
This task depends upon
Closed by Tobias Kieslich (tobias)
Thursday, 30 December 2004, 20:47 GMT
Reason for closing: Works for me
Additional comments about closing: no more complaints and i wasn't able to reproduce the error
Thursday, 30 December 2004, 20:47 GMT
Reason for closing: Works for me
Additional comments about closing: no more complaints and i wasn't able to reproduce the error
which does mean it is running it after monodoc has been installed and the
binaries should be in place. So the crystall ball service starts here:
- did monodoc worked b4 and post the upgrade at all? (just call monodoc from console)
- after the actual installation of mono, did you relogin to export the pathes in /opt/mono (... where also monodoc sits?)
I just tried and it works for me.