date:20170507

Bug#856487: marked as done (libsbc1: compiling with gcc > 4.9 causes stack corruption)

2017-05-07 Thread Debian Bug Tracking System

Your message dated Mon, 08 May 2017 05:19:02 +
with message-id 
and subject line Bug#856487: fixed in sbc 1.3-2
has caused the Debian Bug report #856487,
regarding libsbc1: compiling with gcc > 4.9 causes stack corruption
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.)


-- 
856487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pulseaudio
Version: 10.0-1
Severity: important

Hi,

I updated pulseaudio from 9.0-5 to 10.0-1 two days ago and since then
I'm having segfaults for it when using bluetooth.

Using the local sound card works fine, also connecting the headset with
the bluetooth stick still works.

However once I actually start streaming audio to the headset, pulseaudio
crashes immediately, always.

Devices involved:
* Machine: Odroid U3 (an ARMv7 device)
* Headset: Plantronics Backbeat Pro
* Stick: Sena Parani-UD100-G03 Bluetooth Adapter

The coredump seems to contain a broken stack, unfortunately :( :

#
sudo coredumpctl dump --output /tmp/core
   PID: 15991 (pulseaudio)
   UID: 1001 (odroid)
   GID: 1001 (odroid)
Signal: 11 (SEGV)
 Timestamp: Wed 2017-03-01 08:00:18 CET (7h ago)
  Command Line: pulseaudio -D
Executable: /usr/bin/pulseaudio
 Control Group: /system.slice/tigervncserver.service
  Unit: tigervncserver.service
 Slice: system.slice
   Boot ID: ac412473aa4a4c6bb9a7784048ee138c
Machine ID: 5716166b59b3477b83939474094b846e
  Hostname: otheros
   Storage: 
/var/lib/systemd/coredump/core.pulseaudio.1001.ac412473aa4a4c6bb9a7784048ee138c.15991.1488351618.lz4
   Message: Process 15991 (pulseaudio) of user 1001 dumped core.

Stack trace of thread 17605:
#0  0xb0e0b962 n/a (libsbc.so.1)
More than one entry matches, ignoring rest.
#

Storage part can be found here:
http://metameute.de/~tux/bugreport/pulseaudio/core.pulseaudio.1001.ac412473aa4a4c6bb9a7784048ee138c.15991.1488351618.lz4

Or the coredump created via the "coredumpctl dump --output" above:
http://metameute.de/~tux/bugreport/pulseaudio/pulseaudio.core.xz

Regards, Linus

#
odroid(1001)$ cat ~/.config/pulse/default.pa
.include /etc/pulse/default.pa

load-module module-native-protocol-unix socket=/tmp/my-pulse-socket-name
load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1
#


-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 4.2.3-00234-g11acd64 (SMP w/4 CPU cores; PREEMPT)
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 pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-9
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.16-1
ii  libgcc1  1:6.3.0-8
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1
ii  libsm6   2:1.2.2-1+b1
ii  libsndfile1  1.0.27-1+b1
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-8
ii  libsystemd0  232-18
ii  libtdb1  1.3.11-2
ii  libudev1 232-18
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 10.0-1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-3+b2
pn  pavumeter
ii  udev 232-18

-- Configuration Files:
/etc/pulse/default.pa changed:
.fail
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
load-module module-augment-properties
load-module module-switch-on-port-available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
load-module module-detect

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

2017-05-07 Thread Nobuhiro Iwamatsu

Hi, all.

Thanks for your comments.

>On Mon, Apr 17, 2017 at 05:02:32PM +0100, Paul Brook wrote:
>> 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.
>
>Unfortunately this is not correct since extended asm is not allowed in
>naked functions.
>
>Short-term I'd suggest to use the attached patch, that disables the
>ARMv6 asm implementation and uses the C implementation instead.
>
>> 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).
>
>This is either a bug in gcc or insufficient documentation in gcc.
>

I see.
I will fix using --enable-high-precision of configure option.

>Could you (or did you already) submit that to the gcc bugzilla?

OK, I will report this to GCC.
>
>> Paul
>>...
>
>Thanks
>Adrian


Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#862027: marked as done (serf: FTBFS in stretch ("There were 14 failures"))

2017-05-07 Thread Debian Bug Tracking System

Your message dated Mon, 08 May 2017 03:39:17 +
with message-id 
and subject line Bug#862027: fixed in serf 1.3.9-2
has caused the Debian Bug report #862027,
regarding serf: FTBFS in stretch ("There were 14 failures")
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.)


-- 
862027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:serf
Version: 1.3.9-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-arch
QUILT_PATCHES=debian/patches \
quilt --quiltrc /dev/null push -a || test $? = 2
Applying patch libtool
patching file SConstruct

Now at patch libtool
touch debian/stamp-patched
dh_testdir
scons -j 1 GSSAPI=/usr CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LINKFLAGS="-specs=/usr/share/dpkg/no-pie-link.specs -Wl,-z,relro -Wl,-z,now 
-Wl,-z,defs -Wl,--as-needed" PREFIX=/usr LIBDIR=/usr/lib/x86_64-linux-gnu
scons: Reading SConscript files ...
Checking for GNU-compatible C compiler...yes
scons: done reading SConscript files.
scons: Building targets ...
gcc -o context.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
context.c
gcc -o incoming.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
incoming.c
gcc -o outgoing.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
outgoing.c
gcc -o ssltunnel.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
ssltunnel.c
gcc -o buckets/aggregate_buckets.o -c -g -O2 
-fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
buckets/aggregate_buckets.c
gcc -o buckets/allocator.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
buckets/allocator.c
gcc -o buckets/barrier_buckets.o -c -g -O2 
-fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
buckets/barrier_buckets.c
gcc -o buckets/buckets.o -c -g -O2

Bug#712612: gcr: diff for NMU version 3.20.0-5.1

2017-05-07 Thread Michael Biebl

Am 06.05.2017 um 10:43 schrieb Christoph Biedl:
> Michael Biebl wrote...
> 
>> Am 06.05.2017 um 00:00 schrieb Christoph Biedl:
> 
>>> I've prepared an NMU for gcr (versioned as 3.20.0-5.1), upload to
>>> DELAYED/5 will follow in a few hours. Please feel free to tell me if I
>>> should delay it longer.
>>>
>>
>> Seems to be missing doc/
> 
> That's not obvious for me.

Well, Ansgar mentioned this:

> there are two files under a BSD license in build/valgrind/*. In
addition the
> documentation has its own license in docs/reference/COPYING.

He was referring to that file afaics:
https://git.gnome.org/browse/gcr/tree/docs/reference/COPYING



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



signature.asc
Description: OpenPGP digital signature

Bug#858250: Bug#861953: unblock: runc/0.1.1+dfsg1-3

2017-05-07 Thread Roger Shimizu

[ CC: original Bug #858250 ]

On Sun, 07 May 2017 21:02:00 +
Niels Thykier  wrote:

> Roger Shimizu:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > 
> > Please unblock package runc
> > 
> > Since there's already a newer package in unstable, I guess it's
> > necessary to use "testing-proposed-updates"
> > 
> > Here I'm fixing #858250, which is FTBFS RC issue.
> 
> 
> Hi Roger,
> 
> Thanks for working on fixing #858250 for stretch. :)
> 
> Before there is an upload to testing-proposed-updates, the original bug
> should be resolved in unstable first.  That means that #858250 should be
> closed in unstable first.
> 
> On a related note, the Debian Bug Tracker can determine which suites are
> affected by looking at found + fixed versions, so there is no need to
> have two bugs for this (which is why I have merged #861966 back into
> #858250).

#858250 is not easy to fix for unstable, since there's already newer version
runc/1.0.0~rc2+git20161109.131.5137186-2, with newer version of Build-Depends
golang-github-opencontainers-specs/1.0.0~rc2+git20160926.38.1c7c27d-1.

As stated by #858250, runc is FTBFS with
golang-github-opencontainers-specs/1.0.0~rc2+git20160926.38.1c7c27d-1.
So my original plan was just patch d/control to limit the version of
Build-Depends.

Since you say it should fix unstable first, then stretch or t-p-u,
now I think we may just leave runc/0.1.1+dfsg1-2 (current in stretch)
as it is in stretch. Because it builds OK (without FTBFS) for stretch.
The #858250 FTBFS only occurs on unstable.

What's your opinion?

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

pgplaYcX_k6Ze.pgp
Description: PGP signature

Bug#861957: closed by Joachim Breitner <nome...@debian.org> (Re: Bug#861976: libghc-glut-dev: attempts to load libglut.so instead of libglut.so.3)

2017-05-07 Thread James Cowgill

Hi,

On 07/05/17 19:38, Adrian Bunk wrote:
> Control: reassign -1 libghc-glut-dev 2.7.0.10-3
> Control: fixed -1 2.7.0.10-4
> Control: affects -1 src:raincat
> 
> On Sun, May 07, 2017 at 01:51:04PM +, Debian Bug Tracking System wrote:
>> ...
>> With haskell-glut 2.7.0.10-4 this should be fixed in unstable.
> 
> I am reassigning it so that version tracking covers this.
> 
> I'd guess raincat might additionally need a binNMU?

It does - filed as #862061.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#861484: [Pkg-julia-devel] Bug#861484: Bug#861484: Bug#861484: Bug#861484: julia: FTBFS on arm64

2017-05-07 Thread Graham Inggs

Julia builds successfully on a Raspberry Pi 3 running an image
prepared by xylnao, dated 2016-04-14 [1] with kernel 4.5.0.
It fails in the same way as on arm-arm-04 and arm-conova-01 on a
Raspberry Pi 3 running an image prepared by Michael Stapelberg, dated
2017-03-22 [2] with kernel 4.9.18-1.
Both images were upgraded to current Stretch and 1GB was allocated for
a swapfile.

The build failures occur after the Julia executable has been built,
when it is run for the first time in order to compile coreimg.jl.

Instead of building the package, the segfault should be reproducible
by installing julia from the archive and then running 'julia' from a
terminal.

You should get output similar to:

ginggs@rpi3:~$ uname -a
Linux rpi3 4.5.0+ #1 SMP PREEMPT Tue Apr 12 22:51:39 PDT 2016 aarch64 GNU/Linux
ginggs@rpi3:~$ julia
   _
   _   _ _(_)_ |  A fresh approach to technical computing
  (_) | (_) (_)|  Documentation: http://docs.julialang.org
   _ _   _| |_  __ _   |  Type "?help" for help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 0.4.7 (2016-09-18 16:17 UTC)
 _/ |\__'_|_|_|\__'_|  |  Debian version 0.4.7-6+b2
|__/   |  aarch64-linux-gnu

julia> versioninfo()
Julia Version 0.4.7
Commit ae26b25 (2016-09-18 16:17 UTC)
Platform Info:
  System: Linux (aarch64-linux-gnu)
  CPU: unknown
  WORD_SIZE: 64
  BLAS: libopenblas (NO_LAPACKE NO_AFFINITY ARMV8)
  LAPACK: libopenblas
  LIBM: libopenlibm
  LLVM: libLLVM-3.8

...but this is bad:

ginggs@rpi3:~$ uname -a
Linux rpi3 4.9.0-2-arm64 #1 SMP Debian 4.9.18-1 (2017-03-30) aarch64 GNU/Linux
ginggs@rpi3:~$ julia

signal (11): Segmentation fault
isfile at ./stat.jl:107
Segmentation fault


[1] https://www.raspberrypi.org/forums/viewtopic.php?f=72=137963=141
[2] https://people.debian.org/~stapelberg//2017/03/22/raspberry-pi-3.html

Processed: Re: Bug#861953: unblock: runc/0.1.1+dfsg1-3

2017-05-07 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 moreinfo
Bug #861953 [release.debian.org] unblock: runc/0.1.1+dfsg1-3
Added tag(s) moreinfo.
> forcemerge 858250 861966
Bug #858250 [runc] Fails to build for stretch, build-depends not strict enough
Bug #858250 [runc] Fails to build for stretch, build-depends not strict enough
Marked as found in versions runc/1.0.0~rc2+git20161109.131.5137186-2.
Bug #861966 [runc] Fails to build for sid, build-depends not strict enough
Removed indication that 861966 affects sid
Added indication that 861966 affects stretch
Marked as found in versions runc/0.1.1+dfsg1-2.
Added tag(s) pending.
Merged 858250 861966

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

Bug#839575: Tinyca is incompatible with openssl 1.1 and some 1.0.2 versions

2017-05-07 Thread Thomas Viehweger

Edit:
The working openssl-version 1.02g-2 was not from jessie-backports.
It was from an older stretch version.

Now I tried the current version 1.0.2k-1~bpo8+1 from jessie-backports:
Tinyca hangs with this version, too - when creating a CA.

openssl version 1.0.1t-1+deb8u6 works as expected...

Bug#861112: xsane: always crashes on start

2017-05-07 Thread Aaro Koskinen

Hi,

On Fri, May 05, 2017 at 08:04:26PM +0200, John Paul Adrian Glaubitz wrote:
> On 05/05/2017 07:16 PM, Aaro Koskinen wrote:
> > I think Jörg Frings-Fürst has analyzed and fixed this bug already - he
> > provided me test packages (libsane_1.0.25-4~test1_amd64.deb etc.) offline
> > for testing and they seemed to fix the issue.
> 
> No, he didn't "fix" the issue. He completely removed a feature from 
> sane-backends
> and called it a fix, assuming that no one in Debian or Ubuntu or any of the 
> derived
> distributions wants to use Avahi with SANE.

Okay...

> > I'm currently away from my machines, but next week I'll recheck the
> > situation again with up-to-date Debian testing, If the problem is still
> > present I will provide the full backtrace etc.
> 
> Yes, please. I am not going to accept such a rather big cut in functionality
> without proper testing and error analysis first.

I found something when enabling debug outputs:

$ SANE_DEBUG_NET=3 scanimage -L
[sanei_debug] Setting debug level of net to 3.
[net] sane_init: authorize != null, version_code != null
[net] net_avahi_init: could not create Avahi client: Daemon not running
[net] net_avahi_init: Avahi init failed, support disabled
[net] sane_init: SANE net backend version 1.0.14 (AF-indep+IPv6) from 
sane-backends 1.0.25
[net] sane_init: Client has little endian byte order
[net] sane_init: searching for config file
scanimage: thread-watch.c:171: avahi_threaded_poll_lock: Assertion `p' failed.
Aborted

It's disabling Avahi support (I don't have such daemon) but still later
calling avahi_threaded_poll_lock() with NULL avahi_thread.

Here's the backtrace:

$ gdb scanimage
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from scanimage...Reading symbols from 
/usr/lib/debug/.build-id/2a/f2218a71fe370679d900eca9ab1b1e4f575859.debug...done.
done.
(gdb) run -L
Starting program: /usr/bin/scanimage -L
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x76420700 (LWP 6782)]
scanimage: thread-watch.c:171: avahi_threaded_poll_lock: Assertion `p' failed.

Thread 1 "scanimage" received signal SIGABRT, Aborted.
x773c7fcf in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x773c7fcf in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x773c93fa in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x773c0e37 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x773c0ee2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x70ce9404 in avahi_threaded_poll_lock ()
   from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
#5  0x7fffeadcac7c in sane_net_init (version_code=, 
authorize=) at net.c:1048
#6  0x77bd4dd0 in init (be=be@entry=0x55762290) at dll.c:614
#7  0x77bd5681 in sane_dll_get_devices (device_list=0x7fffbc18, 
local_only=0) at dll.c:1055
#8  0x62ab in main (argc=2, argv=0x7fffe068)
at scanimage.c:2038

A.

Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...

2017-05-07 Thread Sebastian Rasmussen

Of course, no problem, but it will have to wait a day or so. I didn't
notice that there was a new version in /unstable or /experimental when I
checked the other day so it is likely fairly recent.

/Sebastian

Bug#861736:

2017-05-07 Thread PICCA Frederic-Emmanuel

activating the NXError reporting we got

filenamenxs.h5 5 
ERROR: cannot open file: filenamenxs.h5
0


and looking for this errormessage,

we found it in the napi5.c file



NXstatus  NX5open(CONSTCHAR *filename, NXaccess am, 
 NXhandle* pHandle)
  {
  hid_t attr1,aid1, aid2, iVID;
  pNexusFile5 pNew = NULL;
  char pBuffer[512];
  char *time_buffer = NULL;
  char version_nr[10];
  unsigned int vers_major, vers_minor, vers_release, am1 ;
  hid_t fapl = -1; 
  int mdc_nelmts;
  size_t rdcc_nelmts;
  size_t rdcc_nbytes;
  double rdcc_w0;
  unsigned hdf5_majnum, hdf5_minnum, hdf5_relnum;

  *pHandle = NULL;

  if (H5get_libversion(_majnum, _minnum, _relnum) < 0)
  {
  NXReportError("ERROR: cannot determine HDF5 library version");
  return NX_ERROR;
  }
  if (hdf5_majnum == 1 && hdf5_minnum < 8)
  {
  NXReportError("ERROR: HDF5 library 1.8.0 or higher required");
  return NX_ERROR;
  }

  /* mask of any options for now */
  am = (NXaccess)(am & NXACCMASK_REMOVEFLAGS);

  /* turn off the automatic HDF error handling */  
  H5Eset_auto(H5E_DEFAULT, NULL, NULL);  
#ifdef USE_FTIME
struct timeb timeb_struct;
#endif 


pNew = (pNexusFile5) malloc (sizeof (NexusFile5));
if (!pNew) {
  NXReportError("ERROR: not enough memory to create file structure");
  return NX_ERROR;
}
memset (pNew, 0, sizeof (NexusFile5));


/* start HDF5 interface */
if (am == NXACC_CREATE5) {  
   fapl = H5Pcreate(H5P_FILE_ACCESS);
   H5Pget_cache(fapl,_nelmts,_nelmts,_nbytes,_w0);
   rdcc_nbytes=(size_t)nx_cacheSize;
   H5Pset_cache(fapl,mdc_nelmts,rdcc_nelmts,rdcc_nbytes,rdcc_w0);
   H5Pset_fclose_degree(fapl,H5F_CLOSE_STRONG);
   am1 = H5F_ACC_TRUNC;
   pNew->iFID = H5Fcreate (filename, am1, H5P_DEFAULT, fapl);
} else {
   if (am == NXACC_READ) {
  am1 = H5F_ACC_RDONLY;
} else {
  am1 = H5F_ACC_RDWR;
}
fapl = H5Pcreate(H5P_FILE_ACCESS);
H5Pset_fclose_degree(fapl,H5F_CLOSE_STRONG);
pNew->iFID = H5Fopen (filename, am1, fapl);
}  
if(fapl != -1) {
  H5Pclose(fapl);
}
if (pNew->iFID <= 0) {
  sprintf (pBuffer, "ERROR: cannot open file: %s", filename);
  NXReportError( pBuffer);
  free (pNew);
  return NX_ERROR;
}

Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...

2017-05-07 Thread Niels Thykier

On Mon, 8 May 2017 03:51:45 +0800 Sebastian Rasmussen 
wrote:
> Package: slim
> Version: 1.3.6-5
> Severity: serious
> 
> When upgrading from 1.3.6-4+b2 to 1.3.6-5 of slim I noticed that my
> window manager appeared to suddenly "crash" and logged me out. However
> I had
> not changed anything related to that but I had recently upgraded slim so I
> investigated it a bit.
> 
> I compiled 1.3.6-5 without the fix for 860465 as mentioned in the -5 debian
> patch (but keeping all other additions from -4+b2 to -5 the same). Without
> this "fix" my desktop no longer had problems. Could this be because
> I don't have plymouth installed (whatever that is)? I'm happy to do further
> testing if you can provide something for me to test. Besides this minor
> mishap I'm actually a happy slim user, thanks for putting in the effort. :)
> 
>  / Sebastian
> 
> 

Hi Sebastian,

Sorry to hear you ran into issues with the update.

Could you please try to upgrade to slim/1.3.6-5.1 to see if that fixes
your issue?  It is intended to fix some regressions in the -5 upload.

Thanks,
~Niels

Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...

2017-05-07 Thread Sebastian Rasmussen

Package: slim
Version: 1.3.6-5
Severity: serious

When upgrading from 1.3.6-4+b2 to 1.3.6-5 of slim I noticed that my
window manager appeared to suddenly "crash" and logged me out. However
I had
not changed anything related to that but I had recently upgraded slim so I
investigated it a bit.

I compiled 1.3.6-5 without the fix for 860465 as mentioned in the -5 debian
patch (but keeping all other additions from -4+b2 to -5 the same). Without
this "fix" my desktop no longer had problems. Could this be because
I don't have plymouth installed (whatever that is)? I'm happy to do further
testing if you can provide something for me to test. Besides this minor
mishap I'm actually a happy slim user, thanks for putting in the effort. :)

 / Sebastian

Bug#861736:

2017-05-07 Thread PICCA Frederic-Emmanuel

Herethe code ofthismethod

/**/
static NXstatus   NXinternalopen(CONSTCHAR *userfilename, NXaccess am, 
   pFileStack fileStack);
/*--*/
NXstatus   NXopen(CONSTCHAR *userfilename, NXaccess am, NXhandle *gHandle){
  int status;
  pFileStack fileStack = NULL;

  *gHandle = NULL;
  fileStack = makeFileStack();
  if(fileStack == NULL){
NXReportError("ERROR: no memory to create filestack");
  return NX_ERROR;
  }
  status = NXinternalopen(userfilename,am,fileStack);
  if(status == NX_OK){
*gHandle = fileStack;
  }

  return status;


so lets's see the internalopen


static NXstatus   NXinternalopen(CONSTCHAR *userfilename, NXaccess am, 
pFileStack fileStack)
{
return LOCKED_CALL(NXinternalopenImpl(userfilename, am, fileStack));
}



/*---*/
static NXstatus   NXinternalopenImpl(CONSTCHAR *userfilename, NXaccess am, 
pFileStack fileStack)
  {
int hdf_type=0;
int iRet=0;
NXhandle hdf5_handle = NULL;
pNexusFunction fHandle = NULL;
NXstatus retstat = NX_ERROR;
char error[1024];
char *filename = NULL;
int my_am = (am & NXACCMASK_REMOVEFLAGS);

/* configure fortify 
iFortifyScope = Fortify_EnterScope();
Fortify_CheckAllMemory();
*/

/*
  allocate data
*/
fHandle = (pNexusFunction)malloc(sizeof(NexusFunction));
if (fHandle == NULL) {
  NXReportError("ERROR: no memory to create Function structure");
  return NX_ERROR;
}
memset(fHandle, 0, sizeof(NexusFunction)); /* so any functions we miss are 
NULL */
   
/*
  test the strip flag. Elimnate it for the rest of the tests to work
*/
fHandle->stripFlag = 1;
if(am & NXACC_NOSTRIP){
  fHandle->stripFlag = 0;
  am = (NXaccess)(am & ~NXACC_NOSTRIP);
}
fHandle->checkNameSyntax = 0;
if (am & NXACC_CHECKNAMESYNTAX) {
fHandle->checkNameSyntax = 1;
am = (NXaccess)(am & ~NXACC_CHECKNAMESYNTAX);
}


if (my_am==NXACC_CREATE) {
  /* HDF4 will be used ! */
  hdf_type=1;
  filename = strdup(userfilename);
} else if (my_am==NXACC_CREATE4) {
  /* HDF4 will be used ! */
  hdf_type=1;   
  filename = strdup(userfilename);
} else if (my_am==NXACC_CREATE5) {
  /* HDF5 will be used ! */
  hdf_type=2;   
  filename = strdup(userfilename);
} else if (my_am==NXACC_CREATEXML) {
  /* XML will be used ! */
  hdf_type=3;   
  filename = strdup(userfilename);
} else {
  filename = locateNexusFileInPath((char *)userfilename);
  if(filename == NULL){
NXReportError("Out of memory in NeXus-API");
free(fHandle);
return NX_ERROR;
  }
  /* check file type hdf4/hdf5/XML for reading */
  iRet = determineFileType(filename);
  if(iRet < 0) {
snprintf(error,1023,"failed to open %s for reading",
 filename);
NXReportError(error);
free(filename);
return NX_ERROR;
  }
  if(iRet == 0){
snprintf(error,1023,"failed to determine filetype for %s ",
 filename);
NXReportError(error);
free(filename);
free(fHandle);
return NX_ERROR;
  }
  hdf_type = iRet;
}
if(filename == NULL){
NXReportError("Out of memory in NeXus-API");
return NX_ERROR;
}

if (hdf_type==1) {
  /* HDF4 type */
#ifdef HDF4
NXhandle hdf4_handle = NULL;
  retstat = NX4open((const char *)filename,am,_handle);
  if(retstat != NX_OK){
free(fHandle);
free(filename);
return retstat;
  }
  fHandle->pNexusData=hdf4_handle;
  NX4assignFunctions(fHandle);
  pushFileStack(fileStack,fHandle,filename);
#else
  NXReportError(
 "ERROR: Attempt to create HDF4 file when not linked with HDF4");
  retstat = NX_ERROR;
#endif /* HDF4 */
  free(filename);
  return retstat; 
} else if (hdf_type==2) {
  /* HDF5 type */
#ifdef HDF5
  retstat = NX5open(filename,am,_handle);
  if(retstat != NX_OK){
free(fHandle);
free(filename);
return retstat;
  }
  fHandle->pNexusData=hdf5_handle;
  NX5assignFunctions(fHandle);
  pushFileStack(fileStack,fHandle, filename);
#else
  NXReportError(
 "ERROR: Attempt to create HDF5 file when not linked with HDF5");
  retstat = NX_ERROR;
#endif /* HDF5 */
  free(filename);
  return retstat;
} else if(hdf_type == 3){
  /*
XML type
  */
#ifdef NXXML
NXhandle xmlHandle = NULL;
  retstat = NXXopen(filename,am,);
  if(retstat != NX_OK){
free(fHandle);
free(filename);
return retstat;
  }
  fHandle->pNexusData=xmlHandle;
  NXXassignFunctions(fHandle);
  pushFileStack(fileStack,fHandle,

Bug#861736:

2017-05-07 Thread PICCA Frederic-Emmanuel

in the napi.h files we saw this.

define CONCAT(__a,__b) __a##__b/* token concatenation */

#ifdef __VMS
#define MANGLE(__arg)   __arg
#else
#define MANGLE(__arg)   CONCAT(__arg,_)
#endif

#define NXopen  MANGLE(nxiopen)

 /**
   * Open a NeXus file.
   * NXopen honours full path file names. But it also searches
   * for files in all the paths given in the NX_LOAD_PATH environment variable.
   * NX_LOAD_PATH is supposed to hold a list of path string separated by the 
platform
   * specific path separator. For unix this is the : , for DOS the ; . Please 
note
   * that crashing on an open NeXus file will result in corrupted data. Only 
after a NXclose
   * or a NXflush will the data file be valid.
   * \param filename The name of the file to open
   * \param access_method The file access method. This can be:
   * \li NXACC__READ read access
   * \li NXACC_RDWR read write access
   * \li NXACC_CREATE, NXACC_CREATE4 create a new HDF-4 NeXus file
   * \li NXACC_CREATE5 create a new HDF-5 NeXus file
   * \li NXACC_CREATEXML create an XML NeXus file.
   * see #NXaccess_mode
   * Support for HDF-4 is deprecated.
   * \param pHandle A file handle which will be initialized upon successfull 
completeion of NXopen.
   * \return NX_OK on success, NX_ERROR in the case of an error.
   * \ingroup c_init
   */
extern  NXstatus  NXopen(CONSTCHAR * filename, NXaccess access_method, 
NXhandle* pHandle);


so we need to check in this method what is going on.

Bug#857573: systemd: Raise network interfaces fails to stop cleanly on shutdown/reboot

2017-05-07 Thread Mike Edwards

On Fri, May 05, 2017 at 08:31:07AM +0200, Christoph Biedl babbled thus:
> The issues here are pretty similar so I guess it's the same thing: Up to
> and including jessie(sic!), networking wasn't brought down if there is
> something mounted using AoE.

This issue was definitely present in jessie - I discovered it while
building a test machine with jessie and AoE, and it's the reason that I
held off on upgrading my fileserver from wheezy for so long.

I believe the issue was introduced with the changeover to systemd,
which is why I initially opened the bug against systemd, not ifupdown.

In any case, the fix of adding 'no-auto-down' for any interfaces that
serve AoE appears to work well for me.  It's a slight annoyance, but it
means no more hangs on shutdown.

-- 
  
Mike Edwards|   If this email address disappears,   
Unsolicited advertisments to|   assume it was spammed to death.  To
this address are not welcome.   |   reach me in that case, s/-.*@/@/

"Our progress as a nation can be no swifter than our progress in education.
The human mind is our fundamental resource."
  -- John F. Kennedy

Processed: limit source to debhelper, tagging 862049

2017-05-07 Thread Debian Bug Tracking System

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

> limit source debhelper
Limiting to bugs with field 'source' containing at least one of 'debhelper'
Limit currently set to 'source':'debhelper'

> tags 862049 + pending
Bug #862049 [debhelper] dh_missing aborts with "dh_missing: unknown option; 
aborting"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#862008: crashes, segmentation fault

2017-05-07 Thread Debian Bug Tracking System

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

> # Version was from at-spi2-core instead of pyatspi...
> found 862008 2.20.3+dfsg-1
Bug #862008 [python-pyatspi] crashes, segmentation fault
Marked as found in versions pyatspi/2.20.3+dfsg-1.
> notfound 862008 2.22.0-5
Bug #862008 [python-pyatspi] crashes, segmentation fault
There is no source info for the package 'python-pyatspi' at version '2.22.0-5' 
with architecture ''
Unable to make a source version for version '2.22.0-5'
No longer marked as found in versions 2.22.0-5.
> thanks
Stopping processing here.

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

Bug#861957: closed by Joachim Breitner <nome...@debian.org> (Re: Bug#861976: libghc-glut-dev: attempts to load libglut.so instead of libglut.so.3)

2017-05-07 Thread Adrian Bunk

Control: reassign -1 libghc-glut-dev 2.7.0.10-3
Control: fixed -1 2.7.0.10-4
Control: affects -1 src:raincat

On Sun, May 07, 2017 at 01:51:04PM +, Debian Bug Tracking System wrote:
>...
> With haskell-glut 2.7.0.10-4 this should be fixed in unstable.

I am reassigning it so that version tracking covers this.

I'd guess raincat might additionally need a binNMU?

> https://packages.qa.debian.org/h/haskell-glut.html
> does not tell me yet whether it will migrate to testing automatically
> or not.

Due to the freeze, there is no automatic testing migration since 
February 5th.

Please file an unblock request.

> Greetings,
> Joachim

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

Processed: Re: Bug#861957 closed by Joachim Breitner <nome...@debian.org> (Re: Bug#861976: libghc-glut-dev: attempts to load libglut.so instead of libglut.so.3)

2017-05-07 Thread Debian Bug Tracking System

Processing control commands:

> reassign -1 libghc-glut-dev 2.7.0.10-3
Bug #861957 {Done: Joachim Breitner } [raincat] raincat: 
Raincat doesn't run: user error (unknown GLUT entry glutInit)
Bug reassigned from package 'raincat' to 'libghc-glut-dev'.
No longer marked as found in versions raincat/1.1.1.2-3.
Ignoring request to alter fixed versions of bug #861957 to the same values 
previously set
Bug #861957 {Done: Joachim Breitner } [libghc-glut-dev] 
raincat: Raincat doesn't run: user error (unknown GLUT entry glutInit)
Marked as found in versions haskell-glut/2.7.0.10-3.
> fixed -1 2.7.0.10-4
Bug #861957 {Done: Joachim Breitner } [libghc-glut-dev] 
raincat: Raincat doesn't run: user error (unknown GLUT entry glutInit)
Marked as fixed in versions haskell-glut/2.7.0.10-4.
> affects -1 src:raincat
Bug #861957 {Done: Joachim Breitner } [libghc-glut-dev] 
raincat: Raincat doesn't run: user error (unknown GLUT entry glutInit)
Added indication that 861957 affects src:raincat

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

Bug#851909: Problems disappear after downgrade

2017-05-07 Thread Roger Kalt

Dear Adrian

On 05/07/2017 10:38 AM, Adrian Bunk wrote:
> could you ask to get your fix included into the next jessie point release?
> 
> "reportbug release.debian.org" -> jessie-pu

The jessie-pu bug is here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856240

I will ask my sponsor for upload.

Kind regards
  Roger

Bug#861979: marked as done (ufoai: crashes with signal 11 at mission start)

2017-05-07 Thread Debian Bug Tracking System

Your message dated Sun, 07 May 2017 18:18:41 +
with message-id 
and subject line Bug#861979: fixed in ufoai 2.5-3
has caused the Debian Bug report #861979,
regarding ufoai: crashes with signal 11 at mission start
to be marked as done.

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

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


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

Dear Maintainer,

ufoai crashes when starting a mission. I see the mission description ("Victory
condition: kill all the aliens"), and after I klick start i see "please wait"
for about one second and then it crashes with "Error: Received signal 11." on
the commandline output.

Below is the full output on the commandline from start to crash:

$ ufoai
 endianness initialization -
found little endian system

 filesystem initialization -
Adding game dir: /usr/share/games/ufoai/base
Added packfile /usr/share/games/ufoai/base/0base.pk3 (14 files)
Added packfile /usr/share/games/ufoai/base/0maps.pk3 (933 files)
Added packfile /usr/share/games/ufoai/base/0materials.pk3 (54 files)
Added packfile /usr/share/games/ufoai/base/0models.pk3 (2801 files)
Added packfile /usr/share/games/ufoai/base/0music.pk3 (65 files)
Added packfile /usr/share/games/ufoai/base/0pics.pk3 (875 files)
Added packfile /usr/share/games/ufoai/base/0shaders.pk3 (37 files)
Added packfile /usr/share/games/ufoai/base/0snd.pk3 (366 files)
Added packfile /usr/share/games/ufoai/base/0textures.pk3 (2720 files)
Added packfile /usr/share/games/ufoai/base/0ufos.pk3 (135 files)
Adding game dir: ./base
Added packfile ./base/0base.pk3 (14 files)
Added packfile ./base/0maps.pk3 (933 files)
Added packfile ./base/0materials.pk3 (54 files)
Added packfile ./base/0models.pk3 (2801 files)
Added packfile ./base/0music.pk3 (65 files)
Added packfile ./base/0pics.pk3 (875 files)
Added packfile ./base/0shaders.pk3 (37 files)
Added packfile ./base/0snd.pk3 (366 files)
Added packfile ./base/0textures.pk3 (2720 files)
Added packfile ./base/0ufos.pk3 (135 files)
Adding game dir: /home/libiko/.ufoai/2.5/base
using /home/libiko/.ufoai/2.5/base for writing
executing filesystem.cfg
executing default.cfg
executing config.cfg

- network initialization ---
libcurl/7.52.1 GnuTLS/3.5.8 zlib/1.2.8 libidn2/0.16 libpsl/0.17.0
(+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3 initialized.

-- server initialization ---
added 12 maps to the mapcycle

- console initialization ---
Console initialized.

--- video initialization ---
SDL version: 2.0.5
I: setting mode 24
I: disable multisample buffers
I: set swap control to 0
available driver: x11
available driver: wayland
available driver: dummy
current desktop mode: 1920x1080@60Hz (SDL_PIXELFORMAT_RGB888)
driver: x11
found 2 display(s)
use fake fullscreen for the first display: 1920:1080
I: 1920x1080 (fullscreen: yes)
I: got 24 bits of depth buffer
I: got double buffer
I: got 8 bits for red
I: got 8 bits for green
I: got 8 bits for blue
I: got 0 bits for alpha
I: got multisample disabled
I: got 0 multisample buffers
GL_VENDOR: X.Org
GL_RENDERER: Gallium 0.4 on AMD CAPE VERDE (DRM 2.48.0 / 4.9.0-2-amd64, LLVM
3.9.1)
GL_VERSION: 3.0 Mesa 13.0.6
GL_EXTENSIONS: GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color
GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_copy_texture
GL_EXT_polygon_offset GL_EXT_subtexture GL_EXT_texture_object
GL_EXT_vertex_array GL_EXT_compiled_vertex_array GL_EXT_texture
GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters
GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters
GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp
GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp
GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture
GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays
GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add
GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord
GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add
GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias
GL_INGR_blend_func_separate GL_NV_blend_square GL_NV_light_max_exponent
GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_S3_s3tc
GL_SUN_multi_draw_arrays GL_ARB_texture_border_clamp GL_ARB_texture_compression
GL_EXT_framebuffer_object GL_EXT_texture_compression_s3tc
GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_MESA_window_pos

Bug#837510: marked as done (mozart: Please replace build dependency on sp with opensp)

2017-05-07 Thread Debian Bug Tracking System

Your message dated Sun, 07 May 2017 18:09:19 +
with message-id 
and subject line Bug#862018: Removed package(s) from unstable
has caused the Debian Bug report #837510,
regarding mozart: Please replace build dependency on sp with opensp
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.)


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

The mozart package build depends on the obsolete package sp.  Please
change that to depend on the newer package opensp.  This change will
require changing all instances of the command nsgmls to onsgmls.

-- 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
--- End Message ---
--- Begin Message ---
Version: 1.4.0-8.1+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#728441: marked as done (mozart: FTBFS on 5 architectures where it built in the past)

2017-05-07 Thread Debian Bug Tracking System

Your message dated Sun, 07 May 2017 18:09:19 +
with message-id 
and subject line Bug#862018: Removed package(s) from unstable
has caused the Debian Bug report #728441,
regarding mozart: FTBFS on 5 architectures where it built in the past
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.)


-- 
728441: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mozart
Version: 1.4.0-8.1
Severity: serious

Hi Kevin and Sergei,

mozart/1.4.0-8.1 FTBFS on armel, kfreebsd-i386, powerpc and sparc.
However, previous version built there, so this failure blocks testing
migration (and therefore keeps the fix for #726030 out of testing).

NB: The state of the mipsel build is still undetermined, so please keep an
eye on that as well.

~Niels

Ref: https://buildd.debian.org/status/package.php?p=mozart
--- End Message ---
--- Begin Message ---
Version: 1.4.0-8.1+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#842208: marked as done (mozart-stdlib: FTBFS: dpkg-checkbuilddeps: error: Unmet build dependencies: mozart (>= 1.4.0))

2017-05-07 Thread Debian Bug Tracking System

Your message dated Sun, 07 May 2017 18:09:05 +
with message-id 
and subject line Bug#862020: Removed package(s) from unstable
has caused the Debian Bug report #842208,
regarding mozart-stdlib: FTBFS: dpkg-checkbuilddeps: error: Unmet build 
dependencies: mozart (>= 1.4.0)
to be marked as done.

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

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


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

Dear Maintainer,

mozart-stdlib fails to build from source in unstable/amd64:

  […]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  mozart-stdlib
   Version:  20060615-6
   Build architecture:   amd64
   Date: Wed, 26 Oct 2016 23:16:47 +0100
   Hostname: b6921c65188e
   Uname:Linux b6921c65188e 4.7.0-1-amd64 #1 SMP Debian 4.7.8-1 
(2016-10-19) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'mozart-stdlib-build-deps' in 
'../mozart-stdlib-build-deps_20060615-6_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package mozart-stdlib-build-deps.
  (Reading database ... 23467 files and directories currently installed.)
  Preparing to unpack mozart-stdlib-build-deps_20060615-6_all.deb ...
  Unpacking mozart-stdlib-build-deps (20060615-6) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following packages will be REMOVED:
mozart-stdlib-build-deps
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 9216 B disk space will be freed.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23471 files and directories currently installed.)
  Removing mozart-stdlib-build-deps (20060615-6) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=b6921c65188e
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20161026231645.tihYNoe0dk.db.mozart-stdlib/mozart-stdlib-20060615
  OLDPWD=/home/lamby/temp/cdt.20161026231645.tihYNoe0dk.db.mozart-stdlib
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env

Bug#822002: marked as done (mozart: Build arch:all+arch:any but is missing build-{arch,indep} targets)

2017-05-07 Thread Debian Bug Tracking System

Your message dated Sun, 07 May 2017 18:09:19 +
with message-id 
and subject line Bug#862018: Removed package(s) from unstable
has caused the Debian Bug report #822002,
regarding mozart: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
822002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mozart
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package mozart builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that mozart builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to mozart at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, mozart will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Version: 1.4.0-8.1+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#754020: marked as done (mozart: please switch to emacs24)

2017-05-07 Thread Debian Bug Tracking System

Your message dated Sun, 07 May 2017 18:09:19 +
with message-id 
and subject line Bug#862018: Removed package(s) from unstable
has caused the Debian Bug report #754020,
regarding mozart: please switch to emacs24
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.)


-- 
754020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mozart
Severity: normal
Tags: patch
User: r...@debian.org
Usertags: emacs24
Control: block 753885 by -1

Dear maintainer,

we're hoping to remove emacs23 from unstable/testing in future:

  https://bugs.debian.org/753885

Please migrate your dependencies to "emacs | emacsen" (or whatever's
more appropriate for your package) as soon as possible.  The attached
patch may help.

Thanks for considering.

--
mass bug filer on behalf of Rob Browning, emacs maintainer
--- mozart-1.4.0/debian/control.orig	2014-07-06 13:06:17.197496515 +0200
+++ mozart-1.4.0/debian/control	2014-07-06 13:06:36.601732956 +0200
@@ -6,7 +6,7 @@
 Homepage: http://www.mozart-oz.org/
 Vcs-Git: git://anonscm.debian.org/collab-maint/mozart.git
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/mozart.git
-Build-Depends: debhelper (>> 7.0.0), bison (>= 1.25), flex-old (>= 2.5.3), ghostscript, libgdbm-dev, libgmp-dev, m4, netpbm, sp, tcl8.5-dev, texlive, texlive-pstricks, tk8.5-dev, zlib1g-dev, emacs23 | emacs22 | xemacs21
+Build-Depends: debhelper (>> 7.0.0), bison (>= 1.25), flex-old (>= 2.5.3), ghostscript, libgdbm-dev, libgmp-dev, m4, netpbm, sp, tcl8.5-dev, texlive, texlive-pstricks, tk8.5-dev, zlib1g-dev, emacs | emacsen
 
 Package: mozart
 Architecture: hppa i386 m68k mipsel mips powerpc sparc s390 arm armeb armel kfreebsd-i386 sh4
--- End Message ---
--- Begin Message ---
Version: 1.4.0-8.1+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Processed: Re: Bug#862008: crashes, segmentation fault

2017-05-07 Thread Debian Bug Tracking System

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

> reassign 862008 python-pyatspi
Bug #862008 [gnome-orca] crashes, segmentation fault
Bug reassigned from package 'gnome-orca' to 'python-pyatspi'.
No longer marked as found in versions gnome-orca/3.22.2-3.
Ignoring request to alter fixed versions of bug #862008 to the same values 
previously set
> forwarded 862008 https://bugzilla.gnome.org/show_bug.cgi?id=767074
Bug #862008 [python-pyatspi] crashes, segmentation fault
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=767074'.
> found 862008 2.22.0-5
Bug #862008 [python-pyatspi] crashes, segmentation fault
There is no source info for the package 'python-pyatspi' at version '2.22.0-5' 
with architecture ''
Unable to make a source version for version '2.22.0-5'
Marked as found in versions 2.22.0-5.
> affects 862008 gnome-orca
Bug #862008 [python-pyatspi] crashes, segmentation fault
Added indication that 862008 affects gnome-orca
> tags 862008 confirmed
Bug #862008 [python-pyatspi] crashes, segmentation fault
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: Re: Bug#861979: ufoai: crashes with signal 11 at mission start

2017-05-07 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #861979 [ufoai] ufoai: crashes with signal 11 at mission start
Severity set to 'serious' from 'normal'
> tags -1 pending
Bug #861979 [ufoai] ufoai: crashes with signal 11 at mission start
Added tag(s) pending.

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

Bug#862008: crashes, segmentation fault

2017-05-07 Thread Mika Hanhijärvi


Ok, thanks for the info :-)


_ Mika




On 05/07/2017 05:49 PM, Joanmarie Diggs wrote:

I am looking at the line of code which caused the crash and it is the
same line of code as in the bug I reported. So you might have been doing
something different, but it appears to be the same bug which needs to be
fixed in AT-SPI2.

--joanie

On 05/07/2017 09:14 AM, Mika Hanhijärvi wrote:


If it is the same bug then I have to say I did not close any application
when Orca crashed. I also did not do anythything particularly fast. I am
not 100% sure what I Was doing but If I remember correctly I just
switched between virtual Gnome desktops which did have some application
windows open.




On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug:
https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is
not good
because blind users like me have to rely on screen reader working
reliably.
This, or similar, problem also existed before the latest update to
Orca in
Debian Stretch, so I do not know if this has anything to do with the
latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal
Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack
(most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184
in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in
_dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- 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/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 gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#861826: marked as done (heaptrack FTBFS on mips: tst_trace (Failed))

2017-05-07 Thread Debian Bug Tracking System

Your message dated Sun, 07 May 2017 17:20:15 +
with message-id 
and subject line Bug#861826: fixed in heaptrack 1.0.1~20170503.git4da8c45-2
has caused the Debian Bug report #861826,
regarding heaptrack FTBFS on mips: tst_trace (Failed)
to be marked as done.

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

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


-- 
861826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: heaptrack
Version: 1.0.1~20170503.git4da8c45-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=heaptrack=mips=1.0.1~20170503.git4da8c45-1=1493846157=0

...
cd /<>/debian/build ; /usr/bin/make test ARGS=-VV
make[2]: Entering directory '/<>/debian/build'
Running tests...
/usr/bin/ctest --force-new-ctest-process -VV
UpdateCTestConfiguration  from 
:/<>/debian/build/DartConfiguration.tcl
UpdateCTestConfiguration  from 
:/<>/debian/build/DartConfiguration.tcl
Test project /<>/debian/build
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 1
Start 1: tst_trace

1: Test command: /<>/debian/build/tests/auto/tst_trace
1: Test timeout computed to be: 9.99988e+06
1: 
1: 
~~~
1: tst_trace is a Catch v1.2.1 host application.
1: Run with -? for options
1: 
1: 
---
1: getting backtrace traces
1:   fill without skipping
1: 
---
1: /<>/tests/auto/tst_trace.cpp:48
1: 
...
1: 
1: /<>/tests/auto/tst_trace.cpp:53: FAILED:
1:   REQUIRE( trace.fill(0) )
1: with expansion:
1:   false
1: 
1: terminate called after throwing an instance of 'Catch::TestFailureException'
1: terminate called recursively
1: /<>/tests/auto/tst_trace.cpp:52: FAILED:
1:   {Unknown expression after the reported line}
1: due to a fatal error condition:
1:   SIGABRT - Abort (abnormal termination) signal
1: 
1: 
===
1: test cases: 1 | 1 failed
1: assertions: 5 | 3 passed | 2 failed
1: 
1/1 Test #1: tst_trace ***Failed0.01 sec

0% tests passed, 1 tests failed out of 1

Total Test time (real) =   0.03 sec

The following tests FAILED:
  1 - tst_trace (Failed)
Errors while running CTest
Makefile:86: recipe for target 'test' failed
make[2]: *** [test] Error 8
--- End Message ---
--- Begin Message ---
Source: heaptrack
Source-Version: 1.0.1~20170503.git4da8c45-2

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated heaptrack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 07 May 2017 19:16:18 +0200
Source: heaptrack
Binary: heaptrack heaptrack-gui libheaptrack
Architecture: source
Version: 1.0.1~20170503.git4da8c45-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 heaptrack  - Heap memory profiler for Linux
 heaptrack-gui - Heap memory profiler for Linux
 libheaptrack - Heap memory profiler for Linux
Closes: 861826
Changes:
 heaptrack (1.0.1~20170503.git4da8c45-2) unstable; urgency=medium
 .
   * [50e65ec] Disable unittests on mips due to crash in a third lib.
   (Closes: #861826)
   * [f7f6bed] Add d/watch.
   * [84c5439] Add simple autopkgtest.
Checksums-Sha1:
 1aae01cb25956c57dd384b14ebdb031db6fc6457 2565 
heaptrack_1.0.1~20170503.git4da8c45-2.dsc
 46e460b31befeb88ba82d0c50601f682db56ab80 6336 
heaptrack_1.0.1~20170503.git4da8c45-2.debian.tar.xz
 12fc1861f3c56787ba4dd1b72ef3b86bf69c4fac

Bug#861592: marked as done (node-dateformat: FTBFS: AssertionError: '1:19:44 PM GMT' === '1:19:44 PM UTC')

2017-05-07 Thread Debian Bug Tracking System

Your message dated Sun, 07 May 2017 16:04:10 +
with message-id 
and subject line Bug#861592: fixed in node-dateformat 1.0.11-3
has caused the Debian Bug report #861592,
regarding node-dateformat: FTBFS: AssertionError: '1:19:44 PM GMT' === '1:19:44 
PM UTC'
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.)


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

Dear Maintainer,

node-dateformat fails to build from source in unstable/amd64:

  […]

  dh build
 dh_testdir
 dh_update_autotools_config
 dh_auto_configure
 dh_auto_build
 debian/rules override_dh_auto_test
  make[1]: Entering directory '«BUILDDIR»'
  mocha -R spec
  
  [0m[0m
  [0m  dayOfWeek[0m
  
  [32m  ✓[0m[90m should correctly format the timezone part [0m
  
  [0m  dateformat([now], [mask])[0m
  
  [32m  ✓[0m[90m should format `default` mask [0m
  
  [32m  ✓[0m[90m should format `shortDate` mask [0m
  
  [32m  ✓[0m[90m should format `mediumDate` mask [0m
  
  [32m  ✓[0m[90m should format `longDate` mask [0m
  
  [32m  ✓[0m[90m should format `fullDate` mask [0m
  
  [32m  ✓[0m[90m should format `shortTime` mask [0m
  
  [32m  ✓[0m[90m should format `mediumTime` mask [0m
  
  [31m  1) should format `longTime` mask[0m
  
  [32m  ✓[0m[90m should format `isoDate` mask [0m
  
  [32m  ✓[0m[90m should format `isoTime` mask [0m
  
  [32m  ✓[0m[90m should format `isoDateTime` mask [0m
  
  [32m  ✓[0m[90m should format `isoUtcDateTime` mask [0m
  
  [31m  2) should format `expiresHeaderFormat` mask[0m
  
  [32m  ✓[0m[90m should use `default` mask, when `mask` is empty [0m
  
  [0m  isoUtcDateTime[0m
  
  [32m  ✓[0m[90m should correctly format the timezone part [0m
  
  
  [92m [0m[32m 14 passing[0m[90m (22ms)[0m
  [31m  2 failing[0m
  
  [0m  1) dateformat([now], [mask]) should format `longTime` mask:
  
[31mAssertionError: '1:19:44 PM GMT' === '1:19:44 PM UTC'[0m
[42m+ expected[0m [41m- actual[0m
  
[41m-1:19:44 PM GMT[0m
[42m+1:19:44 PM UTC[0m
[0m[90m
at Context. («BUILDDIR»/test/test_formats.js:64:14)
at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:196:15)
at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
at /usr/lib/nodejs/mocha/lib/runner.js:451:12
at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
at /usr/lib/nodejs/mocha/lib/runner.js:308:7
at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
at processImmediate [as _immediateCallback] (timers.js:396:17)
  [0m
  [0m  2) dateformat([now], [mask]) should format `expiresHeaderFormat` mask:
  
[31mAssertionError: 'Wed, 26 Nov 2014 13:19:44 GMT' === 'Wed, 26 Nov 
2014 13:19:44 UTC'[0m
[42m+ expected[0m [41m- actual[0m
  
[41m-Wed, 26 Nov 2014 13:19:44 GMT[0m
[42m+Wed, 26 Nov 2014 13:19:44 UTC[0m
[0m[90m
at Context. («BUILDDIR»/test/test_formats.js:64:14)
at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:196:15)
at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
at /usr/lib/nodejs/mocha/lib/runner.js:451:12
at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
at /usr/lib/nodejs/mocha/lib/runner.js:308:7
at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
at processImmediate [as _immediateCallback] (timers.js:396:17)
  [0m
  
  
  debian/rules:7: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 2
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:3: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


node-dateformat.1.0.11-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: node-dateformat

Bug#860952: fixed in rar 2:5.4.0+dfsg.1-0.1

2017-05-07 Thread Ivo De Decker

Hi Ben,

On Sun, May 07, 2017 at 03:44:14PM +0100, Ben Hutchings wrote:
> > On Thu, May 04, 2017 at 04:03:36AM +, Ben Hutchings wrote:
> > > Files:
> > >  6e4f05c3a05bc43f3eaab0da36e6d163 2015 non-free/utils optional 
> > > rar_5.4.0+dfsg.1-0.1.dsc
> > >  d02b8742478d5e6428c12ee14b2a678d 531782 non-free/utils optional 
> > > rar_5.4.0+dfsg.1.orig-amd64.tar.gz
> > >  efa2a5a29f57f34999a9bae355510618 541123 non-free/utils optional 
> > > rar_5.4.0+dfsg.1.orig.tar.gz
> > >  a8223a408d2e8e3be2e73caf21da259d 9124 non-free/utils optional 
> > > rar_5.4.0+dfsg.1-0.1.debian.tar.xz
> > >  aa92212e604f7c183d5a56d7dfc2a6dd 5637 non-free/utils optional 
> > > rar_5.4.0+dfsg.1-0.1_source.buildinfo
> > 
> > Please note that rar isn't autobuilt. So the binaries for amd64 and i386 
> > need
> > to be uploaded manually.
> 
> debian/control and debian/copyright say it is!

According to devref, someone needs to send a mail to
nonf...@release.debian.org and ask to put in on the list of autobuilt
packages.

https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd

Looking at /srv/wanna-build/etc/non-free-include-list (on buildd.debian.org),
rar isn't on that list.

It looks like the builds for rar 5.4.0+dfsg.1-0.1 are uploaded. Thanks for
that.

Cheers,

Ivo

Bug#862008: crashes, segmentation fault

2017-05-07 Thread Joanmarie Diggs

I am looking at the line of code which caused the crash and it is the
same line of code as in the bug I reported. So you might have been doing
something different, but it appears to be the same bug which needs to be
fixed in AT-SPI2.

--joanie

On 05/07/2017 09:14 AM, Mika Hanhijärvi wrote:
> 
> 
> If it is the same bug then I have to say I did not close any application
> when Orca crashed. I also did not do anythything particularly fast. I am
> not 100% sure what I Was doing but If I remember correctly I just
> switched between virtual Gnome desktops which did have some application
> windows open.
> 
> 
> 
> 
> On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:
>> That is this AT-SPI2 bug:
>> https://bugzilla.gnome.org/show_bug.cgi?id=767074
>>
>> --joanie
>>
>> On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:
>>> Package: gnome-orca
>>> Version: 3.22.2-3
>>> Severity: grave
>>>
>>> Orca seems to sometime crash suddenly without any warning. This is
>>> not good
>>> because blind users like me have to rely on screen reader working
>>> reliably.
>>> This, or similar, problem also existed before the latest update to
>>> Orca in
>>> Debian Stretch, so I do not know if this has anything to do with the
>>> latest
>>> Orca update.
>>>
>>> There are these lines in the /var/log/syslog
>>>
>>> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal
>>> Python error:
>>> Segmentation fault
>>> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack
>>> (most recent
>>> call first):
>>> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
>>> "/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184
>>> in 
>>> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
>>> "/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
>>> _queuePrintln
>>> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
>>> "/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in
>>> _dequeue
>>> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
>>> "/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
>>> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
>>> "/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
>>> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
>>> "/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
>>> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
>>> "/usr/bin/orca", line 269 in main
>>> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
>>> "/usr/bin/orca", line 272 in 
>>>
>>>
>>>
>>>
>>> -- 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/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 gnome-orca depends on:
>>> ii  gir1.2-glib-2.01.50.0-1+b1
>>> ii  gir1.2-gtk-3.0 3.22.11-1
>>> ii  gir1.2-pango-1.0   1.40.5-1
>>> ii  gir1.2-wnck-3.03.20.1-3
>>> ii  gsettings-desktop-schemas  3.22.0-1
>>> ii  python3-brlapi 5.4-7
>>> ii  python3-cairo  1.10.0+dfsg-5+b1
>>> ii  python3-gi 3.22.0-2
>>> ii  python3-louis  3.0.0-3
>>> ii  python3-pyatspi2.20.3+dfsg-1
>>> ii  python3-speechd0.8.6-4
>>> pn  python3:any
>>> ii  speech-dispatcher  0.8.6-4
>>>
>>> Versions of packages gnome-orca recommends:
>>> ii  libgail-common  2.24.31-2
>>> ii  xbrlapi 5.4-7
>>>
>>> gnome-orca suggests no packages.
>>>
>>> -- no debconf information
>>>
>>>
> 
>

Bug#860952: fixed in rar 2:5.4.0+dfsg.1-0.1

2017-05-07 Thread Ben Hutchings

On Sun, 2017-05-07 at 15:29 +0200, Ivo De Decker wrote:
> Hi Ben,
> 
> On Thu, May 04, 2017 at 04:03:36AM +, Ben Hutchings wrote:
> > Files:
> >  6e4f05c3a05bc43f3eaab0da36e6d163 2015 non-free/utils optional 
> > rar_5.4.0+dfsg.1-0.1.dsc
> >  d02b8742478d5e6428c12ee14b2a678d 531782 non-free/utils optional 
> > rar_5.4.0+dfsg.1.orig-amd64.tar.gz
> >  efa2a5a29f57f34999a9bae355510618 541123 non-free/utils optional 
> > rar_5.4.0+dfsg.1.orig.tar.gz
> >  a8223a408d2e8e3be2e73caf21da259d 9124 non-free/utils optional 
> > rar_5.4.0+dfsg.1-0.1.debian.tar.xz
> >  aa92212e604f7c183d5a56d7dfc2a6dd 5637 non-free/utils optional 
> > rar_5.4.0+dfsg.1-0.1_source.buildinfo
> 
> Please note that rar isn't autobuilt. So the binaries for amd64 and i386 need
> to be uploaded manually.

debian/control and debian/copyright say it is!

Ben.

-- 
Ben Hutchings
[W]e found...that it wasn't as easy to get programs right as we had
thought.
... I realized that a large part of my life from then on was going to
be spent
in finding mistakes in my own programs. - Maurice Wilkes, 1949



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

Processed: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3

2017-05-07 Thread Debian Bug Tracking System

Processing control commands:

> tags 860224 + patch
Bug #860224 [src:bind9] bind9: CVE-2017-3136: An error handling synthesized 
records could cause an assertion failure when using DNS64 with "break-dnssec 
yes;"
Ignoring request to alter tags of bug #860224 to the same tags previously set
> tags 860224 + pending
Bug #860224 [src:bind9] bind9: CVE-2017-3136: An error handling synthesized 
records could cause an assertion failure when using DNS64 with "break-dnssec 
yes;"
Ignoring request to alter tags of bug #860224 to the same tags previously set
> tags 860225 + pending
Bug #860225 [src:bind9] bind9: CVE-2017-3137: A response packet can cause a 
resolver to terminate when processing an answer containing a CNAME or DNAME
Ignoring request to alter tags of bug #860225 to the same tags previously set
> tags 860226 + patch
Bug #860226 [src:bind9] bind9: CVE-2017-3138: named exits with a REQUIRE 
assertion failure if it receives a null command string on its control channel
Ignoring request to alter tags of bug #860226 to the same tags previously set
> tags 860226 + pending
Bug #860226 [src:bind9] bind9: CVE-2017-3138: named exits with a REQUIRE 
assertion failure if it receives a null command string on its control channel
Ignoring request to alter tags of bug #860226 to the same tags previously set

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

Processed: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3

2017-05-07 Thread Debian Bug Tracking System

Processing control commands:

> tags 860224 + patch
Bug #860224 [src:bind9] bind9: CVE-2017-3136: An error handling synthesized 
records could cause an assertion failure when using DNS64 with "break-dnssec 
yes;"
Added tag(s) patch.
> tags 860224 + pending
Bug #860224 [src:bind9] bind9: CVE-2017-3136: An error handling synthesized 
records could cause an assertion failure when using DNS64 with "break-dnssec 
yes;"
Added tag(s) pending.
> tags 860225 + pending
Bug #860225 [src:bind9] bind9: CVE-2017-3137: A response packet can cause a 
resolver to terminate when processing an answer containing a CNAME or DNAME
Added tag(s) pending.
> tags 860226 + patch
Bug #860226 [src:bind9] bind9: CVE-2017-3138: named exits with a REQUIRE 
assertion failure if it receives a null command string on its control channel
Added tag(s) patch.
> tags 860226 + pending
Bug #860226 [src:bind9] bind9: CVE-2017-3138: named exits with a REQUIRE 
assertion failure if it receives a null command string on its control channel
Added tag(s) pending.

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

Processed: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3

2017-05-07 Thread Debian Bug Tracking System

Processing control commands:

> tags 860224 + patch
Bug #860224 [src:bind9] bind9: CVE-2017-3136: An error handling synthesized 
records could cause an assertion failure when using DNS64 with "break-dnssec 
yes;"
Ignoring request to alter tags of bug #860224 to the same tags previously set
> tags 860224 + pending
Bug #860224 [src:bind9] bind9: CVE-2017-3136: An error handling synthesized 
records could cause an assertion failure when using DNS64 with "break-dnssec 
yes;"
Ignoring request to alter tags of bug #860224 to the same tags previously set
> tags 860225 + pending
Bug #860225 [src:bind9] bind9: CVE-2017-3137: A response packet can cause a 
resolver to terminate when processing an answer containing a CNAME or DNAME
Ignoring request to alter tags of bug #860225 to the same tags previously set
> tags 860226 + patch
Bug #860226 [src:bind9] bind9: CVE-2017-3138: named exits with a REQUIRE 
assertion failure if it receives a null command string on its control channel
Ignoring request to alter tags of bug #860226 to the same tags previously set
> tags 860226 + pending
Bug #860226 [src:bind9] bind9: CVE-2017-3138: named exits with a REQUIRE 
assertion failure if it receives a null command string on its control channel
Ignoring request to alter tags of bug #860226 to the same tags previously set

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

Bug#860225: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3

2017-05-07 Thread Salvatore Bonaccorso

Control: tags 860224 + patch
Control: tags 860224 + pending
Control: tags 860225 + pending
Control: tags 860226 + patch
Control: tags 860226 + pending

Dear maintainer,

I've prepared an NMU for bind9 (versioned as 1:9.10.3.dfsg.P4-12.3) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Please note, I could not test bind9 under real conditions with those
patches. The testsuite passed though the dname tests.

I'm cc'ing as well Mike and Florian for possible review.

Furthermore the version for jessie ist still not yet done.

Regards,
Salvatore
diff -Nru bind9-9.10.3.dfsg.P4/debian/changelog 
bind9-9.10.3.dfsg.P4/debian/changelog
--- bind9-9.10.3.dfsg.P4/debian/changelog   2017-04-18 17:42:50.0 
+0200
+++ bind9-9.10.3.dfsg.P4/debian/changelog   2017-05-07 15:22:46.0 
+0200
@@ -1,3 +1,15 @@
+bind9 (1:9.10.3.dfsg.P4-12.3) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Dns64 with "break-dnssec yes;" can result in a assertion failure
+(CVE-2017-3136) (Closes: #860224)
+  * Some chaining (CNAME or DNAME) responses to upstream queries could trigger
+assertion failures (CVE-2017-3137) (Closes: #860225)
+  * 'rndc ""' could trigger a assertion failure in named (CVE-2017-3138)
+(Closes: #860226)
+
+ -- Salvatore Bonaccorso   Sun, 07 May 2017 15:22:46 +0200
+
 bind9 (1:9.10.3.dfsg.P4-12.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru bind9-9.10.3.dfsg.P4/debian/patches/CVE-2017-3136.patch 
bind9-9.10.3.dfsg.P4/debian/patches/CVE-2017-3136.patch
--- bind9-9.10.3.dfsg.P4/debian/patches/CVE-2017-3136.patch 1970-01-01 
01:00:00.0 +0100
+++ bind9-9.10.3.dfsg.P4/debian/patches/CVE-2017-3136.patch 2017-05-07 
15:22:46.0 +0200
@@ -0,0 +1,19 @@
+From 764240ca07ab1b796226d5402ccd9fbfa77ec32a Mon Sep 17 00:00:00 2001
+From: Mark Andrews 
+Date: Wed, 15 Feb 2017 12:18:51 +1100
+Subject: [PATCH] 4575.   [security]  Dns64 with break-dnssec yes; can
+ result in a assertion failure. (CVE-2017-3136) [RT
+ #44653]
+
+(cherry picked from commit 3bce12e4b6d37f570ffc7747b499f8b90e8521ac)
+---
+--- a/bin/named/query.c
 b/bin/named/query.c
+@@ -8145,6 +8145,7 @@ query_find(ns_client_t *client, dns_fetc
+   result = query_dns64(client, , rdataset,
+sigrdataset, dbuf,
+DNS_SECTION_ANSWER);
++  noqname = NULL;
+   dns_rdataset_disassociate(rdataset);
+   dns_message_puttemprdataset(client->message, );
+   if (result == ISC_R_NOMORE) {
diff -Nru bind9-9.10.3.dfsg.P4/debian/patches/CVE-2017-3137-1.patch 
bind9-9.10.3.dfsg.P4/debian/patches/CVE-2017-3137-1.patch
--- bind9-9.10.3.dfsg.P4/debian/patches/CVE-2017-3137-1.patch   1970-01-01 
01:00:00.0 +0100
+++ bind9-9.10.3.dfsg.P4/debian/patches/CVE-2017-3137-1.patch   2017-05-07 
15:22:46.0 +0200
@@ -0,0 +1,83 @@
+From 69fd759b4aa02047e42e5cf4227f8257c4547988 Mon Sep 17 00:00:00 2001
+From: Evan Hunt 
+Date: Thu, 23 Feb 2017 15:01:30 -0800
+Subject: [PATCH] [v9_10] remove unnecessary INSIST and prep 9.10.5rc2
+
+4578.  [security]  Some chaining (CNAME or DNAME) responses to upstream
+   queries could trigger assertion failures.
+   (CVE-2017-3137) [RT #44734]
+
+(cherry picked from commit a1365a0042db8c1cd0ee4dbd0c91ce65ae09e098)
+(cherry picked from commit 559cbe04e73cf601784a371e09554c20407a6c7b)
+---
+--- a/lib/dns/resolver.c
 b/lib/dns/resolver.c
+@@ -6924,15 +6924,15 @@ answer_response(fetchctx_t *fctx) {
+   rdataset->attributes |=
+   DNS_RDATASETATTR_CACHE;
+   rdataset->trust = dns_trust_answer;
+-  if (chaining == 0) {
++  if (external) {
+   /*
+-   * This data is "the" answer
+-   * to our question only if
+-   * we're not chaining (i.e.
+-   * if we haven't followed
+-   * a CNAME or DNAME).
++   * This data is outside of
++   * our query domain, and
++   * may not be cached.
+*/
+-  INSIST(!external);
++  rdataset->attributes |=
++  DNS_RDATASETATTR_EXTERNAL;
++

Processed: gufw should depend on net-tools (crashes without it)

2017-05-07 Thread Debian Bug Tracking System

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

> severity 855400 serious
Bug #855400 [gufw] gufw should depend on net-tools (crashes without it)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#862027: serf: FTBFS in stretch ("There were 14 failures")

2017-05-07 Thread Santiago Vila

Package: src:serf
Version: 1.3.9-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-arch
QUILT_PATCHES=debian/patches \
quilt --quiltrc /dev/null push -a || test $? = 2
Applying patch libtool
patching file SConstruct

Now at patch libtool
touch debian/stamp-patched
dh_testdir
scons -j 1 GSSAPI=/usr CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LINKFLAGS="-specs=/usr/share/dpkg/no-pie-link.specs -Wl,-z,relro -Wl,-z,now 
-Wl,-z,defs -Wl,--as-needed" PREFIX=/usr LIBDIR=/usr/lib/x86_64-linux-gnu
scons: Reading SConscript files ...
Checking for GNU-compatible C compiler...yes
scons: done reading SConscript files.
scons: Building targets ...
gcc -o context.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
context.c
gcc -o incoming.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
incoming.c
gcc -o outgoing.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
outgoing.c
gcc -o ssltunnel.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
ssltunnel.c
gcc -o buckets/aggregate_buckets.o -c -g -O2 
-fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
buckets/aggregate_buckets.c
gcc -o buckets/allocator.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
buckets/allocator.c
gcc -o buckets/barrier_buckets.o -c -g -O2 
-fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
buckets/barrier_buckets.c
gcc -o buckets/buckets.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include 
buckets/buckets.c
gcc -o buckets/bwtp_buckets.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -std=c89 -Wdeclaration-after-statement 
-Wmissing-prototypes -Wall -O2 -pthread -isystem /usr/include/mit-krb5 
-Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DLINUX -D_REENTRANT -D_GNU_SOURCE 
-DSERF_HAVE_GSSAPI -I. -I/usr/include/apr-1.0 -I/usr/include -I/usr/include

Bug#861074: cryptsetup: cryptroot-hook doesn't honor initramfs-tools' (>= 0.129) logic for resume devices

2017-05-07 Thread Jochen

Package: cryptsetup
Version: 2:1.7.3-3
Followup-For: Bug #861074

Applying the fix from the cryptsetup git also eliminates a 30sec sleep during
boot when the resume device is not found. +1 from me.


-- Package-specific info:
-- /proc/cmdline
root=UUID=0556bb4e-09e2-48ee-ba4c-729e7a22eee3 ro quiet rootfstype=ext4 
add_efi_memmap initrd=\EFI\debian\initrd.img

-- /etc/crypttab
sda2_crypt /dev/sda2 /dev/urandom cipher=aes-xts-plain64,size=256,swap
#sda4_crypt UUID=5abbd8f2-9615-46fd-a4a7-a18c74400eb2 none luks

-- /etc/fstab
/dev/sda3 / ext4  errors=remount-ro 0 1
/dev/sda1 /boot/efi vfat  errors=remount-ro 0 0
/dev/sdb1 /mnt  vfat user,noauto   0 0

-- lsmod
Module  Size  Used by
fuse   98304  3
algif_skcipher 20480  0
af_alg 16384  1 algif_skcipher
ctr16384  2
ccm20480  1
joydev 20480  0
btusb  45056  0
btrtl  16384  1 btusb
uvcvideo   90112  0
videobuf2_vmalloc  16384  1 uvcvideo
videobuf2_memops   16384  1 videobuf2_vmalloc
videobuf2_v4l2 24576  1 uvcvideo
videobuf2_core 36864  2 uvcvideo,videobuf2_v4l2
videodev  176128  3 uvcvideo,videobuf2_core,videobuf2_v4l2
media  40960  2 uvcvideo,videodev
arc4   16384  2
intel_rapl 20480  0
x86_pkg_temp_thermal16384  0
intel_powerclamp   16384  0
coretemp   16384  0
kvm_intel 192512  0
snd_hda_codec_hdmi 49152  1
snd_soc_skl65536  0
kvm   589824  1 kvm_intel
snd_hda_codec_realtek90112  1
snd_soc_skl_ipc45056  1 snd_soc_skl
irqbypass  16384  1 kvm
snd_hda_codec_generic69632  1 snd_hda_codec_realtek
snd_soc_sst_ipc16384  1 snd_soc_skl_ipc
snd_soc_sst_dsp28672  1 snd_soc_skl_ipc
crct10dif_pclmul   16384  0
snd_hda_ext_core   28672  1 snd_soc_skl
crc32_pclmul   16384  0
snd_soc_sst_match  16384  1 snd_soc_skl
snd_soc_core  212992  1 snd_soc_skl
ghash_clmulni_intel16384  0
iwlmvm245760  0
snd_compress   20480  1 snd_soc_core
intel_cstate   16384  0
mac80211  671744  1 iwlmvm
iwlwifi   147456  1 iwlmvm
cfg80211  589824  3 iwlmvm,iwlwifi,mac80211
iTCO_wdt   16384  0
iTCO_vendor_support16384  1 iTCO_wdt
dm_crypt   24576  2
dm_mod118784  4 dm_crypt
nls_ascii  16384  1
nls_cp437  20480  1
vfat   20480  1
fat69632  1 vfat
snd_hda_intel  36864  1
intel_uncore  118784  0
snd_hda_codec 135168  4 
snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_core   81920  7 
snd_hda_intel,snd_hda_codec,snd_hda_ext_core,snd_soc_skl,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
xhci_pci   16384  0
snd_hwdep  16384  1 snd_hda_codec
i915 1232896  4
xhci_hcd  188416  1 xhci_pci
intel_rapl_perf16384  0
snd_pcm   110592  7 
snd_hda_intel,snd_hda_codec,snd_hda_ext_core,snd_hda_core,snd_soc_skl,snd_hda_codec_hdmi,snd_soc_core
efi_pstore 16384  0
drm_kms_helper155648  1 i915
usbcore   249856  4 uvcvideo,xhci_pci,btusb,xhci_hcd
drm   360448  5 i915,drm_kms_helper
snd_timer  32768  1 snd_pcm
hci_uart   98304  0
efivars20480  1 efi_pstore
i2c_algo_bit   16384  1 i915
btbcm  16384  2 hci_uart,btusb
shpchp 36864  0
snd86016  12 
snd_compress,snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek,snd_soc_core,snd_pcm
psmouse   135168  0
i2c_i801   24576  0
btqca  16384  1 hci_uart
usb_common 16384  1 usbcore
mei_me 36864  0
btintel16384  2 hci_uart,btusb
sg 32768  0
i2c_smbus  16384  1 i2c_i801
soundcore  16384  1 snd
intel_pch_thermal  16384  0
mei   102400  1 mei_me
pcspkr 16384  0
battery20480  0
bluetooth 552960  7 btrtl,hci_uart,btintel,btqca,btbcm,btusb
rfkill 24576  4 bluetooth,cfg80211
intel_lpss_acpi16384  0
button 16384  1 i915
intel_lpss 16384  1 intel_lpss_acpi
video  40960  1 i915
mfd_core   16384  1 intel_lpss
i2c_hid20480  0
hid   122880  1 i2c_hid
acpi_pad   24576  0
ac 16384  0
efivarfs   16384  1
ip_tables  24576  0
x_tables   36864  1 ip_tables
autofs440960  2
ext4  585728  2
crc16

Processed: tagging -ignore

2017-05-07 Thread Debian Bug Tracking System

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

> # arch:all failure on i386 which builds fine on amd64
> tags 860687 stretch-ignore
Bug #860687 [src:cross-toolchain-base] cross-toolchain-base: FTBFS on i386: 
configure: error: cannot compute suffix of object files: cannot compile
Added tag(s) stretch-ignore.
> tags 860626 stretch-ignore
Bug #860626 [src:cross-toolchain-base-ports] cross-toolchain-base-ports: FTBFS 
on i386: configure: error: cannot compute suffix of object files: cannot compile
Added tag(s) stretch-ignore.
> thanks
Stopping processing here.

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

Processed: Re: Bug#860650: zookeeper: FTBFS on i386: java.io.FileNotFoundException: /home/user42/.ant/cache/resolved-org.apache.zookeeper-zookeeper-3.4.9-2.xml (No such file or directory)

2017-05-07 Thread Debian Bug Tracking System

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

> # arch:all failure on i386, which builds fine on amd64
> tags 860650 stretch-ignore
Bug #860650 [src:zookeeper] zookeeper: FTBFS on i386:   
java.io.FileNotFoundException: 
/home/user42/.ant/cache/resolved-org.apache.zookeeper-zookeeper-3.4.9-2.xml (No 
such file or directory)
Added tag(s) stretch-ignore.
> thanks
Stopping processing here.

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

Bug#862008: crashes, segmentation fault

2017-05-07 Thread Mika Hanhijärvi

When I read the discussion in Gnome bug page I see that some people have 
regular Orca crashes which happen often e.g when they close some 
application. Luckily I have not noticed problem like that. Orca crashes 
do not happen often or regularly on my computer, just sometimes. I also 
have not had Orca crashes when I have closed applications. I think those 
crashes have happened mostly when I have switched between apps running 
on different Gnome virtual desktops. I run just one application on each 
virtual desktop.






On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug: https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is not good
because blind users like me have to rely on screen reader working reliably.
This, or similar, problem also existed before the latest update to Orca in
Debian Stretch, so I do not know if this has anything to do with the latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- 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/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 gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#861957: marked as done (raincat: Raincat doesn't run: user error (unknown GLUT entry glutInit))

2017-05-07 Thread Debian Bug Tracking System

Your message dated Sun, 07 May 2017 09:16:21 -0400
with message-id <1494162981.1219.1.ca...@debian.org>
and subject line Re: Bug#861976: libghc-glut-dev: attempts to load libglut.so 
instead of libglut.so.3
has caused the Debian Bug report #861957,
regarding raincat: Raincat doesn't run: user error (unknown GLUT entry glutInit)
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.)


-- 
861957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: raincat
Version: 1.1.1.2-3+b1
Severity: important

Dear Maintainer,

when trying to run raincat, the program silently quits. When ran via console it
outputs the following error: user error (unknown GLUT entry glutInit)

I'm attaching output of $ldd /usr/games/raincat

Best Regards,
Andrej Mernik



-- 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/4 CPU cores)
Locale: LANG=sl_SI.UTF-8, LC_CTYPE=sl_SI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages raincat depends on:
ii  libc6 2.24-10
ii  libffi6   3.2.1-6
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgmp10  2:6.1.2+dfsg-1
ii  libsdl-image1.2   1.2.12-5+b8
ii  libsdl-mixer1.2   1.2.12-11+b3
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  raincat-data  1.1.1.2-3

raincat recommends no packages.

raincat suggests no packages.
linux-vdso.so.1 (0x7ffc3f1bb000)
libSDL_mixer-1.2.so.0 => 
/usr/lib/x86_64-linux-gnu/libSDL_mixer-1.2.so.0 (0x7fcf7ea64000)
libSDL_image-1.2.so.0 => 
/usr/lib/x86_64-linux-gnu/libSDL_image-1.2.so.0 (0x7fcf7e846000)
libSDL-1.2.so.0 => /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 
(0x7fcf7e5ac000)
libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1 
(0x7fcf7e33d000)
libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x7fcf7e0cb000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
(0x7fcf7de46000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fcf7db42000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fcf7d93a000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fcf7d736000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 
(0x7fcf7d52d000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fcf7d18f000)
libmikmod.so.3 => /usr/lib/x86_64-linux-gnu/libmikmod.so.3 
(0x7fcf7cf49000)
libfluidsynth.so.1 => /usr/lib/x86_64-linux-gnu/libfluidsynth.so.1 
(0x7fcf7cc8)
libvorbisfile.so.3 => /usr/lib/x86_64-linux-gnu/libvorbisfile.so.3 
(0x7fcf7ca77000)
libFLAC.so.8 => /usr/lib/x86_64-linux-gnu/libFLAC.so.8 
(0x7fcf7c80)
libmad.so.0 => /usr/lib/x86_64-linux-gnu/libmad.so.0 
(0x7fcf7c5e)
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 
(0x7fcf7c3ad000)
libjpeg.so.62 => /usr/lib/x86_64-linux-gnu/libjpeg.so.62 
(0x7fcf7c14)
libtiff.so.5 => /usr/lib/x86_64-linux-gnu/libtiff.so.5 
(0x7fcf7beca000)
libwebp.so.6 => /usr/lib/x86_64-linux-gnu/libwebp.so.6 
(0x7fcf7bc69000)
libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 
(0x7fcf7b95c000)
libpulse-simple.so.0 => /usr/lib/x86_64-linux-gnu/libpulse-simple.so.0 
(0x7fcf7b757000)
libpulse.so.0 => /usr/lib/x86_64-linux-gnu/libpulse.so.0 
(0x7fcf7b506000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 
(0x7fcf7b1c4000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 
(0x7fcf7afb2000)
libcaca.so.0 => /usr/lib/x86_64-linux-gnu/libcaca.so.0 
(0x7fcf7ace9000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fcf7aacc000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fcf7a74a000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fcf7a533000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 
(0x7fcf7a307000)
libxcb-dri3.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 
(0x7fcf7a104000)
libxcb-present.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-present.so.0 
(0x7fcf79f01000)
libxcb-sync.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-sync.so.1 
(0x7fcf79cfa000)

Bug#860952: fixed in rar 2:5.4.0+dfsg.1-0.1

2017-05-07 Thread Ivo De Decker

Hi Ben,

On Thu, May 04, 2017 at 04:03:36AM +, Ben Hutchings wrote:
> Files:
>  6e4f05c3a05bc43f3eaab0da36e6d163 2015 non-free/utils optional 
> rar_5.4.0+dfsg.1-0.1.dsc
>  d02b8742478d5e6428c12ee14b2a678d 531782 non-free/utils optional 
> rar_5.4.0+dfsg.1.orig-amd64.tar.gz
>  efa2a5a29f57f34999a9bae355510618 541123 non-free/utils optional 
> rar_5.4.0+dfsg.1.orig.tar.gz
>  a8223a408d2e8e3be2e73caf21da259d 9124 non-free/utils optional 
> rar_5.4.0+dfsg.1-0.1.debian.tar.xz
>  aa92212e604f7c183d5a56d7dfc2a6dd 5637 non-free/utils optional 
> rar_5.4.0+dfsg.1-0.1_source.buildinfo

Please note that rar isn't autobuilt. So the binaries for amd64 and i386 need
to be uploaded manually.

Cheers,

Ivo

Bug#861468: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED

2017-05-07 Thread Ivo De Decker

Hi,

On Sun, May 07, 2017 at 12:51:00PM +0200, Florian Vessaz wrote:
> > If you can't reproduce, feel feel to close...
> 
> Could you try a build on your system with the above Dockerfile?

Please note that this message (and the one before) was sent to the wrong bug.
It was meant for #861523 (which is about bup), but was sent to #861468 (which
is about php-monolog).

Please follow up to #861523.

Cheers,

Ivo

Bug#862008: crashes, segmentation fault

2017-05-07 Thread Mika Hanhijärvi




If it is the same bug then I have to say I did not close any application 
when Orca crashed. I also did not do anythything particularly fast. I am 
not 100% sure what I Was doing but If I remember correctly I just 
switched between virtual Gnome desktops which did have some application 
windows open.





On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug: https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is not good
because blind users like me have to rely on screen reader working reliably.
This, or similar, problem also existed before the latest update to Orca in
Debian Stretch, so I do not know if this has anything to do with the latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- 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/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 gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862008: crashes, segmentation fault

2017-05-07 Thread Joanmarie Diggs

That is this AT-SPI2 bug: https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:
> Package: gnome-orca
> Version: 3.22.2-3
> Severity: grave
> 
> Orca seems to sometime crash suddenly without any warning. This is not good
> because blind users like me have to rely on screen reader working reliably.
> This, or similar, problem also existed before the latest update to Orca in
> Debian Stretch, so I do not know if this has anything to do with the latest
> Orca update.
> 
> There are these lines in the /var/log/syslog
> 
> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python 
> error:
> Segmentation fault
> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
> call first):
> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
> "/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
> 
> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
> "/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
> _queuePrintln
> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
> "/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
> "/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
> "/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
> "/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
> "/usr/bin/orca", line 269 in main
> May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
> "/usr/bin/orca", line 272 in 
> 
> 
> 
> 
> -- 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/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 gnome-orca depends on:
> ii  gir1.2-glib-2.01.50.0-1+b1
> ii  gir1.2-gtk-3.0 3.22.11-1
> ii  gir1.2-pango-1.0   1.40.5-1
> ii  gir1.2-wnck-3.03.20.1-3
> ii  gsettings-desktop-schemas  3.22.0-1
> ii  python3-brlapi 5.4-7
> ii  python3-cairo  1.10.0+dfsg-5+b1
> ii  python3-gi 3.22.0-2
> ii  python3-louis  3.0.0-3
> ii  python3-pyatspi2.20.3+dfsg-1
> ii  python3-speechd0.8.6-4
> pn  python3:any
> ii  speech-dispatcher  0.8.6-4
> 
> Versions of packages gnome-orca recommends:
> ii  libgail-common  2.24.31-2
> ii  xbrlapi 5.4-7
> 
> gnome-orca suggests no packages.
> 
> -- no debconf information
> 
>

Processed: Tinyca is incompatible with openssl 1.1

2017-05-07 Thread Debian Bug Tracking System

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

> severity 839575 serious
Bug #839575 [tinyca] hangs waiting for openssl
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#860225: bind9: CVE-2017-3137: A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME

2017-05-07 Thread Cédric Dufour - Idiap Research Institute

Same here.

Multi/redundant DNS servers do not help, the culprit recursive query being sent 
multiple times by client as each DNS server falls in turn.
And multi- firewall/IPS doesn't help catching the faulty packets :-(

I may state the obvious, but only workaround so far is (already saved the night 
a few times):
$ cat /etc/cron.d/cve-2017-3137 
# Make sure BIND9 has not crashed (cf. CVE-2017-3137)
* * * * * root pgrep named >/dev/null || service bind9 restart
(not so elegant however)

Any hope Debian/Stable BIND gets patched ?
(that's a pretty severe DoS vulnerability we have here)

Thanks and sincerily,

Cédric

Processed: Add tags and change severity

2017-05-07 Thread Debian Bug Tracking System

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

> tags 861975 = moreinfo unreproducible
Bug #861975 [audacity] audacity doesn't start
Added tag(s) moreinfo and unreproducible.
> severity 861975 important
Bug #861975 [audacity] audacity doesn't start
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#861305: marked as done (python-cairo-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

2017-05-07 Thread Debian Bug Tracking System

Your message dated Sun, 07 May 2017 12:04:38 +
with message-id 
and subject line Bug#861305: fixed in pycairo 1.8.8-2.2
has caused the Debian Bug report #861305,
regarding python-cairo-dbg: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
to be marked as done.

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

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


-- 
861305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cairo-dbg
Version: 1.8.8-2.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths on i386:

  lenny -> squeeze -> wheezy -> jessie -> stretch

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

4m41.3s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python-cairo-dbg/AUTHORS (python-cairo-dbg) != 
/usr/share/doc/python-cairo/AUTHORS (python-cairo)
/usr/share/doc/python-cairo-dbg -> python-cairo
  /usr/share/doc/python-cairo-dbg/NEWS.gz (python-cairo-dbg) != 
/usr/share/doc/python-cairo/NEWS.gz (python-cairo)
/usr/share/doc/python-cairo-dbg -> python-cairo
  /usr/share/doc/python-cairo-dbg/README (python-cairo-dbg) != 
/usr/share/doc/python-cairo/README (python-cairo)
/usr/share/doc/python-cairo-dbg -> python-cairo
  /usr/share/doc/python-cairo-dbg/changelog.Debian.gz (python-cairo-dbg) != 
/usr/share/doc/python-cairo/changelog.Debian.gz (python-cairo)
/usr/share/doc/python-cairo-dbg -> python-cairo
  /usr/share/doc/python-cairo-dbg/copyright (python-cairo-dbg) != 
/usr/share/doc/python-cairo/copyright (python-cairo)
/usr/share/doc/python-cairo-dbg -> python-cairo


cheers,

Andreas


python-cairo-dbg_1.8.8-2.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pycairo
Source-Version: 1.8.8-2.2

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

Debian distribution maintenance software
pp.
Ivo De Decker  (supplier of updated pycairo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 07 May 2017 13:10:03 +0200
Source: pycairo
Binary: python-cairo python-cairo-dbg python-cairo-dev
Architecture: source
Version: 1.8.8-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ivo De Decker 
Description:
 python-cairo - Python bindings for the Cairo vector graphics library
 python-cairo-dbg - Python bindings for the Cairo vector graphics library 
(debug exte

Bug#862008: crashes, segmentation fault

2017-05-07 Thread Mika Hanhijärvi

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is not good
because blind users like me have to rely on screen reader working reliably.
This, or similar, problem also existed before the latest update to Orca in
Debian Stretch, so I do not know if this has anything to do with the latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




-- 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/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 gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#712612: gcr: diff for NMU version 3.20.0-5.1

2017-05-07 Thread Christoph Biedl

Christoph Biedl wrote...

> Michael Biebl wrote...
>
> > Seems to be missing doc/
> 
> That's not obvious for me. Besides, I haven't uploaded yet due to a
> technical problem on my side. Want to take over?

Now uploaded to delayed+5 without further changes.

Christoph, from the Zürich BSP


signature.asc
Description: Digital signature

Bug#862001: in apt marked as pending

2017-05-07 Thread Julian Andres Klode

Control: tag 862001 pending

Hello,

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

https://anonscm.debian.org/cgit/apt/apt.git/diff/?id=315d6aa

(this message was generated automatically based on the git commit message)
---
commit 315d6aac02b657a4742b5fe2695707904c6033dd
Author: Julian Andres Klode 
Date:   Sun May 7 12:17:05 2017 +0200

Do not try to (re)start timers outside 'apt' package

dh_systemd_start inserted postinst commands in all packages,
rather than just the package containing the timers.

This also gets rid of postinst scripts for all other
packages, yay.

Closes: #862001

Processed: Bug#862001 in apt marked as pending

2017-05-07 Thread Debian Bug Tracking System

Processing control commands:

> tag 862001 pending
Bug #862001 [libapt-pkg5.0] libapt-pkg5.0: Failed to try-restart 
apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.
Added tag(s) pending.

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

Bug#861523: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED

2017-05-07 Thread Christoph Biedl

severity 861523 important
thanks

Chris Lamb wrote...

> If you can't reproduce, feel feel to close...

In spite of many efforts, nobody here at the Zürich BSP was able to
reproduce the issue. Attempts included several different build systems
(sbuild, pbuilder, docker, manual chroots etc.), fiddling time zone
information in several ways, poking docker configuration and many
things more.

Therefore I'm lowering the bug severity since that package does not
deserve to get kicked out of stretch for an issue that obviously occurs
under rare circumstances only. I will however leave it open, since
still I'd like to know what triggered the build failure on Chris'
system.

Some bits if anyone wishes to investigate further:

The expected output is '1977-09-05-125600' which is created from
a unix time_t in

vfs.py:553
| l = time.localtime(date)
| ls = time.strftime('%Y-%m-%d-%H%M%S', l)

The timestamp is created in

test-ls.sh:32
| WVPASS bup save -n src -d 242312160 src

The fact Chris observes '1977-09-05-1*3*5600' suggests the outside time
zone information (he is in +0100) is used in the localtime() call
although the bup test itself sets TZ to UTC. This looks quite weird. So
it might as well be a symptom of an, er, surprising behaviour somewhere
else.

Christoph


signature.asc
Description: Digital signature

Processed: Re: Bug#861523: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED

2017-05-07 Thread Debian Bug Tracking System

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

> severity 861523 important
Bug #861523 [src:bup] bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = 
'1977-09-05-125600 latest' FAILED
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#861468: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED

2017-05-07 Thread Florian Vessaz

Chris Lamb wrote:
> Whilst I don't have a _minimal_ Dockerfile, looking at my setup I think
> the "non-standard" things I do are:
> 
>   $ docker \
> --tty --user=$(id -u) \
> --group-add=$(id -g) \
> --volume=/tmp:/tmp \
> --volume=/home:/home
> 
> .. particularly the last two.
> 

I'm sharing the following simple Dockerfile the resulting container builds the
package without issue on my system. I also tried changing the timezone of the
container from the default "Etc/UTC" to "Etc/GMT", "Europe/London",
"Europe/Zurich" and "Pacific/Aukland" and it didn't make any difference. I also
tried to build in a directory bind-mounted with --volume from the host and the
build also succeeded in that case.

# Dockerfile
FROM debian:unstable

RUN \
  echo "deb-src http://deb.debian.org/debian unstable main" >> 
/etc/apt/sources.list; \
  apt-get update; \
  useradd --create-home --shell /bin/bash user; \
  apt-get build-dep -y bup; \
  apt-get install -y fakeroot; \
  su user -c 'cd; apt-get source bup'

CMD su user -c 'cd ~/bup-0.29; dpkg-buildpackage -uc -us'
# Dockerfile end

> If you can't reproduce, feel feel to close...

Could you try a build on your system with the above Dockerfile?

Cheers,
-- Florian

signature.asc
Description: PGP signature

Processed: found 862001 in 1.4.1

2017-05-07 Thread Debian Bug Tracking System

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

> found 862001 1.4.1
Bug #862001 [libapt-pkg5.0] libapt-pkg5.0: Failed to try-restart 
apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.
Ignoring request to alter found versions of bug #862001 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#862001: libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.

2017-05-07 Thread Julian Andres Klode

Control: found -1 1.4~beta1

On Sun, May 07, 2017 at 11:30:04AM +0200, Laurent Bigonville wrote:
> Package: libapt-pkg5.0
> Version: 1.4.2
> Severity: serious
> 
> Hi,
> 
> When upgrading my system today I saw the following line in the output:
> 
> Dépaquetage de libapt-pkg5.0:amd64 (1.4.2) sur (1.4.1) ...
> Paramétrage de libapt-pkg5.0:amd64 (1.4.2) ...
> Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer 
> not found.

Does this cause the installation to fail for you, or why is
that serious?

The same issue also happens in 1.4~beta1, although only for the
apt-daily timer (I guess nobody noticed it because everyone already
had the timer installed at that point, so nobody noticed it).

> 
> It seems that the libapt-pkg5.0 postinst script contains the following
> snippet but that the apt-daily-upgrade.timer and apt-daily.timer are not
> shipped in that package (they are in apt package instead):
> 
> # Automatically added by dh_systemd_start
> if [ -d /run/systemd/system ]; then
> systemctl --system daemon-reload >/dev/null || true
> if [ -n "$2" ]; then
> _dh_action=try-restart
> else
> _dh_action=start
> fi
> deb-systemd-invoke $_dh_action apt-daily-upgrade.timer 
> apt-daily.timer >/dev/null || true
> fi
> # End automatically added section

Oh, I thought dh_systemd would be clever enough to fix this.

Your patch is about right, I think we should call

dh_systemd_start --remaining-packages

afterwards, though (in case we add a unit elsewhere).

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Processed: Re: Bug#862001: libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.

2017-05-07 Thread Debian Bug Tracking System

Processing control commands:

> found -1 1.4~beta1
Bug #862001 [libapt-pkg5.0] libapt-pkg5.0: Failed to try-restart 
apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.
Marked as found in versions apt/1.4~beta1.

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

Bug#862001: libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.

2017-05-07 Thread Laurent Bigonville


Le 07/05/17 à 12:16, Julian Andres Klode a écrit :

Control: found -1 1.4~beta1

On Sun, May 07, 2017 at 11:30:04AM +0200, Laurent Bigonville wrote:

Package: libapt-pkg5.0
Version: 1.4.2
Severity: serious

Hi,

When upgrading my system today I saw the following line in the output:

Dépaquetage de libapt-pkg5.0:amd64 (1.4.2) sur (1.4.1) ...
Paramétrage de libapt-pkg5.0:amd64 (1.4.2) ...
Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not 
found.

Does this cause the installation to fail for you, or why is
that serious?

The same issue also happens in 1.4~beta1, although only for the
apt-daily timer (I guess nobody noticed it because everyone already
had the timer installed at that point, so nobody noticed it).
If you for example uninstall apt-doc (or any other packages) the .timer 
unit will be stopped too, this is not a good idea and this needs to be 
fixed before the release IMHO.





It seems that the libapt-pkg5.0 postinst script contains the following
snippet but that the apt-daily-upgrade.timer and apt-daily.timer are not
shipped in that package (they are in apt package instead):

# Automatically added by dh_systemd_start
if [ -d /run/systemd/system ]; then
 systemctl --system daemon-reload >/dev/null || true
 if [ -n "$2" ]; then
 _dh_action=try-restart
 else
 _dh_action=start
 fi
 deb-systemd-invoke $_dh_action apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true
fi
# End automatically added section

Oh, I thought dh_systemd would be clever enough to fix this.

Your patch is about right, I think we should call

 dh_systemd_start --remaining-packages

afterwards, though (in case we add a unit elsewhere).

I don't think it's 100% necessary as there are no other .service files 
shipped by apt binary packages but it might be good for consistency.

Bug#861736:

2017-05-07 Thread PICCA Frederic-Emmanuel

Let's instrument the code

print filename, mode, _ref(self.handle)
status = nxlib.nxiopen_(filename,mode,_ref(self.handle))
print status

$ python bug.py
filenamenxs.h5 5 
0

Bug#861468: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED

2017-05-07 Thread Chris Lamb

Hi Florian,

> > If you can't reproduce, feel feel to close...

I think you should just close the bug; my system is perhaps a little
too strange, etc. :)


Regards,

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

Processed: found 862001 in 1.4.1

2017-05-07 Thread Debian Bug Tracking System

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

> found 862001 1.4.1
Bug #862001 [libapt-pkg5.0] libapt-pkg5.0: Failed to try-restart 
apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.
Marked as found in versions apt/1.4.1.
> thanks
Stopping processing here.

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

Processed: Re: systemd: Raise network interfaces fails to stop cleanly on shutdown/reboot

2017-05-07 Thread Debian Bug Tracking System

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

> retitle 857573 No longer umounts AoE/NBD-based file systems, causing data loss
Bug #857573 [ifupdown] systemd: Raise network interfaces fails to stop cleanly 
on shutdown/reboot
Changed Bug title to 'No longer umounts AoE/NBD-based file systems, causing 
data loss' from 'systemd: Raise network interfaces fails to stop cleanly on 
shutdown/reboot'.
> severity 857573 grave
Bug #857573 [ifupdown] No longer umounts AoE/NBD-based file systems, causing 
data loss
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#862001: libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.

2017-05-07 Thread Laurent Bigonville

Package: libapt-pkg5.0
Followup-For: Bug #862001

Hi,

It seems that the fix is pretty trivial, see attached patch.

Cheers,

Laurent Bigonville

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

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

Versions of packages libapt-pkg5.0 depends on:
ii  libbz2-1.0  1.0.6-8.1
ii  libc6   2.24-10
ii  libgcc1 1:6.3.0-16
ii  liblz4-10.0~r131-2+b1
ii  liblzma55.2.2-1.2+b1
ii  libstdc++6  6.3.0-16
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages libapt-pkg5.0 recommends:
ii  apt  1.4.2

libapt-pkg5.0 suggests no packages.

-- no debconf information
diff -Nru apt-1.4.2/debian/rules apt-1.4.2bigon1/debian/rules
--- apt-1.4.2/debian/rules  2017-05-04 22:52:10.0 +0200
+++ apt-1.4.2bigon1/debian/rules2017-05-07 11:36:04.0 +0200
@@ -37,7 +37,7 @@
# Do not restart "apt-daily.service" because this script runs
# unattended-upgrades. So if apt itself is upgraded as part of
# an unattended-upgrades run it would kill itself
-   dh_systemd_start apt-daily.timer apt-daily-upgrade.timer
+   dh_systemd_start -papt apt-daily.timer apt-daily-upgrade.timer
 
 override_dh_auto_configure-arch: flags=-DWITH_DOC=OFF
 override_dh_auto_configure-indep: flags=-DWITH_DOC=ON

Processed: tagging 862001

2017-05-07 Thread Debian Bug Tracking System

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

> tags 862001 + patch
Bug #862001 [libapt-pkg5.0] libapt-pkg5.0: Failed to try-restart 
apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#862001: libapt-pkg5.0: Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not found.

2017-05-07 Thread Laurent Bigonville

Package: libapt-pkg5.0
Version: 1.4.2
Severity: serious

Hi,

When upgrading my system today I saw the following line in the output:

Dépaquetage de libapt-pkg5.0:amd64 (1.4.2) sur (1.4.1) ...
Paramétrage de libapt-pkg5.0:amd64 (1.4.2) ...
Failed to try-restart apt-daily-upgrade.timer: Unit apt-daily-upgrade.timer not 
found.

It seems that the libapt-pkg5.0 postinst script contains the following
snippet but that the apt-daily-upgrade.timer and apt-daily.timer are not
shipped in that package (they are in apt package instead):

# Automatically added by dh_systemd_start
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
_dh_action=try-restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true
fi
# End automatically added section

That code (or that file) should be moved around between apt and libapt-pkg5.0 
packages.

Regards,

Laurent Bigonville

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

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

Versions of packages libapt-pkg5.0 depends on:
ii  libbz2-1.0  1.0.6-8.1
ii  libc6   2.24-10
ii  libgcc1 1:6.3.0-16
ii  liblz4-10.0~r131-2+b1
ii  liblzma55.2.2-1.2+b1
ii  libstdc++6  6.3.0-16
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages libapt-pkg5.0 recommends:
ii  apt  1.4.2

libapt-pkg5.0 suggests no packages.

-- no debconf information

Bug#861736:

2017-05-07 Thread PICCA Frederic-Emmanuel

Hello


here the napi code which cause some trouble.

# Convert open mode from string to integer and check it is valid
if mode in _nxopen_mode: mode = _nxopen_mode[mode]
if mode not in _nxopen_mode.values():
raise ValueError, "Invalid open mode %s",str(mode)

self.filename, self.mode = filename, mode
self.handle = c_void_p(None)
self._path = []
self._indata = False
status = nxlib.nxiopen_(filename,mode,_ref(self.handle))
if status == ERROR:
if mode in [ACC_READ, ACC_RDWR]:
op = 'open'
else:
op = 'create'
raise NeXusError, "Could not %s %s"%(op,filename)


Soit seems that the nxlib.nxiopen_ method return an error

Bug#861878: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

2017-05-07 Thread Samuel Thibault

Hello,

Lumin, on dim. 07 mai 2017 02:29:46 +, wrote:
> I'm not sure whether this bug should be marked as serious. Since your test
> cases are mixing the default cc (GCC-6) and clang-3.8 together.

Well, there is no choice about this: not doing so leads to:

cc-c -o test.o test.c
nvcc  -c test-cuda.cu -o test-cuda.o
ERROR: No supported gcc/g++ host compiler found, but clang-3.8 is available.
   Use 'nvcc -ccbin clang-3.8' to use that instead.

This was documented in NEWS.Debian.gz. Having to use "--compiler-options
-fPIC" was however not documented in NEW.Debian.gz, at least that should
be done.

> I reproduced the failure you reported, but there is a simpler solution
> to the issue as shown below.
> 
> test$ CC=clang-3.8 make
> clang-3.8-c -o test.o test.c
> nvcc -ccbin clang-3.8 -c test-cuda.cu -o test-cuda.o
> clang-3.8   test.o test-cuda.o  -lcudart -o test

Ok, but that's still something difficult to the user to work out, while
it is needed for basically any use of nvcc. Currently NEWS.Debian.gz
only advises to use -ccbin clang-3.8.

> Maybe this is a bug about GCC's linking process on a set of GCC-6 and
> clang-3.8 produced objects.

> Clang-3.8 is able to link a set of mixed object files while GCC-6
> fails to do so. I guess
> this bug is a GCC-6 bug and not related to CUDA?

Well, AIUI it's not considered a bug to require PIE, but a toolchain
goal...

> On the other hand, for instance, cuda application package
> "caffe-contrib" was thoroughly
> and finely compiled by clang-3.8 .

Sure, but application Makefiles are not ready for that, we had to
tinker them to use clang-3.8, and NEWS.Debian.gz only talks about the
invokation of nvcc, not the eventual linking issue.

Samuel

Bug#861484: [Pkg-julia-devel] Bug#861484: Bug#861484: Bug#861484: julia: FTBFS on arm64

2017-05-07 Thread Graham Inggs

On 7 May 2017 at 10:26, Graham Inggs  wrote:
> Always succeeds on:
> Linux 3.16.0-4-arm64 armhf (aarch64)

I just noticed this line has armhf and I thought that was a bit odd.
It seems arm-linaro-01 and arm-linaro-03 have machine architecture:
armhf and host and build architecture: arm64.

Successful builds on arm-arm-01 and arm-arm03 have the line as:
Linux 3.16.0-4-arm64 arm64 (aarch64)

Bug#851909: Problems disappear after downgrade

2017-05-07 Thread Adrian Bunk

On Thu, Feb 02, 2017 at 10:06:42PM +0100, Roger Kalt wrote:
> Yes, I can confirm I was able to reproduce and it was the patch which was not
> correctly backported for deb8u1.
> 
> Please test the UNRELEASED deb8u2 version available from here and give 
> feedback:
> https.//www.helferplan.ch/debian/

Hi Roger,

could you ask to get your fix included into the next jessie point release?

"reportbug release.debian.org" -> jessie-pu

> Kind regards
>   Roger

Thanks
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#861484: [Pkg-julia-devel] Bug#861484: Bug#861484: julia: FTBFS on arm64

2017-05-07 Thread Graham Inggs

On 2 May 2017 at 13:10, Graham Inggs  wrote:
> I've been unable to reproduce this failure on asachi.debian.org.
> It built without failure ten times yesterday, and again once today.

I requested a give back by mailing debian-wb-team, but it hasn't happened yet.
If it is successful, it completes the llvm-symver transition, and if
not, it provides us with more data for determining whether the problem
lies with different hardware or with different kernel versions.
Either way, it shouldn't change the status of this bug.

> There is definitely something wrong though, according to the julia arm64
> build logs [1], the build has failed in the same way since January every
> time it was attempted on arm-arm-04.
>
> The most recent success a week ago was on arm-arm-03 and against
> llvm-3.8/1:3.8.1-22 which should have included the versioned symbols.

Looking at recent (>= December 2016) build success and failures [1]
combined with machine information [2]:

Always succeeds on:
arm-linaro-01 APM X-Gene Mustang board
arm-arm-01 Juno Versatile Express board (ARMv8-A)
arm-linaro-03 APM X-Gene Mustang board
arm-arm-03 APM X-Gene Mustang board
asachi.debian.org APM X-Gene Mustang board

Always fails on:
arm-arm-04 AMD Seattle rev B1
arm-conova-01 ?

Looking at kernel versions from the build logs:

Always succeeds on:
Linux 3.16.0-4-arm64 armhf (aarch64)

Always fails on:
Linux 4.8.0-0.bpo.2-arm64 arm64 (aarch64)
Linux 4.9.0-0.bpo.2-arm64 arm64 (aarch64)
Linux 4.9.0-2-arm64 arm64 (aarch64)

[1] https://buildd.debian.org/status/logs.php?pkg=julia=arm64
[2] https://db.debian.org/machines.cgi

Bug#861693: swftools: CVE-2017-8400 CVE-2017-8401

2017-05-07 Thread Salvatore Bonaccorso

Control: clone -1 -2
Control: retitle -1 swftools: CVE-2017-8400: out-of-bound write of heap data 
issue can occur in function png_load()
Control: forwarded -1 https://github.com/matthiaskramm/swftools/issues/13
Control: severity -2 important
Control: retitle -2 swftools: CVE-2017-8401: out-of-bound read of heap data 
issue can occur in function png_load()
Control: forwarded -2 https://github.com/matthiaskramm/swftools/issues/14

On Sat, May 06, 2017 at 08:12:13PM +0200, Salvatore Bonaccorso wrote:
> Hi
> 
> On Tue, May 02, 2017 at 10:01:31PM +0200, Salvatore Bonaccorso wrote:
> > CVE-2017-8400[0]:
> > | In SWFTools 0.9.2, an out-of-bounds write of heap data can occur in the
> > | function png_load() in lib/png.c:755. This issue can be triggered by a
> > | malformed PNG file that is mishandled by png2swf. Attackers could
> > | exploit this issue for DoS; it might cause arbitrary code execution.
> > 
> > CVE-2017-8401[1]:
> > | In SWFTools 0.9.2, an out-of-bounds read of heap data can occur in the
> > | function png_load() in lib/png.c:724. This issue can be triggered by a
> > | malformed PNG file that is mishandled by png2swf. Attackers could
> > | exploit this issue for DoS.
> 
> I only skimmed over this bug during the BSP in Zurich. Whilst the
> CVE-2017-8400 is fixed upstream, the CVE-2017-8401 seem still present.
> Upsteam claims it should be fixed with a particular commit, but
> running under valgrind I see still out-of-bounds reads in the png_load
> function. So needs further investigation.

Since two classes of issues, splitting this bug up into one for
CVE-2017-8400 and one for CVE-2017-8401 for better tracking the fixes.

Regards,
Salvatore

Processed: Re: Bug#861693: swftools: CVE-2017-8400 CVE-2017-8401

2017-05-07 Thread Debian Bug Tracking System

Processing control commands:

> clone -1 -2
Bug #861693 [src:swftools] swftools: CVE-2017-8400 CVE-2017-8401
Bug 861693 cloned as bug 861998
> retitle -1 swftools: CVE-2017-8400: out-of-bound write of heap data issue can 
> occur in function png_load()
Bug #861693 [src:swftools] swftools: CVE-2017-8400 CVE-2017-8401
Changed Bug title to 'swftools: CVE-2017-8400: out-of-bound write of heap data 
issue can occur in function png_load()' from 'swftools: CVE-2017-8400 
CVE-2017-8401'.
> forwarded -1 https://github.com/matthiaskramm/swftools/issues/13
Bug #861693 [src:swftools] swftools: CVE-2017-8400: out-of-bound write of heap 
data issue can occur in function png_load()
Set Bug forwarded-to-address to 
'https://github.com/matthiaskramm/swftools/issues/13'.
> severity -2 important
Bug #861998 [src:swftools] swftools: CVE-2017-8400 CVE-2017-8401
Severity set to 'important' from 'grave'
> retitle -2 swftools: CVE-2017-8401: out-of-bound read of heap data issue can 
> occur in function png_load()
Bug #861998 [src:swftools] swftools: CVE-2017-8400 CVE-2017-8401
Changed Bug title to 'swftools: CVE-2017-8401: out-of-bound read of heap data 
issue can occur in function png_load()' from 'swftools: CVE-2017-8400 
CVE-2017-8401'.
> forwarded -2 https://github.com/matthiaskramm/swftools/issues/14
Bug #861998 [src:swftools] swftools: CVE-2017-8401: out-of-bound read of heap 
data issue can occur in function png_load()
Set Bug forwarded-to-address to 
'https://github.com/matthiaskramm/swftools/issues/14'.

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

Bug#861994: live-wrapper: Lacks dependency on python-pycurl

2017-05-07 Thread Stefan Fritsch

Package: live-wrapper
Version: 0.6
Severity: serious

lwr seems to require pycurl:

$ lwr --help
Traceback (most recent call last):
  File "/usr/bin/lwr", line 11, in 
load_entry_point('live-wrapper==0.6', 'console_scripts', 'lwr')()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 561, 
in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2631, 
in load_entry_point
return ep.load()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2291, 
in load
return self.resolve()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2297, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python2.7/dist-packages/lwr/run.py", line 18, in 
import pycurl
ImportError: No module named pycurl


But it lacks the proper dependency on python-pycurl. With python-pycurl
installed, it works.

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

Kernel: Linux 4.9.0-3-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: systemd (via /run/systemd/system)

Versions of packages live-wrapper depends on:
ii  debian-archive-keyring  2014.3
ii  isolinux3:6.03+dfsg-14.1
ii  python-apt  1.4.0~beta3
ii  python-cliapp   1.20160724-2
ii  python-distro-info  0.15
ii  python-requests 2.12.4-1
pn  python:any  
ii  vmdebootstrap   1.7-1
ii  xorriso 1.4.6-1+b1

live-wrapper recommends no packages.

Versions of packages live-wrapper suggests:
pn  cmdtest  

-- no debconf information

Processed: your mail

2017-05-07 Thread Debian Bug Tracking System

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

> # totally broken on at least some hardware
> severity 857591 serious
Bug #857591 [libclc-amdgcn] libclc-amdgcn: apply upstream Mesa patch
Severity set to 'serious' from 'important'
> severity 861986 serious
Bug #861986 [libclc-amdgcn] unsupported call to function get_local_size on AMD 
GPUs
Severity set to 'serious' from 'grave'
> merge 857591 861986
Bug #857591 [libclc-amdgcn] libclc-amdgcn: apply upstream Mesa patch
Bug #861986 [libclc-amdgcn] unsupported call to function get_local_size on AMD 
GPUs
Marked as fixed in versions libclc/0.2.0+git20170213-1.
Merged 857591 861986
>
End of message, stopping processing here.

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

Bug#861592: node-dateformat: FTBFS: AssertionError: '1:19:44 PM GMT' === '1:19:44 PM UTC'

2017-05-07 Thread Florian Vessaz

Dear maintainer,

Whether the issue arises or not depends on the timezone of the system.
For instance the test suite fails in the following timezones: Etc/GMT,
Etc/GMT+1 or Pacific/Tahiti (and ina lot of others too).

I couldn't find a reliable way to set the timezone after node has started.
I've found the following discussion in the NodeJS issue tracker
confirming this situation:
https://github.com/nodejs/node-v0.x-archive/issues/3286

IMHO it would thus be best to set the timezone to UTC before running the
tests. This can easily be achieved from debian/control:

override_dh_auto_test:
TZ=Etc/UTC mocha -R spec

Cheers,
-- Florian


signature.asc
Description: PGP signature

83 matches

Mail list logo