Your message dated Mon, 17 Sep 2012 20:08:28 +0200
with message-id <5057671c.2050...@debian.org>
and subject line Fixed by libbcprov-java 1.44+dfsg-3.1 upload
has caused the Debian Bug report #684815,
regarding jenkins-instance-identity: FTBFS: missing 
org.bouncycastle:bcprov:jar:debian
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
684815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jenkins-instance-identity
Version: 1.2-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120814 qa-ftbfs
Justification: FTBFS in wheezy on amd64

Hi,

During a rebuild of all packages in *wheezy*, 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 /«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.bouncycastle:bcprov:jar:debian
> 
>   Try downloading the file manually from the project website.
> 
>   Then, install it using the command: 
>       mvn install:install-file -DgroupId=org.bouncycastle -DartifactId=bcprov 
> -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.bouncycastle -DartifactId=bcprov 
> -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.2
>       2) org.bouncycastle:bcprov:jar:debian
> 
> ----------
> 1 required artifact is missing.
> 
> for artifact: 
>   org.jenkins-ci.modules:instance-identity:jenkins-module:1.2
> 
> 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: 3 seconds
> [INFO] Finished at: Mon Aug 13 22:49:47 UTC 2012
> [INFO] Final Memory: 26M/733M
> [INFO] 
> ------------------------------------------------------------------------
> make: *** [mvn-build] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/08/14/jenkins-instance-identity_1.2-1_wheezy.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.

--- End Message ---
--- Begin Message ---
FTBFS in the following packages :
 - wagon2 (#684841)
 - jenkins-ssh-cli-auth (#684829)
 - jenkins-instance-identity (#684815)
 - jenkins (#684826)
were fixed by libbcprov-java 1.44+dfsg-3.1 upload in t-p-u

Cheers,
--
Damien - Debian Developper
http://wiki.debian.org/DamienRaudeMorvan

--- End Message ---

Reply via email to