Bug#848307: gdb-doc has no binaries on any arch

[Sven Joachim]

Source: gdb-doc
Version: 7.12-1
Severity: serious

The latest upload of gdb-doc included only the source, but the
autobuilders are not allowed to build the binary package because there
is no XS-Autobuild field in debian/control.

And because of #825398 the binary package has already been removed from
unstable, so you will have to build and upload it. :-(

Bug#842675: Fix, NMU to DELAYED/5

[Hilko Bengen]

Hi,

here is a set of patches that I intend to NMU to DELAYED/5 later. I have
changed the .symbols file to use C++ name demangling and added some
optional symbols that seem to come directly from the Qt library.

I have also taken the liberty to add a missing dependency on lsb-base
which was flagged as an error by Lintian.

Cheers,
-Hilko
>From 94e74966b47a28e0753c75311d7073d9763ffc25 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Wed, 14 Dec 2016 17:46:21 +0100
Subject: [PATCH 1/4] Use demangled symbols

---
 debian/liblightdm-qt-3-0.symbols | 260 ++-
 1 file changed, 118 insertions(+), 142 deletions(-)

diff --git a/debian/liblightdm-qt-3-0.symbols b/debian/liblightdm-qt-3-0.symbols
index a1cd79c..3ceea6a 100644
--- a/debian/liblightdm-qt-3-0.symbols
+++ b/debian/liblightdm-qt-3-0.symbols
@@ -1,143 +1,119 @@
 liblightdm-qt-3.so.0 liblightdm-qt-3-0 #MINVER#
- _ZN10QDBusErrorD1Ev@Base 1.8.7
- _ZN10QDBusErrorD2Ev@Base 1.8.7
- _ZN10QDBusReplyI7QStringED1Ev@Base 1.8.7
- _ZN10QDBusReplyI7QStringED2Ev@Base 1.8.7
- _ZN11SessionItemD1Ev@Base 1.8.7
- _ZN11SessionItemD2Ev@Base 1.8.7
- _ZN20SessionsModelPrivate12loadSessionsEN8QLightDM13SessionsModel11SessionTypeE@Base 1.8.7
- _ZN20SessionsModelPrivateC1EPN8QLightDM13SessionsModelE@Base 1.8.7
- _ZN20SessionsModelPrivateC2EPN8QLightDM13SessionsModelE@Base 1.8.7
- _ZN5QHashIi10QByteArrayE11deleteNode2EPN9QHashData4NodeE@Base 1.8.7
- _ZN5QHashIi10QByteArrayE13detach_helperEv@Base 1.8.7
- _ZN5QHashIi10QByteArrayE13duplicateNodeEPN9QHashData4NodeEPv@Base 1.8.7
- _ZN5QListI11SessionItemE18detach_helper_growEii@Base 1.8.7
- _ZN5QListI11SessionItemE6appendERKS0_@Base 1.8.7
- _ZN5QListI8UserItemE13detach_helperEi@Base 1.8.7
- _ZN5QListI8UserItemE18detach_helper_growEii@Base 1.8.7
- _ZN5QListI8UserItemE6appendERKS0_@Base 1.8.7
- _ZN6QDebugD1Ev@Base 1.8.7
- _ZN6QDebugD2Ev@Base 1.8.7
- _ZN8QLightDM10UsersModel11qt_metacallEN11QMetaObject4CallEiPPv@Base 1.8.7
- _ZN8QLightDM10UsersModel11qt_metacastEPKc@Base 1.8.7
- _ZN8QLightDM10UsersModel16staticMetaObjectE@Base 1.8.7
- _ZN8QLightDM10UsersModelC1EP7QObject@Base 1.8.7
- _ZN8QLightDM10UsersModelC2EP7QObject@Base 1.8.7
- _ZN8QLightDM10UsersModelD0Ev@Base 1.8.7
- _ZN8QLightDM10UsersModelD1Ev@Base 1.8.7
- _ZN8QLightDM10UsersModelD2Ev@Base 1.8.7
- _ZN8QLightDM13SessionsModel11qt_metacallEN11QMetaObject4CallEiPPv@Base 1.8.7
- _ZN8QLightDM13SessionsModel11qt_metacastEPKc@Base 1.8.7
- _ZN8QLightDM13SessionsModel16staticMetaObjectE@Base 1.8.7
- _ZN8QLightDM13SessionsModelC1ENS0_11SessionTypeEP7QObject@Base 1.8.7
- _ZN8QLightDM13SessionsModelC1EP7QObject@Base 1.8.7
- _ZN8QLightDM13SessionsModelC2ENS0_11SessionTypeEP7QObject@Base 1.8.7
- _ZN8QLightDM13SessionsModelC2EP7QObject@Base 1.8.7
- _ZN8QLightDM13SessionsModelD0Ev@Base 1.8.7
- _ZN8QLightDM13SessionsModelD1Ev@Base 1.8.7
- _ZN8QLightDM13SessionsModelD2Ev@Base 1.8.7
- _ZN8QLightDM14GreeterPrivate13cb_showPromptEP14LightDMGreeterPKc17LightDMPromptTypePv@Base 1.8.7
- _ZN8QLightDM14GreeterPrivate14cb_showMessageEP14LightDMGreeterPKc18LightDMMessageTypePv@Base 1.8.7
- _ZN8QLightDM14GreeterPrivate19cb_autoLoginExpiredEP14LightDMGreeterPv@Base 1.8.7
- _ZN8QLightDM14GreeterPrivate25cb_authenticationCompleteEP14LightDMGreeterPv@Base 1.8.7
- _ZN8QLightDM14GreeterPrivate7cb_idleEP14LightDMGreeterPv@Base 1.12.2
- _ZN8QLightDM14GreeterPrivate8cb_resetEP14LightDMGreeterPv@Base 1.12.2
- _ZN8QLightDM14GreeterPrivateC1EPNS_7GreeterE@Base 1.8.7
- _ZN8QLightDM14GreeterPrivateC2EPNS_7GreeterE@Base 1.8.7
- _ZN8QLightDM14PowerInterface10canRestartEv@Base 1.8.7
- _ZN8QLightDM14PowerInterface10canSuspendEv@Base 1.8.7
- _ZN8QLightDM14PowerInterface11canShutdownEv@Base 1.8.7
- _ZN8QLightDM14PowerInterface11qt_metacallEN11QMetaObject4CallEiPPv@Base 1.8.7
- _ZN8QLightDM14PowerInterface11qt_metacastEPKc@Base 1.8.7
- _ZN8QLightDM14PowerInterface12canHibernateEv@Base 1.8.7
- _ZN8QLightDM14PowerInterface16staticMetaObjectE@Base 1.8.7
- _ZN8QLightDM14PowerInterface21PowerInterfacePrivateC1Ev@Base 1.8.7
- _ZN8QLightDM14PowerInterface21PowerInterfacePrivateC2Ev@Base 1.8.7
- _ZN8QLightDM14PowerInterface7restartEv@Base 1.8.7
- _ZN8QLightDM14PowerInterface7suspendEv@Base 1.8.7
- _ZN8QLightDM14PowerInterface8shutdownEv@Base 1.8.7
- _ZN8QLightDM14PowerInterface9hibernateEv@Base 1.8.7
- _ZN8QLightDM14PowerInterfaceC1EP7QObject@Base 1.8.7
- _ZN8QLightDM14PowerInterfaceC2EP7QObject@Base 1.8.7
- _ZN8QLightDM14PowerInterfaceD0Ev@Base 1.8.7
- _ZN8QLightDM14PowerInterfaceD1Ev@Base 1.8.7
- _ZN8QLightDM14PowerInterfaceD2Ev@Base 1.8.7
- _ZN8QLightDM17UsersModelPrivate12cb_userAddedEP15LightDMUserListP11LightDMUserPv@Base 1.8.7
- _ZN8QLightDM17UsersModelPrivate14cb_userChangedEP15LightDMUserListP11LightDMUserPv@Base 1.8.7
- _ZN8QLightDM17UsersModelPrivate14cb_userRemovedEP15LightDMUserListP11LightDMUserPv@Base 1.8.7
- _ZN8QLightDM17UsersModelPrivate9loadUsersEv@Base 1.8.7
- _ZN8QLightDM17UsersModelPrivateC1EPNS_10UsersModelE@Base 1.8.7
- 

Bug#845871: marked as done (lua-dbi: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Fri, 16 Dec 2016 05:19:06 +
with message-id 
and subject line Bug#845871: fixed in lua-dbi 0.5.hg5ba1dd988961-4
has caused the Debian Bug report #845871,
regarding lua-dbi: switch to build depend on the metapackage 
default-libmysqlclient-dev
to be marked as done.

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

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


-- 
845871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lua-dbi
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: lua-dbi
Source-Version: 0.5.hg5ba1dd988961-4

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

Debian distribution maintenance software
pp.
Mathieu Parent  (supplier of updated lua-dbi 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: Fri, 16 Dec 2016 04:46:14 +0100
Source: lua-dbi
Binary: lua-dbi-common lua-dbi-sqlite3 lua-dbi-sqlite3-dev lua-dbi-mysql 
lua-dbi-mysql-dev lua-dbi-postgresql lua-dbi-postgresql-dev lua-dbi-mysql-dbg 
lua-dbi-postgresql-dbg lua-dbi-sqlite3-dbg
Architecture: source all amd64
Version: 0.5.hg5ba1dd988961-4
Distribution: unstable
Urgency: medium
Maintainer: Enrico Tassi 
Changed-By: Mathieu Parent 
Description:
 lua-dbi-common - DBI library for the Lua language, common files
 lua-dbi-mysql - DBI library for the Lua language, MySQL backend
 lua-dbi-mysql-dbg - DBI library for the Lua language, MySQL backend debug 
symbols
 lua-dbi-mysql-dev - DBI library for the Lua language, MySQL development files
 lua-dbi-postgresql - DBI library for the Lua language, PostgreSQL backend
 lua-dbi-postgresql-dbg - DBI library for the Lua language, PostgreSQL backend 
debug symbol
 lua-dbi-postgresql-dev - DBI library for the Lua language, PostgreSQL 
development files
 lua-dbi-sqlite3 - DBI library for the Lua language, sqlite3 backend
 lua-dbi-sqlite3-dbg - DBI library for the Lua language, sqlite3 backend debug 
symbols
 lua-dbi-sqlite3-dev - DBI library for the Lua language, sqlite3 development 
files
Closes: 845871
Changes:
 lua-dbi (0.5.hg5ba1dd988961-4) unstable; urgency=medium
 .
   * Team upload
   * Replace Build-Depends: libmysqlclient-dev by default-libmysqlclient-dev
 (Closes: #845871)
Checksums-Sha1:
 53641cf4b6a48464acc5beb1c7e0611e3d1dafff 2640 lua-dbi_0.5.hg5ba1dd988961-4.dsc
 5d98ac5719697cc28d1a3354c6f2e05190d22df4 3708 
lua-dbi_0.5.hg5ba1dd988961-4.debian.tar.xz
 1198d977749f8611ace66a3c1d15be8276ef9cda 3462 
lua-dbi-common_0.5.hg5ba1dd988961-4_all.deb
 9c25949a5512ea57b16c379f157425451dd19133 24148 
lua-dbi-mysql-dbg_0.5.hg5ba1dd988961-4_amd64.deb
 7812df4c759609f4b6c2c1df0fa34910e6f8e43e 9420 
lua-dbi-mysql-dev_0.5.hg5ba1dd988961-4_amd64.deb
 deeb33471ecf7eb8c31756cda887b903e822629b 9844 
lua-dbi-mysql_0.5.hg5ba1dd988961-4_amd64.deb
 a291c18f07bb4d691af93cada75aac9a942aed87 18664 
lua-dbi-postgresql-dbg_0.5.hg5ba1dd988961-4_amd64.deb
 bf013e52f9cbecdc19865e3331fa8fd96d7480f6 8958 
lua-dbi-postgresql-dev_0.5.hg5ba1dd988961-4_amd64.deb
 738abd1c89c6bbf8d4c9206e8f08248195297c23 9242 
lua-dbi-postgresql_0.5.hg5ba1dd988961-4_amd64.deb
 99b152a8ac1f5781f4f3ab1c0bab6d5cce384a73 16794 
lua-dbi-sqlite3-dbg_0.5.hg5ba1dd988961-4_amd64.deb
 

Bug#847227: marked as done (emdebian-archive-keyring: fails to install: post-installation script returned error exit status 2)

[Debian Bug Tracking System]

Your message dated Fri, 16 Dec 2016 05:18:50 +
with message-id 
and subject line Bug#847227: fixed in emdebian-archive-keyring 2.2
has caused the Debian Bug report #847227,
regarding emdebian-archive-keyring: fails to install: post-installation script 
returned error exit status 2
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.)


-- 
847227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emdebian-archive-keyring
Version: 2.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package emdebian-archive-keyring.
  (Reading database ... 
(Reading database ... 4537 files and directories currently installed.)
  Preparing to unpack .../emdebian-archive-keyring_2.1_all.deb ...
  Unpacking emdebian-archive-keyring (2.1) ...
  Setting up emdebian-archive-keyring (2.1) ...
  Warning: apt-key should not be used in scripts (called from postinst 
maintainerscript of the package emdebian-archive-keyring)
  gpg: no valid OpenPGP data found.
  dpkg: error processing package emdebian-archive-keyring (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   emdebian-archive-keyring


cheers,

Andreas


emdebian-archive-keyring_2.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: emdebian-archive-keyring
Source-Version: 2.2

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

Debian distribution maintenance software
pp.
Wookey  (supplier of updated emdebian-archive-keyring 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Dec 2016 03:37:37 +
Source: emdebian-archive-keyring
Binary: emdebian-archive-keyring emdebian-archive-keyring-udeb
Architecture: source all
Version: 2.2
Distribution: unstable
Urgency: medium
Maintainer: Wookey 
Changed-By: Wookey 
Description:
 emdebian-archive-keyring - GnuPG archive keys for the emdebian repository
 emdebian-archive-keyring-udeb - GnuPG keys of the Emdebian archive - udeb 
(udeb)
Closes: 796548 832356 847136 847227
Changes:
 emdebian-archive-keyring (2.2) unstable; urgency=medium
 .
   * Fix priority (Closes: #796548)
   * Update for gnupg2 compatibility (Closes: #847136, #847227)
   * Cleanup (purge) without relying on gnupg (Closes: #832356)
   * Switch to dh from cdbs
Checksums-Sha1:
 bdf99cc5f012ad9b2fa96367131726038d0bc08d 1809 emdebian-archive-keyring_2.2.dsc
 a9af90aff9a4c6bef48756c1567b90e7104c597c 4608 
emdebian-archive-keyring_2.2.tar.gz
 042adea2b2852db1a5f97110257b0ba7cefd3775 2568 
emdebian-archive-keyring-udeb_2.2_all.udeb
 22271ce776626433856a87c38087724c6a1d15b0 4770 
emdebian-archive-keyring_2.2_all.deb
 7f7150585780ce108031e5e8dfcb0ad6399b48e3 5169 
emdebian-archive-keyring_2.2_amd64.buildinfo
Checksums-Sha256:
 40f92499b3bcafa98e06e0181c58c2ce3477deb783daf87317816f5f8acf05c5 1809 
emdebian-archive-keyring_2.2.dsc
 fe040d195a8321b3164188cbe03002026207b55f04d6d24ecb20934bf3893259 4608 
emdebian-archive-keyring_2.2.tar.gz
 8ef58acca3d574dbd055cc99dc3a4e7128faae419ad9812bc3a451d139ed1de1 2568 
emdebian-archive-keyring-udeb_2.2_all.udeb
 f94891f46e05c25343f49a09be21ba7d370aa32c3110c8cd86872b6e2131be20 4770 
emdebian-archive-keyring_2.2_all.deb
 a8174f1f2f968b63a00d8eab2b8b757b89611812a1813f9dba6343b4c220da43 5169 
emdebian-archive-keyring_2.2_amd64.buildinfo
Files:
 ebe7c48f2dd51d753a68825ba6fc9955 1809 utils extra 
emdebian-archive-keyring_2.2.dsc
 cfcb9b50b4e94b9eed5f4a852ea221df 4608 utils extra 
emdebian-archive-keyring_2.2.tar.gz
 1249d94b4216d92c76c4dfb23fe01e39 2568 debian-installer 

Bug#845872: marked as done (lua-sql: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Fri, 16 Dec 2016 05:04:32 +
with message-id 
and subject line Bug#845872: fixed in lua-sql 2.3.0-5
has caused the Debian Bug report #845872,
regarding lua-sql: switch to build depend on the metapackage 
default-libmysqlclient-dev
to be marked as done.

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

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


-- 
845872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lua-sql
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: lua-sql
Source-Version: 2.3.0-5

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

Debian distribution maintenance software
pp.
Mathieu Parent  (supplier of updated lua-sql 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: Fri, 16 Dec 2016 05:13:42 +0100
Source: lua-sql
Binary: lua-sql-sqlite3 lua-sql-sqlite3-dev lua-sql-postgres 
lua-sql-postgres-dev lua-sql-mysql lua-sql-mysql-dev lua-sql-doc
Architecture: source all amd64
Version: 2.3.0-5
Distribution: unstable
Urgency: medium
Maintainer: Enrico Tassi 
Changed-By: Mathieu Parent 
Description:
 lua-sql-doc - luasql documentation
 lua-sql-mysql - luasql library for the Lua language
 lua-sql-mysql-dev - luasql development files for the Lua language
 lua-sql-postgres - luasql library for the Lua language
 lua-sql-postgres-dev - luasql development files for the Lua language
 lua-sql-sqlite3 - luasql library for the Lua language
 lua-sql-sqlite3-dev - luasql development files for the Lua language
Closes: 845872
Changes:
 lua-sql (2.3.0-5) unstable; urgency=medium
 .
   * Team upload
   * Replace Build-Depends: libmysqlclient-dev by default-libmysqlclient-dev
 (Closes: #845872)
   * Replace Pre-Depends: multiarch-support by ${misc:Pre-Depends}
Checksums-Sha1:
 d1e7f6a2be7a33c99e93d8b34f872e63cec86e75 2329 lua-sql_2.3.0-5.dsc
 935472a3260b7d38199947f7f42cf577c91798c0 3772 lua-sql_2.3.0-5.debian.tar.xz
 9e9ea0464bcb1cf472a4e863e913398aa9b3ee43 25210 lua-sql-doc_2.3.0-5_all.deb
 db32cabe74094affdb8bc5754a71d7108978dd66 32002 
lua-sql-mysql-dbgsym_2.3.0-5_amd64.deb
 9fc750cf84b961f80ff2845b98fe6d1d2c727419 9762 
lua-sql-mysql-dev_2.3.0-5_amd64.deb
 ccefd0ea620cfc02336d72e6bae11338a4d19f41 11164 lua-sql-mysql_2.3.0-5_amd64.deb
 04decc4ff9876c6a7b66272a9134b65dc060dff2 27276 
lua-sql-postgres-dbgsym_2.3.0-5_amd64.deb
 8898000ecf504d2f4d9b74ba348ccd1161c777df 9852 
lua-sql-postgres-dev_2.3.0-5_amd64.deb
 618883796717124dabe082aa4580b8b34b72df4f 11204 
lua-sql-postgres_2.3.0-5_amd64.deb
 a3440c61fc6920381d539347afa154d1c1f030fb 24590 
lua-sql-sqlite3-dbgsym_2.3.0-5_amd64.deb
 fa618a8aca0d76ef450b5e35fe839e416f12cc24 9856 
lua-sql-sqlite3-dev_2.3.0-5_amd64.deb
 9b907424c4533afbfd1b37ad3d233fae37001a49 11166 
lua-sql-sqlite3_2.3.0-5_amd64.deb
 14706b503fcaaba04fa219e3e9179a0b668e21b3 8696 lua-sql_2.3.0-5_amd64.buildinfo
Checksums-Sha256:
 a1f52229b7a139b4805c311affce193040b5f00cf63dba956f93c42ba059a80f 2329 
lua-sql_2.3.0-5.dsc
 0480ffc54c0d43ab39eb4a931ca5ab8e1eec3de18d58b4833bab418def0a6826 3772 
lua-sql_2.3.0-5.debian.tar.xz
 c6113d693dcebaec9f3d2c0536f3cdd2c2c55a6a39edbee588e5338fcd50bddf 25210 
lua-sql-doc_2.3.0-5_all.deb
 

Processed: fixed 832908 in 1:3.2.11-1

[Debian Bug Tracking System]

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

> fixed 832908 1:3.2.11-1
Bug #832908 {Done: Laszlo Boszormenyi (GCS) } 
[mongodb-clients] mongodb: CVE-2016-6494: world-readable .dbshell history file
Marked as fixed in versions mongodb/1:3.2.11-1.
> thanks
Stopping processing here.

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

Processed: closing 796331

[Debian Bug Tracking System]

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

> #package working correctly
> close 796331
Bug #796331 [emdebian-archive-keyring] emdebian-archive-keyring: The following 
signatures were invalid: REVKEYSIG B5B7720097BB3B58
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#796331: closing 796331

[Wookey]

#package working correctly
close 796331 
thanks
-- 
Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/

Processed: Re: libopenmpi2: broken SONAME links

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.0.2~git.20161225-5
Bug #847806 {Done: Alastair McKinstry } [libopenmpi2] 
libopenmpi2: broken SONAME links
Marked as found in versions openmpi/2.0.2~git.20161225-5; no longer marked as 
fixed in versions openmpi/2.0.2~git.20161225-5 and reopened.

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

Bug#847806: libopenmpi2: broken SONAME links

[Andreas Beckmann]

Followup-For: Bug #847806
Control: found -1 2.0.2~git.20161225-5

This is not yet fixed. This is not a duplicate of #837525.


Andreas

Bug#828606: xmlsec1: diff for NMU version 1.2.23-0.1

[John Belmonte]

Looks good, thank you Sebastian.

On Thu, Dec 15, 2016 at 12:27 PM, Sebastian Andrzej Siewior <
sebast...@breakpoint.cc> wrote:

> Control: tags 828606 + patch
> Control: tags 828606 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for xmlsec1 (versioned as 1.2.23-0.1) and
> uploaded it to DELAYED/4. Please feel free to tell me if I
> should delay it longer.
> I replaced the orig tar archive from 1.2.20 to 1.2.23 and dropped the
> patches since they are applied upstream. The OpenSSL 1.1.0 support is
> already part of this release so this comes for free.
>
> Regards.
> Sebastian
>

Bug#848299: icedove crashes with SIGPIPE in libc's send.c

[Mirko Vogt]

Package: icedove
Version: 1:45.4.0-1
Severity: grave
Justification: renders package unusable

One of icedove's threads randomly(TM) crashes with SIGPIPE in libc's send.c

This can happen shortly after being started or after running for a
couple of hours. No direct trigger identified so far.

Output of gdb:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/icedove'.
Program terminated with signal SIGPIPE, Broken pipe.
#0  0x77bcd65f in __libc_send (fd=67, buf=0x7fffa9834000, n=31,
flags=0) at ../sysdeps/unix/sysv/linux/x86_64/send.c:26
26  ../sysdeps/unix/sysv/linux/x86_64/send.c: No such file or directory.
[Current thread is 1 (Thread 0x7fffe2ffe700 (LWP 28924))]

backtrace for this particular thread:

(gdb) bt
#0  0x77bcd65f in __libc_send (fd=67, buf=0x7fffa9834000, n=31,
flags=0) at ../sysdeps/unix/sysv/linux/x86_64/send.c:26
#1  0x75ea4e4b in ?? () from /usr/lib/x86_64-linux-gnu/libnspr4.so
#2  0x7fffeeca759a in ?? () from /usr/lib/x86_64-linux-gnu/libssl3.so
#3  0x7fffeec9b999 in ?? () from /usr/lib/x86_64-linux-gnu/libssl3.so
#4  0x7fffeec9d694 in ?? () from /usr/lib/x86_64-linux-gnu/libssl3.so
#5  0x7fffeecad9fb in ?? () from /usr/lib/x86_64-linux-gnu/libssl3.so
#6  0x73998afe in ?? () from /usr/lib/icedove/libxul.so
#7  0x73998b86 in ?? () from /usr/lib/icedove/libxul.so
#8  0x722d6fc0 in ?? () from /usr/lib/icedove/libxul.so
#9  0x722db356 in ?? () from /usr/lib/icedove/libxul.so
#10 0x722d8c50 in ?? () from /usr/lib/icedove/libxul.so
#11 0x722d8fdc in ?? () from /usr/lib/icedove/libxul.so
#12 0x722e0cb5 in ?? () from /usr/lib/icedove/libxul.so
#13 0x7225ea53 in ?? () from /usr/lib/icedove/libxul.so
#14 0x72278ae9 in ?? () from /usr/lib/icedove/libxul.so
#15 0x7245be9b in ?? () from /usr/lib/icedove/libxul.so
#16 0x7244bf62 in ?? () from /usr/lib/icedove/libxul.so
#17 0x72260742 in ?? () from /usr/lib/icedove/libxul.so
#18 0x75ea8549 in ?? () from /usr/lib/x86_64-linux-gnu/libnspr4.so
#19 0x77bc4464 in start_thread (arg=0x7fffe2ffe700) at
pthread_create.c:333
#20 0x76e679df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Core dump exists but I'm not keen of publishing it due to included
sensitive data. I'm happy to help debugging though.

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

Kernel: Linux 4.9.0-rc8+ (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 icedove depends on:
ii  debianutils   4.8.1
ii  fontconfig2.11.0-6.7
ii  libasound21.1.2-1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-7
ii  libcairo2 1.14.6-1.1
ii  libdbus-1-3   1.10.14-1
ii  libdbus-glib-1-2  0.108-1
ii  libevent-2.0-52.0.21-stable-2.1
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.2.1-5
ii  libgdk-pixbuf2.0-02.36.0-1
ii  libglib2.0-0  2.50.2-2
ii  libgtk2.0-0   2.24.31-1
ii  libhunspell-1.4-0 1.4.1-2+b1
ii  libicu57  57.1-5
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.26.2-1
ii  libpango-1.0-01.40.3-3
ii  libpangocairo-1.0-0   1.40.3-3
ii  libpangoft2-1.0-0 1.40.3-3
ii  libpixman-1-0 0.34.0-1
ii  libsqlite3-0  3.15.2-1
ii  libstartup-notification0  0.12-4
ii  libstdc++66.2.1-5
ii  libvpx4   1.6.0-3
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.2-1
ii  libxrender1   1:0.9.9-2
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b1
ii  zlib1g1:1.2.8.dfsg-2+b3

Versions of packages icedove recommends:
ii  hunspell-en-us [hunspell-dictionary]  20070829-6
ii  iceowl-extension  1:45.4.0-1

Versions of packages icedove suggests:
pn  apparmor  
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.15~beta1-1

-- no debconf information

Bug#848294: diaspora-installer-mysql: update mysql dependencies for mariadb

[Emilio Pozuelo Monfort]

Package: diaspora-installer-mysql
Version: 0.6.0.0+debian4
Severity: serious

diaspora-installer-mysql depends on mysql-server and libmysqlclient-dev.

Those dependencies should be updated as:

  default-mysql-server | virtual-mysql-server, default-libmysqlclient-dev

as we are making mariadb the default mysql provider.

Thanks,
Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Bug#848293: postgresql-9.6-mysql-fdw: update mysql dependencies for mariadb

[Emilio Pozuelo Monfort]

Package: postgresql-9.6-mysql-fdw
Version: 2.1.2-3
Severity: serious

postgresql-9.6-mysql-fdw depends on libmysqlclient-dev.

That should be updated to:

  default-libmysqlclient-dev

as we are making mariadb the default mysql provider.

Thanks,
Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Bug#845830: cl-sql: switch to build depend on the metapackage default-libmysqlclient-dev

[Emilio Pozuelo Monfort]

Please make sure you also update cl-sql-mysql's runtime dependency on
libmysqlclient-dev to:

  default-libmysqlclient-dev

Thanks,
Emilio

Bug#848288: ruby-em-synchrony: (build-)depends on mysql-{client,server}

[Emilio Pozuelo Monfort]

Package: ruby-em-synchrony
Version: 1.0.5-1
Severity: serious

Your package build-depends on mysql-server. Since we're transitioning to
mariadb as the default mysql provider, you should switch your build
dependency to default-mysql-server | virtual-mysql-server.

Cheers,
Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Bug#847340: marked as done (initramfs-tools: fails to copy DRM modules with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 23:33:34 +
with message-id 
and subject line Bug#847325: fixed in initramfs-tools 0.126
has caused the Debian Bug report #847325,
regarding initramfs-tools: fails to copy DRM modules with plymouth, 
firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
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.)


-- 
847325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.125
Severity: important
Tags: patch

With these package versions:

linux-image-4.9.0-rc8-amd64-unsigned 4.9~rc8-1~exp1
firmware-misc-nonfree 20161130-1
plymouth 0.9.2-3+b1

and plymouth enabled, my initramfs fails to rebuild with exit status 1
from the plymouth hook.

Editing the plymouth hook to "set -x" reveals that two nvidia-related
graphics drivers (gm206 and gm200) both want to include
/lib/firmware/nvidia/gm200/gr/gpcss_bl.bin in the initramfs. The first
one copies successfully, but for the second, copy_file() returns 1,
causing unsuccessful exit from the manual_add_modules() function.

I attach a possible patch.

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 27M Nov 25 22:54 /boot/initrd.img-3.16.0-4-amd64
-rw--- 1 root root 13M Jan 20  2016 /boot/initrd.img-4.3.0-1-amd64.dracut
-rw--- 1 root root 32M Jan 20  2016 
/boot/initrd.img-4.3.0-1-amd64.dracut.full
-rw-r--r-- 1 root root 30M Jan 20  2016 /boot/initrd.img-4.3.0-1-amd64.i-t
-rw-r--r-- 1 root root 33M Nov 25 22:53 /boot/initrd.img-4.7.0-1-amd64
-rw-r--r-- 1 root root 33M Dec  2 16:03 /boot/initrd.img-4.8.0-2-amd64
-rw-r--r-- 1 root root 34M Dec  7 10:53 /boot/initrd.img-4.9.0-rc8-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.9.0-rc8-amd64 root=/dev/mapper/perpetual_ssd-root ro 
rootflags=subvol=@ apparmor=1 security=apparmor net.ifnames=1 quiet splash

-- resume
RESUME=/dev/mapper/perpetual_ssd-swap
-- /proc/filesystems
btrfs
fuseblk
ext3
ext2
ext4
vfat

-- lsmod
Module  Size  Used by
cpuid  16384  0
rfcomm 77824  2
xt_CHECKSUM16384  1
tun28672  1
ctr16384  6
ccm20480  3
nf_conntrack_netbios_ns16384  2
nf_conntrack_broadcast16384  1 nf_conntrack_netbios_ns
xt_CT  16384  2
ipt_MASQUERADE 16384  4
nf_nat_masquerade_ipv416384  1 ipt_MASQUERADE
xt_tcpudp  16384  59
ip6t_rpfilter  16384  1
ip6t_REJECT16384  2
nf_reject_ipv6 16384  1 ip6t_REJECT
ipt_REJECT 16384  4
nf_reject_ipv4 16384  1 ipt_REJECT
xt_conntrack   16384  60
ip_set 45056  0
nfnetlink  16384  1 ip_set
ebtable_broute 16384  1
bridge135168  1 ebtable_broute
stp16384  1 bridge
llc16384  2 bridge,stp
ebtable_nat16384  1
ip6table_mangle16384  1
ip6table_security  16384  1
ip6table_raw   16384  1
ip6table_nat   16384  1
nf_conntrack_ipv6  20480  32
nf_defrag_ipv6 36864  1 nf_conntrack_ipv6
nf_nat_ipv616384  1 ip6table_nat
iptable_mangle 16384  1
iptable_security   16384  1
iptable_raw16384  1
iptable_nat16384  1
nf_conntrack_ipv4  16384  32
nf_defrag_ipv4 16384  1 nf_conntrack_ipv4
nf_nat_ipv416384  1 iptable_nat
nf_nat 28672  3 nf_nat_ipv6,nf_nat_masquerade_ipv4,nf_nat_ipv4
nf_conntrack  114688  10 
nf_conntrack_ipv6,nf_conntrack_ipv4,nf_conntrack_broadcast,nf_conntrack_netbios_ns,xt_CT,nf_nat_ipv6,nf_nat_masquerade_ipv4,xt_conntrack,nf_nat_ipv4,nf_nat
ebtable_filter 16384  1
ebtables   36864  3 ebtable_filter,ebtable_nat,ebtable_broute
ip6table_filter16384  1
ip6_tables 28672  5 
ip6table_mangle,ip6table_filter,ip6table_security,ip6table_raw,ip6table_nat
iptable_filter 16384  1
cpufreq_userspace  16384  0
cpufreq_powersave  16384  0
cpufreq_conservative16384  0
bnep   20480  2
binfmt_misc20480  1
nls_ascii  16384  1
nls_cp437  20480  1
vfat   20480  1
fat69632  1 vfat
ext4  581632  2
jbd2  106496  1 ext4
fscrypto   28672  1 ext4
ecb16384  0
mbcache16384  3 ext4
iTCO_wdt   16384  0

Bug#848287: python-testing.mysqld: (build-)depends on mysql-{client,server}

[Emilio Pozuelo Monfort]

Source: python-testing.mysqld
Version: 1.4.0-1
Severity: serious

Your package (build-)depends on mysql-server/client. Since we're
transitioning to mariadb as the default mysql provider, you should
switch your build dependencies and dependencies to something like:

default-mysql-server | virtual-mysql-server, default-mysql-client | 
virtual-mysql-client

I have seen in your override that you have forwarded this upstream.
I am filing this anyway to keep track of this along with the rest of the
packages.

Cheers,
Emilio

Cheers,
Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Bug#825929: marked as done (initramfs-tools-core - incorrect busybox relations)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 23:33:33 +
with message-id 
and subject line Bug#825929: fixed in initramfs-tools 0.126
has caused the Debian Bug report #825929,
regarding initramfs-tools-core - incorrect busybox relations
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.)


-- 
825929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools-core
Version: 0.125
Severity: serious

Moin

update-initramfs fails if busybox is of a wrong version, however I see
no breaks or conflicts to make sure the correct version is available.

| Setting up linux-image-4.5.0-2-amd64 (4.5.4-1) ...
| /etc/kernel/postinst.d/initramfs-tools:
| update-initramfs: Generating /boot/initrd.img-4.5.0-2-amd64
| E: busybox or busybox-static, version 1:1.22.0-17~ or later, is required but 
not installed
| update-initramfs: failed for /boot/initrd.img-4.5.0-2-amd64 with 1.
| run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
| Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.5.0-2-amd64.postinst line 525.
| dpkg: error processing package linux-image-4.5.0-2-amd64 (--configure):
|  subprocess installed post-installation script returned error exit status 1
| dpkg: dependency problems prevent configuration of linux-image-amd64:
|  linux-image-amd64 depends on linux-image-4.5.0-2-amd64; however:
|   Package linux-image-4.5.0-2-amd64 is not configured yet.
| 
| dpkg: error processing package linux-image-amd64 (--configure):
|  dependency problems - leaving unconfigured

Regards,
Bastian

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

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

Versions of packages initramfs-tools depends on:
ii  initramfs-tools-core  0.125
ii  linux-base4.0

initramfs-tools recommends no packages.

Versions of packages initramfs-tools suggests:
pn  bash-completion  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: initramfs-tools
Source-Version: 0.126

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated initramfs-tools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Dec 2016 22:43:05 +
Source: initramfs-tools
Binary: initramfs-tools initramfs-tools-core
Architecture: source
Version: 0.126
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team 
Changed-By: Ben Hutchings 
Description:
 initramfs-tools - generic modular initramfs generator (automation)
 initramfs-tools-core - generic modular initramfs generator (core tools)
Closes: 822671 824385 825687 825929 829280 845581 847325
Changes:
 initramfs-tools (0.126) unstable; urgency=medium
 .
   [ Ben Hutchings ]
   * [0b2266e] bash-completion: Fix installation of update-initramfs completion
 script.  Thanks to Stephan Suerken .  (Closes: #824385)
   * [7d875ad] Revert "hook-functions: Add detached module signatures if 
present"
   * [b0a5f26] update-initramfs, hooks/resume: Use ischroot command instead of
 our own function
   * [385e3fc] hook-functions: Make copy_file return 0 on creating a link to an
 existing file (Closes: #847325)
   * [82f4bcf] Fix initramfs.conf move to ensure default values are upgraded.
 Thanks to Andreas Beckmann  (Closes: #822671, #825929)
   * [d9f77c1] Remove obsolete bash-completion file on upgrade.
 Thanks to Andreas Beckmann 
   * [4a10868] Remove code that prunes 'broken' symlinks and sometimes /etc/mtab
 (Closes: #845581)

Bug#848289: ruby-riddle: (build-)depends on mysql-{client,server}

[Emilio Pozuelo Monfort]

Package: ruby-riddle
Version: 1.5.12-3
Severity: serious

Your package build-depends on mysql-server. Since we're transitioning to
mariadb as the default mysql provider, you should switch your build
dependency to default-mysql-server | virtual-mysql-server.

Cheers,
Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Bug#822671: marked as done (initramfs-tools: preserves unmodified /etc/initramfs-tools/initramfs.conf on upgrades from jessie)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 23:33:33 +
with message-id 
and subject line Bug#822671: fixed in initramfs-tools 0.126
has caused the Debian Bug report #822671,
regarding initramfs-tools: preserves unmodified 
/etc/initramfs-tools/initramfs.conf on upgrades from jessie
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.)


-- 
822671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.125
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package causes some trouble
with /etc/initramfs-tools/initramfs.conf upon upgrades from jessie:

1m18.3s ERROR: FAIL: debsums reports modifications inside the chroot:
  /etc/initramfs-tools/initramfs.conf

Rerunning the test manually and analyzing the situation lead to this
conclusion:

The initramfs.conf from jessie is always preserved, regardless of whether
it contained user modifications.

This will cause a dpkg modified-conffile prompt the next time an upgrade
to initramfs-tools-core with an updated version of that conffile is
performed. (This is a policy violation if the conffile was not modified
by the admin.)

Taking over conffiles (and modifying them at the same time) is not an
easy task :-) You probably need to do something even more resembling
dpkg-maintscript-helper mv_conffile in your maintainer scripts, quoting
from the manpage:

  Current  implementation:  the preinst checks if the conffile has been
  modified, if yes it's left on place otherwise it's renamed to
  old-conffile.dpkg-remove. On configuration, the postinst removes old-
  conffile.dpkg-remove and renames old-conffile to new-conffile if
  old-conffile is still available. On abort-upgrade/abort-install, the
  postrm renames old-conffile.dpkg-remove  back  to  old-conffile  if
  required.

You currently use .dpkg-backup for the old conffile, but you should
probably use .dpkg-remove instead *if the old conffile was unmodified*.
The postinst should then probably move .dpkg-backup back (as done now),
delete .dpkg-remove. And in the abort-upgrade case, you have two choices
to restore (but only one will exist).

There is probably no easy way to recover systems that have upgraded from
jessie (with pristine initramfs.conf) to stretch. (To avoid unneccessary
future dpkg prompting.)
(Maybe: compare md5sum againt the version shipped in jessie, restore the
conffile from /usr/share/initramfsfoo in case that matches ...)


Andreas
--- End Message ---
--- Begin Message ---
Source: initramfs-tools
Source-Version: 0.126

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated initramfs-tools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Dec 2016 22:43:05 +
Source: initramfs-tools
Binary: initramfs-tools initramfs-tools-core
Architecture: source
Version: 0.126
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team 
Changed-By: Ben Hutchings 
Description:
 initramfs-tools - generic modular initramfs generator (automation)
 initramfs-tools-core - generic modular initramfs generator (core tools)
Closes: 822671 824385 825687 825929 829280 845581 847325
Changes:
 initramfs-tools (0.126) unstable; urgency=medium
 .
   [ Ben Hutchings ]
   * [0b2266e] bash-completion: Fix installation of update-initramfs completion
 script.  Thanks to Stephan Suerken .  (Closes: #824385)
   * [7d875ad] Revert "hook-functions: Add detached module signatures if 
present"
   * [b0a5f26] update-initramfs, hooks/resume: Use ischroot command instead of
 our own function
   * [385e3fc] hook-functions: Make copy_file return 0 on creating a link to an
 existing file (Closes: #847325)
   * [82f4bcf] Fix initramfs.conf move to ensure default 

Bug#845907: ruby-mysql2: switch to build depend on the metapackage default-libmysqlclient-dev

[Emilio Pozuelo Monfort]

Please make sure you also update your mysql-server build-dependency to

  default-mysql-server | virtual-mysql-server

Thanks,
Emilio

Bug#845905: ruby-dataobjects-mysql: switch to build depend on the metapackage default-libmysqlclient-dev

[Emilio Pozuelo Monfort]

Please make sure you also update your mysql-server build-dependency to

  default-mysql-server | virtual-mysql-server

Thanks,
Emilio

Bug#847325: marked as done (Unable to copy symlinks with copy_file)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 23:33:34 +
with message-id 
and subject line Bug#847325: fixed in initramfs-tools 0.126
has caused the Debian Bug report #847325,
regarding Unable to copy symlinks with copy_file
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.)


-- 
847325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools-core
Version: 0.125
Severity: normal
File: /usr/share/initramfs-tools/hook-functions

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

Today, new firmware-misc-nonfree package contains some symlinks:

lrwxrwxrwx 1 root root   26 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_bl.bin -> ../../gm200/gr/fecs_bl.bin
- -rw-r--r-- 1 root root 1968 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_data.bin
lrwxrwxrwx 1 root root   28 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_inst.bin -> ../../gm200/gr/fecs_inst.bin
- -rw-r--r-- 1 root root   76 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_sig.bin
lrwxrwxrwx 1 root root   27 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin -> ../../gm200/gr/gpccs_bl.bin
- -rw-r--r-- 1 root root 2056 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_data.bin
lrwxrwxrwx 1 root root   29 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_inst.bin -> ../../gm200/gr/gpccs_inst.bin
- -rw-r--r-- 1 root root   76 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_sig.bin
lrwxrwxrwx 1 root root   33 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_bundle_init.bin -> 
../../gm200/gr/sw_bundle_init.bin
lrwxrwxrwx 1 root root   25 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_ctx.bin -> ../../gm200/gr/sw_ctx.bin
lrwxrwxrwx 1 root root   33 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_method_init.bin -> 
../../gm200/gr/sw_method_init.bin
lrwxrwxrwx 1 root root   28 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_nonctx.bin -> ../../gm200/gr/sw_nonctx.bin

I have this error on update-initramfs -u -vv:

Adding firmware /lib/firmware/nvidia/gm206/gr/gpccs_data.bin
Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_inst.bin
Adding firmware /usr/lib/firmware/nvidia/gm200/gr/gpccs_inst.bin
Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
Removing /boot/initrd.img-4.8.0-2-amd64.dpkg-bak
update-initramfs: failed for /boot/initrd.img-4.8.0-2-amd64 with 1.

I have traced to this:

+ copy_file firmware /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ local type src target link_target
+ type=firmware
+ src=/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ target=/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ [ -f /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ [ -d /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ [ -e /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ mkdir -p /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr
+ [ -h /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ readlink -f /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ link_target=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
+ [ /usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin != 
/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ [ y = y ]
+ echo Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ ln -rs 
/var/tmp/mkinitramfs_S838WR//usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin 
/var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ src=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
+ target=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
+ [ -e 
/var/tmp/mkinitramfs_S838WR//usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin ]
+ return 1

Maybe the check should also use cmp.

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

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

Versions of packages initramfs-tools-core depends on:
ii  cpio 2.11+dfsg-6
ii  klibc-utils  2.0.4-9
ii  kmod 23-1
ii  udev 232-7

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.22.0-19

Versions of packages initramfs-tools-core suggests:
ii  bash-completion  1:2.1-4.3

- 

Bug#848291: mysql-connector-python: build-depends on mysql-{client,server}

[Emilio Pozuelo Monfort]

Source: mysql-connector-python
Version: 2.1.3-1
Severity: serious

Your package build-depends on mysql-server. Since we're transitioning to
mariadb as the default mysql provider, you should switch your build
dependency to default-mysql-server | virtual-mysql-server.

Cheers,
Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Bug#848290: python-tooz: (build-)depends on mysql-{client,server}

[Emilio Pozuelo Monfort]

Source: python-tooz
Version: 1.40.0-3
Severity: serious

Your package build-depends on mysql-server. Since we're transitioning to
mariadb as the default mysql provider, you should switch your build
dependency to default-mysql-server | virtual-mysql-server.

Cheers,
Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Bug#848285: jackd2: spits verbose output and exits immediately when the client stops sending audio

[Francesco Poli (wintermute)]

Package: jackd2
Version: 1.9.10+20150825git1ed50c92~dfsg-4
Severity: grave
Justification: renders package unusable

Hello and thanks for maintaining jackd2!

After the upgrade

  [UPGRADE] jackd2:amd64 1.9.10+20150825git1ed50c92~dfsg-3 -> 
1.9.10+20150825git1ed50c92~dfsg-4
  [UPGRADE] jackd2-firewire:amd64 1.9.10+20150825git1ed50c92~dfsg-3 -> 
1.9.10+20150825git1ed50c92~dfsg-4
  [UPGRADE] libjack-jackd2-0:amd64 1.9.10+20150825git1ed50c92~dfsg-3 -> 
1.9.10+20150825git1ed50c92~dfsg-4

I experienced a grave bug: as soon as the client (audacious, firefox through
ALSA redirection in ~/.asoundrc, ...) stops sending audio to the jackd
sound server, the latter spits a bunch of output messages and exits
immediately (as if the --temporary option were passed, no!, even worse!).

Steps to reproduce:

  0) run jackd with the following command line:

 $ jackd --realtime -d alsa --device hw:1 --softmode --hwmeter --rate 44100 
&

  1) run, e.g., audacious (configured to use the Jack output plugin)

  2) play some audio: everything seems to work, even though jackd seems
 to have become more verbose than ever, with a long sequence of
 output lines similar to:

 [...]
 Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
 Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
 Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
 Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
 Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
 Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
 [...]

  3) click on the stop button in the audacious interface: jackd spits the
 following output and exits immediately:

 Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
 Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
 Jack: JackRequest::DeactivateClient
 Jack: JackEngine::ClientDeactivate ref = 2 name = audacious
 Jack: JackEngine::PortDisconnect ref = -1 src = 9 dst = 65535
 Jack: JackEngine::PortDisconnect ref = -1 src = 9 dst = 3
 Jack: JackGraphManager::Disconnect port_src = 9 port_dst = 3
 Jack: JackConnectionManager::Disconnect port_src = 9 port_dst = 3
 Jack: JackConnectionManager::Disconnect port_src = 3 port_dst = 9
 Jack: JackConnectionManager::DecConnectionRef: ref1 = 2 ref2 = 0
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::PortDisconnect ref = -1 src = 10 dst = 65535
 Jack: JackEngine::PortDisconnect ref = -1 src = 10 dst = 4
 Jack: JackGraphManager::Disconnect port_src = 10 port_dst = 4
 Jack: JackConnectionManager::Disconnect port_src = 10 port_dst = 4
 Jack: JackConnectionManager::Disconnect port_src = 4 port_dst = 10
 Jack: JackConnectionManager::DirectDisconnect last: ref1 = 2 ref2 = 0
 Jack: JackConnectionManager::DecConnectionRef: ref1 = 2 ref2 = 0
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackConnectionManager::DirectDisconnect last: ref1 = 2 ref2 = 1
 Jack: JackGraphManager::DisconnectRefNum cur_index = 3 ref1 = 2 ref2 = 1
 Jack: JackConnectionManager::DirectDisconnect last: ref1 = 1 ref2 = 2
 Jack: JackGraphManager::DisconnectRefNum cur_index = 3 ref1 = 1 ref2 = 2
 Jack: JackPosixProcessSync::TimedWait time out = 464380
 Jack: JackPosixProcessSync::TimedWait finished delta = 16446.0
 Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
 Jack: JackRequest::Notification
 Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel 
notify = 18
 Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel 
notify = 18
 Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel 
notify = 18
 Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel 
notify = 18
 Jack: JackEngine::ClientNotify: no callback for notification = 4
 Jack: JackEngine::ClientNotify: no callback for notification = 4
 Jack: JackEngine::ClientNotify: no callback for notification = 4
 Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
 Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 

Bug#817645: marked as done (qmc: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 23:03:50 +
with message-id 
and subject line Bug#817645: fixed in qmc 0.94-3.1
has caused the Debian Bug report #817645,
regarding qmc: Removal of debhelper compat 4
to be marked as done.

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

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


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

Hi,

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: qmc
Source-Version: 0.94-3.1

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

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

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

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated qmc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Dec 2016 15:17:57 -0200
Source: qmc
Binary: qmc
Architecture: source
Version: 0.94-3.1
Distribution: unstable
Urgency: medium
Maintainer: Rene Engelhard 
Changed-By: Giovani Augusto Ferreira 
Description:
 qmc- Quine McClusky Simplification Tool
Closes: 817645
Changes:
 qmc (0.94-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update DH level to 10. (Closes: #817645)
   * debian/compat: updated to 10.
   * debian/control:
  - Bumped Standards-Version to 3.9.8.
Checksums-Sha1:
 88656eabef8b0fcd34bfd2a14f44f259bd6c192a 1599 qmc_0.94-3.1.dsc
 ff79b997dacd6664fa602286a8a40ecfd786ec2c 3069 qmc_0.94-3.1.diff.gz
Checksums-Sha256:
 1847521bd194aa7ed8ce3026425da77b037936ff21adb5d65e68b0f1ba0e1562 1599 
qmc_0.94-3.1.dsc
 c73046a540898451aa2f5ef77a08ed8f8af7c540358374bfebb1e09e2ab9c936 3069 
qmc_0.94-3.1.diff.gz
Files:
 1603132ad65e2200255600563be3d905 1599 science optional qmc_0.94-3.1.dsc
 92fc4bba8bc4fc8ab4a09f33562b6634 3069 science optional qmc_0.94-3.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhTG2oACgkQ3mO5xwTr
6e/0whAAla398HLIPs0LeQBxscpSCCrKkU3jRxvHPk6r+iQpgiVx2hmhn8Q4iGUJ
bypi7ak0iLzS9YkFizfEpaOJS4bx7oOfE8CVh4IHyPvWnSXolvpoMWMlwjuU9niV
aQrGPB6zzjnoiD7D3/6taSFtu/6ViZO5H7aHn6Wa6ftxRz3ELS7Baps16Bt8qgO3
VxRIET/4Pj9pnl2hTIMEJDgCuNzPJ/on3+xf+1udkTA4I2UC7joq6mVtXpGMWtuS
Lm/1Lsqxb406hKBPAr0w/22y6LOIarKG/8huuIrtP3dClZfl7bEblsJK42QhG/Sj
Y0fTlfno30aDC8V+sTQgz9hHytiLAvghBpxDV4X3OoCvbGcRtBgFjNb7KP9nKYqU
bM0iTO/mCEJQ/IOCemChO27W7yJlVM+lrGqfnNDam5393EwMpkrFjL295yZymo9M
1kFYMlrWI3eUESCcCYtgabnRGyhEwTlaC7Qc5//IyZN9o6lGl31uubJ7kS0d5YlP
IpIPK6t4nDJoPZK78HHHrj7kVKk1T2XPrs3MzytmLSRsc7HSW7KsO+89WgdL5gWI
iAiaHB4ivqGNYRzpTSkzLcXUjAyKd0XheNcFC11370QU0wb8uPrpdlWK/8tZGL7n
9w+Cj06TQfrHrnVHTFhrdZgvB+U9bqRwSwWqs1diuDL10cWL+FA=
=Ow23
-END PGP SIGNATURE End Message ---

Bug#817471: marked as done (gco: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 22:48:33 +
with message-id 
and subject line Bug#817471: fixed in gco 0.5.0-6.3
has caused the Debian Bug report #817471,
regarding gco: Removal of debhelper compat 4
to be marked as done.

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

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


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

Hi,

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: gco
Source-Version: 0.5.0-6.3

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

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

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

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated gco package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Dec 2016 14:41:40 -0200
Source: gco
Binary: gco
Architecture: source
Version: 0.5.0-6.3
Distribution: unstable
Urgency: medium
Maintainer: Sam Hocevar (Debian packages) 
Changed-By: Giovani Augusto Ferreira 
Description:
 gco- comics organizer
Closes: 817471
Changes:
 gco (0.5.0-6.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update DH level to 10. (Closes: #817471)
   * debian/compat: updated to 10.
   * debian/control:
  - Added the ${misc:Depends} variable to provide the right install
dependencies.
  - Bumped Standards-Version to 3.9.8.
Checksums-Sha1:
 36b81a358ebea41d0c068a028918bbcec77a402f 1716 gco_0.5.0-6.3.dsc
 4ee158f6efd10bb9d21fec3a7ccdaee66a491264 4172 gco_0.5.0-6.3.diff.gz
Checksums-Sha256:
 d067e8ef6cd2d53d36338c44a7ab64989bbc292b03486269376fb02fd5c5a35a 1716 
gco_0.5.0-6.3.dsc
 dc080d314b14abe933f22ddc7ade5f1b6385f1bb31a25f263e74792280e77891 4172 
gco_0.5.0-6.3.diff.gz
Files:
 a1b39ca9f04e1e2633728b4e8c217af6 1716 gnome extra gco_0.5.0-6.3.dsc
 7b2065a84d07fb6578b7cea800898296 4172 gnome extra gco_0.5.0-6.3.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhTGL4ACgkQ3mO5xwTr
6e+UNQ/+LejrKRuVDbFJmhBxg0BwYE3dibFvB97lXBU3M+d4rhJOPE6JGMifbqSj
v3FWbujDruKT4HvWhEs614+nLBa5hH4Q6DPg/Jnr9l3/AxAagu+/tdEsOlCYq5Lo
e1/Q62yIbDkZtaV6UXAikX3KjAx/F7J2Jr+jrrePkKDEy9fCr73U1hyH89T/Aiv+
hYppafILRAYa7ohY0TAAY8WP5thqUL7x8pr76bmuI83dv2MVCBY/VIeUCQ2pOwnv
4pMTovTey1p0GTHhcBIVQartPr6+GZk7TZTzJLbzfpO4h5h5+3pf2Eb2UsYEvfS+
zvj+81bwa77p2mZkyG6SHPQR4bph87RbBpD354u2v3JsBBn0goCUxJiUzfJYgoMa
/g2LRoh2xjU1KnRmrwAZiuPkNrKs8kHMUBhPPjlLaYEObJhohizvaArXdjgOE8IC
seyVhrS5K2tpRccUiA9nh5Gc2os2uw7eYLyhsw7u34pB939Q0fqLL+rUYCQxI5wW
JE6ftsmTSp579gzReVw7O7Tza1aY23DCUEiuso64poLfUKE3s/yF+2e/NafDMpgu
KoPQ9xis71iZ+W5w5Lc2rsQYHfq9CrXFLZqew9gJLNhDWpmezSLxJxWRWbLT2eR4
3kBrjZfHq/AViw/e4aY5cxqxZRIbVXAn0iZrcndnJ8F2AoNQ5E4=
=+gcR
-END PGP SIGNATURE End Message ---

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Bill Blough]

On a whim, I decided to install the Hercules s390 emulator and see if I
could reproduce the problem there.  It's slow (4+ hours to do a build of
xerces) but it appears to work, and the issue shows up there as well.

I started trying to trace down the memory issue in real time, but the
variables I needed to inspect had been optimized out.  As it turns out,
building with reduced/no optimization (I tested both -O1 and -O0) allows
all of the tests to pass except for one (XSValueTest).  Can someone
please confirm this on the porterbox?

Adding

export DEB_BUILD_MAINT_OPTIONS=noopt

to the top of d/rules and rebuilding should do it.

Thanks!

Bug#847812: pysolfc: crash on startup

[Markus Koschany]

Control: severity -1 normal
Control: tags -1 unreproducible

On 12.12.2016 00:21, Ben Hildred wrote:
> Package: pysolfc
> Version: 2.0-4
> Severity: grave
> Justification: renders package unusable
> 
> $  pysolfc
> Traceback (most recent call last):
>   File "/usr/games/pysolfc", line 32, in 
> sys.exit(main(sys.argv))
>   File "/usr/share/games/pysolfc/pysollib/main.py", line 359, in main
> r = pysol_init(app, args)
>   File "/usr/share/games/pysolfc/pysollib/main.py", line 196, in pysol_init
> app.loadImages1()
>   File "/usr/share/games/pysolfc/pysollib/app.py", line 712, in loadImages1
> im = loadImage(fn)
>   File "/usr/share/games/pysolfc/pysollib/tile/tkutil.py", line 276, in
> makeImage
> im = PIL_Image(file)
>   File "/usr/share/games/pysolfc/pysollib/tile/tkutil.py", line 254, in
> __init__
> ImageTk.PhotoImage.__init__(self, image)
>   File "/usr/lib/python2.7/dist-packages/PIL/ImageTk.py", line 120, in 
> __init__
> self.paste(image)
>   File "/usr/lib/python2.7/dist-packages/PIL/ImageTk.py", line 187, in paste
> _imagingtk.tkinit(tk.interpaddr(), 1)
> OverflowError: Python int too large to convert to C long

Hello,

pysolfc works fine in Debian testing. There is no startup error on my
system.

Markus Koschany





signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#847812: pysolfc: crash on startup

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #847812 [pysolfc] pysolfc: crash on startup
Severity set to 'normal' from 'grave'
> tags -1 unreproducible
Bug #847812 [pysolfc] pysolfc: crash on startup
Added tag(s) unreproducible.

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

Bug#817447: marked as done (efax: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 22:34:13 +
with message-id 
and subject line Bug#817447: fixed in efax 1:0.9a-19.1
has caused the Debian Bug report #817447,
regarding efax: Removal of debhelper compat 4
to be marked as done.

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

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


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

Hi,

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: efax
Source-Version: 1:0.9a-19.1

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

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

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

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated efax package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Dec 2016 10:12:26 -0200
Source: efax
Binary: efax
Architecture: source
Version: 1:0.9a-19.1
Distribution: unstable
Urgency: medium
Maintainer: MJ Ray (Debian) 
Changed-By: Giovani Augusto Ferreira 
Description:
 efax   - programs to send and receive fax messages
Closes: 817447
Changes:
 efax (1:0.9a-19.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update DH level to 10. (Closes: #817447)
   * debian/compat: updated to 10.
   * debian/control:
  - Bumped Standards-Version to 3.9.8.
Checksums-Sha1:
 60bf50dffc326973ad8277438d87bde241c48201 1614 efax_0.9a-19.1.dsc
 0126baf702a401f10785a99db9f40755fa096c7f 18698 efax_0.9a-19.1.diff.gz
Checksums-Sha256:
 6ee7598ce125efd7d41010e58c2b3d0f9d9bfac8c67725d78f55edc0cdf36dfe 1614 
efax_0.9a-19.1.dsc
 0582c744382085048049d8eb30f530cf2661c0c0c48d5c4b9b3cd2bd5fb3dc1f 18698 
efax_0.9a-19.1.diff.gz
Files:
 ce17036390170215214cad2d2e4a9352 1614 comm optional efax_0.9a-19.1.dsc
 ec00d9c4905348ae06955f3f50fcce35 18698 comm optional efax_0.9a-19.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhTFL0ACgkQ3mO5xwTr
6e92nhAAl7HtUSH7U1GPOUAu7aDlzCBBUoZw++RenGlTAbJ7va4aSdm3u58M7J0S
8e5xRr3XWEpBEbJaEv0N/QtZQM7hpa4JbKSh36wzHcPvva5+ETJQWIHluXKOUOHc
O8fwRU6rI+mmHqB4Yh2pkfmI14l6ejnehI7KdP6Z7342iNkGVxn9uT6Z9E1XEq24
vNtMBUdLIHlcwBe9in8HJKU45btkAr3k9FwHbF6JM/ZYVW6yFOtODMXAU5p5MUjB
aH+m7LrMzMSVEIR8LJluh2IkEV9u43BSHKKiRa7sSKCGM8xqsyp04axwi5mtu+Cd
UMjHGhP+KCaa9qrFTcb+xMXp2sqSPRgSUgP/IkX/xSjQHRlKZvp8sgy9IOrmIrts
zMfd6Lw+jZge54W7rqIB+DaOWTGm1S5uiY3mIHqfk3PtvVf8nOFuW5QkzDY6PLLm
uTD6UuWA1itDsWyd9I0xGjtvgVEM0oO4l2maZ/UkQ7TccJVprWhAeQb2b1HLT6JR
z6QR4ohpYIuAQsUQ/mlPAA6rGpr7wO5A9gUnxFfJbVhwq76JaUy9gXL3LKQe5IVs
+gzxXO8MtFGX9dadQahXfITk/IQjTVgsuDpuK7fqt+1mDYBujuPtDoAQpv94Bh3r
wsY85GtZaR7UaIXn5moVUdbLgiNoIKQ2fWoB8OKLhIrItJ+BcHs=
=qDbG
-END PGP SIGNATURE End Message ---

Bug#847651: doomsday: Segfaults at startup

[Markus Koschany]

On Sun, 11 Dec 2016 14:13:46 + James Cowgill 
wrote:
> Control: severity -1 grave
> 
> On 10/12/16 10:16, eingousef wrote:
> > Package: doomsday
> > Version: 1.15.8-3
> > Severity: important
> > 
> > Dear Maintainer,
> > 
> > Doomsday just segfaults at startup, producting to following output :
> > 
> > $ doomsday
> > zsh: segmentation fault  doomsday
> 
> I can confirm this. Doomsday is fairly useless at the moment.

That's true. I had a go at this but I can't figure out what is going
wrong here. A rebuild doesn't resolve the issue.



signature.asc
Description: OpenPGP digital signature

Bug#848105: [rt.cpan.org #119235] Bio/Coordinate/Pair.pm removed from BioPerl in version 1.00070001

[Andreas Tille]

On Thu, Dec 15, 2016 at 12:40:01PM -0500, Chris Fields via RT wrote:
> 
> Just a last minute addition, I'm checking in with Lincoln to see if I can 
> attempt a new Bio-Graphics CPAN release (I am apparently still listed as a 
> co-maintainer on PAUSE).

OK, if you would confirm that Bio-Graphics could be brought into a state
that it works with Bio-Coordinate I would reconsider my plan to switch
the Debian packages back to the old series of BioPerl since this would
have been the safest way to ensure that all depenencies in Debian will
work properly. 

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: tagging 811068

[Debian Bug Tracking System]

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

> tags 811068 - patch
Bug #811068 [libgda5] FTBFS: FAIL: check_vcnc: ../../test-driver: line 107: 
77018 Aborted
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Processed: davix: diff for NMU version 0.6.4-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 828279 + patch
Bug #828279 [src:davix] davix: FTBFS with openssl 1.1.0
Added tag(s) patch.
> tags 828279 + pending
Bug #828279 [src:davix] davix: FTBFS with openssl 1.1.0
Added tag(s) pending.

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

Bug#828279: davix: diff for NMU version 0.6.4-1.1

[Sebastian Andrzej Siewior]

Control: tags 828279 + patch
Control: tags 828279 + pending

Dear maintainer,

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

Regards.
diff -Nru davix-0.6.4/debian/changelog davix-0.6.4/debian/changelog
--- davix-0.6.4/debian/changelog	2016-08-25 15:23:58.0 +0200
+++ davix-0.6.4/debian/changelog	2016-12-15 21:40:12.0 +0100
@@ -1,3 +1,11 @@
+davix (0.6.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add OpenSSL 1.1.0 support (Closes: #828279).
+  * Don't install gtest's header files or static libs.
+
+ -- Sebastian Andrzej Siewior   Thu, 15 Dec 2016 21:40:12 +0100
+
 davix (0.6.4-1) unstable; urgency=medium
 
   * Update to version 0.6.4
diff -Nru davix-0.6.4/debian/control davix-0.6.4/debian/control
--- davix-0.6.4/debian/control	2016-08-25 15:23:58.0 +0200
+++ davix-0.6.4/debian/control	2016-12-15 21:40:12.0 +0100
@@ -1,7 +1,7 @@
 Source: davix
 Priority: optional
 Maintainer: Mattias Ellert 
-Build-Depends: debhelper (>= 8.0.0), cmake, libxml2-dev, libssl-dev, gsoap, libboost-system-dev, libboost-thread-dev, libgtest-dev, abi-compliance-checker, pkg-config, doxygen, python-sphinx
+Build-Depends: debhelper (>= 8.0.0), cmake, libxml2-dev, libssl-dev, gsoap, libboost-system-dev, libboost-thread-dev, libgtest-dev, abi-compliance-checker, pkg-config, doxygen, python-sphinx, zlib1g-dev
 Standards-Version: 3.9.8
 Section: net
 Homepage: http://dmc.web.cern.ch/projects/davix/home
diff -Nru davix-0.6.4/debian/patches/0001-DMC-888-16-Add-support-for-openssl-1.1.0.patch davix-0.6.4/debian/patches/0001-DMC-888-16-Add-support-for-openssl-1.1.0.patch
--- davix-0.6.4/debian/patches/0001-DMC-888-16-Add-support-for-openssl-1.1.0.patch	1970-01-01 01:00:00.0 +0100
+++ davix-0.6.4/debian/patches/0001-DMC-888-16-Add-support-for-openssl-1.1.0.patch	2016-12-15 21:38:21.0 +0100
@@ -0,0 +1,145 @@
+From 748698152f2d9c049c31ad7d44d6d2405e540163 Mon Sep 17 00:00:00 2001
+From: Georgios Bitzes 
+Date: Tue, 20 Sep 2016 14:16:38 +0200
+Subject: [PATCH 1/2] DMC-888 #16 Add support for openssl-1.1.0
+
+---
+ deps/libneon/src/ne_openssl.c |   41 +-
+ deps/libneon/src/ne_socket.c  |   11 +++-
+ src/modules/copy/delegation/GRSTx509MakeProxyCert.cpp |2 
+ 3 files changed, 39 insertions(+), 15 deletions(-)
+
+--- a/deps/libneon/src/ne_openssl.c
 b/deps/libneon/src/ne_openssl.c
+@@ -128,12 +128,12 @@ char *ne_ssl_readable_dname(const ne_ssl
+ 	
+ /* Skip commonName or emailAddress except if there is no other
+  * attribute in dname. */
+-	if ((OBJ_cmp(ent->object, cname) && OBJ_cmp(ent->object, email)) ||
++	if ((OBJ_cmp(X509_NAME_ENTRY_get_object(ent), cname) && OBJ_cmp(X509_NAME_ENTRY_get_object(ent), email)) ||
+ (!flag && n == 1)) {
+  	if (flag++)
+ 		ne_buffer_append(dump, ", ", 2);
+ 
+-if (append_dirstring(dump, ent->value))
++ if (append_dirstring(dump, X509_NAME_ENTRY_get_data(ent)))
+ ne_buffer_czappend(dump, "???");
+ 	}
+ }
+@@ -475,6 +475,17 @@ static int check_certificate(ne_session
+ return ret;
+ }
+ 
++#if OPENSSL_VERSION_NUMBER < 0x1010L
++void X509_up_ref(X509 *x)
++{
++x->references++;
++}
++void EVP_PKEY_up_ref(EVP_PKEY *pkey)
++{
++pkey->references++;
++}
++#endif
++
+ /* Duplicate a client certificate, which must be in the decrypted state. */
+ static ne_ssl_client_cert *dup_client_cert(const ne_ssl_client_cert *cc)
+ {
+@@ -488,15 +499,15 @@ static ne_ssl_client_cert *dup_client_ce
+ 
+ populate_cert(>cert, cc->cert.subject);
+ 
+-cc->cert.subject->references++;
+-cc->pkey->references++;
++X509_up_ref(cc->cert.subject);
++EVP_PKEY_up_ref(cc->pkey);
+ 
+ if(cc->cert.chain != NULL){
+ 	int count, n;
+ 	newcc->cert.chain = sk_X509_dup(cc->cert.chain);
+ 	count = sk_X509_num(newcc->cert.chain);
+ 	for (n = 0; n < count; ++n) {
+-	  sk_X509_value(newcc->cert.chain, n)->references++;
++	  X509_up_ref(sk_X509_value(newcc->cert.chain, n));
+ 	}
+  }
+ 
+@@ -540,8 +551,8 @@ static int provide_client_cert(SSL *ssl,
+ 
+ ne_ssl_client_cert *const cc = sess->client_cert;
+ NE_DEBUG(NE_DBG_SSL, "Supplying client certificate.");
+-cc->pkey->references++;
+-cc->cert.subject->references++;
++EVP_PKEY_up_ref(cc->pkey);
++X509_up_ref(cc->cert.subject);
+ *cert = cc->cert.subject;
+ *pkey = cc->pkey;
+ 
+@@ -664,8 +675,14 @@ void ne_ssl_context_destroy(ne_ssl_conte
+  * sufficient. */
+ static int SSL_SESSION_cmp(SSL_SESSION *a, SSL_SESSION *b)
+ {
+-return a->session_id_length == b->session_id_length
+-&& memcmp(a->session_id, b->session_id, a->session_id_length) == 0;
++unsigned int len1;
++

Bug#817523: marked as done (libarray-refelem-perl: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 21:04:40 +
with message-id 
and subject line Bug#827681: fixed in libarray-refelem-perl 1.00+ds-1
has caused the Debian Bug report #827681,
regarding libarray-refelem-perl: Removal of debhelper compat 4
to be marked as done.

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

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


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

Hi,

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: libarray-refelem-perl
Source-Version: 1.00+ds-1

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

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

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated 
libarray-refelem-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Dec 2016 20:22:41 +0100
Source: libarray-refelem-perl
Binary: libarray-refelem-perl
Architecture: source
Version: 1.00+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Christoph Biedl 
Closes: 817523 827681 843358
Description: 
 libarray-refelem-perl - module to set up array elements as aliases
Changes:
 libarray-refelem-perl (1.00+ds-1) unstable; urgency=medium
 .
   * Take package under the pkg-perl umbrella. Closes: #843358
   * Packaging cleanup
 - Use the pristine upstream tarball
 - Declare compliance with policy 3.9.8
 - Raise debhelper compat level to 10. Closes: #817523, #827681
 - Use dh7-style debian/rules
 - Declare source format
 - Update package description
 - Re-write debian/copyright in format 1.0
 - Add watch file
Checksums-Sha1: 
 6f47aff3fe6ff3400a35c4e64c8e3a8bd321f52e 2275 
libarray-refelem-perl_1.00+ds-1.dsc
 ff2966ffb64338176d18c2f3ebb5075954b2949e 2030 
libarray-refelem-perl_1.00+ds.orig.tar.gz
 4066d550c8f04738f2c67fe63d9ec783ccbbf290 1848 
libarray-refelem-perl_1.00+ds-1.debian.tar.xz
Checksums-Sha256: 
 f8c248bf13e5971382899dca9439ec8ee05aa7edd0950a7ae98927ea4a97c13f 2275 
libarray-refelem-perl_1.00+ds-1.dsc
 53b880a3aec043e4e370ce12682b4756de45dd742dab57294fe21a15453cefe3 2030 
libarray-refelem-perl_1.00+ds.orig.tar.gz
 94dfb5db63ab8cddb77bcc2979cb1dcd92694b535d1a9bb9980a4060946ef202 1848 
libarray-refelem-perl_1.00+ds-1.debian.tar.xz
Files: 
 569f4f4584a27c66657afa75352f72e8 2275 perl optional 
libarray-refelem-perl_1.00+ds-1.dsc
 43ff2dd2049258634cb00697198572d1 2030 perl optional 
libarray-refelem-perl_1.00+ds.orig.tar.gz
 392a9204ef29def1ba10476c9e3f067b 1848 perl optional 
libarray-refelem-perl_1.00+ds-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlhTALxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qga4LA//XHhp8bOrlYmZ2EQFYHMc8oZhNoJnHXaBZC8sDPsLZSWVQIrky0e3O8DS
5TYx1MbixDHfl8U/xKufXTnADHq7xJXBWo0iQB1RJs3jKyeaTJTiaYzb0t8AIm04
GctUBz5HkHxf26ylerCbDj6qeVYX6uTh5EpB2T0+S0V5unEvEMxHAq2hl1xyu8eD
ouqO8Al9W0V8pvb66Ig+W/AkXs8HIQS3OONuRjxl9Ox72yb2kS6+0ynnA2dGqjqu
KVZ1ncEFDiCAFExxt/RHE/OWKipWdlRb/Y64QfoYxWeGYac1FxzzmBlsdG90mUq0
knHE1cRDZnrA0rH7TiDr2xm2YYCnt4hm1Ms7qOwJAO0zJFzL6mWMMyx8GFpfV6o5

Bug#827681: marked as done (libarray-refelem-perl: FTBFS: dh_clean: Compatibility levels before 5 are no longer supported (level 4 requested))

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 21:04:40 +
with message-id 
and subject line Bug#817523: fixed in libarray-refelem-perl 1.00+ds-1
has caused the Debian Bug report #817523,
regarding libarray-refelem-perl: FTBFS: dh_clean: Compatibility levels before 5 
are no longer supported (level 4 requested)
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.)


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

libarray-refelem-perl fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  libarray-refelem-perl
   Version:  1.00-1.1
   Build architecture:   amd64
   Date: Sun, 19 Jun 2016 17:12:00 +0100
   Hostname: 0f1b73fd4167
   Uname:Linux 0f1b73fd4167 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 
(2016-05-16) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'libarray-refelem-perl-build-deps' in 
'../libarray-refelem-perl-build-deps_1.00-1.1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package libarray-refelem-perl-build-deps.
  (Reading database ... 23077 files and directories currently installed.)
  Preparing to unpack libarray-refelem-perl-build-deps_1.00-1.1_all.deb ...
  Unpacking libarray-refelem-perl-build-deps (1.00-1.1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up libarray-refelem-perl-build-deps (1.00-1.1) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=0f1b73fd4167
  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.20160619171158.XYg3BdombD.libarray-refelem-perl/libarray-refelem-perl-1.00
  OLDPWD=/home/lamby/temp/cdt.20160619171158.XYg3BdombD.libarray-refelem-perl
  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
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building libarray-refelem-perl 1.00-1.1 on amd64   
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package libarray-refelem-perl
  dpkg-buildpackage: info: source version 1.00-1.1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Niko Tyni 
   dpkg-source --before-build libarray-refelem-perl-1.00
  dpkg-buildpackage: info: host architecture amd64
   fakeroot 

Bug#817523: marked as done (libarray-refelem-perl: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 21:04:40 +
with message-id 
and subject line Bug#817523: fixed in libarray-refelem-perl 1.00+ds-1
has caused the Debian Bug report #817523,
regarding libarray-refelem-perl: Removal of debhelper compat 4
to be marked as done.

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

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


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

Hi,

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: libarray-refelem-perl
Source-Version: 1.00+ds-1

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

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

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated 
libarray-refelem-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Dec 2016 20:22:41 +0100
Source: libarray-refelem-perl
Binary: libarray-refelem-perl
Architecture: source
Version: 1.00+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Christoph Biedl 
Closes: 817523 827681 843358
Description: 
 libarray-refelem-perl - module to set up array elements as aliases
Changes:
 libarray-refelem-perl (1.00+ds-1) unstable; urgency=medium
 .
   * Take package under the pkg-perl umbrella. Closes: #843358
   * Packaging cleanup
 - Use the pristine upstream tarball
 - Declare compliance with policy 3.9.8
 - Raise debhelper compat level to 10. Closes: #817523, #827681
 - Use dh7-style debian/rules
 - Declare source format
 - Update package description
 - Re-write debian/copyright in format 1.0
 - Add watch file
Checksums-Sha1: 
 6f47aff3fe6ff3400a35c4e64c8e3a8bd321f52e 2275 
libarray-refelem-perl_1.00+ds-1.dsc
 ff2966ffb64338176d18c2f3ebb5075954b2949e 2030 
libarray-refelem-perl_1.00+ds.orig.tar.gz
 4066d550c8f04738f2c67fe63d9ec783ccbbf290 1848 
libarray-refelem-perl_1.00+ds-1.debian.tar.xz
Checksums-Sha256: 
 f8c248bf13e5971382899dca9439ec8ee05aa7edd0950a7ae98927ea4a97c13f 2275 
libarray-refelem-perl_1.00+ds-1.dsc
 53b880a3aec043e4e370ce12682b4756de45dd742dab57294fe21a15453cefe3 2030 
libarray-refelem-perl_1.00+ds.orig.tar.gz
 94dfb5db63ab8cddb77bcc2979cb1dcd92694b535d1a9bb9980a4060946ef202 1848 
libarray-refelem-perl_1.00+ds-1.debian.tar.xz
Files: 
 569f4f4584a27c66657afa75352f72e8 2275 perl optional 
libarray-refelem-perl_1.00+ds-1.dsc
 43ff2dd2049258634cb00697198572d1 2030 perl optional 
libarray-refelem-perl_1.00+ds.orig.tar.gz
 392a9204ef29def1ba10476c9e3f067b 1848 perl optional 
libarray-refelem-perl_1.00+ds-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlhTALxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qga4LA//XHhp8bOrlYmZ2EQFYHMc8oZhNoJnHXaBZC8sDPsLZSWVQIrky0e3O8DS
5TYx1MbixDHfl8U/xKufXTnADHq7xJXBWo0iQB1RJs3jKyeaTJTiaYzb0t8AIm04
GctUBz5HkHxf26ylerCbDj6qeVYX6uTh5EpB2T0+S0V5unEvEMxHAq2hl1xyu8eD
ouqO8Al9W0V8pvb66Ig+W/AkXs8HIQS3OONuRjxl9Ox72yb2kS6+0ynnA2dGqjqu
KVZ1ncEFDiCAFExxt/RHE/OWKipWdlRb/Y64QfoYxWeGYac1FxzzmBlsdG90mUq0
knHE1cRDZnrA0rH7TiDr2xm2YYCnt4hm1Ms7qOwJAO0zJFzL6mWMMyx8GFpfV6o5

Bug#827681: marked as done (libarray-refelem-perl: FTBFS: dh_clean: Compatibility levels before 5 are no longer supported (level 4 requested))

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 21:04:40 +
with message-id 
and subject line Bug#827681: fixed in libarray-refelem-perl 1.00+ds-1
has caused the Debian Bug report #827681,
regarding libarray-refelem-perl: FTBFS: dh_clean: Compatibility levels before 5 
are no longer supported (level 4 requested)
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.)


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

libarray-refelem-perl fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  libarray-refelem-perl
   Version:  1.00-1.1
   Build architecture:   amd64
   Date: Sun, 19 Jun 2016 17:12:00 +0100
   Hostname: 0f1b73fd4167
   Uname:Linux 0f1b73fd4167 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 
(2016-05-16) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'libarray-refelem-perl-build-deps' in 
'../libarray-refelem-perl-build-deps_1.00-1.1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package libarray-refelem-perl-build-deps.
  (Reading database ... 23077 files and directories currently installed.)
  Preparing to unpack libarray-refelem-perl-build-deps_1.00-1.1_all.deb ...
  Unpacking libarray-refelem-perl-build-deps (1.00-1.1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up libarray-refelem-perl-build-deps (1.00-1.1) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=0f1b73fd4167
  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.20160619171158.XYg3BdombD.libarray-refelem-perl/libarray-refelem-perl-1.00
  OLDPWD=/home/lamby/temp/cdt.20160619171158.XYg3BdombD.libarray-refelem-perl
  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
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building libarray-refelem-perl 1.00-1.1 on amd64   
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package libarray-refelem-perl
  dpkg-buildpackage: info: source version 1.00-1.1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Niko Tyni 
   dpkg-source --before-build libarray-refelem-perl-1.00
  dpkg-buildpackage: info: host architecture amd64
   fakeroot 

Bug#848272: golang-go-dbus FTBFS in stretch due to missing golang-gocheck-dev

[Adrian Bunk]

Source: golang-go-dbus
Version: 1~bzr20150122-1
Severity: serious
Tags: stretch sid
Control: block -1 by 789991

golang-go-dbus build-depends on golang-gocheck-dev,
which is not in stretch due to #789991

Processed: Re: Bug#774164: libocrad-dev: libocrad.a contains non-reallocatable code

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #774164 [libocrad-dev] libocrad-dev: libocrad.a contains non-reallocatable 
code
Severity set to 'grave' from 'normal'

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

Bug#848271: docbook-defguide FTBFS in stretch due to missing docbook-ebnf

[Adrian Bunk]

Source: docbook-defguide
Version: 2.0.17+svn9912-1
Severity: serious
Tags: stretch sid
Control: block -1 by 817433

node-yargs build-depends on docbook-ebnf,
which is not in stretch due to #817433

Processed: docbook-defguide FTBFS in stretch due to missing docbook-ebnf

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 817433
Bug #848271 [src:docbook-defguide] docbook-defguide FTBFS in stretch due to 
missing docbook-ebnf
848271 was not blocked by any bugs.
848271 was not blocking any bugs.
Added blocking bug(s) of 848271: 817433

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

Processed: golang-go-dbus FTBFS in stretch due to missing golang-gocheck-dev

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 789991
Bug #848272 [src:golang-go-dbus] golang-go-dbus FTBFS in stretch due to missing 
golang-gocheck-dev
848272 was not blocked by any bugs.
848272 was not blocking any bugs.
Added blocking bug(s) of 848272: 789991

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

Processed: Pending fixes for bugs in the libparanoid-perl package

[Debian Bug Tracking System]

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

> tag 848266 + pending
Bug #848266 [src:libparanoid-perl] libparanoid-perl: FTBFS: tests timeout
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#848266: Pending fixes for bugs in the libparanoid-perl package

[pkg-perl-maintainers]

tag 848266 + pending
thanks

Some bugs in the libparanoid-perl package are closed in revision
84a79e3d51baedf80e6b5c8c43f35f3dd2781de6 in branch 'master' by gregor
herrmann

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

Commit message:

Skip t/50_process.t during build and autopkgtest.

Closes: #848266

Bug#848266: libparanoid-perl: FTBFS: tests timeout

[gregor herrmann]

On Thu, 15 Dec 2016 20:52:35 +0100, Chris Lamb wrote:

> libparanoid-perl fails to build from source in unstable/amd64:

>   t/43_network.t .. 
>   1..34
>   ok 1 - ipInNetworks 1
>   ok 2 - ipInNetworks 2
>   ok 3 - ipInNetworks 3
>   ok 4 - ipInNetworks 4
>   ok 5 - ipInNetworks 5
>   ok 6 - ipInNetworks 6
>   ok 7 - hostInDomains 1
>   ok 8 - hostInDomains 2
>   ok 9 - hostInDomains 3
>   ok 10 - hostInDomains 4
>   ok 11 - hostInDomains 5
>   ok 12 - extractIPs 1
>   ok 13 - extractIPs 2
>   ok 14 - extractIPs 3
>   ok 15 - extractIPs 4
>   ok 16 - netIntersect 1
>   ok 17 - netIntersect 2
>   ok 18 - netIntersect 3
>   ok 19 - ipInNetworks 7
>   ok 20 - ipInNetworks 8
>   ok 21 - ipInNetworks 9
>   ok 22 - ipInNetworks 9
>   ok 23 - ipInNetworks 10
>   ok 24 - ipInNetworks 11
>   ok 25 - ipInNetworks 12
>   ok 26 - ipInNetworks 13
>   ok 27 - ipInNetworks ipv6 1
>   ok 28 - extractIPs 5
>   ok 29 - extractIPs 6
>   ok 30 - extractIPs 7
>   ok 31 - extractIPs 8
>   ok 32 - netIntersect ipv6 1
>   ok 33 - netIntersect ipv6 2
>   ok 34 - netIntersect ipv6 3
>   ok
> 
>   […]
> 
> (It hangs here)

Not for me at first try :)

But I see a delay of a couple seconds before the next test output is
written.


And when running the tests in a loop, I see interesting pauses in the
next test. Or now a complete hang here:

t/50_process.t .. 
1..36
ok 1 - ptranslateUser 1 (root)
ok 2 - ptranslateUser 2
ok 3 - ptranslateGroup 1 (root)
ok 4 - ptranslateGroup 2
ok 5 - switchUser 1 (from user root to pbuilder)
ok 6 - switchUser 2 (to group pbuilder)
ok 7 - switchUser 3 (user & group)
ok 8 - pfork 1
ok 9 - pfork 2
ok 10 - pfork 3
ok 11 - pfork 4
ok 12 - pfork 5
ok 13 - childrenCount 1
[some seconds ...]
[still waiting ...]
[and stil ...]

Ok, this hang (in the chroot when running the tests manually) is
fairly reproducible.

And then a "normal" package build succeeds. - And another one hangs
exactly at the same place as in the original report.


When I skip t/50_process.t, the test suite passes both during build
and when run in the chroot manually in a loop.

Committed to git. But I wait a bit with uploading since I'm not sure
if this is a problem in the test suite or in the code.


Cheers,
gregor


-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rigmor Gustafsson: The More I See


signature.asc
Description: Digital Signature

Bug#848235: freerdp2-dev: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libfreerdp-client.so

[Mike Gabriel]

Hi,

On  Do 15 Dez 2016 14:35:24 CET, Andreas Beckmann wrote:


Package: freerdp2-dev
Version: 2.0.0~git20161130.1.e60d0d5+dfsg1-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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


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


  Selecting previously unselected package freerdp2-dev:amd64.
  Preparing to unpack  
.../96-freerdp2-dev_2.0.0~git20161130.1.e60d0d5+dfsg1-1~exp1_amd64.deb  
...

  Unpacking freerdp2-dev:amd64 (2.0.0~git20161130.1.e60d0d5+dfsg1-1~exp1) ...
  dpkg: error processing archive  
/tmp/apt-dpkg-install-ycEMaI/96-freerdp2-dev_2.0.0~git20161130.1.e60d0d5+dfsg1-1~exp1_amd64.deb  
(--unpack):
   trying to overwrite  
'/usr/lib/x86_64-linux-gnu/libfreerdp-client.so', which is also in  
package libfreerdp-dev:amd64 1.1.0~git20140921.1.440916e+dfsg1-11

  Errors were encountered while processing:

/tmp/apt-dpkg-install-ycEMaI/96-freerdp2-dev_2.0.0~git20161130.1.e60d0d5+dfsg1-1~exp1_amd64.deb



cheers,

Andreas


The underlying problem here is, that freerdp1 gets upgraded and pulls  
in freerdp2. This should never happen for Debian 9. This is something  
for Debian 9+1.


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpN0VQtBWkOh.pgp
Description: Digitale PGP-Signatur

Processed: xmlsec1: diff for NMU version 1.2.23-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 828606 + patch
Bug #828606 [src:xmlsec1] xmlsec1: FTBFS with openssl 1.1.0
Ignoring request to alter tags of bug #828606 to the same tags previously set
> tags 828606 + pending
Bug #828606 [src:xmlsec1] xmlsec1: FTBFS with openssl 1.1.0
Added tag(s) pending.

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

Processed: Pending fixes for bugs in the libarray-refelem-perl package

[Debian Bug Tracking System]

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

> tag 817523 + pending
Bug #817523 [src:libarray-refelem-perl] libarray-refelem-perl: Removal of 
debhelper compat 4
Bug #827681 [src:libarray-refelem-perl] libarray-refelem-perl: FTBFS: dh_clean: 
Compatibility levels before 5 are no longer supported (level 4 requested)
Added tag(s) pending.
Added tag(s) pending.
> tag 827681 + pending
Bug #827681 [src:libarray-refelem-perl] libarray-refelem-perl: FTBFS: dh_clean: 
Compatibility levels before 5 are no longer supported (level 4 requested)
Bug #817523 [src:libarray-refelem-perl] libarray-refelem-perl: Removal of 
debhelper compat 4
Ignoring request to alter tags of bug #827681 to the same tags previously set
Ignoring request to alter tags of bug #817523 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#827681: Pending fixes for bugs in the libarray-refelem-perl package

[pkg-perl-maintainers]

tag 817523 + pending
tag 827681 + pending
thanks

Some bugs in the libarray-refelem-perl package are closed in revision
c6f223c6b244b96f8fee698b8330dbc58b0f484f in branch 'master' by
Christoph Biedl

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

Commit message:

Packaging cleanup

* Use the pristine upstream tarball
* Declare compliance with policy 3.9.8
* Raise debhelper compat level to 10. Closes: #817523, #827681
* Use dh7-style debian/rules
* Declare source format
* Update package description
* Re-write debian/copyright in format 1.0
* Add watch file

Processed: Re: Bug#848178: gimagereader fails to start

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #848178 {Done: Philip Rinn } [gimagereader] 
gimagereader fails to start
Bug reopened
Ignoring request to alter fixed versions of bug #848178 to the same values 
previously set
> reassign -1 libtesseract3 3.04.01-4.2
Bug #848178 [gimagereader] gimagereader fails to start
Bug reassigned from package 'gimagereader' to 'libtesseract3'.
No longer marked as found in versions gimagereader/3.2.0-1.
Ignoring request to alter fixed versions of bug #848178 to the same values 
previously set
Bug #848178 [libtesseract3] gimagereader fails to start
Marked as found in versions tesseract/3.04.01-4.2.
> retitle -1 libtesseract3: generated shlibs dependencies are not strict enough
Bug #848178 [libtesseract3] gimagereader fails to start
Changed Bug title to 'libtesseract3: generated shlibs dependencies are not 
strict enough' from 'gimagereader fails to start'.

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

Bug#848178: gimagereader fails to start

[Adrian Bunk]

Control: reopen -1
Control: reassign -1 libtesseract3 3.04.01-4.2
Control: retitle -1 libtesseract3: generated shlibs dependencies are not strict 
enough

On Wed, Dec 14, 2016 at 11:56:01PM +0100, Philip Rinn wrote:
> Hi joe,
> 
> true, it's the same problem again. But this time it's only revealed as you 
> didn't
> update tesseract. The version you have install is neither part of testing nor 
> unstable
> 
> > ii  libtesseract33.04.00-5
> 
> Current is:
> 
> testing: 3.04.01-4.2
> unstable: 3.04.01-5
> 
> Please check again after updating libtesseract3 and close the bug if it's 
> fixed.

Please do not close bugs that are actual bug - the generated 
dependencies must ensure that problems like the issue in this
bug won't happen.

Reopened and moved to the package where the root cause of this bug is.

> Best,
> Philip

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#848266: libparanoid-perl: FTBFS: tests timeout

[Chris Lamb]

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

Dear Maintainer,

libparanoid-perl fails to build from source in unstable/amd64:

  […]

  ok 23 - test/2/1 == "-P"
  ok 24 - parseArgs 8
  ok 25 - error string matches
  ok 26 - parseArgs 9
  ok 27 - error string matches
  ok 28 - parseArgs 10
  ok 29 - error string matches
  ok 30 - parseArgs 10
  ok 31 - error string matches
  ok 32 - parseArgs 10
  ok 33 - error string matches
  ok
  t/12_lockfile.t . 
  1..6
  ok 1 - plock excluse 1
  ok 2 - plock exclusive 2
  ok 3 - plock share 1
  ok 4 - pexclock 1
  ok 5 - pshclock 1
  ok 6 - punlock 1
  ok
  t/20_filesystem_pmkdir.t  
  1..9
  ok 1 - pmkdir 1
  ok 2 - pmkdir 2
  ok 3 - pmkdir 3
  ok 4 - pmkdir perms 1
  ok 5 - pmkdir 4
  ok 6 - pmkdir 5
  ok 7 - pmkdir 6
  ok 8 - pmkdir 7
  ok 9 - pmkdir 8
  ok
  t/21_filesystem_preadDir.t .. 
  1..18
  ok 1 - preadDir 1
  ok 2 - preadDir 2
  ok 3 - preadDir 3
  ok 4 - preadDir 4
  ok 5 - preadDir 5
  ok 6 - preadDir 6
  ok 7 - psubdirs 1
  ok 8 - psubdirs 2
  ok 9 - psubdirs 3
  ok 10 - psubdirs 4
  ok 11 - psubdirs 5
  ok 12 - psubdirs 6
  ok 13 - pfiles 1
  ok 14 - pfiles 2
  ok 15 - pfiles 3
  ok 16 - pfiles 4
  ok 17 - pfiles 5
  ok 18 - pfiles 6
  ok
  t/22_filesystem_prm.t ... 
  1..9
  ok 1 - prm single 1
  ok 2 - prm glob 1
  ok 3 - prm glob 2
  ok 4 - prmR 1
  ok 5 - prmR 2
  ok 6 - prmR 3
  ok 7 - prmR 4
  ok 8 # skip Running as root -- skipping permissions test
  ok 9 - prmR 6
  ok
  t/23_filesystem_ptouch.t  
  1..14
  ok 1 - ptouch missing 1
  ok 2 - ptouch single 1
  ok 3 - ptouch single 2
  ok 4 - ptouch checking atime 1
  ok 5 - ptouch checking mtime 1
  ok 6 - ptouch single 4
  ok 7 - ptouchR nofollow 1
  ok 8 - ptouchR checking atime 1
  ok 9 - ptouchR checking atime 1
  ok 10 - ptouchR follow 1
  ok 11 - ptouchR checking atime 2
  ok 12 - ptouchR checking mtime 2
  ok 13 - ptouchR glob 1
  ok 14 - error message
  ok
  t/24_filesystem_misc.t .. 
  1..12
  ok 1 - pcleanPath 1
  ok 2 - pcleanPath 2
  ok 3 - pcleanPath 3
  ok 4 - pcleanPath 4
  ok 5 - pcleanPath 5
  ok 6 - pcleanPath 6
  ok 7 - pcleanPath 7
  ok 8 - ptranslateLink 1
  ok 9 - ptranslateLink 2
  ok 10 - pwhich 1
  ok 11 - pwhich 2
  ok 12 - pwhich 3
  ok
  t/25_filesystem_pchmod.t  
  1..19
  ok 1 - perms match (ugo+rwxt)
  ok 2 - perms match (u+rwxs)
  ok 3 - perms match (ug+rwx)
  ok 4 - perms undef ()
  ok 5 - perms undef (0990)
  ok 6 - perms undef (xr+uG)
  ok 7 - pchmod 1
  ok 8 - pchmod 2
  ok 9 - pchmod 3
  ok 10 - pchmod 4
  ok 11 - pchmod 5
  ok 12 - pchmodR 1
  ok 13 - pchmodR 2
  ok 14 - pchmodR 3
  ok 15 - pchmodR 4
  ok 16 - pchmodR 5
  ok 17 - pchmodR 6
  ok 18 - pchmodR 7
  ok 19 - pchmodR 7
  ok
  t/26_filesystem_pchown.t  
  1..15
  ok 1 # skip Non-root user running tests
  ok 2 # skip Non-root user running tests
  ok 3 # skip Non-root user running tests
  ok 4 # skip Non-root user running tests
  ok 5 # skip Non-root user running tests
  ok 6 # skip Non-root user running tests
  ok 7 # skip Non-root user running tests
  ok 8 # skip Non-root user running tests
  ok 9 # skip Non-root user running tests
  ok 10 # skip Non-root user running tests
  ok 11 # skip Non-root user running tests
  ok 12 # skip Non-root user running tests
  ok 13 # skip Non-root user running tests
  ok 14 # skip Non-root user running tests
  ok 15 # skip Non-root user running tests
  ok
  t/30_log.t .. 
  1..9
  ok 1 - startLogger 1
  ok 2 - startLogger 2
  ok 3 - plog 1a
  ok 4 - plog 1b
  ok 5 - stopLogger 1
  ok 6 - plog 2
  ok 7 - plog 3
  ok 8 - plog 4
  ok 9 - plog 5
  ok
  t/31_log_buffer.t ... 
  1..20
  ok 1 - startLogger 1
  ok 2 - plog 1
  ok 3 - dumpBuffer 1
  ok 4 - check message 1
  ok 5 - plog 2
  ok 6 - dumpBuffer 2
  ok 7 - startLogger 2
  ok 8 - plog 3
  ok 9 - dumpBuffer 3
  ok 10 - plog 4
  ok 11 - dumpBuffer 4
  ok 12 - plog 5
  ok 13 - dumpBuffer 5
  ok 14 - dumpBuffer 6
  ok 15 - check message 2
  ok 16 - check message 3
  ok 17 - stopLogger 1
  ok 18 - startLogger 3
  ok 19 - check message 4
  ok 20 - check message 5
  ok
  t/32_log_file.t . 
  1..12
  ok 1 - startLogger 1
  ok 2 - plog 1
  ok 3 - stopLogger 1
  ok 4 - startLogger 2
  ok 5 - plog 2
  ok 6 - line count
  ok 7 - stopLogger 2
  ok 8 - logger options 1
  ok 9 - file size
  ok 10 - stopLogger 2
  ok 11 - logger options 2
  ok 12 - file perm
  ok
  t/40_socket.t ... 
  1..3
  ok 1 - sockaddr_in 1
  ok 2 - sockaddr_in6 1y
  ok 3 - CRLF 1
  ok
  t/41_ipv4.t . 
  1..32
  ok 1 - convert 192.168.0.0/24 1
  ok 2 - convert 192.168.0.0/24 2
  ok 3 - convert 192.168.0.0/24 3
  ok 4 - convert 192.168.0.0/24 4
  ok 5 - convert 192.168.0.64/28 1
  ok 6 - convert 192.168.0.64/28 2
  ok 7 - convert 192.168.0.64/28 3
  ok 8 - convert 192.168.0.64/28 4
  

Bug#848264: FTBFS on mips*

[Andrey Rahmatullin]

Package: src:spice-gtk
Version: 0.33-3.1
Severity: serious
Justification: fails to build from source

mips, mipsel and mips64el fail with the same messages. This is what I
get on eller in a mipsel chroot with make V=1:

make[2]: Entering directory '/home/wrar/spice-gtk-0.33/build-gtk3/src'
/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/home/wrar/spice-gtk-0.33=. -fstack-protector-strong 
-Wformat -Werror=format-security  -Wl,-z,relro -Wl,-z,now -o spicy 
spicy-spicy.o spicy-spicy-connect.o spicy-spice-cmdline.o  
libspice-client-gtk-3.0.la libspice-client-glib-2.0.la -lgthread-2.0 -pthread 
-lglib-2.0 -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 
-lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 
-lepoxy -lm  
libtool: link: gcc -g -O2 -fdebug-prefix-map=/home/wrar/spice-gtk-0.33=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -o .libs/spicy spicy-spicy.o spicy-spicy-connect.o 
spicy-spice-cmdline.o -pthread  ./.libs/libspice-client-gtk-3.0.so 
/home/wrar/spice-gtk-0.33/build-gtk3/src/.libs/libspice-client-glib-2.0.so 
-lX11 ./.libs/libspice-client-glib-2.0.so -lopus -ljpeg -lz -llz4 -lpixman-1 
-lssl -lcrypto -lpulse-mainloop-glib -lpulse -lgstaudio-1.0 -lgstapp-1.0 
-lgstvideo-1.0 -lgstbase-1.0 -lgstreamer-1.0 -lsasl2 -lcacard -lusb-1.0 
-lusbredirhost -lusbredirparser -lphodav-2.0 -lsoup-2.4 -lgthread-2.0 -lgtk-3 
-lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo 
-lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lepoxy -lm -pthread
spicy-spicy.o: In function `create_spice_window':
./build-gtk3/src/spicy.c:1003: undefined reference to 
`spice_display_new_with_monitor'
./build-gtk3/src/spicy.c:1003: undefined reference to 
`spice_display_new_with_monitor'
spicy-spicy.o: In function `main_channel_event':
./build-gtk3/src/spicy.c:1182: undefined reference to `spice_channel_get_error'
./build-gtk3/src/spicy.c:1182: undefined reference to `spice_channel_get_error'
collect2: error: ld returned 1 exit status
Makefile:1229: recipe for target 'spicy' failed

I could not understand why this happens, because:

$ nm -D build-gtk3/src/.libs/libspice-client-gtk-3.0.so|fgrep 
spice_display_new_with_monitor
00011e78 T spice_display_new_with_monitor
$ nm -D build-gtk3/src/.libs/libspice-client-glib-2.0.so|fgrep 
spice_channel_get_error
00021b8c T spice_channel_get_error

Bug#845798: patch for amarok

[Maximilian Engelhardt]

Hi,

I created a patch for amarok that switches to using mariadb. I don't see how 
the current mysql-defaults system can be used in amarok, as there is no 
default-mysqld-dev package.

$ diff -u debian.orig/amarok-2.8.0/debian/control 
debian/amarok-2.8.0/debian/control
--- debian.orig/amarok-2.8.0/debian/control 2016-12-01 20:16:40.0 
+0100
+++ debian/amarok-2.8.0/debian/control  2016-12-15 20:26:31.791265529 +0100
@@ -11,12 +11,12 @@
  kdelibs5-dev (>= 4:4.8.4),
  libmtp-dev (>= 1.0.0), libqjson-dev,
  libglib2.0-dev, libgpod-nogtk-dev (>= 0.7.0) | libgpod-dev (>= 0.7.0),
- libmysqld-pic (>= 5.5.23+dfsg), libwrap0-dev,
+ libmariadbd-dev, libwrap0-dev,
  libcurl4-gnutls-dev, libxml2-dev, libloudmouth1-dev,
  libgtk2.0-dev, libqca2-dev, liblastfm-dev (>= 1.0.3),
  libavformat-dev (>= 4:0.5), libofa0-dev, libaio-dev [linux-any],
  libgcrypt20-dev
-Build-Depends-Indep: mysql-server-core-5.6 | virtual-mysql-server-core
+Build-Depends-Indep: mariadb-server-core-10.0 | virtual-mysql-server-core
 Standards-Version: 3.9.8
 Homepage: http://amarok.kde.org
 Vcs-Git: https://anonscm.debian.org/git/pkg-kde/kde-extras/amarok.git

I compile tested the patch in pbuilder and tested the resulting .debs on my 
system.

It would be great If this could get reviewed and if acceptable uploaded to 
unstable so we can get an amarok in stretch.

Thanks,
Maxi

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

Processed: gkrellmoon: diff for NMU version 0.6-5.1

[Debian Bug Tracking System]

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

> tags 817338 + patch
Bug #817338 [src:gkrellmoon] gkrellmoon: Mandatory debian/compat for debhelper
Added tag(s) patch.
> tags 817338 + pending
Bug #817338 [src:gkrellmoon] gkrellmoon: Mandatory debian/compat for debhelper
Added tag(s) pending.
> tags 817477 + patch
Bug #817477 [src:gkrellmoon] gkrellmoon: Removal of debhelper compat 4
Added tag(s) patch.
> tags 817477 + pending
Bug #817477 [src:gkrellmoon] gkrellmoon: Removal of debhelper compat 4
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#817338: gkrellmoon: diff for NMU version 0.6-5.1

[Christoph Biedl]

tags 817338 + patch
tags 817338 + pending
tags 817477 + patch
tags 817477 + pending
thanks

Dear maintainer,

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

Regards,

Christoph
diff -u gkrellmoon-0.6/debian/rules gkrellmoon-0.6/debian/rules
--- gkrellmoon-0.6/debian/rules
+++ gkrellmoon-0.6/debian/rules
@@ -6,7 +6,7 @@
 #export DH_VERBOSE=1
 
 # This is the debhelper compatibility version to use.
-export DH_COMPAT=4
+# export DH_COMPAT=4
 
 
 CFLAGS = -g -Wall
@@ -17,7 +17,7 @@
 endif
 
 
-build: 
+build:
dh_testdir
 
# Add here commands to compile the package.
diff -u gkrellmoon-0.6/debian/control gkrellmoon-0.6/debian/control
--- gkrellmoon-0.6/debian/control
+++ gkrellmoon-0.6/debian/control
@@ -2,7 +2,7 @@
 Section: x11
 Priority: optional
 Maintainer: Martin Zobel-Helas 
-Build-Depends: debhelper (>= 4.1.0), gkrellm, libgtk2.0-dev
+Build-Depends: debhelper (>= 9~), gkrellm, libgtk2.0-dev
 Standards-Version: 3.7.2
 
 Package: gkrellmoon
diff -u gkrellmoon-0.6/debian/changelog gkrellmoon-0.6/debian/changelog
--- gkrellmoon-0.6/debian/changelog
+++ gkrellmoon-0.6/debian/changelog
@@ -1,3 +1,10 @@
+gkrellmoon (0.6-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Bump debhelper compat level to 9. Closes: #817338, #817477
+
+ -- Christoph Biedl   Wed, 14 Dec 2016 
21:04:35 +0100
+
 gkrellmoon (0.6-5) unstable; urgency=low
 
   * Don't strip binaries if build with DEB_BUILD_OPTIONS=nostrip. Thanks to
only in patch2:
unchanged:
--- gkrellmoon-0.6.orig/debian/compat
+++ gkrellmoon-0.6/debian/compat
@@ -0,0 +1 @@
+9


signature.asc
Description: Digital signature

Bug#846678: pgpdump: diff for NMU version 0.31-0.2

[Christoph Biedl]

tags 846678 patch pending
thanks

I've prepared an NMU for pgpdump (versioned as 0.31-0.2) and
uploaded it to DELAYED/05. Please feel free to tell me if I
should delay it longer.

Regards,

Christoph


signature.asc
Description: Digital signature

Processed: pgpdump: diff for NMU version 0.31-0.2

[Debian Bug Tracking System]

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

> tags 846678 patch pending
Bug #846678 [src:pgpdump] pgpdump: FTBFS: Test failures
Added tag(s) pending and patch.
> thanks
Stopping processing here.

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

Bug#846678: pgpdump: diff for NMU version 0.31-0.2

[Christoph Biedl]

Christoph 'always forgets to attch' Biedl wrote...

> I've prepared an NMU for pgpdump (versioned as 0.31-0.2) and
> uploaded it to DELAYED/05.

debdiff attached.

Christoph
diff -Nru pgpdump-0.31/debian/changelog pgpdump-0.31/debian/changelog
--- pgpdump-0.31/debian/changelog   2016-11-23 07:23:35.0 +0100
+++ pgpdump-0.31/debian/changelog   2016-12-14 21:49:14.0 +0100
@@ -1,3 +1,10 @@
+pgpdump (0.31-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Fix failing test suite. Closes: #846678
+
+ -- Christoph Biedl   Wed, 14 Dec 2016 
21:49:14 +0100
+
 pgpdump (0.31-0.1) unstable; urgency=medium
 
   [ Daniel Kahn Gillmor ]
diff -Nru pgpdump-0.31/debian/control pgpdump-0.31/debian/control
--- pgpdump-0.31/debian/control 2016-11-23 07:07:03.0 +0100
+++ pgpdump-0.31/debian/control 2016-12-14 21:47:55.0 +0100
@@ -6,6 +6,7 @@
  debhelper (>= 10~),
  dh-autoreconf,
  libbz2-dev,
+ tzdata,
  zlib1g-dev,
 Standards-Version: 3.9.8
 Homepage: http://www.mew.org/~kazu/proj/pgpdump/en/


signature.asc
Description: Digital signature

Bug#845167: Unable to reproduce

[Santiago Vila]

On Thu, 15 Dec 2016, Xavier Guimard wrote:

> I'm not able to reproduce the bug. It looks like if
> lemonldap-ng-handler-t-sessions directory wasn't readable by test
> process. Could you test another time to see if something has changed in
> dependencies since 2016-11-21 ?

It still fails (see attachements).

If you are trying to reproduce it, please try a *lot* of times,
because the failure rate is about 5%.

Thanks.

lemonldap-ng_1.9.5-1_amd64-20161215T183111Z.gz
Description: application/gzip


lemonldap-ng_1.9.5-1_amd64-20161215T183630Z.gz
Description: application/gzip


lemonldap-ng_1.9.5-1_amd64-20161215T184850Z.gz
Description: application/gzip


lemonldap-ng_1.9.5-1_amd64-20161215T185013Z.gz
Description: application/gzip

Bug#846698: marked as done (xserver-xorg-video-sisusb: FTBFS: ../../src/sisusb_driver.c:1670:6: error: too many arguments to function 'pScreen->BlockHandler')

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 18:50:44 +
with message-id 
and subject line Bug#846698: fixed in xserver-xorg-video-sisusb 1:0.9.6-3
has caused the Debian Bug report #846698,
regarding xserver-xorg-video-sisusb: FTBFS: ../../src/sisusb_driver.c:1670:6: 
error: too many arguments to function 'pScreen->BlockHandler'
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.)


-- 
846698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xserver-xorg-video-sisusb
Version: 1:0.9.6-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../../src -I..-fvisibility=hidden -I/usr/include/pixman-1 
> -I/usr/include/libdrm -I/usr/include/xorg -I/usr/include/X11/dri -g -O2 -c -o 
> sisusb_driver.lo ../../src/sisusb_driver.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. 
> -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/libdrm 
> -I/usr/include/xorg -I/usr/include/X11/dri -g -O2 -c 
> ../../src/sisusb_driver.c  -fPIC -DPIC -o .libs/sisusb_driver.o
> ../../src/sisusb_driver.c: In function 'SISUSBFreeRec':
> ../../src/sisusb_driver.c:201:13: warning: passing argument 1 of 'free' 
> discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
> free(pScrn->chipset);
>  ^
> In file included from /usr/include/xorg/misc.h:154:0,
>  from /usr/include/xorg/xf86str.h:37,
>  from /usr/include/xorg/xf86Privstr.h:37,
>  from /usr/include/xorg/xf86Priv.h:38,
>  from ../../src/sisusb.h:84,
>  from ../../src/sisusb_driver.c:36:
> /usr/include/stdlib.h:444:13: note: expected 'void *' but argument is of type 
> 'const char *'
>  extern void free (void *__ptr) __THROW;
>  ^~~~
> ../../src/sisusb_driver.c: In function 'SiSUSBFindUSBDongle':
> ../../src/sisusb_driver.c:302:11: warning: assignment discards 'const' 
> qualifier from pointer target type [-Wdiscarded-qualifiers]
> else p = dev->busID;
>^
> ../../src/sisusb_driver.c:304:13: warning: assignment discards 'const' 
> qualifier from pointer target type [-Wdiscarded-qualifiers]
>p = dev->busID;
>  ^
> ../../src/sisusb_driver.c: In function 'SISUSBPreInit':
> ../../src/sisusb_driver.c:836:32: warning: passing argument 1 of 
> 'SiSUSBCheckForUSBDongle' discards 'const' qualifier from pointer target type 
> [-Wdiscarded-qualifiers]
>  if(SiSUSBCheckForUSBDongle(pScrn->chipset, pSiSUSB, >sisusbdev) 
> < 0) {
> ^
> ../../src/sisusb_driver.c:240:1: note: expected 'char *' but argument is of 
> type 'const char *'
>  SiSUSBCheckForUSBDongle(char *filename, SISUSBPtr pSiSUSB, int *filehandle)
>  ^~~
> ../../src/sisusb_driver.c: In function 'SISUSBBlockHandler':
> ../../src/sisusb_driver.c:1648:31: warning: passing argument 1 of 
> 'SiSUSBCheckForUSBDongle' discards 'const' qualifier from pointer target type 
> [-Wdiscarded-qualifiers]
> if(SiSUSBCheckForUSBDongle(pScrn->chipset, pSiSUSB, >sisusbdev) 
> >= 0) {
>^
> ../../src/sisusb_driver.c:240:1: note: expected 'char *' but argument is of 
> type 'const char *'
>  SiSUSBCheckForUSBDongle(char *filename, SISUSBPtr pSiSUSB, int *filehandle)
>  ^~~
> ../../src/sisusb_driver.c:1670:6: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ~^~~
> ../../src/sisusb_driver.c:1671:27: warning: assignment from incompatible 
> pointer type [-Wincompatible-pointer-types]
>  pScreen->BlockHandler = SISUSBBlockHandler;
>^
> ../../src/sisusb_driver.c: In function 'SISUSBScreenInit':
> ../../src/sisusb_driver.c:1988:27: warning: assignment from incompatible 
> pointer type [-Wincompatible-pointer-types]
>  pScreen->BlockHandler = SISUSBBlockHandler;
>^
> Makefile:515: recipe for target 'sisusb_driver.lo' failed
> make[3]: *** [sisusb_driver.lo] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/12/02/xserver-xorg-video-sisusb_0.9.6-2_unstable.log

A list of current common 

Bug#848256: lastpass-cli: lpass segfaults attempting to log in

[C. Morgan Hamill]

Package: lastpass-cli
Version: 1.0.0-1.1
Severity: grave
Justification: renders package unusable

Hello,

Since upgrading to the version of lastpass-cli built against OpenSSL
1.1, Any attempt to use lpass has resulted in the error "Segmentation
fault" followed by an immediate exit.

Please let me know if I can provide further debugging information.
--
Morgan Hamill


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

Kernel: Linux 4.8.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 lastpass-cli depends on:
ii  binutils   2.27.51.20161201-1
ii  libc6  2.24-7
ii  libcurl3   7.50.1-1
ii  libssl1.1  1.1.0c-2
ii  libxml22.9.4+dfsg1-2.1

lastpass-cli recommends no packages.

lastpass-cli suggests no packages.

-- no debconf information

Bug#828395: libexosip2: diff for NMU version 4.1.0-2.1

[Andrey Rahmatullin]

Control: tags 828395 + pending

Dear maintainer,

I've prepared an NMU for libexosip2 (versioned as 4.1.0-2.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -Nru libexosip2-4.1.0/debian/changelog libexosip2-4.1.0/debian/changelog
--- libexosip2-4.1.0/debian/changelog	2014-06-25 18:12:22.0 +0600
+++ libexosip2-4.1.0/debian/changelog	2016-12-15 23:31:29.0 +0500
@@ -1,3 +1,10 @@
+libexosip2 (4.1.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with OpenSSL 1.1, patch by Andreas Henriksson (Closes: #828395).
+
+ -- Andrey Rahmatullin   Thu, 15 Dec 2016 23:31:29 +0500
+
 libexosip2 (4.1.0-2) unstable; urgency=low
 
   * Upload to unstable - coordinated through debian-release 
diff -Nru libexosip2-4.1.0/debian/patches/openssl110.patch libexosip2-4.1.0/debian/patches/openssl110.patch
--- libexosip2-4.1.0/debian/patches/openssl110.patch	1970-01-01 05:00:00.0 +0500
+++ libexosip2-4.1.0/debian/patches/openssl110.patch	2016-12-15 23:31:29.0 +0500
@@ -0,0 +1,69 @@
+## Description: add some description
+## Origin/Author: add some origin or author
+## Bug: bug URL
+diff -urip libexosip2-4.1.0/src/eXtl_dtls.c libexosip2-4.1.0.openssl110/src/eXtl_dtls.c
+--- libexosip2-4.1.0/src/eXtl_dtls.c	2014-01-06 19:30:21.0 +0100
 libexosip2-4.1.0.openssl110/src/eXtl_dtls.c	2016-11-07 20:23:01.503943171 +0100
+@@ -233,7 +233,7 @@ shutdown_free_client_dtls (struct eXosip
+ 
+   BIO_ctrl (rbio, BIO_CTRL_DGRAM_SET_PEER, 0, (char *) );
+ 
+-  (reserved->socket_tab[pos].ssl_conn)->rbio = rbio;
++  SSL_set0_rbio((reserved->socket_tab[pos].ssl_conn), rbio);
+ 
+   i = SSL_shutdown (reserved->socket_tab[pos].ssl_conn);
+ 
+@@ -588,12 +588,11 @@ dtls_tl_read_message (struct eXosip_t *e
+   rbio = BIO_new_mem_buf (enc_buf, enc_buf_len);
+   BIO_set_mem_eof_return (rbio, -1);
+ 
+-  reserved->socket_tab[pos].ssl_conn->rbio = rbio;
++  SSL_set0_rbio(reserved->socket_tab[pos].ssl_conn, rbio);
+ 
+   i = SSL_read (reserved->socket_tab[pos].ssl_conn, dec_buf, SIP_MESSAGE_MAX_LENGTH);
+   /* done with the rbio */
+-  BIO_free (reserved->socket_tab[pos].ssl_conn->rbio);
+-  reserved->socket_tab[pos].ssl_conn->rbio = BIO_new (BIO_s_mem ());
++  SSL_set0_rbio(reserved->socket_tab[pos].ssl_conn, BIO_new (BIO_s_mem ()));
+ 
+   if (i > 5) {
+ dec_buf[i] = '\0';
+@@ -904,7 +903,7 @@ dtls_tl_send_message (struct eXosip_t *e
+ _dtls_stream_used = >socket_tab[pos];
+ rbio = BIO_new_dgram (reserved->dtls_socket, BIO_NOCLOSE);
+ BIO_ctrl (rbio, BIO_CTRL_DGRAM_SET_PEER, 0, (char *) );
+-reserved->socket_tab[pos].ssl_conn->rbio = rbio;
++SSL_set0_rbio(reserved->socket_tab[pos].ssl_conn, rbio);
+ break;
+   }
+ }
+@@ -918,7 +917,7 @@ dtls_tl_send_message (struct eXosip_t *e
+   _dtls_stream_used = >socket_tab[pos];
+   rbio = BIO_new_dgram (reserved->dtls_socket, BIO_NOCLOSE);
+   BIO_ctrl (rbio, BIO_CTRL_DGRAM_SET_PEER, 0, (char *) );
+-  reserved->socket_tab[pos].ssl_conn->rbio = rbio;
++  SSL_set0_rbio(reserved->socket_tab[pos].ssl_conn, rbio);
+   break;
+ }
+   }
+diff -urip libexosip2-4.1.0/src/eXtl_tls.c libexosip2-4.1.0.openssl110/src/eXtl_tls.c
+--- libexosip2-4.1.0/src/eXtl_tls.c	2014-01-06 19:30:21.0 +0100
 libexosip2-4.1.0.openssl110/src/eXtl_tls.c	2016-11-07 20:27:51.568892332 +0100
+@@ -838,7 +838,7 @@ verify_cb (int preverify_ok, X509_STORE_
+* it for something special
+*/
+   if (!preverify_ok && (err == X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT)) {
+-X509_NAME_oneline (X509_get_issuer_name (store->current_cert), buf, 256);
++X509_NAME_oneline (X509_get_issuer_name (X509_STORE_CTX_get_current_cert(store)), buf, 256);
+ OSIP_TRACE (osip_trace (__FILE__, __LINE__, OSIP_ERROR, NULL, "issuer= %s\n", buf));
+   }
+ 
+@@ -1155,7 +1155,7 @@ initialize_client_ctx (struct eXosip_t *
+   }
+   else {
+ /* this is used to add a trusted certificate */
+-X509_STORE_add_cert (ctx->cert_store, cert);
++X509_STORE_add_cert (SSL_CTX_get_cert_store(ctx), cert);
+   }
+   BIO_free (bio);
+ }
diff -Nru libexosip2-4.1.0/debian/patches/series libexosip2-4.1.0/debian/patches/series
--- libexosip2-4.1.0/debian/patches/series	2012-12-25 05:46:23.0 +0600
+++ libexosip2-4.1.0/debian/patches/series	2016-12-15 23:31:29.0 +0500
@@ -1,2 +1,3 @@
 spelling-error-in-manpage.patch
 spelling-error-in-binary.patch
+openssl110.patch


signature.asc
Description: PGP signature

Processed: libexosip2: diff for NMU version 4.1.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 828395 + pending
Bug #828395 [src:libexosip2] libexosip2: FTBFS with openssl 1.1.0
Added tag(s) pending.

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

Bug#843434: marked as done (terminology: CVE-2015-8971: Escape Sequence Command Execution vulnerability)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 18:19:36 +
with message-id 
and subject line Bug#843434: fixed in terminology 0.9.1-1
has caused the Debian Bug report #843434,
regarding terminology: CVE-2015-8971: Escape Sequence Command Execution 
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.)


-- 
843434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: terminology
Version: 0.7.0-1
Severity: grave
Tags: security upstream patch
Justification: user security hole

Hi

terminology is suspectible to an escape sequence command execution
vulnerability, as described in
http://www.openwall.com/lists/oss-security/2016/11/04/12

The CVE has not yet been assigned, will update the subject here once
it's done.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: terminology
Source-Version: 0.9.1-1

We believe that the bug you reported is fixed in the latest version of
terminology, 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.
Ross Vandegrift  (supplier of updated terminology 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, 11 Dec 2016 12:25:35 -0500
Source: terminology
Binary: terminology terminology-data
Architecture: source
Version: 0.9.1-1
Distribution: unstable
Urgency: high
Maintainer: Debian Pkg-e Team 
Changed-By: Ross Vandegrift 
Closes: 766705 773057 774111 779494 782082 843434 844244
Description: 
 terminology-data - Enlightenment efl based terminal emulator data
 terminology - Enlightenment efl based terminal emulator
Changes:
 terminology (0.9.1-1) unstable; urgency=high
 .
   [ Ross Vandegrift ]
   * New upstream release
 - Fix for "CVE-2015-8971: Escape Sequence Command Execution
   vulnerability" (Closes: #843434)
   * fix-minus-signs-manpage.patch: drop patch, fixed upstream
   * use-system-lz4.patch: defuzz
   * fix-del-backspace-key.patch: defuzz
   * Provide x-terminal-emulator alternative (Closes: #774111)
   * debian/copyright: remove unused ltmain.sh paragraph
   * Add gbp.conf and notes on usage in README.source
   * Enable build hardening options
   * Suggest libemotion-players for media support (Closes: #773057, #766705)
   * Reformat package descriptions (Closes: #779494, #782082)
   * Use secure Vcs- URLs in debian/control
   * Bump Standards-Version to 3.9.8
   * New Maintainer.  Thanks to Anthony for original work. (Closes: #844244)
   * debian/gbp.conf: import & build upstream tarballs
 .
   [ Nicolas Braud-Santoni ]
   * Normalize links and use HTTPS
Checksums-Sha1: 
 1683745ae69ff9c3ffa0a809398779311e1cd243 2338 terminology_0.9.1-1.dsc
 b9fa5811e279782d4a2f6a25e86d09b128217bcf 4961876 terminology_0.9.1.orig.tar.xz
 1491468c735b490cc7a61970355066ddce812aba 11680 
terminology_0.9.1-1.debian.tar.xz
Checksums-Sha256: 
 8c09bbc23f0ed772a2c9ce9b1c2ea3c80c6ee3f14cda11364b22a7435d97bb3e 2338 
terminology_0.9.1-1.dsc
 ecee7ae6ba2fa10bfc5b6531292157dec2373dbb7d248cc62eb53d0be74e9bcf 4961876 
terminology_0.9.1.orig.tar.xz
 687253d1748c68e74636fe4c999f8b70ecf0dca4be61eb8f7476b4c2cae90b92 11680 
terminology_0.9.1-1.debian.tar.xz
Files: 
 a32b07f7da270ba949b546e8f90815e0 2338 x11 optional terminology_0.9.1-1.dsc
 b2a3890cf2a765762d1c4d10d82eb699 4961876 x11 optional 
terminology_0.9.1.orig.tar.xz
 6bc67d905ff6ed3a6d70528a28e11a65 11680 x11 optional 
terminology_0.9.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAlhS2H0ACgkQpU8BhUOC
FIQ/zBAAkWjSy9OOtu6YropZIMteY/Iaqb1CxqH5A9bwVs7vdOWBnj49pl3Hrfcj
EQ1Dg1mgVNpOiDsJeaw8p/9DX1UnF1JsNabq3PM/rJM6Z0RcsI0byei9XI2E/yEm
5KfKR+AAFuz2TuGpIRJiK/tIUrzc8+M0yRm3XVAJblUgSwKf9MrvSu28akmXUJOL
qvxpFniu3jeHwxg70U7I3pHC0Bwt1tg2kCIHJKSmjjILwhSF5iu6cPTdrSAQTAhP
HH7pteEvQ0Tuap0DegnFS4qogm8FuUTaZT15ELgOyi97pcd95miyTmgs+9JM4tFw
CyrU6Ve64sBchlXbWgM6G/c5o3TPAuwQ+wGG8QRIwBIXqfUg2IYl04tlYJbxlsht
D44fehwC1IgM3CtVzTkb8dA4qv2Rkg9QvkilnGjZ/kd60tDNOz24+jwbLl4l/qfl

Bug#846458: marked as done (xmlindent: add libfl-dev to Build-Depends)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 18:04:15 +
with message-id 
and subject line Bug#846458: fixed in xmlindent 0.2.17-4.1
has caused the Debian Bug report #846458,
regarding xmlindent: add libfl-dev to Build-Depends
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.)


-- 
846458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmlindent
Severity: important
User: helm...@debian.org
Usertags: libfldep

xmlindent will soon fail to build from source, beause flex drops its
dependency on libfl-dev. Since xmlindent uses parts of libfl-dev
(e.g. libl.a, libfl.a or FlexLexer.h), it should add libfl-dev to its
Build-Depends. This change was previously announced[1] to
debian-devel in accordance with DevRef 7.1.1. Please add the missing
dependency.

Helmut

[1] https://lists.debian.org/debian-devel/2016/03/msg00162.html 
--- End Message ---
--- Begin Message ---
Source: xmlindent
Source-Version: 0.2.17-4.1

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated xmlindent 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: Wed, 14 Dec 2016 21:56:42 +0500
Source: xmlindent
Binary: xmlindent
Architecture: source
Version: 0.2.17-4.1
Distribution: unstable
Urgency: medium
Maintainer: Miriam Ruiz 
Changed-By: Andrey Rahmatullin 
Description:
 xmlindent  - XML stream reformatter
Closes: 846458
Changes:
 xmlindent (0.2.17-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add Build-Depends: libfl-dev (Closes: #846458).
Checksums-Sha1:
 88dc8b9075536a256f7c5c64c1eacb4ac3b462c5 1766 xmlindent_0.2.17-4.1.dsc
 a73e29c73cbec8d07d9fe23db5c5c0927354d1ae 3440 
xmlindent_0.2.17-4.1.debian.tar.bz2
Checksums-Sha256:
 a72f61a0428ac5a49e3e987baffcb012b794fb35924a966d19daa3d7aa2c1de0 1766 
xmlindent_0.2.17-4.1.dsc
 3ab7fc5110a6b2111d980f3611cff6995cced3d0a61f4bceffa8c346de3a3731 3440 
xmlindent_0.2.17-4.1.debian.tar.bz2
Files:
 647f482d54780a333b6af296e69c297c 1766 devel optional xmlindent_0.2.17-4.1.dsc
 deb6809bb5269b5ab7b0b722d3b0a591 3440 devel optional 
xmlindent_0.2.17-4.1.debian.tar.bz2

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAlhRe0cACgkQM2L3AxpJ
kuHy0Q/+OluTAiSCX5uh/I+SfU+B0OnXzB+OjTZD2Vy/2AMnyHmuGaEMXpxGJ4du
BOwi2u7Rev39F5QonBzYb5PEIX7iHbTcuxB8/VCofNTW2EZzhHucQ3VMBLK+LUKx
OAhLSEfoSTw7pyU3Vuv083RgNrsHFsMoDGjdA9mbCN6QWNWFBEOuHKsXMsKfM+ab
bynRRZHa4C1KWT1UkvNzsMg9rCjXlxOz8+RiLIrZXhDuKUnSCj5QT19RlRbWwVPh
T/z4rTfAuHB1okQPjc3aQ6Mqr2tZAXLm8dGUyb3Ot1m45GX50/tYgu2wyitO7mCm
4ZDIF2MvamqoPilUc+cW9VZO8Ff4dCzbAv3yZDrrs+PDlwdOB6PNHUhGqJc7KMcU
nx3G12kiZ9c3TCI3ArLgIcYj/S2fvds9kS2kbNYWpfkFN3eQh816zYtgqK9HKCrj
IKurUgzZ+9ss3A2xNqswJOeuoNaP5Z51AkpqVr+48DtbVYz1Ss0/nwbMgXr3lLqB
ilX6s0lW7jjw4HMF+YDaUqJ6ViaarEwA5zbLP9lQCczgqb68gBVOYF6MGvF77rML
Y1VJONvWawqK7VsefBV4NK3NsGNVL6265fYj6Ux2HXXpdW1WFgjXc97JbcblTMke
2Oi/Q+fI6dC+XssIXkX2ZhF8nezy07yn7Yxqq3HeMDuA9UTEX7Y=
=wbkF
-END PGP SIGNATURE End Message ---

Processed: retitle 848114 to flightgear: CVE-2016-9956: Allows the route manager to overwrite arbitrary files

[Debian Bug Tracking System]

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

> retitle 848114 flightgear: CVE-2016-9956: Allows the route manager to 
> overwrite arbitrary files
Bug #848114 {Done: Markus Wanner } [src:flightgear] 
flightgear: Allows the route manager to overwrite arbitrary files
Changed Bug title to 'flightgear: CVE-2016-9956: Allows the route manager to 
overwrite arbitrary files' from 'flightgear: Allows the route manager to 
overwrite arbitrary files'.
> thanks
Stopping processing here.

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

Processed (with 1 error): merge two bugs in mpich (take 4)

[Debian Bug Tracking System]

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

> forcemerge 842881 831442
Bug #842881 [src:mpich] libmpich12: extraneous - and possibly wrong - symbolic 
link: /usr/lib/libmpich.so.12 -> libmpi.so
Bug #831442 [src:mpich] mpich: Broken /usr/lib/libmpich.so.12 symlink, 
depending on installation order
Failed to forcibly merge 842881: Not altering archived bugs; see unarchive.

> thanks
Stopping processing here.

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

Processed: closing 848213

[Debian Bug Tracking System]

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

> close 848213 2.20.4-1
Bug #848213 [src:apport] apport: CVE-2016-9949 CVE-2016-9950 CVE-2016-9951
Ignoring request to alter fixed versions of bug #848213 to the same values 
previously set
Bug #848213 [src:apport] apport: CVE-2016-9949 CVE-2016-9950 CVE-2016-9951
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#846698: xserver-xorg-video-sisusb: FTBFS: ../../src/sisusb_driver.c:1670:6: error: too many arguments to function 'pScreen->BlockHandler'

[Andreas Boll]

Control: tags -1 patch fixed-upstream pending

Hi,

thanks much for your work. I've noticed that upstream has already
merged a patch for compatibility with xserver 1.19 [1]. I've gone
ahead and cherry-picked that patch from upstream (the diff is
identical, but it has proper authorship).  Furthermore I've cleaned up
the package a little bit and included your second patch to fix
#745173.

We'll upload the fixed package soon.

Thanks,
Andreas

[1] 
https://cgit.freedesktop.org/xorg/driver/xf86-video-sisusb/commit/?id=6d44eb7a6075b9cc359b44282a7095a8b46c8a38

On Thu, Dec 15, 2016 at 04:41:29PM +0100, Mateusz Łukasik wrote:
> Tags: control + patch
> 
> Hi,
> 
> My NMU debdiff to fix that. Patch is take over from PLD Linux.
> 
> 
> -- 
>  .''`.  Mateusz Łukasik
> : :' :  http://mati75.eu
> `. `'   Debian Member - mat...@linuxmint.pl
>   `-GPG: D93B 0C12 C8D0 4D7A AFBC  FA27 CCD9 1D61 11A0 6851
> 
> 

> diff -u xserver-xorg-video-sisusb-0.9.6/debian/changelog 
> xserver-xorg-video-sisusb-0.9.6/debian/changelog
> --- xserver-xorg-video-sisusb-0.9.6/debian/changelog
> +++ xserver-xorg-video-sisusb-0.9.6/debian/changelog
> @@ -1,3 +1,11 @@
> +xserver-xorg-video-sisusb (1:0.9.6-2.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Fix FTBFS with xserver 1.19. (Closes: #846698)
> +  * Use arch:linux-any. (Closes: #745173)
> +
> + -- Mateusz Łukasik   Mon, 12 Dec 2016 09:58:58 +0100
> +
>  xserver-xorg-video-sisusb (1:0.9.6-2) unstable; urgency=low
>  
>* Release to unstable.
> diff -u xserver-xorg-video-sisusb-0.9.6/debian/control 
> xserver-xorg-video-sisusb-0.9.6/debian/control
> --- xserver-xorg-video-sisusb-0.9.6/debian/control
> +++ xserver-xorg-video-sisusb-0.9.6/debian/control
> @@ -22,7 +22,7 @@
>  Vcs-Browser: 
> http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-sisusb.git
>  
>  Package: xserver-xorg-video-sisusb
> -Architecture: any
> +Architecture: linux-any
>  Depends:
>   ${shlibs:Depends},
>   ${misc:Depends},
> diff -u xserver-xorg-video-sisusb-0.9.6/debian/patches/series 
> xserver-xorg-video-sisusb-0.9.6/debian/patches/series
> --- xserver-xorg-video-sisusb-0.9.6/debian/patches/series
> +++ xserver-xorg-video-sisusb-0.9.6/debian/patches/series
> @@ -1,0 +2 @@
> +xserver-1.19.patch
> only in patch2:
> unchanged:
> --- xserver-xorg-video-sisusb-0.9.6.orig/debian/patches/xserver-1.19.patch
> +++ xserver-xorg-video-sisusb-0.9.6/debian/patches/xserver-1.19.patch
> @@ -0,0 +1,16 @@
> +--- xf86-video-chips-1.2.6/src/compat-api.h~ 2015-09-26 18:28:01.0 
> +0200
>  xf86-video-chips-1.2.6/src/compat-api.h  2016-11-28 09:12:37.337570460 
> +0100
> +@@ -75,8 +75,13 @@
> + 
> + #define SCREEN_INIT_ARGS_DECL ScreenPtr pScreen, int argc, char **argv
> + 
> ++#if ABI_VIDEODRV_VERSION >= SET_ABI_VERSION(23, 0)
> ++#define BLOCKHANDLER_ARGS_DECL ScreenPtr arg, pointer pTimeout
> ++#define BLOCKHANDLER_ARGS arg, pTimeout
> ++#else
> + #define BLOCKHANDLER_ARGS_DECL ScreenPtr arg, pointer pTimeout, pointer 
> pReadmask
> + #define BLOCKHANDLER_ARGS arg, pTimeout, pReadmask
> ++#endif
> + 
> + #define CLOSE_SCREEN_ARGS_DECL ScreenPtr pScreen
> + #define CLOSE_SCREEN_ARGS pScreen



signature.asc
Description: Digital signature

Bug#848213: apport: CVE-2016-9949 CVE-2016-9950 CVE-2016-9951

[Salvatore Bonaccorso]

Hi!

On Thu, Dec 15, 2016 at 08:04:05PM +0530, Ritesh Raj Sarraf wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Control: tag -1 +pending
> Control: fixed -1 2.20.4-1
> 
> Hello Salvatore,
> 
> Thank you very much for the bug report.
> 
> On Thu, 2016-12-15 at 06:49 +0100, Salvatore Bonaccorso wrote:
> > Source: apport
> > Version: 2.16.2-1
> > Severity: grave
> > Tags: security upstream patch
> > Justification: user security hole
> > 
> 
> I am just curious how you came up with that version because it is quite old.
> apport is only available through Experimental and its current version in
> experimental is: 2.20.3-1

Because that was the oldest still affected version, which seem present
in experimental (not checked further), as as well per
https://www.ubuntu.com/usn/usn-3157-1/ as well back to older 2.x
versions.

Thanks a lot for your quick action, I have updated the
security-tracker with the fixed version.

> Thanks. Upstream has mentioned that all vulnerabilities are fixed in version
> 2.20.4, for which I've made an upload. It should clear ftp-masters queue soon.
> 
> Since this is an experimental only package, is there anywhere else, any action
> is required ?

No all done! Thanks a lot for your work.

Regards,
Salvatore

Processed (with 3 errors): merge two bugs in mpich (take 3)

[Debian Bug Tracking System]

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

> unarchive 831442
> unarchive 842881
> forcemerge 831442 842881
Bug #831442 [src:mpich] mpich: Broken /usr/lib/libmpich.so.12 symlink, 
depending on installation order
Bug #842881 [src:mpich] libmpich12: extraneous - and possibly wrong - symbolic 
link: /usr/lib/libmpich.so.12 -> libmpi.so
Failed to forcibly merge 831442: Not altering archived bugs; see unarchive.

> thanks
Stopping processing here.

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

Bug#848213: closing 848213

[Salvatore Bonaccorso]

close 848213 2.20.4-1
thanks

Processed: Re: Bug#846698: xserver-xorg-video-sisusb: FTBFS: ../../src/sisusb_driver.c:1670:6: error: too many arguments to function 'pScreen->BlockHandler'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream pending
Bug #846698 [src:xserver-xorg-video-sisusb] xserver-xorg-video-sisusb: FTBFS: 
../../src/sisusb_driver.c:1670:6: error: too many arguments to function 
'pScreen->BlockHandler'
Added tag(s) pending, fixed-upstream, and patch.

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

Processed: [bts-link] source package imagemagick

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package imagemagick
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #846385 (http://bugs.debian.org/846385)
> # Bug title: imagemagick: Potential ABI break upstream (without SONAME change)
> #  * https://github.com/ImageMagick/ImageMagick/issues/320
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 846385 + fixed-upstream
Bug #846385 [imagemagick] imagemagick: Potential ABI break upstream (without 
SONAME change)
Added tag(s) fixed-upstream.
> usertags 846385 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed (with 2 errors): merge two bugs in mpich (take 2)

[Debian Bug Tracking System]

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

> unarchive 831442
> forcemerge 831442 842881
Bug #831442 [src:mpich] mpich: Broken /usr/lib/libmpich.so.12 symlink, 
depending on installation order
Bug #842881 [src:mpich] libmpich12: extraneous - and possibly wrong - symbolic 
link: /usr/lib/libmpich.so.12 -> libmpi.so
Failed to forcibly merge 831442: Not altering archived bugs; see unarchive.

> thanks
Stopping processing here.

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

Processed (with 1 error): merge two bugs in mpich

[Debian Bug Tracking System]

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

> severity 831442 serious
Bug #831442 [src:mpich] mpich: Broken /usr/lib/libmpich.so.12 symlink, 
depending on installation order
Severity set to 'serious' from 'normal'
> reassign 842881 src:mpich
Bug #842881 [libmpich12] libmpich12: extraneous - and possibly wrong - symbolic 
link: /usr/lib/libmpich.so.12 -> libmpi.so
Bug reassigned from package 'libmpich12' to 'src:mpich'.
No longer marked as found in versions mpich/3.2-7.
Ignoring request to alter fixed versions of bug #842881 to the same values 
previously set
> forcemerge 831442 842881
Bug #831442 [src:mpich] mpich: Broken /usr/lib/libmpich.so.12 symlink, 
depending on installation order
Bug #842881 [src:mpich] libmpich12: extraneous - and possibly wrong - symbolic 
link: /usr/lib/libmpich.so.12 -> libmpi.so
Failed to forcibly merge 831442: Not altering archived bugs; see unarchive.

> thanks
Stopping processing here.

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

Bug#845167: Unable to reproduce

[Xavier Guimard]

Hi Santiago,

I'm not able to reproduce the bug. It looks like if
lemonldap-ng-handler-t-sessions directory wasn't readable by test
process. Could you test another time to see if something has changed in
dependencies since 2016-11-21 ?

Regards,
Xavier

Bug#835127: tellico: Tellico always crashes at boot time

[Andrej Mernik]

Dear Maintainer,

I tested this on Stretch with the package from unstable.

First problem: libkf5sane-data is in conflict with libksane-data which means 
that I must remove KIPI plugins to install this package -> not acceptable.

Second problem: it crashes with a segfault when run normally

Application: Tellico (tellico), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f78beabf089 in QWidgetPrivate::showChildren(bool) () from /usr/lib/
x86_64-linux-gnu/libQtGui.so.4
#7  0x7f78beabf19f in QWidgetPrivate::show_helper() () from /usr/lib/
x86_64-linux-gnu/libQtGui.so.4
#8  0x7f78beac11fa in QWidget::setVisible(bool) () from /usr/lib/x86_64-
linux-gnu/libQtGui.so.4
#9  0x7f78beabf0d7 in QWidgetPrivate::showChildren(bool) () from /usr/lib/
x86_64-linux-gnu/libQtGui.so.4
#10 0x7f78beabf19f in QWidgetPrivate::show_helper() () from /usr/lib/
x86_64-linux-gnu/libQtGui.so.4
#11 0x7f78beac11fa in QWidget::setVisible(bool) () from /usr/lib/x86_64-
linux-gnu/libQtGui.so.4
#12 0x00447fb5 in ?? ()
#13 0x7f78bd2372b1 in __libc_start_main () from /lib/x86_64-linux-gnu/
libc.so.6
#14 0x00448ae9 in _start ()

Interestingly, the program started working without problems when I ran it via 
Valgrind (I attach the output) . I deleted the tellicorc file and the program 
started to crash as described above until I  ran it with Valgrind again and 
the tellicorc file was recreated.

Please fix this asap as this is the last chance to get the program into 
Stretch.

Best Regards,
Andrej Mernik

==9527== Memcheck, a memory error detector
==9527== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==9527== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==9527== Command: tellico
==9527== 
tellico(9527)/kdeui (kdelibs): Attempt to use QAction "edit_undo" with 
KXMLGUIFactory! 
tellico(9527)/kdeui (kdelibs): Attempt to use QAction "edit_redo" with 
KXMLGUIFactory! 
==9527== Invalid read of size 8
==9527==at 0x9ADC085: QWidgetPrivate::showChildren(bool) (in 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)
==9527==by 0x9ADC19E: QWidgetPrivate::show_helper() (in 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)
==9527==by 0x9ADE1F9: QWidget::setVisible(bool) (in 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)
==9527==by 0x9ADC0D6: QWidgetPrivate::showChildren(bool) (in 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)
==9527==by 0x9ADC19E: QWidgetPrivate::show_helper() (in 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)
==9527==by 0x9ADE1F9: QWidget::setVisible(bool) (in 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)
==9527==by 0x447FB4: ??? (in /usr/bin/tellico)
==9527==by 0xB8C42B0: (below main) (libc-start.c:291)
==9527==  Address 0x2110bbe8 is 8 bytes inside a block of size 16 free'd
==9527==at 0x4C2C2DB: operator delete(void*) (vg_replace_malloc.c:576)
==9527==by 0xAC4E3A7: QObject::event(QEvent*) (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.7)
==9527==by 0x9A8854B: QApplicationPrivate::notify_helper(QObject*, QEvent*) 
(in /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)
==9527==by 0x9A8F52B: QApplication::notify(QObject*, QEvent*) (in 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)
==9527==by 0x947A1B9: KApplication::notify(QObject*, QEvent*) (in 
/usr/lib/libkdeui.so.5.14.26)
==9527==by 0xAC33F1C: QCoreApplication::notifyInternal(QObject*, QEvent*) 
(in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.7)
==9527==by 0xAC37A15: QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.7)
==9527==by 0xAC64702: ??? (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.7)
==9527==by 0x1303B7F6: g_main_context_dispatch (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.5000.2)
==9527==by 0x1303BA5F: ??? (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.5000.2)
==9527==by 0x1303BB0B: g_main_context_iteration (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.5000.2)
==9527==by 0xAC64853: 
QEventDispatcherGlib::processEvents(QFlags) (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.7)
==9527==  Block was alloc'd at
==9527==at 0x4C2B21F: operator new(unsigned long) (vg_replace_malloc.c:334)
==9527==by 0x9F39D50: ??? (in /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)
==9527==by 0x9E98008: ??? (in /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)  

==9527==by 0x9EC236F: ??? (in /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)  

==9527==by 0x9EC6FCA: ??? (in /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)  

==9527==by 0x9AB516C: QLayoutPrivate::doResize(QSize const&) (in 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)
==9527==by 0x9AB6D0F: QLayout::activate() (in 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7)
==9527==by 0x9ADE105: QWidget::setVisible(bool) (in 

Bug#848131: [Debian-science-sagemath] libmpich.so.12: cannot open shared object file: No such file or directory

[Tobias Hansen]

And also #831442, which has a workaround that can be applied to tachyon.

Best,
Tobias

On 12/15/2016 05:03 PM, Tobias Hansen wrote:
> Hi,
> 
> yes, this looks like #842881.
> 
> Note by the way that libtachyon-mpich-0 already depends on libmpich12 on
> hurd-i386, m68k, mips, mipsel, ppc64 and sh4.
> 
> Best,
> Tobias
> 
> On 12/15/2016 04:56 PM, Jerome BENOIT wrote:
>> Hello,
>>
>> I can reproduce the issue in schroot Sid environment on an amd64 box.
>> The Depends fields for the libraries is
>>
>> ${shlibs:Depends}, ${misc:Depends}
>>
>> and it works fine except for mpich. Before to add it by hand, I want
>> to understand why dpkg-shlibdep does not make properly its job.
>>
>> $ dpkg-shlibdeps 
>> debian/libtachyon-mpich-0/usr/lib/x86_64-linux-gnu/libtachyon-mpich-openmp.so.0
>>
>> gives something interesting:
>>
>> dpkg-shlibdeps: warning: /usr/lib/libmpich.so.12 has an unexpected SONAME 
>> (libmpi.so.20)
>> dpkg-shlibdeps: error: no dependency information found for 
>> /usr/lib/libmpich.so.12 (used by 
>> debian/libtachyon-mpich-0/usr/lib/x86_64-linux-gnu/libtachyon-mpich-openmp.so.0)
>>
>> And, more interestingly,
>>
>> ls -l /usr/lib/libmpich.so.12
>>
>> gives
>>
>> /usr/lib/libmpich.so.12 -> libmpi.so
>>
>> libmpi.so coming from libopenmpi-dev while 
>>
>>
>> Installing only libmpich-dev on a fresh schroot gives similar output:
>> it looks as a mpich building error.
>>
>>
>>
>> Thanks,
>> Jerome
>>
>>
>> ___
>> Debian-science-sagemath mailing list
>> debian-science-sagem...@lists.alioth.debian.org
>> https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath
>>
> 
> 
> ___
> Debian-science-sagemath mailing list
> debian-science-sagem...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath
> 

Bug#848131: [Debian-science-sagemath] libmpich.so.12: cannot open shared object file: No such file or directory

[Tobias Hansen]

Hi,

yes, this looks like #842881.

Note by the way that libtachyon-mpich-0 already depends on libmpich12 on
hurd-i386, m68k, mips, mipsel, ppc64 and sh4.

Best,
Tobias

On 12/15/2016 04:56 PM, Jerome BENOIT wrote:
> Hello,
> 
> I can reproduce the issue in schroot Sid environment on an amd64 box.
> The Depends fields for the libraries is
> 
> ${shlibs:Depends}, ${misc:Depends}
> 
> and it works fine except for mpich. Before to add it by hand, I want
> to understand why dpkg-shlibdep does not make properly its job.
> 
> $ dpkg-shlibdeps 
> debian/libtachyon-mpich-0/usr/lib/x86_64-linux-gnu/libtachyon-mpich-openmp.so.0
> 
> gives something interesting:
> 
> dpkg-shlibdeps: warning: /usr/lib/libmpich.so.12 has an unexpected SONAME 
> (libmpi.so.20)
> dpkg-shlibdeps: error: no dependency information found for 
> /usr/lib/libmpich.so.12 (used by 
> debian/libtachyon-mpich-0/usr/lib/x86_64-linux-gnu/libtachyon-mpich-openmp.so.0)
> 
> And, more interestingly,
> 
> ls -l /usr/lib/libmpich.so.12
> 
> gives
> 
> /usr/lib/libmpich.so.12 -> libmpi.so
> 
> libmpi.so coming from libopenmpi-dev while 
> 
> 
> Installing only libmpich-dev on a fresh schroot gives similar output:
> it looks as a mpich building error.
> 
> 
> 
> Thanks,
> Jerome
> 
> 
> ___
> Debian-science-sagemath mailing list
> debian-science-sagem...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath
> 

Bug#848131: libmpich.so.12: cannot open shared object file: No such file or directory

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

I can reproduce the issue in schroot Sid environment on an amd64 box.
The Depends fields for the libraries is

${shlibs:Depends}, ${misc:Depends}

and it works fine except for mpich. Before to add it by hand, I want
to understand why dpkg-shlibdep does not make properly its job.

$ dpkg-shlibdeps 
debian/libtachyon-mpich-0/usr/lib/x86_64-linux-gnu/libtachyon-mpich-openmp.so.0

gives something interesting:

dpkg-shlibdeps: warning: /usr/lib/libmpich.so.12 has an unexpected SONAME 
(libmpi.so.20)
dpkg-shlibdeps: error: no dependency information found for 
/usr/lib/libmpich.so.12 (used by 
debian/libtachyon-mpich-0/usr/lib/x86_64-linux-gnu/libtachyon-mpich-openmp.so.0)

And, more interestingly,

ls -l /usr/lib/libmpich.so.12

gives

/usr/lib/libmpich.so.12 -> libmpi.so

libmpi.so coming from libopenmpi-dev while 


Installing only libmpich-dev on a fresh schroot gives similar output:
it looks as a mpich building error.



Thanks,
Jerome

- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJYUss5AAoJED+SGaZ/NsaLK1QgALlj2ZJXzdAxOmWpHKKVruY/
kCKyohDtPF5GhJJMQdH/rx2DUK8OXyNBO0mQfFPg4yEcqcO90xedVjnQdC/Zly79
SGP7UWyA0EX+qiIQsFXBFBVI53SOCDLBPoXN7YQBFio7kC7Cd33PpwceGVBkNb76
vkk2yonI54XP0HdpDvrodX+mxjiSVScNEj+6aWTvLLtvCfQ9JL6ZmAW1RXzSO2fS
qLZ+k73QUW5AdgTetpRTrPDZ/OjNJjxyeKvnOkUT4OFfUG/By/fAReeLKY6OGpQa
/MmciVqDm+cQftoqdjT94PJH9i+lamUM/qfUebjZ//cjlqNxmTz/uO3Za0tt8cxP
73+fXk4h+dc5SITx5/fV+U+Kuk76hCXr+W4Z4HoA4hhSmJ6viRNLeQVxsXajcqeH
AsRIjFgPQFw8cfabCTycimbAud0UaSZUKdU1yrDIWjsmet8Cq7yMiJTnNrvWZnP3
85+YWPXulNuoeWWxBGSucJjsE/ytIXDBYMxGpNVjvoDSthh95ov0Q9UotTkSO9yO
WAWUy9Jpa78+Xu+ZvFHm0/7cLWWPHkTojnUiHBhjNWFfA1KLFaMef4w2KKg6fjzp
wa6idHQdmzz1W3o+ZL7ws7PeFFFgbFG18K4UX4wA5aaY6jiALGebh/iZBESKBAD3
Hke6SP6Y0df8Sq0ThXr+1PlNFnwBEzeReT3ktvjBAtOUy6USEK/JkiL0FBGQ4+F0
ttJQjm81n98LkZvjT/nxc2atZC0jF1ECtYej1b/Ws+KauGuX5KaRHDstafistIPB
Art/UOCOMM/qD39kXaSv0vtl2n22VH+/pg4Z1w+BbndjYTVXlY6c7HD3YrFrWwCG
eYtQvuH+GK+r9W4eFKdN1sDs6Ob/RpPknTbzyQStiWUZBioyEzWKtALpkFCps4lF
tF0cKztNQCZXBKaJGksNHlnpB96h4z2XQcUSLynBlqEWM5zuobOWP8v0wSPWxz3S
ARBd0/qlqJJybwP0v4id8ovvJg6bxZ4uBKZyEk1e/NIajs1Tbr7e7UBo1tBF+BCE
MT6KC3bRP+DgdY++ibq6pLPipqTj9ereDxwdZOkTbQsb0PubcTVPsBOBlhvQLAwn
2hptW7kDQbLsafFzoPuj7qQ9JOgwCO4cplWlEoK48ziilJAudFLXHSLhQPORh9RC
s/KyuoQ4lNb3xBs+OAU8zAUeg6+K6R47Jf7dRhHuhrFqcfT0vj7XNephZM20QMRR
QlDdne1hGTPPX23Tl3InMYvFKnIIWjdpkQAZuF351WBJ/qODdzqrPAR4aqffyyrq
DqH2+DJSCWq8JfjxQVXjs6HJKjhXhUZQg7p5JpPqtUJ/f6fYna/Sl6wyRiMydVE=
=ZczI
-END PGP SIGNATURE-

Processed: This bug affects the source of git-build-recipe by making it to FTBFS

[Debian Bug Tracking System]

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

> affects 846711 = src:git-build-recipe
Bug #846711 {Done: James McCoy } [devscripts] debuild: no 
longer checks whether lintian exists before implicitly running it
Bug #847629 {Done: James McCoy } [devscripts] 
git-build-recipe: FTBFS in sid: tests fail, lintian is missing
Removed indication that 846711 affects git-build-recipe
Added indication that 846711 affects src:git-build-recipe
Removed indication that 847629 affects git-build-recipe
Added indication that 847629 affects src:git-build-recipe
> thanks
Stopping processing here.

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

Bug#846704: marked as done (waffle: FTBFS: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_L

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 16:54:40 +
with message-id 
and subject line Bug#846704: fixed in waffle 1.5.2-2.1
has caused the Debian Bug report #846704,
regarding waffle: FTBFS: dh_auto_configure: cmake .. 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_BINARY_DIR=/<>/debian/tmp -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Release 
-Dwaffle_has_gbm=1 -Dwaffle_has_glx=1 -Dwaffle_has_x11_egl=1 
-Dwaffle_has_wayland=1 -Dwaffle_build_manpages=1 -Dwaffle_build_htmldocs=0 
-Dwaffle_build_examples=0 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.)


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

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> Building C object CMakeFiles/cmTC_176cd.dir/feature_tests.c.o
> /usr/bin/cc-g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2-std=c90 -o 
> CMakeFiles/cmTC_176cd.dir/feature_tests.c.o   -c 
> /<>/obj-x86_64-linux-gnu/CMakeFiles/feature_tests.c
> Linking C executable cmTC_176cd
> /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_176cd.dir/link.txt 
> --verbose=1
> /usr/bin/cc  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -Wl,-z,relro  
> CMakeFiles/cmTC_176cd.dir/feature_tests.c.o  -o cmTC_176cd -rdynamic 
> make[3]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> make[2]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> 
> 
> Feature record: C_FEATURE:1c_function_prototypes
> Feature record: C_FEATURE:0c_restrict
> Feature record: C_FEATURE:0c_static_assert
> Feature record: C_FEATURE:0c_variadic_macros
> dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_BINARY_DIR=/<>/debian/tmp -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Release 
> -Dwaffle_has_gbm=1 -Dwaffle_has_glx=1 -Dwaffle_has_x11_egl=1 
> -Dwaffle_has_wayland=1 -Dwaffle_build_manpages=1 -Dwaffle_build_htmldocs=0 
> -Dwaffle_build_examples=0 returned exit code 1
> debian/rules:10: recipe for target 'override_dh_auto_configure' failed
> make[1]: *** [override_dh_auto_configure] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/waffle_1.5.2-2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated waffle 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: Wed, 14 Dec 2016 22:53:42 +0500
Source: waffle
Binary: libwaffle-1-0 libwaffle-dev libwaffle-doc waffle-utils
Architecture: source
Version: 1.5.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Jordan Justen 
Changed-By: Andrey Rahmatullin 

Bug#835800: transmission: FTBFS with openssl 1.1.0

[Sandro Tosi]

On Fri, Dec 9, 2016 at 4:09 PM, Sebastian Andrzej Siewior
 wrote:
> This bug reached serious and has a patch available which is merged
> upstream. Is there something I can help you with?

I'll try to address this (by backporting the patch, most likely) very soon


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#848105: [rt.cpan.org #119235] Bio/Coordinate/Pair.pm removed from BioPerl in version 1.00070001

[Andreas Tille]

Hi Chris,

On Thu, Dec 15, 2016 at 10:08:53AM -0500, Chris Fields via RT wrote:
> It's now on CPAN:
> 
> https://metacpan.org/pod/Bio::Coordinate

Thanks a lot for the quick confirmation.
 
> I had actually pushed a release out a month ago but it apparently didn't 
> index correctly (it needed a module with the same name as the distribution).  
> 
> Let me know if this works!

I just noticed that the issue with libbio-graphics-perl is even more
complex than just a missing Bio::Coordinate.  I noticed that other
packages that are depending from libbio-graphics-perl are failing to
build[1].  May be the only quick solution is to revert the bump of
BioPerl version for the moment (= before the next stable release of
Debian) and try upgrading later.

I'll keep you informed if I might find any problem with Bio::Coordinate.

Just for the sake of interest: Is there any specific reason to outsource
Bio::Coordinate from BioPerl?

Kind regards

   Andreas.

[1] https://bugs.debian.org/848236

-- 
http://fam-tille.de

Processed: ruby-fog-rackspace: FTBFS randomly (undefined method `flavors')

[Debian Bug Tracking System]

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

> found 842607 0.1.1-3
Bug #842607 {Done: Pirate Praveen } 
[src:ruby-fog-rackspace] ruby-fog-rackspace: FTBFS (undefined method `flavors')
Marked as found in versions ruby-fog-rackspace/0.1.1-3; no longer marked as 
fixed in versions ruby-fog-rackspace/0.1.1-3 and reopened.
> retitle 842607 ruby-fog-rackspace: FTBFS randomly (undefined method flavors')
Bug #842607 [src:ruby-fog-rackspace] ruby-fog-rackspace: FTBFS (undefined 
method `flavors')
Changed Bug title to 'ruby-fog-rackspace: FTBFS randomly (undefined method 
flavors')' from 'ruby-fog-rackspace: FTBFS (undefined method `flavors')'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
842607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842607
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:

> tag 835437 unreproducible
Bug #835437 [src:pycurl] pycurl: FTBFS randomly (failing tests)
Added tag(s) unreproducible.
> severity 835437 important
Bug #835437 [src:pycurl] pycurl: FTBFS randomly (failing tests)
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Bug#839322: marked as done (libmoops-perl: FTBFS: build-dependency not installable: libkavorka-perl)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 17:24:21 +0100
with message-id <20161215162421.mnbifen6xqkgx...@jadzia.comodo.priv.at>
and subject line Re: Bug#839322: libmoops-perl: FTBFS: build-dependency not 
installable: libkavorka-perl
has caused the Debian Bug report #839322,
regarding libmoops-perl: FTBFS: build-dependency not installable: 
libkavorka-perl
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.)


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

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, devscripts, debhelper, dh-buildinfo, 
> libimport-into-perl, libkavorka-perl, libkeyword-simple-perl, 
> liblexical-accessor-perl, libmoox-late-perl, libmoosex-mungehas-perl, 
> libparse-keyword-perl, libperlx-assert-perl, libtype-tiny-perl, 
> libvariable-magic-perl, libtrue-perl, libexporter-tiny-perl (>= 0.040), 
> libmodule-runtime-perl (>= 0.013), libmoo-perl (>= 1.006000), 
> libscalar-list-utils-perl (>= 1:0.40), libtry-tiny-perl (>= 0.12), 
> libnamespace-autoclean-perl (>= 0.20), perl (>= 5.14), libtest-fatal-perl, 
> libtest-requires-perl, libtest-warnings-perl, libtypes-xsd-lite-perl, 
> libmoose-perl, libmouse-perl, libmoosex-types-common-perl
> Filtered Build-Depends: cdbs, devscripts, debhelper, dh-buildinfo, 
> libimport-into-perl, libkavorka-perl, libkeyword-simple-perl, 
> liblexical-accessor-perl, libmoox-late-perl, libmoosex-mungehas-perl, 
> libparse-keyword-perl, libperlx-assert-perl, libtype-tiny-perl, 
> libvariable-magic-perl, libtrue-perl, libexporter-tiny-perl (>= 0.040), 
> libmodule-runtime-perl (>= 0.013), libmoo-perl (>= 1.006000), 
> libscalar-list-utils-perl (>= 1:0.40), libtry-tiny-perl (>= 0.12), 
> libnamespace-autoclean-perl (>= 0.20), perl (>= 5.14), libtest-fatal-perl, 
> libtest-requires-perl, libtest-warnings-perl, libtypes-xsd-lite-perl, 
> libmoose-perl, libmouse-perl, libmoosex-types-common-perl
> dpkg-deb: building package 'sbuild-build-depends-libmoops-perl-dummy' in 
> '/<>/resolver-UeBrho/apt_archive/sbuild-build-depends-libmoops-perl-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-libmoops-perl-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-UeBrho/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-UeBrho/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-UeBrho/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-UeBrho/apt_archive ./ Sources [597 B]
> Get:5 copy:/<>/resolver-UeBrho/apt_archive ./ Packages [689 B]
> Fetched 2249 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install libmoops-perl build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-libmoops-perl-dummy : Depends: libkavorka-perl but it 
> is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/09/30/libmoops-perl_0.034-1_unstable.log

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

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

Bug#846450: marked as done (surf-alggeo: add libfl-dev to Build-Depends)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 16:19:00 +
with message-id 
and subject line Bug#846450: fixed in surf-alggeo 1.0.6+ds-4
has caused the Debian Bug report #846450,
regarding surf-alggeo: add libfl-dev to Build-Depends
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.)


-- 
846450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: surf-alggeo
Severity: important
User: helm...@debian.org
Usertags: libfldep

surf-alggeo will soon fail to build from source, beause flex drops
its dependency on libfl-dev. Since surf-alggeo uses parts of
libfl-dev (e.g. libl.a, libfl.a or FlexLexer.h), it should add
libfl-dev to its Build-Depends. This change was previously
announced[1] to debian-devel in accordance with DevRef 7.1.1. Please
add the missing dependency.

Helmut

[1] https://lists.debian.org/debian-devel/2016/03/msg00162.html 
--- End Message ---
--- Begin Message ---
Source: surf-alggeo
Source-Version: 1.0.6+ds-4

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated surf-alggeo 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: Thu, 15 Dec 2016 04:40:20 +
Source: surf-alggeo
Binary: surf-alggeo surf-alggeo-nox surf-alggeo-doc
Architecture: source
Version: 1.0.6+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jerome Benoit 
Description:
 surf-alggeo - visualization of real algebraic geometry
 surf-alggeo-doc - visualization of real algebraic geometry -- manual
 surf-alggeo-nox - visualization of real algebraic geometry -- no X support
Closes: 846450
Changes:
 surf-alggeo (1.0.6+ds-4) unstable; urgency=medium
 .
   * Fix Release Critical bug caused by novel but missing dependency
 (Closes: #846450), thanks to Helmut Grohne .
Checksums-Sha1:
 55d8581f51f3fe5b8a902e2f6dcd027b8d1e0180 3090 surf-alggeo_1.0.6+ds-4.dsc
 a0e69f60f58fc6f47cda557b9aa1bfe122a7c37e 216324 
surf-alggeo_1.0.6+ds.orig.tar.xz
 63af596943e6c4348feba5214c7ebdd431428db4 47904 
surf-alggeo_1.0.6+ds-4.debian.tar.xz
Checksums-Sha256:
 504eaaf2755b32a3842d16e1f914ad5f3aad7add16f490da6d9a1b696c5f59ce 3090 
surf-alggeo_1.0.6+ds-4.dsc
 eda8cf4286891d22d38343ca42796f345d61ffb0e4a0410cacba4b00c1fec4d3 216324 
surf-alggeo_1.0.6+ds.orig.tar.xz
 48ffbfa48bdf07b7022669e6caa6f047be8558a5c127fc120d5ecf48fe4dda7c 47904 
surf-alggeo_1.0.6+ds-4.debian.tar.xz
Files:
 01ba7a57af0ea11c8822c33ee2d062aa 3090 math optional surf-alggeo_1.0.6+ds-4.dsc
 be5b3a7eb99a7783129c5ba74151e500 216324 math optional 
surf-alggeo_1.0.6+ds.orig.tar.xz
 4d8ac3e9ba2868f1576f0b279bfe7aee 47904 math optional 
surf-alggeo_1.0.6+ds-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJYUr1zAAoJED+SGaZ/NsaLxoUgAMsdo7aQgIclf3kdYlW213TD
fbokLcPsRyaBHzh5hluWUv7/mmmCfG199kqWVvATZFUD0sPbDg725tKXx89BR8Kx
4fa90MHKi9cvJ8w8fpTQjJ10glDz94vUH0Y/zGgliMGwJ8UmAGifSgZBMtNcNp33
b13PD/lWJknj1tqTUu4pDco9xgfLSTlycnSfWoYr8e//QA4OStjvt0uzOkrvq/M6
fpj8/ZT1NPhUaErPpaA8mR/oOgTE+pJb7NU//g8xQvostHZlafiW+pcicU4s/mWQ
7cIUOAKVsHHbBlzg+utPMjegh4cEq6lNpEXin1+tsjs011p8mzal1CAfuAIJBcuv
QIu5yHh5iG0bxtIRs3ICOyEEa/yVsWm0znYVTdrQ12oSIaQQbpS5frRRfFNJwdjJ
Hxv0bhwLW09oQNsEGmPJuwIWM72SyYuie5OE0DmV1ALQGtoBlgerlKxapDq9vmYz
96t57xu6mtKVZlJw5E/6pTSke41XlwKvNbV8GniOEMEi6x1cNCUp3ZykrRjr5D8Z
Admm3Nlda65pPROeUJ/DmTFKbuQaYotVpkh3RNnWHMfMIUyUj+ncmzNQdAznTcyV
uDTWtNzq8K2ly2zFH4BEGiJ0mm+PV01lexkz8rTLJzLAG0eK9R0mPEAWP03OS4gV
tvzBqgd7+tdLAIxHhByWouSqzxsphy7T1Qcg0TJXyFaP4lxPX5+xkQ0ftmwCVxce
a/Tw5oVkki5a6TjlmVVhtbLcw5sqjjcdNIRtmfkhHUo2xpvI9I0XsyTXivsuaGRV
YWkgb68/schlTvXn9iqCOSkmpA4Sh0J8Brl+4d9FgifqEUzk5WHar6eqmLcmCgXa
gPIJj7ruNyoZsrvH9kftxpGdD4il0wtYQDEbDosVznXcKk42b6pGD1+Vjhlxc6Jy
Q8d4lHUhySa9XaI81qHX7onPdxI55flKSYloQ+AmwXAb64NiBx2svA7mNV9lxfF0

Bug#836419: marked as done (vde2: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 16:06:41 +
with message-id 
and subject line Bug#836419: fixed in vde2 2.3.2+r586-2.1
has caused the Debian Bug report #836419,
regarding vde2: 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.)


-- 
836419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vde2
Version: 2.3.2+r586-2
Severity: important
Tags: patch
Control: block 827061 by -1

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-08-26/failed/vde2_2.3.2%2Br586-2_amd64-2016-08-26T19%3A57%3A29Z

I made a patch to fix this problem. Your package seems also to fail to build in
parallel (-j2+). I didn't look into this.

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
>From 5f2c4c7b67617991af65798a4d177ada90f7e463 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Fri, 2 Sep 2016 19:52:49 +
Subject: [PATCH] vde_cryptcab: compile against openssl 1.1.0

Signed-off-by: Sebastian Andrzej Siewior 
---
 src/vde_cryptcab/cryptcab.c | 30 +++---
 1 file changed, 19 insertions(+), 11 deletions(-)

diff --git a/src/vde_cryptcab/cryptcab.c b/src/vde_cryptcab/cryptcab.c
index c5b4474..a2780f1 100644
--- a/src/vde_cryptcab/cryptcab.c
+++ b/src/vde_cryptcab/cryptcab.c
@@ -22,7 +22,7 @@ static void Usage(char *programname)
 	exit(1);
 }
 	
-static EVP_CIPHER_CTX ctx;
+static EVP_CIPHER_CTX *ctx;
 static int ctx_initialized = 0;
 static int encryption_disabled = 0;
 static int nfd;
@@ -30,6 +30,10 @@ static unsigned long long mycounter=1;
 static struct vde_open_args open_args={.port=0,.group=NULL,.mode=0700};
 static int verbose = 0;
 
+#if OPENSSL_VERSION_NUMBER < 0x1010
+#define EVP_CIPHER_CTX_reset(x)	EVP_CIPHER_CTX_cleanup(x)
+#endif
+
 void vc_printlog(int priority, const char *format, ...)
 {
 	va_list arg;
@@ -105,19 +109,21 @@ int data_encrypt(unsigned char *src, unsigned char *dst, int len, struct peer *p
 	}
 
 	if (!ctx_initialized) {
-		EVP_CIPHER_CTX_init ();
+		ctx = EVP_CIPHER_CTX_new ();
+		if (!ctx)
+			return -1;
 		ctx_initialized = 1;
 	}
 	
-	EVP_EncryptInit (, EVP_bf_cbc (), p->key, p->iv);
-	if (EVP_EncryptUpdate (, dst, , src, len) != 1)
+	EVP_EncryptInit (ctx, EVP_bf_cbc (), p->key, p->iv);
+	if (EVP_EncryptUpdate (ctx, dst, , src, len) != 1)
 	{
 		fprintf (stderr,"error in encrypt update\n");
 		olen = -1;
 		goto cleanup;
 	}
 
-	if (EVP_EncryptFinal (, dst + ulen, ) != 1)
+	if (EVP_EncryptFinal (ctx, dst + ulen, ) != 1)
 	{
 		fprintf (stderr,"error in encrypt final\n");
 		olen = -1;
@@ -126,7 +132,7 @@ int data_encrypt(unsigned char *src, unsigned char *dst, int len, struct peer *p
 	olen += tlen;
 
 cleanup:
-	EVP_CIPHER_CTX_cleanup();	
+	EVP_CIPHER_CTX_reset(ctx);
 	return olen;
 }
 
@@ -142,19 +148,21 @@ int data_decrypt(unsigned char *src, unsigned char *dst, int len, struct peer *p
 	}
 	
 	if (!ctx_initialized) {
-		EVP_CIPHER_CTX_init ();
+		ctx = EVP_CIPHER_CTX_new ();
+		if (!ctx)
+			return -1;
 		ctx_initialized = 1;
 	}
 
-	EVP_DecryptInit (, EVP_bf_cbc (), p->key, p->iv);
-	if (EVP_DecryptUpdate (, dst, , src, ulen) != 1)
+	EVP_DecryptInit (ctx, EVP_bf_cbc (), p->key, p->iv);
+	if (EVP_DecryptUpdate (ctx, dst, , src, ulen) != 1)
 	{
 		fprintf (stderr,"error in decrypt update\n");
 		olen = -1;
 		goto cleanup;
 	}
 
-	if (EVP_DecryptFinal (, dst + ulen, ) != 1)
+	if (EVP_DecryptFinal (ctx, dst + ulen, ) != 1)
 	{
 		fprintf (stderr,"error in decrypt final, ulen = %d, tlen = %d\n", ulen, tlen);
 		olen = -1;
@@ -163,7 +171,7 @@ int data_decrypt(unsigned char *src, unsigned char *dst, int len, struct peer *p
 	olen += tlen;
 
 cleanup:
-	EVP_CIPHER_CTX_cleanup();	
+	EVP_CIPHER_CTX_reset (ctx);
 	return olen;
 }
 
-- 
2.9.3

--- End Message ---
--- Begin Message ---
Source: vde2
Source-Version: 2.3.2+r586-2.1

We believe that the bug you reported is fixed in the latest version of
vde2, which is due to be 

Bug#828554: marked as done (spice-gtk: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 16:06:36 +
with message-id 
and subject line Bug#828554: fixed in spice-gtk 0.33-3.1
has caused the Debian Bug report #828554,
regarding spice-gtk: 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.)


-- 
828554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spice-gtk
Version: 0.30-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/spice-gtk_0.30-1_amd64-20160529-1539

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: spice-gtk
Source-Version: 0.33-3.1

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

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

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated spice-gtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 10 Dec 2016 20:06:07 +0500
Source: spice-gtk
Binary: spice-client-gtk spice-client-glib-usb-acl-helper 
libspice-client-glib-2.0-8 gir1.2-spice-client-glib-2.0 
libspice-client-glib-2.0-dev libspice-client-gtk-3.0-5 
gir1.2-spice-client-gtk-3.0 libspice-client-gtk-3.0-dev
Architecture: source
Version: 0.33-3.1
Distribution: unstable
Urgency: medium
Maintainer: Liang Guo 
Changed-By: Andrey Rahmatullin 
Description:
 gir1.2-spice-client-glib-2.0 - GObject for communicating with Spice servers 
(GObject-Introspecti
 gir1.2-spice-client-gtk-3.0 - GTK3 widget for SPICE clients 
(GObject-Introspection)
 libspice-client-glib-2.0-8 - GObject for communicating with Spice servers 
(runtime library)
 libspice-client-glib-2.0-dev - GObject for communicating with Spice servers 
(development files)
 libspice-client-gtk-3.0-5 - GTK3 widget for SPICE clients (runtime library)
 libspice-client-gtk-3.0-dev - GTK3 widget for SPICE clients (development files)
 spice-client-glib-usb-acl-helper - Helper tool to validate usb ACLs
 spice-client-gtk - Simple clients for interacting with SPICE servers
Closes: 828554
Changes:
 spice-gtk (0.33-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with OpenSSL 1.1, patch by Sebastian Andrzej Siewior (Closes:
 #828554).
Checksums-Sha1:
 ff6c48d1c5001e8ff35d5de0a22c2309deccafb0 3321 spice-gtk_0.33-3.1.dsc
 adbbfffa2aac83a8558249fc252b6cbd77bb2e97 14268 spice-gtk_0.33-3.1.debian.tar.xz
Checksums-Sha256:
 351520276d08f773845c1ed1ae82e58a808f2e2b6bee86bdb75ac71d9b3d5f83 3321 
spice-gtk_0.33-3.1.dsc
 14483a73d35088ccb63b49e24f0789c8a419d7df209db00cdb9e693654e40804 14268 
spice-gtk_0.33-3.1.debian.tar.xz
Files:
 e85649dceea6db26dafc1bdcd15666b5 3321 misc optional spice-gtk_0.33-3.1.dsc
 1c5113d679c2afe953b094ba5e53a5d9 14268 misc optional 
spice-gtk_0.33-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAlhMHZkACgkQM2L3AxpJ
kuFKFw//eWcyHhNwonZhqn1V4Rv/0swFRpeWkI5MykGAmpVnmanOIsTrQ7fA+7e4
BsG84ESO5yVpa+i2DhloyVvUhQCBmNxT+7kYcQFgnf9oBRtwcOkTdK5oggghXVNR
1AZi3jRw0B/w6QPEVXPu6sAN1YuHaA9/cfpt9QhnN6NLbZBxvSRemIwJHKstQ71j
7CHUQfhaH7IUPaIt3PoTzeb4hDhjg0NP4+WyjmInVubz8X8w9dPjTkw4eK7tE2UF
PkTXjXKV8QGKPP+KnM/f+/759ciwBuNUdlH4pZ18JzftLcN0j4VSBW44rWXj6p6i
6LzfeHzOv0LHaF1Zyz5PPREH6aGvsyCxehM3cvfEj/3qPZnz3xuQhk7dtMFovPkE
aycT+lru8/ccKXOhGC8SOrJco5R6rCKfS97iZwaZwIh3roxA8xR/e6QWzYgzyMpc

Bug#835437: (no subject)

[Barry Warsaw]

I can't reproduce the build failures reported here even with dpkg-buildpackage
-A.  However, I am going to add the discard-port proxies to d/rules that
pybuild normally adds by default (this package doesn't use pybuild).  That at
least will prevent the tests from *actually* hitting the internet.  I'll close
#830281 against that change.

Yes, this makes the test suite fail during package build.  I have reported
this upstream at https://github.com/pycurl/pycurl/issues/424

However note that d/rules currently discards test suite errors, so they don't
prevent the build from succeeding.  This makes running the tests semi-useless
but I think until upstream fixes their test suite, it's the best we can do.
Therefore I'm going to tag this bug as unreproducible and reduce the
severity.

I also can't reproduce the C locale problem, but I'm going to consider that a
separate bug so please file a new one on that issue.

Bug#805997: marked as done (banshee: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2016 15:48:31 +
with message-id 
and subject line Bug#805997: fixed in banshee 2.6.2-6.1
has caused the Debian Bug report #805997,
regarding banshee: FTBFS when built with dpkg-buildpackage -A (No such file or 
directory)
to be marked as done.

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

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


-- 
805997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:banshee
Version: 2.6.2-5
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
dh binary-indep --with=cli,autoreconf
   dh_testroot -i
   dh_prep -i
   dh_auto_install -i
make -j1 install DESTDIR=/<>/debian/tmp 
AM_UPDATE_INFO_DIR=no
make[1]: Entering directory '/<>'
Making install in build
make[2]: Entering directory '/<>/build'
Making install in pkg-config
make[3]: Entering directory '/<>/build/pkg-config'
make[4]: Entering directory '/<>/build/pkg-config'
make[4]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/pkgconfig'
 /usr/bin/install -c -m 644 banshee-musicbrainz.pc banshee-hyena.pc 
banshee-lastfm-gui.pc banshee-hyena-data-sqlite.pc banshee-core.pc 
banshee-hyena-gui.pc banshee-nowplaying.pc banshee-mono-media.pc 
banshee-collection-indexer.pc banshee-webbrowser.pc banshee-services.pc 
banshee-thickclient.pc banshee-lastfm.pc 
'/<>/debian/tmp/usr/lib/pkgconfig'
make[4]: Leaving directory '/<>/build/pkg-config'
make[3]: Leaving directory '/<>/build/pkg-config'
Making install in m4
make[3]: Entering directory '/<>/build/m4'
make[4]: Entering directory '/<>/build/m4'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.

[... snipped ...]

  debian/banshee/usr/lib/banshee/MeeGo.exe \
  debian/banshee/usr/lib/banshee/Extensions/Banshee.MeeGo.dll* \
  debian/banshee/usr/share/dbus-1/services/com.meego*
rm: cannot remove 'debian/banshee/usr/share/mutter-meego/': No such file or 
directory
rm: cannot remove 'debian/banshee/usr/lib/banshee/MeeGo.exe': No such file or 
directory
rm: cannot remove 
'debian/banshee/usr/lib/banshee/Extensions/Banshee.MeeGo.dll*': No such file or 
directory
rm: cannot remove 'debian/banshee/usr/share/dbus-1/services/com.meego*': No 
such file or directory
debian/rules:79: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:104: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:

* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
 
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:

* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.

* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.


After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B"
work properly, this package will be suitable to be uploaded in
source-only form if you wish (you might want to try it).

Thanks.
--- End Message ---
--- Begin Message ---
Source: banshee
Source-Version: 2.6.2-6.1

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of 

Bug#846698: xserver-xorg-video-sisusb: FTBFS: ../../src/sisusb_driver.c:1670:6: error: too many arguments to function 'pScreen->BlockHandler'

[Mateusz Łukasik]

Tags: control + patch

On Sat, 3 Dec 2016 08:23:02 +0100 Lucas Nussbaum  wrote:
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
> > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H 
-I. -I../../src -I.. -fvisibility=hidden -I/usr/include/pixman-1 
-I/usr/include/libdrm -I/usr/include/xorg -I/usr/include/X11/dri -g -O2 
-c -o sisusb_driver.lo ../../src/sisusb_driver.c
> > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. 
-fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/libdrm 
-I/usr/include/xorg -I/usr/include/X11/dri -g -O2 -c 
../../src/sisusb_driver.c -fPIC -DPIC -o .libs/sisusb_driver.o

> > ../../src/sisusb_driver.c: In function 'SISUSBFreeRec':
> > ../../src/sisusb_driver.c:201:13: warning: passing argument 1 of 
'free' discards 'const' qualifier from pointer target type 
[-Wdiscarded-qualifiers]

> > free(pScrn->chipset);
> > ^
> > In file included from /usr/include/xorg/misc.h:154:0,
> > from /usr/include/xorg/xf86str.h:37,
> > from /usr/include/xorg/xf86Privstr.h:37,
> > from /usr/include/xorg/xf86Priv.h:38,
> > from ../../src/sisusb.h:84,
> > from ../../src/sisusb_driver.c:36:
> > /usr/include/stdlib.h:444:13: note: expected 'void *' but argument 
is of type 'const char *'

> > extern void free (void *__ptr) __THROW;
> > ^~~~
> > ../../src/sisusb_driver.c: In function 'SiSUSBFindUSBDongle':
> > ../../src/sisusb_driver.c:302:11: warning: assignment discards 
'const' qualifier from pointer target type [-Wdiscarded-qualifiers]

> > else p = dev->busID;
> > ^
> > ../../src/sisusb_driver.c:304:13: warning: assignment discards 
'const' qualifier from pointer target type [-Wdiscarded-qualifiers]

> > p = dev->busID;
> > ^
> > ../../src/sisusb_driver.c: In function 'SISUSBPreInit':
> > ../../src/sisusb_driver.c:836:32: warning: passing argument 1 of 
'SiSUSBCheckForUSBDongle' discards 'const' qualifier from pointer target 
type [-Wdiscarded-qualifiers]
> > if(SiSUSBCheckForUSBDongle(pScrn->chipset, pSiSUSB, 
>sisusbdev) < 0) {

> > ^
> > ../../src/sisusb_driver.c:240:1: note: expected 'char *' but 
argument is of type 'const char *'
> > SiSUSBCheckForUSBDongle(char *filename, SISUSBPtr pSiSUSB, int 
*filehandle)

> > ^~~
> > ../../src/sisusb_driver.c: In function 'SISUSBBlockHandler':
> > ../../src/sisusb_driver.c:1648:31: warning: passing argument 1 of 
'SiSUSBCheckForUSBDongle' discards 'const' qualifier from pointer target 
type [-Wdiscarded-qualifiers]
> > if(SiSUSBCheckForUSBDongle(pScrn->chipset, pSiSUSB, 
>sisusbdev) >= 0) {

> > ^
> > ../../src/sisusb_driver.c:240:1: note: expected 'char *' but 
argument is of type 'const char *'
> > SiSUSBCheckForUSBDongle(char *filename, SISUSBPtr pSiSUSB, int 
*filehandle)

> > ^~~
> > ../../src/sisusb_driver.c:1670:6: error: too many arguments to 
function 'pScreen->BlockHandler'

> > (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
> > ~^~~
> > ../../src/sisusb_driver.c:1671:27: warning: assignment from 
incompatible pointer type [-Wincompatible-pointer-types]

> > pScreen->BlockHandler = SISUSBBlockHandler;
> > ^
> > ../../src/sisusb_driver.c: In function 'SISUSBScreenInit':
> > ../../src/sisusb_driver.c:1988:27: warning: assignment from 
incompatible pointer type [-Wincompatible-pointer-types]

> > pScreen->BlockHandler = SISUSBBlockHandler;
> > ^

Hi,

My NMU debdiff to fix that. Patch is take over from PLD Linux.


--
 .''`.  Mateusz Łukasik
: :' :  http://mati75.eu
`. `'   Debian Member - mat...@linuxmint.pl
  `-GPG: D93B 0C12 C8D0 4D7A AFBC  FA27 CCD9 1D61 11A0 6851


diff -u xserver-xorg-video-sisusb-0.9.6/debian/changelog 
xserver-xorg-video-sisusb-0.9.6/debian/changelog
--- xserver-xorg-video-sisusb-0.9.6/debian/changelog
+++ xserver-xorg-video-sisusb-0.9.6/debian/changelog
@@ -1,3 +1,11 @@
+xserver-xorg-video-sisusb (1:0.9.6-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with xserver 1.19. (Closes: #846698)
+  * Use arch:linux-any. (Closes: #745173)
+
+ -- Mateusz Łukasik   Mon, 12 Dec 2016 09:58:58 +0100
+
 xserver-xorg-video-sisusb (1:0.9.6-2) unstable; urgency=low
 
   * Release to unstable.
diff -u xserver-xorg-video-sisusb-0.9.6/debian/control 
xserver-xorg-video-sisusb-0.9.6/debian/control
--- xserver-xorg-video-sisusb-0.9.6/debian/control
+++ xserver-xorg-video-sisusb-0.9.6/debian/control
@@ -22,7 +22,7 @@
 Vcs-Browser: 
http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-sisusb.git
 
 Package: xserver-xorg-video-sisusb
-Architecture: any
+Architecture: linux-any
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
diff -u xserver-xorg-video-sisusb-0.9.6/debian/patches/series 
xserver-xorg-video-sisusb-0.9.6/debian/patches/series
--- xserver-xorg-video-sisusb-0.9.6/debian/patches/series
+++ xserver-xorg-video-sisusb-0.9.6/debian/patches/series
@@ -1,0 +2 @@
+xserver-1.19.patch
only in