Bug#837629: marked as done (u-boot 2016.09~rc2+dfsg1-1 bricks my openrd ultimate)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2016 05:50:41 +
with message-id 
and subject line Bug#837629: fixed in u-boot 2016.09+dfsg1-2
has caused the Debian Bug report #837629,
regarding u-boot 2016.09~rc2+dfsg1-1 bricks my openrd ultimate
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.)


-- 
837629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: u-boot
Version: 2016.09~rc2+dfsg1-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
As requested by Vagrant I'm testing u-boot 2016.09~rc2+dfsg1-1 on my OpenRD 
Ultimate machine.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I followed the instructions for upgrading u-boot on Martin's web page at
 https://www.cyrius.com/debian/kirkwood/openrd/uboot-upgrade/
   * What was the outcome of this action?
After telling u-boot to "reset", the machine went dead.  There was no output on 
the serial console, no answer to ping ... nothing.
   * What outcome did you expect instead?
I expected it to reset and reboot.  But it didn't do that.

*** End of the template - remove these template lines ***

I unbricked it follwing the instructions at
https://www.newit.co.uk/forum/index.php?topic=2835.0
and I'm writing this bugreport on it.  It boots using
U-Boot 2016.03+dfsg1-3 (Apr 04 2016 - 18:23:06 +)

Please advise what I can do to help debug this.


-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (900, 'stable-updates'), (900, 'testing'), (900, 'stable'), (50, 
'unstable')
Architecture: armel (armv5tel)

Kernel: Linux 4.6.0-1-marvell
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: u-boot
Source-Version: 2016.09+dfsg1-2

We believe that the bug you reported is fixed in the latest version of
u-boot, 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 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated u-boot 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: Sun, 23 Oct 2016 19:36:36 -0700
Source: u-boot
Binary: u-boot u-boot-imx u-boot-qcom u-boot-tegra u-boot-omap u-boot-sunxi 
u-boot-exynos u-boot-rockchip u-boot-rpi u-boot-tools
Architecture: source
Version: 2016.09+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian 
Changed-By: Vagrant Cascadian 
Description:
 u-boot - A boot loader for embedded systems
 u-boot-exynos - A boot loader for exynos systems
 u-boot-imx - A boot loader for imx systems
 u-boot-omap - A boot loader for omap systems
 u-boot-qcom - A boot loader for qcom systems
 u-boot-rockchip - A boot loader for rockchip systems
 u-boot-rpi - A boot loader for Raspberry PI systems
 u-boot-sunxi - A boot loader for sunxi systems
 u-boot-tegra - A boot loader for NVIDIA Tegra systems
 u-boot-tools - companion tools for Das U-Boot bootloader
Closes: 837629 841351
Changes:
 u-boot (2016.09+dfsg1-2) unstable; urgency=medium
 .
   * odroid-xu3: Add patch to use the default bootdelay from
 distro_bootcmd.
   * Remove Philip Rinn from Cubieboard2 testers.
   * u-boot-rpi: Add documentation for configuring raspberry pi to use
 u-boot.
   * debian/watch: Add signature checking of upstream tarball.
   * u-boot-tools: Add device-tree-compiler to Recommends. Thanks to
 Pierre-Hugues Husson.  (Closes: #841351).
   * Apply patches from v2016.09.01:
 - 0001-Revert-Increase-default-of-CONFIG_SYS_MALLOC_F_LEN-f.patch
 - 0002-Revert-image-fit-switch-ENOLINK-to-ENOENT.patch
   * Remove openrd targets, as they do not boot (Closes: #837629).
Checksums-Sha1:
 262612f012864c641f1fe76021c0a65264d507ce 2660 u-boot_2016.09+dfsg1-2.dsc
 2ea9d5c60d0ae1d3406104b632d661ad42d4aa04 36572 

Bug#812303: synergy: diff for NMU version 1.4.16-1.1

[Joshua Honeycutt]

Control: tags 812303 + patch
Control: tags 812303 + pending

Dear maintainer,

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

Regards.
diff -Nru synergy-1.4.16/debian/changelog synergy-1.4.16/debian/changelog
--- synergy-1.4.16/debian/changelog	2014-03-16 17:58:42.0 -0500
+++ synergy-1.4.16/debian/changelog	2016-10-23 23:54:38.0 -0500
@@ -1,3 +1,11 @@
+synergy (1.4.16-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Added debian_google-test.patch to build against Debian's
+google-mock and libgtest-dev packages. Closes: #812303
+
+ -- Joshua Honeycutt   Sun, 23 Oct 2016 23:36:22 -0500
+
 synergy (1.4.16-1) unstable; urgency=low
 
   * New upstream version.
diff -Nru synergy-1.4.16/debian/control synergy-1.4.16/debian/control
--- synergy-1.4.16/debian/control	2014-03-16 12:10:31.0 -0500
+++ synergy-1.4.16/debian/control	2016-10-24 00:06:26.0 -0500
@@ -5,7 +5,7 @@
 Homepage: http://synergy-foss.org/
 Vcs-Git: http://git.licquia.org/raw/synergy-debian.git
 Vcs-Browser: http://git.licquia.org/?p=synergy-debian.git;a=summary
-Build-Depends: debhelper (>= 7), libxt-dev, libxtst-dev, libxinerama-dev, cmake, docbook-utils, libcrypto++-dev, pkg-config, libqt4-dev, libcurl4-gnutls-dev | libcurl-dev
+Build-Depends: debhelper (>= 7), libxt-dev, libxtst-dev, libxinerama-dev, cmake, docbook-utils, libcrypto++-dev, pkg-config, libqt4-dev, libcurl4-gnutls-dev | libcurl-dev, google-mock, libgtest-dev
 Standards-Version: 3.9.5
 
 Package: synergy
diff -Nru synergy-1.4.16/debian/patches/debian_google-test.patch synergy-1.4.16/debian/patches/debian_google-test.patch
--- synergy-1.4.16/debian/patches/debian_google-test.patch	1969-12-31 18:00:00.0 -0600
+++ synergy-1.4.16/debian/patches/debian_google-test.patch	2016-10-23 23:55:18.0 -0500
@@ -0,0 +1,48 @@
+Description: Builds against Debian packaged google-mock
+ and libgtest-dev
+Author: Joshua Honeycutt 
+Forwarded: not-needed
+Last-Update: 2016-10-23
+
+--- a/src/test/CMakeLists.txt
 b/src/test/CMakeLists.txt
+@@ -15,13 +15,11 @@
+ # along with this program.  If not, see .
+ 
+ include_directories(
+-	../../tools/gtest-1.6.0
+-	../../tools/gtest-1.6.0/include
+-	../../tools/gmock-1.6.0
+-	../../tools/gmock-1.6.0/include)
++	/usr/src/gtest
++	/usr/src/gmock)
+ 	
+-add_library(gtest STATIC ../../tools/gtest-1.6.0/src/gtest-all.cc)
+-add_library(gmock STATIC ../../tools/gmock-1.6.0/src/gmock-all.cc)
++add_library(gtest STATIC /usr/src/gtest/src/gtest-all.cc)
++add_library(gmock STATIC /usr/src/gmock/src/gmock-all.cc)
+ 
+ add_subdirectory(integtests)
+ add_subdirectory(unittests)
+--- a/src/test/integtests/CMakeLists.txt
 b/src/test/integtests/CMakeLists.txt
+@@ -72,8 +72,6 @@
+ 	../../lib/synergy
+ 	../../lib/synwinhk
+ 	../../lib/synwinxt
+-	../../../tools/gtest-1.6.0/include
+-	../../../tools/gmock-1.6.0/include
+ 	../unittests
+ )
+ 
+--- a/src/test/unittests/CMakeLists.txt
 b/src/test/unittests/CMakeLists.txt
+@@ -49,8 +49,6 @@
+ 	../../lib/net
+ 	../../lib/platform
+ 	../../lib/synergy
+-	../../../tools/gtest-1.6.0/include
+-	../../../tools/gmock-1.6.0/include
+ 	../../../tools
+ 	io
+ 	synergy
diff -Nru synergy-1.4.16/debian/patches/series synergy-1.4.16/debian/patches/series
--- synergy-1.4.16/debian/patches/series	2014-03-16 15:13:23.0 -0500
+++ synergy-1.4.16/debian/patches/series	2016-10-23 23:18:36.0 -0500
@@ -1,3 +1,4 @@
+debian_google-test.patch
 system-cryptopp.patch
 cprotocolutil-writef.patch
 versioncheck-disable.patch

Processed: synergy: diff for NMU version 1.4.16-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 812303 + patch
Bug #812303 [synergy] synergy: FTBFS with GCC 6: test suite segfaults
Added tag(s) patch.
> tags 812303 + pending
Bug #812303 [synergy] synergy: FTBFS with GCC 6: test suite segfaults
Added tag(s) pending.

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

Bug#841532: libgit2: FTBFS under some timezones (eg. GMT-14)

[Chris Lamb]

Hi Russell,

> I think that preventing random failures from Debian build infrastructure
> is the best I can do for the time being

Well, not if the upstream library code itself is broken wrt to the timezones
and its not just some peculiarity of the test. In fact, if the code is broken
then breaking in Debian is actually "correct", from a funny point of view.

Anyway, worth checking with upstream before patching over the issue within
Debian just in case they never respond and this (potentially) falls through
the gaps IMHO. :)


Regards,

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

Bug#837854: marked as done (jana: FTBFS due to undeclared build dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2016 05:18:35 +
with message-id 
and subject line Bug#837854: fixed in jana 0.0.0+git20091215.9ec1da8a-4
has caused the Debian Bug report #837854,
regarding jana: FTBFS due to undeclared build dependencies
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.)


-- 
837854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jana
Version: 0.0.0+git20091215.9ec1da8a-3
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk-doc-tools

Hi,

your package jana declares a build dependency on gtk-doc-tools.
gtk-doc-tools in turn depends on gnome-common, which in turn pulls in packages
like gettext, intltool or pkg-config.

The dependency on gnome-common was originally added for the GNOME_GTKDOC_CHECK
macro which has been deprecated and replaced by GTK_DOC_CHECK a long time ago.

As gnome-common has been declared deprecated by GNOME upstream [1], we would
like to drop this dependency from gtk-doc-tools.

We did a test of all reverse build dependencies of gtk-doc-tools and jana
failed to build due to now missing build dependencies which are no longer
pulled in by gtk-doc-tools.

A complete build log is available at
https://people.debian.org/~biebl/gtk-doc-tools/jana.log

We have uploaded that gtk-doc-tools package as 1.25-4 to experimental as well,
so you can test your package against this version.

Common build-failures and their fixes:

a/ configure.ac:32: error: possibly undefined macro: AC_PROG_INTLTOOL

   make[1]: intltoolize: Command not found

   → Build-Depends: intltool

b/ ./configure: line 5461: syntax error near unexpected token `yes'
   ./configure: line 5461: `GNOME_COMPILE_WARNINGS(yes)'

   ./configure: line 14801: GNOME_CODE_COVERAGE: command not found

   → Build-Depends: gnome-common (for GNOME_* macros)

c/ ./configure: line 17439: syntax error near unexpected token 
`$WARN_CFLAGS_EXTRA,'
   ./configure: line 17439: `AX_APPEND_COMPILE_FLAGS($WARN_CFLAGS_EXTRA, 
WARN_CFLAGS)'

   ./configure: line 2629: syntax error near unexpected token `git-directory'
   ./configure: line 2629: `AX_IS_RELEASE(git-directory)'

   → Build-Depends: autoconf-archive (for AX_* macros)

d/ ./configure: line 12518: intltool-update: command not found
   checking for intltool >= 0.40.0...  found
   ./configure: error: Your intltool is too old.  You need intltool 0.40.0 or 
later.

   → Build-Depends: intltool

e/ make[1]: intltoolize: Command not found

   → Build-Depends: intltool

f/ ./autogen.sh calls gnome-autogen.sh

   → Build-Depends: gnome-common


Please add the required build-dependencies to your package so once we upload
gtk-doc-tools_1.25-4 to unstable your package doesn't FTBFS.

Regards,
Michael


[1] https://wiki.gnome.org/Projects/GnomeCommon/Migration
--- End Message ---
--- Begin Message ---
Source: jana
Source-Version: 0.0.0+git20091215.9ec1da8a-4

We believe that the bug you reported is fixed in the latest version of
jana, 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 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated jana 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: Mon, 24 Oct 2016 11:52:53 +0800
Source: jana
Binary: libjana0 libjana-dev libjana-doc libjana0-dbg libjana-ecal0 
libjana-ecal-dev libjana-ecal-doc libjana-gtk0 libjana-gtk-dev libjana-gtk-doc 
libjana-test libjana-examples
Architecture: source amd64 all
Version: 0.0.0+git20091215.9ec1da8a-4
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 libjana-dev - interface library for time-related personal information (dev. fil
 libjana-doc - interface library for time-related personal information (document
 libjana-ecal-dev - implementation of libjana based on evolution-data-server 
(dev. fi
 libjana-ecal-doc - implementation of libjana based on evolution-data-server 
(documen
 

Bug#841879: freetennis: FTBFS: libasmrun.a(backtrace.o): relocation R_X86_64_32 against symbol `caml_backtrace_last_exn' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld:

[Chris Lamb]

Source: freetennis
Version: 0.4.8-10
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,

freetennis fails to build from source in unstable/amd64:

  […]

  Setting up x11proto-xext-dev (7.3.0-1) ...
  Setting up libfreetype6-dev (2.6.3-3+b1) ...
  Setting up libice-dev:amd64 (2:1.0.9-1+b1) ...
  Setting up aspell-en (2016.06.26-0-0.1) ...
  Setting up libxcomposite1:amd64 (1:0.4.4-1) ...
  Setting up libxcb-shm0:amd64 (1.12-1) ...
  Setting up libxt6:amd64 (1:1.1.5-1) ...
  Setting up libxcb-shape0:amd64 (1.12-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libxcb1-dev:amd64 (1.12-1) ...
  Setting up libxcb-glx0-dev:amd64 (1.12-1) ...
  Setting up libavahi-client3:amd64 (0.6.32-1) ...
  Setting up libx11-dev:amd64 (2:1.6.3-1) ...
  Setting up libxft2:amd64 (2.3.2-1) ...
  Setting up libharfbuzz-dev:amd64 (1.2.7-1+b1) ...
  Setting up libxcb-sync-dev:amd64 (1.12-1) ...
  Setting up fontconfig (2.11.0-6.7) ...
  Regenerating fonts cache... done.
  Setting up libcups2:amd64 (2.2.1-1) ...
  Setting up libfontconfig1-dev:amd64 (2.11.0-6.7) ...
  Setting up libenchant1c2a:amd64 (1.6.0-11+b1) ...
  Setting up libx11-xcb-dev:amd64 (2:1.6.3-1) ...
  Setting up libsm-dev:amd64 (2:1.2.2-1+b1) ...
  Setting up mesa-common-dev:amd64 (12.0.3-2) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxfixes3:amd64 (1:5.0.2-1) ...
  Setting up libxmu-headers (2:1.1.2-2) ...
  Setting up libxss1:amd64 (1:1.2.2-1) ...
  Setting up x11proto-fixes-dev (1:5.0-2) ...
  Setting up libgdk-pixbuf2.0-0:amd64 (2.36.0-1) ...
  Setting up libxcb-shm0-dev:amd64 (1.12-1) ...
  Setting up gir1.2-gdkpixbuf-2.0:amd64 (2.36.0-1) ...
  Setting up libxrender-dev:amd64 (1:0.9.9-2) ...
  Setting up libxmu6:amd64 (2:1.1.2-2) ...
  Setting up libxcb-dri2-0-dev:amd64 (1.12-1) ...
  Setting up libxcb-render0-dev:amd64 (1.12-1) ...
  Setting up x11proto-damage-dev (1:1.2.1-2) ...
  Setting up libxft-dev (2.3.2-1) ...
  Setting up gtk-update-icon-cache (3.22.1-1) ...
  Setting up libgdk-pixbuf2.0-dev (2.36.0-1) ...
  Setting up libxcb-dri3-dev:amd64 (1.12-1) ...
  Setting up libxcursor1:amd64 (1:1.1.14-1+b1) ...
  Setting up libtk8.5:amd64 (8.5.19-1) ...
  Setting up libxext-dev:amd64 (2:1.3.3-1) ...
  Setting up libpango-1.0-0:amd64 (1.40.3-2) ...
  Setting up libxcb-shape0-dev:amd64 (1.12-1) ...
  Setting up libxxf86vm1:amd64 (1:1.1.4-1) ...
  Setting up libenchant-dev (1.6.0-11+b1) ...
  Setting up libxxf86vm-dev:amd64 (1:1.1.4-1) ...
  Setting up libxfixes-dev:amd64 (1:5.0.2-1) ...
  Setting up x11proto-composite-dev (1:0.4.2-2) ...
  Setting up libxrandr2:amd64 (2:1.5.0-1) ...
  Setting up tk8.5 (8.5.19-1) ...
  Setting up libxi6:amd64 (2:1.7.6-1) ...
  Setting up libcairo2:amd64 (1.14.6-1+b1) ...
  Setting up libxinerama1:amd64 (2:1.1.3-1+b1) ...
  Setting up libxcursor-dev:amd64 (1:1.1.14-1+b1) ...
  Setting up libxcb-randr0-dev:amd64 (1.12-1) ...
  Setting up libxt-dev:amd64 (1:1.1.5-1) ...
  Setting up libxdamage1:amd64 (1:1.1.4-2+b1) ...
  Setting up libxrandr-dev:amd64 (2:1.5.0-1) ...
  Setting up libxcomposite-dev (1:0.4.4-1) ...
  Setting up libxmu-dev:amd64 (2:1.1.2-2) ...
  Setting up libcairo-script-interpreter2:amd64 (1.14.6-1+b1) ...
  Setting up libxcb-xfixes0-dev:amd64 (1.12-1) ...
  Setting up libtk8.6:amd64 (8.6.6-1) ...
  Setting up libcairo-gobject2:amd64 (1.14.6-1+b1) ...
  Setting up libxdamage-dev:amd64 (1:1.1.4-2+b1) ...
  Setting up libxss-dev:amd64 (1:1.2.2-1) ...
  Setting up libxtst6:amd64 (2:1.2.2-1+b1) ...
  Setting up libpangoft2-1.0-0:amd64 (1.40.3-2) ...
  Setting up libgl1-mesa-glx:amd64 (12.0.3-2) ...
  Setting up tk8.5-dev:amd64 (8.5.19-1) ...
  Setting up libxinerama-dev:amd64 (2:1.1.3-1+b1) ...
  Setting up libglu1-mesa:amd64 (9.0.0-2.1) ...
  Setting up libxcb-present-dev:amd64 (1.12-1) ...
  Setting up libxi-dev (2:1.7.6-1) ...
  Setting up liblabltk-ocaml (8.06.0+dfsg-3) ...
  Setting up freeglut3:amd64 (2.8.1-3) ...
  Setting up libcairo2-dev (1.14.6-1+b1) ...
  Setting up gir1.2-freedesktop:amd64 (1.50.0-1) ...
  Setting up liblablgl-ocaml (1:1.05-2) ...
  Setting up libpangoxft-1.0-0:amd64 (1.40.3-2) ...
  Setting up libpangocairo-1.0-0:amd64 (1.40.3-2) ...
  Setting up libpulse0:amd64 (9.0-4) ...
  Setting up gir1.2-pango-1.0:amd64 (1.40.3-2) ...
  Setting up libgl1-mesa-dev:amd64 (12.0.3-2) ...
  Setting up libpango1.0-dev (1.40.3-2) ...
  Setting up libfluidsynth1:amd64 (1.1.6-3+b1) ...
  Setting up libglu1-mesa-dev:amd64 (9.0.0-2.1) ...
  Setting up libpulse-mainloop-glib0:amd64 (9.0-4) ...
  Setting up libpulse-dev:amd64 (9.0-4) ...
  Setting up librsvg2-2:amd64 (2.40.16-1) ...
  Setting up libsdl1.2debian:amd64 (1.2.15+dfsg1-4) ...
  Setting up librsvg2-common:amd64 (2.40.16-1) ...
  Setting up libmikmod3:amd64 (3.3.10-1) ...
  Setting up libsdl-ttf2.0-0:amd64 (2.0.11-3+b1) ...
  Setting up libsdl1.2-dev (1.2.15+dfsg1-4) 

Bug#841880: virt-top: FTBFS: libasmrun.a(backtrace.o): relocation R_X86_64_32 against symbol `caml_backtrace_last_exn' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: fi

[Chris Lamb]

Source: virt-top
Version: 1.0.7-1.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,

virt-top fails to build from source in unstable/amd64:

  […]

  Unpacking libvirt-ocaml-dev (0.6.1.2-1+b2) ...
  Selecting previously unselected package libcurses-ocaml.
  Preparing to unpack .../24-libcurses-ocaml_1.0.3-2+b2_amd64.deb ...
  Unpacking libcurses-ocaml (1.0.3-2+b2) ...
  Selecting previously unselected package libncursesw5-dev:amd64.
  Preparing to unpack .../25-libncursesw5-dev_6.0+20160917-1_amd64.deb ...
  Unpacking libncursesw5-dev:amd64 (6.0+20160917-1) ...
  Selecting previously unselected package libcurses-ocaml-dev.
  Preparing to unpack .../26-libcurses-ocaml-dev_1.0.3-2+b2_amd64.deb ...
  Unpacking libcurses-ocaml-dev (1.0.3-2+b2) ...
  Selecting previously unselected package libcsv-ocaml-dev.
  Preparing to unpack .../27-libcsv-ocaml-dev_1.5-1_amd64.deb ...
  Unpacking libcsv-ocaml-dev (1.5-1) ...
  Selecting previously unselected package libcamomile-ocaml-data.
  Preparing to unpack .../28-libcamomile-ocaml-data_0.8.4-4_all.deb ...
  Unpacking libcamomile-ocaml-data (0.8.4-4) ...
  Selecting previously unselected package libcamomile-ocaml-dev.
  Preparing to unpack .../29-libcamomile-ocaml-dev_0.8.4-4+b1_amd64.deb ...
  Unpacking libcamomile-ocaml-dev (0.8.4-4+b1) ...
  Selecting previously unselected package libfileutils-ocaml-dev.
  Preparing to unpack .../30-libfileutils-ocaml-dev_0.4.5-4+b1_amd64.deb ...
  Unpacking libfileutils-ocaml-dev (0.4.5-4+b1) ...
  Selecting previously unselected package libgettext-ocaml.
  Preparing to unpack .../31-libgettext-ocaml_0.3.5-2+b1_amd64.deb ...
  Unpacking libgettext-ocaml (0.3.5-2+b1) ...
  Selecting previously unselected package libcamlp4-ocaml-dev.
  Preparing to unpack .../32-libcamlp4-ocaml-dev_4.02.1+3-2_amd64.deb ...
  Unpacking libcamlp4-ocaml-dev (4.02.1+3-2) ...
  Selecting previously unselected package libgettext-ocaml-dev.
  Preparing to unpack .../33-libgettext-ocaml-dev_0.3.5-2+b1_amd64.deb ...
  Unpacking libgettext-ocaml-dev (0.3.5-2+b1) ...
  Selecting previously unselected package libxml-light-ocaml.
  Preparing to unpack .../34-libxml-light-ocaml_2.2-17+b1_amd64.deb ...
  Unpacking libxml-light-ocaml (2.2-17+b1) ...
  Selecting previously unselected package libxml-light-ocaml-dev.
  Preparing to unpack .../35-libxml-light-ocaml-dev_2.2-17+b1_amd64.deb ...
  Unpacking libxml-light-ocaml-dev (2.2-17+b1) ...
  Selecting previously unselected package dh-ocaml.
  Preparing to unpack .../36-dh-ocaml_1.0.10_all.deb ...
  Unpacking dh-ocaml (1.0.10) ...
  Selecting previously unselected package libextlib-ocaml.
  Preparing to unpack .../37-libextlib-ocaml_1.7.0-2+b1_amd64.deb ...
  Unpacking libextlib-ocaml (1.7.0-2+b1) ...
  Selecting previously unselected package libextlib-ocaml-dev.
  Preparing to unpack .../38-libextlib-ocaml-dev_1.7.0-2+b1_amd64.deb ...
  Unpacking libextlib-ocaml-dev (1.7.0-2+b1) ...
  Setting up cdbs (0.4.148) ...
  Setting up libcamomile-ocaml-data (0.8.4-4) ...
  Setting up libnuma1:amd64 (2.0.11-1) ...
  Setting up ocaml-base-nox (4.02.3-7) ...
  Setting up libtinfo-dev:amd64 (6.0+20160917-1) ...
  Setting up libxenstore3.0:amd64 (4.6.0-1+nmu2) ...
  Setting up dh-ocaml (1.0.10) ...
  Setting up libncurses5-dev:amd64 (6.0+20160917-1) ...
  Setting up libyajl2:amd64 (2.1.0-2) ...
  Processing triggers for libc-bin (2.24-5) ...
  Setting up libncursesw5-dev:amd64 (6.0+20160917-1) ...
  Setting up libxen-4.6:amd64 (4.6.0-1+nmu2) ...
  Setting up libxml-light-ocaml (2.2-17+b1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libextlib-ocaml (1.7.0-2+b1) ...
  Setting up libnl-3-200:amd64 (3.2.27-1) ...
  Setting up libfindlib-ocaml (1.6.2-1) ...
  Setting up ocaml-findlib (1.6.2-1) ...
  Setting up libdbus-1-3:amd64 (1.10.12-1) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libgettext-ocaml (0.3.5-2+b1) ...
  Setting up libcurses-ocaml (1.0.3-2+b2) ...
  Setting up libnl-route-3-200:amd64 (3.2.27-1) ...
  Setting up libxen-dev (4.6.0-1+nmu2) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libavahi-client3:amd64 (0.6.32-1) ...
  Setting up libvirt0 (2.3.0-3) ...
  Setting up libvirt-dev (2.3.0-3) ...
  Setting up libvirt-ocaml (0.6.1.2-1+b2) ...
  Setting up ocaml-compiler-libs (4.02.3-7) ...
  Setting up ocaml-interp (4.02.3-7) ...
  Setting up ocaml-nox (4.02.3-7) ...
  Setting up libxml-light-ocaml-dev (2.2-17+b1) ...
  Setting up libcamomile-ocaml-dev (0.8.4-4+b1) ...
  Setting up libcsv-ocaml-dev (1.5-1) ...
  Setting up libcurses-ocaml-dev (1.0.3-2+b2) ...
  Setting up libvirt-ocaml-dev (0.6.1.2-1+b2) ...
  Setting up libextlib-ocaml-dev (1.7.0-2+b1) ...
  Setting up libcamlp4-ocaml-dev (4.02.1+3-2) ...
  Setting up libfileutils-ocaml-dev (0.4.5-4+b1) ...
  Setting up libgettext-ocaml-dev (0.3.5-2+b1) 

Bug#841867: marked as done (dgit cannot cope with some patches because it uses gbp-pq)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2016 05:07:35 +
with message-id 
and subject line Bug#841867: fixed in dgit 2.7
has caused the Debian Bug report #841867,
regarding dgit cannot cope with some patches because it uses gbp-pq
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.)


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

gbp pq cannot cope with all patches that dpkg-source can, because it
uses git-apply and git-apply is not very compatible.

At the moment, this means that `dgit clone glibc' fails:

  gbp:error: Failed to apply
  
'/home/ian/junk/d/glibc/.git/dgit/unpack/glibc-2.19/debian/patches/any/submitted-nl_langinfo-static.diff':
  Error running git apply: error: dev/null: does not exist in index

I think I need to switch to using repeated dpkg-source --before-build.
This means I need to reimplement gbp pq's metadata processing
algorithm :-/.

Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 2.7

We believe that the bug you reported is fixed in the latest version of
dgit, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated dgit 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, 24 Oct 2016 02:37:28 +0100
Source: dgit
Binary: dgit dgit-infrastructure
Architecture: all source
Version: 2.7
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Closes: 841867
Description: 
 dgit   - git interoperability with the Debian archive
 dgit-infrastructure - dgit server backend infrastructure
Changes:
 dgit (2.7) unstable; urgency=medium
 .
   Absurd bugfix for serious bug:
   * Work around `git-apply' problems (eg #841865, #829067) exposed by
 `gbp pq import' (#841866) by sometimes falling back to an emulation of
 git-apply in terms of dpkg-source --before-build.  Closes:#841867.
 .
   Minor changes:
   * dgit(1): Reorder the options, moving more important ones earlier.
   * dgit(1): Some more info about --deliberately.
   * Provide various --force-something options.  Please don't use them.
Checksums-Sha1: 
 e6cec952f40933131cf795537cd33fbf3db31e10 1340 dgit_2.7.dsc
 75cc60bc271e02bc6687a0312522762c1783c790 353016 dgit_2.7.tar.gz
 167a11e6426966ea062eb08481c8edce10bd9b5d 40560 dgit-infrastructure_2.7_all.deb
 c761a5fee048d64ee15d2d7f0524b4c6951125cc 88164 dgit_2.7_all.deb
Checksums-Sha256: 
 a2c22ed7a70325397bb45da3f186e8be07d5fadc1d367f55c7bb45cc8752074d 1340 
dgit_2.7.dsc
 91d86cd92ccba350951ae04916cc0f689fbab6ecedb755a5ebe472c33b2a6f22 353016 
dgit_2.7.tar.gz
 ab4a927b8f78a6f376f758a114d9b7917f4e362251305849805393432480abb6 40560 
dgit-infrastructure_2.7_all.deb
 8e01bb3c1b5fc96ab2aaf4eacda41589a47f35e5f5d05de638bef234c5c0cd0c 88164 
dgit_2.7_all.deb
Files: 
 c63ae7be1b05a2704b9ffe1ea07932e5 1340 devel optional dgit_2.7.dsc
 3ad889bfee6bc8688343a9a37bfabf46 353016 devel optional dgit_2.7.tar.gz
 c75dffc82e036f2f4e321ec082adba4f 40560 devel extra 
dgit-infrastructure_2.7_all.deb
 68e7562b935ed6b034715d699c8583cf 88164 devel optional dgit_2.7_all.deb

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJYDWY4AAoJEOPjOSNItQ05NXgIAJMv4XbY4HtgOQQePACUNLpE
BwphYbru4OK3pIn4xZJQ+w25LQFCpURVmIdoaCRbAXphoT3cpn+rfiarmLnuwYXL
qWkYh134Ku/6mhuw5PHQW+W2aedg5YDnaIGa1N14rQ46JSp9Ivrn84xdPYlguoHT
xW6pkyeOXC1j4vCviufrYkPC61HHvGfMArjFVBD7dl/5WD0LRCulnVF9nGs2uVel
62g+1Jpn6rPrOfm2SYIK379k5webC66JTowF7EglNe/MNNpQB9Qbu98mBHdj1odf
dMcu5GByx8TrQTT7jdz0+Rqb16SeNQJWizA3qL4kIf/0w29MY6IUbatKIRQvxyI=
=8K1F
-END PGP SIGNATURE End Message ---

Bug#812303:

[Joshua Honeycutt]

This is an issue with the gmock-1.6.0 and gtest-1.6.0 test suite. I have
created a patch to build against Debian's google-mock and libgtest-dev
packages instead which will fix the issue. This also requires synergy's
build dependencies to be updated to depend on google-mock and
libgtest-dev.

I intend to do a NMU for this fix.
Description: Builds against Debian packaged google-mock
 and libgtest-dev
Author: Joshua Honeycutt 
Forwarded: not-needed
Last-Update: 2016-10-23

--- a/src/test/CMakeLists.txt
+++ b/src/test/CMakeLists.txt
@@ -15,13 +15,11 @@
 # along with this program.  If not, see .
 
 include_directories(
-	../../tools/gtest-1.6.0
-	../../tools/gtest-1.6.0/include
-	../../tools/gmock-1.6.0
-	../../tools/gmock-1.6.0/include)
+	/usr/src/gtest
+	/usr/src/gmock)
 	
-add_library(gtest STATIC ../../tools/gtest-1.6.0/src/gtest-all.cc)
-add_library(gmock STATIC ../../tools/gmock-1.6.0/src/gmock-all.cc)
+add_library(gtest STATIC /usr/src/gtest/src/gtest-all.cc)
+add_library(gmock STATIC /usr/src/gmock/src/gmock-all.cc)
 
 add_subdirectory(integtests)
 add_subdirectory(unittests)
--- a/src/test/integtests/CMakeLists.txt
+++ b/src/test/integtests/CMakeLists.txt
@@ -72,8 +72,6 @@
 	../../lib/synergy
 	../../lib/synwinhk
 	../../lib/synwinxt
-	../../../tools/gtest-1.6.0/include
-	../../../tools/gmock-1.6.0/include
 	../unittests
 )
 
--- a/src/test/unittests/CMakeLists.txt
+++ b/src/test/unittests/CMakeLists.txt
@@ -49,8 +49,6 @@
 	../../lib/net
 	../../lib/platform
 	../../lib/synergy
-	../../../tools/gtest-1.6.0/include
-	../../../tools/gmock-1.6.0/include
 	../../../tools
 	io
 	synergy

Processed: tagging 837489, owner 837489

[Debian Bug Tracking System]

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

> tags 837489 + pending
Bug #837489 [src:antlr] antlr: Please build libantlr.a with -fPIC
Added tag(s) pending.
> owner 837489 tmanc...@debian.org
Bug #837489 [src:antlr] antlr: Please build libantlr.a with -fPIC
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.

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

Bug#837854: jana: FTBFS due to undeclared build dependencies

[Ying-Chun Liu (PaulLiu)]

I'll fix this soon.

-- 
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) 
diff -Nru jana-0.0.0+git20091215.9ec1da8a/debian/changelog jana-0.0.0+git20091215.9ec1da8a/debian/changelog
--- jana-0.0.0+git20091215.9ec1da8a/debian/changelog	2013-09-22 03:11:12.0 +0800
+++ jana-0.0.0+git20091215.9ec1da8a/debian/changelog	2016-10-24 11:52:53.0 +0800
@@ -1,3 +1,10 @@
+jana (0.0.0+git20091215.9ec1da8a-4) unstable; urgency=low
+
+  * debian/control: Add gnome-common to Build-Depends. (Closes: #837854)
+  * Bump Standards-Version to 3.9.8
+
+ -- Ying-Chun Liu (PaulLiu)   Mon, 24 Oct 2016 11:52:53 +0800
+
 jana (0.0.0+git20091215.9ec1da8a-3) unstable; urgency=low
 
   * Upload jana with eds 3.8 patch to unstable.
diff -Nru jana-0.0.0+git20091215.9ec1da8a/debian/control jana-0.0.0+git20091215.9ec1da8a/debian/control
--- jana-0.0.0+git20091215.9ec1da8a/debian/control	2013-09-22 03:11:12.0 +0800
+++ jana-0.0.0+git20091215.9ec1da8a/debian/control	2016-10-24 11:52:53.0 +0800
@@ -8,6 +8,7 @@
cdbs,
debhelper (>= 9),
docbook-xsl,
+   gnome-common,
gtk-doc-tools (>= 1.8),
intltool,
libecal1.2-dev (>= 3.8),
@@ -16,7 +17,7 @@
libgtk2.0-dev (>= 2.10.0),
libtool,
xsltproc
-Standards-Version: 3.9.4
+Standards-Version: 3.9.8
 
 Package: libjana0
 Section: libs
diff -Nru jana-0.0.0+git20091215.9ec1da8a/debian/libjana-test.manpages jana-0.0.0+git20091215.9ec1da8a/debian/libjana-test.manpages
--- jana-0.0.0+git20091215.9ec1da8a/debian/libjana-test.manpages	2013-09-21 03:06:23.0 +0800
+++ jana-0.0.0+git20091215.9ec1da8a/debian/libjana-test.manpages	2016-10-24 11:52:53.0 +0800
@@ -1,4 +1,4 @@
 jana-ecal-event.1
 jana-ecal-store-view.1
-jana-ecal-time.1
 jana-ecal-time-2.1
+jana-ecal-time.1


signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Debian Bug Tracking System]

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

> tags 831211 pending
Bug #831211 [src:ucommon] ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due 
to earlier errors
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#840728: marked as pending

[Eric Dorland]

tag 840728 pending
thanks

Hello,

Bug #840728 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-opensc/libp11.git;a=commitdiff;h=9e2a79f

---
commit 9e2a79fb560f7d368c17ed31f972df11579fe852
Author: Eric Dorland 
Date:   Sun Oct 23 15:05:38 2016 -0400

Use enginesexecdir instead of enginesdir, to work around install-exec-hook 
issues

Closes: 840728

diff --git a/debian/changelog b/debian/changelog
index 637c180..86eb1e7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,10 @@ libp11 (0.4.2-1) unstable; urgency=medium
   * New upstream release.
   * debian/control, debian/libengine-pkcs11-openssl.install, debian/rules:
 Move libengine-pkcs11-openssl package here.
+  *
+debian/patches/0001-Add-enginesexecdir-use-it-instead-of-enginesdir.patch:
+Use enginesexecdir instead of enginesdir, to work around
+install-exec-hook issues. (Closes: #840728)
 
  -- Eric Dorland   Sun, 23 Oct 2016 01:13:29 -0400
 

Processed: Bug#840728 marked as pending

[Debian Bug Tracking System]

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

> tag 840728 pending
Bug #840728 {Done: Eric Dorland } [src:libp11] libp11: FTBFS: 
openssl-1.0.2/engines: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Sun, 2016-10-23 at 22:17 +0200, Petra Ruebe-Pugliese wrote:
> Package: src:linux
> Version: 4.7.8-1
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> when performing this week's regular update on my Debian Testing
> systems, linux-image-4.7.0-1-686 was updated from 4.7.6-1 to
> 4.7.8-1_i386.deb on two Thinkpads T41.
> 
> On both of them, the system failed to boot after that update:
> grub started correctly and let me "choose" the system to boot
> (there is only one!);  after that I saw a blank screen with a
> blinking cursor in the upper left corner, and that was all.
> Something seemed to be "going on" (fan working more than usual);
> but no further reaction was to be obtained from the system(s).
> 
> Downgrading to linux-image-4.7.0-1-686_4.7.6-1_i386.deb via
> rescue-CD and "dpkg -i" (fortunately!!!) solved the problem.

> (There was no similar problem with linux-image-4.7.0-1-686-pae_4.7.8-
> 1_i386.deb
>  on two old PCs I was updating at the same time, nor with the
>  corresponding version on an AMD64 PC.)

Or on most other PCs, it seems - so I'm reducing the severity.

> -- Package-specific info:
> ** Version:
> Linux version 4.7.0-1-686 (debian-ker...@lists.debian.org) (gcc
> version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.6-1
> (2016-10-07)
> 
>  4.7.6-1 is now running correctly again, 4.7.8-1 did not boot, see
> above!
>  (So the first line does _not_ describe the problematic system!)
[...]

We're going to need some more information about where things went
wrong, which you should be able to get by replacing the 'quiet'
parameter on the boot command line with 'earlyprintk=vga'.  Please send
a photo of the log messages.

Ben.

-- 
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.

signature.asc
Description: This is a digitally signed message part

Processed: Re: Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #841850 [src:linux] linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot 
on Thinkpad T41
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #841850 [src:linux] linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot 
on Thinkpad T41
Added tag(s) moreinfo.

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

Bug#841867: dgit cannot cope with some patches because it uses gbp-pq [and 1 more messages]

[Ian Jackson]

Ian Jackson writes ("dgit cannot cope with some patches because it uses 
gbp-pq"):
> gbp pq cannot cope with all patches that dpkg-source can, because it
> uses git-apply and git-apply is not very compatible.
> 
> At the moment, this means that `dgit clone glibc' fails:
...
> I think I need to switch to using repeated dpkg-source --before-build.
> This means I need to reimplement gbp pq's metadata processing
> algorithm :-/.

You are not going to believe what I have done instead.
I suggest you sit down before you read what follows.

Ian.

>From 05db7ab051736bb106467e7f83b9e45684dd227c Mon Sep 17 00:00:00 2001
From: Ian Jackson 
Date: Mon, 24 Oct 2016 01:06:29 +0100
Subject: [PATCH] Import: Use absurd `git apply' emulation if gbp pq import
 fails

gbp import can fail due to git apply not understanding patches.
This is #841867 (against dgit).

The underlying problem is #841866 (in gbp pq) which exposes things
like #841865 and #829067 (in git).  I imagine there are other lurking
incompatibilities between git-apply and dpkg-source.

We could in principle reimplement the gbp patch metadata extraction.
But that would be quite tiresome and have its own compatibility
problems.

The real problem is just `git apply'.  (Indeed gbp already tries git
apply without, and then with, a whitespace fix option.)  We work
around the trouble by providing our own implementation of `git apply'.

Specifically:

We try to do things the sane way (just running gbp pq import) first.
If that works, great.  If it doesn't, we put /usr/share/dgit/absurd on
the PATH.  That contains only a sh script called `git'.  This sh
script figures out whether the caller is trying to invoke `git apply'.
If not, it runs the real git.

If the caller wanted git-apply, the absurd git script emulates it
using dpkg-source --before-build.  Conveniently, we know that the
series file will not be touched by patches.  So we can write just the
patch we care about into the series file, and run --before-build,
which applies just that one patch.

The results are committed (minus the .pc), and for the next patch,
dpkg-source sees again a tree with simply a single patch to apply.

We try ordinary gbp pq first because our absurd approach is very slow
on a big tree.  Also we would like to maximise our chances of the
import working.  If git and/or gbp ever work better by themselves, all
of this craziness will simply not happen.

Signed-off-by: Ian Jackson 
---
 Makefile   |  3 +++
 absurd/git | 70 ++
 dgit   | 49 +++
 3 files changed, 109 insertions(+), 13 deletions(-)
 create mode 100755 absurd/git

diff --git a/Makefile b/Makefile
index b72a1e9..9491e4d 100644
--- a/Makefile
+++ b/Makefile
@@ -37,6 +37,7 @@ MAN1PAGES=dgit.1
 MAN7PAGES=dgit.7 dgit-maint-merge.7
 TXTDOCS=README.dsc-import
 PERLMODULES=Debian/Dgit.pm
+ABSURDITIES=git
 
 INFRA_PROGRAMS=dgit-repos-server dgit-ssh-dispatch \
dgit-repos-policy-debian dgit-repos-admin-debian \
@@ -57,6 +58,8 @@ substituted/%:%
 install:   installdirs all
$(INSTALL_PROGRAM) $(addprefix substituted/,$(PROGRAMS)) \
$(DESTDIR)$(bindir)
+   $(INSTALL_PROGRAM) $(addprefix absurd/,$(ABSURDITIES)) \
+   $(DESTDIR)$(absurddir)
$(INSTALL_DATA) $(MAN1PAGES) $(DESTDIR)$(man1dir)
$(INSTALL_DATA) $(MAN7PAGES) $(DESTDIR)$(man7dir)
$(INSTALL_DATA) $(TXTDOCS) $(DESTDIR)$(txtdocdir)
diff --git a/absurd/git b/absurd/git
new file mode 100755
index 000..039bbf0
--- /dev/null
+++ b/absurd/git
@@ -0,0 +1,70 @@
+#!/bin/sh
+set -e
+
+fail () {
+   echo >&2 "DGIT ABSURD GIT APPLY - FAILED: $*"
+   exit 127
+}
+
+self=${0%/*}
+npath=${PATH#$self:}
+if test "x$PATH" = "x$npath"; then
+   fail "PATH FILTER FAIL ($0 $self $PATH)"
+fi
+
+bypass=true
+for arg in "$@"; do
+   case "$arg" in
+   apply)  bypass=false; break ;;
+   -*) ;;
+   *)  bypass=true; break  ;;
+   esac
+done
+
+if $bypass; then
+   PATH=$npath
+   exec git "$@"
+fi
+
+echo >&2 "DGIT ABSURD GIT APPLY - NO BYPASS: $*"
+
+#exec >/dev/tty 2>&1
+
+index=0
+noo=0
+
+for arg in "$@"; do
+   case "$noo.$arg" in
+   1.--index)
+   index=1
+   continue
+   ;;
+   ?.-*)
+   fail "UNKNOWN OPTION $arg ($*)"
+   ;;
+   0.apply)
+   ;;
+   1.*)patch="$arg"
+   ;;
+   *)
+   fail "BAD USAGE $arg ($noo $*)"
+   esac
+   noo=$(( $noo + 1 ))
+done
+
+if [ $noo != 2 ]; then
+   fail "NO PATCH ($*)"
+fi
+
+pwd=`pwd`
+patch=${patch#$pwd/debian/patches/}
+printf "%s\n" "$patch" >debian/patches/series
+
+dpkg-source --before-build .
+
+rm -rf .pc
+git checkout debian/patches/series
+git add -Af .
+
+echo >&2 "DGIT ABSURD GIT APPLY - APPLIED 

Processed: Re: Bug#841768: mtasc: FTBFS: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + wontfix
Bug #841768 [src:mtasc] mtasc: FTBFS: relocation R_X86_64_32S against `.rodata' 
can not be used when making a shared object; recompile with -fPIC
Added tag(s) wontfix.

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

Bug#841768: mtasc: FTBFS: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC

[Paul Wise]

Control: tags -1 + wontfix

On Sun, 2016-10-23 at 11:56 +0100, Chris Lamb wrote:

> mtasc fails to build from source in unstable/amd64:

Sounds like the recent GCC changes broke ocaml. In either case, this
won't be fixed in mtasc, because I want to remove it from Debian
because it is obsoleted by browser HTML5 support (#831553).

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#837663: [Pkg-kannel-devel] Bug#837663: Only a binNMU is required for kannel-dev

[Jonas Smedegaard]

Quoting Adrian Bunk (2016-10-23 20:32:23)
> Control: retitle -1 kannel-dev: libgwlib.a needs binNMU rebuild with MySQL 
> 5.7 and -fPIE
> Control: severity -1 serious
> Control: affects -1 = src:kannel-sqlbox
> 
> Two issues appeared in unstable:
> - MySQL 5.7 removes -lmysqlclient_r, which breaks packages using
>   "gw-config --libs"
> - libgwlib.a nneds a rebuild with -fPIE
> 
> A binNMU is sufficient to fix both issues, and already requested.

Thanks a lot for taking care of it!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#812532: marked as done (files with the same name installed in / and /usr)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:48:44 +
with message-id 
and subject line Bug#812532: fixed in yp-tools 3.3-5
has caused the Debian Bug report #812532,
regarding files with the same name installed in / and /usr
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.)


-- 
812532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yp-tools
Version: 3.3-1
Severity: important
Usertags: usrmerge

The package installs some files in /usr/bin/:

/usr/bin/domainname
/usr/bin/nisdomainname
/usr/bin/ypdomainname

which have the same name of file installed by the hostname package in 
/bin/, so this breaks the package when installed on a marged /usr system.

For more information about merged /usr please see
https://wiki.debian.org/UsrMerge and
https://anonscm.debian.org/cgit/users/md/usrmerge.git/plain/debian/README.Debian

I do not know exactly how yp-tools is supposed to work, but this kind of 
setup is definitely not correct because both programs may be called by 
different software depending on the $PATH, boot progress and explicit 
paths.

If the files are not actually needed then they should not be installed 
at all, but if they must be used instead of the ones provided by 
hostname then yp-tools should divert these and install its own binaries 
in /bin/.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: yp-tools
Source-Version: 3.3-5

We believe that the bug you reported is fixed in the latest version of
yp-tools, 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.
Mark Brown  (supplier of updated yp-tools 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: Sun, 23 Oct 2016 00:15:55 +0100
Source: yp-tools
Binary: yp-tools libnis-dev libnis1
Architecture: source amd64
Version: 3.3-5
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Description:
 libnis-dev - Library for NIS applications - development files
 libnis1- Library for Network Information Service (NIS) applications
 yp-tools   - Tools for working with Network Information System (NIS)
Closes: 812532
Changes:
 yp-tools (3.3-5) unstable; urgency=low
 .
   * Don't bother installing the domainname utilities (closes: #812532).
Checksums-Sha1:
 abf1fa812abf49c03cab6f08cb1fba92f5635e4c 1471 yp-tools_3.3-5.dsc
 abd555f2865b6165c021fc0d3525f01171d634a1 5272 yp-tools_3.3-5.debian.tar.xz
 57f0dd4f0c0105babe4d74b9940c1063181d7596 14526 libnis-dev_3.3-5_amd64.deb
 7d873d46aff94fcd25041bab1179da89a3cfde2d 47698 libnis1-dbgsym_3.3-5_amd64.deb
 8d4e3f7a6bd580e83b3f703c11363be1fba397d2 17278 libnis1_3.3-5_amd64.deb
 9a081408404f5ef30b159d0d3268b646d19a47bc 83678 yp-tools-dbgsym_3.3-5_amd64.deb
 812a3a050d02679d324447cf5b1336abd82175ad 41052 yp-tools_3.3-5_amd64.deb
Checksums-Sha256:
 d38bc9d4bceb738a71f34a0a6a96f48cb880a11e21ebf37c0004e7223a5fda61 1471 
yp-tools_3.3-5.dsc
 6c7c6058736a5ce75b627dee226bf1220c90f35f2b92f4174da64c6b6dc019bf 5272 
yp-tools_3.3-5.debian.tar.xz
 95aac8aac36cf06bd13efcb6d0c2ac6f45a86368a27ac8f3a0e6a217283e4627 14526 
libnis-dev_3.3-5_amd64.deb
 a50660275bd900cacca7c19cdcfb1deb6f029c45e3d86cd3b9a85c3b226858a7 47698 
libnis1-dbgsym_3.3-5_amd64.deb
 65e77e1deb9c76db6304b6a0788a4bdb8e322c7fa916a3ac7442f81c03b2a71a 17278 
libnis1_3.3-5_amd64.deb
 e65648d7d63bca4c355b52bdef8ca525854bcb9d3fb24049a86ef875e9dac242 83678 
yp-tools-dbgsym_3.3-5_amd64.deb
 bddd43c9446e1beb79afd3098128f05432a574c4d71870e86404cef7310b03e8 41052 
yp-tools_3.3-5_amd64.deb
Files:
 b0ac163f4aaad81e2ddd7351b6109511 1471 libs optional yp-tools_3.3-5.dsc
 d3f3c9bbecc5415cbe058e619b686ab9 5272 libs optional 
yp-tools_3.3-5.debian.tar.xz
 98fd58717259cfa2426b6a51c18d05bf 14526 libdevel optional 
libnis-dev_3.3-5_amd64.deb
 ff0a3c989f8f51df97d5463c3cd88006 47698 debug extra 
libnis1-dbgsym_3.3-5_amd64.deb
 0161523c7aea31a02989631c060d5724 17278 libs optional 

Bug#817733: marked as done (xkbset: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:48:21 +
with message-id 
and subject line Bug#817733: fixed in xkbset 0.5-5.2
has caused the Debian Bug report #817733,
regarding xkbset: Removal of debhelper compat 4
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.)


-- 
817733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xkbset
Severity: important
Usertags: compat-4-removal

Hi,

The package xkbset uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: xkbset
Source-Version: 0.5-5.2

We believe that the bug you reported is fixed in the latest version of
xkbset, 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 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated xkbset 
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, 12 Oct 2016 22:44:24 -0300
Source: xkbset
Binary: xkbset
Architecture: source amd64
Version: 0.5-5.2
Distribution: unstable
Urgency: medium
Maintainer: Francois Gurin 
Changed-By: Joao Eriberto Mota Filho 
Description:
 xkbset - Small utility to change the AccessX settings of XKEYBOARD
Closes: 817733
Changes:
 xkbset (0.5-5.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817733)
   * debian/control:
   - Added the ${misc:Depends} variable.
   - Added the Homepage field.
   - Bumped Standards-Version to 3.9.8.
   * debian/watch: created.
Checksums-Sha1:
 f83b0d34d9306e7d5ae596d4a30e5bc32bf251fb 1651 xkbset_0.5-5.2.dsc
 82cca8b0091607d4cb5df29a598ca0c2396146c5 4007 xkbset_0.5-5.2.diff.gz
 4d9e8f9abba6a822074b5353b50429912c811033 18294 xkbset_0.5-5.2_amd64.deb
Checksums-Sha256:
 fe8ee481a01dc894b0fa4d0f6bf3621a6689b0458afcde50197b31dc30604cea 1651 
xkbset_0.5-5.2.dsc
 f5aa1601224cfb8f890ff25d51e1d3caa0031c8070c657bedd70ab612bdedf41 4007 
xkbset_0.5-5.2.diff.gz
 fbabd642aadd4b754309d1d17b076560e432374e6766d3a7f51fe825cffc3461 18294 
xkbset_0.5-5.2_amd64.deb
Files:
 74cd41298ac64d10a8fe1aa79e6e1131 1651 x11 extra xkbset_0.5-5.2.dsc
 fd992e30ddcdab64ca16b0a9a1b1c7f6 4007 x11 extra xkbset_0.5-5.2.diff.gz
 b68859b6c946a5186d3626566fba28ed 18294 x11 extra xkbset_0.5-5.2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX/uoAAAoJEN5juccE6+nvSMUP/3WQ2S5V9gNXQgm6FupsbRFW
L+XelknpEs5ekYsBo5jUIPfqLc/Y7oyD7wFztl9OTkYi3/KN9SVaeGVKHUsmtUot
JbJNXOv7k8I1YSv/ydB8mmI41UjIfLnmYgz8vzygYZVzmIlOT9RLE+KrRiKiqlGz
3awffZ3NTqh7UcZ74ttETibPx0O3dduriVDwleD+gnexavu6OfLstrLX4E1u7Mso
DHHhWaoB9quRjj2pFesDWpUA6xw83xemehn9efHPT05C1bmvVoWOw/R/EzAe4hLH
1sh304b3Qz7NdZ32pYWRwm5hhCgt2h6nMkGn1SbZ9svsp2+mdQWFZplgaq/mRKwO
krdlwqAZMIR/F2U8zZLhZa6xI9SetL6DxWtmG2Kr1d/aLK6gHpT0Cjvk2wi2MFNS
m00XTIFjUlkei5Er54Ay9BG9XnsngR/j6gUuR/mYsIkO5NY7ukcBbW2RM7MBYrcM
9gBjGXaWpkBtY1Hy70fc0rRLdbFj4HmWuwfMWM2D2nEXt0keGRvxq9/PkZX594w0
Iw6nmuLj04vva0NpuX0e/p/Ahug6CYftN2hP71bA/NzTNqzlQkzFudlhvwjK16bf
R/D4rC1JZaMgiR/7rVip9jEdJx82pd34HE8yUmuMX4OSWpmSLWmMTlWG/cRU5wCb
g8oULLXg08suewJtd1Bg
=u1Ak
-END PGP SIGNATURE End Message ---

Bug#840230: marked as done (When installing to rootfs on LVM, an empty subvol= is appended to rootflags)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:49:06 +
with message-id 
and subject line Bug#840230: fixed in zipl-installer 0.0.35
has caused the Debian Bug report #840230,
regarding When installing to rootfs on LVM, an empty subvol= is appended to 
rootflags
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.)


-- 
840230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zipl-installer
Version: 0.0.33
Severity: serious

zipl-installer 0.0.33 breaks installation for normal non-btrfs root
filesystems.

  (initramfs) cat /proc/cmdline
  root=/dev/mapper/vg-root rootflags=subvol= BOOT_IMAGE=0 

The empty subvol= makes mount barf as it's not a valid ext4 flag. The code
does not seem too healthy to me either:

  if subvol="$(btrfs subvolume show /target 2>/dev/null | sed -n '2s/.*:[\t 
]*//p')"
  then
  info "Root filesystem on btrfs subvolume ${subvol}"
  PARAMETER="$PARAMETER rootflags=subvol=${subvol}"
  fi

It'd have been more helpful to take the output and compare it to the empty
string instead.
--- End Message ---
--- Begin Message ---
Source: zipl-installer
Source-Version: 0.0.35

We believe that the bug you reported is fixed in the latest version of
zipl-installer, 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 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Kern  (supplier of updated zipl-installer 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, 23 Oct 2016 23:25:37 +0200
Source: zipl-installer
Binary: zipl-installer
Architecture: source s390x
Version: 0.0.35
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Philipp Kern 
Description:
 zipl-installer - Make DASD bootable (udeb)
Closes: 840230
Changes:
 zipl-installer (0.0.35) unstable; urgency=medium
 .
   * Copy Ubuntu's fix-up for the btrfs subvolume check from 0.0.33ubuntu2.
 (Closes: #840230)
Checksums-Sha1:
 be89448c61727659a11a95995425dee9b34f404f 1353 zipl-installer_0.0.35.dsc
 77317ffefb821e20cd1a8e4508afb63d3fced7dc 22540 zipl-installer_0.0.35.tar.xz
 e9a47eddcb43626ffcf3c081ef2c2f2f42576b72 4916 zipl-installer_0.0.35_s390x.udeb
Checksums-Sha256:
 ad52e17d7d4ea2e91522dd81acf0fd4137e821aaa22c2d046604921e9276a8be 1353 
zipl-installer_0.0.35.dsc
 6fd0d45bf975b3c48d082311b1c41e0c526f4839b249fac44476492540e1d5c7 22540 
zipl-installer_0.0.35.tar.xz
 df46026f84f7defb62c7f7fc8304b281296b2a62c11c34746a9644867fde08d8 4916 
zipl-installer_0.0.35_s390x.udeb
Files:
 2664aaa0cb419b3c2f03be456d4dbc0f 1353 debian-installer standard 
zipl-installer_0.0.35.dsc
 5fbf03ccddd733e608c16c14a0da0084 22540 debian-installer standard 
zipl-installer_0.0.35.tar.xz
 20b236791456cff8c2035fe20d78 4916 debian-installer standard 
zipl-installer_0.0.35_s390x.udeb

-BEGIN PGP SIGNATURE-

iQEuBAEBCAAYBQJYDSssERxwa2VybkBkZWJpYW4ub3JnAAoJEERuJUU10FbseQMI
ALPjYQyhtqUZA1hTwV1Y6GnjI2M3BTg/9Jku9AsbwqeTG58kdRl+tW+aGUHaTSg8
wghnwaBGgRRwJ6TdrT/lFPslNtWHt+/+Ttm+QUSG4BWDQNpZFbTVPPQFk2KSMxiC
K5mN9U6Oyv22Vuy2Pi826jN92XhJpEvWPXhAyzhTFG1G/Gh6iPM+vLsN+7ZhYxel
WVPKRX9UGP4fYEQGlaSF8wNBdgMPPXCmhgHdFzgCTD8vlvWsjjA4EeOH7dTnXP6R
hiTd+jMY7+O6YBnqWC/WZ0KSgNwjGW99iZAAdqtidwKZOwLugfedpiOVydQTGUyI
JC6d6lqI2aF1WmWb35Dljvs=
=1Igk
-END PGP SIGNATURE End Message ---

Bug#837712: marked as done (xemacs21: FTBFS with bindnow and PIE enabled)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:48:15 +
with message-id 
and subject line Bug#837712: fixed in xemacs21 21.4.24-4
has caused the Debian Bug report #837712,
regarding xemacs21: FTBFS with bindnow and PIE enabled
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.)


-- 
837712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xemacs21
Version: 21.4.24-2
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: FTBFS on amd64 with extra hardening

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64 with patched GCC and dpkg.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64.

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part (hopefully):
...
Loading /<>/lisp/loadhist.elc...
Loading /<>/lisp/loaddefs.elc...
Loading site-load...
Finding pointers to doc strings...
Finding pointers to doc strings...done
Dumping under the name xemacs
Testing for Lisp shadows ...
GNUmakefile:103: recipe for target 'xemacs.dmp' failed
make[3]: *** [xemacs.dmp] Segmentation fault
make[3]: *** Deleting file 'xemacs.dmp'
...

The full build log is available from:
 
https://people.debian.org/~lucas/logs/2016/08/30/pie-bindnow-20160830/with-pie-bindnow/xemacs21_21.4.24-2_unstable_pie-bindnow.log.gz

The patch used in Ubuntu disabling PIE probably fixes the problem.

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Source: xemacs21
Source-Version: 21.4.24-4

We believe that the bug you reported is fixed in the latest version of
xemacs21, 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 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mark Brown  (supplier of updated xemacs21 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: Sun, 23 Oct 2016 00:08:16 +0100
Source: xemacs21
Binary: xemacs21 xemacs21-mule xemacs21-nomule xemacs21-mule-canna-wnn 
xemacs21-bin xemacs21-support xemacs21-supportel
Architecture: source amd64 all
Version: 21.4.24-4
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Description:
 xemacs21   - highly customizable text editor
 xemacs21-bin - highly customizable text editor -- support binaries
 xemacs21-mule - highly customizable text editor -- Mule binary
 xemacs21-mule-canna-wnn - highly customizable text editor -- Mule binary 
compiled with Cann
 xemacs21-nomule - highly customizable text editor -- Non-mule binary
 xemacs21-support - highly customizable text editor -- architecture independent 
suppo
 xemacs21-supportel - highly customizable text editor -- non-required library 
files
Closes: 837712
Changes:
 xemacs21 (21.4.24-4) unstable; urgency=low
 .
   * Force off PIE since GCC enabled it by default which breaks the LISP
 handling (closes: #837712)
Checksums-Sha1:
 0f770214ca16919f8c6594d818b9543f2e3b43fa 2114 xemacs21_21.4.24-4.dsc
 d9c3d13be9022cc4ca5a9128190a964f2932ebed 32816 xemacs21_21.4.24-4.debian.tar.xz
 b7c531e30b70cc70a09b213a7640f25a815daee3 215780 
xemacs21-bin-dbgsym_21.4.24-4_amd64.deb
 f75691353527af82e0680033e15b21ff7884e862 399500 
xemacs21-bin_21.4.24-4_amd64.deb
 43b7a34ad83c141268848c32c89630d47e175a03 3072354 
xemacs21-mule-canna-wnn-dbgsym_21.4.24-4_amd64.deb
 331a194d35cc8bd280945f293e92db6f14e4c5e9 1756910 
xemacs21-mule-canna-wnn_21.4.24-4_amd64.deb
 44343c595a36c86106ac87ec052bc17d071fac4f 3015058 
xemacs21-mule-dbgsym_21.4.24-4_amd64.deb
 526f1161eb44f1d1d1a507c4f24fdf53aff73348 1674164 
xemacs21-mule_21.4.24-4_amd64.deb
 840e4b907f7741fb080d527ccb99dd62ecffaf3b 2760802 
xemacs21-nomule-dbgsym_21.4.24-4_amd64.deb
 f8d8a24821602477e815587f62c0dd24ba828640 1505292 
xemacs21-nomule_21.4.24-4_amd64.deb
 36b86980d2e61e726c476029803f71b319760f1a 4182744 
xemacs21-support_21.4.24-4_all.deb
 be4e360ea3aefced4d66b37ae19dbb66a6c6b1c3 1310618 

Bug#817742: marked as done (yaret: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:48:33 +
with message-id 
and subject line Bug#817742: fixed in yaret 2.1.0-5.1
has caused the Debian Bug report #817742,
regarding yaret: Removal of debhelper compat 4
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.)


-- 
817742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yaret
Severity: important
Usertags: compat-4-removal

Hi,

The package yaret uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: yaret
Source-Version: 2.1.0-5.1

We believe that the bug you reported is fixed in the latest version of
yaret, 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 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated yaret 
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, 12 Oct 2016 22:28:47 -0300
Source: yaret
Binary: yaret
Architecture: source
Version: 2.1.0-5.1
Distribution: unstable
Urgency: medium
Maintainer: Marco Nenciarini 
Changed-By: Joao Eriberto Mota Filho 
Description:
 yaret  - console tool to turn CDs into encoded music
Closes: 817742
Changes:
 yaret (2.1.0-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817742)
   * Used wrap-and-sort.
   * debian/control:
   - Added Homepage field.
   - Bumped Standards-Version to 3.9.8.
   - Removed the leading article from short description.
Checksums-Sha1:
 beec2bb4f9294dfdafa248687b53d94db22d4e40 1644 yaret_2.1.0-5.1.dsc
 8af3078dd5b938a1ffb79154d89841282b74c1a4 7867 yaret_2.1.0-5.1.diff.gz
Checksums-Sha256:
 7c47696657a202b72d23042a84289ce7eba29c7083a5ae789d1d00d6554682ba 1644 
yaret_2.1.0-5.1.dsc
 b0c1b05bced482341fba6535ac6cd379e1c3f3278dd9401896b0dbd6952d1143 7867 
yaret_2.1.0-5.1.diff.gz
Files:
 d74791fb28949dd9e9e6437bc9c048b2 1644 sound optional yaret_2.1.0-5.1.dsc
 d056e15fd29d9feb4fe0af8ce0dbe9c2 7867 sound optional yaret_2.1.0-5.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX/uUlAAoJEN5juccE6+nvPg0QAJQfzqCk9/wc/Fnh4mhgVAue
n7tA5CECEaZLNxYAZwkKoboKeZEDHwpfwxei6BLWzpBIq1fw/2vZl0ibGZlKGUI0
/dVW0UtJDdH9YzKd4OWgJnvt8neH/ix8jZuJkrZxFAKdSNmcHfsB3FeCh5IzwT8Z
b1XiFJlqzQjG8SrO/wrVyDKX4R5bBjlLGKMTN98MafNVi75hUyODiERhfPw+1ggE
98koH/UtW2YocsHn8cR+X5dpjCM+vDjg4ltUWwu2Nn6juyj856tiUjlASDz0yvfY
dQ2U1n8ngRcsFTqrxU9Ig4Qi1sGC3aLUaWZ+9SdSSzM/VRw/1oz+VxNuIcxoKlff
b4YE63slyHHSTHlc9vGRBoDGdT7mD+/9jRqlv+wKOOgv2D6nwnwDTx1gELhIKjJx
nuG6JpZh9/2nWx2ljzzPj5A1m79pGf+e0qDdzpWzqG8jJZITO2rsGkApIfPm4AOh
lr/YwjzK5EBjymIkBInoWlzWarVXodAQ+u2wYnwkhfdOYy0sGSC8D2LgxfCR+cUv
uFrHRoMdtMy9Q2np6fP/ZN7umb63RjRJY2THvaQTyPfEIItmQ/grBV0gm4bcMcWC
hy+mMzKB3PRh7FsYJzOm/3h+vHIPqswTAsn4ZgMFZ4wBgsQ/WVx8xMrAQY+acRXw
OOeCMJDy+lAA1iuCvHYK
=c3So
-END PGP SIGNATURE End Message ---

Bug#839306: marked as done (translate-toolkit: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:46:28 +
with message-id 
and subject line Bug#839306: fixed in translate-toolkit 2.0.0~b5-2
has caused the Debian Bug report #839306,
regarding translate-toolkit: FTBFS: Tests failures
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.)


-- 
839306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: translate-toolkit
Version: 1.13.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160930 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> __query_init_orig(self, *args)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = <[AttributeError("'Query' object has no attribute 'this'") raised in 
> repr()] SafeRepr object at 0x7f3871c186c8>
> args = <[TypeError("__repr__ returned non-string (type NoneType)") raised in 
> repr()] SafeRepr object at 0x7f3871c18830>
> 
> def __init__(self, *args):
> """Xapian::Query::Query(Query::op op_) """
> >   _xapian.Query_swiginit(self, _xapian.new_Query(*args))
> E   TypeError: in method 'new_Query', argument 1 of type 'std::string 
> const &'
> 
> /usr/lib/python2.7/dist-packages/xapian/__init__.py:2268: TypeError
> === 1 failed, 1996 passed, 2 skipped, 45 xfailed, 3 xpassed in 9.29 seconds 
> 
> E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: 
> PATH=/<>/.pybuild/pythonX.Y_2.7/build:$PATH py.test -rxs
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
> exit code 13
> debian/rules:61: recipe for target 'override_dh_auto_test' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

The full build log is available from:
   http://aws-logs.debian.net/2016/09/30/translate-toolkit_1.13.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: translate-toolkit
Source-Version: 2.0.0~b5-2

We believe that the bug you reported is fixed in the latest version of
translate-toolkit, 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 839...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated translate-toolkit 
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, 23 Oct 2016 01:11:44 +1100
Source: translate-toolkit
Binary: translate-toolkit python-translate python3-translate 
translate-toolkit-doc
Architecture: source
Version: 2.0.0~b5-2
Distribution: experimental
Urgency: medium
Maintainer: Debian l10n developers 
Changed-By: Stuart Prescott 
Closes: 839306
Description: 
 python3-translate - Toolkit assisting in the localization of software (Python 
3)
 python-translate - Toolkit assisting in the localization of software (Python 2)
 translate-toolkit-doc - Toolkit assisting in the localization of software 
(documentation)
 translate-toolkit - Toolkit assisting in the localization of software
Changes:
 translate-toolkit (2.0.0~b5-2) experimental; urgency=medium
 .
   * Add python3-xapian to the dependencies now that it is available.
   * Add patches so that indexers and xapian module work under Python 3
 - xapian-no-apache-check.patch: skip check if module is 

Bug#841759: marked as done (smarty-gettext : Depends: php7-cli but it is not installable)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:44:57 +
with message-id 
and subject line Bug#841759: fixed in smarty-gettext 1.4.0-2
has caused the Debian Bug report #841759,
regarding smarty-gettext : Depends: php7-cli but it is not installable
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.)


-- 
841759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: smarty-gettext
Version: 1.4.0-1
Severity: serious
Justification: fails to install

Hi Mike,

in current sid of today:

$ apt install smarty-gettext
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 smarty-gettext : Depends: php7-cli but it is not installable
E: Unable to correct problems, you have held broken packages.


This also makes gosa and thus education-main-server fail to install…


-- 
cheers,
Holger


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: smarty-gettext
Source-Version: 1.4.0-2

We believe that the bug you reported is fixed in the latest version of
smarty-gettext, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated smarty-gettext 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, 23 Oct 2016 22:35:38 +0200
Source: smarty-gettext
Binary: smarty-gettext
Architecture: source all
Version: 1.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel 
Changed-By: Mike Gabriel 
Description:
 smarty-gettext - Gettext plugin enabling internationalization in Smarty
Closes: 841759
Changes:
 smarty-gettext (1.4.0-2) unstable; urgency=medium
 .
   * debian/control:
 + Fix flawed dependency on phpX-cli: php7.0-cli (Closes: #841759).
Checksums-Sha1:
 a7477b693315ab59b7dc33fe3b3c842809c5b2bb 1930 smarty-gettext_1.4.0-2.dsc
 ab2b1bb23bbda3306a312c022f516db62fc16f26 3336 
smarty-gettext_1.4.0-2.debian.tar.xz
 43aaef75f5d05a7eed21f469d1a7bb75d48f098a 13296 smarty-gettext_1.4.0-2_all.deb
Checksums-Sha256:
 fd72add86818904316f71aea9c4799d978903d14140ac3608c2c1f47091a45bd 1930 
smarty-gettext_1.4.0-2.dsc
 af41e85e95c121af9e2afadacad2957cb1fe6dc85c568dbb6177f026827bc93b 3336 
smarty-gettext_1.4.0-2.debian.tar.xz
 43f8e894f08d2b5595e0407d7b66eb62226e4d57654e52841c2fc66f5e9b8817 13296 
smarty-gettext_1.4.0-2_all.deb
Files:
 eda61837c86bbcac720f20a40d767ece 1930 web optional smarty-gettext_1.4.0-2.dsc
 0fd7ebdb098459fbab6945756de66738 3336 web optional 
smarty-gettext_1.4.0-2.debian.tar.xz
 d7f22f2326fbabae8340a1dffca8a508 13296 web optional 
smarty-gettext_1.4.0-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYDSBQAAoJEJr0azAldxsx/bcP/1yDRI0k4yssDziq3HiODtPB
wTsNhw328gEILLi7WZCjXTuezt17NWorOQzpnwN8NAYsEbbIC/a2qcRpLdSJNJQX
7hBog5kmf1Wyi11auHbY0nO5YZx+vmtNsFq3p8NDM29iqpSjz2JZuUv5meI0mLQK
3xMEKE/Mqg35exGdIbIIAEPUDiOKwnNilrwOmaKYKTNWW1qG6Q2qLEDdhhkgWb6B
7Mzp3c2vnkZHZH8kd1+0FR2hCuLXuYnxQ3BAzmSIua38eKona3+JK5iNQFXTwcCq
65opImXRqUcjNwifpCu4CK9J+4XVTZRdW0NOrxAysqc1yk3syMQX3Do7Q2jDESyR
ijb4dzd3NgXzYWHatiXiZBxg33VT1FuwaeRxuxbDdw673+BJ5W6TkHqEmSmuSeK2
0R8r9TsOd8/b8lQMtcxau4k/ncTh8Mp+wQphh7WDCNywHxMeGI4oDEfSTM08UJHv
E+XMk6bLdvluSkemz1Rq6CbrgfMGvvsAcyqP82ISf7Fq+LrRaWQ7KinRudkonuP9
HmTKd4LYcZGRzH+eT5eM0YDSA5289R13Fozz9p/BE7rPHIoC2cXSTJH8d/l18Kjd
Is/16CZO084x+8IecVRFMHVxMeOjGhPWSGiOFHM4Aw43tgWZEtcsRSnqwYbz8pb8
VIrH94egaH26IGEx8IUq
=y2+5
-END PGP SIGNATURE End Message ---

Bug#841713: marked as done (tunnelx: FTBFS with dpkg-buildpackage -A (chown error))

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:46:33 +
with message-id 
and subject line Bug#841713: fixed in tunnelx 20160713-2
has caused the Debian Bug report #841713,
regarding tunnelx: FTBFS with dpkg-buildpackage -A (chown error)
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.)


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

Hello Wookey (and Niels).

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


[...]
 debian/rules build-indep
dh --with javahelper build-indep
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
   jh_linkjars -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
docbook-to-man debian/manpage.sgml > tunnelx.1
dh_installman --verbose
dh_installman: Compatibility levels before 9 are deprecated (level 7 in use)
install -d debian/tunnelx/usr/share/man/man1/
install -p -m0644 tunnelx.1 debian/tunnelx/usr/share/man/man1/tunnelx.1
man --recode UTF-8 ./tunnelx\.1 > tunnelx\.1\.new
chmod 0755 -- tunnelx.1.new
chown 0:0 -- tunnelx.1.new
chown: changing ownership of 'tunnelx.1.new': Operation not permitted
dh_installman: chown 0:0 -- tunnelx.1.new returned exit code 1
debian/rules:11: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The reason seems to be that there is a "dh_installman" command inside
override_dh_auto_build target, which runs as a normal user, but
dh_installman makes a chown and it fails, because we are not root yet.

Since we are already using "dh" here, the easy fix is not to call
dh_installman yet but instead let it happen automatically as part of
the dh sequence.

Trivial patch below.

The funny thing is that "dpkg-buildpackage" alone does not fail and I
don't know why. I'm Cc:ing Niels (with X-Debbugs-Cc) in case he wants
to say something about this.

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -9,7 +9,6 @@ export JAVE_HOME=/usr/lib/jvm/default-java
 
 override_dh_auto_build:
docbook-to-man debian/manpage.sgml > tunnelx.1
-   dh_installman --verbose
 
 override_dh_clean:
dh_clean
--- End Message ---
--- Begin Message ---
Source: tunnelx
Source-Version: 20160713-2

We believe that the bug you reported is fixed in the latest version of
tunnelx, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Wookey  (supplier of updated tunnelx 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, 22 Oct 2016 21:24:22 +0100
Source: tunnelx
Binary: tunnelx
Architecture: source
Version: 20160713-2
Distribution: unstable
Urgency: medium
Maintainer: Wookey 
Changed-By: Wookey 
Description:
 tunnelx- Cave Survey drawing software
Closes: 841713
Changes:
 tunnelx (20160713-2) unstable; urgency=medium
 .
   * Fix FTBFS with dpkg-buildpackage -A (Closes: #841713)
Checksums-Sha1:
 a41ea03f35fac96ac5e60c52e9c8315c079cc99d 1893 tunnelx_20160713-2.dsc
 067ff5d0c9baf9508507a259c5305f3f1bd9ab2e 13728 tunnelx_20160713-2.debian.tar.xz
Checksums-Sha256:
 79e58990439e9c6ddcc781100bf81d27d8715d681665869fb37efb8d3a7984e5 1893 
tunnelx_20160713-2.dsc
 581ae22ead1698b04a983e1673a966e9fb964aa19346edadffa0c20229f3d0b6 13728 
tunnelx_20160713-2.debian.tar.xz
Files:
 7ad7926abdabe1ea9cce9e1fc0c667ff 1893 

Bug#831093: marked as done (qterm: FTBFS with GCC 6: uaocodec.cpp:15598:1: error: narrowing conversion of ''\37777777600'' from 'char' to 'uchar {aka unsigned char}' inside { } [-Wnarrowing])

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:43:07 +
with message-id 
and subject line Bug#831093: fixed in qterm 1:0.5.12-1.2
has caused the Debian Bug report #831093,
regarding qterm: FTBFS with GCC 6: uaocodec.cpp:15598:1: error: narrowing 
conversion of ''\3777600'' from 'char' to 'uchar {aka unsigned char}' 
inside { } [-Wnarrowing]
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.)


-- 
831093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qterm
Version: 1:0.5.12-1.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> [ 51%] Building CXX object src/CMakeFiles/qterm.dir/aboutdialog.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/g++   -DDBUS_ENABLED 
> -DHAVE_CONFIG_H -DSCRIPT_ENABLED -DSSH_ENABLED -I/usr/include/qt4/QtDBus 
> -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -o CMakeFiles/qterm.dir/aboutdialog.cpp.o -c 
> /«PKGBUILDDIR»/src/aboutdialog.cpp
> [ 52%] Building CXX object src/CMakeFiles/qterm.dir/addrdialog.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/g++   -DDBUS_ENABLED 
> -DHAVE_CONFIG_H -DSCRIPT_ENABLED -DSSH_ENABLED -I/usr/include/qt4/QtDBus 
> -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -o CMakeFiles/qterm.dir/addrdialog.cpp.o -c 
> /«PKGBUILDDIR»/src/addrdialog.cpp
> [ 53%] Building CXX object src/CMakeFiles/qterm.dir/articledialog.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/g++   -DDBUS_ENABLED 
> -DHAVE_CONFIG_H -DSCRIPT_ENABLED -DSSH_ENABLED -I/usr/include/qt4/QtDBus 
> -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -o CMakeFiles/qterm.dir/articledialog.cpp.o -c 
> /«PKGBUILDDIR»/src/articledialog.cpp
> [ 54%] Building CXX object src/CMakeFiles/qterm.dir/assistantclient.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/g++   -DDBUS_ENABLED 
> -DHAVE_CONFIG_H -DSCRIPT_ENABLED -DSSH_ENABLED -I/usr/include/qt4/QtDBus 
> -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -o CMakeFiles/qterm.dir/assistantclient.cpp.o -c 
> /«PKGBUILDDIR»/src/assistantclient.cpp
> [ 54%] Building CXX object src/CMakeFiles/qterm.dir/imageviewer.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/g++   -DDBUS_ENABLED 
> -DHAVE_CONFIG_H -DSCRIPT_ENABLED -DSSH_ENABLED -I/usr/include/qt4/QtDBus 
> -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -o CMakeFiles/qterm.dir/imageviewer.cpp.o -c 
> /«PKGBUILDDIR»/src/imageviewer.cpp
> [ 55%] Building CXX object 

Bug#817627: marked as done (poster: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:34:01 +
with message-id 
and subject line Bug#817627: fixed in poster 1:20050907-1.1
has caused the Debian Bug report #817627,
regarding poster: Removal of debhelper compat 4
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.)


-- 
817627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: poster
Severity: important
Usertags: compat-4-removal

Hi,

The package poster uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: poster
Source-Version: 1:20050907-1.1

We believe that the bug you reported is fixed in the latest version of
poster, 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 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated poster 
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, 12 Oct 2016 23:12:23 -0300
Source: poster
Binary: poster
Architecture: source
Version: 1:20050907-1.1
Distribution: unstable
Urgency: medium
Maintainer: Peter S Galbraith 
Changed-By: Joao Eriberto Mota Filho 
Description:
 poster - Create large posters out of PostScript pages
Closes: 817627
Changes:
 poster (1:20050907-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817627)
   * debian/compat: created.
   * debian/control:
   - Added the ${misc:Depends} variable.
   - Added the Homepage field.
   - Bumped Standards-Version to 3.9.8.
   - Removed the Section and Priority fields from binary block.
Checksums-Sha1:
 3cbfd149bbf02c66d59e3667b4a8d2b2fd1cc276 1629 poster_20050907-1.1.dsc
 900a19b5c9e8f64ab8cdb576586339b4605312f9 5307 poster_20050907-1.1.diff.gz
Checksums-Sha256:
 8fbea1ba9d96430f410777ba0779db563beeba1e5759780bf3aecd28a3f90650 1629 
poster_20050907-1.1.dsc
 05f78bed18e69395cf8c06e52099ba61e03e407ebbfee59b96e06b9cfbfcc02a 5307 
poster_20050907-1.1.diff.gz
Files:
 96d59ef42146952521e1c673e4ace3ed 1629 text optional poster_20050907-1.1.dsc
 6152ebcf183871c3b8fc38aa9d7eb902 5307 text optional poster_20050907-1.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX/u/0AAoJEN5juccE6+nvLPoQAKjtBVr2nmSz0yzVF9slB4sL
JE4LPqfpU2va8ZTslGTPQarCpliFuR45v8IQZ+ymlG7d0xtk0ndgBeDAgwaNF8RF
Z8FLaLu8BuV+w4HityjiJwhaxgvlWeh+FRi8Xt1kk19QdgAhpCrIqdLhG5Qn1Fy5
pULmbna5cpyHVdVYsh7OeQJrHTlFt/VFKsqVvm5GJlrrHLnqcftN5eLHIvK69xQA
cWhVpIxqtZMtW2NZRsPi5URs0DqglAQA5a226eNW5qecssO3flNnVIZAFMVzxCkF
Zf9usa1TnzC4BQcak2qnttNEF8XNLk6BaYF1kPuaxxQd0GvpMBTL5Mz8yXFLw1ml
tGImGDcXnUNn1HTcVhnMAZLpzti1dBMp0WdYSB5Om+pHttH55Nu19WkNYaT5S2En
Grs5eqNInGh3ktt/kR/Un5fD8PaBlXn+bNv+X4DAQxDb6nEtHQLmvDErjUaiJIrD
PsgpJ6B65yOQHVUvFjZIh48FG1hwdIKoM5si26YsZtqTvsAWa2Gl2q20Yie3KqQq
0gaFnABTS6bW/fMMceDPeHhciOtVySf+ZoC1HjiPGpsyVesnALVJnOUG5dkhFWfE
uMSb6OEG+8ZutJg8jd9sHKNWDH9gTRdPIypD3ZldsWVGs0RKP6bxDaGgVIbiSCao
aBwfKXmDCl+1ubTyW5Hj
=811p
-END PGP SIGNATURE End Message ---

Bug#817613: marked as done (outguess: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:31:33 +
with message-id 
and subject line Bug#817613: fixed in outguess 1:0.2-7.1
has caused the Debian Bug report #817613,
regarding outguess: Removal of debhelper compat 4
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.)


-- 
817613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: outguess
Severity: important
Usertags: compat-4-removal

Hi,

The package outguess uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: outguess
Source-Version: 1:0.2-7.1

We believe that the bug you reported is fixed in the latest version of
outguess, 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 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated outguess 
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: Thu, 13 Oct 2016 00:00:36 -0300
Source: outguess
Binary: outguess
Architecture: source
Version: 1:0.2-7.1
Distribution: unstable
Urgency: medium
Maintainer: anthony Gasperin 
Changed-By: Joao Eriberto Mota Filho 
Description:
 outguess   - Universal Steganographic tool
Closes: 817613
Changes:
 outguess (1:0.2-7.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817613)
   * debian/control:
   - Added the ${misc:Depends} variable.
   - Bumped Standards-Version to 3.9.8.
Checksums-Sha1:
 964c9722d3ce27bfc33568aad7d5c14e5e8254c0 1613 outguess_0.2-7.1.dsc
 5403aa76607c27a341cf0604de3d4cf99f9c2dca 3762 outguess_0.2-7.1.diff.gz
Checksums-Sha256:
 49afb1a85ea8d9c20e975cc94320969ce3564ed8c59073cd254aa048c703022c 1613 
outguess_0.2-7.1.dsc
 71c81c48eb97cf7e8361e963e03ed20b31940301c121b995803a314e170a57eb 3762 
outguess_0.2-7.1.diff.gz
Files:
 7cbdcba8e083fda8ace9e9e9d3980ddd 1613 utils optional outguess_0.2-7.1.dsc
 31b44fb0a3c0c140e85c0c10e7e37830 3762 utils optional outguess_0.2-7.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIbBAEBCAAGBQJX/vx4AAoJEN5juccE6+nvJPYP90JwaS4K0iQeYdwhxgdck+Dm
KZ3iR5BU5CssJCofGCVD784SGexYAT1z/R6zxsoS421u1pQqaCQaFrvZBjEeHdeM
cf87jsKwgdjMM72x1yoWeeJYm9CjzkNpDvXfjL9BmvzElCpaTTsMdfb4DacOrBPE
/gAhgw8n3z8veC3OTlNrB/cuj5FX0Dh6H94iIZRGn2J0z5nPTujTKVaoFXMDO+8X
Q8cwBryyD6W4FvZPton6NhTDk+E9ZK9sPOd/MqTa6ieAo5FJHbzUyTzsL1DFxEBi
8ymu/y7CIssTX/4axaFRKZqopnGovXQEGt9AFFJQPeGMReVp6zNUNDIe7KofXYY6
25oUInrcase7qQIgxn6XaVeIvcLNlI166PG6RDKsGRoIXbYKD1FOK66/msQYJrsv
cqnvMPHGVA0FecUrSG6YgjtaGqgMmlomV6byA6H7ARhu3eP1HVyXturI2LMHMPqe
wc9lqIbWkR+6VLkzn/7MvFkqrU2PfgKT5nJVW/XnGpg+xQK/xejIg49dGoKBL86V
TrVxaiWb4fYIRZb1o9sD0z6H+kO1hYpR9LJubcZtmFW7y+JN4yW6UA+RgAOgGCjw
aknPq3CLImLpRc2HbHOuHlU++wwlzTiIUX7KVsIrRs/WYw3WKRiqCaKCgfQMBv8x
NNK9PJzy7x+86KO0OKs=
=Z3YL
-END PGP SIGNATURE End Message ---

Bug#824825: marked as done (liblxqt-l10n: fails to upgrade from 'sid' - trying to overwrite /usr/share/lxqt/translations/liblxqt/liblxqt_ar.qm)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:27:23 +
with message-id 
and subject line Bug#824825: fixed in lxqt-l10n 0.11.0-19-g717bd7e-4
has caused the Debian Bug report #824825,
regarding liblxqt-l10n: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/lxqt/translations/liblxqt/liblxqt_ar.qm
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.)


-- 
824825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblxqt-l10n
Version: 0.10.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
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 liblxqt-l10n.
  Preparing to unpack .../liblxqt-l10n_0.10.9-1_all.deb ...
  Unpacking liblxqt-l10n (0.10.9-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/liblxqt-l10n_0.10.9-1_all.deb (--unpack):
   trying to overwrite '/usr/share/lxqt/translations/liblxqt/liblxqt_ar.qm', 
which is also in package liblxqt0:amd64 0.10.0-5
  Processing triggers for fontconfig (2.11.0-6.4) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/liblxqt-l10n_0.10.9-1_all.deb


cheers,

Andreas


liblxqt0=0.10.0-5_liblxqt-l10n=0.10.9-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lxqt-l10n
Source-Version: 0.11.0-19-g717bd7e-4

We believe that the bug you reported is fixed in the latest version of
lxqt-l10n, 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 824...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alf Gaida  (supplier of updated lxqt-l10n 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: Sat, 22 Oct 2016 20:39:39 +0200
Source: lxqt-l10n
Binary: compton-conf-l10n libfm-qt-l10n liblxqt-l10n lximage-qt-l10n 
lxqt-about-l10n lxqt-admin-l10n lxqt-config-l10n lxqt-globalkeys-l10n 
lxqt-notificationd-l10n lxqt-openssh-askpass-l10n lxqt-panel-l10n 
lxqt-policykit-l10n lxqt-powermanagement-l10n lxqt-runner-l10n 
lxqt-session-l10n lxqt-sudo-l10n obconf-qt-l10n pavucontrol-qt-l10n 
pcmanfm-qt-l10n qterminal-l10n
Architecture: source
Version: 0.11.0-19-g717bd7e-4
Distribution: unstable
Urgency: medium
Maintainer: LXQt Packaging Team 
Changed-By: Alf Gaida 
Description:
 compton-conf-l10n - Language package for compton-conf
 libfm-qt-l10n - Language package for libfm-qt
 liblxqt-l10n - Language package for liblxqt
 lximage-qt-l10n - Language-package for lximage-qt
 lxqt-about-l10n - Language package for lxqt-about
 lxqt-admin-l10n - Language package for lxqt-admin
 lxqt-config-l10n - Language package for lxqt-config
 lxqt-globalkeys-l10n - Language package for lxqt-globalkeys
 lxqt-notificationd-l10n - Language package for lxqt-notificationd
 lxqt-openssh-askpass-l10n - Language package for lxqt-openssh-askpass
 lxqt-panel-l10n - Language package for lxqt-panel
 lxqt-policykit-l10n - Language package for lxqt-policykit
 lxqt-powermanagement-l10n - Language package for lxqt-powermanagement
 lxqt-runner-l10n - Language package for lxqt-runner
 lxqt-session-l10n - Language package for lxqt-session
 lxqt-sudo-l10n - Language package for lxqt-sudo
 obconf-qt-l10n - Language package for obconf-qt
 pavucontrol-qt-l10n - Language package for pavucontrol-qt
 pcmanfm-qt-l10n - Language package for pcmanfm-qt
 qterminal-l10n - Language package for qterminal
Closes: 824825
Changes:
 lxqt-l10n (0.11.0-19-g717bd7e-4) unstable; urgency=medium
 .
   * Re-Added merged changelog entries
   * Explicitly close #824825 which i had overseen (Closes: #824825)
   * Thanks Adrian Bunk for the advice (Close: #841721)
Checksums-Sha1:
 

Bug#841532: libgit2: FTBFS under some timezones (eg. GMT-14)

[Russell Sim]

Yeah, I totally agree it's an upstream bug, the bug exists in not only
this version but also the master branch so I can't backport a fix. 

I did have a quick look at the test code, and it's not obviously due to
that, so it must be related to how they store or retrieve the offset in
this case.

I'll leave this bug open until we have an actual fix. But I think that
preventing random failures from Debian build infrastructure is the best
I can do for the time being.

Thanks for adding the forwarded tag, I'm still learning and I forget
these things sometimes.

Chris Lamb  writes:

> forwarded 841532 https://github.com/libgit2/libgit2/issues/3970
> thanks
>
> Russell Sim wrote:
>
>> I have forwarded this bug report upstream
>> https://github.com/libgit2/libgit2/issues/3970 in the mean time I'll add
>> a fix to the existing package to force tests to run in GMT timezone.
>
> Be careful; it could mean that you are masking underlying bugs by forcing
> the timezone - the code (outside of the tests) itself could be buggy!
>
>
> Regards,

-- 
Cheers,
Russell

Bug#841442: marked as done (lintian: FTBFS: fail tests::shared-libs-non-pic-i386)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:21:13 +
with message-id 
and subject line Bug#841442: fixed in lintian 2.5.49
has caused the Debian Bug report #841442,
regarding lintian: FTBFS: fail tests::shared-libs-non-pic-i386
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.)


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

Source: lintian
Version: 2.5.48
Severity: serious
Justification: fails to build from source

lintian FTBFS on i386:
| tests::shared-libs-non-pic-i386: diff -u 
t/tests/shared-libs-non-pic-i386/tags 
/home/jwilk/lintian-2.5.48/debian/test-out/tests/shared-libs-non-pic-i386/tags.shared-libs-non-pic-i386
| --- t/tests/shared-libs-non-pic-i386/tags 2015-10-05 20:08:38.0 
+
| +++ 
/home/jwilk/lintian-2.5.48/debian/test-out/tests/shared-libs-non-pic-i386/tags.shared-libs-non-pic-i386
   2016-10-20 17:45:44.831884940 +
| @@ -1 +0,0 @@
| -E: libbaz3-1: shlib-with-non-pic-code usr/lib/libbaz3.so.1.0.3b
| fail tests::shared-libs-non-pic-i386: output differs!
[...]
| Failed tests (1)
| tests::shared-libs-non-pic-i386
| debian/rules:48: recipe for target 'runtests' failed

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.49

We believe that the bug you reported is fixed in the latest version of
lintian, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated lintian 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, 22 Oct 2016 13:42:28 +
Source: lintian
Binary: lintian
Architecture: source
Version: 2.5.49
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Niels Thykier 
Description:
 lintian- Debian package checker
Closes: 731987 839874 840009 841000 841356 841442 841455
Changes:
 lintian (2.5.49) unstable; urgency=medium
 .
   * Summary of tag changes:
 + Added:
   - homepage-for-bioconductor-package-not-canonical
 .
   * checks/debhelper.desc:
 + [CL] Drop double leading spaces in includes-maint-script-parameters
   paragraph that was causing indentation when rendered on lintian.d.o.
   * checks/fields.{pm,desc}:
 + [NT] Apply patch from Dylan Aïssi to tag non-canonical uses of
   the bioconductor homepage in the Homepage field.  (Closes: #839874)
 + [JW] Apply patch from Dylan Aïssi to tag r-other packages not in
   section "gnu-r".  (Closes: #841455)
   * checks/init.d.pm:
 + [JW] Don't require version constraint for lsb-base dependencies.
   The needed version has been available for many stable releases.
   * checks/shared-libs.pm:
 + [JW] Don't complain about executable bit for ld.so shipped in
   multi-arch directories.
 + [JW] Don't complain about missing SONAME for position-independent
   executables.  Thanks to Reuben Thomas for the bug report.
   (Closes: #731987)
 + [JW] Check for PT_GNU_STACK existence on all architectures.
   * checks/source-copyright.pm:
 + [RA, JW] Fix handling punctuation characters in license expressions
   in machine-readable copyright files.  (Closes: #841356)
   * checks/watch-file.pm:
 + [JW] Assume that watch files containing the pgpmode option (different
   than "none") verify upstream signature.  Thanks to Robert Luberda for
   the bug report.  (Closes: #841000)
 .
   * data/cruft/non-distributable-files:
 + [BR] Add some rapidjson files.
   * data/debhelper/compat-level:
 + [NT] Bump the deprecated debhelper compat level to match the one
   in debhelper.
   * data/files/privacy-breaker-tag-attr:
 + [BR] Apply patch from Frederic Bonnard detecting audio tags.
   (Closes: #840009)
   * data/spelling/corrections*:
 + [JW, PW] Add more corrections.
 .
   * lib/Lintian/Unpacker.pm:
 + [NT] Use the new "do_fork()" sub to ensure works do not inherit
   the default signal 

Bug#841625: marked as done (gupnp-tools: FTBFS: playlist-treeview.h:35:34: error: unknown type name 'GUPnPDeviceProxy')

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:02:04 +
with message-id 
and subject line Bug#841625: fixed in gupnp-tools 0.8.12-2
has caused the Debian Bug report #841625,
regarding gupnp-tools: FTBFS: playlist-treeview.h:35:34: error: unknown type 
name 'GUPnPDeviceProxy'
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.)


-- 
841625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gupnp-tools
Version: 0.8.12-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../..   -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
> -I/usr/include/gupnp-1.0 -I/usr/include/gssdp-1.0 -I/usr/include/libsoup-2.4 
> -I/usr/include/libxml2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
> -I/usr/include/gupnp-av-1.0 -pthread -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/gtksourceview-3.0 -I/usr/include/libxml2 
> -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../.. 
> -DDATA_DIR='"/usr/share/gupnp-tools"' -I../../src/common 
> -DLOCALEDIR='"/usr/share/locale"' -fno-strict-aliasing -Wall -Wextra -Wundef 
> -Wnested-externs -Wwrite-strings -Wpointer-arith -Wmissing-declarations 
> -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls 
> -Wno-unused-parameter -Wno-missing-field-initializers 
> -Wdeclaration-after-statement -Wformat=2 -Wold-style-definition -Wcast-align 
> -Wformat-nonliteral -Wformat-security -Wsign-compare -Wstrict-aliasing 
> -Wshadow -Winline -Wpacked -Wmissing-format-attribute -Wmissing-noreturn 
> -Winit-self -Wmissing-include-dirs -Wunused-but-set-variable -Warray-bounds 
> -Wimplicit-function-declaration -Wreturn-type -Wswitch-enum -Wswitch-default 
> -Wno-error=unused-parameter -Wno-error=missing-field-initializers -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -g -O0 -Wall -c -o playlist-treeview.o 
> playlist-treeview.c
> In file included from playlist-treeview.c:30:0:
> playlist-treeview.h:35:34: error: unknown type name 'GUPnPDeviceProxy'
>  add_media_server(GUPnPDeviceProxy   *proxy);
>   ^~~~
> playlist-treeview.h:38:34: error: unknown type name 'GUPnPDeviceProxy'
>  remove_media_server (GUPnPDeviceProxy   *proxy);
>   ^~~~
> playlist-treeview.c:1027:1: warning: no previous prototype for 
> 'add_media_server' [-Wmissing-prototypes]
>  add_media_server (GUPnPDeviceProxy *proxy)
>  ^~~~
> playlist-treeview.c:1055:1: warning: no previous prototype for 
> 'remove_media_server' [-Wmissing-prototypes]
>  remove_media_server (GUPnPDeviceProxy *proxy)
>  ^~~
> Makefile:508: recipe for target 'playlist-treeview.o' failed
> make[5]: *** [playlist-treeview.o] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly 

Bug#837568: marked as done (libctl-dev: Please build libctlgeom.a with -fPIC)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 23:10:56 +
with message-id 
and subject line Bug#837568: fixed in libctl 3.2.2-3
has caused the Debian Bug report #837568,
regarding libctl-dev: Please build libctlgeom.a with -fPIC
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.)


-- 
837568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libctl-dev
Version: 3.2.2-2
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: makes mpb FTBFS with extra hardening
Affects: mpb

Dear Maintainers,

During a rebuild of all packages in sid, mpb
failed to build on amd64 with patched GCC and dpkg. The root
cause seems to be that libctlgeom.a is shipped as a non-PIC library.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64 (and selected architectures).

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part of mpb's build log:
...
libtool: link: mpicc -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -W
error=format-security -Wall -W -Wbad-function-cast -Wcast-qual
-Wpointer-arith -Wcast-align -pedantic
-Wl,-z -Wl,relro -Wl,-z -Wl,now
-Wl,-L/usr/lib/x86_64-linux-gnu/hdf5/openmpi -o normal_vectors normal_
vectors.o  -lctlgeom ../src/.libs/libmpb.a
-L/usr/lib/gcc/x86_64-linux-gnu/6 -L/usr/lib/gcc/x86_64-lin
ux-gnu/6/../../../x86_64-linux-gnu
-L/usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib -L/lib/x86_64-lin
ux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib
-L/usr/lib/gcc/x86_64-linux-gnu/6/.
./../.. -L/usr/lib/x86_64-linux-gnu/hdf5/openmpi -lctl -lguile-2.0 -lgc
-lhdf5 -lz -llapack -lblas -lf
ftw3 -lgfortran -lm -lquadmath
/usr/bin/ld:
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libctlgeom.a(geom.o):
relocation R_X86_64_32 against `.rodata.str1.1' can not be used when
making a shared object; recompile with -fPIC
...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/mpb_1.5-2_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Source: libctl
Source-Version: 3.2.2-3

We believe that the bug you reported is fixed in the latest version of
libctl, 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 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated libctl 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: Sat, 22 Oct 2016 12:00:26 +0200
Source: libctl
Binary: libctl-dev libctl5 libctl-doc
Architecture: source amd64 all
Version: 3.2.2-3
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 libctl-dev - library for flexible control files, development version
 libctl-doc - library for flexible control files, documentation
 libctl5- library for flexible control files
Closes: 837568
Changes:
 libctl (3.2.2-3) unstable; urgency=medium
 .
   * debian/copyright: reorder to calm lintian
   * debian/control: add ${misc:Pre-Depends} instead of multiarch-suppport
   * debian/control: bump standard to 3.9.8 (no change)
   * debian/rules: build everything with -fPIC (Closes: #837568)
   * remove false positive overrides libctl-doc.lintian-overrides
Checksums-Sha1:
 78fa870fa890ddd4a8d81326f3a7ebb95673cca9 1997 libctl_3.2.2-3.dsc
 d7f860313d5cc226c51f868bbe9bb930d143ab9c 505796 libctl_3.2.2.orig.tar.gz
 b7b4a2458056ec3966a7071a07605a9d8482b663 6744 libctl_3.2.2-3.debian.tar.xz
 c405fbf5b641900d7ec364736a8fb66fc37ba488 90986 libctl-dev_3.2.2-3_amd64.deb
 dd28563f83a5a19c5b81cf52d883e70839b611cf 76524 libctl-doc_3.2.2-3_all.deb
 26719c5703d4826949fd0f7abd039482aead6f3f 74204 libctl5-dbgsym_3.2.2-3_amd64.deb
 4d7e78f3a9b6cd77d284fdc57c28eca75d2f83cc 100070 libctl5_3.2.2-3_amd64.deb
Checksums-Sha256:
 d9314af124b1a768593b43114a6a19731a3e017b616bc6984cbc5aa4a386c8b3 1997 
libctl_3.2.2-3.dsc
 

Bug#841707: marked as done (eximdoc4: FTBFS with bash as /bin/sh)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 22:44:56 +
with message-id 
and subject line Bug#841707: fixed in eximdoc4 4.87-2
has caused the Debian Bug report #841707,
regarding eximdoc4: FTBFS with bash as /bin/sh
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.)


-- 
841707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eximdoc4
Version: 4.87-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,

eximdoc4 fails to build from source in unstable/amd64 when 
/bin/sh is set to bash:

  cd build-tree/html/exim-html-*/doc/html/spec_html/ && \
find -name 'ch??.html' -or -name 'filter_ch??.html' | \
while read i ; do s=`readlink "$i" | sed -e 's:.*/::'` ; \
rm "$i" ; ln -vs "$s" "$i" ; done
  /bin/sh: line 0: cd: too many arguments

The full build log is attached.


Regards,

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


eximdoc4.4.87-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: eximdoc4
Source-Version: 4.87-2

We believe that the bug you reported is fixed in the latest version of
eximdoc4, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated eximdoc4 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: Sat, 22 Oct 2016 17:51:19 +0200
Source: eximdoc4
Binary: exim4-doc-info exim4-doc-html
Architecture: source
Version: 4.87-2
Distribution: unstable
Urgency: medium
Maintainer: Exim4 Maintainers 
Changed-By: Andreas Metzler 
Closes: 841707
Description: 
 exim4-doc-html - documentation for the Exim MTA (v4) in html format
 exim4-doc-info - documentation for the Exim MTA (v4) in info format
Changes:
 eximdoc4 (4.87-2) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * Fix FTBFS with bash as /bin/sh. Closes: #841707
Checksums-Sha1: 
 876f2fb7c936c65e39a2cf38ff71ce97f5fd267b 2149 eximdoc4_4.87-2.dsc
 66d3961314ef2005059838fefdc7b7d814cc09b0 8924 eximdoc4_4.87-2.debian.tar.xz
Checksums-Sha256: 
 fc07f613eeffd0f03cad9b56396988272f65bd8b218f28dc718836eaba689955 2149 
eximdoc4_4.87-2.dsc
 fedffa8f312132802278531a507155b9f0a2fde9425fec12490fa8fb15ddcbab 8924 
eximdoc4_4.87-2.debian.tar.xz
Files: 
 f483c29d96b98e13c66f2db7089fa199 2149 doc optional eximdoc4_4.87-2.dsc
 e4e0110278d29ce5a96c176d6a869d85 8924 doc optional 
eximdoc4_4.87-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYC4tvAAoJEKVPAYVDghSE76oQAJtAwWCadTgJw4Z2HYHyqgqI
oU03hE6J7N+VOehIadgx3SKGSRugshkEKO+wTHevjt9zUxHVwZXL+DPSJxWYpmMF
Q2Z/ilFxhv6QL7gukXRd82BbbpwKPgA0adaJXSvkc8aaUVYrQF/1RJwS4EV6L7iU
5hBxcFTZ0LzYY7mwJ7ZU1Ua27v/OI6wfFxVW3/iJH8QQ9JPgJn0hhgxJAOFUrNEu
TCKbLY1tikU54OjdCaMvcMUS4Usi31EwtEkTvcUsxXfw7pYUEvUEPn0c3dD5eZ1y
eRiSBOijvqJacvSw5lOyI6C2A4Khj8V6gCO+kYd1z4J5GOi8dQs+0Yl/r2w157W1
RqgHY8H304AdFsHeEIw7tuye1CunMePzE6tqdo7BFh8q6xXeeYsYWul07QBXKYr9
oK4R57YU1gkRBnedU4etR13wZiVIPGXxuT1g8zp3pnvmmX2wlrKdaRcTeR4T+cf2
WaoPu8qAi8uwmLg2Qx9hWqtpERkEAcjvKBSjtA+W7szwcSP04cwQJJAdNfUS3i1t
EEEkZKINb8IlZFMMlDMOGjIJgwq2dX+LR/5nETAGuSZAFXnAiWeifhXZrKR1o3oy
/KrlOyZW4hosALmqoKmGL58bvbqX1RCH5/h8UG9pd99lRCyB5MMpSxQsBFcI4BGI
LiKkeh/tJEytHAKgXXok
=2swM
-END PGP SIGNATURE End Message ---

Bug#841082: marked as done (epiphany-browser: bump dependency on epiphany-browser-data)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 22:44:29 +
with message-id 
and subject line Bug#841082: fixed in epiphany-browser 3.22.1-2
has caused the Debian Bug report #841082,
regarding epiphany-browser: bump dependency on epiphany-browser-data
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.)


-- 
841082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: epiphany-browser
Version: 3.22.1-1
Severity: important

Dear Maintainer,

   * What led up to the situation?

  Visit https://davidwalsh.name/demo/notifications-api.php and click on 
"Show a notification" button

   * What was the outcome of this action?

 The browser crashed. Launching it from the terminal allowed me to see this 
error.

 (epiphany:760): GLib-GIO-ERROR **: Settings schema 
'org.gnome.Epiphany.host' is not installed

 That's making the UI process crash as seen in this backtrace (no debug 
symbols but good enough)

 Thread 1 "epiphany" received signal SIGTRAP, Trace/breakpoint trap.
 0x70c36241 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 (gdb) bt
 #0  0x70c36241 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 #1  0x70c37297 in g_log_default_handler () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #2  0x555d53e2 in ?? ()
 #3  0x70c375a4 in g_logv () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #4  0x70c377af in g_log () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #5  0x712542ef in ?? () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 #6  0x70f0e583 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #7  0x70f1010e in g_object_new_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #8  0x70f103b1 in g_object_new () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #9  0x7125559a in g_settings_new_with_backend_and_path () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 #10 0x555bc760 in ?? ()
 #11 0x555bc9e9 in 
ephy_hosts_manager_get_notifications_permission_for_address ()
 #12 0x555beed5 in ?? ()

   * What outcome did you expect instead?

 Browser should show a permission request dialog.

 This is working fine on the MiniBrowser included in the package, so it's 
likely a configuration issue.


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

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

Versions of packages epiphany-browser depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.10.10-1
ii  dbus-x11 [dbus-session-bus]   1.10.12-1
ii  epiphany-browser-data 3.22.0-1
ii  gsettings-desktop-schemas 3.22.0-1
ii  iso-codes 3.67-1
ii  libavahi-client3  0.6.32-1
ii  libavahi-common3  0.6.32-1
ii  libavahi-gobject0 0.6.32-1
ii  libc6 2.23-5
ii  libcairo2 1.14.6-1+b1
ii  libgcr-base-3-1   3.20.0-2
ii  libgcr-ui-3-1 3.20.0-2
ii  libgdk-pixbuf2.0-02.35.5-1
ii  libglib2.0-0  2.50.0-1
ii  libgnome-desktop-3-12 3.21.90-3
ii  libgtk-3-03.22.0-1
ii  libjavascriptcoregtk-4.0-18   2.14.1-1
ii  libnotify40.7.6-2
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libsecret-1-0 0.18.5-2
ii  libsoup2.4-1  2.54.0.1-2
ii  libsqlite3-0  3.12.2-1
ii  libwebkit2gtk-4.0-37  2.14.1-1
ii  libx11-6  2:1.6.3-1
ii  libxml2   2.9.3+dfsg1-1
ii  libxslt1.11.1.29-1

Versions of packages epiphany-browser recommends:
ii  browser-plugin-evince  3.21.4-1
ii  ca-certificates20160104
ii  evince 

Bug#817354: marked as done (aspell-br: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 22:32:11 +
with message-id 
and subject line Bug#817354: fixed in aspell-br 0.50-2-6.1
has caused the Debian Bug report #817354,
regarding aspell-br: Removal of debhelper compat 4
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.)


-- 
817354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aspell-br
Severity: important
Usertags: compat-4-removal

Hi,

The package aspell-br uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: aspell-br
Source-Version: 0.50-2-6.1

We believe that the bug you reported is fixed in the latest version of
aspell-br, 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 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated aspell-br 
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, 12 Oct 2016 22:03:34 -0300
Source: aspell-br
Binary: aspell-br
Architecture: source
Version: 0.50-2-6.1
Distribution: unstable
Urgency: medium
Maintainer: Brian Nelson 
Changed-By: Joao Eriberto Mota Filho 
Description:
 aspell-br  - Breton dictionary for GNU Aspell
Closes: 817354
Changes:
 aspell-br (0.50-2-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817354)
   * debian/control:
   - Added the ${misc:Depends} variable.
   - Added the Homepage field.
   - Bumped Standards-Version to 3.9.8.
   * debian/watch: created.
Checksums-Sha1:
 7433cfc3312fea01d43ea019e8c4375182fe664e 1703 aspell-br_0.50-2-6.1.dsc
 30d4fdfc9dc3f7043b77f4dfda7fca72434f6425 1947 aspell-br_0.50-2-6.1.diff.gz
Checksums-Sha256:
 2faef4ed21c0079c0445c6ba17599e4b17cbdd24347d854f2c044589613fedb2 1703 
aspell-br_0.50-2-6.1.dsc
 b71c2329d791ed52e5eb2fe197b33952269006ae8e497f2f5fc2b5aaa8378f08 1947 
aspell-br_0.50-2-6.1.diff.gz
Files:
 d889ab045a84fc6151c298a9abc68567 1703 text optional aspell-br_0.50-2-6.1.dsc
 13a06b9232cd363e28fe6338fcf99ff3 1947 text optional 
aspell-br_0.50-2-6.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX/vfEAAoJEN5juccE6+nvThkP/Ruobu5FwWGxMzgDvl+4W39N
oRG5lG2I5QEFVWJvxLLG2F0FiQ6SluHtZ4O6jsELBsqAejBexDA5wphUFjNfLtUg
pEzB/y5FSCRERp9jQLo5zO/xe4XciW+uH8FPQvpnQx9hv/NhC0od03QzTtspNqQy
SJ/SSrdp/3k5V+scBDyehisgcwMmOSDdc/btUYDnLNIiDgllfmroVrTlGD/mHf5M
qTp74BvFK2wSb3jSwhjARFhqxoxdJI184PTH9WnoLk7sA1NZ1j1liM92KVB/PhvF
rj5gvz3UQphB41yx8JDDAPK1SfTRVcE40177drfn2t3EUV0lyFKxUFBNZTYpx6/d
rAhHEMYpIc7++Wy3r+6w/r7fQRinsoKDaszmiAGu37ItoaWeEmtzMQqht/vQ95D0
BY4T4962P16BlOelSR9hqStTFa7YZgCPmCdvF0QGDpZaiz3GpO2/IARXGPlEAuRd
MCaTzmWGi40yTTburzyfNyt25DYdwzsagAp4MFsIEFBT7kVuzaCsrCe7nITdrA9t
5hziMCm6zXemEyD0RchEI4A2eFMn4SJHgLjl4oqsJtCIGLchvo03zGn5euRHfGcI
lYEDUZm8xyILyxHiRId2gcQdX3wlPGa4AnAGEVPWgqlCM69HwSCsw5pS5Ex1jX6q
NivpVwBCjvXOSvzU9gbw
=thgV
-END PGP SIGNATURE End Message ---

Bug#841064: marked as done (awscli: FTBFS: ImportError: No module named 's3transfer')

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 22:32:29 +
with message-id 
and subject line Bug#841064: fixed in awscli 1.11.7-2
has caused the Debian Bug report #841064,
regarding awscli: FTBFS: ImportError: No module named 's3transfer'
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.)


-- 
841064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: awscli
Version: 1.11.2-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,

awscli fails to build from source in unstable/amd64:

  […]

  copying awscli/examples/cloudfront/list-invalidations.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/create-distribution.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/list-distributions.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/get-distribution.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/create-invalidation.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/get-distribution-config.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/update-distribution.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/get-invalidation.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  creating 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/upload-part.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/head-bucket.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/get-bucket-lifecycle-configuration.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/list-object-versions.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/delete-bucket-tagging.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/delete-bucket-lifecycle.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/put-bucket-versioning.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/get-object.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/abort-multipart-upload.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/put-bucket-cors.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/get-bucket-policy.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/get-object-torrent.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api

Bug#841867: dgit cannot cope with some patches because it uses gbp-pq

[Ian Jackson]

Package: dgit
Version: 2.6
Severity: serious

gbp pq cannot cope with all patches that dpkg-source can, because it
uses git-apply and git-apply is not very compatible.

At the moment, this means that `dgit clone glibc' fails:

  gbp:error: Failed to apply
  
'/home/ian/junk/d/glibc/.git/dgit/unpack/glibc-2.19/debian/patches/any/submitted-nl_langinfo-static.diff':
  Error running git apply: error: dev/null: does not exist in index

I think I need to switch to using repeated dpkg-source --before-build.
This means I need to reimplement gbp pq's metadata processing
algorithm :-/.

Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*

[Pietro Battiston]

Package: ardour
Version: 1:5.4.0~dfsg-1
Severity: grave

Ardour 1:4.7~dfsg-2 works great. If instead I upgrade to 1:5.3~dfsg-1 (current
unstable) or 1:5.4.0~dfsg-1 (current testing), I get a segfault when I try to
load any project.

I am attaching a gdb run (from 1:5.4.0~dfsg-1).



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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ardour depends on:
ii  ardour-data   1:4.2~dfsg-5
ii  jackd 5
ii  libarchive13  3.2.1-4
ii  libasound21.0.29-1
ii  libatk1.0-0   2.18.0-1
ii  libatkmm-1.6-1v5  2.24.2-1
ii  libaubio4 0.4.1-2+b3
ii  libbluetooth3 5.33-1
ii  libc6 2.24-3
ii  libcairo2 1.14.2-2
ii  libcairomm-1.0-1v51.12.0-1
ii  libcurl3-gnutls   7.45.0-1
ii  libcwiid1 0.6.00+svn201-3.2
ii  libfftw3-single3  3.3.5-1
ii  libflac8  1.3.1-4
ii  libfluidsynth11.1.6-3
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6-2
ii  libgcc1   1:5.2.1-22
ii  libgdk-pixbuf2.0-02.36.0-1
ii  libglib2.0-0  2.50.0-1
ii  libglibmm-2.4-1v5 2.50.0-1
ii  libgtk2.0-0   2.24.28-1
ii  libgtkmm-2.4-1v5  1:2.24.5-1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1
ii  liblilv-0-0   0.24.0~dfsg0-1
ii  liblo70.28-5
ii  liblrdf0  0.4.0-5
ii  libltc11  1.1.4-1
ii  libogg0   1.3.2-1
ii  libpango-1.0-01.38.0-3
ii  libpangocairo-1.0-0   1.38.0-3
ii  libpangoft2-1.0-0 1.38.0-3
ii  libpangomm-1.4-1v52.40.1-3
ii  librubberband21.8.1-6+b1
ii  libsamplerate00.1.8-8
ii  libserd-0-0   0.24.0~dfsg0-1
ii  libsigc++-2.0-0v5 2.10.0-1
ii  libsndfile1   1.0.25-9.1
ii  libsord-0-0   0.16.0~dfsg0-1
ii  libsratom-0-0 0.4.6~dfsg0-1
ii  libstdc++66.2.0-6
ii  libsuil-0-0   0.8.2~dfsg0-1
ii  libtag1v5 1.9.1-2.4
ii  libvamp-hostsdk3v52.6~repack0-2
ii  libvamp-sdk2v52.6~repack0-2
ii  libx11-6  2:1.6.3-1
ii  libxml2   2.9.2+zdfsg1-4

Versions of packages ardour recommends:
ii  ardour-video-timeline   1:5.4.0~dfsg-1
ii  chromium [www-browser]  50.0.2661.94-1
ii  epiphany-browser [www-browser]  3.18.0-1+b1
ii  firefox-esr [www-browser]   45.0.1esr-1
ii  iceweasel   45.3.0esr-1
ii  links [www-browser] 2.12-1
ii  w3m [www-browser]   0.5.3-25

Versions of packages ardour suggests:
pn  jamin 
ii  qjackctl  0.4.0-1

-- no debconf information
(gdb) r
Starting program: /usr/lib/ardour5/ardour-5.4.0 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Cannot find ArdourMono TrueType font
bind txt domain [gtk2_ardour5] to /usr/share/ardour5/locale
Ardour5.4.0 (built using 1:5.4.0~dfsg-1 and GCC version 6.2.0 20161010)
ardour: [INFO]: Your system is configured to limit Ardour to only 65.536 open files
ardour: [INFO]: Loading system configuration file /etc/ardour5/system_config
ardour: [INFO]: Loading user configuration file /home/pietro/.config/ardour5/config
[New Thread 0x7fffd942d700 (LWP 27425)]
ardour: [INFO]: CPU vendor: GenuineIntel
ardour: [INFO]: AVX-capable processor
ardour: [INFO]: CPU brand: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
ardour: [INFO]: Using SSE optimized routines
[New Thread 0x7fffd8c2c700 (LWP 27426)]
[New Thread 0x7fffd3fff700 (LWP 27427)]
[New Thread 0x7fffd37fe700 (LWP 27428)]
[New Thread 0x7fffd196e700 (LWP 27429)]
[New Thread 0x7fffd116d700 (LWP 27430)]
Cannot xinstall SIGPIPE error handler
ardour: [INFO]: Loading default ui configuration file /etc/ardour5/default_ui_config
ardour: [INFO]: Loading user ui configuration file /home/pietro/.config/ardour5/ui_config
ardour: [WARNING]: Color file for dark-ardour not found along /home/pietro/.config/ardour5/themes:/usr/share/ardour5/themes
ardour: [INFO]: Loading ui configuration file /etc/ardour5/clearlooks.rc
/etc/ardour5/clearlooks.rc:9: Invalid symbolic 

Bug#841548: marked as done (autopkgtest: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 21:28:50 +
with message-id 
and subject line Bug#841548: fixed in wand 0.4.3-1
has caused the Debian Bug report #841548,
regarding autopkgtest: FTBFS: Tests failures
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.)


-- 
841548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: autopkgtest
Version: 4.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> autopkgtest: DBG: no need to restore click AppArmor profiles
> autopkgtest: DBG: needs_reset, previously=False, requested by run_tests() 
> line 169
> autopkgtest [01:20:21]:  summary
> tFAIL non-zero exit status 1
> autopkgtest: DBG: testbed stop
> autopkgtest: DBG: testbed close, scratch=/tmp/autopkgtest.2SwpBj
> autopkgtest: DBG: sending command to testbed: close
> autopkgtest: DBG: got reply from testbed: ok
> autopkgtest: DBG: sending command to testbed: quit
> 
> 
> --
> Ran 48 tests in 92.641s
> 
> FAILED (failures=1, skipped=2)
> debian/rules:38: recipe for target 'override_dh_auto_test' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/autopkgtest_4.1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: wand
Source-Version: 0.4.3-1

We believe that the bug you reported is fixed in the latest version of
wand, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Changwoo Ryu  (supplier of updated wand 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, 22 Oct 2016 18:59:14 +0900
Source: wand
Binary: python-wand python3-wand pypy-wand wand-doc
Architecture: source
Version: 0.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Changwoo Ryu 
Changed-By: Changwoo Ryu 
Description:
 pypy-wand  - Python interface for ImageMagick library (PyPy build)
 python-wand - Python interface for ImageMagick library (Python 2 build)
 python3-wand - Python interface for ImageMagick library (Python 3 build)
 wand-doc   - Python interface for ImageMagick library - documentation
Closes: 841548
Changes:
 wand (0.4.3-1) unstable; urgency=medium
 .
   * New upstream release
   * Fix TypeError on ImageMagick 6.9.6.2 (Closes: #841548)
   * Standards-Version: 3.9.8
   * Fix lintian errors
 - debian/control: Use https protocol for Vcs-* fields
 - debian/copyright: Fix the copyright format
   * debian/gbp.conf: upstream-0.4 branch for upstream
Checksums-Sha1:
 10577934afc7f57c13d8d409a2bbc2782876b31d 2117 wand_0.4.3-1.dsc
 deb41458ba578ccea46bf8fb7431987ab0debc12 6662464 wand_0.4.3.orig.tar.gz
 abb4fda182eadb8a8a89372bbcfe62b631cba34e 9908 wand_0.4.3-1.debian.tar.xz
Checksums-Sha256:
 61df0ac13524b5dc07c1230e384d355e7054f34f2f801eed3c508e27e16b5635 2117 
wand_0.4.3-1.dsc
 

Bug#841653: marked as done (Importing wand.image fails)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 21:28:50 +
with message-id 
and subject line Bug#841548: fixed in wand 0.4.3-1
has caused the Debian Bug report #841548,
regarding Importing wand.image fails
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.)


-- 
841548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-wand
Severity: serious
Version: 0.3.9-1

Hello,

In current sid, at least in a minimal chroot, this module is broken:

  # apt-get install -y python3-wand
  # python3 -c 'import wand.image'
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/wand/image.py", line 21, in 
  from .color import Color
File "/usr/lib/python3/dist-packages/wand/color.py", line 12, in 
  from .version import QUANTUM_DEPTH
File "/usr/lib/python3/dist-packages/wand/version.py", line 95, in 
  *map(int, MAGICK_RELEASE_DATE_STRING.split('-')))
  TypeError: Required argument 'month' (pos 2) not found

This must have happened relatively recently. This is spotted by
autopkgtest's testsuite, and Lukas just reported that it's now failing
(#841548). It was still working on October 7 when I did the last
upload.

Thanks for considering,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
--- End Message ---
--- Begin Message ---
Source: wand
Source-Version: 0.4.3-1

We believe that the bug you reported is fixed in the latest version of
wand, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Changwoo Ryu  (supplier of updated wand 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, 22 Oct 2016 18:59:14 +0900
Source: wand
Binary: python-wand python3-wand pypy-wand wand-doc
Architecture: source
Version: 0.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Changwoo Ryu 
Changed-By: Changwoo Ryu 
Description:
 pypy-wand  - Python interface for ImageMagick library (PyPy build)
 python-wand - Python interface for ImageMagick library (Python 2 build)
 python3-wand - Python interface for ImageMagick library (Python 3 build)
 wand-doc   - Python interface for ImageMagick library - documentation
Closes: 841548
Changes:
 wand (0.4.3-1) unstable; urgency=medium
 .
   * New upstream release
   * Fix TypeError on ImageMagick 6.9.6.2 (Closes: #841548)
   * Standards-Version: 3.9.8
   * Fix lintian errors
 - debian/control: Use https protocol for Vcs-* fields
 - debian/copyright: Fix the copyright format
   * debian/gbp.conf: upstream-0.4 branch for upstream
Checksums-Sha1:
 10577934afc7f57c13d8d409a2bbc2782876b31d 2117 wand_0.4.3-1.dsc
 deb41458ba578ccea46bf8fb7431987ab0debc12 6662464 wand_0.4.3.orig.tar.gz
 abb4fda182eadb8a8a89372bbcfe62b631cba34e 9908 wand_0.4.3-1.debian.tar.xz
Checksums-Sha256:
 61df0ac13524b5dc07c1230e384d355e7054f34f2f801eed3c508e27e16b5635 2117 
wand_0.4.3-1.dsc
 d10139a413f03ab0b9fe548919fadbd671ba4e24f6289124aa45e210c14fb7fd 6662464 
wand_0.4.3.orig.tar.gz
 a97458ecabc5c17f0f2228f3f67481327ac302dd0bf1380b7e8f2c510e64f78a 9908 
wand_0.4.3-1.debian.tar.xz
Files:
 b7e90c1b197cb7e83acce119dabc4502 2117 python optional wand_0.4.3-1.dsc
 324de1bf3ef7970da517cc0d79690fa3 6662464 python optional wand_0.4.3.orig.tar.gz
 1e9897f80ce08917e8af509fcc22bbbf 9908 python optional 
wand_0.4.3-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYC0sIAAoJEPNPCXROn13ZqnkQAMZMdxljxG/4yHLh5UHomDXF
S0Te2QzSLga3crIvk7bE0C9ACBTPJSU4seyuWPIoeTlwlSnzOCdJ0lD1sPO7DRwA
5bojxgFUWPYYUziX/w0UinIfk+sLB6GsSreBJvctr+syPTVpCm3RLvS3dNzFipAW
RrRDVbJBYkrpfiJ9qNkhi7++F9GU0gG7YkkAKDnxqzQpPP5DhmhBq0XblTRRRACt
0WYyq2BhS1FCFyBZ1kZns6pwvjc94kKAJWLAnIaN9G60MmMB/AiWnu20qCCJf/MC
G/Xx8vCi9V57O0YWBFJ1SR+ZJESvW7TLeD9nxcdUTWm3xSzJ6glaRgYPnW/jjnKR
39drBYxtcLS/ebBE2KD6zzM22pVGe0fbTaKGu1fdTLN6SEdrIs4UmAVhWh5Qkchl

Bug#839181: marked as done (transmission-remote-gtk: FTBFS: Option release requires an argument [pod2man --release=""] )

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 21:28:06 +
with message-id 
and subject line Bug#839181: fixed in transmission-remote-gtk 1.3.1-1
has caused the Debian Bug report #839181,
regarding transmission-remote-gtk: FTBFS: Option release requires an argument 
[pod2man --release=""] 
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.)


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

Dear Maintainer,

transmission-remote-gtk fails to build from source in
unstable/amd64. A patch is attached.

  [..]

  pod2man --release="" --center="Transmission Remote GTK" 
transmission-remote-gtk.pod > transmission-remote-gtk.1
  Option release requires an argument
  Makefile:963: recipe for target 'transmission-remote-gtk.1' failed

  [..]

The full build log and patch is attached.


Regards,

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


transmission-remote-gtk.1.1.1-3.unstable.amd64.log.txt.gz
Description: Binary data
diff --git a/src/Makefile.am b/src/Makefile.am
index 0c1abd6..0df267e 100644
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -121,7 +121,7 @@ transmission_remote_gtk_SOURCES += win32.rc win32-mailslot.c
 INCLUDES += -O2
 else
 %.1: %.pod
-   pod2man --release="" --center="Transmission Remote GTK" $< > $@
+   pod2man --release="$(VERSION)" --center="Transmission Remote 
GTK" $< > $@
 endif
 
 install-data-local: install-icons update-icon-cache
--- End Message ---
--- Begin Message ---
Source: transmission-remote-gtk
Source-Version: 1.3.1-1

We believe that the bug you reported is fixed in the latest version of
transmission-remote-gtk, 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 839...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Barenblat  (supplier of updated 
transmission-remote-gtk 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: Sun, 23 Oct 2016 13:15:58 -0400
Source: transmission-remote-gtk
Binary: transmission-remote-gtk
Architecture: source amd64
Version: 1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Barenblat 
Changed-By: Benjamin Barenblat 
Description:
 transmission-remote-gtk - GTK+ interface for the Transmission BitTorrent daemon
Closes: 827154 839181
Changes:
 transmission-remote-gtk (1.3.1-1) unstable; urgency=medium
 .
   * New upstream release (closes: #827154, #839181).
Checksums-Sha1:
 29773caaf249c1385a26b423c4aa7dbf2f58fdf2 2067 
transmission-remote-gtk_1.3.1-1.dsc
 c2cc2bb90c1209fcc00707706b3c12fba239285e 359603 
transmission-remote-gtk_1.3.1.orig.tar.gz
 2a07c825049d5c85563caa5efcbca2603ee6bbdc 6688 
transmission-remote-gtk_1.3.1-1.debian.tar.xz
 70af6b77b35aa99ba209b7b9d59917c866cafd4e 571980 
transmission-remote-gtk-dbgsym_1.3.1-1_amd64.deb
 4b70666ada5f2e6579fbb9521cf46f85fcdfec16 180208 
transmission-remote-gtk_1.3.1-1_amd64.deb
Checksums-Sha256:
 dd2ca336fd4d141ad8ae72e2df1044ded4a4663120924f3e5040f9ec7cee5bfd 2067 
transmission-remote-gtk_1.3.1-1.dsc
 bd28adfd419e61a5a0915f22c302e1e53efaa18155890055e86d8b4b3041e90e 359603 
transmission-remote-gtk_1.3.1.orig.tar.gz
 476f7b7ef269cad2f816a59230c27a81ac95d7f0ff3d471f94585e85b9adbfdd 6688 
transmission-remote-gtk_1.3.1-1.debian.tar.xz
 3004d5c98b915838524aa5d6ad392f9e9bed818e0dc8d8cc8f4c4520e903eb4d 571980 
transmission-remote-gtk-dbgsym_1.3.1-1_amd64.deb
 7acb4af7b41e6880021931c62eafa17899dfcbd9d768ec9892c8db6466dedcc8 180208 
transmission-remote-gtk_1.3.1-1_amd64.deb
Files:
 b778c9ce60f097b509b188d76ba318b3 2067 net optional 
transmission-remote-gtk_1.3.1-1.dsc
 6c4839045e30eb9869b61553f4133e0b 359603 net optional 
transmission-remote-gtk_1.3.1.orig.tar.gz
 8a2cf176d9ff88f32f1d64c260270b7a 6688 net optional 

Bug#830392: marked as done (oidua: FTBFS: dh_clean: Please specify the compatibility level in debian/compat)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 21:22:14 +
with message-id 
and subject line Bug#830392: fixed in oidua 0.16.1-8
has caused the Debian Bug report #830392,
regarding oidua: FTBFS: dh_clean: Please specify the compatibility level in 
debian/compat
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.)


-- 
830392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oidua
Version: 0.16.1-7
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh_listpackages: Please specify the compatibility level in debian/compat
> dh_listpackages: Compatibility levels before 5 are no longer supported (level 
> 1 requested)
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> test -x debian/rules
> dh_clean 
> dh_clean: Please specify the compatibility level in debian/compat
> make: *** [clean] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/oidua_0.16.1-7_unstable_reb.normal.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: oidua
Source-Version: 0.16.1-8

We believe that the bug you reported is fixed in the latest version of
oidua, 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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Erik Wenzel  (supplier of updated oidua 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, 23 Oct 2016 19:00:46 +0200
Source: oidua
Binary: oidua
Architecture: source amd64
Version: 0.16.1-8
Distribution: unstable
Urgency: medium
Maintainer: Erik Wenzel 
Changed-By: Erik Wenzel 
Description:
 oidua  - audio file metadata lister
Closes: 830392
Changes:
 oidua (0.16.1-8) unstable; urgency=medium
 .
   * [f59972d0] change to new vcs-browser path
   * [07b261c0] change build dependencies to new debhelper minimum
   * [10ccbd10] add debian/compat with version 9 (closes: 830392)
   * [cc4107f3] [debian/control] bumped stardard version to 3.9.8
   * [d8261cf3] add dh-python to build-depends
Checksums-Sha1:
 e54bf85f94966342a767af75de65ea4fc94b7fcf 1428 oidua_0.16.1-8.dsc
 fe368a2fefffe821bebaed038c93f6aa60cfcbad 21735 oidua_0.16.1.orig.tar.gz
 0a14221fa7cd5087581faa4d29fd060f3dfac437 4632 oidua_0.16.1-8.debian.tar.xz
 41a59803406be7e145d63da0e301c6ae54bf82c3 18776 oidua_0.16.1-8_amd64.deb
Checksums-Sha256:
 c4a0890512e58ff0e895db728d78ba687863fa4256cc778a3ec49c2481e4c57f 1428 
oidua_0.16.1-8.dsc
 b624dad00e4679b055ef94c68bd998d7bda71e47b1b994137f40b15540ebbd7a 21735 
oidua_0.16.1.orig.tar.gz
 ff5ae6a307472ebfa620a28a15f3220ea0fcd149cebd08c0396dfea200dd2249 4632 
oidua_0.16.1-8.debian.tar.xz
 02450bfa213efe4e74699df60b14605dcded953494bf5d19856efbb6f007cb8e 18776 
oidua_0.16.1-8_amd64.deb
Files:
 f41394d2ce96a87e6889faa29c8666d6 1428 sound optional oidua_0.16.1-8.dsc
 819e1d888600a33e6db02df953ae0578 21735 sound optional oidua_0.16.1.orig.tar.gz
 0022109806f833b4e12fdd3071cb9194 4632 sound optional 
oidua_0.16.1-8.debian.tar.xz
 ceea2b2c6834741afd53f797285c7f34 18776 sound optional oidua_0.16.1-8_amd64.deb

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJYDOz1AAoJECbsZ7T+bLyPdlIH/A8+UjMBn8D7Mv71NBILIXrK
LKQtHEQiCk7rpqVFJ4jjhTf6zvrTOjM77S68VqElNea/LvG/qAzvey7q1t3QL5sP
7Yx4Xr8KoV7r/Xqxli8nyQPEZeCWPgt0JLOK/SesF92epLGtZtN+B5uCm/dGcmnP
+d1oSqA6shQ9NlvZQ7l1RW8PZwpez2u63VvzTFUn4fer5uA5d1SetTNCoOOs8iLc

Bug#840728: marked as done (libp11: FTBFS: openssl-1.0.2/engines: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 21:19:29 +
with message-id 
and subject line Bug#840728: fixed in libp11 0.4.2-1
has caused the Debian Bug report #840728,
regarding libp11: FTBFS: openssl-1.0.2/engines: 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.)


-- 
840728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libp11
Version: 0.4.1-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,

libp11 fails to build from source in unstable/amd64:

  [..]

  checking if gcc supports -c -o file.o... (cached) yes
  checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
  checking whether -lc should be explicitly linked in... no
  checking dynamic linker characteristics... GNU/Linux ld.so
  checking how to hardcode library paths into programs... immediate
  checking whether stripping libraries is possible... yes
  checking if libtool supports shared libraries... yes
  checking whether to build shared libraries... yes
  checking whether to build static libraries... yes
  checking for windres... no
  checking for ANSI C header files... (cached) yes
  checking for sys/wait.h that is POSIX.1 compatible... yes
  checking errno.h usability... yes
  checking errno.h presence... yes
  checking for errno.h... yes
  checking fcntl.h usability... yes
  checking fcntl.h presence... yes
  checking for fcntl.h... yes
  checking malloc.h usability... yes
  checking malloc.h presence... yes
  checking for malloc.h... yes
  checking for stdlib.h... (cached) yes
  checking for inttypes.h... (cached) yes
  checking for string.h... (cached) yes
  checking for strings.h... (cached) yes
  checking sys/time.h usability... yes
  checking sys/time.h presence... yes
  checking for sys/time.h... yes
  checking for unistd.h... (cached) yes
  checking locale.h usability... yes
  checking locale.h presence... yes
  checking for locale.h... yes
  checking getopt.h usability... yes
  checking getopt.h presence... yes
  checking for getopt.h... yes
  checking for dlfcn.h... (cached) yes
  checking utmp.h usability... yes
  checking utmp.h presence... yes
  checking for utmp.h... yes
  checking for doxygen... no
  checking for library containing dlopen... -ldl
  checking for __register_atfork... yes
  checking for OPENSSL... yes
  checking that generated files are newer than configure... done
  configure: creating ./config.status
  config.status: creating Makefile
  config.status: creating src/Makefile
  config.status: creating src/libp11.pc
  config.status: creating src/libp11.rc
  config.status: creating src/pkcs11.rc
  config.status: creating doc/Makefile
  config.status: creating doc/doxygen.conf
  config.status: creating examples/Makefile
  config.status: creating tests/Makefile
  config.status: creating src/config.h
  config.status: executing depfiles commands
  config.status: executing libtool commands
  configure: WARNING: unrecognized options: --disable-maintainer-mode
  
  libp11 has been configured with the following options:
  
  Version: 0.4.1
  libp11 directory:/usr/lib/x86_64-linux-gnu
  Engine directory:/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines
  Default PKCS11 module:   
  API doc support: no
  
  Host:x86_64-pc-linux-gnu
  Compiler:gcc
  Preprocessor flags:  -Wdate-time -D_FORTIFY_SOURCE=2
  Compiler flags:  -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1=.
 -fstack-protector-strong -Wformat -Werror=format-security
  Linker flags:-Wl,-z,relro
  Libraries:   -ldl 
  
  OPENSSL_CFLAGS:  
  OPENSSL_LIBS:-lcrypto
  
 dh_auto_build
make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1'
  Making all in src
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1/src'
  make  all-am
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1/src'
  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
-Wdate-time -D_FORTIFY_SOURCE=2-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1=.
 

Bug#841443: marked as done (hmqv.h is missing: refered to by /usr/include/cryptopp/eccrypto.h)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 21:18:56 +
with message-id 
and subject line Bug#841443: fixed in libcrypto++ 5.6.4-2
has caused the Debian Bug report #841443,
regarding hmqv.h is missing: refered to by /usr/include/cryptopp/eccrypto.h
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.)


-- 
841443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcrypto++
Severity: serious

Hello,

It looks like hmqv.h is missing. It is refered by the following file:
 - /usr/include/cryptopp/eccrypto.h

The prevents the program I am working on to build.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libcrypto++
Source-Version: 5.6.4-2

We believe that the bug you reported is fixed in the latest version of
libcrypto++, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated libcrypto++ 
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, 23 Oct 2016 16:46:44 +0200
Source: libcrypto++
Binary: libcrypto++6 libcrypto++6-dbg libcrypto++-dev libcrypto++-utils 
libcrypto++-doc
Architecture: source amd64 all
Version: 5.6.4-2
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libcrypto++-dev - General purpose cryptographic library - C++ development
 libcrypto++-doc - General purpose cryptographic library - documentation
 libcrypto++-utils - General purpose cryptographic library - utilities and data 
files
 libcrypto++6 - General purpose cryptographic library - shared library
 libcrypto++6-dbg - General purpose cryptographic library - debug symbols
Closes: 841443
Changes:
 libcrypto++ (5.6.4-2) unstable; urgency=low
 .
   * Add missed headers to libcrypto++-dev (closes: #841443).
Checksums-Sha1:
 1f01845a76e52f087c31146169c9a6efb9aebff9 2040 libcrypto++_5.6.4-2.dsc
 3bb89d7ae4dd4a68dce7f77dbad338d81afe03f5 14644 
libcrypto++_5.6.4-2.debian.tar.xz
 901ccd35a9c7179cf7283f71e7b0f0ac2be9fc42 1294464 
libcrypto++-dev_5.6.4-2_amd64.deb
 c5b865e6690e262204f8730aedc9e97d6f181c9e 4090034 
libcrypto++-doc_5.6.4-2_all.deb
 99a95191d5086ea63565fb66d4d326a53c3ca086 3204654 
libcrypto++-utils_5.6.4-2_amd64.deb
 76414454efb48bc265aceafe8a14d642be962f9c 12199188 
libcrypto++6-dbg_5.6.4-2_amd64.deb
 ed6da33c1ea6f0fc501fe77035ec59867716dbe6 823244 libcrypto++6_5.6.4-2_amd64.deb
Checksums-Sha256:
 32ebd36ed9a6430060d98b4984b7df70f1586cb36b7c58348febe4a4f2b55e52 2040 
libcrypto++_5.6.4-2.dsc
 876dffcf1bfa785d598235a2d435911890aaa940b38632342785f59a77853e7e 14644 
libcrypto++_5.6.4-2.debian.tar.xz
 4765fb2fab5451d6bf38d881a6985b4b2eff885a247a7e2529d1df4d9b3cd78b 1294464 
libcrypto++-dev_5.6.4-2_amd64.deb
 be7dbfc365b6d6a2b5d3feec039dcce7fd826cd00313e73949c74ecbb9da7a8c 4090034 
libcrypto++-doc_5.6.4-2_all.deb
 f9e643f3ef5a095b489c72b5be1a59bd52c02322a45c8572de3833308e40418e 3204654 
libcrypto++-utils_5.6.4-2_amd64.deb
 924f046ee0876e134986667acbf685fcb205a46266a8213e220d37329b586f11 12199188 
libcrypto++6-dbg_5.6.4-2_amd64.deb
 163fca13b264e2d211f9f7f4f44819fc8d1e725fbd911e37ef271ec715810af7 823244 
libcrypto++6_5.6.4-2_amd64.deb
Files:
 1260038af7a49f10a85672a87c56913b 2040 libs optional libcrypto++_5.6.4-2.dsc
 d95a4ba0d519c93f23de6cc4921eb48c 14644 libs optional 
libcrypto++_5.6.4-2.debian.tar.xz
 acb2af5a29ea78e41cc42138724ba428 1294464 libdevel optional 
libcrypto++-dev_5.6.4-2_amd64.deb
 e0f18b0d527eff707486b70368e696fd 4090034 doc optional 
libcrypto++-doc_5.6.4-2_all.deb
 7b4ce86d5b5debba9be6b387cf217b24 3204654 utils optional 
libcrypto++-utils_5.6.4-2_amd64.deb
 4505787300a6e0c3207409afc84d77f0 12199188 debug extra 
libcrypto++6-dbg_5.6.4-2_amd64.deb
 5f9b8b6d7a2ef5b4a3d2ebcdc20c9e58 823244 libs optional 
libcrypto++6_5.6.4-2_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#840841: marked as done (digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 21:09:58 +
with message-id 
and subject line Bug#841751: fixed in digikam 4:5.2.0-2
has caused the Debian Bug report #841751,
regarding digikam: fails to upgrade from jessie to stretch: gets removed, not 
upgraded
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.)


-- 
841751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 4:5.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails.

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

[...]
# distupgrade from jessie to stretch
3m14.4s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp_SRqAA', 
'apt-get', '-yf', 'dist-upgrade']
5m43.2s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages were automatically installed and are no longer 
required:
[...]
  Use 'apt-get autoremove' to remove them.
  The following packages will be REMOVED:
digikam digikam-private-libs libclucene-core1 libebml4 libgpgme++2
libmarblewidget19 libmatroska6 libopencv-calib3d2.4 libopencv-contrib2.4
libopencv-core2.4 libopencv-features2d2.4 libopencv-flann2.4
libopencv-highgui2.4 libopencv-imgproc2.4 libopencv-ml2.4
libopencv-objdetect2.4 libopencv-video2.4 libproxy1 libstreamanalyzer0
libtag1-vanilla libtag1c2a perl-modules vlc-plugin-pulse
  The following NEW packages will be installed:
[...]

# ok, lets try to install it in stretch
5m45.0s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp_SRqAA', 
'apt-get', '-y', 'install', 'digikam']
5m45.6s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   digikam : Depends: digikam-private-libs (= 4:5.2.0-1) but it is not going to 
be installed
  E: Unable to correct problems, you have held broken packages.
5m45.6s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmp_SRqAA', 'apt-get', '-y', 'install', 'digikam']
  

cheers,

Andreas


digikam_4:5.2.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: digikam
Source-Version: 4:5.2.0-2

We believe that the bug you reported is fixed in the latest version of
digikam, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated digikam 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, 23 Oct 2016 11:39:28 -0500
Source: digikam
Binary: digikam-private-libs digikam showfoto digikam-data digikam-doc 
kipi-plugins kipi-plugins-common
Architecture: source
Version: 4:5.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Steve M. Robbins 
Description:
 digikam- digital photo management application for KDE
 digikam-data - digiKam architecture-independant data
 digikam-doc - handbook for digiKam
 digikam-private-libs - private libraries for digiKam and kipi plugins
 kipi-plugins - image manipulation/handling plugins for KIPI aware programs
 kipi-plugins-common - kipi-plugins architecture-independent data
 showfoto   - image viewer/editor for KDE
Closes: 834365 840841 841751
Changes:
 digikam (4:5.2.0-2) unstable; urgency=medium
 .
   * Add missing dependency for libqt5sql5-mysql.  Closes: #834365.
   * Rebuild will update libmarblewidget-qt5 dependency.  Closes: #840841,
 #841751.
Checksums-Sha1:
 

Bug#840841: marked as done (digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 21:09:58 +
with message-id 
and subject line Bug#840841: fixed in digikam 4:5.2.0-2
has caused the Debian Bug report #840841,
regarding digikam: fails to upgrade from jessie to stretch: gets removed, not 
upgraded
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.)


-- 
840841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 4:5.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails.

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

[...]
# distupgrade from jessie to stretch
3m14.4s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp_SRqAA', 
'apt-get', '-yf', 'dist-upgrade']
5m43.2s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages were automatically installed and are no longer 
required:
[...]
  Use 'apt-get autoremove' to remove them.
  The following packages will be REMOVED:
digikam digikam-private-libs libclucene-core1 libebml4 libgpgme++2
libmarblewidget19 libmatroska6 libopencv-calib3d2.4 libopencv-contrib2.4
libopencv-core2.4 libopencv-features2d2.4 libopencv-flann2.4
libopencv-highgui2.4 libopencv-imgproc2.4 libopencv-ml2.4
libopencv-objdetect2.4 libopencv-video2.4 libproxy1 libstreamanalyzer0
libtag1-vanilla libtag1c2a perl-modules vlc-plugin-pulse
  The following NEW packages will be installed:
[...]

# ok, lets try to install it in stretch
5m45.0s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp_SRqAA', 
'apt-get', '-y', 'install', 'digikam']
5m45.6s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   digikam : Depends: digikam-private-libs (= 4:5.2.0-1) but it is not going to 
be installed
  E: Unable to correct problems, you have held broken packages.
5m45.6s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmp_SRqAA', 'apt-get', '-y', 'install', 'digikam']
  

cheers,

Andreas


digikam_4:5.2.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: digikam
Source-Version: 4:5.2.0-2

We believe that the bug you reported is fixed in the latest version of
digikam, 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 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated digikam 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, 23 Oct 2016 11:39:28 -0500
Source: digikam
Binary: digikam-private-libs digikam showfoto digikam-data digikam-doc 
kipi-plugins kipi-plugins-common
Architecture: source
Version: 4:5.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Steve M. Robbins 
Description:
 digikam- digital photo management application for KDE
 digikam-data - digiKam architecture-independant data
 digikam-doc - handbook for digiKam
 digikam-private-libs - private libraries for digiKam and kipi plugins
 kipi-plugins - image manipulation/handling plugins for KIPI aware programs
 kipi-plugins-common - kipi-plugins architecture-independent data
 showfoto   - image viewer/editor for KDE
Closes: 834365 840841 841751
Changes:
 digikam (4:5.2.0-2) unstable; urgency=medium
 .
   * Add missing dependency for libqt5sql5-mysql.  Closes: #834365.
   * Rebuild will update libmarblewidget-qt5 dependency.  Closes: #840841,
 #841751.
Checksums-Sha1:
 

Bug#841751: marked as done (digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 21:09:58 +
with message-id 
and subject line Bug#841751: fixed in digikam 4:5.2.0-2
has caused the Debian Bug report #841751,
regarding digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25
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.)


-- 
841751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 4:5.2.0-1
Severity: normal

Dear Maintainer,

Hope it will be uploaded soon.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages digikam depends on:
ii  digikam-data  4:5.2.0-1
ii  digikam-private-libs  4:5.2.0-1
ii  libc6 2.24-5
ii  libgcc1   1:6.2.0-9
ii  libkf5configcore5 5.27.0-1
ii  libkf5coreaddons5 5.27.0-1
ii  libkf5filemetadata3   5.27.0-1
ii  libkf5i18n5   5.27.0-1
ii  libqt5core5a  5.6.1+dfsg-3+b1
ii  libqt5gui55.6.1+dfsg-3+b1
ii  libqt5sql55.6.1+dfsg-3+b1
ii  libqt5sql5-sqlite 5.6.1+dfsg-3+b1
ii  libqt5widgets55.6.1+dfsg-3+b1
ii  libstdc++66.2.0-9
pn  perl:any  

Versions of packages digikam recommends:
ii  chromium [www-browser]  53.0.2785.143-1
ii  ffmpegthumbs4:16.08.0-1
ii  firefox [www-browser]   49.0-4
ii  w3m [www-browser]   0.5.3-31

Versions of packages digikam suggests:
pn  digikam-doc 
ii  systemsettings  4:5.8.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: digikam
Source-Version: 4:5.2.0-2

We believe that the bug you reported is fixed in the latest version of
digikam, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated digikam 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, 23 Oct 2016 11:39:28 -0500
Source: digikam
Binary: digikam-private-libs digikam showfoto digikam-data digikam-doc 
kipi-plugins kipi-plugins-common
Architecture: source
Version: 4:5.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Steve M. Robbins 
Description:
 digikam- digital photo management application for KDE
 digikam-data - digiKam architecture-independant data
 digikam-doc - handbook for digiKam
 digikam-private-libs - private libraries for digiKam and kipi plugins
 kipi-plugins - image manipulation/handling plugins for KIPI aware programs
 kipi-plugins-common - kipi-plugins architecture-independent data
 showfoto   - image viewer/editor for KDE
Closes: 834365 840841 841751
Changes:
 digikam (4:5.2.0-2) unstable; urgency=medium
 .
   * Add missing dependency for libqt5sql5-mysql.  Closes: #834365.
   * Rebuild will update libmarblewidget-qt5 dependency.  Closes: #840841,
 #841751.
Checksums-Sha1:
 242053e873a7ef432852c6acfc86df0c48cdc898 3105 digikam_5.2.0-2.dsc
 06a1726161722d05b033c8362042563846462ebc 33348 digikam_5.2.0-2.debian.tar.xz
Checksums-Sha256:
 a997401c22806965d15972ad914e6e9d14004b4fdcc856491134df313a4fbf61 3105 
digikam_5.2.0-2.dsc
 8fadd78737d797bcf60251a4d584c4c4e4b4208b49925932a281ab5915e897ff 33348 
digikam_5.2.0-2.debian.tar.xz
Files:
 e76f4bbaa2e58bc48bc7a801619d60ce 3105 graphics optional digikam_5.2.0-2.dsc
 9f9bfd08cd30c7f80bfa8896d6c63598 33348 graphics optional 
digikam_5.2.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIsBAEBCAAWBQJYDP77DxxzbXJAZGViaWFuLm9yZwAKCRDJ5V4vrcj0uSFmD/9x
TZAvRPwyBkCL4jCfq2D1iCa99pfoMHMVbxdrl58Q1QJlfH03DFti9leA0ehFt6ss
8sp+6mWcnTJWmaJY2NSe5NExoZ9CkXNfjcK9gae0lXdSafxdVRq6zryvd+zY3ZwQ
sMBUsTGH6I/AAPg24l2L9uzTM3KUPriamiSLQITtJz7uJxYQYyziPx/JYmao4NT5

Bug#841751: marked as done (digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 21:09:58 +
with message-id 
and subject line Bug#840841: fixed in digikam 4:5.2.0-2
has caused the Debian Bug report #840841,
regarding digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25
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.)


-- 
840841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 4:5.2.0-1
Severity: normal

Dear Maintainer,

Hope it will be uploaded soon.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages digikam depends on:
ii  digikam-data  4:5.2.0-1
ii  digikam-private-libs  4:5.2.0-1
ii  libc6 2.24-5
ii  libgcc1   1:6.2.0-9
ii  libkf5configcore5 5.27.0-1
ii  libkf5coreaddons5 5.27.0-1
ii  libkf5filemetadata3   5.27.0-1
ii  libkf5i18n5   5.27.0-1
ii  libqt5core5a  5.6.1+dfsg-3+b1
ii  libqt5gui55.6.1+dfsg-3+b1
ii  libqt5sql55.6.1+dfsg-3+b1
ii  libqt5sql5-sqlite 5.6.1+dfsg-3+b1
ii  libqt5widgets55.6.1+dfsg-3+b1
ii  libstdc++66.2.0-9
pn  perl:any  

Versions of packages digikam recommends:
ii  chromium [www-browser]  53.0.2785.143-1
ii  ffmpegthumbs4:16.08.0-1
ii  firefox [www-browser]   49.0-4
ii  w3m [www-browser]   0.5.3-31

Versions of packages digikam suggests:
pn  digikam-doc 
ii  systemsettings  4:5.8.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: digikam
Source-Version: 4:5.2.0-2

