I was able solve it. I will share the rpms as soon as i get the installation working. Den den 9 mars 2012 13:56:48 skrev Elias Abacioglu:
I have gotten to this point during the RPM build process:
[INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] org.apache.maven.shared.io.location.ArtifactLocatorStrategy.<init>(Lorg/apache/maven/artifact/factory/ArtifactFactory;Lorg/apache/maven/artifact/resolver/ArtifactResolver;Lorg/apache/maven/artifact/repository/ArtifactRepository;Ljava/util/List;Ljava/lang/String;Ljava/lang/String;)V [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.NoSuchMethodError: org.apache.maven.shared.io.location.ArtifactLocatorStrategy.<init>(Lorg/apache/maven/artifact/factory/ArtifactFactory;Lorg/apache/maven/artifact/resolver/ArtifactResolver;Lorg/apache/maven/artifact/repository/ArtifactRepository;Ljava/util/List;Ljava/lang/String;Ljava/lang/String;)V at org.apache.maven.plugin.assembly.io.DefaultAssemblyReader.readAssemblies(DefaultAssemblyReader.java:102) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:296) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1 minute 47 seconds [INFO] Finished at: Fri Mar 09 12:50:16 CET 2012 [INFO] Final Memory: 237M/834M [INFO] ------------------------------------------------------------------------ make: *** [build_mvn] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.95OcZi (%install)
RPM build errors: Bad exit status from /var/tmp/rpm-tmp.95OcZi (%install)
Chris Brown had a similar issue. http://www.mail-archive.com/users@ovirt.org/msg00078.html His solution was to run maven 2.2. But the problem is that I do.
[elab@virtual SPECS]$ mvn -v /usr/lib/jvm/java Apache Maven 2.2.1 (rNON-CANONICAL_2011-10-17_20-32_mockbuild; 2011-10-17 21:32:08+0200) Java version: 1.6.0_22 Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux" version: "2.6.32-220.7.1.el6.x86_64" arch: "amd64" Family: "unix"
Any ideas now?
2012/3/9 Elias Abacioglu <elias.rabi@gmail.com <mailto:elias.rabi@gmail.com>>
> > Trey, did you have a Python 2.7 RPM or SRPM for EL6?
Where do you see the Python 2.7 dependency? Running a rebuild with no changes on the latest SPEC gives me this ...
Maybe you are right.. I was just blinded by the fact that the ovirt-engine rpms needed 2.7.. So that is probably not needed after I have rebuilt ovirt rpms.
# rpmbuild -ba --define 'dist .el6' --define 'rhel 6' ovirt-engine.spec <snip> + make PREFIX=/builddir/build/BUILDROOT/ovirt-engine-3.0.0_0001-1.6.el6.x86_64/ install which: no mvn in (/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/builddir/bin) export MAVEN_OPTS="-XX:MaxPermSize=512m" install -P gwt-admin,gwt-user -D skipTests install: WARNING: ignoring --preserve-context; this kernel is not SELinux-enabled install: cannot stat `gwt-admin,gwt-user': No such file or directory make: *** [build_mvn] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.oHg34r (%install)
I think it requires maven 2.2. There is a maven 2.2 in jpackage 6.0. But it got a broken dependency. I tried compiling with maven 2.0 and that failed.