Bug#864637: slapd -V output does not include version

[Ryan Tandy]

Package: slapd
Version: 2.4.31-1
Severity: minor

It was reported to me in IRC that 'slapd -V' in Debian does not actually 
print the version.

stretch:

@(#) $OpenLDAP: slapd  (May 28 2017 16:59:46) $
Debian OpenLDAP Maintainers 

jessie:

@(#) $OpenLDAP: slapd  (May 30 2017 07:55:01) $

buildd@binet:/build/openldap-_xApQ_/openldap-2.4.40+dfsg/debian/build/servers/slapd

wheezy:

@(#) $OpenLDAP: slapd  (Jun  1 2017 21:00:18) $

@846ffda51af4:/home/lamby/temp/cdt.20170601183203.g6ykv6eyq9.ags.openldap/openldap-2.4.31/debian/build/servers/slapd

Squeeze is the last release where it works properly.

@(#) $OpenLDAP: slapd 2.4.23 (Sep 14 2015 13:48:45) $

buildd@x86-csail-01:/build/openldap-9arzX0/openldap-2.4.23/debian/build/servers/slapd

Bug#864636: zutils FTCBFS: uses the build architecture compiler

[Helmut Grohne]

Source: zutils
Version: 1.5-5
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

zutils fails to cross build from source, because it uses the build
architecture compiler. A cross compiler should be passed to ./configure
as a value to CXX. After doing so, zutils cross builds successfully.
Please consider applying the attached patch after stretch is released.

Helmut
diff --minimal -Nru zutils-1.5/debian/changelog zutils-1.5/debian/changelog
--- zutils-1.5/debian/changelog 2017-01-26 17:41:26.0 +0100
+++ zutils-1.5/debian/changelog 2017-06-12 06:51:16.0 +0200
@@ -1,3 +1,10 @@
+zutils (1.5-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: pass triplet-prefixed CXX to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 12 Jun 2017 06:51:16 +0200
+
 zutils (1.5-5) unstable; urgency=low
 
   * Uploading to sid.
diff --minimal -Nru zutils-1.5/debian/rules zutils-1.5/debian/rules
--- zutils-1.5/debian/rules 2017-01-26 17:41:26.0 +0100
+++ zutils-1.5/debian/rules 2017-06-12 06:51:16.0 +0200
@@ -1,10 +1,15 @@
 #!/usr/bin/make -f
 
+include /usr/share/dpkg/architecture.mk
+ifeq ($(origin CXX),default)
+CXX := $(DEB_HOST_GNU_TYPE)-g++
+endif
+
 %:
dh ${@} --parallel
 
 override_dh_auto_configure:
-   LDFLAGS="${LDFLAGS} -static" dh_auto_configure -- --exec-prefix=/
+   LDFLAGS="${LDFLAGS} -static" dh_auto_configure -- --exec-prefix=/ 
CXX=$(CXX)
 
 override_dh_auto_install:
dh_auto_install -- DESTDIR=$(CURDIR)/debian/zutils

Bug#864477: nvidia_icd.json does not refer to correct library when non-GLVND driver variant is installed

[Andreas Beckmann]

On 2017-06-11 19:00, Luca Boccassi wrote:
> Having libGL.so.1 in the ICD works when running with the non-glvnd
> stuff as far as I can see.

So you can confirm the bug with the currently shipped configuration?
(Installing libgl1-nvidia-glx + nvidia-vulkan-icd (s.t. nvidia_icd.json
references libGLX_nvidia.so.0) triggers some bug)


Andreas

Bug#864635: cron.daily: info: rules: meta test __MONEY_FRAUD_8 has dependency 'LOTTO_AGENT' with a zero score

[Paul Wise]

Package: spamassassin
Version: 3.4.1-6
Severity: normal
File: /etc/cron.daily/spamassassin
Usertags: verbose

Yesterday I got these messages from the spamassassin cron job.
I am guessing these are from the downloaded/compiled rules.
It would be better for non-warnings like these to be disabled.

Jun 12 01:23:08.924 [3147] info: rules: meta test __MONEY_FRAUD_8 has 
dependency 'LOTTO_AGENT' with a zero score
Jun 12 01:23:08.925 [3147] info: rules: meta test __FORM_FRAUD_3 has dependency 
'LOTTO_AGENT' with a zero score
Jun 12 01:23:08.927 [3147] info: rules: meta test __ADVANCE_FEE_3_NEW has 
dependency 'LOTTO_AGENT' with a zero score
Jun 12 01:23:08.928 [3147] info: rules: meta test __MONEY_FRAUD_5 has 
dependency 'LOTTO_AGENT' with a zero score
Jun 12 01:23:08.930 [3147] info: rules: meta test __FORM_FRAUD_5 has dependency 
'LOTTO_AGENT' with a zero score
Jun 12 01:23:08.931 [3147] info: rules: meta test __MONEY_FRAUD_3 has 
dependency 'LOTTO_AGENT' with a zero score
Jun 12 01:23:08.932 [3147] info: rules: meta test __ADVANCE_FEE_4_NEW has 
dependency 'LOTTO_AGENT' with a zero score
Jun 12 01:23:08.935 [3147] info: rules: meta test __ADVANCE_FEE_5_NEW has 
dependency 'LOTTO_AGENT' with a zero score
Jun 12 01:23:08.940 [3147] info: rules: meta test __ADVANCE_FEE_2_NEW has 
dependency 'LOTTO_AGENT' with a zero score
Jun 12 01:23:08.941 [3147] info: rules: meta test __FORM_FRAUD has dependency 
'LOTTO_AGENT' with a zero score

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 'testing-
proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790,
'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'),
(690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages spamassassin depends on:
ii  adduser  3.115
ii  curl 7.52.1-5
ii  init-system-helpers  1.48
ii  libhtml-parser-perl  3.72-3
ii  libhttp-date-perl6.02-1
ii  libmail-dkim-perl0.40-1
ii  libnet-dns-perl  1.07-1
ii  libnetaddr-ip-perl   4.079+dfsg-1+b1
ii  libsocket6-perl  0.27-1+b1
ii  libsys-hostname-long-perl1.5-1
ii  libwww-perl  6.15-1
ii  lsb-base 9.20161125
ii  perl 5.24.1-3
ii  perl-modules-5.24 [libarchive-tar-perl]  5.24.1-3
ii  w3m  0.5.3-34

Versions of packages spamassassin recommends:
ii  gnupg 2.1.18-6
ii  libio-socket-inet6-perl   2.72-2
ii  libmail-spf-perl  2.9.0-4
ii  libperl5.24 [libsys-syslog-perl]  5.24.1-3
ii  sa-compile3.4.1-6
ii  spamc 3.4.1-6+b1

Versions of packages spamassassin suggests:
ii  libdbi-perl  1.636-1+b1
pn  libencode-detect-perl
pn  libgeo-ip-perl   
ii  libio-socket-ssl-perl2.044-1
pn  libnet-patricia-perl 
ii  libperl5.24 [libcompress-zlib-perl]  5.24.1-3
pn  pyzor
pn  razor

-- Configuration Files:
/etc/default/spamassassin changed:
CRON=1
PATH="/usr/lib/ccache:$PATH"

/etc/spamassassin/v320.pre changed:
loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#864634: ITP: php-klogger -- simple logging class

[James Valleroy]

Package: wnpp
Severity: wishlist
Owner: James Valleroy 

* Package name: php-klogger
  Version : 1.2.1
  Upstream Author : Kenny Katzgrau 
* URL : https://github.com/katzgrau/KLogger
* License : Expat
  Programming Lang: PHP
  Description : simple logging class

KLogger is a PSR-3 compliant logging class for PHP. It is designed to
be quickly included into a project and work right away.

This is a dependency for php-netscape-bookmark-parser, which is a
dependency for shaarli. I plan to maintain it within the
freedombox-pkg-team.

Bug#864633: fail2ban: Add extra Exim bans.

[Aaron Howell]

Package: fail2ban
Version: 0.9.7-1
Severity: wishlist

There are two types of Exim failures which are logged but not currentlly 
handled by fail2ban.
The first is when a client sends an invalid HELO/EHLO command, and the second 
is when the client sends commands before the banner is displayed.
Both of these are indications of clients looking for open proxies using various 
protocols, and are not something which should be allowed to continuously 
connect (if nothing else, its a waste of bandwidth on bw restricted links).

Here are examples of both.


2017-06-11 16:22:54 rejected HELO from 
163.242-136-217.adsl-static.isp.belgacom.be [217.136.242.163]: syntactically 
invalid argument(s): *.*
2017-06-12 01:54:33 SMTP protocol synchronization error (input sent without 
waiting for greeting): rejected connection from H=[211.138.219.67] input="GET / 
HTTP/1.1\r\n\r\n"

Ideally fail2ban should ban clients who attempt either of these.

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

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

Versions of packages fail2ban depends on:
ii  init-system-helpers  1.47
ii  lsb-base 9.20160110ubuntu5
ii  python3  3.5.3-1

Versions of packages fail2ban recommends:
ii  iptables   1.6.1-1~exp1
ii  python 2.7.13-2
pn  python3-pyinotify  
pn  python3-systemd
ii  whois  5.2.15

Versions of packages fail2ban suggests:
ii  bsd-mailx [mailx]8.1.2-0.20160123cvs-4
pn  monit
ii  rsyslog [system-log-daemon]  8.16.0-1ubuntu5

-- no debconf information

Bug#864632: ksh package does not include libraries needed to load "loadable built-ins"

[George Caswell]

Package: ksh
Version: 93u+20120801-3.1
Severity: normal

I previously reported this problem as issue #821806: However, I think I
initially misunderstood the problem to the extent that the information in that
issue may be misleading.

Korn Shell provides a feature that allows the user to load shared objects into
the shell process as new commands that will be integrated into the shell
environment. The commands loaded in this way have the same functionality as
"built-in" commands internal to the shell, including the ability to manipulate
shell variables and file descriptors. The feature is used like this:

$ ksh
$ builtin -f  

If successful, the newly-loaded command may be run within the shell.

Debian's ksh package appears to contain mostly just those sources needed to
build Korn Shell itself. The current home of the upstream sources, however,
contains a more complete set of related sources:

https://github.com/att/ast

Among other things, this repository includes working examples of loadable
"built-in" libraries, and the dynamic libraries needed to allow these modules
to interface with the shell:

src/cmd/kshlib/: Contains source code for examples of loadable built-ins
src/lib/libast/: Source for libast.so
src/lib/libcmd/: Source for libcmd.so
src/lib/libdll/: Source for libdll.so
src/lib/libcoshell/: I believe this is the directory that provides source for
libshell.so

The four libraries (libast.so, libcmd.so, libdll.so, and libshell.so) are
necessary in order to load the libraries built from src/cmd/kshlib/.  When
built properly, the modules can be loaded and used as follows:

$ builtin -f arch/linux.i386-64/lib/ksh/libcmdtst.so # Provides "xargs" and
various forms of "grep" as builtins
$ builtin grep && echo "grep is builtin"
grep is builtin
$ grep --help
(...Help text demonstrates that "grep" is no longer GNU grep)

$ builtin -f arch/linux.i386-64/lib/ksh/libopen.so open
$ open -r fd /etc/passwd
$ echo $fd
( atime='Sun Jun 11 18:35:02 EDT 2017' ctime='Sun Jun 11 18:35:02 EDT 2017'
dev=2050 fd=4 gid=0 ino=2885926 mode=u='rw,g=r,o=r' mtime='Sun Jun 11 18:35:02
EDT 2017' name=/etc/passwd nlink=1 size=2052 uid=0 )


I am not sure why, but when I have built loadable modules from the upstream
"ast" source tree, I have been unable to load and use them in Debian's version
of ksh. (I usually get a segfault.) But I can load them into the ksh binary
built from the "ast" source tree.



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

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

Versions of packages ksh depends on:
ii  binfmt-support  2.1.6-1
ii  libc6   2.24-9

ksh recommends no packages.

ksh suggests no packages.

-- no debconf information

Bug#862258: so far

[Geert Stappers]

So far is this bugreport missing how the existence of a mlmmj user
could hinder any mlmmj workflow.

There is being told "not needed".  And "do it by hand".
That are no good reasons to block something that upstream advices.


Going to CTTE is indeed an option, for later.

Please reconsider the creation of an user during install.


Cheers
Geert Stappers
Hoping that the BTS accepts this update to this premature closed bugreport.

Bug#864599: python-minimal: pyclean, pycompile and pyversions: Error when /usr/bin/python is python3

[Matthias Julius]

Am 11.06.2017 um 12:35 schrieb Piotr Ozarowski:
> Control: severity 864599 wishlist
> 
> [Matthias Julius, 2017-06-11]
> 
> /usr/bin/python is not something you should be changing via alternatives

Why not?  Can there be no legitimate reason for wanting python3 to be
the default python?

>>   File "/usr/bin/pyclean", line 63
>> except (IOError, OSError), e:
>>  ^
>> SyntaxError: invalid syntax
> 
> if you want Python 3 version of these scripts, use py3compile / py3clean

This is not the point.  Debconf's install script is apparently using
them and they fail if python3 is the default.  This makes debconf
uninstallable.  I don't think this is a bug in debconf.

>> #! /usr/bin/python2
>>
>> helped. They are apparently not compatible with python3.
> 
> I'm not a fan of python2 - we'll not change /usr/bin/python to
> something else than Python 2.X so there's no need to change shebangs.

python-policy 2.4.1 says:

"Python scripts that require the default Python 2 version should specify
python2 as the interpreter name."

While that does not say "must" it is still a strong recommendation.  And
I would also consider that good practice - especially if the fix is so easy.

So while this is no policy violation, to me it is more than a "nice to
have".  But, I will leave it up to you to decide on the proper severity.

Bug#863276: nvidia-driver: nvidia fails to initialize Xorg with linux-image-4.9.0-0.bpo.3-amd64

[Hugo Sepulveda]

Greetings Luca,



Just had time today to test this again , sorry for the delay. I can
confirm the addition of the package into the repo's fixed the issue,
believing this bug report can thus be closed.
Thank you for your time and effort.
Kind regards,
Hugo


Op 01-06-17 om 12:09 schreef Luca Boccassi:
> On Thu, 2017-06-01 at 11:42 +0200, Hugo Sepulveda wrote:
>> Goodmorning  Luca,
>>
>>
>> Is it possible Andreas has uploaded it only to Stretch and sid? I've
>> yet
>> to see the update on jessie-backports.
>>
>> With kind regards,
>>
>>
>> Hugo.
> It's waiting in the queue:
>
> https://ftp-master.debian.org/backports-new.html
>
> Should be a matter of days, hopefully.
>
> Kind regards,
> Luca Boccassi
>
>> Op 31-05-17 om 11:25 schreef Luca Boccassi:
>>> On Mon, 2017-05-29 at 09:41 +0200, Hugo Sepulveda wrote:
 Op 28-05-17 om 14:18 schreef Luca Boccassi:
> On Fri, 2017-05-26 at 13:37 +0200, Hugo Sepulveda wrote:
>> I've isolated the problem, it seems the DisplayPort does not
>> get
>> initialized. Have no other OS to test this behaviour, not a
>> replacement
>> GPU card. However i really doubt the displayport just "died"
>> on
>> me,
>> neither is the error caused by hardware failure of the screen
>> itself.
>>
>> Admitted, it's a luxury problem (i cna still work with 2
>> display's
>> connected to the DVI ports), but it used to work fine with 3,
>> now
>> it's
>> all fubar, and X is tripping.
>>
>> Maybe that helps. If you need any additional info, i'm happy
>> to
>> provide it.
> If 375.66 fixes the problem, it might be just your lucky day!
>
> CVEs have been revealed and they are fixed by that version, so
> I
> have
> now uploaded it to unstable. Due to the security implications
> I've
> requested the release team to allow it to migrate to testing as
> well,
> and after that happens we will upload to jessie-backports too.
>
> It will take a few days to a couple of weeks to happen.
>
> Kind regards,
> Luca Boccassi
 That would be really wonderful! Great way to start of a monday.
 Thank you again for your efforts, I'll get back on this issue
 after
 the
 new version has been released on backports to give a status
 update.


 With kind regards,

 Hugo
>>> Andreas has just uploaded 375.66 to jessie-backports, it should be
>>> available in the repositories in a few hours.
>>>
>>> Kind regards,
>>> Luca Boccassi

Bug#864631: unblock: jetty9/9.2.22-1

[Emmanuel Bourg]

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

Hi,

This is a pre-upload request to unblock jetty9/9.2.22-1. This update fixes
a timing attack in a class checking passwords (no CVE ID has been assigned yet)
and removes a broken symlink (#857217).

Note that Jetty 9.2.x is in maintenance mode and receives only critical fixes
from upstream, that's why I'm suggesting to upload a new version (it mostly
consists in the security fix anyway).

Thank you,

Emmanuel Bourg
diff --git a/VERSION.txt b/VERSION.txt
index 5257d881..5ae8c45c 100644
--- a/VERSION.txt
+++ b/VERSION.txt
@@ -1,3 +1,10 @@
+jetty-9.2.22.v20170531 - 31 May 2017
+ + 920 no main manifest attribute, in jetty-runner-.jar
+ + 1108 Please improve logging in SslContextFactory when there are no approved
+   cipher suites
+ + 1523 Update ALPN support for Java 8u131
+ + 1556 A timing channel in Password.java
+
 jetty-9.2.21.v20170120 - 20 January 2017
  + 592 Support no-value Host header in HttpParser
  + 1229 ClassLoader constraint issue when using NativeWebSocketConfiguration
diff --git a/aggregates/jetty-all/pom.xml b/aggregates/jetty-all/pom.xml
index 2e21ad21..41b2f86c 100644
--- a/aggregates/jetty-all/pom.xml
+++ b/aggregates/jetty-all/pom.xml
@@ -2,7 +2,7 @@
   
 org.eclipse.jetty
 jetty-project
-9.2.21.v20170120
+9.2.22.v20170531
 ../../pom.xml
   
   4.0.0
diff --git a/apache-jsp/pom.xml b/apache-jsp/pom.xml
index 41c59d9c..b4114897 100644
--- a/apache-jsp/pom.xml
+++ b/apache-jsp/pom.xml
@@ -2,7 +2,7 @@
   
 org.eclipse.jetty
 jetty-project
-9.2.21.v20170120
+9.2.22.v20170531
   
   4.0.0
   apache-jsp
diff --git a/apache-jstl/pom.xml b/apache-jstl/pom.xml
index 0a4f3463..cc7566a9 100644
--- a/apache-jstl/pom.xml
+++ b/apache-jstl/pom.xml
@@ -2,7 +2,7 @@
   
 org.eclipse.jetty
 jetty-project
-9.2.21.v20170120
+9.2.22.v20170531
   
   4.0.0
   apache-jstl
diff --git a/debian/changelog b/debian/changelog
index 4470c642..46ffe734 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+jetty9 (9.2.22-1) unstable; urgency=medium
+
+  * Team upload.
+  * New upstream release
+  * No longer create a link to jetty-overlay-deployer (Closes: #857217)
+
+ -- Emmanuel Bourg   Sun, 11 Jun 2017 23:23:14 +0200
+
 jetty9 (9.2.21-1) unstable; urgency=medium
 
   * Team upload.
diff --git a/debian/jetty9.install b/debian/jetty9.install
index ae122cb4..58aa01b3 100644
--- a/debian/jetty9.install
+++ b/debian/jetty9.install
@@ -6,7 +6,6 @@ jetty-distribution/src/main/resources/etc/*  etc/jetty9
 jetty-jaas/src/main/config/etc/* etc/jetty9
 jetty-jmx/src/main/config/etc/*  etc/jetty9
 jetty-monitor/src/main/config/etc/*  etc/jetty9
-jetty-overlay-deployer/src/main/config/etc/* etc/jetty9
 jetty-plus/src/main/config/etc/* etc/jetty9
 jetty-proxy/src/main/config/etc/*etc/jetty9
 jetty-quickstart/src/main/config/etc/*   etc/jetty9
@@ -39,7 +38,6 @@ jetty-jaspi/src/main/config/modules/*.mod 
  usr/share/je
 jetty-jmx/src/main/config/modules/*.mod 
usr/share/jetty9/modules
 jetty-jndi/src/main/config/modules/*.mod
usr/share/jetty9/modules
 jetty-monitor/src/main/config/modules/*.mod 
usr/share/jetty9/modules
-jetty-overlay-deployer/src/main/config/modules/*.mod
usr/share/jetty9/modules
 jetty-plus/src/main/config/modules/*.mod
usr/share/jetty9/modules
 jetty-proxy/src/main/config/modules/*.mod   
usr/share/jetty9/modules
 jetty-quickstart/src/main/config/modules/*.mod  
usr/share/jetty9/modules
diff --git a/debian/jetty9.links b/debian/jetty9.links
index 0608047b..95e92111 100755
--- a/debian/jetty9.links
+++ b/debian/jetty9.links
@@ -25,7 +25,6 @@ usr/share/java/jetty9-jaspi.jar 
usr/share/jetty9/lib/jetty-jaspi
 usr/share/java/jetty9-jmx.jar   
usr/share/jetty9/lib/jetty-jmx-${VERSION}.jar
 usr/share/java/jetty9-jndi.jar  
usr/share/jetty9/lib/jetty-jndi-${VERSION}.jar
 usr/share/java/jetty9-monitor.jar   
usr/share/jetty9/lib/monitor/jetty-monitor-${VERSION}.jar
-usr/share/java/jetty9-overlay-deployer.jar  
usr/share/jetty9/lib/jetty-overlay-deployer-${VERSION}.jar
 usr/share/java/jetty9-plus.jar  
usr/share/jetty9/lib/jetty-plus-${VERSION}.jar
 usr/share/java/jetty9-proxy.jar 
usr/share/jetty9/lib/jetty-proxy-${VERSION}.jar
 usr/share/java/jetty9-quickstart.jar
usr/share/jetty9/lib/jetty-quickstart-${VERSION}.jar
diff --git a/debian/libjetty9-java.poms b/debian/libjetty9-java.poms
index 488baacf..8bff1950 100644
--- a/debian/libjetty9-java.poms
+++ b/debian/libjetty9-java.poms
@@ -38,7 +38,6 @@ jetty-http/pom.xml  
--java-lib 

Bug#780706: even with 'libjsch-java' package com.jcraft.jsch does not exist

[Geert Stappers]

Hello Debian Java

While working on 
 java.lang.SecurityException: Invalid signature file digest for Manifest main 
attributes
that I report two weeks ago, I encountered another obstacle  :-)

  [javac]   ^
  [javac] 
/build/arduino-1.8.2+dfsg/arduino-core/src/cc/arduino/packages/ssh/SSHPwdSetup.java:33:
 error: package com.jcraft.jsch does not exist
  [javac] import com.jcraft.jsch.JSch;
  [javac]   ^
  [javac] 
/build/arduino-1.8.2+dfsg/arduino-core/src/cc/arduino/packages/ssh/SSHPwdSetup.java:34:
 error: package com.jcraft.jsch does not exist
  [javac] import com.jcraft.jsch.JSchException;
  [javac]   ^

The build depends do have libjsch-java.

In CLASSPATH is /usr/share/java/jsch.jar


Now I'm here asking for a clue where to proceed.



Previous I had successfull build, but with runtime error at startup.

Reason for now having a build error is because I removed .jar files
from uptime tarball. Among the removed jars was jsch-0.1.50.jar.

Commands for reproducing the build error:
  debcheckout arduino
  pristine-tar checkout ../arduino_1.8.2+dfsg.orig.tar.xz
  $YOUR_FAVORITE_BUILD_TOOL



Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#864630: unblock: tomcat8/8.5.14-2

[Emmanuel Bourg]

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

Please unblock package tomcat8, the version 8.5.14-2 contains a fix
for CVE-2017-5664 (#864447).

Thank you,

Emmanuel Bourg
diff --git a/debian/changelog b/debian/changelog
index 363623db..9045d407 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+tomcat8 (8.5.14-2) unstable; urgency=high
+
+  * Team upload.
+  * Fixed CVE-2017-5664: Static error pages can be overwritten if the
+DefaultServlet is configured to permit writes (Closes: #864447)
+
+ -- Emmanuel Bourg   Thu, 08 Jun 2017 12:28:34 +0200
+
 tomcat8 (8.5.14-1) unstable; urgency=medium
 
   * Team upload.
diff --git a/debian/patches/CVE-2017-5664.patch 
b/debian/patches/CVE-2017-5664.patch
new file mode 100644
index ..44476c9b
--- /dev/null
+++ b/debian/patches/CVE-2017-5664.patch
@@ -0,0 +1,56 @@
+Description: CVE-2017-5664: Static error pages can be overwritten
+ if the DefaultServlet is configured to permit writes.
+Origin: backport, https://svn.apache.org/r1793469
+  https://svn.apache.org/r1793488
+--- a/java/org/apache/catalina/servlets/DefaultServlet.java
 b/java/org/apache/catalina/servlets/DefaultServlet.java
+@@ -407,6 +407,18 @@
+ }
+ 
+ 
++@Override
++protected void service(HttpServletRequest req, HttpServletResponse resp)
++throws ServletException, IOException {
++
++if (req.getDispatcherType() == DispatcherType.ERROR) {
++doGet(req, resp);
++} else {
++super.service(req, resp);
++}
++}
++
++
+ /**
+  * Process a GET request for the specified resource.
+  *
+@@ -794,7 +806,7 @@
+ return;
+ }
+ 
+-boolean isError = response.getStatus() >= 
HttpServletResponse.SC_BAD_REQUEST;
++boolean isError = DispatcherType.ERROR == request.getDispatcherType();
+ 
+ boolean included = false;
+ // Check if the conditions specified in the optional If headers are
+--- a/java/org/apache/catalina/servlets/WebdavServlet.java
 b/java/org/apache/catalina/servlets/WebdavServlet.java
+@@ -30,6 +30,7 @@
+ import java.util.TimeZone;
+ import java.util.Vector;
+ 
++import javax.servlet.DispatcherType;
+ import javax.servlet.RequestDispatcher;
+ import javax.servlet.ServletContext;
+ import javax.servlet.ServletException;
+@@ -315,6 +316,11 @@
+ return;
+ }
+ 
++if (req.getDispatcherType() == DispatcherType.ERROR) {
++doGet(req, resp);
++return;
++}
++
+ final String method = req.getMethod();
+ 
+ if (debug > 0) {
diff --git a/debian/patches/series b/debian/patches/series
index 1b369897..fe0ccaef 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -8,3 +8,4 @@
 0018-fix-manager-webapp.patch
 0019-add-distribution-to-error-page.patch
 0021-dont-test-unsupported-ciphers.patch
+CVE-2017-5664.patch

Bug#863216: ITP: emacs-ivy -- a generic completion frontend for Emacs

[Nicholas D Steeves]

Hi Sean,

On Sat, Jun 10, 2017 at 07:39:26AM +0100, Sean Whitton wrote:
> Hello Nicholas,
> 
> Nicholas D Steeves  writes:
> 
> > The emacs-ivy-doc repo is going to be easier because I can rebase as
> > necessary before the initial push.  Would you like to see all the docs
> > in emacs-ivy-doc, or only the two non-free ones?
> 
> This is up to your judgement.  If they are very small, it might be
> better to have them in the main archive.

Hmm...  I'm going to have to investigate this some more.  From what
I've read, the info pages (and optionally the man pages) are intended
to be built from those non-free sources.  This makes it seem like
emacs-ivy-doc should contain the bulk of the documentation; however,
there is one exception that ivy.el references.

> > By the way, how soon do we (as pkg-emacsen) have to implement policy
> > 12.4, and can you provide an example of the style we're going to use?
> 
> I don't think that anyone on the team has done any work on this.  Feel
> free to take the initiative, if it interests you.

Maybe later? :-)  At this point in time I'd like to focus on my RFPs
and ITPs.  It's something that will need to be done, but it seems a
bit early still.

> > Do we also provide the .org and .md markdown files or convert
> > everything using pandoc and install that?
> 
> I would say that the HTML alone would be enough.

Hmm, I've decided to strip documentation from emacs-ivy for now,
because I recently read (on debian-devel) that html documentation is
supposed to go in the -doc package and not the primary package.  If,
as I wait for the conversation to develop on -devel, a user files a
request for documentation bug, then I'll rename it as an ITP for
emacs-ivy-doc and will have to prioritise all of this.

Cheers,
Nicholas

P.S. The git repo is an a reasonable state and I think it might be
time for a preliminary RFS.


signature.asc
Description: Digital signature

Bug#864629: live-build: When build hdd img: chroot/usr/lib/syslinux/mbr.bin’: No such file or directory

[Franz Schleindlhuber]

Package: live-build
Version: 4.0.3-1
Severity: normal

Dear Maintainer,

On a freshly installed Debian Jessie I tried to build a live image with 
target hdd, following exactly the description in
https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html
4.7 Building and using an HDD image.

At the end of the build I get no image and the reason seems to be this:
P: Mounting /dev/loop1 with offset 0
dd: failed to open ‘chroot/usr/lib/syslinux/mbr.bin’: No such file or directory
...
I checked and found chroot/usr/lib/syslinux not existing.
Instead chroot/usr/lib/SYSLINUX exists and contains the file mbr.bin.
As a workaround I copied chroot/usr/lib/SYSLINUX/* to chroot/usr/lib/syslinux/*
and finally could build the hdd image.

One other note: the built hdd image is missing the .img extension but it works.


-- Package-specific info:

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages live-build depends on:
ii  debootstrap  1.0.67

Versions of packages live-build recommends:
ii  cpio2.11+dfsg-4.1+deb8u1
ii  live-boot-doc   4.0.2-1
ii  live-config-doc 4.0.4-1
ii  live-manual-html [live-manual]  1:4.0.1-1

live-build suggests no packages.

-- no debconf information



part of console log

The following NEW packages will be installed:
  dosfstools libparted2 parted syslinux
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/740 kB of archives.
After this operation, 1354 kB of additional disk space will be used.
Selecting previously unselected package libparted2:amd64.
(Reading database ... 22002 files and directories currently installed.)
Preparing to unpack .../libparted2_3.2-7_amd64.deb ...
Unpacking libparted2:amd64 (3.2-7) ...
Selecting previously unselected package dosfstools.
Preparing to unpack .../dosfstools_3.0.27-1_amd64.deb ...
Unpacking dosfstools (3.0.27-1) ...
Selecting previously unselected package parted.
Preparing to unpack .../parted_3.2-7_amd64.deb ...
Unpacking parted (3.2-7) ...
Selecting previously unselected package syslinux.
Preparing to unpack .../syslinux_3%3a6.03+dfsg-5+deb8u1_amd64.deb ...
Unpacking syslinux (3:6.03+dfsg-5+deb8u1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up libparted2:amd64 (3.2-7) ...
Setting up dosfstools (3.0.27-1) ...
Setting up parted (3.2-7) ...
Setting up syslinux (3:6.03+dfsg-5+deb8u1) ...
Processing triggers for libc-bin (2.19-18+deb8u9) ...
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00028981 s, 0.0 kB/s
!!! The following error/warning messages can be ignored !!!
P: Mounting /dev/loop1 with offset 0
dd: failed to open ‘chroot/usr/lib/syslinux/mbr.bin’: No such file or directory
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists... Done
Building dependency tree   
Reading state information... Done
root@jessie:/home/franz/live-default# 
root@jessie:/home/franz/live-default# ls -l
total 249624
drwxr-xr-x  2 root  root   4096 Jun 11 22:11 auto
drwxr-xr-x  5 root  root   4096 Jun 11 22:18 binary
drwxr-xr-x  7 root  root   4096 Jun 11 22:12 cache
drwxr-xr-x 22 root  root   4096 Jun 11 22:18 chroot
-rw-r--r--  1 root  root1188505 Jun 11 22:13 chroot.files
-rw-r--r--  1 root  root   5816 Jun 11 22:13 chroot.packages.install
-rw-r--r--  1 root  root   5816 Jun 11 22:13 chroot.packages.live
drwxr-xr-x 18 franz franz  4096 Jun 11 15:47 config
-rw-r--r--  1 root  root441 Jun 11 22:18 live-image-amd64.contents
-rw-r--r--  1 root  root1188505 Jun 11 22:17 live-image-amd64.files
-rw-r--r--  1 root  root   5816 Jun 11 22:17 live-image-amd64.packages
drwxr-xr-x  3 root  root   4096 Jun 11 22:11 local

Bug#863464: xserver-xorg-video-openchrome: Experimental package solves WLAN

[hp_mini2133_user]

Package: xserver-xorg-video-openchrome
Followup-For: Bug #863464

Dear Maintainer,
as it was asked, I installed the experimental package to prove that it 
contains the fix. As it states in the package official repository this version 
fixes the issue. It would be nice to have the bug fix in the next stable 
release (aka stretch), althoug I am not aware of the difficulty.

Than you for your work!


-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. 
CN896/VN896/P4M900 [Chrome 9 HC] [1106:3371] (rev 01)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.9.0-3-686-pae (debian-ker...@lists.debian.org) (gcc version 
6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-1 (2017-06-04)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 50215 Jun 11 17:35 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[25.875] 
X.Org X Server 1.19.2
Release Date: 2017-03-02
[25.876] X Protocol Version 11, Revision 0
[25.876] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian
[25.876] Current Operating System: Linux vonbergen-zm-backup 
4.9.0-3-686-pae #1 SMP Debian 4.9.30-1 (2017-06-04) i686
[25.880] Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.0-3-686-pae 
root=/dev/mapper/vonbergen--zm--backup--vg-root ro quiet
[25.880] Build Date: 03 March 2017  03:15:35PM
[25.880] xorg-server 2:1.19.2-1 (https://www.debian.org/support) 
[25.880] Current version of pixman: 0.34.0
[25.880]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[25.880] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[25.881] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun 11 17:32:40 
2017
[25.963] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[25.978] (==) No Layout section.  Using the first Screen section.
[25.978] (==) No screen section available. Using defaults.
[25.979] (**) |-->Screen "Default Screen Section" (0)
[25.979] (**) |   |-->Monitor ""
[25.996] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[25.996] (==) Automatically adding devices
[25.996] (==) Automatically enabling devices
[25.996] (==) Automatically adding GPU devices
[25.996] (==) Max clients allowed: 256, resource mask: 0x1f
[26.367] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[26.367]Entry deleted from font path.
[26.447] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[26.448] (==) ModulePath set to "/usr/lib/xorg/modules"
[26.448] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[26.448] (II) Loader magic: 0x80276720
[26.448] (II) Module ABI versions:
[26.448]X.Org ANSI C Emulation: 0.4
[26.448]X.Org Video Driver: 23.0
[26.448]X.Org XInput driver : 24.1
[26.448]X.Org Server Extension : 10.0
[26.451] (++) using VT number 7

[26.451] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[26.455] (--) PCI:*(0:1:0:0) 1106:3371:103c:3030 rev 1, Mem @ 
0xd000/134217728, 0xfc00/16777216, BIOS @ 0x/131072
[26.469] (II) LoadModule: "glx"
[26.578] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[26.718] (II) Module glx: vendor="X.Org Foundation"
[26.719]compiled for 1.19.2, module version = 1.0.0
[26.719]ABI class: X.Org Server Extension, version 10.0
[26.719] (==) Matched openchrome as autoconfigured driver 0
[26.719] (==) Matched modesetting as autoconfigured driver 1
[26.719] (==) Matched fbdev as autoconfigured driver 2
[26.719] (==) Matched vesa as autoconfigured driver 3
[26.719] (==) Assigned the driver to the xf86ConfigLayout
[26.719] (II) LoadModule: "openchrome"
[26.758] (II) Loading /usr/lib/xorg/modules/drivers/openchrome_drv.so
[26.783] (II) Module openchrome: 
vendor="https://www.freedesktop.org/wiki/Openchrome/;
[

Bug#864464: openjdk-9: Please drop armel from hotspot_archs

[John Paul Adrian Glaubitz]

On 06/10/2017 10:24 AM, peter green wrote:
> From some googling it seems that PLD is just a cache hint instruction, so 
> afaict it
> should be ok just to ifdef it out when building for CPUs that don't support 
> it.

I gave it a short (patches for disabling "bkpt" and "pld" attached), but ran 
into
yet another problem with an unresolvable linker symbol:

/usr/bin/printf "* For target 
hotspot_variant-server_libjvm_gtest_objs_BUILD_GTEST_LIBJVM_link:\n"
* For target hotspot_variant-server_libjvm_gtest_objs_BUILD_GTEST_LIBJVM_link:
(/bin/grep -v -e "^Note: including file:" <
/home/glaubitz/openjdk-9/openjdk-9-9~b170/build/make-support/failure-logs/hotspot_variant-server_libjvm_gtest_objs_BUILD_GTEST_LIBJVM_link.log
 || true) |
/usr/bin/head -n 12
/home/glaubitz/openjdk-9/openjdk-9-9~b170/build/hotspot/variant-server/libjvm/objs/c1_LIRGenerator_arm.o:
 In function
`LIRGenerator::do_ArithmeticOp_FPU(ArithmeticOp*)':
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_LIRGenerator_arm.cpp:745: 
undefined reference to `__aeabi_fadd_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_LIRGenerator_arm.cpp:745: 
undefined reference to `__aeabi_fsub_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_LIRGenerator_arm.cpp:745: 
undefined reference to `__aeabi_dadd_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_LIRGenerator_arm.cpp:745: 
undefined reference to `__aeabi_dsub_glibc'
/home/glaubitz/openjdk-9/openjdk-9-9~b170/build/hotspot/variant-server/libjvm/objs/c1_Runtime1_arm.o:
 In function `Runtime1::pd_name_for_address(unsigned char*)':
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_Runtime1_arm.cpp:1228: 
undefined reference to `__aeabi_fadd_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_Runtime1_arm.cpp:1228: 
undefined reference to `__aeabi_fsub_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_Runtime1_arm.cpp:1228: 
undefined reference to `__aeabi_dadd_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_Runtime1_arm.cpp:1228: 
undefined reference to `__aeabi_dsub_glibc'
/home/glaubitz/openjdk-9/openjdk-9-9~b170/build/hotspot/variant-server/libjvm/objs/templateTable_arm.o:
 In function `TemplateTable::fop2(TemplateTable::Operation)':
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/templateTable_arm.cpp:1747: 
undefined reference to `__aeabi_fadd_glibc'
if test `/usr/bin/wc -l <
/home/glaubitz/openjdk-9/openjdk-9-9~b170/build/make-support/failure-logs/hotspot_variant-server_libjvm_gtest_objs_BUILD_GTEST_LIBJVM_link.log`
 -gt 12; then
/bin/echo "   ... (rest of output omitted)" ; fi
   ... (rest of output omitted)
/usr/bin/printf "* For target 
hotspot_variant-server_libjvm_objs_BUILD_LIBJVM_link:\n"
* For target hotspot_variant-server_libjvm_objs_BUILD_LIBJVM_link:
(/bin/grep -v -e "^Note: including file:" <
/home/glaubitz/openjdk-9/openjdk-9-9~b170/build/make-support/failure-logs/hotspot_variant-server_libjvm_objs_BUILD_LIBJVM_link.log
 || true) | /usr/bin/head -n 12
/home/glaubitz/openjdk-9/openjdk-9-9~b170/build/hotspot/variant-server/libjvm/objs/c1_LIRGenerator_arm.o:
 In function
`LIRGenerator::do_ArithmeticOp_FPU(ArithmeticOp*)':
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_LIRGenerator_arm.cpp:745: 
undefined reference to `__aeabi_fadd_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_LIRGenerator_arm.cpp:745: 
undefined reference to `__aeabi_fsub_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_LIRGenerator_arm.cpp:745: 
undefined reference to `__aeabi_dadd_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_LIRGenerator_arm.cpp:745: 
undefined reference to `__aeabi_dsub_glibc'
/home/glaubitz/openjdk-9/openjdk-9-9~b170/build/hotspot/variant-server/libjvm/objs/c1_Runtime1_arm.o:
 In function `Runtime1::pd_name_for_address(unsigned char*)':
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_Runtime1_arm.cpp:1228: 
undefined reference to `__aeabi_fadd_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_Runtime1_arm.cpp:1228: 
undefined reference to `__aeabi_fsub_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_Runtime1_arm.cpp:1228: 
undefined reference to `__aeabi_dadd_glibc'
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/c1_Runtime1_arm.cpp:1228: 
undefined reference to `__aeabi_dsub_glibc'
/home/glaubitz/openjdk-9/openjdk-9-9~b170/build/hotspot/variant-server/libjvm/objs/templateTable_arm.o:
 In function `TemplateTable::fop2(TemplateTable::Operation)':
./src/hotspot/make/./src/hotspot/src/cpu/arm/vm/templateTable_arm.cpp:1747: 
undefined reference to `__aeabi_fadd_glibc'
if test `/usr/bin/wc -l < 
/home/glaubitz/openjdk-9/openjdk-9-9~b170/build/make-support/failure-logs/hotspot_variant-server_libjvm_objs_BUILD_LIBJVM_link.log`
-gt 12; then /bin/echo "   ... (rest of output omitted)" ; fi
   ... (rest of output omitted)
/usr/bin/printf "\n* All command lines available in 
/home/glaubitz/openjdk-9/openjdk-9-9~b170/build/make-support/failure-logs.\n"

* All command lines available in 

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

[Nicholas D Steeves]

I decided to change this one to experimental rather than unstable and
have pushed the changes and reuploaded to mentors.  Rationale: I
haven't tested smart-mode-line extensively enough with emacs25.


signature.asc
Description: Digital signature

Bug#864628: audacious: Audacious is stuck at version 3.7.2 in Debian Testing

[Simon]

Package: audacious
Version: 3.7.2-1+b1
Severity: normal

Dear Maintainer,

Upstream Audacious version is 3.8.2 but in Debian Testing there is the 3.7.2
version (released more than a year ago). Could you please repackage the last
available version?
Thanks.



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

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

Versions of packages audacious depends on:
ii  audacious-plugins3.7.2-2.1
ii  dbus 1.10.18-1
ii  dbus-x11 1.10.18-1
ii  gtk2-engines-pixbuf  2.24.31-2
ii  libaudcore3  3.7.2-1+b1
ii  libc62.24-11
ii  libgcc1  1:6.3.0-18
ii  libglib2.0-0 2.50.3-2
ii  libstdc++6   6.3.0-18

Versions of packages audacious recommends:
ii  unzip  6.0-21

audacious suggests no packages.

Bug#864627: gromit FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: gromit
Version: 20041213-9
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

gromit fails to cross build from source, because it uses the build
architecture pkg-config. After prefixing it with the host architecture
gnu triplet, gromit cross compiles successfully. Please consider
applying the attached patch after stretch is released.

Helmut
diff --minimal -Nru gromit-20041213/debian/changelog 
gromit-20041213/debian/changelog
--- gromit-20041213/debian/changelog2011-11-13 20:55:40.0 +0100
+++ gromit-20041213/debian/changelog2017-06-11 21:45:14.0 +0200
@@ -1,3 +1,10 @@
+gromit (20041213-9.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Use a triplet-prefixed pkg-config (closes: #-1)
+
+ -- Helmut Grohne   Sun, 11 Jun 2017 21:45:14 +0200
+
 gromit (20041213-9) unstable; urgency=low
 
   * create and install scalable icon
diff --minimal -Nru gromit-20041213/debian/patches/debian-changes 
gromit-20041213/debian/patches/debian-changes
--- gromit-20041213/debian/patches/debian-changes   2011-11-13 
20:56:29.0 +0100
+++ gromit-20041213/debian/patches/debian-changes   2017-06-11 
21:45:14.0 +0200
@@ -273,11 +273,12 @@
   }
 --- gromit-20041213.orig/Makefile
 +++ gromit-20041213/Makefile
-@@ -1,10 +1,18 @@
+@@ -1,10 +1,19 @@
  all: gromit
  
 -proptest: proptest.c
 -  gcc -o proptest proptest.c `gtk-config --libs --cflags`
++PKG_CONFIG ?= pkg-config
 +CPPFLAGS += -DG_DISABLE_DEPRECATED
 +CPPFLAGS += -DGDK_PIXBUF_DISABLE_DEPRECATED
 +# CPPFLAGS += -DGDK_DISABLE_DEPRECATED
@@ -286,7 +287,7 @@
  
 -propertywatch: propertywatch.c
 -  gcc -o propertywatch propertywatch.c `gtk-config --libs --cflags`
-+CPPFLAGS += $(shell pkg-config --cflags-only-I gtk+-2.0 x11)
++CPPFLAGS += $(shell $(PKG_CONFIG) --cflags-only-I gtk+-2.0 x11)
  
 -gromit: gromit.c Makefile
 -  gcc -DG_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED 
-DGDK_DISABLE_DEPRECATED -DPANGO_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE 
-DGTK_MULTIHEAD_SAFE -o gromit gromit.c -Wall `pkg-config --libs --cflags 
gtk+-2.0`
@@ -294,7 +295,7 @@
 +CFLAGS += -O2
 +CFLAGS += -g
 +
-+CFLAGS += $(shell pkg-config --cflags-only-other gtk+-2.0 x11)
++CFLAGS += $(shell $(PKG_CONFIG) --cflags-only-other gtk+-2.0 x11)
 +
-+LOADLIBES += $(shell pkg-config --libs gtk+-2.0 x11)
++LOADLIBES += $(shell $(PKG_CONFIG) --libs gtk+-2.0 x11)
 +LOADLIBES += -lm
diff --minimal -Nru gromit-20041213/debian/rules gromit-20041213/debian/rules
--- gromit-20041213/debian/rules2011-11-13 20:53:16.0 +0100
+++ gromit-20041213/debian/rules2017-06-11 21:45:11.0 +0200
@@ -1,4 +1,7 @@
 #!/usr/bin/make -f
+include /usr/share/dpkg/architecture.mk
+export PKG_CONFIG=$(DEB_HOST_GNU_TYPE)-pkg-config
+
 %:
dh $@ --parallel
 

Bug#864626: RFS: visual-fill-column/1.11-1 [ITP]

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: wishlist
Control: block 861687 by -1

Dear mentors,

I am looking for a sponsor for my package "visual-fill-column"

Package name: visual-fill-column
Version : 1.11-1
Upstream Author : Joost Kremers 
URL : https://github.com/joostkremers/visual-fill-column
License : GPL-3+
Section : lisp

It builds these binary packages:

elpa-visual-fill-column - Emacs mode that wraps visual-line-mode buffers at 
fill-column

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

  https://mentors.debian.net/package/visual-fill-column


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

dget -x 
https://mentors.debian.net/debian/pool/main/v/visual-fill-column/visual-fill-column_1.11-1.dsc

The package's git remote is here:

  https://github.com/joostkremers/visual-fill-column.git

Changes since the last upload:

visual-fill-column (1.11-1) unstable; urgency=medium

  * Initial release. (Closes: #861687)
  * Add 0001-Update-claimed-version-important-for-integration-wit.patch
- Provides the correct version to GNU ELPA and MELPA to prevent
  potential dependency resolution issues.

 -- Nicholas D Steeves   Sun, 11 Jun 2017 15:20:24 -0400

Regards,
Nicholas D Steeves


signature.asc
Description: Digital signature

Bug#864623: 3dchess FTCBFS: uses the build architecture compiler

[Helmut Grohne]

Source: 3dchess
Version: 0.8.1-19
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

3dchess fails to cross build from source, because it uses the build
architecture compiler. Indirecting the $(MAKE) invocation through
dh_auto_build fixes that, because dh_auto_build knows how to pass cross
compilers. The simplest way of doing so is passing --sourcedirectory to
the general dh invocation thus making override_dh_auto_build (and
others) completely redundant. Please consider applying the attached
patch after stretch is released.

Helmut
diff --minimal -Nru 3dchess-0.8.1/debian/changelog 
3dchess-0.8.1/debian/changelog
--- 3dchess-0.8.1/debian/changelog  2015-11-01 01:09:14.0 +0100
+++ 3dchess-0.8.1/debian/changelog  2017-06-11 21:21:39.0 +0200
@@ -1,3 +1,13 @@
+3dchess (0.8.1-19.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Pass --sourcedirectory to dh.
++ Remove redundant overrides such as override_dh_auto_build thus letting
+  dh_auto_build pass cross compilers.
+
+ -- Helmut Grohne   Sun, 11 Jun 2017 21:21:39 +0200
+
 3dchess (0.8.1-19) unstable; urgency=medium
 
   * Team upload.
diff --minimal -Nru 3dchess-0.8.1/debian/rules 3dchess-0.8.1/debian/rules
--- 3dchess-0.8.1/debian/rules  2015-11-01 01:09:14.0 +0100
+++ 3dchess-0.8.1/debian/rules  2017-06-11 21:21:36.0 +0200
@@ -3,16 +3,10 @@
 export DEB_BUILD_MAINT_OPTIONS=hardening=-stackprotectorstrong
 
 %:
-   dh $@ --parallel
-
-override_dh_auto_build:
-   $(MAKE) -C `pwd`/src
-
-override_dh_auto_clean:
-   [ ! -f "`pwd`/src/Makefile" ] || $(MAKE) -C `pwd`/src clean
+   dh $@ --parallel --sourcedirectory=src
 
 override_dh_auto_install:
-   $(MAKE) -C `pwd`/src install BINDIR=`pwd`/debian/3dchess/usr/games
+   dh_auto_install -- BINDIR=`pwd`/debian/3dchess/usr/games
 
 override_dh_installchangelogs:
dh_installchangelogs CHANGES

Bug#864624: sawfish FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: sawfish
Version: 1:1.11.90-1
Tags: upstream patch
User: helm...@debian.org
Usertags: rebootstrap

sawfish fails to cross build from source, because it generally uses the
build architecture pkg-config. It either does so by avoiding the
PKG_PROG_PKG_CONFIG macro, which would properly set up PKG_CONFIG, or by
hard coding pkg-config. After fixing all of these in configure.in,
sawfish still fails to cross build, because it fails executing repdoc.
This sounds like a bug in librep-dev and shall be handled in a separate
bug. Please consider applying the attached patch after stretch is
released.

Helmut
diff --minimal -Nru sawfish-1.11.90/debian/changelog 
sawfish-1.11.90/debian/changelog
--- sawfish-1.11.90/debian/changelog2016-04-24 19:09:19.0 +0200
+++ sawfish-1.11.90/debian/changelog2017-06-11 21:34:00.0 +0200
@@ -1,3 +1,10 @@
+sawfish (1:1.11.90-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: cross.patch (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 11 Jun 2017 21:34:00 +0200
+
 sawfish (1:1.11.90-1) unstable; urgency=low
 
   * New upstream release.
diff --minimal -Nru sawfish-1.11.90/debian/patches/cross.patch 
sawfish-1.11.90/debian/patches/cross.patch
--- sawfish-1.11.90/debian/patches/cross.patch  1970-01-01 01:00:00.0 
+0100
+++ sawfish-1.11.90/debian/patches/cross.patch  2017-06-11 21:33:57.0 
+0200
@@ -0,0 +1,123 @@
+From: Helmut Grohne 
+Subject: use a triplet-prefixed pkg-config for cross compilation
+
+Index: sawfish-1.11.90/configure.in
+===
+--- sawfish-1.11.90.orig/configure.in
 sawfish-1.11.90/configure.in
+@@ -59,7 +59,7 @@
+ AC_HEADER_SYS_WAIT
+ AC_HEADER_TIME
+ AC_CHECK_HEADERS(fcntl.h sys/time.h sys/utsname.h)
+-AC_PATH_PROG(PKG_CONFIG, [pkg-config], [no])
++PKG_PROG_PKG_CONFIG
+ 
+ dnl Check for X headers, etc
+ _cppflags="${CPPFLAGS}"
+@@ -97,7 +97,7 @@
+ 
+ PKG_CHECK_MODULES(libXft, xft >= 1.0
+ ,XFT_LIBS="-lXft"
+-XFT_CFLAGS="`pkg-config --cflags xft`"
++XFT_CFLAGS="`$PKG_CONFIG --cflags xft`"
+ AC_DEFINE(HAVE_X11_XFT_XFT_H, 1, [Have xft])
+ ,AC_MSG_ERROR([cannot locate libXft]))
+ 
+@@ -106,8 +106,8 @@
+ 
+ PKG_CHECK_MODULES(libX11, x11 >= 1.0
+ ,AC_DEFINE(HAVE_X11, 1, [Have X11])
+-X_LIBS="`pkg-config --libs x11`"
+-X_CFLAGS="`pkg-config --cflags x11`"
++X_LIBS="`$PKG_CONFIG --libs x11`"
++X_CFLAGS="`$PKG_CONFIG --cflags x11`"
+ AC_DEFINE(X_DISPLAY_MISSING, 0, [Have x11])
+ ,AC_MSG_ERROR([cannot locate libX11]))
+ 
+@@ -206,8 +206,8 @@
+ ,AC_DEFINE(HAVE_PANGO_XFT, 1, [Have pangoxft]) 
PANGO_MODULES="${PANGO_MODULES} pangoxft" have_pango_xft="yes" 
FONT_LOADER="Pango XFT" AC_SUBST(have_pango_xft)
+ ,AC_MSG_WARN([pango xft support not available 
$PANGO_MIN_VER]))
+ 
+-PANGO_LIBS=`pkg-config --libs $PANGO_MODULES`
+-PANGO_CFLAGS=`pkg-config --cflags $PANGO_MODULES`
++PANGO_LIBS=`$PKG_CONFIG --libs $PANGO_MODULES`
++PANGO_CFLAGS=`$PKG_CONFIG --cflags $PANGO_MODULES`
+ 
+ else FONT_LOADER="X.Org"
+ fi
+@@ -216,11 +216,11 @@
+ REP_MIN_VER="0.92.3"
+ 
+ PKG_CHECK_MODULES(LIBREP, librep >= ${REP_MIN_VER}
+-,REP_EXECDIR="`pkg-config --variable=repcommonexecdir librep`"
+-REP_CFLAGS="`pkg-config --cflags librep`"
+-REP_LIBS="`pkg-config --libs librep`"
++,REP_EXECDIR="`$PKG_CONFIG --variable=repcommonexecdir 
librep`"
++REP_CFLAGS="`$PKG_CONFIG --cflags librep`"
++REP_LIBS="`$PKG_CONFIG --libs librep`"
+ REP_MSGFMT="`which msgfmt`"
+-REP_VERSION="`pkg-config --variable=version librep`"
++REP_VERSION="`$PKG_CONFIG --variable=version librep`"
+ ,AC_MSG_ERROR([cannot locate librep >= $REP_MIN_VER]))
+ 
+ dnl Check for rep-gtk
+@@ -235,8 +235,8 @@
+ GDK_MIN_VER="2.23.0"
+ 
+ PKG_CHECK_MODULES(GTK, gtk+-2.0 >= ${GTK_MIN_VER}
+-,GTK_LIBS="`pkg-config --libs gtk+-2.0`"
+-GTK_CFLAGS="`pkg-config --cflags gtk+-2.0`"
++,GTK_LIBS="`$PKG_CONFIG --libs gtk+-2.0`"
++GTK_CFLAGS="`$PKG_CONFIG --cflags gtk+-2.0`"
+ AC_DEFINE(HAVE_GTK, 1, [Have GTK])
+ ,AC_MSG_ERROR([cannot locate gtk+ >= $GTK_MIN_VER]))
+ 
+@@ -247,8 +247,8 @@
+ 
+ if test "$with_gdk_pixbuf" != "no"; then
+   PKG_CHECK_MODULES(GDK_PIXBUF, gdk-pixbuf-xlib-2.0 >= ${GDK_MIN_VER}
+-,IMAGE_CFLAGS="`pkg-config --cflags 
gdk-pixbuf-xlib-2.0`"
+-IMAGE_LIBS="`pkg-config --libs gdk-pixbuf-xlib-2.0`"
++,IMAGE_CFLAGS="`$PKG_CONFIG --cflags 
gdk-pixbuf-xlib-2.0`"
++IMAGE_LIBS="`$PKG_CONFIG --libs 

Bug#864563: [Android-tools-devel] Bug#864563: android-platform-external-libselinux FTCBFS: uses the build architecture compiler

[Hans-Christoph Steiner]

Looks good to me!

.hc

Bug#864625: librcc FTCBFS: uses the build architecture compiler

[Helmut Grohne]

Source: librcc
Version: 0.2.12-0.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

librcc fails to cross build from source, because it uses the build
architecture compiler by failing to pass --host to ./configure.
Thankfully, dh_auto_configure automatically takes care of that.
Indirecting ./configure through dh_auto_configure almost fixes the cross
build, but it also passes a multiarch --libdir, so a few
debian/*.install files need updating. Please consider applying the
attached patch after stretch is released.

Helmut
diff --minimal -Nru librcc-0.2.12/debian/changelog 
librcc-0.2.12/debian/changelog
--- librcc-0.2.12/debian/changelog  2014-03-10 00:40:19.0 +0100
+++ librcc-0.2.12/debian/changelog  2017-06-11 20:07:52.0 +0200
@@ -1,3 +1,12 @@
+librcc (0.2.12-0.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_configure pass --host to ./configure.
++ As a consequence, multiarch debian/*.install.
+
+ -- Helmut Grohne   Sun, 11 Jun 2017 20:07:52 +0200
+
 librcc (0.2.12-0.1) unstable; urgency=high
 
   * Non-maintainer upload.
diff --minimal -Nru librcc-0.2.12/debian/librcc-dev.dirs 
librcc-0.2.12/debian/librcc-dev.dirs
--- librcc-0.2.12/debian/librcc-dev.dirs2010-04-16 21:46:11.0 
+0200
+++ librcc-0.2.12/debian/librcc-dev.dirs2017-06-11 20:07:52.0 
+0200
@@ -1,3 +1,2 @@
 usr/lib
-usr/lib/rcc/engines
 usr/include
diff --minimal -Nru librcc-0.2.12/debian/librcc-dev.install 
librcc-0.2.12/debian/librcc-dev.install
--- librcc-0.2.12/debian/librcc-dev.install 2010-04-16 21:46:11.0 
+0200
+++ librcc-0.2.12/debian/librcc-dev.install 2017-06-11 20:07:52.0 
+0200
@@ -1,6 +1,6 @@
 usr/include/*
-usr/lib/lib*.a
-usr/lib/lib*.so
-usr/lib/*.la
-usr/lib/rcc/engines/*.a
-usr/lib/rcc/engines/*.la
+usr/lib/*/lib*.a
+usr/lib/*/lib*.so
+usr/lib/*/*.la
+usr/lib/*/rcc/engines/*.a
+usr/lib/*/rcc/engines/*.la
diff --minimal -Nru librcc-0.2.12/debian/librcc0.dirs 
librcc-0.2.12/debian/librcc0.dirs
--- librcc-0.2.12/debian/librcc0.dirs   2010-04-16 21:46:11.0 +0200
+++ librcc-0.2.12/debian/librcc0.dirs   2017-06-11 20:07:52.0 +0200
@@ -1,2 +1 @@
 usr/lib
-usr/lib/rcc/engines
diff --minimal -Nru librcc-0.2.12/debian/librcc0.install 
librcc-0.2.12/debian/librcc0.install
--- librcc-0.2.12/debian/librcc0.install2010-04-16 21:46:11.0 
+0200
+++ librcc-0.2.12/debian/librcc0.install2017-06-11 20:07:52.0 
+0200
@@ -1,2 +1,2 @@
-usr/lib/librcc.so.*
-usr/lib/rcc/engines/*.so
+usr/lib/*/librcc.so.*
+usr/lib/*/rcc/engines/*.so
diff --minimal -Nru librcc-0.2.12/debian/librccgtk2-0.install 
librcc-0.2.12/debian/librccgtk2-0.install
--- librcc-0.2.12/debian/librccgtk2-0.install   2010-04-16 21:46:11.0 
+0200
+++ librcc-0.2.12/debian/librccgtk2-0.install   2017-06-11 20:07:52.0 
+0200
@@ -1,2 +1,2 @@
-usr/lib/librccui.so.*
-usr/lib/librccgtk2.so.*
+usr/lib/*/librccui.so.*
+usr/lib/*/librccgtk2.so.*
diff --minimal -Nru librcc-0.2.12/debian/rules librcc-0.2.12/debian/rules
--- librcc-0.2.12/debian/rules  2014-03-09 21:46:07.0 +0100
+++ librcc-0.2.12/debian/rules  2017-06-11 20:07:50.0 +0200
@@ -4,7 +4,7 @@
 
 override_dh_auto_configure:
./autogen.sh
-   ./configure --prefix=/usr --disable-libtranslate \
+   dh_auto_configure -- --disable-libtranslate \
--enable-force-dynamic-engines
 
 override_dh_auto_build:

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: wishlist
Control: block 864393 by -1

Dear mentors,

I am looking for a sponsor for my package "rich-minority"

Package name: rich-minority
Version : 1.0.1-1
Upstream Author : Artur Malabarba 
URL : https://github.com/Malabarba/rich-minority
License : GPL-2+

"rich-minority" is a dependency of "smart-mode-line" (see chain of blocks).

It builds these binary packages:

elpa-rich-minority - Clean-up and beautify the list of minor-modes in 
Emacs' mode-line

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

  https://mentors.debian.net/package/rich-minority

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

dget -x 
https://mentors.debian.net/debian/pool/main/r/rich-minority/rich-minority_1.0.1-1.dsc

The project git remote is here:

  git+ssh://git.debian.org/git/pkg-emacsen/pkg/rich-minority.git

Changes since the last upload:

rich-minority (1.0.1-1) unstable; urgency=medium

  * Initial release. (Closes: #864393)

 -- Nicholas D Steeves   Sun, 11 Jun 2017 15:18:12 -0400

Regards,
Nicholas D Steeves


signature.asc
Description: Digital signature

Bug#861989: nautilus: Nautilus freezes/crashes when right clicking and selecting properties for 1 or more files

[Jason Crain]

On Wed, Jun 07, 2017 at 08:24:54PM +1000, Luke Christopher Clarke wrote:
> Tracker-Message:   Setting page size to 8192
> Tracker-Message:   Setting cache size to 250
> (tracker-store:2134): Tracker-DEBUG: Preparing query: 'PRAGMA
> integrity_check(1)'
> ^C
> luke@luk-main:~$
> 
> -- END TERMINAL COMMANDS 002 --
> 
> 
> I let this run for over 15 minutes

My understanding of sqlite's integrity_check is that can be slow, but
15+ minutes seems excessive.

How large is your tracker database ~/.cache/tracker/meta.db?  Do you
have gigabytes of documents being indexed that would inflate the
database?

Bug#864621: ITP: racket-mode -- emacs support for editing and running racket code

[David Bremner]

Package: wnpp
Severity: wishlist
Owner: David Bremner 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: racket-mode
  Version : 20161103+0+gab6255718
  Upstream Author : Greg Hendershott 
* URL : https://github.com/greghendershott/racket-mode
* License : GPL2+
  Programming Lang: racket, emacs-lisp
  Description : emacs support for editing and running racket code

Provides a major mode to edit Racket source files, as well as a major
mode for a Racket REPL. The edit/run experience is similar to
DrRacket.

This will be maintained as part of the pkg-emacsen-addons team.

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlk9lu0ACgkQ8gKXHaSn
nizx/Av/TQ1/LMouhVfA6VJdfwMgQo6E8+7xBMg7gQ1f/v5Pwoc2FZTj7aTGFl6b
wBMotced4/G7ikcpOw3xw1o7ObqvElvGetFctueIJoQw3yhvY2RsqrH5Uk25SeKx
iU96/rBuuRzM4h4GGFO14cWFZOkvoHMENhUcwcyjmUWdQNVIVZnC8cwlKDIy3aV5
kFKZPxg2G/xYuxsY4GP1lX65ZwcXJXClvU+r8junUdIynaXpzyo2ZBT7RY7BO0Kj
Aym6ZB1vABCh96dYmOSi1IvhBRKTDJJXRXLZofQtDNrVNE9HPCMo1eqLdAqWqLHn
zTaflR1omT4LNDMmJlB4AgMeB81haNB/Uwj8MUft71SYOo4qivhXVU2jbKeHqahP
fEScWo3lw2pP98UA/pLpojtzL6nbxRgemcSw2edKhkBj2bkI277Oo7o1RenBtrBz
exbU8017Oa9p2m20fabWMWeJkJjOYC4RqKMqsYpSeQpD1ZNuEYQS1DVfl5g3poEK
7+SjNnif
=/0ar
-END PGP SIGNATURE-

Bug#864620: camo: missing dependency on openssl

[Jakub Wilk]

Package: camo
Version: 2.3.0+dfsg-1

This happened when installing camo:

   Setting up camo (2.3.0+dfsg-1) ...
   /var/lib/dpkg/info/camo.postinst: 1: /var/lib/dpkg/info/camo.postinst: 
openssl: not found

The installation didn't fail, but I ended up with this:

   $ grep KEY /etc/default/camo
   CAMO_KEY=

--
Jakub Wilk

Bug#864615: please update version of posix standard for scripts (section 10.4)

[Bill Allombert]

On Sun, Jun 11, 2017 at 06:51:49PM +0200, Ralf Treinen wrote:
> Package: debian-policy
> Version: 4.0.0.0
> Severity: normal
> 
> Hello,
> 
> section 10.4 says:
> 
>   Scripts may assume that /bin/sh implements the SUSv3 Shell Command
>   Language ...
> 
> This version of the standard is so outdated that it isn't even any
> longer available on the opengroup web site. The latest version of the
> standard is 4.2 (published in 2016), earlier versions currently 
> available on the opengroup site are 4 (from 2008) and 4.1 (from 2013).
> Please consider updating the policy.

Hello Ralf,

Before doing that, we have to check whether all the relevant packages
are compliant with this update.

This requires that someone reviews all packages that provide /bin/sh to
check whether they implement SUSv4.
The difference between SUSv3 and SUSv4 need to be listed to check
whether this can affect any shell script that rely on SUSv3

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#864544: libgetopt-long-descriptive-perl: option value : and :+ processing are very broken

[Dominic Hargreaves]

On Sun, Jun 11, 2017 at 12:06:49PM +0100, Graham Cobb wrote:
> On 10/06/17 22:21, Dominic Hargreaves wrote:
> > Unfortunately we won't be able to fix either of these issues before
> > stretch releases because we're past the last upload date, even if 
> > fixes were available.
> > 
> > Given the last few releases of Getopt::Long have contained various
> > regressions and regression fixes I'd also be a bit wary of trying to
> > fix this in a stable point release, and indeed of diving in to try 
> > and fix the issue.
> > 
> > This is all a bit unfortunate but I'm not sure there is a solution
> > at this point.
> 
> I wonder if a solution for the immediate future might be to re-package
> the same version of Getopt::Long as available in (the latest update to)
> Jessie (which seems to be 2.42)? Obviously this would be missing some
> number of other bug fixes but it would, at least, not be a regression
> from Jessie.
> 
> As you say, it is too late to change the stretch release content, but
> that version could be made available in sid and in testing when it is
> opened up again (so fairly easily accessible to anyone who hits the
> bug), and could be made available as a stretch backport and in a stretch
> update release. After that is available, we could go back to repackaging
> the upstream version (which would hopefully include both fixes by then)
> and get that into testing to shake it down.
> 
> Or are there too many important changes to Getopt::Long since 2.42 to
> consider reverting?

I did briefly ponder that, but downgrading Getopt::Long in a point
release seems at least as invasive as the bug at hand. It's going
to be quite hard to tell whether that would break more than it would
fix due to people relying on the newer Getopt::Long.

And backports is not the right place for such things either (see
extensive discussions in recent Debian backports threads).

Dominic.

Bug#864617: RM: vtkdata/5.8.0-1

[Adrian Bunk]

On Sun, Jun 11, 2017 at 07:28:55PM +0200, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: rm
> 
> The maintainer filed RC bug
>   #864452 vtkdata: do not ship in stretch
>...

This RC bug does *not* come from the maintainer. [1]

> Andreas

cu
Adrian

[1] I have no clue whether or not the removal request is justified,
or what the maintainer opinion might be

-- 

   "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#864619: RM: flashplugin-nonfree-extrasound/0.0.svn2431-6

[Adrian Bunk]

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

flashplugin-nonfree-extrasound should be removed from stretch since:
- the functionality of the package is adding Esound (removed from
  Debian several releases ago) and OSS (mostly obsolete on Linux,
  src:oss4 is not in stretch) support to Flash,
- looking at bugs like #573846 it is unclear whether it still works at all,
- and flashplugin-nonfree was recently removed from stretch

Bug#832241: librarian-puppet: Section should not be “ruby”

[Sebastien Badia]

owner -1 !
tags -1 + pending
block 832241 by 864616
thanks

Hi Ben,

Thanks for the bug report, this should be fixed in the next upload of
librarian-puppet!

Cheers,

Seb, for pkg-ruby-extras


signature.asc
Description: PGP signature

Bug#864607: noisy mariadb-server-10.1 installation

[Dominic Hargreaves]

Control: reassign -1 debconf
Control: forcemerge 863479 -1

On Sun, Jun 11, 2017 at 07:21:20PM +0200, Andreas Beckmann wrote:
> Control: reassign -1 perl 5.24.1-3
> Control: tag -1 stretch
> Control: retitle -1 perl: noisy about "Unescaped left brace in regex" on 
> upgrades to stretch
> 
> On Sun, 11 Jun 2017 16:59:38 +0300 Juha Heinanen  wrote:
> > During 'apt-get dist-upgrade' from jessie to stretch, this got printed
> > to console:
> > 
> > Setting up mariadb-common (10.1.23-9+deb9u1) ...
> > Selecting previously unselected package mariadb-server-10.1.
> > (Reading database ... 72727 files and directories currently installed.)
> > Preparing to unpack .../mariadb-server-10.1_10.1.23-9+deb9u1_amd64.deb ...
> > Unescaped left brace in regex is deprecated, passed through in regex; 
> > marked by <-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at 
> > /usr/share/perl5/Debconf/Question.pm line 72.
> > Unescaped left brace in regex is deprecated, passed through in regex; 
> > marked by <-- HERE in m/\${ <-- HERE ([^}]+)}/ at 
> > /usr/share/perl5/Debconf/Config.pm line 30.
> > 
> > Please fix so that the deprecated info does not get printed.  If every
> > package would be as noisy, user couldn't comprehend anything about what
> > is going on.
> 
> perl probably should silence this warning for stretch. Especially
> if it triggers on perl packages from jessie during the upgrade
> (because perl was upgraded first, and the package in question will
> be upgraded soon. Or should debconf in jessie be "fixed"?

This has already been discussed in #863479 where it was suggested
that this should be fixed in debconfi in a jessie point-release.

Regards,
Dominic.

Bug#864618: mate-themes: BlackMATE makes Google Chrome 59 unreadable

[Ayke van Laethem]

Package: mate-themes
Version: 3.22.11-1
Severity: normal
Tags: patch

Dear Maintainer,

The most recent Google Chrome version switched to GTK3 [1]. Because of
this, most of the URL bar and some other parts of Chrome are now
unreadable. See the upstream bug [2] for more details.

The fix is really easy. Upstream has made two simple patches to fix the
issue:


https://github.com/mate-desktop/mate-themes/commit/b471395f38fa682bbc4d788703e9e3de38016310

https://github.com/mate-desktop/mate-themes/commit/bb1f13b4146eed2080c7f4b852fc4158a6973842

It would be great if these could be included in mate-themes.

[1]: https://bugs.chromium.org/p/chromium/issues/detail?id=79722#c110
[2]: https://github.com/mate-desktop/mate-themes/issues/182


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

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

Versions of packages mate-themes depends on:
ii  gtk2-engines  1:2.20.2-3
ii  gtk2-engines-murrine  0.98.1.1-6
ii  gtk2-engines-pixbuf   2.24.31-2
ii  librsvg2-common   2.40.16-1+b1
ii  mate-icon-theme   1.16.2-1

Versions of packages mate-themes recommends:
ii  dmz-cursor-theme  0.4.4

mate-themes suggests no packages.

-- no debconf information

Bug#864617: RM: vtkdata/5.8.0-1

[Andreas Beckmann]

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

The maintainer filed RC bug
  #864452 vtkdata: do not ship in stretch
vtkdata is useless with vtk (5.8) gone. There is vtk6 in stretch.

There are no dependency problems.

Andreas

Bug#864616: override: librarian-puppet:admin/optional

[Sebastien Badia]

Package: ftp.debian.org
Severity: normal

Hello,

librarian-puppet is in the Ruby section, but this package ship an Admin
tool (written in Ruby…). Please accept this move of librarian-puppet from
ruby/optional to admin/optional.

Thanks in advance!

Cheers,



(Describe here the reason for this change)

Bug#864607: noisy mariadb-server-10.1 installation

[Andreas Beckmann]

Control: reassign -1 perl 5.24.1-3
Control: tag -1 stretch
Control: retitle -1 perl: noisy about "Unescaped left brace in regex" on 
upgrades to stretch

On Sun, 11 Jun 2017 16:59:38 +0300 Juha Heinanen  wrote:
> During 'apt-get dist-upgrade' from jessie to stretch, this got printed
> to console:
> 
> Setting up mariadb-common (10.1.23-9+deb9u1) ...
> Selecting previously unselected package mariadb-server-10.1.
> (Reading database ... 72727 files and directories currently installed.)
> Preparing to unpack .../mariadb-server-10.1_10.1.23-9+deb9u1_amd64.deb ...
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at 
> /usr/share/perl5/Debconf/Question.pm line 72.
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm 
> line 30.
> 
> Please fix so that the deprecated info does not get printed.  If every
> package would be as noisy, user couldn't comprehend anything about what
> is going on.

perl probably should silence this warning for stretch. Especially
if it triggers on perl packages from jessie during the upgrade
(because perl was upgraded first, and the package in question will
be upgraded soon. Or should debconf in jessie be "fixed"?


Andreas

Bug#864477: nvidia_icd.json does not refer to correct library when non-GLVND driver variant is installed

[Luca Boccassi]

On Sat, 2017-06-10 at 22:51 +0100, Luca Boccassi wrote:
> On June 10, 2017 7:48:55 PM GMT+01:00, Andreas Beckmann  org> wrote:
> > On 2017-06-10 17:36, Luca Boccassi wrote:
> > > Andreas, given we ship it in /usr/share, perhaps the easiest
> > > thing
> > > would be to modify in the maintainer scripts (via config-package-
> > > dev
> > > maybe) in the non-GLVND GLX package. What do you think?
> > 
> > No way. Anything that would trigger debsums is forbidden :-)
> > 
> > Luckily we don't have alternatives for that case :-)
> > So it will probably be diversions + shipping the alternate json in
> > non-glvnd libgl1-nvidia-glx.
> 
> Yes that's what I meant, sorry wrote in a hurry :-) - config-package-
> dev automates generating dpkg-divert snippets for the maintainer
> scripts, I've used it a lot and I find it quite handy. It's a build-
> time tool. We can do it manually too of course!
> 
> I'll give it a test tomorrow for the alternate json and check that it
> works with the applications I've got.
> 
> Kind regards,
> Luca Boccassi

Having libGL.so.1 in the ICD works when running with the non-glvnd
stuff as far as I can see.

I tested DOTA 2 in Vulkan mode and a couple of OpenGL games.

But unfortunately I don't think we can use dpkg-divert as the libgl-
nvidia-glx packages are multiarch (and amd64 + i386 is needed for most
stuff) so they clash :-(

Shall we add a conflict on nvidia-vulkan-common to the non-glvnd
libraries? I guess another solution would be to have a nvidia-vulkan-
common-nonglvnd that conflicts and ships the modified file, but it
seems a bit ugly. It's not very "common" for starters :-)

Kind regards,
Luca Boccassi

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

Bug#864615: please update version of posix standard for scripts (section 10.4)

[Ralf Treinen]

Package: debian-policy
Version: 4.0.0.0
Severity: normal

Hello,

section 10.4 says:

  Scripts may assume that /bin/sh implements the SUSv3 Shell Command
  Language ...

This version of the standard is so outdated that it isn't even any
longer available on the opengroup web site. The latest version of the
standard is 4.2 (published in 2016), earlier versions currently 
available on the opengroup site are 4 (from 2008) and 4.1 (from 2013).
Please consider updating the policy.

Thanks -Ralf.


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

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

debian-policy depends on no packages.

debian-policy recommends no packages.

Versions of packages debian-policy suggests:
ii  doc-base  0.10.7

-- no debconf information

Bug#864614: opendnssec: missing 2.0 upgrade scripts

[Dominik Paulus]

Package: opendnssec-common
Version: 1:2.0.4-3
Severity: normal

Dear Maintainer,

the current opendnssec package is missing the 1.4-2.0 database migration
scripts. Even though there is a debconf note explicitely referring to
/usr/share/opendnssec/1.4-2.0_db_convert, that folder - as installed by
the package opendnssec-common - is empty.

Regards
Dominik

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

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

Versions of packages opendnssec depends on:
ii  libhsm-bin   1:2.0.4-3
ii  opendnssec-enforcer  1:2.0.4-3
ii  opendnssec-signer1:2.0.4-3

Versions of packages opendnssec recommends:
ii  softhsm2  2.2.0-3

Versions of packages opendnssec suggests:
pn  opendnssec-doc  

-- no debconf information

Bug#790803: ITP: neural -- machine-learning for atomistics

[Muammar El Khatib]

Hi,

On Thu, Jul 16, 2015 at 7:53 AM, Andreas Tille  wrote:
>
> I think this ITP is relevant for Debian Science and DebiChem.  I guess
> you intend to maintain it in one of these teams.  Please make sure it
> will be added to the according Blends tasks (I'm fine if you tell me to
> what task what binary package should be added).
>
> It would be nice if you would CC the relevant teams in the beginning
> (and sorry if I missed the announcement).
>
> Thanks for this ITP.

I have a Debian package done for Amp¹ that I built inspired by
Graham's previous packaging that I plan to upload after this latest
Debian release.  I think Debian Science is a good fit for it. I am
very interested in this program because I am currently doing my
postdoc in the group where it is developed and I am working on it a
lot. I will start by moving the repo to /git/debian-science/packages/.

Best,

1. https://anonscm.debian.org/git/collab-maint/amp.git/
-- 
Muammar El Khatib.
http://muammar.me

Bug#864604: usb-modeswitch: USB 3G modem is detected twice as "USB Mass Storage"

[Teemu Likonen]

Josua Dietze [2017-06-11 16:31:16+02] wrote:

> Bottom line:
> The product ID 0x9801 needs to be added to the serial driver of the kernel.
>
> For a quick fix you can do what usb_modeswitch did previously:
> # modprobe -v option
> # echo "1c9e 9801" > /sys/bus/usb-serial/drivers/option1/new_id
>
> You can put this into a script and let it be called by udev
> automatically if your modem is plugged. Put this below the first
> "ACTION" line in /lib/udev/rules.d/40-usb_modeswitch.rules:
>
> ATTR{idVendor}=="1c9e", ATTR{idProduct}=="9801", RUN+="/path/to/your/script"

Thank you very much. I did your suggested quick fix and got my device
working again. I'll try to help others and report the vendor and product
ids to kernel's USB serial subsystem maintainers.

So it's not really usb-modeswitch package's bug but the removed feature
of not loading kernel modules "manually" triggers the underlying
problem. Maybe this bug can be closed.

Thanks!


signature.asc
Description: PGP signature

Bug#864560: gnutls28: CVE-2017-7507

[Andreas Metzler]

Control: found -1 3.3.8-1

On 2017-06-10 Salvatore Bonaccorso  wrote:
> Source: gnutls28
> Version: 3.5.8-1
[...]
> the following vulnerability was published for gnutls28.

> CVE-2017-7507[0]:
> Crash upon receiving well-formed status_request extension
[...]
> Please adjust the affected versions in the BTS as needed, just checked
> 3.5.8 in unstable sourcewise. Not sure as well if it would need a DSA
> if older versions are affected as well.

Hello Salvatore,

thank you for notifying me, I somehow missed this when reading 3.5.13's
NEWS.

It does apply to stable. There is patchset on upstream's gnutls_3_3_x
branch which applies without fuzz to 3.3.8. (See attachment.)

If you are not doing a DSA I can try to fix this in jessie and stretch
point releases.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru gnutls28-3.3.8/debian/changelog gnutls28-3.3.8/debian/changelog
--- gnutls28-3.3.8/debian/changelog	2017-04-27 18:10:54.0 +0200
+++ gnutls28-3.3.8/debian/changelog	2017-06-11 18:07:39.0 +0200
@@ -1,3 +1,14 @@
+gnutls28 (3.3.8-6+deb8u6) UNRELEASED; urgency=medium
+
+  * 56_CVE-2017-7507_1-ext-status_request-ensure-response-IDs-are-pro.patch
+56_CVE-2017-7507_2-ext-status_request-Removed-the-parsing-of-resp.patch
+56_CVE-2017-7507_3-gnutls_ocsp_status_request_enable_client-docum.patch
+from upstream gnutls_3_3_x branch: Fix crash upon receiving
+well-formed status_request extension. GNUTLS-SA-2017-4/CVE-2017-7507
+Closes: #864560
+
+ -- Andreas Metzler   Sun, 11 Jun 2017 11:31:58 +0200
+
 gnutls28 (3.3.8-6+deb8u5) jessie; urgency=medium
 
   * Pull multiple fixes from gnutls_3_3_x branch:
diff -Nru gnutls28-3.3.8/debian/patches/56_CVE-2017-7507_1-ext-status_request-ensure-response-IDs-are-pro.patch gnutls28-3.3.8/debian/patches/56_CVE-2017-7507_1-ext-status_request-ensure-response-IDs-are-pro.patch
--- gnutls28-3.3.8/debian/patches/56_CVE-2017-7507_1-ext-status_request-ensure-response-IDs-are-pro.patch	1970-01-01 01:00:00.0 +0100
+++ gnutls28-3.3.8/debian/patches/56_CVE-2017-7507_1-ext-status_request-ensure-response-IDs-are-pro.patch	2017-06-11 18:03:10.0 +0200
@@ -0,0 +1,71 @@
+From 9d95c912b5843e664c8210887a6719f02a9028be Mon Sep 17 00:00:00 2001
+From: Nikos Mavrogiannopoulos 
+Date: Wed, 24 May 2017 10:46:03 +0200
+Subject: [PATCH 1/3] ext/status_request: ensure response IDs are properly
+ deinitialized
+
+That is, do not attempt to loop through the array if there is no array
+allocated.
+
+Signed-off-by: Nikos Mavrogiannopoulos 
+---
+ lib/ext/status_request.c | 17 +++--
+ 1 file changed, 11 insertions(+), 6 deletions(-)
+
+diff --git a/lib/ext/status_request.c b/lib/ext/status_request.c
+index 8cefc617e..1340dbbb5 100644
+--- a/lib/ext/status_request.c
 b/lib/ext/status_request.c
+@@ -68,7 +68,10 @@ typedef struct {
+ 
+ static void deinit_responder_id(status_request_ext_st *priv)
+ {
+-unsigned i;
++	unsigned i;
++
++	if (priv->responder_id == NULL)
++		return;
+ 
+ 	for (i = 0; i < priv->responder_id_size; i++)
+ 		gnutls_free(priv->responder_id[i].data);
+@@ -134,6 +137,7 @@ server_recv(gnutls_session_t session,
+ {
+ 	size_t i;
+ 	ssize_t data_size = size;
++	unsigned responder_ids = 0;
+ 
+ 	/* minimum message is type (1) + responder_id_list (2) +
+ 	   request_extension (2) = 5 */
+@@ -152,23 +156,24 @@ server_recv(gnutls_session_t session,
+ 	DECR_LEN(data_size, 1);
+ 	data++;
+ 
+-	priv->responder_id_size = _gnutls_read_uint16(data);
++	responder_ids = _gnutls_read_uint16(data);
+ 
+ 	DECR_LEN(data_size, 2);
+ 	data += 2;
+ 
+-	if (data_size <= (ssize_t) (priv->responder_id_size * 2))
++	if (data_size <= (ssize_t) (responder_ids * 2))
+ 		return
+ 		gnutls_assert_val(GNUTLS_E_RECEIVED_ILLEGAL_PARAMETER);
+ 
+-	if (priv->responder_id != NULL)
+-		deinit_responder_id(priv);
++	deinit_responder_id(priv);
+ 
+-	priv->responder_id = gnutls_calloc(1, priv->responder_id_size
++	priv->responder_id = gnutls_calloc(1, responder_ids
+ 	   * sizeof(*priv->responder_id));
+ 	if (priv->responder_id == NULL)
+ 		return gnutls_assert_val(GNUTLS_E_MEMORY_ERROR);
+ 
++	priv->responder_id_size = responder_ids;
++
+ 	for (i = 0; i < priv->responder_id_size; i++) {
+ 		size_t l;
+ 
+-- 
+2.11.0
+
diff -Nru gnutls28-3.3.8/debian/patches/56_CVE-2017-7507_2-ext-status_request-Removed-the-parsing-of-resp.patch gnutls28-3.3.8/debian/patches/56_CVE-2017-7507_2-ext-status_request-Removed-the-parsing-of-resp.patch
--- gnutls28-3.3.8/debian/patches/56_CVE-2017-7507_2-ext-status_request-Removed-the-parsing-of-resp.patch	1970-01-01 01:00:00.0 +0100
+++ gnutls28-3.3.8/debian/patches/56_CVE-2017-7507_2-ext-status_request-Removed-the-parsing-of-resp.patch	2017-06-11 18:03:10.0 +0200
@@ -0,0 +1,132 @@
+From 023a20d21b762918d3e1ab25a207ecf874ba21a9 Mon Sep 17 

Bug#864613: yarssr: default browser invocation command doesn't exist

[Daniel Shahaf]

Package: yarssr
Version: 0.2.2-9
Severity: important

Dear Maintainer,

When clicking on an article's headline, the headline is marked unread but the
article isn't opened.  When I changed the browser invocation command from
"mozilla" (which was the default) to "x-www-browser", clicking on a headline
did open it in a new browser tab.

There is no "mozilla" command on a default jessie installation.  (In fact, I
checked apt-file(1) and couldn't find any package providing a /usr/bin/mozilla.)

I think two changes are needed:

1. (debian specific) Change the default browser from "mozilla" to 
"x-www-browser".

2. (upstreamable) When the browser invocation fails — executing 'mozilla' would
return an exit code of 127, rather than EXIT_SUCCESS, from system(3) — don't
mark the headline, which had just been clicked, unread.

Cheers,

Daniel


-- System Information:
Debian Release: 8.8
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing-updates'), (500, 
'stable-updates'), (250, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages yarssr depends on:
ii  libgnome2-perl 1.045-1+b1
ii  libgnome2-vfs-perl 1.082-1+b1
ii  libgnomevfs2-extra 1:2.24.4-6+b1
ii  libgtk2-gladexml-perl  1.007-2+b1
ii  libgtk2-perl   2:1.2492-4
ii  libgtk2-trayicon-perl  0.06-2+b1
ii  libxml-rss-perl1.55-1
ii  perl   5.20.2-3+deb8u6

yarssr recommends no packages.

yarssr suggests no packages.

-- no debconf information

Bug#864612: irker: Occasional FTBFS: cp: cannot create regular file '/build/1st/irker-2.18+dfsg/irkerhook.html': File exists

[Adrian Bunk]

Source: irker
Version: 2.18+dfsg-2
Severity: important

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/irker.html

...
make[2]: Entering directory '/build/1st/irker-2.18+dfsg'
xmlto html-nochunks irkerd.xml
xmlto man irkerd.xml
xmlto html-nochunks irkerhook.xml
xmlto man irkerhook.xml
xmlto html-nochunks irkerhook.xml
xmlto man irk.xml
/bin/cp: cannot create regular file 
'/build/1st/irker-2.18+dfsg/irkerhook.html': File exists
Makefile:22: recipe for target 'irkerhook.html' failed
make[2]: *** [irkerhook.html] Error 1


This seems to be caused by a cut'n'paste error in the Makefile:

irkerhook.1: irkerhook.xml
xmlto man irkerhook.xml
irkerhook.html: irkerhook.xml
xmlto html-nochunks irkerhook.xml

irk.1: irk.xml
xmlto man irk.xml
irk.html: irk.xml
xmlto html-nochunks irkerhook.xml
^

Bug#864611: config-package-dev: transform: let users pick local files as source

[Luca Boccassi]

Package: config-package-dev
Version: 5.1.2
Severity: wishlist
Tags: patch

Dear Maintainer,

I have a use case where I would like to transform and displace a file
shipped from the same upstream source, so that 2 binary packages (that
conflict with each other) can be built from the same repository without
having to keep local copies.

The first check, dpkg-divert --truename, immediately fails if the path
is not absolute. A simple patch is inlined.

Kind regards,
Luca Boccassi


From 15864748b3170217ed0665e3cc2716c1fdf6754c Mon Sep 17 00:00:00 2001
From: Luca Boccassi 
Date: Sun, 11 Jun 2017 16:29:49 +0100
Subject: [PATCH] transform: let users pick local files as source

In some case it's desirable to use a local file as the source of the
transform operation. For example, an upstream file from the same
repository that could be sourced at built time.
Skip dpkg checks on the source file if it does not start with /
---
 dh_configpackage | 9 -
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/dh_configpackage b/dh_configpackage
index 942766f..e76048c 100755
--- a/dh_configpackage
+++ b/dh_configpackage
@@ -369,9 +369,13 @@ foreach my $package (@{$dh{DOPACKAGES}}) {
 my $file = shift @$line;
 $file =~ s|^/?|/|;
 my $source;
+my $source_is_local = 0;
 if (@$line[0] =~ /^

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

Bug#864610: ITP: php-netscape-bookmark-parser -- generic Netscape bookmark parser

[James Valleroy]

Package: wnpp
Severity: wishlist
Owner: James Valleroy 

* Package name: php-netscape-bookmark-parser
  Version : 2.0.2
  Upstream Author : Kafene , VirtualTam 
 
* URL : https://github.com/shaarli/netscape-bookmark-parser
* License : MIT Expat
  Programming Lang: PHP
  Description : generic Netscape bookmark parser

This library provides a generic NetscapeBookmarkParser class that is
able of parsing Netscape bookmarks as exported by common Web browsers
and bookmarking services.

This is a dependency for shaarli. I plan to maintain it within the
freedombox-pkg-team.

Bug#864604: usb-modeswitch: USB 3G modem is detected twice as "USB Mass Storage"

[Josua Dietze]

Am 11.06.2017 um 14:44 schrieb Teemu Likonen:

Extra info: If I run manually
 modprobe usbserial vendor=0x1c9e product=0x9801
the 3G modem starts working.


This is a clear indication that usb_modeswitch is working as intended. There 
is nothing it can change in that respect, the modem mode is reached.


It is in fact standard behaviour of a USB modem to provide either only its 
MicroSD slot or both the slot and the install storage AFTER the mode switch, 
in addition to the modem ports. So your's is not behaving unusually at all.


It looks like your modem's USB product ID is not yet included in the modem 
driver ("option.c") in kernel version 4.9.0 (and indeed not in any more recent 
version).
Previous usb_modeswitch versions took care of loading the driver 'manually' 
when it didn't bind so you probably were not aware of that issue.


If you had had a look into the system log you would have seen this:

usb_modeswitch: add device ID 1c9e:9801 to driver "option"
usb_modeswitch: please report the device ID to the Linux USB developers!

You are not to blame of course - why should you look if everything worked? :-)

Bottom line:
The product ID 0x9801 needs to be added to the serial driver of the kernel.

For a quick fix you can do what usb_modeswitch did previously:
# modprobe -v option
# echo "1c9e 9801" > /sys/bus/usb-serial/drivers/option1/new_id

You can put this into a script and let it be called by udev automatically if 
your modem is plugged. Put this below the first "ACTION" line in 
/lib/udev/rules.d/40-usb_modeswitch.rules:


ATTR{idVendor}=="1c9e", ATTR{idProduct}=="9801", RUN+="/path/to/your/script"


Good luck,
Josua Dietze

Bug#864457: Bug#864536: missing kernel modules in D-I sd-card images

[Cyril Brulebois]

Hey debian-kernel,

Karsten Merker  (2017-06-11):
> as we appear to have the same underlying problem in bugs 864536,
> 864457 and 856111, I personally think that adding the modules
> necessary for i2c-support in d-i is worth another upload before
> r0, provided the current diagnosis in 864457 is correct and
> handling the additional work due to this is doable for everybody
> involved.
> 
> If the current diagnosis in 864457 is correct, not providing i2c
> modules AFAICS will not only break d-i completely on the
> Firefly-RK3288 (bug 864536) but also the following usecases:
> 
> - all hd-media and thereby all offline installs
> - all installations to USB-connected harddisks
> - all non-serial-console installations due to non-working
>   USB keyboard support
> 
> on all systems that use the AXP20x series of powermanagement
> controllers, which is a significant part of the armhf platforms
> that we provide installer images for:
> 
> - A10-OLinuXino-Lime
> - A20-OLinuXino-Lime
> - A20-OLinuXino-Lime2
> - A20-OLinuXino-MICRO
> - A20-Olimex-SOM-EVB
> - BananaPi
> - BananaPro
> - Cubieboard
> - Cubieboard2
> - Cubietruck
> - Lamobo_R1
> - orangepi_plus
> - pcDuino
> - pcDuino3
> 
> AIUI, the following changes to the kernel package would be
> needed:
> 
> - add an i2c-modules config for armhf which includes the generic
>   i2c-modules config plus the i2c-mv64xxx and i2c-rk3x modules 
> - add the axp20x_usb_power module to the armhf kernel-image config
>   to address the specifics of bug #856111 (see Ben Hutchings' notes
>   at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856111#54)
> 
> As that effectively only makes the same modules that we already
> install on all armhf systems also available inside the d-i
> environment, the chances of causing a regression by this change
> are rather low.  Size constraints are AFAIK not a problem on
> armhf (in contrast to armel), so the aforementioned changes
> should be rather low-risk.

Based on Karsten's input, I'm now rather convinced that adding a udeb
before r0 would be the best way to deal with it. Even if some other
modules are missing inside, we still have a chance of fixing this in a
point release by just adding a few .ko files to an already existing
udeb, instead of introducing it during a point release.

I've just checked with Niels, and this looks like a sane approach from a
release team point of view.

Do you know if you'll be able to perform a new linux upload from the
stretch branch in a relatively near future? The sooner we get fixes, the
more we can run tests, and the saner release people will be. ;)

Please let me know if I can help.


KiBi.


signature.asc
Description: Digital signature

Bug#864609: postfix install fails on stretch

[Juha Heinanen]

Niels Thykier writes:

> > Setting up postfix (3.1.4-7) ...
> > [...]
> > Created symlink /etc/systemd/system/multi-user.target.wants/postfix.service 
> > → /lib/systemd/system/postfix.service.
> > setting myhostname=jessie-8.0 in /etc/postfix
>  ^^
> 
> That looks like an invalid hostname.

Perhaps it is and therefore (as I explained in previous message), I
changed hostname to 'jessie'.

> Can you give me the output of:
> 
>  * hostname -s
>  * hostname -f

# hostname -s
jessie
# hostname -f
hostname: Name or service not known

> I suspect you can get postfix to work by editing the configuration files
> in /etc/postfix and setting "myhostname" to a valid hostname.  Though, I
> don't remember offhand if myhostname wants just the shortname or the
> fully qualified domain name (FQDN).

This is a test upgrade from jessie to stretch, so there is no hurry to
get postfix working.

My point still is, this is the first Debian release in my quite long
history, where postfix does not install without manual configuration.
Until now, there has been some working defaults.

-- Juha

Bug#864580: [Python-modules-team] Bug#864580: Updating the python-twitter Uploaders list

[Sandro Tosi]

On Sat, Jun 10, 2017 at 5:25 PM, Tobias Frost  wrote:
> Koichi Akabe  has not been working on
> the python-twitter package for quite some time.
>
> We are tracking their status in the MIA team and would like to ask you
> to remove them from the Uploaders list of the package so we can close
> that part of the file.

i'm using the `twitter` module in the tweet dput-ng plugin, so i'm
going to take this over

-- 
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#864609: postfix install fails on stretch

[Niels Thykier]

Control: tags -1 moreinfo

On Sun, 11 Jun 2017 17:24:33 +0300 Juha Heinanen  wrote:
> Package: postfix
> Version: 3.1.4-7
> 
> Upgrade from Jessie to Stretch didn't complete, but failed at postfix:
> 

Hi Juha,

Thanks for reporting this bug.

I have a question for more:

> Setting up postfix (3.1.4-7) ...
> [...]
> Created symlink /etc/systemd/system/multi-user.target.wants/postfix.service 
> → /lib/systemd/system/postfix.service.
> setting myhostname=jessie-8.0 in /etc/postfix
 ^^

That looks like an invalid hostname.

Can you give me the output of:

 * hostname -s
 * hostname -f


> [...]
> 
> I then tried by purging postfix and installing it again, but that didn't

I suspect you can get postfix to work by editing the configuration files
in /etc/postfix and setting "myhostname" to a valid hostname.  Though, I
don't remember offhand if myhostname wants just the shortname or the
fully qualified domain name (FQDN).

Thanks,
~Niels

Bug#863366: RFA: pylint-common -- Pylint plugin for the standard Python library

[陳昌倬]

Control: retitle -1 ITA: pylint-common -- Pylint plugin for the standard Python 
library
Control: owner -1 !

On Thu, May 25, 2017 at 09:15:21PM +0200, Daniel Stender wrote:
> Package: wnpp
> Severity: normal
> 
> I request an adopter for the pylint-common package [1].

I will adopt this package.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#864609: postfix install fails on stretch

[Juha Heinanen]

Package: postfix
Version: 3.1.4-7

Upgrade from Jessie to Stretch didn't complete, but failed at postfix:

Setting up postfix (3.1.4-7) ...
Installing new version of config file /etc/init.d/postfix ...
Installing new version of config file /etc/network/if-down.d/postfix ...
Installing new version of config file /etc/network/if-up.d/postfix ...
Installing new version of config file /etc/postfix/post-install ...
Installing new version of config file /etc/postfix/postfix-files ...
Installing new version of config file /etc/postfix/postfix-script ...
Installing new version of config file /etc/ppp/ip-down.d/postfix ...
Installing new version of config file /etc/ppp/ip-up.d/postfix ...
Installing new version of config file /etc/resolvconf/update-libc.d/postfix ...
Created symlink /etc/systemd/system/multi-user.target.wants/postfix.service → 
/lib/systemd/system/postfix.service.
setting myhostname=jessie-8.0 in /etc/postfix
setting explicit chroot on /etc/postfix:smtp/inet/chroot
setting explicit chroot on /etc/postfix:pickup/unix/chroot
setting explicit chroot on /etc/postfix:cleanup/unix/chroot
setting explicit chroot on /etc/postfix:tlsmgr/unix/chroot
setting explicit chroot on /etc/postfix:rewrite/unix/chroot
setting explicit chroot on /etc/postfix:bounce/unix/chroot
setting explicit chroot on /etc/postfix:defer/unix/chroot
setting explicit chroot on /etc/postfix:trace/unix/chroot
setting explicit chroot on /etc/postfix:verify/unix/chroot
setting explicit chroot on /etc/postfix:flush/unix/chroot
setting explicit chroot on /etc/postfix:smtp/unix/chroot
setting explicit chroot on /etc/postfix:relay/unix/chroot
setting explicit chroot on /etc/postfix:showq/unix/chroot
setting explicit chroot on /etc/postfix:error/unix/chroot
setting explicit chroot on /etc/postfix:retry/unix/chroot
setting explicit chroot on /etc/postfix:discard/unix/chroot
setting explicit chroot on /etc/postfix:lmtp/unix/chroot
setting explicit chroot on /etc/postfix:anvil/unix/chroot
setting explicit chroot on /etc/postfix:scache/unix/chroot

Postfix (main.cf) is now set up with the changes above.  If you need to make 
changes, edit /etc/postfix/main.cf (and others) as needed.  To view Postfix 
configuration values, see postconf(1).

After modifying main.cf, be sure to run 'service postfix reload'.

Running newaliases
newaliases: warning: valid_hostname: numeric hostname: 0
newaliases: fatal: file /etc/postfix/main.cf: parameter mydomain: bad parameter 
value: 0
dpkg: error processing package postfix (--configure):
 subprocess installed post-installation script returned error exit status 75
dpkg: dependency problems prevent configuration of bsd-mailx:
 bsd-mailx depends on default-mta | mail-transport-agent; however:
  Package default-mta is not installed.
  Package exim4-daemon-light which provides default-mta is not installed.
  Package mail-transport-agent is not installed.
  Package postfix which provides mail-transport-agent is not configured yet.
  Package exim4-daemon-light which provides mail-transport-agent is not 
installed.

dpkg: error processing package bsd-mailx (--configure):
 dependency problems - leaving unconfigured

I then tried by purging postfix and installing it again, but that didn't
help either:

Unpacking postfix (3.1.4-7) ...
Processing triggers for systemd (232-25) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for rsyslog (8.24.0-1) ...
Setting up postfix (3.1.4-7) ...
Created symlink /etc/systemd/system/multi-user.target.wants/postfix.service → 
/lib/systemd/system/postfix.service.
Adding group `postfix' (GID 117) ...
Done.
Adding system user `postfix' (UID 110) ...
Adding new user `postfix' (UID 110) with group `postfix' ...
Not creating home directory `/var/spool/postfix'.
Creating /etc/postfix/dynamicmaps.cf
Adding group `postdrop' (GID 118) ...
Done.
setting myhostname: jessie-8.0
setting alias maps
setting alias database
setting myorigin
setting destinations: $myhostname, test.tutpro.com, jessie-8.0, localhost.0, 
localhost
setting relayhost: 
setting mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
setting mailbox_command
setting mailbox_size_limit: 0
setting recipient_delimiter: +
setting inet_interfaces: all
setting inet_protocols: all

Postfix (main.cf) is now set up with a default configuration.  If you need to 
make changes, edit /etc/postfix/main.cf (and others) as needed.  To view 
Postfix configuration values, see postconf(1).

After modifying main.cf, be sure to run 'service postfix reload'.

Running newaliases
newaliases: warning: valid_hostname: numeric hostname: 0
newaliases: fatal: file /etc/postfix/main.cf: parameter mydomain: bad parameter 
value: 0
dpkg: error processing package postfix (--configure):
 subprocess installed post-installation script returned error exit status 75
Processing triggers for systemd (232-25) ...
Processing triggers for rsyslog (8.24.0-1) ...
Errors were encountered while processing:
 postfix
E: Sub-process /usr/bin/dpkg returned an 

Bug#864608: RFP: python-digitalocean -- Python bindings for the DigitalOcean API

[Daniel Stender]

Package: wnpp
Severity: wishlist

* Package name: python-digitalocean
  Version : 1.10.0
  Upstream Author : Lorenzo Setale 
* URL : https://github.com/koalalorenzo/python-digitalocean
* License : LGPL-3.0
  Programming Lang: Python
  Description : Python bindings for the DigitalOcean API

These are Python bindings for the API of the cloud provider DigitalOcean.
With that, actions otherwise performed on the web interface could be
performed like creating/shutdown/delete virtual machines (droplets) etc.

I would sponsor this, please just contact me if you have a package that
builds.

Thanks,
Daniel Stender

Bug#864607: noisy mariadb-server-10.1 installation

[Juha Heinanen]

Package: mariadb-server-10.1
Version: 10.1.23-9+deb9u1

During 'apt-get dist-upgrade' from jessie to stretch, this got printed
to console:

Setting up mariadb-common (10.1.23-9+deb9u1) ...
Selecting previously unselected package mariadb-server-10.1.
(Reading database ... 72727 files and directories currently installed.)
Preparing to unpack .../mariadb-server-10.1_10.1.23-9+deb9u1_amd64.deb ...
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at 
/usr/share/perl5/Debconf/Question.pm line 72.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm line 
30.

Please fix so that the deprecated info does not get printed.  If every
package would be as noisy, user couldn't comprehend anything about what
is going on.

-- Juha

Bug#864605: new upstream version (6.11)

[Daniel Baumann]

Package: nodejs
Severity: wishlist
Tags: experimental

Hi,

it would be nice if you could upgrade to the current 6.x upstream in
experimental (6.10 is in the archive, 6.11 was released some days ago).

Regards,
Daniel

Bug#864604: usb-modeswitch: USB 3G modem is detected twice as "USB Mass Storage"

[Teemu Likonen]

Package: usb-modeswitch
Version: 2.5.0+repack0-1
Severity: normal

Dear Maintainer,

I have a Telewell TW-3G HSPA+ modem (usb). When it is plugged the device
is identified as usb mass storage. See the kernel log below (journalctl
-fk):

2017-06-11T12:29:52+ mithlond kernel: usb 1-7: new high-speed USB device 
number 15 using xhci_hcd
2017-06-11T12:29:53+ mithlond kernel: usb 1-7: New USB device found, 
idVendor=1c9e, idProduct=98ff
2017-06-11T12:29:53+ mithlond kernel: usb 1-7: New USB device strings: 
Mfr=3, Product=2, SerialNumber=4
2017-06-11T12:29:53+ mithlond kernel: usb 1-7: Product: USB Modem
2017-06-11T12:29:53+ mithlond kernel: usb 1-7: Manufacturer: USB Modem
2017-06-11T12:29:53+ mithlond kernel: usb 1-7: SerialNumber: 
1234567890ABCDEF
2017-06-11T12:29:53+ mithlond kernel: usb-storage 1-7:1.0: USB Mass Storage 
device detected
2017-06-11T12:29:53+ mithlond kernel: scsi host4: usb-storage 1-7:1.0
2017-06-11T12:29:53+ mithlond kernel: usb-storage 1-7:1.1: USB Mass Storage 
device detected
2017-06-11T12:29:53+ mithlond kernel: scsi host5: usb-storage 1-7:1.1

Then usb-modeswitch (I presume) disconnects the device (idProduct=98ff)
and immediately connects it again as another device (idProduct=9801)
which is supposed to be the actual 3G modem. See the kernel log below:

2017-06-11T12:29:53+ mithlond kernel: usb 1-7: USB disconnect, device 
number 15
2017-06-11T12:29:54+ mithlond kernel: usb 1-7: new high-speed USB device 
number 16 using xhci_hcd
2017-06-11T12:29:54+ mithlond kernel: usb 1-7: New USB device found, 
idVendor=1c9e, idProduct=9801
2017-06-11T12:29:54+ mithlond kernel: usb 1-7: New USB device strings: 
Mfr=3, Product=2, SerialNumber=4
2017-06-11T12:29:54+ mithlond kernel: usb 1-7: Product: USB Modem
2017-06-11T12:29:54+ mithlond kernel: usb 1-7: Manufacturer: USB Modem
2017-06-11T12:29:54+ mithlond kernel: usb 1-7: SerialNumber: 
1234567890ABCDEF
2017-06-11T12:29:54+ mithlond kernel: usb-storage 1-7:1.4: USB Mass Storage 
device detected
2017-06-11T12:29:54+ mithlond kernel: scsi host4: usb-storage 1-7:1.4
2017-06-11T12:29:54+ mithlond kernel: usb-storage 1-7:1.5: USB Mass Storage 
device detected
2017-06-11T12:29:54+ mithlond kernel: scsi host5: usb-storage 1-7:1.5
2017-06-11T12:30:04+ mithlond kernel: scsi 5:0:0:0: Direct-Access 
USBModem Disk 2.31 PQ: 0 ANSI: 2
2017-06-11T12:30:04+ mithlond kernel: scsi 4:0:0:0: CD-ROM
USBModem Disk 2.31 PQ: 0 ANSI: 2
2017-06-11T12:30:04+ mithlond kernel: sd 5:0:0:0: Attached scsi generic sg3 
type 0
2017-06-11T12:30:04+ mithlond kernel: sr 4:0:0:0: [sr1] scsi-1 drive
2017-06-11T12:30:04+ mithlond kernel: sd 5:0:0:0: [sdc] Attached SCSI 
removable disk
2017-06-11T12:30:04+ mithlond kernel: sr 4:0:0:0: Attached scsi CD-ROM sr1
2017-06-11T12:30:04+ mithlond kernel: sr 4:0:0:0: Attached scsi generic sg4 
type 5

But there is the problem: this new device is still a usb-storage ("USB
Mass Storage device detected"). Network Manager can't see the 3G modem.

This all worked fine with Debian 8 (Jessie) but broke in Debian 9
(Stretch).


Extra info: If I run manually

modprobe usbserial vendor=0x1c9e product=0x9801

the 3G modem starts working.


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

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

Versions of packages usb-modeswitch depends on:
ii  libc62.24-11
ii  libjim0.76   0.76-2+b1
ii  libusb-1.0-0 2:1.0.21-1
ii  usb-modeswitch-data  20170120-1

usb-modeswitch recommends no packages.

Versions of packages usb-modeswitch suggests:
ii  comgt   0.32-3
pn  wvdial  

-- no debconf information

Bug#864603: gufw does not launch

[jensome]

Package: gufw
Version: 17.04.1-1.1
Severity: important

Dear Maintainer,

Launching gufw on debian stretch does not work (tested on gnome desktop)

When started via terminal the messages below appear (after the root password 
was requested):
(the same error appears when gufw is started directly as root)

$ gufw
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: 
Connection refused
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: 
Connection refused

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:2743): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:2743): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed
/usr/bin/gufw-pkexec: line 13:  2743 Segmentation fault  python3 
${LOCATIONS[${i}]} $1



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

Bug#863596: mytop can't installed

[Werner Detter]

Hi,

> mytop is now part of mariadb-client-10.1, therefore the mytop package
> doesn't seem to make much sense in stretch.

I don't know which source of mytop is included in mariadb-client-10.1
and cannot estimate if the standalone package of mytop makes sense or
not in stretch. I assume the Maintainers of MariaDB do things right
so I won't look further into this.

Cheers,
Werner

Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Bill Allombert]

On Sun, Jun 11, 2017 at 11:13:05AM +0200, Cyril Brulebois wrote:
> Package: upgrade-reports
> Severity: critical
> Justification: makes upgrade from stable abort
> 
> [ X-D-Cc:
>   debian-rele...@lists.debian.org
>   pkg-java-maintain...@lists.alioth.debian.org
>   pkg-gnome-maintain...@lists.alioth.debian.org ]
> 
> Hi,
> 
> Regression spotted by Pere in some debian-edu job, but also seen since
> the 2nd of June in normal gnome chroot installation then upgrade from
> jessie to stretch:
>   
> https://jenkins.debian.net/view/edu_devel/job/chroot-installation_jessie_install_education-desktop-gnome_upgrade_to_stretch/
>   
> https://jenkins.debian.net/job/chroot-installation_jessie_install_gnome_upgrade_to_stretch/
> 
> I've managed to reproduce it locally with basically a debootstrap of
> jessie, installation of gnome, then switch sources.list from jessie to
> stretch, then update & upgrade & dist-upgrade.
> 
> I've bisected the archive using snapshot.debian.org and found out:
>  - 20170601T212625Z = last timestamp found to be OK;
>  - 20170602T033358Z = first timestamp to be KO.

For what it is worth, according to

a circular dependency between ca-certificates-java and
openjdk-8-jre-headless has been added on Thu Jun  1 01:02:00 CEST 2017

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#864602: Double free or corruption error/segfault when trying to restore files from a specific partition

[Andoru]

Package: extundelete
Version: 0.2.4-1
Severity: important
Tags: upstream


I've tried to restore files from a specific partition (ext4), which worked
previously (did this a couple of months ago), but now it seems that I can
only get it to exit with this:
> *** Error in `extundelete': double free or corruption (!prev):
0x01a95000 ***

I've tried recovering from other partitions on the same system (also ext4),
and they work as expected...
At first, since I attempted this from a LMDE 2 Live CD session, I thought
it might be a bug in the specific package that was available, but then I
switched to Ubuntu and to Arch LiveCDs (here's the arch package page:
https://www.archlinux.org/packages/community/x86_64/extundelete/), and they
both gave me the same results, except that at times it segfaults instead of
returning the above error.
Here's the command I used:
> $ sudo extundelete --restore-directory /user/bin/storage /dev/sdb1

Also used the --restore-all and --restore-file, and both gave me the same
result.

So after all of this I gather that the problem is with the partition I'm
trying to recover specifically, and that this is a upstream issue.
Now I know that I should've written this to the package maintainers, but
their mailing list seems dead for quite a while, and I thought you as
maintainers might have a more direct way to contact the developers.
Regardless, I will try to post this bug on their mailing list too.

Here's the superblock info of the partition in case it helps:
Let me know if you need any additional info.

$ sudo extundelete /dev/sdb1

No action specified; implying --superblock.
NOTICE: Extended attributes are not restored.
Inodes count: 61054976
Blocks count: 244190208
Reserved blocks count: 0
Free blocks count: 31904860
Free inodes count: 60920436
First Data Block: 0
Block size: 4096
Fragment size: 4096
# Blocks per group: 32768
# Fragments per group: 1
# Inodes per group: 8192
Mount time: 1497147585
Write time: 1497147585
Mount count: 73
Maximal mount count: -1
Magic signature: 61267
File system state: 1
Behaviour when detecting errors: 1
minor revision level: 0
time of last check: 1475524694
max. time between checks: 0
OS: 0
Revision level: 1
Default uid for reserved blocks: 0
Default gid for reserved blocks: 0
First non-reserved inode: 11
size of inode structure: 256
block group # of this superblock: 0
compatible feature set: 60
incompatible feature set: 706
readonly-compatible feature set: 1131
128-bit uuid for volume: ad3c96f09c8346308a497f3f17d1f2f2
For compression: 0
Nr to preallocate for dirs: 0
Per group table for online growth: 1024
uuid of journal superblock: 
inode number of journal file: 8
device number of journal file: 0
start of list of inodes to delete: 0
HTREE hash seed: 1423a337854ef9fc32efd09bbb4ea8ee
Default hash version to use: 1
Default type of journal backup: 1
First metablock group: 0
When the filesystem was created: 1470435884
Compatible feature set: HAS_JOURNAL EXT_ATTR RESIZE_INODE DIR_INDEX
Incompatible feature set: FILETYPE
Read only compatible feature set: SPARSE_SUPER LARGE_FILE



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

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

Versions of packages extundelete depends on:
ii  e2fslibs1.42.12-2+b1
ii  libc6   2.19-18+deb8u7
ii  libcomerr2  1.42.12-2+b1
ii  libgcc1 1:4.9.2-10
ii  libstdc++6  4.9.2-10

extundelete recommends no packages.

extundelete suggests no packages.

-- no debconf information

Bug#864601: Missing 'HuC' firmware on Intel Kabylake/Skylake/Broxton

[Yuri D'Elia]

Package: firmware-misc-nonfree
Version: 20161130-3
Severity: normal

The HuC firmware is currently missing for the i915 module:

W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for 
module i915

It is currently available on https://01.org/linuxgraphics/downloads/firmware

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

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

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ii  initramfs-tools  0.130

Bug#864566: [DRE-maint] Bug#864566: librarian-puppet FTBFS in unstable: ERROR: Test "ruby2.3" failed. Exiting.

[Sebastien Badia]

owner 864566 !
tags 864566 + pending confirmed
thanks

Hi Adrian,

Thanks for the bug report, I'm currently working on it (ruby-puppet-forge, r10k,
librarian-puppet and ruby-semantic-puppet)

Cheers,

Seb


signature.asc
Description: PGP signature

Bug#864544: libgetopt-long-descriptive-perl: option value : and :+ processing are very broken

[Graham Cobb]

On 10/06/17 22:21, Dominic Hargreaves wrote:
> Unfortunately we won't be able to fix either of these issues before
> stretch releases because we're past the last upload date, even if 
> fixes were available.
> 
> Given the last few releases of Getopt::Long have contained various
> regressions and regression fixes I'd also be a bit wary of trying to
> fix this in a stable point release, and indeed of diving in to try 
> and fix the issue.
> 
> This is all a bit unfortunate but I'm not sure there is a solution
> at this point.

I wonder if a solution for the immediate future might be to re-package
the same version of Getopt::Long as available in (the latest update to)
Jessie (which seems to be 2.42)? Obviously this would be missing some
number of other bug fixes but it would, at least, not be a regression
from Jessie.

As you say, it is too late to change the stretch release content, but
that version could be made available in sid and in testing when it is
opened up again (so fairly easily accessible to anyone who hits the
bug), and could be made available as a stretch backport and in a stretch
update release. After that is available, we could go back to repackaging
the upstream version (which would hopefully include both fixes by then)
and get that into testing to shake it down.

Or are there too many important changes to Getopt::Long since 2.42 to
consider reverting?

I am no perl expert but if I can help at all (for example with testing)
please let me know.

Bug#864600: linux-image-4.9.0-3-amd64: Audio not audible on Intel Corporation C610/X99 series

[Sean Clarke]

Package: src:linux
Version: 4.9.30-1
Severity: normal
Tags: upstream

Dear Maintainer,
on a fresh Stretch install on a Alienware Area 51 R2 audio is not working
from the built in sound card.

If I increase settings to max aidio is very very faintly heard, but below
whisper levels.

I have tweaked levels with alsamixer and the system is able to detect headphone
add/remove and line out add/remove so it seems to be semi operational, however
try as I might I cannot get audio to play.

Some additional info:

also-info available here:
http://www.alsa-project.org/db/?f=1705b025353cc272db1497d87d06dbf79220c922


aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: CA0132 Analog [CA0132 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: CA0132 Digital [CA0132 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

NOTE: I have also disabled all HDMI outputs in case there was some confusion.


lspci -nn | grep -i audio
00:1b.0 Audio device [0403]: Intel Corporation C610/X99 series chipset HD Audio
Controller [8086:8d20] (rev 05)
03:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio
Controller [10de:10f0] (rev a1)


I have also installed the non free and intel audio firmware packages

dmesg | grep snd
[7.389818] snd_hda_intel :00:1b.0: enabling device ( -> 0002)
[7.390213] snd_hda_intel :03:00.1: Disabling MSI
[7.390254] snd_hda_intel :03:00.1: Handle vga_switcheroo audio client
[7.406491] snd_hda_codec_ca0132 hdaudioC0D0: autoconfig for CA0132:
line_outs=1 (0xb/0x0/0x0/0x0/0x0) type:line
[7.406496] snd_hda_codec_ca0132 hdaudioC0D0:speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
[7.406500] snd_hda_codec_ca0132 hdaudioC0D0:hp_outs=2
(0x10/0xf/0x0/0x0/0x0)
[7.406503] snd_hda_codec_ca0132 hdaudioC0D0:mono: mono_out=0x0
[7.406506] snd_hda_codec_ca0132 hdaudioC0D0:dig-out=0xc/0x0
[7.406508] snd_hda_codec_ca0132 hdaudioC0D0:inputs:
[7.406512] snd_hda_codec_ca0132 hdaudioC0D0:  Mic=0x12
[7.406515] snd_hda_codec_ca0132 hdaudioC0D0:  Line=0x11
[7.420705] snd_hda_intel :00:1b.0: firmware: direct-loading firmware
ctefx.bin
[9.032404] snd_hda_codec_ca0132 hdaudioC0D0: ca0132 DSP downloaded and
running
[   10.044261] snd_hda_intel :00:1b.0: firmware: direct-loading firmware
ctefx.bin
[   11.516055] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 71
[   11.648060] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 8
[   11.872154] snd_hda_codec_ca0132 hdaudioC0D0: ca0132 DSP downloaded and
running
[   11.908057] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 12
[   11.980051] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 3
[   12.304017] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 17
[   27.504065] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 17
[   27.576057] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 3
[   27.648055] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 3
[   28.652055] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 69
[   28.784053] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 8
[   29.056048] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 13
[   29.104042] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 1
[   29.424050] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 17





-- Package-specific info:
** Version:
Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-1 (2017-06-04)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 
root=UUID=b159e08b-0777-4a63-86c9-a4ca32465712 ro quiet

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[8.272287] usb 4-5.4: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[8.273142] hub 4-5.4:1.0: USB hub found
[8.273168] hub 4-5.4:1.0: 4 ports detected
[8.352726] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[8.353366] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[8.365734] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[8.368089] usb 3-9.4: new high-speed USB device number 7 using xhci_hcd
[8.484332] usb 3-9.4: New USB device found, idVendor=0451, idProduct=8142
[8.484335] usb 3-9.4: New USB device strings: Mfr=0, Product=0, 
SerialNumber=1
[8.484337] usb 3-9.4: SerialNumber: F70D0841F0AD
[

Bug#864599: python-minimal: pyclean, pycompile and pyversions: Error when /usr/bin/python is python3

[Piotr Ozarowski]

Control: severity 864599 wishlist

[Matthias Julius, 2017-06-11]
> After setting /usr/bin/python to point to python3 via alternatives the
> next update of debconf failed with:

/usr/bin/python is not something you should be changing via alternatives

>   File "/usr/bin/pyclean", line 63
> except (IOError, OSError), e:
>  ^
> SyntaxError: invalid syntax

if you want Python 3 version of these scripts, use py3compile / py3clean

> #! /usr/bin/python2
> 
> helped. They are apparently not compatible with python3.

I'm not a fan of python2 - we'll not change /usr/bin/python to
something else than Python 2.X so there's no need to change shebangs.

/usr/bin/python2 symlink is provided only to workaround damage done by
one other distro.

Bug#864599: python-minimal: pyclean, pycompile and pyversions: Error when /usr/bin/python is python3

[Matthias Julius]

Package: python-minimal
Version: 2.7.13-2
Severity: normal

Dear Maintainer,

After setting /usr/bin/python to point to python3 via alternatives the
next update of debconf failed with:

  File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
 ^
SyntaxError: invalid syntax

and

  File "/usr/bin/pycompile", line 35, in 
from debpython.version import SUPPORTED, debsorted, vrepr, \
  File "/usr/share/python/debpython/version.py", line 24, in 
from ConfigParser import SafeConfigParser
ImportError: No module named 'ConfigParser'

pyversions also fails with:

  File "/usr/bin/pyversions", line 20
except IOError, msg:
  ^
SyntaxError: invalid syntax


Changing the first line of all scripts to

#! /usr/bin/python2

helped. They are apparently not compatible with python3.

Best regards,
Matthias


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

Kernel: Linux 4.9.0-2-amd64 (SMP w/1 CPU core)
Shell: /bin/sh linked to /bin/dash
Init:  systemd (via /run/systemd/system)

Versions of packages python-minimal depends on:
ii  dpkg   1.18.24
ii  python2.7-minimal  2.7.13-2

Versions of packages python-minimal recommends:
ii  python 2.7.13-2

python-minimal suggests no packages.

-- debconf information excluded

Bug#864590: unblock: aptitude/0.8.8-1 (pre-approval)

[Manuel A. Fernandez Montecelo]

2017-06-11 10:29 GMT+02:00 Niels Thykier :
>
> Unfortunately, we are past the deadline for anything but major bugs.
> Your changes look fine and some of them may be acceptable for a stable
> update.  Please consider requesting one with the SRMs after the initial
> stretch release.

All right, I will do that.  Thanks!


-- 
Manuel A. Fernandez Montecelo 

Bug#864598: python-reportbug: logic error in send_report()

[g1]

Package: python-reportbug
Version: 6.6.3
Severity: normal

The condition 

elif outfile or not ((mta and os.path.exists(mta)) or smtphost):

in /usr/lib/python2.7/dist-packages/reportbug/submit.py (line 315) is true
also if outfile is None and mta is set to a non-existent path.

The following line 

msgname = os.path.expanduser(outfile) or ('/var/tmp/%s.bug' % package)

triggers an exception when os.path.expanduser is called with outfile=None
as its argument.

e.g., with .reportbugrc containing 

reportbug_version "6.6.3"
mode standard
ui text
realname "john smith"
email "john.sm...@example.com"
mta "~/bin/mta-wrapper"

submitting bug reports fails with

Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2211, in 
main()
  File "/usr/bin/reportbug", line 1081, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 2203, in user_interface
self.options.envelopefrom)
  File "/usr/lib/python2.7/dist-packages/reportbug/submit.py", line 316, in 
send_report
elif outfile or not ((mta and os.path.exists(mta)) or smtphost):
  File "/usr/lib/python2.7/posixpath.py", line 261, in expanduser
if not path.startswith('~'):

because

- mta is true
- os.path.exists(mta) is false (tilde expansion is not performed before testing)
- smtphost is false

so the block is entered with outfile=None

Best regards,
g.

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

Kernel: Linux 3.16.0-4-586
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages python-reportbug depends on:
ii  apt   1.0.9.8.4
ii  python-debian 0.1.27
ii  python-debianbts  1.12
pn  python:any

python-reportbug recommends no packages.

Versions of packages python-reportbug suggests:
ii  reportbug  6.6.3

-- no debconf information

Bug#859787: experimental versus unstable

[Geert Stappers]

On Sun, Jun 11, 2017 at 11:44:40AM +0200, Geert Stappers wrote:
> On Sat, Jun 10, 2017 at 10:43:25PM +0200, Alexandre Rossi wrote:
> > Geert Stappers:
> > >
> > > Why the request for uploading to 'experimental'?
> > 
> > With my understanding of the freeze policy, for a package that is in
> > testing, one should upload to unstable only version fixing RC bugs.
> > Although the release is near, I'm sticking to the rules.
> 
> Good to know:
> * What is uploaded to experimental, stays in experimental.
> * There is no automatic "elevation" from experimental to unstable.
> * What is uploaded to unstable elevates to testing,
>   but not during a freeze. The freeze block prevents it.
> * To get elevation from unstable to testing during freeze
>   starts with a unblock request.
> * A valid reason for honouring a unblock request
>   is a fix for a release critical bug.
> * What in testing is elavates into stable (at "release").
> * Uploads to experimental don't close bugs, uploads to unstable do.
> 
> Upload to experimental done.
> 

The automatic email from FTP-masters has

| Format: 1.8
| Date: Fri, 09 Jun 2017 07:19:27 +0200
| Source: davmail
| Binary: davmail
| Architecture: source all
| Version: 4.8.0.2479-1
| Distribution: unstable
| Urgency: low
| Maintainer: Alexandre Rossi 
| Changed-By: Alexandre Rossi 
| Description:
|  davmail- POP/IMAP/SMTP/CalDav/LDAP to Microsoft Exchange gateway
| Closes: 859787 863849
| Changes:
|  davmail (4.8.0.2479-1) experimental; urgency=low
|  .
|* New upstream version (Closes: #859787)
|* Refresh patches
|* Drop javamail compatibility patch (fixed upstream)
|* Depend on headless JRE (Closes: #863849)

Seems like I did an accidental upload to unstable.
My plan was to upload to experimental as Alexandre requested.

Sorry.


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Niels Thykier]

Cyril Brulebois:
> Package: upgrade-reports
> Severity: critical
> Justification: makes upgrade from stable abort
> 
> [ X-D-Cc:
>   debian-rele...@lists.debian.org
>   pkg-java-maintain...@lists.alioth.debian.org
>   pkg-gnome-maintain...@lists.alioth.debian.org ]
> 
> Hi,
> 
> Regression spotted by Pere in some debian-edu job, but also seen since
> the 2nd of June in normal gnome chroot installation then upgrade from
> jessie to stretch:
>   
> https://jenkins.debian.net/view/edu_devel/job/chroot-installation_jessie_install_education-desktop-gnome_upgrade_to_stretch/
>   
> https://jenkins.debian.net/job/chroot-installation_jessie_install_gnome_upgrade_to_stretch/
> 

Hi,

Thanks for reporting this.

Timing being what it is, we need to act fast if we want to fix this for
stretch.  I have CC'ed maintainers of (presumably) relevant packages;
please be ready to upload a fix to your package if needed.

Long story short:
=

 * dpkg reports a trigger cycle between gnome-menus and
   desktop-file-utils.

 * desktop-file-utils has an "interest" (implicit "-await") trigger, so
   it is plausible.  I have not verified the dependency relationship.

 * shared-mime-info also has an "interest" (implicit "-await") trigger.
   It may (or may not) be an accomplice to this issue.

 * gnome-menus only have "interest-noawait" and should therefore not be
   able to start the trigger cycle (but it can be part of one).

Things to do / research:
===

 * @desktop-file-utils: The trigger seems to be used for a cache.  Is
   there any reason for using the implicit "-await" trigger or can this
   cache update be deferred like the "man-db" cache can?

 * @shared-mime-info: The trigger seems to be used for a cache.  Is
   there any reason for using the implicit "-await" trigger or can this
   cache update be deferred like the "man-db" cache can?

 * @Andreas: Could you have a look at the upgrade ordering in this case.
   You are usually pretty good at spotting if we need Breaks, so I would
   be delighted if you could give it a go.
   (E.g. if gnome-menus need to break desktop-file-utils in jessie even
if desktop-file-utils in stretch uses a "-noawait" trigger)


I have left the remaining parts of KiBi's mails below for the newly
CC'ed people.

Thanks,
~Niels


> I've managed to reproduce it locally with basically a debootstrap of
> jessie, installation of gnome, then switch sources.list from jessie to
> stretch, then update & upgrade & dist-upgrade.
> 
> I've bisected the archive using snapshot.debian.org and found out:
>  - 20170601T212625Z = last timestamp found to be OK;
>  - 20170602T033358Z = first timestamp to be KO.
> 
> Since logs are a bit too heavy for a bug report, I've uploaded them
> there:
>   https://people.debian.org/~kibi/jessie2stretch/gnome/
> 
> $timestamp.log is the output of the installation & dist-upgrade process,
> while $timestamp.log.clean is a cleaned version (with Get: lines edited
> to remove the package indice and the timestamp, then sort them by block,
> so as to avoid a huge diff).
> 
> Then I've generated upgrade.diff by diffing both clean versions:
>   https://people.debian.org/~kibi/jessie2stretch/gnome/upgrade.diff
> 
> This file consists mainly of some differences which should help us
> pinpoint the exact issue (first part of the diff), but also of a big
> diff at the end, since the OK log goes on with the install while the KO
> one is cut rather quickly. Actual error follows:
> | Unpacking default-jre-headless (2:1.8-58) over (2:1.7-52) ...
> | Processing triggers for libc-bin (2.24-10) ...
> | Processing triggers for hicolor-icon-theme (0.15-1) ...
> | Processing triggers for desktop-file-utils (0.23-1) ...
> | Processing triggers for man-db (2.7.6.1-2) ...
> | Processing triggers for libglib2.0-0:amd64 (2.50.3-2) ...
> | (Reading database ... 129883 files and directories currently installed.)
> | Removing openjdk-7-jre:amd64 (7u111-2.6.7-1~deb8u1) ...
> | Removing openjdk-7-jre-headless:amd64 (7u111-2.6.7-1~deb8u1) ...
> | Removing tzdata-java (2017b-0+deb8u1) ...
> | Processing triggers for hicolor-icon-theme (0.15-1) ...
> | dpkg: cycle found while processing triggers:
> |  chain of packages whose triggers are or may be responsible:
> |   gnome-menus -> desktop-file-utils
> |  packages' pending triggers which are or may be unresolvable:
> |   gnome-menus: /usr/share/applications
> |   shared-mime-info: /usr/share/mime/packages
> |   desktop-file-utils: /usr/share/applications
> | dpkg: error processing package gnome-menus (--remove):
> |  triggers looping, abandoned
> | Processing triggers for desktop-file-utils (0.23-1) ...
> | Errors were encountered while processing:
> |  gnome-menus
> | E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> By looking at the diff before that, this might have been triggered (no
> pun intended) by the ca-certificates-java update, which included changes
> in the required java version, which might explain why 

Bug#859787: experimental

[Geert Stappers]

On Sat, Jun 10, 2017 at 10:43:25PM +0200, Alexandre Rossi wrote:
> Hi,

  :-)


> > debian/changelog begins with
> >   davmail (4.8.0.2479-1) experimental; urgency=low
> >
> > Why the request for uploading to 'experimental'?
> 
> With my understanding of the freeze policy, for a package that is in
> testing, one should upload to unstable only version fixing RC bugs.
> Although the release is near, I'm sticking to the rules.

Good to know:
* What is uploaded to experimental, stays in experimental.
* There is no automatic "elevation" from experimental to unstable.
* What is uploaded to unstable elevates to testing,
  but not during a freeze. The freeze block prevents it.
* To get elevation from unstable to testing during freeze
  starts with a unblock request.
* A valid reason for honouring a unblock request
  is a fix for a release critical bug.
* What in testing is elavates into stable (at "release").
* Uploads to experimental don't close bugs, uploads to unstable do.

Upload to experimental done.


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Cyril Brulebois]

Package: upgrade-reports
Severity: critical
Justification: makes upgrade from stable abort

[ X-D-Cc:
  debian-rele...@lists.debian.org
  pkg-java-maintain...@lists.alioth.debian.org
  pkg-gnome-maintain...@lists.alioth.debian.org ]

Hi,

Regression spotted by Pere in some debian-edu job, but also seen since
the 2nd of June in normal gnome chroot installation then upgrade from
jessie to stretch:
  
https://jenkins.debian.net/view/edu_devel/job/chroot-installation_jessie_install_education-desktop-gnome_upgrade_to_stretch/
  
https://jenkins.debian.net/job/chroot-installation_jessie_install_gnome_upgrade_to_stretch/

I've managed to reproduce it locally with basically a debootstrap of
jessie, installation of gnome, then switch sources.list from jessie to
stretch, then update & upgrade & dist-upgrade.

I've bisected the archive using snapshot.debian.org and found out:
 - 20170601T212625Z = last timestamp found to be OK;
 - 20170602T033358Z = first timestamp to be KO.

Since logs are a bit too heavy for a bug report, I've uploaded them
there:
  https://people.debian.org/~kibi/jessie2stretch/gnome/

$timestamp.log is the output of the installation & dist-upgrade process,
while $timestamp.log.clean is a cleaned version (with Get: lines edited
to remove the package indice and the timestamp, then sort them by block,
so as to avoid a huge diff).

Then I've generated upgrade.diff by diffing both clean versions:
  https://people.debian.org/~kibi/jessie2stretch/gnome/upgrade.diff

This file consists mainly of some differences which should help us
pinpoint the exact issue (first part of the diff), but also of a big
diff at the end, since the OK log goes on with the install while the KO
one is cut rather quickly. Actual error follows:
| Unpacking default-jre-headless (2:1.8-58) over (2:1.7-52) ...
| Processing triggers for libc-bin (2.24-10) ...
| Processing triggers for hicolor-icon-theme (0.15-1) ...
| Processing triggers for desktop-file-utils (0.23-1) ...
| Processing triggers for man-db (2.7.6.1-2) ...
| Processing triggers for libglib2.0-0:amd64 (2.50.3-2) ...
| (Reading database ... 129883 files and directories currently installed.)
| Removing openjdk-7-jre:amd64 (7u111-2.6.7-1~deb8u1) ...
| Removing openjdk-7-jre-headless:amd64 (7u111-2.6.7-1~deb8u1) ...
| Removing tzdata-java (2017b-0+deb8u1) ...
| Processing triggers for hicolor-icon-theme (0.15-1) ...
| dpkg: cycle found while processing triggers:
|  chain of packages whose triggers are or may be responsible:
|   gnome-menus -> desktop-file-utils
|  packages' pending triggers which are or may be unresolvable:
|   gnome-menus: /usr/share/applications
|   shared-mime-info: /usr/share/mime/packages
|   desktop-file-utils: /usr/share/applications
| dpkg: error processing package gnome-menus (--remove):
|  triggers looping, abandoned
| Processing triggers for desktop-file-utils (0.23-1) ...
| Errors were encountered while processing:
|  gnome-menus
| E: Sub-process /usr/bin/dpkg returned an error code (1)

By looking at the diff before that, this might have been triggered (no
pun intended) by the ca-certificates-java update, which included changes
in the required java version, which might explain why this block was
present in the OK log but no longer in the KO one?
| -dpkg: openjdk-7-jre-headless:amd64: dependency problems, but removing anyway 
as you requested:
| - ca-certificates-java depends on openjdk-7-jre-headless | 
java7-runtime-headless; however:
| -  Package openjdk-7-jre-headless:amd64 is to be removed.
| -  Package java7-runtime-headless is not installed.
| -  Package openjdk-8-jre-headless:amd64 which provides java7-runtime-headless 
is not configured yet.
| -  Package default-jre-headless which provides java7-runtime-headless is not 
configured yet.
| -  Package openjdk-7-jre-headless:amd64 which provides java7-runtime-headless 
is to be removed.
| - ca-certificates-java depends on openjdk-7-jre-headless | 
java7-runtime-headless; however:
| -  Package openjdk-7-jre-headless:amd64 is to be removed.
| -  Package java7-runtime-headless is not installed.
| -  Package openjdk-8-jre-headless:amd64 which provides java7-runtime-headless 
is not configured yet.
| -  Package default-jre-headless which provides java7-runtime-headless is not 
configured yet.
| -  Package openjdk-7-jre-headless:amd64 which provides java7-runtime-headless 
is to be removed.
| -

I don't see any immediate solutions (mostly because it's the first dpkg
triggers cycle I encounter), but this looks like something that really
should be fixed before the stretch release, hence the severity and the
x-d-cc list.


KiBi.

Bug#864596: openjdk-9: Please disable generation of jvmti.html on m68k

[John Paul Adrian Glaubitz]

Source: openjdk-9
Version: 9~b170-2
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: m68k

Hi!

Like for openjdk-8 in #864205, the generation of jvmti.html causes
an out-of-memory error on m68k. To avoid this problem, we can just
disable the generation of jvmti.html on m68k which is achieved
by the simple attached patch.

I just added it to debian/rules with:

ifneq (,$(findstring m68k, $(DEB_HOST_ARCH)))
  COMMON_PATCHES += \
hotspot-disable-jvmtihtml.diff
endif

Thanks for consideration.

Adrian

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864205

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- hotspot-jdk-9+170/hotspot/make/gensrc/GensrcJvmti.gmk.orig  2017-05-11 
14:11:42.0 +0200
+++ hotspot-jdk-9+170/hotspot/make/gensrc/GensrcJvmti.gmk   2017-06-06 
16:38:26.990673621 +0200
@@ -103,7 +103,6 @@
 -PARAM interface jvmti -PARAM trace Trace))
 $(eval $(call SetupJvmtiGeneration, jvmtiEnv.hpp, jvmtiHpp.xsl))
 $(eval $(call SetupJvmtiGeneration, jvmti.h, jvmtiH.xsl))
-$(eval $(call SetupJvmtiGeneration, jvmti.html, jvmti.xsl))
 $(eval $(call SetupJvmtiGeneration, jvmtiEnvStub.cpp, jvmtiEnv.xsl))
 
 JVMTI_BC_SRCDIR := $(HOTSPOT_TOPDIR)/src/share/vm/interpreter

Bug#864595: openjdk-9: Please update the patch for m68k support

[John Paul Adrian Glaubitz]

Source: openjdk-9
Version: 9~b170-2
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: m68k

Hi!

Like openjdk-8 in #864180 [1], openjdk-9 needs an updated patch to
properly work on m68k. The attached patch comes again from Andreas
Schwab. I had to make two minor modifications to make it work as his
patch was untested.

This patch is the main bit that is necessary to fix openjdk-9 on
m68k. Two additional patches are required which are less related
to m68k and are both workarounds. I will file separate bug reports
for them.

Thanks,
Adrian

 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
Index: jdk9-fe8466adaef8/common/autoconf/generated-configure.sh
===
--- jdk9-fe8466adaef8.orig/common/autoconf/generated-configure.sh
+++ jdk9-fe8466adaef8/common/autoconf/generated-configure.sh
@@ -15595,6 +15595,12 @@ test -n "$target_alias" &&
   VAR_CPU_BITS=64
   VAR_CPU_ENDIAN=big
   ;;
+m68k)
+  VAR_CPU=m68k
+  VAR_CPU_ARCH=m68k
+  VAR_CPU_BITS=32
+  VAR_CPU_ENDIAN=big
+  ;;
 *)
   as_fn_error $? "unsupported cpu $build_cpu" "$LINENO" 5
   ;;
@@ -15734,6 +15740,12 @@ $as_echo "$OPENJDK_BUILD_OS-$OPENJDK_BUI
   VAR_CPU_BITS=64
   VAR_CPU_ENDIAN=big
   ;;
+m68k)
+  VAR_CPU=m68k
+  VAR_CPU_ARCH=m68k
+  VAR_CPU_BITS=32
+  VAR_CPU_ENDIAN=big
+  ;;
 *)
   as_fn_error $? "unsupported cpu $host_cpu" "$LINENO" 5
   ;;
Index: jdk9-fe8466adaef8/common/autoconf/platform.m4
===
--- jdk9-fe8466adaef8.orig/common/autoconf/platform.m4
+++ jdk9-fe8466adaef8/common/autoconf/platform.m4
@@ -96,6 +96,12 @@ AC_DEFUN([PLATFORM_EXTRACT_VARS_FROM_CPU
   VAR_CPU_BITS=64
   VAR_CPU_ENDIAN=big
   ;;
+m68k)
+  VAR_CPU=m68k
+  VAR_CPU_ARCH=m68k
+  VAR_CPU_BITS=32
+  VAR_CPU_ENDIAN=big
+  ;;
 *)
   AC_MSG_ERROR([unsupported cpu $1])
   ;;
Index: jdk9-fe8466adaef8/hotspot/src/os/linux/vm/os_linux.cpp
===
--- jdk9-fe8466adaef8.orig/hotspot/src/os/linux/vm/os_linux.cpp
+++ jdk9-fe8466adaef8/hotspot/src/os/linux/vm/os_linux.cpp
@@ -2214,6 +2214,8 @@ const char* search_string = "cpu";
 const char* search_string = "processor";
 #elif defined(SPARC)
 const char* search_string = "cpu";
+#elif defined(M68K)
+const char* search_string = "CPU";
 #else
 const char* search_string = "Processor";
 #endif
Index: jdk9-fe8466adaef8/hotspot/src/os_cpu/linux_zero/vm/atomic_linux_zero.hpp
===
--- 
jdk9-fe8466adaef8.orig/hotspot/src/os_cpu/linux_zero/vm/atomic_linux_zero.hpp
+++ jdk9-fe8466adaef8/hotspot/src/os_cpu/linux_zero/vm/atomic_linux_zero.hpp
@@ -36,7 +36,7 @@
  * __m68k_cmpxchg
  *
  * Atomically store newval in *ptr if *ptr is equal to oldval for user space.
- * Returns newval on success and oldval if no exchange happened.
+ * Returns oldval on success and *ptr if no exchange happened.
  * This implementation is processor specific and works on
  * 68020 68030 68040 and 68060.
  *
@@ -60,40 +60,48 @@ static inline int __m68k_cmpxchg(int old
 static inline int m68k_compare_and_swap(volatile int *ptr,
 int oldval,
 int newval) {
+  int prev = *ptr;
   for (;;) {
-  int prev = *ptr;
+  int newprev;
   if (prev != oldval)
 return prev;
 
-  if (__m68k_cmpxchg (prev, newval, ptr) == newval)
+  newprev = __m68k_cmpxchg (prev, newval, ptr);
+  if (newprev == prev)
 // Success.
 return prev;
 
   // We failed even though prev == oldval.  Try again.
+  prev = newprev;
 }
 }
 
 /* Atomically add an int to memory.  */
 static inline int m68k_add_and_fetch(volatile int *ptr, int add_value) {
+  int prev = *ptr;
   for (;;) {
   // Loop until success.
+  int newprev;
 
-  int prev = *ptr;
-
-  if (__m68k_cmpxchg (prev, prev + add_value, ptr) == prev + add_value)
+  newprev = __m68k_cmpxchg (prev, prev + add_value, ptr);
+  if (newprev == prev)
 return prev + add_value;
+  prev = newprev;
 }
 }
 
 /* Atomically write VALUE into `*PTR' and returns the previous
contents of `*PTR'.  */
 static inline int m68k_lock_test_and_set(volatile int *ptr, int newval) {
+  int prev = *ptr;
   for (;;) {
   // Loop until success.
-  int prev = *ptr;
+  int newprev;
 
-  if (__m68k_cmpxchg (prev, newval, ptr) == prev)
+  newprev = __m68k_cmpxchg (prev, newval, ptr);
+  if (newprev == prev)
 return prev;
+  prev = newprev;
 }
 }
 #endif // M68K
Index: 

Bug#864594: ITP: fbkeyboard -- on screen keyboard for fbdev

[Julian Winkler]

Package: wnpp
Severity: wishlist
Owner: Julian Winkler 

* Package name: fbkeyboard
  Version : 0.1
  Upstream Author : Julian Winkler 
* URL : https://github.com/julianwi/fbkeyboard
* License : GPL
  Programming Lang: C
  Description : on screen keyboard for fbdev

This is a framebuffer softkeyboard for use on devices with
touchscreen input like smartphones. It was designed for the
linux text console. It uses lib freetype to render fonts.
Keystrokes will be send to the kernel using uinput. An example
of using this can be found here: 
http://julianwi.square7.ch/debian-on-smartphone/

Bug#864593: [mariadb-server-10.1] Fails to upgrade

[mirq-deboogs]

Removing /etc/init.d/mysql allows upgrade to complete successfully.

Bug#864593: [mariadb-server-10.1] Fails to upgrade

[mirq-deboogs]

Package: mariadb-server-10.1
Version: 10.1.23-9+deb9u1
Severity: important

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

Package fails to upgrade when main mariadb.service is disabled:

# apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  mariadb-server-10.1
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
11 not fully installed or removed.
Need to get 0 B/5276 kB of archives.
After this operation, 1024 B disk space will be freed.
Do you want to continue? [Y/n] 
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 59318 files and directories currently installed.)
Preparing to unpack .../mariadb-server-10.1_10.1.23-9+deb9u1_i386.deb ...
Failed to stop mysql.service: Unit mysql.service not loaded.
invoke-rc.d: initscript mysql, action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit statu s 5
dpkg: trying script from the new package instead ...
Failed to stop mysql.service: Unit mysql.service not loaded.
invoke-rc.d: initscript mysql, action "stop" failed.
dpkg: error processing archive
/var/cache/apt/archives/mariadb-server-10.1_10.1.23-9+deb9u1_i386.deb 
(--unpack):
subprocess new pre-removal script returned error exit status 5
Failed to start mysql.service: Unit mysql.service not found.
invoke-rc.d: initscript mysql, action "start" failed.
Unit mysql.service could not be found.
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 5
Errors were encountered while processing:
 /var/cache/apt/archives/mariadb-server-10.1_10.1.23-9+deb9u1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

# systemctl status mariadb.service
● mariadb.service - MariaDB database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; disabled; vendor 
preset: enabled)
   Active: inactive (dead)

# systemctl status mysql.service
Unit mysql.service could not be found.

# dpkg --status mariadb-server-10.1
Package: mariadb-server-10.1
Status: install reinstreq half-configured
Priority: optional
Section: database
Installed-Size: 73115
Maintainer: Debian MySQL Maintainers 
Architecture: i386
Source: mariadb-10.1
Version: 10.1.23-8
Config-Version: 10.1.23-8
Replaces: mariadb-galera-server, mariadb-galera-server-10.0, 
mariadb-galera-server-5.5, mariadb-server-10.0, mariadb-server-5.5, 
mariadb-tokudb-engine-10.0, mariadb-tokudb-engine-10.1, 
mariadb-tokudb-engine-5.5, mysql-client-5.5, mysql-server-5.5, 
mysql-server-5.6, mysql-server-5.7, virtual-mysql-server
Provides: virtual-mysql-server
Depends: galera-3 (>= 25.3), gawk, iproute2, libdbi-perl, lsb-base (>= 3.0-10), 
lsof, mariadb-client-10.1 (>= 10.1.23-8), mariadb-server-core-10.1 (>= 
10.1.23-8), passwd, perl (>= 5.6), psmisc, rsync, socat, debconf (>= 0.5) | 
debconf-2.0, init-system-helpers (>= 1.18~), libaio1 (>= 0.3.93), libc6 (>= 
2.17), libpam0g (>= 0.99.7.1), libstdc++6 (>= 5.2), libsystemd0, zlib1g (>= 
1:1.2.0)
Pre-Depends: adduser (>= 3.40), debconf, mariadb-common (>= 10.1.23-8)
Recommends: libhtml-template-perl
Suggests: mailx, mariadb-test, netcat-openbsd, tinyca
Breaks: mariadb-galera-server, mariadb-galera-server-10.0, 
mariadb-galera-server-5.5, mariadb-server-10.0, mariadb-server-5.5, 
mariadb-tokudb-engine-10.0, mariadb-tokudb-engine-10.1, 
mariadb-tokudb-engine-5.5, mysql-client-5.5, mysql-server-5.5, 
mysql-server-5.6, mysql-server-5.7
Conflicts: mariadb-tokudb-engine-10.0, mariadb-tokudb-engine-10.1, 
mariadb-tokudb-engine-5.5, mysql-server-core-5.5, mysql-server-core-5.6, 
mysql-server-core-5.7, virtual-mysql-server
Conffiles:
 /etc/apparmor.d/usr.sbin.mysqld 5b43a33a4995f3532bcea02d9c2c87c1
 /etc/default/mysql 64e6d248978c07392628278d0be66888
 /etc/init.d/mysql 50c82644a999f08a0861a85c92b7d525
 /etc/insserv.conf.d/mariadb/mariadb-server-10.1.insserv.conf 
2588bf6ebd0da2f146befac246610658
 /etc/logcheck/ignore.d.paranoid/mariadb-server-10_1 
6babe46e791059cdd5a26f4f7fec9eca
 /etc/logcheck/ignore.d.server/mariadb-server-10_1 
a5b52544898b1d96ce64f96ec913ee65
 /etc/logcheck/ignore.d.workstation/mariadb-server-10_1 
a9766f2dd21ba5e5474526b9df4a82a7
 /etc/logrotate.d/mysql-server 3b27c6ac3dbfe31c1c1db0f880b3a2f4
 /etc/mysql/debian-start 698c5abe65f83aec900a3f0e3500e758
 /etc/mysql/mariadb.conf.d/50-mysqld_safe.cnf ace3390ea785e7bb3e87bee2ef0f9da8
 /etc/mysql/mariadb.conf.d/50-server.cnf 073e32328fb38e45ea4d3a497bbda982
Description: MariaDB database server binaries
 MariaDB is a fast, stable and true multi-user, multi-threaded SQL database
 server. SQL (Structured Query Language) is the most popular database query
 language in the world. The main goals of MariaDB are speed, robustness and
 ease of use.
 .
 This package includes the server binaries.
Homepage: https://mariadb.org/