We believe that the bug you reported is fixed in the latest version of
digikam, 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 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated digikam 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, 23 Oct 2016 11:39:28 -0500
Source: digikam
Binary: digikam-private-libs digikam showfoto digikam-data digikam-doc 
kipi-plugins kipi-plugins-common
Architecture: source
Version: 4:5.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Steve M. Robbins 
Description:
 digikam- digital photo management application for KDE
 digikam-data - digiKam architecture-independant data
 digikam-doc - handbook for digiKam
 digikam-private-libs - private libraries for digiKam and kipi plugins
 kipi-plugins - image manipulation/handling plugins for KIPI aware programs
 kipi-plugins-common - kipi-plugins architecture-independent data
 showfoto   - image viewer/editor for KDE
Closes: 834365 840841 841751
Changes:
 digikam (4:5.2.0-2) unstable; urgency=medium
 .
   * Add missing dependency for libqt5sql5-mysql.  Closes: #834365.
   * Rebuild will update libmarblewidget-qt5 dependency.  Closes: #840841,
 #841751.
Checksums-Sha1:
 242053e873a7ef432852c6acfc86df0c48cdc898 3105 digikam_5.2.0-2.dsc
 06a1726161722d05b033c8362042563846462ebc 33348 digikam_5.2.0-2.debian.tar.xz
Checksums-Sha256:
 a997401c22806965d15972ad914e6e9d14004b4fdcc856491134df313a4fbf61 3105 
digikam_5.2.0-2.dsc
 8fadd78737d797bcf60251a4d584c4c4e4b4208b49925932a281ab5915e897ff 33348 
digikam_5.2.0-2.debian.tar.xz
Files:
 e76f4bbaa2e58bc48bc7a801619d60ce 3105 graphics optional digikam_5.2.0-2.dsc
 9f9bfd08cd30c7f80bfa8896d6c63598 33348 graphics optional 
digikam_5.2.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIsBAEBCAAWBQJYDP77DxxzbXJAZGViaWFuLm9yZwAKCRDJ5V4vrcj0uSFmD/9x
TZAvRPwyBkCL4jCfq2D1iCa99pfoMHMVbxdrl58Q1QJlfH03DFti9leA0ehFt6ss
8sp+6mWcnTJWmaJY2NSe5NExoZ9CkXNfjcK9gae0lXdSafxdVRq6zryvd+zY3ZwQ
sMBUsTGH6I/AAPg24l2L9uzTM3KUPriamiSLQITtJz7uJxYQYyziPx/JYmao4NT5

Processed: This is the same bug

[Debian Bug Tracking System]

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

> reassign 841757 src:check
Bug #841757 [src:mpc] mpc: FTBFS: relocation R_X86_64_32S against `.rodata' can 
not be used when making a shared object; recompile with -fPIC
Bug reassigned from package 'src:mpc' to 'src:check'.
No longer marked as found in versions mpc/0.28-1.
Ignoring request to alter fixed versions of bug #841757 to the same values 
previously set
> forcemerge 837445 841757
Bug #837445 [src:check] check: Please build libcheck.a with -fPIC
Bug #841757 [src:check] mpc: FTBFS: relocation R_X86_64_32S against `.rodata' 
can not be used when making a shared object; recompile with -fPIC
Added indication that 841757 affects 
src:vnstat,src:galera-3,src:gubbins,src:ettercap,src:netcfg
Marked as found in versions check/0.10.0-3.
Added tag(s) patch.
Merged 837445 841757
> affects 837445 src:mpc
Bug #837445 [src:check] check: Please build libcheck.a with -fPIC
Bug #841757 [src:check] mpc: FTBFS: relocation R_X86_64_32S against `.rodata' 
can not be used when making a shared object; recompile with -fPIC
Added indication that 837445 affects src:mpc
Added indication that 841757 affects src:mpc
> thanks
Stopping processing here.

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

Bug#841665: marked as done (boinc-client: The boinc-client init script has a badly constructed parameter for xhost)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 20:58:09 +
with message-id 
and subject line Bug#841665: fixed in boinc 7.6.33+dfsg-2
has caused the Debian Bug report #841665,
regarding boinc-client: The boinc-client init script has a badly constructed 
parameter for xhost
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.)


-- 
841665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: boinc-client
Version: 7.6.33+dfsg-1~bpo8+1
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainers,

boinc-client shell script is used by init/systemd to start the boinc client 
daemon (typically running as user=boinc)

In order for boinc to access GPU hardware -  xhost is used to grant access to 
boinc.

At line 109-110
---
# grant the boinc client to perform GPU computing
   xhost local:boinc || echo -n "xhost error ignored, GPU computing may not 
be possible"


the correct syntax stould be 
   xhost +si:localuser:boinc
or more correctly for the this script
   xhost +si:localuser:$BOINC_USER

The impact of using this incorrect syntax - is not to error, but grant ALL 
local users access.  
(This could be a very old or different maybe BSD syntax)

The intention of the script to grant ONLY user=boinc access, instead all local 
users have access.

For example a little test.

agentb@dejon:/etc/init.d$ xhost
access control enabled, only authorized clients can connect
SI:localuser:agentb

agentb@dejon:/etc/init.d$ xhost local:random-string
non-network local connections being added to access control list

agentb@dejon:/etc/init.d$ xhost
access control enabled, only authorized clients can connect
LOCAL:
SI:localuser:boinc
SI:localuser:agentb

Hope this is clear, and thank you for maintaining boinc!

Cheers
Mike


-- Package-specific info:
-- Contents of /etc/default/boinc-client:
# This file is /etc/default/boinc-client, it is a configuration file for the
# /etc/init.d/boinc-client init script.

# Set this to 1 to enable and to 0 to disable the init script.
ENABLED="1"

# Set this to 1 to enable advanced scheduling of the BOINC core client and
# all its sub-processes (reduces the impact of BOINC on the system's
# performance).
SCHEDULE="1"

# The BOINC core client will be started with the permissions of this user.
BOINC_USER="boinc"

# This is the data directory of the BOINC core client.
BOINC_DIR="/var/lib/boinc-client"

# This is the location of the BOINC core client, that the init script uses.
# If you do not want to use the client program provided by the boinc-client
# package, you can specify here an alternative client program.
#BOINC_CLIENT="/usr/local/bin/boinc"
BOINC_CLIENT="/usr/bin/boinc"

# Here you can specify additional options to pass to the BOINC core client.
# Type 'boinc --help' or 'man boinc' for a full summary of allowed options.
#BOINC_OPTS="--allow_remote_gui_rpc"
BOINC_OPTS=""

# Scheduling options

# Set SCHEDULE="0" if prefering to run with upstream default priority
# settings.

# Nice levels. When systems are truly busy, e.g. because of too many active
# scientific applications started by the boinc client, there is a chance for
# the boinc client not to be granted sufficient opportunity to check for
# scientific applications to be alive and make the (wrong) decision to
# terminate the scientific app. This is particularly an issue with many
# apps started in parallel on modern multi-core systems and extra overheads
# for the download and uploads of files with the project servers. Another
# concern is the latency for scientific applications to communicate with the
# graphics card, which should be low. All such values should be set and
# controled from within the BOINC client. The Debian init script also sets
# extra constrains via chrt on real time performance and via ionice on 
# I/O performance, which is beyond the regular BOINC client. It then was
# too easy to use that code to also constrain minimal nice levels. We still
# think about how to best distinguish GPU applications from regular apps.
BOINC_NICE_CLIENT=10
BOINC_NICE_APP_DEFAULT=19
#BOINC_NICE_APP_GPU=5# not yet used

# ionice classes. See manpage of ionice (1) in the util-linux package.
BOINC_IONICE_CLIENT=3# idle
#BOINC_IONICE_APP_DEFAULT=3  # idle, not yet used
#BOINC_IONICE_APP_GPU=2  # best effort, not 

