Bug#896710: harfbuzz: autopkgtest to detect freetype regressions

[أحمد المحمودي]

reopen 896710
quit

On Mon, Apr 23, 2018 at 05:14:19PM -0700, Steve Langasek wrote:
> So I've added a simple build-only autopkgtest to harfbuzz in Ubuntu; please
> see the attached patch, and please consider whether you think this would
> also be useful to have in Debian.
---end quoted text---

I removed this testsuite, since Debian prohibits adding no-op tests.

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#905944: Broken rdepends command

[Julien Puydt]

Package: npm2deb
Version: 0.2.7-6
Severity: normal

The 'rdepends' command is broken ; the reason is that the api to do the 
request wasn't official and has been removed, see:

  https://github.com/npm/registry/issues/231

Currently the best way to get it back might be to parse the pages like:
  https://www.npmjs.com/browse/depended/MODULE_NAME


I hope that helps,

jpuydt on irc.debian.org

Bug#826003: login: su(1) man page should document that su may not work at boot time

[Andreas Henriksson]

Control: tags -1 + moreinfo

On Wed, Jun 01, 2016 at 12:09:08PM +0200, Vincent Lefevre wrote:
> Package: login
> Version: 1:4.2-3.1
> Severity: minor
> 
> I've used "su some_user -c some_command" for years at boot time,
> with sysvinit and more recently with systemd. But starting with
> systemd 230, this no longer works due to the (undocumented)
> dependency on PAM/dbus (PAM is just mentioned for -m and -p).
> 
> It should be documented that su may not work at boot time, at least
> until dbus is available. And runuser should be suggested.
> 
> In ,
> Michael Biebl says:
> 
>   You are involving the pam stack here at a point when dbus is not
>   available yet. So this is a misconfiguration of sorts.
> 
>   I think you really want runuser instead of su here.

I'm not sure runuser would work as that also has a separate pam config.
Quoting from the runuser manpage:

   If  the PAM session is not required then recommended solution is
   to use setpriv(1) command.

Both su and runuser manpages already talk about pam configuration so
should be fairly obvious pam needs to be up first, but this seems more
like an issue related to how systemd works - or possibly rather how you
wrote your unit/service file and its dependencies.

I'm likely of the opinion that different init systems behaviours should
not be documented in util-linux, as util-linux has no relationship to
the init system what so ever (eg. feel free to use su, runuser, setpriv,
etc. in your init-less container/chroot).

I'll likely wontfix and close this issue unless someone can provide an
actual tested and working suggestion and a rationale why this belongs in
util-linux. Tagging moreinfo for now.

Regards,
Andreas Henriksson

Bug#905943: Should create Vcs-* fields pointing to salsa

[Julien Puydt]

Package: npm2deb
Version: 0.2.7-6
Severity: wishlist

Hi,

I was surprised this morning that npm2deb created a package with Vcs-* 
fields pointing to anonscm.debian.org... they should point to salsa instead.


Thanks,

jpuydt on irc.debian.org

Bug#711104: [Pkg-shadow-devel] Bug#711104: login: su - doesn't set umask

[Andreas Henriksson]

Control: tags -1 + help

On Wed, Jun 05, 2013 at 07:00:29AM +0200, Christian PERRIER wrote:
> Quoting Piotr Engelking (inkerma...@gmail.com):
[...]
> > The 'su -' command, unlike login, doesn't set umask. This behavior
> > disagrees with the man page, which says:
> > 
> >   The optional argument - may be used to provide an environment similar
> >   to what the user would expect had the user logged in directly.
> > 
> > Operating with an unexpected umask value is dangerous, particularly so
> > if running as root.
> > 
> > Please change su - to set umask to the same value that login does.
> 
> 
> Without checking, though, I suspect this to be a PAM issue.

Should /etc/pam.d/su-l gain a line for pam_umask ? Possibly also
pam_limits ? Maybe they should even be in /etc/pam.d/su (which is also
included by /et/pam.d/su-l)

Help from pam experts would be appreciated.

(Maybe this is looking at it too narrowly though, and instead the entire
/etc/pam.d/su file carried over from src:shadow/login days should be
revamped/rewritten.)

Regards,
Andreas Henriksson

Bug#905409: upgrade of util-linux and login break the xhost command for other users

[Andreas Henriksson]

Hello Helge Kreutzmann,

I'm skeptical how relevant it is to document how X and ssh works
in the _su_ manpage, but either way since you're patching the
manpage this is something you want to send upstream for review if
you think it's worth persuing and my opinion doesn't count there.

As always to increase chances of a favourable review getting the
administrative details right from the start is useful, so please
see Documentation/howto-contribute.txt

(You might also want to replace references to 'Debian 9' with
'shadow su implementation' or similar.)

I'll add a note to util-linux.NEWS about DISPLAY and XAUTHORITY.

Regards,
Andreas Henriksson

Bug#905881: lintian: detect packages containing X11 fonts that do not run update-fonts-* or do not dep on xfonts-utils

[Paul Wise]

On Sat, 2018-08-11 at 10:07 +0100, Chris Lamb wrote:

>   
> https://salsa.debian.org/lintian/lintian/commit/1fe8f33d7ffaab74c47d5ed61c56d8a8a0abb693

Thanks.

A few fixes are needed:

s/which comes/which come/

s/If you are using dh_installxfonts/If you are using debhelper/

The code unconditionally detects update-fonts-scale but the
dh_installxfonts code only inserts that conditionally (see below).

The code does not detect update-fonts-alias being missing but
dh_installxfonts conditionally inserts calls to that (see below).

One of the tag descriptions mentions an update-fonts-utils script,
but that does not exist:

$ find /usr/sbin/update-fonts-*
/usr/sbin/update-fonts-alias
/usr/sbin/update-fonts-dir
/usr/sbin/update-fonts-scale

Here is most of the code from dh_installxfonts:

foreach my $package (@{$dh{DOPACKAGES}}) {
my $tmp=tmpdir($package);

# Find all font directories in the package build directory.
my @fontdirs;
foreach my $parentdir ("$tmp/usr/share/fonts/X11/") {
opendir(DIR, $parentdir) || next;
@fontdirs = grep { -d "$parentdir/$_" && !/^\./ } (readdir DIR);
closedir DIR;
}

if (@fontdirs) {
# Figure out what commands the postinst and postrm will need 
# to call.
my @cmds;
my @cmds_postinst;
my @cmds_postrm;
# Sort items for reproducible binary package contents.
foreach my $f (sort @fontdirs) {
# This must come before update-fonts-dir.
push @cmds, "update-fonts-scale $f"
if -f "$tmp/etc/X11/fonts/$f/$package.scale";
push @cmds, "update-fonts-dir --x11r7-layout $f";
if (-f "$tmp/etc/X11/fonts/$f/$package.alias") {
push @cmds_postinst, "update-fonts-alias 
--include /etc/X11/fonts/$f/$package.alias $f";
push @cmds_postrm, "update-fonts-alias 
--exclude /etc/X11/fonts/$f/$package.alias $f";
}
}

autoscript($package, "postinst", "postinst-xfonts",
{ 'CMDS' => join(";", @cmds, @cmds_postinst) });
autoscript($package, "postrm", "postrm-xfonts",
{ 'CMDS' => join(";", @cmds, @cmds_postrm) });

if (@cmds_postrm) {
addsubstvar($package, "misc:Depends", "xfonts-utils", 
">= 1:7.5+2");
} else {
addsubstvar($package, "misc:Depends", "xfonts-utils");
}
}
}

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#905880: tex-gyre: contains X11 fonts but does not run update-fonts-* in postinst nor dep on xfonts-utils

[Paul Wise]

On Sat, 2018-08-11 at 22:31 +0900, Norbert Preining wrote:

> How can I check this? I tried xlsfonts and it showed me the texgyre
> fonts.

I tried installing tex-gyre as well as some other xfonts-* packages and
none of them show up in the xlsfonts output for me. I guess existing
Xorg processes don't automatically reload fonts.

I created a new user and logged into an openbox session and xlsfonts
showed the new fonts (unifont and baekmuk) but not gyre fonts.
I got the same with a GNOME Wayland session with XWayland.

Can you try creating a new user and running xlsfonts there?

Do you maybe have the gyre fonts installed elsewhere on your system?

Does this command print anything for you?

find /usr/share/fonts/X11/ -name fonts.dir -print0 | xargs -0 grep -i gyre

Can you delete the /usr/share/fonts/X11/*/fonts.dir files, reinstall
tex-gyre/lmodern and all the xfonts-* packages you have installed?

BTW, it might be a good idea to move the fonts into an xfonts-gyre
package to match how other X11 fonts are packaged.

> So moving the dh_installxfonts call to below the loop would solve it,
> but I first want to know what you mean with "not registered properly".

Solely the update-fonts-* in postinst and dep on xfonts-utils.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#905942: apt-move: diff for NMU version 4.2.27-5.1

[Luis Chamberlain]

Package: apt-move
Version: 4.2.27-5
Severity: normal
Tags: patch  pending

Dear maintainer,

I've prepared an NMU for apt-move (versioned as 4.2.27-5.1) and
the patch fixes a small issue found with apt-move. It is reported
on many lists, and some folks have done hacks around this.

Regards.
diff -Nru apt-move-4.2.27/debian/changelog apt-move-4.2.27/debian/changelog
--- apt-move-4.2.27/debian/changelog	2016-11-01 23:11:28.0 -0600
+++ apt-move-4.2.27/debian/changelog	2018-08-11 19:06:52.0 -0600
@@ -1,3 +1,10 @@
+apt-move (4.2.27-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use a modern shell to fix waitall odd /bin/sh issue
+
+ -- Luis Chamberlain   Sat, 11 Aug 2018 19:06:52 -0600
+
 apt-move (4.2.27-5) unstable; urgency=medium
 
   * QA upload.
diff -Nru apt-move-4.2.27/debian/patches/fix-waitall.patch apt-move-4.2.27/debian/patches/fix-waitall.patch
--- apt-move-4.2.27/debian/patches/fix-waitall.patch	1969-12-31 18:00:00.0 -0600
+++ apt-move-4.2.27/debian/patches/fix-waitall.patch	2018-08-11 19:06:52.0 -0600
@@ -0,0 +1,10 @@
+/bin/sh cannot find waitall(). Use a much more modern shell.
+
+--- a/apt-move
 b/apt-move
+@@ -1,4 +1,4 @@
+-#!/bin/sh
++#!/bin/bash
+ #
+ #  Copyright (c) 1999 Michael Merten 
+ #  Copyright (c) 1999-2000 Gregory T. Norris 

Bug#905941: apt-move: diff for NMU version 4.2.27-5.1

[Luis Chamberlain]

Package: apt-move
Version: 4.2.27-5
Severity: normal
Tags: patch  pending

[Replace XX with correct value]

Dear maintainer,

I've prepared an NMU for apt-move (versioned as 4.2.27-5.1) and
the attached small fix fixes a long reported issue with running
apt-move.

Regards.

diff -Nru apt-move-4.2.27/debian/changelog apt-move-4.2.27/debian/changelog
--- apt-move-4.2.27/debian/changelog	2016-11-01 23:11:28.0 -0600
+++ apt-move-4.2.27/debian/changelog	2018-08-11 19:06:52.0 -0600
@@ -1,3 +1,10 @@
+apt-move (4.2.27-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use a modern shell to fix waitall odd /bin/sh issue
+
+ -- Luis Chamberlain   Sat, 11 Aug 2018 19:06:52 -0600
+
 apt-move (4.2.27-5) unstable; urgency=medium
 
   * QA upload.
diff -Nru apt-move-4.2.27/debian/patches/fix-waitall.patch apt-move-4.2.27/debian/patches/fix-waitall.patch
--- apt-move-4.2.27/debian/patches/fix-waitall.patch	1969-12-31 18:00:00.0 -0600
+++ apt-move-4.2.27/debian/patches/fix-waitall.patch	2018-08-11 19:06:52.0 -0600
@@ -0,0 +1,10 @@
+/bin/sh cannot find waitall(). Use a much more modern shell.
+
+--- a/apt-move
 b/apt-move
+@@ -1,4 +1,4 @@
+-#!/bin/sh
++#!/bin/bash
+ #
+ #  Copyright (c) 1999 Michael Merten 
+ #  Copyright (c) 1999-2000 Gregory T. Norris 

Bug#905880: tex-gyre: contains X11 fonts but does not run update-fonts-* in postinst nor dep on xfonts-utils

[Paul Wise]

On Sat, 2018-08-11 at 22:33 +0900, Norbert Preining wrote:

> You mean the ... stuff? We don't call anything defoma related other than this.

Also these:

$ find debian/ -iname *defoma*
debian/tex-gyre.defoma-hints
$ grep defoma debian/rules
# Generate $(PKG).scale from $(PKG).defoma-hints (since it contains
  "debian/$(PKG).defoma-hints" > "debian/$(PKG).scale.tmp"
  < "debian/$(PKG).defoma-hints" > "debian/$(PKG).fontlist-x11"

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#905939: tzdata files can get corrupted via write to /etc/localtime

[Vincent Lefevre]

Package: tzdata
Version: 2018e-0+deb9u1
Severity: important

On a Debian 9 machine:

patate:~> TZ=UTC date; TZ=UTC0 date
Sun Aug 12 03:02:35 CEST 2018
Sun Aug 12 01:02:35 UTC 2018

The first line is based on the /usr/share/zoneinfo/UTC file according
to strace, but this is wrong as CEST is not UTC. The file is:

-rw-r--r-- 1 root root 2971 2018-05-15 10:01:38 /usr/share/zoneinfo/UTC

which doesn't seem to be the original one. I assume that it got
corrupted via a write to /etc/localtime, but /etc/localtime is
a symlink to /usr/share/zoneinfo/Etc/UTC, which is itself a
symlink to /usr/share/zoneinfo/UTC.

Now, could the write to /etc/localtime be regarded as a bug?
Probably not, because /etc/localtime is a config file, and one
is allowed to write to config files under /etc.

In short, having a symlink from a file under /etc to a file from
a package does not seem to be correct.

BTW, on https://www.virtualmin.com/node/15246 someone mentioned
another issue with a symlink: "It's not really wise to make
/etc/localtime a symlink. That used to be the standard behavior for
Linux in the past, but then someone realized that /usr/share/zoneinfo
could be on a different volume that's not always mounted, and we
definitely don't want to be without /etc/localtime, [...]"

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

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

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.61

tzdata recommends no packages.

tzdata suggests no packages.

-- no debconf information

Bug#905940: Please resolve failing autopkgtests, preferably by converting to dh-elpa

[Nicholas D Steeves]

Package: tuareg-mode
Severity: important

Dear Debian OCaml Maintainers,

Thank you for maintaining tuareg-mode!  Unfortunately it's
autopkgtests have been failing since emacsen-common 3.0.2 and
unversioned emacs were uploaded, and tuareg-mode is delaying their
migration to testing.  Would you please adapt tuareg-mode to the new
infrastructure?

In the case of irony-mode, the quick fix for autopkgtest on LXC was to
add "ert_eval = (require 'cl)" to debian/elpa-test; this was not
required for tests to pass on a real system or in any type of chroot.
The use of d/elpa-test requires converting the package to use dh-elpa
rather than legacy debian/emacsen.scripts.  In addition to the general
case of making src:packages maintenance less burdensome, using dh-elpa
appears to have insulated many packages from the breaking changes
recently introduced by emacs upgrades.

This action will also close #850071, #582981, because dh-elpa does not
support XEmacs.

Please let me know if I can be of any assistance :-)

Cheers,
Nicholas

Bug#905938: git-rebase(1) has wrong filename for revert-a-faulty-merge.html

[Ben Hutchings]

Package: git-man
Version: 1:2.18.0-1
Severity: normal

git-rebase(1) refers to
/usr/share/doc/git/html/howto/revert-a-faulty-merge.html, but this
filename does not exist in any package.  git-doc contains
/usr/share/doc/git-doc/howto/revert-a-faulty-merge.html which is
presumably the right file to refer to.

Ben.

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

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

-- no debconf information

Bug#905934: git-debrebase: convert-from-gbp may lose non-git header fields

[Ben Hutchings]

Control: tag -1 patch

On Sun, 2018-08-12 at 00:28 +0100, Ben Hutchings wrote:
> Control: reassign -1 git-buildpackage 0.9.9
> 
> gbp pq is actually responsible for this.
[...]

I've written test cases and fixes for this and a related bug, and
pushed them to:
https://salsa.debian.org/benh/git-buildpackage

Ben.

-- 
Ben Hutchings
The Peter principle: In a hierarchy, every employee tends to rise to
their level of incompetence.


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

Bug#904796: chromium for arm64 lacks security updates

[Michael Gilbert]

control: tag -1 pending

On Tue, Aug 7, 2018 at 9:07 AM, Riku Voipio wrote:
> I didn't push this to main stretch branch, as the security upload commit
> is reconstructed rather the original from Michael. Changelog hasn't been
> updated either.

I had forgotten to push after the previous upload, done now.  I will
include this in the next stable-sec upload.

Best wishes,
Mike

Bug#900399: More good news

[ydirson]

severity 900399 normal
thanks

I suggest you get some advice from the forum[1], and as Dmitry mentionned, 
bring the issue to Lenovo.

[1] 
http://forum.canardpc.com/forums/73-Memtest86-Official-forum?s=1407c99a4da914ef85e60c32c658ba16

- Mail original -
> De: "Сергей Коган" 
> À: 900...@bugs.debian.org
> Envoyé: Jeudi 7 Juin 2018 15:26:43
> Objet: Bug#900399: More good news
> 
> Hi!
> 
> Let's lower the severity of this bug and flag it as unverified.
> 
> Given the datasheet for the TB62501 and actual board layout of the
> T500
> - the described scenario (short from the VCC3SW to GND caused by a
> stray
> write to the PMH register) is highly improbable:
> 
> - The LDO inside the RINKAN has an over-current protection set as low
> as
> 55mA and should prevent any damage even if the VCC3SW is shorted.
> After
> the single over-current/under-voltage event, RINKAN LDO is locked in
> the
> OFF state and requires a complete power-off to restart.
> 
> - Unused pins of the PMH are in fact floating
> 
> - Some RINKAN batches do show tendency to malfunction with no
> apparent
> reasons. The main board temperature could be a contributing factor.
> 
> So, we have to seriously consider the possibility that two laptops
> died
> at the same time just by a coincidence.
> 
> We do plan to run a memtest on the restored laptop using a current
> measuring/limiting circuit on the VCC3SW bus. If no excessive current
> consumption would be detected - the memtest has nothing to do with
> the
> issue. If an excessive current during the test would be observed, it
> would get us a direction to resume the investigation.
> 
> ---
> Sincerely yours,
> Sergey Kogan
> 

Bug#897189: chromium 66 tab crash on certain sites with ublock origin

[Michael Gilbert]

On Sat, Aug 11, 2018 at 8:11 PM, Michael Gilbert wrote:
> As far as I can tell, this is upstream http://crbug.com/844377.  It
> was introduced in chromium 66 just like you experienced and symptoms
> are nearly identical.
>
> I previously checked that their fix was applied in version
> 68.0.3440.75-1~deb9u1 and have just double checked it, so as far as I
> can tell it should be fixed.  Can you provide any more detail? dbgsym
> packages are in fact available [0].

Correction, missing dbgsym packages for stable-sec is a known bug [1].
You could try rebuilding from source, one of the outputs will be the
dbgsym package.

Best wishes,
Mike

[1] http://bugs.debian.org/894081

Bug#897189: chromium 66 tab crash on certain sites with ublock origin

[Michael Gilbert]

control: tag -1 moreinfo

On Sat, Aug 11, 2018 at 3:20 PM, Ryan Tandy wrote:
> I'm afraid I'm still experiencing the same tab crashes with M68 in
> stretch-security.

As far as I can tell, this is upstream http://crbug.com/844377.  It
was introduced in chromium 66 just like you experienced and symptoms
are nearly identical.

I previously checked that their fix was applied in version
68.0.3440.75-1~deb9u1 and have just double checked it, so as far as I
can tell it should be fixed.  Can you provide any more detail? dbgsym
packages are in fact available [0].

Best wishes,
Mike

[0] http://debug.mirrors.debian.org/debian-debug/pool/main/c/chromium-browser

Bug#905937: RFP: python-kivy-garden.modernmenu -- a stylized menu system for kivy

[W. Martin Borgert]

Package: wnpp
Severity: wishlist

* Package name: python-kivy-garden.modernmenu
  Version : (2017-06-18)
  Upstream Author : Gabriel Pettier
* URL : https://github.com/kivy-garden/garden.modernmenu
* License : MIT/X
  Programming Lang: Python
  Description : a stylized menu system for kivy

(This is a dependency for cagou https://bugs.debian.org/897232 .)

Bug#580312: multipath-tools: multipathd segfaults when restarted

[Vincent McIntyre]

On Sat, Aug 11, 2018 at 05:09:58PM +0200, Chris Hofstaedtler wrote:
> 
> Do you still see this in current versions?

No, have not seen this occur again like this that I can recall;
we would have followed up to this bug if we had.
 
I think this bug can probably be closed, the code has improved
enormously since this occurred and nobody else seems to have hit it.

Kind regards
Vince

Bug#905936: RFP: python-kivy-garden.contextmenu -- collection of classes for easy creating context and application menus with kivy

[W. Martin Borgert]

Package: wnpp
Severity: wishlist

* Package name: python-kivy-garden.contextmenu
  Version : (2017 -01-10)
  Upstream Author : Martin Sikora
* URL : https://github.com/kivy-garden/garden.contextmenu
* License : MIT/X
  Programming Lang: Python
  Description : collection of classes for easy creating context and 
application menus with kivy

(This is a dependency for cagou https://bugs.debian.org/897232 .)

Bug#902413: systemd-tmpfiles migration warning

[Julian Gilbey]

tags 902413 +patch
thanks

On Tue, Jun 26, 2018 at 12:28:48PM +0200, wavexx wrote:
> Package: fail2ban
> Version: 0.10.2-2
> Severity: minor
> 
> systemd-tmpfiles[2145]: [/usr/lib/tmpfiles.d/fail2ban-tmpfiles.conf:1] Line 
> references path below legacy directory /var/run/, updating /var/run/fail2ban 
> → /run/fail2ban; please update the tmpfiles.d/ drop-in file accordingly.

All that is needed is to change /var/run/fail2ban to /run/fail2ban in
this file (/usr/lib/tmpfiles.d/fail2ban-tmpfiles.conf).

(You might want to add a newline at the end of the file, too.
Incidentally, most packages I have installed just call their
configuration .conf rather than -tmpfiles.conf.  But
that's cosmetic.)

Best wishes,

   Julian

Bug#905694: chromium: *** version in stable/security-updates still has video/ffmpeg bug that was closed 2 months ago

[Michael Gilbert]

control: tag -1 moreinfo

On Wed, Aug 8, 2018 at 3:35 AM, Tim Connors wrote:
> Package: chromium
> Version: 68.0.3440.75-1~deb9u1
> Severity: normal
>
> Dear Maintainer,
>
> bugs 900533, 902909 have been long closed, but unforuntately that is
> completely irrelevant for those of us who are running stable and had a
> security update pushed on us that has broken most the the www's
> functionality:

What specifically do you see that isn't working in
68.0.3440.75-1~deb9u1?  Youtube and vimeo both work for me in this
version.  Ff you check the changelog this is the version where the bug
is fixed.

Best wishes,
Mike

Bug#905934: git-debrebase: convert-from-gbp may lose non-git header fields

[Ben Hutchings]

Control: reassign -1 git-buildpackage 0.9.9

gbp pq is actually responsible for this.

Ben.

On Sat, 2018-08-11 at 23:48 +0100, Ben Hutchings wrote:
> Package: git-debrebase
> Version: 6.6
> Severity: normal
> 
> Where patches have DEP-3 header fields that cannot be directly included
> in git metadata, such as Origin, Forwarded, and Bug-Debian, they don't
> seem to be reliably included in git commits.
> 
> For a real example, compare branches use-dgit (patch queue) and
> use-dgit-broken (converted) of
> .  Patch
> debian/powerpcspe-omit-uimage.patch has:
> 
> Description: Prevent building uImage with missing mkimage
>  On some powerpc platforms, CONFIG_DEFAULT_UIMAGE is selected automatically,
>  which leads to uImage being built automatically with mkimage. This tool is 
> not
>  available in linux's build-dependencies, and the file is not strictly
>  necessary, so we are omitting this step in the build process, 
> Debian-specific.
> Author: Roland Stigge 
> Bug-Debian: https://bugs.debian.org/708094
> Forwarded: not-needed
> 
> and the Bug-Debian and Forwarded fields are included in commit
> 59bf920cddd60a767f0647b07ac4eea5904c35c1a.
> 
> Whereas patch bugfix/all/usbip-fix-misuse-of-strncpy.patch has:
> 
> From: Ben Hutchings 
> Date: Fri, 20 Jul 2018 01:30:24 +0100
> Subject: usbip: Fix misuse of strncpy()
> Bug-Debian: https://bugs.debian.org/897802
> 
> and the Bug-Debian field is not included in commit
> abd4e2a8668e7c52a565d15bc8ce71d4b4780122.
> 
> It looks as if when the body of the commit message comes mostly from a
> Description field placed before the non-git headers, they are added at
> the end of the body.  But if the body of the commit comes from free
> text below the patch headers, they are not included (perhaps they are
> overwritten?).
> 
> Ben.
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
> 'unstable'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages git-debrebase depends on:
> ii  git [git-core]1:2.18.0-1
> ii  libdpkg-perl  1.19.0.5
> ii  libfile-fnmatch-perl  0.02-2+b5
> ii  perl  5.26.2-6
> 
> Versions of packages git-debrebase recommends:
> ii  dgit  6.6
> ii  git-buildpackage  0.9.9
> 
> git-debrebase suggests no packages.
> 
> -- no debconf information
-- 
Ben Hutchings
The Peter principle: In a hierarchy, every employee tends to rise to
their level of incompetence.


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

Bug#100808: Don't miss out

[FSJ]

 Hi,
 You have been randomly selected to participate in the ongoing campus/work from 
home part time work. With no work experience and must be above 18 years old. 
Kindly forward your name, contact number and age by taping reply now, for a 
representative to contact you.
  
 Laurel Gom.
  

Bug#905935: lirc: systemd complains about legacy directory /var/run/ in tmpfiles.d/lirc.conf

[Julian Gilbey]

Package: lirc
Version: 0.10.0-2+b1
Severity: normal
Tags: patch

The file /usr/lib/tmpfiles.d/lirc.conf contains a reference to the
legacy /var/run/ directory, which has been replaced by /run/.  systemd
now complains:

[lirc.conf:1] Line references path below legacy directory /var/run/, updating 
/var/run/lirc → /run/lirc; please update the tmpfiles.d/ drop-in file 
accordingly.

Simple one-line patch: replaced /var/run/lirc by /run/lirc in this file.

Best wishes,

   Julian

Bug#903869: steam: Some games not open because of locales

[Michael Gilbert]

control: reassign -1 libx11-6
control: forcemerge 822438 -1

On Sun, Jul 15, 2018 at 9:53 PM, Vinícius Couto wrote:
> In my initial case (only pt_BR.UTF-8 locale enabled - is the default
> definition on brazilian debian fresh install), the Steam client worked well.
> The problem was that some games is mandatory the en_US.UTF-8 locale needs to
> be enabled too (if this locale is not the default of the system).

According to an upstream discussion [0], this seems to be a bug in xlib.

Best wishes,
Mike

[0] https://github.com/ValveSoftware/steam-for-linux/issues/1420

Bug#905934: git-debrebase: convert-from-gbp may lose non-git header fields

[Ben Hutchings]

Package: git-debrebase
Version: 6.6
Severity: normal

Where patches have DEP-3 header fields that cannot be directly included
in git metadata, such as Origin, Forwarded, and Bug-Debian, they don't
seem to be reliably included in git commits.

For a real example, compare branches use-dgit (patch queue) and
use-dgit-broken (converted) of
.  Patch
debian/powerpcspe-omit-uimage.patch has:

Description: Prevent building uImage with missing mkimage
 On some powerpc platforms, CONFIG_DEFAULT_UIMAGE is selected automatically,
 which leads to uImage being built automatically with mkimage. This tool is not
 available in linux's build-dependencies, and the file is not strictly
 necessary, so we are omitting this step in the build process, Debian-specific.
Author: Roland Stigge 
Bug-Debian: https://bugs.debian.org/708094
Forwarded: not-needed

and the Bug-Debian and Forwarded fields are included in commit
59bf920cddd60a767f0647b07ac4eea5904c35c1a.

Whereas patch bugfix/all/usbip-fix-misuse-of-strncpy.patch has:

From: Ben Hutchings 
Date: Fri, 20 Jul 2018 01:30:24 +0100
Subject: usbip: Fix misuse of strncpy()
Bug-Debian: https://bugs.debian.org/897802

and the Bug-Debian field is not included in commit
abd4e2a8668e7c52a565d15bc8ce71d4b4780122.

It looks as if when the body of the commit message comes mostly from a
Description field placed before the non-git headers, they are added at
the end of the body.  But if the body of the commit comes from free
text below the patch headers, they are not included (perhaps they are
overwritten?).

Ben.

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

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

Versions of packages git-debrebase depends on:
ii  git [git-core]1:2.18.0-1
ii  libdpkg-perl  1.19.0.5
ii  libfile-fnmatch-perl  0.02-2+b5
ii  perl  5.26.2-6

Versions of packages git-debrebase recommends:
ii  dgit  6.6
ii  git-buildpackage  0.9.9

git-debrebase suggests no packages.

-- no debconf information

Bug#905933: plinth: [INTL:fr] French debconf translation

[jean-pierre giraud]

Package: plinth
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french debconf translation file for plinth,
proofread by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Kind Regards

jipege


fr.po.gz
Description: application/gzip

Bug#905932: linuxinfo: [INTL:fr] French translation

[jean-pierre giraud]

Package: linuxinfo
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french translation for linuxinfo,
proofread by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Kind Regards

jipege


fr.po.gz
Description: application/gzip

Bug#905931: x2goserver: [INTL:fr] French translation

[jean-pierre giraud]

Package: x2goserver
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french debconf translation for x2goserver,
proofread by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Kind Regards

jipege


fr.po.gz
Description: application/gzip

Bug#905824: med-fichier: missing files due to non-CMake build

[Kurt Kremitzki]

Hello Gilles,

On 08/11/2018 04:43 PM, Gilles Filippini wrote:
> Control: tags -1 + moreinfo
> 
> Hi,
> 
-snip-
> 
> Patches welcome :)
> 
> I gave a try using the CMake build system, but it failed. Firstly, there
> is no CMakeList.txt to build the doc. Secondly the test suite fails:
-snip-
> 
> Thanks,
> 
> _g.
> 

Indeed, I should have mentioned that I am working on this myself! (Still
a bit new so please bear with me.) I created a bug since I'm a bit stuck
and wanted to try to get other people involved, and to track the work.

I don't have a build log handy to provide specifics just now, but at
this point, I've got a successful build (sans the docs) although the
main problem at this point is that the shared libraries are all coming
out unversioned, i.e. `usr/lib/*.so` instead of `usr/lib/*.so.x.y.z`.

I've already made a patch for CMakeLists.txt which adds multi-arch
support, and I presume I'll have to do the same for the versioning and
the docs.

I was hoping to find a package I could refer to which had a similar
unversioned shared library problem but was fixed with a patch--do you
happen to know of any? I am having the exact same unversioned shared
library problem trying to package SMESH, which depends on med-fichier,
and it's the reason I started investigating this issue. So, there's a
nice 2-birds-with-1-stone opportunity here.

Thanks for your quick response to the bug by the way!

P.S. By later today I'll have a buildlog + my changes up on salsa.d.o
and I'll update the bug with that info.

Bug#901701:

[Ricardo Ribalda Delgado]

This patch[1] fixes the bug for me:

diff --git a/libglfork.cpp b/libglfork.cpp
index 03f514f..dda6e4c 100644
--- a/libglfork.cpp
+++ b/libglfork.cpp
@@ -359,7 +359,7 @@ static bool test_drawpixels_fast(Display *dpy,
GLXContext ctx, GLXFBConfig dconf
   int iters = 0;
   do {
 primus.dfns.glBufferSubData(GL_PIXEL_UNPACK_BUFFER_EXT, 0,
width*height*4, pixeldata);
-primus.dfns.glDrawPixels(width, height, GL_BGRA, GL_UNSIGNED_BYTE, NULL);
+primus.dfns.glDrawPixels(width, height, GL_BGRA,
GL_UNSIGNED_BYTE, pixeldata);
 primus.dfns.glXSwapBuffers(dpy, pbuffer);
 iters++;
   } while (end > Profiler::get_timestamp());

[1] 
https://github.com/ribalda/primus/commit/1b6dbc56040a59b6b222ba40d7c2de8c6cf1fbba

--
Ricardo Ribalda

Bug#901052: New maintainer version

[Steve Langasek]

Hi Hugh,

On Sat, Aug 11, 2018 at 01:21:45PM +, Hugh McMaster wrote:
> Hi Steve,

> I'm going to re-release the NMU version as a maintainer version, since I'm
> now a co-maintainer of freetype.

As I said in my earlier email, you are welcome to take over the package. 
But I have not agreed to comaintain the package with you.  This should be
clear that you and I are not comaintainers, and anyone sponsoring an upload
that adds you as a comaintainer should have the good sense to either check
with the existing uploaders, or remove them from debian/control, before
sponsoring.

I'm really, perfectly fine with you taking over the package.  I do not have
time to maintain it to the level you're seeking, and I am not going to
commit any more time to it because I have no attachment to this software.  I
only object to having my name attached to work that's not my own, or to
changes being made in NMU that are not the prerogative of an NMUer.

If it's a practical problem to find sponsorship for such an adoption without
a clear paper trail, then I'm happy to either file an RFA: bug or do a
no-change upload setting you as the uploader and letting you take it from
there.

> It will be an experimental version, so I can handle the remaining bug
> reports for the removal of freetype-config.

> Then, unless any bugs come in, a second version will be released to
> Unstable.
> 
> I'll also add a git repository for freetype before making that second
> version.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#905090: wine-development: Causing SEGV when using Qt.

[Bernhard Übelacker]

Hello,
just tried to reproduce the issue and was able to in a buster i386 VM.

Unfortunately winedbg does not take advantage of the automatic dbgsym pages.

Therefore running from a local package build directory gives this stack:

Backtrace:
=>0 0x7ea989c5 USER_SetWindowPos+0x25() [./dlls/user32/winpos.c:2220] in user32 
(0x0060dac8)
  1 0x7ea5cd7f handle_internal_message+0x1de(hwnd=0x10070, msg=, wparam=0xc00) [./dlls/user32/message.c:1861] in user32 (0x0060db18)
  2 0x7ea61998 peek_message+0x1987(msg=, hwnd=(nil), 
first=, last=, flags=0x1, changed_mask=) [./dlls/user32/message.c:2920] in user32 (0x0060de38)
  3 0x7ea66cef PeekMessageW+0x79(msg_out=, 
hwnd=, first=, 
last=, flags=) 
[./dlls/user32/message.c:3768] in user32 (0x0060dea8)
  4 0x66b887bf in qt5core (+0x2487be) (0x0060fbb8)
  5 0x025a9347 in qwindows (+0x79346) (0x0060fbf8)
  6 0x66b27980 in qt5core (+0x1e797f) (0x0060fca8)
  7 0x66b31bd9 in qt5core (+0x1f1bd8) (0x0060fd28)
  8 0x0040189b in digitalclock (+0x189a) (0x0011c2d8)



Starting with some more verbosity leads to some PostMessageW call that puts
this message in some message queue:

$ WINEDEBUG=+win,+msg wine digitalclock.exe...
003c:trace:msg:PostMessageW hwnd 0x2007e msg 8001 (WM_WINE_SETWINDOWPOS) wp 
c00 lp 0
...
003c:trace:msg:peek_message got type 6 msg 8001 (WM_WINE_SETWINDOWPOS) hwnd 
0x2007e wp c00 lp 0
wine: Unhandled page fault on read access to 0x0018 at address 0x7ea989c5 
(thread 003c), starting debugger...



Another run in winedbg gives following stack where the message is entered into
the message queue:

$ wine winedbg digitalclock.exe
...
Wine-dbg>b PostMessageW
Wine-dbg>cont
Wine-dbg>cont
Wine-dbg>cont
...
Wine-dbg>bt
Backtrace:
=>0 0x7ea65cb0 PostMessageW(hwnd=0x40088, msg=0x8001, wparam=0xc00, 
lparam=0) [./dlls/user32/message.c:3643] in user32 (0x0060f568)
  1 0x7db6427e TABLET_PostTabletMessage+0x4d() in wintab32 (0x0060f598)
  2 0x7db64e23 WTOpenW+0x4f2(hWnd=, 
lpLogCtx=, fEnable=) 
[./dlls/wintab32/context.c:487] in wintab32 (0x0060f758)
  3 0x02596789 in qwindows (+0x66788) (0x00040088)


See below for the relevant source.
I think following might happen:

- Qt executes following to get a copy of the default context.
  WTInfoW -> WTInfoT -> LoadTablet -> LoadTabletInfo==X11DRV_LoadTabletInfo.

  In X11DRV_LoadTabletInfo the default context gets WT_DEFBASE(0x7FF0)
  assigned to member lcMsgBase in line 522.

  Some lines later is decided whether the device is usable
  by wintab32.dll and if yes add_system_cursor is called that
  increments gNumCursors.

  In every case X11DRV_LoadTabletInfo returns TRUE here.

  Therefore we continue here:
  WTInfoW -> WTInfoT -> pWTInfoW==X11DRV_WTInfoW
  As gNumCursors is 0 we do in line 1134 "if (0 == gNumCursors)" copy
  nothing and return 0 bytes copied.

  Unfortunately Qt does not check the return value of the WTInfoT call.

- Qt continues now to call wTOpen==WTOpenW assuming that we received a copy
  of the default context which we have not.

  Near the end WTOpenW wants to post a message:
  _WT_CTXOVERLAP(newcontext->context.lcMsgBase)

  Unfortunately lcMsgBase was not properly initialized and contains some 
"random" data.
  In our case it is quite reproducible as the resulting message is always
  WM_WINE_SETWINDOWPOS instead of WT_DEFBASE+4.

- Later USER_SetWindowPos expects the parameter lparam to contain
  a pointer to a WINDOWPOS struct.
  But the lparam is filled also from the context's lcStatus and contains also
  some "random" data and the process crashes.



I assume this worked before just because this resulting "random" window message
was just not used and therefore ignored.

I tried 3.12-2 from snapshot.debian.org and that did not crash.

When trying to run with e.g. WINEDEBUG=+win,+msg,+wintab32 the crash does also 
not happen.



Attached are some more information on my debugging and a patch that would
return FALSE from X11DRV_LoadTabletInfo in case no usable device was found.


Kind regards,
Bernhard









In Qt we might be in that location:

http://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/platforms/windows/qwindowstabletsupport.cpp
230 QWindowsTabletSupport *QWindowsTabletSupport::create()
231 {
232 if (!m_winTab32DLL.init())
233 return 0;
234 const HWND window = 
QWindowsContext::instance()->createDummyWindow(QStringLiteral("TabletDummyWindow"),
235
L"TabletDummyWindow",
236
qWindowsTabletSupportWndProc);
237 if (!window) {
238 qCWarning(lcQpaTablet) << __FUNCTION__ << "Unable to create window 
for tablet.";
239 return 0;
240 }
241 LOGCONTEXT lcMine;
242 // build our context from the default context
243 QWindowsTabletSupport::m_winTab32DLL.wTInfo(WTI_DEFSYSCTX, 0, ); 
  <-- return value is not checked ...
244 qCDebug(lcQpaTablet) << "Default: " << lcMine;

Bug#883950: Next steps on "[GPL-3+]" proposal

[Paul Hardy]

Just a couple of random thoughts...

There are two recurring themes (among others) in this bug report:

* How to make sure users know what "+" means, as in "GPL-2+"

* How to make sure users know where to find a full license

Suppose a tiny README file (uncompressed) is added to
/usr/share/common-licenses.  It can explain what the "+" in "GPL-2+"
etc. mean, and even contain a pointer to the copyright-1.0 document.

As for making it easy for a user find the license file, would it be
too complicated to use a standard URI in d/copyright?

So for example a d/copyright file could contain:

 License: GPL-2
  file:///usr/share/common-licenses/GPL-2

or

 License: GPL-2+
  file:///usr/share/common-licenses/README
  file:///usr/share/common-licenses/GPL-2

where the README file explains the "+" in "GPL-2+".  It would be
improbable for a user to see a URI like that and not realize that it
points to a specific file location on the system.

Thanks,


Paul Hardy

Bug#905824: med-fichier: missing files due to non-CMake build

[Gilles Filippini]

Control: tags -1 + moreinfo

Hi,

On Fri, 10 Aug 2018 04:59:38 -0500 Kurt Kremitzki 
wrote:
> Source: med-fichier
> Severity: normal
> 
> Dear Maintainer,
> 
> Med-fichier supports CMake builds, and if CMake is used there are
> several .cmake helper files generated which are currently missing from
> the package. Downstream projects then expect those .cmake files to be
> available, and it causes difficulty when they are not.
> 
> Please update the package to use the CMake buildsystem and include all
> missing files.

Patches welcome :)

I gave a try using the CMake build system, but it failed. Firstly, there
is no CMakeList.txt to build the doc. Secondly the test suite fails:
>   Start 37: Testtest13f   
>   
> 37/70 Test #37: Testtest13f ..***Failed0.01 sec   
>   
>
>0  
> 
>  Maillage de nom : maa1   
>   et de dimension :3
>0  
> 
>  Nombre d'equivalence :1  
>  
>  Equivalence numero :1
>   
>   
> /build/med-fichier-VMwX2G/med-fichier-3.3.1+repack/src/hdfi/MEDfichierNo.c 
> [39] : Impossible d'identifier un numéro de fichier correct à partir de 
> l'identifiant : 
> /build/med-fichier-VMwX2G/med-fichier-3.3.1+repack/src/hdfi/MEDfichierNo.c 
> [40] : id = 4294967296
> 
> /build/med-fichier-VMwX2G/med-fichier-3.3.1+repack/src/misc/MEDversionedApi3C.c
>  [42] : Cette bibliothèque MED n'est pas capable de lire un fichier MED de 
> version < 2.2.0
> /build/med-fichier-VMwX2G/med-fichier-3.3.1+repack/src/misc/MEDversionedApi3C.c
>  [43] : La version demandée est :
> /build/med-fichier-VMwX2G/med-fichier-3.3.1+repack/src/misc/MEDversionedApi3C.c
>  [44] : _fversionMMR = 0
> /build/med-fichier-VMwX2G/med-fichier-3.3.1+repack/src/misc/MEDversionedApi3C.c
>  [116] : Impossible d'obtenir une implémentation de :
> /build/med-fichier-VMwX2G/med-fichier-3.3.1+repack/src/misc/MEDversionedApi3C.c
>  [117] : key = "_MEDequivalenceInfo"  
>  
> /build/med-fichier-VMwX2G/med-fichier-3.3.1+repack/src/misc/MEDversionedApi3C.c
>  [118] : en version :  
> /build/med-fichier-VMwX2G/med-fichier-3.3.1+repack/src/misc/MEDversionedApi3C.c
>  [119] : _fversionMMR = 0 
> 
> /build/med-fichier-VMwX2G/med-fichier-3.3.1+repack/src/misc/MEDversionedApi3C.c
>  [120] : Vérifiez votre fichier .med et votre version de bibliothèque.

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Bug#905930: www.debian.org: Duplication of text in webpage https://www.debian.org/doc/manuals/developers-reference/ch04.en.html 4.6.5 "Debian 10, will be called buster and Debian 10 will be called bus

[Lucy Wayland]

Package: www.debian.org
Severity: minor

Dear Maintainer,

   * What led up to the situation?
   I am trying to apply to be a non-uploading DD, and I was reading up on the 
approriate documentation.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 N/A
   * What was the outcome of this action?
   No effect, just trying to help.
   * What outcome did you expect instead?
   Corrected during general clean ups as happen.

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

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

Bug#905874: libreoffice: No input of accented characters through dead-key composition

[Mario L. Epp K.]

Bug also present in the Backport.

On 08/11/2018 09:58 AM, Rene Engelhard wrote:

retitle 905874: libreoffice: No input of accented characters through dead-key 
composition in gen and kde4 plugins
thanks

On Sat, Aug 11, 2018 at 01:22:51PM +0200, Rene Engelhard wrote:

On Fri, Aug 10, 2018 at 10:18:30PM -0400, Mario L. Epp wrote:

On researching the issue prior to making this report, I found this issue
reported on the DocumentFoundation Bugzilla as "Bug 112770" at
. But I am not
shure how to implement the solution from 6.0.0 to 5.2.7.2 for KDE5 on Debian 9.


Maybe install the 6.1.0 backport from stretch-backports? That one also
has a KDE5 integration other than that KDE4 thingy "working" with KDE5.

This will never be fixed in stable properly (until buster releases of
course with above new KDE5 integration)


I uninstalled the "stable" LibreOffice before installing the 
"backported" LibreOffice with the Metapackage. After the instalation I 
rebooted the computer.


But the same bug appears also in LibreOffice 6.1.0.2 (Build ID: 
1:6.1.0~rc2-3~bpo9+1), Linux 4.9; UI render: defualt; VCL: x11.


Mario L. Epp

Bug#230068:

[hannah justin]

Ciao!!

Buon giorno, sono Hannah Justin, alla ricerca di un rispetto, onesto,
degno di fiducia e cura qualcuno per una relazione cordiale.

Distinti saluti!

Hannah

Bug#887809: Info received (Bug#887809: RFP: borgmatic -- A wrapper script for Borg backup software that creates and prunes backups)

[Dan Helfman]

Also, I filed this issue on pykwalify to hopefully rectify the license:

https://github.com/Grokzen/pykwalify/issues/136

Dan

Bug#891077: kpartx -d doesn't cleanup

[Chris Hofstaedtler]

Control: tags -1 + upstream confirmed

> >> If I execute the following testcase:
> >> #!/bin/bash -xe
> >> IMAGE_PATH=bug.img
[..]
> >> sudo kpartx -a "${IMAGE_PATH}"
> >> sudo kpartx -d "${IMAGE_PATH}"
> >> then kpartx won't cleanup its loop devices:

Indeed. The problem here is that the loop device refers to the image
file by full path, and then the comparison at -d time fails.
In general upstream thinks that this is a convenience feature and
you should delete mappings by passing the loop device name instead
(so kpartx -d /dev/loop1).

This is also LP#1747044.

Upstream has improved/fixes this in commit
c1adcc5ba452bb1252c97c8066e340433976c23e (past 0.7.7).

Cheers,
Chris

Bug#905196: nmu: pike8.0_8.0.610-1

[Adrian Bunk]

Control: reassign -1 release.debian.org
Control: retitle -1 nmu: pike8.0_8.0.610-1
Control: severity -1 normal

On Wed, Aug 01, 2018 at 08:20:41PM +0800, Boyuan Yang wrote:
>...
> Please consider making another upload to make sure that pike8.0 is
> built against new libsass / libsass1 library. BinNMU might be
> applicable but considering that the Testing migration is already
> blocked by some other problems [2], it might be better to fix the
> problem together with another upload.

The other problem is only related to cruft, so a binNMU is sufficient:

nmu pike8.0_8.0.610-1 . amd64 arm64 armhf i386 mips mipsel ppc64el s390x . 
unstable . -m "Rebuild with libsass1"

> Regards,
> Boyuan Yang
>...

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#887809: RFP: borgmatic -- A wrapper script for Borg backup software that creates and prunes backups

[Dan Helfman]

borgmatic author here. As a former Debian maintainer and a current 
Debian users, I care about free software too! If you find something like 
pykwalify (YAML validator using a YAML-based or similar schema) with a 
better license, I'd be happy to switch.


Thanks,

Dan

Bug#905929: sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile

[Adrian Bunk]

Source: sysdig
Version: 0.22.0-1
Severity: serious

https://buildd.debian.org/status/package.php?p=sysdig

...
cd /<>/obj-aarch64-linux-gnu/userspace/libscap && /usr/bin/cc 
-DHAS_CAPTURE -DK8S_DISABLE_THREAD -DPLATFORM_NAME=\"Linux\" 
-I/<>/common  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -ggdb   -o 
CMakeFiles/scap.dir/__/__/driver/fillers_table.c.o   -c 
/<>/driver/fillers_table.c
/<>/driver/syscall_table.c:54:3: error: '__NR_open' undeclared 
here (not in a function); did you mean 'f_sys_open_x'?
  [__NR_open - SYSCALL_TABLE_ID0] =   {UF_USED | 
UF_NEVER_DROP, PPME_SYSCALL_OPEN_E, PPME_SYSCALL_OPEN_X},
   ^

Bug#905928: RFS: phoronix-test-suite/8.0.1-2 [ITP]

[Zebulon McCorkle]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "phoronix-test-suite"

* Package name: phoronix-test-suite
  Version : 8.0.1-2
  Upstream Author : Phoronix 
* URL : https://phoronix-test-suite.com
* License : GPL-3+
  Section : utils

It builds those binary packages:

phoronix-test-suite - Benchmarking and system testing framework

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

  https://mentors.debian.net/package/phoronix-test-suite

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/phoronix-test-suite/phoronix-test-suite_8.0.1-2.dsc

More information about hello can be obtained from 
https://phoronix-test-suite.com.

Due to it downloading tests from OpenBenchmark.org, I think this belongs
in contrib.

This is a new package, and would therefore need to pass the NEW queue. I
plan on using this package to benchmark an assortment of systems, and
prefer installing with a Debian package to running a shell script any
day.

This package was removed between wheezy and jessie, and much time has
passed since then, so I completely repackaged it for the latest version.
A new version will be released soon ("Milestone 1" of 8.2.0 was released
21 days ago), so I will need an update upload sponsored then as well
(and far into the future, at least until I'm a DM; I plan on ensuring
this package doesn't get removed again).

Apologies for already bumping this to -2, I had forgotten to change the
release from UNRELEASED to unstable in the changelog, so I released -2
to fix that.

Regards,
-- 
Zebulon McCorkle
zebmccor...@asymptote.club | https://keybase.io/zebMcCorkle
803A 0F47 82AD DDEA 46BE  055F F8F9 DB8C 1A54 6398

   |
   |
__/
  __  Asymptote Club
 /(bad ASCII graph by yours truly)
 |
 |


signature.asc
Description: PGP signature

Bug#860298: undertaker: diff for NMU version 1.6.1-4.2

[Adrian Bunk]

Control: tags 860298 + patch
Control: tags 860298 + pending

Dear maintainer,

I've prepared an NMU for undertaker (versioned as 1.6.1-4.2) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

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

diff -Nru undertaker-1.6.1/debian/changelog undertaker-1.6.1/debian/changelog
--- undertaker-1.6.1/debian/changelog	2017-09-03 14:54:27.0 +0300
+++ undertaker-1.6.1/debian/changelog	2018-08-11 23:11:23.0 +0300
@@ -1,3 +1,11 @@
+undertaker (1.6.1-4.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Add the missing dependency on python-whatthepatch.
+(Closes: #860298)
+
+ -- Adrian Bunk   Sat, 11 Aug 2018 23:11:23 +0300
+
 undertaker (1.6.1-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru undertaker-1.6.1/debian/control undertaker-1.6.1/debian/control
--- undertaker-1.6.1/debian/control	2016-12-21 23:08:23.0 +0200
+++ undertaker-1.6.1/debian/control	2018-08-11 23:11:23.0 +0300
@@ -25,7 +25,7 @@
 
 Package: undertaker
 Architecture: any
-Depends: git, ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
+Depends: git, ${misc:Depends}, ${python:Depends}, python-whatthepatch, ${shlibs:Depends}
 Description: variability-aware tool for static code analysis
  The "undertaker" is a tool suite for static source code analysis for
  checking C preprocessor directives. Also included are "golem", "vampyr"

Bug#905923: debos: autopkgtest regression: m.SetShowBoot undefined

[Simon McVittie]

Control: retitle -1 debos: autopkgtest regression: missing versioned B-D for 
m.SetShowBoot

On Sat, 11 Aug 2018 at 20:45:55 +0200, Paul Gevers wrote:
> src/github.com/go-debos/debos/cmd/debos/debos.go:159:4: m.SetShowBoot
> undefined (type *fakemachine.Machine has no field or method SetShowBoot)

I contributed this feature to debos upstream. It is going to need a
versioned build-dependency on the fakemachine version that added this
method.

smcv

Bug#905921: hplip: hp-setup and hp-plugin fail to retrive key from keyserver and cannot get Laserjet1020 to work

[Brian Potkin]

Thank you for your report, hpeter.


On Sat 11 Aug 2018 at 18:18:19 +, hpeter wrote:

> Package: hplip
> Version: 3.17.10+repack0-5
> Severity: important
> 
> Dear Maintainer,
> 
> Stock or live Debian9.5 LXDE. Running hp-setup to get HP LaserJet 1020 
> working.
>   $ sudo hp-setup -i
>   ...
>   Enter option (d=download*, p=specify path, q=quit) ? d
>   ...
>   Checking for network connection...
>   Downloading plug-in from: 
>   Downloading plug-in: [\  ] 0%
>   Receiving digital keys: /usr/bin/gpg --homedir /root/.hplip/.gnupg 
> --no-permission-warning --keyserver pgp.mit.edu --recv-keys 
> 0x4ABA2F66DBD5A95894910E0673D770CDA59047B9
>   error: Unable to recieve key from keyserver
>   Do you still want to install the plug-in? (y=yes, n=no*, q=quit) ? y

Problems with plug-in installation are always the responsibility of
upstream and we will not deal with them, except to help with advice
on workarounds.

>   ...
>   error: No PPD found for model laserjet_1020 using old algorithm.
>   error: Unable to find an appropriate PPD file.
>   ...
>   error: PPD file required. Setup cannot continue. Exiting.

Never seen this before. The package has all the needed PPDs.

> Running "sudo hp-setup -i" on stock or live Ubuntu 18.04.1 works seamlessly.
> (no keyserver issue, no PPD file issue, prints a page from a pdf as expected)
> Since Ubuntu 18.04 has hplip 3.17, as opposed to 3.16 of Debian 9.5,
> I tried hplip 3.17 with Debian, by changing the apt source to testing,
> and upgraded hplip, together with its dependencies.
> Result is the same.

The Debian and Ubuntu packages are (given an inconsequential Ubuntu tweak
or two) identical. See the changelogs. I do not know where that leaves us.

Upstream is at

 https://bugs.launchpad.net/hplip/

Please inform us of the URL of your post if you contact them.

I'd purge and delete everything hplip related and try again from a
terminal. Not having the printer makes testing impossible for us.

Regards,

Brian.

Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz

[Niels Thykier]

On Thu, 05 Jul 2018 17:35:30 +0300 Lars Wirzenius  wrote:
> On Thu, 2018-07-05 at 15:06 +0200, Andreas Beckmann wrote:
> > But the upgrade path from stretch is not clean:
> > 
> >   Selecting previously unselected package python3-cliapp.
> >   Preparing to unpack .../python3-cliapp_1.20170827-1_all.deb ...
> >   Unpacking python3-cliapp (1.20170827-1) ...
> >   dpkg: error processing archive 
> > /var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb (--unpack):
> >trying to overwrite '/usr/share/man/man5/cliapp.5.gz', which is also in 
> > package python-cliapp 1.20160724-2
> >   Errors were encountered while processing:
> >/var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb
> > 
> > So you will need some Breaks and Replaces against the old
> > package in stretch.
> 
> I see the problem now. I was confused by you calling it an upgrade problem,
> when it isn't. It's a problem with one package containing the same file as
> another package, and the two packages are only tangentially related.
> 
> It doesn't seem to me to be a particularly likely scenario, to me. A user
> would need to change their sources.list to point from stretch to buster,
> and then not upgrade anything else, but install python3-cliapp.
> 
> I'll add the Breaks and Replaces some day. Or have all of cliapp removed
> from Debian.

Hi Lars,

Do you have an ETA on the upload fixing cliapp?  At the moment, cliapp
is a key package and as such a potential blocker for the new Debian release.

If you are pondering a removal (per your last sentence), the following
packages currently rely on cliapp in testing and would need to migrate
away first:

"""

Checking reverse dependencies...
# Broken Depends:

cmdtest: cmdtest
freedom-maker: freedom-maker
live-wrapper: live-wrapper
vmdb2: vmdb2
vmdebootstrap: vmdebootstrap

# Broken Build-Depends:
cmdtest: python-cliapp
freedom-maker: python3-cliapp
live-wrapper: python-cliapp
vmdb2: python3-cliapp
"""

Thanks,
~Niels

Bug#571617: multipath-tools: multipathd "switch multipath group" leads to strange state

[Chris Hofstaedtler]

Hello John,

sorry for the late reply.

* John Hughes  [180811 19:37]:
> Version: 0.4.8+git0.761c66f-7

[..]

> doing repeated "switch multipath group" commands leaves a multipath in
> a strange state with both paths "enabled".
> 
>multipathd> show multipath 35000c50012b1450f topology
>35000c50012b1450f dm-25 SEAGATE,ST373455SS
>size=68G features='0' hwhandler='0' wp=rw
>|-+- policy='round-robin 0' prio=1 status=active
>| `- 3:0:24:0 sdy  65:128 active ready running
>`-+- policy='round-robin 0' prio=1 status=enabled
>  `- 4:0:24:0 sdbc 67:96  active ready running

[..]

> Both paths are shown enabled.  Which is active?

Do you still see this behaviour in stretch and/or buster?

Thanks,
Chris

Bug#905926: squid-deb-proxy-client: ENETUNRECH on system with IPV6 and IPv4

[Lisandro Damián Nicanor Pérez Meyer]

I have just discovered the --debug switch:

$ /usr/share/squid-deb-proxy-client/apt-avahi-discover --debug
avahi-browse output:
'+;enp9s0;IPv6;apt-cacher-ng\032proxy\032on\032sirius;_apt_proxy._tcp;local
'
'+;enp9s0;IPv4;apt-cacher-ng\032proxy\032on\032sirius;_apt_proxy._tcp;local
'
'=;enp9s0;IPv4;apt-cacher-ng\032proxy\032on\032sirius;_apt_proxy._tcp;local;sirius.local;192.168.7.9;3142;
'
'=;enp9s0;IPv6;apt-cacher-ng\032proxy\032on\032sirius;_apt_proxy._tcp;local;sirius.local;fdf3:7106:c31b:0:f66d:4ff:fe8f:76a2;3142;
'
Traceback (most recent call last):
 File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 126, in

   address = get_proxy_host_port_from_avahi()
 File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 109, in
get_proxy_host_port_from_avahi
   hosts.append(AptAvahiClient(addr))
 File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 44, in
__init__
   self.connect( (addr[0], addr[1], 0, 0) )
 File "/usr/lib/python2.7/asyncore.py", line 356, in connect
   raise socket.error(err, errorcode[err])
socket.error: [Errno 101] ENETUNREACH

Bug#905927: postgresql-10 breaks pglogical autopkgtest:

[Paul Gevers]

Source: postgresql-10, pglogical
Version: postgresql-10/10.5-1
Version: pglogical/2.2.0-1
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of postgresql-10 the autpkgtest of pglogical
started to fail in unstable and testing. I copied the output of the
second test below, the fist test is killed because it times out and
doesn't seem to show anything suspicious why. Probably it doesn't handle
an error case properly and keeps waiting, because normally the test
isn't even close to the time out time (3 minutes versus 2:45 hours).

Currently this regression is delaying the migration of postgresql-10 to
testing by 13 days. Could you please investigate the situation and
assign the bug to the right package? If needed, please change severity
as appropriate.

More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pglogical/798275/log.gz

#   Failed test 'replication check 2 '
#   at
/usr/lib/postgresql/10/lib/pgxs/src/makefiles/../../src/test/perl/TestLib.pm
line 230.

#   Failed test 'replication check 3 '
#   at
/usr/lib/postgresql/10/lib/pgxs/src/makefiles/../../src/test/perl/TestLib.pm
line 230.
# Looks like you failed 2 tests of 11.

SNIP

*** tmp_check/log/*.log (last 100 lines) ***
tail: cannot open 'tmp_check/log/*.log' for reading: No such file or
directory




signature.asc
Description: OpenPGP digital signature

Bug#905926: squid-deb-proxy-client: ENETUNRECH on system with IPV6 and IPv4

[Lisandro Damián Nicanor Pérez Meyer]

Package: squid-deb-proxy-client
Version: 0.8.14
Severity: normal

Hi! While running apt update I see:

  Traceback (most recent call last):
File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 126, in 

  address = get_proxy_host_port_from_avahi()
File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 109, in 
get_proxy_host_port_from_avahi
  hosts.append(AptAvahiClient(addr))
File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 44, in 
__init__
  self.connect( (addr[0], addr[1], 0, 0) )
File "/usr/lib/python2.7/asyncore.py", line 356, in connect
  raise socket.error(err, errorcode[err])
  socket.error: [Errno 101] ENETUNREACH

Lots of times. I can't see the issue when the same machine is connected to a 
pure IPv4 network.
This is the same as running 
/usr/share/squid-deb-proxy-client/apt-avahi-discover by hand.

More info:

$ ip -c addr
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: enp9s0:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether 00:22:19:fe:4d:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.7.8/24 brd 192.168.7.255 scope global dynamic noprefixroute 
enp9s0
   valid_lft 40810sec preferred_lft 40810sec
inet6 fe80::abc6:fe30:8407:8032/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever
3: wlp12s0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether 00:22:69:21:7c:21 brd ff:ff:ff:ff:ff:ff
7: enp9s0.900@enp9s0:  mtu 1500 qdisc noqueue 
state UP group default qlen 1000
link/ether 00:22:19:fe:4d:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.3.7/24 brd 192.168.3.255 scope global noprefixroute enp9s0.900
   valid_lft forever preferred_lft forever
inet6 fe80::1669:b8f6:57fc:2e9f/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever
8: enp9s0.901@enp9s0:  mtu 1500 qdisc noqueue 
state UP group default qlen 1000
link/ether 00:22:19:fe:4d:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.4.7/24 brd 192.168.4.255 scope global noprefixroute enp9s0.901
   valid_lft forever preferred_lft forever
9: enp9s0.1@enp9s0:  mtu 1500 qdisc noqueue 
state UP group default qlen 1000
link/ether 00:22:19:fe:4d:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.2.1/24 brd 192.168.2.255 scope global noprefixroute enp9s0.1
   valid_lft forever preferred_lft forever

I do not think the VLANs are to be blamed. I hope.

Of course I'll be happy to help debugging this.

Kinds regards, Lisandro.



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

Kernel: Linux 4.17.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages squid-deb-proxy-client depends on:
ii  apt  1.6.3
ii  avahi-utils  0.7-4
ii  python   2.7.15-3

squid-deb-proxy-client recommends no packages.

squid-deb-proxy-client suggests no packages.

-- no debconf information

Bug#900240: cmake: FTBFS on hurd-i386

[Petter Reinholdtsen]

[Svante Signell]
> Currently cmake FTBFS on GNU/Hurd due to a PATH_MAX issue. Attached is
> the patch path_max.patch also provided by the first attachment in this
> bug #900240, there named path_max.path. With the attached patch and the
> upcoming bug report on linux-any, providing
> Source_Modules_FindLibUV.cmake.diff cmake builds fine. 

I tested the patch, and it seem to solve the problem.  I hope this issue
can be fixed soon, as the missing cmake is blocking a lot of builds.

But one of the 496 tests failed:

426/496 Test #426: RunCMake.CPack_DEB 
.***Failed  136.49 sec
-- CUSTOM_NAMES-COMPONENT-type - PASSED
-- CUSTOM_NAMES-COMPONENT-type-Build - PASSED
-- DEB/CUSTOM_NAMES-COMPONENT-type - PASSED
-- DEFAULT_PERMISSIONS-CMAKE_var_set-subtest-MONOLITHIC-type - PASSED
-- DEB/DEFAULT_PERMISSIONS-CMAKE_var_set-subtest-MONOLITHIC-type - PASSED
-- DEFAULT_PERMISSIONS-CMAKE_var_set-subtest-COMPONENT-type - PASSED
-- DEB/DEFAULT_PERMISSIONS-CMAKE_var_set-subtest-COMPONENT-type - PASSED
-- DEFAULT_PERMISSIONS-CPACK_var_set-subtest-MONOLITHIC-type - PASSED
-- DEB/DEFAULT_PERMISSIONS-CPACK_var_set-subtest-MONOLITHIC-type - PASSED
-- DEFAULT_PERMISSIONS-CPACK_var_set-subtest-COMPONENT-type - PASSED
-- DEB/DEFAULT_PERMISSIONS-CPACK_var_set-subtest-COMPONENT-type - PASSED
-- DEFAULT_PERMISSIONS-both_set-subtest-MONOLITHIC-type - PASSED
-- DEB/DEFAULT_PERMISSIONS-both_set-subtest-MONOLITHIC-type - PASSED
-- DEFAULT_PERMISSIONS-both_set-subtest-COMPONENT-type - PASSED
-- DEB/DEFAULT_PERMISSIONS-both_set-subtest-COMPONENT-type - PASSED
-- DEFAULT_PERMISSIONS-invalid_CMAKE_var-subtest-MONOLITHIC-type - PASSED
-- DEB/DEFAULT_PERMISSIONS-invalid_CMAKE_var-subtest-MONOLITHIC-type - PASSED
-- DEFAULT_PERMISSIONS-invalid_CMAKE_var-subtest-COMPONENT-type - PASSED
-- DEB/DEFAULT_PERMISSIONS-invalid_CMAKE_var-subtest-COMPONENT-type - PASSED
-- DEFAULT_PERMISSIONS-invalid_CPACK_var-subtest-MONOLITHIC-type - PASSED
-- DEB/DEFAULT_PERMISSIONS-invalid_CPACK_var-subtest-MONOLITHIC-type - PASSED
-- DEFAULT_PERMISSIONS-invalid_CPACK_var-subtest-COMPONENT-type - PASSED
-- DEB/DEFAULT_PERMISSIONS-invalid_CPACK_var-subtest-COMPONENT-type - PASSED
-- DEPENDENCIES-COMPONENT-type - PASSED
-- DEPENDENCIES-COMPONENT-type-Build - PASSED
-- DEB/DEPENDENCIES-COMPONENT-type - PASSED
-- EMPTY_DIR-MONOLITHIC-type - PASSED
-- EMPTY_DIR-MONOLITHIC-type-Build - PASSED
-- DEB/EMPTY_DIR-MONOLITHIC-type - PASSED
-- EMPTY_DIR-COMPONENT-type - PASSED
-- EMPTY_DIR-COMPONENT-type-Build - PASSED
-- DEB/EMPTY_DIR-COMPONENT-type - PASSED
-- VERSION-MONOLITHIC-type - PASSED
-- DEB/VERSION-MONOLITHIC-type - PASSED
-- VERSION-COMPONENT-type - PASSED
-- DEB/VERSION-COMPONENT-type - PASSED
-- EXTRA-COMPONENT-type - PASSED
-- DEB/EXTRA-COMPONENT-type - PASSED
-- GENERATE_SHLIBS-soversion_not_zero-subtest-COMPONENT-type - PASSED
-- GENERATE_SHLIBS-soversion_not_zero-subtest-COMPONENT-type-Build - PASSED
CMake Error at /home/pere/cmake-3.12.1/Tests/RunCMake/RunCMake.cmake:150 
(message):
  DEB/GENERATE_SHLIBS-soversion_not_zero-subtest-COMPONENT-type - FAILED:

  Result is [1], not [0].

  stderr does not match that expected.

  Command was:

   command> "/home/pere/cmake-3.12.1/Build/bin/cmake" 
"-DRunCMake_TEST=GENERATE_SHLIBS-soversion_not_zero-subtest-COMPONENT-type" 
"-DRunCMake_TEST_FILE_PREFIX=GENERATE_SHLIBS" 
"-DRunCMake_SUBTEST_SUFFIX=soversion_not_zero" "-DGENERATOR_TYPE=DEB" 
"-DPACKAGING_TYPE=COMPONENT" 
"-Dsrc_dir=/home/pere/cmake-3.12.1/Tests/RunCMake/CPack" 
"-Dbin_dir=/home/pere/cmake-3.12.1/Build/Tests/RunCMake/DEB/CPack/GENERATE_SHLIBS-build-soversion_not_zero-subtest"
 
"-Dconfig_file=/home/pere/cmake-3.12.1/Build/Tests/RunCMake/CPack/conf/DEB_config.cmake"
 "-P" "/home/pere/cmake-3.12.1/Tests/RunCMake/CPack/VerifyResult.cmake"

  Actual stdout:

   actual-out> 

  Expected stderr to match:

   expect-err> ^$

  Actual stderr:

   actual-err> CMake Error at 
/home/pere/cmake-3.12.1/Tests/RunCMake/CPack/DEB/Helpers.cmake:144 (message):
   actual-err>   Expected Debian control file does not exist: 'shlibs' Extra: 
install files
   actual-err>   
'/home/pere/cmake-3.12.1/Build/Tests/RunCMake/DEB/CPack/GENERATE_SHLIBS-build-soversion_not_zero-subtest/data_shlibs/usr/foo/libtest_lib.so:
   actual-err>   symbolic link to libtest_lib.so.0.8
   actual-err> 
   actual-err>   
   actual-err>   
;/home/pere/cmake-3.12.1/Build/Tests/RunCMake/DEB/CPack/GENERATE_SHLIBS-build-soversion_not_zero-subtest/data_shlibs/usr/foo/libtest_lib.so.0.8:
   actual-err>   ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), 
dynamically
   actual-err>   linked, 
BuildID[sha1]=dd4771c7b0eef02c878a458492e8b02797b12a0a, with
   actual-err>   debug_info, not stripped
   actual-err> 
   actual-err>   '; readelf "
   actual-err> 
   actual-err>   "
   actual-err> Call Stack (most recent call first):
   actual-err>   
/home/pere/cmake-3.12.1/Tests/RunCMake/CPack/tests/GENERATE_SHLIBS/VerifyResult.cmake:9
 (verifyDebControl)
   actual-err>  

Bug#897189: chromium 66 tab crash on certain sites with ublock origin

[Ryan Tandy]

Control: reopen -1
Control: found -1 68.0.3440.75-1~deb9u1

On Sat, Jul 28, 2018 at 07:49:10PM -0400, Michael Gilbert wrote:

version: 68.0.3440.75-1


I'm afraid I'm still experiencing the same tab crashes with M68 in 
stretch-security.

Bug#905925: ITP: phoronix-test-suite -- Benchmarking and system testing framework

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist

* Package name: phoronix-test-suite
  Version: 8.0.1
  Upstream author: Phoronix 
* URL: https://phoronix-test-suite.org
  License: GPL-3+
  Description: Benchmarking and system testing framework

The Phoronix Test Suite is the most comprehensive testing and benchmarking
platform available that provides an extensible framework for which new tests
can be easily added. The software is designed to effectively carry out both
qualitative and quantitative benchmarks in a clean, reproducible, and
easy-to-use manner. The Phoronix Test Suite can be used for simply comparing
your computer's performance with your friends and colleagues or can be used
within your organization for internal quality assurance purposes, hardware
validation, and continuous integration / performance management.

This package was removed between wheezy and jessie. I have completely
repackaged it. I am not a DD, so I will need a sponsor for this package.

-- 
Zebulon McCorkle
zebmccor...@asymptote.club | https://keybase.io/zebMcCorkle
803A 0F47 82AD DDEA 46BE  055F F8F9 DB8C 1A54 6398

   |
   |
__/
  __  Asymptote Club
 /(bad ASCII graph by yours truly)
 |
 |


signature.asc
Description: PGP signature

Bug#905924: bluez: Connections (such as file transfer, HID) stopped establishing but pairing works well

[Горбешко Богдан]

Package: bluez
Version: 5.50-1
Severity: normal

Dear Maintainer,

today I discovered that bluetooth connections don't establish.
They worked fine near month ago. This is definitely not the
dongle issue, as it works well on Windows machine, and
unlikely the remote devices issue, as I tried several.
Re-pairing works successfully, but other activities, such as
sending a file via bluetooth-sendto, sending via blueman,
enabling HID via blueman, initiating HID from remote device —
fail after timeout. Blueman prints the following message after
a failed file transfer:

>Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the
network connection was broken.

Output of btmon during bluetooth-sendto connection trial
attached.



-- System Information:
Debian Release: buster/sid
  APT prefers oldoldstable-updates
  APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable'), 
(500, 'testing')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_UA.UTF-8, LC_CTYPE=ru_UA.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_UA:ru (charmap=UTF-8)

Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bluez depends on:
ii  dbus  1.12.10-1
ii  kmod  25-1
ii  libasound2    1.1.6-1
ii  libc6 2.27-5
ii  libdbus-1-3   1.12.10-1
ii  libdw1    0.170-0.5
ii  libglib2.0-0  2.56.1-2
ii  libreadline7  7.0-5
ii  libudev1  239-7
ii  lsb-base  9.20170808
ii  udev  239-7

bluez recommends no packages.

Versions of packages bluez suggests:
ii  pulseaudio-module-bluetooth  11.1-5

-- no debconf information

@ MGMT Command: Stop Discovery (0x0024) plen 1  
{0x0001} [hci0] 1301.687691
Address type: 0x01
  BR/EDR
< HCI Command: Inquiry Cancel (0x01|0x0002) plen 0  
  #8 [hci0] 1301.687771
> HCI Event: Command Complete (0x0e) plen 4 
>   #9 [hci0] 1301.690051
  Inquiry Cancel (0x01|0x0002) ncmd 1
Status: Success (0x00)
@ MGMT Event: Discovering (0x0013) plen 2   
{0x0002} [hci0] 1301.690132
Address type: 0x01
  BR/EDR
Discovery: Disabled (0x00)
@ MGMT Event: Discovering (0x0013) plen 2   
{0x0001} [hci0] 1301.690132
Address type: 0x01
  BR/EDR
Discovery: Disabled (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4  
{0x0001} [hci0] 1301.690192
  Stop Discovery (0x0024) plen 1
Status: Success (0x00)
Address type: 0x01
  BR/EDR
@ RAW Open: blueman-manager version 2.22
   {0x0003} 1301.719646
@ RAW Close: blueman-manager
   {0x0003} 1301.719830
< HCI Command: Create Connection (0x01|0x0005) plen 13  
 #10 [hci0] 1301.803590
Address: xx:xx:xx:xx:xx:xx (Sony Mobile Communications Inc)
Packet type: 0xcc18
  DM1 may be used
  DH1 may be used
  DM3 may be used
  DH3 may be used
  DM5 may be used
  DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4   
>  #11 [hci0] 1301.806063
  Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
@ RAW Open: blueman-manager version 2.22
   {0x0003} 1302.719761
@ RAW Close: blueman-manager
   {0x0003} 1302.719792
@ RAW Open: blueman-manager version 2.22
   {0x0003} 1303.720970
@ RAW Close: blueman-manager
   {0x0003} 1303.721005
@ RAW Open: blueman-manager version 2.22
   {0x0003} 1304.722029
@ RAW Close: blueman-manager

Bug#905923: debos: autopkgtest regression: m.SetShowBoot undefined

[Paul Gevers]

Source: debos
Version: 1.0.0+git20180808.5b74d5d-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Since the last upload of your package the autopkgtest started to fail. I
have copied the output below.

Could you please investigate? Currently this failure is contributing to
delaying the migration to testing with 13 days.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/d/debos/798284/log.gz

autopkgtest [04:34:02]: test command1: [---
[info] Testing github.com/go-debos/debos...
[info] Source code installed by binary package, overriding
dh_auto_configure...
dh build --buildsystem=golang --with=golang
   dh_update_autotools_config -O--buildsystem=golang
   dh_autoreconf -O--buildsystem=golang
   debian/rules override_dh_auto_configure
make[1]: Entering directory
'/tmp/autopkgtest-lxc.cmzit47x/downtmp/autopkgtest_tmp'
mkdir -p "obj-x86_64-linux-gnu"
cp -a /usr/share/gocode/src "obj-x86_64-linux-gnu"
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.cmzit47x/downtmp/autopkgtest_tmp'
   dh_auto_build -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install
-gcflags=\"-trimpath=/tmp/autopkgtest-lxc.cmzit47x/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
-asmflags=\"-trimpath=/tmp/autopkgtest-lxc.cmzit47x/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
-v -p 2 github.com/go-debos/debos github.com/go-debos/debos/actions
github.com/go-debos/debos/cmd/debos github.com/go-debos/debos/recipe
github.com/surma/gocpio
github.com/go-debos/fakemachine/cpio
github.com/docker/go-units
github.com/go-debos/fakemachine
github.com/sjoerdsimons/ostree-go/pkg/glibobject
github.com/go-debos/debos
gopkg.in/yaml.v2
github.com/jessevdk/go-flags
github.com/sjoerdsimons/ostree-go/pkg/otbuiltin
github.com/go-debos/debos/actions
github.com/go-debos/debos/recipe
github.com/go-debos/debos/cmd/debos
# github.com/go-debos/debos/cmd/debos
src/github.com/go-debos/debos/cmd/debos/debos.go:159:4: m.SetShowBoot
undefined (type *fakemachine.Machine has no field or method SetShowBoot)
dh_auto_build: cd obj-x86_64-linux-gnu && go install
-gcflags=\"-trimpath=/tmp/autopkgtest-lxc.cmzit47x/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
-asmflags=\"-trimpath=/tmp/autopkgtest-lxc.cmzit47x/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
-v -p 2 github.com/go-debos/debos github.com/go-debos/debos/actions
github.com/go-debos/debos/cmd/debos github.com/go-debos/debos/recipe
returned exit code 2
make: *** [debian/rules:4: build] Error 2
autopkgtest [04:34:19]: test command1: ---]



signature.asc
Description: OpenPGP digital signature

Bug#905922: Please enable support for Sinovoip Banana Pi M3

[Bernhard]

Source: u-boot
Severity: wishlist

Hello,

It'd be great to support the Banana Pi M3.
The support for the A83t is not fully complete in the Kernel mainline.
An overview for the A83t is available at: 
http://linux-sunxi.org/Linux_mainlining_effort

Basically, the board should be booted and the installer should be started.
- HDMI is available since kernel 4.17
- USB is available since kernel 4.14

Best regards and thank you for the great support
Bernhard



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

Bug#903428: javadocs generated by javahelper include jquery

[Markus Koschany]

Hi tony,

Am 11.08.2018 um 20:12 schrieb tony mancill:
[...]
> Hi Markus,
> 
> I'm glad that you were able to discuss this directly with Matthias, and
> thank you for sharing the gist of that conversation.  For our sanity, I
> will take a look to see if we can get the severity of the lintian
> warning [1] reduced to some lower level (pedantic?) or completely
> ignored for javadoc packages.
> 
> Cheers,
> tony
> 
> [1] https://lintian.debian.org/tags/embedded-javascript-library.html

A severity of pedantic or informational would be appreciated but I guess
they won't change it. I just remembered that I build the documentation
in src:renpy from source with Sphinx and this tool also embeds jquery
and bootstrap. However Lintian still emits the warning about embedded
javascript libraries. We probably have to get used to the fact that we
will never be able to fix all Lintian warnings again (at least for some
packages).

Cheers,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#905921: hplip: hp-setup and hp-plugin fail to retrive key from keyserver and cannot get Laserjet1020 to work

[hpeter]

Package: hplip
Version: 3.17.10+repack0-5
Severity: important

Dear Maintainer,

Stock or live Debian9.5 LXDE. Running hp-setup to get HP LaserJet 1020 working.
  $ sudo hp-setup -i
  ...
  Enter option (d=download*, p=specify path, q=quit) ? d
  ...
  Checking for network connection...
  Downloading plug-in from: 
  Downloading plug-in: [\  ] 0%
  Receiving digital keys: /usr/bin/gpg --homedir /root/.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 
0x4ABA2F66DBD5A95894910E0673D770CDA59047B9
  error: Unable to recieve key from keyserver
  Do you still want to install the plug-in? (y=yes, n=no*, q=quit) ? y
  ...
  error: No PPD found for model laserjet_1020 using old algorithm.
  error: Unable to find an appropriate PPD file.
  ...
  error: PPD file required. Setup cannot continue. Exiting.

Running "sudo hp-setup -i" on stock or live Ubuntu 18.04.1 works seamlessly.
(no keyserver issue, no PPD file issue, prints a page from a pdf as expected)
Since Ubuntu 18.04 has hplip 3.17, as opposed to 3.16 of Debian 9.5,
I tried hplip 3.17 with Debian, by changing the apt source to testing,
and upgraded hplip, together with its dependencies.
Result is the same.



-- Package-specific info:
Saving output in log file: /home/user/hp-check.log

HP Linux Imaging and Printing System (ver. 3.17.10)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
dependencies are   
installed to successfully compile HPLIP.


2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball 
has the  
proper dependencies installed to successfully run.  


3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both compile- and run-time dependencies).   
   

Check types:


a. EXTERNALDEP - External Dependencies  


b. GENERALDEP - General Dependencies (required both at compile and run time)


c. COMPILEDEP - Compile time Dependencies   


d. [All are run-time checks]


PYEXT SCANCONF QUEUES PERMISSION



Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

warning: 2-9.5 version is not supported. Using 2-9.1 versions dependencies to 
verify and install...

---
| SYSTEM INFO |
---

 Kernel: 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) GNU/Linux
 Host: debian
 Proc: 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) GNU/Linux
 Distribution: 2 9.5
 Bitness: 64 bit


---
| HPLIP CONFIGURATION |
---

HPLIP-Version: HPLIP 3.17.10
HPLIP-Home: /usr/share/hplip
warning: HPLIP-Installation: Auto installation is not supported for 2 distro  
9.5 version 

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.17.10

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/hplip/HP
ppdbase=/usr/share/ppd/hplip
doc=/usr/share/doc/hplip
html=/usr/share/doc/hplip-doc
icon=no
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
pp-build=yes
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=yes
foomatic-drv-install=yes
foomatic-ppd-install=yes

Bug#905920: (no subject)

[Nazar Mokrynskyi]

Package: initramfs-tools
Version: 0.131ubuntu8
Severity: normal
Tags: security

I have fully encrypted (UEFI, LUKS, BTRFS) system and in order to avoid typing 
password for the second time after GRUB2 added `keyscript` option to 
`/etc/crypttab`.
Keyscript file is only readable by root, however, resulting `initrd.img*` file 
is readable by anyone, which I think is a security issue.
I'd like to see `initrd.img*` files to also be readable by root user only.

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 53M Aug 11 19:50 /boot/initrd.img-4.17.0-5-generic
-rw-r--r-- 1 root root 53M Aug 11 19:49 /boot/initrd.img-4.17.0-6-generic
-rw-r--r-- 1 root root 53M Aug 11 19:49 /boot/initrd.img-4.17.0-7-generic
-- /proc/cmdline
BOOT_IMAGE=/root/boot/vmlinuz-4.17.0-5-generic 
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root 
nosplash intel_pstate=disable scsi_mod.use_blk_mq=1 intel_iommu=on 
i915.fastboot=1

-- /etc/crypttab
# 
system UUID=739967f1-9770-470a-a031-8d8b8bcdb350 none 
luks,discard,keyscript=/etc/cryptroot/system.64.sh

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic-proposed
  APT policy: (500, 'cosmic-proposed'), (500, 'cosmic')
Architecture: amd64 (x86_64)

Bug#903428: javadocs generated by javahelper include jquery

[tony mancill]

On Sat, Aug 11, 2018 at 10:12:03AM +0200, Markus Koschany wrote:
> FTR: I have talked to Matthias Klose (doko) at DebConf18 about the
> embedding of jquery into javadoc packages. He pointed me to a similar
> discussion in doxygen which also embeds jquery while building doc packages.
> 
> In short he doesn't consider it to be a worthwhile task because there is
> a risk of breaking the documentation when Debian's system jquery version
> is either too old or too new. The security risk of embedding jquery is
> also rather low in this case because the documentation is static in
> contrast to web applications and it is unlikely that users would be
> affected by jquery vulnerabilities.
> 
> README.jquery in doxygen explains the problem in more detail.
> 
> https://sources.debian.org/src/doxygen/1.8.13-10/debian/README.jquery/
> 
> All in all there is no chance that a patch to change the current
> situation would be accepted, hence I no longer intend to spend time on it.

Hi Markus,

I'm glad that you were able to discuss this directly with Matthias, and
thank you for sharing the gist of that conversation.  For our sanity, I
will take a look to see if we can get the severity of the lintian
warning [1] reduced to some lower level (pedantic?) or completely
ignored for javadoc packages.

Cheers,
tony

[1] https://lintian.debian.org/tags/embedded-javascript-library.html


signature.asc
Description: PGP signature

Bug#905919: lxde: pdf opened with libreoffice despite a proper pdf app (evince) being installed

[hpeter]

Package: lxde
Version: 9
Severity: normal

Dear Maintainer,

Using a stock Debian9.5 LXDE, or the LXDE-live system from USB flash drive,
and double-clicking a pdf in the file manager (pcmanfm), it opens in 
libreoffice,
instead of the proper pdf-app (evince), which is also installed by default.
After uninstalling libreoffice, it opens in GIMP, instead of evince.

This might be misleading and errorprone for older or non-technical users,
and might be a sign of a more general issue involving file associations.

Workaround: Manually changing the file association, after each installation of 
Debian.




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

Kernel: Linux 4.9.0-7-amd64 (SMP w/2 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 lxde depends on:
ii  galculator   2.1.4-1+b1
ii  gpicview 0.2.5-2+b1
ii  leafpad  0.8.18.1-5
ii  lxappearance 0.6.3-1
ii  lxappearance-obconf  0.2.3-1
ii  lxde-core9
ii  lxde-icon-theme  0.5.1-2
ii  lxhotkey-gtk 0.1.0-1
ii  lxinput  0.3.5-1
ii  lxrandr  0.3.1-1
ii  lxsession-edit   0.5.3-2
ii  lxterminal   0.3.0-2
ii  xarchiver1:0.5.4-7

Versions of packages lxde recommends:
ii  clipit   1.4.2-1.2
ii  deluge   1.3.13+git20161130.48cedf63-3
ii  evince [pdf-viewer]  3.22.1-3+deb9u1
ii  firefox-esr [www-browser]52.9.0esr-1~deb9u1
ii  gnome-disk-utility   3.22.1-1
ii  gnome-system-tools   3.0.0-6
ii  gucharmap1:9.0.2-1
ii  lightdm [x-display-manager]  1.18.3-1
ii  lxmusic  0.4.7-1
ii  lxpolkit 0.5.3-2
ii  menu-xdg 0.5
ii  smplayer 16.11.0~ds0-1+deb9u1
ii  usermode 1.109-1+b2
ii  wicd 1.7.4+tb2-4
ii  xserver-xorg 1:7.7+19

Versions of packages lxde suggests:
ii  gimp 2.8.18-1+deb9u1
pn  libreoffice  
ii  lxlauncher   0.2.5-1
ii  lxtask   0.1.8-1
pn  pidgin   
pn  pk-update-icon   
pn  xfce4-power-manager  

-- no debconf information

Bug#905732: kernel-package: fails to create debian directory (/bin/sh: 1: [: -lt: unexpected operator)

[Claude Heiland-Allen]

On 08/08/18 19:37, Claude Heiland-Allen wrote:

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

.../linux-4.18-rc8$ make-kpkg --rootcmd=fakeroot -j 32 --initrd kernel_image 
--verbose

* What was the outcome of this action?

The build failed after a couple of seconds, with errors from /bin/sh along the 
way.



Worked (albeit slowly) without  -j 32.  To be precise, this worked:

.../linux-4.18-rc8$ make-kpkg --rootcmd=fakeroot --initrd kernel_image

Bug#905384: libmuscle does not build any more - probably some issue of newer automake

[Adrian Bunk]

On Sat, Aug 11, 2018 at 08:15:20AM +0200, Andreas Tille wrote:
> Hi,
> 
> libmuscle[1] was bilding fine in several uploads but when I now
> try to rebuild to fix #904690 I get:
> 
> ...
> dh_auto_build --no-parallel
> make -j1
> make[2]: Entering directory '/build/libmuscle-3.7+4565'
> Making all in libMUSCLE
> make[3]: Entering directory '/build/libmuscle-3.7+4565/libMUSCLE'
> g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
> -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT
> _H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 
> -DLT_OBJDIR=\".libs/\" -DSTDC_HEADERS=
> 1 -DTIME_WITH_SYS_TIME=1 -I. -I..  -Wdate-time -D_FORTIFY_SOURCE=2 -O2 
> -funroll-loops -fomit-frame-pointer -ftree-vectorize  -DNDEBUG=1  -fopenmp -g 
> -O2 -fdebug-prefix-map=/build/libmuscle-
> 3.7+4565=. -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> main.o main.cpp
> make[3]: *** No rule to make target '../libMUSCLE/libMUSCLE.la', needed by 
> 'muscle'.  Stop.
> make[3]: Leaving directory '/build/libmuscle-3.7+4565/libMUSCLE'
> ...
> 
> 
> I suspect an issue in libMUSCLE/Makefile.am.  Any hint how to fix this?

Fix is attached.

The triggering change for the FTBFS was automake 1.16, but this was an 
old bug. The --no-parallel in debian/rules was a workaround for the same
bug and can now be dropped.

> Kind regards
> 
>   Andreas.

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

Description: Correct the libMUSCLE.la dependency
 This allows automake to generate proper dependencies.
Author: Adrian Bunk 

--- libmuscle-3.7+4565.orig/libMUSCLE/Makefile.am
+++ libmuscle-3.7+4565/libMUSCLE/Makefile.am
@@ -36,6 +36,6 @@ bin_PROGRAMS = muscle
 
 
 muscle_SOURCES = main.cpp
-muscle_LDADD = $(top_builddir)/libMUSCLE/libMUSCLE.la
+muscle_LDADD = libMUSCLE.la
 
 

Bug#862884: Disable libnm-glib support

[Mike Miller]

On Sat, Aug 11, 2018 at 17:08:54 +0200, Michael Biebl wrote:
> To finish off the libnm-glib transition (nm-openconnect being the last
> package at [1]), I decided to prepare an NMU and upload to DELAYED/7
> 
> While at it, I've also included the changes for #852705 and #852706.
> Full debdiff attached.
> 
> Please holler if you want me to cancel the NMU and you want to make a
> maintainer upload instead.

No, thank you for taking care of this, looks good.

-- 
mike


signature.asc
Description: PGP signature

Bug#905908: libGL.so.1: cannot open shared object file: No such file or directory when updating to 4.4.1~rc2-3

[Mike Miller]

On Sat, Aug 11, 2018 at 16:00:18 +0200, Kyle Robbertze wrote:
> When updating octave to 4.4.1~rc2-3, I received the following error:
> 
> Setting up octave (4.4.1~rc2-3) ...
> /usr/bin/octave-cli: error while loading shared libraries: libGL.so.1: cannot 
> open shared object file: No such file or directory
> dpkg: error processing package octave (--configure):
>  installed octave package post-installation script subprocess returned error 
> exit status 127
> 
> It appears to be missing a dependency on a package that provides libGL.

That's odd, because that package is exactly

> ii  libgl1 1.0.0+git20180308-4

Can you check the contents of the package on your system?

$ ldconfig -p | grep libGL.so.1
libGL.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so.1
$ ls -lgo /usr/lib/x86_64-linux-gnu/libGL.so.*
lrwxrwxrwx 1 14 Aug  8 03:41 /usr/lib/x86_64-linux-gnu/libGL.so.1 -> 
libGL.so.1.7.0
-rw-r--r-- 1 575816 Aug  8 03:41 /usr/lib/x86_64-linux-gnu/libGL.so.1.7.0
$ dpkg -S /usr/lib/x86_64-linux-gnu/libGL.so.*
libgl1:amd64: /usr/lib/x86_64-linux-gnu/libGL.so.1
libgl1:amd64: /usr/lib/x86_64-linux-gnu/libGL.so.1.7.0

-- 
mike


signature.asc
Description: PGP signature

Bug#905918: caffeine not inhibiting screensaver

[Michael]

Package: caffeine
Version: 2.9.4-1
Severity: normal

Hi, 
( Disclaimer: This is my first time using reportbug so I'm sorry for any 
beginners mistakes. )

Caffeine hasn't been inhibiting xscreensaver since I first set up this laptop. 

When running manually I get logs like

"matschi@errors:~$ caffeine
  INFO:root:caffeine is inhibiting desktop idleness
  Protocol error: bad 3 (Window); Sequence Number 11
   Opcode (20, 0) = GetProperty
   Bad resource 0 (0x0)
   at -e line 15.
INFO:root:caffeine is no longer inhibiting desktop idleness"

This happens in single as well as multi screen mode. 

I found a similar bug at launchpad.net and also added my report there:
https://bugs.launchpad.net/caffeine/+bug/1700419


My xscreensaver is v 5.36-1, 
 settings: 
   * blank only
   * power management enabled
   * quick power off in Blank Only Mode

As DE I use xfce4 
   * display power management disabled in xfce4-powermanager
   
   xfce4 pkg list : https://pastebin.com/mEtQkU6P

Thanks for your effort and time, 
Michael

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (999, 'testing'), (500, 'stable-updates'), (500, 
'oldstable-updates'), (500, 'oldoldstable-updates'), (103, 'unstable'), (102, 
'stable'), (101, 'oldstable'), (100, 'oldoldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages caffeine depends on:
ii  gir1.2-appindicator3-0.1  0.4.92-6
ii  gir1.2-gtk-3.03.22.30-2
ii  python3   3.6.5-3
ii  python3-ewmh  0.1.6-1
ii  python3-gi3.28.2-1+b1
ii  python3-pkg-resources 39.2.0-1
ii  python3-xlib  0.23-2
ii  xdg-utils 1.1.3-1

caffeine recommends no packages.

caffeine suggests no packages.

-- no debconf information

Bug#905917: New upstream version available with support for view-template

[Emanuele Aina]

Package: jenkins-job-builder
Version: 2.0.3-3
Severity: wishlist

Upstream version 2.2.1 is available, but what I'm really interested
about is the commit introducing support for `view-template`, which is
shipped starting from version 2.0.8:

https://git.openstack.org/cgit/openstack-infra/jenkins-job-builder/commit/?id=418e7c628d5ce

Is there any plan to upload a new version?

Thanks!

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

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

Versions of packages jenkins-job-builder depends on:
ii  python3  3.6.6-1
ii  python3-jenkins-job-builder  2.0.3-3

jenkins-job-builder recommends no packages.

jenkins-job-builder suggests no packages.

-- no debconf information
-- 
Emanuele Aina
www.collabora.com

Bug#815164: Welcome to

[Firelip Bjeg]

Hi, My Name is Albert MItchell (racineLLC Corporation)
Please i need to talk with someone from Support Team.
Thanks

Bug#804190: please support cross compiler builds without relying on binutils-multiarch

[Helmut Grohne]

Control: reassign -1 src:gcc-8
Control: tags -1 + patch

Hi Matthias,

I've updated the patch now. It has become fairly trivial.

We added support for "X-DH-Build-For-Type: target" a while ago. That
flag alone makes dh_strip choose the right tooling.

So whenever debhelper is recent enough, we can just skip the
binutils-multiarch dependency.

On Fri, Nov 13, 2015 at 12:20:14AM +0100, Matthias Klose wrote:
>  - please update the patch to apply to the current VCS

Please tell me where to find the current VCS. I've attached a patch
against the version in unstable anyhow.

>  - the patch is incomplete.  It still calls the binutils tools
>for the host unprefixed.

This is solved by X-DH-Build-For-Type.

>  - maybe make it clear which tools are used (target_strip, host_strip
>instead of cross_strip).

No cross_strip is needed at all anymore as X-DH-Build-For-Type has taken
care of this.

> I think that the rather simplistic view of dh_strip should be addressed in
> this context too, always using the non-prefixed binutils tools.  In GCC you
> don't have binary packages anymore with both host and target objects within
> the same binary package, however this is not guaranteed for other binary
> packages. So you need to find a way to strip host and target objects in the
> same binary package.

I didn't encounter a single binary package that ships both host and
target objects. Whenever they do, we can simply split the packages.
debhelper and dh_strip now support selecting host vs. target per binary
package and we're actively using that support since gcc-7.

Helmut
--- a/debian/rules.conf
+++ b/debian/rules.conf
@@ -221,7 +221,7 @@
   endif
 endif
 ifeq ($(DEB_CROSS),yes)
-  BINUTILS_BUILD_DEP = binutils$(TS)$(NT) (>= $(BINUTILSBDV)), binutils-multiarch$(NT) (>= $(BINUTILSBDV))
+  BINUTILS_BUILD_DEP = binutils$(TS)$(NT) (>= $(BINUTILSBDV)), debhelper (>= 10.10.6~) | binutils-multiarch$(NT) (>= $(BINUTILSBDV))
   BINUTILSV := $(shell dpkg -l binutils$(TS) \
 			| awk '/^ii/{print $$3;exit}' | sed 's/-.*//')
 else

