date:20170527

Hey Nis!

On Tue, Apr 25, 2017 at 5:56 PM, Nis Martensen  wrote:
> Let's fix this before we find out exactly what else was broken by my
> patch in reportbug 7.1.6.

should we revert to the previous behavior of get_command_output before
introducing other regressions?

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

Bug#863524: mldonkey-server: The Hyperlink "Clear all" is invalid on the web site interface of the mldonkey

2017-05-27 Thread Lu Wang

Package: mldonkey-server
Version: 3.1.5-3.1
Severity: normal

Dear Maintainer,
When I click the hyperlink "Clear all", nothing happens. I think when I
click "Clear all", all frames before items should be selected and then I
can "Submit changes".


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

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

Versions of packages mldonkey-server depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.60
ii  libbz2-1.0 1.0.6-8.1
ii  libc6  2.24-10
ii  libgcc11:6.3.0-18
ii  libgd3 2.2.4-2
ii  libjpeg62-turbo1:1.5.1-2
ii  libpng16-161.6.28-1
ii  libstdc++6 6.3.0-18
ii  lsb-base   9.20161125
ii  mime-support   3.60
ii  ucf3.0036
ii  zlib1g 1:1.2.8.dfsg-5

mldonkey-server recommends no packages.

mldonkey-server suggests no packages.

-- debconf information:
* mldonkey-server/launch_at_startup: false

Bug#863286: completely broken in non-US locales

2017-05-27 Thread Daurnimator

On 28 May 2017 at 01:38, Santiago Ruano Rincón  wrote:
> In case you want to test it, I've uploaded a patched version to my
> personal repo:
> https://people.debian.org/~santiago/debian/santiago-unstable/

If patching the upstream, please update the version in
http/version.lua to something like version="0.1.debian-1"

However I'm hoping to make a 0.2 release today that includes the fix
(as well as others that weren't reported to debian directly): please
consider packaging that instead.

Bug#863513: [Reportbug-maint] Bug#863513: Bug#863513: reportbug: No GUI; only '--ui=text'

On Sat, May 27, 2017 at 10:09 PM, Diego A. Casas Toro
 wrote:
> It means the gtk2 UI is supposed to be the default, and it doesn't make sense
> to create a menu entry for program that doesn’t start how it is supposed to.

do you know of a way to create a menu entry only if the needed
dependencies are installed? They are in Suggests, because *many*
reportbug users prefer the text UI and dont want their systems to be
cluttered by graphical libs.

> To conclude, GTK UI should be default for people using a DE in order to be
> user-friendly (maybe include it in the task-* packages). Or if the gtk2 UI is
> not supposed to be the default, the menu entry should not be created during
> install.

what's probably going to happen is the removal of the GTK UI: it is
unmaintained.

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

Bug#863522: unblock: python-numpy/1:1.12.1-3

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-numpy

This upload fixes a bug when using numpy.abs() on numpy.nan on some
architectures; the bug is minor, but a user noticed nonetheless, the patch comes
directly from upstream and it's just a one-liner with extensive tests.

Source debdiff is attached

unblock python-numpy/1:1.12.1-3

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

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 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)
diff -Nru python-numpy-1.12.1/debian/changelog 
python-numpy-1.12.1/debian/changelog
--- python-numpy-1.12.1/debian/changelog2017-04-05 06:26:43.0 
-0400
+++ python-numpy-1.12.1/debian/changelog2017-05-27 19:44:59.0 
-0400
@@ -1,3 +1,10 @@
+python-numpy (1:1.12.1-3) unstable; urgency=medium
+
+  * debian/patches/0007-BUG-Don-t-signal-FP-exceptions-in-np.absolute.patch
+- fix RuntimeWarning on numpy.abs(numpy.nan) on some archs; Closes: #863192
+
+ -- Sandro Tosi   Sat, 27 May 2017 19:44:59 -0400
+
 python-numpy (1:1.12.1-2) unstable; urgency=medium
 
   * Team upload
diff -Nru python-numpy-1.12.1/debian/.git-dpm 
python-numpy-1.12.1/debian/.git-dpm
--- python-numpy-1.12.1/debian/.git-dpm 2017-04-04 12:49:56.0 -0400
+++ python-numpy-1.12.1/debian/.git-dpm 2017-05-27 19:44:59.0 -0400
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-4b26915f32eec3afa476d678bc7831ab7b1899c1
-4b26915f32eec3afa476d678bc7831ab7b1899c1
+285b463e037cd9aeaf37ccc90ccf3349cc84b88a
+285b463e037cd9aeaf37ccc90ccf3349cc84b88a
 db9ad0d21c51a5a4983387c232c00bd6f844e406
 db9ad0d21c51a5a4983387c232c00bd6f844e406
 python-numpy_1.12.1.orig.tar.gz
diff -Nru 
python-numpy-1.12.1/debian/patches/0007-BUG-Don-t-signal-FP-exceptions-in-np.absolute.patch
 
python-numpy-1.12.1/debian/patches/0007-BUG-Don-t-signal-FP-exceptions-in-np.absolute.patch
--- 
python-numpy-1.12.1/debian/patches/0007-BUG-Don-t-signal-FP-exceptions-in-np.absolute.patch
 1969-12-31 19:00:00.0 -0500
+++ 
python-numpy-1.12.1/debian/patches/0007-BUG-Don-t-signal-FP-exceptions-in-np.absolute.patch
 2017-05-27 19:44:59.0 -0400
@@ -0,0 +1,89 @@
+From 285b463e037cd9aeaf37ccc90ccf3349cc84b88a Mon Sep 17 00:00:00 2001
+From: James Cowgill 
+Date: Tue, 7 Mar 2017 11:39:01 +
+Subject: BUG: Don't signal FP exceptions in np.absolute
+
+Fixes #8686
+
+This PR centers around this piece of code in 
`numpy/core/src/umath/loops.c.src`:
+```c
+UNARY_LOOP {
+const @type@ in1 = *(@type@ *)ip1;
+const @type@ tmp = in1 > 0 ? in1 : -in1;
+/* add 0 to clear -0.0 */
+*((@type@ *)op1) = tmp + 0;
+}
+```
+
+If in1 is `NaN`, the C99 standard requires that the comparison `in1 > 0`
+signals `FE_INVALID`, but the usual semantics for the absolute function are
+that no FP exceptions should be generated (eg compare to C `fabs` and Python
+`abs`). This was probably never noticed due to a bug in GCC x86 where all
+floating point comparisons do not signal exceptions, however Clang on x86 and
+GCC on other architectures (including ARM and MIPS) do signal an FP exception
+here.
+
+Fix by clearing the floating point exceptions after the loop has
+finished. The alternative of rewriting the loop to use `npy_fabs`
+instead would also work but has performance issues because that function
+is not inlined. The `test_abs_neg_blocked` is adjusted not to ignore
+`FE_INVALID` errors because now both absolute and negate should never
+produce an FP exceptions.
+---
+ numpy/core/src/umath/loops.c.src |  1 +
+ numpy/core/tests/test_umath.py   | 30 ++
+ 2 files changed, 15 insertions(+), 16 deletions(-)
+
+diff --git a/numpy/core/src/umath/loops.c.src 
b/numpy/core/src/umath/loops.c.src
+index 3c11908..7e683ab 100644
+--- a/numpy/core/src/umath/loops.c.src
 b/numpy/core/src/umath/loops.c.src
+@@ -1840,6 +1840,7 @@ NPY_NO_EXPORT void
+ *((@type@ *)op1) = tmp + 0;
+ }
+ }
++npy_clear_floatstatus();
+ }
+ 
+ NPY_NO_EXPORT void
+diff --git a/numpy/core/tests/test_umath.py b/numpy/core/tests/test_umath.py
+index 6fea832..fad75cd 100644
+--- a/numpy/core/tests/test_umath.py
 b/numpy/core/tests/test_umath.py
+@@ -1226,22 +1226,20 @@ class TestAbsoluteNegative(TestCase):
+ np.negative(inp, out=out)
+ assert_equal(out, tgt, err_msg=msg)
+ 
+-# will throw invalid flag depending on compiler optimizations
+-with np.errstate(invalid='ignore'):
+-for v in [np.nan, -np.inf, np.inf]:
+-for i in range(inp.size):
+-d =

Bug#863518: nftables: "workstation" example causes unkillable application hangs

2017-05-27 Thread Harlan Lieberman-Berg

retitle 863518 nftables: "workstation" example causes unkillable
application hangs
severity 863518 grave
submitter !
thanks

Dear Maintainer,

It seems the problem is more serious than I thought.  Certain
applications -- chromium/google-chrome, nft itself -- can no longer
function with this ruleset in place.  Running `nft flush ruleset`, for
example, hangs forever in uninterruptable sleep.  An strace is
attached.

The only way I've found to fix the problem is to remove the
/etc/nftables.conf and reboot.

(Sorry for breaking the threading; accidentally sent the mail with a
bad reportbug conf.)

Sincerely,
-- 
Harlan Lieberman-Berg
~hlieberman
agartha 福 ~ 
10012 ◯ : sudo strace -fff nft flush ruleset ⏎ 
execve("/usr/sbin/nft", ["nft", "flush", "ruleset"], [/* 23 vars */]) = 0
brk(NULL)   = 0x55599d8c5000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f6ee430a000
access("/etc/ld.so.preload", R_OK)  = 0
open("/etc/ld.so.preload", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
close(3)= 0
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=210070, ...}) = 0
mmap(NULL, 210070, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f6ee42d6000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libmnl.so.0", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@\33\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=26616, ...}) = 0
mmap(NULL, 2121744, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f6ee3ee3000
mprotect(0x7f6ee3ee8000, 2097152, PROT_NONE) = 0
mmap(0x7f6ee40e8000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x5000) = 0x7f6ee40e8000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/usr/lib/x86_64-linux-gnu/libnftnl.so.4", O_RDONLY|O_CLOEXEC) = 3
read(3, 
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\257\0\0\0\0\0\0"..., 832) = 
832
fstat(3, {st_mode=S_IFREG|0644, st_size=201728, ...}) = 0
mmap(NULL, 2296856, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f6ee3cb2000
mprotect(0x7f6ee3ce1000, 2097152, PROT_NONE) = 0
mmap(0x7f6ee3ee1000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2f000) = 0x7f6ee3ee1000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/usr/lib/x86_64-linux-gnu/libxtables.so.12", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\2401\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=51120, ...}) = 0
mmap(NULL, 2148184, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f6ee3aa5000
mprotect(0x7f6ee3ab1000, 2093056, PROT_NONE) = 0
mmap(0x7f6ee3cb, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xb000) = 0x7f6ee3cb
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libreadline.so.7", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200f\1\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=309168, ...}) = 0
mmap(NULL, 2409704, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f6ee3858000
mprotect(0x7f6ee389c000, 2093056, PROT_NONE) = 0
mmap(0x7f6ee3a9b000, 32768, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x43000) = 0x7f6ee3a9b000
mmap(0x7f6ee3aa3000, 5352, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f6ee3aa3000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/usr/lib/x86_64-linux-gnu/libgmp.so.10", O_RDONLY|O_CLOEXEC) = 3
read(3, 
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\305\0\0\0\0\0\0"..., 832) = 
832
fstat(3, {st_mode=S_IFREG|0644, st_size=537448, ...}) = 0
mmap(NULL, 2632576, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f6ee35d5000
mprotect(0x7f6ee3656000, 2097152, PROT_NONE) = 0
mmap(0x7f6ee3856000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x81000) = 0x7f6ee3856000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320\3\2\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1685264, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f6ee42d4000
mmap(NULL, 3791264, PROT_READ|PROT_EXEC,

Bug#863513: [Reportbug-maint] Bug#863513: reportbug: No GUI; only '--ui=text'

2017-05-27 Thread Diego A. Casas Toro

On Saturday, May 27, 2017 7:33:56 PM -05 you wrote:
> On Sat, May 27, 2017 at 5:00 PM, Diego A. Casas Toro
> 
>  wrote:
> > I tried to start reportbug for the first time in KDE Plasma 5, but it did
> > not start.
> did you install the additional dependencies as specified by the
> documentation?
> 
> ```
> How to Use New GTK+ User Interface
> ==
> 
> If you tried to set the new GTK+ UI (named in reportbug as gtk2 ui)
> and it fails to start (falling back to text mode, hopefully), chances
> are that you are missing some of the packages listed as Suggests, in
> particular:
> 
> - python3-gi
> - python3-gi-cairo
> - gir1.2-gtk-3.0
> - gir1.2-vte-2.91
> - python3-gtkspellcheck
> 
> If after installing both of them still GTK+ UI doesn't show up, please
> file a report (in text ui :) ).
> ```
> 
> from /usr/share/doc/reportbug/README.Users.gz

I did not install the suggests of reportbug. After 2 years using GTK-based 
desktop environments (GNOME, Mate, Xfce), I thought the GTK UI was the 
“default” UI; I never had to install “additional dependencies” in those DEs.

I just installed python3-gi-cairo, gir1.2-vte-2.91 and python3-gtkspellcheck, 
and it works. Now the default UI is GTK.

So the bug is actually different: why does the reportbug package create a menu 
entry for the gtk2 UI if it's not the default UI?

This is the command of the '.desktop' file:

reportbug --exit-prompt --ui gtk2

It means the gtk2 UI is supposed to be the default, and it doesn't make sense 
to create a menu entry for program that doesn’t start how it is supposed to.

To conclude, GTK UI should be default for people using a DE in order to be 
user-friendly (maybe include it in the task-* packages). Or if the gtk2 UI is 
not supposed to be the default, the menu entry should not be created during 
install.

-- 
Diego A. Casas Toro
Est. de ingeniería civil
C. e.: daca...@uninorte.edu.co

-- 
*Este correo no representa opinión o consentimiento oficial de la 
Universidad del Norte, por lo que esta no adquiere ninguna responsabilidad 
por su contenido, salvo en el caso de funcionarios en ejercicio de 
atribuciones reglamentarias. Puede provenir de una cuenta ofrecida a 
funcionarios o estudiantes, como parte del ejercicio educativo, evento en 
el cual tanto el mensaje como sus anexos son estrictamente confidenciales. 
Ha sido analizado con software antivirus; no obstante, no se garantiza que 
sea seguro o no contenga errores o virus, por lo que la Universidad del 
Norte no se hace responsable de su transmisión.*

Bug#863131: unblock: tomcat-native/1.2.12-2

2017-05-27 Thread Emmanuel Bourg

Control: tags -1 - moreinfo

Thanks a lot, uploaded.

Bug#863521: unblock: devscripts/2.17.6 (pre-approval)

2017-05-27 Thread James McCoy

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package devscripts

There are a few changes sitting in git right now that would be useful to
make it into Stretch.  The full log is
https://anonscm.debian.org/git/collab-maint/devscripts.git/log/?id=v2.17.5..master

uscan/debdiff: Typos/documentation improvements (7f07b7bc, f447aafb)
chdist: Support running aptitude (f722bf62)
debcheckout: Understand cgit URLs (4e1867dc)
debrepro: Check for and inform user of missing runtime dependencies (ad90af3a)
debsign: Fix regression when signing a dsc file (51e909fd)

Additionally, there are changes to various scripts to make them work
better when $HOME isn't set by using Perl's File::HomeDir, a new
Depends (56e38636, 3ff2f9db).

The $HOME handling is the most disruptive, so I'd be willing to drop
that.

unblock devscripts/2.17.6

-- 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-3-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)
 debian/changelog   | 30 ++
 debian/control |  1 +
 scripts/bts.pl |  2 ++
 scripts/chdist.bash_completion |  6 +++---
 scripts/chdist.pl  | 12 ++--
 scripts/debcheckout.pl |  5 +++--
 scripts/debcommit.pl   |  3 ++-
 scripts/debdiff.pl |  2 +-
 scripts/debrepro.pod   |  4 
 scripts/debrepro.sh| 21 +
 scripts/debsign.sh |  2 +-
 scripts/dscverify.pl   |  2 ++
 scripts/grep-excuses.pl|  3 ++-
 scripts/namecheck.pl   |  8 +++-
 scripts/rc-alert.pl|  2 ++
 scripts/svnpath.pl |  7 +--
 scripts/uscan.pl   | 18 +++---
 scripts/wnpp-alert.sh  |  2 +-
 18 files changed, 112 insertions(+), 18 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 0c32aaac..e436d4be 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,33 @@
+devscripts (2.17.6) UNRELEASED; urgency=medium
+
+  [ Osamu Aoki ]
+  * uscan:
++ Update manpage on the github.com behavior and the alternative
+  shorthand form.  (Closes: #836507, #859089)
+
+  [ Adam D. Barratt ]
+  * uscan: fix a typo in the manpage
+  * debdiff: fix a typo
+
+  [ Paul Wise ]
+  * chdist:
++ add support for running aptitude
+  * debcheckout:
++ handle cgit URLs too. Thanks to Rhonda for the suggestion.
+  * Make various scripts work when HOME is unset:
+bts chdist debcommit dscverify grep-excuses
+namecheck rc-alert svnpath wnpp-alert
+
+  [ Antonio Terceiro ]
+  * debrepro:
++ check for dependencies before doing any builds (Closes: #862586)
+
+  [ James Clarke ]
+  * debsign:
++ Fix signing a dsc directly.  (Closes: #863497)
+
+ -- Osamu Aoki   Fri, 31 Mar 2017 02:03:30 +0900
+
 devscripts (2.17.5) unstable; urgency=medium
 
   * Create GNUPGHOME in /tmp to fix CI failures due to long path names.
diff --git a/debian/control b/debian/control
index 52b774e9..3a2994a8 100644
--- a/debian/control
+++ b/debian/control
@@ -46,6 +46,7 @@ Package: devscripts
 Architecture: any
 Multi-Arch: foreign
 Depends: dpkg-dev (>= 1.17.6),
+ libfile-homedir-perl,
  ${misc:Depends},
  ${perl:Depends},
  ${python3:Depends},
diff --git a/scripts/bts.pl b/scripts/bts.pl
index 2a650d10..a2a64c51 100755
--- a/scripts/bts.pl
+++ b/scripts/bts.pl
@@ -47,6 +47,7 @@ use strict;
 use warnings;
 use File::Basename;
 use File::Copy;
+use File::HomeDir;
 use File::Path qw(make_path rmtree);
 use File::Spec;
 use File::Temp qw/tempfile/;
@@ -173,6 +174,7 @@ my @valid_severities=qw(wishlist minor normal important
 
 my $browser;  # Will set if necessary
 
+$ENV{HOME} = File::HomeDir->my_home;
 my $cachedir = $ENV{XDG_CACHE_HOME} || File::Spec->catdir($ENV{HOME}, 
'.cache');
 $cachedir = File::Spec->catdir($cachedir, 'devscripts', 'bts');
 
diff --git a/scripts/chdist.bash_completion b/scripts/chdist.bash_completion
index 89773313..51dbf499 100644
--- a/scripts/chdist.bash_completion
+++ b/scripts/chdist.bash_completion
@@ -6,7 +6,7 @@ _chdist ()
 {
   local cur=$2 prev=$3
   local options='--help -h --data-dir -d --arch -a'
-  local commands='create apt apt-get apt-cache apt-rdepends
+  local commands='create apt apt-get apt-cache apt-rdepends aptitude
src2bin bin2src
compare-packages compare-bin-packages
compare-versions compare-bin-versions
@@ -14,7 +14,7 @@ _chdist ()
list'
   # Sync'd with buildd.debian.org on 2016-04-02:
   local archs="all alpha amd64 arm64 armel armhf hppa hurd-i386 i386 ia64

Bug#861989: nautilus: Nautilus freezes/crashes when right clicking and selecting properties for 1 or more files

2017-05-27 Thread Jason Crain

On Sun, May 28, 2017 at 10:44:41AM +1000, Luke Christopher Clarke wrote:
> I ran both commands as non-sudo and sudo respectively.

You should run these as your regular user, not root.

> -- START tracker-control -S --
> luke@luk-main:~$ tracker-control -S
> Store:
> ^C

It is odd that tracker-control freezes too.  I was expecting a message
about how the tracker store is initializing or reindexing.

> -- tracker-control -k store; TRACKER_VERBOSITY=3 G_DEBUG=all --
> G_MESSAGES_DEBUG=all /usr/lib/tracker/tracker-store
> luke@luk-main:~$ tracker-control store; TRACKER_VERBOSITY=3 G_DEBUG=all
   ^

This is supposed to be "tracker-control -k store".  The point is to kill
(-k) the existing tracker-store process before running tracker-store
with debug messages enabled, because otherwise it will just complain
that there is already a process running.

> G_MESSAGES_DEBUG=all /usr/lib/tracker/tracker-store
> Unrecognized options: 'store'
> Tracker-Message: Starting tracker-store 1.2.4
...
> Tracker-Message: Registering D-Bus service...
>   Name:'org.freedesktop.Tracker1'
> 
> (tracker-store:12568): Tracker-CRITICAL **: D-Bus service
> name:'org.freedesktop.Tracker1' is already taken, perhaps the daemon is
> already running?
> Trace/breakpoint trap

As it does here.

Bug#863484: dpkg-buildpackage: build error for some package when whitespace in the working directory path

2017-05-27 Thread Guillem Jover

Control: reassign -1 cdbs

Hi!

[ Leaving most of the report intact for the cdbs maintainers. ]

On Sat, 2017-05-27 at 17:56:00 +0200, Quentin C. wrote:
> Package: dpkg-dev
> Version: 1.18.24
> Severity: normal
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> Whitespace in the working directory path
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> $ mkdir "/tmp/a path with whitespace/"
> $ cd "/tmp/a path with whitespace"
> $ apt-get source grep
> $ cd grep-2.27
> $ dpkg-buildpackage -us -uc
> 
>* What was the outcome of this action?
> 
> ...
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> set -e;   mv ./build-aux/config.guess
> ./build-aux/config.guess.cdbs-orig; cp --remove-destination
> /usr/share/misc/config.guess ./build-aux/config.guess;
> set -e;   mv ./build-aux/config.sub ./build-aux/config.sub.cdbs-orig; cp
> --remove-destination /usr/share/misc/config.sub ./build-aux/config.sub;
> dh_autoreconf 
> find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
> '*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path
> '*/CVS/*' \) -a  -type f -exec md5sum {} + >
> debian/autoreconf.before
> autoreconf -f -i
> find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
> '*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path
> '*/CVS/*' \) -a  -type f -exec md5sum {} + >
> debian/autoreconf.after
> touch debian/stamp-autotools-files
> chmod a+x /tmp/a path with whitespace/grep-2.27/./configure
> chmod: impossible d'accéder à 'path': Aucun fichier ou dossier de ce
> type
> chmod: impossible d'accéder à 'with': Aucun fichier ou dossier de ce
> type
> chmod: impossible d'accéder à 'whitespace/grep-2.27/./configure': Aucun
> fichier ou dossier de ce type
> /usr/share/cdbs/1/class/autotools.mk:44 : la recette pour la cible
> « debian/stamp-autotools » a échouée
> make: *** [debian/stamp-autotools] Erreur 1
> dpkg-buildpackage: erreur: debian/rules build a produit une erreur de
> sortie de type 2
> $ 

This seems to be a problem in cdbs, as per the above error message.
Thus reassigning.

> Try with some other package:
>   xpdf is working
>   python3 is working
>   gzip is working
>   lzo2 is not working
> 
> 
> --
> Quentin C.
> 
> 
> -- System Information:
> Debian Release: 9.0
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64
>  (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages dpkg-dev depends on:
> ii  binutils  2.28-5
> ii  bzip2 1.0.6-8.1
> ii  libdpkg-perl  1.18.24
> ii  make  4.1-9.1
> ii  patch 2.7.5-1+b2
> pn  perl:any  
> ii  tar   1.29b-1.1
> ii  xz-utils  5.2.2-1.2+b1
> 
> Versions of packages dpkg-dev recommends:
> ii  build-essential  12.3
> ii  clang-3.5 [c-compiler]   1:3.5.2-3~bpo8+2
> ii  clang-3.8 [c-compiler]   1:3.8.1-23
> ii  clang-3.9 [c-compiler]   1:3.9.1-8
> ii  fakeroot 1.21-3.1
> ii  gcc [c-compiler] 4:6.3.0-4
> ii  gcc-4.6 [c-compiler] 4.6.3-14
> ii  gcc-4.8 [c-compiler] 4.8.4-1
> ii  gcc-4.9 [c-compiler] 4.9.2-10
> ii  gcc-6 [c-compiler]   6.3.0-16
> ii  gnupg2.1.18-6
> ii  gnupg2   2.1.18-6
> ii  gpgv 2.1.18-6
> ii  libalgorithm-merge-perl  0.08-3
> 
> Versions of packages dpkg-dev suggests:
> ii  debian-keyring  2017.01.20
> 
> -- no debconf information

Bug#861989: nautilus: Nautilus freezes/crashes when right clicking and selecting properties for 1 or more files

2017-05-27 Thread Luke Christopher Clarke

Hello Jason,

I ran both commands as non-sudo and sudo respectively.

-- START tracker-control -S --
luke@luk-main:~$ tracker-control -S
Store:
^C
luke@luk-main:~$ sudo tracker-control -S
[sudo] password for luke:
Store:
28 May 2017, 10:27:07:  ✗ Store - Unavailable

Miners:
28 May 2017, 10:27:07:  ✗ File System   - Not running or is a
disabled plugin
28 May 2017, 10:27:07:  ✗ Userguides- Not running or is a
disabled plugin
28 May 2017, 10:27:07:  ✗ Applications  - Not running or is a
disabled plugin
28 May 2017, 10:27:07:  ✗ Extractor - Not running or is a
disabled plugin

luke@luk-main:~$

-- END tracker-control -S --

-- tracker-control -k store; TRACKER_VERBOSITY=3 G_DEBUG=all --
G_MESSAGES_DEBUG=all /usr/lib/tracker/tracker-store
luke@luk-main:~$ tracker-control store; TRACKER_VERBOSITY=3 G_DEBUG=all
G_MESSAGES_DEBUG=all /usr/lib/tracker/tracker-store
Unrecognized options: 'store'
Tracker-Message: Starting tracker-store 1.2.4
Tracker-Message: General options:
Tracker-Message:   Verbosity    0
Tracker-Message: Store options:
Tracker-Message:   Readonly mode    no
Tracker-Message:   GraphUpdated Delay   1000
Tracker-Message: Log verbosity is set to 0, disabling D-Bus client lookup
Tracker-Message: Registering D-Bus object...
Tracker-Message:   Path:'/org/freedesktop/Tracker1/Status'
Tracker-Message:   Type:'TrackerStatus'
Tracker-Message: Registering D-Bus object...
Tracker-Message:   Path:'/org/freedesktop/Tracker1/Statistics'
Tracker-Message:   Type:'TrackerStatistics'
Tracker-Message: Registering D-Bus object...
Tracker-Message:   Path:'/org/freedesktop/Tracker1/Resources'
Tracker-Message:   Type:'TrackerResources'
Tracker-Message: Registering D-Bus object...
Tracker-Message:   Path:'/org/freedesktop/Tracker1/Steroids'
Tracker-Message:   Type:'TrackerSteroids'
Tracker-Message: Registering D-Bus object...
Tracker-Message:   Path:'/org/freedesktop/Tracker1/Backup'
Tracker-Message:   Type:'TrackerBackup'
Tracker-Message: Registering D-Bus service...
  Name:'org.freedesktop.Tracker1'

(tracker-store:12568): Tracker-CRITICAL **: D-Bus service
name:'org.freedesktop.Tracker1' is already taken, perhaps the daemon is
already running?
Trace/breakpoint trap
luke@luk-main:~$ ^C

luke@luk-main:~$ sudo tracker-control store; TRACKER_VERBOSITY=3
G_DEBUG=all G_MESSAGES_DEBUG=all /usr/lib/tracker/tracker-store
[sudo] password for luke:
Unrecognized options: 'store'
Tracker-Message: Starting tracker-store 1.2.4
Tracker-Message: General options:
Tracker-Message:   Verbosity    0
Tracker-Message: Store options:
Tracker-Message:   Readonly mode    no
Tracker-Message:   GraphUpdated Delay   1000
Tracker-Message: Log verbosity is set to 0, disabling D-Bus client lookup
Tracker-Message: Registering D-Bus object...
Tracker-Message:   Path:'/org/freedesktop/Tracker1/Status'
Tracker-Message:   Type:'TrackerStatus'
Tracker-Message: Registering D-Bus object...
Tracker-Message:   Path:'/org/freedesktop/Tracker1/Statistics'
Tracker-Message:   Type:'TrackerStatistics'
Tracker-Message: Registering D-Bus object...
Tracker-Message:   Path:'/org/freedesktop/Tracker1/Resources'
Tracker-Message:   Type:'TrackerResources'
Tracker-Message: Registering D-Bus object...
Tracker-Message:   Path:'/org/freedesktop/Tracker1/Steroids'
Tracker-Message:   Type:'TrackerSteroids'
Tracker-Message: Registering D-Bus object...
Tracker-Message:   Path:'/org/freedesktop/Tracker1/Backup'
Tracker-Message:   Type:'TrackerBackup'
Tracker-Message: Registering D-Bus service...
  Name:'org.freedesktop.Tracker1'

(tracker-store:12587): Tracker-CRITICAL **: D-Bus service
name:'org.freedesktop.Tracker1' is already taken, perhaps the daemon is
already running?
Trace/breakpoint trap

-- END tracker-control -k store; TRACKER_VERBOSITY=3 G_DEBUG=all --

On Sun, May 28, 2017 at 7:56 AM, Jason Crain 
wrote:

> On Fri, May 26, 2017 at 08:03:26PM +1000, Luke Christopher Clarke wrote:
> > I have not gone out of my way to install any extra nautilus extensions to
> > my knowledge. Is there a way I can find that out?
> >
> > Also the following is the output from your command. I also went ahead and
> > replicated the bug.
> >
> ...
> > (nautilus:1733): Tracker-DEBUG: New TrackerTagsView with 1 files
> > (nautilus:1733): Tracker-DEBUG: tracker-backend.vala:37: Waiting for
> > service to become available...
> >
> > -- END TERMINAL OUTPUT --
>
> It looks like it's frozen because tracker is stuck.  What's the output
> of "tracker-control -S"?  And what is the output of running
> "tracker-control -k store; TRACKER_VERBOSITY=3 G_DEBUG=all
> G_MESSAGES_DEBUG=all /usr/lib/tracker/tracker-store" ?
>

Bug#863520: cyrus-imapd version 2.5.10-3 Fatal error with SSL

2017-05-27 Thread roro

Package: cyrus-imapd
Version: 2.5.10-3
Severity: important
Tags: upstream

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages cyrus-imapd depends on:
ii  cyrus-common  2.5.10-3
ii  dpkg  1.18.24
ii  libc6 2.24-10
ii  libicu57  57.1-6
ii  libsasl2-22.1.27~101-g0780600+dfsg-3
ii  libssl1.1 1.1.0e-2
ii  libwrap0  7.6.q-26
ii  zlib1g1:1.2.8.dfsg-5

cyrus-imapd recommends no packages.

cyrus-imapd suggests no packages.

-- no debconf information

Here is the log entry every time SSL fails from a client when it conenects to 
pop3d via SSL on ort 995 :
cyrus/pop3[26981]: Fatal error: Internal error: assertion failed: 
lib/cyrusdb_twoskip.c: 1727: key && keylen

Bug#863519: unblock blockdiag/1.5.3+dfsg-2

2017-05-27 Thread Kouhei Maeda

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock


Dear release team,
Please unblock blockdiag/1.5.3+dfsg-2.

This would fixes #860689, #847930 in stretch and sid,
which are some test failures on FTBFS.

Attached is the source debdiff.

Regards,

diff -Nru blockdiag-1.5.3+dfsg/debian/changelog
blockdiag-1.5.3+dfsg/debian/changelog
--- blockdiag-1.5.3+dfsg/debian/changelog2017-01-23 07:13:59.0 +0900
+++ blockdiag-1.5.3+dfsg/debian/changelog2017-05-26 22:06:40.0 +0900
@@ -1,3 +1,31 @@
+blockdiag (1.5.3+dfsg-2) unstable; urgency=medium
+
+  * Fixes build kills unrelated python processes. Closes: #847930
+- debian/rules
+  * Removes PYBUILD_AFTER_BUILD,PYBUILD_{BEFORE,AFTER}_TEST options.
+- debian/patches
+  * Adds use-vlgothic-package-on-fullpath.patch,
+moves fontpath related modification
+from Fixed-remote-image-resouces.patch
+  * Updates Fixed-remote-image-resouces.patch.
+- debian/control
+  * Removes procps from Build-Depends.
+  * Fixes some test failures
+- debian/patches
+  #* Removes 848748-exception-ignored-in-Image-del.patch unnecessary.
+  * Adds skip-test_app_cleans_up_images.patch.
+  * Adds fixes-test_node_attribute.patch.
+  * Adds fixes_test_fontmap_duplicated_fontentry1.patch.
+  * Fixes Missing Build-Depends on libmagickcore extra lib. Closes: #860689
+- debian/control
+  * Appends libmagickcore-6.q16-3-extra to Build-Depends.
+  * Bumps version debian/compat to 9.
+- Fixes package-uses-deprecated-debhelper-compat-version.
+  * debian/control
+- Appends python-configparser to Build-Depends.
+
+ -- Kouhei Maeda   Fri, 26 May 2017 22:06:40 +0900
+
 blockdiag (1.5.3+dfsg-1.1) unstable; urgency=medium

   * Non-maintainer upload.
diff -Nru blockdiag-1.5.3+dfsg/debian/compat blockdiag-1.5.3+dfsg/debian/compat
--- blockdiag-1.5.3+dfsg/debian/compat2011-05-09 11:31:44.0 +0900
+++ blockdiag-1.5.3+dfsg/debian/compat2017-05-26 00:57:08.0 +0900
@@ -1 +1 @@
-7
+9
diff -Nru blockdiag-1.5.3+dfsg/debian/control
blockdiag-1.5.3+dfsg/debian/control
--- blockdiag-1.5.3+dfsg/debian/control2016-10-11 10:15:43.0 +0900
+++ blockdiag-1.5.3+dfsg/debian/control2017-05-26 22:06:27.0 +0900
@@ -6,6 +6,7 @@
dh-python,
python-all,
python-setuptools,
+   python-configparser,
python-unittest2,
pep8 (>= 1.3),
python-nose,
@@ -17,7 +18,7 @@
python-reportlab,
python-mock,
python-wand,
-   python-pep8,
+   python-pep8,
python3-all,
python3-setuptools,
python3-pep8 (>= 1.3),
@@ -29,7 +30,7 @@
python3-reportlab,
python3-mock,
python3-wand,
-   procps,
+   libmagickcore-6.q16-3-extra,
fonts-vlgothic | fonts-japanese-gothic
 Standards-Version: 3.9.8
 X-Python-Version: 2.7
diff -Nru 
blockdiag-1.5.3+dfsg/debian/patches/848748-exception-ignored-in-Image-del.patch
blockdiag-1.5.3+dfsg/debian/patches/848748-exception-ignored-in-Image-del.patch
--- 
blockdiag-1.5.3+dfsg/debian/patches/848748-exception-ignored-in-Image-del.patch
   2017-01-23 07:13:59.0 +0900
+++ 
blockdiag-1.5.3+dfsg/debian/patches/848748-exception-ignored-in-Image-del.patch
   2017-05-26 01:18:57.0 +0900
@@ -18,9 +18,11 @@
 Bug-Debian: https://bugs.debian.org/848748
 Forwarded: no

 blockdiag-1.5.3+dfsg.orig/src/blockdiag/tests/utils.py
-+++ blockdiag-1.5.3+dfsg/src/blockdiag/tests/utils.py
-@@ -64,7 +64,14 @@ def capture_stderr(func):
+Index: blockdiag-1.5.3+dfsg/src/blockdiag/tests/utils.py
+===
+--- blockdiag-1.5.3+dfsg.orig/src/blockdiag/tests/utils.py
2017-05-25 23:32:58.0 +0900
 blockdiag-1.5.3+dfsg/src/blockdiag/tests/utils.py2017-05-26
01:18:55.308523308 +0900
+@@ -64,7 +64,14 @@

  func(*args, **kwargs)

diff -Nru blockdiag-1.5.3+dfsg/debian/patches/Fixed-remote-image-resouces.patch
blockdiag-1.5.3+dfsg/debian/patches/Fixed-remote-image-resouces.patch
--- blockdiag-1.5.3+dfsg/debian/patches/Fixed-remote-image-resouces.patch
   2016-10-11 10:01:17.0 +0900
+++ blockdiag-1.5.3+dfsg/debian/patches/Fixed-remote-image-resouces.patch
   2017-05-25 23:30:39.0 +0900
@@ -1,66 +1,30 @@
-Description: Fixed remote image resouce for testing data.
+Description: Changes remote image resource to local files from base packages.
 Author: Kouhei Maeda 
-Last-Update: 2014-08-30
+Last-Update: 2017-05-25

 Index: 
blockdiag-1.5.3+dfsg/src/blockdiag/tests/diagrams/background_url_image.diag
 ===

Bug#863513: [Reportbug-maint] Bug#863513: reportbug: No GUI; only '--ui=text'

On Sat, May 27, 2017 at 5:00 PM, Diego A. Casas Toro
 wrote:
> I tried to start reportbug for the first time in KDE Plasma 5, but it did not 
> start.

did you install the additional dependencies as specified by the documentation?

```
How to Use New GTK+ User Interface
==

If you tried to set the new GTK+ UI (named in reportbug as gtk2 ui)
and it fails to start (falling back to text mode, hopefully), chances
are that you are missing some of the packages listed as Suggests, in
particular:

- python3-gi
- python3-gi-cairo
- gir1.2-gtk-3.0
- gir1.2-vte-2.91
- python3-gtkspellcheck

If after installing both of them still GTK+ UI doesn't show up, please
file a report (in text ui :) ).
```

from /usr/share/doc/reportbug/README.Users.gz

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

Bug#861580: (pre-approval) unblock: mysql-connector-python/2.1.6

Control: tags -1 -moreinfo

On Sat, May 27, 2017 at 4:55 PM, Ivo De Decker  wrote:
> Any news on the upload?

2.1.6 has just been uploaded, apologies for the delay

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

Bug#863518: nftables: "workstation" example breaks alternate keyboard layout in gdm

2017-05-27 Thread Harlan Lieberman-Berg

Package: nftables
Version: 0.7-1
Severity: important

Dear Maintainer,

Bizarrely, the quite simple "workstation" example causes the language picker in
gdm3 to disappear and the default layout to switch back to qwerty.  As far as I
can tell this doesn't happen on the next boot, but rather a couple of boots
later.

Disabling the nftables ruleset and rebooting fixes the problem completely.

I'm not sure whether this is an nftables bug or a gdm bug, but I'm putting it
here as similar iptables rules don't cause this behavior.



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

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 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 nftables depends on:
ii  dpkg 1.18.24
ii  init-system-helpers  1.48
ii  libc62.24-10
ii  libgmp10 2:6.1.2+dfsg-1
ii  libmnl0  1.0.4-2
ii  libnftnl41.0.7-1
ii  libreadline7 7.0-3
ii  libxtables12 1.6.0+snapshot20161117-6

nftables recommends no packages.

nftables suggests no packages.

-- Configuration Files:
/etc/nftables.conf changed:
flush ruleset
table inet filter {
chain input {
type filter hook input priority 0;
# accept any localhost traffic
iif lo accept
# accept traffic originated from us
ct state established,related accept
# activate the following line to accept common local services
#tcp dport { 22, 80, 443 } ct state new accept
# accept neighbour discovery otherwise IPv6 connectivity breaks.
ip6 nexthdr icmpv6 icmpv6 type { nd-neighbor-solicit,  
nd-router-advert, nd-neighbor-advert } accept
# count and drop any other traffic
counter drop
}
}


-- no debconf information

Bug#863495: Broken on (at least) amd64, looks in wrong path for libporg-log.so

tags 863495 + pending patch
thanks

I've uploaded porg 0.10-1.1 to DELAYED/5:
  
  porg (2:0.10-1.1) unstable; urgency=medium
  
* Non-maintainer upload.
* Fix broken LD_PRELOAD path for libporg-log.so. (Closes: #863495)

The full debdiff is attached.


Regards,

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

 changelog |7 +++
 rules |2 +-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff -Nru porg-0.10/debian/changelog porg-0.10/debian/changelog
--- porg-0.10/debian/changelog  2016-06-15 05:02:24.0 +0100
+++ porg-0.10/debian/changelog  2017-05-27 23:11:56.0 +0100
@@ -1,3 +1,10 @@
+porg (2:0.10-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix broken LD_PRELOAD path for libporg-log.so. (Closes: #863495)
+
+ -- Chris Lamb   Sat, 27 May 2017 23:11:56 +0100
+
 porg (2:0.10-1) unstable; urgency=low
 
   * Initial release (Closes: #827932)
diff -Nru porg-0.10/debian/rules porg-0.10/debian/rules
--- porg-0.10/debian/rules  2016-06-15 05:02:24.0 +0100
+++ porg-0.10/debian/rules  2017-05-27 23:11:56.0 +0100
@@ -14,4 +14,4 @@
dh $@  --with autotools-dev
 
 override_dh_auto_configure:
-   dh_auto_configure -- --with-porg-logdir=/var/lib/porg
+   dh_auto_configure -- --with-porg-logdir=/var/lib/porg 
--libdir=/usr/lib/porg

Bug#863257: gdm3: stretch - login box displayed off-screen

2017-05-27 Thread Ross Vandegrift

On Sat, May 27, 2017 at 05:56:57PM +0200, Michael Biebl wrote:
> Am 27.05.2017 um 17:50 schrieb Michael Biebl:
> > I remember that this worked in the past, and I suspect an issue related
> > to a kernel update:
> 
> Can you copy the attached service file to /etc/systemd/system/, then run
> systemctl enable dri.service
> Reboot with 4.9, run journalctl -b -u dri.service
> Reboot with 4.8, run journalctl -b -u dri.service

Yep, if I downgrade to a kernel before 4.9.25-1, the display works as expected.

Not sure if it's still helpful, but I'm including the output requested.
Thanks for the investigation and workaround Michael!

With kernel 4.9.25-1:
-
-- Logs begin at Tue 2017-02-07 22:27:19 EST, end at Sat 2017-05-27 17:40:30 
EDT. --
May 27 17:39:47 malaclypse systemd[1]: Started Check dri devices.
May 27 17:39:47 malaclypse sh[824]: /sys/class/drm/card0-DP-1
May 27 17:39:47 malaclypse sh[824]: disconnected
May 27 17:39:47 malaclypse sh[824]: disabled
May 27 17:39:47 malaclypse sh[824]: /sys/class/drm/card0-DP-2
May 27 17:39:47 malaclypse sh[824]: disconnected
May 27 17:39:47 malaclypse sh[824]: disabled
May 27 17:39:47 malaclypse sh[824]: /sys/class/drm/card0-DP-3
May 27 17:39:47 malaclypse sh[824]: disconnected
May 27 17:39:47 malaclypse sh[824]: disabled
May 27 17:39:47 malaclypse sh[824]: /sys/class/drm/card0-DP-4
May 27 17:39:47 malaclypse sh[824]: connected
May 27 17:39:47 malaclypse sh[824]: enabled
May 27 17:39:47 malaclypse sh[824]: /sys/class/drm/card0-DP-5
May 27 17:39:47 malaclypse sh[824]: connected
May 27 17:39:47 malaclypse sh[824]: enabled
May 27 17:39:47 malaclypse sh[824]: /sys/class/drm/card0-HDMI-A-1
May 27 17:39:47 malaclypse sh[824]: disconnected
May 27 17:39:47 malaclypse sh[824]: disabled
May 27 17:39:47 malaclypse sh[824]: /sys/class/drm/card0-HDMI-A-2
May 27 17:39:47 malaclypse sh[824]: disconnected
May 27 17:39:47 malaclypse sh[824]: disabled
May 27 17:39:47 malaclypse sh[824]: /sys/class/drm/card0-eDP-1
May 27 17:39:47 malaclypse sh[824]: connected
May 27 17:39:47 malaclypse sh[824]: enabled


With kernel 4.8.11-1:
-
-- Logs begin at Tue 2017-02-07 22:27:19 EST, end at Sat 2017-05-27 17:59:40 
EDT. --
May 27 17:58:39 malaclypse systemd[1]: Started Check dri devices.
May 27 17:58:39 malaclypse sh[826]: /sys/class/drm/card0-DP-1
May 27 17:58:39 malaclypse sh[826]: disconnected
May 27 17:58:39 malaclypse sh[826]: disabled
May 27 17:58:39 malaclypse sh[826]: /sys/class/drm/card0-DP-2
May 27 17:58:39 malaclypse sh[826]: disconnected
May 27 17:58:39 malaclypse sh[826]: disabled
May 27 17:58:39 malaclypse sh[826]: /sys/class/drm/card0-DP-3
May 27 17:58:39 malaclypse sh[826]: disconnected
May 27 17:58:39 malaclypse sh[826]: disabled
May 27 17:58:39 malaclypse sh[826]: /sys/class/drm/card0-DP-4
May 27 17:58:39 malaclypse sh[826]: connected
May 27 17:58:39 malaclypse sh[826]: enabled
May 27 17:58:39 malaclypse sh[826]: /sys/class/drm/card0-DP-5
May 27 17:58:39 malaclypse sh[826]: connected
May 27 17:58:39 malaclypse sh[826]: enabled
May 27 17:58:39 malaclypse sh[826]: /sys/class/drm/card0-HDMI-A-1
May 27 17:58:39 malaclypse sh[826]: disconnected
May 27 17:58:39 malaclypse sh[826]: disabled
May 27 17:58:39 malaclypse sh[826]: /sys/class/drm/card0-HDMI-A-2
May 27 17:58:39 malaclypse sh[826]: disconnected
May 27 17:58:39 malaclypse sh[826]: disabled
May 27 17:58:39 malaclypse sh[826]: /sys/class/drm/card0-eDP-1
May 27 17:58:39 malaclypse sh[826]: connected
May 27 17:58:39 malaclypse sh[826]: enabled

Ross


signature.asc
Description: PGP signature

Bug#863517: sslh systemd service file doesn't honor /etc/default/sslh

2017-05-27 Thread Cord Beermann

Package: sslh
Version: 1.18-1
Severity: normal

Hello,

I want to use sslh.service with the sslh-select option, but in
/lib/systemd/system/sslh.service is /usr/sbin/sslh hardcoded. 

It should user the information in /etc/default/sslh instead (or switch over to 
update-alternatives?)

Cord

-- System Information:
Debian Release: 8.8
  APT prefers stable
  APT policy: (999, 'stable'), (799, 'stable-updates'), (798, 
'proposed-updates'), (500, 'oldstable'), (299, 'testing'), (199, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages sslh depends on:
ii  adduser  3.113+nmu3
ii  debconf  1.5.56
ii  init-system-helpers  1.22
ii  libc62.19-18+deb8u9
ii  libcap2  1:2.24-8
ii  libconfig9   1.4.9-2
ii  libwrap0 7.6.q-25
ii  lsb-base 4.1+Debian13+nmu1
ii  update-inetd 4.43

Versions of packages sslh recommends:
ii  apache2 [httpd]  2.4.10-10+deb8u8
ii  openssh-server [ssh-server]  1:6.7p1-5+deb8u3

Versions of packages sslh suggests:
ii  openbsd-inetd [inet-superserver]  0.20140418-2

-- debconf information:
* sslh/inetd_or_standalone: standalone

Bug#863477: redis-server: Systemd unit namespace setup can fail on ancient/strange kernels

2017-05-27 Thread Marc Ballarin

Am 27.05.2017 um 20:13 schrieb Chris Lamb:

Can you elaborate more on exactly what this kernel is? eg. what version,
what makes Virtuozzo special here, etc. etc. Trying to work out the
scope of the problem.
Unfortunately, this is a provider kernel. I don't know anything about
its patches or configuration. I don't even have /dev/kmsg or any kernel
related file inside the container.
The full version string is: 3.2.41-042stab120.5 #1 SMP Tue Oct 25
22:31:12 MSK 2016 x86_64 GNU/Linux, but I don't think that tells us more
than that it is ancient and probably heavily patched.

I'm at a loss how to debug the namespace setup:
Strace on PID 1 does not work, most likely due to some hardening (or it
being already traced from the outside):

# strace -p 1
strace: attach: ptrace(PTRACE_ATTACH, 1): Operation not permitted

strace in the unit file is already too late.

Arguably, the best solution - at least for myself - would be, to get rid
of this container.

Nevertheless, the fix to redis-server.service seems straightforward,
even if it is just a workaround for a deeper issue.

Can you comment on whether switching it to /run will work on all systems?
I wouldn't want to push this into Stretch without being very confident.
It seems unit files currently pick /run vs. /var/run at will. Systemd's
own units always use /run, as does LVM, Syslog or ALSA. Samba, CUPS and
DBUs use /var/run.

/run should always work, according to
https://wiki.debian.org/ReleaseGoals/RunDirectory#How_to_transition_from_.2Fvar.2Frun_to_.2Frun_and_.2Fvar.2Flock_to_.2Frun.2Flock.3F

Some additional things I discovered:
1. With the patched unit file there is a follow-up graceful failure:
redis-server.service: SECCOMP features not detected in the kernel,
skipping PrivateDevices=

2. Trying redis-server from Stretch on Wheezy's kernel 3.2.88-1 results
in a failure with "status=227/NO_NEW_PRIVILEGES". This can be worked
around by setting |PrivateDevices=no.
I assume this kernel - unlike the hosted one - knows seccomp, but lacks
"no_new_privs", and that this combination causes a non-graceful failure.

|3. Another unit, mphpsessionclean.service, also has namespace issues:
mphpsessionclean.service: Failed at step NAMESPACE spawning
/usr/lib/php/sessionclean: Value too large for defined data type

Bug#862682: additional info

2017-05-27 Thread Ari

upstreams has an issue on this [1] but not much info there

from a discussion on arch's bbs an patch can be deduced:

--- /usr/share/gnupg/dirmngr-conf.skel  2017-05-27 21:50:57.578027455 +
+++ /usr/share/gnupg/dirmngr-conf.skel  2017-05-27 21:50:48.357812029 +
@@ -67,3 +67,6 @@

 #hkp-cacert /path/to/CA/sks-keyservers.netCA.pem

+# dirmngr fails resolving when /etc/resolv.conf has no IPv4 nameserver
+# see upstream bug https://dev.gnupg.org/T2990
+
+standard-resolver

this will only help users that first start dirmngr. I asked upstream wether 
they see issues with this.

maintainer, please address this in time for stretch's release. Finding this 
workaround is quite unobvious, at least in some situations: for me Linux 
Containers would fail to build.
Also the error message is wrong, which certainly does not help.

Thanks and best regards, Ari



signature.asc
Description: OpenPGP digital signature

Bug#861989: nautilus: Nautilus freezes/crashes when right clicking and selecting properties for 1 or more files

2017-05-27 Thread Jason Crain

On Fri, May 26, 2017 at 08:03:26PM +1000, Luke Christopher Clarke wrote:
> I have not gone out of my way to install any extra nautilus extensions to
> my knowledge. Is there a way I can find that out?
> 
> Also the following is the output from your command. I also went ahead and
> replicated the bug.
> 
...
> (nautilus:1733): Tracker-DEBUG: New TrackerTagsView with 1 files
> (nautilus:1733): Tracker-DEBUG: tracker-backend.vala:37: Waiting for
> service to become available...
> 
> -- END TERMINAL OUTPUT --

It looks like it's frozen because tracker is stuck.  What's the output
of "tracker-control -S"?  And what is the output of running
"tracker-control -k store; TRACKER_VERBOSITY=3 G_DEBUG=all
G_MESSAGES_DEBUG=all /usr/lib/tracker/tracker-store" ?

Bug#863414: coyim FTBFS: xmpp: failed to verify TLS certificate: x509: certificate signed by unknown authority

Hi,

> coyim FTBFS: xmpp: failed to verify TLS certificate: x509:
> certificate signed by unknown authority

Adding `ca-certificates` to Build-Depends works, but then I get different
test failures in the same area (so not tagging as patch).

(Not that the package should really be accessing the internet in the first
place...)



Regards,

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

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

Hi,

On Fri, May 26, 2017 at 12:04:59PM +0200, John Paul Adrian Glaubitz wrote:
> > > As the init system is a rather fundamental component of a Linux
> > > distribution, it affects many other packages, directly or indirectly
> > > and it's therefore too much of a burden to provide support for all
> > > init systems available in Debian. Although runit is available in
> > > Debian, it does not mean that it has to be fully supported.
> > 
> > If an init system is shipped in a stable release, it has to be supported.
> > Otherwise it should not be in a stable release.
> 
> Well, there is also ulibc being shipped with Debian stable. Yet, when
> someone tries to use it and breaks their system, it's not supported
> either. So, I don't think this policy can be sweepingly applied to
> every package.

There is no package named 'ulibc', so I guess that's a typo. If you meant
uclibc, that package only ships uclibc-source, so installing that doesn't
break anything.

> > > A possible solution would be to modify the runit postinst scripts
> > > in a way that it does not automatically overwrite the symlinks
> > > for the the above commands until the machine has been rebooted
> > > (e.g. by placing a script which is run only once after the system
> > > has been first rebooted with runit) so that the 'poweroff' and
> > > 'reboot' commands are still sent to systemd. However, the lack of
> > > a reply of the runit maintainer to this particular bug report seems
> > > to indicate that there is currently no interest for such a solution.
> > 
> > If the maintainer isn't interested in making sure that this package works as
> > expected, it isn't fit for a stable release...
> 
> I fully agree. However, runit is one of the packages which is not
> automatically removed.

No. But it can be manually removed.

> > > Thus, in order to prevent this bug report from blocking the release
> > > of Debian Stretch, I have reduced its severity to 'normal'. You
> > > are still welcome to propose a patch to address this issue though,
> > > it's just not relevant for the upcoming Debian release.
> > 
> > This is not a good reason to downgrade a bug.
> 
> Again, Debian has decided to adopt systemd as the standard init
> system, the same way we have decided to adopt glibc and the Linux
> kernel as the standard C libraries and kernels.
> 
> You really cannot expect a fundamental component like an init system
> to be easily replace by the end user the same way they can swap their
> default text editor.

Well, in that case there shouldn't be a package that tries to swap the init
system. If there is a package that provides the tools to do so, but lets you
do it on your own, that's a different story. It will still allow you to break
your system, but you can do that with lots of tools (certainly with your text
editor).

As there doesn't seem to be an easy way to get an acceptable runit-init
package, which replaces the init system by just installing a package, I don't
see how the current src:runit package can stay in stretch. If someone wants to
keep it, the best option is probably to remove the runit-init binary package,
so that the other binary packages can stay. As Roger noted, that would require
an NMU to do so.

I'd be happy to unblock such a change (if it happens in the next few days,
given the release timing announced in
https://lists.debian.org/debian-devel-announce/2017/05/msg2.html).

Cheers,

Ivo

Bug#862727: ITP: libjasper -- JasPer JPEG-2000 runtime library

2017-05-27 Thread Moritz Muehlenhoff

On Fri, May 19, 2017 at 01:06:08PM +0200, Adam Cecile wrote:
> Control:retitle -1 RFS: jasper/2.0.13+dfsg-1 -- JasPer JPEG-2000 runtime 
> library
> 
> Hi,
> 
> I finished the updated package and reviewed all the CVEs patches that were 
> included.
> Everything is documented in the changelog and there's only one patch not 
> merged yet but I pull-requested it on GitHub.
> 
> I guess it's sadly way too late to get it back for Stretch, but anyway, that 
> would be great to have it in unstable.

This is not a one-off upload, jasper causes a significant
security maintenance overhead. Please only sponsor/upload that if
you're also fully available to adress stable-security.

If you're proceeding with this in unstable, then I also
expect you to deal with src:jasper in jessie from this
point forward.

We should rather stick with one implementation, namely
openjpeg2. Why don't you port opencv instead?

Cheers,
Moritz

Bug#863515: CVE-2017-0350 CVE-2017-0351 CVE-2017-0352

2017-05-27 Thread Moritz Muehlenhoff

Source: nvidia-graphics-drivers
Severity: grave
Tags: security

Please see http://nvidia.custhelp.com/app/answers/detail/a_id/4462

Cheers,
Moritz

Bug#863516: [ntpdate] Returns success exit code on errors

2017-05-27 Thread Roman Mamedov

Package: ntpdate
Version: 1:4.2.6.p5+dfsg-7+deb8u2
Severity: normal

On (some?) errors ntpdate exits with zero (success) exit code:

# ntpdate 2.pool.ntp.org && echo OK || echo Fail
21 Oct 22:34:55 ntpdate[2729]: Can't adjust the time of day: Invalid argument
OK

--- System information. ---
Architecture: armhf
Kernel:   3.4.104-r0-d20-rm2+

-- 
With respect,
Roman

Bug#863488: file: upgrade broke file magic

2017-05-27 Thread Ben Hildred

On Sat, May 27, 2017 at 1:25 PM, Christoph Biedl <
debian.a...@manchmal.in-ulm.de> wrote:

> tags 863488 moreinfo unreproducible
> thanks
>
> Ben Hildred wrote...
>
> > A recent upgrade has rendered file just about usless as it is only able
> to
> > identify text in the most limited sense.
>
> Works for me:
>
> > for example:
> > $ file /usr/bin/file
> > /etc/magic, 4: Warning: using regular magic file `/usr/share/misc/magic'
> > /usr/bin/file: data
>
> /usr/bin/file: ELF 32-bit LSB shared object, Intel 80386, version 1
> (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux
> 2.6.32, BuildID[sha1]=2f833ab1ff58c9e0ae5801481a0dff1da286f30b, stripped
>
> that's more like it.


> (see the release notes why it's not "executable" any longer)
>
> It hasn't been an issue.


> > or:
> > $ file /usr/share/doc/file/*
> > /etc/magic, 4: Warning: using regular magic file `/usr/share/misc/magic'
> > /usr/share/doc/file/changelog.Debian.gz: data
> > /usr/share/doc/file/changelog.gz:data
> > /usr/share/doc/file/copyright:   ASCII text
> > /usr/share/doc/file/README.Debian:   ASCII text
> > /usr/share/doc/file/README.gz:   data
>
> Results in the expected output.
>
> What is in /usr/share/misc/magic, and where did the file(s) come
> from?
>
> it is a symbolic link to '../file/magic' which is/usr/share/file/magic an
empty directory. There is also  /usr/share/file/magic.mgc which is a
symbolic link pointing to ../../lib/file/magic.mgc. If I create a symbolic
link from /usr/share/misc/magic.mgc to /usr/lib/file/magic.mgc it starts
working again.


> Christoph
>



-- 
--
Ben Hildred
Automation Support Services

Bug#861713: netdata: `service netdata restart` fails due to missing pidfile

2017-05-27 Thread Daniel Ring

Control: reopen -1
Control: found -1 1.6.0+dfsg-2

This bug is still present in the current version of netdata.

The patch Daniel Piddock provided fixes the start and stop init triggers,
but unfortunately restart is still broken. It looks like the stop trigger
returns before netdata actually shuts down and causes the start trigger
afterward to fail.

Sincerely,
Daniel Ring

Bug#863514: python-django: Please document rules for updating Django

2017-05-27 Thread Scott Kitterman

Package: python-django
Version: 1.7.11-1+deb8u2
Severity: normal
Tags: patch

As has been discussed extensively, update of python-django to a new major/
minor version can have substantial impacts on other packages and system
upgradability.  It would be helpful to have the policy for updates documented
so that maintainers of Django related packages know what to expect.

Please see the attached patch for a suggested first draft.

Scott K
diff -Nru python-django-1.11.1/debian/changelog python-django-1.11.1/debian/changelog
--- python-django-1.11.1/debian/changelog	2017-05-06 14:32:33.0 -0400
+++ python-django-1.11.1/debian/changelog	2017-05-27 17:01:23.0 -0400
@@ -1,3 +1,9 @@
+python-django (1:1.11.1-4) UNRELEASED; urgency=medium
+
+  * Add considerations for version upgrades to README.Source
+
+ -- Scott Kitterman   Sat, 27 May 2017 17:00:44 -0400
+
 python-django (1:1.11.1-3) experimental; urgency=medium
 
   * Really add Build-Depends on libgdal-dev.
diff -Nru python-django-1.11.1/debian/README.source python-django-1.11.1/debian/README.source
--- python-django-1.11.1/debian/README.source	2017-05-06 14:32:33.0 -0400
+++ python-django-1.11.1/debian/README.source	2017-05-27 17:00:31.0 -0400
@@ -1,3 +1,26 @@
+Introduction of new Django versions to Unstable
+---
+
+The upstream Django project only supports API compatibility between its Long
+Term Support (LTS) releases.  In order to support user upgrades in Debian, the
+python-django package in Unstable/Testing must not skip an LTS release from
+the current Debian Stable version.  
+
+As a result, only LTS releases should be uploaded to Unstable/Testing.
+Non-LTS releases should be uploaded to Experimental to allow maintainers of
+reverse-depends to test and update their packages with the newer releases to
+ease preparation for transition to the next LTS release.
+
+Update of python-django in Unstable to a new major/minor version should be
+coordinated with maintainers of reverse-depends, much like a library
+transition is handled.  Micro version updates do not require coordination.
+
+If there is a newer LTS release available in Testing, it will often be
+backported to the current stable release.  Keeping the upgrade path clean for
+an LTS to LTS upgrade when then next Debian release occurs will also make
+updates to the stable backport possible without needing explicit additional
+coordination with the Backports team.
+
 Git packaging rules for python-django
 -

Bug#863513: reportbug: No GUI; only '--ui=text'

2017-05-27 Thread Diego A. Casas Toro

Package: reportbug
Version: 7.1.6
Severity: important

Dear Maintainer,

I tried to start reportbug for the first time in KDE Plasma 5, but it did not 
start. 
I thought it was a problem with the '.desktop' file asociated with the menu 
entry. 
Then I realized that reportbug was starting in the background, without gtk2 GUI.

I tried to start reportbug from Konsole using '--ui=gtk2', but it starts in 
text mode 
and shows 'Ignored bogus setting for --ui: gtk'. I don't understand why 
reportbug shows
"Ignored bogus setting" when the man entry says "Valid options are text, urwid, 
and gtk2".

I realized that the autocompletion give these options: "gnome newt text", but 
gnome 
and newt cause the same output: 'Ignored bogus setting for --ui'. The bug is 
the same 
with '--interface' and '-u'.

I updated and reinstalled reportbug, but I couldn't solve the problem. 
Actually, I'm 
reporting this bug from command line.

Even if the man entry is wrong, and gnome replaces gtk2 option, reportbug 
should start 
using GUI. So, to conclude, there are two problems: the man entry is incorrect, 
and the 
reportbug program has a missing GUI.


-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/dact/.reportbugrc:
reportbug_version "7.1.6"
mode standard
ui text
email "daca...@uninorte.edu.co"
no-cc
header "X-Debbugs-CC: daca...@uninorte.edu.co"
smtphost reportbug.debian.org

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

Versions of packages reportbug depends on:
ii  apt1.4.4
ii  python3-reportbug  7.1.6
pn  python3:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail   
pn  debconf-utils
pn  debsums  
pn  dlocate  
pn  emacs23-bin-common | emacs24-bin-common  
ii  file 1:5.30-1
ii  gir1.2-gtk-3.0   3.22.11-1
pn  gir1.2-vte-2.91  
ii  gnupg2.1.18-6
pn  postfix | exim4 | mail-transport-agent   
ii  python3-gi   3.22.0-2
pn  python3-gi-cairo 
pn  python3-gtkspellcheck
pn  python3-urwid
ii  xdg-utils1.1.1-1

Versions of packages python3-reportbug depends on:
ii  apt1.4.4
ii  file   1:5.30-1
ii  python3-debian 0.1.30
ii  python3-debianbts  2.6.1
ii  python3-requests   2.12.4-1
pn  python3:any

python3-reportbug suggests no packages.

-- no debconf information

Bug#863512: numba: segfault on test_shape [s390x]

Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=s390x=0.33.0-1=1495911986=0

This test breaks on s390x:


numba/tests/test_array_attr.py::TestNestedArrayAttr::test_shape Segmentation 
fault
E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build && python2.7 -Wd -m pytest 
numba/tests -v -rs
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#861580: (pre-approval) unblock: mysql-connector-python/2.1.6

Hi,

On Sat, May 20, 2017 at 08:34:00AM +, Niels Thykier wrote:
> Sandro Tosi:
> >> NOTE: the test suite contains certificates that expire in 2018.  If that
> >> causes test failures, then that is an RC bug (as it would mean we would
> >> be unable to compile mysql-connector-python in stretch before its EOL).
> >> AFAICT, said problem would also exists in the current version (except
> >> the expiry reads 2017 instead).
> >>   Please consider replacing the certificates with once that can survive
> >> stretch + stretch-lts's life-time.
> > 
> > that's kinda tricky: what is the lifetime for stretch + stretch-lts?
> > :) should i guess (inferring from previous releases), do you want to
> > give me a date until making those certs valid, something else?
> > 
> 
> (For future cases) I would say 10 years would suffice once the freeze
> has started.  That said, I hope that there will be fewer cases of this
> problem in general. :)
> 
> > As of now tests failure wont make the build fail, so --if that's ok
> > with the RT-- i may continue with keeping those certs as upstream
> > released them.
> 
> Ack, fine with me.  Please go ahead with the certs as is.

Any news on the upload? The release is very close now. More info on the timing
and the deadlines in
https://lists.debian.org/debian-devel-announce/2017/05/msg2.html

Maybe someone can upload this patch as an NMU?

Cheers,

Ivo

Bug#863510: ITP: node-readable-stream -- A stream compatibility library for Node.js and browser

2017-05-27 Thread Bastien ROUCARIES

Package: wnpp
Severity: wishlist
Owner: ro...@debian.org
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-readable-stream
  Version : 2.2.9
  Upstream Author : FIX_ME upstream author
* URL : https://github.com/nodejs/readable-stream#readme
* License : Expat
  Programming Lang: JavaScript
  Description : A stream compatibility library for Node.js and browser

 This package is a port to browser context of the well know stream API
of Node.js
.
A stream is an abstract interface for working with streaming data in Node.js.
There are many stream objects provided by Node.js. For instance, a request
 to an HTTP server and process.stdout are both stream instances.
 .
 Node.js is an event-based server-side JavaScript engine.

Bug#863507: numba: tests are not running/immediately breaking (plugin custom failed with: exit code=1) [armel, armhf]

Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=armel=0.33.0-1=1495912245=0
https://buildd.debian.org/status/fetch.php?pkg=numba=armhf=0.33.0-1=1495912383=0

Tests are immediately breaking on armel and armhf:


PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="cd {build_dir} && {interpreter} -Wd -m 
pytest numba/tests -v -rs" dh_auto_test || true
I: pybuild base:184: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build && 
python2.7 -Wd -m pytest numba/tests -v -rs
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.0.6, py-1.4.32, pluggy-0.4.0 -- 
/usr/bin/python2.7
cachedir: ../../../.cache
rootdir: /«PKGBUILDDIR», inifile: 
collecting ... E: pybuild pybuild:283: test: plugin custom failed with: exit 
code=1: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build && python2.7 -Wd -m 
pytest numba/tests -v -rs
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#863509: numba: test_mean_magnitude breaks (plugin custom failed with: exit code=1) [mips, mipsel]

Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=mips=0.33.0-1=1495913987=0
https://buildd.debian.org/status/fetch.php?pkg=numba=mipsel=0.33.0-1=1495915594=0

This test breaks appears on the mips archs:


numba/tests/test_array_reductions.py::TestArrayReductions::test_mean_basic 
PASSED
numba/tests/test_array_reductions.py::TestArrayReductions::test_mean_magnitude 
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build && python2.7 -Wd -m pytest 
numba/tests -v -rs
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#863511: numba: segfault on test_array_reshape [ppc64el]

Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=ppc64el=0.33.0-1=1495912133=0

Tests break with a segault on s390x:


numba/tests/test_array_manipulation.py::TestArrayManipulation::test_add_axis2_npm
 PASSED
numba/tests/test_array_manipulation.py::TestArrayManipulation::test_array_reshape
 Segmentation fault
E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build && python2.7 -Wd -m pytest 
numba/tests -v -rs
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#863508: numba: FTBFS: LLVM ERROR: Program used external function '__aeabi_unwind_cpp_pr0' [armel, armhf]

Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=armel=0.33.0-1=1495912245=0
https://buildd.debian.org/status/fetch.php?pkg=numba=armhf=0.33.0-1=1495912383=0

FTBFS on armel and armhf:


http_proxy='127.0.0.1:9' sphinx-build -N -bhtml 
.pybuild/pythonX.Y_2.7/build/docs/source/ 
debian/numba-doc/usr/share/doc/numba-doc/html/
Running Sphinx v1.4.9
making output directory...
LLVM ERROR: Program used external function '__aeabi_unwind_cpp_pr0' which could 
not be resolved!
debian/rules:22: recipe for target 'override_dh_installdocs' failed
make[1]: *** [override_dh_installdocs] Error 1


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#863506: numba: KeyError in numba/tracing.py [amd64, i386, arm64]

Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=i386=0.33.0-1=1495914429=0
https://buildd.debian.org/status/fetch.php?pkg=numba=arm64=0.33.0-1=1495916190=0

This test failure appears:


_ test _

args = (), kwds = {}, fname = 'numba.tests.test_tracing.test', ftype = None

def wrapper(*args, **kwds):
if not logger.isEnabledFor(logging.INFO) or tls.tracing:
return func(*args, **kwds)

fname, ftype = find_function_info(func, spec, args)

try:
tls.tracing = True
>   enter, leave = create_events(fname, spec, args, kwds)

numba/tracing.py:103: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

fname = 'numba.tests.test_tracing.test'
spec = ArgSpec(args=['x', 'y', 'z'], varargs=None, keywords=None, 
defaults=(True,))
args = (), kwds = {}

def create_events(fname, spec, args, kwds):

values = dict()
if spec.defaults:
values = dict(zip(spec.args[-len(spec.defaults):],spec.defaults))
values.update(kwds)
values.update(list(zip(spec.args[:len(args)], args)))
>   positional = ['%s=%r'%(a, values.pop(a)) for a in spec.args]
E   KeyError: 'x'

numba/tracing.py:66: KeyError


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#845735: New upstream release 2.0.2 available

Control: retitle -1 New upstream release 2.0.3 available
Control: severity -1 important


Hi Pierre!

On Sat, 26 Nov 2016 11:30:04 +0100 Michael Biebl  wrote:
> Source: liblognorm
> Version: 2.0.1-1.1
> Severity: wishlist
> 
> Hi,
> 
> there is a new upstream release available.
> 
> http://www.liblognorm.com/news/liblognorm-2-0-2-released/
> 
> Would be nice to see it packaged for Debian in time for stretch.
> 

The latest upstream release is now 2.0.3 and newer versions of rsyslog
require that, so bumping the severity.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#863505: numba: AssertionError in TestTimedeltaArithmeticNoPython.test_mul and others [arm64]

Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=arm64=0.33.0-1=1495916190=0

There are a couple of supposedly related test failures on arm64:


___ TestTimedeltaArithmeticNoPython.test_mul ___

self = 

def test_mul(self):
f = self.jit(mul_usecase)
def check(a, b, expected):
self.assertPreciseEqual(f(a, b), expected)
self.assertPreciseEqual(f(b, a), expected)

# non-int64 int * timedelta64
check(TD(3), np.uint32(2), TD(6))
# int * timedelta64
check(TD(3), 2, TD(6))
check(TD(3, 'ps'), 2, TD(6, 'ps'))
check(TD('NaT', 'ps'), 2, TD('NaT', 'ps'))
# float * timedelta64
check(TD(7), 1.5, TD(10))
check(TD(-7), 1.5, TD(-10))
check(TD(7, 'ps'), -1.5, TD(-10, 'ps'))
check(TD(-7), -1.5, TD(10))
check(TD('NaT', 'ps'), -1.5, TD('NaT', 'ps'))
>   check(TD(7, 'ps'), float('nan'), TD('NaT', 'ps'))

numba/tests/test_npdatetime.py:328: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_npdatetime.py:313: in check
self.assertPreciseEqual(f(a, b), expected)
numba/tests/support.py:257: in assertPreciseEqual
self.fail("when comparing %s and %s: %s" % (first, second, failure_msg))
E   AssertionError: when comparing 0 picoseconds and NaT: 
numpy.timedelta64(0,'ps') != numpy.timedelta64('NaT','ps')



___ TestLoopTypesDatetimeNoPython.test_multiply_dm_m ___

self = 

def test_template(self):
fn = _make_ufunc_usecase(ufunc)
>   self._check_loop(fn, ufunc, loop)

numba/tests/test_ufuncs.py:1514: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_ufuncs.py:1471: in _check_loop
self._check_ufunc_with_dtypes(fn, ufunc, letter_types)
numba/tests/test_ufuncs.py:1500: in _check_ufunc_with_dtypes
ulps=ulps)
numba/tests/support.py:257: in assertPreciseEqual
self.fail("when comparing %s and %s: %s" % (first, second, failure_msg))
E   AssertionError: when comparing [   -4 0 3 'NaT' 'NaT' 0-7 
'NaT'] and [   -4 0 3 'NaT' 'NaT' 0-7 0]: 
numpy.timedelta64('NaT','D') != numpy.timedelta64(0,'D') : ufunc 'multiply' 
arrays differ ([array([ 1.5,  0. ,  1.5,  nan, -3.5,  0. , -3.5,  nan]), 
array([   -3, 0, 2, 'NaT', 'NaT',-3, 2, 0], 
dtype='timedelta64[D]'), array([   -4, 0, 3, 'NaT', 'NaT', 0,
-7, 0], dtype='timedelta64[D]')]):
E   args: exact
E   expected [   -4 0 3 'NaT' 'NaT' 0-7 'NaT']
E   got [   -4 0 3 'NaT' 'NaT' 0-7 0]



___ TestLoopTypesDatetimeNoPython.test_multiply_md_m ___

self = 

def test_template(self):
fn = _make_ufunc_usecase(ufunc)
>   self._check_loop(fn, ufunc, loop)

numba/tests/test_ufuncs.py:1514: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_ufuncs.py:1471: in _check_loop
self._check_ufunc_with_dtypes(fn, ufunc, letter_types)
numba/tests/test_ufuncs.py:1500: in _check_ufunc_with_dtypes
ulps=ulps)
numba/tests/support.py:257: in assertPreciseEqual
self.fail("when comparing %s and %s: %s" % (first, second, failure_msg))
E   AssertionError: when comparing [   -7 'NaT' 3 0 0 'NaT'-4 
'NaT'] and [   -7 'NaT' 3 0 0 'NaT'-4 0]: 
numpy.timedelta64('NaT','D') != numpy.timedelta64(0,'D') : ufunc 'multiply' 
arrays differ ([array([2, 'NaT', 2, 0,-3, 'NaT',-3, 0], 
dtype='timedelta64[D]'), array([-3.5,  nan,  1.5,  0. ,  0. , -3.5,  1.5,  
nan]), array([   -7, 'NaT', 3, 0, 0, 'NaT',-4, 0], 
dtype='timedelta64[D]')]):
E   args: exact
E   expected [   -7 'NaT' 3 0 0 'NaT'-4 'NaT']
E   got [   -7 'NaT' 3 0 0 'NaT'-4 0]


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#863504: numba: AssertionError in TestRaising.test_assert_statement_objmode [amd64, i386, arm64]

Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=arm64=0.33.0-1=1495916190=0
https://buildd.debian.org/status/fetch.php?pkg=numba=i386=0.33.0-1=1495914429=0

This test failure appears:


__ TestRaising.test_assert_statement_objmode ___

self = 

def test_assert_statement_objmode(self):
>   self.check_assert_statement(flags=force_pyobj_flags)

numba/tests/test_exceptions.py:196: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_exceptions.py:193: in check_assert_statement
self.assertEqual(str(cm.exception), "bar")
E   AssertionError: 'bar\nassert 2 == 1' != 'bar'


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#863131: unblock: tomcat-native/1.2.12-2

Control: tags -1 moreinfo

Hi,

On Mon, May 22, 2017 at 02:40:01PM +0200, Emmanuel Bourg wrote:
> I'd like to request an unblock for a new version of tomcat-native. Testing
> currently has the 1.2.10 version. The versions 1.2.11 and 1.2.12 are bug
> fix releases improving the stability.

Please go ahead with the upload to unstable. We can consider the unblock once
the package is in unstable. Please remove the moreinfo tag from this bug at
that point.

Please note that we are very close to the release. More info about the
deadlines in
https://lists.debian.org/debian-devel-announce/2017/05/msg2.html

Cheers,

Ivo

Bug#863503: numba: numba/compiler.py:243: ConstantInferenceError [amd64, i386, arm64]

Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=i386=0.33.0-1=1495914429=0
https://buildd.debian.org/status/fetch.php?pkg=numba=arm64=0.33.0-1=1495916190=0

This failure appears among the tests several times:


__ TestRaising.test_assert_statement_nopython __

self = 

def test_assert_statement_nopython(self):
>   self.check_assert_statement(flags=no_pyobj_flags)

numba/tests/test_exceptions.py:199: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_exceptions.py:188: in check_assert_statement
cres = compile_isolated(pyfunc, (types.int32,), flags=flags)
numba/compiler.py:150: in compile_isolated
flags, locals)
numba/compiler.py:704: in compile_extra
return pipeline.compile_extra(func)
numba/compiler.py:357: in compile_extra
return self._compile_bytecode()
numba/compiler.py:665: in _compile_bytecode
return self._compile_core()
numba/compiler.py:652: in _compile_core
res = pm.run(self.status)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
status = fail_reason=None, can_fallback=False, can_giveup=False

def run(self, status):
assert self._finalized, "PM must be finalized before run()"
res = None
for pipeline_name in self.pipeline_order:
event(pipeline_name)
is_final_pipeline = pipeline_name == self.pipeline_order[-1]
for stage, stage_name in self.pipeline_stages[pipeline_name]:
try:
event(stage_name)
stage()
except _EarlyPipelineCompletion as e:
return e.result
except BaseException as e:
msg = "Failed at %s (%s)" % (pipeline_name, stage_name)
patched_exception = self._patch_error(msg, e)
# No more fallback pipelines?
if is_final_pipeline:
>   raise patched_exception
E   ConstantInferenceError: Caused By:
E   Traceback (most recent call last):
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/compiler.py", line 235, in 
run
E   stage()
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/compiler.py", line 466, in 
stage_generic_rewrites
E   self, self.func_ir)
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/rewrites/registry.py", 
line 71, in apply
E   pipeline.calltypes)
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/rewrites/static_raise.py", 
line 43, in match
E   const = interp.infer_constant(inst.exception)
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/ir.py", line 873, in 
infer_constant
E   return self._consts.infer_constant(name)
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/consts.py", line 44, in 
infer_constant
E   raise exc(*args)
E   ConstantInferenceError: constant inference not possible 
for call $108.23(@py_format6)
E   
E   Failed at nopython (nopython rewrites)
E   constant inference not possible for call 
$108.23(@py_format6)

numba/compiler.py:243: ConstantInferenceError


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#863497: debsign: Cannot sign just a dsc

2017-05-27 Thread Mattia Rizzolo

Control: tag -1 pending

On Sat, May 27, 2017 at 08:18:03PM +0100, James Clarke wrote:
> Hi,
> Invoking `debsign foo.dsc` gives the error:
> 
> > debsign: Can't find or can't read dsc file !
> 
> The attached patch fixes it.

Thanks, applied!

https://anonscm.debian.org/git/collab-maint/devscripts.git/commit/?id=51e909fdd79c94a957bf441b1c4e4b5e457a07d5

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#863380: unblock: wireshark/2.2.6+g32dac6a-2

Control: tags -1 confirmed moreinfo

Hi,

On Fri, May 26, 2017 at 12:25:07AM +0200, Bálint Réczey wrote:
> I have prepared wireshark 2.2.6+g32dac6a-1 in experimental which fixes
> 10 vulnerabilities and other bugs which are not listed here, just on
> the release notes link.
> 
> Changes:
>  wireshark (2.2.6+g32dac6a-1) experimental; urgency=medium
>  .
>* New upstream release
>  - release notes:
>https://www.wireshark.org/docs/relnotes/wireshark-2.2.6.html
>  - security fixes:
>- The IMAP dissector could crash (CVE-2017-7703)
>- The WBXML dissector could enter an infinite loop (CVE-2017-7702)
>- The NetScaler file parser could enter an infinite loop
>  (CVE-2017-7700)
>- The RPCoRDMA dissector enter an infinite loop (CVE-2017-7705)
>- The BGP dissector could enter an infinite loop (CVE-2017-7701)
>- The DOF dissector could enter an infinite loop (CVE-2017-7704)
>- The PacketBB dissector could crash (CVE-2017-7747)
>- The SLSK dissector could enter a long loop (CVE-2017-7746)
>- The SIGCOMP dissector could enter an infinite loop
>  (CVE-2017-7745)
>- The WSP dissector could enter an infinite loop (CVE-2017-7748)
> 
> 
> I believe wireshark point releases very rarely cause regressions due
> to the heavy testing performed upstream and I think it would be safe
> to upload this point release to unstable and let it migrate to
> testing.
> 
> If you wouldn't like to accept the full point release to Stretch I
> will happily backport the security fixes to 2.2.5 and upload that to
> unstable.
> 
> Please share your preference regarding the next upload.

Please go ahead with the upload to unstable and remove the moreinfo tag from
this bug once the builds are done on all the relevant architectures.

Also, please note that we are very close to the release date. More info about
the deadlines in
https://lists.debian.org/debian-devel-announce/2017/05/msg2.html

Cheers,

Ivo

Bug#863501: numba: RuntimeError: cannot cache function 'simple_usecase' [amd64, i386, arm64]

Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=i386=0.33.0-1=1495914429=0
https://buildd.debian.org/status/fetch.php?pkg=numba=arm64=0.33.0-1=1495916190=0

This failure appeared in the tests:


_ TestCache.test_non_creatable_pycache _

self = 

@unittest.skipIf(os.name == "nt",
 "cannot easily make a directory read-only on Windows")
def test_non_creatable_pycache(self):
# Make it impossible to create the __pycache__ directory
old_perms = os.stat(self.tempdir).st_mode
os.chmod(self.tempdir, 0o500)
self.addCleanup(os.chmod, self.tempdir, old_perms)

>   self._test_pycache_fallback()

numba/tests/test_dispatcher.py:954: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_dispatcher.py:926: in _test_pycache_fallback
mod = self.import_module()
numba/tests/test_dispatcher.py:623: in import_module
mod = import_dynamic(self.modname)
numba/tests/support.py:527: in import_dynamic
__import__(modname)
/tmp/numba-tests.1000/test_cache-jXZpdc/dispatcher_caching_test_fodder.py:19: 
in 
@jit(cache=True, nopython=True)
numba/decorators.py:175: in wrapper
disp.enable_caching()
numba/dispatcher.py:490: in enable_caching
self._cache = FunctionCache(self.py_func)
numba/caching.py:594: in __init__
self._impl = self._impl_class(py_func)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
py_func = 

def __init__(self, py_func):
self._is_closure = bool(py_func.__closure__)
self._lineno = py_func.__code__.co_firstlineno
# Get qualname
try:
qualname = py_func.__qualname__
except AttributeError:
qualname = py_func.__name__
# Find a locator
source_path = inspect.getfile(py_func)
for cls in self._locator_classes:
locator = cls.from_function(py_func, source_path)
if locator is not None:
break
else:
raise RuntimeError("cannot cache function %r: no locator available "
>  "for file %r" % (qualname, source_path))
E   RuntimeError: cannot cache function 'simple_usecase': no locator 
available for file 
'/tmp/numba-tests.1000/test_cache-jXZpdc/dispatcher_caching_test_fodder.py'

numba/caching.py:330: RuntimeError


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#861900: your mail

Hi,

Sorry for the delay in dealing with this request.

On Mon, May 15, 2017 at 07:46:50AM +, PICCA Frederic-Emmanuel wrote:
> I attached the debdiff of the sardana 2.2.2-3 version prepared by the upsteam.
> 
> the changes are:
>  - add themself to Uploaders (at my request).
>  - Remove the dependency on the nexus package (which is broken)
>  - Implement  the nexus functionnaly with the well maintained h5py.
> 
> 
> thanks for considering the pre-approval
> 
> If it is ok, I will upload into unstable.

I'm reluctant to allow this, but as it seems to be a way to get rid of the
dependency on python-nxs, I'm willing to consider it. We are very close to the
release, so I suggest you upload it to unstable, and we can consider the
unblock once it's uploaded.

Please remove the moreinfo tag from this bug once the upload is in unstable.

Cheers,

Ivo

Bug#863496: debian-handbook: add a wireless configuration section

2017-05-27 Thread Matthew Donnelly

Missed that line wrap ...

Dear Maintainer,

I apologize if this is out of place or I am missing something; this is my
first contribution to open source.

I have been browsing through The Debian Administrator's Handbook and noticed
that there is no section describing how to configure wireless from the command
line. This was a major struggle when I first used Debian, and I would like to
write a section (probably in 8.2 of the handbook) illustrating how to do this.
Any help related to how I should create and submit the patch is welcomed.

Thank You,
Matthew D

Bug#863493: symfony: diff for NMU version 2.8.7+dfsg-1.3

2017-05-27 Thread James Clarke

Dear maintainer,

I've prepared an NMU for symfony (versioned as 2.8.7+dfsg-1.3) and
uploaded it to unstable. The diff is attached to this message.

Regards,
James
diff -Nru symfony-2.8.7+dfsg/debian/changelog symfony-2.8.7+dfsg/debian/changelog
--- symfony-2.8.7+dfsg/debian/changelog	2017-01-29 16:05:28.0 +
+++ symfony-2.8.7+dfsg/debian/changelog	2017-05-27 20:39:09.0 +0100
@@ -1,3 +1,13 @@
+symfony (2.8.7+dfsg-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport additional upstream patches needed after PHP 7.0.18 upload
+(Closes: #863493):
+- [VarDumper] Relax tests to adapt for php 7.1rc4
+- [VarDumper] Relax line number for CliDumperTest
+
+ -- James Clarke   Sat, 27 May 2017 20:39:09 +0100
+
 symfony (2.8.7+dfsg-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru symfony-2.8.7+dfsg/debian/patches/series symfony-2.8.7+dfsg/debian/patches/series
--- symfony-2.8.7+dfsg/debian/patches/series	2017-01-29 16:05:28.0 +
+++ symfony-2.8.7+dfsg/debian/patches/series	2017-05-27 20:39:09.0 +0100
@@ -7,3 +7,5 @@
 do-not-depend-on-a-fixed-date-in-layout-
 update-ipvalidatortest-data-set-with-a-v
 relax-1-test-failing-with-latest-php-ver
+vardumper-relax-tests-to-adapt-for-php-7
+vardumper-relax-line-number-for-clidumpe
diff -Nru symfony-2.8.7+dfsg/debian/patches/vardumper-relax-line-number-for-clidumpe symfony-2.8.7+dfsg/debian/patches/vardumper-relax-line-number-for-clidumpe
--- symfony-2.8.7+dfsg/debian/patches/vardumper-relax-line-number-for-clidumpe	1970-01-01 01:00:00.0 +0100
+++ symfony-2.8.7+dfsg/debian/patches/vardumper-relax-line-number-for-clidumpe	2017-05-27 20:39:09.0 +0100
@@ -0,0 +1,28 @@
+From: James Clarke 
+Date: Sat, 27 May 2017 19:48:09 +0100
+X-Dgit-Generated: 2.8.7+dfsg-1.3 d28625b7a6b1b5e9be0b3e2af3e79cbabf6a8bbe
+Subject: [VarDumper] Relax line number for CliDumperTest
+
+Origin: backport, https://github.com/symfony/symfony/commit/6ef78ec55317ac473fa045706244ef1f97d4b2de
+
+---
+
+--- symfony-2.8.7+dfsg.orig/src/Symfony/Component/VarDumper/Tests/CliDumperTest.php
 symfony-2.8.7+dfsg/src/Symfony/Component/VarDumper/Tests/CliDumperTest.php
+@@ -188,7 +188,6 @@ EOTXT
+ }
+ };'),
+ ));
+-$line = __LINE__ - 2;
+ $ref = (int) $out;
+ 
+ $data = $cloner->cloneVar($out);
+@@ -261,7 +260,7 @@ stream resource {@{$ref}
+   }
+   %d. %slosure%s() ==> Twig_Template->render(): {
+ src: {
+-  %sCliDumperTest.php:{$line}: """
++  %sCliDumperTest.php:%d: """
+ %A
+ """
+ }
diff -Nru symfony-2.8.7+dfsg/debian/patches/vardumper-relax-tests-to-adapt-for-php-7 symfony-2.8.7+dfsg/debian/patches/vardumper-relax-tests-to-adapt-for-php-7
--- symfony-2.8.7+dfsg/debian/patches/vardumper-relax-tests-to-adapt-for-php-7	1970-01-01 01:00:00.0 +0100
+++ symfony-2.8.7+dfsg/debian/patches/vardumper-relax-tests-to-adapt-for-php-7	2017-05-27 20:39:09.0 +0100
@@ -0,0 +1,22 @@
+From: Nicolas Grekas 
+Date: Fri, 7 Apr 2017 11:49:35 +0200
+X-Dgit-Generated: 2.8.7+dfsg-1.3 0d8f420c173478e3c199b75e16417bdee99faedf
+Subject: [VarDumper] Relax tests to adapt for php 7.1rc4
+
+Origin: https://github.com/symfony/symfony/commit/3672c01e3c7182888a42b74e2864a20e21cfe7f5
+
+---
+
+--- symfony-2.8.7+dfsg.orig/src/Symfony/Component/VarDumper/Tests/CliDumperTest.php
 symfony-2.8.7+dfsg/src/Symfony/Component/VarDumper/Tests/CliDumperTest.php
+@@ -262,9 +262,7 @@ stream resource {@{$ref}
+   %d. %slosure%s() ==> Twig_Template->render(): {
+ src: {
+   %sCliDumperTest.php:{$line}: """
+-}\\n
+-};'),\\n
+-));\\n
++%A
+ """
+ }
+   }

Bug#863500: sddm: SDDM doesn't allow empty password field for passwordless account

2017-05-27 Thread Diego A. Casas Toro

Package: sddm
Version: 0.14.0-4
Severity: normal

Dear Maintainer,

I did 'passwd -d' and activated autologin. It start seamlessly, but when I try 
to 
logout and relogin using i3-wm, SDDM ask for password. Supposedly, 'passwd -d' 
made the password empty, but SDDM doesn't allow empty password field; it shows 
"Failed Login".

Currently, I'm unable to relogin after logout, so I can't use a different DE. 
The 
only workaround to relogin is start tty1 as root and do 'systemctl restart 
sddm.service'. 
This make SDDM to start in autologin mode, and I get back to Plasma without 
typing my 
password.

I think SDDM should allow me to login without asking password, or at least 
allow empty 
password field.


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

Versions of packages sddm depends on:
ii  adduser 3.115
ii  debconf [debconf-2.0]   1.5.61
ii  libc6   2.24-10
ii  libgcc1 1:6.3.0-18
ii  libpam0g1.1.8-3.5
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5network5  5.7.1+dfsg-3+b1
ii  libqt5qml5  5.7.1-2+b2
ii  libqt5quick55.7.1-2+b2
ii  libstdc++6  6.3.0-18
ii  libsystemd0 232-23
ii  libxcb-xkb1 1.12-1
ii  libxcb1 1.12-1
ii  qml-module-qtquick2 5.7.1-2+b2
ii  x11-common  1:7.7+19
ii  xserver-xorg [xserver]  1:7.7+19

Versions of packages sddm recommends:
ii  libpam-systemd 232-23
ii  sddm-theme-breeze [sddm-theme] 4:5.8.6-2
ii  sddm-theme-debian-breeze [sddm-theme]  4:5.8.6-2
ii  sddm-theme-debian-maui [sddm-theme]0.14.0-4

Versions of packages sddm suggests:
ii  libpam-kwallet5  5.8.4-1

-- debconf information:
  sddm/daemon_name: /usr/bin/sddm
* shared/default-x-display-manager: sddm

Bug#863499: Trash: sort the files/folders by "time of deletion"

2017-05-27 Thread Christian Buhtz

Package: thunar
Version: 1.6.11-1
Severity: normal

Dear Maintainer,

while viewing the content of the Trash there is no way to sort the files and
folders by there deletetion date/time. So I have no way to find the last
deleted files.



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

Kernel: Linux 4.10.15-towo.1-siduction-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages thunar depends on:
ii  desktop-file-utils  0.23-1
ii  exo-utils   0.10.7-1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-10
ii  libcairo2   1.14.8-1
ii  libdbus-1-3 1.10.18-1
ii  libdbus-glib-1-20.108-2
ii  libexo-1-0  0.10.7-1
ii  libgdk-pixbuf2.0-0  2.36.5-2
ii  libglib2.0-02.50.3-2
ii  libgtk2.0-0 2.24.31-2
ii  libgudev-1.0-0  230-3
ii  libice6 2:1.0.9-2
ii  libnotify4  0.7.7-2
ii  libpango-1.0-0  1.40.5-1
ii  libsm6  2:1.2.2-1+b3
ii  libthunarx-2-0  1.6.11-1
ii  libxfce4ui-1-0  4.12.1-2
ii  libxfce4util7   4.12.1-3
ii  libxfconf-0-2   4.12.1-1
ii  shared-mime-info1.8-1
ii  thunar-data 1.6.11-1

Versions of packages thunar recommends:
ii  dbus-x11 [dbus-session-bus]  1.10.18-1
ii  gvfs 1.30.4-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  thunar-volman0.8.1-2
ii  tumbler  0.1.31-2+b3
pn  xdg-user-dirs
ii  xfce4-panel  4.12.1-2

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.3.1-4
ii  thunar-media-tags-plugin  0.2.1-1+b2

-- no debconf information

Bug#863498: Trash: undo for delete files to trash

2017-05-27 Thread Christian Buhtz

Package: thunar
Version: 1.6.11-1
Severity: normal

Dear Maintainer,

when I use the Trash to delete files/folders there is no way (menu or Ctrl+Z)
to get them back.



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

Kernel: Linux 4.10.15-towo.1-siduction-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages thunar depends on:
ii  desktop-file-utils  0.23-1
ii  exo-utils   0.10.7-1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-10
ii  libcairo2   1.14.8-1
ii  libdbus-1-3 1.10.18-1
ii  libdbus-glib-1-20.108-2
ii  libexo-1-0  0.10.7-1
ii  libgdk-pixbuf2.0-0  2.36.5-2
ii  libglib2.0-02.50.3-2
ii  libgtk2.0-0 2.24.31-2
ii  libgudev-1.0-0  230-3
ii  libice6 2:1.0.9-2
ii  libnotify4  0.7.7-2
ii  libpango-1.0-0  1.40.5-1
ii  libsm6  2:1.2.2-1+b3
ii  libthunarx-2-0  1.6.11-1
ii  libxfce4ui-1-0  4.12.1-2
ii  libxfce4util7   4.12.1-3
ii  libxfconf-0-2   4.12.1-1
ii  shared-mime-info1.8-1
ii  thunar-data 1.6.11-1

Versions of packages thunar recommends:
ii  dbus-x11 [dbus-session-bus]  1.10.18-1
ii  gvfs 1.30.4-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  thunar-volman0.8.1-2
ii  tumbler  0.1.31-2+b3
pn  xdg-user-dirs
ii  xfce4-panel  4.12.1-2

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.3.1-4
ii  thunar-media-tags-plugin  0.2.1-1+b2

-- no debconf information

Bug#862258: [Pkg-mlmmj-devel] Bug#862258: Bug#862258: add an user for mlmmj

2017-05-27 Thread Thomas Goirand

On 05/27/2017 01:48 AM, Geert Stappers wrote:
> On Thu, May 25, 2017 at 01:43:01PM +0200, Thomas Goirand wrote:
>> On 05/25/2017 10:59 AM, Geert Stappers wrote:
>>> On Wed, May 24, 2017 at 04:00:37PM +0200, Thomas Goirand wrote:
 just leave the choice to the user and let him do it by hand.
>>>
>>> It is the "add an user _by hand_" that I want to avoid.
>>
>> There's no way to avoid it, since this is a very specific way to use
>> MLMMJ (ie: using a single mlmmj system account isn't the way when doing
>> virtual hosting).
>>
 I believe here, you're maybe too much influenced by bad practice with
 less good list manager, like mailman, maybe?
>>>
>>> Both http://mlmmj.org/docs/readme-exim4/ and 
>>> http://mlmmj.org/docs/readme-postfix/
>>> say to create a mlmmj user.
>>
>> This is *one way* to do things, yes.
> 
> Those who want to use that mlmmj user will benefit from the "postinst 
> adduser".

But those who don't will have a useless user setup *every time* the
package is upgraded.

Cheers,

Thomas Goirand (zigo)

Bug#863481: [Pkg-javascript-devel] Bug#863481: [node-concat-stream] Uninitialized Memory Exposure

2017-05-27 Thread roucaries bastien

I can do it but I do not know that is the best:
- let 1.6 go to unstable
- patch old version

Could you ask release team.

The debdiff between the two version is so small that I have doubt

On Sat, May 27, 2017 at 6:53 PM, Ross Gammon  wrote:
> Hi Bastien,
>
> If you would like me to prepare an upload to unstable for this (& unblock
> request), let me know. I have some time today & tomorrow - but travelling
> with work next week. I have DM upload rights for it.
>
> Only asking in case you are already working on it.
>
> Cheers,
>
> Ross
>
>
> On 05/27/2017 04:51 PM, Bastien ROUCARIÈS wrote:
>
> Package: node-concat-stream
> Version: 1.5.1-1
> Severity: grave
> Tags: patch security fixed-upstream fixed-in-experimental
> X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
> forwarded: https://snyk.io/vuln/npm:concat-stream:20160901
>
> Overview
>
> concat-stream is writable stream that concatenates strings or binary data
> and
> calls a callback with the result. Affected versions of the package are
> vulnerable to Uninitialized Memory Exposure.
>
> A possible memory disclosure vulnerability exists when a value of type
> number
> is provided to the stringConcat() method and results in concatination of
> uninitialized memory to the stream collection.
>
> This is a result of unobstructed use of the Buffer constructor, whose
> insecure
> default constructor increases the odds of memory leakage.
>
>
>
>

Bug#863493: [pkg-php-pear] Bug#863493: FTBFS with PHP 7.0.18+

2017-05-27 Thread David Prévot

Hi James,

Le 27/05/2017 à 09:08, James Clarke a écrit :
> Source: symfony
> Version: 2.8.7+dfsg-1.2

> I noticed that symfony now FTBFS after the upload of php7.0 7.0.18-1,

Thanks!

> I am happy to NMU again with just the changes needed

Please, go ahead, I don’t have much time currently, and haven’t heard of
Daniel for quite some time either. Your help is much appreciated.

Regards



signature.asc
Description: OpenPGP digital signature

Bug#823180: SSO certificates for tracker.debian.org broken

2017-05-27 Thread Russ Allbery

Enrico Zini  writes:
> On Mon, Jan 16, 2017 at 09:26:10PM -0800, Russ Allbery wrote:

>> Is there any way that I or someone can help with the current issue with
>> enrolling on sso.debian.org?  It looks like this was originally
>> reported in May of last year on this bug.

> Sure. Although I'm bad at project managing myself[1], I'm very happy to
> help.

Well, this was also rather embarassing on my part.  I sent that message in
January in a burst of optimism and energy, coming off vacation, and then
promptly ran out of any time and never followed this up.

> Ack. I refactored sso.debian.org when we got rid of DACS, and now there
> are two login pages, one for debian.org and one for alioth.debian.org,
> because sso.debian.org has now been setup with two views of the same
> functionalities each with a different apache authentication.

> That link should probably just be changed to https://sso.debian.org/

I confirm this is now fixed.

>> If one goes directly to sso.debian.org, clicks on Debian account
>> certificates, and logs in, clicks on Get new certificate, and then
>> submits, it just produces "/usr/bin/openssl failed" as an error message
>> at the top of the page.

> That would be with chrome/chromium, I suppose? They disabled the
> certificate generation functionality by default:
> https://wiki.debian.org/DebianSingleSignOn#chromium_.2F_chrome

> I know of no way of doing certificate generation on recent chromes
> without explicitly enabling it as described on the wiki link above, and
> I read somewhere months ago[citation needed] that the chrome devs
> decided it's a feature that they intend to remove altogether. It'd be
> nice if they changed their mind or started suggesting alternatives.

Oh!  Yes, that's indeed the problem, and that makes sense.  I thought the
old error message (about openssl failure) indicated some server-side issue
rather than a client issue.  I see that the error message is now much
nicer (thank you!).

> I started playing with the idea of a command line tool that would take
> care of browsers: https://github.com/spanezz/debsso-client and it looks
> like a promising avenue, in that it's possible to feed client
> certificates to chromium and firefox from the command line:
> https://lists.debian.org/debian-devel/2016/10/msg00131.html

> debsso-client could do SPKAC with sso.debian.org and inject the
> resulting certificate into the browsers key store:

>  1. openssl genrsa -out user.key 2048
> openssl spkac -key user.key -challenge FvIu8NDJZxGmpKmA5pp3asMDZChXD4rc | 
> cut -d= -f2-
>  2. Post it to https://sso.debian.org/debian/certs/enroll_manually or
> https://sso.debian.org/alioth/certs/enroll_manually authenticating
> with HTTP basic auth, together with the validity and comment fields
> that you see on the page
>  3. get the client certificate as the result of the POST
>  4. feed it into the browser key store

I went through the equivalent of that process manually using the manual
certificate generation instructions, and it works great.  This seems like
the right approach to me as well.

I should probably take the five month delay in even responding to this
message as a sign that I have no business trying to dive into new
responsibilities and help out more with this at the moment.  :(  Apologies
for offering help and then going totally silent; my reach exceeded my
grasp.  But thank you *very* much for taking the time to describe the
problem and the proposed approach, and if I manage to pry free any time to
work on SSO stuff again, I will take a look at the code and also look at
the problem area and see if there's something better we can do.

(That said, I suspect that an external script to inject the certificate
into the browser is probably the best approach.  There are various
security worries about letting the browser generate certs directly, and
I'm not sure if the browser authors will be particularly excited about
supporting this functionality.  I think people in the industry have
largely given up on client-side browser certs in favor of U2F, although
that doesn't solve exactly the same problem.)

-- 
Russ Allbery (r...@debian.org)

Bug#863492: pavuk: segmentation fault when opening graphical "Limitations" window

tags 863492 + pending patch
thanks

I've uploaded pavuk 0.9.35-6.1 to DELAYED/5:
  
  pavuk (0.9.35-6.1) unstable; urgency=medium
  
* Non-maintainer upload.
* Fix segmentation fault when opening graphical "Limitations" window due to
  pointer truncation in src/gtkmulticol.[ch]. (Closes: #863492)

The full debdiff is attached.


Regards,

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

 changelog   |8 
 patches/18-fix-pointer-truncation.patch |   25 +
 patches/series  |1 +
 3 files changed, 34 insertions(+)

diff -Nru pavuk-0.9.35/debian/changelog pavuk-0.9.35/debian/changelog
--- pavuk-0.9.35/debian/changelog   2016-12-14 20:03:37.0 +
+++ pavuk-0.9.35/debian/changelog   2017-05-27 20:17:22.0 +0100
@@ -1,3 +1,11 @@
+pavuk (0.9.35-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix segmentation fault when opening graphical "Limitations" window due to
+pointer truncation in src/gtkmulticol.[ch]. (Closes: #863492)
+
+ -- Chris Lamb   Sat, 27 May 2017 20:17:22 +0100
+
 pavuk (0.9.35-6) unstable; urgency=low
 
   * debian/watch: update to v4 to make it work
diff -Nru pavuk-0.9.35/debian/patches/18-fix-pointer-truncation.patch 
pavuk-0.9.35/debian/patches/18-fix-pointer-truncation.patch
--- pavuk-0.9.35/debian/patches/18-fix-pointer-truncation.patch 1970-01-01 
01:00:00.0 +0100
+++ pavuk-0.9.35/debian/patches/18-fix-pointer-truncation.patch 2017-05-27 
20:17:22.0 +0100
@@ -0,0 +1,25 @@
+--- pavuk-0.9.35.orig/src/gtkmulticol.c
 pavuk-0.9.35/src/gtkmulticol.c
+@@ -48,9 +48,9 @@ static void gtk_multicol_size_request(Gt
+ static void gtk_multicol_size_allocate(GtkWidget * widget,
+   GtkAllocation * allocation);
+ 
+-guint gtk_multicol_get_type()
++GtkType gtk_multicol_get_type()
+ {
+-  static guint multicol_type = 0;
++  static GtkType multicol_type = 0;
+ 
+   if(!multicol_type)
+   {
+--- pavuk-0.9.35.orig/src/gtkmulticol.h
 pavuk-0.9.35/src/gtkmulticol.h
+@@ -41,7 +41,7 @@ extern "C"
+ GtkBoxClass parent_class;
+   };
+ 
+-  guint gtk_multicol_get_type(void);
++  GtkType gtk_multicol_get_type(void);
+   GtkWidget *gtk_multicol_new(gint nrows);
+   void gtk_multicol_set_number_of_rows(GtkMultiCol * multicol, gint nrows);
+   void gtk_multicol_set_spacing(GtkMultiCol * multicol,
diff -Nru pavuk-0.9.35/debian/patches/series pavuk-0.9.35/debian/patches/series
--- pavuk-0.9.35/debian/patches/series  2016-12-14 20:03:37.0 +
+++ pavuk-0.9.35/debian/patches/series  2017-05-27 20:17:22.0 +0100
@@ -6,3 +6,4 @@
 15-pavuk-nossl3.patch
 16-reproducible-build.patch
 #17-mozjs185.patch
+18-fix-pointer-truncation.patch

Bug#863488: file: upgrade broke file magic

2017-05-27 Thread Christoph Biedl

tags 863488 moreinfo unreproducible
thanks

Ben Hildred wrote...

> A recent upgrade has rendered file just about usless as it is only able to
> identify text in the most limited sense.

Works for me:

> for example:
> $ file /usr/bin/file
> /etc/magic, 4: Warning: using regular magic file `/usr/share/misc/magic'
> /usr/bin/file: data

/usr/bin/file: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), 
dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, 
BuildID[sha1]=2f833ab1ff58c9e0ae5801481a0dff1da286f30b, stripped

(see the release notes why it's not "executable" any longer)

> or:
> $ file /usr/share/doc/file/*
> /etc/magic, 4: Warning: using regular magic file `/usr/share/misc/magic'
> /usr/share/doc/file/changelog.Debian.gz: data
> /usr/share/doc/file/changelog.gz:data
> /usr/share/doc/file/copyright:   ASCII text
> /usr/share/doc/file/README.Debian:   ASCII text
> /usr/share/doc/file/README.gz:   data

Results in the expected output.

What is in /usr/share/misc/magic, and where did the file(s) come
from?

Christoph


signature.asc
Description: Digital signature

Bug#863279: jbig2dec: CVE-2017-9216: NULL pointer dereference in the jbig2_huffman_get function

2017-05-27 Thread Salvatore Bonaccorso

Control: tags -1 + fixed-upstream

On Wed, May 24, 2017 at 08:40:44PM +0200, Salvatore Bonaccorso wrote:
> Source: jbig2dec
> Version: 0.13-1
> Severity: important
> Tags: upstream security
> Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=697934
> 
> Hi,
> 
> the following vulnerability was published for jbig2dec.
> 
> CVE-2017-9216[0]:
> | libjbig2dec.a in Artifex jbig2dec 0.13, as used in MuPDF and
> | Ghostscript, has a NULL pointer dereference in the jbig2_huffman_get
> | function in jbig2_huffman.c. For example, the jbig2dec utility will
> | crash (segmentation fault) when parsing an invalid file.
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2017-9216
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9216
> [1] https://bugs.ghostscript.com/show_bug.cgi?id=697934

Fixed upstream with

http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=3ebffb1d96ba0cacec23016eccb4047dab365853

Regards,
Salvatore

Bug#863497: debsign: Cannot sign just a dsc

2017-05-27 Thread James Clarke

Package: devscripts
Version: 2.17.5
Severity: normal
Tags: patch

Hi,
Invoking `debsign foo.dsc` gives the error:

> debsign: Can't find or can't read dsc file !

The attached patch fixes it.

Regards,
James
>From a2321a8f177fbd4c85ff18c9809c496a462bab71 Mon Sep 17 00:00:00 2001
From: James Clarke 
Date: Sat, 27 May 2017 20:14:09 +0100
Subject: [PATCH] debsign: Fix signing a dsc directly

---
 scripts/debsign.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/debsign.sh b/scripts/debsign.sh
index 0717bead..924b03eb 100755
--- a/scripts/debsign.sh
+++ b/scripts/debsign.sh
@@ -725,7 +725,7 @@ for valid format" >&2;
 	report_signed
 
 else
-	ensure_local_copy "$remotehost" "$remotehost" "$remotedsc" dsc
+	ensure_local_copy "$remotehost" "$remotedsc" "$dsc" dsc
 	signas="$(guess_signas "$dsc")"
 	maybesign_dsc "$signas" "$remotehost" "$dsc"
 	report_signed
-- 
2.11.0

Bug#863257: gdm3: stretch - login box displayed off-screen

Control: reassign -1 linux-image-4.9.0-3-amd64
Control: severity -1 important
Control: retitle -1 internal display not turned off despite lid closed and 
docked
Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=195455

Am 27.05.2017 um 20:09 schrieb Michael Biebl:
> I've narrowed this down. It seems to be a regression introduced by
> 4.9.25-1, 4.9.18-1 still works fine for me.
> 
> Ben, were there any DRM related changes in 4.9.25 which seem like they
> could be relevant?

I've found this
https://bugzilla.redhat.com/show_bug.cgi?id=1430259


I'm going to reassign this to the kernel for now, as it's not a gdm issue.

Ben, should we revert this commit for now?


commit 8d5dd97f55563634ad830ea47c709bc96606ad65
Author: Lv Zheng 
Date:   Tue Apr 4 19:32:27 2017 +

ACPI / button: Change default behavior to lid_init_state=open

[ Upstream commit 77e9a4aa9de10cc1418bf9a892366988802a8025 ]

More and more platforms need the button.lid_init_state=open quirk. This
patch sets it the default behavior.

If a platform doesn't send lid open event or lid open event is lost due to
the underlying system problems, then we can compare various combinations:
1. systemd/acpid is used to suspend system or not, systemd has a special
   logic forcing open event after resuming;
2. _LID returns a cached value or not.

-- 
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#863496: debian-handbook: add a wireless configuration section

2017-05-27 Thread Matthew D

Package: debian-handbook
Version: 8.20151209~deb8u1
Severity: wishlist

Dear Maintainer,

I apologize if this is out of place or I am missing something; this is my first 
contribution to open source.

I have been browsing through The Debian Administrator's Handbook and noticed 
that there is no section describing how to configure wireless from the command 
line. This was a major struggle when I first used Debian, and I would like to 
write a section (probably in 8.2 of the handbook) illustrating how to do this. 
Any help related to how I should create and submit the patch is welcomed.

Thank You,
Matthew D


-- System Information:
Debian Release: 8.8
Architecture: amd64 (x86_64)

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

-- no debconf information

Bug#863495: Broken on (at least) amd64, looks in wrong path for libporg-log.so

2017-05-27 Thread Andreas Moog

Package: porg
Version: 2:0.10-1
Severity: serious

Hi there,

porg on (at least) amd64 is broken:

$ sudo porg -lp foo-1.0 "touch /usr/bin/foo"
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libporg-log.so' from LD_PRELOAD 
cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libporg-log.so' from LD_PRELOAD 
cannot be preloaded (cannot open shared object file): ignored.
porg: foo-1.0: No files to log

Let me know if you need any more information from me.

There is a Ubuntu report about the same issue in Ubuntu:
https://bugs.launchpad.net/bugs/1664429

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 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 porg depends on:
ii  libc6   2.24-10
ii  libgcc1 1:6.3.0-18
ii  libstdc++6  6.3.0-18

porg recommends no packages.

porg suggests no packages.

-- no debconf information

Bug#863494: unblock: elfutils/0.168-1

2017-05-27 Thread Kurt Roeckx

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Hi,

I've uploaded a new version of elfutils which fixes security
issues:
elfutils (0.168-1) unstable; urgency=medium

  * Fix CVE-2017-7607 (Closes: #859996)
  * Fix CVE-2017-7608 (Closes: #859995)
  * Fix CVE-2017-7609 (Closes: #859994)
  * Fix CVE-2017-7610 (Closes: #859993)
  * Fix CVE-2017-7611 (Closes: #859992)
  * Fix CVE-2017-7612 (Closes: #859991)
  * Fix CVE-2017-7613 (Closes: #859990)

Note that this is not an new upstream version, the version in
testing is currently 0.168-0.2


Kurt

Bug#863493: FTBFS with PHP 7.0.18+

2017-05-27 Thread James Clarke

Source: symfony
Version: 2.8.7+dfsg-1.2
Severity: serious
Tags: patch upstream fixed-upstream

Hi,
I noticed that symfony now FTBFS after the upload of php7.0 7.0.18-1,
with the following error in the test suite:

> 1) Symfony\Component\VarDumper\Tests\CliDumperTest::testThrowingCaster
> Failed asserting that format description matches text.
> --- Expected
> +++ Actual
> @@ @@
>  stream resource {@239
> -%Awrapper_type: "PHP"
> +  timed_out: false
> +  blocked: true
> +  eof: false
> +  wrapper_type: "PHP"
>stream_type: "MEMORY"
> -  mode: "%s+b"
> +  mode: "w+b"
>unread_bytes: 0
>seekable: true
>uri: "php://memory"
> -%Aoptions: []
> -  ⚠: Symfony\Component\VarDumper\Exception\ThrowingCasterException {#%d
> +  options: []
> +  ⚠: Symfony\Component\VarDumper\Exception\ThrowingCasterException {#411
>  #message: "Unexpected Exception thrown from a caster: Foobar"
>  -trace: {
> -  %d. __TwigTemplate_VarDumperFixture_u75a09->doDisplay() ==> new 
> Exception(): {
> +  22. __TwigTemplate_VarDumperFixture_u75a09->doDisplay() ==> new 
> Exception(): {
>  src: {
> -  %sTwig.php:19: """
> +  
> /<>/symfony-2.8.7+dfsg/src/Symfony/Component/VarDumper/Tests/Fixtures/Twig.php:19:
>  """
> 
> @@ @@
>}
> -  %d. Twig_Template->displayWithErrorHandling() ==> 
> __TwigTemplate_VarDumperFixture_u75a09->doDisplay(): {
> +  21. Twig_Template->displayWithErrorHandling() ==> 
> __TwigTemplate_VarDumperFixture_u75a09->doDisplay(): {
>  src: {
> -  %sTemplate.php:%d: """
> +  /usr/share/php/Twig/Template.php:381: """
> 
> @@ @@
>}
> -  %d. Twig_Template->display() ==> 
> Twig_Template->displayWithErrorHandling(): {
> +  20. Twig_Template->display() ==> 
> Twig_Template->displayWithErrorHandling(): {
>  src: {
> -  %sTemplate.php:%d: """
> +  /usr/share/php/Twig/Template.php:355: """
> 
> @@ @@
>}
> -  %d. Twig_Template->render() ==> Twig_Template->display(): {
> +  19. Twig_Template->render() ==> Twig_Template->display(): {
>  src: {
> -  %sTemplate.php:%d: """
> +  /usr/share/php/Twig/Template.php:366: """
> 
> @@ @@
>}
> -  %d. %slosure%s() ==> Twig_Template->render(): {
> +  18. Symfony\Component\VarDumper\Tests\CliDumperTest->{closure}() ==> 
> Twig_Template->render(): {
>  src: {
> -  %sCliDumperTest.php:189: """
> -}\n
> -};'),\n
> -));\n
> +  
> /<>/symfony-2.8.7+dfsg/src/Symfony/Component/VarDumper/Tests/CliDumperTest.php:183:
>  """
> +$cloner->addCasters(array(\n
> +':stream' => eval('return function () use ($twig) {\n
> +try {\n
>  """
>  }
>}
>  }
>}
>  }
> 
> /<>/symfony-2.8.7+dfsg/src/Symfony/Component/VarDumper/Tests/CliDumperTest.php:277

The difference is that the line number for CliDumperTest.php right at
the end is no longer correct, and has some different code after it.
Upstream fixed this already[1,2], and these changes are also in #863441,
but there are other changes not required for PHP 7.0, hence the separate
bug. I am happy to NMU again with just the changes needed, and will do
so if I do not hear anything soon, as the release is approaching and
this will otherwise become a stretch-will-remove bug.

Regards,
James

[1] 
https://github.com/symfony/symfony/commit/3672c01e3c7182888a42b74e2864a20e21cfe7f5
[2] 
https://github.com/symfony/symfony/commit/6ef78ec55317ac473fa045706244ef1f97d4b2de
(only the change to CliDumperTest.php)

Bug#863492: pavuk: segmentation fault when opening graphical "Limitations" window

Package: pavuk
Version: 0.9.35-6
Severity: serious

Hi,

Pavuk segmentation faults when opening the "Limitations" config window:

 $ pavuk -x https://debian.org/

 Select "Config" → "Limitations"


Regards,

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

Bug#863491: Spams the journal with debug messages

Package: tilix
Version: 1.5.6-1
Severity: normal

Hi,

I've been running tilix for a couple of days now and I noticed that
tilix is very chatty. My journal get's "spammed" with what seems to me
are debug messages: Here is an excerpt:

Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.672:session.d:addNewTerminal:394 Splitting Terminal 1
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.672:terminal.d:this:3641 Local Hostname: pluto
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.692:terminal.d:setupDragAndDrop:2450 Setting up drag and 
drop
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.692:terminal.d:setupDragAndDrop:2481 Drag and drop completed
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.692:terminal.d:this:2975 Apply preferences
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.694:terminal.d:updateTitleBar:1139 Showing titlebar
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.694:terminal.d:this:2977 Profile Event Handler
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.694:terminal.d:this:2983 Finished creation
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.694:terminal.d:getDisplayText:3255 Terminal not initialized 
yet or VTE not configured, no path available
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.695:terminal.d:getDisplayText:3255 Terminal not initialized 
yet or VTE not configured, no path available
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.695:terminal.d:updateTitleBar:1139 Showing titlebar
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.695:terminal.d:updateTitleBar:1139 Showing titlebar
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.695:session.d:addNewTerminal:396 Inserting terminal
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.697:terminal.d:terminalWidgetFocusOut:1727 Terminal lost 
focuscd6009a5-efb6-407d-b8ea-005ab36c2334
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.712:terminal.d:focusTerminal:3084 Terminal grabbing focus
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.712:terminal.d:terminalWidgetFocusIn:1709 Terminal gained 
focus 34e341a6-932f-40d0-b639-1a14131fb72c
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.712:terminal.d:getDisplayText:3255 Terminal not initialized 
yet or VTE not configured, no path available
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.713:session.d:addNewTerminal:398 Initializing terminal with 
/home/michael
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.713:terminal.d:initTerminal:3000 Initializing Terminal with 
directory /home/michael
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.713:terminal.d:spawnTerminalProcess:2156 workingDir 
parameter=/home/michael
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.713:terminal.d:spawnTerminalProcess:2174 Spawn setting 
workingDir to /home/michael
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.713:terminal.d:spawnTerminalProcess:2201 Argument: /bin/bash
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.715:terminal.d:initTerminal:3013 Terminal initialized
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.715:terminal.d:getDisplayText:3255 Terminal not initialized 
yet or VTE not configured, no path available
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.719:terminal.d:getDisplayText:3255 Terminal not initialized 
yet or VTE not configured, no path available
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.719:terminal.d:getDisplayText:3255 Terminal not initialized 
yet or VTE not configured, no path available
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.735:terminal.d:updateState:3667 Terminal in initialized 
state
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.767:terminal.d:__dgliteral2:840 Window title changed
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.767:terminal.d:getHostnameAndDirectory:2132 Current 
directory: file://pluto/home/michael
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.767:terminal.d:updateState:3698 Current directory changed, 
hostname 'pluto', directory '/home/michael'
Mai 27 20:52:35 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:52:35.767:terminal.d:checkAutomaticProfileSwitch:1091 Switching 
back to default profile to
Mai 27 20:54:52 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:54:52.008:terminal.d:terminalWidgetFocusOut:1727 Terminal lost 
focus34e341a6-932f-40d0-b639-1a14131fb72c
Mai 27 20:54:52 pluto com.gexperts.Tilix[1793]: 
2017-05-27T20:54:52.009:terminal.d:terminalWidgetFocusIn:1709 Terminal gained 
focus

Bug#223965: postconf with postfix-tls

2017-05-27 Thread Scott Kitterman

postfix-tls is not relevant for any supported Debian release, so closing 
related bugs.

Scott K

Bug#303523: postfix-tls 2.1.5-5 not using correct SASL settongs

2017-05-27 Thread Scott Kitterman

postfix-tls is not relevant for any supported Debian release, so closing 
related bugs.

Scott K

Bug#863146: [libreoffice-kde] Upstream bug report

2017-05-27 Thread Rene Engelhard

On Sat, May 27, 2017 at 08:27:36PM +0200, Rene Engelhard wrote:
> Anyways: There is? The last comment said it's back?

What I forgot to write here:

We don't have 5.3.0 anymore of course but 5.3.3 is in experimental, maybe
it would make sense to check whether it is really fixed there?

Regards,

Rene

Bug#855577: numba: FTBFS: several tests fail

For the latest upload (0.33.0 in experimental), the tests have been failsafed
again so that there are even packages building to try out.

Bug reports on the individual test failures and other remaining things to fix
are coming up.

Failsafe is going to be removed again when the package hits unstable.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#863459: unblock (pre-approval): tiff/4.0.8

2017-05-27 Thread GCS

Control: tags -1 -moreinfo

Hi Ivo,

On Sat, May 27, 2017 at 11:27 AM, Ivo De Decker  wrote:
> On Sat, May 27, 2017 at 09:48:21AM +0200, László Böszörményi (GCS) wrote:
>> Current version of tiff in the archive is 4.0.7 and the package
>> already have 28 security patches that got attention (CVE id). Upstream
>> released 4.0.8 which contains only security related changes[1]
>> including memory leaks, division by zero, undefined behaviour, integer
>> overflows and excessive memory allocation fixes.
>> There are no major or software configuration changes[2].
>
> Please go ahead and remove the moreinfo tag from this bug once the upload is
> in unstable and the builds are done on all the relevant architectures.
 It is built, uploaded and installed on _all_ architectures, Ubuntu
