Bug#840365: 1:45.4.0-1 broke the External Editor plugin

[Carsten Schoenert]

Hello Craig,

On Tue, Oct 11, 2016 at 10:42:31AM +1100, Craig Sanders wrote:
> The External Editor plugin (from http://globs.org/articles.php?lng=en=2)
> was working in icedove up until this upgrade, stopped working immediately
> after.
> 
> Everything looks OK until you select "Edit in External Editor" from the Tools
> menu, and then nothing happens - no gvim as expected.

did you check if this issue also happen with the official version?

https://www.mozilla.org/en-US/thunderbird/all/

The changes in 45.3.0 and 45.4.0 are rather small and mostly happen
inside the JS/IDL thing. I expect to see this issue within the official
version too. Than the plugin needs to be fixed.

Regards
Carsten

Bug#839116: ITP: node-webcomponentsjs-custom-element-v0 -- CustomElements polyfill from the webcomponentsjs project

[Potter, Tim (HPE Linux Support)]

Hi Jérémy.  Just circling back to this after spending time on other things.

On 29 Sep 2016, at 7:31 PM, Jérémy Lal  wrote:
> Packaging only custom-elements actually makes sense in the long term !
> 
> Here's why: currently only the custom-elements part of the v0 spec
> seems to be surviving. The HTML Imports is not supported by firefox [0], and 
> the
> Shadow DOM v0 is hard to polyfill - the version in webcomponents is full of 
> compromises
> and workarounds (just look at the polyfill code size and the fact no new 
> releases happened
> for months).
> Shadom DOM v1 is being upstreamed to whatwg DOM spec [1],
> and some libs are implementing parts of it like the named slots api [2].
> 
> So... i don't know what's the best solution. Using the correct upstream is 
> always better, unless
> the alternate upstream is actually a better maintained fork.

I think I'll go with only custom-element for the moment.  If this turns out to 
be a mistake
it shouldn't be too hard to recover by packaging the full library as 
libjs-webcomponents-js
and judicious use of

> In any case my remark about using libjs is still valid (and sorry for my 
> "wrong" words, i usually
> try to be less rude even before my morning coffee).

I've renamed to libjs-webcomponentsjs-custom-element-v0.


Tim.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#840381: RFP: mdm-display-manager -- MDM Display Manager

[Protserovsd]

Package: wnpp
Severity: wishlist

* Package name: mdm-display-manager
  Version : 2.0.10
* URL : https://github.com/linuxmint/mdm
* License : GPL
  Programming Lang: C
  Description : MDM Display Manager

The MDM Display Manager (MDM) is a display manager that
implements all significant features required for managing
local displays.
It provides your system with a nice login screen which is easy to use, to
configure and to theme.

There is a "debian" directory in MDM's git repository. However, in Linux Mint
this package is named "mdm", and this name conflicts with the name of "mdm"
package in Debian, which has nothing to do with MDM Display Manager
(https://packages.debian.org/jessie/mdm). It was suggested to use Linux Mint's
"debian" directory as an inspiration.

Bug#840380: fpga-icestorm: Allow all console users access to the USB device

[Petter Reinholdtsen]

Package: fpga-icestorm
Version: 0~20160218gitf2b2549-2
Tags: patch
Severity: important

When installing Debian, the initial user was traditionally made a member
of the plugdev group, and this granted access to local hardware dongles
when this user is logged in.  This approach causes problems for users
originating from directory services like LDAP and Active Directory, as
such plugdev membership can not be granted globally.  The plugdev
membership can be assigned during login (using pam_group), but still
this approach is problematic because left behind processes keep the
group membership even when the user is no longer logged in on the
machine, allowing background processes to get access to other peoples
hardware.

There is an alternative to group membership for device access, using
ACL, and with systemd this is the recommended default.  To enable it for
a given device, the 'access' tag can be set.

Please do so for the fpga-icestorm udev rule, to allow the device to
work for any console user, not only the one created during installation.
Here is a patch:

diff -ur fpga-icestorm/debian/40-fpga-icestorm.rules 
fpga-icestorm-0~20160218gitf2b2549/debian/40-fpga-icestorm.rules
--- fpga-icestorm/debian/40-fpga-icestorm.rules 2016-10-11 04:59:54.702535444 
+
+++ fpga-icestorm-0~20160218gitf2b2549/debian/40-fpga-icestorm.rules
2016-10-11 04:58:39.921570952 +
@@ -1 +1 @@
-ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", MODE="0660", GROUP="plugdev"
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", MODE="0660", 
GROUP="plugdev", TAG+="uaccess"

I suspect the plugdev/mode part can be removed, but did not suggest to
do so at this time because I am unsure how it affect non-systemd users.

-- 
Happy hacking
Petter Reinholdtsen

Bug#840379: jessie-pu: package bash/4.3-11+deb8u1

[Salvatore Bonaccorso]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Hi Stable release managers,

X-Debbugs-CC Matthias Klose  if he agrees, or would
me to drop in case he would like to do the upload himself.

bash in Stable is affected by

CVE-2016-0634: Arbitrary code execution via malicious hostname

and

CVE-2016-7543: Specially crafted SHELLOPTS+PS4 variables allows
command substitution

which both are considered no-dsa (actually the first one unimportant,
thus it's not tagged no-dsa in the security tracker). I have prepared
an update for bash picking the two upstream patches for th 4.3 branch.
Attached is the debdiff.

Would it be acceptable for the/an upcoming Jessie point release?

Regards,
Salvatore
diff -Nru bash-4.3/debian/changelog bash-4.3/debian/changelog
--- bash-4.3/debian/changelog	2014-10-07 16:22:00.0 +0200
+++ bash-4.3/debian/changelog	2016-10-09 17:35:21.0 +0200
@@ -1,3 +1,12 @@
+bash (4.3-11+deb8u1) jessie; urgency=medium
+
+  * Non-maintainer upload.
+  * CVE-2016-0634: Arbitrary code execution via malicious hostname
+  * CVE-2016-7543: Specially crafted SHELLOPTS+PS4 variables allows command
+substitution
+
+ -- Salvatore Bonaccorso   Sun, 09 Oct 2016 17:35:21 +0200
+
 bash (4.3-11) unstable; urgency=medium
 
   * Apply upstream patches 028 - 030.
diff -Nru bash-4.3/debian/patches/CVE-2016-0634.diff bash-4.3/debian/patches/CVE-2016-0634.diff
--- bash-4.3/debian/patches/CVE-2016-0634.diff	1970-01-01 01:00:00.0 +0100
+++ bash-4.3/debian/patches/CVE-2016-0634.diff	2016-10-09 17:35:21.0 +0200
@@ -0,0 +1,109 @@
+			 BASH PATCH REPORT
+			 =
+
+Bash-Release:	4.3
+Patch-ID:	bash43-047
+
+Bug-Reported-by:	Bernd Dietzel
+Bug-Reference-ID:
+Bug-Reference-URL:	https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1507025
+
+Bug-Description:
+
+Bash performs word expansions on the prompt strings after the special
+escape sequences are expanded.  If a malicious user can modify the system
+hostname or change the name of the bash executable and coerce a user into
+executing it, and the new name contains word expansions (including
+command substitution), bash will expand them in prompt strings containing
+the \h or \H and \s escape sequences, respectively.
+
+Patch (apply with `patch -p0'):
+
+--- a/parse.y
 b/parse.y
+@@ -5251,7 +5251,7 @@ decode_prompt_string (string)
+ #if defined (PROMPT_STRING_DECODE)
+   int result_size, result_index;
+   int c, n, i;
+-  char *temp, octal_string[4];
++  char *temp, *t_host, octal_string[4];
+   struct tm *tm;  
+   time_t the_time;
+   char timebuf[128];
+@@ -5399,7 +5399,11 @@ decode_prompt_string (string)
+ 
+ 	case 's':
+ 	  temp = base_pathname (shell_name);
+-	  temp = savestring (temp);
++	  /* Try to quote anything the user can set in the file system */
++	  if (promptvars || posixly_correct)
++		temp = sh_backslash_quote_for_double_quotes (temp);
++	  else
++		temp = savestring (temp);
+ 	  goto add_string;
+ 
+ 	case 'v':
+@@ -5489,9 +5493,17 @@ decode_prompt_string (string)
+ 
+ 	case 'h':
+ 	case 'H':
+-	  temp = savestring (current_host_name);
+-	  if (c == 'h' && (t = (char *)strchr (temp, '.')))
++	  t_host = savestring (current_host_name);
++	  if (c == 'h' && (t = (char *)strchr (t_host, '.')))
+ 		*t = '\0';
++	  if (promptvars || posixly_correct)
++		/* Make sure that expand_prompt_string is called with a
++		   second argument of Q_DOUBLE_QUOTES if we use this
++		   function here. */
++		temp = sh_backslash_quote_for_double_quotes (t_host);
++	  else
++		temp = savestring (t_host);
++	  free (t_host);
+ 	  goto add_string;
+ 
+ 	case '#':
+--- a/y.tab.c
 b/y.tab.c
+@@ -7563,7 +7563,7 @@ decode_prompt_string (string)
+ #if defined (PROMPT_STRING_DECODE)
+   int result_size, result_index;
+   int c, n, i;
+-  char *temp, octal_string[4];
++  char *temp, *t_host, octal_string[4];
+   struct tm *tm;  
+   time_t the_time;
+   char timebuf[128];
+@@ -7711,7 +7711,11 @@ decode_prompt_string (string)
+ 
+ 	case 's':
+ 	  temp = base_pathname (shell_name);
+-	  temp = savestring (temp);
++	  /* Try to quote anything the user can set in the file system */
++	  if (promptvars || posixly_correct)
++		temp = sh_backslash_quote_for_double_quotes (temp);
++	  else
++		temp = savestring (temp);
+ 	  goto add_string;
+ 
+ 	case 'v':
+@@ -7801,9 +7805,17 @@ decode_prompt_string (string)
+ 
+ 	case 'h':
+ 	case 'H':
+-	  temp = savestring (current_host_name);
+-	  if (c == 'h' && (t = (char *)strchr (temp, '.')))
++	  t_host = savestring (current_host_name);
++	  if (c == 'h' && (t = (char *)strchr (t_host, '.')))
+ 		*t = '\0';
++	  if (promptvars || posixly_correct)
++		/* Make sure that expand_prompt_string is called with a
++		   second argument of Q_DOUBLE_QUOTES if we 

Bug#820888: [pkg-cryptsetup-devel] Bug#820888: cryptsetup: initramfs cryptroot zfs support

[Fabian Grünbichler]

On October 10, 2016 9:09:12 PM GMT+02:00, Guilhem Moulin  
wrote:
>Hi Fabian,
>
>On Mon, 10 Oct 2016 at 20:42:00 +0200, Fabian Grünbichler wrote:
>> + [ -r /conf/conf.d/cryptroot ]
>> + exit 0
>
>Looks like /conf/conf.d/cryptroot wasn't generated by the hook script.
>Try adding the option ‘initramfs’ on the 4th column of the crypttab(5)
>entry for each underlying device.  This should force unlocking of these
>devices at initramfs stage.
>
>Hope that helps,
>cheers,

Works like a charm! That was unexpectedly easy, thanks!

Bug#827335: evince: assertion failed: (wayland_display->cursor_theme_name)

[Diane Trout]

On Mon, 2016-10-10 at 18:50 -0500, Jason Crain wrote:
> On Tue, Jun 14, 2016 at 06:58:06PM -0700, Diane Trout wrote:
> > I launched evince running under wayland from gnome terminal and it
> > immediately
> > crashed with an
> > assertion failed.
> > 
> > (evince:4492): Gtk-WARNING **: Theme parsing error: :56:20:
> > The 'gtk-key-
> > bindings' property has been renamed to '-gtk-key-bindings'
> > [New Thread 0x7f50825f6700 (LWP 4500)]
> > **
> > Gdk:ERROR:/build/gtk+3.0-UYMeaD/gtk+3.0-
> > 3.20.6/./gdk/wayland/gdkdisplay-
> > wayland.c:827:_gdk_wayland_display_get_scaled_cursor_theme:
> > assertion failed:
> > (wayland_display->cursor_theme_name)
> > 
> > Program received signal SIGABRT, Aborted.
> 
> 
> I haven't been able to reproduce this.  Do you still see this problem
> under more recent versions of gtk and evince?  Do you have some
> cursor
> theme enabled and does the problem stop if you disable the cursor
> theme?
> Does it only happen under wayland and not xorg?
> 

It certainly only happens under wayland, and possibly only with the
dark theme. I think it does work under X.


I managed to get a stack trace

(gdb) 
(gdb) 
(gdb) 
(gdb) bt full
#0  0x7ffaec41dfdf in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:58
set = 
{__val = {0, 0, 0, 0, 0, 140715694469232, 140715694474080,
14071571374, 140727320157392, 140715720592191, 188,
140715735165396, 5, 0, 2064, 140715682110936}}
pid = 
tid = 
#1  0x7ffaec41f40a in __GI_abort () at abort.c:89
save_stage = 2
act = 
  {__sigaction_handler = {sa_handler = 0xbc, sa_sigaction =
0xbc}, sa_mask = {__val = {240, 3, 219043332109, 0, 0, 472446402651, 0,
0, 140715685853952, 140715685854040, 0, 140715685853952, 336, 208,
94377005673952, 188}}, sa_flags = -319044768, sa_restorer =
0x55d5dbe5ede0}
sigs = {__val = {32, 0 }}
#2  0x7ffaecd1b4d5 in g_assertion_message (domain=domain@entry=0x7f
faee1f520e "Gdk", file=file@entry=0x7ffaee21b828 "/build/gtk+3.0-
dN7rjx/gtk+3.0-3.22.1/./gdk/wayland/gdkdisplay-wayland.c", line=line@en
try=1012, func=func@entry=0x7ffaee21bce0 <__func__.65775>
"_gdk_wayland_display_get_scaled_cursor_theme", message=message@entry=0
x55d5dbe5bfc0 "assertion failed: (display_wayland->cursor_theme_name)")
at ././glib/gtestutils.c:2429
lstr =
"1012\000\177\000\000\000\246\375\256\274\301sx\000\000\000\000\000\000
\000\000h\271!\356\372\177\000"
s = 0x55d5dbe5ede0 "p\357\345\333\325U"
#3  0x7ffaecd1b56a in g_assertion_message_expr (domain=domain@entry
=0x7ffaee1f520e "Gdk", file=file@entry=0x7ffaee21b828 "/build/gtk+3.0-
dN7rjx/gtk+3.0-3.22.1/./gdk/wayland/gdkdisplay-wayland.c", line=line@en
try=1012, func=func@entry=0x7ffaee21bce0 <__func__.65775>
"_gdk_wayland_display_get_scaled_cursor_theme", expr=expr@entry=0x7ffae
e21b968 "display_wayland->cursor_theme_name") at
././glib/gtestutils.c:2452
s = 0x55d5dbe5bfc0 "assertion failed: (display_wayland-
>cursor_theme_name)"
#4  0x7ffaee1e80d6 in _gdk_wayland_display_get_scaled_cursor_theme
(display_wayland=display_wayland@entry=0x55d5db8c9040
[GdkWaylandDisplay], scale=) at
././gdk/wayland/gdkdisplay-wayland.c:1012
theme = 
__func__ = "_gdk_wayland_display_get_scaled_cursor_theme"
#5  0x7ffaee1dd27a in _gdk_wayland_cursor_update (display_wayland=d
isplay_wayland@entry=0x55d5db8c9040 [GdkWaylandDisplay], cursor=cursor@
entry=0x55d5dbe59920 [GdkWaylandCursor])
at ././gdk/wayland/gdkcursor-wayland.c:152
c = 
theme = 
__func__ = "_gdk_wayland_cursor_update"
#6  0x7ffaee1dd4e9 in
_gdk_wayland_display_get_cursor_for_name_with_scale
(display=0x55d5db8c9040 [GdkWaylandDisplay], name=0x7ffaee8a4b3f "nw-
resize", scale=1) at ././gdk/wayland/gdkcursor-wayland.c:355
private = 
---Type  to continue, or q  to quit---
display_wayland = 0x55d5db8c9040 [GdkWaylandDisplay]
scale = 1
name = 0x7ffaee8a4b3f "nw-resize"
display = 0x55d5db8c9040 [GdkWaylandDisplay]
private = 
display_wayland = 0x55d5db8c9040 [GdkWaylandDisplay]
#7  0x7ffaee7e7f63 in gtk_window_realize (widget=0x55d5dba12ef0
[EvWindow]) at ././gtk/gtkwindow.c:7336
cursor = 
  {0x7ffaee8a4b3f "nw-resize", 0x7ffaee8a4b61 "n-resize",
0x7ffaee8a4b6a "ne-resize", 0x7ffaee8a4b40 "w-resize", 0x7ffaee8a4b6b
"e-resize", 0x7ffaee8a4b74 "sw-resize", 0x7ffaee8a4b7e "s-resize",
0x7ffaee8a4b87 "se-resize"}
allocation = {x = 0, y = 0, width = 652, height = 699}
child_allocation = {x = 4097, y = 0, width = 1, height =
2020852156}
window = 0x55d5dba12ef0 [EvWindow]
parent_window = 
gdk_window = 0x55d5dbcc6c80 [GdkWaylandWindow]
attributes = 
  {title = 0x55d5db95ebe0 "Document Viewer", event_mask = 256,
x = 0, y = 0, width = 1, height = 1, wclass = GDK_INPUT_ONLY, visual =
0x55d5db8c38c0 [GdkWaylandVisual], window_type = GDK_WINDOW_CHILD,
cursor = 0xed20f660, 

Bug#840378: jessie-pu: package openbox/3.5.2-8+deb8u1

[Salvatore Bonaccorso]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Hi Stable release managers,

In e.g. environments with a huge amount of groups, openbox is
particularly affected by #808138, since openbox did enumerate multiple
time all groups at startup. This was fixed in the recent upload to
unstable and I would like to propose a fix as well for jessie (I know
a environment where using openbox due to a huge amount of groups on
the system, it is massively slowed down).

Attached is the debdiff. The upload has not yet entered testing,
though.

I have also X-Debbugs-CC Mateusz Łukasik.

Regards,
Salvatore
diff -Nru openbox-3.5.2/debian/changelog openbox-3.5.2/debian/changelog
--- openbox-3.5.2/debian/changelog	2014-10-25 14:39:18.0 +0200
+++ openbox-3.5.2/debian/changelog	2016-10-10 09:18:43.0 +0200
@@ -1,3 +1,12 @@
+openbox (3.5.2-8+deb8u1) jessie; urgency=medium
+
+  * Non-maintainer upload.
+  * Add 808138_Replace-getgrent-with-getgroups.patch patch.
+Replace getgrent with getgroups for not enumerate all groups at startup.
+Thanks to Simon  (Closes: #808138)
+
+ -- Salvatore Bonaccorso   Mon, 10 Oct 2016 09:18:43 +0200
+
 openbox (3.5.2-8) unstable; urgency=high
 
   * debian/openbox.install:
diff -Nru openbox-3.5.2/debian/patches/808138_Replace-getgrent-with-getgroups.patch openbox-3.5.2/debian/patches/808138_Replace-getgrent-with-getgroups.patch
--- openbox-3.5.2/debian/patches/808138_Replace-getgrent-with-getgroups.patch	1970-01-01 01:00:00.0 +0100
+++ openbox-3.5.2/debian/patches/808138_Replace-getgrent-with-getgroups.patch	2016-10-10 09:18:43.0 +0200
@@ -0,0 +1,63 @@
+>From e0cb404f53c9b21a521ea2f14c8cd66fdfb68ea7 Mon Sep 17 00:00:00 2001
+From: Simon 
+Date: Tue, 15 Dec 2015 15:46:18 +0100
+Subject: [PATCH] Replace getgrent with getgroups. Fixes #5978.
+
+---
+ obt/paths.c | 34 +-
+ 1 file changed, 21 insertions(+), 13 deletions(-)
+
+diff --git a/obt/paths.c b/obt/paths.c
+index 25cb6b0..d526936 100644
+--- a/obt/paths.c
 b/obt/paths.c
+@@ -108,25 +108,33 @@ static void find_uid_gid(uid_t *u, gid_t **g, guint *n)
+ const gchar *name;
+ struct group *gr;
+ 
++gid_t gmain;
++unsigned int maininc;
++int i;
++
+ *u = getuid();
+ pw = getpwuid(*u);
+ name = pw->pw_name;
+ 
+-*g = g_new(gid_t, *n=1);
+-(*g)[0] = getgid();
+-
+-while ((gr = getgrent())) {
+-if (gr->gr_gid != (*g)[0]) { /* skip the main group */
+-gchar **c;
+-for (c = gr->gr_mem; *c; ++c)
+-if (strcmp(*c, name) == 0) {
+-*g = g_renew(gid_t, *g, ++(*n)); /* save the group */
+-(*g)[*n-1] = gr->gr_gid;
+-break;
+-}
++gmain = getgid();
++
++*n = getgroups(0, *g);
++*g = g_new(gid_t, *n);
++*n = getgroups(*n, *g);
++
++/* Check if the effective group ID of the calling process is already
++   included in the returned list. Add it otherwise. */
++maininc = 0;
++for (i = 0; i < *n; i++) {
++if ( (*g)[i] == gmain ) {
++maininc = 1;
++break;
+ }
+ }
+-endgrent();
++if (!maininc) {
++*g = g_renew(gid_t, *g, ++(*n));
++(*g)[*n-1] = gmain;
++}
+ 
+ qsort(*g, *n, sizeof(gid_t), gid_cmp);
+ }
+-- 
+2.1.4
+
diff -Nru openbox-3.5.2/debian/patches/series openbox-3.5.2/debian/patches/series
--- openbox-3.5.2/debian/patches/series	2014-08-22 22:32:09.0 +0200
+++ openbox-3.5.2/debian/patches/series	2016-10-10 09:18:43.0 +0200
@@ -11,3 +11,4 @@
 fix_rsvg_missing_include.patch
 update_pl_po.patch
 754207_use-scrot.patch
+808138_Replace-getgrent-with-getgroups.patch

Bug#840323: debhelper: cmake build system: cross compilation

[Helmut Grohne]

Hi Holger,

On Mon, Oct 10, 2016 at 09:30:35PM +, Holger Levsen wrote:
> this seems a fairly strong statement, considering
> https://tracker.debian.org/pkg/dpkg-cross shows not a single bug filed
> against the package.

Quoting Neil Williams in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771496#46:
| summary 771496 If anything you are doing would fail after the removal of 
dpkg-cross, you're doing it wrong. It's going away, whether you want it to or 
not.

There is a reason why dpkg-cross is not part of jessie.

Wookey, should we add a blocker bug keep it out of jessie?

Helmut

Bug#840377: pyepl: Please remove build dependency on jade

[Neil Roeth]

Source: pyepl
Severity: normal

The pyepl has a build dependency on jade which is obsolete and will be
removed from Debian.  It doesn't appears that pyepl needs jade at all,
so it can simply be removed.

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

Kernel: Linux 4.3.0-1-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)

-- 
Neil Roeth

Bug#792101: ITP: gogs -- self hosted git service

[Michael Lustfield]

On Mon, Oct 10, 2016 at 6:39 AM, ge...@riseup.net  wrote:
> Hi Michael,
>
> By changing the title of this bug to ITP and recording yourself as the
> owner, can one assume you're packaging gogs within Debian?

Yup, that's exactly what that's meant to indicate.

> If so, any ETA on this?

Nope! Time has been missing, but that tide seems to be receding and
I'm shooting for "sooner than later" but can't provide a whole lot
past that right now.

Bug#840375: dejagnu: Please remove build dependency on jade

[Neil Roeth]

Package: dejagnu
Severity: normal

The dejagnu package build depends on the jade package which is obsolete
and will be removed from Debian.  The replacement for jade is openjade
but it is not necessary to have that as an explicit build dependency
because dejagnu build depends on docbook-utils which depends on
openjade. So, just remove the build dependency on jade.

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

Kernel: Linux 4.3.0-1-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)

-- 
Neil Roeth

Bug#840163: RFS: dh-make-elpa/0.6.0

[Sean Whitton]

On Mon, Oct 10, 2016 at 09:21:00PM +0200, Matteo F. Vescovi wrote:
> Il 10 ott 2016 17:45, "Gianfranco Costamagna"  ha
> scritto:
> > AFAIR as long as you don't introduce new binaries, as a DM
> > you can upload a new package on unstable :)
> 
> As far as I can remember, primary condition to this is the already existence 
> of
> a source package for that suite.

I guess I'll just go ahead and try it next time :P

Thanks for the upload!

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#723071: evince: Send To dunction does nothing

[Jason Crain]

Control: tags -1 + moreinfo

On Tue, Sep 13, 2016 at 06:18:31PM +0200, Darshaka Pathirana wrote:
> just wanted to tell you that the problem still exists in Debian/Jessie. But
> this time it does not fail silently but displays a big red banner with "Could
> not send current document" and "Failed to execute child process "(null)" (No
> such file or directory)". See attached screenshot.

Do you have the "nautilus-sendto" program installed?

Bug#840374: binutils-arm-linux-gnueabi: ld.bfd segfaults when attempting to include binary blob

[Peter Chubb]

Package: binutils-arm-linux-gnueabi
Version: 2.27-8
Severity: normal

Dear Maintainer,
My build system uses LD with a linker script to include a binary blob
in an elf file.  arm-linux-gnueabi-ld.bfd segfaults, but
arm-linux-gnueabi-ld.gold works correctly.

To reproduce:
  dd if=/dev/zero of=blob bs=1k count=1

  cat  > linkscript.ld <

-- no debconf information

Bug#840117: DVB: Made crash sometimes.

[K.Ohta]

Dear Rizzolo-san,
Perhaps you missed a control word?
Please regards,
Ohta.

On Sat, 8 Oct 2016 12:10:03 +
Mattia Rizzolo  wrote:

> control: reassing -1 src:linux 4.7.5-1
> 
> On Sat, Oct 08, 2016 at 08:58:16PM +0900, Kyuma Ohta wrote:
> > Package: linux-image-4.7
> > Severity: important
> > 
> > Dear maintainer,
> > Since kernel linux-4.7, sometimes dvb module has crashed, need to
> > reboot.
> > 
> > Below is kernel log.
> > Best regards,
> > Ohta.
> > 
> > Oct  8 04:12:10 hogefuga kernel: [128981.050249] BUG: unable to
> > handle kernel NULL pointer dereference at (null) Oct  8 04:12:10
> > hogefuga kernel: [128981.050301] IP: []
> > exit_creds+0x1b/0x50 Oct  8 04:12:10 hogefuga kernel:
> > [128981.050335] PGD 417318067 PUD 4248a3067 PMD 0 Oct  8 04:12:10
> > hogefuga kernel: [128981.050364] Oops: 0002 [#1] SMP Oct  8
> > 04:12:10 hogefuga kernel: [128981.050383] Modules linked in:
> > nls_utf8(E) isofs(E) udf(E) pci_stub(E) vboxpci(OE) vboxnetadp(OE)
> > vboxnetflt(OE) vboxdrv (OE) snd_hrtimer(E) snd_seq(E)
> > cpufreq_conservative(E) cpufreq_stats(E) cpufreq_userspace(E)
> > cpufreq_powersave(E) binfmt_misc(E) nls_ascii(E) nls_cp437(E) vf
> > at(E) fat(E) jfs(E) xfs(E) sr_mod(E) cdrom(E) mxm_wmi(E)
> > ata_generic(E) uas(E) pl2303(E) joydev(E) usbserial(E) kvm_amd(E)
> > kvm(E) irqbypass(E) efi_pstore(E)  efivars(E) crct10dif_pclmul(E)
> > crc32_pclmul(E) ghash_clmulni_intel(E) amdkfd(E) radeon(E)
> > k10temp(E) psmouse(E) serio_raw(E) mxl301rf(E) qm1d1c0042(E) fam15h
> > _power(E) tc90522(E) snd_hda_codec_realtek(E)
> > snd_hda_codec_generic(E) snd_hda_codec_hdmi(E) earth_pt3(E)
> > snd_hda_intel(E) firewire_ohci(E) firewire_core(E)  crc_itu_t(E)
> > sg(E) dvb_core(E) ttm(E) snd_hda_codec(E) pata_via(E)
> > drm_kms_helper(E) fjes(E) sp5100_tco(E) drm(E) i2c_algo_bit(E)
> > snd_hda_core(E) wmi(E) floppy(E) pata_atiixp(E) button(E)
> > i2c_piix4(E) acpi_cpufreq(E) tpm_tis(E) tpm(E) cuse(E) fuse(E)
> > w83627ehf(E) hwmon_vid(E) tg3(E) ptp(E)pps_core(E) libphy(E)
> > snd_usb_audio(E) snd_usbmidi_lib(E) snd_hwdep(E) snd_rawmidi(E)
> > snd_seq_device(E) snd_dummy(E) snd_pcm(E) snd_timer(E) snd(E)
> > soundcore(E) loop(E) parport_pc(E) ppdev(E) lp(E) parport(E)
> > efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) overlay(E) aufs(OE)
> > ext4(E) ecb(E) crc16(E) jbd2(E) mbcache(E) raid10(E) raid456(E)
> > libcrc32c(E) crc32c_generic(E) async_raid6_recov(E) async_memcpy(E)
> > async_pq(E) async_xor(E) xor(E) async_tx(E) raid6_pq(E) raid1(E)
> > raid0(E) multipath(E) linear(E) md_mod(E) zsmalloc(E) deflate(E)
> > lz4hc(E) lz4hc_compress(E) lz4(E) lz4_compress(E) evdev(E)
> > hid_generic(E) usbhid(E) hid(E) sd_mod(E) usb_storage(E)
> > crc32c_intel(E) ohci_pci(E) aesni_intel(E) aes_x86_64(E)
> > glue_helper(E) lrw(E) gf128mul(E) ablk_helper(E) cryptd(E) ahci(E)
> > libahci(E) xhci_pci(E) libata(E) ohci_hcd(E) ehci_pci(E)
> > xhci_hcd(E) ehci_hcd(E) usbcore(E) scsi_mod(E) usb_common(E)
> > shpchp(E) Oct  8 04:12:10 hogefuga kernel: [128981.051446] CPU: 7
> > PID: 21681 Comm: fuse_b25 Tainted: G   OE   4.7.0-1-amd64
> > #1 Debian 4.7.5-1 Oct  8 04:12:10 hogefuga kernel: [128981.051491]
> > Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./990FX
> > Extreme4, BIOS P2.70 06/05/2014 Oct  8 04:12:10 hogefuga kernel:
> > [128981.051540] task: 8802c94c6140 ti: 88015c12
> > task.ti: 88015c12 Oct  8 04:12:10 hogefuga kernel:
> > [128981.051577] RIP: 0010:[]
> > [] exit_creds+0x1b/0x50 Oct  8 04:12:10 hogefuga
> > kernel: [128981.051620] RSP: 0018:88015c123cd0  EFLAGS:
> > 00010246 Oct  8 04:12:10 hogefuga kernel: [128981.051647] RAX:
> > 9da94da8 RBX: 880418335080 RCX:  Oct  8
> > 04:12:10 hogefuga kernel: [128981.051682] RDX: 9da94dc0
> > RSI: 880418335080 RDI:  Oct  8 04:12:10
> > hogefuga kernel: [128981.051717] RBP: 880418335080 R08:
> > 8804158c7300 R09: 0040 Oct  8 04:12:10 hogefuga
> > kernel: [128981.051753] R10: 8804158c7338 R11: 8804295cb0c0
> > R12: fffc Oct  8 04:12:10 hogefuga kernel:
> > [128981.051788] R13: 88042289b328 R14: 88042289b378 R15:
> >  Oct  8 04:12:10 hogefuga kernel: [128981.051824]
> > FS: 7f25c5d4e700() GS:88043edc()
> > knlGS: Oct  8 04:12:10 hogefuga kernel:
> > [128981.051864] CS:  0010 DS:  ES:  CR0: 80050033
> > Oct  8 04:12:10 hogefuga kernel: [128981.051909] CR2:
> >  CR3: 00041b6ec000 CR4: 000406e0 Oct  8
> > 04:12:10 hogefuga kernel: [128981.051944] Stack: Oct  8 04:12:10
> > hogefuga kernel: [128981.051956]  880418335080 9d0771d5
> >  880418335080 Oct  8 04:12:10 hogefuga kernel:
> > [128981.051999]  9d098d20 88042289b350 c900025d4198
> > 88042289b3f8 Oct  8 04:12:10 hogefuga kernel: [128981.052041]
> > c089b06c c900026ee130 c900026ee130 88042289b3f8

Bug#830399: python-jedi: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Legimet]

This is blocking vim-youcompleteme from reaching testing.
I think python-pytest would have to be added as a build dependency.

Bug#840373: Instructions are wrong for MP3 conversion

[Akkana Peck]

Package: soundconverter
Version: 3.0.0~alpha1+git20151209-1
Severity: normal

soundconverter -b -m "audio/mpeg" -s ".mp3" stopped working for me,
saying:
"lamemp3enc" gstreamer element not found, disabling MP3 output.

The problem turned out to be that although I had
gstreamer0.10-plugins-ugly installed (as the instructions on
http://soundconverter.org/gstreamer-mp3-encoding-howto/ ,
pointed to by the link in soundconverter's Preferences window,
recommend) what it actually needs now is gstreamer1.0-plugins-ugly.

The instructions also say to add the deb-multimedia repository to
apt sources; but even after I did that,
apt-cache policy gstreamer1.0-plugins-ugly
says it's coming from
500 http://ftp.us.debian.org/debian testing/main i386 Packages
and doesn't say anything about deb-multimedia. So I think that
part must be wrong too.

I know the page is part of the upstream project, but I'm hesitant to
be the one to tell them to change it in case there are other
versions of Debian for which it's right. Maybe they need to specify
different instructions for different Debian versions?


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

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

Versions of packages soundconverter depends on:
ii  gir1.2-gconf-2.0   3.2.6-3
ii  gir1.2-glib-2.01.50.0-1
ii  gir1.2-gstreamer-1.0   1.8.3-1
ii  gir1.2-gtk-3.0 3.22.1-1
ii  gstreamer1.0-plugins-base  1.8.3-1
ii  gstreamer1.0-plugins-good  1.8.3-1+b1
ii  python3-gi 3.22.0-1
pn  python3:any

Versions of packages soundconverter recommends:
ii  gir1.2-notify-0.7   0.7.6-2
pn  gstreamer1.0-libav  

Versions of packages soundconverter suggests:
pn  gstreamer1.0-plugins-ugly  

-- no debconf information

Bug#835360: rkt: FTBFS on several architectures

[Dmitry Smirnov]

On Saturday, 8 October 2016 10:56:05 PM AEDT Andreas Henriksson wrote:
> Is there anything holding back uploading a new version (which should
> resolve the issues)?

Unfortunately rkt is held by "golang-github-appc-spec" 0.8.7 which FTBFS due 
to sub-vendored "go4.org/errorutil". At the moment I do not know how to 
address this problem...


> Please note that the freeze is approaching quickly so
> if you'd like to see the package shipped in stretch it needs to happen
> very soon.

Currently I work at 100% of my capacity and I don't have any hidden reserves 
to activate. Freeze or not I'm doing my best even though right now this issue 
is not my top priority while I'm swamped with other things...


> If you need any help, tell me!

I'd appreciate any help. Thank you.

-- 
All the best,
 Dmitry Smirnov.

---

A man does what he must - in spite of personal consequences, in spite of
obstacles and dangers and pressures - and that is the basis of all human
morality.
-- Winston Churchill


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

Bug#840372: debootstrap: second-stage fails within systemd-nspawn: proc already mounted

[linus . luessing]

Package: debootstrap
Version: 1.0.81~bpo8+1
Severity: normal

Dear Maintainer,

I'm currently trying to first debootstrap with --foreign
("$ sudo debootstrap --foreign sid ./"). And then I'm trying to perform the 
second stage
with qemu-user-static + systemd-nspawn, which fails, unfortunately:


$ sudo systemd-nspawn --bind /usr/bin/qemu-x86_64-static -D ./ 
/debootstrap/debootstrap --second-stage
Spawning container amd64 on /srv/nfs/debian-sid-test/.amd64.
Press ^] three times within 1s to kill container.
/etc/localtime is not a symlink, not updating container timezone.
I: Keyring file not available at 
/usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror 
https://mirrors.kernel.org/debian
W: Failure trying to run:  mount -t proc proc /proc
W: See //debootstrap/debootstrap.log for details
~

The following workaround helps though:


$ sudo systemd-nspawn --bind /usr/bin/qemu-x86_64-static -D "./.amd64/" 
/bin/bash -c "mkdir /tmp/proc; mount --move /proc /tmp/proc; 
/debootstrap/debootstrap --second-stage"


So it looks like systemd-nspawn already took care of mounting /proc and
debootstrap fails when trying to do the same? Maybe debootstrap could
just skip mounting /proc if this mount is already present?

Regards, Linus


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

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

Versions of packages debootstrap depends on:
ii  wget  1.16-1+deb8u1

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.18-7+deb8u3

debootstrap suggests no packages.

-- no debconf information

Bug#839718: chef: Missing dependency on lsb-base

[Christian Hofstaedtler]

Control: tags -1 + pending

* Santiago Vila  [161011 02:05]:
> --- a/debian/control
> +++ b/debian/control
> @@ -51,6 +51,7 @@ Package: chef
>  Architecture: all
>  X-DhRuby-Root: .
>  Depends: chef-zero (>= 4.5),
> + lsb-base,

Fixed in git, thanks.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#468147: Re: Bug#468147: Check for correct lsb-base dependency for init script functions

[Christian Hofstaedtler]

* Santiago Vila  [161011 01:35]:
> As of today, lsb-base is "less essential" than before, because
> util-linux no longer depends on it in stretch.
> 
> Also, if I'm not mistaken, lsb-base is a shell library to be used by
> init.d scripts, but those scripts are obsoleted by systemd.

They are obsolete when replaced by systemd native service files, AND
we are no longer bound to support non-systemd init systems. (Maybe I
have missed a change to that?)

As long as this is not the case, all packages that ship a daemon will
have to depend on lsb-base, or reimplement the log_* functions PLUS the
systemctl redirect logic.

It could have been argued that init-system-helpers ("helper tools
for all init systems") should depend on lsb-base...

How does this change improve the situation, when it is implicitly
forbidden for a system to have lsb-base missing?

Puzzled,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#840371: ITP: git-repo -- CLI utility to manage git services from your workspace

[陳昌倬]

Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)" 

* Package name: git-repo
  Version : 1.7.2
  Upstream Author : Bernard `Guyzmo` Pratz
* URL : https://github.com/guyzmo/git-repo
* License : GPLv2+
  Programming Lang: Python
  Description : CLI utility to manage git services from your workspace

 git-repo is a CLI tool to manage git services likes GitHub, GitLab, and
 Bitbucket. It provides several commands to handle clone, gist, pull
 request.

-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D
  BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#840370: gstreamer1.0: Please remove build dependency on jade

[Neil Roeth]

Source: gstreamer1.0
Severity: normal

The gstreamer1.0 package build depends on jade which is obsolete and
will be removed from Debian. The replacement for jade is openjade, but
that is already an indirect dependency via docbook-utils (which
gstreamer1.0 also build depends upon), so the build dependency on jade
can simply be removed.

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

Kernel: Linux 4.3.0-1-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)

-- 
Neil Roeth

Bug#826636: This bug is NOT fixed in 1.16.0-1

[Laszlo KERTESZ]

This bug is NOT fixed in 1.16.0-1.
On my 2 computers running Debian Testing/Stretch (one has Intel Skylake
graphics, the other AMD radeon/r600g) this bug actually started to manifest
with 1.16.0-1.

Bug#840369: libgnome-autoar-0-0: should have versioned dependency on libarchive13 v3.2+

[Mohammed Sadiq]

Package: libgnome-autoar-0-0
Version: 0.1.1-4
Severity: important
Tags: newcomer

Dear Maintainer,

 libgnome-autoar require libarchive13 version 3.2+
to function. Else applications using autoar may segfault
(Eg: Nautilus)

As gnome-autoar doesn't have a versioned dependency on libarchive13,
an update from Jessie to Stretch may break Nautilus and other applications.

See bug reported upstream[0].


[0] https://bugzilla.gnome.org/show_bug.cgi?id=771803


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

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

Versions of packages libgnome-autoar-0-0 depends on:
ii  libarchive133.2.1-2
ii  libc6   2.24-3
ii  libglib2.0-02.50.0-2
ii  libgnome-autoar-common  0.1.1-4

libgnome-autoar-0-0 recommends no packages.

libgnome-autoar-0-0 suggests no packages.

-- no debconf information

Bug#840356: initscripts: mountkernfs.sh does not mount configfs

[Ian Jackson]

Christophe Vu-Brugier writes ("Bug#840356: initscripts: mountkernfs.sh does not 
mount configfs"):
> Dear Maintainer,

Hi.  FYI, I'm not the maintainer.  But I am interested in sysvinit in
general.

> Maybe we could cut the configfs section from mountkernfs.sh and put it
> in a separate mountconfigfs.sh init script that would start after kmod?

This would be a possibility.  But TBH maybe it would be better to load
kernel modules before trying to mount the kernel filesystems.  I'm not
sure what dependencies there might be in the other direction.  Can
anyone advise ?  I guess maybe modprobe depends on /proc.

Sorry to be vague, but I'm replying to this late at night and not
entirely sober :-).

Thanks,
Ian.

-- 
Ian Jackson    These opinions are my own.

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

Bug#817521: libapache-mod-removeip: Removal of debhelper compat 4

[intrigeri]

Control: tag -1 + patch

ni...@thykier.net:
> The package libapache-mod-removeip uses debhelper with a compat level of 4,
> which is deprecated and scheduled for removal.

I've imported this package's history into a gbp repository using:

  gbp import-dscs --debsnap libapache-mod-removeip   

… and then bumped the compat level to 8 (not 9+ since I did not feel
like dealing with multiarch today). The resulting binary package
is very similar to the one we have in sid currently, according to
debdiff on the main .deb:

  File lists identical (after any substitutions)

  Control files: lines which differ (wdiff format)
  
  Depends: libc6 (>= 2.2.5), [-apache2-api-20120211-] {+apache2-api-20120211, 
apache2-bin (>= 2.4.16)+}
  Installed-Size: [-71-] {+42+}
  Version: [-1.0b-5.1-] {+1.0b-6~1.gbpfff84f+}

I've pushed the result to collab-maint:

  ssh://git.debian.org/git/collab-maint/libapache-mod-removeip.git

… and added Vcs-* control fields.

Hoping it helps :)

I did not actually _test_ the resulting package though, so I realize
I'm a bit bold tagging this patch, but oh well.

Cheers,
-- 
intrigeri

Bug#840368: gnome-software: should depend on software-properties-gtk

[Mohammed Sadiq]

Package: gnome-software
Version: 3.22.0-1
Severity: important
Tags: newcomer

Dear Maintainer,

The Software sources window (in Application menu) doesn't work when
software-properties-gtk isn't installed. A blank window is shown
instead.

Installing software-properties-gtk fixes this bug. So gnome-software
should depend on software-properties-gtk.

As this feature is expected by any user, bumping the severity to important.

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

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

Versions of packages gnome-software depends on:
ii  appstream0.10.1-2
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  gnome-software-common3.22.0-1
ii  gsettings-desktop-schemas3.22.0-1
ii  libappstream-glib8   0.6.2-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-3
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libenchant1c2a   1.6.0-11+b1
ii  libfwupd10.7.3-1
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.0-2
ii  libgnome-desktop-3-123.22.0-1
ii  libgtk-3-0   3.22.1-1
ii  libgtkspell3-3-0 3.0.9-1
ii  libgudev-1.0-0   230-3
ii  libjson-glib-1.0-0   1.2.2-1
ii  libpackagekit-glib2-18   1.1.4-1
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpolkit-gobject-1-00.105-16
ii  libsecret-1-00.18.5-2
ii  libsoup2.4-1 2.56.0-1
ii  libsqlite3-0 3.14.2-1
ii  packagekit   1.1.4-1

gnome-software recommends no packages.

Versions of packages gnome-software suggests:
pn  fwupd  
pn  gnome-software-plugin-flatpak  
pn  gnome-software-plugin-limba

-- no debconf information

Bug#840312: [pkg-gnupg-maint] Bug#840312: scdaemon: Add udev rule for Fujitsu Siemens smart card reader?

[NIIBE Yutaka]

On 10/10/2016 10:11 PM, Petter Reinholdtsen wrote:
> Hi.  I got a smart card reader from Fujitsu Siemens that is not
> recognized by scdaemon.  Perhaps it should be added to the udev rules.d
> file?

Thanks for the report.  If it works well, it should be added.

> Perhaps it is better to try to recognize all USB smart card readers
> using the bus class instead of trying to list the IDs of all card
> readers that exist?

Yes, it is possible for udev to match USB class.  I'm not sure if
it's better to do so.

Please note that smartcard reader products and the standard of CCID
are not that good, unfortunately.

My experience says: Most card readers don't work with OpenPGP card by
scdaemon, only some card readers work well.

Major problem is that people use larger key (RSA-2048 or RSA-4096)
with OpenPGP card.  This is considered "huge" for the technology
around smartcard.
-- 

Bug#814935: [kcollectd] Resizing Issue

[Antonio Russo]

I'd like to point out that the patch submitted for this bug has been tested for 
the last 8 months on my machine, and still applies cleanly.

Bug#840367: calcurse: New version upstream: 4.2.0

[John Eikenberry]

Package: calcurse
Version: 3.1.4-2
Severity: wishlist

Calcure 4.2.0 is available and needed for CalDAV support. Please update the
package when you get a chance. Preferably before the freeze. Thanks.

http://calcurse.org/downloads/

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

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

Versions of packages calcurse depends on:
ii  libc6 2.19-18+deb8u6
ii  libncursesw5  5.9+20140913-1+b1
ii  libtinfo5 5.9+20140913-1+b1

calcurse recommends no packages.

calcurse suggests no packages.

-- no debconf information

Bug#840366: RFP: libsignal-protocol-c -- ratcheting forward secrecy protocol for synchronous and asynchronous messaging

[W. Martin Borgert]

Package: wnpp
Severity: wishlist
Owner: "W. Martin Borgert" 

* Package name: libsignal-protocol-c
  Version : None, 2016-10-05
  Upstream Author : Moxie Marlinspike and others
* URL : https://github.com/WhisperSystems/libsignal-protocol-c
* License : GPL3
  Programming Lang: C
  Description : ratcheting forward secrecy protocol for synchronous and 
asynchronous messaging

This is a ratcheting forward secrecy protocol that works in
synchronous and asynchronous messaging environments.

This will be needed for implementing OMEMO in C, e.g. in
libpurple/pidgin.

Bug#827335: evince: assertion failed: (wayland_display->cursor_theme_name)

[Jason Crain]

On Tue, Jun 14, 2016 at 06:58:06PM -0700, Diane Trout wrote:
> I launched evince running under wayland from gnome terminal and it immediately
> crashed with an
> assertion failed.
> 
> (evince:4492): Gtk-WARNING **: Theme parsing error: :56:20: The 
> 'gtk-key-
> bindings' property has been renamed to '-gtk-key-bindings'
> [New Thread 0x7f50825f6700 (LWP 4500)]
> **
> Gdk:ERROR:/build/gtk+3.0-UYMeaD/gtk+3.0-3.20.6/./gdk/wayland/gdkdisplay-
> wayland.c:827:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed:
> (wayland_display->cursor_theme_name)
> 
> Program received signal SIGABRT, Aborted.

I haven't been able to reproduce this.  Do you still see this problem
under more recent versions of gtk and evince?  Do you have some cursor
theme enabled and does the problem stop if you disable the cursor theme?
Does it only happen under wayland and not xorg?

Bug#840365: 1:45.4.0-1 broke the External Editor plugin

[Craig Sanders]

Package: icedove
Version: 1:45.4.0-1

The External Editor plugin (from http://globs.org/articles.php?lng=en=2)
was working in icedove up until this upgrade, stopped working immediately
after.

Everything looks OK until you select "Edit in External Editor" from the Tools
menu, and then nothing happens - no gvim as expected.

craig

--
craig sanders 

Bug#840328: evince: Evince does not received correct keystroke under Wayland

[Jason Crain]

Control: tags -1 + moreinfo

On Mon, Oct 10, 2016 at 06:25:12PM +0200, Bruno BEAUFILS wrote:
> I use evince under gnome which runs on top of XWayland on stretch.
> 
> My laptop keyboard has a physicial UK layout.
> 
> I configured the keyboard through Gnome Control Center to use another layout
> (french one).
> 
> In any applications (or at least all the one I used so far) when I type the
> physical Q key, the application receive the A keystroke as expected.
> 
> It is not the case in evince (and as far as I know for now) only in evince:
> when I press the physical Q key, it receives the Q keystroke without respect 
> of
> any keyboard settings layout.
> 
> I am unsure where to report this bug (Xwayland, Gnome or Evince) but since I 
> am
> able to reproduce that bug only with evince so far, I try here.

I haven't been able to reproduce the behavior you describe.  Evince is
following the input sources the same as any other gnome app.  Here's
what I've tried:

1. Go into the gnome settings menu for region & language.
2. Add a new input source.  I picked French, so now I have two sources,
   English (US) and French.
3. An input source selecter widget appears in the gnome top bar showing
   "en" as my current input source.
4. I test this in gedit.
a. Type a few q's in gedit and see q's are entered.
b. Use the widget to switch to "fr" input source.
c. Type a few q's in gedit and see a's are entered.
d. Use widget to switch back to "en".
5. Test this in evince.  Open some random PDF.  Push the search button
   so I can see what I'm typing.
a. Same as above, type q's and see q's are entered in the search
   bar.
b. Use the widget to switch to "fr".
c. Type some q's and see a's are entered in the search bar.

Bug#840254: [Pkg-xfce-devel] Bug#840254: thunar: freeze when mounting USB drive

[Ben Caradoc-Davies]

On 11/10/16 09:39, Ben Caradoc-Davies wrote:

Only once during testing, 1.6.10-3 appeared to start working correctly
for all drives. This behaviour did not survive a reboot. Mounting with
1.6.10-2 is always successful.


Failures only start after reboot! Upgrading to 1.6.10-3 appears to work, 
even after all old thunar instances are closed/killed and restarted to 
ensure fresh binaries are in use. After a reboot, freeze on mounting 
happens every time with 1.6.10-3.


(I was testing again to see if recent udev and gvfs changes had any 
effect; they did not.)


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#839433: Pending fixes for bugs in the golang-github-robfig-cron package

[pkg-go-maintainers]

tag 839433 + pending
thanks

Some bugs in the golang-github-robfig-cron package are closed in
revision f45500ef3c541934dcd7ccaf38e4e1b12062cf1a in branch 'master'
by Liang Yan

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-robfig-cron.git/commit/?id=f45500e

Commit message:

Add tzdata into build-depends (Closes: #839433).

Bug#840056: shibboleth-sp2-utils: upgrade attempt of shibboleth-sp2-utils gets hung at restart of shibd service

[S. Banerian]

On 10/10/2016 02:03 PM, S. Banerian wrote:
> On 10/09/2016 05:25 PM, Ferenc Wágner wrote:
> Does shibd still consume significant CPU according to top?
> 
> at this moment, no.
>> What are its memory figures?
> 
> nothing big.
> 
>> Isn't your computer swapping heavily?
> 
> no

with the attempt to perform
systemctl restart shibd.service
I'm now seeing the CPU at 100% and memory (but not yet swap) near 100% also.
and no  shibd.sock.

web app error message:

shibsp::ListenerException

The system encountered an error at Mon Oct 10 14:06:15 2016
To report this problem, please contact the site administrator at ...

Please include the following message in any email:

shibsp::ListenerException at ...

Cannot connect to shibd process, a site administrator should be notified
that this web server has malfunctioned.


rebooting machine gave same result.  I'll let it sit overnight to see
what happens.


-- 
Stefani Banerian
UW Clinical Cyclotron www.uwmcf.org
UW School of Medicine
UW Box 356043
206-598-0302
gpg key 6642E7EE
fingerprint = BD13 875D 2D03 5E1D 1E3B  8BF7 F4B8 63AD 6642 E7EE

Bug#839417: Pending fixes for bugs in the golang-github-jinzhu-now package

[pkg-go-maintainers]

tag 839417 + pending
thanks

Some bugs in the golang-github-jinzhu-now package are closed in
revision 447d67509774953058929410a69179f53e135620 in branch 'master'
by Liang Yan

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-jinzhu-now.git/commit/?id=447d675

Commit message:

Add tzdata into build-depends (Closes: #839417).

Bug#840364: kannel: Please remove build dependency on jade

[Neil Roeth]

Source: kannel
Severity: normal

The kannel package build depends on jade, which is obsolete and will be
removed from Debian.  The replacement for jade is openjade.  However,
kannel does not need to build depend on openjade because the
docbook-dsssl package (also a build dependency of kannel) depends on
openjade.  So, jade can simply be removed from the build dependencies.

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

Kernel: Linux 4.3.0-1-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)

-- 
Neil Roeth

Bug#832116: edgar: Source missing for some GPL licensed assets

[Markus Koschany]

On 10.10.2016 23:54, Francesco Poli wrote:
[...]
> So in conclusion, I am still convinced that the Debian Project must
> distribute the source (for works included in packages in Debian main)
> anyway, regardless of how permissive is the license.

I have commented on this bug report because I feel that both you and the
original bug reporter don't represent all of Debian (you are not even a
Debian developer but you act like one on debian-legal) and I dispute the
severity of this bug report.

You said:
DFSG#2 requires the availability of source code.

That is correct. But an ogg file is not a program. We are not required
to ship a "source" for it, especially if we don't know how the actually
source format looks like. There are many authors and content providers
who license their artwork under the GPL but they don't release some
other (higher) form of this artwork. Granted, the GPL is a poor choice
for licensing artwork but it does not make it unsuitable for Debian if
the original author decides to provide her artwork in a lossy data format.

Coming back to the actual issue at hand: If files have been wrongly
credited, then this issue should be fixed. However there is no
requirement to provide some kind of "source" if it doesn't exist. If
there is some kind of "source" that still exists for the GPL licensed
files, please include it in the source tarball (because it would be the
easiest solution for this bug report). If this situation is impossible
to resolve, please get in touch with me again (@maintainer).

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#840363: git-hub: man page lies about implicit issues list command

[Dominik George]

Package: git-hub
Version: 0.10.2-1
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The man page says:

   issue  This  command is used to manage GitHub issues through a set of 
subcommands.  Is
  no subcommand is specified, list is used.

This is not true:

% git hub issue
usage: git-hub issue [-h] {close,comment,list,new,show,update} ...
git-hub issue: error: too few arguments

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

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

Versions of packages git-hub depends on:
ii  git 1:2.9.3-1
ii  python  2.7.11-2

git-hub recommends no packages.

git-hub suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJhBAEBCABLBQJX/BgXMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MSHG5pa0BuYXR1cmFsbmV0LmRlAAoJELeaPBagxPKW
qTUQAIaWbWr58ML6YvwT3ZC7xIjHfnRyln/8sRbC0a7lLIDWKacFmTn0Ht1AUy+y
8RIu63rfKXFI02CSYt2B9W/seo1BCEtIQFkcZGUKnqZKKzDF3kII5aRze4vFrNSu
kEIg3vsA4SOmDOxbvlMc6gJnZyP8oKd2tE1wlUnawU83jwhE8lx1dA1rukaxsEST
kD3cLQMZWjV+1BHFFzZPfeor81YXGI3OrBOFMRJr9kY848x2GM4JVH8OAAQ3NxVm
iSMiECZf0mdQC/T6uubI+ExxtUk+Ykbo9F1Z1RrqYiXF6lAmSevyBvICm0AsnTuy
pmH5uivsNYupxdLW/prmAykCD+ux7usCS6mlTMqZOcDi82oUueWSAsHEo2ghDkaz
EtAkaZ2ThIJmUePyipO2NL1MsxNK/EJ4hFjExTXYCrEU/aB5MzQO3syl1X0mPNNS
yq1w87nCYzqox8Ospgwsj6cpB9yWd32CMtDTr6K1z6df2qCxHajtCs69pt2qaZJ2
pKDURSvmtC/gWcotEjnIeOAZcBuffsoTQ2Y6Bn7ENlUy1lrnWbvEFu3YBwM5eSUe
MOpYSAT9HMYm0WprhR2A6kGNkb2KEM8t8Hss78o3dl7xU0hssK5gzQUcguw1obec
i2KYB1WiBAvLzH/9UBkxZUAvrEwmA8tdqcOI3MJbyAxSvpbe
=uWjZ
-END PGP SIGNATURE-

Bug#840141: kwin-x11: Short freeze when showing multiple tray notifications

[Alex Dănilă]

Hola!

I believe this is rather and interaction between KWin and Plasmashell. 
If I stopped the Plasmashell process, the freeze doesn't happen anymore 
(those notifications are drawn at the top of the screen in small 
windows). A further argument for this idea is that after the freeze the 
screen goes one "frame" back, and that the music and cursor are not 
affected.


I'll note that after restarting Plasmashell this doesn't happen as 
reliably as before.


However, if you know a good way of triggering this kind of 
notifications, it will be my pleasure to do it.


Thank you,
Alex

On 10/10/16 13:14, Maximiliano Curia wrote:

¡Hola Alex!

El 2016-10-08 a las 22:32 +0300, Alex Dănilă escribió:

Package: kwin-x11 Version: 4:5.7.4-1 Severity: normal


The entire screens freeze for a couple of seconds (3-4, but sometimes 
seemed close to 10) everytime notifications from the tray are about 
to scroll down or disappear. This only affects drawing of screen 
content, it doesn't affect sound or cursor motion.


If relevant, the particular tray notifications are about bluetooth 
devices, I'll attach a screenshot with this. The particular order is 
like this:
-two messages (M1 - connection deactivated, M2 - connection timed 
out) appear one above the other -2-3 seconds pass -freeze -2 -freeze 
ends -M1 disappears, M2 animates going down -messages reappear and 
animate again, but without freezes.


I'll send a screenshot after the bug is created, and if possible a 
recording.


As reported it seems that the issue is bluetooth specific, and it 
might be caused by an underlying issue of the bluetooth kernel module 
or hardware device. In my limited tests I couldn't reproduce this 
behaviour in my laptop.


Would it be feasible for you to test this multiple bluetooth 
notifications in a different desktop environment in order to rule out 
a kernel/hardware issue?


Can you reproduce this triggering a different type of notifications?

Happy hacking,

Bug#836942: transition: glew

[Emilio Pozuelo Monfort]

tags 836942 pending
thanks

Bug#838234: transition: readline/readline6

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 03/10/16 00:10, Emilio Pozuelo Monfort wrote:
> Control: forwarded -1 
> https://release.debian.org/transitions/html/readline7.html
> 
> Hi,
> 
> On 18/09/16 20:43, Matthias Klose wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: transition
>>
>> readline 7.0 is now released, changing the soversion. The idea is to upload 
>> the
>> readline package from experimental (plus providing the libreadline*6-dev
>> packages), and stop building the -dev packages and common packages from
>> readline6.  Afaics, the API didn't change; for rebuild tests I only see build
>> failures for unrelated reasons.  readline and readline6 can stay in testing 
>> for
>> some time, but readline6 should be removed from testing before the stretch 
>> release.
>>
>> I haven't done a test rebuild on unstable, but building on Ubuntu yakkety. 
>> The
>> current state of the transition can be seen at
>> http://people.canonical.com/~ubuntu-archive/transitions/html/readline.html
> 
> Sounds good. I'd prefer to see a test rebuild on sid, but I think we could go
> ahead with this as it's a separate source and shouldn't block anything.

readline 6 got decrufted. Rebuilds scheduled.

Cheers,
Emilio

Bug#840345: firefox-esr: update packaged add-ons automatically

[Mike Hommey]

On Mon, Oct 10, 2016 at 07:02:58PM +, att200...@yahoo.it wrote:
> Subject: firefox-esr: update packaged add-ons automatically
> Package: firefox-esr
> Version: 45.4.0esr-1~deb8u2
> Severity: wishlist
> 
> Dear Maintainer,
> 
> After the transition from Iceweasel to Firefox-ESR, the browser is now 
> configured to update add-ons automatically.

There were no changes in the default settings for that.

Mike

Bug#840362: gmpc segfaults on mpd-server timeout

[Alex]

Package: gmpc
Severity: important

Dear Maintainer,
gmpc segfaults, when the mpd server "hangs" for a longer time. An
example if the mopidy server, which provides a mpd interfaces and
sometimes hangs for quite a long time, i.e while loading a spotify
playlist. gmpc hangs the whole time (GUI unresponsive) and when the
server hangs long enough, gmpc crashes with a segfault.

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

Kernel: Linux 4.3.0-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#840361: ITP: fonts-pt-astra -- metric-compatible Times New Roman and Arial alternatives

[Andrew Shadura]

Package: wnpp
Severity: wishlist
Owner: Andrew Shadura 

* Package name: fonts-pt-astra
  Version : 20160928
  Upstream Author : ParaType Inc
* URL : http://astralinux.com/fonts.html
http://www.paratype.ru/cinfo/news.asp?NewsId=3469
http://astralinux.com/ofl.html
* License : OFL 1.1
  Description : metric-compatible Times New Roman and Arial alternatives

PT Astra Serif and PT Astra Sans are metric-compatible replacements
for Times New Roman and Arial fonts. PT Astra family of fonts have
been developed by ParaType Inc for AstraLinux distribution.

Bug#840342: [ace-of-penguins] Freecell No Longer Runs, Nvidia Legacy-304xx video driver

[Luca Boccassi]

On Mon, 10 Oct 2016 23:01:27 +0300 David Baron  wrote:
> On ×™×•×  ×©× ×™, 10 ×‘× ×•×§×˜×•×‘×¨ 2016 21:54:58 IDT Markus Koschany wrote:
> > On 10.10.2016 21:28, David Baron wrote:
> > > On ×™×•×  ×©× ×™, 10 ×‘× ×•×§×˜×•×‘×¨ 2016 20:42:25 IDT Markus Koschany 
> > > wrote:
> > >> Control: tags -1 moreinfo
> > >>
> > >> On 10.10.2016 20:34, David Baron wrote:
> > >>> Package: ace-of-penguins
> > >>> Version: 1.5~rc2-1+b1
> > >>> Severity: normal
> > >>>
> > >>> --- Please enter the report below this line. ---
> > >>> After upgrade of the Nvidia Legacy 304xx driver (contrib), Freecell no
> > >>> longer runs:
> > >>> ~$ ace-freecell
> > >>> X Error of failed request:  BadMatch (invalid parameter attributes)
> > >>>
> > >>>   Major opcode of failed request:  73 (X_GetImage)
> > >>>   Serial number of failed request:  25
> > >>>   Current serial number in output stream:  25
> > >>
> > >> [...]
> > >>
> > >> Hello,
> > >>
> > >> what makes you think that this is a bug in ace-of-penguins? Did you try
> > >> to downgrade your Nvidia drivers? What was the outcome? Are you able to
> > >> play the game with the free xserver-xorg-video-nouveau drivers?
> > >>
> > >> Markus
> > >
> > > Program did run using nouveau but nouveau and KDE/Plasma desktop do not
> > > mix. So have not played it using nouveau in recent memory.
> > > It is no longer possible to downgrade to the testing version of the
> > > nvidia.
> > >
> > > If other programs fail with the same error, then the point is well made.
> > > If this is unique here, then something in the ace "backend" might be
> > > examined.
> > The error message indicates a bug or incompatibility between your X
> > environment / X server and the proprietary Nvidia driver. This is a low
> > level error and not related to ace-of-penguins which only requires a 2D
> > capable graphics card. Everything from the past 20 years should work.
> >
> > If the game works with nouveau it is most likely a bug in the non-free
> > driver. Since the source code is closed it is not possible for Debian to
> > work on a fix. The game works flawlessly on my system by the way.
> >
> > Please note that you can download an earlier version of the Nvidia
> > driver from snapshots.debian.org.
> >
> > I am inclined to reassign this issue to
> > xserver-xorg-video-nvidia-legacy-304xx. Please confirm this is the
> > package you are currently using.
> >
> > I am sure the maintainers of xserver-xorg-video-nvidia-legacy-304xx
> > would be interested in your /var/log/Xorg.* log file because it provides
> > a more detailed error report. Please attach this file to the bug report.
> >
> > Regards,
> >
>
> Sounds like the way to go!
> Log file is attached.

Hi,

We'd need a bit more information, could you please rerun reportbug to
attach the full report:

reportbug -N 840342 nvidia-legacy-304xx-driver

Kind regards,
Luca Boccassi

Bug#734365: fixed in freeplayer 20070531+dfsg.1-4

[Vincent Danjean]

Le 10/10/2016 à 23:32, Antoine Musso a écrit :
> The bug still happens in Jessie which is stuck to 20070531+dfsg.1-3
> 
>   * Fix vlc invocation (remove the "--http-charset=ISO-8859-1" option)
> (Closes: #734365)
> 
> Is there a way to pick that patch and release an update for Jessie?

The patch is very small. You can try it by editing (as root) the
/usr/bin/vlc-fbx script and remove the --http-charset=ISO-8859-1
options to the vlc invocation. Please, check this works (I do not
use freeplayer at all myself).
  Perhaps, a backport of the testing version would be better (other
vlc options are fixed)

  Regards,
Vincent

-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main

Bug#688760: iceweasel: please enable upstream crash reporting

[Mike Hommey]

On Mon, Oct 10, 2016 at 05:35:07PM +0200, Julien Cristau wrote:
> On Fri, Oct 7, 2016 at 11:42 PM, Mike Hommey  wrote:
> 
> > Version: firefox/49.0-4
> >
> > On Fri, Oct 07, 2016 at 06:52:03PM +0200, Julien Cristau wrote:
> > > On Fri, Oct 7, 2016 at 5:14 PM, Sylvestre Ledru 
> > > wrote:
> > >
> > > > Not yet. If I understood correctly, the way firefox   compresses the
> > > > symbol is not managed by breakpad.
> > > > My gut feeling is that the final link might fail with an oom.
> > > > Maybe Julien has more
> > > >
> > > Right, AIUI the missing piece is to upload the symbols from our firefox
> > > builds (and related libraries) to https://crash-stats.mozilla.
> > com/symbols/
> > > so crash reports can be properly analyzed.  I'm working on teaching
> > > breakpad about compressed debug symbols to make that easier.
> >
> > Actually, I uploaded the symbols for 49.0-4 manually.
> >
> Nice.  Do you plan on doing that for future uploads as well?

Yes

> Should other packages such as nss/nspr also get symbols uploaded?

Yes

> Are there bits of infrastructure that would make this better / less manual?

I was counting on whatever scripts you come up with ;)


Mike

Bug#768073: LXC team take over ITP?

[Jonathan Dowland]

On Sun, Oct 09, 2016 at 08:17:09PM +0200, Adnan Hodzic wrote:
> Jonathan and everybody else,
> 
> Since I couldn't find my original LXD package source, I started from
> scratch.
> 
> I created new Git repo (pkg-lxc/lxd.git) and pushed initial Debian package
> of LXD 2.4.1 (Yakkety release). Git repo is available on Alioth:
> https://anonscm.debian.org/git/pkg-lxc/lxd.git

Great, thanks!

> Building the package will fail due to missing golang-* deps which ATM are
> missing in Debian. I can't remember if the original list of missing
> dependencies was this long, but this is what we we're currently dealing
> with:

I've updated the list at https://wiki.debian.org/LXD accordingly.
 
> Has pkg-go team been notified of this problem? And are they willing to
> package these for Debian?

I have joined pkg-go and tackled one of the dependencies (with a second
incoming) but I hadn't thought to msg the team with this list, I will do
that too.

Thanks!


signature.asc
Description: Digital signature

Bug#425898: Processed: ultrastar-ng is now performous

[Markus Koschany]

Control: retitle -1 performous: Suggest free songs

On 10.10.2016 23:35, Adrian Bunk wrote:
> On Mon, Oct 10, 2016 at 11:10:56PM +0200, Markus Koschany wrote:
>> On 10.10.2016 22:57, Debian Bug Tracking System wrote:
>>> Processing commands for cont...@bugs.debian.org:
>>>
 reassign 425898 performous
>>> Bug #425898 [ultrastar-ng] ultrastar-ng: please provide some demo songs !
>>> Warning: Unknown package 'ultrastar-ng'
>>> Bug reassigned from package 'ultrastar-ng' to 'performous'.
>>> No longer marked as found in versions ultrastar-ng/0.1.4-2 and 
>>> ultrastar-ng/0.1.4-1.
>>> Ignoring request to alter fixed versions of bug #425898 to the same values 
>>> previously set
 thanks
>>> Stopping processing here.
>>>
>>> Please contact me if you need assistance.
>>
>> Why do you reassign bugs from packages that have been removed from
>> Debian a long time ago?
> 
> The package was renamed, not removed.
> 
> This made reassigning sound more appropriate than blindly closing.

Usually the old package gets removed from Debian and all bug reports are
automatically closed. It is then the responsibility of the maintainer to
reassign the bugs that still apply to the new package. So renaming of a
package also involves removal of an old and introduction of a new package.

>> This issue is already resolved because fretsonfire-songs-muldjord and
>> fretsonfire-songs-sectoid are automatically detected by performous. See
>> also /usr/share/doc/performous/README.Debian that lists all directories
>> in which songs are searched for.
> 
> It might not matter much when Lucas is the submitter, but in general
> it is better when this bug gets closed with "already fixed" than a
> not completely correct "package was removed".
> 
> 
> The reason why I didn't close the bug this way myself actually seems to 
> be a bug in the package:
> 
> performous does not have any relationship (Depends/Recommends/Suggests)
> on these song packages you mention.
> 
> This was the reason why I didn't find them when checking quickly whether 
> the bug was clearly already fixed.
> 
> I'd guess users would also appreciate at least a Suggests of them.

Ok this is certainly doable. However in my opinion you should state this
information in your initial e-mail when you reassign the bug report. It
even makes more sense to file a new bug report against performous in the
first place because the ultrastar-ng package has been removed from
Debian a really long time ago. This would demonstrate that you are
actually interested in the game itself and not just someone who randomly
acts on the BTS.

I think suggesting the songs from fretsonfire would be appropriate in
this case because I can't really say for sure that these songs "would be
found together with this [package] in all but unusual installations". I
have retitled the bug report accordingly.

> cu
> Adrian

Regards,

Markus





signature.asc
Description: OpenPGP digital signature

Bug#598235: regression: synaptic no longer preserves "auto" flag on upgrade

[Nicolas LE CAM]

Package: apt
Version: 1.3.1
Followup-For: Bug #598235

Dear Maintainer,

Confirming bug report with current apt version.
Just did a dist-upgrade with NEW automatically packages installed and they were 
reported as manually installed (by aptitude) afterward.

nlecam@rio:~$ sudo apt dist-upgrade 
[sudo] Mot de passe de nlecam : 
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
Calcul de la mise à jour... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus 
nécessaires :
  gnome-packagekit gnome-packagekit-data gnome-shell-extension-weather
  libasm4-java libefiboot27 libefivar27
Veuillez utiliser « sudo apt autoremove » pour les supprimer.
Les NOUVEAUX paquets suivants seront installés :
  appstream gnome-software gnome-software-common libappstream-glib8
  libappstream4 libefiboot1 libefivar1 libfwupd1 libgcab-1.0-0
Les paquets suivants seront mis à jour :
  apache2-bin apt apt-utils binutils efibootmgr gcc-5-base gir1.2-nmgtk-1.0
  gnome gnome-backgrounds gnome-core gnome-games libapt-inst2.0 libapt-pkg5.0
  libetonyek-0.1-1 libguice-java liblangtag-common liblangtag1
  libnm-gtk-common libnm-gtk0 libnma-common libnma0 libopencv-calib3d2.4v5
  libopencv-contrib2.4v5 libopencv-core2.4v5 libopencv-features2d2.4v5
  libopencv-flann2.4v5 libopencv-highgui2.4-deb0 libopencv-imgproc2.4v5
  libopencv-legacy2.4v5 libopencv-ml2.4v5 libopencv-objdetect2.4v5
  libopencv-video2.4v5 libportaudio2 libreadline6 libslang2
  network-manager-gnome vim vim-common vim-runtime xxd
40 mis à jour, 9 nouvellement installés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 39,9 Mo dans les archives.
Après cette opération, 8 787 ko d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] 
[...]
nlecam@rio:~$ aptitude search '~i !~M'
i   appstream   - Software component metadata management
i   cups- système commun d'impression sous Unix - ge
id  deborphan   - Programme recherchant les paquets inutilis
i   firefox - navigateur internet Firefox de Mozilla
i   firmware-iwlwifi- Binary firmware for Intel Wireless cards  
i   git - système de gestion de versions distribué, 
i   gnome-boxes - Simple GNOME app to access remote or virtu
i   gnome-software  - Software Center for GNOME 
i   gnome-software-common   - Software Center for GNOME (common files)  
i   hdparm  - tune hard disk parameters for high perform
i   intel-microcode - Processor microcode firmware for Intel CPU
i   libappstream-glib8  - bibliothèque GNOME pour accéder aux servic
i   libappstream4   - Library to access AppStream services  
i   libefiboot1 - Library to manage UEFI variables  
i   libefivar1  - Library to manage UEFI variables  
i   libfwupd1   - Firmware update daemon library
i   libgcab-1.0-0   - Microsoft Cabinet file manipulation librar
i   linux-image-4.8.0-rc8-amd64 - Linux 4.8-rc8 for 64-bit PCs (signed) 
i   linux-image-amd64   - Linux for 64-bit PCs (meta-package)   
i   lsof- utilitaire pour lister les fichiers ouvert
i   maven   - Java software project management and compr
i   openjdk-8-jdk-headless  - OpenJDK Development Kit (JDK) (headless)  
i   reportbug   - rapporte les bogues de la distribution Deb
i   rfkill  - tool for enabling and disabling wireless d
i   sudo- fournit des privilèges de super-utilisateu
i   sysfsutils  - sysfs query tool and boot-time setup  
i   task-desktop- environnement de bureau Debian
i   task-french - environnement français
i   task-french-desktop - bureau français   
i   task-laptop - ordinateur portable   
i   vim - Vi IMproved - éditeur vi amélioré 

regards,
Nicolas

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "0";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.7\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.8\.0-rc8-amd64$";
APT::NeverAutoRemove:: 

Bug#832116: edgar: Source missing for some GPL licensed assets

[Francesco Poli]

On Wed, 5 Oct 2016 00:04:16 +0200 Markus Koschany wrote:

> On Sat, 23 Jul 2016 12:19:50 +0200 Francesco Poli
>  wrote:
[...]
> > DFSG#2 requires the availability of source code.
> > 
> > Hence, distributing the source-less files under a license that does not
> > require the availability of source would not solve the issue.
> 
> This is certainly not true for an ogg file which might very well be the
> only available source.

If the ogg file were the only existing form for the work, then it would
also be source form (by the "preferred form for making modifications"
definition of source, which is the definition found in the GNU GPL) and
nobody would have been worried about it being GPL-licensed and
distributed without making some other form available.

In other words, we are not talking about a case where the ogg file is
the only existing form.

> 
> > 
> > The Debian Project must distribute the source (for works included in
> > packages in Debian main) anyway, regardless of how permissive is the
> > license.
> 
> This is quoted out of context. If game assets like music or images are
> shipped under a permissive license, then there is no requirement to ship
> some hypothetical "source" as well. There are a lot of artists who reuse
> png, bmp, ogg or other media as their primary source material.
> 
> See https://wiki.debian.org/Games/Source for a collection of quotes
> regarding this topic,

This is a collection of diverse opinions on this topic: it seems that
Bas Wijnen and Paul Wise agree with me, while others (including you)
disagree with me.

> especially the thread on debian-devel and posts like
> 
> https://lists.debian.org/debian-devel/2014/03/msg00293.html

Steve Langasek has expressed opinions like this multiple times, but I
am not convinced at all by them.
If you follow the thread, you can clearly see that Paul Wise disagrees
strongly with Steve Langasek:

https://lists.debian.org/debian-devel/2014/03/msg00295.html
https://lists.debian.org/debian-devel/2014/03/msg00298.html

[...]
> > What I expressed is my own opinion on the topic, but it is shared by a
> > good number of other people.
> > I hope I explained things clearly enough.
> > 
> > Please address this issue in a proper way.
> > Thanks for your time.
> 
> Indeed you have expressed your own opinion and some others might agree
> but this is _not_ the official stance of the Debian project. Please
> carefully read the aforementioned thread on debian-devel
> 
> "https://www.debian.org/vote/2006/vote_004
> 
> That GR proposal does not require source for non-programmatic works.  It
> only "strongly recommends" it, and says explicitly that such source
> doesn't have to be in the archive.
> 
> Quote from Russ Albery on debian-devel
>  https://lists.debian.org/debian-devel/2014/03/msg00299.html;

As far as I can tell, this is Russ Allbery's opinion, not the official
stance of the Debian Project.

It's true that the above-cited GR proposed to affirm that source for
non-programmatic works is only "strongly recommended" and not
required, but the GR option did not win.
Since there was no other option in that GR, we cannot be sure on the
reasons why the option did not win: it could be because many people
thought that availability of source for non-programmatic works should
not even be recommended (as you seem to imply), but it could even be
because many people thought that such availability should be required
(rather than just recommended).

Please note that the FTP Masters seem to require source for at least
some non-programmatic works (such as documents): quoting
https://ftp-master.debian.org/REJECT-FAQ.html

| Source missing
|   Your package contains files that need source but do not have it.
|   These include PDF and PS files in the documentation, or
|   auto-generated files. 


So in conclusion, I am still convinced that the Debian Project must
distribute the source (for works included in packages in Debian main)
anyway, regardless of how permissive is the license.



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp2JVFos_KcA.pgp
Description: PGP signature

Bug#840360: Multiple security issues

[Moritz Muehlenhoff]

Source: libiberty
Severity: important
Tags: security

Several security issues have been reported in libiberty,
the security tracker has additional references:
https://security-tracker.debian.org/tracker/CVE-2016-6131
https://security-tracker.debian.org/tracker/CVE-2016-4493
https://security-tracker.debian.org/tracker/CVE-2016-4492
https://security-tracker.debian.org/tracker/CVE-2016-4491
https://security-tracker.debian.org/tracker/CVE-2016-4490
https://security-tracker.debian.org/tracker/CVE-2016-4489
https://security-tracker.debian.org/tracker/CVE-2016-4488
https://security-tracker.debian.org/tracker/CVE-2016-4487
https://security-tracker.debian.org/tracker/CVE-2016-2226

These are all fixed in trunk since 2016-08-04, the source
package currently in sid as libiberty-20160807 does not
contain those, though.

Cheers,
Moritz

Bug#840359: gstreamer1.0-plugins-good providing an audiosink causes troubles

[Adrian Bunk]

Package: gstreamer1.0-plugins-good
Version: 1.8.3-1+b1
Severity: important

Several packages like quodlibet (#785432) or buzztrax contain the
following in the dependencies:
  Depends: ..., gstreamer1.0-plugins-good, ...
   gstreamer1.0-pulseaudio | gstreamer1.0-audiosink, ...


This does not work due to gstreamer1.0-plugins-good providing
gstreamer1.0-audiosink (since it contains libgstjack).


The result is that many users end up with having only the JACK
audiosink installed, and this is causing a huge amount of headaches
for users and maintainers of packages using GStreamer (I can provide
more bug numbers if necessary).


There are two possible solutions for this problem:
1. split all audiosinks into own packages, so that
   "gstreamer1.0-pulseaudio | gstreamer1.0-audiosink" works as expected
2. merge the ALSA and PulseAudio sinks into -base and -good,
   so depending on -good would ensure all common audio sinks are present

Are there any cases where option 2 would cause problems?

Bug#425898: Processed: ultrastar-ng is now performous

[Adrian Bunk]

On Mon, Oct 10, 2016 at 11:10:56PM +0200, Markus Koschany wrote:
> On 10.10.2016 22:57, Debian Bug Tracking System wrote:
> > Processing commands for cont...@bugs.debian.org:
> > 
> >> reassign 425898 performous
> > Bug #425898 [ultrastar-ng] ultrastar-ng: please provide some demo songs !
> > Warning: Unknown package 'ultrastar-ng'
> > Bug reassigned from package 'ultrastar-ng' to 'performous'.
> > No longer marked as found in versions ultrastar-ng/0.1.4-2 and 
> > ultrastar-ng/0.1.4-1.
> > Ignoring request to alter fixed versions of bug #425898 to the same values 
> > previously set
> >> thanks
> > Stopping processing here.
> > 
> > Please contact me if you need assistance.
> 
> Why do you reassign bugs from packages that have been removed from
> Debian a long time ago?

The package was renamed, not removed.

This made reassigning sound more appropriate than blindly closing.

> This issue is already resolved because fretsonfire-songs-muldjord and
> fretsonfire-songs-sectoid are automatically detected by performous. See
> also /usr/share/doc/performous/README.Debian that lists all directories
> in which songs are searched for.

It might not matter much when Lucas is the submitter, but in general
it is better when this bug gets closed with "already fixed" than a
not completely correct "package was removed".


The reason why I didn't close the bug this way myself actually seems to 
be a bug in the package:

performous does not have any relationship (Depends/Recommends/Suggests)
on these song packages you mention.

This was the reason why I didn't find them when checking quickly whether 
the bug was clearly already fixed.

I'd guess users would also appreciate at least a Suggests of them.


cu
Adrian

-- 

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

Bug#840358: Multiple security issues in libiberty

[Moritz Muehlenhoff]

Package: ht
Severity: grave
Tags: security

ht embeds a copy of libiberty, which was affected by several
vulneranbilities:

https://security-tracker.debian.org/tracker/CVE-2016-6131
https://security-tracker.debian.org/tracker/CVE-2016-4493
https://security-tracker.debian.org/tracker/CVE-2016-4492
https://security-tracker.debian.org/tracker/CVE-2016-4491
https://security-tracker.debian.org/tracker/CVE-2016-4490
https://security-tracker.debian.org/tracker/CVE-2016-4489
https://security-tracker.debian.org/tracker/CVE-2016-4488
https://security-tracker.debian.org/tracker/CVE-2016-4487
https://security-tracker.debian.org/tracker/CVE-2016-2226

Cheers,
Moritz

Bug#840271: Removed package(s) from unstable (codelite)

[James Cowgill]

Hi,

On 10/10/16 11:23, Debian FTP Masters wrote:
> We believe that the bug you reported is now fixed; the following
> package(s) have been removed from unstable:
> 
>   codelite | 9.2+dfsg-2 | powerpc
> codelite-plugins | 9.2+dfsg-2 | powerpc
> 
> --- Reason ---
> ROM; nodejs no longer built on powerpc
> --

I don't understand. codelite neither Build-Depends nor Depends on nodejs
so this removal seems completely pointless to me. Codelite is just going
to reappear on powerpc when I next upload a new version.

Also, it would be great if you could CC the maintainer before removing
packages.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#840323: debhelper: cmake build system: cross compilation

[Holger Levsen]

Hi Helmut,

On Mon, Oct 10, 2016 at 08:39:39PM +0200, Helmut Grohne wrote:
> dpkg-cross is deprecated by its former maintainer and ought to be
> removed.

this seems a fairly strong statement, considering
https://tracker.debian.org/pkg/dpkg-cross shows not a single bug filed
against the package.

cc:ing Neil and wookey for comment - if this is the case, please file a
RM bug, dpkg-cross is even part of testing!


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#840357: CVE-2015-1336

[Moritz Muehlenhoff]

Package: man-db
Version: 2.7.5-1
Severity: important
Tags: security

Please see
http://www.halfdog.net/Security/2015/MandbSymlinkLocalRootPrivilegeEscalation/

Cheers,
Moritz

Bug#734365: fixed in freeplayer 20070531+dfsg.1-4

[Antoine Musso]

The bug still happens in Jessie which is stuck to 20070531+dfsg.1-3

  * Fix vlc invocation (remove the "--http-charset=ISO-8859-1" option)
(Closes: #734365)

Is there a way to pick that patch and release an update for Jessie?

--
Antoine Musso

Bug#833395: emacspeak: please make the build reproducible

[Chris Lamb]

Hi Paul,

> [I] have other things I find more urgent than an upload only fixing
> a reproducibility issue.

Well, uploads are "cheap" and, after all, one can always upload
again…  No, will leave to you :)


Warm regards,

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

Bug#837366: aptitude: #839792 (Segfaults when typing (into aptitude) during or maybe shortly before package download) and #837366 (Crash when typing while saying "Updating ... and quitting") might be

[Axel Beckert]

Hi,

JFTR: in case this is actually an issue inside cwidget or in the way
cwidget is used by aptitude, the two bug reports 839792 (Segfaults
when typing (into aptitude) during or maybe shortly before package
download) and #837366 (Crash when typing while saying "Updating ...
and quitting") might be the same issue or at least related.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#840056: shibboleth-sp2-utils: upgrade attempt of shibboleth-sp2-utils gets hung at restart of shibd service

[S. Banerian]

On 10/09/2016 05:25 PM, Ferenc Wágner wrote:
> "S. Banerian"  writes:
> 
>> On 10/07/2016 02:04 PM, Ferenc Wágner wrote:
>>
 Manually trying to start /usr/sbin/shibd -f -F never produces the
 /run/shibboleth/shibd.sock nor any other files in that dir.
>>>
>>> This is really disturbing.  You don't except the above command to give
>>> back your prompt, right?  
>>
>> correct.
>>
>>> Could you please make sure shibd isn't running
>>> then show me the output of
>>>
>>> # sudo -u _shibd strace shibd -f -F
>>
>> the output is rather long...
>> I shall attach.
> 
> Thanks.  Does it hang there indefinitely, with no further output for
> minutes?  

after some 12 hours of trying to start, failing, it finally started,
created shibd.sock, and under a test, worked.

Its dpkg status is still iF


Does shibd still consume significant CPU according to top?

at this moment, no.
> What are its memory figures?

nothing big.

> Isn't your computer swapping heavily?

no

> Can
> you provide a full GDB backtrace (after installing
> shibboleth-sp2-utils-dbgsym; please yell if you need precise
> instructions).

does not appear to be in stretch. so i need the instructions.


>> Note: prior to the upgrade, shibboleth was working.
> 
> Which version of shibboleth was working for you?

the version just prior to this one 2.6.0+dfsg1-3+b1 on stretch.

> Can you share your shibboleth2.xml?

I'm a bit reluctant to provide some of the information in the
RequestMapper sections.



>> We did note that sometimes shibd was more well-behaved when starting
>> from shell than via systemctl.
> 
> Could you please make this more precise?  How did it misbehave when
> started by systemctl?

this is where it hangs for minutes, says it might start, may or may not
create /run/shibboleth/shibd.sock  and the apache application only
returns with shibboleth errors.

Now, however, as it has sat over the weekend, and finally started, dpkg
has let the upgrade complete, with no errors.

When I force a restart, systemctl restart shibd.service I get the issue
as before, where

\_ /bin/systemd-tty-ask-password-agent --watch

stays there for a looong time, and is not returning, systemctl says it
is started, but journalctl -xe gives:

Oct 10 14:00:35 epics systemd[1]: shibd.service: Killing process 30980
(shibd) with signal SIGKILL.
Oct 10 14:00:35 epics systemd[1]: shibd.service: Main process exited,
code=killed, status=9/KILL
Oct 10 14:00:35 epics systemd[1]: Failed to start Shibboleth Service
Provider Daemon.
-- Subject: Unit shibd.service has failed

there is a shibd -f -F process running, but no shibd.sock file

I'm not convinced that systemd is behaving well.


-- 
Stefani Banerian
UW Clinical Cyclotron www.uwmcf.org
UW School of Medicine
UW Box 356043
206-598-0302
gpg key 6642E7EE
fingerprint = BD13 875D 2D03 5E1D 1E3B  8BF7 F4B8 63AD 6642 E7EE

Bug#839861: lintian: init.d-script-needs-depends-on-lsb-base does not use strict enough lsb-base version for (eg.) status_of_proc

[Chris Lamb]

Hi Vincent,

> Shouldn't we just remove the version? oldstable has a recent enough
> version. 3.2-14 is from 2008. A dependency on lsb-base is enough and
> wouldn't trigger bugs like this where the version needs to be adjusted.

Some thoughts on this are here:

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838997#42

Can you follow-up there? :)


Regards,

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

Bug#425898: Processed: ultrastar-ng is now performous

[Markus Koschany]

On 10.10.2016 22:57, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
>> reassign 425898 performous
> Bug #425898 [ultrastar-ng] ultrastar-ng: please provide some demo songs !
> Warning: Unknown package 'ultrastar-ng'
> Bug reassigned from package 'ultrastar-ng' to 'performous'.
> No longer marked as found in versions ultrastar-ng/0.1.4-2 and 
> ultrastar-ng/0.1.4-1.
> Ignoring request to alter fixed versions of bug #425898 to the same values 
> previously set
>> thanks
> Stopping processing here.
> 
> Please contact me if you need assistance.

Why do you reassign bugs from packages that have been removed from
Debian a long time ago?

This issue is already resolved because fretsonfire-songs-muldjord and
fretsonfire-songs-sectoid are automatically detected by performous. See
also /usr/share/doc/performous/README.Debian that lists all directories
in which songs are searched for.




signature.asc
Description: OpenPGP digital signature

Bug#837238: FTBFS with Django 1.10

[Thomas Goirand]

Hi,

The issue that was reported is gone since the upload of OpenStack Newton
in Sid, however trove-dashboard still FTBFS because of incompatibility
with Django 1.10

A patch upstream was opened here:
https://review.openstack.org/381999

but that's not a 100%: there's still a failure, and many Python
trace-dump during execution of unit test.

Bug#840356: initscripts: mountkernfs.sh does not mount configfs

[Christophe Vu-Brugier]

Package: initscripts
Version: 2.88dsf-59.8
Severity: normal

Dear Maintainer,

I am working on the targetcli-fb and python-rtslib-fb packages that
rely on configfs and I think there is an issue in the mountkernfs.sh
script that prevents it from mounting the configfs file system.

The mount_filesystems() function in /etc/init.d/mountkernfs.sh
contains the following code to mount the configfs file system under
/sys/kernel/config:

  if [ -d /sys/kernel/config ]
  then
domount "$MNTMODE" configfs "" /sys/kernel/config configfs ""
  fi

The problem is that the /sys/kernel/config directory does not exist
when the script is invoked because the configfs kernel module is not
loaded at that time. The /sys/kernel/config directory does not exist
until the configfs module is probed. See:

  http://lxr.free-electrons.com/source/fs/configfs/mount.c#L142

Invoking `modprobe configfs` before testing for /sys/kernel/config
being a directory allows to mount configfs as expected. I am not sure
it is the proper fix though.

There was a similar issue reported for systemd: #800521

  systemd: sys-kernel-config.mount not functional
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800521

The fix for this bug was to make the package install a configuration
file in a modules-load.d directory to load the configfs module. I
tried to do the same for sysv, expecting that the configfs module
would be loaded before mountkernfs.sh is run, but it is not the case.

Maybe we could cut the configfs section from mountkernfs.sh and put it
in a separate mountconfigfs.sh init script that would start after kmod?

What do you think?

With best regards,

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

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

Versions of packages initscripts depends on:
ii  coreutils   8.25-2
ii  debianutils 4.8
ii  lsb-base9.20160629
ii  mount   2.28.2-1
ii  sysv-rc 2.88dsf-59.8
ii  sysvinit-utils  2.88dsf-59.8

Versions of packages initscripts recommends:
ii  e2fsprogs  1.43.3-1
ii  psmisc 22.21-2.1+b1

initscripts suggests no packages.

-- no debconf information

Bug#835177: aodh: FTBFS with eatmydata (build hangs)

[Thomas Goirand]

Hi Santiago,

I have uploaded what I believe is a fix for #835177. Though as I am not
sure how to reproduce your build env, it'd be really nice if you could
try to build aodh 3.0.0-2 and check that the bug is really closed.

If that is the case (that my change fixes the FTBFS of aodh in your
env), then I will apply the same kind of fix for #835178 and #835179.

Thanks a lot if you can help here,
Cheers,

Thomas Goirand (zigo)

Bug#840355: Failed to create spool file /var/spool/exim4//input//...-D: Permission denied

[積丹尼 Dan Jacobson]

Package: exim4
Version: 4.88~RC2-1
Severity: grave

Can't send mail, because:
2016-10-11 04:30:53 Failed to create spool file 
/var/spool/exim4//input//1bthDp-0002gq-Fy-D: Permission denied

-- Package-specific info:
Exim version 4.88 #2 built 09-Oct-2016 15:37:08
Copyright (c) University of Cambridge, 1995 - 2016
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2016
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM DNSSEC Event 
OCSP PRDR SOCKS
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated
dc_eximconfig_configtype='smarthost'
dc_other_hostnames='jidanni2.jidanni.org;jidanni3.jidanni.org;jidanni4.jidanni.org;jidanni5.jidanni.org;jidanni6.jidanni.org'
dc_readhost='jidanni.org'
dc_relay_domains=''
dc_minimaldns='true'
dc_relay_nets=''
dc_smarthost='homie.mail.dreamhost.com::587'
dc_local_interfaces=''
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='false'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:jidanni.org

-- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.7.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages exim4 depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  exim4-base 4.88~RC2-1
ii  exim4-daemon-light 4.88~RC2-1

exim4 recommends no packages.

exim4 suggests no packages.

-- debconf information:
  exim4/drec:

Bug#840254: [Pkg-xfce-devel] Bug#840254: thunar: freeze when mounting USB drive

[Ben Caradoc-Davies]

On 10/10/16 22:40, Yves-Alexis Perez wrote:

Thanks for the report. Does this happen with *all* usb keys / removable
devices? Does the fs matter?


I just confirmed the problem with a vfat thumb drive; I do not think the 
fs matters (mentioned only for completeness). I have tested several 
different drives.


Only once during testing, 1.6.10-3 appeared to start working correctly 
for all drives. This behaviour did not survive a reboot. Mounting with 
1.6.10-2 is always successful.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#840354: src:pcre3: FTBFS on powerpc (G4 CPU)

[Christoph Biedl]

Package: src:pcre3
Version: 2:8.39-2
Severity: important
Usertag: debian-powe...@lists.debian.org

Dear Maintainer,

Rebuilding syslog-ng 3.7.3-3 on a PowerMac G4 failed with SIGILL,
debugging led to libpcre, and finally rebuilding src:pcre3 itself
fails with very similar symptoms:

(...)
/usr/bin/make  check-TESTS
make[3]: Entering directory '/tmp/pcre3/pcre3-8.39'
make[4]: Entering directory '/tmp/pcre3/pcre3-8.39'
./test-driver: line 107: 12195 Illegal instruction "$@" > $log_file 2>&1
FAIL: pcre_jit_test
PASS: pcrecpp_unittest
PASS: pcre_scanner_unittest
(...)

The failing program is .libs/lt-pcre_jit_test. Using gdb is no help at
all, the failures happen at a different point every invocation:

Program received signal SIGILL, Illegal instruction.
0xb7faf0ec in ?? ()
(gdb) bt
#0  0xb7faf0ec in ?? ()
#1  0x1ff30718 in ?? ()
#2  0x1ff30718 in ?? ()
#3  0x1ff0adf4 in ?? ()
#4  0x200061c8 in ?? ()
#5  0x20004a3c in ?? ()
#6  0x1fc97274 in ?? ()
#7  0x1fc9747c in ?? ()
#8  0x in ?? ()
(gdb) disassemble 0xb7faf0ec,0xb7faf0ff
Dump of assembler code from 0xb7faf0ec to 0xb7faf0ff:
=> 0xb7faf0ec:  li  r3,-1
   0xb7faf0f0:  addir5,r30,6
   0xb7faf0f4:  cmplw   cr1,r5,r29
   0xb7faf0f8:  bgt cr1,0xb7faf1b8
   0xb7faf0fc:  lwz r5,36(r1)

Program received signal SIGILL, Illegal instruction.
0xb7fe5008 in ?? ()
(gdb) bt
#0  0xb7fe5008 in ?? ()
#1  0x1ffb8b80 in ?? ()
#2  0x1ff91820 in ?? ()
#3  0x20006110 in ?? ()
#4  0x20004a3c in ?? ()
#5  0x1fc97274 in ?? ()
#6  0x1fc9747c in ?? ()
#7  0x in ?? ()
(gdb) disassemble 0xb7fe5008,0xb7fe5020
Dump of assembler code from 0xb7fe5008 to 0xb7fe5020:
=> 0xb7fe5008:  mflrr0
   0xb7fe500c:  stw r31,-4(r1)
   0xb7fe5010:  stw r30,-8(r1)
   0xb7fe5014:  stw r29,-12(r1)
   0xb7fe5018:  stw r28,-16(r1)
   0xb7fe501c:  stw r27,-20(r1)

Program received signal SIGILL, Illegal instruction.
0xb7faf060 in ?? ()
(gdb) bt
#0  0xb7faf060 in ?? ()
#1  0x1ff30718 in ?? ()
#2  0x1ff30718 in ?? ()
#3  0x1ff0adf4 in ?? ()
#4  0x200061c8 in ?? ()
#5  0x20004a3c in ?? ()
#6  0x1fc97274 in ?? ()
#7  0x1fc9747c in ?? ()
#8  0x in ?? ()
(gdb) disassemble 0xb7faf060,0xb7faf070
Dump of assembler code from 0xb7faf060 to 0xb7faf070:
=> 0xb7faf060:  lwz r28,8(r5)
   0xb7faf064:  addir3,r3,1
   0xb7faf068:  stw r3,32(r1)
   0xb7faf06c:  b   0xb7faf0cc


My last rebuild of syslog-ng in July, using pcre3 version 2:8.38-3.1,
succeded. Therefore I guess it's the changes between 8.38 and 8.39.
Very likely this was introduced by the changes in the ppc_jit code
which unfortunately I was unable to understand.

Disabling jit for powerpc using the following patch:

--- pcre3-8.39.orig/sljit/sljitConfigInternal.h
+++ pcre3-8.39/sljit/sljitConfigInternal.h
@@ -135,11 +135,7 @@
 #elif defined(__ppc64__) || defined(__powerpc64__) || defined(_ARCH_PPC64) || 
(defined(_POWER) && defined(__64BIT__))
 #define SLJIT_CONFIG_PPC_64 1
 #elif defined(__ppc__) || defined(__powerpc__) || defined(_ARCH_PPC) || 
defined(_ARCH_PWR) || defined(_ARCH_PWR2) || defined(_POWER)
-# ifndef __NO_FPRS__
-#  define SLJIT_CONFIG_PPC_32 1
-# else
 #  define SLJIT_CONFIG_UNSUPPORTED 1
-# endif
 #elif defined(__mips__) && !defined(_LP64)
 #define SLJIT_CONFIG_MIPS_32 1
 #elif defined(__mips64)

resulted in a successful pcre3 build, and using the created packages
also syslog-ng passes the failing test again.


So I'm asking you to bring this upstream to sort out how the breakage
was introduced. From other bug reports I guess the created code uses
G5 instructions; the Debian powerpc buildds didn't notice as they
actually are such newer boxes.

As a hopefully temporary workaround you could disable jit for powerpc,
of course a the cost of a performance penalty.

Christoph

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

Kernel: Linux 4.4.23
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect



signature.asc
Description: Digital signature

Bug#840353: RFS: budgie-desktop/10.2.7-3

[foss.freedom]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "budgie-desktop"

 * Package name: budgie-desktop
   Version : 10.2.7-3
   Upstream Author : i...@solus-project.com
 * URL : https://github.com/solus-project/budgie-desktop
 * License : LGPL-2.1/GPL2.0
   Section : x11

  It builds those binary packages:

budgie-core - Core package for Budgie-Desktop
 budgie-core-dev - Development package for budgie-desktop
 budgie-desktop - Desktop package for budgie-desktop
 budgie-desktop-doc - documentation files for the budgie-desktop
 gir1.2-budgie-desktop-1.0 - GNOME introspection library for budgie-desktop
 libbudgie-plugin0 - Plugin library for budgie-desktop
 libbudgietheme0 - Theme library for budgie-desktop
 libraven0  - Raven library for budgie-desktop

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/budgie-desktop


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/b/budgie-desktop/budgie-desktop_10.2.7-3.dsc

Notes:
  upstream (budgie-desktop) have noted various issues with GTK+3.22
currently in Sid.  Patches selected to resolve these.
  Additionally rediagnosed a crash and worked around this using a
gsettings override - upstream are going to rewrite budgie-menu soon so
hopefully this workaround can be dropped in the near future.

  Changes since the last upload:
  * Drop patch to stop refresh of menus
  * replace dropped patch with gsettings override to hide menu headers
- menu crash traced to menu headers; by hiding the menu header
  panel does not crash when installing or removing applications
  upstream issue #632
  * Add upstream patch to stop spamming of log
- 0004-panel-Chain-methods-to-fix-GtkBox-allocation-spam-ev.patch
  * Add upstream patch to fix GTK+3.22 theme display
- 0005-Fix-theme-for-GTK-3.22.patch




  Regards,
   David Mohammed

Bug#840322: emacs24-common: emacsclient fails with *ERROR*: Invalid function

[Tom Marble]

Rob Browning  writes:
> Hmm.  Does foo.txt have anything odd in it, [...]

No, it's a non-existant file.

> and does it still crash if
> you do something like this:
>
>   $ emacs -Q --daemon=foo
>   $ emacsclient -c -s foo /tmp/foo.txt

Interestingly it does not crash:

tmarble@cerise 175 :) emacs -Q --daemon=foo

Warning: due to a long standing Gtk+ bug
http://bugzilla.gnome.org/show_bug.cgi?id=85715
Emacs might crash when run in daemon mode and the X11 connection is 
unexpectedly lost.
Using an Emacs configured with --with-x-toolkit=lucid does not have this 
problem.
Starting Emacs daemon.
tmarble@cerise 176 :)

In another terminal
  emacsclient -c -s foo /tmp/foo.txt
worked just fine

> Just wondering if -Q avoids the problem.

I updated my MELPA and restarted Emacs.. and now I can't
reproduce the bug.. emacsclient just works.

Feel free to close the bug now (sorry for the noise)!

--Tom

Bug#332589: Messages not decrypted when bulk-printing

[Alexander Sack]

tags 332589 - moreinfo
thanks

removing moreinfo tag as we first have to find someone who can reproduce :).

2016-09-09 18:35 GMT+02:00 Alexander Sack :
> tags 332589 + unreproducible
> thanks
>
> ok lets leave it at this for a while before closing.
>
> Thanks!
>
> 2016-09-09 16:47 GMT+02:00 Sven Rudolph :
>> Alexander Sack  writes:
>>
>>> thanks for reporting the bug. We would like to identify issues to
>>> focus on and hence
>>> we would love to hear an update if the issue at hand is still
>>> something you would like
>>> to see fix (if it hasn't).
>>
>> I do not use enigmail anymore.
>>
>> Nowadays enigmail plugs into thunderbird, I do not have a thunderbird
>> setup where I can reproduce the problem.
>>
>> Sven

Bug#840352: non-free license of debian/*

[Thorsten Alteholz]

Package: clod
Version: 1.0.1-1
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

Hi Daniel,

while looking at you debian/copyright again, the license of debian/* only
allows to distribute the files without royalties (not with or without as 
for the modifications).
So this looks like a non-free license that is not DFSG compatible. Can 
you please change the wording or move the package to non-free?


Thanks!
  Thorsten

Bug#461958: screen: Can't press ctrl+pgup/dn to change tabs in vim

[Antti Jarvinen]

Confirmed, this still happens with screen 4.4.0-4. Even the
work-around works. 

It seems to me that there is upstream bug open at
https://savannah.gnu.org/bugs/?24076
and there this is treated as a feature request. The report does not
describe exactly this ctrl+pageup -situation but ctrl-left-arrow is
given as example - this might be the same issue.

--
Antti Järvinen

Bug#836943: Incorporate new and revised documents from upstream

[Thaddeus H. Black]

I'd like to start working toward an NMU to fix this bug, since
you seem too busy to respond at the moment.  The patch would
consist mostly of a large amount of data, so the patch would be
too big to post here, but maybe I can post it elsewhere and
link from here to it; or maybe I'll find another way to
describe or represent the patch.

Objections?  If not, or if I hear no response within two weeks,
then I'll start work and, if I achieve what seems to me to be a
satisfactory patch (which is not guaranteed, for I do not know
this package as well as you do), then I'll post a link to (or
otherwise describe or represent) the patch, wait another two
weeks, and finally upload to DELAYED/10-day.



signature.asc
Description: Digital signature

Bug#840351: user asked same question twice upon upgrade

[積丹尼 Dan Jacobson]

Package: keyboard-configuration
Version: 1.151

During upgrade the user gets asked the same question twice.

The first time is at
Preconfiguring packages ...

The second time is when (viewed with pstree -al):
`-frontend -w /usr/share/debconf/frontend 
/var/lib/dpkg/info/keyboard-configuration.postinst configure 1.150
  |   |-keyboard-config 
/var/lib/dpkg/info/keyboard-configuration.config configure 1.150
  |   `-whiptail --backtitle Package configuration --title 
Configuring keyboard-configuration --output-fd 11 --default-item Generic 
105-key (Intl) PC --menu Please select the model of the keyboard o...

Even though in both cases he says  to the default-item.

Bug#840342: [ace-of-penguins] Freecell No Longer Runs, Nvidia Legacy-304xx video driver

[Markus Koschany]

Control: tags -1 - moreinfo
Control: reassign -1 nvidia-legacy-304xx-driver

I am reassigning this bug report to nvidia-legacy-304xx-driver because
the report indicates that this is a Nvidia specific issue.
Ace-of-Penguins should work with every graphics card of the last decade
and I can't reproduce this issue on my system.

The bug reporter attached a Xorg.* log file. If you have more questions,
please don't hesitate to ask.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#840322: emacs24-common: emacsclient fails with *ERROR*: Invalid function

[Rob Browning]

Tom Marble  writes:

> tmarble@cerise 127 :) emacsclient /tmp/foo.txt
> Waiting for Emacs...
> *ERROR*: Invalid function: (\` ((\, file) _))
> tmarble@cerise 128 :( emacsclient --no-wait --eval '(find-file 
> "/tmp/foo.txt")'
> *ERROR*: Invalid function: (\` ((\, file) _))
> tmarble@cerise 129 :( 

Hmm.  Does foo.txt have anything odd in it, and does it still crash if
you do something like this:

  $ emacs -Q --daemon=foo
  $ emacsclient -c -s foo /tmp/foo.txt

Just wondering if -Q avoids the problem.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#839580: request-tracker4: FTBFS in testing (failed tests)

[Niko Tyni]

Control: tag -1 help

On Sun, Oct 02, 2016 at 10:42:49AM +, Santiago Vila wrote:
> Package: src:request-tracker4
> Version: 4.2.13-2
> Severity: serious

> t/mail/gnupg-outgoing-signed_encrypted.t (Wstat: 3584 Tests: 68 
> Failed: 14)
>   Failed tests:  10-11, 18-19, 27-28, 35-36, 41, 43, 48
> 50, 67-68
>   Non-zero exit status: 14
>   Parse errors: Bad plan.  You planned 104 tests but ran 68.
> t/mail/gnupg-special.t   (Wstat: 512 Tests: 19 
> Failed: 2)
>   Failed tests:  16, 19
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 26 tests but ran 19.

[...]

All this regressed with libgnupg-interface-perl_0.52-4. Presumably the
test suite now exercises gnupg2 instead of gnupg1 for the parts using
GnuPG::Interface (= most of the actual GnuPG related functionality.)

There seem to be at least hardcoded gnupg error messages in the test
suite that probably need changing:

  like( $warnings[0], qr{signing failed: secret key not available},

Not sure if RT::Crypt::GnuPG is going to require some porting too.

Help untangling this mess would be very welcome, as both Dominic and I
are rather short on time. Tagging and copying possible candidates :)

(BTW there's also a missing build dependency on tzdata that can create
additional failures for clean chroots.)
-- 
Niko Tyni   nt...@debian.org

Bug#811868: Fix for the linuxdcpp FTBFS

[Adrian Bunk]

Control: tags -1 +patch

A fix for the linuxdcpp FTBFS is attached.

cu
Adrian

-- 

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

Description: Build with -std=gnu++98
 What broke the build is that gcc 6 changed the default C++ standard
 from C++98 to C++14.
 .
 Not all valid C++98 code is also valid C++11 and C++14 code.
 .
 Note that this just changed the default, when told to process C++98 code 
 gcc 6 does not differ in any significant way from gcc 5.
 .
 Making the code compatible with C++14 would be the best possible 
 solution, but as a workaround it is possible to fix the build with
 this change to tell gcc that this is C++98 code.
Author: Adrian Bunk 
Bug-Debian: https://bugs.debian.org/811868

--- linuxdcpp-1.1.0.orig/SConstruct
+++ linuxdcpp-1.1.0/SConstruct
@@ -18,7 +18,7 @@ BUILD_PATH = '#/build/'
 BUILD_LOCALE_PATH = BUILD_PATH + 'locale/'
 
 BUILD_FLAGS = {
-	'common'  : ['-I#', '-D_GNU_SOURCE', '-D_LARGEFILE_SOURCE', '-D_FILE_OFFSET_BITS=64', '-D_REENTRANT'],
+	'common'  : ['-I#', '-D_GNU_SOURCE', '-D_LARGEFILE_SOURCE', '-D_FILE_OFFSET_BITS=64', '-D_REENTRANT', '-std=gnu++98'],
 	'debug'   : ['-g', '-ggdb', '-Wall', '-D_DEBUG'], 
 	'release' : ['-O3', '-fomit-frame-pointer', '-DNDEBUG']
 }

Bug#840350: jessie-pu: package dbus/1.8.22-0+deb8u1

[Simon McVittie]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

I've released a new upstream version of dbus which fixes a potential
security vulnerability. I don't *think* it's exploitable in Debian
oldstable or later, so the security team don't intend to do a DSA;
but I'd like to get the fix into jessie in case we were wrong.
Advisory: 

In addition, I'd like to fix dbus RC bug
 (dbus fails
to remove if something is trying to connect to the system bus in
parallel with the removal process), which has been fixed in unstable
since March.

Proposed debdiff is attached, with Autotools noise stripped. This is
the minimal version which doesn't add a dependency; the "nice" version
would be to use deb-systemd-invoke instead of systemctl, but
init-system-helpers isn't Essential in jessie, so I'd have to add
a dependency for that. Please let me know which you'd prefer.

The one thing you might find odd in the debdiff is that it adds
-Wno-deprecated-declarations. This was necessary to be able to build
the new upstream release on recent distributions where readdir_r()
is marked deprecated; it doesn't have any practical impact on the
binary contents.

Regards,
S
# debdiff --exclude=config.guess --exclude=config.sub --exclude=config.h.in 
--exclude=configure --exclude=install-sh --exclude=ltmain.sh --exclude=m4 
--exclude=Makefile.in dbus_1.8.20-0%2bdeb8u1.dsc dbus_1.8.22-0+deb8u1.dsc

diffstat for dbus-1.8.20 dbus-1.8.22

 NEWS  |   21 +
 bus/activation.c  |2 +-
 configure.ac  |5 +++--
 debian/changelog  |   11 +++
 debian/dbus.prerm |   14 ++
 5 files changed, 50 insertions(+), 3 deletions(-)

diff -Nru --exclude config.guess --exclude config.sub --exclude config.h.in 
--exclude configure --exclude install-sh --exclude ltmain.sh --exclude m4 
--exclude Makefile.in dbus-1.8.20/bus/activation.c dbus-1.8.22/bus/activation.c
--- dbus-1.8.20/bus/activation.c2015-05-14 13:23:25.0 +0100
+++ dbus-1.8.22/bus/activation.c2016-10-10 10:08:30.0 +0100
@@ -2249,7 +2249,7 @@
  DBUS_TYPE_STRING, ,
  DBUS_TYPE_STRING, ,
  DBUS_TYPE_INVALID))
-dbus_set_error(, code, str);
+dbus_set_error (, code, "%s", str);
 
 
   if (unit)
diff -Nru --exclude config.guess --exclude config.sub --exclude config.h.in 
--exclude configure --exclude install-sh --exclude ltmain.sh --exclude m4 
--exclude Makefile.in dbus-1.8.20/configure.ac dbus-1.8.22/configure.ac
--- dbus-1.8.20/configure.ac2015-07-21 17:32:10.0 +0100
+++ dbus-1.8.22/configure.ac2016-10-10 10:21:56.0 +0100
@@ -3,7 +3,7 @@
 
 m4_define([dbus_major_version], [1])
 m4_define([dbus_minor_version], [8])
-m4_define([dbus_micro_version], [20])
+m4_define([dbus_micro_version], [22])
 m4_define([dbus_version],
   [dbus_major_version.dbus_minor_version.dbus_micro_version])
 
AC_INIT([dbus],[dbus_version],[https://bugs.freedesktop.org/enter_bug.cgi?product=dbus],[dbus])
@@ -37,7 +37,7 @@
 
 ## increment any time the source changes; set to
 ##  0 if you increment CURRENT
-LT_REVISION=13
+LT_REVISION=14
 
 ## increment if any interfaces have been added; set to 0
 ## if any interfaces have been changed or removed. removal has
@@ -1347,6 +1347,7 @@
   dnl - type-limits is probably a bug too, but having the rest of -Wextra
   dnl   is better than nothing
   [$DISABLE_UNUSED_WARNINGS \
+   deprecated-declarations \
missing-field-initializers \
unused-parameter \
sign-compare \
diff -Nru --exclude config.guess --exclude config.sub --exclude config.h.in 
--exclude configure --exclude install-sh --exclude ltmain.sh --exclude m4 
--exclude Makefile.in dbus-1.8.20/debian/changelog dbus-1.8.22/debian/changelog
--- dbus-1.8.20/debian/changelog2015-07-21 18:02:01.0 +0100
+++ dbus-1.8.22/debian/changelog2016-10-10 11:42:50.0 +0100
@@ -1,3 +1,14 @@
+dbus (1.8.22-0+deb8u1) jessie; urgency=medium
+
+  * New upstream bugfix release
+- fix a potential format string vulnerability, which is not believed
+  to be exploitable in practice
+  * dbus.prerm: ensure that dbus.socket is stopped before removal,
+so that a new connection to the bus won't cause dbus.service to be
+restarted (Closes: #813970)
+
+ -- Simon McVittie   Mon, 10 Oct 2016 11:42:50 +0100
+
 dbus (1.8.20-0+deb8u1) jessie; urgency=medium
 
   * New upstream bugfix release
diff -Nru --exclude config.guess --exclude config.sub --exclude config.h.in 
--exclude configure --exclude install-sh --exclude ltmain.sh --exclude m4 
--exclude Makefile.in dbus-1.8.20/debian/dbus.prerm 
dbus-1.8.22/debian/dbus.prerm
--- dbus-1.8.20/debian/dbus.prerm   1970-01-01 01:00:00.0 +0100
+++ 

Bug#840327: stopped working, no helpful feedback

[Brian Potkin]

On Mon 10 Oct 2016 at 18:15:15 +0200, Daniel Pocock wrote:

> Package: cups
> Version: 1.7.5-11+deb8u1
> 
> Printing had been working fine for a long time but about 20 minutes ago
> I tried to print something and an error popup appeared in GNOME asking
> if I wanted to diagnose the printer.  My document appeared paused in the
> queue.

Printing "working fine" for a long time must indicate something to you.
Then it stops working. How is this a bug rather than a matter for
debian-user? Computer systems don't generally go into meltdown because
they feel unappreciated.

> I looked at /var/log/cups/*log and found nothing about the error

You had debug logging enabled?

> I went to the control panel and also the CUPS web interface on port 631
> and tried re-enabling the printer and each time I did that it failed again.
> 
> I looked at /var/log/daemon.log and observed:
> 
> hpcups[16590]: prnt/hpcups/HPCupsFilter.cpp 707: First raster data plane..
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 1...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 2...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 3...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 4...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 5...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 6...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 7...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 8...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 9...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 10...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 11...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 12...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 13...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 14...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 15...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 16...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 17...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 18...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 19...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 20...
> hp[16592]: io/hpmud/jd.c 816: error timeout mdns lookup ABC123DEF.local
> hp[16592]: io/hpmud/jd.c 93: unable to read device-id
> hp[16592]: prnt/backend/hp.c 808: ERROR: open device failed stat=12:
> hp:/net/HP_LaserJet_3055?zc=ABC123DEF

This is a symptom indicating you have done something to the system. It
never happened before; why should it happen now? Things don't generally
occur out of the blue.
 
> I killed the cups process and modified /etc/cups/printers.conf to change
> the URI from:
> 
> DeviceURI hp:/net/HP_LaserJet_3055?zc=ABC123DEF
> 
> to something like:
> 
> DeviceURI hp:/net/HP_LaserJet_3055?ip=192.168.1.234
> 
> 
> and started cups again and now printing works again.
> 
> What is really wrong here?

Who knows? Having to do this is a sign of a non-optimal setup in some
way. You are the one in charge of the system. You've not touched
anything in the last year (or twenty minutes)?
 
> Why did the popup not tell me the root cause of the problem?  Why did I
> have to go hunting around in the log files like this?  How many
> non-developers would be comfortable troubleshooting a problem like that
> without more details?

System administrators should always feel comfortable about trouble
shooting. Admit it; you really love log files. :)

I'd set up the print queue again from scratch. Maybe.

Regards,

Brian.

Bug#840330: [Build-common-hackers] Bug#840330: cdbs: licensecheck runs twice during build

[Jonas Smedegaard]

Quoting Jérémy Lal (2016-10-10 21:24:23)
> 2016-10-10 20:59 GMT+02:00 Jonas Smedegaard :
>> Quoting Jérémy Lal (2016-10-10 18:51:53)
>>> cdbs runs licensecheck two times during build:
[...]
>>> and it crashes too.
>>
>> That's a different and more serious bug.  Please file a bugreport 
>> separately about that, with more details.
>
> ok, bad wording on my side: it doesn't crash, the build is killed 
> after 150 minutes of inactivity. Probably because licensecheck has to 
> analyze a lot more binary files because of this bug - that's fair so i 
> won't open a new bug.

That sounds like two bugs (of severity important, I suggest):

  * licensecheck too slow (takes 150/2 minutes for nodejs)
  * licensecheck is too silent (causes timeout on buildds)

>>> Is there some way to avoid completely running licensecheck when 
>>> building on sbuild. It's a ressource hog and discutably useful.
>>
>> Avoid build-depending on licensecheck should do the trick.
> 
> Well, that would be caused by
> Build-Depends: @cdbs@
> 
> which gives
> Build-Depends: cdbs,
>  licensecheck,
> 
> after refreshing control file with
> DEB_MAINTAINER_MODE=1 debuild clean
> 
> ?

This like suppresses auto-resolved build-dependency:

CDBS_BUILD_DEPENDS_rules_utils_copyright-check =


 - Jonas

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

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


signature.asc
Description: signature

Bug#840342: [ace-of-penguins] Freecell No Longer Runs, Nvidia Legacy-304xx video driver

[David Baron]

On יום שני, 10 באוקטובר 2016 21:54:58 IDT Markus Koschany wrote:
> On 10.10.2016 21:28, David Baron wrote:
> > On יום שני, 10 באוקטובר 2016 20:42:25 IDT Markus Koschany wrote:
> >> Control: tags -1 moreinfo
> >> 
> >> On 10.10.2016 20:34, David Baron wrote:
> >>> Package: ace-of-penguins
> >>> Version: 1.5~rc2-1+b1
> >>> Severity: normal
> >>> 
> >>> --- Please enter the report below this line. ---
> >>> After upgrade of the Nvidia Legacy 304xx driver (contrib), Freecell no
> >>> longer runs:
> >>> ~$ ace-freecell
> >>> X Error of failed request:  BadMatch (invalid parameter attributes)
> >>> 
> >>>   Major opcode of failed request:  73 (X_GetImage)
> >>>   Serial number of failed request:  25
> >>>   Current serial number in output stream:  25
> >> 
> >> [...]
> >> 
> >> Hello,
> >> 
> >> what makes you think that this is a bug in ace-of-penguins? Did you try
> >> to downgrade your Nvidia drivers? What was the outcome? Are you able to
> >> play the game with the free xserver-xorg-video-nouveau drivers?
> >> 
> >> Markus
> > 
> > Program did run using nouveau but nouveau and KDE/Plasma desktop do not
> > mix. So have not played it using nouveau in recent memory.
> > It is no longer possible to downgrade to the testing version of the
> > nvidia.
> > 
> > If other programs fail with the same error, then the point is well made.
> > If this is unique here, then something in the ace "backend" might be
> > examined.
> The error message indicates a bug or incompatibility between your X
> environment / X server and the proprietary Nvidia driver. This is a low
> level error and not related to ace-of-penguins which only requires a 2D
> capable graphics card. Everything from the past 20 years should work.
> 
> If the game works with nouveau it is most likely a bug in the non-free
> driver. Since the source code is closed it is not possible for Debian to
> work on a fix. The game works flawlessly on my system by the way.
> 
> Please note that you can download an earlier version of the Nvidia
> driver from snapshots.debian.org.
> 
> I am inclined to reassign this issue to
> xserver-xorg-video-nvidia-legacy-304xx. Please confirm this is the
> package you are currently using.
> 
> I am sure the maintainers of xserver-xorg-video-nvidia-legacy-304xx
> would be interested in your /var/log/Xorg.* log file because it provides
> a more detailed error report. Please attach this file to the bug report.
> 
> Regards,
> 
> Markus

Sounds like the way to go!
Log file is attached.
[   916.619] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[   916.619] X Protocol Version 11, Revision 0
[   916.619] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[   916.619] Current Operating System: Linux dovidhalevi 4.7.0-1-amd64 #1 SMP Debian 4.7.6-1 (2016-10-07) x86_64
[   916.619] Kernel command line: BOOT_IMAGE=Linux-4.7.0-1 ro root=UUID=d14ae79d-fd96-43d5-83b0-0bbbdd831196 quiet
[   916.619] Build Date: 06 September 2016  01:32:44PM
[   916.620] xorg-server 2:1.18.4-2 (https://www.debian.org/support) 
[   916.620] Current version of pixman: 0.34.0
[   916.620] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   916.620] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   916.620] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 10 16:52:32 2016
[   916.620] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   916.621] (==) No Layout section.  Using the first Screen section.
[   916.621] (==) No screen section available. Using defaults.
[   916.621] (**) |-->Screen "Default Screen Section" (0)
[   916.621] (**) |   |-->Monitor ""
[   916.621] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   916.621] (==) Automatically adding devices
[   916.621] (==) Automatically enabling devices
[   916.621] (==) Automatically adding GPU devices
[   916.621] (==) Max clients allowed: 256, resource mask: 0x1f
[   916.621] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   916.621] 	Entry deleted from font path.
[   916.621] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[   916.621] (==) ModulePath set to "/usr/lib/xorg/modules"
[   916.621] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   916.621] (II) Loader magic: 0x55face61cdc0
[   916.621] (II) Module ABI versions:
[   916.621] 	X.Org ANSI C Emulation: 0.4
[   916.621] 	X.Org Video Driver: 20.0
[   916.621] 	X.Org XInput driver : 22.1
[   916.621] 	X.Org Server Extension : 9.0
[   916.623] (++) using VT number 8

[   916.623] 

Bug#840349: intel-cmt-cat: please enable building of shared library

[Marc Fournier]

Package: intel-cmt-cat
Version: 0.1.5-1
Severity: important

Dear Maintainer,

Current version of intel-cmt-cat doesn't provide the shared library
(/usr/lib/libpqos.so) which is required to link against it.

For example, running "gcc -lpqos ..." fails with:
  relocation R_X86_64_PC32 against undefined symbol `stderr@@GLIBC_2.2.5' can 
not be used when making a shared object; recompile with -fPIC

When rebuilding the intel-cmt-cat package after setting:
  export SHARED=y
in debian/rules, linking against libpqos works just fine, and the
resulting binary runs as expected.

Thanks !

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'stable'), (500, 'oldstable'), (300, 
'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages intel-cmt-cat depends on:
ii  libc6  2.24-3

intel-cmt-cat recommends no packages.

intel-cmt-cat suggests no packages.

-- no debconf information

Bug#840342: [ace-of-penguins] Freecell No Longer Runs, Nvidia Legacy-304xx video driver

[Markus Koschany]

On 10.10.2016 21:28, David Baron wrote:
> On יום שני, 10 באוקטובר 2016 20:42:25 IDT Markus Koschany wrote:
>> Control: tags -1 moreinfo
>>
>> On 10.10.2016 20:34, David Baron wrote:
>>> Package: ace-of-penguins
>>> Version: 1.5~rc2-1+b1
>>> Severity: normal
>>>
>>> --- Please enter the report below this line. ---
>>> After upgrade of the Nvidia Legacy 304xx driver (contrib), Freecell no
>>> longer runs:
>>> ~$ ace-freecell
>>> X Error of failed request:  BadMatch (invalid parameter attributes)
>>>
>>>   Major opcode of failed request:  73 (X_GetImage)
>>>   Serial number of failed request:  25
>>>   Current serial number in output stream:  25
>>
>> [...]
>>
>> Hello,
>>
>> what makes you think that this is a bug in ace-of-penguins? Did you try
>> to downgrade your Nvidia drivers? What was the outcome? Are you able to
>> play the game with the free xserver-xorg-video-nouveau drivers?
>>
>> Markus
> 
> Program did run using nouveau but nouveau and KDE/Plasma desktop do not mix. 
> So have not played it using nouveau in recent memory.
> It is no longer possible to downgrade to the testing version of the nvidia.
> 
> If other programs fail with the same error, then the point is well made.
> If this is unique here, then something in the ace "backend" might be examined.


The error message indicates a bug or incompatibility between your X
environment / X server and the proprietary Nvidia driver. This is a low
level error and not related to ace-of-penguins which only requires a 2D
capable graphics card. Everything from the past 20 years should work.

If the game works with nouveau it is most likely a bug in the non-free
driver. Since the source code is closed it is not possible for Debian to
work on a fix. The game works flawlessly on my system by the way.

Please note that you can download an earlier version of the Nvidia
driver from snapshots.debian.org.

I am inclined to reassign this issue to
xserver-xorg-video-nvidia-legacy-304xx. Please confirm this is the
package you are currently using.

I am sure the maintainers of xserver-xorg-video-nvidia-legacy-304xx
would be interested in your /var/log/Xorg.* log file because it provides
a more detailed error report. Please attach this file to the bug report.

Regards,

Markus





signature.asc
Description: OpenPGP digital signature

Bug#802528: Fixed if VALAC is not needed?

[Daniel Espinosa]

For Vala projects, is possible to distribute C source code then is not
necessary to have installed Vala's compiler to create binaries versions.

Now, if a Vala project doesn't distribute its C, GIR and/or VAPI generated
files, then you need VALAC.

Then is the project distribute all its generated files and build process,
don't required to call VALAC at all, this bug can be dismissed and filed
one against the project's upstream.

Is this correct?


-- 
This electronic message may contain privileged and confidential information
intended only for the use of the addressees named above.  If you are not
the intended recipient of this email, we kindly ask you to delete this
message and any attachment. You are hereby notified that any use,
dissemination, distribution, reproduction of this email is prohibited.  If
you have received this email in error, please notify sender immediately.

Any document, image or any other form of electronic representation of any
work attached to this email, is suitable to be protected by copyright
enforcement by applicable law in your or sender's Country's and
International Legislation

Trabajar, la mejor arma para tu superación
"de grano en grano, se hace la arena" (R) (en trámite, pero para los
cuates: LIBRE)

Bug#840202: Seems to be somehow fixed

[Jonas Baggett]

Hello,

I have found that the texlive-fonts-recommended package has also some 
marvosym related files :
texlive-fonts-recommended: 
/usr/share/texlive/texmf-dist/fonts/afm/public/marvosym/marvosym.afm
texlive-fonts-recommended: 
/usr/share/texlive/texmf-dist/fonts/map/dvips/marvosym/marvosym.map
texlive-fonts-recommended: 
/usr/share/texlive/texmf-dist/fonts/tfm/public/marvosym/umvs.tfm
texlive-fonts-recommended: 
/usr/share/texlive/texmf-dist/fonts/type1/public/marvosym/marvosym.pfb
texlive-fonts-recommended: 
/usr/share/texlive/texmf-dist/tex/latex/marvosym/marvosym.sty
texlive-fonts-recommended: 
/usr/share/texlive/texmf-dist/tex/latex/marvosym/umvs.fd


I removed this package and it works ! It still works after reinstalling 
this package and removing the cache. I have tried different ways to 
reproduce the bug with no success. Then I believe it can be closed.


Cheers,
Jonas

Bug#839991: [pkg-gnupg-maint] Bug#839991: gnupg-agent: 'allow-emacs-pinentry' setting in agent conf makes gpg2 respond no secret key

[Werner Koch]

On Mon, 10 Oct 2016 10:39, u...@gnu.org said:

> That makes sense.  How about this trivial patch?

Fine.  Justus, can you please apply it?


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgpUGWaP6ONgY.pgp
Description: PGP signature

Bug#840193: liferea: Notification icon doesn't work for hide.

[Paul Gevers]

control: forwarded -1 https://github.com/lwindolf/liferea/issues/410

On 10-10-16 21:05, Sven Hartge wrote:
> This does not change anything for me.
> 
> I can right-click the icon and click the "Show / Hide" menu option and it 
> does what it is supposed to do: hiding the window if shown, show the 
> window if hidden, but left-clicking the icon only ever shows the window 
> but does not hide it.

Thanks for the feed-back. I have reported this upstream (and added my
own (different) experience (on KDE).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#840347: CVE-2016-4429

[Moritz Muehlenhoff]

Source: libtirpc
Severity: grave
Tags: security

libtirpc is affected by this vulnerability recently fixed in glibc:
https://security-tracker.debian.org/tracker/CVE-2016-4429

Cheers,
Moritz

Bug#840342: [ace-of-penguins] Freecell No Longer Runs, Nvidia Legacy-304xx video driver

[David Baron]

On יום שני, 10 באוקטובר 2016 20:42:25 IDT Markus Koschany wrote:
> Control: tags -1 moreinfo
> 
> On 10.10.2016 20:34, David Baron wrote:
> > Package: ace-of-penguins
> > Version: 1.5~rc2-1+b1
> > Severity: normal
> > 
> > --- Please enter the report below this line. ---
> > After upgrade of the Nvidia Legacy 304xx driver (contrib), Freecell no
> > longer runs:
> > ~$ ace-freecell
> > X Error of failed request:  BadMatch (invalid parameter attributes)
> > 
> >   Major opcode of failed request:  73 (X_GetImage)
> >   Serial number of failed request:  25
> >   Current serial number in output stream:  25
> 
> [...]
> 
> Hello,
> 
> what makes you think that this is a bug in ace-of-penguins? Did you try
> to downgrade your Nvidia drivers? What was the outcome? Are you able to
> play the game with the free xserver-xorg-video-nouveau drivers?
> 
> Markus

Program did run using nouveau but nouveau and KDE/Plasma desktop do not mix. 
So have not played it using nouveau in recent memory.
It is no longer possible to downgrade to the testing version of the nvidia.

If other programs fail with the same error, then the point is well made.
If this is unique here, then something in the ace "backend" might be examined.

Bug#840330: [Build-common-hackers] Bug#840330: cdbs: licensecheck runs twice during build

[Jérémy Lal]

2016-10-10 20:59 GMT+02:00 Jonas Smedegaard :

> Quoting Jérémy Lal (2016-10-10 18:51:53)
> > cdbs runs licensecheck two times during build:
> > https://buildd.debian.org/status/fetch.php?pkg=nodejs;
> arch=mips64el=4.6.0~dfsg-1=1476084143
>
> Thanks for reporting.  I was aware of that but hadn't reported it.
>
>
> > and it crashes too.
>
> That's a different and more serious bug.  Please file a bugreport
> separately about that, with more details.
>

ok, bad wording on my side: it doesn't crash, the build is killed after 150
minutes
of inactivity. Probably because licensecheck has to analyze a lot more
binary
files because of this bug - that's fair so i won't open a new bug.

> Is there some way to avoid completely running licensecheck when
> > building on sbuild. It's a ressource hog and discutably useful.
>
> Avoid build-depending on licensecheck should do the trick.
>

Well, that would be caused by
Build-Depends: @cdbs@

which gives
Build-Depends: cdbs,
 licensecheck,

after refreshing control file with
DEB_MAINTAINER_MODE=1 debuild clean

?

Jérémy.

Bug#824155: IoTivity

[Philippe Coval]

- Original Message -
> From: "Thorsten Alteholz" 
> To: "Philippe Coval" 
> Cc: 824...@bugs.debian.org
> Sent: Monday, October 10, 2016 8:19:11 PM
> Subject: IoTivity
> 
> Hi Philippe,
> 
> I am trying to start a new debian-iot team within Debian. Up to know
> the libcoap package and some packages of the Alljoyn Framework are
> part of
> it. As the latter also uses scons, I have some experience with it,
> albeit
> I am far from being an expert.
> So if you want to join the team with your iotivity package, I would
> start
> to create the repositories on alioth ...
> 
>Thorsten

Sure that's a great idea, you can add rzr-guest to the alioth team

Today I am building snapshots versions in ppa, but that's unfit for debian 
standards..

Let's wait 1.2.0 to be released first
or patch this branch:

https://github.com/TizenTeam/iotivity/tree/sandbox/pcoval/on/latest/debian

Regards