Bug#1032901: unblock: crystal/1.6.0+dfsg-3

2023-03-13 Thread David Suárez
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: crys...@packages.debian.org, d...@debian.org
Control: affects -1 + src:crystal

Please unblock package crystal

[ Reason ]
The new version will fix #1031812 (the package lacks some
dependencies), and unmark it from autoremovals.

[ Impact ]
Crystal will be removed from testing due to autoremovals.

[ Tests ]
The package was manually tested in a new and clean debian
installation to check that the package has now all the needed 
dependecies to work.

[ Risks ]
The change is trivial, it only implies adding some runtime
dependencies.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

[ Other info ]
The package was upload some days before the hard
freeze so it couldn't get migrated automatically.

unblock crystal/1.6.0+dfsg-3



Bug#822275: ITA: crystal -- Compiler of the Crystal object-oriented programming language

2020-04-09 Thread David Suárez
control: retitle -1 ITA: crystal -- Compiler of the Crystal object 
oriented programming language

control: owner -1 david.sephi...@gmail.com



Bug#822275: ITP: crystal -- Compiler of the Crystal object-oriented programming language

2020-04-09 Thread David Suárez
control: retitle -1 ITP: crystal -- Compiler of the Crystal object 
oriented programming language

control: owner -1 david.sephi...@gmail.com



Bug#948953: RM: ruby-aws-partitions -- ROM; duplicated source packages in unstable

2020-01-19 Thread David Suárez

Control: tags -1 - moreinfo
Control: block -1 by 949292
thanks

Hi,

Blocked by #948953.

As soon as #948953 is closed, the RM could be done.

Thanks,

On 19/1/20 0:58, Scott Kitterman wrote:

On Wed, 15 Jan 2020 10:09:04 +0100 David Suarez 
wrote:

Package: ftp.debian.org
Severity: normal

Hi,

As a member of ruby team I request the removal of ruby-aws-partitions.

Please remove src:ruby-aws-partitions:1.211.0-1 from "unstable" (ant their
binary package).

Is a duplicate of src:ruby-aws-sdk:1.67.0-2, and
src:ruby-aws-sdk:2.9.32-2 that will enter
experimental and latter testing, updated and providing the correct
update path.

The package is maintained by Debian Ruby Extras Maintainers.


There is a dependency issue that needs to be addressed first:

Checking reverse dependencies...
# Broken Depends:
ruby-aws-sdk-core: ruby-aws-sdk-core

# Broken Build-Depends:
ruby-aws-sdk-core: ruby-aws-partitions (>= 1.0)

Dependency problem found.

Please remove the moreinfo tag once that has been addressed.

Scott K





Bug#949292: RM: ruby-aws-sdk-core -- ROM; duplicated source packages in unstable

2020-01-19 Thread David Suárez

Package: ftp.debian.org
Severity: normal

Hi,

As a member of ruby team I request the removal of ruby-aws-sdk-core.

Please remove src:ruby-aws-sdk-core:3.67.0-1 from "unstable" (ant their
binary package).

Is a duplicate of src:ruby-aws-sdk:1.67.0-2, and
src:ruby-aws-sdk:2.9.32-2 that will enter
experimental and latter testing, updated and providing the correct 
update path.


The package is maintained by Debian Ruby Extras Maintainers.

Regards

--

  David



Bug#948905: RM: ruby-aws-sdk-kms -- ROM; duplicated source packages in unstable

2020-01-14 Thread David Suárez

Package: ftp.debian.org
Severity: normal

Hi,

As a member of ruby team I request the removal of ruby-aws-sdk-kms.

Please remove src:ruby-aws-sdk-kms:1.24.0-1 from "unstable" (ant their
binary package).

Is a duplicate of src:ruby-aws-sdk:1.67.0-2, and
src:ruby-aws-sdk:2.9.32-2 that will enter
experimental and latter testing, updated and providing the correct 
update path.


The package is maintained by Debian Ruby Extras Maintainers.

Regards

--

  David



Bug#948683: ruby-aws-sdk: pakage is broken

2020-01-11 Thread David Suárez

Package: ruby-aws-sdk
Version: 2.9.32-2
Severity: grave
Justification: renders package unusable

Hi,

The current version in experimental is broken, Running the tests on it 
gives:


/usr/bin/ruby2.5 /usr/bin/rspec 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec 
-I /usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib -I 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec
Warning: Error occurred while trying to load 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/.simplecov. Error 
message: cannot load such file -- coveralls


An error occurred while loading 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb.
Failure/Error: self.load(File.open(path, 'r', encoding: 'UTF-8') { |f| 
f.read })


Errno::ENOENT:
  No such file or directory @ rb_sysopen - 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/../../endpoints.json
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in 
`initialize'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in 
`open'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in 
`load_file'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions.rb:148:in 
`defaults'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions.rb:155:in 
`default_list'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core.rb:388:in 
`partitions'
# 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb:204:in 
`block (2 levels) in '
# 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb:203:in 
`block in '
# 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb:5:in 
`'
# 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb:4:in 
`'
# 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb:3:in 
`'

sh: 1: unsigns: not found
sh: 1: signs: not found
sh: 1: signs: not found


Finished in 0.00064 seconds (files took 1.23 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

---



Updating this file 
(/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/../../endpoints.json) 
by hand gives:


/usr/bin/ruby2.5 /usr/bin/rspec 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec 
-I /usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib -I 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec
Warning: Error occurred while trying to load 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/.simplecov. Error 
message: cannot load such file -- coveralls


An error occurred while loading 
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb.
Failure/Error: self.load(File.open(path, 'r', encoding: 'UTF-8') { |f| 
f.read })


Errno::ENOENT:
  No such file or directory @ rb_sysopen - 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/../../service-models.json
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in 
`initialize'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in 
`open'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in 
`load_file'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions.rb:164:in 
`service_ids'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/region.rb:49:in 
`region_services'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/region.rb:42:in 
`build'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition.rb:72:in 
`block in build_regions'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition.rb:70:in 
`each'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition.rb:70:in 
`inject'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition.rb:70:in 
`build_regions'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition.rb:60:in 
`build'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition_list.rb:52:in 
`block in build'
# 
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition_list.rb:51:in 
`each'
# 

Bug#946417: RFS: giflib/5.1.9-1 [ITA] -- library for GIF images (utilities) - Fixes CVE's: #904114, #904113

2019-12-08 Thread David Suárez

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "giflib"

* Package name : giflib
Version : 5.1.9-1
Upstream Author : https://sourceforge.net/p/giflib/discussion/
* URL : http://giflib.sourceforge.net/
* License : MIT
* Vcs : https://salsa.debian.org/deiv-guest/giflib
Section : libs

It builds those binary packages:

giflib-tools - library for GIF images (utilities)
libgif7 - library for GIF images (library)
libgif-dev - library for GIF images (development)

To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/giflib

Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/g/giflib/giflib_5.1.9-1.dsc


Changes since the last upload:

  [ Ondřej Nový ]
  * d/watch: Use https protocol.

  [ Andreas Metzler ]
  * AUTHORS file not shipped anymore, update debian/*.docs.
  * Uses straight make instead of autotools, adapt debian/rules 
accordingly.

  * Use dh 12 compat level.
  + Update debian/copyright, add Format specifier.

  [ David Suárez ]
  * New upstream version:
- Add myself as maintainer; Closes: #834410.
- Fixes heap-based buffer overflow in DGifDecompressLine function.
CVE-2018-11490 sf#113; Closes: #904114
- Fixes MemorySanitizer: FPE on unknown address;
CVE-2019-15133 sf#119: Closes: #904113
  * Acknowledges NMU's uploads.
  * d/watch:
- Bump version.
- Don't run uupdate.
- Don't use debian redirector.
  * d/patches:
- Drop '03-spelling_fixes.patch' and 'CVE-2016-3977.patch';
Applied upstream.
- Add 'install-only-distributed-binaries-manuals' patch.
- Add 'revert-GifQuantizeBuffer-remove-from-lib' patch.
  * d/rules
- Don't force the rebuilding of manpages, the clean rule does the job.
- Remove the txt docs from giflib-tools; Not distributed.
- Remove 'dh_strip --dbgsym-migration'; Not needed anymore.
- Set DPKG_GENSYMBOLS_CHECK_LEVEL to 4.
  * giflib-tools.manpages: point to the correct ones.
  * d/control:
- Add 'Rules-Requires-Root' field.
- Update Standars version; no changes needed.
- Change VCS URL's.
  * d/libgif7.symbols:
- Add 'Build-Depends-Package' field.
- Update symbols.
  * d/copyright:
- Remove 'doc/gif87.txt'; Nows not distributed.
- Add myself on debian/* files.
- Add 'upstream-{Name,Contact}'.
  * Wrap and sort.
  * Add upstream metadata.
  * Add lintian overrides for some giflib-tools manpages.
  * Add lintian source override for sourceforge redirector.
  * Drop libgif7.shlibs; not needed.



The package is not in latest upstream because is currently in a process 
of removing a symbol, in the main library, that breaks some dependent 
packages (exactimage, mplayer-gui, mplayer, qutemol and xplanet).


The current version just patch the library to revert the symbol remove, 
to allow the upload without breaking anything (it fixes a pair of CVE's).


The next upload (the last upstream version) will go to experimental, 
trying to ask upstream to install a missing library (libutil.so) that 
contains the moved symbol (I will ask upstream to rename the library to 
something more suitable, like libgifutil or so).


In the meanwhile there are some bugs open on each package to adapt to 
the new upstream changes (currently we have the latest version on 
experimental), so they get informed about the changes of the next 
experimental upload when upstream gets the ABI stable.


Regards,

--

  David



Bug#834410: ITA: giflib -- library for GIF images

2019-11-24 Thread David Suárez

control: retitle -1 ITA: giflib -- library for GIF images
control: owner -1 david.sephi...@gmail.com



Bug#807529: ITP: libjs-lightbox2 -- small javascript library used to overlay images

2019-11-01 Thread David Suárez
control: retitle -1
control: owner -1 david.sephi...@gmail.com



signature.asc
Description: OpenPGP digital signature


Bug#794764: ITP: git-up -- fetch and rebase all locally-tracked remote branches

2015-08-06 Thread David Suárez
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org


   Package name: git-up
   Version: 0.5.12
  Upstream Author: Aanand Prasad aanand.pra...@gmail.com
  URL: https://github.com/aanand/git-up
  License: Other
  Description: fetch and rebase all locally-tracked remote branches


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765190: collab-qa-tools: please include documentation

2014-10-14 Thread David Suárez
Yeah,

This is on TODO sometime ago.

Maybe some help2man magic is needed :)

On the other way, the description links to [1], that contains some info about. 
And most of the commands has a help switch.


[1] https://wiki.debian.org/qa.debian.org/ArchiveTesting

--

  David


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765122: modsecurity-apache: FTBFS: configure: error: pcre library is required

2014-10-13 Thread David Suárez
Source: modsecurity-apache
Version: 2.8.0-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 Checking plataform... Identified as Linux
 configure: looking for Apache module support via DSO through APXS
 configure: found apxs at /usr/bin/apxs2
 configure: checking httpd version
 configure: httpd is recent enough
 configure: error: pcre library is required
 checking for libpcre config script... no
 configure: *** pcre library not found.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/modsecurity-apache_2.8.0-2_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765116: drbd-utils: FTBFS: mv: cannot stat '/«BUILDDIR»/drbd-utils-8.9.1+git0.f861210b/debian/drbd-utils/etc/init.d/drbd': No such file or directory

2014-10-13 Thread David Suárez
Source: drbd-utils
Version: 8.9.1+git0.f861210b-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[1]: Entering directory '/«BUILDDIR»/drbd-utils-8.9.1+git0.f861210b'
 dh_install --fail-missing
 Can't stat debian/tmp: No such file or directory
  at /usr/bin/dh_install line 245.
 # Move drbd-overview to /usr/sbin
 mv 
 /«BUILDDIR»/drbd-utils-8.9.1+git0.f861210b/debian/drbd-utils/sbin/drbd-overview
  /«BUILDDIR»/drbd-utils-8.9.1+git0.f861210b/debian/drbd-utils/usr/sbin/
 # Place the initscript where dh_installinit can find it
 mv 
 /«BUILDDIR»/drbd-utils-8.9.1+git0.f861210b/debian/drbd-utils/etc/init.d/drbd 
 /«BUILDDIR»/drbd-utils-8.9.1+git0.f861210b/debian/drbd-utils.drbd.init
 mv: cannot stat 
 '/«BUILDDIR»/drbd-utils-8.9.1+git0.f861210b/debian/drbd-utils/etc/init.d/drbd':
  No such file or directory
 make[1]: *** [override_dh_install] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/drbd-utils_8.9.1+git0.f861210b-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765118: scilab: FTBFS: [javac] /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/jogl/JoGLCanvas.java:23: error: cannot find symbol

2014-10-13 Thread David Suárez
Source: scilab
Version: 5.5.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[3]: Entering directory '/«PKGBUILDDIR»/modules/prebuildjava'
 Buildfile: /«PKGBUILDDIR»/modules/prebuildjava/build.xml
 
 scirenderer:
  [echo] Using:
  [echo] ${thirdparty.dir}
  [echo] /usr/share/java/jogl2.jar
  [echo] /usr/share/java/gluegen2-rt.jar
  [echo] /usr/share/java/jlatexmath.jar
 
 init:
 [mkdir] Created dir: /«PKGBUILDDIR»/modules/scirenderer/build/classes
 [mkdir] Created dir: /«PKGBUILDDIR»/modules/scirenderer/build/test
 [mkdir] Created dir: /«PKGBUILDDIR»/modules/scirenderer/jar
 
 compile:
 [javac] Compiling 117 source files to 
 /«PKGBUILDDIR»/modules/scirenderer/build/classes
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/Canvas.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/Drawer.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/DrawingTools.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/PackageInfo.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/SciRendererException.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/buffers/BuffersManager.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/buffers/DataBuffer.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/buffers/ElementsBuffer.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/buffers/IndicesBuffer.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/clipping/ClippingManager.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/clipping/ClippingPlane.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/data/AbstractDataProvider.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/data/DataProvider.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/data/DataUser.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/G2DCanvas.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/G2DCanvasFactory.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/G2DDrawingTools.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/buffers/G2DBuffersManager.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/buffers/G2DElementsBuffer.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/buffers/G2DIndicesBuffer.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/clipping/G2DClippingManager.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/clipping/G2DClippingPlane.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/lighting/G2DLight.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/lighting/G2DLightManager.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/AbstractDrawable3DObject.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/BoundingBox.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/Clippable.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/ConvexObject.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/DrawTools.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/G2DStroke.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/InvalidPolygonException.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/LightHelper.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/Motor3D.java
 [javac] 
 /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/PolyLine.java
 [javac] 
 

Bug#765119: php-config: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: php-config
Version: 1.10.12-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[1]: Entering directory '/«PKGBUILDDIR»'
 dh_link -O--buildsystem=phppear
 chmod +x ./debian/tests_run
 ./debian/tests_run
 Testing with bug10010.phpt
 PHPUnit 4.2.6 by Sebastian Bergmann.
 
 F
 
 Time: 80 ms, Memory: 2.00Mb
 
 There was 1 failure:
 
 1) bug10010.phpt
 Failed asserting that two strings are equal.
 --- Expected
 +++ Actual
 @@ @@
 -'Array
 +'Deprecated: Assigning the return value of new by reference is deprecated in 
 /«PKGBUILDDIR»/Config-1.10.12/test/phpt_test.php.inc on line 252
 +
 +Deprecated: Assigning the return value of new by reference is deprecated in 
 /«PKGBUILDDIR»/Config-1.10.12/test/phpt_test.php.inc on line 257
 +
 +Deprecated: Assigning the return value of new by reference is deprecated in 
 /«PKGBUILDDIR»/Config-1.10.12/test/phpt_test.php.inc on line 331
 +
 +Deprecated: Assigning the return value of new by reference is deprecated in 
 /«PKGBUILDDIR»/Config-1.10.12/test/phpt_test.php.inc on line 336
 +
 +Strict Standards: Non-static method PEAR_ErrorStack::singleton() should not 
 be called statically in /usr/share/php/PEAR/ErrorStack.php on line 983
 +
 +Deprecated: Non-static method PEAR::setErrorHandling() should not be called 
 statically, assuming $this from incompatible context in 
 /«PKGBUILDDIR»/Config-1.10.12/test/phpt_test.php.inc on line 15
 +
 +Deprecated: Non-static method PEAR_ErrorStack::setDefaultCallback() should 
 not be called statically, assuming $this from incompatible context in 
 /«PKGBUILDDIR»/Config-1.10.12/test/phpt_test.php.inc on line 16
 +Array
  (
  [foo] = bar
  [aMonths] = Array
  (
  [1] = January
  [2] = February
  [3] = March
  [4] = April
  [5] = May
  [6] = June
  [7] = July
  [8] = August
  [9] = September
  [10] = October
  [11] = November
  [12] = December
  )
  
  )'
 
 FAILURES!
 Tests: 1, Assertions: 1, Failures: 1.
 make[1]: *** [override_dh_link] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/php-config_1.10.12-4_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765115: ruby-yaml-db: FTBFS: build-dependency not installable: ruby-rails-3.2

2014-10-13 Thread David Suárez
Source: ruby-yaml-db
Version: 0.2.3-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ┌──┐
 │ Install ruby-yaml-db build dependencies (apt-based resolver)
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-ruby-yaml-db-dummy : Depends: ruby-rails-3.2 but it is 
 not going to be installed
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/ruby-yaml-db_0.2.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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765117: python-django: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: python-django
Version: 1.7-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 Test multiplication  division ... ok
 testUnitAttName (django.contrib.gis.tests.test_measure.DistanceTest)
 Testing the `unit_attname` class method ... ok
 testUnitConversions (django.contrib.gis.tests.test_measure.DistanceTest)
 Testing default units during maths ... ok
 testUnitsStr (django.contrib.gis.tests.test_measure.DistanceTest)
 Testing conversion to strings ... ok
 test_add_entry 
 (django.contrib.gis.tests.test_spatialrefsys.SpatialRefSysTest) ... skipped 
 'SpatialRefSysTest needs gdal support and a spatial database'
 test_ellipsoid 
 (django.contrib.gis.tests.test_spatialrefsys.SpatialRefSysTest) ... skipped 
 'SpatialRefSysTest needs gdal support and a spatial database'
 test_osr (django.contrib.gis.tests.test_spatialrefsys.SpatialRefSysTest) ... 
 skipped 'SpatialRefSysTest needs gdal support and a spatial database'
 test_retrieve (django.contrib.gis.tests.test_spatialrefsys.SpatialRefSysTest) 
 ... skipped 'SpatialRefSysTest needs gdal support and a spatial database'
 test_empty_permitted (django.contrib.formtools.tests.tests.FormHmacTests) ... 
 ok
 test_textfield_hash (django.contrib.formtools.tests.tests.FormHmacTests) ... 
 ok
 
 ==
 FAIL: test_loading_and_dumping (fixtures.tests.FixtureLoadingTests)
 --
 Traceback (most recent call last):
   File /«PKGBUILDDIR»/tests/fixtures/tests.py, line 170, in 
 test_loading_and_dumping
 self.assertEqual(len(w), 0)
 AssertionError: 1 != 0
 
 --
 Ran 7218 tests in 381.825s
 
 FAILED (failures=1, skipped=527, expected failures=7)
   Applying sessions.0001_initial... OK
 Destroying test database for alias 'default' (':memory:')...
 Destroying test database for alias 'other' (':memory:')...
 make[1]: *** [override_dh_auto_test] Error 1
 debian/rules:30: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/python-django_1.7-2_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765120: monogame: FTBFS: unsatisfiable build-dependency: monodevelop ( 4.0.12.) but 5.5.0.227-1 is to be installed

2014-10-13 Thread David Suárez
Source: monogame
Version: 2.5.1+dfsg-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ┌──┐
 │ Install monogame build dependencies (apt-based resolver)
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-monogame-dummy : Depends: monodevelop ( 4.0.12.) but 
 5.5.0.227-1 is to be installed
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/monogame_2.5.1+dfsg-4_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765113: ruby-webmock: FTBFS: ERROR: Test ruby2.1 failed

2014-10-13 Thread David Suárez
Source: ruby-webmock
Version: 1.19.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
  Failure/Error: lambda {
expected ArgumentError but nothing was raised
  # ./spec/acceptance/shared/returning_declared_responses.rb:381:in `block 
 (4 levels) in top (required)'
 
 Finished in 9.33 seconds
 3186 examples, 1 failure, 2 pending
 
 Failed examples:
 
 rspec ./spec/acceptance/shared/returning_declared_responses.rb:368 # 
 HTTPClient when using async requests with WebMock when request stub declares 
 that request should return a response when exception is declared to be raised 
 more than once should repeat raising sequence of exceptions declared number 
 of times
 /usr/bin/ruby2.1 -S rspec spec/acceptance/curb/curb_spec.rb 
 spec/acceptance/em_http_request/em_http_request_spec.rb 
 spec/acceptance/excon/excon_spec.rb spec/acceptance/http_gem/http_gem_spec.rb 
 spec/acceptance/httpclient/httpclient_spec.rb 
 spec/acceptance/net_http/net_http_spec.rb 
 spec/acceptance/net_http/real_net_http_spec.rb 
 spec/acceptance/typhoeus/typhoeus_hydra_spec.rb spec/quality_spec.rb 
 spec/unit/api_spec.rb spec/unit/errors_spec.rb 
 spec/unit/http_lib_adapters/http_lib_adapter_registry_spec.rb 
 spec/unit/http_lib_adapters/http_lib_adapter_spec.rb 
 spec/unit/matchers/hash_including_matcher_spec.rb 
 spec/unit/rack_response_spec.rb spec/unit/request_execution_verifier_spec.rb 
 spec/unit/request_pattern_spec.rb spec/unit/request_registry_spec.rb 
 spec/unit/request_signature_spec.rb spec/unit/request_stub_spec.rb 
 spec/unit/response_spec.rb spec/unit/stub_registry_spec.rb 
 spec/unit/stub_request_snippet_spec.rb spec/unit/util/hash_counter_spec.rb 
 spec/unit/util/hash_keys_stringifier_spec.rb spec/unit/util/headers_spec.rb 
 spec/unit/util/json_spec.rb spec/unit/util/query_mapper_spec.rb 
 spec/unit/util/uri_spec.rb spec/unit/util/version_checker_spec.rb 
 spec/unit/webmock_spec.rb -c -f progress -r ./spec/spec_helper.rb failed
 ERROR: Test ruby2.1 failed: 

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/ruby-webmock_1.19.0-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.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765121: rampart: FTBFS: configure: error: could not find openssl. stop

2014-10-13 Thread David Suárez
Source: rampart
Version: 1.3.0-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 checking for GNU libc compatible malloc... yes
 checking for stdlib.h... (cached) yes
 checking for GNU libc compatible realloc... yes
 checking path to use Axis2C . This is a compulsory to build Rampart-C... yes
 checking path to use openssl . This is a compulsory to build Rampart-C... yes
 configure: error: could not find openssl. stop

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/10/12/rampart_1.3.0-3_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765114: listaller: FTBFS: error parsing file /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/Listaller-0.5.gir: Failed to parse included gir Appstream-0.7

2014-10-13 Thread David Suárez
Source: listaller
Version: 0.5.9-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
 cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src  /usr/bin/g-ir-compiler 
 --shared-library=listaller-glib --includedir=. 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/Listaller-0.5.gir -o 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/Listaller-0.5.typelib
 Could not find GIR file 'Appstream-0.7.gir'; check XDG_DATA_DIRS or use 
 --includedir
 error parsing file /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/Listaller-0.5.gir: 
 Failed to parse included gir Appstream-0.7
 make[3]: *** [src/CMakeFiles/gir-compile] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/listaller_0.5.9-3_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765127: openvas-libraries: FTBFS: build-dependency not installable: libgnutls-dev

2014-10-13 Thread David Suárez
Source: openvas-libraries
Version: 2.0.4-2.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

It build-depends on libgnutls-dev which is
  - scheduled for removal
  - and (somehow related) uninstallable.

Relevant part (hopefully):
 ┌──┐
 │ Install openvas-libraries build dependencies (apt-based resolver)   
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-openvas-libraries-dummy : Depends: libgnutls-dev but it 
 is not going to be installed
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/openvas-libraries_2.0.4-2.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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765123: python-netaddr: FTBFS: IOError: [Errno 2] No such file or directory: '/«PKGBUILDDIR»/debian/python-netaddr/usr/lib/python2.7/dist-packages/netaddr/eui/oui.txt'

2014-10-13 Thread David Suárez
Source: python-netaddr
Version: 0.7.12-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 dh_installdocs -ppython-netaddr-docs ./README ./AUTHORS ./THANKS 
 dh_installexamples -ppython-netaddr-docs 
 dh_installman -ppython-netaddr-docs  
 dh_installinfo -ppython-netaddr-docs  
 dh_installmenu -ppython-netaddr-docs 
 dh_installcron -ppython-netaddr-docs 
 dh_installinit -ppython-netaddr-docs  
 dh_installdebconf -ppython-netaddr-docs 
 dh_installemacsen -ppython-netaddr-docs   
 dh_installcatalogs -ppython-netaddr-docs 
 dh_installpam -ppython-netaddr-docs 
 dh_installlogrotate -ppython-netaddr-docs 
 dh_installlogcheck -ppython-netaddr-docs 
 dh_installchangelogs -ppython-netaddr-docs  ./CHANGELOG 
 dh_installudev -ppython-netaddr-docs 
 dh_lintian -ppython-netaddr-docs 
 dh_bugfiles -ppython-netaddr-docs 
 dh_install -ppython-netaddr-docs  
 dh_link -ppython-netaddr-docs  
 dh_installmime -ppython-netaddr-docs 
 dh_installgsettings -ppython-netaddr-docs 
 dh_python2 -ppython-netaddr-docs 
 dh_strip -ppython-netaddr  
 dh_compress -ppython-netaddr  
 dh_fixperms -ppython-netaddr  
 dh_makeshlibs -ppython-netaddr  
 rm 
 /«PKGBUILDDIR»/debian/python-netaddr/usr/lib/python*/dist-packages/netaddr/eui/iab.*
 rm 
 /«PKGBUILDDIR»/debian/python-netaddr/usr/lib/python*/dist-packages/netaddr/eui/oui.*
 ln -s /usr/share/misc/oui.txt 
 /«PKGBUILDDIR»/debian/python-netaddr/usr/lib/python*/dist-packages/netaddr/eui/
 ln -s /usr/share/misc/iab.txt 
 /«PKGBUILDDIR»/debian/python-netaddr/usr/lib/python*/dist-packages/netaddr/eui/
 # We use python on purpose: the idx files cannot be generated by python3
 PYTHONPATH=/«PKGBUILDDIR» python \
   
 /«PKGBUILDDIR»/debian/python-netaddr/usr/lib/python*/dist-packages/netaddr/eui/ieee.py
 Traceback (most recent call last):
   File 
 /«PKGBUILDDIR»/debian/python-netaddr/usr/lib/python2.7/dist-packages/netaddr/eui/ieee.py,
  line 285, in module
 create_indices()
   File 
 /«PKGBUILDDIR»/debian/python-netaddr/usr/lib/python2.7/dist-packages/netaddr/eui/ieee.py,
  line 253, in create_indices
 oui_parser = OUIIndexParser(OUI_REGISTRY)
   File 
 /«PKGBUILDDIR»/debian/python-netaddr/usr/lib/python2.7/dist-packages/netaddr/eui/ieee.py,
  line 122, in __init__
 self.fh = open(ieee_file)
 IOError: [Errno 2] No such file or directory: 
 '/«PKGBUILDDIR»/debian/python-netaddr/usr/lib/python2.7/dist-packages/netaddr/eui/oui.txt'
 make: *** [binary-fixup/python-netaddr] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/python-netaddr_0.7.12-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765130: metview: FTBFS: PlotMod.h:47:28: fatal error: MagicsObserver.h: No such file or directory

