Bug#849359: Flent missing package dependency

[Richard Allen]

Package: flent
Version: 0.15.0-3

I believe there is a missing dependency for flent. I also installed
python-setuptools, but that did not fix it.

Error:

rsaxvc@rsaxvc:~$ flent
Traceback (most recent call last):
  File "/usr/bin/flent", line 6, in 
from pkg_resources import load_entry_point
ImportError: No module named 'pkg_resources'
rsaxvc@rsaxvc:~$

Incorrect behaviour: program fails due to missing dependency

Kernel: Linux rsaxvc 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02)
x86_64 GNU/Linux

Pythons:
rsaxvc@rsaxvc:~$ python --version
Python 2.7.13rc1
rsaxvc@rsaxvc:~$ python3 --version
Python 3.5.2+

Libc: Version: 2.24-8

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/24 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 flent depends on:
pn  python3:any  

Versions of packages flent recommends:
ii  iputils-ping [ping]  3:20161105-1
ii  python3-matplotlib   1.5.3-1
ii  python3-pyqt44.11.4+dfsg-2

Versions of packages flent suggests:
pn  netperf  

-- no debconf information
rsaxvc@rsaxvc:~$

Bug#849358: reportbug: crash with character set is us-ascii

[Boyuan Yang]

Package: reportbug
Version: 7.1.1
Severity: important

As reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848655#31,
I think we need a separate bug number.

Detailed output: (same for using LC_ALL=C LANG=C reportbug --ui=text)

% LC_ALL=C LANG=POSIX reportbug --ui=text
Please enter the name of the package in which you have found a problem, or 
type 'other' to
report a more general problem. If you don't know what package the bug is in, 
please contact
debian-u...@lists.debian.org for assistance.
> reportbug
*** Welcome to reportbug.  Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the 
submitter).
Detected character set: us-ascii
Please change your locale if this is incorrect.

Using 'Boyuan Yang <073p...@gmail.com>' as your from address.
Getting status for reportbug...
Checking for newer versions at madison, incoming.debian.org and 
http://ftp-master.debian.org/new.html
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on reportbug (source)...
197 bug reports found:

Bugs with severity grave
1) #846657  ImportError: No module named 'requests'  [RESOLVED]
Bugs with severity important
2) #532150  reportbug: [regression] no longer supports custom mua commands
3) #564112  Checking status of source packages with many binaries can be 
slow
4) #709862  reportbug: GTK interface crashes on continue from package 
selection
5) #711404  reportbug's GTK interface crashes if spelling dictionaries for 
the current loca
6) #717563  reportbug: web access thru proxy not available
7) #840003  reportbug: wrong reporting about bug
8) #846639  reportbug: [sched_delayed] sched: RT throttling activated  
[RESOLVED]
9) #848208  GUI segfaults when trying to collect system information
   10) #848655  reportbug crashes with error "TypeError: * wants int"
   11) #848692  reportbug fails with punctuation in name
   12) #848729  fails with UnicodeDecodeError: 'utf-8' codec can't decode byte 
0xa3 in position
   13) #849124  Reportbug 7.1.1 doesnt start (ValueError: Namespace Vte not 
available + another
   14) #849243  reportbug: TypeError: * wants int
(2-14/197) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? s
Maintainer for reportbug is 'Reportbug Maintainers '.
Looking up dependencies of reportbug...
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2233, in 
main()
  File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 1775, in user_interface
utils.get_dependency_info(package, recommends, "recommends") +
  File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 662, in 
get_dependency_info
for info in get_package_info(dependencies):
  File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 597, in 
get_package_info
for p in packinfo:
  File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 474, in 
__next__
line = self.fp.readline()
  File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 4428: 
ordinal not in range(128)

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

Bug#848029: chromium: sound broken after update

[Nicolai Clemmensen]

Hi all!

Sort of good news. I just upgraded after coming back to my desktop and was then 
having the exact same issue.
I tried to track down the offending code, but the diff was enormous, so I 
couldn't really find anything.
I did however, manage to find a temporary solution to the issue, which might 
point us in the right direction:
Launch with: chromium --audio-buffer-size=8192 (I just tried a random number, a 
lower value might be fine).

When doing this here, the audio is fine again.
So yes, it's basically the same age-old issue with PulseAudio and Chromium. 
Something must have changed that triggered this though, but without knowing the 
code, it's pretty much impossible for me to say what.

Just to clarify, this is definitely not the same bug as Christopher Mark 
describes, as Ubuntu.
Videos works fine for me. Only audio is affected.
YouTube's HTML5 test shows that everything is okay here.

chromium: 55.0.2883.75-1~deb8u1
pulseaudio: 5.0-13
also-base: 1.0.27+1

Bug#848733: xapian-bindings: FTBFS: ../../../../java/org/xapian/TradWeight.java:15: error: cannot access XapianJNI

[Olly Betts]

Control: tags -1 +pending

On Sat, Dec 24, 2016 at 11:04:32AM +0100, Lucas Nussbaum wrote:
> Note that since dpkg 1.18.11, dpkg-buildpackage defaults to setting -Jauto,
> which means automatically passing parallel=64 (on that machine),
> which in turns sets MAKEFLAGS to -j64 in debian/rules,
> which causes the Makefile for the java bindings to be evaluated in
> parallel, which probably triggers a dependency problem.

Aha - I bet that'll be it then.  Thanks for pointing that out.

It looks to my like javac writes .class files out in place, and also reads
existing .class files.  So if run in parallel it can read partial .class
files and fail because they don't contain the classes it expects.

