Bug#881448: python-eventlet fails to install on amd64: SyntaxError: invalid syntax

2017-11-11 Thread Chris Lamb
Hi,

> python-eventlet fails to install on amd64: SyntaxError: invalid syntax

  Sat 11 18:37 < zigo> In Python 2, with what I just uploaded for 
python-eventlet, I have these issues:
  Sat 11 18:37 < zigo> Setting up python-eventlet (0.20.0-1) ...
  Sat 11 18:37 < zigo>   File 
"/usr/lib/python2.7/dist-packages/eventlet/green/http/client.py", line 195
  Sat 11 18:37 < zigo> _is_legal_header_name = 
re.compile(rb'[^:\s][^:\r\n]*\Z').match
  Sat 11 18:37 < zigo>  
  ^
  Sat 11 18:37 < zigo> SyntaxError: invalid syntax
  Sat 11 18:37 < zigo>   File 
"/usr/lib/python2.7/dist-packages/eventlet/green/http/cookiejar.py", line 1269
  Sat 11 18:37 < zigo> yield from deepvalues(obj)
  Sat 11 18:37 < zigo>  ^
  Sat 11 18:37 < zigo> SyntaxError: invalid syntax
  Sat 11 18:37 < zigo> Does anyone know how to patch this?
  Sat 11 18:38 < zigo> It works perfectly in py3...
  Sat 11 18:40 < zigo> Looks like doing b'' for the string of the first issue 
is fixing the issue for py2, and works in py3.
  Sat 11 18:40 < zigo> I'm not sure for the yield though.
  Sat 11 18:44 < wRAR> of course you can't "fix" yield from for Python < 3.5
  Sat 11 18:45 < zigo> Hum... I fix I got it ! :)
  Sat 11 18:46 < wRAR> 
https://github.com/eventlet/eventlet/blob/master/eventlet/green/http/__init__.py#L56
  Sat 11 18:46 < wRAR> you don't need to fix the *code*
  Sat 11 18:47 < zigo> wRAR: I actually do...
  Sat 11 18:48 < wRAR> ok
  Sat 11 18:48 < wRAR> and for the first line do you mean you removed the r 
prefix?
  Sat 11 18:48 < zigo> wRAR: Yes. Is this wrong?
  Sat 11 18:48 < wRAR> do you know what does this prefix mean?
  Sat 11 18:49 < zigo> wRAR: I know what b means, not sure what rb does.
  Sat 11 18:49 < wRAR> I see
  Sat 11 18:49 < zigo> Which is why I'm asking in the channel.
  Sat 11 18:49 < wRAR> 
https://docs.python.org/3/library/stdtypes.html#text-sequence-type-str
  Sat 11 18:50 < wRAR> I guess you never wrote regulare expression code in 
Python?
  Sat 11 18:51 < zigo> Right.
  Sat 11 18:52 < zigo> Oh...
  Sat 11 18:52 < zigo> Indeed, removing r is a bad idea... :P

ie. the maintainer is at least aware of the issue.

Zigo, I just went to provide a patch of my own but I cannot find
the latest packaging corresponding to this version in the Vcs-Git
repository.


Regards,

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



Bug#881472: qtgraphicaleffects-opensource-src FTCBFS: does not pass cross tools to qmake

2017-11-11 Thread Helmut Grohne
Source: qtgraphicaleffects-opensource-src
Version: 5.9.2-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

qtgraphicaleffects-opensource-src fails to cross build from source,
because it does not pass cross tools to qmake. After letting
dh_auto_configure do so, the configure step (but not the build step)
succeeds. Please consider applying the attached patch and closing this
bug when doing so.