2014-10-13 Thread David Suárez
Source: metview
Version: 4.4.8+dfsg.1-6
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 g++ -DHAVE_CONFIG_H -I. -I../../src  -I/usr/include/magics  
 -I/usr/include/hdf5/serial -I/usr/include/pango-1.0 -I/usr/include/cairo 
 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12  
 -DQT_WEBKIT -DQT_NO_DEBUG -DQT_WEBKIT_LIB -DQT_SQL_LIB -DQT_XMLPATTERNS_LIB 
 -DQT_XML_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
 -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore 
 -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui 
 -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtXmlPatterns 
 -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtWebKit -I/usr/include/qt4 
 -I/usr/include/qt4/QtHelp -I. -I.  -DNOMETVIEW_QT -DMETVIEW -I../libMetview 
 -I../libUtil -I../libMars  -I../libFTimeUtil  -I/usr/include/terralib/kernel  
 -I/usr/include/freetype2 -I/usr/include -I/usr/X11R6/include 
 -I/usr/local/include -I/usr/include/X11 -DMETVIEW_MOTIF -DLITTLE -DLITTLE_END 
 -DH_INCLUDES_CC -DR64 -DREAL_8 -DREAL_BIGGER_THAN_INTEGER -DI32 
 -DMAGINT_IS_INT -DREAL_IS_DOUBLE  -O2  -fPIC  -DUSE_NEW_IO -m64 -fPIC 
 -fno-gnu-keywords -Wno-deprecated -Wno-write-strings -DMETVIEW_QT 
 -DQT_NO_DEBUG_OUTPUT -DSiteIsNotECMWF -DLITTLE -DLITTLE_END -DH_INCLUDES_CC 
 -DR64 -DREAL_8 -DREAL_BIGGER_THAN_INTEGER -DI32 -DMAGINT_IS_INT 
 -DREAL_IS_DOUBLE -c -o bin_uPlotBatch-MvMainuPlotBatch.o `test -f 
 'MvMainuPlotBatch.cc' || echo './'`MvMainuPlotBatch.cc
 In file included from PlotModBatch.h:43:0,
  from MvMainuPlotBatch.cc:13:
 PlotMod.h:47:28: fatal error: MagicsObserver.h: No such file or directory
  #include MagicsObserver.h
 ^
 compilation terminated.
 make[6]: *** [bin_uPlotBatch-MvMainuPlotBatch.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/metview_4.4.8+dfsg.1-6_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.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765126: waitress: FTBFS: Sphinx errors

2014-10-13 Thread David Suárez
Source: waitress
Version: 0.8.9-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[2]: Entering directory '/«PKGBUILDDIR»/docs'
 rm -rf _build/*
 mkdir -p _build/html _build/doctrees
 sphinx-build -b html -d _build/doctrees  -N . _build/html
 Running Sphinx v1.2.3
 
 Exception occurred:
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 639, in 
 resolve
 raise DistributionNotFound(req)
 DistributionNotFound: waitress
 The full traceback has been saved in /tmp/sphinx-err-_dx9YA.log, if you want 
 to report the issue to the developers.
 Please also report this if it was a user error, so that a better error 
 message can be provided next time.
 A bug report can be filed in the tracker at 
 https://bitbucket.org/birkenfeld/sphinx/issues/. Thanks!
 make[2]: *** [html] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/waitress_0.8.9-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765129: tcos: FTBFS: build-dependency not installable: libxmlrpc-c3-dev

2014-10-13 Thread David Suárez
Source: tcos
Version: 0.89.93
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ┌──┐
 │ Install tcos build dependencies (apt-based resolver)
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-tcos-dummy : Depends: libxmlrpc-c3-dev but it is not 
 installable
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/10/12/tcos_0.89.93_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765124: ruby-stringex: FTBFS: ERROR: Test ruby2.1 failed: Running tests for ruby2.1 using debian/ruby-tests.rake ...

2014-10-13 Thread David Suárez
Source: ruby-stringex
Version: 2.5.2-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ===
 ...E
 ===
 Error: test_assigns_locale_in_i18n_backend(LocalizationTest)
   I18n::InvalidLocale: :pt-BR is not a valid locale
 /usr/lib/ruby/vendor_ruby/i18n.rb:285:in `enforce_available_locales!'
 /usr/lib/ruby/vendor_ruby/i18n/config.rb:13:in `locale='
 /usr/lib/ruby/vendor_ruby/i18n.rb:35:in `locale='
 /«PKGBUILDDIR»/test/unit/localization_test.rb:132:in 
 `test_assigns_locale_in_i18n_backend'
  129: 
  130:   assert_equal :en, Stringex::Localization.locale
  131: 
   = 132:   I18n.locale = other_locale
  133:   assert_equal other_locale, Stringex::Localization.locale
  134: 
  135:   Stringex::Localization.locale = :de
 ===
 ...
 ...
 ...
 
 
 Finished in 8.502547586 seconds.
 
 792 tests, 807 assertions, 0 failures, 305 errors, 0 pendings, 0 omissions, 0 
 notifications
 61.4899% passed
 
 93.15 tests/s, 94.91 assertions/s
 rake aborted!
 Command failed with status (1): [ruby -Ilib:lib:test 
 -I/usr/lib/ruby/vendor_ruby 
 /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb test/unit/**/*_test.rb 
 ]
 -e:1:in `main'
 Tasks: TOP = default = test
 (See full trace by running task with --trace)
 ERROR: Test ruby2.1 failed: 

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/ruby-stringex_2.5.2-2_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765125: libembperl-perl: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: libembperl-perl
Version: 2.5.0-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 #73 nesting.htm...ok
 #74 nesting2.htm...   ok
 #76 object.htm... ok
 #78 input.htm...  ok
 #79 input.htm...  ok
 #80 hidden.htm... ok
 #81 java.htm...   ok
 #82 inputjava.htm...  ok
 #83 inputjs2.htm...   ok
 #84 inputattr.htm...  ok
 #85 heredoc.htm...ok
 #86 epglobals.htm...  ok
 #88 post.htm...   ok
 #89 upload.htm... 
 Error in Line 9
 Is:   Filename:12upload-filenamebr
 Should:   Content-DispositionContent-Type
 Input:test/html/upload.htm
 Output:   test/tmp/out.htm
 Compared to:  test/cmp/upload.htm
 Log:  test/tmp/test.log
 Testparameter:
   query_info = multval=Amultval=Bmultval=Csingle=S
   offline = 0
   noloop = 1
   reqbody = Hi there!
 
  ERRORS detected! NOT all tests have been passed successfully
 
 make[1]: *** [test_dynamic] Error 9
 Makefile:1616: recipe for target 'test_dynamic' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/libembperl-perl_2.5.0-3_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765131: shogun: FTBFS: make[2]: python: Command not found

2014-10-13 Thread David Suárez
Source: shogun
Version: 3.2.0-7.2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[3]: Entering directory '/«PKGBUILDDIR»/examples'
 bash ./generate_documented.sh
 make[3]: Leaving directory '/«PKGBUILDDIR»/examples'
 echo ../examples/documented ../examples/documented/r_modular 
 ../examples/documented/octave_modular 
 ../examples/documented/octave_modular/tools 
 ../examples/documented/java_modular ../examples/documented/python_modular 
 ../examples/documented/python_modular/tmp 
 ../examples/documented/python_modular/tools 
 ../examples/documented/python_modular/graphical 
 ../examples/documented/ruby_modular ../examples/documented/elwms_static 
 ../examples/documented/python_static 
 ../examples/documented/python_static/tools 
 ../examples/documented/python_static/graphical 
 ../examples/documented/matlab_and_octave 
 ../examples/documented/matlab_and_octave/tests 
 ../examples/documented/matlab_and_octave/tools 
 ../examples/documented/matlab_and_octave/graphical 
 ../examples/documented/cmdline_static ../examples/documented/csharp_modular 
 ../examples/documented/libshogun ../examples/documented/r_static 
 ../examples/documented/r_static/graphical ../examples/documented/lua_modular
 ../examples/documented ../examples/documented/r_modular 
 ../examples/documented/octave_modular 
 ../examples/documented/octave_modular/tools 
 ../examples/documented/java_modular ../examples/documented/python_modular 
 ../examples/documented/python_modular/tmp 
 ../examples/documented/python_modular/tools 
 ../examples/documented/python_modular/graphical 
 ../examples/documented/ruby_modular ../examples/documented/elwms_static 
 ../examples/documented/python_static 
 ../examples/documented/python_static/tools 
 ../examples/documented/python_static/graphical 
 ../examples/documented/matlab_and_octave 
 ../examples/documented/matlab_and_octave/tests 
 ../examples/documented/matlab_and_octave/tools 
 ../examples/documented/matlab_and_octave/graphical 
 ../examples/documented/cmdline_static ../examples/documented/csharp_modular 
 ../examples/documented/libshogun ../examples/documented/r_static 
 ../examples/documented/r_static/graphical ../examples/documented/lua_modular
 python ./insert_examples.py pages/
 make[2]: python: Command not found
 Makefile:29: recipe for target 'examples' failed
 make[2]: *** [examples] Error 127

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/shogun_3.2.0-7.2_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765133: libvmime: FTBFS: build-dependency not installable: libgnutls-dev (= 1.2.0)

2014-10-13 Thread David Suárez
Source: libvmime
Version: 0.9.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

It build-depends on libgnutls-dev which is:
  - scheduled for removal
  - and (somehow related) uninstallable.

Relevant part (hopefully):
 ┌──┐
 │ Install libvmime build dependencies (apt-based resolver)
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-libvmime-dummy : Depends: libgnutls-dev (= 1.2.0) but 
 it is not going to be installed
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/libvmime_0.9.1-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765128: cutter-testing-framework: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: cutter-testing-framework
Version: 1.2.4-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[7]: Entering directory '/«PKGBUILDDIR»/test'
 make[7]: Nothing to be done for 'all-am'.
 make[7]: Leaving directory '/«PKGBUILDDIR»/test'
 make[6]: Leaving directory '/«PKGBUILDDIR»/test'
 
 Testsuite summary for cutter 1.2.4
 
 # TOTAL: 1
 # PASS:  0
 # SKIP:  0
 # XFAIL: 0
 # FAIL:  1
 # XPASS: 0
 # ERROR: 0
 
 See test/test-suite.log
 Please report to k...@clear-code.com
 
 make[5]: *** [test-suite.log] Error 1
 make[4]: *** [check-TESTS] Error 2
 Makefile:788: recipe for target 'test-suite.log' failed
 make[5]: Leaving directory '/«PKGBUILDDIR»/test'
 Makefile:894: recipe for target 'check-TESTS' failed
 make[4]: Leaving directory '/«PKGBUILDDIR»/test'
 make[3]: *** [check-am] Error 2
 make[2]: *** [check-recursive] Error 1
 Makefile:992: recipe for target 'check-am' failed
 make[3]: Leaving directory '/«PKGBUILDDIR»/test'
 Makefile:681: recipe for target 'check-recursive' failed
 make[2]: Leaving directory '/«PKGBUILDDIR»/test'
 make[1]: *** [check-recursive] Error 1
 dh_auto_test: make -j1 check returned exit code 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/cutter-testing-framework_1.2.4-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765136: php-http-upload: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: php-http-upload
Version: 1.0.0b2-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[1]: Entering directory '/«PKGBUILDDIR»'
 dh_link -O--buildsystem=phppear
 chmod +x ./debian/tests_run
 ./debian/tests_run 
 Testing with normal_upload.phpt
 PHPUnit 4.2.6 by Sebastian Bergmann.
 
 F
 
 Time: 61 ms, Memory: 2.25Mb
 
 There was 1 failure:
 
 1) normal_upload.phpt
 Failed asserting that format description matches text.
 --- Expected
 +++ Actual
 @@ @@
 -Valid: bool(true)
 -Missing: bool(false)
 -Error: bool(false)
 -MoveError: bool(false)
 -array(8) {
 -  'real' =
 -  string(3) 10b
 -  'name' =
 -  string(3) 10b
 -  'form_name' =
 -  string(8) userfile
 -  'ext' =
 -  string(0) 
 -  'tmp_name' =
 -  string(%d) %s
 -  'size' =
 -  int(10)
 -  'type' =
 -  string(10) text/plain
 -  'error' =
 -  NULL
 -}
 -bool(true)
 +Warning: require_once(HTTP/Upload.php): failed to open stream: No such file 
 or directory in - on line 2
 +
 +Fatal error: require_once(): Failed opening required 'HTTP/Upload.php' 
 (include_path='.:/usr/share/php:/usr/share/pear') in - on line 2
 
 FAILURES!
 Tests: 1, Assertions: 1, Failures: 1.
 make[1]: *** [override_dh_link] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/php-http-upload_1.0.0b2-2_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765135: gcc-4.9: FTBFS: find: `java': No such file or directory

2014-10-13 Thread David Suárez
Source: gcc-4.9
Version: 4.9.1-16
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[2]: Entering directory '/«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava'
 rm -f src.zip
 here=`pwd`; \
 ( \
   ( cd ../../../src/libjava/classpath; \
   find java gnu javax org sun -name '*.java' -print | \
   while read file; do \
 echo x-C | sed -e 's/^.//'; \
 echo ../../../src/libjava/classpath; \
 echo $file; \
   done ); \
   ( cd ../../../src/libjava/classpath/external/sax; \
   find org -name '*.java' -print | \
   while read file; do \
 echo x-C | sed -e 's/^.//'; \
 echo ../../../src/libjava/classpath/external/sax; \
 echo $file; \
   done ); \
   ( cd ../../../src/libjava/classpath/external/relaxngDatatype; \
   find org -name '*.java' -print | \
   while read file; do \
 echo x-C | sed -e 's/^.//'; \
 echo ../../../src/libjava/classpath/external/relaxngDatatype; \
 echo $file; \
   done ); \
   ( cd ../../../src/libjava/classpath/external/w3c_dom; \
   find org -name '*.java' -print | \
   while read file; do \
 echo x-C | sed -e 's/^.//'; \
 echo ../../../src/libjava/classpath/external/w3c_dom; \
 echo $file; \
   done ); \
   ( cd classpath; \
 find gnu java -name '*.java' -print | \
 while read file; do \
 echo x-C | sed -e 's/^.//'; \
 echo `pwd`; \
 echo $file; \
   done ); \
 ) | \
 jar -cfM@ $here/src.zip
 find: `java': No such file or directory
 here=`pwd`; \
 ( \
   ( cd ../../../src/libjava; \
   find gnu java -name '*.java' -print | \
   while read file; do \
 echo x-C | sed -e 's/^.//'; \
 echo ../../../src/libjava; \
 echo $file; \
   done ); \
 ) | \
 jar -ufM@ $here/src.zip
 make[2]: Leaving directory '/«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava'
 touch stamps/05-build-javasrc-stamp
 dh_testdir
 dh_testroot
 dh_installdirs -pgcj-4.9-source usr/share/java 
 /usr/lib/jvm/java-1.5.0-gcj-4.9-amd64
 cp -p /«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava/src.zip \
debian/gcj-4.9-source/usr/share/java/libgcj-src-4.9.zip
 dh_link -pgcj-4.9-source \
   usr/share/java/libgcj-src-4.9.zip \
   /usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/src.zip
 debian/dh_doclink -pgcj-4.9-source gcc-4.9-base
 WARNING: removing doc directory  gcj-4.9-source
 debian/dh_rmemptydirs -pgcj-4.9-source
 dh_compress -pgcj-4.9-source
 dh_fixperms -pgcj-4.9-source
 dh_gencontrol -pgcj-4.9-source -- -v4.9.1-16 '-Vlibgcc:Version=1:4.9.1-16' 
 '-Vgcc:Version=4.9.1-16' '-Vgcc:EpochVersion=1:4.9.1-16' 
 '-Vgcc:SoftVersion=4.9' '-Vgdc:Version=4.9.1-16' '-Vgcj:Version=4.9.1-16' 
 '-Vgcj:SoftVersion=4.9' '-Vgcj:BaseVersion=4.9' '-Vgnat:Version=4.9.1-16' 
 '-Vbinutils:Version=2.24.51.20141001' '-Vdep:libgcc=libgcc1 (= 1:4.9.1-16)' 
 '-Vdep:libgccdev=libgcc-4.9-dev (= 4.9.1-16)' '-Vdep:libgccbiarch=lib32gcc1 
 (= 1:4.9.1-16), libx32gcc1 (= 1:4.9.1-16)' 
 '-Vdep:libgccbiarchdev=lib32gcc-4.9-dev (= ${gcc:Version}), libx32gcc-4.9-dev 
 (= ${gcc:Version})' '-Vdep:libc=libc6 (= 2.11)' '-Vdep:libcdev=libc6-dev (= 
 2.13-5)' '-Vdep:libcbiarch=${shlibs:Depends}' 
 '-Vdep:libcbiarchdev=libc6-dev-i386 (= 2.11), libc6-dev-x32 (= 2.11)' 
 '-Vdep:libunwinddev=' '-Vdep:libcxxbiarchdev=lib32stdc++-4.9-dev (= 
 ${gcc:Version}), libx32stdc++-4.9-dev (= ${gcc:Version})' 
 '-Vdep:libcxxbiarchdbg=lib32stdc++6-4.9-dbg (= ${gcc:Version}), 
 libx32stdc++6-4.9-dbg (= ${gcc:Version})' '-Vdep:libgnat=' 
 '-Vdep:ecj=ecj-gcj, libecj-java-gcj (= 3.5.1)' '-Vdep:libcloog=' 
 '-Vgcc:multilib=gcc-4.9-multilib' '-Vgxx:multilib=g++-4.9-multilib' 
 '-Vgobjc:multilib=gobjc-4.9-multilib' 
 '-Vgobjcxx:multilib=gobjc++-4.9-multilib' 
 '-Vgfortran:multilib=gfortran-4.9-multilib' '-Vdep:gold=binutils-gold (= 
 2.24.51.20141001)' '-Vdep:libgomp=libgomp1 (= ${gcc:Version})' 
 '-Vdep:libitm=libitm1 (= ${gcc:Version})' '-Vdep:libatomic=libatomic1 (= 
 ${gcc:Version})' '-Vdep:libasan=libasan1 (= ${gcc:Version})' 
 '-Vdep:liblsan=liblsan0 (= ${gcc:Version})' '-Vdep:libtsan=libtsan0 (= 
 ${gcc:Version})' '-Vdep:libubsan=libubsan0 (= ${gcc:Version})' 
 '-Vdep:libcilkrts=libcilkrts5 (= ${gcc:Version})' 
 '-Vdep:libqmath=libquadmath0 (= ${gcc:Version})' 
 '-Vdep:libgfortranbiarchdev=lib32gfortran-4.9-dev (= ${gcc:Version}), 
 libx32gfortran-4.9-dev (= ${gcc:Version})' 
 '-Vdep:libobjcbiarchdev=lib32objc-4.9-dev (= ${gcc:Version}), 
 libx32objc-4.9-dev (= ${gcc:Version})' '-Vdep:libgompbiarch=lib32gomp1 (= 
 ${gcc:Version}), libx32gomp1 (= ${gcc:Version})' 
 '-Vdep:libitmbiarch=lib32itm1 (= ${gcc:Version}), libx32itm1 (= 
 ${gcc:Version})' '-Vdep:libatomicbiarch=lib32atomic1 (= ${gcc:Version}), 
 libx32atomic1 (= ${gcc:Version})' '-Vdep:libasanbiarch=lib32asan1 (= 
 ${gcc:Version}), libx32asan1 (= ${gcc:Version})' 
 '-Vdep:libubsanbiarch=lib32ubsan0 (= ${gcc:Version}), libx32ubsan0 (= 
 ${gcc:Version})' 

Bug#765137: libcgi-fast-perl: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: libcgi-fast-perl
Version: 1:2.02-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 t/004_fcgi_file_handles.t .. ok
 Failed 2/5 test programs. 4/25 subtests failed.
 t/005_no_file_handles.t  ok
 
 Test Summary Report
 ---
 t/001_basic.t(Wstat: 768 Tests: 9 Failed: 3)
   Failed tests:  6-7, 9
   Non-zero exit status: 3
 t/002_import.t   (Wstat: 256 Tests: 3 Failed: 1)
   Failed test:  3
   Non-zero exit status: 1
 Files=5, Tests=25,  1 wallclock secs ( 0.05 usr  0.04 sys +  0.52 cusr  0.09 
 csys =  0.70 CPU)
 Result: FAIL
 make[1]: *** [test_dynamic] Error 255
 Makefile:844: recipe for target 'test_dynamic' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/libcgi-fast-perl_2.02-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765134: sdrangelove: FTBFS: Configure errors

2014-10-13 Thread David Suárez
Source: sdrangelove
Version: 0.0.1.20140824-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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
 dh build --buildsystem=cmake
dh_testdir -O--buildsystem=cmake
dh_auto_configure -O--buildsystem=cmake
 -- The C compiler identification is GNU 4.9.1
 -- The CXX compiler identification is GNU 4.9.1
 -- Check for working C compiler: /usr/bin/cc
 -- Check for working C compiler: /usr/bin/cc -- works
 -- Detecting C compiler ABI info
 -- Detecting C compiler ABI info - done
 -- Check for working CXX compiler: /usr/bin/c++
 -- Check for working CXX compiler: /usr/bin/c++ -- works
 -- Detecting CXX compiler ABI info
 -- Detecting CXX compiler ABI info - done
 CMake Error at 
 /usr/lib/x86_64-linux-gnu/cmake/Qt5Multimedia/Qt5MultimediaConfig.cmake:27 
 (message):
   The imported target Qt5::Multimedia references the file
 
  /usr/lib/x86_64-linux-gnu/qt5/plugins/mediaservice/libgstcamerabin.so
 
   but this file does not exist.  Possible reasons include:
 
   * The file was deleted, renamed, or moved to another location.
 
   * An install or uninstall procedure did not complete successfully.
 
   * The installation package was faulty and contained
 
  
 /usr/lib/x86_64-linux-gnu/cmake/Qt5Multimedia/Qt5Multimedia_CameraBinServicePlugin.cmake
 
   but not all the files it references.
 
 Call Stack (most recent call first):
   /usr/lib/x86_64-linux-gnu/cmake/Qt5Multimedia/Qt5MultimediaConfig.cmake:145 
 (_qt5_Multimedia_check_file_exists)
   
 /usr/lib/x86_64-linux-gnu/cmake/Qt5Multimedia/Qt5Multimedia_CameraBinServicePlugin.cmake:4
  (_populate_Multimedia_plugin_properties)
   /usr/lib/x86_64-linux-gnu/cmake/Qt5Multimedia/Qt5MultimediaConfig.cmake:153 
 (include)
   CMakeLists.txt:19 (find_package)
 
 
 -- Configuring incomplete, errors occurred!
 See also /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log.
 dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
 -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None returned exit code 1
 make: *** [build] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/sdrangelove_0.0.1.20140824-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765139: flowgrind: FTBFS: build-dependency not installable: libxmlrpc-c3-dev

2014-10-13 Thread David Suárez
Source: flowgrind
Version: 0.7.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ┌──┐
 │ Install flowgrind build dependencies (apt-based resolver)   
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-flowgrind-dummy : Depends: libxmlrpc-c3-dev but it is 
 not installable
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/flowgrind_0.7.1-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765141: librest: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: librest
Version: 0.7.92-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[5]: Entering directory '/«PKGBUILDDIR»/tests'
 make[5]: Nothing to be done for 'all'.
 make[5]: Leaving directory '/«PKGBUILDDIR»/tests'
 
 Testsuite summary for rest 0.7.92
 
 # TOTAL: 6
 # PASS:  3
 # SKIP:  0
 # XFAIL: 1
 # FAIL:  2
 # XPASS: 0
 # ERROR: 0
 
 See tests/test-suite.log
 
 make[4]: *** [test-suite.log] Error 1
 Makefile:732: recipe for target 'test-suite.log' failed
 make[4]: Leaving directory '/«PKGBUILDDIR»/tests'
 make[3]: *** [check-TESTS] Error 2
 Makefile:838: recipe for target 'check-TESTS' failed
 make[3]: Leaving directory '/«PKGBUILDDIR»/tests'
 make[2]: *** [check-am] Error 2
 Makefile:946: recipe for target 'check-am' failed
 make[2]: Leaving directory '/«PKGBUILDDIR»/tests'
 make[1]: *** [check-recursive] Error 1
 Makefile:484: recipe for target 'check-recursive' failed
 make[1]: Leaving directory '/«PKGBUILDDIR»'
 dh_auto_test: make -j1 check returned exit code 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/librest_0.7.92-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765140: doxygen: FTBFS: Undefined subroutine main::parse_build_profiles called at /usr/bin/dpkg-genchanges line 365.

2014-10-13 Thread David Suárez
Source: doxygen
Version: 1.8.8-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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/dh-doxygen/dh_doxygen
 rdfind -outputname /dev/null -makehardlinks true 
 debian/doxygen-doc/usr/share/doc/doxygen
 Now scanning debian/doxygen-doc/usr/share/doc/doxygen, found 1438 files.
 Now have 1438 files in total.
 Removed 0 files due to nonunique device and inode.
 Now removing files with zero size from list...removed 0 files
 Total size is 6617799 bytes or 6 Mib
 Now sorting on size:removed 447 files due to unique sizes from list.991 files 
 left.
 Now eliminating candidates based on first bytes:removed 29 files from 
 list.962 files left.
 Now eliminating candidates based on last bytes:removed 7 files from list.955 
 files left.
 Now eliminating candidates based on md5 checksum:removed 70 files from 
 list.885 files left.
 It seems like you have 885 files that are not unique
 Totally, 2 Mib can be reduced.
 Now making results file /dev/null
 Now making hard links.
 Making 855 links.
 dh_installchangelogs doc/changelog.doc
 dh_strip --dbg-package=doxygen-dbg
 dh_link
 dh_compress -X.pdf
 dh_fixperms
 dh_installdeb
 dh_shlibdeps
 dh_gencontrol
 dh_md5sums
 dh_builddeb
 dpkg-deb: building package `doxygen-latex' in 
 `../doxygen-latex_1.8.8-4_all.deb'.
 dpkg-deb: building package `doxygen-doc' in `../doxygen-doc_1.8.8-4_all.deb'.
  dpkg-genchanges -sa ../doxygen_1.8.8-4_amd64.changes
 Undefined subroutine main::parse_build_profiles called at 
 /usr/bin/dpkg-genchanges line 365.
 dpkg-buildpackage: error: dpkg-genchanges gave error exit status 255
 
 Build finished at 20141012-0924

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/10/12/doxygen_1.8.8-4_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765132: user-mode-linux: FTBFS: build-dependency not installable: linux-source-3.13

2014-10-13 Thread David Suárez
Source: user-mode-linux
Version: 3.13-1um-0.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ┌──┐
 │ Install user-mode-linux build dependencies (apt-based resolver) 
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-user-mode-linux-dummy : Depends: linux-source-3.13 but 
 it is not installable
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/user-mode-linux_3.13-1um-0.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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765138: ruby-passenger: FTBFS: ext/common/agents/LoggingAgent/RemoteSender.h:32:18: fatal error: zlib.h: No such file or directory