adopted it as-is as well.

Thanks,
Laszlo/GCS

Bug#863146: [libreoffice-kde] Upstream bug report

2017-05-27 Thread Rene Engelhard

tag 863146 + upstream
forwarded 863146 https://bugs.documentfoundation.org/show_bug.cgi?id=97721
tag 863146 + moreinfo
thanks

Hi,

On Sat, May 27, 2017 at 08:18:50PM +0200, B.M. wrote:
> There is an upstream bug report related to the same problem containing a fix:
> https://bugs.documentfoundation.org/show_bug.cgi?id=97721

Sigh. I repeatedly asked jmux whether/what patches should be backported
as -kde is a bit a off-sider in LO and here (I use GNOME). And it's KDE4
only which is supposed to go away in buster ttbomk...

Anyways: There is? The last comment said it's back?
> 
> Maybe the patch could be backported to stretch before the release?

No. At least not whether it really helps and besides you seem to have
missed the last debian-devel-announce post. A upload just for this.. mmmh..

Regards,

Rene

Bug#863146: [libreoffice-kde] Upstream bug report

2017-05-27 Thread B.M.

There is an upstream bug report related to the same problem containing a fix:
https://bugs.documentfoundation.org/show_bug.cgi?id=97721

Maybe the patch could be backported to stretch before the release?

Thank you.

Bug#863199: happens every time on "slim" images

2017-05-27 Thread Hans-Christoph Steiner


This is happens every time I try to install Java on the official Debian
stretch-slim or testing-slim docker image.  This is a blocker for moving
the F-Droid infrastructure to stretch.

Apparently, it works with the "testing" image, i.e. not "slim":
https://gitlab.com/eighthave/ci-images-base/builds/17325240

Seems like that means that the dependencies are not correctly specified
then.

Bug#863477: redis-server: Systemd unit namespace setup can fail on ancient/strange kernels

Hi Marc,

> I upgraded a hosted Virtuozzo container from Jessie to Stretch. After the
> upgrade, redis-server fails to start:

[..]

> 3. An ancient kernel and/or Virtuozzo is in use. I could not reproduce
> it on a system running the default Debian kernel 4.9.

Can you elaborate more on exactly what this kernel is? eg. what version,
what makes Virtuozzo special here, etc. etc.  Trying to work out the
scope of the problem.

> Nevertheless, the fix to redis-server.service seems straightforward,
> even if it is just a workaround for a deeper issue.

Can you comment on whether switching it to /run will work on all systems?
I wouldn't want to push this into Stretch without being very confident.


Regards,

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

Bug#863420: timemachine: segfaults on startup

