Bug#903016: python3-libvirt: import fails with current python interpreter in sid

2018-07-04 Thread Manuel Traut
Package: python3-libvirt
Version: 4.0.0-1+b1
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

the package is broken on sid:

The following packages were automatically installed and are no longer required:
  iputils-arping liblogging-stdlog0 libnginx-mod-http-auth-pam 
libnginx-mod-http-dav-ext libnginx-mod-http-echo libngin
  libnginx-mod-http-xslt-filter libnginx-mod-mail libnginx-mod-stream 
libplacebo4 libwireshark10 libwiretap7 libwscodec
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
  medcon xmedcon
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up python3-libvirt (4.0.0-1+b1) ...
  File "/usr/lib/python3/dist-packages/libvirtaio.py", line 49
from asyncio import async as ensure_future
^
SyntaxError: invalid syntax

dpkg: error processing package python3-libvirt (--configure):
 installed python3-libvirt package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 python3-libvirt
E: Sub-process /usr/bin/dpkg returned an error code (1)

The problem is fixed upstream with this commit:

https://github.com/libvirt/libvirt-python/commit/e27528204c887b4099b892a0237766f187959737#diff-cd56dd4108fa77f26cb6c1e6358beba1



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

Kernel: Linux 4.16.0-2-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

Versions of packages python3-libvirt depends on:
ii  libc6 2.27-3
ii  libvirt0  4.3.0-1
ii  python3   3.6.6-1

Versions of packages python3-libvirt recommends:
ii  libvirt-daemon  4.3.0-1

python3-libvirt suggests no packages.

-- debconf-show failed
>From e27528204c887b4099b892a0237766f187959737 Mon Sep 17 00:00:00 2001
From: Cole Robinson 
Date: Mon, 25 Jun 2018 14:14:57 -0400
Subject: [PATCH 1/2] libvirtaio: Fix compat with python 3.7

In python 3.7, async is now a keyword, so this throws a syntax error:

  File "/usr/lib64/python3.7/site-packages/libvirtaio.py", line 49
from asyncio import async as ensure_future
^
  SyntaxError: invalid syntax

Switch to getattr trickery to accomplish the same goal

Reviewed-by: Pavel Hrdina 
Reviewed-by: Andrea Bolognani 
Signed-off-by: Cole Robinson 
---
 libvirtaio.py | 11 +++
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/libvirtaio.py b/libvirtaio.py
index 1c432dd..328e6f2 100644
--- a/libvirtaio.py
+++ b/libvirtaio.py
@@ -43,10 +43,13 @@ import warnings
 
 import libvirt
 
-try:
-from asyncio import ensure_future
-except ImportError:
-from asyncio import async as ensure_future
+# Python < 3.4.4 doesn't have 'ensure_future', so we have to fall
+# back to 'async'; however, since 'async' is a reserved keyword
+# in Python >= 3.7, we can't perform a straightforward import and
+# we have to resort to getattr() instead
+ensure_future = getattr(asyncio, "ensure_future", None)
+if not ensure_future:
+ensure_future = getattr(asyncio, "async")
 
 
 class Callback(object):
-- 
2.18.0



Bug#903005: stretch-pu: package clamav/0.100.0+dfsg-0+deb9u1

2018-07-04 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Wed, 2018-07-04 at 23:53 +0200, Sebastian Andrzej Siewior wrote:
> 0.100.0 clamav version had a few config options removed. This is
> covered
> by postinst as long as the config is handled by debconf. If the user
> makes changes manually then ucf ask the user to resolve it and if
> nothing happens
> (during unattended-upgrades) then the old options remain set and
> clamav
> refuses to start.
> This was reported during the deb8 point upgrade. To avoid this during
> the upcomming deb9 upgrade I hereby propose a patch to simply declare
> the removed options as "deprecated" which results in a warning like
> > 

Please go ahead.

Regards,

Adam



Bug#903015: stretch-pu: package gridengine/8.1.9+dfsg-4 - complete diff

2018-07-04 Thread Afif Elghraoui
Here is the complete diff for the proposed upload, including the changelog:

--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+gridengine (8.1.9+dfsg-4+deb9u1) stretch-proposed-updates; urgency=medium
+
+  * gridengine-qmon:
+  - Use correct paths to qmon pixmaps (Closes: #892296)
+
+ -- Afif Elghraoui   Thu, 05 Jul 2018 00:38:58 -0400
+
 gridengine (8.1.9+dfsg-4) unstable; urgency=low

   * Patch upstream source to declare prerequisites for pdc (Closes:
#846770)
diff --git a/debian/gridengine-qmon.install b/debian/gridengine-qmon.install
index 99b6cf17d..59ddc17f0 100644
--- a/debian/gridengine-qmon.install
+++ b/debian/gridengine-qmon.install
@@ -1,2 +1,2 @@
 debian/tmp/usr/bin/*/qmon  usr/lib/gridengine
-debian/tmp/usr/qmon/PIXMAPS/*  usr/share/gridengine/pixmaps
+debian/tmp/usr/qmon/PIXMAPSusr/share/gridengine/qmon/
diff --git a/debian/gridengine-qmon.links b/debian/gridengine-qmon.links
index cefcd72ed..ecaf1fda2 100644
--- a/debian/gridengine-qmon.links
+++ b/debian/gridengine-qmon.links
@@ -1 +1,2 @@
 usr/share/gridengine/gridengine-wrapper usr/bin/qmon
+usr/share/gridengine/qmon/PIXMAPS  var/lib/gridengine/qmon/PIXMAPS

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name



Bug#903015: stretch-pu: package gridengine/8.1.9+dfsg-4

2018-07-04 Thread Afif Elghraoui
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

A user requested that the bug #892296 be fixed in Stable [1].
The necessary patch to fix this is at the end of this message.

Thanks and regards
Afif

1. https://lists.debian.org/debian-hpc/2018/06/msg00021.html

>From c416d2f88fa6ee1518d95e37a65856c571994bc0 Mon Sep 17 00:00:00 2001
From: Afif Elghraoui 
Date: Sun, 11 Mar 2018 17:07:27 -0400
Subject: [PATCH] Use correct paths to qmon pixmaps

Closes: #892296
---
 debian/gridengine-qmon.install | 2 +-
 debian/gridengine-qmon.links   | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/debian/gridengine-qmon.install b/debian/gridengine-qmon.install
index 99b6cf17d..59ddc17f0 100644
--- a/debian/gridengine-qmon.install
+++ b/debian/gridengine-qmon.install
@@ -1,2 +1,2 @@
 debian/tmp/usr/bin/*/qmon  usr/lib/gridengine
-debian/tmp/usr/qmon/PIXMAPS/*  usr/share/gridengine/pixmaps
+debian/tmp/usr/qmon/PIXMAPSusr/share/gridengine/qmon/
diff --git a/debian/gridengine-qmon.links b/debian/gridengine-qmon.links
index cefcd72ed..ecaf1fda2 100644
--- a/debian/gridengine-qmon.links
+++ b/debian/gridengine-qmon.links
@@ -1 +1,2 @@
 usr/share/gridengine/gridengine-wrapper usr/bin/qmon
+usr/share/gridengine/qmon/PIXMAPS  var/lib/gridengine/qmon/PIXMAPS
-- 
2.18.0



Bug#860153: libgoffice-0.10-dev: Could you expose goffice within glade

2018-07-04 Thread Dmitry Smirnov
On Wednesday, 12 April 2017 6:44:11 PM AEST pi...@synchrotron-soleil.fr 
wrote:
> In order to use the goffice widgets, it would be nice make them available
> within glade.

How can this be done? Is this a wish for upstream?

-- 
Regards,
 Dmitry Smirnov.


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


Bug#539621: the bug still exists

2018-07-04 Thread Vincent Lefevre
Control: tags -1 - fixed-upstream
Control: forwarded -1 https://bugs.gnucash.org/show_bug.cgi?id=370331

The upstream bug has moved to a new BTS.

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



Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

2018-07-04 Thread Helmut Grohne
Control: tags -1 - moreinfo

On Wed, Jul 04, 2018 at 10:37:32PM +0200, Michael Biebl wrote:
> sound like an sbuild bug. Using pbuilder I have no problems building the
> gnupg2 package.

I kinda agree with you here. I actually ran into this bug a while
earlier:

Unlike systemd-sysv, systemd-shim isn't Multi-Arch: foreign. So
installing a foreign libpam-systemd (as some cross builds do) did run
into the very same issue for a while already: It tried installing
systemd-shim and gave up even though just picking systemd-sysv would
have worked.

Actually, sbuild defers to apt here, so it would be an apt bug, no?

> Can you please reassign this bug report to the appropriate package?

I thus filed this bug with apt as #883555. The irc discussion on the
matter was unfortunately not reflected on the bug, but essentially deity
ruled that solving each and every situation was infeasible and that
packages must coordinate better to resolve such issues.

In the case of #883555 that meant that both alternatives should share
the same Multi-Arch value.

So even though this issue can be considered and apt bug, it'll be
wontfix there and you'll have to fix it in systemd anyway. I'm Ccing
deity here to have them speak up in case they disagree with that
analysis.

On irc you proposed two solutions:
 * dropping the -shim alternative
 * adding the inverse version restriction of the breaks to the -shim
   alternative

As far as I understand, either solution would solve this bug.

Helmut



Bug#903014: RFS: fcitx-rime/0.3.2-3 [RC]

2018-07-04 Thread Boyuan Yang
Package: sponsorship-requests
Severity: important
X-Debbugs-CC: a...@debian.org sunwea...@debian.org
debian-input-met...@lists.debian.org s...@debian.org culu@gmail.com

Dear Mike, debian-input-method members and mentors,

As part of bug fixes and package rebuild in Debian Input Method Team, I
prepared a team upload for package "fcitx-rime" and I'm currently looking for a
sponsor for this package.

Besides, I am looking for a DD to help to grant me write permission to
fcitx-rime's
git repository on Salsa (https://salsa.debian.org/debian/fcitx-rime)
so that I could
push my work onto the repository. A temporary git repo has been set up on Salsa
already (https://salsa.debian.org/hosiet-guest/fcitx-rime).

Levels of rebuild (and bugfix):

Level 1:
  * libmarisa0 (done), libopencc2 (done)

Level 2:
  * libbkc2 (done), libkkc-data (done), librime1 (done)

Level 3:
  * brise (done), fcitx (done)

Level 4:
  * fcitx-qt5 (done), goldendict

Level 4:
  * fcitx-rime, fcitx-kkc, ibus-kkc, ibus-rime , ibus-libzhuyin
   ^ we are here

 * Package name: fcitx-rime
   Version : 0.3.2-3
   Upstream Author : Weng Xuetian 
 * URL : https://gitlab.com/fcitx/fcitx-rime
 * License : GPL-2+
   Section : utils

  It builds those binary packages:

fcitx-rime - Fcitx wrapper for RIME engine

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

  https://mentors.debian.net/package/fcitx-rime

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

dget -x 
https://mentors.debian.net/debian/pool/main/f/fcitx-rime/fcitx-rime_0.3.2-3.dsc


  Git packaging repository (proposed, not exist yet):

https://salsa.debian.org/debian/fcitx-rime


  Git packaging repository (temporary, contains my work):

https://salsa.debian.org/hosiet-guest/fcitx-rime


  Changes since the last upload:

 fcitx-rime (0.3.2-3) unstable; urgency=medium
 .
   * Team upload.
   * Rebuild against librime 1.3.1.
   * Apply "wrap-and-sort -abst".
   * debian/patches:
 + Backport all upstream commits till 2018-05-31.
   * debian/control:
 + Update maintainer field and use debian-input-method mailing list.
   Closes: #899504.
 + Bump Standards-Version to 4.1.5 (no changes needed).
 + Update YunQiang Su's email address and use the @debian.org one.
 + Update homepage field to use the corresponding GitLab project.
 + Add new build-dependency qtbase5-dev.
   * debian/rules:
 + Enable full hardening.
 + Use "dh_missing --fail-missing".

--
Regards,
Boyuan Yang



Bug#903013: libmp3-tag-perl: diff for NMU version 1.14-1

2018-07-04 Thread Jason Lewis
Package: libmp3-tag-perl
Version: 1.13-1.1
Severity: normal
Tags: patch  pending


Dear maintainer,

I've prepared an NMU for libmp3-tag-perl (versioned as 1.14-1)
Regards.


diff -Nru libmp3-tag-perl-1.13/Changes libmp3-tag-perl-1.14/Changes
--- libmp3-tag-perl-1.13/Changes	2010-07-13 13:37:26.0 +1000
+++ libmp3-tag-perl-1.14/Changes	2016-09-17 16:50:09.0 +1000
@@ -1,3 +1,27 @@
+Release Name: 1.14
+
+
+Tag.pm: Quiet warnings from 5.22.
+	Start implementing handlers: instead of FRAM(langs)[opts], one can use, e.g., func_name(ID3v1,Cue)[arg1][arg2]
+		   # ID3v2::_frame_select_by_descr is missing //s
+	New configuration variable ampersand_joiner (default '; ').
+	New method _auto_field_from() (abstracted from _auto_field()).
+	Change logic of calling ->can() in _auto_field_from().
+	_parse_rex_microinterpolate() would not update $ecount on seeing %%.
+	When parsing with %=c etc: with %==c the match fails if there is no comment.
+		(Checked the same way as for %{c:}.)
+	Support some of %-escapes not being matched (e.g, due to alternatives in a REx).
+		(0-length matches were ignored anyway [when join()ing].)
+	parse_rex(), parse_rex_match() may return an extra result (if %{handler}s are present).
+	Recognize ID3v2 frame names as [A-Z]{3}[A-Z\d] (was \w{4}).
+		(Detection frame/vs/handler happens via PACKAGES; so if lang codes inf/cue appear, we may be in trouble.)
+	Use the same code in parse(_rex)?_prepare.  (Now parse() allows the same %-constructs as parse_rex().)
+ID3v2.pm:
+	New method have_one_of_frames().
+	New methods *_have() (for simplest fields: title, comment, track, artist, album, genre, year).
+ImageExifTool.pm:
+	Comprehensive docs.
+
 Release Name: 1.13
 
 
diff -Nru libmp3-tag-perl-1.13/debian/changelog libmp3-tag-perl-1.14/debian/changelog
--- libmp3-tag-perl-1.13/debian/changelog	2017-07-13 05:25:22.0 +1000
+++ libmp3-tag-perl-1.14/debian/changelog	2018-07-02 16:57:02.0 +1000
@@ -1,3 +1,9 @@
+libmp3-tag-perl (1.14-1) UNRELEASED; urgency=medium
+
+  * New upstream release
+
+ -- jason   Mon, 02 Jul 2018 16:57:02 +1000
+
 libmp3-tag-perl (1.13-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libmp3-tag-perl-1.13/debian/patches/01_spelling.patch libmp3-tag-perl-1.14/debian/patches/01_spelling.patch
--- libmp3-tag-perl-1.13/debian/patches/01_spelling.patch	2012-02-05 17:46:29.0 +1100
+++ libmp3-tag-perl-1.14/debian/patches/01_spelling.patch	2018-07-02 16:57:02.0 +1000
@@ -2,11 +2,11 @@
 Author: Ian Beckwith 
 Last-Update: 2012-020-5
 
-Index: restore/lib/MP3/Tag.pm
+Index: libmp3-tag-perl-1.14/lib/MP3/Tag.pm
 ===
 restore.orig/lib/MP3/Tag.pm	2012-02-05 03:08:33.0 +
-+++ restore/lib/MP3/Tag.pm	2012-02-05 03:09:24.0 +
-@@ -523,7 +523,7 @@
+--- libmp3-tag-perl-1.14.orig/lib/MP3/Tag.pm
 libmp3-tag-perl-1.14/lib/MP3/Tag.pm
+@@ -527,7 +527,7 @@ Returns the second part of track number
  =item track0()
  
  Same as track1(), but pads with leading 0s to width of track2(); takes an
@@ -15,7 +15,7 @@
  
  =item disk1(), disk2()
  
-@@ -1784,7 +1784,7 @@
+@@ -1814,7 +1814,7 @@ frames).
  Strings C and C are replaced by "pure track number" and
  "max track number" (this allows for both formats C and C of "track",
  the latter meaning track N1 of N2); use C to pad C with leading 0
@@ -24,7 +24,7 @@
  but with disk (media) number instead of track number; use C to encode
  C as a letter (see L). 
  
-@@ -3337,7 +3337,7 @@
+@@ -3473,7 +3473,7 @@ method.
  
  The customization modules have an opportunity to change global
  configuration variables on load.  To allow more flexibility, they may
diff -Nru libmp3-tag-perl-1.13/debian/patches/series libmp3-tag-perl-1.14/debian/patches/series
--- libmp3-tag-perl-1.13/debian/patches/series	2017-07-13 05:22:53.0 +1000
+++ libmp3-tag-perl-1.14/debian/patches/series	2018-07-02 16:57:02.0 +1000
@@ -1,2 +1 @@
 01_spelling.patch
-02_fix_escape.patch
diff -Nru libmp3-tag-perl-1.13/lib/MP3/Tag/ID3v2.pm libmp3-tag-perl-1.14/lib/MP3/Tag/ID3v2.pm
--- libmp3-tag-perl-1.13/lib/MP3/Tag/ID3v2.pm	2010-01-03 04:12:40.0 +1100
+++ libmp3-tag-perl-1.14/lib/MP3/Tag/ID3v2.pm	2016-09-28 19:43:14.0 +1000
@@ -15,7 +15,7 @@
 	 %back_splt %embedded_Descr
 	/;
 
-$VERSION = "1.12";
+$VERSION = "1.14";
 @ISA = 'MP3::Tag::__hasparent';
 
 my $trustencoding = $ENV{MP3TAG_DECODE_UNICODE};
@@ -1398,6 +1398,16 @@
 return join '', @parts, $last;
 }
 
+sub have_one_of_frames {
+my $self = shift;
+return grep $self->frame_have($_), @_;
+}
+
+sub title_have {
+my $self = shift;
+$self->have_one_of_frames($self->v2title_order)
+}
+
 =item _comment([$language])
 
 Returns the file comment (COMM with an empty 'Description') from the tag, or
@@ -1406,8 +1416,8 @@
 
 =cut
 
-sub _comment {
-my $self = shift;
+sub __comment {
+my($self, 

Bug#903012: RFS: brise/0.38.20180515-2

2018-07-04 Thread Boyuan Yang
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: debian-input-met...@lists.debian.org  sunwea...@debian.org

Dear Mike, debian-input-method members and mentors,

I am looking for a sponsor for team-maintained package "brise".

With previous upload of brise (librime-data), I received a user bug report
(privately) about a regression. The bug is now documented in #902983. This
upload aims to solve that bug.



 * Package name: brise
   Version : 0.38.20180515-2
   Upstream Author : GONG Chen 
 * URL : https://github.com/rime/brise
 * License : GPL-3
   Section : libs



  It builds those binary packages:


 librime-data - Rime Input Method Engine, the schema data
 librime-data-array30 - RIME schema data - array30
 librime-data-bopomofo - RIME schema data - Bopomofo (a.k.a Zhu Yin)
 librime-data-cangjie5 - RIME schema data - Cangjie5
 librime-data-combo-pinyin - RIME schema data - Combo Pinyin (a.k.a Gong Bao
Pin Yin)
 librime-data-double-pinyin - RIME schema data - Double Pinyin (a.k.a Zi Ran
Ma Shuang Pin)
 librime-data-emoji - RIME schema data - Emoji
 librime-data-ipa-xsampa - RIME schema data - X-SAMPA
 librime-data-jyutping - RIME schema data - jyutping (a.k.a Cantonese)
 librime-data-luna-pinyin - RIME schema data - Luna Pinyin
 librime-data-pinyin-simp - RIME schema data - Pinyin Simp (a.k.a Xiu Zheng
Jian Hua Pin Yin)
 librime-data-quick5 - RIME schema data - quick5
 librime-data-sampheng - RIME schema data - sampheng (a.k.a Zhong Gu San Pin)
 librime-data-scj6 - RIME schema data - scj6 (a.k.a Fast Cangjie IM 6)
 librime-data-soutzoe - RIME schema data - soutzoe
 librime-data-stenotype - RIME schema data - stenotype
 librime-data-stroke - RIME schema data - Stroke
 librime-data-terra-pinyin - RIME schema data - Terra Pinyin (a.k.a Earth
Pinyin)
 librime-data-wubi - RIME schema data - Wubi
 librime-data-wugniu - RIME schema data - wugniu (a.k.a Shanghai Native
Language)
 librime-data-zyenpheng - RIME schema data - zyenpheng (a.k.a Medieval
Chinese)



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

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



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

dget -x https://mentors.debian.net/debian/pool/main/b/brise/
brise_0.38.20180515-2.dsc



  Git packaging repository:

https://salsa.debian.org/debian/brise.git



  Changes since the last upload:

 brise (0.38.20180515-2) unstable; urgency=medium
 .
   * Team upload.
   * Bump Standards-Version to 4.1.5. (no changes needed)
   * Fix the bug that users cannot save custom configurations
 by not installing /usr/share/rime-data/user.yaml and
 /usr/share/rime-data/build/default.yaml.
 Closes: #902983.



The source diff is also posted here to ease review:
===

commit f68eec2862b74a0bcac6765a167e79044b87d239
Author: Boyuan Yang <073p...@gmail.com>
Date:   Thu Jul 5 09:06:59 2018 +0800

debian: Prepare -2 upload that fixes #902983

diff --git a/debian/changelog b/debian/changelog
index fa52040..fee3159 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+brise (0.38.20180515-2) unstable; urgency=medium
+
+  * Team upload.
+  * Bump Standards-Version to 4.1.5. (no changes needed)
+  * Fix the bug that users cannot save custom configurations
+by not installing /usr/share/rime-data/user.yaml and
+/usr/share/rime-data/build/default.yaml.
+Closes: #902983.
+
+ -- Boyuan Yang <073p...@gmail.com>  Thu, 05 Jul 2018 09:18:23 +0800
+
 brise (0.38.20180515-1) unstable; urgency=medium

   * Team upload.
diff --git a/debian/control b/debian/control
index e85f574..b689100 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Build-Depends:
  debhelper (>= 11~),
  kyotocabinet-utils,
  librime-bin (>= 1.3~),
-Standards-Version: 4.1.4
+Standards-Version: 4.1.5
 Homepage: https://github.com/rime/brise
 Vcs-Git: https://salsa.debian.org/debian/brise.git
 Vcs-Browser: https://salsa.debian.org/debian/brise
diff --git a/debian/librime-data.install b/debian/librime-data.install
index 56de2ac..2b94f0d 100644
--- a/debian/librime-data.install
+++ b/debian/librime-data.install
@@ -1,5 +1,3 @@
 usr/share/rime-data/default.yaml
-usr/share/rime-data/user.yaml
 usr/share/rime-data/essay.txt
 usr/share/rime-data/symbols.yaml
-usr/share/rime-data/build/default.yaml
diff --git a/debian/rules b/debian/rules
index 19b3024..54ffb6b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -5,6 +5,10 @@
dh $@

 override_dh_missing:
+   # Explicitly remove config files to force librime not
+   # reading / writing them
+   rm -f debian/tmp/usr/share/rime-data/user.yaml
+   rm -f debian/tmp/usr/share/rime-data/build/default.yaml
dh_missing --fail-missing

 override_dh_auto_build:

==

--
Thanks,
Boyuan Yang



Bug#902937: xul-ext-stylish: more privacy concerns

2018-07-04 Thread Paul Wise
On Tue, 03 Jul 2018 19:10:37 +0200 Pavel Kreuzt wrote:

> https://robertheaton.com/2018/07/02/stylish-browser-extension-steals-your-internet-history/

Mozilla and Chrome have removed it from their addon stores:

https://bugzilla.mozilla.org/show_bug.cgi?id=1472948

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#898968: Re obuild: FTBFS on byte-code architectures

2018-07-04 Thread Andy Li
Hi Ralf,

Upstream has merged the fix

and I've integrated it as a patch to the package.
Would you review and upload it?

Best regards,
Andy


Bug#898556: I can confirm this on KDE NEON

2018-07-04 Thread Drake
I encounter the same bug on KDE Neon. So i think it has more to do with 
KDE then with debian.




Bug#903010: golang-gopkg-inf.v0: No Breaks/Replaces/Conflics with golang-speter-go-exp-math-dec-inf-dev

2018-07-04 Thread Dmitry Smirnov
Source: golang-gopkg-inf.v0
Version: 0.9.0-2
Severity: important
Control: affects -1 golang-speter-go-exp-math-dec-inf
X-Debbugs-CC: sa...@debian.org


This package introduced "gopkg.in/inf.v0" again without Breaks/Replaces/
Conflics with the original package "golang-speter-go-exp-math-dec-inf" which  
"Provides: golang-gopkg-inf.v0-dev".

"apt-file search" is a useful command to find which package provides "/usr/
share/gocode/src/gopkg.in/inf.v0".

-- 
Best wishes,
 Dmitry Smirnov
 GPG key : 2048R/CCBC38B3CCEE

---

If liberty means anything at all, it means the right to tell people what
they do not want to hear.
-- George Orwell


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


Bug#902946: [systemd/systemd] Fails to load autofs module through autofs4 alias (#9501)

2018-07-04 Thread Linus Torvalds
Trying to send test-patch to the Debian bug tracker too.. I suspect
this will be rejected as spam, but I can try.

Linus
 fs/autofs/Makefile | 4 ++--
 fs/autofs/init.c   | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/fs/autofs/Makefile b/fs/autofs/Makefile
index 43fedde15c26..1f85d35ec8b7 100644
--- a/fs/autofs/Makefile
+++ b/fs/autofs/Makefile
@@ -2,6 +2,6 @@
 # Makefile for the linux autofs-filesystem routines.
 #
 
-obj-$(CONFIG_AUTOFS_FS) += autofs.o
+obj-$(CONFIG_AUTOFS_FS) += autofs4.o
 
-autofs-objs := init.o inode.o root.o symlink.o waitq.o expire.o dev-ioctl.o
+autofs4-objs := init.o inode.o root.o symlink.o waitq.o expire.o dev-ioctl.o
diff --git a/fs/autofs/init.c b/fs/autofs/init.c
index cc9447e1903f..79ae07d9592f 100644
--- a/fs/autofs/init.c
+++ b/fs/autofs/init.c
@@ -23,7 +23,7 @@ static struct file_system_type autofs_fs_type = {
 	.kill_sb	= autofs_kill_sb,
 };
 MODULE_ALIAS_FS("autofs");
-MODULE_ALIAS("autofs4");
+MODULE_ALIAS("autofs");
 
 static int __init init_autofs_fs(void)
 {


Bug#903009: calligra: Does not use italic font styles

2018-07-04 Thread Alex Krusemark
Package: calligra
Version: 1:3.1.0+dfsg-2
Severity: normal

Dear Maintainer,

I found that Calligra is not using proper italic font styles for almost all 
fonts, but rather tilting the normal style ("oblique" effect). I tested this in 
Words, Stage, and Sheets, with several fonts such as Fira Sans, EB Garamond, 
and URW Palladio. These all display correct italic styles in other programs 
such as LibreOffice and Firefox. I think this bug is of some importance as it 
limits the ability to create professional-looking documents.

Thanks!
Alex


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

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

Versions of packages calligra depends on:
ii  calligrasheets  1:3.1.0+dfsg-2+b1
ii  calligrastage   1:3.1.0+dfsg-2+b1
ii  calligrawords   1:3.1.0+dfsg-2+b1
ii  karbon  1:3.1.0+dfsg-2+b1

calligra recommends no packages.

calligra suggests no packages.

-- no debconf information



Bug#900368: RFS: pygithub/1.40a3-1 [ITP]

2018-07-04 Thread eamanu15
Hello Dmitry,

I just pushed the update the package to Salsa. I pushed the PyGithub_1.40
version.

Regards!
Emmanuel

El mié., 4 de jul. de 2018 a la(s) 10:41, eamanu15 <
emmanuelaria...@gmail.com> escribió:

> Ok! Thanks !!!
>
> El mié., 4 de jul. de 2018 a la(s) 09:13, Dmitry Shachnev <
> mity...@debian.org> escribió:
>
>> On Wed, Jul 04, 2018 at 07:09:20AM -0300, eamanu15 wrote:
>> > Hello Dmitry,
>> >
>> > I have the fixes almost already, Just, I have a doubt in this point:
>> >
>> > > - When building in the current sid, I get Lintian warnings about
>> three files
>> > >   shipped in /usr/lib/python3.7/dist-packages/.
>> >
>> > To fix this problem I could add in the d/rules the next line:
>> >
>> > override_dh_auto_install:
>> > dh_auto_install
>> > find ./debian/python3-github/usr/lib/ -type f -name python3.*
>> -delete
>> >
>> > isn't?
>>
>> It is a directory, not a file. Also you need to do it after dh_python3
>> runs.
>> So better use this:
>>
>> override_dh_python3:
>> dh_python3
>> rm -rfv debian/python3-github/usr/lib/python3.*
>>
>> --
>> Dmitry Shachnev
>>
> --
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Bug#903008: procps does not show existing process

2018-07-04 Thread Igor Liferenko
Package: procps
Version: 2:3.3.15-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The following process is running on my machine:

$ ps -ef|grep qemu|grep -v grep
user 28971 28635  0 Jul04 pts/000:01:32 qemu-system-x86_64 -enable-kvm 
-display vnc=localhost:0 -hda newcd-qemu.qcow2 -cdrom newcd-qemu.iso -m 1G 
-boot once=d

It is shown as follows by ps from procps version 2:3.3.14-1+b1:

$ ps h -fC qemu-system-x86_64
user 28971 28635  0 Jul04 pts/0Sl+1:32 qemu-system-x86_64 
-enable-kvm -display vnc=local
Then I upgrade procps to version 2:3.3.15-2 and see an _empty_ output with the 
same command:

$ ps h -fC qemu-system-x86_64


Of course, qemu process is still running:

$ ps -ef|grep qemu|grep -v grep
user 28971 28635  0 Jul04 pts/000:01:32 qemu-system-x86_64 -enable-kvm 
-display vnc=localhost:0 -hda newcd-qemu.qcow2 -cdrom newcd-qemu.iso -m 1G 
-boot once=d

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

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

Versions of packages procps depends on:
ii  init-system-helpers  1.51
ii  libc62.27-3
ii  libncurses6  6.1+20180210-2
ii  libncursesw6 6.1+20180210-2
ii  libprocps7   2:3.3.15-2
ii  libtinfo66.1+20180210-2
ii  lsb-base 9.20170808

Versions of packages procps recommends:
ii  psmisc  23.1-1+b1

procps suggests no packages.

-- no debconf information



Bug#902555: radeon.4: Some fixes in the manual

2018-07-04 Thread Bjarni Ingi Gislason
On Fri, Jun 29, 2018 at 10:56:39AM +0200, Michel Dänzer wrote:
> On 2018-06-28 03:58 PM, G. Branden Robinson wrote:
> > At 2018-06-28T11:31:30+0200, Michel Dänzer wrote:
> >>
> >> Please send this kind of change directly upstream to the
> >> amd-...@lists.freedesktop.org list for review, split up into one patch
> >> per logical change.
> > 

  I sent the same patch upstream.

> > Well, a lot of these changes aren't "logical", they're stylistic.
> 
> Funny. :) I'm sure you know what I meant though:
> 
> Every item listed in Bjarni's report is logically a separate change.
> Mixing up logically separate changes (especially such a large number)
> makes for a hard to review patch. Hard to review patches are less likely
> to be applied.
> 
> Anyway, Bjarni, if you can send a proper patch generated by git
> format-patch, I'm willing to make an exception this time.
> 

  I do not work that way with a text in a single file.

1) The extra work producing x patches instead of one for a man page is
a waste of time.

2) The changes are independent of each other.

3) Reviewing a patch for a man page with more than one "logical" change
is only hard for those who have never or too rarely done that or lack
the knowledge and do not want to gain it.

4) You can do the "splitting" to multiple patches yourself, and if not,
why should other want to do it?

5) Using the same rule (one patch for each "logical" type of change) in
all cases is simply ineffective.


  Here is a script that shows changes caused by patches to man pages:

#!/bin/sh
# Compare two versions of a man page
# 

set -efu
inputA=${1##*/}
inputB=${2##*/}
cp $1 /tmp/$inputA
cp $2 /tmp/$inputB

cd /tmp

MAN_KEEP_STDERR=yes
MANOPT='--warnings=w --no-justification --no-hyphenation'
MANWIDTH=80
export MAN_KEEP_STDERR MANOPT MANWIDTH

# Have no sentence space (.ss 12 0)

sed -e '/^.TH /i \
.ss 12 0' $inputA  | man -l - > \
  old.$inputA.txt 2> /dev/null

sed -e '/^.TH /i \
.ss 12 0' $inputB  | man -l - > \
  new.$inputA.txt 2> /dev/null

diff -adu old.$inputA.txt new.$inputA.txt > $inputA.txt.diff || :

# Difference in the output of "troff"

{ sed -e '/^.TH /i \
.ss 12 0\
.ad l' $inputA ; } | groff -t \
  -rHY=0 -rF0 -mandoc -Z - > old.$inputA.ml 2> /dev/null

{ sed -e '/^.TH /i \
.ss 12 0\
.ad l' $inputB ; } | \
  groff -t -rHY=0 -rF0 -mandoc -Z - > new.$inputA.ml 2> /dev/null

diff -adu old.$inputA.ml new.$inputA.ml > $inputA.ml.diff || :

less $inputA.txt.diff

less $inputA.ml.diff

-- 
Bjarni I. Gislason



Bug#903007: Failing test: trustingpolicy-replay

2018-07-04 Thread Ian Jackson
Control: tags -1 confirmed
Control: usertag -1 rsn

Also, is it possible you have a funny version of dput ?  It's weird
that I can't reproduce this.

Some observations:

I suspect it is the t-dgit-push call on l.27 of trustingpolicy-replay
that is failing.  That is preceeded by t-rm-dput-dropping.

In my log that call seems to do this
  + rm -f 
/home/ian/things/Dgit/2dgit/tests/tmp/trustingpolicy-replay/example_1.1_amd64.test-dummy.upload
which I note is 1.1, not the 1.0 in your failing log.  And nobbling
that call does nothing so I am not (now) relying on it.

I don't know how to make my dput complain like yours, but the
t-rm-dput-dropping eems like it is in the wrong place.

OTOH, AFAICT the test has always been broken in the same way, which is
weird, because why would I have this call to t-rm-dput-dropping if it
never worked ?  (Mind you the commit author dates are two weeks
apart.)

Can you try the attached diff and see if it helps ?

Do you know anything about how to get my dput to complain about this
problem ?

...

Ah.  You have dput-ng.  The light dawns.

Ian.

diff --git a/tests/tests/trustingpolicy-replay 
b/tests/tests/trustingpolicy-replay
index ad731f5b..f76835ad 100755
--- a/tests/tests/trustingpolicy-replay
+++ b/tests/tests/trustingpolicy-replay
@@ -16,12 +16,12 @@ git tag start
 
 t-dgit build
 t-dgit push --new
+t-rm-dput-dropping
 
 t-commit 'Prep v1.1 which will be rewound'
 t-dgit build
 t-dgit push
 
-t-rm-dput-dropping
 git checkout $tagpfx/1.0
 t-dgit build
 t-dgit push --deliberately-fresh-repo

-- 
Ian JacksonThese opinions are my own.

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


Bug#903007: Failing test: trustingpolicy-replay

2018-07-04 Thread Ian Jackson
Sean Whitton writes ("Bug#903007: Failing test: trustingpolicy-replay"):
> ! If that .changes file is broken, you will need to use a new version
> ! number for your next attempt at the upload.
> + test 255 = 0
> + t-report-failure
> + set +x
> TEST FAILED
> 
> I can provide the full log by private mail.

Yes, please.  Also, next time, please don't snip the end of the test
log.  That random-looking junk at the end has the line numbers in it
:-).

Ian.

-- 
Ian JacksonThese opinions are my own.

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



Bug#903006: Indeterminacy issues with import-nonnative and import-tarbomb tests

2018-07-04 Thread Ian Jackson
Control: tags -1 confirmed
Control: usertags -1 rsn

Sean Whitton writes ("Bug#903006: Indeterminacy issues with import-nonnative 
and import-tarbomb tests"):
> On my machine, outside of autopkgtest only, these tests are failing
> because of something to do with file ordering:

I have reproduced an apparently-similar bug by running the tests with
  LC_COLLATE=en_US.UTF-8

It's not quite identical though.  What is your locale ?
Ie, output of locale(1).

Ian.



Bug#903007: Failing test: trustingpolicy-replay

2018-07-04 Thread Sean Whitton
Source: dgit
Version: 5.6
Severity: normal

When I run

swhitton@zephyr:~/src/dgit>DGIT_DRS_DEBUG=2 DGIT_TEST_DEBUG=-DD 
tests/using-intree tests/tests/trustingpolicy-replay

the test fails, with the following tail:

+ git update-ref -m 'dgit push' refs/remotes/dgit/dgit/sid 
17d67dbd8f2a46fa824ed7aa5aecd7893ac1dcf9
+ debsign -kBCD22CD83243B79D3DFAC33EA3DBCBC039B13D8A 
../example_1.0_i386.changes
 signfile dsc ../example_1.0.dsc BCD22CD83243B79D3DFAC33EA3DBCBC039B13D8A
gpg: WARNING: unsafe permissions on homedir 
'/home/swhitton/src/dgit/tests/tmp/trustingpolicy-replay/gnupg'
gpg: WARNING: unsafe permissions on homedir 
'/home/swhitton/src/dgit/tests/tmp/trustingpolicy-replay/gnupg'

 fixup_buildinfo ../example_1.0.dsc ../example_1.0_i386.buildinfo
 signfile buildinfo ../example_1.0_i386.buildinfo 
BCD22CD83243B79D3DFAC33EA3DBCBC039B13D8A
gpg: WARNING: unsafe permissions on homedir 
'/home/swhitton/src/dgit/tests/tmp/trustingpolicy-replay/gnupg'
gpg: WARNING: unsafe permissions on homedir 
'/home/swhitton/src/dgit/tests/tmp/trustingpolicy-replay/gnupg'

 fixup_changes dsc ../example_1.0.dsc ../example_1.0_i386.changes
 fixup_changes buildinfo ../example_1.0_i386.buildinfo 
../example_1.0_i386.changes
 signfile changes ../example_1.0_i386.changes 
BCD22CD83243B79D3DFAC33EA3DBCBC039B13D8A
gpg: WARNING: unsafe permissions on homedir 
'/home/swhitton/src/dgit/tests/tmp/trustingpolicy-replay/gnupg'
gpg: WARNING: unsafe permissions on homedir 
'/home/swhitton/src/dgit/tests/tmp/trustingpolicy-replay/gnupg'

Successfully signed dsc, buildinfo, changes files
+ dput 
--config=/home/swhitton/src/dgit/tests/tmp/trustingpolicy-replay/dput.cf 
test-dummy ../example_1.0_i386.changes
Package example was already uploaded to test-dummy
If you want to upload nonetheless, use --force or remove 
../example_1.0_i386.test-dummy.upload
dgit: failed command: dput 
--config=/home/swhitton/src/dgit/tests/tmp/trustingpolicy-replay/dput.cf 
test-dummy ../example_1.0_i386.changes

dgit: error: subprocess failed with error exit status 3
CD /home/swhitton/src/dgit/tests/tmp/trustingpolicy-replay/example
del_lrfetchrefs...
del_lrfetchrefs: a3deec3b729eca8477d7f697f6e1b11629c2cd3b 
refs/dgit-fetch/test-dummy/dgit/sid
del_lrfetchrefs: 7a791d2605c0bade66022fd6561146c3b8477bfe 
refs/dgit-fetch/test-dummy/tags/archive/test-dummy/1.0
del_lrfetchrefs: ff222df94c394245d601c931886cde59bac38406 
refs/dgit-fetch/test-dummy/tags/archive/test-dummy/1.1
! Push failed, while uploading package(s) to the archive server.
! You can retry the upload of exactly these same files with dput of:
!   ../example_1.0_i386.changes
! If that .changes file is broken, you will need to use a new version
! number for your next attempt at the upload.
+ test 255 = 0
+ t-report-failure
+ set +x
TEST FAILED

I can provide the full log by private mail.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#903006: Indeterminacy issues with import-nonnative and import-tarbomb tests

2018-07-04 Thread Sean Whitton
Source: dgit
Version: 5.6
Severity: normal

On my machine, outside of autopkgtest only, these tests are failing
because of something to do with file ordering:

I used these commands:

swhitton@zephyr:~/src/dgit>DGIT_DRS_DEBUG=2 DGIT_TEST_DEBUG=-DD 
tests/using-intree tests/tests/import-tarbomb

swhitton@zephyr:~/src/dgit>DGIT_DRS_DEBUG=2 DGIT_TEST_DEBUG=-DD 
tests/using-intree tests/tests/import-nonnative

and here is the tail of the output:

import-tarbomb:

+ git ls-tree -r --name-only 3bcfe9c1354089cb84a0e112aaac39d8cb2e9c99:
+ sort
+ diff ../files.o ../files.g
1,4d0
< .gitignore
< COPYING
< Makefile
< README
12d7
< boot_head.S
13a9
> boot_head.S
15a12,13
> COPYING
> fel.c
22d19
< fel.c
24a22
> .gitignore
27d24
< jtag-loop.S
29a27,28
> jtag-loop.S
> Makefile
33d31
< nand-part-main.c
34a33
> nand-part-main.c
37,38c36
< script.c
< script.h
---
> README
40a39
> script.c
42a42
> script.h
+ test 1 = 0
+ t-report-failure
+ set +x
TEST FAILED

import-nonnative:

+ git ls-tree -r --name-only 3bcfe9c1354089cb84a0e112aaac39d8cb2e9c99:
+ sort
+ diff ../files.o ../files.g
1,4d0
< .gitignore
< COPYING
< Makefile
< README
12d7
< boot_head.S
13a9
> boot_head.S
15a12,13
> COPYING
> fel.c
22d19
< fel.c
24a22
> .gitignore
27d24
< jtag-loop.S
29a27,28
> jtag-loop.S
> Makefile
33d31
< nand-part-main.c
34a33
> nand-part-main.c
37,38c36
< script.c
< script.h
---
> README
40a39
> script.c
42a42
> script.h
+ test 1 = 0
+ t-report-failure
+ set +x
TEST FAILED

I can provide the full logs by private mail if that's needed; I'd prefer
not to post publically as it's possible they'll contain info about my
machine.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#902967: RFS: ddnet/11.2.1-1

2018-07-04 Thread Adam Borowski
On Wed, Jul 04, 2018 at 12:23:25PM +0800, Yangfl wrote:
>  * Package name: ddnet
>Version : 11.2.1-1
  ^

>   dget -x 
> https://mentors.debian.net/debian/pool/main/d/ddnet/ddnet_11.2.1-2.dsc
 ^
> 
> Changes since the last upload:
> 
>   * New upstream release

Hi!
The version you're requesting sponsorship for, and the one you pointed to,
are different.  The changelog in the latter is:

+ddnet (11.2.1-2) unstable; urgency=medium
+
+  * New upstream release
+
+ -- Yangfl   Wed, 04 Jul 2018 00:17:11 +0800
+
 ddnet (11.1.8-1) unstable; urgency=medium

with no trace of 11.2.1-1 anywhere.

Is something amiss?


喵!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.



Bug#903005: stretch-pu: package clamav/0.100.0+dfsg-0+deb9u1

2018-07-04 Thread Sebastian Andrzej Siewior
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: stretch
Severity: normal

0.100.0 clamav version had a few config options removed. This is covered
by postinst as long as the config is handled by debconf. If the user
makes changes manually then ucf ask the user to resolve it and if nothing 
happens
(during unattended-upgrades) then the old options remain set and clamav
refuses to start.
This was reported during the deb8 point upgrade. To avoid this during
the upcomming deb9 upgrade I hereby propose a patch to simply declare
the removed options as "deprecated" which results in a warning like
| clamd[8720]: WARNING: Ignoring deprecated option StatsTimeout at line 88
| clamd[8720]: WARNING: Ignoring deprecated option StatsPEDisabled at line 89

in the log file and clamav continues.

In terms of full disclosure: There is a yara regression within clamav
(that is if you use clamav-unofficial-sigs) as reported in #902899
yesterday. The bug has been reported on 16th April to
clamav-unofficial-sigs upstream (as per the forwarded link in BTS) and
nothing happend since. Give the freeze this weekend I don't think that
this will change for Stretch.

Sebastian
diff -Nru clamav-0.100.0+dfsg/debian/changelog clamav-0.100.0+dfsg/debian/changelog
--- clamav-0.100.0+dfsg/debian/changelog	2018-04-25 21:59:49.0 +0200
+++ clamav-0.100.0+dfsg/debian/changelog	2018-07-04 23:14:43.0 +0200
@@ -1,3 +1,9 @@
+clamav (0.100.0+dfsg-0+deb9u2) stretch; urgency=medium
+
+  * Don't fail on recently removed config options (Closes: #902290).
+
+ -- Sebastian Andrzej Siewior   Wed, 04 Jul 2018 23:14:43 +0200
+
 clamav (0.100.0+dfsg-0+deb9u1) stretch; urgency=medium
 
   [ Sebastian Andrzej Siewior ]
diff -Nru clamav-0.100.0+dfsg/debian/.git-dpm clamav-0.100.0+dfsg/debian/.git-dpm
--- clamav-0.100.0+dfsg/debian/.git-dpm	2018-04-25 21:59:43.0 +0200
+++ clamav-0.100.0+dfsg/debian/.git-dpm	2018-07-04 22:11:57.0 +0200
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-7a040ad8b6aad81cd3b37661345727e43e3cd78a
-7a040ad8b6aad81cd3b37661345727e43e3cd78a
+e7d1d6e337cc5ecf533b991879c6374a71c0bf18
+e7d1d6e337cc5ecf533b991879c6374a71c0bf18
 c6bf3661e036ec9579e544d999438b0147e75315
 c6bf3661e036ec9579e544d999438b0147e75315
 clamav_0.100.0+dfsg.orig.tar.xz
diff -Nru clamav-0.100.0+dfsg/debian/patches/Deprecate-unused-options-instead-of-removing-it.patch clamav-0.100.0+dfsg/debian/patches/Deprecate-unused-options-instead-of-removing-it.patch
--- clamav-0.100.0+dfsg/debian/patches/Deprecate-unused-options-instead-of-removing-it.patch	1970-01-01 01:00:00.0 +0100
+++ clamav-0.100.0+dfsg/debian/patches/Deprecate-unused-options-instead-of-removing-it.patch	2018-07-04 22:11:57.0 +0200
@@ -0,0 +1,60 @@
+From e7d1d6e337cc5ecf533b991879c6374a71c0bf18 Mon Sep 17 00:00:00 2001
+From: Sebastian Andrzej Siewior 
+Date: Wed, 4 Jul 2018 21:26:50 +0200
+Subject: Deprecate unused options instead of removing it
+
+The following options were removed:
+- StatsHostID
+- StatsEnabled
+- StatsPEDisabled
+- StatsTimeout
+- SubmitDetectionStats
+- DetectionStatsCountry
+- DetectionStatsHostID
+
+and if they remain in the config file (during automatic upgrade without
+user action which would be required by ucf) then clamav will refuse the
+start. By marking them as deprecated clamav will point it out and
+continue. This patch will be dropped by moving to next Debian stable
+version (the user is expected to edit the config manually at this
+point if it did not happen earlier).
+
+BTS: https://bugs.debian.org/902290
+Patch-Name: Deprecate-unused-options-instead-of-removing-it.patch
+Signed-off-by: Sebastian Andrzej Siewior 
+---
+ shared/optparser.c | 14 ++
+ 1 file changed, 14 insertions(+)
+
+diff --git a/shared/optparser.c b/shared/optparser.c
+index b5a7208..7dea853 100644
+--- a/shared/optparser.c
 b/shared/optparser.c
+@@ -194,6 +194,14 @@ const struct clam_option __clam_options[] = {
+ 
+ { "LogFile", "log", 'l', CLOPT_TYPE_STRING, NULL, -1, NULL, 0, OPT_CLAMD | OPT_MILTER | OPT_CLAMSCAN | OPT_CLAMDSCAN, "Save all reports to a log file.", "/tmp/clamav.log" },
+ 
++{ "StatsHostID", "stats-host-id", 0, CLOPT_TYPE_STRING, NULL, -1, NULL, 0, OPT_FRESHCLAM | OPT_CLAMD | OPT_CLAMSCAN | OPT_DEPRECATED, "HostID in the form of an UUID to use when submitting statistical information. See the clamscan manpage for more information.", "default" },
++
++{ "StatsEnabled", "enable-stats", 0, CLOPT_TYPE_BOOL, MATCH_BOOL, 0, NULL, 0, OPT_CLAMD | OPT_FRESHCLAM | OPT_CLAMSCAN | OPT_DEPRECATED, "Enable submission of statistical data", "yes" },
++
++{ "StatsPEDisabled", "disable-pe-stats", 0, CLOPT_TYPE_BOOL, MATCH_BOOL, 0, NULL, 0, OPT_CLAMD | OPT_CLAMSCAN | OPT_DEPRECATED, "Disable submission of PE section statistical data", "no" },
++
++{ "StatsTimeout", "stats-timeout", 0, CLOPT_TYPE_NUMBER, MATCH_NUMBER, -1, NULL, 0, OPT_CLAMD | OPT_CLAMSCAN | OPT_FRESHCLAM | 

Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

2018-07-04 Thread Sven Joachim
On 2018-07-04 23:33 +0200, Michael Biebl wrote:

> Control: tags -1 moreinfo
>
>
> This is what I get when I build a package using pbuilder, which
> build-depends on policykit-1 (which in turn pulls in libpam-systemd):
>
> The following packages have unmet dependencies:
>  systemd : Breaks: systemd-shim (< 10-4~) but 10-3 is to be installed
> The following actions will resolve these dependencies:
>
>  Install the following packages:
> 1) systemd-sysv [239-4 (unstable)]
>
>  Keep the following packages at their current version:
> 2) systemd-shim [Not Installed]
>
> And the build succeeds.
>
> Or running apt install libpam-systemd inside a chroot:
>
> # apt install libpam-systemd
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following additional packages will be installed:
>   dbus dmsetup libapparmor1 libargon2-0 libargon2-1 libcap2
> libcryptsetup12 libdbus-1-3 libdevmapper1.02.1 libexpat1
>   libidn11 libip4tc0 libjson-c3 libkmod2 libprocps7 lsb-base procps
> systemd systemd-sysv
> Suggested packages:
>   default-dbus-session-bus | dbus-session-bus systemd-container policykit-1
> Recommended packages:
>   psmisc libnss-systemd
> The following NEW packages will be installed:
>   dbus dmsetup libapparmor1 libargon2-0 libargon2-1 libcap2
> libcryptsetup12 libdbus-1-3 libdevmapper1.02.1 libexpat1
>   libidn11 libip4tc0 libjson-c3 libkmod2 libpam-systemd libprocps7
> lsb-base procps systemd systemd-sysv
> 0 upgraded, 20 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/5069 kB of archives.
> After this operation, 17.4 MB of additional disk space will be used.
> Do you want to continue? [Y/n] n
> Abort.

This works, but "apt install libgtk-3-0" does not, for instance:

,
| # apt install libgtk-3-0
| Reading package lists... Done
| Building dependency tree   
| Reading state information... Done
| Some packages could not be installed. This may mean that you have
| requested an impossible situation or if you are using the unstable
| distribution that some required packages have not yet been created
| or been moved out of Incoming.
| The following information may help to resolve the situation:
| 
| The following packages have unmet dependencies:
|  libgtk-3-0 : Depends: libgtk-3-common (>= 3.22.30-2) but it is not going to 
be installed
|   Depends: librest-0.7-0 (>= 0.7) but it is not going to be 
installed
|   Depends: libsoup2.4-1 (>= 2.4.0) but it is not going to be 
installed
| E: Unable to correct problems, you have held broken packages.
`

Cheers,
   Sven



Bug#900314: [patch] relax dh 11 build dep to 11~ so a no-change bpo remains possible

2018-07-04 Thread Nicholas D Steeves
Hi Dimitri,

Sorry for the delay replying, sometimes I forget to send emails in my
draft folder when returning to some place with internet access.

On Tue, May 29, 2018 at 10:00:12AM +0100, Dimitri John Ledkov wrote:
> Hello,
> 
> On 29 May 2018 at 01:47, Nicholas D Steeves  wrote:
> > Package: btrfs-progs
> > Version: 4.16.1-1
> > Severity: normal
> > Control: tags -1 patch
> >
> > Hi Dimitri,
> >
> > Trivial patch attached.  The rational is debhelper/11.2.1~bpo9+1 does not 
> > fulfill >= 11, so 11 should be 11~.
> >
> 
> NAK
> 
> 4.16.1 should not be backported as a no-change rebuild. The runtime
> libraries and headers moved, thus breaking existing software in stable
> releases.

Does anything besides snapper use these?  I plan to add breaks
package-version~ for these.

> Also, the transitional package was removed, breaking package declared
> dependencies in earlier releases.

Affected in stretch: xen-tools, schroot, lxc, linaro-image-tools, kvpm, 
fsarchiver

and

libguestfs0: depends on both btrfs-progs and btrfs-tools (yes, really!)

Ok, I agree, a no-change backport is not appropriate, and I'll need to
add the transitional package back in. On a closely-related topic,
would you please consider maintaining the package in git?

Sincerely,
Nicholas


signature.asc
Description: PGP signature


Bug#889056: [RFC: original vs fork] Re: Bug#889056: replace apache-mode.el with elpa package

2018-07-04 Thread Sean Whitton
Hello,

On Tue, Jul 03 2018, Nicholas D Steeves wrote:

> What about in the case of forks?  Eg: goodies' apache-mode is the
> original, by Jonathan Marten.

I still don't see any need for an ITP.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#891793: obfsproxy 0.2.13-2+deb9u1 flagged for acceptance

2018-07-04 Thread Adam D Barratt
Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: obfsproxy
Version: 0.2.13-2+deb9u1

Explanation: don't install the broken AppArmor profile



Bug#903004: scour: Please upgrade to 0.37

2018-07-04 Thread Niels Thykier
Package: scour
Version: 0.36-3
Severity: wishlist

Hi,

Upstream just released version 0.37, which fixes invalid optimizations
and improve performance considerably in some cases.

Please consider updating scour to 0.37 for buster.  :)

Thanks,
~Niels



Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

2018-07-04 Thread Michael Biebl
Control: tags -1 moreinfo


This is what I get when I build a package using pbuilder, which
build-depends on policykit-1 (which in turn pulls in libpam-systemd):

The following packages have unmet dependencies:
 systemd : Breaks: systemd-shim (< 10-4~) but 10-3 is to be installed
The following actions will resolve these dependencies:

 Install the following packages:
1) systemd-sysv [239-4 (unstable)]

 Keep the following packages at their current version:
2) systemd-shim [Not Installed]

And the build succeeds.

Or running apt install libpam-systemd inside a chroot:

# apt install libpam-systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  dbus dmsetup libapparmor1 libargon2-0 libargon2-1 libcap2
libcryptsetup12 libdbus-1-3 libdevmapper1.02.1 libexpat1
  libidn11 libip4tc0 libjson-c3 libkmod2 libprocps7 lsb-base procps
systemd systemd-sysv
Suggested packages:
  default-dbus-session-bus | dbus-session-bus systemd-container policykit-1
Recommended packages:
  psmisc libnss-systemd
The following NEW packages will be installed:
  dbus dmsetup libapparmor1 libargon2-0 libargon2-1 libcap2
libcryptsetup12 libdbus-1-3 libdevmapper1.02.1 libexpat1
  libidn11 libip4tc0 libjson-c3 libkmod2 libpam-systemd libprocps7
lsb-base procps systemd systemd-sysv
0 upgraded, 20 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/5069 kB of archives.
After this operation, 17.4 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.


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



signature.asc
Description: OpenPGP digital signature


Bug#892278: reportbug 7.1.7+deb9u2 flagged for acceptance

2018-07-04 Thread Adam D Barratt
Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: reportbug
Version: 7.1.7+deb9u2

Explanation: notify the security team or LTS team about a possible regression 
if reporting a bug against a package containing a security fix



Bug#891788: starplot 0.95.5-8.2+deb9u1 flagged for acceptance

2018-07-04 Thread Adam D Barratt
Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: starplot
Version: 0.95.5-8.2+deb9u1

Explanation: fix startup crash



Bug#880037: dput-ng 1.13+deb9u1 flagged for acceptance

2018-07-04 Thread Adam D Barratt
Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: dput-ng
Version: 1.13+deb9u1

Explanation: add jessie-backports-sloppy and stretch-backports targets; include 
'testing' in the rm-managed suites and 'oldstable' in "protected 
distributions"; add ports-master profile; FTP: parse and use optional [:port] 
part for fqdn;



Bug#857470: [patch] Suggests: btrfs-tools to btrfs-progs

2018-07-04 Thread Nicholas D Steeves
Control: severity -1 important

On Tue, May 08, 2018 at 08:19:52PM -0400, Nicholas D Steeves wrote:
> Hi,
> 
> On Tue, Oct 17, 2017 at 01:01:41PM -0400, Nicholas D Steeves wrote:
> > Package: schroot
> > Version: 1.6.10-3+b1
> > Followup-For: Bug #857470
> > Control: tags -1 + patch
> > 
> > The attached patch is against 1.7.2-3 of the debian/experimental branch in 
> > VCS.  Atternatively, against git tag "debian/1.7.2-3".
> > 
> > Btrfs-progs is present in stretch so this will not cause problems in
> > stretch-backports.
> > 
> > I am also submitting patches for:
> >   systemd-container
> >   xen-tools
> >   udisks2
> >   snapper
> >   lxc
> >   linaro-image-tools
> >   libguestfs0
> >   kvpm
> >   fsarchiver
> >   btrbk
> > 
> > Cheers,
> > Nicholas
> 
> It looks like the patch didn't make it into schroot/1.6.10-4.  Would
> someone please apply it to preemptively avoid breakage due to the
> eventual (maybe in buster?) removal of the btrfs-tools dummy package.
> 
> Thanks,
> Nicholas

Btrfs-tools transitional package was dropped 08 May with
btrfs-progs/4.16.1-1.  Bumping severity.

Cheers,
Nicholas



signature.asc
Description: PGP signature


Bug#891791: local-apt-repository 0.4+deb9u1 flagged for acceptance

2018-07-04 Thread Adam D Barratt
Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: local-apt-repository
Version: 0.4+deb9u1

Explanation: stop breaking apt when the package is removed but not purged



Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

2018-07-04 Thread Alexis Murzeau
Hi,

Le 27/06/2018 à 00:21, Alexis Murzeau a écrit :
> Le 26/06/2018 à 04:13, vasudev-debian a écrit :
>> I'll have a look. if possible clone from team repo and raise a pr on it.
>>
> 
> I've created 3 PR at [0], one for each branch (in this order: upstream,
> pristine-tar and master).
> The 5.0.10+really4.7.0~dfsg orig tar I imported is the same as the one
> used for 4.7.0~dfsg.
> Debian/watch file tracks the v4 branch (ignoring v5.*)
> I've also added a autopkgtest test to ensure symlinks are not broken.
> 
> [0] https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests
> 
> Le 26/06/2018 à 09:26, Sean Whitton a écrit :
>>
>> The git history is up to you but resetting the changelog seems like a
>> really bad idea -- it is confusing to see that there are uploads to the
>> archive that are not present in the changelog.
>>
>> I think you should at least retain d/changelog, even if you reset
>> everything else (personally, I would keep all the git history).
>>
> 
> I finally kept the full changelog and git history, to not lie the past
> :) if someone wonders what happened.
> Thanks for your advices.
> 

Vasudev, did you get a chance to take a look to the merge requests [0] ?

[0] https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests

-- 
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F



signature.asc
Description: OpenPGP digital signature


Bug#878910: [patch] change suggests btrfs-tools to btrfs-progs

2018-07-04 Thread Nicholas D Steeves
Control: severity -1 important

Hi Axel,

On Tue, Mar 20, 2018 at 09:47:11PM -0400, Nicholas D Steeves wrote:
> Hi Axel,
> 
> On Wed, Mar 21, 2018 at 02:40:04AM +0100, Axel Beckert wrote:
> > Hi Nicholas,
> > 
> > Nicholas D Steeves wrote:
> > > [...], I noticed this bug was still open.  Has
> > > 
> > > - btrfs-tools
> > > + btrfs-progs | btrfs-tools
> > > 
> > > been fixed in git yet?
> > 
> > It's fixed in git, yes:
> > https://github.com/xen-tools/xen-tools/commit/6485f686b76b4b840db5ab7c0312e7d2dbec4c38
> > 
> > I just haven't come around doing a new release.
> 
> Thank you for the update :-)  No rush for a new release!

Btrfs-tools transitional package was dropped from buster with 08 May's
btrfs-progs/4.16.1-1.  Bumping priority accordingly.

Cheers,
Nicholas


signature.asc
Description: PGP signature


Bug#901990: linux-image-4.16.0-2-amd64: kernel BUG at startup in usercopy.c ; impossible to boot

2018-07-04 Thread Ludovic Pouzenc
Package: nvidia-kernel-dkms
Version: 390.48-2~bpo9+3
Followup-For: Bug #901990

Dear Maintainer,

It happens to me to, with AMD Ryzen and 4.16.0-0.bpo.2-amd64.
I am fine with 4.16.0-0.bpo.1-amd64. I've rebooted on vmlinux.old to
reportbug.
I'll try driver from sid.


-- Package-specific info:
uname -a:
Linux lud-MN1 4.16.0-0.bpo.1-amd64 #1 SMP Debian 4.16.5-1~bpo9+1 (2018-05-06) 
x86_64 GNU/Linux

/proc/version:
Linux version 4.16.0-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.16.5-1~bpo9+1 
(2018-05-06)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 PDT 
2018
GCC version:  gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) 

lspci 'display controller [030?]':
07:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 
1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 3GB] 
[1043:85b9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Jul  4 19:57 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Jul  4 19:57 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 Jul  4 19:57 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 Jul  4 19:57 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Jul  4 19:57 /dev/nvidiactl
video:x:44:lpouzenc

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Feb 17 12:02 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   42 Feb 17 12:02 
/etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   44 Feb 17 12:02 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   41 Feb 17 12:02 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   41 Feb 17 12:02 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Feb 17 12:02 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Feb 17 12:02 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   48 Feb 17 12:02 
/etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   48 Feb 17 12:02 
/etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   50 Feb 17 12:02 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   50 Feb 17 12:02 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   45 Feb 17 12:02 
/etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 root root   45 Feb 17 12:02 
/etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 root root   47 Feb 17 12:02 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 root root   47 Feb 17 12:02 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 root root   49 Feb 17 12:02 
/etc/alternatives/glx--libnvidia-cfg.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   51 Feb 17 12:02 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   25 Feb 17 12:02 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Feb 17 12:02 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Feb 17 12:02 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Feb 17 12:02 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Feb 17 12:02 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Feb 17 12:02 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root 

Bug#900867: ITP: firefox-syncserver -- Firefox Sync storage and token server

2018-07-04 Thread Phil Morrell
Control: retitle -1 RFP: firefox-syncserver -- Firefox Sync storage and token 
server
Control: noowner -1
thanks

I've stopped work on this and am for now just using the upstream make
serve. I still think it would be good for Debian, but first the storage
project and the token project need packaging, starting with the deps:

https://github.com/mozilla-services/tokenserver/blob/master/requirements.txt


signature.asc
Description: PGP signature


Bug#902949: RFS: elpy/1.22.0-1

2018-07-04 Thread Nicholas D Steeves
Hi Chris,

On Wed, Jul 04, 2018 at 09:54:44AM +0100, Chris Lamb wrote:
> tags 902949 + pending
> thanks
> 
> Hi Nicholas,
> 
> >   dget -x 
> > https://mentors.debian.net/debian/pool/main/e/elpy/elpy_1.22.0-1.dsc
> 
> elpy_1.22.0-1_amd64.changes uploaded.
>

Thank you for sponsoring :-)

> FYI:
> 
>  * No need for "[ Nicholas D Steeves ]" sections if you are the only
>person in the changelog.

Ah, sorry, that was an oversight due to carelessness--I've been
working on a lot of collaborative packages and have been leaning
heavily on gbp dch -a.

>  * wrong-section-according-to-package-name lintian warning.

Yes, when lintian downgraded this warning to informational in
lintian/2.5.69, I talked with Emacsen team members Sean and David
(Sean is also a member of the Policy Team) about how much latitude a
packager has in defining his/her package's section.  For a similar
case, Magit has section vcs, which I agree is more precise and
discoverable than section lisp.  Consequently I filed a section change
request for Elpy in Bug #900212 and made the change in d/control for
elpy/1.21.0-1.

Cheers,
Nicholas


signature.asc
Description: PGP signature


Bug#900533: The bug still exists in stable

2018-07-04 Thread Michael Wyraz

Hi,

I'm running chromium 67.0.3396.87-1~deb9u1 on stable - the bug still 
occurs here.


Example video: https://www.dailymotion.com/video/x6nlrix (just randomly 
picked from dailymotion)


Behaviour: nothing happens when pressing the play button

Console message: 
[289:318:0704/224715.089182:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[289:289:0704/224715.089572:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN


Tested with a fresh clean chromium profile.



Bug#902997: pulseaudio: every other time sound card does not get loaded

2018-07-04 Thread sergey
No, nobody is holding it. But I've found a clue. Sometimes PCI and 
build-in cards get assigned different names upon boot. When PCI card 
works, its associated file is /dev/controlC3. When it doesn't work, its 
file is /dev/controlC0.




Bug#891784: abiword 3.0.2-2+deb9u2 flagged for acceptance

2018-07-04 Thread Adam D Barratt
Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: abiword
Version: 3.0.2-2+deb9u2

Explanation: resolve binary file conflict between abiword-dbgsym and 
abiword-plugin-grammar-dbgsym



Bug#891470: auto-complete-el 1.3.1-2+deb9u1 flagged for acceptance

2018-07-04 Thread Adam D Barratt
Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: auto-complete-el
Version: 1.3.1-2+deb9u1

Explanation: add upstream fix for emacs25; adjust the emacs dependencies to the 
emacs versions in stretch; set auto-complete-el.emacsen-compat to silence 
installation warning



Bug#901919: nvidia-driver: black screen with the latest Linux kernel

2018-07-04 Thread Luca Boccassi
On Wed, 2018-07-04 at 19:44 +0200, Andreas Beckmann wrote:
> On 2018-07-04 01:54, Andreas Beckmann wrote:
> > On 2018-07-04 01:30, Andreas Beckmann wrote:
> > > I've prepared that in the 390 branch - could you give it a test
> > > run
> > > (with all workarounds disabled)?
> > 
> > patch is not backwards compatible to older kernels:
> 
> I think I fixed that. I also tried to backport the patch to the 340xx
> series. The 390/340 modules build for all kernels that I have in my
> kmod
> testbuild chroot, but I cannot test any of them.
> 
> 
> Andreas

Just tested on stretch + 4.9 and 4.16, and sid + 4.16, seems to work as
intended.

-- 
Kind regards,
Luca Boccassi

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


Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

2018-07-04 Thread Michael Biebl
Am 04.07.2018 um 20:39 schrieb Helmut Grohne:
> Package: libpam-systemd
> Version: 239-4
> Severity: critical
> Justification: makes gnupg2 ftbfs
> User: helm...@debian.org
> Usertags: rebootstrap
> Control: affects -1 + src:gnupg2
> 
> A native(!) build of gnupg2 with sbuild and
> --bd-uninstallable-explainer=apt fails. dose3 finds an installation set,
> but it is too tricky to find for apt and it is caused by systemd, which
> simultaneously "Breaks: systemd-shim" and "Depends: systemd-shim |
> systemd-sysv".
> 
> See explainer output below:
> 
> | Reading package lists...
> | Building dependency tree...
> | Reading state information...
> |   MarkInstall sbuild-build-depends-gnupg2-dummy:amd64 < none -> 0.invalid.0 
> @un puN Ib > FU=1
> |   Installing automake as Depends of sbuild-build-depends-gnupg2-dummy
> | MarkInstall automake:amd64 < none -> 1:1.15.1-3.1 @un uN Ib > FU=0
> | Installing autoconf as Depends of automake
> |   MarkInstall autoconf:amd64 < none -> 2.69-11 @un uN Ib > FU=0
> |   Installing m4 as Depends of autoconf
> | MarkInstall m4:amd64 < none -> 1.4.18-1 @un uN Ib > FU=0
> | Installing libsigsegv2 as Depends of m4
> |   MarkInstall libsigsegv2:amd64 < none -> 2.12-2 @un uN > FU=0
> | Installing autotools-dev as Depends of automake
> |   MarkInstall autotools-dev:amd64 < none -> 20180224.1 @un uN > FU=0
> |   Installing autopoint as Depends of sbuild-build-depends-gnupg2-dummy
> | MarkInstall autopoint:amd64 < none -> 0.19.8.1-6 @un uN > FU=0
> |   Installing debhelper as Depends of sbuild-build-depends-gnupg2-dummy
> | MarkInstall debhelper:amd64 < none -> 11.3.5 @un uN Ib > FU=0
> | Installing dh-autoreconf as Depends of debhelper
> |   MarkInstall dh-autoreconf:amd64 < none -> 19 @un uN Ib > FU=0
> |   Installing libtool as Depends of dh-autoreconf
> | MarkInstall libtool:amd64 < none -> 2.4.6-2.1 @un uN Ib > FU=0
> | Installing file as Depends of libtool
> |   MarkInstall file:amd64 < none -> 1:5.33-3 @un uN Ib > FU=0
> |   Installing libmagic1 as Depends of file
> | MarkInstall libmagic1:amd64 < none -> 1:5.33-3 @un uN Ib > FU=0
> | Installing libmagic-mgc as Depends of libmagic1
> |   MarkInstall libmagic-mgc:amd64 < none -> 1:5.33-3 @un uN > 
> FU=0
> | Installing dh-strip-nondeterminism as Depends of debhelper
> |   MarkInstall dh-strip-nondeterminism:amd64 < none -> 0.042-1 @un uN Ib 
> > FU=0
> |   Installing libfile-stripnondeterminism-perl as Depends of 
> dh-strip-nondeterminism
> | MarkInstall libfile-stripnondeterminism-perl:amd64 < none -> 
> 0.042-1 @un uN Ib > FU=0
> | Installing libarchive-zip-perl as Depends of 
> libfile-stripnondeterminism-perl
> |   MarkInstall libarchive-zip-perl:amd64 < none -> 1.60-1 @un uN > 
> FU=0
> |   Installing libtimedate-perl as Depends of dh-strip-nondeterminism
> | MarkInstall libtimedate-perl:amd64 < none -> 2.3000-2 @un uN > FU=0
> | Installing dwz as Depends of debhelper
> |   MarkInstall dwz:amd64 < none -> 0.12-2 @un uN Ib > FU=0
> |   Installing libelf1 as Depends of dwz
> | MarkInstall libelf1:amd64 < none -> 0.170-0.5 @un uN > FU=0
> | Installing man-db as Depends of debhelper
> |   MarkInstall man-db:amd64 < none -> 2.8.3-2 @un uN Ib > FU=0
> |   Installing bsdmainutils as Depends of man-db
> | MarkInstall bsdmainutils:amd64 < none -> 11.1.2+b1 @un uN Ib > FU=0
> | Installing libbsd0 as Depends of bsdmainutils
> |   MarkInstall libbsd0:amd64 < none -> 0.9.1-1 @un uN > FU=0
> |   Installing groff-base as Depends of man-db
> | MarkInstall groff-base:amd64 < none -> 1.22.3-10 @un uN > FU=0
> |   Installing libpipeline1 as Depends of man-db
> | MarkInstall libpipeline1:amd64 < none -> 1.5.0-1 @un uN > FU=0
> | Installing po-debconf as Depends of debhelper
> |   MarkInstall po-debconf:amd64 < none -> 1.0.20 @un uN Ib > FU=0
> |   Installing gettext as Depends of po-debconf
> | MarkInstall gettext:amd64 < none -> 0.19.8.1-6+b1 @un uN Ib > FU=0
> | Installing libcroco3 as Depends of gettext
> |   MarkInstall libcroco3:amd64 < none -> 0.6.12-2 @un uN Ib > FU=0
> |   Installing libglib2.0-0 as Depends of libcroco3
> | MarkInstall libglib2.0-0:amd64 < none -> 2.56.1-2 @un uN > FU=0
> |   Installing libxml2 as Depends of libcroco3
> | MarkInstall libxml2:amd64 < none -> 2.9.4+dfsg1-7+b1 @un uN Ib 
> > FU=0
> | Installing libicu60 as Depends of libxml2
> |   MarkInstall libicu60:amd64 < none -> 60.2-6 @un uN Ib > FU=0
> |   Installing libicu-le-hb0 as Depends of libicu60
> | MarkInstall libicu-le-hb0:amd64 < none -> 1.0.3+git161113-5 
> @un uN Ib > FU=0
> | Installing libharfbuzz0b as Depends of libicu-le-hb0
> |   

Bug#900704: kitty is not available as an alternative for x-terminal-emulator

2018-07-04 Thread Chris Lamb
Hi James,

> Uploaded.

… and processed :-)


Best wishes,

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



Bug#898075: more info

2018-07-04 Thread ant
hello,

  just ran into this today when trying to get cd into
music collection.

  unfortunately i'm too new to python and multiarch to 
make sense of this but perhaps it will help someone else 
figure it out.


me@ant(33)~$ gdb python
GNU gdb (Debian 7.12-6+b2) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from python...Reading symbols from 
/usr/lib/debug/.build-id/ff/383265973a03ce803bda26de44d4a6c82f0db9.debug...done.
done.
(gdb) run /usr/bin/jack
Starting program: /usr/bin/python /usr/bin/jack
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
This is jack 3.1.1 (C)2004 Arne Zellentin 
 "Album - 01 - Tracktitle.[ext]"
 *info* matching dir found: /home/me/music/jack-a707b20c

Program received signal SIGSEGV, Segmentation fault.
__strlen_avx2 () at 
../sysdeps/x86_64/multiarch/strlen-avx2.S:62
62  ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
(gdb) backtrace
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:62
#1  0x72ecf6be in waddnstr ()
   from /lib/x86_64-linux-gnu/libncursesw.so.6
#2  0x73103585 in ?? ()
   from /usr/lib/python2.7/dist-packages/jack_curses.x86_64-linux-gnu.so
#3  0x5564969a in call_function (oparg=, 
pp_stack=0x7fffde30) at ../Python/ceval.c:4372
#4  PyEval_EvalFrameEx () at ../Python/ceval.c:3009
#5  0x5564e3e2 in fast_function (nk=, 
na=, n=2, pp_stack=0x7fffdf40, func=)
at ../Python/ceval.c:4457
#6  call_function (oparg=, pp_stack=0x7fffdf40)
at ../Python/ceval.c:4392
#7  PyEval_EvalFrameEx () at ../Python/ceval.c:3009
#8  0x5564e3e2 in fast_function (nk=, 
na=, n=0, pp_stack=0x7fffe050, func=)
at ../Python/ceval.c:4457
#9  call_function (oparg=, pp_stack=0x7fffe050)
at ../Python/ceval.c:4392
#10 PyEval_EvalFrameEx () at ../Python/ceval.c:3009
#11 0x55646c7a in PyEval_EvalCodeEx () at ../Python/ceval.c:3604
#12 0x5564e7ae in fast_function (nk=0, na=, 
n=, pp_stack=0x7fffe230, func=)
at ../Python/ceval.c:4467
---Type  to continue, or q  to quit---

ant



Bug#897523: fixed in check-postgres 2.24.0-1

2018-07-04 Thread Santiago Vila
found 897523 2.22.0-2
thanks

Dear maintainer: I tried to build this package in
stretch + security + stretch-proposed-updates and it failed with the
same error posted by Lucas Nussbaum.

Please consider an upload for stretch-proposed-updates, as packages in
stretch must be buildable in stretch.

Thanks.



Bug#900704: kitty is not available as an alternative for x-terminal-emulator

2018-07-04 Thread James McCoy
On Wed, Jul 04, 2018 at 06:52:30AM -0400, James McCoy wrote:
> On Wed, Jul 04, 2018 at 09:24:33AM +0100, Chris Lamb wrote:
> > Chris Lamb wrote:
> > 
> > > > Hint taken.. I have processed src:kitty in NEW (alas with a REJECT).
> > >
> > > Do let me know when you have re-uploaded.
> > 
> > Gentle ping on this? :)
> 
> The new upstream released happened a few days ago.  I've been working on
> updating the packaging.  Should be uploaded in the next couple days.

Uploaded.

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



Bug#902290: Too abrupt removal of configuration option in stable update

2018-07-04 Thread Sebastian Andrzej Siewior
control: tags -1 patch

On 2018-07-04 14:06:54 [+0200], To Hans van Kranenburg wrote:
> On 2018-06-24 17:12:19 [+0200], Hans van Kranenburg wrote:
> > My mailserver logs now contain 'ERROR: Parse error at line 74: Unknown
> > option StatsHostID', and when that's removed, it reports the next option
> > that is removed, 'StatsPEDisabled', and so on.
> …
> > Or, alternatively when throwing newer versions in stable, they have to
> > be closely inspected to detect options that are removed and get patches
> > like you did for #826406.
> 
> I'm sorry. I've seen the removal of options and I didn't think about
> this. If handle the config file with debconf then the option should
> vanish automaticaly. However if you edit the file manually then user's
> input is required and if nothing happens then clamav will abort.
> 
> I intend to address this to for deb9 and document this behaviour so I
> will remember it next time. I have to figure out who is in charge of
> deb8 and I *think* it is LTS by now.

so I added a fix [0] to the Stretch branch for this. It would be nice if
you could have a look on the Stretch package in case something else is
missing :)

With this change you should see something like
| Jul 04 22:14:08 deb9amd64 clamd[8720]: WARNING: Ignoring deprecated option 
StatsTimeout at line 88
| Jul 04 22:14:08 deb9amd64 clamd[8720]: WARNING: Ignoring deprecated option 
StatsPEDisabled at line 89

and move on.
Now Jessie. It would be nice if the LTS team could pick it up. On the
other hand the point-release exposed the problem and everyone had to
deal with it…

[0] 
https://salsa.debian.org/clamav-team/clamav/blob/stretch/debian/patches/Deprecate-unused-options-instead-of-removing-it.patch

> > Thanks,

Sebastian



Bug#903002: mc reset confuses ipmievd

2018-07-04 Thread Sergio Gelato
Package: ipmitool
Version: 1.8.18-3

Seen on multiple ProLiant Gen8 servers with iLO firmware v2.54:

if the BMC is reset (e.g. with "ipmitool mc reset warm", or through the 
embedded web server), the running instance of "ipmievd sel [no]daemon" starts 
logging spurious warnings about the SEL buffer being almost full; e.g.:

/usr/sbin/ipmievd sel nodaemon
Reading sensors...
Waiting for events...
No data available
Get SEL Info command failed
Power Supply sensor Power Supplies Redundancy Lost Asserted
Get SEL Entry 5 command failed: Requested sensor, data, or record not found
Power Supply sensor Power Supplies Redundancy Lost Asserted
Power Supply sensor Power Supplies Redundancy Lost Asserted
Power Supply sensor Power Supplies Redundancy Lost Asserted
SEL buffer is 98% full, please consider clearing the SEL buffer
Power Supply sensor Power Supplies Redundancy Lost Asserted
Get SEL Info command failed: Requested sensor, data, or record not found
Get SEL Entry 2 command failed: Requested sensor, data, or record not found

(About the contents of the log entries, for purposes of this bug report it's 
enough to know that ipmievd is in substantial agreement with "ipmitool sel 
list" and with the view from the BMC's embedded web server. Only the "SEL 
buffer is 98% full" alert is clearly spurious; see below.)

At the same time, "ipmitool sel info" reports:

SEL Information
Version  : 1.5 (v1.5, v2 compliant)
Entries  : 6
Free Space   : 928 bytes 
Percent Used : 9%
Last Add Time: 07/04/2018 19:36:40
Last Del Time: 05/27/2017 08:45:32
Overflow : false
Supported Cmds   : 'Reserve' 

How one gets from 9% to 98% is unclear to me. 

Restarting ipmievd restores sanity, but only until the next BMC reset.

Could ipmievd be caching information that is invalidated by the reset?



Bug#903003: soapaligner should be limited to any-amd64 x32

2018-07-04 Thread Adrian Bunk
Source: soapaligner
Version: 2.20-2
Severity: serious

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

soapaligner uses SSE directly, so the architecture list should
be limited to any-amd64 x32 (and an RM bug filed for the SSE3-using
stale i386 package).



Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)

2018-07-04 Thread Evgeny Kapun

Control: severity -1 serious

This bug affects me as well. I was not able to start any VMs because of this 
error. Raising the severity to prevent this from migrating to testing.



Bug#902990: FTBFS: bus error, alignment problems

2018-07-04 Thread Aurelien Jarno
control: forwarded -1 https://github.com/esheldon/fitsio/issues/86

On 2018-07-04 17:48, Steve McIntyre wrote:
> On Wed, Jul 04, 2018 at 04:56:30PM +0100, Steve McIntyre wrote:
> >Source: python-fitsio
> >Version: 0.9.11+dfsg-1
> >Severity: serious
> >Justification: fails to build from source (but built successfully in the 
> >past)
> >
> >Hi!
> >
> >First seen on the build arm-arm-01 which is an arm64 machine
> >configured to build for armhf, build log at
> >
> >https://buildd.debian.org/status/fetch.php?pkg=python-fitsio=armhf=0.9.11%2Bdfsg-1%2Bb2=1530604224=0
> 
> ...
> 
> >The ldrd instruction will be the read from input[ii]. That's clearly
> >unaligned, given the LONGLONG *input which starts at 0x16568df.
> >
> >This doesn't look like an issue with the compiler coalescing unrelated
> >values (which was an initial guess at the problem when discussing it
> >in #debian-buildd). It's simply reading an unaligned 64-bit value and
> >that's failing.
> 
> Just tested this on the 32-bit porter box abel. It builds fine there
> as we have (slow) alignment fixups enabled in the kernel. Disabling
> that briefly and rebuilding, I see exactly the same build failure:
> 
> ...
> I: pybuild base:217: cd 
> /home/93sam/build/python-fitsio/python-fitsio-0.9.11+dfsg/.pybuild/cpython2_2.7_fitsio/build;
>  python2.7 -m unittest discover -v 
> testAsciiTableWriteRead (fitsio.test.TestReadWrite) ... ok
> testBz2Read (fitsio.test.TestReadWrite) ... skipped 'bzip2 is not supported 
> with debian cfitsio package'
> testChecksum (fitsio.test.TestReadWrite) ... Bus error
> E: pybuild pybuild:336: test: plugin distutils failed with: exit code=135: cd 
> /home/93sam/build/python-fitsio/python-fitsio-0.9.11+dfsg/.pybuild/cpython2_2.7_fitsio/build;
>  python2.7 -m unittest discover -v 
> dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
> debian/rules:10: recipe for target 'build' failed
> make: *** [build] Error 25
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This is upstream issue #86. Marking the bug as forwarded.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net



Bug#903001: O: spotweb -- web interface to search and filter Usenet spots

2018-07-04 Thread Jan-Pascal van Best
Package: wnpp
Severity: normal

I intend to orphan the spotweb package. The package in the repository is
severely outdated. Because of many (new) dependencies and because upstream
tends to embrace-and-extend dependencies, updating the packaging to the 
latest upstream will be more work than I can afford to put into this 
package. Spotweb has a low popcon, so it won't be missed by many people.

Thanks

Jan-Pascal


The package description is:
 SpotWeb is a web-based version of the decentralized news-indexing system
 SpotNet, which fetches Usenet "spots" - postings that contain information
 about uploaded binaries. SpotWeb allows searching, filtering, and viewing
 of the spots and comments. It integrates with NZB downloaders such as
 NZBget and SABnzbd+ to download the binaries from Usenet.



Bug#902997: pulseaudio: every other time sound card does not get loaded

2018-07-04 Thread Felipe Sateler
On Wed, Jul 4, 2018 at 2:30 PM Matsievskiy S.V. 
wrote:

> Package: pulseaudio
> Version: 11.1-5
> Severity: normal
>
> Dear Maintainer,
>
> Every other time (sometimes every third time) after shutdown or reboot my
> PCIe
> sound card does not get loaded.
> This began to happen about a week ago. When it happens, kernel modules
> snd_virtuoso, snd_oxygen_lib and snd are loaded; sound card is listed in
> alsamixer, but itpavucontrol configuration tab does not have the card in
> it.
> After the reboot it appears again.
> Additional information about the card is in the attached text file.
>

Is someone holding open the card when the problem occurs? running `lsof
/dev/snd/*` as root should tell you if there are processes holding the
device open.

-- 

Saludos,
Felipe Sateler


Bug#859724: debhelper: please consider using a non-multiarch libexecdir in new compat levels

2018-07-04 Thread Simon McVittie
On Wed, 04 Jul 2018 at 16:13:33 +0200, Michael Biebl wrote:
> Just wondering: What would be the benefit of such a change?

The main thing I wanted was for the default to be *any* non-multiarch
libexecdir, which can solve multiarch co-installability for files like
GNOME thumbnailers, D-Bus services and systemd services, and makes
writing automated tests and manual test instructions more straightforward
because the path to the helper binary doesn't have the varying multiarch
tuple in it:


If we are changing the default libexecdir away from ${libdir}
(which in general is multiarch), then it seems like it makes sense to
use the Autoconf and Meson default, as Niels said he'd prefer in
.
This would also make Debian put these binaries in the same place as
some other distributions (e.g. Red Hat family and Gentoo, although
openSUSE uses libexecdir=/usr/lib and Arch uses
libexecdir=/usr/lib/$package).

> Atm, if I look through my process list, packages seems to pretty much
> consistently use /usr/lib/foo/bar or /lib/foo/bar
> Some even hard-code that to be like that, e.g. systemd has
> 
> rootlibexecdir = join_paths(rootprefixdir, 'lib/systemd')

systemd is a special case because historically it specifically used /lib,
in its role as the root filesystem's equivalent of all of /usr/lib,
/usr/libexec and /usr/share (there is no /libexec or /share).

The FHS doesn't forbid this use of /{usr/,}lib.

> The result will be, that we now have daemons being started from
> /usr/libexec/, /lib/foo/ or /usr/lib/foo/

I don't see that as a big problem tbh. We already have daemons variously
being started from /usr/bin, /usr/lib (in its role as the substitute for
libexec), /usr/sbin, and their root-filesystem equivalents on non-usrmerge
systems.

In a previous mail you said:
> Apparently there are a few packages using pkglibexecdir although I have
> never encountered one myself.

ostree, dovecot, vala and man-db are examples. You
probably didn't notice them because it's difficult to
distinguish between for example (libexecdir=/usr/lib/flatpak,
libexec_PROGRAMS=flatpak-dbus-proxy) and (libexecdir=/usr/lib,
PACKAGE=libostree, pkglibexec_PROGRAMS=ostree-trivial-httpd)
which end up as /usr/lib/flatpak/flatpak-dbus-proxy and
/usr/lib/libostree/ostree-trivial-httpd respectively.

smcv



Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2

2018-07-04 Thread Adrian Bunk
Control: severity -1 important

On Wed, May 02, 2018 at 10:52:53PM +0200, Lucas Nussbaum wrote:
>...
> > volser/vos..FAILED 5
> > bucoord/backup-man..ok
> > kauth/kas-man...ok
> > 
> > Failed Set Fail/Total (%) Skip Stat  Failing Tests
> > -- --    
> > 
> > volser/vos1/6 17%00  5
> > 
> > Failed 1/710 tests, 99.86% okay.
> > Files=23,  Tests=710,  16.66 seconds (1.13 usr + 1.99 sys = 3.12 CPU)
> > make[2]: *** [Makefile:25: check] Error 1
> > make[2]: Leaving directory '/<>/tests'
> > make[1]: *** [Makefile:644: test] Error 2
> > make[1]: Leaving directory '/<>'
> > dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
>  
> The full build log is available from:
>http://aws-logs.debian.net/2018/05/02/openafs_1.8.0-1_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.

The same sources built on the autobuilder 3 days after this bug report
was submitted:
  https://buildd.debian.org/status/logs.php?pkg=openafs=amd64

There might be some problem somewhere, but when it builds on the 
autobuilders it is usually not considered RC.

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#903000: autopkgtest: regression on arch-specific packages with '@' in their test dependencies

2018-07-04 Thread Niko Tyni
Package: autopkgtest
Version: 5.4 
Severity: important

As seen in at least

 https://ci.debian.net/data/autopkgtest/testing/amd64/n/nftables/556352/log.gz

autopkgtest has regressed for packages that are not Architecture: all or
Architecture: any and have '@' in their test dependencies.

This seems to be due to

 
https://salsa.debian.org/ci-team/autopkgtest/commit/7cc976b02a881e5f2a43945fde87d8b8679ff442

which results in an erroneous 'apt-get install package [linux-any]' call.

The code in  _debian_packages_from_source() adds an architecture qualifier
for non-{any,all} packages, so it's not suitable for feeding to 'apt-get
install' as-is.

Fixes / workarounds we've discussed with Paul include

- parse the architecture list, pass the package to 'apt-get install'
  (without the arch qualifier) if and only we're on a matching
  architecture. (The matching check can be done with dpkg-architecture(1)
  but still leaves parsing the specification.)

- don't try to 'apt-get install' non-{any,all} packages; this can result
  in a Provided package satisfying the dependency so the semantics of '@'
  are not guaranteed

- as above, but mitigate the risk of a Provided package satisfying the 
dependency
  by limiting it only to versioned Provides. This could be done by reverting

   
https://salsa.debian.org/ci-team/autopkgtest/commit/9199bbd3dc4ce845f6739dfebee264111c09fdad

-- 
Niko Tyni   nt...@debian.org



Bug#902999: fail with Python3.7: module 'uuid' has no attribute '_uuid_generate_time'

2018-07-04 Thread Vincent Bernat
Package: python3-freezegun
Version: 0.3.9-1
Severity: normal
Tags: upstream patch fixed-upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

With Python 3.7, we get:

 ERROR collecting 
.pybuild/cpython3_3.7_cookiecutter/build/tests/test_default_extensions.py
tests/test_default_extensions.py:7: in 
import freezegun
/usr/lib/python3/dist-packages/freezegun/__init__.py:9: in 
from .api import freeze_time
/usr/lib/python3/dist-packages/freezegun/api.py:23: in 
real_uuid_generate_time = uuid._uuid_generate_time
E   AttributeError: module 'uuid' has no attribute '_uuid_generate_time'


This is fixed upstream in 0.3.10:
 
https://github.com/spulec/freezegun/commit/0836bc6afea5cea3b44dd8023e2116433f5e69f1

Thanks!

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

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

Versions of packages python3-freezegun depends on:
ii  python3   3.6.6-1
ii  python3-dateutil  2.6.1-1
ii  python3-six   1.11.0-2

python3-freezegun recommends no packages.

python3-freezegun suggests no packages.

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAls9FbESHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5yeYP/iBZFKX56a4j3sL250XYF2fBApRq1tsm
P2aecuvWGk5F4JmDyuIR9XYGSY6bycEjzESfK8CDHtNktSzSpBtICvOB6JDuosg1
LgQHMU6R5mqpLp9Itxgjx1LewR3wDUQAWXkrM740FiRDn2I+psRBGXpMPcECu3Be
McQhyPOTW3SUYYizInYcBIpFTCk4n79FcR2v3JA+rdVE3pHislgafSjAnkSd3ETa
2abALewCnJJqMRpZ0vh6MysUys6bqwpFOtYI7Jnqyfg2pldcK26fkgqfbY7TY1sU
03HbWiA3kmsIJMhTTH1MOlTcRy/nQrqevsWLhbRi1oZLWpW3XgE1YqOlI470gPfH
CUg51c5oP8ctPR7ZNn/p09LWsgKk83O5unGwXlBX2GD9UwUu5uZwjaiQNI6/+wz8
4vPfnwYc1ck/m18Ot5FNbLWYR+qDiXvP0dd2+1HDcZG0gszrNG091dCLyDe/Y5CM
yX4hVVgdOSvt1h7orvyWiKY0E4Jsm5C8TOw/b5FQYen2FzMSNM5yZmiGQ4ZrYzLi
QvDcUsZ0WQO4cXg3I9cx7UtE07nfQDRl4J1E66mK75F2+hovFG5BibwSjhYK9tWH
+rl/uzQxH1YBmud35pgntv4ll7n6kMKpmQY8YWiceyhCfeRDvxIn/LbKe+O1vQ2f
wREFFtuAAKlb
=v/Za
-END PGP SIGNATURE-



Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

2018-07-04 Thread Helmut Grohne
Package: libpam-systemd
Version: 239-4
Severity: critical
Justification: makes gnupg2 ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:gnupg2

A native(!) build of gnupg2 with sbuild and
--bd-uninstallable-explainer=apt fails. dose3 finds an installation set,
but it is too tricky to find for apt and it is caused by systemd, which
simultaneously "Breaks: systemd-shim" and "Depends: systemd-shim |
systemd-sysv".

See explainer output below:

| Reading package lists...
| Building dependency tree...
| Reading state information...
|   MarkInstall sbuild-build-depends-gnupg2-dummy:amd64 < none -> 0.invalid.0 
@un puN Ib > FU=1
|   Installing automake as Depends of sbuild-build-depends-gnupg2-dummy
| MarkInstall automake:amd64 < none -> 1:1.15.1-3.1 @un uN Ib > FU=0
| Installing autoconf as Depends of automake
|   MarkInstall autoconf:amd64 < none -> 2.69-11 @un uN Ib > FU=0
|   Installing m4 as Depends of autoconf
| MarkInstall m4:amd64 < none -> 1.4.18-1 @un uN Ib > FU=0
| Installing libsigsegv2 as Depends of m4
|   MarkInstall libsigsegv2:amd64 < none -> 2.12-2 @un uN > FU=0
| Installing autotools-dev as Depends of automake
|   MarkInstall autotools-dev:amd64 < none -> 20180224.1 @un uN > FU=0
|   Installing autopoint as Depends of sbuild-build-depends-gnupg2-dummy
| MarkInstall autopoint:amd64 < none -> 0.19.8.1-6 @un uN > FU=0
|   Installing debhelper as Depends of sbuild-build-depends-gnupg2-dummy
| MarkInstall debhelper:amd64 < none -> 11.3.5 @un uN Ib > FU=0
| Installing dh-autoreconf as Depends of debhelper
|   MarkInstall dh-autoreconf:amd64 < none -> 19 @un uN Ib > FU=0
|   Installing libtool as Depends of dh-autoreconf
| MarkInstall libtool:amd64 < none -> 2.4.6-2.1 @un uN Ib > FU=0
| Installing file as Depends of libtool
|   MarkInstall file:amd64 < none -> 1:5.33-3 @un uN Ib > FU=0
|   Installing libmagic1 as Depends of file
| MarkInstall libmagic1:amd64 < none -> 1:5.33-3 @un uN Ib > FU=0
| Installing libmagic-mgc as Depends of libmagic1
|   MarkInstall libmagic-mgc:amd64 < none -> 1:5.33-3 @un uN > FU=0
| Installing dh-strip-nondeterminism as Depends of debhelper
|   MarkInstall dh-strip-nondeterminism:amd64 < none -> 0.042-1 @un uN Ib > 
FU=0
|   Installing libfile-stripnondeterminism-perl as Depends of 
dh-strip-nondeterminism
| MarkInstall libfile-stripnondeterminism-perl:amd64 < none -> 0.042-1 
@un uN Ib > FU=0
| Installing libarchive-zip-perl as Depends of 
libfile-stripnondeterminism-perl
|   MarkInstall libarchive-zip-perl:amd64 < none -> 1.60-1 @un uN > FU=0
|   Installing libtimedate-perl as Depends of dh-strip-nondeterminism
| MarkInstall libtimedate-perl:amd64 < none -> 2.3000-2 @un uN > FU=0
| Installing dwz as Depends of debhelper
|   MarkInstall dwz:amd64 < none -> 0.12-2 @un uN Ib > FU=0
|   Installing libelf1 as Depends of dwz
| MarkInstall libelf1:amd64 < none -> 0.170-0.5 @un uN > FU=0
| Installing man-db as Depends of debhelper
|   MarkInstall man-db:amd64 < none -> 2.8.3-2 @un uN Ib > FU=0
|   Installing bsdmainutils as Depends of man-db
| MarkInstall bsdmainutils:amd64 < none -> 11.1.2+b1 @un uN Ib > FU=0
| Installing libbsd0 as Depends of bsdmainutils
|   MarkInstall libbsd0:amd64 < none -> 0.9.1-1 @un uN > FU=0
|   Installing groff-base as Depends of man-db
| MarkInstall groff-base:amd64 < none -> 1.22.3-10 @un uN > FU=0
|   Installing libpipeline1 as Depends of man-db
| MarkInstall libpipeline1:amd64 < none -> 1.5.0-1 @un uN > FU=0
| Installing po-debconf as Depends of debhelper
|   MarkInstall po-debconf:amd64 < none -> 1.0.20 @un uN Ib > FU=0
|   Installing gettext as Depends of po-debconf
| MarkInstall gettext:amd64 < none -> 0.19.8.1-6+b1 @un uN Ib > FU=0
| Installing libcroco3 as Depends of gettext
|   MarkInstall libcroco3:amd64 < none -> 0.6.12-2 @un uN Ib > FU=0
|   Installing libglib2.0-0 as Depends of libcroco3
| MarkInstall libglib2.0-0:amd64 < none -> 2.56.1-2 @un uN > FU=0
|   Installing libxml2 as Depends of libcroco3
| MarkInstall libxml2:amd64 < none -> 2.9.4+dfsg1-7+b1 @un uN Ib > 
FU=0
| Installing libicu60 as Depends of libxml2
|   MarkInstall libicu60:amd64 < none -> 60.2-6 @un uN Ib > FU=0
|   Installing libicu-le-hb0 as Depends of libicu60
| MarkInstall libicu-le-hb0:amd64 < none -> 1.0.3+git161113-5 
@un uN Ib > FU=0
| Installing libharfbuzz0b as Depends of libicu-le-hb0
|   MarkInstall libharfbuzz0b:amd64 < none -> 1.8.1-1 @un uN Ib 
> FU=0
|   Installing libfreetype6 as Depends of libharfbuzz0b
| MarkInstall libfreetype6:amd64 < none -> 2.8.1-2 @un uN 
Ib > FU=0
|

Bug#902869: cookiecutter binary: Should depend on python-cookiecutter | python3-cookiecutter

2018-07-04 Thread Vincent Bernat
 ❦  2 juillet 2018 16:36 +0100, Joel Cross  :

> Thanks for building a Python 3 version of this package. However, when
> attempting to install the cookiecutter binary, I noticed it still depends on
> the Python 2 library.
> If memory serves correctly, it is possible to change the 'Depends' line to
> support either Python 2 or Python 3 version of the package, by changing the
> following:
>
> Depends: ... python-cookiecutter (= version) ...
>
> to this:
>
> Depends: ... python-cookiecutter (= version) | python3-cookiecutter (= 
> version)
> ...

The cookiecutter script is using /usr/bin/python2, so it wouldn't work
if only python3-cookiecutter was installed. However, I will switch to
python 3 instead of python 2 for this package.
-- 
Don't diddle code to make it faster - find a better algorithm.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Bug#902229: reassign rather than close?

2018-07-04 Thread Ben Hutchings
On Wed, 2018-07-04 at 14:24 +0200, Nicola Manini wrote:
> Hello,
>   I faced this very same issue today.
> googling this bug report was extremely useful: I deleted timidity, and now
> sound is back.  Obviously this is no solution, as I (or someone else) will
> need timidity eventually.
> 
> I understand this is not a kernel related issue, but it is still a serious
> issue anyway: timidity may grab the sound card at random moments, making
> sound unusable.

The timidity-daemon package does this, and this is intentional and not
a new behaviour.

What changed recently (I think) is that some versions of timidity
recommended timidity-daemon be installed.

> I cannot tell who is actual package (timidity? systemd?) responsible for this
> nor how this can be corrected (maybe insert an extra delay before the
> timidity daemon is started?), but it sure requires a fix.
> 
> So shouldn't this bug be reassigned rather than closed?

Because the bug was already fixed in timidity version 2.14.0-4.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug


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


Bug#902997: pulseaudio: every other time sound card does not get loaded

2018-07-04 Thread Matsievskiy S.V.
Package: pulseaudio
Version: 11.1-5
Severity: normal

Dear Maintainer,

Every other time (sometimes every third time) after shutdown or reboot my PCIe
sound card does not get loaded.
This began to happen about a week ago. When it happens, kernel modules
snd_virtuoso, snd_oxygen_lib and snd are loaded; sound card is listed in
alsamixer, but itpavucontrol configuration tab does not have the card in it.
After the reboot it appears again.
Additional information about the card is in the attached text file.



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


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

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

Versions of packages pulseaudio depends on:
ii  adduser  3.117
ii  libasound2   1.1.6-1
ii  libasound2-plugins   1.1.6-1
ii  libc62.27-3
ii  libcap2  1:2.25-1.2
ii  libdbus-1-3  1.12.8-3
ii  libgcc1  1:8.1.0-9
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2.1
ii  liborc-0.4-0 1:0.4.28-2
ii  libpulse011.1-5
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.28-4
ii  libsoxr0 0.1.2-3
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   8.1.0-9
ii  libsystemd0  238-5
ii  libtdb1  1.3.15-4
ii  libudev1 238-5
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.5-1
ii  libx11-xcb1  2:1.6.5-1
ii  libxcb1  1.13-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20170808
ii  pulseaudio-utils 11.1-5

Versions of packages pulseaudio recommends:
ii  dbus-user-session  1.12.8-3
ii  libpam-systemd 238-5
ii  rtkit  0.11-6

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-4
pn  pavumeter
ii  udev 238-5

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

;autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = 

Bug#902948: drop upstart-mode.el?

2018-07-04 Thread Stig Sandbeck Mathisen
Nicholas D Steeves  writes:

> Stig, as the author of this mode are you interested in maintaining it
> as an upstream?  The Debian Emacsen team is in the process of
> transitioning src:emacs-goodies-el from a native package of bundled
> lisp files to a dummy package that depends on a series of elpafied
> non-native packages with independent upstreams.

The upstream would be in my "elisp" repo at
https://github.com/ssm/elisp/blob/master/upstart-mode.el

If you forsee any theoretical demand for that emacs mode, I'd be happy
to make a separate repo for it, and try to elpafy (what a verb!) it
properly.

-- 
Stig Sandbeck Mathisen
https://localhost/ <- someone's somewhat secret secure self service site



Bug#902996: RM: erlang-fs-listener -- ROM; no longer needed

2018-07-04 Thread Philipp Huebner
Package: ftp.debian.org
Severity: normal

Hi,

please completely remove erlang-fs-listener from the archive, it is no
longer needed by ejabberd, which was the sole reason for introducing it
in the first place.

Best wishes,
Philipp



Bug#902995: RFP: urh -- Universal Radio Hacker: Investigate wireless protocols like a boss

2018-07-04 Thread Johannes Pohl
Package: wnpp
Severity: wishlist

* Package name: urh
  Version : 2.2.2
  Upstream Author : Johannes Pohl 
* URL : https://github.com/jopohl/urh
* License : GPL
  Programming Lang: Python
  Description : Universal Radio Hacker: Investigate wireless protocols like 
a boss

The Universal Radio Hacker (URH) is a software for investigating unknown
wireless protocols. Features include

* hardware interfaces for common Software Defined Radios
* easy demodulation of signals
* assigning participants to keep overview of your data
* customizable decodings to crack even sophisticated encodings like CC1101
* data whitening
* assign labels to reveal the logic of the protocol
* fuzzing component to find security leaks
* modulation support to inject the data back into the system
* simulation environment to perform stateful attacks

URH was already presented at Blackhat Arsenal 2017 and the CCS Workshop
IoTS '17. It will also be featured at the Usenix Workshop WOOT 2018.



Bug#902991: tomcat 7.0.56-3+really7.0.88-* regression

2018-07-04 Thread Markus Koschany
Hello,

Am 04.07.2018 um 17:54 schrieb Sébastien QUESSON:
[...]
> Caused by:
> javax.servlet.ServletException: java.lang.NoClassDefFoundError: 
> org/apache/tomcat/util/buf/UriUtil
> ...
> Caused by:
> java.lang.NoClassDefFoundError: org/apache/tomcat/util/buf/UriUtil
> at 
> org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:316)

UriUtil is a new class and can be found in
/usr/share/tomcat7/lib/tomcat-coyote.jar. I assume this jar file is not
on your classpath. Looking at the source package of jetty8, I only see
that we symlink some tomcat jars into /usr/share/jetty8/lib/jsp/.

Provided you have libjetty8-extra-java already installed, what happens
when you symlink tomcat-coyote.jar into /usr/share/jetty8/lib/jsp/ ?

Regards,

Markus



signature.asc
Description: OpenPGP digital signature


Bug#901919: nvidia-driver: black screen with the latest Linux kernel

2018-07-04 Thread Andreas Beckmann
On 2018-07-04 01:54, Andreas Beckmann wrote:
> On 2018-07-04 01:30, Andreas Beckmann wrote:
>> I've prepared that in the 390 branch - could you give it a test run
>> (with all workarounds disabled)?
> 
> patch is not backwards compatible to older kernels:

I think I fixed that. I also tried to backport the patch to the 340xx
series. The 390/340 modules build for all kernels that I have in my kmod
testbuild chroot, but I cannot test any of them.


Andreas



Bug#901868: Some clarifications on tvb-* packages

2018-07-04 Thread Lia Domide
Hi,

I am Lia Domide, one of the core developers in TVB Project.
Umar has recently joined the team, as part of Google Summer of Code (GSOC 2018) 
and his task is to package TVB for NeuroDebian, thus he initiated this work 
with you.
I will try to add some details to the questions raised on these threads.

The packages we want to publish now are 4:
- tvb-gdist 
is similar with other geodesic packages. But at the time of our 
implementation, this was the only one working on meshes with areas both concave 
and convex, and easy to access for us from Python.
- tvb-data
contains demo data for TVB demos and tests
- tvb-library
this depends on tvb-gdist and tvb-data
holds the core scientific code for TVB, mainly our simulator. It can be 
used in the python command line without the next package tvb-framework.
is unique by the fact that it does full brain simulations, modeled at a 
macroscopic level, considering delays in signal propagation
- tvb-framework
depends on tvb-library, adds web GUI, DB storage and a simple workflow 
configurator
it includes a full cherrypy based web server structure. Thus, it 
contains minified versions of MatJax, D3, JQuery and Flot libraries. 
We refer their licenses only here: 
https://www.thevirtualbrain.org/tvb/zwei/brainsimulator-requirements 
. Should 
they licenses be better emphasized?

These 4 packages have their sources on Github under GPLv3 license: 
https://github.com/the-virtual-brain 
We packed them for Pypi https://pypi.org/user/tvb/ 
and Conta Forge https://conda-forge.org/feedstocks/ 
 (filter after “tvb”)
We also pack TVB_Distribution 
https://www.thevirtualbrain.org/tvb/zwei/brainsimulator-software 
 which 
includes Python, TVB and all dependencies in a ready to use package.

We would like, if possible, the same structures as on Pypi to be available for 
Debian, with as little as possible changes.
It is important, if our packages are published on your repo, that multiple 
people have rights to maintain them (me included). How can we easily ensure 
that?


Best Regards,


Ing. <> Lia Domide
Director of Development at Codemart
Str. Petofi Sandor, Nr. 13, Ap. 4
Cluj Napoca, 400610, Romania
Tel: +40 (364) 401158
   +40 (744) 580134
Web:  <>http://www.codemart.ro 


Bug#902989: python3-pyatspi: fresh installation breaks

2018-07-04 Thread Paul Gevers
Control: block -1 by 902788

Hi Wolfgang,

On 04-07-18 16:47, Wolfgang Schweer wrote:
> Setting up python3-pyatspi (2.26.0+dfsg-1) ...
>   File "/usr/lib/python3/dist-packages/pyatspi/registry.py", line 114
> self.async = False# not fully supported yet
>  ^
> SyntaxError: invalid syntax

Thanks for reporting this. This is caused by the python3.7 transition.

Paul



signature.asc
Description: OpenPGP digital signature


Bug#900324: [Pkg-tigervnc-devel] Bug#900324: mouse buttons not working in fullscreen mode

2018-07-04 Thread Harald Dunkel
Hi Ola,

On 6/22/18 9:04 PM, Ola Lundqvist wrote:
> Hi
> 
> Thank you for your report. Does it work if you exit full screen mode?
> 

I cannot exit full screen mode, because the popup menu is inaccessible.
It is just a white rectangle.


Regards
Harri



Bug#900324: [Pkg-tigervnc-devel] Bug#900324: mouse buttons not working in fullscreen mode

2018-07-04 Thread Harald Dunkel
PS: In window mode the popup menu works.



Bug#901134: marked as done (RFS: anbox-modules/0.0~git20180608-1 [ITP])

2018-07-04 Thread Geert Stappers
On Wed, Jul 04, 2018 at 05:33:06AM +, Debian Bug Tracking System wrote:
> Your message dated Wed, 4 Jul 2018 13:28:25 +0800
> with message-id 
> 
> and subject line Android modules are built as in-tree modules since kernel 
> 4.17.3
> has caused the Debian Bug report #901134,
> regarding RFS: anbox-modules/0.0~git20180608-1 [ITP]
> to be marked as done.
> 
> 901134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901134
>
> Date: Sat, 9 Jun 2018 17:49:58 +0800
> From: Shengjing Zhu 
> To: Debian Bug Tracking System 
> Subject: RFS: anbox-modules/0.0~git20180608-1 [ITP]
> User-Agent: Mutt/1.10.0 (2018-05-17)
> 
> Package: sponsorship-requests
> Severity: wishlist
> X-Debbugs-CC: Chris Lamb 
> 
> Dear mentors,
> 
>   I am looking for a sponsor for package "anbox-modules"
> 
>  * Package name: anbox-modules
>Upstream Author : Simon Fels 
>  * URL : https://github.com/anbox/anbox-modules/
>  * License : GPL-2
>Section : kernel
> 
>   It builds those binary packages:
> 
> anbox-modules-dkms - Android kernel driver (binder, ashmem) in DKMS format
> 
> Date: Wed, 4 Jul 2018 13:28:25 +0800
> From: Shengjing Zhu 
> To: 901130-d...@bugs.debian.org, 901134-d...@bugs.debian.org
> Subject: Android modules are built as in-tree modules since kernel 4.17.3
> 
> Android modules are built as in-tree modules since kernel 4.17.3

Nice


> Please see  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901492
> Hence, I'm closing these two bugs.

Thanks for doing so.


Groeten
Geert Stappers
-- 
Leven en laten leven



Bug#861027: gprolog bug still there despite easy fixes

2018-07-04 Thread Cedric Ware

Hello,

I don't think anything changed with this bug, which still prevents
gprolog's inclusion in any stable release, and affects Ubuntu as well.

I believe just pulling the latest upstream source would fix it.

Alternatively, if downgrading to the stable gprolog-1.4.4 is an option,
the attached patch lets it compile with gcc 6.  Tested on Debian 9.4.

Thanks in advance,
Cedric Ware.
diff -ru gprolog-1.4.4.orig/src/Ma2Asm/x86_64_any.c gprolog-1.4.4/src/Ma2Asm/x86_64_any.c
--- gprolog-1.4.4.orig/src/Ma2Asm/x86_64_any.c	2013-04-22 13:52:16.0 +0200
+++ gprolog-1.4.4/src/Ma2Asm/x86_64_any.c	2018-05-10 16:31:10.534235899 +0200
@@ -204,8 +204,8 @@
   strcpy(asm_reg_cp, Off_Reg_Bank(MAP_OFFSET_CP));
 #endif
 
-#ifdef M_x86_64_darwin
-  pic_code = 1;			/* NB: on darwin everything is PIC code */
+#if defined(M_x86_64_darwin) || defined(M_x86_64_bsd) || defined(M_x86_64_linux)
+  pic_code = 1;			/* NB: on darwin and BSD everything is PIC code, last gcc 6 needs this for linux */
 #elif defined(_WIN32)
   pic_code = 0;			/* NB: on MinGW nothing is needed for PIC code */
 #endif


Bug#902994: New upstream release

2018-07-04 Thread Laurent Bigonville
Source: nutsqlite
Version: 1.9.9.6-1
Severity: wishlist

Hi,

There is a new release of nutsqlite with the followin changes:

2018-06-22 NUTsqlite-2.0.4 released.

2018-06-22 Found a bug in RecipeDone.  100 gram weight record was wrong.

2018-06-17 NUTsqlite-2.0.3 released.

2018-06-17 Load of USDA database is leaving a carriage return and tilde at the
   end of each food group.  Fixed in proc load_fd_group.  Also updated
   GUI to show correct percentages of carbs and fat in new Daily Values.

2018-06-10 NUTsqlite-2.0.2 released.

2018-06-10 Windows 10 user "Darwin" found some code in proc FoodChoicevf which
   which doesn't work right on his operating system.  It's a thread
   problem in conjunction with the tcl/sqlite interface.

2018-06-07 NUTsqlite-2.0.1 released.

2018-06-07 Procedure which clears the weight log was not updated to match
   bigNUT, so I fixed ClearWeightLog.

2018-05-30 NUTsqlite-2.0 released.

2018-05-30 It looks and acts pretty much the same, but it's a new program made
   up of snippets of the old program stitched together in a new way.
   bigNUT is the back-end, the GUI is threaded, and the performance is
   superb.  All computations and logic are now done by SQLite rather
   than Tcl.  bigNUT uses triggers to keep all the data for the display
   up-to-date, so that Tcl only translates user commands into SQL and
   then retrieves all relevant data to refresh the GUI as necessary.

Apparently it's completely rewritten from scratch, might be inresting to
update

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.16.0-2-amd64 (SMP w/4 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

Versions of packages nutsqlite depends on:
ii  libsqlite3-tcl  3.24.0-1
ii  tk  8.6.0+9

nutsqlite recommends no packages.

nutsqlite suggests no packages.

-- no debconf information



Bug#725821: ITA: swapspace -- dynamic swap space manager

2018-07-04 Thread Jacob Adams
control: retitle -1 ITA: swapspace -- dynamic swap space manager
control: owner -1 !

I'd like to take another shot at maintaining this package.

Thanks,
Jacob



signature.asc
Description: OpenPGP digital signature


Bug#902990: FTBFS: bus error, alignment problems

2018-07-04 Thread Steve McIntyre
On Wed, Jul 04, 2018 at 04:56:30PM +0100, Steve McIntyre wrote:
>Source: python-fitsio
>Version: 0.9.11+dfsg-1
>Severity: serious
>Justification: fails to build from source (but built successfully in the past)
>
>Hi!
>
>First seen on the build arm-arm-01 which is an arm64 machine
>configured to build for armhf, build log at
>
>https://buildd.debian.org/status/fetch.php?pkg=python-fitsio=armhf=0.9.11%2Bdfsg-1%2Bb2=1530604224=0

...

>The ldrd instruction will be the read from input[ii]. That's clearly
>unaligned, given the LONGLONG *input which starts at 0x16568df.
>
>This doesn't look like an issue with the compiler coalescing unrelated
>values (which was an initial guess at the problem when discussing it
>in #debian-buildd). It's simply reading an unaligned 64-bit value and
>that's failing.

Just tested this on the 32-bit porter box abel. It builds fine there
as we have (slow) alignment fixups enabled in the kernel. Disabling
that briefly and rebuilding, I see exactly the same build failure:

...
I: pybuild base:217: cd 
/home/93sam/build/python-fitsio/python-fitsio-0.9.11+dfsg/.pybuild/cpython2_2.7_fitsio/build;
 python2.7 -m unittest discover -v 
testAsciiTableWriteRead (fitsio.test.TestReadWrite) ... ok
testBz2Read (fitsio.test.TestReadWrite) ... skipped 'bzip2 is not supported 
with debian cfitsio package'
testChecksum (fitsio.test.TestReadWrite) ... Bus error
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=135: cd 
/home/93sam/build/python-fitsio/python-fitsio-0.9.11+dfsg/.pybuild/cpython2_2.7_fitsio/build;
 python2.7 -m unittest discover -v 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Who needs computer imagery when you've got Brian Blessed?



Bug#902941: libuv1/1.21.0-1 appears to break lua-luv/1.9.1-0-2 autopkgtest

2018-07-04 Thread Felipe Sateler
Control: retitle -1 libuv1 1.21 broke ABI without SONAME bump
Control: severity -1 serious
Control: affects -1 nodejs

Hi,

On Wed, 04 Jul 2018 13:14:23 +0200 Dominique Dumont  wrote:
> On Tue, 3 Jul 2018 19:46:30 +0200 Paul Gevers  wrote:
> > ok 9 fs - fs.scandir
> >   ./tests/test-fs.lua:83: UNKNOWN FS TYPE 29
>
> Looks like this issue has been fixed in upstream lua:
>
>
https://github.com/luvit/luv/commit/853546063c88f0f06b680844b8a2c90dc13343d3

Lua had a bug, but the change was done incorrectly in libuv. The numbering
of enum values changed between 1.20 and 1.21, thus any binary compiled for
1.20 can be subtly broken by upgrading to 1.21.

In particular, the lchown uv_fs_type was not added at the end[1]. This
breaks ABI and should require a transition.

See also the abi tracker report:
https://abi-laboratory.pro/index.php?view=compat_report=libuv=1.20.3=1.21.0=121f9=abi

This affects nodejs too.

[1]
https://salsa.debian.org/debian/libuv1/commit/aa28f7d5bf36b4df1e606ed47364d91d896b1f8b#1b6daa9127cce1f350074cef165b370bd83dfdcb_1144_1144

Saludos


Bug#899324: ruby-font-awesome-rails: broken with fonts-font-awesome 5

2018-07-04 Thread Pirate Praveen
On Tue, 22 May 2018 16:49:12 -0300 Antonio Terceiro
 wrote:
> My suggestion would be to:
> 
> - base the CSS template on
>   /usr/share/fonts-font-awesome/css/font-awesome.css which is a modified
>   version of the FontAwesome v5 stylesheet adding backwards
>   compatibility for usage of FontAwesome v4.
> - symlink /usr/share/ruby-font-awesome-rails/app/assets/fonts/ directly
>   to /usr/share/fonts-font-awesome/webfonts instead of symlinking
>   individual files (and probably rename the link from fonts to webfonts)

The consensus on fonts-font-awesome bug seems to be a +really upload

There is already an open mr
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899124#164

So once that is uploaded, we can close this bug.



signature.asc
Description: OpenPGP digital signature


Bug#902993: linux-image-4.16.0-2-amd64: Please compile with MOUSE_PS2_SYNAPTICS_SMBUS and RMI4_SMB options

2018-07-04 Thread Zlatko Čalušić
Package: src:linux
Version: 4.16.16-2
Severity: normal

Please compile kernel image with MOUSE_PS2_SYNAPTICS_SMBUS and RMI4_SMB options 
enabled.

psmouse serio1: synaptics: The touchpad can support a better bus than the too 
old PS/2 protocol. Make sure MOUSE_PS2_SYNAPTICS_SMBUS and RMI4_SMB are enabled 
to get a better touchpad experience.
psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 
0xf004a3/0x943300/0x12e800/0x1, board id: 3053, fw id: 2560
psmouse serio1: synaptics: serio: Synaptics pass-through port at 
isa0060/serio1/input0

Thanks!

-- Package-specific info:
** Version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-2 (2018-06-22)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.16.0-2-amd64 
root=UUID=76703dcf-fd76-4b85-aea2-af96cd3b13f9 ro noresume net.ifnames=0 
profile=2 swapaccount=1 vsyscall=emulate snd-hda-intel.probe_mask=2 
modprobe.blacklist=snd_pcsp

** Not tainted

** Kernel log:
[4.654994] snd_hda_codec_realtek hdaudioC1D0:  Dock Mic=0x19
[4.656688] snd_hda_codec_realtek hdaudioC1D0:  Mic=0x1a
[4.656770] media: Linux media interface: v0.10
[4.658600] snd_hda_codec_realtek hdaudioC1D0:  Internal Mic=0x12
[4.666748] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[4.669272] cdc_acm 2-4:1.3: ttyACM1: USB ACM device
[4.672957] cdc_wdm 2-4:1.5: cdc-wdm1: USB WDM device
[4.675593] cdc_acm 2-4:1.9: ttyACM2: USB ACM device
[4.679215] Intel(R) Wireless WiFi driver for Linux
[4.679826] usbcore: registered new interface driver cdc_acm
[4.681119] Copyright(c) 2003- 2015 Intel Corporation
[4.685444] cdc_acm: USB Abstract Control Model driver for USB modems and 
ISDN adapters
[4.688264] Linux video capture interface: v2.00
[4.690678] Bluetooth: Core ver 2.22
[4.691511] cdc_wdm 2-4:1.8: cdc-wdm2: USB WDM device
[4.692688] NET: Registered protocol family 31
[4.693024] iwlwifi :03:00.0: firmware: direct-loading firmware 
iwlwifi-7265D-29.ucode
[4.693322] iwlwifi :03:00.0: loaded firmware version 29.541020.0 
op_mode iwlmvm
[4.695567] usbcore: registered new interface driver cdc_wdm
[4.696342] Bluetooth: HCI device and connection manager initialized
[4.698114] Bluetooth: HCI socket layer initialized
[4.723761] Bluetooth: L2CAP socket layer initialized
[4.725831] Bluetooth: SCO socket layer initialized
[4.726576] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card1/input12
[4.729446] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms 
ovfl timer
[4.729481] input: HDA Intel PCH Dock Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input13
[4.731341] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[4.731342] RAPL PMU: hw unit of domain package 2^-14 Joules
[4.731343] RAPL PMU: hw unit of domain dram 2^-14 Joules
[4.731344] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[4.739223] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input14
[4.743087] input: HDA Intel PCH Dock Headphone as 
/devices/pci:00/:00:1b.0/sound/card1/input15
[4.745264] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card1/input16
[4.766567] usbcore: registered new interface driver btusb
[4.780989] cdc_ncm 2-4:1.6: MAC-Address: 02:15:e0:ec:01:00
[4.783279] iwlwifi :03:00.0: Detected Intel(R) Dual Band Wireless AC 
7265, REV=0x210
[4.784614] cdc_ncm 2-4:1.6 wwan0: register 'cdc_ncm' at usb-:00:14.0-4, 
Mobile Broadband Network Device, 02:15:e0:ec:01:00
[4.787463] Bluetooth: hci0: read Intel version: 370810011003110e00
[4.788723] usbcore: registered new interface driver cdc_ncm
[4.789694] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[4.793248] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[4.799138] usbcore: registered new interface driver cdc_mbim
[4.802984] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b449)
[4.808734] uvcvideo 2-8:1.0: Entity type for entity Extension 4 was not 
initialized!
[4.810151] iwlwifi :03:00.0: base HW address: 18:5e:0f:16:df:55
[4.86] uvcvideo 2-8:1.0: Entity type for entity Processing 2 was not 
initialized!
[4.817476] uvcvideo 2-8:1.0: Entity type for entity Camera 1 was not 
initialized!
[4.820969] input: Integrated Camera: Integrated C as 
/devices/pci:00/:00:14.0/usb2/2-8/2-8:1.0/input/input17
[4.823357] usbcore: registered new interface driver uvcvideo
[4.825423] USB Video Class driver (1.1.1)
[4.844997] iTCO_vendor_support: vendor-support=0
[4.849888] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[4.851945] iTCO_wdt: Found a Wildcat Point_LP TCO device (Version=2, 
TCOBASE=0x1860)
[4.852038] intel_rapl: Found RAPL domain package
[4.854228] 

Bug#902992: live-build broken due subversion recommends

2018-07-04 Thread PICCORO McKAY Lenz
Package: live-build
Version: 1:20171207
Severity: grave

we need a mechanish to avoid bad or abuse of recommends in apt, this
problem avoit the automatization of the process

if we list the package subversion-tools, that recomends exim4 over any
other, take preference to a specific package

root@pc-desk-w32:/vnx/osposos/debianlive8# aptitude why exim4
i   subversion-tools Recomienda exim4 | mail-transport-agent

so then process end with this:

The following packages have unmet dependencies:
 courier-mta : Conflicts: mail-transport-agent
 exim4-config : Conflicts: courier-mta but 0.76.3-5 is to be installed
 exim4-daemon-light : Conflicts: mail-transport-agent

and lb build fails, with a only solution to make interactive shell and
avoiting automatization of the process

we need the mechanish due we cannot track all packages that abuse or
are bad mantained due policy violations!

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com



Bug#902991: tomcat 7.0.56-3+really7.0.88-* regression

2018-07-04 Thread Sébastien QUESSON
Package: libtomcat7-java
Version: 7.0.56-3+really7.0.88-1

7.0.56-3+really7.0.88-1 and 7.0.56-3+really7.0.88-2 makes some web application 
to crash.
We use jasig CAS webapp with a jetty8 daemon. When we try to start jetty8:

2018-07-04 11:48:53.785:INFO:cas:Warning: No org.apache.tomcat.JarScanner set 
in ServletContext. Falling back to default JarScanner implementation.
2018-07-04 11:48:53.790:WARN:oejs.ServletHandler:
org.springframework.web.util.NestedServletException: Request processing failed; 
nested exception is 
org.springframework.webflow.execution.FlowExecutionException: Exception thrown 
in state 'viewLoginForm' of flow 'login'
...
Caused by:
org.springframework.webflow.execution.FlowExecutionException: Exception thrown 
in state 'viewLoginForm' of flow 'login'
...
Caused by:
java.lang.IllegalStateException: Exception occurred rendering view 
org.springframework.web.servlet.view.JstlView: name 'casLoginView'; URL 
[/WEB-INF/view/jsp/default/ui/casLoginView.jsp]
...
Caused by:
javax.servlet.ServletException: java.lang.NoClassDefFoundError: 
org/apache/tomcat/util/buf/UriUtil
...
Caused by:
java.lang.NoClassDefFoundError: org/apache/tomcat/util/buf/UriUtil
at 
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:316)



So we downgraded libtomcat7-java to 7.0.56-3+deb8u11, and jetty8 can start:

2018-07-04 13:25:45.392:INFO:cas:Warning: No org.apache.tomcat.JarScanner set 
in ServletContext. Falling back to default JarScanner implementation.
juil. 04, 2018 1:25:45 PM org.apache.jasper.compiler.TldLocationsCache 
tldScanJar
INFOS: At least one JAR was scanned for TLDs yet contained no TLDs. Enable 
debug logging for this logger for a complete list of JARs that were scanned but 
no TLDs were found in them. Skipping unneeded JARs during scanning can improve 
startup time and JSP compilation time.
juil. 04, 2018 1:25:45 PM org.apache.tomcat.util.scan.StandardJarScanner scan


I checked changelogs, but could'nt identify why 
org/apache/tomcat/util/buf/UriUtil cannot be found. Any ideas?


Best regards,

Sébastien QUESSON 



Bug#902990: FTBFS: bus error, alignment problems

2018-07-04 Thread Steve McIntyre
Source: python-fitsio
Version: 0.9.11+dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!

First seen on the build arm-arm-01 which is an arm64 machine
configured to build for armhf, build log at

https://buildd.debian.org/status/fetch.php?pkg=python-fitsio=armhf=0.9.11%2Bdfsg-1%2Bb2=1530604224=0

I can similarly reproduce this on other arm64 hardware. Backtrace
shows:

(gdb) bt
#0  ffi8fi8 (input=input@entry=0x16568df, ntodo=ntodo@entry=1, scale=1, zero=0, 
output=output@entry=0xfff3d1a0, status=status@entry=0xfff44384) at 
putcolj.c:1871
#1  0xf6cc5a8a in ffpcljj (fptr=0x15d3660, colnum=8, firstrow=, 
firstelem=1, nelem=1, array=0x16568df, status=0xfff44384) at putcolj.c:1428
#2  0xf6cc5c3c in ffpcljj (fptr=, colnum=, 
firstrow=, firstelem=firstelem@entry=1, nelem=nelem@entry=1, 
array=array@entry=0x16568df, 
status=status@entry=0xfff44384) at putcolj.c:1538
#3  0xf6cbc2b4 in ffpcl (fptr=, datatype=, 
colnum=, firstrow=1, firstelem=1, nelem=1, array=0x16568df, 
status=0xfff44384) at putcol.c:701
#4  0xf6e02a26 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) p input
$2 = (LONGLONG *) 0x16568df

