Description of problem: Attempting to build with newest xmvn in F20 results in the following error: Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.0GXgTS + umask 022 + cd /home/fedora/rpmbuild/BUILD + cd hadoop-common-b92d9bcf559cc2e62fc166e09bd2852766b27bec + python /usr/share/java-utils/mvn_build.py -- -Drequire.snappy=true -Dcontainer-executor.conf.dir=/etc/hadoop -Pdist,native -DskipTests -DskipTest -DskipIT java.io.FileNotFoundException: /usr/share/xmvn/conf/logging at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.parse(ConfigurationParser.java:264) at org.codehaus.plexus.classworlds.launcher.Configurator.configure(Configurator.java:133) at org.codehaus.plexus.classworlds.launcher.Launcher.configure(Launcher.java:131) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) error: Bad exit status from /var/tmp/rpm-tmp.0GXgTS (%build) Version-Release number of selected component (if applicable): xmvn-1.1.0-1 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Are you still able to reproduce this problem? I can see from output that you tried to build hadoop locally, without mock. I tried to install xmvn-1.1.0-1 in F20 mock and it failed from different reason (ClassNotFoundException: com.google.inject.Module), but current combination of javapackages-tools-3.3.1-1 and xmvn-1.1.0-2 seems to work. http://koji.fedoraproject.org/koji/taskinfo?taskID=6040387
xmvn-1.1.0-2 doesn't seem to exhibit the problem.
Thanks. Marking as fixed.
Just to note, a full reinstall of the package is required. a `yum update` still fails.
Reopening for investigation. This is most likely a %pretrans scriptlet problem
Hi Timothy, could you please paste the error message from `yum update` here? Thanks.
There is no error in 'yum update', it's an upgrade of a package has a missing directory structure. It complains about the same missing directory structure: /usr/share/xmvn/conf/logging which only appears to be created on a fresh install.
OK, here's how to reproduce it: $ rpm -q maven xmvn maven-3.1.0-3.fc20.noarch xmvn-0.5.1-4.fc20.noarch # rpm -e --nodeps maven # yum install maven-3.1.0-3.fc20.noarch.rpm xmvn-1.1.0-2.fc20.noarch.rpm $ rpm -V xmvn missing /usr/share/xmvn/conf/logging/simplelogger.properties
Confirmed. Another reproducer that does not need removing maven: # rpm -q maven xmvn maven-3.1.0-3.fc20.noarch xmvn-0.5.1-4.fc20.noarch # rpm -V maven xmvn # rpm -U maven-3.1.0-3.fc20.noarch.rpm xmvn-1.1.0-2.fc20.noarch.rpm --force # rpm -V maven xmvn missing /usr/share/xmvn/conf/logging/simplelogger.properties
This is urgent as it breaks upgrade path from Fedora 19 to Fedora 20. We are working on developing a proper fix. For now users reinstall xmvn to workaround this bug. # rpm -V xmvn missing /usr/share/xmvn/conf/logging/simplelogger.properties # rpm -U xmvn-1.1.0-2.fc20.noarch.rpm --force # rpm -V xmvn
Fixed in xmvn-1.2.0-5
I believe that this bug is fixed in xmvn-1.3.0-2, which is available in Fedora 20, so I am closing this bug now. The build containing the fix can be found at Koji: http://koji.fedoraproject.org/koji/buildinfo?buildID=478073