Your message dated Fri, 13 Jan 2017 10:50:41 +0100
with message-id <57092b60-f2e4-9a9d-5b62-ba8964089...@apache.org>
and subject line Re: Bug#849930: easybind: FTBFS (Cannot find pom file 
easybind.pom)
has caused the Debian Bug report #849930,
regarding easybind: FTBFS (Cannot find pom file easybind.pom)
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.)


-- 
849930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:easybind
Version: 1.0.3-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-indep
dh build-indep --buildsystem=gradle --with=maven-repo-helper
   dh_testdir -i -O--buildsystem=gradle
   dh_update_autotools_config -i -O--buildsystem=gradle
   dh_autoreconf -i -O--buildsystem=gradle
   dh_auto_configure -i -O--buildsystem=gradle
   dh_auto_build -i -O--buildsystem=gradle
        mkdir -p .gradle/init.d
        cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
        gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian jar
Initialized native services in: /<<PKGBUILDDIR>>/.gradle/native
Starting Build
Compiling initialization script '/<<PKGBUILDDIR>>/.gradle/init.d/init.gradle' 
using SubsetScriptTransformer.

[... snipped ...]

Total time: 7.476 secs
Stopped 0 compiler daemon(s).
   dh_auto_test -i -O--buildsystem=gradle
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=gradle --with=maven-repo-helper
   dh_testroot -i -O--buildsystem=gradle
   dh_prep -i -O--buildsystem=gradle
        rm -f debian/libeasybind-java.substvars
        rm -f debian/libeasybind-java.*.debhelper
        rm -rf debian/libeasybind-java/
   dh_auto_install -i -O--buildsystem=gradle
        install -d debian/libeasybind-java
   mh_install -i -O--buildsystem=gradle
        mh_installpom --java-lib            --package=libeasybind-java       
build/debian/easybind.pom
        mh_cleanpom   --package=libeasybind-java             
build/debian/easybind.pom debian/.mh/pom.xml debian/.mh/pom.properties
Cannot find pom file /<<PKGBUILDDIR>>/build/debian/easybind.pom
Dec 29, 2016 6:32:03 AM org.debian.maven.repo.POMCleaner cleanPom
SEVERE: null
java.io.FileNotFoundException: build/debian/easybind.pom (No such file or 
directory)
        at java.io.FileInputStream.open0(Native Method)
        at java.io.FileInputStream.open(FileInputStream.java:195)
        at java.io.FileInputStream.<init>(FileInputStream.java:138)
        at org.debian.maven.util.Readers.read(Readers.java:50)
        at org.debian.maven.repo.POMReader.readPom(POMReader.java:57)
        at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:226)
        at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:211)
        at org.debian.maven.repo.POMCleaner.cleanPom(POMCleaner.java:75)
        at org.debian.maven.repo.POMCleaner.main(POMCleaner.java:372)

Cannot find pom file /<<PKGBUILDDIR>>/build/debian/easybind.pom
Dec 29, 2016 6:32:03 AM org.debian.maven.repo.POMCleaner cleanPom
SEVERE: null
java.io.FileNotFoundException: build/debian/easybind.pom (No such file or 
directory)
        at java.io.FileInputStream.open0(Native Method)
        at java.io.FileInputStream.open(FileInputStream.java:195)
        at java.io.FileInputStream.<init>(FileInputStream.java:138)
        at org.debian.maven.util.Readers.read(Readers.java:50)
        at org.debian.maven.repo.POMReader.readPom(POMReader.java:57)
        at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:226)
        at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:211)
        at org.debian.maven.repo.POMCleaner.cleanPom(POMCleaner.java:75)
        at org.debian.maven.repo.POMCleaner.main(POMCleaner.java:372)

/usr/bin/mh_installpom: line 148: debian/.mh/pom.properties: No such file or 
directory
debian/rules:7: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2
--------------------------------------------------------------------------------

The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

If you could not reproduce this using sbuild on a single CPU virtual machine 
(as I did),
please do not downgrade or mark as unreproducible, I would then consider giving 
you access
to a virtual machine on which I can reproduce it so that you can as well.
(In such case, please contact me off-list for details).

Thanks.

--- End Message ---
--- Begin Message ---
Le 13/01/2017 à 10:39, Santiago Vila a écrit :

> Ok, easybind now builds fine in both testing and unstable, but since
> this is not a new version, then either there was a missing versioned
> build-depends or the bug is somewhere else.
> 
> If the bug is somewhere else, please use reassign and affects. I don't
> like reporting bugs against packages which are not to blame.

Thank you for confirming. I don't think easybind is to blame, that looks
like a transient tool chain issue but I don't know which one.

--- End Message ---
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to