Description of problem: mx4j (... and numerous other java packages supplied by Redhat) depends on java-gcj-compat. However, as far as I can see, java-gcj-compat is only provided by java-1.5.0-gcj, which is very flaky (frequently segfaults, for example when starting jboss). So, when doing an "yum install jbossas", jboss (jpackage) will pull in jettison (jpackage), which in turns pulls in jetty5 (jpackage), which pulls in mx4j (Fedora), which in turn pulls in the broken java-1.5.0-gcj . The problem is not limited to mx4j, but shared with 36 other Fedora packages, all pulled in by jbossas. What is especially ironic is the Description shown by rpm -q --info java-1.5.0-gcj "This package installs directory structures, shell scripts and symbolic links to simulate a JPackage-compatible runtime environment with GCJ." However, in reality, it breaks jpackage. Why can't Fedora leave jpackage alone? (I'm reminded here of an older issue around the /usr/bin/rebuild-security-providers script...) Why does Fedora's mx4j take precedence over jpackage's? Version-Release number of selected component (if applicable): mx4j-3.0.1-8.9.fc11.i586 java-1.5.0-gcj-1.5.0.0-28.fc11.i586 How reproducible: Always Steps to Reproduce: 1. Install Fedora 11 2. Add jpackage.repo 3. yum install jbossas 4. /etc/init.d/jbossas start Actual results: After a while, Jboss crashes. /var/log/jbossas/console.log shows a segfault. Manually pointing JAVA_HOME in /etc/sysconfig/jbossas to a non-broken JDK (such as java-1.6.0-openjdk) avoids that segfault. Another workaround is to repoint the link /etc/alternatives/java_sdk to a non-broken JDK. Expected results: - yum install jbossas should pull in a JDK that is compatible with JBoss. - If both a jpackage and a Fedora package are available, the jpackage package should be preferred (when pulled in during the install of another package which is in jpackage) - Java packages (such as mx4j) should require "java" (or "jre") in general, and not a specific implementation (such as gcj) Additional info:
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Problem still exists in Fedora 12
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is still an issue in Fedora13. Not with package m4j (which no longer exists), but with loads of other java packages (tried by attempting to install jboss4 from jpackage on a virgin Fedora 13)
Even in Fedora 14, this still seems to be an issue (install of jbossas pulls in java-gcj-compat) --> Processing Dependency: java-gcj-compat for package: concurrent-1.3.4-11.fc12.i686 It even seems to have gotten worse: previously, this could have been prevented by installing java-1.6.0-openjdk-devel manually before installing jbossas, but now this workaround only keeps away java-gcj-compat-devel, but not java-gcj-compat Now, the workaround is more tricky: yum install msv-msv [disable fedora repository] yum install jbossas [re-enable fedora repository] ... but the downside of this is that it will make any subsequent yum update fail with the following error: file /usr/share/java/commons-logging-adapters.jar from install of apache-commons-logging-1.1.1-11.fc14.noarch conflicts with file from package jakarta-commons-logging-0:1.1-8.jpp5.noarch
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping