[Reproducible-builds] Bug#814072: tomcat-maven-plugin: FTBFS: Invalid plugin descriptor for org.codehaus.plexus:plexus-component-metadata

2016-02-08 Thread Chris Lamb 
Source: tomcat-maven-plugin
Version: 1.1-2.4
Severity: serious
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Dear Maintainer,

tomcat-maven-plugin fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package tomcat-maven-plugin
  dpkg-buildpackage: source version 1.1-2.4
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Emmanuel Bourg 
   dpkg-source --before-build tomcat-maven-plugin-1.1
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh clean --buildsystem=maven
 dh_testdir -O--buildsystem=maven
 dh_auto_clean -O--buildsystem=maven
"for dir in \$(find . -name target -type d); do if [ -f \$(echo \$dir | 
sed -e s/target\$/pom.xml/) ]; then rm -Rf \$dir; fi done"
mh_unpatchpoms -plibtomcat-maven-plugin-java
 dh_clean -O--buildsystem=maven
   debian/rules build
  dh build --buildsystem=maven
 dh_testdir -O--buildsystem=maven
 dh_update_autotools_config -O--buildsystem=maven
 dh_auto_configure -O--buildsystem=maven
  find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
  find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
No such file or directory
  find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
No such file or directory
mh_patchpoms -plibtomcat-maven-plugin-java --debian-build 
--keep-pom-version 
--maven-repo=/home/lamby/temp/cdt.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1/debian/maven-repo
 dh_auto_build -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/home/lamby/temp/cdt.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1/debian
 
-Dmaven.repo.local=/home/lamby/temp/cdt.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1/debian/maven-repo
 package -DskipTests -Dnotimestamp=true -Dlocale=en_US
  [INFO] Scanning for projects...
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.codehaus.mojo:tomcat-maven-plugin:maven-plugin:1.1
  [WARNING] 'dependencies.dependency.systemPath' for 
org.apache.tomcat:jasper-jdt:jar should use a variable instead of a hard-coded 
path /usr/share/java/ecj.jar @ line 152, column 16
  [WARNING] 
  [WARNING] It is highly recommended to fix these problems because they 
threaten the stability of your build.
  [WARNING] 
  [WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
  [WARNING] 
  [INFO]
 
  [INFO] 

  [INFO] Building Tomcat Maven Plugin 1.1
  [INFO] 

  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.115 s
  [INFO] Finished at: 2016-02-08T08:54:02+01:00
  [INFO] Final Memory: 8M/300M
  [INFO] 

  [ERROR] Invalid plugin descriptor for 
org.codehaus.plexus:plexus-component-metadata:1.6 
(/home/lamby/temp/cdt.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1/debian/maven-repo/org/codehaus/plexus/plexus-component-metadata/1.6/plexus-component-metadata-1.6.jar),
 Plugin's descriptor contains the wrong version: 1.5.5 -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/InvalidPluginDescriptorException
  dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20160208085215.TnS3QnKMpI/tomcat-maven-plugin-1.1
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml

[Reproducible-builds] Bug#814073: tzdata: FTBFS: Error: Unable to access jarfile /usr/lib/jvm/default-java//jre/lib/javazic.jar

2016-02-08 Thread Chris Lamb 
Source: tzdata
Version: 2016a-1
Severity: serious
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Dear Maintainer,

tzdata fails to build from source in unstable/amd64:

  [..]

  # Generate a java version
  /usr/lib/jvm/default-java//bin/java -jar 
/usr/lib/jvm/default-java//jre/lib/javazic.jar -V 2016a -d 
/home/lamby/temp/cdt.20160208085405.3qp2pN3cIl/tzdata-2016a/tzgen-java africa 
antarctica asia australasia europe northamerica southamerica etcetera factory 
backward systemv pacificnew gmt jdk11_backward
  Error: Unable to access jarfile /usr/lib/jvm/default-java//jre/lib/javazic.jar
  debian/rules:53: recipe for target 'build-indep-stamp' failed
  make: *** [build-indep-stamp] Error 1

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


tzdata.2016a-1.unstable.amd64.log.txt.gz
Description: Binary data
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

[Reproducible-builds] Bug#814071: pyorbital: FTBFS: AssertionError: 60.371433482573323 != 60.37143348255783

2016-02-08 Thread Chris Lamb 
Source: pyorbital
Version: 0.3.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Dear Maintainer,

pyorbital fails to build from source in unstable/amd64:

  [..]

  
  ==
  FAIL: test_sunangles (pyorbital.tests.test_astronomy.TestAstronomy)
  Test the sun-angle calculations:
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160208085132.sRBTiAzuyQ/pyorbital-0.3.2/pyorbital/tests/test_astronomy.py",
 line 53, in test_sunangles
  self.assertEqual(sun_theta, 60.371433482557833)
  AssertionError: 60.371433482573323 != 60.37143348255783
  
  --
  Ran 16 tests in 0.049s
  
  FAILED (failures=1)
  debian/rules:21: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160208085132.sRBTiAzuyQ/pyorbital-0.3.2'
  debian/rules:11: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


pyorbital.0.3.2-1.unstable.amd64.log.txt.gz
Description: Binary data
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Reproducible-builds] please don't build on archs that packages don't declare support for

2016-02-08 Thread Holger Levsen 
Hi Michael,

thanks for reaching out to us and reporting this…! 

On Samstag, 6. Februar 2016, Michael R. Crusoe wrote:
> I think you all are the bee's knees. However, some of the packages I
> maintain aren't compatible with 32 bit architectures, like armhf, and are
> explicitly marked as such. Yet the reproducible builds infrastructure still
> tries to build on the incompatible architecture and I get an error on
> tracker.d.o and elsewhere.
> 
> Here is an example:
> https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/khmer.html
> 
> Package: khmer
> Architecture: amd64 any-arm64 any-mips64 any-mips64el any-ia64 any-ppc64el
> any-sparc64
> (from https://sources.debian.net/src/khmer/2.0%2Bdfsg-4/debian/control/ )

khmer is being tried to build (on armhf), because it has "all" in the 
Architecture field, at least as seen on 
https://tests.reproducible-
builds.org/rbuild/testing/armhf/khmer_2.0+dfsg-3.rbuild.log where the line 
reads: 
"Architecture: any-amd64 any-arm64 any-mips64 any-mips64el any-ia64 any-
ppc64el any-sparc64 any-s390x all ppc64"

This line is coming from the .dsc file, see 
http://httpredir.debian.org/debian/pool/main/k/khmer/khmer_2.0+dfsg-3.dsc

I have no idea why the .dsc file differs from the control file.

> Could, perhaps, this not happen?

That's surely the idea as you can see if you compare 
https://tests.reproducible-builds.org/unstable/amd64/index_not_for_us.html 
with
https://tests.reproducible-builds.org/unstable/armhf/index_not_for_us.html

however there's a bug somewhere.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Reproducible-builds] please don't build on archs that packages don't declare support for

2016-02-08 Thread Michael R. Crusoe 
On Mon, Feb 8, 2016 at 10:13 AM Holger Levsen  wrote:

> Hi Michael,
>
> thanks for reaching out to us and reporting this…!
>

Of course!

On Samstag, 6. Februar 2016, Michael R. Crusoe wrote:
> > I think you all are the bee's knees. However, some of the packages I
> > maintain aren't compatible with 32 bit architectures, like armhf, and are
> > explicitly marked as such. Yet the reproducible builds infrastructure
> still
> > tries to build on the incompatible architecture and I get an error on
> > tracker.d.o and elsewhere.
> >
> > Here is an example:
> > https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/khmer.html
> >
> > Package: khmer
> > Architecture: amd64 any-arm64 any-mips64 any-mips64el any-ia64
> any-ppc64el
> > any-sparc64
> > (from https://sources.debian.net/src/khmer/2.0%2Bdfsg-4/debian/control/
> )
>
> khmer is being tried to build (on armhf), because it has "all" in the
> Architecture field, at least as seen on
> https://tests.reproducible-
> builds.org/rbuild/testing/armhf/khmer_2.0+dfsg-3.rbuild.log where the line
> reads:
> "Architecture: any-amd64 any-arm64 any-mips64 any-mips64el any-ia64 any-
> ppc64el any-sparc64 any-s390x all ppc64"
>
> This line is coming from the .dsc file, see
> http://httpredir.debian.org/debian/pool/main/k/khmer/khmer_2.0+dfsg-3.dsc
>
> I have no idea why the .dsc file differs from the control file.
>

One of the binary packages, khmer-common, is Architecture: All, Multi-Arch:
foreign. Perhaps that is why?


>
> > Could, perhaps, this not happen?
>
> That's surely the idea as you can see if you compare
> https://tests.reproducible-builds.org/unstable/amd64/index_not_for_us.html
> with
> https://tests.reproducible-builds.org/unstable/armhf/index_not_for_us.html
>
> however there's a bug somewhere.
>
>
> cheers,
> Holger
>
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

[Reproducible-builds] Bug#814146: jpathwatch: FTBFS: jni.h:45:20: fatal error: jni_md.h: No such file or directory

2016-02-08 Thread Chris Lamb 
Source: jpathwatch
Version: 0.95-3
Severity: serious
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Dear Maintainer,

jpathwatch fails to build from source in unstable/amd64:

  [..]

  debian/rules override_dh_auto_build
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160208200841.5hv5hxrBAb/jpathwatch-0.95'
  # build JNI library
  /usr/bin/make -C jpathwatch-native/src -f ../../debian/Makefile.jni
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160208200841.5hv5hxrBAb/jpathwatch-0.95/jpathwatch-native/src'
  g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/jvm/default-java/include  -c 
-o LinuxPathWatchService.o LinuxPathWatchService.cpp
  In file included from name_pachler_nio_file_impl_LinuxPathWatchService.h:2:0,
   from LinuxPathWatchService.cpp:28:
  /usr/lib/jvm/default-java/include/jni.h:45:20: fatal error: jni_md.h: No such 
file or directory
  compilation terminated.
  : recipe for target 'LinuxPathWatchService.o' failed
  make[2]: *** [LinuxPathWatchService.o] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160208200841.5hv5hxrBAb/jpathwatch-0.95/jpathwatch-native/src'
  debian/rules:7: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160208200841.5hv5hxrBAb/jpathwatch-0.95'
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


jpathwatch.0.95-3.unstable.amd64.log.txt.gz
Description: Binary data
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds