Processed: freefem++: diff for NMU version 3.38.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 807200 + pending
Bug #807200 [src:freefem++] freefem++: Update build dependencies for GSL 2.x
Added tag(s) pending.

-- 
807200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#807200: freefem++: diff for NMU version 3.38.1-1.1

[Mattia Rizzolo]

Control: tags 807200 + pending

Dear maintainer,

I've prepared an NMU for freefem++ (versioned as 3.38.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for freefem++-3.38.1 freefem++-3.38.1

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru freefem++-3.38.1/debian/changelog freefem++-3.38.1/debian/changelog
--- freefem++-3.38.1/debian/changelog	2015-09-01 21:16:58.0 +
+++ freefem++-3.38.1/debian/changelog	2016-01-26 11:13:59.0 +
@@ -1,3 +1,13 @@
+freefem++ (3.38.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807200
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 11:13:42 +
+
 freefem++ (3.38.1-1) unstable; urgency=medium
 
   * Imported Upstream version 3.38.1 (Closes: #793237)
diff -Nru freefem++-3.38.1/debian/control freefem++-3.38.1/debian/control
--- freefem++-3.38.1/debian/control	2015-08-30 22:41:24.0 +
+++ freefem++-3.38.1/debian/control	2016-01-26 11:13:40.0 +
@@ -10,7 +10,7 @@
  libxpm-dev, libmumps-scotch-dev, libmumps-ptscotch-dev,
  libfltk1.3-dev | libfltk-dev, freeglut3-dev, ghostscript, imagemagick,
  texlive, texlive-extra-utils, texlive-latex-extra, texlive-font-utils, 
- libfftw3-dev, libgsl0-dev,
+ libfftw3-dev, libgsl-dev,
  libhypre-dev, 
  libarpack2-dev, libsuitesparse-dev,
  libmumps-dev, libblacs-mpi-dev, libscalapack-mpi-dev,


signature.asc
Description: PGP signature

Bug#811428: [debian-mysql] Bug#811428: Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Tue, Jan 26, 2016 at 01:11:45AM -0800, Lars Tangvald wrote:
> Wheezy package has been built and tested
> 
> At the moment it's just on my personal github at
> https://github.com/ltangvald/mysql-5.5/tree/debian/wheezy, but we
> should get it uploaded to Alioth soon.
> Attaching the debdiff and debian/ diff.

Thank you looks good to me.

I haven't seen the same for jessie, but assuming it is basically the
same and matching what you showed me initially from git, let's go
ahead with an upload.

Please remember to do the jessie-security first (built with -sa) and
then after ~20 minutes the wheezy-security one (explicitly without
-sa, and not including the orig source tarball; this is due to some
limitation in the archive software).

The upload needs to be signed by a a key in the DD keyring.

I will then wait for the builds and then take care of releasing the
packages with a DSA.

Regards,
Salvatore


signature.asc
Description: Digital signature

Bug#812745: ruby-fog-xenserver and ruby-fog: error when trying to install together

[Ralf Treinen]

Package: ruby-fog,ruby-fog-xenserver
Version: ruby-fog/1.34.0-2
Version: ruby-fog-xenserver/0.2.3-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-01-26
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:



Extracting templates from packages: 55%
Extracting templates from packages: 100%
Preconfiguring packages ...
Selecting previously unselected package libyaml-0-2:amd64.
(Reading database ... 10941 files and directories currently installed.)
Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ...
Unpacking libyaml-0-2:amd64 (0.1.6-3) ...
Selecting previously unselected package gcc-5-base:amd64.
Preparing to unpack .../gcc-5-base_5.3.1-7_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.3.1-7) ...
Setting up gcc-5-base:amd64 (5.3.1-7) ...
(Reading database ... 10955 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.3.1-7_amd64.deb ...
Unpacking libstdc++6:amd64 (5.3.1-7) over (4.8.2-19) ...
Processing triggers for libc-bin (2.21-7) ...
Setting up libstdc++6:amd64 (5.3.1-7) ...
Processing triggers for libc-bin (2.21-7) ...
Selecting previously unselected package libssl1.0.2:amd64.
(Reading database ... 10969 files and directories currently installed.)
Preparing to unpack .../libssl1.0.2_1.0.2e-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2e-1) ...
Selecting previously unselected package libgcrypt20:amd64.
Preparing to unpack .../libgcrypt20_1.6.4-5_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.6.4-5) ...
Selecting previously unselected package libicu55:amd64.
Preparing to unpack .../libicu55_55.1-7_amd64.deb ...
Unpacking libicu55:amd64 (55.1-7) ...
Selecting previously unselected package libxml2:amd64.
Preparing to unpack .../libxml2_2.9.3+dfsg1-1_amd64.deb ...
Unpacking libxml2:amd64 (2.9.3+dfsg1-1) ...
Selecting previously unselected package openssl.
Preparing to unpack .../openssl_1.0.2e-1_amd64.deb ...
Unpacking openssl (1.0.2e-1) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20160104_all.deb ...
Unpacking ca-certificates (20160104) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-4) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.1.0+dfsg-2_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.0+dfsg-2) ...
Selecting previously unselected package libxslt1.1:amd64.
Preparing to unpack .../libxslt1.1_1.1.28-2.1_amd64.deb ...
Unpacking libxslt1.1:amd64 (1.1.28-2.1) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../rubygems-integration_1.10_all.deb ...
Unpacking rubygems-integration (1.10) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../ruby-power-assert_0.2.6-1_all.deb ...
Unpacking ruby-power-assert (0.2.6-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../ruby-test-unit_3.1.7-1_all.deb ...
Unpacking ruby-test-unit (3.1.7-1) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../ruby-minitest_5.8.4-1_all.deb ...
Unpacking ruby-minitest (5.8.4-1) ...
Selecting previously unselected package libruby2.2:amd64.
Preparing to unpack .../libruby2.2_2.2.4-1_amd64.deb ...
Unpacking libruby2.2:amd64 (2.2.4-1) ...
Selecting previously unselected package ruby2.2.
Preparing to unpack .../ruby2.2_2.2.4-1_amd64.deb ...
Unpacking ruby2.2 (2.2.4-1) ...
Selecting previously unselected package ruby.
Preparing to unpack .../ruby_1%3a2.2.4_all.deb ...
Unpacking ruby (1:2.2.4) ...
Selecting previously unselected package ruby-blankslate.
Preparing to unpack .../ruby-blankslate_3.1.3-1_all.deb ...
Unpacking ruby-blankslate (3.1.3-1) ...
Selecting previously unselected package ruby-builder.
Preparing to unpack .../ruby-builder_3.2.2-4_all.deb ...
Unpacking ruby-builder (3.2.2-4) ...
Selecting previously unselected package ruby-cfpropertylist.
Preparing to unpack .../ruby-cfpropertylist_2.2.8-1_all.deb ...
Unpacking ruby-cfpropertylist (2.2.8-1) ...
Selecting previously unselected package ruby-excon.
Preparing to unpack .../ruby-excon_0.45.1-2_all.deb ...
Unpacking ruby-excon (0.45.1-2) ...
Selecting previously unselected package ruby-fission.
Preparing to unpack .../ruby-fission_0.5.0-2_all.deb ...
Unpacking ruby-fission (0.5.0-2) ...
Selecting previously unselected package ruby-formatador.
Preparing to unpack .../ruby-formatador_0.2.1-2_all.deb ...
Unpacking ruby-formatador (0.2.1-2) ...
Selecting previously unselected package ruby-mime-types.
Preparing to unpack .../ruby-mime-types_2.6.1-1_all.deb ...
Unpacking ruby-mime-types (2.6.1-1) ...
Selecting previously unselected package ruby-net-ssh.
Preparing to unpack .../ruby-net-ssh_1%3a2.9.2-2_all.deb ...
Unpacking 

Bug#812743: libsdformat4-dev and libsdformat3-dev: error when trying to install together

[Ralf Treinen]

Package: libsdformat3-dev,libsdformat4-dev
Version: libsdformat3-dev/3.06.00-3
Version: libsdformat4-dev/4.0.0-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-01-26
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:



Extracting templates from packages: 42%
Extracting templates from packages: 85%
Extracting templates from packages: 100%
Selecting previously unselected package libgmp10:amd64.
(Reading database ... 10941 files and directories currently installed.)
Preparing to unpack .../libgmp10_2%3a6.1.0+dfsg-2_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.0+dfsg-2) ...
Selecting previously unselected package libmpfr4:amd64.
Preparing to unpack .../libmpfr4_3.1.3-2_amd64.deb ...
Unpacking libmpfr4:amd64 (3.1.3-2) ...
Selecting previously unselected package libmpc3:amd64.
Preparing to unpack .../libmpc3_1.0.3-1_amd64.deb ...
Unpacking libmpc3:amd64 (1.0.3-1) ...
Selecting previously unselected package gcc-5-base:amd64.
Preparing to unpack .../gcc-5-base_5.3.1-7_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.3.1-7) ...
Processing triggers for libc-bin (2.21-7) ...
Setting up gcc-5-base:amd64 (5.3.1-7) ...
(Reading database ... 10971 files and directories currently installed.)
Preparing to unpack .../libgcc1_1%3a5.3.1-7_amd64.deb ...
Unpacking libgcc1:amd64 (1:5.3.1-7) over (1:4.8.2-19) ...
Processing triggers for libc-bin (2.21-7) ...
Setting up libgcc1:amd64 (1:5.3.1-7) ...
Processing triggers for libc-bin (2.21-7) ...
(Reading database ... 10971 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.3.1-7_amd64.deb ...
Unpacking libstdc++6:amd64 (5.3.1-7) over (4.8.2-19) ...
Processing triggers for libc-bin (2.21-7) ...
Setting up libstdc++6:amd64 (5.3.1-7) ...
Processing triggers for libc-bin (2.21-7) ...
Selecting previously unselected package libboost-iostreams1.58.0:amd64.
(Reading database ... 10985 files and directories currently installed.)
Preparing to unpack .../libboost-iostreams1.58.0_1.58.0+dfsg-4.1_amd64.deb ...
Unpacking libboost-iostreams1.58.0:amd64 (1.58.0+dfsg-4.1) ...
Selecting previously unselected package binutils.
Preparing to unpack .../binutils_2.25.90.20160101-2_amd64.deb ...
Unpacking binutils (2.25.90.20160101-2) ...
Selecting previously unselected package libisl15:amd64.
Preparing to unpack .../libisl15_0.16.1-1_amd64.deb ...
Unpacking libisl15:amd64 (0.16.1-1) ...
Selecting previously unselected package cpp-5.
Preparing to unpack .../cpp-5_5.3.1-7_amd64.deb ...
Unpacking cpp-5 (5.3.1-7) ...
Selecting previously unselected package cpp.
Preparing to unpack .../cpp_4%3a5.3.1-1_amd64.deb ...
Unpacking cpp (4:5.3.1-1) ...
Selecting previously unselected package libcc1-0:amd64.
Preparing to unpack .../libcc1-0_5.3.1-7_amd64.deb ...
Unpacking libcc1-0:amd64 (5.3.1-7) ...
Selecting previously unselected package libgomp1:amd64.
Preparing to unpack .../libgomp1_5.3.1-7_amd64.deb ...
Unpacking libgomp1:amd64 (5.3.1-7) ...
Selecting previously unselected package libitm1:amd64.
Preparing to unpack .../libitm1_5.3.1-7_amd64.deb ...
Unpacking libitm1:amd64 (5.3.1-7) ...
Selecting previously unselected package libatomic1:amd64.
Preparing to unpack .../libatomic1_5.3.1-7_amd64.deb ...
Unpacking libatomic1:amd64 (5.3.1-7) ...
Selecting previously unselected package libasan2:amd64.
Preparing to unpack .../libasan2_5.3.1-7_amd64.deb ...
Unpacking libasan2:amd64 (5.3.1-7) ...
Selecting previously unselected package liblsan0:amd64.
Preparing to unpack .../liblsan0_5.3.1-7_amd64.deb ...
Unpacking liblsan0:amd64 (5.3.1-7) ...
Selecting previously unselected package libtsan0:amd64.
Preparing to unpack .../libtsan0_5.3.1-7_amd64.deb ...
Unpacking libtsan0:amd64 (5.3.1-7) ...
Selecting previously unselected package libubsan0:amd64.
Preparing to unpack .../libubsan0_5.3.1-7_amd64.deb ...
Unpacking libubsan0:amd64 (5.3.1-7) ...
Selecting previously unselected package libcilkrts5:amd64.
Preparing to unpack .../libcilkrts5_5.3.1-7_amd64.deb ...
Unpacking libcilkrts5:amd64 (5.3.1-7) ...
Selecting previously unselected package libmpx0:amd64.
Preparing to unpack .../libmpx0_5.3.1-7_amd64.deb ...
Unpacking libmpx0:amd64 (5.3.1-7) ...
Selecting previously unselected package libquadmath0:amd64.
Preparing to unpack .../libquadmath0_5.3.1-7_amd64.deb ...
Unpacking libquadmath0:amd64 (5.3.1-7) ...
Selecting previously unselected package libgcc-5-dev:amd64.
Preparing to unpack .../libgcc-5-dev_5.3.1-7_amd64.deb ...
Unpacking libgcc-5-dev:amd64 (5.3.1-7) ...
Selecting previously unselected package gcc-5.
Preparing to unpack .../gcc-5_5.3.1-7_amd64.deb ...
Unpacking gcc-5 (5.3.1-7) ...
Selecting previously unselected package gcc.
Preparing to unpack .../gcc_4%3a5.3.1-1_amd64.deb ...
Unpacking gcc (4:5.3.1-1) ...
Selecting previously unselected package libc-dev-bin.
Preparing to unpack 

Bug#812742: libirstlm-dev and libduo-dev: error when trying to install together

[Ralf Treinen]

Package: libduo-dev,libirstlm-dev
Version: libduo-dev/1.9.11-1+b1
Version: libirstlm-dev/5.80.03-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-01-26
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Preconfiguring packages ...
Selecting previously unselected package gcc-5-base:amd64.
(Reading database ... 10941 files and directories currently installed.)
Preparing to unpack .../gcc-5-base_5.3.1-7_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.3.1-7) ...
Setting up gcc-5-base:amd64 (5.3.1-7) ...
(Reading database ... 10948 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.3.1-7_amd64.deb ...
Unpacking libstdc++6:amd64 (5.3.1-7) over (4.8.2-19) ...
Processing triggers for libc-bin (2.21-7) ...
Setting up libstdc++6:amd64 (5.3.1-7) ...
Processing triggers for libc-bin (2.21-7) ...
Selecting previously unselected package libssl1.0.2:amd64.
(Reading database ... 10962 files and directories currently installed.)
Preparing to unpack .../libssl1.0.2_1.0.2e-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2e-1) ...
Selecting previously unselected package libirstlm0:amd64.
Preparing to unpack .../libirstlm0_5.80.03-1_amd64.deb ...
Unpacking libirstlm0:amd64 (5.80.03-1) ...
Selecting previously unselected package libirstlm-dev.
Preparing to unpack .../libirstlm-dev_5.80.03-1_amd64.deb ...
Unpacking libirstlm-dev (5.80.03-1) ...
Selecting previously unselected package libduo3:amd64.
Preparing to unpack .../libduo3_1.9.11-1+b1_amd64.deb ...
Unpacking libduo3:amd64 (1.9.11-1+b1) ...
Selecting previously unselected package libduo-dev.
Preparing to unpack .../libduo-dev_1.9.11-1+b1_amd64.deb ...
Unpacking libduo-dev (1.9.11-1+b1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libduo-dev_1.9.11-1+b1_amd64.deb (--unpack):
 trying to overwrite '/usr/include/util.h', which is also in package 
libirstlm-dev 5.80.03-1
Processing triggers for libc-bin (2.21-7) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libduo-dev_1.9.11-1+b1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/include/util.h

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.

Bug#812448: marked as done (rustc: FTBFS: =format-security: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 11:23:10 +
with message-id 
and subject line Bug#812448: fixed in rustc 1.6.0+dfsg1-2
has caused the Debian Bug report #812448,
regarding rustc: FTBFS: =format-security: No such file or directory
to be marked as done.

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

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


-- 
812448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rustc
Version: 1.6.0+dfsg1-1
Severity: serious
Justification: fails to build from source

Builds of rustc have been failing with errors along the lines of

  gcc -I/«BUILDDIR»/rustc-1.6.0+dfsg1/src/compiler-rt/lib 
-I/«BUILDDIR»/rustc-1.6.0+dfsg1/src/compiler-rt/include -Wall -g -fPIC -m32 -g 
-O2 -fstack-protector-strong -Wformat =format-security -std=c99 -c -o 
/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/rt/compiler-rt/triple/builtins/i386/SubDir.lib__builtins/ashlti3.o
 /«BUILDDIR»/rustc-1.6.0+dfsg1/src/compiler-rt/lib/builtins/ashlti3.c
  gcc: error: =format-security: No such file or directory
  Makefile:267: recipe for target 
'/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/rt/compiler-rt/triple/builtins/i386/SubDir.lib__builtins/ashlti3.o'
 failed
  make[3]: *** 
[/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/rt/compiler-rt/triple/builtins/i386/SubDir.lib__builtins/ashlti3.o]
 Error 1
  make[3]: Leaving directory '/«BUILDDIR»/rustc-1.6.0+dfsg1/src/compiler-rt'
  /«BUILDDIR»/rustc-1.6.0+dfsg1/mk/rt.mk:364: recipe for target 
'i686-unknown-linux-gnu/rt/libcompiler-rt.a' failed
  make[2]: *** [i686-unknown-linux-gnu/rt/libcompiler-rt.a] Error 2

The issue appears to stem from logic in mk/rt.mk that tries to strip
-Werror from CFLAGS via $(subst ...), which is happy to replace partial
words, and as such interacts poorly with typical hardening flags.  I'd
suggest instead using $(filter-out ...).

Could you please take a look?

Thanks!
--- End Message ---
--- Begin Message ---
Source: rustc
Source-Version: 1.6.0+dfsg1-2

We believe that the bug you reported is fixed in the latest version of
rustc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 812...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Angus Lees  (supplier of updated rustc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 26 Jan 2016 05:40:14 +1100
Source: rustc
Binary: rustc libstd-rust-1.6 libstd-rust-dev rust-gdb rust-lldb rust-doc
Architecture: source amd64 all
Version: 1.6.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Rust Maintainers 
Changed-By: Angus Lees 
Description:
 libstd-rust-1.6 - Rust standard libraries
 libstd-rust-dev - Rust standard libraries - development files
 rust-doc   - Rust systems programming language - Documentation
 rust-gdb   - Rust debugger (gdb)
 rust-lldb  - Rust debugger (lldb)
 rustc  - Rust systems programming language
Closes: 809124 811573 812448
Changes:
 rustc (1.6.0+dfsg1-2) unstable; urgency=medium
 .
   * mk/rt.mk: Modify upstream code to append -Wno-error rather than trying
 to remove the string "-Werror".  (Closes: #812448)
   * Disable new gcc-6 "-Wmisleading-indentation" warning, which triggers
 (incorrectly) on src/rt/miniz.c.  (Closes: #811573)
   * Guard arch-dependent dh_install commands appropriately, fixing
 arch-indep-only builds.  (Closes: #809124)
Checksums-Sha1:
 4b3a485eedbc39d793557ba46f3d6871f03cec7c 2859 rustc_1.6.0+dfsg1-2.dsc
 69eaa70118c647d420cd556f1e59dc069da491ae 89700 
rustc_1.6.0+dfsg1-2.debian.tar.xz
 8c6d3540db6931155001affb54c032b694351a4f 16158216 
libstd-rust-1.6-dbgsym_1.6.0+dfsg1-2_amd64.deb
 ee0d42b79c9a3a87d4d34472b4411363d4d1b1cc 27964746 
libstd-rust-1.6_1.6.0+dfsg1-2_amd64.deb
 156ea22e20f911acf636d633bd365623992d6310 9163692 
libstd-rust-dev_1.6.0+dfsg1-2_amd64.deb
 7ec1138869d2ac7e6f15dc0cbb06634fc66cf1a1 2761360 rust-doc_1.6.0+dfsg1-2_all.deb
 0c29c008a018d22255311ab9930f0f14a91d4d90 58772 rust-gdb_1.6.0+dfsg1-2_amd64.deb
 351316c71fa8ec4b7e41f92d49a605c3fea121e9 59520 

Bug#807237: marked as done (thepeg: Update build dependencies for GSL 2.x)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 12:23:36 +
with message-id 
and subject line Bug#807237: fixed in thepeg 1.8.0-1.1
has caused the Debian Bug report #807237,
regarding thepeg: Update build dependencies for GSL 2.x
to be marked as done.

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

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


-- 
807237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thepeg
Version: 1.8.0-1
Severity: normal
Tags: patch

Dear Maintainer,

Please update your package for the ongoing gsl transition (#804246).

The attached patch updates the build dependencies to use libgsl-dev.

This change is required to not pull in GSL 1.x via libgsl0-dev.

Please note that rivet (#807224) needs to be updated for GSL 2,
before thepeg can be rebuilt with GSL 2.

Having thepeg rebuilt with GSL 2 will unblock the rebuild for herwig++.

Kind Regards,

Bas
diff -Nru thepeg-1.8.0/debian/changelog thepeg-1.8.0/debian/changelog
--- thepeg-1.8.0/debian/changelog	2012-06-16 16:49:45.0 +0200
+++ thepeg-1.8.0/debian/changelog	2015-11-23 01:12:37.0 +0100
@@ -1,3 +1,10 @@
+thepeg (1.8.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+
+ -- Bas Couwenberg   Mon, 23 Nov 2015 01:12:29 +0100
+
 thepeg (1.8.0-1) unstable; urgency=low
 
   * Initial release (Closes: #636986)
diff -Nru thepeg-1.8.0/debian/control thepeg-1.8.0/debian/control
--- thepeg-1.8.0/debian/control	2012-06-16 17:24:03.0 +0200
+++ thepeg-1.8.0/debian/control	2015-11-23 01:12:27.0 +0100
@@ -4,7 +4,7 @@
 Maintainer: Debian Science Maintainers 
 Uploaders: Lifeng Sun 
 DM-Upload-Allowed: yes
-Build-Depends: debhelper (>= 8.0.0), autotools-dev, librivet-dev, libhepmc-dev, liblhapdf-dev, dh-autoreconf, libgsl0-dev, zlib1g-dev, chrpath, default-jdk, libreadline-dev
+Build-Depends: debhelper (>= 8.0.0), autotools-dev, librivet-dev, libhepmc-dev, liblhapdf-dev, dh-autoreconf, libgsl-dev, zlib1g-dev, chrpath, default-jdk, libreadline-dev
 Build-Depends-Indep: doxygen-latex
 Standards-Version: 3.9.3
 Homepage: http://projects.hepforge.org/thepeg/
--- End Message ---
--- Begin Message ---
Source: thepeg
Source-Version: 1.8.0-1.1

We believe that the bug you reported is fixed in the latest version of
thepeg, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 807...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated thepeg package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 26 Jan 2016 12:02:35 +
Source: thepeg
Binary: thepeg thepeg-gui libthepeg15 libthepeg-dev thepeg-reference
Architecture: source
Version: 1.8.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mattia Rizzolo 
Description:
 libthepeg-dev - Development library of ThePEG
 libthepeg15 - Run-time library of ThePEG
 thepeg - Toolkit for High Energy Physics Event Generation
 thepeg-gui - Java GUI of ThePEG
 thepeg-reference - Code reference of ThePEG
Closes: 807237
Changes:
 thepeg (1.8.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Bas Couwenberg ]
   * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
 Closes: #807237
 .
   [ Mattia Rizzolo ]
   * debian/control: drop obsolete DM-Upload-Allowed field.
Checksums-Sha1:
 a0fa82bdbc1471c589d62c241b49b48a4da15317 2335 thepeg_1.8.0-1.1.dsc
 bf0b1f3b92f7bac78d7064172ef6ab444b842687 4740 thepeg_1.8.0-1.1.debian.tar.xz
Checksums-Sha256:
 1d07f9e8a8b279b820ef9a93ebeecedf485cb921e391a24e063d8355431fe1f6 2335 
thepeg_1.8.0-1.1.dsc
 6137e23e6ed1dbccdffb345e164fdb284247e4ac3c1e194eeda1d364045566f4 4740 
thepeg_1.8.0-1.1.debian.tar.xz
Files:
 0ca139764027805f764d45dccaf7f775 2335 science optional thepeg_1.8.0-1.1.dsc
 ee0b516b5c90613f25c7a651b797cf84 4740 science optional 

Bug#812419: marked as done (dlm-controld: fails to install, missing Breaks+Replaces: cman)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 11:33:50 +
with message-id 
and subject line Bug#812419: fixed in dlm 4.0.4-1
has caused the Debian Bug report #812419,
regarding dlm-controld: fails to install, missing Breaks+Replaces: cman
to be marked as done.

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

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


-- 
812419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dlm-controld
Version: 4.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: user trei...@debian.org
Control: usertag -1 edos-file-overwrite


Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package dlm-controld.
  Preparing to unpack .../dlm-controld_4.0.2-1_amd64.deb ...
  Unpacking dlm-controld (4.0.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/dlm-controld_4.0.2-1_amd64.deb (--unpack):
   trying to overwrite '/usr/sbin/dlm_controld', which is also in package cman 
3.1.8-1.3
  Errors were encountered while processing:
   /var/cache/apt/archives/dlm-controld_4.0.2-1_amd64.deb


cheers,

Andreas


cman=3.1.8-1.3_dlm-controld=4.0.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dlm
Source-Version: 4.0.4-1

We believe that the bug you reported is fixed in the latest version of
dlm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 812...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ferenc Wágner  (supplier of updated dlm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 23 Jan 2016 21:21:28 +0100
Source: dlm
Binary: dlm-controld libdlm3 libdlm-dev libdlmcontrol3 libdlmcontrol-dev
Architecture: source
Version: 4.0.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Ferenc Wágner 
Description:
 dlm-controld - Distributed Lock Manager control daemon
 libdlm-dev - Distributed Lock Manager library development
 libdlm3- Distributed Lock Manager library
 libdlmcontrol-dev - Distributed Lock Manager control library development
 libdlmcontrol3 - Distributed Lock Manager control library
Closes: 812419
Changes:
 dlm (4.0.4-1) unstable; urgency=medium
 .
   * [0c99a79] Imported Upstream version 4.0.4
   * [619a537] Avoid useless libxml2 dependency of dlm-controld
   * [203aa46] debian/watch: look for tar.xz instead of tar.gz
   * [0ce96d5] Delete upstreamed patches, update the remaining one
   * [6a30ac3] Upstream udev dir is under /usr/lib since 102d3c2
   * [d655c87] Taking over dlm_{controld,tool} requires Breaks+Replaces cman
 (Closes: #812419)
   * [a7b3406] Hardening seems to work now, enable it
Checksums-Sha1:
 2acd45c96e57379da8454a2052093a39ece07446 2299 dlm_4.0.4-1.dsc
 3cd4bcd124ce9f3d116b59e4cee1a2282cfeccdf 93892 dlm_4.0.4.orig.tar.xz
 c905c0b72cadd5535a7688915d77650e11c6fdbc 4160 dlm_4.0.4-1.debian.tar.xz
Checksums-Sha256:
 86b40c95588ec3c0bd0c67cba5f56b446e7e3de8fa319f1764264a69a7032e42 2299 
dlm_4.0.4-1.dsc
 7eecfcc149def2cdaffc0fddc35e1c4f9bf8ca8aa24bc8ed56d756391f8274f8 93892 
dlm_4.0.4.orig.tar.xz
 bd6fd54df570bafb4a869be9d7aa450d22a68750354cbfc198f364a95f948b74 4160 
dlm_4.0.4-1.debian.tar.xz
Files:
 72967af4e6127522c7c07c293490a023 2299 admin optional dlm_4.0.4-1.dsc
 cea57327f3511621c43fad7a09310897 93892 admin optional dlm_4.0.4.orig.tar.xz
 edc3a2660e61416abd91a59175c6be24 4160 admin optional dlm_4.0.4-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWp1iEAAoJEExaa6sS0qeu5PgQAJkjzygfbgMBAmeNJ5eQui3u
8jrB0eUEfIAEE7FHc/EP9p4n02KEcj7O4Rb42T0/D9mM3tyLv2juhJPcV9Cf3QTm
+RP1bSVPvUqgFGPML2mkAPdOupe7q5m3BB1oBnvAI51Cv3GQOswHNunVh3GiNXPq
jNPDQSHRLUDjx0jx6d+kYnuZEMk2utYlcenMCc5TbWX6umuzJzqhOAS05kmNVx+b

Processed: votca-tools: diff for NMU version 1.2.4-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 807229 + pending
Bug #807229 [src:votca-tools] votca-tools: Update build dependencies for GSL 2.x
Added tag(s) pending.

-- 
807229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#807229: votca-tools: diff for NMU version 1.2.4-1.1

[Mattia Rizzolo]

Control: tags 807229 + pending

Dear maintainer,

I've prepared an NMU for votca-tools (versioned as 1.2.4-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for votca-tools-1.2.4 votca-tools-1.2.4

 changelog |   13 +
 control   |2 +-
 2 files changed, 14 insertions(+), 1 deletion(-)

diff -Nru votca-tools-1.2.4/debian/changelog votca-tools-1.2.4/debian/changelog
--- votca-tools-1.2.4/debian/changelog	2014-09-05 21:04:29.0 +
+++ votca-tools-1.2.4/debian/changelog	2016-01-26 10:39:14.0 +
@@ -1,3 +1,16 @@
+votca-tools (1.2.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807229
+
+  [ Mattia Rizzolo ]
+  * move debian/upstream to debian/upstream/metadata
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 10:38:47 +
+
 votca-tools (1.2.4-1) unstable; urgency=low
 
   * Version bump 
diff -Nru votca-tools-1.2.4/debian/control votca-tools-1.2.4/debian/control
--- votca-tools-1.2.4/debian/control	2014-09-05 21:03:50.0 +
+++ votca-tools-1.2.4/debian/control	2016-01-26 10:37:16.0 +
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debichem Team 
 Uploaders: Christoph Junghans , Michael Banck 
-Build-Depends: debhelper (>= 9.0.0), cmake, libfftw3-dev, libgsl0-dev, txt2tags, libboost-program-options-dev, libexpat1-dev, libsqlite3-dev, pkg-config
+Build-Depends: debhelper (>= 9.0.0), cmake, libfftw3-dev, libgsl-dev, txt2tags, libboost-program-options-dev, libexpat1-dev, libsqlite3-dev, pkg-config
 Standards-Version: 3.9.5
 Homepage: http://www.votca.org
 Vcs-Browser: http://anonscm.debian.org/viewvc/debichem/unstable/votca-tools/
File /tmp/atg6tpHQvt/votca-tools-1.2.4/debian/upstream is a regular file while file /tmp/nSfQXQSgFM/votca-tools-1.2.4/debian/upstream is a directory


signature.asc
Description: PGP signature

Bug#782828: marked as done (libimobiledevice: FTBFS against gnutls 3.4.0)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 10:53:51 +
with message-id 
and subject line Bug#782828: fixed in libimobiledevice 1.2.0+dfsg-2.1
has caused the Debian Bug report #782828,
regarding libimobiledevice: FTBFS against gnutls 3.4.0
to be marked as done.

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

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


-- 
782828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libimobiledevice
Version: 1.1.6+dfsg-3.1
Severity: normal
User: ametz...@debian.org
Usertags: gnutls34

Hello,

the package FTBFS against the recently released GnuTLS 3.4.0:
--
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I.. -Wall -Wextra 
-Wmissing-declarations -Wredundant-decls -Wshadow -Wpointer-arith 
-Wwrite-strings -Wswitch-default -Wno-unused-parameter -fsigned-char 
-I/usr/include/p11-kit-1 -I/usr/include/libxml2 -D_FILE_OFFSET_BITS=64 
-D_LARGE_FILES=1 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -c idevice.c  -fPIC -DPIC -o .libs/idevice.o
idevice.c:719:172: error: unknown type name 'gnutls_retr_st'
 static int internal_cert_callback(gnutls_session_t session, const 
gnutls_datum_t * req_ca_rdn, int nreqs, const gnutls_pk_algorithm_t * 
sign_algos, int sign_algos_length, gnutls_retr_st * st)


^
idevice.c: In function 'idevice_connection_enable_ssl':
idevice.c:839:2: warning: implicit declaration of function 
'gnutls_certificate_client_set_retrieve_function' 
[-Wimplicit-function-declaration]
  gnutls_certificate_client_set_retrieve_function(ssl_data_loc->certificate, 
internal_cert_callback);
  ^
idevice.c:839:77: error: 'internal_cert_callback' undeclared (first use in this 
function)
  gnutls_certificate_client_set_retrieve_function(ssl_data_loc->certificate, 
internal_cert_callback);
 ^
idevice.c:839:77: note: each undeclared identifier is reported only once for 
each function it appears in
Makefile:528: recipe for target 'idevice.lo' failed
make[3]: *** [idevice.lo] Error 1
make[3]: Leaving directory '/tmp/buildd/libimobiledevice-1.1.6+dfsg/src'

--
These functions were dropped in 3.4.0, see
http://www.gnutls.org/manual/html_node/Upgrading-from-previous-versions.html#Upgrading-from-previous-versions
for information on upgrading.

cu Andreas
--- End Message ---
--- Begin Message ---
Source: libimobiledevice
Source-Version: 1.2.0+dfsg-2.1

We believe that the bug you reported is fixed in the latest version of
libimobiledevice, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 782...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated libimobiledevice 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Jan 2016 15:01:41 +
Source: libimobiledevice
Binary: libimobiledevice6 libimobiledevice-dev libimobiledevice6-dbg 
python-imobiledevice libimobiledevice-utils libimobiledevice-doc
Architecture: source
Version: 1.2.0+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: gtkpod Maintainers 
Changed-By: Mattia Rizzolo 
Description:
 libimobiledevice-dev - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice-doc - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice-utils - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice6 - Library for communicating with the iPhone and iPod Touch
 libimobiledevice6-dbg - Library for communicating with iPhone and iPod Touch 
devices
 python-imobiledevice - Library for communicating with iPhone and iPod Touch 
devices
Closes: 782828
Changes:
 libimobiledevice (1.2.0+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Andreas Metzler ]
   * Apply 

Bug#807217: ngraph-gtk: diff for NMU version 6.06.13-5.1

[Mattia Rizzolo]

Control: tags 807217 + pending

Dear maintainer,

I've prepared an NMU for ngraph-gtk (versioned as 6.06.13-5.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for ngraph-gtk-6.06.13 ngraph-gtk-6.06.13

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru ngraph-gtk-6.06.13/debian/changelog ngraph-gtk-6.06.13/debian/changelog
--- ngraph-gtk-6.06.13/debian/changelog	2014-06-15 11:09:33.0 +
+++ ngraph-gtk-6.06.13/debian/changelog	2016-01-26 10:49:40.0 +
@@ -1,3 +1,13 @@
+ngraph-gtk (6.06.13-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807217
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 10:43:45 +
+
 ngraph-gtk (6.06.13-5) unstable; urgency=medium
 
   * debian/rules
diff -Nru ngraph-gtk-6.06.13/debian/control ngraph-gtk-6.06.13/debian/control
--- ngraph-gtk-6.06.13/debian/control	2014-03-31 13:18:20.0 +
+++ ngraph-gtk-6.06.13/debian/control	2016-01-26 10:43:38.0 +
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Koichi Akabe 
 Uploaders: Ito Hiroyuki 
-Build-Depends: debhelper (>= 9.0.0), dh-autoreconf, libgtk-3-dev, libgsl0-dev, libreadline6-dev, ruby (>= 1:2.0.0), ruby-dev (>= 1:2.0.0)
+Build-Depends: debhelper (>= 9.0.0), dh-autoreconf, libgtk-3-dev, libgsl-dev, libreadline6-dev, ruby (>= 1:2.0.0), ruby-dev (>= 1:2.0.0)
 Standards-Version: 3.9.5
 Homepage: http://homepage3.nifty.com/slokar/ngraph/ngraph-gtk.html
 


signature.asc
Description: PGP signature

Processed: ngraph-gtk: diff for NMU version 6.06.13-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 807217 + pending
Bug #807217 [src:ngraph-gtk] ngraph-gtk: Update build dependencies for GSL 2.x
Added tag(s) pending.

-- 
807217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#812764: ruby-redis-store: FTBFS - ruby2.2: No such file or directory -- rake (LoadError)

[Michael Tautschnig]

Package: ruby-redis-store
Version: 1.1.6-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
┌──┐
│ Install Rubygems integration metadata│
└──┘

generating gemspec at 
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-redis-store/ruby-redis-store-1.1.6/debian/ruby-redis-store/usr/share/rubygems-integration/all/specifications/redis-store-1.1.6.gemspec
/usr/bin/ruby2.2 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.2 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/srv/jenkins-slave/workspace/sid-goto-cc-ruby-redis-store/ruby-redis-store-1.1.6/debian/ruby-redis-store/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=/srv/jenkins-slave/workspace/sid-goto-cc-ruby-redis-store/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-redis-store/usr/share/rubygems-integration/all
 ruby2.2 -S rake -f debian/ruby-tests.rake
ruby2.2: No such file or directory -- rake (LoadError)
ERROR: Test "ruby2.2" failed. Exiting.
dh_auto_install: dh_ruby --install 
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-redis-store/ruby-redis-store-1.1.6/debian/ruby-redis-store
 returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further. I am actually
seeing this on a number of ruby packages, so there may as well be a problem in
the ruby tool chain.

Best,
Michael


ruby-redis-store-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature

Processed: sip-tester: diff for NMU version 1:3.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 807226 + pending
Bug #807226 [src:sip-tester] sip-tester: Update build dependencies for GSL 2.x
Added tag(s) pending.

-- 
807226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#807226: sip-tester: diff for NMU version 1:3.2-1.1

[Mattia Rizzolo]

Control: tags 807226 + pending

Dear maintainer,

I've prepared an NMU for sip-tester (versioned as 1:3.2-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for sip-tester-3.2 sip-tester-3.2

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru sip-tester-3.2/debian/changelog sip-tester-3.2/debian/changelog
--- sip-tester-3.2/debian/changelog	2011-11-03 10:57:43.0 +
+++ sip-tester-3.2/debian/changelog	2016-01-26 12:16:25.0 +
@@ -1,3 +1,13 @@
+sip-tester (1:3.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807226
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 12:16:10 +
+
 sip-tester (1:3.2-1) unstable; urgency=low
 
   [ Paul Belanger ]
diff -Nru sip-tester-3.2/debian/control sip-tester-3.2/debian/control
--- sip-tester-3.2/debian/control	2011-11-03 10:56:09.0 +
+++ sip-tester-3.2/debian/control	2016-01-26 12:16:08.0 +
@@ -8,7 +8,7 @@
  libncurses5-dev,
  libnet1-dev,
  libpcap-dev,
- libgsl0-dev,
+ libgsl-dev,
 Build-Conflicts: libssl-dev
 Standards-Version: 3.8.4
 Homepage: http://sourceforge.net/projects/sipp/


signature.asc
Description: PGP signature

Bug#811360: marked as done (php-horde-mapi: depends on not-in-the-archive-anymore php-math-biginteger)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 09:40:09 +
with message-id 
and subject line Bug#811360: fixed in php-horde-mapi 1.0.5-4
has caused the Debian Bug report #811360,
regarding php-horde-mapi: depends on not-in-the-archive-anymore 
php-math-biginteger
to be marked as done.

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

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


-- 
811360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-horde-mapi
Version: 1.0.5-3
Severity: serious

Dear maintainer,

your package depends on a package not available anymore in unstable, and
that is keep in testing just for you.


Is it possible to have a binary without such dependency?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: php-horde-mapi
Source-Version: 1.0.5-4

We believe that the bug you reported is fixed in the latest version of
php-horde-mapi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathieu Parent  (supplier of updated php-horde-mapi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jan 2016 05:29:26 +0100
Source: php-horde-mapi
Binary: php-horde-mapi
Architecture: source all
Version: 1.0.5-4
Distribution: unstable
Urgency: medium
Maintainer: Horde Maintainers 
Changed-By: Mathieu Parent 
Description:
 php-horde-mapi - ${phppear:summary}
Closes: 811360
Changes:
 php-horde-mapi (1.0.5-4) unstable; urgency=medium
 .
   * Update Math_BigInteger dependency (Closes: #811360):
 - Use pkg-php-tools-overrides to drop dependency on php-math-biginteger
 - and depends on php-seclib (<< 2~) instead
 - package name overrides requires pkg-php-tools (>= 1~)
Checksums-Sha1:
 c50a019210433371e2ddc80ef6e9b6f4474acea8 2013 php-horde-mapi_1.0.5-4.dsc
 377c484edd35a186fe7e0bafd504b7bd97ef8d3d 2360 
php-horde-mapi_1.0.5-4.debian.tar.xz
 1aa9733ae8d13011ff9cdaedbaac8fc17535bccd 12318 php-horde-mapi_1.0.5-4_all.deb
Checksums-Sha256:
 c24522502f3878212b75564cee83d85c42de037f24626105462dc0a4dd53d73f 2013 
php-horde-mapi_1.0.5-4.dsc
 3ff1b369631c1469c8acc79323737501bd07cc6f426751bc6d5545acfbc0b950 2360 
php-horde-mapi_1.0.5-4.debian.tar.xz
 646c8335b05cfa8e23f7e6a5ee90f512108929f6621955e14f744a2b1c97d2f8 12318 
php-horde-mapi_1.0.5-4_all.deb
Files:
 530983c8731426ecc7de59f3e8f1cfff 2013 php extra php-horde-mapi_1.0.5-4.dsc
 97b946eb7bf17e9800ec6d4c0987ee68 2360 php extra 
php-horde-mapi_1.0.5-4.debian.tar.xz
 e7db9a677654932f38f25b15fc36ae43 12318 php extra php-horde-mapi_1.0.5-4_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWnw39AAoJEK4DmARmaB+lOXEP/38e8kTtL4631h7f+ijyJgSr
e22M3OPYo4J2BwWOduR6wrhg1g0PijhEoM8hCe3G4Wzw/QfeJT3q1GK/XC77R9wu
EzAWD+MJaTMd1CBSB1lKOJ2WETPDPa/NMYwcgpFLkEr+eUjmsdW19PzFxCwbhaf5
7thzy4QJ3Mp8ZVmkAtTSD23wWQSRLompE3wDIBkCEAJwOAnuOd7xbQnljRUmVz/G
gSe9p9GyUT+8gVSMO2RWg37WmvQM5k9DcYV4mU3sU8YCrhTda3zI5Nhwe9KbzIJP
c5RdvkYMvvthd1P/07sCTyQXBLbZURyOHYrgokjdQ+FcvlRINfoOHpHI98SJCqu8
U1r2NxE1wgLqTPfF2VarvyHnCrNGsSEXUn/FCXQKjaFX7N74RN5vK5qheWPUC4fn
UFqvoHZv7l1J7lsb3SXvx1U44PBqGNaLvTRQ26K9jouTEP2n17Hy5K1pIQHkMuEE
GKKswN3r2htS417wtVTT7k6ODYzdQqyF5rBB0J84LKjvd8doIyfjcAf9HqLOOmoA
s9JkcEDpmRrOBioWuLXi3vr0OtiwccQzuxzvc35p5CJXVp3iZlzCS6YoVSMCvcgy
PTYBeuZcII1pw0vufJsh0JH4Q48Noj7Us/Iqu7lExLtYO01bbEfr2AvLCjM7QT70
Y5k15xD0eIllw2/Oo+ot
=qglJ
-END PGP SIGNATURE End Message ---

Bug#808694: x11proto-fonts: FTBFS: dh_install: x11proto-fonts-dev missing files (usr/share/doc/fontsproto/*.txt), aborting

[Andreas Boll]

This issue has been fixed in xutils-dev 1:7.7+4. See also #613674.

Thanks,
Andreas

On Mon, Dec 21, 2015 at 08:30:04PM +, Chris West (Faux) wrote:
> Source: x11proto-fonts
> Version: 2.1.3-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid stretch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> The package fails to build:
> 
> make[1]: Leaving directory '/x11proto-fonts-2.1.3/build'
> dh_testdir
> dh_testroot
> dh_installdocs
> dh_installman
> find debian/tmp/usr/share/doc/fontsproto -name '*.xml' -delete
> dh_install --sourcedir=debian/tmp --fail-missing --exclude .db
> dh_install: x11proto-fonts-dev missing files 
> (usr/share/doc/fontsproto/*.txt), aborting
> debian/rules:70: recipe for target 'binary-indep' failed
> make: *** [binary-indep] Error 255
> dpkg-buildpackage: error: debian/rules binary gave error exit status 2
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-fonts.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)


signature.asc
Description: Digital signature

Bug#806498: x11proto-core: FTBFS: dh_install: x11proto-core-dev missing files (usr/share/doc/x11proto-core-dev/*.txt), aborting

[Andreas Boll]

This issue has been fixed in xutils-dev 1:7.7+4. See also #613674.

Thanks,
Andreas

On Fri, Nov 27, 2015 at 11:31:12PM +, Chris West (Faux) wrote:
> Source: x11proto-core
> Version: 7.0.27-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid 
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> The package fails to build:
> 
> make[2]: Leaving directory '/x11proto-core-7.0.27/build'
> make[1]: Leaving directory '/x11proto-core-7.0.27'
>debian/rules override_dh_install
> make[1]: Entering directory '/x11proto-core-7.0.27'
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.xml' -delete
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.db' -delete
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.ps' -delete
> dh_install --fail-missing
> dh_install: x11proto-core-dev missing files 
> (usr/share/doc/x11proto-core-dev/*.txt), aborting
> debian/rules:17: recipe for target 'override_dh_install' failed
> make[1]: *** [override_dh_install] Error 255
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-core.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)


signature.asc
Description: Digital signature

Bug#812768: python-whoosh: FTBFS - tests fail with "No such file or directory: ... english-words.10.gz"

[Michael Tautschnig]

Package: python-whoosh
Version: 2.7.0-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
tests/test_sorting.py ..
tests/test_spans.py ...
tests/test_spelling.py F.
tests/test_tables.py .
tests/test_vectors.py .
tests/test_weightings.py ..
tests/test_writing.py .

=== FAILURES ===
___ test_levenshtein ___
Traceback (most recent call last):
  File 
"/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/test_automata.py",
 line 188, in test_levenshtein
wordfile = gzip.open(path, "rb")
  File "/usr/lib/python2.7/gzip.py", line 34, in open
return GzipFile(filename, mode, compresslevel)
  File "/usr/lib/python2.7/gzip.py", line 94, in __init__
fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb')
IOError: [Errno 2] No such file or directory: 
'/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/english-words.10.gz'
___ test_levenshtein_prefix 
Traceback (most recent call last):
  File 
"/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/test_automata.py",
 line 209, in test_levenshtein_prefix
wordfile = gzip.open(path, "rb")
  File "/usr/lib/python2.7/gzip.py", line 34, in open
return GzipFile(filename, mode, compresslevel)
  File "/usr/lib/python2.7/gzip.py", line 94, in __init__
fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb')
IOError: [Errno 2] No such file or directory: 
'/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/english-words.10.gz'
 test_wordfile _
Traceback (most recent call last):
  File 
"/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/test_spelling.py",
 line 84, in test_wordfile
wordfile = gzip.open(path, "rb")
  File "/usr/lib/python2.7/gzip.py", line 34, in open
return GzipFile(filename, mode, compresslevel)
  File "/usr/lib/python2.7/gzip.py", line 94, in __init__
fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb')
IOError: [Errno 2] No such file or directory: 
'/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/english-words.10.gz'
 3 failed, 556 passed in 31.08 seconds =
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd 
/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build;
 python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 --dir . 
returned exit code 13
debian/rules:5: recipe for target 'build' failed
make: *** [build] Error 25


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


python-whoosh-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature

Bug#812626: libfreecontact-perl: FTBFS - Parse errors: Bad plan. You planned 10 tests but ran 6.

[Andreas Tille]

Hi Perl team,

do you have any idea what change might have caused the failures of the
test suite?

Feel free to commit proposed changes to Debian Med Git if this might
simplify your workflow.

Kind regards

Andreas.

On Mon, Jan 25, 2016 at 04:39:25PM +, Michael Tautschnig wrote:
> Package: libfreecontact-perl
> Version: 0.08-4
> Severity: serious
> Usertags: goto-cc
> 
> During a rebuild of all Debian packages in a clean sid chroot (using 
> cowbuilder
> and pbuilder) the build failed with the following error.
> 
> [...]
> make[1]: Leaving directory 
> '/srv/jenkins-slave/workspace/sid-goto-cc-libfreecontact-perl/libfreecontact-perl-0.08'
>dh_auto_test -O--parallel
>   make -j1 test TEST_VERBOSE=1
> make[1]: Entering directory 
> '/srv/jenkins-slave/workspace/sid-goto-cc-libfreecontact-perl/libfreecontact-perl-0.08'
> Running Mkbootstrap for FreeContact ()
> chmod 644 "FreeContact.bs"
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> t/01FreeContact.t .. 
> 1..3
> ok 1 - use FreeContact;
> ok 2 - FreeContact->can(...)
> ok 3 - FreeContact::Predictor->can(...)
> ok
> will use 1 OMP threads
> SSE2 veczweight, wchunk = 32
> total weight (variation) of alignment = 620.777515304633
> 
> seq weight loop for 1000 seqs took 0.012224 secs
> will use 1 OMP threads
> calculated column aa frequencies, gap cols = 4
> calculated pair frequency table in 0.192089 secs
> collected apc_mean[MI] = 0.174031486973761
> aa freq sum (cell) = 0.97158936352, pairfreq sum (cell) = 
> 0.94420985606
> formed covariance matrix (122/126,4)
> LU factorization took 9.17976 secs, inverted matrix (incl LUf) in 23.7932 secs
> density of inverse covariance matrix = 1 (cksum 346842.2)
> went back to gapped (126) wwi matrix
> collected apc_mean[l1norm] = 117.987054769839
> collected apc_mean[fro] = 3.35437751555787
> all done in 24.6311 secs
> will use 1 OMP threads
> SSE2 veczweight, wchunk = 32
> total weight (variation) of alignment = 561.595172234625
> t/02test.t . 
> 1..10
> ok 1 - use FreeContact;
> ok 2 - An object of class 'FreeContact::Predictor' isa 
> 'FreeContact::Predictor'
> ok 3
> ok 4
> ok 5 - precision test
> ok 6 - timing results test
> Failed 4/10 subtests
> 
> Test Summary Report
> ---
> t/02test.t   (Wstat: 11 Tests: 6 Failed: 0)
>   Non-zero wait status: 11
>   Parse errors: Bad plan.  You planned 10 tests but ran 6.
> Files=2, Tests=9, 25 wallclock secs ( 0.06 usr  0.00 sys + 24.63 cusr  0.22 
> csys = 24.91 CPU)
> Result: FAIL
> Failed 1/2 test programs. 0/9 subtests failed.
> Makefile:995: recipe for target 'test_dynamic' failed
> make[1]: *** [test_dynamic] Error 255
> make[1]: Leaving directory 
> '/srv/jenkins-slave/workspace/sid-goto-cc-libfreecontact-perl/libfreecontact-perl-0.08'
> dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
> debian/rules:8: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> I: Copying back the cached apt archive contents
> I: new cache content libextutils-xspp-perl_0.1800-2_all.deb added
> I: new cache content libfreecontact-dev_1.0.21-4_amd64.deb added
> I: new cache content libfreecontact0v5_1.0.21-4_amd64.deb added
> I: unmounting /srv/jenkins-slave/workspace/sid-goto-cc-libfreecontact-perl 
> filesystem
> I: unmounting /run/shm filesystem
> I: unmounting dev/pts filesystem
> I: unmounting run/shm filesystem
> I: unmounting proc filesystem
>  -> Cleaning COW directory
>   forking: rm -rf /srv/jenkins-slave/cow/cow.42349
> 
> 
> The full build log is attached; please do let me know if the problem is
> unreproducible, in which case I shall try to investigate further.
> 
> Best,
> Michael





> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de

Bug#806498: marked as done (x11proto-core: FTBFS: dh_install: x11proto-core-dev missing files (usr/share/doc/x11proto-core-dev/*.txt), aborting)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 12:26:15 +0100
with message-id <20160126112614.GA15421@localhost.localdomain>
and subject line Re: Bug#806498: x11proto-core: FTBFS: dh_install: 
x11proto-core-dev missing files (usr/share/doc/x11proto-core-dev/*.txt), 
aborting
has caused the Debian Bug report #806498,
regarding x11proto-core: FTBFS: dh_install: x11proto-core-dev missing files 
(usr/share/doc/x11proto-core-dev/*.txt), aborting
to be marked as done.

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

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


-- 
806498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: x11proto-core
Version: 7.0.27-1
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

make[2]: Leaving directory '/x11proto-core-7.0.27/build'
make[1]: Leaving directory '/x11proto-core-7.0.27'
   debian/rules override_dh_install
make[1]: Entering directory '/x11proto-core-7.0.27'
find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.xml' -delete
find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.db' -delete
find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.ps' -delete
dh_install --fail-missing
dh_install: x11proto-core-dev missing files 
(usr/share/doc/x11proto-core-dev/*.txt), aborting
debian/rules:17: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 255

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-core.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
This issue has been fixed in xutils-dev 1:7.7+4. See also #613674.

Thanks,
Andreas

On Fri, Nov 27, 2015 at 11:31:12PM +, Chris West (Faux) wrote:
> Source: x11proto-core
> Version: 7.0.27-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid 
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> The package fails to build:
> 
> make[2]: Leaving directory '/x11proto-core-7.0.27/build'
> make[1]: Leaving directory '/x11proto-core-7.0.27'
>debian/rules override_dh_install
> make[1]: Entering directory '/x11proto-core-7.0.27'
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.xml' -delete
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.db' -delete
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.ps' -delete
> dh_install --fail-missing
> dh_install: x11proto-core-dev missing files 
> (usr/share/doc/x11proto-core-dev/*.txt), aborting
> debian/rules:17: recipe for target 'override_dh_install' failed
> make[1]: *** [override_dh_install] Error 255
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-core.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)


signature.asc
Description: Digital signature
--- End Message ---

Bug#808694: marked as done (x11proto-fonts: FTBFS: dh_install: x11proto-fonts-dev missing files (usr/share/doc/fontsproto/*.txt), aborting)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 12:27:19 +0100
with message-id <20160126112719.GA15484@localhost.localdomain>
and subject line Re: Bug#808694: x11proto-fonts: FTBFS: dh_install: 
x11proto-fonts-dev missing files (usr/share/doc/fontsproto/*.txt), aborting
has caused the Debian Bug report #808694,
regarding x11proto-fonts: FTBFS: dh_install: x11proto-fonts-dev missing files 
(usr/share/doc/fontsproto/*.txt), aborting
to be marked as done.

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

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


-- 
808694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: x11proto-fonts
Version: 2.1.3-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

make[1]: Leaving directory '/x11proto-fonts-2.1.3/build'
dh_testdir
dh_testroot
dh_installdocs
dh_installman
find debian/tmp/usr/share/doc/fontsproto -name '*.xml' -delete
dh_install --sourcedir=debian/tmp --fail-missing --exclude .db
dh_install: x11proto-fonts-dev missing files (usr/share/doc/fontsproto/*.txt), 
aborting
debian/rules:70: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 255
dpkg-buildpackage: error: debian/rules binary gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-fonts.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
This issue has been fixed in xutils-dev 1:7.7+4. See also #613674.

Thanks,
Andreas

On Mon, Dec 21, 2015 at 08:30:04PM +, Chris West (Faux) wrote:
> Source: x11proto-fonts
> Version: 2.1.3-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid stretch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> The package fails to build:
> 
> make[1]: Leaving directory '/x11proto-fonts-2.1.3/build'
> dh_testdir
> dh_testroot
> dh_installdocs
> dh_installman
> find debian/tmp/usr/share/doc/fontsproto -name '*.xml' -delete
> dh_install --sourcedir=debian/tmp --fail-missing --exclude .db
> dh_install: x11proto-fonts-dev missing files 
> (usr/share/doc/fontsproto/*.txt), aborting
> debian/rules:70: recipe for target 'binary-indep' failed
> make: *** [binary-indep] Error 255
> dpkg-buildpackage: error: debian/rules binary gave error exit status 2
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-fonts.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)


signature.asc
Description: Digital signature
--- End Message ---

Bug#807186: bist: diff for NMU version 0.5.2-1.1

[Mattia Rizzolo]

Control: tags 807186 + pending

Dear maintainer,

I've prepared an NMU for bist (versioned as 0.5.2-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for bist-0.5.2 bist-0.5.2

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru bist-0.5.2/debian/changelog bist-0.5.2/debian/changelog
--- bist-0.5.2/debian/changelog	2012-04-09 08:48:42.0 +
+++ bist-0.5.2/debian/changelog	2016-01-26 11:47:31.0 +
@@ -1,3 +1,13 @@
+bist (0.5.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807186
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 11:47:21 +
+
 bist (0.5.2-1) unstable; urgency=low
 
   * New upstream version
diff -Nru bist-0.5.2/debian/control bist-0.5.2/debian/control
--- bist-0.5.2/debian/control	2012-04-09 08:48:42.0 +
+++ bist-0.5.2/debian/control	2016-01-26 11:47:18.0 +
@@ -15,7 +15,7 @@
  , libplot-dev
  , libexpat1-dev
  , libxpm-dev
- , libgsl0-dev
+ , libgsl-dev
  , libcurl4-gnutls-dev
 Standards-Version: 3.9.3
 Homepage: https://gna.org/projects/bist/


signature.asc
Description: PGP signature

Processed: bist: diff for NMU version 0.5.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 807186 + pending
Bug #807186 [src:bist] bist: Update build dependencies for GSL 2.x
Added tag(s) pending.

-- 
807186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: libirstlm-dev and libduo-dev: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #812742 [libduo-dev,libirstlm-dev] libirstlm-dev and libduo-dev: error when 
trying to install together
Added tag(s) confirmed.

-- 
812742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#807202: gjay: diff for NMU version 0.3.2-1.2

[Mattia Rizzolo]

Control: tags 807202 + pending

Dear maintainer,

I've prepared an NMU for gjay (versioned as 0.3.2-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for gjay-0.3.2 gjay-0.3.2

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru gjay-0.3.2/debian/changelog gjay-0.3.2/debian/changelog
--- gjay-0.3.2/debian/changelog	2014-09-10 21:44:34.0 +
+++ gjay-0.3.2/debian/changelog	2016-01-26 12:19:32.0 +
@@ -1,3 +1,13 @@
+gjay (0.3.2-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807202
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 12:19:09 +
+
 gjay (0.3.2-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gjay-0.3.2/debian/control gjay-0.3.2/debian/control
--- gjay-0.3.2/debian/control	2014-09-10 21:44:12.0 +
+++ gjay-0.3.2/debian/control	2016-01-26 12:19:02.0 +
@@ -2,7 +2,7 @@
 Section: sound
 Priority: extra
 Maintainer: Craig Small 
-Build-Depends: debhelper (>= 7), autotools-dev, libgtk2.0-dev, libgsl0-dev, audacious-dev, libflac-dev, libvorbis-dev, libmpdclient-dev, libaudclient-dev
+Build-Depends: debhelper (>= 7), autotools-dev, libgtk2.0-dev, libgsl-dev, audacious-dev, libflac-dev, libvorbis-dev, libmpdclient-dev, libaudclient-dev
 Standards-Version: 3.9.1
 Homepage: http://gjay.sourceforge.net/
 


signature.asc
Description: PGP signature

Processed: gjay: diff for NMU version 0.3.2-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 807202 + pending
Bug #807202 [src:gjay] gjay: Update build dependencies for GSL 2.x
Added tag(s) pending.

-- 
807202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#812742: libirstlm-dev and libduo-dev: error when trying to install together

[Balint Reczey]

Control: tags -1 confirmed

Hi Ralf,

Thank you for the bug report.

On Tue, 26 Jan 2016 10:06:07 +0100 Ralf Treinen  wrote:
> Package: libduo-dev,libirstlm-dev
> Version: libduo-dev/1.9.11-1+b1
> Version: libirstlm-dev/5.80.03-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
> 
> Date: 2016-01-26
> Architecture: amd64
> Distribution: sid
> 
> Hi,
> 
> automatic installation tests of packages that share a file and at the
> same time do not conflict by their package dependency relationships has
> detected the following problem:
> 
...

> dpkg: error processing archive 
> /var/cache/apt/archives/libduo-dev_1.9.11-1+b1_amd64.deb (--unpack):
>  trying to overwrite '/usr/include/util.h', which is also in package 
> libirstlm-dev 5.80.03-1
This is indeed a serious bug, the file's name is too generic.
Maybe it is too generic for being in libduo-dev, too, but this is up to
its maintainer.

Moving all include files under /usr/include/irstlm/ seems to be the
appropriate solution.

Cheers,
Balint

Bug#803477: petsc: FTBFS against mpich

[Matthias Klose]

now rebuilt on s390x.

Bug#812681: [help] Bug#812681: mira: FTBFS with flex >= 2.6]

[Gianfranco Costamagna]

Hi, ettercap has some flex code, does it helps?


I don't understand flex either, sorry :(

cheers,

G.





Il Lunedì 25 Gennaio 2016 22:07, Andreas Tille  ha scritto:
Hi,

sorry, I have no idea about fley and need help to fix this problem.

Any hint would be welcome.

Kind regards

 Andreas.

- Forwarded message from Michael Tautschnig  -

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error. It should be noted
right away that this may be one of first attempts building with flex 2.6.
Notably, the flex NEWS says:

"C++ scanners now use references instead of pointers. See the manual for 
details."

[...]
g++ -DPACKAGE_NAME=\"mira\" -DPACKAGE_TARNAME=\"mira\" 
-DPACKAGE_VERSION=\"4.9.5_2\" -DPACKAGE_STRING=\"mira\ 4.9.5_2\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"mira\" 
-DVERSION=\"4.9.5_2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DENABLE64=1 
-DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1 -DSTDC_HEADERS=1 
-DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -Drestrict=__restrict -DHAVE_STDLIB_H=1 
-DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 
-DLSTAT_FOLLOWS_SLASHED_SYMLINK=1 -DHAVE_STRFTIME=1 -DHAVE_MEMSET=1 
-DHAVE_FSEEKO=1 -DHAVE_ISBLANK=1 -DHAVE_BOOST=/\*\*/ -DHAVE_BOOST_THREAD=/\*\*/ 
-DHAVE_BOOST_REGEX=/\*\*/ -DHAVE_BOOST_SYSTEM=/\*\*/ 
-DHAVE_BOOST_FILESYSTEM=/\*\*/ -DHAVE_BOOST_IOSTREAMS=/\*\*/ -DHAVE_LIBRT=1 
-DHAVE_GZOFFSET=1 -DBOUNDTRACKFLAG=1 -DBUGTRACKFLAG=1 -I.  -I../../src  
-Wdate-time  -DPUBLICQUIET -DAJ_Linux64 -g -O0 -fstack-protector-strong 
-Wformat -Werror=format-security  -I/usr/include -O3 -funroll-loops -pthread 
-I/usr/include -I/usr/include -Werror=uninitialized -Werror=return-type 
-Werror=parentheses -Werror=unused-value -std=c++14 -c -o exp_flexer.o 
exp_flexer.cc
exp_flexer.cc: In member function 'virtual int EXPFlexLexer::yylex()':
exp_flexer.cc:766:9: error: no match for 'operator=' (operand types are 
'std::istream {aka std::basic_istream}' and 'std::istream* {aka 
std::basic_istream*}')
yyin = & std::cin;
 ^
In file included from /usr/include/c++/5/iostream:40:0,
 from exp_flexer.cc:96:
/usr/include/c++/5/istream:625:7: note: candidate: std::basic_istream<_CharT, 
_Traits>& std::basic_istream<_CharT, 
_Traits>::operator=(std::basic_istream<_CharT, _Traits>&&) [with _CharT = char; 
_Traits = std::char_traits]
   operator=(basic_istream&& __rhs)
   ^
/usr/include/c++/5/istream:625:7: note:   no known conversion for argument 1 
from 'std::istream* {aka std::basic_istream*}' to 
'std::basic_istream&&'
exp_flexer.cc:769:10: error: no match for 'operator=' (operand types are 
'std::ostream {aka std::basic_ostream}' and 'std::ostream* {aka 
std::basic_ostream*}')
yyout = & std::cout;
  ^
In file included from /usr/include/c++/5/iostream:39:0,
 from exp_flexer.cc:96:
/usr/include/c++/5/ostream:402:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>& std::basic_ostream<_CharT, 
_Traits>::operator=(std::basic_ostream<_CharT, _Traits>&&) [with _CharT = char; 
_Traits = std::char_traits]
   operator=(basic_ostream&& __rhs)
   ^
/usr/include/c++/5/ostream:402:7: note:   no known conversion for argument 1 
from 'std::ostream* {aka std::basic_ostream*}' to 
'std::basic_ostream&&'
exp_flexer.cc:1260:44: error: cannot convert 'std::istream {aka 
std::basic_istream}' to 'std::istream* {aka std::basic_istream*}' 
in assignment
YY_CURRENT_BUFFER_LVALUE->yy_input_file = yyin;
^
In file included from /usr/include/c++/5/iostream:40:0,
 from exp_flexer.cc:96:
/usr/include/c++/5/istream: In constructor 
'EXPFlexLexer::EXPFlexLexer(std::istream*, std::ostream*)':
/usr/include/c++/5/istream:606:7: error: 'std::basic_istream<_CharT, 
_Traits>::basic_istream() [with _CharT = char; _Traits = 
std::char_traits]' is protected
   basic_istream()
   ^
exp_flexer.cc:1370:75: error: within this context
yyFlexLexer::yyFlexLexer( std::istream* arg_yyin, std::ostream* arg_yyout )
   ^
In file included from /usr/include/c++/5/iostream:39:0,
 from exp_flexer.cc:96:
/usr/include/c++/5/ostream:384:7: error: 'std::basic_ostream<_CharT, 
_Traits>::basic_ostream() [with _CharT = char; _Traits = 
std::char_traits]' is protected
   basic_ostream()
   ^
exp_flexer.cc:1370:75: error: within this context
yyFlexLexer::yyFlexLexer( std::istream* arg_yyin, std::ostream* arg_yyout )
   ^
exp_flexer.cc:1372:7: error: no match for 'operator=' (operand types are 
'std::istream {aka std::basic_istream}' and 'std::istream* 

Bug#812818: should dipy be removeed from debian?

[Yaroslav Halchenko]

On Tue, 26 Jan 2016, Mattia Rizzolo wrote:

> As of now there are 2 RC bugs, the package is not in testing, there are
> no reverse (build-)dependencies and the the popcon is resonably low.

> Please, can you consider maintaining the package?  Keeping an unusable
> thing in the archive is not going to help our users in any way.

Thanks for the buzz... we will fix it up in upcoming days

Cheers!

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#812626: libfreecontact-perl: FTBFS - Parse errors: Bad plan. You planned 10 tests but ran 6.

[Andreas Tille]

tags 812626 unreproducible
thanks

On Wed, 27 Jan 2016 gregor herrmann wrote:
> 
> On Tue, 26 Jan 2016 21:14:35 +0100, Andreas Tille wrote:
> 
> > > I cloned the git repo (very handy :)) and had a look, but I can't
> > > reproduce the test failure, not even when running them manually under
> > > high load.
> > H, I should have mentioned this: I also can not reproduce the
> > problem.
> 
> Ok, maybe the submitter can shed some light on this issue.

Michael, could you please be more verbose about the build conditions
since two people can not reproduce this independently.
   
> > > > > SSE2 veczweight, wchunk = 32
> > I get
> >   SSE2 veczweight, wchunk = 64
> > here instead (when building on amd64).
> 
> Me too.
>  
> > > I noticed that the non-perl-test output comes before t/02test.t while
> > > it comes later (after the "ok 3" of t/02test.t) for me. I thought this
> > > might be a parallelization problem but the test was run with -j1, and
> > > it also passes for me with -jN.
> > From my (limited) experience this kind of non-reproducible FTBFS are
> > often connected to parallelization.  I'm tempted to drop the --parallel
> > from d/rules.
> 
> Doesn't hurt, but since since the logs have
> make -j1 test TEST_VERBOSE=1
> this doesn't seem to have any effect anyway.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Processed: tagging 812538, tagging 812691, tagging 812663, tagging 812638, tagging 812637, tagging 812632 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 812538 + sid stretch
Bug #812538 [openvrml] openvrml: FTBFS in clean sid pbuilder envirorment
Added tag(s) sid and stretch.
> tags 812691 + sid stretch
Bug #812691 [mpgtx] mpgtx: FTBFS - variable set but not used
Added tag(s) sid and stretch.
> tags 812663 + sid stretch
Bug #812663 [debian-policy] debian-policy: FTBFS - nsgmls: Command not found
Added tag(s) sid and stretch.
> tags 812638 + sid
Bug #812638 [gbirthday] gbirthday: FTBFS - build-depends on non-existent 
package python-support
Added tag(s) sid.
> tags 812637 + sid stretch
Bug #812637 [antlr] antlr: FTBFS - build-depends on non-existent package 
libmono-winforms2.0-cil
Added tag(s) sid and stretch.
> tags 812632 + sid stretch
Bug #812632 [libindicate] libindicate: FTBFS - build-depends on non-existent 
mono-gmcs
Added tag(s) sid and stretch.
> tags 812818 + sid
Bug #812818 [src:dipy] should dipy be removeed from debian?
Added tag(s) sid.
> found 812794 0.1.0-1
Bug #812794 [ruby-integration] Build-Depends not installable in testing
Marked as found in versions ruby-integration/0.1.0-1.
> tags 812794 + sid stretch
Bug #812794 [ruby-integration] Build-Depends not installable in testing
Added tag(s) stretch and sid.
> found 812793
Bug #812793 [ruby-distribution] Build-Depends not installable in testing
Ignoring request to alter fixed versions of bug #812793 to the same values 
previously set
> tags 812793 + sid stretch
Bug #812793 [ruby-distribution] Build-Depends not installable in testing
Added tag(s) stretch and sid.
> found 812745 1.34.0-2
Bug #812745 [ruby-fog,ruby-fog-xenserver] ruby-fog-xenserver and ruby-fog: 
error when trying to install together
There is no source info for the package 'ruby-fog-xenserver' at version 
'1.34.0-2' with architecture ''
Marked as found in versions ruby-fog/1.34.0-2.
> found 812745 0.2.3-1
Bug #812745 [ruby-fog,ruby-fog-xenserver] ruby-fog-xenserver and ruby-fog: 
error when trying to install together
There is no source info for the package 'ruby-fog' at version '0.2.3-1' with 
architecture ''
Marked as found in versions ruby-fog-xenserver/0.2.3-1.
> found 812742 1.9.11-1
Bug #812742 [libduo-dev,libirstlm-dev] libirstlm-dev and libduo-dev: error when 
trying to install together
There is no source info for the package 'libirstlm-dev' at version '1.9.11-1' 
with architecture ''
Marked as found in versions duo-unix/1.9.11-1.
> found 812742 5.80.03-1
Bug #812742 [libduo-dev,libirstlm-dev] libirstlm-dev and libduo-dev: error when 
trying to install together
There is no source info for the package 'libduo-dev' at version '5.80.03-1' 
with architecture ''
Marked as found in versions irstlm/5.80.03-1.
> found 812696 2.27.1-2
Bug #812696 {Done: Andreas Henriksson } [src:util-linux] 
util-linux: FTBFS on armel, armhf, hppa, mips* - setarch testsuite failure
Marked as found in versions util-linux/2.27.1-2.
> tags 812671 + sid stretch
Bug #812671 [doc-base] doc-base: FTBFS - nsgmls: not found
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812538
812632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812632
812637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812637
812638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812638
812663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812663
812671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812671
812691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812691
812696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812696
812742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812742
812745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812745
812793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812793
812794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812794
812818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#812626: libfreecontact-perl: FTBFS - Parse errors: Bad plan. You planned 10 tests but ran 6.

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 812626 unreproducible
Bug #812626 [libfreecontact-perl] libfreecontact-perl: FTBFS - Parse errors: 
Bad plan.  You planned 10 tests but ran 6.
Added tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#746011: trackballs: updated for guile-2.0

[Rob Browning]

Hi, I've just uploaded a 1.1.4-4.2 NMU to Debian which includes an
initial conversion to Guile 2.0.

You can find the relevant patches in the debian/patches/ directory, or
here:

  https://git.debian.org/?p=users/rlb/trackballs.git

The patches that show up in debian/patches are also separate commits in
the (unnamed) branch that's merged in to sid.  If it's useful, I'd also
be happy to send you a patch series (suitable for "git am").

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#811370: marked as done (libvigraimpex: FTBFS in sid: test suite failure due to pynum 1.10)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jan 2016 06:39:39 +
with message-id 
and subject line Bug#811370: fixed in libvigraimpex 1.10.0+git20160120.803d5d4-1
has caused the Debian Bug report #811370,
regarding libvigraimpex: FTBFS in sid: test suite failure due to pynum 1.10
to be marked as done.

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

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


-- 
811370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvigraimpex
Version: 1.10.0+dfsg-11
Severity: serious
Justification: FTBFS

Hi Daniel,

In the course of the libpng transition I rebuilt also this package, and it 
FTBFS.
The buildlog is here: http://libpng.sviech.de/old/keep/libvigraimpex.build


Cause seems to be the new pynum version, upstream has already a patch [1]
I did not check if the patch work.

--
tobi


[1] 
https://github.com/ukoethe/vigra/commit/ca2246798fed70e8a7bd0994f22ee9f857e9aba0.patch

-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: libvigraimpex
Source-Version: 1.10.0+git20160120.803d5d4-1

We believe that the bug you reported is fixed in the latest version of
libvigraimpex, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated libvigraimpex 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 26 Jan 2016 22:38:23 +0100
Source: libvigraimpex
Binary: libvigraimpex-dev libvigraimpex5v5 libvigraimpex-doc python-vigra 
python-vigra-doc
Architecture: source
Version: 1.10.0+git20160120.803d5d4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Daniel Stender 
Description:
 libvigraimpex-dev - development files for the C++ computer vision library
 libvigraimpex-doc - Documentation for the C++ computer vision library
 libvigraimpex5v5 - C++ computer vision library
 python-vigra - Python bindings for the C++ computer vision library
 python-vigra-doc - Documentation for Python bindings for the C++ computer 
vision lib
Closes: 811370
Changes:
 libvigraimpex (1.10.0+git20160120.803d5d4-1) unstable; urgency=medium
 .
   * Packaging latest development snapshot (Closes: #811370).
   * deb/control:
 + needs python3-sphinx to build.
   * deb/rules:
 + failsafe test/impex temporarily due for problems with EXR.
   * Build with different upstream tarball (the flavour without doc/):
 + deb/watch: changed regex pattern for tarball, added repacksuffix.
 + dropped deb/get-orig.source.sh.
 + deb/copyright: added Files-Excluded with remaining strip patterns.
 + deb/rules: dropped build target get-orig-source, updated clean target.
   * Dropped:
 + deb/*.dirs (obsolete)
 + off-by-on-in-exportImageAlpha.diff (applied upstream).
   * Updated:
 + docsrc-out-of-source.diff, docsrc-paths.diff, removed-static-docs.diff.
Checksums-Sha1:
 296b60d59230f95739171b4c8844b9b2ae653773 2734 
libvigraimpex_1.10.0+git20160120.803d5d4-1.dsc
 9bb1303697291c801f061f4f43a40d7a3a9423d7 25164276 
libvigraimpex_1.10.0+git20160120.803d5d4.orig.tar.xz
 3377913b9aae818ea00ebebbb86213645330dea5 14472 
libvigraimpex_1.10.0+git20160120.803d5d4-1.debian.tar.xz
Checksums-Sha256:
 026e6a5432a7e6146a6ccad275854b6befc2feefa584a2de5384af248fcc1b27 2734 
libvigraimpex_1.10.0+git20160120.803d5d4-1.dsc
 052b26193b0915c8f23cf9f1ca432e0783faa88e020fc8a4747c50c5bc9c 25164276 
libvigraimpex_1.10.0+git20160120.803d5d4.orig.tar.xz
 d5c7e5c76f663cd7210e1de6638e6698f54efd8c5bdce099fd5e48b4a3ca0669 14472 
libvigraimpex_1.10.0+git20160120.803d5d4-1.debian.tar.xz
Files:
 

Bug#746011: marked as done (trackballs: please migrate to guile-2.0)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jan 2016 04:29:08 +
with message-id 
and subject line Bug#746011: fixed in trackballs 1.1.4-4.2
has caused the Debian Bug report #746011,
regarding trackballs: please migrate to guile-2.0
to be marked as done.

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

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


-- 
746011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: trackballs

I'm planning to have guile-1.8 removed from unstable before the
freeze; please migrate to guile-2.0 as soon as possible.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--- End Message ---
--- Begin Message ---
Source: trackballs
Source-Version: 1.1.4-4.2

We believe that the bug you reported is fixed in the latest version of
trackballs, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 746...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rob Browning  (supplier of updated trackballs package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 26 Jan 2016 21:39:58 -0600
Source: trackballs
Binary: trackballs trackballs-dbg trackballs-data
Architecture: source all amd64
Version: 1.1.4-4.2
Distribution: unstable
Urgency: medium
Maintainer: Ari Pollak 
Changed-By: Rob Browning 
Description:
 trackballs - An OpenGL-based game of marbles through a labyrinth
 trackballs-data - Data files for trackballs
 trackballs-dbg - Debugging symbols for Trackballs
Closes: 746011
Changes:
 trackballs (1.1.4-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update source for guile-2.0.
 Add these patches:
   0002-lv1.scm-move-illegal-expression-context-define-to-th.patch
   0003-Port-to-Guile-2.0.patch
   0004-icons-Makefile.am-prepend-DESTDIR-to-iconsdir-here-t.patch
   0005-po-Makefile.in.in-set-mkinstalldirs-to-install-d.patch
   * Change build-dep to guile-2.0-dev. (Closes: 746011)
   * Migrate to debhelper 9
   * Delete automatically generated upstream files.  Add
 0006-Delete-automatically-generated-upstream-files.patch to handle the
 removals.
   * Add dh-autoreconf build-dep.
Checksums-Sha1:
 eb719f8b26a39de2af396002b7b65a4c26aef42b 2022 trackballs_1.1.4-4.2.dsc
 d814a205ab687758ee9e598f945f4b2e3584f369 126244 
trackballs_1.1.4-4.2.debian.tar.xz
 1acc02cb71b6b02ea3f529bb6b425ba360354281 6231186 
trackballs-data_1.1.4-4.2_all.deb
 a2652f7e2db39930c9060d246448762dc57dc87d 627942 
trackballs-dbg_1.1.4-4.2_amd64.deb
 4e797fcb620671c82cdfcb702a52a0e58c585356 159304 trackballs_1.1.4-4.2_amd64.deb
Checksums-Sha256:
 319be60e70fe74dcacf79ca44674387efd87525e5b3e92cf1a876b377a1cba9b 2022 
trackballs_1.1.4-4.2.dsc
 69067495eec77cc1d16945dd1750a221f6c891f8564722680e9c0a440497103b 126244 
trackballs_1.1.4-4.2.debian.tar.xz
 d1123fbb3308cce54da24f71cce1a6a5b291a3fe78b499957a2b16a464a85ea0 6231186 
trackballs-data_1.1.4-4.2_all.deb
 19fa7f67fe5e465c88e9e237c3e0bd5a3c4925d8cd8640bde3cbc5cb0acd279a 627942 
trackballs-dbg_1.1.4-4.2_amd64.deb
 c28b4c07bcac224491a6e7955932d502aea32d58c4b409f2e0e3682dcda3d087 159304 
trackballs_1.1.4-4.2_amd64.deb
Files:
 cc0a3c2f66d7076506e6fefc40c66a79 2022 games extra trackballs_1.1.4-4.2.dsc
 67a6375a52b75578eb34c027763f270a 126244 games extra 
trackballs_1.1.4-4.2.debian.tar.xz
 0e76cfa5b34dbc891b70244537e65eb4 6231186 games extra 
trackballs-data_1.1.4-4.2_all.deb
 d0ed8d30876d672b74fee053305d685c 627942 debug extra 
trackballs-dbg_1.1.4-4.2_amd64.deb
 e2fd595ce284ba268c1c418fb223f9ca 159304 games extra 
trackballs_1.1.4-4.2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWqEAeAAoJEO7xFsVaWkLxSZ0QAImhYyQI3tYHcbOK2DXXiib7
T6JWZY/R3R1/CUvq+qVKqk905S8g7gIFGafiQ5di7Z+ns3+i8SZhKJx/1U1n7agh
VXN/wWItoSKDdmBPzPXR3Jljxp+ckK1ZnxSuLHcss3RtC64aNP9V2Xht6JBMJh1u
XmkrfdabWohJjZJv1i154dpMVAxKo2NJKL8nzuJmElVFgNuS7NFROwScIi3q/eN8
pgJAZGtZHHu5QSY1K83kXw5zGnUQGgw+UJCUFBgPRygljSaYKIkRjJuN2qZgOVZO

Bug#812796: tokyocabinet ftbfs on ppc64el, failing to run the tests

[Tobias Frost]

Control: Retitle -1 tokyocabinet: testsuite sometimes failes
Control: Severity -1 normal
Control: Tags -1 unreproducible help


Hi Matthias,

this is some spurious error I've seen before. A give-back will fixed
that everytime until now... Unfortunatly I'm not able to reproduce it
here, even after looping the testsuite endlessly for an day or so.. 
so nothing I can do at the moment
(I'll do an upload for the parallel, so no gb will be needed)

So let me reduce the severity and tag it help.. Maybe someone is more
lucky than me in repproducing


--
tobi

Am Dienstag, den 26.01.2016, 17:45 +0100 schrieb Matthias Klose:
> Package: src:tokyocabinet
> Version: 1.4.48-4
> Severity: serious
> Tags: sid stretch
> 
> seen in 20160126 unstable:
> 
> AA@A01A2A9CA515D7E849493@98@24787308E46B9E6@44B098 (3850)
> AB3@475D023A21312976ECAA2728AD10C64778CAB06279C468 (3900)
> AC9AAD2EEE@CEC9124524674647@619B17A@EB85A53@01D832 (3950)
> 4DACD34D4B742@C0@02C0DA@9848492@C42@37E520E5480B40 (4000)
> 4E02000@@44331A6C3A845B@1AE8@0CB7DD@D974C048272CB4Makefile:236:
> recipe for 
> target 'check-hdb' failed
> make[2]: *** [check-hdb] Segmentation fault
> make[2]: Leaving directory '/home/doko/tmp/tokyocabinet-1.4.48'
> Makefile:166: recipe for target 'check' failed
> make[1]: *** [check] Error 2
> make[1]: Leaving directory '/home/doko/tmp/tokyocabinet-1.4.48'
> dh_auto_test: make -j1 check returned exit code 2
> debian/rules:9: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 2

Processed: Re: Bug#812796: tokyocabinet ftbfs on ppc64el, failing to run the tests

[Debian Bug Tracking System]

Processing control commands:

> Retitle -1 tokyocabinet: testsuite sometimes failes
Bug #812796 [src:tokyocabinet] tokyocabinet ftbfs on ppc64el, failing to run 
the tests
Changed Bug title to 'tokyocabinet: testsuite sometimes failes' from 
'tokyocabinet ftbfs on ppc64el, failing to run the tests'
> Severity -1 normal
Bug #812796 [src:tokyocabinet] tokyocabinet: testsuite sometimes failes
Severity set to 'normal' from 'serious'
> Tags -1 unreproducible help
Bug #812796 [src:tokyocabinet] tokyocabinet: testsuite sometimes failes
Added tag(s) unreproducible and help.

-- 
812796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 812470 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 812470 serious
Bug #812470 [kernel-package] kernel-package: cannot produce debs anymore
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Closing bug

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 812269 oce 0.15-7
Bug #812269 [freecad] FTBFS in unstable: No rule to make target 
/usr/lib/libfreeimage.so
Bug reassigned from package 'freecad' to 'oce'.
No longer marked as found in versions freecad/0.15.4671+dfsg1-3.
Ignoring request to alter fixed versions of bug #812269 to the same values 
previously set
Bug #812269 [oce] FTBFS in unstable: No rule to make target 
/usr/lib/libfreeimage.so
There is no source info for the package 'oce' at version '0.15-7' with 
architecture ''
Unable to make a source version for version '0.15-7'
Marked as found in versions 0.15-7.
> fixed 812269 0.15-8
Bug #812269 [oce] FTBFS in unstable: No rule to make target 
/usr/lib/libfreeimage.so
There is no source info for the package 'oce' at version '0.15-8' with 
architecture ''
Unable to make a source version for version '0.15-8'
Marked as fixed in versions 0.15-8.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#812621: Bug#812695: pygame-sdl2: FTBFS: format not a string literal and no format arguments

[Gianfranco Costamagna]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi, we uploaded libsdl2 a few days ago, and now we are uploading
image, mixer, ttf and all the related packages.

This API breakage shouldn't have been possible (according to upstream,
no packages should use internal sdl2 functions, and in case they do,
they asked us to report them upstream, so they can have a look and
provide patches)

so, if you say the code is autogenerated, please just wait for our
"internal" transition to finish, and then I guess a simple binNMU
would be already enough to fix the issue.

libsdl2-net and libsdl2-gfx are already in unstable, libsdl2-image
will go in unstable today, while libsdl2-ttf and libsdl2-mixer are on
Manuel todo list.

Please revert your "hack" on pygame-sdl2, and let us know if it still
is a problem after we finished the internal sdl2 transition.

thanks a lot for the ping and the good report to you both!

cheers,

Gianfranco


On Mon, 25 Jan 2016 23:38:28 -0500 u...@debian.org (Aaron M. Ucko) wrote
:
> Markus Koschany  writes:
> 
>> Thanks for the report. I believe this is some sort of regression
>> in SDL2 2.0.4. Four days ago pygame-sdl2 built fine with SDL2
>> 2.0.2. pygame_sdl2.error.c is auto-generated at build-time and
>> the error message,(__pyx_t_3) is controlled by SDL_GetError(), so
>> there is not much I can do here. I will disable this specific
>> -format hardening check for now and re-enable it as soon as this
>> issue is resolved in src:libsdl2 and related packages.
> 
> Ah, yes, I see that SDL_SetError hadn't previously been annotated
> as printf-like.  It would be best if whatever generated
> pygame_sdl2.error.c (cython?) respected this annotation itself.
> 
> At any rate, thanks for the quick response and workaround!
> 
> -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) 
> http://www.mit.edu/~amu/ |
> http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWpy9tAAoJEPNPCXROn13Z+wMQAI6LzrNYVgCPomnZbSpiTQV5
SieWBAqJqRbDkvBf5t4z+4/M7REyRqH/xcx66cIdaBIYiXPluO4u+DG2/XjKKpM4
q2fkJlbF7b4tLBDRzZ2yuXydsWoQLqg7u4JnCxfQstwN8Z7+R3wnhe3MVBB1iaZj
vvAj4O7mFjrUJwCwXeoucSnEhcycyvkEbAmGsLiIhjbdK0nplBwLryc4bBx2rO7i
vt7OMfBKAgTBY+GNDkaeLVXEgTWJpvkevciW88ptuAggmNxiM8QtOTpQ73m7ngBt
JMSF9HvS7AZz9bPhcA7tcIaTIjeLjhwBSQ4GkotDZ2X/aWq9u9+MEnGygubNIrMB
Ymwr6MBCC9uBNt/4uS15NQbz0iGSvrsn8k3oKS4egWW7uHoBqPHEJnbeReULhyki
R7vTrYy1OvGtcrfi/98c+SnxT5AgY2+wnKJd0veLVdERo8etaFQx1rYI7Ie+8Xa5
UqNCSMWaoY8Fawee/lluT3f4kYT8e8/keitJe38h+MK/qOFiJc8kHCFFVAlCcGEP
8KjQQ/V79oDf4iC+s+9n54/RtMYWxpjnNmcx+FzM2YNPHiEAget4ibrpQQHrWPLO
SFud94EzCrSzmvvHpYf1H4wOKeqCaHxNr3FAo/fLltDmvU94FWA5/B3Cu7RYzeo2
VLqh9CsTw2C4L7/wt6q8
=gX22
-END PGP SIGNATURE-

Bug#812269: Closing bug

[Anton Gladky]

reassign 812269 oce 0.15-7
fixed 812269 0.15-8
thanks

Bug#812269: marked as done (FTBFS in unstable: No rule to make target /usr/lib/libfreeimage.so)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 09:35:30 +0100
with message-id 

and subject line Closing bug
has caused the Debian Bug report #812269,
regarding FTBFS in unstable: No rule to make target /usr/lib/libfreeimage.so
to be marked as done.

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

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


-- 
812269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freecad
Version: 0.15.4671+dfsg1-3
Severity: serious

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> rc/3rdParty/salomesmesh/src/DriverUNV 
> -I/<>/freecad-0.15.4671+dfsg1/src/3rdParty/salomesmesh/src/DriverDAT
>  
> -I/<>/freecad-0.15.4671+dfsg1/src/3rdParty/salomesmesh/src/DriverSTL
>  
> -I/<>/freecad-0.15.4671+dfsg1/src/3rdParty/salomesmesh/src/StdMeshers
>  -I/<>/freecad-0.15.4671+dfsg1/src/3rdParty/salomesmesh/inc 
> -I/<>/freecad-0.15.4671+dfsg1/obj-x86_64-linux-gnu/src/3rdParty/salomesmesh
>  -I/usr/lib/x86_64-linux-gnu/oce-0.15/../../../include/oce  -Wall 
> -DHAVE_SWIG=1 -fpermissive -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-deprecated 
> -Wno-write-strings -D_OCC64 -fPIC   -o 
> CMakeFiles/Driver.dir/src/Driver/Driver_Mesh.cpp.o -c 
> /<>/freecad-0.15.4671+dfsg1/src/3rdParty/salomesmesh/src/Driver/Driver_Mesh.cpp
> make[3]: *** No rule to make target '/usr/lib/libfreeimage.so', needed by 
> 'lib/libDriver.so'.  Stop.
> make[3]: Leaving directory 
> '/<>/freecad-0.15.4671+dfsg1/obj-x86_64-linux-gnu'
> CMakeFiles/Makefile2:307: recipe for target 
> 'src/3rdParty/salomesmesh/CMakeFiles/Driver.dir/all' failed
> make[2]: *** [src/3rdParty/salomesmesh/CMakeFiles/Driver.dir/all] Error 2
> make[2]: Leaving directory 
> '/<>/freecad-0.15.4671+dfsg1/obj-x86_64-linux-gnu'
> Makefile:130: recipe for target 'all' failed
> make[1]: *** [all] Error 2
> make[1]: Leaving directory 
> '/<>/freecad-0.15.4671+dfsg1/obj-x86_64-linux-gnu'
> dh_auto_build: make -j1 returned exit code 2
> debian/rules:3: recipe for target 'build' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
reassign 812269 oce 0.15-7
fixed 812269 0.15-8
thanks--- End Message ---

Bug#812732: cyrus-sasl2: FTBFS: /bin/sed: can't read /usr/lib/x86_64-linux-gnu/libheimntlm.la: No such file or directory

[Chris Lamb]

Source: cyrus-sasl2
Version: 2.1.26.dfsg1-14
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

cyrus-sasl2 fails to build from source in unstable/amd64:

  [..]

  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../plugins -I.. 
-I../../include -I../../lib -I../../sasldb -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/heimdal -I/usr/include 
-DOBSOLETE_CRAM_ATTR=1 -DKRB5_HEIMDAL -I/usr/include/mysql 
-I/usr/include/postgresql -I/usr/include -Wall -W -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c 
../../plugins/otp.c -fPIE -o otp.o >/dev/null 2>&1
  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../plugins -I.. -I../../include -I../../lib -I../../sasldb -I../include  
-Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/heimdal  -I/usr/include 
-DOBSOLETE_CRAM_ATTR=1 -DKRB5_HEIMDAL -I/usr/include/mysql 
-I/usr/include/postgresql -I/usr/include  -Wall -W -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -c -o otp_init.lo 
../../plugins/otp_init.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../plugins -I.. 
-I../../include -I../../lib -I../../sasldb -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/heimdal -I/usr/include 
-DOBSOLETE_CRAM_ATTR=1 -DKRB5_HEIMDAL -I/usr/include/mysql 
-I/usr/include/postgresql -I/usr/include -Wall -W -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c 
../../plugins/otp_init.c  -fPIC -DPIC -o .libs/otp_init.o
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../plugins -I.. 
-I../../include -I../../lib -I../../sasldb -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/heimdal -I/usr/include 
-DOBSOLETE_CRAM_ATTR=1 -DKRB5_HEIMDAL -I/usr/include/mysql 
-I/usr/include/postgresql -I/usr/include -Wall -W -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c 
../../plugins/otp_init.c -fPIE -o otp_init.o >/dev/null 2>&1
  /bin/bash ../libtool  --tag=CC   --mode=link gcc  -Wall -W -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -module 
-export-dynamic -rpath /usr/lib/x86_64-linux-gnu/sasl2:/usr/lib/sasl2 
-version-info 2:25:0 -fPIE -pie -Wl,-z,relro -Wl,-z,now 
-L/usr/lib/x86_64-linux-gnu/heimdal -Wl,-z,defs -L/usr/x86_64-linux-gnu/lib -o 
libotp.la  otp.lo otp_init.lo plugin_common.lo -lcrypto   -lresolv  
  libtool: link: gcc -shared  -fPIC -DPIC  .libs/otp.o .libs/otp_init.o 
.libs/plugin_common.o   -L/usr/lib/x86_64-linux-gnu/heimdal 
-L/usr/x86_64-linux-gnu/lib -lcrypto -lresolv  -O2 -Wl,-z -Wl,relro -Wl,-z 
-Wl,now -Wl,-z -Wl,defs   -Wl,-soname -Wl,libotp.so.2 -o .libs/libotp.so.2.0.25
  libtool: link: (cd ".libs" && rm -f "libotp.so.2" && ln -s "libotp.so.2.0.25" 
"libotp.so.2")
  libtool: link: (cd ".libs" && rm -f "libotp.so" && ln -s "libotp.so.2.0.25" 
"libotp.so")
  libtool: link: ar cru .libs/libotp.a  otp.o otp_init.o plugin_common.o
  ar: `u' modifier ignored since `D' is the default (see `U')
  libtool: link: ranlib .libs/libotp.a
  libtool: link: ( cd ".libs" && rm -f "libotp.la" && ln -s "../libotp.la" 
"libotp.la" )
  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../plugins -I.. -I../../include -I../../lib -I../../sasldb -I../include  
-Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/heimdal  -I/usr/include 
-DOBSOLETE_CRAM_ATTR=1 -DKRB5_HEIMDAL -I/usr/include/mysql 
-I/usr/include/postgresql -I/usr/include  -Wall -W -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -c -o gssapi.lo 
../../plugins/gssapi.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../plugins -I.. 
-I../../include -I../../lib -I../../sasldb -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/heimdal -I/usr/include 
-DOBSOLETE_CRAM_ATTR=1 -DKRB5_HEIMDAL -I/usr/include/mysql 
-I/usr/include/postgresql -I/usr/include -Wall -W -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c 
../../plugins/gssapi.c  -fPIC -DPIC -o .libs/gssapi.o
  ../../plugins/gssapi.c: In function 'sasl_gss_seterror_':
  ../../plugins/gssapi.c:214:40: warning: passing argument 3 of 
'_plug_buf_alloc' from incompatible pointer type [-Wincompatible-pointer-types]
   ret = _plug_buf_alloc(utils, , , 256);
  ^
  In file included from ../../plugins/gssapi.c:78:0:
  ../../plugins/plugin_common.h:145:5: note: expected 'unsigned int *' but 
argument is of type 'size_t * {aka long unsigned int *}'
   int _plug_buf_alloc(const sasl_utils_t *utils, char **rwbuf,
   ^
  ../../plugins/gssapi.c:241:37: warning: passing argument 3 of 
'_plug_buf_alloc' from incompatible pointer type [-Wincompatible-pointer-types]
ret = _plug_buf_alloc(utils, , , len);
   ^
  In file included from ../../plugins/gssapi.c:78:0:
  ../../plugins/plugin_common.h:145:5: note: expected 

Bug#812733: dfvfs: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode character u'\xed' in position 72: ordinal not in range(128)

[Chris Lamb]

Source: dfvfs
Version: 20160108-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

dfvfs fails to build from source in unstable/amd64:

  [..]

  
  ==
  ERROR: testResolvePathWithEnvironmentVariable 
(helpers.windows_path_resolver.WindowsPathResolverTest)
  Test the resolve path function with environment variable expansion.
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160126092053.HI2fPHzkja/dfvfs-20160108/tests/helpers/windows_path_resolver.py",
 line 179, in testResolvePathWithEnvironmentVariable
  path_spec = path_resolver.ResolvePath(windows_path)
File "./dfvfs/helpers/windows_path_resolver.py", line 241, in ResolvePath
  path, expand_variables=expand_variables)
File "./dfvfs/helpers/windows_path_resolver.py", line 176, in _ResolvePath
  path_segment, case_sensitive=False)
File "./dfvfs/vfs/file_entry.py", line 317, in GetSubFileEntryByName
  for sub_file_entry in self.sub_file_entries:
File "./dfvfs/vfs/os_file_entry.py", line 228, in sub_file_entries
  for path_spec in self._directory.entries:
File "./dfvfs/vfs/file_entry.py", line 67, in entries
  for entry in self._EntriesGenerator():
File "./dfvfs/vfs/os_file_entry.py", line 45, in _EntriesGenerator
  location, directory_entry])
File "./dfvfs/vfs/os_file_system.py", line 191, in JoinPath
  segment.split(self.PATH_SEPARATOR) for segment in path_segments]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 0: 
ordinal not in range(128)
  
  ==
  ERROR: testDataStreams (vfs.tsk_file_entry.TSKFileEntryTest)
  Test the data streams functionality.
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160126092053.HI2fPHzkja/dfvfs-20160108/tests/vfs/tsk_file_entry.py",
 line 28, in setUp
  self._file_system.Open(self._tsk_path_spec)
File "./dfvfs/vfs/file_system.py", line 230, in Open
  self._Open(path_spec, mode=mode)
File "./dfvfs/vfs/tsk_file_system.py", line 64, in _Open
  path_spec.parent, resolver_context=self._resolver_context)
File "./dfvfs/resolver/resolver.py", line 113, in OpenFileObject
  file_object.open(path_spec=path_spec)
File "./dfvfs/file_io/file_io.py", line 73, in open
  self._Open(path_spec=path_spec, mode=mode)
File "./dfvfs/file_io/os_file_io.py", line 88, in _Open
  stat_info = os.stat(location)
  UnicodeEncodeError: 'ascii' codec can't encode character u'\xed' in position 
72: ordinal not in range(128)
  
  ==
  ERROR: testGetDataStream (vfs.tsk_file_entry.TSKFileEntryTest)
  Test the retrieve data streams functionality.
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160126092053.HI2fPHzkja/dfvfs-20160108/tests/vfs/tsk_file_entry.py",
 line 28, in setUp
  self._file_system.Open(self._tsk_path_spec)
File "./dfvfs/vfs/file_system.py", line 230, in Open
  self._Open(path_spec, mode=mode)
File "./dfvfs/vfs/tsk_file_system.py", line 64, in _Open
  path_spec.parent, resolver_context=self._resolver_context)
File "./dfvfs/resolver/resolver.py", line 113, in OpenFileObject
  file_object.open(path_spec=path_spec)
File "./dfvfs/file_io/file_io.py", line 73, in open
  self._Open(path_spec=path_spec, mode=mode)
File "./dfvfs/file_io/os_file_io.py", line 88, in _Open
  stat_info = os.stat(location)
  UnicodeEncodeError: 'ascii' codec can't encode character u'\xed' in position 
72: ordinal not in range(128)
  
  ==
  ERROR: testGetFileEntryByPathSpec (vfs.tsk_file_entry.TSKFileEntryTest)
  Test the get entry by path specification functionality.
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160126092053.HI2fPHzkja/dfvfs-20160108/tests/vfs/tsk_file_entry.py",
 line 28, in setUp
  self._file_system.Open(self._tsk_path_spec)
File "./dfvfs/vfs/file_system.py", line 230, in Open
  self._Open(path_spec, mode=mode)
File "./dfvfs/vfs/tsk_file_system.py", line 64, in _Open
  path_spec.parent, resolver_context=self._resolver_context)
File "./dfvfs/resolver/resolver.py", line 113, in OpenFileObject
  file_object.open(path_spec=path_spec)
File "./dfvfs/file_io/file_io.py", line 73, in open
  self._Open(path_spec=path_spec, mode=mode)
File 

Bug#812734: libpam-krb5: FTBFS: /bin/sed: can't read /usr/lib/x86_64-linux-gnu/libhx509.la: No such file or directory

[Chris Lamb]

Source: libpam-krb5
Version: 4.7-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

libpam-krb5 fails to build from source in unstable/amd64:

  [..]

  /bin/sed: can't read /usr/lib/x86_64-linux-gnu/libhx509.la: No such file or 
directory
  libtool: link: `/usr/lib/x86_64-linux-gnu/libhx509.la' is not a valid libtool 
archive
  Makefile:968: recipe for target 'pam_krb5.la' failed
  make[3]: *** [pam_krb5.la] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160126092437.40enHpYeqO/libpam-krb5-4.7/build-heimdal'
  Makefile:804: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160126092437.40enHpYeqO/libpam-krb5-4.7/build-heimdal'
  dh_auto_build: make -j9 returned exit code 2
  debian/rules:30: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160126092437.40enHpYeqO/libpam-krb5-4.7'
  debian/rules:9: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


libpam-krb5.4.7-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#812736: ruby-net-ssh: FTBFS: /usr/lib/ruby/2.2.0/rubygems/specification.rb:927:in `block in find_by_path': undefined method `contains_requirable_file?' for nil:NilClass (NoMethodError)

[Chris Lamb]

Source: ruby-net-ssh
Version: 1:2.9.2-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-net-ssh fails to build from source in unstable/amd64:

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/debian/ruby-net-ssh/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-net-ssh/usr/share/rubygems-integration/all
 ruby2.2 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.2   "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/test*.rb" -v
  /usr/lib/ruby/2.2.0/rubygems/specification.rb:927:in `block in find_by_path': 
undefined method `contains_requirable_file?' for nil:NilClass (NoMethodError)
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:895:in `block in 
each'
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:894:in `each'
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:894:in `each'
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:926:in `find'
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:926:in `find_by_path'
from /usr/lib/ruby/2.2.0/rubygems.rb:190:in `try_activate'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:126:in 
`rescue in require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in 
`require'
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/lib/net/ssh/prompt.rb:81:in
 `'
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/lib/net/ssh/prompt.rb:1:in
 `'
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/lib/net/ssh/prompt.rb:1:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/lib/net/ssh/key_factory.rb:2:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/lib/net/ssh/authentication/key_manager.rb:2:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/lib/net/ssh/authentication/session.rb:4:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/lib/net/ssh.rb:11:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/test/start/test_options.rb:2:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/test/test_all.rb:10:in
 `block (2 levels) in '
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/test/test_all.rb:10:in
 `each'
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/test/test_all.rb:10:in
 `block in '
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/test/test_all.rb:5:in
 `chdir'
from 
/home/lamby/temp/cdt.20160126092627.BFUmdh3bRL/ruby-net-ssh-2.9.2/test/test_all.rb:5:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:10:in `block (2 
levels) in '
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:9:in `each'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:9:in `block in 
'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `'
  Skipping packet stream test for idea-cbc
  rake aborted!
  Command failed with status (1): [ruby   
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test*.rb" -v]
  
  Tasks: TOP => default
  (See full trace by running task with --trace)

Bug#812735: ruby-net-scp: FTBFS: /usr/lib/ruby/2.2.0/rubygems/specification.rb:927:in `block in find_by_path': undefined method `contains_requirable_file?' for nil:NilClass (NoMethodError)

[Chris Lamb]

Source: ruby-net-scp
Version: 1.2.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-net-scp fails to build from source in unstable/amd64:

  [..]

  
  
RUBYLIB=/home/lamby/temp/cdt.20160126092606.gZdR9RA6w0/ruby-net-scp-1.2.1/debian/ruby-net-scp/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-net-scp/usr/share/rubygems-integration/all
 ruby2.2 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.2   "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/test_all.rb" "test/test_download.rb" "test/test_scp.rb" 
"test/test_upload.rb" -v
  /usr/lib/ruby/2.2.0/rubygems/specification.rb:927:in `block in find_by_path': 
undefined method `contains_requirable_file?' for nil:NilClass (NoMethodError)
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:895:in `block in 
each'
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:894:in `each'
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:894:in `each'
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:926:in `find'
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:926:in `find_by_path'
from /usr/lib/ruby/2.2.0/rubygems.rb:190:in `try_activate'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:126:in 
`rescue in require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in 
`require'
from /usr/lib/ruby/vendor_ruby/net/ssh/prompt.rb:81:in `'
from /usr/lib/ruby/vendor_ruby/net/ssh/prompt.rb:1:in `'
from /usr/lib/ruby/vendor_ruby/net/ssh/prompt.rb:1:in `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/vendor_ruby/net/ssh/key_factory.rb:2:in `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/usr/lib/ruby/vendor_ruby/net/ssh/authentication/key_manager.rb:2:in `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/vendor_ruby/net/ssh/authentication/session.rb:4:in 
`'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/vendor_ruby/net/ssh.rb:11:in `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160126092606.gZdR9RA6w0/ruby-net-scp-1.2.1/test/common.rb:11:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160126092606.gZdR9RA6w0/ruby-net-scp-1.2.1/test/test_upload.rb:1:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160126092606.gZdR9RA6w0/ruby-net-scp-1.2.1/test/test_all.rb:2:in
 `block (2 levels) in '
from 
/home/lamby/temp/cdt.20160126092606.gZdR9RA6w0/ruby-net-scp-1.2.1/test/test_all.rb:2:in
 `each'
from 
/home/lamby/temp/cdt.20160126092606.gZdR9RA6w0/ruby-net-scp-1.2.1/test/test_all.rb:2:in
 `block in '
from 
/home/lamby/temp/cdt.20160126092606.gZdR9RA6w0/ruby-net-scp-1.2.1/test/test_all.rb:1:in
 `chdir'
from 
/home/lamby/temp/cdt.20160126092606.gZdR9RA6w0/ruby-net-scp-1.2.1/test/test_all.rb:1:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in 
'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `'
  rake aborted!
  Command failed with status (1): [ruby   
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_all.rb" 
"test/test_download.rb" "test/test_scp.rb" "test/test_upload.rb" -v]
  
  Tasks: TOP => default
  (See full trace by running task with --trace)
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 

Bug#812764: marked as done (ruby-redis-store: FTBFS - ruby2.2: No such file or directory -- rake (LoadError))

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 11:23:10 -0200
with message-id <20160126132310.ga11...@debian.org>
and subject line Re: Bug#812764: ruby-redis-store: FTBFS - ruby2.2: No such 
file or directory -- rake (LoadError)
has caused the Debian Bug report #812764,
regarding ruby-redis-store: FTBFS - ruby2.2: No such file or directory -- rake 
(LoadError)
to be marked as done.

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

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


-- 
812764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-redis-store
Version: 1.1.6-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
┌──┐
│ Install Rubygems integration metadata│
└──┘

generating gemspec at 
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-redis-store/ruby-redis-store-1.1.6/debian/ruby-redis-store/usr/share/rubygems-integration/all/specifications/redis-store-1.1.6.gemspec
/usr/bin/ruby2.2 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.2 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/srv/jenkins-slave/workspace/sid-goto-cc-ruby-redis-store/ruby-redis-store-1.1.6/debian/ruby-redis-store/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=/srv/jenkins-slave/workspace/sid-goto-cc-ruby-redis-store/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-redis-store/usr/share/rubygems-integration/all
 ruby2.2 -S rake -f debian/ruby-tests.rake
ruby2.2: No such file or directory -- rake (LoadError)
ERROR: Test "ruby2.2" failed. Exiting.
dh_auto_install: dh_ruby --install 
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-redis-store/ruby-redis-store-1.1.6/debian/ruby-redis-store
 returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further. I am actually
seeing this on a number of ruby packages, so there may as well be a problem in
the ruby tool chain.

Best,
Michael


ruby-redis-store-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Tue, Jan 26, 2016 at 11:46:28AM +, Michael Tautschnig wrote:
> ┌──┐
> │ Run tests for ruby2.2 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/srv/jenkins-slave/workspace/sid-goto-cc-ruby-redis-store/ruby-redis-store-1.1.6/debian/ruby-redis-store/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=/srv/jenkins-slave/workspace/sid-goto-cc-ruby-redis-store/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-redis-store/usr/share/rubygems-integration/all
>  ruby2.2 -S rake -f debian/ruby-tests.rake
> ruby2.2: No such file or directory -- rake (LoadError)
> ERROR: Test "ruby2.2" failed. Exiting.
> dh_auto_install: dh_ruby --install 
> /srv/jenkins-slave/workspace/sid-goto-cc-ruby-redis-store/ruby-redis-store-1.1.6/debian/ruby-redis-store
>  returned exit code 1
> debian/rules:15: recipe for target 'binary' failed
> make: *** [binary] Error 1

This was a regression in src:gem2deb and should be fixed in 0.25.1. I am
closing this but if you can still reproduce please reopen.


signature.asc
Description: PGP signature
--- End Message ---

Bug#812689: ruby-carrierwave fails its tests

[Antonio Terceiro]

On Mon, Jan 25, 2016 at 10:42:04PM +0100, Matthias Klose wrote:
> Package: src:ruby-carrierwave
> Version: 0.10.0+gh-1
> Severity: serious
> Tags: sid stretch
> 
> ruby-carrierwave fails its tests, also

...

> ruby-mysql2 is scheduled for removal,
> so please use ruby-mysql.

I don't remember that. If we were doing something like that, iyt would
be the other way around since ruby-mysql2 gets new upstream development
while ruby-mysql is long dead.

> RUBYLIB=/scratch/packages/tmp/ruby-carrierwave-0.10.0+gh/debian/ruby-carrierwave/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=/home/doko/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-carrierwave/usr/share/rubygems-integration/all
> ruby2.2 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.2 /usr/bin/rspec ./spec/processing/mini_magick_spec.rb
> .FF
> 
> Failures:
> 
>   1) CarrierWave::MiniMagick test errors invalid image file should use I18n
>  Failure/Error: change_locale_and_store_translations(:nl, :errors => {
>  I18n::InvalidLocale:
>:nl is not a valid locale
>  # ./spec/spec_helper.rb:104:in `change_locale_and_store_translations'
>  # ./spec/processing/mini_magick_spec.rb:145:in `block (4 levels) in
> '
> 
>   2) CarrierWave::MiniMagick test errors invalid image file should not
> suppress errors when translation is unavailable
>  Failure/Error: change_locale_and_store_translations(:foo, {}) do
>  I18n::InvalidLocale:
>:foo is not a valid locale
>  # ./spec/spec_helper.rb:104:in `change_locale_and_store_translations'
>  # ./spec/processing/mini_magick_spec.rb:155:in `block (4 levels) in
> '

This is related to a recent change in ruby-i18n.

-- 
Antonio Terceiro 


signature.asc
Description: PGP signature

Bug#812188: marked as done (debiandoc-sgml-doc-pt-br: FTBFS: make[1]: nsgmls: Command not found)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 22:34:58 +0900
with message-id <20160126133458.GB6081@goofy.local>
and subject line Re: Bug#812188: debiandoc-sgml-doc-pt-br: FTBFS: make[1]: 
nsgmls: Command not found
has caused the Debian Bug report #812188,
regarding debiandoc-sgml-doc-pt-br: FTBFS: make[1]: nsgmls: Command not found
to be marked as done.

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

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


-- 
812188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debiandoc-sgml-doc-pt-br
Version: 1.1.11
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

debiandoc-sgml-doc-pt-br fails to build from source in unstable/amd64:

  [..]

  dh clean
 dh_testdir
 dh_auto_clean
make -j1 clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160121121515.djoqVn2ttF/debiandoc-sgml-doc-pt-br-1.1.11'
  /bin/rm -rf debiandoc-sgml.html debiandoc-sgml.pt_BR.txt
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160121121515.djoqVn2ttF/debiandoc-sgml-doc-pt-br-1.1.11'
 dh_clean
   debian/rules build
  dh build
 dh_testdir
 dh_update_autotools_config
 dh_auto_configure
 dh_auto_build
make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160121121515.djoqVn2ttF/debiandoc-sgml-doc-pt-br-1.1.11'
  nsgmls -wall -E20 -gues debiandoc-sgml.pt_BR.sgml
  make[1]: nsgmls: Command not found
  Makefile:27: recipe for target 'all' failed
  make[1]: *** [all] Error 127
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160121121515.djoqVn2ttF/debiandoc-sgml-doc-pt-br-1.1.11'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:14: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


debiandoc-sgml-doc-pt-br.1.1.11.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Hi,

On Thu, Jan 21, 2016 at 12:19:30PM +0100, Chris Lamb wrote:
> Source: debiandoc-sgml-doc-pt-br
> Version: 1.1.11
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

This package is caught up in the package transition which caused:

>   make[1]: nsgmls: Command not found

With recent NMU of debiandoc-sgml changing by Niel its package
dependencies, this should have been fixed. See Bug#805061--- End Message ---

Bug#812742: libirstlm-dev and libduo-dev: error when trying to install together

[Giulio Paci]

Il 26/gen/2016 13:24, "Balint Reczey"  ha scritto:
>
> Control: tags -1 confirmed
>
> Hi Ralf,
>
> Thank you for the bug report.
>
> On Tue, 26 Jan 2016 10:06:07 +0100 Ralf Treinen  wrote:
> > Package: libduo-dev,libirstlm-dev
> > Version: libduo-dev/1.9.11-1+b1
> > Version: libirstlm-dev/5.80.03-1
> > Severity: serious
> > User: trei...@debian.org
> > Usertags: edos-file-overwrite
> >
> > Date: 2016-01-26
> > Architecture: amd64
> > Distribution: sid
> >
> > Hi,
> >
> > automatic installation tests of packages that share a file and at the
> > same time do not conflict by their package dependency relationships has
> > detected the following problem:
> >
> ...
>
> > dpkg: error processing archive
/var/cache/apt/archives/libduo-dev_1.9.11-1+b1_amd64.deb (--unpack):
> >  trying to overwrite '/usr/include/util.h', which is also in package
libirstlm-dev 5.80.03-1
> This is indeed a serious bug, the file's name is too generic.
> Maybe it is too generic for being in libduo-dev, too, but this is up to
> its maintainer.
>
> Moving all include files under /usr/include/irstlm/ seems to be the
> appropriate solution.

I agree. I just pushed the required changes to git repository.

Bug#805844: herwig++: diff for NMU version 2.6.0-1.1

[Mattia Rizzolo]

Control: tags 805844 + patch
Control: tags 805844 + pending

Dear maintainer,

I've prepared an NMU for herwig++ (versioned as 2.6.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for herwig++-2.6.0 herwig++-2.6.0

 changelog |   16 
 compat|2 +-
 control   |3 +--
 rules |8 
 4 files changed, 18 insertions(+), 11 deletions(-)

diff -Nru herwig++-2.6.0/debian/changelog herwig++-2.6.0/debian/changelog
--- herwig++-2.6.0/debian/changelog	2012-06-13 10:18:54.0 +
+++ herwig++-2.6.0/debian/changelog	2016-01-26 14:15:31.0 +
@@ -1,3 +1,19 @@
+herwig++ (2.6.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #805844
+
+  [ Mattia Rizzolo ]
+  * debian/control: drop obsolete Dm-Upload-Allowed field.
+  * debian/rules: drop explicit configuration, the build system is clever
+enough to figure out where the libs are.
+  * Bump debhelper compat version to 9.
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 13:41:58 +
+
 herwig++ (2.6.0-1) unstable; urgency=low
 
   * Initial release (Closes: #636988)
diff -Nru herwig++-2.6.0/debian/compat herwig++-2.6.0/debian/compat
--- herwig++-2.6.0/debian/compat	2012-06-21 11:15:48.0 +
+++ herwig++-2.6.0/debian/compat	2016-01-26 14:15:06.0 +
@@ -1 +1 @@
-8
+9
diff -Nru herwig++-2.6.0/debian/control herwig++-2.6.0/debian/control
--- herwig++-2.6.0/debian/control	2012-06-13 10:18:54.0 +
+++ herwig++-2.6.0/debian/control	2016-01-26 14:15:13.0 +
@@ -3,8 +3,7 @@
 Priority: optional
 Maintainer: Debian Science Maintainers 
 Uploaders: Lifeng Sun 
-DM-Upload-Allowed: yes
-Build-Depends: debhelper (>= 8.0.0), autotools-dev, dh-autoreconf, libthepeg-dev, libfastjet-dev, libfastjettools-dev, libfastjetplugins-dev, libboost-dev, libgsl0-dev, gfortran, chrpath
+Build-Depends: debhelper (>= 9), autotools-dev, dh-autoreconf, libthepeg-dev, libfastjet-dev, libfastjettools-dev, libfastjetplugins-dev, libboost-dev, libgsl-dev, gfortran, chrpath
 Standards-Version: 3.9.3
 Homepage: http://projects.hepforge.org/herwig/
 Vcs-Git: git://git.debian.org/git/debian-science/packages/herwig++.git
diff -Nru herwig++-2.6.0/debian/rules herwig++-2.6.0/debian/rules
--- herwig++-2.6.0/debian/rules	2012-07-15 21:16:11.0 +
+++ herwig++-2.6.0/debian/rules	2016-01-26 13:47:46.0 +
@@ -16,14 +16,6 @@
 
 export CPPFLAGS CFLAGS CXXFLAGS LDFLAGS DEB_HOST_MULTIARCH
 
-override_dh_auto_configure:
-	dh_auto_configure -- \
-		--with-thepeg=/usr \
-		--with-gsl=/usr \
-		--with-boost=/usr \
-		--with-fastjet=/usr \
-		--libdir=$(LIBPATH)
-
 override_dh_auto_install:
 	dh_auto_install --max-parallel=1
 	chrpath -d debian/tmp/$(LIBPATH)/Herwig++/HwMPI.so


signature.asc
Description: PGP signature

Processed: herwig++: diff for NMU version 2.6.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 805844 + patch
Bug #805844 [src:herwig++] herwig++: Fails to build with GSL 2
Added tag(s) patch.
> tags 805844 + pending
Bug #805844 [src:herwig++] herwig++: Fails to build with GSL 2
Added tag(s) pending.

-- 
805844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 777583

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 777583 + pending
Bug #777583 [smartmontools] incorrect debian/copyright for smartmontools 
violates Debian policy
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
777583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#812276: marked as done (knot-resolver: FTBFS: '.../tinyweb/*': No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 15:55:37 +
with message-id 
and subject line Bug#812276: fixed in knot-resolver 1.0.0~beta2-123-g6134920-1
has caused the Debian Bug report #812276,
regarding knot-resolver: FTBFS: '.../tinyweb/*': No such file or directory
to be marked as done.

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

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


-- 
812276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: knot-resolver
Version: 1.0.0~beta2-104-ge110f97-1
Severity: serious
Justification: fails to build from source

Automatic builds of knot-resolver have been failing because they never
install /usr/lib/knot-resolver/tinyweb/*, whose permissions are
therefore impossible to fix:

  chmod -x debian/tmp/usr/lib/knot-resolver/tinyweb/*
  chmod: cannot access 'debian/tmp/usr/lib/knot-resolver/tinyweb/*': No such 
file or directory
  debian/rules:32: recipe for target 'override_dh_auto_install' failed
  make[1]: *** [override_dh_auto_install] Error 1
  make[1]: Leaving directory '/«PKGBUILDDIR»'
  debian/rules:26: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2

Could you please take a look?

Thanks!
--- End Message ---
--- Begin Message ---
Source: knot-resolver
Source-Version: 1.0.0~beta2-123-g6134920-1

We believe that the bug you reported is fixed in the latest version of
knot-resolver, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 812...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated knot-resolver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 26 Jan 2016 15:00:54 +0100
Source: knot-resolver
Binary: knot-resolver knot-resolver-dbg
Architecture: source amd64
Version: 1.0.0~beta2-123-g6134920-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging 
Changed-By: Ondřej Surý 
Description:
 knot-resolver - caching, DNSSEC-validating DNS resolver
 knot-resolver-dbg - Debug symbols for Knot DNS Resolver
Closes: 812276
Changes:
 knot-resolver (1.0.0~beta2-123-g6134920-1) unstable; urgency=medium
 .
   * Imported Upstream version 1.0.0~beta2-123-g6134920
   * Mangle tinyweb only if it exists (Closes: #812276)
   * Mute lintian error about missing tinyweb.js sources and mute lintian
 warnings about shared library
Checksums-Sha1:
 cd5309fc4ef0d4cfb85e27326c733aa39ba0146c 2519 
knot-resolver_1.0.0~beta2-123-g6134920-1.dsc
 bb0550f2eb990d7950b249935c19e175499d0137 435420 
knot-resolver_1.0.0~beta2-123-g6134920.orig.tar.xz
 223ac92128953ddebfefe709733c3207d3628b36 193908 
knot-resolver_1.0.0~beta2-123-g6134920-1.debian.tar.xz
 6456c64c70f109f5c55712f0ac05f24fb3b86b42 1027108 
knot-resolver-dbg_1.0.0~beta2-123-g6134920-1_amd64.deb
 e04e9c63756fc1ff30cb7a9eb9192ca80f0f319d 1778982 
knot-resolver_1.0.0~beta2-123-g6134920-1_amd64.deb
Checksums-Sha256:
 b6e2bc1842a9f4bea65ecac23c2cc2add8eb6703c5b0c31f0cee3775f7f145db 2519 
knot-resolver_1.0.0~beta2-123-g6134920-1.dsc
 c29ba84892ad2c0ce042588d124d24bcb8d2f7bf8e480733912e6d50600c9591 435420 
knot-resolver_1.0.0~beta2-123-g6134920.orig.tar.xz
 beebecfb74bd7eea999042106207f0305e93523f3cb0c71daa6ad4cb0deaf398 193908 
knot-resolver_1.0.0~beta2-123-g6134920-1.debian.tar.xz
 095293d76fad0e31d593c5ab1866b46d5366ee684da0f53563249d72ae27440d 1027108 
knot-resolver-dbg_1.0.0~beta2-123-g6134920-1_amd64.deb
 55d562f13fc1566072f6f6069e94d63272dbe6e95a7e108e16cf6249e6047243 1778982 
knot-resolver_1.0.0~beta2-123-g6134920-1_amd64.deb
Files:
 e1132e80d7777eb28b534fd08c18 2519 net optional 
knot-resolver_1.0.0~beta2-123-g6134920-1.dsc
 0c279ca2b7587d091c73a37c9ec083e4 435420 net optional 
knot-resolver_1.0.0~beta2-123-g6134920.orig.tar.xz
 6edfe078ca3dd0f41dfb5279fa94f651 193908 net optional 
knot-resolver_1.0.0~beta2-123-g6134920-1.debian.tar.xz
 5abd07e85843a17c97df14319025e82c 1027108 debug extra 
knot-resolver-dbg_1.0.0~beta2-123-g6134920-1_amd64.deb
 2dd2a328b44c9151bcd669de398ecd90 1778982 net optional 

Bug#808849: marked as done (fso-frameworkd: FTBFS: cp: cannot stat 'debian/tmp/usr/bin': No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 15:52:32 +
with message-id 
and subject line Bug#808849: fixed in fso-frameworkd 0.10.1-3
has caused the Debian Bug report #808849,
regarding fso-frameworkd: FTBFS: cp: cannot stat 'debian/tmp/usr/bin': No such 
file or directory
to be marked as done.

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

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


-- 
808849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fso-frameworkd
Version: 0.10.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

fso-frameworkd fails to build from source in unstable/amd64:

  [..]

  changing mode of 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/usr/bin/frameworkd
 to 755
  changing mode of 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/usr/bin/dump-netlink
 to 755
  changing mode of 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/usr/bin/opimd_fix_db
 to 755
  running install_data
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/dbus-1
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/dbus-1/system.d
  copying etc/dbus-1/system.d/frameworkd.conf -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/dbus-1/system.d
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/init.d
  copying etc/init.d/frameworkd -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/init.d
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/schema
  copying etc/freesmartphone/opreferences/schema/phone.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/schema/
  copying etc/freesmartphone/opreferences/schema/profiles.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/schema/
  copying etc/freesmartphone/opreferences/schema/rules.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/schema/
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/profiles
  copying etc/freesmartphone/opreferences/conf/profiles/default.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/profiles/
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/phone
  copying etc/freesmartphone/opreferences/conf/phone/default.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/phone
  copying etc/freesmartphone/opreferences/conf/phone/silent.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/phone
  copying etc/freesmartphone/opreferences/conf/phone/vibrate.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/phone
  copying etc/freesmartphone/opreferences/conf/phone/ring.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/phone
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/rules

Processed: cloning 812605, reassign -1 to ruby-distribution, severity of -1 is serious ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 812605 -1
Bug #812605 [release.debian.org] RM: ruby-distribution/0.7.3+dfsg-1
Bug 812605 cloned as bug 812793
> reassign -1 ruby-distribution
Bug #812793 [release.debian.org] RM: ruby-distribution/0.7.3+dfsg-1
Bug reassigned from package 'release.debian.org' to 'ruby-distribution'.
Ignoring request to alter found versions of bug #812793 to the same values 
previously set
Ignoring request to alter fixed versions of bug #812793 to the same values 
previously set
> severity -1 serious
Bug #812793 [ruby-distribution] RM: ruby-distribution/0.7.3+dfsg-1
Severity set to 'serious' from 'normal'
> retitle -1 Build-Depends not installable in testing
Bug #812793 [ruby-distribution] RM: ruby-distribution/0.7.3+dfsg-1
Changed Bug title to 'Build-Depends not installable in testing' from 'RM: 
ruby-distribution/0.7.3+dfsg-1'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812605
812793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: cloning 812606, reassign -1 to ruby-integration, severity of -1 is serious ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 812606 -1
Bug #812606 [release.debian.org] RM: ruby-integration/0.1.0-1
Bug 812606 cloned as bug 812794
> reassign -1 ruby-integration
Bug #812794 [release.debian.org] RM: ruby-integration/0.1.0-1
Bug reassigned from package 'release.debian.org' to 'ruby-integration'.
Ignoring request to alter found versions of bug #812794 to the same values 
previously set
Ignoring request to alter fixed versions of bug #812794 to the same values 
previously set
> severity -1 serious
Bug #812794 [ruby-integration] RM: ruby-integration/0.1.0-1
Severity set to 'serious' from 'normal'
> retitle -1 Build-Depends not installable in testing
Bug #812794 [ruby-integration] RM: ruby-integration/0.1.0-1
Changed Bug title to 'Build-Depends not installable in testing' from 'RM: 
ruby-integration/0.1.0-1'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812606
812794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#812696: marked as done (util-linux: FTBFS on armel, armhf, hppa, mips* - setarch testsuite failure)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 16:09:07 +
with message-id 
and subject line Bug#812696: fixed in util-linux 2.27.1-3
has caused the Debian Bug report #812696,
regarding util-linux: FTBFS on armel, armhf, hppa, mips* - setarch testsuite 
failure
to be marked as done.

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

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


-- 
812696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: util-linux
Version: 2.27.1-2
Severity: serious

Hi,

util-linux FTBFS on the listed architectures with the following
testsuite failure:

     script: /«PKGBUILDDIR»/tests/ts/misc/setarch
sub dir: /«PKGBUILDDIR»/tests/ts/misc
top dir: /«PKGBUILDDIR»/tests
   self: /«PKGBUILDDIR»/tests/ts/misc
  test name: setarch
  test desc: setarch
  component: misc
  namespace: misc/setarch
verbose: yes
 output: /«PKGBUILDDIR»/tests/output/misc/setarch
   valgrind: /«PKGBUILDDIR»/tests/output/misc/setarch.vgdump
   expected: /«PKGBUILDDIR»/tests/expected/misc/setarch
 mountpoint: /«PKGBUILDDIR»/tests/output/misc/setarch-mnt

 misc: rev...  OK
 misc: setarch...  FAILED (misc/setarch)
= script: /«PKGBUILDDIR»/tests/ts/misc/setarch =
= OUTPUT =
 1  Switching on ADDR_NO_RANDOMIZE.
 2  Switching on FDPIC_FUNCPTRS.
 3  Switching on MMAP_PAGE_ZERO.
 4  Switching on ADDR_COMPAT_LAYOUT.
 5  Switching on READ_IMPLIES_EXEC.
 6  Switching on ADDR_LIMIT_32BIT.
 7  Switching on SHORT_INODE.
 8  Switching on WHOLE_SECONDS.
 9  Switching on STICKY_TIMEOUTS.
10  Switching on ADDR_LIMIT_3GB.
11  Switching on UNAME26.
12  FATAL: kernel too old
= EXPECTED ===
 1  Switching on ADDR_NO_RANDOMIZE.
 2  Switching on FDPIC_FUNCPTRS.
 3  Switching on MMAP_PAGE_ZERO.
 4  Switching on ADDR_COMPAT_LAYOUT.
 5  Switching on READ_IMPLIES_EXEC.
 6  Switching on ADDR_LIMIT_32BIT.
 7  Switching on SHORT_INODE.
 8  Switching on WHOLE_SECONDS.
 9  Switching on STICKY_TIMEOUTS.
10  Switching on ADDR_LIMIT_3GB.
11  Switching on UNAME26.
12  success
= O/E diff ===
--- /«PKGBUILDDIR»/tests/output/misc/setarch2016-01-25 14:30:44.350004343 
+
+++ /«PKGBUILDDIR»/tests/expected/misc/setarch  2015-10-05 14:18:43.453759070 
+
@@ -9,4 +9,4 @@
 Switching on STICKY_TIMEOUTS.
 Switching on ADDR_LIMIT_3GB.
 Switching on UNAME26.
-FATAL: kernel too old
+success
==

This is probably related to bug #806911 in glibc and the increase of
the minimum kernel version to 3.2 on non-x86 arches.

The package also FTBFS on alpha and ppc64 but the error is different
there.

Thanks,
James

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.27.1-3

We believe that the bug you reported is fixed in the latest version of
util-linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 812...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated util-linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 26 Jan 2016 15:45:51 +0100
Source: util-linux
Binary: util-linux util-linux-locales mount bsdutils fdisk-udeb libblkid1 
libblkid1-udeb libblkid-dev libfdisk1 libfdisk1-udeb libfdisk-dev libmount1 
libmount-dev libsmartcols1 libsmartcols1-udeb libsmartcols-dev libuuid1 
uuid-runtime libuuid1-udeb uuid-dev util-linux-udeb
Architecture: source amd64 all
Version: 2.27.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian util-linux Maintainers 
Changed-By: Andreas Henriksson 
Description:
 bsdutils   - basic utilities from 4.4BSD-Lite
 fdisk-udeb - Manually partition a hard drive (fdisk) (udeb)
 libblkid-dev - block device ID library - headers and static libraries
 libblkid1  - 

Bug#812681: [help] Bug#812681: mira: FTBFS with flex >= 2.6]

[Jakub Wilk]

* Andreas Tille , 2016-01-25, 22:06:

sorry, I have no idea about fley and need help to fix this problem.


I think it's a bit premature to ask debian-mentors for help when your RC 
bug is 7 minutes old. What you could do instead is:


* Wait a bit longer. Perhaps one of the numerous co-maintainers knows 
how to fix the bug, but they all busy or asleep at the moment?

* Ask on the team's mailing list.
* Ask upstream.

(Not necessarily in that order.)


g++ -DPACKAGE_NAME=\"mira\" -DPACKAGE_TARNAME=\"mira\" -DPACKAGE_VERSION=\"4.9.5_2\" -DPACKAGE_STRING=\"mira\ 4.9.5_2\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"mira\" -DVERSION=\"4.9.5_2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DENABLE64=1 
-DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1 -DSTDC_HEADERS=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -Drestrict=__restrict -DHAVE_STDLIB_H=1 
-DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DLSTAT_FOLLOWS_SLASHED_SYMLINK=1 -DHAVE_STRFTIME=1 -DHAVE_MEMSET=1 -DHAVE_FSEEKO=1 -DHAVE_ISBLANK=1 
-DHAVE_BOOST=/\*\*/ -DHAVE_BOOST_THREAD=/\*\*/ -DHAVE_BOOST_REGEX=/\*\*/ -DHAVE_BOOST_SYSTEM=/\*\*/ -DHAVE_BOOST_FILESYSTEM=/\*\*/ -DHAVE_BOOST_IOSTREAMS=/\*\*/ 
-DHAVE_LIBRT=1 -DHAVE_GZOFFSET=1 -DBOUNDTRACKFLAG=1 -DBUGTRACKFLAG=1 -I.  -I../../src  -Wdate-time  -DPUBLICQUIET -DAJ_Linux64 -g -O0 -fstack-protector-strong -Wformat 
-Werror=format-security  -I/usr/include -O3 -funroll-loops -pthread -I/usr/include -I/usr/include -Werror=uninitialized -Werror=return-type -Werror=parentheses 
-Werror=unused-value -std=c++14 -c -o exp_flexer.o exp_flexer.cc
exp_flexer.cc: In member function 'virtual int EXPFlexLexer::yylex()':
exp_flexer.cc:766:9: error: no match for 'operator=' (operand types are 'std::istream {aka 
std::basic_istream}' and 'std::istream* {aka std::basic_istream*}')
   yyin = & std::cin;
^


The problem is that exp_flexer.cc was not regenerated from the 
corresponding *.ll file at build time. Instead, the file included in the 
.orig.tar (which was generated by an older flex) was used.


Removing the pre-generated flex output fixed it for me:

find -name '*.ll' | sed -e 's/[.]ll$/.cc/' | xargs rm

--
Jakub Wilk

Processed: tagging 810060

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 810060 + pending
Bug #810060 [python3-wreport] python3-wreport: Missing depends on python3 
interpreter
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
810060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#812796: tokyocabinet ftbfs on ppc64el, failing to run the tests

[Matthias Klose]

Package: src:tokyocabinet
Version: 1.4.48-4
Severity: serious
Tags: sid stretch

seen in 20160126 unstable:

AA@A01A2A9CA515D7E849493@98@24787308E46B9E6@44B098 (3850)
AB3@475D023A21312976ECAA2728AD10C64778CAB06279C468 (3900)
AC9AAD2EEE@CEC9124524674647@619B17A@EB85A53@01D832 (3950)
4DACD34D4B742@C0@02C0DA@9848492@C42@37E520E5480B40 (4000)
4E02000@@44331A6C3A845B@1AE8@0CB7DD@D974C048272CB4Makefile:236: recipe for 
target 'check-hdb' failed

make[2]: *** [check-hdb] Segmentation fault
make[2]: Leaving directory '/home/doko/tmp/tokyocabinet-1.4.48'
Makefile:166: recipe for target 'check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory '/home/doko/tmp/tokyocabinet-1.4.48'
dh_auto_test: make -j1 check returned exit code 2
debian/rules:9: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2

Processed: cloning 812606, reassign -1 to ruby-integration, severity of -1 is serious ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 812606 -1
Bug #812606 [release.debian.org] RM: ruby-integration/0.1.0-1
Bug 812606 cloned as bug 812801
> reassign -1 ruby-integration
Bug #812801 [release.debian.org] RM: ruby-integration/0.1.0-1
Bug reassigned from package 'release.debian.org' to 'ruby-integration'.
Ignoring request to alter found versions of bug #812801 to the same values 
previously set
Ignoring request to alter fixed versions of bug #812801 to the same values 
previously set
> severity -1 serious
Bug #812801 [ruby-integration] RM: ruby-integration/0.1.0-1
Severity set to 'serious' from 'normal'
> retitle -1 Build-Depends not installable in testing
Bug #812801 [ruby-integration] RM: ruby-integration/0.1.0-1
Changed Bug title to 'Build-Depends not installable in testing' from 'RM: 
ruby-integration/0.1.0-1'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812606
812801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#812801: marked as done (Build-Depends not installable in testing)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 18:23:52 +0100
with message-id <20160126172352.gb20...@percival.namespace.at>
and subject line mistyped
has caused the Debian Bug report #812801,
regarding Build-Depends not installable in testing
to be marked as done.

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

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


-- 
812801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,

ruby-integration Build-Depends on ruby-gsl, which is not in testing.
(Also nobody seems to be working on fixing ruby-gsl for it to reenter
testing.)

Thanks,
Christian
--- End Message ---
--- Begin Message ---
mistyped a command causing a new clone to be born. therefore
closing, sorry.

Christian--- End Message ---

Bug#759777: marked as done (tt-rss: Partially broken by libjs-dojo-core/dijit upgrade)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 18:40:10 +0100
with message-id <20160126174009.GA30605@earth>
and subject line Close: Partially broken by libjs-dojo-core/dijit upgrade
has caused the Debian Bug report #759777,
regarding tt-rss: Partially broken by libjs-dojo-core/dijit upgrade
to be marked as done.

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

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


-- 
759777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tt-rss
Version: 1.13+dfsg-1
Severity: normal

After libjs-dojo-core/dijit just upgraded in testing (from 1.7.2+dfsg-1 to
1.10.0+dfsg-1), tt-rss' UI is partially broken.  All the feed icons in the
left menu/tree are gone, and the roll-over highlight on all pop-up menu
items is not rendered correctly.

Downgrading this pair of packages back to 1.7.2+dfsg-1 (hooray
snapshot.debian.org) is sufficient to fix the problem.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages tt-rss depends on:
ii  dbconfig-common1.8.47+nmu1
ii  debconf [debconf-2.0]  1.5.53
ii  init-system-helpers1.21
ii  libapache2-mod-php55.6.0~rc4+dfsg-4
ii  libjs-dojo-core1.10.0+dfsg-1
ii  libjs-dojo-dijit   1.10.0+dfsg-1
ii  libjs-scriptaculous1.9.0-2
ii  libphp-phpmailer   5.2.8+dfsg-1
ii  php-gettext1.0.11-1
ii  php5   5.6.0~rc4+dfsg-4
ii  php5-cli   5.6.0~rc4+dfsg-4
ii  php5-json  1.3.6-1
ii  php5-mysql 5.6.0~rc4+dfsg-4
ii  php5-pgsql 5.6.0~rc4+dfsg-4
ii  phpqrcode  1.1.4-1

Versions of packages tt-rss recommends:
ii  apache2  2.4.10-1
ii  apache2-bin [httpd]  2.4.10-1
ii  lighttpd [httpd] 1.4.35-3
ii  php5-gd  5.6.0~rc4+dfsg-4
ii  php5-mcrypt  5.6.0~rc4+dfsg-4

Versions of packages tt-rss suggests:
ii  mysql-client   5.5.37-1
ii  mysql-client-5.5 [mysql-client]5.5.37-1
ii  mysql-server   5.5.37-1
ii  php-apc4.0.6-1
ii  php5-apcu [php-apc]4.0.6-1
ii  postgresql-client-9.3 [postgresql-client]  9.3.4-2
ii  sphinxsearch   2.0.4-1.1

-- Configuration Files:
/etc/default/tt-rss changed [not included]
/etc/tt-rss/apache.conf changed [not included]
/etc/tt-rss/config.php changed [not included]

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Version: 15.7+git20151123+dfsg-1

Hi,

I use 15.7+git20151123 with dojo/dijit for quite some time now and I
guess we don't need a bug with serious severity. Nevertheless not
all UI problems have been solved yet. E.g. the categories are still
all opened by default (this is done by a debian specific patch.
Without this patch all categories are closed on reload).

This kind of problems are also described in #773236, so let's close
this one.

-- Sebastian


signature.asc
Description: PGP signature
--- End Message ---

Bug#812681: [help] Bug#812681: mira: FTBFS with flex >= 2.6]

[Andreas Tille]

Hi Jakub,

On Tue, Jan 26, 2016 at 05:12:26PM +0100, Jakub Wilk wrote:
> * Andreas Tille , 2016-01-25, 22:06:
> >sorry, I have no idea about fley and need help to fix this problem.
> 
> I think it's a bit premature to ask debian-mentors for help when your RC bug
> is 7 minutes old. What you could do instead is:
> 
> * Wait a bit longer. Perhaps one of the numerous co-maintainers knows how to
> fix the bug, but they all busy or asleep at the moment?

The thing is that I know my co-maintainers well enough regarding their
dense schedule (and knowledge about things like flex) that waiting
another 24 hours would not have changed anything.

> * Ask on the team's mailing list.

Receives the message via the bug e-mail anyway.

> * Ask upstream.

Yes, I might pick this option next time.
 
> (Not necessarily in that order.)
> 
> >exp_flexer.cc:766:9: error: no match for 'operator=' (operand types are 
> >'std::istream {aka std::basic_istream}' and 'std::istream* {aka 
> >std::basic_istream*}')
> >   yyin = & std::cin;
> >^
> 
> The problem is that exp_flexer.cc was not regenerated from the corresponding
> *.ll file at build time. Instead, the file included in the .orig.tar (which
> was generated by an older flex) was used.
> 
> Removing the pre-generated flex output fixed it for me:
> 
> find -name '*.ll' | sed -e 's/[.]ll$/.cc/' | xargs rm

Thanks a lot for your patience and help

Andreas. 

-- 
http://fam-tille.de

Bug#777791: [PATCH] ball: ftbfs with GCC-5

[Danny Edel]

Hello Andreas,

I have had some spare time and spent it on the ball package.  I hope
that helps you in getting the package back into Debian.

Some notes regarding the patch:

* I dropped the gcc5.patch, since it created an ambiguous overload of
getline -- Upstream added one themselves in the meantime.

* The patches in debian/patches/backports/ are all cherry-picked from
the upstream git repository at github.com/BALL-project/ball -- their
first line will tell you the commit ID.  Take a look at the branch
qt5_latest if they are not yet in master.
They were created with git format-patch -1 , I hope that's all
right.

* The most problematic part was DOCKING/COMMON/poseClustering.h.  It
seems to break with boost-1.56, because it assumes a certain class is
copyable that has been adapted to c++11's "move" idea.
The commit that breaks it is
https://github.com/boostorg/graph/commit/cb26ccf

I have used a very crude workaround (I have defined a BOOST_* symbol
suggesting that the compiler would not support moves), this needs to be
properly ported to current boost by BALL upstream.  Please try to get in
contact with upstream, and have them properly port the code.

* The upstream code is also not yet ready for libeigen3 version 3.3
(currently in beta) that drops some compatibility code.  I added a
Build-Conflicts to make the buildd's aware of that.  This also needs to
be ported by upstream.

In order to build the package anyway, I had to add to my sources.list a
snapshot.debian.org containing the older version (its header-only, so
it's compiled into the binary and does not generate a run-time
dependency).  sources.list line containing a suitable old version:

deb http://snapshot.debian.org/archive/debian/20150924T154447Z sid main



* I activated the test suite in d/rules -- mainly because I was not sure
if my crude workaround broke anything.
On my test builds, the Socket_test sometimes™ failed.  Maybe there is a
race condition, I don't know.  Could also be my old hardware bitrotting
away...

* Since I used the older libeigen, I set it as a "system" library in
cmake, which prevents the compile log from generating warnings when
eigen uses deprecated features  (just distracted me while working on
ball, feel free to drop that patch).


The patch is based against b915af8eff, which was today (jan 26) the
current master in the debian-med repository.


After all this hacking, the package builds and the resulting .deb's seem
usable to me, but I dont understand enough biochemics to make anything
out of it : )


I can't tell myself if the patch is of acceptable quality, please have a
look over it before adopting.  Feedback would be much appreciated, this
is my first non-trivial contribution.


I hope this helps,


- Danny
diff --git a/debian/control b/debian/control
index ceb15db..2b09efd 100644
--- a/debian/control
+++ b/debian/control
@@ -39,6 +39,7 @@ Build-Depends-Indep: doxygen,
  texlive-latex-recommended,
  texlive-fonts-recommended,
  texlive-latex-extra
+Build-Conflicts: libeigen3-dev( >= 3.3~ )
 Standards-Version: 3.9.6
 Vcs-Browser: https://anonscm.debian.org/cgit/debian-med/ball.git
 Vcs-Git: git://anonscm.debian.org/debian-med/ball.git
diff --git a/debian/patches/adapt-poseClustering-test-archive-boost1.58 b/debian/patches/adapt-poseClustering-test-archive-boost1.58
new file mode 100644
index 000..c5349c0
--- /dev/null
+++ b/debian/patches/adapt-poseClustering-test-archive-boost1.58
@@ -0,0 +1,10 @@
+Subject: Adapt archive version number to 12 (boost1.58)
+
+The upstream boost::archive file was most likely compiled against a more
+recent (version no. 13) serialization library, but boost1.58 (currently
+highest in Debian) only has version no. 12
+--- a/source/TEST/data/PoseClustering_wardtree.dat
 b/source/TEST/data/PoseClustering_wardtree.dat
+@@ -1 +1 @@
+-22 serialization::archive 13 0 0 15 14 0 0 1 0 0 1 0.0e+00 1 0 1 1 0.0e+00 1 0 2 1 0.0e+00 1 0 3 1 0.0e+00 1 0 4 1 0.0e+00 1 0 5 1 0.0e+00 1 0 6 1 0.0e+00 1 0 7 1 0.0e+00 0 0 2 2.930124538e-05 0 0 3 1.017511487e+00 0 0 4 2.349177122e+00 0 0 2 9.453108311e-01 0 0 2 1.095688367e-05 0 0 4 5.062472916e+01 0 0 8 5.839497375e+01 8 1 0 0 8 0 9 3 9 8 10 2 10 9 11 7 11 6 12 4 12 5 13 12 13 11 14 13 14 10 14
++22 serialization::archive 12 0 0 15 14 0 0 1 0 0 1 0.0e+00 1 0 1 1 0.0e+00 1 0 2 1 0.0e+00 1 0 3 1 0.0e+00 1 0 4 1 0.0e+00 1 0 5 1 0.0e+00 1 0 6 1 0.0e+00 1 0 7 1 0.0e+00 0 0 2 2.930124538e-05 0 0 3 1.017511487e+00 0 0 4 2.349177122e+00 0 0 2 9.453108311e-01 0 0 2 1.095688367e-05 0 0 4 5.062472916e+01 0 0 8 5.839497375e+01 8 1 0 0 8 0 9 3 9 8 10 2 10 9 11 7 11 6 12 4 12 5 13 12 13 11 14 13 14 10 14
diff --git a/debian/patches/backports/FingerPrintSim-Fix-build.patch b/debian/patches/backports/FingerPrintSim-Fix-build.patch
new file mode 100644
index 000..4f1eeec
--- 

Bug#791840: marked as done (nagios3: FTBFS on sid due to unsatisfiable build-dependency on libgd2-(no)xpm-dev)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 18:23:12 +
with message-id 
and subject line Bug#791840: fixed in nagios3 3.5.1.dfsg-2.1
has caused the Debian Bug report #791840,
regarding nagios3: FTBFS on sid due to unsatisfiable build-dependency on 
libgd2-(no)xpm-dev
to be marked as done.

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

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


-- 
791840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nagios3
Severity: serious

Dear maintainer,

your package nagios3 ftbfs in current sid due to it Build-Depending
on either libgd2-xpm-dev or libgd2-noxpm-dev with versioned
restriction. The source package providing those packages dropped
those transitive packages on libgd-dev in favour of a Provide, though
a versioned dependecy won't be satisfy by a virtual package.

Suggested action is swapping that build-dependency with one on
libgd-dev, alternatively you can remove the version constraints and
keep the old package name, though that's not suggested since they
already were only transitive packages.

Thanks for maintaining nagios3!

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540 .''`.
more about me:  http://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: nagios3
Source-Version: 3.5.1.dfsg-2.1

We believe that the bug you reported is fixed in the latest version of
nagios3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 791...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated nagios3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jan 2016 18:55:32 +0100
Source: nagios3
Binary: nagios3-common nagios3-cgi nagios3 nagios3-core nagios3-doc nagios3-dbg
Architecture: source amd64 all
Version: 3.5.1.dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Tobias Frost 
Description:
 nagios3- host/service/network monitoring and management system
 nagios3-cgi - cgi files for nagios3
 nagios3-common - support files for nagios3
 nagios3-core - host/service/network monitoring and management system core files
 nagios3-dbg - debugging symbols and debug stuff for nagios3
 nagios3-doc - documentation for nagios3
Closes: 791840
Changes:
 nagios3 (3.5.1.dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * B-D on libgd-dev instead libgd2-(no)xpm-dev (Closes: #791840)
Checksums-Sha1:
 f9c2d234ad6bcf08323771537d8b98c7f4e01c7f 2370 nagios3_3.5.1.dfsg-2.1.dsc
 f48b8a37925abf73163e0f5b7e47660adf3d4b8d 71412 
nagios3_3.5.1.dfsg-2.1.debian.tar.xz
 17fe4ea292d9a9a9a4bef4a42f4b8e7b7b62920c 76082 
nagios3-common_3.5.1.dfsg-2.1_all.deb
 a7c712e105afe5252ac650e2985ff6ee24cd8a33 27266 
nagios3-doc_3.5.1.dfsg-2.1_all.deb
Checksums-Sha256:
 7c98f54f044179f37f01522d104c8f72850e3501ab5035bfb293373576cf49aa 2370 
nagios3_3.5.1.dfsg-2.1.dsc
 9790d2f1b1a5a6361207d1e30229838c07d38405ddc74a32c69793a92c4a3cb0 71412 
nagios3_3.5.1.dfsg-2.1.debian.tar.xz
 f6989eb6305669346b37c03501fa3866aa64253103f1154c79d481dba0bb93c3 76082 
nagios3-common_3.5.1.dfsg-2.1_all.deb
 14495cd69afb75b9c3d6363fc613ddaf6b8bb49d9b0478b64921823d0b8140f3 27266 
nagios3-doc_3.5.1.dfsg-2.1_all.deb
Files:
 fda375dbe06f991d630080ed01900eb8 2370 net optional nagios3_3.5.1.dfsg-2.1.dsc
 984f4da3cfa27eb409cabfcbc9fe5993 71412 net optional 
nagios3_3.5.1.dfsg-2.1.debian.tar.xz
 b1c49967ef92b70f104ce2d7974e9798 76082 net optional 
nagios3-common_3.5.1.dfsg-2.1_all.deb
 27dcbe23b4c5edfd3ff9920732f22bc9 27266 doc optional 
nagios3-doc_3.5.1.dfsg-2.1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWpRIoAAoJEJFk+h0XvV020WAQAKjuFQR5Hem3LkD7/SQsK8FX

Bug#811428: [debian-mysql] Bug#811428: Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

[Robie Basak]

Hi Salvatore,

On Tue, Jan 26, 2016 at 01:19:26PM +0100, Salvatore Bonaccorso wrote:
> Thank you looks good to me.
> 
> I haven't seen the same for jessie, but assuming it is basically the
> same and matching what you showed me initially from git, let's go
> ahead with an upload.

FYI, we're still working on this. I've hit some kind of issue with my
build chroot that I created from scratch for this task, so I think it
may be a bug in sid somewhere. I'm investigating. I'd prefer to
understand the root cause so that I can be sure that we don't upload bad
binaries.

> Please remember to do the jessie-security first (built with -sa) and
> then after ~20 minutes the wheezy-security one (explicitly without
> -sa, and not including the orig source tarball; this is due to some
> limitation in the archive software).
> 
> The upload needs to be signed by a a key in the DD keyring.
> 
> I will then wait for the builds and then take care of releasing the
> packages with a DSA.

Ack.

Robie


signature.asc
Description: Digital signature

Bug#812809: yard and ruby-appraiser: error when trying to install together

[Ralf Treinen]

Package: ruby-appraiser,yard
Version: ruby-appraiser/0.2.0-2
Version: yard/0.8.7.6-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-01-26
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Preconfiguring packages ...
Selecting previously unselected package libyaml-0-2:amd64.
(Reading database ... 10941 files and directories currently installed.)
Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ...
Unpacking libyaml-0-2:amd64 (0.1.6-3) ...
Selecting previously unselected package libssl1.0.2:amd64.
Preparing to unpack .../libssl1.0.2_1.0.2e-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2e-1) ...
Selecting previously unselected package openssl.
Preparing to unpack .../openssl_1.0.2e-1_amd64.deb ...
Unpacking openssl (1.0.2e-1) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20160104_all.deb ...
Unpacking ca-certificates (20160104) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-4) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.1.0+dfsg-2_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.0+dfsg-2) ...
Selecting previously unselected package libjs-jquery.
Preparing to unpack .../libjs-jquery_1.11.3+dfsg-4_all.deb ...
Unpacking libjs-jquery (1.11.3+dfsg-4) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../rubygems-integration_1.10_all.deb ...
Unpacking rubygems-integration (1.10) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../ruby-power-assert_0.2.6-1_all.deb ...
Unpacking ruby-power-assert (0.2.6-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../ruby-test-unit_3.1.7-1_all.deb ...
Unpacking ruby-test-unit (3.1.7-1) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../ruby-minitest_5.8.4-1_all.deb ...
Unpacking ruby-minitest (5.8.4-1) ...
Selecting previously unselected package libruby2.2:amd64.
Preparing to unpack .../libruby2.2_2.2.4-1_amd64.deb ...
Unpacking libruby2.2:amd64 (2.2.4-1) ...
Selecting previously unselected package ruby2.2.
Preparing to unpack .../ruby2.2_2.2.4-1_amd64.deb ...
Unpacking ruby2.2 (2.2.4-1) ...
Selecting previously unselected package ruby.
Preparing to unpack .../ruby_1%3a2.2.4_all.deb ...
Unpacking ruby (1:2.2.4) ...
Selecting previously unselected package ruby-colored.
Preparing to unpack .../ruby-colored_1.2-2_all.deb ...
Unpacking ruby-colored (1.2-2) ...
Selecting previously unselected package ruby-json.
Preparing to unpack .../ruby-json_1.8.3-1+b1_amd64.deb ...
Unpacking ruby-json (1.8.3-1+b1) ...
Selecting previously unselected package ruby-appraiser.
Preparing to unpack .../ruby-appraiser_0.2.0-2_all.deb ...
Unpacking ruby-appraiser (0.2.0-2) ...
Selecting previously unselected package ruby-locale.
Preparing to unpack .../ruby-locale_2.1.2-1_all.deb ...
Unpacking ruby-locale (2.1.2-1) ...
Selecting previously unselected package ruby-text.
Preparing to unpack .../ruby-text_1.3.0-1_all.deb ...
Unpacking ruby-text (1.3.0-1) ...
Selecting previously unselected package ruby-gettext.
Preparing to unpack .../ruby-gettext_3.1.7-1_all.deb ...
Unpacking ruby-gettext (3.1.7-1) ...
Selecting previously unselected package yard.
Preparing to unpack .../yard_0.8.7.6-1_all.deb ...
Unpacking yard (0.8.7.6-1) ...
dpkg: error processing archive /var/cache/apt/archives/yard_0.8.7.6-1_all.deb 
(--unpack):
 trying to overwrite '/usr/lib/ruby/vendor_ruby/rubygems_plugin.rb', which is 
also in package ruby-appraiser 0.2.0-2
Processing triggers for libc-bin (2.21-7) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/yard_0.8.7.6-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/lib/ruby/vendor_ruby/rubygems_plugin.rb

This bug has been filed against both packages. If you, the maintainers of
the two 

Bug#812620: marked as done (libsdl2-image: FTBFS - format not a string literal and no format arguments)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 18:49:01 +
with message-id 
and subject line Bug#812620: fixed in libsdl2-image 2.0.1+dfsg-1
has caused the Debian Bug report #812620,
regarding libsdl2-image: FTBFS - format not a string literal and no format 
arguments
to be marked as done.

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

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


-- 
812620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsdl2-image
Version: 2.0.0+dfsg-3
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
/bin/bash ./libtool  --tag=CC   --mode=compile gcc -DPACKAGE_NAME=\"\" 
-DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" 
-DPACKAGE=\"SDL2_image\" -DVERSION=\"2.0.0\" -DLOAD_JPG=1 -DLOAD_PNG=1 
-DLOAD_TIF=1 -DLOAD_WEBP=1 -DLOAD_BMP=1 -DLOAD_GIF=1 -DLOAD_LBM=1 -DLOAD_PCX=1 
-DLOAD_PNM=1 -DLOAD_TGA=1 -DLOAD_XCF=1 -DLOAD_XPM=1 -DLOAD_XV=1 -I.   
-Wdate-time  -I/usr/include/libpng12 -g -O0 -fstack-protector-strong -Wformat 
-Werror=format-security -pipe -Wall -D_REENTRANT -I/usr/include/SDL2 -c -o 
IMG_lbm.lo IMG_lbm.c
libtool: compile:  gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" 
-DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" 
-DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 
-DLT_OBJDIR=\".libs/\" -DPACKAGE=\"SDL2_image\" -DVERSION=\"2.0.0\" 
-DLOAD_JPG=1 -DLOAD_PNG=1 -DLOAD_TIF=1 -DLOAD_WEBP=1 -DLOAD_BMP=1 -DLOAD_GIF=1 
-DLOAD_LBM=1 -DLOAD_PCX=1 -DLOAD_PNM=1 -DLOAD_TGA=1 -DLOAD_XCF=1 -DLOAD_XPM=1 
-DLOAD_XV=1 -I. -Wdate-time -I/usr/include/libpng12 -g -O0 
-fstack-protector-strong -Wformat -Werror=format-security -pipe -Wall 
-D_REENTRANT -I/usr/include/SDL2 -c IMG_lbm.c  -fPIC -DPIC -o .libs/IMG_lbm.o
IMG_lbm.c: In function 'IMG_LoadLBM_RW':
IMG_lbm.c:479:9: error: format not a string literal and no format arguments 
[-Werror=format-security]
 IMG_SetError( error );
 ^
cc1: some warnings being treated as errors
Makefile:599: recipe for target 'IMG_lbm.lo' failed


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


libsdl2-image-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libsdl2-image
Source-Version: 2.0.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
libsdl2-image, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 812...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
libsdl2-image package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Jan 2016 10:12:59 +0100
Source: libsdl2-image
Binary: libsdl2-image-2.0-0 libsdl2-image-dbg libsdl2-image-dev
Architecture: source
Version: 2.0.1+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Debian SDL packages maintainers 

Changed-By: Gianfranco Costamagna 
Description:
 libsdl2-image-2.0-0 - Image loading library for Simple DirectMedia Layer 2, 
libraries
 libsdl2-image-dbg - Image loading library for Simple DirectMedia Layer 2, 
debugging s
 libsdl2-image-dev - Image loading library for Simple DirectMedia Layer 2, 
development
Closes: 812620
Changes:
 libsdl2-image (2.0.1+dfsg-1) unstable; urgency=low
 .
   * Team upload.
   [ Manuel A. Fernandez Montecelo ]
   * Build-Depends on pkg-config
   * Bump 

Processed: found 809766 in ruby-test-unit/3.1.7-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 809766 ruby-test-unit/3.1.7-1
Bug #809766 [ruby-rubysl-test-unit,ruby-test-unit] ruby-test-unit and 
ruby-rubysl-test-unit: error when trying to install together
Marked as found in versions ruby-test-unit/3.1.7-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
809766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#807196: cvxopt: diff for NMU version 1.1.4-1.4

[Mattia Rizzolo]

Control: tags 807196 + pending

Dear maintainer,

I've prepared an NMU for cvxopt (versioned as 1.1.4-1.4) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for cvxopt-1.1.4 cvxopt-1.1.4

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru cvxopt-1.1.4/debian/changelog cvxopt-1.1.4/debian/changelog
--- cvxopt-1.1.4/debian/changelog	2015-03-15 10:54:07.0 +
+++ cvxopt-1.1.4/debian/changelog	2016-01-26 11:54:03.0 +
@@ -1,3 +1,13 @@
+cvxopt (1.1.4-1.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807196
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 11:53:51 +
+
 cvxopt (1.1.4-1.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru cvxopt-1.1.4/debian/control cvxopt-1.1.4/debian/control
--- cvxopt-1.1.4/debian/control	2011-07-22 15:23:49.0 +
+++ cvxopt-1.1.4/debian/control	2016-01-26 11:53:50.0 +
@@ -4,7 +4,7 @@
 Maintainer: Soeren Sonnenburg 
 Build-Depends: cdbs (>= 0.4.90~), debhelper (>= 5),
  libatlas-base-dev [!powerpc !alpha !arm !armel], libblas-dev, liblapack-dev,
- python-sphinx, libglpk-dev, libfftw3-dev, libgsl0-dev, libdsdp-dev (>= 5.8-4),
+ python-sphinx, libglpk-dev, libfftw3-dev, libgsl-dev, libdsdp-dev (>= 5.8-4),
  texlive-latex-base, texlive-latex-recommended, texlive-latex-extra,
  texlive-fonts-recommended, python-all-dev (>= 2.6.6-3~),
 X-Python-Version: >= 2.5


signature.asc
Description: PGP signature

Processed: cvxopt: diff for NMU version 1.1.4-1.4

[Debian Bug Tracking System]

Processing control commands:

> tags 807196 + pending
Bug #807196 [src:cvxopt] cvxopt: Update build dependencies for GSL 2.x
Added tag(s) pending.

-- 
807196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#809265: marked as done (debci: FTBFS: ./test_blame.sh failed at least one test (test_passing_the_test_resets_the_blame?))

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 19:19:33 +
with message-id 
and subject line Bug#809265: fixed in debci 1.0.2
has caused the Debian Bug report #809265,
regarding debci: FTBFS:  ./test_blame.sh failed at least one test 
(test_passing_the_test_resets_the_blame?)
to be marked as done.

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

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


-- 
809265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debci
Version: 1.0.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

debci fails to build from source in unstable/amd64:

  [..]

  ./test_blame.sh
  ln: failed to create symbolic link 
‘/tmp/tmp.qdthkLehjc/data/packages/unstable/amd64/f/foobar/20151228_221440.autopkgtest.log.gz’:
 File exists
  ln: failed to create symbolic link 
‘/tmp/tmp.VTKBDbCmvI/data/packages/unstable/amd64/f/foobar/20151228_221449.autopkgtest.log.gz’:
 File exists
  test_package_that_never_passed_a_test_cant_blame
  test_failing_test_blames_dependencies
  test_updated_dependency_of_already_failing_package_is_not_blamed
  test_new_dependency_of_already_failing_package_is_not_blamed
  test_passing_the_test_resets_the_blame
  ASSERT:expected:<> but was:
  test_blame_updated_dependency
  test_updated_dependencies_dont_get_blamed_when_package_is_also_updated
  test_package_is_not_blamed_for_its_own_failure
  
  Ran 8 tests.
  
  FAILED (failures=1)
  ☠./test_blame.sh failed at least one test

  [..]

The full build log is attached.


Regards,

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


debci.1.0.1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: debci
Source-Version: 1.0.2

We believe that the bug you reported is fixed in the latest version of
debci, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 809...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated debci package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Jan 2016 18:57:03 -0200
Source: debci
Binary: debci debci-worker debci-collector
Architecture: source
Version: 1.0.2
Distribution: unstable
Urgency: medium
Maintainer: Antonio Terceiro 
Changed-By: Antonio Terceiro 
Description:
 debci  - continuous integration system for Debian
 debci-collector - continuous integration system for Debian (collector daemon)
 debci-worker - continuous integration system for Debian (worker daemon)
Closes: 809265 811563
Changes:
 debci (1.0.2) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * Fix some excessive amd64 hardcoding in the test suite. Thanks Colin
 Watson!
   * test/test_blame.sh: Sleep for one second between process() calls, to
 ensure that timestamps in run IDs are different. (Closes: #809265)
 .
   [ Brian Murray ]
   * Include extra information in HTML  tags, such as package name,
 architecture, suite, etc (Closes: #811563)
Checksums-Sha1:
 d9a6b14be68886e0888cfdd1700c583d07767962 1843 debci_1.0.2.dsc
 4d954ba5ef149b0c2f8a9da1db02c909f08c0645 63796 debci_1.0.2.tar.xz
Checksums-Sha256:
 766c01700c7636331751e120f870dd6c44ad03043b63a433c3488be7fa71f40f 1843 
debci_1.0.2.dsc
 6069ffccce4421ada41302c1b01ca8fcb4168b9488e991f279b84c59bdf8b14d 63796 
debci_1.0.2.tar.xz
Files:
 2f723bd7ba0198d02375f58151d7fe6d 1843 devel optional debci_1.0.2.dsc
 8992c9b41f4cfb0d3879692d4c1e421f 63796 devel optional debci_1.0.2.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWp7+QAAoJEPwNsbvNRgveB7QP/is92LEenVresyEHGfofE282
BPdFBFOEgZv4DIja1PrSexnkMFabWU9BXrNEfdzN+KDCFjn6JQgKRG+UIL87ou9/
r9cSgzOIW1hZMeKir7qs4uBrxxD8EPFBmmvrx+kMZVwJgK+LmccW2VUBP3uHbMtU
vMGq42rM1wulgTZyXnwqCfnscdr2eLiPA9LnJXa938cek8Ij+Uq5VU/h5c2LPQCm

Bug#811428: [debian-mysql] Bug#811428: Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

[Salvatore Bonaccorso]

Hi Robie,

On Tue, Jan 26, 2016 at 06:36:06PM +, Robie Basak wrote:
> Hi Salvatore,
> 
> On Tue, Jan 26, 2016 at 01:19:26PM +0100, Salvatore Bonaccorso wrote:
> > Thank you looks good to me.
> > 
> > I haven't seen the same for jessie, but assuming it is basically the
> > same and matching what you showed me initially from git, let's go
> > ahead with an upload.
> 
> FYI, we're still working on this. I've hit some kind of issue with my
> build chroot that I created from scratch for this task, so I think it
> may be a bug in sid somewhere. I'm investigating. I'd prefer to
> understand the root cause so that I can be sure that we don't upload bad
> binaries.

Thanks for the status-update!

Regards,
Salvatore

Bug#812626: libfreecontact-perl: FTBFS - Parse errors: Bad plan. You planned 10 tests but ran 6.

[gregor herrmann]

On Tue, 26 Jan 2016 10:54:14 +0100, Andreas Tille wrote:

> do you have any idea what change might have caused the failures of the
> test suite?
> Feel free to commit proposed changes to Debian Med Git if this might
> simplify your workflow.

I cloned the git repo (very handy :)) and had a look, but I can't
reproduce the test failure, not even when running them manually under
high load.

Some observations:
 
> > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" 
> > "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 
> > 'blib/lib', 'blib/arch')" t/*.t
> > t/01FreeContact.t .. 
> > 1..3
> > ok 1 - use FreeContact;
> > ok 2 - FreeContact->can(...)
> > ok 3 - FreeContact::Predictor->can(...)
> > ok
> > will use 1 OMP threads
> > SSE2 veczweight, wchunk = 32
> > total weight (variation) of alignment = 620.777515304633
> > 
> > seq weight loop for 1000 seqs took 0.012224 secs
> > will use 1 OMP threads
> > calculated column aa frequencies, gap cols = 4
> > calculated pair frequency table in 0.192089 secs
> > collected apc_mean[MI] = 0.174031486973761
> > aa freq sum (cell) = 0.97158936352, pairfreq sum (cell) = 
> > 0.94420985606
> > formed covariance matrix (122/126,4)
> > LU factorization took 9.17976 secs, inverted matrix (incl LUf) in 23.7932 
> > secs
> > density of inverse covariance matrix = 1 (cksum 346842.2)
> > went back to gapped (126) wwi matrix
> > collected apc_mean[l1norm] = 117.987054769839
> > collected apc_mean[fro] = 3.35437751555787
> > all done in 24.6311 secs
> > will use 1 OMP threads
> > SSE2 veczweight, wchunk = 32
> > total weight (variation) of alignment = 561.595172234625
> > t/02test.t . 
> > 1..10
> > ok 1 - use FreeContact;
> > ok 2 - An object of class 'FreeContact::Predictor' isa 
> > 'FreeContact::Predictor'
> > ok 3
> > ok 4
> > ok 5 - precision test
> > ok 6 - timing results test
> > Failed 4/10 subtests

I noticed that the non-perl-test output comes before t/02test.t while
it comes later (after the "ok 3" of t/02test.t) for me. I thought this
might be a parallelization problem but the test was run with -j1, and
it also passes for me with -jN.

> > 
> > Test Summary Report
> > ---
> > t/02test.t   (Wstat: 11 Tests: 6 Failed: 0)
> >   Non-zero wait status: 11
> >   Parse errors: Bad plan.  You planned 10 tests but ran 6.

What's this 11? A timeout?

Maybe related: the last passing test is "timing results test", the
7th test would be (line 47):
like($@, qr/^Caught FreeContact timeout exception:/);


Sorry for being not able to provide more hints; maybe someone is able
to see what's going on here ...


Since the upstream author is also in Uploaders, I'm adding a CC :)


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Various Artists: A Pair Of Brown Eyes


signature.asc
Description: Digital Signature

Bug#777791: [PATCH] ball: ftbfs with GCC-5

[Andreas Tille]

Hi Danny,

thanks for your continuous work on this which is really appreciated.

On Tue, Jan 26, 2016 at 05:34:53PM +0100, Danny Edel wrote:
> I have had some spare time and spent it on the ball package.  I hope
> that helps you in getting the package back into Debian.
> 
> Some notes regarding the patch:
> 
> * I dropped the gcc5.patch, since it created an ambiguous overload of
> getline -- Upstream added one themselves in the meantime.

OK, fine - we should prefer the upstream patch.
 
> * The patches in debian/patches/backports/ are all cherry-picked from
> the upstream git repository at github.com/BALL-project/ball -- their
> first line will tell you the commit ID.  Take a look at the branch
> qt5_latest if they are not yet in master.
> They were created with git format-patch -1 , I hope that's all
> right.

Looks good.
 
> * The most problematic part was DOCKING/COMMON/poseClustering.h.  It
> seems to break with boost-1.56, because it assumes a certain class is
> copyable that has been adapted to c++11's "move" idea.
> The commit that breaks it is
> https://github.com/boostorg/graph/commit/cb26ccf
> 
> I have used a very crude workaround (I have defined a BOOST_* symbol
> suggesting that the compiler would not support moves), this needs to be
> properly ported to current boost by BALL upstream.  Please try to get in
> contact with upstream, and have them properly port the code.

Thanks for the warning.  You are right that we should contact upstream.
Hope they stopped their habit to simply ignores mails from Debian as I
had experienced in the last gcc transistion ...
 
> * The upstream code is also not yet ready for libeigen3 version 3.3
> (currently in beta) that drops some compatibility code.  I added a
> Build-Conflicts to make the buildd's aware of that.  This also needs to
> be ported by upstream.

Well, I realised the conflict which makes the build fail in the very
beginning:

The following packages have unmet dependencies:
 pbuilder-satisfydepends-dummy : Conflicts: libeigen3-dev (>= 3.3~) but 
3.3~beta1-2 is to be installed.
Unable to resolve dependencies!  Giving up...

> In order to build the package anyway, I had to add to my sources.list a
> snapshot.debian.org containing the older version (its header-only, so
> it's compiled into the binary and does not generate a run-time
> dependency).  sources.list line containing a suitable old version:
> 
> deb http://snapshot.debian.org/archive/debian/20150924T154447Z sid main

H, a bit hackish but I'll try to reproduce.  In any case this will
force us to contact upstream. ;-)
 
> * I activated the test suite in d/rules -- mainly because I was not sure
> if my crude workaround broke anything.
> On my test builds, the Socket_test sometimes™ failed.  Maybe there is a
> race condition, I don't know.  Could also be my old hardware bitrotting
> away...

OK.  Testing sounds always good.
 
> * Since I used the older libeigen, I set it as a "system" library in
> cmake, which prevents the compile log from generating warnings when
> eigen uses deprecated features  (just distracted me while working on
> ball, feel free to drop that patch).
> 
> 
> The patch is based against b915af8eff, which was today (jan 26) the
> current master in the debian-med repository.

Yupp, no change since our last mail exchange.
 
> After all this hacking, the package builds and the resulting .deb's seem
> usable to me, but I dont understand enough biochemics to make anything
> out of it : )

I admit that's the same for me.  I trust on the users of the package
to file bug reports. :_)
 
> I can't tell myself if the patch is of acceptable quality, please have a
> look over it before adopting.

Thanks for the warning.  I'll ask Steffen Möller who has personal
contact to upstream to discuss it there.

> Feedback would be much appreciated, this
> is my first non-trivial contribution.

Definitely non-trivial and really helpful.  Thanks a lot.

BTW, if you are actively seeking for other contribution for C++ issues:
The Debian Med team received recently several bugs containing

  FTBFS with GCC 6

in the bug subject.  Feel free to tackle whatever you might like to
work on at

  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-med-packag...@lists.alioth.debian.org

There are several (but not all bugs) we forwarded upstream.  There is
no point in looking into sitplus - here we need to package refectored
upstream from scratch.  Most others could need helping hands.
 
> I hope this helps,

Definitely.  Thanks a lot again

   Andreas.

-- 
http://fam-tille.de

Processed: notfound 809195 in 1.0.6-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 809195 1.0.6-1
Bug #809195 {Done: Michael Biebl } [network-manager] 
network-manager_1.0.10-1_amd64.deb does not update my I.P address correctly 
when I start my VPN
Bug #809494 {Done: Michael Biebl } [network-manager] 
network-manager: NetworkManager 1.0.10-1 does not add default route for VPN
Bug #809526 {Done: Michael Biebl } [network-manager] 
network-manager-openvpn: Fail to set IPv4 route
Bug #810076 {Done: Michael Biebl } [network-manager] 
network-manager: NM does not honor "push route" any more
Bug #812633 {Done: Michael Biebl } [network-manager] 
network-manager-openvpn: Failure to add server pushed route
No longer marked as found in versions network-manager/1.0.6-1.
No longer marked as found in versions network-manager/1.0.6-1.
No longer marked as found in versions network-manager/1.0.6-1.
No longer marked as found in versions network-manager/1.0.6-1.
No longer marked as found in versions network-manager/1.0.6-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
809195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809195
809494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809494
809526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809526
810076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810076
812633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#812656: dogecoin: FTBFS - invalid application of 'sizeof' to incomplete type 'boost::STATIC_ASSERTION_FAILURE'

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> owner 812656 ken...@lexical.tw
Bug #812656 [dogecoin] dogecoin: FTBFS - invalid application of 'sizeof' to 
incomplete type 'boost::STATIC_ASSERTION_FAILURE'
Owner recorded as ken...@lexical.tw.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
812656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#812812: MySQL client library should ship a symbols file, or at least not have a Lintian override to hide the problem

[Otto Kekäläinen]

Package: mysql-5.6
Version: 5.6.28-1
Severity: serious

The mysql-5.5 source package produces the libmysqlclient18 shared
library, main file being libmysqlclient.so.18. So does the mysql-5.6
package too (even using the same "18" version string oddly, are there
no changes in the ABI?).

It seems the mysql-5.5 never shipped a symbols file. In mysql-5.6
there is a specific Lintian override about not shipping the symbols
file:
http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.6.git/tree/debian/libmysqlclient18.lintian-overrides

The Debian policy states "shared libraries must provide either a
symbols file or a shlibs file" at
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html

For implementation tips see also: https://wiki.debian.org/UsingSymbolsFiles

For examples you can also check libmariadb2 symbol file:
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-client-lgpl.git/tree/debian/libmariadb2.symbols
The mariadb-5.5 package used to have a symbols file some years ago in
Debian until it was denied from shipping a libmariadbclient package,
but it can never the less be used as an example too:
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-5.5.git/tree/debian/libmariadbclient18.symbols


Please do the following things:

1) Drop the Lintian override immediately. This problem should not be
hidden on purpose.

2) Add the symbols file and start tracking symbols.

3) If there are problems with the symbols changing from release to
release, please address it in appropriate ways, e.g. dump the soname
from .18 to .18.1 or .19 or what is most fit.


Thanks!

Bug#812813: lsh-utils: FTBFS: dh_install: lsh-server missing files: usr/sbin/lsh-krb-checkpw

[Chris Lamb]

Source: lsh-utils
Version: 2.1-7
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

lsh-utils fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_install -a --sourcedir=debian/tmp
  dh_install: lsh-server missing files: usr/sbin/lsh-krb-checkpw
  dh_install: missing files, aborting
  debian/rules:94: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 255

  [..]

The full build log is attached.


Regards,

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


lsh-utils.2.1-7.unstable.amd64.log.txt.gz
Description: Binary data

Bug#809265: debci: FTBFS: ./test_blame.sh failed at least one test (test_passing_the_test_resets_the_blame?)

[Chris Lamb]

Hi,

   * test/test_blame.sh: Sleep for one second between process() calls, to
 ensure that timestamps in run IDs are different. (Closes: #809265)

http://anonscm.debian.org/cgit/collab-maint/debci.git/commit/?id=2bbce0782ca079073c2504dacf00058ac4e70420

Can you elaborate how that sleep ensures the ids are the different? Are they 
based on a timestamp..?


Regards,

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

Bug#812626: libfreecontact-perl: FTBFS - Parse errors: Bad plan. You planned 10 tests but ran 6.

[Andreas Tille]

Hi Gregor,

On Tue, Jan 26, 2016 at 08:31:10PM +0100, gregor herrmann wrote:
> > do you have any idea what change might have caused the failures of the
> > test suite?
> > Feel free to commit proposed changes to Debian Med Git if this might
> > simplify your workflow.
> 
> I cloned the git repo (very handy :)) and had a look, but I can't
> reproduce the test failure, not even when running them manually under
> high load.

H, I should have mentioned this: I also can not reproduce the
problem.
 
> Some observations:
>  
> > > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" 
> > > "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 
> > > 'blib/lib', 'blib/arch')" t/*.t
> > > t/01FreeContact.t .. 
> > > 1..3
> > > ok 1 - use FreeContact;
> > > ok 2 - FreeContact->can(...)
> > > ok 3 - FreeContact::Predictor->can(...)
> > > ok
> > > will use 1 OMP threads
> > > SSE2 veczweight, wchunk = 32

I get
  SSE2 veczweight, wchunk = 64
here instead (when building on amd64).

> > > total weight (variation) of alignment = 620.777515304633
> > > 
> > > seq weight loop for 1000 seqs took 0.012224 secs
> > > will use 1 OMP threads
> > > calculated column aa frequencies, gap cols = 4
> > > calculated pair frequency table in 0.192089 secs
> > > collected apc_mean[MI] = 0.174031486973761
> > > aa freq sum (cell) = 0.97158936352, pairfreq sum (cell) = 
> > > 0.94420985606
> > > formed covariance matrix (122/126,4)
> > > LU factorization took 9.17976 secs, inverted matrix (incl LUf) in 23.7932 
> > > secs
> > > density of inverse covariance matrix = 1 (cksum 346842.2)
> > > went back to gapped (126) wwi matrix
> > > collected apc_mean[l1norm] = 117.987054769839
> > > collected apc_mean[fro] = 3.35437751555787
> > > all done in 24.6311 secs
> > > will use 1 OMP threads
> > > SSE2 veczweight, wchunk = 32
> > > total weight (variation) of alignment = 561.595172234625
> > > t/02test.t . 
> > > 1..10
> > > ok 1 - use FreeContact;
> > > ok 2 - An object of class 'FreeContact::Predictor' isa 
> > > 'FreeContact::Predictor'
> > > ok 3
> > > ok 4
> > > ok 5 - precision test
> > > ok 6 - timing results test
> > > Failed 4/10 subtests
> 
> I noticed that the non-perl-test output comes before t/02test.t while
> it comes later (after the "ok 3" of t/02test.t) for me. I thought this
> might be a parallelization problem but the test was run with -j1, and
> it also passes for me with -jN.

>From my (limited) experience this kind of non-reproducible FTBFS are
often connected to parallelization.  I'm tempted to drop the --parallel
from d/rules.
 
> > > 
> > > Test Summary Report
> > > ---
> > > t/02test.t   (Wstat: 11 Tests: 6 Failed: 0)
> > >   Non-zero wait status: 11
> > >   Parse errors: Bad plan.  You planned 10 tests but ran 6.
> 
> What's this 11? A timeout?

I have no idea.
 
> Maybe related: the last passing test is "timing results test", the
> 7th test would be (line 47):
> like($@, qr/^Caught FreeContact timeout exception:/);
> 
> 
> Sorry for being not able to provide more hints; maybe someone is able
> to see what's going on here ...
> 
> 
> Since the upstream author is also in Uploaders, I'm adding a CC :)

Sensible in principle - but Laszlo left the Debian Med team as well as
his employer where he was coding this software.  May be he has some
hint anyway ...
 
Thanks for your investigations

Andreas.

-- 
http://fam-tille.de

Bug#812814: CVE-2015-7578 CVE-2015-7579 CVE-2015-7580

[Moritz Muehlenhoff]

Package: ruby-rails-html-sanitizer
Severity: grave
Tags: security

Please see
https://marc.info/?l=oss-security=145375052028672=2
https://marc.info/?l=oss-security=145375059928688=2
https://marc.info/?l=oss-security=145375090928793=2

Cheers,
Moritz

Processed: found 812814 in 1.0.2-1, tagging 812814

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 812814 1.0.2-1
Bug #812814 [ruby-rails-html-sanitizer] CVE-2015-7578 CVE-2015-7579 
CVE-2015-7580
Marked as found in versions ruby-rails-html-sanitizer/1.0.2-1.
> tags 812814 + upstream fixed-upstream
Bug #812814 [ruby-rails-html-sanitizer] CVE-2015-7578 CVE-2015-7579 
CVE-2015-7580
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#809265: debci: FTBFS: ./test_blame.sh failed at least one test (test_passing_the_test_resets_the_blame?)

[Antonio Terceiro]

On Tue, Jan 26, 2016 at 09:10:09PM +0100, Chris Lamb wrote:
> Hi,
> 
>* test/test_blame.sh: Sleep for one second between process() calls, to
>  ensure that timestamps in run IDs are different. (Closes: #809265)
> 
> http://anonscm.debian.org/cgit/collab-maint/debci.git/commit/?id=2bbce0782ca079073c2504dacf00058ac4e70420
> 
> Can you elaborate how that sleep ensures the ids are the different? Are they 
> based on a timestamp..?

yes, exactly that. the id is mmddHHMMSS


signature.asc
Description: PGP signature

Bug#810846: marked as done (dbconfig-common: /usr/share/dbconfig-common/dpkg/common: bashism)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 21:50:22 +
with message-id 
and subject line Bug#810846: fixed in dbconfig-common 2.0.1
has caused the Debian Bug report #810846,
regarding dbconfig-common: /usr/share/dbconfig-common/dpkg/common: bashism
to be marked as done.

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

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


-- 
810846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dbconfig-common
Version: 2.0.0
Severity: serious
Justification: Policy 10.4

The construct `…` for pre-POSIX style command substitutions
is unportable when double quotes are used both inside and
outside the substitution.

There has recently been an issue raised with POSIX about the
interpretation of the standard regarding this issue, as the
POSIX standard per se *is* clear on this, but the current
interpretation, which is shared by the yash developers, does not
match current shell practice. This only affects constructs like:
echo "`echo \"foo\"`"
which shows
foo
in almost all current and some historic shells, and
"foo"
in mksh’s POSIX mode, yash, and some other historic shells.

Your script relies on one interpretation of this unportability
(and the one which doesn’t match current POSIX at that):

tglase@tglase:~ $ grep -r '".*`.*".*`.*"' /usr/share/dbconfig-common
/usr/share/dbconfig-common/internal/mysql:dbc_error="mysql said: `cat 
\"$l_errfile\"`"
/usr/share/dbconfig-common/dpkg/common:mkdir -p "`dirname 
\"$dbc_packageconfig\"`"

The effect of this is that, when any package using dbconfig-common
is configured while lksh (from the mksh package) or yash is /bin/sh
a directory called ‘"’ is created under the current working directory.

The fix is trivial: use the modern and recommended (since the 1980s
or so) form of command substitution:
mkdir -p "$(dirname "$dbc_packageconfig")"

Further readings:
– GNU autoconf texinfo documentation, section *Portable Shell::
– http://austingroupbugs.net/view.php?id=1015 in which I ask
  POSIX to standardise on current practice (which would make
  your script in theory valid, but still unportable; funnily,
  since people nowadays only ever use ‘`’ to be m̲o̲r̲e̲ portable).

-- System Information:
Debian Release: stretch/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages dbconfig-common depends on:
ii  debconf [debconf-2.0]  1.5.58
ii  ucf3.0031

dbconfig-common recommends no packages.

Versions of packages dbconfig-common suggests:
pn  dbconfig-mysql | dbconfig-pgsql | dbconfig-sqlite | dbconfig-sqlite  

-- debconf information:
  dbconfig-common/mysql/method: Unix socket
* dbconfig-common/remote-questions-default: false
  dbconfig-common/pgsql/method: TCP/IP
  dbconfig-common/dbconfig-remove: true
  dbconfig-common/missing-db-package-error: abort
  dbconfig-common/db/basepath:
  dbconfig-common/pgsql/revertconf: false
  dbconfig-common/pgsql/no-user-choose-other-method:
  dbconfig-common/pgsql/authmethod-user: password
  dbconfig-common/database-type:
  dbconfig-common/pgsql/authmethod-admin: ident
  dbconfig-common/mysql/admin-user: root
  dbconfig-common/remote/newhost:
  dbconfig-common/pgsql/manualconf:
  dbconfig-common/purge: false
  dbconfig-common/db/app-user:
  dbconfig-common/internal/reconfiguring: false
  dbconfig-common/passwords-do-not-match:
  dbconfig-common/remote/port:
  dbconfig-common/remove-error: abort
  dbconfig-common/dbconfig-install: true
  dbconfig-common/upgrade-backup: true
  dbconfig-common/pgsql/changeconf: false
  dbconfig-common/pgsql/no-empty-passwords:
  dbconfig-common/dbconfig-upgrade: true
  dbconfig-common/dbconfig-reinstall: false
  dbconfig-common/install-error: abort
  dbconfig-common/pgsql/admin-user: postgres
* dbconfig-common/remember-admin-pass: true
  dbconfig-common/upgrade-error: abort
  dbconfig-common/remote/host:
  dbconfig-common/internal/skip-preseed: false
  dbconfig-common/db/dbname:
--- End Message ---
--- Begin Message ---
Source: dbconfig-common
Source-Version: 2.0.1

We believe that the bug you reported is fixed in the latest version of
dbconfig-common, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is

Bug#812733: marked as done (dfvfs: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode character u'\xed' in position 72: ordinal not in range(128))

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 21:50:41 +
with message-id 
and subject line Bug#812733: fixed in dfvfs 20160108-2
has caused the Debian Bug report #812733,
regarding dfvfs: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode 
character u'\xed' in position 72: ordinal not in range(128)
to be marked as done.

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

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


-- 
812733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dfvfs
Version: 20160108-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

dfvfs fails to build from source in unstable/amd64:

  [..]

  
  ==
  ERROR: testResolvePathWithEnvironmentVariable 
(helpers.windows_path_resolver.WindowsPathResolverTest)
  Test the resolve path function with environment variable expansion.
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160126092053.HI2fPHzkja/dfvfs-20160108/tests/helpers/windows_path_resolver.py",
 line 179, in testResolvePathWithEnvironmentVariable
  path_spec = path_resolver.ResolvePath(windows_path)
File "./dfvfs/helpers/windows_path_resolver.py", line 241, in ResolvePath
  path, expand_variables=expand_variables)
File "./dfvfs/helpers/windows_path_resolver.py", line 176, in _ResolvePath
  path_segment, case_sensitive=False)
File "./dfvfs/vfs/file_entry.py", line 317, in GetSubFileEntryByName
  for sub_file_entry in self.sub_file_entries:
File "./dfvfs/vfs/os_file_entry.py", line 228, in sub_file_entries
  for path_spec in self._directory.entries:
File "./dfvfs/vfs/file_entry.py", line 67, in entries
  for entry in self._EntriesGenerator():
File "./dfvfs/vfs/os_file_entry.py", line 45, in _EntriesGenerator
  location, directory_entry])
File "./dfvfs/vfs/os_file_system.py", line 191, in JoinPath
  segment.split(self.PATH_SEPARATOR) for segment in path_segments]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 0: 
ordinal not in range(128)
  
  ==
  ERROR: testDataStreams (vfs.tsk_file_entry.TSKFileEntryTest)
  Test the data streams functionality.
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160126092053.HI2fPHzkja/dfvfs-20160108/tests/vfs/tsk_file_entry.py",
 line 28, in setUp
  self._file_system.Open(self._tsk_path_spec)
File "./dfvfs/vfs/file_system.py", line 230, in Open
  self._Open(path_spec, mode=mode)
File "./dfvfs/vfs/tsk_file_system.py", line 64, in _Open
  path_spec.parent, resolver_context=self._resolver_context)
File "./dfvfs/resolver/resolver.py", line 113, in OpenFileObject
  file_object.open(path_spec=path_spec)
File "./dfvfs/file_io/file_io.py", line 73, in open
  self._Open(path_spec=path_spec, mode=mode)
File "./dfvfs/file_io/os_file_io.py", line 88, in _Open
  stat_info = os.stat(location)
  UnicodeEncodeError: 'ascii' codec can't encode character u'\xed' in position 
72: ordinal not in range(128)
  
  ==
  ERROR: testGetDataStream (vfs.tsk_file_entry.TSKFileEntryTest)
  Test the retrieve data streams functionality.
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160126092053.HI2fPHzkja/dfvfs-20160108/tests/vfs/tsk_file_entry.py",
 line 28, in setUp
  self._file_system.Open(self._tsk_path_spec)
File "./dfvfs/vfs/file_system.py", line 230, in Open
  self._Open(path_spec, mode=mode)
File "./dfvfs/vfs/tsk_file_system.py", line 64, in _Open
  path_spec.parent, resolver_context=self._resolver_context)
File "./dfvfs/resolver/resolver.py", line 113, in OpenFileObject
  file_object.open(path_spec=path_spec)
File "./dfvfs/file_io/file_io.py", line 73, in open
  self._Open(path_spec=path_spec, mode=mode)
File "./dfvfs/file_io/os_file_io.py", line 88, in _Open
  stat_info = os.stat(location)
  UnicodeEncodeError: 'ascii' codec can't encode character u'\xed' in position 
72: ordinal not in range(128)
  
  

Bug#812418: marked as done (libowfat-dev: Filename collision with libgd-dev)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 21:52:39 +
with message-id 
and subject line Bug#812418: fixed in libowfat 0.30-2
has caused the Debian Bug report #812418,
regarding libowfat-dev: Filename collision with libgd-dev
to be marked as done.

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

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


-- 
812418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgd-dev,libowfat-dev
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 0.30-1
Control: found -1 2.1.1-4

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package libowfat-dev.
  Preparing to unpack .../libowfat-dev_0.30-1_amd64.deb ...
  Unpacking libowfat-dev (0.30-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libowfat-dev_0.30-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/entities.h', which is also in package 
libgd-dev:amd64 2.1.1-4+b1
  Processing triggers for libc-bin (2.21-6) ...
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libowfat-dev_0.30-1_amd64.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/include/entities.h

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.


entities.h sounds like a very generic name that could be used by many
packages:
https://packages.debian.org/search?searchon=contents=entities.h=path=unstable=any
Most of them have them prefixed and/or in a subdirectory of
/usr/include.


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


libgd-dev=2.1.1-4+b1_libowfat-dev=0.30-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libowfat
Source-Version: 0.30-2

We believe that the bug you reported is fixed in the latest version of
libowfat, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 812...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roland Stigge  (supplier of updated libowfat package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 25 Jan 2016 10:35:16 +0100
Source: libowfat
Binary: libowfat0 libowfat-dev libowfat-dietlibc-dev
Architecture: source amd64
Version: 0.30-2
Distribution: unstable
Urgency: medium
Maintainer: Roland Stigge 
Changed-By: Roland Stigge 
Description:
 libowfat-dev - Reimplementation of libdjb, development files
 libowfat-dietlibc-dev - Reimplementation of libdjb, dietlibc version
 libowfat0  - Reimplementation of libdjb, shared library
Closes: 812418
Changes:
 libowfat (0.30-2) unstable; urgency=medium
 .
   * Fix /usr/include/entities.h file conflict with libgd-dev
 (Closes: #812418)
Checksums-Sha1:
 d1cb867e156421dc4cf1b1f7e4e75d58fcee0115 1854 libowfat_0.30-2.dsc
 5f0d9300895122eb152c7765e85bdc080a4aa9b8 7412 libowfat_0.30-2.debian.tar.xz
 

Bug#802949: marked as done (FTBFS on mipsel during qtbase-5-5-1 transition)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 23:02:25 +0100
with message-id <56a7ecf1.3080...@ktknet.cz>
and subject line Close the issue
has caused the Debian Bug report #802949,
regarding FTBFS on mipsel during qtbase-5-5-1 transition
to be marked as done.

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

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


-- 
802949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gammaray
Version: gammaray
Severity: serious

Hi! While rebuilding gammaray fro the qtbase 5.5.1 private headers' transition
your package failed to build from source on mipsel.

The build was trying twice, both times failing during the tests.


Kinds regards, Lisandro.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'buildd-unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

-- no debconf information
--- End Message ---
--- Begin Message ---
gammaray 2.4.0-1 now builds on mipsel, closing.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#755202: network-manager: Bug also present in Raspbian Jessie

[Jan Heitkoetter]

Package: network-manager
Version: 0.9.10.0-7
Followup-For: Bug #755202

Dear Maintainer,

It occours to me that this bug is still present in Raspbian Jessie.

I'm trying to set up eth0 with static IP.

/etc/network/interfaces:
# Please note that this file is written to be used with dhcpcd.
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'.

auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

#auto wlan0
#allow-hotplug wlan0
#iface wlan0 inet dhcp
#wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

#iface default inet dhcp


Rebooting after installing network-manager, network-manager has automatically 
created a connection 16a3... using device eth0 and DHCP:
root@himbeere2:/home/jan# nmcli c s
NAME  UUID  TYP GERÄT 
eth0  16a38f40-3cd1-4794-a7b3-e86c318546ca  802-3-ethernet  eth0  


Now editing this connection:
root@himbeere2:/home/jan# nmcli c e eth0

===| nmcli interaktiver Verbindungs-Editor |===

Bestehende Verbindung »802-3-ethernet« wird bearbeitet: »eth0«

[setting static IP etc.]

nmcli> save
Saving the connection with 'autoconnect=yes'. That might result in an immediate 
activation of the connection.
Do you still want to save? (ja/nein) [ja] 
Verbindung »eth0« (16a38f40-3cd1-4794-a7b3-e86c318546ca) erfolgreich 
aktualisiert.
nmcli> quit


Reboot and see what happens:
root@himbeere2:/home/jan# reboot

[...]

jan@himbeere2:~$ sudo nmcli c s
[sudo] password for jan: 
NAME  UUID  TYP GERÄT 
eth0  84150a4e-91b0-446d-b324-4298ff3b1d77  802-3-ethernet  eth0  
eth0  16a38f40-3cd1-4794-a7b3-e86c318546ca  802-3-ethernet  --

network-manager has created another connection 8415... claiming device eth0 and 
using DHCP. It does so after each reboot. I would expect network-manager to use 
the existing connection 16a3...


No conffile for 8415...:
jan@himbeere2:~$ ls -l /etc/NetworkManager/system-connections/
insgesamt 4
-rw--- 1 root root 267 Jan 26 22:52 eth0


Conffile for 16a3... is there (contents OK):
jan@himbeere2:~$ sudo grep uuid /etc/NetworkManager/system-connections/eth0
uuid=16a38f40-3cd1-4794-a7b3-e86c318546ca


/etc/NetworkManager/NetworkManager.conf:
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

Regards

Jan

P.S. Does nobody take care about all those spam replies?

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 8.0 (jessie)
Release:8.0
Codename:   jessie
Architecture: armv7l

Kernel: Linux 4.1.15-v7+ (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.8.20-0+deb8u1
ii  init-system-helpers1.22
ii  isc-dhcp-client4.3.1-6+deb8u2
ii  libc6  2.19-18+deb8u2
ii  libdbus-1-31.8.20-0+deb8u1
ii  libdbus-glib-1-2   0.102-1
ii  libgcrypt201.6.3-2
ii  libglib2.0-0   2.42.1-1
ii  libgnutls-deb0-28  3.3.8-6+deb8u3
ii  libgudev-1.0-0 215-17+deb8u3
ii  libmm-glib01.4.0-1
ii  libndp01.4-2
ii  libnewt0.520.52.17-1
ii  libnl-3-2003.2.24-2
ii  libnl-genl-3-200   3.2.24-2
ii  libnl-route-3-200  3.2.24-2
ii  libnm-glib40.9.10.0-7
ii  libnm-util20.9.10.0-7
ii  libpam-systemd 215-17+deb8u3
ii  libpolkit-gobject-1-0  0.105-8
ii  libreadline6   6.3-8
ii  libsoup2.4-1   2.48.0-1
ii  libsystemd0215-17+deb8u3
ii  libteamdctl0   1.12-2
ii  libuuid1   2.25.2-6
ii  lsb-base   4.1+Debian13+rpi1+nmu1
ii  policykit-10.105-8
ii  udev   215-17+deb8u3
ii  wpasupplicant  2.3-1+deb8u3

Versions of packages network-manager recommends:
ii  crda3.13-1
ii  dnsmasq-base2.72-3+deb8u1
ii  iptables1.4.21-2
ii  iputils-arping  3:20121221-5
ii  modemmanager1.4.0-1
ii  ppp 2.4.6-3.1

Versions of packages network-manager suggests:
pn  avahi-autoipd  
pn  libteam-utils  

-- no debconf information

Processed: severity 787959

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 787959 important
Bug #787959 [backintime-common] [backintime-common] backintime failed to start: 
No such file or directory
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
787959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#812814: marked as done (CVE-2015-7578 CVE-2015-7579 CVE-2015-7580)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jan 2016 22:43:15 +
with message-id 
and subject line Bug#812814: fixed in ruby-rails-html-sanitizer 1.0.3-1
has caused the Debian Bug report #812814,
regarding CVE-2015-7578 CVE-2015-7579 CVE-2015-7580
to be marked as done.

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

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


-- 
812814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-rails-html-sanitizer
Severity: grave
Tags: security

Please see
https://marc.info/?l=oss-security=145375052028672=2
https://marc.info/?l=oss-security=145375059928688=2
https://marc.info/?l=oss-security=145375090928793=2

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: ruby-rails-html-sanitizer
Source-Version: 1.0.3-1

We believe that the bug you reported is fixed in the latest version of
ruby-rails-html-sanitizer, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 812...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated 
ruby-rails-html-sanitizer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 26 Jan 2016 19:36:51 -0200
Source: ruby-rails-html-sanitizer
Binary: ruby-rails-html-sanitizer
Architecture: source
Version: 1.0.3-1
Distribution: unstable
Urgency: high
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 ruby-rails-html-sanitizer - HTML sanitization for Rails applications
Closes: 812814
Changes:
 ruby-rails-html-sanitizer (1.0.3-1) unstable; urgency=high
 .
   * New upstream release. Contains fixes for several XSS vulnerabilities:
 CVE-2015-7578 CVE-2015-7579 CVE-2015-7580 (Closes: #812814)
   * debian/ruby-tests.rake: re-enable test that was disabled
   * 0001-Skip-some-tests-under-Debian.patch: skip tests where the sanitized
 HTML is XSS-free but does not match the exact content expected by the
 upstream test suite. I suspect that is due to Nokogiri not using its own
 patched version of libxml2 in Debian, but can't be sure of that yet.
 Also, the same tests would already fail on 1.0.2 if enabled.
Checksums-Sha1:
 f4c7470cc9b1c3d1d824d51e5bdaf954dc3db0b5 2254 
ruby-rails-html-sanitizer_1.0.3-1.dsc
 19cf3baa8925c5314d84c207dcc473a409fb3bae 12012 
ruby-rails-html-sanitizer_1.0.3.orig.tar.gz
 5620823ad032f94399a4cdfa38ab2721faacbcda 3244 
ruby-rails-html-sanitizer_1.0.3-1.debian.tar.xz
Checksums-Sha256:
 2ef86a8ee84d0ccf7b19d524d3fea04693499b2d1b314af26a3f651954e522ee 2254 
ruby-rails-html-sanitizer_1.0.3-1.dsc
 5727cbb975fcf8ccf18a7dee5e3db45dfe15a416f5468009bd33252c3bf490f7 12012 
ruby-rails-html-sanitizer_1.0.3.orig.tar.gz
 4ab79e55188505e1ae79649678a4f508d7ab2f41c96e0c2c0df6526ef509635d 3244 
ruby-rails-html-sanitizer_1.0.3-1.debian.tar.xz
Files:
 d9e1a8212febb62d718d0b7910f02b89 2254 ruby optional 
ruby-rails-html-sanitizer_1.0.3-1.dsc
 39f76abfdc72aeafcc3593347f1bf571 12012 ruby optional 
ruby-rails-html-sanitizer_1.0.3.orig.tar.gz
 ad1db8aa4316d19d22e51d1ac723ebf2 3244 ruby optional 
ruby-rails-html-sanitizer_1.0.3-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWp+ytAAoJEPwNsbvNRgvejXAQAJcTNL58wzHmzcdPkzcx0oNl
DW1AvH/qgJ5OquHBHZOwX71gYMsQKUybTgKrgJOl59tNIcwTLfDFis2m1RgNoLkf
8Cnypy4XzO75bOE2s4Fjchu1kHfAVFXah2N88dtytAfT4Fk/tLqt1NRgt17+KZGP
KZJLZJAb9aiv/Dtgek4ujPgYEQ/ZIifgsiG75WjP2Jc76W4Qh8bqHdvASCR2ta5h
Ze4QQcllfN+3yDT4VWzukC+xS4uA3IRchDWNpzXqPKtSPnTow9zQxHrMRpOWPbtY
rERgumkX/ra32FDNJUyWBJkl3Ow2MYb31L0qmTdnUX+4U8osCPCZTAX2+WPyO/IW
/2UTO/tIO3+xBk8GZa5YLX+mPsWLHYUdEQo/B3R2ByTqfp0z41kiSLfD1JwDhaGw
RHXKYDPDKJLcZZxDPzjMFpbxZqD8XxmUQJt1Jy0Cky57+YKP9PoZjZYyxA05YKJO
C7vog7Erg7Uj/0s9hYjohy37yjSo/7zOpFE5llG4+MZRY16+x//Nqg8pxJeMRMn1
atuVMCPzsimNqq7yYrRRqiRyBlJq2/QsH9HwyxJ1mQPYdV6VB/AI2vqPxT2b5V+/
qyiA2NnmN+plLC+2GAS2tqj+Ff3Vs+sXiwmgOcRsuTQr/X/9hTfAPjSw494BckpX
0L+memNUc/CmEYjZaZnp
=BQFA
-END PGP SIGNATURE End Message ---

Bug#812818: should dipy be removeed from debian?

[Mattia Rizzolo]

Source: dipy
Severity: serious


Dear dipy maintainer,
I know this may sound a bit harsh and premature, but I'm concerned by
the state of dipy in Debian.
The package is currently uninstallable due to the removal of a
dependency (that has been deprecated for 5 years now), and  it's
unbuildable since more than 6 months (and the maintainers are aware of
it, as you can see in #785991#12).
A new upstream release since more or less that time.

From my restricted point of view there is no activity around it (I at
least se no changes in the public VCS).

As of now there are 2 RC bugs, the package is not in testing, there are
no reverse (build-)dependencies and the the popcon is resonably low.

Please, can you consider maintaining the package?  Keeping an unusable
thing in the archive is not going to help our users in any way.


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#812819: should pystatgrab be removed from Debian?

[Mattia Rizzolo]

Source: pystatgrab
Severity: serious


Dear maintainer,

I know this may sound a bit harsh, but I'm concerned by the state of
pystatgrab in Debian.
The package is currently uninstallable due to the removal of a
dependency (that has been deprecated for 5 years now), and  it's
unbuildable since more than 2 years!!

The last upload of this package happened early in 2012, so it's nearly 4
years ago.
There is also a new upstream release out.

pystatgrab missed the last Debian stable release (jessie), and since
then it never came back into testing.
Currently there are 2 open RC bugs, and a kinda low popcon.

Please, can you consider maintaining the package?  Keeping an unusable
thing in the archive is not going to help our users in any way.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature