Source: jenkins
Version: 1.447.2+dfsg-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> debian/rules build
> test -x debian/rules
> mkdir -p "."
> /usr/share/maven-debian-helper/copy-repo.sh
> /«BUILDDIR»/jenkins-1.447.2+dfsg/debian
> mh_patchpoms -plibjenkins-java --debian-build --keep-pom-version
> --maven-repo=/«BUILDDIR»/jenkins-1.447.2+dfsg/debian/maven-repo
> --build-no-docs
> touch debian/stamp-poms-patched
> keytool -genkeypair -dname "cn=Jenkins, ou=Jenkins Project, o=Debian, c=US" \
> -alias jenkins -keypass jenkins -keystore dummy.keystore \
> -storepass jenkins -validity 3650
> # Purge out links relating to jenkins from the copy of the maven repo
> # fixes issue with circular dependency and the need to use the install
> # maven target
> for module in jenkins-core cli pom jenkins-war; do \
> find debian/maven-repo/org/jenkins-ci/main/${module} -type l
> -delete || true ;\
> done
> # Hack in java files from groovy source folder - no idea why they are there
> # might be maven3 related.
> cp core/src/main/groovy/jenkins/util/ServerTcpPort.java
> core/src/main/java/jenkins/util
> # before-build target may be used to unpatch the pom files, so we need to
> check if
> # patching the pom files is needed here, normally not
> if [ ! -f pom.xml.save ]; then \
> /usr/bin/make -f debian/rules patch-poms; \
> fi
> cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp
> /usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
>
> -Dproperties.file.manual=/«BUILDDIR»/jenkins-1.447.2+dfsg/debian/maven.properties
> -Dclassworlds.conf=/etc/maven2/m2-debian-nodocs.conf
> org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
> -Dmaven.repo.local=/«BUILDDIR»/jenkins-1.447.2+dfsg/debian/maven-repo -e
> -Dbuild.version="1.447.2" install
> + Error stacktraces are turned on.
> [INFO]
> NOTE: Maven is executing in offline mode. Any artifacts not already in your
> local
> repository will be inaccessible.
>
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Jenkins main module
> [INFO] Jenkins CLI
> [INFO] Jenkins core
> [INFO] Jenkins war
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) junit:junit:jar:debian
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=junit -DartifactId=junit
> -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=junit -DartifactId=junit
> -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
>
> Path to dependency:
> 1) org.kohsuke.stapler:maven-stapler-plugin:maven-plugin:1.16
> 2) org.apache.ant:ant-junit:jar:debian
> 3) junit:junit:jar:debian
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> org.kohsuke.stapler:maven-stapler-plugin:maven-plugin:1.16
>
> from the specified remote repositories:
> repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/),
> central (http://repo1.maven.org/maven2),
> maven.jenkins-ci.org
> (http://maven.jenkins-ci.org/content/repositories/snapshots/)
>
>
>
> NOTE: Maven is executing in offline mode. Any artifacts not already in your
> local
> repository will be inaccessible.
>
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
> ----------
> 1) junit:junit:jar:debian
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=junit -DartifactId=junit
> -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=junit -DartifactId=junit
> -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
>
> Path to dependency:
> 1) org.kohsuke.stapler:maven-stapler-plugin:maven-plugin:1.16
> 2) org.apache.ant:ant-junit:jar:debian
> 3) junit:junit:jar:debian
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> org.kohsuke.stapler:maven-stapler-plugin:maven-plugin:1.16
>
> from the specified remote repositories:
> repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/),
> central (http://repo1.maven.org/maven2),
> maven.jenkins-ci.org
> (http://maven.jenkins-ci.org/content/repositories/snapshots/)
>
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.loadPluginFully(DefaultLifecycleExecutor.java:1607)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeHandlersInPlugins(DefaultLifecycleExecutor.java:1468)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:222)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:178)
> 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 org.debian.maven.Wrapper.main(Wrapper.java:92)
> 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)
> Caused by:
> org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException:
> Missing:
> ----------
> 1) junit:junit:jar:debian
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=junit -DartifactId=junit
> -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=junit -DartifactId=junit
> -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
>
> Path to dependency:
> 1) org.kohsuke.stapler:maven-stapler-plugin:maven-plugin:1.16
> 2) org.apache.ant:ant-junit:jar:debian
> 3) junit:junit:jar:debian
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> org.kohsuke.stapler:maven-stapler-plugin:maven-plugin:1.16
>
> from the specified remote repositories:
> repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/),
> central (http://repo1.maven.org/maven2),
> maven.jenkins-ci.org
> (http://maven.jenkins-ci.org/content/repositories/snapshots/)
>
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304)
> at
> org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete(DefaultPluginManager.java:835)
> at
> org.apache.maven.plugin.DefaultPluginManager.loadPluginFully(DefaultPluginManager.java:1629)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.loadPluginFully(DefaultLifecycleExecutor.java:1582)
> ... 16 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 1 second
> [INFO] Finished at: Fri Jun 21 06:01:32 UTC 2013
> [INFO] Final Memory: 5M/58M
> [INFO]
> ------------------------------------------------------------------------
> make: *** [mvn-build] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/jenkins_1.447.2+dfsg-3_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
