Bug#549737: libgnucrypto-java: FTBFS: rm: cannot remove `debian/libgnucrypto-java/usr/share/info/dir': No such file or directory
On Sun, Oct 25, 2009 at 08:12:50PM +0100, Lucas Nussbaum wrote: On 25/10/09 at 19:39 +0100, Michael Koch wrote: On Mon, Oct 05, 2009 at 08:54:45PM +0200, Lucas Nussbaum wrote: Source: libgnucrypto-java Version: 2.1.0-3 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091005 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/build/user-libgnucrypto-java_2.1.0-3-amd64-KtKw9k/libgnucrypto-java-2.1.0' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/build/user-libgnucrypto-java_2.1.0-3-amd64-KtKw9k/libgnucrypto-java-2.1.0' make[2]: Leaving directory `/build/user-libgnucrypto-java_2.1.0-3-amd64-KtKw9k/libgnucrypto-java-2.1.0' make[1]: Leaving directory `/build/user-libgnucrypto-java_2.1.0-3-amd64-KtKw9k/libgnucrypto-java-2.1.0' dh_installdirs -plibgnucrypto-java dh_installdocs -plibgnucrypto-java ./README ./AUTHORS ./THANKS dh_installexamples -plibgnucrypto-java dh_installman -plibgnucrypto-java dh_installinfo -plibgnucrypto-java dh_installmenu -plibgnucrypto-java dh_installcron -plibgnucrypto-java dh_installinit -plibgnucrypto-java dh_installdebconf -plibgnucrypto-java dh_installemacsen -plibgnucrypto-java dh_installcatalogs -plibgnucrypto-java dh_installpam -plibgnucrypto-java dh_installlogrotate -plibgnucrypto-java dh_installlogcheck -plibgnucrypto-java dh_installchangelogs -plibgnucrypto-java ./ChangeLog dh_installudev -plibgnucrypto-java dh_lintian -plibgnucrypto-java dh_install -plibgnucrypto-java dh_link -plibgnucrypto-java dh_installmime -plibgnucrypto-java touch debian/libgnucrypto-java/etc/java/security/security.d/3000-gnu.crypto.jce.GnuCrypto rm: cannot remove `debian/libgnucrypto-java/usr/share/info/dir': No such file or directory make: *** [binary-install/libgnucrypto-java] Error 1 I just tried locally in pbuilder and the rm above did not failed and the package build successfully. Is this FTBFS still reproducible for you? Or was the bug somewhere else and got fixed already? It failed again on 16/10/2009, but I haven't tested since then. Have you tried diff'ing your build log with mine? Hmm, after some search I saw that your buildlog warns about missing /usr/bin/install-info which should be provided by dpkg (= 1.15.4) for Build-Depends. Should I Build-Depend on this version of dpkg? Cheers, Michael ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#549737: libgnucrypto-java: FTBFS: rm: cannot remove `debian/libgnucrypto-java/usr/share/info/dir': No such file or directory
On 26/10/09 at 08:54 +0100, Michael Koch wrote: On Sun, Oct 25, 2009 at 08:12:50PM +0100, Lucas Nussbaum wrote: On 25/10/09 at 19:39 +0100, Michael Koch wrote: On Mon, Oct 05, 2009 at 08:54:45PM +0200, Lucas Nussbaum wrote: Source: libgnucrypto-java Version: 2.1.0-3 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091005 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/build/user-libgnucrypto-java_2.1.0-3-amd64-KtKw9k/libgnucrypto-java-2.1.0' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/build/user-libgnucrypto-java_2.1.0-3-amd64-KtKw9k/libgnucrypto-java-2.1.0' make[2]: Leaving directory `/build/user-libgnucrypto-java_2.1.0-3-amd64-KtKw9k/libgnucrypto-java-2.1.0' make[1]: Leaving directory `/build/user-libgnucrypto-java_2.1.0-3-amd64-KtKw9k/libgnucrypto-java-2.1.0' dh_installdirs -plibgnucrypto-java dh_installdocs -plibgnucrypto-java ./README ./AUTHORS ./THANKS dh_installexamples -plibgnucrypto-java dh_installman -plibgnucrypto-java dh_installinfo -plibgnucrypto-java dh_installmenu -plibgnucrypto-java dh_installcron -plibgnucrypto-java dh_installinit -plibgnucrypto-java dh_installdebconf -plibgnucrypto-java dh_installemacsen -plibgnucrypto-java dh_installcatalogs -plibgnucrypto-java dh_installpam -plibgnucrypto-java dh_installlogrotate -plibgnucrypto-java dh_installlogcheck -plibgnucrypto-java dh_installchangelogs -plibgnucrypto-java ./ChangeLog dh_installudev -plibgnucrypto-java dh_lintian -plibgnucrypto-java dh_install -plibgnucrypto-java dh_link -plibgnucrypto-java dh_installmime -plibgnucrypto-java touch debian/libgnucrypto-java/etc/java/security/security.d/3000-gnu.crypto.jce.GnuCrypto rm: cannot remove `debian/libgnucrypto-java/usr/share/info/dir': No such file or directory make: *** [binary-install/libgnucrypto-java] Error 1 I just tried locally in pbuilder and the rm above did not failed and the package build successfully. Is this FTBFS still reproducible for you? Or was the bug somewhere else and got fixed already? It failed again on 16/10/2009, but I haven't tested since then. Have you tried diff'ing your build log with mine? Hmm, after some search I saw that your buildlog warns about missing /usr/bin/install-info which should be provided by dpkg (= 1.15.4) for Build-Depends. Should I Build-Depend on this version of dpkg? No, the build was done with version 1.15.4. You need to build-depend on install-info, which is no longer provided directly by dpkg. dpkg people, wouldn't it make sense to depend on install-info in dpkg, or better, to make the wrapper fail more noisily? It seems that this change is going to silently break lots of builds. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Processing of libstax-java_1.2.0-1_amd64.changes
GnuPG signature check failed on libstax-java_1.2.0-1_amd64.changes gpg: Signature made Mon Oct 26 10:35:44 2009 UTC using DSA key ID 9DCAE61E gpg: Can't check signature: public key not found (Exit status 2) /libstax-java_1.2.0-1_amd64.changes has bad PGP/GnuPG signature! Removing /libstax-java_1.2.0-1_amd64.changes, but keeping its associated files for now. Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Processing of maven-repo-helper_0.9_amd64.changes
GnuPG signature check failed on maven-repo-helper_0.9_amd64.changes gpg: Signature made Mon Oct 26 11:59:22 2009 UTC using DSA key ID 9DCAE61E gpg: Can't check signature: public key not found (Exit status 2) /maven-repo-helper_0.9_amd64.changes has bad PGP/GnuPG signature! Removing /maven-repo-helper_0.9_amd64.changes, but keeping its associated files for now. Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#552455: maven-docck-plugin 1.0-2 ftbfs
Package: maven-docck-plugin Version: 1.0-2 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu karmic ubuntu-patch Seen on http://launchpadlibrarian.net/34406545/buildlog_ubuntu-karmic-i386.maven-docck-plugin_1.0-2_FAILEDTOBUILD.txt.gz Reverting the 1.0-2 change fixes the build failure. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#552455: Acknowledgement (maven-docck-plugin 1.0-2 ftbfs)
forgot to add: fails on current unstable as well ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#549737: libgnucrypto-java: FTBFS: rm: cannot remove `debian/libgnucrypto-java/usr/share/info/dir': No such file or directory
On Mon, 26 Oct 2009, Lucas Nussbaum wrote: No, the build was done with version 1.15.4. You need to build-depend on install-info, which is no longer provided directly by dpkg. dpkg people, wouldn't it make sense to depend on install-info in dpkg, No, the whole point of using Breaks against info readers was to avoid adding a Depends on it. or better, to make the wrapper fail more noisily? It seems that this change is going to silently break lots of builds. The change happened quite some time ago, I don't think it will break many builds. Feel free to suggest another wording but I'm not sure that making it fail (instead of warn) will improve the situation wrt package installability/buildability. Cheers, -- Raphaël Hertzog ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
libjgraphx-java 1.0.2.6-1 MIGRATED to testing
FYI: The status of the libjgraphx-java source package in Debian's testing distribution has changed. Previous version: 1.0.2.4-2 Current version: 1.0.2.6-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
libxstream-java 1.3.1-5 MIGRATED to testing
FYI: The status of the libxstream-java source package in Debian's testing distribution has changed. Previous version: 1.3.1-4 Current version: 1.3.1-5 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
libproxool-java 0.9.1-2 MIGRATED to testing
FYI: The status of the libproxool-java source package in Debian's testing distribution has changed. Previous version: 0.9.1-1 Current version: 0.9.1-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Problems with maven-debian-helper
Hi all. I'm new to this mailing list and with maven and maven-debian-helper, so maybe I'm missing something trivial. I've started comaintaining libgettext-commons-java with Andreas Putzo. Upsteam started using maven to build it, so I think it as good idea to move the package build rules to maven-debian-helper. My current package is in trunk/libgettext-commons-java in pkg-java SVN repository. uscan is able to download correctly upstream tarball. If I try to compile, svn-buildpackage complains with this error message: 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=/home/giovanni/packages/gettext-commons/build-area/libgettext-commons-java-0.9.6/debian/maven.properties -Dclassworlds.conf=/etc/maven2/m2-debian.conf org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml -Dmaven.repo.local=/home/giovanni/packages/gettext-commons/build-area/libgettext-commons-java-0.9.6/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 Gettext Commons [INFO]task-segment: [package] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-assembly-plugin Reason: POM 'org.apache.maven.plugins:maven-assembly-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-assembly-plugin:pom:2.2-beta-2 for project org.apache.maven.plugins:maven-assembly-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Oct 26 17:10:01 CET 2009 [INFO] Final Memory: 4M/54M [INFO] I don't understand why it tries to use maven-assembly-plugin 2.2-beta-2 (2.2-beta-4 is present in sid and installed in my system). I can't find any occurrence of the string 2.2-beta-2 in my package or in /usr/share/maven-repo. What is wrong? Thanks, Giovanni. -- Giovanni Mascellani g.mascell...@gmail.com Pisa, Italy Web: http://poisson.phc.unipi.it/~mascellani Jabber: g.mascell...@jabber.org / giova...@elabor.homelinux.org GPG: 0x5F1FBF70 (FP: 1EB6 3D43 E201 4DDF 67BD 003F FCB0 BB5C 5F1F BF70) signature.asc Description: PGP signature signature.asc Description: OpenPGP digital signature ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: Problems with maven-debian-helper
Hi Giovanni, On Mon, Oct 26, 2009 at 8:39 PM, Giovanni Mascellani mascell...@poisson.phc.unipi.it wrote: What is wrong? AFAIK the versions of maven-plugins are somewhat hard coded but you can patch out the maven-assembly-plugin from pom.xml. I think it is not needed for the Debian package. Cheers, Torsten ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: Problems with maven-debian-helper
Hi Giovanni, Welcome aboard ! :) [You should post to debian-j...@lists.debian.org as pkg-java- maintain...@lists.alioth.debian.org is just a read-only list to monitor uploads and bugs on our packages] Le lundi 26 octobre 2009 21:31:45, Torsten Werner a écrit : Hi Giovanni, On Mon, Oct 26, 2009 at 8:39 PM, Giovanni Mascellani mascell...@poisson.phc.unipi.it wrote: What is wrong? AFAIK the versions of maven-plugins are somewhat hard coded but you can patch out the maven-assembly-plugin from pom.xml. Yep! There is a super pom embedded in /usr/share/maven2/lib/maven-debian-uber.jar in file org/apache/maven/project/pom-4.0.0.xml. This pom define default version of all maven plugins. I think, we should rebuild maven2 package to get new dependencies updated in this file. Cheers, -- Damien Raude-Morvan - http://damien.raude-morvan.com/ signature.asc Description: This is a digitally signed message part. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