Helmut
diff --minimal -Nru qtgraphicaleffects-opensource-src-5.9.2/debian/changelog 
qtgraphicaleffects-opensource-src-5.9.2/debian/changelog
--- qtgraphicaleffects-opensource-src-5.9.2/debian/changelog2017-10-26 
15:38:10.0 +0200
+++ qtgraphicaleffects-opensource-src-5.9.2/debian/changelog2017-11-12 
08:42:04.0 +0100
@@ -1,3 +1,10 @@
+qtgraphicaleffects-opensource-src (5.9.2-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Let dh_auto_configure pass cross tools to qmake. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 12 Nov 2017 08:42:04 +0100
+
 qtgraphicaleffects-opensource-src (5.9.2-2) unstable; urgency=medium
 
   * Upload to unstable.
diff --minimal -Nru qtgraphicaleffects-opensource-src-5.9.2/debian/rules 
qtgraphicaleffects-opensource-src-5.9.2/debian/rules
--- qtgraphicaleffects-opensource-src-5.9.2/debian/rules2017-10-26 
15:38:10.0 +0200
+++ qtgraphicaleffects-opensource-src-5.9.2/debian/rules2017-11-12 
08:42:00.0 +0100
@@ -17,7 +17,7 @@
rm -rfv $(CURDIR)/test_root
 
 override_dh_auto_configure:
-   qmake QT_BUILD_PARTS+=tests
+   dh_auto_configure -- QT_BUILD_PARTS+=tests
 
 override_dh_auto_build-indep:
dh_auto_build -Smakefile -- docs


Bug#794138: reopening 794138

2017-11-11 Thread Helmut Grohne
On Sun, Nov 12, 2017 at 08:05:53AM +0100, Petter Reinholdtsen wrote:
> Hi.  Why was the cross build bug reopened?  Was the fix in 0.59-3.2
> not working?

The patch was not applied. The changelog entry is simply wrong. It still
fails in the very same way. You can try yourself with sbuild --host or
pbuilder --host-arch.

Helmut



Bug#881471: chromium translates tilde to underscore when downloading from packages.debian.org

2017-11-11 Thread Phil Wyett
Package: chromium
Version: 63.0.3239.30-1

Hi all,

Firefox is not affected by the issue laid out below.

All versions of chromium from 9 and above are affected.

Note: Versions of chromium in Debian below 9 have not been tested.

Reproduce...

* Intsall and run chromium.
* Go to...
  https://packages.debian.org/stretch/chromium
  https://packages.debian.org/stretch/firefox-esr
* On right of each page, download the...
  _-~deb9uN.

Should happen...

Download the file and it contain the correct tilde before 'deb9uN'.

Does happen...

File is downloaded with underscore where tilde should be.

Regards

Phil

-- 
*** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

Web: https://kathenas.org

GitLab: https://gitlab.com/kathenas

Twitter: kathenasorg

Instagram: kathenasorg

GPG: 1B97 6556 913F 73F3 9C9B 25C4 2961 D9B6 2017 A57A

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


Bug#661455: ITA: fracplanet -- Fractal planet generator

2017-11-11 Thread Innocent De Marchi
retitle 661455 to ITA: fracplanet -- Fractal planet generator
thanks!



Bug#794138: reopening 794138

2017-11-11 Thread Petter Reinholdtsen
Hi.  Why was the cross build bug reopened?  Was the fix in 0.59-3.2
not working?
-- 
Happy hacking
Petter Reinholdtsen



Bug#747189: startpar: Silence startpar boot messages

2017-11-11 Thread Petter Reinholdtsen
Hi.  Is this change still used and needed on Ubuntu?
-- 
Happy hacking
Petter Reinholdtsen



Bug#875131: qimhangul removal request

2017-11-11 Thread Changwoo Ryu
reassign 875131 ftp.debian.org
title 875131 RM: qimhangul --ROM; unmaintained, QT4 dependent,
replaced by toolkit-independent IMEs
thanks

qimhangul is a Korean input method for Qt. Most users now use
toolkit-independent IMEs like ibus. So it can be safely removed.



Bug#881470: RM: imhangul-common -- ROM; no use after imhangul* removal

2017-11-11 Thread Changwoo Ryu
Package: ftp.debian.org
Severity: normal

This is a support package for imhangul and imhangul3 which are to be removed.



Bug#881469: RM: imhangul3 -- ROM; unmaintained, replaced by toolkit-independent IMEs

2017-11-11 Thread Changwoo Ryu
Package: ftp.debian.org
Severity: normal

It's not maintained in upstream. It is GTK dependent so has limited
features. Most users use toolkit independent IMEs like ibus.



Bug#881468: RM: imhangul -- ROM; unmaintained, replaced by toolkit-independent IMEs

2017-11-11 Thread Changwoo Ryu
Package: ftp.debian.org
Severity: normal

It's not maintained in upstream. It is GTK dependent so has limited
features. Most users use toolkit independent IMEs like ibus.



Bug#881467: git-buildpackage: gbp dch should filter out commits behind upstream-vcs-tag

2017-11-11 Thread Daniel Kahn Gillmor
Package: git-buildpackage
Version: 0.9.1
Severity: wishlist

I use upstream-vcs-tag to include upstream's commits in addition to
the debian packaging commits in debian packaging git history.

This works great for many parts of my workflow, thanks!

However, it causes "gbp dch" to propose incredibly verbose changelogs
when i import new versions from upstream -- the proposed changelog
entry includes all of upstream's commits as well as the debian
packaging.

But, "gbp dch" should be able to tell that upstream-vcs-tag is
available (e.g. debian/gbp.conf) and it could exclude upstream's
changes (maybe replacing them all with "New upstream release") when
generating a new debian/changelog entry.

Does that make sense as a feature request?

 --dkg

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

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

Versions of packages git-buildpackage depends on:
ii  devscripts 2.17.11
ii  git1:2.15.0-1
ii  man-db 2.7.6.1-2
ii  python33.6.3-2
ii  python3-dateutil   2.6.1-1
ii  python3-pkg-resources  36.6.0-1

Versions of packages git-buildpackage recommends:
pn  cowbuilder | pbuilder | sbuild  
ii  pristine-tar1.42
ii  python3-requests2.18.1-1

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
pn  sudo 
ii  unzip6.0-21

-- no debconf information



Bug#881466: ITP: nekojishi -- Interactive visual novel with furries and Taiwanese cultures

2017-11-11 Thread 魏銘廷
Package: wnpp
Severity: wishlist
Owner: Yao Wei (魏銘廷) 

* Package name: nekojishi
  Version : 1.01
  Upstream Author : NekojishiTW 
* URL : https://nekojishi.tw/
* License : Proprietary (Non-commercial)
  Programming Lang: Python
  Description : Interactive visual novel game with furries and Taiwanese 
cultures

=== Detailed descriptions below ===

致家有大貓團隊:我想要將家有大貓 (SFW) 上傳到 Debian 套件庫,其實是個人
私心。身為獸友跟 Debian contributor,我想要找到一個交集點讓我能夠做點什
麼。不過因為 Debian 對授權要求比較嚴格,根據團隊網站,我會建議採納
「創用CC 姓名標示-非商業性」這個授權條款,再加上原住民族智慧創作保護條
例(若有需要),並將授權條款全文放置在遊戲檔案的壓縮檔裡面。若有疑慮,
可以詢問我。

我將會做的事情會包括把原本的 .rpa 檔案透過 unrpa 解壓縮,去除編譯過的檔
案以及不需要的 library (基於 Debian Policy 要求),放進 .deb 裡面,之
後再上傳到 Debian 審核。若審核有通過,將來 Debian 以及包含 Ubuntu 在內
的 Linux 發行版將可以使用 `apt install nekojishi` 下載到家有大貓了。

To Nekojishi team: As a furry fan and Debian contributor, I would like
to find intersection to both of these, and do something together.
However, the license of the game isn't pretty clear.  I would suggest
adopting Creative Commons Attribution-NonCommercial license, amending
with "Indigenous Culture Intellectural Property Protection Act" if
necessary, and put the text file into the .zip archive.  Also, you
probably need to declare if the .zip is distributable.

What I am going to do is to use unrpa to unarchive the files, removing
the unnecessary compiled files, lirbaries and fonts (per Debian Policy
§4.13 Convenience copies of code, we need to strip them and use Debian
provided files).  And upload to Debian for review.  If the review passed
we can download Nekojishi using `apt install nekojishi` in any Debian
and its derivatives including Ubuntu.

===

This is a crowdfunded visual novel game influxing furry culture and
Taiwanese religious and indigenous cultures.  The SFW version is chosen
to package. (and I am wondering if NSFW thing is not a good thing in
Debian.)
The game is free to download, but I am unsure about redistributability.
In this email I am also asking the authors if they can adopt Creative
Commons with non-commercial license (as stated in their website).

If that's a good idea, I would like to maintain the package under Debian
Games Team.

Yao Wei


signature.asc
Description: PGP signature


Bug#881465: /usr/bin/olwmslave: SIGSEGV in font_find_font () from /usr/lib/libxview.so (olwmslave)

2017-11-11 Thread Veek M
Package: olwm
Version: 3.2p1.4-28.2
Severity: normal
File: /usr/bin/olwmslave

Dear Maintainer,

   * What led up to the situation?
dmesg shows
olwmslave[1166]: segfault at e0cdafc0 ip 7f7d3e075910 sp 
7fff1c030a40 
error 5 in libxview.so.3.2.4[7f7d3e01+154000]

additionally running olwmslave segfaults (it's meant to be run via olwm)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Stack trace of thread 1166:
#0  0x7f7d3e075910 font_find_font (libxview.so.3)
#1  0x7f7d3e123efe xv_find_avlist (libxview.so.3)
#2  0x7f7d3e1240a6 xv_find (libxview.so.3)
#3  0x7f7d3e073228 xv_font_with_name (libxview.so.3)
#4  0x7f7d3e11ae36 window_init (libxview.so.3)
#5  0x7f7d3e123be7 xv_create_avlist (libxview.so.3)
#6  0x7f7d3e123e64 xv_create (libxview.so.3)
#7  0x7f7d3e0ccbef screen_init (libxview.so.3)
#8  0x7f7d3e123be7 xv_create_avlist (libxview.so.3)
#9  0x7f7d3e123e64 xv_create (libxview.so.3)
#10 0x7f7d3e0dabd0 server_init (libxview.so.3)
#11 0x7f7d3e123be7 xv_create_avlist (libxview.so.3)
#12 0x7f7d3e123e64 xv_create (libxview.so.3)
#13 0x7f7d3e125901 xv_init (libxview.so.3)
#14 0x55cfe00f5d0c n/a (olwmslave)
#15 0x7f7d3d52f2b1 __libc_start_main (libc.so.6)
#16 0x55cfe00f5fea n/a (olwmslave)


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

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

Versions of packages olwm depends on:
ii  libc6 2.24-11+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  xviewg3.2p1.4-28.2

olwm recommends no packages.

Versions of packages olwm suggests:
pn  menu   
ii  xview-clients  3.2p1.4-28.2

-- no debconf information



Bug#881464: zim: Please don't suggest python-gtksourceview2

2017-11-11 Thread Jeremy Bicha
Package: zim
Version: 0.67-1

python-gtksourceview2 will be removed from Debian Testing soon.
Therefore, please don't Suggest it.

See https://bugs.debian.org/878698

Thanks,
Jeremy Bicha



Bug#881463: eog: menu bar shows in fullscreen

2017-11-11 Thread Jeremy Bicha
Control: forwarded -1 https://launchpad.net/bugs/1672202
Control: fixed -1 3.25.90-1

On Sat, Nov 11, 2017 at 11:04 PM, Neels Hofmeyr  wrote:
> I suspect debian/patches/0001-Add-a-traditional-menu-bar.patch from eog
> (3.19.92-2). It seems the patch adds a menu bar without making provision for
> hiding it in fullscreen or slide show modes.

This was fixed in Debian Testing but it still affects Debian 9
"Stretch". I think you need to be running a desktop that is not GNOME
to be affected by this issue.

By the way, the future of these headerbar patches is being discussed now.

https://community.ubuntu.com/t/removal-of-headerbar-patches-and-impact-on-unity/1456

Thanks,
Jeremy Bicha



Bug#876571: mpage is no longer available on Debian

2017-11-11 Thread Jeremy Bicha
gjots2 also recommends python-gtksourceview2 which will be removed
from Debian Testing soon.

Thanks,
Jeremy Bicha



Bug#881463: eog: menu bar shows in fullscreen

2017-11-11 Thread Neels Hofmeyr
Package: eog
Version: 3.20.5-1+b1
Severity: normal

Dear Maintainer,

eog has always shown just the image in fullscreen mode. After upgrading to the
Debian stable version, I now see a menu bar in fullscreen mode which never goes
away. This is really annoying, as it defies the whole point of fullscreen mode.

I suspect debian/patches/0001-Add-a-traditional-menu-bar.patch from eog
(3.19.92-2). It seems the patch adds a menu bar without making provision for
hiding it in fullscreen or slide show modes.

Please make this menu bar an option that I can switch off in the preferences,
or remove it altogether, or always hide it in fullscreen and slideshow modes
(IMHO it should not have hover-to-appear with delays, just hide completely).

Many Thanks!

~N

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

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

Versions of packages eog depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gir1.2-gtk-3.0   3.22.11-1
ii  gir1.2-peas-1.0  1.20.0-1+b1
ii  gsettings-desktop-schemas3.22.0-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u1
ii  libcairo21.14.8-1
ii  libexempi3   2.4.1-1
ii  libexif120.6.21-2+b2
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u1
ii  libgirepository-1.0-11.50.0-1+b1
ii  libglib2.0-0 2.50.3-2
ii  libgnome-desktop-3-123.22.2-1
ii  libgtk-3-0   3.22.11-1
ii  libjpeg62-turbo  1:1.5.1-2
ii  liblcms2-2   2.8-4
ii  libpeas-1.0-01.20.0-1+b1
ii  librsvg2-2   2.40.16-1+b1
ii  libx11-6 2:1.6.4-3
ii  shared-mime-info 1.8-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages eog recommends:
ii  librsvg2-common  2.40.16-1+b1
ii  yelp 3.22.0-1

Versions of packages eog suggests:
pn  eog-plugins  

-- no debconf information



Bug#881462: knot-resolver: kresd in tight on SIGPIPE when offering TLS or TCP

2017-11-11 Thread Daniel Kahn Gillmor
Package: knot-resolver
Version: 1.3.3-1
Severity: normal
Tags: patch upstream
Control: forwarded -1 https://gitlab.labs.nic.cz/knot/knot-resolver/issues/271

I'm running kresd 1.3.3,  I found it was stuck in a tight loop.  here's the 
output of strace:

```
write(20, 
"\27\3\3\1\356\0\0\0\0\0\0\0\2H\364\352e\235\t\274\237YF\244\260\250K\223q\211EW"...,
 499) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=24582, si_uid=110} ---
write(20, 
"\27\3\3\1\356\0\0\0\0\0\0\0\2H\364\352e\235\t\274\237YF\244\260\250K\223q\211EW"...,
 499) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=24582, si_uid=110} ---
```

looking at the open file descriptors with `lsof`, i see:

```
kresd   24582 knot-resolver   18ur REG   0,35  8192   12524 
/var/cache/knot-resolver/lock.mdb
kresd   24582 knot-resolver   19u  REG   0,35 104857600   12525 
/var/cache/knot-resolver/data.mdb
kresd   24582 knot-resolver   20u sock0,8   0t0 4310946 
protocol: TCPv6
```

If i kill and restart the daemon, it will likely work fine again.


I mentioned this upstream at
https://gitlab.labs.nic.cz/knot/knot-resolver/issues/271, and upstream
suggested the attached patch as a fix.

  --dkg


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

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

Versions of packages knot-resolver depends on:
ii  adduser3.116
ii  dns-root-data  2017072601
ii  libbsd00.8.6-3
ii  libc6  2.24-17
ii  libdnssec4 2.6.0-1
ii  libedit2   3.1-20170329-1
ii  libgnutls303.5.16-1
ii  libhiredis0.13 0.13.3-2
ii  libknot6   2.6.0-1
ii  liblmdb0   0.9.21-1
ii  libluajit-5.1-22.1.0~beta3+dfsg-5.1
ii  libmemcached11 1.0.18-4.2
ii  libmemcachedutil2  1.0.18-4.2
ii  libncurses56.0+20170902-1
ii  libnettle6 3.3-2
ii  libsystemd0235-2
ii  libtinfo5  6.0+20170902-1
ii  libuv1 1.9.1-3
ii  libzscanner1   2.6.0-1
ii  lua-sec0.6-3
ii  lua-socket 3.0~rc1+git+ac3201d-3

Versions of packages knot-resolver recommends:
pn  knot-resolver-module-http  

knot-resolver suggests no packages.

-- no debconf information
Vladimír Čunát commented:

It's been squashed unfortunately.  Let me cut it out:
```diff
diff --git a/daemon/main.c b/daemon/main.c
index 56c2e85a..518a6c2b 100644
--- a/daemon/main.c
+++ b/daemon/main.c
@@ -17,6 +17,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -640,6 +641,14 @@ int main(int argc, char **argv)
}
}
 
+   /* Workaround for https://github.com/libuv/libuv/issues/45
+* (Write after ECONNRESET crash.) */
+   if (signal(SIGPIPE, SIG_IGN) == SIG_ERR) {
+   kr_log_error("[system] can't block SIGPIPE signal: %s\n",
+strerror(errno));
+   ret = EXIT_FAILURE;
+   }
+
if (ret != 0) {
goto cleanup;
}
```

---
View it on GitLab: 
https://gitlab.labs.nic.cz/knot/knot-resolver/issues/271#note_60621
You're receiving this email because of your account on gitlab.labs.nic.cz.


Bug#881461: frei0r-plugins: Breaks frei0r-plugins (<= 1.1.22)

2017-11-11 Thread Kingsley G. Morse Jr.
Package: frei0r-plugins
Version: 1.6.1-1+b1
Severity: minor

Dear Maintainer,

Thanks for maintaining frei0r's plugins.

They look cool.

* What led up to the situation?

I wondered why ffmpeg failed to use frei0r plugins
as ffmpeg sources.

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

I typed

$ apt-cache show frei0r-plugins

and read the "Breaks:" header.

* What was the outcome of this action?

Breaks: frei0r (<= 1.1.22)

* What outcome did you expect instead?

Breaks: frei0r-plugins (<= 1.1.22)


Thanks,
Kingsley

Bonus:  Tell me where to look for documentation on
parameters and syntax for using frei0r effects as
ffmpeg sources.

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

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

Versions of packages frei0r-plugins depends on:
ii  libc62.24-17
ii  libcairo21.14.8-1
ii  libgavl1 1.4.0-3
ii  libgcc1  1:7.2.0-12
ii  libopencv-calib3d3.2 3.2.0+dfsg-3
ii  libopencv-contrib3.2 3.2.0+dfsg-3
ii  libopencv-core3.23.2.0+dfsg-3
ii  libopencv-features2d3.2  3.2.0+dfsg-3
ii  libopencv-flann3.2   3.2.0+dfsg-3
ii  libopencv-highgui3.2 3.2.0+dfsg-3
ii  libopencv-imgcodecs3.2   3.2.0+dfsg-3
ii  libopencv-imgproc3.2 3.2.0+dfsg-3
ii  libopencv-ml3.2  3.2.0+dfsg-3
ii  libopencv-objdetect3.2   3.2.0+dfsg-3
ii  libopencv-photo3.2   3.2.0+dfsg-3
ii  libopencv-shape3.2   3.2.0+dfsg-3
ii  libopencv-stitching3.2   3.2.0+dfsg-3
ii  libopencv-superres3.23.2.0+dfsg-3
ii  libopencv-video3.2   3.2.0+dfsg-3
ii  libopencv-videoio3.2 3.2.0+dfsg-3
ii  libopencv-videostab3.2   3.2.0+dfsg-3
ii  libopencv-viz3.2 3.2.0+dfsg-3
ii  libstdc++6   7.2.0-12

frei0r-plugins recommends no packages.

Versions of packages frei0r-plugins suggests:
pn  opencv-data  

-- no debconf information



Bug#881416: [php-maint] Bug#881416: Please also depend on php7.1-dev

2017-11-11 Thread Ondřej Surý
I'll refresh the versions of PHP 7.0, 7.1 and 7.2 in unstable and start
the transition.

O.
-- 
Ondřej Surý 

On Sat, Nov 11, 2017, at 14:39, Mathieu Parent wrote:
> Package: php-all-dev
> Version: 1:54
> Severity: wishlist
> 
> Hi Ondrej,
> 
> I want to fix #879475, #879476, #879477 by a simple rebuild of those
> packages.
> 
> Maybe a regeneration on debian/control is needed?
> 
> Regards
> 
> Mathieu Parent
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
> LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages php-all-dev depends on:
> ii  php7.0-dev   7.0.22-3
> ii  php7.0-json  7.0.22-3
> 
> php-all-dev recommends no packages.
> 
> php-all-dev suggests no packages.
> 
> ___
> pkg-php-maint mailing list
> pkg-php-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint



Bug#870882: Mention where to send bug reports

2017-11-11 Thread Jeremy Bicha
Please file these bugs upstream since the manpages are shipped as they
come from GNOME.

https://bugzilla.gnome.org/enter_bug.cgi?product=libsecret

Thanks,
Jeremy Bicha



Bug#881460: apparmor-profiles: dhclient set to enforce prevents getting an IPv4 with DHCP

2017-11-11 Thread Gabriel Filion
Package: apparmor-profiles
Version: 2.11.1-3
Severity: critical
Justification: breaks unrelated software

Hello,

I've started using apparmor very recently, and when I rebooted to
activate the kernel part, I didn't notice the issue below.. but a couple
reboots afterwards I couldn't obtain a DHCP address anymore for wired
and wifi interfaces.

>From what I could see, when dhclient6 gets called by network-manager,
this program gets denied a bunch of operations which makes it not do
what it's supposed to and just exit.

The weird part that I don't understand yet is that I don't think I've
installed or upgraded anything else since I enabled apparmor (so why
didn't I see this in a more consistent manner?).

In the syslog I found the following log lines that are relevant:

Nov 11 16:53:14 boohn kernel: [   15.622076] audit: type=1400 
audit(1510437193.949:5): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="dhclient" pid=620 comm="apparmor_parser"
Nov 11 16:53:20 boohn NetworkManager[678]:   [1510437200.9563] dhcp-init: 
Using DHCP client 'dhclient'
Nov 11 16:53:24 boohn NetworkManager[678]:   [1510437204.1739] dhcp4 
(eth0): dhclient started with pid 1184
Nov 11 16:53:24 boohn dhclient[1185]: execve 
(/usr/lib/NetworkManager/nm-dhcp-helper, ...): Permission denied
Nov 11 16:53:24 boohn kernel: [   25.862578] audit: type=1400 
audit(1510437204.189:74): apparmor="DENIED" operation="exec" profile="dhclient" 
name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=1185 comm="dhclient" 
requested_mask="x" denied_mask="x" fsuid=0 ouid=0
Nov 11 16:53:24 boohn dhclient[1184]: DHCPREQUEST of 192.168.2.243 on eth0 to 
255.255.255.255 port 67
Nov 11 16:53:24 boohn dhclient[1184]: DHCPNAK from 192.168.2.1
Nov 11 16:53:24 boohn dhclient[1186]: execve 
(/usr/lib/NetworkManager/nm-dhcp-helper, ...): Permission denied
Nov 11 16:53:24 boohn kernel: [   25.887214] audit: type=1400 
audit(1510437204.214:75): apparmor="DENIED" operation="exec" profile="dhclient" 
name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=1186 comm="dhclient" 
requested_mask="x" denied_mask="x" fsuid=0 ouid=0
Nov 11 16:53:24 boohn kernel: [   25.887967] audit: type=1400 
audit(1510437204.215:76): apparmor="DENIED" operation="exec" profile="dhclient" 
name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=1187 comm="dhclient" 
requested_mask="x" denied_mask="x" fsuid=0 ouid=0
Nov 11 16:53:24 boohn dhclient[1187]: execve 
(/usr/lib/NetworkManager/nm-dhcp-helper, ...): Permission denied
Nov 11 16:53:24 boohn dhclient[1184]: DHCPDISCOVER on eth0 to 255.255.255.255 
port 67 interval 3
Nov 11 16:53:24 boohn dhclient[1184]: DHCPREQUEST of 192.168.2.233 on eth0 to 
255.255.255.255 port 67
Nov 11 16:53:24 boohn dhclient[1184]: DHCPOFFER of 192.168.2.233 from 
192.168.2.1
Nov 11 16:53:24 boohn dhclient[1184]: DHCPACK of 192.168.2.233 from 192.168.2.1
Nov 11 16:53:24 boohn dhclient[1188]: execve 
(/usr/lib/NetworkManager/nm-dhcp-helper, ...): Permission denied
Nov 11 16:53:24 boohn kernel: [   25.894073] audit: type=1400 
audit(1510437204.221:77): apparmor="DENIED" operation="exec" profile="dhclient" 
name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=1188 comm="dhclient" 
requested_mask="x" denied_mask="x" fsuid=0 ouid=0
Nov 11 16:53:24 boohn dhclient[1184]: bound to 192.168.2.233 -- renewal in 
37728 seconds.
Nov 11 16:53:26 boohn NetworkManager[678]:   [1510437206.3351] dhcp6 
(eth0): dhclient started with pid 1189
Nov 11 16:53:26 boohn kernel: [   28.012088] audit: type=1400 
audit(1510437206.339:78): apparmor="DENIED" operation="open" profile="dhclient" 
name="/var/lib/NetworkManager/dhclient6-eth0.conf" pid=1189 comm="dhclient" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Nov 11 16:53:26 boohn kernel: [   28.012098] audit: type=1400 
audit(1510437206.339:79): apparmor="DENIED" operation="open" profile="dhclient" 
name="/var/lib/NetworkManager/dhclient6-b63c69a8-9bf3-4eef-9610-09eee2527a06-eth0.lease"
 pid=1189 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Nov 11 16:53:26 boohn kernel: [   28.012104] audit: type=1400 
audit(1510437206.339:80): apparmor="DENIED" operation="open" profile="dhclient" 
name="/var/lib/NetworkManager/dhclient6-b63c69a8-9bf3-4eef-9610-09eee2527a06-eth0.lease"
 pid=1189 comm="dhclient" requested_mask="wc" denied_mask="wc" fsuid=0 ouid=0
Nov 11 16:53:26 boohn dhclient[1189]: can't create 
/var/lib/NetworkManager/dhclient6-b63c69a8-9bf3-4eef-9610-09eee2527a06-eth0.lease:
 Permission denied
Nov 11 16:53:26 boohn dhclient[1190]: execve 
(/usr/lib/NetworkManager/nm-dhcp-helper, ...): Permission denied
Nov 11 16:53:26 boohn dhclient[1189]: Created duid 
"\000\001\000\001!\232-\326\360\336\361+\253L".
Nov 11 16:53:26 boohn dhclient[1189]: can't create 
/var/lib/NetworkManager/dhclient6-b63c69a8-9bf3-4eef-9610-09eee2527a06-eth0.lease:
 Permission denied
Nov 11 16:53:26 boohn dhclient[1189]: Can't create /run/dhclient6-eth0.pid: 
Permission denied
Nov 11 16:53:26 boohn kernel: [   28.012575] audit: type=1400 

Bug#881459: obsidian-icon-theme: New Icon Theme

2017-11-11 Thread Omar Jair Purata Funes
Package: obsidian-icon-theme
Version: 3.4
Severity: wishlist

For some time the faenza icon theme has been included into
debian and used in some desktop environments like MATE, now
there is a popular faenza-like icon theme that is in constant development, with
the inclusion of new applications faenza is now a little outdated, missing some
icons and it is not into active development anymore (according to github latest
commit was a year ago, and the other ones were 3 years ago).

Obsidian icon theme DOES meet the DFSG, it is based on the GPL v3.0 license
which means that source code can be redistributed & modified, it does not
discriminate any kind of groups/persons and it's license does not conflict with
any other piece of software inside Debian Gnu/Linux.

This icon theme could be a fine replacement of faenza, since it does include
some redesigned icons without losing the original "squared" style.

-Is it needed on Debian? Probably not at a server level, but part of the debian
desktop team is to deliver a good (dedundancy incoming) desktop-experience for
users, if moka icon theme was accepted and it's a relatively popular package
(amongst icon themes) I don't see why this theme cannot reach that mark being
one of the most popular ones in the gnome-look.org page.

Let me know your thoughts on this, maybe I'm missing something here.



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

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



Bug#881458: hlint fails to run

2017-11-11 Thread Tristan Seligmann
Package: hlint
Version: 2.0.9-1+b1
Severity: important

hlint fails to run on everything with this error:

hlint: user error (Failed to find requested hint files:
  /usr/share/hlint/hlint.yaml
)   

That file does indeed not exist (and is not present in the hlint package).

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

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

Versions of packages hlint depends on:
ii  libc62.24-17
ii  libffi6  3.2.1-6
ii  libgmp10 2:6.1.2+dfsg-1.1
ii  libyaml-0-2  0.1.7-2

Versions of packages hlint recommends:
ii  ghc  8.0.2-10

hlint suggests no packages.

-- no debconf information



Bug#881352: kernel crash while upgrading udisks2

2017-11-11 Thread Jiri Palecek

Hello,

I got a similar crash as well (submitted through kerneloops). BT:

[41523.485941] [ cut here ]
[41523.485951] WARNING: CPU: 0 PID: 0 at 
/build/linux-d8soVg/linux-4.13.10/kernel/rcu/tree.c:2821 
rcu_process_callbacks+0x43e/0x460
[41523.485953] Modules linked in: snd_hrtimer snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device cpufreq_powersave 
cpufreq_userspace cpufreq_conservative binfmt_misc fuse nvidia_drm(PO) 
drm_kms_helper drm nls_iso8859_2 snd_hda_codec_via snd_hda_codec_hdmi 
nls_cp437 snd_hda_codec_generic vfat fat nvidia_modeset(PO) 
snd_hda_intel snd_hda_codec snd_hda_core nvidia(PO) snd_hwdep 
snd_pcm_oss edac_mce_amd kvm_amd kvm snd_mixer_oss snd_pcm psmouse 
irqbypass snd_timer sr_mod snd cdrom soundcore pcspkr sg sata_nv 
ohci_pci k10temp ohci_hcd ehci_pci shpchp ehci_hcd forcedeth i2c_nforce2 
asus_atk0110 button acpi_cpufreq usblp usbcore usb_common parport_pc 
ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 
crc32c_generic fscrypto ecb crypto_simd cryptd aes_i586 sd_mod serio_raw 
ata_generic

[41523.485987]  pata_amd libata scsi_mod evdev
[41523.485991] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P O    
4.13.0-1-686-pae #1 Debian 4.13.10-1
[41523.485993] Hardware name: System manufacturer System Product 
Name/M4N68T-M, BIOS 1301    07/05/2011

[41523.485995] task: c77b0280 task.stack: c77a8000
[41523.485997] EIP: rcu_process_callbacks+0x43e/0x460
[41523.485998] EFLAGS: 00010002 CPU: 0
[41523.486000] EAX:  EBX: f4271b00 ECX: 0002 EDX: 0001
[41523.486001] ESI: c77cb8c0 EDI: f4271b20 EBP: fff6 ESP: f3cabfa0
[41523.486002]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[41523.486004] CR0: 80050033 CR2: b444f014 CR3: 306acb00 CR4: 06f0
[41523.486005] Call Trace:
[41523.486008]  
[41523.486012]  ? __do_softirq+0xce/0x235
[41523.486014]  ? __softirqentry_text_start+0x8/0x8
[41523.486016]  ? do_softirq_own_stack+0x21/0x30
[41523.486017]  
[41523.486019]  ? irq_exit+0xad/0xc0
[41523.486021]  ? smp_apic_timer_interrupt+0x35/0x40
[41523.486023]  ? apic_timer_interrupt+0x34/0x3c
[41523.486025]  ? native_safe_halt+0x2/0x10
[41523.486027]  ? default_idle+0x19/0xf0
[41523.486029]  ? do_idle+0x145/0x1c0
[41523.486031]  ? cpu_startup_entry+0x65/0x70
[41523.486033]  ? start_kernel+0x385/0x39c
[41523.486035]  ? startup_32_smp+0x16b/0x16d
[41523.486036] Code: b3 7c c7 0f 8f 1a ff ff ff 8b 15 e0 b3 7c c7 89 53 
64 e9 0c ff ff ff 8d b6 00 00 00 00 89 ea 89 f8 e8 e7 67 50 00 e9 61 fc 
ff ff <0f> ff e9 21 ff ff ff 0f ff e9 f4 fc ff ff e8 bf 8b f9 ff eb 0d

[41523.486054] ---[ end trace 3dbeb3dfc6223f18 ]---

However, I wonder if this is the same as https://bugs.debian.org/876712. 
The backtrace points to softirq processing and rcu as well. I've got 
more of such backtraces (one of them, however, points to an assertion 
failure in rcu code). However, the problem seems sporadic in nature 
(some race condition causing a memory error?) and hard to reproduce.


Please let me know if I can help in any way.

Regards

    Jiri Palecek



Bug#848674: O: f3 -- test real flash memory capacity

2017-11-11 Thread Antoine Beaupre
Control: owner -1 anar...@debian.org
Control: tags -1 +pending

I'm interested in taking over this package. I've worked with upstream
and I use it from time to time. I'll monitor upstream which I hope will
produce a new release soon and then I'll switch maintainership.

It will stay in collab-maint and I'm in lowNMU so don't stop yourself
from taking this on if you're motivated.

A.
-- 
The value of a college education is not the learning of many facts but
the training of the mind to think.
   - Albert Einstein


signature.asc
Description: PGP signature


Bug#881457: glibc: please add mips r6 support

2017-11-11 Thread YunQiang Su
Package: src:glibc
Version: 2.24-17

Since stretch's dpkg has support mips r6 architectures and DSA are
also using it,
we can add mips r6 support now.

MIPS release r6 architectures are new release of MIPS, while they are
not compatible
with the r5/r2 ones.
So we need to treat them as new architectures.

There are also 6 flavors:
 mipsr6 mipsr6el  mipsn32r6 mipsn32r6el  mips64r6 mips64r6el


In this patch, I also include:
  symbol file for mipsn32/mipsn32el/mips64.

-- 
YunQiang Su
diff --git a/debian/control.in/mips32 b/debian/control.in/mips32
index 1d5008a..7831000 100644
--- a/debian/control.in/mips32
+++ b/debian/control.in/mips32
@@ -1,5 +1,5 @@
 Package: libc6-mips32
-Architecture: mipsn32 mipsn32el mips64 mips64el
+Architecture: mipsn32 mipsn32el mips64 mips64el mipsn32r6 mipsn32r6el mips64r6 
mips64r6el
 Section: libs
 Priority: optional
 Depends: libc6 (= ${binary:Version}), ${misc:Depends}
@@ -10,13 +10,13 @@ Description: GNU C Library: o32 Shared libraries for MIPS
  of the library, meant for MIPS systems.
 
 Package: libc6-dev-mips32
-Architecture: mipsn32 mipsn32el mips64 mips64el
+Architecture: mipsn32 mipsn32el mips64 mips64el mipsn32r6 mipsn32r6el mips64r6 
mips64r6el
 Section: libdevel
 Priority: optional
 Provides: lib32c-dev
 Depends: libc6-dev (= ${binary:Version}), libc6-mips32 (= ${binary:Version}),
-   libc6-dev-mipsn32 (= ${binary:Version}) [mips64 mips64el],
-   libc6-dev-mips64 (= ${binary:Version}) [mipsn32 mipsn32el],
+   libc6-dev-mipsn32 (= ${binary:Version}) [mips64 mips64el mips64r6 
mips64r6el],
+   libc6-dev-mips64 (= ${binary:Version}) [mipsn32 mipsn32el mipsn32r6 
mipsn32r6el],
${misc:Depends}
 Recommends: gcc-multilib
 Build-Profiles: 
diff --git a/debian/control.in/mips64 b/debian/control.in/mips64
index ec7b70c..32aa1f3 100644
--- a/debian/control.in/mips64
+++ b/debian/control.in/mips64
@@ -1,5 +1,5 @@
 Package: libc6-mips64
-Architecture: mips mipsel mipsn32 mipsn32el
+Architecture: mips mipsel mipsn32 mipsn32el mipsr6 mipsr6el mipsn32r6 
mipsn32r6el
 Section: libs
 Priority: optional
 Depends: libc6 (= ${binary:Version}), ${misc:Depends}
@@ -10,7 +10,7 @@ Description: GNU C Library: 64bit Shared libraries for MIPS64
  of the library, meant for MIPS64 systems.
 
 Package: libc6-dev-mips64
-Architecture: mips mipsel mipsn32 mipsn32el
+Architecture: mips mipsel mipsn32 mipsn32el mipsr6 mipsr6el mipsn32r6 
mipsn32r6el
 Section: libdevel
 Priority: optional
 Provides: lib64c-dev
diff --git a/debian/control.in/mipsn32 b/debian/control.in/mipsn32
index 019fce2..9ad5c0a 100644
--- a/debian/control.in/mipsn32
+++ b/debian/control.in/mipsn32
@@ -1,5 +1,5 @@
 Package: libc6-mipsn32
-Architecture: mips mipsel mips64 mips64el
+Architecture: mips mipsel mips64 mips64el mipsr6 mipsr6el mips64r6 mips64r6el
 Section: libs
 Priority: optional
 Depends: libc6 (= ${binary:Version}), ${misc:Depends}
@@ -10,11 +10,11 @@ Description: GNU C Library: n32 Shared libraries for MIPS64
  of the library, meant for MIPS64 systems.
 
 Package: libc6-dev-mipsn32
-Architecture: mips mipsel mips64 mips64el
+Architecture: mips mipsel mips64 mips64el mipsr6 mipsr6el mips64r6 mips64r6el
 Section: libdevel
 Priority: optional
 Provides: libn32c-dev
-Depends: libc6-mipsn32 (= ${binary:Version}), libc6-dev-mips64 (= 
${binary:Version}) [mips mipsel], libc6-dev (= ${binary:Version}), 
${misc:Depends}
+Depends: libc6-mipsn32 (= ${binary:Version}), libc6-dev-mips64 (= 
${binary:Version}) [mips mipsel mipsr6 mipsr6el], libc6-dev (= 
${binary:Version}), ${misc:Depends}
 Recommends: gcc-multilib
 Build-Profiles: 
 Description: GNU C Library: n32 Development Libraries for MIPS64
diff --git a/debian/libc6-mips32.symbols.mips64 
b/debian/libc6-mips32.symbols.mips64
new file mode 100644
index 000..5933230
--- /dev/null
+++ b/debian/libc6-mips32.symbols.mips64
@@ -0,0 +1,5 @@
+#include "libc6.symbols.common"
+ld.so.1 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
+libc.so.6 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
diff --git a/debian/libc6-mips32.symbols.mips64r6 
b/debian/libc6-mips32.symbols.mips64r6
new file mode 100644
index 000..5933230
--- /dev/null
+++ b/debian/libc6-mips32.symbols.mips64r6
@@ -0,0 +1,5 @@
+#include "libc6.symbols.common"
+ld.so.1 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
+libc.so.6 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
diff --git a/debian/libc6-mips32.symbols.mips64r6el 
b/debian/libc6-mips32.symbols.mips64r6el
new file mode 100644
index 000..5933230
--- /dev/null
+++ b/debian/libc6-mips32.symbols.mips64r6el
@@ -0,0 +1,5 @@
+#include "libc6.symbols.common"
+ld.so.1 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
+libc.so.6 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
diff --git a/debian/libc6-mips32.symbols.mipsn32 
b/debian/libc6-mips32.symbols.mipsn32
new file mode 100644
index 000..5933230
--- /dev/null
+++ b/debian/libc6-mips32.symbols.mipsn32
@@ -0,0 +1,5 @@
+#include "libc6.symbols.common"
+ld.so.1 #PACKAGE# #MINVER#

Bug#881456: gmediarender: Service started on system boot, but not accepting connections

2017-11-11 Thread Marcos Raul Carot
Package: gmediarender
Version: 0.0.7~git20160329+repack-1
Severity: normal

Dear Maintainer,

   * What led up to the situation? Installing the package just using aptitude
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Despite the service starting on boot, it does not show in 
dlna controllers. Manually running gmediarender -d works fine
   * What was the outcome of this action? Manually running works. Systemd unit 
shows axtive )exited) and does not.
   * What outcome did you expect instead? daemon active on boot.


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

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

Versions of packages gmediarender depends on:
ii  libc6  2.24-17
ii  libglib2.0-0   2.54.1-1
ii  libgstreamer1.0-0  1.12.3-1
ii  libupnp6   1:1.6.22-1
ii  lsb-base   9.20170808

Versions of packages gmediarender recommends:
ii  gstreamer1.0-plugins-good  1.12.3-1

Versions of packages gmediarender suggests:
pn  gstreamer-plugins-ugly
ii  gstreamer1.0-plugins-bad  1.12.3-2

-- no debconf information



Bug#881455: glibc: don't build hardware enhancement library packages when stage1

2017-11-11 Thread YunQiang Su
Package: src:glibc
Version: 2.24-17

hardware enhancement library packages like xen on i386/hurd-i386,
and alphpaev67 on alpha, are not needed for stage1
They are also marked as
Build-Profiles: 

So we need to remove them.

-- 
YunQiang Su
diff --git a/debian/sysdeps/alpha.mk b/debian/sysdeps/alpha.mk
index 223b097..cf8a263 100644
--- a/debian/sysdeps/alpha.mk
+++ b/debian/sysdeps/alpha.mk
@@ -1,6 +1,7 @@
 # configuration options for all flavours
 libc = libc6.1
 
+ifeq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
 # build an ev67 optimized library
 GLIBC_PASSES += alphaev67
 DEB_ARCH_REGULAR_PACKAGES += libc6.1-alphaev67
@@ -8,3 +9,4 @@ alphaev67_configure_target = alphaev67-linux-gnu
 alphaev67_CC = $(CC) -mcpu=ev67 -mtune=ev67 
 alphaev67_CXX = $(CXX) -mcpu=ev67 -mtune=ev67 
 alphaev67_slibdir = /lib/$(DEB_HOST_MULTIARCH)/ev67
+endif
diff --git a/debian/sysdeps/hurd-i386.mk b/debian/sysdeps/hurd-i386.mk
index 81ce1c7..0fccd01 100644
--- a/debian/sysdeps/hurd-i386.mk
+++ b/debian/sysdeps/hurd-i386.mk
@@ -1,3 +1,4 @@
+ifeq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
 # We use -mno-tls-direct-seg-refs to not wrap-around segments, as it
 # greatly increase the speed when running under the 32bit Xen hypervisor.
 GLIBC_PASSES += xen
@@ -6,7 +7,6 @@ xen_extra_cflags = -mno-tls-direct-seg-refs
 xen_slibdir = /lib/$(DEB_HOST_MULTIARCH)/i686/nosegneg
 xen_add-ons = $(libc_add-ons)
 
-ifeq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
 define libc0.3-dev_extra_pkg_install
 mkdir -p debian/libc0.3-dev/$(libdir)/xen
 cp -af debian/tmp-xen/$(libdir)/*.a \
diff --git a/debian/sysdeps/i386.mk b/debian/sysdeps/i386.mk
index 1c87ec2..003f1d6 100644
--- a/debian/sysdeps/i386.mk
+++ b/debian/sysdeps/i386.mk
@@ -2,6 +2,7 @@
 extra_config_options = --enable-multi-arch
 MIN_KERNEL_SUPPORTED := 2.6.32
 
+ifeq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
 # We use -mno-tls-direct-seg-refs to not wrap-around segments, as it
 # greatly increase the speed when running under the 32bit Xen hypervisor.
 GLIBC_PASSES += xen
@@ -18,6 +19,7 @@ echo '# search in nosegneg subdirectories and to match this 
extra hwcap bit'  >>
 echo '# in the ld.so.cache file.' 
>> debian/libc6-xen/etc/ld.so.conf.d/libc6-xen.conf
 echo 'hwcap 1 nosegneg'   
>> debian/libc6-xen/etc/ld.so.conf.d/libc6-xen.conf
 endef
+endif
 
 # build 64-bit (amd64) alternative library
 GLIBC_MULTILIB_PASSES += amd64


Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

2017-11-11 Thread Michael Biebl
Control: tags -1 = patch

Am 12.11.2017 um 00:33 schrieb Alex King:

> So it seems like this will be a problem for stretch systems with
> usrmerge enabled, and are not using systemd-resolved

Indeed, these are the conditions under which you can trigger this issue.

Looking through the git history, to fix this issue, we'd have to  backport
7debb05dbe1f157e5f07c9bffa98fbe33e1b514e
b053cd5f8e48e04ac576296404848bbb8dd26854
7357272ed1c2c7a139c9ecbc8f3b8f63f71dd0b0

That seems like a bit much for a stable upload and I'm not sure if the
stable release managers are ok with such a change, given that this only
affects usrmerged systems.

If you want to see this fixed in stretch, please consider talking to the
stable release managers and get an ok.

I'm attaching the necessary patches. As for buster, the issue is already
fixed there.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
From ce15fd8f60433530f4a157299f711c9fc85ecf14 Mon Sep 17 00:00:00 2001
From: Christian Hesse 
Date: Wed, 9 Nov 2016 04:01:26 +0100
Subject: [PATCH 1/3] nspawn: fix condition for mounting resolv.conf (#4622)

The file /usr/lib/systemd/resolv.conf can be stale, it does not tell us
whether or not systemd-resolved is running or not.
So check for /run/systemd/resolve/resolv.conf as well, which is created
at runtime and hence is a better indication.

(cherry picked from commit 7debb05dbe1f157e5f07c9bffa98fbe33e1b514e)
---
 src/nspawn/nspawn.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/nspawn/nspawn.c b/src/nspawn/nspawn.c
index c56af6e6f..608ad0598 100644
--- a/src/nspawn/nspawn.c
+++ b/src/nspawn/nspawn.c
@@ -1309,7 +1309,8 @@ static int setup_resolv_conf(const char *dest) {
 /* Fix resolv.conf, if possible */
 where = prefix_roota(dest, "/etc/resolv.conf");
 
-if (access("/usr/lib/systemd/resolv.conf", F_OK) >= 0) {
+if (access("/run/systemd/resolve/resolv.conf", F_OK) >= 0 &&
+access("/usr/lib/systemd/resolv.conf", F_OK) >= 0) {
 /* resolved is enabled on the host. In this, case bind mount its static resolv.conf file into the
  * container, so that the container can use the host's resolver. Given that network namespacing is
  * disabled it's only natural of the container also uses the host's resolver. It also has the big
-- 
2.15.0

From ac0e333259054ccb2bd09bb4841616efe3b53d02 Mon Sep 17 00:00:00 2001
From: Lennart Poettering 
Date: Thu, 16 Feb 2017 17:56:10 +0100
Subject: [PATCH 2/3] nspawn: tweak check whether resolved is around a bit

Let's check D-Bus instead of files in /run to see if resolved is
running. This is a bit nicer as bus names are automatically cleaned up
when resolved dies, which is not the case for files in /run.

See: #4649
(cherry picked from commit b053cd5f8e48e04ac576296404848bbb8dd26854)
---
 src/nspawn/nspawn.c | 20 ++--
 1 file changed, 18 insertions(+), 2 deletions(-)

diff --git a/src/nspawn/nspawn.c b/src/nspawn/nspawn.c
index 608ad0598..d641acb10 100644
--- a/src/nspawn/nspawn.c
+++ b/src/nspawn/nspawn.c
@@ -40,6 +40,7 @@
 #include 
 #include 
 
+#include "sd-bus.h"
 #include "sd-daemon.h"
 #include "sd-id128.h"
 
@@ -48,6 +49,7 @@
 #include "base-filesystem.h"
 #include "blkid-util.h"
 #include "btrfs-util.h"
+#include "bus-util.h"
 #include "cap-list.h"
 #include "capability-util.h"
 #include "cgroup-util.h"
@@ -1297,6 +1299,19 @@ static int setup_timezone(const char *dest) {
 return 0;
 }
 
+static int resolved_running(void) {
+_cleanup_(sd_bus_flush_close_unrefp) sd_bus *bus = NULL;
+int r;
+
+/* Check if resolved is running */
+
+r = sd_bus_open_system();
+if (r < 0)
+return r;
+
+return bus_name_has_owner(bus, "org.freedesktop.resolve1", NULL);
+}
+
 static int setup_resolv_conf(const char *dest) {
 const char *where = NULL;
 int r;
@@ -1309,8 +1324,9 @@ static int setup_resolv_conf(const char *dest) {
 /* Fix resolv.conf, if possible */
 where = prefix_roota(dest, "/etc/resolv.conf");
 
-if (access("/run/systemd/resolve/resolv.conf", F_OK) >= 0 &&
-access("/usr/lib/systemd/resolv.conf", F_OK) >= 0) {
+if (access("/usr/lib/systemd/resolv.conf", F_OK) >= 0 &&
+resolved_running() > 0) {
+
 /* resolved is enabled on the host. In this, case bind mount its static resolv.conf file into the
  * container, so that the container can use the host's resolver. Given that network namespacing is
  * disabled it's only natural of the container also uses the host's resolver. It also has the big
-- 
2.15.0

From 5726bd456216b9002a4f01490f0522d234b3224c Mon Sep 17 00:00:00 2001
From: David Michael 
Date: Wed, 8 Mar 2017 12:45:03 -0800

Bug#881454: glibc: don't try build shared library packages when stage1

2017-11-11 Thread YunQiang Su
Package: src:glibc
Version: 2.24-17

Since libc6/libc6.1 etc are marked as
   Build-Profiles: 
So we need to disabled them in
   DEB_ARCH_REGULAR_PACKAGES


-- 
YunQiang Su
diff --git a/debian/rules b/debian/rules
index a7a6ed1..a18e268 100755
--- a/debian/rules
+++ b/debian/rules
@@ -165,7 +165,11 @@ standard-add-ons = libidn,
 
 ifeq ($(filter nobiarch,$(DEB_BUILD_PROFILES)),)
 GLIBC_PASSES += $(GLIBC_MULTILIB_PASSES)
+ifeq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
 DEB_ARCH_REGULAR_PACKAGES += $(DEB_ARCH_MULTILIB_PACKAGES)
+else
+DEB_ARCH_REGULAR_PACKAGES += $(filter 
libc6-dev-%,$(DEB_ARCH_MULTILIB_PACKAGES))
+endif
 endif
 
 # Don't run dh_strip on this package


Bug#881453: primesieve FTBFS on i386: test failures

2017-11-11 Thread Adrian Bunk
Source: primesieve
Version: 6.2+ds-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=primesieve=i386=6.2%2Bds-1=1510442732=0

...
   dh_auto_test -a -O--builddirectory=_build
cd _build && make -j4 test ARGS\+=-j4
make[1]: Entering directory '/<>/primesieve-6.2+ds/_build'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j4
Test project /<>/primesieve-6.2+ds/_build
  Start  1: atomic
  Start  2: count_primes1
  Start  3: count_primes2
  Start  4: count_primes3
 1/24 Test  #1: atomic ...   Passed0.28 sec
 2/24 Test  #2: count_primes1    Passed0.30 sec
  Start  5: count_quadruplets
  Start  6: count_quintuplets
 3/24 Test  #5: count_quadruplets    Passed0.90 sec
 4/24 Test  #6: count_quintuplets    Passed1.08 sec
  Start  7: count_sextuplets
  Start  8: count_triplets
 5/24 Test  #8: count_triplets ...   Passed0.89 sec
 6/24 Test  #7: count_sextuplets .   Passed1.11 sec
  Start  9: count_twins
  Start 10: cpu_info
 7/24 Test #10: cpu_info .   Passed0.31 sec
  Start 11: floorPow2
 8/24 Test #11: floorPow2 ***Failed0.21 sec
floorPow2(1) = 1   OK
floorPow2(2) = 2   OK
floorPow2(3) = 2   OK
floorPow2(4) = 4   OK
floorPow2(5) = 4   OK
floorPow2(6) = 4   OK
floorPow2(7) = 4   OK
floorPow2(8) = 8   ERROR

  Start 12: generate_n_primes1
 9/24 Test  #9: count_twins ..   Passed0.94 sec
  Start 13: generate_primes1
10/24 Test #13: generate_primes1 .   Passed0.30 sec
  Start 14: ilog2
11/24 Test #14: ilog2 ***Failed0.30 sec
ilog2(1) = 0   OK
ilog2(2) = 1   OK
ilog2(3) = 1   OK
ilog2(4) = 2   OK
ilog2(5) = 2   OK
ilog2(6) = 2   OK
ilog2(7) = 2   OK
ilog2(8) = 3   ERROR

  Start 15: isqrt
12/24 Test #15: isqrt    Passed0.89 sec
  Start 16: next_prime1
13/24 Test #16: next_prime1 ..   Passed3.21 sec
  Start 17: nth_prime1
14/24 Test #17: nth_prime1 ...   Passed3.52 sec
  Start 18: nth_prime2
15/24 Test #12: generate_n_primes1 ...   Passed   15.50 sec
  Start 19: nth_prime3
16/24 Test  #3: count_primes2    Passed   22.85 sec
  Start 20: prev_prime1
17/24 Test #18: nth_prime2 ...   Passed   16.06 sec
  Start 21: generate_n_primes2
18/24 Test #21: generate_n_primes2 ...   Passed0.61 sec
  Start 22: generate_primes2
19/24 Test  #4: count_primes3    Passed   29.38 sec
  Start 23: next_prime2
20/24 Test #19: nth_prime3 ...   Passed   23.31 sec
  Start 24: prev_prime2
21/24 Test #20: prev_prime1 ..   Passed   22.00 sec
22/24 Test #24: prev_prime2 ..   Passed3.24 sec
23/24 Test #22: generate_primes2 .   Passed   19.13 sec
24/24 Test #23: next_prime2 ..   Passed   21.86 sec

92% tests passed, 2 tests failed out of 24

Total Test time (real) =  51.51 sec

The following tests FAILED:
 11 - floorPow2 (Failed)
 14 - ilog2 (Failed)
Errors while running CTest
Makefile:121: recipe for target 'test' failed
make[1]: *** [test] Error 8


This can be fixed with:

--- debian/rules.old2017-11-12 00:16:05.0 +
+++ debian/rules2017-11-12 00:17:52.0 +
@@ -17,6 +17,11 @@
CXXFLAGS := $(subst -O2,-O3,$(CXXFLAGS))
 endif
 
+ifeq ($(DEB_HOST_ARCH),i386)
+CFLAGS   += -ffloat-store
+CXXFLAGS += -ffloat-store
+endif
+
 default:
@uscan --no-conf --dehs --report || true
 



Bug#881272: gcc-5-: broken symlink /usr/lib/gcc-cross//5/libcc1.so -> ../../../..//lib/libcc1.so.0

2017-11-11 Thread Andreas Beckmann
On 11/09/2017 04:43 PM, Matthias Klose wrote:
> is this with the gcc-5-cross* packages which are currently built but not 
> uploaded?

I waited a bit, but no new binaries appeared. The tested packages are
versioned 5.5.0-3cross1.

There is another broken link in some gcj-5- packages, that does
remind me of #855640 in gcc-6:

0m40.1s ERROR: FAIL: Broken symlinks:
  /usr/lib/gcc-cross/alpha-linux-gnu/5/ecj1 -> ../../ecj1


Andreas



Bug#819959: links2: Does not jump to fragments of the current documents

2017-11-11 Thread Axel Beckert
Control: tag -1 unreproducible

Hi Axel, :-)

Dr. Axel Stammler wrote:
> Thanks for your tips! You are right, of course, I do mean " href='#crash'>", and I have
> changed "" to "" — unfortunately 
> to no avail,
> the problem persists.

Ok, I tried to reproduce the issue with the following example file:



  
819959.html
  
  
Example for #819959

'#crash'
"#crash2"
'#crash3'
"#crash4"
























id='crash'
id="crash2"
name='crash3'
name="crash4"
  


Unexpectedly #crash and #crash2 work, and #crash3 and #crash4 don't.

That's exactly the opposite of what I expected ("name=" being the
classic jump targets for "href=#") and also the opposite of what your
bug report says.

elinks and lynx both show the same behaviour. I've tried all three
browsers on Debian 7 Wheezy, Debian 8 Jessie (from where your original
report seem) and on Debian Unstable. (Debian 9 Stretch and Debian
Unstable at least have the same links2 upstream version, so that
behaviour shouldn't have changed inbetween.)

It would be nice if you cold check the above HTML code against your
system and check if you still can reproduce the issue with that code.
(If you can't reproduce it neither with that code, please attach the
file in question where this issue occurs.)

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



Bug#881452: RFS: xe/0.11-1 -- simple alternative to xargs and apply

2017-11-11 Thread Nicolas Braud-Santoni
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: xe
  Version : 0.11-1
  Upstream Author : Leah Neukirchen 
* URL : https://github.com/chneukirchen/xe
* License : MIT
  Section : utils

It builds those binary packages:

  xe- simple alternative to xargs and apply

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

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


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

  dget -x https://mentors.debian.net/debian/pool/main/x/xe/xe_0.11-1.dsc


Changes since the last upload:

  * New upstream version (2017-11-05)


Best,

  nicoo


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

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



Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

2017-11-11 Thread Alex King



On 12/11/17 00:53, Michael Biebl wrote:

Hi Alex

Am 11.11.2017 um 00:33 schrieb Alex King:

looks like everything that should be in /lib/systemd and
/usr/lib/systemd is duplicated in both places?!  I guess that is most
likely a sysadmin typo, although the system was reloaded relatively
recently and I have no idea how this could have happened.

That sounds like you might have usrmerge enabled, i.e. /lib is a symlink
to /usr/lib etc. This would explain the resolv.conf in both locations.

Can you post the output of "ls -la /"

Such a system can be created by using debootstrap's --merged-usr or
installing the usrmerge package in the final system.

Michael


Indeed you are correct, this is has a merged /usr:

$ ls -la /
total 68
drwxr-xr-x  18 root root  4096 Nov 11 20:21 .
drwxr-xr-x  18 root root  4096 Nov 11 20:21 ..
lrwxrwxrwx   1 root root 7 Jun 23 23:52 bin -> usr/bin
drwxr-xr-x   2 root root  4096 Apr  4  2017 boot
drwxr-xr-x  12 root root  3380 Nov  9 22:01 dev
drwxr-xr-x  85 root root  4096 Nov  9 23:38 etc
drwxr-xr-x   5 root root  4096 Nov  9 22:59 home
lrwxrwxrwx   1 root root 7 Jun 23 23:52 lib -> usr/lib
lrwxrwxrwx   1 root root 9 Jun 23 23:52 lib32 -> usr/lib32
lrwxrwxrwx   1 root root 9 Jun 23 23:52 lib64 -> usr/lib64
lrwxrwxrwx   1 root root    10 Jun 23 23:52 libx32 -> usr/libx32
drwx--   2 root root 16384 Jun 23 23:44 lost+found
drwxr-xr-x   2 root root  4096 Jun 23 23:52 media
drwxr-xr-x   2 root root  4096 Jun 23 23:52 mnt
drwxr-xr-x   2 root root  4096 Jun 23 23:52 opt
dr-xr-xr-x 152 root root 0 Nov  9 22:01 proc
drwx--   6 root root  4096 Nov 11 20:25 root
drwxr-xr-x  18 root root   580 Nov 11 20:35 run
lrwxrwxrwx   1 root root 8 Jun 23 23:52 sbin -> usr/sbin
drwxr-xr-x   2 root root  4096 Jun 23 23:52 srv
dr-xr-xr-x  13 root root 0 Nov 10 23:47 sys
drwxrwxrwt  10 root root  4096 Nov 11 20:35 tmp
drwxr-xr-x  13 root root  4096 Jun 23 23:52 usr
drwxr-xr-x  12 root root  4096 Jun 30 00:56 var

It looks like the VPS was supplied like that.

So it seems like this will be a problem for stretch systems with 
usrmerge enabled, and are not using systemd-resolved


Thanks,
Alex



Bug#880008: hdparm sets -B for all drives, despite what it says in hdparm.conf

2017-11-11 Thread Alex Mestiashvili
On 10/28/2017 12:07 PM, Ralf Jung wrote:
> Package: hdparm
> Version: 9.51+ds-1
> Severity: normal
>
> Dear Maintainer,
>
> hdparm.conf says:
>
> ## /sbin/hdparm is not run unless a block of the form:
> ##  DEV {
> ## option
> ## option
> ## ...
> ##  }
> ## exists.
>
> However, thta turns out to be wrong.  My hdparm.conf only contains a
block for
> /dev/sdb, and yet:
>
> # /lib/systemd/system-sleep/hdparm post
>
> /dev/sda:
>  setting Advanced Power Management level to 0xfe (254)
>  APM_level= 254
>
> /dev/sdb:
>  setting Advanced Power Management level to 0xfe (254)
>  APM_level= 254
>
> /dev/sdb:
>  setting standby to 50 (4 minutes + 10 seconds)
>
> As you can see, hdparm is called for /dev/sda as well.
>
> Kind regards,
> Ralf
> -- Configuration Files:
> /etc/hdparm.conf changed:
> quiet
> /dev/sdb {
> #apm = 254
> #apm_battery = 254
> # spin-down time of 4:10 min (=50*5 seconds)
> spindown_time = 50
> }


You are right, hdparm shouldn't be touching all disk in the system, but
there is a reason. The issue is summarized here:

 https://wiki.ubuntu.com/DanielHahler/Bug59695
 https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695

Currently -B 254 on AC power and -B 128 on battery seem to be the
sensible default values for the vast majority of disks and are set for
every disk supporting APM.

These defaults are defined in /lib/hdparm/hdparm-functions in
hdparm_option() function.

The (ancient) documentation of hdparm need to be updated to note
these defaults.

Best regards,
Alex


Bug#762715: updates to dch --lts

2017-11-11 Thread Mattia Rizzolo
On Mon, Oct 23, 2017 at 11:21:49AM -0400, Antoine Beaupré wrote:
> I think what we would need here is a "before/after" set of tricky
> changelog files and flags. Building such a corpus takes time,
> unfortunately, but the actual tests shouldn't be that hard...

Yeah, I agree on that..

Anyway, I've wrote a very very small testcase that clearly is not
exercising anything at all, just for some peace of mind.

I also tweaked the merge that you did with your first patches; as I
wrote in a commit I doubt that code ever worked at all, as those regex
looks wrong to me on several levels, but it's so messy that I don't feel
like further refactoring it by myself.


All in all, I've committed it, I'd appreciate if people could run with
git's debchange so to also check nothing was broken by this.

-- 
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#881451: Insecure dependency in chdir while running with -T switch at /usr/share/perl/5.26/File/Find.pm line 375

2017-11-11 Thread Daniel Leidert
Package: perl-modules-5.26
Version: 5.26.1-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I just wrote a test for a module using Test::Version. Running the test shows
the mentioned message:

t/00-version.t .. Insecure dependency in chdir while running with -T switch at 
/usr/share/perl/5.26/File/Find.pm line 375.
t/00-version.t .. Dubious, test returned 255 (wstat 65280, 0xff00)

I'm not fully sure, but the mentioned issue File::Find might cause the test
failure.

Regards, Daniel


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

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

Versions of packages perl-modules-5.26 depends on:
ii  dpkg   1.19.0.4
ii  perl-base  5.26.1-2

Versions of packages perl-modules-5.26 recommends:
ii  perl  5.26.1-2

perl-modules-5.26 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAloHhJUACgkQS80FZ8KW
0F0OcBAAp9J7RGoKmhlOvHecMaYJJwMC+GvV8Wb1WmygElnIsMu0Ia1MKiZ6Ci+D
kolOvt/cfIYfylDG6IrGQjDph/UzQGc/uRfPajJLyx4omR0rrBVQp22TQTdQF0ow
jfXHbs2o6SEbwnPx9JWc8M362sxj5k/WIVp1CQUFmbYHE0ZcjNMtRNUeSrk4KfIw
NVJhaRFnO8zhSkaHOY5md/OAOWJYt/fMm9hODpDUJbSQGrMT0jDT4LDceDeqT1ed
NCP4G61+ld7yU6f6sL7iJX/XKSZaGvctorkuXTgZfmqqkvSvgCB31Mid/q2Q2D/Q
HOE6h+UgtP9R7/acNbI9KwuWeelUcFjsCt0PL4pAZ8IyZD8XE4fOYZ4roaSM25Os
ILKC4cN+MPAurVPNfHrd3gex+VyK3IAz0g0M2+qChsWYV/IFDeeGJjE0nUwRWTep
6pY2m5YbtPDgtAGXIR6DvcS9HD7rWB5PntC9lv/mLyArH4S6LuNM5w5c3tSWdQ4x
hy2bLQILFEaGeG3VKNH//BBZ++u/JP2HZTGHixu28xQpKGYxqloE5G8EdVWNp/Fj
Z0cjX1i7huEH8h1str4eCPZ2RCOnlO+E4jZVVifubMz7ABRToOENHedb/JyrteI7
yTZulLj5TO6oFjw0UuZiWl09mgkPfgUreZOD3pmLtMDgMp7d4t4=
=jsE4
-END PGP SIGNATURE-



Bug#819959: links2: Does not jump to fragments of the current documents

2017-11-11 Thread Dr. Axel Stammler
Hi, Axel ;)

Thanks for your tips! You are right, of course, I do mean "", 
and I have
changed "" to "" — unfortunately 
to no avail,
the problem persists.

Regards,

Axel


signature.asc
Description: PGP signature


Bug#881450: RFS: lr/1.1-2 -- list files, recursively

2017-11-11 Thread Nicolas Braud-Santoni
Package: sponsorship-requests
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear mentors,

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

* Package name: lr
  Version : 1.1-2
  Upstream Author : Leah Neukirchen 
* URL : https://github.com/chneukirchen/lr
* License : MIT
  Section : utils

It builds those binary packages:

  lr- list files, recursively

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

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


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

  dget -x https://mentors.debian.net/debian/pool/main/l/lr/lr_1.1-2.dsc


Changes since the last upload:

  * Fix build on hurd (Closes: #880852)


Best,

  nicoo

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

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

-BEGIN PGP SIGNATURE-

iQJNBAEBCgA3FiEEiWEbFKE2h/s1SpJPnU+IAQz+GeMFAloHgVAZHG5pY29sYXNA
YnJhdWQtc2FudG9uaS5ldQAKCRCdT4gBDP4Z40nZD/4k98C6Rc8NiJ5QdlqVmoAH
cqVkX43TyCNBgRnWQLj9wACFbZG8KPmQL9b4eqp9bsrg0xfcRgbgBPZxyaempJIU
JRtefmNEQYy4dWfKt9qJmk9uPYvKpvMZrEST4xC1DG10qMPkgveIbTkcQoabHitX
xy9h3rPpUW+Po5u7f2gPwghhuE6SoNABti9+1SnAJqlts+MID7ssyJroPS80zor8
NHsVyiVBt1bKkf8fYNYVhX6xFgk4f+iZ5SxOlL47ybygpeyyNNh17L0KGAwHdGC1
4P3N1opGA9AgXHMqZCgMyPbWV6ox7dK2abdJPFUSUzr8CUpOSZ272xkIu+VMlr1q
+weQpFiPMGNgXCmzrMhMg8YAcmFwqQtqYZGmtqbVZgQagfAjS9cnd9EX8U6WdCU+
Di8fuQblEIKH9eVQMATusgRzeLAfe+lWXlNqvX24Ke11ePEZvc1TidCBYWvfkuTL
6KY9bnQsPqwabQn/vPPxTLvPMZWkROj2n1B7+lkgsUK7S1vxxKjR5FiH/4LSCMhS
t/lsS0q1VzpGtSre1jCrBbYkyZyppLFqqsl9WKigDMZMbmPS7iUN+rVhghzA7I/k
ohYKTveVc+wabISoTmCXnH+to5KnyDOnw2y54sJNfz1/8UNr+qiFHbO8ty/HynHP
8H4JjUoat7P1Ct8ODtBn2A==
=B6R9
-END PGP SIGNATURE-



Bug#881432: debian-policy: Please clarify postinst invocation upon first installation

2017-11-11 Thread Sean Whitton
control: tag -1 -patch

Hello again,

On Sat, Nov 11 2017, Christoph Biedl wrote:

> 6.5. Summary of ways maintainer scripts are called
>
> in the paragraph after
>
> "postinst configure most-recently-configured-version"
>
> Suggested wording:
>
> | If this package was prevously uninstalled, the
> | "most-recently-configured-version" string is empty.

Sorry, I spoke too soon.  I withdraw my second.  Currently we have:

> If there is no most recently configured version ``dpkg`` will pass a
> null argument.

This seems to cover your case, but maybe you don't think it's
sufficient?

Further, in dpkg terminology packages aren't "uninstalled" but they are
"removed".  So even if we make a change your wording would not be
advisable.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#876901: QFINDTESTDATA uses __FILE__

2017-11-11 Thread Adrian Bunk
Control: reassign -1 qtbase5-dev
Control: reassign 876917 qtbase5-dev
Control: reassign 876933 qtbase5-dev
Control: forcemerge -1 876917 876933
Control: retitle -1 QFINDTESTDATA uses __FILE__
Control: severity -1 normal
Control: affects -1 src:karchive src:ki18n src:kcodecs src:kparts
thanks

The problem is the following implementation in
/usr/include/x86_64-linux-gnu/qt5/QtTest/qtestcase.h:
# define QFINDTESTDATA(basepath)\
QTest::qFindTestData(basepath, __FILE__, __LINE__)

With the patched gcc in the unstable reproducible builds setting
__FILE__ to something other value, this does no longer find the
test data.

I do not really see any reason for blaming the users here for using
a documented public Qt API for accesssing test data in the source
directory:
  http://doc.qt.io/qt-5/qtest.html#QFINDTESTDATA

I've added reproducible-bui...@lists.alioth.debian.org to Cc for giving 
input what a reproducible and portable implementation might be for Qt.

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#881431: debian-policy: Clarify a version number is unique field

2017-11-11 Thread Sean Whitton
Hello,

On Sat, Nov 11 2017, Mattia Rizzolo wrote:

> There is another reuse that you haven't considered here: reusing a
> version (or even, a lower version) after a package has been removed
> from the archive (and here I mean, remove from all of oldoldstable,
> oldstable, stable, testing, unstable, experimental releases).  At that
> point dak doesn't know of it anymore and allows everything.
>
> TTBOMK that happened in the past several times.
>
> Do you want to forbid such "reuse" as well?

I think so.  There was a thread on -devel recently about the dangers of
reuse in such cases: users with the old package installed are not able
to switch to the new package.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#881404: unison: deleted archive file on other machine & manually resolved previously non-existant conflicts → works again

2017-11-11 Thread Axel Stammler
Package: unison
Version: 2.48.3-1
Followup-For: Bug #881404

Dear Maintainer,

The situation seems to be similar to the one in which Unison asks the user to 
remove the
archives. Unfortunately lots of files are now reported as conflicts whereas 
only a few
really are.

Regards,

Axel

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

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

Versions of packages unison depends on:
ii  libc6  2.24-11+deb9u1

Versions of packages unison recommends:
ii  openssh-client [ssh-client]  1:7.4p1-10+deb9u1

Versions of packages unison suggests:
pn  unison-all  

-- debconf-show failed



Bug#881449: fail2ban: postfix-sasl jail crashes on trying to ban ip address

2017-11-11 Thread Tomasz Ciolek
Package: fail2ban
Version: 0.9.6-2
Severity: important

Fail2ban postfix-sasl jail crashes when trying to ban an IP address: 

Failed to execute ban jail 'postfix-sasl' action 'iptables-multiport' info 
'CallingMap({'time': 1510389716.3446894, 'ip failures': . at 0x7fb8d058a950>, 'ipjailmatches': 
. at 0x7fb8d058a488>, 
'ipjailfailures': . at 
0x7fb8d058a510>, 'matches': 'Nov 11 19:41:40 celaeno postfix/smtpd[12912]: 
warning: unknown[85.183.39.75]: SASL LOGIN authentication failed: 
authentication failure\nNov 11 19:41:48 celaeno postfix/smtpd[12912]: warning: 
unknown[85.183.39.75]: SASL LOGIN authentication failed: authentication 
failure\nNov 11 19:41:55 celaeno postfix/smtpd[12912]: warning: 
unknown[85.183.39.75]: SASL LOGIN authentication failed: authentication 
failure', 'ipmatches': . at 
0x7fb8d0592378>, 'failures': 3, 'ip': '85.183.39.75'})': Error starting action

As a aresult postfix-sasl jail is not fucntiong correctly


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1), LANGUAGE=en_AU 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fail2ban depends on:
ii  init-system-helpers  1.48
ii  lsb-base 9.20161125
ii  python3  3.5.3-1

Versions of packages fail2ban recommends:
ii  iptables   1.6.0+snapshot20161117-6
ii  python 2.7.13-2
ii  python3-pyinotify  0.9.6-1
ii  python3-systemd233-1
ii  whois  5.2.17~deb9u1

Versions of packages fail2ban suggests:
ii  bsd-mailx [mailx]   8.1.2-0.20160123cvs-4
pn  monit   
ii  syslog-ng-core [system-log-daemon]  3.8.1-10

-- /etc/fail2ban/jail.local file: 

[postfix-sasl]
enabled  = true
port = smtp,ssmtp,imap2,imap3,imaps,pop3,pop3s
filter   = postfix-sasl
logpath  = /var/log/mail.log
bantime  = 86400
maxretry = 3
usedns = warn
findtime = 28800


-- Configuration Files:
/etc/logrotate.d/fail2ban changed:
/var/log/fail2ban.log {
   
rotate 52
weekly
dateext
compress
delaycompress
missingok
postrotate
fail2ban-client set logtarget /var/log/fail2ban.log >/dev/null
endscript
# If fail2ban runs as non-root it still needs to have write access
# to logfiles.
# create 640 fail2ban adm
create 640 root adm
}


-- no debconf information



Bug#861857: chromium: when posting an inaccessible file as part of a form submission chromium claims the remote site is not accessible

2017-11-11 Thread Michal Suchanek
Package: chromium
Version: 61.0.3163.100-1~deb9u1
Followup-For: Bug #861857

Hello,

The exact error message is:

This site can’t be reached

The webpage at http://paste.debian.net/ might be temporarily down or it
may have moved permanently to a new web address.
ERR_ACCESS_DENIED


which is the result of

echo Hello > test.txt

chmod 000 test.txt

upload test.txt as paste to paste.debian.net

This is also an issue with google-chrome.

Best regards

Michal


Bug#774453: zoo: directory traversal

2017-11-11 Thread Salvatore Bonaccorso
Control: severity -1 serious

Rationale: The package is currently without maintainer (QA
maintained) and has this open for several years. Thus either for
buster the issue is fixed or not included.

Alternatively, but has still high popcon, remove zoo from the archive?

Regards,
Salvatore



Bug#768536: youtube-dl: problems with BBC data

2017-11-11 Thread Dr. Axel Stammler
Hi,

Sorry, I can only run versions from Stable. The current Stable (Stretch) 
version is
2017.05.18.1-1, and, unfortunately, the problem persists without any change. I 
just tried
this:

youtube-dl --write-annotations --all-subs 
http://www.bbc.co.uk/iplayer/episode/b09bzxdz

Here are some messages:

[bbc.co.uk] b09bzxdz: Downloading video page
[bbc.co.uk] b09bzxdz: Downloading playlist JSON
[bbc.co.uk] b09bzxdc: Downloading media selection XML
[bbc.co.uk] b09bzxdc: Downloading captions
[bbc.co.uk] b09bzxdc: Downloading captions
[bbc.co.uk] b09bzxdc: Downloading captions
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading MPD manifest
[bbc.co.uk] b09bzxdc: Downloading MPD manifest
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading MPD manifest
[bbc.co.uk] b09bzxdc: Downloading MPD manifest
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[bbc.co.uk] b09bzxdc: Downloading m3u8 information
[info] Writing video annotations to: Reporting Scotland, Late News, 
10_11_2017-b09bzxdc.annotations.xml
WARNING: There are no annotations to write.
[info] Writing video subtitles to: Reporting Scotland, Late News, 
10_11_2017-b09bzxdc.en-GB.ttml
[dashsegments] Total fragments: 158
[download] Destination: Reporting Scotland, Late News,
10_11_2017-b09bzxdc.fstream-uk-iptv_streaming_concrete_combined_hd_mf_limelight_uk_dash_https-video=507.mp4

$ ls -al Reporting\ Scotland\,\ Late\ News\,\ 10_11_2017-b09bzxdc.*
-rw-r- 1 axel axel 0 Nov 11 22:10 Reporting Scotland, Late News, 
10_11_2017-b09bzxdc.annotations.xml
-rw-r- 1 axel axel 28487 Nov 11 22:11 Reporting Scotland, Late News, 
10_11_2017-b09bzxdc.en-GB.ttml
-rw-r- 1 axel axel 107105794 Nov 11 22:34 Reporting Scotland, Late News, 
10_11_2017-b09bzxdc.fstream-uk-iptv_streaming_concrete_combined_hd_mf_limelight_uk_dash_https-video=507.mp4.part
-rw-r- 1 axel axel   2129276 Nov 11 22:36 Reporting Scotland, Late News, 
10_11_2017-b09bzxdc.fstream-uk-iptv_streaming_concrete_combined_hd_mf_limelight_uk_dash_https-video=507.mp4.part-Frag48.part
-rw-r- 1 axel axel51 Nov 11 22:34 Reporting Scotland, Late News, 
10_11_2017-b09bzxdc.fstream-uk-iptv_streaming_concrete_combined_hd_mf_limelight_uk_dash_https-video=507.mp4.ytdl

As before, the XML file is empty. I enclose the subtitle file, which, again as 
before,
does not contain all subtitles.

HIH.

Regards,

Axel

On Wed 2014-12-03 22.40.54, Rogério Brito wrote:

> Is this problem still present with the youtube-dl package from unstable?

http://www.w3.org/ns/ttml; 
xmlns:tts="http://www.w3.org/ns/ttml#styling; 
xmlns:ttm="http://www.w3.org/ns/ttml#metadata; 
xmlns:ttp="http://www.w3.org/ns/ttml#parameter; 
xmlns:ebuttm="urn:ebu:tt:metadata" xmlns:ebutts="urn:ebu:tt:style" 
ttp:timeBase="media" ttp:cellResolution="32 15" xml:lang="en-GB">



urn:ebu:tt:distribution:2014-01
BBC
BBC Subtitle 
Converter v0.8.8


















Naomi Campbell speakingto our Arts Editor Will Gompertz.
Now on BBC One, its timefor the news where you are.
Good evening.
A 61-year-old Glasgow man claimshe suffered years of sexual
abuse and was trafficked by 
membersof a Catholic teaching order.
His claims include being rapedwhile on a school trip
to Manchester Unitedalmost 50 years ago.
The UKs National Crime Agency 
hasconcluded he is the victim
of modern slavery.
Our home affairs correspondent,Reevel Alderson has
this exclusive report.
In the late 1960s, these men madeOld Trafford the Theatre of dreams,
but for one Glasgow boy,it was a nightmare.
This council primary schoolin the East End of Glasgow is
very different from its 
predecessorin 

Bug#881447: new version 5.6.4 available

2017-11-11 Thread Emmanuel Bourg
Le 11/11/2017 à 22:46, W. Martin Borgert a écrit :

> Please consider packaging the new version. Thanks!

Hi Martin,

This is unlikely to happen unfortunately, see #803713 for more info.

Emmanuel Bourg



Bug#881448: python-eventlet fails to install on amd64: SyntaxError: invalid syntax

2017-11-11 Thread Adrian Bunk
Package: python-eventlet
Version: 0.20.0-1
Severity: grave

Preparing to unpack .../python-eventlet_0.20.0-1_all.deb ...
Unpacking python-eventlet (0.20.0-1) ...
Setting up python-eventlet (0.20.0-1) ...
  File "/usr/lib/python2.7/dist-packages/eventlet/green/http/client.py", line 
195
_is_legal_header_name = re.compile(rb'[^:\s][^:\r\n]*\Z').match
   ^
SyntaxError: invalid syntax

  File "/usr/lib/python2.7/dist-packages/eventlet/green/http/cookiejar.py", 
line 1269
yield from deepvalues(obj)
 ^
SyntaxError: invalid syntax

dpkg: error processing package python-eventlet (--configure):
 installed python-eventlet package post-installation script subprocess returned 
error exit status 101



Bug#881447: new version 5.6.4 available

2017-11-11 Thread W. Martin Borgert
Source: elasticsearch
Version: 1.7.5-1
Severity: wishlist

Please consider packaging the new version. Thanks!



Bug#881444: Install appstream metadate into /usr/share/metainfo/

2017-11-11 Thread Niels Thykier
Control: tags -1 moreinfo

On Sat, 11 Nov 2017 22:15:26 +0100 Jörg Frings-Fürst 
wrote:
> Package: debhelper
> Version: 10.10.5
> Severity: wishlist
>
> 
> Hello,
> 
> to prevent lintain warnings install appstream metadata into
> /usr/share/metainfo/ instead /usr/share/appdata/.
> 
> CU
> Jörg
> 
> 
> 
> [...]
Hi,

AFAICT, debhelper (itself) does not provide any tool to install
appstream metadata.

Are you certain this bug is filed against the correct package?

Thanks,
~Niels



Bug#862264: libvisual-0.4-dev is not Multi-Arch compatible

2017-11-11 Thread Manuel A. Fernandez Montecelo
2017-11-11 20:35 GMT+01:00 Eriberto :
> Hi Manuel and François,
>
> Sorry for my very long delay. Uploading...

That's great, thanks!


-- 
Manuel A. Fernandez Montecelo 



Bug#881326: re: Bug#881326: re: Bug#881326: mpv: The dependency of mpv should not be recommended, it must be sugerere

2017-11-11 Thread Debian/GNU
On Sat, 11 Nov 2017 15:08:33 +0100 (CET) pubcl  wrote:
> sorry, this is an error.
> 
> Youtube-dl should not depend on mpv and vice versa.>
>  
> 
> because youtube-dl is a downloader.
> 
> mpv is a player.


sure, but youtube-dl does not depend on mpv and mpv does not depend on
youtube-dl.
so there's no error here - problem solved.

(youtube-dl *recommends* mpv, and this is perfectly valid. Recommends is
for "packages that would be found together with this one in all but
unusual installations", and i think having a video-downloader installed
but not a player to view the downloaded videos is certainly an "unusual
installation")

gfasdnmr
IOhannes



signature.asc
Description: OpenPGP digital signature


Bug#881446: wine-development FTBFS on armel: configure: error: You need a target with floating point support to build Wine for ARM.

2017-11-11 Thread Adrian Bunk
Source: wine-development
Version: 2.21-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=wine-development=armel=2.21-1=1510429223=0

...
checking for cpp... cpp
checking for ld... ld
checking whether gcc supports Thumb... yes
checking whether gcc supports floating point... no
configure: error: You need a target with floating point support to build Wine 
for ARM.
debian/rules:112: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1


Unless this can be reverted, removing armel from the architecture list
and an RM bug against ftp.debian.org for removal of the stale old armel
packages is the way forward.



Bug#862328: Ping

2017-11-11 Thread Kim Gräsman
Hello,

I've been banging my head against this for a while, too.

>From what I can tell, Sylvain's original report is correct, there's no
way to use the Clang CMake modules in this packaging.

CMake can be convinced to find Clang with:

find_package(Clang REQUIRED CONFIG NAMES llvm Clang)

but even then it will fail with

 CMake Error at /usr/share/llvm-3.9/cmake/ClangConfig.cmake:16 (include):
  include could not find load file:

/usr/lib/cmake/clang/ClangTargets.cmake
Call Stack (most recent call first):
  CMakeLists.txt:34 (find_package)

The failing module, ClangConfig.cmake, does:

...
set(CLANG_CMAKE_DIR "${CLANG_INSTALL_PREFIX}/lib/cmake/clang")

# Provide all our library targets to users.
include("${CLANG_CMAKE_DIR}/ClangTargets.cmake")
...

This can never match ClangTargets.cmake's true location, which is just
next to ClangConfig.cmake, in /usr/share/llvm-3.9/cmake.

I haven't had a chance to investigate Sylvain's patch, or understand
what the root cause of the problem is (Clang or packaging), but I'll
try to dig deeper.

Cheers,
- Kim



Bug#881444: Install appstream metadate into /usr/share/metainfo/

2017-11-11 Thread Jörg Frings-Fürst
Package: debhelper
Version: 10.10.5
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

to prevent lintain warnings install appstream metadata into
/usr/share/metainfo/ instead /usr/share/appdata/.

CU
Jörg



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

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

Versions of packages debhelper depends on:
ii  autotools-dev20161112.1+nmu1
ii  binutils 2.29.1-6
ii  dh-autoreconf14
ii  dh-strip-nondeterminism  0.040-1
ii  dpkg 1.19.0.4
ii  dpkg-dev 1.19.0.4
ii  file 1:5.32-1
ii  libdpkg-perl 1.19.0.4
ii  man-db   2.7.6.1-2
ii  perl 5.26.1-2
ii  po-debconf   1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201608
pn  dwz  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAloHaG4ACgkQCfifPIyh
0l2QOBAApOFLjgXVrZo5xfCOnLXJugty2pazRzY5buMKm2eUb6Ll7tb9XFtNPf5g
pSSaHQPYTuYbU54TvoW7rmcOBjnA6FXUg+9JWEX2Xg5pYJNMeLozr+goNGHnohnV
Zd1mOVVU7AwI/RJs6uBbgEdA1SV8Ri7hYT7+TIOYChqrusUgyo82JQCI9OwEDgDe
+qo4VFGyiD0tffoaQAKGVUhw5Q5HLA2dYRmQH31gnS1Oy6t2yvRdqL8gRPEFuzNH
OjlweZutPr4HabJUrQ4uVcxAiMHgMU25K/TBktVnlR7Ghmr2oth+elPqF2TDAd7w
nz4IcPq6HWLq1io2nKagec01U41mdkVew9BtvC2MGKHFa38mjWuJzh10SOF5yN/f
qxFL9xBrMpBARnKzV7bRcxZcxZGEH3tCKWAbV9yYl7BrmCjp/lDu2dxYGctb10dX
oBhupvsuSi+vSpz88bTIfI5SLHtgd0e6zC5g4Xu784fOB9Wglxg5dEeAIOxNKYQ1
bVQfam1zzzxfQwrYb3wR3SQ/gSAY5ehBNiWxxS0JhWgV/+78dHoRWmTCdSnc0961
WgcAOtGjemk4p1qRYimnKEb+XQHMam4oGYQgVm7oo11ydBsa8yLOIow6yNB1YdIa
bCQ4msGs9XN/ycybHFtAQlKTa5pAroJlHH2NQTQY2Ebq4sF/Hjo=
=yRhZ
-END PGP SIGNATURE-


Bug#881445: ruby-ox: CVE-2017-15928: Segmentation fault in the parse_obj

2017-11-11 Thread Salvatore Bonaccorso
Source: ruby-ox
Version: 2.1.1-2
Severity: grave
Tags: security upstream
Forwarded: https://github.com/ohler55/ox/issues/194

Hi,

the following vulnerability was published for ruby-ox.

Rationale for RC severity: think the issue warrants to be adressed for
the next stable release. The issue itself possibly though does not
warrant a DSA on it's own for stretch and jessie.

CVE-2017-15928[0]:
| In the Ox gem 2.8.0 for Ruby, the process crashes with a segmentation
| fault when a crafted input is supplied to parse_obj. NOTE: the vendor
| has stated "Ox should handle the error more gracefully" but has not
| confirmed a security implication.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15928
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15928
[1] https://github.com/ohler55/ox/issues/194
[2] 
https://github.com/ohler55/ox/commit/e4565dbc167f0d38c3f93243d7a4fcfc391cbfc8

Regards,
Salvatore



Bug#873916: ITP: shoogle -- Access the Google API from the command line

2017-11-11 Thread David Steele
retitle 873916 ITP: shoogle -- Access the Google API from the command line
owner 873916 !
thanks

Packaging at https://github.com/davesteele/shoogle/tree/debian/debian

-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE


signature.asc
Description: GooPG digital signature


Bug#864927: Can we get a simple fix for #864927 into unstable/testing please?

2017-11-11 Thread Steve McIntyre
On Sat, Nov 11, 2017 at 03:25:29PM -0500, Lou Poppler wrote:
>This seems to be OK as of the weekly testing live build of Nov 5, 2017, with
>plasma-desktop-data (4:5.10.5-2)
>
>That live build boots OK here.

kde-l10n has been removed from testing, and that looks to have solved
the live build problem. Doesn't like the best of ways, maybe?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html



Bug#881443: fails to start with minimal dependencies from testing

2017-11-11 Thread Florian Klink

Package: puppetdb


Oct 10 23:14:49 puppet-db systemd[1]: Started Puppet data warehouse server.
Oct 10 23:14:57 puppet-db java[32440]: Exception in thread "main" 
java.lang.RuntimeException: No such var: cli/parse-opts, 
compiling:(puppetlabs/kitchensink/core.clj:867:52)


It seems some clojure related package versions in stretch are not compatible 
with this version of puppetdb.

I pinned libtools-cli-clojure (0.3.5-2 from sid), and got until the following:


clojure.lang.Compiler$CompilerException: java.lang.RuntimeException: No such 
var: sql/db-do-commands, compiling:(puppetlabs/puppetdb/jdbc.clj:38:3)


I pinned libjava-jdbc-clojure (0.7.0-1 from sid), and got util:


clojure.lang.Compiler$CompilerException: java.lang.RuntimeException: No such 
var: puppetlabs.trapperkeeper.services/this, 
compiling:(puppetlabs/puppetdb/command.clj:627:24)


However, it seems like all the libtrapperkeeper-* packages already are from
unstable now, and execution still fails.

dpkg -l

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version ArchitectureDescription
+++--===-===-=
ii  acpi-support-base0.142-8 all scripts for handling 
base ACPI events such as
ii  acpid1:2.0.28-1+b1   amd64   Advanced Configuration 
and Power Interface ev
ii  adduser  3.115   all add and remove users 
and groups
ii  ant  1.9.9-1 all Java based build tool 
like make
ii  ant-optional 1.9.9-1 all Java based build tool 
like make - optional li
ii  apt  1.4.8   amd64   commandline package 
manager
ii  apt-listchanges  3.10all package change history 
notification tool
ii  apt-transport-https  1.4.8   amd64   https download 
transport for APT
ii  apt-utils1.4.8   amd64   package management 
related utility programs
ii  augeas-lenses1.8.0-1+deb9u1  all Set of lenses needed 
by libaugeas0 to parse c
ii  base-files   9.9+deb9u2  amd64   Debian base system 
miscellaneous files
ii  base-passwd  3.5.43  amd64   Debian base system master password and group 
ii  bash 4.4-5   amd64   GNU Bourne Again SHell

ii  bash-completion  1:2.1-4.3   all programmable 
completion for the bash shell
ii  bind9-host   1:9.10.3.dfsg.P amd64   Version of 'host' 
bundled with BIND 9.X
ii  binutils 2.28-5  amd64   GNU assembler, linker 
and binary utilities
ii  bridge-utils 1.5-13+deb9u1   amd64   Utilities for configuring the Linux Ethernet 
ii  bsdmainutils 9.0.12+nmu1 amd64   collection of more utilities from FreeBSD

ii  bsdutils 1:2.29.2-1  amd64   basic utilities from 
4.4BSD-Lite
ii  busybox  1:1.22.0-19+b3  amd64   Tiny utilities for 
small and embedded systems
ii  bzip21.0.6-8.1   amd64   high-quality block-sorting file compressor - 
ii  ca-certificates  20161130+nmu1   all Common CA certificates

ii  ca-certificates-java 20170531+nmu1   all Common CA certificates 
(JKS keystore)
ii  console-setup1.164   all console font and 
keymap setup program
ii  console-setup-linux  1.164   all Linux specific part of 
console-setup
ii  coreutils8.26-3  amd64   GNU core utilities
ii  cpio 2.11+dfsg-6 amd64   GNU cpio -- a program 
to manage archives of f
ii  cpp  4:6.3.0-4   amd64   GNU C preprocessor 
(cpp)
ii  cpp-66.3.0-18amd64   GNU C preprocessor
ii  cron 3.0pl1-128+b1   amd64   process scheduling 
daemon
ii  cryptsetup   2:1.7.3-4   amd64   disk encryption 
support - startup scripts
ii  cryptsetup-bin   2:1.7.3-4   amd64   disk encryption 
support - command line tools
ii  curl 7.52.1-5+deb9u2 amd64   command line tool for transferring data with 
ii  dash 0.5.8-2.4   amd64   POSIX-compliant shell

ii  dbconfig-common  2.0.8   all framework that helps 
packages to manage datab
ii  dbconfig-pgsql   2.0.8   all dbconfig-common 
PostgreSQL support
ii  dbus 1.10.22-0+deb9u amd64   simple interprocess messaging system (daemon 
ii  debconf  1.5.61  all Debian configuration management system

ii  debconf-i18n 

Bug#877391: Please add apparmor profile

2017-11-11 Thread Michael Gilbert
control: tag -1 -patch

I would prefer a separate abstractions file and the other feedback
fixed before I consider applying this.

I also noticed that a similar file is already in apparmor-profiles.
Is that not sufficient?

Best wishes,
Mike



Bug#881053: ppp: fails to compile because of mistake in rules file

2017-11-11 Thread Chris Boot
On 07/11/17 14:48, Adrian Bunk wrote:
> On Tue, Nov 07, 2017 at 02:46:59PM +0100, Christian Blum wrote:
>> Package: ppp
>> Version: 2.4.7-1+4
>> Severity: serious
>> Tags: patch
>> Justification: fails to build from source (but built successfully in the 
>> past)
>>
>> Dear Maintainer,
>>
>> the rules file contains a problem that keeps ppp from compiling. This patch 
>> fixes the problem.
>>
>>
>> --- debian/rules.ORIG2017-11-07 14:43:08.026945955 +0100
>> +++ debian/rules 2017-11-07 14:43:20.174879455 +0100
>> @@ -156,7 +156,7 @@
>>  # the build fails if there are any discrepancies in the symbols file in 
>> order
>>  # to catch ABI changes.
>>  override_dh_makeshlibs:
>> -dh_makeshlibs --package=ppp -- -c2 -edebian/ppp/usr/sbin/pppd -V
>> +dh_makeshlibs --package=ppp -- -c2 -edebian/ppp/usr/sbin/pppd --version
>>  dh_makeshlibs --no-package=ppp
>> ...
> 
> -V looks correct, and it works everywhere else:
>   https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ppp.html
> 
> What is the exact error message you get?

Hi Christian, Adrian,

The -V comes after the '--' separator and thus should be an argument to
dpkg-gensymbols. Its meaning there is, according to the man page:

"Enable verbose mode. The generated symbols file contains deprecated
symbols as comments. Furthermore in template mode, pattern symbols are
followed by comments listing real symbols that have matched the pattern."

This is probably unnecessary for pppd in the general case but I don't
think it should do any harm. Replacing this with --version is definitely
not correct, however: that should make dpkg-gensymbols show its version
number and exit without producing any output. That would cause the build
to ignore changes in the symbols, which is exactly what this is there to
protect against.

Please let me know if this is causing unexpected build failures and I'll
try to help.

Best regards,
Chris

-- 
Chris Boot
bo...@boo.tc



Bug#880471: Touchpad doesn't work anymore

2017-11-11 Thread Chris Boot
On 11/11/17 19:44, Daniel Leidert wrote:
>> [  164.712261] psmouse serio1: synaptics: queried max coordinates: x 
>> [..5676], y [..4732]
>> [  164.759543] psmouse serio1: synaptics: queried min coordinates: x 
>> [1356..], y [1214..]
>> [  164.759556] psmouse serio1: synaptics: Trying to set up SMBus access
>> [  164.784566] rmi4_smbus 1-002c: registering SMbus-connected sensor
>> [  164.841110] rmi4_f01 rmi4-01.fn01: found RMI device, manufacturer: 
>> Synaptics, product: s3203_ver5, fw id: 1569351
>> [  164.903005] input: Synaptics s3203_ver5 as /devices/rmi4-01/input/input25

Hi Daniel,

This must definitely be because of the config options enabled recently
at my request: the rmi4_smbus module wasn't enabled until then. Perhaps
booting with 'psmouse.synaptics_intertouch=0' on the kernel command-line
can allow this to work normally for now?

Unfortunately I don't know enough about how this works to help much;
perhaps linux-in...@vger.kernel.org can help you further.

Ben / Debian kernel maintainers: perhaps this module would be better off
disabled, or this functionality disabled by default. Given that this
hasn't had the expected result on my X270 anyway that doesn't seem like
a bad option to me.

HTH,
Chris

-- 
Chris Boot
bo...@debian.org



Bug#881442: shotwell: Crashes when deleting all photos from an event

2017-11-11 Thread Manuel Bilderbeek
Package: shotwell
Version: 0.25.4+really0.24.5-0.1+b1
Severity: normal

Dear Maintainer,

I found some events with duplicate photos, so I deleted all photos in that
event. That caused the Shotwell window to disappear. I guess it crashed.

When I tried again running from gdb, I didn't get the crash anymore, just this
message:

(shotwell:28886): GLib-GObject-WARNING **: invalid unclassed pointer in cast to 
'Page'
L 28886 2017-11-11 21:47:36 [CRT] page_get_view: assertion 'IS_PAGE (self)' 
failed
L 28886 2017-11-11 21:47:36 [CRT] data_collection_contains: assertion 
'IS_DATA_COLLECTION (self)' failed

Each time I perform the action of deleting all photos in an event.

I have no idea why it didn't crash this time.

-- Package-specific info:

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

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

Versions of packages shotwell depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.0-1
ii  dbus-x11 [dbus-session-bus]   1.12.0-1
ii  dconf-cli 0.26.1-1
ii  libatk1.0-0   2.26.0-2
ii  libc6 2.24-17
ii  libcairo-gobject2 1.15.8-2
ii  libcairo2 1.15.8-2
ii  libexif12 0.6.21-4
ii  libgdk-pixbuf2.0-02.36.11-1
ii  libgee-0.8-2  0.20.0-1
ii  libgexiv2-2   0.10.6-1
ii  libglib2.0-0  2.54.1-1
ii  libgomp1  7.2.0-12
ii  libgphoto2-6  2.5.16-1
ii  libgphoto2-port12 2.5.16-1
ii  libgstreamer-plugins-base1.0-01.12.3-1
ii  libgstreamer1.0-0 1.12.3-1
ii  libgtk-3-03.22.24-3
ii  libgudev-1.0-0232-1
ii  libjavascriptcoregtk-4.0-18   2.18.2-1
ii  libjson-glib-1.0-01.4.2-2
ii  liblcms2-22.8-4
ii  libpango-1.0-01.40.12-1
ii  libpangocairo-1.0-0   1.40.12-1
ii  libraw16  0.18.5-1
ii  librsvg2-common   2.40.18-2
ii  libsoup2.4-1  2.60.2-1
ii  libsqlite3-0  3.21.0-1
ii  libstdc++67.2.0-12
ii  libwebkit2gtk-4.0-37  2.18.2-1
ii  libxml2   2.9.4+dfsg1-5+b1
ii  shotwell-common   0.25.4+really0.24.5-0.1

shotwell recommends no packages.

shotwell suggests no packages.

-- no debconf information



Bug#864927: Can we get a simple fix for #864927 into unstable/testing please?

2017-11-11 Thread Lou Poppler
This seems to be OK as of the weekly testing live build of Nov 5, 2017, with
plasma-desktop-data (4:5.10.5-2)

That live build boots OK here.

- Steve McIntyre  wrote:
> On Fri, Sep 15, 2017 at 06:15:08PM +0100, Steve McIntyre wrote:
> >It's blocking KDE live builds at the moment...
> 
> *tumbleweed*
> 
> Two months later, we still have no fix for this "closed" bug anywhere
> except experimental. Any chance of this being properly fixed soon?
> 
> -- 
> Steve McIntyre, Cambridge, UK.st...@einval.com
> "Arguing that you don't care about the right to privacy because you have
>  nothing to hide is no different than saying you don't care about free
>  speech because you have nothing to say."
>-- Edward Snowden
> 



Bug#881441: ITP: libaws-signature4-perl -- module to create a version4 signature for Amazon Web Services

2017-11-11 Thread Florian Schlichting
Package: wnpp
Owner: Florian Schlichting 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libaws-signature4-perl
  Version : 1.02
  Upstream Author : Lincoln Stein 
* URL : https://metacpan.org/release/AWS-Signature4
* License : Artistic-2.0 or GPL-1+
  Programming Lang: Perl
  Description : module to create a version4 signature for Amazon Web 
Services

AWS::Signature4 implements Amazon Web Service's Signature version 4
(http://docs.aws.amazon.com/general/latest/gr/signature-version-4.html).
It integrates with modules such as VM::EC2 or Amazon::SQS::Simple.

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

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.



Bug#881431: debian-policy: Clarify a version number is unique field

2017-11-11 Thread Mattia Rizzolo
On Sat, Nov 11, 2017 at 07:07:48PM +0100, Christoph Biedl wrote:
> Version number re-usage happens, probably always by accident. In the
> past, before the advent of slugs to mark security uploads and the like,
> this was more likely to happen, and a long time ago my src:file package
> was affected by that as well[1]. Unfortunately, there was such an event
> even in 2017, see #876633.

There is another reuse that you haven't considered here: reusing a
version (or even, a lower version) after a package has been removed
from the archive (and here I mean, remove from all of oldoldstable,
oldstable, stable, testing, unstable, experimental releases).  At that
point dak doesn't know of it anymore and allows everything.

TTBOMK that happened in the past several times.

Do you want to forbid such "reuse" as well?

> So I'd like to suggest an addition to "3.2. The version of a package",
> for clarification, wording in the simplest form:
> 
> | For any package, a version number must never be re-used.
> 
> What I'd like to express but I guess is a bit too long:
> 
> | Unless bitwise identical, no two files that share the base name and
> | have a version number in it may exist anywhere in the archives, ever.

That's all good and nice, but it requires some techinical block on the
archive software for it not to happen.

> Also I feel a temptation to implement an according check in the
> auto-reject machinery at ftp-master. But that's for another day.

Personally I believe that should come *before* having it in policy.

-- 
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#881432: debian-policy: Please clarify postinst invocation upon first installation

2017-11-11 Thread Mattia Rizzolo
On Sat, Nov 11, 2017 at 07:08:41PM +0100, Christoph Biedl wrote:
> 6.5. Summary of ways maintainer scripts are called
> 
> in the paragraph after
> 
> "postinst configure most-recently-configured-version"
> 
> Suggested wording:
> 
> | If this package was prevously uninstalled, the
> | "most-recently-configured-version" string is empty.

Seconded.

> Reading src/configure.c in dpkg, this should be technically correct.

Isn't there some dpkg manpage or document also nicely documenting this
somewhere?  I know guillem went to great effort of documenting how dpkg
behaves.

-- 
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#880990: widelands: Segmentation fault on loading a game

2017-11-11 Thread Elena ``of Valhalla''
On 2017-11-11 at 19:38:55 +0100, Markus Koschany wrote:
> thank you for reporting this issue. I can confirm that widelands
> segfaults in Testing. After some investigation I have found out that
> libsdl2 in Testing is the root cause for this problem and widelands is
> only affected. I can't reproduce it with the latest version in Sid
> though hence I'm going to mark this issue as fixed in libsdl2 version
> 2.0.7+dfsg1-3.

I've installed the version of libsdl2-2.0-0 from sid on my testing and I
can confirm that the issue is fixed and widelands is running again.

Thanks!

-- 
Elena ``of Valhalla''



Bug#881432: debian-policy: Please clarify postinst invocation upon first installation

2017-11-11 Thread Sean Whitton
control: -1 +patch

Hello Christoph,

On Sat, Nov 11 2017, Christoph Biedl wrote:

> 6.5. Summary of ways maintainer scripts are called
>
> in the paragraph after
>
> "postinst configure most-recently-configured-version"
>
> Suggested wording:
>
> | If this package was prevously uninstalled, the
> | "most-recently-configured-version" string is empty.

Seconded.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#881431: debian-policy: Clarify a version number is unique field

2017-11-11 Thread Sean Whitton
Hello Christoph,

On Sat, Nov 11 2017, Christoph Biedl wrote:

> So I'd like to suggest an addition to "3.2. The version of a package",
> for clarification, wording in the simplest form:
>
> | For any package, a version number must never be re-used.
>
> What I'd like to express but I guess is a bit too long:
>
> | Unless bitwise identical, no two files that share the base name and
> | have a version number in it may exist anywhere in the archives,
> | ever.

Slight wrinkle here: epochs are not included in filenames.  So we might
have both foo_1.1.dsc and foo_1.1.dsc where one has version 1:1.1 and
the other has version 2:1.1.

> PS: Aside, I like the new presentation format of the policy document
> as seen in . Improved
> visual, policy version number at the very beginning, maintainer script
> flowcharts, upgrading checklist included, but no additional and
> dangerous requirements for using the document (i.e. works fine without
> JavaScript). Much appreciated.

Thanks!

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#881440: RM: linthesia -- RoQA; not in stable, FTBFS

2017-11-11 Thread Adrian Bunk
Package: ftp.debian.org
Severity: normal

linthesia has a non-trivial FTBFS bug (#835117)
that already prevented inclusion in stretch.

linthesia is orphaned since 2016 and dead upstream since 2014.



Bug#880471: Touchpad doesn't work anymore

2017-11-11 Thread Daniel Leidert
Am Samstag, den 11.11.2017, 20:44 +0100 schrieb Daniel Leidert:
[..]

> rmmod psmouse
> modprobe psmouse synaptics_intertouch=1
> 
> > [  164.712261] psmouse serio1: synaptics: queried max coordinates: x 
> > [..5676], y [..4732]
> > [  164.759543] psmouse serio1: synaptics: queried min coordinates: x 
> > [1356..], y [1214..]
> > [  164.759556] psmouse serio1: synaptics: Trying to set up SMBus access
> > [  164.784566] rmi4_smbus 1-002c: registering SMbus-connected sensor
> > [  164.841110] rmi4_f01 rmi4-01.fn01: found RMI device, manufacturer: 
> > Synaptics, product: s3203_ver5, fw id: 1569351
> > [  164.903005] input: Synaptics s3203_ver5 as /devices/rmi4-01/input/input25
>
> I every case the touchpad works.

I've found (of course after sending the mail) that this only works
after loading the module. The touchpad stops working as soon as my use
my Logitech mouse connected via USB is used. Then the touchpad doesn't
react anymore.

Regards, Daniel



Bug#880669: irony-mode: tests do not reliably pass for several archs

2017-11-11 Thread Nicholas D Steeves
On Fri, Nov 10, 2017 at 04:53:50PM -0500, Aaron M. Ucko wrote:
> Nicholas D Steeves  writes:
> 
> > I've uploaded irony-mode_1.2.0-2~exp1_amd64.  I'm giving LLVM+Clang a
> > try with the new package, as I've read that MacOS users must use Clang
> > rather than GCC...and I suspect that switching to LLVM+Clang might
> > close this bug (hypothesis: error on mips64 and arm64 only exists when
> > building with GCC).  Also, I suspect that upstream intends
> > irony-server to be compiled with clang ;-)
> 
> Interesting idea.
> 
> This change does seem to have helped for arm64, but the jury's still out
> on mips64el.  However, I see new failures on amd64 and s390x, and builds
> for many architectures (albeit all non-release ones) can no longer even
> start because clang is unavailable there.  As such, I'd recommend
> building with (and build-depending on) clang only on those architectures
> on which GCC builds hit errors.

Unfortunately the transition to libclang-5.0-dev (libclang-dev is a
necessary dependency for irony-mode) requested by the Debian
LLVM/Clang will leave non-release archs in limbo even with GCC.  I
believe the two outcomes are 1) libclang-5.0-dev gains support for
these arches 2) the porter downgrades the libclang-5.0-dev dependency
to the latest version supported by the arch.

I like your recommendation.  If mip64el still fails with the upstream
patch then I'll special-case it to build with Clang.

> On the Mac front, Clang has indeed been the only compiler Apple's
> official Development Tools package supports for years (briefly preceded
> by LLVM GCC), but GCC does still support the platform and is available
> through third-party package managers such as Fink.

Ahhh.  I wonder if a Fink-packaged-GCC-compiled on a modern MacOS
would use symbols from both libgcc (eg: libgcc_s.so.1) and llvm+clang
(I can't check at the moment)?  Depends on the libclang-5.0.so.1
dynamic library is certain, in any case, and I wonder if a
Fink-packaged libclang-5.0.so.1 that links with libgcc_s.so.1
instead of (the llvm+clang runtime lib) would be required?

> At any rate, thanks for looking into the errors!

You're welcome :-)  I've prepared an upload for unstable and will
upload as soon as mips64el and mipsel builds & self-test report
success for ~exp2 (compiled with GCC instead of Clang).  I hope these
archs will not need to be special-cased!

https://buildd.debian.org/status/package.php?p=irony-mode=experimental

Cheers,
Nicholas


signature.asc
Description: PGP signature


Bug#881124: shadow.ind.ntou.edu.tw: request name change, and add as candidate of ftp.tw

2017-11-11 Thread Medical Wei
It was a manual sync due to the discovery of the error during sync when
receiving push.

Cron job for Debian disabled.
Bastian Blank 於 2017年11月12日 週日,01:53寫道:

> On Wed, Nov 08, 2017 at 02:08:38PM +0100, Bastian Blank wrote:
> > On Wed, Nov 08, 2017 at 10:24:51AM +0800, Yao Wei wrote:
> > > I would like to change the name of the server shadow.ind.ntou.edu.tw
> to
> > > ftp.ntou.edu.tw,
> > Okay.
>
> I see some weird behaviour.  At 2017-11-09 21:25:03 we picked up a
> Archive-Update-in-Progress file with timestamp 2017-11-09 21:24:58.
> It disappeared, but the trace file was updated _five hours_ later at
> 2017-11-10 02:40:00.
>
> Please show the ftpsync log for this mirror sync run, as this timestamps
> do not add up.
>
> Bastian
>
> --
> There is a multi-legged creature crawling on your shoulder.
> -- Spock, "A Taste of Armageddon", stardate 3193.9
>


Bug#880471: Touchpad doesn't work anymore

2017-11-11 Thread Daniel Leidert
Am Samstag, den 11.11.2017, 20:15 +0100 schrieb Daniel Leidert:
> Am Samstag, den 11.11.2017, 10:32 + schrieb Chris Boot:
> 
> [..]
> > I wonder if this is somehow related to #875621 where I asked for
> > some
> > additional options to be enabled. Daniel, could you please include
> > a
> > full dmesg output from the 4.13 kernel? In particular I’m looking
> > for
> > lines containing “psmouse” or “rmi4”.
> 
> Attached. In second 34.7 I attached an external mouse. You can ignore
> it. The system is a Lenovo Thinkpad Yoga 11e.
> 
> If you need anything else, please let me know.

I found a "fix". Doing an

rmmod psmouse
modprobe psmouse

fixes the issue. I also tried setting synaptics_intertouch and got
this:

rmmod psmouse
modprobe psmouse

> [   94.525393] psmouse serio1: synaptics: queried max coordinates: x 
> [..5676], y [..4732]
> [   94.571321] psmouse serio1: synaptics: queried min coordinates: x 
> [1356..], y [1214..]
> [   94.669301] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 
> 0x1e2b1, caps: 0xd00123/0x840300/0x12e800/0x0, board id: 2980, fw id: 1569351
> [   94.731729] input: SynPS/2 Synaptics TouchPad as 
> /devices/platform/i8042/serio1/input/input20

rmmod psmouse
modprobe psmouse synaptics_intertouch=0

> [  159.262411] psmouse serio1: synaptics: queried max coordinates: x 
> [..5676], y [..4732]
> [  159.311809] psmouse serio1: synaptics: queried min coordinates: x 
> [1356..], y [1214..]
> [  159.405369] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 
> 0x1e2b1, caps: 0xd00123/0x840300/0x12e800/0x0, board id: 2980, fw id: 1569351
> [  159.466244] input: SynPS/2 Synaptics TouchPad as 
> /devices/platform/i8042/serio1/input/input22

rmmod psmouse
modprobe psmouse synaptics_intertouch=1

> [  164.712261] psmouse serio1: synaptics: queried max coordinates: x 
> [..5676], y [..4732]
> [  164.759543] psmouse serio1: synaptics: queried min coordinates: x 
> [1356..], y [1214..]
> [  164.759556] psmouse serio1: synaptics: Trying to set up SMBus access
> [  164.784566] rmi4_smbus 1-002c: registering SMbus-connected sensor
> [  164.841110] rmi4_f01 rmi4-01.fn01: found RMI device, manufacturer: 
> Synaptics, product: s3203_ver5, fw id: 1569351
> [  164.903005] input: Synaptics s3203_ver5 as /devices/rmi4-01/input/input25

I every case the touchpad works. So there is something going wrong in
booting phase. There is says:

> [3.292713] psmouse serio1: synaptics: queried max coordinates: x 
> [..5676], y [..4732]
> [3.340327] psmouse serio1: synaptics: queried min coordinates: x 
> [1356..], y [1214..]
> [3.340352] psmouse serio1: synaptics: Trying to set up SMBus access

Is there anything I have to load first, before psmouse?

HTH and regards, Daniel



Bug#852944: chromium: Poor font rendering

2017-11-11 Thread Michael Gilbert
On Sun, Nov 5, 2017 at 5:59 PM, Michael Gilbert wrote:
> control: tag -1 moreinfo
>
>> Chromium renders the body text on vox.com poorly. Vertical strokes in
>> the 'T' and 'e' characters among others are too thick. Changing the text
>> zoom size makes everything look fine. Attached is a test case and
>> screenshot.
>
> This works well in chromium 62 for me.  Can you provide more info
> about the font configuration on your system if its still a problem?

One thing to try, chromium recommends fonts-liberation, but doesn't
depend on it.  If you don't have it installed, would you mind adding
it?

Here is an upstream bug about missing fonts-liberation with the
internal pdf viewer, I suppose this could be a more general version of
that problem:
http://crbug.com/369991

Best wishes,
Mike



Bug#881425: linux-image-4.13.0-1-amd64: "rm -rf " fails with ENOTEMPTY (Directory not empty)

2017-11-11 Thread Ben Hutchings
On Sat, 2017-11-11 at 16:53 +0100, Philipp Marek wrote:
> Package: src:linux
> Version: 4.13.4-2
> Severity: normal
[...]

Can you try the newer version in unstable?

Ben.

-- 
Ben Hutchings
Who are all these weirdos? - David Bowie, reading IRC for the first
time



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


Bug#862264: libvisual-0.4-dev is not Multi-Arch compatible

2017-11-11 Thread Eriberto
Hi Manuel and François,

Sorry for my very long delay. Uploading...

Regards,

Eriberto


2017-11-11 9:11 GMT-02:00 Manuel A. Fernandez Montecelo
:
> Oi Eriberto (and François),
>
> 2017-05-10 13:39 Francois Gouget:
>>
>> Package: libvisual-0.4-dev
>> Version: 0.4.0-10
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> The amd64 version conflicts with the i386 one which makes it impossible
>> to install both. As a result one is forced to chose between developing
>> 32 bit or 64 bit applications.
>
>
> As far as I can tell, the only missing bit is to add "Multi-Arch: same"
> to the section of the -dev package in debian/control.
>
> Do you have any plans to address this soon?
>
> If not, do you mind if I NMU the package and push to the repo in
> collab-maint?
>
>
> Cheers.
> --
> Manuel A. Fernandez Montecelo 



Bug#880990: Qualify for Natural Pain Relief! See How NrXe

2017-11-11 Thread Cecil Riggenbach
Do you got weed

On Nov 11, 2017 2:13 PM, "Living With Pain"  wrote:

> Welcome To LivingWithPain.org
>
> 
>
> 
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Your message dated Sat, 11 Nov 2017 19:38:55 +0100 with message-id and
> subject line Re: Bug#880990: widelands: Segmentation fault on loading a
> game has caused the Debian Bug report #880990, regarding widelands:
> Segmentation fault on loading a game to be marked as done. This means that
> you claim that the problem has been dealt with. If this is not the case it
> is now your responsibility to reopen the Bug report if necessary, and/or
> fix the problem forthwith. (NB: If you are a system administrator and have
> no idea what this message is talking about, this may indicate a serious
> mail system misconfiguration somewhere. Please contact
> ow...@bugs.debian.org immediately.) -- 880990:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880990 Debian Bug
> Tracking System Contact ow...@bugs.debian.org with problems
>
> -- Forwarded message --
> From: "Elena ``of Valhalla''" 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Mon, 06 Nov 2017 19:25:27 +0100
> Subject: widelands: Segmentation fault on loading a game
> Package: widelands
> Version: 1:19+repack-4
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> I have installed widelands on a buster amd64 system and found the sad
> surprise that it is no longer working: opening any game (tutorial,
> campaign or game) results in a segfault with the attached output.
> I didn't try multiplayer games.
>
> Originally I tried with an existing ~/.widelands directory, but I moved
> it away and could still reproduce the behaviour.
>
> Please let me know if there is any other information I can provide: I
> have all of the free time saved by not playing widelands that I can use
> to help investigate this issue :)
>
> The following are the last few lines of ``strace widelands``:
>
> [ENOENT on files in ~/.widelands as far as my eyesbdwabacklog can see]
> 
> stat("/usr/share/games/widelands/data/world/critters/fox/fox_walk_nw_20.png",
> 0x7ffe463be940) = -1 ENOENT (No such file or directory)
> stat("/home/valhalla/.widelands/sound/animals", 0x7ffe463be220) = -1
> ENOENT (No such file or directory)
> stat("/usr/share/games/widelands/data/sound/animals",
> {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
> open("/home/valhalla/.widelands/sound/animals", 
> O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC)
> = -1 ENOENT (No such file or directory)
> open("/usr/share/games/widelands/data/sound/animals",
> O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 18
> fstat(18, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
> getdents(18, /* 46 entries */, 32768)   = 1488
> getdents(18, /* 0 entries */, 32768)= 0
> close(18)   = 0
> stat("/home/valhalla/.widelands/sound/animals/coyote_01.ogg",
> 0x7ffe463be170) = -1 ENOENT (No such file or directory)
> stat("/usr/share/games/widelands/data/sound/animals/coyote_01.ogg",
> {st_mode=S_IFREG|0644, st_size=29348, ...}) = 0
> stat("/usr/share/games/widelands/data/sound/animals/coyote_01.ogg",
> {st_mode=S_IFREG|0644, st_size=29348, ...}) = 0
> open("/usr/share/games/widelands/data/sound/animals/coyote_01.ogg",
> O_RDONLY) = 18
> fstat(18, {st_mode=S_IFREG|0644, st_size=29348, ...}) = 0
> fstat(18, {st_mode=S_IFREG|0644, st_size=29348, ...}) = 0
> lseek(18, 28672, SEEK_SET)  = 28672
> read(18, 
> "\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1"...,
> 676) = 676
> lseek(18, 0, SEEK_SET)  = 0
> read(18, 
> "OggS\0\2\0\0\0\0\0\0\0\0\320S(t\0\0\0\0006~\352\315\1\36\1vor"...,
> 28672) = 28672
> read(18, 
> "\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1"...,
> 4096) = 676
> close(18)   = 0
> brk(0x55fb3b0f8000) = 0x55fb3b0f8000
> mmap(NULL, 33329152, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
> -1, 0) = 0x7f5e59837000
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
> si_addr=0x7ffe463c5000} ---
> +++ killed by SIGSEGV +++
> Segmentation fault
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores)
> 

Bug#881433: maven: /usr/share/maven/boot/plexus-classworlds-2.x.jar should point to /usr/share/java/plexus-classworlds.jar

2017-11-11 Thread Emmanuel Bourg
Le 11/11/2017 à 19:26, Miguel Landaeta a écrit :

> However, maven switched its dependency to libplexus-classworlds-java,
> so this causes a dangling pointer and breaks maven unless you have
> installed both libplexus-classworlds-java packages.

Thank you Miguel! You can even remove the 2.x suffix from the symlink.
Feel free to upload the update.

Emmanuel Bourg



Bug#880990: Qualify for Natural Pain Relief! See How ImvY

2017-11-11 Thread John Cantu
STOP

On Nov 11, 2017 1:13 PM, "Living With Pain"  wrote:

> Welcome To LivingWithPain.org
>
> 
>
> 
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Your message dated Sat, 11 Nov 2017 19:38:55 +0100 with message-id and
> subject line Re: Bug#880990: widelands: Segmentation fault on loading a
> game has caused the Debian Bug report #880990, regarding widelands:
> Segmentation fault on loading a game to be marked as done. This means that
> you claim that the problem has been dealt with. If this is not the case it
> is now your responsibility to reopen the Bug report if necessary, and/or
> fix the problem forthwith. (NB: If you are a system administrator and have
> no idea what this message is talking about, this may indicate a serious
> mail system misconfiguration somewhere. Please contact
> ow...@bugs.debian.org immediately.) -- 880990:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880990 Debian Bug
> Tracking System Contact ow...@bugs.debian.org with problems
>
> -- Forwarded message --
> From: "Elena ``of Valhalla''" 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Mon, 06 Nov 2017 19:25:27 +0100
> Subject: widelands: Segmentation fault on loading a game
> Package: widelands
> Version: 1:19+repack-4
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> I have installed widelands on a buster amd64 system and found the sad
> surprise that it is no longer working: opening any game (tutorial,
> campaign or game) results in a segfault with the attached output.
> I didn't try multiplayer games.
>
> Originally I tried with an existing ~/.widelands directory, but I moved
> it away and could still reproduce the behaviour.
>
> Please let me know if there is any other information I can provide: I
> have all of the free time saved by not playing widelands that I can use
> to help investigate this issue :)
>
> The following are the last few lines of ``strace widelands``:
>
> [ENOENT on files in ~/.widelands as far as my eyesbdwabacklog can see]
> 
> stat("/usr/share/games/widelands/data/world/critters/fox/fox_walk_nw_20.png",
> 0x7ffe463be940) = -1 ENOENT (No such file or directory)
> stat("/home/valhalla/.widelands/sound/animals", 0x7ffe463be220) = -1
> ENOENT (No such file or directory)
> stat("/usr/share/games/widelands/data/sound/animals",
> {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
> open("/home/valhalla/.widelands/sound/animals", 
> O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC)
> = -1 ENOENT (No such file or directory)
> open("/usr/share/games/widelands/data/sound/animals",
> O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 18
> fstat(18, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
> getdents(18, /* 46 entries */, 32768)   = 1488
> getdents(18, /* 0 entries */, 32768)= 0
> close(18)   = 0
> stat("/home/valhalla/.widelands/sound/animals/coyote_01.ogg",
> 0x7ffe463be170) = -1 ENOENT (No such file or directory)
> stat("/usr/share/games/widelands/data/sound/animals/coyote_01.ogg",
> {st_mode=S_IFREG|0644, st_size=29348, ...}) = 0
> stat("/usr/share/games/widelands/data/sound/animals/coyote_01.ogg",
> {st_mode=S_IFREG|0644, st_size=29348, ...}) = 0
> open("/usr/share/games/widelands/data/sound/animals/coyote_01.ogg",
> O_RDONLY) = 18
> fstat(18, {st_mode=S_IFREG|0644, st_size=29348, ...}) = 0
> fstat(18, {st_mode=S_IFREG|0644, st_size=29348, ...}) = 0
> lseek(18, 28672, SEEK_SET)  = 28672
> read(18, 
> "\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1"...,
> 676) = 676
> lseek(18, 0, SEEK_SET)  = 0
> read(18, 
> "OggS\0\2\0\0\0\0\0\0\0\0\320S(t\0\0\0\0006~\352\315\1\36\1vor"...,
> 28672) = 28672
> read(18, 
> "\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1\1"...,
> 4096) = 676
> close(18)   = 0
> brk(0x55fb3b0f8000) = 0x55fb3b0f8000
> mmap(NULL, 33329152, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
> -1, 0) = 0x7f5e59837000
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
> si_addr=0x7ffe463c5000} ---
> +++ killed by SIGSEGV +++
> Segmentation fault
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores)
> Locale: 

Bug#880471: Touchpad doesn't work anymore

2017-11-11 Thread Daniel Leidert
Am Samstag, den 11.11.2017, 10:32 + schrieb Chris Boot:

[..]
> I wonder if this is somehow related to #875621 where I asked for some
> additional options to be enabled. Daniel, could you please include a
> full dmesg output from the 4.13 kernel? In particular I’m looking for
> lines containing “psmouse” or “rmi4”.

Attached. In second 34.7 I attached an external mouse. You can ignore
it. The system is a Lenovo Thinkpad Yoga 11e.

If you need anything else, please let me know.

HTH and regards, Daniel[0.00] random: get_random_bytes called from start_kernel+0x3d/0x456 with crng_init=0
[0.00] Linux version 4.13.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 6.4.0 20171026 (Debian 6.4.0-9)) #1 SMP Debian 4.13.10-1 (2017-10-30)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.13.0-1-amd64 root=UUID=60132919-d963-4d39-aaa5-42110dd8c247 ro quiet
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x00057fff] usable
[0.00] BIOS-e820: [mem 0x00058000-0x00058fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x00059000-0x0008bfff] usable
[0.00] BIOS-e820: [mem 0x0008c000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x0010-0x1fff] usable
[0.00] BIOS-e820: [mem 0x2000-0x200f] reserved
[0.00] BIOS-e820: [mem 0x2010-0x77f47fff] usable
[0.00] BIOS-e820: [mem 0x77f48000-0x78047fff] type 20
[0.00] BIOS-e820: [mem 0x78048000-0x79087fff] reserved
[0.00] BIOS-e820: [mem 0x79088000-0x79287fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x79288000-0x792c7fff] ACPI data
[0.00] BIOS-e820: [mem 0x792c8000-0x79ff] usable
[0.00] BIOS-e820: [mem 0xe00f8000-0xe00f8fff] reserved
[0.00] BIOS-e820: [mem 0xfed01000-0xfed01fff] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00027fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.31 by Phoenix Technologies Ltd.
[0.00] efi:  ACPI=0x792c7000  ACPI 2.0=0x792c7014  SMBIOS=0x79087000  ESRT=0x78884000 
[0.00] random: fast init done
[0.00] SMBIOS 2.7 present.
[0.00] DMI: LENOVO 20DA001CUK/Intel powered classmate PC, BIOS N15ET71W (1.31) 09/14/2017
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x28 max_arch_pfn = 0x4
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 0FFC0 mask FFFC0 write-protect
[0.00]   1 base 0 mask F8000 write-back
[0.00]   2 base 07C00 mask FFC00 uncachable
[0.00]   3 base 07A00 mask FFE00 uncachable
[0.00]   4 base 1 mask F write-back
[0.00]   5 base 2 mask F8000 write-back
[0.00]   6 disabled
[0.00]   7 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] e820: last_pfn = 0x7a000 max_arch_pfn = 0x4
[0.00] esrt: Reserving ESRT space from 0x78884000 to 0x78884038.
[0.00] Base memory trampoline at [a0cdc006] 6 size 24576
[0.00] BRK [0x20c557000, 0x20c557fff] PGTABLE
[0.00] BRK [0x20c558000, 0x20c558fff] PGTABLE
[0.00] BRK [0x20c559000, 0x20c559fff] PGTABLE
[0.00] BRK [0x20c55a000, 0x20c55afff] PGTABLE
[0.00] BRK [0x20c55b000, 0x20c55bfff] PGTABLE
[0.00] BRK [0x20c55c000, 0x20c55cfff] PGTABLE
[0.00] BRK [0x20c55d000, 0x20c55dfff] PGTABLE
[0.00] BRK [0x20c55e000, 0x20c55efff] PGTABLE
[0.00] BRK [0x20c55f000, 0x20c55] PGTABLE
[0.00] Secure boot could not be determined
[0.00] RAMDISK: [mem 0x3583d000-0x36c15fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x792C7014 24 (v02 LENOVO)
[0.00] ACPI: XSDT 0x792C7170 B4 (v01 LENOVO TP-N15   1310 PTEC 0002)
[0.00] ACPI: FACP 0x792C4000 00010C (v05 PTEC   OEMTABLE 0003 VLV2 010D)
[0.00] ACPI: DSDT 0x792B1000 00E623 (v02 PTEC   OEMTABLE 0003 VLV2 010D)
[0.00] ACPI: FACS 0x791FC000 40
[0.00] ACPI: FACS 0x791FC000 40
[0.00] ACPI: SLIC 0x792C6000 000176 (v01 LENOVO TP-N15   1310 PTEC 0002)
[0.00] ACPI: UEFI 0x792C5000 42 (v01 

Bug#881439: xombrero: no scrolling with mouse wheel

2017-11-11 Thread Dimitri
Package: xombrero
Version: 2:1.6.4-3+b2
Severity: important

Dear Maintainer,

I installed xombrero browser and i can see any pages, but i can't
scroll pages by mouse wheel. I can click into scrollbar and drag the
thumb, but wheel doesn't work. In other applications it's not a problem - 
i can scroll by wheel in terminal, in Firefox etc... 

I use just fvwm (fvwm-crystal - the window manager) together with
xserver-xorg - everything is from standard distribution, no custom
packets. It's a totally new system - it's a notebook I bought a week ago.

I checked man xombrero, but didn't find any special options for mouse
handling.

Please, help me.

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

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

Versions of packages xombrero depends on:
ii  libbsd0 0.8.3-1
ii  libc6   2.24-11+deb9u1
ii  libgdk-pixbuf2.0-0  2.36.5-2+deb9u1
ii  libglib2.0-02.50.3-2
ii  libgnutls30 3.5.8-5+deb9u3
ii  libgtk-3-0  3.22.24-3
ii  libjavascriptcoregtk-3.0-0  2.4.11-3
ii  libpango-1.0-0  1.40.5-1
ii  libsoup2.4-12.56.0-2+deb9u1
ii  libwebkitgtk-3.0-0  2.4.11-3

xombrero recommends no packages.

xombrero suggests no packages.

-- no debconf information



Bug#881438: activity-log-manager: Missing dependency against python-zeitgeist

2017-11-11 Thread Laurent Bigonville
Package: activity-log-manager
Version: 0.8.0-1.1
Severity: serious
File: /usr/bin/activity-log-manager

Hi,

It seems that activity-log-manager is missing a dependecy against 
python-zeitgeist

/usr/bin/activity-log-manager fails to start if the package is not
installed

Regards,

Laurent Bigonville

-- System Information:
Debian Release: buster/sid
  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.14.0-rc8+ (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages activity-log-manager depends on:
ii  python  2.7.14-1
ii  python-cairo1.8.8-2.2
ii  python-gtk2 2.24.0-5.1
ii  zeitgeist-core  1.0-0.1

activity-log-manager recommends no packages.

activity-log-manager suggests no packages.

-- no debconf information



Bug#881437: aggregate can't handle all CIDR input correctly

2017-11-11 Thread Lonesome Walker
Package: aggregate
Version: 1.6-7
(/var/lib/apt/lists/cdn.debian.net_debian_dists_jessie_main_binary-amd64_Pac
kages)
MD5: f997a857d65d21bbf877320588a8a99c


When using aggregate to simplify an CIDR list, aggregate tries to understand
the submitted subnets; unfortunately it doesn't do well.

For example:
curl -s
'https://stat.ripe.net/data/ris-prefixes/data.json?list_prefixes=true
ce=16276' | jq -r '.data.prefixes.v4.originating' | sed
'1d;$d;s/"//g;s/,//g;s/ //g' | aggregate

This fetches the ipv4 addresses from OVH and outputs them as needed to
stdout.
When piping this to aggregate, well see the errors yourself...

At first i thought, i was too stupid to "sed" the list, but then i realized:
176.31.188/22 becomes 176.31.0.188/22
which is false.

Consider this as a bug, since 176.31.188/22 is a valid CIDR.


Using the latest Debian Jessie, bug is FIXED in Debian Stretch.



Bug#881436: RM: gnome-sushi/experimental -- RoM; cruft

2017-11-11 Thread Jeremy Bicha
Package: ftp.debian.org
X-Debbugs-Cc:gnome-su...@packages.debian.org

Please remove gnome-sushi 3.24.0-1experimental1 from Debian
experimental. It should be cruft since I believe 3.24.0-1+b1 has a
higher version number (and fulfills the need to have gnome-sushi
rebuilt against gjs 1.50).

Thank you,
Jeremy Bicha



Bug#880404: quantlib-examples: fails to upgrade from 'stretch' - trying to overwrite /usr/bin/CVAIRS

2017-11-11 Thread Andreas Beckmann
On 11/10/2017 02:04 PM, Dirk Eddelbuettel wrote:
> Slight problem. When I add 
> 
>   Breaks: libquantlib0v5
>   Replaces: libquantlib0v5
> 
> I run into
> 
>   E: quantlib-examples: conflicts-with-dependency depends libquantlib0v5
> 
> as it also has
> 
>   Depends: ${shlibs:Depends}, ${misc:Depends}, libc6-dev, libboost-test-dev, 
> libquantlib0v5 (= ${binary:Version})
> 
> Ideas?

Breaks+Replaces should be versioned (<< 1.11-2), since that was the
versioned that moved around the files.

Andreas



Bug#881435: vtk6: Please move the build-depends on ftgl-dev to libftgl-dev

2017-11-11 Thread Manuel A. Fernandez Montecelo
Source: vtk6
Version: 6.3.0+dfsg1-10
Severity: wishlist
Control: block 878529 by -1

Hello,

In order to be possible to drop the transitional package ftgl-dev, the packages
depending on it have to migrate first.

Please move the build-depends on ftgl-dev to libftgl-dev.

Additionally, as per #750186, it seems that the build-dependency it's not even
needed because the system-provided ftgl is not used, so maybe it can be dropped
entirely.


Cheers.



Bug#881433: maven: /usr/share/maven/boot/plexus-classworlds-2.x.jar should point to /usr/share/java/plexus-classworlds.jar

2017-11-11 Thread Miguel Landaeta
Package: maven
Version: 3.3.9-4
Severity: normal
Tags: patch

As title says.

/usr/share/maven/boot/plexus-classworlds-2.x.jar is currently pointing
to /usr/share/java/plexus-classworlds2.jar that is provided by
transitional package libplexus-classworlds2-java.

However, maven switched its dependency to libplexus-classworlds-java,
so this causes a dangling pointer and breaks maven unless you have
installed both libplexus-classworlds-java packages.

Anyway, the fix should be trivial and I pushed it to the repo.
Feel free to revert if there is a better alternative or I'm wrong
about this.

Cheers,
Miguel.


diff --git a/debian/maven.links b/debian/maven.links
index 8a017ef..5a7cec0 100644
--- a/debian/maven.links
+++ b/debian/maven.links
@@ -2,7 +2,7 @@
 
 /etc/maven/m2.conf /usr/share/maven/bin/m2.conf
 
-/usr/share/java/plexus-classworlds2.jar 
/usr/share/maven/boot/plexus-classworlds-2.x.jar
+/usr/share/java/plexus-classworlds.jar 
/usr/share/maven/boot/plexus-classworlds-2.x.jar
 
 /usr/share/java/aopalliance.jar  
/usr/share/maven/lib/aopalliance.jar
 /usr/share/java/cdi-api.jar  
/usr/share/maven/lib/cdi-api.jar

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

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

Versions of packages maven depends on:
ii  default-jre-headless [java7-runtime-headless]2:1.8-58
ii  libmaven3-core-java  3.3.9-4
ii  openjdk-8-jre-headless [java7-runtime-headless]  8u141-b15-1~deb9u1

maven recommends no packages.

maven suggests no packages.

-- no debconf information

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


signature.asc
Description: PGP signature


Bug#881434: darkradiant: Please move the build-depends on ftgl-dev to libftgl-dev

2017-11-11 Thread Manuel A. Fernandez Montecelo
Source: darkradiant
Version: 2.1.0-1
Severity: wishlist
Control: block 878529 by -1

Hello,

In order to be possible to drop the transitional package ftgl-dev, the packages
depending on it have to migrate first.

Please move the build-depends on ftgl-dev to libftgl-dev.

Cheers.



Bug#880921: libopencv-dev: removal of libopencv-dev makes files disappear from libhighgui-dev

2017-11-11 Thread Andreas Beckmann
On 11/08/2017 04:08 PM, Mattia Rizzolo wrote:
> libhighgui-dev has been removed altogether.  Therefore, I wonder if an
> acceptable solution would be to remove the version restriction in the
> Conflicts.
> Seemingly, I'd remove the version from the libcv-dev, libcvaux-dev
> Conflicts as well

Sounds like a sensible approach to get cruft deinstalled.

> (they are in the same situation, probably if you test
> them you will find the same bug).
> Are the other binaries that are affected by a similar situation?

Didn't see similar problems in other packages, but if the dependency
chain is not trivial, it may take more crafting to get a reproducible
buggy path ...

Andreas



Bug#881431: debian-policy: Clarify a version number is unique field

2017-11-11 Thread Christoph Biedl
Package: debian-policy
Version: 4.1.1.1
Severity: wishlist

Hello,

this is in the category of "It should be obvious to anybody but I'd
prefer things are well-defined in case anybody wishes to start an
argument over that". So rather nitpicking.

Version number re-usage happens, probably always by accident. In the
past, before the advent of slugs to mark security uploads and the like,
this was more likely to happen, and a long time ago my src:file package
was affected by that as well[1]. Unfortunately, there was such an event
even in 2017, see #876633.

Such re-usage is fairly annoying:

* It breaks a reasonable assumption about the features provided by
  a package installed in a given version.

* It breaks caching proxies that rely on the uniqueness for performance
  i.e. no re-validation with upstream required. Also, proxies might
  retain packages for longer than they exist on a mirror.

So I'd like to suggest an addition to "3.2. The version of a package",
for clarification, wording in the simplest form:

| For any package, a version number must never be re-used.

What I'd like to express but I guess is a bit too long:

| Unless bitwise identical, no two files that share the base name and
| have a version number in it may exist anywhere in the archives, ever.

Also, this is rather file-system based. But it should serve the first
purpose as well: If a package in a given version is installed on two
systems, the same feature set is provided on both without a doubt.

A few explanations:

* As it says, it's about *all* files that have a version number in
  the name, source and binary packages, upstream tarballs, *.dsc,
  *.diff.*, *.debian.tar.* and anything else.
* Files without a version number in the name like package indexes and
  documentation are considered volatile anyway.
* Moving files around without modification is acceptable and also daily
  routine: Between the queues, also from security to -proposed-updates
* By archive I think about the Debian files served by ftp.debian.org,
  security.debian.org, ftp.ports.debian.org and probably a few,
  rather semi-official more. Perhaps "archive" isn't the best word
  for this.

As always about policy, I'm interested about the idea but don't stick
to a particular wording. Feel free to improve as I'm also not a native
speaker.

Also I feel a temptation to implement an according check in the
auto-reject machinery at ftp-master. But that's for another day.

Regards,
Christoph

[1] Examples:
* Completely different
  http://snapshot.debian.org/package/file/4.17-5etch2/
* Duplicate on .dsc only (different signature, how did *that*
  ever happen?):
  http://snapshot.debian.org/package/file/5.04-5%2Bsqueeze2/

PS: Aside, I like the new presentation format of the policy document as
seen in . Improved visual,
policy version number at the very beginning, maintainer script
flowcharts, upgrading checklist included, but no additional and
dangerous requirements for using the document (i.e. works fine without
JavaScript). Much appreciated.


signature.asc
Description: Digital signature


Bug#881432: debian-policy: Please clarify postinst invocation upon first installation

2017-11-11 Thread Christoph Biedl
Package: debian-policy
Version: 4.1.1.1
Severity: wishlist

Hello,

the question of how to tell in postinst whether this is an upgrade or a
first installation comes up every now and then. Again yesterday in
#debian-mentors. Therefore I'm asking for a clarifcation in

6.5. Summary of ways maintainer scripts are called

in the paragraph after

"postinst configure most-recently-configured-version"

Suggested wording:

| If this package was prevously uninstalled, the
| "most-recently-configured-version" string is empty.

Reading src/configure.c in dpkg, this should be technically correct.

Also testing for an empty $2 in postinst is common according to
codesearch[1].

Regards,
Christoph

[1] 
https://codesearch.debian.net/search?q=-z+%22%5C%242%22+path%3Adebian%2F*.postinst


signature.asc
Description: Digital signature


Bug#881427: [debhelper-devel] Bug#881427: Bug#881427: debhelper: dh_builddep fails, causing FTBFS: undefined value as an ARRAY reference

2017-11-11 Thread Axel Beckert
Control: close -1

Hi Hilko,

Hilko Bengen wrote:
> > This should be fixed with the just uploaded 10.10.7:
> 
> It is. I have tried a rebuild using debhelper/10.10.7 built from git and
> everything is fine.

Thanks for the feedback. I'm hence closing the bug report as fixed
with 10.10.7 (as you already set).

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



Bug#881430: vim is destroyed when using gpm

2017-11-11 Thread vimuser
Package: vim
Version: 2:8.0.0197-4+deb9u1
Severity: important

Dear Maintainer,

vim is not usable on virtual console or X-window

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

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

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


-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.gtk3
/usr/bin/vim is /usr/bin/vim.gtk3
/usr/bin/gvim is /usr/bin/vim.gtk3

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

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

Versions of packages vim depends on:
ii  libacl1  2.2.52-3+b1
ii  libc62.24-11+deb9u1
ii  libgpm2  1.20.4-6.2+b1
ii  libselinux1  2.6-3+b3
ii  libtinfo56.0+20161126-1+deb9u1
ii  vim-common   2:8.0.0197-4+deb9u1
ii  vim-runtime  2:8.0.0197-4+deb9u1

vim recommends no packages.

Versions of packages vim suggests:
pn  ctags
pn  vim-doc  
ii  vim-scripts  20130814

-- no debconf information



Bug#871987: This bug appears to be fixed as of 1.1.0g-2

2017-11-11 Thread James Bottomley
I can confirm that all the previously failing tools (dovecot, stunnel
etc) are working again with 1.1.0g-2

Presumably this also fixes 

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875423

James



  1   2   >