Processed: found 835185 in 1.1.5-1

[Debian Bug Tracking System]

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

> found 835185 1.1.5-1
Bug #835185 {Done: Rene Engelhard } [libmysqlcppconn7v5] 
mysql-workbench: Segfault when opening connection
Bug #836587 {Done: Rene Engelhard } [libmysqlcppconn7v5] 
mysql-workbench: Mysql-workbench opened ok but when I try to connect to db, it 
crashes with segfault
Bug #836731 {Done: Rene Engelhard } [libmysqlcppconn7v5] 
libmysqlcppconn7v5 version 1.1.4-2 crash Libreoffice Base
There is no source info for the package 'libmysqlcppconn7v5' at version 
'1.1.5-1' with architecture ''
Unable to make a source version for version '1.1.5-1'
Marked as found in versions 1.1.5-1 and reopened.
Marked as found in versions 1.1.5-1 and reopened.
Marked as found in versions 1.1.5-1 and reopened.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> block 832931 by  843926
Bug #832931 [src:mariadb-10.0] mariadb-10.0: FTBFS on powerpc
832931 was not blocked by any bugs.
832931 was not blocking any bugs.
Added blocking bug(s) of 832931: 843926
>
End of message, 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#843457: mysql-workbench: Dependency gdal-abi-2-1-1 no longer in repo

[Alessio]

2016-11-13 2:44 GMT+01:00 Dmitry Smirnov :
> On Thursday, 10 November 2016 9:16:16 AM AEDT Alessio Gaeta wrote:
>> Is this package abandoned?
> Sort of... It needs new upstream capable of maintaining fork...

Wow, that's bad news... At that point, the only way to go seems
pinning libgdal until possible.

There is no chance to embed the needed libraries? I know this is
strongly discouraged by Debian policies, but M-W is very useful (and
packages like chromium did it already).

Thank you. Regards
--
Alessio Gaeta

Bug#844160: Bug#828236: Bug#844160: marked as done (apache2-dev should depend on libssl1.0-dev)

[Adrian Bunk]

On Mon, Nov 14, 2016 at 08:44:35AM +0100, Ondřej Surý wrote:
> On Mon, Nov 14, 2016, at 08:21, Adrian Bunk wrote:
> > On Mon, Nov 14, 2016 at 05:03:45AM +0100, Ondřej Surý wrote:
> > > > Looking at mod_ssl_openssl.h and the comment in #828330,
> > > > I'd suggest the change below to add a dependency on libssl1.0-dev
> > > > to apache2-dev.
> > > 
> > > And that exactly happens meaning that PHP 7.0 can no longer be built
> > > unless all it's build-depends (including PHP 7.0) and rdepends move to
> > > libssl1.0-dev as well.
> > > 
> > > So a nice deadlock, right? To be honest I would rather have a slightly
> > > less tested apache2 with OpenSSL 1.1.0 and iron out the bugs as we go
> > > than revert all the work I have done.
> > > 
> > > I reviewed the patch Kurt has provided and I don't see any strong reason
> > > why anything should break.
> > >...
> > 
> > Can you guarantee that rdeps of Apache can use 1.0.2 in stretch when 
> > Apache itself uses 1.1?
> 
> Why?

How do you fix rdeps of Apache that are not compiling or working
stable with 1.1?

We are already inside the stretch freeze.

Many packages are not even compiling with 1.1

And run-time testing with 1.1 has not even begun for most packages.
Did you confirm that the Apache code you reviewed actually works
flawlessly? Runtime bugs like #843988 are possible.

> > That is the most important question here.
> 
> No, I think the question is:
> 
> Can we migrate (or drop) all rdeps to 1.0.2?

The answer is "yes, we can migrate all".

All OpenSSL-using packages in unstable were compiled with and using 
1.0.2 until libssl-dev switched from 1.0.2 to 1.1 just 2 weeks ago.

Even today 80% of all libssl dependencies in unstable are still
against libssl1.0.2 (1.1 binNMUs have not yet been done).

> > This is what my "mod_ssl_openssl.h and the comment in #828330"
> > was referring to.
> > 
> > The dual 1.0.2/1.1 setup for stretch can only work when any set of 
> > packages in the archive that needs the same OpenSSL version stays
> > at 1.0.2 unless *all* packages in this set are compiling and working
> > fine with 1.1
> 
> The *set* you are talking probably cover whole archive, since the
> Build-Depends of PHP are quite vast and here are the Build-Depends
> of Build-Depends:
> 
> (This is from stretch, not from unstable)
> apache2-dev libssl-dev (>= 0.9.8m)
> libc-client2007e-dev libssl-dev
> libcurl4-openssl-dev libssl-dev
> libevent-dev libssl-dev
> libkrb5-dev libssl-dev
> libpq-dev libssl-dev
> libsasl2-dev libssl-dev
> libsnmp-dev libssl-dev (>> 0.9.8)
> 
> Greping just Depends: on -dev packages is slightly more optimistic:
> 
> apache2-dev libssl-dev (<< 1.1)
> libc-client2007e-dev libssl-dev
> libpq-dev libssl-dev
> libsnmp-dev libssl-dev
> 
> But ultimately I am afraid that libssl dependencies are so entagled
> that it will cover all archive.

"all archive" is not correct, but more packages in stretch using
1.0.2 than 1.1 sounds realistic.

> > And since the OpenSSL version used is part of the libcurl3 ABI
> > (see #844018 for details), using 1.1 in stretch is anyway not
> > really an option for Apache/PHP in stretch.
> 
> What you are really saying is that using OpenSSL 1.1 is generally
> not an option for stretch.

It is not a realistic option for larger groups of packages that have to 
use the same OpenSSL version.

It was clear before the OpenSSL default changed that using only 1.1 in 
stretch would not be realistic.

It was known before the OpenSSL default changed that problems like with 
libcurl3 could happen.

Considering that we are already in the freeze, for any OpenSSL 1.1 
related problem without a simple and fast solution the only option
within the stretch release schedule is to move packages back to 1.0.2

> Cheers,

cu
Adrian

-- 

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

Bug#844132: marked as pending

[Aurelien Jarno]

tag 844132 pending
thanks

Hello,

Bug #844132 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-glibc/glibc.git;a=commitdiff;h=1966184

---
commit 19661849464f962a0a1b65733508976a708dfe08
Author: Aurelien Jarno 
Date:   Mon Nov 14 10:16:31 2016 +0100

Add bug number

diff --git a/debian/changelog b/debian/changelog
index 82b7346..dc0ad3f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -20,6 +20,7 @@ glibc (2.24-6) UNRELEASED; urgency=medium
 - Fix pread/pwrite syscalls on SH4.
 - Fix build on powerpc/ppc64el with binutils from trunk.  Closes: #843691.
 - Fix flexible array usage in gconv.h.  Closes: #841304.
+- Fix linknamespace parallel test failures.  Closes: #844132.
 
  -- Aurelien Jarno   Tue, 18 Oct 2016 23:17:42 +0200
 

Bug#828453: nginx: FTBFS with openssl 1.1.0

[Christos Trochalakis]

On Fri, Nov 11, 2016 at 12:46:49PM +0100, Moritz Muehlenhoff wrote:

B0;115;0cOn Fri, Nov 04, 2016 at 10:03:02AM +0200, Christos Trochalakis wrote:

On Wed, Nov 02, 2016 at 05:22:21PM +0100, Kurt Roeckx wrote:
>On Wed, Nov 02, 2016 at 10:39:29AM +0100, Moritz Muehlenhoff wrote:
>>
>>The issue hasn't been diagnosed upstream, but this will likely also affect 
nginx
>>once rebuilt against openssl 1.1.
>
>It seems it was fixed in OpenSSL in the mean time.
>

I have pushed all the needed changes to master.

I believe that we should wait for the bug to be fixed in Debian before
uploading. Kurt, do you plan to backport that change or wait for the
next OpenSSL release?


That patch is part of the openssl 1.1.0c release which was uploaded yesterday.

Cheers,
   Moritz


It is uploaded for sid but it hit the NEW queue (we introduced a new
binary package).

https://ftp-master.debian.org/new/nginx_1.10.2-2.html

Processed: Bug#844132 marked as pending

[Debian Bug Tracking System]

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

> tag 844132 pending
Bug #844132 [src:glibc] glibc: FTBFS: tests failed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: adjust aubio versions affected by 843482

[Debian Bug Tracking System]

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

> notfound 843482 0.4.1-2.2
Bug #843482 {Done: Paul Brossier } [src:aubio] aubio: FTBFS on 
PowerPC variants: test_zeros fails
No longer marked as found in versions aubio/0.4.1-2.2.
> found 843482 0.4.3-1
Bug #843482 {Done: Paul Brossier } [src:aubio] aubio: FTBFS on 
PowerPC variants: test_zeros fails
Ignoring request to alter found versions of bug #843482 to the same values 
previously set
> fixed 843482 0.4.3-2
Bug #843482 {Done: Paul Brossier } [src:aubio] aubio: FTBFS on 
PowerPC variants: test_zeros fails
Ignoring request to alter fixed versions of bug #843482 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#844291: marked as done (timidity FTBFS: fails to rebuild configure from configure.in, automake1.9 is no longer in unstable)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 11:45:10 +0200
with message-id <20161114094509.xecaz2e2rdpaw...@bunk.spdns.de>
and subject line Re: timidity FTBFS: fails to rebuild configure from 
configure.in, automake1.9 is no longer in unstable
has caused the Debian Bug report #844291,
regarding timidity FTBFS: fails to rebuild configure from configure.in, 
automake1.9 is no longer in unstable
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.)


-- 
844291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: timidity
Version: 2.13.2-40.5
Severity: serious
Justification: configure cannot be built from source
User: helm...@debian.org
Usertags: rebootstrap

timidity still builds fine on buildds, because it uses ./configure as a
pre-built artifact. Unfortunately ./configure cannot be regenerated
anymore, because autogen.sh relies on aclocal-1.9 which was formerly
part of automake1.9. The latter got removed from unstable two years ago.

There are essentially three ways to resolve this bug:
 * Move timidity to a newer automake.
 * Reintroduce automake1.9 into unstable.
 * Remove timidity.

Helmut
--- End Message ---
--- Begin Message ---
On Mon, Nov 14, 2016 at 07:14:07AM +0100, Helmut Grohne wrote:
> Source: timidity
> Version: 2.13.2-40.5
> Severity: serious
> Justification: configure cannot be built from source
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> timidity still builds fine on buildds, because it uses ./configure as a
> pre-built artifact. Unfortunately ./configure cannot be regenerated
> anymore, because autogen.sh relies on aclocal-1.9 which was formerly
> part of automake1.9. The latter got removed from unstable two years ago.
> 
> There are essentially three ways to resolve this bug:
>  * Move timidity to a newer automake.
>  * Reintroduce automake1.9 into unstable.
>  * Remove timidity.

* problems in a non-mandatory and unused script like autogen.sh
  are not RC bugs; autoreconf works

Closing.

> Helmut

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#842808: marked as done (gant: FTBFS: Cannot add task ':gant:install' as a task with that name already exists)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 09:49:28 +
with message-id 
and subject line Bug#842808: fixed in gant 1.9.11-5
has caused the Debian Bug report #842808,
regarding gant: FTBFS: Cannot add task ':gant:install' as a task with that name 
already exists
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.)


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

gant fails to build from source in unstable/amd64:

  […]

   debian/rules build
  dh build --buildsystem=gradle
 dh_testdir -O--buildsystem=gradle
 dh_update_autotools_config -O--buildsystem=gradle
 dh_auto_configure -O--buildsystem=gradle
 dh_auto_build -O--buildsystem=gradle
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 jar
  Starting Build
  Compiling initialization script 
'/home/lamby/temp/cdt.20161101123313.GJANPAnLhA.db.gant/gant-1.9.11/.gradle/init.d/init.gradle'
 using SubsetScriptTransformer.
  Compiling initialization script 
'/home/lamby/temp/cdt.20161101123313.GJANPAnLhA.db.gant/gant-1.9.11/.gradle/init.d/init.gradle'
 using BuildScriptTransformer.
Loading the Maven rules...
  Compiling settings file 
'/home/lamby/temp/cdt.20161101123313.GJANPAnLhA.db.gant/gant-1.9.11/settings.gradle'
 using SubsetScriptTransformer.
  Compiling settings file 
'/home/lamby/temp/cdt.20161101123313.GJANPAnLhA.db.gant/gant-1.9.11/settings.gradle'
 using BuildScriptTransformer.
  Settings evaluated using settings file 
'/home/lamby/temp/cdt.20161101123313.GJANPAnLhA.db.gant/gant-1.9.11/settings.gradle'.
  Projects loaded. Root project using build file 
'/home/lamby/temp/cdt.20161101123313.GJANPAnLhA.db.gant/gant-1.9.11/build.gradle'.
  Included projects: [root project 'gant-1.9.11', project ':gant', project 
':gant_groovy2.0', project ':gant_groovy2.1', project ':gant_groovy2.2', 
project ':gant_groovy2.3']
Keep-alive timer started
Adding Debian repository to project 'gant-1.9.11'
Adding Debian repository to project 'gant'
Adding Debian repository to project 'gant_groovy2.0'
Adding Debian repository to project 'gant_groovy2.1'
Adding Debian repository to project 'gant_groovy2.2'
Adding Debian repository to project 'gant_groovy2.3'
  Evaluating root project 'gant-1.9.11' using build file 
'/home/lamby/temp/cdt.20161101123313.GJANPAnLhA.db.gant/gant-1.9.11/build.gradle'.
  Compiling build file 
'/home/lamby/temp/cdt.20161101123313.GJANPAnLhA.db.gant/gant-1.9.11/build.gradle'
 using SubsetScriptTransformer.
  Compiling build file 
'/home/lamby/temp/cdt.20161101123313.GJANPAnLhA.db.gant/gant-1.9.11/build.gradle'
 using BuildScriptTransformer.
Replacing commons-cli:commons-cli:jar:1.2  ->  
commons-cli:commons-cli:jar:debian
Replacing org.apache.ant:ant:jar:1.9.2  ->  
org.apache.ant:ant:jar:debian
Passing through org.apache.ant:ant-parent:jar:debian
Replacing org.codehaus.groovy:groovy-all:jar:2.2.2  ->  
org.codehaus.groovy:groovy-all:jar:debian
Replacing junit:junit:jar:4.11  ->  junit:junit:jar:4.x
Replacing org.apache.ivy:ivy:jar:2.3.0  ->  
org.apache.ivy:ivy:jar:debian
Passing through org.apache.ant:ant-launcher:jar:debian
Passing through org.hamcrest:hamcrest-core:jar:debian
Replacing org.codehaus.groovy:groovy-all:jar:2.0.8  ->  
org.codehaus.groovy:groovy-all:jar:debian
Replacing org.codehaus.groovy:groovy-all:jar:2.1.9  ->  
org.codehaus.groovy:groovy-all:jar:debian
Replacing org.codehaus.groovy:groovy-all:jar:2.3.0  ->  
org.codehaus.groovy:groovy-all:jar:debian
  Evaluating project ':gant' using build file 
'/home/lamby/temp/cdt.20161101123313.GJANPAnLhA.db.gant/gant-1.9.11/gant/build.gradle'.
Adding task debianMavenPom to project 'gant'
  
  FAILURE: Build failed with an exception.
  
  * What went wrong:
  A problem occurred configuring project ':gant'.
  > Failed to apply plugin [id 'org.gradle.maven']
 > Cannot add task ':gant:install' as a task with that name already exists.
  
  * Try:
  Run with --debug option to get more log output.
  
  * Exception i

Bug#828496: marked as done (pgbouncer: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 10:04:46 +
with message-id 
and subject line Bug#828496: fixed in pgbouncer 1.7.2-2
has caused the Debian Bug report #828496,
regarding pgbouncer: FTBFS with openssl 1.1.0
to be marked as done.

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

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


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

Hi,

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

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Source: pgbouncer
Source-Version: 1.7.2-2

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated pgbouncer 
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, 14 Nov 2016 10:17:30 +0100
Source: pgbouncer
Binary: pgbouncer
Architecture: source
Version: 1.7.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 

Changed-By: Christoph Berg 
Description:
 pgbouncer  - lightweight connection pooler for PostgreSQL
Closes: 819178 828496
Changes:
 pgbouncer (1.7.2-2) unstable; urgency=medium
 .
   * Build-Depend on libssl1.0-dev. Closes: #828496.
   * Build-Depend on ca-certificates to correctly pick up
 /etc/ssl/certs/ca-certificates.crt. Closes: #819178.
Checksums-Sha1:
 fe1e91134c2fe6ca3f8b3e38c56211ff7cdd8345 2160 pgbouncer_1.7.2-2.dsc
 36bd5d3d3a917d05981d275150972e91b622accd 8720 pgbouncer_1.7.2-2.debian.tar.xz
Checksums-Sha256:
 b8e1362b9ef6a1316a7e00eee13241e48753658b8c485fff5fac07bf8b784d25 2160 
pgbouncer_1.7.2-2.dsc
 4dee03aeee08e17eaa8d1caa59e9daafb8c2cd5e25ded764834b17aec77c3830 8720 
pgbouncer_1.7.2-2.debian.tar.xz
Files:
 b6b95799567dc6c79db61ccb01775ee9 2160 database optional pgbouncer_1.7.2-2.dsc
 eb2c7c046bdfdb6e37b9d198f387b055 8720 database optional 
pgbouncer_1.7.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYKYTTAAoJEExaa6sS0qeuxbgP/i2PvTTS9xmK1zmP5RgcJdmd
xZpYj+nBS1AWMjW8YjzmknRkgcSCBmm8udeV6JBu+6zi1OkGiftBiaIllkM40UjR
I10gd6O6ACvGZ414oOW7QXCuINmsEGB6IV8z8vuR9FqvfGCB0xL8yM3Sntde3dsN
lxlSBVjLcPq3Wn92aK1Nc0JWm3LfpMHXESy2ctAjLL4+iDTKDKhDzZTy1PVBdpPV
TNMpBJe4/+lgTjt5tZbf7+RHuIFtuuw+R6TvclRSjDx1n+j7cebTozVS8m/vWuN0
8aseVSzpCKJHYgUtT9U/3jFgFH/+S5G0jEZfMP7FUXijafSiCvSmhBTGmPBoPgBD
vjW0QQNSnba5uXGjemvj1VbqHoDVByfBrRtE6sPAD3dUY3h+39PYejbjdtxFhaXZ
GaEjbVP5SD3wtb7VZ+Mh1lHpDSoqATXQfBRDnGIRLPEBtnZFjGqEVsoC79MAECD/
x+wY3ShM3HlT57KAh5s8DGa8nIcz/9spKTPC3H7xIJBzW096KDub76KmS2i+TbKk
UyD/IxiijgJ5tVBw3D7N06afQTZEqW7KWJQ7fvlB/X38rYRWrkeuzX+iw9YoIA1H
R8oymoEChNHwCA1J0LchGy9ZG/s7uE3m68cw6EDHC69vfLID0ldqRB40pJC9F7k5
Oj5zAzxXgKVPXodE47L0
=W29x
-END PGP SIGNATURE End Message ---

Bug#844263: libxml-security-c-dev: depending on libssl1.0-dev breaks open-vm-tools

[Ferenc Wágner]

Russ Allbery  writes:

> Bernd Zeimetz  writes:
>
>> unfortunately your decision to depend on libssl1.0-dev breaks the build
>> open-vm-tools as most other build-dependencies decided to migrate to
>> the new openssl version.
>
>> I know that shibboleth is the issue, but the current situation breaks
>> open-vm-tools, which is a requirement if you want to run Debian on
>> vmware - and there are *loads* of installations out there.
>
> Well, my understanding is that xml-security-c doesn't support OpenSSL 1.1
> upstream, the porting is not trivial, and will not be completed in the
> release time frame.  So I'm not sure there's any other alternative.
>
> Whatever dependencies that were pushing open-vm-tools to 1.1 may have to
> be reverted back to 1.0.

Just adding that Shibboleth itself is also problematic, because
XMLTooling, which is incompatible with OpenSSL 1.1, uses libcurl, which
already switched to OpenSSL 1.1.  So switching xml-security-c to OpenSSL
1.0 did not actually solve the problem for Shibboleth because of the
above version clash in XMLTooling.  While I've got the patches porting
xml-security-c and XMLTooling to OpenSSL 1.1, they aren't integrated
into upstream yet (and probably won't ever be in their current form).
So at least libcurl will have to be switched back to OpenSSL 1.0, or
the Shibboleth stack will see serious trouble.  Shall I bring it up with
the curl maintainers?  Or wait for the conclusion on debian-devel?
-- 
Thanks,
Feri

Bug#844299: big $HISTSIZE causes exessive memory usage

[Jonas Meurer]

Package: bash
Version: 4.4-1
Severity: serious

Hello,

apparently bash 4.4 as available in Debian Stretch introduced a
regression compared to 4.3 from Debian Jessie: when setting $HISTSIZE to
a big value (e.g.  as suggested in a lot of docs out there on
the web), the resulting bash process seems to allocate way to much
memory, approximately 800MB each.

I consider this a severe memory leak/consumption bug, thus setting
severity to serious. Feel free to lower severity if you disagree.

It's not enough to set the environment variable $HISTSIZE in a running
bash session. Instead, it needs to set at invocation of the shell, e.g.
by setting it in the ~/.bashrc:

HISTSIZE=

Here's the process status page of a process with HISTSIZE=:

$ cat /proc/3156/status
Name:   bash
Umask:  0022
State:  S (sleeping)
Tgid:   3156
Ngid:   0
Pid:3156
PPid:   2796
TracerPid:  0
Uid:1000100010001000
Gid:1000100010001000
FDSize: 256
Groups: 24 25 27 29 30 44 46 107 111 123 125 126 127 1000 
NStgid: 3156
NSpid:  3156
NSpgid: 3156
NSsid:  3156
VmPeak:  1071904 kB
VmSize:  1071868 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM:787328 kB
VmRSS:787328 kB
RssAnon:  783640 kB
RssFile:3688 kB
RssShmem:  0 kB
VmData:  1050920 kB
VmStk:   136 kB
VmExe:  1024 kB
VmLib:  2116 kB
VmPTE:  1600 kB
VmPMD:16 kB
VmSwap:0 kB
HugetlbPages:  0 kB
Threads:1
SigQ:   0/45722
SigPnd: 
ShdPnd: 
SigBlk: 0001
SigIgn: 00380004
SigCgt: 4b817efb
CapInh: 
CapPrm: 
CapEff: 
CapBnd: 003f
CapAmb: 
Seccomp:0
Cpus_allowed:   ff
Cpus_allowed_list:  0-7
Mems_allowed:   ,0001
Mems_allowed_list:  0
voluntary_ctxt_switches:30
nonvoluntary_ctxt_switches: 13

And here you find the status page of a bash process with default
HISTSIZE=1000:

$ cat /proc/6888/status
Name:   bash
Umask:  0022
State:  S (sleeping)
Tgid:   6888
Ngid:   0
Pid:6888
PPid:   2796
TracerPid:  0
Uid:1000100010001000
Gid:1000100010001000
FDSize: 256
Groups: 24 25 27 29 30 44 46 107 111 123 125 126 127 1000 
NStgid: 6888
NSpid:  6888
NSpgid: 6888
NSsid:  6888
VmPeak:23220 kB
VmSize:23156 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM:  6028 kB
VmRSS:  6028 kB
RssAnon:2248 kB
RssFile:3780 kB
RssShmem:  0 kB
VmData: 2208 kB
VmStk:   136 kB
VmExe:  1024 kB
VmLib:  2116 kB
VmPTE:64 kB
VmPMD:12 kB
VmSwap:0 kB
HugetlbPages:  0 kB
Threads:1
SigQ:   0/45722
SigPnd: 
ShdPnd: 
SigBlk: 0001
SigIgn: 00380004
SigCgt: 4b817efb
CapInh: 
CapPrm: 
CapEff: 
CapBnd: 003f
CapAmb: 
Seccomp:0
Cpus_allowed:   ff
Cpus_allowed_list:  0-7
Mems_allowed:   ,0001
Mems_allowed_list:  0
voluntary_ctxt_switches:57
nonvoluntary_ctxt_switches: 7

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

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) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bash depends on:
ii  base-files   9.6
ii  dash 0.5.8-2.3
ii  debianutils  4.8
ii  libc62.24-5
ii  libtinfo56.0+20160917-1

