Bug#860515: Many translations missing in french KDE lang packages while we're close to release

2017-04-17 Thread Julien Aubin 
Package: kde-l10n-fr
Version: 4:16.04.3-1
Severity: grave

Hi,

I know that the severity is exagerated but this is because we're very close
to
release and the issue is still not fixed.

There are still many missing translations in French KDE translation package,
such as many "Apply" buttons left untranslated, some "do you want to
continue"
questions untranslated and so on. The issue is due to some translations in
Debian being too old, as the same package, kde-l10n-fr 16.04 in Gentoo is
not
affected.

So could you please upload newer translations for KDE before release ? It's
a
matter of how the UX looks in front of the user.

Thanks



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

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

Versions of packages kde-l10n-fr depends on:
ii  libkdecore5  4:4.14.26-1
ii  libkf5i18n5  5.28.0-2

kde-l10n-fr recommends no packages.

Versions of packages kde-l10n-fr suggests:
ii  kde-standard  5:92

-- no debconf information

Bug#859926: speechd-up: fails to install

2017-04-17 Thread Cindy-Sue Causey 
On 4/17/17, MENGUAL Jean-Philippe  wrote:
> Hi,
>
> We're going to have a look, but here I cannot reproduce. On Stretch, I
> install the package without problems. So I am surprised. I may have
> systemd-sysv, indeed, but not much more.
>

Hi.. I follow accessibility lists and thought I recognized this as a
topic of theirs so I'm "playing along" to finally learn a little more
about it.

I was able to install speechd-up successfully, BUT I have no idea if
it's functional because I don't know how to use it.

I'm on a super basic debootstrap'ed Stretch with Xfce4 as my primary
desktop environment. I've got Fluxbox and something else small that
I've forgotten because I haven't switched around between them in a
while.

All of this is being provided in case it somehow helps explain why
it's working for some of us and not for others.

About the only programs I have are: Libreoffice, GIMP, Inkscape,
Openshot, newly installed Piviti, Xine, and PySolFC (card games).

For sound, aumix is my hero because I went almost a year without sound
until I discovered that package. Others installed include GNOME ALSA
mixer, Qas mixer, mpv video player. Seriously, I was desperate and
downloading things that even remotely sounded like they might help
trigger sound back on.

Again, am mentioning all those because maybe they did something that
triggered at least a successful install. Whether it actually works as
intended or not, I have no clue aka literally clueless.

As for systemd, I haven't touched a thing there. My system is whatever
comes with a debootstrap install.

I'm on a now older ASUS 10" where "uname -a" gets: Linux northpole
4.9.0-1-amd64 #1 SMP Debian 4.9.2-2 (2017-01-12) x86_64 GNU/Linux

That's all I can think to write right now. :)


> Le 16/04/2017 à 22:17, Paul Gevers a écrit :
>> Hi
>>
>> On 16-04-17 21:51, Paul Gevers wrote:
>>> I haven't figured out the difference yet.
>>
>> Probably somebody who knows systemd should have a look. I have the
>> feeling it is interfering with the script and not doing what I read.
>>
>> I have no clue where to find the input (the service file?) that systemd
>> is actually using yet. This is all new to me.


#ThankYou for the work you all do!

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Bug#858876: libjna-jni: causes NoClassDefFoundError

2017-04-17 Thread Emmanuel Bourg 
Le 17/04/2017 à 17:45, YOSHINO Yoshihito a écrit :

> I have upgraded this package, while this error still persists.
> Exactly the same error message appears in the netbeans log.
> Creating the symlink works around this error.

Thank you for the feedback. That's odd because the renamed path of the
library is now hardcoded and can't be changed by a system property.
Creating a symlink should have no effect. Could this be caused by an
embedded jar in netbeans ?

Emmanuel Bourg

Bug#858876: libjna-jni: causes NoClassDefFoundError

2017-04-17 Thread Emmanuel Bourg 
Le 17/04/2017 à 23:55, Markus Koschany a écrit :

> I'm quite sure that we don't use an embedded jar of JNA somewhere in
> Netbeans.

Could you try removing the jna jar manually from /usr/share/java to
confirm that?


> I suspect that Netbeans' System.setProperty does something differently
> and not what we expect or the patch for libjna-jni was incomplete.

I'll get another look.

Bug#858876: libjna-jni: causes NoClassDefFoundError

2017-04-17 Thread Markus Koschany 
Am 17.04.2017 um 21:08 schrieb Emmanuel Bourg:
> Le 17/04/2017 à 17:45, YOSHINO Yoshihito a écrit :
> 
>> I have upgraded this package, while this error still persists.
>> Exactly the same error message appears in the netbeans log.
>> Creating the symlink works around this error.
> 
> Thank you for the feedback. That's odd because the renamed path of the
> library is now hardcoded and can't be changed by a system property.
> Creating a symlink should have no effect. Could this be caused by an
> embedded jar in netbeans ?

I can confirm that I see the same error message in the messages.log
file. When I change the following line in my patch from:

System.setProperty( "jna.boot.library.name", "jnidispatch" );

to

System.setProperty( "jna.boot.library.name", "jnidispatch.system" );

the INFO warning in the log file is gone.

I'm quite sure that we don't use an embedded jar of JNA somewhere in
Netbeans. I removed everything when I repacked the tarball. I also had
to make sure to patch libs.jna/nbproject/project.properties, so that the
build system doesn't try to install those external non-existent JNA
jars, otherwise the build would have failed.

I suspect that Netbeans' System.setProperty does something differently
and not what we expect or the patch for libjna-jni was incomplete.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#860489: apache-log4j2: CVE-2017-5645: socket receiver deserialization vulnerability

2017-04-17 Thread Salvatore Bonaccorso 
Source: apache-log4j2
Version: 2.0~beta9-1
Severity: grave
Tags: security upstream
Forwarded: https://issues.apache.org/jira/browse/LOG4J2-1863

Hi,

the following vulnerability was published for apache-log4j2.

CVE-2017-5645[0]:
Apache Log4j socket receiver deserialization vulnerability

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

This one might warrant a DSA, but please check back with
t...@security.debian.org .

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-5645
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645
[1] https://issues.apache.org/jira/browse/LOG4J2-1863

Regards,
Salvatore

Bug#805370: mpage licensing

2017-04-17 Thread Paul Gevers 
Ping...

As a QA maintained package which is not going into the upcoming release
with a license issue open for 1.5 years, shouldn't this package be
removed from Debian?

Paul



signature.asc
Description: OpenPGP digital signature

Processed: Bug#778720: bind9: hangs / crashes on mips after some time (Was: Bug#839010: bug still there in jessie (mips))

2017-04-17 Thread Debian Bug Tracking System 
Processing control commands:

> retitle -1 bind9: hangs / crashes on mips after some time
Bug #778720 [bind9] bind9: hangs on mips jessie based machine
Changed Bug title to 'bind9: hangs / crashes on mips after some time' from 
'bind9: hangs on mips jessie based machine'.
> severity -1 grave
Bug #778720 [bind9] bind9: hangs / crashes on mips after some time
Severity set to 'grave' from 'important'

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

Processed: tag 856487 patch

2017-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 856487 patch
Bug #856487 [libsbc1] libsbc1: compiling with gcc > 4.9 causes stack corruption
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#856024: armhf bootstrap + molly-guard

2017-04-17 Thread Jonas Smedegaard 
Quoting Tim Retout (2017-04-17 19:22:15)
> Would you be able to supply more info about your armhf bootstrap in 
> #856024?
> 
> I've tried to reproduce the issue today (albeit on amd64) and I'm not 
> having much luck.
> 
> The original error message suggests to me that molly-guard's 
> dpkg-divert must have failed previously somehow (?), because 
> systemd-sysv should not otherwise complain that molly-guard installed 
> /sbin/halt.  I'm wondering if there's something specific to armhf 
> (seems unlikely) or the particular bootstrap process.

Not sure what info you need that was not in the original report.

Recent attempts at replicating seems to not use real hardware, which I 
suspect is more important than whether it is the same architecture, for 
a bug involving hijacking files from an init-related package.

I don't recall, but believe I installed using plain standard 
debian-installer with the "netboot" image.  But possibly I might have 
used multistrap, which means the order of installing the various 
packages may be different from (c)debootrap-based installs.  Something 
that is *not* a bug in multistrap - Debian Policy mandates package 
relations but no specific install order.


 - 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

Processed: [bts-link] source package src:chaussette

2017-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:chaussette
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #855671 (http://bugs.debian.org/855671)
> # Bug title: FTBFS: chaussette incompatible with waitress 1.0, tests fail
> #  * https://github.com/circus-tent/chaussette/issues/82
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 855671 + fixed-upstream
Bug #855671 [src:chaussette] FTBFS: chaussette incompatible with waitress 1.0, 
tests fail
Added tag(s) fixed-upstream.
> usertags 855671 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 855671 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#856024: armhf bootstrap + molly-guard

2017-04-17 Thread Tim Retout 
Hi Jonas,

Would you be able to supply more info about your armhf bootstrap in #856024?

I've tried to reproduce the issue today (albeit on amd64) and I'm not
having much luck.

The original error message suggests to me that molly-guard's
dpkg-divert must have failed previously somehow (?), because
systemd-sysv should not otherwise complain that molly-guard installed
/sbin/halt.  I'm wondering if there's something specific to armhf
(seems unlikely) or the particular bootstrap process.

Kind regards,

-- 
Tim Retout

Bug#860483: [node-minimalistic-assert] Could be replaced by node-assert

2017-04-17 Thread Bastien ROUCARIÈS 
Package: node-minimalistic-assert
Severity: serious

This is only two function of node-assert..

This module is compatible with node-assert.

so nuke it before it go to release

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

Processed: severity of 860426 is serious

2017-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 860426 serious
Bug #860426 [urweb] Urweb package has missing runtime dependency on gcc.
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#860393: Segfaults on startup

2017-04-17 Thread Bernhard Übelacker 
Hello,
just tried if I can reproduce the issue.

I think this is a again a case of a pointer truncation by default
int for a pointer returning function.


First patch is just to build with debug information to make the
automatic dbgsym packages helpful.

The second patch adds some includes to get prototypes for alloc function.
This is also warned about in the current amd64 build log:
../win/proxy/nhext.c:36:39: warning: implicit declaration of function 'alloc' 
[-Wimplicit-function-declaration]
 nhext_connection.in = (NhExtXdr *)alloc(sizeof(NhExtXdr));
   ^

The third patch adds the prototype into a header file for nh_option_get_boolopt.

With these applied at least the user interface can start without crashing.
The build shows another 58 "warning: implicit declaration of function", that
may crash later.

Kind regards,
Bernhard
From b173980b4d068ddee3074c7dc89d7f4e465ecb76 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?= 
Date: Mon, 17 Apr 2017 16:35:55 +0200
Subject: Compile with debug information to make dbgsym package useful.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860393
---
 sys/unix/Makefile.src | 4 ++--
 sys/unix/Makefile.utl | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/sys/unix/Makefile.src b/sys/unix/Makefile.src
index 9d657a5..05528ba 100644
--- a/sys/unix/Makefile.src
+++ b/sys/unix/Makefile.src
@@ -129,9 +129,9 @@ SYSOBJ = ioctl.o unixmain.o unixtty.o unixunix.o unixres.o
 #   compile normally
 #   disable optimization on non-Linux archs due to FTBFS
 ifeq ($(UNAME),Linux)
-CFLAGS = -DDEBIAN_$(GUI) -O2 -fomit-frame-pointer -fstack-protector --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include
+CFLAGS = -DDEBIAN_$(GUI) -g -O2 -fomit-frame-pointer -fstack-protector --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include
 else
-CFLAGS = -DDEBIAN_$(GUI) -fstack-protector --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include
+CFLAGS = -DDEBIAN_$(GUI) -g -fstack-protector --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include
 endif
 LFLAGS = -L/usr/X11R6/lib -Wl,-z,relro
 #   OR compile backwards compatible a.out format
diff --git a/sys/unix/Makefile.utl b/sys/unix/Makefile.utl
index b253b5d..e34d711 100644
--- a/sys/unix/Makefile.utl
+++ b/sys/unix/Makefile.utl
@@ -77,9 +77,9 @@ UNAME := $(shell uname -s)
 #   compile normally
 #   disable optimization on non-Linux archs due to FTBFS
 ifeq ($(UNAME),Linux)
-CFLAGS = -DDEBIAN_$(GUI) -O2 -fomit-frame-pointer -fstack-protector --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include
+CFLAGS = -DDEBIAN_$(GUI) -g -O2 -fomit-frame-pointer -fstack-protector --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include
 else
-CFLAGS = -DDEBIAN_$(GUI) -fstack-protector --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include
+CFLAGS = -DDEBIAN_$(GUI) -g -fstack-protector --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include
 endif
 LFLAGS = -L/usr/X11R6/lib -Wl,-z,relro
 #   OR compile backwards compatible a.out format
-- 
2.11.0

From 388d1b18a6a90fb3495d77b75acac9d73cdbcc0c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?= 
Date: Mon, 17 Apr 2017 17:33:13 +0200
Subject: Avoid pointer truncation because of default int return type for
 alloc.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This patch add includes for config.h that includes global.h that has
the prototype for alloc function.

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


$ gdb -q --args slashem-gtk

Program received signal SIGSEGV, Segmentation fault.
nhext_xdrio_create (xdrs=0x5054a740, io=io@entry=0x563550549ea0, op=op@entry=NHEXT_XDR_DECODE) at ../win/proxy/nhxdr.c:232
232 xdrs->x_data = io;
(gdb) bt
#0  0x56354f7ac0c7 in nhext_xdrio_create (xdrs=0x5054a740, io=io@entry=0x563550549ea0, op=op@entry=NHEXT_XDR_DECODE)
at ../win/proxy/nhxdr.c:232
#1  0x56354f7aa793 in nhext_init (rd=rd@entry=0x563550549ea0, wr=wr@entry=0x56355054a2f0, cb=0x56354fa516e0 )
at ../win/proxy/nhext.c:38
#2  0x56354f7a5dcc in proxy_init (auth=0x0) at ../win/proxy/winproxy.c:1295
#3  0x56354f7a5dcc in win_proxy_init () at ../win/proxy/winproxy.c:1515
#4  0x56354f7a2f54 in GTK_proxy_init_nhwindows (argcp=0x7fff4f9d5f8c, argv=0x7fff4f9d60a8) at ../win/gtk/gtkint.c:185
#5  0x56354f6042c7 in main (argc=, argv=0x7fff4f9d60a8) at ../sys/unix/unixmain.c:139


cc -DDEBIAN_GTK -g -O2 -fomit-frame-pointer -fstack-protector --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include -c ../win/proxy/nhext.c
../win/proxy/nhext.c: In function ‘nhext_init’:
../win/proxy/nhext.c:38:39: warning: implicit declaration of function ‘alloc’ [-Wimplicit-function-declaration]
 nhext_connection.in = (NhExtXdr *)alloc(sizeof(NhExtXdr));
   ^
---
 win/proxy/nhext.c| 1 +
 win/proxy/proxycb.c  | 1 +
 win/proxy/proxysvc.c | 1 +
 win/proxy/prxych

Bug#860479: openvswitch-datapath-dkms (and openvswitch-datapath-source) fail compiling on fresh install of 7.11

2017-04-17 Thread Bogdan Ilisei 
Package: openvswitch-datapath-dkms
Version: 1.4.2+git20120612-9.1~deb7u1.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Installing openvswitch-datapath-dkms (OR openvswitch-datapath-source) is
currently broken in Wheezy 7.11.

I have tested both on a fresh install and an upgraded (from 7.8 to 7.11)
install.

The issue seems present in "datapath/linux/tunnel.c":

