Bug#811857: fixed in synaptic 0.83+nmu1

[Jeremy Bicha]

Olly, thanks for fixing this bug.

Since Ubuntu 16.10 has gcc 6 too, the patch should also be added to
00list.Ubuntu like this:

=== modified file 'debian/patches/00list.Ubuntu'
--- debian/patches/00list.Ubuntu2016-10-02 04:10:59 +
+++ debian/patches/00list.Ubuntu2016-10-02 04:14:11 +
@@ -1,3 +1,3 @@
 01_ubuntu_changelog
 #10_ubuntu_maintenance_gui
-
+99_fix_build_with_gcc6



Thanks,
Jeremy Bicha

Processed: closing 813719

[Debian Bug Tracking System]

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

> close 813719 0.18-1
Bug #813719 [src:scikit-learn] scikit-learn: FTBFS: RuntimeError: lena() is no 
longer included in SciPy, please use ascent() or face() instead
Marked as fixed in versions scikit-learn/0.18-1.
Bug #813719 [src:scikit-learn] scikit-learn: FTBFS: RuntimeError: lena() is no 
longer included in SciPy, please use ascent() or face() instead
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: libvisca: FTBFS: dh_install: Cannot find (any matches for) "debian/tmp/usr/lib/*.so.*" (tried in "." and "debian/tmp")

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #826671 [src:libvisca] libvisca: FTBFS: dh_install: Cannot find (any 
matches for) "debian/tmp/usr/lib/*.so.*" (tried in "." and "debian/tmp")
Added tag(s) patch.

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

Bug#826671: libvisca: FTBFS: dh_install: Cannot find (any matches for) "debian/tmp/usr/lib/*.so.*" (tried in "." and "debian/tmp")

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * Use dh-autoreconf to fix FTBFS.

Thanks for considering the patch.

Logan Rosen
diff -u libvisca-1.0.1/debian/control libvisca-1.0.1/debian/control
--- libvisca-1.0.1/debian/control
+++ libvisca-1.0.1/debian/control
@@ -2,7 +2,7 @@
 Maintainer: Alan Woodland 
 Section: libdevel
 Priority: extra
-Build-depends: debhelper (>= 7), cdbs, autotools-dev, libtool, libtool-bin, autoconf, automake
+Build-depends: debhelper (>= 7), cdbs, autotools-dev, libtool, libtool-bin, autoconf, automake, dh-autoreconf
 Standards-version: 3.8.3
 Homepage: http://damien.douxchamps.net/libvisca/
 
diff -u libvisca-1.0.1/debian/rules libvisca-1.0.1/debian/rules
--- libvisca-1.0.1/debian/rules
+++ libvisca-1.0.1/debian/rules
@@ -2,6 +2,7 @@
 
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/autotools.mk
+include /usr/share/cdbs/1/rules/autoreconf.mk
 #include /usr/share/cdbs/1/rules/dpatch.mk
 #include /usr/share/dpatch/dpatch.make
 

Bug#839560: tech-ctte: failure to suspend sesion or lock computer

[Timothy Danielson]

Package: tech-ctte
Severity: serious
Tags: security
Justification: must

Dear Maintainer,

   * Q: What led up to the situation? A: attempt to lock, suspend or hibernate 
the sytemt to NOT shut down entirely.
   * Q: What exactly did you do (or not do) that was effective (or
 ineffective)? A: I attempted the three mentioned options.
   * Q: What was the outcome of this action? A: forced restart in all cases, 
resulting on fallback to journaled entries.
   * Q: What outcome did you expect instead? I expected those functions to... 
function.

-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

OK.  I’ll give it a try.

More when I know more.

Rick

On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian  wrote:

> On 2016-09-17, Rick Thomas wrote:
>> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
>>> https://bugs.debian.org/837629
>>> 
>>> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
>>> so that u-boot 2016.09 can migrate to stretch... but it would be more
>>> ideal to fix it, of course! :)
>> 
>> It looks like you’ll have to pull OpenRD support out of this version.
>> I tried 2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result
>> with it as I got with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no
>> response following u-boot “reset” command.
> 
> I've uploaded packages based on 2016.09.01 to:
> 
>  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
> 
> The repository should be signed by my key, available in the
> debian-keyring package in the archive
> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
> 
> There were two critical fixes in 2016.09.01, *maybe* they fix the issue?
> 
> If not, I'll likely be removing OpenRD* from the packages on future
> uploads.
> 
> 
> live well,
>  vagrant

Bug#832824: marked as done (haskell-src-exts: fails to build on mips64el: ghc_8.hc:(.text+0x10c): relocation truncated to fit: R_MIPS_GOT_DISP against `stg_ap_0_fast')

[Debian Bug Tracking System]

Your message dated Sun, 02 Oct 2016 00:18:47 +
with message-id 
and subject line Bug#832824: fixed in haskell-src-exts 1.17.1-2
has caused the Debian Bug report #832824,
regarding haskell-src-exts: fails to build on mips64el: ghc_8.hc:(.text+0x10c): 
relocation truncated to fit: R_MIPS_GOT_DISP against `stg_ap_0_fast'
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.)


-- 
832824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-src-exts
Version: 1.17.1-1
Severity: serious

Your package has been failing to build on mips64el for a while now:

https://buildd.debian.org/status/logs.php?pkg=haskell-src-exts&arch=mips64el

>From the last two logs:

[22 of 24] Compiling Language.Haskell.Exts.Parser ( 
src/Language/Haskell/Exts/Parser.hs, 
dist-ghc/build/Language/Haskell/Exts/Parser.p_o )
[23 of 24] Compiling Language.Haskell.Exts.Annotated ( 
src/Language/Haskell/Exts/Annotated.hs, 
dist-ghc/build/Language/Haskell/Exts/Annotated.p_o )
[24 of 24] Compiling Language.Haskell.Exts ( src/Language/Haskell/Exts.hs, 
dist-ghc/build/Language/Haskell/Exts.p_o )
dist-ghc/build/Language/Haskell/Exts/Annotated/Syntax.dyn_o: In function 
`c66jH_entry':
ghc_8.hc:(.text+0x10c): relocation truncated to fit: R_MIPS_GOT_DISP against 
`stg_ap_0_fast'
dist-ghc/build/Language/Haskell/Exts/Annotated/Syntax.dyn_o: In function 
`c66jZ_entry':
ghc_8.hc:(.text+0x18c): relocation truncated to fit: R_MIPS_GOT_DISP against 
`stg_ap_0_fast'
dist-ghc/build/Language/Haskell/Exts/Annotated/Syntax.dyn_o: In function 
`s5G5u_entry':
ghc_8.hc:(.text+0x1b4): relocation truncated to fit: R_MIPS_GOT_DISP against 
`stg_upd_frame_info'
dist-ghc/build/Language/Haskell/Exts/Annotated/Syntax.dyn_o: In function 
`c66xW_entry':
ghc_8.hc:(.text+0x32c): relocation truncated to fit: R_MIPS_GOT_DISP against 
`base_GHCziNum_zp_entry'
dist-ghc/build/Language/Haskell/Exts/Annotated/Syntax.dyn_o: In function 
`s5G5A_entry':
ghc_8.hc:(.text+0x364): relocation truncated to fit: R_MIPS_GOT_DISP against 
`stg_upd_frame_info'
dist-ghc/build/Language/Haskell/Exts/Annotated/Syntax.dyn_o: In function 
`haskezu4FklJxiwJoAI0XtFimUoU7_LanguageziHaskellziExtsziAnnotatedziSyntax_zdfFoldableAnnotation7_entry':
ghc_8.hc:(.text+0x500): relocation truncated to fit: R_MIPS_GOT_DISP against 
`ghczmprim_GHCziTypes_False_closure'
dist-ghc/build/Language/Haskell/Exts/Annotated/Syntax.dyn_o: In function 
`s5G5Z_entry':
ghc_8.hc:(.text+0x630): relocation truncated to fit: R_MIPS_GOT_DISP against 
`stg_upd_frame_info'
dist-ghc/build/Language/Haskell/Exts/Annotated/Syntax.dyn_o: In function 
`s5G62_entry':
ghc_8.hc:(.text+0x6b0): relocation truncated to fit: R_MIPS_GOT_DISP against 
`stg_upd_frame_info'
dist-ghc/build/Language/Haskell/Exts/Annotated/Syntax.dyn_o: In function 
`s5G63_entry':
ghc_8.hc:(.text+0x730): relocation truncated to fit: R_MIPS_GOT_DISP against 
`stg_upd_frame_info'
dist-ghc/build/Language/Haskell/Exts/Annotated/Syntax.dyn_o: In function 
`c66Al_entry':
ghc_8.hc:(.text+0x884): relocation truncated to fit: R_MIPS_GOT_DISP against 
`base_GHCziNum_zp_entry'
ghc_8.hc:(.text+0x8e4): additional relocation overflows omitted from the output
collect2: error: ld returned 1 exit status

I'm cc'ing debian-mips@ in case they have some insight.

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: haskell-src-exts
Source-Version: 1.17.1-2

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

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated haskell-src-exts 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, 01 Oct 2016 19:49:24 -0400
Source: haskell-src-exts
Binary: libghc-src-exts-dev libghc-src-exts-prof libghc-src-exts-doc
Architecture: source
Version: 1.17.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description:
 libghc-src-exts-dev - Haskell-Source with eXtensions library for 
GHC${haskell:ShortBlur
 libghc

Bug#839557: Package is empty (aside from man pages)

[Michael Biebl]

Package: debhelper
Version: 10.1
Severity: grave
Tags: patch

My patch to add the dh-systemd transitional package was incomplete. It
missed that debhelper was only building a single binary package and is
now building two.
We either need to add a debhelper.install file now or, as dh-systemd is
actually supposed to be empty, set --destdir=debian/debhelper when
running dh_auto_install.

Attached is a patch for the latter.

Sorry for the mess.

Michael


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

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

Versions of packages debhelper depends on:
ii  autotools-dev20160430.1
ii  binutils 2.27-8
ii  dh-autoreconf12
ii  dh-strip-nondeterminism  0.028-1
ii  dpkg 1.18.10
ii  dpkg-dev 1.18.10
ii  file 1:5.28-4
ii  libdpkg-perl 1.18.10
ii  man-db   2.7.5-1
ii  perl 5.24.1~rc3-3
ii  po-debconf   1.0.19

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201608

-- no debconf information
>From bb6ac51c480a4bff3ebb3377ec583cae22538480 Mon Sep 17 00:00:00 2001
From: Michael Biebl 
Date: Sun, 2 Oct 2016 01:41:34 +0200
Subject: [PATCH] Make sure all files are installed into the debhelper binary
 package

Now that we are building more then one binary package, dh_auto_install
no longer uses debian/debhelper by default. Since the transitional
dh-systemd package is supposed to be empty, override dh_auto_install and
set --destdir=debian/debhelper to make sure all files end up in the
debhelper binary package.
---
 debian/rules | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/rules b/debian/rules
index addfbff..b507359 100755
--- a/debian/rules
+++ b/debian/rules
@@ -16,3 +16,6 @@
 # Disable as they are unneeded (and we can then be sure debhelper
 # builds without needing autotools-dev, dh-strip-nondetermism etc.)
 override_dh_update_autotools_config override_dh_strip_nondeterminism:
+
+override_dh_auto_install:
+	dh_auto_install --destdir=debian/debhelper
-- 
2.9.3

Bug#832824: haskell-src-exts: reporting a bug at GHC for linker error. build fail on mips64el

[Clint Adams]

On Sat, Oct 01, 2016 at 04:06:15PM +0200, Florian Weimer wrote:
> So passing -mxgot would be worth a try.  This seems to be similar to
> the -fpic/-fPIC distinction.

That appears to do the trick.

Bug#839295: marked as done (groovy: FTBFS: Could not find org.ow2.asm:asm:4.x.)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 23:26:46 +
with message-id 
and subject line Bug#839295: fixed in groovy 2.4.7-2
has caused the Debian Bug report #839295,
regarding groovy: FTBFS: Could not find org.ow2.asm:asm:4.x.
to be marked as done.

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

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


-- 
839295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: groovy
Version: 2.4.7-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):
> make[1]: Entering directory '/<>'
> dh_auto_build -- --project-prop finalRelease=true dist -x :grooidjar
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian --project-prop finalRelease=true dist -x :grooidjar
> To honour the JVM settings for this build a new JVM will be forked. Please 
> consider using the daemon: 
> https://docs.gradle.org/2.13/userguide/gradle_daemon.html.
> Starting daemon process: workingDir = /<>/.gradle/daemon/2.13, 
> daemonArgs: [/usr/lib/jvm/java-8-openjdk-amd64/bin/java, 
> -XX:MaxPermSize=384m, -XX:+CMSClassUnloadingEnabled, 
> -XX:+CMSPermGenSweepingEnabled, -Xmx1G, -Dfile.encoding=UTF-8, 
> -Duser.country=US, -Duser.language=en, -Duser.variant, -cp, 
> /usr/share/gradle/lib/gradle-launcher-2.13.jar, 
> org.gradle.launcher.daemon.bootstrap.GradleDaemon, 2.13]
> Starting process 'Gradle build daemon'. Working directory: 
> /<>/.gradle/daemon/2.13 Command: 
> /usr/lib/jvm/java-8-openjdk-amd64/bin/java -XX:MaxPermSize=384m 
> -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled -Xmx1G 
> -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp 
> /usr/share/gradle/lib/gradle-launcher-2.13.jar 
> org.gradle.launcher.daemon.bootstrap.GradleDaemon 2.13
> Successfully started process 'Gradle build daemon'
> An attempt to start the daemon took 0.832 secs.
> Connected to daemon DaemonInfo{pid=32430, 
> address=[353de2de-8e21-46e7-8b7f-a10aba47eb6c port:49583, 
> addresses:[/0:0:0:0:0:0:0:1%lo, /127.0.0.1]], idle=false, 
> context=DefaultDaemonContext[uid=d68b1a02-9392-4896-9bcc-15c96d2e5aa4,javaHome=/usr/lib/jvm/java-8-openjdk-amd64,daemonRegistryDir=/<>/.gradle/daemon,pid=32430,idleTimeout=12,daemonOpts=-XX:MaxPermSize=384m,-XX:+CMSClassUnloadingEnabled,-XX:+CMSPermGenSweepingEnabled,-Xmx1G,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}.
>  Dispatching request BuildAndStop{id=8dd2668e-e1d7-4927-b917-7acc8d7f8d76.1, 
> currentDir=/<>}.
> Received result org.gradle.launcher.daemon.protocol.BuildStarted@44a59da3 
> from daemon DaemonInfo{pid=32430, 
> address=[353de2de-8e21-46e7-8b7f-a10aba47eb6c port:49583, 
> addresses:[/0:0:0:0:0:0:0:1%lo, /127.0.0.1]], idle=false, 
> context=DefaultDaemonContext[uid=d68b1a02-9392-4896-9bcc-15c96d2e5aa4,javaHome=/usr/lib/jvm/java-8-openjdk-amd64,daemonRegistryDir=/<>/.gradle/daemon,pid=32430,idleTimeout=12,daemonOpts=-XX:MaxPermSize=384m,-XX:+CMSClassUnloadingEnabled,-XX:+CMSPermGenSweepingEnabled,-Xmx1G,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}
>  (build should be starting).
> The client will now receive all logging from the daemon (pid: 32430). The 
> daemon log file: /<>/.gradle/daemon/2.13/daemon-32430.out.log
> Executing build with daemon context: 
> DefaultDaemonContext[uid=d68b1a02-9392-4896-9bcc-15c96d2e5aa4,javaHome=/usr/lib/jvm/java-8-openjdk-amd64,daemonRegistryDir=/<>/.gradle/daemon,pid=32430,idleTimeout=12,daemonOpts=-XX:MaxPermSize=384m,-XX:+CMSClassUnloadingEnabled,-XX:+CMSPermGenSweepingEnabled,-Xmx1G,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]
> Closing daemon's stdin at end of input.
> The daemon will no longer process any standard input.
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
>   Loading the Maven rules...
>   Loading the Maven rules...
> Compiling script 
> 'jar:file:/usr/share/gradle/lib/gradle-core-2.13.jar!/org/gradle/initialization/buildsrc/defaultBuildSourceScript.txt'
>  using SubsetScriptTransformer.
> Compiling script 
> 'ja

Bug#811906: marked as done (shelxle: FTBFS with GCC 6: declared in this scope)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 23:28:39 +
with message-id 
and subject line Bug#811906: fixed in shelxle 1.0.807-1
has caused the Debian Bug report #811906,
regarding shelxle: FTBFS with GCC 6: declared in this scope
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.)


-- 
811906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shelxle
Version: 1.0.748-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-not-declared

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -c -m64 -pipe -fopenmp -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT 
> -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB 
> -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. 
> -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4 -I. 
> -I/usr/X11R6/include -I. -o qrc_icons.o qrc_icons.cpp
> fcvsfo.cpp: In function 'int isnormal(double)':
> fcvsfo.cpp:624:23: error: '_finite' was not declared in this scope
>  return _finite(arg)||(arg==0);
>^
> 
> molecule.cpp: In member function 'double Molecule::dimension()':
> molecule.cpp:1976:5: warning: statement is indented as if it were guarded 
> by... [-Wmisleading-indentation]
>  if (max==0) return 10.0;
>  ^~
> 
> molecule.cpp:1970:3: note: ...this 'for' clause, but it is not
>for (int i=0;i^~~
> 
> Makefile:467: recipe for target 'fcvsfo.o' failed
> make[1]: *** [fcvsfo.o] Error 1
> make[1]: *** Waiting for unfinished jobs
> fourxle.cpp: In member function 'bool FourXle::loadFouAndPerform(const char*, 
> bool)':
> fourxle.cpp:118:22: warning: ignoring return value of 'char* fgets(char*, 
> int, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
>  fgets(line,120,f);
>   ^
> 
> fourxle.cpp:133:22: warning: ignoring return value of 'char* fgets(char*, 
> int, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
>  fgets(line,120,f);
>   ^
> 
> make[1]: Leaving directory '/<>'
> dh_auto_build: make -j30 returned exit code 2
> debian/rules:6: recipe for target 'build' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: shelxle
Source-Version: 1.0.807-1

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

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

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated shelxle 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, 02 Oct 2016 00:09:30 +0200
Source: shelxle
Binary: shelxle
Architecture: source amd64
Version: 1.0.807-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Daniel Leidert 
Description:
 shelxle- graphical user interface for SHELXL
Closes: 811906
Changes:
 shelxle (1.0.807-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes FTBFS with GCC 6 (closes: #811906).
   * debian/control (Standards-Version): Bumped to 3.9.8.
   * debian/copyright: Updated.
   * debian/patches/fix_typos.patch: Added.
 - Fixes some typos discovered by lintian.
   * debian/patches/series: Adjusted.
Checksums-Sha1:
 c7ebeb7eb47aeb88940d70bcbec73551dfbfd9b7 1950 shelxle_1.0.807-1.dsc
 d1eed7138f9a9933f8e3909b741e1a0d1e4307da 3034261 shelxle_1.0.807.orig.tar.bz2
 825e097a2f6e0fa3a5ccfe0f6a1836b0e98ece43 10152 shelxle_1.0

Bug#839345: marked as done (resteasy: FTBFS: Could not resolve dependency javax.activation:activation)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 23:28:28 +
with message-id 
and subject line Bug#839345: fixed in resteasy 3.0.19-2
has caused the Debian Bug report #839345,
regarding resteasy: FTBFS: Could not resolve dependency 
javax.activation:activation
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.)


-- 
839345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: resteasy
Version: 3.0.19-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):
>  debian/rules build
> dh build --buildsystem=maven --with javahelper
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibresteasy-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>jh_linkjars -O--buildsystem=maven
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] RESTEasy JAX-RS
> [INFO] RESTEasy JAX-RS Implementation
> [INFO] RESTEasy JAX-RS Client
> [INFO] Resteasy JAXB Provider
> [INFO] Resteasy Jettison Provider
> [INFO] Resteasy Jackson Provider
> [INFO] Resteasy Atom Provider
> [INFO] Resteasy YAML Provider
> [INFO] Resteasy HTML Provider
> [INFO] Resteasy Providers
> [INFO] RESTEasy
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building RESTEasy JAX-RS 3.0.19.Final
> [INFO] 
> 
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building RESTEasy JAX-RS Implementation 3.0.19.Final
> [INFO] 
> 
> [WARNING] The POM for javax.activation:activation:jar:debian is missing, no 
> dependency information available
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] RESTEasy JAX-RS  SUCCESS [  0.006 
> s]
> [INFO] RESTEasy JAX-RS Implementation . FAILURE [  0.182 
> s]
> [INFO] RESTEasy JAX-RS Client . SKIPPED
> [INFO] Resteasy JAXB Provider . SKIPPED
> [INFO] Resteasy Jettison Provider . SKIPPED
> [INFO] Resteasy Jackson Provider .. SKIPPED
> [INFO] Resteasy Atom Provider . SKIPPED
> [INFO] Resteasy YAML Provider . SKIPPED
> [INFO] Resteasy HTML Provider . SKIPPED
> [INFO] Resteasy Providers . SKIPPED
> [INFO] RESTEasy ... SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.542 s
> [INFO] Finished at: 2016-10-01T00:08:16+00:00
> [INFO] Final Memory: 9M/153M
> [INFO] 
> 
> [ERROR] Failed to execute goal on project resteasy-jaxrs: Could not

Processed: Re: libgweather: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #839365 [src:libgweather] libgweather: FTBFS: dh_auto_test: make -j1 check 
VERBOSE=1 returned exit code 2
Added tag(s) pending.
> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=772253
Bug #839365 [src:libgweather] libgweather: FTBFS: dh_auto_test: make -j1 check 
VERBOSE=1 returned exit code 2
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=772253'.

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

Bug#839365: libgweather: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2

[Jeremy Bicha]

Control: tags -1 + pending
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=772253

This is fixed in pkg-gnome svn with

https://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/libgweather/debian/patches/Rename-Rangoon-to-Yangon.patch?view=markup

Since I don't think this is urgent, we might just wait until GNOME
gets around to releasing a new version for this issue.

Thanks,
Jeremy

Bug#839362: marked as done (assertj-core: FTBFS: Could not resolve dependency cglib:cglib-nodep:jar:3.x)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 23:25:14 +
with message-id 
and subject line Bug#839362: fixed in assertj-core 2.3.0-3
has caused the Debian Bug report #839362,
regarding assertj-core: FTBFS: Could not resolve dependency 
cglib:cglib-nodep:jar:3.x
to be marked as done.

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

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


-- 
839362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: assertj-core
Version: 2.3.0-2
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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibassertj-core-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building AssertJ fluent assertions 2.3.0
> [INFO] 
> 
> [WARNING] The POM for cglib:cglib-nodep:jar:3.x is missing, no dependency 
> information available
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.883 s
> [INFO] Finished at: 2016-10-01T00:06:07+00:00
> [INFO] Final Memory: 10M/153M
> [INFO] 
> 
> [ERROR] Failed to execute goal on project assertj-core: Could not resolve 
> dependencies for project org.assertj:assertj-core:bundle:2.3.0: Cannot access 
> central (https://repo.maven.apache.org/maven2) in offline mode and the 
> artifact cglib:cglib-nodep:jar:3.x has not been downloaded from it before. -> 
> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US returned exit code 1
> debian/rules:4: recipe for target 'build' failed
> make: *** [build] 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

The full build log is available from:
   http://aws-log

Bug#822709: cgminer now builds with gcc 6

[Scott Howard]

Hi - I can't reproduce this anymore, and reproducible builds have been
able to compile cgminer with the new gcc default:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cgminer.html

Maybe something changed somewhere else?

Closing for now.

Thanks

Bug#822709: marked as done (cgminer: FTBFS with GCC 6: storage size of 'bitforce_drv' isn't known)

[Debian Bug Tracking System]

Your message dated Sat, 1 Oct 2016 19:08:55 -0400
with message-id 
and subject line cgminer now builds with gcc 6
has caused the Debian Bug report #822709,
regarding cgminer: FTBFS with GCC 6: storage size of 'bitforce_drv' isn't known
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.)


-- 
822709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cgminer
Version: 4.9.2-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-storage-size

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but will probably come out this week.

You can find GCC 6 in unstable (gcc-6).  To build with
GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> make[4]: Entering directory '/<>'
> gcc -DHAVE_CONFIG_H -I.  -lpthread -fno-strict-aliasing 
> -I./compat/jansson-2.6/src -I./compat/jansson-2.6/src 
> -I./compat/libusb-1.0/libusb -I./compat/libusb-1.0/libusb -I./lib -I./lib  
> -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o cgminer-cgminer.o `test -f 'cgminer.c' || echo 
> './'`cgminer.c
> In file included from ./sha2.h:36:0,
>  from cgminer.c:57:
> ./miner.h:233:21: error: storage size of 'bitforce_drv' isn't known
>   DRIVER_ADD_COMMAND(bitforce) \
>  ^
> ./miner.h:264:47: note: in definition of macro 'DRIVER_PROTOTYPE'
>  #define DRIVER_PROTOTYPE(X) struct device_drv X##_drv;
>^
> ./miner.h:260:2: note: in expansion of macro 'FPGA_PARSE_COMMANDS'
>   FPGA_PARSE_COMMANDS(DRIVER_ADD_COMMAND) \
>   ^~~
> ./miner.h:273:1: note: in expansion of macro 'DRIVER_PARSE_COMMANDS'
>  DRIVER_PARSE_COMMANDS(DRIVER_PROTOTYPE)
>  ^
> ./miner.h:234:21: error: storage size of 'modminer_drv' isn't known
>   DRIVER_ADD_COMMAND(modminer)
>  ^
> ./miner.h:264:47: note: in definition of macro 'DRIVER_PROTOTYPE'
>  #define DRIVER_PROTOTYPE(X) struct device_drv X##_drv;
>^
> ./miner.h:260:2: note: in expansion of macro 'FPGA_PARSE_COMMANDS'
>   FPGA_PARSE_COMMANDS(DRIVER_ADD_COMMAND) \
>   ^~~
> ./miner.h:273:1: note: in expansion of macro 'DRIVER_PARSE_COMMANDS'
>  DRIVER_PARSE_COMMANDS(DRIVER_PROTOTYPE)
>  ^
> ./miner.h:237:21: error: storage size of 'ants1_drv' isn't known
>   DRIVER_ADD_COMMAND(ants1) \
>  ^
> ./miner.h:264:47: note: in definition of macro 'DRIVER_PROTOTYPE'
>  #define DRIVER_PROTOTYPE(X) struct device_drv X##_drv;
>^
> ./miner.h:261:2: note: in expansion of macro 'ASIC_PARSE_COMMANDS'
>   ASIC_PARSE_COMMANDS(DRIVER_ADD_COMMAND)
>   ^~~
> ./miner.h:273:1: note: in expansion of macro 'DRIVER_PARSE_COMMANDS'
>  DRIVER_PARSE_COMMANDS(DRIVER_PROTOTYPE)
>  ^
> ./miner.h:238:21: error: storage size of 'ants2_drv' isn't known
>   DRIVER_ADD_COMMAND(ants2) \
>  ^
> ./miner.h:264:47: note: in definition of macro 'DRIVER_PROTOTYPE'
>  #define DRIVER_PROTOTYPE(X) struct device_drv X##_drv;
>^
> ./miner.h:261:2: note: in expansion of macro 'ASIC_PARSE_COMMANDS'
>   ASIC_PARSE_COMMANDS(DRIVER_ADD_COMMAND)
>   ^~~
> ./miner.h:273:1: note: in expansion of macro 'DRIVER_PARSE_COMMANDS'
>  DRIVER_PARSE_COMMANDS(DRIVER_PROTOTYPE)
>  ^
> ./miner.h:239:21: error: storage size of 'ants3_drv' isn't known
>   DRIVER_ADD_COMMAND(ants3) \
>  ^
> ./miner.h:264:47: note: in definition of macro 'DRIVER_PROTOTYPE'
>  #define DRIVER_PROTOTYPE(X) struct device_drv X##_drv;
>^
> ./miner.h:261:2: note: in expansion of macro 'ASIC_PARSE_COMMANDS'
>   ASIC_PARSE_COMMANDS(DRIVER_ADD_COMMAND)
>   ^~~
> ./miner.h:273:1: note: in expansion of macro 'DRIVER_PARSE_COMMANDS'
>  DRIVER_PARSE_COMMANDS(DRIVER_PROTOTYPE)
>  ^
> ./miner.h:240:21: error: storage size of 'avalon_drv' isn't known
>   DRIVER_ADD_COMMAND(avalon) \
>  ^
> ./miner.h:264:47: note: in definition of macro 'DRIVER_PROTOTYPE'
>  #define DRIVER_PROTOTYPE(X) struct device_drv X##_drv;
> 

Processed: Re: Bug#839362: assertj-core: FTBFS: Could not resolve dependency cglib:cglib-nodep:jar:3.x

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 assertj-core: FTBFS: Could not resolve dependency 
> cglib:cglib-nodep:jar:3.x
Bug #839362 [src:assertj-core] assertj-core: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
Changed Bug title to 'assertj-core: FTBFS: Could not resolve dependency 
cglib:cglib-nodep:jar:3.x' from 'assertj-core: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory'.

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

Bug#839362: assertj-core: FTBFS: Could not resolve dependency cglib:cglib-nodep:jar:3.x

[Emmanuel Bourg]

Control: retitle -1 assertj-core: FTBFS: Could not resolve dependency 
cglib:cglib-nodep:jar:3.x

Thank you for the report Lucas, I'm going to fix this issue. Just note
that the "No such file or directory" message you used in the bug title
isn't the cause of the build failure in this case, you'll see this with every
build using maven-debian-helper and it can be safely ignored. The
actual reason is given by Maven on the first [ERROR] line:

 [ERROR] Failed to execute goal on project assertj-core: Could not
 resolve dependencies for project org.assertj:assertj-core:bundle:2.3.0:
 Cannot access central (https://repo.maven.apache.org/maven2) in
 offline mode and the artifact cglib:cglib-nodep:jar:3.x has not been
 downloaded from it before. -> [Help 1]

This means that a dependency can't be resolved (here cglib:cglib-nodep:jar:3.x
which is currently subject to a transition).

Emmanuel Bourg

Processed: retitle 839345 to resteasy: FTBFS: Could not resolve dependency javax.activation:activation

[Debian Bug Tracking System]

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

> retitle 839345 resteasy: FTBFS: Could not resolve dependency 
> javax.activation:activation
Bug #839345 [src:resteasy] resteasy: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
Changed Bug title to 'resteasy: FTBFS: Could not resolve dependency 
javax.activation:activation' from 'resteasy: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory'.
> thanks
Stopping processing here.

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

Bug#811857: marked as done (synaptic: FTBFS with GCC 6: no matching function for call to)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 22:40:54 +
with message-id 
and subject line Bug#811857: fixed in synaptic 0.83+nmu1
has caused the Debian Bug report #811857,
regarding synaptic: FTBFS with GCC 6: no matching function for call to
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.)


-- 
811857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synaptic
Version: 0.83
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -DHAVE_CONFIG_H -I. -I.. -I../common -I../pixmaps 
> -DPACKAGE_DATA_DIR=\""/usr/share"\" 
> -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" 
> -DSYNAPTIC_GTKBUILDERDIR=\""/usr/share/synaptic/gtkbuilder/"\" 
> -DSYNAPTIC_PIXMAPDIR=\""/usr/share/synaptic/pixmaps/"\" -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/atk-1.0 -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/vte-2.91 
> -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/in
> clude/gtk-3.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 
> -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/p11-kit-1 -g 
> -O2 -c -o rgpkgtreeview.o rgpkgtreeview.cc
> rglogview.cc: In member function 'void RGLogView::readLogs()':
> rglogview.cc:89:71: error: no matching function for call to 'make_pair(int&, 
> GtkTreeIter&)'
>history_map.insert(make_pair(history_key,month_iter));
>^
> 
> In file included from /usr/include/c++/6/bits/stl_algobase.h:64:0,
>  from /usr/include/c++/6/bits/stl_tree.h:63,
>  from /usr/include/c++/6/map:60,
>  from rglogview.cc:25:
> /usr/include/c++/6/bits/stl_pair.h:406:5: note: candidate: template _T1, class _T2> constexpr std::pair std::__decay_and_strip<_Tp>::__type, typename 
> std::__decay_and_strip<_T2>::__type> std::make_pair(_T1&&, _T2&&)
>  make_pair(_T1&& __x, _T2&& __y)
>  ^
> 
> /usr/include/c++/6/bits/stl_pair.h:406:5: note:   template argument 
> deduction/substitution failed:
> rglogview.cc:89:71: note:   cannot convert 'history_key' (type 'int') to type 
> 'int&&'
>history_map.insert(make_pair(history_key,month_iter));
>^
> 
> Makefile:593: recipe for target 'rglogview.o' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: synaptic
Source-Version: 0.83+nmu1

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

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

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

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated synaptic 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...@ft

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Vagrant Cascadian]

On 2016-09-17, Rick Thomas wrote:
> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
>>  https://bugs.debian.org/837629
>> 
>> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
>> so that u-boot 2016.09 can migrate to stretch... but it would be more
>> ideal to fix it, of course! :)
>
> It looks like you’ll have to pull OpenRD support out of this version.
> I tried 2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result
> with it as I got with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no
> response following u-boot “reset” command.

I've uploaded packages based on 2016.09.01 to:

  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main

The repository should be signed by my key, available in the
debian-keyring package in the archive
(F0ADA5240891831165DF98EA7CFCD8CD257721E9).

There were two critical fixes in 2016.09.01, *maybe* they fix the issue?

If not, I'll likely be removing OpenRD* from the packages on future
uploads.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#838715: marked as done (pacemaker: properly remove CTS python files for all versions)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 22:36:56 +
with message-id 
and subject line Bug#838715: fixed in pacemaker 1.1.15-2
has caused the Debian Bug report #838715,
regarding pacemaker: properly remove CTS python files for all versions
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.)


-- 
838715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pacemaker
Version: 1.1.15-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/rules: update CTS python files' path for python3 and possibly
site-packages. If the code is updated to use setuptools, cts should
continue to not be shipped. Fixes FTBFS for arch-only builds
(LP: #1627125).

Thanks for considering the patch.

diff -Nru pacemaker-1.1.15/debian/rules pacemaker-1.1.15/debian/rules
--- pacemaker-1.1.15/debian/rules   2016-06-23 13:47:01.0 -0700
+++ pacemaker-1.1.15/debian/rules   2016-09-23 13:51:00.0 -0700
@@ -37,8 +37,11 @@
 override_dh_auto_test:
 
 override_dh_install:
+   # remove any possible python CTS files, including site-packages.
+   # If the code is updated to use setuptools, CTS should
+   # continue to not be shipped. 
rm -r   debian/tmp/usr/share/pacemaker/tests \
-   debian/tmp/usr/lib/python2.7/dist-packages/cts \
+   debian/tmp/usr/lib/python*/*packages/cts \
debian/tmp/usr/lib/*/lib*.la \
debian/tmp/usr/share/doc/pacemaker/COPYING \
debian/tmp/usr/share/doc/pacemaker/COPYING.LIB


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

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

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
Source: pacemaker
Source-Version: 1.1.15-2

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

Debian distribution maintenance software
pp.
Ferenc Wágner  (supplier of updated pacemaker 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, 01 Oct 2016 22:01:27 +0200
Source: pacemaker
Binary: pacemaker-common pacemaker-resource-agents pacemaker 
pacemaker-cli-utils pacemaker-remote pacemaker-doc libcib4 libcib-dev 
libcrmcluster4 libcrmcluster-dev libcrmcommon3 libcrmcommon-dev libcrmservice3 
libcrmservice-dev liblrmd1 liblrmd-dev libpe-rules2 libpe-status10 libpengine10 
libpengine-dev libstonithd2 libstonithd-dev libtransitioner2
Architecture: source
Version: 1.1.15-2
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Ferenc Wágner 
Description:
 libcib-dev - cluster resource manager CIB library development
 libcib4- cluster resource manager CIB library
 libcrmcluster-dev - cluster resource manager cluster library development
 libcrmcluster4 - cluster resource manager cluster library
 libcrmcommon-dev - cluster resource manager common library development
 libcrmcommon3 - cluster resource manager common library
 libcrmservice-dev - cluster resource manager service library development
 libcrmservice3 - cluster resource manager service library
 liblrmd-dev - cluster resource manager LRMD library development
 liblrmd1   - cluster resource manager LRMD library
 libpe-rules2 - cluster resource manager Policy Engine rules library
 libpe-status10 - cluster resource manager Policy Engine status library
 libpengine-dev - cluster resource manager Policy Engine library development
 libpengine10 - cluster resource manager Policy Engine library
 libstonithd-de

Bug#817563: marked as done (libxml-dumper-perl: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 22:33:12 +
with message-id 
and subject line Bug#817563: fixed in libxml-dumper-perl 0.81-1.2
has caused the Debian Bug report #817563,
regarding libxml-dumper-perl: 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.)


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

Hi,

The package libxml-dumper-perl 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: libxml-dumper-perl
Source-Version: 0.81-1.2

We believe that the bug you reported is fixed in the latest version of
libxml-dumper-perl, 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.
Chris Lamb  (supplier of updated libxml-dumper-perl 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, 26 Sep 2016 23:44:25 +0200
Source: libxml-dumper-perl
Binary: libxml-dumper-perl
Architecture: source all
Version: 0.81-1.2
Distribution: unstable
Urgency: medium
Maintainer: Florian Hinzmann 
Changed-By: Chris Lamb 
Description:
 libxml-dumper-perl - Perl module for dumping Perl objects from/to XML
Closes: 817563
Changes:
 libxml-dumper-perl (0.81-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Move to debhelper compat level 9. (Closes: #817563)
   * Move debhelper to Build-Depends (from Build-Depends-Indep) to satisfy clean
 target.
Checksums-Sha1:
 ae8aa9024cb4d644ce5dc7ef73bbb02d15c0be35 1730 libxml-dumper-perl_0.81-1.2.dsc
 8ea54a4a951f86d2e2528a4fb03734d8b944758b 3325 
libxml-dumper-perl_0.81-1.2.diff.gz
 1f8d999ed8626836f96b8b1938392e0efbcc2cf7 20740 
libxml-dumper-perl_0.81-1.2_all.deb
Checksums-Sha256:
 bc6b3584048b23224c3aea65616b16d6df7836769921b49a462b9fe8d5c2369a 1730 
libxml-dumper-perl_0.81-1.2.dsc
 4c1276bd1f09081965a7cf845e17e776727a62b8489e09382f42a70c66792d5d 3325 
libxml-dumper-perl_0.81-1.2.diff.gz
 45f7197e404e68c88e1fde68ac2378f6ab6a5fcb2208476a9fbdb5521b9d7d05 20740 
libxml-dumper-perl_0.81-1.2_all.deb
Files:
 d565894c19befc47ce3c0be9f4aba8e8 1730 perl optional 
libxml-dumper-perl_0.81-1.2.dsc
 9e3216adc8289714fafbdc56e8284386 3325 perl optional 
libxml-dumper-perl_0.81-1.2.diff.gz
 95e7924b3d73b9b028ffb93739c8199c 20740 perl optional 
libxml-dumper-perl_0.81-1.2_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX6Ze/AAoJEB6VPifUMR5YHrQP+wUbyefjDABrR2Zqnk4DLn0k
D9bAXkTYZGOlNNLSXdUB78IIN+0VK3KI7i6SRwqQvoPvwi9Kh7kmOWrJUmI0z5B9
5Q/o+WThSk3R4CGyMRtENzS3vTEVcEFMONLDe2ZFqOXTiVKm9fVNUakxD9QekV8V
sxummS3izhe46B4ZShKJrBOqmIGL9NYuzwxi5T+nixYCvpkng6CUf7vd2uMRipKv
PXqyBoWMuudj1Fq4DDyKXsLo3cdWv5zfDbHZdCatZE8q3086P2WnaFkpJBzDPtXX
l/FlGdULk8Loxf9+cT+n4L4pxDECvjBLdi/0idgu8QPkjK+e1fdAMkZgNcQsiSqO
Cmxzju1oqqN5FG2o4Ghe86eCo2vT4z9ftuW7rpS1w4jIsKJ22yaiOXZUJNiKCB+u
e8BDWcXA1OfAM3IrMXIfXMN3fNS8gT6ShRbB+7GIw7rPQzxte9hX1I07ONFM580h
fwT4oA9UKUVSuYOYIWSaP0APu/+bfjqPLOuaCB+zVLSBIfUOxjY6dqwD5YeDTUpI
67hqC23NwNIrLqoJGd2z5cf0M/mHI+jJ9QPjeSO8JDhvmQHvZh0vDC0mULyzSALI
D4mY7Tk7BG07SDZL+QHLCU+eis+Sy48sbiER8IYngoSfb1SvjFzBgVW9TnroTazq
mXcyWFkPJbLz3xkTMCjW
=EmWM
-END PGP SIGNATURE End Message ---

Bug#830410: marked as done (libxml-dumper-perl: FTBFS: make[1]: *** No rule to make target 'clean'. Stop.)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 22:33:12 +
with message-id 
and subject line Bug#817563: fixed in libxml-dumper-perl 0.81-1.2
has caused the Debian Bug report #817563,
regarding libxml-dumper-perl: FTBFS: make[1]: *** No rule to make target 
'clean'.  Stop.
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.)


-- 
817563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxml-dumper-perl
Version: 0.81-1.1
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_testdir
> dh_testroot
> rm -f build-stamp configure-stamp
> # Add here commands to clean up after the build process.
> /usr/bin/make clean
> make[1]: *** No rule to make target 'clean'.  Stop.
> make[1]: Entering directory '/«PKGBUILDDIR»'
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> make: [clean] Error 2 (ignored)
> debian/rules:38: recipe for target 'clean' failed
> dh_clean
> dh_clean: Compatibility levels before 5 are no longer supported (level 4 
> requested)
> make: *** [clean] Error 25

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/libxml-dumper-perl_0.81-1.1_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: libxml-dumper-perl
Source-Version: 0.81-1.2

We believe that the bug you reported is fixed in the latest version of
libxml-dumper-perl, 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.
Chris Lamb  (supplier of updated libxml-dumper-perl 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, 26 Sep 2016 23:44:25 +0200
Source: libxml-dumper-perl
Binary: libxml-dumper-perl
Architecture: source all
Version: 0.81-1.2
Distribution: unstable
Urgency: medium
Maintainer: Florian Hinzmann 
Changed-By: Chris Lamb 
Description:
 libxml-dumper-perl - Perl module for dumping Perl objects from/to XML
Closes: 817563
Changes:
 libxml-dumper-perl (0.81-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Move to debhelper compat level 9. (Closes: #817563)
   * Move debhelper to Build-Depends (from Build-Depends-Indep) to satisfy clean
 target.
Checksums-Sha1:
 ae8aa9024cb4d644ce5dc7ef73bbb02d15c0be35 1730 libxml-dumper-perl_0.81-1.2.dsc
 8ea54a4a951f86d2e2528a4fb03734d8b944758b 3325 
libxml-dumper-perl_0.81-1.2.diff.gz
 1f8d999ed8626836f96b8b1938392e0efbcc2cf7 20740 
libxml-dumper-perl_0.81-1.2_all.deb
Checksums-Sha256:
 bc6b3584048b23224c3aea65616b16d6df7836769921b49a462b9fe8d5c2369a 1730 
libxml-dumper-perl_0.81-1.2.dsc
 4c1276bd1f09081965a7cf845e17e776727a62b8489e09382f42a70c66792d5d 3325 
libxml-dumper-perl_0.81-1.2.diff.gz
 45f7197e404e68c88e1fde68ac2378f6ab6a5fcb2208476a9fbdb5521b9d7d05 20740 
libxml-dumper-perl_0.81-1.2_all.deb
Files:
 d565894c19befc47ce3c0be9f4aba8e8 1730 perl optional 
libxml-dumper-perl_0.81-1.2.dsc
 9e3216adc8289714fafbdc56e8284386 3325 perl optional 
libxml-dumper-perl_0.81-1.2.diff.gz
 95e7924b3d73b9b028ffb93739c8199c 20740 perl optional 
libxml-dumper-perl_0.81-1.2_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX6Ze/AAoJEB6VPifUMR5YHrQP+wUbyefjDABrR2Zqnk4DLn0k
D9bAXkTYZGOlNNLSXdUB78IIN+0VK3KI7i6SRwqQvoPvwi9Kh7kmOWrJUmI0z5B9
5Q/o+WThSk3R4CGyMRtENzS3vTEVcEFMONLDe2ZFqOXTiVKm9fVNUakxD9QekV8V
sxummS3izhe46B4ZShKJrBOqmIGL9NYuzwxi5T+nixYCvpkng6CUf7vd2uMRipKv
PXqyBoWMuudj1Fq4DDyKXsLo3cdWv5zfDbHZdCatZE8q3086P2WnaFkpJBzDPtXX
l/FlGdULk8Loxf9+cT+n4L4pxDECvjBLdi/0idgu8QPkjK+e1fdAMkZgNcQsiSqO
Cmxzju1oqqN5FG2o4Ghe86eCo2vT4z9ftuW7rpS1w4jIsKJ22yaiOX

Bug#839315: marked as done (jack-midi-clock: FTBFS: jack_midi_clock.c:669:14: error: too many arguments to function 'jack_get_time')

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 22:31:49 +
with message-id 
and subject line Bug#839315: fixed in jack-midi-clock 0.4.3-1
has caused the Debian Bug report #839315,
regarding jack-midi-clock: FTBFS: jack_midi_clock.c:669:14: error: too many 
arguments to function 'jack_get_time'
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.)


-- 
839315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jack-midi-clock
Version: 0.4.2-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):
> cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -DWITH_JITTER -DVERSION="\"0.4.2\"" 
> `pkg-config --cflags jack` -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro  
> jack_midi_clock.c `pkg-config --cflags --libs jack` -lm -lpthread  -o 
> jack_midi_clock
> jack_midi_clock.c: In function 'main':
> jack_midi_clock.c:669:14: error: too many arguments to function 
> 'jack_get_time'
> _rseed =  jack_get_time (j_client);
>   ^
> In file included from jack_midi_clock.c:27:0:
> /usr/include/jack/jack.h:1274:13: note: declared here
>  jack_time_t jack_get_time(void) JACK_OPTIONAL_WEAK_EXPORT;
>  ^
> jack_midi_clock.c: In function 'wake_main_now':
> jack_midi_clock.c:126:3: warning: ignoring return value of 'write', declared 
> with attribute warn_unused_result [-Wunused-result]
>write(wake_main_write, &c, sizeof(c));
>^
> jack_midi_clock.c: In function 'wake_main_wait':
> jack_midi_clock.c:140:4: warning: ignoring return value of 'read', declared 
> with attribute warn_unused_result [-Wunused-result]
> read(wake_main_read, &c, sizeof(c));
> ^~~
> : recipe for target 'jack_midi_clock' failed
> make[1]: *** [jack_midi_clock] 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

The full build log is available from:
   http://aws-logs.debian.net/2016/09/30/jack-midi-clock_0.4.2-1_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
jack-midi-clock, 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.
Jaromír Mikeš  (supplier of updated jack-midi-clock 
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, 01 Oct 2016 23:39:20 +0200
Source: jack-midi-clock
Binary: jack-midi-clock
Architecture: source amd64
Version: 0.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description:
 jack-midi-clock - JACK client that sends MIDI beat clock pulses
Closes: 839315
Changes:
 jack-midi-clock (0.4.3-1) unstable; urgency=medium
 .
   * New upstream version 0.4.3 (Closes: #839315)
   * Bump Standards.
   * Fix VCS fields.
   * Fix hardening.
   * Set dh/compat 10.
Checksums-Sha1:
 4ce14377f44800f66e70a1a7e6758e5965f33454 2039 jack-midi-clock_0.4.3-1.dsc
 5b020e81da0e50ca6f6c6fb970bd8039f397ccb7 19155 
jack-midi-clock_0.4.3.orig.tar.gz
 a194482ea45e17eb2d4f4e59ce518413dc0951f5 2092 
ja

Bug#839377: marked as done (chromium-browser: FTBFS: ../../printing/backend/print_backend_cups.cc:243:36: error: 'cupsGetPPD' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 22:27:15 +
with message-id 
and subject line Bug#839377: fixed in chromium-browser 53.0.2785.143-1
has caused the Debian Bug report #839377,
regarding chromium-browser: FTBFS: 
../../printing/backend/print_backend_cups.cc:243:36: error: 'cupsGetPPD' was 
not declared in this scope
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.)


-- 
839377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chromium-browser
Version: 53.0.2785.113-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):
> c++ -MMD -MF obj/printing/backend/printing.print_backend_cups.o.d 
> -DV8_DEPRECATION_WARNINGS -D_FILE_OFFSET_BITS=64 -DNO_TCMALLOC -DDISABLE_NACL 
> -DCHROMIUM_BUILD -DCR_CLANG_REVISION=274142-1 -DUI_COMPOSITOR_IMAGE_TRANSPORT 
> -DUSE_AURA=1 -DUSE_PANGO=1 -DUSE_CAIRO=1 -DUSE_DEFAULT_RENDER_THEME=1 
> -DUSE_LIBJPEG_TURBO=1 -DUSE_X11=1 -DUSE_CLIPBOARD_AURAX11=1 -DENABLE_WEBRTC=1 
> -DENABLE_MEDIA_ROUTER=1 -DUSE_PROPRIETARY_CODECS -DENABLE_PEPPER_CDMS 
> -DENABLE_NOTIFICATIONS -DUSE_UDEV -DFIELDTRIAL_TESTING_ENABLED 
> -DENABLE_TASK_MANAGER=1 -DENABLE_EXTENSIONS=1 -DENABLE_PDF=1 
> -DENABLE_PLUGINS=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1 
> -DENABLE_PRINTING=1 -DENABLE_BASIC_PRINTING=1 -DENABLE_PRINT_PREVIEW=1 
> -DENABLE_SPELLCHECK=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 
> -DENABLE_SUPERVISED_USERS=1 -DENABLE_MDNS=1 -DENABLE_SERVICE_DISCOVERY=1 
> -DV8_USE_EXTERNAL_STARTUP_DATA -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD 
> -DSAFE_BROWSING_DB_LOCAL -DPRINTING_IMPLEMENTATION -DPRINT_BACKEND_AVAILABLE 
> -DSK_SUPPORT_GPU=1 -DSK_IGNORE_DW_GRAY_FIX 
> -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS -DU_USING_ICU_NAMESPACE=0 
> -DU_ENABLE_DYLOAD=0 -DU_NOEXCEPT= -DU_STATIC_IMPLEMENTATION -DUSE_CUPS 
> -DUSE_LIBPCI=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -D__STDC_CONSTANT_MACROS 
> -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
> -D_FORTIFY_SOURCE=2 -Igen/shim_headers/ffmpeg/target -Igen -I../.. 
> -I../../skia/config -I../../third_party/khronos -I../../gpu -Igen/angle 
> -I../../third_party/skia/include/core 
> -I../../third_party/skia/include/effects -I../../third_party/skia/include/pdf 
> -I../../third_party/skia/include/gpu -I../../third_party/skia/include/lazy 
> -I../../third_party/skia/include/pathops 
> -I../../third_party/skia/include/pipe -I../../third_party/skia/include/ports 
> -I../../third_party/skia/include/utils -I../../skia/ext 
> -I../../third_party/icu/source/i18n -I../../third_party/icu/source/common 
> -fstack-protector --param=ssp-buffer-size=4  -pthread -fno-strict-aliasing 
> -Wall -Wno-extra -Wno-unused-parameter -Wno-missing-field-initializers 
> -fvisibility=hidden -pipe -fPIC -Wno-unused-local-typedefs -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -m64 
> -march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections 
> -funwind-tables -Wdate-time -D_FORTIFY_SOURCE=2 
> -fno-delete-null-pointer-checks -fuse-ld=gold -fno-delete-null-pointer-checks 
> -fuse-ld=gold -fno-exceptions -fno-rtti -fno-threadsafe-statics 
> -fvisibility-inlines-hidden -std=gnu++11 -Wno-narrowing  -c 
> ../../printing/backend/print_backend_cups.cc -o 
> obj/printing/backend/printing.print_backend_cups.o
> ../../printing/backend/print_backend_cups.cc: In member function 
> 'base::FilePath printing::PrintBackendCUPS::GetPPD(const char*)':
> ../../printing/backend/print_backend_cups.cc:243:36: error: 'cupsGetPPD' was 
> not declared in this scope
>  ppd_file_path = cupsGetPPD(name);
> ^
> ../../printing/backend/print_backend_cups.cc:256:50: error: 'cupsGetPPD2' was 
> not declared in this scope
>  ppd_file_path = cupsGetPPD2(http.http(), name);
>   ^
> [10199/20095] CXX obj/printing/printing.printing_context_linux.o
> [10200/20095] CXX obj/printing/backend/printing.cups_helper.o
> ninja: build stopped: subcommand failed.
> debian/rules:130: recipe for target 'override_dh_auto_build-arch' failed
> make[1]: *** [override_dh_auto_build-arch] 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 re

Bug#831268: marked as done (synaptic: FTBFS: cacheset.h:718:15: error: 'make_unsigned' in namespace 'std' does not name a template type)

[Debian Bug Tracking System]

Your message dated Sun, 2 Oct 2016 10:16:51 +1300
with message-id <20161001211651.chn7a6jbzt26a...@survex.com>
and subject line Re: Bug#831268: synaptic: FTBFS: cacheset.h:718:15: error: 
'make_unsigned' in namespace 'std' does not name a template type
has caused the Debian Bug report #831268,
regarding synaptic: FTBFS: cacheset.h:718:15: error: 'make_unsigned' in 
namespace 'std' does not name a template type
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.)


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

Hi,

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

Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/apt-pkg  
> -DSYNAPTICLOCALEDIR=\""/usr/share/locale"\" 
> -DSYNAPTICSTATEDIR=\""/var/lib/synaptic"\"-g -O2 -c -o rinstallprogress.o 
> rinstallprogress.cc
> In file included from /usr/include/apt-pkg/edsp.h:12:0,
>  from /usr/include/apt-pkg/packagemanager.h:27,
>  from rinstallprogress.h:29,
>  from rinstallprogress.cc:38:
> /usr/include/apt-pkg/cacheset.h:718:15: error: 'make_unsigned' in namespace 
> 'std' does not name a template type
>   typedef std::make_unsigned::type size_type;
>^
> In file included from /usr/include/apt-pkg/packagemanager.h:27:0,
>  from rinstallprogress.h:29,
>  from rinstallprogress.cc:38:
> /usr/include/apt-pkg/edsp.h:270:45: error: '>>' should be '> >' within a 
> nested template argument list
>std::list> &actions,
>  ^
> /usr/include/apt-pkg/edsp.h:272:64: error: '>>' should be '> >' within a 
> nested template argument list
> bool ApplyRequest(std::list> &actions,
> ^
> rinstallprogress.cc: In member function 'virtual 
> pkgPackageManager::OrderResult RInstallProgress::start(pkgPackageManager*, 
> int, int)':
> rinstallprogress.cc:127:35: warning: 'pkgPackageManager::OrderResult 
> pkgPackageManager::DoInstallPostFork(int)' is deprecated: Use 
> APT::Progress::PackageManager subclass instead of fd 
> [-Wdeprecated-declarations]
>res = pm->DoInstallPostFork();
>^
> In file included from rinstallprogress.h:29:0,
>  from rinstallprogress.cc:38:
> /usr/include/apt-pkg/packagemanager.h:134:95: note: declared here
> APT_DEPRECATED_MSG("Use APT::Progress::PackageManager subclass instead of 
> fd") OrderResult DoInstallPostFork(int statusFd=-1);
>   
>  ^
> make[4]: *** [rinstallprogress.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/synaptic_0.83_unstable_gcc5.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 ---
On Thu, Jul 14, 2016 at 12:01:12PM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/apt-pkg  
> > -DSYNAPTICLOCALEDIR=\""/usr/share/locale"\" 
> > -DSYNAPTICSTATEDIR=\""/var/lib/synaptic"\"-g -O2 -c -o 
> > rinstallprogress.o rinstallprogress.cc
> > In file included from /usr/include/apt-pkg/edsp.h:12:0,
> >  from /usr/include/apt-pkg/packagemanager.h:27,
> >  from rinstallprogress.h:29,
> >  from rinstallprogress.cc:38:
> > /usr/include/apt-pkg/cacheset.h:718:15: error: 'make_unsigned' in namespace 
> > 'std' does not name a template type
> >   typedef std::make_unsigned::type 
> > size_type;
> >^

std::make_unsigned() is new in C++11:

http://en.cppreference.com/w/cpp/types/make_unsigned

> > In file included from /usr/include/apt-pkg/packagemanager.h:27:0,
> >  from rinstallprogress.h:29,
> >  from rinstallprogress.cc:38:
> > /usr/include/apt-pkg/edsp.h:270:45: erro

Bug#811857: synaptic: diff for NMU version 0.83+nmu1

[Olly Betts]

Control: tags 811857 + patch

Dear maintainer,

I've prepared an NMU for synaptic (versioned as 0.83+nmu1) and
uploaded it under the zero-day NMU rules as this FTBFS was blocking
the auto-xapian-core transition.

The patch applied was cherry-picked from your git repo.

Cheers,
Olly
diff -Nru synaptic-0.83/debian/changelog synaptic-0.83+nmu1/debian/changelog
--- synaptic-0.83/debian/changelog	2016-01-11 22:20:13.0 +1300
+++ synaptic-0.83+nmu1/debian/changelog	2016-10-02 09:50:57.0 +1300
@@ -1,3 +1,11 @@
+synaptic (0.83+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with GCC6 (Closes: #811857)
++ New patch 99_fix_build_with_gcc6, cherry-picked from git.
+
+ -- Olly Betts   Sun, 02 Oct 2016 09:50:57 +1300
+
 synaptic (0.83) unstable; urgency=medium
 
   [ xuzhen ]
diff -Nru synaptic-0.83/debian/patches/00list synaptic-0.83+nmu1/debian/patches/00list
--- synaptic-0.83/debian/patches/00list	2016-01-11 22:22:42.0 +1300
+++ synaptic-0.83+nmu1/debian/patches/00list	2016-10-02 09:50:57.0 +1300
@@ -0,0 +1 @@
+99_fix_build_with_gcc6
diff -Nru synaptic-0.83/debian/patches/00list.Debian synaptic-0.83+nmu1/debian/patches/00list.Debian
--- synaptic-0.83/debian/patches/00list.Debian	2016-01-11 22:20:13.0 +1300
+++ synaptic-0.83+nmu1/debian/patches/00list.Debian	2016-10-02 09:49:29.0 +1300
@@ -0,0 +1 @@
+99_fix_build_with_gcc6
diff -Nru synaptic-0.83/debian/patches/99_fix_build_with_gcc6.dpatch synaptic-0.83+nmu1/debian/patches/99_fix_build_with_gcc6.dpatch
--- synaptic-0.83/debian/patches/99_fix_build_with_gcc6.dpatch	1970-01-01 12:00:00.0 +1200
+++ synaptic-0.83+nmu1/debian/patches/99_fix_build_with_gcc6.dpatch	2016-10-02 09:50:39.0 +1300
@@ -0,0 +1,38 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 99_fix_build_with_gcc6.dpatch
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: commit a18b8e55c78f735446db69010872b66e8fbd5ff4
+## DP: Author: Michael Vogt 
+## DP: Date:   Thu Jan 21 16:59:53 2016 +0100
+## DP: 
+## DP: Fix build with gcc6
+## DP: 
+## DP: The make_pair() functions does not take a template parameter
+## DP: anymore.
+## DP: 
+## DP: Thanks: Martin Michlmayer
+## DP: Closes: #811857
+
+@DPATCH@
+diff --git a/gtk/rglogview.cc b/gtk/rglogview.cc
+index b55bc8da..317457d2 100644
+--- a/gtk/rglogview.cc
 b/gtk/rglogview.cc
+@@ -23,6 +23,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ 
+ #include "config.h"
+@@ -86,7 +87,7 @@ void RGLogView::readLogs()
+ 			 COLUMN_LOG_TYPE, LOG_TYPE_TOPLEVEL, 
+ 			 -1);
+ 	 g_free(sort_key);
+-	 history_map.insert(make_pair(history_key,month_iter));
++	 history_map.insert(std::make_pair(history_key,month_iter));
+   } else {
+ 	 month_iter = history_map[history_key];
+   }


signature.asc
Description: PGP signature

Bug#817347: marked as done (anon-proxy: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 22:19:45 +
with message-id 
and subject line Bug#817347: fixed in anon-proxy 00.05.38+20081230-4
has caused the Debian Bug report #817347,
regarding anon-proxy: 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.)


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

Hi,

The package anon-proxy 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: anon-proxy
Source-Version: 00.05.38+20081230-4

We believe that the bug you reported is fixed in the latest version of
anon-proxy, 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.
Chris Lamb  (supplier of updated anon-proxy 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, 01 Oct 2016 20:44:37 +0100
Source: anon-proxy
Binary: anon-proxy
Architecture: source amd64
Version: 00.05.38+20081230-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Chris Lamb 
Description:
 anon-proxy - Proxy to surf the web anonymously
Closes: 817347
Changes:
 anon-proxy (00.05.38+20081230-4) unstable; urgency=medium
 .
   * QA upload.
   * Move to debhelper compat 9. (Closes: #817347)
   * Bump Standards-Version to 3.9.8.
Checksums-Sha1:
 60c44dffea51f5efdb5e60fc1d2006b91f4697af 1813 
anon-proxy_00.05.38+20081230-4.dsc
 7105002dc818c52bc268fca227eb87bfed4571ca 1883873 
anon-proxy_00.05.38+20081230.orig.tar.gz
 3508c15ade58fbcae425ba641ed8b5ba3e6af21e 46738 
anon-proxy_00.05.38+20081230-4.diff.gz
 221c3a73751edf402c915abc6768736ccdea8595 15558 
anon-proxy-dbgsym_00.05.38+20081230-4_amd64.deb
 d3f1d93cea886ac0c344127fe9c9d30d5cc34d45 125700 
anon-proxy_00.05.38+20081230-4_amd64.deb
Checksums-Sha256:
 53ee4cae0bffd2421abf87ab958117f904ba6c3dfa656f3f12c20b931b0970c5 1813 
anon-proxy_00.05.38+20081230-4.dsc
 db6310fc54dc0b52d523ecbc229fa762698c3ea2fb852c389021a115f41336e1 1883873 
anon-proxy_00.05.38+20081230.orig.tar.gz
 4c3e5d0d3f8ffbf71fc2bdbc5ae30842730176982d89eb026e9479bac4e0ca15 46738 
anon-proxy_00.05.38+20081230-4.diff.gz
 bdb7fafc88a9d2edfd8789a157fafa7ad111c4bf4b10360c1df705090961ae68 15558 
anon-proxy-dbgsym_00.05.38+20081230-4_amd64.deb
 6b156c3926018d1f5a4c07c73cb6cebaebeef844433a08f45061343ff541b637 125700 
anon-proxy_00.05.38+20081230-4_amd64.deb
Files:
 637e8562f1f301997b19863b1f9361d9 1813 web optional 
anon-proxy_00.05.38+20081230-4.dsc
 71c238a1e219809ef8df0758b0ef4c9b 1883873 web optional 
anon-proxy_00.05.38+20081230.orig.tar.gz
 7ab1cf1ce7b9d5afe6c9a506b65db952 46738 web optional 
anon-proxy_00.05.38+20081230-4.diff.gz
 953a9b97f5961d2d7ec28abcd5da1e60 15558 debug extra 
anon-proxy-dbgsym_00.05.38+20081230-4_amd64.deb
 b99f41ed087096818a5fd6a6cedecec1 125700 web optional 
anon-proxy_00.05.38+20081230-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX8BLyAAoJEB6VPifUMR5YyGEP/jnekgLSfBqtxLk0YsMbVy8+
BpMEphwlZtejZMXhP5LZyUnwsNZFyOB7bhngiT8dqyuD/mNK5JruLYTZh/ncQA3U
DkUFwkS6Oav4n/YB8Gxd0HMmfCNFr8EaIeanI+ueJ94BrKhW698iKwp4Ioyq6GLr
PCldYDCgi9dHUZ8JZFnM2YfKwGYXfohqHaMASpEOcpZiURado2O7KOpRuCzpAKdZ
DLCD+ZQJCKKzeodFYL/vccNZzhBxn665N6aMLB9gZNnigyvIHVL6383W/5DWZJBC
lwxN51s369oyaB3HDRYHfT5UlkZWEDOFk0rQqjl6lHMavaJid9wC1fvf+dw59o9m
HJuu3NBW0P88wm/oz2bvi4ZgtvRQE7S0gEtN8MtdmvP8TbOugiQAof2H2JCK5G5r
CthdaZiDeXb6FyseX4rcoqkFwrqAmD8ykzdloXFjMmhaWn6eJnXiMCWMS7g2UjTA
80inPKTJ/Bw3W58CTSz4YUqRucUlmFrxJKFU6JcyfC8RZwbKOHwLWT728TU6mGhf
GIXoqRSE1Gxnd2eoQW5ffb

Bug#797271: Synaptic false positive, does not launch

[Olly Betts]

Control: severity -1 important
Control: tags -1 + unreproducible

On Fri, Aug 28, 2015 at 09:57:08PM -0400, Carlos Kosloff wrote:
> I did not do anything except dist-upgrade my system with apt-get.
> All of a sudden synaptic will not launch.
> Reports a false positive, bad password given for root.
> This is not correct because I can launch synaptic from console as root.
> I think that this bug arises from a faulty implementation of policykit-1

I just NMUed synaptic, and while testing my build I couldn't reproduce
this issue.  Hence lowering severity and tagging as unreproducible.

Cheers,
Olly

Processed: Re: Bug#797271: Synaptic false positive, does not launch

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #797271 [synaptic] Synaptic false positive, does not launch
Severity set to 'important' from 'grave'
> tags -1 + unreproducible
Bug #797271 [synaptic] Synaptic false positive, does not launch
Added tag(s) unreproducible.

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

Processed: synaptic: diff for NMU version 0.83+nmu1

[Debian Bug Tracking System]

Processing control commands:

> tags 811857 + patch
Bug #811857 [synaptic] synaptic: FTBFS with GCC 6: no matching function for 
call to
Added tag(s) patch.

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

Bug#839315: marked as pending

[Jaromír Mikeš]

tag 839315 pending
thanks

Hello,

Bug #839315 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-multimedia/jack-midi-clock.git;a=commitdiff;h=8dcec11

---
commit 8dcec11a4c558079a285c5cc9a3bdb5174060673
Author: Jaromír Mikeš 
Date:   Sat Oct 1 23:55:55 2016 +0200

Finalize changelog.

diff --git a/debian/changelog b/debian/changelog
index 9418466..ca9e295 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,10 @@
-jack-midi-clock (0.4.3-1) UNRELEASED; urgency=medium
+jack-midi-clock (0.4.3-1) unstable; urgency=medium
 
-  * New upstream version 0.4.3
+  * New upstream version 0.4.3 (Closes: #839315)
+  * Bump Standards.
+  * Fix VCS fields.
+  * Fix hardening.
+  * Set dh/compat 10.
 
  -- Jaromír Mikeš   Sat, 01 Oct 2016 23:39:20 +0200
 

Processed: Bug#839315 marked as pending

[Debian Bug Tracking System]

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

> tag 839315 pending
Bug #839315 [src:jack-midi-clock] jack-midi-clock: FTBFS: 
jack_midi_clock.c:669:14: error: too many arguments to function 'jack_get_time'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#817742: yaret: Removal of debhelper compat 4

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Bump to 10.
  * debian/control:
- Build-depend on debhelper (>= 10).
- Move all Build-Depends-Indep to Build-Depends, since they're used in
  the clean target.

Thanks for considering the patch.

Logan Rosen
diff -u yaret-2.1.0/debian/control yaret-2.1.0/debian/control
--- yaret-2.1.0/debian/control
+++ yaret-2.1.0/debian/control
@@ -2,7 +2,7 @@
 Section: sound
 Priority: optional
 Maintainer: Marco Nenciarini 
-Build-Depends-Indep: cdbs, debhelper (>= 5.0.0), quilt
+Build-Depends: cdbs, debhelper (>= 10), quilt
 Standards-Version: 3.6.2.2
 
 Package: yaret
diff -u yaret-2.1.0/debian/compat yaret-2.1.0/debian/compat
--- yaret-2.1.0/debian/compat
+++ yaret-2.1.0/debian/compat
@@ -1 +1 @@
-4
+10

Processed: Re: yaret: Removal of debhelper compat 4

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #817742 [src:yaret] yaret: Removal of debhelper compat 4
Added tag(s) patch.

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

Bug#701367: marked as done (toonloop: ftbfs with GCC-4.8)

[Debian Bug Tracking System]

Your message dated Sat, 1 Oct 2016 23:32:04 +0300
with message-id <20161001203204.cutuyqvwhgzsf...@bunk.spdns.de>
and subject line Closing bugs in the removed toonloop
has caused the Debian Bug report #701367,
regarding toonloop: ftbfs with GCC-4.8
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.)


-- 
701367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:toonloop
Version: 2.2.0-1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.8

The package fails to build in a test rebuild on at least amd64 with
gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The
severity of this report may be raised before the jessie release.

  configure: error: missing package: libboost-thread-dev

The full build log can be found at:
http://people.debian.org/~doko/logs-20130217/gcc48/toonloop_2.2.0-1_unstable_gcc48.log
The last lines of the build log are at the end of this report.

To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev

The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues
might be caused by the updated glibc.

[...]
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking dependency style of g++... none
checking whether ln -s works... yes
checking for ANSI C header files... (cached) yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking for unistd.h... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for an ANSI C-conforming const... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether gcc needs -traditional... no
checking for inet_ntoa... yes
checking for memset... yes
checking for socket... yes
checking for pthread_exit in -lpthread... yes
checking for sin in -lm... yes
checking for LIBLO... yes
checking for GST... yes
checking for GSTAPP... yes
checking for CLUTTER... yes
checking for CLUTTERGST... yes
checking for RAW1394... yes
checking for AVC1394... yes
checking for LIBXML... yes
checking for boostlib >= 1.35... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options-mt... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem-mt... yes
checking whether the Boost::Thread library is available... no
configure: error: missing package: libboost-thread-dev
make: *** [debian/stamp-autotools] Error 1
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
toonloop was removed from unstable in 2014.

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#721368: marked as done (toonloop: FTBFS with newer boost.)

[Debian Bug Tracking System]

Your message dated Sat, 1 Oct 2016 23:32:04 +0300
with message-id <20161001203204.cutuyqvwhgzsf...@bunk.spdns.de>
and subject line Closing bugs in the removed toonloop
has caused the Debian Bug report #701367,
regarding toonloop: FTBFS with newer boost.
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.)


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

Package: toonloop
Severity: serious
Version: 2.2.0-1
Tags: patch

Toonloop fails to build with boost 1.54

checking for boostlib >= 1.35... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options... yes
checking whether the Boost::Filesystem library is available... no
configure: error: missing package: libboost-filesystem-dev
make: *** [debian/stamp-autotools] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
root@debian:/toonloop-2.2.0#

root@debian:/toonloop-2.2.0# dpkg -l libboost-filesystem-dev
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  libboost-files 1.54.0.1 amd64filesystem operations 
(portable p

root@debian:/toonloop-2.2.0#

From config.log

/usr/include/boost/filesystem/config.hpp:16:5: error: #error Compiling 
Filesystem versio
#   error Compiling Filesystem version 3 file with 
BOOST_FILESYSTEM_VERSION defined !=

^
configure:17193: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "TOONLOOP"
| #define PACKAGE_TARNAME "toonloop"
| #define PACKAGE_VERSION "2.2.0"
| #define PACKAGE_STRING "TOONLOOP 2.2.0"
| #define PACKAGE_BUGREPORT "supp...@toonloop.com"
| #define PACKAGE_URL "http://www.toonloop.com";
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR ".libs/"
| #define PACKAGE "toonloop"
| #define VERSION "2.2.0"
| #define PACKAGE_VERSION_MAJOR 2
| #define PACKAGE_VERSION_MINOR 2
| #define PACKAGE_VERSION_MICRO 0
| #define STDC_HEADERS 1
| #define HAVE_ARPA_INET_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_SYS_IOCTL_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE__BOOL 1
| #define HAVE_STDBOOL_H 1
| #define HAVE_INET_NTOA 1
| #define HAVE_MEMSET 1
| #define HAVE_SOCKET 1
| #define HAVE_BOOST /**/
| #define HAVE_BOOST_PROGRAM_OPTIONS /**/
| /* end confdefs.h.  */
| #include 
| int
| main ()
| {
| using namespace boost::filesystem;
|path my_path( "foo/bar/data.txt" );
|return 0;
|   ;
|   return 0;
| }
configure:17207: result: no
configure:17371: error: missing package: libboost-filesystem-dev

I initally saw this on a raspbian buildd but I can reproduce it in a sid 
amd64 chroot.


In raspbian I fixed this by changing the build dependencies to force 
boost 1.49, a debdiff for that is attatched


diff -Nru toonloop-2.2.0/debian/changelog toonloop-2.2.0/debian/changelog
--- toonloop-2.2.0/debian/changelog 2012-04-29 11:49:18.0 +
+++ toonloop-2.2.0/debian/changelog 2013-08-30 10:49:53.0 +
@@ -1,3 +1,9 @@
+toonloop (2.2.0-1+rpi1) jessie-staging; urgency=low
+
+  * Use boost 1.49 explicitly to avoid error from configure script.
+
+ -- Peter Michael Green   Fri, 30 Aug 2013 10:49:36 
+
+
 toonloop (2.2.0-1) unstable; urgency=low
 
   * New upstream stable release (source identical to 2.1.18).
diff -Nru toonloop-2.2.0/debian/control toonloop-2.2.0/debian/control
--- toonloop-2.2.0/debian/control   2012-04-29 11:49:18.0 +
+++ toonloop-2.2.0/debian/control   2013-08-30 10:47:10.0 +
@@ -17,12 +17,12 @@
  help2man,
  libasound2-dev,
  libavc1394-dev,
- libboost-date-time-dev,
- libboost-filesystem-dev,
- libboost-program-options-dev,
- libboost-signals-dev,
- libboost-system-dev,
- libboost-thread-dev,
+ libboost-date-time1.49-dev,
+ libboost-filesystem1.49-dev,
+ libboost-program-options1.49-dev,
+ libboost-signals1.49-dev,
+ libboost-system1.49-dev,
+ libboost-thread1.49-dev,
  libclutter-1.0-dev,
  libclutter-gst-dev,
  libglew-dev,
--- End Message 

Processed: merging

[Debian Bug Tracking System]

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

> reassign 839312 golang-github-prometheus-common-dev
Bug #839312 [src:prometheus] prometheus: FTBFS: dh_auto_build: go install -v -p 
1 -ldflags  -X github.com/prometheus/common/version.Version=1.1.2+ds -X 
github.com/prometheus/common/version.Revision=1.1.2+ds-2 -X 
github.com/prometheus/common/version.Branch=debian/sid -X 
github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
 -X github.com/prometheus/common/version.BuildDate=20160910-20:06:40 -X 
github.com/prometheus/common/version.GoVersion=go1.7.1 
github.com/prometheus/prometheus/cmd/prometheus 
github.com/prometheus/prometheus/cmd/promtool 
github.com/prometheus/prometheus/config 
github.com/prometheus/prometheus/notifier 
github.com/prometheus/prometheus/promql 
github.com/prometheus/prometheus/relabel 
github.com/prometheus/prometheus/retrieval 
github.com/prometheus/prometheus/retrieval/discovery 
github.com/prometheus/prometheus/retrieval/discovery/consul 
github.com/prometheus/prometheus/retrieval/discovery/dns 
github.com/prometheus/prometheus/retrieval/discovery/kubernetes 
github.com/prometheus/prometheus/retrieval/discovery/marathon 
github.com/prometheus/prometheus/rules github.com/prometheus/prometheus/storage 
github.com/prometheus/prometheus/storage/local 
github.com/prometheus/prometheus/storage/local/codable 
github.com/prometheus/prometheus/storage/local/index 
github.com/prometheus/prometheus/storage/local/storagetool 
github.com/prometheus/prometheus/storage/metric 
github.com/prometheus/prometheus/storage/remote 
github.com/prometheus/prometheus/storage/remote/graphite 
github.com/prometheus/prometheus/storage/remote/influxdb 
github.com/prometheus/prometheus/storage/remote/opentsdb 
github.com/prometheus/prometheus/template 
github.com/prometheus/prometheus/util/cli 
github.com/prometheus/prometheus/util/flock 
github.com/prometheus/prometheus/util/httputil 
github.com/prometheus/prometheus/util/stats 
github.com/prometheus/prometheus/util/strutil 
github.com/prometheus/prometheus/util/testutil 
github.com/prometheus/prometheus/util/treecache 
github.com/prometheus/prometheus/vendor/github.com/influxdb/influxdb/client 
github.com/prometheus/prometheus/vendor/github.com/influxdb/influxdb/tsdb 
github.com/prometheus/prometheus/web 
github.com/prometheus/prometheus/web/api/v1 
github.com/prometheus/prometheus/web/ui returned exit code 2
Bug reassigned from package 'src:prometheus' to 
'golang-github-prometheus-common-dev'.
No longer marked as found in versions prometheus/1.1.2+ds-2.
Ignoring request to alter fixed versions of bug #839312 to the same values 
previously set
> reassign 839360 golang-github-prometheus-common-dev
Bug #839360 [src:prometheus-alertmanager] prometheus-alertmanager: FTBFS: 
dh_auto_build: go install -v -p 1 -ldflags  -X 
github.com/prometheus/common/version.Version=0.3.0+ds -X 
github.com/prometheus/common/version.Revision=0.3.0+ds-2 -X 
github.com/prometheus/common/version.Branch=debian/sid -X 
github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
 -X github.com/prometheus/common/version.BuildDate=20160715-12:56:49 -X 
github.com/prometheus/common/version.GoVersion=go1.7.1 
github.com/prometheus/alertmanager github.com/prometheus/alertmanager/config 
github.com/prometheus/alertmanager/notify 
github.com/prometheus/alertmanager/provider 
github.com/prometheus/alertmanager/provider/boltmem 
github.com/prometheus/alertmanager/provider/sqlite 
github.com/prometheus/alertmanager/template 
github.com/prometheus/alertmanager/template/internal/deftmpl 
github.com/prometheus/alertmanager/test 
github.com/prometheus/alertmanager/types 
github.com/prometheus/alertmanager/vendor/github.com/prometheus/client_golang/api/alertmanager
 returned exit code 2
Bug reassigned from package 'src:prometheus-alertmanager' to 
'golang-github-prometheus-common-dev'.
No longer marked as found in versions prometheus-alertmanager/0.3.0+ds-2.
Ignoring request to alter fixed versions of bug #839360 to the same values 
previously set
> merge 839360 839312
Bug #839360 [golang-github-prometheus-common-dev] prometheus-alertmanager: 
FTBFS: dh_auto_build: go install -v -p 1 -ldflags  -X 
github.com/prometheus/common/version.Version=0.3.0+ds -X 
github.com/prometheus/common/version.Revision=0.3.0+ds-2 -X 
github.com/prometheus/common/version.Branch=debian/sid -X 
github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
 -X github.com/prometheus/common/version.BuildDate=20160715-12:56:49 -X 
github.com/prometheus/common/version.GoVersion=go1.7.1 
github.com/prometheus/alertmanager github.com/prometheus/alertmanager/config 
github.com/prometheus/alertmanager/notify 
github.com/prometheus/alertmanager/provider 
github.com/prometheus/alertmanager/provider/boltmem 
github.com/prometheus/alertmanager/provider/sqlite 
github.com/prometheus/alertmanager/template 
github.com/prometheus/alertmanager/

Bug#839317: [pkg-golang-devel] Bug#839317: golang-1.7: FTBFS: tests failed

[Florian Weimer]

* Lucas Nussbaum:

>> --- FAIL: TestLoadFixed (0.00s)
>>  time_test.go:943: Now().In(loc).Zone() = "-01", -3600, want
>> "GMT+1", -3600

Is this due to a tzdata change?

Bug#822671: initramfs-tools: preserves unmodified /etc/initramfs-tools/initramfs.conf on upgrades from jessie

[Ben Hutchings]

On Fri, 2016-09-30 at 09:57 +1000, Andrew Worsley wrote:
> Hi, I am a newbie (have a mentor account and looking to help)
> I just looked into this bug and tried to apply the patch - but it
> appears the files are missing - perhaps way out of date?
[...]

The patch applies for me with 'patch -p1'.  But I haven't yet taken the
time to try it out.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy
others.


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

Bug#822418: marked as done (twisted-web2: FTBFS: twisted.python.dist module not found)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 20:50:25 +0100
with message-id 
<1475351425.188387.742967481.22507...@webmail.messagingengine.com>
and subject line Re: twisted-web2: FTBFS: twisted.python.dist module not found
has caused the Debian Bug report #822418,
regarding twisted-web2: FTBFS: twisted.python.dist module not found
to be marked as done.

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

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


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

twisted-web2 fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'twisted-web2-build-deps' in 
'../twisted-web2-build-deps_8.1.0-3_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package twisted-web2-build-deps.
  (Reading database ... 23003 files and directories currently installed.)
  Preparing to unpack twisted-web2-build-deps_8.1.0-3_all.deb ...
  Unpacking twisted-web2-build-deps (8.1.0-3) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
libexpat1-dev libpython-all-dev libpython-dev libpython2.7 libpython2.7-dev
python-all python-all-dev python-attr python-cffi-backend
python-cryptography python-dev python-enum34 python-idna python-ipaddress
python-openssl python-pyasn1 python-pyasn1-modules python-service-identity
python-twisted-bin python-twisted-core python-zope.interface python2.7-dev
  Suggested packages:
python-cryptography-doc python-cryptography-vectors python-enum34-doc
python-openssl-doc python-openssl-dbg doc-base python-twisted-bin-dbg
python-tk python-gtk2 python-glade2 python-qt3 python-wxgtk3.0
  Recommended packages:
python-pam python-serial
  The following NEW packages will be installed:
libexpat1-dev libpython-all-dev libpython-dev libpython2.7 libpython2.7-dev
python-all python-all-dev python-attr python-cffi-backend
python-cryptography python-dev python-enum34 python-idna python-ipaddress
python-openssl python-pyasn1 python-pyasn1-modules python-service-identity
python-twisted-bin python-twisted-core python-zope.interface python2.7-dev
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 31.8 MB of archives.
  After this operation, 62.1 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 python-all amd64 
2.7.11-1 [936 B]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 libpython2.7 amd64 
2.7.11-8 [1069 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libexpat1-dev amd64 
2.1.1-1 [126 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libpython2.7-dev 
amd64 2.7.11-8 [27.8 MB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libpython-dev amd64 
2.7.11-1 [19.6 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libpython-all-dev 
amd64 2.7.11-1 [952 B]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 python2.7-dev amd64 
2.7.11-8 [278 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 python-dev amd64 
2.7.11-1 [1116 B]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 python-all-dev amd64 
2.7.11-1 [956 B]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 python-twisted-bin 
amd64 16.1.1-1 [19.6 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 
python-zope.interface amd64 4.1.3-1+b1 [87.3 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 python-cffi-backend 
amd64 1.5.2-1+b1 [64.3 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 python-enum34 all 
1.1.2-1 [35.9 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 python-idna all 
2.1-1 [31.4 kB]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 python-ipaddress all 
1.0.16-1 [17.9 kB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 python-pyasn1 all 
0.1.9-1 [51.4 kB]
  G

Bug#821819: marked as done (sympa: upgrade overwrites configfiles with debconf values)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 19:28:59 +
with message-id 
and subject line Bug#821819: fixed in sympa 6.2.16~dfsg-1
has caused the Debian Bug report #821819,
regarding sympa: upgrade overwrites configfiles with debconf values
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.)


-- 
821819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sympa
Version: 6.1.11~dfsg-5+deb7u2
Severity: serious
Justification: Policy 10.7.3

Dear Maintainer,

installing any updated sympa package overwrites changes to configuration files
using values stored in debconf. The packages config script must give preference
to values from the configuration file. Currently values are only extracted from
configuration files if a debconf value is not present. See also debconf-devel(7)
section "Config file handling".

best regards
Maurice Massar


-- System Information:
Debian Release: 7.10
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sympa depends on:
ii  adduser  3.113+nmu3
ii  ca-certificates  20130119+deb7u1
ii  dbconfig-common  1.8.47+nmu1+deb7u1
ii  debconf [debconf-2.0]1.5.49
ii  dpkg 1.16.17
ii  libarchive-zip-perl  1.30-6
ii  libc62.13-38+deb7u10
ii  libcgi-fast-perl 5.14.2-21+deb7u3
ii  libdbd-mysql-perl4.021-1+b1
ii  libdbd-pg-perl   2.19.2-2+deb7u1
ii  libdbd-sqlite3-perl  1.37-1
ii  libdbd-sybase-perl   1.14-1
ii  libdbi-perl  1.622-1+deb7u1
ii  libfcgi-perl 0.74-1+b1
ii  libfile-copy-recursive-perl  0.38-1
ii  libhtml-format-perl  2.10-1
ii  libhtml-stripscripts-parser-perl 1.03-1
ii  libhtml-tree-perl5.02-1
ii  libintl-perl 1.20-1
ii  libio-stringy-perl   2.110-5
ii  libmailtools-perl2.09-1
ii  libmime-charset-perl 1.009.2-1
ii  libmime-encwords-perl1.012.4-1
ii  libmime-lite-html-perl   1.23-1.1
ii  libmime-tools-perl   5.503-1
ii  libmsgcat-perl   1.03-5+b2
ii  libnet-ldap-perl 1:0.4400-1
ii  libnet-netmask-perl  1.9016-1
ii  libregexp-common-perl2011121001-1
ii  libtemplate-perl 2.24-1
ii  libterm-progressbar-perl 2.13-1
ii  libunicode-linebreak-perl0.0.20120401-1
ii  libxml-libxml-perl   2.0001+dfsg-1+deb7u1
ii  lsb-base 4.1+Debian8+deb7u1
ii  mhonarc  2.6.18-2
ii  perl 5.14.2-21+deb7u3
ii  perl-modules [libcgi-pm-perl]5.14.2-21+deb7u3
ii  rsyslog [system-log-daemon]  5.8.11-3+deb7u2
ii  sendmail-bin [mail-transport-agent]  8.14.4-4+deb7u1
ii  sqlite3  3.7.13-1+deb7u2

Versions of packages sympa recommends:
ii  apache2-suexec 2.2.22-13+deb7u6
pn  doc-base   
ii  libapache2-mod-fcgid   1:2.3.6-1.2+deb7u1
ii  libcrypt-ciphersaber-perl  0.61-4
ii  libfile-nfslock-perl   1.21-1
ii  libio-socket-ssl-perl  1.76-2
ii  libmail-dkim-perl  0.39-1
ii  libsoap-lite-perl  0.714-1
ii  locales2.13-38+deb7u10
ii  logrotate  3.8.1-4
ii  postgresql 9.1+134wheezy4

Versions of packages sympa suggests:
ii  apache2 2.2.22-13+deb7u6
ii  apache2-mpm-worker [httpd-cgi]  2.2.22-13+deb7u6
pn  libauthcas-perl 
pn  libdbd-oracle-perl  
pn  libtext-wrap-perl   
ii  openssl 1.0.1e-2+deb7u20

-- Configuration Files:
/etc/sympa/topics.conf changed [not included]

-- debconf information:
...
  wwsympa/fastcgi: false
...
--- End Message ---
--- Begin Message ---
Source: sympa
Source-Version: 6.2.16~dfsg-1

We believe that the bug you reported is fixed in the latest version of
sympa, 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 y

Bug#839348: astroml: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13

[Ole Streicher]

Control: reassign -1 python-sklearn 0.18-1
Control: retitle -1 python-sklearn: wrong import of "parallel"
Control: affects -1 src:astroml

This is a bug in scikit-learn, not in astroml:

$ python
Python 2.7.12+ (default, Sep  1 2016, 20:27:38) 
[GCC 6.2.0 20160822] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sklearn.mixture
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/sklearn/mixture/__init__.py", line 5, 
in 
from .gmm import sample_gaussian, log_multivariate_normal_density
  File "/usr/lib/python2.7/dist-packages/sklearn/mixture/gmm.py", line 27, in 

from .. import cluster
  File "/usr/lib/python2.7/dist-packages/sklearn/cluster/__init__.py", line 6, 
in 
from .spectral import spectral_clustering, SpectralClustering
  File "/usr/lib/python2.7/dist-packages/sklearn/cluster/spectral.py", line 16, 
in 
from ..metrics.pairwise import pairwise_kernels
  File "/usr/lib/python2.7/dist-packages/sklearn/metrics/__init__.py", line 33, 
in 
from . import cluster
  File "/usr/lib/python2.7/dist-packages/sklearn/metrics/cluster/__init__.py", 
line 20, in 
from .unsupervised import silhouette_samples
  File 
"/usr/lib/python2.7/dist-packages/sklearn/metrics/cluster/unsupervised.py", 
line 13, in 
from ..pairwise import pairwise_distances
  File "/usr/lib/python2.7/dist-packages/sklearn/metrics/pairwise.py", line 27, 
in 
from ..externals.joblib import parallel
ImportError: cannot import name parallel

It is a regression; 0.17.1-2 (in testing) works fine.

Best regards

Ole

Processed: Re: astroml: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python-sklearn 0.18-1
Bug #839348 [src:astroml] astroml: FTBFS: dh_auto_test: pybuild --test 
--test-nose -i python{version} -p 2.7 returned exit code 13
Bug reassigned from package 'src:astroml' to 'python-sklearn'.
No longer marked as found in versions astroml/0.3-5.
Ignoring request to alter fixed versions of bug #839348 to the same values 
previously set
Bug #839348 [python-sklearn] astroml: FTBFS: dh_auto_test: pybuild --test 
--test-nose -i python{version} -p 2.7 returned exit code 13
Marked as found in versions scikit-learn/0.18-1.
> retitle -1 python-sklearn: wrong import of "parallel"
Bug #839348 [python-sklearn] astroml: FTBFS: dh_auto_test: pybuild --test 
--test-nose -i python{version} -p 2.7 returned exit code 13
Changed Bug title to 'python-sklearn: wrong import of "parallel"' from 
'astroml: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 
2.7 returned exit code 13'.
> affects -1 src:astroml
Bug #839348 [python-sklearn] python-sklearn: wrong import of "parallel"
Added indication that 839348 affects src:astroml

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

Bug#839372: marked as done (luminance-hdr: FTBFS: Option release requires an argument)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 18:34:00 +
with message-id 
and subject line Bug#839372: fixed in luminance-hdr 2.4.0-9
has caused the Debian Bug report #839372,
regarding luminance-hdr: FTBFS: Option release requires an argument
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.)


-- 
839372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: luminance-hdr
Version: 2.4.0-8
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):
> make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [100%] Building CXX object 
> test/WhiteBalance/CMakeFiles/WhiteBalance.dir/WhiteBalanceMain.cpp.o
> cd /<>/obj-x86_64-linux-gnu/test/WhiteBalance && /usr/bin/c++   
> -DBRANCH_PREDICTION -DDEMOSAICING_GPL2 -DDEMOSAICING_GPL3 -DHAVE_CCFITS 
> -DHAVE_FFTW3F -DLHDR_CXX11_ENABLED -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
> -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB 
> -I/usr/include/exiv2 -I/usr/include/x86_64-linux-gnu -I/usr/include/OpenEXR 
> -I/usr/include/libraw -I/<>/src 
> -I/<>/obj-x86_64-linux-gnu/src 
> -I/<>/obj-x86_64-linux-gnu -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -std=c++11 -fopenmp  
>  -Wall -Wno-unknown-pragmas -ffast-math -fPIC -o 
> CMakeFiles/WhiteBalance.dir/WhiteBalanceMain.cpp.o -c 
> /<>/test/WhiteBalance/WhiteBalanceMain.cpp
> [100%] Linking CXX executable WhiteBalance
> cd /<>/obj-x86_64-linux-gnu/test/WhiteBalance && /usr/bin/cmake 
> -E cmake_link_script CMakeFiles/WhiteBalance.dir/link.txt --verbose=1
> /usr/bin/c++   -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -std=c++11 -fopenmp   -Wl,-z,relro -Wl,-z,now 
> -Wl,--as-needed CMakeFiles/WhiteBalance.dir/WhiteBalanceMain.cpp.o  -o 
> WhiteBalance -rdynamic -Xlinker --start-group ../../src/Libpfs/libpfs.a 
> ../../src/TonemappingOperators/libpfstmo.a 
> ../../src/HdrCreation/libhdrcreation.a ../../src/MainCli/libmain_cli.a 
> ../../src/Common/libcommon.a ../../src/OsIntegration/libosintegration.a 
> ../../src/Core/libcore.a ../../src/Exif/libexif.a 
> ../../src/Fileformat/libfileformat.a ../../src/Alignment/libalign.a 
> ../../src/HdrWizard/libhdrwizard-cli.a ../../src/Alignment/libalign.a 
> ../../src/Viewers/libviewers.a -Xlinker --end-group -lcfitsio -lCCfits -lHalf 
> -lIex -lIlmImf -lIlmThread -lImath -ltiff -lraw_r -lfftw3f -lfftw3f_threads 
> -lgsl -lgslcblas -lexiv2 -ljpeg -llcms2 -lpng -lz -lboost_program_options 
> /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5.6.1 
> /usr/lib/x86_64-linux-gnu/libQt5Sql.so.5.6.1 
> /usr/lib/x86_64-linux-gnu/libQt5Concurrent.so.5.6.1 
> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.6.1 
> /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.6.1 
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1 
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [100%] Built target WhiteBalance
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> /usr/bin/cmake -E cmake_progress_start 
> /<>/obj-x86_64-linux-gnu/CMakeFiles 0
> make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
>   cd /<>
> # Build the minimal manpage:
> pod2man --center='Minimal luminance-hdr manpage' \
>   --release='' \
>   debian/luminance-hdr.pod > debian/luminance-hdr.1
> Option release requires an argument
> debian/rules:26: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] 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

The full build log is available from:
   http:

Bug#838792: marked as done (openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 18:35:20 +
with message-id 
and subject line Bug#838792: fixed in openmw 0.40.0-2
has caused the Debian Bug report #838792,
regarding openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr
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.)


-- 
838792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openmw
Version: 0.40.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

openmw/experimental FTBFS on armhf:

https://buildd.debian.org/status/fetch.php?pkg=openmw&arch=armhf&ver=0.40.0-1&stamp=1474694818

In file included from /usr/include/osg/GL:113:0,
 from /usr/include/osg/GLDefines:25,
 from /usr/include/osg/GLExtensions:18,
 from /usr/include/osg/State:18,
 from /usr/include/osg/GraphicsContext:17,
 from /usr/include/osgViewer/GraphicsWindow:17,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:19,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
/usr/include/GLES2/gl2.h:69:25: error: conflicting declaration 'typedef 
khronos_ssize_t GLsizeiptr'
 typedef khronos_ssize_t GLsizeiptr;
 ^~
In file included from /usr/include/GL/gl.h:2055:0,
 from /usr/include/qt4/QtOpenGL/qgl.h:88,
 from /usr/include/qt4/QtOpenGL/QGLWidget:1,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:17,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
/usr/include/GL/glext.h:468:19: note: previous declaration as 'typedef 
ptrdiff_t GLsizeiptr'
 typedef ptrdiff_t GLsizeiptr;
   ^~
In file included from /usr/include/osg/GL:113:0,
 from /usr/include/osg/GLDefines:25,
 from /usr/include/osg/GLExtensions:18,
 from /usr/include/osg/State:18,
 from /usr/include/osg/GraphicsContext:17,
 from /usr/include/osgViewer/GraphicsWindow:17,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:19,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
/usr/include/GLES2/gl2.h:70:26: error: conflicting declaration 'typedef 
khronos_intptr_t GLintptr'
 typedef khronos_intptr_t GLintptr;
  ^~~~
In file included from /usr/include/GL/gl.h:2055:0,
 from /usr/include/qt4/QtOpenGL/qgl.h:88,
 from /usr/include/qt4/QtOpenGL/QGLWidget:1,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:17,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
/usr/include/GL/glext.h:469:19: note: previous declaration as 'typedef 
ptrdiff_t GLintptr'
 typedef ptrdiff_t GLintptr;
   ^~~~


Andreas
--- End Message ---
--- Begin Message ---
Source: openmw
Source-Version: 0.40.0-2

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

Debian distribution maintenance software
pp.
Bret Curtis  (supplier of updated openmw 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: Sat, 01 Oct 2016 08:14:09 +0200
Source: openmw
Binary: openmw openmw-cs openmw-data openmw-launcher
Architecture: source amd64 all
Version: 0.40.0-2
Distribution: unstable
Urgency: low
Maintainer: Bret Curtis 
Changed-By: Bret Curtis 
Description:
 openmw - Reimplementation of The Elder Scrolls III: Morrowind
 openmw-cs  - Replacement of The Elder Scrolls Construction Set
 openmw-data - Resources for the OpenMW engine
 openmw-launcher - Launcher for OpenMW using the Qt-Gui-Toolkit
Closes: 838792
Changes:
 openmw (0.40.0-2) unstable; urgency=low
 .
   [ Bret Curtis ]
   * Fix armhf problems (Closes: #838792)
Checksums-Sha1:
 6f8446390c3b27af957b670aca48aab4b921e4f6 2531 openmw_0.40.0-2.dsc
 cf48518179d0d93b5c99ff3d42c8e2c9df260193 7900 openmw_0.40.0-2.debian.tar.xz
 909b0d5e8c7fd104d2

Bug#784845: marked as done (libdevel-gdb-perl: FTBFS: t/expect.t #8 sometimes fails)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 18:29:47 +
with message-id 
and subject line Bug#784845: fixed in libdevel-gdb-perl 2.02-4
has caused the Debian Bug report #784845,
regarding libdevel-gdb-perl: FTBFS: t/expect.t #8 sometimes 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.)


-- 
784845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdevel-gdb-perl
Version: 2.02-2
Severity: normal
User: debian-p...@lists.debian.org
Usertags: autopkgtest

This package recently failed its autopkgtest checks on ci.debian.net:
 http://ci.debian.net/packages/libd/libdevel-gdb-perl/unstable/amd64/

It seems to work for me with a couple of tries, so presumably it's either
some sort of a race condition or specific to the ci.debian.net setup.
Further investigation needed.

t/expect.t ... 
1..8
ok 1 - use Devel::GDB;
ok 2
ok 3
Reading symbols from /usr/bin/perl...
(no debugging symbols found)...done.
ok 4
ok 5
ok 6
ok 7
not ok 8

#   Failed test at t/expect.t line 30.
# Looks like you failed 1 test of 8.
close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/8 subtests 

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libdevel-gdb-perl
Source-Version: 2.02-4

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libdevel-gdb-perl 
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, 01 Oct 2016 20:08:31 +0200
Source: libdevel-gdb-perl
Binary: libdevel-gdb-perl
Architecture: source
Version: 2.02-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 784845
Description: 
 libdevel-gdb-perl - module to open and communicate with a gdb session
Changes:
 libdevel-gdb-perl (2.02-4) unstable; urgency=medium
 .
   * Remove Deepak Tripathi from Uploaders. Thanks for your work!
   * Drop Split-brittle-test-into-two-smaller-ones.patch which was meant
 for debugging test issues.
   * Skip test t/expect.t during build and autopkgtest. The test causes
 occasional, probably timing-related, failures. (Closes: #784845)
   * Drop libexpect-perl from Build-Depends-Indep. Not needed after the
 relevant test was disabled.
   * Update years of packaging copyright.
Checksums-Sha1: 
 ac8c650fb207d73235fff0a77d94a941d27812b7 2269 libdevel-gdb-perl_2.02-4.dsc
 95c0b864b9fbb21bb1f81ac6e9cf2a4c9646c6b3 4016 
libdevel-gdb-perl_2.02-4.debian.tar.xz
Checksums-Sha256: 
 7560f0b703878f8a2be0daba9c2318b7df27202846836ce0e3f9b17a70f32fc0 2269 
libdevel-gdb-perl_2.02-4.dsc
 0ef79e5a7af107e676bb00aca996f09d97ee055f00bd2e657af76c1c94cc331c 4016 
libdevel-gdb-perl_2.02-4.debian.tar.xz
Files: 
 432a6263ebee62f56f5d7d55c593f079 2269 perl optional 
libdevel-gdb-perl_2.02-4.dsc
 ab89d1b2a263d296a47abfa64ae52756 4016 perl optional 
libdevel-gdb-perl_2.02-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJX7/vgXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGEQMQALb1ONKwP2kMztBVscLF6KYV
5ruqhROjHAaYdW6dR1XbWYfEttsx8p9rQZI007YHXceAixBQuxiOSWoyed/1UFD/
i58PBCWFrph/DPZtMUrVzIis+EUGKPrIWrilgz50A/McmfgUl6EmF/hbUenFaxKN
pJ72a77Bz37cMHytMVyBOiMBwVaP+diqAyxBlCQnKq+DZ5SJR9T6lo1iYUlWNSeH
2x6+9IN0aZXYgKdrfTGfuy23fD0XJOhR+KyUHSuySiUsv9xKE4ejdWr7BStUWJDy
oqrEZQvjBGhwg1w+foAbws5T1eiGealPj5y2sv9GZ204kCdhasEGRhOrglblWae7
KvtqG8Gn8lntLeqXHwKJofUCaNyVkcOJGyaBSIPoRGV0Kd71KmzdgezTd9yxt5wh
aeGhF4PnKkPC+z1dMN079/lSP9SUqjaHMJVpJ5sJW4ofdR9ntZbxS388SXOkkYuY
POyP/+L3nAuM88cj/BU4cU8byHD75OF+kuB2vJTLgQMO2gqY97c1e3fafiEe5tt7
eXhJUIITh6AlIlSrAOt2ftjw5eeZH3lxfKTVOA70ZURVxWx43n4Xr7PmF3OQlrUA
FgvapFNllyDj9vPu+d4rNDlt1nuZr5hP/++7jdsQKJkQZKp0JScBOPiOMk0zCNPH
FH0mJoozh2E4oAf4XNhU
=iNBc
-END PGP SIGNATURE End Message ---

Processed: Pending fixes for bugs in the libdevel-gdb-perl package

[Debian Bug Tracking System]

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

> tag 784845 + pending
Bug #784845 [libdevel-gdb-perl] libdevel-gdb-perl: FTBFS: t/expect.t #8 
sometimes fails
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#784845: libdevel-gdb-perl: autopkgtest failure in t/expect.t

[gregor herrmann]

On Sun, 25 Sep 2016 13:04:33 +0200, gregor herrmann wrote:

> Currently I'm very tempted to disable t/expect.t since it's both
> unreproducible for me and undebuggable with my amount of tuits.

Done.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#784845: Pending fixes for bugs in the libdevel-gdb-perl package

[pkg-perl-maintainers]

tag 784845 + pending
thanks

Some bugs in the libdevel-gdb-perl package are closed in revision
f7f2c98f4690cd5d4ad455838a45484c3e5134b5 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdevel-gdb-perl.git/commit/?id=f7f2c98

Commit message:

Skip test t/expect.t during build and autopkgtest.

The test causes occasional, probably timing-related, failures.

Closes: #784845

Processed: tagging 839372

[Debian Bug Tracking System]

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

> # fixed in git
> tags 839372 + pending
Bug #839372 [src:luminance-hdr] luminance-hdr: FTBFS: Option release requires 
an argument
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#839312: [pkg-go] Bug#839312: prometheus: FTBFS: dh_auto_build: go install -v -p 1 -ldflags -X github.com/prometheus/common/version.Version=1.1.2+ds -X github.com/prometheus/common/version.Revision

[Martín Ferrari]

On 01/10/16 10:50, Lucas Nussbaum wrote:

> Justification: FTBFS on amd64 

>> # github.com/prometheus/prometheus/web
>> src/github.com/prometheus/prometheus/web/web.go:118: not enough arguments in 
>> call to route.New

> 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

Both these bugs are caused by the same issue: I uploaded a new version
of the common prometheus library a bit too soon, since upstream does
niot make releases for it, I did not know it was not safe..

-- 
Martín Ferrari (Tincho)

Bug#839375: marked as done (python-uniconvertor: FTBFS: Option release requires an argument)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 17:33:37 +
with message-id 
and subject line Bug#839375: fixed in python-uniconvertor 1.1.5-3
has caused the Debian Bug report #839375,
regarding python-uniconvertor: FTBFS: Option release requires an argument
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.)


-- 
839375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-uniconvertor
Version: 1.1.5-2
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):
> make[1]: Entering directory '/<>'
> pod2man --section=1 --release= debian/uniconvertor.pod > uniconvertor.1
> Option release requires an argument
> debian/rules:11: recipe for target 'override_dh_installman' failed
> make[1]: *** [override_dh_installman] 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

The full build log is available from:
   
http://aws-logs.debian.net/2016/09/30/python-uniconvertor_1.1.5-2_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
python-uniconvertor, 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.
Chris Lamb  (supplier of updated python-uniconvertor 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, 01 Oct 2016 16:14:52 +0100
Source: python-uniconvertor
Binary: python-uniconvertor python-uniconvertor-dbg
Architecture: source amd64
Version: 1.1.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Chris Lamb 
Description:
 python-uniconvertor - Universal vector graphics translator
 python-uniconvertor-dbg - Universal vector graphics translator (debug 
extension)
Closes: 839375
Changes:
 python-uniconvertor (1.1.5-3) unstable; urgency=medium
 .
   * QA upload.
   * Fix "Option release requires an argument" FTBFS by adding a missing
 definition of VERSION to debian/rules. (Closes: #839375)
   * Bump Standards-Version to 3.9.8.
   * Run ``wrap-and-sort``.
   * Also clean generated uniconvertor.1 file in clean target.
Checksums-Sha1:
 cd3e783c406f406b2cbcca97bbf23cc36965c52a 1958 python-uniconvertor_1.1.5-3.dsc
 51ec7c4487048c3357ed95cdb4ab3524018a2c9e 246998 
python-uniconvertor_1.1.5.orig.tar.gz
 17a20166e644097971f3d4e0850c6de097b3c8ae 5104 
python-uniconvertor_1.1.5-3.debian.tar.xz
 2df0e7c5bab4cf2d23c0a95c930aaf1cf1fece18 375244 
python-uniconvertor-dbg_1.1.5-3_amd64.deb
 521ce1f99f2175d0629d13330b855792b65362d5 225994 
python-uniconvertor_1.1.5-3_amd64.deb
Checksums-Sha256:
 0de630c0503424468e5037cfa0adda0817da0b436b3252f91e517c3be01cb1ea 1958 
python-uniconvertor_1.1.5-3.dsc
 c3a9ecb70779911470e01c6b1950b07fc2fe1880777a1e70e44251323f4d5882 246998 
python-uniconvertor_1.1.5.orig.tar.gz
 9d22fa0154308ceceda961477323bd2b4653c17b81c12bd5d6f5cc668fb511ec 5104 
python-uniconvertor_1.1.5-3.debian.tar.xz
 bddff31c92d6a572d875e9e9e3010aad7e8980beca38fd857ac14314ace88e31 375244 
python-uniconvertor-dbg_1.1.5-3_amd64.deb
 d57f058f8380ea0e2847b5854362f1df4968fa23af70eab652beded91e5148e1 225994 
python-uniconvertor_1.1.5-3_amd64.deb
Files:
 6f529e57005234b32d30c179

Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

[Mattia Rizzolo]

On Mon, Sep 19, 2016 at 10:44:21PM +0200, Hilmar Preuße wrote:
> On 19.09.2016 19:29, Niels Thykier wrote:
> > On Sat, 17 Sep 2016 22:36:20 +0200 Hilmar Preusse  wrote:
> 
> Hi,
> 
> >> Is it OK to simply remove that check? Is there an replacement for
> >> hardening-check?
> >>
> > Hi Hilmar :)
> > 
> > I believe you can just remove that check.
> > 
> Done in git, tag pending.

Can you also upload it?

We want to remove the whole hardening-wrapper package, and ~everything
is already uploaded (either in the archive or as NMU in the DEFERRED
queue).

-- 
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  `-


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 832931 10.0.27-1
Bug #832931 [src:mariadb-10.0] mariadb-10.0: FTBFS on powerpc
Marked as fixed in versions mariadb-10.0/10.0.27-1.
> thanks
Stopping processing here.

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