Versions of packages bash recommends:
ii  bash-completion  1:2.1-4.3

Versions of packages bash suggests:
pn  bash-doc  

-- no debconf information

Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Vincent Lefevre]

Package: nvidia-driver-libs
Version: 367.57-2
Severity: grave
Justification: renders package unusable

I got the folloing failure when upgrading with aptitude:

Preconfiguring packages ...
(Reading database ... 528479 files and directories currently installed.)
Removing nvidia-driver-libs-i386:i386 (367.57-1) ...
Removing libopengl0-glvnd-nvidia:i386 (367.57-1) ...
Removing nvidia-vulkan-icd:i386 (367.57-1) ...
Removing libglx-nvidia0:i386 (367.57-1) ...
Removing libglx0-glvnd-nvidia:i386 (367.57-1) ...
Removing libgles-nvidia2:i386 (367.57-1) ...
Removing libgles2-glvnd-nvidia:i386 (367.57-1) ...
Removing libgles-nvidia1:i386 (367.57-1) ...
Removing libgles1-glvnd-nvidia:i386 (367.57-1) ...
Removing libgles-nvidia1:amd64 (367.57-1) ...
Removing libgles-nvidia2:amd64 (367.57-1) ...
Removing libgles1-glvnd-nvidia:amd64 (367.57-1) ...
Removing libgles2-glvnd-nvidia:amd64 (367.57-1) ...
Removing nvidia-vulkan-icd:amd64 (367.57-1) ...
Removing libglx-nvidia0:amd64 (367.57-1) ...
Removing libglx0-glvnd-nvidia:amd64 (367.57-1) ...
Removing libnvidia-cfg1:amd64 (367.57-1) ...
Removing libnvidia-cfg1:i386 (367.57-1) ...
Removing libopengl0-glvnd-nvidia:amd64 (367.57-1) ...
Removing libvulkan1:i386 (1.0.26.0+dfsg1-1) ...
Removing libvulkan1:amd64 (1.0.26.0+dfsg1-1) ...
Removing nvidia-vulkan-common (367.57-1) ...
(Reading database ... 528357 files and directories currently installed.)
Preparing to unpack .../00-xserver-xorg-video-nvidia_367.57-2_amd64.deb ...
Unpacking xserver-xorg-video-nvidia (367.57-2) over (367.57-1) ...
Preparing to unpack .../01-nvidia-kernel-support_367.57-2_amd64.deb ...
Unpacking nvidia-kernel-support (367.57-2) over (367.57-1) ...
Preparing to unpack .../02-nvidia-driver-bin_367.57-2_amd64.deb ...
Unpacking nvidia-driver-bin (367.57-2) over (367.57-1) ...
Preparing to unpack .../03-libnvidia-ml1_367.57-2_amd64.deb ...
Unpacking libnvidia-ml1:amd64 (367.57-2) over (367.57-1) ...
Preparing to unpack .../04-nvidia-driver-libs_367.57-2_amd64.deb ...
De-configuring nvidia-driver-libs:i386 (367.57-1) ...
Unpacking nvidia-driver-libs:amd64 (367.57-2) over (367.57-1) ...
Preparing to unpack .../05-libnvidia-glcore_367.57-2_amd64.deb ...
De-configuring libnvidia-glcore:i386 (367.57-1) ...
Unpacking libnvidia-glcore:amd64 (367.57-2) over (367.57-1) ...
Preparing to unpack .../06-libnvidia-glcore_367.57-2_i386.deb ...
Unpacking libnvidia-glcore:i386 (367.57-2) over (367.57-1) ...
Preparing to unpack .../07-libgl1-nvidia-glx_367.57-2_i386.deb ...
De-configuring libgl1-nvidia-glx:amd64 (367.57-1) ...
Unpacking libgl1-nvidia-glx:i386 (367.57-2) over (367.57-1) ...
Preparing to unpack .../08-libgl1-nvidia-glx_367.57-2_amd64.deb ...
Unpacking libgl1-nvidia-glx:amd64 (367.57-2) over (367.57-1) ...
Preparing to unpack .../09-libegl1-glvnd-nvidia_367.57-2_amd64.deb ...
De-configuring libegl1-glvnd-nvidia:i386 (367.57-1) ...
Unpacking libegl1-glvnd-nvidia:amd64 (367.57-2) over (367.57-1) ...
Preparing to unpack .../10-libegl-nvidia0_367.57-2_amd64.deb ...
De-configuring libegl-nvidia0:i386 (367.57-1) ...
Unpacking libegl-nvidia0:amd64 (367.57-2) over (367.57-1) ...
Preparing to unpack .../11-nvidia-alternative_367.57-2_amd64.deb ...
Unpacking nvidia-alternative (367.57-2) over (367.57-1) ...
Preparing to unpack .../12-nvidia-driver_367.57-2_amd64.deb ...
Unpacking nvidia-driver (367.57-2) over (367.57-1) ...
Preparing to unpack .../13-nvidia-vdpau-driver_367.57-2_amd64.deb ...
Unpacking nvidia-vdpau-driver:amd64 (367.57-2) over (367.57-1) ...
Preparing to unpack .../14-libgldispatch0-nvidia_367.57-2_amd64.deb ...
De-configuring libgldispatch0-nvidia:i386 (367.57-1) ...
Unpacking libgldispatch0-nvidia:amd64 (367.57-2) over (367.57-1) ...
Preparing to unpack .../15-libnvidia-eglcore_367.57-2_amd64.deb ...
De-configuring libnvidia-eglcore:i386 (367.57-1) ...
Unpacking libnvidia-eglcore:amd64 (367.57-2) over (367.57-1) ...
Preparing to unpack .../16-nvidia-legacy-check_367.57-2_amd64.deb ...
Unpacking nvidia-legacy-check (367.57-2) over (367.57-1) ...
Processing triggers for glx-alternative-nvidia (0.7.4) ...
dpkg: error processing package nvidia-driver-libs:amd64 (--configure):
 package nvidia-driver-libs:amd64 367.57-2 cannot be configured because 
nvidia-driver-libs:i386 is at a different version (367.57-1)
Processing triggers for mime-support (3.60) ...
dpkg: error processing package libnvidia-eglcore:amd64 (--configure):
 package libnvidia-eglcore:amd64 367.57-2 cannot be configured because 
libnvidia-eglcore:i386 is at a different version (367.57-1)
dpkg: error processing package libgldispatch0-nvidia:amd64 (--configure):
 package libgldispatch0-nvidia:amd64 367.57-2 cannot be configured because 
libgldispatch0-nvidia:i386 is at a different version (367.57-1)
Processing triggers for desktop-file-utils (0.23-1) ...
Setting up libnvidia-glcore:amd64 (367.57-2) ...
Setting up libnvidia-glcore:i386 (367.57-2) ...
dpkg: error processing package libegl1-glvnd-nvidia:amd64 (--configure):
 package libegl1-glvnd-nv

Bug#844303: ncrack: FTBFS: configure:6846: error: ./configure failed for opensshlib

[Chris Lamb]

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

Dear Maintainer,

ncrack fails to build from source in unstable/amd64:

  […]

  | main ()
  | {
  | #if BYTE_ORDER != BIG_ENDIAN
  |  not big endian
  | #endif
  | 
  |   ;
  |   return 0;
  | }
  configure:5000: result: no
  configure:5019: checking if struct in_addr is a wacky huge structure (some 
Sun boxes)
  configure:5033: gcc -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 conftest.c >&5
  conftest.c: In function 'main':
  conftest.c:25:20: error: 'struct in_addr' has no member named '_S_un'
   struct in_addr i; i._S_un._S_addr;
  ^
  configure:5033: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME ""
  | #define PACKAGE_TARNAME ""
  | #define PACKAGE_VERSION ""
  | #define PACKAGE_STRING ""
  | #define PACKAGE_BUGREPORT ""
  | #define PACKAGE_URL ""
  | #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_PWD_H 1
  | #define HAVE_TERMIOS_H 1
  | /* end confdefs.h.  */
  | #include 
  | int
  | main ()
  | {
  | struct in_addr i; i._S_un._S_addr;
  |   ;
  |   return 0;
  | }
  configure:5053: gcc -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 conftest.c >&5
  conftest.c: In function 'main':
  conftest.c:26:20: error: 'struct in_addr' has no member named 'S_un'
   struct in_addr i; i.S_un.S_addr;
  ^
  configure:5053: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME ""
  | #define PACKAGE_TARNAME ""
  | #define PACKAGE_VERSION ""
  | #define PACKAGE_STRING ""
  | #define PACKAGE_BUGREPORT ""
  | #define PACKAGE_URL ""
  | #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_PWD_H 1
  | #define HAVE_TERMIOS_H 1
  | /* end confdefs.h.  */
  | #include 
  | #include 
  | int
  | main ()
  | {
  | struct in_addr i; i.S_un.S_addr;
  |   ;
  |   return 0;
  | }
  configure:5061: result: no
  configure:5071: checking for strerror
  configure:5071: gcc -o conftest -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c  >&5
  configure:5071: $? = 0
  configure:5071: result: yes
  configure:5082: checking for signal
  configure:5082: gcc -o conftest -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c  >&5
  configure:5082: $? = 0
  configure:5082: result: yes
  configure:5103: checking for type of 6th argument to recvfrom()
  configure:5124: g++ -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -O2 -Wall 
-fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 conftest.cpp >&5
  configure:5124: $? = 0
  configure:5138: result: socklen_t
  configure:5178: checking openssl/ssl.h usability
  configure:5178: gcc -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:5178: $? = 0
  configure:5178: result: yes
  configure:5178: checking openssl/ssl.h presence
  configure:5178: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
  configure:5178: $? = 0
  configure:5178: result: yes
  configure:5178: checking for openssl/ssl.h
  configure:5178: result: yes
  configure:5195: checking for BIO_int_ctrl in -lcrypto
  configure:5220: gcc -o conftest -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c -lcrypto   >&5
  configure:5220: $? = 0
  configure:5229: result: yes
  configure:5246: checking for SSL_new in -lssl
  configure:5271: gcc -o

Bug#844304: python-mysqldb: FTBFS: x86_64-linux-gnu-gcc: error: .specs: No such file or directory

[Chris Lamb]

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

Dear Maintainer,

python-mysqldb fails to build from source in unstable/amd64:

  […]

  Get:1 http://httpredir.debian.org/debian sid/main amd64 mysql-common all 
5.8+1.0.1 [5436 B]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 libmysqlclient20 
amd64 5.7.16-1 [872 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 zlib1g-dev amd64 
1:1.2.8.dfsg-2+b3 [205 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libmysqlclient-dev 
amd64 5.7.16-1 [1218 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 python-all amd64 
2.7.11-2 [938 B]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libpython2.7-dbg 
amd64 2.7.12-5 [4651 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libpython-dbg amd64 
2.7.11-2 [19.8 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 libpython-all-dbg 
amd64 2.7.11-2 [1074 B]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 python2.7-dbg amd64 
2.7.12-5 [7872 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 python-dbg amd64 
2.7.11-2 [1204 B]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 python-all-dbg amd64 
2.7.11-2 [956 B]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 libpython2.7 amd64 
2.7.12-5 [1072 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 libexpat1-dev amd64 
2.2.0-1 [128 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 libpython2.7-dev 
amd64 2.7.12-5 [28.2 MB]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 libpython-dev amd64 
2.7.11-2 [19.8 kB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 libpython-all-dev 
amd64 2.7.11-2 [952 B]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 python2.7-dev amd64 
2.7.12-5 [281 kB]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 python-dev amd64 
2.7.11-2 [1128 B]
  Get:19 http://httpredir.debian.org/debian sid/main amd64 python-all-dev amd64 
2.7.11-2 [954 B]
  Get:20 http://httpredir.debian.org/debian sid/main amd64 python-setuptools 
all 28.7.1-1 [218 kB]
  Get:21 http://httpredir.debian.org/debian sid/main amd64 libpython3.5-dbg 
amd64 3.5.2-7 [9414 kB]
  Get:22 http://httpredir.debian.org/debian sid/main amd64 libpython3-dbg amd64 
3.5.1-4 [18.6 kB]
  Get:23 http://httpredir.debian.org/debian sid/main amd64 libpython3-all-dbg 
amd64 3.5.1-4 [952 B]
  Get:24 http://httpredir.debian.org/debian sid/main amd64 python3-all amd64 
3.5.1-4 [928 B]
  Get:25 http://httpredir.debian.org/debian sid/main amd64 python3.5-dbg amd64 
3.5.2-7 [10.8 MB]
  Get:26 http://httpredir.debian.org/debian sid/main amd64 python3-dbg amd64 
3.5.1-4 [1196 B]
  Get:27 http://httpredir.debian.org/debian sid/main amd64 python3-all-dbg 
amd64 3.5.1-4 [950 B]
  Get:28 http://httpredir.debian.org/debian sid/main amd64 libpython3.5 amd64 
3.5.2-7 [1370 kB]
  Get:29 http://httpredir.debian.org/debian sid/main amd64 libpython3.5-dev 
amd64 3.5.2-7 [37.7 MB]
  Get:30 http://httpredir.debian.org/debian sid/main amd64 libpython3-dev amd64 
3.5.1-4 [18.7 kB]
  Get:31 http://httpredir.debian.org/debian sid/main amd64 libpython3-all-dev 
amd64 3.5.1-4 [954 B]
  Get:32 http://httpredir.debian.org/debian sid/main amd64 python3.5-dev amd64 
3.5.2-7 [413 kB]
  Get:33 http://httpredir.debian.org/debian sid/main amd64 python3-dev amd64 
3.5.1-4 [1152 B]
  Get:34 http://httpredir.debian.org/debian sid/main amd64 python3-all-dev 
amd64 3.5.1-4 [956 B]
  Get:35 http://httpredir.debian.org/debian sid/main amd64 
python3-pkg-resources all 28.7.1-1 [135 kB]
  Get:36 http://httpredir.debian.org/debian sid/main amd64 python3-setuptools 
all 28.7.1-1 [137 kB]
  Fetched 105 MB in 3s (32.8 MB/s)
  Selecting previously unselected package mysql-common.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23473 files and directories currently installed.)
  Preparing to unpack .../00-mysql-common_5.8+1.0.1_all.deb ...
  Unpacking mysql-common (5.8+1.0.1) ...
  Selecting previously unselected package libmysqlclient20:amd64.
  Preparing to unpack .../01-libmysqlclient20_5.7.16-1_amd64.deb ...
  Unpacking libmysqlclient20:amd64 (5.7.16-1) ...
  Selecting previously unselected package zlib1g-dev:amd64.
  Preparing to unpack .../02-zlib1g-dev_1%3a1.2.8.dfsg-2+b3_amd64.deb ...
  U

Bug#804193: marked as done (ndiff python module is not installed)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 11:35:50 +0100
with message-id <87eg2ez6ux@msgid.hilluzination.de>
and subject line Fixed in 6.47-3+deb8u1
has caused the Debian Bug report #804193,
regarding ndiff python module is not installed
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.)


-- 
804193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ndiff
Version: 6.47-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The ndiff utility exits with the following error: Could not import the 
ndiff module: 'No module named ndiff'.

The problem was already fixed for the testing debian branch, please also fix it
for stable. See debian bug #789776


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
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)

Versions of packages ndiff depends on:
ii  python-lxml  3.4.0-1
pn  python:any   

Versions of packages ndiff recommends:
ii  nmap  6.47-3+b1

ndiff suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 6.47-3+deb8u1

This bug has been fixed in an update to the jessie distribution.

Cheers,
-Hilko--- End Message ---

Bug#828254: bro: FTBFS with openssl 1.1.0

[Sascha Steinbiss]

Hi Hilko and Kurt,

some progress on this: I have modified Hilko's patch to use new API
functions to access the OCSP response info, see attachment. This seems
to have been the last issue, Bro builds fine with this patch for me with
no additional API breaks.

Unfortunately my additions require the changes from OpenSSL pull request
#1876 [1]. Let's hope that there will be another release with that fix
before the stretch freeze... Kurt, do you think that would be realistic?
Otherwise we'll have to look into other options, up to removing OCSP
functionality from Bro.

I'd be happy to receive some comments. Thanks!

Cheers
Sascha

[1] https://github.com/openssl/openssl/pull/1876
--- a/src/File.cc
+++ b/src/File.cc
@@ -688,7 +688,7 @@
 	// Depending on the OpenSSL version, EVP_*_cbc()
 	// returns a const or a non-const.
 	EVP_CIPHER* cipher_type = (EVP_CIPHER*) EVP_bf_cbc();
-	cipher_ctx = new EVP_CIPHER_CTX;
+	cipher_ctx = EVP_CIPHER_CTX_new();
 
 	unsigned char secret[EVP_PKEY_size(pub_key)];
 	unsigned char* psecret = secret;
@@ -743,7 +743,7 @@
 			return;
 			}
 
-		delete cipher_ctx;
+		EVP_CIPHER_CTX_free(cipher_ctx);
 		cipher_ctx = 0;
 		}
 	}
--- a/src/file_analysis/analyzer/x509/X509.cc
+++ b/src/file_analysis/analyzer/x509/X509.cc
@@ -138,7 +138,9 @@
 	// we only read 255 bytes because byte 256 is always 0.
 	// if the string is longer than 255, that will be our null-termination,
 	// otherwhise i2t does null-terminate.
-	if ( ! i2t_ASN1_OBJECT(buf, 255, ssl_cert->cert_info->key->algor->algorithm) )
+	ASN1_OBJECT *algorithm;
+	X509_PUBKEY_get0_param(&algorithm, NULL, NULL, NULL, X509_get_X509_PUBKEY(ssl_cert));
+	if ( ! i2t_ASN1_OBJECT(buf, 255, algorithm) )
 		buf[0] = 0;
 
 	pX509Cert->Assign(7, new StringVal(buf));
@@ -149,14 +151,12 @@
 	// actually should be (namely - rsaEncryption), so that OpenSSL will parse out the
 	// key later. Otherwise it will just fail to parse the certificate key.
 
-	ASN1_OBJECT* old_algorithm = 0;
-	if ( OBJ_obj2nid(ssl_cert->cert_info->key->algor->algorithm) == NID_md5WithRSAEncryption )
-		{
-		old_algorithm = ssl_cert->cert_info->key->algor->algorithm;
-		ssl_cert->cert_info->key->algor->algorithm = OBJ_nid2obj(NID_rsaEncryption);
-		}
+	if ( X509_get_signature_nid(ssl_cert) == NID_md5WithRSAEncryption )
+		X509_PUBKEY_set0_param(X509_get_X509_PUBKEY(ssl_cert), OBJ_nid2obj(NID_rsaEncryption), 0, NULL, NULL, 0);
+else
+		algorithm = 0;
 
-	if ( ! i2t_ASN1_OBJECT(buf, 255, ssl_cert->sig_alg->algorithm) )
+	if ( ! i2t_ASN1_OBJECT(buf, 255, OBJ_nid2obj(X509_get_signature_nid(ssl_cert))) )
 		buf[0] = 0;
 
 	pX509Cert->Assign(8, new StringVal(buf));
@@ -165,14 +165,16 @@
 	EVP_PKEY *pkey = X509_extract_key(ssl_cert);
 	if ( pkey != NULL )
 		{
-		if ( pkey->type == EVP_PKEY_DSA )
+		if ( EVP_PKEY_base_id(pkey) == EVP_PKEY_DSA )
 			pX509Cert->Assign(9, new StringVal("dsa"));
 
-		else if ( pkey->type == EVP_PKEY_RSA )
+		else if ( EVP_PKEY_base_id(pkey) == EVP_PKEY_RSA )
 			{
 			pX509Cert->Assign(9, new StringVal("rsa"));
 
-			char *exponent = BN_bn2dec(pkey->pkey.rsa->e);
+			const BIGNUM *e;
+			RSA_get0_key(EVP_PKEY_get0_RSA(pkey), NULL, &e, NULL);
+			char *exponent = BN_bn2dec(e);
 			if ( exponent != NULL )
 {
 pX509Cert->Assign(11, new StringVal(exponent));
@@ -181,7 +183,7 @@
 }
 			}
 #ifndef OPENSSL_NO_EC
-		else if ( pkey->type == EVP_PKEY_EC )
+		else if ( EVP_PKEY_base_id(pkey) == EVP_PKEY_EC )
 			{
 			pX509Cert->Assign(9, new StringVal("ecdsa"));
 			pX509Cert->Assign(12, KeyCurve(pkey));
@@ -190,8 +192,8 @@
 
 		// set key algorithm back. We do not have to free the value that we created because (I think) it
 		// comes out of a static array from OpenSSL memory.
-		if ( old_algorithm )
-			ssl_cert->cert_info->key->algor->algorithm = old_algorithm;
+		if ( algorithm )
+			X509_PUBKEY_set0_param(X509_get_X509_PUBKEY(ssl_cert), algorithm, 0, NULL, NULL, 0);
 
 		unsigned int length = KeyLength(pkey);
 		if ( length > 0 )
@@ -262,7 +264,7 @@
 
 	BIO *bio = BIO_new(BIO_s_mem());
 	if( ! X509V3_EXT_print(bio, ex, 0, 0))
-		M_ASN1_OCTET_STRING_print(bio,ex->value);
+		ASN1_STRING_print(bio,(ASN1_STRING *)X509_EXTENSION_get_data(ex));
 
 	StringVal* ext_val = GetExtensionFromBIO(bio);
 
@@ -444,7 +446,7 @@
 	// well, we do not have EC-Support...
 	return NULL;
 #else
-	if ( key->type != EVP_PKEY_EC )
+	if ( EVP_PKEY_base_id(key) != EVP_PKEY_EC )
 		{
 		// no EC-key - no curve name
 		return NULL;
@@ -452,7 +454,7 @@
 
 	const EC_GROUP *group;
 	int nid;
-	if ( (group = EC_KEY_get0_group(key->pkey.ec)) == NULL)
+	if ( (group = EC_KEY_get0_group(EVP_PKEY_get0_EC_KEY(key))) == NULL)
 		// I guess we could not parse this
 		return NULL;
 
@@ -473,12 +475,16 @@
 	{
 	assert(key != NULL);
 
-	switch(key->type) {
+	switch(EVP_PKEY_base_id(key)) {
 	case EVP_PKEY_RSA:
-		return BN_num_bits(key->pkey.rsa->n);
+		const BIGNUM *n;
+		RSA_get0_key(EVP_PKEY_get0_RSA(key), &n, NULL, NULL);
+		return BN_num_bits(n);
 
 	case EVP_PKEY_DSA:
-		return BN

Bug#844302: libapache-mod-musicindex: FTBFS: x86_64-linux-gnu-gcc: error: .specs: No such file or directory

[Chris Lamb]

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

Dear Maintainer,

libapache-mod-musicindex fails to build from source in unstable/amd64:

  […]

  Unpacking libarchive-dev:amd64 (3.2.1-5) ...
  Selecting previously unselected package mysql-common.
  Preparing to unpack .../29-mysql-common_5.8+1.0.1_all.deb ...
  Unpacking mysql-common (5.8+1.0.1) ...
  Selecting previously unselected package libmysqlclient20:amd64.
  Preparing to unpack .../30-libmysqlclient20_5.7.16-1_amd64.deb ...
  Unpacking libmysqlclient20:amd64 (5.7.16-1) ...
  Selecting previously unselected package libmysqlclient-dev.
  Preparing to unpack .../31-libmysqlclient-dev_5.7.16-1_amd64.deb ...
  Unpacking libmysqlclient-dev (5.7.16-1) ...
  Selecting previously unselected package libmp4v2-2.
  Preparing to unpack .../32-libmp4v2-2_2.0.0~dfsg0-5_amd64.deb ...
  Unpacking libmp4v2-2 (2.0.0~dfsg0-5) ...
  Selecting previously unselected package libmp4v2-dev.
  Preparing to unpack .../33-libmp4v2-dev_2.0.0~dfsg0-5_amd64.deb ...
  Unpacking libmp4v2-dev (2.0.0~dfsg0-5) ...
  Setting up libldap2-dev:amd64 (2.4.42+dfsg-2+b3) ...
  Setting up libapr1:amd64 (1.5.2-4) ...
  Setting up libid3tag0:amd64 (0.15.1b-12) ...
  Setting up libsctp1:amd64 (1.0.17+dfsg-1) ...
  Setting up mysql-common (5.8+1.0.1) ...
  update-alternatives: using /etc/mysql/my.cnf.fallback to provide 
/etc/mysql/my.cnf (my.cnf) in auto mode
  Setting up uuid-dev:amd64 (2.29-1) ...
  Setting up libmp4v2-2 (2.0.0~dfsg0-5) ...
  Setting up libogg0:amd64 (1.3.2-1) ...
  Setting up pkg-config (0.29-4) ...
  Processing triggers for libc-bin (2.24-5) ...
  Setting up libaprutil1:amd64 (1.5.4-2) ...
  Setting up openssl (1.1.0c-1) ...
  Setting up libexpat1-dev:amd64 (2.2.0-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libmysqlclient20:amd64 (5.7.16-1) ...
  Setting up libmad0:amd64 (0.15.1b-8) ...
  Setting up libmp4v2-dev (2.0.0~dfsg0-5) ...
  Setting up libvorbis0a:amd64 (1.3.5-3) ...
  Setting up libogg-dev:amd64 (1.3.2-1) ...
  Setting up liblzo2-2:amd64 (2.08-1.2) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b3) ...
  Setting up libvorbisfile3:amd64 (1.3.5-3) ...
  Setting up libsctp-dev (1.0.17+dfsg-1) ...
  Setting up libmad0-dev (0.15.1b-8) ...
  Setting up libapr1-dev (1.5.2-4) ...
  Setting up libmysqlclient-dev (5.7.16-1) ...
  Setting up libarchive13:amd64 (3.2.1-5) ...
  Setting up libaprutil1-dev (1.5.4-2) ...
  Setting up libflac8:amd64 (1.3.1-4) ...
  Setting up libssl1.0-dev:amd64 (1.0.2j-4) ...
  Setting up libid3tag0-dev (0.15.1b-12) ...
  Setting up libvorbisenc2:amd64 (1.3.5-3) ...
  Setting up apache2-dev (2.4.23-7) ...
  Setting up libarchive-dev:amd64 (3.2.1-5) ...
  Setting up libvorbis-dev:amd64 (1.3.5-3) ...
  Setting up libflac-dev:amd64 (1.3.1-4) ...
  Setting up libapache-mod-musicindex-build-deps (1.4.1-1) ...
  Processing triggers for libc-bin (2.24-5) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=f724196aba34
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20161114094607.osX7pL8bcm.db.libapache-mod-musicindex/libapache-mod-musicindex-1.4.1
  
OLDPWD=/home/lamby/temp/cdt.20161114094607.osX7pL8bcm.db.libapache-mod-musicindex
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building libapache-mod-musicindex 1.4.1-1 on amd64 
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package libapache-mod-musicindex
  dpkg-buildpackage: info: source version 1.4.1-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Thibaut VARENE 
   dpkg-source --before-build libapache-mod-musicindex-1.4.1
  dpkg-buildpackage: info: host architecture amd64
  dpkg-source: info: using options from 
libapache-mod-musicindex-1.4.1/debian/source/options: 
--extend-diff-ignore=(^|/)(config.sub|config.guess|configure

Bug#844301: arc-gui-clients: FTBFS: /usr/include/openssl/asn1_mac.h:10:2: error: #error "This file is obsolete; please update your software."

[Chris Lamb]

Source: arc-gui-clients
Version: 0.4.6-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,

arc-gui-clients fails to build from source in unstable/amd64:

  […]

  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.12-1) ...
  Setting up liblzo2-2:amd64 (2.08-1.2) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b3) ...
  Setting up libjsoncpp1:amd64 (1.7.4-3) ...
  Setting up libgstreamer-plugins-base1.0-0:amd64 (1.10.0-1) ...
  Setting up libpcre3-dev:amd64 (2:8.39-2) ...
  Setting up fontconfig-config (2.11.0-6.7) ...
  Setting up libxmlsec1-openssl (1.2.20-2+b3) ...
  Setting up libmng1:amd64 (1.0.10+dfsg-3.1+b3) ...
  Setting up libsigc++-2.0-dev:amd64 (2.10.0-1) ...
  Setting up libarchive13:amd64 (3.2.1-5) ...
  Setting up qt4-qmake (4:4.8.7+dfsg-11) ...
  Setting up libnss3:amd64 (2:3.26.2-1) ...
  Setting up libqt4-sql:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libicu-dev (57.1-4) ...
  Setting up libnss3-dev:amd64 (2:3.26.2-1) ...
  Setting up libglib2.0-dev (2.50.2-1) ...
  Setting up libxml2-dev:amd64 (2.9.4+dfsg1-2.1) ...
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up libglibmm-2.4-1v5:amd64 (2.50.0-1) ...
  Setting up cmake (3.7.0-1) ...
  Setting up libqtdbus4:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libxcb1:amd64 (1.12-1) ...
  Setting up libarccommon3v5 (5.2.0-1) ...
  Setting up libxcb-present0:amd64 (1.12-1) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.7) ...
  Setting up libxcb-dri2-0:amd64 (1.12-1) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxcb-dri3-0:amd64 (1.12-1) ...
  Setting up libxcb-glx0:amd64 (1.12-1) ...
  Setting up libglibmm-2.4-dev:amd64 (2.50.0-1) ...
  Setting up libqt4-script:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up qdbus (4:4.8.7+dfsg-11) ...
  Setting up libxcb-sync1:amd64 (1.12-1) ...
  Setting up libx11-xcb1:amd64 (2:1.6.3-1) ...
  Setting up libxt6:amd64 (1:1.1.5-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libqt4-dbus:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libqt4-network:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libaudio2:amd64 (1.9.4-5) ...
  Setting up fontconfig (2.11.0-6.7) ...
  Regenerating fonts cache... done.
  Setting up nordugrid-arc-dev (5.2.0-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxfixes3:amd64 (1:5.0.2-1) ...
  Setting up libqt4-xmlpatterns:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libxxf86vm1:amd64 (1:1.1.4-1) ...
  Setting up libqtgui4:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libxdamage1:amd64 (1:1.1.4-2+b1) ...
  Setting up libqt4-designer:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libqt4-help:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libgl1-mesa-glx:amd64 (12.0.4-2) ...
  Setting up libqt4-svg:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libqt4-scripttools:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libqt4-opengl:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libqt4-declarative:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libqt4-qt3support:amd64 (4:4.8.7+dfsg-11) ...
  Setting up libqt4-dev-bin (4:4.8.7+dfsg-11) ...
  Setting up libqt4-dev (4:4.8.7+dfsg-11) ...
  Setting up libqtwebkit4:amd64 (2.3.4.dfsg-9) ...
  Setting up libqtwebkit-dev (2.3.4.dfsg-9) ...
  Setting up arc-gui-clients-build-deps (0.4.6-3) ...
  Processing triggers for libc-bin (2.24-5) ...
  Processing triggers for systemd (232-3) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=f0c32f8af0f7
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20161114094506.svl4gNwFAa.db.arc-gui-clients/arc-gui-clients-0.4.6
  OLDPWD=/home/lamby/temp/cdt.20161114094506.svl4gNwFAa.db.arc-gui-clients
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building arc-gui-clients 0.4.6-3 on amd64  
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package arc-gui-clients
  dpkg-buildpackage: info: source versi

Bug#843145: files with the same name installed in / and /usr -- NMUed

[Martin Pitt]

Hello again,

Martin Pitt [2016-11-09 10:24 +0100]:
> I pushed the fix now:
> 
>   
> https://anonscm.debian.org/cgit/collab-maint/json-c.git/commit/?id=bf85685a69
> 
> (without changelog as you apparently do that on release time).
> 
> > (I'd also fix the broken Vcs-Browse: field while I'm at it).
> 
> Done as well:
> 
>   
> https://anonscm.debian.org/cgit/collab-maint/json-c.git/commit/?id=2873190fdf

I uncommitted these, as even that branch is out of date: it has
0.12-3, but testing/unstable have 0.12.1-1.

> I uploaded this as an NMU to DELAYED/5, with the attached "release"
> commit. I will push this to git if and when this lands.

As there is no git branch that corresponds to reality, I attach the
NMU debdiff.

Thanks,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
diff -Nru json-c-0.12.1/debian/changelog json-c-0.12.1/debian/changelog
--- json-c-0.12.1/debian/changelog  2016-09-02 10:28:57.0 +0200
+++ json-c-0.12.1/debian/changelog  2016-11-14 11:33:17.0 +0100
@@ -1,3 +1,12 @@
+json-c (0.12.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Fix Vcs-Browser URL
+  * debian/libjson-c-dev.links: Fix library symlinks to not collide between
+/lib/ and /usr/lib/ (Closes: #843145, LP: #1629552)
+
+ -- Martin Pitt   Mon, 14 Nov 2016 11:33:17 +0100
+
 json-c (0.12.1-1) unstable; urgency=medium
 
   * Imported Upstream version 0.12.1
diff -Nru json-c-0.12.1/debian/control json-c-0.12.1/debian/control
--- json-c-0.12.1/debian/control2016-09-02 10:28:57.0 +0200
+++ json-c-0.12.1/debian/control2016-11-14 11:33:10.0 +0100
@@ -10,7 +10,7 @@
 Section: libs
 Homepage: https://github.com/json-c/json-c/wiki
 Vcs-Git: git://anonscm.debian.org/git/collab-maint/json-c
-Vcs-Browser: http://anonscm.debian.org/?p=collab-maint/json-c.git;a=summary
+Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/json-c.git
 
 Package: libjson-c3
 Architecture: any
diff -Nru json-c-0.12.1/debian/libjson-c-dev.links 
json-c-0.12.1/debian/libjson-c-dev.links
--- json-c-0.12.1/debian/libjson-c-dev.links2016-09-02 10:28:57.0 
+0200
+++ json-c-0.12.1/debian/libjson-c-dev.links2016-11-14 11:33:10.0 
+0100
@@ -1,3 +1,2 @@
 #!/usr/bin/dh-exec
-/lib/${DEB_HOST_MULTIARCH}/libjson-c.so.3 
/usr/lib/${DEB_HOST_MULTIARCH}/libjson-c.so.3
-/usr/lib/${DEB_HOST_MULTIARCH}/libjson-c.so.3 
/usr/lib/${DEB_HOST_MULTIARCH}/libjson-c.so
+/lib/${DEB_HOST_MULTIARCH}/libjson-c.so.3 
/usr/lib/${DEB_HOST_MULTIARCH}/libjson-c.so


signature.asc
Description: PGP signature

Bug#812303: marked as done (synergy: FTBFS with GCC 6: test suite segfaults)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 10:50:13 +
with message-id 
and subject line Bug#812303: fixed in synergy 1.4.16-1.1
has caused the Debian Bug report #812303,
regarding synergy: FTBFS with GCC 6: test suite segfaults
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.)


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

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.

Unfortunately, it's not clear from the log why the build failed.
It's possible there's a bug in this package or in GCC.  It's also
possible I reported a non-issue, although I tried to avoid that.
I apologize in advance if this is the case.

If you have some time to look into this issue, that'd be great.  If
not, I can re-test the package with GCC 6 in a few weeks time.

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
...
> [ RUN  ] CKeyStateTests.sendKeyEvent_halfDuplexAndRepeat_addEventNotCalled
> [   OK ] 
> CKeyStateTests.sendKeyEvent_halfDuplexAndRepeat_addEventNotCalled (0 ms)
> [ RUN  ] CKeyStateTests.sendKeyEvent_halfDuplex_addEventCalledTwice
> debian/rules:113: recipe for target 'test' failed
> make: *** [test] Segmentation fault
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2
> 
> Build finished at 20160118-2056
> 

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: synergy
Source-Version: 1.4.16-1.1

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

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

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

Debian distribution maintenance software
pp.
Joshua Honeycutt  (supplier of updated synergy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Oct 2016 23:36:22 -0500
Source: synergy
Binary: synergy
Architecture: source amd64
Version: 1.4.16-1.1
Distribution: unstable
Urgency: medium
Maintainer: Jeff Licquia 
Changed-By: Joshua Honeycutt 
Description:
 synergy- Share mouse, keyboard and clipboard over the network
Closes: 812303
Changes:
 synergy (1.4.16-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Added debian_google-test.patch to build against Debian's
 google-mock and libgtest-dev packages. Closes: #812303
Checksums-Sha1:
 9d59d5232dcc590bfc7644ab042ad076cfda32a2 1964 synergy_1.4.16-1.1.dsc
 b625cf76fe028138c9eee446d4560cfd218fe574 16976 synergy_1.4.16-1.1.debian.tar.xz
 5745b7cb3f4192eccd8d1a7e985e9baafc3949fd 9611234 
synergy-dbgsym_1.4.16-1.1_amd64.deb
 08c00764b4b490180c522b48e65f6c01031cbf51 10080 
synergy_1.4.16-1.1_20161109T095450z-56f15e79.buildinfo
 d3e2e2981777ca422e4b1eafd3e67ba95d4243e9 730320 synergy_1.4.16-1.1_amd64.deb
Checksums-Sha256:
 e83eaabf5a4d49a85e2fa431354b06225174503f8ac472b59dd83724dcb0137c 1964 
synergy_1.4.16-1.1.dsc
 12c539e46ac8328e276d9c9e006c0ad14fe5950467072565a1593664dc159d0d 16976 
synergy_1.4.16-1.1.debian.tar.xz
 47069a8562447a74cada475ab93a2ef04157913e096efc8b39b2fbe1dd54b348 9611234 
synergy-dbgsym_1.4.16-1.1_amd64.deb
 9ef0efdfc9e9e273366dc8f86aecbbf03d3517c6be7c68f4574da66c86adc9c9 10080 
synergy_1.4.16-1.1_20161109T095450z-56f15e79.buildinfo
 7cdaae6a57702e400caab9de2c41e5b1e9353606e6f58e268d20a7803956af74 730320 
synergy_1.4.16-1.1_amd64.deb
Files:
 b82450041398f6f9264d63bec6acb6f0 1964 x11 optional synergy_1.4.16-1.1.dsc
 e9356bc3f989afe178838023d181e335 16976 x11 optional 
synergy_1.4.16-1.1.debian.tar.xz
 75fc844da9de45660dfa759083ca96ec 9611234 debug extra 
synergy-dbgsym_1.4.16-1.1_amd64.deb
 56f15e79f

Bug#841592: [debian-mysql] Bug#841592: Bug#841592: mysql-5.7: FTBFS: Tests failures

[Lars Tangvald]

- lu...@debian.org wrote:

> On 13/11/16 at 22:59 -0800, Lars Tangvald wrote:
> > 
> > - lu...@debian.org wrote:
> > 
> > > > Do you have the logs from the last run?
> > > > While we could disable the test that's failing, it would be
> > > counterproductive since we can't reproduce the issue in any of
> our
> > > normal build environments.
> > > 
> > > This is the log without your patch applied
> > > 
> > > Lucas
> > 
> > Or did you mean with?
> 
> no, the log was without the patch. I did not keep the log with the
> patch
> 
> > It's failing in a different way. I think the way it's failing here
> is to do with insufficient system resources.
> 
> unlikely, that node has 64 cores and 256 GB of RAM.
>  
> Lucas

I got it backwards, then :)
A high number of cores might cause this if fs.aio-max-nr is set low (cat 
/proc/sys/fs/aio-max-nr | aio-nr), or rather, too low for the the 
parallelization used by the test run.
https://www.kernel.org/doc/Documentation/sysctl/fs.txt

--
Lars

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

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 10:49:14 +
with message-id 
and subject line Bug#843145: fixed in json-c 0.12.1-1.1
has caused the Debian Bug report #843145,
regarding files with the same name installed in / and /usr
to be marked as done.

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

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


-- 
843145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjson-c-dev
Severity: important
Version: 0.12.1-1
User: m...@linux.it
Usertags: usrmerge

Hello,

libjson-c-3 installs

  /lib/x86_64-linux-gnu/libjson-c.so.3 -> libjson-c.so.3.0.1

while libjson-c-dev installs the same file name into /usr:

  /usr/lib/x86_64-linux-gnu/libjson-c.so -> libjson-c.so.3
  /usr/lib/x86_64-linux-gnu/libjson-c.so.3 -> 
/lib/x86_64-linux-gnu/libjson-c.so.3

this is redundant. It would be enough for the -dev to ship

  /usr/lib/x86_64-linux-gnu/libjson-c.so -> /lib/x86_64-linux-gnu/libjson-c.so.3

Merged /usr is the default since debootstrap 1.0.85, so this is
possibly even RC.

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

Thanks for considering,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
--- End Message ---
--- Begin Message ---
Source: json-c
Source-Version: 0.12.1-1.1

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

Debian distribution maintenance software
pp.
Martin Pitt  (supplier of updated json-c 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, 14 Nov 2016 11:33:17 +0100
Source: json-c
Binary: libjson-c3 libjson-c-dev libjson-c-doc
Architecture: source amd64 all
Version: 0.12.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: fabien boucher 
Changed-By: Martin Pitt 
Description:
 libjson-c-dev - JSON manipulation library - development files
 libjson-c-doc - JSON manipulation library - documentation files
 libjson-c3 - JSON manipulation library - shared library
Closes: 843145
Changes:
 json-c (0.12.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Fix Vcs-Browser URL
   * debian/libjson-c-dev.links: Fix library symlinks to not collide between
 /lib/ and /usr/lib/ (Closes: #843145, LP: #1629552)
Checksums-Sha1:
 da2be58015a8c6b133de0df427cbb386a1b350e4 2017 json-c_0.12.1-1.1.dsc
 59303b064dd188a92012d58b0d977d1acdcbcae5 5644 json-c_0.12.1-1.1.debian.tar.xz
 f802c848d10b1d7a931f7031aba8fd411580e064 5187 
json-c_0.12.1-1.1_20161114T103520z-510c7132.buildinfo
 70256495c7745ea18a7a97acfc344276f7bf4728 37502 
libjson-c-dev_0.12.1-1.1_amd64.deb
 a891ccf0749b05e114acb5e8a02fe115e5d693c7 61632 libjson-c-doc_0.12.1-1.1_all.deb
 faf47854f04751b8d2948c9dea85d1602ae08da5 38716 
libjson-c3-dbgsym_0.12.1-1.1_amd64.deb
 0372b36cb1507cdc9c5e8cdec0d611018c1ba5fa 25848 libjson-c3_0.12.1-1.1_amd64.deb
Checksums-Sha256:
 a5021f5337edc1b3be37c67d367fcb926ba2957701092e93c2ed6253009f3ba3 2017 
json-c_0.12.1-1.1.dsc
 14f083c10a9f733f9bc27ead2c9e2dc1057e68a1ae223b21548cb955eeeab3cc 5644 
json-c_0.12.1-1.1.debian.tar.xz
 8aa081a91e06d248a6e0e9593bf808d00416723b1b5ee3cae74d3e7b6aa8aeed 5187 
json-c_0.12.1-1.1_20161114T103520z-510c7132.buildinfo
 e972101a41f1368045f341d891d9b34906f41b3a47cefbb9a2af6463cc3a0b80 37502 
libjson-c-dev_0.12.1-1.1_amd64.deb
 4f3bb42551415c70e770d6645472f656fc24a48bd7b2735298956fc8cbe976b5 61632 
libjson-c-doc_0.12.1-1.1_all.deb
 9e861a26cbfeeb26ebdaf6bb79fae6601b08f1be4d2ae9edd54b3970d85b9024 38716 
libjson-c3-dbgsym_0.12.1-1.1_amd64.deb
 8aeee80907a69484c5f6327b2711fb0b4c30cb114e074b31188e564879483cb2 25848 
libjson-c3_0.12.1-1.1_amd64.deb
Files:
 ea788d8723edaeae7975818cd068cc5b 2017 libs extra json-c_0.12.1-1.1.dsc
 62d69868b418e7bddcf12ae53757d5e0 5644 libs extra 
json-c_0.12.1-1.1.debian.tar.xz
 510c71326280ac57ef62e55b36a2b753 5187 libs extra 
json-c_0.12.1-1.1_20161114T103520z-510c7132.buildinfo
 805bda62e27c5f696

Bug#842048: marked as done (plaso: FTBFS: dpkg-gencontrol: error: error occurred while parsing Depends field: , , python:any, python:any (<< 2.8), python:any (>= 2.7.5-5~), python:any (>= 2.7~),)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 11:05:56 +
with message-id 
and subject line Bug#842048: fixed in plaso 1.5.1+dfsg-2
has caused the Debian Bug report #842048,
regarding plaso: FTBFS: dpkg-gencontrol: error: error occurred while parsing 
Depends field: , , python:any, python:any (<< 2.8), python:any (>= 2.7.5-5~), 
python:any (>= 2.7~),
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.)


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

Dear Maintainer,

plaso fails to build from source in unstable/amd64:

  […]

 dh_fixperms
 dh_installdeb
 dh_gencontrol
  dpkg-gencontrol: warning: Depends field of package plaso: unknown 
substitution variable ${shlibs:Depends}
  dpkg-gencontrol: warning: can't parse dependency (>= 20160418)
  dpkg-gencontrol: error: error occurred while parsing Depends field: , , 
python:any, python:any (<< 2.8), python:any (>= 2.7.5-5~), python:any (>= 2.7~),
  ipython (>= 1.2.1),
  python-binplist (>= 0.1.4),
  python-bittorrent,
  python-construct (>= 2.5.2),
  python-crypto (>= 2.6.0),
  python-dateutil (>= 1.5),
  python-dfdatetime (>= 20160319),
  python-dfvfs (>= 20160803),
  python-dfwinreg (>= 20160320),
  python-dpkt (>= 1.8),
  python-hachoir-core (>= 1.3.3),
  python-hachoir-metadata (>= 1.3.3),
  python-hachoir-parser (>= 1.3.4),
  python-libbde (>= 20140531),
  python-libesedb (>= 20150409),
  python-libevt (>= 20120410),
  python-libevtx (>= 20141112),
  python-libewf (>= 20131210),
  python-libfsntfs (>= 20151130),
  python-libfvde (>= 20160719),
  python-libfwnt, (>= 20160418),
  python-libfwsi (>= 20150606),
  python-liblnk (>= 20150830),
  python-libmsiecf (>= 20150314),
  python-libolecf (>= 20151223),
  python-libqcow (>= 20131204),
  python-libregf (>= 20150315),
  python-libscca (>= 20151226),
  python-libsigscan (>= 20150627),
  python-libsmdev (>= 20140529),
  python-libsmraw (>= 20140612),
  python-libvhdi (>= 20131210),
  python-libvmdk (>= 20140421),
  python-libvshadow (>= 20160109),
  python-libvslvm (>= 20160109),
  python-pefile,
  python-protobuf,
  python-psutil (>= 1.2.1),
  python-pyparsing (>= 2.0.3),
  python-requests (>= 2.2.1),
  python-six (>= 1.1.0),
  python-tsk (>= 20160721),
  python-tz,
  python-xlsxwriter (>= 0.9.3),
  python-yaml (>= 3.10),
  python-yara (>= 3.4.0),
  python-zmq (>= 2.1.11),
  dh_gencontrol: dpkg-gencontrol -pplaso -ldebian/changelog 
-Tdebian/plaso.substvars -Pdebian/plaso returned exit code 255
  debian/rules:12: recipe for target 'binary' failed
  make: *** [binary] Error 2

  […]

The full build log is attached.


Regards,

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


plaso.1.5.1+dfsg-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: plaso
Source-Version: 1.5.1+dfsg-2

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated plaso 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, 14 Nov 2016 11:39:56 +0100
Source: plaso
Binary: plaso
Architecture: source
Version: 1.5.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Forensics 
Changed-By: Hilko Bengen 
Description:
 plaso  - super timeline all the things
Closes: 842048
Changes:
 plaso (1.5.1+dfsg-2) unstable; urgency=medium
 .
   * Fix debian/control syntax error (Closes: #842048)
Checksums-Sha1:
 85b85836283eda5db4ee6d62939b75b42887d417 1937 plaso_1.5.1+dfsg-2.dsc
 876f1f639b337d3ce6a56d8911ff49d0f3c35028 3260 plaso_1.5.1+dfsg-2.debian.tar.xz
Checksums-Sha256:
 bbb9e47e5e68fd85a2e82f0b11005c765b4cd018038f38de5e0725bc7e0d0d8b 1937 
plaso_1.5.1+dfsg-2.dsc
 645c30dc62e046

Bug#830433: marked as done (gopacket: FTBFS: dh_auto_test: go test -v github.com/google/gopacket github.com/google/gopacket/afpacket github.com/google/gopacket/bytediff github.com/google/gopacket/dump

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 11:04:41 +
with message-id 
and subject line Bug#830433: fixed in gopacket 1.1.12-1
has caused the Debian Bug report #830433,
regarding gopacket: FTBFS: dh_auto_test: go test -v github.com/google/gopacket 
github.com/google/gopacket/afpacket github.com/google/gopacket/bytediff 
github.com/google/gopacket/dumpcommand github.com/google/gopacket/ip4defrag 
github.com/google/gopacket/layers github.com/google/gopacket/macs 
github.com/google/gopacket/pcap github.com/google/gopacket/pcapgo 
github.com/google/gopacket/pfring github.com/google/gopacket/routing 
github.com/google/gopacket/tcpassembly 
github.com/google/gopacket/tcpassembly/tcpreader returned exit code 1
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.)


-- 
830433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gopacket
Version: 1.1.11-2
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):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> dh_auto_configure
>   mkdir -p obj-x86_64-linux-gnu
>   Copy decode.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/decode.go
>   Copy packet.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/packet.go
>   Copy writer_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/writer_test.go
>   Copy writer.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/writer.go
>   Copy layerclass.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/layerclass.go
>   Copy doc.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/doc.go
>   Copy layertype.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/layertype.go
>   Copy parser.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/parser.go
>   Copy base.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/base.go
>   Copy flows.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/flows.go
>   Copy benchmark_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/benchmark_test.go
>   Copy afpacket/header.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/afpacket/header.go
>   Copy afpacket/afpacket.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/afpacket/afpacket.go
>   Copy afpacket/options.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/afpacket/options.go
>   Copy afpacket/afpacket_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/afpacket/afpacket_test.go
>   Copy examples/pfdump/main.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/examples/pfdump/main.go
>   Copy examples/httpassembly/main.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/examples/httpassembly/main.go
>   Copy examples/util/util.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/examples/util/util.go
>   Copy examples/synscan/main.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/examples/synscan/main.go
>   Copy examples/pcapdump/main.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/examples/pcapdump/main.go
>   Copy examples/bytediff/main.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/examples/bytediff/main.go
>   Copy examples/bidirectional/main.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/examples/bidirectional/main.go
>   Copy examples/statsassembly/main.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/examples/statsassembly/main.go
>   Copy examples/arpscan/arpscan.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/examples/arpscan/arpscan.go
>   Copy tcpassembly/assembly_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/tcpassembly/assembly_test.go
>   Copy tcpassembly/assembly.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/tcpassembly/assembly.go
>   Copy tcpassembly/tcpreader/reader.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/tcpassembly/tcpreader/reader.go
>   Copy tcpassembly/tcpreader/reader_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/tcpassembly/tcpreader/reader_test.go
>   Copy layers/usb_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/google/gopacket/layers/usb_test.go
>   Copy layers/radiotap.go -> 
> obj-x86_64-linux-gnu/src/

Processed: Re: Debian Installer Stretch Alpha 8 release

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #843073 [dpkg-dev] dpkg-shlibdeps: broken on i386 with merged /usr
Added tag(s) patch.
> severity -1 serious
Bug #843073 [dpkg-dev] dpkg-shlibdeps: broken on i386 with merged /usr
Severity set to 'serious' from 'wishlist'

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

Processed: affects 842142

[Debian Bug Tracking System]

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

> affects 842142 - src:afl
Bug #842142 [src:llvm-toolchain-3.8] llvm-toolchain-3.8: armhf: defaults to 
emitting NEON instructions
Removed indication that 842142 affects src:afl
> affects 842143 + src:afl
Bug #842143 [src:llvm-toolchain-3.9] llvm-toolchain-3.9: armhf: defaults to 
emitting NEON instructions
Added indication that 842143 affects src:afl
> thanks
Stopping processing here.

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

Bug#842082: torch-core-free: uninstallable on architectures without lua-torch-image

[lumin]

Hi,

Thank you for pointing this out, I noticed it.

Actually I plan to add all of its runtime dependencies
to its B-D list and add autopkgtest support for this
package. In this way the installation failure issue
on any architecture will be eliminated.

Will fix it in 1~exp2 .

Bug#844221: marked as done (debootstrap: Please revert merged-/usr by default as it breaks builds)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 12:29:29 +0100
with message-id <20161114112929.7eyuh5mzkxmto...@home.ouaza.com>
and subject line Re: Bug#844221: Debian Installer Stretch Alpha 8 release
has caused the Debian Bug report #844221,
regarding debootstrap: Please revert merged-/usr by default as it breaks builds
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.)


-- 
844221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.18.10
Severity: normal

Dear Maintainer,

debootstrap 1.0.85 began deploying with --merged-usr by default in
response to #839046.  On i386, this causes dpkg-shlibdeps to fail on
(some?) shared libraries.

An example error:
dpkg-shlibdeps: error: no dependency information found for 
/usr/lib/ld-linux.so.2 (used by 
debian/libevas1/usr/lib/i386-linux-gnu/libevas.so.1.18.2)
Hint: check if the library actually comes from a package.

In this case:
# ls -l /usr/lib/ld-linux.so.2
lrwxrwxrwx 1 root root 25 Oct 18 21:10 /usr/lib/ld-linux.so.2 -> 
i386-linux-gnu/ld-2.24.so

To workaround with a pbuilder chroot, when creating, supply:
  --debootstrapopts --no-merged-usr.

I'm not sure if this is a debootstrap or dpkg-dev issue.  Apologies in
advance if I'm incorrect.  The same underlying problem was reported
against usrmerge in #810499.  For some reason, debootstrap does not
create this symlink on amd64.

Ross.

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 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)

Versions of packages dpkg-dev depends on:
ii  base-files9.6
ii  binutils  2.27-9+b1
ii  bzip2 1.0.6-8
ii  libdpkg-perl  1.18.10
ii  make  4.1-9
ii  patch 2.7.5-1
ii  tar   1.29b-1
ii  xz-utils  5.2.2-1.2

Versions of packages dpkg-dev recommends:
ii  build-essential  12.2
ii  fakeroot 1.21-2
ii  gcc [c-compiler] 4:6.1.1-1
ii  gcc-5 [c-compiler]   5.4.1-3
ii  gcc-6 [c-compiler]   6.2.0-9
ii  gnupg2.1.15-4
ii  gnupg2   2.1.15-4
ii  gpgv 2.1.15-4
ii  libalgorithm-merge-perl  0.08-3

Versions of packages dpkg-dev suggests:
ii  debian-keyring  2016.09.04

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,

On Sun, 13 Nov 2016, Sven Joachim wrote:
> I fail to see how this would solve the problem in #843073, unless your
> plan is to move away all files from /lib and its subdirectories which
> would seem quite problematic to achieve, especially given the short time
> until the full freeze.

Now that there is a patch for #843073, I believe that we can close this
bug. There's no need to revert anything, we can just upload a fixed dpkg.

I bumped the severity of #843073 back to serious so that we track it
properly.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/--- End Message ---

Bug#828263: cfengine3: FTBFS with openssl 1.1.0

[Petter Reinholdtsen]

Hi.  Any news on fixing cfengine3 in time for the Stretch release?  Is
the problem reported upstream?  Fixed in newer versions?

The problem caused cfengine3 to be removed from testing three days ago.

-- 
Happy hacking
Petter Reinholdtsen

Bug#841592: [debian-mysql] Bug#841592: Bug#841592: mysql-5.7: FTBFS: Tests failures

[Lucas Nussbaum]

On 14/11/16 at 02:47 -0800, Lars Tangvald wrote:
> 
> - lu...@debian.org wrote:
> 
> > On 13/11/16 at 22:59 -0800, Lars Tangvald wrote:
> > > 
> > > - lu...@debian.org wrote:
> > > 
> > > > > Do you have the logs from the last run?
> > > > > While we could disable the test that's failing, it would be
> > > > counterproductive since we can't reproduce the issue in any of
> > our
> > > > normal build environments.
> > > > 
> > > > This is the log without your patch applied
> > > > 
> > > > Lucas
> > > 
> > > Or did you mean with?
> > 
> > no, the log was without the patch. I did not keep the log with the
> > patch
> > 
> > > It's failing in a different way. I think the way it's failing here
> > is to do with insufficient system resources.
> > 
> > unlikely, that node has 64 cores and 256 GB of RAM.
> >  
> > Lucas
> 
> I got it backwards, then :)
> A high number of cores might cause this if fs.aio-max-nr is set low (cat 
> /proc/sys/fs/aio-max-nr | aio-nr), or rather, too low for the the 
> parallelization used by the test run.
> https://www.kernel.org/doc/Documentation/sysctl/fs.txt

Well, it was also failing on a more standard machine. The test suite
should be robust to that...

Lucas

Bug#844302: libapache-mod-musicindex: FTBFS: x86_64-linux-gnu-gcc: error: .specs: No such file or directory

[Thibaut VARENE]

> Le 14 nov. 2016 à 11:37, Chris Lamb  a écrit :
> 
> Source: libapache-mod-musicindex
> Version: 1.4.1-1
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> libapache-mod-musicindex fails to build from source in unstable/amd64:
> 
>  […]

> Making all in src
> make[3]: Entering directory 
> '/home/lamby/temp/cdt.20161114094607.osX7pL8bcm.db.libapache-mod-musicindex/libapache-mod-musicindex-1.4.1/build/src'
> /bin/bash ../libtool  --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
> -DHAVE_CONFIG_H -I. -I../../src -I.. -I/usr/include/apache2 
> -I/usr/include/apr-1.0 -I/usr/include/mysql -DLINUX -D_REENTRANT 
> -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic 
> -fstrict-aliasing -pipe -g -O2 -fdebug-prefix-map=/build/apache2-2.4.23=. 
> -fstack-protector-strong -Wformat -Werror=format-security   -pthread 
> -I/usr/include  -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -g -O2 
> -fdebug-prefix-map=/home/lamby/temp/cdt.20161114094607.osX7pL8bcm.db.libapache-mod-musicindex/libapache-mod-musicindex-1.4.1=.
>  -fstack-protector-strong -Wformat -Werror=format-security -MT 
> mod_musicindex_la-mod_musicindex.lo -MD -MP -MF 
> .deps/mod_musicindex_la-mod_musicindex.Tpo -c -o 
> mod_musicindex_la-mod_musicindex.lo `test -f 'mod_musicindex.c' || echo 
> '../../src/'`mod_musicindex.c
>  libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../src -I.. 
> -I/usr/include/apache2 -I/usr/include/apr-1.0 -I/usr/include/mysql -DLINUX 
> -D_REENTRANT -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic 
> -fstrict-aliasing -pipe -g -O2 -fdebug-prefix-map=/build/apache2-2.4.23=. 
> -fstack-protector-strong -Wformat -Werror=format-security -pthread 
> -I/usr/include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -g -O2 
> -fdebug-prefix-map=/home/lamby/temp/cdt.20161114094607.osX7pL8bcm.db.libapache-mod-musicindex/libapache-mod-musicindex-1.4.1=.
>  -fstack-protector-strong -Wformat -Werror=format-security -MT 
> mod_musicindex_la-mod_musicindex.lo -MD -MP -MF 
> .deps/mod_musicindex_la-mod_musicindex.Tpo -c ../../src/mod_musicindex.c  
> -fPIC -DPIC -o .libs/mod_musicindex_la-mod_musicindex.o
>  x86_64-linux-gnu-gcc: error: .specs: No such file or directory

I don’t see how this is a bug in my package. I don’t know where that spurious « 
.specs » on the command line comes from. Looks like a build system cockup to me.

Besides, this package is orphaned.

T.

Bug#841592: [debian-mysql] Bug#841592: Bug#841592: Bug#841592: mysql-5.7: FTBFS: Tests failures

[Robie Basak]

On Mon, Nov 14, 2016 at 12:31:43PM +0100, Lucas Nussbaum wrote:
> On 14/11/16 at 02:47 -0800, Lars Tangvald wrote:
> > I got it backwards, then :)
> > A high number of cores might cause this if fs.aio-max-nr is set low (cat 
> > /proc/sys/fs/aio-max-nr | aio-nr), or rather, too low for the the 
> > parallelization used by the test run.
> > https://www.kernel.org/doc/Documentation/sysctl/fs.txt
> 
> Well, it was also failing on a more standard machine. The test suite
> should be robust to that...

Should we perhaps check the sysctl knobs in debian/rules, and warn and
cap the parallelism before running the test suite if they aren't high
enough?

Robie

Bug#843073: Debian Installer Stretch Alpha 8 release

[Michael Biebl]

Am 14.11.2016 um 12:22 schrieb Raphael Hertzog:

> Please find two patches attached.
> 
> I checked that the command below was failing with the current dpkg-dev
> and it did no longer fail with the updated one.
> 
> $ sbuild -d sid --add-depends=usrmerge --chroot-setup-commands="sed -i 
> 's#^/usr##;t;s#^/lib#/usr&#' /etc/ld.so.conf.d/x86_64-linux-gnu.conf" dash
> 
> I believe my patch to be correct and clean.
> 
>> Err, well exactly because usemerge is a major hack, and I'm actually
>> surprised we are deploying systems by default with that. As an
> 
> It's easier to push work upon others... to be honest the code (that I
> wrote) in dpkg-dev that tries to identifiy the canonical version of the
> library is also somewhat hackish.
> 
> I think the updated code that I submitted works better in all weird
> corner cases that we could think of.
> 
> I'm happy to assist you shall any regression be found.

That's great, thanks a lot Raphael!

I debugged this issue myself this evening and came up with a patch on my
own. Your's is nicer und more generic though. So I'm happy to scrap mine.

Just for the record: I can confirm it fixes the problem in dpkg-shlibdeps.

I've CCed the debootrap bug, so the debian-boot people are aware that a
fix for dpkg is available and a revert in debootstrap is not necessary.

Guillem, it would be great if you can upload a fixed dpkg soon.
Julien Cristau told me, that he didn't want to see this issue unresolved
for too long.

Thanks everyone involved in getting this resolved.

Regards,
Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Bug#843169 marked as pending

[Debian Bug Tracking System]

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

> tag 843169 pending
Bug #843169 [xbmc-eventclients-j2me] xbmc-eventclients-j2me: uninstallable in 
unstable
Ignoring request to alter tags of bug #843169 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#844315: tzdata version breaks dist-upgrade leaving version from oldstable security installed

[Marcel Meckel]

Package: tzdata
Version: 2016i-0+deb7u1
Severity: critical

Upgrading a fully updated wheezy system (incl. security repo) to
jessie (incl. security repo) results in tzdata not being updated
because the version in wheezy-security is newer than in jessie.

Package tzdata on amd64

  wheezy:  2016d-0+deb7u1
  wheezy-security: 2016i-0+deb7u1

  jessie:  2016f-0+deb8u1
  jessie-updates:  2016i-0+deb8u1
  jessie-proposed-updates: 2016i-0+deb8u1

Using only the main repo + security repo results in tzdata not being
updates since wheezy-securities '2016i-0+deb7u1' is higher than
jessies '2016f-0+deb8u1'.

Comment from IRC:

 That's indeed unfortunate. You can work around the
problem by adding jessie-updates, though.

 I think it's because wheezy didn't have a wheezy-updates,
so all updates must go through wheezy-security, whereas in jessie all
non-critical updates go through jessie-updates, and get wrapped up in
point releases every few months.

 It's still a bug though, I'd report it on the tzdata
package. Might warrant a RC severity, since it breaks automatic upgrades
and is easy to fix.

Bug#843169: marked as pending

[Balint Reczey]

tag 843169 pending
thanks

Hello,

Bug #843169 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/kodi.git;a=commitdiff;h=998f833

---
commit 998f833ed5cdd00967c5aff738a616d2f9302526
Author: Balint Reczey 
Date:   Sun Nov 13 22:59:58 2016 +0100

Update changelog

diff --git a/debian/changelog b/debian/changelog
index d86cd83..d91272c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,21 @@
-kodi (17.0~beta5+dfsg1-2) UNRELEASED; urgency=medium
+kodi (17.0~beta5+dfsg1-2) unstable; urgency=medium
 
-  *
+  [ Balint Reczey ]
+  * Stop providing xbmc-eventclients-j2me.
+This was a transitional package originally, but Kodi stopped shipping
+J2ME client. (Closes: #843169)
+  * Transition to depending on fonts-anonymous-pro.
+Also accept ttf-anonymous-pro instead to support older releases
+  * Generate additional original source tarball names from current version
+  * Use more absolute paths in d/rules
+
+  [ Tobias Grimm ]
+  * Updated tarball versions in `debian/rules extract-components`
+  * Provide virtual packages for addon APIs and install a debhelper addon
+to enable KODI addon packages to depend on these virtual packages.
+  * Standards-Version: 3.9.8
 
- -- Balint Reczey   Fri, 04 Nov 2016 17:05:37 +0100
+ -- Balint Reczey   Mon, 14 Nov 2016 11:32:17 +0100
 
 kodi (17.0~beta5+dfsg1-1) unstable; urgency=medium
 

Bug#843457: mysql-workbench: Dependency gdal-abi-2-1-1 no longer in repo

[Dmitry Smirnov]

On Monday, 14 November 2016 9:31:08 AM AEDT Alessio wrote:
> At that point, the only way to go seems
> pinning libgdal until possible.

I've managed to build mysql-connector-c++ and mysql-workbench with mariadb 
libraries. M-W was uploaded to unstable earlier today and seems to work. :)


> There is no chance to embed the needed libraries?

I would not be comfortable doing that. Besides upstream do not bundle libgdal 
and having two libraries linked against different MySQL flavors would be too 
much troubles...

-- 
Regards,
 Dmitry Smirnov.

---

For a creative writer possession of the 'truth' is less important than
emotional sincerity.
-- George Orwell


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

Bug#828263: cfengine3: FTBFS with openssl 1.1.0

[Antonio Radici]

On Mon, Nov 14, 2016 at 12:29:04PM +0100, Petter Reinholdtsen wrote:
> Hi.  Any news on fixing cfengine3 in time for the Stretch release?  Is
> the problem reported upstream?  Fixed in newer versions?
> 
> The problem caused cfengine3 to be removed from testing three days ago.

Hi Peter,
the version in experimental builds fine with 1.1.0, I'll upload it to unstable
tonight.

Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Vincent Lefevre]

On 2016-11-14 11:31:38 +0100, Vincent Lefevre wrote:
> dpkg: error processing package nvidia-driver-libs:amd64 (--configure):
>  package nvidia-driver-libs:amd64 367.57-2 cannot be configured because 
> nvidia-driver-libs:i386 is at a different version (367.57-1)

I wonder why such a failure since there are no dependencies between
the amd64 and i386 versions.

And if this combination doesn't work, there should be a "Breaks:"
against the older versions.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#843169: marked as done (xbmc-eventclients-j2me: uninstallable in unstable)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 12:04:35 +
with message-id 
and subject line Bug#843169: fixed in kodi 17.0~beta5+dfsg1-2
has caused the Debian Bug report #843169,
regarding xbmc-eventclients-j2me: uninstallable in unstable
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.)


-- 
843169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xbmc-eventclients-j2me
Version: 17.0~beta5+dfsg1-1
Severity: serious
Tags: sid stretch

Hi,

The xbmc-eventclients-j2me cannot be installed in unstable.
The kodi-eventclients-j2me package does not exist.

$ sudo apt-get install -o Debug::pkgProblemResolver=true xbmc-eventclients-j2me
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) xbmc-eventclients-j2me:amd64 < none -> 2:17.0~beta5+dfsg1-1 
@un puN Ib >
Broken xbmc-eventclients-j2me:amd64 Depends on kodi-eventclients-j2me:amd64 < 
none @un H >
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xbmc-eventclients-j2me : Depends: kodi-eventclients-j2me but it is not 
installable
E: Unable to correct problems, you have held broken packages.

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: kodi
Source-Version: 17.0~beta5+dfsg1-2

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated kodi 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, 14 Nov 2016 11:32:17 +0100
Source: kodi
Binary: kodi kodi-data kodi-bin kodi-eventclients-common kodi-eventclients-dev 
kodi-eventclients-wiiremote kodi-eventclients-ps3 kodi-eventclients-kodi-send 
kodi-addons-dev xbmc xbmc-bin xbmc-eventclients-common xbmc-eventclients-dev 
xbmc-eventclients-wiiremote xbmc-eventclients-ps3 xbmc-eventclients-xbmc-send 
xbmc-addons-dev
Architecture: source
Version: 17.0~beta5+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Balint Reczey 
Description:
 kodi   - Open Source Home Theatre (executable binaries)
 kodi-addons-dev - Open Source Home Theatre (Addons Dev package)
 kodi-bin   - Open Source Home Theatre (architecture-dependent files)
 kodi-data  - Open Source Home Theatre (arch-independent data package)
 kodi-eventclients-common - Open Source Home Theatre (Event Client Common 
package)
 kodi-eventclients-dev - Open Source Home Theatre (Event Client Dev package)
 kodi-eventclients-kodi-send - Open Source Home Theatre (Event Client Kodi-SEND 
package)
 kodi-eventclients-ps3 - Open Source Home Theatre (Event Client PS3 package)
 kodi-eventclients-wiiremote - Open Source Home Theatre (Event Client WII 
Remote support package
 xbmc   - transitional dummy package
 xbmc-addons-dev - transitional dummy package
 xbmc-bin   - transitional dummy package
 xbmc-eventclients-common - transitional dummy package
 xbmc-eventclients-dev - transitional dummy package
 xbmc-eventclients-ps3 - transitional dummy package
 xbmc-eventclients-wiiremote - transitional dummy package
 xbmc-eventclients-xbmc-send - transitional dummy package
Closes: 843169
Changes:
 kodi (17.0~beta5+dfsg1-2) unstable; urgency=medium
 .
   [ Balint Reczey ]
   * Stop providing xbmc-eventclients-j2me.
 This was a transitional package originally, but Kodi stopped shipping
 J2ME client. (Closes: #843169)
   * Transition to depending on fonts-anonymous-pro.
 Also accept ttf-anonymous-pro instead to support older releases
   * Generate additional original source tarball names 

Processed: Re: Bug#844286: grep: Non-deterministic behavior when output redirected to /dev/null

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #844286 [grep] grep: Non-deterministic behavior when output redirected to 
/dev/null
Severity set to 'important' from 'grave'

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

Bug#844286: grep: Non-deterministic behavior when output redirected to /dev/null

[James McCoy]

Control: severity -1 important

On Sun, Nov 13, 2016 at 10:38:37PM -0500, James McCoy wrote:
> On Sun, Nov 13, 2016 at 08:40:02PM -0500, James McCoy wrote:
> > The relevant part of the script is just looking for whether patch
> > numbers are applied or marked NA in neovim's src/nvim/version.c:
> > 
> > is_missing="$(sed -n '/static int included_patches/,/}/p' 
> > "${NVIM_SOURCE_DIR}/src/nvim/version.c" |
> >   grep -x -e "[[:space:]]*//[[:space:]]${patch_number} NA.*" -e 
> > "[[:space:]]*${patch_number}," >/dev/null && echo "false" || echo "true")"
> 
> Playing with this some more, I attempted to change this to use “grep -q …”
> instead of the redirection to /dev/null.  This exhibited the same
> problematic behavior, regardless of which version of grep I was using
> (back to 2.22).
> 
> So, the problematic behavior seems to be related to the "immediate exit"
> behavior of -q (and now also when output is redirected to /dev/null)
> causing the left-hand side of the pipe to get a SIGPIPE.  Since the
> script has “set -o pipefail”, this causes the "sed … | grep …" to be
> considered a failure and echo the wrong value.

Since the problem isn't actuall that grep itself is non-deterministic
but that it's non-deterministic whether grep gets fed all of the input
from the pipe, I'm lowering the severity to important.

I still think this change of behavior should be revisited due its impact
on existing scripts.  It's not clear how broad the effects will be and I
don't see a good way to avoid SIGPIPE with this change since both -q and
redirecting to /dev/null now can cause that.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Processed: Re: Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #844300 [nvidia-driver-libs] nvidia-driver-libs:amd64: upgrade failure due 
to dependency issue
Added tag(s) moreinfo.

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

Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Luca Boccassi]

Control: tags -1 moreinfo

On Mon, 2016-11-14 at 11:31 +0100, Vincent Lefevre wrote:
> Package: nvidia-driver-libs
> Version: 367.57-2
> Severity: grave
> Justification: renders package unusable
> 
> I got the folloing failure when upgrading with aptitude:
> 
> Preconfiguring packages ...
> (Reading database ... 528479 files and directories currently installed.)
> Removing nvidia-driver-libs-i386:i386 (367.57-1) ...
> Removing libopengl0-glvnd-nvidia:i386 (367.57-1) ...
> Removing nvidia-vulkan-icd:i386 (367.57-1) ...
> Removing libglx-nvidia0:i386 (367.57-1) ...
> Removing libglx0-glvnd-nvidia:i386 (367.57-1) ...
> Removing libgles-nvidia2:i386 (367.57-1) ...
> Removing libgles2-glvnd-nvidia:i386 (367.57-1) ...
> Removing libgles-nvidia1:i386 (367.57-1) ...
> Removing libgles1-glvnd-nvidia:i386 (367.57-1) ...
> Removing libgles-nvidia1:amd64 (367.57-1) ...
> Removing libgles-nvidia2:amd64 (367.57-1) ...
> Removing libgles1-glvnd-nvidia:amd64 (367.57-1) ...
> Removing libgles2-glvnd-nvidia:amd64 (367.57-1) ...
> Removing nvidia-vulkan-icd:amd64 (367.57-1) ...
> Removing libglx-nvidia0:amd64 (367.57-1) ...
> Removing libglx0-glvnd-nvidia:amd64 (367.57-1) ...
> Removing libnvidia-cfg1:amd64 (367.57-1) ...
> Removing libnvidia-cfg1:i386 (367.57-1) ...
> Removing libopengl0-glvnd-nvidia:amd64 (367.57-1) ...
> Removing libvulkan1:i386 (1.0.26.0+dfsg1-1) ...
> Removing libvulkan1:amd64 (1.0.26.0+dfsg1-1) ...
> Removing nvidia-vulkan-common (367.57-1) ...
> (Reading database ... 528357 files and directories currently installed.)
> Preparing to unpack .../00-xserver-xorg-video-nvidia_367.57-2_amd64.deb ...
> Unpacking xserver-xorg-video-nvidia (367.57-2) over (367.57-1) ...
> Preparing to unpack .../01-nvidia-kernel-support_367.57-2_amd64.deb ...
> Unpacking nvidia-kernel-support (367.57-2) over (367.57-1) ...
> Preparing to unpack .../02-nvidia-driver-bin_367.57-2_amd64.deb ...
> Unpacking nvidia-driver-bin (367.57-2) over (367.57-1) ...
> Preparing to unpack .../03-libnvidia-ml1_367.57-2_amd64.deb ...
> Unpacking libnvidia-ml1:amd64 (367.57-2) over (367.57-1) ...
> Preparing to unpack .../04-nvidia-driver-libs_367.57-2_amd64.deb ...
> De-configuring nvidia-driver-libs:i386 (367.57-1) ...
> Unpacking nvidia-driver-libs:amd64 (367.57-2) over (367.57-1) ...
> Preparing to unpack .../05-libnvidia-glcore_367.57-2_amd64.deb ...
> De-configuring libnvidia-glcore:i386 (367.57-1) ...
> Unpacking libnvidia-glcore:amd64 (367.57-2) over (367.57-1) ...
> Preparing to unpack .../06-libnvidia-glcore_367.57-2_i386.deb ...
> Unpacking libnvidia-glcore:i386 (367.57-2) over (367.57-1) ...
> Preparing to unpack .../07-libgl1-nvidia-glx_367.57-2_i386.deb ...
> De-configuring libgl1-nvidia-glx:amd64 (367.57-1) ...
> Unpacking libgl1-nvidia-glx:i386 (367.57-2) over (367.57-1) ...
> Preparing to unpack .../08-libgl1-nvidia-glx_367.57-2_amd64.deb ...
> Unpacking libgl1-nvidia-glx:amd64 (367.57-2) over (367.57-1) ...
> Preparing to unpack .../09-libegl1-glvnd-nvidia_367.57-2_amd64.deb ...
> De-configuring libegl1-glvnd-nvidia:i386 (367.57-1) ...
> Unpacking libegl1-glvnd-nvidia:amd64 (367.57-2) over (367.57-1) ...
> Preparing to unpack .../10-libegl-nvidia0_367.57-2_amd64.deb ...
> De-configuring libegl-nvidia0:i386 (367.57-1) ...
> Unpacking libegl-nvidia0:amd64 (367.57-2) over (367.57-1) ...
> Preparing to unpack .../11-nvidia-alternative_367.57-2_amd64.deb ...
> Unpacking nvidia-alternative (367.57-2) over (367.57-1) ...
> Preparing to unpack .../12-nvidia-driver_367.57-2_amd64.deb ...
> Unpacking nvidia-driver (367.57-2) over (367.57-1) ...
> Preparing to unpack .../13-nvidia-vdpau-driver_367.57-2_amd64.deb ...
> Unpacking nvidia-vdpau-driver:amd64 (367.57-2) over (367.57-1) ...
> Preparing to unpack .../14-libgldispatch0-nvidia_367.57-2_amd64.deb ...
> De-configuring libgldispatch0-nvidia:i386 (367.57-1) ...
> Unpacking libgldispatch0-nvidia:amd64 (367.57-2) over (367.57-1) ...
> Preparing to unpack .../15-libnvidia-eglcore_367.57-2_amd64.deb ...
> De-configuring libnvidia-eglcore:i386 (367.57-1) ...
> Unpacking libnvidia-eglcore:amd64 (367.57-2) over (367.57-1) ...
> Preparing to unpack .../16-nvidia-legacy-check_367.57-2_amd64.deb ...
> Unpacking nvidia-legacy-check (367.57-2) over (367.57-1) ...
> Processing triggers for glx-alternative-nvidia (0.7.4) ...
> dpkg: error processing package nvidia-driver-libs:amd64 (--configure):
>  package nvidia-driver-libs:amd64 367.57-2 cannot be configured because 
> nvidia-driver-libs:i386 is at a different version (367.57-1)
> Processing triggers for mime-support (3.60) ...
> dpkg: error processing package libnvidia-eglcore:amd64 (--configure):
>  package libnvidia-eglcore:amd64 367.57-2 cannot be configured because 
> libnvidia-eglcore:i386 is at a different version (367.57-1)
> dpkg: error processing package libgldispatch0-nvidia:amd64 (--configure):
>  package libgldispatch0-nvidia:amd64 367.57-2 cannot be configured because 
> libgldispatch0-nvidia:i386 is at a different version (367.57-1

Bug#844275: mysql_config injects build flags which breaks the build for other packages

[Peter van Dijk]

Hi,

On Mon, 14 Nov 2016 00:39:50 +0100 Michael Biebl  
wrote:
Looking a bit closer, this is a bug in mysql_config, which injects 
bogus

build flags.

# mysql_config --cflags
# mysql_config --cflags
-I/usr/include/mysql 
-fdebug-prefix-map=/build/mysql-5.7-Q0jPG6/mysql-5.7-5.7.16=. .specs 
-fabi-version=2 -fno-omit-frame-pointer -fno-expensive-optimizations


Marking as RC, as this breaks the build for other packages.


Using --include instead may help here.

Peter

Processed (with 5 errors): wontfix

[Debian Bug Tracking System]

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

> severity 844064 normal
Bug #844064 [libgrib-api0] libgrib-api0: shared data files shipped in library 
package
Severity set to 'normal' from 'serious'
> tag 844064 wontfix
Bug #844064 [libgrib-api0] libgrib-api0: shared data files shipped in library 
package
Added tag(s) wontfix.
> done
Unknown command or malformed arguments to command.
> I'm tagging this WONTFIX as it won't happen in actual practice. grib-api
Unknown command or malformed arguments to command.
> is end-of-life, being replaced by eccodes (which is now present in
Unknown command or malformed arguments to command.
> Debian archive, for stretch). Hence there won't be a libgrib-api1 to
Unknown command or malformed arguments to command.
> conflict with libgrib-api0d.
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Processed: fixed 835185 in 1.1.7-3

[Debian Bug Tracking System]

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

> fixed 835185 1.1.7-3
Bug #835185 [libmysqlcppconn7v5] mysql-workbench: Segfault when opening 
connection
Bug #836587 [libmysqlcppconn7v5] mysql-workbench: Mysql-workbench opened ok but 
when I try to connect to db, it crashes with segfault
Bug #836731 [libmysqlcppconn7v5] libmysqlcppconn7v5 version 1.1.4-2 crash 
Libreoffice Base
Marked as fixed in versions mysql-connector-c++/1.1.7-3.
Marked as fixed in versions mysql-connector-c++/1.1.7-3.
Marked as fixed in versions mysql-connector-c++/1.1.7-3.
> thanks
Stopping processing here.

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

Bug#828439: monit: FTBFS with openssl 1.1.0

[Sergey B Kirpichev]

On Sun, Nov 13, 2016 at 06:41:31PM +0100, Kurt Roeckx wrote:
> On Sun, Nov 13, 2016 at 08:26:48PM +0300, Sergey B Kirpichev wrote:
> > On Sun, Nov 13, 2016 at 05:29:10PM +0100, Kurt Roeckx wrote:
> > > That's because the configure script tries to look for a function
> > > that's been turned into a define. For some reason it's only trying
> > > to look for SSL_library_init() on i386.
> > 
> > Could you suggest a more portable solution?
> 
> If you really want configure to detect something, write a real
> program that includes the proper header file. That way
> SSL_library_init() should still work even when we turned it into
> a define.
> 
> An other solution is that you take an other function, like
> SSL_new().

Thank you for help.  I believe, now FTBFS was really fixed (i.e. for
i386 too).

Bug#841592: [debian-mysql] Bug#841592: Bug#841592: mysql-5.7: FTBFS: Tests failures

[Lars Tangvald]

- lu...@debian.org wrote:

> On 14/11/16 at 02:47 -0800, Lars Tangvald wrote:
> > 
> > - lu...@debian.org wrote:
> > 
> > > On 13/11/16 at 22:59 -0800, Lars Tangvald wrote:
> > > > 
> > > > - lu...@debian.org wrote:
> > > > 
> > > > > > Do you have the logs from the last run?
> > > > > > While we could disable the test that's failing, it would be
> > > > > counterproductive since we can't reproduce the issue in any
> of
> > > our
> > > > > normal build environments.
> > > > > 
> > > > > This is the log without your patch applied
> > > > > 
> > > > > Lucas
> > > > 
> > > > Or did you mean with?
> > > 
> > > no, the log was without the patch. I did not keep the log with
> the
> > > patch
> > > 
> > > > It's failing in a different way. I think the way it's failing
> here
> > > is to do with insufficient system resources.
> > > 
> > > unlikely, that node has 64 cores and 256 GB of RAM.
> > >  
> > > Lucas
> > 
> > I got it backwards, then :)
> > A high number of cores might cause this if fs.aio-max-nr is set low
> (cat /proc/sys/fs/aio-max-nr | aio-nr), or rather, too low for the the
> parallelization used by the test run.
> > https://www.kernel.org/doc/Documentation/sysctl/fs.txt
> 
> Well, it was also failing on a more standard machine. The test suite
> should be robust to that...
> 
The original failure you reported was something else; a test failing because of 
an issue with the build environment. The patch I uploaded should make it more 
robust to that.

We could probably set some upper bound on the number of tests run in parallel 
based on the value of this setting, as Robie suggests.

--
Lars

> Lucas

Processed: notfixed 836731 in 1.1.7-3

[Debian Bug Tracking System]

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

> notfixed 836731 1.1.7-3
Bug #836731 [libmysqlcppconn7v5] libmysqlcppconn7v5 version 1.1.4-2 crash 
Libreoffice Base
Bug #835185 [libmysqlcppconn7v5] mysql-workbench: Segfault when opening 
connection
Bug #836587 [libmysqlcppconn7v5] mysql-workbench: Mysql-workbench opened ok but 
when I try to connect to db, it crashes with segfault
No longer marked as fixed in versions mysql-connector-c++/1.1.7-3.
No longer marked as fixed in versions mysql-connector-c++/1.1.7-3.
No longer marked as fixed in versions mysql-connector-c++/1.1.7-3.
> thanks
Stopping processing here.

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

Bug#843532:

[Zack Weinberg]

I can now confirm that the problem I was having is solved.  I don't
use all the functionality of dnssec-trigger, though.

I would have appreciated your waiting at least another 48 hours before
assuming I had no further complaints.

zw

Bug#844320: BTS no longer knows packages and versions in stable/testing/unstable/experimental

[Adrian Bunk]

Package: bugs.debian.org
Severity: serious

https://bugs.debian.org/release-critical/ says
"2619 release-critical bugs were closed and NONE were opened."

Looking at individual bugs, it seems the BTS no longer knows packages
and versions in stable/testing/unstable/experimental (oldstable is fine).

https://bugs.debian.org/release-critical/graph-month.png
The recent downwards bump in the red line was the Packages.gz change
affecting unstable, but that had already recovered (and went higher
than before since the Packages.xz fix also fixed version tracking
for experimental that was broken for half a year).

But something (different?) broke between 6:00 UTC and 12:00 UTC today,
and in addition to unstable and experimental is also affects
stable and testing.

Bug#828284: marked as done (dnsval: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 12:46:08 +
with message-id 
and subject line Bug#843478: Removed package(s) from unstable
has caused the Debian Bug report #828284,
regarding dnsval: FTBFS with openssl 1.1.0
to be marked as done.

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

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


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

Hi,

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

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Version: 2.2-4+rm

Dear submitter,

as the package dnsval has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/843478

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: fixed 835185 in 1.1.7-3

[Debian Bug Tracking System]

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

> fixed 835185 1.1.7-3
Bug #835185 [libmysqlcppconn7v5] mysql-workbench: Segfault when opening 
connection
Bug #836587 [libmysqlcppconn7v5] mysql-workbench: Mysql-workbench opened ok but 
when I try to connect to db, it crashes with segfault
Bug #836731 [libmysqlcppconn7v5] libmysqlcppconn7v5 version 1.1.4-2 crash 
Libreoffice Base
Marked as fixed in versions mysql-connector-c++/1.1.7-3.
Marked as fixed in versions mysql-connector-c++/1.1.7-3.
Marked as fixed in versions mysql-connector-c++/1.1.7-3.
> thanks
Stopping processing here.

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

Bug#797470: marked as done (dnsval: val_dane_check: usage DANE-TA(2) may bypass cert validation entirely)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 12:46:08 +
with message-id 
and subject line Bug#843478: Removed package(s) from unstable
has caused the Debian Bug report #797470,
regarding dnsval: val_dane_check: usage DANE-TA(2) may bypass cert validation 
entirely
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.)


-- 
797470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dnsval
Version: 2.0-1.1
Severity: grave
Tags: security upstream
Justification: user security hole

Dear Maintainer,

With the version 2.0 of the libval library, val_dane_check() completely fails 
to verify the certificate and always returns a success status when used with 
the DANE-TA(2) usage. An unsuspecting application using libval 2.0 could be 
tricked into trusting any certificate that is provided.

For example, with the DNS record:
 example.net. IN TLSA 2 0 1 a
val_dane_check() assumes that "a" is a valid DER-encoded certificate, and 
passes it without validation to OpenSSL as a trusted anchor certificate. After 
that, any certificate is accepted by SSL_get_verify_result() (as seen in 
libval.c, lines 768 to 784).

Please note that I did not find any CVE nor upstream bug report regarding this 
issue, and the library is still considered as experimental by its authors. The 
bug has already been reported in May 2013 on the IETF DANE Working Group 
mailing list by Viktor Dukhovni and acknowledged by Suresh Krishnaswamy 
(libval's developper):
https://mailarchive.ietf.org/arch/msg/dane/QySBNeQevpD3gZCLJp1ohqPpaxc

I have only partially tested the version 2.1 of libval (which is in the 
experimental depot), but could not reproduce the same issue. In addition, the 
code was completely rewritten and the logical flow modified, so the 2.1 API is 
incompatible with version 2.0.


-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Version: 2.2-4+rm

Dear submitter,

as the package dnsval has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/843478

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#794858: marked as done (sivp: non DFSG file in the source package)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 12:49:00 +
with message-id 
and subject line Bug#844209: Removed package(s) from unstable
has caused the Debian Bug report #794858,
regarding sivp: non DFSG file in the source package
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.)


-- 
794858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sivp
Version: 0.5.3+svn287-2.1
Severity: Serious
Justification: non DFSG file in the source package
User: locutusofb...@debian.org
Usertags: license-problem-non-free-img-lenna

Hi sivp Maintainer(s),
your package has been found to contain a copy of a non DFSG
file, that makes your package non DFSG.

This image (called lenna.jpg, or lena.jpg with some variants)
is an image of Lena Söderberg, photographed by Dwight Hooker,
cropped from the centerfold of the November 1972 issue of Playboy magazine.

This file is to be considered distributable but non free
(at the end of this bug report you will find a link to the lintian tag,
with a more complete description of the issue and references)

Below a list of the affected files:
- images/lena.png

note, I did stop checking for the all files as soon as I found one
good match, so they might be not all bad references, please update
this bug if not correct.

More information about this issue can be found on the
license-problem-non-free-img-lenna lintian tag [1] and Debian bug [2]

[1] https://lintian.debian.org/tags/license-problem-non-free-img-lenna.html
[2] https://bugs.debian.org/771191

thanks,

Gianfranco
--- End Message ---
--- Begin Message ---
Version: 0.5.3+svn287-2.1+rm

Dear submitter,

as the package sivp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/844209

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#754668: marked as done (sivp: obsolete binaries on powerpc)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 12:49:00 +
with message-id 
and subject line Bug#844209: Removed package(s) from unstable
has caused the Debian Bug report #754668,
regarding sivp: obsolete binaries on powerpc
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.)


-- 
754668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sivp
Version: 0.5.3+svn287-2.1
Severity: serious
Justification: FTBFS

Hi,

it seems you're no longer building sivp on powerpc but there are
binaries left behind, which is preventing its migration to testing.
Please investigate whether dropping support for powerpc was the right
thing, and if it is, please request removal of outdated powerpc packages
from unstable:
  https://wiki.debian.org/ftpmaster_Removals

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Version: 0.5.3+svn287-2.1+rm

Dear submitter,

as the package sivp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/844209

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#805683: marked as done (sineshaper: FTBFS: incompatiable compile flags for glibmm-2.4)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 12:50:09 +
with message-id 
and subject line Bug#844266: Removed package(s) from unstable
has caused the Debian Bug report #805683,
regarding sineshaper: FTBFS: incompatiable compile flags for glibmm-2.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.)


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

Dear Maintainer,

The package fails to build:

In file included from /usr/include/c++/5/type_traits:35:0,
 from /usr/include/sigc++-2.0/sigc++/visit_each.h:22,
 from /usr/include/sigc++-2.0/sigc++/functors/slot.h:6,
 from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
 from /usr/include/sigc++-2.0/sigc++/signal.h:8,
 from /usr/include/sigc++-2.0/sigc++/sigc++.h:86,
 from /usr/include/glibmm-2.4/glibmm/thread.h:51,
 from /usr/include/glibmm-2.4/glibmm.h:87,
 from dssiuiclient.cpp:31:
/usr/include/c++/5/bits/c++0x_warning.h:32:2: error: #error This file requires 
compiler and library support for the ISO C++ 2011 standard. This support is 
currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 
compiler options.
 #error This file requires compiler and library support for the \
  ^
In file included from 
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:7:0,
 from /usr/include/sigc++-2.0/sigc++/functors/slot.h:7,
 from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
 from /usr/include/sigc++-2.0/sigc++/signal.h:8,
 from /usr/include/sigc++-2.0/sigc++/sigc++.h:86,
 from /usr/include/glibmm-2.4/glibmm/thread.h:51,
 from /usr/include/glibmm-2.4/glibmm.h:87,
 from dssiuiclient.cpp:31:
/usr/include/sigc++-2.0/sigc++/functors/functor_trait.h:92:3: warning: 
identifier 'decltype' is a keyword in C++11 [-Wc++0x-compat]
   static int check(X_functor* obj, decltype(&X_functor::operator()) p = 
nullptr);
   ^

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Version: 0.4.2-8+rm

Dear submitter,

as the package sineshaper has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/844266

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#832366: marked as done (sineshaper: does not start)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 12:50:09 +
with message-id 
and subject line Bug#844266: Removed package(s) from unstable
has caused the Debian Bug report #832366,
regarding sineshaper: does not start
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.)


-- 
832366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sineshaper
Version: 0.4.2-8
Severity: grave

Hi,

sineshaper does not start properly. When run it gives the jack-dssi-
host usage message:

Usage: sineshaper [-v] [-a] [-n] [-p ] [-c ] [-] 
[:] [...]
[...]

This is because the sineshaper dssi plugin is installed into
/usr/lib//dssi which is not in the dssi search path (only
/usr/lib/dssi is).

Given that a bug this serious has not been reported in two years, maybe
no-one uses this package?

Thanks,
James

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 0.4.2-8+rm

Dear submitter,

as the package sineshaper has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/844266

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#801738: marked as done (scilab-sivp: Please either update the depends so that it picks up gcc 5 migration or remove it.)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 12:49:00 +
with message-id 
and subject line Bug#844209: Removed package(s) from unstable
has caused the Debian Bug report #801738,
regarding scilab-sivp: Please either update the depends so that it picks up gcc 
5 migration or remove it.
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.)


-- 
801738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scilab-sivp
Version: 0.5.3+svn287-2.1
Severity: important

Dear Maintainer,
The depends of scilab-sivp are

Depends: libc6 (>= 2.14), libgcc1 (>= 1:4.1.1), libopencv-calib3d2.4,
libopencv-contrib2.4, libopencv-core2.4, libopencv-features2d2.4,
libopencv-flann2.4, libopencv-gpu2.4, libopencv-highgui2.4,
libopencv-imgproc2.4, libopencv-legacy2.4, libopencv-ml2.4,
libopencv-objdetect2.4, libopencv-ocl2.4, libopencv-photo2.4,
libopencv-stitching2.4, libopencv-superres2.4,
libopencv-ts2.4,libopencv-video2.4, libopencv-videostab2.4, libstdc++6
(>= 4.1.1), scilab (>= 5.0)

So please update it for gcc 5 migration or remove it if that is not possible.

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

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 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)

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Version: 0.5.3+svn287-2.1+rm

Dear submitter,

as the package sivp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/844209

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#844133: marked as done (sivp: FTBFS: segmentation fault)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 12:49:00 +
with message-id 
and subject line Bug#844209: Removed package(s) from unstable
has caused the Debian Bug report #844133,
regarding sivp: FTBFS: segmentation fault
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.)


-- 
844133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sivp
Version: 0.5.3+svn287-2.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-2016 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 '/<>/sivp-0.5.3+svn287'
> make[1]: 'update-config' is up to date.
> make[1]: Leaving directory '/<>/sivp-0.5.3+svn287'
> SCI_DISABLE_TK=1 SCI_JAVA_ENABLE_HEADLESS=1 
> DOCBOOK_ROOT=/usr/share/sgml/docbook/stylesheet/xsl/nwalsh \
> /usr/bin/scilab -nw -f builder.sce
> Error: Impossible to define SCIHOME environment variable.
> libEGL warning: DRI3: xcb_connect failed
> libEGL warning: DRI2: xcb_connect failed
> libEGL warning: DRI2: xcb_connect failed
> Caught handled GLException: EGLGLXDrawableFactory - Could not initialize 
> shared resources for EGLGraphicsDevice[type .egl, v0.0.0, connection nil, 
> unitID 0, handle 0x0, owner true, ResourceToolkitLock[obj 0x2f7b8b80, isOwner 
> true, <6a79100b, 50c7e9d4>[count 1, qsz 0, owner 
> ]]] on thread main-SharedResourceRunner
> [0]: 
> jogamp.opengl.egl.EGLDrawableFactory$SharedResourceImplementation.createSharedResource(EGLDrawableFactory.java:518)
> [1]: jogamp.opengl.SharedResourceRunner.run(SharedResourceRunner.java:353)
> [2]: java.lang.Thread.run(Thread.java:745)
> Caused[0] by GLException: Failed to created/initialize EGL display incl. 
> fallback default: native 0x0, error 0x3001/0x3001 on thread 
> main-SharedResourceRunner
> [0]: 
> jogamp.opengl.egl.EGLDisplayUtil.eglGetDisplayAndInitialize(EGLDisplayUtil.java:297)
> [1]: jogamp.opengl.egl.EGLDisplayUtil.access$300(EGLDisplayUtil.java:58)
> [2]: 
> jogamp.opengl.egl.EGLDisplayUtil$1.eglGetAndInitDisplay(EGLDisplayUtil.java:320)
> [3]: 
> com.jogamp.nativewindow.egl.EGLGraphicsDevice.open(EGLGraphicsDevice.java:125)
> [4]: 
> jogamp.opengl.egl.EGLDrawableFactory$SharedResourceImplementation.createEGLSharedResourceImpl(EGLDrawableFactory.java:532)
> [5]: 
> jogamp.opengl.egl.EGLDrawableFactory$SharedResourceImplementation.createSharedResource(EGLDrawableFactory.java:516)
> [6]: jogamp.opengl.SharedResourceRunner.run(SharedResourceRunner.java:353)
> [7]: java.lang.Thread.run(Thread.java:745)
> Building macros...
> -- Creation of [SIVPlib] (Macros) --
> WARNING: Due to the multivendors nature of the Unix world, the function 
> 'haveacompiler' is only supported under Windows.
> Building gateway...
> WARNING: Due to the multivendors nature of the Unix world, the function 
> 'haveacompiler' is only supported under Windows.
>Generate a gateway file
>  
> !#ifdef __cplusplus !
> !   !
> !extern "C" {   !
> !   !
> !#endif !
> !   !
> !#include!
> !   !
> !#include!
> !   !
> !#include !
> !   !
> !#include !
> !   !
> !static int direct_gateway(char *fname,void F(void)) { F();return 0;};  !
> !   !
> !extern Gatefunc int_test;  !
> !   !
> !extern Gatefunc int_sivp_init; !
> !   !
> !extern Gatefunc int_imread; 

Bug#834893: marked as done (gnupg: CVE-2016-6313: RNG prediction vulnerability)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 12:51:04 +
with message-id 
and subject line Bug#844272: Removed package(s) from unstable
has caused the Debian Bug report #834893,
regarding gnupg: CVE-2016-6313: RNG prediction vulnerability
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.)


-- 
834893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnupg
Version: 1.4.12-1
Severity: grave
Tags: security upstream patch fixed-upstream
Control: fixed -1 1.4.18-7+deb8u2

Hi,

the following vulnerability was published for gnupg.

CVE-2016-6313[0]:
libgcrypt: PRNG output is predictable

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-6313

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 1.4.20-6+rm

Dear submitter,

as the package gnupg has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/844272

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: Bug#841474 marked as pending

[Debian Bug Tracking System]

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

> tag 841474 pending
Bug #841474 [afl] afl: FTBFS on armhf (illegal instruction in afl-clang-fast)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#844140: mia: FTBFS: lxml.etree.XMLSyntaxError: None

[Gert Wollny]

I don't think that the bug is related to threading/locking failures
within mia, i.e. compiling the package by using g++-5* and 
-fsanitize=thread doesn't show any locking problems (specifically no
double un-locking of a mutex). 

Specifically, the error hints at 

   ./mia-3dmaskseeded --help-xml  

not generating the required output that is later used by the python
program that actually fails. And this command is run without reported
errors, i.e. it doesn't crash like it seems to be what would be
expected from threading errors that are revealed when TSX is enabled. 

In addition, the only place in the code where mutex locking is applied
when running the command like given above is a piece of code that is
shared by all other command line tools in mia, and running these tools
with the the same command line option (--help-xml) don't fail.

It would be nice to know whether the failure was exactly at the same
point when the build was tried, or whether there were differences
there?

Are there any other options, apart from using the thread sanitizer,
that can help me to debug this problem?


Best, 
Gert 

* g++-5, because for g++-6 on Debian the thread sanitizer is currently
broken (#796246). 

Processed: Please help fixing since several dependencies are in danger to become removed

[Debian Bug Tracking System]

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

> tags 841610 help
Bug #841610 [src:statsmodels] statsmodels: FTBFS: TypeError: cannot sort an 
Index object in-place, use sort_values instead
Added tag(s) help.
> tags 841610 upstream
Bug #841610 [src:statsmodels] statsmodels: FTBFS: TypeError: cannot sort an 
Index object in-place, use sort_values instead
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#841474: marked as pending

[Daniel Stender]

tag 841474 pending
thanks

Hello,

Bug #841474 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=collab-maint/afl.git;a=commitdiff;h=a4abda1

---
commit a4abda1a4f8cdff5b4bd59df968e861f9d27bcb5
Author: Daniel Stender 
Date:   Mon Nov 14 13:50:31 2016 +0100

deb/rules: add -mfpu=vfp3 to $CFLAGS on armhf

diff --git a/debian/changelog b/debian/changelog
index 547b2ff..e78f22f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+afl (2.34b-3) UNRELEASED; urgency=medium
+
+  * deb/rules:
++ add -mfpu=vfp3 to $CFLAGS on armhf (Closes: #841474).
++ pass $clang_cflags to make -C llvm_mode.
+
+ -- Daniel Stender   Mon, 14 Nov 2016 13:50:06 +0100
+
 afl (2.34b-2) unstable; urgency=medium
 
   * Upload to unstable.

Bug#841474: marked as done (afl: FTBFS on armhf (illegal instruction in afl-clang-fast))

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 13:18:38 +
with message-id 
and subject line Bug#841474: fixed in afl 2.34b-3
has caused the Debian Bug report #841474,
regarding afl: FTBFS on armhf (illegal instruction in afl-clang-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.)


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

>From 2.30b-1 onwards (the first package which was tried to build against 
>llvm-toolchain
> 3.7 on this arch), AFL build breaks with "illegal instruction" trying to 
> compile
test-instr.c with afl-clang-fast, now trying to build with clang 3.9 [1]:


[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; AFL_QUIET=1 AFL_PATH=. 
AFL_CC=clang-3.9
../afl-clang-fast -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign
-DAFL_PATH=\"/usr/lib/afl\" -DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.34b\"  
../test-instr.c -o
test-instr -fPIE -pie -Wl,-z,relro -Wl,-z,now
Illegal instruction


Julien Puydt has reported something similar for the flint package:
https://bugs.debian.org/798111 (Illegal instruction after compiling some code)

Strangely, the package builds fine in the porterbox and with a 
qemu-bootstrapped local
sbuild [2].

Thanks for any input (if this could be worked around in the AFL package),
I'll try to seek what's causing this in the build toolchain.
DS

[1] 
https://buildd.debian.org/status/fetch.php?pkg=afl&arch=armhf&ver=2.34b-2&stamp=1474836143

[2] 
http://www.danielstender.com/buildlogs/afl_2.34b-2_armhf-2016-10-20T23:40:16Z.build

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

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

Versions of packages afl depends on:
ii  build-essential  12.2
ii  libc62.24-3

Versions of packages afl recommends:
pn  afl-clang  
ii  afl-doc2.34b-2

Versions of packages afl suggests:
ii  gnuplot  5.0.4+dfsg1-3

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: afl
Source-Version: 2.34b-3

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

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

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

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated afl 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, 14 Nov 2016 14:00:47 +0100
Source: afl
Binary: afl afl-clang afl-doc
Architecture: source amd64 all
Version: 2.34b-3
Distribution: experimental
Urgency: medium
Maintainer: Daniel Stender 
Changed-By: Daniel Stender 
Description:
 afl- instrumentation-driven fuzzer for binary formats
 afl-clang  - instrumentation-driven fuzzer for binary formats - clang support
 afl-doc- instrumentation-driven fuzzer for binary formats - documentation
Closes: 841474
Changes:
 afl (2.34b-3) experimental; urgency=medium
 .
   * deb/rules:
 + add -mfpu=vfp3 to $CFLAGS for clang on armhf (Closes: #841474).
 + pass $clang_cflags to make -C llvm_mode.
 + drop removal of -fstack-protector from $CFLAGS for clang (not needed
   anymore).
Checksums-Sha1:
 937743f32562174ca8e340b45763defec6c782d4 1965 afl_2.34b-3.dsc
 b5916e54b55fcc5670a3ca88011052fea14801cc 761084 afl_2.34b.orig.tar.xz
 de952d0e0e1339425c0ffebce02e5c8188a0961a 13900 afl_2.34b-3.debian.tar.xz
 bbc533dba14fbc00cf37f3e24b9c011a888bbdae 58726 afl-clang_2.34b-3_amd64.deb
 c440a05a78b794e4dd8ee2c40602ff01e61898aa 223658 afl-dbgsym_2.34b-3_amd64.deb
 5fc8b99828a7836821348afddcfe55e1115dcc67 131828 afl-doc_2.34b-3_all.deb
 3101cf07cdb46a246909ae15fcc81ed71ea9f59c 5663 
afl_2.34b-3_20161114T130308z-1d1c1723.buildi

Bug#844323: FTBFS on ppc64el

[Breno Leitao]

Source: haskell-zeromq4-haskell
Version: 0.6.5
Severity: serious
Justification: fails to build from source (but built successfully in the past)


The package haskell-zeromq4-haskell is failing to build on ppc64el port
due to the following error:

  [1 of 6] Compiling System.ZMQ4.Internal.Base (
  dist/build/System/ZMQ4/Internal/Base.hs,
  dist/build/System/ZMQ4/Internal/Base.o )
  /tmp/ghc7817_0/ghc_6.s: Assembler messages:
  
  /tmp/ghc7817_0/ghc_6.s:14471:0: error:
   Error: operand out of domain (2 is not a multiple of 4)
  
This is being caused by a wrong assembly code at ghc_6.s

The faulty instruction is:
   
   lwa 29, 2(3)
  
This is a not valid assembly code, because DS filed (2 argument), should
be a word offset. Since a word is 32 bits, it should be multiple of 4.
In this case, it is trying to load an un-aligned word.


I am still trying to discover why this illegal instruction was
generated.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: ppc64el (ppc64le)

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

Bug#844324: bup: bup join produces invalid tar output

[John Kozak]

Package: bup
Version: 0.25-1
Severity: serious

Dear Maintainer,

Here's a transcript of a session to illustrate the problem:

  renn:/tmp$ mkdir test
  renn:/tmp$ echo xxx>test/xxx
  renn:/tmp$ bup -d test.bup init
  Initialized empty Git repository in /tmp/test.bup/
  renn:/tmp$ bup -d test.bup index /tmp/test
  Indexing: 2, done.
  renn:/tmp$ bup -d test.bup save -n t1 /tmp/test
  Reading index: 2, done.
  Saving: 100.00% (4/4k, 2/2 files), done.
  bloom: creating from 1 file (8 objects).
  renn:/tmp$ bup -d test.bup ls
  t1/
  renn:/tmp$ bup -d test.bup ls t1
  2016-11-14-132249@  latest@
  renn:/tmp$ bup -d test.bup join t1 | tar tf -
  tar: This does not look like a tar archive
  tar: Exiting with failure status due to previous errors

The command `bup -d test.bup join t1` should send a tar file to stdout;
what is being sent looks a bit like one, but obviously isn't quite.

I have marked this as "serious" because I believe this is the only way
to directly restore a remote backup.

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

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

Versions of packages bup depends on:
ii  git  1:2.1.4-2.1+deb8u2
ii  libc62.19-18+deb8u6
ii  par2 0.6.11-1
ii  python   2.7.9-1
ii  python-pylibacl  0.5.2-1
ii  python-pyxattr   0.5.3-1
ii  python2.72.7.9-2+deb8u1
pn  python:any   

Versions of packages bup recommends:
ii  bup-doc 0.25-1
ii  python-fuse 2:0.2.1-10
ii  python-tornado  4.2.0-1~bpo8+1

bup suggests no packages.

-- no debconf information

--
John

Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Vincent Lefevre]

On 2016-11-14 12:09:50 +, Luca Boccassi wrote:
> The same versions are available in the i386 and amd64 archives. Are you
> sure your local apt sources are all up to date?

I could install the i386 versions later. But an upgrade should not
fail even when the apt sources are not up to date: that's the goal
of Depends and Breaks to make sure that the package system remains
in a consistent state.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Luca Boccassi]

On Mon, 2016-11-14 at 14:40 +0100, Vincent Lefevre wrote:
> On 2016-11-14 12:09:50 +, Luca Boccassi wrote:
> > The same versions are available in the i386 and amd64 archives. Are you
> > sure your local apt sources are all up to date?
> 
> I could install the i386 versions later. But an upgrade should not
> fail even when the apt sources are not up to date: that's the goal
> of Depends and Breaks to make sure that the package system remains
> in a consistent state.

If the i386 libraries are installed, then they must be upgraded at the
same time. You cannot install them later. The dependencies are there to
ensure this happens.

This looks like a bug in aptitude, which shouldn't have let the upgrade
happen if it couldn't satisfy all dependencies. Given the i386 top-level
dependencies, the nvidia-driver-libs-i386 metapapkg, is only a recommend
of nvidia-driver-libs, I'd guess aptitude failed to parse it.

Kind regards,
Luca Boccassi


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

Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Vincent Lefevre]

On 2016-11-14 14:01:55 +, Luca Boccassi wrote:
> If the i386 libraries are installed, then they must be upgraded at the
> same time. You cannot install them later. The dependencies are there to
> ensure this happens.
> 
> This looks like a bug in aptitude, which shouldn't have let the upgrade
> happen if it couldn't satisfy all dependencies. Given the i386 top-level
> dependencies, the nvidia-driver-libs-i386 metapapkg, is only a recommend
> of nvidia-driver-libs, I'd guess aptitude failed to parse it.

nvidia-driver-libs-i386 was installed, but aptitude chose to remove
it (together with other packages) for the reason it was not used:

[REMOVE, NOT USED] libegl-nvidia0:i386 367.57-1
[REMOVE, NOT USED] libegl1-glvnd-nvidia:i386 367.57-1
[REMOVE, NOT USED] libgldispatch0-nvidia:i386 367.57-1
[REMOVE, NOT USED] libgles-nvidia1:amd64 367.57-1
[REMOVE, NOT USED] libgles-nvidia1:i386 367.57-1
[REMOVE, NOT USED] libgles-nvidia2:amd64 367.57-1
[REMOVE, NOT USED] libgles-nvidia2:i386 367.57-1
[REMOVE, NOT USED] libgles1-glvnd-nvidia:amd64 367.57-1
[REMOVE, NOT USED] libgles1-glvnd-nvidia:i386 367.57-1
[REMOVE, NOT USED] libgles2-glvnd-nvidia:amd64 367.57-1
[REMOVE, NOT USED] libgles2-glvnd-nvidia:i386 367.57-1
[REMOVE, NOT USED] libglx-nvidia0:amd64 367.57-1
[REMOVE, NOT USED] libglx-nvidia0:i386 367.57-1
[REMOVE, NOT USED] libglx0-glvnd-nvidia:amd64 367.57-1
[REMOVE, NOT USED] libglx0-glvnd-nvidia:i386 367.57-1
[REMOVE, NOT USED] libnvidia-cfg1:amd64 367.57-1
[REMOVE, NOT USED] libnvidia-cfg1:i386 367.57-1
[REMOVE, NOT USED] libnvidia-eglcore:i386 367.57-1
[REMOVE, NOT USED] libopengl0-glvnd-nvidia:amd64 367.57-1
[REMOVE, NOT USED] libopengl0-glvnd-nvidia:i386 367.57-1
[REMOVE, NOT USED] libvulkan1:amd64 1.0.26.0+dfsg1-1
[REMOVE, NOT USED] libvulkan1:i386 1.0.26.0+dfsg1-1
[REMOVE, NOT USED] nvidia-driver-libs:i386 367.57-1
[REMOVE, NOT USED] nvidia-driver-libs-i386:i386 367.57-1
[REMOVE, NOT USED] nvidia-vulkan-common:amd64 367.57-1
[REMOVE, NOT USED] nvidia-vulkan-icd:amd64 367.57-1
[REMOVE, NOT USED] nvidia-vulkan-icd:i386 367.57-1

I don't know why aptitude did this. But anyway, Recommends are not
strong dependencies, and aptitude often ignores Recommends. So, you
should not rely on it.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#811825: FaCT++ Debian package removal

[Roberto Bagnara]

Hello Tobias.

Sorry for the delay in answering your message: I was traveling.

On 11/11/2016 02:08 AM, Tobias Hansen wrote:
> I noticed today that ppl was removed from Debian testing due to two RC
> bugs. The problem is that ppl 1.2 has a new soname (14), that means it
> requires a library transition. We are now already past the library
> transition freeze for Debian stretch. Are you shure that the ABI of ppl
> changed with version 1.2, i.e. that this soname bump is required?

No, I am not sure it is required: we bump it at any new release
just as a caution.

> It would now probably be best to patch version 1.1 of ppl to have at
> least this version in the next Debian release. The previous mails from
> this bug report suggest that the patch that was discussed was not enough
> to fix the build with gcc 6. Could you provide a new patch for this?

I am sorry, but I do not follow: why not switch to PPL 1.2, which
was released around 9 months ago and that is the current stable version?
More generally, we have no time to follow the evolution of Debian.
We have offered (multiple times) all the possible cooperation upstream,
but we got the impression the Debian people is not interested:
they do not use our mailing list and they seem totally uninterested to
explain the issues in non-Debian terms.  I now repeat the offer to you:
if you are willing to explain what the problem is without assuming
we know anything about Debian, you are more than welcome, and the
problem will be solved very quickly.
Kind regards,

   Roberto

> On Sat, 6 Aug 2016 14:34:14 +0200 Roberto Bagnara 
> wrote:
>> The new version upstream (PPL 1.2, released in February 2016) solves
>> all problems wrt GCC 6.  If upgrading to the latest upstream release
>> is not wanted (why?), then patches have been provided in this very issue.
>> Kind regards,
>>
>>Roberto
>>
> 


-- 
 Prof. Roberto Bagnara

Applied Formal Methods Laboratory - University of Parma, Italy
mailto:bagn...@cs.unipr.it
  BUGSENG srl - http://bugseng.com
  mailto:roberto.bagn...@bugseng.com

Bug#806865: transition: ppl

[Roberto Bagnara]

On 11/12/2016 03:02 PM, Tobias Hansen wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi Release Team,
> 
> I noticed yesterday that ppl has two RC bugs and was removed from
> testing. I would like to take over the package and fix it, but one of
> the RC bugs (#811825) is best fixed by updating to the new upstream
> version, which requires a small library transition. Since the
> debian-devel-announce@l.d.o mail from November 5 said the transition
> freeze is only for "transitions that involve a large number of packages",
> I'd thought I'd ask if we can still do this transition.
> 
> I already created a package of ppl 1.2 that fixes both RC bugs. ppl has
> two reverse dependencies, which were of course both removed from testing
> because of ppl:
> 
> apron
> cloog-ppl
> 
> I checked that they both build without changes against the updated ppl
> package.
> 
> If it's too late for the transition, we'll have to see if we can fix
> #811825 by applying a patch that does not require a transition.
> 
> Thanks,
> Tobias
> 
> Ben file:
> 
> title = "ppl";
> is_affected = .depends ~ "libppl13v5" | .depends ~ "libppl14";
> is_good = .depends ~ "libppl14";
> is_bad = .depends ~ "libppl13v5";

Just to say that upstream is more than willing too cooperate
with Tobias if he decides to take over the ppl package.
Kind regards,

   Roberto

-- 
 Prof. Roberto Bagnara

Applied Formal Methods Laboratory - University of Parma, Italy
mailto:bagn...@cs.unipr.it
  BUGSENG srl - http://bugseng.com
  mailto:roberto.bagn...@bugseng.com

Bug#811825: FaCT++ Debian package removal

[Tobias Hansen]

Hello Roberto,

I have some good news. But let me first explain the situation.

What happened here is a social problem that sometimes occurs in Debian.
The package has a single person as a maintainer. He didn't respond to
the bugs, and nobody else felt responsible to work on the issue. On top
of that, it is normally expected not to upload a package without the
maintainers consent, so a non-responding maintainer can slow things down
quite a lot.

The reason I asked for a patch is that a soname bump requires a library
transitions and for the next Debian release these were only allowed
until November 5. The good news is, we moved the package to team
maintenance, packaged version 1.2 and got a transition granted despite
the freeze. So the problem should be resolved. With a team maintained
package RC bugs will hopefully be fixed more quickly in the future.

Here is the bug tracking the ppl 1.2 transition:
https://bugs.debian.org/844100

Best,
Tobias

On 11/14/2016 02:05 PM, Roberto Bagnara wrote:
> 
> Hello Tobias.
> 
> Sorry for the delay in answering your message: I was traveling.
> 
> On 11/11/2016 02:08 AM, Tobias Hansen wrote:
>> I noticed today that ppl was removed from Debian testing due to two RC
>> bugs. The problem is that ppl 1.2 has a new soname (14), that means it
>> requires a library transition. We are now already past the library
>> transition freeze for Debian stretch. Are you shure that the ABI of ppl
>> changed with version 1.2, i.e. that this soname bump is required?
> 
> No, I am not sure it is required: we bump it at any new release
> just as a caution.
> 
>> It would now probably be best to patch version 1.1 of ppl to have at
>> least this version in the next Debian release. The previous mails from
>> this bug report suggest that the patch that was discussed was not enough
>> to fix the build with gcc 6. Could you provide a new patch for this?
> 
> I am sorry, but I do not follow: why not switch to PPL 1.2, which
> was released around 9 months ago and that is the current stable version?
> More generally, we have no time to follow the evolution of Debian.
> We have offered (multiple times) all the possible cooperation upstream,
> but we got the impression the Debian people is not interested:
> they do not use our mailing list and they seem totally uninterested to
> explain the issues in non-Debian terms.  I now repeat the offer to you:
> if you are willing to explain what the problem is without assuming
> we know anything about Debian, you are more than welcome, and the
> problem will be solved very quickly.
> Kind regards,
> 
>Roberto
> 
>> On Sat, 6 Aug 2016 14:34:14 +0200 Roberto Bagnara 
>> wrote:
>>> The new version upstream (PPL 1.2, released in February 2016) solves
>>> all problems wrt GCC 6.  If upgrading to the latest upstream release
>>> is not wanted (why?), then patches have been provided in this very issue.
>>> Kind regards,
>>>
>>>Roberto
>>>
>>
> 
> 

Bug#843073: Debian Installer Stretch Alpha 8 release

[Felipe Sateler]

On Mon, 14 Nov 2016 12:22:58 +0100 Raphael Hertzog 
wrote:
> Control: tag -1 + patch
> Control: severity -1 serious
>
> Hi Guillem,
>
> On Sun, 13 Nov 2016, Guillem Jover wrote:
> > > The /usr merge violates core assumptions in dpkg-shlibdeps. The reason
> > > that amd64 isn't broken is sheer luck.
> > > /etc/ld.so.conf.d/x86_64-linux-gnu.conf lists /lib before /usr/lib, so
> > > dpkg-shlibdeps considers that first. Swapping them or simply removing
> > > /lib (as seems reasonable on a merged /usr), breaks almost any build
on
> > > amd64 (e.g. dash). The breakage on amd64 is simply hidden.
> >
> > Right. I'm happy to assist people who want to fix this to try to find
> > a proper solution in dpkg-dev, but I'm not planning on spending time
> > on this on my own.
>
> Please find two patches attached.

Thanks for the patch. This looks better than what I had been working on.

Saludos

Bug#844233: python-passlib: FTBFS with probability of 0.22% due to non-deterministic testsuite

[Chris Lamb]

James Clarke wrote:

> I believe it's actually (3C2)*(2/3)^16 - (3C1)*(1/3)^16 ~= 0.46% (the
> subtracted value is negligible).

Thanks :)