Processed: Re: roboptim-core: FTBFS: dh_install: libroboptim-core2-plugin-base missing files (usr/lib/*/roboptim-core/*.so.2*), aborting

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #808455 [src:roboptim-core] roboptim-core: FTBFS: dh_install: 
libroboptim-core2-plugin-base missing files (usr/lib/*/roboptim-core/*.so.2*), 
aborting
Added tag(s) patch.

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

Bug#808455: roboptim-core: FTBFS: dh_install: libroboptim-core2-plugin-base missing files (usr/lib/*/roboptim-core/*.so.2*), aborting

[Petter Reinholdtsen]

Control: tags -1 + patch

[Chris Lamb 2015-12-20]
> roboptim-core fails to build from source in unstable/amd64:

It still fail to build.

>   dh_install: libroboptim-core2-plugin-base missing files 
> (usr/lib/*/roboptim-core/*.so.2*), aborting
>   debian/rules:26: recipe for target 'binary' failed
>   make: *** [binary] Error 255

The files in that directory is no longer named *.so.2*, but only *.so.  I thus
suggest changing the .install file to look like this:

  usr/lib/*/roboptim-core/*.so*

There is a new failure caused by a new C++ compiler.  The attached patch solve
this problem.  The changes were fetched from upstream, so upgrading to a new
upstream version might be a good idea too.

With these two changes in place, the package build in unstable.

Btw, is this package still being maintained?  No RC fixes for a long time and
last maintainer upload 2014-06-26 make me uneasy about this.

-- 
Happy hacking
Petter Reinholdtsen
Description: Fix build problems with the recent C++ compiler
 Fix C++ resolver issues breaking the build.  The changes are fetched
 from upstream, where the solution was already in place 2016-10-23.
Author: Petter Reinholdtsen 
Bug-Debian: https://bugs.debian.org/808455
Forwarded: not-needed
Reviewed-By: 
Last-Update: 2016-10-23

--- roboptim-core-2.0.orig/include/roboptim/core/terminal-color.hh
+++ roboptim-core-2.0/include/roboptim/core/terminal-color.hh
@@ -26,32 +26,25 @@
 #  include 
 # endif // _WIN32
 
-# ifdef _WIN32
-#  define ROBOPTIM_CORE_FILTER_TTY()			\
-  do			\
-{			\
-  return o;		\
-}			\
-  while (0)
-# else
-#  define ROBOPTIM_CORE_FILTER_TTY()			\
-  do			\
-{			\
-  if (o == std::cout && !isatty (fileno (stdout)))	\
-	return o;	\
-  if (o == std::cerr && !isatty (fileno (stderr)))	\
-	return o;	\
-  if (o != std::cout && o != std::cerr)		\
-	return o;	\
-}			\
-  while (0)
-#endif // _WIN32
+# define ROBOPTIM_CORE_FILTER_TTY()		\
+  if (!roboptim::fg::isTtyStream (o))		\
+return o
 
 
 namespace roboptim
 {
   namespace fg
   {
+inline bool isTtyStream (const std::ostream& o)
+{
+# ifdef _WIN32
+  return false;
+# else
+  return !((o.rdbuf () == std::cout.rdbuf () && !isatty (fileno (stdout))) ||
+   (o.rdbuf () == std::cerr.rdbuf () && !isatty (fileno (stderr))) ||
+   (o.rdbuf () != std::cout.rdbuf () && o.rdbuf () != std::cerr.rdbuf ()));
+#endif // _WIN32
+}
 inline std::ostream& reset (std::ostream& o)
 {
   ROBOPTIM_CORE_FILTER_TTY ();
--- roboptim-core-2.0.orig/include/roboptim/core/solver-factory.hxx
+++ roboptim-core-2.0/include/roboptim/core/solver-factory.hxx
@@ -144,7 +144,7 @@ namespace roboptim
 	std::stringstream sserror;
 	sserror << "libltdl failed to close plug-in: "
 		<< lt_dlerror ();
-	std::cerr << sserror << std::endl;
+	std::cerr << sserror.str() << std::endl;
   }
 
 if (lt_dlexit ())
@@ -152,7 +152,7 @@ namespace roboptim
 	std::stringstream sserror;
 	sserror << "libltdl failed to call ``create'': "
 		<< lt_dlerror ();
-	std::cerr << sserror << std::endl;
+	std::cerr << sserror.str() << std::endl;
   }
   }
 

Bug#840853: Reassign

[Hilko Bengen]

* Neil Williams:

> The requirement for linuxboot_dma.bin is specific to QEMU 2.7 and is
> not provided by the seabios package (which provides linuxboot_dma.bin).
> As a workaround, symlinking linuxboot_dma.bin as linuxboot.bin
> in /usr/share/seabios/ allows the guestfs operations to proceed.

This is the qemu upstream commit that introduces linuxboot_dma.bin, this
contains what looks to me like code has been forked from seabios.

,
| commit b2a575a1c652904600869e774e45bf4c9ed72c55
| Author: Marc Marí 
| Date:   Mon May 23 19:11:33 2016 +0100
| 
| Add optionrom compatible with fw_cfg DMA version
| 
| This optionrom is based on linuxboot.S.
| 
| Signed-off-by: Marc Marí 
| Signed-off-by: Richard W.M. Jones 
| Message-Id: <1464027093-24073-2-git-send-email-rjo...@redhat.com>
| [Add -fno-toplevel-reorder, support clang without -m16. - Paolo]
| Signed-off-by: Paolo Bonzini 
`

We have already established that symlinking linuxboot_dma.bin to
linuxboot.bin fixes directly booting a Linux kernel, so I suppose that
backing out the change to hw/i386/pc.c may do the trick, as below.

Cheers,
-Hilko

diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index 1b8baa8..f56e225 100644
--- a/hw/i386/pc.c
+++ b/hw/i386/pc.c
@@ -998,13 +998,8 @@ static void load_linux(PCMachineState *pcms,
 fw_cfg_add_i32(fw_cfg, FW_CFG_SETUP_SIZE, setup_size);
 fw_cfg_add_bytes(fw_cfg, FW_CFG_SETUP_DATA, setup, setup_size);

-if (fw_cfg_dma_enabled(fw_cfg)) {
-option_rom[nb_option_roms].name = "linuxboot_dma.bin";
-option_rom[nb_option_roms].bootindex = 0;
-} else {
-option_rom[nb_option_roms].name = "linuxboot.bin";
-option_rom[nb_option_roms].bootindex = 0;
-}
+option_rom[nb_option_roms].name = "linuxboot.bin";
+option_rom[nb_option_roms].bootindex = 0;
 nb_option_roms++;
 }

@@ -1296,7 +1291,6 @@ void xen_load_linux(PCMachineState *pcms)
 load_linux(pcms, fw_cfg);
 for (i = 0; i < nb_option_roms; i++) {
 assert(!strcmp(option_rom[i].name, "linuxboot.bin") ||
-   !strcmp(option_rom[i].name, "linuxboot_dma.bin") ||
!strcmp(option_rom[i].name, "multiboot.bin"));
 rom_add_option(option_rom[i].name, option_rom[i].bootindex);
 }

Processed: Bug#841625 marked as pending

[Debian Bug Tracking System]

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

> tag 841625 pending
Bug #841625 [src:gupnp-tools] gupnp-tools: FTBFS: playlist-treeview.h:35:34: 
error: unknown type name 'GUPnPDeviceProxy'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841625: marked as pending

[Andreas Henriksson]

tag 841625 pending
thanks

Hello,

Bug #841625 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-gnome/gupnp-tools.git;a=commitdiff;h=d756041

---
commit d7560414d57520a05b4643d4d043b17b6ab8285a
Author: Andreas Henriksson 
Date:   Sun Oct 23 21:48:32 2016 +0200

Update debian/changelog

diff --git a/debian/changelog b/debian/changelog
index f5923c1..24ec511 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+gupnp-tools (0.8.12-2) unstable; urgency=medium
+
+  * Add debian/gbp.conf
+  * Add debian/patches/Fix-desktop-file-generation.patch (Closes: #836002)
+  * Add debian/patches/av-cp-Fix-compiling-when-using-recent-GUPnP-AV.patch
+(Closes: #841625)
+  * Convert from cdbs to dh
+  * Bump dh compat to 10
+
+ -- Andreas Henriksson   Sun, 23 Oct 2016 21:48:20 +0200
+
 gupnp-tools (0.8.12-1) unstable; urgency=medium
 
   * New upstream release.

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Petra Ruebe-Pugliese]

Package: src:linux
Version: 4.7.8-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

when performing this week's regular update on my Debian Testing
systems, linux-image-4.7.0-1-686 was updated from 4.7.6-1 to
4.7.8-1_i386.deb on two Thinkpads T41.

On both of them, the system failed to boot after that update:
grub started correctly and let me "choose" the system to boot
(there is only one!);  after that I saw a blank screen with a
blinking cursor in the upper left corner, and that was all.
Something seemed to be "going on" (fan working more than usual);
but no further reaction was to be obtained from the system(s).

Downgrading to linux-image-4.7.0-1-686_4.7.6-1_i386.deb via
rescue-CD and "dpkg -i" (fortunately!!!) solved the problem.

(There was no similar problem with linux-image-4.7.0-1-686-pae_4.7.8-1_i386.deb
 on two old PCs I was updating at the same time, nor with the
 corresponding version on an AMD64 PC.)

Greetings
  Petra


-- Package-specific info:
** Version:
Linux version 4.7.0-1-686 (debian-ker...@lists.debian.org) (gcc version 5.4.1 
20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.6-1 (2016-10-07)

 4.7.6-1 is now running correctly again, 4.7.8-1 did not boot, see above!
 (So the first line does _not_ describe the problematic system!)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.7.0-1-686 
root=UUID=496e0e0a-6e7c-46c2-9132-315243394a2d ro framebuffer=false quiet 
fb=false systemd.show_status=true

** Not tainted

** Kernel log:
[   28.664766] [drm] register mmio size: 65536
[   28.665108] agpgart-intel :00:00.0: AGP 2.0 bridge
[   28.665133] agpgart-intel :00:00.0: putting AGP V2 device into 1x mode
[   28.665183] radeon :01:00.0: putting AGP V2 device into 1x mode
[   28.665218] radeon :01:00.0: GTT: 256M 0xD000 - 0xDFFF
[   28.665236] radeon :01:00.0: VRAM: 128M 0xE000 - 
0xE7FF (32M used)
[   28.665802] [drm] Detected VRAM RAM=128M, BAR=128M
[   28.665812] [drm] RAM width 64bits DDR
[   28.666000] [TTM] Zone  kernel: Available graphics memory: 254772 kiB
[   28.666007] [TTM] Initializing pool allocator
[   28.666094] [drm] radeon: 32M of VRAM memory ready
[   28.666102] [drm] radeon: 256M of GTT memory ready.
[   28.666165] [drm] radeon: power management initialized
[   28.672409] radeon :01:00.0: WB disabled
[   28.672430] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0xd000 and cpu addr 0xe0784000
[   28.672438] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   28.672444] [drm] Driver supports precise vblank timestamp query.
[   28.672473] [drm] radeon: irq initialized.
[   28.672503] [drm] Loading R100 Microcode
[   29.806006] Adding 1253032k swap on /dev/sda5.  Priority:-1 extents:1 
across:1253032k FS
[   31.399282] radeon :01:00.0: firmware: direct-loading firmware 
radeon/R100_cp.bin
[   31.399675] [drm] radeon: ring at 0xD0001000
[   31.399708] [drm] ring test succeeded in 1 usecs
[   31.400728] [drm] ib test succeeded in 0 usecs
[   31.415037] [drm] Panel ID String: 1024x768
[   31.415051] [drm] Panel Size 1024x768
[   31.415229] [drm] No TV DAC info found in BIOS
[   31.415399] [drm] Radeon Display Connectors
[   31.415406] [drm] Connector 0:
[   31.415411] [drm]   VGA-1
[   31.415420] [drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[   31.415425] [drm]   Encoders:
[   31.415430] [drm] CRT1: INTERNAL_DAC1
[   31.415436] [drm] Connector 1:
[   31.415440] [drm]   DVI-D-1
[   31.415445] [drm]   HPD1
[   31.415453] [drm]   DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[   31.415458] [drm]   Encoders:
[   31.415463] [drm] DFP1: INTERNAL_TMDS1
[   31.415468] [drm] Connector 2:
[   31.415473] [drm]   LVDS-1
[   31.415477] [drm]   Encoders:
[   31.415482] [drm] LCD1: INTERNAL_LVDS
[   31.415487] [drm] Connector 3:
[   31.415491] [drm]   SVIDEO-1
[   31.415496] [drm]   Encoders:
[   31.415500] [drm] TV1: INTERNAL_DAC2
[   31.519004] [drm] fb mappable at 0xE004
[   31.519014] [drm] vram apper at 0xE000
[   31.519018] [drm] size 786432
[   31.519022] [drm] fb depth is 8
[   31.519026] [drm]pitch is 1024
[   31.524653] fbcon: radeondrmfb (fb0) is primary device
[   31.581140] Console: switching to colour frame buffer device 128x48
[   31.586351] radeon :01:00.0: fb0: radeondrmfb frame buffer device
[   31.586745] [drm] Initialized radeon 2.45.0 20080528 for :01:00.0 on 
minor 0
[   35.646219] systemd-sysv-generator[416]: Overwriting existing symlink 
/run/systemd/generator.late/chrony.service with real service.
[  371.780145] usb 1-4: new high-speed USB device number 2 using ehci-pci
[  371.912886] usb 1-4: New USB device found, idVendor=0781, idProduct=5406
[  371.912899] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  371.912909] usb 1-4: Product: U3 Cruzer Micro
[  371.912917] usb 1-4: Manufacturer: SanDisk
[  371.912926] usb 1-4: SerialNumber: 08782107F6117022
[  

Bug#838897: jitsi: Replace the glassfish dependencies

[Ingo Bauersachs]

On Mon, 26 Sep 2016 10:43:42 +0200 Emmanuel Bourg  wrote:
> jitsi still depends on glassfish-activation and glassfish-mail which are
going
> to be removed. glassfish-activation can be safely removed (the API has
been
> integrated to the standard JDK) and glassfish-mail should be replaced by
libmail-java.

I'm not sure where these dependencies would come from. javax.activation is
nowhere to be found in the source code, and Jitsi doesn't send mails either.

Anyway if the Jitsi package poses a problem, please remove it from Debian.
It is unusable anyway as libjitsi is missing. Once I manage to get version
2.10 out, I'll try to continue packaging dependencies so it can come back to
Debian in a clean fashion.

> Thank you,
> Emmanuel Bourg

Ingo

Bug#837658: libfl_pic.a needs more than a binNMU

[Adrian Bunk]

Control: retitle 837658 libfl_pic.a is not compiled with -fPIC

#837658 is different from many other PIE issues:

This is a _pic.a library that includes the non-PIC objects instead of 
the PIC objects it should contain.

A binNMU with -fPIE would not fix the root cause that this library is 
supposed to contain PIC code.

See the flex README.Debian for background.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: libfl_pic.a needs more than a binNMU

[Debian Bug Tracking System]

Processing control commands:

> retitle 837658 libfl_pic.a is not compiled with -fPIC
Bug #837658 [libfl-dev] libfl-dev: Please build libfl_pic.a with -fPIC
Bug #840394 [libfl-dev] motif: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
Bug #841360 [libfl-dev] libmotif-common stuck at 2.3.4-10 in sid (src:motif is 
2.3.4-11)
Bug #841394 [libfl-dev] filters: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
Changed Bug title to 'libfl_pic.a is not compiled with -fPIC' from 'libfl-dev: 
Please build libfl_pic.a with -fPIC'.
Changed Bug title to 'libfl_pic.a is not compiled with -fPIC' from 'motif: 
FTBFS: relocation R_X86_64_PC32 against symbol `exit@@GLIBC_2.2.5' can not be 
used when making a shared object; recompile with -fPIC'.
Changed Bug title to 'libfl_pic.a is not compiled with -fPIC' from 
'libmotif-common stuck at 2.3.4-10 in sid (src:motif is 2.3.4-11)'.
Changed Bug title to 'libfl_pic.a is not compiled with -fPIC' from 'filters: 
FTBFS: relocation R_X86_64_PC32 against symbol `exit@@GLIBC_2.2.5' can not be 
used when making a shared object; recompile with -fPIC'.

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

Processed: Fix for the qterm FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #831093 [src:qterm] qterm: FTBFS with GCC 6: uaocodec.cpp:15598:1: error: 
narrowing conversion of ''\3777600'' from 'char' to 'uchar {aka unsigned 
char}' inside { } [-Wnarrowing]
Added tag(s) patch.

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

Bug#831093: Fix for the qterm FTBFS

[Adrian Bunk]

Control: tags -1 +patch

What broke the build is that gcc 6 changed the default C++ standard
from C++98 to C++14.

Not all valid C++98 code is also valid C++11 and C++14 code.

Note that this just changed the default, when told to process C++98 code 
gcc 6 does not differ in any significant way from gcc 5.

Making the code compatible with C++14 would be the best possible 
solution, but as a workaround it is possible to fix the build with
this change to tell gcc that this is C++98 code.


--- debian/rules.old2016-10-23 19:32:24.0 +
+++ debian/rules2016-10-23 19:32:31.0 +
@@ -1,4 +1,6 @@
 #!/usr/bin/make -f
 
+export DEB_CXXFLAGS_MAINT_APPEND = -std=gnu++98
+
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/cmake.mk


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#841635: marked as done (kannel-sqlbox: FTBFS: Kannel gwlib is required)

[Debian Bug Tracking System]

Your message dated Sun, 23 Oct 2016 22:10:45 +0300
with message-id <20161023191045.qjocu2psij7od...@bunk.spdns.de>
and subject line Re: Bug#828362: Acknowledgement (kannel-sqlbox: FTBFS with 
openssl 1.1.0)
has caused the Debian Bug report #841635,
regarding kannel-sqlbox: FTBFS: Kannel gwlib is required
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.)


-- 
841635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kannel-sqlbox
Version: 0.7.2-4
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/kannel-sqlbox_0.7.2-4_amd64-20160529-1433

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Control: reassign 828362 kannel-dev
Control: affects 828362 src:kannel-sqlbox
Control: retitle 828362 kannel needs binNMU when OpenSSL 1.1.0 enters unstable

On Sun, Jul 03, 2016 at 08:48:12PM +0200, Kurt Roeckx wrote:
> retitle 828362 kannel-sqlbox: FTBFS: Kannel gwlib is required
> severity 828362 serious
> thanks
> 
> It's failing with:
> checking for cfg_create in -lgwlib... no
> configure: error: Kannel gwlib is required!

After looking more into this bug, it turns out this is actually due
to OpenSSL 1.1.0

kannel-sqlbox builds fine in testing.

Trying to build kannel-sqlbox in testing plus libssl-dev from 
experimental gives the error message you got.
According to config.log, the actual error is:
  /usr/bin/ld: /usr/lib/kannel/libgwlib.a(conn.o): undefined
  reference to symbol 'SSLv23_client_method@@OPENSSL_1.0.2d'

kannel-sqlbox fails to build in unstable with the same -lgwlib error,
but this are two (sic) unrelated issues (see #837663).

A binNMU against OpenSSL 1.1.0 will be sufficient to fix this
when 1.1.0 will be in unstable (tested).

> Kurt

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#841844: libtesseract3: shared data files shipped in shared library package

[Helmut Grohne]

Package: libtesseract3
Version: 3.04.01-4.1
Severity: serious
Justification: Debian Policy section 8.2

libtesseract3 includes data files in /usr/share/tesseract-ocr/tessdata.
That filename is not versioned. After a soname bump, the new library
package will thus conflict with libtesseract3. Such behaviour is
forbidden by Debian Policy section 8.2:

| If your package contains files whose names do not change with each
| change in the library shared object version, you must not put them in
| the shared library package. 

The usual solution is to add a libtesseract-data package containing
them.

Helmut

Bug#811808: ns2: diff for NMU version 2.35+dfsg-2.1

[Mattia Rizzolo]

Control: tags 727930 + patch
Control: tags 727930 + pending
Control: tags 811808 + patch
Control: tags 811808 + pending

Dear maintainer,

I've prepared an NMU for ns2 (versioned as 2.35+dfsg-2.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:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for ns2-2.35+dfsg ns2-2.35+dfsg

 changelog  |   18 +
 compat |2 -
 control|7 --
 patches/0007-fix-build-with-gcc6.patch |   34 +
 patches/series |1 
 rules  |7 +-
 6 files changed, 65 insertions(+), 4 deletions(-)

diff -Nru ns2-2.35+dfsg/debian/changelog ns2-2.35+dfsg/debian/changelog
--- ns2-2.35+dfsg/debian/changelog	2014-11-09 13:26:27.0 +
+++ ns2-2.35+dfsg/debian/changelog	2016-10-23 18:44:37.0 +
@@ -1,3 +1,21 @@
+ns2 (2.35+dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump debhelper compat level to 10:
++ don't automatically run dh_autoreconf, as it currently makes the package
+  FTBFS.
++ dh_update_autotools_dev run is assured.  Closes: #727930
++ the install target is not parallel-safe, don't run it parallelized.
+  * Drop pointless build-dependency on quilt.
+  * Add patch fixing build with GCC 6.  Closes: #811808
+  * Apply hints from the multiarch hinters adding M-A:foreign to -doc and
+-example and M-A:same to -dbg.
+  * Add libperl4-corelibs-perl to build-dependencies, so the tests have an
+actual chance to do some good (testsuite results still being ignored).
+  * Respect DEB_BUILD_OPTIONS=nocheck.
+
+ -- Mattia Rizzolo   Sun, 23 Oct 2016 18:44:37 +
+
 ns2 (2.35+dfsg-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru ns2-2.35+dfsg/debian/compat ns2-2.35+dfsg/debian/compat
--- ns2-2.35+dfsg/debian/compat	2014-11-09 10:52:56.0 +
+++ ns2-2.35+dfsg/debian/compat	2016-10-23 17:08:14.0 +
@@ -1 +1 @@
-9
+10
diff -Nru ns2-2.35+dfsg/debian/control ns2-2.35+dfsg/debian/control
--- ns2-2.35+dfsg/debian/control	2014-11-09 13:18:41.0 +
+++ ns2-2.35+dfsg/debian/control	2016-10-23 17:40:16.0 +
@@ -3,9 +3,9 @@
 Priority: optional
 Maintainer: Debian Network Simulators Team 
 Uploaders: YunQiang Su 
-Build-Depends: debhelper (>= 9), quilt (>= 0.46-7~), cmake, 
+Build-Depends: debhelper (>= 10), cmake,
  tcl-dev, tk-dev, libxext-dev, libxt-dev, libpcap0.8-dev,
- libotcl1-dev, tclcl, libtclcl1-dev  (>=1.20-6~), perl (>=5.003)
+ libotcl1-dev, tclcl, libtclcl1-dev  (>=1.20-6~), perl (>=5.003), libperl4-corelibs-perl
 Standards-Version: 3.9.3
 Vcs-git: git://git.debian.org/git/pkg-netsim/ns2.git
 Vcs-Browser: http://git.debian.org/?p=pkg-netsim/ns2.git
@@ -32,6 +32,7 @@
 
 Package: ns2-dbg
 Architecture: any
+Multi-Arch: same
 Priority: extra
 Section: debug
 Depends: ns2 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
@@ -54,6 +55,7 @@
 
 Package: ns2-doc
 Architecture: all
+Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Section: doc
 Description: docs of ns2
@@ -75,6 +77,7 @@
 
 Package: ns2-examples
 Architecture: all
+Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Suggests: ns2
 Description: examples of ns2
diff -Nru ns2-2.35+dfsg/debian/patches/0007-fix-build-with-gcc6.patch ns2-2.35+dfsg/debian/patches/0007-fix-build-with-gcc6.patch
--- ns2-2.35+dfsg/debian/patches/0007-fix-build-with-gcc6.patch	1970-01-01 00:00:00.0 +
+++ ns2-2.35+dfsg/debian/patches/0007-fix-build-with-gcc6.patch	2016-10-23 17:35:05.0 +
@@ -0,0 +1,34 @@
+Description: Fix build with gcc-6
+Author: Mattia Rizzolo 
+Bug-Debian: https://bugs.debian.org/811808
+Last-Update: 2016-10-23
+
+--- a/mdart/mdart_adp.cc
 b/mdart/mdart_adp.cc
+@@ -105,7 +105,7 @@
+ #ifdef DEBUG_ADP
+ 	fprintf(stdout, "%.9f\tADP::sendDarq(%d)\t\t\tin node %d\twith address %s\n", CURRENT_TIME, reqId, mdart_->id_, bitString(mdart_->address_));
+ #endif
+-	nsaddr_t dstAdd_ = hash(reqId);
++	nsaddr_t dstAdd_ = ::hash(reqId);
+ #ifdef DEBUG_ADP
+ 	fprintf(stdout, "\tsending darq for node %s\n", bitString(dstAdd_));
+ #endif
+@@ -393,7 +393,7 @@
+ 	fprintf(stdout, "%.9f\tMDART::sendDaup()\t\t\t\tin node %d\twith address %s\n", CURRENT_TIME, mdart_->id_, bitString(mdart_->address_));
+ //	printDHT();
+ #endif
+-	nsaddr_t dstAdd_ = hash(mdart_->id_);
++	nsaddr_t dstAdd_ = ::hash(mdart_->id_);
+ #ifdef DEBUG_ADP
+ 	

Processed: ns2: diff for NMU version 2.35+dfsg-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 727930 + patch
Bug #727930 [src:ns2] ns2: run dh-autoreconf to update config.{sub,guess} and 
{libtool,aclocal}.m4
Ignoring request to alter tags of bug #727930 to the same tags previously set
> tags 727930 + pending
Bug #727930 [src:ns2] ns2: run dh-autoreconf to update config.{sub,guess} and 
{libtool,aclocal}.m4
Ignoring request to alter tags of bug #727930 to the same tags previously set
> tags 811808 + patch
Bug #811808 [ns2] ns2: FTBFS with GCC 6: error: reference is ambiguous
Ignoring request to alter tags of bug #811808 to the same tags previously set
> tags 811808 + pending
Bug #811808 [ns2] ns2: FTBFS with GCC 6: error: reference is ambiguous
Ignoring request to alter tags of bug #811808 to the same tags previously set

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

Processed: ns2: diff for NMU version 2.35+dfsg-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 727930 + patch
Bug #727930 [src:ns2] ns2: run dh-autoreconf to update config.{sub,guess} and 
{libtool,aclocal}.m4
Added tag(s) patch.
> tags 727930 + pending
Bug #727930 [src:ns2] ns2: run dh-autoreconf to update config.{sub,guess} and 
{libtool,aclocal}.m4
Added tag(s) pending.
> tags 811808 + patch
Bug #811808 [ns2] ns2: FTBFS with GCC 6: error: reference is ambiguous
Added tag(s) patch.
> tags 811808 + pending
Bug #811808 [ns2] ns2: FTBFS with GCC 6: error: reference is ambiguous
Added tag(s) pending.

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

Processed: Only a binNMU is required for kannel-dev

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 kannel-dev: libgwlib.a needs binNMU rebuild with MySQL 5.7 and 
> -fPIE
Bug #837663 [kannel-dev] kannel-dev: Please build libgwlib.a with -fPIC
Changed Bug title to 'kannel-dev: libgwlib.a needs binNMU rebuild with MySQL 
5.7 and -fPIE' from 'kannel-dev: Please build libgwlib.a with -fPIC'.
> severity -1 serious
Bug #837663 [kannel-dev] kannel-dev: libgwlib.a needs binNMU rebuild with MySQL 
5.7 and -fPIE
Severity set to 'serious' from 'important'
> affects -1 = src:kannel-sqlbox
Bug #837663 [kannel-dev] kannel-dev: libgwlib.a needs binNMU rebuild with MySQL 
5.7 and -fPIE
Removed indication that 837663 affects xmonad, ganeti, nwchem, acl2, psi4, 
ucspi-unix, libbonobo, ocaml-ctypes, ocaml-text, parmap, lsh-utils, pyresample, 
mclibs, axiom, proftmb, reiser4progs, lwt, snort, numexpr, partclone, 
kannel-sqlbox, tiledarray, paw, xemacs21, and psicode
Added indication that 837663 affects src:kannel-sqlbox

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

Processed: severity of 838897 is serious

[Debian Bug Tracking System]

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

> severity 838897 serious
Bug #838897 [src:jitsi] jitsi: Replace the glassfish dependencies
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#837490: libpapyrus3-dev: Please build libPapyrus3.a with -fPIC

[Steve M. Robbins]

On Mon, Sep 12, 2016 at 01:18:32AM +0200, Balint Reczey wrote:

> /usr/bin/ld:
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib/libPapyrus3.a(PapyError3.c.o):
> relocation
>  R_X86_64_32 against `.rodata.str1.8' can not be used when making a
> shared object; recompile with -fPIC
> ...

The Ubuntu notes [1] for this may apply:

Relocation Linking Failure

A dynamically linked program that pulls in a static library that was not 
built with -fPIC. These give an error like: 

relocation R_X86_64_32 against '[SYMBOL]' can not be used when
making a shared object; recompile with -fPIC To address these
types of issues, the package providing the static object needs
to be rebuilt (usually just a no-change rebuild against the
pie-by-default compiler) before rebuilding the failed package.

Did you try rebuilding libpapyrus3-dev and then using that to build gdcm?


[1] https://wiki.ubuntu.com/SecurityTeam/PIE

-Steve


signature.asc
Description: PGP signature

Processed: Add tags

[Debian Bug Tracking System]

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

> tags 804442 + pending
Bug #804442 [src:python-memory-profiler] python-memory-profiler: FTBFS: 
NameError: name 'profile' is not defined
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837490: libpapyrus3-dev: Please build libPapyrus3.a with -fPIC

[Steve M. Robbins]

On Mon, Sep 12, 2016 at 01:18:32AM +0200, Balint Reczey wrote:

> During a rebuild of all packages in sid, gdcm
> failed to build on amd64 with patched GCC and dpkg. The root
> cause seems to be that libPapyrus3.a is shipped as a non-PIC library.

That cannot be the root cause.  Debian Policy [1] is to build static
libs without -fPIC

 10.2 Libraries

 [...]  As to the static libraries, the common case is not to have
 relocatable code, since there is no benefit, unless in specific
 cases; therefore the static version must not be compiled with the
 -fPIC flag. Any exception to this rule should be discussed on the
 mailing list debian-de...@lists.debian.org, and the reasons for
 compiling with the -fPIC flag must be recorded in the file
 README.Debian.


[1] https://www.debian.org/doc/debian-policy/ch-files.html#s-libraries

-Steve


signature.asc
Description: PGP signature

Processed: Re: [Debian-med-packaging] Bug#834856: python-pysam fails to build on mips64el arch.: failed test

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #834856 [python-pysam] python-pysam fails to build on mips64el arch.: 
failed test
Severity set to 'important' from 'serious'
> retitle -1 python-pysam: FTBFS on 32-bit architectures: segmentation fault in 
> testsuite
Bug #834856 [python-pysam] python-pysam fails to build on mips64el arch.: 
failed test
Changed Bug title to 'python-pysam: FTBFS on 32-bit architectures: segmentation 
fault in testsuite' from 'python-pysam fails to build on mips64el arch.: failed 
test'.

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

Bug#834856: [Debian-med-packaging] Bug#834856: python-pysam fails to build on mips64el arch.: failed test

[Aurelien Jarno]

control: severity -1 important
control: retitle -1 python-pysam: FTBFS on 32-bit architectures: segmentation 
fault in testsuite

On 2016-10-23 12:25, Emilio Pozuelo Monfort wrote:
> On 23/10/16 00:48, Aurelien Jarno wrote:
> > On 2016-10-21 15:15, James Cowgill wrote:
> >> On 21/10/16 14:55, YunQiang Su wrote:
> >>> On Fri, Oct 14, 2016 at 3:47 PM, Emilio Pozuelo Monfort
> >>>  wrote:
>  Control: severity -1 serious
> 
>  On Fri, 19 Aug 2016 22:29:48 -0700 Afif Elghraoui  
>  wrote:
> > Control: severity -1 important
> > Control: tag -1 + help
> >
> > Hello and thank you for the report.
> >
> > على الجمعـة 19 آب 2016 ‫14:48، كتب Jonathan Jackson:
> >> Package: python-pysam
> >> Version: 0.9.1.4+ds-1
> >> Severity: grave
> >> Justification: renders package unusable
> >>
> >
> > While the package may be unusable on mips64el, it works well for the
> > vast majority of users as I understand it, so this situation deserves a
> > severity of 'important' rather than 'grave'.
> 
>  mips64el is a release architecture, thus this bug is serious.
> >>>
> >>> mips64el seems building successfully now, while mipsel fails.
> >>> I guess it is due to Loongson machine.
> >>
> >> If mips64el has built (possibly one of the build machines is 'nicer' to
> >> it), is this bug RC anymore?
> >>
> >>> Let me have a give-back on mipsel.
> >>
> >> While it could help, the same segfault happens on armel, mipsel and x32
> >> according to the build logs. I don't think it's hardware specific.
> >>
> >> https://buildd.debian.org/status/package.php?p=python-pysam
> > 
> > I agree with this analysis. I confirm it doesn't build either on
> > eller.d.o and from what I have been able to start debugging with GDB, it
> > rather looks like some bug in the 32-bit support. There is something
> > wrong in htslib or the cython code which doesn't convert C struct into
> > Python struct correctly.
> > 
> > I therefore also suggest to downgrade the severity of this bug, maybe
> > also retitling it to say it fail to all 32-bit architectures.
> 
> Sounds good.
> 

Ok, doing so with this mail.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: severity of 837925 is normal

[Debian Bug Tracking System]

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

> severity 837925 normal
Bug #837925 {Done: Marco d'Itri } [usrmerge] usrmerge: fails to 
merge with molly-guard installed
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Processed: Re: Bug#837925: usrmerge: fails to merge with molly-guard installed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #837928 [molly-guard] usrmerge: fails to merge with molly-guard installed
Severity set to 'grave' from 'important'

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

Bug#841759: smarty-gettext : Depends: php7-cli but it is not installable

[Wolfgang Schweer]

> The following packages have unmet dependencies:
>  smarty-gettext : Depends: php7-cli but it is not installable
> E: Unable to correct problems, you have held broken packages.

should either be php-cli (as it has been before, prefered) or
php7.0-cli.

Wolfgang


signature.asc
Description: Digital signature

Processed: Re: Bug#841098 closed by Andreas Henriksson <andr...@fatal.se> (Re: Bug#841098: not fixed in rygel 0.32.1-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #841098 {Done: Andreas Henriksson } [src:rygel] rygel: 
FTBFS (rygel-media-engine-test fails)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.32.1-1.

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

Bug#841098: closed by Andreas Henriksson <andr...@fatal.se> (Re: Bug#841098: not fixed in rygel 0.32.1-1)

[Guillem Jover]

Control: reopen -1

Hi!

On Thu, 2016-10-20 at 20:15:06 +, Debian Bug Tracking System wrote:
> Date: Thu, 20 Oct 2016 22:14:11 +0200
> From: Andreas Henriksson 
> To: Santiago Vila 
> Cc: 841098-d...@bugs.debian.org
> Subject: Re: Bug#841098: not fixed in rygel 0.32.1-1
> Message-ID: <20161020201411.ga27...@fatal.se>
> User-Agent: Mutt/1.5.23 (2014-03-12)
> X-Spam-Status: No, score=-8.3 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
>  RP_MATCHES_RCVD,VERSION autolearn=ham autolearn_force=no
>  version=3.4.0-bugs.debian.org_2005_01_02

> The above mentioned upload was done as a source-only upload.
> It built successfully not only in my local environment but also on *all*
> architectures (and thus on atleast one buildd for each architecture).

> This is obviously a problem in your environment.

As Santiago has shown this has also happened on the buildds, very
recent example being:

  

  


And he can still reproduce it. If this is, say, a timing issue, then it
might not always manifest itself. It does not mean it's not present. A
segfault in the buildds is a clear indication this is not an imagined
situation.

> The debian bug tracking system is not a support forum. If you need
> personal support, then you need to negotiate a support contract first.
> The debian bug tracking system is not the place for this.

I'm sorry to say but I feel this comment is inappropriate. Santiago is
doing distro-wide QA, I'd even go as far as to hazard he does not even
use this package at all!

Thanks,
Guillem

Processed (with 1 error): Re: Bug#841364: clementine: no sound at all, "GStreamer encountered a general stream error."

[Debian Bug Tracking System]

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

> severity 841364 important
Bug #841364 [clementine] clementine: no sound at all, "GStreamer encountered a 
general stream error."
Severity set to 'important' from 'grave'
> retitle 841364 clementine: unable to play anything in special
Bug #841364 [clementine] clementine: no sound at all, "GStreamer encountered a 
general stream error."
Changed Bug title to 'clementine: unable to play anything in special' from 
'clementine: no sound at all, "GStreamer encountered a general stream error."'.
> configuration cases, "GStreamer encountered a general stream error"
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#836991: golang-doc: fails to upgrade from 'jessie': error: directory '/usr/lib/go' contains files not owned by package golang-go:i386, cannot switch to symlink

[k0d]

This is what I ended up doing.  Not sure if this is correct method but
seems to have worked.  I can now perform an apt-get update && apt-get
upgrade.

sudo rm /usr/lib/go -Rf
sudo rm /usr/share/doc/golang-doc/ -Rf
sudo mkdir /usr/lib/go
sudo apt-get -f install
sudo apt-get update && apt-get upgrade

Cheers!




On Wed, 07 Sep 2016 23:18:47 +0200 Andreas Beckmann 
wrote:
> Package: golang-doc
> Version: 2:1.7~1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade
from
> 'jessie'.
> It installed fine in 'jessie', then the upgrade to 'stretch' fails.
> 
> >From the attached log (scroll to the bottom...):
> 
>   Preparing to unpack .../golang-go_2%3a1.7~1_i386.deb ...
>   dpkg-maintscript-helper: error: directory '/usr/lib/go' contains
files not owned by package golang-go:i386, cannot switch to symlink
>   dpkg: error processing archive /var/cache/apt/archives/golang-
go_2%3a1.7~1_i386.deb (--unpack):
>subprocess new pre-installation script returned error exit status
1
> 
> 
> cheers,
> 
> Andreas

Bug#841364: clementine: no sound at all, "GStreamer encountered a general stream error."

[Thomas Pierson]

severity 841364 important
retitle 841364 clementine: unable to play anything in special
configuration cases, "GStreamer encountered a general stream error"
thanks

Hi,

@Adam, I tried many migrations and I still could not reproduce your bug.
I still think that this is caused by a special use case of forcing a
sink device in the config file or something like this.
So before I get more information about your configuration, I'm lowering
the severity of this bug and retitle it because it only affect a
particular configuration case.

@Dio, I confirm with your screenshot that your issue sound like a
missing Gstreamer plugin story and it's not related with this issue.
Please open a new bug with all informations needed: what file are you
trying to play, what is exactly the error message you got.

Thanks,

Thomas Pierson

Processed: Re: vowpal-wabbit: FTBFS everywhere

[Debian Bug Tracking System]

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

> retitle 836450 FTBFS: RunTests: test 5: FAILED: 
> ref(train-sets/ref/0002a.stderr) != stderr(0002a.stderr)
Bug #836450 [src:vowpal-wabbit] vowpal-wabbit: FTBFS everywhere
Changed Bug title to 'FTBFS: RunTests: test 5: FAILED: 
ref(train-sets/ref/0002a.stderr) != stderr(0002a.stderr)' from 'vowpal-wabbit: 
FTBFS everywhere'.
> thanks
Stopping processing here.

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

Bug#836450: vowpal-wabbit: FTBFS everywhere

[Chris Lamb]

retitle 836450 FTBFS: RunTests: test 5: FAILED: 
ref(train-sets/ref/0002a.stderr) != stderr(0002a.stderr)
thanks

Looks like non-deterministic test timings...?


Regards,

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

Bug#836991: golang-doc: fails to upgrade from 'jessie': error: directory '/usr/lib/go' contains files not owned by package golang-go:i386, cannot switch to symlink

[k0d]

What is the fix for this?  I have the same problem.  Cant update
anything due to this problem.  Should any new sources be added to
/etc/apt/sources.list?


On Wed, 07 Sep 2016 23:18:47 +0200 Andreas Beckmann 
wrote:
> Package: golang-doc
> Version: 2:1.7~1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade
from
> 'jessie'.
> It installed fine in 'jessie', then the upgrade to 'stretch' fails.
> 
> >From the attached log (scroll to the bottom...):
> 
>   Preparing to unpack .../golang-go_2%3a1.7~1_i386.deb ...
>   dpkg-maintscript-helper: error: directory '/usr/lib/go' contains
files not owned by package golang-go:i386, cannot switch to symlink
>   dpkg: error processing archive /var/cache/apt/archives/golang-
go_2%3a1.7~1_i386.deb (--unpack):
>subprocess new pre-installation script returned error exit status
1
> 
> 
> cheers,
> 
> Andreas

Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

[Sascha Steinbiss]

Hi all,

thanks John for the detailed explanation and the patches.

>> So the real solution here is to revert your autoconf-archive to 6dc6cc5^
>> and use that unborked ax_with_curses.m4, which will in future be bundled
>> with samtools.
> 
> This should have been 0351b06^.

I see. For now I have bundled the correct ax_with_curses.m4 with our source 
package (alongside ax_with_htslib.m4) and use it instead of the one in 
autoconf-archive until this issue gets addressed by you upstream.

>>> Cannot open a pty at test/test.pl line 551.
> 
> I've now further tweaked test/test.pl's pty setup to skip the tests instead
> of aborting with this message.  So you may wish to pull this in as a patch
> as well as fixing /dev inside your chroot :-)
> 
> https://github.com/samtools/samtools/commit/ce4a601a0859bc9ccfcf000dddf0ac77e7d576b3

Thanks. This has fixed the problem for me. Is this solution OK for everyone?

Cheers
Sascha

Processed: Re: Bug#841532: libgit2: FTBFS under some timezones (eg. GMT-14)

[Debian Bug Tracking System]

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

> forwarded 841532 https://github.com/libgit2/libgit2/issues/3970
Bug #841532 [src:libgit2] libgit2: FTBFS under some timezones (eg. GMT-14)
Set Bug forwarded-to-address to 
'https://github.com/libgit2/libgit2/issues/3970'.
> thanks
Stopping processing here.

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

Bug#841532: libgit2: FTBFS under some timezones (eg. GMT-14)

[Chris Lamb]

forwarded 841532 https://github.com/libgit2/libgit2/issues/3970
thanks

Russell Sim wrote:

> I have forwarded this bug report upstream
> https://github.com/libgit2/libgit2/issues/3970 in the mean time I'll add
> a fix to the existing package to force tests to run in GMT timezone.

Be careful; it could mean that you are masking underlying bugs by forcing
the timezone - the code (outside of the tests) itself could be buggy!


Regards,

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

Bug#841784: gnucash: FTBFS under some timezones (eg. GMT-14)

[Chris Lamb]

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

Dear Maintainer,

gnucash fails to build from source in unstable/amd64 under 
some timezones (eg. TZ="/usr/share/zoneinfo/Etc/GMT-14").

This is due to the use of gmtime and the day "wrapping" to the
previous so the test assertion fails:

  […]
  
  FAIL: test-csv-imp
  ==
  
  /import-export/csv-imp/gnc-csv-model/parse date: 
  
(/home/lamby/temp/cdt.20161024032458.8lL14gIH7K.db.gnucash/gnucash-2.6.13/src/import-export/csv-imp/test/.libs/lt-test-csv-imp:17582):
 gnc.import.csv-ERROR **: Parse_date failed for date '2013-08-01' and format 
'0'.
  Expected result: year 113, month 7, day 1
  Obtained result: year 113, month 6, day 31
  FAIL test-csv-imp (exit status: 133)


Regards,

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


gnucash.1:2.6.13-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#841064: marked as pending

[TANIGUCHI Takaki]

tag 841064 pending
thanks

Hello,

Bug #841064 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=python-modules/packages/awscli.git;a=commitdiff;h=dfcad50

---
commit dfcad50a177cc3b459915f809510a0f6344e50c4
Author: TANIGUCHI Takaki 
Date:   Sun Oct 23 21:25:07 2016 +0900

add python3-s3transfer to B-D.

diff --git a/debian/changelog b/debian/changelog
index 3fcd869..ee20bf0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+awscli (1.11.7-2) UNRELEASED; urgency=medium
+
+  * debian/control: add python3-s3tranfert to B-D. (Closes: #841064)
+
+ -- TANIGUCHI Takaki   Sun, 23 Oct 2016 21:24:30 +0900
+
 awscli (1.11.7-1) unstable; urgency=medium
 
   * debian/control: Update Vcs-* to new git repository.

Processed: Bug#841064 marked as pending

[Debian Bug Tracking System]

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

> tag 841064 pending
Bug #841064 [src:awscli] awscli: FTBFS: ImportError: No module named 
's3transfer'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841763: unattended-upgrades: Breaks hard when apt is upgraded

[Alexandre Detiste]

Le dimanche 23 octobre 2016, 13 h 43 min 59 s CEST Santiago Vila a écrit :
> Aha! I can reproduce this too. On the machines where this happens,
> I believe I answered "yes" to a debconf question about restarting
> services automatically (one of the times I upgraded by hand and not
> using unattended-upgrades).
> 
> Maybe something like this would work as a workaround?
> 
> echo "libc6 libraries/restart-without-asking boolean false" | 
> debconf-set-selections
> 
> Thanks a lot.

Hi,

I think that adding this snippet to apt's debian/rules would fix this problem,
not tested tough.



override_dh_systemd_start:
dh_systemd_start apt-daily.timer



Without this override, we get this: apt got -daily.service got "try-restart"ed
bit this statement in atp.postinst:
-


# Automatically added by dh_systemd_start
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
_dh_action=try-restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action apt-daily.service apt-daily.timer 
>/dev/null || true
fi
# End automatically added section




Greets,

Alexandre Detiste

Bug#841763: unattended-upgrades: Breaks hard when apt is upgraded

[Santiago Vila]

On Sun, Oct 23, 2016 at 12:08:53PM +0200, Stefan Fritsch wrote:
> Package: unattended-upgrades
> Version: 0.92
> Severity: grave
> 
> Dear Maintainer,
> 
> 
> When unattended-upgrades has to upgrade apt itself, it will be
> terminated and leaves the system in a state that requires manual
> intervention, like
> 
>   dpkg --reconfigure --pending
>   apt-get -f install
> 
> 
> A second bug is that this broken state does not lead to any mails being
> sent to root, and it may take a long time until it is discovered that
> updates do not work.
> 
> Possibly, apt is killed because systemd is killing all processes
> belonging to a service when that service is stopped/restarted and maybe
> apt restarts the daily apt service. 

Aha! I can reproduce this too. On the machines where this happens,
I believe I answered "yes" to a debconf question about restarting
services automatically (one of the times I upgraded by hand and not
using unattended-upgrades).

Maybe something like this would work as a workaround?

echo "libc6 libraries/restart-without-asking boolean false" | 
debconf-set-selections

Thanks a lot.

Bug#841769: libzypp: FTBFS: tests/zypp/Capabilities_test.cc:19:26: error: 'boost::test_tools::close_at_tolerance' has not been declared

[Chris Lamb]

Source: libzypp
Version: 15.3.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,

libzypp fails to build from source in unstable/amd64:

  […]

  [ 75%] Building CXX object 
tests/zypp/CMakeFiles/Digest_test.dir/Digest_test.cc.o
  cd 
/home/lamby/temp/cdt.20161023130302.kCbukqwUX3.db.libzypp/libzypp-15.3.0/obj-x86_64-linux-gnu/tests/zypp
 && /usr/bin/g++   -DHAVE_PIPE2 -DHAVE_UDEV 
-DTESTS_BUILD_DIR=\"/home/lamby/temp/cdt.20161023130302.kCbukqwUX3.db.libzypp/libzypp-15.3.0/obj-x86_64-linux-gnu/tests\"
 
-DTESTS_SRC_DIR=\"/home/lamby/temp/cdt.20161023130302.kCbukqwUX3.db.libzypp/libzypp-15.3.0/tests\"
 -DVERSION=\"15.3.0\" -D_FILE_OFFSET_BITS=64 -D_RPM_4_X 
-D_WITH_LIBPROXY_SUPPORT_ 
-I/home/lamby/temp/cdt.20161023130302.kCbukqwUX3.db.libzypp/libzypp-15.3.0 
-I/home/lamby/temp/cdt.20161023130302.kCbukqwUX3.db.libzypp/libzypp-15.3.0/obj-x86_64-linux-gnu
 -I/usr/include/rpm -I/usr/include/libxml2 -I/usr/include/x86_64-linux-gnu 
-I/home/lamby/temp/cdt.20161023130302.kCbukqwUX3.db.libzypp/libzypp-15.3.0/tests/lib
  -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161023130302.kCbukqwUX3.db.libzypp/libzypp-15.3.0=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility-inlines-hidden -fno-strict-aliasing -fPIC -g 
-rdynamic -Wall -Woverloaded-virtual -Wnon-virtual-dtor -Wl,-as-needed 
-std=c++11 -Werror=format-security -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161023130302.kCbukqwUX3.db.libzypp/libzypp-15.3.0=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility-inlines-hidden -fno-strict-aliasing -fPIC -g 
-rdynamic -Wall -Woverloaded-virtual -Wnon-virtual-dtor -Wl,-as-needed 
-std=c++11 -O3 -DZYPP_NDEBUG   -DBOOST_TEST_DYN_LINK -DBOOST_TEST_MAIN 
-DBOOST_AUTO_TEST_MAIN=""  -o CMakeFiles/Digest_test.dir/Digest_test.cc.o -c 
/home/lamby/temp/cdt.20161023130302.kCbukqwUX3.db.libzypp/libzypp-15.3.0/tests/zypp/Digest_test.cc
  
/home/lamby/temp/cdt.20161023130302.kCbukqwUX3.db.libzypp/libzypp-15.3.0/tests/zypp/Capabilities_test.cc:19:26:
 error: 'boost::test_tools::close_at_tolerance' has not been declared
   using boost::test_tools::close_at_tolerance;
^~
  tests/zypp/CMakeFiles/Capabilities_test.dir/build.make:65: recipe for target 
'tests/zypp/CMakeFiles/Capabilities_test.dir/Capabilities_test.cc.o' failed
  make[3]: *** 
[tests/zypp/CMakeFiles/Capabilities_test.dir/Capabilities_test.cc.o] Error 1

  […]

The full build log is attached.


Regards,

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


libzypp.15.3.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Processed: bug 841110 is forwarded to https://github.com/mdadams/jasper/issues/32

[Debian Bug Tracking System]

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

> forwarded 841110 https://github.com/mdadams/jasper/issues/32
Bug #841110 [src:jasper] jasper: CVE-2016-8693
Set Bug forwarded-to-address to 'https://github.com/mdadams/jasper/issues/32'.
> thanks
Stopping processing here.

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

Bug#841768: mtasc: FTBFS: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC

[Chris Lamb]

Source: mtasc
Version: 1.14-3
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,

mtasc fails to build from source in unstable/amd64:

  […]

libxdmcp6 ocaml ocaml-base ocaml-base-nox ocaml-compiler-libs ocaml-findlib
ocaml-interp ocaml-native-compilers ocaml-nox x11proto-core-dev
x11proto-input-dev x11proto-kb-dev xorg-sgml-doctools xtrans-dev zlib1g-dev
  Suggested packages:
ncurses-doc libxcb-doc ocaml-doc tuareg-mode | ocaml-mode
  Recommended packages:
libx11-doc libfindlib-ocaml-dev ledit | readline-editor
  The following NEW packages will be installed:
camlp4 libcamlp4-ocaml-dev libextlib-ocaml libextlib-ocaml-dev
libfindlib-ocaml libncurses5-dev libpthread-stubs0-dev libtinfo-dev libx11-6
libx11-data libx11-dev libxau-dev libxau6 libxcb1 libxcb1-dev libxdmcp-dev
libxdmcp6 ocaml ocaml-base ocaml-base-nox ocaml-compiler-libs ocaml-findlib
ocaml-interp ocaml-native-compilers ocaml-nox x11proto-core-dev
x11proto-input-dev x11proto-kb-dev xorg-sgml-doctools xtrans-dev zlib1g-dev
  0 upgraded, 31 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 39.4 MB of archives.
  After this operation, 252 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 ocaml-base-nox amd64 
4.02.3-7 [539 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 libtinfo-dev amd64 
6.0+20160917-1 [77.3 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libncurses5-dev amd64 
6.0+20160917-1 [173 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 ocaml-compiler-libs 
amd64 4.02.3-7 [9443 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 ocaml-interp amd64 
4.02.3-7 [360 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 ocaml-nox amd64 
4.02.3-7 [5539 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libcamlp4-ocaml-dev 
amd64 4.02.1+3-2 [12.5 MB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 camlp4 amd64 
4.02.1+3-2 [3454 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 libextlib-ocaml amd64 
1.7.0-2+b1 [341 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 libextlib-ocaml-dev 
amd64 1.7.0-2+b1 [209 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 libxau6 amd64 
1:1.0.8-1 [20.7 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 libxdmcp6 amd64 
1:1.1.2-1.1 [26.2 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 libxcb1 amd64 1.12-1 
[133 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 libx11-data all 
2:1.6.3-1 [128 kB]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 libx11-6 amd64 
2:1.6.3-1 [742 kB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 ocaml-base amd64 
4.02.3-7 [133 kB]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 xorg-sgml-doctools 
all 1:1.11-1 [21.9 kB]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 x11proto-core-dev 
all 7.0.29-1 [728 kB]
  Get:19 http://httpredir.debian.org/debian sid/main amd64 libxau-dev amd64 
1:1.0.8-1 [23.6 kB]
  Get:20 http://httpredir.debian.org/debian sid/main amd64 libxdmcp-dev amd64 
1:1.1.2-1.1 [42.0 kB]
  Get:21 http://httpredir.debian.org/debian sid/main amd64 x11proto-input-dev 
all 2.3.2-1 [158 kB]
  Get:22 http://httpredir.debian.org/debian sid/main amd64 x11proto-kb-dev all 
1.0.7-1 [233 kB]
  Get:23 http://httpredir.debian.org/debian sid/main amd64 xtrans-dev all 
1.3.5-1 [100 kB]
  Get:24 http://httpredir.debian.org/debian sid/main amd64 
libpthread-stubs0-dev amd64 0.3-4 [3866 B]
  Get:25 http://httpredir.debian.org/debian sid/main amd64 libxcb1-dev amd64 
1.12-1 [169 kB]
  Get:26 http://httpredir.debian.org/debian sid/main amd64 libx11-dev amd64 
2:1.6.3-1 [813 kB]
  Get:27 http://httpredir.debian.org/debian sid/main amd64 ocaml amd64 4.02.3-7 
[121 kB]
  Get:28 http://httpredir.debian.org/debian sid/main amd64 
ocaml-native-compilers amd64 4.02.3-7 [2541 kB]
  Get:29 http://httpredir.debian.org/debian sid/main amd64 libfindlib-ocaml 
amd64 1.6.2-1 [160 kB]
  Get:30 http://httpredir.debian.org/debian sid/main amd64 ocaml-findlib amd64 
1.6.2-1 [274 kB]
  Get:31 http://httpredir.debian.org/debian sid/main amd64 zlib1g-dev amd64 
1:1.2.8.dfsg-2+b1 [206 kB]
  Fetched 39.4 MB in 0s (60.0 MB/s)
  Selecting previously unselected package ocaml-base-nox.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading 

Processed: forcibly merging 840841 841751

[Debian Bug Tracking System]

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

> forcemerge 840841 841751
Bug #840841 [digikam] digikam: fails to upgrade from jessie to stretch: gets 
removed, not upgraded
Bug #841751 [digikam] digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25
Bug #841751 [digikam] digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25
Merged 840841 841751
> thanks
Stopping processing here.

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