> Note that I just realized that I sometimes get another error:
> 
> ../../../../java/org/xapian/TradWeight.java:11: error: cannot access Weight
> public class TradWeight extends Weight {
> ^
>   bad class file: ./org/xapian/Weight.class
> illegal start of class file
> Please remove or make sure it appears in the correct subdirectory of the 
> classpath.

...or it finds a seemingly corrupt file.

I'll add .NOTPARALLEL for that subdirectory.

Cheers,
Olly

Bug#849150: sagemath: FTBFS on arm64 and ppc64el: cannot allocate memory building docs

[Aaron M. Ucko]

Ximin Luo  writes:

> The error occurs right when the docbuild starts, before it actually
> attempts to build anything, so my guess is that it would also occur
> when starting the normal Sage CLI. So I don't think we should skip the
> docbuild and release the build products as-is.

Thanks for clarifying.  You might want to consider conditionalizing the
docbuild anyway to save build time and disk space, since crashing at
startup would presumably also break the test suite.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#849357: kernel-package: make-kpkg kernel_headers fails for linux 4.10-rc1; missing REPORTING-BUGS

[Joe Public]

Package: kernel-package
Version: 13.018
Severity: normal

Dear Maintainer,

Linux kernel sources for kernel 4.10-rc1 do not include the file
REPORTING-BUGS, however make-kpkg kernel_headers seems to depend on the
presence of this file.  The recipe fails for kernel_headers due to
absence of this file.

Creating an empty REPORTING-BUGS file in the kernel source directory
resulted in a successful build.

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

Kernel: Linux 4.9.0 (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 kernel-package depends on:
ii  bc   1.06.95-9+b2
ii  binutils 2.27.51.20161201-1
ii  build-essential  12.2
ii  bzip21.0.6-8
ii  dpkg-dev 1.18.15
ii  file 1:5.29-2
ii  gettext  0.19.8.1-1
ii  kmod 23-1
ii  po-debconf   1.0.20
ii  xmlto0.0.28-0.1
ii  xz-utils [lzma]  5.2.2-1.2

Versions of packages kernel-package recommends:
ii  cpio   2.11+dfsg-6
ii  docbook-utils  0.6.14-3.3
ii  kernel-common  13.018
pn  uboot-mkimage  

Versions of packages kernel-package suggests:
ii  libncurses5-dev [libncurses-dev]  6.0+20161126-1
pn  linux-source  

-- no debconf information

Bug#849351: exiftool: manual page does not document -All option

[Phil Harvey]

Hi Mattia,

This is explained in the "-TAG" section of the ExifTool application 
documentation:

A special tag name of "All" may be used to indicate all meta
information.  This is particularly useful when a group name is
specified to extract all information in a group (but beware that
unless the -a option is also used, some tags in the group may be
suppressed by same-named tags in other groups).  The wildcard
characters "?" and "*" may be used in a tag name to match any
single character and zero or more characters respectively.  These
may not be used in a group name, with the exception that a group
name of "*" (or "All") may be used to extract all instances of a
tag (as if -a was used).  Note that arguments containing wildcards
must be quoted on the command line of most systems to prevent
shell globbing.

- Phil

> On Dec 25, 2016, at 7:29 PM, Mattia Rizzolo  wrote:
> 
> Control: reassign -1 libimage-exiftool-perl
> 
> On Mon, Dec 26, 2016 at 01:28:56AM +0200, Jari Aalto wrote:
>> Package: exiftool
> 
> Assuming you mean /usr/bin/exiftool, that's pkg libimage-exiftool-perl.
> 
>> Severity: minor
>> 
>> The manual page refers to -All option but it is not listed in
>> any of the options sections.
>> 
>> Please document -All in a standard way as the other options.
>> 
>> Jari
> 
> -- 
> 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  `-

Bug#812137: FTBFS with GCC 6: statement is indented as if

[Legimet]

This patch fixes the issue.Index: mailavenger-0.8.4/libasync/maketables.c
===
--- mailavenger-0.8.4.orig/libasync/maketables.c
+++ mailavenger-0.8.4/libasync/maketables.c
@@ -132,7 +132,9 @@ for (i = 0; i < 256; i++)
   meta-character, which in this sense is any character that terminates a run
   of data characters. */
 
-  if (strchr("*+?{^.$|()[", i) != 0) x += ctype_meta; *p++ = x; }
+  if (strchr("*+?{^.$|()[", i) != 0) x += ctype_meta;
+  *p++ = x;
+  }
 
 return yield;
 }

Bug#849356: Debian 5.4.1-4 LXDE

[Benjamin A]

Package: libfm-extra4
 Heads up,

libfm-extra.so.4 on apt-get upgrade and dist-upgrade around the 23rd of 
December returned seg faults in dmesg, conflicts consist of LXDE menu-cache


 Thanks,
Benjamin

CONFIDENTIALITY NOTICE: This e-mail is for the sole use of the intended 
recipient and may contain information that is confidential and privileged under 
state and federal privacy laws. If you received this e-mail in error, be aware 
that any unauthorized use, disclosure, copying, or distribution is strictly 
prohibited. Please contact the sender immediately and delete and/or destroy all 
copies of this message.

Bug#849352: gimp: Saving overtop existing BZ2 compressesd XCF files does not truncate them

[Brendon Higgins]

On Monday, December 26, 2016 1:03:49 AM EST Ari Pollak wrote:
> Is the undo history saved too, which should contain the original layers?

I considered that, too, but the undo history is blank (except for the single 
"Base Image" item) when I load the file. Also, that wouldn't explain bunzip2 
complaining about trialing garbage, nor the fact that the uncompressed .xcf 
file bunzip2 produces (which, for the record, can itself be correctly opened in 
gimp) is significantly smaller than the .xcf.bz2 file that gimp had saved.

Peace,
Brendon

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

[Legimet]

These two patches fix the errors. Also, python-pytest and python3-pytest must 
be added as build dependencies.>From de7273e04b3c8e4ca3f8ba32298a5d3d763b3ab3 Mon Sep 17 00:00:00 2001
From: Sid Shanker 
Date: Sun, 17 May 2015 23:11:02 -0700
Subject: [PATCH] Fixed utf-8 decoding error in build.

---
 test/run.py | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/test/run.py b/test/run.py
index a48e1fb..d730914 100755
--- a/test/run.py
+++ b/test/run.py
@@ -290,9 +290,12 @@ def collect_dir_tests(base_dir, test_files, check_thirdparty=False):
 skip = 'Thirdparty-Library %s not found.' % lib
 
 path = os.path.join(base_dir, f_name)
-source = open(path).read()
-if not is_py3:
-source = unicode(source, 'UTF-8')
+
+if is_py3:
+source = open(path, encoding='utf-8').read()
+else:
+source = unicode(open(path).read(), 'UTF-8')
+
 for case in collect_file_tests(StringIO(source),
lines_to_execute):
 case.path = path
Description: 
 TODO: Put a short summary on the line above and replace this paragraph
 with a longer explanation of this change. Complete the meta-information
 with other relevant fields (see below for details). To make it easier, the
 information below has been extracted from the changelog. Adjust it or drop
 it.
 .
 python-jedi (0.9.0-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/watch: use pypi.debian.net redirector
Author: Piotr Ożarowski 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 2016-11-16

--- python-jedi-0.9.0.orig/test/test_integration_import.py
+++ python-jedi-0.9.0/test/test_integration_import.py
@@ -18,22 +18,22 @@ def test_goto_definition_on_import():
 def test_complete_on_empty_import():
 assert Script("from datetime import").completions()[0].name == 'import'
 # should just list the files in the directory
-assert 10 < len(Script("from .", path='').completions()) < 30
+assert 10 < len(Script("from .", path='whatever.py').completions()) < 30
 
 # Global import
-assert len(Script("from . import", 1, 5, '').completions()) > 30
+assert len(Script("from . import", 1, 5, 'whatever.py').completions()) > 30
 # relative import
-assert 10 < len(Script("from . import", 1, 6, '').completions()) < 30
+assert 10 < len(Script("from . import", 1, 6, 'whatever.py').completions()) < 30
 
 # Global import
-assert len(Script("from . import classes", 1, 5, '').completions()) > 30
+assert len(Script("from . import classes", 1, 5, 'whatever.py').completions()) > 30
 # relative import
-assert 10 < len(Script("from . import classes", 1, 6, '').completions()) < 30
+assert 10 < len(Script("from . import classes", 1, 6, 'whatever.py').completions()) < 30
 
 wanted = set(['ImportError', 'import', 'ImportWarning'])
 assert set([c.name for c in Script("import").completions()]) == wanted
 if not is_py26:  # python 2.6 doesn't always come with a library `import*`.
-assert len(Script("import import", path='').completions()) > 0
+assert len(Script("import import", path='whatever.py').completions()) > 0
 
 # 111
 assert Script("from datetime import").completions()[0].name == 'import'

Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed

[Vincent Lefevre]

Control: retitle -1 fvwm: with FvwmIconMan, GetWindowSizeHints warnings when 
windows and opened and closed

On 2016-12-26 02:37:46 +0100, Vincent Lefevre wrote:
> I get the following warnings in my .xsession-errors file (where FVWM's
> standard error is redirected):
> 
> [fvwm][GetWindowSizeHints]: <> reason: 2: The hints have been 
> ignored because the window's current size would have become invalid.  The new 
> hints will become active when the window generates the next ConfigureRequest.
> 
> when a window is opened.
> 
> [fvwm][GetWindowSizeHints]: <> reason: 4: The hints have been 
> ignored because the window's current size would have become invalid.  The new 
> hints will become active when the window generates the next ConfigureRequest.
> 
> when a window is closed.
[...]

This only occurs when I use the FvwmIconMan module (which I start
from RestartFunction, itself invoked from InitFunction).

If I remove my specific FvwmIconMan configuration, the problem still
occurs.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#752094: pptpd: Restarting daemon breaks existing connections

[James Cameron]

On Sat, Dec 24, 2016 at 11:17:18PM +0100, Christoph Biedl wrote:
> Unfortunately this has an unpleaseant side effect: Since the new
> pptpd instance has no knowlegde of the old one's children, it will
> happily allocate connection slots (by IP address) that are already
> in use. So the second client will not see any traffic.

Yes, but only when IP address allocation is controlled by pptpd.

Other IP address allocation methods are radius, chap-secrets (pppd),
and remote (ipcp-accept-remote).  For this pptpd takes --delegate
option.

> The only way to solve this AFAICS was the old instance persists all
> the childrens' information so the new one will not allocate them
> while they are running. There might be some race conditions to
> consider as well. James (upstream) is reading this, if you can solve
> this by Jan 20th I'll be happy to include it for stretch. Afterwards
> it might be too late.

I've no plans to fix this by that date, but I'm interested in patches
to do so.

My preference is a /var/run/pptpd/ip directory containing a file for
each active connection, name equal to IP address, content is PID.

pptpmanager.c slot_* functions would maintain these files as a mirror
of struct slot *slots.

Here's a quick pseudo-code plan;

void slot_set_pid(int i, pid_t pid)
{
  struct slot *slot = [i];
  // if pid is zero, {
  //   delete file,
  // } else {
  //   create and write pid to file
  // }
  slot->pid = pid; 
}

int slot_find_by_pid(pid_t pid)
{
  int i;
  for(i=0; ipid == pid)
  // if file exists, {
  //   read pid from file,
  //   if pid exists (kill with sig zero), {
  // continue (skip slot),
  //   } else {
  // unlink file,
  // }
  return i;
  }
  return -1;
}

-- 
James Cameron
http://quozl.netrek.org/

Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed

[Vincent Lefevre]

Package: fvwm
Version: 1:2.6.7-2
Severity: normal

I get the following warnings in my .xsession-errors file (where FVWM's
standard error is redirected):

[fvwm][GetWindowSizeHints]: <> reason: 2: The hints have been ignored 
because the window's current size would have become invalid.  The new hints 
will become active when the window generates the next ConfigureRequest.

when a window is opened.

[fvwm][GetWindowSizeHints]: <> reason: 4: The hints have been ignored 
because the window's current size would have become invalid.  The new hints 
will become active when the window generates the next ConfigureRequest.

when a window is closed.

I've tried with windows from the following applications: xterm, Emacs,
xev. This seems to be always reproducible.

This also occurs when I move to a different page with FvwmPager, with
lots of warnings (I assume one for each window of the old and new
pages).

After 23 hours, the size of my .xsession-errors file is 678 KB.
I don't think that the space taken is much a problem, but the major
consequence is that these warnings can easily hide more interesting
warning/error messages (from FVWM or applications started by it).

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 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 fvwm depends on:
ii  libc6   2.24-8
ii  libcairo2   1.14.8-1
ii  libfontconfig1  2.11.0-6.7
ii  libfreetype62.6.3-3+b1
ii  libfribidi0 0.19.7-1
ii  libgdk-pixbuf2.0-0  2.36.2-1
ii  libglib2.0-02.50.2-2
ii  libice6 2:1.0.9-1+b1
ii  libperl4-corelibs-perl  0.003-2
ii  libpng16-16 1.6.26-6
ii  libreadline77.0-1
ii  librplay3   3.3.2-16+b1
ii  librsvg2-2  2.40.16-1
ii  libsm6  2:1.2.2-1+b1
ii  libstroke0  0.5.1-8
ii  libtinfo5   6.0+20161126-1
ii  libx11-62:1.6.4-2
ii  libxcursor1 1:1.1.14-1+b1
ii  libxext62:1.3.3-1
ii  libxft2 2.3.2-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.12-1
ii  libxrender1 1:0.9.10-1
ii  perl5.24.1~rc4-1

Versions of packages fvwm recommends:
ii  lxmenu-data  0.1.5-1
ii  python   2.7.13-1
ii  python-xdg   0.25-4

Versions of packages fvwm suggests:
ii  cpp   4:6.2.1-1
ii  libx11-protocol-perl  0.56-7
ii  m41.4.17-5
ii  perl-tk   1:804.033-1+b3
pn  stalonetray   

-- no debconf information

Bug#837750: build from diff-match-patch source package

[Stuart Prescott]

Control: reassign -1 src:diff-match-patch

The python package is based on the source package uploaded to pypi. Given that 
there seems to be no clear upstream (and that upstream development looks 
pretty dead), I have no problem with the diff-match-patch package taking over 
the python packages. The diff-match-patch source package can simply start 
including the python packages in d/control and then later the python-diff-
match-patch source package can be removed. Please feel free to do so -- I can 
ask ftp-master to remove the python-diff-match-patch source package later or 
you can point to this email yourself.

regards
Stuart



-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#849354: fvwm: Click not always taken into account or freezes the desktop

[Vincent Lefevre]

Package: fvwm
Version: 1:2.6.7-2
Severity: important

Since I've upgraded fvwm from 1:2.6.5.ds-4.1 to 1:2.6.7-2 (last night),
I have the following problems. I have the following in my config:

Mouse 1 A   SCM Raise

1. If the window is not yet on top, then it is not always raised.
Well, I'm not sure. It could be problem 2. See below.

2. If the window is already on top, then this sometimes freezes the
desktop: I can't do anything until I do another click.

I'd say that problem 1 occurs at around 1 over 10. AFAIK, it had never
occurred before the upgrade.

Problem 2 can occur at around 1 over 10, but sometimes it occurs
several times in a row. I don't know whether it is new, since I had
probably never done tests before. FYI, I've noticed it when I was
trying to find the cause of problem 1: I tried with xev to see if
the clicks were always reported[*], where the xev window is usually
on top.

[*] The result is that they seem to be.

Now, back to problem 1, I think that what I always did is to try
again, so that the window is raised. But with more tests, it actually
seems to be problem 2, i.e. the desktop is frozen, and the window is
not raised *as a consequence*! If I click anywhere (without SCM held),
then the window is raised, which would confirm that this is problem 2.

Note: I have not changed my FVWM config except the replacement of
FvwmWinList by FvwmIconMan (since FvwmWinList is no longer available
in FVWM 2.6.7).

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 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 fvwm depends on:
ii  libc6   2.24-8
ii  libcairo2   1.14.8-1
ii  libfontconfig1  2.11.0-6.7
ii  libfreetype62.6.3-3+b1
ii  libfribidi0 0.19.7-1
ii  libgdk-pixbuf2.0-0  2.36.2-1
ii  libglib2.0-02.50.2-2
ii  libice6 2:1.0.9-1+b1
ii  libperl4-corelibs-perl  0.003-2
ii  libpng16-16 1.6.26-6
ii  libreadline77.0-1
ii  librplay3   3.3.2-16+b1
ii  librsvg2-2  2.40.16-1
ii  libsm6  2:1.2.2-1+b1
ii  libstroke0  0.5.1-8
ii  libtinfo5   6.0+20161126-1
ii  libx11-62:1.6.4-2
ii  libxcursor1 1:1.1.14-1+b1
ii  libxext62:1.3.3-1
ii  libxft2 2.3.2-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.12-1
ii  libxrender1 1:0.9.10-1
ii  perl5.24.1~rc4-1

Versions of packages fvwm recommends:
ii  lxmenu-data  0.1.5-1
ii  python   2.7.13-1
ii  python-xdg   0.25-4

Versions of packages fvwm suggests:
ii  cpp   4:6.2.1-1
ii  libx11-protocol-perl  0.56-7
ii  m41.4.17-5
ii  perl-tk   1:804.033-1+b3
pn  stalonetray   

-- no debconf information

Bug#847288: libdbd-firebird-perl: FTBFS randomly (failing tests)

[gregor herrmann]

On Sun, 25 Dec 2016 20:06:46 +0100, Santiago Vila wrote:

> The "slowness" is the inverse of the speed. My unit of measure
> (i.e. slowness 1) is the speed of my i3-3217U @ 1.80GHz at home,
> which was my first autobuilder.

Don't know where my laptop qualifies with
model name  : Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz
:)
 
I let the test suite run in a loop several times now.
- In the first round it hang after t/embed-80-event-ithreads.t in the
  15th run.
- In the second round, it hang there in the 13th run.
- I stopped the third loop after 133 successful iterations.
- The fourth loop hangs in the 9th iteration, again after:

t/embed-80-event-ithreads.t . 
1..22
ok 1 - Connected to the database
ok 2 - Table is 'TESTAA'
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9 - callback registered
ok 10 - thread created
ok 11 - thread joined
ok 12 - callback unregistered
ok 13
ok 14
ok 15 - create thread


I don't think this qualifies as RC but there is indeed some sporadic
issue in the test suite.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Howe Gelb: Neon Filler


signature.asc
Description: Digital Signature

Bug#849352: gimp: Saving overtop existing BZ2 compressesd XCF files does not truncate them

[Ari Pollak]

Is the undo history saved too, which should contain the original layers?

Bug#765630: ssh_config(5): errors in the Debian defaults documentation

[Colin Watson]

Control: tag -1 pending

On Thu, Oct 16, 2014 at 08:25:40PM +0200, Christoph Anton Mitterer wrote:
> 1) In the beginning of the ssh_config(5) manpage it states:
> > Note that the Debian openssh-client package sets several options as stan‐
> > dard in /etc/ssh/ssh_config which are not the default in ssh(1):
> > ·   SendEnv LANG LC_*
> > ·   HashKnownHosts yes
> > ·   GSSAPIAuthentication yes
> 
> Looking however at the current fresh ssh_config shipped in the package
> this misses the entry:
> GSSAPIDelegateCredentials no

It's in fact the upstream default and always has been, so the manual
page isn't *wrong*, but this does mean that setting it explicitly is
redundant.  I've removed that for my next upload.

> 2) Also it seems that having  ServerAliveInterval=300 when BatchMode=yes
> is a Debian specific thing, which is no where documented.

The behaviour itself was documented in ssh_config(5), but I've committed
a change to note explicitly that it's Debian-specific.

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]

Bug#849353: btrfs-progs: new upstream version

[Christoph Anton Mitterer]

Package: btrfs-progs
Severity: wishlist

Hi.

The 4.7.x tree is pretty outdated... 4.9 is out since a few days.

Cheers,
Chris.

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

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

Versions of packages btrfs-progs depends on:
ii  e2fslibs1.43.3-1
ii  libblkid1   2.29-1
ii  libc6   2.24-8
ii  libcomerr2  1.43.3-1
ii  liblzo2-2   2.08-1.2
ii  libuuid12.29-1
ii  zlib1g  1:1.2.8.dfsg-4

btrfs-progs recommends no packages.

btrfs-progs suggests no packages.

-- no debconf information

Bug#734688: Logs are not rotated for a month

[Christoph Biedl]

Hello everybody,

looking at this old but nasty bug that must be fixed for stretch:

* Trying to understand what goes wrong I wrote a small script that
  creates a few scenarios and executes logrotate then. Run it in
  an arbitrary directory like /tmp/ as regular user, with a single
  parameter in the range 0 to 4. Expect a lot of failures.

* In my understanding logrotate never compresses older logfiles even
  if they are not compressed yet, this will lead to the observed
  clashes. So I was about to write a patch that similar for Bolesław's
  proposal detects if the target file already exists, but would
  compress it then. However:

* github[1] contains a link[2] to a patch gentoo created. At least
  for all scenario my test script above creates, it solves the problems.
  I'd suggest you all test it as well and report back.

Cheers,

Christoph

[1] https://github.com/logrotate/logrotate/pull/23
[2] 
https://gitweb.gentoo.org/repo/gentoo.git/plain/app-admin/logrotate/files/logrotate-3.10.0-atomic-create.patch?id=3aae9fbc
#!/bin/sh

set -e

mkdir -p logs
rm logs/* 2>/dev/null || true

create () {
touch logs/logfile
while [ "$1" ] ; do
echo "$1" >logs/logfile$1
shift
done
}

compress () {
while [ "$1" ] ; do
gzip logs/logfile$1
shift
done
}


case "$1" in
0)
# vanilla: some older logfiles
create  '.1' '.2' '.3'
compress'.1' '.2' '.3'
;;
1)
# first generation exists both plain and compressed
create  '.1' '.2' '.3'
compress'.1' '.2' '.3'
create  '.1'
;;
2)
# first generation is not compressed - ERROR
create  '.1' '.2' '.3' '.4'
compress '.2' '.3' '.4'
;;
3)
# gen.1 not compressed, gen.2 missing
create  '.1'  '.3' '.4'
compress  '.3' '.4'
;;
4)
# gen.1 not compressed, gen.[23] missing
create  '.1'   '.4'
compress   '.4'
;;
'')
echo "Usage: $0 "
exit 1
;;
*)
echo "BUG: Undefined scenario '$1'"
exit 2
;;
esac

CONF="$PWD/logrotate.conf"

cat <<__EOS__ >"$CONF"
$PWD/logs/logfile {
daily
missingok
rotate 3
compress
copytruncate
create 640 $(getent passwd $(id -u) | cut -d: -f1) $(getent group $(id -g) 
| cut -d: -f1)
}
__EOS__

STATE="$PWD/state"
rm "$STATE" >/dev/null || true

echo 'Files in logs/ [PRE]:'
ls -1 logs/

/usr/sbin/logrotate --force --state "$STATE" --verbose "$CONF" || true

echo 'Files in logs/ [POST]:'
ls -1 logs/
echo 'State file:'
cat "$STATE"


signature.asc
Description: Digital signature

Bug#849351: exiftool: manual page does not document -All option

[Mattia Rizzolo]

Control: reassign -1 libimage-exiftool-perl

On Mon, Dec 26, 2016 at 01:28:56AM +0200, Jari Aalto wrote:
> Package: exiftool

Assuming you mean /usr/bin/exiftool, that's pkg libimage-exiftool-perl.

> Severity: minor
> 
> The manual page refers to -All option but it is not listed in
> any of the options sections.
> 
> Please document -All in a standard way as the other options.
> 
> Jari

-- 
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#841670: lintian: Check udev rules and AppStream metadata

[Petter Reinholdtsen]

Is this patch OK, or should I clean it up some more?

I would love to have it included in lintian soon, to make more people
aware of the problem with device access in Stretch before the complete
freeze.

-- 
Happy hacking
Petter Reinholdtsen

Bug#776193: unshield: CVE-2015-1386: directory traversal

[Petter Reinholdtsen]

[Petter Reinholdtsen]
> A fix for this release critical security issue is now available as a
> pull request upstream.

I had a look at the upstream patch, and it do not apply cleanly to the
code in unstable, as the code has been restructured quite a bit upstream.

As unshield is currently missing from testing, and today is the last day
to upload packages missing in testing, I suspect unshield will be missing
from Stretch.  At least I lack the capacity to fix the problem in time.

-- 
Happy hacking
Petter Reinholdtsen

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[James Cameron]

Thanks to Paul Wise for the heads-up.

OLPC still has a software and hardware organisation (me), and is
using a Debian derivative (Ubuntu) on our latest hardware (NL3), using
the Debian packages of Sugar desktop.

Debian should drop olpc-xo1, olpc-powerd, and olpc-kbdshim.

OLPC models are XO-1, XO-1.5, XO-1.75, XO-4, and now NL3.

Right now, OLPC has manufacturing capability for XO-4 and NL3.

Debian only really worked well on the XO-1 and XO-1.5 models; these
are no longer manufactured, units in the field are past end of life,
and are failing at an expected high rate.

Anybody relying on an XO-1 or XO-1.5 should buy a new laptop.  ;-)

Disclosure: I'm paid by OLPC.

-- 
James Cameron
http://quozl.netrek.org/

Bug#837756: Pending fixes for bugs in the prometheus-alertmanager package

[pkg-go-maintainers]

tag 837756 + pending
thanks

Some bugs in the prometheus-alertmanager package are closed in
revision cfdebd8fcfa5767aeacaa7c3d561647166de8e1d in branch ' 
debian/sid' by Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/prometheus-alertmanager.git/commit/?id=cfdebd8

Commit message:

Provide golang-github-prometheus-alertmanager-dev. Closes: #837756.

Bug#846799: Pending fixes for bugs in the golang-google-cloud package

[Martín Ferrari]

Dmitry,

On 16/12/16 19:30, Dmitry Smirnov wrote:

>> Ensure the transition from symlink to directory is handled correctly.
>> Closes: #846799
> 
> Thanks for fixing this problem. FYI there is a better way to do that.
> Instead of duplicated section in preinst/postinst/postrm you can use one 
> "{PKGNAME}.maintscript" file with "symlink_to_dir" line.
> See dpkg-maintscript-helper(1) for details.

Thanks for the tip, I did not know this!


-- 
Martín Ferrari (Tincho)

Bug#849350: Pending fixes for bugs in the jimfs package

[pkg-java-maintainers]

tag 849350 + pending
thanks

Some bugs in the jimfs package are closed in revision
d3c825ff34ffbd7db24302e5cbf82b735e7d2494 in branch 'master' by
Hans-Christoph Steiner

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jimfs.git/commit/?id=d3c825f

Commit message:

add missing copyright statement (Closes: #849350)

Bug#849352: gimp: Saving overtop existing BZ2 compressesd XCF files does not truncate them

[Brendon Lloyd Higgins]

Package: gimp
Version: 2.8.18-1
Severity: normal

Dear Maintainer,

It seems that saving a .xcf.bz2 file does not properly trunctate it if the file
already exists. It's easy to not notice because it's only apparent if the file
should obviously be smaller than before. In my case, for example, I created a
file with many complex layers and saved it as .xcf.bz2. I then deleted all but
one simple layer and saved it, and found that the resulting filesize had not
reduced. When I tried bunzip2 on that file, it said "trailing garbage after EOF
ignored", which is what makes me believe the file was not truncated when gimp
saved it.

Peace,
Brendon



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

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

Versions of packages gimp depends on:
ii  gimp-data2.8.18-1
ii  libaa1   1.4p5-44
ii  libatk1.0-0  2.22.0-1
ii  libbabl-0.1-00.1.18-1
ii  libbz2-1.0   1.0.6-8
ii  libc62.24-8
ii  libcairo21.14.8-1
ii  libdbus-1-3  1.10.14-1
ii  libdbus-glib-1-2 0.108-1
ii  libexif120.6.21-2
ii  libexpat12.2.0-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libgegl-0.3-00.3.8-3
ii  libgimp2.0   2.8.18-1
ii  libglib2.0-0 2.50.2-2
ii  libgs9   9.20~dfsg-1
ii  libgtk2.0-0  2.24.31-1
ii  libgudev-1.0-0   230-3
ii  libice6  2:1.0.9-1+b1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libjson-glib-1.0-0   1.2.2-1
ii  liblcms2-2   2.8-2
ii  libmng1  1.0.10+dfsg-3.1+b3
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpangoft2-1.0-01.40.3-3
ii  libpng16-16  1.6.26-6
ii  libpoppler-glib8 0.48.0-2
ii  librsvg2-2   2.40.16-1
ii  libsm6   2:1.2.2-1+b1
ii  libtiff5 4.0.7-3
ii  libwmf0.2-7  0.2.8.4-10.6
ii  libx11-6 2:1.6.4-2
ii  libxcursor1  1:1.1.14-1+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2
ii  libxpm4  1:3.5.11-1+b1
ii  libxt6   1:1.1.5-1
ii  python-gtk2  2.24.0-5.1
ii  python2.72.7.13~rc1-1
pn  python:any   
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages gimp recommends:
ii  ghostscript  9.20~dfsg-1

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
pn  gvfs-backends 
ii  libasound21.1.2-1

-- no debconf information

Bug#848073: python3-django-macaddress: Compatibility of django-macaddress with django 1.10 in stretch

[Pierre-Elliott Bécue]

Control: severity -1 grave

This bug appears to be Release Critical as it prevents the library to work
with the current version of django.

Increasing severity to grave.

-- 
PEB

Bug#849351: exiftool: manual page does not document -All option

[Jari Aalto]

Package: exiftool
Severity: minor

The manual page refers to -All option but it is not listed in
any of the options sections.

Please document -All in a standard way as the other options.

Jari

Bug#826215: Bug #826214: Bug #826215: init-d-script and systemd: solution

[Christian Seiler]

Hello Martin,

On 12/25/2016 09:18 PM, Martin Pitt wrote:
> Christian Seiler [2016-12-25 13:34 +0100]:
>> I think I have a solution to both issues - and my solution
>> does not require any change to any individual init script,
>> and best of all it doesn't even require changes to any
>> sysvinit-related package (we get to have our cake and eat
>> it too):
> 
> Thanks for working on this!
> 
>> The systemd package could install a diversion of /lib/init/init-d-script and
>> install its own wrapper.
> 
> I don't like this approach, to be honest. (1) This diversion would be present
> on practically all installs anyway, as it would (necessarily) be in the
> "systemd" binary, not the "systemd-sysv" one. (2) I don't want to maintain 
> this
> SysV stuff in the systemd package forever, AND still have someone else 
> maintain
> the non-diverted variant in sysvinit-utils. I'd much prefer to just change the
> "master" copy in sysvinit-utils, and packages which use that should grow a
> dependency to that (so that it can become non-essential).

But the reason why you want to make sysvinit-utils non-essential is to
be able to remove the package. But if a lot of packages now depend on
it, then this will be installed on most installs regardless, so there's
no point in making the effort of making it non-essential. (Unless you
are really only interested in minimalistic base systems that aren't
really useful to anybody.)

What's the alternative? Michael proposed to go back to the old
template for init scripts in the initial bug report and basically drop
init-d-script from packages. As someone who maintains packages that
contain daemons, I strongly disagree: one of the appeals of systemd
(which I use and like btw.) is that service files are easy to read.
Same goes for init scripts that use init-d-script instead of what was
there previously, they are much easier to read than the horrible mess
that was there previously. His alternative proposal is much better,
but apparently not something the init-d-script people want, for
understandable reasons, and in addition both suggestions would
require that lots of consumers of init-d-script change their code.

In the end, you're just distributing a single additional script with
the systemd package. The maintenance burden is going to be essentially
zero, because the interface of init-d-script can't change without all
of the consumers having to be updated. I think the whole integration
that makes shutdown while switching init systems work is probably a
lot more work than shipping this file + the diversion, even if that
diversion is going to be installed on most systems. (Which I don't
consider to be a problem, just look at the fact that /bin/sh is a
diversion on nearly all installed Debian systems, which is a lot more
essential to a running system than init-d-script.)

Also, consider the following: with how I wrote this wrapper, if _all_
installed init scripts use init-d-script _and_ have native systemd
service equivalents, then /lib/lsb/init-functions and
/lib/init/vars.sh also don't have to be installed on systemd systems,
because the wrapper will also work in those cases and properly
redirect to systemctl there. You can then get rid of all of the
sysvinit packages in that case - and just carry two files in the
systemd package, /lib/lsb/init-functions.d/40-systemd and the
wrapper I created, for compatibility reasons. This will make it quite
a bit easier to reduce the amount of installed packages on the system.

> I. e. use your script but patch the current one instead of duplicating it.

Well, my script doesn't duplicate the init-d-script logic at all. It is
just some glue code hat hooks up the upcall to systemctl (but reuses
existing code for that), and falls back to the original implementation
if systemd isn't used (or another corner case is hit).

> If the SysV init maintainers don't want to carry this either, then there's
> still the option to just drop the systemd integration, and break calling
> /etc/init.d/foo directly under systemd. WDYT?

I don't think that we should break that as long as we provide init
scripts in packages.

That all said: if you just want to fix #826214, I can also provide
a patch for the systemd package that updates
/lib/lsb/init-functions.d/40-systemd to properly work with
init-d-script - without you having to modify init-d-script or any
consumer thereof itself. But that won't help for #826215, when it
comes to how packages acquire dependencies on sysvinit-utils.

Regards,
Christian

Bug#849350: jimfs: Incomplete debian/copyright?

[Chris Lamb]

Source: jimfs
Version: 1.1-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Hans-Christoph Steiner 

Hi,

I just ACCEPTed jimfs from NEW but noticed it was missing attribution 
in debian/copyright for the embedded murmurhash implementation.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

Bug#806092: proposed fix

[Dima Kogan]

I'm attaching two patches to fix this. Please review soon if
possible. If I don't hear back by Dec 26, I'll NMU this. That's the
latest possible day to meet the cutoff for stretch.


>From 65bd793529cc6aae5f6f1946396cde03e55a2620 Mon Sep 17 00:00:00 2001
From: Dima Kogan 
Date: Sun, 25 Dec 2016 14:55:05 -0800
Subject: [PATCH 1/2] We can now build arch-dependent and arch-independent
 packages only

I.e. "dpkg-buildpackage -A" and "dpkg-buildpackage -B" works. Closes: #806092
---
 debian/rules | 32 ++--
 1 file changed, 22 insertions(+), 10 deletions(-)

diff --git a/debian/rules b/debian/rules
index 759ed3d..e7df4c7 100755
--- a/debian/rules
+++ b/debian/rules
@@ -10,26 +10,31 @@ CONFIGURE_OPTS=--disable-rpath --enable-dbus --disable-update-desktop-database -
 %:
 	dh $@ --with=autotools_dev
 
+# I configure build-gtk unconditionally (arch-dependent and arch-independent)
+# because I need a single configure invocation in both cases
 override_dh_auto_configure:
-	dh_auto_configure --builddirectory build_gtk -- $(CONFIGURE_OPTS) --with-gui=gtk
-	dh_auto_configure --builddirectory build_lesstif -- $(CONFIGURE_OPTS) --with-gui=lesstif
+	dh_auto_configure--builddirectory build_gtk -- $(CONFIGURE_OPTS) --with-gui=gtk
+	dh_auto_configure -a --builddirectory build_lesstif -- $(CONFIGURE_OPTS) --with-gui=lesstif
 
 override_dh_auto_build:
-	dh_auto_build --builddirectory build_gtk
-	dh_auto_build --builddirectory build_lesstif
+	dh_auto_build -a --builddirectory build_gtk
+	dh_auto_build -a --builddirectory build_lesstif
 
 override_dh_auto_test:
-	dh_auto_test --builddirectory build_gtk
-	dh_auto_test --builddirectory build_lesstif
+	dh_auto_test -a --builddirectory build_gtk
+	dh_auto_test -a --builddirectory build_lesstif
 
-override_dh_auto_install:
-	dh_auto_install --builddirectory build_gtk
+override_dh_auto_install-arch:
+	make -C build_gtk install-exec DESTDIR=$$PWD/debian/tmp AM_UPDATE_INFO_DIR=no
+
+override_dh_auto_install-indep:
+	make -C build_gtk install-data DESTDIR=$$PWD/debian/tmp AM_UPDATE_INFO_DIR=no
 
 override_dh_auto_clean:
 	dh_auto_clean --builddirectory build_gtk
 	dh_auto_clean --builddirectory build_lesstif
 
-override_dh_install:
+override_dh_install-arch:
 	# Remove needlessly installed static library and header file before
 	# installing common files:
 	rm -rf $(CURDIR)/debian/tmp/usr/lib
@@ -42,6 +47,13 @@ override_dh_install:
 	# Install pcb-lesstif binary:
 	install build_lesstif/src/pcb debian/$(package)-lesstif/usr/bin/pcb-lesstif
 
+override_dh_install-indep:
+	# Remove needlessly installed static library and header file before
+	# installing common files:
+	rm -rf $(CURDIR)/debian/tmp/usr/lib
+	rm -rf $(CURDIR)/debian/tmp/usr/include
+	dh_install -Xusr/bin -Xusr/share/pcb- -Xusr/share/doc -Xexamples -Xtutorial -Xusr/share/info
+
 	# Set executable bit for pcb tools:
 	[ ! -d debian/$(package)-common ] || chmod a+x debian/$(package)-common/usr/share/pcb/tools/MergePCBPS
 	[ ! -d debian/$(package)-common ] || chmod a+x debian/$(package)-common/usr/share/pcb/tools/Merge_dimPCBPS
@@ -52,7 +64,7 @@ override_dh_install:
 	# Remove empty dirs:
 	[ ! -d debian/$(package)-common ] || find debian/$(package)-common -type d -empty -delete
 
-override_dh_fixperms:
+override_dh_fixperms-indep:
 	dh_fixperms
 	# Fix permissions of a couple of example files:
 	[ ! -d debian/$(package)-common ] || chmod -x debian/$(package)-common/usr/share/doc/$(package)-common/examples/LED.pcb
-- 
2.10.1

>From 77ee5069c455bd3458a20875c328c9642ded0fdf Mon Sep 17 00:00:00 2001
From: Dima Kogan 
Date: Sun, 25 Dec 2016 14:56:11 -0800
Subject: [PATCH 2/2] changelog bump

---
 debian/changelog | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 1fa754f..62c65c5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+pcb (20140316-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Closes: #806092
+
+ -- Dima Kogan   Sun, 25 Dec 2016 14:56:02 -0800
+
 pcb (20140316-3) unstable; urgency=medium
 
   * (Build-)Depend on unversioned tcl/tk
-- 
2.10.1

Bug#849338: ITP: hxtools -- Collection of tools and scripts

[Ben Hutchings]

On Sun, 2016-12-25 at 19:50 +0100, Jochen Sprickerhof wrote:
> Package: wnpp
> Severity: wishlist
> > Owner: Jochen Sprickerhof 
> 
> * Package name: hxtools
>   Version : 20150304
>   Upstream Author : Jan Engelhardt 
> * URL : http://inai.de/projects/hxtools/
> * License : GPL, LGPL, WTFPL
>   Programming Lang: C, Perl, Bash
>   Description : Collection of tools and scripts
> 
>  A collection of tools and scripts that have accumulated over the years, and
>  each of which seems to be too small to warrants its own project.

These look mostly very esoteric; could you consider packaging just the
most general and polished ones?

[...]
>   * git-author-stat(1) - show commit author statistics of a git repository
>   * git-blame-stat(1) - show per-line author statistics of a git repository
>   * git-export-patch(1) - produce perfect patch from git commits for mail 
> submission
>   * git-forest(1) - display the commit history forest
>   * git-lemon(1) - don't just pick cherries, but take it all (cherry-pick a 
> commit range)
>   * git-new-root(1) - start a new root in the git history
>   * git-revert-stats(1) - show reverting statistics of a git repository
>   * git-track(1) - set up branch for tracking a remote

Perhaps (some of) these belong in the contrib directory of git
upstream?

[...]
>   * png2wx.pl(1) - transform arbitrary files into C++ files for wxWidgets
[...]
>   * rpmdep.pl(1) - read RPM dependencies and output a graph
[...]

Extensions like .pl in command names are forbidden by policy.

Ben.

-- 
Ben Hutchings
I say we take off; nuke the site from orbit.  It's the only way to be
sure.



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

Bug#849338: ITP: hxtools -- Collection of tools and scripts

[Guus Sliepen]

On Sun, Dec 25, 2016 at 07:50:43PM +0100, Jochen Sprickerhof wrote:

> * Package name: hxtools
>   Upstream Author : Jan Engelhardt 
> * URL : http://inai.de/projects/hxtools/
> 
>  A collection of tools and scripts that have accumulated over the years, and
>  each of which seems to be too small to warrants its own project.

I agree these are too small to warrant their own project/package, on the
other hand, this collection is very random. Some comments:

>   * cctypeinfo(1) - show sizes of C types on the implementation it was 
> compiled with

This just prints the results of a hardcoded list of types, it is not
some generic tool that can give info about any type.

>   * cwdiff(1) - run wdiff with color

This is a oneliner, this kind of functionality would be better merged
into wdiff itself.

>   * declone(1) - break hardlinks

Maybe something for coreutils?

>   * doxygen-kerneldoc-filter(1) - filter for Doxygen to support kerneldoc

Should go into Doxygen.

>   * extract_d3pkg(1) - extract Descent3 PKG files
>   * extract_dxhog(1) - extract Descent HOG files
>   * extract_f3pod(1) - extract Fury3 POD files
>   * extract_qupak(1) - extract Quake2 PACK files

Very game specific.

>   * fxterm(1) - start xterm with sane settings

It's very subjective what you think "sane" means.

>   * git-author-stat(1) - show commit author statistics of a git repository
>   * git-blame-stat(1) - show per-line author statistics of a git repository
>   * git-export-patch(1) - produce perfect patch from git commits for mail 
> submission
>   * git-forest(1) - display the commit history forest
>   * git-lemon(1) - don't just pick cherries, but take it all (cherry-pick a 
> commit range)
>   * git-new-root(1) - start a new root in the git history
>   * git-revert-stats(1) - show reverting statistics of a git repository
>   * git-track(1) - set up branch for tracking a remote

I would avoid packaging these. If upstream git wants to implement
commands with identical names, it will create a problem.

>   * mailsplit(1) - split an mbox into single files
>   * man2html(1) - convert nroff manpages to HTML

There is already a binary with this name in the man2html-base package.

>   * netload(8) - show utilization of network interface

Already in the package netdiag.

>   * newns(8) - clone current filesystem namespace and start a process

Sounds like something for util-linux,

>   * omixer(1) - volume control using the OSS Sound API
>   * oplay(1) - raw PCM playback using the OSS Sound API
>   * orec(1) - raw PCM recording using the OSS Sound API

Does anyone still use OSS?

>   * pshtreads(1) - alternative experiment to ps(1) involving thread display

If it's useful, merge it with procps?

>   * sysinfo(1) - print IRC-style system information banner

A binary with that name is already in the sysinfo package.

>   * tailhex(1) - hex dumper with tail-following support

od -x | tail? Do we really need a tool for this?

>   * wavdiff(1) - proof-of-concept raw PCM deltifier

I think it's called pcmdiff in the latest version from hxtools git
repository. Also, I'd expect sox to be the place for this kind of
funtionality.

>   * xcp(1) - proof-of-concept cp(1) with alternate copying mechanisms

I'm quite sure cp from coreutils is using an optimal algorithm, and if
it doesn't, it should be fixed there instead of having another tool that
does not implement everything cp does, and may not even be faster.

>   * xfs_irecover(1) - recover lost inodes from XFS filesystems.

This should go into xfsprogs.

> This package is used by the libpam-mount package (currently patched in).

What exactly of hxtools is used in libpam-mount?

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature

Bug#849349: ipmitool: Please fix enablement of usb interface in 1.8.18

[Steve Langasek]

Package: ipmitool
Version: 1.8.18-2
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch

It has been reported in Ubuntu that ipmitool 1.8.18 is missing the USB
interface.  Looking at the build logs in both Debian and Ubuntu shows that
support for usb is not being autodetected.

However, a simple change to debian/rules to force enablement of the usb
interface results in it being properly built in.

Please find attached a patch to correct this missing functionality in
ipmitool in Debian.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ipmitool-1.8.18/debian/rules ipmitool-1.8.18/debian/rules
--- ipmitool-1.8.18/debian/rules	2016-05-15 01:16:02.0 -0500
+++ ipmitool-1.8.18/debian/rules	2016-12-25 16:44:17.0 -0600
@@ -16,6 +16,8 @@
 ifneq ($(DEB_HOST_ARCH_OS),linux)
 	# USB implementation is Linux-specific
 	extra_config_opts += --disable-intf-usb
+else
+	extra_config_opts += --enable-intf-usb
 endif
 
 

Bug#818230: aircrack-ng: please make the build reproducible

[Samuel Henrique]

Control: tags -1 + pending
Control: forwarded -1 https://github.com/aircrack-ng/aircrack-ng/pull/91

Fix commited and sent upstream, thanks a lot Reiner

Samuel Henrique 

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Jonas Smedegaard]

Quoting Adam Borowski (2016-12-25 23:23:32)
> On Sun, Dec 25, 2016 at 06:06:12PM +0100, Jonas Smedegaard wrote:
> > > I'm pretty sure they haven't produced XO-1s in close to a decade, and 
> > > that us what my packages are for.  XO-1.5 and XO-4 were never 
> > > supported without additional hacks.
> > > 
> > > That said, I can orphan the packages; I just don't see much point with 
> > > such old hardware and the lack of package users.
> > 
> > I agree it makes sense to drop this package: Despite the hardware vendor 
> > still issueing software, we can no longer do so, because the XO-1 uses 
> > an X86 chipset is incompatible with our i686 libc and kernel, I believe 
> > (I haven't tested for quite some time, though - please correct me if 
> > wrong).
> 
> XO-1 uses Geode LX which lacks just NOPL for full 686 ISA, and our version
> of gas doesn't issue NOPL for this reason.
> 
> It's possible there are other show stoppers, but I have no idea here.

Ah, interesting.  Then there might be hope still.  thanks!

@Andres: Please don't drop the OLPC packages.  I can adopt them and 
maintain them in the Sugar team (and will dust off my XO-1 laptops 
collecting dust in a shelf).

 - Jonas

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

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

Bug#849348: chrome-gnome-shell: Install Firefox extension

[Jeremy Bicha]

Package: chrome-gnome-shell
Version: 7.2-2
Severity: wishlist

Take a look here:
https://blogs.gnome.org/ne0sight/2016/12/25/how-to-install-gnome-shell-extensions-with-firefox-52/

Firefox 52 is scheduled for release March 7 and is also an ESR release
so it will impact Debian soon.

Maybe we should have gnome-shell depend on chrome-gnome-shell. (I
still don't understand the circular dependency issue, but in that case
maybe chrome-gnome-shell should not depend on gnome-shell but only
Recommend or Enhance it). And then release chrome-gnome-shell 8 and
the gnome-shell dependency change to jessie.

Anyway, the bug I intended to report here is that I think it would be
nice if the chrome-gnome-shell package installed at least the Firefox
browser extension so that users don't have to manually visit
https://addons.mozilla.org/ to get about the same behavior as before
Firefox 52.

There's a Firefox requirement for extensions to be signed but Debian
overrides this for extensions in system directories.

Thanks,
Jeremy Bicha

Bug#849347: libchromaprint.so.1.4.1: prelink complains that libchromaprint.so.1.4.1 contains a dependency cycle

[Arthur Marsh]

Package: libchromaprint1
Version: 1.4.1-1
Severity: normal
File: libchromaprint.so.1.4.1

Dear Maintainer,

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

   * What led up to the situation?

upgrading libchromaprint1 and running prelink

Nothing leapt out at me when I looked at the ldd output:

$ ldd $(locate libchromaprint.so.1.4.1)
linux-vdso.so.1 (0x7ffeb459)
libavcodec.so.57 => /usr/lib/x86_64-linux-gnu/libavcodec.so.57 
(0x7f151616)
libavformat.so.57 => /usr/lib/x86_64-linux-gnu/libavformat.so.57 
(0x7f1515d25000)
libavutil.so.55 => /usr/lib/x86_64-linux-gnu/libavutil.so.55 
(0x7f1515aa2000)
libswresample.so.2 => /usr/lib/x86_64-linux-gnu/libswresample.so.2 
(0x7f1515883000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f1515501000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f15151fb000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f1514fe4000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1514c46000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f1514a42000)
libva.so.1 => /usr/lib/x86_64-linux-gnu/libva.so.1 (0x7f1514822000)
libzvbi.so.0 => /usr/lib/x86_64-linux-gnu/libzvbi.so.0 
(0x7f1514595000)
libxvidcore.so.4 => /usr/lib/x86_64-linux-gnu/libxvidcore.so.4 
(0x7f151427f000)
libx265.so.95 => /usr/lib/x86_64-linux-gnu/libx265.so.95 
(0x7f151364b000)
libx264.so.148 => /usr/lib/x86_64-linux-gnu/libx264.so.148 
(0x7f15132a9000)
libwebpmux.so.2 => /usr/lib/x86_64-linux-gnu/libwebpmux.so.2 
(0x7f151309f000)
libwebp.so.6 => /usr/lib/x86_64-linux-gnu/libwebp.so.6 
(0x7f1512e3f000)
libwavpack.so.1 => /usr/lib/x86_64-linux-gnu/libwavpack.so.1 
(0x7f1512c15000)
libvpx.so.4 => /usr/lib/x86_64-linux-gnu/libvpx.so.4 
(0x7f15127dd000)
libvorbisenc.so.2 => /usr/lib/x86_64-linux-gnu/libvorbisenc.so.2 
(0x7f1512534000)
libvorbis.so.0 => /usr/lib/x86_64-linux-gnu/libvorbis.so.0 
(0x7f1512308000)
libtwolame.so.0 => /usr/lib/x86_64-linux-gnu/libtwolame.so.0 
(0x7f15120e5000)
libtheoraenc.so.1 => /usr/lib/x86_64-linux-gnu/libtheoraenc.so.1 
(0x7f1511ea6000)
libtheoradec.so.1 => /usr/lib/x86_64-linux-gnu/libtheoradec.so.1 
(0x7f1511c88000)
libspeex.so.1 => /usr/lib/x86_64-linux-gnu/libspeex.so.1 
(0x7f1511a6d000)
libsnappy.so.1 => /usr/lib/x86_64-linux-gnu/libsnappy.so.1 
(0x7f1511865000)
libshine.so.3 => /usr/lib/x86_64-linux-gnu/libshine.so.3 
(0x7f1511658000)
libopus.so.0 => /usr/lib/x86_64-linux-gnu/libopus.so.0 
(0x7f151140b000)
libopenjp2.so.7 => /usr/lib/x86_64-linux-gnu/libopenjp2.so.7 
(0x7f15111d)
libmp3lame.so.0 => /usr/lib/x86_64-linux-gnu/libmp3lame.so.0 
(0x7f1510f59000)
libgsm.so.1 => /usr/lib/x86_64-linux-gnu/libgsm.so.1 
(0x7f1510d4a000)
libcrystalhd.so.3 => /usr/lib/x86_64-linux-gnu/libcrystalhd.so.3 
(0x7f1510b2f000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f1510909000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f15106ef000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f15104d2000)
libssh-gcrypt.so.4 => /usr/lib/x86_64-linux-gnu/libssh-gcrypt.so.4 
(0x7f1510263000)
libmodplug.so.1 => /usr/lib/x86_64-linux-gnu/libmodplug.so.1 
(0x7f150fed4000)
libgme.so.0 => /usr/lib/x86_64-linux-gnu/libgme.so.0 
(0x7f150fc87000)
libbluray.so.1 => /usr/lib/x86_64-linux-gnu/libbluray.so.1 
(0x7f150fa3d000)
libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 
(0x7f150f6a5000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f150f495000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 
(0x7f150f155000)
libvdpau.so.1 => /usr/lib/x86_64-linux-gnu/libvdpau.so.1 
(0x7f150ef4f000)
libva-drm.so.1 => /usr/lib/x86_64-linux-gnu/libva-drm.so.1 
(0x7f150ed4c000)
libva-x11.so.1 => /usr/lib/x86_64-linux-gnu/libva-x11.so.1 
(0x7f150eb46000)
libsoxr.so.0 => /usr/lib/x86_64-linux-gnu/libsoxr.so.0 
(0x7f150e8e3000)
/lib64/ld-linux-x86-64.so.2 (0x55589c1ea000)
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 
(0x7f150e6b)
libnuma.so.1 => /usr/lib/x86_64-linux-gnu/libnuma.so.1 
(0x7f150e4a3000)
libogg.so.0 => /usr/lib/x86_64-linux-gnu/libogg.so.0 
(0x7f150e29a000)
libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 
(0x7f150df86000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f150dd7e000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f150da6e000)
libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 

Bug#755434: pmount: please support exfat filesystem (via fuse)

[Vincent Danjean]

Package: pmount
Version: 0.9.99-alpha-1
Followup-For: Bug #755434

  Hi,

  It would be pleasant if pmount stretch supports exfat. I know
the problems with this FS, but it is more and more used on
large SD cards (in camera for example).

  The patch is simple (and can be applied on the current stretch
version if you do not plan to upload 0.9.99-alpha-1 to stretch).
It comes from https://bugs.launchpad.net/ubuntu/+source/pmount/+bug/1524523
I add it for reference in this mail.

  Regards,
Vincent


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

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

Versions of packages pmount depends on:
ii  libblkid1  2.29-1
ii  libc6  2.24-8

pmount recommends no packages.

Versions of packages pmount suggests:
ii  cryptsetup  2:1.7.3-3

-- no debconf information
diff --git a/debian/patches/02-exfat-support.diff 
b/debian/patches/02-exfat-support.diff
new file mode 100644
index 000..19650df
--- /dev/null
+++ b/debian/patches/02-exfat-support.diff
@@ -0,0 +1,11 @@
+Add support for exfat
+--- a/src/fs.c
 b/src/fs.c
+@@ -23,6 +23,7 @@
+ { "iso9660", "nosuid,nodev,user", 1, NULL, ",iocharset=%s" },
+ { "vfat", "nosuid,nodev,user,quiet,shortname=mixed", 1, "077", 
+   ",iocharset=%s",",fmask=%04o,dmask=%04o"},
++{ "exfat", "nosuid,nodev,user,quiet,nonempty", 1, "077", 
",iocharset=%s",",fmask=%04o,dmask=%04o"},
+ { "hfsplus", "nosuid,nodev,user", 1, NULL, 0 },
+ { "hfs", "nosuid,nodev,user", 1, "077", NULL, 
+   ",file_umask=%04o,dir_umask=%04o"},
diff --git a/debian/patches/series b/debian/patches/series
index e706419..f1ac0f2 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 01-man-plugdev.diff
+02-exfat-support.diff

Bug#835456: FTBFS: t/refhang.t test fail on s390x

[Ivo De Decker]

Control: found -1 1.4.28-1
Control: retitle -1 FTBFS: t/refhang.t test fail

Hi,

On Thu, Aug 25, 2016 at 10:27:33PM +0200, g...@iroqwa.org wrote:
> Just for the record, the upstream test suite fail on s390x
> 
> https://buildd.debian.org/status/fetch.php?pkg=memcached=s390x=1.4.31-1=1471823136
> 
> I'll open a issue to upstream to definitively fix it.

The issue also happens with version 1.4.28-1 (currently in testing) and on the
buildd on ppc64el:
https://buildd.debian.org/status/fetch.php?pkg=memcached=ppc64el=1.4.33-1=1478289801

I was able to reproduce it on amd64 by running the build in a loop (it failed
in less than 10 tries).

This probably is the same issue as #831253.

Cheers,

Ivo

Bug#848999: gnupg-agent: Fails to work

[Joerg Jaspert]

reassign 848999 pinentry-gtk2
notfound 848999 2.1.16-3
found 848999 1.0.0-1
affects 848999 gnupg-agent
thanks

(Lets see if the affects works out, never used before.

On 14528 March 1977, Joerg Jaspert wrote:
> Package: gnupg-agent
> Version: 2.1.16-3
> Severity: important

> not an easy problem to describe, but from the effects on me, grave or
> critical ought to be the Severity...

> Since the switch to gpg2 as default and especially with the latest
> version recently appeared in stretch, gnupg-agent is about unusable
> here. It basically refuses to work in 98% of the times.

[...]

> Now, how to debug this and find a cause and fix?

While noone else has actually send anything in ( :( ), I got a reply
from upstream, which made me play around with settings. Didn't help
much, but one sentence mentioned brokenness in the pinentry-gnome part.

Also, I was using pinentry-gtk2 all the time, so that shouldn't hit, but
well, change it, worth a try. And voila, I put pinentry-qt onto my
system and update-alternative-d it to be the one in use - and since then
(2 days by now!), I did not have the mentioned problems anymore.

Both, -gtk2 and -qt have the same version number and appear to be from
same source, but qt works for me, gtk2 not.

-- 
bye, Joerg

Bug#836885: Re-add heimdal-multidev?

[Jelmer Vernooij]

On Sun, Dec 25, 2016 at 01:03:15PM -0800, Ryan Tandy wrote:
> On Sun, Dec 25, 2016 at 09:05:15PM +0100, Michael Fladischer wrote:
> > Now that heimdal has some upstream activity again and 7.1.0 has been
> > uploaded to unstable, is there a chance that openldap will reenable
> > support for "krb5" in "olcSmbK5PwdEnable"?
> 
> I really hope we can, but right now I'm reluctant to change anything until
> heimdal actually migrates to testing.
> 
> My understanding is since heimdal was removed it will be subject to the
> freeze on new packages entering testing (Jan 5th); and given the mips*
> builds currently appear to be blocked by #844357 or something resembling it,
> that doesn't look guaranteed. :/
> 
> If the new version of heimdal does enter testing I will for sure do my best
> to enable support for it in smbk5pwd again promptly.

FWIW Heimdal wasn't actually removed from testing - the new upstream version
happened before all the packages that depended on it were removed from testing
- but we can't really release with what's currently in testing.

Jelmer

Bug#846854: nagios2mantis: Don't depend on nagios3 which has been removed from unstable

[Moritz Mühlenhoff]

On Sat, Dec 03, 2016 at 06:54:26PM +0100, Bas Couwenberg wrote:
> Source: nagios2mantis
> Version: 3.1-1.1
> Severity: normal
> Tags: patch
> 
> Dear Maintainer,
> 
> Please update your package to deal with the nagios3 removal from Debian
> (#845765).

Or let's simply remove nagios2mantis, after all mantis has been removed
from Debian as well.

Cheers,
Moritz

Bug#846061: [Pkg-amule-devel] Bug#846061: (no subject)

[Sandro Tosi]

On Sun, Dec 25, 2016 at 4:33 AM, eder  wrote:
> Same here. Amule completly unusable because constant crashes.

and as i've asked before:

please follow the steps at
http://wiki.amule.org/wiki/Backtraces#Create_a_backtrace to generate a
gdb backtrace and report it back here, thanks

-- 
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#848025: RM: openslp-dfsg -- RoQA; unmaintained, no longer used

[Moritz Mühlenhoff]

tags 848025 -moreinfo
thanks

On Tue, Dec 20, 2016 at 01:04:21AM -0500, Scott Kitterman wrote:
> On Tue, 13 Dec 2016 11:46:55 +0100 Moritz Muehlenhoff  wrote:
> > Package: ftp.debian.org
> > Severity: normal
> > 
> > Hi,
> > please remove openslp-dfsg. See
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795428
> > for further information, all reverse dependencies have been
> > fixed now.
> 
> Not according to dak:
> 
> Checking reverse dependencies...
> # Broken Depends:
> open-build-service: obs-worker [amd64 arm64 armhf i386 mips mips64el mipsel 
> ppc64el s390x]
> roaraudio: libroar-dev [kfreebsd-amd64 kfreebsd-i386]
> 
> The one that impacts release archs will have to be addressed prior to 
> removal.  
> Please remove the moreinfo tag once it's addressed.

These are now resolved.

Cheers,
Moritz

Bug#849346: CVE-2015-3239

[Moritz Muehlenhoff]

Source: android-platform-external-libunwind
Severity: grave
Tags: security

Hi,
https://security-tracker.debian.org/tracker/CVE-2015-3239 has been fixed in
src:unwind, but is still needed in android-platform-external-libunwind

Cheers,
Moritz
 

Bug#849316: machinctl: fails to list anything if a libvirt qemu container is running

[Felipe Sateler]

Control: forwarded -1 https://github.com/systemd/systemd/pull/4972

On 25 December 2016 at 06:52, Guido Günther  wrote:
> Package: systemd
> Version: 232-8
> Severity: normal
> Tags: patch
>
> Hi,
> machinectl currently silently aborts if libvirt managed QEMU VMs are
> running and does not list anything. This is fixed in
>
> https://github.com/systemd/systemd/pull/4972
> or
> https://github.com/systemd/systemd/pull/4978
>
> Would be great to ohave this in stretch since it breaks machinectl
> completely for some use cases.
>

PR 4978 was closed in favor of 4972. However, it has not been merged
yet. The patch is small so at least I don't have a problem with
backporting. However, we prefer patches to be merged upstream, so
we'll wait until the PR is merged. Feel free to ping again if the PR
is merged and there has been no activity.


-- 

Saludos,
Felipe Sateler

Bug#849345: The connman.postrm is plain wrong. It must remove the state dir only on purging

[Alf Gaida]

Package: connman
Version: 1.33-2
Severity: serious

Dear Maintainer,
that goes in per incident - reverting this would fix the situation.

Cheers Alf


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

Kernel: Linux 4.9.0-towo.1-siduction-amd64 (SMP w/8 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 connman depends on:
ii  dbus 1.10.14-1
ii  init-system-helpers  1.46
ii  libc62.24-8
ii  libdbus-1-3  1.10.14-1
ii  libglib2.0-0 2.50.2-2
ii  libgnutls30  3.5.7-3
ii  libreadline7 7.0-1
ii  libxtables12 1.6.0+snapshot20161117-4
ii  lsb-base 9.20161125

Versions of packages connman recommends:
pn  bluez  
pn  ofono  
ii  wpasupplicant  2.6-2

Versions of packages connman suggests:
pn  connman-vpn  

-- no debconf information

Bug#848419: trac-announcer: FTBFS in stretch (failing tests)

[W. Martin Borgert]

It seems, that trac-announcer is not yet compatible with current
trac. The package will therefore not be in stretch. If a fixed
version is released, we can deliver it via backports.

Bug#836885: Re-add heimdal-multidev?

[Ryan Tandy]

On Sun, Dec 25, 2016 at 09:05:15PM +0100, Michael Fladischer wrote:

Now that heimdal has some upstream activity again and 7.1.0 has been
uploaded to unstable, is there a chance that openldap will reenable
support for "krb5" in "olcSmbK5PwdEnable"?


I really hope we can, but right now I'm reluctant to change anything 
until heimdal actually migrates to testing.


My understanding is since heimdal was removed it will be subject to the 
freeze on new packages entering testing (Jan 5th); and given the mips* 
builds currently appear to be blocked by #844357 or something resembling 
it, that doesn't look guaranteed. :/


If the new version of heimdal does enter testing I will for sure do my 
best to enable support for it in smbk5pwd again promptly.

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Jonas Smedegaard]

Quoting Andres Salomon (2016-12-25 06:26:43)
> On December 24, 2016 7:24:00 PM PST, Paul Wise  wrote:
>>On Sun, Dec 25, 2016 at 10:38 AM, Andres Salomon wrote:
>>
>>> Thanks for the patch.  Given that OLPC isn't really alive any more,
>>> I'm thinking the OLPC packages should probably just be removed from
>>the
>>> archive for Stretch.  Popcon shows exactly 1 installation of this
>>> package.. https://qa.debian.org/popcon.php?package=olpc-xo1
>>
>>I think you will find that OLPC is still active and recently made a
>>release:
>>
>>http://lists.laptop.org/pipermail/devel/2016-December/thread.html
>>
>>They also have a Debian derivative:
>>
>>https://wiki.debian.org/Derivatives/Census/OLPC
>>
>>I've asked James to respond to your mail.
>>
> 
> 
> I meant OLPC the hardware organization.
>
> I'm glad to see James is still producing Fedora-based images for 
> legacy hardware.

For the record, OLPC is still alive, and still (pay James Cameron to 
help prepare, and) release (Fedora-derived) system images for the (no 
longer sold) XO-1 laptop.


> I'm pretty sure they haven't produced XO-1s in close to a decade, and 
> that us what my packages are for.  XO-1.5 and XO-4 were never 
> supported without additional hacks.
> 
> That said, I can orphan the packages; I just don't see much point with 
> such old hardware and the lack of package users.

I agree it makes sense to drop this package: Despite the hardware vendor 
still issueing software, we can no longer do so, because the XO-1 uses 
an X86 chipset is incompatible with our i686 libc and kernel, I believe 
(I haven't tested for quite some time, though - please correct me if 
wrong).


 - Jonas

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

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

Bug#849298: libconfig-inifiles-perl: Infinite loop when "each" is used

[Niko Tyni]

Control: tag -1 patch

On Sun, Dec 25, 2016 at 12:24:45AM +0100, Johannes Schauer wrote:
> Package: libconfig-inifiles-perl
> Version: 2.94-1
> Severity: normal

> use Config::IniFiles;
> tie (my %ini, 'Config::IniFiles', -file=>"test.ini");
> foreach my $s (keys %ini) {
> while (my ($k,$v) = each %{$ini{$s}}) {
> print("$s $k $v\n");
> }
> }

> The result will be an infinite loop printing "foo bar baz".

Thanks for the report.

What is happening is that every time $ini{$s} is evaluated,
Config::IniFiles::FETCH() creates a new Config::IniFiles::_section tied
hash that has its own each() iterator.

A workaround is to do something like

  foreach my $s (@k) {
  my $i = $ini{$s};
  while (my ($k,$v) = each %$i) {
  print("$s $k $v\n");
  }
  }
 
but I'm attaching a patch that seems to fix this without breaking any
existing tests.
-- 
Niko Tyni   nt...@debian.org
>From b9acffc56b85c71cde4b13751256bb37a64d9c2a Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sun, 25 Dec 2016 21:38:51 +0200
Subject: [PATCH] Reuse Config::IniFiles::_section hashes in
 Config::IniFiles::FETCH

As reported by Johannes Schauer, code like

 foreach my $s (keys %ini) {
 while (my ($k,$v) = each %{$ini{$s}}) {
 print("$s $k $v\n");
 }
 }

goes to an infinite loop. This is because every time $ini{$s}
is evaluated, Config::IniFiles::FETCH() creates a new
Config::IniFiles::_section tied hash that has its own each() iterator.

Store and reuse the section hashes instead.

Bug-Debian: https://bugs.debian.org/849298
---
 lib/Config/IniFiles.pm  |  6 +-
 t/35section-iterators.t | 24 
 2 files changed, 29 insertions(+), 1 deletion(-)
 create mode 100644 t/35section-iterators.t

diff --git a/lib/Config/IniFiles.pm b/lib/Config/IniFiles.pm
index 85296e8..817dece 100644
--- a/lib/Config/IniFiles.pm
+++ b/lib/Config/IniFiles.pm
@@ -1841,12 +1841,16 @@ sub FETCH {
   my $self = shift;
   my( $key ) = @_;
 
+  $self->{_section_cache} ||= {};
+
   $self->_caseify(\$key);
   return if (! $self->{v}{$key});
 
+  return $self->{_section_cache}->{$key} if exists $self->{_section_cache}->{$key};
+
   my %retval;
   tie %retval, 'Config::IniFiles::_section', $self, $key;
-  return \%retval;
+  return $self->{_section_cache}->{$key} = \%retval;
 
 } # end FETCH
 
diff --git a/t/35section-iterators.t b/t/35section-iterators.t
new file mode 100644
index 000..54adf7f
--- /dev/null
+++ b/t/35section-iterators.t
@@ -0,0 +1,24 @@
+#!/usr/bin/perl
+
+# See: https://bugs.debian.org/849298
+
+use strict;
+use warnings;
+
+use Test::More tests => 2;
+
+use Config::IniFiles;
+
+my $ini_contents = <<'EOF';
+[foo]
+bar=baz
+rab=zab
+EOF
+
+tie (my %ini, 'Config::IniFiles', -file=>\$ini_contents);
+
+my ($k1,$v1) = each %{$ini{foo}};
+my ($k2,$v2) = each %{$ini{foo}};
+
+isnt($k1, $k2, "got different keys with successive each() calls");
+isnt($v1, $v2, "got different values with successive each() calls");
-- 
2.11.0

Bug#849344: xalan: Support parallel builds

[William Blough]

Source: xalan
Severity: wishlist
Tags: upstream


Parallel builds (such as is the default with debhelper 10) fail due to
missing LocalMsgIndex.hpp.  This file is generated during the "Utils"
build, which is supposed to occur before the "PlatformSupport" build. However,
building in parallel causes this to happen out of order.

To fix this, rework the dependencies in the makefile.



-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
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)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#802018: systemd: _SYSTEMCTL_SKIP_REDIRECT=true is leaked to daemon

[Martin Pitt]

Hello all,

Michael Biebl [2016-12-22  9:21 +0100]: > Am 16.10.2015 um 23:07 schrieb 
Sebastian Schmidt:
> Looking at that old code again, I actually don't remember, why we export
>  _SYSTEMCTL_SKIP_REDIRECT="true" at all and if the obvious fix would be
> to simply drop that else clause.

AFAIK the original intent was that if you call "/etc/init.d/foo start" this
would redirect to "systemctl start" which would run "Exec=/etc/init.d/foo
start" in the generated unit which must not do that same redirection again.

This should be sufficiently covered by the [ $PPID -ne 1 ] test, though. git
archeology shows that commit c04d0f71 introduced the script and both the
SKIP_REDIRECT and the [ $PPID -ne 1 ] were already present, though.

So, I can't think of a good reason to set this either, thanks for dropping it
from master.

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: PGP signature

Bug#836885: Re-add heimdal-multidev?

[Michael Fladischer]

Now that heimdal has some upstream activity again and 7.1.0 has been
uploaded to unstable, is there a chance that openldap will reenable
support for "krb5" in "olcSmbK5PwdEnable"?

Cheers,
Michael

Bug#826214: Bug #826214: Bug #826215: init-d-script and systemd: solution

[Martin Pitt]

Hello Christian,

Christian Seiler [2016-12-25 13:34 +0100]:
> I think I have a solution to both issues - and my solution
> does not require any change to any individual init script,
> and best of all it doesn't even require changes to any
> sysvinit-related package (we get to have our cake and eat
> it too):

Thanks for working on this!

> The systemd package could install a diversion of /lib/init/init-d-script and
> install its own wrapper.

I don't like this approach, to be honest. (1) This diversion would be present
on practically all installs anyway, as it would (necessarily) be in the
"systemd" binary, not the "systemd-sysv" one. (2) I don't want to maintain this
SysV stuff in the systemd package forever, AND still have someone else maintain
the non-diverted variant in sysvinit-utils. I'd much prefer to just change the
"master" copy in sysvinit-utils, and packages which use that should grow a
dependency to that (so that it can become non-essential).

I. e. use your script but patch the current one instead of duplicating it.
If the SysV init maintainers don't want to carry this either, then there's
still the option to just drop the systemd integration, and break calling
/etc/init.d/foo directly under systemd. WDYT?

Thanks,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Bug#818230: Fwd: aircrack-ng: please make the build reproducible

[Reiner Herrmann]

Control: tags -1 + patch

On Sun, Dec 25, 2016 at 11:05:56AM -0200, Samuel Henrique wrote:
> Could you please update the patch to rc4? I would be infinitely grateful :)

Updated patch attached. :)

> Also, i believe you can also send this upstream, but if you don't, i can do
> that for you.

Please send it upstream, thanks!

Regards,
  Reiner
diff --git a/debian/patches/reproducible-build.patch b/debian/patches/reproducible-build.patch
new file mode 100644
index 000..8ef2eae
--- /dev/null
+++ b/debian/patches/reproducible-build.patch
@@ -0,0 +1,28 @@
+--- a/src/Makefile
 b/src/Makefile
+@@ -4,6 +4,7 @@
+ TEST_DIR	= $(AC_ROOT)/test
+ 
+ CFLAGS		+= -Iinclude
++ASFLAGS		+= $(CFLAGS)
+ 
+ iCC		= /opt/intel/bin/icc
+ iCFLAGS		= -w -xHOST $(COMMON_CFLAGS)
+@@ -75,7 +76,7 @@
+ SRC_PTW		= aircrack-ptw-lib.c
+ SRC_AC		= aircrack-ng.c crypto.c common.c $(SSEC_INT) $(SRC_PTW)
+ OBJS_PTW	= aircrack-ptw-lib.o
+-OBJS_AC		= aircrack-ng.o cpuid.o crypto.o common.o $(SSEO_INT) uniqueiv.o $(OBJS_PTW) $(LIBLINECOUNT)
++OBJS_AC		= aircrack-ng.o cpuid.o crypto.o common.o $(SSEO_INT) uniqueiv.o sha1-sse2.o $(OBJS_PTW) $(LIBLINECOUNT)
+ OBJS_AC_MULTI	= crypto.o common.o uniqueiv.o $(OBJS_PTW)
+ ASM_AC		= sha1-sse2.S
+ 
+@@ -170,7 +171,7 @@
+ 	aircrack-ng-opt-prof -lpthread $(LIBSQL)
+ 
+ aircrack-ng$(EXE): $(OBJS_AC)
+-	$(CC) $(CFLAGS) $(LDFLAGS) $(OBJS_AC) $(ASM_AC) -o $(@) -lpthread $(LIBSSL) $(LIBSQL) $(LIBSTDCXX)
++	$(CC) $(CFLAGS) $(LDFLAGS) $(OBJS_AC) -o $(@) -lpthread $(LIBSSL) $(LIBSQL) $(LIBSTDCXX)
+ 
+ ifeq ($(subst TRUE,true,$(filter TRUE true,$(multibin) $(MULTIBIN))),true)
+ wpapsk-simd.o: wpapsk.c
diff --git a/debian/patches/series b/debian/patches/series
index f47153b..57f333a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@
 01_remove_check.patch
 02_bashisms.patch
 03_fix_trap_usage_dash.patch
+reproducible-build.patch

Bug#849342: [xrdp] xrdp-sesman: Fails to start Xorg

[Ben Armstrong]

Package: xrdp
Version: 0.9.1-1
Severity: normal

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

After upgrading to 0.9.1-1, Xorg is no longer started when xrdp-sesman
runs. Downgrading back to xrdp_0.9.1~20161126+git589b29f-1 resolves the
issue.

Here's what is in journalctl -u xrdp-sesman after the failure:

Dec 25 15:49:13 lear xrdp-sesman[15625]: (15625)(-148605184)[INFO ] A 
connection received from ::1 port 49836
Dec 25 15:49:13 lear xrdp-sesman[15625]: (15625)(-148605184)[INFO ] ++ created 
session (access granted): username synrg, ip 0.0.0.0:49658 - socket: 12
Dec 25 15:49:13 lear xrdp-sesman[15625]: (15625)(-148605184)[INFO ] starting 
Xorg session...
Dec 25 15:49:13 lear xrdp-sesman[15625]: (15625)(-148605184)[DEBUG] Closed 
socket 9 (AF_INET6 :: port 5910)
Dec 25 15:49:14 lear xrdp-sesman[15625]: (15625)(-148605184)[DEBUG] Closed 
socket 9 (AF_INET6 :: port 6010)
Dec 25 15:49:14 lear xrdp-sesman[15625]: (15625)(-148605184)[DEBUG] Closed 
socket 9 (AF_INET6 :: port 6210)
Dec 25 15:49:14 lear xrdp-sesman[15630]: (15630)(-148605184)[DEBUG] Closed 
socket 7 (AF_INET6 ::1 port 3350)
Dec 25 15:49:14 lear xrdp-sesman[15625]: (15625)(-148605184)[DEBUG] Closed 
socket 8 (AF_INET6 ::1 port 3350)
Dec 25 15:49:14 lear xrdp-sesman[15632]: (15632)(-148605184)[INFO ] Xorg :10 
-auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
Dec 25 15:49:24 lear xrdp-sesman[15630]: (15630)(-148605184)[ERROR] X server 
for display 10 startup timeout
Dec 25 15:49:24 lear xrdp-sesman[15630]: (15630)(-148605184)[INFO ] starting 
xrdp-sessvc - xpid=15632 - wmpid=15631
Dec 25 15:49:24 lear xrdp-sesman[15631]: (15631)(-148605184)[ERROR] X server 
for display 10 startup timeout
Dec 25 15:49:24 lear xrdp-sesman[15631]: pam_unix(gdm:session): session opened 
for user synrg by (uid=0)
Dec 25 15:49:24 lear xrdp-sesman[15625]: (15625)(-148605184)[INFO ] ++ 
terminated session:  username synrg, display :10.0, session_pid 15630, ip 
0.0.0.0:49658 - socket: 12

I don't see an Xorg log in any of the usual places, so the reason for
the failure is obscure. I confirmed there was no Xorg :10 running before
each test, however. Let me know whatever other info you need and how to
obtain it. The issue is 100% reproducible for me.

I was very much looking forward to this release as I experience a number
of issues with prior releases, including not working with any android
RDP client, which I had hope this would help with:

+ Enables libpainter for clients not supporting drawing orders.
  + Fixes MS RDP client on Android and others.

No open source Android client works with xrdp (key mappings or pointer
or both are broken) and the MS client fails because of the issue the
above changelog entry addresses.

Thanks,
Ben



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

Debian Release: stretch/sid
990 testing lear.edennet
500 unstable lear.edennet
500 sid linux.dropbox.com

--- Package information. ---
Depends (Version) | Installed
==-+-===
adduser | 3.115
lsb-base (>= 3.0-6) | 9.20161125
init-system-helpers (>= 1.18~) | 1.46
libc6 (>= 2.15) |
libfuse2 (>= 2.6) |
libjpeg62-turbo (>= 1.3.1) |
libopus0 (>= 1.1) |
libpam0g (>= 0.99.7.1) |
libssl1.1 (>= 1.1.0) |
libx11-6 |
libxfixes3 |
libxrandr2 |
libc6 (>= 2.15) |
xorg-input-abi-24 |
xorg-video-abi-23 |
xserver-xorg-core (>= 2:1.18.99.901) |


Package Status (Version) | Installed
=-+-===
vnc-server |


Recommends (Version) | Installed
=-+-===
fuse | 2.9.7-1
xorgxrdp | 0.9.1-1
xorg | 1:7.7+18


Suggests (Version) | Installed
-+-===
guacamole |

Bug#849343: ITP: libspecio-library-path-tiny-perl -- Path::Tiny types and coercions for Specio

[Jonas Smedegaard]

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: libspecio-library-path-tiny-perl
  Version : 0.04
  Upstream Author : Dave Rolsky 
* URL : http://metacpan.org/release/Specio-Library-Path-Tiny
* License : Apache-2.0
  Programming Lang: Perl
  Description : Path::Tiny types and coercions for Specio

 Specio::Library::Path::Tiny provides a set of Path::Tiny types and
 coercions for Specio. These types can be used with Moose, Moo,
 Params::ValidationCompiler, and other modules.

Package is needed for recent releases of Code::Tidyall
(libcode-tidyall-perl).

Package will be maintained in the Debian Perl team.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYYBrKAAoJECx8MUbBoAEhpncQAJ6Tv8osV3LJonN7gJyL4LhR
xdjmYFJOD0KricEJWdp82ZfR8fE+5lXPFAIF1cgC8dkKV5zPZ+xy2/6uq1tQJXTw
aY28m05sTHedYD1s5B/f2C1fPf2gqZiTfekPOADXnZizCdbd0jpHW8plSv0km0ia
RgZSrcPubQUkAkYs3isMXPHoPBli1YYJIXObABcSyPJJpKb038GKKbYYBAbU8f75
UqRn8yyfn6hYc4Qhq8l6g4b1XY2g70I0QPYOxX5soyU4G8e6dJNNsg5YOl4sqW1o
6b3/LwZPU0g+MsFlt/GdxTbDFJI0yHW6RcuJ9BT7lVv+rCZoretA+seoRnsfx8G7
IEGTzDDMj+0T/6N5hdZxKsHBwEb6SrEsjer0WCWwQkG4KCC1eSElQ++eCA8rxu24
Jq8FVLroqzPM+3tO/OyQVo3Ol+TCOAZw1+G6IVgIAQxeqKiyNJ3tskLOFjRBnJql
AHaKjtc0Cri6ralUs4YaHJwjlsxjOzRA8n4dqkueB9wEKjq50zRea+vuQjq9Cy76
mygVtcewUK4BYH4McAGqm+m8rAIQCjkAtXU2H94k6AjteUbyi3zBWlOA4jTMRJzm
7jv8kfA5axOR34QZHW9PwjC2uSHgWQ1ExzZVskh8Rcd/gSSUg3pNnjldhoTwdVNo
ySF3/5DLhpS2DumIIwAi
=zoEW
-END PGP SIGNATURE-

Bug#849341: ITP: libtext-hogan-perl -- mustache templating engine statement-for-statement cloned from hogan.js

[Jonas Smedegaard]

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: libtext-hogan-perl
  Version : 1.04
  Upstream Author : Alex Balhatchet 
* URL : https://metacpan.org/release/Text-Hogan
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : mustache templating engine statement-for-statement cloned 
from hogan.js

 Text::Hogan is a statement-for-statement rewrite of hogan.js in Perl.
 .
 It is a mustache templating engine which supports pre-compilation of
 your templates into pure Perl code, which then renders very quickly.
 .
 It passes the full mustache spec.

Package is needed for recent releases of Catmandu (libcatmandu-perl).

Package will be maintained in the Debian Perl team.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYX/E9AAoJECx8MUbBoAEh4OgP/1Nm8FHUrilWeWfkOvAnko2/
6xraIkvqGoqqfrlfZ4jFJSW+1dynXX7LiTQTEZWu/9/2xoT6bgTnEX7jwcjLu/LO
dzc63O0F6wsCBevfQPq0A9uoPIigV5N/hvRm1Sj3Nhc0ZyT4i0AWvHt/QTYQB/z9
OrFLYGyIpoMaHy1svBZf0ME9a5HVwg3vY+BIGonWbWYlSvt1pGyzHjM8zmh9UhRD
QUQST9ph8HGNTOAhr5Va6IF4TLCYeYnAvzawDMy3qJtZScYb+pq+xsl0du6dg0c9
DORrytmPqhyFXXRPxnCupzSDdywfzLp7XnnzmlV8uD+FoC+JfssR8TN6JmjPjNfo
Yhcn8uP/YliJKXKkG85K9B6f6RzUAZZm1TwUwIONnlGi9AY4xLxABAEZOGYoF5wy
0U2fHltFU1S1utRUxMdwdS5DTmpZTJG7lAxJsMv8NuiLvrZCcWe18DSgjW3J7/4z
frPO/2oo4+bUaa52jn6IGL9sZiWIe+bMs2R6KLpI43VxwuseMtaXnQQDzinFB7Wq
UF5TbtvdCKGpZkzYESFwk3vfnDTqqpCnaTkJkI3CK5FAgHxwAxX79gISld5oEXAG
6/k6GphTdHiwEXDUWjo1Ky6mdIxhqQiOrJojoaCcjunO7NRGRNefi1fYRoFZN7hf
Q3ENhL1llceCQ2tQT880
=kQth
-END PGP SIGNATURE-

Bug#849340: ITP: libterm-table-perl -- module to format a header and rows into a table

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libterm-table-perl
  Version : 0.004
  Upstream Author : Chad Granum 
* URL : https://metacpan.org/release/Term-Table
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : module to format a header and rows into a table

The Term::Table module is able to generic format rows of data into tables.
This is used in test suites by some failing tests to provide diagnostics
about what has gone wrong but can also be used in all kinds of other
contexts.

The package will be maintained under the umbrella of the Debian Perl Group.


signature.asc
Description: Digital Signature

Bug#848298: [Pkg-mongodb-maintainers] Bug#848298: mongodb: Build for s390x

[Jeremy Bicha]

Merry Christmas!

On Sun, Dec 25, 2016 at 10:05 AM, László Böszörményi (GCS)
 wrote:
>  Just for the record, Apollon packaged 3.4.1-3 and it just compiled on
> s390x in experimental.

3.4.1-2 built fine for s390x on Launchpad for Ubuntu:

https://launchpad.net/ubuntu/+source/mongodb/1:3.4.1-2/

So I tried without disabling hardware crc32 on s390x. It built but
crashed when it tried to run the tests.

https://launchpad.net/ubuntu/+source/mongodb/1:3.4.1-2ubuntu2

(I had the same build problem with arm64 with 1:3.4.1-1)

Attached are the changes I made if you want to apply them in Debian.
In the second patch, I went ahead and left hardware crc32 disabled on
s390x even on Ubuntu, but I showed how we could turn it on if we
wanted to. I think the s390x patch could be submitted upstream.

Thank you,
Jeremy Bicha


0002-Use-a-configure-flag-to-disable-hardware-crc32-on-s3.patch
Description: Binary data


0001-Split-arm64-and-s390x-patches.patch
Description: Binary data

Bug#835437: Seems fixed

[Barry Warsaw]

On Dec 25, 2016, at 05:49 PM, Santiago Vila wrote:

>The bug I reported said FTBFS. After the tests are disabled, this builds
>ok again, so the FTBFS problem I reported is fixed.

Thanks.  If you're happy closing this bug, then so am I!  I'll just clarify
that I didn't actually disable the tests; they were already disabled, in the
sense that the exit code of the failing build-time tests were already
explicitly ignored in the d/rules target.

>Well, I would like, but after building version 7.43.0-2 one hundred
>times the locale problem does not happen anymore.

Cool.


pgpTOFI8wHHG4.pgp
Description: OpenPGP digital signature

Bug#849339: xcolorsel: FTBFS on hppa - conflicting HP compiler options

[John David Anglin]

Package: xcolorsel
Version: 1.1a-20
Severity: normal
Tags: patch

Dear Maintainer,

The build fails here:
gcc -g -O2 -fdebug-prefix-map=/<>=. -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Aa 
-D_HPUX_SOURCE-Dlinux -D__hppa__ -D_POSIX_C_SOURCE=199309L  
-D_POSIX_SOURCE -D_XOPEN_SOURCE 
-D_BSD_SOURCE -D_SVID_SOURCE 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  
 -DFUNCPROTO=15 -DNARROWPROTO
-DHELPFILE=\"/usr/lib/X11/xcolorsel/Xcolorsel.help\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -o RgbText.o RgbText.c
:0:1: error: missing '(' after predicate
In file included from /usr/include/stdio.h:27:0,
 from RgbText.c:77:

This error is caused by the HP compiler option '-Aa'.

Full log is here:
https://buildd.debian.org/status/fetch.php?pkg=xcolorsel=hppa=1.1a-20=1482455899

The HP options are added by Imakefile.  Build is successful with the attached
patch.

Regards,
Dave Anglin

-- System Information:
Debian Release: stretch/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.9.0+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- Imakefile.save  2016-12-25 13:50:49.166869105 -0500
+++ Imakefile   2016-12-22 21:10:25.409482294 -0500
@@ -50,8 +50,10 @@
 /* Please add any preprocessor defines in config.h */
 
 #ifdef HPArchitecture
+#ifndef __GNUC__
 CCOPTIONS = -Aa -D_HPUX_SOURCE
 #endif
+#endif
 
 XPALDIR = $(LIBDIR)/xcolorsel
 HELPFILE = $(XPALDIR)/Xcolorsel.help

Bug#776800: X server crashes when switching to another user

[Richard B. Kreckel]

As of stretch, with the nvidia-driver 375.20 and Xorg 1.19 this problem
has disappeared.

Bug#847288: libdbd-firebird-perl: FTBFS randomly (failing tests)

[Santiago Vila]

Ok, I made the following test today: Built this package 1000 times,
on 20 different autobuilders.

It built ok this many times in these autobuilders:

  67 uranio2
  58 uranio1
  53 e5
  53 e12
  48 leaseweb2
  48 leaseweb1
  47 e16
  35 e14
  34 e4
  34 e17
  34 e10
  32 e11
  30 e20
  28 e18

and it failed to build this many times in these autobuilders:

  65 e8
  65 e6
  64 e3
  61 e7
  52 yoda2
  50 yoda1
  50 skywalker1
   2 uranio2

Now the fun part: The machines on which it fails are the "fast" ones,
and the machines on which it builds ok are the "slow" ones.

I have good estimations for the CPU speed for these machines.

This is the "slowness" of the machines on which it fails to build:

e6   0.413
e8   0.413
e3   0.417
e7   0.417
yoda10.418
yoda20.429
skywalker1   0.446
uranio2  0.540

and this is the "slowness" of the machines on which it builds ok:

e12  0.526
e5   0.540
uranio2  0.540
e16  0.646
uranio1  0.734
e14  1.528
e17  1.537
e10  1.545
e11  1.558
e4   1.573
e18  1.977
e20  2.074

The "slowness" is the inverse of the speed. My unit of measure
(i.e. slowness 1) is the speed of my i3-3217U @ 1.80GHz at home,
which was my first autobuilder.

Can you host a virtual machine somewhere which is at least twice as
fast as my i3 at home? I guess, but I'm not sure, that the problem
could be reproduced there as well.

[ Of course, if we can confirm that speed is the issue here, this should
  be "serious" again, as packages should never fail to build just because
  the CPU is "too fast" ].

Thanks.

Bug#849337: get-iplayer: podcast mode has stopped working

[Axel]

Package: get-iplayer
Version: 2.94-1
Severity: normal

Dear Maintainer,

Programmes of type podcast cannot be downloaded at all anymore.

- The PID field, which used to contain the download URI ending in a media 
extension like
  ‘.mp3’, now ends in a file name without any extension and points to an HTML 
page
  containing a choice of download URIs.

- While attempting to download the programme, the following messages appear:

  Matches:
  203170: podcast, BBC Proms Music Guide - Strauss - Heldenleben, Wed, 08 Aug 
2012 00:00:00 +, BBC Radio 3, Music

  INFO: 1 Matching Programmes
  INFO: Checking existence of default version
  INFO: podcast modes will be tried for version default
  INFO: Trying podcast mode to record podcast: BBC Proms Music Guide - Strauss 
- Heldenleben
  INFO: File name prefix = 
BBC_Proms_Music_Guide_-_Strauss_-_Heldenleben_http://www.bbc.co.uk/programmes/p02r7nl4
  ERROR: Cannot write or append to 
/home/axel/Downloads/BBC/BBC_Proms_Music_Guide_-_Strauss_-_Heldenleben_http:/www.bbc.co.uk/programmes/p02r7nl4.partial.http:/www.bbc.co.uk/programmes/p02r7nl4

- This happens for all podcast-type download attempts, no matter whether Get I 
Player is
  called with the PID (e.g., ‘p02r7nl4’) or with the programme index (203170).

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

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

Versions of packages get-iplayer depends on:
ii  libwww-perl 6.08-1
ii  libxml-simple-perl  2.20-1
ii  perl5.20.2-3+deb8u6
ii  rtmpdump2.4+20150115.gita107cef-1

Versions of packages get-iplayer recommends:
ii  atomicparsley 0.9.2~svn110-4
ii  id3v2 0.1.12-2.1
ii  libmp3-info-perl  1.24-1

Versions of packages get-iplayer suggests:
ii  libav-tools 6:11.8-1~deb8u1
ii  mplayer2 [mplayer]  2.0-728-g2c378c7-4+b1

-- no debconf information

Bug#849338: ITP: hxtools -- Collection of tools and scripts

[Jochen Sprickerhof]

Package: wnpp
Severity: wishlist
Owner: Jochen Sprickerhof 

* Package name: hxtools
  Version : 20150304
  Upstream Author : Jan Engelhardt 
* URL : http://inai.de/projects/hxtools/
* License : GPL, LGPL, WTFPL
  Programming Lang: C, Perl, Bash
  Description : Collection of tools and scripts

 A collection of tools and scripts that have accumulated over the years, and
 each of which seems to be too small to warrants its own project.
 .
  * bsvplay(1) - convert BASICA music files to PCM
  * cctypeinfo(1) - show sizes of C types on the implementation it was compiled 
with
  * checkbrack(1) - check parenthesis and bracket count
  * cwdiff(1) - run wdiff with color
  * declone(1) - break hardlinks
  * diff2php(1) - transform patch to self-serving PHP file
  * doxygen-kerneldoc-filter(1) - filter for Doxygen to support kerneldoc
  * extract_d3pkg(1) - extract Descent3 PKG files
  * extract_dxhog(1) - extract Descent HOG files
  * extract_f3pod(1) - extract Fury3 POD files
  * extract_qupak(1) - extract Quake2 PACK files
  * fd0ssh(1) - pipe for password-over-stdin support to ssh
  * fduphl(1) - find duplicate files and hardlink them
  * filenameconv(1) - convert file name encoding
  * flv2avi(1) - repackage Flash video into an AVI container with PCM audio
  * fnt2bdf(1) - convert VGA raw fonts to X11 BDF
  * fxterm(1) - start xterm with sane settings
  * git-author-stat(1) - show commit author statistics of a git repository
  * git-blame-stat(1) - show per-line author statistics of a git repository
  * git-export-patch(1) - produce perfect patch from git commits for mail 
submission
  * git-forest(1) - display the commit history forest
  * git-lemon(1) - don't just pick cherries, but take it all (cherry-pick a 
commit range)
  * git-new-root(1) - start a new root in the git history
  * git-revert-stats(1) - show reverting statistics of a git repository
  * git-track(1) - set up branch for tracking a remote
  * gpsh(1) - grep in tracklists and play audio files
  * graph-fanout(1) - fan a tree (for graphviz)
  * graph-lchain(1) - remove circles in graphs using longest-chaining method
  * logontime(8) - show cumulative logon time from wtmp
  * mailsplit(1) - split an mbox into single files
  * man2html(1) - convert nroff manpages to HTML
  * mod2ogg(1) - wrapper for module to OggVorbis transcoding
  * mpg2ogg(1) - wrapper for mass mp3 to OggVorbis transcoding
  * netload(8) - show utilization of network interface
  * newns(8) - clone current filesystem namespace and start a process
  * ofl(1) - open file lister (replaces fuser and lsof -m)
  * omixer(1) - volume control using the OSS Sound API
  * oplay(1) - raw PCM playback using the OSS Sound API
  * orec(1) - raw PCM recording using the OSS Sound API
  * paddrspacesize(1) - print size of processes' address spaces
  * pesubst(1) - perl-regexp stream substitution (replaces sed for 
sub-stitutions)
  * pmap_dirty(1) - display amount of RAM a process uses hard
  * png2wx.pl(1) - transform arbitrary files into C++ files for wxWidgets
  * printcaps(1) - print currently active process capabilities
  * proc_iomem_count(1) - show MMIO region sizes
  * proc_stat_signal(1) - decode /proc/self/stat for signal status
  * pshtreads(1) - alternative experiment to ps(1) involving thread display
  * qplay(1) - convert QBASIC play strings to PCM
  * qtar(1) - faster interface to tar with file ordering
  * raregetty(8) - local login program for remote hosts
  * recursive_lower(1) - recursively lowercase all filenames
  * rpmdep.pl(1) - read RPM dependencies and output a graph
  * sourcefuncsize(1) - statistical analysis of code
  * spec-beautifier(1) - program to clean up RPM .spec files
  * stxdb(1) - A/V file database
  * su1(8) - what sudo should have done
  * sysinfo(1) - print IRC-style system information banner
  * tailhex(1) - hex dumper with tail-following support
  * utmp_register(1) - make entries in the utmp/wtmp database
  * vcsaview(8) - display a screen dump in VCSA format
  * vfontas(1) - VGA font file assembler
  * wavdiff(1) - proof-of-concept raw PCM deltifier
  * wktimer(1) - work timer
  * xcp(1) - proof-of-concept cp(1) with alternate copying mechanisms
  * xfs_irecover(1) - recover lost inodes from XFS filesystems.

This package is used by the libpam-mount package (currently patched in).
I've created an initial version on collab-maint:

https://anonscm.debian.org/cgit/collab-maint/hxtools.git

Bug#828525: qupzilla: diff for NMU version 1.8.9~dfsg1-3.1

[Georges Khaznadar]

Thank you very much, Andrey!

Andrey Rahmatullin a écrit :
> 
> 
> Dear maintainer,
> 
> I've prepared an NMU for qupzilla (versioned as 1.8.9~dfsg1-3.1). The diff
> is attached to this message.
> 
> Regards.
> 
> -- 
> WBR, wRAR

> diff -Nru qupzilla-1.8.9~dfsg1/debian/changelog 
> qupzilla-1.8.9~dfsg1/debian/changelog
> --- qupzilla-1.8.9~dfsg1/debian/changelog 2016-01-23 20:42:31.0 
> +0500
> +++ qupzilla-1.8.9~dfsg1/debian/changelog 2016-12-18 20:22:33.0 
> +0500
> @@ -1,3 +1,10 @@
> +qupzilla (1.8.9~dfsg1-3.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Build with OpenSSL 1.0 (Closes: #828525).
> +
> + -- Andrey Rahmatullin   Sun, 18 Dec 2016 20:22:33 +0500
> +
>  qupzilla (1.8.9~dfsg1-3) unstable; urgency=medium
>  
>* removed the dependency on libqt5xcbqpa5. Closes: #812233
> diff -Nru qupzilla-1.8.9~dfsg1/debian/control 
> qupzilla-1.8.9~dfsg1/debian/control
> --- qupzilla-1.8.9~dfsg1/debian/control   2016-01-23 20:42:16.0 
> +0500
> +++ qupzilla-1.8.9~dfsg1/debian/control   2016-12-18 20:22:33.0 
> +0500
> @@ -7,7 +7,7 @@
>   qtbase5-private-dev, qtscript5-dev,
>   libqt5x11extras5-dev,
>   libx11-dev,
> - libssl-dev, kdelibs5-dev, libgnome-keyring-dev,
> + libssl1.0-dev | libssl-dev (<< 1.1.0~), kdelibs5-dev, libgnome-keyring-dev,
>   libjs-jquery, libjs-jquery-ui
>  Standards-Version: 3.9.7
>  Homepage: http://www.qupzilla.com/





signature.asc
Description: PGP signature

Bug#692293: sbox declared with conflicting sizes

[Samuel Henrique]

Control: tag -1 + pending

Fix commited.


Samuel Henrique 

Bug#849336: fence-agents: accesses the internet during build

[Chris Lamb]

Source: fence-agents
Version: 4.0.24-1
Severity: important
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst fence-agents builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

   00:00:00.00 IP 13e5ab701260.48959 > OpenWrt.lan.domain: 54700+ A? 
test.lan. (26)
   00:00:00.94 IP 13e5ab701260.48959 > OpenWrt.lan.domain: 45382+ ? 
test.lan. (26)
   00:00:00.011205 IP OpenWrt.lan.domain > 13e5ab701260.48959: 54700 NXDomain 
0/0/0 (26)
   00:00:00.176930 IP OpenWrt.lan.domain > 13e5ab701260.48959: 45382 NXDomain 
0/0/0 (26)
   00:00:00.177185 IP 13e5ab701260.54706 > OpenWrt.lan.domain: 40406+ A? 
test.chris-lamb.co.uk. (39)
   00:00:00.177282 IP 13e5ab701260.54706 > OpenWrt.lan.domain: 12927+ ? 
test.chris-lamb.co.uk. (39)
   00:00:00.460181 IP OpenWrt.lan.domain > 13e5ab701260.54706: 40406 1/0/0 A 
92.242.132.15 (55)
   00:00:00.460199 IP OpenWrt.lan.domain > 13e5ab701260.54706: 12927 0/0/0 (39)
   00:00:00.460580 IP 13e5ab701260.42582 > unallocated.barefruit.co.uk.http: 
Flags [S], seq 1343347188, win 29200, options [mss 1460,sackOK,TS val 135398169 
ecr 0,nop,wscale 7], length 0
   00:00:00.726838 IP unallocated.barefruit.co.uk.http > 13e5ab701260.42582: 
Flags [S.], seq 2820189304, ack 1343347189, win 13480, options [mss 
1360,sackOK,TS val 2161112508 ecr 135398169,nop,wscale 7], length 0

  [..]

The full build log (including tcpdump output) is attached.


Regards,

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


fence-agents.4.0.24-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#849334: [dnscrypt-proxy] dnscrypt-proxy fails to start due to incorrect configuration path on systemd service file

[Ximo Baldó i Soriano]

Package: dnscrypt-proxy
Version: 1.8.1-3
Severity: serious

--- Please enter the report below this line. ---
Since last upgrade, Dnscrypt fails to start due search configuration file at 
path that does 
not exist.

Service file (/lib/systemd/system/dnscrypt-proxy.service) has incorrect path on 
Exec line:
ExecStart=/usr/sbin/dnscrypt-proxy /etc/dnscrypt-proxy/dnscrypt-proxy.conf

and, on my system, since last update dnscrypt-proxy.conf is located at 
/etc/dnscrypt-proxy/dnscrypt-proxy.conf/dnscrypt-proxy.conf


Service file after update:

[Unit]
Description=DNSCrypt client proxy Documentation=man:dnscrypt-proxy(8) 
Requires=dnscrypt-proxy.socket After=network.target Before=nss-lookup.target 

[Install] Also=dnscrypt-proxy.socket WantedBy=multi-user.target 

[Service] Type=notify NonBlocking=true User=_dnscrypt-proxy ExecStart=/usr/sbin/
dnscrypt-proxy /etc/dnscrypt-proxy/dnscrypt-proxy.conf Restart=always 
ProtectSystem=strict ProtectHome=true ProtectKernelModules=true 
ProtectKernelTunables=true ProtectControlGroups=true 
MemoryDenyWriteExecute=true 
RestrictRealtime=true




Directory structure on disk:

~$ tree /etc/dnscrypt-proxy/
/etc/dnscrypt-proxy/└── dnscrypt-proxy.conf   └── dnscrypt-proxy.conf



Modifying incorrect path on systemd service file or moving config file to path 
in systemd 
service file makes dnscrypt work correctly again.

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

Debian Release: stretch/sid
  950 unstablewww.deb-multimedia.org 
  900 unstable-debug  deb.debian.org 
  900 unstableftp.debian.org 
  800 experimentalftp.debian.org 
  500 stable  people.debian.org 
 
--- Package information. ---
Depends   (Version) | Installed
===-+-
adduser | 3.115
lsb-base (>= 3.0-6) | 9.20161125
init-system-helpers  (>= 1.18~) | 1.46
libc6 (>= 2.17) | 
libltdl7 (>= 2.4.6) | 
libsodium18 (>= 1.0.10) | 
libsystemd0 | 


Package's Recommends field is empty.

Suggests(Version) | Installed
=-+-===
resolvconf| 




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

Bug#849335: Support keyfile-size, keyfile-offset in cryptroot

[schaarsc]

Package: cryptsetup
Version: 2:1.7.3-3
Tags: patch


Debian supports keyscript, systemd does not. Using keyscript for the root 
device results either in
delays during boot or (sometimes) in boot errors.
Someone suggested to use devices + keyfile-size, keyfile-offset [1] instead.
However, the cryptroot hook does not pass those options to initramfs. 
Please consider adding keyfile-size, keyfile-offset to the supported options.


[1] 
https://wiki.debianforum.de/Cryptsetup_mit_systemd_und_Schlüssel_auf_externem_USB-Stick


--- /tmp/cryptsetup_1.7.3-3/lib/cryptsetup/cryptdisks.functions	2016-12-09 01:18:17.0 +0100
+++ /lib/cryptsetup/cryptdisks.functions	2016-12-25 19:02:23.179147532 +0100
@@ -203,6 +203,20 @@
 			fi
 			LUKSPARAMS="$LUKSPARAMS --key-slot $VALUE"
 			;;
+		keyfile-size)
+			if [ -z "$VALUE" ]; then
+log_warning_msg "$dst: no value for keyfile-size option, skipping"
+return 1
+			fi
+			LUKSPARAMS="$LUKSPARAMS --keyfile-size $VALUE"
+			;;
+		keyfile-offset)
+			if [ -z "$VALUE" ]; then
+log_warning_msg "$dst: no value for keyfile-offset option, skipping"
+return 1
+			fi
+			LUKSPARAMS="$LUKSPARAMS --keyfile-offset $VALUE"
+			;;
 		tcrypthidden)
 			TCRYPTPARAMS="$TCRYPTPARAMS --tcrypt-hidden"
 			;;
@@ -213,7 +227,7 @@
 
 		CRYPTTAB_OPTIONS="$CRYPTTAB_OPTIONS $PARAM"
 		[ -z "$VALUE" ] && VALUE="yes"
-		eval export CRYPTTAB_OPTION_$PARAM="\"$VALUE\""
+		eval export CRYPTTAB_OPTION_$(echo $PARAM | sed 's/-/_/g')="\"$VALUE\""
 	done
 	export CRYPTTAB_OPTIONS
 
--- /tmp/cryptsetup_1.7.3-3/usr/share/initramfs-tools/hooks/cryptroot	2016-12-09 01:18:17.0 +0100
+++ /usr/share/initramfs-tools/hooks/cryptroot	2016-12-25 19:03:12.954987653 +0100
@@ -444,8 +444,15 @@
 			resumedev)
 OPTIONS="$OPTIONS,$opt"
 ;;
+			keyfile-size=*)
+OPTIONS="$OPTIONS,$opt"
+;;
+			keyfile-offset=*)
+OPTIONS="$OPTIONS,$opt"
+;;
 			*)
 # Presumably a non-supported option
+echo "option not supported: $opt" >&2
 ;;
 		esac
 	done
@@ -473,25 +480,33 @@
 key="/cryptroot-keyfiles/${target}.key"
 ;;
 			*)
-key=$(readlink -e "$key")
+# only resolve sym-links for files, not for disks
+if [ "$key" = "${key%/dev/disk/*}" ] ; then
+	key=$(readlink -e "$key")
+fi
 # test whether $target is a root device (or parent of the root device)
 if printf '%s' "$OPTIONS" | grep -Eq '^(.*,)?rootdev(,.*)?$'; then
-	echo "cryptsetup: WARNING: root target $target uses a key file, skipped" >&2
-	return 1
+	if [ "$key" = "${key%/dev/disk/*}" ] ; then
+		echo "cryptsetup: WARNING: root target $target uses a key file, skipped" >&2
+		return 1
+	else
+		echo "cryptsetup: NOTE: root target $target uses a device, $key" >&2 
+	fi
 # test whether a) key file is not on root fs
 #   or b) root fs is not encrypted
 elif [ "$(stat -c %m -- "$key" 2>/dev/null)" != / ] || ! node_or_pv_is_in_crypttab $rootdevs; then
 	echo "cryptsetup: WARNING: $target's key file $key is not on an encrypted root FS, skipped" >&2
 	return 1
+else
+	if printf '%s' "$OPTIONS" | grep -Eq '^(.*,)?resumedev(,.*)?$'; then
+		# we'll be able to decrypt the device, but won't be able to use it for resuming
+		echo "cryptsetup: WARNING: resume device $source uses a key file" >&2
+	fi
+	# prepend "/root" (to be substituted by the real root FS
+	# mountpoint "$rootmnt" in the boot script) to the
+	# absolute filename
+	key="/root$key"
 fi
-if printf '%s' "$OPTIONS" | grep -Eq '^(.*,)?resumedev(,.*)?$'; then
-	# we'll be able to decrypt the device, but won't be able to use it for resuming
-	echo "cryptsetup: WARNING: resume device $source uses a key file" >&2
-fi
-# prepend "/root" (to be substituted by the real root FS
-# mountpoint "$rootmnt" in the boot script) to the
-# absolute filename
-key="/root$key"
 ;;
 		esac
 		OPTIONS="$OPTIONS,keyscript=cat"
--- /tmp/cryptsetup_1.7.3-3/usr/share/initramfs-tools/scripts/local-top/cryptroot	2016-12-09 01:18:17.0 +0100
+++ /usr/share/initramfs-tools/scripts/local-top/cryptroot	2016-12-25 19:07:16.661745962 +0100
@@ -70,6 +70,8 @@
 	cryptkeyscript=""
 	cryptkey="" # This is only used as an argument to an eventual keyscript
 	cryptkeyslot=""
+	cryptkeyfilesize=""
+	cryptkeyfileoffset=""
 	crypttries=3
 	crypttcrypt=""
 	cryptveracrypt=""
@@ -124,6 +126,12 @@
 		keyslot=*)
 			cryptkeyslot=${x#keyslot=}
 			;;
+		keyfile-size=*)
+			cryptkeyfilesize=${x#keyfile-size=}
+			;;
+		keyfile-offset=*)
+			cryptkeyfileoffset=${x#keyfile-offset=}
+			;;
 		tries=*)
 			crypttries="${x#tries=}"
 			case "$crypttries" in
@@ -152,7 +160,7 @@
 			VALUE="${x#*=}"
 		fi
 		CRYPTTAB_OPTIONS="$CRYPTTAB_OPTIONS $PARAM"
-		eval export CRYPTTAB_OPTION_$PARAM="\"$VALUE\""
+		eval export CRYPTTAB_OPTION_$(echo $PARAM | sed 's/-/_/g')="\"$VALUE\""
 	done
 	export CRYPTTAB_OPTIONS
 
@@ -288,6 +296,12 @@
 	if [ -n "$cryptkeyslot" 

Bug#846002: blends-tasks must not be priority:important (was Re: Bug#846002: Lowering severity)

[Philip Hands]

Cyril Brulebois  writes:

> Philip Hands  (2016-12-24):
>> OK, this is tiresome -- you're complaining about question marks when I
>> was still exploring the options and looking for feedback -- I could
>> instead have been definite about an earlier option, but that would
>> have deprived you of choices, and would not have resulted in a patch
>> as good as it is now.
>> 
>> Please don't punish me for being open about my feelings on the various
>> commits because if you do that you'll reap the whirlwind when people
>> start lying to you to get past your superficial metrics.
>
> My initial comments weren't about those.

I've no idea what you mean by that sentence really, but it's possible
that it renders the rest of this mail totally irrelevant, so feel free
to clarify in that case.

> But they indeed add up with
> what I mentioned earlier, and this tends to confirm that december,
> with a freeze already started, is just not the right time to start
> exploring options.
>
> Sorry, but my mind is made up here: it's just too late (1) to change
> tasksel entirely, (2) to require translation updates we're already not
> getting in time, be it for screens, and for the installation guide.
>
> I'll stop repeating myself here, and start enjoying festivities.

Just in case there was any doubt, I have no problem with the decision
that this is all too late -- it was clear that might well be the outcome
when I started this, so I'm not surprised.

I was just concerned that you might be basing that decision on some
false perceptions.

Now that I've had chance to check, it seems that there was just one
commit with a question mark in the commit message:

  "move the task lists into the template (to make it preseedable?)"
  http://deb.li/3maqd

which was only there to remind me to check if I could find a way of
preseeding the Choices-C: value (seems not, BTW).

It also happens to be the commit where the '; then' was missing (which I
guess would be the obvious syntax errors you mention).

Perhaps you saw that commit being present from 09:28 on Dec 20th and
only being fixed at 22:07 on Dec 22nd and thought I was being totally
rubbish.

In fact, the reason I pushed that on the morning of the 20th was because
I knew I was going to be busy all day and wanted jenkins to also be busy
testing for me while I was out.

Of course, when I came back, I discovered that by then d-i FTBFS because
of the dejavu rename, so then I spent some time fixing that (leaving the
broken commit in place even longer).

So, if you are judging this negatively on the basis of that commit, then
you are failing to understand that the reason you saw that commit was
because I was attempting to get jenkins to do some testing for me while
I didn't have time to do it myself -- which is rather the point of
jenkins.

The reason it stayed there so long unfixed with its question mark was
because of the dejavu rename FTBFS.

I do not point this out in an attempt to change your decision in this
particular case, but rather to point out that it makes little sense to
be overly judgemental about such a commit.

The reason I've been putting effort into jenkins is so that people
(myself in particular) should be able to throw commits at jenkins and
have them tested without worrying too much about whether they are
perfect.  The hope being that this would lower the bar for contributions
by letting people play in safety while getting decent feedback about
whether their efforts were producing viable results.

Frowning at people when they then use that system for its designed
purpose seems just a tad counter productive.

Anyway, no hard feelings, and I hope you're having fun :-)

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#849333: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

[Chris Lamb]

tags 849333 + patch
thanks

Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/faker/providers/ssn/fi_FI/__init__.py 
b/faker/providers/ssn/fi_FI/__init__.py
index 44d9ff3..bba2c0b 100644
--- a/faker/providers/ssn/fi_FI/__init__.py
+++ b/faker/providers/ssn/fi_FI/__init__.py
@@ -39,7 +39,7 @@ class Provider(SsnProvider):
 if birthday.year < 2000:
 separator = '-'
 else:
-separator += 'A'
+separator = 'A'
 suffix = str(random.randrange(2, 899)).zfill(3)
 checksum = _checksum(hetu_date + suffix)
 hetu = "".join([hetu_date, separator, suffix, checksum])

Bug#849333: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

[Chris Lamb]

forwarded 849333 https://github.com/joke2k/faker/pull/441
thanks

I've forwarded this upstream here:

   https://github.com/joke2k/faker/pull/441


Regards,

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

Bug#849333: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

[Chris Lamb]

Source: faker
Version: 0.7.7-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

faker's testsuite appears to non-deterministically vary in behaviour,
causing a FTBFS when it exposes a programming error:

  […]

  ==
  ERROR: test_documentor (faker.tests.FactoryTestCase)
  --
  Traceback (most recent call last):
File "faker/tests/__init__.py", line 207, in test_documentor
  print_doc(output=output)
File "faker/cli.py", line 110, in print_doc
  excludes=base_provider_formatters):
File "faker/documentor.py", line 32, in get_formatters
  (provider, self.get_provider_formatters(provider, **kwargs))
File "faker/documentor.py", line 87, in get_provider_formatters
  example = self.generator.format(name)
File "faker/generator.py", line 66, in format
  return self.get_formatter(formatter)(*args, **kwargs)
File "faker/providers/profile/__init__.py", line 47, in profile
  "ssn": self.generator.ssn(),
File "faker/providers/ssn/fi_FI/__init__.py", line 42, in ssn
  separator += 'A'
  UnboundLocalError: local variable 'separator' referenced before assignment
  
  --
  Ran 45 tests in 2.150s
  
  FAILED (errors=1)
  debian/rules:27: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:10: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


faker.0.7.7-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#849296: [Pkg-samba-maint] Bug#849296: libsmbclient-dev: Incorrect version (0.2.1 instead of 4.2.14) in pkgconfig/smbclient.pc

[Konstantin Gribov]

Sorry folks, I take it back.

They are exposing ABI version instead of Samba version, so Debian
`libsmbclient-dev` is perfectly OK.
Issue can be closed. I'll take care of that on my side and will look for
ways to improve it in Samba docs.

вс, 25 дек. 2016 г. в 19:52, Mathieu Parent :

> Control: tag -1 + moreinfo
> Control: severity -1 normal
>
> 2016-12-24 23:31 GMT+01:00 Konstantin Gribov :
> > Package: libsmbclient-dev
> > Version: 2:4.2.14+dfsg-0+deb8u2
> > Severity: important
> >
> > Hello, Debian maintainers.
>
> Hello,
>
> >
> > -- Steps to reproduce:
> > $ apt-get install -y libsmbclient-dev pkg-config
> > $ pkg-config --cflags --libs 'smbclient >= 4.0'
> > Requested 'smbclient >= 4.0' but version of smbclient is 0.2.1
> > You may find new versions of smbclient at http://www.samba.org/
> > $ pkg-config --modversion smbclient
> > 0.2.1
>
> What do you want to do (what is your intention)? Here we behave like
> upstream.
>
> Regards
> --
> Mathieu Parent
>
-- 

Best regards,
Konstantin Gribov

Bug#800546: guymager: please add arm64

[Samuel Henrique]

Hello Michael,

Have you seen this bugreport?

I think we should change guymager to Architecture: any and see in which
architectures it doesn't builds.

I can prepare an upload to experimental for test purposes if you want.

Regards,

Samuel Henrique 

Bug#835268: hashrat: Please enable support for filesystem Extended Attributes

[Samuel Henrique]

Hello Giovani,

Did you give a look a this one?

I think we could enable xattr on experimental and see if it breaks build on
the other architectures (actually, other kernels).

I can do that if you want.

Samuel Henrique 

Bug#844707: plasma-workspace: plasmadesktop - excessive cpu usage, slow desktop operation

[Manas]

Hello,

I am experiencing this issue too.

Related links:
https://bugs.kde.org/show_bug.cgi?id=356479
https://phabricator.kde.org/D2986
https://forum.kde.org/viewtopic.php?f=289=135019=369331#p369331

This is a major issue on laptops when running on the battery.
Any kind of animation in the System Tray causes 'plasmashell --shut-up' to 
consume 100% CPU.

I am running 'Linux 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02) x86_64 
GNU/Linux' and 'plasma-workspace' version 4:5.8.2-1

Bug#849332: ITP: auto-resize-image -- Resizer for inline and attachment images (thunderbird)

[Christoph Biedl]

Package: wnpp
Severity: wishlist
Owner: Christoph Biedl 

* Package name: auto-resize-image
  Version : 0.14.3-tb
  Upstream Author : TrVTrV 

* URL : 
https://addons.mozilla.org/en-US/thunderbird/addon/auto-resize-image/
* License : GPL2+
  Programming Lang: XUL
  Description : Resizer for inline and attachment images (thunderbird)


Tentative long description:

 Auto Resize Image is a Thunderbird add-on which allows one to resize
 inline and attached images while composing email messages.
 .
 The main purpose is to:
  - reduce size of image files
  - give the image convenient dimensions for it to be visible directly
in email client without using scrollbars.

Personally, I'm a bit surprised this very useful tool does not exist in
Debian yet - or did I just not see it?

Additionally, my main interest is to have this plugin in Debian - while
I'm not particularily keen on maintaining it. So if anybody else wishes
to do this, perhaps under the pkg-mozext umbrella, just let me know.

Christoph



signature.asc
Description: Digital signature

Bug#849331: fails to build with linux-rt kernel

[YD]

Package: spl-dkms
Version: 0.6.5.8-2
Severity: normal

Build fails during compilation of spl-rwlock:

 CC [M]  /var/lib/dkms/spl/0.6.5.8/build/module/splat/splat-thread.o
In file included from 
/usr/src/linux-headers-4.8.0-2-common-rt/include/linux/spinlock.h:290:0,
from 
/usr/src/linux-headers-4.8.0-2-common-rt/include/linux/seqlock.h:35,
from 
/usr/src/linux-headers-4.8.0-2-common-rt/include/linux/time.h:5,
from 
/usr/src/linux-headers-4.8.0-2-common-rt/include/linux/stat.h:18,
from 
/usr/src/linux-headers-4.8.0-2-common-rt/include/linux/module.h:10,
from /var/lib/dkms/spl/0.6.5.8/build/include/sys/sysmacros.h:28,
from /var/lib/dkms/spl/0.6.5.8/build/include/sys/types.h:29,
from /var/lib/dkms/spl/0.6.5.8/build/include/sys/rwlock.h:28,
from /var/lib/dkms/spl/0.6.5.8/build/module/spl/spl-rwlock.c:27:
/var/lib/dkms/spl/0.6.5.8/build/include/sys/rwlock.h: In function 
‘spl_rw_set_owner’:
/var/lib/dkms/spl/0.6.5.8/build/include/sys/rwlock.h:55:41: error: ‘struct rw_semaphore’ has no 
member named ‘wait_lock’

spl_rwsem_lock_irqsave((rwp)->wait_lock, flags);
^
/usr/src/linux-headers-4.8.0-2-common-rt/include/linux/spinlock_rt.h:45:40: note: in definition of  
macro ‘spin_lock’   
#define spin_lock(lock)   rt_spin_lock(lock)
   ^ 
/var/lib/dkms/spl/0.6.5.8/build/include/linux/rwsem_compat.h:55:46: note: in expansion of macro 
‘spin_lock_irqsave’

#define spl_rwsem_lock_irqsave(lk, fl)   spin_lock_irqsave(lk, fl)
 ^
/var/lib/dkms/spl/0.6.5.8/build/include/sys/rwlock.h:55:9: note: in expansion of macro  
‘spl_rwsem_lock_irqsave’

spl_rwsem_lock_irqsave((rwp)->wait_lock, flags);
^


and so on.


-- System Information:
Debian Release: stretch/sid
 APT prefers unstable
 APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages spl-dkms depends on:
ii  dkms  2.3-1
ii  file  1:5.29-2
ii  libc6-dev [libc-dev]  2.24-8
ii  lsb-release   9.20161125

Versions of packages spl-dkms recommends:
pn  spl  

spl-dkms suggests no packages.

Bug#849330: firmware-iwlwifi: intel 8260 does not work when using modfile /lib/firmware/iwlwifi-8000C-22.ucode and kernel 4.8

[Jon Parker]

Package: firmware-iwlwifi
Version: 20161130-2
Severity: important

Hello Maintainer,

Using a laptop with an intel 8260 wifi chip (HP Zbook 15 G3) and linux kernel 
4.8, wifi does not work.
This is a known problem; see https://bugs.archlinux.org/task/51271

It looks like the answer is that the debian package does not contain the latest 
fixes.

I can fix the problem by following the directions in the website link given 
above:
- copy / move /lib/firmware/iwlwifi-8000C-22.ucode, and the kernel will then 
use /lib/firmware/iwlwifi-8000C-21.ucode, which works.

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/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)

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.125

-- no debconf information

Bug#849288: [Pkg-zsh-devel] Bug#849288: Bug#849288: zsh-dev: installing config.h breaks reproducibility (followup to #776964)

[Daniel Shahaf]

Control: retitle -1 zsh-dev: installs header files containing declarations of 
non-"mod_export" functions (followup to #776964)

Axel Beckert wrote on Sun, Dec 25, 2016 at 17:17:36 +0100:
> Both issues are about zsh-dev not being reproducibly if once /bin/sh
> is dash and once bash.
> 
> One issue (upstream) is about fixing configure.ac, Makefile.am so that
> this no more happens.
> 
> The other issue (this Debian bug report) is about whether we want to
> continue to differ from upstream wrt. the inclusion of config.h in the
> zsh-dev package.

Yes.  This issue is not just about config.h, actually; it's about how
the package installs _all_ *.h and *.epro files, without making
a distinction between what's an interface between core and modules, and
what's an intra-core interface.  ("intraface"?)

For functions, the distinction is easy: only functions that are tagged
"mod_export" should be used by modules, however, zsh-dev installs
prototypes of other functions as well, such as findpwd().  That function
is defined with external linkage (= without the "static" keyword), but
without the "mod_export" annotation, meaning that modules that #include
/usr/include/zsh/utils.epro will be able to call findpwd(), even though
upstream does not consider that function a public/stable API.

For preprocessor macros and type definitions there is no equivalent of
the "mod_export" explicit scoping tag, however, we have no reason to
believe that every single #define and typedef shared between different
*.c files of zsh core, is blessed for use by modules.  We shouldn't
install #define's and type definitions that upstream has not
specifically blessed as an interface between modules and core.

> Obviously the following actions would resolve this Debian bug report
> (#849288):
> 
> * Upstream changes its code to install config.h as well.
> * We stop shipping config.h. That would reopen #776964.

To be clear, these options are mutually exclusive, not cumulative.

And they refer not just to config.h but in general, to all header files
(*.h, *.epro) that are installed by zsh-dev v. by upstream.

> But what I currently plan to do is to use the patch from
> http://www.zsh.org/mla/workers/2016/msg02716.html and hence make
> zsh-dev reproducible again without having decided on the config.h
> inclusion discusssion.

+1, and thanks.  I'll push it upstream soon.

> Would that action close this issue, too, or not? Because if zsh-dev
> becomes reproducible, this is mere a "we differ from upstream" issue,
> nothing more and not really a bug anymore, at most a wishlist item.

Making zsh-dev reproducible would not close this issue.  This issue is
about the divergence from upstream: since zsh-dev.deb installs headers
upstream does not, users of zsh-dev could rely on interfaces that
upstream does not bless for usage by modules.  (Such as findpwd())

Apologies for not giving these details and concrete example earlier;
that might have been clearer.  I've retitled this bug to clarify its
scope.

Cheers,

Daniel

Bug#849329: unblock: gnutls28/3.5.7-3

[Andreas Metzler]

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

Hello,

please speed up propagation of gnutls28 3.5.7-3 to testing. This is a
single-bugfix upload for #848905.

* 35_01_pkcs8-ensure-that-the-correct-error-code-is-returned.patch,
  35_02_tests-added-test-for-PKCS-8-encrypted-key-decoding.patch from
  upstream 3.5 branch: Ensure that GNUTLS_E_DECRYPTION_FAIL will be returned
  by PKCS#8 decryption functions when an invalid key is provided. This
  addresses regression on decrypting certain PKCS#8 keys.
  Closes: #848905

unblock gnutls28/3.5.7-3

Thanks in advance, cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .changes but not in first
-
-rw-r--r--  root/root   /usr/lib/debug/.build-id/06/92627b5d607063eb71903a721233f5901066e9.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/1e/16d3b5f659ca4250cdd1a4cf9709b8b85f53fb.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/1f/32a0a57aec655b07964a5d98497e025cae7262.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/2b/a9be2c2eb381dc4edf836d798e59bdb361412c.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/52/67bd611b093a4b73120b2b5d283543e88df4bd.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/5f/5a02703e99f9e428a82aa80b90688b13f756b8.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/7c/e5a5afbd26492c200471e1c2ba705e922b8c55.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/8f/0f41e04edf62b0a7808b48ea52470517c48b9a.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/9a/ddeb34b9f349ee50037cd28d46fc5c9112c6fe.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/c1/ead7f61001838e6d88ff1cd74ac74e22c469f4.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/c2/f5f35a3622da6852d137d9610c9f94e44e4e67.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/c5/ed28d817ac7aaf9d6a0aa028f34f13e57f7a45.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/e5/412e005b4e94b4cc8270a540bb3db74af67b19.debug

Files in first .changes but not in second
-
-rw-r--r--  root/root   /usr/lib/debug/.build-id/1e/e95a5dada2caafea18c6fb0a31662eaf74fd1b.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/25/49b7cc772d8fd074de0be00f0619db53bee1f1.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/39/bb37cbf9a096e7455e8799ee146f31942120d3.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/49/42f0c0688463070e6410365999f7a60d5bde23.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/85/be5dbc76bf55586a82cf140ae0f179b516acaf.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/97/c2ab04e6f0fa0d5ac7bf71e0e34c86fc3f3d6d.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/99/d619c6678ed0f956097d75c33cc897caf31647.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/9d/6f39cb57ee78768fb728e590d19669272f0816.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/a7/2a600aee19233e265d10b0e78447a952cb822c.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/b3/d24cdffab087bfe7d2b92c235a98d7ab0b91c8.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/cd/b980046cd934ff2b0fedb5235e56484dcfadcd.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/d5/48d9fedb88409e1a5f3e025a2d6eeae871fafd.debug
-rw-r--r--  root/root   /usr/lib/debug/.build-id/d7/b94bc8d9b61dbb6da08afe0c08294819fe7bda.debug

Control files of package gnutls-bin: lines which differ (wdiff format)
--
Version: [-3.5.7-2-] {+3.5.7-3+}

Control files of package gnutls-bin-dbgsym: lines which differ (wdiff format)
-
Build-Ids: [-1ee95a5dada2caafea18c6fb0a31662eaf74fd1b 39bb37cbf9a096e7455e8799ee146f31942120d3 85be5dbc76bf55586a82cf140ae0f179b516acaf 97c2ab04e6f0fa0d5ac7bf71e0e34c86fc3f3d6d 99d619c6678ed0f956097d75c33cc897caf31647 a72a600aee19233e265d10b0e78447a952cb822c b3d24cdffab087bfe7d2b92c235a98d7ab0b91c8 d548d9fedb88409e1a5f3e025a2d6eeae871fafd d7b94bc8d9b61dbb6da08afe0c08294819fe7bda-] {+1e16d3b5f659ca4250cdd1a4cf9709b8b85f53fb 1f32a0a57aec655b07964a5d98497e025cae7262 2ba9be2c2eb381dc4edf836d798e59bdb361412c 5267bd611b093a4b73120b2b5d283543e88df4bd 5f5a02703e99f9e428a82aa80b90688b13f756b8 7ce5a5afbd26492c200471e1c2ba705e922b8c55 8f0f41e04edf62b0a7808b48ea52470517c48b9a c2f5f35a3622da6852d137d9610c9f94e44e4e67 e5412e005b4e94b4cc8270a540bb3db74af67b19+}
Depends: gnutls-bin (= [-3.5.7-2)-] {+3.5.7-3)+}
Installed-Size: [-991-] {+992+}
Version: [-3.5.7-2-] {+3.5.7-3+}

Control files of package gnutls-doc: lines which differ (wdiff format)
--
Version: [-3.5.7-2-] {+3.5.7-3+}

Control files of package 

Bug#849326: [Pkg-kde-extras] Bug#849326: [amarok] Collection is disabled due to failing MySQL operation (errmsg.sys) at startup

[Pino Toscano]

Hi,

In data domenica 25 dicembre 2016 16:51:23 CET, Alex Dănilă ha scritto:
> Package: amarok
> Version: 2.8.0-7
> Severity: important
> 
> --- Please enter the report below this line. ---
> After upgrading everything from Testing to Unstable, Amarok cannot use 
> the music collection anymore. An error related to the MySQL error type 
> version is displayed at startup:
> 
> GREPME MySQLe query failed! (2000) Error message file 
> '/usr/share/kde4/apps/amarok/mysqle/errmsg.sys' had only 969 error 
> messages, but it should contain at least 982 error messages.
> Check that the above file is the right version for this program! on init
> In most cases you will need to resolve these errors before Amarok will 
> run properly.
> 
> Amarok is able to play music, but all features related to the collection 
> are gone.
> 
> --- System information. ---

Unfortunately, this part (system information) does not provide the
versions of packages... please paste it from the output of
  $ reportbug --template amarok

Thanks,
-- 
Pino Toscano

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

Bug#849296: [Pkg-samba-maint] Bug#849296: libsmbclient-dev: Incorrect version (0.2.1 instead of 4.2.14) in pkgconfig/smbclient.pc

[Mathieu Parent]

Control: tag -1 + moreinfo
Control: severity -1 normal

2016-12-24 23:31 GMT+01:00 Konstantin Gribov :
> Package: libsmbclient-dev
> Version: 2:4.2.14+dfsg-0+deb8u2
> Severity: important
>
> Hello, Debian maintainers.

Hello,

>
> -- Steps to reproduce:
> $ apt-get install -y libsmbclient-dev pkg-config
> $ pkg-config --cflags --libs 'smbclient >= 4.0'
> Requested 'smbclient >= 4.0' but version of smbclient is 0.2.1
> You may find new versions of smbclient at http://www.samba.org/
> $ pkg-config --modversion smbclient
> 0.2.1

What do you want to do (what is your intention)? Here we behave like upstream.

Regards
-- 
Mathieu Parent

Bug#829661: Sorry for not closing the ceph security reports properly

[Salvatore Bonaccorso]

Hi Gaudenz,

Thanks for your reply!

On Sat, Dec 24, 2016 at 01:19:20PM +0100, Gaudenz Steinlin wrote:
> 
> Hi Salvatore
> 
> Thanks for closing these bugs and sorry for not closing these properly.
> I'm currently the only one left on the "Ceph maintainers team" and so my
> top priority was to at least get something uploaded and through new.
> Thus I forgot to check all the bug reports to see which ones were closed
> with the new upstream release. Sorry for that and sorry for making the
> life of the security harder than necessary.

Thanks a lot for the expalantion. I have to admint, my first
impression was that the mails to the (moderated) list do not really go
trough.

> Which of the bugs do you think also warant an upload to stable?

My gut feeling is that none of those would really warrant a DSA, but
I'm Cc'ing the team on that matter, since I'm not too familiar with
ceph itself. As such, and since the jessie point release is already
scheduled for 14th of january, it would be great to see those fixed in
stable via a jessie-pu upload.

Thanks for your work on ceph, and apologies if my initial mail might
have been taken grumpy.

Salvatore

Bug#835437: Seems fixed

[Santiago Vila]

Version: 7.43.0-2

On Thu, 15 Dec 2016, Barry Warsaw wrote:

> I can't reproduce the build failures reported here even with dpkg-buildpackage
> -A.  However, I am going to add the discard-port proxies to d/rules that
> pybuild normally adds by default (this package doesn't use pybuild).  That at
> least will prevent the tests from *actually* hitting the internet.  I'll close
> #830281 against that change.
> 
> Yes, this makes the test suite fail during package build.  I have reported
> this upstream at https://github.com/pycurl/pycurl/issues/424
> 
> However note that d/rules currently discards test suite errors, so they don't
> prevent the build from succeeding.  This makes running the tests semi-useless
> but I think until upstream fixes their test suite, it's the best we can do.
> Therefore I'm going to tag this bug as unreproducible and reduce the
> severity.

I'll apreciate that you want to keep this open on the basis that "not
everything that was reported is fixed yet", but I'm not really happy
with this solution.

The bug I reported said FTBFS. After the tests are disabled, this builds
ok again, so the FTBFS problem I reported is fixed.

So, I prefer to close this one to better track the FTBFS bugs I report.

> I also can't reproduce the C locale problem, but I'm going to consider that a
> separate bug so please file a new one on that issue.

Well, I would like, but after building version 7.43.0-2 one hundred
times the locale problem does not happen anymore.

Thanks.

Bug#849212: msgpuck: CVE-2016-9036: Invalid handling of map16 format in mp_check()

[Salvatore Bonaccorso]

Hi Roman,

On Sat, Dec 24, 2016 at 12:03:16PM +0300, Roman Tsisyk wrote:
> 
> 
> 
> >Friday, December 23, 2016 7:09 PM +03:00 from Salvatore Bonaccorso 
> >:
> >
> >Source: msgpuck
> >Version: 1.0.3-1
> >Severity: important
> >Tags: security upstream
> >Forwarded:  https://github.com/rtsisyk/msgpuck/issues/12
> >
> >Hi,
> >
> >the following vulnerability was published for msgpuck.
> >
> >CVE-2016-9036[0]:
> >Invalid handling of map16 format in mp_check()
> >
> >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-2016-9036
> > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9036
> >[1]  https://github.com/rtsisyk/msgpuck/issues/12
> >[2]  http://www.talosintelligence.com/reports/TALOS-2016-0254/
> >
> 
> I already prepared a fix for this bug [1].
> 
> [1]: https://github.com/rtsisyk/msgpuck/blob/master/debian/changelog#L5
> 
> The package is waiting for uploading, I'm not DD.
> I added Dmitry E. Oboukhov to CC.

Alright, thanks a lot!

Regards,
Salvatore

Bug#849284: insserv: fopen(/etc/insserv.conf): No such file or directory

[積丹尼 Dan Jacobson]

I'll send you the whole apt log when I get back to town where it is, Jan. 15.

Bug#849288: [Pkg-zsh-devel] Bug#849288: zsh-dev: installing config.h breaks reproducibility (followup to #776964)

[Axel Beckert]

Hi again,

Axel Beckert wrote:
> Daniel Shahaf wrote:
> > The patch I sent upstream removes dead code in order to make zsh-dev.deb
> > reproducible.
> > 
> > This bug is about divergence from upstream (debian installs config.h but
> > upstream does not).  The divergence has not been addressed either
> > upstream or in the downstream package.
> 
> Ok, they're both about reproducibility, but indeed not the same issue.

Well, no, I'm slightly confused: They're about the same issue, but
from different points of view:

Both issues are about zsh-dev not being reproducibly if once /bin/sh
is dash and once bash.

One issue (upstream) is about fixing configure.ac, Makefile.am so that
this no more happens.

The other issue (this Debian bug report) is about whether we want to
continue to differ from upstream wrt. the inclusion of config.h in the
zsh-dev package.

Obviously the following actions would resolve this Debian bug report
(#849288):

* Upstream changes its code to install config.h as well.
* We stop shipping config.h. That would reopen #776964.

But what I currently plan to do is to use the patch from
http://www.zsh.org/mla/workers/2016/msg02716.html and hence make
zsh-dev reproducible again without having decided on the config.h
inclusion discusssion.

Would that action close this issue, too, or not? Because if zsh-dev
becomes reproducible, this is mere a "we differ from upstream" issue,
nothing more and not really a bug anymore, at most a wishlist item.

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

Bug#849328: outputs absolute source path in output

[Jelmer Vernooij]

Source: cython
Version: 0.25.2~b0-2
Severity: normal
Tags: upstream

cython encodes the path of the source cython path of the module it compiles in
its output.

It would be useful if it was possible to generate output that can be compiled
into bit-for-bit reproducible binaries.

E.g. 
static const char __pyx_k_home_jelmer_src_bzr_unstable_bz[] = 
"/home/jelmer/src/bzr/unstable/bzrlib/_annotator_pyx.pyx";

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

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

Bug#823241: unhide: please make the build reproducible (fileordering)

[Samuel Henrique]

​Control: tag -1 + pending

Fix commited to git, version 20130526-2 will fix/close this bug.​

Thanks for the patch!

Samuel Henrique 

Bug#849284: insserv: fopen(/etc/insserv.conf): No such file or directory

[Petter Reinholdtsen]

[積丹尼 Dan Jacobson]
> First I installed a fresh Debian testing system from a USB stick.
> The stick was only 300 MB big and only needed to go online to get the
> current time to set the clock.
> Then I installed aptitude.
> Then I installed the rest of the packages by
> # aptitude install package1 package2 ... package777
> My point is there are many different orders one could install packages,
> all legal, and it would be good to do some checks in order not to
> have the administrator see these warnings.

While I agree, I need more details to try to reproduce this.  What where
the names of the 777 packages?  As far as I know, the situation you
described should only happen when installing insserv and next remove its
configuration, so I need more information on what to do see the problem
myself.

--
Happy hacking
Petter Reinholdtsen

Bug#848941: gbp pq import can give different results to dpkg-source

[Ian Jackson]

Guido Günther writes ("Re: Bug#848941: gbp pq import can give different results 
to dpkg-source"):
> control: retitle -1 git-apply patches different file than patch
> control: reassign -1 git
> control: affects -1 git-buildpackage

How exciting!  Thanks for investigating.

Ian.