2014-10-13 Thread David Suárez
Source: ruby-passenger
Version: 4.0.52-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 c++ -o buildout/agents/PassengerLoggingAgent.o  -Iext -Iext/common  
 -I/usr/include/libev   -I/usr/include/jsoncpp -D_REENTRANT 
 -I/usr/local/include -Wall -Wextra -Wno-unused-parameter -Wno-parentheses 
 -Wpointer-arith -Wwrite-strings -Wno-long-long 
 -Wno-missing-field-initializers -fcommon -feliminate-unused-debug-symbols 
 -feliminate-unused-debug-types -fvisibility=hidden 
 -DVISIBILITY_ATTRIBUTE_SUPPORTED -Wno-attributes -ggdb -DHAS_ALLOCA_H 
 -DHAVE_ACCEPT4 -DHAS_SFENCE -DHAS_LFENCE -DPASSENGER_DEBUG 
 -DBOOST_DISABLE_ASSERTS -std=gnu++11 -Wno-unused-local-typedefs 
 -DHASH_NAMESPACE=__gnu_cxx -DHASH_MAP_HEADER=hash_map 
 -DHASH_MAP_CLASS=hash_map -DHASH_FUN_H=hash_fun.h -g -O2 
 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
 -c ext/common/agents/LoggingAgent/Main.cpp
 In file included from ext/common/agents/LoggingAgent/LoggingServer.h:46:0,
  from ext/common/agents/LoggingAgent/Main.cpp:41:
 ext/common/agents/LoggingAgent/RemoteSender.h:32:18: fatal error: zlib.h: No 
 such file or directory
  #include zlib.h
   ^
 compilation terminated.
 rake aborted!
 Command failed with status (1): [c++ -o 
 buildout/agents/PassengerLoggingAgent.o  -Iext -Iext/common  
 -I/usr/include/libev   -I/usr/include/jsoncpp -D_REENTRANT 
 -I/usr/local/include -Wall -Wextra -Wno-unused-parameter -Wno-parentheses 
 -Wpointer-arith -Wwrite-strings -Wno-long-long 
 -Wno-missing-field-initializers -fcommon -feliminate-unused-debug-symbols 
 -feliminate-unused-debug-types -fvisibility=hidden 
 -DVISIBILITY_ATTRIBUTE_SUPPORTED -Wno-attributes -ggdb -DHAS_ALLOCA_H 
 -DHAVE_ACCEPT4 -DHAS_SFENCE -DHAS_LFENCE -DPASSENGER_DEBUG 
 -DBOOST_DISABLE_ASSERTS -std=gnu++11 -Wno-unused-local-typedefs 
 -DHASH_NAMESPACE=__gnu_cxx -DHASH_MAP_HEADER=hash_map 
 -DHASH_MAP_CLASS=hash_map -DHASH_FUN_H=hash_fun.h -g -O2 
 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
 -c ext/common/agents/LoggingAgent/Main.cpp]
 /«PKGBUILDDIR»/build/cplusplus_support.rb:51:in `run_compiler'
 /«PKGBUILDDIR»/build/cplusplus_support.rb:61:in `compile_cxx'
 /«PKGBUILDDIR»/build/agents.rb:136:in `block in top (required)'
 Tasks: TOP = fakeroot = apache2 = buildout/agents/PassengerLoggingAgent
 (See full trace by running task with --trace)
 make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/ruby-passenger_4.0.52-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765142: beautifulsoup4: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: beautifulsoup4
Version: 4.3.2-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 test_wrap_puts_new_contents_at_the_end 
 (bs4.tests.test_tree.TestTreeModification) ... ok
 
 ==
 FAIL: test_disk_file_warning (bs4.tests.test_soup.TestWarnings)
 --
 Traceback (most recent call last):
   File /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/bs4/tests/test_soup.py, 
 line 91, in test_disk_file_warning
 self.assertEqual(0, len(w))
 AssertionError: 0 != 2
 
 ==
 FAIL: test_url_warning (bs4.tests.test_soup.TestWarnings)
 --
 Traceback (most recent call last):
   File /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/bs4/tests/test_soup.py, 
 line 101, in test_url_warning
 self.assertEqual(0, len(w))
 AssertionError: 0 != 2
 
 --
 Ran 343 tests in 0.331s
 
 FAILED (failures=2)
 E: pybuild pybuild:256: test: plugin distutils failed with: exit code=1: cd 
 /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build; python3.4 -m unittest discover 
 -v 
 dh_auto_test: pybuild --test -i python{version} -p 3.4 --dir . returned exit 
 code 13

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/beautifulsoup4_4.3.2-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765143: ruby-i18n-inflector-rails: FTBFS: unsatisfiable build-dependencies: ruby-actionpack-3.2, ruby-railties-3.2

2014-10-13 Thread David Suárez
Source: ruby-i18n-inflector-rails
Version: 1.0.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ┌──┐
 │ Install ruby-i18n-inflector-rails build dependencies (apt-based resolver)   
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-ruby-i18n-inflector-rails-dummy : Depends: 
 ruby-actionpack-3.2 but it is not going to be installed
 Depends: 
 ruby-railties-3.2 but it is not going to be installed
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/ruby-i18n-inflector-rails_1.0.7-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765148: cynthiune.app: FTBFS: build-dependency not installable: libavifile-0.7-dev (= 1:0.7.48~20090503.ds)

2014-10-13 Thread David Suárez
Source: cynthiune.app
Version: 0.9.5-14
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ┌──┐
 │ Install cynthiune.app build dependencies (apt-based resolver)   
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-cynthiune.app-dummy : Depends: libavifile-0.7-dev (= 
 1:0.7.48~20090503.ds) but it is not going to be installed
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/cynthiune.app_0.9.5-14_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765153: php-symfony-process: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: php-symfony-process
Version: 2.3.19-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 /«PKGBUILDDIR»/Process.php:195
 /«PKGBUILDDIR»/Tests/AbstractProcessTest.php:359
 
 --
 
 There was 1 failure:
 
 1) 
 Symfony\Component\Process\Tests\SigchildDisabledProcessTest::testTTYCommandExitCode
 Failed asserting that exception of type PHPUnit_Framework_Error_Warning 
 matches expected exception 
 \Symfony\Component\Process\Exception\RuntimeException. Message was: 
 proc_open(/dev/tty): failed to open stream: No such device or address at
 #0 [internal function]: PHPUnit_Util_ErrorHandler::handleError(2, 
 'proc_open(/dev/...', '/build/php-symf...', 246, Array)
 #1 /«PKGBUILDDIR»/Process.php(246): proc_open('echo foo  /...', Array, 
 Array, '/build/php-symf...', NULL, Array)
 #2 /«PKGBUILDDIR»/Process.php(195): 
 Symfony\Component\Process\Process-start(NULL)
 #3 /«PKGBUILDDIR»/Tests/AbstractProcessTest.php(359): 
 Symfony\Component\Process\Process-run()
 #4 /«PKGBUILDDIR»/Tests/SigchildDisabledProcessTest.php(178): 
 Symfony\Component\Process\Tests\AbstractProcessTest-testTTYCommandExitCode()
 #5 [internal function]: 
 Symfony\Component\Process\Tests\SigchildDisabledProcessTest-testTTYCommandExitCode()
 #6 /usr/share/php/PHPUnit/Framework/TestCase.php(963): 
 ReflectionMethod-invokeArgs(Object(Symfony\Component\Process\Tests\SigchildDisabledProcessTest),
  Array)
 #7 /usr/share/php/PHPUnit/Framework/TestCase.php(835): 
 PHPUnit_Framework_TestCase-runTest()
 #8 /usr/share/php/PHPUnit/Framework/TestResult.php(643): 
 PHPUnit_Framework_TestCase-runBare()
 #9 /usr/share/php/PHPUnit/Framework/TestCase.php(771): 
 PHPUnit_Framework_TestResult-run(Object(Symfony\Component\Process\Tests\SigchildDisabledProcessTest))
 #10 /usr/share/php/PHPUnit/Framework/TestSuite.php(703): 
 PHPUnit_Framework_TestCase-run(Object(PHPUnit_Framework_TestResult))
 #11 /usr/share/php/PHPUnit/Framework/TestSuite.php(703): 
 PHPUnit_Framework_TestSuite-run(Object(PHPUnit_Framework_TestResult))
 #12 /usr/share/php/PHPUnit/TextUI/TestRunner.php(423): 
 PHPUnit_Framework_TestSuite-run(Object(PHPUnit_Framework_TestResult))
 #13 /usr/share/php/PHPUnit/TextUI/Command.php(186): 
 PHPUnit_TextUI_TestRunner-doRun(Object(PHPUnit_Framework_TestSuite), Array)
 #14 /usr/share/php/PHPUnit/TextUI/Command.php(138): 
 PHPUnit_TextUI_Command-run(Array, true)
 #15 /usr/bin/phpunit(42): PHPUnit_TextUI_Command::main()
 #16 {main}.
  
 FAILURES!
 Tests: 274, Assertions: 453, Failures: 1, Errors: 5, Skipped: 18.
 make[1]: *** [override_dh_auto_test] Error 2
 debian/rules:7: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/php-symfony-process_2.3.19-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.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765150: libhtml-formfu-perl: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: libhtml-formfu-perl
Version: 2.01000-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 CGI::param called in list context from package HTML::FormFu line 307, this 
 can lead to vulnerabilities. See the warning in Fetching the value or values 
 of a single named parameter at /usr/share/perl5/CGI.pm line 425.
 CGI::param called in list context from package HTML::FormFu::QueryType::CGI 
 line 14, this can lead to vulnerabilities. See the warning in Fetching the 
 value or values of a single named parameter at /usr/share/perl5/CGI.pm line 
 425.
 
 #   Failed test at t/nested-elements-file_post.t line 73.
 #  got: '1656'
 # expected: '4'
 
 #   Failed test at t/nested-elements-file_post.t line 74.
 #  got: 'image/gif'
 # expected: 'text/plain'
 # Looks like you failed 2 tests of 8.
 t/nested-elements-file_post.t .. 
 Dubious, test returned 2 (wstat 512, 0x200)
 Failed 3/3 test programs. 15/435 subtests failed.
 Failed 2/8 subtests 
 
 Test Summary Report
 ---
 t/aggregate.t(Wstat: 768 Tests: 402 Failed: 3)
   Failed tests:  57-58, 60
   Non-zero exit status: 3
 t/elements-file_post.t   (Wstat: 2560 Tests: 25 Failed: 10)
   Failed tests:  6-7, 9-10, 13-14, 18-19, 23-24
   Non-zero exit status: 10
 t/nested-elements-file_post.t (Wstat: 512 Tests: 8 Failed: 2)
   Failed tests:  6-7
   Non-zero exit status: 2
 Files=3, Tests=435, 11 wallclock secs ( 0.39 usr  0.09 sys + 10.14 cusr  0.59 
 csys = 11.21 CPU)
 Result: FAIL
 make[1]: *** [test_dynamic] Error 2
 Makefile:1801: recipe for target 'test_dynamic' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/libhtml-formfu-perl_2.01000-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765146: mimedefang: FTBFS: configure: WARNING: Oops.. I couldn't find libmilter.a or libmilter.so. Please install Sendmail

2014-10-13 Thread David Suárez
Source: mimedefang
Version: 2.73-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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
 dh_testdir
 # Add here commands to configure the package.
 ./configure --host=x86_64-linux-gnu --build=x86_64-linux-gnu --prefix=/usr 
 --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info 
 --disable-anti-virus --with-confsubdir=/ 
 --with-quarantinedir=/var/spool/MIMEDefang 
 checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
 checking whether the C compiler works... yes
 checking for C compiler default output file name... a.out
 checking for suffix of executables... 
 checking whether we are cross compiling... no
 checking for suffix of object files... o
 checking whether we are using the GNU C compiler... yes
 checking whether x86_64-linux-gnu-gcc accepts -g... yes
 checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
 checking for ar... ar
 checking for a BSD-compatible install... /usr/bin/install -c
 checking for perl... /usr/bin/perl
 checking whether socklen_t is defined... yes
 checking for Perl installation variable prefix... /usr
 checking for Perl installation variable siteprefix... /usr/local
 checking for Perl installation variable vendorprefix... /usr
 checking for Perl installation variable installarchlib... 
 /usr/lib/x86_64-linux-gnu/perl/5.20
 checking for Perl installation variable installprivlib... /usr/share/perl/5.20
 checking for Perl installation variable installbin... /usr/bin
 checking for Perl installation variable installman1dir... /usr/share/man/man1
 checking for Perl installation variable installman3dir... /usr/share/man/man3
 checking for Perl installation variable installscript... /usr/bin
 checking for Perl installation variable installsitearch... 
 /usr/local/lib/x86_64-linux-gnu/perl/5.20.1
 checking for Perl installation variable installsitelib... 
 /usr/local/share/perl/5.20.1
 checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
 checking for grep that handles long lines and -e... /bin/grep
 checking for egrep... /bin/grep -E
 checking for ANSI C header files... yes
 checking for sys/types.h... yes
 checking for sys/stat.h... yes
 checking for stdlib.h... yes
 checking for string.h... yes
 checking for memory.h... yes
 checking for strings.h... yes
 checking for inttypes.h... yes
 checking for stdint.h... yes
 checking for unistd.h... yes
 checking for wait3 that fills in rusage... yes
 checking for nm... /usr/bin/nm
 checking for Perl module IO::Socket... ok
 checking for Perl module MIME::Tools 5.410 ()... ok
 checking for Perl module MIME::WordDecoder... ok
 checking for Perl module Digest::SHA... ok
 checking for Perl module Mail::SpamAssassin 3.0 or better... yes
 checking for Perl module HTML::Parser... yes
 checking for Perl module Archive::Zip... yes
 checking MIME-Tools version... 5.505
 checking for Perl module Sys::Syslog... ok
 checking for Perl module Unix::Syslog... ok
 checking for Perl module ExtUtils::Embed... ok
 checking getopt.h usability... yes
 checking getopt.h presence... yes
 checking for getopt.h... yes
 checking for unistd.h... (cached) yes
 checking for stdint.h... (cached) yes
 checking poll.h usability... yes
 checking poll.h presence... yes
 checking for poll.h... yes
 checking whether stdint.h defines uint32_t... yes
 checking whether sys/types.h defines uint32_t... no
 checking whether sig_atomic_t is defined... yes
 checking whether x86_64-linux-gnu-gcc accepts -pthread... yes
 checking if we can embed a Perl interpreter in C... yes
 checking if it is safe to destroy and recreate a Perl interpreter... yes
 checking for res_init in -lresolv... no
 checking for htons in -lsocket... no
 checking for gethostbyname in -lnsl... yes
 checking for pthread_once in -lpthread... yes
 checking for initgroups... yes
 checking for getpwnam_r... yes
 checking for setrlimit... yes
 checking for snprintf... yes
 checking for vsnprintf... yes
 checking for readdir_r... yes
 checking for pathconf... yes
 checking for inet_ntop... yes
 checking for libmilter/mfapi.h... /usr/include/libmilter/mfapi.h
 checking for libmilter.a... no
 checking for libsm.a... no
 checking for libmilter.so... no
 checking for sendmail... /usr/sbin/sendmail
 checking for rm... /bin/rm
 configure: WARNING: Oops.. I couldn't find libmilter.a or libmilter.so.  
 Please install Sendmail
 configure: WARNING: and its libraries.  You must run Build in the libmilter/ 
 directory
 configure: WARNING: to compile libmilter.
 make: *** [config.status] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/mimedefang_2.73-2_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 

Bug#765144: amule: FTBFS: Logger.h:346: undefined reference to `MULE_EVT_LOGLINE'

2014-10-13 Thread David Suárez
Source: amule
Version: 2.3.1+git1a369e47-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 g++ -W -Wall -Wshadow -Wundef -pthread  -g -O2 -fstack-protector-strong 
 -Wformat -Werror=format-security -Wall -lpthread -Wl,-z,relro -o amulecmd 
 amulecmd-TextClient.o amulecmd-ExternalConnector.o amulecmd-LoggerConsole.o 
 amulecmd-OtherFunctions.o amulecmd-NetworkFunctions.o  -Llibs/common 
 -Llibs/ec/cpp -L. -lmulecommon -lec -lmulesocket -L/usr/lib/x86_64-linux-gnu 
 -pthread   -lwx_baseu_net-3.0 -lwx_baseu-3.0  -lreadline   -lz
 amulecmd-LoggerConsole.o: In function `CLoggingEvent':
 /«BUILDDIR»/amule-2.3.1+git1a369e47/obj-x86_64-linux-gnu/src/../../src/Logger.h:346:
  undefined reference to `MULE_EVT_LOGLINE'
 collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/amule_2.3.1+git1a369e47-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765145: globus-simple-ca: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: globus-simple-ca
Version: 4.14-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[5]: Entering directory '/«PKGBUILDDIR»/test'
 make[5]: Nothing to be done for 'all'.
 make[5]: Leaving directory '/«PKGBUILDDIR»/test'
 
 Testsuite summary for globus_simple_ca 4.14
 
 # TOTAL: 2
 # PASS:  1
 # SKIP:  0
 # XFAIL: 0
 # FAIL:  1
 # XPASS: 0
 # ERROR: 0
 
 See test/test-suite.log
 Please report to https://globus.atlassian.net/
 
 make[4]: *** [test-suite.log] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/globus-simple-ca_4.14-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765149: freebsd-libs: FTBFS: MK_TESTS can't be set by a user

2014-10-13 Thread David Suárez
Source: freebsd-libs
Version: 10.1~svn272464-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
  fakeroot debian/rules clean
 dh_testdir
 dh_testroot
 CFLAGS=-Wall -g -pipe -fPIC -I. -I/«PKGBUILDDIR»/sys -D_GNU_SOURCE 
 -D__FreeBSD_version=__FreeBSD_kernel_version -I/usr/include/freebsd 
 -Werror=implicit-function-declaration -O2 
 -I/«PKGBUILDDIR»/debian/local/include MAKEFLAGS= NO_WERROR=1 NOGCCERROR=1 
 NOSHARED=NO NO_SHARED=NO NO_PROFILE=1 DESTDIR=/«PKGBUILDDIR»/debian/tmp 
 SHLIB_MAJOR=0 MK_TESTS=yes bmake  -C /«PKGBUILDDIR»/lib/libsbuf clean
 bmake[1]: /usr/share/mk-freebsd/bsd.own.mk line 484: MK_TESTS can't be set 
 by a user.
 make: *** [clean] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/freebsd-libs_10.1~svn272464-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765147: seaborn: FTBFS: unsatisfiable build-dependency: python-matplotlib ( 1.2.0~) but 1.3.1-2 is to be installed

2014-10-13 Thread David Suárez
Source: seaborn
Version: 0.4.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ┌──┐
 │ Install seaborn build dependencies (apt-based resolver) 
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-seaborn-dummy : Depends: python-matplotlib ( 1.2.0~) 
 but 1.3.1-2 is to be installed
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/10/12/seaborn_0.4.0-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765152: liggghts: FTBFS: ld: cannot find -lQt5::Widgets

2014-10-13 Thread David Suárez
Source: liggghts
Version: 3.0.3+repack-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):  
 ^
 /usr/bin/cmake -E cmake_progress_report 
 /«BUILDDIR»/liggghts-3.0.3+repack/debian/build/CMakeFiles 
 [ 99%] Building CXX object src/CMakeFiles/libliggghts.dir/angle.cpp.o
 cd /«BUILDDIR»/liggghts-3.0.3+repack/debian/build/src  /usr/bin/mpicxx   
 -Dlibliggghts_EXPORTS -g -O2 -fstack-protector-strong -Wformat 
 -Werror=format-security -D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK 
 -DLAMMPS_JPEG -fPIC -I/usr/include/vtk-6.1 -I/usr/include/python2.7 
 -I/usr/include/freetype2 -I/usr/include/jsoncpp 
 -I/usr/include/x86_64-linux-gnu -I/usr/lib/openmpi/include 
 -I/usr/lib/openmpi/include/openmpi -I/usr/include/hdf5/serial 
 -I/usr/include/libxml2 -I/usr/include/tcl -I/usr/include/eigen3 
 -I/«BUILDDIR»/liggghts-3.0.3+repack -I/«BUILDDIR»/liggghts-3.0.3+repack/src   
  -o CMakeFiles/libliggghts.dir/angle.cpp.o -c 
 /«BUILDDIR»/liggghts-3.0.3+repack/src/angle.cpp
 Linking CXX shared library libliggghts.so
 cd /«BUILDDIR»/liggghts-3.0.3+repack/debian/build/src  /usr/bin/cmake -E 
 cmake_link_script CMakeFiles/libliggghts.dir/link.txt --verbose=1
 /usr/bin/mpicxx  -fPIC -g -O2 -fstack-protector-strong -Wformat 
 -Werror=format-security -D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK 
 -DLAMMPS_JPEG  -Wl,-z,relro -Wl,--as-needed -shared 
 -Wl,-soname,libliggghts.so.3 -o libliggghts.so.3.0.0 
 CMakeFiles/libliggghts.dir/dump_atom_vtk.cpp.o 
 CMakeFiles/libliggghts.dir/write_restart.cpp.o 
 CMakeFiles/libliggghts.dir/write_dump.cpp.o 
 CMakeFiles/libliggghts.dir/write_data.cpp.o 
 CMakeFiles/libliggghts.dir/verlet_implicit.cpp.o 
 CMakeFiles/libliggghts.dir/verlet.cpp.o 
 CMakeFiles/libliggghts.dir/velocity.cpp.o 
 CMakeFiles/libliggghts.dir/variable.cpp.o 
 CMakeFiles/libliggghts.dir/update.cpp.o 
 CMakeFiles/libliggghts.dir/universe.cpp.o 
 CMakeFiles/libliggghts.dir/tri_mesh_planar.cpp.o 
 CMakeFiles/libliggghts.dir/tri_mesh.cpp.o 
 CMakeFiles/libliggghts.dir/timer.cpp.o 
 CMakeFiles/libliggghts.dir/thermo.cpp.o 
 CMakeFiles/libliggghts.dir/special.cpp.o CMakeFiles/libliggghts.dir/set.cpp.o 
 CMakeFiles/libliggghts.dir/run.cpp.o CMakeFiles/libliggghts.dir/respa.cpp.o 
 CMakeFiles/libliggghts.dir/rerun.cpp.o 
 CMakeFiles/libliggghts.dir/replicate.cpp.o 
 CMakeFiles/libliggghts.dir/region_wedge.cpp.o 
 CMakeFiles/libliggghts.dir/region_union.cpp.o 
 CMakeFiles/libliggghts.dir/region_sphere.cpp.o 
 CMakeFiles/libliggghts.dir/region_prism.cpp.o 
 CMakeFiles/libliggghts.dir/region_plane.cpp.o 
 CMakeFiles/libliggghts.dir/region_mesh_tet.cpp.o 
 CMakeFiles/libliggghts.dir/region_intersect.cpp.o 
 CMakeFiles/libliggghts.dir/region_cylinder.cpp.o 
 CMakeFiles/libliggghts.dir/region_cone.cpp.o 
 CMakeFiles/libliggghts.dir/region_block.cpp.o 
 CMakeFiles/libliggghts.dir/region.cpp.o 
 CMakeFiles/libliggghts.dir/reader_xyz.cpp.o 
 CMakeFiles/libliggghts.dir/reader_native.cpp.o 
 CMakeFiles/libliggghts.dir/reader.cpp.o 
 CMakeFiles/libliggghts.dir/read_restart.cpp.o 
 CMakeFiles/libliggghts.dir/read_dump.cpp.o 
 CMakeFiles/libliggghts.dir/read_data.cpp.o 
 CMakeFiles/libliggghts.dir/random_park.cpp.o 
 CMakeFiles/libliggghts.dir/random_mars.cpp.o 
 CMakeFiles/libliggghts.dir/property_registry.cpp.o 
 CMakeFiles/libliggghts.dir/procmap.cpp.o 
 CMakeFiles/libliggghts.dir/particleToInsert.cpp.o 
 CMakeFiles/libliggghts.dir/pair_zbl.cpp.o 
 CMakeFiles/libliggghts.dir/pair_yukawa.cpp.o 
 CMakeFiles/libliggghts.dir/pair_table.cpp.o 
 CMakeFiles/libliggghts.dir/pair_sph_artvisc_tenscorr.cpp.o 
 CMakeFiles/libliggghts.dir/pair_sph.cpp.o 
 CMakeFiles/libliggghts.dir/pair_soft.cpp.o 
 CMakeFiles/libliggghts.dir/pair_morse.cpp.o 
 CMakeFiles/libliggghts.dir/pair_mie_cut.cpp.o 
 CMakeFiles/libliggghts.dir/pair_lj_smooth_linear.cpp.o 
 CMakeFiles/libliggghts.dir/pair_lj_smooth.cpp.o 
 CMakeFiles/libliggghts.dir/pair_lj_gromacs_coul_gromacs.cpp.o 
 CMakeFiles/libliggghts.dir/pair_lj_gromacs.cpp.o 
 CMakeFiles/libliggghts.dir/pair_lj_expand.cpp.o 
 CMakeFiles/libliggghts.dir/pair_lj_cut_coul_dsf.cpp.o 
 CMakeFiles/libliggghts.dir/pair_lj_cut_coul_debye.cpp.o 
 CMakeFiles/libliggghts.dir/pair_lj_cut_coul_cut.cpp.o 
 CMakeFiles/libliggghts.dir/pair_lj_cut.cpp.o 
 CMakeFiles/libliggghts.dir/pair_lj_cubic.cpp.o 
 CMakeFiles/libliggghts.dir/pair_lj96_cut.cpp.o 
 CMakeFiles/libliggghts.dir/pair_hybrid_overlay.cpp.o 
 CMakeFiles/libliggghts.dir/pair_hybrid.cpp.o 
 CMakeFiles/libliggghts.dir/pair_gran_proxy.cpp.o 
 CMakeFiles/libliggghts.dir/pair_gran.cpp.o 
 CMakeFiles/libliggghts.dir/pair_gauss.cpp.o 
 CMakeFiles/libliggghts.dir/pair_dpd_tstat.cpp.o 
 CMakeFiles/libliggghts.dir/pair_dpd.cpp.o 
 CMakeFiles/libliggghts.dir/pair_coul_wolf.cpp.o 
 CMakeFiles/libliggghts.dir/pair_coul_dsf.cpp.o 
 