/var/lib/dkms/openvswitch/1.4.2+git20120612/build/datapath/linux/tunnel.c:
In function ‘ecn_decapsulate’:
/var/lib/dkms/openvswitch/1.4.2+git20120612/build/datapath/linux/tunnel.c:395:4:
warning: passing argument 1 of ‘IP6_ECN_set_ce’ from incompatible pointer
type [enabled by default]
/usr/src/linux-headers-3.2.0-4-common/include/net/inet_ecn.h:118:19: note:
expected ‘struct sk_buff *’ but argument is of type ‘struct ipv6hdr *’
/var/lib/dkms/openvswitch/1.4.2+git20120612/build/datapath/linux/tunnel.c:395:4:
error: too few arguments to function ‘IP6_ECN_set_ce’
/usr/src/linux-headers-3.2.0-4-common/include/net/inet_ecn.h:118:19: note:
declared here
/var/lib/dkms/openvswitch/1.4.2+git20120612/build/datapath/linux/tunnel.c:
In function ‘ovs_tnl_send’:
/var/lib/dkms/openvswitch/1.4.2+git20120612/build/datapath/linux/tunnel.c:1304:3:
warning: passing argument 2 of ‘ip_select_ident’ from incompatible pointer
type [enabled by default]
/usr/src/linux-headers-3.2.0-4-common/include/net/ip.h:293:20: note:
expected ‘struct sock *’ but argument is of type ‘struct dst_entry *’
make[4]: ***
[/var/lib/dkms/openvswitch/1.4.2+git20120612/build/datapath/linux/tunnel.o]
Error 1
make[3]: ***
[_module_/var/lib/dkms/openvswitch/1.4.2+git20120612/build/datapath/linux]
Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64'
make: *** [default] Error 2
make: Leaving directory
`/var/lib/dkms/openvswitch/1.4.2+git20120612/build/datapath/linux'

Both "dkms autoinstal" and "m-a -t a-i openvswitch-datapath" fail on the
same issue.

Removing the ipv6-related code between

  #if defined(CONFIG_IPV6) || defined(CONFIG_IPV6_MODULE)

and

  #endif

allows the module to be built without errors, but obviously with broken
ipv6 support.

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

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

Versions of packages openvswitch-datapath-dkms depends on:
ii  dkms   2.2.0.3-1.2
ii  libc6-dev  2.13-38+deb7u11
ii  make   3.81-8.2

openvswitch-datapath-dkms recommends no packages.

openvswitch-datapath-dkms suggests no packages.

-- no debconf information

Bug#856487: libsbc1: compiling with gcc > 4.9 causes stack corruption

2017-04-17 Thread Paul Brook 
Package: libsbc1
Version: 1.3-1+b2
Followup-For: Bug #856487

Not a stack corruption.

This is miscompilation of sbc_analyze_4b_8s_armv6.  gcc appears to look
into the asm function and decides that it does not clobber r3 (which the
normal ARM ABI says is call clobbered).  The last out += out_stride ends
up incrementing the pointer by an arbitrary amount.

The attached patch works around the bug.

I'm not entirely sure whether this is a gcc bug or not, but at best it's
surprising behavior from gcc.  I've attached a reduced testcase for the 
toolchain
folks to argue over (compile with gcc -O2, tested with gcc 6.3.0-2 from
sid).

Paul

diff -ur clean/sbc/sbc_primitives_armv6.c sbc-1.3/sbc/sbc_primitives_armv6.c
--- clean/sbc/sbc_primitives_armv6.c2013-04-30 17:19:23.0 +0100
+++ sbc-1.3/sbc/sbc_primitives_armv6.c  2017-04-17 16:43:49.918809345 +0100
@@ -102,6 +102,7 @@
"pop{r8-r11}\n"
"stmia  r1, {r4, r5, r6, r7}\n"
"pop{r1, r4-r7, pc}\n"
+:::"r0", "r2", "r3", "ip"
);
 }
 
@@ -258,6 +259,7 @@
"pop{r8-r11}\n"
"stmia  r1!, {r4, r5, r6, r7}\n"
"pop{r1, r4-r7, pc}\n"
+:::"r0", "r2", "r3", "ip"
);
 }
 
/* Compile with -O2 on arm */
#include 
#include 

static void __attribute__((naked)) frob(int16_t *a, int32_t *b, const int16_t 
*c)
{
/* The explicit clobber of r3 should not be necessary because that it 
is implied by the function call?
   gcc6 seems to look into the naked function and assume r3 is 
preserved accross the call.  */
__asm__ volatile ("mov r3, #0x8000\n\t"
"str r3, [r1]\n\t"
"bx lr"
#if 0
:::"r3"
#endif
);
}

int16_t c[4];
struct sbc_encoder_state;

void test(struct sbc_encoder_state *state,
int16_t *x, int32_t *out, int out_stride)
{
frob(x + 24, out, c);
out += out_stride;
frob(x + 16, out, c);
out += out_stride;
frob(x + 8, out, c);
out += out_stride;
frob(x + 0, out, c);
}

int main()
{
static int16_t a[32];
static int32_t b[32];
test(NULL, a, b, 8);
return 0;
}

Bug#860440: marked as done (UEFI build will break UEFI boot on the build host)

2017-04-17 Thread Debian Bug Tracking System 
Your message dated Mon, 17 Apr 2017 15:49:07 +
with message-id 
and subject line Bug#860440: fixed in openstack-debian-images 1.19
has caused the Debian Bug report #860440,
regarding UEFI build will break UEFI boot on the build host
to be marked as done.

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

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


-- 
860440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openstack-debian-images
Version: 1.14
Severity: serious
Tags: patch

Hi,

Just found and debugged this when integrating the arm64 build on
pettersson. The call to grub-install in the chroot is updating the
UEFI boot variables on the host, breaking its boot setup. Simple patch
makes all the difference.

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

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

Versions of packages openstack-debian-images depends on:
ii  debootstrap  1.0.67
ii  extlinux 3:6.03+dfsg-5+deb8u1
ii  initramfs-tools  0.120+deb8u2
ii  kpartx   0.5.0-6+deb8u2
ii  mbr  1.1.11-5+b1
ii  parted   3.2-7
ii  qemu-utils   1:2.1+dfsg-12+deb8u6

openstack-debian-images recommends no packages.

openstack-debian-images suggests no packages.

-- no debconf information
>From 12c5e3a7de103e6cb73235cff6d11180a225c98c Mon Sep 17 00:00:00 2001
From: Steve McIntyre 
Date: Sun, 16 Apr 2017 22:37:32 +0100
Subject: [PATCH] Add --no-nvram to the grub-install command line

On a UEFI build on a UEFI-using host, this will otherwise modify the
UEFI variables on the host. We don't want that!
---
 build-openstack-debian-image | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/build-openstack-debian-image b/build-openstack-debian-image
index fc405a2..3a8d7d6 100755
--- a/build-openstack-debian-image
+++ b/build-openstack-debian-image
@@ -608,7 +608,7 @@ GRUB_DISABLE_OS_PROBER=true" >>${MOUNT_DIR}/etc/default/grub
 	echo "grub-efi-${ARCH} grub2/force_efi_extra_removable boolean true" | chroot ${MOUNT_DIR} debconf-set-selections
 	chroot ${MOUNT_DIR} grub-mkconfig -o /boot/grub/grub.cfg
 	# Run grub from the chroot, pointing to the bind mounted /dev device.
-	chroot ${MOUNT_DIR} grub-install --target=${GRUB_TARGET} --force-extra-removable --no-floppy --modules="part_msdos part_gpt" --grub-mkdevicemap=/boot/grub/device.map /dev/${LOOPRAW_DEVICE}
+	chroot ${MOUNT_DIR} grub-install --target=${GRUB_TARGET} --no-nvram --force-extra-removable --no-floppy --modules="part_msdos part_gpt" --grub-mkdevicemap=/boot/grub/device.map /dev/${LOOPRAW_DEVICE}
 	# Run grub from the host, pointing to the guest installation
 	#grub-install --no-floppy --modules=part_msdos --grub-mkdevicemap=${MOUNT_DIR}/boot/grub/device.map --root-directory=${MOUNT_DIR} /dev/${LOOPRAW_DEVICE}
 	umount ${MOUNT_DIR}/sys
-- 
2.1.4

--- End Message ---
--- Begin Message ---
Source: openstack-debian-images
Source-Version: 1.19

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated openstack-debian-images 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Apr 2017 17:27:15 +0200
Source: openstack-debian-images
Binary: openstack-debian-images
Architecture: source amd64
Version: 1.19
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 openstack-debian-images - script to build a Debian image for OpenStack
Closes: 860440
Changes:
 openstack-debian-images (1.19) unstable; urgency=medium
 .
   * Add --no-nvram when calling grub-install to avoid breaking UEFI boot on the
 build host (Closes: #860440). Thanks to Steve McIntyre for reporting and
 patch.
Checksums-Sha1:
 7bb8ad7ae44

Processed: Re: libjna-jni: causes NoClassDefFoundError

2017-04-17 Thread Debian Bug Tracking System 
Processing control commands:

> reopen -1
Bug #858876 {Done: Emmanuel Bourg } [libjna-jni] libjna-jni: 
causes NoClassDefFoundError
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libjna-java/4.2.2-3.

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

Bug#858876: libjna-jni: causes NoClassDefFoundError

2017-04-17 Thread YOSHINO Yoshihito 
Package: libjna-jni
Followup-For: Bug #858876
Control: reopen -1

Dear Maintainer,

Sorry for the delay.

I have upgraded this package, while this error still persists.
Exactly the same error message appears in the netbeans log.
Creating the symlink works around this error.

Regards,
-- 
YOSHINO Yoshihito

Processed: Bug#860440 marked as pending

2017-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tag 860440 pending
Bug #860440 [openstack-debian-images] UEFI build will break UEFI boot on the 
build host
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#860440: marked as pending

2017-04-17 Thread Thomas Goirand 
tag 860440 pending
thanks

Hello,

Bug #860440 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/openstack/openstack-debian-images.git/commit/?id=f70559e

---
commit f70559e0469fddb78aa5df7bbcac7c7d44b8e0bd
Author: Thomas Goirand 
Date:   Mon Apr 17 17:31:41 2017 +0200

  * Add --no-nvram when calling grub-install to avoid breaking UEFI boot on 
the
build host (Closes: #860440). Thanks to Steve McIntyre for reporting and
patch.

diff --git a/debian/changelog b/debian/changelog
index 988513b..5008751 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+openstack-debian-images (1.19) unstable; urgency=medium
+
+  * Add --no-nvram when calling grub-install to avoid breaking UEFI boot on the
+build host (Closes: #860440). Thanks to Steve McIntyre for reporting and
+patch.
+
+ -- Thomas Goirand   Mon, 17 Apr 2017 17:27:15 +0200
+
 openstack-debian-images (1.18) unstable; urgency=medium
 
   * Add more protocols to the default datasource_list.

Bug#855920: marked as done (fail2ban: FTBFS: test_rewrite_file: AssertionError: False is not true)

2017-04-17 Thread Debian Bug Tracking System 
Your message dated Mon, 17 Apr 2017 15:18:50 +
with message-id 
and subject line Bug#855920: fixed in fail2ban 0.9.6-2
has caused the Debian Bug report #855920,
regarding fail2ban: FTBFS: test_rewrite_file: AssertionError: False is not true
to be marked as done.

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

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


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

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> 
> ==
> FAIL: test_rewrite_file 
> (fail2ban.tests.filtertestcase.get_monitor_failures_testcase..MonitorFailures)
> --
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/pythonX.Y_3.5/build/fail2ban/tests/filtertestcase.py",
>  line 605, in test_rewrite_file
> self.assert_correct_last_attempt(GetFailures.FAILURES_01)
>   File 
> "/<>/.pybuild/pythonX.Y_3.5/build/fail2ban/tests/filtertestcase.py",
>  line 569, in assert_correct_last_attempt
> self.assertTrue(self.isFilled(20)) # give Filter a chance to react
> AssertionError: False is not true
> 
> --
> Ran 268 tests in 262.422s
> 
> FAILED (failures=31, errors=2, skipped=4)
> debian/rules:54: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/02/21/fail2ban_0.9.6-1_testing.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated fail2ban 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Apr 2017 10:27:28 -0400
Source: fail2ban
Binary: fail2ban
Architecture: source all
Version: 0.9.6-2
Distribution: unstable
Urgency: medium
Maintainer: Yaroslav Halchenko 
Changed-By: Yaroslav Halchenko 
Description:
 fail2ban   - ban hosts that cause multiple authentication errors
Closes: 855920
Changes:
 fail2ban (0.9.6-2) unstable; urgency=medium
 .
   * debian/patches/changeset_a639f0b083c213bde4ff3dcfbbb9fbcab0dd55f8.diff
 to resolve occasional FTBFSs if tzdata is not available (Closes: #855920)
Checksums-Sha1:
 a2559f202505c9879096955affa1ef36d211ebfb 1843 fail2ban_0.9.6-2.dsc
 1d89b42e7f074b5cad0faabca7803345131f5628 25948 fail2ban_0.9.6-2.debian.tar.xz
 a0e32f96a89e86d4994ce9bf224dca1e281334cc 287540 fail2ban_0.9.6-2_all.deb
 07c08acbf68b899b8c05d1a7f6963aed8ae8941a 5358 fail2ban_0.9.6-2_amd64.buildinfo
Checksums-Sha256:
 38936d1140f54a0645e636699b8f47fe0a6e49cb9fa8ae62e1794b3fa9da31ca 1843 
fail2ban_0.9.6-2.dsc
 22c9386e9493c1fb4d8371c59a066b88d500354d9758a80b4274dcb5b7bd1704 25948 
fail2ban_0.9.6-2.debian.tar.xz
 e68bb7afbd68c53741630c834ab78f093bfc393e88f40b37dc5904f773a371dd 287540 
fail2ban_0.9.6-2_all.deb
 f48a6ee6d2b788ed52a84d6fffd3d924f26e44585f95a7878b6e9235bb8a4585 5358 
fail2ban_0.9.6-2_amd64.buildinfo
Files:
 0d0f6863494ec810fb1806223888bd6f 1843 net optional fail2ban_0.9.6-2.dsc
 ae53eb6fb8bb7a190399e4711a4d7d7b 25948 net optional 
fail2ban_0.9.6-2.debian.tar.xz
 296e18a9b089bfefaef25489cb22fd25 287540 net optional fail2ban_0.9.6-2_all.deb
 c6d5f76b6e1deb43be4afdb00ccd5483 5358 net optional 
fail2ban_0.9.6-

Processed: Re: Bug#860468: system-config-printer needs libnotify4

2017-04-17 Thread Debian Bug Tracking System 
Processing control commands:

> severity -1 grave
Bug #860468 [system-config-printer] system-config-printer needs libnotify4
Severity set to 'grave' from 'normal'
> reassign -1 gir1.2-notify-0.7
Bug #860468 [system-config-printer] system-config-printer needs libnotify4
Bug reassigned from package 'system-config-printer' to 'gir1.2-notify-0.7'.
No longer marked as found in versions system-config-printer/1.5.7-3.
Ignoring request to alter fixed versions of bug #860468 to the same values 
previously set
> found -1 0.7.7-1
Bug #860468 [gir1.2-notify-0.7] system-config-printer needs libnotify4
Marked as found in versions libnotify/0.7.7-1.
> retitle -1 gir1.2-notify-0.7: missing dependency on ${gir:Depends}
Bug #860468 [gir1.2-notify-0.7] system-config-printer needs libnotify4
Changed Bug title to 'gir1.2-notify-0.7: missing dependency on ${gir:Depends}' 
from 'system-config-printer needs libnotify4'.
> tags -1 pending
Bug #860468 [gir1.2-notify-0.7] gir1.2-notify-0.7: missing dependency on 
${gir:Depends}
Added tag(s) pending.

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

Bug#856720: Patch

2017-04-17 Thread shanavas 
Package: diaspora-common
Followup-For: Bug #856720
Tags: patch

attaching patch
Shanavas M


0001-Add-missing-directories.patch
Description: Binary data

Processed: Re: #860233: gnome-paint: Segmentation fault on startup

2017-04-17 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + patch
Bug #860233 [gnome-paint] gnome-paint: Segmentation fault on startup
Added tag(s) patch.

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

Bug#859926: speechd-up: fails to install

2017-04-17 Thread Paul Gevers 
Hi Jean-Philippe,

On 17-04-17 11:19, MENGUAL Jean-Philippe wrote:
> We're going to have a look, but here I cannot reproduce. On Stretch, I
> install the package without problems. So I am surprised. I may have
> systemd-sysv, indeed, but not much more.

Seems like your system is the only system where it works then. Also in
Ubuntu, this issue was twice reported¹, while looking at the popcon, it
isn't heavily installed. That makes 5 people where it fails to install.

Paul

¹ https://bugs.launchpad.net/ubuntu/+source/speechd-up/+bug/1504054



signature.asc
Description: OpenPGP digital signature

Bug#860233: #860233: gnome-paint: Segmentation fault on startup

2017-04-17 Thread Boyuan Yang 
Control: tags -1 + patch

Hello all,

I found proper patches for this problem (from Ubuntu [1]), which is:
   1) force running dh-autoreconf;
   2) enabling deprecated gdk functions.

After that, the program runs normally without any crashing.

Debdiff for a new version is provided below. Source code is pushed onto Git 
repository on Alioth 
(https://anonscm.debian.org/git/collab-maint/gnome-paint.git).

diff -Nru gnome-paint-0.4.0/debian/changelog gnome-paint-0.4.0/debian/changelog
--- gnome-paint-0.4.0/debian/changelog  2013-07-30 21:29:55.0 +0800
+++ gnome-paint-0.4.0/debian/changelog  2017-04-17 21:42:56.0 +0800
@@ -1,3 +1,17 @@
+gnome-paint (0.4.0-5) unstable; urgency=medium
+
+  * Sponsored upload.
+  * d/control: Add myself into uploaders list.
+  * d/control: Bump Standards Version to 3.9.8.
+  * d/control: Use secure URI for homepage.
+  * d/control: Add Vcs-Git and Vcs-Browser.
+  * control,rules: Use dh-autoreconf instead of autotools-dev.
+(Closes: #727874)
+  * d/patches: Add patch to enable deprecated gdk functions.
+(Closes: #860233)
+
+ -- Boyuan Yang <073p...@gmail.com>  Mon, 17 Apr 2017 21:42:56 +0800
+
 gnome-paint (0.4.0-4) unstable; urgency=low
 
   * debian/ftbfs-libs-lm.patch:
diff -Nru gnome-paint-0.4.0/debian/control gnome-paint-0.4.0/debian/control
--- gnome-paint-0.4.0/debian/control  2013-07-30 21:29:55.0 +0800
+++ gnome-paint-0.4.0/debian/control  2017-04-17 21:42:54.0 +0800
@@ -2,9 +2,13 @@
 Section: graphics
 Priority: optional
 Maintainer: Aron Xu 
-Build-Depends: debhelper (>= 9), autotools-dev, libgtk2.0-dev, intltool ( >= 
0.35.0), gettext
-Standards-Version: 3.9.4
-Homepage: http://launchpad.net/gnome-paint/
+Uploaders:
+ Boyuan Yang <073p...@gmail.com>
+Build-Depends: debhelper (>= 9), dh-autoreconf, libgtk2.0-dev, intltool ( >= 
0.35.0), gettext
+Standards-Version: 3.9.8
+Homepage: https://launchpad.net/gnome-paint/
+Vcs-Git: https://anonscm.debian.org/git/collab-maint/gnome-paint.git
+Vcs-Browser: https://anonscm.debian.org/git/collab-maint/gnome-paint.git
 
 Package: gnome-paint
 Architecture: any
diff -Nru gnome-paint-0.4.0/debian/patches/debian-860233-enable-deprecated-gdk-
functions.patch gnome-paint-0.4.0/debian/patches/debian-860233-enable-
deprecated-gdk-functions.patch
--- gnome-paint-0.4.0/debian/patches/debian-860233-enable-deprecated-gdk-
functions.patch  1970-01-01 08:00:00.0 +0800
+++ gnome-paint-0.4.0/debian/patches/debian-860233-enable-deprecated-gdk-
functions.patch  2017-04-17 21:37:47.0 +0800
@@ -0,0 +1,25 @@
+From: Logan Rosen 
+Date: Mon, 17 Apr 2017 21:34:19 +0800
+Subject: Enable deprecated gdk functions
+Forwarded: no
+Last-Update: 2015-12-21
+
+Enable deprecated GDK functions to fix Debian Bug #860233.
+
+Original patch picked from Ubuntu gnome-paint 0.4.0-4ubuntu2.
+---
+ src/Makefile.am | 1 -
+ 1 file changed, 1 deletion(-)
+
+diff --git a/src/Makefile.am b/src/Makefile.am
+index 852ae55..fe405ff 100644
+--- a/src/Makefile.am
 b/src/Makefile.am
+@@ -78,7 +78,6 @@ gnome_paint_SOURCES = \
+ gnome_paint_CFLAGS = \
+   -DG_DISABLE_DEPRECATED\
+   -DG_DISABLE_SINGLE_INCLUDES\
+-  -DGDK_DISABLE_DEPRECATED\
+   -DGTK_DISABLE_DEPRECATED\
+   -DGDK_DISABLE_SINGLE_INCLUDES\
+   -DGTK_DISABLE_SINGLE_INCLUDES
diff -Nru gnome-paint-0.4.0/debian/patches/series gnome-paint-0.4.0/debian/
patches/series
--- gnome-paint-0.4.0/debian/patches/series  2013-07-30 21:29:55.0 
+0800
+++ gnome-paint-0.4.0/debian/patches/series  2017-04-17 21:38:19.0 
+0800
@@ -3,3 +3,4 @@
 debian-612470-handle-urls.patch
 ftbfs-libs-lm.patch
 ftbfs-format-security.patch
+debian-860233-enable-deprecated-gdk-functions.patch
diff -Nru gnome-paint-0.4.0/debian/rules gnome-paint-0.4.0/debian/rules
--- gnome-paint-0.4.0/debian/rules  2010-12-31 12:45:40.0 +0800
+++ gnome-paint-0.4.0/debian/rules  2017-04-17 21:26:06.0 +0800
@@ -4,7 +4,7 @@
 LDFLAGS += -Wl,--as-needed
 
 %:
-  dh  $@
+  dh  $@ --with autoreconf
 override_dh_install:
   mkdir -p debian/gnome-paint/usr/share/doc/gnome-paint/
   mv debian/gnome-paint/usr/doc/gnome-paint/README debian/gnome-paint/usr/
share/doc/gnome-paint/

Thanks!

[1] https://patches.ubuntu.com/g/gnome-paint/gnome-paint_0.4.0-4ubuntu2.patch

--
Sincerely,
Boyuan Yang

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

Processed: tagging 860464

2017-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 860464 + patch
Bug #860464 [wdm] wdm: Missing handling of plymouth (#782456)
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#856720: symlink target does not exists

2017-04-17 Thread shanavas 
diaspora-common package creates symlink from /usr/share/diaspora to 
/run/diaspora but the target directory /run/diaspora is never created.

fixing the broken symlink fixes the issue

Bug#860464: wdm: Missing handling of plymouth (#782456)

2017-04-17 Thread Axel Beckert 
Hi Niels,

Niels Thykier wrote:
> > [...] As I'm currently travelling, I can't promise to get this tested 
> > before Tuesday evening.
> 
> Ok, that will be fine.  For avoidance of doubt, is Tuesday evening
> tomorrow (UTC) or 8 days from now?

I'll be on the road again later today and expect to arrive back home
latest tomorrow (Tuesday) evening. There it's easier to setup an
according VM than on my laptop. (And I probably don't have enough time
to do this properly before network teardown at Easterhegg...)

> > I assume fixing that issue doesn't hinder getting a freeze exception.
> > The according commit in Git is
> > https://anonscm.debian.org/cgit/collab-maint/wdm.git/commit/?id=5c5dc8d62117d6f5448ab3a82bf7f97283146c02
> 
> Ack, should be fine.

Thanks!

> > P.S.: Your bug report (and #860463) was caught by my spam filter as
> > one of the bugs.debian.org hosts seems to be blacklisted:
> > RCVD_IN_BL_SPAMCOP_NET, RCVD_IN_SBL_CSS, RCVD_IN_SORBS_SPAM,
> > RCVD_IN_SORBS_WEB, T_DKIM_INVALID, URIBL_BLOCKED (Will write a full
> > "bug report" against the BTS for that.)
> 
> Thanks, wasn't aware of that.

This mail of yours also came from buxtehude.d.o and went through fine
again so I assume this issue is already fixed.

I only noticed your bug report because of the "Processing" mail after
adding the according blocking of the plymouth bug report.

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#860464: wdm: Missing handling of plymouth (#782456)

2017-04-17 Thread Niels Thykier 
Axel Beckert:
> Hi Niels,
> 
> Niels Thykier wrote:
>> I have reviewed the wdm init.d script and I cannot see that it takes
>> plymouth into account (which leads to #782456).  To the best of my
>> knowledge, #782456 have to be fixed in the DMs.
> 
> Thanks for the bug report. I wasn't aware that login manager need to
> do that. (I never use plymouth.)
> 

Hi,

Thanks for the quick response to this bug :)

>> For init scripts that can be done by the following shell snippet (just
>> before starting the DM):
>>
>> """
>> if [ -x /bin/plymouth ] ; then
>>/bin/plymouth quit
>> fi
>> """
> 
> Done in git:
> https://anonscm.debian.org/cgit/collab-maint/wdm.git/commit/?id=d3b07cbd0024c888e24d3617d89fa24044bd15d5
> 
> [...] As I'm currently travelling, I can't promise to get this tested before 
> Tuesday evening.
> 

Ok, that will be fine.  For avoidance of doubt, is Tuesday evening
tomorrow (UTC) or 8 days from now?

> If the release team prefers a soon upload, I can do an upload with
> that feature untested.
> 

I am okay with the wait. :)

> [...]
> I assume fixing that issue doesn't hinder getting a freeze exception.
> The according commit in Git is
> https://anonscm.debian.org/cgit/collab-maint/wdm.git/commit/?id=5c5dc8d62117d6f5448ab3a82bf7f97283146c02
> 

Ack, should be fine.

>> PS: If a later version should add a systemd service file then it
>> should be a question of adding the following under the "[Unit]"
>> section:
>>
>> """
>> After=plymouth-quit.service
>> """
> 
> Cc'ing #761642 for that so it doesn't become left behind after this
> bug report has been closed.
> 
>> NB: Please do *not* add a systemd unit for stretch at this point in
>> time.
> 
> Sure.
> 
> P.S.: Your bug report (and #860463) was caught by my spam filter as
> one of the bugs.debian.org hosts seems to be blacklisted:
> RCVD_IN_BL_SPAMCOP_NET, RCVD_IN_SBL_CSS, RCVD_IN_SORBS_SPAM,
> RCVD_IN_SORBS_WEB, T_DKIM_INVALID, URIBL_BLOCKED (Will write a full
> "bug report" against the BTS for that.)
> 
>   Regards, Axel
> 

Thanks, wasn't aware of that.

~Niels

Bug#860455: marked as done (nnn: Illegal instruction reported on an AMD Phenom II X4 system)

2017-04-17 Thread Debian Bug Tracking System 
Your message dated Mon, 17 Apr 2017 12:33:56 +
with message-id 
and subject line Bug#860455: fixed in nnn 1.0-1~exp2
has caused the Debian Bug report #860455,
regarding nnn: Illegal instruction reported on an AMD Phenom II X4 system
to be marked as done.

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

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


-- 
860455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nnn
Version: 1.0-1~exp1
Severity: serious

I just installed nnn from experimental on my AMD Phenom II X4 system and I
get an "Illegal instruction" message right after I start it.

Perhaps it has optimizations specific to Intel processors? In particular, I
think that my system may not have SSSE3 instructions (and up).

Looking at the logs at

https://buildd.debian.org/status/package.php?p=nnn&suite=experimental

I see that the compilation options include -O3 and -march=native, which
makes the binaries unusable by machines that don't support the instructions
where the binaries were built.

Please, fix this.


Thanks,

Rogério Brito.


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

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

Versions of packages nnn depends on:
ii  libc62.24-9
ii  libncurses5  6.0+20161126-1
ii  libtinfo56.0+20161126-1

nnn recommends no packages.

nnn suggests no packages.

-- no debconf information

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--- End Message ---
--- Begin Message ---
Source: nnn
Source-Version: 1.0-1~exp2

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

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

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

Debian distribution maintenance software
pp.
SZ Lin (林上智)  (supplier of updated nnn package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 17 Apr 2017 19:38:17 +0800
Source: nnn
Binary: nnn
Architecture: source amd64
Version: 1.0-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: SZ Lin (林上智) 
Changed-By: SZ Lin (林上智) 
Description:
 nnn- Free, fast, friendly file browser
Closes: 860455
Changes:
 nnn (1.0-1~exp2) experimental; urgency=medium
 .
   * Remove -march=native and change -O3 to -O2 in cflags (Closes: #860455)
Checksums-Sha1:
 abc532ef8e0c74238fd20513868a5f5f4de508d3 1836 nnn_1.0-1~exp2.dsc
 73f8d23163be13e9a0c38e9df3d9891f652ca884 4616 nnn_1.0-1~exp2.debian.tar.xz
 12902e74d4f9895c5fd48c3556d5e48c85c30fdd 5710 nnn_1.0-1~exp2_amd64.buildinfo
 38b2ac2f67038684a49ff8e7a84ad9cef1814123 16952 nnn_1.0-1~exp2_amd64.deb
Checksums-Sha256:
 2fb53d57ae85a544fda30ff4d0b32cc06762a659b0920333988ddcfae5c1930a 1836 
nnn_1.0-1~exp2.dsc
 dfe76b007457f382a6cfd2e3f229846b9e56e020387d6a9dbb6fb9ac4a6dd0de 4616 
nnn_1.0-1~exp2.debian.tar.xz
 16a7afc5f49da49fc8a2c52b91a3ea42919732f64c395fc01a58ea2d2b5bf4ed 5710 
nnn_1.0-1~exp2_amd64.buildinfo
 f1c98a84854d0bd7008aa668b626f108f1f9c26f468c9a76a8f41c9bbd0c65b1 16952 
nnn_1.0-1~exp2_amd64.deb
Files:
 58f2bf4f7959a8a5307f8041f3fe6b9e 1836 misc optional nnn_1.0-1~exp2.dsc
 dceda0de7c315105ce2319edaffd7eec 4616 misc optional 
nnn_1.0-1~exp2.debian.tar.xz
 51045faa895976c6c7cecc249cd0d1df 5710 misc optional 
nnn_1.0-1~exp2_amd64.buildinfo
 93650c59489874df4015bfcb63da7885 16952 misc optional nnn_1.0-1~exp2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEF4+DOLMUAeME/ES6qVmzipVh8/kFAlj0snQACgkQqVmzipVh
8/kmmQ/8Cew+IxqPP+IfjT40fKNO+JtCQpvBpXcLQQ6McYpU6M3LCPqz9cXSMEFe
xT2tK+wevFkWi3w93Fdg9V4bhM0r/EppIzhs1+y4OKXEaN1g3RWkWGI7Zl5ZyTwv
Y/fytzwWJIIC0zbrkbpdK8t2AUnYcRqOhI1QaDk6ygPDG/B9Lv4Zs9/gshP++03c
QzZjNYK//mJvmXIanAr1FRcKJTmPjvoAoSlIUGUGuvf+W82770yNCZBYdiDdCeSy
TVrLxBp+evsDl2rKjmvixykjc71swvVWLzFMEnWBnc

Bug#860464: wdm: Missing handling of plymouth (#782456)

2017-04-17 Thread Axel Beckert 
Hi Niels,

Niels Thykier wrote:
> I have reviewed the wdm init.d script and I cannot see that it takes
> plymouth into account (which leads to #782456).  To the best of my
> knowledge, #782456 have to be fixed in the DMs.

Thanks for the bug report. I wasn't aware that login manager need to
do that. (I never use plymouth.)

> For init scripts that can be done by the following shell snippet (just
> before starting the DM):
> 
> """
> if [ -x /bin/plymouth ] ; then
>/bin/plymouth quit
> fi
> """

Done in git:
https://anonscm.debian.org/cgit/collab-maint/wdm.git/commit/?id=d3b07cbd0024c888e24d3617d89fa24044bd15d5

Since I don't have a real hardware running plymouth on and I refuse to
install it on any machine in even near-production level use, I'll have
to setup a VM specifically to test this. As I'm currently travelling,
I can't promise to get this tested before Tuesday evening.

If the release team prefers a soon upload, I can do an upload with
that feature untested.

Lintian also informed me about another issue in the package:

  E: wdm: init.d-script-needs-depends-on-lsb-base etc/init.d/wdm (line 30)

I assume fixing that issue doesn't hinder getting a freeze exception.
The according commit in Git is
https://anonscm.debian.org/cgit/collab-maint/wdm.git/commit/?id=5c5dc8d62117d6f5448ab3a82bf7f97283146c02

> PS: If a later version should add a systemd service file then it
> should be a question of adding the following under the "[Unit]"
> section:
> 
> """
> After=plymouth-quit.service
> """

Cc'ing #761642 for that so it doesn't become left behind after this
bug report has been closed.

> NB: Please do *not* add a systemd unit for stretch at this point in
> time.

Sure.

P.S.: Your bug report (and #860463) was caught by my spam filter as
one of the bugs.debian.org hosts seems to be blacklisted:
RCVD_IN_BL_SPAMCOP_NET, RCVD_IN_SBL_CSS, RCVD_IN_SORBS_SPAM,
RCVD_IN_SORBS_WEB, T_DKIM_INVALID, URIBL_BLOCKED (Will write a full
"bug report" against the BTS for that.)

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

Processed: tagging 860464

2017-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 860464 + pending
Bug #860464 [wdm] wdm: Missing handling of plymouth (#782456)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: severity of 860347 is important

2017-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # Work around exists - just less than nice for people using sudo
> severity 860347 important
Bug #860347 [xserver-xorg-core] xserver-xorg-core: can't produce script.log for 
running X server
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#860465: slim: Missing handling of plymouth (#782456)

2017-04-17 Thread Niels Thykier 
Package: slim
Version: 1.3.6-4
Severity: serious
Tags: sid stretch
Control: block 782456 by -1

Hi,

I have reviewed the slim systemd service file plus the init.d script
and I cannot see that it takes plymouth into account (which leads to
#782456).  To the best of my knowledge, #782456 have to be fixed in
the DMs.


For init scripts that can be done by the following shell snippet (just
before starting the DM):

"""
if [ -x /bin/plymouth ] ; then
   /bin/plymouth quit
fi
"""

For systemd, it should be a question of adding the following under the
"[Unit]" section:

"""
After=plymouth-quit.service
"""

I have X-CC'ed Laurent Bigonville, who is the maintainer of plymouth
in case you have any technical questions related to this bug.

Thanks,
~Niels

Processed: slim: Missing handling of plymouth (#782456)

2017-04-17 Thread Debian Bug Tracking System 
Processing control commands:

> block 782456 by -1
Bug #782456 [plymouth] plymouth: With plymouth installed, starting the DM 
sometimes fails
782456 was blocked by: 860464 860463
782456 was blocking: 783364
Added blocking bug(s) of 782456: 860465

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

Bug#859560: xen: CVE-2017-7228: x86: broken check in memory_exchange() permits PV guest breakout (XSA-212)

2017-04-17 Thread Niels Thykier 
On Tue, 11 Apr 2017 18:38:22 +0100 Ian Jackson
 wrote:
> Niels Thykier writes ("Bug#859560: xen: CVE-2017-7228: x86: broken check in 
> memory_exchange() permits PV guest breakout (XSA-212)"):
> > Hi Xen maintainers,
> > Is there any update on this bug?
> 
> Sorry for having dropping this.  I will try to sort out this (and the
> other outstanding security issues with this package) this week.
> 
> Ian.
> 
> 

Hi Ian,

Thanks for looking into this. :)

~Niels

Processed: block 782456 with 860463 860464

2017-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> block 782456 with 860463 860464
Bug #782456 [plymouth] plymouth: With plymouth installed, starting the DM 
sometimes fails
782456 was not blocked by any bugs.
782456 was blocking: 783364
Added blocking bug(s) of 782456: 860463 and 860464
> thanks
Stopping processing here.

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

Bug#860464: wdm: Missing handling of plymouth (#782456)

2017-04-17 Thread Niels Thykier 
Package: wdm
Version: 1.28-19
Severity: serious

Hi,

I have reviewed the wdm init.d script and I cannot see that it takes
plymouth into account (which leads to #782456).  To the best of my
knowledge, #782456 have to be fixed in the DMs.


For init scripts that can be done by the following shell snippet (just
before starting the DM):

"""
if [ -x /bin/plymouth ] ; then
   /bin/plymouth quit
fi
"""

I have X-CC'ed Laurent Bigonville, who is the maintainer of plymouth
in case you have any technical questions related to this bug.

Thanks,
~Niels

PS: If a later version should add a systemd service file then it
should be a question of adding the following under the "[Unit]"
section:

"""
After=plymouth-quit.service
"""

NB: Please do *not* add a systemd unit for stretch at this point in
time.

Bug#860463: nodm: Missing handling of plymouth (#782456)

2017-04-17 Thread Niels Thykier 
Package: nodm
Version: 0.13-1
Severity: serious

Hi,

I have reviewed the nodm systemd service file plus the init.d script
and I cannot see that it takes plymouth into account (which leads to
#782456).  To the best of my knowledge, #782456 have to be fixed in
the DMs.


For init scripts that can be done by the following shell snippet (just
before starting the DM):

"""
if [ -x /bin/plymouth ] ; then
   /bin/plymouth quit
fi
"""

For systemd, it should be a question of adding the following under the
"[Unit]" section:

"""
After=plymouth-quit.service
"""

I have X-CC'ed Laurent Bigonville, who is the maintainer of plymouth
in case you have any technical questions related to this bug.

Thanks,
~Niels

Bug#859926: speechd-up: fails to install

2017-04-17 Thread MENGUAL Jean-Philippe 
Hi,

We're going to have a look, but here I cannot reproduce. On Stretch, I
install the package without problems. So I am surprised. I may have
systemd-sysv, indeed, but not much more.

Regards,


Le 16/04/2017 à 22:17, Paul Gevers a écrit :
> Hi
> 
> On 16-04-17 21:51, Paul Gevers wrote:
>> I haven't figured out the difference yet.
> 
> Probably somebody who knows systemd should have a look. I have the
> feeling it is interfering with the script and not doing what I read.
> 
> I have no clue where to find the input (the service file?) that systemd
> is actually using yet. This is all new to me.
> 
> Paul
> 

-- 
Logo Hypra  
Photo Jean-Philippe MENGUAL *JEAN-PHILIPPE MENGUAL**
DIRECTEUR TECHNIQUE ET QUALITÉ*
adresse84, quai de Jemappes, 75010, Paris
téléphone+331 84 71 06 61 
courieljpmeng...@hypra.fr
site webwww.hypra.fr
Facebook Hypra Twitter Hypra
Linkedin





signature.asc
Description: OpenPGP digital signature

Bug#860450: marked as done (Gtk.TreeView.get/set_Model() throws NullReferenceException and spews GLib-GObject-CRITICAL errors)

2017-04-17 Thread Debian Bug Tracking System 
Your message dated Mon, 17 Apr 2017 09:34:05 +
with message-id 
and subject line Bug#860450: fixed in gtk-sharp2 2.12.40-2
has caused the Debian Bug report #860450,
regarding Gtk.TreeView.get/set_Model() throws NullReferenceException and spews 
GLib-GObject-CRITICAL errors
to be marked as done.

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

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


-- 
860450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtk2.0-cil
Version: 2.12.40-1
Severity: serious
Forwarded: https://bugzilla.xamarin.com/show_bug.cgi?id=55235
Owner: mee...@debian.org
Control: -1 affects smuxi-frontend-gnome

In Smuxi when you rejoin a channel this will lead to exception after
upgrading from GTK# 2.12.10 to 2.12.40 like this:

System.NullReferenceException: Object reference not set to an instance of
an object
 at GLib.GType.GetQualifiedName (System.String cname) [0x0005d] in
<8c54b02ecd9b45db868abfb5696ef2d4>:0
 at GLib.GType.LookupType (System.IntPtr typeid) [0x00020] in
<8c54b02ecd9b45db868abfb5696ef2d4>:0
 at GLib.ObjectManager.GetTypeOrParent (System.IntPtr obj) [0x7] in
<8c54b02ecd9b45db868abfb5696ef2d4>:0
 at GLib.ObjectManager.CreateObject (System.IntPtr raw) [0x00012] in
<8c54b02ecd9b45db868abfb5696ef2d4>:0
 at GLib.Object.GetObject (System.IntPtr o, System.Boolean owned_ref)
[0x00074] in <8c54b02ecd9b45db868abfb5696ef2d4>:0
 at Gtk.TreeModelAdapter.GetObject (System.IntPtr handle, System.Boolean
owned) [0x0] in <8bc02e9c110240acb0e1344122d80ad3>:0
 at Gtk.TreeView.get_Model () [0xc] in
<8bc02e9c110240acb0e1344122d80ad3>:0
 at Smuxi.Frontend.Gnome.GroupChatView.Populate () [0x0004c] in
/tmp/buildd/smuxi-1.0.6/src/Frontend-GNOME/Views/Chats/GroupChatView.cs:325
 at
Smuxi.Frontend.Gnome.ChatViewManager+c__AnonStorey1.<>m__0 ()
[0x0007b] in
/tmp/buildd/smuxi-1.0.6/src/Frontend-GNOME/ChatViewManager.cs:351
 at GLib.Idle+IdleProxy.Handler (System.IntPtr data) [0x0003c] in
<8c54b02ecd9b45db868abfb5696ef2d4>:0

And the console output will show GTK/GLib CRITICAL messages:

(smuxi-frontend-gnome:1992): Gtk-CRITICAL **: IA__gtk_list_store_clear:
assertion 'GTK_IS_LIST_STORE (list_store)' failed
(smuxi-frontend-gnome:1992): Gtk-CRITICAL **: IA__gtk_tree_view_set_model:
assertion 'model == NULL || GTK_IS_TREE_MODEL (model)' failed
(smuxi-frontend-gnome:1992): GLib-GObject-CRITICAL **: g_object_unref:
assertion 'G_IS_OBJECT (object)' failed
(smuxi-frontend-gnome:1992): Gtk-CRITICAL **: IA__gtk_list_store_clear:
assertion 'GTK_IS_LIST_STORE (list_store)' failed
(smuxi-frontend-gnome:1992): GLib-GObject-CRITICAL **:
g_object_remove_toggle_ref: assertion 'G_IS_OBJECT (object)' failed
(smuxi-frontend-gnome:1992): GLib-GObject-CRITICAL **:
g_object_remove_toggle_ref: assertion 'G_IS_OBJECT (object)' failed
(smuxi-frontend-gnome:1992): GLib-GObject-CRITICAL **:
g_object_remove_toggle_ref: assertion 'G_IS_OBJECT (object)' failed
(smuxi-frontend-gnome:1992): GLib-GObject-CRITICAL **:
g_object_remove_toggle_ref: assertion 'G_IS_OBJECT (object)' failed

This has never been a problem though with GTK# < 2.12.40, which makes this
a regression of GTK# 2.12.40

I have debugged the issue already and found the fix in the stable branch of
upstream's git repository here:
https://github.com/mono/gtk-sharp/commit/4ac71507fffce997207215ac3f8b38471ce60a14#commitcomment-21776072

So I will backport that fix and request a freeze exception as this bug
affects all GTK# users that use the Gtk.TreeView and replace the model.

Best regards,

Mirco (meebey) Bauer

FOSS Hacker mee...@meebey.net  https://www.meebey.net/
Debian Developermee...@debian.org  http://www.debian.org/
GNOME Foundation Member mmmba...@gnome.org http://www.gnome.org/
CTO @ Gatecoin Ltd. mi...@gatecoin.com https://gatecoin.com/
.NET Foundation Advisory Council Memberhttp://www.dotnetfoundation.org/
PGP-Key ID  0x7127E5ABEEF946C8 https://meebey.net/pubkey.asc
--- End Message ---
--- Begin Message ---
Source: gtk-sharp2
Source-Version: 2.12.40-2

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

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

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

Debian distribution maintenance software
pp.
Mirco Bauer  (supplier of updated gtk-sharp2 package)

(This message was generated automat

Bug#860455: nnn: Illegal instruction reported on an AMD Phenom II X4 system

2017-04-17 Thread Rogério Brito 
Package: nnn
Version: 1.0-1~exp1
Followup-For: Bug #860455

The fix is really, really obvious here: just use upstream's Makefile.generic
instead of Makefile and it should fix this and also all the other FTBFS
failures with other arches.


Regards,

Rogério.


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

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

Versions of packages nnn depends on:
ii  libc62.24-9
ii  libncurses5  6.0+20161126-1
ii  libtinfo56.0+20161126-1

nnn recommends no packages.

nnn suggests no packages.

-- no debconf information

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

Bug#860455: nnn: Illegal instruction reported on an AMD Phenom II X4 system

2017-04-17 Thread Rogério Brito 
Package: nnn
Version: 1.0-1~exp1
Severity: serious

I just installed nnn from experimental on my AMD Phenom II X4 system and I
get an "Illegal instruction" message right after I start it.

Perhaps it has optimizations specific to Intel processors? In particular, I
think that my system may not have SSSE3 instructions (and up).

Looking at the logs at

https://buildd.debian.org/status/package.php?p=nnn&suite=experimental

I see that the compilation options include -O3 and -march=native, which
makes the binaries unusable by machines that don't support the instructions
where the binaries were built.

Please, fix this.


Thanks,

Rogério Brito.


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

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

Versions of packages nnn depends on:
ii  libc62.24-9
ii  libncurses5  6.0+20161126-1
ii  libtinfo56.0+20161126-1

nnn recommends no packages.

nnn suggests no packages.

-- no debconf information

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

Bug#860446: gravit: Segmentation violation on start

2017-04-17 Thread Chris Lamb 
Hi,

> gravit: Segmentation violation on start

Can't seem to reproduce the _segfault_ here (amd64):

$ gravit
libpng warning: Interlace handling should be turned on when using png_read_image
SDL_SetVideoMode failed: Couldn't find matching GLX visual
You have videoantialiasing on. I'm turning it off and restarting...
SDL_SetVideoMode failed: Couldn't find matching GLX visual
There has been an error on start-up. Read your gravit configration file to 
possibly fix this.

$ echo $?
0


Regards,

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