Bug 144665 - eclipse-rpm documentation missing screenshots
Summary: eclipse-rpm documentation missing screenshots
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: eclipse   
(Show other bugs)
Version: 3.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: eclipse-bugs
QA Contact: eclipse-bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2005-01-10 14:31 UTC by Paul A. Kennedy
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 19:09:37 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Paul A. Kennedy 2005-01-10 14:31:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.3)

Description of problem:
The documentation for the RPM Manipulation Plugin is incomplete. 
Screenshots in the HTML docs refer to pictures that do not seem to
exist on the system anywhere (a 'locate 01_eclipse_rpm_prefs_page.png'
produces no output).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Select 'Help' from the main menubar
2. Select 'Help Contents' from the menu
3. At the browser, select 'RPM Developer's Guide'
4. Note that the page has broken links for all the screenshots.   

Actual Results:  A page with text and broken links for the screenshots
was displayed

Expected Results:  I expected text and screenshots.

Additional info:

Comment 1 RHEL Product and Program Management 2007-10-19 19:09:37 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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