Bug#827199: hfst: FTBFS: twolc test fails on big-endian systems

[Emilio Pozuelo Monfort]

On Wed, 15 Jun 2016 17:03:20 +0200 Tino Didriksen  wrote:
> On 13 June 2016 at 18:00, Aaron M. Ucko  wrote:
> 
> > Justification: fails to build from source (but built successfully in the
> > past)
> >
> > Thanks for taking care of the twolc errors I reported in #826659.  The
> > twolc test now succeeds on little-endian systems, and no longer hangs
> > anywhere, but still fails on big-endian architectures (mips, powerpc,
> > s390x, and several non-release architectures).  I don't have further
> > details, but perhaps you can reproduce the problem on a porterbox.
> > Could you please take a look?
> 
> 
> Can reproduce. Looking into it upstream:
> https://github.com/hfst/hfst/issues/328
> 
> While it did successfully build in the past, that was only because the test
> suite was disabled until recently. The tests revealed the unsigned char
> issue which was easy to fix, and now the endian issue which will not be as
> easy.

Hi,

Any progress on this?

Thanks,
Emilio

Bug#836757: marked as done (netatalk: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 16:36:51 +
with message-id 
and subject line Bug#836757: fixed in netatalk 2.2.5-1.1
has caused the Debian Bug report #836757,
regarding netatalk: please drop the build dependency on hardening-wrapper
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.)