Bug#905916: pam: diff for NMU version 1.1.8-3.8

[Niels Thykier]

Package: pam
Version: 1.1.8-3.7
Severity: normal
Tags: patch  pending


Dear maintainer,

I've prepared an NMU for pam (versioned as 1.1.8-3.8) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -u pam-1.1.8/debian/changelog pam-1.1.8/debian/changelog
--- pam-1.1.8/debian/changelog
+++ pam-1.1.8/debian/changelog
@@ -1,3 +1,24 @@
+pam (1.1.8-3.8) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Set Rules-Requires-Root to binary-targets as pam relies on
+chgrp in debian/rules.
+  * Update pam-auth-update to detect write errors and properly
+fail when that happens.  (Closes: #880501)
+  * Remove Roger Leigh from uploaders as he has restired from
+Debian.  (Closes: #869348)
+  * Reduce priority of libpam0g to optional.
+  * Rebuild with a recent version of dpkg-source, which ensures
+that the Build-Depends are correct in the .dsc file.
+(Closes: #890602)
+  * Apply patch from Felix Lechner to make pam-auth-update ignore
+editor backup files.  (Closes: #519361)
+  * Apply update to Brazilian Portuguese translations of the
+debconf templates.  Thanks to Adriano Rafael Gomes.
+(Closes: #799417)
+
+ -- Niels Thykier   Sat, 11 Aug 2018 15:31:24 +
+
 pam (1.1.8-3.7) unstable; urgency=medium
 
   * Non-maintainer upload.
@@ -385,7 +406,7 @@
 - Add support for NSS groups to pam_group.  Closes: #589019,
   LP: #297408.
 - Support cross-building the package.  Thanks to Neil Williams
-   for the patch.  Closes: #284854.   
+   for the patch.  Closes: #284854.
   * debian/rules: pass getconf LFS_CFLAGS so that we get a 64-bit rlimit
 interface.  Closes: #579402.
   * Drop patches conditional_module,_conditional_man and
@@ -700,7 +721,7 @@
   * Fix lintian overrides for libpam-runtime
   * Overrides for lintian finding quilt patches
   * pam_mail-fix-quiet: patch from Andreas Henriksson
-applied upstream to fix quiet option of pam_mail, Closes: #439268 
+applied upstream to fix quiet option of pam_mail, Closes: #439268
 
   [ Dustin Kirkland ]
   * debian/patches/update-motd: run the update-motd scripts in pam_motd;
@@ -708,7 +729,7 @@
 
   [ Sam Hartman ]
   * cve-2009-0887-libpam-pam_misc.patch: avoid integer signedness problem
-(CVE-2009-0887) (Closes: #520115) 
+(CVE-2009-0887) (Closes: #520115)
 
  -- Steve Langasek   Thu, 06 Aug 2009 17:54:32 +0100
 
@@ -730,7 +751,7 @@
 - Swedish, thanks to Martin Bagge  (closes: #518324)
 - Vietnamese, thanks to Clytie Siddall 
   (closes: #518329)
-- Japanese, thanks to Kenshi Muto  (closes: #518335) 
+- Japanese, thanks to Kenshi Muto  (closes: #518335)
 - Slovak, thanks to Ivan Masár  (closes: #518341)
 - Czech, thanks to Miroslav Kure  (closes: #518992)
 - Portuguese, thanks to Américo Monteiro 
@@ -748,14 +769,14 @@
 pam (1.0.1-7) unstable; urgency=low
 
   * 027_pam_limits_better_init_allow_explicit_root:
-- fix the patch so that our limit resets are actually *applied*, 
+- fix the patch so that our limit resets are actually *applied*,
   which has apparently been broken for who knows how long!
 - shadow the finite kernel defaults for RLIMIT_SIGPENDING and
   RLIMIT_MSGQUEUE as well, so that the preceding change doesn't
   suddenly expose systems to DoS or other issues.
-- include documentation in the patch, giving examples of how to set 
+- include documentation in the patch, giving examples of how to set
   limits for root.  Thanks to Jonathan Marsden.
-  * pam-auth-update: swap out known md5sums from intrepid pre-release 
+  * pam-auth-update: swap out known md5sums from intrepid pre-release
 versions with the md5sums from the released intrepid version
   * pam-auth-update: set the umask, so we don't accidentally mark
 /etc/pam.d/common-* unreadable.  Thanks to Martin Krafft for catching.
@@ -806,7 +827,7 @@
 - Czech, thanks to Miroslav Kure <
   (closes: #510608)
 - French, thanks to Steve Petruzzello 
-- German, thanks to Sven Joachim  (closes: #510617)  
+- German, thanks to Sven Joachim  (closes: #510617)
 - Basque, thanks to Piarres Beobide 
   (closes: #510699)
 - Russian, thanks to Yuri Kozlov  (closes: #510701)
@@ -1347,7 +1368,7 @@
 pam (0.79-3.2) unstable; urgency=low
 
   * Non-maintainer upload to fix important bug, that makes passwd segfault
-when CTRL-D is pressed at the password prompt.  Applied the patch 
+when CTRL-D is pressed at the password prompt.  Applied the patch
 provided by Dann Frazier.  (Closes: #360657)
 
  -- Margarita Manterola   Sat,  5 Aug 2006 02:11:22 -0300
@@ -1453,7 +1474,7 @@
 pam (0.76-21) unstable; urgency=medium
 
   * Fix patch 055 again because -20 was broken and didn't actually fix the
-problem. 
+problem.
 
  -- Sam Hartman   Tue,  4 May 2004 21:37:38 -0400
 
@@ -1464,22 +1485,22 @@
   * Medium urgency because the version now in testing has confusing and
 

Bug#905915: subtitleeditor: sometimes gets stuck when hitting key to play video

[cacatoes]

Package: subtitleeditor
Version: 0.54.0-3

Hi,

This bug may not be obvious to reproduce, but after using the app for
some time (10-30 mins), it happens the GUI gets frozen right after some
'play' command is issued. I use a shortcut for play current selection.
The video is not played, and most parts of the apps turn unresponsive,
including the menu options which are greyed out. We can't save the work
so it's lost.

In the terminal, it produces and repeats these messages, which may not
be related:

[...]
(subtitleeditor:22468): GLib-WARNING **: 17:11:58.103: corrupted
double-linked list detected

(subtitleeditor:22468): GLib-WARNING **: 17:12:36.575: corrupted
double-linked list detected
[...]

I might be able to provide more informations if there is a way to debug
this.

Regards,

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

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

Versions of packages subtitleeditor depends on:
ii  gstreamer1.0-plugins-base   1.14.2-1
ii  gstreamer1.0-plugins-good   1.14.2-1
ii  gstreamer1.0-x  1.14.2-1
ii  libatkmm-1.6-1v52.24.2-3
ii  libc6   2.27-5
ii  libcairomm-1.0-1v5  1.12.2-3
ii  libgcc1 1:8.2.0-3
ii  libglib2.0-02.56.1-2
ii  libglibmm-2.4-1v5   2.56.0-2
ii  libgstreamer-plugins-base1.0-0  1.14.2-1
ii  libgstreamer1.0-0   1.14.2-2
ii  libgstreamermm-1.0-11.10.0+dfsg-2
ii  libgtk-3-0  3.22.30-2
ii  libgtkmm-3.0-1v53.22.2-2
ii  libpangomm-1.4-1v5  2.40.1-4
ii  libsigc++-2.0-0v5   2.10.0-2
ii  libstdc++6  8.2.0-3
ii  libsubtitleeditor0  0.54.0-3

subtitleeditor recommends no packages.

Versions of packages subtitleeditor suggests:
pn  gstreamer1.0-libav  

-- no debconf information

Bug#905914: dput internal error about non-ascii chars in source package

[Harald Dunkel]

Package: dput
Version: 1.0.2

I downloaded Stéphane's lxc-template source package [1], built it for
sid and tried to dput it into my local repository. Result:

{harri@cecil:tmp () 508} dput sid lxc-templates_3.0.0-0ubuntu1_amd64.changes
Traceback (most recent call last):
  File "/usr/bin/dput", line 11, in 
load_entry_point('dput==1.0.2', 'console_scripts', 'execute-dput')()
  File "/usr/share/dput/dput/dput.py", line 1014, in main
config, check_only, check_version, unsigned_upload, debug)
  File "/usr/share/dput/dput/dput.py", line 344, in verify_files
changes = parse_changes(chg_fd)
  File "/usr/share/dput/dput/dput.py", line 69, in parse_changes
check = chg_fd.read(5)
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 315: 
ordinal not in range(128)


According to #876671 this is not supposed to happen.


Regards
Harri

[1] 
http://archive.ubuntu.com/ubuntu/pool/universe/l/lxc-templates/lxc-templates_3.0.0-0ubuntu1.dsc

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Mar 2018 23:45:00 -0400
Source: lxc-templates
Binary: lxc-templates
Architecture: source amd64
Version: 3.0.0-0ubuntu1
Distribution: bionic
Urgency: medium
Maintainer: Ubuntu Developers 
Changed-By: Stéphane Graber 
Description:
 lxc-templates - Linux Containers userspace tools (templates)
Changes:
 lxc-templates (3.0.0-0ubuntu1) bionic; urgency=medium
 .
   * New upstream release
 - lxc-templates is now its own project.
 - Announcement: https://linuxcontainers.org/lxc/news/
Checksums-Sha1:
 b6e9955c8cca3c906a495dbea1450c36b9666d3f 1739 lxc-templates_3.0.0-0ubuntu1.dsc
 53d00206b58921aeddb2a1612ac3294b3a66cc97 255781 lxc-templates_3.0.0.orig.tar.gz
 a181f3331abd4fdf3a61c9909aaad9300defd372 833 
lxc-templates_3.0.0.orig.tar.gz.asc
 102e0b16afa6e9acfe6309337335e393935696a7 56536 
lxc-templates_3.0.0-0ubuntu1.debian.tar.xz
 fad68e72eaf11d51398111b532e46ffc3a0ded4d 5350 
lxc-templates_3.0.0-0ubuntu1_amd64.buildinfo
 e3fbefc990c2c6527819b5c6c432da97722be56d 82712 
lxc-templates_3.0.0-0ubuntu1_amd64.deb
Checksums-Sha256:
 1e3328929e7d41b71b2a26648e946d1549b86beb5eeb1a082422f61609638911 1739 
lxc-templates_3.0.0-0ubuntu1.dsc
 e22b5d602d080ef4e7746a8d8cc3e445ab080c1d2a28a5c570a07a5b493188fd 255781 
lxc-templates_3.0.0.orig.tar.gz
 909e666141097473417bb0a2594a2b890a39a1f0cb2d6b87349a4a75f885be7c 833 
lxc-templates_3.0.0.orig.tar.gz.asc
 0b34acfbcd28a842dac4d9778c20e8571106a44895dbe274b637169477dd 56536 
lxc-templates_3.0.0-0ubuntu1.debian.tar.xz
 1d4f3144bee384dfcad16e17c634ff868a344a718668529bb8bd124fc0eb19d9 5350 
lxc-templates_3.0.0-0ubuntu1_amd64.buildinfo
 411ee188f39c9e02c84ac18b7d5cf144d226939f997392afb7afd68baa826446 82712 
lxc-templates_3.0.0-0ubuntu1_amd64.deb
Files:
 6406b1501dcfa987e370d06a528d1a6c 1739 admin optional 
lxc-templates_3.0.0-0ubuntu1.dsc
 0336196415de03c3264315feac5917bc 255781 admin optional 
lxc-templates_3.0.0.orig.tar.gz
 724e3800ccd10a6948e7feb575dc42e3 833 admin optional 
lxc-templates_3.0.0.orig.tar.gz.asc
 dd1b3f0e8db9be287b3e962869033f5c 56536 admin optional 
lxc-templates_3.0.0-0ubuntu1.debian.tar.xz
 901f17887edc8b0009f634882bb0b213 5350 admin optional 
lxc-templates_3.0.0-0ubuntu1_amd64.buildinfo
 63bf826d9f947683530662d803ae4822 82712 admin optional 
lxc-templates_3.0.0-0ubuntu1_amd64.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEH2V614LbR/u1O+a1Cp4qnmbTgcsFAltu9rsACgkQCp4qnmbT
gcuiTgf/b6XoSNQYbCg8PYQLCxTb2dT/BlRK//kN1XwLblXV0LhxBurH/wJEBpbH
eyEeVoikXT6ZjjwUt2X040z2RQJoaMU3BwZCTvMGSV9IXJOH2AtFIHmpXW8/Ley7
7SNbHw2Yg4y4dLAewqGYq+e46dHqffDOEX1YuKEeMwv9bxTfJU7m/P/MZ2tNqppi
p0+8zeWDLHm2qK3Vjov4H54Q76YKtZUn5CV6QLvOCspJgqZK2MXkb69QuVsvEKcS
2ZFdQKkOY54lOsggmeuLXoUy8ihe5Bhzr/1y2A/N+Z2K+ThAmVF+LOxvnYahbQME
Q9FvntwXSqyqJBuH+/qERoHwpIFOZw==
=DQS7
-END PGP SIGNATURE-

Bug#905435: vim: please add riscv64 to syntax module for debian/control

[James McCoy]

On Sat, Aug 04, 2018 at 04:30:14PM +0200, Reiner Herrmann wrote:
> when using riscv64 in the Architecture field in debian/control, vim
> highlights it as invalid (red background).
> Please add riscv64 to the list of recognized architectures, like in
> the attached patch.

Applied in the vim-debian repo and sent upstream.  Will close once it's
in the Vim package.

Thanks,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#905913: Don't install into testing

[Jörg Frings-Fürst]

Source: sane-backends
Version: 1.0.27-1~experimental6
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

don't install 1.0.27-1~experimental6 into testing.


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.17.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)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAltu/BsACgkQCfifPIyh
0l31yBAAwJ7jxhCcqLrIj92rSTZOUhimcGX2O6qiIk39ftpnjonBOxFUM0cVZq/5
X8TJnPj98Yo0Gd7mtNqRWSvmn4YW12D9jRwagpGzEOG2d5qiuGzMpATJT5vm8MJm
VlA+FzhHX53NDRefgBicWKfdLTNb1cnlS0M8Tj6LsFU6OccnFTMHoXJCHBfRUluM
TDHQnI0A4gkBGDKW/Gc44A6jyl5Lyf6Uk47Yv9iXhMNB2KgdDH8uZC4SIWU5hmok
O65o5ll5FgR8yLY2X35vcxZ8mD+stR17z1tyo0n1sR8tjgDSakjA1+f1KRnsgp6t
iVm7DsWgK92JbFdEhgn1IY8PibSjnt2N0hq4GMER/tjEzEN3Fyog4ZU6YzD7OXZ8
nM9XbTYCjAJ+Kh1q4Xn8Qz3w7vG3q1iUq4XIgE+grBY8dn+CVP6R7tVWQhzkebEK
JdNdNTfeS+ijzVhTpk8Nzpz/PuabL5HLTunx3a+Kk2gS+bsPed/RC0ojCFbKWjFl
UlhzmJvzCwUEyI8ssGF9LFFFhPZmRvKgzU4Dk5X4kDGp6wB+kh3xHn1MSGqsmgoy
d2PhUT9hmtIFj6kobJe3cCEgMqi2PjhL1WOgP7L9AIT0QwL8sfCtM5p5gT5zGBGW
+Bbq7EUpqVDVU4zNnFGlUryKReBniJ71gnOgrL9RDaAolnumXWc=
=ZZ97
-END PGP SIGNATURE-

Bug#580312: multipath-tools: multipathd segfaults when restarted

[Chris Hofstaedtler]

Vincent,

* Vincent McIntyre  [180811 15:09]:
> Package: multipath-tools
> Version: 0.4.8-14+lenny2
> Severity: normal
> 
> I have a simple setup with a Promise VTrak E610f direct-connected
> to a Dell 2950 with LSI FC949SE card. There is only one FC connection.
> Two LUNs are exposed by the Promise.
> 
> # multipath -l
> mpath1 (2227300015530e20d) dm-1 Promise ,VTrak E610f [size=13T][features=1
> queue_if_no_path][hwhandler=0]
> \_ round-robin 0 [prio=0][active]
>  \_ 0:0:0:1 sdf 8:80  [active][undef]
>  mpath0 (2228f000155e2acda) dm-0 Promise ,VTrak E610f
>  [size=13T][features=1 queue_if_no_path][hwhandler=0]
>  \_ round-robin 0 [prio=0][active]
>   \_ 0:0:0:0 sda 8:0   [active][undef]
> 
> When rebooting, or sometimes doing /etc/init.d/multipath-tools restart,
> multipathd segfaults, e.g.
>   kernel: [  511.240204] multipathd[6331]: segfault at 00645a68 ip 
> 7ffe3777ea0e sp 4000fd30 error 4 in libc-2.7.so[7ffe3770b000+14a000]
> 
> and another
>   kernel: [ 1150.730222] multipathd[6379]: segfault at a ip 7f02665569fb sp 
> 7fffe0a0 error 4 in libc-2.7.so[7f02664e3000+14a000]
> 
> It doesn't occur reliably.

Do you still see this in current versions?

Thanks,
Chris

Bug#862884: Disable libnm-glib support

[Michael Biebl]

Hi mike

On Sat, 14 Apr 2018 00:45:10 -0700 Mike Miller  wrote:
> On Sat, Apr 14, 2018 at 01:02:45 +0200, Michael Biebl wrote:
> > I intend to upload a new version of network-manager soonish which will
> > drop libnm-glib/libnm-util. I'm thus bumping this issue to RC in
> > preparation for that.
> 
> Thanks for the reminder and lighting a fire, will do.

To finish off the libnm-glib transition (nm-openconnect being the last
package at [1]), I decided to prepare an NMU and upload to DELAYED/7

While at it, I've also included the changes for #852705 and #852706.
Full debdiff attached.

Please holler if you want me to cancel the NMU and you want to make a
maintainer upload instead.

Regards,
Michael

[1]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia-maintain...@lists.alioth.debian.org;tag=libnm
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff -Nru network-manager-openconnect-1.2.4/debian/changelog 
network-manager-openconnect-1.2.4/debian/changelog
--- network-manager-openconnect-1.2.4/debian/changelog  2016-12-09 
06:05:50.0 +0100
+++ network-manager-openconnect-1.2.4/debian/changelog  2018-08-11 
16:34:05.0 +0200
@@ -1,3 +1,13 @@
+network-manager-openconnect (1.2.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable libnm-glib support (Closes: #862884, #898661)
+  * Install AppData file (Closes: #852705)
+  * Move libnm-vpn-plugin-openconnect and translations into main package
+(Closes: #852706)
+
+ -- Michael Biebl   Sat, 11 Aug 2018 16:34:05 +0200
+
 network-manager-openconnect (1.2.4-1) unstable; urgency=medium
 
   * New upstream version 1.2.4
diff -Nru network-manager-openconnect-1.2.4/debian/control 
network-manager-openconnect-1.2.4/debian/control
--- network-manager-openconnect-1.2.4/debian/control2016-12-09 
06:00:27.0 +0100
+++ network-manager-openconnect-1.2.4/debian/control2018-08-11 
16:34:05.0 +0200
@@ -6,14 +6,10 @@
intltool,
libglib2.0-dev,
libgtk-3-dev,
-   libnm-dev,
-   libnm-glib-dev (>= 1.2.0),
-   libnm-glib-vpn-dev (>= 1.2.0),
-   libnm-util-dev (>= 1.2.0),
+   libnm-dev (>= 1.2.0),
libopenconnect-dev,
libsecret-1-dev,
-   libxml2-dev,
-   network-manager-dev (>= 1.2.0)
+   libxml2-dev
 Standards-Version: 3.9.8
 Vcs-Browser: 
https://anonscm.debian.org/cgit/collab-maint/network-manager-openconnect.git
 Vcs-Git: 
https://anonscm.debian.org/git/collab-maint/network-manager-openconnect.git
@@ -26,6 +22,8 @@
  openconnect,
  ${misc:Depends},
  ${shlibs:Depends}
+Breaks: network-manager-openconnect-gnome (<< 1.2.4-1.1)
+Replaces: network-manager-openconnect-gnome (<< 1.2.4-1.1)
 Description: network management framework (OpenConnect plugin core)
  NetworkManager is a system network service that manages your network devices
  and connections, attempting to keep active network connectivity when
diff -Nru 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect-gnome.install
 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect-gnome.install
--- 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect-gnome.install
  2016-12-09 06:00:27.0 +0100
+++ 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect-gnome.install
  2018-08-11 16:34:05.0 +0200
@@ -1,4 +1,4 @@
-usr/lib/*/NetworkManager/*.so
+usr/lib/*/NetworkManager/libnm-vpn-plugin-openconnect-editor.so
 usr/lib/NetworkManager/nm-openconnect-auth-dialog
+usr/share/appdata/network-manager-openconnect.metainfo.xml
 usr/share/gnome-vpn-properties
-usr/share/locale
diff -Nru 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect.install 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect.install
--- 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect.install
2016-12-09 06:00:27.0 +0100
+++ 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect.install
2018-08-11 16:34:05.0 +0200
@@ -1,3 +1,5 @@
 etc
 usr/lib/NetworkManager/VPN/nm-openconnect-service.name
 usr/lib/NetworkManager/nm-openconnect-service*
+usr/lib/*/NetworkManager/libnm-vpn-plugin-openconnect.so
+usr/share/locale
diff -Nru 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect.maintscript
 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect.maintscript
--- 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect.maintscript
1970-01-01 01:00:00.0 +0100
+++ 
network-manager-openconnect-1.2.4/debian/network-manager-openconnect.maintscript
2018-08-11 16:34:05.0 +0200
@@ -0,0 +1 @@
+rm_conffile /etc/NetworkManager/VPN/nm-openconnect-service.name 1.2.4-1.1~
diff -Nru 

Bug#905912: linux-image-3.16.0-6-amd64: Fails to mount SMB share using mount.cifs

[Takashi Yoshi]

Package: src:linux
Version: 3.16.57-2
Severity: normal

Dear Maintainer,

With the kernel 3.16.0-6 on Debian jessie I cannot mount my SMB shares anymore
using mount.cifs on the command line.
It does work fine if I reboot to 3.16.0-5.

Mounting fails with "BUG: unable to handle kernel NULL pointer dereference at
0058" in dmesg.



-- Package-specific info:
** Version:
Linux version 3.16.0-6-amd64 (debian-ker...@lists.debian.org) (gcc version
4.9.2 (Debian 4.9.2-10+deb8u1) ) #1 SMP Debian 3.16.57-2 (2018-07-14)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-6-amd64 root=/dev/mapper/vg01-root ro quiet

** Tainted: D (128)
 * Kernel has oopsed before.

** Kernel log:
[   18.955350] EXT4-fs (dm-1): re-mounted. Opts: (null)
[   19.094955] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
[   19.813136] lp0: using parport0 (interrupt-driven).
[   19.917354] fuse init (API version 7.23)
[   20.212870] Adding 9539580k swap on /dev/mapper/vg01-swap_1.  Priority:-1
extents:1 across:9539580k FS
[   20.513526] EXT4-fs (sda1): mounting ext2 file system using the ext4
subsystem
[   20.525119] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
[   20.557456] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts:
(null)
[   21.463205] RPC: Registered named UNIX socket transport module.
[   21.463211] RPC: Registered udp transport module.
[   21.463214] RPC: Registered tcp transport module.
[   21.463217] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   21.503812] FS-Cache: Loaded
[   21.557305] FS-Cache: Netfs 'nfs' registered for caching
[   21.639155] Installing knfsd (copyright (C) 1996 o...@monad.swb.de).
[   25.366951] systemd-logind[2022]: New seat seat0.
[   25.382056] systemd-logind[2022]: Watching system buttons on
/dev/input/event2 (Power Button)
[   25.382234] systemd-logind[2022]: Watching system buttons on
/dev/input/event1 (Power Button)
[   27.490434] systemd-logind[2022]: Failed to start user service: Unknown
unit: user@1000.service
[   27.501213] systemd-logind[2022]: New session 1 of user user.
[   50.139474] Key type dns_resolver registered
[   50.193033] FS-Cache: Netfs 'cifs' registered for caching
[   50.193120] Key type cifs.spnego registered
[   50.193136] Key type cifs.idmap registered
[   51.225073] BUG: unable to handle kernel NULL pointer dereference at
0058
[   51.225196] IP: [] crypto_shash_setkey+0x1c/0xc0
[   51.225289] PGD 0
[   51.225322] Oops:  [#1] SMP
[   51.225350] Modules linked in: md4 hmac nls_utf8 cifs dns_resolver ctr ccm
cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative nfsd
auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc fuse lp arc4 rt61pci
rt2x00pci rt2x00mmio rt2x00lib eeprom_93cx6 mac80211 cfg80211 rfkill crc_itu_t
iTCO_wdt iTCO_vendor_support ppdev lpc_ich parport_pc mfd_core parport pcspkr
rng_core serio_raw evdev snd_intel8x0 snd_ac97_codec shpchp snd_pcm snd_timer
snd soundcore ac97_bus acpi_cpufreq processor ext4 crc16 mbcache jbd2 xts
gf128mul algif_skcipher af_alg dm_crypt dm_mod nouveau mxm_wmi ttm sd_mod
crc_t10dif sg crct10dif_generic sr_mod cdrom crct10dif_common ata_generic
ata_piix psmouse libata scsi_mod wmi floppy i915 i2c_algo_bit tg3 video ptp
drm_kms_helper pps_core libphy ehci_pci uhci_hcd
[   51.225998]  ehci_hcd button drm i2c_core thermal_sys usbcore usb_common
[   51.226053] CPU: 1 PID: 2639 Comm: mount.cifs Not tainted 3.16.0-6-amd64 #1
Debian 3.16.57-2
[   51.226106] Hardware name: Hewlett-Packard HP Compaq dc7100
CMT(PE224ET)/0968h, BIOS 786C1 v02.15 08/07/2008
[   51.226168] task: 88007a190cf0 ti: 88007b39c000 task.ti:
88007b39c000
[   51.226215] RIP: 0010:[]  []
crypto_shash_setkey+0x1c/0xc0
[   51.226274] RSP: 0018:88007b39fa68  EFLAGS: 00010292
[   51.226309] RAX: 88003697ee00 RBX: 0002 RCX:
88007ace4800
[   51.226354] RDX: 0010 RSI: 88003697ef18 RDI:

[   51.226400] RBP:  R08: 88007adfbf08 R09:

[   51.226445] R10: 756574735c53414e R11: 88007b5cf800 R12:
88003697ef18
[   51.226490] R13: 88007b39fb50 R14: 0010 R15:
88007b39fbd4
[   51.226536] FS:  7fbebabb8740() GS:88007f50()
knlGS:
[   51.226586] CS:  0010 DS:  ES:  CR0: 80050033
[   51.226624] CR2: 0058 CR3: 7ad2a000 CR4:
0770
[   51.226670] Stack:
[   51.226684]  88007b2150f0 0002 88007b39fb08
88007a0b1800
[   51.226738]  88007b39fb50 0002 88007b39fbd4
a083eaf3
[   51.226790]  88007b39fbe0 88007ace4800 0246

[   51.226842] Call Trace:
[   51.226874]  [] ? smb3_calc_signature+0x93/0x2b0 [cifs]
[   51.226927]  [] ? smb2_setup_request+0xb8/0x190 [cifs]
[   51.226980]  [] ? SendReceive2+0xd2/0x450 [cifs]
[   51.227029]  [] ? SMB2_ioctl+0x13f/0x320 [cifs]
[   51.227076]  [] ? 

Bug#625200: Add debconf warning stating that the package can prevent boot

[Chris Hofstaedtler]

Hi Laurent,

* Laurent Bigonville  [180811 14:52]:
> Version: 0.4.8+git0.761c66f-9

[..]

> It could be interesting to add a debconf warning stating that the
> package can prevent to boot if the package is installed and that the
> local disk is not blacklisted in the config.

Current versions blacklist at least these devices by default:

devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st|dcssblk)[0-9]"
devnode "^(td|hd|vd)[a-z]"
devnode "^cciss!c[0-9]d[0-9]*"

Plus a lot of storage device exports.

Maybe this is good enough now as a "standard local disk" shouldn't be
affected anymore? In a quick local test (with an sd* device node
though) boot kept working for me.
Are you still interested in the warning?

Cheers,
Chris

Bug#905911: Conky does not work because hwmon path is not persistent !

[Carmelo C]

Package: linux-image-4.9.0-7-amd64
Version: 4.9.110-3+deb9u1
Severity: normal


<< Dear Maintainer,

I installed from scratch firmware-9.4.0-amd64-netinst.iso

I installed conky to display the sensors in the desktop.

The modules that load on the desktop are:

coretemp (Temp)
it8772 (Temp, Fan)
nouveau (Temp, In)
dell_smm (Fan, Temp)

With the coretemp, it8772 modules I'm not having any problem, the problem
concerns the modules nouveau and dell_smm because they are loaded randomly
in the paths:

/sys/class/hwmon/hwmon4
/sys/class/hwmon/hwmon3

Given that on conky I use the following code:

nouveau: $ {offset 2} Temp1: $ {hwmon 4 temp 1} ° C $ {offset 10} Core GPU:
$ {hwmon 4 in 0} V dell_smm: $ {offset 2} Fan Processor: $ {hwmon 3 fan 1}
RPM $ {offset 10} Motherboard Fan: $ {hwmon 3 fan 2} RPM $ {offset 10}
Other: $ {hwmon 3 temp 2} ° C

I have to make debian load the modules in persistent paths, otherwise the
following errors are generated:

conky: desktop window (c3) is subwindow of root window (4dd)
conky: window type - override
conky: drawing to created window (0x321)
conky: drawing to double buffer
conky: can not open '/sys/class/hwmon/hwmon4/temp1_input': File or
directory does not exist please check your device or remove this from conky
conky: can not open '/sys/class/hwmon/hwmon4/in0_input': File or directory
does not exist please check your device or remove this from conky
conky: can not open '/sys/class/hwmon/hwmon3/fan1_input': File or directory
does not exist please check your device or remove this from conky
conky: can not open '/sys/class/hwmon/hwmon3/fan2_input': File or directory
does not exist please check your device or remove this from conky
conky: can not open '/sys/class/hwmon/hwmon3/temp2_input': File or
directory does not exist please check your device or remove this from conky
conky: forked to background, pid is 1007

>>

Bug#689605: multipath-tools: no default multipath.conf

[Chris Hofstaedtler]

Control: tags -1 + upstream
Control: retitle -1 multipath-tools: blacklist Xen devices by default

* Andreas Pflug  [180811 14:47]:
> Package: multipath-tools
> Version: 0.4.8+git0.761c66f-10
> Severity: normal
> 
> Since the multipath-tools package includes no standard multipath.conf, 
> multipathd will grab any new block device. This can lead to surprising and 
> hard debug effects.
> e.g. attaching a device in a XEN dom0 domain will render the device 
> inaccessible. This corrupts xen-utils-4.1 since xend will attach the boot 
> device locally for pygrub, but can't release it properly because multipathd 
> has it.
> 
> I suggest supplying at least a minimal multipath.conf that blacklists the 
> most dangerous devices by default.
> -- Package-specific info:
> Contents of /etc/multipath.conf:
> blacklist
> {
>   devnode "^xvd[0-9a-z]*"
> }

The built-in defaults in current versions appear to be:

blacklist {
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st|dcssblk)[0-9]"
devnode "^(td|hd|vd)[a-z]"
devnode "^cciss!c[0-9]d[0-9]*"
...
}

Note that this doesn't match xvd*, but is this still a thing with
current Xen versions, or has everything moved to vd* anyway?

Chris

Bug#905910: libssh has dropped libssh_threads library

[Laurent Bigonville]

Source: remmina
Version: 1.2.31.2+dfsg-1
Severity: serious
Tags: patch

Hi,

libssh 0.8.0 has dropped the libssh_thread library and the only function
exported by it has been merged in the main library

Applying the attached patch should fix the build

Kind 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.18.0-rc4-amd64 (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)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
diff -Nru remmina-1.2.31.2+dfsg/debian/control 
remmina-1.2.31.2+dfsg/debian/control
--- remmina-1.2.31.2+dfsg/debian/control2018-07-29 14:54:23.0 
+0200
+++ remmina-1.2.31.2+dfsg/debian/control2018-08-11 16:03:14.0 
+0200
@@ -20,7 +20,7 @@
  libsoup2.4-dev,
  libspice-client-gtk-3.0-dev,
  libspice-protocol-dev,
- libssh-dev (>= 0.8.0~20170825.94fa1e38),
+ libssh-dev (>= 0.8.0),
  libtelepathy-glib-dev,
  libvncserver-dev,
  libvte-2.91-dev,
diff -Nru remmina-1.2.31.2+dfsg/debian/patches/0002-remove-libssh_threads.patch 
remmina-1.2.31.2+dfsg/debian/patches/0002-remove-libssh_threads.patch
--- remmina-1.2.31.2+dfsg/debian/patches/0002-remove-libssh_threads.patch   
1970-01-01 01:00:00.0 +0100
+++ remmina-1.2.31.2+dfsg/debian/patches/0002-remove-libssh_threads.patch   
2018-08-11 16:03:14.0 +0200
@@ -0,0 +1,14 @@
+--- a/cmake/FindLIBSSH.cmake
 b/cmake/FindLIBSSH.cmake
+@@ -42,11 +42,6 @@ find_library(LIBSSH_LIBRARY
+   PATHS ${PC_LIBSSH_PKGCONF_LIBRARY_DIRS}
+ )
+ 
+-find_library(LIBSSH_THREADS_LIBRARY
+-  NAMES ssh_threads
+-  PATHS ${PC_LIBSSH_LIBDIR} ${PC_LIBSSH_LIBRARY_DIRS}
+-)
+-
+ include(FindPackageHandleStandardArgs)
+ 
+ find_package_handle_standard_args(LIBSSH DEFAULT_MSG LIBSSH_LIBRARY 
LIBSSH_INCLUDE_DIR)
diff -Nru remmina-1.2.31.2+dfsg/debian/patches/series 
remmina-1.2.31.2+dfsg/debian/patches/series
--- remmina-1.2.31.2+dfsg/debian/patches/series 2018-08-01 22:20:23.0 
+0200
+++ remmina-1.2.31.2+dfsg/debian/patches/series 2018-08-11 16:03:14.0 
+0200
@@ -1 +1,2 @@
 0001-Fix_warnings_on_manpages.patch
+0002-remove-libssh_threads.patch

Bug#900573: qreator: won't start complaining no module named Image

[Philipp Matthias Hahn]

Package: qreator
Version: 16.06.1-3
Followup-For: Bug #900573

Dear Maintainer,

Quoting :
> PIL used to provide a PIL.pth file which allowed you to `import Image`
> but this is deprecated. Use `from PIL import Image` now, or install
> this compatibility package to temporarily get the old behavior back. 

sed -i -e '/^import Image/s/^/from PIL /' /usr/bin/qreator

that "fixes" it for me, but now I get:

> Traceback (most recent call last):
>   File "/usr/bin/qreator", line 46, in 
> qreator.main()
>   File "/usr/share/qreator/qreator/__init__.py", line 73, in main
> window = QreatorWindow.QreatorWindow()
>   File "/usr/share/qreator/qreator_lib/Window.py", line 48, in __new__
> new_object.finish_initializing(builder)
>   File "/usr/share/qreator/qreator/QreatorWindow.py", line 79, in 
> finish_initializing
> self.init_qr_types()
>   File "/usr/share/qreator/qreator/QreatorWindow.py", line 135, in 
> init_qr_types
> self.qr_types = [d(self.update_qr_code) for d in QRCodeType.dataformats]
>   File "/usr/share/qreator/qreator/qrcodes/QRCodeType.py", line 71, in 
> __init__
> self.create_widget()  # pylint: disable=E1101
>   File "/usr/share/qreator/qreator/qrcodes/QRCodeLocation.py", line 29, in 
> create_widget
> self.widget = QRCodeLocationGtk(self.qr_code_update_func)
>   File "/usr/share/qreator/qreator/qrcodes/QRCodeLocationGtk.py", line 50, in 
> __init__
> latitude, longitude = get_current_location()
>   File "/usr/share/qreator/qreator/qrcodes/QRCodeLocationGtk.py", line 93, in 
> get_current_location
> 'qreator', Geoclue.AccuracyLevel.EXACT)
> GLib.Error: g-dbus-error-quark: 
> GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'qreator' disallowed, no 
> agent for UID 1000 (9)

but that's a different bug...
-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages qreator depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.28.0-2
ii  geoclue-2.0  2.4.10-1
ii  gir1.2-champlain-0.120.12.16-2
ii  gir1.2-clutter-1.0   1.26.2+dfsg-4
ii  gir1.2-gdkpixbuf-2.0 2.36.12-1
ii  gir1.2-geoclue-2.0   2.4.10-1
ii  gir1.2-glib-2.0  1.56.1-1
ii  gir1.2-gtk-3.0   3.22.30-2
ii  gir1.2-gtkchamplain-0.12 0.12.16-2
ii  gir1.2-gtkclutter-1.01.8.4-3
ii  gir1.2-nm-1.01.12.2-2
ii  python   2.7.15-3
ii  python-cairo 1.16.2-1+b1
ii  python-dbus  1.2.8-2+b1
ii  python-gi3.28.2-1+b1
ii  python-gi-cairo  3.28.2-1+b1
ii  python-pil   5.2.0-2
ii  python-qrencode  1.2-4+b1
ii  python-requests  2.18.4-2
ii  python-vobject   0.9.5-2
ii  python-xdg   0.25-4

qreator recommends no packages.

qreator suggests no packages.

-- no debconf information

Bug#904286: f2fs-tools: Please package f2fs-tools v1.11.0

[Theodore Y. Ts'o]

On Sun, Jul 22, 2018 at 01:49:17PM -0400, Theodore Y. Ts'o wrote:
> 
> Please consider packaginging f2fs-tools 1.11.0 from upstream.  This
> release includes:
> 
>   - add sg_write_buffer for UFS firmware update in Android
>   - wanted_sector_size to specify sector size explicity
>   - support fsverity feature bit
>   - support lost+found feature
>   - some critical bug fixes

Hi Vincent,

Do you think you will have time to update f2fs-tools to 1.11?  If not,
would you be OK if I were to submit an NMU to update f2fs-tools?

Many thanks!!

- Ted

Bug#905769: node-toidentifier: Unnecessary $(DEB_BUILD_PROFILES) check?

[Chris Lamb]

Bastian,

> It is a feature that dpkg-buildpackage -P nocheck does not set
> DEB_BUILD_OPTIONS.
> 
> My solution above is policy compliant and allow to test nocheck with
> dpkg-buildpackage

Then the lintian check and/or description is buggy and/or misleading.

Regards,

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

Bug#905885: diffoscope: skipping tests on ci.debian.net is perhaps wrong?

[Stuart Prescott]

> Braindumping here whilst I have a second...
> 
> > diffoscope recommends apktool but apktool is not currently in buster.
> 
>  ^^
> 
> Ah, this was the bit I was missing in my head. ie. not a Build-Depends :)

both, actually. diffoscope FTBFS in buster because:

Build-Depends: apktool , …

(which is an RC bug waiting to be filed)

*also* diffoscope recommends apktool but tests on ci.d.n do not fail (but 
should, I think)

> > Perhaps @tool_required could be extended with an "all tools required"
> > mode such that no tests are skipped or missing tools are a test failure
> > (or error). An environment variable would work for setting that mode
> > and that mode used at package build time and in autopkgtest.
> 
> Out of curiousity, is there an environment variable that ci.debian.net
> reliably exports?

You'd set that environment variable in d/rules and d/tests/* (and so could 
other distros who want to test that packages are working)

> (One difficulty with "just" extending @tool_required is that sometimes
> we really do want to skip the tests as they require a newer/older
> version of a particular tool in order that we can correctly match up
> the output.)

If the newer/older version doesn't work, surely the test should fail?

cheers
Stuart

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

Bug#905769: node-toidentifier: Unnecessary $(DEB_BUILD_PROFILES) check?

[roucaries bastien]

On Thu, Aug 9, 2018 at 11:36 AM Chris Lamb  wrote:
>
> Source: node-toidentifier
> Version: 1.0.0-1
> Severity: wishlist
> X-Debbugs-CC: Bastien Roucaris ,
> ftpmas...@debian.org
>
> Hi,
>
> I just ACCEPTed node-toidentifier from NEW but was wondering if:
>
>ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS) $(DEB_BUILD_PROFILES)))
>
> .. should really be checking (only) DEB_BUILD_OPTIONS?

It is a feature that dpkg-buildpackage -P nocheck does not set
DEB_BUILD_OPTIONS.

My solution above is policy compliant and allow to test nocheck with
dpkg-buildpackage

Bastien

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

Bug#905909: README.md: Formatting and publication to www.debian.org

[Osamu Aoki]

Package: src:debian-policy
Version: 4.2.0.1
Severity: normal
Tags: patch

README.md of debian-policy at salsa doesn't show indexed list as
expected.

Also, it doesn't provide information on how it get published to
www.debiasn.org site to track down issues.

This github style MD s a bit tricky but my commit
  baea79f ("Format ...", 2018-08-11)
at
  https://salsa.debian.org/osamu/policy
should fix issues in "Making a release".

Now number goes 7 8 9 10 11 instead of 7 1 2 3.

See the bottm of these web pages.
  https://salsa.debian.org/dbnpolicy/policy
  https://salsa.debian.org/osamu/policy

Please merge my changes after squishing history :-)

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

Kernel: Linux 4.17.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:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#905885: diffoscope: skipping tests on ci.debian.net is perhaps wrong?

[Chris Lamb]

Hi Stuart,

> > Ah, this was the bit I was missing in my head. ie. not a Build-Depends :)
> 
> both, actually. diffoscope FTBFS in buster 
[..]

I'll leave these to Mattia has he has been playing about in this area
recently.

> You'd set that environment variable in d/rules and d/tests/* (and so could 
> other distros who want to test that packages are working)

Sure of course one would take this approach, but just out of curiousity
whether there is a 100% reliable one set by ci.debian.net?

> > (One difficulty with "just" extending @tool_required is that sometimes
> > we really do want to skip the tests as they require a newer/older
> > version of a particular tool in order that we can correctly match up
> > the output.)
> 
> If the newer/older version doesn't work, surely the test should fail?

work != differ. If it *fails*, sure (and we handle/fix those), but
ironically don't guarantee that the output of diffoscope will be reproducible
across (invented example here) ImageMagick 5.1 and 5.2.


Regards,

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

Bug#905339: Some open operations are DENIED by AppArmor

[Haruki TSURUMOTO]

Hi,

On 2018年08月04日 11:06, intrigeri wrote:

Control: tag -1 + moreinfo

Hi,

Haruki TSURUMOTO:


I had enabled AppArmor on my debian stretch machine.
I found some libvirt's open operations are DENIED by apparmor.

Indeed, the AppArmor policy for libvirt has been improved a lot since
Stretch, where it's far from being perfect.


Would you apply this patch for stretch?

(I'm not the libvirt maintainer but I work on AppArmor in Debian.)

I would happily work on backports for Stretch of fixes to user-visible
issues in the AppArmor policy. I probably won't have time to work on
fixes to issues that have no perceivable user impact apart of noise in
the logs. Could you please extract from your proposed patch the subset
that fits into the first category?

Cheers,


I am searching there are something user inconveniences.
libvirt collects host's resource for unknown reason.
IMO,  I think something user inconveniences is there.

Anyway, DENIED log was noisy for me.

Bug#905874: libreoffice: No input of accented characters through dead-key composition

[Rene Engelhard]

retitle 905874: libreoffice: No input of accented characters through dead-key 
composition in gen and kde4 plugins
thanks

On Sat, Aug 11, 2018 at 01:22:51PM +0200, Rene Engelhard wrote:
> On Fri, Aug 10, 2018 at 10:18:30PM -0400, Mario L. Epp wrote:
> > On researching the issue prior to making this report, I found this issue
> > reported on the DocumentFoundation Bugzilla as "Bug 112770" at
> > . But I am not
> > shure how to implement the solution from 6.0.0 to 5.2.7.2 for KDE5 on 
> > Debian 9.
> 
> Maybe install the 6.1.0 backport from stretch-backports? That one also
> has a KDE5 integration other than that KDE4 thingy "working" with KDE5.
> 
> This will never be fixed in stable properly (until buster releases of
> course with above new KDE5 integration)

I missed to mention that I repeatedly asked whether there were any
important fixes for KDE4 which should be backported to 5.2.7 as for
stretch; no reply, and at some point in time it was too late.

OK, this time according  to the upstream bug this also affects "gen",
but most people will use gtk3/gtk2 or kde(4)...

Regards,
 
Rene

Bug#905908: libGL.so.1: cannot open shared object file: No such file or directory when updating to 4.4.1~rc2-3

[Kyle Robbertze]

Package: octave
Version: 4.4.1~rc2-3
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

When updating octave to 4.4.1~rc2-3, I received the following error:

Setting up octave (4.4.1~rc2-3) ...
/usr/bin/octave-cli: error while loading shared libraries: libGL.so.1: cannot 
open shared object file: No such file or directory
dpkg: error processing package octave (--configure):
 installed octave package post-installation script subprocess returned error 
exit status 127

It appears to be missing a dependency on a package that provides libGL.

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

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

Versions of packages octave depends on:
ii  libamd21:5.3.0+dfsg-1
ii  libarpack2 3.6.2-1
ii  libasound2 1.1.6-1
ii  libblas3 [libblas.so.3]3.8.0-1+b1
ii  libbz2-1.0 1.0.6-8.1
ii  libc6  2.27-5
ii  libcamd2   1:5.3.0+dfsg-1
ii  libccolamd21:5.3.0+dfsg-1
ii  libcholmod31:5.3.0+dfsg-1
ii  libcolamd2 1:5.3.0+dfsg-1
ii  libcxsparse3   1:5.3.0+dfsg-1
ii  libfftw3-double3   3.3.8-1
ii  libfftw3-single3   3.3.8-1
ii  libfltk-gl1.3  1.3.4-7
ii  libfltk1.3 1.3.4-7
ii  libfreetype6   2.8.1-2
ii  libgcc11:8.2.0-3
ii  libgl1 1.0.0+git20180308-4
ii  libglpk40  4.65-2
ii  libglu1-mesa [libglu1] 9.0.0-2.1
ii  libgomp1   8.2.0-3
ii  libklu11:5.3.0+dfsg-1
ii  liblapack3 [liblapack.so.3]3.8.0-1+b1
ii  liboctave5 4.4.1~rc2-3
ii  libopenblas-base [liblapack.so.3]  0.3.2+ds-1
ii  libportaudio2  19.6.0-1
ii  libqhull7  2015.2-4
ii  libqrupdate1   1.1.2-2+b2
ii  libqscintilla2-qt5-13  2.10.4+dfsg-1+b1
ii  libqt5core5a   5.11.1+dfsg-6
ii  libqt5gui5 5.11.1+dfsg-6
ii  libqt5help55.11.1-5
ii  libqt5network5 5.11.1+dfsg-6
ii  libqt5opengl5  5.11.1+dfsg-6
ii  libqt5printsupport55.11.1+dfsg-6
ii  libqt5sql5 5.11.1+dfsg-6
ii  libqt5widgets5 5.11.1+dfsg-6
ii  libsndfile11.0.28-4
ii  libstdc++6 8.2.0-3
ii  libsuitesparseconfig5  1:5.3.0+dfsg-1
ii  libumfpack51:5.3.0+dfsg-1
ii  libx11-6   2:1.6.5-1
ii  octave-common  4.4.1~rc2-3
ii  texinfo6.5.0.dfsg.1-4
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages octave recommends:
ii  default-jre-headless  2:1.10-68
ii  epstool   3.08+repack-7
ii  gnuplot-qt [gnuplot-nox]  5.2.2+dfsg1-2
ii  libopenblas-base  0.3.2+ds-1
ii  octave-doc4.4.1~rc2-3
ii  pstoedit  3.73-1+b1

Versions of packages octave suggests:
pn  liboctave-dev  

-- no debconf information

Bug#904652: pulseaudio: looses device and replace it with dummy package so no sound possible

[Meinolf Gödde]

The problem is back again. So i hope it helps.

Am 10.08.2018 22:25 schrieb Felipe Sateler:

(Please keep the bug in CC)
On Fri, Aug 10, 2018 at 4:06 PM Meinolf Gödde  
wrote:



Hi,

Here is the output.

Hope you can find a hint.

Greetings



Unfortunately it is not useful unless it is a log of the problem 
occurring.


Saludos




Meinolf

Am 07.08.2018 17:39 schrieb Felipe Sateler:
> On Sat, Jul 28, 2018 at 8:24 AM Charlemagne Lasse <
> charlemagnela...@gmail.com> wrote:
>
>> found 904652 11.1-5
>> thanks
>>
>> > i didn't do anything.
>> > Upgrading the system like always.
>> > Suddenly there was no sound available.
>>
>> Change /etc/pulse/default.pa to automatically load module-alsa-sink on
>> boot (module-udev-detect is broken and will not load the alsa-sink
>> anymore)
>>
>> This is also a problem in buster (which is still using 11.1-5)
>>
>
> Seems like pulseaudio is not starting. Please attach the output of
> `pulseaudio - --daemonize=no`, without applying your workaround.

Bug#903343: voikko-fi: diff for NMU version 2.2-1.1

[Adrian Bunk]

Control: tags 903343 + patch
Control: tags 903343 + pending

Dear maintainer,

I've prepared an NMU for voikko-fi (versioned as 2.2-1.1) and uploaded 
it to DELAYED/15. Please feel free to tell me if I should cancel it.

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

diff -Nru voikko-fi-2.2/debian/changelog voikko-fi-2.2/debian/changelog
--- voikko-fi-2.2/debian/changelog	2017-09-08 16:05:40.0 +0300
+++ voikko-fi-2.2/debian/changelog	2018-08-11 16:41:17.0 +0300
@@ -1,3 +1,10 @@
+voikko-fi (2.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Adjust debian/docs to what is shipped upstream. (Closes: #903343)
+
+ -- Adrian Bunk   Sat, 11 Aug 2018 16:41:17 +0300
+
 voikko-fi (2.2-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru voikko-fi-2.2/debian/docs voikko-fi-2.2/debian/docs
--- voikko-fi-2.2/debian/docs	2017-09-08 16:05:40.0 +0300
+++ voikko-fi-2.2/debian/docs	2018-08-11 16:41:13.0 +0300
@@ -1,2 +1 @@
-README
-README.fi
+README.md

Bug#897732: patches

[Vasudev Kamath]

Vasudev Kamath  writes:

> Hi Adrian,
>
> Adrian Bunk  writes:
>>
>> Hi Vasudev,
>>
>> are there any remaining problems with
>>   https://salsa.debian.org/debian/ctpp2/merge_requests/1
>> ?
>
> I've merged the changes. I had requested changes from Kunal but I did
> not get notification or got and it got filtered hence failed to notice.
>
>>
>> If there are any issues left that cannot be resolved quickly,
>> for a temporary fix I could do an NMU.
>
> No need for NMU but can you or Jonas upload package?. I use dgit
> push-source --gbp but getting some error on my side. Which I'm not sure
> if its only my case or every one else gets it. 

Uploaded manually and sorry last time missed to Cc the bug.

Cheers,
Vasudev

Bug#903338: opencryptoki: diff for NMU version 3.8.1+dfsg-3.1

[Adrian Bunk]

Control: tags 903338 + pending

Dear maintainer,

I've prepared an NMU for opencryptoki (versioned as 3.8.1+dfsg-3.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

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

diff -Nru opencryptoki-3.8.1+dfsg/debian/changelog opencryptoki-3.8.1+dfsg/debian/changelog
--- opencryptoki-3.8.1+dfsg/debian/changelog	2017-11-09 13:52:15.0 +0200
+++ opencryptoki-3.8.1+dfsg/debian/changelog	2018-08-11 16:27:36.0 +0300
@@ -1,3 +1,11 @@
+opencryptoki (3.8.1+dfsg-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Adjust debian/opencryptoki.docs for upstream changes.
+(Closes: #903338)
+
+ -- Adrian Bunk   Sat, 11 Aug 2018 16:27:36 +0300
+
 opencryptoki (3.8.1+dfsg-3) unstable; urgency=emergency
 
   * Remove wrong tmpfiles.conf file present in systemd path. Closes: #881222
diff -Nru opencryptoki-3.8.1+dfsg/debian/opencryptoki.docs opencryptoki-3.8.1+dfsg/debian/opencryptoki.docs
--- opencryptoki-3.8.1+dfsg/debian/opencryptoki.docs	2016-08-16 11:52:18.0 +0300
+++ opencryptoki-3.8.1+dfsg/debian/opencryptoki.docs	2018-08-11 16:27:30.0 +0300
@@ -1,4 +1,3 @@
 AUTHORS
 FAQ
-README
-TODO
+README.md