James Cowgill wrote:

> I tested your fixes, unfortunately timemachine still segfaults on
> startup. This time it occurs in gtk_meterscale_new and it looks like the
> same pointer truncation problem there.

Huh, how did I miss that. Anyway, I've re-uploaded timemachine 0.3.3-2.1 to
DELAYED/5:
  
  timemachine (0.3.3-2.1) unstable; urgency=medium
  
* Non-maintainer upload.
* Fix two segmentation faults in src/gtkmeter.c and gtkmeterscale.c caused
  by passing a truncated pointers using guint instead of a GtkType.
  (Closes: #863420)

The full debdiff is attached.


Regards,

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

 changelog |9 +
 patches/0002-truncated-pointers.patch |   52 ++
 patches/series|1 
 3 files changed, 62 insertions(+)

diff -Nru timemachine-0.3.3/debian/changelog timemachine-0.3.3/debian/changelog
--- timemachine-0.3.3/debian/changelog  2013-10-06 14:13:24.0 +0100
+++ timemachine-0.3.3/debian/changelog  2017-05-27 09:41:19.0 +0100
@@ -1,3 +1,12 @@
+timemachine (0.3.3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix two segmentation faults in src/gtkmeter.c and gtkmeterscale.c caused
+by passing a truncated pointers using guint instead of a GtkType.
+(Closes: #863420)
+
+ -- Chris Lamb   Sat, 27 May 2017 09:41:19 +0100
+
 timemachine (0.3.3-2) unstable; urgency=low
 
   * Team upload.
diff -Nru timemachine-0.3.3/debian/patches/0002-truncated-pointers.patch 
timemachine-0.3.3/debian/patches/0002-truncated-pointers.patch
--- timemachine-0.3.3/debian/patches/0002-truncated-pointers.patch  
1970-01-01 01:00:00.0 +0100
+++ timemachine-0.3.3/debian/patches/0002-truncated-pointers.patch  
2017-05-27 09:41:19.0 +0100
@@ -0,0 +1,52 @@
+--- timemachine-0.3.3.orig/src/gtkmeter.c
 timemachine-0.3.3/src/gtkmeter.c
+@@ -48,10 +48,10 @@ static float iec_scale(float db);
+ 
+ static GtkWidgetClass *parent_class = NULL;
+ 
+-guint
++GtkType
+ gtk_meter_get_type ()
+ {
+-  static guint meter_type = 0;
++  static GtkType meter_type = 0;
+ 
+   if (!meter_type)
+ {
+--- timemachine-0.3.3.orig/src/gtkmeter.h
 timemachine-0.3.3/src/gtkmeter.h
+@@ -87,7 +87,7 @@ struct _GtkMeterClass
+ GtkWidget* gtk_meter_new(GtkAdjustment *adjustment,
+gint direction);
+ 
+-guint  gtk_meter_get_type   (void);
++GtkTypegtk_meter_get_type   (void);
+ GtkAdjustment* gtk_meter_get_adjustment (GtkMeter *meter);
+ 
+ void   gtk_meter_set_adjustment (GtkMeter *meter,
+--- timemachine-0.3.3.orig/src/gtkmeterscale.c
 timemachine-0.3.3/src/gtkmeterscale.c
+@@ -45,10 +45,10 @@ static void meterscale_draw_notch(GtkMet
+ 
+ static GtkWidgetClass *parent_class = NULL;
+ 
+-guint
++GtkType
+ gtk_meterscale_get_type ()
+ {
+-  static guint meterscale_type = 0;
++  static GtkType meterscale_type = 0;
+ 
+   if (!meterscale_type)
+ {
+--- timemachine-0.3.3.orig/src/gtkmeterscale.h
 timemachine-0.3.3/src/gtkmeterscale.h
+@@ -67,7 +67,7 @@ GtkWidget* gtk_meterscale_new
+gfloat min,
+gfloat max);
+ 
+-guint  gtk_meterscale_get_type  (void);
++GtkTypegtk_meterscale_get_type  (void);
+ 
+ #ifdef __cplusplus
+ }
diff -Nru timemachine-0.3.3/debian/patches/series 
timemachine-0.3.3/debian/patches/series
--- timemachine-0.3.3/debian/patches/series 2013-10-06 14:09:12.0 
+0100
+++ timemachine-0.3.3/debian/patches/series 2017-05-27 09:41:19.0 
+0100
@@ -1 +1,2 @@
 0001-ldflags.patch
+0002-truncated-pointers.patch

Bug#863490: unblock: uanytun/0.3.6-2

2017-05-27 Thread Darshaka Pathirana

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package uanytun

The /etc/init.d/uanytun script did not source /lib/lsb/init-functions. The
systemd package provides /lib/lsb/init-functions.d/40-systemd to redirect
/etc/init.d/$script calls to systemctl.

When a init script sources the /lib/lsb/init-functions utility
we have to declare a dependency on lsb-base (>= 3.0-6).
See: 
https://lintian.debian.org/tags/init.d-script-needs-depends-on-lsb-base.html

This patch includes an upstream commit which was commited after the release of 
v0.3.6
Source: 
https://git.spreadspace.org/anytun/uanytun.git/commit/?id=e84f028444822b2a185395a640c5e12da4db8454

And below the source debdiff. Thank you very much!

Regards,
 - Darsha

% debdiff uanytun_0.3.6-1.dsc uanytun_0.3.6-2.dsc
diff -Nru uanytun-0.3.6/debian/changelog uanytun-0.3.6/debian/changelog
--- uanytun-0.3.6/debian/changelog  2017-01-26 08:47:07.0 +0100
+++ uanytun-0.3.6/debian/changelog  2017-05-08 01:11:49.0 +0200
@@ -1,3 +1,9 @@
+uanytun (0.3.6-2) unstable; urgency=medium
+
+  * [45680e6] Fix lintian-warning: init.d-script-does-not-source-init-functions
+
+ -- Darshaka Pathirana   Mon, 08 May 2017 01:11:49 +0200
+
 uanytun (0.3.6-1) unstable; urgency=medium
 
   * [43e4474] Bump debian compat version to 9
diff -Nru uanytun-0.3.6/debian/control uanytun-0.3.6/debian/control
--- uanytun-0.3.6/debian/control2017-01-26 08:47:07.0 +0100
+++ uanytun-0.3.6/debian/control2017-05-08 01:11:49.0 +0200
@@ -13,6 +13,7 @@
 Package: uanytun
 Architecture: any
 Depends: adduser,
+ lsb-base (>= 3.0-6),
  ${misc:Depends},
  ${shlibs:Depends}
 Description: tiny implementation of the secure anycast tunneling protocol
diff -Nru uanytun-0.3.6/debian/patches/01_source-init-functions.diff 
uanytun-0.3.6/debian/patches/01_source-init-functions.diff
--- uanytun-0.3.6/debian/patches/01_source-init-functions.diff  1970-01-01 
01:00:00.0 +0100
+++ uanytun-0.3.6/debian/patches/01_source-init-functions.diff  2017-05-08 
01:11:49.0 +0200
@@ -0,0 +1,22 @@
+From e84f028444822b2a185395a640c5e12da4db8454 Mon Sep 17 00:00:00 2001
+From: Christian Pointner 
+Date: Mon, 16 Jan 2017 05:53:34 +0100
+Subject: source init-functions at initscript
+
+
+diff --git a/etc/init.d/uanytun b/etc/init.d/uanytun
+index 9071e5a..b8a8573 100755
+--- a/etc/init.d/uanytun
 b/etc/init.d/uanytun
+@@ -22,6 +22,8 @@ if [ -f /etc/default/uanytun ] ; then
+   . /etc/default/uanytun
+ fi
+ 
++. /lib/lsb/init-functions
++
+ start_vpn () {
+   STATUS="OK"
+   if [ -f $CONFIG_DIR/$VPNNAME/config ] ; then
+-- 
+cgit v0.10.2
+
diff -Nru uanytun-0.3.6/debian/patches/series 
uanytun-0.3.6/debian/patches/series
--- uanytun-0.3.6/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ uanytun-0.3.6/debian/patches/series 2017-05-08 01:11:49.0 +0200
@@ -0,0 +1 @@
+01_source-init-functions.diff


unblock uanytun/0.3.6-2

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

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

Bug#863257: gdm3: stretch - login box displayed off-screen