> > It will also FTBFS if it generates the exact same random string, but
> > that seems a little more unlikely.
> 
> P = (1/3)^16 = 2.3e-8 or 0.023%, which isn't quite as absurdly small
> as you might think.

Ah, but a little more unlikely than 0.46%… :)


Regards,

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

Bug#843073: Debian Installer Stretch Alpha 8 release

[Raphael Hertzog]

On Mon, 14 Nov 2016, Raphael Hertzog wrote:
> Please find two patches attached.

Given Felipe's comment about not breaking API for find_library()
I opted to create a new function, but a quick codesearch seems
to indicate that no other package is relying on this function.

https://codesearch.debian.net/search?q=find_library+filetype%3Aperl&perpkg=1

And the versioning of the module is 0.x indicating that the API
had not been declared stable.

So you can either get rid of find_library() entirely or replace
it entirely with the code find_library_locations() (and then drop
find_library_locations) to clean up the codebase.

dpkg-shlibdeps is the only user of that function within dpkg.

If you want me to rework the patches to do one of the suggested
cleanup, let me know.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#844333: node-iconv-lite: Source doesn't include required directories

[Shanavas M]

Package: node-iconv-lite
Version: 0.4.13-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Directories `encodings` and `generation` are not included in debian package 
archive.
npm2deb skips it as those directories are not mentioned in package.json.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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)

Versions of packages node-iconv-lite depends on:
ii  nodejs  4.6.1~dfsg-1

node-iconv-lite recommends no packages.

node-iconv-lite suggests no packages.

-- no debconf information

Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Diederik de Haas]

On maandag 14 november 2016 15:12:14 CET Vincent Lefevre wrote:
> aptitude often ignores Recommends. So, you should not rely on it.

That's an incorrect statement.
Aptitude, and I think apt too, doesn't automatically install _new_ recommended 
packages for an already installed package. 
It does report "The following recommended packages will not be installed" (or 
sth along those lines). But that's far from ignoring it.

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

Processed: block 844186 with 844333

[Debian Bug Tracking System]

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

> block 844186 with 844333
Bug #844186 [wnpp] RFH: libjs-handlebars -- need help in modifying grunt to 
build libjs-handlebars (and other modules with Gruntfile.js)
844186 was not blocked by any bugs.
844186 was blocking: 837467
Added blocking bug(s) of 844186: 844333
> thanks
Stopping processing here.

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

Bug#828255: marked as done (burp: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 15:03:43 +
with message-id 
and subject line Bug#828255: fixed in burp 1.4.40-5
has caused the Debian Bug report #828255,
regarding burp: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: burp
Version: 1.3.48-4.1
Severity: important
Control: block 827061 by -1

Hi,

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

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Source: burp
Source-Version: 1.4.40-5

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

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated burp 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, 14 Nov 2016 12:24:58 +0100
Source: burp
Binary: burp
Architecture: source amd64
Version: 1.4.40-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Christoph Martin 
Description:
 burp   - Simple cross-platform network BackUp and Restore Program
Closes: 828255
Changes:
 burp (1.4.40-5) unstable; urgency=medium
 .
   * QA upload
   * fix flags-32bit.patch
   * fix build with openssl 1.1 (closes: #828255)
Checksums-Sha1:
 59e01b8d1ba84b56024e11c79e59764780f80f6c 1900 burp_1.4.40-5.dsc
 27f5cd892e6d2ae359d38c74870110d111273a0e 23948 burp_1.4.40-5.debian.tar.xz
 30bc167694e2c2dab263aff3c9f545dfc632c8fc 531310 burp-dbgsym_1.4.40-5_amd64.deb
 f5c5b2c695543664ae4b8e01b18c5db2778be693 5601 
burp_1.4.40-5_20161114T133429z-37438e48.buildinfo
 2ba7d1877c927a0655fff5bf78b835efb00aa7ab 188740 burp_1.4.40-5_amd64.deb
Checksums-Sha256:
 d028fce0e3253ab5ee21b1905ce7df6c642079731385b1971c252f3406d39f0c 1900 
burp_1.4.40-5.dsc
 c01a4d76a0085487d383ea87e66b3b2c9c94e5a0dfdfd9869e01f1705bd477bb 23948 
burp_1.4.40-5.debian.tar.xz
 7ba78b74bb1b2098ee6e15cc4e38aaa1304aebdadda6fbf5e26e1fb875368f32 531310 
burp-dbgsym_1.4.40-5_amd64.deb
 693c5216ce5d9bb39c56002243b39a36f8827d3dfde2d36a9c219ed3deaa5540 5601 
burp_1.4.40-5_20161114T133429z-37438e48.buildinfo
 9e49584ecb9ab62af7a09cde0877a6a196fff2cec427eba9d4d310db56eb2e30 188740 
burp_1.4.40-5_amd64.deb
Files:
 25b3c74963b67c8a2cb06a57597c289d 1900 utils extra burp_1.4.40-5.dsc
 dcd207630ede011ef7696feb4a17fd10 23948 utils extra burp_1.4.40-5.debian.tar.xz
 85e78595cc6891e775429a08d1db2d87 531310 debug extra 
burp-dbgsym_1.4.40-5_amd64.deb
 37438e48c93eb73c899877ec03c78b9b 5601 utils extra 
burp_1.4.40-5_20161114T133429z-37438e48.buildinfo
 330244613b3b550a97c9b531a6d0e6c2 188740 utils extra burp_1.4.40-5_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYKb8SAAoJEPqBswqWsQmc9cAP/jIbLWhtsOX4rxnBkYd5yV6d
qefUNlBMBvI5bMhFUCkhySzfpCt38RiqzgSdYzel1FEqMLGBs1TDutEi5jZahg2/
PrgCTZ1LV2Wewr0X/3aP2heYvDoxbNiDQv6E3QSwmtzRfgrLu5darsomOTRuE3rz
nsOEDdbe1oTK58Erhdxv1sz8APaX9HnNDrT3hUlhk9xj+mZlrCqRXVnFkkyl+Zxe
Bs5mOckXveWF4BUM0hBFQ98uiF9+MysN/UvmhGh8cS+36ELtAWfn2b9f9I6QHxq2
LXbl/SK9rZGgV+tWEGqzsNx7WG0OHZs7yadqeEt0uLetH8bWlJ/Jxdf7p0cH0hH4
MbKzGMEWIRVoQn1NY1987fzYF5/thR//CMmxq8xp1aF8Zbq5/YVQIivVZkW7mQC/
OYa4CezTZjuIiOv/YjgvVhVFNr3kRDpMoGJ2DflMYS9pkwqoXHpFOghJDAptUC0S
c96PIR8TLJCPmyLXJTRNt5hzUc25oC3Oc4ea3i0asDd26YUW7ao8Sc7p/1Bag+ss
TDhJlhwE9qBnV1Pe/XdG4HG6tgClwAn3TUNeA/HseZUQ72zYS76fLN/YN546X0nn
QBbkkOlIwLluFMzJsTLd6wKJ7bYTqdL4Xka16zrD7kDXNyHhAfYd6bDJ/bRHpz6J
R+

Bug#842815: marked as done (libsis-jhdf5-java: Please support HDF5 1.10)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 15:04:27 +
with message-id 
and subject line Bug#842815: fixed in libsis-jhdf5-java 14.12.6-1
has caused the Debian Bug report #842815,
regarding libsis-jhdf5-java: Please support HDF5 1.10
to be marked as done.

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

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


-- 
842815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsis-jhdf5-java
Version: 14.12.1-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

libsis-jhdf5-java FTBFS against hdf5-1.10 currently in experimental:

===
All
Total tests run: 309, Failures: 279, Skips: 6
===

[Utils] Attempting to create /<>/test-output/old/All/toc.html
[Utils]   Directory /<>/test-output/old/All exists: true
[Utils] Attempting to create /<>/test-output/old/All/All.properties
[Utils]   Directory /<>/test-output/old/All exists: true
[Utils] Attempting to create /<>/test-output/old/All/index.html
[Utils]   Directory /<>/test-output/old/All exists: true
[Utils] Attempting to create /<>/test-output/old/All/main.html
[Utils]   Directory /<>/test-output/old/All exists: true
[Utils] Attempting to create /<>/test-output/old/All/groups.html
[Utils]   Directory /<>/test-output/old/All exists: true
[Utils] Attempting to create /<>/test-output/old/All/classes.html
[Utils]   Directory /<>/test-output/old/All exists: true
[Utils] Attempting to create 
/<>/test-output/old/All/reporter-output.html
[Utils]   Directory /<>/test-output/old/All exists: true
[Utils] Attempting to create 
/<>/test-output/old/All/methods-not-run.html
[Utils]   Directory /<>/test-output/old/All exists: true
[Utils] Attempting to create 
/<>/test-output/old/All/testng.xml.html
[Utils]   Directory /<>/test-output/old/All exists: true
[Utils] Attempting to create test-output/old/index.html
[Utils]   Directory test-output/old exists: true
[TestNG] Time taken by org.testng.reporters.SuiteHTMLReporter@156643d4: 83 ms
[TestNG] Time taken by org.testng.reporters.EmailableReporter2@7d6f77cc: 37 ms
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.HDF5TimeDurationReaderTest.xml
[Utils]   Directory test-output/junitreports exists: true
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.HDF5UtilsTest.xml
[Utils]   Directory test-output/junitreports exists: true
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.h5ar.DirectoryIndexUpdaterTest.xml
[Utils]   Directory test-output/junitreports exists: true
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.UnsignedIntUtilsTest.xml
[Utils]   Directory test-output/junitreports exists: true
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.io.HDF5DataSetRandomAccessFileTest.xml
[Utils]   Directory test-output/junitreports exists: true
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.HDF5RoundtripTest.xml
[Utils]   Directory test-output/junitreports exists: true
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.BitSetConversionTest.xml
[Utils]   Directory test-output/junitreports exists: true
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.h5ar.HDF5ArchiverTest.xml
[Utils]   Directory test-output/junitreports exists: true
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.HDF5TimeUnitTest.xml
[Utils]   Directory test-output/junitreports exists: true
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.h5ar.UtilsTest.xml
[Utils]   Directory test-output/junitreports exists: true
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.h5ar.ArchivingStrategyTest.xml
[Utils]   Directory test-output/junitreports exists: true
[Utils] Attempting to create 
test-output/junitreports/TEST-ch.systemsx.cisd.hdf5.MatrixUtilsTest.xml
[Utils]   Directory test-output/junitreports exists: true
[TestNG] Time taken by org.testng.reporters.JUnitReportReporter@6f75e721: 44 ms
[Utils] Attempting to create test-output/testng-failed.xml
[Utils]   Directory test-output exists: true
[Utils] Attempting to create /<>/test-output/All/testng-failed.xml
[Utils]   Directory /<>/test-output/All exists: true
[TestNG] Time taken by [FailedReporter passed=0 failed=0 skipped=0]: 17 ms
[TestNG] Time taken by org.testng.reporters.XMLReporter@41a4555e: 65 ms
[TestNG] Time tak

Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Vincent Lefevre]

On 2016-11-14 15:52:28 +0100, Diederik de Haas wrote:
> On maandag 14 november 2016 15:12:14 CET Vincent Lefevre wrote:
> > aptitude often ignores Recommends. So, you should not rely on it.
> 
> That's an incorrect statement.
> Aptitude, and I think apt too, doesn't automatically install _new_ 
> recommended 
> packages for an already installed package. 
> It does report "The following recommended packages will not be installed" (or 
> sth along those lines). But that's far from ignoring it.

No, I do not always get these reports. Here I didn't even have any
report that a recommended package would be removed: aptitude just
said that  would be removed because they are
no longer used.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#844323: (no subject)

[Breno Leitao]

reassign ghc

After some further debug, I found this is, in fact, a ghc bug and it was
fixed in version 8.0.2, as showed in:

https://ghc.haskell.org/trac/ghc/ticket/12621

Processed (with 1 error): forcibly merging 844333 844186

[Debian Bug Tracking System]

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

> forcemerge 844333 844186
Bug #844333 [node-iconv-lite] node-iconv-lite: Source doesn't include required 
directories
Unable to merge bugs because:
package of #844186 is 'wnpp' not 'node-iconv-lite'
Failed to forcibly merge 844333: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#830984: marked as done (ball: FTBFS: test suite errors)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 15:49:08 +
with message-id 
and subject line Bug#830984: fixed in ball 1.4.3~beta1-3
has caused the Debian Bug report #830984,
regarding ball: FTBFS: test suite errors
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.)


-- 
830984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ball
Version: 1.4.3~beta1-1
Severity: serious

Your package failed to build on most architectures with test suite errors.

Build logs at

https://buildd.debian.org/status/package.php?p=ball

Emilio
--- End Message ---
--- Begin Message ---
Source: ball
Source-Version: 1.4.3~beta1-3

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

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

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

