Bug 855370 - RPM installation - incorrect channels provided
Summary: RPM installation - incorrect channels provided
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Web Server 2
Classification: JBoss
Component: doc-Installation-Guide
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: gsheldon
QA Contact: Ondrej Chaloupka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-07 14:25 UTC by Ondrej Chaloupka
Modified: 2012-11-08 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-08 22:10:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ondrej Chaloupka 2012-09-07 14:25:22 UTC
Information on RPM channels that should be used for RPM installation in installation guide:
http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Web_Server/2/html-single/Installation_Guide/index.html#sec-Installing_EWS_from_RPM_Packages

is out-dated. It invites to install EWS2 from:

on Red Hat Enterprise Linux 6:
    jb-ews-1-i386-server-6-rpm
    jb-ews-1-x86_64-server-6-rpm 
on Red Hat Enterprise Linux 5:
    jb-ews-1-i386-server-5-rpm
    jb-ews-1-x86_64-server-5-rpm 

I suppose that it should be jb-ews-2-*

how was agreed here
https://docspace.corp.redhat.com/docs/DOC-108784#comment-42391

Comment 1 gsheldon 2012-09-11 04:21:12 UTC
I am in the process of changing rpm package names in CCMS version of the Installation Guide book.

Will follow this up with Misha when she has returned from PTO.

Comment 2 gsheldon 2012-09-19 02:15:04 UTC
RPM package names have been changed in svn repo version. Will set to On_QA when available on the stage.

Comment 4 Ondrej Chaloupka 2012-09-20 07:06:14 UTC
Hi,
thank you for the change. The documentation is fine at this point, I think.

Comment 5 Misha H. Ali 2012-09-25 23:24:08 UTC
Ondrej, sorry, I'm not sure why this bug is set to closed upstream. Generally docs bugs will be set to VERIFIED by the QE person to confirm that the changes are correct, after which they are set for the next release by docs. I'm switching to to verified in line with c#4, if there was a specific reason for setting it to CLOSED, please let me know.

Comment 6 Ondrej Chaloupka 2012-09-26 05:53:00 UTC
Aj, ok, thank you. That was my mistake. 
I wasn't sure what is the correct workflow for documentation bugs in bugzilla. I asked few folks here and they proposed me to close it what was incorrect action. Next time I'll already know.

Comment 7 Misha H. Ali 2012-11-08 22:10:32 UTC
This bug is set to CLOSED CURRENT RELEASE to indicate that this fix is now released and available at access.redhat.com.


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