Bug#765156: flashproxy: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: flashproxy
Version: 1.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 # ERROR: 0
 
 See ./test-suite.log
 
 make[4]: *** [test-suite.log] Error 1
 Makefile:809: recipe for target 'test-suite.log' failed
 make[4]: Leaving directory '/«PKGBUILDDIR»/facilitator'
 make[3]: *** [check-TESTS] Error 2
 Makefile:915: recipe for target 'check-TESTS' failed
 make[3]: Leaving directory '/«PKGBUILDDIR»/facilitator'
 make[2]: *** [check-am] Error 2
 dh_auto_test: make -j1 check PYTHONPATH=.. returned exit code 2
 Makefile:1107: recipe for target 'check-am' failed
 make[2]: Leaving directory '/«PKGBUILDDIR»/facilitator'
 make[1]: *** [override_dh_auto_test] Error 2
 debian/rules:37: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/flashproxy_1.7-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765154: gwave: FTBFS: build-dependency not installable: libgwrap-runtime-dev

2014-10-13 Thread David Suárez
Source: gwave
Version: 20090213-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ┌──┐
 │ Install gwave build dependencies (apt-based resolver)   
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-gwave-dummy : Depends: libgwrap-runtime-dev but it is 
 not going to be installed
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/gwave_20090213-5_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765160: python-jingo: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: python-jingo
Version: 0.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 mod = load_module(part_fqname, fh, filename, desc)
   File /«PKGBUILDDIR»/jingo/tests/test_monkey.py, line 9, in module
 import jingo.monkey
   File /«PKGBUILDDIR»/jingo/monkey.py, line 60, in module
 class SafeStrAndUnicode(django.utils.encoding.StrAndUnicode):
 AttributeError: 'module' object has no attribute 'StrAndUnicode'
 
 ==
 ERROR: jingo.tests.test_views.test_template_substitution_crash
 --
 Traceback (most recent call last):
   File /usr/lib/python2.7/dist-packages/nose/case.py, line 197, in runTest
 self.test(*self.arg)
   File /«PKGBUILDDIR»/jingo/tests/test_views.py, line 15, in 
 test_template_substitution_crash
 translation.activate('xx')
   File 
 /usr/lib/python2.7/dist-packages/django/utils/translation/__init__.py, line 
 145, in activate
 return _trans.activate(language)
   File 
 /usr/lib/python2.7/dist-packages/django/utils/translation/trans_real.py, 
 line 225, in activate
 _active.value = translation(language)
   File 
 /usr/lib/python2.7/dist-packages/django/utils/translation/trans_real.py, 
 line 209, in translation
 default_translation = _fetch(settings.LANGUAGE_CODE)
   File 
 /usr/lib/python2.7/dist-packages/django/utils/translation/trans_real.py, 
 line 189, in _fetch
 The translation infrastructure cannot be initialized before the 
 AppRegistryNotReady: The translation infrastructure cannot be initialized 
 before the apps registry is ready. Check that you don't make non-lazy gettext 
 calls at import time.
 
 --
 Ran 24 tests in 0.275s
 
 FAILED (errors=9)
 make[1]: *** [override_dh_auto_test] Error 1
 debian/rules:24: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/python-jingo_0.7-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765159: libvirt-python: FTBFS: ERROR: failed virNodeAllocPages

2014-10-13 Thread David Suárez
Source: libvirt-python
Version: 1.2.8-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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
 dh build --with python3,python2 --buildsystem=pybuild
dh_testdir -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
 I: pybuild base:170: python2.7 setup.py config 
 running config
 I: pybuild base:170: python3.4 setup.py config 
 running config
dh_auto_build -O--buildsystem=pybuild
 I: pybuild base:170: /usr/bin/python setup.py build 
 running build
 /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
 /usr/bin/python generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml
 Found 394 functions in /usr/share/libvirt/api/libvirt-api.xml
 Found 0 functions in libvirt-override-api.xml
 Generated 328 wrapper functions
 Missing type converters: 
 unsigned int *:1 
 ERROR: failed virNodeAllocPages
 error: command '/usr/bin/python' failed with exit status 1
 E: pybuild pybuild:256: build: plugin distutils failed with: exit code=1: 
 /usr/bin/python setup.py build 
 dh_auto_build: pybuild --build -i python{version} -p 2.7 --dir . returned 
 exit code 13
 make: *** [build] Error 13

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/libvirt-python_1.2.8-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765157: crystalspace: FTBFS: make[2]: *** No rule to make target 'install_lib'. Stop.

2014-10-13 Thread David Suárez
Source: crystalspace
Version: 2.0+dfsg-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
  fakeroot debian/rules binary
 dh binary --with autotools_dev
dh_testroot
dh_prep
debian/rules override_dh_auto_install
 make[1]: Entering directory '/«BUILDDIR»/crystalspace-2.0+dfsg'
 /usr/bin/make 
 DESTDIR=/«BUILDDIR»/crystalspace-2.0+dfsg/debian/libcrystalspace-2.0 
 install_lib install_plugin
 make[2]: Entering directory '/«BUILDDIR»/crystalspace-2.0+dfsg'
 make[2]: *** No rule to make target 'install_lib'.  Stop.
 make[2]: Leaving directory '/«BUILDDIR»/crystalspace-2.0+dfsg'
 debian/rules:28: recipe for target 'override_dh_auto_install' failed
 make[1]: *** [override_dh_auto_install] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/crystalspace_2.0+dfsg-2_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765155: zendframework: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: zendframework
Version: 1.12.9+dfsg-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 dpkg-buildpackage: host architecture amd64
  fakeroot debian/rules clean
 dh clean --with phpcomposer
dh_testdir
dh_auto_clean
debian/rules override_dh_clean
 make[1]: Entering directory '/«BUILDDIR»/zendframework-1.12.9+dfsg'
 rm -rf tests/Zend/Filter/_files/home
 dh_clean -X.orig
 make[1]: Leaving directory '/«BUILDDIR»/zendframework-1.12.9+dfsg'
  dpkg-source -b zendframework-1.12.9+dfsg
 dpkg-source: info: using source format `3.0 (quilt)'
 dpkg-source: info: building zendframework using existing 
 ./zendframework_1.12.9+dfsg.orig.tar.gz
 dpkg-source: info: building zendframework in 
 zendframework_1.12.9+dfsg-1.debian.tar.xz
 dpkg-source: info: building zendframework in zendframework_1.12.9+dfsg-1.dsc
  debian/rules build
 dh build --with phpcomposer
dh_testdir
dh_auto_configure
dh_auto_build
debian/rules override_dh_auto_test
 make[1]: Entering directory '/«BUILDDIR»/zendframework-1.12.9+dfsg'
 # The following symlinks can’t be handled by dpkg’s own implementation of 
 quilt
 ln -s /usr/share/fonts/truetype/ttf-bitstream-vera 
 tests/Zend/Barcode/Object/_fonts
 ln -s /usr/share/fonts/truetype/ttf-bitstream-vera tests/Zend/Pdf/_fonts
 cd tests  ./runtests.sh
 + phpunit --verbose AllTests
 ...  63 / 248 ( 
 25%)
 PHP Fatal error:  Class 'Text_Template' not found in 
 /usr/share/php/PHPUnit/Framework/TestCase.php on line 698
 make[1]: *** [override_dh_auto_test] Error 255
 .E...debian/rules:11: recipe for target 
 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/zendframework_1.12.9+dfsg-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765158: smuxi: FTBFS: build-dependency not installable: libmessagingmenu-cil-dev

2014-10-13 Thread David Suárez
Source: smuxi
Version: 0.11~rc5-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ┌──┐
 │ Install smuxi build dependencies (apt-based resolver)   
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-smuxi-dummy : Depends: libmessagingmenu-cil-dev but it 
 is not installable
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/smuxi_0.11~rc5-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765163: lua-lgi: FTBFS: regress.c:2:20: fatal error: config.h: No such file or directory

2014-10-13 Thread David Suárez
Source: lua-lgi
Version: 0.8.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 cc -fPIC   -pthread -I/usr/include/cairo -I/usr/include/pixman-1 
 -I/usr/include/freetype2 -I/usr/include/libpng12 
 -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 
 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -g -O2 -fstack-protector-strong 
 -Wformat -Werror=format-security -c -o regress.o 
 /usr/share/gobject-introspection-1.0/tests/regress.c
 /usr/share/gobject-introspection-1.0/tests/regress.c:2:20: fatal error: 
 config.h: No such file or directory
  #include config.h
 ^
 compilation terminated.
 make[2]: *** [regress.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/10/12/lua-lgi_0.8.0-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765162: pgloader: FTBFS: cp: cannot stat 'debian/tmp/build/bin/pgloader': No such file or directory

2014-10-13 Thread David Suárez
Source: pgloader
Version: 3.1.0+dfsg-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
  fakeroot debian/rules binary
 dh binary 
dh_testroot
dh_prep
dh_installdirs
dh_auto_install
dh_install
 cp: cannot stat 'debian/tmp/build/bin/pgloader': No such file or directory
 dh_install: cp -a debian/tmp/build/bin/pgloader debian/pgloader//usr/bin/ 
 returned exit code 1
 make: *** [binary] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/pgloader_3.1.0+dfsg-2_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765164: php-event-dispatcher: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: php-event-dispatcher
Version: 1.1.0-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 make[1]: Entering directory '/«PKGBUILDDIR»'
 dh_link -O--buildsystem=phppear
 chmod +x ./debian/tests_run
 ./debian/tests_run 
 Testing with *.phpt
 PHPUnit 4.2.6 by Sebastian Bergmann.
 
 ..
 
 Time: 39 ms, Memory: 2.75Mb
 
 OK (2 tests, 21 assertions)
 
 PHPUnit 4.2.6 by Sebastian Bergmann.
 
 F.
 
 Time: 45 ms, Memory: 2.75Mb
 
 There was 1 failure:
 
 1) DispatcherTest::test1
 Error
 Failed asserting that 3 matches expected 2.
 
 /«PKGBUILDDIR»/Event_Dispatcher-1.1.0/tests/DispatcherTest.php:89
 
 FAILURES!
 Tests: 2, Assertions: 13, Failures: 1.
 make[1]: *** [override_dh_link] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/php-event-dispatcher_1.1.0-3_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765161: xemacs21: FTBFS: build-dependency not installable: libtiff4-dev

2014-10-13 Thread David Suárez
Source: xemacs21
Version: 21.4.22-8
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
 ┌──┐
 │ Install xemacs21 build dependencies (apt-based resolver)
  │
 └──┘
 
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  sbuild-build-depends-xemacs21-dummy : Depends: libtiff4-dev but it is not 
 installable
 E: Unable to correct problems, you have held broken packages.
 apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/xemacs21_21.4.22-8_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765151: gdebi: FTBFS: Tests failures

2014-10-13 Thread David Suárez
Source: gdebi
Version: 0.9.5.5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
   W: error-package: no-section-field
   W: error-package: no-priority-field
   E: error-package: wrong-file-owner-uid-or-gid etc/ 1000/1000
   E: error-package: wrong-file-owner-uid-or-gid etc/foo 1000/1000
   W: error-package: maintainer-script-ignores-errors postinst
   
 - Lintian finished with exit status 0?   ^
 + Lintian finished with exit status 1?   ^
 
 
 --
 Ran 7 tests in 8.445s
 
 FAILED (failures=1)
 make[1]: *** [override_dh_auto_test] Error 1
 debian/rules:14: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/10/12/gdebi_0.9.5.5_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763263: fbi: FTBFS: transupp.c:892: undefined reference to `jpeg_core_output_dimensions'

2014-10-04 Thread David Suárez
Hi Moritz,

El Viernes, 3 de octubre de 2014 16:45:52 Moritz Mühlenhoff escribió:
 On Sun, Sep 28, 2014 at 06:41:58PM +0200, David Suárez wrote:
  Source: fbi
  Version: 2.07-14
  Severity: serious
  Tags: jessie sid
  User: debian...@lists.debian.org
  Usertags: qa-ftbfs-20140926 qa-ftbfs
  Justification: FTBFS on amd64
  
  Hi,
  
  During a rebuild of all packages in sid, your package failed to build on
  amd64.
 
 Hi David,
 thanks for your archive rebuilds. I tried to reproduce this, but fbi builds
 fine with current unstable. Can you still reproduce it?

Just build it again some minutes ago. It's still failing.

Failure lines:

 Make.config written, edit if needed
 
  CC  exiftran.o
   CC  genthumbnail.o
   CC  jpegtools.o
   CC  jpeg/transupp.o
 In file included from jpeg/transupp.c:21:0:
 jpeg/jpeglib.h:40:0: warning: JPEG_LIB_VERSION redefined
  #define JPEG_LIB_VERSION80 /* Compatibility version 8.0 */
  ^
 In file included from jpeg/jinclude.h:20:0,
  from jpeg/transupp.c:20:
 /usr/include/x86_64-linux-gnu/jconfig.h:5:0: note: this is the location of 
the previous definition
  #define JPEG_LIB_VERSION 62
  ^
   CC  filter.o
   CC  op.o
   CC  readers.o
   CC  rd/read-jpeg.o
   LD  exiftran
 jpeg/transupp.o: In function `jtransform_request_workspace':
 /«PKGBUILDDIR»/jpeg/transupp.c:892: undefined reference to 
`jpeg_core_output_dimensions'
 collect2: error: ld returned 1 exit status
 make[2]: *** [exiftran] Error 1
 mk/Compile.mk:83: recipe for target 'exiftran' failed
 make[2]: Leaving directory '/«PKGBUILDDIR»'
 make[1]: *** [override_dh_auto_build] Error 2
 debian/rules:7: recipe for target 'override_dh_auto_build' failed
 make[1]: Leaving directory '/«PKGBUILDDIR»'
 make: *** [build] Error 2
 debian/rules:4: recipe for target 'build' failed
 dpkg-buildpackage: error: debian/rules build gave error exit status 2

--

  David


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763264: ooniprobe: FTBFS: Tests failures

2014-10-04 Thread David Suárez
Hi,

El Lunes, 29 de septiembre de 2014 13:26:55 Arturo Filastò escribió:
 It appears that there is something on the machine that is running the
 test that has already binded to port .
 Since you say that this is run on a clean, minimal EC2 instance, this
 behavior is quite peculiar.
 Nonetheless the unittest should figure out that something is listening
 on that port and pick another random port.

Sorry for be late. Yes, in  it's running approx. We use it for caching 
build depends.

--

  David


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#762959: [libclang1-3.5] ABI break: missing libclang.so.1

2014-09-28 Thread David Suárez
Package: libclang1-3.5
Version: 1:3.5-3

New version, 1:3.5-3, have this bug too. I see 311 FTBFS on last archive 
rebuild.

Logs at: http://aws-logs.debian.net/ftbfs-logs/2014/09/26/

Example pkgs:

 alsa-lib alsaplayer apr-util aroarfw assimp atlas-cpp

  David


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763212: kxd: FTBFS: Tests failures

2014-09-28 Thread David Suárez
Source: kxd
Version: 0.12-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[1]: Entering directory '/«PKGBUILDDIR»'
 go build -o ./out/kxd ./kxd
 go build --tags netgo -a -o ./out/kxc ./kxc
 python tests/run_tests -b
 .F.
 ==
 FAIL: test_server_cert (__main__.TrickyRequests)
 --
 Traceback (most recent call last):
   File tests/run_tests, line 408, in test_server_cert
 self.assertTrue(sock.cipher()[2]  128)
 AssertionError: False is not true
 
 Stdout:
 Launching server:  /«PKGBUILDDIR»/out/kxd 
 --data_dir=/tmp/kxdtest-uCp7Qz/config-server-vQZQFI/data 
 --key=/tmp/kxdtest-uCp7Qz/config-server-vQZQFI/key.pem 
 --cert=/tmp/kxdtest-uCp7Qz/config-server-vQZQFI/cert.pem 
 --logfile=/tmp/kxdtest-uCp7Qz/config-server-vQZQFI/log
 
 --
 Ran 11 tests in 18.263s
 
 FAILED (failures=1)
 
 Stdout:
 Launching server:  /«PKGBUILDDIR»/out/kxd 
 --data_dir=/tmp/kxdtest-uCp7Qz/config-server-vQZQFI/data 
 --key=/tmp/kxdtest-uCp7Qz/config-server-vQZQFI/key.pem 
 --cert=/tmp/kxdtest-uCp7Qz/config-server-vQZQFI/cert.pem 
 --logfile=/tmp/kxdtest-uCp7Qz/config-server-vQZQFI/log
 make[1]: *** [test] Error 1
 dh_auto_test: make -j1 test returned exit code 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/09/26/kxd_0.12-2_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763213: haskell-libsystemd-journal: FTBFS: No uhc found