Debian distribution maintenance software
pp.
Danny Edel  (supplier of updated ball 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, 13 Nov 2016 18:24:33 +0100
Source: ball
Binary: libball1.4-data libball1.4 libball1.4-dev libballview1.4 
libballview1.4-dev python-ball python-ballview ballview libball1.4-doc
Architecture: source amd64 all
Version: 1.4.3~beta1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Danny Edel 
Description:
 ballview   - free molecular modeling and molecular graphics tool
 libball1.4 - Biochemical Algorithms Library
 libball1.4-data - Biochemical Algorithms Library (data files)
 libball1.4-dev - Header files for the Biochemical Algorithms Library
 libball1.4-doc - documentation for the BALL library
 libballview1.4 - Biochemical Algorithms Library, VIEW framework
 libballview1.4-dev - Header files for the VIEW part of the Biochemical 
Algorithms Libr
 python-ball - Python bindings for the Biochemical Algorithms Library
 python-ballview - Python bindings for VIEW-parts of the Biochemical Algorithms 
Libr
Closes: 830984
Changes:
 ball (1.4.3~beta1-3) unstable; urgency=medium
 .
   * Ignore test suite result on non-amd64
 Closes: #830984
Checksums-Sha1:
 b486e6de316c8b79c4e70fa9ba2be1de1e2cc1a8 2973 ball_1.4.3~beta1-3.dsc
 0f9d8da2f6dd0c09d6b851221fc9fa9fbc893877 36256 ball_1.4.3~beta1-3.debian.tar.xz
 82a4ced670e7488b573f266fa396cc9451aaa93f 17512 
ball_1.4.3~beta1-3_20161114T152115z-10b773fd.buildinfo
 1f55f09ab73b265a2a559fb0ecf830fa7a056919 1234496 
ballview-dbgsym_1.4.3~beta1-3_amd64.deb
 2ef107d92215a50008149cf3fbe441629e38f4c1 2518026 
ballview_1.4.3~beta1-3_amd64.deb
 45d7fb14e9c1e55ff25645a1457eb26599068adb 28737310 
libball1.4-data_1.4.3~beta1-3_all.deb
 7c98c8e666df1ffe64ce7b9fd25e715d32dd0e01 63581546 
libball1.4-dbgsym_1.4.3~beta1-3_amd64.deb
 2e9113f1e611c3abbecb0cec3b5648dac74b049b 543042 
libball1.4-dev_1.4.3~beta1-3_amd64.deb
 77bd7c8ae83c31a74cfd1ba4846307ce6d158796 8764398 
libball1.4-doc_1.4.3~beta1-3_all.deb
 1325e9cedd5177873e40a0124cc4d38187c43d16 3236420 
libball1.4_1.4.3~beta1-3_amd64.deb
 20cdf0aa68c008c84983a30dfdf0d0c3e00be3a3 31707168 
libballview1.4-dbgsym_1.4.3~beta1-3_amd64.deb
 38cd295484fc37e7e15ef69829f9855d32764014 152988 
libballview1.4-dev_1.4.3~beta1-3_amd64.deb
 26de501248c1d6e8ddbd9fa10a60d8cc55ea9afa 1440188 
libballview1.4_1.4.3~beta1-3_amd64.deb
 ab046e70d485ff3c9a06de9f639c4090b6876b1f 5736106 
python-ball-dbgsym_1.4.3~beta1-3_amd64.deb
 e974c8040bbd516a19a6c42757e03b027b401c83 886060 
python-ball_1.4.3~beta1-3_amd64.deb
 e8632b5e3dff14fef305e46d6ac49aec1d01af9c 2477562 
python-ballview-dbgsym_1.4.3~beta1-3_amd64.deb
 78040fb6681a72071f0d9c46d6dfdf98d2f0e3d8 226332 
python-ballview_1.4.3~beta1-3_amd64.deb
Checksums-Sha256:
 bb2254aab240b1c5c16a8415bf1aa4c04e95ee07cfd7a7dfc5cbbecd743ce05f 2973 
ball_1.4.3~beta1-3.dsc
 3f5d53aa3b41f2d7838e7f2dd45af2f3b29cca510664080051c096a556cfbd2f 36256 
ball_1.4.3~beta1-3.debian.tar.xz
 d936676484cfafe0c52f4f04f65b2f3b8efe787747bada7c6f31429583100337 17512 
ball_1.4.3~beta1-3_20161114T152115z-10b773fd.buildinfo
 e1113356ffd3b16d8fa13e9d4a3832a86d863b7a69d98ce2dba6c9603aa7b9df 1234496 
ballview-dbgsym_1.4.3~beta1-3_amd64.deb
 dda5ca9cc0a7af5337ee43d72a0fc703a4227ab

Processed (with 1 error): forcibly merging 844333 844186

[Debian Bug Tracking System]

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

> forcemerge 844333 844186
Bug #844333 [node-iconv-lite] node-iconv-lite: Source doesn't include required 
directories
Bug #844186 [node-iconv-lite] RFH: libjs-handlebars -- need help in modifying 
grunt to build libjs-handlebars (and other modules with Gruntfile.js)
Severity set to 'grave' from 'normal'
837467 was blocked by: 844186
837467 was blocking: 837466
Removed blocking bug(s) of 837467: 844186
Failed to forcibly merge 844333: It is nonsensical for a bug to block itself 
(or a merged partner): 844186.

> thanks
Stopping processing here.

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

Bug#828286: Reopen?

[Lance Lassetter]

Could you please reopen this bug?  Or do you see this as an error on my
part?

Lance

Bug#844343: golang-github-pierrec-lz4: FTBFS on armhf (TestCopy crashes)

[Daniel Stender]

Source: golang-github-pierrec-lz4
Version: 0.0~git20151216.222ab1f-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

The build of this package break in the reproducible build environment during the
2nd build on armhf [1]:


=== RUN   TestCopy
SIGQUIT: quit
PC=0x709f8 m=0

goroutine 0 [idle]:
runtime.futex(0x1c48fc, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1dba0, 0x0, 0x0, 0x0, ...)
/usr/lib/go-1.7/src/runtime/sys_linux_arm.s:247 +0x20
runtime.futexsleep(0x1c48fc, 0x0, 0x, 0x)
/usr/lib/go-1.7/src/runtime/os_linux.go:45 +0x68
runtime.notesleep(0x1c48fc)
/usr/lib/go-1.7/src/runtime/lock_futex.go:145 +0xa4
runtime.stopm()
/usr/lib/go-1.7/src/runtime/proc.go:1594 +0x100
runtime.findrunnable(0x1051f400, 0x0)
/usr/lib/go-1.7/src/runtime/proc.go:2021 +0x758
runtime.schedule()
/usr/lib/go-1.7/src/runtime/proc.go:2120 +0x26c
runtime.goexit0(0x117eb770)
/usr/lib/go-1.7/src/runtime/proc.go:2257 +0x1d0
runtime.mcall(0x1c4600)
/usr/lib/go-1.7/src/runtime/asm_arm.s:183 +0x5c

goroutine 1 [chan receive, 3 minutes]:
testing.(*T).Run(0x10588000, 0x14906a, 0x8, 0x15c6f4, 0xa1901)
/usr/lib/go-1.7/src/testing/testing.go:647 +0x324
testing.RunTests.func1(0x10590100)
/usr/lib/go-1.7/src/testing/testing.go:793 +0xb8
testing.tRunner(0x10590100, 0x1053ced4)
/usr/lib/go-1.7/src/testing/testing.go:610 +0xa4
testing.RunTests(0x15c714, 0x1c3120, 0x8, 0x8, 0xa1)
/usr/lib/go-1.7/src/testing/testing.go:799 +0x388
testing.(*M).Run(0x1053cf7c, 0x40)
/usr/lib/go-1.7/src/testing/testing.go:743 +0x8c
main.main()
github.com/pierrec/lz4/_test/_testmain.go:76 +0x118

goroutine 17422 [semacquire]:
sync.runtime_Semacquire(0x10516080)
/usr/lib/go-1.7/src/runtime/sema.go:47 +0x24
sync.(*WaitGroup).Wait(0x10516074)
/usr/lib/go-1.7/src/sync/waitgroup.go:131 +0xc0
github.com/pierrec/lz4.(*Writer).Write(0x10516050, 0x128c, 0x10, 
0x10, 0x0, 0x0, 0x0)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:183
 +0x9b0
github.com/pierrec/lz4.(*Writer).ReadFrom(0x10516050, 0x1b2770, 0x10570128, 
0x20, 0x0, 0x0, 0x0)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:357
 +0x1a0
io.copyBuffer(0x1b2758, 0x10516050, 0x1b2770, 0x10570128, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, ...)
/usr/lib/go-1.7/src/io/io.go:384 +0x124
io.Copy(0x1b2758, 0x10516050, 0x1b2770, 0x10570128, 0x10, 0x148670, 0x0, 0x0)
/usr/lib/go-1.7/src/io/io.go:360 +0x64
github.com/pierrec/lz4_test.TestCopy(0x10588000)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/lz4_test.go:493
 +0x370
testing.tRunner(0x10588000, 0x15c6f4)
/usr/lib/go-1.7/src/testing/testing.go:610 +0xa4
created by testing.(*T).Run
/usr/lib/go-1.7/src/testing/testing.go:646 +0x304

goroutine 25094 [runnable]:
github.com/pierrec/lz4.(*Writer).Write.func1(0x10516050, 0x128c, 0x10, 
0x10)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:120
created by github.com/pierrec/lz4.(*Writer).Write

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:123
 +0xf8

goroutine 25098 [runnable]:
github.com/pierrec/lz4.CompressBlock(0x1298, 0x4, 0x4, 0x112a8000, 
0x4, 0x4, 0x0, 0x4, 0x6fe08, 0x10516074)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/block.go:116
github.com/pierrec/lz4.(*Writer).compressBlock(0x10516050, 0x116ea084)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:238
 +0x310
created by github.com/pierrec/lz4.(*Writer).Write

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:165
 +0x530

goroutine 25097 [runnable]:
github.com/pierrec/lz4.(*Writer).compressBlock(0x10516050, 0x116ea058)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:228
created by github.com/pierrec/lz4.(*Writer).Write

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:165
 +0x530

goroutine 25096 [runnable]:
github.com/pierrec/lz4.(*Writer).compressBlock(0x10516050, 0x116ea02c)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:228
created by github.com/pierrec/lz4.(*Writer).Write

/build/golang-github-

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[殷啟聰]

Control: tags -1 moreinfo

Gradle 3.1 is now uploaded, looks like this bug is fixed?

Processed: Re: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #844021 [libnative-platform-java] libnative-platform-java 0.11-4 is not 
compatible with programs built with 0.10*
Added tag(s) moreinfo.

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

Bug#844323: (no subject)

[Clint Adams]

On Mon, Nov 14, 2016 at 01:34:05PM -0200, Breno Leitao wrote:
> reassign ghc
> 
> After some further debug, I found this is, in fact, a ghc bug and it was
> fixed in version 8.0.2, as showed in:
> 
> https://ghc.haskell.org/trac/ghc/ticket/12621

Great!

Processed (with 3 errors): cloning 828286, retitle -1 to dovecot: Unknown protocol SSLv2, forcibly merging 844271 -1

[Debian Bug Tracking System]

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

> clone 828286 -1
Bug #828286 {Done: Apollon Oikonomopoulos } [src:dovecot] 
dovecot: FTBFS with openssl 1.1.0
Bug 828286 cloned as bug 844345
827061 was blocked by: 828342 828618 828270 828549 828413 828255 828323 828275 
828616 828294 828600 828570 828266 828594 828428 843532 828372 828303 828271 
828485 828344 828343 828249 828602 828361 828497 828613 828262 828417 828265 
828531 828563 828269 828407 828279 828617 828458 828478 828346 843988 828519 
828580 828591 828337 828480 828366 828465 828592 828261 835794 828379 828345 
844254 835799 835786 828538 828456 827068 828334 828601 828311 828385 828241 
828356 828589 828511 828327 828331 828338 828430 828489 828566 828442 808669 
828263 828405 828547 828302 828484 828577 828376 828560 828240 835797 828545 
841635 828347 828340 828491 828583 828268 828289 828487 828281 827076 828572 
828598 828483 828291 828233 822380 828533 828614 828339 828258 828503 828416 
828359 835800 828505 828537 828596 828522 828308 828298 828446 828252 828584 
828526 828409 828351 828504 828412 828326 828515 828297 828535 828468 828391 
828552 828362 835811 828352 828493 828558 828402 828387 828403 828523 828610 
828365 828528 828418 828508 828229 828393 828244 828324 828363 828374 828551 
828313 828576 828599 828290 828384 828479 828437 828397 828335 828234 828473 
828525 828394 828431 828283 828457 828555 828462 828278 828482 828559 828341 
828579 828585 828534 828282 828435 828421 828328 828382 828330 828314 828399 
828434 828378 828280 828388 828127 828543 828312 828476 828235 828604 828541 
828612 828301 828400 828425 828527 828373 812166 828499 828542 828383 828564 
828466 828274 828530 829452 828449 828439 828355 828557 828367 828469 828422 
828490 828257 828590 828607 828242 828358 828495 835785 828237 828321 828597 
828424 828471 828287 828139 828477 828443 828455 828410 828450 828509 828448 
828517 828307 828253 828260 828474 828452 835793 828251 828426 828433 828082 
828396 828322 828595 828228 835585 828556 828245 828375 828536 828349 828259 
828277 837960 828360 828569 828357 809271 828463 828438 828516 835804 828305 
828354 828315 828246 828309 828230 828336 828350 828586 828496 828432 835789 
828390 828429 828615 828510 828608 828420 828453 828486 828512 828256 828441 
828574 835790 828567 828411 828562 828454 828521 828296 828582 828619 828377 
828459 828318 828332 828568 828492 828488 828368 828578 828250 828444 828316 
828502 828546 828427 828540 828501 828544 828539 828389 828514 828381 828467 
828243 828231 828548 828472 828398 828272 828447 828554 828248 828232 828320 
828348 835549 828254 828142 828395 828401 828470 828606 828451 828506 828304 
828445 828238 828392 828550 828300 828573 828292 828460 828288 828524 828620 
836419 828386 828423 828306 828364 835798 828588 828518 828605 828406 828319 
828419 828500 828284 828310 828440 828436 828371 828553 828369 828611 828513 
828286 828529 828494 828507 828293 828532 828561 828481 828329 828498 814600 
828520 828267 828295 828285 828083 828370 828603 828239 828571 828464 828587 
828415 828404 828414 828353 829465 828581 828264 828609 828575 828276 828333 
835796 828317 828380 828593 828273 828565 828325 828461
827061 was not blocking any bugs.
Added blocking bug(s) of 827061: 844345; removed blocking bug(s) of 827061: 
828245, 828479, 829452, 828463, 828317, 828316, 828616, 828252, 828503, 828372, 
828244, 828401, 828518, 828619, 828530, 828237, 828482, 828230, 828595, 828488, 
828302, 844254, 828283, 828436, 843988, 828509, 828233, 828583, 828618, 828490, 
828552, 828506, 828562, 836419, 828493, 828610, 828241, 828142, 828338, 828229, 
828500, 828507, 828519, 828434, 828375, 828385, 828246, 828569, 828487, 828294, 
828443, 828354, 828418, 828388, 828521, 828334, 828402, 828597, 822380, 828355, 
828291, 828259, 828510, 828582, 828399, 828494, 828273, 828466, 828576, 828456, 
828566, 828281, 828472, 828348, 828429, 828378, 828551, 828570, 828228, 828481, 
828376, 828280, 828421, 828312, 828250, 828373, 828303, 828416, 828269, 827076, 
828558, 828451, 828290, 828256, 828442, 828363, 828431, 828403, 828370, 835800, 
828533, 828346, 828331, 828314, 828420, 828565, 835811, 828339, 828393, 828255, 
828271, 828497, 828300, 828238, 828541, 828254, 828428, 828382, 835785, 828465, 
828381, 828243, 828353, 828417, 835549, 828426, 828563, 828460, 828607, 828547, 
828612, 828359, 829465, 828332, 814600, 828531, 828358, 835804, 828535, 828318, 
828580, 828325, 828505, 828608, 828268, 828260, 828430, 828540, 828529, 828352, 
828361, 828349, 828435, 828603, 828305, 828491, 828347, 828379, 828409, 828606, 
828467, 828520, 828422, 828585, 828532, 828411, 828413, 828450, 828555, 828380, 
827068, 828611, 828545, 828319, 828248, 828083, 828323, 828613, 828343, 828326, 
828557, 828282, 828538, 828335, 828474, 828249, 828438, 828313, 828553, 828357, 
828311, 835796, 828498, 828550, 828528, 835797, 828405, 828257, 828389, 828544, 
828377, 828526, 828356, 828286, 828333, 828448, 82825

Bug#828286: Reopen?

[Apollon Oikonomopoulos]

Hi,

On 09:58 Mon 14 Nov , Lance Lassetter wrote:
> Could you please reopen this bug?  Or do you see this as an error on my
> part?

This bug (#828286) tracked the failure of dovecot to be built against 
OpenSSL 1.1. You re-opened the bug by mailing to it, but that's for a 
different (although related) issue.

I'll clone your bug report to a new one and will close #828286 as it 
was. You don't have to do anything on your side.

Regards,
Apollon

Bug#842910: marked as done (ruby-nokogiri: FTBFS: Failure: Nokogiri::XML::TestNode#test_document_compare)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 16:05:18 +
with message-id 
and subject line Bug#842910: fixed in ruby-nokogiri 1.6.8.1-1
has caused the Debian Bug report #842910,
regarding ruby-nokogiri: FTBFS: Failure:   
Nokogiri::XML::TestNode#test_document_compare
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.)


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

Dear Maintainer,

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

  […]

  TestConvertXPath#test_css_class = 0.01 s = .
  TestConvertXPath#test_child_tag = 0.01 s = .
  TestConvertXPath#test_child_tag_equals = 0.01 s = .
  TestConvertXPath#test_css_tags = 0.00 s = .
  TestConvertXPath#test_filter_comment = 0.03 s = .
  TestConvertXPath#test_css_id = 0.01 s = .
  ad hoc node reparenting behavior::#add_child::given a parent node with a 
default and non-default namespace::and a child node with a default namespace 
not matching the parent's default namespace and a namespace matching a parent 
namespace but with a different prefix#test_0001_inserts a node that keeps its 
namespace = 0.00 s = .
  standard node reparenting behavior::#next=::passed a Node::passed a Node in 
the current document#test_0001_unlinks the Node from its previous position = 
0.00 s = .
  standard node reparenting behavior::#next=::passed a Node::passed a Node in 
the current document#test_0003_returns the expected value = 0.00 s = .
  standard node reparenting behavior::#next=::passed a Node::passed a Node in 
the current document#test_0002_inserts the Node in the proper position = 0.00 s 
= .
  ad hoc node reparenting behavior::#add_child::given a parent node with a 
default and non-default namespace::and a child with a namespace matching the 
parent's non-default namespace::set by #namespace=#test_0001_inserts a node 
that inherits the matching parent namespace = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_deprecated_attributes = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_deprecated? = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_optional_attributes = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_implied_start_tag? = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_default_sub_element = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_block? = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_description = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_to_s = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_subelements = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_fetch_element_description = 0.00 
s = .
  Nokogiri::HTML::TestElementDescription#test_required_attributes = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_save_end_tag? = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_empty? = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_implied_end_tag? = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_inline? = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_fetch_nonexistent = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_inspect = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_name = 0.00 s = .
  Nokogiri::HTML::TestElementDescription#test_null_default_sub_element = 0.00 s 
= .
  Nokogiri::XML::TestBuilder#test_root_namespace_default_decl = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_set_encoding = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_builder_no_block = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_with_root = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_raw_xml_append_with_namespaces = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_builder_namespace_part_deux = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_dtd_in_builder_output = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_raw_append = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_specified_namespace_postdeclared = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_specify_namespace = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_raw_xml_append = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_specified_namespace_undeclared = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_square_brackets_set_attributes = 0.00 s = .
  Nokogiri::XML::TestBuilder#test_builder_can_handle_namespace_override = 0.00 
s = .
  Nokogiri::XML::TestBuilder#test_comment = 0.00 s = .
  N

Bug#844333: marked as done (node-iconv-lite: Source doesn't include required directories)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2016 16:05:12 +
with message-id 
and subject line Bug#844333: fixed in node-iconv-lite 0.4.13-2
has caused the Debian Bug report #844333,
regarding node-iconv-lite: Source doesn't include required directories
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.)


-- 
844333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-iconv-lite
Version: 0.4.13-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Directories `encodings` and `generation` are not included in debian package 
archive.
npm2deb skips it as those directories are not mentioned in package.json.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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)

Versions of packages node-iconv-lite depends on:
ii  nodejs  4.6.1~dfsg-1

node-iconv-lite recommends no packages.

node-iconv-lite suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: node-iconv-lite
Source-Version: 0.4.13-2

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-iconv-lite 
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, 14 Nov 2016 21:06:00 +0530
Source: node-iconv-lite
Binary: node-iconv-lite
Architecture: source
Version: 0.4.13-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-iconv-lite - Pure JS character encoding conversion
Closes: 844333
Changes:
 node-iconv-lite (0.4.13-2) unstable; urgency=medium
 .
   * Team upload
   * Install all required files (Closes: #844333)
Checksums-Sha1:
 551d061c6caaafc3cc495a9257773e3795f8b9b4 2069 node-iconv-lite_0.4.13-2.dsc
 4ba1446e297ab8e01ad2b8359bdf41b20651502a 2220 
node-iconv-lite_0.4.13-2.debian.tar.xz
Checksums-Sha256:
 e8bb9c2eed2e5e9d3e359ea8190fc11290df0b30415b6539a2a115c04342c811 2069 
node-iconv-lite_0.4.13-2.dsc
 8b47f0fb51de99157c2282575edba5f675e592a5d5e84e57b00674d16a6e0916 2220 
node-iconv-lite_0.4.13-2.debian.tar.xz
Files:
 4cfb5f55c59bf39b97b736389a3f3e1a 2069 web optional node-iconv-lite_0.4.13-2.dsc
 fb664b6dad3e3abf8774d9bb145034b2 2220 web optional 
node-iconv-lite_0.4.13-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYKdsjAAoJEM4fnGdFEsIq0TcQALJx3OOoggwjb+aysWcsSQco
OZg31eCcaokdXeBjlogW+RTyGsWzPoqflQSwraZ/iH16jAL4TWbnO45m0gNKa0Mc
OE2p4wIRd/AgPojko9bWGI7VxmmPxAXSOWBO29t1tYSEFVmwm4sXkw4uEcRjDltS
RnR9udB8SP7/7H2X8ysljFjAVF//Os8Ynr/ABD1GRcbDKFw3AFSgBpDZBopMGpPz
9XIpKJG9RGe3Ki0a7Xoe29HWfROKy3nQ+GmCpC3YjpbzpMjGdHm5CveYt3P8qd14
mCJeOx4BIqhfeRfKQZAiT9hhg4+679ReJADfFj9vBw6QbDYWlRme5nb5EWzHmhVz
h4yNFsy40NARBVpseOYXtI4V0j20A/IJ150yqL+857nUydzRPb5Ve7USbjr2AXhm
btx1u9BZuEar/QFhKxNQvyLvrQJlx1JVNSeWCYIc+DatLjhYMATFIxFl6V3NFpgk
FO9Hc7mJwxn/qGDTy3kZDFk8LE3020abL7J8341erGmDn5iJx+ESs12AiOtXh3SH
lfGTui73PyBlH3zIvSh/ZuGR95hCT29R7PY8bHmnhwqjkFpwojMORlz8+orXHzhW
gWzQ88E0vqEeTh/FADv7tCcj5uoRcWVSiHE1YXsYZR3msYNgfuAAENz2TMwmg1k/
HOsEJbjsQ14mUs5REpYV
=y8am
-END PGP SIGNATURE End Message ---

Processed: retitle 844345 to dovecot: unknown protocol SSLv2, reassign 844345 to dovecot-core ...

[Debian Bug Tracking System]

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

> retitle 844345 dovecot: unknown protocol SSLv2
Bug #844345 {Done: Apollon Oikonomopoulos } [src:dovecot] 
dovecot: FTBFS with openssl 1.1.0
Changed Bug title to 'dovecot: unknown protocol SSLv2' from 'dovecot: FTBFS 
with openssl 1.1.0'.
> reassign 844345 dovecot-core
Bug #844345 {Done: Apollon Oikonomopoulos } [src:dovecot] 
dovecot: unknown protocol SSLv2
Bug reassigned from package 'src:dovecot' to 'dovecot-core'.
No longer marked as found in versions dovecot/1:2.2.26.0-3 and dovecot/2.2.24-1.
No longer marked as fixed in versions dovecot/1:2.2.26.0-1.
> forcemerge 844271 844345
Bug #844271 [dovecot-core] imap-login: Fatal: Invalid ssl_protocols setting: 
Unknown protocol 'SSLv2'
Bug #844311 [dovecot-core] dovecot-core: Invalid ssl_protocols setting: Unknown 
protocol 'SSLv2'
Bug #844271 [dovecot-core] imap-login: Fatal: Invalid ssl_protocols setting: 
Unknown protocol 'SSLv2'
Added tag(s) sid, fixed-upstream, and stretch.
Added tag(s) fixed-upstream, sid, and stretch.
Bug #844345 {Done: Apollon Oikonomopoulos } [dovecot-core] 
dovecot: unknown protocol SSLv2
Severity set to 'important' from 'serious'
827061 was blocked by: 844345
827061 was not blocking any bugs.
Removed blocking bug(s) of 827061: 844345
Bug reopened
Ignoring request to alter fixed versions of bug #844345 to the same values 
previously set
Marked as found in versions dovecot/1:2.2.26.0-3.
Added tag(s) upstream.
Bug #844311 [dovecot-core] dovecot-core: Invalid ssl_protocols setting: Unknown 
protocol 'SSLv2'
Merged 844271 844311 844345
> thanks
Stopping processing here.

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