Bug 192565 - tomcat5 fails to build in mock
Summary: tomcat5 fails to build in mock
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: tomcat5
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Rafael H. Schloming
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: BuildReqBlocker
TreeView+ depends on / blocked
 
Reported: 2006-05-20 19:56 UTC by Michael J Knox
Modified: 2014-12-01 23:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-06-25 04:19:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Matt Domsch's root.log (11.52 KB, text/plain)
2006-05-20 19:56 UTC, Michael J Knox
no flags Details

Description Michael J Knox 2006-05-20 19:56:24 UTC
This package fails to build in mock.  root.log is attached.

Executing /usr/sbin/mock-helper yum --installroot
/var/lib/mock/fedora-development-x86_64-core-tomcat5-5.5.15-1jpp_6fc.src.rpm/root
resolvedep  'jakarta-commons-collections >= 0:3.1' 'xml-commons-apis >= 1.3'
'javamail >= 0:1.3.1' 'jsse >= 0:1.0.3' 'mx4j >= 0:3.0.1' 'struts >= 0:1.2.7'
'java-gcj-compat-devel >= 1.0.43' 'jndi-ldap' 'ant-trax' 'ant >= 0:1.6.2'
'jpackage-utils >= 0:1.6.0' 'jaf >= 0:1.0.1' 'jakarta-commons-modeler >= 1.1'
'junit >= 0:3.8.1' 'jakarta-taglibs-standard >= 0:1.1.0'
'jakarta-commons-logging >= 0:1.0.4' 'xerces-j2 >= 0:2.7.1' 'jndi >= 0:1.2.1'
'jakarta-commons-fileupload >= 0:1.0' 'jaas' 'jakarta-commons-pool >= 0:1.2'
'jakarta-commons-el >= 0:1.0' 'regexp >= 0:1.3' 'eclipse-ecj >= 0:3.0.2'
'jakarta-commons-daemon >= 1.0' 'jakarta-commons-dbcp >= 0:1.2.1' 'xalan-j2'
'jakarta-commons-launcher >= 0:0.9' 'jta >= 0:1.0.1' 'jakarta-commons-digester
>= 0:1.7' 'jakarta-commons-beanutils >= 1.7' 'jdbc-stdext >= 0:2.0'
No Package Found for jdbc-stdext >= 0:2.0

Comment 1 Michael J Knox 2006-05-20 19:56:24 UTC
Created attachment 129767 [details]
Matt Domsch's root.log

Comment 2 Michael J Knox 2006-06-25 04:19:22 UTC
Now builds in mock. 


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