2014-09-28 Thread David Suárez
Source: haskell-libsystemd-journal
Version: 1.1.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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/cdbs/1/rules/buildcore.mk:110: CDBS WARNING:
 DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
 if test ! -e Setup.lhs -a ! -e Setup.hs; then echo No setup script found!; 
 exit 1; fi
 for setup in Setup.lhs Setup.hs; do if test -e $setup; then ghc --make $setup 
 -o debian/hlibrary.setup; exit 0; fi; done
 [1 of 1] Compiling Main ( Setup.hs, Setup.o )
 Linking debian/hlibrary.setup ...
 debian/hlibrary.setup configure --ghc -v2 \
   --prefix=/usr --libdir=/usr/lib/haskell-packages/ghc/lib \
   --builddir=dist-ghc \
   --haddockdir=/usr/lib/ghc-doc/haddock/libsystemd-journal-1.1.0/ 
 --datasubdir=libsystemd-journal\
   --htmldir=/usr/share/doc/libghc-libsystemd-journal-doc/html/ 
 --enable-library-profiling  \
  
 Configuring libsystemd-journal-1.1.0...
 Dependency base ==4.6.*: using base-4.6.0.1
 Dependency bytestring =0.9.1: using bytestring-0.10.0.2
 Dependency hashable =1.1.2.5: using hashable-1.2.1.0
 Dependency hsyslog -any: using hsyslog-1.6
 Dependency pipes =4.0: using pipes-4.1.2
 Dependency pipes-safe =2.0: using pipes-safe-2.2.0
 Dependency text =0.1  1.2: using text-0.11.3.1
 Dependency transformers =0.3: using transformers-0.3.0.0
 Dependency uniplate =1.6: using uniplate-1.6.11
 Dependency unix-bytestring =0.3.2  0.4: using unix-bytestring-0.3.5.4
 Dependency unordered-containers =0.1  0.3: using
 unordered-containers-0.2.5.0
 Dependency uuid -any: using uuid-1.3.3
 Dependency vector =0.4  0.11: using vector-0.10.0.1
 hlibrary.setup: Missing dependency on a foreign library:
 * Missing C library: systemd-journal
 This problem can usually be solved by installing the system package that
 provides this library (you may need the -dev version). If the library is
 already installed but in a non-standard location then you can use the flags
 --extra-include-dirs= and --extra-lib-dirs= to specify where it is.
 Using Cabal-1.16.0 compiled by ghc-7.6
 Using compiler: ghc-7.6.3
 Using install prefix: /usr
 Binaries installed in: /usr/bin
 Libraries installed in:
 /usr/lib/haskell-packages/ghc/lib/libsystemd-journal-1.1.0/ghc-7.6.3
 Private binaries installed in: /usr/libexec
 Data files installed in: /usr/share/libsystemd-journal
 Documentation installed in: /usr/share/doc/libsystemd-journal-1.1.0
 No alex found
 Using ar found on system at: /usr/bin/ar
 No c2hs found
 No cpphs found
 No ffihugs found
 Using gcc version 4.9.1 found on system at: /usr/bin/gcc
 Using ghc version 7.6.3 found on system at: /usr/bin/ghc
 Using ghc-pkg version 7.6.3 found on system at: /usr/bin/ghc-pkg
 No greencard found
 Using haddock version 2.13.2 found on system at: /usr/bin/haddock
 No happy found
 No hmake found
 Using hpc version 0.6 found on system at: /usr/bin/hpc
 Using hsc2hs version 0.67 found on system at: /usr/bin/hsc2hs
 Using hscolour version 1.20 found on system at: /usr/bin/HsColour
 No hugs found
 No jhc found
 Using ld found on system at: /usr/bin/ld
 No lhc found
 No lhc-pkg found
 No nhc98 found
 No pkg-config found
 Using ranlib found on system at: /usr/bin/ranlib
 Using strip found on system at: /usr/bin/strip
 Using tar found on system at: /bin/tar
 No uhc found
 make: *** [configure-ghc-stamp] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/haskell-libsystemd-journal_1.1.0-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763211: libappindicator: FTBFS: src/app-indicator.c:480: Error: AppIndicator: multiple @arg1 parameters for identifier AppIndicator::new-label:

2014-09-28 Thread David Suárez
Source: libappindicator
Version: 0.4.92-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
 -I../../src -I..   -D_FORTIFY_SOURCE=2 -pthread 
 -I/usr/include/libdbusmenu-gtk3-0.4 -I/usr/include/libdbusmenu-glib-0.4 
 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 
 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 
 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
 -I/usr/include/libindicator3-0.4  -Wall -Werror 
 -DG_LOG_DOMAIN=\libappindicator\ -g -O2 -fstack-protector-strong -Wformat 
 -Werror=format-security -Wall -c -o libappindicator3_la-app-indicator.lo 
 `test -f 'app-indicator.c' || echo '../../src/'`app-indicator.c
 libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. 
 -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libdbusmenu-gtk3-0.4 
 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 
 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
 -I/usr/include/freetype2 -I/usr/include/libpng12 
 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 
 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libindicator3-0.4 
 -Wall -Werror -DG_LOG_DOMAIN=\libappindicator\ -g -O2 
 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c 
 ../../src/app-indicator.c  -fPIC -DPIC -o 
 .libs/libappindicator3_la-app-indicator.o
 ../../src/app-indicator.c: In function 'app_indicator_set_property':
 ../../src/app-indicator.c:902:6: error: 'gtk_status_icon_set_title' is 
 deprecated (declared at 
 /usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:143) 
 [-Werror=deprecated-declarations]
   gtk_status_icon_set_title(priv-status_icon, priv-title ? priv-title 
 : );
   ^
 ../../src/app-indicator.c: In function 'fallback':
 ../../src/app-indicator.c:1512:2: error: 'gtk_status_icon_new' is deprecated 
 (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:84) 
 [-Werror=deprecated-declarations]
   GtkStatusIcon * icon = gtk_status_icon_new();
   ^
 ../../src/app-indicator.c:1514:2: error: 'gtk_status_icon_set_name' is 
 deprecated (declared at 
 /usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:148) 
 [-Werror=deprecated-declarations]
   gtk_status_icon_set_name(icon, app_indicator_get_id(self));
   ^
 ../../src/app-indicator.c:1517:3: error: 'gtk_status_icon_set_title' is 
 deprecated (declared at 
 /usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:143) 
 [-Werror=deprecated-declarations]
gtk_status_icon_set_title(icon, title);
^
 ../../src/app-indicator.c: In function 'status_icon_changes':
 ../../src/app-indicator.c:1614:3: error: 'gtk_status_icon_set_visible' is 
 deprecated (declared at 
 /usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:151) 
 [-Werror=deprecated-declarations]
gtk_status_icon_set_visible(icon, FALSE);
^
 ../../src/app-indicator.c:1619:3: error: 'gtk_status_icon_set_visible' is 
 deprecated (declared at 
 /usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:151) 
 [-Werror=deprecated-declarations]
gtk_status_icon_set_visible(icon, TRUE);
^
 ../../src/app-indicator.c:1624:3: error: 'gtk_status_icon_set_visible' is 
 deprecated (declared at 
 /usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:151) 
 [-Werror=deprecated-declarations]
gtk_status_icon_set_visible(icon, TRUE);
^
 ../../src/app-indicator.c:1630:4: error: 'gtk_status_icon_set_from_file' is 
 deprecated (declared at 
 /usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:100) 
 [-Werror=deprecated-declarations]
 gtk_status_icon_set_from_file(icon, icon_name);
 ^
 ../../src/app-indicator.c:1635:5: error: 'gtk_status_icon_set_from_icon_name' 
 is deprecated (declared at 
 /usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:106) 
 [-Werror=deprecated-declarations]
  gtk_status_icon_set_from_icon_name(icon, longname);
  ^
 ../../src/app-indicator.c:1637:5: error: 'gtk_status_icon_set_from_icon_name' 
 is deprecated (declared at 
 /usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:106) 
 [-Werror=deprecated-declarations]
  

Bug#763218: python-pysam: FTBFS: Tests failures

2014-09-28 Thread David Suárez
Source: python-pysam
Version: 0.7.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 ==
 FAIL: testBAM (__main__.TestUnmappedReads)
 --
 Traceback (most recent call last):
   File ./pysam_test_offline.py, line 998, in testBAM
 self.assertEqual( len(list(samfile.fetch( until_eof = True))), 2 )
 AssertionError: 0 != 2
 
 --
 Ran 158 tests in 9.110s
 
 FAILED (failures=2, errors=31)
 E: pybuild pybuild:256: test: plugin custom failed with: exit code=1: cd 
 tests  PYTHONPATH=/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build python2.7 
 ./pysam_test_offline.py
 dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
 code 13
 make[1]: *** [override_dh_auto_test] Error 13
 debian/rules:29: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/python-pysam_0.7.7-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763215: latexila: FTBFS: latexila.vala:139.43-139.46: error: duplicating List instance, use unowned variable or explicitly invoke copy method

2014-09-28 Thread David Suárez
Source: latexila
Version: 2.12.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 main_window.vala:404.54-404.58: warning: Gtk.Stock has been deprecated since 
 3.10
 main_window.vala:409.51-409.55: warning: Gtk.Stock has been deprecated since 
 3.10
 latexila.vala:139.43-139.46: error: duplicating List instance, use unowned 
 variable or explicitly invoke copy method
 Gtk.Window.set_default_icon_list (list);
   
 
 ** (valac:27484): CRITICAL **: vala_ccode_function_call_add_argument: 
 assertion 'expr != NULL' failed
 Compilation failed: 1 error(s), 154 warning(s)
 make[4]: *** [latexila_vala.stamp] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/latexila_2.12.1-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763214: libcitygml: FTBFS: dh_install: openscenegraph-plugin-citygml-shared missing files (usr/lib/osgPlugins-*/*.so), aborting

2014-09-28 Thread David Suárez
Source: libcitygml
Version: 0.14+svn134-1+3p2p0
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[2]: Entering directory 
 '/«BUILDDIR»/libcitygml-0.14+svn134/obj-x86_64-linux-gnu'
 make[2]: Nothing to be done for 'preinstall'.
 make[2]: Leaving directory 
 '/«BUILDDIR»/libcitygml-0.14+svn134/obj-x86_64-linux-gnu'
 Install the project...
 /usr/bin/cmake -P cmake_install.cmake
 -- Install configuration: None
 -- Installing: 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/lib/x86_64-linux-gnu/libcitygml.so.0.0.0
 -- Installing: 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/lib/x86_64-linux-gnu/libcitygml.so.0
 -- Installing: 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/lib/x86_64-linux-gnu/libcitygml.so
 -- Installing: 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/lib/x86_64-linux-gnu/libcitygml.a
 -- Installing: 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/include/citygml.h
 -- Installing: 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/include/vecs.h
 -- Installing: 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/citygml.pc
 -- Installing: 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/bin/citygml2vrml
 -- Removed runtime path from 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/bin/citygml2vrml
 -- Installing: 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/bin/citygmltest
 -- Removed runtime path from 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/bin/citygmltest
 -- Installing: 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/lib/x86_64-linux-gnu/osgPlugins-3.2.1/ReaderWriterCityGML.so
 -- Removed runtime path from 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/lib/x86_64-linux-gnu/osgPlugins-3.2.1/ReaderWriterCityGML.so
 -- Installing: 
 /«BUILDDIR»/libcitygml-0.14+svn134/debian/tmp/usr/lib/x86_64-linux-gnu/osgPlugins-3.2.1/ReaderWriterCityGML.a
 make[1]: Leaving directory 
 '/«BUILDDIR»/libcitygml-0.14+svn134/obj-x86_64-linux-gnu'
   cd /«BUILDDIR»/libcitygml-0.14+svn134
dh_install
   install -d debian/libcitygml0//usr/lib/x86_64-linux-gnu
   cp -a debian/tmp/usr/lib/x86_64-linux-gnu/libcitygml.so.0 
 debian/libcitygml0//usr/lib/x86_64-linux-gnu/
   cp -a debian/tmp/usr/lib/x86_64-linux-gnu/libcitygml.so.0.0.0 
 debian/libcitygml0//usr/lib/x86_64-linux-gnu/
   install -d debian/libcitygml0-dev//usr/include
   cp -a debian/tmp/usr/include/citygml.h 
 debian/libcitygml0-dev//usr/include/
   cp -a debian/tmp/usr/include/vecs.h debian/libcitygml0-dev//usr/include/
   install -d debian/libcitygml0-dev//usr/lib/x86_64-linux-gnu
   cp -a debian/tmp/usr/lib/x86_64-linux-gnu/libcitygml.a 
 debian/libcitygml0-dev//usr/lib/x86_64-linux-gnu/
   cp -a debian/tmp/usr/lib/x86_64-linux-gnu/libcitygml.so 
 debian/libcitygml0-dev//usr/lib/x86_64-linux-gnu/
   install -d debian/libcitygml0-dev//usr/lib/x86_64-linux-gnu/pkgconfig
   cp -a debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/citygml.pc 
 debian/libcitygml0-dev//usr/lib/x86_64-linux-gnu/pkgconfig/
   install -d debian/libcitygml0-bin//usr/bin
   cp -a debian/tmp/usr/bin/citygml2vrml debian/libcitygml0-bin//usr/bin/
   cp -a debian/tmp/usr/bin/citygmltest debian/libcitygml0-bin//usr/bin/
 dh_install: openscenegraph-plugin-citygml-shared missing files 
 (usr/lib/osgPlugins-*/*.so), aborting
 debian/rules:10: recipe for target 'binary' failed
 make: *** [binary] Error 255

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/libcitygml_0.14+svn134-1+3p2p0_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763216: wkhtmltopdf: FTBFS: ../lib/pdfsettings.hh:25:20: fatal error: QPrinter: No such file or directory

