Bug 1160660 - [rpm][el5] Unsatisfied dependencies for tomcat6-maven-devel
Summary: [rpm][el5] Unsatisfied dependencies for tomcat6-maven-devel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: JBoss Enterprise Web Server 2
Classification: JBoss
Component: tomcat6, tomcat7
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: David Knox
QA Contact: Michal Haško
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-05 10:42 UTC by Michal Haško
Modified: 2015-11-02 00:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-11 13:25:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1842 0 normal SHIPPED_LIVE Red Hat JBoss Web Server additional packages 2014-11-11 18:24:59 UTC

Description Michal Haško 2014-11-05 10:42:03 UTC
Description of problem:
It's not possible to install tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch.rpm because it has unsatisfied dependencies:

error: Failed dependencies:
	tomcat6-annotations-api = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-api = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-catalina = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-catalina-ant = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-coyote = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-i18n-es = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-i18n-fr = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-i18n-ja = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-jasper = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-jasper-el = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-jdbc = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-juli = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch
	tomcat6-util = 0:6.0.41-8_patch_02.ep6.el5 is needed by tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5.noarch

I believe this is caused by missing "Provides:" statements for tomcat6-lib in tomcat6.spec

From tomcat6.spec from el6 tomcat6-6.0.41-6_patch_02.ep6.el6.src.rpm:

    %package lib
    Provides: %{name}-annotations-api = %{epoch}:%{version}-%{release}
    Provides: %{name}-api = %{epoch}:%{version}-%{release}
    Provides: %{name}-catalina-ant = %{epoch}:%{version}-%{release}
    Provides: %{name}-catalina = %{epoch}:%{version}-%{release}
    Provides: %{name}-coyote = %{epoch}:%{version}-%{release}
    Provides: %{name}-i18n-es = %{epoch}:%{version}-%{release}
    Provides: %{name}-i18n-fr = %{epoch}:%{version}-%{release}
    Provides: %{name}-i18n-ja = %{epoch}:%{version}-%{release}
    Provides: %{name}-jasper-el = %{epoch}:%{version}-%{release}
    Provides: %{name}-jasper = %{epoch}:%{version}-%{release}
    Provides: %{name}-jdbc = %{epoch}:%{version}-%{release}
    Provides: %{name}-juli = %{epoch}:%{version}-%{release}
    Provides: %{name}-util = %{epoch}:%{version}-%{release}

There is no such code in tomcat6.spec on el5 tomcat6-6.0.41-8_patch_02.ep6.el5.src.rpm

Version-Release number of selected component (if applicable):
tomcat6-maven-devel-6.0.41-8_patch_02.ep6.el5

Comment 3 errata-xmlrpc 2014-11-11 13:25:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2014-1842.html


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