Bug 550144 - gtk-sharp2-doc does not show up in Monodoc
Summary: gtk-sharp2-doc does not show up in Monodoc
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk-sharp2
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-23 18:25 UTC by Lester
Modified: 2010-04-20 13:33 UTC (History)
5 users (show)

Fixed In Version: gtk-sharp2-2.12.10-2.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of: 481182
Environment:
Last Closed: 2010-04-20 13:18:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Lester 2009-12-23 18:25:28 UTC
Due to the presence of this bug in the latest fedora spin, I think someone should clone it as only the maintainer can change its status.

+++ This bug was initially created as a clone of Bug #481182 +++

Description of problem:

The Gtk# documentation does not show up in the monodoc browser.

Version-Release number of selected component (if applicable):
gtk-sharp2-doc-2.12.7-1.fc10.1.i386
monodoc-2.0-5.fc10.i386

Steps to Reproduce:
1. Install gtk-sharp2-doc
2. Start Monodoc
3. See this console-output:

Loading uncompiled help from /usr/lib/monodoc/sources/gtk-sharp-docs
Error: did not find one of the files in sources//usr/lib/monodoc/sources/gtk-sharp-docs
  
Actual results:


Expected results:


Additional info:

--- Additional comment from lester.dev on 2009-08-16 07:18:17 EDT ---

I can confirm, got this problem on my fedora 11 either. Probably we should file a bug in monodoc too, because how should one find out what file is missing if it doesn't give the details? Look through the source? That's ridiculous!

--- Additional comment from fedora-triage-list on 2009-11-18 05:49:55 EDT ---


This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from craftjml on 2009-11-27 21:53:23 EDT ---

This bug is still a problem in Fedora 12 and gtk-sharp2-doc 2.12.9.1.fc12.

That is, GTK# documentation does not show up in monodoc or MonoDevelop/Help.

--- Additional comment from fedora-triage-list on 2009-12-18 02:40:35 EDT ---


Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

--- Additional comment from craftjml on 2009-12-23 12:26:22 EDT ---

I repeat, still a problem in Fedora 12.  I have no idea how to reopen this bug as a non-maintainer.

Comment 1 Paul Lange 2010-01-17 17:30:07 UTC
Would be nice if this bug could be fixed.

Comment 2 Christian Krause 2010-04-05 21:51:43 UTC
(In reply to comment #1)
> Would be nice if this bug could be fixed.    

Bug fix is committed in CVS, new packages will be in updates-testing soon...

Comment 3 Fedora Update System 2010-04-05 21:53:47 UTC
gtk-sharp2-2.12.10-2.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/gtk-sharp2-2.12.10-2.fc13

Comment 4 Fedora Update System 2010-04-05 22:02:51 UTC
gtk-sharp2-2.12.10-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/gtk-sharp2-2.12.10-2.fc12

Comment 5 Lester 2010-04-06 12:35:09 UTC
Thanks, Christian!

Comment 6 Fedora Update System 2010-04-06 19:58:08 UTC
gtk-sharp2-2.12.10-2.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gtk-sharp2'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gtk-sharp2-2.12.10-2.fc13

Comment 7 Fedora Update System 2010-04-09 01:41:31 UTC
gtk-sharp2-2.12.10-2.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gtk-sharp2'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gtk-sharp2-2.12.10-2.fc12

Comment 8 Fedora Update System 2010-04-20 13:18:12 UTC
gtk-sharp2-2.12.10-2.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2010-04-20 13:33:44 UTC
gtk-sharp2-2.12.10-2.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.