2014-09-28 Thread David Suárez
Source: wkhtmltopdf
Version: 0.12.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 g++ -c -m64 -pipe -g -O2 -fstack-protector-strong -Wformat 
 -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC 
 -DQT_SHARED -DVERSION=0.12.1 -DFULL_VERSION=0.12.1 -DBUILDING_DLL 
 -DQT_NO_DEBUG -DQT_WEBKITWIDGETS_LIB -DQT_SVG_LIB -DQT_XMLPATTERNS_LIB 
 -DQT_WEBKIT_LIB -DQT_WIDGETS_LIB -DQT_NETWORK_LIB -DQT_GUI_LIB -DQT_CORE_LIB 
 -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -I. -I../../include 
 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -o pdfsettings.o 
 ../lib/pdfsettings.cc
 In file included from ../lib/pdfsettings.cc:26:0:
 ../lib/pdfsettings.hh:25:20: fatal error: QPrinter: No such file or directory
  #include QPrinter
 ^
 compilation terminated.
 make[2]: *** [pdfsettings.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/wkhtmltopdf_0.12.1-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763219: zeitgeist: FTBFS: Makefile:505: recipe for target 'docs_vala' failed

2014-09-28 Thread David Suárez
Source: zeitgeist
Version: 0.9.14-2.2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[4]: Entering directory '/«PKGBUILDDIR»/doc/libzeitgeist'
 /usr/bin/valadoc \
   -o docs_vala \
   --force --pkg gio-2.0 --pkg gio-unix-2.0 --pkg sqlite3 --pkg 
 zeitgeist-internal --vapidir ../../libzeitgeist --basedir ../../libzeitgeist 
 --package-name zeitgeist-2.0 --package-version 0.9.14 
 ../../libzeitgeist/data-source.vala 
 ../../libzeitgeist/data-source-registry.vala ../../libzeitgeist/mimetype.vala 
 ../../libzeitgeist/enumerations.vala ../../libzeitgeist/event.vala 
 ../../libzeitgeist/errors.vala ../../libzeitgeist/subject.vala 
 ../../libzeitgeist/timerange.vala ../../libzeitgeist/index.vala 
 ../../libzeitgeist/log.vala ../../libzeitgeist/timestamp.vala 
 ../../libzeitgeist/monitor.vala ../../libzeitgeist/ontology-uris.vala 
 ../../libzeitgeist/ontology.vala ../../libzeitgeist/queued-proxy-wrapper.vala 
 ../../libzeitgeist/remote.vala ../../libzeitgeist/result-set.vala 
 ../../libzeitgeist/simple-result-set.vala ../../libzeitgeist/utils.vala   \
   
 error: Package `glib-2.0' not found in specified Vala API directories or 
 GObject-Introspection GIR directories
 error: glib-2.0 not found in specified Vala API directories
 error: Package `gobject-2.0' not found in specified Vala API directories or 
 GObject-Introspection GIR directories
 error: gobject-2.0 not found in specified Vala API directories
 error: Package `gio-2.0' not found in specified Vala API directories or 
 GObject-Introspection GIR directories
 error: Package `gio-2.0' not found in specified Vala API directories or 
 GObject-Introspection GIR directories
 error: Package `gio-unix-2.0' not found in specified Vala API directories or 
 GObject-Introspection GIR directories
 error: Package `gio-unix-2.0' not found in specified Vala API directories or 
 GObject-Introspection GIR directories
 error: Package `sqlite3' not found in specified Vala API directories or 
 GObject-Introspection GIR directories
 error: Package `sqlite3' not found in specified Vala API directories or 
 GObject-Introspection GIR directories
 Failed: 10 error(s), 0 warning(s)
 Makefile:505: recipe for target 'docs_vala' failed
 make[4]: *** [docs_vala] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/zeitgeist_0.9.14-2.2_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763220: dwb: FTBFS: completion.c:92: undefined reference to `GTK_ALIGNMENT'

2014-09-28 Thread David Suárez
Source: dwb
Version: 20140702hg-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 cc -o dwb
 completion.o: In function `completion_get_completion_item':
 /«PKGBUILDDIR»/src/completion.c:92: undefined reference to `GTK_ALIGNMENT'
 view.o: In function `view_create_web_view':
 /«PKGBUILDDIR»/src/view.c:1756: undefined reference to `GTK_ALIGNMENT'
 dwb.o: In function `dwb_init_gui':
 /«PKGBUILDDIR»/src/dwb.c:4804: undefined reference to `GTK_ALIGNMENT'
 download.o: In function `download_add_progress_label':
 /«PKGBUILDDIR»/src/download.c:425: undefined reference to `GTK_ALIGNMENT'
 collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/dwb_20140702hg-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763222: django-guardian: FTBFS: Tests failures

2014-09-28 Thread David Suárez
Source: django-guardian
Version: 1.2.4-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[2]: Entering directory '/«PKGBUILDDIR»/docs'
 sphinx-build -b html -d build/doctrees   . build/html
 Making output directory...
 Running Sphinx v1.2.3
 [NOTE] In order to build PDF you need rst2pdf with version =0.16
 loading pickled environment... failed: [Errno 2] No such file or directory: 
 '/«PKGBUILDDIR»/docs/build/doctrees/environment.pickle'
 building [html]: targets for 32 source files that are out of date
 updating environment: 32 added, 0 changed, 0 removed
 reading sources... [  3%] api/guardian.admin
 reading sources... [  6%] api/guardian.backends
 reading sources... [  9%] api/guardian.core
 reading sources... [ 12%] api/guardian.decorators
 reading sources... [ 15%] api/guardian.forms
 reading sources... [ 18%] api/guardian.management.commands
 reading sources... [ 21%] api/guardian.managers
 reading sources... [ 25%] api/guardian.mixins
 reading sources... [ 28%] api/guardian.models
 reading sources... [ 31%] api/guardian.shortcuts
 reading sources... [ 34%] api/guardian.templatetags.guardian_tags
 reading sources... [ 37%] api/guardian.utils
 reading sources... [ 40%] api/index
 reading sources... [ 43%] configuration
 reading sources... [ 46%] develop/changes
 reading sources... [ 50%] develop/example_project
 reading sources... [ 53%] develop/index
 reading sources... [ 56%] develop/overview
 reading sources... [ 59%] develop/supported-versions
 reading sources... [ 62%] develop/testing
 reading sources... [ 65%] index
 reading sources... [ 68%] installation
 reading sources... [ 71%] license
 reading sources... [ 75%] overview
 reading sources... [ 78%] userguide/admin-integration
 reading sources... [ 81%] userguide/assign
 reading sources... [ 84%] userguide/caveats
 reading sources... [ 87%] userguide/check
 reading sources... [ 90%] userguide/custom-user-model
 reading sources... [ 93%] userguide/index
 reading sources... [ 96%] userguide/performance
 reading sources... [100%] userguide/remove
 
 /«PKGBUILDDIR»/guardian/core.py:docstring of 
 guardian.core.ObjectPermissionChecker:18: WARNING: Field list ends without a 
 blank line; unexpected unindent.
 /«PKGBUILDDIR»/guardian/forms.py:docstring of 
 guardian.forms.BaseObjectPermissionsForm:5: WARNING: Field list ends without 
 a blank line; unexpected unindent.
 /«PKGBUILDDIR»/guardian/shortcuts.py:docstring of 
 guardian.shortcuts.get_objects_for_user:18: WARNING: Field list ends without 
 a blank line; unexpected unindent.
 looking for now-outdated files... none found
 pickling environment... done
 checking consistency... done
 preparing documents... done
 writing output... [  3%] api/guardian.admin
 writing output... [  6%] api/guardian.backends
 writing output... [  9%] api/guardian.core
 writing output... [ 12%] api/guardian.decorators
 writing output... [ 15%] api/guardian.forms
 writing output... [ 18%] api/guardian.management.commands
 writing output... [ 21%] api/guardian.managers
 writing output... [ 25%] api/guardian.mixins
 writing output... [ 28%] api/guardian.models
 writing output... [ 31%] api/guardian.shortcuts
 writing output... [ 34%] api/guardian.templatetags.guardian_tags
 writing output... [ 37%] api/guardian.utils
 writing output... [ 40%] api/index
 writing output... [ 43%] configuration
 writing output... [ 46%] develop/changes
 writing output... [ 50%] develop/example_project
 writing output... [ 53%] develop/index
 writing output... [ 56%] develop/overview
 writing output... [ 59%] develop/supported-versions
 writing output... [ 62%] develop/testing
 writing output... [ 65%] index
 writing output... [ 68%] installation
 writing output... [ 71%] license
 writing output... [ 75%] overview
 writing output... [ 78%] userguide/admin-integration
 writing output... [ 81%] userguide/assign
 writing output... [ 84%] userguide/caveats
 writing output... [ 87%] userguide/check
 writing output... [ 90%] userguide/custom-user-model
 writing output... [ 93%] userguide/index
 writing output... [ 96%] userguide/performance
 writing output... [100%] userguide/remove
 
 writing additional files... genindex py-modindex search
 copying static files... done
 copying extra files... done
 dumping search index... done
 dumping object inventory... done
 build succeeded, 3 warnings.
 
 Build finished. The HTML pages are in build/html.
 make[2]: Leaving directory '/«PKGBUILDDIR»/docs'
 # rename file license.txt
 mv -f /«PKGBUILDDIR»/docs/build/html/_sources/license.txt \
   /«PKGBUILDDIR»/docs/build/html/_sources/lic.txt 
 sed -i 's:href=_sources/license.txt:href=_sources/lic.txt:g' \
   /«PKGBUILDDIR»/docs/build/html/license.html
 rm -rf /«PKGBUILDDIR»/docs/guardian
 make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_test 

Bug#763217: libnet-ping-external-perl: FTBFS: Tests failures

2014-09-28 Thread David Suárez
Source: libnet-ping-external-perl
Version: 0.13-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 Linux ip-172-31-12-31 2.6.32-5-xen-amd64 #1 SMP Sun Sep 23 13:49:30 UTC 2012 
 x86_64 GNU/Linux
 Perl version: This is perl 5, version 20, subversion 1 (v5.20.1) built for 
 x86_64-linux-gnu-thread-multi
 Ping help: Usage: ping [-aAbBdDfhLnOqrRUvV] [-c count] [-i interval] [-I 
 interface]
 [-m mark] [-M pmtudisc_option] [-l preload] [-p pattern] [-Q tos]
 [-s packetsize] [-S sndbuf] [-t ttl] [-T timestamp_option]
 [-w deadline] [-W timeout] [hop1 ...] destination
 
 -
 If any of the above tests failed, please e-mail the bits between the dashed
 lines or content of 'NPE.out' to alexchorny AT gmail.com This will help me in
 fixing this code for maximum portability to your platform. Thanks!
 
 Tests: fail
 make[1]: *** [test_dynamic] Error 1
 dh_auto_test: make -j1 test returned exit code 2
 Makefile:813: recipe for target 'test_dynamic' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/libnet-ping-external-perl_0.13-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763221: haskell-gtk3: FTBFS: Couldn't match type `CInt' with `()'

2014-09-28 Thread David Suárez
Source: haskell-gtk3
Version: 0.12.5.6-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 [113 of 198] Compiling Graphics.UI.Gtk.ModelView.CellRendererSpinner ( 
 dist-ghc/build/Graphics/UI/Gtk/ModelView/CellRendererSpinner.hs, 
 dist-ghc/build/Graphics/UI/Gtk/ModelView/CellRendererSpinner.o )
 [114 of 198] Compiling Graphics.UI.Gtk.ModelView.CellRenderer ( 
 dist-ghc/build/Graphics/UI/Gtk/ModelView/CellRenderer.hs, 
 dist-ghc/build/Graphics/UI/Gtk/ModelView/CellRenderer.o )
 [115 of 198] Compiling Graphics.UI.Gtk.ModelView.CellLayout ( 
 dist-ghc/build/Graphics/UI/Gtk/ModelView/CellLayout.hs, 
 dist-ghc/build/Graphics/UI/Gtk/ModelView/CellLayout.o )
 [116 of 198] Compiling Graphics.UI.Gtk.MenuComboToolbar.ComboBox ( 
 dist-ghc/build/Graphics/UI/Gtk/MenuComboToolbar/ComboBox.hs, 
 dist-ghc/build/Graphics/UI/Gtk/MenuComboToolbar/ComboBox.o )
 [117 of 198] Compiling Graphics.UI.Gtk.Multiline.TextTagTable ( 
 dist-ghc/build/Graphics/UI/Gtk/Multiline/TextTagTable.hs, 
 dist-ghc/build/Graphics/UI/Gtk/Multiline/TextTagTable.o )
 
 Graphics/UI/Gtk/Multiline/TextTagTable.chs:88:3:
 Couldn't match type `CInt' with `()'
 Expected type: IO ()
   Actual type: IO CInt
 In the return type of a call of `\ (TextTagTable arg1)
(TextTag arg2)
- withForeignPtr arg1
   $ \ argPtr1 - withForeignPtr arg2 
 $ \ argPtr2 - ...'
 In the expression:
   (\ (TextTagTable arg1) (TextTag arg2)
  - withForeignPtr arg1
 $ \ argPtr1
 - withForeignPtr arg2
$ \ argPtr2 - gtk_text_tag_table_add argPtr1 argPtr2)
 (toTextTagTable self) (toTextTag tag)
 In an equation for `textTagTableAdd':
 textTagTableAdd self tag
   = (\ (TextTagTable arg1) (TextTag arg2)
- withForeignPtr arg1
   $ \ argPtr1 - withForeignPtr arg2 $ \ argPtr2 - ...)
   (toTextTagTable self) (toTextTag tag)
 make: *** [build-ghc-stamp] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/haskell-gtk3_0.12.5.6-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763223: codelite: FTBFS: ld: cannot find -llldb

2014-09-28 Thread David Suárez
Source: codelite
Version: 6.1.1+dfsg-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 /usr/bin/c++  -fPIC -g -O2 -fPIE -fstack-protector-strong -Wformat 
 -Werror=format-security -D_FORTIFY_SOURCE=2  -O2 -pthread  -fPIE -pie 
 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -shared  -o ../lib/LLDBDebugger.so 
 CMakeFiles/LLDBDebugger.dir/lldbbreakpointmodel.cpp.o 
 CMakeFiles/LLDBDebugger.dir/UI_lldbdebugger_bitmaps.cpp.o 
 CMakeFiles/LLDBDebugger.dir/UI.cpp.o 
 CMakeFiles/LLDBDebugger.dir/LLDBTooltip.cpp.o 
 CMakeFiles/LLDBDebugger.dir/LLDBThreadsView.cpp.o 
 CMakeFiles/LLDBDebugger.dir/LLDBSettingDialog.cpp.o 
 CMakeFiles/LLDBDebugger.dir/LLDBPlugin.cpp.o 
 CMakeFiles/LLDBDebugger.dir/LLDBNewBreakpointDlg.cpp.o 
 CMakeFiles/LLDBDebugger.dir/LLDBLocalsView.cpp.o 
 CMakeFiles/LLDBDebugger.dir/LLDBCallStack.cpp.o 
 CMakeFiles/LLDBDebugger.dir/LLDBBreakpointsPane.cpp.o 
 CMakeFiles/LLDBDebugger.dir/FolderMappingDlg.cpp.o ../lib/libLLDBProtocol.a 
 -llldb -Wl,-rpath,/usr/lib/codelite -L/usr/lib/x86_64-linux-gnu -pthread 
 -lwx_gtk2u_aui-3.0 -lwx_gtk2u_propgrid-3.0 -lwx_gtk2u_stc-3.0 
 -lwx_gtk2u_richtext-3.0 -lwx_gtk2u_ribbon-3.0 -lwx_gtk2u_xrc-3.0 
 -lwx_gtk2u_html-3.0 -lwx_gtk2u_qa-3.0 -lwx_gtk2u_adv-3.0 -lwx_gtk2u_core-3.0 
 -lwx_baseu_xml-3.0 -lwx_baseu_net-3.0 -lwx_baseu-3.0 
 -L/«BUILDDIR»/codelite-6.1.1+dfsg/obj-x86_64-linux-gnu/lib -lLLDBProtocol 
 -llibcodelite -lplugin -lwxsqlite3-3.0 -lsqlite3 
 /usr/bin/ld: cannot find -llldb
 collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/codelite_6.1.1+dfsg-3_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.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763232: mate-panel: FTBFS: cp: cannot stat 'debian/tmp/usr/lib/girepository-1.0/': No such file or directory

2014-09-28 Thread David Suárez
Source: mate-panel
Version: 1.8.0+dfsg1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[1]: Entering directory '/«BUILDDIR»/mate-panel-1.8.0+dfsg1'
 I: mate-panel_1.8.0+dfsg1
 rm -f debian/tmp/usr/lib/*/*.la
 rm -f debian/tmp/usr/share/MateConf/gsettings/mate-panel.convert
 dh_install --list-missing
 cp: cannot stat 'debian/tmp/usr/lib/girepository-1.0/': No such file or 
 directory
 dh_install: cp -a debian/tmp/usr/lib/girepository-1.0/ 
 debian/gir1.2-mate-panel//usr/lib/ returned exit code 1
 make[1]: *** [override_dh_install] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/mate-panel_1.8.0+dfsg1-2_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763229: gnumeric: FTBFS: Tests failures

2014-09-28 Thread David Suárez
Source: gnumeric
Version: 1.12.17-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 30 of 35 tests failed
 (80 tests were not run)
 Please report to http://bugzilla.gnome.org/enter_bug.cgi?product=gnumeric
 =
 make[4]: *** [check-TESTS] Error 1
 make[3]: *** [check-am] Error 2
 Makefile:551: recipe for target 'check-TESTS' failed
 make[4]: Leaving directory '/«PKGBUILDDIR»/test'
 Makefile:674: recipe for target 'check-am' failed
 make[3]: Leaving directory '/«PKGBUILDDIR»/test'
 make[2]: *** [check-recursive] Error 1
 dh_auto_test: make -j1 check returned exit code 2
 Makefile:643: recipe for target 'check-recursive' failed
 make[2]: Leaving directory '/«PKGBUILDDIR»'
 make[1]: [override_dh_auto_test] Error 2 (ignored)
 debian/rules:80: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/gnumeric_1.12.17-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763225: r-cran-rms: FTBFS: ERROR: lazy loading failed for package 'rms'

2014-09-28 Thread David Suárez
Source: r-cran-rms
Version: 4.2-0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[1]: Entering directory '/«PKGBUILDDIR»/src'
 make[1]: Leaving directory '/«PKGBUILDDIR»/src'
 installing to /«PKGBUILDDIR»/debian/r-cran-rms/usr/lib/R/site-library/rms/libs
 ** R
 ** demo
 ** preparing package for lazy loading
 Error in loadNamespace(j - i[[1L]], c(lib.loc, .libPaths()), versionCheck = 
 vI[[j]]) : 
   there is no package called 'foreign'
 Error : package 'Hmisc' could not be loaded
 ERROR: lazy loading failed for package 'rms'
 * removing '/«PKGBUILDDIR»/debian/r-cran-rms/usr/lib/R/site-library/rms'
 make: *** [R_any_arch] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/r-cran-rms_4.2-0-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763228: cbmc: FTBFS: ld: final link failed: Bad value

2014-09-28 Thread David Suárez
Source: cbmc
Version: 4.9-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs.
 /usr/bin/ld: final link failed: Bad value
 collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/09/26/cbmc_4.9-3_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763231: python-bottle: FTBFS: Tests failures

2014-09-28 Thread David Suárez
Source: python-bottle
Version: 0.12.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 AssertionError: AttributeError: 'NoneType' object has no attribute 'split'
 
 ==
 FAIL: test_path_create (test_resources.TestResourceManager)
 --
 Traceback (most recent call last):
   File /«PKGBUILDDIR»/test/test_resources.py, line 20, in test_path_create
 self.assertEqual(exists, False)
 AssertionError: True != False
 
 --
 Ran 328 tests in 11.741s
 
 FAILED (failures=1, errors=2)
 make[1]: *** [override_dh_auto_test] Error 1
 debian/rules:26: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/python-bottle_0.12.7-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763224: luminance-hdr: FTBFS: helpbrowser.cpp:48:20: fatal error: QPrinter: No such file or directory

2014-09-28 Thread David Suárez
Source: luminance-hdr
Version: 2.4.0-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[4]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
 /usr/bin/cmake -E cmake_progress_report 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 
 [ 52%] Building CXX object 
 src/HelpBrowser/CMakeFiles/helpbrowser.dir/helpbrowser.cpp.o
 cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/HelpBrowser  /usr/bin/c++   
 -DBRANCH_PREDICTION -DDEMOSAICING_GPL2 -DDEMOSAICING_GPL3 -DHAVE_CCFITS 
 -DHAVE_FFTW3F -DLHDR_CXX11_ENABLED -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
 -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_WEBKITWIDGETS_LIB 
 -DQT_WEBKIT_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB -g -O2 -fstack-protector-strong 
 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2  -std=c++11 -fopenmp 
 -fPIC -I/usr/include/exiv2 -I/usr/include/x86_64-linux-gnu 
 -I/usr/include/OpenEXR -I/usr/include/libraw -I/«PKGBUILDDIR»/src 
 -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src 
 -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
 -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/HelpBrowser -isystem 
 /usr/include/x86_64-linux-gnu/qt5 -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
 /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
 /usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets-Wall 
 -Wno-unknown-pragmas -ffast-math -o 
 CMakeFiles/helpbrowser.dir/helpbrowser.cpp.o -c 
 /«PKGBUILDDIR»/src/HelpBrowser/helpbrowser.cpp
 /«PKGBUILDDIR»/src/HelpBrowser/helpbrowser.cpp:48:20: fatal error: QPrinter: 
 No such file or directory
  #include QPrinter
 ^
 compilation terminated.
 src/HelpBrowser/CMakeFiles/helpbrowser.dir/build.make:82: recipe for target 
 'src/HelpBrowser/CMakeFiles/helpbrowser.dir/helpbrowser.cpp.o' failed
 make[4]: *** [src/HelpBrowser/CMakeFiles/helpbrowser.dir/helpbrowser.cpp.o] 
 Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/luminance-hdr_2.4.0-5_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.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763226: jackson-dataformat-yaml: FTBFS: Compilation failure

2014-09-28 Thread David Suárez
Source: jackson-dataformat-yaml
Version: 2.2.3-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[1]: Entering directory '/«PKGBUILDDIR»'
 sh debian/replace-generate.sh 
 src/main/java/com/fasterxml/jackson/dataformat/yaml/PackageVersion.java
 dh_auto_configure
 make[1]: Leaving directory '/«PKGBUILDDIR»'
jh_linkjars -O--buildsystem=maven
dh_auto_build -O--buildsystem=maven
 [INFO] 
 NOTE: Maven is executing in offline mode. Any artifacts not already in your 
 local
 repository will be inaccessible.
 
 [INFO] Scanning for projects...
 [INFO] Searching repository for plugin with prefix: 'javadoc'.
 [INFO] 
 
 [INFO] Building Jackson-dataformat-YAML
 [INFO]task-segment: [package, javadoc:jar]
 [INFO] 
 
 [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 3 resources
 [INFO] [compiler:compile {execution: default-compile}]
 [WARNING] File encoding has not been set, using platform encoding 
 ANSI_X3.4-1968, i.e. build is platform dependent!
 [INFO] Compiling 6 source files to /«PKGBUILDDIR»/target/classes
 [INFO] -
 [ERROR] COMPILATION ERROR : 
 [INFO] -
 [ERROR] 
 /«PKGBUILDDIR»/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLFactory.java:[586,4]
  error: method does not override or implement a method from a supertype
 [ERROR] 
 /«PKGBUILDDIR»/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLFactory.java:[593,4]
  error: method does not override or implement a method from a supertype
 [ERROR] 
 /«PKGBUILDDIR»/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLFactory.java:[600,4]
  error: method does not override or implement a method from a supertype
 [ERROR] 
 /«PKGBUILDDIR»/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLFactory.java:[618,4]
  error: method does not override or implement a method from a supertype
 [ERROR] 
 /«PKGBUILDDIR»/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLFactory.java:[630,4]
  error: method does not override or implement a method from a supertype
 [INFO] 5 errors 
 [INFO] -
 [INFO] 
 
 [ERROR] BUILD FAILURE
 [INFO] 
 
 [INFO] Compilation failure
 
 /«PKGBUILDDIR»/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLFactory.java:[586,4]
  error: method does not override or implement a method from a supertype
 /«PKGBUILDDIR»/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLFactory.java:[593,4]
  error: method does not override or implement a method from a supertype
 /«PKGBUILDDIR»/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLFactory.java:[600,4]
  error: method does not override or implement a method from a supertype
 /«PKGBUILDDIR»/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLFactory.java:[618,4]
  error: method does not override or implement a method from a supertype
 /«PKGBUILDDIR»/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLFactory.java:[630,4]
  error: method does not override or implement a method from a supertype
 
 [INFO] 
 
 [INFO] For more information, run Maven with the -e switch
 [INFO] 
 
 [INFO] Total time: 3 seconds
 [INFO] Finished at: Sun Sep 28 09:12:49 UTC 2014
 [INFO] Final Memory: 19M/205M
 [INFO] 
 
 dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
 /usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
  -Dclassworlds.conf=/etc/maven2/m2-debian.conf 
 -Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties 
 org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml 
 -Ddebian.dir=/«PKGBUILDDIR»/debian 
 -Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo package javadoc:jar 
 javadoc:aggregate returned exit code 1
 make: *** [build] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/jackson-dataformat-yaml_2.2.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 

Bug#763233: hedgewars: FTBFS: /bin/sh: 1: Qt4::lrelease: not found

2014-09-28 Thread David Suárez
Source: hedgewars
Version: 0.9.20.5-9
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
 /usr/bin/cmake -E cmake_progress_report 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 100
 [ 91%] Generating hedgewars_bg.qm
 cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/share/hedgewars/Data/Locale  
 Qt4::lrelease /«PKGBUILDDIR»/share/hedgewars/Data/Locale/hedgewars_bg.ts -qm 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/share/hedgewars/Data/Locale/hedgewars_bg.qm
 /bin/sh: 1: Qt4::lrelease: not found
 make[3]: *** [share/hedgewars/Data/Locale/hedgewars_bg.qm] Error 127

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/hedgewars_0.9.20.5-9_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763227: libinline-c-perl: FTBFS: Tests failures

2014-09-28 Thread David Suárez
Source: libinline-c-perl
Version: 0.61-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
   Non-zero exit status: 2
   Parse errors: Bad plan.  You planned 1 tests but ran 0.
 t/14void_arg.t(Wstat: 512 Tests: 0 Failed: 0)
   Non-zero exit status: 2
   Parse errors: No plan found in TAP output
 t/14void_arg_PRD.t(Wstat: 512 Tests: 0 Failed: 0)
   Non-zero exit status: 2
   Parse errors: No plan found in TAP output
 t/24prefix.t  (Wstat: 512 Tests: 0 Failed: 0)
   Non-zero exit status: 2
   Parse errors: No plan found in TAP output
 Files=29, Tests=76, 56 wallclock secs ( 0.12 usr  0.17 sys + 48.14 cusr 14.06 
 csys = 62.49 CPU)
 Result: FAIL
 Failed 8/29 test programs. 0/76 subtests failed.
 make[1]: *** [test_dynamic] Error 255
 Makefile:848: recipe for target 'test_dynamic' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/libinline-c-perl_0.61-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763237: gav: FTBFS: ld: final link failed: Bad value

2014-09-28 Thread David Suárez
Source: gav
Version: 0.9.0-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs.
 /usr/bin/ld: final link failed: Bad value
 collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/09/26/gav_0.9.0-3_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763235: lightspark: FTBFS: abc.cpp:38:36: fatal error: llvm/Analysis/Verifier.h: No such file or directory

2014-09-28 Thread David Suárez
Source: lightspark
Version: 0.7.2-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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): 
 [ 40%] Building CXX object src/CMakeFiles/spark.dir/scripting/abc.cpp.o
 cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src  /usr/bin/c++   
 -DAUDIO_BACKEND=\pulse sdl\ -DBOOST_MULTI_INDEX_DISABLE_SERIALIZATION 
 -DENABLE_CURL -DENABLE_LIBAVCODEC -DENABLE_RTMP 
 -DGNASH_PATH=\/usr/bin/gnash\ -DHAVE_ATOMIC -DHAVE_AVCODECID 
 -DHAVE_AVCODEC_ALLOC_CONTEXT3 -DHAVE_AVCODEC_DECODE_AUDIO4 
 -DHAVE_AVCODEC_DECODE_VIDEO2 -DHAVE_AVCODEC_OPEN2 -DHAVE_AVFORMAT_CLOSE_INPUT 
 -DHAVE_AVFORMAT_FIND_STREAM_INFO -DHAVE_AVIO_ALLOC_CONTEXT 
 -DHAVE_LIBAVRESAMPLE -DHAVE_NEW_GLIBMM_THREAD_API 
 -DHAVE_SUPPORT_TARGETSELECT_H -DLLVM_31 -DLLVM_34 
 -DLS_DATADIR=\/usr/share/lightspark\ 
 -DPRIVATELIBDIR=\/usr/lib/lightspark\ -DXMLPP_2_35_1 -Dspark_EXPORTS -g -O2 
 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
  -Wall -Wnon-virtual-dtor -Woverloaded-virtual -pipe -fvisibility=hidden 
 -fvisibility-inlines-hidden -std=c++0x -Wdisabled-optimization -Wextra 
 -Wno-unused-parameter -Wno-invalid-offsetof -fPIC 
 -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/usr/include/glibmm-2.4 
 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 
 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 
 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/lib/llvm-3.5/include 
 -I/usr/include/libxml2 -I/usr/include/libxml++-2.6 
 -I/usr/lib/libxml++-2.6/include -I/usr/include/pango-1.0 -I/usr/include/cairo 
 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 
 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 
 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/harfbuzz -I/«PKGBUILDDIR»/src 
 -I/«PKGBUILDDIR»/src/scripting-o CMakeFiles/spark.dir/scripting/abc.cpp.o 
 -c /«PKGBUILDDIR»/src/scripting/abc.cpp
 /«PKGBUILDDIR»/src/scripting/abc.cpp:38:36: fatal error: 
 llvm/Analysis/Verifier.h: No such file or directory
  #include llvm/Analysis/Verifier.h
 ^
 compilation terminated.
 make[3]: *** [src/CMakeFiles/spark.dir/scripting/abc.cpp.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/lightspark_0.7.2-5_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.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763236: packagekit-qt: FTBFS: daemonproxy.h:160:7: error: redefinition of 'class DaemonProxy'

2014-09-28 Thread David Suárez
Source: packagekit-qt
Version: 0.9.2-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
 /usr/bin/cmake -E cmake_progress_report 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 7
 [ 50%] Building CXX object src/CMakeFiles/packagekitqt4.dir/bitfield.cpp.o
 cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src  /usr/bin/c++   
 -DLOCALSTATEDIR=\/var\ -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_SQL_LIB 
 -Dpackagekitqt4_EXPORTS -g -O2 -fstack-protector-strong -Wformat 
 -Werror=format-security -D_FORTIFY_SOURCE=2  -g -fPIC -isystem 
 /usr/include/qt4 -isystem /usr/include/qt4/QtDBus -isystem 
 /usr/include/qt4/QtSql -isystem /usr/include/qt4/QtCore 
 -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
 -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src
 -std=gnu++11 -o CMakeFiles/packagekitqt4.dir/bitfield.cpp.o -c 
 /«PKGBUILDDIR»/src/bitfield.cpp
 /usr/bin/cmake -E cmake_progress_report 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 8
 [ 57%] Building CXX object src/CMakeFiles/packagekitqt4.dir/daemon.cpp.o
 cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src  /usr/bin/c++   
 -DLOCALSTATEDIR=\/var\ -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_SQL_LIB 
 -Dpackagekitqt4_EXPORTS -g -O2 -fstack-protector-strong -Wformat 
 -Werror=format-security -D_FORTIFY_SOURCE=2  -g -fPIC -isystem 
 /usr/include/qt4 -isystem /usr/include/qt4/QtDBus -isystem 
 /usr/include/qt4/QtSql -isystem /usr/include/qt4/QtCore 
 -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
 -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src
 -std=gnu++11 -o CMakeFiles/packagekitqt4.dir/daemon.cpp.o -c 
 /«PKGBUILDDIR»/src/daemon.cpp
 In file included from /«PKGBUILDDIR»/src/daemon.cpp:28:0:
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/daemonproxy.h:160:7: error: 
 redefinition of 'class DaemonProxy'
  class DaemonProxy: public QDBusAbstractInterface
^
 In file included from /«PKGBUILDDIR»/src/daemon.cpp:28:0:
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/daemonproxy.h:26:7: error: previous 
 definition of 'class DaemonProxy'
  class DaemonProxy: public QDBusAbstractInterface
^
 In file included from /«PKGBUILDDIR»/src/daemon.cpp:28:0:
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/daemonproxy.h:206:26: error: 
 'namespace org::freedesktop::PackageKit { }' redeclared as different kind of 
 symbol
  namespace PackageKit {
   ^
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/daemonproxy.h:205:27: note: previous 
 declaration 'typedef class DaemonProxy org::freedesktop::PackageKit'
  typedef ::DaemonProxy PackageKit;
^
 make[3]: *** [src/CMakeFiles/packagekitqt4.dir/daemon.cpp.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/packagekit-qt_0.9.2-4_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763238: gambas3: FTBFS: dh_install: gambas3-gb-jit missing files (usr/lib/gambas3/gb.jit.*), aborting

2014-09-28 Thread David Suárez
Source: gambas3
Version: 3.5.4-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[3]: Entering directory '/«PKGBUILDDIR»'
 make[3]: Nothing to be done for 'install-data-am'.
 make[3]: Leaving directory '/«PKGBUILDDIR»'
 make[2]: Leaving directory '/«PKGBUILDDIR»'
 make[1]: Leaving directory '/«PKGBUILDDIR»'
 find /«PKGBUILDDIR»/debian/tmp/usr -name *.la -delete
 find /«PKGBUILDDIR»/debian/tmp/usr -name *.png -perm /ugo+x -exec chmod 644 
 \{} \;
 chmod 644 /«PKGBUILDDIR»/debian/tmp/usr/share/gambas3/gb.sdl/_default.bdf
 dh_install --sourcedir=debian/tmp -XCOPYING -XLicense -XLicence -i 
 dh_installman debian/gambas3.1 -p gambas3-ide
 dh_installman debian/gbs3.1 -p gambas3-script
 dh_installman debian/gbw3.1 -p gambas3-script
 dh_link -i
 dh_fixperms -i
 dh_gencontrol -i
 dpkg-gencontrol: warning: Depends field of package gambas3-gb-memcached: 
 unknown substitution variable ${shlibs:Depends}
 dpkg-gencontrol: warning: Depends field of package gambas3-gb-args: unknown 
 substitution variable ${shlibs:Depends}
 dh_installdocs -i
 dh_installchangelogs -i
 dh_lintian -i
 dh_compress -i
 dh_builddeb -i
 dpkg-deb: building package `gambas3' in `../gambas3_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-form-stock' in 
 `../gambas3-gb-form-stock_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-examples' in 
 `../gambas3-examples_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-chart' in 
 `../gambas3-gb-chart_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-db-form' in 
 `../gambas3-gb-db-form_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-form' in 
 `../gambas3-gb-form_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-form-dialog' in 
 `../gambas3-gb-form-dialog_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-form-mdi' in 
 `../gambas3-gb-form-mdi_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-report' in 
 `../gambas3-gb-report_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-settings' in 
 `../gambas3-gb-settings_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-web' in 
 `../gambas3-gb-web_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-xml-rpc' in 
 `../gambas3-gb-xml-rpc_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-ide' in `../gambas3-ide_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-script' in 
 `../gambas3-script_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-eval-highlight' in 
 `../gambas3-gb-eval-highlight_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-memcached' in 
 `../gambas3-gb-memcached_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-args' in 
 `../gambas3-gb-args_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-map' in 
 `../gambas3-gb-map_3.5.4-1_all.deb'.
 dpkg-deb: building package `gambas3-gb-logging' in 
 `../gambas3-gb-logging_3.5.4-1_all.deb'.
 dh_install --sourcedir=debian/tmp -a
 dh_install: gambas3-gb-jit missing files (usr/lib/gambas3/gb.jit.*), aborting
 make: *** [binary-arch] Error 255

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/09/26/gambas3_3.5.4-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763234: anjuta: FTBFS: error: Package `libvala-0.24' not found in specified Vala API directories or GObject-Introspection GIR directories

2014-09-28 Thread David Suárez
Source: anjuta
Version: 2:3.12.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[4]: Leaving directory '/«PKGBUILDDIR»/plugins/language-support-js'
 Making all in language-support-python
 make[4]: Entering directory '/«PKGBUILDDIR»/plugins/language-support-python'
 /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
 -I../..  -I/usr/include/libxml2  -pthread -I/usr/include/gtk-3.0 
 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
 -I/usr/include/freetype2 -I/usr/include/libpng12 
 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 
 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -pthread 
 -I/usr/include/libgdl-3.0 -I/usr/include/libxml2 -I/usr/include/gtk-3.0 
 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
 -I/usr/include/freetype2 -I/usr/include/libpng12 
 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 
 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -I../.. -I../../libanjuta 
 -DPACKAGE_PIXMAPS_DIR=\/usr/share/pixmaps/anjuta\ 
 -DPACKAGE_LIB_DIR=\/usr/lib/anjuta\ 
 -DPACKAGE_DATA_DIR=\/usr/share/anjuta\ -DSCRIPTS_DIR=\/usr/lib/anjuta\ 
 -DG_LOG_DOMAIN=\language-support-python\ -D_FORTIFY_SOURCE=2 -Wall 
 -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes 
 -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self 
 -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs  -g -O2 
 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o 
 plugin.lo plugin.c
 libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/libxml2 
 -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 
 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 
 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
 -I/usr/include/libgdl-3.0 -I/usr/include/libxml2 -I/usr/include/gtk-3.0 
 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
 -I/usr/include/freetype2 -I/usr/include/libpng12 
 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 
 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../.. -I../../libanjuta 
 -DPACKAGE_PIXMAPS_DIR=\/usr/share/pixmaps/anjuta\ 
 -DPACKAGE_LIB_DIR=\/usr/lib/anjuta\ 
 -DPACKAGE_DATA_DIR=\/usr/share/anjuta\ -DSCRIPTS_DIR=\/usr/lib/anjuta\ 
 -DG_LOG_DOMAIN=\language-support-python\ -D_FORTIFY_SOURCE=2 -Wall 
 -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes 
 -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self 
 -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O2 
 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c plugin.c  
 -fPIC -DPIC -o .libs/plugin.o
 plugin.c: In function 'on_check_finished':
 plugin.c:76:52: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations]
 GTK_STOCK_OK,
 ^
 /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
 -I../..  -I/usr/include/libxml2  -pthread -I/usr/include/gtk-3.0 
 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
 -I/usr/include/freetype2 -I/usr/include/libpng12 
 

