date:20180417

Package: testng
Version: 6.9.12-2
Severity: important

Dear Maintainer,

while trying to use testng to update package htsjdk (using gradle),
I face errors about jcommander not being found when running tests

Task :compileTestJava actions class loader hash:
1526b3b109d06b230b32697697c7e0ca
Passing through org.scala-lang:scala-library:jar:2.11.x
Passing through com.google.jimfs:jimfs:jar:debian
Passing through com.google.jimfs:jimfs-parent:jar:debian
Passing through org.testng:testng:jar:debian
Passing through com.google.guava:guava:jar:debian
Passing through com.google.guava:guava-parent:jar:debian
Passing through org.beanshell:bsh:jar:debian
Passing through com.beust:jcommander:jar:1.x
POM relocation to an other version number is not fully supported in Gradle
: com.beust:jcommander:1.x relocated to com.beust:jcommander:debian.
Please update your dependency to directly use the correct version
'com.beust:jcommander:debian'.
Resolution will only pick dependencies of the relocated element.  Artifacts
and other metadata will be ignored.
...
Caused by: java.lang.NoClassDefFoundError:
com/beust/jcommander/ParameterException
at
org.gradle.api.internal.tasks.testing.testng.TestNGTestClassProcessor.runTests(TestNGTestClassProcessor.java:95)
at
org.gradle.api.internal.tasks.testing.testng.TestNGTestClassProcessor.stop(TestNGTestClassProcessor.java:88)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:61)

I see in gradle logs that jcommander is not added in the classpath, so
there may be a dependency management issue with jcommander.

It seems there are resolution issues I did not face in the past.
Don't know if issue is testng or jcommander related as I see jcommander was
updated not so long ago.


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

