Bug#856774: marked as done (xfce4-equake-plugin: Fails to download data, needs to use https)

[Debian Bug Tracking System]

Your message dated Sun, 19 Mar 2017 03:11:25 +
with message-id 
and subject line Bug#856774: fixed in xfce4-equake-plugin 1.3.8.1-2
has caused the Debian Bug report #856774,
regarding xfce4-equake-plugin: Fails to download data, needs to use https
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.)


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

Package: xfce4-equake-plugin
Version: 1.3.8-1
Severity: important
Tags: upstream

The 1.3.8-1 version of xfce4-equake-plugin uses unencrypted http to 
download data from the USGS website. The USGS website has migrated since 
03-01-2017 to only offer https access (see also https://https.cio.gov). 
This means that from that date the equake plugin will not be able to 
download data. I have released upstream version 1.3.8.1 to fix this 
problem, I will submit an updated debian package with this new upstream 
release to mentors.debian.net. Assuming that is the correct way to do this.


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: xfce4-equake-plugin
Source-Version: 1.3.8.1-2

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

Debian distribution maintenance software
pp.
Jeroen van Aart  (supplier of updated xfce4-equake-plugin 
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, 18 Mar 2017 18:04:09 -0800
Source: xfce4-equake-plugin
Binary: xfce4-equake-plugin
Architecture: amd64 source
Version: 1.3.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jeroen van Aart 
Changed-By: Jeroen van Aart 
Closes: 856774
Description: 
 xfce4-equake-plugin - Xfce panel plugin which monitors earthquakes
Changes:
 xfce4-equake-plugin (1.3.8.1-2) unstable; urgency=medium
 .
   * New upstream release: Closes: 856774
   * Migrated to use https to download earthquake data because USGS will phase
 out or has phased out http access, see also: https://https.cio.gov
 older versions of equake will stop working as a result
   * Make sure libcurl is part of Build-Depends
   * Bump standards version to 3.9.8 (no changes required)
   * Updated Homepage control field to show the https version of the homepage
   * Changed copyright years and added explicit copyright notice for icons
Checksums-Sha1: 
 d06c409ac28fe2a6c5f5c6b5433c637780dc6db3 2180 xfce4-equake-plugin_1.3.8.1-2.dsc
 b432dd9a4833d46da28816b08150af95a928903e 488470 
xfce4-equake-plugin_1.3.8.1.orig.tar.gz
 a93a99c96fbd4c28d272c6693e6261aa5b2e0c17 2008 
xfce4-equake-plugin_1.3.8.1-2.debian.tar.xz
 4e07118111c98596443ea4e8f7c8e8c196e7e94c 213446 
xfce4-equake-plugin-dbgsym_1.3.8.1-2_amd64.deb
 cec0f30373d20d95ae2db5ad1f1ca83560e8a801 11727 
xfce4-equake-plugin_1.3.8.1-2_amd64.buildinfo
 79842c6f763ce1b3437d6a7b5755f42f068c8c98 82912 
xfce4-equake-plugin_1.3.8.1-2_amd64.deb
Checksums-Sha256: 
 a8d9c90c7f85282a589dc20d35f961113c2ac6ec00d50fc9a82b8308ba942542 2180 
xfce4-equake-plugin_1.3.8.1-2.dsc
 32378cfcc741c024fa2dccc50f0b303039968761e81e211bac7e225dc4868295 488470 
xfce4-equake-plugin_1.3.8.1.orig.tar.gz
 a9fee6158c3b737aff3eecffadfa8101f1b70c750d18b23279be27f191b15707 2008 
xfce4-equake-plugin_1.3.8.1-2.debian.tar.xz
 c62cf75cc13d5aee26d25f7387f19253b7b4ef043c3eb620c4ffef1a55c9948d 213446 
xfce4-equake-plugin-dbgsym_1.3.8.1-2_amd64.deb
 34ea953ca5bde6c5cedb455c43ae474f1876728196d6ec586d22b96d656979c9 11727 
xfce4-equake-plugin_1.3.8.1-2_amd64.buildinfo
 215bc8575e2c5b1cae91ffac3cc9a98a0bc92eb2e78f0607f11f1234589e9c66 82912 
xfce4-equake-plugin_1.3.8.1-2_amd64.deb
Files: 
 4b7af49af392acfdccbae81da136187f 2180 

Bug#857065: gmrun: diff for NMU version 0.9.2-2.2

[Sean Whitton]

Update NMUdiff attached.  Thanks.

-- 
Sean Whitton
diff -Nru gmrun-0.9.2/debian/changelog gmrun-0.9.2/debian/changelog
--- gmrun-0.9.2/debian/changelog	2010-07-17 10:05:43.0 -0700
+++ gmrun-0.9.2/debian/changelog	2017-03-12 15:49:46.0 -0700
@@ -1,3 +1,12 @@
+gmrun (0.9.2-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Andreas Henriksson ]
+  * fix return type of gtk_completion_line_get_type (Closes: #857065)
+
+ -- Lukas Schwaighofer   Sun, 12 Mar 2017 23:49:46 +0100
+
 gmrun (0.9.2-2.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru gmrun-0.9.2/debian/patches/return-type-gtk_completion_line_get_type.patch gmrun-0.9.2/debian/patches/return-type-gtk_completion_line_get_type.patch
--- gmrun-0.9.2/debian/patches/return-type-gtk_completion_line_get_type.patch	1969-12-31 17:00:00.0 -0700
+++ gmrun-0.9.2/debian/patches/return-type-gtk_completion_line_get_type.patch	2017-03-12 15:49:46.0 -0700
@@ -0,0 +1,45 @@
+From: Andreas Henriksson 
+Date: Wed, 8 Mar 2017 23:21:15 +0100
+Subject: fix return type of gtk_completion_line_get_type
+
+Patch originally downloaded from
+https://src.fedoraproject.org/cgit/rpms/gmrun.git/plain/gmrun-0.9.2-f12.patch
+
+slighly modified (parts dropped, fuzz fixed) to apply on top of debian
+package
+
+Closes: #857065
+---
+ src/gtkcompletionline.cc | 4 ++--
+ src/gtkcompletionline.h  | 2 +-
+ 2 files changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/src/gtkcompletionline.cc b/src/gtkcompletionline.cc
+index 90897f7..c247994 100644
+--- a/src/gtkcompletionline.cc
 b/src/gtkcompletionline.cc
+@@ -77,9 +77,9 @@ static gboolean
+ on_key_press(GtkCompletionLine *cl, GdkEventKey *event, gpointer data);
+ 
+ /* get_type */
+-guint gtk_completion_line_get_type(void)
++GtkType gtk_completion_line_get_type(void)
+ {
+-  static guint type = 0;
++  static GtkType type = 0;
+   if (type == 0)
+   {
+ GtkTypeInfo type_info =
+diff --git a/src/gtkcompletionline.h b/src/gtkcompletionline.h
+index 5e14cd7..caed4c7 100644
+--- a/src/gtkcompletionline.h
 b/src/gtkcompletionline.h
+@@ -76,7 +76,7 @@ extern "C++" {
+ void (* cancel)(GtkCompletionLine *cl);
+   };
+ 
+-  guint gtk_completion_line_get_type(void);
++  GtkType gtk_completion_line_get_type(void);
+   GtkWidget *gtk_completion_line_new();
+ 
+   void gtk_completion_line_last_history_item(GtkCompletionLine*);
diff -Nru gmrun-0.9.2/debian/patches/series gmrun-0.9.2/debian/patches/series
--- gmrun-0.9.2/debian/patches/series	2010-07-17 10:05:49.0 -0700
+++ gmrun-0.9.2/debian/patches/series	2017-03-12 15:49:46.0 -0700
@@ -9,3 +9,4 @@
 90-window_placement.patch
 100-gmrunrc.patch
 debian-changes-0.9.2-2.1
+return-type-gtk_completion_line_get_type.patch


signature.asc
Description: PGP signature

Bug#857897: qtads FTBFS on 32bit: error: exception cleanup for this placement new selects non-placement operator delete

[Andreas Beckmann]

Followup-For: Bug #857897
Control: tag -1 patch pending

We can just build it with -std=c++11 if it does not like -std=c++14
(default in gcc-6).

Uploading NMU to DELAYED/5, please let me know if I should delay it
longer or reschedule.


Andreas
diff -Nru qtads-2.1.6/debian/changelog qtads-2.1.6/debian/changelog
--- qtads-2.1.6/debian/changelog	2013-07-14 20:32:49.0 +0200
+++ qtads-2.1.6/debian/changelog	2017-03-19 02:41:27.0 +0100
@@ -1,3 +1,10 @@
+qtads (2.1.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with -std=c++11. qtads is not ready for C++14.  (Closes: #857897)
+
+ -- Andreas Beckmann   Sun, 19 Mar 2017 02:41:27 +0100
+
 qtads (2.1.6-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru qtads-2.1.6/debian/rules qtads-2.1.6/debian/rules
--- qtads-2.1.6/debian/rules	2012-06-10 23:27:17.0 +0200
+++ qtads-2.1.6/debian/rules	2017-03-19 02:24:36.0 +0100
@@ -6,7 +6,7 @@
 export QTDIR = /usr/share/qt4
 
 CFLAGS += -fno-strict-aliasing
-CXXFLAGS += -fno-strict-aliasing
+CXXFLAGS += -fno-strict-aliasing -std=c++11
 
 QMAKE = qmake-qt4
 DEB_QMAKE_ARGS := BIN_INSTALL=/usr/games DOC_INSTALL=/usr/share/doc \

Processed: Re: qtads FTBFS on 32bit: error: exception cleanup for this placement new selects non-placement operator delete

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #857897 [src:qtads] qtads FTBFS on 32bit: error: exception cleanup for this 
placement new selects non-placement operator delete
Added tag(s) patch and pending.

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

Bug#812002: smokeqt: FTBFS with GCC 6: deleted function

[Giovani Ferreira]

Control: tags -1 + pending
Control: user debian-rele...@lists.debian.org
Control: usertags -1 + bsp-2017-03-br-curitiba

Hi,

I did make a NMU with the suggested patch to 5-day/delay queue.
Feel free to cancel this upload if needed.

The debian/changelog is:

  * Non-maintainer upload.
  * debian/rules: added g++ flag to avoid FTBFS with GCC 6. (Closes: #812002)

I attached a debdiff.

cheers,

Giovani
diff -Nru smokeqt-4.14.3/debian/changelog smokeqt-4.14.3/debian/changelog
--- smokeqt-4.14.3/debian/changelog 2015-09-10 23:22:34.0 -0300
+++ smokeqt-4.14.3/debian/changelog 2017-03-18 13:49:35.0 -0300
@@ -1,3 +1,10 @@
+smokeqt (4:4.14.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: added g++ flag to avoid FTBFS with GCC 6. (Closes: #812002)
+
+ -- Giovani Augusto Ferreira   Sat, 18 Mar 2017 13:49:35 
-0300
+
 smokeqt (4:4.14.3-1) unstable; urgency=medium
 
   * Team upload
diff -Nru smokeqt-4.14.3/debian/rules smokeqt-4.14.3/debian/rules
--- smokeqt-4.14.3/debian/rules 2015-09-10 16:40:53.0 -0300
+++ smokeqt-4.14.3/debian/rules 2017-03-18 13:49:35.0 -0300
@@ -3,6 +3,8 @@
 pkgs_lib := $(filter-out %-dev %-dbg,$(filter lib%,$(shell dh_listpackages)))
 current_version := $(shell dpkg-parsechangelog | sed -n 's/^Version: //p')
 
+export DEB_CXXFLAGS_MAINT_APPEND = -std=c++98
+
 override_dh_install:
dh_install --list-missing
 

Processed (with 2 errors): Re: smokeqt: FTBFS with GCC 6: deleted function

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #812002 [smokeqt] smokeqt: FTBFS with GCC 6: deleted function
Added tag(s) pending.
> user debian-rele...@lists.debian.org
Unknown command or malformed arguments to command.

> usertags -1 + bsp-2017-03-br-curitiba
Unknown command or malformed arguments to command.


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

Bug#852960: marked as done (rt-app FTBFS on mips64el/ppc64el: error: conflicting types for 'timespec_to_nsec')

[Debian Bug Tracking System]

Your message dated Sun, 19 Mar 2017 01:05:10 +
with message-id 
and subject line Bug#852960: fixed in rt-app 0.3-2
has caused the Debian Bug report #852960,
regarding rt-app FTBFS on mips64el/ppc64el: error: conflicting types for 
'timespec_to_nsec'
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.)


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

https://buildd.debian.org/status/package.php?p=rt-app

...
gcc -DHAVE_CONFIG_H -I.  -I./../libdl/ -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o rt-app_parse_config.o rt-app_parse_config.c
rt-app_utils.c:46:1: error: conflicting types for 'timespec_to_nsec'
 timespec_to_nsec(struct timespec *ts)
 ^~~~
In file included from rt-app_utils.c:24:0:
rt-app_utils.h:127:1: note: previous declaration of 'timespec_to_nsec' was here
 timespec_to_nsec(struct timespec *ts);
 ^~~~
 ...
--- End Message ---
--- Begin Message ---
Source: rt-app
Source-Version: 0.3-2

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

Debian distribution maintenance software
pp.
Wookey  (supplier of updated rt-app 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, 09 Mar 2017 13:44:33 +
Source: rt-app
Binary: rt-app
Architecture: source amd64
Version: 0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Linaro Packagers 
Changed-By: Wookey 
Description:
 rt-app - Test application which simulates a real-time periodic load
Closes: 852960
Changes:
 rt-app (0.3-2) unstable; urgency=medium
 .
   * Fix FTBFS on some arches by defining unsigned long long as __u64
 (Closes: 852960)
Checksums-Sha1:
 cb6ba61d0b3849ac645ba0aef79959715b267c1f 1744 rt-app_0.3-2.dsc
 2158563a41fa1c0b75ccd6e9d3c3a102fe5553ce 3664 rt-app_0.3-2.debian.tar.xz
 2d4bd30e7673c1423c5f1f5be0583aed3b0f2e64 44556 rt-app-dbgsym_0.3-2_amd64.deb
 b27d2ba3772dfe9345b2a09bf4b67882c72788e1 4776 rt-app_0.3-2_amd64.buildinfo
 8540620836421a37d6c5c3179060988d496dd519 37000 rt-app_0.3-2_amd64.deb
Checksums-Sha256:
 7c9a0427b6c792fe03047fae67812f595cef767410859a4533a9d333479e3c3b 1744 
rt-app_0.3-2.dsc
 9b2f0e613fb95e9bd472446b4a4779840eef53f52a9306408650e2af212f2b4e 3664 
rt-app_0.3-2.debian.tar.xz
 76b025c376230d811e28a8bfad029df941ef65cac64084e09b8e442f66b49978 44556 
rt-app-dbgsym_0.3-2_amd64.deb
 42019c2dc83e71f0070b232fed84c9d588a05a303effd10ff04e8dbe1aaca727 4776 
rt-app_0.3-2_amd64.buildinfo
 ec8f937cfb839120bd68e4ef91191e25d87284fefb47b32532e54b7595914c49 37000 
rt-app_0.3-2_amd64.deb
Files:
 e37decd1417b59a49140e1ba00611d18 1744 misc optional rt-app_0.3-2.dsc
 4c8f0d34301e60be08ee560c0962f311 3664 misc optional rt-app_0.3-2.debian.tar.xz
 502265b6f8a8ced607ab7de72190d3c0 44556 debug extra 
rt-app-dbgsym_0.3-2_amd64.deb
 145c53b648b1366062f1f2b9c239d328 4776 misc optional 
rt-app_0.3-2_amd64.buildinfo
 5f2348c9c8a222fc4afa2a57e4430e22 37000 misc optional rt-app_0.3-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYzdVuAAoJEPuGMlGob55H/fUP/0QuSQEJaY6TMErAIbdzgpM8
pve21ac6ufNUEtb15oku6VOkx9eHVwjJgLWWP3ld0rRa/12xzWYeBQnoAcCwlNtC
5caBOeFbMeJkEbSs5m2x1IoQClOcQ61tFDDmh+PkE4elbAeaLx66oWKHUj60yrvG
lC9BI3GsVBMA0a1LBcZaoQk4rqgOCpWZIGGGfUnJdgI8/U3t+hrUd06e7JvkTwJC
IcqTGVlTWFpFPbz8/PyJ7iaYkMxjqwwSmjDz5nuHn/IMOwLWG0lZjHibtt2VfPBj
Wm3CNfZfNNumggqiP+kkGjt+gR7ozR262KtVJvTbUXa6SBFWElI4AD8dr+GkXjXc
jmXz/Y4UzJK3TaSFh2mxCScm10cC1Pk08TEbvVLEOkhWdMdycasB3tEagKKe6T2k
ykhriI8jA/695zWyzhmXgYiV56A2DVV5VgvAn9W9Np5/6OZvu9QYMPaDgLJB+YuS
C6KRvkoFz/r/sZVG9K2ek55+3Ge5sli/4f697ZEHXOWkbCYMuXEh9WsUmZLq4rtr
JT9VwsESViU99EFp0iYczuoaEiSLbnKhWwCspl75KLZ6jo2jf5F/4wznX9v+B4P4
SQ1hIIEi8fDKqU+gt1UkcyWtkSlYBSASePhShwv/MdJLgbItAovziaZe9B+5BTTp
m8TwGPI92cnm4fn7h7R3
=CsSZ
-END PGP SIGNATURE End 

Bug#857310: marked as done (sdpb FTBFS: *** stack smashing detected ***: ./sdpb terminated)

[Debian Bug Tracking System]

Your message dated Sun, 19 Mar 2017 00:50:03 +
with message-id 
and subject line Bug#857310: fixed in sdpb 1.0-2
has caused the Debian Bug report #857310,
regarding sdpb FTBFS: *** stack smashing detected ***: ./sdpb terminated
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.)


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

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

...
make[1]: Leaving directory '/«PKGBUILDDIR»'
   dh_auto_test -a
make -j6 test
make[1]: Entering directory '/«PKGBUILDDIR»'
./sdpb -s test.xml --noFinalCheckpoint
SDPB started at 2017-Mar-09 19:16:03
SDP file: "test.xml"
out file: "test.out"
checkpoint file : "test.ck"

Parameters:
maxIterations= 500
maxRuntime   = 86400
checkpointInterval   = 3600
noFinalCheckpoint= true
findPrimalFeasible   = false
findDualFeasible = false
detectPrimalFeasibleJump = false
detectDualFeasibleJump   = false
precision(actual)= 400(448)
maxThreads(using)= 4(4)
dualityGapThreshold  = 1e-30
primalErrorThreshold = 1e-30
dualErrorThreshold   = 1e-30
initialMatrixScalePrimal = 1
initialMatrixScaleDual   = 1
feasibleCenteringParameter   = 0.1
infeasibleCenteringParameter = 0.3
stepLengthReduction  = 0.7
choleskyStabilizeThreshold   = 1e-40
maxComplementarity   = 1e+100

*** stack smashing detected ***: ./sdpb terminated
Makefile:89: recipe for target 'test' failed
make[1]: *** [test] Aborted
--- End Message ---
--- Begin Message ---
Source: sdpb
Source-Version: 1.0-2

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sdpb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 19 Mar 2017 00:06:27 +
Source: sdpb
Binary: sdpb sdpb-doc
Architecture: source amd64 all
Version: 1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Description:
 sdpb   - Semidefinite program solver
 sdpb-doc   - Semidefinite program solver (documentation)
Closes: 857310
Changes:
 sdpb (1.0-2) unstable; urgency=medium
 .
   * Add patch use-system-tinyxml2.h.patch. (Closes: #857310)
   * Use boost 1.63 instead of 1.62.
Checksums-Sha1:
 e58773fd63f3d7d1c1fdef27938328cd1c28ac92 2281 sdpb_1.0-2.dsc
 10cf5e915634c0528a192c6115d6a3e6f072ff9d 4756 sdpb_1.0-2.debian.tar.xz
 1a49d1ea46ed0ae57b15c97fb9bb13f11130bf4f 2465354 sdpb-dbgsym_1.0-2_amd64.deb
 e7233a5675ccf0f2ce08eced34d27f9423c8cc78 297552 sdpb-doc_1.0-2_all.deb
 07542dedb7093ccd02bf5dcdb18efdc893d89c4c 8406 sdpb_1.0-2_amd64.buildinfo
 4fb011c7d5a13a3a37139e2c151f3115116a1781 181220 sdpb_1.0-2_amd64.deb
Checksums-Sha256:
 31752bc7053c450edc798bafbd1c5cbd160328933698bbc60efb55564c12989a 2281 
sdpb_1.0-2.dsc
 ebd2b82c681ea16e385f80de0c9d1f478b8ac7bf10a0436152c4eaf735c3188c 4756 
sdpb_1.0-2.debian.tar.xz
 fb8795060dade51649c74fef46e091df52efbc4aa4291f13bfb9cac45400f1bd 2465354 
sdpb-dbgsym_1.0-2_amd64.deb
 8097fbab18f6eb95eeac4f860ec21beadefe9e66b5c0657e3898e64b0d4e9a4f 297552 
sdpb-doc_1.0-2_all.deb
 19eb7f1907a1e71247c7b465a0bff2f5c5c677d85e4030b91780d82eacf46eaa 8406 
sdpb_1.0-2_amd64.buildinfo
 6b5ec2f817cde792200fddc727e8ff1762d2f60627a061a243a07772e7d683f8 181220 
sdpb_1.0-2_amd64.deb
Files:
 f61bb04f047041643a6d971dab69afb6 2281 math optional sdpb_1.0-2.dsc
 a0287766f0f9eaf68490274e1ed4568f 4756 math optional sdpb_1.0-2.debian.tar.xz
 ab01afe211f9a0b4bb69a4e48ce57404 2465354 debug extra 
sdpb-dbgsym_1.0-2_amd64.deb
 d446b8d9f2336d3c749bdf235aa47c29 297552 doc optional sdpb-doc_1.0-2_all.deb
 0a3c95cec224bda31805fbf9f71aa682 8406 math 

Bug#857794: reportbug: crash when encountering some non-ASCII characters

[Dima Kogan]

On March 18, 2017 12:24:12 PM PDT, Evgeni Golov  wrote:
>Hi Dima,
>
>> Hi. I just tried to send an unblock, and reportbug crashed. Session:
>> 
>> dima@scrawny:~$ sudo apt install reportbug
>> ...
>> Please enter the name of the package: geda-gaf
>> Checking status database...
>> Traceback (most recent call last):
>…
>> return codecs.ascii_decode(input, self.errors)[0]
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xd8 in
>position 327: ordinal not in range(128)
>
>The package has "أحمد المحمودي (Ahmed El-Mahmoudy)
>" as uploader.
>And that is not parsable by your non Unicode environment.
>
>> Presumably there's some non-ascii something somewhere that's tripping
>it
>> up. It is 100% reproducible, and as you can see I'm using the latest
>> available reportbug. Thanks.
>
>I can reproduce it with LC_ALL=C, but not with C.UTF-8.
>
>I would argue that reportbug can't do anything here, as your
>environment just can't display the string correctly.

Hi. Reportbug can do some set of these:

1. Tell me what is wrong and how I can make it work instead of throwing an 
opaque exception. I never did report that bug

2. Turn on whatever setting it needs. Is it just an incompatible environment 
setting? If I set LC_ALL to C.UTF-8 then this will magically work? What does 
this setting mean? Can reportbug set this?

3. If reportbug can't display some unicode string, can it simply not display 
it, or display an ascii version of it (this was available here)? The bug report 
it generates can still contain the unicode.

Any of these would be an improvement. Thanks

Bug#858096: [mate-panel?] Mate panel unstable, notification area icons disappear without warning

[michael (C0bb3r)]

Hi Adrian

On 19/03/17 09:43, John Paul Adrian Glaubitz wrote:

Hello!

On 03/18/2017 11:07 PM, michael (C0bb3r) wrote:

Thanks for your assistance. The .xsession-errors, syslog, and  dmesg files are 
attached. Also attached are a couple of screenshots showing what I mean.

Attaching large files to bug reports should be avoided. It would have been 
better to upload
the screenshots to a webspace. And screenshots should also be sent on request 
only as they
aren't really necessary in most cases. But, oh well.

Duly noted.

Anyway, from your .xsession-errors there seem to be two warnings which could be 
related to
your problem:

(mate-panel:1286): Gtk-WARNING **: Negative content width -3 (allocation 15, 
extents 9x9) while allocating gadget (node button, owner PanelActionButton)
(mate-panel:1286): Gtk-WARNING **: Allocating size to GtkAlignment 
0x55cfb821bdf0 without calling gtk_widget_get_preferred_width/height(). How 
does the code
know the size to allocate?

Other than that, there are also lots of theme-related warnings and since you 
have such a
fancy theme, I'd try resetting the theme as first attempt. If that doesn't 
help, we need
to investigate the two warnings above.
Switching themes has this effect: n.b. using only standard themes and 
associated icons no modifications apart from added shutdown made.

Blackbird - lose all notification icons apart from shutdown.
Blackmate - all icons appear.
Bluementa - lose bluetooth icon.
Blue Submarine - same as Blackbird.
Green Laguna - as above.
Green Submarine - as above.
Greybird - as above.
High contrast - as above and also get error "Clock has quit unexpectedly".
High contrast inverse - all icons appear.
Menta - same as Blackbird.
Traditional Green - as above.
Traditional OK - all icons appear.

Process used - I switched from one theme to another until icons 
appeared. Then switched from working theme (e.g. Blackmate) to another 
theme (e.g. Blackbird) to see effect. Each switch went from a working 
theme to a different theme.


I will use Traditional OK today and see how long the icons stay, 
tomorrow I will switch to Blackmate and test it. I will report back if 
the icons disappear from these two themes.


Cheers.
Michael.

Bug#858096: [mate-panel?] Mate panel unstable, notification area icons disappear without warning

[John Paul Adrian Glaubitz]

Hello!

On 03/18/2017 11:07 PM, michael (C0bb3r) wrote:
> Thanks for your assistance. The .xsession-errors, syslog, and  dmesg files 
> are attached. Also attached are a couple of screenshots showing what I mean.

Attaching large files to bug reports should be avoided. It would have been 
better to upload
the screenshots to a webspace. And screenshots should also be sent on request 
only as they
aren't really necessary in most cases. But, oh well.

Anyway, from your .xsession-errors there seem to be two warnings which could be 
related to
your problem:

(mate-panel:1286): Gtk-WARNING **: Negative content width -3 (allocation 15, 
extents 9x9) while allocating gadget (node button, owner PanelActionButton)
(mate-panel:1286): Gtk-WARNING **: Allocating size to GtkAlignment 
0x55cfb821bdf0 without calling gtk_widget_get_preferred_width/height(). How 
does the code
know the size to allocate?

Other than that, there are also lots of theme-related warnings and since you 
have such a
fancy theme, I'd try resetting the theme as first attempt. If that doesn't 
help, we need
to investigate the two warnings above.

This is unrelated, but:

> I am very well aware that I have an external source on my system. I added it 
> so I could get a package for flash which is, unfortunately, still a 
> requirement on
> some websites.

Debian has its own flashplugin-nonfree installer for the Flash package.

> Many Debian Derivatives have external sources, infact one of the Debian pages 
> concerning Derivatives recommends using Debian as the base and
> adding external sources for other things that are required (1). As it is I 
> have 1 external package on 1 machine (that last message was from my laptop I 
> am
> currently on my desktop) and the problem is on both and has been since a few 
> minutes after the installation was finished not including the old install.

The wiki page you linked outlines the guidelines for developers who want to 
create their
own derivative of Debian so that their works doesn't interfere with Debian and 
does not
violate any trademark/branding issues. This guide is not for end users and it 
most certainly
does not encourage the creation of a FrankenDebian. Anyway, this is off-topic, 
but you
should be aware that using a FrankenDebian is at your own risk.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Rebecca N. Palmer]

Can this be fixed in time for Ubuntu 17.04?  Their mesa is built against 
LLVM 4.0, so if this bug isn't fixed, I (as beignet maintainer) have to 
choose between "apply a very new 4.0-support patch that might or might 
not work" and "leave beignet on 3.9, making OpenCL+OpenGL applications 
(e.g. blender) subject to this bug".



I've been told that there is a command line to add a version to all symbols
without a script, that should be enough at least for Debian packaging.
-Wl,--default-symver : rarely used (only 5 packages), and forces the 
symbol version to be the soname (i.e. libLLVM-3.9.so.1) rather than the 
conventional LLVM_3.9 form (i.e. potential binary incompatibility if 
upstream later decide to do it the conventional way), but should at 
least fix this crash.


The attached debdiff is for this option, and also fixes #857623 and 
#857683.  Warning: has NOT been tested yet.


I intend to try extending the earlier "version script" patch to also 
cover libclang and liblldb tomorrow.
diff -Nru llvm-toolchain-3.9-3.9.1/debian/changelog 
llvm-toolchain-3.9-3.9.1/debian/changelog
--- llvm-toolchain-3.9-3.9.1/debian/changelog   2017-03-12 09:01:10.0 
+
+++ llvm-toolchain-3.9-3.9.1/debian/changelog   2017-03-18 21:33:53.0 
+
@@ -1,3 +1,11 @@
+llvm-toolchain-3.9 (1:3.9.1-5local1) UNRELEASED; urgency=medium
+
+  * Allow '!pointer' in OpenCL (Closes: #857623)
+  * Add missing liblldb symlink (Closes: #857683)
+  * Use versioned symbols (Closes: #848368)
+
+ -- Rebecca N. Palmer   Sat, 18 Mar 2017 21:29:25 
+
+
 llvm-toolchain-3.9 (1:3.9.1-5) unstable; urgency=medium
 
   * Fix the incorrect symlink to scan-build-py (Closes: #856869)
diff -Nru llvm-toolchain-3.9-3.9.1/debian/liblldb-X.Y.links.in 
llvm-toolchain-3.9-3.9.1/debian/liblldb-X.Y.links.in
--- llvm-toolchain-3.9-3.9.1/debian/liblldb-X.Y.links.in2016-08-08 
16:02:20.0 +0100
+++ llvm-toolchain-3.9-3.9.1/debian/liblldb-X.Y.links.in2017-03-18 
17:33:17.0 +
@@ -1,3 +1,4 @@
 usr/lib/@DEB_HOST_MULTIARCH@/liblldb-@LLVM_VERSION@.so.1   
usr/lib/@DEB_HOST_MULTIARCH@/liblldb-@LLVM_VERSION@.so
 usr/lib/@DEB_HOST_MULTIARCH@/liblldb-@LLVM_VERSION@.so.1   
usr/lib/llvm-@LLVM_VERSION@/lib/liblldb.so.1
+usr/lib/@DEB_HOST_MULTIARCH@/liblldb-@LLVM_VERSION@.so.1   
usr/lib/llvm-@LLVM_VERSION@/lib/liblldb-@LLVM_VERSION@.so.1
 
diff -Nru 
llvm-toolchain-3.9-3.9.1/debian/patches/857623-allow-opencl-pointer-to-bool.diff
 
llvm-toolchain-3.9-3.9.1/debian/patches/857623-allow-opencl-pointer-to-bool.diff
--- 
llvm-toolchain-3.9-3.9.1/debian/patches/857623-allow-opencl-pointer-to-bool.diff
1970-01-01 01:00:00.0 +0100
+++ 
llvm-toolchain-3.9-3.9.1/debian/patches/857623-allow-opencl-pointer-to-bool.diff
2017-03-18 21:25:52.0 +
@@ -0,0 +1,20 @@
+Description: Allow "if (!pointer)" in OpenCL 1.1
+
+Used by e.g. Blender on mesa-opencl-icd
+
+Author: Anastasia Stulova
+Origin: upstream https://reviews.llvm.org/rL294313
+Bug: https://bugs.llvm.org/show_bug.cgi?id=30217
+Bug-Debian: https://bugs.debian.org/857623
+
+--- llvm-toolchain-3.9-3.9.1.orig/clang/lib/Sema/SemaExpr.cpp
 llvm-toolchain-3.9-3.9.1/clang/lib/Sema/SemaExpr.cpp
+@@ -11424,7 +11424,7 @@ ExprResult Sema::CreateBuiltinUnaryOp(So
+  Context.getLangOpts().OpenCLVersion < 120) {
+ // OpenCL v1.1 6.3.h: The logical operator not (!) does not
+ // operate on scalar float types.
+-if (!resultType->isIntegerType())
++if (!resultType->isIntegerType() && !resultType->isPointerType())
+   return ExprError(Diag(OpLoc, diag::err_typecheck_unary_expr)
+<< resultType << Input.get()->getSourceRange());
+   }
diff -Nru llvm-toolchain-3.9-3.9.1/debian/patches/series 
llvm-toolchain-3.9-3.9.1/debian/patches/series
--- llvm-toolchain-3.9-3.9.1/debian/patches/series  2017-01-27 
09:03:47.0 +
+++ llvm-toolchain-3.9-3.9.1/debian/patches/series  2017-03-18 
21:20:57.0 +
@@ -47,3 +47,4 @@
 amdgpu-regression.diff
 esan-Fix-ESan-test-failure-on-Debian-Sid-bot.diff
 esan-Fix-ESan-test-failure-on-Debian-Sid-bot2.diff
+857623-allow-opencl-pointer-to-bool.diff
diff -Nru llvm-toolchain-3.9-3.9.1/debian/rules 
llvm-toolchain-3.9-3.9.1/debian/rules
--- llvm-toolchain-3.9-3.9.1/debian/rules   2017-01-26 08:35:04.0 
+
+++ llvm-toolchain-3.9-3.9.1/debian/rules   2017-03-18 17:25:11.0 
+
@@ -24,7 +24,7 @@
 
 OCAML_STDLIB_DIR?= $(shell ocamlc -where)
 
-LDFLAGS_EXTRA =
+LDFLAGS_EXTRA = -Wl,--default-symver
 CXXFLAGS_EXTRA = -std=c++0x
 CONFIGURE_EXTRA =
 CMAKE_EXTRA =

Bug#857167: marked as done (autodocktools: broken symlink: /usr/bin/autoligand -> ../share/pyshared/AutoDockTools/AutoLigand.py)

[Debian Bug Tracking System]

Your message dated Sat, 18 Mar 2017 23:38:24 +0100
with message-id <20170318223822.ga8...@ugent.be>
and subject line 857167 fixed in 1.5.7-2
has caused the Debian Bug report #857167,
regarding autodocktools: broken symlink: /usr/bin/autoligand -> 
../share/pyshared/AutoDockTools/AutoLigand.py
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.)


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

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

1m28.0s ERROR: FAIL: Broken symlinks:
  /usr/bin/autoligand -> ../share/pyshared/AutoDockTools/AutoLigand.py

But there is /usr/lib/python2.7/dist-packages/AutoDockTools/AutoLigand.py


cheers,

Andreas


mgltools-pmv_1.5.7-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1.5.7-2

Hi,

This bug is fixed in the latest upload.

Cheers,

Ivo--- End Message ---

Processed: fixing wrong affects

[Debian Bug Tracking System]

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

> # cleaning up last but one line of msg 96 in #760853
> affects 760853 - usertag 710257 piuparts
Bug #760853 [jitsi] jitsi uninstallable
Bug #779521 [jitsi] jitsi uninstallable
Bug #779522 [jitsi] jitsi uninstallable
Bug #789038 [jitsi] jitsi uninstallable
Bug #831232 [jitsi] jitsi uninstallable
Bug #833902 [jitsi] jitsi uninstallable
Removed indication that 760853 affects usertag, 710257, and piuparts
Removed indication that 779521 affects usertag, 710257, and piuparts
Removed indication that 779522 affects usertag, 710257, and piuparts
Removed indication that 789038 affects usertag, 710257, and piuparts
Removed indication that 831232 affects usertag, 710257, and piuparts
Removed indication that 833902 affects usertag, 710257, and piuparts
> # though i'm not fully sure what you really ment, Andreas…
> usertag 710257 piuparts
User is hol...@layer-acht.org
There were no usertags set.
Usertags are now: piuparts.
> # not sure if 760853 should affect a package too and which…
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
710257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710257
760853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760853
779521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779521
779522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779522
789038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789038
831232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831232
833902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855951: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

[Michael Biebl]

Hi Charsten

Am 18.03.2017 um 19:57 schrieb Carsten Leonhardt:
> Control: tags -1 patch pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for libsecret (versioned as 0.18.5-3.1) and am
> about to upload it to DELAYED/5. Please feel free to tell me if I should
> delay it longer.
> 

If you are sure it fixes the issue, feel free to upload without delay.

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



signature.asc
Description: OpenPGP digital signature

Bug#858123: marked as done (glance-api: Automatic installation/configuration via debconf fails without net-tools)

[Debian Bug Tracking System]

Your message dated Sat, 18 Mar 2017 22:03:59 +
with message-id 
and subject line Bug#858123: fixed in glance 2:13.0.0-3
has caused the Debian Bug report #858123,
regarding glance-api: Automatic installation/configuration via debconf fails 
without net-tools
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.)


-- 
858123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glance-api
Version: 2:13.0.0-2
Severity: normal

Dear Maintainer,

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

# apt-get install net-tools
on a freshly installed system

   * What was the outcome of this action?

http://paste.debian.net/922549/

   * What outcome did you expect instead?

Successful configuration. The issue is likely caused by a missing dependency to 
net-tools


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

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: No such file or directory
UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages glance-api depends on:
ii  adduser 3.115
ii  debconf [debconf-2.0]   1.5.60
ii  glance-common   2:13.0.0-2
ii  init-system-helpers 1.47
ii  lsb-base9.20161125
ii  python-openstackclient  3.2.1-1
ii  python-q-text-as-data [q-text-as-data]  1.4.0-1
pn  python2.7:any   

Versions of packages glance-api recommends:
ii  python-glanceclient  1:2.5.0-3

glance-api suggests no packages.

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: glance
Source-Version: 2:13.0.0-3

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

Debian distribution maintenance software
pp.
David Rabel  (supplier of updated glance 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, 18 Mar 2017 19:06:26 +0100
Source: glance
Binary: python-glance glance python-glance-doc glance-common glance-api 
glance-glare glance-registry
Architecture: source all
Version: 2:13.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: David Rabel 
Description:
 glance - OpenStack Image Registry and Delivery Service - Daemons
 glance-api - OpenStack Image Registry and Delivery Service - API server
 glance-common - OpenStack Image Registry and Delivery Service - common files
 glance-glare - OpenStack Artifacts - API server
 glance-registry - OpenStack Image Registry and Delivery Service - registry 
server
 python-glance - OpenStack Image Registry and Delivery Service - Python library
 python-glance-doc - OpenStack Image Registry and Delivery Service - 
Documentation
Closes: 858123
Changes:
 glance (2:13.0.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Added dependency: net-tools ( Closes: #858123 )
Checksums-Sha1:
 e61842033526b4140ffd79ba698745f6bdfdffd2 4092 glance_13.0.0-3.dsc
 35e748d243dcd2868503182ec3cbec0fb5986426 37064 glance_13.0.0-3.debian.tar.xz
 a0ae0c00b46810ff5683a2c7d0b6b610591d36d4 45674 glance-api_13.0.0-3_all.deb
 2693fa4645b09712cce3c7ccc9fd0c2d3d4adb6d 94956 glance-common_13.0.0-3_all.deb
 f64303dae6d0e24229786e49e1d1704d7d857be5 14052 glance-glare_13.0.0-3_all.deb
 3e2fb9d07a46a60c6d9d08fd9ed0af53078edb90 15870 glance-registry_13.0.0-3_all.deb
 43bfaafa3aa5b296952538f2027bc747a00e0a24 10972 glance_13.0.0-3_all.deb
 dc4cb2f6147d5207135b57e8e63a97e5491f057e 17136 glance_13.0.0-3_amd64.buildinfo
 bd6950b5bc14660c45810f8ad3280f8433488c17 654698 
python-glance-doc_13.0.0-3_all.deb
 482aa03fb0d354d5c73029b73803c6b3420d229d 750648 

Bug#734837: tk8.4: Time to remove from testing

[Mattia Rizzolo]

Hi!

On Thu, Mar 09, 2017 at 02:34:38PM +0300, Sergei Golovan wrote:
> > So are you fine if I file a RoQA for those?  (or will send a ROM?)
> 
> I'll send a ROM. I think it's nicer to do that.

I haven't seen it coming, is anything blocking it?
FWIW now also the single blocking package is gone, and `dak rm` reports
"No dependency problem found." :)

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#858122: Upgrade linux kernel to 4.9.15 in sid and stretch

[Ben Hutchings]

On Sat, Mar 18, 2017 at 10:08:10PM +0100, Julien Aubin wrote:
> OK I did this. Does it have a huge impact on the system except mitigating
> the flaw ? (I don't think I have an HDLC hardware...)

If you don't know whether you have it, you don't have it. :-)

Ben.

-- 
Ben Hutchings
Life is like a sewer:
what you get out of it depends on what you put into it.


signature.asc
Description: Digital signature

Processed: Re: gecode FTBFS on ppc64el: error: narrowing conversion of '18444492273895866370ull' from 'long long unsigned int' to 'gecode_boost::long_long_type {aka long long int}'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #858132 [src:gecode] gecode FTBFS on ppc64el: error: narrowing conversion 
of '1892273895866370ull' from 'long long unsigned int' to 
'gecode_boost::long_long_type {aka long long int}'
Added tag(s) patch.

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

Bug#858132: gecode FTBFS on ppc64el: error: narrowing conversion of '18444492273895866370ull' from 'long long unsigned int' to 'gecode_boost::long_long_type {aka long long int}'

[John Paul Adrian Glaubitz]

Control: tags -1 patch

Hi!

The attached debdiff contains a patch which fixes the issue for me. I changed
the type for imode inside rounding_mode_struct from long_long_type to its
unsigned counterpart ulong_long_type so that assigning the large unsigned
R-values wouldn't trigger the narrowing-conversion warning anymore:

--- 
gecode-4.4.0.orig/gecode/third-party/boost/numeric/interval/detail/ppc_rounding_control.hpp
+++ 
gecode-4.4.0/gecode/third-party/boost/numeric/interval/detail/ppc_rounding_control.hpp
@@ -24,7 +24,7 @@ namespace interval_lib {
 namespace detail {

 typedef union {
-   ::gecode_boost::long_long_type imode;
+   ::gecode_boost::ulong_long_type imode;
   double dmode;
 } rounding_mode_struct;

Successfully tested on the ppc64 porterbox pizzetti.debian.org. I couldn't
test on plummer.debian.org for ppc64el since the machine is down at the
moment.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
diff -Nru gecode-4.4.0/debian/changelog gecode-4.4.0/debian/changelog
--- gecode-4.4.0/debian/changelog	2015-09-05 23:20:35.0 +0300
+++ gecode-4.4.0/debian/changelog	2017-03-19 00:01:25.0 +0300
@@ -1,3 +1,12 @@
+gecode (4.4.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add ppc_use_ulong-long-type patch to use ulong_long_type inside
+rounding_mode_struct to fix narrowing conversion issue on all
+PowerPC targets. (Closes: #858132)
+
+ -- John Paul Adrian Glaubitz   Sat, 18 Mar 2017 22:01:25 +0100
+
 gecode (4.4.0-3) unstable; urgency=medium
 
   * Library transition for GCC 5 (Closes: #791042)
diff -Nru gecode-4.4.0/debian/patches/ppc_use_ulong-long-type gecode-4.4.0/debian/patches/ppc_use_ulong-long-type
--- gecode-4.4.0/debian/patches/ppc_use_ulong-long-type	1970-01-01 03:00:00.0 +0300
+++ gecode-4.4.0/debian/patches/ppc_use_ulong-long-type	2017-03-19 00:01:25.0 +0300
@@ -0,0 +1,15 @@
+Description: Use ulong_long_type for imode on PowerPC
+Author: John Paul Adrian Glaubitz 
+Last-Update: 2017-03-18
+
+--- gecode-4.4.0.orig/gecode/third-party/boost/numeric/interval/detail/ppc_rounding_control.hpp
 gecode-4.4.0/gecode/third-party/boost/numeric/interval/detail/ppc_rounding_control.hpp
+@@ -24,7 +24,7 @@ namespace interval_lib {
+ namespace detail {
+ 
+ typedef union {
+-   ::gecode_boost::long_long_type imode;
++   ::gecode_boost::ulong_long_type imode;
+   double dmode;
+ } rounding_mode_struct;
+ 
diff -Nru gecode-4.4.0/debian/patches/series gecode-4.4.0/debian/patches/series
--- gecode-4.4.0/debian/patches/series	2015-04-29 22:47:28.0 +0300
+++ gecode-4.4.0/debian/patches/series	2017-03-19 00:01:25.0 +0300
@@ -1,2 +1,3 @@
 no-O3
 bison-3-support
+ppc_use_ulong-long-type

Processed: Raising severity to serious, package is noninstallable without this dep

[Debian Bug Tracking System]

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

> severity 858123 serious
Bug #858123 [glance-api] glance-api: Automatic installation/configuration via 
debconf fails without net-tools
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#858122: Upgrade linux kernel to 4.9.15 in sid and stretch

[Julien Aubin]

OK I did this. Does it have a huge impact on the system except mitigating
the flaw ? (I don't think I have an HDLC hardware...)

2017-03-18 21:54 GMT+01:00 Ben Hutchings :

> On Sat, 2017-03-18 at 17:01 +0100, Julien Aubin wrote:
> > Source: linux
> > Severity: critical
> > Tags: security
> > Justification: root security hole
> >
> > Hi,
> >
> > Security issue CVE-2017-2636 (severity 7.8) has been disclosed and the
> fix
> > has
> > been provided for Jessie and Wheezy. The problem is that there's as of
> now
> > no
> > fix available for sid and stretch while things become more and more
> critical
> > due to the severity of the issue.
> >
> > Kernel 4.9.15 contains a fix for this. Could you please integrate it
> ASAP on
> > Stretch ?
> [...]
>
> Note that we already documented a mitigation for this in the DSA.
>
> Ben.
>
> --
> Ben Hutchings
> Editing code like this is akin to sticking plasters on the bleeding
> stump
> of a severed limb. - me, 29 June 1999
>
>

Processed: severity of 858125 is important

[Debian Bug Tracking System]

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

> severity 858125 important
Bug #858125 [src:linux] e1000: ethernet interface hangs occasionally, kernel 
reports hang
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#858122: Upgrade linux kernel to 4.9.15 in sid and stretch

[Ben Hutchings]

On Sat, 2017-03-18 at 17:01 +0100, Julien Aubin wrote:
> Source: linux
> Severity: critical
> Tags: security
> Justification: root security hole
> 
> Hi,
> 
> Security issue CVE-2017-2636 (severity 7.8) has been disclosed and the fix
> has
> been provided for Jessie and Wheezy. The problem is that there's as of now
> no
> fix available for sid and stretch while things become more and more critical
> due to the severity of the issue.
> 
> Kernel 4.9.15 contains a fix for this. Could you please integrate it ASAP on
> Stretch ?
[...]

Note that we already documented a mitigation for this in the DSA.

Ben.

-- 
Ben Hutchings
Editing code like this is akin to sticking plasters on the bleeding
stump
of a severed limb. - me, 29 June 1999



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

Bug#858132: gecode FTBFS on ppc64el: error: narrowing conversion of '18444492273895866370ull' from 'long long unsigned int' to 'gecode_boost::long_long_type {aka long long int}'

[Kari Pahula]

On Sat, Mar 18, 2017 at 08:08:55PM +0200, Adrian Bunk wrote:
> Source: gecode
> Version: 4.4.0-3
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=gecode=ppc64el=4.4.0-3%2Bb1=1489745301=0

Aside from some namespacing changes, the ppc_rounding_control.hpp
included with Gecode is identical to the current libboost-dev version.
Is there an binNMU scheduled for Boost?  I'd expect the issue to exist
there also.

Bug#857794: reportbug: crash when encountering some non-ASCII characters

[Evgeni Golov]

Hi Dima,

> Hi. I just tried to send an unblock, and reportbug crashed. Session:
> 
> dima@scrawny:~$ sudo apt install reportbug
> ...
> Please enter the name of the package: geda-gaf
> Checking status database...
> Traceback (most recent call last):
…
> return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xd8 in position 327: 
> ordinal not in range(128)

The package has "أحمد المحمودي (Ahmed El-Mahmoudy) 
" as uploader.
And that is not parsable by your non Unicode environment.

> Presumably there's some non-ascii something somewhere that's tripping it
> up. It is 100% reproducible, and as you can see I'm using the latest
> available reportbug. Thanks.

I can reproduce it with LC_ALL=C, but not with C.UTF-8.

I would argue that reportbug can't do anything here, as your environment just 
can't display the string correctly.

Bug#857972: marked as done (tagainijisho: uninstallable after binNMU)

[Debian Bug Tracking System]

Your message dated Sat, 18 Mar 2017 19:20:54 +
with message-id 
and subject line Bug#857972: fixed in tagainijisho 1.0.2-2
has caused the Debian Bug report #857972,
regarding tagainijisho: uninstallable after binNMU
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.)


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

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 tagainijisho : Depends: tagainijisho-common (= 1.0.2-1+b1) but 1.0.2-1 is to 
be installed

This is caused by using
  dh_installdocs --link-doc
from an arch:any to an arch:all package.


Cheers,


Andreas
--- End Message ---
--- Begin Message ---
Source: tagainijisho
Source-Version: 1.0.2-2

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated tagainijisho package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 18 Mar 2017 20:05:13 +0100
Source: tagainijisho
Binary: tagainijisho tagainijisho-common tagainijisho-dic-en 
tagainijisho-dic-fr tagainijisho-dic-de tagainijisho-dic-es tagainijisho-dic-ru 
tagainijisho-dic-it tagainijisho-dic-pt tagainijisho-dic-th tagainijisho-dic-tr
Architecture: source
Version: 1.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 tagainijisho - Japanese dictionary and learning assistant
 tagainijisho-common - Common files for Tagaini Jisho
 tagainijisho-dic-de - German dictionary files for Tagaini Jisho
 tagainijisho-dic-en - English dictionary files for Tagaini Jisho
 tagainijisho-dic-es - Spanish dictionary files for Tagaini Jisho
 tagainijisho-dic-fr - French dictionary files for Tagaini Jisho
 tagainijisho-dic-it - Italian dictionary files for Tagaini Jisho
 tagainijisho-dic-pt - Portuguese dictionary files for Tagaini Jisho
 tagainijisho-dic-ru - Russian dictionary files for Tagaini Jisho
 tagainijisho-dic-th - Thai dictionary files for Tagaini Jisho
 tagainijisho-dic-tr - Turkish dictionary files for Tagaini Jisho
Closes: 857972
Changes:
 tagainijisho (1.0.2-2) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group (See: #830766)
   * d/rules: Use dh for the build/build-arch/build-indep targets to get
 support for override_dh_*-arch/indep.
   * Do not use dh_installdocs --link-doc between arch:any and arch:all
 packages.  (Closes: #857972)
Checksums-Sha1:
 276611657cd3df6dab9547dc8b53ab93ef402a39 2536 tagainijisho_1.0.2-2.dsc
 bd6460a1b2370237aeb7602290b20684d1177825 11680 
tagainijisho_1.0.2-2.debian.tar.xz
 fff737696b67ccd1a79a9aa4c48df4752a92ab5f 6878 
tagainijisho_1.0.2-2_source.buildinfo
Checksums-Sha256:
 c3b7bbeb11d79a22012df22be07c081e08668f1309b198b5ec2353008e053c0e 2536 
tagainijisho_1.0.2-2.dsc
 a2dc770e7409234c298443e045fe345e4faacbf6c54719a691c28b8e3fe3167e 11680 
tagainijisho_1.0.2-2.debian.tar.xz
 9af69de0ca7ef2f7a04a42b8b05ab4f2675ac143a64f402cd5a6c3d2ddbc1403 6878 
tagainijisho_1.0.2-2_source.buildinfo
Files:
 331eb11d8a7ba1fb3799863ea00d6bed 2536 education extra tagainijisho_1.0.2-2.dsc
 f958730647c93b8cba8a9be86c742819 11680 education extra 
tagainijisho_1.0.2-2.debian.tar.xz
 de475eb37c7df20310991c3eec8c5a7e 6878 education extra 
tagainijisho_1.0.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYzYVfAAoJEF+zP5NZ6e0IATQP/iUYwoDg0hST8coHTa23i7vx
iZpgjCsOAQVef3JOpcbEuCWiVgjYZcR4LCX/k3CHV3Z5sdnAJD5LV5nuIYpGXkg5
v5AKvUYGUphlYlfdjcTs5pgwwwqzCGpWuCjlAX1UJZxofo+tMZFQaY3QKiYub0F8
J1T9p+N+wz5G1NLMQVK+kQhM3Vu8qbvrxbJtmk8qrYI3CJl/wWV4VLL6C72W4/iN
K0/Xu/5j05rpbKGe2NN3uwgNNMkCLIdxIk4JERxoeRTIhI7tfBk2YNaZtWYdhF7f

Bug#856024: Processed: Adding a conflict in systemd-sysv

[Michael Biebl]

Am 18.03.2017 um 19:11 schrieb Francois Marier:
> Control: reassign -1 systemd-sysv
> 
>> This looks like a genuine bug in molly-guard,
> 
> Yes and that's tracked in bug #837928.

And why is that bug not treated as RC then?

> The present bug is specifically about the interaction between
> molly-guard and systemd-sysv.

No, it's in the broken dpkg-divert handling of molly-guard. You can't
blame systemd-sysv here.

>> so this RC bug should be assigned to molly-guard.
>>
>> Adding a Breaks to systemd-sysv is backwards.
> 
> If the underlying bug was going to be fixed in time for stretch, then
> sure, that would be ideal. However, that's not going to happen in time.
> 
> The breaks/conflict seems like the best option to resolve this issue
> without removing molly-guard entirely from the release.
> 

Well, if molly-guard does not work with the default init system, it
doesn't seem like it's in a releasable state and it should indeed be
removed from stretch.
As such this RC bugs needs to be assigned to molly-guard and not
systemd. Or #837928 needs to be made RC, in which point this bug report
against systemd-sysv is pointless.

Adding a Conflicts to systemd might even be considered a policy violation.

Asking the release team for their input.

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



signature.asc
Description: OpenPGP digital signature

Processed: tagging 858046

[Debian Bug Tracking System]

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

> tags 858046 + unreproducible
Bug #858046 [logtool] logtool: uninstallable
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#845323: Issue resolved

[Evgeni Golov]

Hi

On Mon, Dec 05, 2016 at 02:21:24PM +0100, pyt...@gmx.li wrote:
> After playing around a while with the packets I could figure out, that the 
> package is working with the stable version of "python-ethtool" (currently 
> 0.11-2).

Thanks for the report and the debugging.
This could be https://bugs.debian.org/857346

Can you please test the packages at [1] which contain a patch for the above bug?

Regards
Evgeni

[1] https://people.debian.org/~evgeni/tmp/python-ethtool/

Processed: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #855951 [src:libsecret] libsecret FTBFS with test failures on many 
architectures
Added tag(s) pending and patch.

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

Bug#855951: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

[Carsten Leonhardt]

Control: tags -1 patch pending

Dear maintainer,

I've prepared an NMU for libsecret (versioned as 0.18.5-3.1) and am
about to upload it to DELAYED/5. Please feel free to tell me if I should
delay it longer.

After the package enters unstable, I'll open another bug for the release
team to unblock it.

 - Carsten

diff -Nru libsecret-0.18.5/debian/changelog libsecret-0.18.5/debian/changelog
--- libsecret-0.18.5/debian/changelog	2017-02-21 22:57:01.0 +0100
+++ libsecret-0.18.5/debian/changelog	2017-03-18 16:56:31.0 +0100
@@ -1,3 +1,12 @@
+libsecret (0.18.5-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/0004-tests-collection-add-setup-delay.patch:
++ Fix failing test "collection/delete-sync" by correctly placing
+  the delay. Closes: #855951.
+
+ -- Carsten Leonhardt   Sat, 18 Mar 2017 15:56:31 +
+
 libsecret (0.18.5-3) unstable; urgency=medium
 
   [ Jeremy Bicha ]
diff -Nru libsecret-0.18.5/debian/patches/0004-tests-collection-add-setup-delay.patch libsecret-0.18.5/debian/patches/0004-tests-collection-add-setup-delay.patch
--- libsecret-0.18.5/debian/patches/0004-tests-collection-add-setup-delay.patch	2017-02-21 22:56:07.0 +0100
+++ libsecret-0.18.5/debian/patches/0004-tests-collection-add-setup-delay.patch	2017-03-18 16:55:44.0 +0100
@@ -2,9 +2,14 @@
 Bug: https://bugzilla.gnome.org/show_bug.cgi?id=779041
 Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837067
 
 a/libsecret/test-collection.c
-+++ b/libsecret/test-collection.c
-@@ -56,6 +56,8 @@
+Update by Carsten Leonhardt : move sleep(1) to the
+beginning of teardown() to address bug #855951
+
+Index: libsecret-0.18.5/libsecret/test-collection.c
+===
+--- libsecret-0.18.5.orig/libsecret/test-collection.c
 libsecret-0.18.5/libsecret/test-collection.c
+@@ -56,12 +56,15 @@ setup (Test *test,
  	test->service = secret_service_get_sync (SECRET_SERVICE_NONE, NULL, );
  	g_assert_no_error (error);
  	g_object_add_weak_pointer (G_OBJECT (test->service), (gpointer *)>service);
@@ -13,11 +18,10 @@
  }
  
  static void
-@@ -67,6 +69,7 @@
- 	g_assert (test->service == NULL);
- 
- 	mock_service_stop ();
+ teardown (Test *test,
+   gconstpointer unused)
+ {
 +	sleep(1);
- }
- 
- static void
+ 	g_object_unref (test->service);
+ 	secret_service_disconnect ();
+ 	g_assert (test->service == NULL);

Processed: Re: openhpi: debug symbol packages in wrong archive

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #852433 [src:openhpi] openhpi: debug symbol packages in wrong archive
Added tag(s) patch and pending.

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

Bug#852433: openhpi: debug symbol packages in wrong archive

[Andreas Beckmann]

Followup-For: Bug #852433
Control: tag -1 patch pending

Hi,

I just uploaded the attached patch as a NMU to DELAYED/5. Please let me
know if I should delay it longer or reschedule.

Greetings from the credativ BSP.


Andreas
diff -Nru openhpi-3.6.1/debian/changelog openhpi-3.6.1/debian/changelog
--- openhpi-3.6.1/debian/changelog	2017-01-18 20:45:48.0 +0100
+++ openhpi-3.6.1/debian/changelog	2017-03-18 17:13:16.0 +0100
@@ -1,3 +1,13 @@
+openhpi (3.6.1-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove -dbgsym packages from debian/control, these are autogenerated by
+dh_strip.  (Closes: #852433)
+  * Move the plugin .so links into the plugin packages.  (Closes: #615955)
+  * libopenhpi3.postrm: Drop manual ldconfig call.
+
+ -- Andreas Beckmann   Sat, 18 Mar 2017 17:13:16 +0100
+
 openhpi (3.6.1-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru openhpi-3.6.1/debian/control openhpi-3.6.1/debian/control
--- openhpi-3.6.1/debian/control	2017-01-18 20:45:42.0 +0100
+++ openhpi-3.6.1/debian/control	2017-03-18 16:01:20.0 +0100
@@ -70,7 +70,8 @@
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, libopenhpi3 (= ${binary:Version})
 Conflicts: libopenhpi, libopenhpi2
-Replaces: libopenhpi, libopenhpi2
+Breaks: libopenhpi3 (<< 3.6.1-2.2~)
+Replaces: libopenhpi, libopenhpi2, libopenhpi3 (<< 3.6.1-2.2~)
 Description: OpenHPI plugin module for HP's ProLiant rackmount servers
  OpenHPI is an implementation of the Service Availability Forum's Hardware
  Platform Interface specification.  (See http://www.saforum.org)  As
@@ -86,7 +87,8 @@
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, libopenhpi3 (= ${binary:Version}), libopenipmi0 (>=2.0.7), openipmi (>=2.0.7)
 Conflicts: libopenhpi, libopenhpi2
-Replaces: libopenhpi, libopenhpi2
+Breaks: libopenhpi3 (<< 3.6.1-2.2~)
+Replaces: libopenhpi, libopenhpi2, libopenhpi3 (<< 3.6.1-2.2~)
 Description: OpenHPI plugin module for OpenIPMI
  OpenHPI is an implementation of the Service Availability Forum's Hardware
  Platform Interface specification.  (See http://www.saforum.org)  As
@@ -101,7 +103,8 @@
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, libopenhpi3 (= ${binary:Version})
 Conflicts: libopenhpi, libopenhpi2
-Replaces: libopenhpi, libopenhpi2
+Breaks: libopenhpi3 (<< 3.6.1-2.2~)
+Replaces: libopenhpi, libopenhpi2, libopenhpi3 (<< 3.6.1-2.2~)
 Description: OpenHPI plugin module for direct IPMI over LAN (RMCP) or SMI
  OpenHPI is an implementation of the Service Availability Forum's Hardware
  Platform Interface specification.  (See http://www.saforum.org)  As
@@ -116,7 +119,8 @@
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, libopenhpi3 (= ${binary:Version})
 Conflicts: libopenhpi, libopenhpi2
-Replaces: libopenhpi, libopenhpi2
+Breaks: libopenhpi3 (<< 3.6.1-2.2~)
+Replaces: libopenhpi, libopenhpi2, libopenhpi3 (<< 3.6.1-2.2~)
 Description: OpenHPI plugin module for HP's BladeSystem c-Class
  OpenHPI is an implementation of the Service Availability Forum's Hardware
  Platform Interface specification.  (See http://www.saforum.org)  As
@@ -132,7 +136,8 @@
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, libopenhpi3 (= ${binary:Version})
 Conflicts: libopenhpi, libopenhpi2
-Replaces: libopenhpi, libopenhpi2
+Breaks: libopenhpi3 (<< 3.6.1-2.2~)
+Replaces: libopenhpi, libopenhpi2, libopenhpi3 (<< 3.6.1-2.2~)
 Description: OpenHPI plugin module for slave plugin
  OpenHPI is an implementation of the Service Availability Forum's Hardware
  Platform Interface specification.  (See http://www.saforum.org)  As
@@ -147,7 +152,8 @@
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, libopenhpi3 (= ${binary:Version})
 Conflicts: libopenhpi, libopenhpi2
-Replaces: libopenhpi, libopenhpi2
+Breaks: libopenhpi3 (<< 3.6.1-2.2~)
+Replaces: libopenhpi, libopenhpi2, libopenhpi3 (<< 3.6.1-2.2~)
 Description: OpenHPI plugin module for test agent plugin
  OpenHPI is an implementation of the Service Availability Forum's Hardware
  Platform Interface specification.  (See http://www.saforum.org)  As
@@ -161,7 +167,8 @@
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, libopenhpi3 (= ${binary:Version})
 Conflicts: libopenhpi, libopenhpi2
-Replaces: libopenhpi, libopenhpi2
+Breaks: libopenhpi3 (<< 3.6.1-2.2~)
+Replaces: libopenhpi, libopenhpi2, libopenhpi3 (<< 3.6.1-2.2~)
 Description: OpenHPI plugin module for IBM's BladeCenter or RSA over SNMP
  OpenHPI is an implementation of the Service Availability Forum's Hardware
  Platform Interface specification.  (See http://www.saforum.org)  As
@@ -177,7 +184,8 @@
 Architecture: linux-any
 Depends: ${shlibs:Depends}, ${misc:Depends}, libopenhpi3 (= ${binary:Version})
 Conflicts: libopenhpi, libopenhpi2
-Replaces: libopenhpi, libopenhpi2
+Breaks: libopenhpi3 (<< 3.6.1-2.2~)
+Replaces: libopenhpi, libopenhpi2, libopenhpi3 (<< 3.6.1-2.2~)
 Description: OpenHPI 

Bug#858133: python-tz: FTBFS: AssertionError: '+0020+0020' != 'NET+0020'

[Chris Lamb]

Source: python-tz
Version: 2016.7-0.2
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,

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

  […]

  tzname, str(utc_dt), dt.tzname()
  E   AssertionError: Expected WSDT as tzname for 2011-12-30 11:00:00+00:00. 
Got +14
  _ SamoaInternationalDateLineChange.testTwoHoursBefore 
__
  
  self = 
  
  def testTwoHoursBefore(self):
  self._test_all(
  >   self.transition_time - timedelta(hours=2), self.before
  )
  
  pytz/tests/test_tzinfo.py:302: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  pytz/tests/test_tzinfo.py:292: in _test_all
  self._test_tzname(utc_dt, wanted)
  pytz/tests/test_tzinfo.py:241: in _test_tzname
  tzname, str(utc_dt), dt.tzname()
  E   AssertionError: Expected SDT as tzname for 2011-12-30 08:00:00+00:00. Got 
-10
  __ LocalTestCase.testLocalize 
__
  
  self = 
  
  def testLocalize(self):
  loc_tz = pytz.timezone('Europe/Amsterdam')
  
  loc_time = loc_tz.localize(datetime(1930, 5, 10, 0, 0, 0))
  # Actually +00:19:32, but Python datetime rounds this
  self.assertEqual(loc_time.strftime('%Z%z'), 'AMT+0020')
  
  loc_time = loc_tz.localize(datetime(1930, 5, 20, 0, 0, 0))
  # Actually +00:19:32, but Python datetime rounds this
  self.assertEqual(loc_time.strftime('%Z%z'), 'NST+0120')
  
  loc_time = loc_tz.localize(datetime(1940, 5, 10, 0, 0, 0))
  >   self.assertEqual(loc_time.strftime('%Z%z'), 'NET+0020')
  E   AssertionError: '+0020+0020' != 'NET+0020'
  
  pytz/tests/test_tzinfo.py:614: AssertionError
   38 failed, 196 passed in 2.54 seconds 
=
  E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
«BUILDDIR»/.pybuild/pythonX.Y_2.7/build; python2.7 -m pytest 
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 
--before-test=   cp «BUILDDIR»/README.txt {build_dir};   cp -r 
/home/lamby/temp/cdt.20170318181551.yfmWAMyfvQ.db.python-tz/python-tz-2016.7/pytz/tests
 {build_dir}/pytz/ --after-test=rm -rf {build_dir}/README.txt 
{build_dir}/pytz/tests returned exit code 13
  debian/rules:9: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 25
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


python-tz.2016.7-0.2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#856024: Processed: Adding a conflict in systemd-sysv

[Francois Marier]

Control: reassign -1 systemd-sysv


This looks like a genuine bug in molly-guard,


Yes and that's tracked in bug #837928.

The present bug is specifically about the interaction between 
molly-guard and systemd-sysv.



so this RC bug should be assigned to molly-guard.

Adding a Breaks to systemd-sysv is backwards.


If the underlying bug was going to be fixed in time for stretch, then 
sure, that would be ideal. However, that's not going to happen in time.


The breaks/conflict seems like the best option to resolve this issue 
without removing molly-guard entirely from the release.


Francois

Processed: Re: Processed: Adding a conflict in systemd-sysv

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 systemd-sysv
Bug #856024 [molly-guard] molly-guard: causes failure to update systemd-sysv
Bug reassigned from package 'molly-guard' to 'systemd-sysv'.
No longer marked as found in versions molly-guard/0.6.4.
Ignoring request to alter fixed versions of bug #856024 to the same values 
previously set

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

Bug#858132: gecode FTBFS on ppc64el: error: narrowing conversion of '18444492273895866370ull' from 'long long unsigned int' to 'gecode_boost::long_long_type {aka long long int}'

[Adrian Bunk]

Source: gecode
Version: 4.4.0-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=gecode=ppc64el=4.4.0-3%2Bb1=1489745301=0

...
In file included from 
./gecode/third-party/boost/numeric/interval/hw_rounding.hpp:26:0,
 from ./gecode/third-party/boost/numeric/interval.hpp:18,
 from ./gecode/float.hh:82,
 from ./gecode/gist.hh:47,
 from ./gecode/gist/stopbrancher.hh:39,
 from gecode/gist/spacenode.cpp:40:
./gecode/third-party/boost/numeric/interval/detail/ppc_rounding_control.hpp: At 
global scope:
./gecode/third-party/boost/numeric/interval/detail/ppc_rounding_control.hpp:31:77:
 error: narrowing conversion of '1892273895866370ull' from 'long long 
unsigned int' to 'gecode_boost::long_long_type {aka long long int}' inside { } 
[-Wnarrowing]
 static const rounding_mode_struct mode_upward  = { 0xFFF80002LL };
 ^
./gecode/third-party/boost/numeric/interval/detail/ppc_rounding_control.hpp:32:77:
 error: narrowing conversion of '1892273895866371ull' from 'long long 
unsigned int' to 'gecode_boost::long_long_type {aka long long int}' inside { } 
[-Wnarrowing]
 static const rounding_mode_struct mode_downward= { 0xFFF80003LL };
 ^
./gecode/third-party/boost/numeric/interval/detail/ppc_rounding_control.hpp:33:77:
 error: narrowing conversion of '1892273895866368ull' from 'long long 
unsigned int' to 'gecode_boost::long_long_type {aka long long int}' inside { } 
[-Wnarrowing]
 static const rounding_mode_struct mode_to_nearest  = { 0xFFF8LL };
 ^
./gecode/third-party/boost/numeric/interval/detail/ppc_rounding_control.hpp:34:77:
 error: narrowing conversion of '1892273895866369ull' from 'long long 
unsigned int' to 'gecode_boost::long_long_type {aka long long int}' inside { } 
[-Wnarrowing]
 static const rounding_mode_struct mode_toward_zero = { 0xFFF80001LL };
 ^
...

Bug#857411: marked as done (libqpid-proton-cpp8-dev: missing Depends: libqpid-proton-cpp8 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Sat, 18 Mar 2017 18:05:07 +
with message-id 
and subject line Bug#857411: fixed in qpid-proton 0.14.0-5
has caused the Debian Bug report #857411,
regarding libqpid-proton-cpp8-dev: missing Depends: libqpid-proton-cpp8 (= 
${binary:Version})
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.)


-- 
857411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqpid-proton-cpp8-dev
Version: 0.14.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m19.2s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libqpid-proton-cpp.so -> libqpid-proton-cpp.so.8


The exisisting dependency on libqpid-proton8 is probably a copy+paste
error, since that is also implied by the dependency on
libqpid-proton8-dev.


cheers,

Andreas


libqpid-proton-cpp8-dev_0.14.0-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: qpid-proton
Source-Version: 0.14.0-5

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated qpid-proton 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: Fri, 10 Mar 2017 22:56:38 +0100
Source: qpid-proton
Binary: libqpid-proton8 libqpid-proton-cpp8 libqpid-proton8-dev 
libqpid-proton-cpp8-dev libqpid-proton8-dev-examples libqpid-proton8-dev-doc 
libqpid-proton-cpp8-dev-doc python-qpid-proton python3-qpid-proton 
python-qpid-proton-doc
Architecture: source
Version: 0.14.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Middleware Maintainers 

Changed-By: Ondřej Nový 
Description:
 libqpid-proton-cpp8 - C++ libraries for Qpid Proton
 libqpid-proton-cpp8-dev - C++ Development libraries for writing messaging apps 
with Qpid Pr
 libqpid-proton-cpp8-dev-doc - C++ developer documentation for Qpid Proton
 libqpid-proton8 - C libraries for Qpid Proton
 libqpid-proton8-dev - C Development libraries for writing messaging apps with 
Qpid Prot
 libqpid-proton8-dev-doc - Developer documentation for Qpid Proton
 libqpid-proton8-dev-examples - Example applications for writign messaging apps 
with Qpid Proton
 python-qpid-proton - language bindings for Qpid Proton messaging framework - 
Python 2.
 python-qpid-proton-doc - Documentation for the Python language bindings for 
Qpid Proton
 python3-qpid-proton - language bindings for Qpid Proton messaging framework - 
Python 3.
Closes: 857411
Changes:
 qpid-proton (0.14.0-5) unstable; urgency=medium
 .
   * Team upload.
   * Change libqpid-proton-cpp8-dev depend to libqpid-proton-cpp8
 (Closes: #857411)
Checksums-Sha1:
 2a3b2823f7084d3a43261d052f848743ea54c7b7 2964 qpid-proton_0.14.0-5.dsc
 50e5cbb1aa1567b3a8a2f7ecf76aa157133b3120 8220 
qpid-proton_0.14.0-5.debian.tar.xz
 8329db24f4044c38dfd87c70e576d180dd8d18ec 11694 
qpid-proton_0.14.0-5_amd64.buildinfo
Checksums-Sha256:
 9001c508949151ceb58faa78edfcb961602e0db690b41607bc08baa6d8c1f4cb 2964 
qpid-proton_0.14.0-5.dsc
 7504e16ade9e48ea4f91126eb64f805ddaa159d0e748691c3df8f2581749c703 8220 
qpid-proton_0.14.0-5.debian.tar.xz
 df1ba8e63529e745b16f968679084c07c14235d2b016016f854e4940d828602d 11694 
qpid-proton_0.14.0-5_amd64.buildinfo
Files:
 298f77158722abebb91fc611d50e08ee 2964 libs optional qpid-proton_0.14.0-5.dsc
 423ab55a032f5fd40034448b07155478 8220 libs optional 
qpid-proton_0.14.0-5.debian.tar.xz
 d066dd3696bf2d3b33ce30bc62f0d8f2 11694 libs optional 
qpid-proton_0.14.0-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAljNcdsACgkQNXMSVZ0e
BkuKFBAAj88VyNQvEVY/ndsnJ/oL+1lOX8+f80QZ/FPrR/m3d4XMEj0nJbpIdBkE
EKE02pqxNhL0/tUw/PQTOc73Ft6SCC5R4dEZGhHF/wJ4LT96bnIPYHZ63nfqWsFU

Bug#858125: e1000: ethernet interface hangs occasionally, kernel reports hang

[Bruce Momjian,,,]

Here is a more complete dmesg output with a few resets included at the
bottom.  You can see there is 14 minutes between the resets:

[Mar18 12:26] [ cut here ]
[  +0.19] WARNING: CPU: 0 PID: 0 at 
/build/linux-GU1w8g/linux-3.16.39/net/sched/sch_generic.c:264 
dev_watchdog+0x236/0x240()
[  +0.04] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out
[  +0.02] Modules linked in: binfmt_misc cpufreq_stats 
cpufreq_conservative cpufreq_powersave cpufreq_userspace cfg80211 rfkill nfsd 
auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc pl2303 usbserial 
intel_powerclamp coretemp kvm_intel serio_raw kvm nvidia(PO) drm 
snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt iTCO_vendor_support 
snd_hda_intel evdev pcspkr lpc_ich snd_hda_controller snd_hda_codec mfd_core 
i2c_i801 i2c_core snd_hwdep snd_pcm snd_timer ioatdma snd soundcore button 
i7core_edac shpchp acpi_cpufreq edac_core dca processor thermal_sys loop 
firewire_sbp2 fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 
hid_generic usbhid hid usb_storage sd_mod crc_t10dif sg crct10dif_generic 
sr_mod crct10dif_common cdrom ata_generic crc32c_intel ata_piix psmouse uhci_hcd
[  +0.75]  ehci_pci libata e1000e ehci_hcd firewire_ohci usbcore 
ptp firewire_core scsi_mod crc_itu_t pps_core usb_common
[  +0.13] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P   O  
3.16.0-4-amd64 #1 Debian 3.16.39-1
[  +0.09] Hardware name: Supermicro X8DA3/X8DA3, BIOS 2.1a
04/06/2012
[  +0.05]   81514c11 88033fc03e28 
0009
[  +0.03]  81068867  88033fc03e78 
0001
[  +0.09]   88063042 810688cc 
81777e40
[  +0.04] Call Trace:
[  +0.02][] ? dump_stack+0x5d/0x78
[  +0.14]  [] ? warn_slowpath_common+0x77/0x90
[  +0.03]  [] ? warn_slowpath_fmt+0x4c/0x50
[  +0.07]  [] ? dev_watchdog+0x236/0x240
[  +0.04]  [] ? dev_graft_qdisc+0x70/0x70
[  +0.05]  [] ? call_timer_fn+0x31/0x140
[  +0.03]  [] ? dev_graft_qdisc+0x70/0x70
[  +0.04]  [] ? run_timer_softirq+0x1e9/0x2f0
[  +0.05]  [] ? __do_softirq+0xf1/0x2d0
[  +0.03]  [] ? irq_exit+0x95/0xa0
[  +0.05]  [] ? smp_apic_timer_interrupt+0x40/0x50
[  +0.04]  [] ? apic_timer_interrupt+0x6d/0x80
[  +0.01][] ? 
__hrtimer_start_range_ns+0x1cd/0x3a0
[  +0.08]  [] ? cpuidle_enter_state+0x4f/0xc0
[  +0.03]  [] ? cpuidle_enter_state+0x48/0xc0
[  +0.05]  [] ? cpu_startup_entry+0x328/0x470
[  +0.08]  [] ? start_kernel+0x497/0x4a2
[  +0.03]  [] ? set_init_arg+0x4e/0x4e
[  +0.03]  [] ? 
early_idt_handler_array+0x120/0x120
[  +0.03]  [] ? x86_64_start_kernel+0x14d/0x15c
[  +0.05] ---[ end trace 09366cbabe9552a8 ]---
--> [  +0.18] e1000e :03:00.0 eth0: Reset adapter unexpectedly
--> [  +3.963164] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
--> [Mar18 12:40] e1000e :03:00.0 eth0: Reset adapter unexpectedly
--> [  +3.891401] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx

-- 
  Bruce Momjian  http://momjian.us
  EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+  Ancient Roman grave inscription +

Bug#857772: marked as done (sushi: FTBFS with bash as /bin/sh)

[Debian Bug Tracking System]

Your message dated Sat, 18 Mar 2017 17:22:06 +
with message-id 
and subject line Bug#857772: fixed in sushi 1.4.0+git20160822+dfsg-3
has caused the Debian Bug report #857772,
regarding sushi: FTBFS with bash as /bin/sh
to be marked as done.

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

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


-- 
857772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sushi
Version: 1.4.0+git20160822+dfsg-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,

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

  […]

  'configure' finished successfully (0.019s)
  cd chirashi env LINKFLAGS='-Wl,-z,relro -Wl,-z,now' && env WAFDIR=«BUILDDIR» 
./waf configure --prefix /usr
  /bin/sh: line 0: cd: too many arguments
  debian/rules:29: recipe for target 'override_dh_auto_configure' failed
  make[1]: *** [override_dh_auto_configure] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:16: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


sushi.1.4.0+git20160822+dfsg-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: sushi
Source-Version: 1.4.0+git20160822+dfsg-3

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

Debian distribution maintenance software
pp.
Devid Antonio Filoni  (supplier of updated sushi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 18 Mar 2017 16:08:30 +0100
Source: sushi
Binary: sushi maki maki-plugins nigiri tekka chirashi sushi-plugins
Architecture: source
Version: 1.4.0+git20160822+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Devid Antonio Filoni 
Changed-By: Devid Antonio Filoni 
Description:
 chirashi   - D-Bus-based IRC suite (clients plugins)
 maki   - D-Bus-based IRC suite (daemon)
 maki-plugins - D-Bus-based IRC suite (daemon plugins)
 nigiri - D-Bus-based IRC suite (terminal client)
 sushi  - D-Bus-based IRC suite (metapackage)
 sushi-plugins - transitional dummy package
 tekka  - D-Bus-based IRC suite (graphical client)
Closes: 836195 857772
Changes:
 sushi (1.4.0+git20160822+dfsg-3) unstable; urgency=medium
 .
   * Fix FTBFS with bash as /bin/sh (Closes: #857772)
 Thanks to Chris Lamb for fixing this.
   * Fix package-uses-deprecated-debhelper-compat-version lintian warning
 switching to debhelper 9.
   * Fix empty-binary-package lintian warning
 Thanks to Adrian Vondendriesch for fixing this.
   * debian/control: both tekka and nigiri are now sushi deps (Closes: #836195)
   * Fix spelling-error-in-description-synopsis lintian warning.
   * Fix nigiri crashes:
 - debian/patches/nigiri-00-fix-gobject-import.diff: fix GObject ImportError
 - debian/patches/nigiri-01-fix-urwid-indexerror.diff: fix urwid
   'IndexError: No widget at position 1' error
 - debian/patches/nigiri-02-none-has-no-auto_scroll.diff: fix AttributeError
   * debian/control: remove DM-Upload-Allowed field.
Checksums-Sha1:
 0c11a4e3e444ffe90368f762ebf8d4b4e7bb3360 2181 
sushi_1.4.0+git20160822+dfsg-3.dsc
 f7d961e9cc88a2611a77d97ec5cbf2f067bbeab5 6656 
sushi_1.4.0+git20160822+dfsg-3.debian.tar.xz
Checksums-Sha256:
 344722500c866be74f856069d368b2f0f7a49816a0d620fed4cfff7fe38c78c7 2181 
sushi_1.4.0+git20160822+dfsg-3.dsc
 4d98c233329b0bf98c29330c4b917a10424f3a994c78e42bd10eea59fe8be440 6656 
sushi_1.4.0+git20160822+dfsg-3.debian.tar.xz
Files:
 ee68fb9c4b2007ccf6881ce3baab675f 2181 net extra 
sushi_1.4.0+git20160822+dfsg-3.dsc
 a883fb9c4fece23b6363b0e36efe8349 6656 

Bug#857772: Fix uploaded

[Devid Antonio Filoni]

Thank you Chris for pointing out that typo and providing a fix! I've
uploaded a fixed package.

Thank you Adrian for your efforts too, however please be more careful in
future, you uploaded a package with -2.1 as revision, but the package in
unstable is -1 so you were supposed to use -1.1 as revision number. I had
to upload two packages because I noticed this mistake after the first
upload...

Thank you again,
Devid

Bug#858125: e1000: ethernet interface hangs occasionally, kernel reports hang

[Bruce Momjian,,,]

Package: src:linux
Version: 3.16.39-1
Severity: critical
File: e1000
Justification: breaks unrelated software

Dear Maintainer,

I have had intermittent hangs of my two built-in ethernet interfaces since 
switching from 100Mb ethernet to 1Gb ethernet.  During the
hangs, no traffic passes through the port.  This has been happening since 
August 2016 and the hangs are 20-60 seconds.  Sometimes the
hangs happen every half hour, other times I can go days with no hang, but the 
hangs are becoming more frequent.

Sometimes the hangs report this kernel message:

kernel: [96085.866650] e1000e: eth0 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: Rx/Tx

but other times there is more detail:

Mar 18 11:20:13 momjian kernel: [ 2537.679019] [ cut here 
]
Mar 18 11:20:13 momjian kernel: [ 2537.679031] WARNING: CPU: 0 PID: 0 
at /build/linux-GU1w8g/linux-3.16.39/net/sched/sch_generic.c:264 
dev_watchdog+0x236/0x240()
Mar 18 11:20:13 momjian kernel: [ 2537.679034] NETDEV WATCHDOG: eth1 
(e1000e): transmit queue 0 timed out
Mar 18 11:20:13 momjian kernel: [ 2537.679035] Modules linked in: 
cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_userspace cfg80211 
rfkill binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache 
sunrpc pl2303 usbserial iTCO_wdt iTCO_vendor_support nvidia(PO) 
intel_powerclamp coretemp pcspkr kvm_intel i2c_i801 kvm snd_hda_codec_realtek 
drm snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec evdev 
serio_raw i2c_core snd_hwdep lpc_ich snd_pcm mfd_core snd_timer button 
i7core_edac snd ioatdma soundcore edac_core shpchp acpi_cpufreq dca processor 
thermal_sys loop firewire_sbp2 fuse parport_pc ppdev lp parport autofs4 ext4 
crc16 mbcache jbd2 hid_generic usbhid usb_storage hid sg sr_mod cdrom sd_mod 
crc_t10dif crct10dif_generic crct10dif_common ata_generic crc32c_intel ata_piix 
ehci_pci uhci_hcd psmouse libata ehci_hcd firewire_ohci e1000e usbcore ptp 
firewire_core scsi_mod pps_core crc_itu_t usb_common
Mar 18 11:20:13 momjian kernel: [ 2537.679107] CPU: 0 PID: 0 Comm: 
swapper/0 Tainted: P   O  3.16.0-4-amd64 #1 Debian 3.16.39-1
Mar 18 11:20:13 momjian kernel: [ 2537.679109] Hardware name: 
Supermicro X8DA3/X8DA3, BIOS 2.1a04/06/2012
Mar 18 11:20:13 momjian kernel: [ 2537.679111]   
81514c11 88033fc03e28 0009
Mar 18 11:20:13 momjian kernel: [ 2537.679114]  81068867 
 88033fc03e78 0001
Mar 18 11:20:13 momjian kernel: [ 2537.679117]   
880330d2 810688cc 81777e40
Mar 18 11:20:13 momjian kernel: [ 2537.679121] Call Trace:
Mar 18 11:20:13 momjian kernel: [ 2537.679123]
[] ? dump_stack+0x5d/0x78
Mar 18 11:20:13 momjian kernel: [ 2537.679133]  [] ? 
warn_slowpath_common+0x77/0x90
Mar 18 11:20:13 momjian kernel: [ 2537.679137]  [] ? 
warn_slowpath_fmt+0x4c/0x50
Mar 18 11:20:13 momjian kernel: [ 2537.679141]  [] ? 
mod_timer+0xf5/0x200
Mar 18 11:20:13 momjian kernel: [ 2537.679148]  [] ? 
dev_watchdog+0x236/0x240
Mar 18 11:20:13 momjian kernel: [ 2537.679152]  [] ? 
dev_graft_qdisc+0x70/0x70
Mar 18 11:20:13 momjian kernel: [ 2537.679155]  [] ? 
call_timer_fn+0x31/0x140
Mar 18 11:20:13 momjian kernel: [ 2537.679158]  [] ? 
dev_graft_qdisc+0x70/0x70
Mar 18 11:20:13 momjian kernel: [ 2537.679162]  [] ? 
run_timer_softirq+0x1e9/0x2f0
Mar 18 11:20:13 momjian kernel: [ 2537.679165]  [] ? 
__do_softirq+0xf1/0x2d0
Mar 18 11:20:13 momjian kernel: [ 2537.679168]  [] ? 
irq_exit+0x95/0xa0
Mar 18 11:20:13 momjian kernel: [ 2537.679172]  [] ? 
smp_apic_timer_interrupt+0x40/0x50
Mar 18 11:20:13 momjian kernel: [ 2537.679177]  [] ? 
apic_timer_interrupt+0x6d/0x80
Mar 18 11:20:13 momjian kernel: [ 2537.679178]
[] ? get_next_timer_interrupt+0x1d6/0x250
Mar 18 11:20:13 momjian kernel: [ 2537.679185]  [] ? 
cpuidle_enter_state+0x4f/0xc0
Mar 18 11:20:13 momjian kernel: [ 2537.679188]  [] ? 
cpuidle_enter_state+0x48/0xc0
Mar 18 11:20:13 momjian kernel: [ 2537.679193]  [] ? 
cpu_startup_entry+0x328/0x470
Mar 18 11:20:13 momjian kernel: [ 2537.679197]  [] ? 
start_kernel+0x497/0x4a2
Mar 18 11:20:13 momjian kernel: [ 2537.679200]  [] ? 
set_init_arg+0x4e/0x4e
Mar 18 11:20:13 momjian kernel: [ 2537.679203]  [] ? 
early_idt_handler_array+0x120/0x120
Mar 18 11:20:13 momjian kernel: [ 2537.679207]  [] ? 
x86_64_start_kernel+0x14d/0x15c
Mar 18 11:20:13 momjian kernel: [ 2537.679209] ---[ end trace 
927f39a58f3280de ]---

Things I have tried to fix it:

*  switched interface ports;  the hang moved to the new port

*  switched from Cat5e to Cat6 cable

*  upgraded the motherboard firmware

*  disabled TCP segmentation offload via ethtool -K eth0 tso off and ethtool -K 

Bug#858122: Upgrade linux kernel to 4.9.15 in sid and stretch

[Salvatore Bonaccorso]

Hi

On Sat, Mar 18, 2017 at 05:01:56PM +0100, Julien Aubin wrote:
> Source: linux
> Severity: critical
> Tags: security
> Justification: root security hole
> 
> Hi,
> 
> Security issue CVE-2017-2636 (severity 7.8) has been disclosed and the fix
> has
> been provided for Jessie and Wheezy. The problem is that there's as of now
> no
> fix available for sid and stretch while things become more and more critical
> due to the severity of the issue.
> 
> Kernel 4.9.15 contains a fix for this. Could you please integrate it ASAP on
> Stretch ?
> 
> Thanks in advance.

yes this is already pending in git.

https://anonscm.debian.org/cgit/kernel/linux.git/commit/?h=sid=11d69f4069a047f1fa0dffa71762b54fdde4f08f

Regards,
Salvatore

Processed: fixed

[Debian Bug Tracking System]

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

> fixed 855705 2.0.25-1+deb8u3
Bug #855705 {Done: Holger Levsen } [munin] munin: 
CVE-2017-6188: munin-cgi-graph local file write vulnerability
Marked as fixed in versions munin/2.0.25-1+deb8u3.
> thanks
Stopping processing here.

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

Processed: retitle 858122 to linux: CVE-2017-2636: tty: n_hdlc: get rid of racy n_hdlc.tbuf, tagging 858122 ...

[Debian Bug Tracking System]

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

> retitle 858122 linux: CVE-2017-2636: tty: n_hdlc: get rid of racy n_hdlc.tbuf
Bug #858122 [src:linux] Upgrade linux kernel to 4.9.15 in sid and stretch
Changed Bug title to 'linux: CVE-2017-2636: tty: n_hdlc: get rid of racy 
n_hdlc.tbuf' from 'Upgrade linux kernel to 4.9.15 in sid and stretch'.
> tags 858122 + pending upstream fixed-upstream
Bug #858122 [src:linux] linux: CVE-2017-2636: tty: n_hdlc: get rid of racy 
n_hdlc.tbuf
Added tag(s) fixed-upstream, pending, and upstream.
> found 858122 4.9.13-1
Bug #858122 [src:linux] linux: CVE-2017-2636: tty: n_hdlc: get rid of racy 
n_hdlc.tbuf
Marked as found in versions linux/4.9.13-1.
> thanks
Stopping processing here.

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

Processed: python-ethtool: diff for NMU version 0.12-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 857346 + pending
Bug #857346 [python-ethtool] Segmentation Fault when trying to use get_hwaddr()
Added tag(s) pending.

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

Bug#857346: python-ethtool: diff for NMU version 0.12-1.1

[Evgeni Golov]

Control: tags 857346 + pending

Dear maintainer,

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

Regards.
Evgeni
diff -Nru python-ethtool-0.12/debian/changelog python-ethtool-0.12/debian/changelog
--- python-ethtool-0.12/debian/changelog	2016-09-24 15:34:09.0 +0200
+++ python-ethtool-0.12/debian/changelog	2017-03-18 16:47:04.0 +0100
@@ -1,3 +1,15 @@
+python-ethtool (0.12-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Evgeni Golov ]
+  * update Homage in d/control
+
+  [ Reiner Herrmann ]
+  * Fix argument parsing in C library (Closes: #857346)
+
+ -- Evgeni Golov   Sat, 18 Mar 2017 16:47:04 +0100
+
 python-ethtool (0.12-1) unstable; urgency=medium
 
   * [ea5192b] Fix some other gcc5 warnings.
diff -Nru python-ethtool-0.12/debian/control python-ethtool-0.12/debian/control
--- python-ethtool-0.12/debian/control	2016-09-24 15:34:09.0 +0200
+++ python-ethtool-0.12/debian/control	2017-03-17 16:34:53.0 +0100
@@ -5,7 +5,7 @@
 Maintainer: Bernd Zeimetz 
 Build-Depends: debhelper (>= 7.0.50~), python-all-dev (>= 2.6.6-3~), libnl-route-3-dev, asciidoc, pkg-config, libxml2-utils, docbook-xml, xsltproc, sgml-data, libxml2, docbook-xsl, docbook-xml
 Standards-Version: 3.9.3
-Homepage: http://fedorapeople.org/gitweb?p=dsommers/public_git/python-ethtool.git;a=summary
+Homepage: https://fedorapeople.org/cgit/dsommers/public_git/python-ethtool.git/
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/spacewalk/python-ethtool.git
 Vcs-Git: git://anonscm.debian.org/collab-maint/spacewalk/python-ethtool.git
 
diff -Nru python-ethtool-0.12/debian/patches/fix_argument_parsing python-ethtool-0.12/debian/patches/fix_argument_parsing
--- python-ethtool-0.12/debian/patches/fix_argument_parsing	1970-01-01 01:00:00.0 +0100
+++ python-ethtool-0.12/debian/patches/fix_argument_parsing	2017-03-17 16:37:38.0 +0100
@@ -0,0 +1,111 @@
+Author: Reiner Herrmann 
+Description: Fix argument parsing of device names
+ PyArg_ParseTuple was called with the format string "s*" to parse the
+ passed device name into a C string.
+ But according to Python C-API documentation, "s*" is used for parsing data
+ into a Py_buffer structure:  https://docs.python.org/2/c-api/arg.html
+ To store it into a C string, "s" has to be used.
+ (Memory doesn't need to be freed, as it is managed by Python.)
+Bug-Debian: https://bugs.debian.org/857346
+
+--- a/python-ethtool/ethtool.c
 b/python-ethtool/ethtool.c
+@@ -121,7 +121,7 @@
+ 	const char *devname;
+ 	char hwaddr[20];
+ 
+-	if (!PyArg_ParseTuple(args, "s*", ))
++	if (!PyArg_ParseTuple(args, "s", ))
+ 		return NULL;
+ 
+ 	/* Setup our request structure. */
+@@ -163,7 +163,7 @@
+ 	const char *devname;
+ 	char ipaddr[20];
+ 
+-	if (!PyArg_ParseTuple(args, "s*", ))
++	if (!PyArg_ParseTuple(args, "s", ))
+ 		return NULL;
+ 
+ 	/* Setup our request structure. */
+@@ -295,7 +295,7 @@
+ 	const char *devname;
+ 	int fd, err;
+ 
+-	if (!PyArg_ParseTuple(args, "s*", ))
++	if (!PyArg_ParseTuple(args, "s", ))
+ 		return NULL;
+ 
+ 	/* Setup our request structure. */
+@@ -328,7 +328,7 @@
+ 	const char *devname;
+ 	char netmask[20];
+ 
+-	if (!PyArg_ParseTuple(args, "s*", ))
++	if (!PyArg_ParseTuple(args, "s", ))
+ 		return NULL;
+ 
+ 	/* Setup our request structure. */
+@@ -368,7 +368,7 @@
+ 	const char *devname;
+ 	char broadcast[20];
+ 
+-	if (!PyArg_ParseTuple(args, "s*", ))
++	if (!PyArg_ParseTuple(args, "s", ))
+ 		return NULL;
+ 
+ 	/* Setup our request structure. */
+@@ -409,7 +409,7 @@
+ 	char buf[2048];
+ 	const char *devname;
+ 
+-	if (!PyArg_ParseTuple(args, "s*", ))
++	if (!PyArg_ParseTuple(args, "s", ))
+ 		return NULL;
+ 
+ 	/* Setup our control structures. */
+@@ -479,7 +479,7 @@
+ 	char buf[1024];
+ 	const char *devname;
+ 
+-	if (!PyArg_ParseTuple(args, "s*", ))
++	if (!PyArg_ParseTuple(args, "s", ))
+ 		return NULL;
+ 
+ 	/* Setup our control structures. */
+@@ -545,7 +545,7 @@
+ 	const char *devname;
+ 	int err = -1;
+ 
+-	if (PyArg_ParseTuple(args, "s*", ))
++	if (PyArg_ParseTuple(args, "s", ))
+ 		err = send_command(cmd, devname, value);
+ 
+ 	return err;
+@@ -567,7 +567,7 @@
+ 	struct ethtool_value eval;
+ 	const char *devname;
+ 
+-	if (!PyArg_ParseTuple(args, "s*i", , ))
++	if (!PyArg_ParseTuple(args, "si", , ))
+ 		return -1;
+ 
+ 	return send_command(cmd, devname, );
+@@ -752,7 +752,7 @@
+ 	const char *devname;
+ 	PyObject *dict;
+ 
+-	if (!PyArg_ParseTuple(args, "s*O", , ))
++	if (!PyArg_ParseTuple(args, "sO", , ))
+ 		return NULL;
+ 
+ 	if (struct_desc_from_dict(ethtool_coalesce_desc, , dict) != 0)
+@@ -792,7 +792,7 @@
+ 	const char *devname;
+ 	PyObject *dict;
+ 
+-	if (!PyArg_ParseTuple(args, "s*O", , ))
++	if (!PyArg_ParseTuple(args, "sO", , ))
+ 		return NULL;
+ 
+ 	if (struct_desc_from_dict(ethtool_ringparam_desc, , dict) != 0)
diff -Nru 

Bug#858122: Upgrade linux kernel to 4.9.15 in sid and stretch

[Julien Aubin]

Source: linux
Severity: critical
Tags: security
Justification: root security hole

Hi,

Security issue CVE-2017-2636 (severity 7.8) has been disclosed and the fix
has
been provided for Jessie and Wheezy. The problem is that there's as of now
no
fix available for sid and stretch while things become more and more critical
due to the severity of the issue.

Kernel 4.9.15 contains a fix for this. Could you please integrate it ASAP on
Stretch ?

Thanks in advance.

More info at :
https://www.ptsecurity.com/ww-en/about/news/199636/



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

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

Processed: tagging 854592

[Debian Bug Tracking System]

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

> # based on comment from taffit
> tags 854592 - patch
Bug #854592 [php-phpseclib] dokuwiki: Unable to login, missing 
usr/share/php/Crypt/AES.php
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#818558: Useless in Debian

[Paul Gevers]

@ BSP Mönchengladbach

On Thu, 17 Mar 2016 20:56:06 -0400 David Prévot=  wrote:
> I intend to follow up with an RM request in a few months if nobody
> objects (but feel free to beat me to it).

RoQA filed in bug 858120.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: severity of 852433 is serious, user bugsqu...@qa.debian.org, usertagging 852433

[Debian Bug Tracking System]

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

> # this may break if the Debian tooling implements stricter checks
> severity 852433 serious
Bug #852433 [src:openhpi] openhpi: debug symbol packages in wrong archive
Severity set to 'serious' from 'important'
> user bugsqu...@qa.debian.org
Setting user to bugsqu...@qa.debian.org (was a...@debian.org).
> usertags 852433 + a...@debian.org
There were no usertags set.
Usertags are now: a...@debian.org.
> thanks
Stopping processing here.

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

Bug#857521: Patch

[K-C Videri]

See attachment for bug

-- 
CU
  Michael
diff -Nru alljoyn-services-1509-15.09/debian/changelog alljoyn-services-1509-15.09/debian/changelog
--- alljoyn-services-1509-15.09/debian/changelog	2016-12-25 18:28:32.0 +0100
+++ alljoyn-services-1509-15.09/debian/changelog	2017-03-18 15:20:28.0 +0100
@@ -1,3 +1,10 @@
+alljoyn-services-1509 (15.09-4) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fixed broken symlink (closes: #857521).
+
+ -- Michael Ott   Sat, 18 Mar 2017 15:20:28 +0100
+
 alljoyn-services-1509 (15.09-3) unstable; urgency=medium
 
   * move package to debian-iot-maintainer
diff -Nru alljoyn-services-1509-15.09/debian/liballjoynservices1509.install alljoyn-services-1509-15.09/debian/liballjoynservices1509.install
--- alljoyn-services-1509-15.09/debian/liballjoynservices1509.install	2016-12-25 18:28:32.0 +0100
+++ alljoyn-services-1509-15.09/debian/liballjoynservices1509.install	2017-03-18 15:20:28.0 +0100
@@ -5,3 +5,4 @@
 controlpanel/build/*/*/*/dist/controlpanel/lib/liballjoyn_controlpanel.so.* /usr/lib/${DEB_HOST_MULTIARCH}
 notification/build/*/*/*/dist/notification/lib/liballjoyn_notification.so.* /usr/lib/${DEB_HOST_MULTIARCH}
 onboarding/build/*/*/*/dist/onboarding/lib/liballjoyn_onboarding.so.* /usr/lib/${DEB_HOST_MULTIARCH}
+config/build/*/*/*/dist/config/lib/liballjoyn_config.so.* /usr/lib/${DEB_HOST_MULTIARCH}

Bug#842130: Useless in Stretch

[Paul Gevers]

Hi David,

On Tue, 25 Oct 2016 20:31:54 -1000 David Prévot  wrote:
> Package: libjs-ie7
> Version: 2.1~beta4-2

> I intend to ask for removal of this package in a few month.

Is it about time to do this now?

Paul



signature.asc
Description: OpenPGP digital signature

Processed: tagging 857521

[Debian Bug Tracking System]

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

> tags 857521 + patch
Bug #857521 [liballjoynservices-dev-1509] liballjoynservices-dev-1509: broken 
symlink: /usr/lib/x86_64-linux-gnu/liballjoyn_config.so -> 
liballjoyn_config.so.1509
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#857301: i've uploaded to DELAYED/5

[gustavo panizzo]

Hi,

I've uploaded an updated version to DELAYED/5, I'll follow up with the
release team to unblock it unless the maintainer says otherwise

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858113

--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa

Bug#850885: fixed in dwww 1.13.3

[Martin Maney]

Two months later, there's no fix for Stable (1.12.1 is the current
version).  Is it stuck somewhere in process?

Thanks.

On Wed, 18 Jan 2017 21:19:01 + Robert Luberda  wrote:
> Source: dwww
> Source-Version: 1.13.3
> 
> We believe that the bug you reported is fixed in the latest version of
> dwww, 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 850...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Robert Luberda  (supplier of updated dwww 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, 18 Jan 2017 21:47:05 +0100
> Source: dwww
> Binary: dwww
> Architecture: source i386
> Version: 1.13.3
> Distribution: unstable
> Urgency: medium
> Maintainer: Robert Luberda 
> Changed-By: Robert Luberda 
> Description:
>  dwww   - Read all on-line documentation with a WWW browser
> Closes: 850016 850885
> Changes:
>  dwww (1.13.3) unstable; urgency=medium
>  .
>* Fix a typo in the `Last-Modified' header name (closes: #850016, #850885).
>* Fix a spelling typo found by lintian.
> Checksums-Sha1:
>  3f87f329a39398b353bf3cab9cafc624308710e4 1584 dwww_1.13.3.dsc
>  7ba623f4b603a5c615665ec972c26c3b93e18de5 124628 dwww_1.13.3.tar.xz
>  cd3ea8eb32b83cc58574853dca0f3b566b31dca1 37844 dwww-dbgsym_1.13.3_i386.deb
>  aec76aef7c19a2745e4b246af3d826e87321f536 5982 dwww_1.13.3_i386.buildinfo
>  ce87e623d30ac610d5bec2956f5505dd3f487cfc 126748 dwww_1.13.3_i386.deb
> Checksums-Sha256:
>  f12caec4a45a02493a16ed532c9153a323ded8a7a7e6eb5506f17ff923759313 1584 
> dwww_1.13.3.dsc
>  00b1f95dcd49c1592c4c39a890f3df3b0b70c45a88b129ff7720a32fce8231bd 124628 
> dwww_1.13.3.tar.xz
>  a18617476741c9f65e62ce6771c1319da0db3d756d0fd6ff891cff1f36dc8223 37844 
> dwww-dbgsym_1.13.3_i386.deb
>  f7bbf60c3126fc7f4ac35fe43ba2477145b1361f5e4219450acb894b46365c2b 5982 
> dwww_1.13.3_i386.buildinfo
>  e5619394bd9f612a373ab499ff3961ea4376c7fca8a7b42d6b9fc6c8f54bf96e 126748 
> dwww_1.13.3_i386.deb
> Files:
>  4dfbfcb6785ceb7f6cf26eba087c1aa3 1584 doc optional dwww_1.13.3.dsc
>  f2770bdf3647a6f324d13a5e460aef0a 124628 doc optional dwww_1.13.3.tar.xz
>  dc6c918f4b919f00977fac1d238bd5e7 37844 debug extra 
> dwww-dbgsym_1.13.3_i386.deb
>  f14784bbb3a8156327f7f8875c2360c2 5982 doc optional dwww_1.13.3_i386.buildinfo

-- 
Remember the refrain:  We always build on the past;
the past always tries to stop us.  Freedom is about stopping the past,
but we have lost that ideal.  -- Lawrence Lessig

Bug#857561: polarssl: CVE-2017-2784: Freeing of memory allocated on stack when validating a public key with a secp224k1 curve

[James Cowgill]

Control: tags -1 patch

Hi,

On Sun, 12 Mar 2017 15:19:58 + James Cowgill 
wrote:
> Package: libmbedcrypto0
> Version: 2.4.0-1
> Severity: grave
> Tags: security
> Control: clone -1 -2
> Control: reassign -2 libpolarssl7 1.3.9-2.1+deb8u1
> Control: retitle -2 polarssl: CVE-2017-2748 - Freeing of memory allocated on 
> stack when validating a public key with a secp224k1 curve
> 
> Hi all,
> 
> This security advisory was recently published and contains one "high"
> severity bug:
> https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2017-01
> 
> The security changelog for 2.4.2 also contains fixes for some other
> bugs as well. The 3rd bug (relating to SLOTH) does not affect polarssl.

The attached patch should fix CVE-2017-2784 in jessie. I haven't
attempted to fix any of the other lower priority bugs which were fixed
in 1.3.19 / 2.4.2

Thanks,
James
diff -Nru polarssl-1.3.9/debian/changelog polarssl-1.3.9/debian/changelog
--- polarssl-1.3.9/debian/changelog 2016-02-06 13:29:38.0 +
+++ polarssl-1.3.9/debian/changelog 2017-03-17 21:38:48.0 +
@@ -1,3 +1,11 @@
+polarssl (1.3.9-2.1+deb8u2) jessie-security; urgency=high
+
+  * Non-maintainer upload.
+  * Fix CVE-2017-2784: Freeing of memory allocated on stack when
+validating a public key with a secp224k1 curve. (Closes: #857561)
+
+ -- James Cowgill   Fri, 17 Mar 2017 21:38:48 +
+
 polarssl (1.3.9-2.1+deb8u1) jessie-security; urgency=high
 
   * Non-maintainer upload.
diff -Nru polarssl-1.3.9/debian/patches/CVE-2017-2784.patch 
polarssl-1.3.9/debian/patches/CVE-2017-2784.patch
--- polarssl-1.3.9/debian/patches/CVE-2017-2784.patch   1970-01-01 
01:00:00.0 +0100
+++ polarssl-1.3.9/debian/patches/CVE-2017-2784.patch   2017-03-17 
21:38:48.0 +
@@ -0,0 +1,49 @@
+Description: Fix for CVE-2017-2784
+ Fixed a bug that caused freeing a buffer that was allocated on the stack,
+ when verifying the validity of a key on secp224k1. This could be
+ triggered remotely for example with a maliciously constructed certificate
+ and might have led to remote code execution on some exotic embedded
+ platforms. Reported independently by rongsaws and Regina Wilson.
+ .
+ The function ecp_mod_koblitz computed the space for the result of a
+ multiplication optimally for that specific case, but unfortunately
+ the function mbedtls_mpi_mul_mpi performs a generic, suboptimal
+ calculation and needs one more limb for the result. Since the result's
+ buffer is on the stack, the best case scenario is that the program
+ stops.
+ .
+ This only happened on 64 bit platforms.
+Origin: upstream, 
https://github.com/ARMmbed/mbedtls/commit/f5ffc79896681daddf7530646c0908f51a887dbd
+Bug-Debian: https://bugs.debian.org/857561
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+--- a/library/ecp_curves.c
 b/library/ecp_curves.c
+@@ -1268,7 +1268,7 @@ static inline int ecp_mod_koblitz( mpi *
+ int ret;
+ size_t i;
+ mpi M, R;
+-t_uint Mp[P_KOBLITZ_MAX + P_KOBLITZ_R];
++t_uint Mp[P_KOBLITZ_MAX + P_KOBLITZ_R + 1];
+ 
+ if( N->n < p_limbs )
+ return( 0 );
+@@ -1290,7 +1290,7 @@ static inline int ecp_mod_koblitz( mpi *
+ memcpy( Mp, N->p + p_limbs - adjust, M.n * sizeof( t_uint ) );
+ if( shift != 0 )
+ MPI_CHK( mpi_shift_r( , shift ) );
+-M.n += R.n - adjust; /* Make room for multiplication by R */
++M.n += R.n; /* Make room for multiplication by R */
+ 
+ /* N = A0 */
+ if( mask != 0 )
+@@ -1312,7 +1312,7 @@ static inline int ecp_mod_koblitz( mpi *
+ memcpy( Mp, N->p + p_limbs - adjust, M.n * sizeof( t_uint ) );
+ if( shift != 0 )
+ MPI_CHK( mpi_shift_r( , shift ) );
+-M.n += R.n - adjust; /* Make room for multiplication by R */
++M.n += R.n; /* Make room for multiplication by R */
+ 
+ /* N = A0 */
+ if( mask != 0 )
diff -Nru polarssl-1.3.9/debian/patches/series 
polarssl-1.3.9/debian/patches/series
--- polarssl-1.3.9/debian/patches/series2016-02-05 12:25:30.0 
+
+++ polarssl-1.3.9/debian/patches/series2017-03-17 21:38:22.0 
+
@@ -5,3 +5,4 @@
 CVE-2015-8036-Added-bounds-checking-for-TLS-extensions.patch
 CVE-2015-8036-Reordered-extension-fields-and-added-to-Cha.patch
 CVE-2015-8036-Add-extra-check-before-integer-conversion.patch
+CVE-2017-2784.patch


signature.asc
Description: OpenPGP digital signature

Processed: Bug#857561: polarssl: CVE-2017-2784: Freeing of memory allocated on stack when validating a public key with a secp224k1 curve

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #857561 [libpolarssl7] polarssl: CVE-2017-2784: Freeing of memory allocated 
on stack when validating a public key with a secp224k1 curve
Added tag(s) patch.

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

Bug#857296: hol88-library is an empty package on arm64, hppa, and m68k

[Carsten Leonhardt]

> Something weired seems to have happend to hol88-library. On some
> architectures (arm64, hppa, m68k), the package is simply empty. Upon
> closer inspection it turns out that the upstream build system simply
> hides build failures.
> 
> https://sources.debian.net/src/hol88/2.02.19940316-32/Makefile/#L291
> | (date; $(MAKE) hol; date; $(MAKE) library; date)
> 
> Thus technically, hol88 fails to build from source, it violates policy
> by not detecting such failure and it is dysfunctional by shipping
> empty packages.

I've discussed this bug with release team member Ivo De Decker.

Currently the package builds ok on arm64, which means the underlying
problem is probably in gcl. Nonetheless the build system needs to catch
the build errors and abort.

 - Carsten

Bug#857657: marked as done (pybit-client: broken symlinks: /var/lib/pybit-client.d/*.py -> /usr/share/pyshared/pybitclient/*.py)

[Debian Bug Tracking System]

Your message dated Sat, 18 Mar 2017 13:36:29 +
with message-id 
and subject line Bug#857657: fixed in pybit 1.0.0-3
has caused the Debian Bug report #857657,
regarding pybit-client: broken symlinks: /var/lib/pybit-client.d/*.py -> 
/usr/share/pyshared/pybitclient/*.py
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.)


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

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

1m36.3s ERROR: FAIL: Broken symlinks:
  /var/lib/pybit-client.d/git.py -> /usr/share/pyshared/pybitclient/git.py
  /var/lib/pybit-client.d/apt.py -> /usr/share/pyshared/pybitclient/apt.py
  /var/lib/pybit-client.d/subversion.py -> 
/usr/share/pyshared/pybitclient/subversion.py
  /var/lib/pybit-client.d/debianclient.py -> 
/usr/share/pyshared/pybitclient/debianclient.py

These files are now found in /usr/lib/python2.7/dist-packages/pybitclient/


cheers,

Andreas


pybit-client_1.0.0-2.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pybit
Source-Version: 1.0.0-3

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated pybit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 18 Mar 2017 14:15:43 +0100
Source: pybit
Binary: pybit-svn pybit-client pybit-web pybit-common pybit-watcher
Architecture: source
Version: 1.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 pybit-client - buildd client support for pybit
 pybit-common - Common objects for pybit
 pybit-svn  - Subversion post commit hook for pybit
 pybit-watcher - watches incoming directories for reprepro
 pybit-web  - buildd toolkit based on message queues (web frontend)
Closes: 762220 767405 774473 781594 815169 834277 846529 857657
Changes:
 pybit (1.0.0-3) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * QA upload.
   * Set Maintainer to Debian QA Group, remove Uploaders.  (See: #835908)
   * Move packaging repository to collab-maint.
   * Switch from cdn.debian.net to deb.debian.org.  (Closes: #774473)
   * Make the build reproducible, thanks to Chris Lamb.  (Closes: #834277)
   * Add missing dependencies on lsb-base.
   * [INTL:pt_BR] Brazilian Portuguese debconf translations.  (Closes: #846529)
 .
   [ Neil Williams ]
   * Incorporate NMU, thanks to Jonathan Wiltshire. (Closes: #762220)
   * Update backend support to only svn and git, add note to manpage
 for pybit-client manpage to explain the issues with the
 incomplete apt backend. (Closes: #781594, #857657, #815169)
   * [INTL:nl] Dutch translation of debconf messages
 (Closes: #767405)
Checksums-Sha1:
 587089e4c665c8eeb71ba5e7ce50360e78fde643 2154 pybit_1.0.0-3.dsc
 cd477f7bdc0819f3c661599763c0cb03c4fdd1a2 41796 pybit_1.0.0-3.debian.tar.xz
 a348ffea23c0053149a8047e184fac6249e8335b 5295 pybit_1.0.0-3_source.buildinfo
Checksums-Sha256:
 2aedc37a37e950eb73350e80987954c77d6dcefe147363b6040654431c7a67ba 2154 
pybit_1.0.0-3.dsc
 5ae3451a66a1a1112c3f2d053199ecaed9ad2706bb5f87ff54747e1b24e7df84 41796 
pybit_1.0.0-3.debian.tar.xz
 c87fc90a8b222d5cbddabd945781bf64c017f83dae48c6c2f87990d4a299a962 5295 
pybit_1.0.0-3_source.buildinfo
Files:
 aa88970438672e5e32e73b8f95902b11 2154 devel extra pybit_1.0.0-3.dsc
 4b7f46c5c06f001d561b338136fec139 41796 devel extra pybit_1.0.0-3.debian.tar.xz
 5b8550f440b559aeaee7355f571d365e 5295 devel extra 
pybit_1.0.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYzTN4AAoJEF+zP5NZ6e0IsdgQAJFaRtq1yGvl41zyQmBh+i2J

Bug#857513: Patch

[K-C Videri]

See attachment for bug

-- 
CU
  Michael
diff -Nru mobyle-1.5.5+dfsg/debian/changelog mobyle-1.5.5+dfsg/debian/changelog
--- mobyle-1.5.5+dfsg/debian/changelog	2016-05-20 23:14:19.0 +0200
+++ mobyle-1.5.5+dfsg/debian/changelog	2017-03-18 14:20:44.0 +0100
@@ -1,3 +1,10 @@
+mobyle (1.5.5+dfsg-2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fixed broken symlink (closes: #857513).
+
+ -- Michael Ott   Sat, 18 Mar 2017 14:20:44 +0100
+
 mobyle (1.5.5+dfsg-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru mobyle-1.5.5+dfsg/debian/mobyle.links mobyle-1.5.5+dfsg/debian/mobyle.links
--- mobyle-1.5.5+dfsg/debian/mobyle.links	2016-05-20 23:14:19.0 +0200
+++ mobyle-1.5.5+dfsg/debian/mobyle.links	2017-03-18 14:20:30.0 +0100
@@ -1,7 +1,7 @@
 usr/share/javascript/scriptaculous/builder.js usr/share/mobyle/htdocs/portal/js/builder.js
 usr/share/javascript/scriptaculous/effects.js usr/share/mobyle/htdocs/portal/js/effects.js
 usr/share/javascript/scriptaculous/scriptaculous.js usr/share/mobyle/htdocs/portal/js/scriptaculous.js
-usr/share/javascript/jquery/jquery.min/js usr/share/mobyle/htdocs/portal/js/openid/jquery-1.3.2.js
+usr/share/javascript/jquery/jquery.min.js usr/share/mobyle/htdocs/portal/js/openid/jquery-1.3.2.js
 usr/share/javascript/prototype/prototype.js usr/share/mobyle/htdocs/portal/js/prototype-1.7.js
 etc/mobyle/Config.py usr/share/mobyle/core/Local/Config/Config.py
 etc/mobyle/CustomClasses/__init__.py usr/share/mobyle/core/Local/CustomClasses/__init__.py

Processed: tagging 857417

[Debian Bug Tracking System]

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

> tags 857417 + patch
Bug #857417 {Done: Laszlo Boszormenyi (GCS) } 
[python-ecryptfs] python-ecryptfs: broken symlinks: 
/usr/lib/python2.7/dist-packages/ecryptfs-utils/_libecryptfs.so.* -> 
_libecryptfs.so
Ignoring request to alter tags of bug #857417 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 857513

[Debian Bug Tracking System]

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

> tags 857513 + patch
Bug #857513 [mobyle] mobyle: broken symlink: 
/usr/share/mobyle/htdocs/portal/js/openid/jquery-1.3.2.js -> 
../../../../../javascript/jquery/jquery.min/js
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#857417: marked as done (python-ecryptfs: broken symlinks: /usr/lib/python2.7/dist-packages/ecryptfs-utils/_libecryptfs.so.* -> _libecryptfs.so)

[Debian Bug Tracking System]

Your message dated Sat, 18 Mar 2017 13:19:01 +
with message-id 
and subject line Bug#857417: fixed in ecryptfs-utils 111-4
has caused the Debian Bug report #857417,
regarding python-ecryptfs: broken symlinks: 
/usr/lib/python2.7/dist-packages/ecryptfs-utils/_libecryptfs.so.* -> 
_libecryptfs.so
to be marked as done.

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

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


-- 
857417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-ecryptfs
Version: 111-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m21.5s ERROR: FAIL: Broken symlinks:
  /usr/lib/python2.7/dist-packages/ecryptfs-utils/_libecryptfs.so.0.0.0 -> 
_libecryptfs.so
  /usr/lib/python2.7/dist-packages/ecryptfs-utils/_libecryptfs.so.0.0 -> 
_libecryptfs.so

I assume the lack of _libecryptfs.so renders the package unusable.


cheers,

Andreas


python-ecryptfs_111-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ecryptfs-utils
Source-Version: 111-4

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated ecryptfs-utils 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 18 Mar 2017 12:32:08 +
Source: ecryptfs-utils
Binary: ecryptfs-utils ecryptfs-utils-dbg libecryptfs1 libecryptfs-dev 
python-ecryptfs
Architecture: source amd64
Version: 111-4
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 ecryptfs-utils - ecryptfs cryptographic filesystem (utilities)
 ecryptfs-utils-dbg - ecryptfs cryptographic filesystem (utilities; debug)
 libecryptfs-dev - ecryptfs cryptographic filesystem (development)
 libecryptfs1 - ecryptfs cryptographic filesystem (library)
 python-ecryptfs - ecryptfs cryptographic filesystem (python)
Closes: 857417
Changes:
 ecryptfs-utils (111-4) unstable; urgency=medium
 .
   * Correct _libecryptfs.so symlink in python-ecryptfs (closes: #857417).
Checksums-Sha1:
 7ebb7a71cadfea3dd36df0122cc7997e35fef1b0 2295 ecryptfs-utils_111-4.dsc
 739de50d45ed0ee72d7d60309f503d6ace7e7964 11540 
ecryptfs-utils_111-4.debian.tar.xz
 757751adbdcf2c9f9131dd7996ed4a79e15a 296160 
ecryptfs-utils-dbg_111-4_amd64.deb
 8daf9c30967fbd97102cf249d886bf491325d2e0 9734 
ecryptfs-utils_111-4_amd64.buildinfo
 7066b9186a1fc26a0fbb6883766f27f4bd48f5e4 101042 ecryptfs-utils_111-4_amd64.deb
 2885c8c1a908e67f9043c5d3c62a06a9f8049005 49270 libecryptfs-dev_111-4_amd64.deb
 f79a99fe68f580dc38f7a7f6eedb938b41c075b6 41464 libecryptfs1_111-4_amd64.deb
 b8bcd66c202fe9aec3621e72f81a1589e4496d0d 19676 python-ecryptfs_111-4_amd64.deb
Checksums-Sha256:
 c8a0f2ae1e3f4cf2acfaa4a21653ebd2cae4f54c3d803302528022aa71608c9b 2295 
ecryptfs-utils_111-4.dsc
 5fb3af79243b94cdf981a7e7ad664854c1a12a9213aa04f4fdc2a406952e92fc 11540 
ecryptfs-utils_111-4.debian.tar.xz
 9e4b7e3c21b497a51f5bcb0e37e1187320e7b9076c937087ebc95b0667ddfb7e 296160 
ecryptfs-utils-dbg_111-4_amd64.deb
 4d05effc6d937c4ddeb98ec3350b4e242ff8d98e4385f67cdd38324a5f3b2f86 9734 
ecryptfs-utils_111-4_amd64.buildinfo
 48674a70a7de103f7df626bd05331a00493e81c401cda689db9f18426f92f766 101042 
ecryptfs-utils_111-4_amd64.deb
 f15b1f47232ec147976c2a3b5fa00bff37801901dca3f9fb4d1ed003d2559eeb 49270 
libecryptfs-dev_111-4_amd64.deb
 9b57bae40f7f71ee8f8351bbe7bebd8aa8145983f99b4ec263ae1622f6c9f204 41464 
libecryptfs1_111-4_amd64.deb
 17c16356c8b80d4b60fded01a2a9202e29b196760eaa8a04779ef1dc40b3b3e7 19676 
python-ecryptfs_111-4_amd64.deb
Files:
 c26d9b8e29a5bdd639812b88fc2cc2ee 2295 misc optional ecryptfs-utils_111-4.dsc
 2de23b59004f671ab68f2f68363b3b5b 11540 misc optional 
ecryptfs-utils_111-4.debian.tar.xz
 

Bug#847571: upstream patch fixes the problem

[Wolfgang Schweer]

At BSP Mönchengladbach at credativ, Tomasz Rybak and I have rebuilt 
smarty3 with the patched smarty-lexer 
and the problem is gone.

Wolfgang


signature.asc
Description: PGP signature

Bug#857417: Patch

[K-C Videri]

See attach for this bugs report
diff -Nru ecryptfs-utils-111/debian/changelog 
ecryptfs-utils-111/debian/changelog
--- ecryptfs-utils-111/debian/changelog 2016-12-07 16:07:48.0 +0100
+++ ecryptfs-utils-111/debian/changelog 2017-03-18 12:41:41.0 +0100
@@ -1,3 +1,10 @@
+ecryptfs-utils (111-4) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fixed broken symlinks (closes: #857417).
+
+ -- Michael Ott   Sat, 18 Mar 2017 12:41:41 +0100
+
 ecryptfs-utils (111-3) unstable; urgency=medium
 
   * Change build dependency to libgpgme-dev (closes: #846983).
diff -Nru ecryptfs-utils-111/debian/rules ecryptfs-utils-111/debian/rules
--- ecryptfs-utils-111/debian/rules 2016-07-14 22:04:18.0 +0200
+++ ecryptfs-utils-111/debian/rules 2017-03-18 12:41:41.0 +0100
@@ -54,6 +54,7 @@
 
# Adding missing symlinks
cd debian/python-ecryptfs/usr/lib/python*/dist-packages/ecryptfs-utils 
&& \
+   ln -s _libecryptfs.*.so _libecryptfs.so && \
ln -s _libecryptfs.so _libecryptfs.so.0.0 && \
ln -s _libecryptfs.so _libecryptfs.so.0.0.0
 

Bug#858109: live-f1 isn't working anymore due to changes on the data-providing side.

[Cord Beermann]

Package: live-f1
Version: 0.2.10-1.1+b2
Severity: grave
Tags: upstream
Justification: renders package unusable

This package relies on the presence of a data-providing API at
live-timing.formula1.com.

live-f1: login request failed: Could not resolve hostname
`live-timing.formula1.com': Host not found

That address isn't available anymore. The new method from Formula1 is at
https://www.formula1.com/en/f1-live.html and as far as i can see is completely
new, so this program would require a rewrite to handle that.

In this version (even the newer 0.2.11 from 2014) the program doesn't do
anything anymore.

Cord


-- System Information:
Debian Release: 9.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages live-f1 depends on:
ii  libc6 2.24-9
ii  libncurses5   6.0+20161126-1
ii  libneon27-gnutls  0.30.2-2
ii  libtinfo5 6.0+20161126-1

live-f1 recommends no packages.

live-f1 suggests no packages.

-- debconf-show failed

Processed: tagging 857417

[Debian Bug Tracking System]

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

> tags 857417 + patch
Bug #857417 [python-ecryptfs] python-ecryptfs: broken symlinks: 
/usr/lib/python2.7/dist-packages/ecryptfs-utils/_libecryptfs.so.* -> 
_libecryptfs.so
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#857162: marked as done (libdublintraceroute-dev: missing Depends: libdublintraceroute0 (= ${binary:version}))

[Debian Bug Tracking System]

Your message dated Sat, 18 Mar 2017 12:19:18 +
with message-id 
and subject line Bug#857162: fixed in dublin-traceroute 0.3-3
has caused the Debian Bug report #857162,
regarding libdublintraceroute-dev: missing Depends: libdublintraceroute0 (= 
${binary:version})
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.)


-- 
857162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdublintraceroute-dev
Version: 0.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m22.1s ERROR: FAIL: Broken symlinks:
  /usr/lib/libdublintraceroute.so -> libdublintraceroute.so.0.0.0


cheers,

Andreas


libdublintraceroute-dev_0.3-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dublin-traceroute
Source-Version: 0.3-3

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated dublin-traceroute 
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, 17 Mar 2017 10:34:42 +
Source: dublin-traceroute
Binary: dublin-traceroute libdublintraceroute0 libdublintraceroute-dev
Architecture: source amd64
Version: 0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Description:
 dublin-traceroute - NAT-aware multipath tracerouting tool
 libdublintraceroute-dev - NAT-aware multipath tracerouting tool (dev)
 libdublintraceroute0 - NAT-aware multipath tracerouting tool (library)
Closes: 857162
Changes:
 dublin-traceroute (0.3-3) unstable; urgency=medium
 .
   * Add dependencies on libdulintraceroute0 (Closes: #857162)
Checksums-Sha1:
 1e6eb7c35e96e473073d4556f4586fec4124ef1c 2164 dublin-traceroute_0.3-3.dsc
 191161c31504bb28431faca2d9f30a1849eef8cc 2672 
dublin-traceroute_0.3-3.debian.tar.xz
 1af92f9b4aa09b56485ba1164dd682ec4b8be2a5 103348 
dublin-traceroute-dbgsym_0.3-3_amd64.deb
 88417e7b20d6dc1d3d8cf1e2a55e6d6e8030a6dc 7641 
dublin-traceroute_0.3-3_amd64.buildinfo
 bb8402092ee8dc129de81fdafe4532ee4e85dcfe 11584 
dublin-traceroute_0.3-3_amd64.deb
 e25196e79082a56db1977f79df1ab014b1117297 6304 
libdublintraceroute-dev_0.3-3_amd64.deb
 9b2784864d15d9641b947555ca46d4ee937a0ebf 730608 
libdublintraceroute0-dbgsym_0.3-3_amd64.deb
 f51195482138ae325245ef723140f2a78573584b 37282 
libdublintraceroute0_0.3-3_amd64.deb
Checksums-Sha256:
 ac79435b08cae34658e879085e56170c57db0af4895c6d9c34110f1de827c207 2164 
dublin-traceroute_0.3-3.dsc
 f8ebd9a1d3110efe076a48f4d7920107c9047a7c4d2bee0a9adbfe1c6f22 2672 
dublin-traceroute_0.3-3.debian.tar.xz
 3107a5598f2b11beeae5e3d369155731f64d572e4f816d5e793dd6eb11d9624a 103348 
dublin-traceroute-dbgsym_0.3-3_amd64.deb
 03bb672e891a3571ad574e2a629751097a8720d25c7207077fdbaf766e31 7641 
dublin-traceroute_0.3-3_amd64.buildinfo
 d9ebcb220b5ada470e315b433f672c4e6c8d3e8b73fd20dd5d522441f138b246 11584 
dublin-traceroute_0.3-3_amd64.deb
 57de59861fcf28f7f419a467c1f55da96eab8d42127c0ba55022efcd43dcdc44 6304 
libdublintraceroute-dev_0.3-3_amd64.deb
 f7afefe36c03532337fc6a6ba36a03efce3815fd613697739b340c40ca940341 730608 
libdublintraceroute0-dbgsym_0.3-3_amd64.deb
 7a2a22a3085c57904bb312e5cad9361038eba989282541b9a47c95e914e407ee 37282 
libdublintraceroute0_0.3-3_amd64.deb
Files:
 7d119361f99556dd66d7567ded2f2a3b 2164 net optional dublin-traceroute_0.3-3.dsc
 af526b74801605f3d8eaf254ef2cf798 2672 net optional 
dublin-traceroute_0.3-3.debian.tar.xz
 11950115bb60ef1eddfc3d57336dad1f 103348 debug extra 
dublin-traceroute-dbgsym_0.3-3_amd64.deb
 747fff0e5fb85dfc2c92833315f45368 7641 net optional 
dublin-traceroute_0.3-3_amd64.buildinfo
 c62950af2de2798d0dcce4b6d9887101 11584 net optional 
dublin-traceroute_0.3-3_amd64.deb
 

Bug#857210: marked as done (binutils-m68hc1x: broken symlink: /usr/bin/m68hc12-gasp -> m68hc11-gasp)

[Debian Bug Tracking System]

Your message dated Sat, 18 Mar 2017 12:19:00 +
with message-id 
and subject line Bug#857210: fixed in binutils-m68hc1x 1:2.18-9
has caused the Debian Bug report #857210,
regarding binutils-m68hc1x: broken symlink: /usr/bin/m68hc12-gasp -> 
m68hc11-gasp
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.)


-- 
857210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: binutils-m68hc1x
Version: 1:2.18-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m30.4s ERROR: FAIL: Broken symlinks:
  /usr/bin/m68hc12-gasp -> m68hc11-gasp

The m68hc11-gasp binary seems to be missing, but the manpage is there.


cheers,

Andreas


binutils-m68hc1x_1:2.18-8.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: binutils-m68hc1x
Source-Version: 1:2.18-9

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated binutils-m68hc1x package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 18 Mar 2017 12:21:41 +0100
Source: binutils-m68hc1x
Binary: binutils-m68hc1x
Architecture: source
Version: 1:2.18-9
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Paul Gevers 
Description:
 binutils-m68hc1x - binary utilities that support Motorola's 68HC11/12 targets
Closes: 857210
Changes:
 binutils-m68hc1x (1:2.18-9) unstable; urgency=medium
 .
   * QA upload
   * Removed unneeded gasp manpage since gasp was eliminated as a distinct
 binary somewhere around 2002 (Closes: #857210)
Checksums-Sha1:
 12660192d1cf2901f465b2bd1af59deab5265c30 1617 binutils-m68hc1x_2.18-9.dsc
 9a5a515644883af6cb2e0cadee5a86b66838eb4e 62096 
binutils-m68hc1x_2.18-9.debian.tar.xz
Checksums-Sha256:
 1ccbe81bfb46453e30f0833e78d5dfbebf672e83a2fb8aa0bae08d5361705d10 1617 
binutils-m68hc1x_2.18-9.dsc
 75c644813db32a700c8abf4e4f8a02dc69f3feb733b126a9c6c8564045704692 62096 
binutils-m68hc1x_2.18-9.debian.tar.xz
Files:
 ef57e6a84246e4d5149e13d9de325110 1617 devel extra binutils-m68hc1x_2.18-9.dsc
 9c8832b348086f3a4dcc5c7a24346481 62096 devel extra 
binutils-m68hc1x_2.18-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCAAwFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAljNIJQSHGVsYnJ1c0Bk
ZWJpYW4ub3JnAAoJEJxcmesFvXUKpTUH/1x/hoyy+dk/NcAZ8SfeHaE0H16jphou
MsLZxivdMWnW6XRySKjqN4jyURgNrTkWb5o3V0XEUMjRXp5vAX/y78c4ftdVc86O
WKjztCLYDEbZOxV8X/MEbdc63mbF4faFIZVJwuyuspq7O/NnSsh2sOyWcEbSz+Fs
uigmWu/WOuSLUK+tqqAyazNkhsk8PPCEtDJ5MlsrnL5FOrm4HTZ5aE+yUJ9DeyG6
T8Psn1e7b9jZ9KysvwqbG+0dKkUOTN6EbI5nQ+F2CgIusNgqAk/pP/WDghXkxgNH
HcMmBUluID4RzgwCvIdCRA3HD1VR4XSgwM63xz57Quimr39mSNlCL3w=
=H1r1
-END PGP SIGNATURE End Message ---

Bug#857346: Segmentation Fault when trying to use get_hwaddr()

[Evgeni Golov]

On Fri, Mar 17, 2017 at 08:11:18PM +0100, Reiner Herrmann wrote:
> On Fri, Mar 17, 2017 at 07:45:49PM +0100, Evgeni Golov wrote:
> > It's now on 
> > https://fedorapeople.org/cgit/dsommers/public_git/python-ethtool.git/
> 
> Is that the official repository? It looks outdated (version 0.12 is
> missing there).

It is at least the same repo (but a different url, cgit instead of gitweb) as 
before.
I could not find any newer version or repo yet.

> > I am currently looking into #845323 and wonder if that is related to this.
> 
> It's very likely the same issue:
> 
> $ grep -r ethtool
> ovirt-guest-agent/GuestAgentLinux2.py: import ethtool
> ovirt-guest-agent/GuestAgentLinux2.py:  'hw': 
> self.ethtool.get_hwaddr(dev)})

Yepp, but I wanted to be sure ;)

Processed: Re: Bug#858046: logtool: uninstallable

[Debian Bug Tracking System]

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

> severity 858046 grave
Bug #858046 [logtool] logtool: uninstallable
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#858104: win32-loader: FTBFS (error parsing Built-Using field)

[Santiago Vila]

Package: src:win32-loader
Version: 0.8.1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
/bin/sh: 1: test: xloadlin: unexpected operator
/bin/sh: 1: test: xnsis: unexpected operator
/bin/sh: 1: test: xloadlin: unexpected operator
/bin/sh: 1: test: xnsis: unexpected operator
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/bin/sh: 1: test: xloadlin: unexpected operator
/bin/sh: 1: test: xnsis: unexpected operator
/bin/sh: 1: test: xloadlin: unexpected operator

[... snipped ...]

Total size:   632178 / 1137727 bytes (55.5%)

1 warning:
  Generating version information for language "1033-English" without standard 
key "FileVersion"
du -h win32-loader.exe
620Kwin32-loader.exe
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_auto_test -i
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
/bin/sh: 1: test: xloadlin: unexpected operator
/bin/sh: 1: test: xnsis: unexpected operator
/bin/sh: 1: test: xloadlin: unexpected operator
/bin/sh: 1: test: xnsis: unexpected operator
dh binary-indep
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i
   dh_prep -i
   dh_auto_install -i
   dh_install -i
   dh_installdocs -i
   dh_installchangelogs -i
   dh_perl -i
   dh_link -i
   dh_strip_nondeterminism -i
   dh_compress -i
   dh_fixperms -i
   dh_installdeb -i
   debian/rules override_dh_gencontrol
make[1]: Entering directory '/<>'
/bin/sh: 1: test: xloadlin: unexpected operator
/bin/sh: 1: test: xnsis: unexpected operator
/bin/sh: 1: test: xloadlin: unexpected operator
/bin/sh: 1: test: xnsis: unexpected operator
dh_gencontrol -- -Vw32-loader:built-using="grub2 (= 2.02~beta3-5), cpio (= 
2.11+dfsg-6), gzip (= 1.6-5), gnupg2 (= 2.1.18-6), debian-archive-keyring (= 
2014.3), loadlin (1.6f-5) (= 1.6f-5+b1), ipxe (= 1.0.0+git-20161027.b991c67-1), 
nsis (2.51-1) (= 2.51-1+b1), libgcrypt20 (= 1.7.6-1), libgpg-error (= 1.26-2), "
dpkg-gencontrol: warning: can't parse dependency loadlin (1.6f-5) (= 1.6f-5+b1)
dpkg-gencontrol: error: error occurred while parsing Built-Using field: grub2 
(= 2.02~beta3-5), cpio (= 2.11+dfsg-6), gzip (= 1.6-5), gnupg2 (= 2.1.18-6), 
debian-archive-keyring (= 2014.3), loadlin (1.6f-5) (= 1.6f-5+b1), ipxe (= 
1.0.0+git-20161027.b991c67-1), nsis (2.51-1) (= 2.51-1+b1), libgcrypt20 (= 
1.7.6-1), libgpg-error (= 1.26-2), 
dh_gencontrol: dpkg-gencontrol -pwin32-loader -ldebian/changelog 
-Tdebian/win32-loader.substvars -Pdebian/win32-loader 
-Vw32-loader:built-using=grub2 (= 2.02~beta3-5), cpio (= 2.11+dfsg-6), gzip (= 
1.6-5), gnupg2 (= 2.1.18-6), debian-archive-keyring (= 2014.3), loadlin 
(1.6f-5) (= 1.6f-5+b1), ipxe (= 1.0.0+git-20161027.b991c67-1), nsis (2.51-1) (= 
2.51-1+b1), libgcrypt20 (= 1.7.6-1), libgpg-error (= 1.26-2),  returned exit 
code 255
debian/rules:79: recipe for target 'override_dh_gencontrol' failed
make[1]: *** [override_dh_gencontrol] Error 2
make[1]: Leaving directory '/<>'
debian/rules:38: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


The same thing happens in the reproducible builds autobuilders:

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

so this should be easy to reproduce.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#857811: [857811] synaptic: On Launch Synaptic Immediately Shuts Down w/Error

[Jörg Frings-Fürst]

Hello S.,
hello Michael,

on several installations the error could not be confirmed.
I therefore go along with the bugreporter to close this bug.

Have a nice weekend

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Processed: Re: [mate-panel?] Mate panel unstable, notification area icons disappear without warning

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #858096 [mate-panel] [mate-panel?] Mate panel unstable, notification area 
icons disappear without warning.
Added tag(s) moreinfo.

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

Bug#858096: [mate-panel?] Mate panel unstable, notification area icons disappear without warning

[John Paul Adrian Glaubitz]

Control: tags -1 moreinfo

Hi Michael!

> On a brand new install of Stretch on 2 different computers (both x86-64)
> mate-panel is unstable and the notification icons (e.g. bluetooth,
> sound, network) disappear without warning. This also occurred when Mate
> 1.16 was released on an old install of Stretch that was upgraded from
> Jessie, at the time I thought my settings may have caused the problem.

Could you please provide the contents of ~/.xession-errors after the error
has occurred? If there are any components of MATE crashing, it should show
up in that log file. Also, can you check your syslog or dmesg for any
crash messages?

> 500 testing ftp.deb-multimedia.org

Please be aware that you are mixing in packages from an external source and
you are therefore creating a so-called FrankenDebian [1]. Debian Multimedia
is not an official Debian repository and should only ever add it with down-
graded priority (less than 500). Otherwise APT will randomly pull in packages
from that source.

Adrian

> [1] https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#854078: network-manager: nm-online returns before network devices got an address

[Uwe Kleine-König]

Hello Michael,

On Sat, Mar 18, 2017 at 12:10:48AM +0100, Michael Biebl wrote:
> I've updated the packages at [1] to 1.6.2-3~test0 including the patches
> from the th/device-wifi-wait-for-scan-bgo770938 branch.
> 
> Would be great if you can give those packages a try and report back.

I installed
{gir1.2-networkmanager-1.0,libnm{-glib4,-util2,0},network-manager}=1.6.2-3~test0
(i.e. all packages from the network-manager source package that I had
installed in an earlier version) and the problem doesn't reproduce any
more.

Thanks
Uwe


signature.asc
Description: PGP signature

Bug#857121: marked as done (biosig4c++ FTBFS on architectures where char is unsigned)

[Debian Bug Tracking System]

Your message dated Sat, 18 Mar 2017 09:05:13 +
with message-id 
and subject line Bug#857121: fixed in biosig4c++ 1.3.0-2.2
has caused the Debian Bug report #857121,
regarding biosig4c++ FTBFS on architectures where char is unsigned
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.)


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

https://buildd.debian.org/status/package.php?p=biosig4c%2B%2B=sid

...
gcc -c -pipe -fPIC -Wall -fno-builtin-memcmp -O2 -D=WITH_ZLIB  -D=__4HAERTEL__ 
-D=WITH_FAMOS -D=WITH_CHOLMOD -D=WITHOUT_NETWORK -Wextra  -I 
/usr/include/libxml2/ -o "scp-decode.o" "t210/scp-decode.cpp"
In file included from t210/scp-decode.cpp:113:0:
t210/codes.h:25:37: error: narrowing conversion of '-1' from 'int' to 'char' 
inside { } [-Wnarrowing]
 static const char STR_END[]={-1,'\0'};
 ^
...
--- End Message ---
--- Begin Message ---
Source: biosig4c++
Source-Version: 1.3.0-2.2

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

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
biosig4c++ package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 18 Mar 2017 08:37:44 +0100
Source: biosig4c++
Binary: libbiosig1 libbiosig1-dbg libbiosig-dev biosig-tools python-biosig 
octave-biosig
Architecture: source amd64
Version: 1.3.0-2.2
Distribution: sid
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: John Paul Adrian Glaubitz 
Description:
 biosig-tools - format conversion tools for biomedical data formats
 libbiosig-dev - I/O library for biomedical data - development files
 libbiosig1 - I/O library for biomedical data - dynamic library
 libbiosig1-dbg - I/O library for biomedical data - debug symbols
 octave-biosig - Octave bindings for BioSig library
 python-biosig - Python bindings for BioSig library
Closes: 857121
Changes:
 biosig4c++ (1.3.0-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches:
 - added fix_STR_END_signage_FTBFS from upstream to fix FTBFS
   on architectures where char is unsigned (Closes: #857121)
Checksums-Sha1:
 b08bb5e2b9fccd92e15a7cb08f8b15472d91f390 2361 biosig4c++_1.3.0-2.2.dsc
 80452e953fe5fffb2312e6f89bce243445b2d8ca 13968 
biosig4c++_1.3.0-2.2.debian.tar.xz
 d2ebba563a5b617c3d1c09f2df82ffe85fe7113d 177452 
biosig-tools_1.3.0-2.2_amd64.deb
 8828c377ad8fb1bef4db7fb44af020b3f4436f52 13881 
biosig4c++_1.3.0-2.2_amd64.buildinfo
 d98c2f3f58fc7477940b4fc3d19006e70523e06b 285892 
libbiosig-dev_1.3.0-2.2_amd64.deb
 a20dcbddee11d82b0d7d79595dbb6498ddfc5a4e 66414 
libbiosig1-dbg_1.3.0-2.2_amd64.deb
 ef15892bf45a927eeb234da3c5804906ec2d83f3 265180 libbiosig1_1.3.0-2.2_amd64.deb
 1b2e8bdbcde9a290d168c4d3b0783ae91579de35 19638 
octave-biosig_1.3.0-2.2_amd64.deb
 14944dc20e4f0ca233f9a1be2841da320ecd09c4 32326 
python-biosig_1.3.0-2.2_amd64.deb
Checksums-Sha256:
 1879726cc5d9c34f046231654058f9cb0d53bf9b27e49052d9eefa47b9b583d2 2361 
biosig4c++_1.3.0-2.2.dsc
 5b554956c29d059d71de7fa5db551f8a80a37ae4f18cf6f91fc97f149e7cc32b 13968 
biosig4c++_1.3.0-2.2.debian.tar.xz
 6dcc43acd9c2dd42670f9add6aea2c8fef7d6bd6589cd42fc549ad2483912bcb 177452 
biosig-tools_1.3.0-2.2_amd64.deb
 dbc72f5bd7f859b10c72e9b7309a63d1a9b07727b60a8fab49a359bddd945be2 13881 
biosig4c++_1.3.0-2.2_amd64.buildinfo
 107167ed7ce4ce942b0398f79250cd8d45ac32810b5530ba991ef51b06656b4f 285892 
libbiosig-dev_1.3.0-2.2_amd64.deb
 ff9af331c302f4c5c74c80824a882c1b7780bfbdf52b5bd86d7c0c9ea125e747 66414 
libbiosig1-dbg_1.3.0-2.2_amd64.deb
 b77a7f9ce2b36cc6eb814e885a3bc4686aa5da221a09ea97e44dedba75ec8077 265180 
libbiosig1_1.3.0-2.2_amd64.deb
 90eed1c89711a60cb131b2871cd933e442fcc855ede9af7ef067c134c5521fe4 19638 
octave-biosig_1.3.0-2.2_amd64.deb
 

Bug#858096: [mate-panel?] Mate panel unstable, notification area icons disappear without warning.

[michael (C0bb3r)]

Package: mate-panel
Version: 1.16.0-2
Severity: serious

--- Please enter the report below this line. ---

On a brand new install of Stretch on 2 different computers (both x86-64) 
mate-panel is unstable and the notification icons (e.g. bluetooth, 
sound, network) disappear without warning. This also occurred when Mate 
1.16 was released on an old install of Stretch that was upgraded from 
Jessie, at the time I thought my settings may have caused the problem. 
Now I am wondering if this is a gtk3 incompatibility issue.


I have tried various icons (Moblin, Gnome-Brave, default Mate just to 
name a few) and the same thing happens. Created new test-user with 
default settings (nothing from my old settings was migrated to the new 
user) using default icons and panel layout and the icons disappeared 
after about 10 minutes.


The only icon (if it is available) that ever stays is the, added by me, 
shutdown icon. Icons can be brought back by clicking where they are 
supposed to be and opening one of the options provided in the drop down 
menu (e.g. click on location sound icon was and a menu will appear, open 
Sound Preferences and the icon will reappear and stay while sound 
preferences is open). This indicates the location is still being used by 
the process even though the icon has disappeared.


Occasionally the workspaces area also disappears and nothing but a 
reboot will bring it back.


I'm happy to provide any information required if you can provide tell me 
how to obtain it.

Cheers.
Michael.


--- System information. ---
Architecture:
Kernel: Linux 4.9.0-2-amd64

Debian Release: 9.0
500 testing ftp.deb-multimedia.org
500 testing ftp.au.debian.org

--- Package information. ---
Depends (Version) | Installed
-+-
libmate-panel-applet-4-1 (= 1.16.0-2) | 1.16.0-2
mate-desktop | 1.16.1-1
mate-menus | 1.16.0-2
mate-panel-common (= 1.16.0-2) | 1.16.0-2
mate-polkit | 1.16.0-2
menu-xdg | 0.5
dconf-gsettings-backend | 0.26.0-2+b1
OR gsettings-backend |
libatk1.0-0 (>= 1.12.4) | 2.22.0-1
libc6 (>= 2.14) | 2.24-9
libcairo-gobject2 (>= 1.10.0) | 1.14.8-1
libcairo2 (>= 1.4.10) | 1.14.8-1
libcanberra-gtk3-0 (>= 0.25) | 0.30-3
libcanberra0 (>= 0.2) | 0.30-3
libdbus-1-3 (>= 1.9.14) | 1.10.16-1
libdbus-glib-1-2 (>= 0.78) | 0.108-2
libdconf1 (>= 0.14.0) | 0.26.0-2+b1
libgdk-pixbuf2.0-0 (>= 2.22.0) | 2.36.5-2
libglib2.0-0 (>= 2.37.3) | 2.50.3-1
libgtk-3-0 (>= 3.19.12) | 3.22.8-1
libice6 (>= 1:1.0.0) | 2:1.0.9-2
libmate-desktop-2-17 (>= 1.14.0) | 1.16.1-1
libmate-menu2 (>= 1.6.0) | 1.16.0-2
libmateweather1 (>= 1.6.2) | 1.16.1-2
libpango-1.0-0 (>= 1.18.0) | 1.40.4-1
libpangocairo-1.0-0 (>= 1.14.0) | 1.40.4-1
librsvg2-2 (>= 2.14.4) | 2.40.16-1+b1
libsm6 | 2:1.2.2-1+b3
libstartup-notification0 (>= 0.2) | 0.12-4
libwnck-3-0 (>= 3.4.7) | 3.20.1-3
libx11-6 | 2:1.6.4-3
libxau6 | 1:1.0.8-1
libxrandr2 (>= 2:1.2.99.3) | 2:1.5.1-1


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#858095: atlc FTBFS on mips: Build killed with signal TERM after 360 minutes of inactivity

[Adrian Bunk]

Source: atlc
Version: 4.6.1-1
Severity: serious

https://buildd.debian.org/status/logs.php?pkg=atlc=mips

...
PASS: 13a-check_rect_cen_in_rect.test
PASS: 13b-check_rect_cen_in_rect.test
PASS: 13c-check_rect_cen_in_rect.test
PASS: 13d-check_rect_cen_in_rect.test
PASS: 14a-check-circ-in-rect.test
PASS: 14b-check-circ-in-rect.test
PASS: 14c-check-circ-in-rect.test
PASS: 14d-check-circ-in-rect.test
PASS: WARNING-The-next-test-is-a-benchmark-and-takes-a-long-while.test
E: Caught signal ‘Terminated’: terminating immediately
make[3]: *** wait: No child processes.  Stop.
make[3]: *** Waiting for unfinished jobs
make[3]: *** wait: No child processes.  Stop.
make[2]: *** wait: No child processes.  Stop.
make[2]: *** Waiting for unfinished jobs
make[2]: *** wait: No child processes.  Stop.
make[1]: *** wait: No child processes.  Stop.
make[1]: *** Waiting for unfinished jobs
make[1]: *** wait: No child processes.  Stop.
make: *** wait: No child processes.  Stop.
make: *** Waiting for unfinished jobs
make: *** wait: No child processes.  Stop.
Build killed with signal TERM after 360 minutes of inactivity


The latest successful build of the same source took 17 minutes.
This includes configuring, building and running all tests.

Now one test is taking over 6 hours (is that completely hanging?).

Bug#857121: biosig4c++ FTBFS on architectures where char is unsigned

[John Paul Adrian Glaubitz]

Control: tags -1 patch

On 03/18/2017 07:54 AM, Alois Schloegl wrote:
> -static const char STR_END[]={-1,'\0'};
> +static const char STR_END[]={(char)-1,'\0'};
>  static char STR_NULL[]=" unspecified/unknown ";

I'm not sure whether I like that patch because I would rather get rid of the
out-of-range value inside a const char but I guess the fix will at least let
us get the package fixed for Stretch.

The patch works, of course. I have just verified that this is the only change
required to fix the package on the affected architectures. Will prepare an NMU.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Processed: Re: biosig4c++ FTBFS on architectures where char is unsigned

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #857121 [src:biosig4c++] biosig4c++ FTBFS on architectures where char is 
unsigned
Added tag(s) patch.

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

Bug#857121: biosig4c++ FTBFS on architectures where char is unsigned

[Alois Schloegl]

This bug was fixed upstream in
   commit 8e7c3d7e485e1d3af3f3094641282274424b7385

Attaches is the corresponding patch.


Thanks for consideration,
   Alois
commit 8e7c3d7e485e1d3af3f3094641282274424b7385
Author: Christoph Schmidt-Hieber 
Date:   Sat Dec 10 16:50:41 2016 +0100

Fix compilation with gcc6 on armhf. See Debian Bug #847526

diff --git a/biosig4c++/t210/codes.h b/biosig4c++/t210/codes.h
index 4db65b2..53affbf 100644
--- a/biosig4c++/t210/codes.h
+++ b/biosig4c++/t210/codes.h
@@ -22,7 +22,7 @@ Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA  02111-1307, USA.
 #ifndef __CODES_H__
 #define __CODES_H__
 
-static const char STR_END[]={-1,'\0'};
+static const char STR_END[]={(char)-1,'\0'};
 static char STR_NULL[]=" unspecified/unknown ";
 
 static alfabetic _special[]={

Bug#850994: marked as done (berkshelf: FTBFS: ERROR: Test "ruby2.3" failed.)

[Debian Bug Tracking System]

Your message dated Sat, 18 Mar 2017 06:48:58 +
with message-id 
and subject line Bug#850994: fixed in berkshelf 4.3.5-2
has caused the Debian Bug report #850994,
regarding berkshelf: FTBFS: ERROR: Test "ruby2.3" failed.
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.)


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

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> fatal: Not a git repository (or any of the parent directories): .git
> GEM_PATH=debian/berkshelf/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"berkshelf\"
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/berkshelf/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=debian/berkshelf/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation
> Run options:
>   include {:focus=>true}
>   exclude {:not_supported_on_windows=>false}
> 
> All examples were filtered out; ignoring {:focus=>true}
> 
> Berkshelf::Berksfile
>   ClassMethods
> ::from_file
>   reads the content of the Berksfile and binds them to a new instance
>   returns an instance of Berkshelf::Berksfile
>   when Berksfile does not exist at given path
> raises BerksfileNotFound
>   #cookbook
> sends the add_dependency message with the name, constraint, and options 
> to the instance of the includer
> merges the default options into specified options
> converts a single specified group option into an array of groups
> is a DSL method
> when no constraint specified
>   sends the add_dependency message with a nil value for constraint
> when no options specified
>   sends the add_dependency message with an empty Hash for the value of 
> options
>   #group
> sends the add_dependency message with an array of groups determined by 
> the parameter to the group block
> is a DSL method
>   #metadata
> sends the add_dependency message with an explicit version constraint and 
> the path to the cookbook
> is a DSL method
>   #source
> is a DSL method
> adds a source to the sources
> converts the string to a Source
> adds each source in order they appear
> does not add duplicate entries
> adding an invalid source
>   raises an InvalidSourceURI
>   #sources
> when there are no sources
>   raises an exception
> when there are sources
>   returns an Array
>   contains a collection of Berkshelf::Source
>   #site
> raises a Berkshelf::Deprecated error
> is a DSL method
>   #chef_api
> raises a Berkshelf::Deprecated error
> is a DSL method
>   #extension
> is a DSL method
>   #dependencies
> returns all Berkshelf::Dependencys added to the instance of Berksfile
>   #cookbooks
> raises an exception if a cookbook is not installed
> retrieves the locked (cached) cookbook for each dependency
>   #groups
> returns a hash containing keys for every group a dependency is a member of
> returns an Array of Berkshelf::Dependencys who are members of the group 
> for value
>   #add_dependency
> adds new dependency to the list of dependencies
> is a Berkshelf::Dependency
> has a name matching the given name
> has a version_constraint matching the given constraint
> raises DuplicateDependencyDefined if multiple dependencies of the same 
> name are found
> has a nil