Bug#753221: jenkins-instance-identity: FTBFS: Missing required artifact: org.codehaus.groovy:groovy-all:jar:debian

[David Suárez]

Source: jenkins-instance-identity
Version: 1.3-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140628 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> /usr/share/maven-debian-helper/copy-repo.sh /«PKGBUILDDIR»/debian
> mh_patchpoms -pjenkins-instance-identity --debian-build --keep-pom-version --maven-repo=/«PKGBUILDDIR»/debian/maven-repo  --build-no-docs
> touch debian/stamp-poms-patched
> # 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=/«PKGBUILDDIR»/debian/maven.properties -Dclassworlds.conf=/etc/maven2/m2-debian-nodocs.conf org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml -Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo  package
> [INFO] 
> NOTE: Maven is executing in offline mode. Any artifacts not already in your local
> repository will be inaccessible.
> 
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Instance Identity
> [INFO]    task-segment: [package]
> [INFO] ------------------------------------------------------------------------
> [INFO] [localizer:generate {execution: default}]
> [INFO] [resources:resources {execution: default-resources}]
> [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered resources, i.e. build is platform dependent!
> [INFO] Copying 1 resource
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> 
> Missing:
> ----------
> 1) org.codehaus.groovy:groovy-all:jar:debian
> 
>   Try downloading the file manually from the project website.
> 
>   Then, install it using the command: 
>       mvn install:install-file -DgroupId=org.codehaus.groovy -DartifactId=groovy-all -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=org.codehaus.groovy -DartifactId=groovy-all -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> 
>   Path to dependency: 
>   	1) org.jenkins-ci.modules:instance-identity:jenkins-module:1.3
>   	2) org.jenkins-ci.main:jenkins-core:jar:1.509.2
>   	3) org.codehaus.groovy:groovy-all:jar:debian
> 
> ----------
> 1 required artifact is missing.
> 
> for artifact: 
>   org.jenkins-ci.modules:instance-identity:jenkins-module:1.3
> 
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
> 
> 
> 
> NOTE: Maven is executing in offline mode. Any artifacts not already in your local
> repository will be inaccessible.
> 
> 
> [INFO] ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 4 seconds
> [INFO] Finished at: Sat Jun 28 22:02:22 UTC 2014
> [INFO] Final Memory: 26M/568M
> [INFO] ------------------------------------------------------------------------
> make: *** [mvn-build] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/06/28/jenkins-instance-identity_1.3-1_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.