-- 
836757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: netatalk
Version: 2.2.5-1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-includes package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-includes
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: netatalk
Source-Version: 2.2.5-1.1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated netatalk 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, 28 Sep 2016 11:27:14 +0100
Source: netatalk
Binary: netatalk netatalk-dbg
Architecture: source amd64
Version: 2.2.5-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Netatalk team 
Changed-By: Chris Lamb 
Description:
 netatalk   - AppleTalk user binaries
 netatalk-dbg - Debug symbols for netatalk
Closes: 836757
Changes:
 netatalk (2.2.5-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop Build-Depends on hardening-includes. (Closes: #836757)
Checksums-Sha1:
 6cb3830569ef9937b655a9575ea418702590924c 2200 netatalk_2.2.5-1.1.dsc
 069e98a63b57d25bec5521a6dcdc0d38957f9f35 1727893 netatalk_2.2.5.orig.tar.gz
 83441b0771f2576b973faf285e620f7f04f13e99 45756 netatalk_2.2.5-1.1.debian.tar.xz
 f77a2fc3fdc7ce36d8bee2127082b28f38d1b809 1492354 
netatalk-dbg_2.2.5-1.1_amd64.deb
 6c253049ba40af9c29b8067c633b31e476534ec4 754568 netatalk_2.2.5-1.1_amd64.deb
Checksums-Sha256:
 0ece864d9e4845576869f3cd07f08d22149717460b846733acec470f33350027 2200 
netatalk_2.2.5-1.1.dsc
 efd95fc95c1821a80d0db34babf1e94d70145aaa7c6a2597f10ff1f72508f9c7 1727893 
netatalk_2.2.5.orig.tar.gz
 7124baf0e1524e4581f2fb8ee2f3f4f916eb6bfc6c2e38443a277b9c66ae372b 45756 
netatalk_2.2.5-1.1.debian.tar.xz
 a6aaed429e9129ef0d4c4c8d7e1bab07a817d701149f4dffbe53337b687569f5 1492354 
netatalk-dbg_2.2.5-1.1_amd64.deb
 305ced37bac5bef5d30c74233223b903bde86ba2e183840c8a2fff75d67a1bb9 754568 
netatalk_2.2.5-1.1_amd64.deb
Files:
 8a291a16f2f22c84b3ea77ca202e8dd3 2200 net extra netatalk_2.2.5-1.1.dsc
 f93d23ceb27a77634fcd554858d0857f 1727893 net extra netatalk_2.2.5.orig.tar.gz
 99d8025ddff5eb97230f5c70d4273848 45756 net extra 
netatalk_2.2.5-1.1.debian.tar.xz
 ae1bb4828bbe7cea2d6f3f5d72df6600 1492354 debug extra 
netatalk-dbg_2.2.5-1.1_amd64.deb
 5b2497fdbb739406511923f8b0f6b1f5 754568 net extra netatalk_2.2.5-1.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX658gAAoJEB6VPifUMR5YEYEP/3FdNIfuoI1qPfUlV8QHa/9N
ossJpjQ7yl6odH52u8Ta9lRqPyEreZzncMrgsdRnnMyH1JrIrmfEpO27BQFTa5Bq
As0UVAOegASiUZIKi2hk01XZSzXvEr3xQlN6aCGj9UPfZzf8QfLH0VRWiqWGAcka
gX6nZxJa9scA6UcdBoJRCeO6OHBFEuUpwEluzAVDU2+zU1AjJX0OjXt8h8O3krOl
8tyrjAFMLlfjD0gV/4S7VjQu2TffqMSY9yL8A8nYGgVYhp/rzFcD+BbsSPwERWsp
UVIbKsKd9T/BnfyKODThN0UPhHRoGW4Jq/lZ3L6b4ML5ZfkOdyn3bTUR1Pv24qr/
GbSkO0r7LBFERSBc16DU/hMJMiwwbR5BYImaZEpeBd375xHbSLMGzUG5VFt3qkjA
ERwPZrupsXw5613ddqEsrwi+yU9ITi9rtI6DUrbe4nPtnLPYpokK9lzEwmdUh+4b
JphwZriMkA7TFoNDOcPo9h4cFvqWatvLIMRwhSmLWLgBd7v6d6Rg3XCGj1FjcUk1
oIpPtbrAv1Wq7qzVPIRd+TXhbx56Lb9m6j6TLboj/6vQd4I5+zYNdRlmGXHihRDy
jcrBfbxF/q+0R+fWJgU1wTbW7V3zj6W6iifqYkpUOdrCdRWf9S0sb+4ZSzlABw1Z
Cem0CpsVVyfrWSiKc7A3
=L3sW
-END PGP SIGNATURE End Messa

Bug#836652: marked as done (rtpproxy: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 16:38:03 +
with message-id 
and subject line Bug#836652: fixed in rtpproxy 1.2.1-2.2
has caused the Debian Bug report #836652,
regarding rtpproxy: please drop the build dependency on hardening-wrapper
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.)


-- 
836652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rtpproxy
Version: 1.2.1-2.1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-wrapper
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: rtpproxy
Source-Version: 1.2.1-2.2

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated rtpproxy 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, 26 Sep 2016 15:11:44 +
Source: rtpproxy
Binary: rtpproxy
Architecture: source
Version: 1.2.1-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Mattia Rizzolo 
Description:
 rtpproxy   - Relay for Real-time Transport Protocol (RTP) media streams
Closes: 741660 765250 836652
Changes:
 rtpproxy (1.2.1-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bump debhelper compat level to 10:
 + This means automatic dh-autoreconf.  Closes: #765250
 + This also means automatic config.{sub,guess} update.  Closes: #741660
 + Also drop build-dependencies on dh-autoreconf and all autotools, they are
   implied by debhelper >= 10
   * Stop using hardening-wrapper and instead make use of dpkg-buildflags with
 DEB_BUILD_MAINT_OPTIONS = hardening=+all
 Closes: 836652
   * Bump Standards-Version to 3.9.8, no changes needed.
Checksums-Sha1:
 dabb5a7d8be563c41570f3d83e2083a7d0dd929a 1937 rtpproxy_1.2.1-2.2.dsc
 10e015aac4d53d5d58a2a77c1f9bb74ebfa33501 5568 rtpproxy_1.2.1-2.2.debian.tar.xz
Checksums-Sha256:
 bbc79f077ae65d58bdee5ac07813e4a2083081af94bb7bca82cbe04928ea6092 1937 
rtpproxy_1.2.1-2.2.dsc
 cdb8a707016f71cdc49ebf87f4dbeaa1c7c61b60a2b0a149eb3c4f3897d8c51e 5568 
rtpproxy_1.2.1-2.2.debian.tar.xz
Files:
 de2626b7e4fbfb18af71f669074b30ee 1937 net optional rtpproxy_1.2.1-2.2.dsc
 3988a424365cc1c420642db02534621d 5568 net optional 
rtpproxy_1.2.1-2.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX6Tq3AAoJEEsEP825REVA/woP+wb9aUO9u49x8JClC2wa1is4
zxxpYtJh5PH50oO0RhPP369otByuwYrTAtp0BguFJ0+c0RmMwtLVunTCwpy+Vgen
luiVQ+hGStoU1nZ31bYDZHFB4UiXGDhd2Da4eGlMKX2DA1IbHXHHxMJynQK3LC+P
uNSdmRXkz57NUGVd1iViUyaf39TyrzdxIfMFxJ7XHYyG2ReDdzK6ou44PP5blyyc
AvXci4pn+dKTkmK96hjBXv4mMt/TodFrvtzFGfTWMXMY4RyTUKNNELJSio5PVKI3
UFep467cs6fe2U47ZKEWIOwmr/px4GWX1TkoV5EhaPKigBkPEBh3Op4HuBE2fIvd
Eubp6m7HKBYBUcSQJZ/uvINTA1irR9ezUP0iGL6Im3ESIZFua1E7/iPHuLj9edIL
Z4fbPzjvwJC+Hlu4cRaw4zZu2PK5SnnJ0aglaWEwvo6PQnZMarq2Y+ZlRWnoKMsi
IdyKbHe+8JHYNDExOFHEEX1R0+qnLiUXLrdRRBOXM4QkWikiebLw4uBF1EArC4ej
GQ/fbWPaXHOPBYyPt8fooFW4MPLpKT3J2N7OpaBPNZjGC6k10mGx4Kf0OqwBNj/6
EfCKxaPPil4HODYz6S4+WXOdvGKjPH1Wilaz9zAOeN+hVzitCPfBZl+vY7FICHEZ
7VAFmmRadZFHgB4iuIj+
=ZSSU
-END PGP SIGNATURE End Message ---

Bug#836664: marked as done (wsjtx: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 16:38:09 +
with message-id 
and subject line Bug#836664: fixed in wsjtx 1.1.r3496-3.1
has caused the Debian Bug report #836664,
regarding wsjtx: please drop the build dependency on hardening-wrapper
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.)


-- 
836664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wsjtx
Version: 1.1.r3496-3
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-wrapper
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: wsjtx
Source-Version: 1.1.r3496-3.1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated wsjtx 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, 26 Sep 2016 15:33:49 +
Source: wsjtx
Binary: wsjtx
Architecture: source
Version: 1.1.r3496-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hams group 
Changed-By: Mattia Rizzolo 
Description:
 wsjtx  - weak-signal amateur radio communications
Closes: 836664
Changes:
 wsjtx (1.1.r3496-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch so that the build system can make use of exported buildflags
   * Bump compat level to 9, so that dh exports dpkg-buildflags in the env by
 itself.
   * Use DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie instead of using
 hardening-wrapper.  Closes: #836664
   * Remove a bunch of useless comments from d/rules.
Checksums-Sha1:
 cec80121379c80afbef7660f76f9b7ce2f361a19 1965 wsjtx_1.1.r3496-3.1.dsc
 814bd12eabbeb59627a45e24eb07272253e9c1ed 850872 
wsjtx_1.1.r3496-3.1.debian.tar.xz
Checksums-Sha256:
 e9b59440963a3bf1bd34bac2170c8f6f7dd83844cfdb25b0d75f3ec5bd1d1b46 1965 
wsjtx_1.1.r3496-3.1.dsc
 ed1b3e94f6c3bed0bf8bb6cf136d256a55bd86e9b110de38d711374a932a1849 850872 
wsjtx_1.1.r3496-3.1.debian.tar.xz
Files:
 8fc27fcdba892a4662ff5927bade37ce 1965 hamradio optional wsjtx_1.1.r3496-3.1.dsc
 f601f95dd9a68544c8aff0751d649317 850872 hamradio optional 
wsjtx_1.1.r3496-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX6T/oAAoJEEsEP825REVA9YoP/37nlpMstLMXjkJPcW+N2XQ3
MhICKvwiyWnGntYm39pv6HJIjAURpTBEqrzfsgY7714P1kCiLnkcE6WGVNQc/yvs
sjDDp00UIv5/6LGw3XCIlJel55gZeuhYgk1L3SAtacUi14KUnox7YuCbDT3xKiv8
XCnotg+rWf/mO7MkxN5/65PG2cept/VjeQrUyna5PdIshYOqesdiWSMKNqB3heKZ
GoOWd+y+O9LYVpxJ/8agLOscDzCDfi814xN5Xdf65PUB8x7Lz9dI04e/T1wA2jfv
VUmy+gLgNHVph2GMl9M7T46YMIdbVCTB1I8m8PiAJv3PkGpwJj0Dw2IpIm7vB2Iv
J0/r51g7pe8ely8sgui4V8nNJYzcJ4ecAbJA0TM2G0L/fnSBY44ln0+WbWWXgoYh
+n1bdSKPH8Dc4+PNwwF3Qws9M0WH2BNdhylaiQRVbNVwQi35oHFrK11nIJFsKeEP
gnAVgpwgMDr0BhzqdLz76CekBtON5KYVHV2PoTyTcea7DkNeDR6jADNnWMWSn0KQ
9cxYOwC4PMX0RYGUzZnL688dW8qerTPhhrGCDlClO9oP0b81Rim5GQyneV2sGtk5
9QdrXE/PEwRkPB2Zh0TceEBLvK6oU+nD7ZJ6bz6dz5dIU7MbNwGNRbs6yommofDF
ntr8sdlJGVOPxAC3Zg99
=dRd1
-END PGP SIGNATURE End Message ---

Bug#831269: marked as done (kover: FTBFS: /bin/sh: 1: cd: can't cd to builddir)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 16:35:04 +
with message-id 
and subject line Bug#831269: fixed in kover 1:4-10
has caused the Debian Bug report #831269,
regarding kover: FTBFS: /bin/sh: 1: cd: can't cd to builddir
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build-arch
> test -d debian/patched || install -d debian/patched
> dpatch  apply-all  
> applying patch 10-missing_headers to ./ ... ok.
> dpatch  cat-all  >>patch-stampT
> mv -f patch-stampT patch-stamp
> dh_testdir
> cd builddir && /usr/bin/make
> /bin/sh: 1: cd: can't cd to builddir
> make: *** [build-arch-stamp] Error 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/07/14/kover_4-9_unstable_gcc5.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: kover
Source-Version: 1:4-10

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated kover 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, 01 Oct 2016 15:45:29 +0200
Source: kover
Binary: kover
Architecture: source
Version: 1:4-10
Distribution: unstable
Urgency: medium
Maintainer: Pino Toscano 
Changed-By: Pino Toscano 
Description:
 kover  - WYSIWYG CD cover printer
Closes: 622303 668640 831269
Changes:
 kover (1:4-10) unstable; urgency=medium
 .
   * Switch myself as Maintainer, as agreed with Rene Engelhard -- thanks Rene
 for all the 14 years of work on it!
   * Stop converting the application PNG icon to xpm, as it was used only by
 the (removed already) Debian menu entry.
 - drop the imagemagick build dependency, no more useful now
   * Use a kover.docs file to install the documentation files, instead of
 passing the file names to dh_installdocs.
   * Do not pass ChangeLog explicitly to dh_installchangelogs, as in
 compat >= 7 (which we use) is detected automatically.
   * Switch format to "3.0 (quilt)".
   * Convert the patches from dpatch to integrated quilt: (Closes: #668640)
 - 02_make-kover.desktop-valid.dpatch: replace with the upstream commit
   5670584e275d2eb119744717291979a11becafa4; patch
   upstream_make-kover.desktop-valid.patch
 - 10-missing_headers.dpatch: replace with the upstream commit
   234296fa6816848c35ad3838efb711bb2e005bd9; patch
   upstream_fix-compilation-errors-with-gcc-4.4.patch
 - make sure upstream_make-kover.desktop-valid.patch is applied
   (Closes: #622303)
 - remove all the patch/unpatch stuff in rules
 - drop the dpatch build dependency, no more useful now
   * Rewrite rules to use the dh sequencer:
 - cmake is correctly configured by debhelper (Closes: #831269)
 - there is no extra RPATH in binaries, so drop the chrpath build dependency
 - enable parallel build
   * Add the Homepage field.
   * Add the Vcs-Browser & Vcs-Git fields.
   * Add a watch file.
   * Link in as-needed mode.
   * Bump Standards-Version to 3.9.8, no changes required.
   * Backport upstream commit e023986e8561ceb71cfef055de8f6b652230133f to build
 and install all the available translations; patch
 upstream_applied-patch-from-Adi-Roiban-adi-roiban.ro.patch. (LP: #478507)
Checksums-Sha1:
 4bea203ee2eee4e904f5eac2cddc75980ca67dc4 1817 kove

Bug#839477: marked as done (libposix-strftime-compiler-perl: FTBFS: dh_auto_test: perl Build test --verbose 1 returned exit code 5)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 16:35:25 +
with message-id 
and subject line Bug#839477: fixed in libposix-strftime-compiler-perl 0.42-1
has caused the Debian Bug report #839477,
regarding libposix-strftime-compiler-perl: FTBFS: dh_auto_test: perl Build test 
--verbose 1 returned exit code 5
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.)


-- 
839477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libposix-strftime-compiler-perl
Version: 0.41-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_auto_configure
>   perl -I. Build.PL --installdirs vendor
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'POSIX-strftime-Compiler' version '0.41'
> cp META.json MYMETA.json
> cp META.yml MYMETA.yml
>dh_auto_build
>   perl Build
> Building POSIX-strftime-Compiler
>dh_auto_test
>   perl Build test --verbose 1
> t/00_compile.t ... 
> ok 1 - use POSIX::strftime::Compiler;
> 1..1
> ok
> t/01_basic.t . 
> ok 1 - %%
> ok 2 - %%
> ok 3 - %%
> ok 4 - %A
> ok 5 - %A
> ok 6 - %A
> ok 7 - %B
> ok 8 - %B
> ok 9 - %B
> ok 10 - %C
> ok 11 - %C
> ok 12 - %C
> ok 13 - %D
> ok 14 - %D
> ok 15 - %D
> ok 16 - %EC
> ok 17 - %EC
> ok 18 - %EC
> ok 19 - %EX
> ok 20 - %EX
> ok 21 - %EX
> ok 22 - %EY
> ok 23 - %EY
> ok 24 - %EY
> ok 25 - %Ex
> ok 26 - %Ex
> ok 27 - %Ex
> ok 28 - %Ey
> ok 29 - %Ey
> ok 30 - %Ey
> ok 31 - %F
> ok 32 - %F
> ok 33 - %F
> ok 34 - %G
> ok 35 - %G
> ok 36 - %G
> ok 37 - %H
> ok 38 - %H
> ok 39 - %H
> ok 40 - %I
> ok 41 - %I
> ok 42 - %I
> ok 43 - %M
> ok 44 - %M
> ok 45 - %M
> ok 46 - %N
> ok 47 - %N
> ok 48 - %N
> ok 49 - %OH
> ok 50 - %OH
> ok 51 - %OH
> ok 52 - %OI
> ok 53 - %OI
> ok 54 - %OI
> ok 55 - %OM
> ok 56 - %OM
> ok 57 - %OM
> ok 58 - %OS
> ok 59 - %OS
> ok 60 - %OS
> ok 61 - %OU
> ok 62 - %OU
> ok 63 - %OU
> ok 64 - %OV
> ok 65 - %OV
> ok 66 - %OV
> ok 67 - %Od
> ok 68 - %Od
> ok 69 - %Od
> ok 70 - %Oe
> ok 71 - %Oe
> ok 72 - %Oe
> ok 73 - %Om
> ok 74 - %Om
> ok 75 - %Om
> ok 76 - %Ou
> ok 77 - %Ou
> ok 78 - %Ou
> ok 79 - %Ow
> ok 80 - %Ow
> ok 81 - %Ow
> ok 82 - %Oy
> ok 83 - %Oy
> ok 84 - %Oy
> ok 85 - %P
> ok 86 - %P
> ok 87 - %P
> ok 88 - %Q
> ok 89 - %Q
> ok 90 - %Q
> ok 91 - %R
> ok 92 - %R
> ok 93 - %R
> ok 94 - %S
> ok 95 - %S
> ok 96 - %S
> ok 97 - %T
> ok 98 - %T
> ok 99 - %T
> ok 100 - %U
> ok 101 - %U
> ok 102 - %U
> ok 103 - %V
> ok 104 - %V
> ok 105 - %V
> ok 106 - %W
> ok 107 - %W
> ok 108 - %W
> ok 109 - %X
> ok 110 - %X
> ok 111 - %X
> ok 112 - %Y
> ok 113 - %Y
> ok 114 - %Y
> ok 115 - %Z
> ok 116 - %a
> ok 117 - %a
> ok 118 - %a
> ok 119 - %b
> ok 120 - %b
> ok 121 - %b
> ok 122 - %c
> ok 123 - %c
> ok 124 - %c
> ok 125 - %d
> ok 126 - %d
> ok 127 - %d
> ok 128 - %e
> ok 129 - %e
> ok 130 - %e
> ok 131 - %g
> ok 132 - %g
> ok 133 - %g
> ok 134 - %h
> ok 135 - %h
> ok 136 - %h
> ok 137 - %j
> ok 138 - %j
> ok 139 - %j
> ok 140 - %k
> ok 141 - %k
> ok 142 - %k
> ok 143 - %l
> ok 144 - %l
> ok 145 - %l
> ok 146 - %m
> ok 147 - %m
> ok 148 - %m
> ok 149 - %n
> ok 150 - %n
> ok 151 - %n
> ok 152 - %p
> ok 153 - %p
> ok 154 - %p
> ok 155 - %q
> ok 156 - %q
> ok 157 - %q
> ok 158 - %r
> ok 159 - %r
> ok 160 - %r
> ok 161 - %s
> ok 162 - %s
> ok 163 - %s
> ok 164 - %t
> ok 165 - %t
> ok 166 - %t
> ok 167 - %u
> ok 168 - %u
> ok 169 - %u
> ok 170 - %w
> ok 171 - %w
> ok 172 - %w
> ok 173 - %x
> ok 174 - %x
> ok 175 - %x
> ok 176 - %y
> ok 177 - %y
> ok 178 - %y
> ok 179 - %z
> ok 180 - %z
> ok 181 - %z
> ok 182 - %%=6
> ok 183 - %%foo=6
> ok 184 - %% foo=6
> ok 185 - %A=6
> ok 186 - %Afoo=6
> ok 187 - %A foo=6
> ok 188 - %B=6
>

Bug#839513: marked as done (libapache-logformat-compiler-perl: FTBFS: dh_auto_test: perl Build test --verbose 1 returned exit code 8)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 16:35:10 +
with message-id 
and subject line Bug#839513: fixed in libapache-logformat-compiler-perl 0.33-2
has caused the Debian Bug report #839513,
regarding libapache-logformat-compiler-perl: FTBFS: dh_auto_test: perl Build 
test --verbose 1 returned exit code 8
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.)


-- 
839513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libapache-logformat-compiler-perl
Version: 0.33-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_auto_configure
>   perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
> "ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'Apache-LogFormat-Compiler' version '0.33'
> cp META.json MYMETA.json
> cp META.yml MYMETA.yml
>dh_auto_build
>   perl Build
> Building Apache-LogFormat-Compiler
>dh_auto_test
>   perl Build test --verbose 1
> t/00_compile.t .. 
> ok 1 - use Apache::LogFormat::Compiler;
> 1..1
> ok
> t/01_basic.t  
> ok 1
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok 7
> ok 8
> 1..8
> ok
> t/02_custom.t ... 
> ok 1
> ok 2
> ok 3
> ok 4
> 1..4
> ok
> t/03_extra.t  
> ok 1
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok 7
> 1..7
> ok
> 
> #   Failed test 'Australia/Darwin 2013/1/10'
> #   at t/04_tz.t line 54.
> #  got: '[10/Jan/2013:12:45:00 +]
> # '
> # expected: '[10/Jan/2013:12:45:00 +0930]
> # '
> 
> #   Failed test 'Australia/Darwin 2013/5/10'
> #   at t/04_tz.t line 54.
> #  got: '[10/May/2013:12:45:00 +]
> # '
> # expected: '[10/May/2013:12:45:00 +0930]
> # '
> 
> #   Failed test 'Australia/Darwin 2013/8/15'
> #   at t/04_tz.t line 54.
> #  got: '[15/Aug/2013:12:45:00 +]
> # '
> # expected: '[15/Aug/2013:12:45:00 +0930]
> # '
> 
> #   Failed test 'Australia/Darwin 2013/11/15'
> #   at t/04_tz.t line 54.
> #  got: '[15/Nov/2013:12:45:00 +]
> # '
> # expected: '[15/Nov/2013:12:45:00 +0930]
> # '
> # Looks like you failed 4 tests of 4.
> 
> #   Failed test 'Australia/Darwin'
> #   at t/04_tz.t line 57.
> 
> #   Failed test 'custom format: Australia/Darwin 2013/1/10'
> #   at t/04_tz.t line 74.
> #  got: '[+]
> # '
> # expected: '[+0930]
> # '
> 
> #   Failed test 'custom format: Australia/Darwin 2013/5/10'
> #   at t/04_tz.t line 74.
> #  got: '[+]
> # '
> # expected: '[+0930]
> # '
> 
> #   Failed test 'custom format: Australia/Darwin 2013/8/15'
> #   at t/04_tz.t line 74.
> #  got: '[+]
> # '
> # expected: '[+0930]
> # '
> 
> #   Failed test 'custom format: Australia/Darwin 2013/11/15'
> #   at t/04_tz.t line 74.
> #  got: '[+]
> # '
> # expected: '[+0930]
> # '
> # Looks like you failed 4 tests of 4.
> 
> #   Failed test 'Australia/Darwin custom format'
> #   at t/04_tz.t line 77.
> 
> #   Failed test 'Asia/Tokyo 2013/1/10'
> #   at t/04_tz.t line 54.
> #  got: '[10/Jan/2013:12:45:00 +]
> # '
> # expected: '[10/Jan/2013:12:45:00 +0

Bug#839442: marked as done (libtime-parsedate-perl: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 16:35:31 +
with message-id 
and subject line Bug#839442: fixed in libtime-parsedate-perl 2015.103-2
has caused the Debian Bug report #839442,
regarding libtime-parsedate-perl: 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.)


-- 
839442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtime-parsedate-perl
Version: 2015.103-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> 
> Test Summary Report
> ---
> t/datetime.t (Wstat: 0 Tests: 325 Failed: 23)
>   Failed tests:  86-89, 160-162, 166-168, 176-179, 186-187
> 192, 197, 213-214, 221, 238-239
> t/order1.t  (Wstat: 512 Tests: 5 Failed: 2)
>   Failed tests:  3-4
>   Non-zero exit status: 2
> t/order2.t  (Wstat: 512 Tests: 5 Failed: 2)
>   Failed tests:  3-4
>   Non-zero exit status: 2
> Files=4, Tests=335,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.10 cusr  0.02 
> csys =  0.14 CPU)
> Result: FAIL
> Failed 3/4 test programs. 27/335 subtests failed.
> Makefile:846: recipe for target 'test_dynamic' 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/01/libtime-parsedate-perl_2015.103-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: libtime-parsedate-perl
Source-Version: 2015.103-2

We believe that the bug you reported is fixed in the latest version of
libtime-parsedate-perl, 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.
gregor herrmann  (supplier of updated libtime-parsedate-perl 
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, 01 Oct 2016 16:59:19 +0200
Source: libtime-parsedate-perl
Binary: libtime-parsedate-perl libtime-modules-perl
Architecture: source
Version: 2015.103-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 839442
Description: 
 libtime-modules-perl - Transitional package for libtime-modules-perl
 libtime-parsedate-perl - collection of Perl modules for time/date manipulation
Changes:
 libtime-parsedate-perl (2015.103-2) unstable; urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * debian/upstream/metadata: change GitHub/CPAN URL(s) to HTTPS.
   * Remove Jay Bonci from Uploaders. Thanks for your work!
   * Add build dependency on tzdata.
 Thanks to Lucas Nussbaum for the bug report. (Closes: #839442)
   * Update years of packaging copyright.
   * Declare compliance with Debian Policy 3.9.8.
Checksums-Sha1: 
 ea3cc2223ede500d5fc515a7bbad759faa1186ff 2386 
libtime-parsedate-perl_2015.103-2.dsc
 bd9a6df04cc9915428d801ab4921965399bf377f 3912 
libtime-parsedate-perl_2015.103-2.debian.tar.xz
Checksums-Sha256: 
 8475e69552bc950b39607581c73

Bug#839516: marked as done (libclass-date-perl: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 16:35:14 +
with message-id 
and subject line Bug#839516: fixed in libclass-date-perl 1.1.15-2
has caused the Debian Bug report #839516,
regarding libclass-date-perl: 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.)


-- 
839516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libclass-date-perl
Version: 1.1.15-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 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):
> ok 8 - tzdst
> not ok 9 - epoch
> ok 10 - epoch
> ok 11 - gmdate
> Dubious, test returned 4 (wstat 1024, 0x400)
> Failed 4/11 subtests 
> 
> Test Summary Report
> ---
> t/50_timezone.t (Wstat: 1024 Tests: 11 Failed: 4)
>   Failed tests:  4-6, 9
>   Non-zero exit status: 4
> Files=7, Tests=193,  1 wallclock secs ( 0.05 usr  0.00 sys +  0.20 cusr  0.02 
> csys =  0.27 CPU)
> Result: FAIL
> Failed 1/7 test programs. 4/193 subtests failed.
> Makefile:1023: recipe for target 'test_dynamic' 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/01/libclass-date-perl_1.1.15-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: libclass-date-perl
Source-Version: 1.1.15-2

We believe that the bug you reported is fixed in the latest version of
libclass-date-perl, 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.
gregor herrmann  (supplier of updated libclass-date-perl 
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, 01 Oct 2016 17:50:12 +0200
Source: libclass-date-perl
Binary: libclass-date-perl
Architecture: source
Version: 1.1.15-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 839516
Description: 
 libclass-date-perl - Perl module for easy date and time manipulation
Changes:
 libclass-date-perl (1.1.15-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
 .
   [ Martín Ferrari ]
   * Remove myself from Uploaders.
 .
   [ gregor herrmann ]
   * Remove Jay Bonci from Uploaders. Thanks for your work!
   * Add build dependency on tzdata.
 Thanks to Lucas Nussbaum for the bug report. (Closes: #839516)
   * Set bindnow linker flag in debian/rules.
   * Declare compliance with Debian Policy 3.9.8.
   * Add a patch to fix some spelling mistakes.
Checksums-Sha1: 
 3f3a2011da103aff3612b305c5c51c1312720642 2317 libclass-date-perl_1.1.15-2.dsc
 9588111834de7e74a45c6b26a3248f9bf0f46fe3 3620 
libclass-date-perl_1.1.15-2.debian.tar.xz
Checksums-Sha256: 
 2d7807c37361769df6d8e4b07b75f46b4925660f73aac37dfc1a0e5136bd30af 2317 
libclass-date-perl_1.1.15-2.dsc
 ff898da22fae994f68ca84c9e982ebd311749

Bug#839323: marked as done (lordsawar: FTBFS: use-item-on-player-dialog.cpp:70:13: error: no match for 'operator==' (operand types are 'Glib::RefPtr' and 'bool'))

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 16:35:45 +
with message-id 
and subject line Bug#839323: fixed in lordsawar 0.3.0-4
has caused the Debian Bug report #839323,
regarding lordsawar: FTBFS: use-item-on-player-dialog.cpp:70:13: error: no 
match for 'operator==' (operand types are 'Glib::RefPtr' 
and 'bool')
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.)


-- 
839323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lordsawar
Version: 0.3.0-3
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):
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../..  -pthread -I/usr/include/gtkmm-3.0 
> -I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include -I/usr/include/atkmm-1.6 
> -I/usr/include/gtk-3.0/unix-print -I/usr/include/gdkmm-3.0 
> -I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 
> -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 
> -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 
> -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -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/cairomm-1.0 
> -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
> -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/usr/include/libxml++-2.6 
> -I/usr/lib/x86_64-linux-gnu/libxml++-2.6/include -I/usr/include/libxml2 
> -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include  
> -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wshadow -Wextra -pedantic 
> -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -c -o use-item-on-player-dialog.lo 
> use-item-on-player-dialog.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -pthread 
> -I/usr/include/gtkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include 
> -I/usr/include/atkmm-1.6 -I/usr/include/gtk-3.0/unix-print 
> -I/usr/include/gdkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include 
> -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include 
> -I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include 
> -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
> -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/cairomm-1.0 
> -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
> -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/usr/include/libxml++-2.6 
> -I/usr/lib/x86_64-linux-gnu/libxml++-2.6/include -I/usr/include/libxml2 
> -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
> -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wshadow -Wextra -pedantic 
> -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -c use-item-on-player-dialog.cpp  -fPIC 
> -DPIC -o .libs/use-item-on-player-dialog.o
> use-item-on-player-dialog.cpp: In member function 'Player* 
> UseItemOnPlayerDialog::grabSelectedPlayer()':
> use-item-on-player-dialog.cpp:

Bug#839393: marked as done (exabgp: FTBFS sometimes (failing tests))

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2016 16:24:24 +
with message-id 
and subject line Bug#839393: fixed in exabgp 3.4.17-1
has caused the Debian Bug report #839393,
regarding exabgp: FTBFS sometimes (failing tests)
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.)


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

Dear maintainer:

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


[...]

debian/rules:11: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


It does not always fail, but it does not always build ok, and this
failure is an example. Sorry, I don't know how to reproduce the
failure, but the build log (which is attached) gives a very good hint
about why this can happen, as it contains a line like this:

failed, a test is taking more than the allocated time

An autobuilder does not necessarily have a constant and predictable
CPU speed. The same machine could be doing other things in parallel.
Therefore, any test which tries to check that things are ok by
measuring execution times should better be disabled.

Thanks.

exabgp_3.4.16-1_amd64-20160930T115703Z.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: exabgp
Source-Version: 3.4.17-1

We believe that the bug you reported is fixed in the latest version of
exabgp, 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.
Vincent Bernat  (supplier of updated exabgp 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, 01 Oct 2016 15:57:59 +0200
Source: exabgp
Binary: exabgp
Architecture: source all
Version: 3.4.17-1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Bernat 
Changed-By: Vincent Bernat 
Description:
 exabgp - BGP swiss army knife of networking
Closes: 839393
Changes:
 exabgp (3.4.17-1) unstable; urgency=medium
 .
   * New upstream version.
   * d/control: bump Standards-Version.
   * d/patches: don't disable unittests.
   * d/rules: disable conversation tests. Closes: #839393.
Checksums-Sha1:
 6d4924d6613472601bd7cdf0a9801fc8193e72f7 1908 exabgp_3.4.17-1.dsc
 377795fa7a02d5bc893fed66a0bc0d4c049a6c27 540416 exabgp_3.4.17.orig.tar.gz
 20e48d9488c1ccf53c4653023b440ffbc6a668bf 8616 exabgp_3.4.17-1.debian.tar.xz
 91a9d5813b27ce715db4deba9f08d3ca4bbc182a 237810 exabgp_3.4.17-1_all.deb
Checksums-Sha256:
 e7537751932dc1cecf437538226eaac730068b785aaca5845fa4f4b8bb344f46 1908 
exabgp_3.4.17-1.dsc
 5c40f28e1c49c9b3d5d2206c2b3b30c85f0c4a43bf2a140ac4431472ba0b9157 540416 
exabgp_3.4.17.orig.tar.gz
 cef5e3f6beb18437da6ff96b0f63821e31f6478819ffb5cb31c0925fc16dfd77 8616 
exabgp_3.4.17-1.debian.tar.xz
 04e997cc5da74d94dfdcaeffafaad776243e71ec34aa4f4523a99012edef8d1e 237810 
exabgp_3.4.17-1_all.deb
Files:
 55581e0ac965441b4047733adf456d34 1908 net optional exabgp_3.4.17-1.dsc
 4a0941ff96a5ebcadc161b9eed465951 540416 net optional exabgp_3.4.17.orig.tar.gz
 7539b16d344fba3d3485d25fcf73b4a4 8616 net optional 
exabgp_3.4.17-1.debian.tar.xz
 3fdcbb935e07ffc111c99bd20668294d 237810 net optional exabgp_3.4.17-1_all.deb

-BEGIN PGP SIGNATURE-

iQIvBAEBCAAZBQJX78ayEhxiZXJuYXRAZGViaWFuLm9yZwAKCRCVpC/oNTUl+Y13
D/wO5JWm5j1xjQbwq8qVMwt1y6ZvpxnNyfYMGT0RWSwK0KvadLwuTZeqq1dC2ID5
itYrzXSEwmzcFiXsncFrSiKjR/zkOOBrchy6s8YY+dYhggL6X/VW/bd6KO2VPlmr
S10tIsM+AqNz2xqmCNBR3Ej3ixaxMGxVvuK8xP+PAITETaGQYUFBI54JZCeakM3j
K8B0URF/uTMUI8tALZh0UZdIv39HBnIndR8UbSXZvLx0fQMrTpSHRm0zpy1Pd5HQ
ykLHnrtnyYukxajXwWpVGvI8ZuNnmKKaH8hPXAe5QqBZqXDgUNelWMPtFVnWQg7O
14iyQwTvvK/4m+ndwZCtus

Processed: merge bugs

[Debian Bug Tracking System]

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

> merge 839300 838278
Bug #839300 [src:gnustep-make] gnustep-make: FTBFS: dh_install: missing files, 
aborting
Bug #838278 [src:gnustep-make] gnustep-make: FTBFS in testing 
(@setcontentsaftertitlepage no longer works)
Added tag(s) sid and stretch.
Merged 838278 839300
> thanks
Stopping processing here.

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

Processed: tag 838278

[Debian Bug Tracking System]

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

> tags 839300 + confirmed
Bug #839300 [src:gnustep-make] gnustep-make: FTBFS: dh_install: missing files, 
aborting
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: tag 839300

[Debian Bug Tracking System]

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

> tags 839300 + confirmed
Bug #839300 [src:gnustep-make] gnustep-make: FTBFS: dh_install: missing files, 
aborting
Ignoring request to alter tags of bug #839300 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tag 838278

[Debian Bug Tracking System]

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

> tags 838278 + confirmed
Bug #838278 [src:gnustep-make] gnustep-make: FTBFS in testing 
(@setcontentsaftertitlepage no longer works)
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: Re: [pkg-fgfs-crew] Bug#839357: fgrun: FTBFS: wizard_funcs.cxx:1202:51: error: no matching function for call to 'readProperties(const char*, SGPropertyNode*)'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #839357 [src:fgrun] fgrun: FTBFS: wizard_funcs.cxx:1202:51: error: no 
matching function for call to 'readProperties(const char*, SGPropertyNode*)'
Added tag(s) fixed-upstream.

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

Bug#839357: [pkg-fgfs-crew] Bug#839357: fgrun: FTBFS: wizard_funcs.cxx:1202:51: error: no matching function for call to 'readProperties(const char*, SGPropertyNode*)'

[Rebecca N. Palmer]

Control: tags -1 fixed-upstream

https://sourceforge.net/p/flightgear/fgrun/ci/312a8de41336cfe6d85336e8909b517e0c590c0c/

(We might need the next commit as well; given how little has changed, 
probably easiest to take the whole upstream release)

Bug#839516: Pending fixes for bugs in the libclass-date-perl package

[pkg-perl-maintainers]

tag 839516 + pending
thanks

Some bugs in the libclass-date-perl package are closed in revision
2acc79bb43a639c3cf3c70ba2fb3b5638a84da21 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libclass-date-perl.git/commit/?id=2acc79b

Commit message:

Add build dependency on tzdata.

Thanks: Lucas Nussbaum for the bug report.
Closes: #839516

Processed: Pending fixes for bugs in the libclass-date-perl package

[Debian Bug Tracking System]

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

> tag 839516 + pending
Bug #839516 [src:libclass-date-perl] libclass-date-perl: FTBFS: Tests failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: reassign

[Debian Bug Tracking System]

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

> reassign 839347 xml-core
Bug #839347 {Done: Lucas Nussbaum } [src:dia] dia: FTBFS: 
dh_installxmlcatalogs: Unexpected debhelper version format
Bug reassigned from package 'src:dia' to 'xml-core'.
No longer marked as found in versions dia/0.97.3+git20160904-2.
Ignoring request to alter fixed versions of bug #839347 to the same values 
previously set
> forcemerge 837618 839347
Bug #837618 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Bug #837620 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Bug #837745 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Bug #839526 {Done: Santiago Vila } [xml-core] dia FTBFS: 
dh_installxmlcatalogs: Unexpected debhelper version format
Bug #839347 {Done: Lucas Nussbaum } [xml-core] dia: FTBFS: 
dh_installxmlcatalogs: Unexpected debhelper version format
Added indication that 839347 affects 
src:docbook5-xml,src:docbook-xml,src:python-docutils,src:dia,src:gnustep-base,src:w3c-sgml-lib,src:sgml-data,src:docbook-mathml,src:w3-dtd-mathml,src:docbook-slides,src:docbook-xsl,src:docbook-simple
The source xml-core and version 0.14 do not appear to match any binary packages
Marked as fixed in versions xml-core/0.14.
Marked as found in versions xml-core/0.13+nmu2.
Added tag(s) patch.
Bug #837620 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Bug #837745 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Bug #839526 {Done: Santiago Vila } [xml-core] dia FTBFS: 
dh_installxmlcatalogs: Unexpected debhelper version format
Merged 837618 837620 837745 839347 839526
> thanks
Stopping processing here.

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

Bug#839513: Pending fixes for bugs in the libapache-logformat-compiler-perl package

[pkg-perl-maintainers]

tag 839513 + pending
thanks

Some bugs in the libapache-logformat-compiler-perl package are closed
in revision 75563a29cc1754ac1466ed07ff3fd2705e8326fe in branch
'master' by gregor herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libapache-logformat-compiler-perl.git/commit/?id=75563a2

Commit message:

Add build dependency on tzdata.

Thanks: Lucas Nussbaum for the bug report.
Closes: #839513

Bug#839526: dia FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format

[Santiago Vila]

Actually, the bug is indeed in the web page for dia:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=dia

but since it's fixed, it's at the bottom, not at the top, so it's easy
to miss. It happened to me in a similar case as well :-)

Thanks.

Processed: Pending fixes for bugs in the libapache-logformat-compiler-perl package

[Debian Bug Tracking System]

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

> tag 839513 + pending
Bug #839513 [src:libapache-logformat-compiler-perl] 
libapache-logformat-compiler-perl: FTBFS: dh_auto_test: perl Build test 
--verbose 1 returned exit code 8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#839369: marked as pending

[Tristan Seligmann]

tag 839369 pending
thanks

Hello,

Bug #839369 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/python-cryptography.git;a=commitdiff;h=617ff97

---
commit 617ff971a389db85a257b7f3eab60c1a65c1
Author: Tristan Seligmann 
Date:   Sat Oct 1 17:26:35 2016 +0200

Fixes failure on OpenSSL 1.0.2j (closes: #839369)

diff --git a/debian/changelog b/debian/changelog
index d13f18e..9b6b4fd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,9 @@
-python-cryptography (1.5.2-1) UNRELEASED; urgency=medium
+python-cryptography (1.5.2-1) unstable; urgency=medium
 
   * New upstream release.
+- Fixes failure on OpenSSL 1.0.2j (closes: #839369)
 
- -- Tristan Seligmann   Sat, 01 Oct 2016 17:19:12 +0200
+ -- Tristan Seligmann   Sat, 01 Oct 2016 17:26:32 +0200
 
 python-cryptography (1.5-2) unstable; urgency=medium
 

Processed: Bug#839369 marked as pending

[Debian Bug Tracking System]

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

> tag 839369 pending
Bug #839369 [src:python-cryptography] python-cryptography: FTBFS: dh_auto_test: 
pybuild --test -i python{version} -p 2.7 returned exit code 13
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: This is a bug in xml-core and it was fixed just yesterday

[Debian Bug Tracking System]

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

> reassign 839526 xml-core
Bug #839526 [src:dia] dia FTBFS: dh_installxmlcatalogs: Unexpected debhelper 
version format
Bug reassigned from package 'src:dia' to 'xml-core'.
No longer marked as found in versions dia/0.97.3+git20160904-2.
Ignoring request to alter fixed versions of bug #839526 to the same values 
previously set
> close 839526 0.14
Bug #839526 [xml-core] dia FTBFS: dh_installxmlcatalogs: Unexpected debhelper 
version format
There is no source info for the package 'xml-core' at version '0.14' with 
architecture ''
Unable to make a source version for version '0.14'
Marked as fixed in versions 0.14.
Bug #839526 [xml-core] dia FTBFS: dh_installxmlcatalogs: Unexpected debhelper 
version format
Marked Bug as done
> forcemerge 837618 839526
Bug #837618 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Bug #837620 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Bug #837745 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Bug #837745 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Removed indication that 837745 affects src:w3c-sgml-lib, src:dia, 
src:docbook5-xml, src:docbook-xsl, src:sgml-data, src:w3-dtd-mathml, 
src:gnustep-base, src:docbook-simple, src:docbook-slides, src:docbook-mathml, 
src:python-docutils, and src:docbook-xml
Added indication that 837745 affects 
src:docbook5-xml,src:docbook-xml,src:python-docutils,src:dia,src:gnustep-base,src:w3c-sgml-lib,src:sgml-data,src:docbook-mathml,src:w3-dtd-mathml,src:docbook-slides,src:docbook-xsl,src:docbook-simple
Removed indication that 837618 affects src:docbook-xsl, src:sgml-data, 
src:w3-dtd-mathml, src:gnustep-base, src:docbook-simple, src:docbook-slides, 
src:python-docutils, src:docbook-xml, src:docbook-mathml, src:w3c-sgml-lib, 
src:dia, and src:docbook5-xml
Added indication that 837618 affects 
src:docbook5-xml,src:docbook-xml,src:python-docutils,src:dia,src:gnustep-base,src:w3c-sgml-lib,src:sgml-data,src:docbook-mathml,src:w3-dtd-mathml,src:docbook-slides,src:docbook-xsl,src:docbook-simple
Removed indication that 837620 affects src:gnustep-base, src:docbook-xml, 
src:docbook-mathml, src:python-docutils, src:docbook-slides, 
src:docbook-simple, src:sgml-data, src:docbook-xsl, src:w3-dtd-mathml, 
src:docbook5-xml, src:dia, and src:w3c-sgml-lib
Added indication that 837620 affects 
src:docbook5-xml,src:docbook-xml,src:python-docutils,src:dia,src:gnustep-base,src:w3c-sgml-lib,src:sgml-data,src:docbook-mathml,src:w3-dtd-mathml,src:docbook-slides,src:docbook-xsl,src:docbook-simple
Bug #839526 {Done: Santiago Vila } [xml-core] dia FTBFS: 
dh_installxmlcatalogs: Unexpected debhelper version format
Added indication that 839526 affects 
src:docbook5-xml,src:docbook-xml,src:python-docutils,src:dia,src:gnustep-base,src:w3c-sgml-lib,src:sgml-data,src:docbook-mathml,src:w3-dtd-mathml,src:docbook-slides,src:docbook-xsl,src:docbook-simple
The source xml-core and version 0.14 do not appear to match any binary packages
Marked as fixed in versions xml-core/0.14; no longer marked as fixed in 
versions 0.14.
Marked as found in versions xml-core/0.13+nmu2.
Added tag(s) sid, patch, and stretch.
Bug #837620 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Merged 837618 837620 837745 839526
> affects 839526 src:dia
Bug #839526 {Done: Santiago Vila } [xml-core] dia FTBFS: 
dh_installxmlcatalogs: Unexpected debhelper version format
Bug #837618 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Bug #837620 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Bug #837745 {Done: Mattia Rizzolo } [xml-core] xml-core: 
Makes some packages to FTBFS with 'dh_installxmlcatalogs: Unexpected debhelper 
version format'
Ignoring request to set affects of bug 839526 to the same value previously set
Ignoring request to set affects of bug 837618 to the same value previously set
Ignoring request to set affects of bug 837620 to the same value previously set
Ignoring request to set affects of bug 837745 to the same value previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
837618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837618
837620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837620
837745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837745
839526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839526
Debian Bug Tracking System
Contact

Processed: openjade: diff for NMU version 1.4devel1-21.3

[Debian Bug Tracking System]

Processing control commands:

> tags 823419 + pending
Bug #823419 [src:openjade] openjade: Broken if rebuilt using g++-6 and glibc 
2.23
Added tag(s) pending.

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

Bug#823419: openjade: diff for NMU version 1.4devel1-21.3

[Jakub Wilk]

Control: tags 823419 + pending

Dear maintainer,

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


--
Jakub Wilk
diffstat for openjade-1.4devel1 openjade-1.4devel1

 changelog |9 +
 rules |1 +
 2 files changed, 10 insertions(+)


No differences were encountered between the control files

diff -Nru openjade-1.4devel1/debian/changelog openjade-1.4devel1/debian/changelog
--- openjade-1.4devel1/debian/changelog	2016-10-01 17:30:14.0 +0200
+++ openjade-1.4devel1/debian/changelog	2016-10-01 17:30:15.0 +0200
@@ -1,3 +1,12 @@
+openjade (1.4devel1-21.3) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Pass -fno-lifetime-dse to GCC to work around invalid assumptions about
+object lifetimes (closes: #823419). Thanks to Daniel Schepler for the bug
+report.
+
+ -- Jakub Wilk   Sat, 01 Oct 2016 17:01:25 +0200
+
 openjade (1.4devel1-21.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru openjade-1.4devel1/debian/rules openjade-1.4devel1/debian/rules
--- openjade-1.4devel1/debian/rules	2016-10-01 17:30:14.0 +0200
+++ openjade-1.4devel1/debian/rules	2016-10-01 17:30:15.0 +0200
@@ -31,6 +31,7 @@
   CFLAGS += -ffunction-sections
   CXXFLAGS += -ffunction-sections
 endif
+CXXFLAGS += -fno-lifetime-dse  # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69534
 export CFLAGS
 export CXXFLAGS
 

Bug#839477: Pending fixes for bugs in the libposix-strftime-compiler-perl package

[pkg-perl-maintainers]

tag 839477 + pending
thanks

Some bugs in the libposix-strftime-compiler-perl package are closed
in revision 4e16881846671d910b901686e69508e8222064d5 in branch
'master' by gregor herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libposix-strftime-compiler-perl.git/commit/?id=4e16881

Commit message:

Add build dependency on tzdata.

Thanks: Lucas Nussbaum for the bug report.
Closes: #839477

Bug#839526: dia FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format

[Santiago Vila]

On Sat, Oct 01, 2016 at 05:44:33PM +0300, Adrian Bunk wrote:
> Source: dia
> Version: 0.97.3+git20160904-2
> Severity: serious
> 
> dia FTBFS on all architecture:
>   https://buildd.debian.org/status/package.php?p=dia
> 
> The error message is:
> 
> ...
> # Workaround as long as dh_installxmlcatalogs is not integrated in dh 
> (#575770)
> dh_installxmlcatalogs
> dh_installxmlcatalogs: Unexpected debhelper version format

Hello. This was a bug in xml-core, the package containing
dh_installxmlcatalogs, which get confused about debhelper version "10"
not containing any dot.

It was fixed just yesterday, so autobuilders should really try again.

I'm going to do the usual tidy up (reassign + affects).

Thanks.

Processed: Pending fixes for bugs in the libposix-strftime-compiler-perl package

[Debian Bug Tracking System]

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

> tag 839477 + pending
Bug #839477 [src:libposix-strftime-compiler-perl] 
libposix-strftime-compiler-perl: FTBFS: dh_auto_test: perl Build test --verbose 
1 returned exit code 5
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#823419: openjade: Broken if rebuilt using g++-6 and glibc 2.23

[Jakub Wilk]

* Jakub Wilk , 2016-10-01, 16:52:

See https://bugzilla.redhat.com/show_bug.cgi?id=1306162 for the analysis.


Oops, I actually meant: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69534

--
Jakub Wilk

Processed: Pending fixes for bugs in the libtime-parsedate-perl package

[Debian Bug Tracking System]

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

> tag 839442 + pending
Bug #839442 [src:libtime-parsedate-perl] libtime-parsedate-perl: FTBFS: Tests 
failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#839442: Pending fixes for bugs in the libtime-parsedate-perl package

[pkg-perl-maintainers]

tag 839442 + pending
thanks

Some bugs in the libtime-parsedate-perl package are closed in
revision ddaf5435c77f83ff0d225821bc6c61b08ee1ae1e in branch 'master'
by gregor herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libtime-parsedate-perl.git/commit/?id=ddaf543

Commit message:

Add build dependency on tzdata.

Thanks: Lucas Nussbaum for the bug report.
Closes: #839442

Processed: Re: Bug#823419: openjade: Broken if rebuilt using g++-6 and glibc 2.23

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #823419 [src:openjade] openjade: Broken if rebuilt using g++-6 and glibc 
2.23
Added tag(s) patch.

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

Bug#823419: openjade: Broken if rebuilt using g++-6 and glibc 2.23

[Jakub Wilk]

Control: tags -1 + patch

See https://bugzilla.redhat.com/show_bug.cgi?id=1306162 for the analysis.

The attached patch fixes it for me.

--
Jakub Wilk
diff -Nru openjade-1.4devel1/debian/rules openjade-1.4devel1/debian/rules
--- openjade-1.4devel1/debian/rules	2016-10-01 16:50:44.0 +0200
+++ openjade-1.4devel1/debian/rules	2016-10-01 16:50:45.0 +0200
@@ -31,6 +31,7 @@
   CFLAGS += -ffunction-sections
   CXXFLAGS += -ffunction-sections
 endif
+CXXFLAGS += -fno-lifetime-dse  # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69534
 export CFLAGS
 export CXXFLAGS
 

Bug#839528: ike-scan FTBFS on s390x (check-packet failure)

[Adrian Bunk]

Source: ike-scan
Version: 1.9.4-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=ike-scan&arch=s390x&ver=1.9.4-1&stamp=1468880613

FAIL: check-packet
==

Checking ike-scan default packet against ./pkt-default-proposal.dat ...
ok
Checking ike-scan custom packet (adv trans) against ./pkt-custom-proposal.dat 
...
ok
Checking ike-scan aggressive mode packet against ./pkt-aggressive.dat ...
ok
Checking ike-scan malformed packet against ./pkt-malformed.dat ...
FAILED
FAIL check-packet (exit status: 1)

Bug#839520: gtk-sharp2: FTBFS: mdoc: Could not find file "/etc/localtime"

[Lucas Nussbaum]

Source: gtk-sharp2
Version: 2.12.10-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc'
> /usr/bin/mdassembler --ecma ./en -o gtk-sharp-docs
> Error reading namespace XML for GLib at ./en/ns-GLib.xml
> mdoc: Could not find file "/etc/localtime"
> See `mdoc help' for more information.
> Makefile:569: recipe for target 'gtk-sharp-docs.zip' failed
> make[3]: *** [gtk-sharp-docs.zip] 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 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/01/gtk-sharp2_2.12.10-6_unstable.log

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

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

Bug#839526: dia FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format

[Adrian Bunk]

Source: dia
Version: 0.97.3+git20160904-2
Severity: serious

dia FTBFS on all architecture:
  https://buildd.debian.org/status/package.php?p=dia

The error message is:

...
# Workaround as long as dh_installxmlcatalogs is not integrated in dh (#575770)
dh_installxmlcatalogs
dh_installxmlcatalogs: Unexpected debhelper version format
debian/rules:38: recipe for target 'override_dh_installcatalogs' failed
make[1]: *** [override_dh_installcatalogs] Error 255

Bug#839525: ruby-active-model-serializers: FTBFS: ERROR: Test "ruby2.3" failed.

[Lucas Nussbaum]

Source: ruby-active-model-serializers
Version: 0.9.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=debian/ruby-active-model-serializers/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.3 -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
> "test/integration/action_controller/namespaced_serialization_test.rb" 
> "test/integration/action_controller/serialization_test.rb" 
> "test/integration/action_controller/serialization_test_case_test.rb" 
> "test/integration/active_record/active_record_test.rb" 
> "test/integration/generators/resource_generator_test.rb" 
> "test/integration/generators/scaffold_controller_generator_test.rb" 
> "test/integration/generators/serializer_generator_test.rb" 
> "test/unit/active_model/array_serializer/except_test.rb" 
> "test/unit/active_model/array_serializer/key_format_test.rb" 
> "test/unit/active_model/array_serializer/meta_test.rb" 
> "test/unit/active_model/array_serializer/only_test.rb" 
> "test/unit/active_model/array_serializer/options_test.rb" 
> "test/unit/active_model/array_serializer/root_test.rb" 
> "test/unit/active_model/array_serializer/scope_test.rb" 
> "test/unit/active_model/array_serializer/serialization_test.rb" 
> "test/unit/active_model/default_serializer_test.rb" 
> "test/unit/active_model/serializer/associations/build_serializer_test.rb" 
> "test/unit/active_model/serializer/associations_test.rb" 
> "test/unit/active_model/serializer/attributes_test.rb" 
> "test/unit/active_model/serializer/config_test.rb" 
> "test/unit/active_model/serializer/filter_test.rb" 
> "test/unit/active_model/serializer/has_many_polymorphic_test.rb" 
> "test/unit/active_model/serializer/has_many_test.rb" 
> "test/unit/active_model/serializer/has_one_and_has_many_test.rb" 
> "test/unit/active_model/serializer/has_one_polymorphic_test.rb" 
> "test/unit/active_model/serializer/has_one_test.rb" 
> "test/unit/active_model/serializer/key_format_test.rb" 
> "test/unit/active_model/serializer/meta_test.rb" 
> "test/unit/active_model/serializer/options_test.rb" 
> "test/unit/active_model/serializer/root_test.rb" 
> "test/unit/active_model/serializer/scope_test.rb" 
> "test/unit/active_model/serializer/url_helpers_test.rb" -v
> DEPRECATION WARNING: ** Notice: include was renamed to embed_in_root. **
> . (called from initialize at 
> /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/association.rb:10)
> DEPRECATION WARNING: ** Notice: include was renamed to embed_in_root. **
> . (called from initialize at 
> /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/association.rb:10)
> DEPRECATION WARNING: ** Notice: include was renamed to embed_in_root. **
> . (called from initialize at 
> /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/association.rb:10)
> DEPRECATION WARNING: `#timestamps` was called without specifying an option 
> for `null`. In Rails 5, this behavior will change to `null: false`. You 
> should manually specify `null: true` to prevent the behavior of your existing 
> migrations from changing. (called from block (2 levels) in  
> at /<>/test/fixtures/active_record.rb:13)
> DEPRECATION WARNING: `#timestamps` was called without specifying an option 
> for `null`. In Rails 5, this behavior will change to `null: false`. You 
> should manually specify `null: true` to prevent the behavior of your existing 
> migrations from changing. (called from block (2 levels) in  
> at /<>/test/fixtures/active_record.rb:19)
> /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:182:in `rescue in 
> create_de

Bug#839523: openbve: FTBFS: System.IO.FileNotFoundException: Could not find file "/etc/localtime"

[Lucas Nussbaum]

Source: openbve
Version: 1.4.0.10-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for builddir in openBVE/OpenBve openBVE/OpenBveApi openBVE/OpenBveAts 
> openBVE/Sound.Flac openBVE/Sound.RiffWave openBVE/Texture.Ace 
> openBVE/Texture.BmpGifJpegPngTiff; do \
>   (cd $builddir && xbuild /p:Configuration=Release *.csproj) || exit 1; \
> done
> XBuild Engine Version 12.0
> Mono, Version 4.2.1.0
> Copyright (C) 2005-2013 Various Mono authors
> 
> Unhandled Exception:
> System.IO.FileNotFoundException: Could not find file "/etc/localtime"
> File name: '/etc/localtime'
>   at System.IO.FileStream..ctor (System.String path, FileMode mode, 
> FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, 
> FileOptions options) <0x7f802895d2c0 + 0x005ed> in :0 
>   at System.IO.FileStream..ctor (System.String path, FileMode mode, 
> FileAccess access, FileShare share) <0x7f802895cf30 + 0x0004b> in  unknown>:0 
>   at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor 
> (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare)
>   at System.IO.File.OpenRead (System.String path) <0x7f802895aa50 + 0x00034> 
> in :0 
>   at System.TimeZoneInfo.FindSystemTimeZoneByFileName (System.String id, 
> System.String filepath) <0x7f80288bbfe0 + 0x00032> in :0 
>   at System.TimeZoneInfo.CreateLocal () <0x7f80288ba850 + 0x00176> in 
> :0 
>   at System.TimeZoneInfo.get_Local () <0x7f80288ba7c0 + 0x00025> in  unknown>:0 
>   at System.TimeZoneInfo.GetDateTimeNowUtcOffsetFromUtc (DateTime time, 
> System.Boolean& isAmbiguousLocalDst) <0x7f80288bbce0 + 0x00017> in  unknown>:0 
>   at System.DateTime.get_Now () <0x7f8028764260 + 0x00046> in  unknown>:0 
>   at Microsoft.Build.BuildEngine.Project..ctor 
> (Microsoft.Build.BuildEngine.Engine engine, System.String toolsVersion) 
> <0x40fbda90 + 0x00220> in :0 
>   at Microsoft.Build.BuildEngine.Project..ctor 
> (Microsoft.Build.BuildEngine.Engine engine) <0x40fbda40 + 0x0001b> in 
> :0 
>   at Microsoft.Build.BuildEngine.Engine.CreateNewProject () <0x40fbd9f0 + 
> 0x00037> in :0 
>   at Mono.XBuild.CommandLine.MainClass.Execute () <0x40fb45d0 + 0x00be3> in 
> :0 
>   at Mono.XBuild.CommandLine.MainClass.Main (System.String[] args) 
> <0x40fb1d70 + 0x0008b> in :0 
> debian/rules:20: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] 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 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/01/openbve_1.4.0.10-3_unstable.log

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

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

Bug#839522: ruby-roadie-rails: FTBFS: ERROR: Test "ruby2.3" failed: RuntimeError:

[Lucas Nussbaum]

Source: ruby-roadie-rails
Version: 1.1.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 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):
>  RuntimeError:
>No output present. Did the application crash?
>  # ./spec/support/rails_app.rb:35:in `read_providers'
>  # ./spec/integration_spec.rb:77:in `block (4 levels) in '
> 
> Finished in 5.6 seconds (files took 0.66281 seconds to load)
> 105 examples, 5 failures
> 
> Failed examples:
> 
> rspec ./spec/integration_spec.rb:48 # Integrations with Rails 4.2.x inlines 
> styles for multipart emails
> rspec ./spec/integration_spec.rb:52 # Integrations with Rails 4.2.x 
> automatically inlines styles with automatic mailer
> rspec ./spec/integration_spec.rb:56 # Integrations with Rails 4.2.x 
> automatically inlines styles with automatic mailer and forced delivery
> rspec ./spec/integration_spec.rb:60 # Integrations with Rails 4.2.x inlines 
> no styles when roadie_options are nil
> rspec ./spec/integration_spec.rb:76 # Integrations with Rails 4.2.x has a 
> AssetPipelineProvider together with a FilesystemProvider
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.3" 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/01/ruby-roadie-rails_1.1.0-1_unstable.log

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

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

Bug#839524: sdb: FTBFS: src/AssemblyInfo.cs(30,12): error CS0647: Error during emitting `System.Reflection.AssemblyVersionAttribute' attribute. The reason is `Could not find file "/etc/localtime"'

[Lucas Nussbaum]

Source: sdb
Version: 1.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> mkdir -p bin
> cp LICENSE bin/LICENSE
> mkdir -p bin
> cp README.md bin/README
> cp `pkg-config --variable=Sources mono-options` dep/Options.cs
> cp `pkg-config --variable=Sources mono-lineeditor` dep/getline.cs
> mkdir -p bin
> cp `pkg-config --variable=Libraries mono-cecil` bin/
> cp `pkg-config --variable=Libraries mono-debugger` bin/
> mcs -debug -langversion:future -unsafe -warnaserror -keyfile:mono.snk 
> -lib:bin -out:bin/sdb.exe -target:exe -r:Mono.Posix -r:Mono.Cecil.dll 
> -r:Mono.Cecil.Mdb.dll -r:Mono.Debugger.Soft.dll -r:Mono.Debugging.dll 
> -r:Mono.Debugging.Soft.dll -pkg:nrefactory dep/Options.cs dep/getline.cs 
> src/Commands/AttachCommand.cs src/Commands/BacktraceCommand.cs 
> src/Commands/BreakpointCommand.cs src/Commands/CatchpointCommand.cs 
> src/Commands/ConfigCommand.cs src/Commands/ConnectCommand.cs 
> src/Commands/ContinueCommand.cs src/Commands/DatabaseCommand.cs 
> src/Commands/DecompileCommand.cs src/Commands/DirectoryCommand.cs 
> src/Commands/DisassembleCommand.cs src/Commands/EnvironmentCommand.cs 
> src/Commands/FrameCommand.cs src/Commands/HelpCommand.cs 
> src/Commands/KillCommand.cs src/Commands/ListenCommand.cs 
> src/Commands/PluginCommand.cs src/Commands/PrintCommand.cs 
> src/Commands/QuitCommand.cs src/Commands/ResetCommand.cs 
> src/Commands/RootCommand.cs src/Commands/RunCommand.cs 
> src/Commands/SourceCommand.cs src/Commands/StepCommand.cs 
> src/Commands/ThreadCommand.cs src/Commands/WatchCommand.cs 
> src/AssemblyInfo.cs src/Color.cs src/Command.cs src/CommandAttribute.cs 
> src/CommandLine.cs src/Configuration.cs src/CustomLogger.cs src/Debugger.cs 
> src/LibEdit.cs src/Log.cs src/MultiCommand.cs src/Plugins.cs src/Program.cs 
> src/SessionKind.cs src/State.cs src/Utilities.cs
> warning CS8000: Language version `future' is no longer supported
> src/AssemblyInfo.cs(30,12): error CS0647: Error during emitting 
> `System.Reflection.AssemblyVersionAttribute' attribute. The reason is `Could 
> not find file "/etc/localtime"'
> Compilation failed: 1 error(s), 0 warnings
> Makefile:187: recipe for target 'bin/sdb.exe' failed
> make[2]: *** [bin/sdb.exe] 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 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/01/sdb_1.2-1_unstable.log

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

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