Kernel: Linux 4.4.0-116-generic (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages testng depends on:
ii  libbsh-java 2.0b4-19
ii  libjcommander-java  1.71-1

Versions of packages testng recommends:
ii  ant 1.10.3-1
ii  junit4  4.12-6
ii  libyaml-snake-java  1.20-1

testng suggests no packages.

-- no debconf information

Bug#895887: jessie-pu: package libipc-run-perl/0.92-1+deb8u1

2018-04-17 Thread Paul Wise

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

libipc-run-perl 0.92-1 has a memory leak that causes some code at $work
to use all of the RAM on the machine. We would like to fix it in jessie
using the patch accepted upstream and released into sid and buster.
We have tested the patches internally and they resolve our issue.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
diff -Nru libipc-run-perl-0.92/debian/changelog libipc-run-perl-0.92/debian/changelog
--- libipc-run-perl-0.92/debian/changelog	2012-09-01 01:21:38.0 +0800
+++ libipc-run-perl-0.92/debian/changelog	2018-04-17 16:16:38.0 +0800
@@ -1,3 +1,9 @@
+libipc-run-perl (0.92-1+deb8u1) jessie; urgency=medium
+
+  * Backport upstream patch to fix memory leak
+
+ -- Paul Wise   Tue, 17 Apr 2018 16:16:38 +0800
+
 libipc-run-perl (0.92-1) unstable; urgency=low
 
   [ gregor herrmann ]
diff -Nru libipc-run-perl-0.92/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch libipc-run-perl-0.92/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch
--- libipc-run-perl-0.92/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch	1970-01-01 08:00:00.0 +0800
+++ libipc-run-perl-0.92/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch	2018-04-17 16:16:38.0 +0800
@@ -0,0 +1,31 @@
+From 5cd3a5b21bd00dbb2e54e58fec6b0349bf457bb0 Mon Sep 17 00:00:00 2001
+From: Konrad Bucheli 
+Date: Tue, 27 Mar 2018 11:22:58 +0200
+Subject: [PATCH] Another Bugfix for memory leak [rt.cpan.org #57990] #86
+Origin: https://github.com/kbucheli/IPC-Run/commit/d706e65d0e5dab055d9b6c8d070330fdc7b1a883
+Bug: https://github.com/toddr/IPC-Run/issues/86
+
+---
+ lib/IPC/Run.pm | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/lib/IPC/Run.pm b/lib/IPC/Run.pm
+index 2436bc5..61cdb5f 100644
+--- a/lib/IPC/Run.pm
 b/lib/IPC/Run.pm
+@@ -1135,6 +1135,12 @@ sub DESTROY {
+my IPC::Run $self = shift;
+POSIX::close $self->{DEBUG_FD} if defined $self->{DEBUG_FD};
+$self->{DEBUG_FD} = undef;
++
++   for my $kid ( @{$self->{KIDS}} ) {
++   for my $op ( @{$kid->{OPS}} ) {
++   delete $op->{FILTERS};
++   }
++   }
+ }
+ 
+ ##
+-- 
+2.17.0
+
diff -Nru libipc-run-perl-0.92/debian/patches/series libipc-run-perl-0.92/debian/patches/series
--- libipc-run-perl-0.92/debian/patches/series	2012-09-01 01:21:38.0 +0800
+++ libipc-run-perl-0.92/debian/patches/series	2018-04-17 16:08:26.0 +0800
@@ -1 +1,2 @@
 hashbang.patch
+0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch


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

Bug#895888: stretch-pu: package libipc-run-perl/0.94-1+deb9u1

2018-04-17 Thread Paul Wise

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

libipc-run-perl 0.94-1 has a memory leak that causes some code at $work
to use all of the RAM on the machine. We would like to fix it in jessie
using the patch accepted upstream and released into sid and buster.
We have tested the patches internally and they resolve our issue.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
diff -Nru libipc-run-perl-0.94/debian/changelog libipc-run-perl-0.94/debian/changelog
--- libipc-run-perl-0.94/debian/changelog	2015-05-10 23:05:50.0 +0800
+++ libipc-run-perl-0.94/debian/changelog	2018-04-17 16:24:46.0 +0800
@@ -1,3 +1,9 @@
+libipc-run-perl (0.94-1+deb9u1) stretch; urgency=medium
+
+  * Backport upstream patch to fix memory leak
+
+ -- Paul Wise   Tue, 17 Apr 2018 16:24:46 +0800
+
 libipc-run-perl (0.94-1) unstable; urgency=low
 
   [ Salvatore Bonaccorso ]
diff -Nru libipc-run-perl-0.94/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch libipc-run-perl-0.94/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch
--- libipc-run-perl-0.94/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch	1970-01-01 08:00:00.0 +0800
+++ libipc-run-perl-0.94/debian/patches/0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch	2018-04-17 16:24:10.0 +0800
@@ -0,0 +1,31 @@
+From 5cd3a5b21bd00dbb2e54e58fec6b0349bf457bb0 Mon Sep 17 00:00:00 2001
+From: Konrad Bucheli 
+Date: Tue, 27 Mar 2018 11:22:58 +0200
+Subject: [PATCH] Another Bugfix for memory leak [rt.cpan.org #57990] #86
+Origin: https://github.com/kbucheli/IPC-Run/commit/d706e65d0e5dab055d9b6c8d070330fdc7b1a883
+Bug: https://github.com/toddr/IPC-Run/issues/86
+
+---
+ lib/IPC/Run.pm | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/lib/IPC/Run.pm b/lib/IPC/Run.pm
+index 2436bc5..61cdb5f 100644
+--- a/lib/IPC/Run.pm
 b/lib/IPC/Run.pm
+@@ -1135,6 +1135,12 @@ sub DESTROY {
+my IPC::Run $self = shift;
+POSIX::close $self->{DEBUG_FD} if defined $self->{DEBUG_FD};
+$self->{DEBUG_FD} = undef;
++
++   for my $kid ( @{$self->{KIDS}} ) {
++   for my $op ( @{$kid->{OPS}} ) {
++   delete $op->{FILTERS};
++   }
++   }
+ }
+ 
+ ##
+-- 
+2.17.0
+
diff -Nru libipc-run-perl-0.94/debian/patches/series libipc-run-perl-0.94/debian/patches/series
--- libipc-run-perl-0.94/debian/patches/series	2015-05-10 23:05:50.0 +0800
+++ libipc-run-perl-0.94/debian/patches/series	2018-04-17 16:24:20.0 +0800
@@ -1 +1,2 @@
 hashbang.patch
+0001-Another-Bugfix-for-memory-leak-rt.cpan.org-57990-86.patch


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

Bug#851827: scim-qt-immodule seems to be not working with Qt5 apps

2018-04-17 Thread Rolf Leggewie

Package: scim
Version: 1.4.18-1
Followup-For: Bug #851827

Artem,

thank you for your report.  Unfortunately, scim does not yet support Qt5.

You can follow upstream discussion at https://github.com/scim-im/scim/issues/21

I'm sorry, I don't have better news at this point in time.

Regards

Rolf

Bug#894015: Bug #894015 in gitlab marked as pending

2018-04-17 Thread Pirate Praveen


On Tuesday 17 April 2018 02:02 PM, Dmitry Smirnov wrote:

Technically speaking Gitaly may be running from another server therefore
recommends should be sufficient.


ok.


Besides Gitaly works well with bundled grpc. I did some work on Gitaly so it
should be (almost) ready for upload...


Thanks.

Bug#895208: gnumeric: missing build dependency on libxml2-utils

2018-04-17 Thread Dmitry Smirnov

On Monday, 16 April 2018 4:30:43 PM AEST Andreas Tille wrote:
> I'd volunteer to NMU this package but it seems it also needs migration
> to Salsa.  Since I usually like to push my changes to Git I'd like to
> ask for permission to do the Salsa migration for gnumeric.  I'll assume
> that you agree to this if I do not hear from you soon.

I would appreciate any help with migration to Salsa. Please go ahead with NMU 
as well if you feel it is urgent. I'm planning to spend some time on Gnumeric 
hopefully this weekend...

-- 
Regards,
 Dmitry Smirnov.

---

The surest way to corrupt a youth is to instruct him to hold in higher
esteem those who think alike than those who think differently.
-- Friedrich Nietzsche

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

Bug#895889: golang-github-weaveworks-mesh: new version causes regression in prometheus-alertmanager

2018-04-17 Thread Paul Gevers

Source: golang-github-weaveworks-mesh
Version: 0.1+git20180323.0c91e69-1
Severity: serious
User: debian...@lists.debian.org
Usertags: triggers
Affects: prometheus-alertmanager

Since the upload of golang-github-weaveworks-mesh version
0.1+git20180323.0c91e69-1, the autopkgtest of prometheus-alertmanager¹
fails with the errors copied below.

As the it seems that the same code is used to build the
prometheus-alertmanager package, I think this means that that now FTBFS
(haven't verified). If you believe this was exaggerated or the issue is
really in prometheus-alertmanager, please don't hesitate to lower it
accordingly and/or reassign to prometheus-alertmanager.

I suggest the maintainers of golang-github-weaveworks-mesh and
prometheus-alertmanager discuss how this issue should be solved (hence
the CC).

Paul

¹ https://ci.debian.net/packages/p/prometheus-alertmanager

dh_auto_build: cd build && go install
-gcflags=\"-trimpath=/tmp/autopkgtest-lxc.6nk_tdek/downtmp/autopkgtest_tmp/build/src\"
-asmflags=\"-trimpath=/tmp/autopkgtest-lxc.6nk_tdek/downtmp/autopkgtest_tmp/build/src\"
-v -p 2 -ldflags " -X
github.com/prometheus/common/version.Version=0.6.2+ds -X
github.com/prometheus/common/version.Revision=0.6.2+ds-5 -X
github.com/prometheus/common/version.Branch=debian/sid -X
github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
-X github.com/prometheus/common/version.BuildDate=20180327-00:03:07 -X
github.com/prometheus/common/version.GoVersion=go1.10rc2"
github.com/prometheus/alertmanager/api
github.com/prometheus/alertmanager/artifacts
github.com/prometheus/alertmanager/cli
github.com/prometheus/alertmanager/cli/format
github.com/prometheus/alertmanager/cmd/alertmanager
github.com/prometheus/alertmanager/cmd/amtool
github.com/prometheus/alertmanager/config
github.com/prometheus/alertmanager/dispatch
github.com/prometheus/alertmanager/examples/webhook
github.com/prometheus/alertmanager/inhibit
github.com/prometheus/alertmanager/nflog
github.com/prometheus/alertmanager/nflog/nflogpb
github.com/prometheus/alertmanager/notify
github.com/prometheus/alertmanager/pkg/parse
github.com/prometheus/alertmanager/provider
github.com/prometheus/alertmanager/provider/mem
github.com/prometheus/alertmanager/silence
github.com/prometheus/alertmanager/silence/silencepb
github.com/prometheus/alertmanager/template
github.com/prometheus/alertmanager/template/internal/deftmpl
github.com/prometheus/alertmanager/test
github.com/prometheus/alertmanager/types
github.com/prometheus/alertmanager/ui returned exit code 2
debian/rules:51: recipe for target 'override_dh_auto_build' failed
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.6nk_tdek/downtmp/autopkgtest_tmp'
make[1]: *** [override_dh_auto_build] Error 2
debian/rules:31: recipe for target 'build' failed
make: *** [build] Error 2



signature.asc
Description: OpenPGP digital signature

Bug#895855: debian-handbook: apt-key add should not be used

2018-04-17 Thread Raphael Hertzog

Control: reassign -1 harden-doc

On Tue, 17 Apr 2018, sergio wrote:
> man APT-KEY(8) on stretch for the "add" command says
> 
> "Note: Instead of using this command a keyring should be placed directly
> in the /etc/apt/trusted.gpg.d/ directory with a descriptive name and
> either "gpg" or "asc" as file extension."
> 
> but "The Debian Administrator's Handbook" and
> https://www.debian.org/doc/manuals/securing-debian-howto/ch7
> still say to use apt-key add.

This is not part of the Debian Administrator's Handbook. I'm reassigning
to the correct package. The stretch version of my book (not yet released)
already contains wording recommending the use of a drop-in file
instead of calling "apt-key add".

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#895849: sphinxcontrib-autoprogram: Incompatible with Sphinx 1.7

Hi,

On Mon, Apr 16, 2018 at 09:48:28PM +0200, Bas Couwenberg wrote:
> Source: sphinxcontrib-autoprogram
> Version: 0.1.2-1

I applied the suggested patch to version 0.1.4 since I wanted to upload
this version anyway.  However, when trying to build the package in Git[1]
I get a test suite failure:

...
test_make_rst (sphinxcontrib.autoprogram.AutoprogramDirectiveTestCase)
Alt least it shouldn't raise errors during making RST string. ... ERROR
test_import_object (sphinxcontrib.autoprogram.UtilTestCase) ... ok

==
ERROR: test_make_rst (sphinxcontrib.autoprogram.AutoprogramDirectiveTestCase)
Alt least it shouldn't raise errors during making RST string.
--
Traceback (most recent call last):
  File "/build/sphinxcontrib-autoprogram-0.1.4/sphinxcontrib/autoprogram.py", 
line 398, in test_make_rst
list(self.directive.make_rst())
  File "/build/sphinxcontrib-autoprogram-0.1.4/sphinxcontrib/autoprogram.py", 
line 162, in make_rst
parser = import_object(import_name or '__undefined__')
  File "/build/sphinxcontrib-autoprogram-0.1.4/sphinxcontrib/autoprogram.py", 
line 139, in import_object
raise ImportError("No module named {}".format(module_name))
ImportError: No module named cli

--
Ran 6 tests in 0.003s

FAILED (errors=1)
Test failed: 
error: Test failed: 
...

I can confirm that there is no such module cli.  Before I report the
issue upstream I'd like to ask for confirmation that it is not just me
overlooking something.

Thanks for any help

  Andreas.

[1] https://salsa.debian.org/med-team/sphinxcontrib-autoprogram

-- 
http://fam-tille.de

Bug#873397: radio: input frequency uses floating point, causing rounding errors

2018-04-17 Thread Maximiliano Curia


¡Hola Ben!

El 2017-08-27 a las 06:21 -0700, Ben Wong escribió:

Package: radio
Version: 3.103-3+b1
Severity: normal
Tags: patch



Dear Maintainer,



  To replicate: Run 'radio -f 107.7'
Expected result: Frequency should be 107.7.
 Actual result: Frequency is 107.69.



The 'radio' program uses floating point when reading in the frequency
from the user. (E.g. "107.7"). However, the frequency actually set are
usually wrong due to floating point rounding.



The fix is to read the input as a string and manipulate it as
characters. I've included a patch which does exactly that.


Sorry that it took me so long to reply your email.

You are reporting an upstream issue, and it seems to me that it would be 
better if you send this kind of patches upstream directly. You can contact 
upstream through the linux-media mailing list: linux-me...@vger.kernel.org


Although the project is no longer in active development the still accept 
patches/fixes.


Happy hacking,
--
"People get lost in thought because it is unfamiliar territory."
-- Fix's Principle
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#895849: sphinxcontrib-autoprogram: Incompatible with Sphinx 1.7

2018-04-17 Thread Bas Couwenberg


On 2018-04-17 11:25, Andreas Tille wrote:

On Mon, Apr 16, 2018 at 09:48:28PM +0200, Bas Couwenberg wrote:

Source: sphinxcontrib-autoprogram
Version: 0.1.2-1


I applied the suggested patch to version 0.1.4 since I wanted to upload
this version anyway.  However, when trying to build the package in 
Git[1]

I get a test suite failure:


The changes from the PR in question were already included in 0.1.4, and 
subsequently changed in later commits in that release.


 
https://github.com/sphinx-contrib/autoprogram/commit/2debd1489c5a576a8f33b27e847077b860319916


Try building just 0.1.4 without the patch.

Kind Regards,

Bas

Bug#873402: Radio: frequency can get reset to preset #1 on startup

2018-04-17 Thread Maximiliano Curia


¡Hola Ben!

El 2017-08-27 a las 06:59 -0700, Ben Wong escribió:

Package: radio
Version: 3.103-3+b1
Severity: normal
Tags: patch



Dear Maintainer,



The radio program incorrectly changes the frequency on startup under
certain circumstances because it does not correctly calculate the band.



To recreate:



1. Create a file called "~/.radio" with contents like this:



   [Buttons]
   1= 8955
   2= 9035



2. Tune in a frequency that is not one of the presets.
  For example, 'radio -f 94.9'  (then 'q' to quit)



3. Run 'radio' again and note that the frequency gets changed to the
  first preset.



(Note: This bug doesn't occur if the radio is set to a frequency that
is one of the presets).



The problem is that the radio program converts the current frequency
to a band by looking at frequencies that are listed in the presets. It
ought to look at the frequency ranges of the available bands.



I have included a patch which does that.


Sorry that it took me so long to reply your email.

You are reporting an upstream issue, and it seems to me that it would be 
better if you send this kind of patches upstream directly. You can contact 
upstream through the linux-media mailing list: linux-me...@vger.kernel.org


Although the project is no longer in active development the still accept 
patches/fixes.


Happy hacking,
--
"Seek simplicity, and distrust it." -- Whitehead's Rule
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#895855: debian-handbook: apt-key add should not be used

2018-04-17 Thread sergio


On 17/04/18 12:21, Raphael Hertzog wrote:


This is not part of the Debian Administrator's Handbook. I'm reassigning
to the correct package.


https://www.debian.org/doc/manuals/debian-handbook/sect.package-authentication.en.html

Would you say this link also is not a part of debian-handbook?


--
sergio.

Bug#892394: [pkg-boost-devel] Bug#892394: boost1.63: build-depends on GCC 6

2018-04-17 Thread Marc Glisse


Dimitri John Ledkov:


boost1.65 has been rejected by ftp-masters, on copyright reasons.


Hello,

could you include a reference to the corresponding discussion, please? I 
didn't manage to find it on the debian mailing lists. The only potentially 
relevant thing I found is a discussion in February on the boost mailing 
list about one stackoverflow snippet, but it does not mention debian at 
all and seems too small a reason to reject the library.


--
Marc Glisse

Bug#893039: libccnet0: contains a python module

2018-04-17 Thread Moritz Schlarb

Hi Helmut,

I addressed this issue in 6.1.5-2, but since this leads to a new binary
upload, I can't upload it myself since I'm just a DM.
My mentor/sponsor Christoph is currently out of the office, so he can't
do it either.
So I've uploaded it to https://mentors.debian.net/package/ccnet - maybe
you are willing to perform the upload for me (If that went through, I'm
gonna upload the new upstream version myself).

Best regards,
Moritz



signature.asc
Description: OpenPGP digital signature

Bug#891504: tracker.debian.org: emails sent to 'team+slug@tracker.d.o' are trashed

2018-04-17 Thread Chris Lamb

Hi Mattia,

> emails sent to 'team+slug@tracker.d.o' are trashed

Can you clarify what "are trashed" means here? They are sent to
"spam", or are lost, or..?


Best wishes,

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

Bug#895890: pandas: FTBFS on mips and powerpc: test_unstack_odd_failure crashes

2018-04-17 Thread Graham Inggs


Source: pandas
Version: 0.22.0-2
Severity: serious

Hi Science Team

Since the upload of 0.22.0-2, pandas has FTBFS on mips and powerpc with 
errors similar to the following:


../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/test_multilevel.py::TestMultiLevel::test_unstack_odd_failure 
realloc(): invalid next size

Aborted
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":99"

make[1]: *** [debian/rules:127: python-test2.7] Error 134
make[1]: Leaving directory '/<>'

The errors I have found in the build logs are:
realloc(): invalid next size
malloc(): smallbin double linked list corrupted
Segmentation fault
corrupted double-linked list

Pandas 0.22.0-1 failed for an unrelated reason.
The test_unstack_odd_failure did not fail with any of the 0.20.3-* 
uploads (it either passed, or the build failed for other reasons).


I'm marking this serious as the failure on mips prevents the migration 
of pandas to testing.


Regards
Graham

Bug#895849: sphinxcontrib-autoprogram: Incompatible with Sphinx 1.7

> 
> The changes from the PR in question were already included in 0.1.4, and
> subsequently changed in later commits in that release.
> 
> https://github.com/sphinx-contrib/autoprogram/commit/2debd1489c5a576a8f33b27e847077b860319916
> 
> Try building just 0.1.4 without the patch.

This is what I did some days ago.  The patch is not the issue for the
build failure.  I removed the patch from git again - any help is
welcome. 

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#895891: ITP: golang-github-vimeo-go-magic -- Go bindings for libmagic

2018-04-17 Thread Sascha Steinbiss

Package: wnpp
Severity: wishlist
Owner: Sascha Steinbiss 

* Package name: golang-github-vimeo-go-magic
  Version : 0.0~git20180208.aff138d-1
  Upstream Author : Vimeo, LLC.
* URL : https://github.com/vimeo/go-magic
* License : BSD-2-clause
  Programming Lang: Go
  Description : Go bindings for libmagic

Go-magic is a Golang library that wraps libmagic and provides API functions
for file type detection. it also provides an API for getting a file's MIME
type using libmagic.

Bug#891504: tracker.debian.org: emails sent to 'team+slug@tracker.d.o' are trashed

2018-04-17 Thread Mattia Rizzolo

On Tue, Apr 17, 2018 at 11:13:08AM +0100, Chris Lamb wrote:
> Hi Mattia,
> 
> > emails sent to 'team+slug@tracker.d.o' are trashed
> 
> Can you clarify what "are trashed" means here? They are sent to
> "spam", or are lost, or..?

"discarded" is probably the correct word.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#895889: golang-github-weaveworks-mesh: new version causes regression in prometheus-alertmanager

2018-04-17 Thread Adrian Bunk

On Tue, Apr 17, 2018 at 11:20:13AM +0200, Paul Gevers wrote:
>...
> As the it seems that the same code is used to build the
> prometheus-alertmanager package, I think this means that that now FTBFS
> (haven't verified).
>...

prometheus-alertmanager does FTBFS now:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus-alertmanager.html

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#895893: gqrx-sdr crashes with segfault

2018-04-17 Thread Hans-J. Ullrich

Package: gqrx-sdr
Version: 2.9-2
Severity: important

Dear Maintainer,

I discovered, that gqrx in debian/testing is crashing with segfault. To find 
the reason, I 
tried to downgrade to gqrx of debian/stable as well as gqrx of debin/unstable.

Please note: All versions do crash with segfault! 

So I believe, that a library, which belongs to gqrx might cause the problem. 
The strange thing is, that gqrx 2.6 (from stable) was running well, and also 
the version from testing was running well for a longer time.

Of course on this system during the time things have changed, i.e. now I am 
running kernel 4.15-XXX and all libs are now in the state of debian/testing.

I also googled the internet and saw lots of "gqrx segfault" discussions within 
Ubuntu 16.04 and 17.04, but there were no real results. Some people pointed to 
libboost, but I tried also the versions from stable (which ran fine in the 
past), but got segfault again.

Another hint was the sound backend in the windowmanager. As I am running 
pulseaudio, I tried vlc-backend and pulseaudio-backend, with no success.

Starting with strace showed me no unusual output. Just segfault. If needed, I 
can send it later.

And last but not least, I purged everything related to gqrx (libs and 
config-files) with no success, too.

Now I am stuck, but maybe someone knows more.

Thanks for looking at and reading this.

Best regards

Hans



Still believe, that there is a  

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

Kernel: Linux 4.15.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 gqrx-sdr depends on:
ii  libboost-program-options1.62.0  1.62.0+dfsg-5
ii  libboost-system1.62.0   1.62.0+dfsg-5
ii  libc6   2.27-3
ii  libgcc1 1:8-20180402-1
ii  libgnuradio-analog3.7.113.7.11-8
ii  libgnuradio-audio3.7.11 3.7.11-8
ii  libgnuradio-blocks3.7.113.7.11-8
ii  libgnuradio-digital3.7.11   3.7.11-8
ii  libgnuradio-fft3.7.11   3.7.11-8
ii  libgnuradio-filter3.7.113.7.11-8
ii  libgnuradio-osmosdr0.1.40.1.4-14+b2
ii  libgnuradio-pmt3.7.11   3.7.11-8
ii  libgnuradio-runtime3.7.11   3.7.11-8
ii  liblog4cpp5v5   1.1.1-3
ii  libpulse0   11.1-5
ii  libqt5core5a5.10.1+dfsg-5
ii  libqt5gui5  5.10.1+dfsg-5
ii  libqt5network5  5.10.1+dfsg-5
ii  libqt5svg5  5.10.1-2
ii  libqt5widgets5  5.10.1+dfsg-5
ii  libstdc++6  8-20180402-1
ii  libvolk1.3  1.3.1-1
ii  pulseaudio  11.1-5

gqrx-sdr recommends no packages.

gqrx-sdr suggests no packages.

-- no debconf information

Bug#820129: grub2: Disallow booting unsigned kernels when Secure Boot is enabled

2018-04-17 Thread Luca Boccassi

On Mon, 2018-04-16 at 17:16 +0200, Philipp Hahn wrote:
> Hello,
> 
> Am 15.04.2018 um 23:03 schrieb Steve McIntyre:
> > On Thu, Apr 12, 2018 at 05:10:38PM +0100, Luca Boccassi wrote:
> > > On Thu, 2018-04-12 at 15:58 +0100, Steve McIntyre wrote:
> > > > [ Note cc to the d-efi list. SB is finally in progress after
> > > > last
> > > >   week's sprint! ]
> > > > 
> > > > Very belated, it's time we discussed this.
> 
> ...
> > > > This looks like one way of doing this. Philipp Hahn is
> > > > suggesting
> > > > that
> > > > we just don't include the "linux" module in our signed grub
> > > > build. That's simpler, but potentially causes problems
> > > > elsewhere,
> > > > e.g. "it gets a bit nasty to try and dynamically switch between
> > > > linux
> > > > and linuxefi in live-build". So, let's discuss - we need to
> > > > agree our
> > > > policy and decide the best mechanism here. Go...!
> > > 
> > > The issues I see is that until now pretty much everywhere "linux"
> > > is
> > > used in grub.cfg.
> > > 
> > > This can be solved easily, and indeed Philipp has already done
> > > it, for
> > > local installations - the problems arise when building images.
> > > 
> > > At least in live-build (not sure about debootstrap/live-
> > > wrapper?),
> > > users can provide their own grub.cfg. Personally I've never seen
> > > anyone
> > > use anything but "linux" in the menuentry (eg: Kali [2]).
> > > 
> > > So I'd need to do something like this [1] in live-build:
> > > 
> > > sed -i "s|linux\(\s\+/\w\+/vmlinuz\)|linuxefi\1|" \
> > >    binary/boot/grub/grub.cfg
> > > sed -i "s|initrd\(\s\+/\w\+/initrd\)|initrdefi\1|" \
> > >    binary/boot/grub/grub.cfg
> > > 
> > > With the risk of randomly breaking with weird user's grub.cfg :-/
> > > 
> > > I'd really like to make the process as transparent as possible
> > > for
> > > users, as there are already enough hoops to jump through as-is to
> > > get
> > > secure boot working.
> > > 
> > > I have been using the patch from this bug in production for about
> > > a
> > > year as an alternative in the downstream distro at $work, and it
> > > seems
> > > to work fine.
> 
> FYI: We (Univention) have been running with "linux" removed for >2
> years.
> 
> > > On the other hand, I imagine it's easier to verify that nothing
> > > is
> > > broken by removing the "linux" module rather than using this
> > > patch. So
> > > there's the other side of the coin.
> 
> I see 2 use-cases here:
> 
> 1. make it as easiest as possible to install Debian even on systems
> where Secure Boot is enabled by default by providing a signed GRUB
> which
> loads anything.
> 
> 2. have a more secure setup where everything must be signed.
> 
> We chose to be on the save side and thus removed "linux". But you
> patch
> seems to be small enough to verify and actually looks quite nice:
> With
> it both "linux" and "linuxefi" can be used, which has an appeal.
> 
> So I'm okay to switch to your implementation.

Great, thanks! (but please note that the patch is from HPE and the
original submitter of this ticket, not myself :-) )

> @steve: I'm currently busy with work and family and don't have that
> much
> time until next weekend. I havenn't yet checked back for the status
> of
> the signing box, but how do you want to proceed with GRUB: I haven't
> yet
> done a complete test build of my patched packages with a self-created
> set of key to check that everything work as expected. Shall we
> continue
> working on my GIT repo or how do you want to get the required changed
> in
> your repo?
> 
> Thanks in advance and thanks to everyone working on this.
> Philipp

The Ubuntu folks have quite a lot of additional grub + secureboot
patches:

https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/tree/debian/patches/series?h=ubuntu

What are the chances that efforts could be combined? Otherwise we'll
end up facing the same bugs that they already fixed [1].

For what it's worth, I've been shipping our downstream at $work with
those patches as well.

-- 
Kind regards,
Luca Boccassi

[1] I know I have already mentioned it a few times, but those patches
include the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1418360
which completely breaks the kernel lockdown functionality.

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

Bug#895841: lintian -- False positive on spelling-error-in-binary

2018-04-17 Thread Chris Lamb

tags 895841 + pending
thanks

Fixed in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/4aa9f16d236c31ce0a9a078d6e8e30a7ba754123

  data/binaries/spelling-exceptions | 1 +
  debian/changelog  | 1 +
  2 files changed, 2 insertions(+)


Regards,

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

Bug#895896: nm.debian.org: uses the public key network to fetch DDs public keys

2018-04-17 Thread Mattia Rizzolo

Package: nm.debian.org
Severity: important

So, today I discovered that nm2 doesn't actually use the manually
curated debian keyring to fetch gpg keys to use for e.g. validating
signatures in the statements.  Instead, it fatches the keys from the
public keyserver networks.

I consider this a misfuture: the very goal of the debian keyring is to
have clean and tidy keyring full of things we can trust, this behaviour
could lead to e.g. accepting a signature done by a key that is not
considered trusted by our keyring maintainers.
I acknowledge that often people forget to push their keys to
keyring.debian.org when updating expiries or subkeys, but today happened
the exact opposite, where a DD pushed new subkeys to the debian keyring
but not to the public network, and as a result he couldn't advocate a
process.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#895895: linux-image-4.15.0-2-amd64: shutdown, suspend operations do not work

2018-04-17 Thread tristan alexander mc leay

Package: linux-image-4.15.0-2-amd64
Severity: normal

Dear Maintainer,

My computer boots directly into X. If I:

   (a) run "shutdown -h now" or otherwise initiate a shutdown
   (b) close the lid or otherwise attempt to suspend the system

the computer hangs instead of completing. In case (a), the computer will
not shutdown. Instead, whatever state the screen was in when I initiated
the shutdown command remains on screen.

Likewise, in case (b), if I ask it to suspend, it doesn't work. Instead,
the screen goes black and it looks as though it's really suspending, but
the computer remains hot, the fan will turn on if it has to, and whether
I open the laptop or press the power button, the system will not resume.

I have now booted into 4.14, and it works normally.

Here's the contents of lspci which I think might be useful in this case.
If some other information is more useful, please reply by email.

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor
Host Bridge/DRAM Registers (rev 05)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor
Thermal Subsystem (rev 05)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI
Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal
subsystem (rev 31)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial
IO I2C Controller #0 (rev 31)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H Serial
IO I2C Controller #1 (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI
#1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller
[AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1
(rev f1)
00:1c.1 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #2
(rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9
(rev f1)
00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13
(rev f1)
00:1d.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #15
(rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev
a1)
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network
Adapter (rev 32)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI
Express Card Reader (rev 01)
04:00.0 Non-Volatile memory controller: Toshiba America Info Systems XG4 NVMe
SSD Controller (rev 01)
06:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine
Ridge 2C 2015]
07:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine
Ridge 2C 2015]
07:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine
Ridge 2C 2015]
07:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine
Ridge 2C 2015]
3e:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine
Ridge]


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

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

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



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

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=eo.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=eo.UTF-8:eo.UTF-8:eo:en_AU.UTF-8:en.UTF-8:en 
(charmap=UTF-8) (ignored: LC_ALL set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-4.15.0-2-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod25-1
ii  linux-base  4.5

Versions of packages linux-image-4.15.0-2-amd64 recommends:
ii  apparmor 2.12-4
ii  firmware-linux-free  3.4
ii  irqbalance   1.3.0-0.1

Versions of packages linux-image-4.15.0-2-amd64 suggests:
pn  debian-kernel-handbook  
ii  extlinux3:6.03+dfsg1-2
ii  grub-efi-amd64  2.02+dfsg1-4
pn  linux-doc-4.15

Bug#895894: Duplicate

2018-04-17 Thread steven hay

This appears to be duplicated from 895892. I attempted to send the message a 
second time directly from my account when my email provided indicated that the 
previous mail had not been delivered. My apologies.
Steven M. Hay wintermute...@yahoo.com

Bug#895897: how to purge removed packages without breaking your fingers

2018-04-17 Thread Harald Dunkel


Package: apt
Version: 1.4.8
Severity: wishlist

There are some weird constructs floating around about how to
purge removed packages, see

https://askubuntu.com/questions/687295/how-to-purge-previously-only-removed-packages

for example. And

https://www.debian.org/doc/manuals/debian-reference/ch02.en.html

mentions only "aptitude purge '~c'".

This could be improved.

Please reassign, if necessary.


Thanx in advance. Please keep on your good work
Harri

Bug#895884: Pending fixes for bugs in the java-wrappers package

2018-04-17 Thread pkg-java-maintainers

tag 895884 + pending
thanks

Some bugs in the java-wrappers package are closed in revision
84fabb71e85eb33432d62ccfcc34f7656219658f in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/java-wrappers.git/commit/?id=84fabb7

Commit message:

Added Java 10 and 11 support (Closes: #895884)

Bug#895886: set jcommander dep to :debian works

in testng pom file, if I replace:


com.beust
jcommander
1.x


by


com.beust
jcommander
debian


testing works

Bug#895879: quantlib: enable parallel builds

2018-04-17 Thread Dirk Eddelbuettel


On 17 April 2018 at 08:44, Emilio Pozuelo Monfort wrote:
| Source: quantlib
| Version: 1.12.1-1
| Severity: wishlist
| 
| Hi,
| 
| Your package takes a significant time to build. Enabling parallel builds
| could significantly reduce the build time, which goes up to 20 hours in
| some buildds.

That is true. But over the (many) years I maintained it, I also had
(significant) issue on some smaller arches for lack of ram.  Running in
parallel will not make that better. So I am not sure we can do this that
easily.

Dirk
 
| Thanks for considering,
| Emilio

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#895886: testng: jcommander classes not found

2018-04-17 Thread 殷啟聰 | Kai-Chung Yan

Control: tags -1 |confirmed

I relocated `jcommander` from version `1.x` to `debian`, but unfortunately 
Gradle does not recognize Maven artifact relocations.

To fix this, simply remove the line about `jcommander` in `debian/maven.rules`.

Hmm, now I have no idea why it used `1.x` in the first place. (I am not the 
original maintainer)
|


signature.asc
Description: OpenPGP digital signature

Bug#895886: testng: jcommander classes not found

Le mar. 17 avr. 2018 à 13:37, 殷啟聰 | Kai-Chung Yan  a
écrit :

> Control: tags -1 confirmed
>
> I relocated `jcommander` from version `1.x` to `debian`, but unfortunately
> Gradle does not recognize Maven artifact relocations.
>
> To fix this, simply remove the line about `jcommander` in
> `debian/maven.rules`.
>

it is not defined in debian/maven.rules, only testng. It is a gradle build
, and a dependency of testng so "automatically" added to the test step
classpath.

Olivier

>
> Hmm, now I have no idea why it used `1.x` in the first place. (I am not
> the original maintainer)
>

Bug#772674: RFP: xul-ext-mail-redirect -- Redirect mail to other recipients

2018-04-17 Thread Rogério Brito

Hi there, people.

On Jan 03 2015, Luca Capello wrote:
> On Tue, 09 Dec 2014 22:36:42 +0100, Dominik George wrote:
> > * Package name: xul-ext-mail-redirect
> 
> JFTR, the corresponding URL in the extension list is:
> 
>   
> 
> ...and the corresponding upstream bug is:
> 
>   

And the newest version on addons.mozilla.org indicates that this is
compatible with thunderbird 60 (I have not read the code to verify).

> > The Mailredirect extension for Mozilla Thunderbird (version 6.0 and
> > above) and SeaMonkey adds the ability to redirect one or more emails to
> > one or more recipients. The feature of mail redirecting is also known as
> > bouncing forward or resending.
> 
> I use this extension for a while now and thus I am willing to package
> it, would you like to co-maintain it (I can sponsor, if needed)?

Can we have this extension packaged in Debian? It would be awesome to
"bounce" messages in Thunderbird just like we can with Mutt.

Sorry for the amount of emails sent (I don't know who is responsible for it)
and thanks for packaging this and making Thunderbird very convenient in
Debian.

Thanks,

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

Bug#895879: quantlib: enable parallel builds

2018-04-17 Thread Emilio Pozuelo Monfort

On 17/04/18 13:36, Dirk Eddelbuettel wrote:
> 
> On 17 April 2018 at 08:44, Emilio Pozuelo Monfort wrote:
> | Source: quantlib
> | Version: 1.12.1-1
> | Severity: wishlist
> | 
> | Hi,
> | 
> | Your package takes a significant time to build. Enabling parallel builds
> | could significantly reduce the build time, which goes up to 20 hours in
> | some buildds.
> 
> That is true. But over the (many) years I maintained it, I also had
> (significant) issue on some smaller arches for lack of ram.  Running in
> parallel will not make that better. So I am not sure we can do this that
> easily.

I see. One option is to enable parallel builds on 64 bit architectures
(DEB_HOST_ARCH_BITS == 64) unconditionally. And for 32 bit architectures, it
could be enabled but limited to 2 processes maximum, as an idea. And if that
turns out to cause problems it can be disabled.

Feel free to try something like that if you think it can work.

Cheers,
Emilio

Bug#892994: chromium 65.x issue with proxy

2018-04-17 Thread Pascal Obry

And when I do

chrome://net-internals/#proxy

I get:

<<<
Effective proxy settings

Use DIRECT connections.
Source: SYSTEM FAILED
>>>

So no surprise after all, the proxy settings are not retrieved from
the OS configuration (GNOME for me).

Is there something to do about this?

Thanks,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://photos.obry.net
  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Bug#895898: virt-install adds "method=" boot parameter, which is copied to Grub config

2018-04-17 Thread Raphaël Halimi

Package: virtinst
Version: 1:1.4.0-5
Severity: minor

Hi,

I'm trying to fully automatically install virtual machines by means of a
preseed file. I set "--location" to the desired URL and add some
parameters to "--extra-args" to ask debian-installer to run an automated
installation, tell it where to fetch the preseed file, and add some
parameters that I want copied to the installed system's boot
configuration (for example "elevator=noop").

This works almost perfectly, but there one slight problem: for a reason
I don't understand, virt-install adds "method=" to the kernel parameters (qemu's "-append" option), *after* the
contents of "--extra-args".

As stated in its documentation, debian-installer will copy most kernel
parameters found after "--" or "---" to the installed system's boot
configuration (eg. in /etc/default/grub), filtering the ones it thinks
are destined to itself; so if the "--extra-args" option contains "--" or
"---", the "method=..." argument ends up being copied in
/etc/default/grub, which of course is not desired. Obviously,
debian-installer filter doesn't catch it.

Now, I'm not sure what would be the correct fix for this. I see two
possibilities:

- the conservative (and simple) one: modify virt-install to add
"method=..." *before* the contents of "--extra-args", so that if the
latter contains "--" or "---", "method=..." will be positioned before
those, and won't be copied to the installed system's boot configuration.

- the risky one: modify virt-install to not add "method=..." at all;
after re-reading debian-installer's documentation, I didn't see this
parameter mentioned anywhere. Come to think of it, this shouldn't be
needed: virt-install already fetches the kernel and initrd, and passes
them to the VM, so I can't see why debian-installer should need to know
how they were fetched.

If the second suggestion is totally wrong, and debian-installer does
know (and thus, sometimes need) "method=..." (it should be documented,
then !), maybe the bug should be reassigned to debian-installer, and ask
to add "method=..." to the list of filtered parameters, to prevent it to
be passed to Grub.

I tried to find by myself where the "-append" option is constructed, to
provide a patch for the first fix, but I don't know much python and
couldn't understand the scripts. If you give me a hint about this, I'll
be glad to (try to) help.

Regards,

--
Raphaël Halimi

signature.asc
Description: OpenPGP digital signature

Bug#895899: libhtmlcleaner-java FTBFS with openjdk-9

2018-04-17 Thread Adrian Bunk

Source: libhtmlcleaner-java
Version: 2.21-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libhtmlcleaner-java.html

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.htmlcleaner.UtilsTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.136 s 
- in org.htmlcleaner.UtilsTest
[INFO] Running org.htmlcleaner.DomSerializerTest
[WARNING] Tests run: 5, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.231 
s - in org.htmlcleaner.DomSerializerTest
[INFO] Running org.htmlcleaner.ScriptTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 s 
- in org.htmlcleaner.ScriptTest
[INFO] Running org.htmlcleaner.NamespacesTest
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.088 s 
- in org.htmlcleaner.NamespacesTest
[INFO] Running org.htmlcleaner.TagBalancingTest
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.292 s 
- in org.htmlcleaner.TagBalancingTest
[INFO] Running org.htmlcleaner.VisitorTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 s 
- in org.htmlcleaner.VisitorTest
[INFO] Running org.htmlcleaner.XmlDeclarationsTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 s 
- in org.htmlcleaner.XmlDeclarationsTest
[INFO] Running org.htmlcleaner.JDomSerializerTest
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.053 s 
- in org.htmlcleaner.JDomSerializerTest
[INFO] Running org.htmlcleaner.RandomCloseTagTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.htmlcleaner.RandomCloseTagTest
[INFO] Running org.htmlcleaner.BadTerminationTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.htmlcleaner.BadTerminationTest
[INFO] Running org.htmlcleaner.TagManipulationTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.htmlcleaner.TagManipulationTest
[INFO] Running org.htmlcleaner.SpecialEntitiesTest
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.htmlcleaner.SpecialEntitiesTest
[INFO] Running org.htmlcleaner.EntityDeserializationTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 s 
- in org.htmlcleaner.EntityDeserializationTest
[INFO] Running org.htmlcleaner.SVGTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s 
- in org.htmlcleaner.SVGTest
[INFO] Running org.htmlcleaner.HtmlCleanerTest
[ERROR] Tests run: 56, Failures: 0, Errors: 1, Skipped: 4, Time elapsed: 0.493 
s <<< FAILURE! - in org.htmlcleaner.HtmlCleanerTest
[ERROR] attributeNames(org.htmlcleaner.HtmlCleanerTest)  Time elapsed: 0.193 s  
<<< ERROR!
java.lang.StringIndexOutOfBoundsException: begin 117, end -1, length 161
at 
org.htmlcleaner.HtmlCleanerTest.attributeNames(HtmlCleanerTest.java:61)

[INFO] Running org.htmlcleaner.ClosedTagReopenTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 s 
- in org.htmlcleaner.ClosedTagReopenTest
[INFO] Running org.htmlcleaner.BrowserCompactXmlSerializerTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.htmlcleaner.BrowserCompactXmlSerializerTest
[INFO] Running org.htmlcleaner.TransformationTest
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.htmlcleaner.TransformationTest
[INFO] Running org.htmlcleaner.ConstructorTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.htmlcleaner.ConstructorTest
[INFO] Running org.htmlcleaner.ThreadSafetyTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.276 s 
- in org.htmlcleaner.ThreadSafetyTest
[INFO] Running org.htmlcleaner.PropertiesTest
[INFO] Tests run: 27, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.093 s 
- in org.htmlcleaner.PropertiesTest
[INFO] Running org.htmlcleaner.TagCopyingAndLimitingTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 s 
- in org.htmlcleaner.TagCopyingAndLimitingTest
[INFO] Running org.htmlcleaner.CDATATest
[INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 s 
- in org.htmlcleaner.CDATATest
[INFO] Running org.htmlcleaner.XPatherTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.404 s 
- in org.htmlcleaner.XPatherTest
[INFO] Running org.htmlcleaner.RandomPageTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.htmlcleaner.RandomPageTest
[INFO] Running org.htmlcleaner.DocTypesTest
[INFO] Tests run: 40, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 s 
- in org.htmlcleaner.DocTypesTest
[INFO] Running org.htmlcleaner.CollapseHtmlTest
[INFO] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elap

Bug#887559: jessie-pu: package nvidia-graphics-drivers/340.106-1

2018-04-17 Thread Andreas Beckmann

Followup-For: Bug #887559

Hi,

uploaded according to the new (O)PU instructions. Updated source debdiff
attached.


Andreas


ngd-340.106-1.diff.gz
Description: application/gzip

Bug#895886: testng: jcommander classes not found

2018-04-17 Thread 殷啟聰 | Kai-Chung Yan

By `debian/maven.rules` I mean [1]. It's at line 3. This file configures Gradle 
as well.

Gradle understands the relocations, but it won't add it to the build classpath, 
that's why it fails.

[1]: https://sources.debian.org/src/testng/6.9.12-2/debian/maven.rules



signature.asc
Description: OpenPGP digital signature

Bug#895900: invesalius: Please port to python3

2018-04-17 Thread Gert Wollny

Package: invesalius
Version: 3.1.1-3
Severity: important

Dear Maintainer,

Invesalius is the only package that depends on python-*gdcm, and gdcm
is currently 
going to a transition to provide python3-*gdcm instead. 

This change is also imposed by moving forward with VTK for which we now
also provide 
python3 packages. Unfortunately both, vtk and gdcm, don't make it easy
to provide bindings for both 
python 2 and 3 in one build (and if they would, I'm not sure whether
they would be 
co-installable). 

python3-vtk7 is now available in unstable, and python3-*gdcm is in
experimental, so please consider 
porting the package to python3, or co-ordinate with upstream to do so. 

Many thanks,
Gert

Bug#895208: gnumeric: missing build dependency on libxml2-utils

Hi Dmitry,

On Tue, Apr 17, 2018 at 06:53:11PM +1000, Dmitry Smirnov wrote:
> 
> I would appreciate any help with migration to Salsa. Please go ahead with NMU 
> as well if you feel it is urgent. I'm planning to spend some time on Gnumeric 
> hopefully this weekend...

Gnumeric moved to

https://salsa.debian.org/debian/gnumeric

adapted Vcs-fields, fixed bug and uploaded.

Kind regards

   Andreas.


-- 
http://fam-tille.de

Bug#895886: testng: jcommander classes not found

Le mar. 17 avr. 2018 à 14:06, 殷啟聰 | Kai-Chung Yan  a
écrit :

> By `debian/maven.rules` I mean [1]. It's at line 3. This file configures
> Gradle as well.
>

oh ok, you meant in testng, not in our package...
I locally updated pom to make it work, but means that testng needs to be
updated by maintainers

>
> Gradle understands the relocations, but it won't add it to the build
> classpath, that's why it fails.
>
> [1]: https://sources.debian.org/src/testng/6.9.12-2/debian/maven.rules
>
>

Bug#895886: testng: jcommander classes not found

2018-04-17 Thread 殷啟聰 | Kai-Chung Yan

Yeah, I misunderstood you too.

Strange, if `htsjdk` does not configure `jcommander` in `maven.rules`, `1.x` 
should have been replaced by `debian` on the fly. Maybe `gradle-debian-helper` 
ignores test classpath?



signature.asc
Description: OpenPGP digital signature

Bug#895855: debian-handbook: apt-key add should not be used

2018-04-17 Thread Raphael Hertzog

Hello Sergio,

On Tue, 17 Apr 2018, sergio wrote:
> On 17/04/18 12:21, Raphael Hertzog wrote:
> 
> > This is not part of the Debian Administrator's Handbook. I'm reassigning
> > to the correct package.
> 
> https://www.debian.org/doc/manuals/debian-handbook/sect.package-authentication.en.html
> 
> Would you say this link also is not a part of debian-handbook?

This is part of Debian Handbook, but as I said, I already improved the
wording for the next version of the book:
https://salsa.debian.org/hertzog/debian-handbook/blob/stretch/master/en-US/06_apt.xml#L1859

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#895900: invesalius: Please port to python3

Control: forwarded -1 https://github.com/invesalius/invesalius3/issues/134
Control: tags -1 upstream

-- 
http://fam-tille.de

Bug#895901: backup-manager: fails to purge old remote archives via ftp and ssh

2018-04-17 Thread Thomas Parmelan

Package: backup-manager
Version: 0.7.14-1
Severity: normal
Tags: patch

Hi there,

I recently noticed that my remote archives were not purged anymore (I am
using FTP but the problem would be the same for SSH). This seems to have
started when I upgraded from 0.7.12-4 to 0.7.14-1.

After investigating, I found the problem lies in the fact that
/usr/sbin/backup-manager exports
BM_BMP_PATH=/usr/bin/backup-manager-purge, whereas backup-manager-upload
tries to run $ENV{BM_BMP_PATH}/backup-manager-purge, thus trying to run
/usr/bin/backup-manager-purge/backup-manager-purge, which does not
exist.

My fix was to simply delete the line "export BM_BMP_PATH=$bmp" (line 37)
in /usr/sbin/backup-manager.

For what it's worth, this line was introduced in a commit related to
upstream issue #91 and I reported it there too:
https://github.com/sukria/Backup-Manager/issues/91#issuecomment-381925277

Thanks


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

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

Versions of packages backup-manager depends on:
ii  debconf [debconf-2.0]  1.5.66
ii  perl   5.26.1-5
ii  ucf3.0038

backup-manager recommends no packages.

Versions of packages backup-manager suggests:
pn  anacron
pn  backup-manager-doc 
ii  dar2.5.14+bis-2
ii  dvd+rw-tools   7.1-12
ii  genisoimage9:1.1.11-3+b2
ii  gettext-base   0.19.8.1-6
pn  libnet-amazon-s3-perl  
ii  openssh-client 1:7.7p1-2
ii  wodim  9:1.1.11-3+b2
ii  zip3.0-11+b1

-- debconf-show failed

-- 
Thomas PARMELAN
Ingénierie Vidéo - Unicast / CDN
SFR / Altice Labs France
Campus SFR Saint-Denis

Bug#895855: debian-handbook: apt-key add should not be used

2018-04-17 Thread sergio


On 17/04/18 15:21, Raphael Hertzog wrote:


already improved the wording for the next version of the book:
https://salsa.debian.org/hertzog/debian-handbook/blob/stretch/master/en-US/06_apt.xml#L1859


Thank you!

--
sergio.

Bug#895886: testng: jcommander classes not found

Le mar. 17 avr. 2018 à 14:19, 殷啟聰 | Kai-Chung Yan  a
écrit :

> Yeah, I misunderstood you too.
>
> Strange, if `htsjdk` does not configure `jcommander` in `maven.rules`,
> `1.x` should have been replaced by `debian` on the fly. Maybe
> `gradle-debian-helper` ignores test classpath?
>

I tried to add manually jcommander in htsjdk as a
compile/testcompile/testruntime dependency, but was not added anyway in
test classpath, certainly because it was found, in a way, as an already
defined dep in testng.

But updating
/usr/share/maven-repo/org/testng/testng/debian/testng-debian.pom to specify
debian in version of jcommander instead of 1.x fix the problem for me

Bug#895902: pgadmin4-apache2: Installation via root fails at postinst due to 'sudo not found'

2018-04-17 Thread Benjamin Redling

Package: pgadmin4-apache2
Version: 2.1-2.pgdg90+1
Severity: important

Dear Maintainer,

   * What led up to the situation?

Neither was 'sudo' installed after a minimal install, nor does
the package declare a dependency on 'sudo'

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

Tried to install pgadmin4-apache2 from apt.postgresql.org 

   * What was the outcome of this action?

The installation failed at the postinst script.

   * What outcome did you expect instead?

The proper installation of pgadmin4-apache2 to the point where I
can start to customise the configuratiton.


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

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

Versions of packages pgadmin4-apache2 depends on:
ii  apache2   2.4.25-3+deb9u4
ii  debconf [debconf-2.0] 1.5.61
ii  libapache2-mod-wsgi-py3 [httpd-wsgi]  4.5.11-1
ii  pgadmin4-common   2.1-2.pgdg90+1

pgadmin4-apache2 recommends no packages.

pgadmin4-apache2 suggests no packages.

-- debconf information excluded

Bug#894272: Some fixes

2018-04-17 Thread Er_Maqui

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

re fixed by bug report #895871 / fix
https://salsa.debian.org/ruby-team/gitlab/commit/42a8e904e211a78c9dd018637e339d6562fb2f4a

But this bug / solution does not mention fail with 2FA or with GPG
signatures.

Regards,

https://maqui.darkbolt.net/
Linux registered user ~#363219
PGP keys avaiables at KeyServ. ID: 0x4233E9F2
Los hombres somos esclavos de la historia
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYf0F71OtDykDsKZdCU2zE9sy6H8FAlrV7r8ACgkQCU2zE9sy
6H80+g/9HOZ+4uRFFLFR5qMIK3WD4JdvLLoYzCHuxZHnToqbbl7lvCzTjYMNFyYg
jL7FkiXxDv6Wk1OHEAObYuOOruBuhZ+j1GrgvGAqsED8hq+21HiCVei3hVxvhDeK
Kjns77vzaAGY71lg9ew2jX4lXgoFZWbgRrqtQ9j4RpujbkIaPmEUB/5+4w5JQUBK
uOQHWwLZI7X9apYkOAMb96weAUt0EdJShvz2TGxjMzEwSvDUdcn51slnt5z9iC65
Q7ZAvs37IXNo2zJQ+EImxEmUhtiU9Au4WvU7gQB/5fHE/LYnPomtpRzIyIiUa0la
Wuz9T1wdwJmr1wPHAt7SNy7PQP+gGwTxqAn5T7XFJyD4OVURFQ7+s8lD7eqYI0o5
yMX65uakduXVUkOOEJLDKY/Rr3ZEcLLZio6HPOyvT5fSu+bO3DvYHqDodLfI7f/e
FUOTL/Zx25aGg2U3hZ85EGGd7QAZWADZjUxPJAXqXJ+RerttCywOdOzKq391LhgG
iFAcXVMw8YE+PW/rvv97q0y3ofrqPf5XZi0LJrCl0Ji1rBpT5VGwZrleGfkxnDSp
uEY+odJOwNdURH3aMtwyb3UFKkJk1KBBuqA0OvpAFxp5DsDncNTIbHAhJxdQ2WQ9
hsQf57j1ihzo0dQywPr1us6aNyNjxPy/coZ92yFcL+6Vd7fSLrE=
=5eni
-END PGP SIGNATURE-

Bug#882381: Vielen Dank

2018-04-17 Thread MICHELLE GOODMAN

Sehr geehrte (r) Bitte, ich möchte wissen, ob Sie meine
Nachrichtenvorschläge erhalten, ich brauche Ihre sofortige Antwort
jetzt
Michelle
Vielen Dank

Bug#895903: [torsocks] AAAA replies from Tor not handled

2018-04-17 Thread Kevin Steen


Package: torsocks
Severity: important

torsocks version : 2.2.0-1+deb9u1

Tor now returns IPv6 addresses when hostnames are resolved, but torsocks 
cannot handle this case.


To reproduce:
torsocks -d nc ipv6.test-ipv6.com 80

[I'm using torsocks against the SOCKS5 proxy in TorBrowser.]

This makes it tricky to report bugs using
   torsocks reportbug-ng
as bugs.debian.org will sometimes resolve to a , causing the whole 
program to abort with no error message.

Bug#894971: stretch-pu: package nvidia-graphics-drivers/384.130-1

2018-04-17 Thread Andreas Beckmann

Followup-For: Bug #894971

Hi,

just uploaded according to the new PU instructions. Updated debdiff
attached (some documentation updates).


Andreas


ngd-384.130-1.diff.gz
Description: application/gzip

Bug#895904: getty-run may conflicts with other gettys

2018-04-17 Thread Lorenzo Puliti

Package: getty-run
Version: 2.1.2-11
Severity: important



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

Kernel: Linux 4.15.12-van (SMP w/4 CPU cores; PREEMPT)
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: sysvinit (via /sbin/init)  ( EDIT: It's actually runit )

Versions of packages getty-run depends on:
ii  runit 2.1.2-11
ii  runit-helper  2.7.2

Versions of packages getty-run recommends:
ii  fgetty  0.7-3

getty-run suggests no packages.

-- Configuration Files:
/etc/sv/getty-tty3/finish changed:
SERVICE=getty-tty3
[ $1 = 163 ] && echo "runsv: ERROR $1 in $SERVICE: another getty already on 
tty3" \
 && sv d $(dirname $0) && exit 0 
exec utmpset -w tty3

/etc/sv/getty-tty3/run changed:
pgrep -x getty -t tty3 && exit 163
pgrep -x agetty -t tty3 && exit 163
! type fgetty >/dev/null 2>&1 || exec chpst -P fgetty tty3
exec getty 38400 tty3 linux


-- no debconf information

Welcome back :)

The getty-run package does not check whether the tty is busy with another getty 
(nor try to stop the 
already-running getty) before starting the getty-ttyX services. 
As far as I know the default is to have a getty running in each of the six 
ttys, so the conflict will
happen by default unless the admin takes some action to prevent it.
In my case the getty-run package was installed as a dependency of runit-init, 
so I start noticing the cpu
usage at 100% and it took me a while to understand why..

A easy way to prevent this is to check for an already runing getty (and exit if 
such a getty is found) in
the run file as you see in the /etc/sv/getty-tty3/run file attached above;
also, it's good to print some debug message that explain why the service is not 
running and finally do a 
'sv d service', otherwise runit will endlessly try to restart the service ( see 
the finish file above).

Many Thanks

Lorenzo

Bug#895905: mesa-va-drivers attempts to overwrite nouveau_drv_video.so from vdpau-va-driver

2018-04-17 Thread Piotr Szydelko

Source: mesa
Version: 17.3.8-1
Severity: important

I run `apt full-upgrade` and it ended up with an error.
Now the `apt-get install -f` reports the following:

 Preparing to unpack .../mesa-va-drivers_17.3.8-1_amd64.deb ...
 Unpacking mesa-va-drivers:amd64 (17.3.8-1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/mesa-va-drivers_17.3.8-1_amd64.deb (--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so', 
which is also in package vdpau-va-driver:amd64 0.7.4-dmo5
 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
 Errors were encountered while processing:
  /var/cache/apt/archives/mesa-va-drivers_17.3.8-1_amd64.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)

Maybe those packages should be marked as conflicting or the file should
be handled as by update-alternatives?

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

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

Bug#741964: debootstrap: --variant=fakechroot and --foreign

2018-04-17 Thread Hideki Yamane

control: tags -1 +pending

On Wed, 17 Feb 2016 15:44:53 + jhcha54008  wrote:
> Here is an updated patch for debootstrap 1.0.78+nmu1.

 Adjust it for current git.


diff --git a/scripts/debian-common b/scripts/debian-common
index 4ab1fe8..9b313fc 100644
--- a/scripts/debian-common
+++ b/scripts/debian-common
@@ -56,6 +56,10 @@ first_stage_install () {
fi
 
setup_devices
+
+   if doing_variant fakechroot; then
+   setup_proc_fakechroot
+   fi
 }
 
 second_stage_install () {
@@ -89,9 +93,7 @@ Status: install ok installed" >> "$TARGET/var/lib/dpkg/status"
baseprog="$(($baseprog + ${1:-1}))"
}
 
-   if doing_variant fakechroot; then
-   setup_proc_fakechroot
-   else
+   if doing_variant ! fakechroot; then
setup_proc
in_target /sbin/ldconfig
fi

Bug#895847: RFS: pqiv/2.10.3-1 [ITA] -- Powerful image viewer with minimal UI

2018-04-17 Thread Phillip Berndt

Control: retitle -1 RFS: pqiv/2.10.3-1 [ITA] -- Powerful image viewer with 
minimal UI


This RFS reached Bart. He reached out and asked me if I'd like to maintain the
package myself, provided I can find a sponsor. Would gladly do so - package
updated with myself as maintainer, bug updated to be an ITA. New path to dsc:

https://mentors.debian.net/debian/pool/main/p/pqiv/pqiv_2.10.3-1.dsc


- Phillip

Bug#895905: +second file

2018-04-17 Thread Piotr Szydełko

The package overwrites the
/usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so too.

-- 
Pozdrawiam
Piotr Szydełko

Bug#893700: php7.2: Would you please backport for stretch

2018-04-17 Thread contact


reopen 893700
thanks

Hi Ondřej,

The policy for PHP is same as policy for all other software. Means 
TL;DR: No new major versions.


Is it not possible using the backports repositories for instance 
`stretch-backports`?
The major condition is that the version must be already packaged in 
testing but it seems to be the case with php7.2.


Beside that, from a practical point of view, it seems that many major 
PHP frameworks already require PHP7.1 and above.
I think if we don't provide a backport soon, many users will use 
unofficial packages like dotdeb instead of Debian packages…


Regards,

Thomas Pierson

Bug#895906: pgadmin4-apache2: Purge after unmodified install fails due to missing /var/lib/pgadmin/storage

2018-04-17 Thread Benjamin Redling

Package: pgadmin4-apache2
Version: 2.1-2.pgdg90+1
Severity: important

Dear Maintainer,

   * What led up to the situation?

Purging pgadmin4-apache2 without manual modifications fails
because a directory that wasn't added during install is missing

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

apt purge pgadmin4-apache2
and to make sure buggy first install due to missing sudo (s.
other bug report) wasn't the culprit:
apt install --reinstall pgadmin4-apache2; apt purge
pgadmin4-apache2

   * What was the outcome of this action?

The package removal fails:
Purging configuration files for pgadmin4-apache2 (2.1-2.pgdg90+1)
...
rmdir: failed to remove '/var/lib/pgadmin/storage': No such file
or directory
dpkg: error processing package pgadmin4-apache2 (--purge):
 subprocess installed post-removal script returned error exit
 status 1



   * What outcome did you expect instead?

An error free purge of the unmodified installation


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

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

Versions of packages pgadmin4-apache2 depends on:
ii  apache2   2.4.25-3+deb9u4
ii  debconf [debconf-2.0] 1.5.61
ii  libapache2-mod-wsgi-py3 [httpd-wsgi]  4.5.11-1
ii  pgadmin4-common   2.1-2.pgdg90+1

pgadmin4-apache2 recommends no packages.

pgadmin4-apache2 suggests no packages.

Bug#895907: RM: libtggraphlayout-java -- ROM; Low popcon, never used in 8 years

2018-04-17 Thread Emmanuel Bourg

Package: ftp.debian.org
Severity: normal

Hi,

Please remove the libtggraphlayout-java package. It has never
been used since its upload 8 years ago.

Thank you,

Emmanuel Bourg

Bug#895908: [apt-transport-tor] Invalid DNS SRV queries sent for _socks._tcp.localhost

2018-04-17 Thread Kevin Steen


Package: apt-transport-tor
Version: 0.3
Severity: normal

After installing apt-transport-tor and running
apt update
I noticed a few DNS SRV queries for '_socks._tcp.localhost' are sent to 
my nameserver.


Since the queries are invalid and the tor proxy address is configured in 
apt.conf, these queries shouldn't be generated.

Bug#895909: RM: libspark-java -- ROM; Low popcon, never used in 7 years

2018-04-17 Thread Emmanuel Bourg

Package: ftp.debian.org
Severity: normal

Hi,

Please remove the libspark-java package. It has never
been used since its upload 7 years ago.

Thank you,

Emmanuel Bourg

Bug#895905: mesa-va-drivers attempts to overwrite nouveau_drv_video.so from vdpau-va-driver

2018-04-17 Thread Sebastian Ramacher

On 2018-04-17 15:07:10, Piotr Szydelko wrote:
> Source: mesa
> Version: 17.3.8-1
> Severity: important
> 
> I run `apt full-upgrade` and it ended up with an error.
> Now the `apt-get install -f` reports the following:
> 
>  Preparing to unpack .../mesa-va-drivers_17.3.8-1_amd64.deb ...
>  Unpacking mesa-va-drivers:amd64 (17.3.8-1) ...
>  dpkg: error processing archive 
> /var/cache/apt/archives/mesa-va-drivers_17.3.8-1_amd64.deb (--unpack):
>   trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so', 
> which is also in package vdpau-va-driver:amd64 0.7.4-dmo5

You are using vdpau-va-driver from dmo which is not supported. Please use the
version provided by Debian.

Cheers

>  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
>  Errors were encountered while processing:
>   /var/cache/apt/archives/mesa-va-drivers_17.3.8-1_amd64.deb
>  E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Maybe those packages should be marked as conflicting or the file should
> be handled as by update-alternatives?
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.15.11 (SMP w/4 CPU cores)
> Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8), 
> LANGUAGE=pl_PL.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#895910: RM: colorchooser -- ROM; Low popcon, never used in 7 years

2018-04-17 Thread Emmanuel Bourg

Package: ftp.debian.org
Severity: normal

Hi,

Please remove the colorchooser package. It has never
been used since its upload 7 years ago.

Thank you,

Emmanuel Bourg

Bug#895798: /usr/bin/systemd-nspawn: systemd-nspawn doesn't recognise -E, does recognise --setenv

2018-04-17 Thread Michael Biebl

Control: fixed -1 233-1
Control: tags -1 fixed-upstream patch

Am 16.04.2018 um 08:30 schrieb Lars Wirzenius:
> Package: systemd-container
> Version: 232-25+deb9u3
> Severity: minor
> File: /usr/bin/systemd-nspawn
> 
> Dear Maintainer,
> 
> I wanted to set an environment variable inside the container, when
> running a command with systemd-nspawn. -E doesn't work, --setenv does.
> 

--setenv was added in v209
https://github.com/systemd/systemd/commit/f4889f656b477887b02caa5e9d27387309c75a87

The -E alias in v230
https://github.com/systemd/systemd/commit/a5f1cb3bad6742ca21e31d8cd71190b93b3c0cef

But the following was missed, and added in v233
https://github.com/systemd/systemd/commit/2e1f244efd2dfc1a60d032bef3d88b9ba6e0444b

Thus marking as fixed in 233-1.

Whether this is something important enough to be fixed for stable is up
to the SRM to decide.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#730638: closed by Gürkan Myczko

2018-04-17 Thread Wookey

On 2018-04-16 11:03 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the wnpp package:
> 
> #730638: ITP: cloudcompare -- 3D point cloud and mesh processing software
> 
> It has been closed by Gürkan Myczko .
> 
> Source: cloudcompare
> Source-Version: 2.9.1+git20180223-1
> 
> We believe that the bug you reported is fixed in the latest version of
> cloudcompare, which is due to be installed in the Debian FTP archive.

Hi thanks for finishing off this work.

My original packaging was rejected (in Oct 2014) due to a non-free
component (triangle implementation), which I reported upstream and
they eventually fixed ( a year or so later (Nov 2015) (by replacing
it).

I see that I got a notification about that fix in 2015, and I did
update my local copy to 2.7.0 in Sept 2016, but I clearly failed to
actually finish that and do an upload since then, so well done for
actually getting round to it, as opposed to my mere good intentions
:-)

I'm pleased to see cloudcompare in Debian at last, after ~4 years of
somewhat sporadic efforts.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Bug#895906: Manually adding missing dir /var/lib/pgadmin/storage won't help

2018-04-17 Thread Benjamin Redling

apt purge will still fail after manually adding the missing, empty directory

apt remove is works as expected

BR
-- 
FSU Jena | JULIELab.de/Staff/Benjamin+Redling.html

Bug#730638: closed by Gürkan Myczko

2018-04-17 Thread Gürkan Myczko

Only happened because we have users of it. I am looking at micmac now...

If you want I can add you as co-maintainer

Best,

Gürkan
Tel. 076 436 72 00


> On Apr 17, 2018, at 15:39, Wookey  wrote:
> 
>> On 2018-04-16 11:03 +, Debian Bug Tracking System wrote:
>> This is an automatic notification regarding your Bug report
>> which was filed against the wnpp package:
>> 
>> #730638: ITP: cloudcompare -- 3D point cloud and mesh processing software
>> 
>> It has been closed by Gürkan Myczko .
>> 
>> Source: cloudcompare
>> Source-Version: 2.9.1+git20180223-1
>> 
>> We believe that the bug you reported is fixed in the latest version of
>> cloudcompare, which is due to be installed in the Debian FTP archive.
> 
> Hi thanks for finishing off this work.
> 
> My original packaging was rejected (in Oct 2014) due to a non-free
> component (triangle implementation), which I reported upstream and
> they eventually fixed ( a year or so later (Nov 2015) (by replacing
> it).
> 
> I see that I got a notification about that fix in 2015, and I did
> update my local copy to 2.7.0 in Sept 2016, but I clearly failed to
> actually finish that and do an upload since then, so well done for
> actually getting round to it, as opposed to my mere good intentions
> :-)
> 
> I'm pleased to see cloudcompare in Debian at last, after ~4 years of
> somewhat sporadic efforts.
> 
> Wookey
> -- 
> Principal hats:  Linaro, Debian, Wookware, ARM
> http://wookware.org/

Bug#895911: RM: mandelbulber -- ROM; Superseded by mandelbulber2

2018-04-17 Thread Giovanni Mascellani

Package: ftp.debian.org
Severity: normal

Please remove package mandelbulber, which is now superseded by
mandelbulber2 and not maintained upstream anymore.

Thanks, Giovanni.

Bug#895913: please upgrade to new upstream version

2018-04-17 Thread Gürkan Myczko


Package: file
Version: 1:5.32-2
Severity: normal

Please upgrade to the newer version 5.33

Thanks

Bug#895912: newer upstream version available

2018-04-17 Thread Gürkan Myczko


Package: kea-dhcp4-server
Version: 1.1.0-1
Severity: normal

Please upgrade to the newer version, 1.3.0 available at 
https://www.isc.org/downloads/


Thanks

Bug#895915: blktrace: libav-tools has been removed

Package: blktrace
Version: 1.1.0-2
Severity: normal
Tags: sid buster
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-libav-tools-removal

Hi,

As of ffmpeg 7:3.4.2-2, libav-tools has been removed from unstable. In
the initial check of packages, only Depends relations were looked so
this package was missed - sorry about that.

Please recommend on ffmpeg instead of libav-tools if you require its
functionality. For this package, ffmpeg2avconv.patch should probably be
dropped as well.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#895914: runit-init: stage 1: missing support for emergency shell (grub 'recovery mode')

2018-04-17 Thread Lorenzo Puliti

Package: runit-init
Version: 2.1.2-11
Severity: normal



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

Kernel: Linux 4.15.12-van (SMP w/4 CPU cores; PREEMPT)
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: sysvinit (via /sbin/init)

Versions of packages runit-init depends on:
ii  getty-run 2.1.2-11
ii  initscripts   2.88dsf-59.10
ii  libc6 2.27-3
ii  runit 2.1.2-11
ii  runit-helper  2.7.2
ii  sysv-rc   2.88dsf-59.10

runit-init recommends no packages.

runit-init suggests no packages.

-- no debconf information

Dear Maintainer,

I've found two issues with the stage 1 file you are shipping with 2.1.11
 first: touch/chmod on /run/runit.stopit is done too early in the boot process, 
/run is not yet mounted 
(not in the title, just don't want to open another bug as i'm attaching 
a 
 stage1 example that fixes both)

 second: GRUB menu has two line for each kernel, and the second one is supposed 
to boot you into an 
 emergency sell, but runit has no support for that so it turns out into 
a regular boot. 
 I think that a working emergency shell is a "must-have" feature, 
expecially untill runit
 suport within Debian is still in development.
 
the following example of stage 1 file works for me

---

$ cat /etc/runit/1  

#!/bin/sh   
  
# system one time tasks 
  

  
PATH=/sbin:/usr/sbin:/bin:/usr/bin  
  

  
# starting initscripts  
  
for initdir in /etc/rcS.d ; do  
  
   for script in "$initdir/S"* ; do
   path=$(realpath "$script")
   name=$(basename "$path")
"$script" start
   done
done
unset path name

# now /run is mounted
touch /run/runit.stopit
chmod 0 /run/runit.stopit

# single mode emergency shell, if requested in GRUB menu
if grep -q -w -i "single" /proc/cmdline 
  then
   echo "Give root password for maintenance or press CONTROL-D to continue"
   sulogin
fi

# starting sevices not yet-migrated to runit
for servicedir in  /etc/rc2.d ; do
for script in "$servicedir/S"* ; do
path=$(realpath "$script")
name=$(basename "$path")
[ -d "/etc/sv/$name" ] || "$script" start
done
done
unset path name

--

I'm aware that a proper support for emergency shell is more complex than this ( 
a single runlevel with 
a sulogin service and some code that select the runlevel to boot into ) but in 
the meantime could you 
evaluate the example and eventually (if it looks ok to you) add it to runit?

Anyway, thank you for maintaining runit!
Lorenzo

Bug#895919: xwax: libav-tools has been removed

Package: xwax
Version: 1.6-2
Severity: normal
Tags: sid buster
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-libav-tools-removal

Hi,

As of ffmpeg 7:3.4.2-2, libav-tools has been removed from unstable. In
the initial check of packages, only Depends relations were looked so
this package was missed - sorry about that.

Please recommend on ffmpeg instead of libav-tools.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#895916: education-video: libav-tools has been removed

Package: education-video
Version: 2.10.22
Severity: normal
Tags: sid buster
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-libav-tools-removal

Hi,

As of ffmpeg 7:3.4.2-2, libav-tools has been removed from unstable. In
the initial check of packages, only Depends relations were looked so
this package was missed - sorry about that.

Please recommend on ffmpeg instead of libav-tools.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#895917: multimedia-video: libav-tools has been removed

Package: multimedia-video
Version: 0.6
Severity: normal
Tags: sid buster
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-libav-tools-removal

Hi,

As of ffmpeg 7:3.4.2-2, libav-tools has been removed from unstable. In
the initial check of packages, only Depends relations were looked so
this package was missed - sorry about that.

Please recommend on ffmpeg instead of libav-tools.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#895918: vcmi: libav-tools has been removed

Package: vcmi
Version: 0.99+dfsg-2
Severity: normal
Tags: sid buster
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-libav-tools-removal

Hi,

As of ffmpeg 7:3.4.2-2, libav-tools has been removed from unstable. In
the initial check of packages, only Depends relations were looked so
this package was missed - sorry about that.

Please recommend on ffmpeg instead of libav-tools if you require its
functionality.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#887725: what's holding up 2.93 from debian?

2018-04-17 Thread Sandro Tosi

> Any reason why the newer version has not been packaged in Debian yet?

looking from the opposite angle: what do you need so badly in the
latest release?

your NMU version is wrong: since it's a new release, the debian
revision should have been -0.1 not -1.1 - please cancel the NMU and
i'll take care of the upload myself.

> (Any plans on switching away from Alioth as well for git?)

it's already been migrated to salsa:
https://salsa.debian.org/debian/transmission

thanks!

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#895920: ecj: only a virtual package and not installable

2018-04-17 Thread Markus Koschany

Source: ecj
Version: 3.13.2-2
Severity: serious

while I was having some fun with lombok, I discovered that ecj is just
a virtual package and not installable. I don't think that's intended.

Markus

Bug#895921: woo: prefer ffmpeg over mencoder and libav-tools

Source: woo
Version: 1.0+dfsg1-2
Severity: wishlist
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-libav-tools-removal

Hi,

While looking at the libav-tools rdeps, I noticed python-woo and
python3-woo have a recommends on:
 mencoder | libav-tools | ffmpeg

libav-tools has been removed from unstable so please remove this
alternative.

I think packages should recommend ffmpeg over mencoder because ffmpeg is
much more actively developed than mplayer. I also found this line in the
woo source which might indicate mencoder support is disabled anyway?
 https://sources.debian.org/src/woo/1.0+dfsg1-2/py/utils.py/#L504
 "if False and menc: encExec,encType=menc,'mencoder'"

Thanks,
James





signature.asc
Description: OpenPGP digital signature

Bug#893312: lombok FTBFS with openjdk-9

2018-04-17 Thread Markus Koschany

I've fixed the original errors in Javac.java but there are more later on
due to our friend OpenPain 9. I had no choice but to upgrade to a newer
lombok version. Now I'm stuck because ecj can't be found.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#894217: [reprotest] kk_KZ.RK1048 again

2018-04-17 Thread Inaki Malerba

Package: reprotest
Version: 0.7.7

--- Please enter the report below this line. ---

Hi there!

It's me again. I came across the same problem while checking another
package.
Sphinx breaks when the kk_KZ.RK1048 locale is chosen.

Should//I send a patch to change this encoding to a less problematic one?


Cheers!
//

```
# build the html pages for the -doc package
set -ex; \
    cd docs; \
    make html
+ cd docs
+ make html
make[2]�: on entre dans le repertoire
��/tmp/reprotest.eK3Bui/build-experiment-1/docs��
sphinx-build -b html -d _build/doctrees   . _build/html
Running Sphinx v1.7.2
making output directory...
loading pickled environment... not yet created
loading intersphinx inventory from
/usr/share/doc/python2.7/html/objects.inv...
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 24 source files that are out of date
updating environment: 24 added, 0 changed, 0 removed
reading sources... [  4%]
api/base
Exception occurred:
  File
"/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc/__init__.py", line
507, in get_sourcename
    sys.getfilesystemencoding(), 'replace')
TypeError: unicode() argument 2 must be string, not None
```


--- System information. ---
Architecture:
Kernel: Linux 4.15.0-2-amd64

Debian Release: buster/sid
500 unstable httpredir.debian.org
500 trusty ppa.launchpad.net
500 stretch download.docker.com
500 stable repository.spotify.com
500 jessie packagecloud.io

--- Package information. ---
Depends (Version) | Installed
-+-===
diffoscope | 93
python3-distro | 1.0.1-2
python3-rstr | 2.2.6-1
python3:any (>= 3.5~) |
python3-debian | 0.1.32
apt-utils | 1.6~rc1
libdpkg-perl | 1.19.0.5
procps | 2:3.3.14-1
python3-pkg-resources | 39.0.1-2


Recommends (Version) | Installed
==-+-===
diffutils | 1:3.6-1
OR diffoscope (>= 84) | 93
disorderfs (>= 0.5.2) |
faketime | 0.9.7-2
locales-all |
sudo | 1.8.21p2-3


Suggests (Version) | Installed
==-+-===
autodep8 | 0.11.1
schroot | 1.6.10-4
qemu-system |
qemu-utils |

-- 
- ina



signature.asc
Description: OpenPGP digital signature

Bug#891204: irssi: Interface not showing properly

2018-04-17 Thread Francesco

Package: irssi
Followup-For: Bug #891204

Dear Maintainer,


I think the bug is no more present; it could be related to #892923 and #894315


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

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

Versions of packages irssi depends on:
ii  libc6   2.27-3
ii  libglib2.0-02.56.1-2
ii  libperl5.26 5.26.1-5
ii  libssl1.1   1.1.0h-2
ii  libtinfo5   6.1-1
ii  perl5.26.1-5
ii  perl-base [perlapi-5.26.1]  5.26.1-5

irssi recommends no packages.

Versions of packages irssi suggests:
pn  irssi-scripts  

-- no debconf information

Bug#895922: isc-dhcp-server: dhcp server still binds additionally to IPv6 even with explicit -4 option

2018-04-17 Thread Tobias Koeck

Package: isc-dhcp-server
Version: 4.3.5-3+deb9u1
Severity: normal

Dear Maintainer,

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

I was wondering why the DHCP server still binds to the IPv6 address,
too.

I have two internal IPv4 addresses on the eth0 and eth0:0 interface and
one IPv6 address.

root@pdns:/etc/default# cat /etc/default/isc-dhcp-server
# Defaults for dhcp initscript
# sourced by /etc/init.d/dhcp
# installed at /etc/default/isc-dhcp-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
#   Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACESv4="eth0 eth0:0"
OPTIONS="-4"
---

root@pdns:/etc/default# lsof -i -P|grep dhcp
dhcpd   1479 root8u  IPv4  20538  0t0  UDP *:67
dhcpd   1479 root   20u  IPv4  20522  0t0  UDP *:59311
dhcpd   1479 root   21u  IPv6  20523  0t0  UDP *:61725

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

-
Why does it bind to the IPv6 address. And why does it need a second IPv4
binding to Port 59311

-
root@pdns:/etc/default# ps awux|grep dhcpd
root  1479  0.0  0.2  14212  9708 ?Ss   18:30   0:00
/usr/sbin/dhcpd -q -4 -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid
-

I am little bit puzzled about that behavior. Is it a bug or a 'feature'
i didn't recognize in the man pages.

Greetings and thanks,
Tobias


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

Kernel: Linux 4.9.0-6-686-pae (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 isc-dhcp-server depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  debianutils4.8.1.1
ii  libc6  2.24-11+deb9u3
ii  libdns-export162   1:9.10.3.dfsg.P4-12.3+deb9u4
ii  libirs-export141   1:9.10.3.dfsg.P4-12.3+deb9u4
ii  libisc-export160   1:9.10.3.dfsg.P4-12.3+deb9u4
ii  lsb-base   9.20161125

Versions of packages isc-dhcp-server recommends:
ii  isc-dhcp-common  4.3.5-3+deb9u1
ii  policycoreutils  2.6-3

Versions of packages isc-dhcp-server suggests:
pn  isc-dhcp-server-ldap  
ii  policykit-1   0.105-18

-- Configuration Files:
/etc/dhcp/dhcpd.conf changed [not included]
/etc/init.d/isc-dhcp-server changed [not included]

-- debconf information:
  isc-dhcp-server/interfaces:

Bug#724738: sflowtool: changing from RFP to ITP

2018-04-17 Thread Rowan Thorpe

Oops, after 3 years I just noticed that the link I sent in the
previous email was wrong (to the repository I put on github in the
hopes of being helpful despite the lack of Debian Official uptake).
The correct one is (a gbp repo):

 https://github.com/rowanthorpe/sflowtool-debian

Anyway, that is still based on a very old upstream version, but
because the packaging framework is in place it would be relatively
easy to sync it with the latest upstream version, if anyone ever
indicates they would find it useful.

Bug#891339: libglib-object-introspection-perl: Documentation should make a note that the base library devel packages must be installed

2018-04-17 Thread oldtechaa

Here's a patch for debian/control that should fix this. It seems like it
could be made clearer. If you have any thoughts on this, I can change it.

oldtechaa

On Mon, Feb 26, 2018 at 11:55 AM, oldtechaa  wrote:

> OK. I'll work on it.
>
> oldtechaa
>
> On Feb 26, 2018 9:26 AM, "intrigeri"  wrote:
>
>> oldtechaa:
>> > Do you want it in both the package description and README.debian?
>>
>> One of those is sufficient (and duplicated info would inevitably end
>> up de-synchronized).
>>
>
diff --git a/debian/control b/debian/control
index 7f99dac..8232fd4 100644
--- a/debian/control
+++ b/debian/control
@@ -36,3 +36,8 @@ Description: Perl bindings for gobject-introspection libraries
  This package contains Glib::Object::Introspection, the Perl binding
  generator for libraries that support gobject-introspection, such as
  GTK+, WebKit, libsoup and many more.
+ .
+ To use perli11ndoc, the Perl introspection documentation tool, the
+ -dev version of the introspected library must be installed. For
+ example, perli11ndoc can only show documentation for libgtk3-perl if
+ libgtk-3-dev is installed.

Bug#895921: woo: prefer ffmpeg over mencoder and libav-tools