Bug#857766: flashplugin-nonfree: ERROR 404: File not found

[Charles A Schmitz III]

Package: flashplugin-nonfree
Version: 1:3.6.1+deb8u1
Followup-For: Bug #857766

Dear Maintainer,

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

   * What led up to the situation?
apt-get update-flashplugin-nonfree --install 
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
charles@debian:/etc/apt$ sudo update-flashplugin-nonfree --install
   * What was the outcome of this action?
charles@debian:/etc/apt$ sudo update-flashplugin-nonfree --install
--2017-03-19 02:30:40--  
https://fpdownload.adobe.com/get/flashplayer/pdc/24.0.0.186/flash_player_npapi_linux.x86_64.tar.gz
Resolving fpdownload.adobe.com (fpdownload.adobe.com)... 23.202.233.69
Connecting to fpdownload.adobe.com (fpdownload.adobe.com)|23.202.233.69|:443... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2017-03-19 02:30:40 ERROR 404: Not Found.
   * What outcome did you expect instead?
   flashplugin-nonfree would update, so that I could report another bug. I'm a 
bit confused on playing any Flash on firefox


-- Package-specific info:
Debian version: 8.7
Architecture: amd64
Package version: 1:3.6.1+deb8u1
MD5 checksums:
29c85bc8504422120cf89702986ff8e1  
/var/cache/flashplugin-nonfree/get-upstream-version.pl
md5sum: /usr/lib/flashplugin-nonfree/libflashplayer.so: No such file or 
directory
Alternatives:
flash-mozilla.so - auto mode
  link currently points to /usr/lib/gnash/libgnashplugin.so
/usr/lib/gnash/libgnashplugin.so - priority 10
Current 'best' version is '/usr/lib/gnash/libgnashplugin.so'.
lrwxrwxrwx 1 root root 34 Mar 19 01:21 
/usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so
/usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to 
/etc/alternatives/flash-mozilla.so

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

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

Versions of packages flashplugin-nonfree depends on:
ii  binutils   2.25-5
ii  ca-certificates20141019+deb8u2
ii  debconf [debconf-2.0]  1.5.56
ii  gnupg  1.4.18-7+deb8u3
ii  libatk1.0-02.14.0-1
ii  libcairo2  1.14.0-2.1+deb8u2
ii  libcurl3-gnutls7.38.0-4+deb8u5
ii  libfontconfig1 2.11.0-6.3+deb8u1
ii  libfreetype6   2.5.2-3+deb8u1
ii  libgcc11:4.9.2-10
ii  libglib2.0-0   2.42.1-1+b1
ii  libgtk2.0-02.24.25-3+deb8u1
ii  libnspr4   2:4.12-1+debu8u1
ii  libnss32:3.26-1+debu8u1
ii  libpango1.0-0  1.36.8-3
ii  libstdc++6 4.9.2-10
ii  libx11-6   2:1.6.2-3
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.4-1+b1
ii  wget   1.16-1+deb8u1

flashplugin-nonfree recommends no packages.

Versions of packages flashplugin-nonfree suggests:
ii  fonts-dejavu   2.34-1
pn  hal
ii  iceweasel  45.8.0esr-1~deb8u1
pn  konqueror-nsplugins
pn  ttf-mscorefonts-installer  
pn  ttf-xfree86-nonfree

-- no debconf information

Bug#855671: chaussette: FTBFS: ConnectionError: HTTPConnectionPool(host='localhost', port=8080): Max retries exceeded with url: /

[Evgeni Golov]

Hi,

On Tue, Feb 21, 2017 at 09:29:50AM +0100, David Douard wrote:
> Thanks for the bug report. I'll try to investiate this (as well as several 
> other small issues) ASAP (probably not before one or 2 weeks however).

The issue is that the waitress backend does not start:
% /usr/bin/python2.7 -m chaussette.server --backend waitress
2017-03-19 08:46:54 [23969] [INFO] Application is 
2017-03-19 08:46:54 [23969] [INFO] Serving on localhost:8080
2017-03-19 08:46:54 [23969] [INFO] Using  as a backend
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File 
"/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py", 
line 228, in 
main()
  File 
"/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py", 
line 224, in main
inner()
  File 
"/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py", 
line 205, in inner
socket_type=_SOCKET_TYPE[args.socket_type])
  File 
"/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py", 
line 38, in make_server
server = server_class((host, port), app, **server_class_kwargs)
  File "chaussette/backend/_waitress.py", line 20, in __init__
port=port)
  File "/usr/lib/python2.7/dist-packages/waitress/server.py", line 179, in 
__init__
self.socket.setsockopt(IPPROTO_IPV6, IPV6_V6ONLY, 1)
  File "/usr/lib/python2.7/socket.py", line 228, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 92] Protocol not available

But it is announced as available:
>>> import chaussette.backend
>>> chaussette.backend.backends()
['eventlet', 'fastgevent', 'gevent', 'geventwebsocket', 'geventws4py', 
'socketio', 'tornado', 'waitress', 'wsgiref']

Bug#855671: chaussette: FTBFS: ConnectionError: HTTPConnectionPool(host='localhost', port=8080): Max retries exceeded with url: /

[Evgeni Golov]

On Sun, Mar 19, 2017 at 08:48:47AM +0100, Evgeni Golov wrote:

> The issue is that the waitress backend does not start:
> % /usr/bin/python2.7 -m chaussette.server --backend waitress
> 2017-03-19 08:46:54 [23969] [INFO] Application is  0x7f6317213758>
> 2017-03-19 08:46:54 [23969] [INFO] Serving on localhost:8080
> 2017-03-19 08:46:54 [23969] [INFO] Using  'chaussette.backend._waitress.Server'> as a backend
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
> "__main__", fname, loader, pkg_name)
>   File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
> exec code in run_globals
>   File 
> "/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py", 
> line 228, in 
> main()
>   File 
> "/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py", 
> line 224, in main
> inner()
>   File 
> "/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py", 
> line 205, in inner
> socket_type=_SOCKET_TYPE[args.socket_type])
>   File 
> "/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py", 
> line 38, in make_server
> server = server_class((host, port), app, **server_class_kwargs)
>   File "chaussette/backend/_waitress.py", line 20, in __init__
> port=port)
>   File "/usr/lib/python2.7/dist-packages/waitress/server.py", line 179, in 
> __init__
> self.socket.setsockopt(IPPROTO_IPV6, IPV6_V6ONLY, 1)
>   File "/usr/lib/python2.7/socket.py", line 228, in meth
> return getattr(self._sock,name)(*args)
> socket.error: [Errno 92] Protocol not available

That's probably https://github.com/circus-tent/chaussette/issues/82?
But the traceback looks different, so not setting forwarded just yet.

Bug#858110: peg-solitaire: A list of suggestions to improve the game

[Andrej Mernik]

Dne sobota, 18. marec 2017 ob 17:38:39 CET je Innocent De Marchi napisal(a):
> Hi Andrej,
> 
> Thank you for your suggestions.
> I will incorporate them into the program:
> I'm working on a new version and I guess it will be ready this year.
> 
> Just a comment on this suggestion:
> 
> - save game data in a hidden folder inside $HOME instead of creating two
> 
> > folders directly in $HOME
> > 
> > The data in the \Solitari directory is intentionally visible: Are data
> 
> that the user may want to save, erase or change to another computer and I
> think it is better that they are visible.
> The \Solitari_seg directory is backed up by version 2.1. Changes in Qt have
> required changes in the encoding of program file names: before migration is
> backed up. There is another hidden directory with the program configuration
> data.
> 
> Regards!
> 
> I. De Marchi

Hi Innocent,

if the program really needs only one folder, then this is fine by me. Keep up 
the good work.

Best Regards,
Andrej Mernik  

Bug#856526: Problem with SAUCE in stretch

[Ian Jackson]

Control: reassign -1 libtcl-chiark-1
Control: found -1 1.2.0
Control: retitle -1 chiark-tcl uses wrong multiarch path on i386

libtcl-chiark-1_1.2.0_i386.deb contains
/usr/lib/i686-linux-gnu/chiark_tcl_adns-1.so

But:

(stretch32)root@zealot:/home/ian# ldd /usr/bin/tclsh
linux-gate.so.1 (0xf7748000)
libtcl8.6.so => /usr/lib/i386-linux-gnu/libtcl8.6.so (0xf7559000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7554000)
libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf7537000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf751a000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf74c5000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf730e000)
/lib/ld-linux.so.2 (0x5663b000)
(stretch32)root@zealot:/home/ian#

Ian.

Bug#855671: chaussette: FTBFS: ConnectionError: HTTPConnectionPool(host='localhost', port=8080): Max retries exceeded with url: /

[Evgeni Golov]

Control: forwarded -1 https://github.com/circus-tent/chaussette/issues/82
Control: tags -1 + upstream
Control: retitle -1 FTBFS: chaussette incompatible with waitress 1.0, tests fail

On Sun, Mar 19, 2017 at 08:56:42AM +0100, Evgeni Golov wrote:
> On Sun, Mar 19, 2017 at 08:48:47AM +0100, Evgeni Golov wrote:
> 
> > The issue is that the waitress backend does not start:
> > % /usr/bin/python2.7 -m chaussette.server --backend waitress
> > 2017-03-19 08:46:54 [23969] [INFO] Application is  > 0x7f6317213758>
> > 2017-03-19 08:46:54 [23969] [INFO] Serving on localhost:8080
> > 2017-03-19 08:46:54 [23969] [INFO] Using  > 'chaussette.backend._waitress.Server'> as a backend
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
> > "__main__", fname, loader, pkg_name)
> >   File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
> > exec code in run_globals
> >   File 
> > "/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py",
> >  line 228, in 
> > main()
> >   File 
> > "/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py",
> >  line 224, in main
> > inner()
> >   File 
> > "/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py",
> >  line 205, in inner
> > socket_type=_SOCKET_TYPE[args.socket_type])
> >   File 
> > "/home/evgeni/Debian/BSP/credativ2017/chaussette-1.3.0/chaussette/server.py",
> >  line 38, in make_server
> > server = server_class((host, port), app, **server_class_kwargs)
> >   File "chaussette/backend/_waitress.py", line 20, in __init__
> > port=port)
> >   File "/usr/lib/python2.7/dist-packages/waitress/server.py", line 179, in 
> > __init__
> > self.socket.setsockopt(IPPROTO_IPV6, IPV6_V6ONLY, 1)
> >   File "/usr/lib/python2.7/socket.py", line 228, in meth
> > return getattr(self._sock,name)(*args)
> > socket.error: [Errno 92] Protocol not available
> 
> That's probably https://github.com/circus-tent/chaussette/issues/82?
> But the traceback looks different, so not setting forwarded just yet.

Confirmed, downgading python-waitress to 0.8.10-1 from snapshot.d.o makes the 
test succeed.

Bug#858163: unblock: gitlab/8.13.11+dfsg-6

[Pirate Praveen]

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

Please unblock package gitlab

This fixes RC bug #857967. Also sine the version in stretch is currently
not installable, please reduce the age.

debdiff with 8.13.11+dfsg-5 attached (changes upto this version is
already approved)

unblock gitlab/8.13.11+dfsg-6

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ml_IN.UTF-8, LC_CTYPE=ml_IN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru gitlab-8.13.11+dfsg/debian/changelog 
gitlab-8.13.11+dfsg/debian/changelog
--- gitlab-8.13.11+dfsg/debian/changelog2017-03-14 17:21:21.0 
+0530
+++ gitlab-8.13.11+dfsg/debian/changelog2017-03-17 22:29:40.0 
+0530
@@ -1,3 +1,9 @@
+gitlab (8.13.11+dfsg-6) unstable; urgency=medium
+
+  * Improve configuration file parsing by using source (Closes: #857967) 
+
+ -- Pirate Praveen   Fri, 17 Mar 2017 22:29:40 +0530
+
 gitlab (8.13.11+dfsg-5) unstable; urgency=medium
 
   * Move variables used only in maintainer scripts to /usr/lib from /etc
diff -Nru gitlab-8.13.11+dfsg/debian/conf/gitlab 
gitlab-8.13.11+dfsg/debian/conf/gitlab
--- gitlab-8.13.11+dfsg/debian/conf/gitlab  2017-03-14 17:21:21.0 
+0530
+++ gitlab-8.13.11+dfsg/debian/conf/gitlab  2017-03-17 18:05:51.0 
+0530
@@ -7,9 +7,8 @@
 # Normal values are "production", "test" and "development".
 RAILS_ENV="production"
 
-# Read and export debian specific configuration
-# Only exported variables will be passed on to gitlab app
-export $(cat /etc/gitlab/gitlab-debian.conf)
+# Read debian specific configuration
+. /etc/gitlab/gitlab-debian.conf
 
 # app_user defines the user that GitLab is run as.
 # The default is "git".
diff -Nru gitlab-8.13.11+dfsg/debian/gitlab-check.sh 
gitlab-8.13.11+dfsg/debian/gitlab-check.sh
--- gitlab-8.13.11+dfsg/debian/gitlab-check.sh  2017-03-14 17:21:21.0 
+0530
+++ gitlab-8.13.11+dfsg/debian/gitlab-check.sh  2017-03-17 21:42:48.0 
+0530
@@ -2,12 +2,12 @@
 
 set -e
 
-# Read and export debian specific configuration
-# Only exported variables will be passed on to gitlab app
-export $(cat /etc/gitlab/gitlab-debian.conf)
+# Read debian specific configuration
+. /etc/gitlab/gitlab-debian.conf
+export DB RAILS_ENV
+
 cd /usr/share/gitlab
 
 # Check gitlab is configured correctly
 printf "Check if Gitlab is configured correctly...\n"
-su ${gitlab_user} -s /bin/sh -c 'bundle exec rake gitlab:check 
RAILS_ENV=production'
-
+su ${gitlab_user} -s /bin/sh -c 'bundle exec rake gitlab:check'
diff -Nru gitlab-8.13.11+dfsg/debian/postinst 
gitlab-8.13.11+dfsg/debian/postinst
--- gitlab-8.13.11+dfsg/debian/postinst 2017-03-14 17:21:21.0 +0530
+++ gitlab-8.13.11+dfsg/debian/postinst 2017-03-17 21:58:12.0 +0530
@@ -40,19 +40,19 @@
 # `abort-remove' or `abort-deconfigure'.
 
 ###
-# Read and export debian specific configuration
-# Only exported variables will be passed on to gitlab app
+# Read debian specific configuration
 ###
 
 # Bootstrap config file - first try
-export $(cat ${gitlab_debian_conf_example})
+. ${gitlab_debian_conf_example}
 # second try
 test -f ${gitlab_debian_conf_private} || \
 cp ${gitlab_debian_conf_example} ${gitlab_debian_conf_private}
-export $(cat ${gitlab_debian_conf_private})
+. ${gitlab_debian_conf_private}
 
 # If /etc/gitlab/gitlab-debian.conf is already present, use it
-test -f ${gitlab_debian_conf} && export $(cat ${gitlab_debian_conf})
+test -f ${gitlab_debian_conf} && . ${gitlab_debian_conf}
+export DB RAILS_ENV
 
 # Read default values (we cannot do this before gitlab-debian.conf is exported
 # as we want to override variables set by gitlab-debian.conf in earlier gitlab
@@ -76,7 +76,7 @@
 ###
 # update Gemfile.lock, always
 ###
-su ${gitlab_user} -s /bin/sh -c 'truncate -s 0 ${gitlab_data_dir}/Gemfile.lock'
+su ${gitlab_user} -s /bin/sh -c "truncate -s 0 ${gitlab_data_dir}/Gemfile.lock"
 cd ${gitlab_app_root}
 if ! su ${gitlab_user} -s /bin/sh -c 'bundle --local --quiet'; then
   if [ "$1" = "triggered" ]; then
diff -Nru gitlab-8.13.11+dfsg/debian/postrm gitlab-8.13.11+dfsg/debian/postrm
--- gitlab-8.13.11+dfsg/debian/postrm   2017-03-14 17:21:21.0 +0530
+++ gitlab-8.13.11+dfsg/debian/postrm   2017-03-17 18:08:07.0 +0530
@@ -17,8 +17,8 @@
 
 # Ensure the menu system is updated
 
-# Read and export debian specific configuration
-test -f ${gitlab_debian_conf} && export $(cat ${gitlab_debian_conf})
+# Read debian specific co

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Sylvestre Ledru]

Le 18/03/2017 à 23:40, Rebecca N. Palmer a écrit :
> Can this be fixed in time for Ubuntu 17.04?  Their mesa is built against LLVM 
> 4.0, so if this bug isn't fixed, I (as beignet maintainer) have to choose 
> between "apply a very new 4.0-support patch that might or might not work" and 
> "leave beignet on 3.9, making OpenCL+OpenGL applications (e.g.
> blender) subject to this bug".
> 
>> I've been told that there is a command line to add a version to all symbols
>> without a script, that should be enough at least for Debian packaging.
> -Wl,--default-symver : rarely used (only 5 packages), and forces the symbol 
> version to be the soname (i.e. libLLVM-3.9.so.1) rather than the conventional 
> LLVM_3.9 form (i.e. potential binary incompatibility if upstream later decide 
> to do it the conventional way), but should at least fix this crash.
> 
> The attached debdiff is for this option, and also fixes #857623 and #857683.  
> Warning: has NOT been tested yet.
> 
> I intend to try extending the earlier "version script" patch to also cover 
> libclang and liblldb tomorrow.

Impressive! I believe we can try this solution. Many thanks.
I started to build this myself.

If it is working file, I will discuss with upstream about integrating that!
Bravo,
Sylvestre

Bug#858164: unblock: chiark-tcl/1.2.1

[Ian Jackson]

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

Please unblock package chiark-tcl


This fixes the RC bug #856526 (detected by piuparts of src:sauce).
There are no other changes.

The source diff is below.


unblock chiark-tcl/1.2.1


diff --git a/debian/changelog b/debian/changelog
index 1848e82..f002642 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+chiark-tcl (1.2.1) unstable; urgency=high
+
+  * Multiarch: Use correct M-A triplet (DEB_HOST_MULTIARCH) for
+libsubdir.  Closes:#856526.
+
+ -- Ian Jackson   Sun, 19 Mar 2017 09:22:48 
+
+
 chiark-tcl (1.2.0) unstable; urgency=medium
 
   * wiringpi module.  Built only if the wiringpi headers are actually
diff --git a/debian/rules b/debian/rules
index f9ed503..3675728 100755
--- a/debian/rules
+++ b/debian/rules
@@ -26,11 +26,12 @@ docdir=usr/share/doc/$(docpackage)
 tclh:=$(firstword $(wildcard /usr/include/tcl8.*/tcl.h))
 tclversion:=$(patsubst /usr/include/tcl%/tcl.h,%,$(tclh))
 
+march := $(shell dpkg-architecture -q DEB_HOST_MULTIARCH)
+libsubdir = /$(march)
+
 garch := $(shell dpkg-architecture -q DEB_HOST_GNU_TYPE)
 ifneq ($(garch),)
 
-libsubdir = /$(garch)
-
 ifeq ($(origin CC),default)
 export CC=$(garch)-gcc
 endif



-- 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=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#856526: Problem with SAUCE in stretch

[Ian Jackson]

> during a test with piuparts I noticed your package failed to install

I have just pushed a fix for this and filed an unblock request.
Thanks for your contribution to the quality of my packages.

Regards,
Ian.

Bug#794294: Automatic disk backups fail with "an operation is already running"

[Todor Tsankov]

I have exactly the same problem running Jessie on amd64, deja-dup
version 32.0-1. It is getting quite annoying after awhile. Is there a
chance to fix that for Stretch? I can provide more information if that
will be helpful to debug the problem.

--Todor

Bug#858122: Upgrade linux kernel to 4.9.15 in sid and stretch

[Julien Aubin]

Yup checked. These drivers are used for satellite communication devices.
Unsure many desktop and server users need them.

Le 18 mars 2017 23:01, "Ben Hutchings"  a écrit :

> On Sat, Mar 18, 2017 at 10:08:10PM +0100, Julien Aubin wrote:
> > OK I did this. Does it have a huge impact on the system except mitigating
> > the flaw ? (I don't think I have an HDLC hardware...)
>
> If you don't know whether you have it, you don't have it. :-)
>
> Ben.
>
> --
> Ben Hutchings
> Life is like a sewer:
> what you get out of it depends on what you put into it.
>

Bug#853929: Please upstream modifications to Thunderbird/Icedove AppArmor profile

[Douglas Bagnall]

hi Ulrike,

On 18/03/17 03:56, Ulrike Uhlig wrote:
> Hi Douglas,
> 
> it's great that you provided modifications to the AppArmor profile in
> Debian [1]! May I kindly ask you to send these upstream too? That way,
> they will get reviewed first and then all other distributions using
> AppArmor can profit from your improvements.
> 
> Debian has some documentation on how to do so:
> https://wiki.debian.org/AppArmor/Contribute/Upstream
> 
> Basically, their Git repo lives here:
> https://code.launchpad.net/~apparmor-dev/apparmor-profiles/+git/apparmor-profiles
> (The particular file lives here:
> https://git.launchpad.net/apparmor-profiles/tree/ubuntu/17.04/usr.bin.thunderbird)
> When done, you can ask for a merge using Launchpad or the mailinglist:
> appar...@lists.ubuntu.com
> 
> If you think that's too much work, please just tag your bug using a
> usertag. The corresponding tag would be "merge-to-upstream" and then the
> AppArmor team can take care of this. See
> https://wiki.debian.org/AppArmor/Reportbug#Usertags for how to do that.

Thanks. I am taking this last option because trying to work out where
that commit with the dots-for-spaces came from has baffled me, and in
dealing with upstream I lack the historical context of the two teams
interactions to know whether they would prefer the broken patch and
its fix merged into one or both in series or some other thing. People
are particular about how they like to manage mistakes in their git
trees, so it is best in this case that you/they do it.

cheers,
Douglas


> [1]
> https://anonscm.debian.org/cgit/pkg-mozilla/icedove.git/commit/?h=debian/experimental&id=e2c8a2391c7b6d422f5df40682b8b19f08b88dcf
> 

Bug#858165: firefox: audio playback has stopped to work without pulseaudio

[Roman Tsisyk]

Package: firefox
Version: 53.0~b4-2
Severity: important

Dear Maintainer,

Audio playback has stopped to work in firefox-53.0~b4-2 when pulseaudio daemon 
is not installed.
Firefox shows "To play audio, you may need to install the required PulseAudio 
software".
This is a **regression ** since firefox-51.

I carefully read upstream bug report [1].  I don't have pulseaudio daemon 
installed and I don't plan to.
Please enable ALSA support for `firefox` package in order to provide the better 
user experience for Debian users.
Thanks.

[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1345661

-- Package-specific info:

-- Extensions information
Name: Application Update Service Helper
Location: ${PROFILE_EXTENSIONS}/aushel...@mozilla.org.xpi
Status: enabled

Name: Compact Dark theme
Status: user-disabled

Name: Compact Light theme
Status: user-disabled

Name: Default theme
Location: 
/usr/lib/firefox/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox
Status: enabled

Name: Multi-process staged rollout
Location: ${PROFILE_EXTENSIONS}/e10sroll...@mozilla.org.xpi
Status: enabled

Name: NoScript
Location: /usr/share/xul-ext/noscript
Package: xul-ext-noscript
Status: enabled

Name: Pocket
Location: ${PROFILE_EXTENSIONS}/fire...@getpocket.com.xpi
Status: enabled

Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled

Name: United States English Spellchecker dictionary
Location: ${PROFILE_EXTENSIONS}/en...@dictionaries.addons.mozilla.org
Status: enabled

Name: User Agent Switcher
Location: ${PROFILE_EXTENSIONS}/{e968fc70-8f95-4ab9-9e79-304de2a71ee1}.xpi
Status: enabled

Name: Web Compat
Location: ${PROFILE_EXTENSIONS}/webcom...@mozilla.org.xpi
Status: enabled

-- Plugins information
Name: Shockwave Flash (25.0.0.127)
Location: /usr/lib/mozilla/plugins/libflashplayer.so
Status: enabled


-- Addons package information
ii  firefox53.0~b4-2amd64Mozilla Firefox web browser
ii  xul-ext-noscri 2.9.0.14-1   all  permissions manager for Firefox

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

Kernel: Linux 4.6.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 firefox depends on:
ii  debianutils   4.8.1
ii  fontconfig2.11.0-6.7
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-9
ii  libcairo-gobject2 1.14.6-1.1
ii  libcairo2 1.14.6-1.1
ii  libdbus-1-3   1.10.14-1
ii  libdbus-glib-1-2  0.108-2
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:7-20170121-1
ii  libgdk-pixbuf2.0-02.36.0-1
ii  libglib2.0-0  2.50.2-2
ii  libgtk-3-03.22.4-1
ii  libgtk2.0-0   2.24.31-1
ii  libhunspell-1.6-0 1.6.0-1
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.30-1
ii  libpango-1.0-01.40.3-3
ii  libsqlite3-0  3.13.0-1
ii  libstartup-notification0  0.12-4
ii  libstdc++67-20170121-1
ii  libvpx4   1.6.0-3
ii  libx11-6  2:1.6.3-1
ii  libx11-xcb1   2:1.6.3-1
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
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.2-1
ii  libxrender1   1:0.9.9-2
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3
ii  zlib1g1:1.2.8.dfsg-2+b3

firefox recommends no packages.

Versions of packages firefox suggests:
ii  fonts-lmodern  2.004.5-3
ii  fonts-stix [otf-stix]  1.1.1-4
ii  libcanberra0   0.30-3
ii  libgssapi-krb5-2   1.15~beta1-1
pn  mozplugger 

-- no debconf information

-- 
WBR,
   Roman Tsisyk 
   http://tarantool.org/ - an efficient in-memory data store and a Lua 
application server

Bug#857885: regression: Acquire::http::ProxyAutoDetect no longer running script

[David Kalnischkies]

On Wed, Mar 15, 2017 at 09:14:01PM -0500, csights wrote:
>   It appears that the script listed after Acquire::http::ProxyAutoDetect is 
> no longer called.

We have a few tests covering that option and while adding a few more
tests locally to doublecheck I can confirm that they work as intended…

(The tests cover Proxy-Auto-Detect, but the non-dashed name is an old
alias and I just confirmed that they both work exchangeably. You should
be prefering the dashed on your configuration through)

So there is something more to your setup causing it to not work as it
works just fine here (and in the autopkgtests).


Simplest of guess: Are you actually still using 'http' sources or is
your stretch system using 'https'?

Running "apt update -o Debug::Acquire::http=1" might also shine some
light on things as it has a bunch of output.

Also check that you haven't proxy environment variables ("export | grep
-i proxy") or similar such interfering.


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#858167: unblock: sushi/1.4.0+git20160822+dfsg-3

[Devid Antonio Filoni]

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

Please unblock package sushi.

sushi 1.4.0+git20160822+dfsg-3 fixes a serious bug (#857772: FTBFS with
bash as /bin/sh) and contains fixes for some crashes in nigiri binary which
was not working anymore.
debdiff attached.

Thank you,
Devid

unblock: sushi/1.4.0+git20160822+dfsg-3


1.4.0+git20160822+dfsg-3.debdiff
Description: Binary data

Bug#853929: Please upstream modifications to Thunderbird/Icedove AppArmor profile

[Ulrike Uhlig]

Hi Douglas,

>> it's great that you provided modifications to the AppArmor profile in
>> Debian! May I kindly ask you to send these upstream too? 

>> If you think that's too much work, please just tag your bug using a
>> usertag. The corresponding tag would be "merge-to-upstream" and then the
>> AppArmor team can take care of this. See
>> https://wiki.debian.org/AppArmor/Reportbug#Usertags for how to do that.
> 
> Thanks. I am taking this last option because trying to work out where
> that commit with the dots-for-spaces came from has baffled me, and in
> dealing with upstream I lack the historical context of the two teams
> interactions to know whether they would prefer the broken patch and
> its fix merged into one or both in series or some other thing. People
> are particular about how they like to manage mistakes in their git
> trees, so it is best in this case that you/they do it.

I've just updated the documentation:
https://wiki.debian.org/AppArmor/Contribute/Upstream#Quick_howto_contribute_to_upstream_AppArmor_profiles_using_Git
because I realized that some parts were missing. Basically the idea
would always be to get patches upstreamed and then to tell Debian
(Thunderbird +  AppArmor) maintainers about it once it's been merged.

For this particular case, I think Simon said he would take care of it.

Have a nice day,
ulrike

Bug#855396: Please close

[Philip Hands]

David Griffith  writes:

> Please close this bug.  The root cause turned out to be not enough memory.

Well, we could close the bug, but it strikes me that this is still a
bug, since the stick could have saved you the wasted time if it had
detected the lack of RAM and told you that it wasn't going to work, or
failing that we could at least add a note about it to the manual.

Do you happen to know how little RAM was enough for it to work, or how
much you had when it wasn't working?

Cheers, Phil.

P.S. you can close bugs yourself by mailing e.g. 855396-d...@bugs.debian.org
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#858166: Installation of snaps hangs ervery time

[Jörg Frings-Fürst]

Source: snapd
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

on a fresh updated sid install "snap install XXX" hangs on every snaps with

[|] Run configure hook of "core" snap if present

If you need more infos please ask me.

CU
Jörg



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

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAljOWdIACgkQCfifPIyh
0l3rGRAAmpQ7VIVO2Bw+C5rGEpvLhxL9EzYSG6+EA9ESjcDsSVsZrRCi2z30AXA5
MO+P8ORBdLoEIczMJEcKCKHwNaHCcv1EhcFx8L6jQeqV8LKyb31oP8qjGAhTPKUn
sAYPhuka1ynnUQTtWE4qmsNXG/wyXXNs+L4ZtutMFLdhD8dtSHyW0xTIjTP1gN/0
sCAbW8r+FQIVrca51YXgbrg1jSsL8mfd4XuseBiEfeVPwwGvIf7wZoQWxr56AOk3
x3YbEimg6MDkKu3FKa3zU5w5Dl6AWtI7OUr/vnh9s9d4d4QLgaV8qGC3jShDVQDG
q1noudkN5TC9dzTc+3jMPhNu0sOk/J73U8oEvPjr9IWg52BjpywHbc2UvmUqTmZ4
zxu1JJQ4NYDfj/zX90P4iPzngPDyKQvw8lm1N8vCnKwO87qthjG69sK9vqo4ZrSp
20pRRxiOK0vIOgmQ2dJeDRkZa6z5jQDgMr2aNeyd7isw4ristzamwnMNI5j35ERU
gsOd1N+FE1TvgXsoX2l64Q5l5RwYKp7qO9TzOyXc2hb6uTUjql4SOJp6jgznRehs
4ACwRqCAVW2vpTB1tswrevL2Rmmy4TKZ7UULpona1CR8OGFRuzUPzSSh9vqalnzS
1ixavPLiixHFyNB1fXCIiYgOHL+oTwaPUfP/nT1n6ChlAmXtOLw=
=lOpH
-END PGP SIGNATURE-

Bug#819893: NMU ahead

[Holger Levsen]

Hi,

I plan to upload a fix for this bug (#819893: libsasl2-modules:amd64:
unnecessary exec perm on /etc/logcheck/ignore.d.server/libsasl2-modules) to 
DELAYED-3 in a moment, using the patch from Andreas (in this bug), plus 
filing an unblock request to get the fix into stretch.

This bug blocks >5000 packages in jessie2stretch-rcmd from being piuparts 
tested… and as recommends are enabled by default, I think thats actually an 
interesting suite to be tested, so we should make this possible.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#854588: debian-installer: recognize arrow keys as esc in serial console

[John Paul Adrian Glaubitz]

Hi!

On 03/15/2017 10:45 AM, John Paul Adrian Glaubitz wrote:
>> For most keys, it seems works well, while when press
>> arrow keys "up"/"down"/"left"/"right",
>> they are recognized as 'ESC' key.
> 
> We are seeing this issue on sparc64 now as well when using a serial
> console for the installation. Using the arrow keys in the serial
> console leads to random key presses (not sure whether it's 
> or  here), it did work fine in the past.

Michael Karcher (CC'ed) has had a go at this and it seems it is an issue
with the serial connection dropping some characters during transmission.

Since the cursor keys generate escape sequences in the terminal, the
transmission for a cursor key press needs to be stable over several
characters.

Invoking "infocmp ansi" will print out the escape sequences for various
terminal actions. The cursor movement is controlled by these sequences:

cr=^M, cub=\E[%p1%dD, cub1=\E[D, cud=\E[%p1%dB, cud1=\E[B,
cuf=\E[%p1%dC, cuf1=\E[C, cup=\E[%i%p1%d;%p2%dH,
cuu=\E[%p1%dA, cuu1=\E[A, dch=\E[%p1%dP, dch1=\E[P,

As you can see, these sequences usually involve  plus additional
characters. So, what happens in the case of Debian installer is that the
characters after the  are dropped and instead of the escape sequence,
the terminal application (debian-installer) is receiving  only
which results in an escape key press.

As possible cause for the issue might be a bug in the FIFO implementation
of the serial connection. Michael will hopefully correct me if I am wrong.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#858168: New upstream version

[Eduard Bloch]

Package: terminator
Version: 1.91-1
Severity: serious
Tags: upstream patch

Hi,

Upstream released a new minor stable version weeks ago and it seems to
fix at least a couple of bugs reported here.

Setting serious severity because I consider #857562 and #852282 actually
RC (it breaks popular user features on XFCE and partly with IceWM and
probably others) and because the maintainer(s) are basically MIA.

Patch attached with NMU ultimatum, 10 days from now.

Best regards,
Eduard.

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

Kernel: Linux 4.10.0+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages terminator depends on:
ii  gir1.2-glib-2.0   1.50.0-1+b1
ii  gir1.2-gtk-3.03.22.8-1
ii  gir1.2-pango-1.0  1.40.3-3
ii  gir1.2-vte-2.91   0.46.1-1
ii  python-cairo  1.8.8-2.1
ii  python-dbus   1.2.4-1
ii  python-gi 3.22.0-2
ii  python-gi-cairo   3.22.0-2
ii  python-psutil 5.0.1-1
pn  python:any

Versions of packages terminator recommends:
ii  gir1.2-keybinder-3.0  0.3.1-1
ii  gir1.2-notify-0.7 0.7.7-1+b1
ii  xdg-utils 1.1.1-1

terminator suggests no packages.

-- no debconf information

-- 
Trost gibt der Himmel, von den Menschen erwartet man Beistand.
-- Ludwig Börne
Index: debian/changelog
===
--- debian/changelog	(Revision 13918)
+++ debian/changelog	(Arbeitskopie)
@@ -1,3 +1,14 @@
+terminator (1.91-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream version
++ opening in folder works with thunar (closes: #857562)
++ crazy new window handling fixed (closes: #852282, LP: #1646437)
+  * dropped Debian patches applied upstream (add-keywords-entry.diff,
+gi-require-exception.diff, subwindows-zero-size.patch)
+
+ -- Eduard Bloch   Sun, 19 Mar 2017 11:12:18 +0100
+
 terminator (1.90+bzr-1705-1) unstable; urgency=medium
 
   * New upstream snapshot.
Index: debian/patches/add-keywords-entry.diff
===
--- debian/patches/add-keywords-entry.diff	(Revision 13918)
+++ debian/patches/add-keywords-entry.diff	(nicht existent)
@@ -1,16 +0,0 @@
-Description: Add Keywords entry to the desktop file.
-Forwarded: https://bugs.launchpad.net/bugs/1241052
-Author: Julián Moreno Patiño 
-Last-Update: 2013-10-17
 a/data/terminator.desktop.in
-+++ b/data/terminator.desktop.in
-@@ -9,8 +9,8 @@
- StartupNotify=true
- X-Ubuntu-Gettext-Domain=terminator
- X-Ayatana-Desktop-Shortcuts=NewWindow;
-+Keywords=terminal;shell;prompt;command;commandline;
- [NewWindow Shortcut Group]
- Name=Open a New Window
- Exec=terminator
- TargetEnvironment=Unity
--
Index: debian/patches/gi-require-exception.diff
===
--- debian/patches/gi-require-exception.diff	(Revision 13918)
+++ debian/patches/gi-require-exception.diff	(nicht existent)
@@ -1,28 +0,0 @@
-Author: Emilio Pozuelo Monfort 
-Bug: https://bugs.launchpad.net/terminator/+bug/1574399
-Description: catch all exceptions
-
-As gi.require_version throws ValueErrors
-
 a/terminatorlib/window.py
-+++ b/terminatorlib/window.py
-@@ -23,7 +23,7 @@
- gi.require_version('Keybinder', '3.0')
- from gi.repository import Keybinder
- Keybinder.init()
--except ImportError:
-+except:
- err('Warning: python-keybinder is not installed. This means the \
- hide_window shortcut will be unavailable')
- 
 a/terminatorlib/plugins/activitywatch.py
-+++ b/terminatorlib/plugins/activitywatch.py
-@@ -21,7 +21,7 @@
- # This is inside this try so we only make the plugin available if pynotify
- #  is present on this computer.
- AVAILABLE = ['ActivityWatch', 'InactivityWatch']
--except ImportError:
-+except:
- err(_('ActivityWatch plugin unavailable: please install python-notify'))
- 
- config = Config()
Index: debian/patches/series
===
--- debian/patches/series	(Revision 13918)
+++ debian/patches/series	(Arbeitskopie)
@@ -1,4 +1 @@
 not-install-terminator-wrapper.diff
-add-keywords-entry.diff
-gi-require-exception.diff
-subwindows-zero-size.patch
Index: debian/patches/subwindows-zero-size.patch
===
--- debian/patches/subwindows-zero-size.patch	(Revision 13918)
+++ debian/patches/subwindows-zero-size.patch	(nicht existent)
@@ -1,38 +0,0 @@
-From: Emilio Pozuelo Monfort 
-
-https://bugs.launchpad.net/terminator/+bug/1646257
-
-=== modified file 'terminatorlib/paned.py'
 a/terminatorlib/paned.py	2016-11-25 01:29:55 +
-+++ b/termin

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Rebecca N. Palmer]

Here's the 'version script' solution, now covering libLLVM, libclang, 
liblldb, libLTO, BugpointPasses, LLVMHello and LLVMgold (I suspect only 
the first 2-3 actually have use for it, but all except the first are set 
from the same place).


Warning: this hasn't been tested either, and the 
cmake/modules/AddLLVM.cmake modified here gets shipped in llvm-3.9-dev.


The full list of .so libraries built from llvm-toolchain-3.9:
llvm-3.9-dev:
./usr/lib/llvm-3.9/lib/libLTO.so 
-Wl,--version-script,/«PKGBUILDDIR»/build-llvm/tools/lto/LTO.exports
./usr/lib/llvm-3.9/lib/BugpointPasses.so 
-Wl,--version-script,/«PKGBUILDDIR»/build-llvm/tools/bugpoint-passes/BugpointPasses.exports
./usr/lib/llvm-3.9/lib/LLVMHello.so 
-Wl,--version-script,/«PKGBUILDDIR»/build-llvm/lib/Transforms/Hello/LLVMHello.exports
./usr/lib/llvm-3.9/lib/LLVMPolly.so none, linked from 
build-llvm/tools/polly/lib
./usr/lib/llvm-3.9/lib/LLVMgold.so 
-Wl,--version-script,/«PKGBUILDDIR»/build-llvm/tools/gold/LLVMgold.exports

libllvm3.9:
./usr/lib/i386-linux-gnu/libLLVM-3.9.so.1
liblldb-3.9:
./usr/lib/llvm-3.9/lib/python2.7/site-packages/readline.so none, linked 
from build-llvm/tools/lldb/scripts/Python/modules/readline
./usr/lib/i386-linux-gnu/liblldb-3.9.so.1 
-Wl,--version-script,/«PKGBUILDDIR»/build-llvm/tools/lldb/source/API/liblldb.exports

libclang1-3.9:
./usr/lib/i386-linux-gnu/libclang-3.9.so.1 
-Wl,--version-script,/«PKGBUILDDIR»/build-llvm/tools/clang/tools/libclang/libclang.exports

libclang-common-3.9-dev:
./usr/lib/llvm-3.9/lib/clang/3.9.1/lib/linux/libclang_rt.dyndd-x86_64.so 
(only, though this is from the i386 build log...) none, linked from 
build-llvm/projects/compiler-rt/lib/tsan/dd
./usr/lib/llvm-3.9/lib/clang/3.9.1/lib/linux/libclang_rt.asan-x86_64.so 
-Wl,--version-script,/«PKGBUILDDIR»/build-llvm/projects/compiler-rt/lib/asan/clang_rt.asan-dynamic-x86_64.vers
./usr/lib/llvm-3.9/lib/clang/3.9.1/lib/linux/libclang_rt.asan-i686.so 
none, linked from build-llvm/projects/compiler-rt/lib/asan
./usr/lib/llvm-3.9/lib/clang/3.9.1/lib/linux/libclang_rt.asan-i386.so 
none, linked from build-llvm/projects/compiler-rt/lib/asan
diff -Nru llvm-toolchain-3.9-3.9.1/debian/changelog 
llvm-toolchain-3.9-3.9.1/debian/changelog
--- llvm-toolchain-3.9-3.9.1/debian/changelog   2017-03-12 09:01:10.0 
+
+++ llvm-toolchain-3.9-3.9.1/debian/changelog   2017-03-19 09:48:56.0 
+
@@ -1,3 +1,11 @@
+llvm-toolchain-3.9 (1:3.9.1-5local2) UNRELEASED; urgency=medium
+
+  * Allow '!pointer' in OpenCL (Closes: #857623)
+  * Add missing liblldb symlink (Closes: #857683)
+  * Use versioned symbols (Closes: #848368)
+
+ -- Rebecca N. Palmer   Sat, 18 Mar 2017 21:29:25 
+
+
 llvm-toolchain-3.9 (1:3.9.1-5) unstable; urgency=medium
 
   * Fix the incorrect symlink to scan-build-py (Closes: #856869)
diff -Nru llvm-toolchain-3.9-3.9.1/debian/liblldb-X.Y.links.in 
llvm-toolchain-3.9-3.9.1/debian/liblldb-X.Y.links.in
--- llvm-toolchain-3.9-3.9.1/debian/liblldb-X.Y.links.in2016-08-08 
16:02:20.0 +0100
+++ llvm-toolchain-3.9-3.9.1/debian/liblldb-X.Y.links.in2017-03-19 
09:47:46.0 +
@@ -1,3 +1,4 @@
 usr/lib/@DEB_HOST_MULTIARCH@/liblldb-@LLVM_VERSION@.so.1   
usr/lib/@DEB_HOST_MULTIARCH@/liblldb-@LLVM_VERSION@.so
 usr/lib/@DEB_HOST_MULTIARCH@/liblldb-@LLVM_VERSION@.so.1   
usr/lib/llvm-@LLVM_VERSION@/lib/liblldb.so.1
+usr/lib/@DEB_HOST_MULTIARCH@/liblldb-@LLVM_VERSION@.so.1   
usr/lib/llvm-@LLVM_VERSION@/lib/liblldb-@LLVM_VERSION@.so.1
 
diff -Nru 
llvm-toolchain-3.9-3.9.1/debian/patches/857623-allow-opencl-pointer-to-bool.diff
 
llvm-toolchain-3.9-3.9.1/debian/patches/857623-allow-opencl-pointer-to-bool.diff
--- 
llvm-toolchain-3.9-3.9.1/debian/patches/857623-allow-opencl-pointer-to-bool.diff
1970-01-01 01:00:00.0 +0100
+++ 
llvm-toolchain-3.9-3.9.1/debian/patches/857623-allow-opencl-pointer-to-bool.diff
2017-03-19 09:47:46.0 +
@@ -0,0 +1,20 @@
+Description: Allow "if (!pointer)" in OpenCL 1.1
+
+Used by e.g. Blender on mesa-opencl-icd
+
+Author: Anastasia Stulova
+Origin: upstream https://reviews.llvm.org/rL294313
+Bug: https://bugs.llvm.org/show_bug.cgi?id=30217
+Bug-Debian: https://bugs.debian.org/857623
+
+--- llvm-toolchain-3.9-3.9.1.orig/clang/lib/Sema/SemaExpr.cpp
 llvm-toolchain-3.9-3.9.1/clang/lib/Sema/SemaExpr.cpp
+@@ -11424,7 +11424,7 @@ ExprResult Sema::CreateBuiltinUnaryOp(So
+  Context.getLangOpts().OpenCLVersion < 120) {
+ // OpenCL v1.1 6.3.h: The logical operator not (!) does not
+ // operate on scalar float types.
+-if (!resultType->isIntegerType())
++if (!resultType->isIntegerType() && !resultType->isPointerType())
+   return ExprError(Diag(OpLoc, diag::err_typecheck_unary_expr)
+<< resultType << Input.get()->getSourceRange());
+   }
diff -Nru llvm-toolchain-3.9-3.9.1/debian/patches/add_symbols_versioning.patch 
llvm-toolchain-3.9-3.9.1/debian/patches/add_symbols_ve

Bug#853929: (no subject)

[Ulrike Uhlig]

Proposed Douglas' patch here:

https://code.launchpad.net/~u-d/apparmor-profiles/+git/apparmor-profiles/+ref/thunderbird/links

Bug#858169: apt-listchanges: [INTL:de] Initial German documentation translation

[Chris Leick]

Package: apt-listchanges
Version: 3.9
Severity: wishlist
Tags: l10n patch


Hi,

please find attached the initial German documentation translation.
(apt-listchanges-3.9/doc/po/de.po)

Kind regards,
Chris


de.po.gz
Description: application/gzip

Bug#841452: tgtd != open-iscsi

[David Rabel]

Hi Turbo,

someone may correct if I'm wrong. But AFAIR open-iscsi is the initiator
part and tgtd is the target part of iscsi. So in your case it is
probably correct that both are running. That means cinder-volume does
need tgtd, not "tgtd or open-iscsi".

I hope that helps.

Yours
  David



signature.asc
Description: OpenPGP digital signature

Bug#858170: awesome: Package new upstream version 4.1

[Julian Wollrath]

Package: awesome
Version: 4.0-1
Severity: wishlist
Tags: patch

Dear Maintainer,

upstream has released version 4.1. The attached patches update the
debian packaging for that version.


Best regards,
Julian Wollrath

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


-- 
 ()  ascii ribbon campaign - against html e-mail 
 /\- against proprietary attachments
From b23927006592b80b83541c274c00c092d56ffaf2 Mon Sep 17 00:00:00 2001
From: Julian Wollrath 
Date: Sun, 19 Mar 2017 10:51:51 +0100
Subject: [PATCH 1/6] Run wrap-and-sort

---
 debian/awesome.install |  2 +-
 debian/control | 72 +-
 2 files changed, 37 insertions(+), 37 deletions(-)

diff --git a/debian/awesome.install b/debian/awesome.install
index e50e2c74..7ff29bf2 100644
--- a/debian/awesome.install
+++ b/debian/awesome.install
@@ -1,2 +1,2 @@
-debian/awesome.xpm usr/share/pixmaps
 debian/55awesome-javaworkaround /etc/X11/Xsession.d
+debian/awesome.xpm usr/share/pixmaps
diff --git a/debian/control b/debian/control
index 43fb79f1..7a6c1ed3 100644
--- a/debian/control
+++ b/debian/control
@@ -3,34 +3,34 @@ Section: x11
 Priority: optional
 Maintainer: Julien Danjou 
 Uploaders: Arnaud Fontaine 
-Build-Depends: debhelper (>= 9),
-  libcairo2-dev,
-  xmlto,
-  asciidoc,
-  cmake (>= 2.6.0),
-  lua5.1,
-  lua-ldoc,
-  libxcb-xtest0-dev,
-  libxcb-icccm4-dev (>= 0.3.8),
-  libxcb-randr0-dev (>= 0.3.0),
-  libxcb-keysyms1-dev (>= 0.3.4),
-  libxcb-xinerama0-dev,
-  liblua5.1-dev,
-  libdbus-1-dev,
-  libxdg-basedir-dev (>= 1.0.0),
-  libstartup-notification0-dev (>= 0.10),
-  imagemagick,
-  libxcb1-dev (>= 1.6),
-  libxcb-shape0-dev,
-  libxcb-util0-dev,
-  libxcb-cursor-dev (>= 0.1.0-2),
-  libgdk-pixbuf2.0-dev,
-  libglib2.0-dev,
-  libxcb-xrm-dev,
-  libxcb-xkb-dev,
-  libxkbcommon-x11-dev,
-  libxkbcommon-dev,
-  lua-lgi (>= 0.7.0),
+Build-Depends: asciidoc,
+   cmake (>= 2.6.0),
+   debhelper (>= 9),
+   imagemagick,
+   libcairo2-dev,
+   libdbus-1-dev,
+   libgdk-pixbuf2.0-dev,
+   libglib2.0-dev,
+   liblua5.1-dev,
+   libstartup-notification0-dev (>= 0.10),
+   libxcb-cursor-dev (>= 0.1.0-2),
+   libxcb-icccm4-dev (>= 0.3.8),
+   libxcb-keysyms1-dev (>= 0.3.4),
+   libxcb-randr0-dev (>= 0.3.0),
+   libxcb-shape0-dev,
+   libxcb-util0-dev,
+   libxcb-xinerama0-dev,
+   libxcb-xkb-dev,
+   libxcb-xrm-dev,
+   libxcb-xtest0-dev,
+   libxcb1-dev (>= 1.6),
+   libxdg-basedir-dev (>= 1.0.0),
+   libxkbcommon-dev,
+   libxkbcommon-x11-dev,
+   lua-ldoc,
+   lua-lgi (>= 0.7.0),
+   lua5.1,
+   xmlto
 Standards-Version: 3.9.7
 Homepage: http://awesome.naquadah.org
 Vcs-Git: git://anonscm.debian.org/collab-maint/awesome.git
@@ -38,14 +38,14 @@ Vcs-Browser: http://anonscm.debian.org/git/collab-maint/awesome.git
 
 Package: awesome
 Architecture: any
-Recommends: x11-xserver-utils, rlwrap, feh
-Depends: ${shlibs:Depends},
-  ${misc:Depends},
-  menu,
-  dbus-x11,
-  lua-lgi (>= 0.7.0),
-  gir1.2-freedesktop,
-  gir1.2-pango-1.0
+Recommends: feh, rlwrap, x11-xserver-utils
+Depends: dbus-x11,
+ gir1.2-freedesktop,
+ gir1.2-pango-1.0,
+ lua-lgi (>= 0.7.0),
+ menu,
+ ${misc:Depends},
+ ${shlibs:Depends}
 Provides: x-window-manager
 Description: highly configurable X window manager
  awesome manages windows dynamically in floating or tiled layouts. It is
-- 
2.11.0

From 4540e01a36973244413e14a282afd5f756349a31 Mon Sep 17 00:00:00 2001
From: Julian Wollrath 
Date: Sun, 19 Mar 2017 11:14:28 +0100
Subject: [PATCH 2/6] Update build dependencies

---
 debian/control | 13 -
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/debian/control b/debian/control
index 7a6c1ed3..3287d0a2 100644
--- a/debian/control
+++ b/debian/control
@@ -12,24 +12,27 @@ Build-Depends: asciidoc,
libgdk-pixbuf2.0-dev,
libglib2.0-dev,
liblua5.1-dev,
+   libpango1.0-dev,
libstartup-notification0-dev (>= 0.10),
-   libxcb-cursor-dev (>= 0.1.0-2),
+   libx11-xcb-dev,
+   libxcb-cursor-dev,
libxcb-icccm4-dev (>= 0.3.8),
libxcb-keysyms1-dev (>= 0.3.4),
-   libxcb-randr0-dev (>= 0.3.0),
+   libxcb-randr0-dev,
libxcb-shape0-dev,
-   libxcb-util0-dev,
+   libxcb-util0-dev (>= 0.3.8),
libxcb-xinerama0-dev,
libxcb-xkb-dev,
libxcb-xrm-dev,
libxcb-

Bug#858171: openscenegraph outdated

[Peter Keel]

Source: openscenegraph
Version: 3.2.3
Severity: wishlist

Dear Maintainer,

I can't compile openmw, because openscenegraph is way too old:

  Could NOT find OpenSceneGraph: Found unsuitable version "3.2.3", but
  required is at least "3.3.4" (found

And there's no newer version than 3.2.3 available, not even in
experimental.

I'd be grateful if you could package a newer version.


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

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

Bug#847104: I was not able to reproduce

[David Rabel]

Hi Turbo,

I was no able to reproduce this error here. Could you provide some more
information about your environment?

Also could you provide the output of running this after running 'set -x'?

And it seems that you already have an idea what is the problem. If so,
could explain your thoughts a little more?

Yours
  David



signature.asc
Description: OpenPGP digital signature

Bug#858172: nanomsg FTBFS on armel: tests/ipc_shutdown fails

[Adrian Bunk]

Source: nanomsg
Version: 0.8~beta+dfsg-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=nanomsg&arch=armel&ver=0.8~beta%2Bdfsg-1%2Bb1&stamp=1489891037&raw=0

...
make  check-TESTS
make[3]: Entering directory '/«BUILDDIR»/nanomsg-0.8~beta+dfsg'
make[4]: Entering directory '/«BUILDDIR»/nanomsg-0.8~beta+dfsg'
PASS: tests/inproc
PASS: tests/inproc_shutdown
PASS: tests/ipc
./test-driver: line 107: 12350 Aborted "$@" > $log_file 2>&1
FAIL: tests/ipc_shutdown
PASS: tests/ipc_stress
PASS: tests/tcp
PASS: tests/tcp_shutdown
PASS: tests/ws
PASS: tests/tcpmux
PASS: tests/pair
PASS: tests/pubsub
PASS: tests/reqrep
PASS: tests/pipeline
PASS: tests/survey
PASS: tests/bus
PASS: tests/async_shutdown
PASS: tests/block
PASS: tests/term
PASS: tests/timeo
PASS: tests/iovec
PASS: tests/msg
PASS: tests/prio
PASS: tests/poll
PASS: tests/device
PASS: tests/device4
PASS: tests/device5
PASS: tests/emfile
PASS: tests/domain
PASS: tests/trie
PASS: tests/list
PASS: tests/hash
PASS: tests/symbol
PASS: tests/separation
PASS: tests/zerocopy
PASS: tests/shutdown
PASS: tests/cmsg
PASS: tests/bug328

   nanomsg : ./test-suite.log


# TOTAL: 37
# PASS:  36
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tests/ipc_shutdown


Unexpected source: state=5 source=1 action=5 
(src/transports/utils/streamhdr.c:306)
FAIL tests/ipc_shutdown (exit status: 134)


Testsuite summary for nanomsg 

# TOTAL: 37
# PASS:  36
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to nano...@freelists.org

Makefile:3350: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1

Bug#848559: zeroinstall-injector: Don't recommend python3-aptdaemon.pkcompat

[Thomas Leonard]

On 16 March 2017 at 08:15, Mattia Rizzolo  wrote:
> On Sun, Jan 01, 2017 at 11:01:16AM +, Thomas Leonard wrote:
>> OK. I've removed it from the control file:
>>
>> https://github.com/0install/0install-debian/commit/0dc07b3cd4487fb0bed282495ccef26ed314fbe0
>>
>> Here's a 2.12-3 version with the change, if someone wants to approve it:
>>
>>   https://mentors.debian.net/package/zeroinstall-injector
>
> Are you still looking for a sponsor and would you like to see it in
> streatch?
> If so, I'll happily sponsor it after a refresh of the date in the
> changelog.

Thanks for the offer. I have now got my replacement key approved (this
week), and I'm just waiting for the acl at
https://ftp-master.debian.org/dm.txt to be updated (rt.debian.org
#5239]). Once that's done, I can update the package myself.

I don't have any opinion on whether this fix needs to be in stretch or not.


-- 
talex5 (GitHub/Twitter)http://roscidus.com/blog/
GPG: 5DD5 8D70 899C 454A 966D  6A51 7513 3C8F 94F6 E0CC
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

Bug#858173: audacity: please upgrade audacity to 2.1.3

[Klaumi Klingsporn]

Package: audacity
Version: 2.1.2-2
Severity: wishlist

Dear Maintainer,

there is a new version out since last week:
http://www.audacityteam.org/download/

I tested it this weekend and it seems to work fine. 
(Note: While trying to compile the new sources with the same config-
options as the debian-package configure refuses to link against the 
system-libraries of LIBSBSMS and used the insource-version of the library.)

Would you please upgrade the package? This version has some nice improvements
(http://manual.audacityteam.org/man/new_features_in_this_release.html) and 
it would be nice to have it in stretch.

Thanks for maintaining the package!

Klaumi


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

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

Versions of packages audacity depends on:
ii  audacity-data   2.1.2-2
ii  libasound2  1.1.3-5
ii  libavcodec-extra57  7:3.2.4-1
ii  libavformat57   7:3.2.4-1
ii  libavutil55 7:3.2.4-1
ii  libc6   2.24-9
ii  libexpat1   2.2.0-2
ii  libflac++6v51.3.2-1
ii  libflac81.3.2-1
ii  libgcc1 1:6.3.0-6
ii  libgdk-pixbuf2.0-0  2.36.5-2
ii  libglib2.0-02.50.3-1
ii  libgtk2.0-0 2.24.31-2
ii  libid3tag0  0.15.1b-12
ii  liblilv-0-0 0.24.2~dfsg0-1
ii  libmad0 0.15.1b-8
ii  libmp3lame0 3.99.5+repack1-9+b2
ii  libogg0 1.3.2-1
ii  libportaudio2   19.6.0-1
ii  libportsmf0 0.1~svn20101010-5
ii  libsbsms10  2.0.2-2
ii  libsndfile1 1.0.27-1+b1
ii  libsoundtouch1  1.9.2-2+b1
ii  libsoxr00.1.2-2
ii  libstdc++6  6.3.0-6
ii  libsuil-0-0 0.8.4~dfsg0-2
ii  libtwolame0 0.3.13-2
ii  libvamp-hostsdk3v5  2.6~repack0-3
ii  libvorbis0a 1.3.5-4
ii  libvorbisenc2   1.3.5-4
ii  libvorbisfile3  1.3.5-4
ii  libwxbase3.0-0v53.0.2+dfsg-3
ii  libwxgtk3.0-0v5 3.0.2+dfsg-3

audacity recommends no packages.

Versions of packages audacity suggests:
ii  amb-plugins [ladspa-plugin]   0.8.1-7
ii  blop [ladspa-plugin]  0.2.8-6
ii  caps [ladspa-plugin]  0.9.24-4
ii  cmt [ladspa-plugin]   1.16-2
ii  fil-plugins [ladspa-plugin]   0.3.0-6
ii  guitarix-ladspa [ladspa-plugin]   0.35.2-2
ii  invada-studio-plugins-ladspa [ladspa-plugin]  0.3.1-4
ii  ladspa-sdk [ladspa-plugin]1.13-3
ii  rev-plugins [ladspa-plugin]   0.7.1-3
ii  ste-plugins [ladspa-plugin]   0.0.2-5
ii  swh-plugins [ladspa-plugin]   0.4.17-1
ii  tap-plugins [ladspa-plugin]   0.7.3-2
ii  wah-plugins [ladspa-plugin]   0.1.0-3

-- no debconf information

Bug#858171: openscenegraph outdated

[Alberto Luaces Fernández]

Dear Peter,

please use the 3.4 package, available in testing:

https://packages.qa.debian.org/o/openscenegraph-3.4.html

Regards,

Alberto

Bug#856122: calf-plugins: UI not loaded in ardour (works in the standelone app)

[Eugen Wintersberger]

Package: calf-plugins
Version: 0.0.60-4+b1
Followup-For: Bug #856122

Dear Maintainer,

I can confirm the Bug reported by Jean-Marie. Same issue here on my
box.The only thing I am not sure is whether this bug is related to the calf-
plugins package or to the ardour package.

regards
   Eugen



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

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

Versions of packages calf-plugins depends on:
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-9
ii  libcairo2 1.14.8-1
ii  libexpat1 2.2.0-2
ii  libfluidsynth11.1.6-4
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3+b2
ii  libgcc1   1:6.3.0-6
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libglib2.0-0  2.50.3-1
ii  libgtk2.0-0   2.24.31-2
ii  libjack-jackd2-0 [libjack-0.125]  1.9.10+20150825git1ed50c92~dfsg-4+b1
ii  libjs-jquery  3.1.1-2
ii  libjs-jquery-colorbox 1.6.3-1
ii  libpango-1.0-01.40.4-1
ii  libpangocairo-1.0-0   1.40.4-1
ii  libpangoft2-1.0-0 1.40.4-1
ii  libstdc++66.3.0-6

Versions of packages calf-plugins recommends:
ii  gtk2-engines-pixbuf  2.24.31-2

Versions of packages calf-plugins suggests:
pn  ladish  

-- no debconf information

Bug#858174: Please provide an AppArmor profile for Firefox

[Ulrike Uhlig]

Package: firefox
Severity: normal

Hi,

as you might know, AppArmor confines programs according to a set of
rules that specify what files a given program can access. This approach
helps protect the system against both known and unknown vulnerabilities.
In several distributions such as Ubuntu or Tails, AppArmor is enabled by
default.

I've not been able to find such a profile in the current Firefox package.

There is an AppArmor profile for Firefox available upstream:
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/firefox/vivid/view/head:/debian/usr.bin.firefox.apparmor.10.04
(this is the upstream profile which has been integrated into Ubuntu's
packaging of Firefox).

This profile is only active if people have installed AppArmor in first
case, so it should never break the package for users without AppArmor.

The profile can be included in your packaging quite easily.
All the necessary steps are documented here:
https://wiki.debian.org/AppArmor/Contribute/FirstTimeProfileImport

Please also see examples in the packages torbrowser-launcher or in
Icedove
(https://anonscm.debian.org/cgit/pkg-mozilla/icedove.git/tree/debian).

Please let me know if you need help.

Cheers!
ulrike

Bug#856845: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

[Holger Levsen]

Dear systemd maintainers,

On Sun, Mar 05, 2017 at 01:27:22PM +0100, Holger Levsen wrote:
> Package: piuparts.debian.org
> 
> the subject says it: jessie2bpo has >400 packages in dependency-failed-testing
> status, which is far too many for the stable release. We should track down the
> cause for this and fix it.
> 
> see https://piuparts.debian.org/jessie2bpo/

as https://piuparts.debian.org/jessie2bpo/state-failed-testing.html shows,
this is mostly due to libsystemd0 and udev (look at the numbers in brackets
after the package names on that last URL, those are the number of packages
affected…) which both fail as shown in 

https://piuparts.debian.org/jessie2bpo/fail/libsystemd0_230-7~bpo8+2.log
and https://piuparts.debian.org/jessie2bpo/fail/udev_230-7~bpo8+2.log

Both these logs contain this:

  Preparing to unpack .../udev_215-17+deb8u6_amd64.deb ...
  Unpacking udev (215-17+deb8u6) over (230-7~bpo8+2) ...
  Processing triggers for systemd (230-7~bpo8+2) ...
  dpkg: dependency problems prevent configuration of udev:
   systemd (230-7~bpo8+2) breaks udev (<< 228-5) and is installed.
Version of udev to be configured is 215-17+deb8u6.

  dpkg: error processing package udev (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   udev
  E: Sub-process /usr/bin/dpkg returned an error code (1)


As I see it this is because we only tell apt-get to install udev from
backports but dont tell it to also upgrade systemd to that version, so this
is probably rather a bug in apt (or maybe piuparts) but not in src:systemd.

Do you agree?


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#855951: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

[Carsten Leonhardt]

Michael Biebl  writes:

> If you are sure it fixes the issue, feel free to upload without delay.

I've made a dozen test runs of the collection tests on arm64, all
passed. After double checking the buildd logs, I noticed a different
failing test on mipsel, I've made 5 complete test runs there without
failure.

I'll move it to delayed/0 shortly.

 - Carsten

Bug#858175: libunistring: New upstream version 0.9.7

[Andreas Metzler]

Source: libunistring
Version: 0.9.6+really0.9.3-0.1
Severity: wishlist

libunistring was released in December 2017 with the following importatnt
change:
The license has changed from LGPLv3+ to "LGPLv3+ or GPLv2"

cu Andreas

Bug#857531: spambayes: broken symlink: /usr/bin/sb_notesfilter.py -> /usr/bin/sb_notesfilter

[Andreas Metzler]

Control: tags -1 patch

On 2017-03-12 Andreas Beckmann  wrote:
> Package: spambayes
> Version: 1.1b1-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts

> Hi,

> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.

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

> 0m32.2s ERROR: FAIL: Broken symlinks:
>   /usr/bin/sb_notesfilter.py -> /usr/bin/sb_notesfilter


Find attached a trivial debdiff. I won't do a NMU since the package has
not seen a maintainer upload for almost 3 years (dh compat v5).

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru spambayes-1.1b1/debian/changelog spambayes-1.1b1/debian/changelog
--- spambayes-1.1b1/debian/changelog	2014-06-13 14:25:16.0 +0200
+++ spambayes-1.1b1/debian/changelog	2017-03-19 13:15:11.0 +0100
@@ -1,3 +1,12 @@
+spambayes (1.1b1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Do not generate symlink sb_notesfilter.py -> sb_notesfilter in postinst,
+the script is not shipped. (Keep the the removal code in prerm.)
+Closes: #857531
+
+ -- Andreas Metzler   Sun, 19 Mar 2017 13:15:11 +0100
+
 spambayes (1.1b1-1) unstable; urgency=low
 
   [ Jakub Wilk ]
diff -Nru spambayes-1.1b1/debian/spambayes.postinst spambayes-1.1b1/debian/spambayes.postinst
--- spambayes-1.1b1/debian/spambayes.postinst	2014-06-13 12:16:24.0 +0200
+++ spambayes-1.1b1/debian/spambayes.postinst	2017-03-19 13:13:16.0 +0100
@@ -6,7 +6,7 @@
 SCRIPTS="sb_xmlrpcserver sb_server sb_bnfilter sb_mailsort \
 sb_unheader sb_client sb_filter sb_mboxtrain sb_bnserver \
 sb_chkopts sb_upload sb_dbexpimp sb_imapfilter \
-sb_notesfilter sb_evoscore"
+sb_evoscore"
 
 
 if [ "$1" = configure ] ; then

Bug#858176: pulseaudio: module-combine is deprecated

[Cristian Ionescu-Idbohrn]

Package: pulseaudio
Version: 10.0-1
Severity: normal

I see these log messages:

/var/log/user.log:Mar 18 22:43:50 debian pulseaudio[5682]: [pulseaudio] 
module.c: module-combine is deprecated: Please use module-combine-sink instead 
of module-combine!
/var/log/user.log:Mar 18 22:43:50 debian pulseaudio[5682]: [pulseaudio] 
module-combine.c: We will now load module-combine-sink. Please make sure to 
remove module-combine from your configuration.

but I can't find any 'module-combine' reference in the configuration
files, neither under /etc/pulse nor ~/.pulse.  I see though both libs:

pulseaudio: /usr/lib/pulse-10.0/modules/module-combine-sink.so
pulseaudio: /usr/lib/pulse-10.0/modules/module-combine.so

are distributed.  My conclusion is that the deprecated module-combine
is loaded by default.  What can I do to avoid seeing those messages?

I do see some traces of the word 'combine' in the output from:

$ pactl info
Server String: /tmp/pulse-2L9K88eMlGn7/native
Library Protocol Version: 32
Server Protocol Version: 32
Is Local: yes
Client Index: 7
Tile Size: 65496
User Name: foo
Host Name: debian
Server Name: pulseaudio
Server Version: 10.0
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-_00_1b.0.analog-stereo
Default Source: combined.monitor

Cookie: b907:c1f0

and:

$ pactl list
Module #13
Name: module-combine
Argument:
Usage counter: n/a
Properties:
module.author = "Colin Guthrie"
module.description = "Compatibility module (module-combine 
rename)"
module.version = "10.0"

Module #14
Name: module-combine-sink
Argument:
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Combine multiple sinks to one"
module.version = "10.0"

Sink #1
State: SUSPENDED
Name: combined
Description: Simultaneous output to Built-in Audio Analog Stereo
Driver: module-combine-sink.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 14
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: combined.monitor
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY
Properties:
device.class = "filter"
device.description = "Simultaneous output to Built-in Audio 
Analog Stereo"
device.icon_name = "audio-card"
Formats:
pcm

Source #2
State: SUSPENDED
Name: combined.monitor
Description: Monitor Source of Simultaneous output to Built-in Audio 
Analog Stereo
Driver: module-combine-sink.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 14
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor of Sink: combined
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY
Properties:
device.description = "Monitor Source of Simultaneous output to 
Built-in Audio Analog Stereo"
device.class = "monitor"
device.icon_name = "audio-input-microphone"
Formats:
pcm



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


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

Kernel: Linux 4.9.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1:1.1.1-dmo1
ii  libc62.24-9
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.16-1
ii  libgcc1  1:6.3.0-6
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.27-1+b1
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-6
ii  libsystemd0  232-19
ii  libtdb1  1.3.11-2
ii  libudev1 232-19
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1   

Bug#855671: chaussette: FTBFS: ConnectionError: HTTPConnectionPool(host='localhost', port=8080): Max retries exceeded with url: /

[Evgeni Golov]

Control: tags -1 + patch

On Sun, Mar 19, 2017 at 10:06:01AM +0100, Evgeni Golov wrote:
> > > socket.error: [Errno 92] Protocol not available
> > 
> > That's probably https://github.com/circus-tent/chaussette/issues/82?
> > But the traceback looks different, so not setting forwarded just yet.
> 
> Confirmed, downgading python-waitress to 0.8.10-1 from snapshot.d.o makes the 
> test succeed.

I posted a patch [1] upstream [2], let's see what they think.

[1] 
https://github.com/circus-tent/chaussette/pull/83/commits/e10c891bb2a003dd7827f7d96bf458e0e4ca2dd8
[2] https://github.com/circus-tent/chaussette/pull/83

Bug#858177: CVE-2016-3921

[Moritz Muehlenhoff]

Source: android-platform-system-core
Severity: grave
Tags: security

Please see
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3921

Cheers,
Moritz

Bug#856122: calf-plugins: UI not loaded in ardour (works in the standelone app)

[Klaumi Klingsporn]

Am / On Sun, 19 Mar 2017 12:45:51 +0100
schrieb / wrote Eugen Wintersberger :

> I can confirm the Bug reported by Jean-Marie. Same issue here on my
> box.The only thing I am not sure is whether this bug is related to
> the calf- plugins package or to the ardour package.

I can NOT confirm this.

I just tried calf-reverb with ardour-5.5 from the
debian-testing-package, with the ardour-5.5-binaries from ardour.org
and with a self-packaged ardour-4.7 (which I normally use because of
ardour-bug 0007022 in the 5.x-series), and in all versions of
ardour the plugin and its GUI just works fine.

Does your reported bug only appear with some calf-plugins?

Klaumi


---
Klaus-Michael Klingsporn 
mail: klaumi...@gmx.de
web: www.klaumikli.de

Bug#858178: uuidcdef: buffer overflow

[Christian Buhtz]

Package: uuidcdef
Version: 0.3.13-6
Severity: normal

Dear Maintainer,

I simply tried to run "uuidcdef" and got this output.

user@TONNE:/etc$ uuidcdef
*** buffer overflow detected ***: uuidcdef terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7fcfa7284bcb]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7fcfa730d0b7]
/lib/x86_64-linux-gnu/libc.so.6(+0xf71f0)[0x7fcfa730b1f0]
/lib/x86_64-linux-gnu/libc.so.6(+0xf67a9)[0x7fcfa730a7a9]
/lib/x86_64-linux-gnu/libc.so.6(_IO_default_xsputn+0xac)[0x7fcfa7288bdc]
/lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x789)[0x7fcfa725b4a9]
/lib/x86_64-linux-gnu/libc.so.6(__vsprintf_chk+0x8c)[0x7fcfa730a83c]
/lib/x86_64-linux-gnu/libc.so.6(__sprintf_chk+0x7d)[0x7fcfa730a78d]
uuidcdef(+0xd5b)[0x563bec86bd5b]
uuidcdef(+0xa7b)[0x563bec86ba7b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fcfa72342b1]
uuidcdef(+0xad9)[0x563bec86bad9]
=== Memory map: 
563bec86b000-563bec86d000 r-xp  08:01 95421035
/usr/bin/uuidcdef
563beca6c000-563beca6d000 r--p 1000 08:01 95421035
/usr/bin/uuidcdef
563beca6d000-563beca6e000 rw-p 2000 08:01 95421035
/usr/bin/uuidcdef
563becad6000-563becaf7000 rw-p  00:00 0  [heap]
7fcfa6df8000-7fcfa6e0e000 r-xp  08:01 95683143
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fcfa6e0e000-7fcfa700d000 ---p 00016000 08:01 95683143
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fcfa700d000-7fcfa700e000 r--p 00015000 08:01 95683143
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fcfa700e000-7fcfa700f000 rw-p 00016000 08:01 95683143
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fcfa700f000-7fcfa7013000 r-xp  08:01 95682770
/lib/x86_64-linux-gnu/libuuid.so.1.3.0
7fcfa7013000-7fcfa7212000 ---p 4000 08:01 95682770
/lib/x86_64-linux-gnu/libuuid.so.1.3.0
7fcfa7212000-7fcfa7213000 r--p 3000 08:01 95682770
/lib/x86_64-linux-gnu/libuuid.so.1.3.0
7fcfa7213000-7fcfa7214000 rw-p 4000 08:01 95682770
/lib/x86_64-linux-gnu/libuuid.so.1.3.0
7fcfa7214000-7fcfa73a9000 r-xp  08:01 9567
/lib/x86_64-linux-gnu/libc-2.24.so
7fcfa73a9000-7fcfa75a8000 ---p 00195000 08:01 9567
/lib/x86_64-linux-gnu/libc-2.24.so
7fcfa75a8000-7fcfa75ac000 r--p 00194000 08:01 9567
/lib/x86_64-linux-gnu/libc-2.24.so
7fcfa75ac000-7fcfa75ae000 rw-p 00198000 08:01 9567
/lib/x86_64-linux-gnu/libc-2.24.so
7fcfa75ae000-7fcfa75b2000 rw-p  00:00 0
7fcfa75b2000-7fcfa75d5000 r-xp  08:01 95686995
/lib/x86_64-linux-gnu/ld-2.24.so
7fcfa77a8000-7fcfa77ab000 rw-p  00:00 0
7fcfa77d1000-7fcfa77d5000 rw-p  00:00 0
7fcfa77d5000-7fcfa77d6000 r--p 00023000 08:01 95686995
/lib/x86_64-linux-gnu/ld-2.24.so
7fcfa77d6000-7fcfa77d7000 rw-p 00024000 08:01 95686995
/lib/x86_64-linux-gnu/ld-2.24.so
7fcfa77d7000-7fcfa77d8000 rw-p  00:00 0
7ffc8c9bd000-7ffc8c9de000 rw-p  00:00 0
[stack]
7ffc8c9ed000-7ffc8c9ef000 r--p  00:00 0  [vvar]
7ffc8c9ef000-7ffc8c9f1000 r-xp  00:00 0  [vdso]
ff60-ff601000 r-xp  00:00 0
[vsyscall]
Abgebrochen

And by the way: The manpage mentioned the existence of "uuidgen". But it is not
in the system.

kind



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

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

Versions of packages uuidcdef depends on:
ii  libc6 2.24-9
ii  libuuid1  2.29.1-1

uuidcdef recommends no packages.

uuidcdef suggests no packages.

-- no debconf information

Bug#819893: NMU ahead

[Holger Levsen]

Hi,

On Sun, Mar 19, 2017 at 10:28:38AM +, Holger Levsen wrote:
> I plan to upload a fix for this bug (#819893: libsasl2-modules:amd64:
> unnecessary exec perm on /etc/logcheck/ignore.d.server/libsasl2-modules) to 
> DELAYED-3 in a moment, using the patch from Andreas (in this bug),

I've uploaded this to DELAYED-2 just now.

> plus 
> filing an unblock request to get the fix into stretch.

Will do once the package hits sid.

Will then also file a "please acknowledge and include NMU" bug then, unless
you dont want that, either because you include the change into git already or
because you've done an upload yourself, which invalidated my NMU.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#858165: Acknowledgement (firefox: audio playback has stopped to work without pulseaudio)

[Roman Tsisyk]

BTW, the latest version of Flash Player doesn't support Pulse Audio. I've 
managed to get working playback via ALSA->PulseAudio->ALSA emulation, but 
microphone still doesn't work at all.  I would like to completely exclude Flash 
Player from my live, but it is still needed for some business tasks.

-- 
WBR,
  Roman Tsisyk 
  http://tarantool.org/ - an efficient in-memory data store and a Lua 
application server

Bug#857396: open-font-design-toolkit: Depends on fontforge-doc in testing while fontforge-doc was removed from unstable

[Ivo De Decker]

Hi,

On Sat, Mar 11, 2017 at 11:21:34PM +0100, Ivo De Decker wrote:
> On Fri, Mar 10, 2017 at 07:46:22AM +0100, Niels Thykier wrote:
> > In testing, open-font-design-toolkit depends on fontforge-doc and in
> > unstable said dependency is removed (since fontforge-doc was removed
> > from unstable).
> > 
> > Unfortunately, open-font-design-toolkit/1.6 depends on the RC-buggy
> > fontmatrix (which is *not* in testing), so the fix cannot migrate.
> 
> It seems the changes from 1.5.1 are not included in 1.6, so 1.6 reintroduced
> the issues from 1.5. Merging 1.5.1 and 1.6 will probably fix this bug.

I uploaded an NMU to fix this. The debdiff is attached.

Cheers,

Ivo

diff -Nru open-font-design-toolkit-1.6/debian/changelog 
open-font-design-toolkit-1.6+nmu1/debian/changelog
--- open-font-design-toolkit-1.6/debian/changelog   2017-02-13 
23:41:56.0 +0100
+++ open-font-design-toolkit-1.6+nmu1/debian/changelog  2017-03-19 
12:45:53.0 +0100
@@ -1,3 +1,11 @@
+open-font-design-toolkit (1.6+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Merge changes from 1.5.1 upload, which got dropped accidentally in the 1.6
+upload (Closes: #857396)
+
+ -- Ivo De Decker   Sun, 19 Mar 2017 12:45:53 +0100
+
 open-font-design-toolkit (1.6) unstable; urgency=medium
 
   * Team upload.
@@ -7,6 +15,16 @@
 
  -- Hideki Yamane   Tue, 14 Feb 2017 07:41:56 +0900
 
+open-font-design-toolkit (1.5.1) unstable; urgency=medium
+
+  * The aim is to make this package suitable for jessie
+  * debian/control
+- Remove dependency on currently unmaintained package cl-zpb-ttf
+- Move RC buggy fontmatrix to Recommends
+- set "Standards-Version: 3.9.6" (no change)
+
+ -- Daniel Glassey   Wed, 05 Nov 2014 18:55:33 +
+
 open-font-design-toolkit (1.5) unstable; urgency=medium
 
   * Team upload.
diff -Nru open-font-design-toolkit-1.6/debian/control 
open-font-design-toolkit-1.6+nmu1/debian/control
--- open-font-design-toolkit-1.6/debian/control 2017-02-13 23:41:56.0 
+0100
+++ open-font-design-toolkit-1.6+nmu1/debian/control2017-03-19 
12:40:07.0 +0100
@@ -4,7 +4,7 @@
 Maintainer: Debian Fonts Task Force 
 Uploaders: Nicolas Spalinger , Daniel Glassey 
, Martin Hosken  
 Build-Depends: debhelper (>= 9)
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
 Homepage: http://pkg-fonts.alioth.debian.org
 Vcs-Git: git://anonscm.debian.org/pkg-fonts/open-font-design-toolkit/
 Vcs-Browser: 
http://anonscm.debian.org/gitweb/?p=pkg-fonts/open-font-design-toolkit.git;a=summary
@@ -13,10 +13,10 @@
 Architecture: all
 Depends: fontforge, python-fontforge, fontforge-extras,
  inkscape, gimp, fonttools, grcompiler, libfont-ttf-perl, gucharmap, 
- gnome-specimen, lcdf-typetools, gwaterfall, freetype2-demos, cl-zpb-ttf,
- ghostscript, poppler-utils, fondu, fontmatrix, fontypython, 
+ gnome-specimen, lcdf-typetools, gwaterfall, freetype2-demos,
+ ghostscript, poppler-utils, fondu, fontypython, 
  libotf-bin, xgridfit, gozer, ${misc:Depends}
-Recommends: scribus, subversion, bzr, darcs, git, giggle, meld, mercurial
+Recommends: scribus, subversion, bzr, darcs, git, giggle, meld, mercurial, 
fontmatrix
 Description: metapackage for open font design
  This package provides all tools needed to design, adapt, improve and
  hack on open fonts, including recommendations for the ones needed to

Bug#851555: Blends install options removed from tasksel menu

[Ivo De Decker]

Control: tags -1 stretch-ignore

Hi,

On Mon, Jan 16, 2017 at 09:44:09AM +0100, Ole Streicher wrote:
> Since revision 3.39, tasksel limits the tasks to a predefined list in
> the installer, which ignores the blends task selection currently under
> CTTE discussion in #846002. The result of the discussion is still open,
> and this bug is created to mark tasksel as a potential target of the
> CTTE decision. BTW, I usually would have expected that all parties keep
> the status quo during the discussion until a decision is made; trying to
> undermine the discussion result is IMO improper and unfriendly behaviour.
> 
> The change (ba4e0289) also makes it more difficult for others to add
> items to the installer tasksel menu for customized builds without a
> technical reason. And any CTTE decision will anyway make the patch obsolete.

It looks like this might be an issue for after the stretch release.

Cheers,

Ivo

Bug#855096: unison: segfaults after connection has been established

[Norbert Preining]

Hi Stéphane,

> > since short time unison (gtk and text mode) is crashing with
> > sigsegv after the connection has been started.
> 
> What are the versions (and origin) of unison used at each endpoint? Can you
> reproduce the bug easily?

I *could* reproduce it even after a few reboots, but due to proper need
I have reverted to removing the cache files and let unison restart
checking everything.

THis was again a problem (ok, I am syncing a few hundred GB), as unison
has a very common tendency to just simply die, repeatedly.

I realized from iterated repeating that single *BIG* directories are
very prone to kill unison, while if I pre-populate the directory
hierarchy and each file is considered by itself, unison continues
without any problem despite the big amount of data transfered.
(So wild guess: some memory leak or other problem with big directories)

> I (and others) routinely run Unison 2.48.3-1 (on both ends) and I've never
> seen this bug. Since this bug doesn't seem to happen everywhere, I downgrade
> the severity to important.

I am using the latest versions available in Debian/sid, updated daily.

I tried to search for debug symbols, but there aren't any as far as I see,
so I am having a hard time debugging it.

If you have a suggestion how to debug it, please let me know.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#858168: new upstream version = wishlist

[Holger Levsen]

control: severity -1 wishlist
thanks

Eduard,

if you think that #857562 and #852282 are serious bugs, you need to convince
the maintainer that this is the case. Failing this, you can try to convince 
the release team, failing this, you can try the CTTE.

Filing a "please package new upstream version" bug and making this bug serious
is *NOT* the right way to do this. Seriously.

Please also note that the changes with this new upstream version are not
exactly trivial… (and the patch you attached to this bug only included the
Debian packaging changes, but not the upstream changes…)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#846998: nbd-server: Broken NBD configurations using a leading slash

[Wolfgang Schweer]

On Sat, Mar 18, 2017 at 08:03:44AM -0700, Vagrant Cascadian wrote:
> On 2017-03-18, Wolfgang Schweer wrote:
> > just a reminder for this issue. As you know, Debian Edu needs it fixed 
> > as well. 
> 
> The workaround for LTSP would be to add an additional stanza in the
> nbd-server configuration so that both behave the same.
> 
> [opt/ltsp/i386]
> 
> [/opt/ltsp/i386]

We have already documented a workaround on the Stretch status page:
https://wiki.debian.org/DebianEdu/Status/Stretch#Known_installation_related_issues
 
> The better solution would be to fix in nbd's initramfs hooks:
> 
> case nbdroot in
>   ^/*|*:/*) nbdpath= ...
>   nbdsrv= ... ;;
> esac

While trying to fix it there w/o success, I'm wondering if something 
like this would be ok (might be smarter, though):

diff --git a/server/ltsp-config b/server/ltsp-config
index c7fa7c4f..fb6f51a0 100755
--- a/server/ltsp-config
+++ b/server/ltsp-config
@@ -211,9 +211,12 @@ EOF
 echo "Removing old configuration file $conf in order to 
upgrade it"
 rm -f "$conf"
 fi
+echo "Adjusting old configuration file $conf to be compatible with NBD"
+sed -i "s#/opt/ltsp#opt/ltsp#" /etc/nbd-server/conf.d/ltsp_$name.conf
 fi
 
 if check_overwrite $conf; then
+BASE=$(echo $BASE | sed -e "s#/##")
 cat >"$conf" <

signature.asc
Description: PGP signature

Bug#709198: [Debconf-devel] Bug#709198: debconf: should not use python in maintainer scripts

[Ivo De Decker]

Control: tags -1 stretch-ignore

Hi,

On Sun, Jan 29, 2017 at 06:13:10PM +, Colin Watson wrote:
> On Sun, Jan 29, 2017 at 06:04:09PM +, Simon McVittie wrote:
> > On Sat, 18 May 2013 at 23:29:22 +0200, Richard Hartmann wrote:
> > > Broken Python upgrade left me without working debconf.
> > 
> > I can't help thinking that this would be a lot more robust if debconf.deb
> > (which is pseudo-Essential) didn't ship language bindings for a
> > non-Essential programming language. perl-base and sh are Essential,
> > but python (even the -minimal flavour) isn't.
> 
> Yes, I think this is probably the best fix.  I've been putting it off
> because it's somewhat tedious to rearrange everything, but you're quite
> right.
> 
> > According to  and
> > , if
> > debconf.py was split out into python-debconf and python3-debconf as per
> > ,
> > the only packages that would need changes (RC bug + versioned Breaks)
> > would be apt-listchanges and greylistd.
> 
> Also at least ubiquity in Ubuntu.  It ought to be possible to change all
> of the rdepends first so that the impact is minimal.
> 
> > That seems maybe a worthwhile thing to do post-stretch?
> 
> Yep.

OK. This kind of change shouldn't happen in stretch at this point, so tagging
this -ignore.

Cheers,

Ivo

Bug#858171: openscenegraph outdated

[Peter Keel]

Hi

* on the Sun, Mar 19, 2017 at 12:23:42PM +0100, Alberto Luaces Fernández wrote:
> please use the 3.4 package, available in testing:
> 
> https://packages.qa.debian.org/o/openscenegraph-3.4.html

Oh, IC. 

I was looking for newer versions of libopenscenegraph-dev, and 
thus did not notice a newer one with a changed name.

I now made me some packages for openscenegraph 3.5.5 (but of course
they're better when they're directly in debian ;). 

Kind Regards
Peter
-- 
"Those who give up essential liberties for temporary safety deserve 
neither liberty nor safety." -- Benjamin Franklin
"It's also true that those who would give up privacy for security are 
likely to end up with neither." -- Bruce Schneier

Bug#819893: NMU ahead

[Holger Levsen]

Hi,

On Sun, Mar 19, 2017 at 12:47:21PM +, Holger Levsen wrote:
> I've uploaded this to DELAYED-2 just now.

as discussed with Roberto Sanchez on #debian-devel, I've 
made this a 0-day NMU now.
 
> Will then also file a "please acknowledge and include NMU" bug then, unless
> you dont want that, either because you include the change into git already or
> because you've done an upload yourself, which invalidated my NMU.

the debdiff is attched, please add it to git, Roberto.


-- 
cheers,
Holger
diff -Nru cyrus-sasl2-2.1.27~101-g0780600+dfsg/debian/changelog cyrus-sasl2-2.1.27~101-g0780600+dfsg/debian/changelog
--- cyrus-sasl2-2.1.27~101-g0780600+dfsg/debian/changelog	2016-12-31 15:59:34.0 +0100
+++ cyrus-sasl2-2.1.27~101-g0780600+dfsg/debian/changelog	2017-03-19 13:30:33.0 +0100
@@ -1,3 +1,15 @@
+cyrus-sasl2 (2.1.27~101-g0780600+dfsg-3) unstable; urgency=medium
+
+  [ Holger Levsen ]
+  * NMU to help with #856847.
+
+  [ Andreas Beckmann ]
+  * libsasl2-modules.postinst: Remove executable permissions from
+/etc/logcheck/ignore.d.server/libsasl2-modules on upgrades from jessie.
+(Closes: #819893)
+
+ -- Holger Levsen   Sun, 19 Mar 2017 12:30:33 +
+
 cyrus-sasl2 (2.1.27~101-g0780600+dfsg-2) unstable; urgency=medium
 
   * Reinstate Heimdal Kerberos support (Closes: #849706)
diff -Nru cyrus-sasl2-2.1.27~101-g0780600+dfsg/debian/libsasl2-modules.postinst cyrus-sasl2-2.1.27~101-g0780600+dfsg/debian/libsasl2-modules.postinst
--- cyrus-sasl2-2.1.27~101-g0780600+dfsg/debian/libsasl2-modules.postinst	1970-01-01 01:00:00.0 +0100
+++ cyrus-sasl2-2.1.27~101-g0780600+dfsg/debian/libsasl2-modules.postinst	2017-03-19 13:30:30.0 +0100
@@ -0,0 +1,13 @@
+#!/bin/sh
+set -e
+
+if [ "$1" = "configure" ]; then
+	if dpkg --compare-versions "$2" lt-nl "2.1.27~101-g0780600+dfsg-3~" ; then
+		# fix permissions 0755 -> 0644 upon upgrades from jessie
+		if [ -f /etc/logcheck/ignore.d.server/libsasl2-modules ]; then
+			chmod a-x /etc/logcheck/ignore.d.server/libsasl2-modules
+		fi
+	fi
+fi
+
+#DEBHELPER#


signature.asc
Description: Digital signature

Bug#858179: scan-view-4.0 fails to start due to missing Python module

[Paul Menzel]

Package: clang-4.0
Version: 1:4.0-1
Severity: normal

Dear Maintainer,


Running `scan-build-4.0`, and then `scan-view-4.0` it fails to start
with the error below.

```
$ scan-view-4.0 /tmp/scan-build-2017-03-19-141107-6557-1
Traceback (most recent call last):
  File "/usr/bin/scan-view-4.0", line 144, in 
main()
  File "/usr/bin/scan-view-4.0", line 141, in main
run(port, args, args.root)
  File "/usr/bin/scan-view-4.0", line 71, in run
import ScanView
ImportError: No module named ScanView
Unhandled exception in thread started by 
sys.excepthook is missing
lost sys.stderr
```


Thanks,

Paul

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

Kernel: Linux 4.10.0-trunk-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages clang-4.0 depends on:
ii  binutils 2.28-2
ii  libc62.24-9
ii  libc6-dev2.24-9
ii  libclang-common-4.0-dev  1:4.0-1
ii  libclang1-4.01:4.0-1
ii  libgcc-6-dev 6.3.0-9
ii  libgcc1  1:6.3.0-9
ii  libjsoncpp1  1.7.4-3
ii  libllvm4.0   1:4.0-1
ii  libobjc-6-dev6.3.0-9
ii  libstdc++-6-dev  6.3.0-9
ii  libstdc++6   6.3.0-9

Versions of packages clang-4.0 recommends:
ii  llvm-4.0-dev  1:4.0-1
ii  python2.7.13-2

Versions of packages clang-4.0 suggests:
pn  clang-4.0-doc  
pn  gnustep
pn  gnustep-devel  

-- no debconf information

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

Bug#818787: doxygen: Changes default HAVE_DOT to YES without having graphviz in the Depends line.

[Ivo De Decker]

Control: severity -1 important

Hi,

On Wed, Mar 23, 2016 at 04:50:34PM +0100, Matthias Klose wrote:
> On 22.03.2016 17:12, Santiago Vila wrote:
> >Dear Matthias:
> >
> >If the default HAVE_DOT is changed to "no", it is relatively easy to
> >check which packages would need to add "graphviz" to their build-depends.
> >(See the thread in -devel about this).
> >
> >In other words: If you think that's the right fix (I do), don't worry
> >about the additional bugs that will have to be reported as a
> >consequence.
> 
> I think, these packages should explicitly build-depend on graphviz.  You
> didn't find that many.

OK. Downgrading based on the input of the maintainer.

Cheers,

Ivo

Bug#858095: atlc FTBFS on mips: Build killed with signal TERM after 360 minutes of inactivity

[Bdale Garbee]

Adrian Bunk  writes:

> Now one test is taking over 6 hours (is that completely hanging?).

I have no idea.  Never seen that happen.  Makes me wonder what's changed
in your kernel or toolchain since the last build?

Bdale



signature.asc
Description: PGP signature

Bug#819893: NMU ahead

[Holger Levsen]

On Sun, Mar 19, 2017 at 12:47:21PM +, Holger Levsen wrote:
> > filing an unblock request to get the fix into stretch.
> Will do once the package hits sid.

the package has been unblocked already, thanks to the awesome release team and
specifically Ivo here! 


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#855535: python-numpy: More info

[Nicolas Patrois]

Package: python-numpy
Followup-For: Bug #855535

Dear Maintainer,

More information about the bug I still have in my machine. I asked help in the 
mailing list and somewhere else.
I also reinstalled the dependencies and some libraries.
In fact, there is something with io.py.
Importing io then numpy works but importing numpy then io fails for both. I 
suspect a namespace bug but editing io.py (moving back _io to io) kept the bug.

In the Python 2.7 console, this is OK:
Python 2.7.13 (default, Jan 19 2017, 14:48:08) 
[GCC 6.3.0 20170118] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import io
>>> import numpy

But this crashes:
Python 2.7.13 (default, Jan 19 2017, 14:48:08) 
[GCC 6.3.0 20170118] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/numpy/__init__.py", line 142, in 

from . import add_newdocs
  File "/usr/lib/python2.7/dist-packages/numpy/add_newdocs.py", line 13, in 

from numpy.lib import add_newdoc
  File "/usr/lib/python2.7/dist-packages/numpy/lib/__init__.py", line 8, in 

from .type_check import *
  File "/usr/lib/python2.7/dist-packages/numpy/lib/type_check.py", line 11, in 

import numpy.core.numeric as _nx
  File "/usr/lib/python2.7/dist-packages/numpy/core/__init__.py", line 72, in 

from numpy.testing.nosetester import _numpy_tester
  File "/usr/lib/python2.7/dist-packages/numpy/testing/__init__.py", line 12, 
in 
from . import decorators as dec
  File "/usr/lib/python2.7/dist-packages/numpy/testing/decorators.py", line 20, 
in 
from .utils import SkipTest, assert_warns
  File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 15, in 

from tempfile import mkdtemp, mkstemp
  File "/usr/lib/python2.7/tempfile.py", line 32, in 
import io as _io
  File "/usr/lib/python2.7/dist-packages/io.py", line 331, in 
def bget(imfile,shp=None,unpackstr=N.int16,bytesperpixel=2.0,sliceinit=0):
AttributeError: 'module' object has no attribute 'int16'
>>> import io
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/io.py", line 72, in 
import numpy as N
  File "/usr/lib/python2.7/dist-packages/numpy/__init__.py", line 142, in 

from . import add_newdocs
  File "/usr/lib/python2.7/dist-packages/numpy/add_newdocs.py", line 13, in 

from numpy.lib import add_newdoc
  File "/usr/lib/python2.7/dist-packages/numpy/lib/__init__.py", line 8, in 

from .type_check import *
  File "/usr/lib/python2.7/dist-packages/numpy/lib/type_check.py", line 11, in 

import numpy.core.numeric as _nx
  File "/usr/lib/python2.7/dist-packages/numpy/core/__init__.py", line 24, in 

raise ImportError(msg)
ImportError: 
Importing the multiarray numpy extension module failed.  Most
likely you are trying to import a failed build of numpy.
If you're working with a numpy git repo, try `git clean -xdf` (removes all
files not under version control).  Otherwise reinstall numpy.

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

Kernel: Linux 3.16.0-4-686-pae (SMP w/3 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 python-numpy depends on:
ii  libatlas3-base [liblapack.so.3]3.10.3-1+b1
ii  libblas3 [libblas.so.3]3.7.0-1
ii  libc6  2.24-9
ii  liblapack3 [liblapack.so.3]3.7.0-1
ii  libopenblas-base [liblapack.so.3]  0.2.19-2
ii  python 2.7.13-2
pn  python2.7:any  
pn  python:any 

python-numpy recommends no packages.

Versions of packages python-numpy suggests:
ii  gcc   4:6.3.0-2
ii  gfortran  4:6.3.0-2
ii  python-dev2.7.13-2
ii  python-nose   1.3.7-2
pn  python-numpy-dbg  
pn  python-numpy-doc  

-- no debconf information

Bug#857531: spambayes: broken symlink: /usr/bin/sb_notesfilter.py -> /usr/bin/sb_notesfilter

[Marcio de Souza Oliveira]

control: tags -1 +pending

Bug#857531: spambayes: broken symlink: /usr/bin/sb_notesfilter.py -> /usr/bin/sb_notesfilter

[Marcio de Souza Oliveira]

Hi,

I did make a NMU and Giovanni sponsored upload to 5-day/delay queue.

Feel free to cancel this upload if needed.

The debian/changelog is:

  * Non-maintainer upload.
  * debian/spambayes.postinst:
  - Removed the sb_notesfilter to avoid create broken symlink.
(closes: #857531)

I attached a debdiff.

Cheers,

Marcio Souza


diff -Nru spambayes-1.1b1/debian/changelog spambayes-1.1b1/debian/changelog
--- spambayes-1.1b1/debian/changelog2014-06-13 09:07:33.0 +
+++ spambayes-1.1b1/debian/changelog2017-03-18 16:59:15.0 +
@@ -1,3 +1,12 @@
+spambayes (1.1b1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/spambayes.postinst:
+  - Removed the sb_notesfilter to avoid create broken symlink.
+(closes: #857531)
+
+ -- Marcio de Souza Oliveira   Sat, 18 Mar 2017 
16:59:15 +
+
 spambayes (1.1b1-1) unstable; urgency=low
 
   [ Jakub Wilk ]
diff -Nru spambayes-1.1b1/debian/spambayes.postinst 
spambayes-1.1b1/debian/spambayes.postinst
--- spambayes-1.1b1/debian/spambayes.postinst   2014-06-13 09:07:33.0 
+
+++ spambayes-1.1b1/debian/spambayes.postinst   2017-03-18 16:59:15.0 
+
@@ -6,7 +6,7 @@
 SCRIPTS="sb_xmlrpcserver sb_server sb_bnfilter sb_mailsort \
 sb_unheader sb_client sb_filter sb_mboxtrain sb_bnserver \
 sb_chkopts sb_upload sb_dbexpimp sb_imapfilter \
-sb_notesfilter sb_evoscore"
+sb_evoscore"
 
 
 if [ "$1" = configure ] ; then


signature.asc
Description: OpenPGP digital signature

Bug#858180: unblock: diaspora-installer/0.6.3.0+debian2

[Pirate Praveen]

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

Please unblock package diaspora-installer

This fixes RC bug #856720

migrate-to-0.6.3.0.sh is just used as a note, its not used anywhere and
its not installed.

unblock diaspora-installer/0.6.3.0+debian2

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ml_IN.UTF-8, LC_CTYPE=ml_IN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru diaspora-installer-0.6.3.0+debian1/debian/changelog 
diaspora-installer-0.6.3.0+debian2/debian/changelog
--- diaspora-installer-0.6.3.0+debian1/debian/changelog 2017-01-26 
04:39:32.0 +0530
+++ diaspora-installer-0.6.3.0+debian2/debian/changelog 2017-03-17 
11:43:04.0 +0530
@@ -1,3 +1,12 @@
+diaspora-installer (0.6.3.0+debian2) unstable; urgency=medium
+
+  * Change section to net (Closes: #832219)
+  * Crete public/source.tar.gz only if the file is missing
+  * Fix diaspora backup logic for updates (to remove files removed upstream)
+(Closes: #856720)
+
+ -- Pirate Praveen   Fri, 17 Mar 2017 11:43:04 +0530
+
 diaspora-installer (0.6.3.0+debian1) unstable; urgency=medium
 
   * Install 0.6.3.0 version
diff -Nru diaspora-installer-0.6.3.0+debian1/debian/control 
diaspora-installer-0.6.3.0+debian2/debian/control
--- diaspora-installer-0.6.3.0+debian1/debian/control   2017-01-26 
04:39:32.0 +0530
+++ diaspora-installer-0.6.3.0+debian2/debian/control   2017-03-15 
10:12:32.0 +0530
@@ -1,5 +1,5 @@
 Source: diaspora-installer
-Section: ruby
+Section: net
 Priority: optional
 Maintainer: Debian Ruby Extras Maintainers 

 Uploaders: Pirate Praveen 
@@ -15,7 +15,7 @@
 
 Package: diaspora-installer
 Architecture: all
-Section: contrib/ruby
+Section: contrib/net
 XB-Ruby-Versions: ${ruby:Versions}
 Depends: build-essential,
  diaspora-common (= ${source:Version}),
diff -Nru diaspora-installer-0.6.3.0+debian1/debian/postinst 
diaspora-installer-0.6.3.0+debian2/debian/postinst
--- diaspora-installer-0.6.3.0+debian1/debian/postinst  2017-01-26 
04:39:32.0 +0530
+++ diaspora-installer-0.6.3.0+debian2/debian/postinst  2017-03-17 
11:12:41.0 +0530
@@ -56,8 +56,9 @@
 
echo "Precompiling assets..."
su diaspora -s /bin/sh -c 'bundle exec rake tmp:cache:clear 
assets:precompile'
+# preinst creates backup (to be able to remove files removed upstream)
 echo "Remove backup..."
-rm -rf ${diaspora_home}-backup.*
+rm -rf ${diaspora_home}/.backup.*
 
 # Starting diaspora
 service diaspora start
diff -Nru diaspora-installer-0.6.3.0+debian1/debian/preinst 
diaspora-installer-0.6.3.0+debian2/debian/preinst
--- diaspora-installer-0.6.3.0+debian1/debian/preinst   2017-01-26 
04:39:32.0 +0530
+++ diaspora-installer-0.6.3.0+debian2/debian/preinst   2017-03-17 
11:12:41.0 +0530
@@ -2,6 +2,7 @@
 set -e
 
 diaspora_home=/usr/share/diaspora
+diaspora_symlinks_list="Gemfile.lock log tmp app/assets bin/bundle 
vendor/bundle db/schema.rb config/database.yml config/diaspora/yml"
 
 # Fix bin symlink set by earlier versions
 if test -L ${diaspora_home}/bin
@@ -10,20 +11,21 @@
 fi
 
 # Backup the previous version
-# Just keep the config and vendor/bundle
+# Just keep the modified files/directories
+# We need this to remove files removed upstream
 backup() {
-cp -r ${diaspora_home}/config ${diaspora_home}-config
-cp -r ${diaspora_home}/vendor/bundle ${diaspora_home}-vendor-bundle
-cp -r ${diaspora_home}/.bundle ${diaspora_home}.bundle
 backup_suffix=$(openssl rand -hex 4)
-mv ${diaspora_home} ${diaspora_home}-backup.${backup-suffix}
-mkdir ${diaspora_home}
-mkdir ${diaspora_home}/vendor
-mv ${diaspora_home}-config ${diaspora_home}/config
-mv ${diaspora_home}-vendor-bundle ${diaspora_home}/vendor/bundle
-mv ${diaspora_home}.bundle ${diaspora_home}/.bundle
-mv ${diaspora_home}-backup.${backup-suffix}/public ${diaspora_home}/public
-   
+backup_dir=${diaspora_home}/.backup.${backup_suffix}
+mkdir  ${backup_dir}
+mv ${diaspora_home}/* ${backup_dir}
+
+for i in vendor,app,bin,db,config; do
+  mkdir ${diaspora_home}/$i
+done
+
+for i in ${diaspora_symlinks_list}; do
+  mv ${backup_dir}/$i ${diaspora_home}/$i
+done
 }
  
 case "$1" in
diff -Nru diaspora-installer-0.6.3.0+debian1/diaspora-download.sh 
diaspora-installer-0.6.3.0+debian2/diaspora-download.sh
--- diaspora-installer-0.6.3.0+debian1/diaspora-download.sh 2017-01-26 
04:39:32.0 +0530
+++ diaspora-installer-0.6.3.0+debian2/diaspora-download.sh 2017-03-17 
11:00:01.0 +0530
@@ -33,7 +33,7 @@
 
 echo "diaspora archive to copy: ${diaspora_archive}"
 
-rsync -a ${diaspora_cache}/${diaspora_arc

Bug#834204: libsdl1.2: Nonfree file: src/video/fbcon/riva_mmio.h

[Ivo De Decker]

Control: tags -1 stretch-ignore

Hi,

On Sat, Aug 13, 2016 at 10:50:03AM +0100, Manuel A. Fernandez Montecelo wrote:
> > The file src/video/fbcon/riva_mmio.h has a nonfree license that does not
> > explicitly allow modification.
> 
> Thanks for the report.
> 
> I am copying FTP-masters to know their opinion.
> 
> This file has been present in Debian for the best part of 2 decades,
> so possibly the people who reviewed and approved this initially are
> not around anymore or, if they are, that they don't recall the details
> if they were discussed.
> 
> From my understanding, despite the brevity of the wording but given
> the context, with "using this code in individual and commercial
> software" is implicit the possibility of modification, as in "use in
> any way you wish" -- modifications might be needed due to changes in
> compiler/toolchain or to integrate in the bigger "commercial" software
> (e.g. changing names to avoid clashes).
> 
> These licenses are usually to prevent that the source code is
> leaked/accessible to the outside world, or used in commercial software
> without being paid.  Since this license prevents neither, I don't
> think that prevent modification is of any use to the copyright
> holders...
> 
>  but it's true that it doesn't explicitly allow modification or
> says anything beyond "use".
> 
> 
> > The file is from xf86-video-nv, and has
> > subsequently been relicensed under the MIT/Expat license:
> > https://cgit.freedesktop.org/xorg/driver/xf86-video-nv/tree/src/riva_hw.h
> >
> > It should be possible to use the newer version of the file.
> 
> The code is not identical, for example the "NV_" macros in the
> beginning of the old file are not present in the second.
> 
> The "struct _riva_hw_inst" is different in both versions as well (e.g.
> fields Architecture and Version present in the first file, but not in
> the second), so not API nor ABI compatible.
> 
> So it needs to be handled with some care in any case.

Based on the fact that the license for the newer version of the file is OK,
and that we shipped the old version for a long time, I think it's better to
leave it the way it is for stretch, to avoid breaking things this late in the
freeze. Tagging accordingly. This issue should be fixed after the stretch
release.

Cheers,

Ivo

Bug#858181: Package: installation-reports

[Andrew M.A. Cater]

Package: installation-reports

Boot method:  PXE boot
Image version: 
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/netboot/netboot.tar.gz
Date: 201703182350

lsb-release
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20170318-00:06"
X_INSTALLATION_MEDIUM=netboot

Machine: Acer Revo M1-601 - 32G flash disk, 8G memory [Upgraded from initial 2G]
Partitions: 

Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs   4036584   0   4036584   0% /dev
tmpfs  tmpfs   8096369096800540   2% /run
/dev/mmcblk0p1 ext4  21753000 1299184  19325780   7% /
tmpfs  tmpfs  4048180   0   4048180   0% /dev/shm
tmpfs  tmpfs 5120   0  5120   0% /run/lock
tmpfs  tmpfs  4048180   0   4048180   0% /sys/fs/cgroup
tmpfs  tmpfs   809636   0809636   0% /run/user/0
tmpfs  tmpfs   809636   0809636   0% /run/user/1000

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

This is a problematic machine. It requires to be booted in Legacy - MBR - mode.
It requires the kernel arguments noapic and edd=off or it fails.
Most reports of this under Linux are where people have given up in disgust 
after tryning to install Ubuntu.

Would not complete install with Stretch RC2 netboot.tar.gz as the kernel 
versions are now different hence the download of
the newer netboot.tar.gz - from the dailies

This was also tried under UEFI - the UEFI install does not recognise the 
EMMC/SD flash disk type so the install fails.




uname -a: Linux acer 4.9.0-2-amd64 #1 SMP Debian 4.9.13-1 (2017-02-27) x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 
21)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:1073]
lspci -knn: Kernel driver in use: iosf_mbi_pci
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics 
Controller [8086:22b1] (rev 21)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:1073]
lspci -knn: 00:0b.0 Signal processing controller [1180]: Intel Corporation 
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management 
Controller [8086:22dc] (rev 21)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:1073]
lspci -knn: 00:10.0 SD Host controller [0805]: Intel Corporation 
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series MMC Controller 
[8086:2294] (rev 21)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:1073]
lspci -knn: Kernel driver in use: sdhci-pci
lspci -knn: Kernel modules: sdhci_pci
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller 
[8086:22b5] (rev 21)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:1073]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:1a.0 Encryption controller [1080]: Intel Corporation 
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution 
Engine [8086:2298] (rev 21)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:1073]
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller 
[8086:2284] (rev 21)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:1073]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 [8086:22c8] (rev 21)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #2 [8086:22ca] (rev 21)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 [8086:22cc] (rev 21)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #4 [8086:22ce] (rev 21)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Atom/Celeron/P

Bug#857991: [Pkg-javascript-devel] Bug#857991: npm2deb: Please Recommend npm instead of Depend

[Pirate Praveen]

On വെള്ളി 17 മാര്‍ച്ച് 2017 11:01 വൈകു, Jérémy Lal wrote:
> I perfectly understand the idea of keeping it - i don't intend to
> remove it from unstable, but from testing.
> Since npm2deb users are largely us, debian developers, and we are
> supposed to develop new packages in a testing environment,
> it shouldn't be a problem (should it ?).

I just wrote it as soon as I saw your mail, later I realized you are
planning to remove it only from testing. If it remains in unstable, that
should be enough for this use case.




signature.asc
Description: OpenPGP digital signature

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Sylvestre Ledru]

Le 19/03/2017 à 11:13, Rebecca N. Palmer a écrit :
> Here's the 'version script' solution, now covering libLLVM, libclang,
> liblldb, libLTO, BugpointPasses, LLVMHello and LLVMgold (I suspect
> only the first 2-3 actually have use for it, but all except the first
> are set from the same place).
>
> Warning: this hasn't been tested either, and the
> cmake/modules/AddLLVM.cmake modified here gets shipped in llvm-3.9-dev.
>
Looks great, well done for this great work!
What do you mean by "not tested" ? You did built it right?

S

Bug#848559: zeroinstall-injector: Don't recommend python3-aptdaemon.pkcompat

[Mattia Rizzolo]

On Sun, Mar 19, 2017 at 11:30:03AM +, Thomas Leonard wrote:
> Thanks for the offer. I have now got my replacement key approved (this
> week), and I'm just waiting for the acl at
> https://ftp-master.debian.org/dm.txt to be updated (rt.debian.org
> #5239]).

Wow, what a convoluted process you had...

> Once that's done, I can update the package myself.

keyring maint will definitely not update your DM rights.  In the perfect
world you'd ask to somebody trusting you (like the one granting the DM
rights initially, Arno Töll).
Nonetheless, your case seems pretty simple, with you maintaining a
single package... I've sent the appropriate dak updates.

> I don't have any opinion on whether this fix needs to be in stretch or not.

I believe it would be good if it was, as it prevents `apt autoremove`
(in its default configuration) from removing a removed package.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#858182: unblock: gthumb/3:3.4.4.1-5

[Herbert Parentes Fortes Neto]

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

Please unblock package gthumb

I made two Debian revisions:

 - revision 4:
 * debian/gthumb-data.install:
 - Remove /usr/share/appdata
 * debian/gthumb.install:
 - Add /usr/share/appdata
 (Closes: #857012)

 - revision 5:
 * debian/control:(gthumb package)
 - Remove:
- Replaces gthumb2
 - Add: (because of the previous revision)
- Breaks: gthumb-data (<< 3:3.4.4.1-4~)
- Replaces: gthumb-data (<< 3:3.4.4.1-4~)
   (Closes: #857181)


Please, unblock gthumb/3:3.4.4.1-5



Regards,
Herbert

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru gthumb-3.4.4.1/debian/changelog gthumb-3.4.4.1/debian/changelog
--- gthumb-3.4.4.1/debian/changelog 2016-11-28 09:13:26.0 -0200
+++ gthumb-3.4.4.1/debian/changelog 2017-03-08 15:48:41.0 -0300
@@ -1,3 +1,26 @@
+gthumb (3:3.4.4.1-5) unstable; urgency=medium
+
+  * debian/control:(gthumb package)
+  - Remove:
+  - Replaces gthumb2
+  - Add: (because of the previous revision)
+  - Breaks: gthumb-data (<< 3:3.4.4.1-4~)
+  - Replaces: gthumb-data (<< 3:3.4.4.1-4~)
+  (Closes: #857181)
+  Thanks Jeremy Bicha (previous revision too) and Sebastian Ramacher.
+
+ -- Herbert Parentes Fortes Neto   Wed, 08 Mar 2017 15:48:41 
-0300
+
+gthumb (3:3.4.4.1-4) unstable; urgency=medium
+
+  * debian/gthumb-data.install:
+  - Remove /usr/share/appdata
+  * debian/gthumb.install:
+  - Add /usr/share/appdata
+  (Closes: #857012) 
+
+ -- Herbert Parentes Fortes Neto   Wed, 08 Mar 2017 09:38:35 
-0300
+
 gthumb (3:3.4.4.1-3) unstable; urgency=medium
 
   * debian/control:
diff -Nru gthumb-3.4.4.1/debian/control gthumb-3.4.4.1/debian/control
--- gthumb-3.4.4.1/debian/control   2016-11-28 09:13:26.0 -0200
+++ gthumb-3.4.4.1/debian/control   2017-03-08 15:48:41.0 -0300
@@ -60,7 +60,8 @@
 libgphoto2-port12
 Conflicts: gthumb2
 Provides: gthumb2
-Replaces: gthumb2
+Breaks: gthumb-data (<< 3:3.4.4.1-4~)
+Replaces: gthumb-data (<< 3:3.4.4.1-4~)
 Description: image viewer and browser
  gThumb is an advanced image viewer and browser. It has many useful
  features, such as filesystem browsing, slide show, image catalogs, web
diff -Nru gthumb-3.4.4.1/debian/gthumb-data.install 
gthumb-3.4.4.1/debian/gthumb-data.install
--- gthumb-3.4.4.1/debian/gthumb-data.install   2016-05-30 11:52:14.0 
-0300
+++ gthumb-3.4.4.1/debian/gthumb-data.install   2017-03-08 09:38:35.0 
-0300
@@ -1,5 +1,4 @@
 usr/share/aclocal
-usr/share/appdata
 usr/share/glib-2.0
 usr/share/gthumb
 usr/share/help
diff -Nru gthumb-3.4.4.1/debian/gthumb.install 
gthumb-3.4.4.1/debian/gthumb.install
--- gthumb-3.4.4.1/debian/gthumb.install2016-04-13 14:49:43.0 
-0300
+++ gthumb-3.4.4.1/debian/gthumb.install2017-03-08 09:38:35.0 
-0300
@@ -1,4 +1,5 @@
 usr/bin/*
 usr/lib/*/gthumb/extensions/*.extension
 usr/lib/*/gthumb/extensions/*.so
+usr/share/appdata
 usr/share/applications

Bug#858095: atlc FTBFS on mips: Build killed with signal TERM after 360 minutes of inactivity

[Adrian Bunk]

On Sun, Mar 19, 2017 at 07:28:47AM -0600, Bdale Garbee wrote:
> Adrian Bunk  writes:
> 
> > Now one test is taking over 6 hours (is that completely hanging?).
> 
> I have no idea.  Never seen that happen.  Makes me wonder what's changed
> in your kernel or toolchain since the last build?

Nothing of this is "mine", this is a build failure seen on the
Debian buildds:
  https://buildd.debian.org/status/logs.php?pkg=atlc&arch=mips

The latest successful build was in 2011 using gcc 4.6 on a machine 
running kernel 2.6.32

The failing attempts are with gcc 6 and kernel 3.16

> Bdale

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#858008: [pkg-go] Bug#858008: hugo FTBFS: cannot use &jwalterweatherman.FEEDBACK (type **jwalterweatherman.Feedback) as type logPrinter in field value

[Dr. Tobias Quathamer]

control: tag -1 sid
thanks

Am 17.03.2017 um 10:45 schrieb Adrian Bunk:

Source: hugo
Version: 0.18.1-1
Severity: serious

https://buildd.debian.org/status/package.php?p=hugo&suite=sid

...
github.com/spf13/hugo/livereload
github.com/spf13/hugo/hugofs
github.com/spf13/hugo/helpers
# github.com/spf13/hugo/helpers
src/github.com/spf13/hugo/helpers/general.go:250: cannot use 
&jwalterweatherman.FEEDBACK (type **jwalterweatherman.Feedback) as type 
logPrinter in field value:
**jwalterweatherman.Feedback does not implement logPrinter (missing 
Println method)
dh_auto_build: go install -v -p 4 github.com/spf13/hugo 
github.com/spf13/hugo/bufferpool github.com/spf13/hugo/commands 
github.com/spf13/hugo/create github.com/spf13/hugo/helpers 
github.com/spf13/hugo/hugofs github.com/spf13/hugo/hugolib 
github.com/spf13/hugo/livereload github.com/spf13/hugo/parser 
github.com/spf13/hugo/source github.com/spf13/hugo/target 
github.com/spf13/hugo/tpl github.com/spf13/hugo/transform 
github.com/spf13/hugo/utils github.com/spf13/hugo/watcher returned exit code 2
debian/rules:13: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2


Hi,

thanks for the bug report. However, hugo still builds fine in a stretch 
chroot, this bug only applies to unstable.


It was triggered by the recent upload of a new upstream version of 
golang-github-spf13-jwalterweatherman.


@Anthony, did you have a specific reason to upload the new upstream 
version? The changelog does not mention anything, and we've been in the 
freeze for quite some time already.


If there would be a real release critical bug in hugo, now it could not 
be fixed with a simple upload to unstable, which is very unfortunate.


Regards,
Tobias




signature.asc
Description: OpenPGP digital signature

Bug#858183: binNMU needed for r-bioc- packages broken by R 3.3.3.

[Charles Plessy]

Package: release.debian.org
Severity: grave

Hello everybody,

the update of R to version 3.3.3 unexpectedly breaks some R packages, which
need to be reinstalled from source.  In Debian terms, given how we package R
packages, this can be solved by a binNMU.

A quick look at ci.debian.net shows that a large number of Bioconductor
packages (r-bioc-*) started to fail their tests at the end of February
following the upload of r-base version 3.3.2.20170227-1, which was a release
candidate of 3.3.3.  Some of the failures are direct, and some may be a ripple
effect.

On Bioconductor's support forum 
(https://support.bioconductor.org/p/93695/#93719),
it was suggested to reinstall the packages "BiocGenerics", "S4Vectors",
"IRanges", and "GenomicRanges".  I tried this on my computer (using sbuild 
--make-binNMU)
and their regression tests restarted to pass.  These packages are very central 
in
Bioconductor's dependency graph.

If time remains, how about starting with these four and see if the failures in 
the 
the other packages dissapear ?

nmu r-bioc-biocgenerics_0.20.0-1 . all . -m "Rebuild for R 3.3.3."
nmu r-bioc-s4vectors_0.12.1-2 . ANY . -m "Rebuild for R 3.3.3." 
nmu r-bioc-iranges_2.8.1-1-m . ANY . "Rebuild for R 3.3.3."
nmu r-bioc-genomicranges_1.26.2-1 . ANY -m "Rebuild for R 3.3.3."

Otherwise I can prepare a more extensive list of packages to rebuild.

Cheers,

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan

Bug#857385: jablicator: should it be removed from the archive?

[Mattia Rizzolo]

On Sat, Mar 18, 2017 at 11:29:01PM -0700, Jeff Breidenbach wrote:
> Yes, I concur. I also checked with upstream (myself) and he agrees too.

Ok.
Would you ask for removal or shall I?

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Rebecca N. Palmer]

What do you mean by "not tested" ? You did built it right?

Not as of that message.

I since tried to build the "version script" option: it failed most of 
its tests with

--
Exit Code: 126

Command Output (stderr):
--
E: env var COWDANCER_ILISTFILE not defined
E: cowdancer: Fatal, initialize_functions failed
E: env var COWDANCER_ILISTFILE not defined
E: env var COWDANCER_ILISTFILE not defined
E: env var COWDANCER_ILISTFILE not defined
/bin/bash: 
/home/rnpalmer/Debian/builds/stackbuild/llvm-toolchain-3.9-3.9.1/build-llvm/test/CodeGen/X86/Output/2008-04-09-BranchFolding.ll.script: 
Cannot allocate memory


  Expected Passes: 1550
  Expected Failures  : 141
  Unsupported Tests  : 339
  Unexpected Failures: 15192

(dpkg-buildpackage -us -uc inside cowbuilder --login (*not* --build), 
4GB RAM)


That looks like an environment problem, but as this was my first attempt 
to build LLVM, I don't know for sure.

Bug#858184: unblock: notmuch/0.23.7-2

[David Bremner]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Please unblock package notmuch

We've recently fixed a use-after-free bug upstream.  As this error is
in the library, it does at least potentially impact a large number of
users.  We've not seen any problems in the wild because of it (or
detected a bad memory access with valgrind). On the other hand I think
the fix is low risk, it mimics things we've done before.

diff -Nru notmuch-0.23.7/debian/changelog notmuch-0.23.7/debian/changelog
- --- notmuch-0.23.7/debian/changelog   2017-02-28 20:39:30.0 -0400
+++ notmuch-0.23.7/debian/changelog 2017-03-19 09:38:17.0 -0300
@@ -1,3 +1,9 @@
+notmuch (0.23.7-2) unstable; urgency=medium
+
+  * Cherry pick 06adc276, fix use after free in libnotmuch4
+
+ -- David Bremner   Sun, 19 Mar 2017 09:38:17 -0300
+
 notmuch (0.23.7-1) unstable; urgency=medium
 
   * Move test suite $GNUPGHOME to /tmp to avoid problems with long build paths.
diff -Nru notmuch-0.23.7/debian/patches/0001-debcherry-fixup-patch.patch 
notmuch-0.23.7/debian/patches/0001-debcherry-fixup-patch.patch
- --- notmuch-0.23.7/debian/patches/0001-debcherry-fixup-patch.patch
1969-12-31 20:00:00.0 -0400
+++ notmuch-0.23.7/debian/patches/0001-debcherry-fixup-patch.patch  
2017-03-19 09:38:17.0 -0300
@@ -0,0 +1,27 @@
+From 0fa0d9586e63d44e53aa7cf6cde5d1bd88bdbf35 Mon Sep 17 00:00:00 2001
+From: David Bremner 
+Date: Sun, 19 Mar 2017 09:48:03 -0300
+Subject: [PATCH] debcherry fixup patch
+
+aa0bccba lib/message.cc: fix Coverity finding (use after free)
+- extra changes or conflicts
+---
+ lib/message.cc | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/lib/message.cc b/lib/message.cc
+index 9d3e8071..a91e69e0 100644
+--- a/lib/message.cc
 b/lib/message.cc
+@@ -849,9 +849,9 @@ _notmuch_message_ensure_filename_list (notmuch_message_t 
*message)
+*
+* It would be nice to do the upgrade of the document directly
+* here, but the database is likely open in read-only mode. */
+-  const char *data;
+ 
+-  data = message->doc.get_data ().c_str ();
++  std::string datastr = message->doc.get_data ();
++  const char *data = datastr.c_str ();
+ 
+   if (data == NULL)
+   INTERNAL_ERROR ("message with no filename");
diff -Nru notmuch-0.23.7/debian/patches/series 
notmuch-0.23.7/debian/patches/series
- --- notmuch-0.23.7/debian/patches/series  1969-12-31 20:00:00.0 
-0400
+++ notmuch-0.23.7/debian/patches/series2017-03-19 09:38:17.0 
-0300
@@ -0,0 +1,2 @@
+# exported from git by git-debcherry
+0001-debcherry-fixup-patch.patch


unblock notmuch/0.23.7-2

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

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

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAljOnAsACgkQ8gKXHaSn
niwVVQv9FPjOrf9lA+2gfftBiPBjNRBX6akl01H+WysWsSeMg8rcb3lMPEI4JjIl
QtemhZgRdVbe7wvyE1sBVhJY6Byj4P+0JQsGu+ldWZMGqqIp9/Dc9uLn/B8qpqXE
WLce8TJwV2Kf20bxPGt2S3Var967ZoAR4fccaOpVSs+rPs1njdHMOcvO5zSZJeaR
5ri/33fAunkvrElnS6eO3SzHkdg5onfi8IUGUA7JIWgPD7+RQATGn4pab+mBl4lv
AUlB54sNI/opn6P9JLV1dso2wGIiJEbRuLSx2GIbWH4vhIw9z3PnzMRoQ2iMkNPL
yJETZjfLNj7qFZWPjKIIMRZSu4cDRuZa3E2r9oJEC5eaXYAAnGcgV9nLDKMxALO/
bVcCnx5fKjUoum73Vm+C0tTUeoS+h6xdjlQV24ilQwU3Lc5aC5MoRkC6f4MBAzKX
JU87YRzpPBC7IexPrl/jymN8eUq+9xYT4GE517/QHJaxLSqgmTn0BkE3+JQ7sAIY
YteBO+Ev
=LEXU
-END PGP SIGNATURE-

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

[Guus Sliepen]

On Sun, Mar 12, 2017 at 08:36:19PM +0100, Michael Biebl wrote:

> > The stop job for 'Raise network interfaces' fails to complete when
> > shutting down or rebooting a fresh stretch install when certain
> > conditions are met:
> > 
> >  * ATA-over-Ethernet (aoe) kernel module is loaded, and AOE devices are
> > listed in /dev/etherd
> >  * Interface bridging via brctl is used
> > 
> > If either one of these conditions are not satisfied, reboot or shutdown
> > will proceed without issue.  If both are present, 'Raise network
> > interfaces' will repeatedly try to stop, raising the timeout on
> > occasion, but will never complete.  This means an easy workaround is
> > ensuring the 'aoe' kernel module is removed before shutting down or
> > rebooting, if no aoe disks are in use at that time, but that can't be
> > guaranteed in all situations.
> 
> This looks like something which needs to be looked at by the ifupdown
> maintainter, so reassigning accordingly.

This seems to be an issue with the AoE implementation in the kernel. It
correctly keeps an interface busy when an AoE device is mounted over it,
but it handles the teardown very badly.

I'm not sure how you mount the AoE device, but most likely there is
nothing declaring a relationship between it and the bridge interface. So
systemd will not unmount the device before trying to stop the network.

Ifupdown in turn will call brctl delif. I see that this causes the brctl
command to hang. The kernel will repeatedly log this:

unregister_netdevice: waiting for br0 to become free. Usage count = 1

Meanwhile br0 has disappeared from the output of ifconfig. Also, any
access to the mounted device will also hang (because the slaves of the
bridge are down at this point).

Either you have to ensure that systemd unmounts the device before
bringing down the network, or as a workaround you can tell ifupdown to
keep the bridge interface up at shutdown time, by adding something like
this to /etc/network/interfaces:

no-auto-down br0

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


signature.asc
Description: Digital signature

Bug#857991: [Pkg-javascript-devel] Bug#857991: npm2deb: Please Recommend npm instead of Depend

[Shanavas]

npm2deb depends on npm. It uses npm to retrieve npm module metadata and 
tarballs from npm registry.

On March 17, 2017 8:31:41 PM GMT+03:00, "Jérémy Lal"  wrote:
>2017-03-17 18:07 GMT+01:00 Pirate Praveen :
>>
>>
>> On 2017, മാർച്ച് 17 5:02:25 AM IST, "Jérémy Lal" 
>wrote:
>>>I intend to ask removal of npm from testing.
>>>
>>
>> :( It is currently used to bootstrap circular dependencies too. Would
>it be possible to keep it?
>
>
>I perfectly understand the idea of keeping it - i don't intend to
>remove it from unstable, but from testing.
>Since npm2deb users are largely us, debian developers, and we are
>supposed to develop new packages in a testing environment,
>it shouldn't be a problem (should it ?).
>
>Jérémy
>
>-- 
>Pkg-javascript-devel mailing list
>pkg-javascript-de...@lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Sylvestre Ledru]

Le 19/03/2017 à 15:46, Rebecca N. Palmer a écrit :
>> What do you mean by "not tested" ? You did built it right?
> Not as of that message.
>
> I since tried to build the "version script" option: it failed most of
> its tests with
> -- 
> Exit Code: 126
>
> Command Output (stderr):
> -- 
> E: env var COWDANCER_ILISTFILE not defined
> E: cowdancer: Fatal, initialize_functions failed
> E: env var COWDANCER_ILISTFILE not defined
> E: env var COWDANCER_ILISTFILE not defined
> E: env var COWDANCER_ILISTFILE not defined
> /bin/bash:
> /home/rnpalmer/Debian/builds/stackbuild/llvm-toolchain-3.9-3.9.1/build-llvm/test/CodeGen/X86/Output/2008-04-09-BranchFolding.ll.script:
> Cannot allocate memory 
First time that I see that error
and LLVM should not have any test failing

S

Bug#847571: smartly-lexer NMUed, please merge NMU into git

[Holger Levsen]

Hi Mike,

I've just NMUed smarty-lexer to fix #847571, please merge the attached patch 
into the
GIT repo. (If you want me, I'd be glad to file an NMU bug about this, so you 
dont forget ;-)


-- 
cheers,
Holger
diff -Nru smarty-lexer-3.1.30+dfsg1/debian/changelog smarty-lexer-3.1.30+dfsg1/debian/changelog
--- smarty-lexer-3.1.30+dfsg1/debian/changelog	2016-11-25 18:47:13.0 +
+++ smarty-lexer-3.1.30+dfsg1/debian/changelog	2017-03-19 14:57:26.0 +
@@ -1,3 +1,13 @@
+smarty-lexer (3.1.30+dfsg1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply upstream commits 54c249cf and ccaeeca3 to fix broken lexer breaking
+the template generator. (Closes: #847571)
+Thanks to Mike Gabriel for pointing out the upstream commits and equally
+thanks to Wolfgang Schweer and Tomasz Rybak for confirming the fix works.
+
+ -- Holger Levsen   Sun, 19 Mar 2017 14:57:26 +
+
 smarty-lexer (3.1.30+dfsg1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru smarty-lexer-3.1.30+dfsg1/debian/patches/0001-optimize-lexer-code-for-speed-https-github.com-smart.patch smarty-lexer-3.1.30+dfsg1/debian/patches/0001-optimize-lexer-code-for-speed-https-github.com-smart.patch
--- smarty-lexer-3.1.30+dfsg1/debian/patches/0001-optimize-lexer-code-for-speed-https-github.com-smart.patch	1970-01-01 00:00:00.0 +
+++ smarty-lexer-3.1.30+dfsg1/debian/patches/0001-optimize-lexer-code-for-speed-https-github.com-smart.patch	2017-03-19 14:44:52.0 +
@@ -0,0 +1,32 @@
+From 54c249cf7da0dbf9b3d7581d1b6a9e1da8e73f3f Mon Sep 17 00:00:00 2001
+From: uwetews 
+Date: Mon, 7 Nov 2016 03:01:34 +0100
+Subject: [PATCH] optimize lexer code for speed 
+ https://github.com/smarty-php/smarty/issues/311
+
+---
+ LexerGenerator/Parser.php | 8 ++--
+ 1 file changed, 6 insertions(+), 2 deletions(-)
+
+diff --git a/LexerGenerator/Parser.php b/LexerGenerator/Parser.php
+index dce414b..6728ebe 100644
+--- a/LexerGenerator/Parser.php
 b/LexerGenerator/Parser.php
+@@ -362,8 +362,12 @@ class PHP_LexerGenerator_Parser#line 171 "Parser.php"
+ if (preg_match($this->yy_global_pattern' . $ruleindex . ',' . $this->input . ', $yymatches, null, ' .
+  $this->counter .
+ ')) {
+- $yymatches = array_filter($yymatches);
+- if (empty($yymatches)) {
++if (!isset($yymatches[ 0 ][1])) {
++   $yymatches = preg_grep("/(.|\s)+/", $yymatches);
++} else {
++$yymatches = array_filter($yymatches);
++}
++if (empty($yymatches)) {
+ throw new Exception(\'Error: lexing failed because a rule matched\' .
+ \' an empty string.  Input "\' . substr(' . $this->input . ',
+ ' . $this->counter . ', 5) . \'... state ' . $statename . '\');
+-- 
+2.1.4
+
diff -Nru smarty-lexer-3.1.30+dfsg1/debian/patches/0002-fix-spelleing.patch smarty-lexer-3.1.30+dfsg1/debian/patches/0002-fix-spelleing.patch
--- smarty-lexer-3.1.30+dfsg1/debian/patches/0002-fix-spelleing.patch	1970-01-01 00:00:00.0 +
+++ smarty-lexer-3.1.30+dfsg1/debian/patches/0002-fix-spelleing.patch	2017-03-19 14:44:59.0 +
@@ -0,0 +1,48 @@
+From ccaeeca3051d00953a7d6954b00d944d79fc18ae Mon Sep 17 00:00:00 2001
+From: uwetews 
+Date: Fri, 11 Nov 2016 21:14:28 +0100
+Subject: [PATCH] fix spelleing
+
+---
+ LexerGenerator/Parser.php | 10 +-
+ 1 file changed, 5 insertions(+), 5 deletions(-)
+
+diff --git a/LexerGenerator/Parser.php b/LexerGenerator/Parser.php
+index 6728ebe..b7d01fb 100644
+--- a/LexerGenerator/Parser.php
 b/LexerGenerator/Parser.php
+@@ -350,10 +350,10 @@ class PHP_LexerGenerator_Parser#line 171 "Parser.php"
+ if (!isset($this->yy_global_pattern' . $ruleindex . ')) {
+ $this->yy_global_pattern' . $ruleindex . ' = "' . $pattern . 'isS";
+ }
+-if (!isset($this->dataLenght)) {
+-$this->dataLenght = strlen(' . $this->input . ');
++if (!isset($this->dataLength)) {
++$this->dataLength = strlen(' . $this->input . ');
+ }
+-if (' . $this->counter . ' >=  $this->dataLenght) {
++if (' . $this->counter . ' >=  $this->dataLength) {
+ return false; // end of input
+ }
+ ');
+@@ -388,7 +388,7 @@ class PHP_LexerGenerator_Parser#line 171 "Parser.php"
+ } elseif ($r === false) {
+ ' . $this->counter . ' += strlen(' . $this->value . ');
+ ' . $this->line . ' += substr_count(' . $this->value . ', "\n");
+-if (' . $this->counter . ' >=  $this->dataLenght) {
++if (' . $this->counter . ' >=  $this->dataLength) {
+ return false; // end of input
+ }
+ // skip this token
+@@ -437,7 +437,7 @@ class PHP_LexerGenerator_Par

Bug#858185: nmu: slepc_3.7.3+dfsg1-5

[Drew Parsons]

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

petsc 3.7.5 is now built on kfreebsd. slepc should be rebuilt to match.

nmu slepc_3.7.3+dfsg1-5 . kfreebsd-amd64 kfreebsd-i386 . unstable . -m "Build 
against PETSc 3.7.5."

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

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Rebecca N. Palmer]

Looks like this is a known cowdancer issue (#640684 - fixed only for 
cowbuilder --build, not --login); continuing with LD_PRELOAD= 
debian/rules build, the LLVM tests pass:


  Expected Passes: 16742
  Expected Failures  : 124
  Unsupported Tests  : 339
  Unexpected Passes  : 17

Still building the clang tests...

Bug#857679: reopen #761909: system fails to shutdown if there is a mounted nfs share, due to it not being unmounted before network is brought down

[Guus Sliepen]

On Mon, Mar 13, 2017 at 10:00:04PM +0100, Giuseppe Bilotta wrote:

> I am still affected by issue #761909. Essentially, if there is a mounted nfs
> share, shutdown will stall forever trying to unmount it unsuccessfully due to
> the network going down before the attempted unmounting of the share. This only
> happens with systemd.

Hm, on a fresh stretch install here systemd does seem to stop NFS mounts
before stopping the network.

Could you send me a full copy of your /etc/fstab and
/etc/network/interfaces?

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


signature.asc
Description: Digital signature

Bug#858186: unblock: libpfm4/4.8.0-2

[Andreas Beckmann]

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

Please unblock package libpfm4

It contains a few patches cherry picked from upstream fixing/improving
event definitions to better support newer CPUs.

unblock libpfm4/4.8.0-2

Andreas
diff -Nru libpfm4-4.8.0/debian/changelog libpfm4-4.8.0/debian/changelog
--- libpfm4-4.8.0/debian/changelog	2016-11-07 15:46:31.0 +0100
+++ libpfm4-4.8.0/debian/changelog	2017-03-11 02:47:54.0 +0100
@@ -1,3 +1,13 @@
+libpfm4 (4.8.0-2) unstable; urgency=medium
+
+  [ Andreas Beckmann ]
+  * Cherry-pick event fixes, event additions and RAPL support for newer CPUs.
+
+  [ Dimitri John Ledkov ]
+  * Execute validation tests at build time. LP: #1521969
+
+ -- Andreas Beckmann   Sat, 11 Mar 2017 02:47:54 +0100
+
 libpfm4 (4.8.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru libpfm4-4.8.0/debian/patches/0001-Fix-offcore_response-for-Intel-BDW-EP.patch libpfm4-4.8.0/debian/patches/0001-Fix-offcore_response-for-Intel-BDW-EP.patch
--- libpfm4-4.8.0/debian/patches/0001-Fix-offcore_response-for-Intel-BDW-EP.patch	1970-01-01 01:00:00.0 +0100
+++ libpfm4-4.8.0/debian/patches/0001-Fix-offcore_response-for-Intel-BDW-EP.patch	2017-03-11 02:47:54.0 +0100
@@ -0,0 +1,102 @@
+From 05edb2f56598752e14071009c3c52cb22ae6036b Mon Sep 17 00:00:00 2001
+From: Stephane Eranian 
+Date: Sun, 5 Feb 2017 00:35:24 -0800
+Subject: [PATCH 1/3] Fix offcore_response for Intel BDW-EP
+
+The umasks was missing all the L3_HIT umasks because
+they wer all marked as Broadwell (client) only.
+
+Signed-off-by: Stephane Eranian 
+---
+ lib/events/intel_bdw_events.h | 12 
+ 1 file changed, 12 deletions(-)
+
+diff --git a/lib/events/intel_bdw_events.h b/lib/events/intel_bdw_events.h
+index fba5ad2..ba5d1f7 100644
+--- a/lib/events/intel_bdw_events.h
 b/lib/events/intel_bdw_events.h
+@@ -1746,81 +1746,69 @@ static const intel_x86_umask_t bdw_offcore_response[]={
+{ .uname  = "L3_HITM",
+  .udesc  = "Supplier: counts L3 hits in M-state (initial lookup)",
+  .ucode = 1ULL << (18+8),
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid = 1,
+},
+{ .uname  = "LLC_HITM",
+  .udesc  = "Supplier: counts L3 hits in M-state (initial lookup)",
+  .ucode = 1ULL << (18+8),
+  .uequiv = "L3_HITM",
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid = 1,
+},
+{ .uname  = "L3_HITE",
+  .udesc  = "Supplier: counts L3 hits in E-state",
+  .ucode = 1ULL << (19+8),
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid = 1,
+},
+{ .uname  = "LLC_HITE",
+  .udesc  = "Supplier: counts L3 hits in E-state",
+  .ucode = 1ULL << (19+8),
+  .uequiv = "L3_HITE",
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid = 1,
+},
+{ .uname  = "L3_HITS",
+  .udesc  = "Supplier: counts L3 hits in S-state",
+  .ucode = 1ULL << (20+8),
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid = 1,
+},
+{ .uname  = "LLC_HITS",
+  .udesc  = "Supplier: counts L3 hits in S-state",
+  .ucode = 1ULL << (20+8),
+  .uequiv = "L3_HITS",
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid = 1,
+},
+{ .uname  = "L3_HITF",
+  .udesc  = "Supplier: counts L3 hits in F-state",
+  .ucode = 1ULL << (21+8),
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid = 1,
+},
+{ .uname  = "LLC_HITF",
+  .udesc  = "Supplier: counts L3 hits in F-state",
+  .ucode = 1ULL << (20+8),
+  .uequiv = "L3_HITF",
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid = 1,
+},
+{ .uname  = "L3_HITMESF",
+  .udesc  = "Supplier: counts L3 hits in any state (M, E, S, F)",
+  .ucode  = 0xfULL << (18+8),
+  .uequiv = "L3_HITM:L3_HITE:L3_HITS:L3_HITF",
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid  = 1,
+},
+{ .uname  = "LLC_HITMESF",
+  .udesc  = "Supplier: counts L3 hits in any state (M, E, S, F)",
+  .ucode  = 0xfULL << (18+8),
+  .uequiv = "L3_HITMESF",
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid  = 1,
+},
+{ .uname  = "L3_HIT",
+  .udesc  = "Alias for L3_HITMESF",
+  .ucode  = 0xfULL << (18+8),
+  .uequiv = "L3_HITM:L3_HITE:L3_HITS:L3_HITF",
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid  = 1,
+},
+{ .uname  = "LLC_HIT",
+  .udesc  = "Alias for LLC_HITMESF",
+  .ucode  = 0xfULL << (18+8),
+  .uequiv = "L3_HITM:L3_HITE:L3_HITS:L3_HITF",
+- .umodel = PFM_PMU_INTEL_BDW,
+  .grpid  = 1,
+},
+{ .uname  = "L3_MISS_LOCAL",
+-- 
+2.11.0
+
diff -Nru libpfm4-4.8.0/debian/patches/0002-add-UOPS_DISPATCHED_PORT-event-for-Intel-Skylake.patch libpfm4-4.8.0/debian/patches/0002-add-UOPS_DISPATCHED_PORT-event-for-Intel-Skylake.patch
--- libpfm4-4.8.0/debian/patches/0002-add-UOPS_DISPATCHED_PORT-event-for-Intel-Skylake.patch	1970-01-01 01:00:00.0 +0100
+++ libpfm4-4.8.0/debian/patches/0002-add-UOPS_DISPATCHED_PORT-event-for-Intel-Skylake.patch	2017-03-11 02:47:54.0

Bug#858187: boinc-manager: boincmgr suddenly needs -d /etc/boinc-client

[Russell Coker]

Package: boinc-manager
Version: 7.6.33+dfsg-10
Severity: normal

When configuring a boinc-client on localhost (or tunneled through ssh) boincmgr
stopped working recently.  According to my records (looking at the timestamps
on /etc/boinc-client/global_prefs_override.xml and comparing it to dpkg.log)
it seems that version 7.6.33+dfsg-6 worked correctly and sometime between that
and 7.6.33+dfsg-10 it broke.

I expect "boincmgr -n 127.0.0.1", I don't expect that I should be required to
run "boincmgr -n 127.0.0.1 -d /etc/boinc-client".

boincmgr(1) isn't particularly clear either, "data_dir" meaning configuration
dir is unexpected and confusing (I tried both -e and -d to see which one
worked).  Perhaps an example of the options would be good.

Also boingmgr shouldn't just say "Disconnected" at the bottom of the screen if
it can't manage to connect.  It should give the user some clue as to what went
wrong.  Even when run with "--verbose" it gives nothing to stdout/stderr and
nothing more informative in the GUI display.

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

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

Versions of packages boinc-manager depends on:
ii  boinc-client 7.6.33+dfsg-10
ii  libboinc77.6.33+dfsg-10
ii  libc62.24-9
ii  libgcc1  1:6.3.0-9
ii  libglib2.0-0 2.50.3-1
ii  libgtk2.0-0  2.24.31-2
ii  libnotify4   0.7.7-1+b1
ii  libsqlite3-0 3.16.2-3
ii  libstdc++6   6.3.0-9
ii  libwxbase3.0-0v5 3.0.2+dfsg-3
ii  libwxgtk-webview3.0-0v5  3.0.2+dfsg-3
ii  libwxgtk3.0-0v5  3.0.2+dfsg-3

boinc-manager recommends no packages.

Versions of packages boinc-manager suggests:
ii  libgl1-mesa-glx  13.0.5-1
ii  libxt6   1:1.1.5-1

-- no debconf information

Bug#855951: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

[Michael Biebl]

Am 19.03.2017 um 12:59 schrieb Carsten Leonhardt:
> Michael Biebl  writes:
> 
>> If you are sure it fixes the issue, feel free to upload without delay.
> 
> I've made a dozen test runs of the collection tests on arm64, all
> passed. After double checking the buildd logs, I noticed a different
> failing test on mipsel, I've made 5 complete test runs there without
> failure.

The changes in 0.18.5-3 were supposed to fix #837067, i.e. the test
suite failing to pass on a single CPU machine.

Did you test that as well?

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#858188: new upstream version

[Bartosz Fenski]

Package: syncthing
Version: 0.14.18+dfsg1-1
Severity: wishlist

Dear Maintainer,

The newest upstream version is 0.14.24.
Could you please update Debian package?

regards
Bartosz Fenski

Bug#858191: linssid: missing root privileges to run "iw wlan0 scan"

[Alf]

Package: linssid
Version: 2.9-3
Severity: important
Tags: security

Dear Maintainer,

Just installing linssid in Stretch results in beeing unfunctional.
The installer creates an entry in the Applications-Menu which just is
unable to start linssid.

A (dirty) workaround is to start the application comletely as root from
the command line. However this is a unnecessary security risk as the
whole graphical stuff does not need the root privileges, it is just the
command "iw wlan0 scan" to contol the wifi-device. Running it this way
also spams the home directory of root with its configuration settings
and logging.

To demonstrate how it should work, and as version 2.7-1 under Jessie
does, I downloaded the original package linssid_2.9-1_amd64.deb from
SourceForge, installed the necessary dependencies (libboost-regex1.58
and libicu55) from Debian-snapshots and it works as expected. At start
it requests the root-PW once (popup window) and runs
"sudo iw wlan0 scan" to scan the device.

Of course this requires the user starting linssid, to be member of group
"sudo" and to modify /etc/sudoers to ask the root-PW, i.e like this:
Defaultsenv_reset, targetpw, timestamp_timeout=0

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Rebecca N. Palmer]

12 clang tests "unexpectedly" fail, but they're the same 12 that do so 
in the existing package:

Failing Tests (12):
Clang :: CodeGen/linux-arm-atomic.c
Clang :: Driver/arm-cortex-cpus.c
Clang :: Driver/arm-features.c
Clang :: Driver/arm-ias-Wa.s
Clang :: Driver/arm-mfpu.c
Clang :: Driver/cross-linux.c
Clang :: Driver/mips-as.c
Clang :: Driver/mips-integrated-as.s
Clang :: Preprocessor/arm-acle-6.5.c
Clang :: Preprocessor/arm-target-features.c
Clang :: Sema/builtins.c
Clang :: SemaCXX/warn-memsize-comparison.cpp

  Expected Passes: 9572
  Expected Failures  : 16
  Unsupported Tests  : 40
  Unexpected Failures: 12

The build then fails for symbols mismatch...with what looks like exactly 
the change we *want*:


(last few of many)
+ clang_saveTranslationUnit@LLVM_3.9 1:3.9.1-5local2
+#MISSING: 1:3.9.1-5local2# clang_sortCodeCompletionResults@Base 3.2
+ clang_sortCodeCompletionResults@LLVM_3.9 1:3.9.1-5local2
+#MISSING: 1:3.9.1-5local2# clang_toggleCrashRecovery@Base 3.2
+ clang_toggleCrashRecovery@LLVM_3.9 1:3.9.1-5local2
+#MISSING: 1:3.9.1-5local2# clang_tokenize@Base 3.2
+ clang_tokenize@LLVM_3.9 1:3.9.1-5local2
+#MISSING: 1:3.9.1-5local2# clang_visitChildren@Base 3.2
+ clang_visitChildren@LLVM_3.9 1:3.9.1-5local2
+#MISSING: 1:3.9.1-5local2# clang_visitChildrenWithBlock@Base 3.2
+ clang_visitChildrenWithBlock@LLVM_3.9 1:3.9.1-5local2
dh_makeshlibs: failing due to earlier errors

Bug#854494: execnet: testing/test_gateway.py::TestPopenGateway::test_waitclose_on_remote_killed FAILED/PASSEDSegmentation fault

[Daniel Stender]

In the test builds for reproducible builds, this repeatedly occurs as segfault:


testing/test_gateway.py::TestPopenGateway::test_waitclose_on_remote_killed 
PASSEDSegmentation fault
E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: 
python3.5 -m pytest -v -x -rs testing/
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 returned 
exit code 13


https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/execnet_1.4.1-3.rbuild.log
https://tests.reproducible-builds.org/debian/rbuild/testing/armhf/execnet_1.4.1-3.rbuild.log

DS

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

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Sylvestre Ledru]

Le 19/03/2017 à 17:02, Rebecca N. Palmer a écrit :
> 12 clang tests "unexpectedly" fail, but they're the same 12 that do so
> in the existing package:
> Failing Tests (12):
> Clang :: CodeGen/linux-arm-atomic.c
> Clang :: Driver/arm-cortex-cpus.c
> Clang :: Driver/arm-features.c
> Clang :: Driver/arm-ias-Wa.s
> Clang :: Driver/arm-mfpu.c
> Clang :: Driver/cross-linux.c
> Clang :: Driver/mips-as.c
> Clang :: Driver/mips-integrated-as.s
> Clang :: Preprocessor/arm-acle-6.5.c
> Clang :: Preprocessor/arm-target-features.c
> Clang :: Sema/builtins.c
> Clang :: SemaCXX/warn-memsize-comparison.cpp
>
>   Expected Passes: 9572
>   Expected Failures  : 16
>   Unsupported Tests  : 40
>   Unexpected Failures: 12
>
> The build then fails for symbols mismatch...with what looks like
> exactly the change we *want*:
>
> (last few of many)
> + clang_saveTranslationUnit@LLVM_3.9 1:3.9.1-5local2
> +#MISSING: 1:3.9.1-5local2# clang_sortCodeCompletionResults@Base 3.2
> + clang_sortCodeCompletionResults@LLVM_3.9 1:3.9.1-5local2
> +#MISSING: 1:3.9.1-5local2# clang_toggleCrashRecovery@Base 3.2
> + clang_toggleCrashRecovery@LLVM_3.9 1:3.9.1-5local2
> +#MISSING: 1:3.9.1-5local2# clang_tokenize@Base 3.2
> + clang_tokenize@LLVM_3.9 1:3.9.1-5local2
> +#MISSING: 1:3.9.1-5local2# clang_visitChildren@Base 3.2
> + clang_visitChildren@LLVM_3.9 1:3.9.1-5local2
> +#MISSING: 1:3.9.1-5local2# clang_visitChildrenWithBlock@Base 3.2
> + clang_visitChildrenWithBlock@LLVM_3.9 1:3.9.1-5local2
> dh_makeshlibs: failing due to earlier errors
>
Indeed. Are you going to update the symbol file?

Many thanks again!

S

Bug#858192: fritzing: confusing binary naming

[Premek]

Package: fritzing
Version: 0.9.3b+dfsg-4
Severity: normal

Hi,

the 'fritzing' package provides two executables: /usr/bin/Fritzing and
/usr/bin/fritzing
The second one is the one that most people will IMO intuitively try to run
after installing the package. Unfortunately that is the one that does not work.
It starts the GUI but with a lot of error messages and it is unable to load
some 'parts'.
Running 'Fritzing' command works well.

   * What led up to the situation?
Installed the package for the first time.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I never used it before and didn't study any instructions how to run it.
I tried to run a command of the same name as the package name (as it usually is
in many other cases)

   * What was the outcome of this action?
The app started but in a way that is unusable - cannot load some components etc

   * What outcome did you expect instead?
I expected it to work :)


Thank you and have a nice day

Regards
Premek





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

Kernel: Linux 4.9.0-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 fritzing depends on:
ii  fritzing-data 0.9.3b+dfsg-4
ii  libc6 2.24-9
ii  libgcc1   1:6.3.0-6
ii  libgit2-240.24.5-1
ii  libgl1-mesa-glx [libgl1]  13.0.5-1
ii  libqt5concurrent5 5.7.1+dfsg-3+b1
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5network55.7.1+dfsg-3+b1
ii  libqt5printsupport5   5.7.1+dfsg-3+b1
ii  libqt5serialport5 5.7.1~20161021-2
ii  libqt5sql55.7.1+dfsg-3+b1
ii  libqt5sql5-sqlite 5.7.1+dfsg-3+b1
ii  libqt5svg55.7.1~20161021-2+b2
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqt5xml55.7.1+dfsg-3+b1
ii  libstdc++66.3.0-6
ii  zlib1g1:1.2.8.dfsg-5

fritzing recommends no packages.

Versions of packages fritzing suggests:
ii  fritzing-parts  0.9.3b-1

-- no debconf information

Bug#858168: new upstream version = wishlist

[Adrian Bunk]

Adding Eduard to the Cc - the BTS does not do that.

On Sun, Mar 19, 2017 at 01:05:25PM +, Holger Levsen wrote:
> control: severity -1 wishlist
> thanks
> 
> Eduard,
> 
> if you think that #857562 and #852282 are serious bugs, you need to convince
> the maintainer that this is the case. Failing this, you can try to convince 
> the release team, failing this, you can try the CTTE.

CTTE does not have the power to overrule decisions by DPL delegates,
this would require a GR.

> Filing a "please package new upstream version" bug and making this bug serious
> is *NOT* the right way to do this. Seriously.
> 
> Please also note that the changes with this new upstream version are not
> exactly trivial… (and the patch you attached to this bug only included the
> Debian packaging changes, but not the upstream changes…)
> 
> 
> -- 
> cheers,
>   Holger

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#855951: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

[Carsten Leonhardt]

Hi,

> The changes in 0.18.5-3 were supposed to fix #837067, i.e. the test
> suite failing to pass on a single CPU machine.
>
> Did you test that as well?

I did now, on a virtual single CPU kfreebsd-amd64 machine. 6 test runs,
no failures.

Or is this too modern?

$ sysctl hw | head -n 3
hw.machine: amd64
hw.model: Intel Core i7 9xx (Nehalem Class Core i7)
hw.ncpu: 1


I've never looked at this package before the BSP this weekend, does it
have a history of getting stuck during the tests, like the buildds of
kfreebsd did just now?

 - Carsten

Bug#857808: debian-installer: Garbage on terminal with default TERM setting over serial console

[Samuel Thibault]

Hello,

John Paul Adrian Glaubitz, on mer. 15 mars 2017 12:05:56 +0100, wrote:
> The second issue we are seeing is that the terminal output is garbage
> with the default terminal settings. I have taken some screenshots
> of a serial console connected to a SPARC-T5 machine [3].
> 
> Basically, it works when booting with TERM_TYPE=linux (no colors)
> or TERM=ansi (setting TERM=linux produces garbage as well). It
> does not work when not setting TERM or TERM_TYPE at all or when
> setting TERM to vt102.

Well, what terminal are you actually using on the serial port? Is it
really vt102-compatible? Perhaps we should ship a vt102 terminfo with
less capabilities or even another dumber term entry to be used by
default over serial?

> Both issues did not exist with previous versions of debian-installer,

Yes, they were using fewer features of vt102.

Samuel

Bug#856122: calf-plugins: UI not loaded in ardour (works in the standelone app)

[Klaumi Klingsporn]

Am / On Sun, 19 Mar 2017 13:37:00 +0100
schrieb / wrote Klaumi Klingsporn :

> I can NOT confirm this.
> 
> I just tried calf-reverb with ardour-5.5 from the
> debian-testing-package, with the ardour-5.5-binaries from ardour.org
> and with a self-packaged ardour-4.7 (which I normally use because of
> ardour-bug 0007022 in the 5.x-series), and in all versions of
> ardour the plugin and its GUI just works fine.

O.K., now me too!

I just downloaded Ardour-5.8 and opened the test-session created with
Ardour-5.5. There is a calf-reverb inserted pre-fader in a track,
which I cannot access anymore. It is not shown in the mixer strip
anymore and I cannot recall its GUI, but it *is* inserted and works,
as I can hear! I can also manipulate the automation of the reverb in
the tracks automation bar. When I try to delete all inserts from the
track (I can not select the non-visible reverb itself, but it's the
only insert) nothing happens.

But this only happens with Ardour-5.8! When I reopen the session with
Ardour-5.5 all works as expected: The plugin appears in the
mixer-strip and its GUI as well after a double-click.

So I think it's more an Ardour-bug than a calf-bug and may be related
to the modified version of some libraries the Ardour-builds use: 
http://ardour.org/current_dependencies.html

BTW: At least Ardour-bug 0007022 seems to be fixed in Ardour-5.8!
So, it would be nice to have this version in Debian nevertheless. Who
really needs plugins ;-)

Klaumi


---
Klaus-Michael Klingsporn 
mail: klaumi...@gmx.de
web: www.klaumikli.de

Bug#856845: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

[Michael Biebl]

Hi Holger

Am 19.03.2017 um 12:56 schrieb Holger Levsen:
> As I see it this is because we only tell apt-get to install udev from
> backports but dont tell it to also upgrade systemd to that version, so this
> is probably rather a bug in apt (or maybe piuparts) but not in src:systemd.
> 
> Do you agree?

both systemd and udev need to be upgraded in lockstep:

a/ udev has Breaks/Replaces systemd (<< 224-2)

b/ systemd has a Breaks/Replaces udev (<< 228-5)


Forcing the upgrade of only one of the two will fail.

Regards,
Michael


a/ for moving the .link and *.network files from systemd to udev

b/ later we decided to move the *.network files back from udev to systemd
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808237

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



signature.asc
Description: OpenPGP digital signature

Bug#855951: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

[Michael Biebl]

Am 19.03.2017 um 17:22 schrieb Carsten Leonhardt:
> Hi,
> 
>> The changes in 0.18.5-3 were supposed to fix #837067, i.e. the test
>> suite failing to pass on a single CPU machine.
>>
>> Did you test that as well?
> 
> I did now, on a virtual single CPU kfreebsd-amd64 machine. 6 test runs,
> no failures.
> 
> Or is this too modern?
> 
> $ sysctl hw | head -n 3
> hw.machine: amd64
> hw.model: Intel Core i7 9xx (Nehalem Class Core i7)
> hw.ncpu: 1
> 
> 
> I've never looked at this package before the BSP this weekend, does it
> have a history of getting stuck during the tests, like the buildds of
> kfreebsd did just now?

I've seen collection/delete-sync fail once or twice in the past on
slower architectures.
Building on a single CPU machine was apparently sufficient to make this
particular test fail reliably.

I don't remember seeing the test suite to get stuck completely (as it
apparently did on kfreebsd-* now).

Regards,
Michael


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



signature.asc
Description: OpenPGP digital signature

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Rebecca N. Palmer]

On 19/03/17 16:09, Sylvestre Ledru wrote:

Indeed. Are you going to update the symbol file?


I just deleted the symbols file to get the build to finish (which it 
did, and objdump -T confirmed that libLLVM and libclang had versioned 
symbols), but if you want to keep it, here's the full patch from the 
build log (1:3.9.1-5local2 will obviously be 1:3.9.1-6 in the final 
package):


--- debian/libclang1-3.9.symbols (libclang1-3.9_1:3.9.1-5local2_amd64)
+++ dpkg-gensymbolsd20Wgc   2017-03-19 15:49:47.859944671 +
@@ -1,340 +1,680 @@
 libclang-3.9.so.1 libclang1-3.9 #MINVER#
- clang_BlockCommandComment_getArgText@Base 3.2
- clang_BlockCommandComment_getCommandName@Base 3.2
- clang_BlockCommandComment_getNumArgs@Base 3.2
- clang_BlockCommandComment_getParagraph@Base 3.2
- clang_CXCursorSet_contains@Base 3.2
- clang_CXCursorSet_insert@Base 3.2
- clang_CXIndex_getGlobalOptions@Base 3.2
- clang_CXIndex_setGlobalOptions@Base 3.2
- clang_CXXConstructor_isConvertingConstructor@Base 3.9
- clang_CXXConstructor_isCopyConstructor@Base 3.9
- clang_CXXConstructor_isDefaultConstructor@Base 3.9
- clang_CXXConstructor_isMoveConstructor@Base 3.9
- clang_CXXField_isMutable@Base 3.8
- clang_CXXMethod_isConst@Base 3.4
- clang_CXXMethod_isDefaulted@Base 3.9
- clang_CXXMethod_isPureVirtual@Base 3.4
- clang_CXXMethod_isStatic@Base 3.2
- clang_CXXMethod_isVirtual@Base 3.2
- clang_Comment_getChild@Base 3.2
- clang_Comment_getKind@Base 3.2
- clang_Comment_getNumChildren@Base 3.2
- clang_Comment_isWhitespace@Base 3.2
- clang_CompilationDatabase_dispose@Base 3.2
- clang_CompilationDatabase_fromDirectory@Base 3.2
- clang_CompilationDatabase_getAllCompileCommands@Base 3.4
- clang_CompilationDatabase_getCompileCommands@Base 3.2
- clang_CompileCommand_getArg@Base 3.2
- clang_CompileCommand_getDirectory@Base 3.2
- clang_CompileCommand_getFilename@Base 3.8
- clang_CompileCommand_getMappedSourceContent@Base 3.8
- clang_CompileCommand_getMappedSourcePath@Base 3.8
- clang_CompileCommand_getNumArgs@Base 3.2
- clang_CompileCommands_dispose@Base 3.2
- clang_CompileCommands_getCommand@Base 3.2
- clang_CompileCommands_getSize@Base 3.2
- clang_Cursor_Evaluate@Base 3.9
- clang_Cursor_getArgument@Base 3.2
- clang_Cursor_getBriefCommentText@Base 3.2
- clang_Cursor_getCXXManglings@Base 3.8
- clang_Cursor_getCommentRange@Base 3.2
- clang_Cursor_getMangling@Base 3.6
- clang_Cursor_getModule@Base 3.2
- clang_Cursor_getNumArguments@Base 3.2
- clang_Cursor_getNumTemplateArguments@Base 3.6
- clang_Cursor_getObjCDeclQualifiers@Base 3.4
- clang_Cursor_getObjCPropertyAttributes@Base 3.4
- clang_Cursor_getObjCSelectorIndex@Base 3.2
- clang_Cursor_getOffsetOfField@Base 3.7
- clang_Cursor_getParsedComment@Base 3.2
- clang_Cursor_getRawCommentText@Base 3.2
- clang_Cursor_getReceiverType@Base 3.2
- clang_Cursor_getSpellingNameRange@Base 3.2
- clang_Cursor_getStorageClass@Base 3.6
- clang_Cursor_getTemplateArgumentKind@Base 3.6
- clang_Cursor_getTemplateArgumentType@Base 3.6
- clang_Cursor_getTemplateArgumentUnsignedValue@Base 3.6
- clang_Cursor_getTemplateArgumentValue@Base 3.6
- clang_Cursor_getTranslationUnit@Base 3.2
- clang_Cursor_hasAttrs@Base 3.9
- clang_Cursor_isAnonymous@Base 3.7
- clang_Cursor_isBitField@Base 3.4
- clang_Cursor_isDynamicCall@Base 3.2
- clang_Cursor_isFunctionInlined@Base 3.9
- clang_Cursor_isMacroBuiltin@Base 3.9
- clang_Cursor_isMacroFunctionLike@Base 3.9
- clang_Cursor_isNull@Base 3.2
- clang_Cursor_isObjCOptional@Base 3.4
- clang_Cursor_isVariadic@Base 3.4
- clang_EvalResult_dispose@Base 3.9
- clang_EvalResult_getAsDouble@Base 3.9
- clang_EvalResult_getAsInt@Base 3.9
- clang_EvalResult_getAsStr@Base 3.9
- clang_EvalResult_getKind@Base 3.9
- clang_File_isEqual@Base 3.6
- clang_FullComment_getAsHTML@Base 3.2
- clang_FullComment_getAsXML@Base 3.2
- clang_HTMLStartTagComment_isSelfClosing@Base 3.2
- clang_HTMLStartTag_getAttrName@Base 3.2
- clang_HTMLStartTag_getAttrValue@Base 3.2
- clang_HTMLStartTag_getNumAttrs@Base 3.2
- clang_HTMLTagComment_getAsString@Base 3.2
- clang_HTMLTagComment_getTagName@Base 3.2
- clang_IndexAction_create@Base 3.2
- clang_IndexAction_dispose@Base 3.2
- clang_InlineCommandComment_getArgText@Base 3.2
- clang_InlineCommandComment_getCommandName@Base 3.2
- clang_InlineCommandComment_getNumArgs@Base 3.2
- clang_InlineCommandComment_getRenderKind@Base 3.2
- clang_InlineContentComment_hasTrailingNewline@Base 3.2
- clang_Location_isFromMainFile@Base 3.4
- clang_Location_isInSystemHeader@Base 3.4
- clang_ModuleMapDescriptor_create@Base 3.6
- clang_ModuleMapDescriptor_dispose@Base 3.6
- clang_ModuleMapDescriptor_setFrameworkModuleName@Base 3.6
- clang_ModuleMapDescriptor_setUmbrellaHeader@Base 3.6
- clang_ModuleMapDescriptor_writeToBuffer@Base 3.6
- clang_Module_getASTFile@Base 3.4
- clang_Module_getFullName@Base 3.2
- clang_Module_getName@Base 3.2
- clang_Module_getNumTopLevelHeaders@Base 3.2
- clang_Module_getParent@Base 3.2
- clang_Module_getTopLevelHeader@Base 3.2
- clang_Module_isSystem@Base 3.6
- clang_ParamCom

Bug#858130: jessie-pu: package wget/1.16-1+deb8u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2017-03-18 at 18:44 +0100, Noël Köthe wrote:
> wget 1.16-1+deb8u2 fixes CVE-2017-6508 (no-dsa) with the upstream patch.
> https://security-tracker.debian.org/tracker/CVE-2017-6508

Please go ahead.

Regards,

Adam

Bug#826893: marked as done (piuparts aborts with "RuntimeError: maximum recursion depth exceeded")

[Andreas Beckmann]

On 2017-03-19 17:24, Debian Bug Tracking System wrote:
> so because "unable to sync file '/var/lib/dpkg/tmp.ci//md5sums': Input/output
> error" is most likely a hardware related error and not a piuparts issue.

Or a full filesystem (tmpdir) ?


Andreas

Bug#855951: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

[Carsten Leonhardt]

Michael Biebl  writes:

> I don't remember seeing the test suite to get stuck completely (as it
> apparently did on kfreebsd-* now).

It could well be a general problem of the kfreebsd buildds, as they
regularly get completely stuck during the build of gcc-6 in the last
weeks.

Should I go ahead and request the unblock?

 - Carsten