[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738055#comment-13738055
 ] 

shweta agarwal commented on CLOUDSTACK-4081:
--------------------------------------------

now coming to what Frank Suggested

# cd /etc/yum.repos.d/
# wget http://jpackage.org/jpackage50.repo
# yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps 
 installation of it also failed

The output is
[root@d8d1db22-8b6b-4c98-8ecd-77bddf5d9071 yum.repos.d]# yum install tomcat6 
tomcat6-webapps tomcat6-admin-webapps
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * addons: ftp.iitm.ac.in
 * base: ftp.iitm.ac.in
 * extras: ftp.iitm.ac.in
 * jpackage-generic: ftp.heanet.ie
 * jpackage-generic-updates: ftp.heanet.ie
 * updates: ftp.iitm.ac.in
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package tomcat6.noarch 0:6.0.36-1.jpp5 set to be updated
--> Processing Dependency: tomcat6-lib = 6.0.36-1.jpp5 for package: tomcat6
--> Processing Dependency: java for package: tomcat6
--> Processing Dependency: jakarta-commons-logging for package: tomcat6
--> Processing Dependency: jakarta-commons-daemon for package: tomcat6
---> Package tomcat6-admin-webapps.noarch 0:6.0.36-1.jpp5 set to be updated
---> Package tomcat6-webapps.noarch 0:6.0.36-1.jpp5 set to be updated
--> Processing Dependency: jakarta-taglibs-standard >= 1.1 for package: 
tomcat6-webapps
--> Running transaction check
---> Package jakarta-commons-daemon.noarch 1:1.0.1-7.jpp5 set to be updated
---> Package jakarta-commons-logging.noarch 0:1.1-8.jpp5 set to be updated
--> Processing Dependency: jpackage-utils >= 1.7.2 for package: 
jakarta-commons-logging
---> Package jakarta-taglibs-standard.noarch 0:1.1.2-7.jpp5 set to be updated
--> Processing Dependency: tomcat5-jsp-2.0-api >= 5.0.16 for package: 
jakarta-taglibs-standard
--> Processing Dependency: servletapi5 >= 5.0.16 for package: 
jakarta-taglibs-standard
--> Processing Dependency: xalan-j2 >= 2.6.0 for package: 
jakarta-taglibs-standard
---> Package java-1.6.0-openjdk.x86_64 1:1.6.0.0-1.41.1.11.11.90.el5_9 set to 
be updated
--> Processing Dependency: tzdata-java for package: java-1.6.0-openjdk
--> Processing Dependency: libXtst.so.6()(64bit) for package: java-1.6.0-openjdk
--> Processing Dependency: libgif.so.4()(64bit) for package: java-1.6.0-openjdk
---> Package tomcat6-lib.noarch 0:6.0.36-1.jpp5 set to be updated
--> Processing Dependency: tomcat6-servlet-2.5-api = 6.0.36-1.jpp5 for package: 
tomcat6-lib
--> Processing Dependency: tomcat6-el-1.0-api = 6.0.36-1.jpp5 for package: 
tomcat6-lib
--> Processing Dependency: tomcat6-jsp-2.1-api = 6.0.36-1.jpp5 for package: 
tomcat6-lib
--> Processing Dependency: ecj for package: tomcat6-lib
--> Processing Dependency: /usr/share/java/ecj.jar for package: tomcat6-lib
--> Processing Dependency: jakarta-commons-dbcp-tomcat5 for package: tomcat6-lib
--> Processing Dependency: jakarta-commons-collections-tomcat5 for package: 
tomcat6-lib
--> Processing Dependency: jakarta-commons-pool-tomcat5 for package: tomcat6-lib
--> Running transaction check
---> Package ecj.noarch 1:3.3.1.1-3.jpp5 set to be updated
---> Package eclipse-ecj.x86_64 1:3.2.1-19.el5.centos set to be updated
--> Processing Dependency: libgcj >= 4.0.2 for package: eclipse-ecj
--> Processing Dependency: java-gcj-compat >= 1.0.64 for package: eclipse-ecj
--> Processing Dependency: /usr/bin/rebuild-gcj-db for package: eclipse-ecj
--> Processing Dependency: libgcj_bc.so.1()(64bit) for package: eclipse-ecj
---> Package giflib.x86_64 0:4.1.3-7.3.3.el5 set to be updated
---> Package jakarta-commons-collections-tomcat5.x86_64 0:3.2-2jpp.3 set to be 
updated
---> Package jakarta-commons-dbcp-tomcat5.noarch 0:1.2.2-2.jpp5 set to be 
updated
---> Package jakarta-commons-pool-tomcat5.noarch 0:1.3-11.jpp5 set to be updated
---> Package jpackage-utils.noarch 0:5.0.0-2.jpp5 set to be updated
---> Package libXtst.x86_64 0:1.0.1-3.1 set to be updated
---> Package tomcat5-jsp-2.0-api.noarch 0:5.5.27-7.jpp5 set to be updated
---> Package tomcat5-servlet-2.4-api.noarch 0:5.5.27-7.jpp5 set to be updated
---> Package tomcat6-el-1.0-api.noarch 0:6.0.36-1.jpp5 set to be updated
---> Package tomcat6-jsp-2.1-api.noarch 0:6.0.36-1.jpp5 set to be updated
---> Package tomcat6-servlet-2.5-api.noarch 0:6.0.36-1.jpp5 set to be updated
---> Package tzdata-java.x86_64 0:2013c-2.el5 set to be updated
---> Package xalan-j2.noarch 0:2.7.0-10.jpp5 set to be updated
--> Running transaction check
---> Package java-1.4.2-gcj-compat.x86_64 0:1.4.2.0-40jpp.115 set to be updated
--> Processing Dependency: /usr/bin/rebuild-security-providers for package: 
java-1.4.2-gcj-compat
--> Processing Dependency: /usr/bin/rebuild-security-providers for package: 
java-1.4.2-gcj-compat
--> Processing Dependency: gjdoc for package: java-1.4.2-gcj-compat
---> Package libgcj.x86_64 0:4.1.2-54.el5 set to be updated
--> Running transaction check
---> Package gjdoc.x86_64 0:0.7.7-12.el5 set to be updated
--> Processing Dependency: antlr for package: gjdoc
---> Package java-1.4.2-gcj-compat.x86_64 0:1.4.2.0-40jpp.115 set to be updated
--> Processing Dependency: /usr/bin/rebuild-security-providers for package: 
java-1.4.2-gcj-compat
--> Processing Dependency: /usr/bin/rebuild-security-providers for package: 
java-1.4.2-gcj-compat
--> Running transaction check
---> Package antlr.noarch 0:2.7.6-6.jpp5 set to be updated
---> Package java-1.4.2-gcj-compat.x86_64 0:1.4.2.0-40jpp.115 set to be updated
--> Processing Dependency: /usr/bin/rebuild-security-providers for package: 
java-1.4.2-gcj-compat
--> Processing Dependency: /usr/bin/rebuild-security-providers for package: 
java-1.4.2-gcj-compat
--> Processing Dependency: /usr/bin/rebuild-security-providers for package: 
java-1.4.2-gcj-compat
--> Processing Dependency: /usr/bin/rebuild-security-providers for package: 
java-1.4.2-gcj-compat
--> Finished Dependency Resolution
java-1.4.2-gcj-compat-1.4.2.0-40jpp.115.x86_64 from base has depsolving problems
  --> Missing Dependency: /usr/bin/rebuild-security-providers is needed by 
package java-1.4.2-gcj-compat-1.4.2.0-40jpp.115.x86_64 (base)
Error: Missing Dependency: /usr/bin/rebuild-security-providers is needed by 
package java-1.4.2-gcj-compat-1.4.2.0-40jpp.115.x86_64 (base)
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
                        package-cleanup --dupes
       package-cleanup --dupes
                        rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.
[root@d8d1db22-8b6b-4c98-8ecd-77bddf5d9071 yum.repos.d]#


                
> Fresh install of cloud platform failed with dependency errors on centos5.5 OS
> -----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4081
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4081
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Doc, Install and Setup
>    Affects Versions: 4.2.0
>         Environment: centos 5.5 MS host
>            Reporter: shweta agarwal
>            Assignee: Rayees Namathponnan
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Trying to install CloudPlatform-4.2-dbupgrade-56-rhel5.tar.gz build on centos 
> 5.5  OS 
> Installation failing with following dependency error
> --> Finished Dependency Resolution
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
>  You could try using --skip-broken to work around the problem
>  You could try running: package-cleanup --problems
>                         package-cleanup --dupes
>                         rpm -Va --nofiles --nodigest
> The program package-cleanup is found in the yum-utils package.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to