Bug#763239: its: FTBFS: there is no package called 'foreign

2014-09-28 Thread David Suárez
Source: its
Version: 1.1.8-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
  fakeroot debian/rules binary
 /usr/share/cdbs/1/rules/simple-patchsys.mk:31: CDBS WARNING:
 simple-patchsys.mk is deprecated since 0.4.85 - please use source format 3.0 
 (quilt) instead
 test -x debian/rules
 dh_testroot
 dh_clean -k 
 dh_clean: dh_clean -k is deprecated; use dh_prep instead
 dh_installdirs -A 
 mkdir -p .
 dh_installdirsusr/lib/R/site-library
 echo R:Depends=r-base-core (= 3.1.1-1)  debian/r-cran-its.substvars
 if test -f /usr/bin/xvfb-run; then\
xvfb-run -a\
   R CMD INSTALL -l 
 /«PKGBUILDDIR»/debian/r-cran-its/usr/lib/R/site-library --clean \
. ;\
   else\
R CMD INSTALL -l 
 /«PKGBUILDDIR»/debian/r-cran-its/usr/lib/R/site-library   \
   --clean  . ;\
   fi
 * installing *source* package 'its' ...
 ** R
 ** inst
 ** preparing package for lazy loading
 Error in loadNamespace(j - i[[1L]], c(lib.loc, .libPaths()), versionCheck = 
 vI[[j]]) : 
   there is no package called 'foreign'
 Error : package 'Hmisc' could not be loaded
 ERROR: lazy loading failed for package 'its'
 * removing '/«PKGBUILDDIR»/debian/r-cran-its/usr/lib/R/site-library/its'
 make: *** [R_any_arch] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/09/26/its_1.1.8-4_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763241: udisks2: FTBFS: dh_install: gir1.2-udisks-2.0 missing files (usr/lib/girepository*/), aborting

2014-09-28 Thread David Suárez
Source: udisks2
Version: 2.1.3-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[1]: Entering directory '/«PKGBUILDDIR»'
 dh_install -X.la --fail-missing
 dh_install: gir1.2-udisks-2.0 missing files (usr/lib/girepository*/), aborting
 debian/rules:23: recipe for target 'override_dh_install' failed
 make[1]: *** [override_dh_install] Error 255

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/09/26/udisks2_2.1.3-3_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763240: python-django-jsonfield: FTBFS: Tests failures

2014-09-28 Thread David Suárez
Source: python-django-jsonfield
Version: 0.9.13-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 Traceback (most recent call last):
   File debian/run_tests.py, line 23, in module
 management.call_command('test')
   File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py, 
 line 93, in call_command
 app_name = get_commands()[name]
   File /usr/lib/python2.7/dist-packages/django/utils/lru_cache.py, line 
 101, in wrapper
 result = user_function(*args, **kwds)
   File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py, 
 line 73, in get_commands
 for app_config in reversed(list(apps.get_app_configs())):
   File /usr/lib/python2.7/dist-packages/django/apps/registry.py, line 137, 
 in get_app_configs
 self.check_apps_ready()
   File /usr/lib/python2.7/dist-packages/django/apps/registry.py, line 124, 
 in check_apps_ready
 raise AppRegistryNotReady(Apps aren't loaded yet.)
 django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
 make[1]: *** [override_dh_auto_test] Error 1
 debian/rules:10: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/python-django-jsonfield_0.9.13-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763242: kst: FTBFS: command-line:0:1: error: macro names must be identifiers

2014-09-28 Thread David Suárez
Source: kst
Version: 2.0.3-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[4]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
 /usr/bin/cmake -E cmake_progress_report 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 
 [  0%] Generating kstcore_pch.h.gch
 cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst  /usr/bin/cmake -E remove 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst/kstcore_pch.h.gch
 cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst  /usr/bin/c++ 
 -DKST_HAVE_SVN_REVISION_H  -DQT_GUI_LIB -DQT_CORE_LIB -DBUILD_KSTCORE -g -O2 
 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
 -Wall -lrt -g -fPIC -D -I /usr/include/qt4 -I /usr/include/qt4/QtGui -I 
 /usr/include/qt4/QtCore -I /«PKGBUILDDIR»/obj-x86_64-linux-gnu -I 
 /usr/include/qt4/QtDesigner -I /usr/include/qt4/QtDeclarative -I 
 /usr/include/qt4/QtScriptTools -I /usr/include/qt4/QtDBus -I 
 /usr/include/qt4/QtDesigner -I /usr/include/qt4/QtXml -I 
 /usr/include/qt4/QtSql -I /usr/include/qt4/QtOpenGL -I 
 /usr/include/qt4/QtNetwork -I /usr/include/qt4/QtXmlPatterns -I 
 /usr/include/qt4/QtHelp -I /usr/include/qt4/QtUiTools -I 
 /usr/include/qt4/QtTest -I /usr/include/qt4/QtScript -I 
 /usr/include/qt4/QtSvg -I /usr/include/qt4/Qt3Support -I 
 /usr/include/qt4/QtGui -I /usr/include/qt4/QtCore -I 
 /usr/share/qt4/mkspecs/default -I /usr/include/qt4 -I /usr/include/qt4/QtCore 
 -I /«PKGBUILDDIR»/src/libkst -I 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst -c 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst/kstcore_pch.h -o 
 /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst/kstcore_pch.h.gch
 command-line:0:1: error: macro names must be identifiers
 make[4]: *** [src/libkst/kstcore_pch.h.gch] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/09/26/kst_2.0.3-2_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.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763244: givaro: FTBFS: dh_install: libgivaro-doc missing files (docs/givaro-html/*), aborting

2014-09-28 Thread David Suárez
Source: givaro
Version: 3.7.2-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
 make[3]: Entering directory '/«PKGBUILDDIR»'
  /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/bin'
  /usr/bin/install -c givaro-config givaro-makefile 
 '/«PKGBUILDDIR»/debian/tmp/usr/bin'
  /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/include'
  /usr/bin/install -c -m 644 givaro-config.h 
 '/«PKGBUILDDIR»/debian/tmp/usr/include'
 make[3]: Leaving directory '/«PKGBUILDDIR»'
 make[2]: Leaving directory '/«PKGBUILDDIR»'
 make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_install -O--parallel
 dh_install: libgivaro-doc missing files (docs/givaro-html/*), aborting
 make: *** [binary] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/09/26/givaro_3.7.2-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763245: axiom: FTBFS: make[4]: *** [/«PKGBUILDDIR»/int/algebra/CABMON.nrlib/code.o] Error 134

2014-09-28 Thread David Suárez
Source: axiom
Version: 20140801-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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): 
 sa07 compiling ALAGG.spad to ALAGG.nrlib
 sa06 copying ALAGG.nrlib to ALAGG.o
 GCL (GNU Common Lisp)  2.6.11 CLtL1Sep  6 2014 12:34:43
 Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
 Binary License:  GPL due to GPL'ed components: (XGCL READLINE UNEXEC)
 Modifications of this banner must retain notice of a compatible license
 Dedicated to the memory of W. Schelter
 
 Use (help) to get some basic information on how to use GCL.
 Temporary directory for compiler files set to /«PKGBUILDDIR»/obj/tmp/
 
 
 
 sa07 compiling BOOLEAN.spad to BOOLEAN.nrlib
 sa06 copying BOOLEAN.nrlib to BOOLEAN.o
 GCL (GNU Common Lisp)  2.6.11 CLtL1Sep  6 2014 12:34:43
 Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
 Binary License:  GPL due to GPL'ed components: (XGCL READLINE UNEXEC)
 Modifications of this banner must retain notice of a compatible license
 Dedicated to the memory of W. Schelter
 
 Use (help) to get some basic information on how to use GCL.
 Temporary directory for compiler files set to /«PKGBUILDDIR»/obj/tmp/
 
 
 
 sa07 compiling CABMON.spad to CABMON.nrlib
 make[4]: *** [/«PKGBUILDDIR»/int/algebra/CABMON.nrlib/code.o] Error 134

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/axiom_20140801-5_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.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



  1   2   3   4   5   6   7   8   9   10   >