Disassembly of the problem area gives:

   0xf6cc54ce <+206>:   ldr.w   r0, [r10]
   0xf6cc54d2 <+210>:   ldmia.w sp!, {r4, r5, r6, r7, r8, r10, r11, pc}
   0xf6cc54d6 <+214>:   cmp r1, #0
   0xf6cc54d8 <+216>:   ble.n   0xf6cc54ca 
   0xf6cc54da <+218>:   subsr2, #8
   0xf6cc54dc <+220>:   add.w   r1, r0, r1, lsl #3
=> 0xf6cc54e0 <+224>:   ldrdr4, r5, [r0], #8
   0xf6cc54e4 <+228>:   cmp r1, r0
   0xf6cc54e6 <+230>:   strdr4, r5, [r2, #8]!
   0xf6cc54ea <+234>:   bne.n   0xf6cc54e0 
   0xf6cc54ec <+236>:   vpop{d8-d12}
   0xf6cc54f0 <+240>:   ldr.w   r0, [r10]

The offending ldrd instruction here clearly matches up with the
source, which is the simple-case loop in ffi8fi8():

if (scale == 1. && zero == 0.)
{   
for (ii = 0; ii < ntodo; ii++)
output[ii] = input[ii];
}

The ldrd instruction will be the read from input[ii]. That's clearly
unaligned, given the LONGLONG *input which starts at 0x16568df.

This doesn't look like an issue with the compiler coalescing unrelated
values (which was an initial guess at the problem when discussing it
in #debian-buildd). It's simply reading an unaligned 64-bit value and
that's failing.

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

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



Bug#816297: must not prefer mexim4 due break live-build user preferences

2018-07-04 Thread PICCORO McKAY Lenz
i have brtoken live buil due this package preferes exim4 over the
mail-transport-agentand must not


root@pc-desk-w32:/vnx/osposos/debianlive8# aptitude why exim4
i   subversion-tools Recomienda exim4 | mail-transport-agent


Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com


Bug#890483: bind9: compile with dnstap support

2018-07-04 Thread Axel Beckert
Hi,

just my two cents:

Richard James Salts wrote:
> It would be nice to enable the dnstap functionality included in bind
> 9.11 for detailed logging of dns queries going throught bind.

Yes, please enable dnstap in Debian's bind9 packages.

Additionally I'd be happy to see the tool dnstap-read from the bind9
sources being available in the bind9utils package in Debian (as would
be if Richard's patch would be applied).

> It would pull in extra dependencies on libfstrm0, libprotobuf-c1 and
> zlib1g, however this might be worth it.

It is definitely worth it.



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


signature.asc
Description: Digital signature


Bug#902513: openturns: FTBFS in buster/sid (nlopt.hpp: No such file or directory)

2018-07-04 Thread D. Barbier
fixed 902513 openturns/1.11-2
stop

On 2018-06-27 14:50 GMT+02:00 Santiago Vila wrote:
> Package: src:openturns
> Version: 1.10-5
> Severity: serious
> Tags: ftbfs
[...]
> /<>/lib/src/Base/Optim/NLopt.cxx:27:11: fatal error: nlopt.hpp: 
> No such file or directory
>  # include 
>^~~
> compilation terminated.
> lib/src/CMakeFiles/OT.dir/build.make:3302: recipe for target 
> 'lib/src/CMakeFiles/OT.dir/Base/Optim/NLopt.cxx.o' failed
> make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Optim/NLopt.cxx.o] Error 1

Hello,

This bug is already fixed in experimental, but I have to fix FTBFS on
several architectures before uploading to unstable.

Denis



Bug#898310: [Pkg-pascal-devel] Bug#898310: lcl-units-1.8 unusable due to file permissions

2018-07-04 Thread Alexander Kernozhitsky
Sorry, the previous patch caused build failure, here is the correct version.

-- 
-
Alexander Kernozhitskydiff -rU3 lazarus-1.8.4+dfsg.orig/debian/lcl-gtk2.install.in lazarus-1.8.4+dfsg/debian/lcl-gtk2.install.in
--- lazarus-1.8.4+dfsg.orig/debian/lcl-gtk2.install.in	2017-06-09 16:04:43.0 +0300
+++ lazarus-1.8.4+dfsg/debian/lcl-gtk2.install.in	2018-07-04 17:49:01.478017232 +0300
@@ -1,4 +1,5 @@
 /usr/lib/lazarus/${VERSION}/components/ideintf/units/*/gtk2
+/usr/lib/lazarus/${VERSION}/components/lazcontrols/design/lib/*/gtk2
 /usr/lib/lazarus/${VERSION}/components/lazcontrols/lib/*/gtk2
 /usr/lib/lazarus/${VERSION}/components/synedit/design/units/*/gtk2
 /usr/lib/lazarus/${VERSION}/components/synedit/units/*/gtk2
diff -rU3 lazarus-1.8.4+dfsg.orig/debian/lcl-qt5.install.in lazarus-1.8.4+dfsg/debian/lcl-qt5.install.in
--- lazarus-1.8.4+dfsg/debian/lcl-qt5.install.in	2017-10-21 08:22:18.0 +0300
+++ lazarus-1.8.4+dfsg/debian/lcl-qt5.install.in	2018-07-04 17:49:14.798023605 +0300
@@ -1,5 +1,6 @@
 #! /usr/bin/dh-exec
 /usr/lib/lazarus/${VERSION}/components/ideintf/units/*/qt5 [!linux-mips !linux-mipsel]
+/usr/lib/lazarus/${VERSION}/components/lazcontrols/design/lib/*/qt5 [!linux-mips !linux-mipsel]
 /usr/lib/lazarus/${VERSION}/components/lazcontrols/lib/*/qt5 [!linux-mips !linux-mipsel]
 /usr/lib/lazarus/${VERSION}/components/synedit/design/units/*/qt5 [!linux-mips !linux-mipsel]
 /usr/lib/lazarus/${VERSION}/components/synedit/units/*/qt5 [!linux-mips !linux-mipsel]
diff -rU3 lazarus-1.8.4+dfsg.orig/debian/rules lazarus-1.8.4+dfsg/debian/rules
--- lazarus-1.8.4+dfsg/debian/rules	2018-05-24 10:30:04.0 +0300
+++ lazarus-1.8.4+dfsg/debian/rules	2018-07-04 18:08:37.759414210 +0300
@@ -212,11 +212,11 @@
 	find -name debian -prune -or '(' -name lib -or -name units ')' -print | xargs ${CP} --parents -t ${LIB_DIR}
 	# Remove READM.txt files from output directories
 	find ${LIB_DIR} '(' -name '*.or' -or -wholename '*/lib/README.txt' ')' -delete
-	# Mark package as manually compilable and install them
+	# Install packages
 	for package in `find -name '*.lpk'` ; \
 	do \
 		${MKDIR} `dirname "${LIB_DIR}/$${package}"` ; \
-		sed -e 's@\(\W*\).*@\1\n&@' "$${package}" > "${LIB_DIR}/$${package}" ; \
+		cp "$${package}" "${LIB_DIR}/$${package}" ; \
 	done
 	# Install packages global links
 	${CP} -t ${LIB_DIR}/packager $(CURDIR)/packager/globallinks


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

2018-07-04 Thread Lars Wirzenius
On Wed, Sep 06, 2017 at 12:31:19AM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch'.
> It installed fine in 'stretch', then the upgrade to 'buster' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

While it's true there's a bug, and I will fix that, I do not
understand why piuparts is installing python3-cliapp. That doesn't
seem like an obvious thing to do. The python3 version of the package
did not exist in stretch, and upgrading the python2 version from
stretch to buster seems to work just fine: I just tested that manually
in a chroot.

From the piuparts log I see that it is explicitly installing the
python3 version after upgrading to buster.

(Also, the advice to use Replaces+Breaks is just wrong for this
package. The bug is that the same file is in both the python2 and
python3 versions of the package. The correct solution is to have it in
at most one package. I will be making that fix eventually.)

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature


Bug#884797: ITP: anbox -- Run Android applications on any GNU/Linux operating system

2018-07-04 Thread Shengjing Zhu
Hi Chris,

On Wed, Jul 4, 2018 at 10:54 PM Chris Lamb  wrote:
>   Uploading anbox_0.0~git20180612-1.dsc
>   Uploading anbox_0.0~git20180612.orig.tar.gz
>   Uploading anbox_0.0~git20180612-1.debian.tar.xz
>   Uploading anbox-dbgsym_0.0~git20180612-1_amd64.deb
>   Uploading anbox_0.0~git20180612-1_amd64.buildinfo
>   Uploading anbox_0.0~git20180612-1_amd64.deb
>   Uploading anbox_0.0~git20180612-1_amd64.changes
>
>   $ echo $?
>   0
>

Thanks, it hits NEW now.

--
Best regards,
Shengjing Zhu



Bug#855320: developers-reference: Please do not recommend debrsign

2018-07-04 Thread Ian Jackson
dgit rpush ought to work fairly well for the stuations where debrsign
might be used, and does not have this ssh trust reversal problem.

(It still operates rather as a signing oracle but the signing oracle
is much more restricted.)

Ian.

-- 
Ian JacksonThese opinions are my own.

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



Bug#902965: xserver-xorg-core: lxdm fails to start xserver with 2:1.20.0-3

2018-07-04 Thread Michel Dänzer
On 2018-07-04 04:39 PM, Arthur Marsh wrote:
> 
> radeon: Failed to deallocate virtual address for buffer:
> radeon:size  : 8355840 bytes
> radeon:va: 0x10090

Looks like maybe you're running into https://bugs.freedesktop.org/105381
. In which case it's not specific to 2:1.20.0-3, you're just lucky when
not hitting this issue with any Xorg 1.20.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer



Bug#898310: [Pkg-pascal-devel] Bug#898310: lcl-units-1.8 unusable due to file permissions

2018-07-04 Thread Alexander Kernozhitsky
By the way, here is the patch (also fixes the related bug #896702)

-
Alexander Kernozhitskydiff -rU3 lazarus-1.8.4+dfsg.orig/debian/lcl-gtk2.install.in lazarus-1.8.4+dfsg/debian/lcl-gtk2.install.in
--- lazarus-1.8.4+dfsg.orig/debian/lcl-gtk2.install.in	2017-06-09 16:04:43.0 +0300
+++ lazarus-1.8.4+dfsg/debian/lcl-gtk2.install.in	2018-07-04 17:49:01.478017232 +0300
@@ -1,4 +1,5 @@
 /usr/lib/lazarus/${VERSION}/components/ideintf/units/*/gtk2
+/usr/lib/lazarus/${VERSION}/components/lazcontrols/design/lib/*/gtk2
 /usr/lib/lazarus/${VERSION}/components/lazcontrols/lib/*/gtk2
 /usr/lib/lazarus/${VERSION}/components/synedit/design/units/*/gtk2
 /usr/lib/lazarus/${VERSION}/components/synedit/units/*/gtk2
diff -rU3 lazarus-1.8.4+dfsg.orig/debian/lcl-qt5.install.in lazarus-1.8.4+dfsg/debian/lcl-qt5.install.in
--- lazarus-1.8.4+dfsg/debian/lcl-qt5.install.in	2017-10-21 08:22:18.0 +0300
+++ lazarus-1.8.4+dfsg/debian/lcl-qt5.install.in	2018-07-04 17:49:14.798023605 +0300
@@ -1,5 +1,6 @@
 #! /usr/bin/dh-exec
 /usr/lib/lazarus/${VERSION}/components/ideintf/units/*/qt5 [!linux-mips !linux-mipsel]
+/usr/lib/lazarus/${VERSION}/components/lazcontrols/design/lib/*/qt5 [!linux-mips !linux-mipsel]
 /usr/lib/lazarus/${VERSION}/components/lazcontrols/lib/*/qt5 [!linux-mips !linux-mipsel]
 /usr/lib/lazarus/${VERSION}/components/synedit/design/units/*/qt5 [!linux-mips !linux-mipsel]
 /usr/lib/lazarus/${VERSION}/components/synedit/units/*/qt5 [!linux-mips !linux-mipsel]
diff -rU3 lazarus-1.8.4+dfsg.orig/debian/rules lazarus-1.8.4+dfsg/debian/rules
--- lazarus-1.8.4+dfsg/debian/rules	2018-05-24 10:30:04.0 +0300
+++ lazarus-1.8.4+dfsg/debian/rules	2018-07-04 17:48:48.202010921 +0300
@@ -212,12 +212,6 @@
 	find -name debian -prune -or '(' -name lib -or -name units ')' -print | xargs ${CP} --parents -t ${LIB_DIR}
 	# Remove READM.txt files from output directories
 	find ${LIB_DIR} '(' -name '*.or' -or -wholename '*/lib/README.txt' ')' -delete
-	# Mark package as manually compilable and install them
-	for package in `find -name '*.lpk'` ; \
-	do \
-		${MKDIR} `dirname "${LIB_DIR}/$${package}"` ; \
-		sed -e 's@\(\W*\).*@\1\n&@' "$${package}" > "${LIB_DIR}/$${package}" ; \
-	done
 	# Install packages global links
 	${CP} -t ${LIB_DIR}/packager $(CURDIR)/packager/globallinks
 	# copy icons and menu entries for the GNOME menu


Bug#884797: ITP: anbox -- Run Android applications on any GNU/Linux operating system

2018-07-04 Thread Chris Lamb
Hi Shengjing,

> Sorry, previous I run `dcut ftp-master rm -f 'anbox_0.0~git20180612*',

No problem :)

  Uploading anbox_0.0~git20180612-1.dsc
  Uploading anbox_0.0~git20180612.orig.tar.gz
  Uploading anbox_0.0~git20180612-1.debian.tar.xz
  Uploading anbox-dbgsym_0.0~git20180612-1_amd64.deb
  Uploading anbox_0.0~git20180612-1_amd64.buildinfo
  Uploading anbox_0.0~git20180612-1_amd64.deb
  Uploading anbox_0.0~git20180612-1_amd64.changes

  $ echo $?
  0

\o/


Regards,

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



Bug#834607: lintian: /usr/lib/ vs /usr/libexec

2018-07-04 Thread Chris Lamb
tags 834607 + pending
thanks

Fixed in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/a4de10f70370a1fe7f7d6ff22d76f80173626917

  checks/files.pm| 4 +++-
  debian/changelog   | 2 ++
  t/tests/files-foo-in-bar/debian/debian/install | 1 +
  3 files changed, 6 insertions(+), 1 deletion(-)


Regards,

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



Bug#902989: python3-pyatspi: fresh installation breaks

2018-07-04 Thread Wolfgang Schweer
Package:  python3-pyatspi
Version:  2.26.0+dfsg-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: debian-edu


Dear Maintainer,

when running 'apt --reinstall install python3-pyatspi' on a system 
running buster/sid the installation breaks. 
This is the error output when running 'LC_ALL=C apt -f install':

Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up python3-pyatspi (2.26.0+dfsg-1) ...
  File "/usr/lib/python3/dist-packages/pyatspi/registry.py", line 114
self.async = False  # not fully supported yet
 ^
SyntaxError: invalid syntax

dpkg: error processing package python3-pyatspi (--configure):
 installed python3-pyatspi package post-installation script subprocess 
returned error exit status 1
Errors were encountered while processing:
 python3-pyatspi
E: Sub-process /usr/bin/dpkg returned an error code (1)

I noticed this problem in the first place when searching for reasons why
the src:debian-edu autopkgtest is failing; see:
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/debian-edu/556605/log.gz

Due to this bug, both GNOME and MATE desktop installations seem to be 
broken.

Wolfgang


signature.asc
Description: PGP signature


Bug#884797: ITP: anbox -- Run Android applications on any GNU/Linux operating system

2018-07-04 Thread Shengjing Zhu
Hi Chris,

On Wed, Jul 4, 2018 at 8:55 PM Chris Lamb  wrote:
> Failed to upload anbox-dbgsym_0.0~git20180612-1_amd64.deb to 
> la...@ssh.upload.debian.org:/srv/upload.debian.org/UploadQueue/anbox-dbgsym_0.0~git20180612-1_amd64.deb:
>  scp: 
> /srv/upload.debian.org/UploadQueue/anbox-dbgsym_0.0~git20180612-1_amd64.deb: 
> Permission denied

Sorry, previous I run `dcut ftp-master rm -f 'anbox_0.0~git20180612*',
so anbox-dbgsym_0.0~git20180612-1_amd64.deb is not deleted.
I re-sent with `dcut ftp-master rm -f 'anbox*'

> Log of processing your commands file /zsj-1530715180.commands:
>
> > rm anbox*
> Files removed: anbox_0.0~git20180612-1.debian.tar.xz 
> anbox_0.0~git20180612-1.dsc anbox-dbgsym_0.0~git20180612-1_amd64.deb > 
> anbox_0.0~git20180612.orig.tar.gz

All problem files should be deleted now.

Please upload again, thanks!

--
Best regards,
Shengjing Zhu



  1   2   >