Bug#852163: python3.5-minimal wont configure

[Gary Roach]

Package: python3.5-minimal
Version: 3.5.3~rc1-1
OS: Debian Stretch 64 bit
Kde Desktop

Three different mirror sites gave the same results.

Aptitude and apt-get consistantly give the following:

Setting up python3.5-minimal (3.5.3~rc1-1) ...
Traceback (most recent call last):
  File "/usr/lib/python3.5/py_compile.py", line 6, in 
import importlib._bootstrap_external
  File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
import types
  File "/usr/lib/python3.5/types.py", line 166, in 
import functools as _functools
  File "/usr/lib/python3.5/functools.py", line 23, in 
from weakref import WeakKeyDictionary
  File "/usr/lib/python3.5/weakref.py", line 12, in 
from _weakref import (
ImportError: cannot import name '_remove_dead_weakref'
dpkg: error processing package python3.5-minimal (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python3.5:
 python3.5 depends on python3.5-minimal (= 3.5.3~rc1-1); however:
  Package python3.5-minimal is not configured yet.

dpkg: error processing package python3.5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3-numpy:
 python3-numpy depends on python3.5:any; however:
  Package python3.5 is not configured yet.

dpkg: error processing package python3-numpy (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3.5-venv:
 python3.5-venv depends on python3.5 (= 3.5.3~rc1-1); however:
  Package python3.5 is not configured yet.

dpkg: error processing package python3.5-venv (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3.5-dev:
 python3.5-dev depends on python3.5 (= 3.5.3~rc1-1); however:
  Package python3.5 is not configured yet.

dpkg: error processing package python3.5-dev (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 python3.5-minimal
 python3.5
 python3-numpy
 python3.5-venv
 python3.5-dev
E: Sub-process /usr/bin/dpkg returned an error code (1)

Since all the packages depend on python3.5-minimal I attempted to force 
a rebuild of its dependancies with "aptitude build-dep python3.5-minimal

" with the following results:

root@supercrunch:/etc# aptitude build-dep python3.5-minimal
The following packages will be REMOVED:
  libkf5config-bin{u} libkf5dbusaddons-bin{u} libkf5iconthemes-bin{u}
  liblircclient0{u} libraptor1{u}
The following partially installed packages will be configured:
  python3-numpy python3.5 python3.5-dev python3.5-minimal python3.5-venv
0 packages upgraded, 0 newly installed, 5 to remove and 41 not upgraded.
Need to get 0 B of archives. After unpacking 766 kB will be freed.
Do you want to continue? [Y/n/?]
(Reading database ... 462079 files and directories currently installed.)
Removing libkf5config-bin (5.28.0-1) ...
Removing libkf5dbusaddons-bin (5.28.0-1) ...
Removing libkf5iconthemes-bin (5.28.0-1) ...
Removing liblircclient0 (0.9.4c-7) ...
Removing libraptor1:amd64 (1.4.21-11+b1) ...
Setting up python3.5-minimal (3.5.3~rc1-1) ...
Traceback (most recent call last):
  File "/usr/lib/python3.5/py_compile.py", line 6, in 
import importlib._bootstrap_external
  File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
import types
  File "/usr/lib/python3.5/types.py", line 166, in 
import functools as _functools
  File "/usr/lib/python3.5/functools.py", line 23, in 
from weakref import WeakKeyDictionary
  File "/usr/lib/python3.5/weakref.py", line 12, in 
from _weakref import (
ImportError: cannot import name '_remove_dead_weakref'
dpkg: error processing package python3.5-minimal (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python3.5:
 python3.5 depends on python3.5-minimal (= 3.5.3~rc1-1); however:
  Package python3.5-minimal is not configured yet.

dpkg: error processing package python3.5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3-numpy:
 python3-numpy depends on python3.5:any; however:
  Package python3.5 is not configured yet.

dpkg: error processing package python3-numpy (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3.5-venv:
 python3.5-venv depends on python3.5 (= 3.5.3~rc1-1); however:
  Package python3.5 is not configured yet.

dpkg: error processing package python3.5-venv (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3.5-dev:
 python3.5-dev depends on python3.5 (= 3.5.3~rc1-1); however:
  Package python3.5 is not configured yet.

dpkg: error processing package python3.5-dev (--configure):
 dependency problems - leaving unconfigured
Errors were 

Bug#852162: libkscreenlocker5: cannot enter password when two mirrored monitors are connected

[Dominik George]

Package: libkscreenlocker5
Version: 5.8.4-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

[ If this is the wrong package, please reassign the bug, thanks ☺! ]

When I have two monitors connected and they are set up to share the same
picture, the password input field in the lock screen stops accepting
input. No characters I type make it to the input field and hitting the
Enter key tries a login with an empty password.

Most excitingly, the input seems to make it “somewhere”, because
everything I entered is sent to the input field at once when I unplug
one of the monitors.

The issue does not happen when the monitors are set up to extend the
desktop to the left or right, only when the picture is mirrored.

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

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

Versions of packages libkscreenlocker5 depends on:
ii  kpackagetool5 5.28.1-1
ii  libc6 2.24-9
ii  libkf5configcore5 5.28.0-1
ii  libkf5configgui5  5.28.0-1
ii  libkf5coreaddons5 5.28.0-1
ii  libkf5crash5  5.28.0-1
ii  libkf5declarative55.28.0-1
ii  libkf5globalaccel55.28.0-1
ii  libkf5i18n5   5.28.0-1
ii  libkf5idletime5   5.28.0-1
ii  libkf5notifications5  5.28.0-1
ii  libkf5package55.28.1-1
ii  libkf5quickaddons55.28.0-1
ii  libkf5waylandclient5  4:5.28.0-1
ii  libkf5waylandserver5  4:5.28.0-1
ii  libkf5windowsystem5   5.28.0-1
ii  libpam0g  1.1.8-3.5
ii  libqt5core5a  5.7.1+dfsg-3
ii  libqt5dbus5   5.7.1+dfsg-3
ii  libqt5gui55.7.1+dfsg-3
ii  libqt5network55.7.1+dfsg-3
ii  libqt5qml55.7.1-2
ii  libqt5quick5  5.7.1-2
ii  libqt5widgets55.7.1+dfsg-3
ii  libqt5x11extras5  5.7.1~20161021-2
ii  libstdc++66.3.0-3
ii  libwayland-client01.12.0-1
ii  libwayland-server01.12.0-1
ii  libx11-6  2:1.6.4-2
ii  libxcb-keysyms1   0.4.0-1
ii  libxcb1   1.12-1
ii  libxi62:1.7.8-2

Versions of packages libkscreenlocker5 recommends:
ii  kde-config-screenlocker  5.8.4-1

libkscreenlocker5 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAliEY0MxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pbXnxAA2dbWCrYXtq5LyABcREE7SSxy8Rz0
Wq+lVpu082lMybIDB/+iUTTuY9k6n6PkIGRWga5pt1ccwp/iZashPW2kVG7FrlGa
FqBvxvhTHCu+5Ecdu9DFGZ5PkS7+jymNfeZnOhsQmxsKrUZWYr3KE7zuaZUfC/oG
ZOeNH8MC+JLjJUlZoBTvdMfzVdHRt5sCY/FZRS8TzzXNbFACeRonyosk5ECTotKb
Pdo7Fy7C8muceCrRlzrcOKsEKNh5W3Ucm+ADRhkqVukSoZEZsZpkVa4Gy2YKLmSM
j98KFHGSKy7RXYvwzCGEDgnjBt+lYpwPJiQwrBdIeA4sZNhhv0QgitT50QO2EQhO
uN46teO8ks3VAa9NXOux6kiOt0WRpHLLOKiZ9bpC+68wYmaze9Va786uoojE1Y/y
w20YUuEhgQsodaiCEI+4zlNliOZollroLoP/wc7yRpgaLzEBxLFZ5p47i/4BkmF8
QnpVTA2sovMZKAYL8QE0tZ549DGNey+idl4DQNvndVN59BBoKA2OPKWrssfEJhGZ
kl8LF45px9T5+yCDLfk2EjMhxZO0Se8nOtbgLpfKd/cfefbMJq1TMmCQWO8DtWqn
/sQ4RwgRIV48YtMWbpEcrHBovGqzmrdY4TBwU6881iFm3ViGV0Vv1tsZPP6/E6oF
qAiXHCSlXkSt+Mc=
=jh0Y
-END PGP SIGNATURE-

Bug#851946: Depending on libssl1.0-dev breaks PHP builds

[Niels Thykier]

Sebastian Andrzej Siewior:
> On 2017-01-20 21:36:00 [+], Niels Thykier wrote:
>> Hi Ondřej,
>>
>> Sorry for being the "messenger" triggering this issue in php7.0.
>>
>> Kurt/Sebastian, what are you recommendations here?  Should we migrate
>> net-snmp itself to ssl1.1 (possibly with all of its rdeps) or can we
>> detangle net-snmp and php7 from each other in a graceful manner?
> 
> [...] I grep the deps [0] and didn't find a user of
> cert_util.h so it looks like nobody cares about that.
> 

Thanks. :)

Codesearch also appears to agree with this (assuming we are only looking
at rdeps). :)  Internally, snmp appears to have a few uses of it.

> I would suggest to drop the the libssl1.0-dev dep in libsnmp-dev and add
> a guard cert_util.h to ensure openssl's version is less than 1.1.0 in
> case someone tries to use this on its own.

The header file is used internally by snmp, so this change implies
upgrading snmp to ssl1.1.  All in all, we need to:

 * Apply the patch in #828449

 * Remove "libssl1.0-dev | libssl-dev (<< 1.1)" from Depends and add a
   "libssl-dev" to Suggests in the the "-dev" package?

 * Add an "#if"-guard rejecting ssl1.0 in the cert_util.h file.
   (Can you provide me with an example/patch for the guard?)

> I will try to make that change tomorrow and rebuild the packages [0].
> 
> [...]

Thanks.  Let me know how it goes.  I am happy to do the upload if your
test says go and you can provide me with the "#if"-guard.  (apparently,
net-snmp also needs an unrelated patch for pie - see #852023)


Thanks,
~Niels

Bug#852077: [src:libint2] What about packaging basisset definition files?

[Katsuhiko Nishimra]

Sorry, there was an oversight in the previous patch.

I'm attaching a fixed patch.

Best regards,
Katsuhiko
diff -Nru libint2-2.3.0~beta3/debian/changelog 
libint2-2.3.0~beta3/debian/changelog
--- libint2-2.3.0~beta3/debian/changelog2017-01-21 04:40:07.0 
+0900
+++ libint2-2.3.0~beta3/debian/changelog2017-01-22 02:50:14.0 
+0900
@@ -1,3 +1,22 @@
+libint2 (2.3.0~beta3-2+basisset1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix debian/patches/no_convenience_copy.patch
+
+ -- Katsuhiko Nishimra   Sun, 22 Jan 2017 02:50:14 +0900
+
+libint2 (2.3.0~beta3-2+basisset0) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install basisset definition files via libint2-data package.
+  * Install document files from the upstream.
+  * Respect DEB_BUILD_OPTIONS=parallel.
+  * Avoid using convenience copy from boost.
+  * debian/watch: Scan the upstream github repository.
+  * Fix comma separated file list in the debian/copyright file.
+
+ -- Katsuhiko Nishimra   Sat, 21 Jan 2017 15:31:07 +0900
+
 libint2 (2.3.0~beta3-2) unstable; urgency=medium
 
   * Upload to unstable. 
diff -Nru libint2-2.3.0~beta3/debian/control libint2-2.3.0~beta3/debian/control
--- libint2-2.3.0~beta3/debian/control  2016-10-02 06:37:03.0 +0900
+++ libint2-2.3.0~beta3/debian/control  2017-01-21 18:30:11.0 +0900
@@ -14,6 +14,7 @@
 Section: libs
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
+Recommends: libint2-data (=${binary:Version})
 Description: Computation Chemistry Integral Evaluation Library
  The LIBINT library is used to evaluate the traditional (electron repulsion)
  and certain novel two-body matrix elements (integrals) over Cartesian
@@ -34,7 +35,7 @@
 Package: libint2-dev
 Section: libdevel
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libint2-2 (= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, libint2-2 (= ${binary:Version}), 
libboost-dev
 Description: Computation Chemistry Integral Evaluation Library (development 
files)
  The Libint2 library is used to evaluate the traditional (electron 
  repulsion) and certain novel two-body matrix elements (integrals) over
@@ -51,3 +52,24 @@
  doubles (CCSD) method, as well as explicitly correlated R12 methods.
  .
  This package contains the static library and header files.
+
+Package: libint2-data
+Architecture: all
+Depends: ${misc:Depends}
+Recommends: libint2-2 (= ${binary:Version})
+Description: Computation Chemistry Integral Evaluation Library (data files)
+ The Libint2 library is used to evaluate the traditional (electron 
+ repulsion) and certain novel two-body matrix elements (integrals) over
+ Cartesian Gaussian functions used in modern atomic and molecular
+ theory.  The idea of the library is to let computer write optimized
+ code for computing such integrals. There are two primary advantages to
+ this: much less human effort is required to write code for computing
+ new integrals, and code can be optimized specifically for a particular
+ computer architecture (e.g., vector processor).
+ .
+ Libint2 has been utilized to implement methods such as Hartree-Fock
+ (HF) and Kohn-Sham density functional theory (KS DFT), second-order
+ Moeller-Plesset perturbation theory (MP2), coupled cluster singles and
+ doubles (CCSD) method, as well as explicitly correlated R12 methods.
+ .
+ This package contains basis set definition files.
diff -Nru libint2-2.3.0~beta3/debian/copyright 
libint2-2.3.0~beta3/debian/copyright
--- libint2-2.3.0~beta3/debian/copyright2015-09-02 21:30:13.0 
+0900
+++ libint2-2.3.0~beta3/debian/copyright2017-01-21 19:04:14.0 
+0900
@@ -10,7 +10,7 @@
 Copyright: Curtis Janssen
 License: GPL-2+
 
-Files: include/util_types.h, tests/*
+Files: include/util_types.h tests/*
 Copyright: 2004-2014 Edward F. Valeev
 License: GPL-2+
 
diff -Nru libint2-2.3.0~beta3/debian/libint2-2.docs 
libint2-2.3.0~beta3/debian/libint2-2.docs
--- libint2-2.3.0~beta3/debian/libint2-2.docs   1970-01-01 09:00:00.0 
+0900
+++ libint2-2.3.0~beta3/debian/libint2-2.docs   2017-01-21 15:29:11.0 
+0900
@@ -0,0 +1,2 @@
+CITATION
+README.md
diff -Nru libint2-2.3.0~beta3/debian/libint2-data.install 
libint2-2.3.0~beta3/debian/libint2-data.install
--- libint2-2.3.0~beta3/debian/libint2-data.install 1970-01-01 
09:00:00.0 +0900
+++ libint2-2.3.0~beta3/debian/libint2-data.install 2017-01-21 
15:29:11.0 +0900
@@ -0,0 +1 @@
+usr/share/libint/*/basis/*.g94
diff -Nru libint2-2.3.0~beta3/debian/libint2-data.lintian-overrides 
libint2-2.3.0~beta3/debian/libint2-data.lintian-overrides
--- libint2-2.3.0~beta3/debian/libint2-data.lintian-overrides   1970-01-01 
09:00:00.0 +0900
+++ libint2-2.3.0~beta3/debian/libint2-data.lintian-overrides   2017-01-21 
17:49:09.0 +0900
@@ -0,0 +1,2 @@
+libint2-data: file-name-contains-wildcard-character 

Bug#261415: network installation always asks for proxy

[Josh Triplett]

On Fri, 28 Feb 2014 23:49:59 +0100 Cyril Brulebois  wrote:
> Martin Pitt  (2004-03-24):
> > - network installation always asks for proxy; I know what a proxy is,
> >   but not all potential users may; would it be possible to try without
> >   proxy first and ask for proxy settings only if direct connection
> >   does not work?  Never mind if that is not possible, just asking :-)
> 
> Some translations have a less-techy way of explaining what a proxy is,
> and a default empty value should just be OK (people are expected to
> install Debian by pressing Enter most of the time, right? :)). I'm not
> sure we want to play with trial-and-error in d-i too much…
> 
> Tagging wontfix for now to allow for somebody to step up and say
> otherwise.

I do think we ought to attempt autodetection for this.  As long as a
means exists for preseeders and expert installs to specify one anyway
(for optional caching proxies), autodetecting by default seems like a
good idea, to eliminate one of the more highly technical questions in
the install.

Bug#852161: ytnef-tools: no manual pages for ytnef, ytnefprint

[Arthur Marsh]

Package: ytnef-tools
Version: 1.9-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

I installed the package, looked at the installed binaries and
couldn't find manual page entries for them.

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

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


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

Kernel: Linux 4.10.0-rc4+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages ytnef-tools depends on:
ii  libc6  2.24-9
ii  libytnef0  1.9-1

ytnef-tools recommends no packages.

ytnef-tools suggests no packages.

-- no debconf information

Bug#852160: gstreamer1.0-vaapi: presence breaks totem-video-thumbnailer

[Christoph Anton Mitterer]

Package: gstreamer1.0-vaapi
Severity: important


Hi.

This problem exists since quite a while now, as soon as gstreamer1.0-vaapi
is installed totem-video-thumbnailer fails to create thumbnails for many
formats (I've noticed e.g. WMV, realmead, some mpeg container formats).


For example with the package being installed:

$ totem-video-thumbnailer --verbose video.wmv foo.jpg
TotemVideoThumbnailer-Message: Initialised libraries, about to create video 
widget
TotemVideoThumbnailer-Message: setting URI file:///tmp/video.wmv
TotemVideoThumbnailer-Message: Video widget created
TotemVideoThumbnailer-Message: About to open video file
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
TotemVideoThumbnailer-Message: Checking whether file has cover
TotemVideoThumbnailer-Message: Opened video file: 'video.wmv'
TotemVideoThumbnailer-Message: About to seek to 0,33
TotemVideoThumbnailer-Message: About to get frame for iter 0

** (totem-video-thumbnailer:11267): WARNING **: Could not take screenshot: 
failed to retrieve or convert video frame
TotemVideoThumbnailer-Message: Frame for iter 0 was not interesting
TotemVideoThumbnailer-Message: About to seek to 0,67
TotemVideoThumbnailer-Message: About to get frame for iter 1

** (totem-video-thumbnailer:11267): WARNING **: Could not take screenshot: 
failed to retrieve or convert video frame
TotemVideoThumbnailer-Message: Frame for iter 1 was not interesting
TotemVideoThumbnailer-Message: About to seek to 0,10
TotemVideoThumbnailer-Message: About to get frame for iter 2

** (totem-video-thumbnailer:11267): WARNING **: Could not take screenshot: 
failed to retrieve or convert video frame
TotemVideoThumbnailer-Message: Frame for iter 2 was not interesting
TotemVideoThumbnailer-Message: About to seek to 0,90
TotemVideoThumbnailer-Message: About to get frame for iter 3

** (totem-video-thumbnailer:11267): WARNING **: Could not take screenshot: 
failed to retrieve or convert video frame
TotemVideoThumbnailer-Message: Frame for iter 3 was not interesting
TotemVideoThumbnailer-Message: About to seek to 0,50
TotemVideoThumbnailer-Message: About to get frame for iter 4

** (totem-video-thumbnailer:11267): WARNING **: Could not take screenshot: 
failed to retrieve or convert video frame
TotemVideoThumbnailer-Message: Frame for iter 4 was not interesting
totem-video-thumbnailer couldn't get a picture from 'video.wmv'
calestyo@heisenberg:~/data/__todo/.HSA/deletable$ totem-video-thumbnailer 
--verbose video.wmv foo.jpg --gst-debug
couldn't parse command-line options: Missing argument for --gst-debug




And without it being installed:

$ totem-video-thumbnailer --verbose video.wmv foo.jpg
TotemVideoThumbnailer-Message: Initialised libraries, about to create video 
widget
TotemVideoThumbnailer-Message: setting URI file:///tmp/video.wmv
TotemVideoThumbnailer-Message: Video widget created
TotemVideoThumbnailer-Message: About to open video file
TotemVideoThumbnailer-Message: Checking whether file has cover
TotemVideoThumbnailer-Message: Opened video file: 'video.wmv'
TotemVideoThumbnailer-Message: About to seek to 0,33
TotemVideoThumbnailer-Message: About to get frame for iter 0
TotemVideoThumbnailer-Message: Frame for iter 0 is interesting
TotemVideoThumbnailer-Message: Saving captured screenshot



This affects of course any piece of software that uses totem-video-thumbnailer
for creating thumbails (e.g. nautilus).


Cheers,
Chris.


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

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

Bug#811496: the remaing packages that need to be moved over to /usr/share/bash-completions/completions/

[shirish शिरीष]

Hi all,

Apart from bzr here are the other ones which are still stuck in
/etc/bash-completions.d/ at least on my desktop.

┌─[shirish@debian] - [/etc/bash_completion.d] - [10082]
└─[$] ls

apt-show-versions  deborphan dput grub maven quilt ufw bzr
desktop-file-validate  feedgnuplot  gtcli_bash_completion  notmuch
schroot cowbuilder dkms  git-extras insserv ocamlfind scilab darcs
dlocate-completion git-prompt lttng openvpn  tuxpaint-completion.bash

I would try to add the resulting affects to the other packages as well.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#852159: mktorrent: upstream changed maintainer, actual version missing new interesting features

[benoit barthelet]

Package: mktorrent
Version: 1.0-4+b1
Severity: important

 hello, esmil transmitted the maintenance / development of mktorrent: see
 https://github.com/Rudde/mktorrent/pull/15
 
 the pull in question adds the ability to put a source to infohash wich tends
 to become a 'standard'
 
 if debian package could change its source that would be awesome, is that
 possibke ?



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 
'experimental'), (90, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages mktorrent depends on:
ii  libc62.24-8
ii  libssl1.0.2  1.0.2j-4

mktorrent recommends no packages.

mktorrent suggests no packages.

-- no debconf information

Bug#830810: [Secure-testing-team] Bug#830810: bind9: CVE-2016-6170: Improper restriction of zone size limit

[Michael Gilbert]

control: reopen -1

I was wrong in the changelog, upstream has not yet implemented a fix for this.

Bug#852158: Preseeding debconf/priority causes main menu to display

[Josh Triplett]

Package: main-menu
Severity: normal

I'd like to use preseeding to pre-answer some questions in the
installer, while leaving others for the user to answer, including
questions asked with priority "high".  Using "auto url=..." sets the
priority to critical, so I tried including the following in my preseed
file:

d-i debconf/priority high

When I did so, the installer displayed the main menu immediately after
processing the preseed file, rather than proceeding to the next step.

If preseeding the priority in this way breaks some assumption in
main-menu, please document how a preseed file can change the debconf
priority without causing the menu to display.

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

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

Bug#852157: unknown-horizons: Fail to start (due to missing images content/gui/images/buttons/close_d.png?)

[Petter Reinholdtsen]

Package: unknown-horizons
Version: 2017.1+ds-1
Severity: important

Dear Maintainer,

When I try to start unknown-horizons (I used the package from unstable
in testing), it fail to start and complain about a missing image
close_d.png.  When I tried to copy
/usr/share/unknown-horizons/content/gui/images/buttons/close_h.png to
/usr/share/unknown-horizons/content/gui/images/buttons/close_d.png, the
program got a bit further and complained about another image.  It look
to me like a complete image set is missing in the package.

Here is the error I see:

% unknown-horizons 
libGL error: failed to authenticate magic 9
libGL error: failed to load driver: i965
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, 
skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, 
skipping unlock
Traceback (most recent call last):
  File "/usr/games/unknown-horizons", line 381, in 
main()
  File "/usr/games/unknown-horizons", line 191, in main
ret = horizons.main.start(options)
  File "/usr/lib/python2.7/dist-packages/horizons/main.py", line 166, in start
_modules.gui = Gui()
  File "/usr/lib/python2.7/dist-packages/horizons/gui/gui.py", line 128, in 
__init__
self.singleplayermenu = SingleplayerMenu(self.windows)
  File 
"/usr/lib/python2.7/dist-packages/horizons/gui/modules/singleplayermenu.py", 
line 62, in __init__
self._gui = load_uh_widget('singleplayermenu.xml')
  File "/usr/lib/python2.7/dist-packages/horizons/gui/util.py", line 89, in 
load_uh_widget
widget = loadXML(StringIO(get_widget_xml(filename)))
  File "/usr/lib/python2.7/dist-packages/fife/extensions/pychan/__init__.py", 
line 428, in loadXML
parse(filename_or_stream,loader)
  File "/usr/lib/python2.7/xml/sax/__init__.py", line 33, in parse
parser.parse(source)
  File "/usr/lib/python2.7/xml/sax/expatreader.py", line 110, in parse
xmlreader.IncrementalParser.parse(self, source)
  File "/usr/lib/python2.7/xml/sax/xmlreader.py", line 123, in parse
self.feed(buffer)
  File "/usr/lib/python2.7/xml/sax/expatreader.py", line 213, in feed
self._parser.Parse(data, isFinal)
  File "/usr/lib/python2.7/xml/sax/expatreader.py", line 317, in start_element
self._cont_handler.startElement(name, AttributesImpl(attrs))
  File "/usr/lib/python2.7/dist-packages/fife/extensions/pychan/__init__.py", 
line 354, in startElement
self._createInstance(cls,name,attrs)
  File "/usr/lib/python2.7/dist-packages/fife/extensions/pychan/__init__.py", 
line 363, in _createInstance
obj = cls(parent=self.root)
  File "/usr/lib/python2.7/dist-packages/horizons/engine/pychan_util.py", line 
230, in wrapper
func(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/horizons/gui/widgets/imagebutton.py", 
line 171, in __init__
self.path = "images/buttons/close"
  File "/usr/lib/python2.7/dist-packages/horizons/gui/widgets/imagebutton.py", 
line 118, in _set_path
self.down_image = image_path.format(mode='_d')
  File "/usr/lib/python2.7/dist-packages/horizons/engine/pychan_util.py", line 
66, in wrapper
return func(self, obj, image)
  File "/usr/lib/python2.7/dist-packages/fife/extensions/pychan/properties.py", 
line 92, in __set__
image_info["image"] = get_manager().loadImage(image)
  File "/usr/lib/python2.7/dist-packages/fife/extensions/pychan/internal.py", 
line 249, in loadImage
return self.hook.load_image(filename)
  File "/usr/lib/python2.7/dist-packages/fife/extensions/pychan/compat.py", 
line 88, in _fife_load_image
img = engine.getImageManager().load(filename)
  File "/usr/lib/python2.7/dist-packages/fife/fife.py", line 6840, in load
return _fife.ImageManager_load(self, name, loader)
RuntimeError: _[NotFound]_ , Something was searched, but not found :: 
content/gui/images/buttons/close_d.png
AL lib: (EE) alc_cleanup: 1 device not closed
%

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

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

Versions of packages unknown-horizons depends on:
ii  python   2.7.13-1
ii  python-enet  0.0~svn24-1+b2
ii  python-fife  0.3.5+git160920-1
ii  python-yaml  3.12-1
pn  python:any   
ii  ttf-unifont  1:9.0.06-2

unknown-horizons recommends no packages.

unknown-horizons suggests no packages.

-- no debconf information

Bug#852156: systemd-sysv: fails to upgrade from 'jessie' - trying to overwrite /usr/share/man/man8/halt.8.gz

[Andreas Beckmann]

Package: systemd-sysv
Version: 232-12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package systemd-sysv.
  Preparing to unpack .../systemd-sysv_232-12_amd64.deb ...
  Unpacking systemd-sysv (232-12) ...
  dpkg: error processing archive 
/var/cache/apt/archives/systemd-sysv_232-12_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man8/halt.8.gz', which is also in 
package upstart 1.11-5
  Errors were encountered while processing:
   /var/cache/apt/archives/systemd-sysv_232-12_amd64.deb


cheers,

Andreas


upstart=1.11-5_systemd-sysv=232-12.log.gz
Description: application/gzip

Bug#851826: pulseaudio: USB headset detected, but no sound

[Michael Haag]

That works in most instances, but it doesn't work in my use case. I have
an older OpenGL/OpenAL/OSS game that takes control of the keyboard and
mouse when it loads. This means I cannot access pulseaudio to change
devices. Oddly, there is no need to do this when my headset is plugged
in using the legacy audio jacks. Sound is directed to BOTH my speakers
and my headset.

The other case is when I use a Windows-only language learning
application which I run in a VM. The headset works with both legacy and
USB connections, but the sound quality with USB is so poor the
application cannot match my spoken pronunciation to the recorded voice,
making it impossible to use the program.

Maybe neither of the above can be attributed soley to pulseaudio, but I
didn't have this problem with my legacy headset. I can get by with the
legacy audio jacks, but the USB problem means I can't use some of the
headset features, such as surround sound.

On Sat, Jan 21, 2017, at 20:11, Felipe Sateler wrote:
> Hi,
> 
> On Jan 21, 2017 00:24, "Michael Haag"  wrote:
> 
> Sorry it took so long to reply. My ISP was switching our service, so I
> was without Internet access for a time. Please see attached screenshots.
> 
> 
> You did not have an audio-using application when you took the screenshot.
> Please open an audio player, start playing something, and check the
> Playback tab. In there you can choose what device the player will play
> through.
> 
> 
> Saludos,
> Felipe Sateler


-- 
"Democracy is ... a form of religion; it is the worship of jackals by
jackasses." -- H. L. Mencken

Bug#852155: python-persistent: please add dependency “Suggests: python-persistent-doc”

[Ben Finney]

Source: python-persistent
Version: 4.2.2-1
Severity: minor

Dear Maintainer,

Working with the ‘python-persistent’ packages requires understanding
how it works and what it does.

Please set a “Suggests: python-persistent-doc” dependency to the
binary package ‘python3-persistent’, or other binary packages for which
it is appropriate.

This will present the suggestion to administrators choosing which
packages to install.

-- 
 \ “Beware of and eschew pompous prolixity.” —Charles A. Beardsley |
  `\   |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#851722: [Python-modules-team] Bug#851722: django-pipeline: FTBFS randomly (failing tests)

[Brian May]

Santiago Vila  writes:

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

I am not able to reproduce this :-(

I am guessing it might be related to different order the tests are being
run in or something. Which can be non-determinstic - depends on order
files are listed in filesystem.

Are you able to reproduce with the following patch? This will show what
order the tests are being run in:


diff --git a/debian/rules b/debian/rules
index dc35e19..f53ec96 100755
--- a/debian/rules
+++ b/debian/rules
@@ -21,4 +21,4 @@ override_dh_installchangelogs:
dh_installchangelogs -- HISTORY.rst
 
 override_dh_auto_test:
-   PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONPATH=. python{version} 
/usr/bin/django-admin test --settings=tests.settings" dh_auto_test
+   PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONPATH=. python{version} 
/usr/bin/django-admin test -v3 --settings=tests.settings" dh_auto_test


Thanks!
-- 
Brian May 

Bug#852150: Remmina builds wrong cmd line for FreeRDP for RDP gateway connection )

[Jörg Frings-Fürst]

Hello Duncan,

thank you for spending your time helping to make Debian better with
this bug report.

First some suggestions: 

 * for the initial report please use reportbug to get all relevant
   informations.
 * please don't use html in your bugmails.  

Am Sonntag, den 22.01.2017, 01:17 + schrieb d...@synoia.com:
> Package: remmina
> 
> 
> Version: 1.1.1-2
> Severity: important
> 
> Remmina builds a command line to launch for FreeRDP in the Microsoft RDP 
> environment.
> 
The Debian Release 1.1.1-1 comes out at 2014-10-13. 

The Remmina issue 347 comes out at 2014-10-05 and is taged with
newfeature. This issue is still open.

So this bug should be tagged as wishlist. A wishlist bug on the Debian
stable Release and on a upstream not longer supported version is
practically useless.

So I close this bug.

[...]

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#802284: git-buildpackage: should assemble overlay before issuing 'debian/rules' commands

[Ben Finney]

On 17-Feb-2016, Ben Finney wrote:
> On 20-Oct-2015, Guido Günther wrote:
> > I'd be happy to apply a patch to achieve this behaviour. Given
> > that I'm not a overlay user myself and currently stall on other
> > things already.
> 
> I have implemented this behaviour and it seems to work correctly.

The patch has been updated against the latest release.

Please merge from my ‘issue/802284-overlay-before-rules’ branch

if you approve of the implementation.

-- 
 \“It is always a silly thing to give advice, but to give good |
  `\   advice is absolutely fatal.” —Oscar Wilde, _The Portrait of Mr. |
_o__)  W. H._, 1889-07 |
Ben Finney 


signature.asc
Description: PGP signature

Bug#820361: chromium connections to 1e100.net

[Michael Gilbert]

Most of the connections to 1e100.net are due to using Google as the
default search engine.  README.Debian describes how you can change
that.

Best wishes,
Mike

Bug#852078: [Python-modules-team] Bug#852078: src:python-mkdocs: New upstream release (0.16.x)

[Brian May]

Ghislain Antony Vaillant  writes:

> A new version is available upstream [1]. Please consider packaging it,
> perhaps in time for Stretch?
>
> https://github.com/mkdocs/mkdocs/releases/tag/0.16.1

I think it might be a bit late for Stretch, considering we are in soft
freeze (meaning no new packages, no re-entry, normal migrations). Don't
want to risk uploading a new package that gets into stretch and creates
RC bugs - it might mean the package fails to get into Stretch.
-- 
Brian May 

Bug#806037: gnumail: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Andreas Beckmann]

Followup-For: Bug #806037

Hi,

I stomped over this again and found your overhauled packaging in git. So
I went ahead and uploaded this to DELAYED/2, that should be sufficient
for the package to reach testing before the freeze.
Please let me know if I should delay this longer or cancel.

 gnumail (1.2.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop -dbg package in favor of autogenerated -dbgsym packages.
 .
   [ Eric Heintzmann ]
   * Update debian/watch file
   * Bump Standards-Version to 3.9.8
   * Add myself as new Uploader
   * Update Vcs-* fields
   * Add homepage
   * Remove useless ${gnustep:Depends} variable
   * Update debian/copyright file
   * Refresh patches
   * Overhaul *.install and *.links
   * Remove debian/menu file
   * Update debian/rules file  (Closes: #806037)


Andreas

Bug#845555: lxpanel: battery monitor no longer working

[Evgeny Kapun]

In version 0.9.3-1, the remaining time is shown correctly. There is still a minor glitch: if 
battery charge level is 100%, the remaining time is not shown. I think that this is due to this 
check [1]. I think that this check is wrong. I think the right check would be 
"lx_b->b->seconds >= 0" (since -1 is used to indicate that the value is not 
available).

BTW, time to full charge is still not correct, but now the reason is that the 
formula (time=energy/power) doesn't work for charging. While during discharge, 
power stays roughly the same (assuming that workload doesn't change), during 
charge power drops significantly as the battery nears full charge. As a result, 
the time displayed is about three times smaller than the actual time it takes 
for the battery to fully charge. Still, the value can be used as a (very) rough 
estimate.

[1] 
https://git.lxde.org/gitweb/?p=lxde/lxpanel.git;a=blob;f=plugins/batt/batt.c;h=988d9fdfb7ec9a01d1d692b8ea30e3e3a878b9a5;hb=9dbda5c15782596983ae61478c1612262633ae41#l164

Bug#852011: petsc (libpetsc3.7.4-dev) depends on libgfortran-5-dev

[Drew Parsons]

On Fri, 20 Jan 2017 18:22:01 +0100 Matthias Klose 
wrote:
> 
> The severity of this report is likely to be raised before the
release,
> so that the gcc-5 package can be removed for the release.
> 


"Likely to be raised..." ??  The severity is already serious!

Drew

Bug#685146: wicd-daemon packages dependencies

[Axel Beckert]

Hi,

Jörg-Volker Peetz wrote:
> the dependency on an dhcp client in the packages should be formulated with the
> help of the virtual packet "dhcp-client" as something like
> 
>   dhcpcd | pump | udhcpc | dhcp-client
> 
> (Compare bug #680976.)

I disagree here. Wicd has a list of supported DHCP clients and handles
each one differently depending on its features. AFAIK wicd is not
capable of talking to arbitrary DHCP clients. Hence the way #680976
has been fixed was correct.

> Furthermore, I would like to suggest to change the dependency on
> "wireless-tools" to a recommendation,

Indeed, wicd theoretically could be used to handle wired
configurations only. I'm though not sure if wicd works properly
without iwconfig, iwlist and friends installed, so I'm reluctant here.
Additionally, I consider such cases being very rare.

Less rare, but a similar case is the question if wpa-supplicant needs
to be a hard dependency. E.g. there might be users just connecting to
open or WEP-"secured" wifi networks. (But at least the latter case
should be very rare nowadays, too.)

I'd avoid these kind of changes before the Stretch release as they
need quite some testing. But I might reconsider them after the Stretch
release.

> since with newer kernels this package isn't mandatory any more.

I don't see why this would be relevant here. The sole reason for
downgrading these dependencies is because there might be use cases
where wireless at all is not needed. (AFAIK wicd can't yet use "iw"
instead of iwconfig and friends.)

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#852154: pdfshuffler: Namespace Poppler not available

[Christian Buhtz]

Package: pdfshuffler
Version: 0.6.0-8
Severity: normal

Dear Maintainer,

I installed pdfshuffler but can not start it because of that message.

$ pdfshuffler
Traceback (most recent call last):
  File "/usr/local/bin/pdfshuffler", line 30, in 
from pdfshuffler.pdfshuffler import main
  File "/usr/local/lib/python2.7/dist-packages/pdfshuffler/pdfshuffler.py",
line 76, in 
gi.require_version('Poppler', '0.18')
  File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 118, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Poppler not available

After that I installed python-poppler* packages. But the message didn't change.

Here are some more package informations

$ apt-cache policy pdfshuffler
pdfshuffler:
  Installiert:   0.6.0-8
  Installationskandidat: 0.6.0-8
  Versionstabelle:
 *** 0.6.0-8 500
500 http://httpredir.debian.org/debian unstable/main i386 Packages
100 /var/lib/dpkg/status

$ apt-cache policy python-poppler*
python-poppler-dbg:
  Installiert:   0.12.1-9
  Installationskandidat: 0.12.1-9
  Versionstabelle:
 *** 0.12.1-9 500
500 http://httpredir.debian.org/debian unstable/main i386 Packages
100 /var/lib/dpkg/status
python-poppler-qt4:
  Installiert:   0.24.0-1+b2
  Installationskandidat: 0.24.0-1+b2
  Versionstabelle:
 *** 0.24.0-1+b2 500
500 http://httpredir.debian.org/debian unstable/main i386 Packages
100 /var/lib/dpkg/status
python-poppler:
  Installiert:   0.12.1-9
  Installationskandidat: 0.12.1-9
  Versionstabelle:
 *** 0.12.1-9 500
500 http://httpredir.debian.org/debian unstable/main i386 Packages
100 /var/lib/dpkg/status



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

Kernel: Linux 4.9.5-towo.1-siduction-686 (SMP w/2 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 pdfshuffler depends on:
ii  python-gtk2 2.24.0-5.1
ii  python-poppler  0.12.1-9
ii  python-pypdf2   1.26.0-2
pn  python:any  

pdfshuffler recommends no packages.

pdfshuffler suggests no packages.

-- no debconf information

Bug#679089: wicd-gtk: regression: pulls a lot of GNOME stuff by default

[Axel Beckert]

Control: tags -1 + wontfix moreinfo

Hi Eugene,

Eugene V. Lyubimkin wrote:
> New wicd-gtk (currently in testing/unstable) stopped recommending any
> other "sudo-client" than gksu

Because all others are no more available in Debian and plain sudo
doesn't make sense for a GUI application to me.

> and gksu pulls by default gnome-keyring
> which pulls a lot of other unrelated stuff.
> 
> If wicd-gtk can work without gksu without losing a major part of
> functionality, please downgrade it to Suggests.

No. gksu is the right tool for the majority of users, so it should be
installed with default settings. But since it's only a Recommends, you
are free to uninstall (or choose to not install) it at any time.

Dropping it to Suggest would mean the admin would have to select it
explicitly to get it installed. That's not what we want.

I'm though open to any alternative recommendation in addition to gksu.
I'm just not aware of any package suitable as alternative to gksu.

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#578757: xine-ui: checksum problems with /var/lib/xine/xine.desktop

[Andreas Beckmann]

Followup-For: Bug #578757
Control: tag -1 patch pending

Hi,

I just uploaded a NMU to finally fix this problem in stretch to
DELAYED/2. Please let me know if I should delay it longer.

Cheers,

Andreas

diff -Nru xine-ui-0.99.9/debian/changelog xine-ui-0.99.9/debian/changelog
--- xine-ui-0.99.9/debian/changelog	2015-01-17 20:29:02.0 +0100
+++ xine-ui-0.99.9/debian/changelog	2017-01-22 04:12:02.0 +0100
@@ -1,3 +1,13 @@
+xine-ui (0.99.9-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop -dbg package in favor of autogenerated -dbgsym packages.
+  * Ship xine.desktop template in /usr/share/xine and do not modify it
+in-place.  (Closes: #578757)
+  * Add missing build-{arch,indep} targets.
+
+ -- Andreas Beckmann   Sun, 22 Jan 2017 04:12:02 +0100
+
 xine-ui (0.99.9-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru xine-ui-0.99.9/debian/control xine-ui-0.99.9/debian/control
--- xine-ui-0.99.9/debian/control	2014-10-06 13:12:05.0 +0200
+++ xine-ui-0.99.9/debian/control	2017-01-22 03:50:14.0 +0100
@@ -42,16 +42,3 @@
  This package contains additional front ends, aaxine, cacaxine and fbxine
  which run even on the console, so you can use it to watch DVDs even in
  an xterm. ;-)
-
-Package: xine-dbg
-Architecture: any
-Priority: extra
-Section: debug
-Depends: ${misc:Depends}, xine-ui (= ${binary:Version}) | xine-console (= ${binary:Version})
-Description: the xine video player, debug symbols
- xine-ui is a frontend for the libxine video player library.
- .
- This package contains debug symbols for the xine frontends xine,
- aaxine, cacaxine, fbxine. Please install them to create meaningful
- backtraces when reporting bugs.
-
diff -Nru xine-ui-0.99.9/debian/copyright xine-ui-0.99.9/debian/copyright
--- xine-ui-0.99.9/debian/copyright	2014-10-06 13:12:05.0 +0200
+++ xine-ui-0.99.9/debian/copyright	2017-01-22 04:01:54.0 +0100
@@ -15,4 +15,4 @@
 (at your option) any later version.
 
 On Debian systems, the full text of the GPL can be found in the file
-/usr/share/common-licenses/GPL
+/usr/share/common-licenses/GPL-2
diff -Nru xine-ui-0.99.9/debian/rules xine-ui-0.99.9/debian/rules
--- xine-ui-0.99.9/debian/rules	2014-10-06 13:12:05.0 +0200
+++ xine-ui-0.99.9/debian/rules	2017-01-22 04:04:30.0 +0100
@@ -17,6 +17,9 @@
 		--build $(DEB_HOST_GNU_TYPE) || \
 		(echo "=== config.log: ==="; cat config.log; false)
 
+build: build-arch build-indep
+build-indep:
+build-arch: build-stamp
 build-stamp: config.status
 	dh_testdir
 	$(MAKE)
@@ -42,7 +45,7 @@
 install: build-stamp
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 	$(MAKE) install DESTDIR=$(CURDIR)/debian/tmp
 	mv debian/tmp/usr/share/doc/xitk/README \
@@ -55,7 +58,7 @@
 # no arch-indep packages
 
 # Build architecture-dependent files here.
-binary-arch: build-stamp install debian/xine-ui.postinst
+binary-arch: build-arch install debian/xine-ui.postinst
 	dh_testdir
 	dh_testroot
 	dh_install
@@ -64,7 +67,7 @@
 	dh_installmime
 	dh_installchangelogs -k ChangeLog
 	dh_link
-	dh_strip --dbg-package=xine-dbg
+	dh_strip
 	dh_compress -X README.
 	dh_fixperms
 	dh_installdeb
diff -Nru xine-ui-0.99.9/debian/xine-ui.dirs xine-ui-0.99.9/debian/xine-ui.dirs
--- xine-ui-0.99.9/debian/xine-ui.dirs	1970-01-01 01:00:00.0 +0100
+++ xine-ui-0.99.9/debian/xine-ui.dirs	2017-01-22 03:56:19.0 +0100
@@ -0,0 +1 @@
+var/lib/xine
diff -Nru xine-ui-0.99.9/debian/xine-ui.install xine-ui-0.99.9/debian/xine-ui.install
--- xine-ui-0.99.9/debian/xine-ui.install	2014-10-06 13:12:05.0 +0200
+++ xine-ui-0.99.9/debian/xine-ui.install	2017-01-22 03:53:17.0 +0100
@@ -7,7 +7,7 @@
 debian/tmp/usr/share/man/man1/xine-remote.1
 debian/tmp/usr/share/man/man1/xine.1
 debian/tmp/usr/share/pixmaps
-debian/tmp/usr/share/applications/xine.desktop var/lib/xine
+debian/tmp/usr/share/applications/xine.desktop usr/share/xine
 debian/tmp/usr/share/xine/skins
 debian/tmp/usr/share/xine/visuals
 src/xitk/xine-toolkit/README usr/share/doc/xine-ui/README.xitk
diff -Nru xine-ui-0.99.9/debian/xine-ui.postinst.in xine-ui-0.99.9/debian/xine-ui.postinst.in
--- xine-ui-0.99.9/debian/xine-ui.postinst.in	2014-10-06 13:12:05.0 +0200
+++ xine-ui-0.99.9/debian/xine-ui.postinst.in	2017-01-22 03:54:48.0 +0100
@@ -6,7 +6,7 @@
   triggered|configure)
 if test -x @XINE_LIST@; then
   {
-	sed -e '/^MimeType=/ d' 

Bug#852153: gcc-6/mips: backport option to disable madd4 instructions and set it default

[YunQiang Su]

Package: src:gcc-6
Version: 6.3.0-3

Hi, gcc-7 has added a new option to disable madd.fmt/msub.fmt etc instructions,
as
1. For the MIPS standard, these instructions are unfused, while on Loongson,
they are fused. With these instructions enabled, some software
may failed to
run on Loongson.
 2. With some test, these instructions won't take significant
performance boost.

So, we decide to disable these instructions at all.

In this patch, we also:
  1. generate fused madd4 instructions when -march=loongson3a used.
  2. add a new option: -mlxc1-sxc1.

-- 
YunQiang Su
diff --git a/debian/patches/MIPS-MADD4.diff b/debian/patches/MIPS-MADD4.diff
new file mode 100644
index 000..e668b8c
--- /dev/null
+++ b/debian/patches/MIPS-MADD4.diff
@@ -0,0 +1,307 @@
+From eb5c0cb6c16d435f6797cd934ceaac73ac7db52c Mon Sep 17 00:00:00 2001
+From: clm 
+Date: Fri, 20 Jan 2017 01:05:25 +
+Subject: [PATCH] gcc/ 2017-01-19  Matthew Fortune 
+   Yunqiang Su  
+
+   * config.gcc (supported_defaults): Add madd4.
+   (with_madd4): Add validation.
+   (all_defaults): Add madd4.
+   * config/mips/mips.opt (mmadd4): New option.
+   * gcc/config/mips/mips.h (OPTION_DEFAULT_SPECS): Add a default for
+   mmadd4.
+   (TARGET_CPU_CPP_BUILTINS): Add builtin_define for
+   __mips_no_madd4.
+   (ISA_HAS_UNFUSED_MADD4): Gate with mips_madd4.
+   (ISA_HAS_FUSED_MADD4): Likewise.
+   * gcc/doc/invoke.texi (-mmadd4): Document the new option.
+   * gcc/doc/install.texi (--with-madd4): Document the new option.
+
+gcc/testsuite/
+2017-01-19  Matthew Fortune  
+
+   * gcc.target/mips/madd4-1.c: New file.
+   * gcc.target/mips/madd4-2.c: Likewise.
+   * gcc.target/mips/mips.exp (mips_option_groups): Add ghost option
+   HAS_MADD4.
+   (mips_option_groups): Add -m[no-]madd4.
+   (mips-dg-init): Detect default -mno-madd4.
+   (mips-dg-options): Handle HAS_MADD4 arch upgrade/downgrade.
+   * gcc.target/mips/mips-ps-type.c: Add -mmadd4 test option.
+   * gcc.target/mips/mips-ps-type-2.c: Likewise.
+   * gcc.target/mips/nmadd-1.c: Likewise.
+   * gcc.target/mips/nmadd-2.c: Likewise.
+   * gcc.target/mips/nmadd-3.c: Likewise.
+
+
+git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@244676 
138bc75d-0d04-0410-961f-82ee72b054a4
+---
+ gcc/ChangeLog  | 16 
+ gcc/config.gcc | 19 +--
+ gcc/config/mips/mips.h | 12 +---
+ gcc/config/mips/mips.opt   |  4 
+ gcc/doc/install.texi   | 14 ++
+ gcc/doc/invoke.texi|  8 +++-
+ gcc/testsuite/ChangeLog| 15 +++
+ gcc/testsuite/gcc.target/mips/madd4-1.c| 14 ++
+ gcc/testsuite/gcc.target/mips/madd4-2.c| 14 ++
+ gcc/testsuite/gcc.target/mips/mips-ps-type-2.c |  2 +-
+ gcc/testsuite/gcc.target/mips/mips-ps-type.c   |  2 +-
+ gcc/testsuite/gcc.target/mips/mips.exp | 12 +++-
+ gcc/testsuite/gcc.target/mips/nmadd-1.c|  2 +-
+ gcc/testsuite/gcc.target/mips/nmadd-2.c|  2 +-
+ gcc/testsuite/gcc.target/mips/nmadd-3.c|  2 +-
+ 15 files changed, 126 insertions(+), 12 deletions(-)
+ create mode 100644 gcc/testsuite/gcc.target/mips/madd4-1.c
+ create mode 100644 gcc/testsuite/gcc.target/mips/madd4-2.c
+
+Index: b/src/gcc/config.gcc
+===
+--- a/src/gcc/config.gcc
 b/src/gcc/config.gcc
+@@ -3987,7 +3987,7 @@ case "${target}" in
+   ;;
+ 
+   mips*-*-*)
+-  supported_defaults="abi arch arch_32 arch_64 float fpu nan 
fp_32 odd_spreg_32 tune tune_32 tune_64 divide llsc mips-plt synci lxc1-sxc1"
++  supported_defaults="abi arch arch_32 arch_64 float fpu nan 
fp_32 odd_spreg_32 tune tune_32 tune_64 divide llsc mips-plt synci lxc1-sxc1 
madd4"
+ 
+   case ${with_float} in
+   "" | soft | hard)
+@@ -4125,6 +4125,21 @@ case "${target}" in
+   exit 1
+   ;;
+   esac
++
++  case ${with_madd4} in
++  yes)
++  with_madd4=madd4
++  ;;
++  no)
++  with_madd4=no-madd4
++  ;;
++  "")
++  ;;
++  *)
++  echo "Unknown madd4 type used in --with-madd4" 1>&2
++  exit 1
++  ;;
++  esac
+   ;;
+ 
+   nds32*-*-*)
+@@ -4558,7 +4573,7 @@ case ${target} in
+ esac
+ 
+ t=
+-all_defaults="abi cpu cpu_32 cpu_64 arch arch_32 arch_64 tune tune_32 tune_64 
schedule float 

Bug#852096: psgml: please migrate to emacs25 soon

[Rob Browning]

Neil Roeth  writes:

> I actually just uploaded a new version of psgml yesterday with the
> dependencies updated to include Emacs 25. :-)   However, it just has
> emacs25 | emacs24.  Prior versions did not include emacs*-nox or
> emacs*-lucid, but I don't know why.   I'll look into making it depend on
> "emacs25-nox | emacs25 | emacs25-lucid | emacs24-nox | emacs24 |
> emacs24-lucid".

Nice, and thanks.

And if it's not a build dependency, then "emacs25 | emacs24 ..." should
be just fine.  The -nox dep first just lightens the load on the buildds.
Probably should have mentioned that.

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

Bug#787152: Section 11.5/11.6 - Replace Boot-up method from init to systemd

[Joost van Baal-Ilić]

tags 787152 + patch
thanks

Hi,

Alan: thanks for reporting this issue; and for supplying the nice patch.

See also https://lists.debian.org/<20160530145917.ge...@beskar.mdcc.cx> .
(Working on this is still on my todo-list.)

Bye,

Joost



On Fri, May 29, 2015 at 03:17:10PM +0800, Alan Lee wrote:
> Package: debian-faq
> 
> Section 11.5/11.6 - Replace Boot-up method from init to systemd.
> 
> Proposed change in patch file attached.

> --- customizing.sgml2015-05-29 14:15:36.792753648 +0800
> +++ customizing.sgml.new2015-05-29 15:08:09.037752850 +0800
> @@ -52,96 +52,32 @@
>  Every distribution seems to have a different boot-up
>method.  Tell me about Debian's.
> 
> -Like all Unices, Debian boots up by executing the program init
> -As of this writing, the unstable release for Debian GNU/Linux is
> -replacing sysvinit with  Linux. For
> -more information see https://wiki.debian.org/systemd;>..
> -The configuration file for init (which is /etc/inittab)
> -specifies that the first script to be executed should be
> -/etc/init.d/rcS.  This script runs all of the scripts in
> -/etc/rcS.d/ by forking subprocess
> -to perform initialization such as to check and to mount file systems,
> -to load modules, to start the network services, to set the clock, and to
> -perform other initialization.
> -
> -After completing the boot process, init executes all start
> -scripts in a directory specified by the default runlevel (this runlevel
> -is given by the entry for id in /etc/inittab).
> -Like most  System V compatible Unices, Linux has 7 
> runlevels:
> -
> -  0 (halt the system),
> -  1 (single-user mode),
> -  2 through 5 (various multi-user modes), and
> -  6 (reboot the system).
> -
> -Debian systems come with id=2, which indicates that the default
> -runlevel will be '2' when the multi-user state is entered, and the
> -scripts in /etc/rc2.d/ will be run.
> -
> -Debian uses dependency-based boot ordering through  the
> -LSB headers in each script under /etc/init.d/, as well as
> -parallel concurrent booting through the use of  -up the boot process.
> -
> -The scripts in any of the directories, /etc/rcN.d/
> -are just symbolic links back to scripts in /etc/init.d/.  However,
> -the names of the files in each of the /etc/rcN.d/
> -directories are selected to indicate the way the scripts in
> -/etc/init.d/ will be run.  Specifically, before entering any
> -runlevel, all the scripts beginning with 'K' are run; these scripts kill
> -services.  Then all the scripts beginning with 'S' are run; these scripts
> -start services.  The two-digit number following the 'K' or 'S' indicates
> -the order in which the script is run.  Lower numbered scripts are executed
> -first.
> -
> -This approach works because the scripts in /etc/init.d/ all
> -take an argument which can be either `start', `stop', `reload', `restart'
> -or `force-reload' and will then do the task indicated by the argument.
> -These scripts can be used even after a system has been booted, to control
> -various processes.
> -
> -For example, with the argument `reload' the command
> -  /etc/init.d/sendmail reload
> -sends the sendmail daemon a signal to reread its configuration file.
> -
> -Note that  -/etc/init.d/ scripts,  -
> -What other facilities are provided
> -  to customize the boot process besides
> -  rc.local?
> -
> -The rc.local script is executed at the end of each multiuser
> -runlevel. In Debian it is configured to do nothing. This provides
> -customisation of the boot process, but might not be sufficient
> -for all situations.
> -
> -Suppose a system needs to execute script foo on start-up,
> -or on entry to a particular (System V) runlevel.  Then the system
> -administrator should:
> -
> -  Enter the script foo into the directory 
> /etc/init.d/.
> -  Run the Debian command update-rc.d with appropriate
> -  arguments, to specify which runlevels should start the service, and which
> -  runlevels should stop the service.
> -  Consider rebooting the system to check that the service starts
> -  correctly (assuming that you've asked for it to be started in the
> -  default runlevel).  Otherwise, manually start it by running
> -  `/etc/init.d/foo start'.
> -
> -
> -One might, for example, cause the script foo to execute at
> -boot-up, by putting it in /etc/init.d/ and running
> -update-rc.d foo defaults 19.  The argument `defaults' 
> refers
> -to the default runlevels, which means (at least in absence of any LSB comment
> -block to the contrary) to start the service in runlevels 2 through 5,
> -and to stop the service in runlevels 0, 1 and 6.
> -(Any LSB Default-Start and Default-Stop directives in foo take
> -precedence when using the sysv-rc version of update-rc.d, but are
> -ignored by the current (v0.8.10) file-rc version of update-rc.d.)
> -The argument `19' ensures that foo is called after all
> -scripts whose number is less than 19 have completed, and before all scripts
> -whose number is 20 or greater.
> +Like most Linux 

Bug#852152: kernel 4.9: NVIDIA: Failed to load the NVIDIA kernel module

[Dan Jacobson]

Package: nvidia-legacy-304xx-kernel-dkms
Version: 304.134-1
Severity: grave

Even though your package Description says
"Building the kernel module has been tested up to Linux 4.9."

Maybe BUILDING yes, but not RUNNING, no.
With 4.9 you will get: NVIDIA: Failed to load the NVIDIA kernel module

P.S.,
https://wiki.debian.org/NvidiaGraphicsDrivers
does not mention the case when
$ cat /etc/debian_version
9.0

Only older versions.

-- System Information:
Debian Release: 9.0
  APT prefers experimental
  APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages nvidia-legacy-304xx-kernel-dkms depends on:
ii  dkms 2.3-2
ii  nvidia-installer-cleanup 20151021+4
ii  nvidia-legacy-304xx-kernel-support [nvidia-legacy-304xx-kernel-  304.134-1

Versions of packages nvidia-legacy-304xx-kernel-dkms recommends:
ii  nvidia-legacy-304xx-driver  304.134-1

nvidia-legacy-304xx-kernel-dkms suggests no packages.

Versions of packages nvidia-legacy-304xx-driver depends on:
ii  nvidia-installer-cleanup20151021+4
ii  nvidia-legacy-304xx-alternative 304.134-1
ii  nvidia-legacy-304xx-driver-bin  304.134-1
ii  nvidia-legacy-304xx-driver-libs 304.134-1
ii  nvidia-legacy-304xx-vdpau-driver304.134-1
ii  nvidia-support  20151021+4
ii  xserver-xorg-video-nvidia-legacy-304xx  304.134-1

Versions of packages nvidia-legacy-304xx-driver recommends:
ii  nvidia-persistenced   375.26-1
ii  nvidia-settings-legacy-304xx  304.134-1

nvidia-legacy-304xx-driver suggests no packages.

Versions of packages nvidia-legacy-304xx-driver-libs depends on:
ii  libgl1-nvidia-legacy-304xx-glx  304.134-1

Versions of packages nvidia-legacy-304xx-driver-libs recommends:
ii  libnvidia-legacy-304xx-cfg1   304.134-1
pn  nvidia-legacy-304xx-driver-libs-i386  

Versions of packages libgl1-nvidia-legacy-304xx-glx depends on:
ii  libc62.24-9
ii  libnvidia-legacy-304xx-glcore304.134-1
ii  libx11-6 2:1.6.4-2
ii  libxext6 2:1.3.3-1
ii  libxv1   2:1.0.11-1
ii  libxvmc1 2:1.0.10-1
ii  nvidia-installer-cleanup 20151021+4
ii  nvidia-legacy-304xx-alternative  304.134-1
ii  nvidia-support   20151021+4

libgl1-nvidia-legacy-304xx-glx recommends no packages.

libgl1-nvidia-legacy-304xx-glx suggests no packages.

Versions of packages xserver-xorg-video-nvidia-legacy-304xx depends on:
ii  libc6  2.24-9
ii  libnvidia-legacy-304xx-glcore  304.134-1
ii  nvidia-installer-cleanup   20151021+4
ii  nvidia-legacy-304xx-alternative304.134-1
ii  nvidia-support 20151021+4
ii  xserver-xorg-core [xorg-video-abi-23]  2:1.19.1-4
ii  xserver-xorg-legacy2:1.19.1-4

Versions of packages xserver-xorg-video-nvidia-legacy-304xx recommends:
ii  nvidia-legacy-304xx-driver304.134-1
ii  nvidia-legacy-304xx-vdpau-driver  304.134-1
ii  nvidia-settings-legacy-304xx  304.134-1

xserver-xorg-video-nvidia-legacy-304xx suggests no packages.

Versions of packages nvidia-legacy-304xx-alternative depends on:
ii  glx-alternative-nvidia  0.7.4

Versions of packages glx-alternative-nvidia depends on:
ii  glx-alternative-mesa  0.7.4
ii  glx-diversions0.7.4
ii  update-glx0.7.4

Versions of packages glx-alternative-nvidia suggests:
pn  nvidia-driver  

Versions of packages xserver-xorg-video-intel depends on:
ii  libc6  2.24-9
ii  libdrm-intel1  2.4.74-1
ii  libdrm22.4.74-1
ii  libpciaccess0  0.13.4-1
ii  libpixman-1-0  0.34.0-1
ii  libudev1   232-12
ii  libx11-6   2:1.6.4-2
ii  libx11-xcb12:1.6.4-2
ii  libxcb-dri2-0  1.12-1
ii  libxcb-dri3-0  1.12-1
ii  libxcb-sync1   1.12-1
ii  libxcb-util0   0.3.8-3
ii  libxcb11.12-1
ii  libxcursor11:1.1.14-1+b1
ii  libxdamage11:1.1.4-2+b1
ii  libxext6   2:1.3.3-1
ii  libxfixes3 1:5.0.3-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxrandr2 2:1.5.1-1
ii  libxrender11:0.9.10-1
ii  libxshmfence1  1.2-1
ii  libxss1

Bug#852020: Further Investigation

[Bachsau]

I further investigated this error and it seems it has to do with my 
system already using the new directory structure, where /lib is 
symlinked to /usr/lib and your packages tries to place an aditional 
symlink in /usr/lib/x86_64-linux-gnu/libpng12.so.0 which would then link 
to itself. However, /usr/lib is never accessed when loading 
x86_64-linux-gnu libraries, so it should be save to remove this part 
from the package.




smime.p7s
Description: S/MIME Cryptographic Signature

Bug#852096: psgml: please migrate to emacs25 soon

[Neil Roeth]

On 01/21/2017 12:28 PM, Rob Browning wrote:
> Package: psgml
> Version: 1.4.0-5
> User: debian-emac...@lists.debian.org
> Usertags: debian-emac...@lists.debian.org
>
> We'd like to remove emacs24 from the archive, so please try to upgrade
> to emacs25, or add optional support for emacs25 as soon as you can.
>
> For example, assuming the package works with emacs25, a dependency like
>
>   emacs25-nox | emacs25 | emacs24 | ...
>
> should suffice.
>
> If you don't have time to handle this yourself, we'd be happy to try to
> assist with an NMU (please let us know).
>
> Our original goal was to finish this for stretch, but we missed your
> package in our initial analysis, so there are only a couple of days
> left to upload this kind of change.
>
> Thanks
I actually just uploaded a new version of psgml yesterday with the
dependencies updated to include Emacs 25. :-)   However, it just has
emacs25 | emacs24.  Prior versions did not include emacs*-nox or
emacs*-lucid, but I don't know why.   I'll look into making it depend on
"emacs25-nox | emacs25 | emacs25-lucid | emacs24-nox | emacs24 |
emacs24-lucid".

-- 
Neil Roeth

Bug#852151: error: cannot open Packages index using db5 - Input/output error (5)

[積丹尼 Dan Jacobson]

Package: dkms
Version: 2.3-2
Severity: wishlist

Please clean up these errors.

# aptitude install linux-headers-amd64
The following NEW packages will be installed:
  linux-headers-4.9.0-1-amd64{a} (D: linux-headers-amd64) (linux-headers-amd64 
D: linux-headers-4.9.0-1-amd64)
  linux-headers-4.9.0-1-common{a} (D: linux-headers-4.9.0-1-amd64) 
(linux-headers-amd64 D: linux-headers-4.9.0-1-amd64 D: 
linux-headers-4.9.0-1-common)
  linux-headers-amd64
  linux-kbuild-4.9{a} (D: linux-headers-4.9.0-1-amd64) (linux-headers-amd64 D: 
linux-headers-4.9.0-1-amd64 D: linux-kbuild-4.9)
0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/8,495 kB of archives. After unpacking 50.8 MB will be used.
Do you want to continue? [Y/n/?]
Selecting previously unselected package linux-headers-4.9.0-1-common.
(Reading database ... 163792 files and directories currently installed.)
Preparing to unpack .../linux-headers-4.9.0-1-common_4.9.2-2_all.deb ...
Unpacking linux-headers-4.9.0-1-common (4.9.2-2) ...
Selecting previously unselected package linux-kbuild-4.9.
Preparing to unpack .../linux-kbuild-4.9_4.9.2-2_amd64.deb ...
Unpacking linux-kbuild-4.9 (4.9.2-2) ...
Selecting previously unselected package linux-headers-4.9.0-1-amd64.
Preparing to unpack .../linux-headers-4.9.0-1-amd64_4.9.2-2_amd64.deb ...
Unpacking linux-headers-4.9.0-1-amd64 (4.9.2-2) ...
Selecting previously unselected package linux-headers-amd64.
Preparing to unpack .../linux-headers-amd64_4.9+78_amd64.deb ...
Unpacking linux-headers-amd64 (4.9+78) ...
Setting up linux-headers-4.9.0-1-common (4.9.2-2) ...
Setting up linux-kbuild-4.9 (4.9.2-2) ...
Setting up linux-headers-4.9.0-1-amd64 (4.9.2-2) ...
/etc/kernel/header_postinst.d/dkms:
error: db5 error(5) from dbenv->open: Input/output error
error: cannot open Packages index using db5 - Input/output error (5)
error: cannot open Packages database in /root/.rpmdb
error: db5 error(5) from dbenv->open: Input/output error
error: cannot open Packages index using db5 - Input/output error (5)
error: cannot open Packages database in /root/.rpmdb
error: db5 error(5) from dbenv->open: Input/output error
error: cannot open Packages index using db5 - Input/output error (5)
error: cannot open Packages database in /root/.rpmdb
error: db5 error(5) from dbenv->open: Input/output error
error: cannot open Packages index using db5 - Input/output error (5)
error: cannot open Packages database in /root/.rpmdb
error: db5 error(5) from dbenv->open: Input/output error
error: cannot open Packages index using db5 - Input/output error (5)
error: cannot open Packages database in /root/.rpmdb
error: db5 error(5) from dbenv->open: Input/output error
error: cannot open Packages index using db5 - Input/output error (5)
error: cannot open Packages database in /root/.rpmdb
error: db5 error(5) from dbenv->open: Input/output error
error: cannot open Packages index using db5 - Input/output error (5)
error: cannot open Packages database in /root/.rpmdb
error: db5 error(5) from dbenv->open: Input/output error
error: cannot open Packages index using db5 - Input/output error (5)
error: cannot open Packages database in /root/.rpmdb

Bug#852046: fvwm: GUI menu config tool doesn't pop-up having several "menus" installed.

[Jaimos Skriletz]

On Fri, 20 Jan 2017 21:22:41 -0500 Awtul  wrote:
> Package: fvwm
> Version: 1:2.6.7-3
> Severity: normal
>
> Dear Maintainer,
>

Thank you for the bug report

> The GUI menu config tool doesn't pop-up when  having several "menus" 
> installed.
> Right now I have 'enlightenment.menu', 'razor-config.menu', 
> 'lxde-applications.menu', 'xfce-applications.menu', 'debian-menu.menu',
> 'razor-applications.menu', 'lxlauncher-applications.menu' and 
> 'gnome-applications.menu' installed.
> Removing one of them (lxlauncher-applications.menu) solves the problem.
> I get this error in .xsession-errors  "[fvwm] [module_receive]: <>" 
> Module (0x55a8a10061f0) command is too big (1156), limit is 1000".
> Seems like that's an issue related to FvwmForums module hitting a size limit.
>

It appears this is an issue due to a limitation in the amount of data
sent to a module. I will forward this to upstream and see what their
response is.

In the meantime some workarouds could be

1) Configure fvwm-menu-desktop from the command line. Its manpage
should help and the config file will need updated.

2) Remove unused menus.

jaimos

Bug#845555: Bug fixed

[128]

Hi,

I tried lxpanel 0.9.3-1 from unstable and I can confirm that the bug has
been fixed. The battery monitor works as expected.

Thanks

Bug#851928: linux-image-4.9.0-1-amd64: Kernel 4.9 fails to boot on Thinkpad T440p

[Roger Shimizu]

On Sun, Jan 22, 2017 at 3:18 AM, John M.  wrote:
>
> It took forever to build (i.e., about three hours just for amd64), but yes,
> after applying those two patches I can boot properly ("journalctl -b -k"
> messages attached).

Thanks for the verification!

You're lucky that it just takes 2-3 hours on amd64.
There's platform that take days to build the kernel [0] (look at
"Build time" column). :-P

[0] https://buildd.debian.org/status/logs.php?pkg=linux=sh4


On Sun, Jan 22, 2017 at 2:30 AM, Ben Hutchings  wrote:
>
> Please add this bug number to the changelog so it gets closed.

Thanks for the remind!
Fixed.

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

Bug#851339: [Pkg-fonts-devel] Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Paul Wise]

On Sat, 2017-01-21 at 12:39 +0100, Fabian Greffrath wrote:

> I find this by far the most convincing argument, although I still find
> it difficult to accept that it should make a difference for Debian as a
> mere downstream distributor. We provide many packages with fonts in OTF
> format and while this is accepted as a proper source for some, it is not
> for others because of upstream design decisions?

Upstream decisions are the best proxy we have for preferred form for
modification, since they are the ones who are working on the project.

Lets take the example of the obfuscated Xorg nv driver. NVIDIA had some
released driver code, but they were not developing that code. Instead
they had some secret internal code that they developed. Their release
process was to automatically obfuscate the code by expanding macros and
replacing constants with numeric values and other things. Clearly their
preferred form for modification was that internal code and not the
released code. This was a DFSG violation because upstream and Debian
users did not have equivalent access to the work.

Another example is Perl. Perl has a Configure script that the Debian
Perl Team has declared is source. Helmut Grohne found a bug in that
script that prevented it from working in cross-compilation scenarios.
He attempted to send a patch for it upstream but discovered that it was
in fact generated from another file (so wasn't source despite what the
Debian Perl team said) and the issue was already fixed in the other
file but the Configure script hadn't been built from source in ages and
it couldn't be built any more. This highlights that we need to be
always (re-)building from source in order to detect FTBFS and to prove
to our users that they have the freedom to modify and rebuild Debian.

Both of these are slightly different to Firacode, which is the fair bit
more straight forward issue of non-free Build-Depends. Based solely on
the commits in their github repo, the source for Firacode is the
.glyphs file and not the TTF/etc files. To convert that to the other
formats, you currently need the proprietary Glyphsapp. According to
Debian Policy, that means the font belongs in contrib because we can't
guarantee to our users that they will be able to modify the source and
rebuild the font using only packages in Debian main. Upstream and
Debian main users do not have equivalent access to the work.

> Well, RMS himself told me that the Type1 format in which the fonts are
> distributed is considered a proper source format. Apparently he doesn't
> even care about what tools upstream used to create the fonts as long as
> they are distributed in a proper source format.

The point I've been trying to make so far is that what the proper
source format is, is completely dependent on the development scenario.
It can be the source format or it can not be the source format,
depending on the development processes upstream chose for the fonts.

Quite unrelated to that is whether or not it is a good choice of source
format or not. As a software developer used to version control I find
binary formats a poor choice but upstream might have really great font
tools that deal fine with binary fonts by doing visual comparisons.

> Agreed, but I don't think that this (i.e. "is it easy or even possible
> to create a patch that upstream would outright accept in that form?")
> should be a criterion to decide if a package is suitable for Debian
> main or not (as long as it is possible to create the patch in the first
> place, that is).

Ack, I wasn't suggesting that. I was suggesting that this is the best
way to determine which files in the upstream repository are source and
which are not source. Doing that would really be forcing the issue
though. You really don't need to go that far, for Firacode you just
need to look at the commits in the repository to determine that.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#852150: .rdp file 852150: Acknowledgement (Remmina builds wrong cmd line for FreeRDP for RDP gateway connection ))

[dh]

 Duncan Hare

714 931 7952

 
- Forwarded Message -
 From: Debian Bug Tracking System 
 To: d...@synoia.com 
 Sent: Saturday, January 21, 2017 8:24 PM
 Subject: Bug#852150: Acknowledgement (Remmina builds wrong cmd line for 
FreeRDP for RDP gateway connection ))
   
Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Jörg Frings-Fürst 

If you wish to submit further information on this problem, please
send it to 852...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

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

   

cpub-iVenture_RDS_Dem-iVenture_RDS_Dem-CmsRdsh.rdp
Description: application/rdp

Bug#852149: firefox-esr: Firefox crashes in various circunstances

[Jean-Philippe MENGUAL]

Package: firefox-esr
Version: 45.6.0esr-1
Severity: important

Dear Maintainer,

Hi,

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

   * What led up to the situation?

The central problem has appeared when I updated Firefox in testing.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

When I open Firefox, then exit with alt-f4, it often crashes opening the
crash reporter wizard. I never know why, as no apparent problem.

When I go to a website an user asked me to test, I get the same. But moreover,
I get a Firefox which uses all CPU resources, is slow, I need to exit. This
happens when I open a user account. If I am anonymous, everything is good.

If I run gdb, see the results. Firefox crashes. After bt full, I exit Firefox
with alt-f4. The crash reporter wizard appears.

   * What was the outcome of this action?

Slow, CPU spent, and crash if tested on gdb.

   * What outcome did you expect instead?

1st, the wizard shouldn't appear. 2nd on any website, should work fine.

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

Available for any further test is helpful or to forward.

Regards,


-- Package-specific info:


-- Addons package information

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.1
ii  fontconfig2.11.0-6.7
ii  libasound21.1.2-1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-8
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.14-1
ii  libdbus-glib-1-2  0.108-1
ii  libevent-2.0-52.0.21-stable-2.1
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.2.1-5
ii  libgdk-pixbuf2.0-02.36.3-1
ii  libglib2.0-0  2.50.2-2
ii  libgtk2.0-0   2.24.31-1
ii  libhunspell-1.4-0 1.4.1-2+b1
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.26.2-1
ii  libpango-1.0-01.40.3-3
ii  libsqlite3-0  3.16.2-1
ii  libstartup-notification0  0.12-4
ii  libstdc++66.2.1-5
ii  libvpx4   1.6.0-3
ii  libx11-6  2:1.6.4-2
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3
ii  zlib1g1:1.2.8.dfsg-4

Versions of packages firefox-esr recommends:
ii  gstreamer1.0-libav 1.10.2-1
ii  gstreamer1.0-plugins-good  1.10.2-1

Versions of packages firefox-esr suggests:
ii  fonts-lmodern  2.004.5-3
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-3
pn  libgnomeui-0   
ii  libgssapi-krb5-2   1.15-1
pn  mozplugger 

-- debconf-show failed
$ gdb --args firefox-esr -safe-mode 
[37@MOZILLA_DISABLE_PLUGINS=1 
firefox-esr
GNU gdb (Debian 7.12-4) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from firefox-esr...Reading symbols from 
/home/debug//usr/lib/firefox-esr/firefox-esr...done.
done.
(gdb) run set pagination off
(gdb) run
Starting program: /usr/bin/firefox-esr -safe-mode
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe71aa700 (LWP 21751)]
[Thread 0x7fffe71aa700 (LWP 21751) exited]
[New Thread 0x7fffe71aa700 (LWP 21753)]
[New Thread 0x7fffe44ff700 (LWP 21754)]
[New Thread 0x77fde700 (LWP 21755)]
[New Thread 0x7fffe3cfe700 (LWP 21756)]
[New Thread 0x7fffe30f2700 (LWP 21757)]
[New Thread 0x7fffe2ef1700 (LWP 21758)]
[New Thread 0x7fffe2cf0700 (LWP 21759)]
[New Thread 0x7fffe2aef700 (LWP 21760)]
[New Thread 0x7fffe28ee700 (LWP 

Bug#852150: Remmina builds wrong cmd line for FreeRDP for RDP gateway connection )

[dh]

Package: remmina


Version: 1.1.1-2
Severity: important
Remmina builds a command line to launch for FreeRDP in the Microsoft RDP 
environment.
In the RDP gateway environment there are two DNS names for connection. A 
Gateway name and Server name.
After importing the .rdp file, then launching the access, 

Remmina builds a command line to connect to the server, however in this 
environment Remmina should build a command line to connect to the gateway. 

In addition remmina should set the parameter to ignore certificate errors as 
documented in:
http://github.com/FreeRDP/Remmina/issues/347 at the date 28 February 2015

Further discussions are at:

http://ubuntuforums.org/showthread.php?t=2259430
In a previous bug report the remote desktop access problem was forwarded to 
rDesktop, which is not the remote desktop package installed with remmina.

.rdp file to follow after bug is opened.
In addition remmina should not store passwords, as this is a large potential 
security exposure.
   

Bug#841401: Bug#851927: chromium: Update removed all (local) installed extensions

[Michael Gilbert]

control: reopen -1

The updater patch is mistakenly still applied.

Best wishes,
Mike

Bug#852090: Bug#851897: dgit: please have generated source packages contain standard patch series

[Sean Whitton]

Hello again,

We've two separate bugs, but I'll just address my feedback to both of
them, to minimise the number of e-mails you two receive.  I'm sorry for
not having made best use of the BTS 'clone' command earlier today.

 changes to manpage introduction (#852090) 

On Sat, Jan 21, 2017 at 06:21:04PM +, Ian Jackson wrote:
>   @@ -23,7 +23,9 @@ the usefulness of the raw Debian source package.  The 
> Debian archive
>is thought of as an output format.
> 
>For example, we don't spend time curating a series of quilt patches.
>   -However, the information such a series would contain is readily
>   +However,
>   +in straightforward cases,
>   +the information such a series would contain is readily
>available from B.
> 
> This sentence wasn't quite true (as Daniel points out) without
> qualification.

Fine with me.

>=item
>   @@ -34,6 +36,17 @@ that upstream makes available for download.
> 
>=back
> 
>   +This workflow is less suitable for some packages.
>   +When the Debian delta contains multiple pieces which interact,
>   +or which you aren't going to be able to upstream soon,
>   +it might be preferable to
>   +maintain the delta as a rebasing patch series,
> 
> This part is from the most recent suggestion, from Daniel.

Good.

> I suggest adding this part...
> 
>   +to facilitate
>   +reviewing/upstreaming/dropping
>   +individual pieces.
> 
> ... because I agreed with Daniel's point about rationales.

I would still prefer not to include this.

>   +For such a workflow see for example
>   +dgit-maint-gbp(7).
> 
> And I think a cross-reference is helpful here so the advice isn't a
> dead-end.

Good.  I would also refer to #720177, partially so that we remember to
replace it with a reference to dgit-maint-rebase(7) once that exists.

 changes to patch header (#851897) 

On Sat, Jan 21, 2017 at 08:42:40PM +, Ian Jackson wrote:
> I now have:
> 
>The Debian packaging of foo is maintained in git,
>using the merging workflow described in dgit-maint-merge(7).
>  | There isn't a patch queue that can be represented as a quilt series.
> 
>A detailed breakdown of the changes is available from their

s/the changes/the Debian delta/

Thanks to the removal of the "automatically generated" sentence, "the
changes" has lost its referent.  And since we use "changes" in the next
paragraph, a "delta" here reads better.

>canonical representation -
>git commits in the packaging repository.
>For example, to see the changes made by the Debian maintainer in the
>first upload of upstream version 1.2.3, you could use:
> 
>=over 4
> 
>% git clone https://git.dgit.debian.org/
>% cd foo
>% git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian'
> 
>=back
> 
>See dgit-maint-merge(7) for more information.
>(If you have dgit, use dgit clone foo,
>rather than plain git clone.)
> 
>  | A single combined diff, containing all the changes, follows.

Consider dropping one of either

>using the merging workflow described in dgit-maint-merge(7).

or

>See dgit-maint-merge(7) for more information.

as we don't need two references to the manpage.  I would suggest
dropping the latter.

On Sat, Jan 21, 2017 at 06:21:04PM +, Ian Jackson wrote:
> Sean writes:
> > I don't think the `dgit clone` need be given since the `git clone` will
> > contain git.dgit.debian.org, so anyone even slightly familiar with dgit
> > will know they can use `dgit clone` if they want to.
>
> I don't think they will necessarily know that it's advisable.  There
> are a two reasons I can think of why `dgit clone' is better:
>
>  * It will include changes made in non-dgit-based uploads (eg NMUs).

Good point, I hadn't thought of NMUs.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#831805: [pkg-wicd-maint] Bug#831805: wicd-daemon: Not all PEAP/MS-CHAP-V2 networks require a "Domain" field

[Axel Beckert]

Hi,

Giap Tran wrote:
> Yesterday, we have received a new bug from report bugs system.
> Bug#831805: wicd-daemon: Not all PEAP/MS-CHAP-V2 networks require a
> "Domain" field.
> 
> I have searched this bug in Upstream. There have some bug same:
> 
> - https://bugs.launchpad.net/wicd/+bug/897399 (Identity/Domain problem
> in PEAP Edit) in 2011
> Dev report fixed,

Yes, but the patch found in that bug report
(https://bugs.launchpad.net/wicd/+bug/897399/+attachment/3414734/+files/wicd-897399)
doesn't fit what I would expect as patch for this issue.

> but a person reported it not fixed.
>
> > This problem still exists in 2015, isn't the fix going to be accepted
> > into the upstream code?

I assume the initial bug report was about two separate bugs which were
not clearly distinguishable back then and only one of them git fixed
while the other is still present:

> - https://bugs.launchpad.net/wicd/+bug/1591489 in 11/06/2016
> (no for answer)
> 
> I think #897399 have a patch fixed, but upsteam doesn't apply it.

No, upstream applied it and the current Debian package contains that
patch.

I'll probably add the additional template suggested in Launchpad as
well as in the Debian BTS.

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#852079: Problem in universal media server.

[Aldrin P. S. Castro]

When I use the server in my network that have a TV sony bravia model 
kdl32bx305 It does not appear in my tv. However others servers like 
Imediashare appear in it. If The Debian team decide to pack, could fix 
this problem.

Bug#851986: [request-tracker-maintainers] Bug#851986: rt-extension-sla: Obsolete with RT 4.4

[Joost van Baal-Ilić]

On Fri, Jan 20, 2017 at 03:38:31PM +, Dominic Hargreaves wrote:
> Source: rt-extension-sla
> Version: 1.04-2
> Severity: serious
> Justification: obsolete, uninstallable
> 
> With the upload of RT 4.4 to unstable, this separate package is
> obsoleted - RT 4.4 includes the SLA functionality out of the box. As
> such, rt-extension-sla should not be released with stretch.

Thanks for reporting this; you are right.

FWIW; rt-extension-sla has been packaged to be useful for people running
jessie/stable.  I am running it on jessie production systems.

I am wondering if it would be usefull to have rt-extension-sla in unstable for
the next couple of months...  Unfortunately, as long as it is not in testing,
it can't be in backports either; due to the backports policy :( .

Bye,

Joost

Bug#848930: kills fellow process if window doesn't have focus

[Michael Gilbert]

control: tag -1 moreinfo, upstream

Did versions prior to the latest security update do this?  Is there an
upstream bug about it?  If not, please submit one and link back here.

Best wishes,
Mike

Bug#851724: python-llfuse: FTBFS (failing tests)

[Santiago Vila]

On Sat, Jan 21, 2017 at 04:12:28PM -0800, Nikolaus Rath wrote:

> Are you able to reproduce this with Python 3.5?

I don't know. I'm just building the package from source.

The package currently build-depends on both python-all-dev and python3-all-dev.

By "trying with Python 3.5" you mean removing the build-dependency on 
python-all-dev?

Thanks.

Bug#784578: kodi: Can't play DVDs locally or from samba shares

[Michel]

Package: kodi
Version: 2:17.0~rc3+dfsg1-1
Followup-For: Bug #784578

Dear Maintainer,

problem still exists in 17rc3. 
It seems to me that kodi hangs when trying to open the libdvdcss library.
gdb stack strace of the dvdnav thread is provided below.

Please let me know which additional information may be useful,
Michel


Reading symbols from /usr/lib/x86_64-linux-gnu/kodi/kodi.bin...Reading symbols 
from 
/usr/lib/debug/.build-id/79/0438b053381d2e97d27fd62fc4954ce88f3ee5.debug...done.
done.
Starting program: /usr/lib/x86_64-linux-gnu/kodi/kodi.bin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffd03a7700 (LWP 21399)]
[New Thread 0x7fffcfba6700 (LWP 21400)]
[Thread 0x7fffcfba6700 (LWP 21400) exited]
[New Thread 0x7fffcfba6700 (LWP 21401)]
[New Thread 0x7fffcf191700 (LWP 21402)]
[New Thread 0x7fffce990700 (LWP 21403)]
[New Thread 0x7fffce18f700 (LWP 21404)]
[New Thread 0x7fffcd98e700 (LWP 21405)]
[Thread 0x7fffcd98e700 (LWP 21405) exited]
[New Thread 0x7fffcd98e700 (LWP 21408)]
[New Thread 0x7fffa61c1700 (LWP 21409)]
[New Thread 0x7fffa59c0700 (LWP 21410)]
[New Thread 0x7fffa51bf700 (LWP 21411)]
[New Thread 0x7fffa49be700 (LWP 21412)]
[New Thread 0x7fffa66a4700 (LWP 21413)]
[New Thread 0x7fff97715700 (LWP 21414)]
[New Thread 0x7fff96f14700 (LWP 21415)]
[New Thread 0x7fff96713700 (LWP 21416)]
[New Thread 0x7fff95f12700 (LWP 21417)]
[New Thread 0x7fff95711700 (LWP 21418)]
[New Thread 0x7fff94f10700 (LWP 21419)]
[New Thread 0x7fff7700 (LWP 21420)]
[New Thread 0x7fff7f7fe700 (LWP 21421)]
[New Thread 0x7fff7effd700 (LWP 21422)]
[New Thread 0x7fff7e7fc700 (LWP 21423)]
[New Thread 0x7fff7dffb700 (LWP 21424)]
[New Thread 0x7fff7d7fa700 (LWP 21425)]
[New Thread 0x7fff7cff9700 (LWP 21426)]
[New Thread 0x7fff6bfff700 (LWP 21427)]
[New Thread 0x7fff6b7fe700 (LWP 21428)]
[New Thread 0x7fff6affd700 (LWP 21429)]
[New Thread 0x7fff6a7fc700 (LWP 21430)]
[New Thread 0x7fff69ffb700 (LWP 21431)]
[New Thread 0x7fff697fa700 (LWP 21432)]
[New Thread 0x7fff68ff9700 (LWP 21433)]
[New Thread 0x7fff53fff700 (LWP 21434)]
[Thread 0x7fff7d7fa700 (LWP 21425) exited]
[Thread 0x7fff7cff9700 (LWP 21426) exited]
[New Thread 0x7fff7cff9700 (LWP 21435)]
[New Thread 0x7fff7d7fa700 (LWP 21436)]
[New Thread 0x7fff537fe700 (LWP 21437)]
[New Thread 0x7fff52ffd700 (LWP 21438)]
[Thread 0x7fff537fe700 (LWP 21437) exited]
[Thread 0x7fff52ffd700 (LWP 21438) exited]
[Thread 0x7fff7dffb700 (LWP 21424) exited]
[Thread 0x7fff6bfff700 (LWP 21427) exited]
[Thread 0x7fff6b7fe700 (LWP 21428) exited]
[Thread 0x7fff6a7fc700 (LWP 21430) exited]
[Thread 0x7fff7cff9700 (LWP 21435) exited]
[Thread 0x7fff7d7fa700 (LWP 21436) exited]
[Thread 0x7fff69ffb700 (LWP 21431) exited]
[Thread 0x7fff697fa700 (LWP 21432) exited]
[Thread 0x7fff68ff9700 (LWP 21433) exited]
[Thread 0x7fff53fff700 (LWP 21434) exited]
[New Thread 0x7fff53fff700 (LWP 21439)]
[Thread 0x7fff53fff700 (LWP 21439) exited]
[New Thread 0x7fff53fff700 (LWP 21440)]
[Thread 0x7fff53fff700 (LWP 21440) exited]
[New Thread 0x7fff53fff700 (LWP 21441)]
[Thread 0x7fff53fff700 (LWP 21441) exited]
[New Thread 0x7fff53fff700 (LWP 21442)]
[Thread 0x7fff96f14700 (LWP 21415) exited]
[Thread 0x7fff97715700 (LWP 21414) exited]
[Thread 0x7fffcfba6700 (LWP 21401) exited]

Thread 1 "kodi.bin" received signal SIGINT, Interrupt.
pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:180
180 ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S: No such 
file or directory.

Thread 43 (Thread 0x7fff53fff700 (LWP 21442)):
#0  __wrap_dlopen (filename=0x7fffa6e9554d "libdvdcss.so.2", flag=1) at 
wrapper.c:123
No locals.
#1  0x7fffa6e76c7f in dvdinput_setup () at src/dvd_input.c:313
dvdcss_library = 0x0
#2  0x7fffa6e772d1 in DVDOpenCommon (ppath=ppath@entry=0x7fff640021a0 
"/var/local/test.iso", stream=stream@entry=0x0, stream_cb=stream_cb@entry=0x0) 
at src/dvd_reader.c:385
fileinfo = {st_dev = 0, st_ino = 0, st_nlink = 8028562942127975800, 
st_mode = 1932487012, st_uid = 1702130553, st_gid = 0, __pad0 = 0, st_rdev = 0, 
st_size = 8243128152309641069, st_blksize = 5795962727387508595, st_blocks = 0, 
st_atim = {tv_sec = 0, tv_nsec = 8028562942127975800}, st_mtim = {tv_sec = 
7310595060589881700, tv_nsec = 0}, st_ctim = {tv_sec = 0, tv_nsec = 31996}, 
__glibc_reserved = {15, 0, 62}}
have_css = 
ret_val = 0x0
dev_name = 0x0
path = 0x7fff64001eb0 "/var/local/test.iso"
path_copy = 0x0
#3  0x7fffa6e78469 in DVDOpen (ppath=ppath@entry=0x7fff640021a0 
"/var/local/test.iso") at src/dvd_reader.c:636
No locals.
#4  0x7fffa6e927c5 in vm_reset (vm=0x7fff64012850, 
dvdroot=dvdroot@entry=0x7fff640021a0 "/var/local/test.iso", 
stream=stream@entry=0x0, stream_cb=stream_cb@entry=0x0) at src/vm/vm.c:381
No locals.
#5  0x7fffa6e8a329 in dvdnav_open_common (dest=0x7fff64004bd0, 
path=0x7fff640021a0 "/var/local/test.iso", stream=0x0, 

Bug#851724: python-llfuse: FTBFS (failing tests)

[Nikolaus Rath]

On Jan 17 2017, Santiago Vila  wrote:
> Exception in thread Thread-1 (most likely raised during interpreter shutdown):
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
>   File "/usr/lib/python2.7/threading.py", line 754, in run
>   File "src/misc.pxi", line 261, in llfuse._notify_loop (src/llfuse.c:29495)
>   File "/usr/lib/python2.7/Queue.py", line 179, in get
>   File "/usr/lib/python2.7/threading.py", line 384, in notify
> : 'NoneType' object is not callable
>  Interrupted: stopping after 1 failures 
> 

Thanks for reporting. This looks like a bug in Python 2.7
itself. Calling Queue.get() (a standard library class) should never fail
like that. Probably the best solution is for the test to ignore errors
during interpreter shutdown.

Are you able to reproduce this with Python 3.5?


Thanks,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

Bug#852082: gwc in testing crashes at startup

[James Cowgill]

Control: severity -1 grave

Hi,

[Jaromír: please send mail to the bug, not the list]

On 21/01/17 14:18, Christian Grigis wrote:
> Package: gwc
> Version: 0.21.19~dfsg0-6
> Severity: important
> 
> Running 'gnome_wave_cleaner' from the testing package version
> (0.21.19~dfsg0-6) crashes immediately at startup:
> 
> $ gnome_wave_cleaner 
> Current stack limit: 8388608 bytes
> Segmentation fault

This bug is clearly RC. Jaromír, you did test this before uploading it
right?

[...]
> The gdb backtrace gives:
> 
> (gdb) run
> Starting program: /home/glove/tmp/gwc-testing/gwc-0.21.19~dfsg0/gwc 
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Current stack limit: 8388608 bytes
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x76e047f9 in g_type_is_a () from 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> (gdb) bt
> #0  0x76e047f9 in g_type_is_a () from 
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #1  0x77519084 in gtk_type_new () from 
> /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
> #2  0x5557223c in led_bar_new (segments=20, orientation=0) at 
> gtkledbar.c:82

The problem is here. led_bar_get_type returns an unsigned int, but
gtk_type_new expects a "GtkType" which is an integer with the same size
as a pointer. This code is going to need porting to work on 64-bit arches.

> I experimented with optimization levels but even -O0 gives the crash.
> 
> However, it looks like it is related to the compiler, because forcing to
> compile with gcc-5 instead of gcc-6 produces a binary that starts up
> normally.

This is probably related to PIE being enabled. I suspect that without
PIE (and therefore ASLR), by chance all the pointers were < 4GB so the
bug never occurred.

James



signature.asc
Description: OpenPGP digital signature

Bug#792075: doesn't seem to have any movement at all on git-lfs

[shirish शिरीष]

Hi all,

Doesn't seem to have any acitivity on the packaging. I did see that
upstream released the latest just a few days back.

https://github.com/git-lfs/git-lfs/releases

v 1.5.5

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#850968: CVE-2016-2788

[Christian Hofstaedtler]

* Moritz Muehlenhoff  [170121 23:16]:
> Source: mcollective
> 
> Please see https://puppet.com/security/cve/cve-2016-2788

Looks like the fix is in this commit/merge:
https://github.com/puppetlabs/marionette-collective/commit/4918a0f136aea04452b48a1ba29eb9aabcf5c97d

I've checked the 2.6.x branch and it appears to have the vulnerable
code too.

-- 
christian hofstaedtler 

Bug#809692: Build content module

[Michael Gilbert]

control: retitle -1 RFP: libchromiumcontent -- content module
control: reassign -1 wnpp

I recently added a chromium-shell package, but I don't think that's
quite what you're looking for.

You're probably looking for something like libchromiumcontent [0]?

Best wishes,
Mike

[0] https://github.com/electron/libchromiumcontent

Bug#852147: sawfish: Upstream version 1.12.0 available since August 06

[Jose Antonio Ortega Ruiz]

Package: sawfish
Version: 3:1.12.0-1nano
Severity: normal

Dear Maintainer,

I am using the .debs provided upstream by Christian, but it'd be very
nice if sawfish's packages in debian be updated to the latest version,
1.12.0, so that we don't need to depend on non-official repositories.

Thanks a lot!
jao

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

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

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


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

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

Versions of packages sawfish depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgmp10 2:6.1.2+dfsg-1
ii  libgtk2.0-0  2.24.31-1
ii  libice6  2:1.0.9-1+b1
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  libpangoxft-1.0-01.40.3-3
ii  librep16 3:0.92.6-1nano
ii  libsm6   2:1.2.2-1+b1
ii  libx11-6 2:1.6.4-2
ii  libxext6 2:1.3.3-1
ii  libxft2  2.3.2-1
ii  libxinerama1 2:1.1.3-1+b1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxtst6 2:1.2.3-1
ii  rep  3:0.92.6-1nano
ii  rep-gtk  3:0.90.8.3-1nano
ii  rxvt-unicode-256color [x-terminal-emulator]  9.22-1+b1
ii  sawfish-data 3:1.12.0-1nano
ii  xterm [x-terminal-emulator]  327-2

sawfish recommends no packages.

sawfish suggests no packages.

-- no debconf information

Bug#852148: RFS: zodb/1:3.10.7-2

[Julien Muchembled]

Package: sponsorship-requests
Severity: normal

 Dear mentors,

 I am looking for a sponsor for my package "zodb"

* Package name: zodb
  Version : 1:3.10.7-2
  Upstream Author : Zope Foundation and Contributors 
* URL : http://zodb.org/
* License : Zope-2.1
  Section : python

 It builds this binary package:

   python-zodb - Zope Object Database (ZODB)

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

   https://mentors.debian.net/package/zodb

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

   dget -x https://mentors.debian.net/debian/pool/main/z/zodb/zodb_3.10.7-2.dsc

 Changes since the last upload:

zodb (1:3.10.7-2) unstable; urgency=medium

  * Team upload.
  * New upstream release 3.10.7
- drop patches merged upstream:
  Fix-possible-data-corruption-after-FileStorage-is-tr.patch
  * Use pybuild instread of van.pydeb.
  * Use debhelper 10.
  * d/control:
- Drop 'Conflicts: zope3': this package was removed long time ago.
- Update Standards-Version to 3.9.8 (no change needed).
- Use HTTPS for Vcs-Browser.
- Set section back to 'python'. As clarified upstream:
  « ZODB doesn't depend on Zope in any way and is used in many projects
that have nothing to do with Zope. »
  This also fixes an override disparity.
  * d/copyright: update Copyright: year.
  * d/watch: fix by refreshing it from pypi.debian.net

 Regards,
  Julien Muchembled



signature.asc
Description: OpenPGP digital signature

Bug#687463: ocsinventory-agent: fails to purge - command ucf in postrm not found

[Andreas Beckmann]

Followup-For: Bug #687463
Control: tag -1 pending patch

Hi,

I just uploaded a NMU to DELAYED/2 that makes the ucf usage during
postrm purge conditional. This should reach stretch just before the
freeze.


Andreas
diff -u ocsinventory-agent-2.0.5/debian/changelog ocsinventory-agent-2.0.5/debian/changelog
--- ocsinventory-agent-2.0.5/debian/changelog
+++ ocsinventory-agent-2.0.5/debian/changelog
@@ -1,3 +1,10 @@
+ocsinventory-agent (2:2.0.5-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * postrm purge: Only run ucf if it is available.  (Closes: #687463)
+
+ -- Andreas Beckmann   Sun, 22 Jan 2017 00:00:41 +0100
+
 ocsinventory-agent (2:2.0.5-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u ocsinventory-agent-2.0.5/debian/ocsinventory-agent.postrm ocsinventory-agent-2.0.5/debian/ocsinventory-agent.postrm
--- ocsinventory-agent-2.0.5/debian/ocsinventory-agent.postrm
+++ ocsinventory-agent-2.0.5/debian/ocsinventory-agent.postrm
@@ -21,10 +21,12 @@
 
 case "$1" in
 purge)
-  ucf --purge /etc/ocsinventory-client/ocsinv.conf
-  ucf --purge /etc/ocsinventory/ocsinventory-agent.cfg
   rm -f /etc/ocsinventory-client/ocsinv.conf
   rm -f /etc/ocsinventory/ocsinventory-agent.cfg
+  if which ucf >/dev/null; then
+ucf --purge /etc/ocsinventory-client/ocsinv.conf
+ucf --purge /etc/ocsinventory/ocsinventory-agent.cfg
+  fi
   rm -f /var/lib/ocsinventory-agent/ocsinv.adm
   rm -f /usr/share/ocsinventory-client/ocsinv.conf
   rm -f /usr/share/ocsinventory-client/ocsinv.adm

Bug#851692: chromium: startup script is disabling all extensions

[Daniel Serpell]

Package: chromium
Version: 55.0.2883.75-5
Followup-For: Bug #851692

Hi!

The attached patch to the chromium launcher script allows enabling
extensions by adding a file to /etc/chromium.d/ with the line:

   CHROME_ENABLE_REMOTE_EXTENSIONS=1

Currently, it is really difficult to enable extensions, so my adblock
extensions is disabled :-(

Thanks,



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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec-extra57   7:3.2.2-1
ii  libavformat577:3.2.2-1
ii  libavutil55  7:3.2.2-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-6
ii  libdbus-1-3  1.10.14-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.3.0-3
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.28-1
ii  libpulse010.0-1
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-3
ii  libvpx4  1.6.1-2
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-2
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
ii  chromium-l10n  55.0.2883.75-5
pn  chromium-shell 
ii  chromium-widevine  55.0.2883.75-5

-- no debconf information
--- chromium.orig   2017-01-21 19:57:28.782389670 -0300
+++ chromium2017-01-21 19:56:28.017972885 -0300
@@ -41,6 +41,9 @@
 ;;
 esac
 
+# Initial settings
+CHROME_ENABLE_REMOTE_EXTENSIONS=0
+
 # Source additional settings
 for file in /etc/chromium.d/*; do
   test $file = /etc/chromium.d/README || expr $file : .*\.dpkg > /dev/null || 
. $file
@@ -60,7 +63,6 @@
 
 want_debug=0
 want_temp_profile=0
-want_remote_extensions=0
 while [ $# -gt 0 ]; do
   case "$1" in
 -h | --help | -help )
@@ -73,7 +75,7 @@
   want_temp_profile=1
   shift ;;
 --enable-remote-extensions )
-  want_remote_extensions=1
+  CHROME_ENABLE_REMOTE_EXTENSIONS=1
   shift ;;
 -- ) # Stop option prcessing
   shift
@@ -84,7 +86,7 @@
 done
 
 # Whitelist installed extensions that are specified via --load-extension
-if [ $want_remote_extensions -eq 0 ]; then
+if [ $CHROME_ENABLE_REMOTE_EXTENSIONS -eq 0 ]; then
   export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --disable-extensions-except=$(echo 
$CHROMIUM_FLAGS | tr ' ' \\n | grep \\-\\-load-extension | cut -d= -f2 | tr \\n 
,)"
 fi
 

Bug#851026: ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen'

[Andreas Cadhalpun]

Hi,

On 19.01.2017 00:05, Bálint Réczey wrote:
> 2017-01-14 23:54 GMT+01:00 Adrian Bunk :
>> No, you should only look at the first compile error in that file:
>>
>> src/libavformat/chromaprint.c:42:24: error: field 'ctx' has incomplete type
>>  ChromaprintContext ctx;
>> ^~~
>> This is the actual error.
>>
>> Whatever the compiler comes up with for cpr->ctx in the place you quoted
>> might be garbage, but at that point it is already game over.
>>
>> Upstream fix:
>>   
>> http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=581f93f37ef2e7a00662828ed0348d1edb9041fe
>>
> 
> Is there a new FFmpeg upstream release on the horizon or I should just
> update the package with a cherry-picked patch?

The next FFmpeg upstream release will probably not be in time for the freeze,
so I've just cherry-picked this patch.

Best regards,
Andreas

Bug#850762: setserial: missing dependency on lsb-base

[Christian Hofstaedtler]

* Adrian Bunk  [170120 19:57]:
> Control: reopen -1
> 
> On Fri, Jan 20, 2017 at 12:42:38AM +0100, Christian Hofstaedtler wrote:
> > Hi,
> > 
> > * Andreas Beckmann  [170119 23:40]:
> > >   Selecting previously unselected package setserial.
> > >   (Reading database ... 
> > > (Reading database ... 4394 files and directories currently installed.)
> > >   Preparing to unpack .../setserial_2.17-49.1_amd64.deb ...
> > >   Unpacking setserial (2.17-49.1) ...
> > >   Setting up setserial (2.17-49.1) ...
> > >   removing the old setserial entry in the rcn.d directories
> > >   Update complete.
> > >   update-rc.d: warning: start and stop actions are no longer supported; 
> > > falling back to defaults
> > >   update-rc.d: warning: start and stop actions are no longer supported; 
> > > falling back to defaults
> > >   update-rc.d: warning: start and stop actions are no longer supported; 
> > > falling back to defaults
> > >   update-rc.d: warning: start and stop actions are no longer supported; 
> > > falling back to defaults
> > >   /etc/init.d/setserial: 35: .: Can't open /lib/lsb/init-functions
> > 
> > It is believed that this is fixed with the newer
> > init-system-helpers - the invoke-rc.d call should now be ignored in
> > chroots that miss an init system.
> > (And, if sysvinit is present, the missing file is present, or if
> > systemd is present, setserial.service is used instead.)
> 
> You are looking at the wrong line.
> The update-rc.d warnings are non-fatal warnings.
> 
> The error is the "Can't open /lib/lsb/init-functions" in the last line.

I was refering to that line.

> (lintian also gives an error for this bug.)

A very misguided one though.

I'll leave this for someone else to test, there may very well be
additional issues hiding in postinst.

Best,
-- 
christian hofstaedtler 

Bug#792150: jruby: Package 9.0.0.0 releases

[Miguel Landaeta]

# polyglot-maven is not really a blocker just a nice to have
unblock 792150 by 792149
block 792150 by 851197
block 792150 by 851350
thanks

Hi,

I made progress recently with this effort.

All the important missing dependencies were recently uploaded but not
all of them have been accepted yet.

https://ftp-master.debian.org/new/dirgra_0.3-1.html
https://ftp-master.debian.org/new/jitescript_0.4.1-2.html
https://packages.qa.debian.org/i/invokebinder.html
https://packages.qa.debian.org/j/jnr-constants.html
https://packages.qa.debian.org/j/jnr-ffi.html
https://packages.qa.debian.org/j/jnr-posix.html
https://packages.qa.debian.org/j/jnr-unixsocket.html
https://packages.qa.debian.org/libb/libbytelist-java.html

I should upload 9.1.6.0 or 9.1.7.0 to experimental soon.

Cheers,

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature

Bug#841642:

[Ayke van Laethem]

This could even be seen as a security issue - the display isn't hidden
at all using the screen lock, the only thing it does is making it
impossible to interact with it. So it is visible what the user was
doing when leaving the computer for some time.

Upstream bug:
https://github.com/mate-desktop/mate-screensaver/issues/103

It appears to be fixed with this patch:
https://github.com/mate-desktop/mate-screensaver/pull/110

It would be nice if this could go into stable stretch.

-- Ayke

Bug#852146: Changing board size while game window is maximized results in clipped output

[Evgeny Kapun]

Package: sgt-puzzles
Version: 20161228.7cae89f-1

In many games (such as Loopy, Palisade, Slant), it is possible to select 
different sizes of the game board (using Type menu). However, if this is done 
while game window is maximized, the result won't look right (usually, only the 
top level corner would be visible).

Bug#851806: ITP: libmseed2 -- seed (Standard for the Exchange of Earthquake Data) data records manipulation library

[Pierre Duperray]

Hi Andreas,


On 01/19/2017 03:05 PM, Andreas Tille wrote:

Hi Pierre,

On Thu, Jan 19, 2017 at 02:46:26PM +0100, Pierre Duperray wrote:

I'd be up for sponsoring if the package is in Debian Science Git following
Debian Science policy:

https://debian-science.alioth.debian.org/debian-science-policy.html

I read the link and wish to conform to the debian science policy.
I'd like to upload to a debian-science git repo but I can't log into
git.debian.org, it's said I have to belong to the group (debian science
maintainer?)
where should I apply?

You need to follow

 http://wiki.debian.org/Alioth/SSH

*exactly* step by step to be able to

 ssh git.debian.org

On

 https://alioth.debian.org/projects/debian-science/

(I think bottom right) is a link to apply for team membership.

It took me ages to log in, but hello alioth I'm in!



I admit I'm wondering into what task this package might belong -
suggestions?

by task you mean link to web sentinel ? (I'm new to this, I only use "pure"
debian)

Blends *are* *pure* Debian!  All the packages displayed on the web
sentinel are pure Debian packages but these are somehow organised in
respect of the people working on the packages and targeting a certain
user group.  Blends should simplify the usage for such user groups.


got it

there is nothing related to geophysics or seismology, perhaps the safer
choice would be science tool.
To me it's only a library to allow manipulation of "sismic" oriented data.
I hope soon be able to package software depending on libmseed2 for making
real science with this
freshly acquired data.

I think Ghislain's suggestion geography-dev makes a reasonable match.

not sure if geophysics/seismology is related to geography in any way...



Unless Andreas is already on it? I would also be happy to review the
packaging but cannot upload.

Ghislain, I'd welcome your review before it gets on my table for
sponsering.

thanks all for your next review/help/sponsoring

You are welcome (and welcoming newcomers is another feature of
Blends *inside* Debian ;-) )

Andreas.


thanks, I'm very happy and proud to belong to this team ;)


Right now, I'm learning git-package and to be honest even if not completely
noob in git I think I screwed my local git repo because instead of 
commiting in local master
the change I did, I first imported with `gbp pq import' my already done 
debian/patches.
after commiting a few change to master I realized my patch-queue/master 
is completely
unrelated to my master commits. I though I could work around this with 
an interactive

rebase but I'm not sure where I'm standing now :)
I will clone back my initial alioth master branch and start from scratch.
Sorry for the delay, but I really need to learn more indepth gbp.

If I manage to make this clear, I will then contact upstream to submit 
my patches
and try to agree on a better approach of his library versionning which 
will be a pb for debian
(wrong age revision and such, that was the primary reason why I 
autotoolized for using libtool)


Cheers,

Pierre

Bug#851927: chromium: Update removed all (local) installed extensions

[Michael Gilbert]

control: severity -1 wishlist
control: retitle -1 chromium: add extensions option to CHROMIUM_FLAGS

This update does not remove anything, so there is no reason to think
there is data loss.

I agree that setting the option in CHROMIUM_FLAGS should be supported.

Best wishes,
Mike

Bug#852145: +1 for targetting

[Adam Borowski]

> targetted and targetting are valid alternative spellings

I agree -- in Crawl's upstream, we had a very lengthy flamewar about this
topic (that game's original author was an australian, thus .au spelling is
preferred):

* US uses -t- exclusively
* UK allows both although -t- is more prevalent than -tt- these days
* AU uses mostly -tt- but -t- is (per foreign influence) also often seen

Thus, it is a minority spelling, and it might even be reasonable for a
general purpose spelcheckar to complain -- usual spell checkers are expected
to have a fair rate of false positives.  It takes more work to ignore a
Lintian warning, though.

A dubious warning might be appropriate for functional problems; for
spelling, though, I'd suggest marking up only certain ones.


Meow!
-- 
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
  ./configure --host=zx-spectrum --build=pdp11

Bug#737106: Ping?

[gregor herrmann]

On Sat, 21 Jan 2017 10:40:49 +0100, Elena ``of Valhalla'' wrote:

> > It looks like we something working in git; we finally went for the
> > tri-state solution if the fav button (no / weak / strong).
> > 
> > I'll try to get something out tomorrow; unless you want to try and
> > build from git yourself to take a look:
> > http://git.toastfreeware.priv.at/toast/confclerk.git
> 
> That's great, thanks!

Thanks for trying and reporting back!
 
> I've only stumbled on one UI issue: when something is half-starred and
> you're browsing it from the favourites view there is no way to turn it
> into a full star, because clicking on the star goes through the
> unstarred phase and removes it from the view.

Ack, that's annoying.
 
> On the PC using right click to go through the states in
> the opposite direction looks to me like a natural interface to work
> around the problem (and it would work on the Pandora / Pyra, even if
> it's a bit less natural); 

Implemented by my co-author Philipp in Git.

> I'm not sure how well it would work on other
> mobile devices (maybe long tap? I don't know how easy/hard it would be
> to do it with QT).

AFAIK at least on Maemo it's the system qt which re-maps right-click
to long tap. So I hope this will Just Work™ (have to test it
tomorrow).
 
> Anyway, you've just made my fosdem experience MUCH smoother, THANKS!

That's good to hear :)


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: Tracy Chapman: Hard Wired


signature.asc
Description: Digital Signature

Bug#834032: dict-gcide: fails to purge - command in postrm not found

[Andreas Beckmann]

Control: severity -1 serious

On 2016-08-16 20:15, Ritesh Raj Sarraf wrote:
> So, to summarize, let's hold this bug for a month or two.
> If I get dico done by then, then we'll just drop this package altogether.
> OTOH, if that doesn't happen in time, I'll do an upload for this one.

> Please feel free to mark it RC eventually, if it isn't done by then

Doing so now, but only because I found another issue while reviewing
your patch: restarting dictd in postrm purge will also fail if dictd is
no longer installed. This issue is not found by piuparts since its
policy-rc.d forbits starting/stopping services.

doing this manually in a chroot results in

# dpkg --purge dict-gcide
(Reading database ... 15410 files and directories currently installed.)
Purging configuration files for dict-gcide (0.48.2) ...
invoke-rc.d: unknown initscript, /etc/init.d/dictd not found.
dpkg: error processing package dict-gcide (--purge):
 subprocess installed post-removal script returned error exit status 100
Errors were encountered while processing:
 dict-gcide


I also do not see any point why you would want to run dictdconfig during
purge and restart dictd:

* dict-gcide has no conffiles
* dict-gcide does no cleanup in its postrm purge

there is no point in "touching" dictd at all again during postm purge -
all neccessary operations have been done already during postrm remove.


I'd suggesst this minimal postrm script (do not check for unknown
arguments!):

#!/bin/sh
set -e
if [ "$1" = "remove" ]; then
dictdconfig -w
invoke-rc.d dictd restart
fi
#DEBHELPER#


Andreas

Bug#851620: partman-md: doesn't warn about not being able to embed in the end

[Samuel Thibault]

Hello,

Please remember that the submitter is *not* mailed when
n...@bugs.debian.org is mailed.  I just happen to be subscribed to
d-b@...

Roger Lynn, on Sat 21 Jan 2017 21:50:18 +, wrote:
> On 16/01/17 22:00, Samuel Thibault wrote:
> > partman-md doesn't warn when disks to be used for RAID are partitioned
> > with GPT without a bios boot partition for embedding (and I haven't seen
> > documentation about the issue in the installer manual).
> 
> Is this the same problem that was reported in installation-report bug
> #768624 "grub core.img won't fit in the embedding area which is required for
> LVM"?

It doesnt look so: "It won't fit in the embedding area.", I'm not
getting this message: I don't even have an embedding area with the GPT
partition.

Samuel

Bug#851620: partman-md: doesn't warn about not being able to embed in the end

[Roger Lynn]

On 16/01/17 22:00, Samuel Thibault wrote:
> partman-md doesn't warn when disks to be used for RAID are partitioned
> with GPT without a bios boot partition for embedding (and I haven't seen
> documentation about the issue in the installer manual).

Is this the same problem that was reported in installation-report bug
#768624 "grub core.img won't fit in the embedding area which is required for
LVM"?

Roger

Bug#847282: imagemagick-doc: fails to upgrade wheezy -> jessie -> stretch

[Andreas Beckmann]

Followup-For: Bug #847282
Control: found -1 8:6.9.7.0+dfsg-2

Hi,

there are still a few traces left from this bug:

  Preparing to unpack .../imagemagick-doc_8%3a6.9.7.0+dfsg-2_all.deb ...
  dpkg-maintscript-helper: error: directory '/usr/share/doc/imagemagick-doc' 
contains files not owned by package imagemagick-doc:all, cannot switch to 
symlink
  dpkg: error processing archive 
/var/cache/apt/archives/imagemagick-doc_8%3a6.9.7.0+dfsg-2_all.deb (--unpack):
   subprocess new pre-installation script returned error exit status 1

some info from the chroot:

# ls -la /usr/share/doc/imagemagick-doc
total 176
drwxr-xr-x   4 root root   220 Jan 21 21:57 .
drwxr-xr-x 117 root root  2500 Jan 21 21:59 ..
-rw-r--r--   1 root root   991 Nov 25 20:45 NEWS.Debian.gz
-rw-r--r--   1 root root 32429 Nov 25 20:45 changelog.Debian.gz
-rw-r--r--   1 root root 77347 Oct 25  2014 changelog.gz
-rw-r--r--   1 root root 42835 Nov 25 20:45 copyright
drwxr-xr-x   3 root root  1040 Jan 21 21:57 images
lrwxrwxrwx   1 root root21 Apr  7  2016 images.dpkg-backup -> 
../imagemagick/images
-rw-r--r--   1 root root 18947 Nov 26 18:00 index.html
drwxr-xr-x   5 root root  1340 Jan 21 21:57 www
lrwxrwxrwx   1 root root18 Apr  7  2016 www.dpkg-backup -> 
../imagemagick/www

# dpkg -S /usr/share/doc/imagemagick-doc/*
imagemagick-doc: /usr/share/doc/imagemagick-doc/NEWS.Debian.gz
imagemagick-doc: /usr/share/doc/imagemagick-doc/changelog.Debian.gz
imagemagick-doc: /usr/share/doc/imagemagick-doc/changelog.gz
imagemagick-doc: /usr/share/doc/imagemagick-doc/copyright
imagemagick-doc: /usr/share/doc/imagemagick-doc/images
dpkg-query: no path found matching pattern 
/usr/share/doc/imagemagick-doc/images.dpkg-backup
imagemagick-doc: /usr/share/doc/imagemagick-doc/index.html
imagemagick-doc: /usr/share/doc/imagemagick-doc/www
dpkg-query: no path found matching pattern 
/usr/share/doc/imagemagick-doc/www.dpkg-backup


Andreas


imagemagick-doc_8:6.9.7.0+dfsg-2.log.gz
Description: application/gzip

Bug#852145: lintian: [PATCH] targetted and targetting are valid alternative spellings

[Edward Betts]

Package: lintian
Version: 2.5.50
Severity: normal
Tags: patch

---
 data/spelling/corrections | 2 --
 1 file changed, 2 deletions(-)

diff --git a/data/spelling/corrections b/data/spelling/corrections
index 87a5aafec..c396355b0 100644
--- a/data/spelling/corrections
+++ b/data/spelling/corrections
@@ -3388,8 +3388,6 @@ sytems||systems
 sytem||system
 sythesis||synthesis
 taht||that
-targetted||targeted
-targetting||targeting
 teached||taught
 teh||the
 temorary||temporary
-- 
2.11.0

Bug#848895: Chromium freezes randomly

[Michael Gilbert]

Douglas A. Augusto wrote:
> This trick works for me too. By the way, I just found out that the reported
> bug also affects octave-gui (4.0.3-2+b2), which randomly freezes just like
> chromium. And the exact same trick you described also works with
> octave.

Is this #801128?

Best wishes,
Mike

Bug#688295: Fwd: Accepted debsums 2.2 (source all) into unstable [origin: a...@debian.org]

[Axel Beckert]

Control: tag -1 - patch

Hi,

I've applied Andreas' patch in the last upload. As I read it, his
patch only mitigates the amount of issues, but doesn't fix all of
them, hence keeping the bug report open, but removing the tag "patch".

Andreas: If you think your patch suffices to fix this issue, feel free
to close the bug report as fixed with 2.2.

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
--- Begin Message ---


pgpEtHzAwPlRc.pgp
Description: PGP message
--- End Message ---

Bug#852144: python-uniconvertor-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: python-uniconvertor-dbg
Version: 1.1.5-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

This was observed on the following upgrade paths:

  wheezy -> jessie -> stretch

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

For other overwritten locations anything interesting may happen.

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

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


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

1m32.0s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python-uniconvertor-dbg/changelog.Debian.gz 
(python-uniconvertor-dbg) != 
/usr/share/doc/python-uniconvertor/changelog.Debian.gz (python-uniconvertor)
/usr/share/doc/python-uniconvertor-dbg -> python-uniconvertor
  /usr/share/doc/python-uniconvertor-dbg/copyright (python-uniconvertor-dbg) != 
/usr/share/doc/python-uniconvertor/copyright (python-uniconvertor)
/usr/share/doc/python-uniconvertor-dbg -> python-uniconvertor


cheers,

Andreas


python-uniconvertor-dbg_1.1.5-3.log.gz
Description: application/gzip

Bug#852143: unknown-horizons 2017.1 crashes with old version of python-fife, please update the depends.

[shirish शिरीष]

Package: unknown-horizons
Version: 2017.1+ds-1
Severity: normal

Dear Maintainer,
Unknown-horizons 2017.1+ds-1 needs to update dependencies of
python-fife to 0.4.0-2 . If I use python-fife 0.3.5+git160920-1 it
promptly crashes. Please fix the depends.


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

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

Versions of packages unknown-horizons depends on:
ii  python   2.7.13-1
ii  python-enet  0.0~svn24-1+b2
ii  python-fife  0.3.5+git160920-1
ii  python-yaml  3.12-1
pn  python:any   
ii  ttf-unifont  1:9.0.06-2

unknown-horizons recommends no packages.

unknown-horizons suggests no packages.

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#852142: ifuse: iPhone not mountable

[Francois Mescam]

Package: ifuse
Version: 1.1.2-0.1+b4
Severity: important

Dear Maintainer,

When I try to mount my iPhone I obtain :
$ ifuse /iphone
GnuTLS error: Error in the pull function.
Failed to connect to lockdownd service on the device.
Try again. If it still fails try rebooting your device.

My iPhone is under IOS 10.2

In syslog there is :
Jan 21 22:32:02 eiffel6 kernel: [10721.895452] usb 1-1: new high-speed USB 
device number 11 using xhci_hcd
Jan 21 22:32:02 eiffel6 kernel: [10722.037715] usb 1-1: New USB device found, 
idVendor=05ac, idProduct=12a8
Jan 21 22:32:02 eiffel6 kernel: [10722.037717] usb 1-1: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Jan 21 22:32:02 eiffel6 kernel: [10722.037718] usb 1-1: Product: iPhone
Jan 21 22:32:02 eiffel6 kernel: [10722.037719] usb 1-1: Manufacturer: Apple Inc.
Jan 21 22:32:02 eiffel6 kernel: [10722.037721] usb 1-1: SerialNumber: 
df6ae10492bc8bc5bd00c3f0289909b1f6aac480
Jan 21 22:32:02 eiffel6 mtp-probe: checking bus 1, device 11: 
"/sys/devices/pci:00/:00:14.0/usb1/1-1"
Jan 21 22:32:02 eiffel6 mtp-probe: bus: 1, device: 11 was not an MTP device
Jan 21 22:32:03 eiffel6 usbmuxd[16504]: [22:32:03.027][3] usbmuxd v1.1.0 
starting up
Jan 21 22:32:03 eiffel6 usbmuxd[16504]: [22:32:03.029][3] Successfully dropped 
privileges to 'usbmux'
Jan 21 22:32:03 eiffel6 usbmuxd[16504]: [22:32:03.032][3] Could not get old 
configuration descriptor for device 1-11: -5
Jan 21 22:32:03 eiffel6 colord[801]: CdMain: failed to emit DeviceAdded: failed 
to register object: Un objet est déjà exporté pour l'interface « 
org.freedesktop.ColorManager.Device » en « 
/org/freedesktop/ColorManager/devices/sysfs__null_ »
Jan 21 22:32:03 eiffel6 colord[801]: CdMain: failed to emit DeviceAdded: failed 
to register object: Un objet est déjà exporté pour l'interface « 
org.freedesktop.ColorManager.Device » en « 
/org/freedesktop/ColorManager/devices/sysfs__null_ »
Jan 21 22:32:03 eiffel6 kernel: [10722.210039] ipheth 1-1:4.2: Apple iPhone USB 
Ethernet device attached
Jan 21 22:32:03 eiffel6 kernel: [10722.213309] ipheth 1-1:4.2 enp0s20u1c4i2: 
renamed from eth0
Jan 21 22:32:03 eiffel6 usbmuxd[16504]: [22:32:03.171][3] Connecting to new 
device on location 0x1000b as ID 1
Jan 21 22:32:03 eiffel6 usbmuxd[16504]: [22:32:03.171][3] Initialization 
complete
Jan 21 22:32:03 eiffel6 usbmuxd[16504]: [22:32:03.171][3] Enabled exit on 
SIGUSR1 if no devices are attached. Start a new instance with "--exit" to 
trigger.
Jan 21 22:32:03 eiffel6 usbmuxd[16504]: [22:32:03.171][3] Connected to v2.0 
device 1 on location 0x1000b with serial number 
df6ae10492bc8bc5bd00c3f0289909b1f6aac480
Jan 21 22:32:03 eiffel6 systemd-udevd[16523]: Process 'ipheth-pair' failed with 
exit code 255.
Jan 21 22:32:03 eiffel6 kernel: [10722.241735] IPv6: ADDRCONF(NETDEV_UP): 
enp0s20u1c4i2: link is not ready
Jan 21 22:32:03 eiffel6 kernel: [10722.242658] IPv6: ADDRCONF(NETDEV_UP): 
enp0s20u1c4i2: link is not ready
Jan 21 22:32:03 eiffel6 gvfs-gphoto2-vo[3406]: device (null) has no BUSNUM 
property, ignoring
Jan 21 22:32:03 eiffel6 gvfs-gphoto2-vo[3406]: device (null) has no BUSNUM 
property, ignoring
Jan 21 22:32:03 eiffel6 gvfs-gphoto2-vo[3406]: device (null) has no BUSNUM 
property, ignoring
Jan 21 22:32:03 eiffel6 gvfs-gphoto2-vo[3406]: device (null) has no BUSNUM 
property, ignoring
Jan 21 22:32:03 eiffel6 gvfs-afc-volume-monitor[3411]: creating volume for 
device uuid 'df6ae10492bc8bc5bd00c3f0289909b1f6aac480'
Jan 21 22:32:03 eiffel6 usbmuxd[16504]: [22:32:03.779][1] 
config_get_device_record: failed to read 
'/var/lib/lockdown/df6ae10492bc8bc5bd00c3f0289909b1f6aac480.plist': No such 
file or directory
Jan 21 22:32:04 eiffel6 usbmuxd[16504]: [22:32:04.779][1] 
config_get_device_record: failed to read 
'/var/lib/lockdown/df6ae10492bc8bc5bd00c3f0289909b1f6aac480.plist': No such 
file or directory
Jan 21 22:32:09 eiffel6 usbmuxd[16504]: [22:32:09.925][1] 
config_get_device_record: failed to read 
'/var/lib/lockdown/df6ae10492bc8bc5bd00c3f0289909b1f6aac480.plist': No such 
file or directory
Jan 21 22:32:11 eiffel6 upowerd[2816]: GnuTLS error: Error in the pull function.
Jan 21 22:32:12 eiffel6 upowerd[2816]: GnuTLS error: Error in the pull function.
Jan 21 22:32:13 eiffel6 upowerd[2816]: GnuTLS error: Error in the pull function.
Jan 21 22:32:14 eiffel6 upowerd[2816]: GnuTLS error: Error in the pull function.
Jan 21 22:32:15 eiffel6 upowerd[2816]: GnuTLS error: Error in the pull function.
Jan 21 22:32:16 eiffel6 kernel: [10735.713496] usb 1-1: USB disconnect, device 
number 11
Jan 21 22:32:16 eiffel6 usbmuxd[16504]: [22:32:16.717][3] Removed device 1 on 
location 0x1000b
Jan 21 22:32:16 eiffel6 usbmuxd[16504]: [22:32:16.717][3] usbmuxd shutting down
Jan 21 22:32:16 eiffel6 gvfs-afc-volume-monitor[3411]: removing volume for 
device uuid 'df6ae10492bc8bc5bd00c3f0289909b1f6aac480'
Jan 21 22:32:16 eiffel6 kernel: [10735.760556] ipheth 1-1:4.2: Apple iPhone USB 
Ethernet now disconnected
Jan 21 22:32:16 eiffel6 

Bug#852003: Video freezes with xserver-xorg-video-radeon-7.8

[Victor Leschuk]

I confirm: with

xserver-xorg-core  2:1.19.1-4
xserver-xorg-video-radeon  1:7.8.0-1+b1

the problem is gone.
On 01/21/2017 10:46 AM, Michel Dänzer wrote:

On 21/01/17 02:11 AM, Victor Leschuk wrote:

Package: xserver-xorg-video-radeon

Version: 7.8.0-1+b1

Hello, after upgrading to version 7.8 of xserver-xorg-video-radeon I
experienced multiple freezes of video during playing netflix via chrome,
launching full-screen video games, etc. The symptoms are always the
same: video freezes, sound continues playing, switching to console works
fine and allows to kill -9 frozen application.

Downgrading to 7.7.1-1 (and xorg from 1.19 to 1.18.4-2) from
http://snapshot.debian.org/archive/debian/20160916T045559Z/ solves the
situation.

Sounds like bug #846779 / #850940, fixed in xserver-xorg-core 2:1.19.1-1
or newer.




--
Best Regards,
Victor

Bug#852141: ubertooth: Please package latest version (2015-10-R1 or later)

[Eric Cooper]

Source: ubertooth
Version: 2015.09.R2-4
Severity: normal

The current version of Ubertooth firmware and utilities is
https://github.com/greatscottgadgets/ubertooth/releases/tag/2015-10-R1

Thank you for maintaining this.

Bug#852139: google-android-installers: unowned directory after purge: /usr/lib/android-sdk/{build-tools/, platforms/}

[Andreas Beckmann]

Source: google-android-installers
Version: 1472023576
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + google-android-build-tools-17-installer 
google-android-platform-2-installer

Hi,

during a test with piuparts I noticed all binary packages built
from src:google-android-installers leave unowned
directories on the system after purge, which is a violation of
policy 6.8:

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

The maintainer scripts create (and later remove) a file in that
directory. Manual directory removal may be not appropriate as this
directory is shared between several packages.

If the package would ship this as an empty directory, dpkg would take
care of the creation and removal (if it's empty).

>From the attached log (scroll to the bottom...):

0m58.9s ERROR: FAIL: Package purging left files on system:
  /usr/lib/android-sdk/  not owned
  /usr/lib/android-sdk/build-tools/  not owned

and the google-android-platform-*-installer packages have

1m9.8s ERROR: FAIL: Package purging left files on system:
  /usr/lib/android-sdk/  not owned
  /usr/lib/android-sdk/platforms/not owned


cheers,

Andreas


google-android-build-tools-17-installer_17.0.0.log.gz
Description: application/gzip

Bug#848895: Chromium freezes randomly

[Michael Gilbert]

control: tag -1 moreinfo

Since this also effects upstream google-chrome, and other applications
like octave-gui, it may be more likely a mesa, X11, or gpu driver bug.
For those willing to dig in, try rolling some of the underlying
packages back a few months.

Best wishes,
Mike

Bug#852137: RFA: libgpuarray -- library to compute tensors on the GPU

[Daniel Stender]

Package: wnpp
Severity: normal

Due to the lack of time I'm seeking for somebody to adopt this package [1]. This
is an alternative GPU backend for Theano [2].
If you are interested please consult with me first ().

Thanks,
DS

Description: library to compute tensors on the GPU (development)
 libgpuarray provides a ndarray (multi-dimensional array) object which
 is computed on the GPU. It supports int, single and double precision
 floats.
 .
 libgpuarray supports Nvidia's CUDA interface as well as OpenCL. The
 Debian packages have been build against OpenCL. However, the source
 package could be rebuild locally also for CUDA (which is non-free)
 without changes, if that's needed.

[1] https://packages.qa.debian.org/libg/libgpuarray.html

[2] https://packages.qa.debian.org/t/theano.html

Bug#851946: Depending on libssl1.0-dev breaks PHP builds

[Sebastian Andrzej Siewior]

On 2017-01-20 21:36:00 [+], Niels Thykier wrote:
> Hi Ondřej,
> 
> Sorry for being the "messenger" triggering this issue in php7.0.
> 
> Kurt/Sebastian, what are you recommendations here?  Should we migrate
> net-snmp itself to ssl1.1 (possibly with all of its rdeps) or can we
> detangle net-snmp and php7 from each other in a graceful manner?

From what it looks, net-snmp/library/cert_util.h exposes openssl' data
types and that is probably why they Depend on libssl-dev in the
libsnmp-dev package. I grep the deps [0] and didn't find a user of
cert_util.h so it looks like nobody cares about that.

I would suggest to drop the the libssl1.0-dev dep in libsnmp-dev and add
a guard cert_util.h to ensure openssl's version is less than 1.1.0 in
case someone tries to use this on its own.
I will try to make that change tomorrow and rebuild the packages [0].

[0] grep-dctrl -s Package -F Build-Depends,Build-Depends-Indep \
libsnmp-dev /var/lib/apt/lists/*Sources | sort -u

> Thanks,
> ~Niels

Sebastian

Bug#852138: RFA: theano -- CPU/GPU math expression compiler for Python

[Daniel Stender]

Package: wnpp
Severity: normal

I request an adopter for the theano package [1]. If you are interested, please
consult me first ().

Thanks,
DS

The package description is:
 Theano is a Python library that allows one to define and evaluate mathematical
 expressions involving multi-dimensional arrays efficiently. It provides a
 high-level Numpy like expression language for functional description of
 calculation, rearranges expressions for speed and stability, and generates
 native machine instructions for fast calculation. Optionally, highly
 accelerated computations could be carried out on graphics cards processors.

[1] https://packages.qa.debian.org/t/theano.html

Bug#852136: RFS: python-btrees/4.3.1-1 [ITP]

[Julien Muchembled]

Package: sponsorship-requests
Severity: normal

 Dear mentors,

 I am looking for a sponsor for my package "fssync"

* Package name: fssync
  Version : 1.6-1
  Upstream Author : Julien Muchembled 
* URL : http://jmuchemb.eu/fssync.git
* License : GPL-3.0
  Section : utils

 It builds this binary package:

   fssync - File system synchronization tool (1-way, over SSH)

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

 https://mentors.debian.net/package/fssync

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

   dget -x https://mentors.debian.net/debian/pool/main/f/fssync/fssync_1.6-1.dsc

 Changes since the last upload:

fssync (1.6-1) unstable; urgency=medium

  * New upstream release.
  * Update Standards-Version to 3.9.8 (no change needed).
  * Use debhelper 10 (no change).
  * Unit tests are now run during build, so switch build-depends to python3-*
and add python3-pylibacl.
  * d/copyright: update Copyright: year

 Upstream changes since the last upload:

1.6 (2017-01-21)


- --check option crashed on destination when it has untracked inodes
  whose paths are greater (alphabetically) than any path on source side.

 Regards,
  Julien Muchembled



signature.asc
Description: OpenPGP digital signature

Bug#852133: RFA: keras

[Daniel Stender]

Control: retitle -1 RFA: keras -- deep learning framework running on Theano or 
TensorFlow

Description: deep learning framework running on Theano or TensorFlow
 Keras is a Python library for machine learning based on deep (multi-
 layered) artificial neural networks (DNN), which follows a minimalistic
 and modular design with a focus on fast experimentation.
 .
 Features of DNNs like neural layers, cost functions, optimizers,
 initialization schemes, activation functions and regularization schemes
 are available in Keras a standalone modules which can be plugged together
 as wanted to create sequence models or more complex architectures.
 Keras supports convolutions neural networks (CNN, used for image
 recognition resp. classification) and recurrent neural networks (RNN,
 suitable for sequence analysis like in natural language processing).
 .
 It runs as an abstraction layer on the top of Theano (math expression
 compiler) by default, which makes it possible to accelerate the computations
 by using (GP)GPU devices. Alternatively, Keras could run on Google's
 TensorFlow (not yet available in Debian, but coming up).

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/

Bug#837387: xul-ext-compactheader: uninstallable in jessie and wheezy

[Andreas Beckmann]

Hi David,

could you take a look at updating xul-ext-compactheader in jessie (and
wheezy)? These have become uninstallable after switching to newer
icedove versions in stable/oldstable.

Thanks

Andreas

On Sun, 11 Sep 2016 11:13:04 +0200 Andreas Beckmann  wrote:
> Package: xul-ext-compactheader
> Version: 2.0.8-1
> Severity: grave
> 
> Package: xul-ext-compactheader
> Source: compactheader
> Version: 2.0.8-1
> Architecture: all
> Provides: compactheader, icedove-compactheader
> Depends: icedove (>= 9.0)
> Enhances: icedove
> Breaks: icedove (<< 9.0)
> Description-en: Icedove extension to reduce header size to one or two lines
> 
> Package: icedove
> Version: 1:45.2.0-1~deb8u1
> Architecture: amd64
> Replaces: icedove-gnome-support (<< 3.0-1~)
> Provides: mail-reader
> Depends: ...
> Recommends: ...
> Suggests: ...
> Breaks: ..., xul-ext-compactheader (<< 2.1.0~)
> Description-en: mail/news client with RSS and integrated spam filter support
> 
> 
> Andreas
> 
> 

Bug#851897: dgit: please have generated source packages contain standard patch series

[Ian Jackson]

Daniel Shahaf writes ("Re: Bug#851897: dgit: please have generated source 
packages contain standard patch series"):
> The language "automatically generated representation" raises the
> "inferior representation" v. "best possible representation in the
> format" question again.  (mentioned in my previous email)

Yes.

> How about:
> 
>  The Debian packaging of foo is maintained in git,
>  using the merging workflow described in dgit-maint-merge(7).
>  That workflow does not have a patch queue that can be represented
>  as a quilt series.
>  A detailed breakdown of the Debian changes is available from…
>  .
>  An automatically generated representation of the same changes follows.
> 
> [lines 3-4 are new]
> 
> A bit verbose, maybe, but hopefully unambiguous.

This is a good direction.  I now have:

   The Debian packaging of foo is maintained in git,
   using the merging workflow described in dgit-maint-merge(7).
 | There isn't a patch queue that can be represented as a quilt series.

   A detailed breakdown of the changes is available from their
   canonical representation -
   git commits in the packaging repository.
   For example, to see the changes made by the Debian maintainer in the
   first upload of upstream version 1.2.3, you could use:

   =over 4

   % git clone https://git.dgit.debian.org/
   % cd foo
   % git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian'

   =back

   See dgit-maint-merge(7) for more information.
   (If you have dgit, use dgit clone foo,
   rather than plain git clone.)

 | A single combined diff, containing all the changes, follows.

(nontrivial changes marked with |)

> Editorials: s/break down/breakdown/; s/-/:/ (as Sean had).

I have fixed the former.  I feel `:' would need to introduce more of a
sentence; I don't feel it can introduce a single noun phrase in this
way.

Thanks,
Ian.

-- 
Ian Jackson    These opinions are my own.

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

Bug#852135: debdelta: installation leaves gpg-agent process running

[Andreas Beckmann]

Package: debdelta
Version: 0.56
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + debdelta-doc

Hi,

during a test with piuparts I noticed your package left processes
running after the package has been removed and/or purged.

In https://lists.debian.org/debian-devel/2009/08/msg00182.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

>From the attached log (scroll to the bottom...):

0m49.3s ERROR: FAIL: Processes are running inside chroot:
  COMMAND PID USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
  gpg-agent 11803 root  cwdDIR   0,21  440 3463512416 
/tmp/piupartss/tmpGfwH0w
  gpg-agent 11803 root  rtdDIR   0,21  440 3463512416 
/tmp/piupartss/tmpGfwH0w
  gpg-agent 11803 root  memREG   0,21  1787812 3463515254 
/tmp/piupartss/tmpGfwH0w/lib/i386-linux-gnu/libc-2.24.so
  gpg-agent 11803 root  memREG   0,21   132408 3463515240 
/tmp/piupartss/tmpGfwH0w/lib/i386-linux-gnu/libpthread-2.24.so
  gpg-agent 11803 root  memREG   0,2187432 3463515211 
/tmp/piupartss/tmpGfwH0w/lib/i386-linux-gnu/libgpg-error.so.0.21.0
  gpg-agent 11803 root  memREG   0,21   842884 3463515213 
/tmp/piupartss/tmpGfwH0w/lib/i386-linux-gnu/libgcrypt.so.20.1.5
  gpg-agent 11803 root  memREG   0,21   146716 3463515258 
/tmp/piupartss/tmpGfwH0w/lib/i386-linux-gnu/ld-2.24.so
  gpg-agent 11803 root0r   CHR1,3  0t0 3463498470 
/tmp/piupartss/tmpGfwH0w/dev/null
  gpg-agent 11803 root1w   CHR1,3  0t0 3463498470 
/tmp/piupartss/tmpGfwH0w/dev/null
  gpg-agent 11803 root2w   CHR1,3  0t0 3463498470 
/tmp/piupartss/tmpGfwH0w/dev/null


This agent is automatically started by the gpg command in the postinst script
unfortunately there is no option to automatically terminate such a temporary
agent. But you could add the following command to your postinst,
directly after the gpg command, to terminate the agent:

gpgconf --homedir ${GPG_HOME} --kill gpg-agent || true


cheers,

Andreas


debdelta_0.56.log.gz
Description: application/gzip

Bug#695179: psnup(1) has a confusing bit

[Reuben Thomas]

On 21 January 2017 at 19:36, Ian Jackson 
wrote:

>
> In the absence of time to fix this properly by listing the available
> units I have at least dropped the confusing sentence.
>

​I have since become upstream, and have rewritten the documentation. I need
to do a bit more work (of indeterminate wall-clock duration), so this fix
is appreciated (thanks!), but I should eventually have a Debian-ready
rewrite.

-- 
http://rrt.sc3d.org

Bug#695179: psnup(1) has a confusing bit

[Ian Jackson]

Reuben Thomas writes ("Re: Bug#695179: psnup(1) has a confusing bit"):
> On 21 January 2017 at 19:36, Ian Jackson 
> wrote:
> 
> In the absence of time to fix this properly by listing the available
> units I have at least dropped the confusing sentence.
> 
> 
> I have since become upstream, and have rewritten the documentation. I need to
> do a bit more work (of indeterminate wall-clock duration), so this fix is
> appreciated (thanks!), but I should eventually have a Debian-ready rewrite.

Great.  Thanks.

Ian.

-- 
Ian Jackson    These opinions are my own.

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

Bug#852134: RFA: lasagne -- deep learning Python library build on the top of Theano

[Daniel Stender]

Package: wnpp
Severity: normal

Due to the lack of time I request an adopter for the lasagne package [1]. If 
you are
interested, please consult with me, first ().

Thanks,
DS

The package description is:
 Lasagne is a Python library to build and train deep (multi-layered) artificial
 neural networks on the top of Theano (math expression compiler). In comparison
 to other abstraction layers for that like e.g. Keras, it abstracts Theano as
 little as possible.
 .
 Lasagne supports networks like Convolutional Neural Networks (CNN, mostly used
 for image recognition resp. classification) and the Long Short-Term Memory type
 (LSTM, a subtype of Recurrent Neural Networks, RNN).

[1] https://packages.qa.debian.org/l/lasagne.html

Bug#852085: packagekit: Add breaks packagekit-plugin-click

[Jeremy Bicha]

Control: tags -1 +patch
From 62119f192e342b95ab965d9190d6ccc37198185b Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Sat, 21 Jan 2017 20:32:30 +
Subject: [PATCH] Add Breaks: packagekit-plugin-click

Closes: #852085
---
 debian/control | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index c01dc50..e045ce7 100644
--- a/debian/control
+++ b/debian/control
@@ -47,7 +47,8 @@ Breaks: libpackagekit-glib2-14 (<= 0.7.6-4),
 packagekit-backend-apt (<< 1.0),
 packagekit-backend-aptcc (<< 1.0),
 packagekit-backend-smart (<< 1.0),
-packagekit-offline-update (<< 1.0)
+packagekit-offline-update (<< 1.0),
+packagekit-plugin-click (<= 0.3.1)
 Recommends: packagekit-tools
 Suggests: appstream
 Description: Provides a package management service
-- 
2.10.2

Bug#852133: RFA: keras

[Daniel Stender]

Package: wnpp
Severity: normal

Due to the lack of time I'm seeking for somebody to adopt this package [1]. If
you're interested please consult with me, first ().

[1] https://packages.qa.debian.org/k/keras.html

Bug#851950: [pkg-dhcp-devel] Bug#851950: isc-dhcp-client: unusual signs in dhclient.leases

[Michael Gilbert]

control: severity -1 normal
control: tag -1 unreproducible, moreinfo

On Fri, Jan 20, 2017 at 5:15 AM, moep wrote:
> My dhclient.leases looked normal, but at one section there are unusual signs:

Can you provide more information about how to reproduce this?  Are you
using anything else that might be touching the leases file, maybe
network manager?

You could try watching it with lsof to see if any other process is touching it.

Best wishes,
Mike

Bug#851897: dgit: please have generated source packages contain standard patch series

[Daniel Shahaf]

Ian Jackson wrote on Sat, Jan 21, 2017 at 18:21:04 +:
> How about this.  Comments interleaved:
> 
>   @@ -23,7 +23,9 @@ the usefulness of the raw Debian source package.  The 
> Debian archive
>is thought of as an output format.
> 
>For example, we don't spend time curating a series of quilt patches.
>   -However, the information such a series would contain is readily
>   +However,
>   +in straightforward cases,
>   +the information such a series would contain is readily
>available from B.
> 
> This sentence wasn't quite true (as Daniel points out) without
> qualification.

*nod* The target audience here is the package maintainer and this
phrasing hints at the trade-offs between the merge and patch queue
workflows.

>   +For such a workflow see for example
>   +dgit-maint-gbp(7).
> 
> And I think a cross-reference is helpful here so the advice isn't a
> dead-end.

+1

>   -The Debian packaging of foo is maintained using dgit.  For the sake of
>   -an efficient workflow, Debian modifications to the upstream source are
>   -squashed into a single diff, rather than a series of quilt patches.
>   -To obtain a patch queue for package version 1.2.3-1:
>   +The Debian packaging of foo is maintained in git,
>   +using the merging workflow described in dgit-maint-merge(7).
>   +An automatically generated representation of the Debian changes follows.
> 

The language "automatically generated representation" raises the
"inferior representation" v. "best possible representation in the
format" question again.  (mentioned in my previous email)

How about:

 The Debian packaging of foo is maintained in git,
 using the merging workflow described in dgit-maint-merge(7).
 That workflow does not have a patch queue that can be represented
 as a quilt series.
 A detailed breakdown of the Debian changes is available from…
 .
 An automatically generated representation of the same changes follows.

[lines 3-4 are new]

A bit verbose, maybe, but hopefully unambiguous.

> This is from Sean's lates suggestion, except that
> 
>   +A detailed break down of these changes is available from their
>   +canonical representation -
>   +git commits in the packaging repository.
> 
> I have changed the punctation, and written `git commits' rather than
> just `commits'.  I think this is clearer.
> 

It is clearer, yes.

Editorials: s/break down/breakdown/; s/-/:/ (as Sean had).

> Sean writes:
> > I don't think the `dgit clone` need be given since the `git clone` will
> > contain git.dgit.debian.org, so anyone even slightly familiar with dgit
> > will know they can use `dgit clone` if they want to.
> 
> I don't think they will necessarily know that it's advisable.  There
> are a two reasons I can think of why `dgit clone' is better:
> 
>  * It will include changes made in non-dgit-based uploads (eg NMUs).
>I hope that non-dgit users who read about `the packaging
>repository' will realise that it may not contain out-of-workflow
>uploads such as (some) NMUs.

They should, yes; the way Debian is set up, debcheckout may miss NMUs.

(Come to think of it, debcheckout(1) could compare the revision in
changelog to what's in sid and warn if sid is newer...  Something along
the lines of

debcheckout() {
  local package="$1"
  command debcheckout "$1"
  if ! dpkg --compare-versions \
  $(cd $1*/debian/changelog(:h:h) && dpkg-parsechangeloeg -SVersion) \
  ge \
  $(rmadison "$1" | grep -w sid | tail -1 | cut ...);
  then
  echo >&2 "debcheckout: warning: ..."
 fi
   }

)

Cheers,

Daniel

Bug#852131: binutils-hppa-linux-gnu: Cannot crossbuild for hppa on i386: "libgcc.a: file not recognized: File format not recognized"

[Matthias Klose]

This seems to be a duplicate of #850191, please can you check if this is fixed
with  gcc-6-cross-ports 12?

On 21.01.2017 20:58, Christoph Biedl wrote:
> Package: binutils-hppa-linux-gnu
> Version: 2.27.90.20170118-1
> Severity: important
> 
> Dear Maintainer,
> 
> while trying to fix the palo package (#851792) I noticed I cannot
> crossbuild binaries for hppa in i386. On amd64, things look good.
> 
> Reproducer:
> 
>   hppa-linux-gnu-gcc -o hello.o hello.c
> 
> Expected (and also seen when building on amd64):
> 
> - No output
> - hello.o created
> 
> Actually seen:
> 
> | /usr/lib/gcc-cross/hppa-linux-gnu/6/libgcc.a: file not recognized: File 
> format not recognized
> | collect2: error: ld returned 1 exit status
> 
> According to strace, the process (reformatted)
> 
> execve("/usr/lib/gcc-cross/hppa-linux-gnu/6/../../../../hppa-linux-gnu/bin/ld",
> ["/usr/lib/gcc-cross/hppa-linux-gnu/6/../../../../hppa-linux-gnu/bin/ld",
> "-plugin",
> "/usr/lib/gcc-cross/hppa-linux-gnu/6/liblto_plugin.so",
> "-plugin-opt=/usr/lib/gcc-cross/hppa-linux-gnu/6/lto-wrapper",
> "-plugin-opt=-fresolution=/tmp/ccuiWhDv.res",
> "-plugin-opt=-pass-through=-lgcc",
> "-plugin-opt=-pass-through=-lgcc_s",
> "-plugin-opt=-pass-through=-lc",
> "-plugin-opt=-pass-through=-lgcc",
> "-plugin-opt=-pass-through=-lgcc_s",
> "--sysroot=/",
> "--build-id",
> "--eh-frame-hdr",
> "-dynamic-linker",
> "/lib/ld.so.1",
> "-o",
> "hello.o",
> 
> "/usr/lib/gcc-cross/hppa-linux-gnu/6/../../../../hppa-linux-gnu/lib/crt1.o",
> 
> "/usr/lib/gcc-cross/hppa-linux-gnu/6/../../../../hppa-linux-gnu/lib/crti.o",
> "/usr/lib/gcc-cross/hppa-linux-gnu/6/crtbegin.o",
> "-L/usr/lib/gcc-cross/hppa-linux-gnu/6",
> "-L/usr/lib/gcc-cross/hppa-linux-gnu/6/../../../../hppa-linux-gnu/lib",
> "/tmp/ccAMlfsW.o",
> "-lgcc",
> "--as-needed",
> "-lgcc_s",
> "--no-as-needed",
> "-lc",
> "-lgcc",
> "--as-needed",
> "-lgcc_s",
> "--no-as-needed",
> "/usr/lib/gcc-cross/hppa-linux-gnu/6/crtend.o",
> 
> "/usr/lib/gcc-cross/hppa-linux-gnu/6/../../../../hppa-linux-gnu/lib/crtn.o"],
> [/* 16 vars */] 
> 
> opens the file "/usr/lib/gcc-cross/hppa-linux-gnu/6/libgcc.a" but does
> not like the content, resulting in the above message.
> 
> Find attached the output of the hppa-linux-gnu-gcc invocation with
> additional "--verbose --verbose", for both i386 and amd64.
> 
> Christoph
> 
> -- System Information:
> Debian Release: 9.0
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 4.9.4 (SMP w/4 CPU cores)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: unable to detect
> 
> Versions of packages binutils-hppa-linux-gnu depends on:
> ii  binutils  2.27.90.20170118-1
> ii  libc6 2.24-9
> ii  zlib1g1:1.2.8.dfsg-4
> 
> binutils-hppa-linux-gnu recommends no packages.
> 
> Versions of packages binutils-hppa-linux-gnu suggests:
> pn  binutils-doc  
> 
> -- no debconf information
> 

Bug#831540: theano: assertion error in test_fit_int64 on i386 and hurd/kreebsd-i386

[Daniel Stender]

Control: severity -1 serious

The build time tests are temporarily failsafed on i386 to workaround this, but 
that must
be solved for the release.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



signature.asc
Description: OpenPGP digital signature

Bug#831541: theano: single GradientError and WrongValues in tests on s390x, ppc64 and sparc

[Daniel Stender]

Control: severity -1 serious

The build time tests for s390x are temporarily failsafed to workaround this, but
this must be solved before the release.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



signature.asc
Description: OpenPGP digital signature

Bug#852132: linux-latest: Add support for Hardkernel Odroid-C2

[Heinrich Schuchardt]

Package: linux-latest
Severity: wishlist

Dear Maintainer,

please, add support for the Hardkernel Odroid C2 to the kernel configuration.

For 4.9 kernels this involves:

CONFIG_ARCH_MESON=y
CONFIG_SERIAL_MESON=y
CONFIG_SERIAL_MESON_CONSOLE=y
CONFIG_HW_RANDOM_MESON=m
CONFIG_I2C_MESON=m
CONFIG_SPI_MESON_SPIFC=m
CONFIG_PINCTRL_MESON=y
CONFIG_MESON_GXBB_WATCHDOG=y
CONFIG_PWM_MESON=m
CONFIG_RESET_MESON=y
CONFIG_MESON_SM=y
CONFIG_COMMON_CLK_AMLOGIC=y

For 4.10 kernels this involves

CONFIG_ARCH_MESON=y
CONFIG_DWMAC_MESON=y
CONFIG_MESON_GXL_PHY=y
CONFIG_SERIAL_MESON=y
CONFIG_SERIAL_MESON_CONSOLE=y
CONFIG_HW_RANDOM_MESON=m
CONFIG_I2C_MESON=m
CONFIG_SPI_MESON_SPIFC=m
CONFIG_PINCTRL_MESON=y
CONFIG_MESON_GXBB_WATCHDOG=y
CONFIG_MESON_WATCHDOG=y
CONFIG_DRM_MESON=m
CONFIG_MMC_MESON_GX=y
CONFIG_PWM_MESON=m
CONFIG_RESET_MESON=y
CONFIG_PHY_MESON8B_USB2=m
CONFIG_MESON_SM=y
CONFIG_COMMON_CLK_AMLOGIC=y

The following patch is essential. It is queued for 4.10-rc6:

ARM64: dts: meson-gx: Add firmware reserved memory zones
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ecb88f3001ed9ee8c53450d971de8c18bcbf7925

Best regards

Heinrich Schuchardt


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

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