1077909 – maven-release ftbfs due to missing BR for modello

Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1077909 - maven-release ftbfs due to missing BR for modello

Summary: maven-release ftbfs due to missing BR for modello

Keywords:
Status:	CLOSED RAWHIDE
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	maven-release
Sub Component:
Version:	rawhide
Hardware:	All
OS:	Linux
Priority:	unspecified
Severity:	high
Target Milestone:	---
Assignee:	Mikolaj Izdebski
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	F-ExcludeArch-ppc64le, PPC64LETracker
TreeView+	depends on / blocked

Reported:	2014-03-18 19:49 UTC by Brent Baude
Modified:	2014-03-19 07:17 UTC (History)
CC List:	4 users (show)
Fixed In Version:	2.2.1-11
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2014-03-19 07:17:33 UTC
Type:	Bug
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Description Brent Baude 2014-03-18 19:49:06 UTC

Finish: build setup for maven-release-2.2.1-10.fc21.src.rpm
Start: rpmbuild -bb maven-release-2.2.1-10.fc21.src.rpm
DEBUG: Executing command: ['ccache', '-M', '4G'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'CCACHE_DIR': '/tmp/ccache', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'echo -n "<mock-chroot>"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'CCACHE_UMASK': '002'}
DEBUG: Set cache size limit to 4.0 Gbytes
DEBUG: Child return code was: 0
Start: Outputting list of installed packages
DEBUG: Executing command: /usr/bin/repoquery --installroot=/var/lib/mock/fedora-21-ppc64le/root/ -c /tmp/tmpQUaKkG --installed -a --qf '%{nevra} %{buildtime} %{size} %{pkgid} %{yumdb_info.from_repo}' > /var/lib/mock/fedora-21-ppc64le/result/installed_pkgs with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'CCACHE_DIR': '/tmp/ccache', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'echo -n "<mock-chroot>"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'CCACHE_UMASK': '002'}
DEBUG: Child return code was: 0
Finish: Outputting list of installed packages
INFO: ENTER do(['bash', '--login', '-c', 'rpmbuild -bb --target ppc64le --nodeps  builddir/build/SPECS/maven-release.spec'], False, '/var/lib/mock/fedora-21-ppc64le/root/', None, 0, True, False, 1000, 135, None, False, {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'CCACHE_DIR': '/tmp/ccache', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'echo -n "<mock-chroot>"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'CCACHE_UMASK': '002'}, logger=<mockbuild.trace_decorator.getLog object at 0x1002aaa1550>)
DEBUG: Executing command: ['bash', '--login', '-c', 'rpmbuild -bb --target ppc64le --nodeps  builddir/build/SPECS/maven-release.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'CCACHE_DIR': '/tmp/ccache', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'echo -n "<mock-chroot>"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'CCACHE_UMASK': '002'}
DEBUG: Building target platforms: ppc64le
DEBUG: Building for target ppc64le
DEBUG: Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.TYUmeE
DEBUG: + umask 022
DEBUG: + cd /builddir/build/BUILD
DEBUG: + cd /builddir/build/BUILD
DEBUG: + rm -rf maven-release-2.2.1
DEBUG: + /usr/bin/unzip -qq /builddir/build/SOURCES/maven-release-2.2.1-source-release.zip
DEBUG: + STATUS=0
DEBUG: + '[' 0 -ne 0 ']'
DEBUG: + cd maven-release-2.2.1
DEBUG: + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
DEBUG: + echo 'Patch #1 (002-mavenrelease-fixbuild.patch):'
DEBUG: Patch #1 (002-mavenrelease-fixbuild.patch):
DEBUG: + /usr/bin/cat /builddir/build/SOURCES/002-mavenrelease-fixbuild.patch
DEBUG: + /usr/bin/patch -p1 --fuzz=0
DEBUG: patching file maven-release-manager/pom.xml
DEBUG: patching file maven-release-plugin/pom.xml
DEBUG: Patch #2 (003-fixing-migration-to-component-metadata.patch):
DEBUG: + echo 'Patch #2 (003-fixing-migration-to-component-metadata.patch):'
DEBUG: + /usr/bin/cat /builddir/build/SOURCES/003-fixing-migration-to-component-metadata.patch
DEBUG: + /usr/bin/patch -p1 --fuzz=0
DEBUG: patching file maven-release-manager/pom.xml
DEBUG: + echo 'Patch #3 (maven-release-ftbfs.patch):'
DEBUG: Patch #3 (maven-release-ftbfs.patch):
DEBUG: + /usr/bin/cat /builddir/build/SOURCES/maven-release-ftbfs.patch
DEBUG: + /usr/bin/patch -p1 --fuzz=0
DEBUG: patching file maven-release-manager/src/main/mdo/release-descriptor.mdo
DEBUG: + cat
DEBUG: + exit 0
DEBUG: Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.NmGs9r
DEBUG: + umask 022
DEBUG: + cd /builddir/build/BUILD
DEBUG: + cd maven-release-2.2.1
DEBUG: + python /usr/share/java-utils/mvn_file.py :maven-release-manager maven-release-manager
DEBUG: + python /usr/share/java-utils/mvn_file.py :maven-release-plugin maven-release-plugin
DEBUG: + python /usr/share/java-utils/mvn_package.py :maven-release-manager manager
DEBUG: + python /usr/share/java-utils/mvn_package.py :maven-release-plugin plugin
DEBUG: + python /usr/share/java-utils/mvn_build.py -n maven-release -f
DEBUG: [INFO] Scanning for projects...
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] Reactor Build Order:
DEBUG: [INFO] 
DEBUG: [INFO] Maven Release
DEBUG: [INFO] Maven Release Manager
DEBUG: [INFO] Maven Release Plugin
DEBUG: [INFO] 
DEBUG: [INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
DEBUG: [INFO]                                                                         
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] Building Maven Release 2.2.1
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] 
DEBUG: [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ maven-release ---
DEBUG: [INFO]                                                                         
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] Building Maven Release Manager 2.2.1
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] Failed to resolve artifact: org.codehaus.modello:modello-maven-plugin:pom:1.4.1
DEBUG: [WARNING] The POM for org.codehaus.modello:modello-maven-plugin:jar:1.4.1 is missing, no dependency information available
DEBUG: [INFO] Failed to resolve artifact: org.codehaus.modello:modello-maven-plugin:jar:1.4.1
DEBUG: [INFO]                                                                         
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] Skipping Maven Release
DEBUG: [INFO] This project has been banned from the build due to previous failures.
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] Reactor Summary:
DEBUG: [INFO] 
DEBUG: [INFO] Maven Release ..................................... SUCCESS [  3.289 s]
DEBUG: [INFO] Maven Release Manager ............................. FAILURE [  0.015 s]
DEBUG: [INFO] Maven Release Plugin .............................. SKIPPED
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] BUILD FAILURE
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] Total time: 5.647 s
DEBUG: [INFO] Finished at: 2014-03-18T14:48:25-06:00
DEBUG: [INFO] Final Memory: 15M/37M
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [ERROR] Plugin org.codehaus.modello:modello-maven-plugin:1.4.1 or one of its dependencies could not be resolved: Cannot access central (http://repo.maven.apache.org/maven2) in offline mode and the artifact org.codehaus.modello:modello-maven-plugin:jar:1.4.1 has not been downloaded from it before. -> [Help 1]
DEBUG: [ERROR] 
DEBUG: [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
DEBUG: [ERROR] Re-run Maven using the -X switch to enable full debug logging.
DEBUG: [ERROR] 
DEBUG: [ERROR] For more information about the errors and possible solutions, please read the following articles:
DEBUG: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
DEBUG: error: Bad exit status from /var/tmp/rpm-tmp.NmGs9r (%build)
DEBUG: RPM build errors:
DEBUG:     Bad exit status from /var/tmp/rpm-tmp.NmGs9r (%build)
DEBUG: Child return code was: 1
INFO: EXCEPTION: Command failed. See logs for output.
 # ['bash', '--login', '-c', 'rpmbuild -bb --target ppc64le --nodeps  builddir/build/SPECS/maven-release.spec']
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line 70, in trace
    result = func(*args, **kw)
  File "/usr/lib/python2.7/site-packages/mockbuild/util.py", line 376, in do
    raise mockbuild.exception.Error, ("Command failed. See logs for output.\n # %s" % (command,), child.returncode)
Error: Command failed. See logs for output.
 # ['bash', '--login', '-c', 'rpmbuild -bb --target ppc64le --nodeps  builddir/build/SPECS/maven-release.spec']
INFO: LEAVE do --> EXCEPTION RAISED

DEBUG: Executing command: ['/bin/umount', '-n', '/var/lib/mock/fedora-21-ppc64le/root/proc/filesystems'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'}
DEBUG: Child return code was: 0
DEBUG: Executing command: ['/bin/umount', '-n', '/var/lib/mock/fedora-21-ppc64le/root/tmp/ccache'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'}
DEBUG: Child return code was: 0
DEBUG: Executing command: ['/bin/umount', '-n', '/var/lib/mock/fedora-21-ppc64le/root/var/cache/yum'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'}
DEBUG: Child return code was: 0
DEBUG: Executing command: ['/bin/umount', '-n', '-l', '/var/lib/mock/fedora-21-ppc64le/root/dev/pts'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'}
DEBUG: Child return code was: 0
DEBUG: Executing command: ['/bin/umount', '-n', '-l', '/var/lib/mock/fedora-21-ppc64le/root/dev/shm'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'}
DEBUG: Child return code was: 0
DEBUG: Executing command: ['/bin/umount', '-n', '-l', '/var/lib/mock/fedora-21-ppc64le/root/sys'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'}
DEBUG: Child return code was: 0
DEBUG: Executing command: ['/bin/umount', '-n', '-l', '/var/lib/mock/fedora-21-ppc64le/root/proc'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'}
DEBUG: Child return code was: 0
ERROR: Exception(/home/baude/tmp/maven-release/maven-release-2.2.1-10.fc21.src.rpm) Config(fedora-21-ppc64le) 1 minutes 29 seconds
INFO: Results and/or logs in: /var/lib/mock/fedora-21-ppc64le/result
ERROR: Command failed. See logs for output.
 # ['bash', '--login', '-c', 'rpmbuild -bb --target ppc64le --nodeps  builddir/build/SPECS/maven-release.spec']
DEBUG: kill orphans


Adding a BR for modello resolves the ftbfs.

Comment 1 Mikolaj Izdebski 2014-03-19 07:09:25 UTC

Fixed in maven-release-2.2.1-11

Comment 2 Mikolaj Izdebski 2014-03-19 07:17:33 UTC

I believe that this bug is fixed in maven-release-2.2.1-11,
which is available in Fedora Rawhide, so I am closing this bug now.

The build containing the fix can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=505448

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