Bug#864402: lxde "No session for pid ...." on screen after login.

[David Lawyer]

Package: lxde
Version:9_all

When I login to the GUI X screen an error message appears reading "No
session for pid " where  is a pid and is different for each login.
Checking on the inet found the problem reported by others but a suggested
work around didn't work for me or for someone else.   The pid always maps
to lxpolkit.  You have to click "OK" on this error message to get rid of
it.

David Lawyer

Bug#864401: Upgrade Firefox-ESR to 52.xx

[Julien Aubin]

Subject: firefox-esr: Upgrade Firefox ESR to 52.x before testing release
Package: firefox-esr
Version: 45.9.0esr-1
Severity: wishlist

Hi,

As Firefox ESR 45.x is reaching EOL just beforce Stretch release, wouldn't
it
be wise to upgrade it to 52.xx branch before Stretch ?

Otherwise you'll have to rush out to release it just after Stretch.

Thanks



-- Package-specific info:

-- Extensions information
Name: Cookie Monster
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{45d8ff86-d909-11db-9705-005056c8}
Package: xul-ext-cookie-monster
Status: enabled

Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: enabled

Name: Firefox Hello Beta
Location: ${PROFILE_EXTENSIONS}/l...@mozilla.org.xpi
Status: enabled

Name: Français Language Pack locale
Location:
/usr/lib/firefox-esr/browser/extensions/langpack...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-fr
Status: enabled

Name: HTTPS Everywhere
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
https-everywhere-...@eff.org
Package: xul-ext-https-everywhere
Status: enabled

Name: RequestPolicy Continued
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
rpcontin...@amo.requestpolicy.org
Package: xul-ext-requestpolicy
Status: enabled

Name: Thème par défaut theme
Location:
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: enabled

Name: uBlock Origin
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/
ublo...@raymondhill.net
Package: xul-ext-ublock-origin
Status: enabled

Name: User Agent Switcher
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{e968fc70-8f95-4ab9-9e79-304de2a71ee1}
Package: xul-ext-useragentswitcher
Status: enabled

-- Plugins information
Name: GNOME Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: enabled

Name: Google Talk Plugin
Location: /opt/google/talkplugin/libnpgoogletalk.so
Package: google-talkplugin
Status: enabled

Name: Google Talk Plugin Video Renderer
Location: /opt/google/talkplugin/libnpo1d.so
Package: google-talkplugin
Status: enabled

Name: IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3.1))
Location: /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-8-plugin:amd64
Status: enabled

Name: iTunes Application Detector
Location: /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
Package: rhythmbox-plugins
Status: enabled

Name: Shockwave Flash (25.0.0.171)
Location: /usr/lib/flashplayer-mozilla/libflashplayer.so
Package: flashplayer-mozilla
Status: enabled

Name: Skype Buttons for Kopete
Location: /usr/lib/mozilla/plugins/skypebuttons.so
Package: kopete
Status: enabled

Name: VLC Web Plugin
Location: /usr/lib/mozilla/plugins/libvlcplugin.so
Package: browser-plugin-vlc
Status: enabled


-- Addons package information
ii  browser-plugin 2.0.6-4  amd64multimedia plugin for web
browser
ii  firefox-esr45.9.0esr-1  amd64Mozilla Firefox web browser -
Ext
ii  firefox-esr-l1 45.9.0esr-1  all  French language package for
Firef
ii  flashplayer-mo 3:25.0.0.171 amd64Adobe Flash Player
ii  gnome-shell3.22.3-3 amd64graphical shell for the GNOME
des
ii  google-talkplu 5.41.3.0-1   amd64Google Talk Plugin
ii  icedtea-8-plug 1.6.2-3.1amd64web browser plugin based on
OpenJ
ii  kopete 4:16.08.1-3  amd64instant messaging and chat
applic
ii  rhythmbox-plug 3.4.1-2+b1   amd64plugins for rhythmbox music
playe
ii  xul-ext-cookie 1.3.0.5-1all  manage cookies in a
whitelist-bas
ii  xul-ext-https- 5.2.8-1  all  extension to force the use of
HTT
ii  xul-ext-reques 1.0.0~beta12 all  improve your browsing: more
priva
ii  xul-ext-ublock 1.10.4+dfsg- all  general-purpose lightweight
ads,
ii  xul-ext-userag 0.7.3-3  all  Firefox addon that allows the
use

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libasound21.1.3-5
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.18-1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   

Bug#864400: irssi: CVE-2017-9468 CVE-2017-9469

[Salvatore Bonaccorso]

Source: irssi
Version: 0.8.17-1
Severity: important
Tags: security upstream patch

Hi,

the following vulnerabilities were published for irssi.

CVE-2017-9468[0]:
| In Irssi before 1.0.3, when receiving a DCC message without source
| nick/host, it attempts to dereference a NULL pointer. Thus, remote IRC
| servers can cause a crash.

CVE-2017-9469[1]:
| In Irssi before 1.0.3, when receiving certain incorrectly quoted DCC
| files, it tries to find the terminating quote one byte before the
| allocated memory. Thus, remote attackers might be able to cause a
| crash.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-9468
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9468
[1] https://security-tracker.debian.org/tracker/CVE-2017-9469
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9469
[2] https://irssi.org/security/irssi_sa_2017_06.txt
[3] 
https://github.com/irssi/irssi/commit/fb08fc7f1aa6b2e616413d003bf021612301ad55

Regards,
Salvatore

Bug#864388: pulseaudio: Regression - sound audibly distorted for Creative Soundblaster Live

[Peter Tuharsky]

Package: pulseaudio
Version: 10.0-1
Followup-For: Bug #864388

I have probably figured something out.

I have installed GNOME ALSA Mixer, since it reveals much more sound settings
than standard applet. I have tackled it for a while and found there some
channels signed for recording. I have muted all the recordings and the
distortion is gone.

The pitty thing is that I cannot figure out, which one it was. I attempted to
go up and down with faders and allow recording from channel to channel but the
distortion has not returned back. I even deleted the GNOME ALSA Mixer settings
from my profile, however the sound settings are probably stored also somewhere
else and have not returned to the defaults.

So, it would seem that there is some broken default in mixer settings for
Stretch that was correct before in Jessie. Now it's only difficult to say,
which one.

I have nothing connected to any input channel of soundcard, so there is no way
it could do something on output. The distortion only took place when playing
the sound file, not when there was no sound playing.

I just feel that it has been some strange, seemingly output channel marked for
recording (possibly some line out?), thus possibly returned by the mixer's
routing back to input, thus causing distortion of general output signal.

Is there a possibility to compare the default mixer settings in source code
from Jessie and Stretch, thus finding the difference? Or is there some other
way of knowing, what has changed since I saved new (and seemingly correct)
mixer settings?



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


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

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

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-11
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.18-1
ii  libgcc1  1:6.3.0-18
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.27-3
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-18
ii  libsystemd0  232-25
ii  libtdb1  1.3.11-2
ii  libudev1 232-25
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 10.0-1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4+b1

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
pn  pavucontrol  
pn  pavumeter
ii  udev 232-25

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

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

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

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

; cookie-file =

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

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# 

Bug#864399: unblock: serf/1.3.9-3

[James McCoy]

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

Please unblock package serf

libserf-dev was missing a Depends on libssl-dev.  This caused pkg-config
to error when querying information for serf unless libssl-dev happened
to be installed.

diffstat for serf_1.3.9-2 serf_1.3.9-3

 changelog |7 +++
 control   |3 ++-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff -u serf-1.3.9/debian/changelog serf-1.3.9/debian/changelog
--- serf-1.3.9/debian/changelog
+++ serf-1.3.9/debian/changelog
@@ -1,3 +1,10 @@
+serf (1.3.9-3) unstable; urgency=medium
+
+  * Add libssl-dev to libserf-dev's Depends, otherwise pkg-config can't
+provide information about serf.  Thanks to Daniel Shahaf for noticing!
+
+ -- James McCoy   Wed, 07 Jun 2017 23:09:48 -0400
+
 serf (1.3.9-2) unstable; urgency=medium
 
   * Remove Peter Samuelson as maintainer, at request of MIA team.  Thanks for
diff -u serf-1.3.9/debian/control serf-1.3.9/debian/control
--- serf-1.3.9/debian/control
+++ serf-1.3.9/debian/control
@@ -28,7 +28,8 @@
 Package: libserf-dev
 Section: libdevel
 Architecture: any
-Depends: libserf-1-1 (= ${binary:Version}), ${misc:Depends}, libapr1-dev, 
libaprutil1-dev
+Depends: libserf-1-1 (= ${binary:Version}), ${misc:Depends}, libapr1-dev,
+ libaprutil1-dev, libssl-dev
 Description: high-performance asynchronous HTTP client library headers
  serf library is a C-based HTTP client library built upon the Apache
  Portable Runtime (APR) library.  It multiplexes connections, running the

unblock serf/1.3.9-3

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

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

Bug#744931: Reopening

[Lumin]

Control: reopen -1

Reopening this bug because old-bpo still ships this version.
Sorry for the inconvinience.

Bug#844285: pidgin: steals (warps) mouse cursor (not just focus) when new message comes in [SEC=UNCLASSIFIED]

[Tim Connors]

Fvwm, only relevant configuration:
Style "Pidgin"   Sticky

(plus other sensible defaults like focus-follows-mouse, no AutoRaise or
anything silly like that)

I long ago set a plugin option to disable pidgin setting new notifications
because it was so unusable (though this means I don't get notified anymore
other than a tiny little icon on a window that's usually lowered, so on
the whole jabber has become mostly useless to me).  I think the option
was:

tools->plugins->message notification->"present conversation window"
("raise conversation window" would have already been off by default).

I'm pretty sure "Set window manager URGENT hint" was already off by
default.  I might expect URGENT to focus a window, and I'd definitely
expect that without it, a new window popped up would just follow the
window manager policy for focus, which in my case, doesn't steal
focus or warp the mouse pointer.

Here's message notification plugin's prefs as they now are:


























I'm not currently in a position to test setting method_raise back on, or
checking what the defaults are, because our jabber server is broken for
unrelated reasons.


> From: John Paul Adrian Glaubitz 
>
> I have been using Pidgin for years and I never observed this behavior on any
> desktop or window manager. Whenever I received a new message (currently using
> KDE), the systray icon changes to indicate a new message. But the cursor focus
> remains unchanged.
>
> Could you give a bit more detail on your environment, particularly which 
> desktop
> or window manager you are using? I suspect an issue with your particular 
> setup.
>
>
> Package: pidgin
> Followup-For: Bug #844285
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
> Read the bugreport
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> For what it's worth. I have also been using Pidgin (on XFCE4) for years. 
> Never observed the mentioned bug.
>
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***




-- 
Tim Connors

Bug#856190: Tagging as wontfix

[Lumin]

Control: tags -1 +wontfix

This issue is caused by the files under your /usr/local directory which
is out of the domain of package maintainance.

Bug#864398: nfs-common: can't mount nfs3 after updating to nfs-common 1:1.3.4-2.1

[Selene Scriven]

Package: nfs-common
Version: 1:1.3.4-2.1
Severity: important

Dear Maintainer,

It looks like something somewhat recent in testing broke the nfs3 client.

   * What led up to the situation?

 After updating from stable to testing, I could not mount nfs3
 shares.  Typical results were pretty opaque:

   $ mount /mnt/shared
   mount.nfs: mount system call failed

 There is no firewall; iptables -L shows no rules at all.  It
 appears that rpcbind and rpc.statd are both running.  The nfs
 server works for other clients, and worked for this client before
 updating.

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

 While looking for relevant bugs, I found mentions of
 systemd-related problems, including nfs-common.service being
 masked (which it was).

 First I asked apt to downgrade nfs-common and rpcbind to the stable
 version, but it complained it would need to remove systemd.  So I
 found some intermediate-version systemd packages cached on another
 host and downgraded to match what it has.

 To get nfs3 working again, I downgraded several packages:
   downgrading systemd from 232-25 to 229-4
   downgrading libsystemd0:amd64 from 232-25 to 229-4
   downgrading udev from 232-25 to 229-4
   downgrading libudev1:amd64 from 232-25 to 229-4
   downgrading libpam-systemd:amd64 from 232-25 to 229-4
   downgrading rpcbind from 0.2.3-0.6 to 0.2.1-6.1
   downgrading nfs-common from 1:1.3.4-2.1 to 1:1.2.8-9

 Since these had to be downgraded as a set, I'm not sure exactly
 which package(s) are responsible.  It also doesn't narrow down the
 nature of the error, but it does at least reduce things to a
 specific range of versions.  I don't see packages available for
 intermediate versions though, so I haven't found a more specific
 revision to check.

   * What was the outcome of this action?

 Upgrading from stable (jessie) to testing broke nfs3; I couldn't
 mount remote filesystems from /etc/fstab or from a command line.

 Downgrading a few packages back to stable (or an earlier version
 from testing, in some cases) got nfs3 working again.

   * What outcome did you expect instead?

 In general, nfs is something which usually "just works", using the
 following steps:

 - Do a minimal install.
 - (optional) add debian/testing to sources.list and
  apt upgrade/dist-upgrade to it
 - apt install nfs-common
 - mkdir /mnt/path ; mount server:/path /mnt/path

 Something in testing is breaking this use case.
 I'm sorry I don't have more specifics...


The information below is from after I got it working.


-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  33146  status
1000241   tcp  50201  status
-- /etc/default/nfs-common --
NEED_STATD=yes
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
nas:/volume1/shared /mnt/shared nfs 
user,nolock,intr,rsize=8192,wsize=8192,exec 0 0
-- /proc/mounts --
nas:/volume1/shared /mnt/shared nfs 
rw,nosuid,nodev,relatime,vers=3,rsize=8192,wsize=8192,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.5.5.4,mountvers=3,mountport=892,mountproto=udp,local_lock=all,addr=10.5.5.4
 0 0

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

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

Versions of packages nfs-common depends on:
ii  adduser 3.115
ii  initscripts 2.88dsf-59.9
ii  libc6   2.24-11
ii  libcap2 1:2.25-1
ii  libcomerr2  1.43.4-2
ii  libdevmapper1.02.1  2:1.02.137-2
ii  libevent-2.0-5  2.0.21-stable-3
ii  libgssapi-krb5-21.15-1
ii  libk5crypto31.15-1
ii  libkeyutils11.5.9-9
ii  libkrb5-3   1.15-1
ii  libmount1   2.29.2-1
ii  libnfsidmap20.25-5.1
ii  libtirpc1   0.2.5-1.2
ii  libwrap07.6.q-26
ii  lsb-base9.20161125
ii  rpcbind 0.2.1-6.1
ii  ucf 3.0036

Versions of packages nfs-common recommends:
ii  python  2.7.13-2

Versions of packages nfs-common suggests:
pn  open-iscsi  
pn  watchdog

-- Configuration Files:
/etc/default/nfs-common changed [not included]

-- no 

Bug#864397: Get error "PHP Warning: Module 'memcache' already loaded in Unknown on line 0" intermittently

[Commercial [Elthéa Moto Addict]]

Package: php5-memcached

Version: 2.2.0-2

Severity: important

 

Dear Maintainer,

 

 

   * What led up to the situation?

  Removal of local libraries

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

 ineffective)?

 Remove local libmemcached 

   * What was the outcome of this action?

 Got a new warning

   * What outcome did you expect instead?

To use the libmemcached without any warning.

The issue could cause bad libmemcached usage

 

After having removed libraries from /usr/local that caused the following
error,

 

---> PHP Warning:  PHP Startup: Unable to load dynamic library
'/usr/lib/php5/20131226/memcached.so' -/usr/lib/php5/20131226/memcached.so:
undefined symbol:memcached_destroy_sasl_auth_data in Unknown on line 0

 

I now get a new one intermittently:

 

---> PHP Warning:  Module 'memcache' already loaded in Unknown on line 0

 

I reboot the server in order to reinitiliazed the memory but it didn't
change the issue.

 

Thank you for your help,

Vincent

 

-- System Information:

Debian Release: 8.7

  APT prefers stable-updates

  APT policy: (500, 'stable-updates'), (500, 'stable')

Architecture: amd64 (x86_64)

 

Kernel: Linux 3.14.32--grs-ipv6-64 (SMP w/8 CPU cores)

Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/bash

Init: systemd (via /run/systemd/system)

 

Versions of packages php5-memcached depends on:

ii  libc6  2.19-18+deb8u7

ii  libmemcached11 1.0.18-4

ii  libmemcachedutil2  1.0.18-4

ii  libsasl2-2 2.1.26.dfsg1-13+deb8u1

ii  php5-common [phpapi-20131226]  5.6.30+dfsg-0+deb8u1

ii  ucf3.0030

ii  zlib1g 1:1.2.8.dfsg-2+b1

 

php5-memcached recommends no packages.

 

php5-memcached suggests no packages.

 

-- no debconf information

 

 

Sportivement, 
Vincent Boyadjian

Service Commercial 
36 Av. des Combattants en Afrique du Nord
13700 Marignane
Tél: 06.26.69.50.70
Email:  
commerc...@elthea-moto-addict.com
SIRET: 798220513 00021 
 
http://elthea-moto-addict.com/img/elt-import/logo/logoElthea.jpg

 

Bug#819136: firmware-b43-installer: Desire packaging script

[Rogério Brito]

Package: firmware-b43-installer
Version: 1:019-3
Followup-For: Bug #819136

I just skimmed through the patches that the submitter sent and they seem
like a huge improvement over what we have in the current version, while
fixing many bugs and updating the firmware for other cards.

Generating a debian package is the main goal, but the rest of the patches
look very nice and it would be great to have them integrated.

Can we have a new upload of firmware-b43-installer with these changes?


Thanks,

Rogério.


-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 4.9.0-3-powerpc
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.utf-8 (charmap=UTF-8), 
LANGUAGE=en_US.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages firmware-b43-installer depends on:
ii  b43-fwcutter  1:019-3
ii  bzip2 1.0.6-8.1
ii  wget  1.19.1-3

firmware-b43-installer recommends no packages.

firmware-b43-installer suggests no packages.

-- no debconf information

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

Bug#864396: git cherry-pick segfaults

[Rogério Brito]

Package: git
Version: 1:2.11.0-4
Severity: important

Hi.

I am keeping my dotfiles on a git repository and I just tried to cherry-pick
a commit from one branch to another and, to my surprise, it consistently
segfaults (and leaves a lock file on the git repository).

This is what running git under gdb with debug symbols give me:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
rbrito@g4:~/.dotfiles/config$ gdb git
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from git...Reading symbols from 
/usr/lib/debug/.build-id/30/3bab2a397b912a0229aa38a3d8574d5d245624.debug...done.
done.
(gdb) set args cherry-pick -x 7eb3540b6e58735ff56e50d403ec0892f8878e2a
(gdb) run
Starting program: /usr/bin/git cherry-pick -x 
7eb3540b6e58735ff56e50d403ec0892f8878e2a
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
[New Thread 0xb75d2460 (LWP 29473)]
[New Thread 0xb6dd2460 (LWP 29474)]
[Thread 0xb75d2460 (LWP 29473) exited]
[Thread 0xb6dd2460 (LWP 29474) exited]

Thread 1 "git" received signal SIGSEGV, Segmentation fault.
add_index_entry_with_check (option=0, ce=0x0, istate=0x10237348 ) at 
read-cache.c:1012
1012read-cache.c: No such file or directory.
(gdb) bt
#0  add_index_entry_with_check (option=0, ce=0x0, istate=0x10237348 
) at read-cache.c:1012
#1  add_index_entry (istate=0x10237348 , ce=0x0, option=0) at 
read-cache.c:1061
#2  0x100f7b70 in merge_content (o=o@entry=0xbfffe55c, 
path=path@entry=0x103d40c0 "xbmc/userdata/sources.xml", 
o_oid=, o_oid@entry=0x102e724c, o_mode=o_mode@entry=33188, 
a_oid=a_oid@entry=0x102e7264, 
a_mode=a_mode@entry=33188, b_oid=b_oid@entry=0x102e727c, b_mode=, rename_conflict_info=0x102a72c0)
at merge-recursive.c:1727
#3  0x100f8594 in process_entry (entry=, path=, 
o=0xbfffe55c) at merge-recursive.c:1885
#4  merge_trees (o=o@entry=0xbfffe55c, head=head@entry=0x102493e0, 
merge=, merge@entry=0x102493c0, 
common=, common@entry=0x10249400, 
result=result@entry=0xbfffe550) at merge-recursive.c:1948
#5  0x10148f64 in do_recursive_merge (opts=0xbfffea48, msgbuf=0xbfffe544, 
head=0xbfffe5e4 
"\364dK\257{\310-D\025\373\361\370\264id\274⦧\243\020#\243\300\020#\243\300\277\377\346\060(",
 
next_label=, base_label=, next=, base=) at sequencer.c:389
#6  do_pick_commit (command=TODO_PICK, commit=commit@entry=0x1023e3b0, 
opts=opts@entry=0xbfffea48) at sequencer.c:757
#7  0x1014ab48 in single_pick (opts=0xbfffea48, cmit=0x1023e3b0) at 
sequencer.c:1329
#8  sequencer_pick_revisions (opts=0xbfffea48) at sequencer.c:1378
#9  0x1007568c in run_sequencer (argc=, argc@entry=3, 
argv=argv@entry=0xbfffef08, opts=, 
opts@entry=0xbfffea48) at builtin/revert.c:178
#10 0x10075b10 in cmd_cherry_pick (argc=3, argv=0xbfffef08, prefix=) at builtin/revert.c:203
#11 0x100046c8 in run_builtin (argv=, argc=, 
p=) at git.c:373
#12 handle_builtin (argc=3, argv=0xbfffef08) at git.c:572
#13 0x10004b54 in run_argv (argv=0xbfffeb58, argcp=0xbfffeb5c) at git.c:630
#14 cmd_main (argc=, argc@entry=4, argv=, 
argv@entry=0xbfffef04) at git.c:707
#15 0x10003894 in main (argc=4, argv=0xbfffef04) at common-main.c:40
(gdb) 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

If there is any extra information that yout want me to provide, please let
me know and I will do my best.

Thanks,

Rogério Brito.

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 4.9.0-3-powerpc
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.utf-8 (charmap=UTF-8), 
LANGUAGE=en_US.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git depends on:
ii  dpkg 1.18.24
ii  git-man  1:2.11.0-4
ii  libc62.24-11
ii  libcurl3-gnutls  7.52.1-5
ii  liberror-perl0.17024-1
ii  libexpat12.2.0-2
ii  libpcre3 2:8.39-3
ii  perl 5.24.1-3
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages git recommends:
ii  less 481-2.1
ii  openssh-client [ssh-client]  1:7.4p1-11
ii  patch2.7.5-1+b2

Versions of packages git suggests:
ii  

Bug#528774: squeak-vm: Patch

[John David Anglin]

Package: squeak-vm
Followup-For: Bug #528774

Dear Maintainer,

Attached patch.

Regards,
Dave Anglin

-- System Information:
Debian Release: 9.0
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.11.3+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8), 
LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- ./squeak-vm-4.10.2.2614/unix/vm/sqUnixMain.c.save   2017-06-07 
18:37:47.652186881 -0400
+++ ./squeak-vm-4.10.2.2614/unix/vm/sqUnixMain.c2017-06-07 
18:38:20.912338583 -0400
@@ -152,7 +152,7 @@
 #  else
sa.sa_flags= 0; /* assume we already have BSD behaviour */
 #  endif
-#  if defined(__linux__) && !defined(__ia64) && !defined(__alpha__)
+#  if defined(__linux__) && !defined(__ia64) && !defined(__alpha__) && 
!defined(__hppa__)
sa.sa_restorer= 0;
 #  endif
sigaction(SIGALRM, , 0);
--- ./squeak-vm-4.10.2.2614/unix/vm-display-fbdev/sqUnixFBDevKeyboard.c.save
2017-06-07 18:58:01.947534222 -0400
+++ ./squeak-vm-4.10.2.2614/unix/vm-display-fbdev/sqUnixFBDevKeyboard.c 
2017-06-07 18:58:29.837647210 -0400
@@ -258,7 +258,7 @@
   sa.sa_handler= sigusr1;
   sigemptyset(_mask);
   sa.sa_flags= 0;
-#if !defined(__ia64) && !defined(__alpha__)
+#if !defined(__ia64) && !defined(__alpha__) && !defined (__hppa__)
   sa.sa_restorer= 0;
 #endif
   sigaction(SIGUSR1, , 0);

Bug#856552: progress on Kiwix RFPs?

[Antoine Beaupre]

On Thu, Mar 02, 2017 at 08:00:33PM +0100, Emmanuel Engelhart wrote:
> Debian developer Vasudev/Copyninja
> (uid=vasudev,ou=users,dc=debian,dc=org) has already volunteered to
> work on this RFP. One time implemented this package should IMO be
> maintained within the DebianEdu team.

Any progress here? Anything holding this up that we can help with?

A.


signature.asc
Description: PGP signature

Bug#763321: Kiwix - An offline wikipedia reader

[Antoine Beaupre]

On Sat, Sep 19, 2015 at 02:31:48PM +0200, Emmanuel Engelhart wrote:
> On 02.09.2015 11:23, Elena ``of Valhalla'' wrote:
> > X-Debbugs-Cc: debian-edu-pkg-t...@lists.alioth.debian.org, 
> > 1o5g4...@gmail.com
> > 
> > What about packaging just kiwix-serve?
> > It shouldn't depend on xulrunner, and adding it back into debian would
> > mean that there would be at least one reader for ZIM files, which is
> > currently lacking.
> > 
> > .. _kiwix-serve: http://www.kiwix.org/wiki/Kiwix-serve
> > 
> 
> Definitely a good idea! I support it to 100%. I'm ready to answer to
> questions and help any volunteer maintainer wanting to work on this. This
> should not be too complicated and the impact would be huge.

For what it's worth, seperate RFP bug reports were filed for
kiwix-serve (kiwix-serve, actually) and kiwix-lib:

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

So some future for Kiwix in Debian may exist after all. :)

Once those are done, maybe someone could start looking at the XUL
extension again? Or should we just give up on that?

A.


signature.asc
Description: PGP signature

Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

[Afif Elghraoui]

Hello,

على الأربعاء  7 حزيران 2017 ‫08:40، كتب Andreas Tille:
> Hi Adrian,
> 
> On Wed, Jun 07, 2017 at 03:26:49PM +0300, Adrian Bunk wrote:
>>
>>> NMUs are in any case OK for any Debian Med package.  I would have
>>> uploaded as well if I would know the best solution.  So please apply
>>> what you consider best and upload as soon as possible.  Alternatively
>>> send a patch and I'll hurry up.
>>
>> I actually got the same error that Andreas got on i386 also on amd64.
>>
>> It seems you also got the same in the past:
>>   https://lists.debian.org/debian-med/2017/01/msg00085.html
>>
>> In addition to changing the architecture list, my upload
>> (debdiff attached) uses for #863929 the big hammer of no
>> longer running integration-tests.
> 
> Hmmm, we need to discuss this with upstream, thought.  Afif, just let me
> know if you have continuous time constraints or whether you can take
> over from here.
>  

I have unfortunately severe time constraints until the end of Ramadan,
which would be in about 2.5 weeks. I might be able to spare some time on
the weekends, but I don't think this will mean much for falcon.

>> I'll open a new (non-RC) bug to make it visible that this is
>> an issue that should be investigated properly.
> 
> Thanks a lot for your last minute rescue action.  I'll commit your
> changes to Git (however, if you used Git locally feel free to push
> your changes - any DD has commit permissions).
> 

Yes, thank you very much, Adrian!

regards.
Afif

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

Bug#864382: tpu: mariadb-10.1/10.1.23-9+deb9u1

[Andreas Beckmann]

Followup-For: Bug #864382
Control: tag -1 - moreinfo

Uploaded ... and realized that it includes the bugfix from 10.1.23-9
(fixing up -8) which I thought that it had already migrated to testing
(but that was only at -8).  Actual debdiff attached.

Let's hope this build without needing give-backs.


Andreas
diff -Nru mariadb-10.1-10.1.23/debian/changelog mariadb-10.1-10.1.23/debian/changelog
--- mariadb-10.1-10.1.23/debian/changelog	2017-05-13 11:08:43.0 +0200
+++ mariadb-10.1-10.1.23/debian/changelog	2017-06-07 21:11:23.0 +0200
@@ -1,3 +1,18 @@
+mariadb-10.1 (10.1.23-9+deb9u1) stretch; urgency=medium
+
+  [ Ondřej Surý ]
+  * Add Breaks: cqrlog (<< 1.9.0-5~) to ensure correct upgrade order
+(Closes: #864159)
+
+ -- Andreas Beckmann   Wed, 07 Jun 2017 21:11:23 +0200
+
+mariadb-10.1 (10.1.23-9) unstable; urgency=medium
+
+  * Fix the invalid location of insserv configuration snippet
+(Thanks Michael Biebl for catching that)
+
+ -- Ondřej Surý   Fri, 26 May 2017 09:26:33 +0200
+
 mariadb-10.1 (10.1.23-8) unstable; urgency=medium
 
   * Use /etc/insserv.conf.d/mariadb to provide $database system facility
diff -Nru mariadb-10.1-10.1.23/debian/control mariadb-10.1-10.1.23/debian/control
--- mariadb-10.1-10.1.23/debian/control	2017-05-13 11:08:43.0 +0200
+++ mariadb-10.1-10.1.23/debian/control	2017-06-07 21:11:23.0 +0200
@@ -282,7 +282,8 @@
mysql-server-core-5.6,
mysql-server-core-5.7,
virtual-mysql-server
-Breaks: mariadb-galera-server,
+Breaks: cqrlog (<< 1.9.0-5~),
+mariadb-galera-server,
 mariadb-galera-server-10.0,
 mariadb-galera-server-5.5,
 mariadb-server-10.0,
diff -Nru mariadb-10.1-10.1.23/debian/mariadb-server-10.1.install mariadb-10.1-10.1.23/debian/mariadb-server-10.1.install
--- mariadb-10.1-10.1.23/debian/mariadb-server-10.1.install	2017-05-13 11:08:43.0 +0200
+++ mariadb-10.1-10.1.23/debian/mariadb-server-10.1.install	2017-06-07 21:11:23.0 +0200
@@ -9,7 +9,7 @@
 debian/additions/mariadb.conf.d/50-mysqld_safe.cnf etc/mysql/mariadb.conf.d
 debian/additions/mariadb.conf.d/50-server.cnf etc/mysql/mariadb.conf.d
 debian/additions/source_mariadb-10.1.py usr/share/apport/package-hooks
-debian/mariadb-server-10.1.insserv.conf etc/insserv.conf.d/mariadb
+debian/mariadb-server-10.1.insserv.conf => etc/insserv.conf.d/mariadb
 etc/apparmor.d/usr.sbin.mysqld
 [linux-any] lib/systemd/system/mariadb@.service
 [linux-any] lib/systemd/system/mariadb.service
diff -Nru mariadb-10.1-10.1.23/debian/mariadb-server-10.1.preinst mariadb-10.1-10.1.23/debian/mariadb-server-10.1.preinst
--- mariadb-10.1-10.1.23/debian/mariadb-server-10.1.preinst	2017-05-13 11:08:43.0 +0200
+++ mariadb-10.1-10.1.23/debian/mariadb-server-10.1.preinst	2017-06-07 21:11:23.0 +0200
@@ -9,6 +9,11 @@
 
 . /usr/share/debconf/confmodule
 
+# Just kill the invalid insserv.conf.d directory without fallback
+if [ -d "/etc/insserv.conf.d/mariadb/" ]; then
+rm -rf "/etc/insserv.conf.d/mariadb/"
+fi
+
 if [ -n "$DEBIAN_SCRIPT_DEBUG" ]; then set -v -x; DEBIAN_SCRIPT_TRACE=1; fi
 ${DEBIAN_SCRIPT_TRACE:+ echo "#42#DEBUG# RUNNING $0 $*" 1>&2 }
 

Bug#864395: pytables: autopkgtests do not fail even if tests fail

[Michael Hudson-Doyle]

Source: pytables
Severity: important
Tags: patch

Dear Maintainer,

It turns out that the tables.test function the autopkgtest call returns the
exit code and does not exit with it. Simple patch attached.

Cheers,
mwh

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial'), (400, 
'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-78-generic (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/tests/python2 b/debian/tests/python2
index 56c0d1a..42f6674 100755
--- a/debian/tests/python2
+++ b/debian/tests/python2
@@ -8,5 +8,5 @@ cd "$ADTTMP"
 
 for py in $PYS; do
 echo "=== $py ==="
-$py -c "import $TESTPKG; $TESTPKG.test(verbose=2)" 2>&1
+$py -c "import $TESTPKG, sys; sys.exit($TESTPKG.test(verbose=2))" 2>&1
 done
diff --git a/debian/tests/python2-dbg b/debian/tests/python2-dbg
index 1df3f6a..f7adb1d 100755
--- a/debian/tests/python2-dbg
+++ b/debian/tests/python2-dbg
@@ -8,5 +8,5 @@ cd "$ADTTMP"
 
 for py in $PYS; do
 echo "=== $py ==="
-$py-dbg -c "import $TESTPKG; $TESTPKG.test(verbose=2)" 2>&1
+$py-dbg -c "import $TESTPKG, sys; sys.exit($TESTPKG.test(verbose=2))" 2>&1
 done
diff --git a/debian/tests/python3 b/debian/tests/python3
index 13187cc..10531d3 100755
--- a/debian/tests/python3
+++ b/debian/tests/python3
@@ -8,5 +8,5 @@ cd "$ADTTMP"
 
 for py in $PYS; do
 echo "=== $py ==="
-$py -c "import $TESTPKG; $TESTPKG.test(verbose=2)" 2>&1
+$py -c "import $TESTPKG, sys; sys.exit($TESTPKG.test(verbose=2))" 2>&1
 done
diff --git a/debian/tests/python3-dbg b/debian/tests/python3-dbg
index 122cc3c..a13c00f 100755
--- a/debian/tests/python3-dbg
+++ b/debian/tests/python3-dbg
@@ -8,5 +8,5 @@ cd "$ADTTMP"
 
 for py in $PYS; do
 echo "=== $py ==="
-$py-dbg -c "import $TESTPKG; $TESTPKG.test(verbose=2)" 2>&1
+$py-dbg -c "import $TESTPKG, sys; sys.exit($TESTPKG.test(verbose=2))" 2>&1
 done

Bug#864388: pulseaudio: Regression - sound audibly distorted for Creative Soundblaster Live

[Felipe Sateler]

Control: tags -1 moreinfo

On Wed, Jun 7, 2017 at 4:42 PM, Peter Tuharsky  wrote:

> Package: pulseaudio
> Version: 10.0-1
> Severity: normal
>
> Dear Maintainer,
>
> I have Creative Soundblaster Live PCI soundcard that I have been gladly
> using
> for years. With Debian Jessie it still works fine. However, with Stretch
> there
> is audible distortion on any playback, regardless on PCM or general
> volume. The
> original sound is audible and articulated, however the distortion makes it
> unpleasant.
>


Could you please attach a verbose log of pulseaudio while the problem is
happening?

https://wiki.ubuntu.com/PulseAudio/Log



>
> I have tested playing the same files from command line on tty1 console
> using
> "play" command, and the sound is OK from there. So it seems that kernel
> driver
> is OK and only GNOME sound is affected, therefore I suspect Pulseaudio to
> be
> the centre of trouble.
>

Could you try using the old kernel with the new pulseaudio? Pulseaudio
excercises the driver more than the simple play command, so it may be that
some part of the driver is buggy.

Also, please try adding tsched=0 to the module-udev-detect line in
/etc/pulse/default.pa


> Tested with three different pieces of SB Live card of different branches,
> and
> on two PCs.
>
> Please, what could I do to workaround the problem until it gets fixed in
> Debian?
>

 Difficult to say without knowing what the problem is.

-- 

Saludos,
Felipe Sateler

Bug#841028: cups-daemon: cupsd uses 100% CPU

[Brian Potkin]

On Thu 08 Jun 2017 at 00:01:55 +0200, Samuel Wolf wrote:

> 2017-06-07 23:47 GMT+02:00 Till Kamppeter :
> 
> > The fix prevents the repeated loading of this printer as it considers the
> > loading done after the first load.
> >
> >
> Is this update/patch for Stretch available?

Not yet.

cups-filters, cups-filters-core-drivers and libcupsfilters1 from
experimental will install on Stretch at the present time.

-- 
Brian.

Bug#863858: issues with grub config symlinks

[dann frazier]

On Thu, Jun 01, 2017 at 01:36:06PM +0200, Louis Bouchard wrote:
> Le 01/06/2017 à 06:11, dann frazier a écrit :
> > I wonder if we could simplify this by doing the default config file
> > selection at build time instead of installtime. That should still solve
> > preserve the behavior of dpkg only considering the file to be modified
> > if the user manually edited it.
>
> This is definitively a better solution than a symlink hack. Let's figure
> out how to handle the upgrade & I'll hapilly merge it in.

Ah - and I see I failed to notice the main reason for the symlink
hack in the first place - kdump-tools is arch: all, so build time
decisions weren't an option! Whoops..

That said, I still think I'd rather have a per-arch build of
kdump-tools then install config files for every architecture on every
system. Therefore, I've updated my branch[1] to make kdump-tools
non-Arch: all.

I've also added code to reverse the symlink transition. I tested this
in a few ways, all on x86:

Clean 1:1.6.1-1 install upgrade to 1:1.6.1-2
  - Non-interactive upgrade, cleanup DTRT
1:16.1-2, modify kdump-tools.cfg, upgrade to 1:1.6.1-2.
  - Upgrade correctly prompts for conf-file resolution
Clean 1:1.5.3-2 (stable) install upgrade to 1:1.6.1-2
  - Non-interactive upgrade, no cleanup done

Let me know what you think.

[1] https://git.launchpad.net/~dannf/+git/makedumpfile/log/?h=grubcfg

  -dann

Bug#864394: ITP: ayatana-indicator-power -- Ayatana Indicator showing power state

[Mike Gabriel]

Package: wnpp
Severity: wishlist
Owner: Mike Gabriel 

* Package name: ayatana-indicator-power
  Version : 2.0.91
  Upstream Author : Mike Gabriel 
Charles Kerr 
Ted Gould 
* URL : https://github.com/ArcticaProject/ayatana-indicator-power
* License : GPL-3
  Programming Lang: C
  Description : Ayatana Indicator showing power state

 This Ayatana Indicator displays current power management information and
 gives the user a way to access power management preferences.
 .
 The Ayatana Indicator provides a generic, multi-desktop-env aware
 approach of accessing power information and management features.

Bug#864393: ITP: elpa-rich-minority -- Clean-up and beautify the list of minor-modes in Emacs' mode-line

[Nicholas D Steeves]

Package: wnpp
Severity: wishlist
Owner: Nicholas D Steeves 

Package name: elpa-rich-minority
Version : 1.0.1
Upstream Author : Artur Malabarba 
URL : https://github.com/Malabarba/rich-minority
License : GPL2+
Programming Lang: Lisp
Description : Clean-up and beautify the list of minor-modes in Emacs' 
mode-line
 Rich-minority-mode is used for hiding and/or highlighting the list of
 minor-modes in the mode-line.
 .
 By default, it has a couple of small effects (provided as examples).
 These can be customised by modifying the following three variables:
 .
 rm-blacklist: List of minor mode names that will be hidden from the
 minor-modes list. Use this to hide only a few modes that are always
 active and don’t really contribute information.
 .
 rm-whitelist: List of minor mode names that are allowed on the
 minor-modes list. Use this to hide all but a few modes.
 .
 rm-text-properties: List text properties to apply to each minor-mode
 lighter. For instance, by default Ovwrt is highlighted with a red
 face, so you always know if you’re in overwrite-mode.

I'm not a fan of the upstream name "rich-minority", but this package
is a dependency for elpa-smart-mode-line.  The name seems to be a pun
on rich text (eg: coloured) support for the mode line.  I would
maintain it as part of the pkg-emacsen team and will require a sponsor.

Sincerely,
Nicholas

Bug#864366: CVE-2017-9433

[Rene Engelhard]

Hi,

On Wed, Jun 07, 2017 at 11:54:26PM +0200, Moritz Mühlenhoff wrote:
> Please go ahead (needs -sa since orig tarball is new)

Ah, right. Almost forgot, thanks.

Done.

Regards,

Rene

Bug#856234: haskell-cryptol FTBFS on !x86: #error unknown max width for gmp on this architecture

[Edmund Grimley Evans]

This is easy to fix: in "Arch.hs" just use the smaller value of
maxBigIntWidth on any unrecognised architecture.

Bug#863426: isc-dhcp: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

Package: isc-dhcp
Version: 4.3.5-3
Followup-For: Bug #863426
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Dear Maintainer,

an updated isc-dhcp patch is attached, that moves the interface alias
stripping to client/dhclient.c as soon as the parameter is parsed from argv.
This allows dhclient to handle the interface name with no alias at all times.
The previous patch failed to allow dhclient to release the interface.

Thanks for considering the patch.
diff -Nru isc-dhcp-4.3.5/debian/control isc-dhcp-4.3.5/debian/control
--- isc-dhcp-4.3.5/debian/control   2017-01-19 12:11:21.0 -0500
+++ isc-dhcp-4.3.5/debian/control   2017-06-07 16:38:45.0 -0400
@@ -1,8 +1,7 @@
 Source: isc-dhcp
 Section: net
 Priority: important
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian ISC DHCP maintainers 

+Maintainer: Debian ISC DHCP maintainers 

 Uploaders: Andrew Pollock , Michael Gilbert 

 Vcs-Git: https://anonscm.debian.org/pkg-dhcp/isc-dhcp.git
 Vcs-Browser: 
https://anonscm.debian.org/gitweb/?p=pkg-dhcp/isc-dhcp.git;a=summary
diff -Nru isc-dhcp-4.3.5/debian/patches/series 
isc-dhcp-4.3.5/debian/patches/series
--- isc-dhcp-4.3.5/debian/patches/series2017-01-19 12:11:21.0 
-0500
+++ isc-dhcp-4.3.5/debian/patches/series2017-06-07 16:38:38.0 
-0400
@@ -32,3 +32,4 @@
 dhcp-improved-xid-correct-byte-order.patch
 dhcp-4.2.4-dhclient-options-changed.patch
 ubuntu-dhcpd-conf.patch
+strip-interface-alias.patch
diff -Nru isc-dhcp-4.3.5/debian/patches/strip-interface-alias.patch 
isc-dhcp-4.3.5/debian/patches/strip-interface-alias.patch
--- isc-dhcp-4.3.5/debian/patches/strip-interface-alias.patch   1969-12-31 
19:00:00.0 -0500
+++ isc-dhcp-4.3.5/debian/patches/strip-interface-alias.patch   2017-06-07 
16:38:38.0 -0400
@@ -0,0 +1,39 @@
+Author: Dan Streetman 
+Description: Since isc-dhcp strips the interface alias from all
+  interfaces it enumerates, when comparing the cmdline interface
+  name to find the matching enumerated interface, the cmdline name
+  must have its alias stripped also.  Without this, DHCPv6 fails
+  when using an interface alias.
+Forwarded: yes
+Bug: [ISC bug tracking is private; bug email has been sent]
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819
+
+
+Index: isc-dhcp-4.3.5/client/dhclient.c
+===
+--- isc-dhcp-4.3.5.orig/client/dhclient.c
 isc-dhcp-4.3.5/client/dhclient.c
+@@ -447,15 +447,19 @@ main(int argc, char **argv) {
+ " requested interface %s", argv[i]);
+   } else {
+   struct interface_info *tmp = NULL;
++  int len;
+ 
+   status = interface_allocate(, MDL);
+   if (status != ISC_R_SUCCESS)
+   log_fatal("Can't record interface %s:%s",
+ argv[i], isc_result_totext(status));
+-  if (strlen(argv[i]) >= sizeof(tmp->name))
+-  log_fatal("%s: interface name too long (is %ld)",
+-argv[i], (long)strlen(argv[i]));
+-  strcpy(tmp->name, argv[i]);
++  /* strip any interface alias, e.g. eth1:1 -> eth1 */
++  len = strchrnul(argv[i], ':') - argv[i];
++  if (len >= sizeof(tmp->name))
++  log_fatal("%s: interface name too long (is %d)",
++argv[i], len);
++  strncpy(tmp->name, argv[i], len);
++  tmp->name[len] = 0;
+   if (interfaces) {
+   interface_reference(>next,
+   interfaces, MDL);

Bug#846548: marked as pending

[Eric Dorland]

* Julien Cristau (jcris...@debian.org) wrote:
> It's now through NEW.  The next step would be an upload to sid, with
> urgency=high, and an unblock request to the release.debian.org
> pseudopackage.

Thanks and done as you have seen. I'm guessing it's not worth it, but
should we promote libp11 0.4.4-1 as well for version parity?

> On 06/06/2017 02:26 AM, Eric Dorland wrote:
> > OK, apologies for the delay (and I know we're getting down to the
> > wire). I just uploaded libp11-openssl1.1 to experimental and of course
> > it's in NEW. If this looks ok let me know what the next steps are if
> > we want to try to get it into stretch.
> > 
> > * Julien Cristau (jcris...@debian.org) wrote:
> >> On 05/30/2017 07:16 AM, Eric Dorland wrote:
> >>> * Julien Cristau (jcris...@debian.org) wrote:
>  On 05/29/2017 03:15 AM, Eric Dorland wrote:
> > * Julien Cristau (jcris...@debian.org) wrote:
> >> On Mon, May 22, 2017 at 03:42:57 +, Eric Dorland wrote:
> >>
> >>> tag 846548 pending
> >>> thanks
> >>>
> >>> Hello,
> >>>
> >>> Bug #846548 reported by you has been fixed in the Git repository. You 
> >>> can
> >>> see the changelog below, and you can check the diff of the fix at:
> >>>
> >>> 
> >>> https://anonscm.debian.org/cgit/pkg-opensc/libp11.git/commit/?id=e8d6da0
> >>>
> >> So, erm.  This seems like it would break using libengine-pkcs11-openssl
> >> in an application using libssl1.0.2.  As a SONAME bump it also seems
> >> rather inappropriate during the freeze.
> >
> > That's a good point. I was trying to provide an alternative to the
> > broken NMU that was going to be uploaded, but yes this will break
> > applications built against libssl1.0.2. It does fix using this with
> > the openssl tool however.
> >
>  Right.
> 
> >> I'm very interested in having this fixed in stretch so I can get the
> >> secure-boot stuff working on ftp-master, but this doesn't look like the
> >> way to go.  Not to mention that you'd have to justify the bump from
> >> 0.4.3 to 0.4.4.
> >>
> >> Can you explain your plans here?
> >
> > As you suggested in your followup, the way forward would appear to be
> > to upload a new libp11 source package that builds against
> > libssl1.0.2. I can also backport all of the changes to 0.4.3 and
> > upload to testing-proposed-updates. Does that sound reasonable?
> >
>  Having read through the 0.4.4 changes I think I'd be ok with getting
>  that in if you're confident.  I guess the other question is should
>  libp11-dev come from the openssl1.1-using package or the
>  openssl1.0.2-using one.  At this late stage I guess it's safer to stay
>  with 1.0.2, and have the libp11-openssl1.1 package (or however it's
>  called) only provide a libengine-pkcs11-openssl1.1 binary?
> >>>
> >>> OK, I like this plan. We should get the naming right going forward
> >>> though for the libengine-pkcs11-openssl1.1 package. Is that how other
> >>> packages are handling naming when they depend on a particular version
> >>> of openssl?
> >>>
> >> I'm not sure, to be honest.  I don't know if there are any other similar
> >> cases right now.  This package name wouldn't survive stretch in any
> >> case, I guess?
> >>
> >>> I should be able to get fixed uploads to unstable in a couple of days.
> >>>
> >> Nice.  Thanks.
> >>
> >> Cheers,
> >> Julien
> > 
> 

-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93

Bug#841028: cups-daemon: cupsd uses 100% CPU

[Samuel Wolf]

2017-06-07 23:47 GMT+02:00 Till Kamppeter :

> The fix prevents the repeated loading of this printer as it considers the
> loading done after the first load.
>
>
Is this update/patch for Stretch available?


>Till
>
>

Bug#864366: CVE-2017-9433

[Moritz Mühlenhoff]

On Wed, Jun 07, 2017 at 11:07:02PM +0200, Rene Engelhard wrote:
> Hi,
> 
> On Wed, Jun 07, 2017 at 06:13:05PM +0200, Moritz Muehlenhoff wrote:
> > Source: libmwaw
> > Severity: grave
> > Tags: security
> > 
> > Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9433
> 
> sid (and thus hopefully stretch assuming will be unblocked, see # -
> otherwise we'd need stretch-security) and experimental done.
> 
> stable diff is here:
> 
> diff -Nru libmwaw-0.3.1/debian/changelog libmwaw-0.3.1/debian/changelog
> --- libmwaw-0.3.1/debian/changelog2014-08-07 23:53:29.0 +0200
> +++ libmwaw-0.3.1/debian/changelog2017-06-07 22:47:24.0 +0200
> @@ -1,3 +1,9 @@
> +libmwaw (0.3.1-2+deb8u1) jessie-security; urgency=medium
> +
> +  * backport upstream patch to fix CVE-2017-9433 (closes: #864366)
> +
> + -- Rene Engelhard   Wed, 07 Jun 2017 22:47:10 +0200
> +
>  libmwaw (0.3.1-2) unstable; urgency=low
>  
>* upload to unstable 
> diff -Nru libmwaw-0.3.1/debian/patches/CVE-2017-9433.diff 
> libmwaw-0.3.1/debian/patches/CVE-2017-9433.diff
> --- libmwaw-0.3.1/debian/patches/CVE-2017-9433.diff   1970-01-01 
> 01:00:00.0 +0100
> +++ libmwaw-0.3.1/debian/patches/CVE-2017-9433.diff   2017-06-07 
> 22:46:57.0 +0200
> @@ -0,0 +1,11 @@
> +--- a/src/lib/MsWrd1Parser.cxx
>  b/src/lib/MsWrd1Parser.cxx
> +@@ -902,7 +902,7 @@
> + int id = fIt++->second;
> + fPos[1] = fIt==footnoteMap.end() ? m_state->m_eot : fIt->first;
> + if (id >= int(m_state->m_footnotesList.size()))
> +-  m_state->m_footnotesList.resize(size_t(id),0);
> ++  m_state->m_footnotesList.resize(size_t(id)+1,0);
> + m_state->m_footnotesList[size_t(id)]=fPos;
> +   }
> +   ascii().addDelimiter(input->tell(),'|');
> diff -Nru libmwaw-0.3.1/debian/patches/series 
> libmwaw-0.3.1/debian/patches/series
> --- libmwaw-0.3.1/debian/patches/series   1970-01-01 01:00:00.0 
> +0100
> +++ libmwaw-0.3.1/debian/patches/series   2017-06-07 22:13:15.0 
> +0200
> @@ -0,0 +1 @@
> +CVE-2017-9433.diff
> 
> Should I upload?

Please go ahead (needs -sa since orig tarball is new)

Cheers,
Moritz

Bug#863802: severity of 863802 is wishlist

[Alexander Wirt]

severity 863802 wishlist
thanks

As discussed, I don't this is a bug.

Bug#841028: cups-daemon: cupsd uses 100% CPU

[Till Kamppeter]

The fix prevents the repeated loading of this printer as it considers 
the loading done after the first load.


   Till

Bug#864382: stretch-pu: mariadb-10.1/10.1.23-9+deb9u1

[Jonathan Wiltshire]

Control: tag -1 confirmed moreinfo

On Wed, Jun 07, 2017 at 09:26:09PM +0200, Andreas Beckmann wrote:
> Please approve package mariadb-10.1
> 
> As suggested by Jonathan,
> here is the proposed debdiff to fix #864159 in mariadb-10.1 via tpu.

Please go ahead.

Thanks,


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#841028: cups-daemon: cupsd uses 100% CPU

[Samuel Wolf]

Hi Till,

2017-06-07 20:20 GMT+02:00 Till Kamppeter :

> On 06/07/2017 03:05 PM, Samuel Wolf wrote:
>
>> Wed Jun  7 20:03:07 2017 Unable to create/modify CUPS queue (Success)!
>>
>
> Here a successful operation was considered an error and this leads to the
> repetition.
>
> I have fixed this already in the 1.13.4 release of cups-filters.
>

this fix also the issue with the 100% CPU load and cups-browsed?
The load coming from the reload of the printers, right?

cups-filters:
  Installiert:   1.11.6-3
  Installationskandidat: 1.11.6-3
  Versionstabelle:
 *** 1.11.6-3 500
500 http://ftp.de.debian.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status

No update for Stretch available.

Samuel


>
>Till
>
>

Bug#863139: mongo-tools FTBFS on arm64: _build/src/github.com/spacemonkeygo/spacelog/capture_other.go:26: undefined: syscall.Dup2

[Edmund Grimley Evans]

The fix is described here:

https://github.com/spacemonkeygo/spacelog/issues/6

Add golang-golang-x-sys-dev to the Build-Depends, and in capture_other.go
replace "syscall" with "golang.org/x/sys/unix",
and each "syscall." with "unix.".

Bug#864366: CVE-2017-9433

[Rene Engelhard]

On Wed, Jun 07, 2017 at 11:07:02PM +0200, Rene Engelhard wrote:
> Hi,
> 
> On Wed, Jun 07, 2017 at 06:13:05PM +0200, Moritz Muehlenhoff wrote:
> > Source: libmwaw
> > Severity: grave
> > Tags: security
> > 
> > Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9433
> 
> sid (and thus hopefully stretch assuming will be unblocked, see # -

Oops.

#864384

Regards,

Rene

Bug#864391: stunnel4: SSL session leak

[Scott Emmons]

Package: stunnel4
Version: 3:5.30-1.1
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Dear Maintainer,

This fixes an SSL session leak present in the version of stunnel4 currently
in jessie-backports (the versions in jessie (main), stretch, and sid are not
subject to this bug). This bug was introduced in stunnel4 5.27, subsequently
fixed in 5.33, leaving the version in jessie-backports (5.30) subject to
the leak (and the version in Ubuntu Xenial, which appears to be the same
version and have the same patchset as jessie-backports).

The bug results in long running stunnel4 processes eventually consuming all
memory.

*** /tmp/tmpjfgeGr/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

With 5.30-1 (the current version in Xenial), the RSS keeps growing. With
this patch applied, RSS grows to around ~13000 and stays there.

It's somewhat difficult to prove the derivation of this patch from
upstream stunnel4, as there is no version control repository for
stunnel4. I made this patch by comparing the source of 5.32 and 5.33,
and ultimately there was just a single line that looked to be relevant -
adding a call to SSL_SESSION_free(). I can't promise this is a full fix,
but it looks promising based on my own testing.

More information in:
   https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1655153

  * Non-maintainer upload.
- Backport fix for TLS session leak introduced in stunnel4 5.27
  from stunnel4 5.33. Fixes launchpad bug 1655153.


Thanks for considering the patch.


-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 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)
diff -Nru stunnel4-5.30/debian/patches/30-fix-ssl-session-leak.patch stunnel4-5.30/debian/patches/30-fix-ssl-session-leak.patch
--- stunnel4-5.30/debian/patches/30-fix-ssl-session-leak.patch	1970-01-01 00:00:00.0 +
+++ stunnel4-5.30/debian/patches/30-fix-ssl-session-leak.patch	2017-06-07 00:30:17.0 +
@@ -0,0 +1,12 @@
+Index: stunnel4-5.30/src/ctx.c
+===
+--- stunnel4-5.30.orig/src/ctx.c
 stunnel4-5.30/src/ctx.c
+@@ -734,6 +734,7 @@ NOEXPORT void sess_remove_cb(SSL_CTX *ct
+ opt=SSL_CTX_get_ex_data(ctx, index_opt);
+ if(opt->option.sessiond)
+ cache_remove(ctx, sess);
++SSL_SESSION_free(sess);
+ }
+ 
+ / sessiond functionality */
diff -Nru stunnel4-5.30/debian/patches/series stunnel4-5.30/debian/patches/series
--- stunnel4-5.30/debian/patches/series	2015-12-03 22:28:57.0 +
+++ stunnel4-5.30/debian/patches/series	2017-06-07 00:29:27.0 +
@@ -4,3 +4,4 @@
 10-no-zlib-compression.patch
 12-restore-pidfile-default.patch
 21-author-tests.patch
+30-fix-ssl-session-leak.patch

Bug#863663: libgstreamer1.0-0: plays MJPEG AVI files (and possibly other formats) at degraded quality

[Francesco Poli]

On Wed, 07 Jun 2017 09:44:02 +0300 Sebastian Dröge wrote:

> On Thu, 2017-06-01 at 23:47 +0200, Francesco Poli wrote:
[...]
> > I tried with
> > 
> >   $ gst-launch-1.0 filesrc location=wave_anim.avi \! avidemux \!
> > avdec_mjpeg \! autovideosink
> >   $ gst-launch-1.0 filesrc location=wave_anim.avi \! avdec_mjpeg \!
> > autovideosink
> > 
> > to no avail.
> > Both pipelines abort with errors (although they spit different error
> > messages).
> 
> The first, but with adding jpegparse between avidemux and avdec_mjpeg
> should work. And potentially adding a videoconvert before
> autovideosink.

Thanks, I can confirm that

  $ gst-launch-1.0 filesrc location=wave_anim.avi \! avidemux \! jpegparse \! 
avdec_mjpeg \! videoconvert \! autovideosink

works as expected (quality nearly identical to mpv and to ffplay).

[...]
> > Which is the feature that corresponds to avdec_mjpeg?
> > Which is the one corresponding to jpegdec?
> 
> You could get them from the registry by exactly those names with
> gst_registry_find_feature(). The type is GST_TYPE_ELEMENT_FACTORY.

Mmmh, I suppose that this is translatable into Vala, if the application
is written in Vala...

At least, by looking at "gstreamer-1.0.vapi", I see that there is a
method named find_feature() in the class Registry of namespace Gst and
a method set_rank() in the class PluginFeature of namespace Gst.
I have to figure out how to use them, since I am not familiar at all
with Vala (are you able to help me, by chance?), but that's another
story!


As an alternative, is there some configuration file that the user can
tweak in order to adjust the ranks of jpegparse and avdec_mjpeg,
without modifying the application that uses the GStreamer library?


I really hope we can find a workaround soon (and, in the meanwhile, I
also hope that the actual bug gets a proper fix).

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpcnfZLcIoCO.pgp
Description: PGP signature

Bug#862228: Patch attached

[Ghislain Vaillant]

control: tags -1 patchFrom 641bcb9cf814f0d8b17d5ead07da82dd22789ae9 Mon Sep 17 00:00:00 2001
From: Ghislain Antony Vaillant 
Date: Wed, 7 Jun 2017 21:16:44 +0100
Subject: [PATCH] Fix XML errors in joy themes

---
 joy-inksplat-theme/gnome-wp-list.xml | 2 --
 joy-theme/gnome-wp-list.xml  | 2 --
 2 files changed, 4 deletions(-)

diff --git a/joy-inksplat-theme/gnome-wp-list.xml b/joy-inksplat-theme/gnome-wp-list.xml
index 5e13ed1..49a07a8 100644
--- a/joy-inksplat-theme/gnome-wp-list.xml
+++ b/joy-inksplat-theme/gnome-wp-list.xml
@@ -2,8 +2,6 @@
 
 
   
-
-  
 Joy Inksplat
 /usr/share/desktop-base/joy-inksplat-theme/wallpaper/gnome-background.xml
 zoom
diff --git a/joy-theme/gnome-wp-list.xml b/joy-theme/gnome-wp-list.xml
index f772b4b..84372fc 100644
--- a/joy-theme/gnome-wp-list.xml
+++ b/joy-theme/gnome-wp-list.xml
@@ -2,8 +2,6 @@
 
 
   
-
-  
 Joy
 /usr/share/desktop-base/joy-theme/wallpaper/gnome-background.xml
 zoom
-- 
2.11.0

Bug#864390: sbuild: world-readable key file for recent versions of apt

[Peter Pentchev]

Package: sbuild
Version: 0.73.0-4+0~roam1
Severity: important
Tags: patch

Hi,

First of all, thanks for maintaining and developing sbuild!

Recent versions of apt started dropping privileges to an _apt
user account; thus, the keyring file that sbuild creates for
use in the chroot is no longer readable by apt, so it issues
a warning, exits with a non-zero code, and breaks the build.

What do you think about the attached two patches?  The second
one fixes the problem itself; the first one is a drive-by fix.

Thanks again for your work on sbuild and Debian in general!

G'luck,
Peter

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sbuild depends on:
ii  adduser 3.115
ii  libsbuild-perl  0.73.0-4+0~roam1
ii  perl5.24.1-3

Versions of packages sbuild recommends:
ii  autopkgtest  4.4
ii  debootstrap  1.0.89
ii  schroot  1.7.2-3

Versions of packages sbuild suggests:
ii  deborphan  1.7.28.8-0.3+b1
ii  kmod   23-2
ii  wget   1.18-5

-- no debconf information
From eec3335c7e62658325e65e56d1ce873382bad499 Mon Sep 17 00:00:00 2001
From: Peter Pentchev 
Date: Wed, 7 Jun 2017 22:28:39 +0300
Subject: [PATCH 1/2] Check the result of a rename() operation

---
 lib/Sbuild/ResolverBase.pm | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/lib/Sbuild/ResolverBase.pm b/lib/Sbuild/ResolverBase.pm
index 24d14643..78f00b75 100644
--- a/lib/Sbuild/ResolverBase.pm
+++ b/lib/Sbuild/ResolverBase.pm
@@ -1383,7 +1383,11 @@ EOF
&$kill_gpgagent();
return 0;
}
-   $session->rename($tmpfilename, $self->get('Dummy archive key file'));
+   if (!$session->rename($tmpfilename, $self->get('Dummy archive key 
file'))) {
+   $self->log("Failed to rename the dummy archive key.\n");
+   &$kill_gpgagent();
+   return 0;
+   }
&$kill_gpgagent();
 }
 
-- 
2.11.0

From 86c5720ba2b8f9a0093ff549ac54541abe837185 Mon Sep 17 00:00:00 2001
From: Peter Pentchev 
Date: Wed, 7 Jun 2017 22:29:48 +0300
Subject: [PATCH 2/2] Make the dummy archive key file world-readable

Recent versions of apt drop privileges by switching to the _apt
user account.
---
 lib/Sbuild/ResolverBase.pm | 5 +
 1 file changed, 5 insertions(+)

diff --git a/lib/Sbuild/ResolverBase.pm b/lib/Sbuild/ResolverBase.pm
index 78f00b75..deb36172 100644
--- a/lib/Sbuild/ResolverBase.pm
+++ b/lib/Sbuild/ResolverBase.pm
@@ -1388,6 +1388,11 @@ EOF
&$kill_gpgagent();
return 0;
}
+   if (!$session->chmod($self->get('Dummy archive key file'), '0644')) {
+   $self->log("Failed to set the permissions on the dummy archive 
key.\n");
+   &$kill_gpgagent();
+   return 0;
+   }
&$kill_gpgagent();
 }
 
-- 
2.11.0



signature.asc
Description: PGP signature

Bug#864356: [Pkg-utopia-maintainers] Bug#864356: Acknowledgement (network-manager: Support for certificate hashes when writing 802.1x configuration.)

[Michael Biebl]

Control: forcemerge -1 864356

Am 07.06.2017 um 16:26 schrieb ebik:
> This was created by invoking 'reportbug -d', thus I assumed,
> that this won't reach debian servers. Corrected version of
> the bugreport is #864357. 

Let's merge the two bug reports.

Would be great if you can forward your patch to upstream.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#864366: CVE-2017-9433

[Rene Engelhard]

Hi,

On Wed, Jun 07, 2017 at 06:13:05PM +0200, Moritz Muehlenhoff wrote:
> Source: libmwaw
> Severity: grave
> Tags: security
> 
> Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9433

sid (and thus hopefully stretch assuming will be unblocked, see # -
otherwise we'd need stretch-security) and experimental done.

stable diff is here:

diff -Nru libmwaw-0.3.1/debian/changelog libmwaw-0.3.1/debian/changelog
--- libmwaw-0.3.1/debian/changelog  2014-08-07 23:53:29.0 +0200
+++ libmwaw-0.3.1/debian/changelog  2017-06-07 22:47:24.0 +0200
@@ -1,3 +1,9 @@
+libmwaw (0.3.1-2+deb8u1) jessie-security; urgency=medium
+
+  * backport upstream patch to fix CVE-2017-9433 (closes: #864366)
+
+ -- Rene Engelhard   Wed, 07 Jun 2017 22:47:10 +0200
+
 libmwaw (0.3.1-2) unstable; urgency=low
 
   * upload to unstable 
diff -Nru libmwaw-0.3.1/debian/patches/CVE-2017-9433.diff 
libmwaw-0.3.1/debian/patches/CVE-2017-9433.diff
--- libmwaw-0.3.1/debian/patches/CVE-2017-9433.diff 1970-01-01 
01:00:00.0 +0100
+++ libmwaw-0.3.1/debian/patches/CVE-2017-9433.diff 2017-06-07 
22:46:57.0 +0200
@@ -0,0 +1,11 @@
+--- a/src/lib/MsWrd1Parser.cxx
 b/src/lib/MsWrd1Parser.cxx
+@@ -902,7 +902,7 @@
+ int id = fIt++->second;
+ fPos[1] = fIt==footnoteMap.end() ? m_state->m_eot : fIt->first;
+ if (id >= int(m_state->m_footnotesList.size()))
+-  m_state->m_footnotesList.resize(size_t(id),0);
++  m_state->m_footnotesList.resize(size_t(id)+1,0);
+ m_state->m_footnotesList[size_t(id)]=fPos;
+   }
+   ascii().addDelimiter(input->tell(),'|');
diff -Nru libmwaw-0.3.1/debian/patches/series 
libmwaw-0.3.1/debian/patches/series
--- libmwaw-0.3.1/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ libmwaw-0.3.1/debian/patches/series 2017-06-07 22:13:15.0 +0200
@@ -0,0 +1 @@
+CVE-2017-9433.diff

Should I upload?

Regards,

Rene

Bug#863838: unblock: debian-edu-install/1.926

[Wolfgang Schweer]

On Wed, Jun 07, 2017 at 10:29:15PM +0200, Cyril Brulebois wrote:
> Jonathan Wiltshire  (2017-06-06):
> > This fixed list really is a bit of a nuisance.  Are you able to commit
> > to not needing it in buster (or preferably before)? I can't speak for
> > d-i, but that might a be a compromise we can reach.
> 
> Works for me.

I've modified the patch proposed earlier; see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863838#47

Then I've built the package from my locally modified git repo and 
installed it on a test system. Tests were ok: the version string was 
modified each time like expected; so I assume that it will work. 

But I propose to do this change for buster rather than now in a hurry.

This is the diff:

diff --git a/debian/debian-edu-install.postinst 
b/debian/debian-edu-install.postinst
index 1f145383..679a0ad6 100644
--- a/debian/debian-edu-install.postinst
+++ b/debian/debian-edu-install.postinst
@@ -115,54 +115,14 @@ fi
 # Source the debconf confmodule to ensure that the templates are loaded.
 . /usr/share/debconf/confmodule
 
-oldversions="sarge \
-  terra_alpha \
-  terra_test01 terra_test02 terra_test03 terra_test04 \
-  terra_pre01 terra_pre02 \
-  terra_rc1 terra_rc2 terra_rc3 terra_rc4 terra_rc5"
-
 # get the current version
 new_version="$(cat /usr/lib/debian-edu-install/version)"
 
 if [ -f $debian_edu_config ] ; then
( # Subshell to avoid importing the variables into the entire script
-   VERSION=""
. $debian_edu_config
-
-   # FIXME: the following code doesn't seem to make any sense and should
-   # be cleaned up post jessie release. It's seems way simpler (and
-   # easier to maintain) to just rewrite /etc/debian-edu/config on
-   # upgrades like it done on installation in pre-pkgsel (from this
-   # package).
-
-   # clean up missing version caused by bug introduced in version
-   # 1.810 and fixed in version 1.813.
-   if [ -z "$VERSION" ] ; then
sed -i $debian_edu_config -e \
"s/^VERSION=.*$/VERSION=\"$new_version\"/"
-   fi
-
-   # Need to list versions with space here, to avoid unwanted
-   # word splitting
-   for i in $oldversions '3.0r0 terra' '3.0r1 terra' '4.0r0 luna alpha1' \
- '5.0r0+edu0 alpha' '5.0.0+edu0 alpha' '5.0.1+edu0 alpha' \
- '5.0.2+edu0 alpha' '5.0.3+edu0 alpha' '5.0.3+edu0 rc1' \
- '5.0.4+edu0 rc2' '5.0.4+edu0' '5.0.6+edu1' '6.0.0+edu0 alpha' 
\
- '6.0.3+edu0 beta1' '6.0.3+edu0 beta2' '6.0.3+edu0 beta3' \
- '6.0.4+edu0 beta3' '6.0.4+edu0 rc1' '6.0.4+edu0 rc2' \
-'6.0.4+edu0 rc3' '6.0.4+edu+r0' '6.0.7+edu+r1' \
-'7.0.0+edu+alpha0' '7.0.0+edu+alpha2' '7.0.0+edu+alpha3' \
-'7.1+edu0~a3' '7.1+edu0~b0' '7.1+edu0~b1' '7.1+edu0~b2' \
-'7.1+edu0' '8.0.0+edu+alpha0' '8.0+edu+alpha0' \
-'8.0+edu0~alpha0' '8.0+edu0~alpha1' '8.0+edu0~alpha2' \
-'8.0+edu0~beta1' '8+edu0' '9+edu0~alpha0' '9+edu0~a0'
-
-   do
-   if [ "$VERSION" = "$i" ] ; then
-   sed -i $debian_edu_config -e \
-   "s/^VERSION=.*$/VERSION=\"$new_version\"/"
-   fi
-   done
)
 fi
 

Wolfgang


signature.asc
Description: PGP signature

Bug#846499: qstopmotion: FTBFS: tries to compare va_list to NULL

[Edmund Grimley Evans]

The comparison makes no sense on any arch. Just replace "if (args !=
NULL)" with "if (1)".
It then builds on arm64.

Bug#853013:

[Michael Hudson-Doyle]

I found this too and while I don't really understand how this test ever
passes, I have a proposed fix upstream:
https://github.com/urwid/urwid/pull/238 which I have just uploaded to ubuntu

Bug#853750: hdfview version 3

[Peter Würtz]

Hi,
I ran into the same issue on Ubuntu. After searching the hdfgroup websites
for a while I found a link to the beta release of the upcoming version 3.0
of hdfview. This version is designed to work with the new 64bit-object
libraries.

Announcement of the beta release:
https://support.hdfgroup.org/products/java/release/hdfview3.html
https://support.hdfgroup.org/newsletters/newsletter154.pdf

The beta is s a source-only release. The correct link to the source is:
https://support.hdfgroup.org/ftp/HDF5/releases/HDF-JAVA/hdfview-3.0.0/src/hdfview-3.0.0.tar.gz

So theoretically, version 3 of hdfview should fix the problem.
Unfortunately the build system fails on my machine, being unable to find
the hdf libraries installed via apt.

Bug#864383: unblock: libp11-openssl1.1/0.4.4-4

[Julien Cristau]

On 06/07/2017 04:45 PM, Eric Dorland wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package libp11-openssl1.1
> 
> This is a new package which is adds only pkcs11 engine support for openssl 
> 1.1.
> Without this the change it can't be used with openssl 1.1 only with openssl
> 1.0.2 and since the openssl command is coming from 1.1 without this it would 
> be a functionality regression in stretch.
> 
> Full context in #846548.
> 
Unblocked, with a 3-day delay so anyone can still object or amend.

Cheers,
Julien

Bug#862580: Bug #862580: Winbind crashes on ssh login of a domain user.

[Christian Meyer]

Hello Louis
and thank you for your very long tutorial.
I tried to fix my 'wrong' smb.conf on my existing machine but that gave
trouble.
So I tried to setup a fresh stretch box step by step (had to change some
things but I had a look at
https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member,
too) but after some days and a reboot I see the problem again, it just
appears less often till now.

CONFIG
==
> Setup jessie: 
I did stretch.
> # Choose expert install, and at taskselect choose only ssh server.
I did so and used dhcp:

$ cat /etc/hosts
127.0.0.1   localhost
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

$ cat /etc/resolv.conf
domain WORK.COMPANY
search WORK.COMPANY
nameserver 172.16.0.2

$ cat /etc/network/interfaces.
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug enp0s25
iface enp0s25 inet dhcp


> # Check all these. 
$ hostname -s
sambawb
$ hostname -d
WORK.COMPANY
$ hostname -f
sambawb.WORK.COMPANY
$ hostname -i
172.16.0.209

> # install samba winbind and needed extras. 
> apt-get install samba smbclient samba-dsdb-modules samba-vfs-modules
winbind libpam-winbind libnss-winbind krb5-user ntp bind9-host
libpam-krb5
I did so.

> When questions come, fill in :
No questions came.
> # AD DC ipnumbers at ntp questions 
added 'server 172.16.0.2 iburst' to /etc/ntp.conf (thats my AD DC
ipnumber)
> # krb5-user fill in your REALM in CAPS.  ! CAPS YES ! 
$ cat /etc/krb5.conf
[libdefaults]
default_realm = WORK.COMPANY

> # Change your /etc/nsswitch.conf
$ cat /etc/nsswitch.conf
passwd: compat winbind
group:  compat winbind
shadow: compat
gshadow:files
hosts:  files dns
networks:   files
protocols:  db files
services:   db files
ethers: db files
rpc:db files
netgroup:   nis

# kinit administrator
worked great.

> Setup a "correct smb.conf" like this one.
I don't know whats "correct" in your sense. I did:

## -- START AD MEMBER SMB.CONF - ## 
# /etc/samba/smb.conf
[global]
   security = ads
   realm = WORK.COMPANY
   workgroup = WORK

   netbios name = sambawb

   preferred master = no
   domain master = no
   host msdfs = no
  # speeds up name resolving, (WINS), through dns.
   dns proxy = yes
#   local master = no


   # I left out bind interfaces
   #bind interfaces only = yes
   #interfaces = enp0s25 127.0.0.1


   # I've added these, mustly same as the defaults, but this explains things 
for others 
   # if they have auth problems. 
   # mandatory will still require SMB2 clients to use signing
server signing = mandatory

   #  if ntlm and lanman auth are both disabled, then only NTLMv2 logins will 
be permited
ntlm auth = no
lanman auth = no

   # TODO: I skipped TLS keys!

   name resolve order = lmhosts host bcast

   idmap config * : backend = tdb
   idmap config * : range = 2000-
  # https://wiki.samba.org/index.php/Idmap_config_rid
   idmap config WORK : backend = rid
   idmap config WORK : range = 1-99

template homedir = /home/%D/%U
template shell = /bin/bash
winbind nss info = template

# renew the kerberos ticket
winbind refresh tickets = yes

# Changed to not use winbind trusted domains only
winbind trusted domains only = no
# and to use default domain
winbind use default domain = yes

winbind enum groups = yes
winbind enum users = yes

# Enable offline logins, if needed. I don't want it.
winbind offline logon = no
# left out: winbind max domain connections = 10

kerberos method = secrets and keytab
dedicated keytab file = /etc/krb5.keytab

winbind expand groups = 4

# User Administrator workaround, without it you are unable to set
# username map = /etc/samba/samba_usermapping

# disable usershares creating, no log errors.
usershare path =

# Disable printing completely, no log errors. 

# Disable printing completely, no log errors. 
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes

# For ACL support on member servers with shares (oblicated member
setting)
vfs objects = acl_xattr
map acl inherit = Yes
store dos attributes = Yes

# Share Setting Globally
veto files = /.bash_logout/.bash_profile/.bash_history/.bashrc/
hide unreadable = yes

# From debian default config: 
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# Do something sensible when Samba crashes: mail the admin
   panic action = /usr/share/samba/panic-action %d
## -- END AD MEMBER SMB.CONF - ## 

> net ads join -S hostname-DC.work.company -k

Bug#864389: squid: Regression - after upgrade, squid takes over minute to display a web page

[Peter Tuharsky]

Package: squid
Version: 3.5.23-4
Severity: important

Dear Maintainer,

I have been using squid for several weeks on my PC. Now it takes over minute to
display a web page. During the time, the page is not listed in log, only when
it is finally displayed, and I don't see any error there either. So it seems
that squid simply waits for something to time out. I would guess that problem
is related to some system update from previous week.



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

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

Versions of packages squid depends on:
ii  adduser  3.115
ii  libc62.24-11
ii  libcap2  1:2.25-1
ii  libcomerr2   1.43.4-2
ii  libdb5.3 5.3.28-12+b1
ii  libdbi-perl  1.636-1+b1
ii  libecap3 1.0.1-3.2
ii  libexpat12.2.0-2
ii  libgcc1  1:6.3.0-18
ii  libgssapi-krb5-2 1.15-1
ii  libkrb5-31.15-1
ii  libldap-2.4-22.4.44+dfsg-5
ii  libltdl7 2.4.6-2
ii  libnetfilter-conntrack3  1.0.6-2
ii  libnettle6   3.3-1+b1
ii  libpam0g 1.1.8-3.6
ii  libsasl2-2   2.1.27~101-g0780600+dfsg-3
ii  libstdc++6   6.3.0-18
ii  libxml2  2.9.4+dfsg1-2.2
ii  logrotate3.11.0-0.1
ii  lsb-base 9.20161125
ii  netbase  5.4
ii  squid-common 3.5.23-4

Versions of packages squid recommends:
ii  libcap2-bin  1:2.25-1

Versions of packages squid suggests:
pn  resolvconf   
pn  smbclient
pn  squid-cgi
pn  squid-purge  
pn  squidclient  
pn  ufw  
pn  winbindd 

-- Configuration Files:
/etc/squid/squid.conf changed [not included]

-- no debconf information

Bug#864364: freemat: toolbox missing diff() and run_tests()

[Graham Inggs]

Control: tags -1 + pending

These files are not very big, so instead of generating a new tarball,
we can restore them with a patch until the next upstream release.  I
have pushed this to git [1], as well updating Files-Excluded, and
enabling the diff() and hist() tests.
Please let me know if you have any objections to this approach.

[1] 
https://anonscm.debian.org/cgit/debian-science/packages/freemat.git/commit/?id=0b8cf010e3f58afe222a36b644c896d77ed945e6

Bug#864260: Missing kernel in debian-installer sd-card images for armhf (stretch)

[Cyril Brulebois]

Karsten Merker  (2017-06-07):
> I have done test builds with both 50MB and 100MB raw image size. 
> The difference in the resulting compressed binary size is less
> than 60kBytes, so that shouldn't pose a problem even for people
> on very-low-bandwidth internet connections.  I suppose the
> additional write time to the target medium also isn't much of a
> problem either.  On modern SD cards, linear write rates are nearly
> always larger than 5MB per second (even cheap SD cards nowadays
> commonly reach nearly 10MB/s on linear writes), so setting the
> image size to 100MB costs at most 10 seconds of extra write time. 
> That shouldn't be a problem even for CI systems that do lots of
> image writes.
> 
> If the size increase eases debugging, I think it is worth that
> cost, so I'll commit a change to ~100MB to d-i git.

Oh, I failed to notice your mail when I wrote the one I've just sent.
Since you're fine with 100, let's go for it; I just needed a fix to be
committed before the upload (which should happen in a few hours), that's
why I was going for a temporary decision. All the better if you're fine
with the suggested new value. :)

Thanks!


KiBi.


signature.asc
Description: Digital signature

Bug#864181: Fwd: Bug#864181: os-prober: dmraid detection not functional.

[Mike Mestnik]

In that case the proposed patch is wrong, dmraid is run every time the
file exists.  Not only is the conditional in test wrong, but the file
is created when it should be being removed.

Bug#864388: pulseaudio: Regression - sound audibly distorted for Creative Soundblaster Live

[Peter Tuharsky]

Package: pulseaudio
Version: 10.0-1
Severity: normal

Dear Maintainer,

I have Creative Soundblaster Live PCI soundcard that I have been gladly using
for years. With Debian Jessie it still works fine. However, with Stretch there
is audible distortion on any playback, regardless on PCM or general volume. The
original sound is audible and articulated, however the distortion makes it
unpleasant.

I have tested playing the same files from command line on tty1 console using
"play" command, and the sound is OK from there. So it seems that kernel driver
is OK and only GNOME sound is affected, therefore I suspect Pulseaudio to be
the centre of trouble.

Tested with three different pieces of SB Live card of different branches, and
on two PCs.

Please, what could I do to workaround the problem until it gets fixed in
Debian?



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


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

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

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-11
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.18-1
ii  libgcc1  1:6.3.0-18
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.27-3
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-18
ii  libsystemd0  232-24
ii  libtdb1  1.3.11-2
ii  libudev1 232-24
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 10.0-1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4+b1

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
pn  pavucontrol  
pn  pavumeter
ii  udev 232-24

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

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

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

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

; cookie-file =

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

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

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

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

Bug#864368: Expand kernel serial port configuration

[Dave Hansen]

On 06/07/2017 01:14 PM, Ben Hutchings wrote:
> On Wed, 2017-06-07 at 18:10 +0100, Ben Hutchings wrote:
>>> CONFIG_SERIAL_8250_RUNTIME_UARTS=16
>> That seems reasonable.
> [...]
> 
> Actually, having looked further at what this does, I'm unconvinced
> about changing it.  It can always be overridden through the
> '8250.nr_uarts' kernel parameter where needed.

On my system, this meant that I could not use the serial console to do
an install.  Doing console=ttyS4 on the command-line didn't work because
the kernel didn't support anything after ttyS3.

I guess we could also teach folks to add nr_uarts=8 (or whatever) to
their kernel command-line, which also works around this.  But, it would
be handy to have it work by default.

I don't think there's really any overhead to raising 'nr_uarts', either.
 It makes some (unimportant) loops longer, but I don't think there's any
real downsides.

FWIW, a lot of distros make it pretty large.  My Ubuntu desktop has it
set to 48 and Fedora evidently sets it to 32.

Bug#863140: libretro-desmume FTBFS everywhere except armhf and x86: src/utils/AsmJit/x86/x86cpuinfo.cpp:151:56: error: impossible constraint in asm

[Edmund Grimley Evans]

I was able to build this package on arm64 by disabling the "JIT" as follows.
Please implement something similar in the next upload.

--- libretro-desmume-0.9.11+git20160819+dfsg1.orig/debian/rules
+++ libretro-desmume-0.9.11+git20160819+dfsg1/debian/rules
@@ -12,11 +12,15 @@
 PLATFORM=platform="armv hardfloat"
 endif

+ifneq (,$(filter-out amd64 armhf i386 %-amd64 %-i386 x32, $(ARCH)))
+NO_JIT=DESMUME_JIT=0
+endif
+
 %:
 dh $@ --sourcedirectory=desmume/

 override_dh_auto_build:
-dh_auto_build -- -f Makefile.libretro $(PLATFORM)
+dh_auto_build -- -f Makefile.libretro $(PLATFORM) $(NO_JIT)

 override_dh_auto_clean:
 dh_auto_clean -- -f Makefile.libretro

Bug#864260: Missing kernel in debian-installer sd-card images for armhf (stretch)

[Cyril Brulebois]

Cyril Brulebois  (2017-06-07):
> I'm fine with whatever value is determined by consensus among arm
> people.
> 
> Currently testing a patch to detect full disk (it's been in our build
> logs for months…).

As mentioned a couple hours ago, patches were pushed for that, and I've
also verified that the 40k to 50k bump is sufficient. We can experiment
with a higher value (like the proposed 100k) in unstable, and maybe
backport the bump in a stretch point release, but I'll go for a minimal
bump that is sufficient for all builds for the time being.

Thanks everyone for your collective input. Feel free to discuss the
merits of a bump to a given specific value in a bug report against
src:debian-installer, for further action.


KiBi.


signature.asc
Description: Digital signature

Bug#863838: unblock: debian-edu-install/1.926

[Cyril Brulebois]

Jonathan Wiltshire  (2017-06-06):
> This fixed list really is a bit of a nuisance.  Are you able to commit
> to not needing it in buster (or preferably before)? I can't speak for
> d-i, but that might a be a compromise we can reach.

Works for me.

(Please cc me if you want to make sure I read your replies.)


KiBi.


signature.asc
Description: Digital signature

Bug#864361: release-notes: Add LXQt 0.11 as new desktop environment in Stretch

[陳昌倬]

On Wed, Jun 07, 2017 at 04:16:43PM +0100, Justin B Rye wrote:
> ChangZhuo Chen wrote:
> Preferably with a "Harvard comma" before the "and".
> 
> The Debian version of LXQt appears to be "13".  How does that relate
> to the "LXQt 0.11" released last September?

LXQt is just a meta package, not a upstream package, so its version does
not related to upstream. Most of the lxqt-* packages now are upstream
version 0.11.1 [0].

But I think unversion is also okay to avoid confusion.

[0] 
https://qa.debian.org/developer.php?email=pkg-lxqt-devel%40lists.alioth.debian.org

> Meanwhile, does LXDE not use numbered releases?  The versioning on the
> metapackages just calls it "9", whereas wiki.lxde.org says the latest
> version is "0.99.2".
> 
> Also, isn't "KDE" officially the name of the development project
> rather than the desktop environment (which is "Plasma")?

I am not familiar with KDE, but someone else mentioned this problem in
debian-release list [1], so I guess "KDE Plasma 5.8" is preferable.

[1] https://lists.debian.org/debian-release/2017/06/msg00328.html

> And finally, what sort of ordering is this?  Is there any reason not
> to list them alphabetically?
> 
> So maybe it should be something like:
> 
>   GNOME 3.22, KDE Plasma 5.8, LXDE, LXQt, MATE 1.16, and Xfce 4.12.
> 


-- 
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#864368: Expand kernel serial port configuration

[Ben Hutchings]

On Wed, 2017-06-07 at 18:10 +0100, Ben Hutchings wrote:
> Control: reassign -1 src:linux 4.9.30-1
> Control: severity -1 important
> 
> On Wed, 2017-06-07 at 09:38 -0700, Dave Hansen wrote:
> [...]
> > Please raise:
> > 
> > CONFIG_SERIAL_8250_RUNTIME_UARTS
> > 
> > to something larger, perhaps 16 or 8, such as:
> > 
> > CONFIG_SERIAL_8250_RUNTIME_UARTS=16
> 
> That seems reasonable.
[...]

Actually, having looked further at what this does, I'm unconvinced
about changing it.  It can always be overridden through the
'8250.nr_uarts' kernel parameter where needed.

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.



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

Bug#864386: live-build: Keyboard shortcut for "Advanced options" missing in some syslinux-based menus

[Daniel Reichelt]

Package: live-build
Version: 1:20170213
Severity: minor
Tags: patch


Hi,

the attached patch streamlines the missing keyboard shortcut "A" for the
"Advanced options" entry in the syslinux-based boot menu configs.


Thanks

Daniel
diff --git a/share/bootloaders/extlinux/menu.cfg b/share/bootloaders/extlinux/menu.cfg
index d2daa80..9368260 100644
--- a/share/bootloaders/extlinux/menu.cfg
+++ b/share/bootloaders/extlinux/menu.cfg
@@ -6,7 +6,7 @@ include stdmenu.cfg
 include live.cfg
 include install.cfg
 menu begin advanced
-	menu title Advanced options
+	menu title ^Advanced options
 	include stdmenu.cfg
 	label mainmenu
 		menu label ^Back..
diff --git a/share/bootloaders/isolinux/menu.cfg b/share/bootloaders/isolinux/menu.cfg
index d2daa80..9368260 100644
--- a/share/bootloaders/isolinux/menu.cfg
+++ b/share/bootloaders/isolinux/menu.cfg
@@ -6,7 +6,7 @@ include stdmenu.cfg
 include live.cfg
 include install.cfg
 menu begin advanced
-	menu title Advanced options
+	menu title ^Advanced options
 	include stdmenu.cfg
 	label mainmenu
 		menu label ^Back..
diff --git a/share/bootloaders/pxelinux/menu.cfg b/share/bootloaders/pxelinux/menu.cfg
index d2daa80..9368260 100644
--- a/share/bootloaders/pxelinux/menu.cfg
+++ b/share/bootloaders/pxelinux/menu.cfg
@@ -6,7 +6,7 @@ include stdmenu.cfg
 include live.cfg
 include install.cfg
 menu begin advanced
-	menu title Advanced options
+	menu title ^Advanced options
 	include stdmenu.cfg
 	label mainmenu
 		menu label ^Back..

Bug#864387: please update Yacas to version 1.6.1

[Adam Dingle]

Package: yacas
Version: 1.3.6-2

Debian unstable currently includes Yacas 1.3.6, which is 2-1/2 years 
old. Please update to the latest version, 1.6.1:


http://www.yacas.org/getting_started/downloads/

Bug#864385: live-boot: fix file duplication in initramfs-tools hook

[Daniel Reichelt]

Package: live-boot
Version: 1:20170112
Severity: minor
Tags: patch

Hi,

live-boot's initramfs-hook contains these lines ([1], [2]), which put
live-boot's /lib/live/boot/ twice into the initramfs image: the latter one at
/lib/live/boot/ and the former one - wrongly - also at /bin/boot/).


The duplication was introduced by [3] and is fixed by this patch to read

8<-
cp -a /bin/live-boot "${DESTDIR}/bin"
>8-


There were no problems in multiple testing scenarios (including booting from
the ISO and via PXE).


Thanks,

Daniel




[1]
https://anonscm.debian.org/cgit/debian-live/live-boot.git/tree/backend/initramfs-tools/live.hook#n31

[2]
https://anonscm.debian.org/cgit/debian-live/live-boot.git/tree/backend/initramfs-tools/live.hook#n34

[3]
https://anonscm.debian.org/cgit/debian-live/live-boot.git/commit/backend/initramfs-tools/live.hook?id=0aa07bd386f516176364e710e8b9132036c72986
diff --git a/backend/initramfs-tools/live.hook b/backend/initramfs-tools/live.hook
index 54a566f..889809a 100755
--- a/backend/initramfs-tools/live.hook
+++ b/backend/initramfs-tools/live.hook
@@ -28,7 +28,7 @@ fi
 [ "${QUIET}" ] || echo -n " core"
 
 mkdir -p "${DESTDIR}/bin"
-cp -a /bin/live-boot /lib/live/boot "${DESTDIR}/bin"
+cp -a /bin/live-boot "${DESTDIR}/bin"
 
 mkdir -p "${DESTDIR}/lib/live"
 cp -a /lib/live/boot "${DESTDIR}/lib/live"

Bug#847566: ITP: libolm -- An implementation of the Double Ratchet cryptographic ratchet written in C and C++11 and exposed as a C API

[Hubert Chathi]

owner 847566 uho...@debian.org
retitle 847566 ITP: libolm -- An implementation of the Double Ratchet 
cryptographic ratchet written in C and C++11 and exposed as a C API
thanks

I should be able to package this.

Bug#864384: unblock: libmwaw/0.3.9-2

[Rene Engelhard]

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

Please unblock (and age-days...) package libmwaw

Fixes a (security) bug found by fuzzing: CVE-2017-9433.
See #864366

Debdiff:

diff -Nru libmwaw-0.3.9/debian/changelog libmwaw-0.3.9/debian/changelog
--- libmwaw-0.3.9/debian/changelog  2016-11-23 22:47:03.0 +0100
+++ libmwaw-0.3.9/debian/changelog  2017-06-07 21:47:49.0 +0200
@@ -1,3 +1,9 @@
+libmwaw (0.3.9-2) unstable; urgency=medium
+
+  * apply upstream patch to fix CVE-2017-9433 (closes: #864366)
+
+ -- Rene Engelhard   Wed, 07 Jun 2017 21:47:49 +0200
+
 libmwaw (0.3.9-1) unstable; urgency=medium
 
   * Imported Upstream version 0.3.9
diff -Nru libmwaw-0.3.9/debian/patches/CVE-2017-9433.diff 
libmwaw-0.3.9/debian/patches/CVE-2017-9433.diff
--- libmwaw-0.3.9/debian/patches/CVE-2017-9433.diff 1970-01-01 
01:00:00.0 +0100
+++ libmwaw-0.3.9/debian/patches/CVE-2017-9433.diff 2017-06-07 
21:47:49.0 +0200
@@ -0,0 +1,11 @@
+--- a/src/lib/MsWrd1Parser.cxx
 b/src/lib/MsWrd1Parser.cxx
+@@ -902,7 +902,7 @@
+ int id = fIt++->second;
+ fPos[1] = fIt==footnoteMap.end() ? m_state->m_eot : fIt->first;
+ if (id >= int(m_state->m_footnotesList.size()))
+-  m_state->m_footnotesList.resize(size_t(id),MWAWVec2l(0,0));
++  m_state->m_footnotesList.resize(size_t(id)+1,MWAWVec2l(0,0));
+ m_state->m_footnotesList[size_t(id)]=fPos;
+   }
+   ascii().addDelimiter(input->tell(),'|');
diff -Nru libmwaw-0.3.9/debian/patches/series 
libmwaw-0.3.9/debian/patches/series
--- libmwaw-0.3.9/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ libmwaw-0.3.9/debian/patches/series 2017-06-07 21:47:49.0 +0200
@@ -0,0 +1 @@
+CVE-2017-9433.diff

unblock libmwaw/0.3.9-2

Regards,

Rene

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

Kernel: Linux 3.18.0-trunk-rpi2 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#864373: unblock: ycmd/0+20161219+git486b809-2.1

[Adrian Bunk]

Control: tags -1 - moreinfo

On Wed, Jun 07, 2017 at 07:36:26PM +0100, Jonathan Wiltshire wrote:
> Control: tag -1 moreinfo
> 
> On Wed, Jun 07, 2017 at 08:53:14PM +0300, Adrian Bunk wrote:
> > +ycmd (0+20161219+git486b809-2.1) unstable; urgency=medium
> > +
> > +  * Non-maintainer upload.
> > +  * Run fewer tests on mipsel and mips64el, some fail on Loongson buildds.
> > +(Closes: #852962)
> 
> Perhaps I misunderstood, but I thought the intention was simply to
> blacklist the loongson builders so that all tests can still be run?

That was a question to the release team that was as far as I am aware 
never definitely answered.

And I assumed you would have tarred and feathered me if I had asked 
again on #debian-release to get an answer.

"(small?) part of the functionality of a package is broken on a subset 
of the supported machines on two architectures" is not usually 
considered release critical, the only release critical issue was
that this also caused frequent FTBFS.

Blacklisting the Loongson buildds or disabling part of the tests in all 
mipsel/mips64el builds are two possible workarounds for this FTBFS.

> What's the impact of not unblocking this, considering the other changes
> behind it? I presume #861483 would prevent an update in stretch, but I
> want to be sure I understand correctly.

#861483 and #852962 are both stretch-will-remove.

> Thanks,

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#864181: Fwd: Bug#864181: os-prober: dmraid detection not functional.

[Philip Hands]

Mike Mestnik  writes:

> This does look better, I love the use of operators over if statements.
> I don't think using a temp file is necessary here.  I also wish the
> regex wouldn't ever match a device containing the name of another
> device, in that it should match the surrounding bits.
>
> { dmraid -r -c 2>/dev/null || true } | grep -q "$device" && return 0

The use of the temporary file is there to stop the repeated running of
dmraid, which was the sole purpose of the commit that introduced the
bug, so if one gets rid of that one might as well just revert that
commit.

I agree that there appears to be the potential for $device to match
inappropriately, but I'd need to know something about what dmraid
outputs in order to improve on the grep (I don't have a sataraid machine
to test it on).  Adding a -F option might be a good start.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#864383: unblock: libp11-openssl1.1/0.4.4-4

[Eric Dorland]

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

Please unblock package libp11-openssl1.1

This is a new package which is adds only pkcs11 engine support for openssl 1.1.
Without this the change it can't be used with openssl 1.1 only with openssl
1.0.2 and since the openssl command is coming from 1.1 without this it would 
be a functionality regression in stretch.

Full context in #846548.

No debdiff since this is a new package.

unblock libp11-openssl1.1/0.4.4-4

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

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

Bug#863956: unblock: golang-1.7/1.7.6-1, golang-1.8/1.8.3-1

[Hilko Bengen]

* Jonathan Wiltshire:

> Control: tag -1 wontfix
>
> On Wed, Jun 07, 2017 at 12:29:43AM +0200, Hilko Bengen wrote:
>> * Jonathan Wiltshire:
>> 
>> > Forgive my short memory, but are there any implication for packages built
>> > with golang? I recall some rebuild dragons there.
>> 
>> Yes, there are such implications.
>
> Sorry, but there is absolutely zero chance we're rebuilding that many
> packages at this stage unless it's a release blocker. To be honest I'm
> surprised even to receive such a request.

Hi Jonathan,

no packages were "Built-Using golang-1.8" -- shouldn't it be possible to
migrate that package?

I'm sorry for not including or even thinking about this information for
my initial request (mistake #1).

By using a too simple grep-dctrl query (mistake #2), I included source
packages that only generate golang-*-dev packages which are
"Architecture: all" and which only contain a copy of the source code in
/usr/share/gocode. There is no need to rebuild those packages.

Using a query that ignores the "Architecture: all" packages...

,
| apt-cache dumpavail | \
| grep-dctrl \
| -F Built-Using 'golang-1.7' -a \
| '(' --not -F Architecture all ')' \
| -s Source,Package,Version
`

... my count for the number of source packages drops from 107 to 63, see
below. This still is too much, right?

In any case, is there going to be a way to rebuild/update those
remaining 63 source packages via a point release?

Cheers,
-Hilko

Source: acmetool (0.0.58-5)
Package: acmetool
Version: 0.0.58-5+b1

Source: chasquid (0.01+git20161124.6479138-2)
Package: chasquid
Version: 0.01+git20161124.6479138-2+b2

Package: coyim
Version: 0.3.7-3

Source: dh-make-golang (0.0~git20161120.0.71f5e23-1)
Package: dh-make-golang
Version: 0.0~git20161120.0.71f5e23-1+b2

Source: dnss (0.0~git20161126.0.162090e-1)
Package: dnss
Version: 0.0~git20161126.0.162090e-1+b2

Source: etcd-fs (0.0+git20140621.0.395eacb-1)
Package: etcd-fs
Version: 0.0+git20140621.0.395eacb-1+b2

Source: fuji (1.0.2-1)
Package: fuji
Version: 1.0.2-1+b2

Source: gb (0.4.2-2)
Package: gb
Version: 0.4.2-2+b2

Source: gitlab-workhorse (0.8.5+debian-3)
Package: gitlab-workhorse
Version: 0.8.5+debian-3+b2

Source: go-md2man (1.0.6+ds-1)
Package: go-md2man
Version: 1.0.6+ds-1+b1

Source: go-mtpfs (0.0~git20150917.0.bc7c0f7-1)
Package: go-mtpfs
Version: 0.0~git20150917.0.bc7c0f7-1+b2

Source: gobgp (1.15-1)
Package: gobgpd
Version: 1.15-1+b1

Source: gocryptfs (1.2-2)
Package: gocryptfs
Version: 1.2-2+b1

Source: goiardi (0.11.2-2)
Package: goiardi
Version: 0.11.2-2+b2

Source: golang-bindata (3.0.7+git20151023.72.a0ff256-1)
Package: go-bindata
Version: 3.0.7+git20151023.72.a0ff256-1+b2

Source: golang-github-appc-spec (0.8.9+dfsg-1)
Package: appc-spec
Version: 0.8.9+dfsg-1+b1

Source: golang-github-cloudflare-redoctober
(0.0~git20161017.0.78e9720-1)
Package: golang-redoctober
Version: 0.0~git20161017.0.78e9720-1+b2

Source: golang-github-docker-docker-credential-helpers
(0.3.0+git20160601.0.5128fa1-1)
Package: golang-docker-credential-helpers
Version: 0.3.0+git20160601.0.5128fa1-1+b2

Source: golang-github-eknkc-amber (0.0~git20161231.0.9be5e8a-1)
Package: amber
Version: 0.0~git20161231.0.9be5e8a-1+b1

Source: golang-github-geertjohan-go.rice (0.0~git20160123.0.0f3f5fd-2)
Package: golang-rice
Version: 0.0~git20160123.0.0f3f5fd-2+b1

Source: golang-github-gucumber-gucumber (0.0~git20160715.0.71608e2-1)
Package: gucumber
Version: 0.0~git20160715.0.71608e2-1+b2

Source: golang-github-hpcloud-tail (1.0.0+git20160415.b294095-3)
Package: gotail
Version: 1.0.0+git20160415.b294095-3+b2

Source: golang-github-masterzen-winrm (0.0~git20160323.0752679-3)
Package: winrm
Version: 0.0~git20160323.0752679-3+b1

Source: golang-github-miekg-mmark (1.3.4+git20161103.9.2d4f1dd+dfsg-1)
Package: mmark
Version: 1.3.4+git20161103.9.2d4f1dd+dfsg-1+b1

Source: golang-github-nicksnyder-go-i18n (1.7.0-1)
Package: goi18n
Version: 1.7.0-1+b1

Source: golang-github-opencontainers-image-spec (1.0.0~rc2+dfsg-1)
Package: oci-image-tool
Version: 1.0.0~rc2+dfsg-1+b2

Source: golang-github-pelletier-go-toml (0.4.0+git20161213.2.017119f-1)
Package: golang-github-pelletier-go-toml
Version: 0.4.0+git20161213.2.017119f-1+b1

Source: golang-github-spf13-cobra (0.0~git20161229.0.1dd5ff2-1)
Package: cobra
Version: 0.0~git20161229.0.1dd5ff2-1+b2

Source: golang-github-vbatts-tar-split (0.9.13-1)
Package: tar-split
Version: 0.9.13-1+b2

Source: golang-github-xenolf-lego (0.3.1-4)
Package: lego
Version: 0.3.1-4+b3

Source: golang-github-xordataexchange-crypt
(0.0.2+git20150523.17.749e360-4)
Package: golang-github-xordataexchange-crypt
Version: 0.0.2+git20150523.17.749e360-4+b2

Source: golang-github-yosssi-ace (0.0.4+git20160102.51.71afeb7-1)
Package: ace
Version: 0.0.4+git20160102.51.71afeb7-1+b2

Source: golang-glide (0.12.3-2)
Package: golang-glide
Version: 0.12.3-2+b3

Source: golang-golang-x-tools (1:0.0~git20161028.0.b814a3b+ds-4)
Package: golang-golang-x-tools
Version: 

Bug#853034: patches Re: unar: Fuzzer-generated crashing testcases for a dozen identified file formats

[Julián Moreno Patiño]

Hello YOSHINO Yoshihito,

Unfortunately after test the new unar binary is failing to extract
some kind of files, may be is related to the upstream changes. Please
test to extract these files with unstable version:

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=859346;filename=rar-files.tar.gz;msg=22

Only fails rar13.rar and rar50.rar files.

In the new unar binary only extract rar20.rar file.

I think that there is a regression about fix crashes in some files.

Kind regards,

-- 
Julián Moreno Patiño
Debian Developer
 .''`. Debian GNU/{Linux,KfreeBSD}
: :' : Free Operating Systems
`. `'  http://debian.org/
  `-   GPG Fingerprint:
C2C8 904E 314C D8FA 041D 9B00 D5FD FC15 6168 BF60
Registered GNU Linux User ID 488513

Bug#864382: stretch-pu: mariadb-10.1/10.1.23-9+deb9u1

[Andreas Beckmann]

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

Please approve package mariadb-10.1

As suggested by Jonathan,
here is the proposed debdiff to fix #864159 in mariadb-10.1 via tpu.

Andreas

approve mariadb-10.1/10.1.23-9+deb9u1
diff --git a/debian/changelog b/debian/changelog
index 6d3693fb..c2fd1f42 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+mariadb-10.1 (10.1.23-9+deb9u1) stretch; urgency=medium
+
+  [ Ondřej Surý ]
+  * Add Breaks: cqrlog (<< 1.9.0-5~) to ensure correct upgrade order
+(Closes: #864159)
+
+ -- Andreas Beckmann   Wed, 07 Jun 2017 21:11:23 +0200
+
 mariadb-10.1 (10.1.23-9) unstable; urgency=medium
 
   * Fix the invalid location of insserv configuration snippet
diff --git a/debian/control b/debian/control
index fb7d55ea..07612515 100644
--- a/debian/control
+++ b/debian/control
@@ -282,7 +282,8 @@ Conflicts: mariadb-tokudb-engine-10.0,
mysql-server-core-5.6,
mysql-server-core-5.7,
virtual-mysql-server
-Breaks: mariadb-galera-server,
+Breaks: cqrlog (<< 1.9.0-5~),
+mariadb-galera-server,
 mariadb-galera-server-10.0,
 mariadb-galera-server-5.5,
 mariadb-server-10.0,

Bug#688336: os-probe: subvol: patches to provide bootloaders with all the subvolume info.

[Mike Mestnik]

Hello,
  This is the result of several days working the issues and analysing
each aspect.  These patches include only what is necessary to support
subvol.  Care has been taken to future proof by preparing for other
filesystems, currently this only works with btrfs.  These patches have
been split, solving four main goals.

1. Scan btrfs filesystems only once, regardless of how many devices they span.
2. Report to the bootloader the existence of OS lurking on subvolumes.
3. Add option to linux-boot-prober for subvolume and output
appropriate rootoptions.
4. Tell bootloader about boot filesystems on a subvolume.

1 is simple and can be applied with no changes to the bootloader.

2 extends the output of os-prober to support subvolumes. Existing
bootloaders should ignore these records as the key was changed from
linux to linux-subvol and the device is listed as device@subvolid.

3 requires the bootloader to be patched to support the above
linux-subvol records.  It should be a noop for bootloaders that don't
pass a subvolid as the second parameter to linux-boot-prober.

4 I would hold off on, it requires the bootloader to support
subvolumes and I think it's ok to restrict the boot device to
non-subvolumes until such support is added.
From c37c722edba11566ce4bd73e80120b56a37dfa37 Mon Sep 17 00:00:00 2001
From: Michael Mestnik 
Date: Mon, 5 Jun 2017 11:08:42 -0500
Subject: [PATCH 4/4] Pass subvol data for /boot to bootloadter(s)

---
 common.sh   | 36 +
 linux-boot-prober   |  6 +++--
 linux-boot-probes/mounted/common/40grub2|  3 ++-
 linux-boot-probes/mounted/common/90fallback |  5 ++--
 linux-boot-probes/mounted/powerpc/40yaboot  |  3 ++-
 linux-boot-probes/mounted/sparc/50silo  |  3 ++-
 linux-boot-probes/mounted/x86/40grub|  3 ++-
 linux-boot-probes/mounted/x86/50lilo|  3 ++-
 8 files changed, 53 insertions(+), 9 deletions(-)

diff --git a/common.sh b/common.sh
index 1001c74..ff278c3 100644
--- a/common.sh
+++ b/common.sh
@@ -253,6 +253,42 @@ linux_mount_boot () {
 			shift
 			set -- "$(mapdevfs "$tmppart")" "$@"
 
+			if bootsubvolid="$(echo "$4" | grep -o 'subvolid=[0-9][0-9]*')"; then
+bootsubvolid="$(echo "$bootsubvolid" | cut -d= -f2-)"
+if mount -o "subvolid=$bootsubvolid" "$1" "$tmpmnt/boot"; then
+	if [ "$bootsubvolid" = "$(get_default_subvolid "$tmpmnt/boot")" ]; then
+		mountboot="$1 1"
+		return
+	else
+		mountboot="$1 1 $bootsubvolid"
+		return
+	fi
+else
+	debug "failed to subvolid-mount $1 onto $tmpmnt/boot"
+	mountboot="$1 0 $bootsubvolid"
+	return
+fi
+			else
+if bootsubvol="$(echo "$4" | grep -o 'subvol=[^,]*')"; then
+	bootsubvol="$(echo "$bootsubvol" | cut -d= -f2-)"
+	bootsubvol="${bootsubvol#/}"
+	if mount -o "subvol=${bootsubvol:=/}" "$1" "$tmpmnt/boot"; then
+		bootsubvolid="$(grep "^/dev/" /proc/mounts | parse_proc_mounts | grep " $tmpmnt/boot " | cut -d ' ' -f 4)"
+		if [ "$bootsubvolid" = "$(get_default_subvolid "$tmpmnt/boot")" ]; then
+			mountboot="$1 1"
+			return
+		else
+			mountboot="$1 1 ${bootsubvolid:-@$bootsubvol}"
+			return
+		fi
+	else
+		debug "failed to subvol-mount $1 onto $tmpmnt/boot"
+		mountboot="$1 0 @$bootsubvol"
+		return
+	fi
+fi
+			fi
+
 			if grep -q "^$1 " "$OS_PROBER_TMP/mounted-map"; then
 bindfrom="$(grep "^$1 " "$OS_PROBER_TMP/mounted-map" | head -n1 | cut -d " " -f 2)"
 bindfrom="$(unescape_mount "$bindfrom")"
diff --git a/linux-boot-prober b/linux-boot-prober
index c53f05d..ba1a0bf 100755
--- a/linux-boot-prober
+++ b/linux-boot-prober
@@ -36,19 +36,21 @@ else
 	mpoint="$(unescape_mount "$mpoint")"
 	if [ "$mpoint" != "/target/boot" ] && [ "$mpoint" != "/target" ] && [ "$mpoint" != "/" ]; then
 		type=$(echo "$mrecord" | head -n1 | cut -d " " -f 3)
-		if ! grep -q " $mpoint/boot " "$OS_PROBER_TMP/mounted-map"; then
+		if ! bootrecord="$(grep -q " $mpoint/boot " "$OS_PROBER_TMP/mounted-map")"; then
 			linux_mount_boot "$partition" "$mpoint"
 			set -- $mountboot
 			bootpart="$1"
 			bootmounted="$2"
+			bootsubvolid="$3"
 		else
 			bootpart="$partition"
 			bootmounted=0
+			bootsubvolid="$(echo "$bootrecord" | head -n1 | cut -d ' ' -f 4)"
 		fi
 		for test in /usr/lib/linux-boot-probes/mounted/*; do
 			if [ -f $test ] && [ -x $test ]; then
 debug "running $test on mounted $partition"
-if $test "$partition" "$bootpart" "$mpoint" "$type" "$subvolid"; then
+if $test "$partition" "$bootpart" "$mpoint" "$type" "$subvolid" "$bootsubvolid"; then
 	debug "$test succeeded"
 	break
 fi
diff --git a/linux-boot-probes/mounted/common/40grub2 b/linux-boot-probes/mounted/common/40grub2
index 9d0b48c..06b8744 100755
--- a/linux-boot-probes/mounted/common/40grub2
+++ b/linux-boot-probes/mounted/common/40grub2
@@ -7,6 +7,7 @@ bootpart="$2"
 mpoint="$3"
 type="$4"
 

Bug#749275: Version 2 of PGObject::Util::PseudoCSV released

[Robert J. Clay]

Happened to check the open issue regarding the tests not passing and found
that the author had updated the module to a version 2 and closed the issue
last month:
https://github.com/einhverfr/PGObject-Util-PseudoCSV/issues/1

However; the release of Debian 9 ("Stretch") is currently scheduled for
just a little over a week so will still wait until after that to start
working on completing this ITP.


-- 
Robert J. Clay
rjc...@gmail.com
j...@rocasa.us

Bug#861444: Info received (Bug#861444: Acknowledgement (linux-image-4.9.0-2-amd64: kernel hangs when AC power state changes between suspend and resume))

[Steve VanDevender]

Still happening in linux-image-4.9.0-3-amd64_4.9.30-1.

Bug#863673: [Pkg-freeradius-maintainers] Bug#863673: CVE-2017-9148: FreeRADIUS TLS resumption authentication bypass

[Salvatore Bonaccorso]

Hi Michael,

On Wed, Jun 07, 2017 at 08:30:31AM +0200, Michael Stapelberg wrote:
> Thanks for your reply. I don’t have a way to test the vulnerability either.
> I’d trust Pavel’s assessment and call this done.

I have updated the security-tracker accordingly. So all should be
settled now.

Thanks for your work,

Regards,
Salvatore

Bug#864379: unblock: pgloader/3.3.2+dfsg-1.1

[Jonathan Wiltshire]

Control: tag -1 confirmed

On Wed, Jun 07, 2017 at 08:33:27PM +0200, Christoph Berg wrote:
> This could be accomplished by a binnmu, but I guess that means
> cl-plus-ssl needs an unblock as well, and it was uploaded only after
> the deadline. I guess we'll just wait for the next point release with
> that, and downgrade #864363 to important.)

I wouldn't bet on that. Unblocked both, aged to 2, rebuild scheduled.
I'll leave this request open for now to remind me to check up them.

(blah, blah, does not set precedent, disclaim all responsibility,
stretch is going to be awesome, etc.)

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#863470: ftp.debian.org: security sync must not exclude .buildinfo

[Ansgar Burchardt]

Rene Engelhard writes:
> So if I get this right any package having .buildinfo will fail at this stage.
>
> Which will get problematic in stretch security updates since anything built
> inside stretch will not only have the source but also the binary .buildinfo's.
>
> I think  this must be (somehow) fixed before stretch releases to be able
> to do security updates (well, sync them into s-p-u and not get lost and 
> needing
> manual recovery).

My current plan is to make dak handle .buildinfo files like .changes in
policy queues.  That is, store them in dists/${suite} and copy them into
the Process-Policy::CopyDir directory when the upload is accepted.

Maybe only copy them into dists/${suite} when CopyDir is set so this
only happens on sec-master and not for p-u on ftp-master.

Ansgar

Bug#788185: Info received (potential fix for mksquashfs corruption?)

[Robert McQueen]

I can confirmed that, at least in our test case (a 19GB .img file alone
inside a .squashfs) this patch fixes the corruption.

Our patched package is here:
 http://ramcq.net/files/tmp/squashfs-tools_4.3-3endless1.dsc
 http://ramcq.net/files/tmp/squashfs-tools_4.3-3endless1.debian.tar.xz
 http://ramcq.net/files/tmp/squashfs-tools_4.3.orig.tar.gz

Cheers,
Rob

On 07/06/17 16:57, Debian Bug Tracking System wrote:
> Thank you for the additional information you have supplied regarding
> this Bug report.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Laszlo Boszormenyi (GCS) 
> 
> If you wish to submit further information on this problem, please
> send it to 788...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.



Robert McQueen  |  Endless 

Bug#864381: dependencies to initramfs

[Christian Ehrhardt]

Package: multipath-tools
Version: 0.6.4-5
Severity: wishlist

Hi,
many core packages depend on initramfs-tools when they should actually
depend on linux-initramfs-tool (virtual package provided by initramfs-tools
and dracut).

Debian seems to be using "Depends: initramfs-tools | linux-initramfs-tool"
for almost every relevant package.

This is actually a spin-off of Ubuntu bug 109029 - but the parts not Ubunut
only should be fixed in Debian to be coherent.

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

Bug#864373: unblock: ycmd/0+20161219+git486b809-2.1

[Jonathan Wiltshire]

Control: tag -1 moreinfo

On Wed, Jun 07, 2017 at 08:53:14PM +0300, Adrian Bunk wrote:
> +ycmd (0+20161219+git486b809-2.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Run fewer tests on mipsel and mips64el, some fail on Loongson buildds.
> +(Closes: #852962)

Perhaps I misunderstood, but I thought the intention was simply to
blacklist the loongson builders so that all tests can still be run?

What's the impact of not unblocking this, considering the other changes
behind it? I presume #861483 would prevent an update in stretch, but I
want to be sure I understand correctly.


Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#864380: unblock: falcon/1.8.6-1.1

[Adrian Bunk]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: block -1 by 864371

Please unblock package falcon.

These are two separate fixes coming from #863929:
- Afif (maintainer of falcon) explained that the package actually
  doesn't make sense on 32bit architectures.
- It was originally believed the above change would also fix the
  #863929 testsuite failure, but I got the same failure on amd64
  (and the build sometimes succeeded on i386 on the buildds).
  I submitted #864376 to track that the test failures get
  properly fixed later.

(Adam Borowski already noticed that any-amd64 includes x32,
 luckily this does not impact stretch release architectures
 and I've asked the maintainers in #864378 to correct my
 mistake after stretch is released.)

unblock falcon/1.8.6-1.1


 changelog |   10 ++
 control   |2 +-
 rules |2 +-
 3 files changed, 12 insertions(+), 2 deletions(-)

diff -Nru falcon-1.8.6/debian/changelog falcon-1.8.6/debian/changelog
--- falcon-1.8.6/debian/changelog   2017-01-24 08:57:51.0 +0200
+++ falcon-1.8.6/debian/changelog   2017-06-07 14:56:14.0 +0300
@@ -1,3 +1,13 @@
+falcon (1.8.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * For any actual use, this package requires more memory than would
+be addressable on a 32-bit system. Change the architecture list
+from any to a list of all current 64bit architectures.
+  * Don't run integration-tests, they sometimes fail. (Closes: #863929)
+
+ -- Adrian Bunk   Wed, 07 Jun 2017 14:56:14 +0300
+
 falcon (1.8.6-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru falcon-1.8.6/debian/control falcon-1.8.6/debian/control
--- falcon-1.8.6/debian/control 2016-12-13 10:29:36.0 +0200
+++ falcon-1.8.6/debian/control 2017-06-07 14:56:14.0 +0300
@@ -18,7 +18,7 @@
 Vcs-Browser: https://anonscm.debian.org/cgit/debian-med/falcon.git
 
 Package: falcon
-Architecture: any
+Architecture: alpha any-amd64 arm64 hppa mips64el ppc64 ppc64el s390x sparc64
 Depends:
${shlibs:Depends},
${misc:Depends},
diff -Nru falcon-1.8.6/debian/rules falcon-1.8.6/debian/rules
--- falcon-1.8.6/debian/rules   2016-12-02 10:25:50.0 +0200
+++ falcon-1.8.6/debian/rules   2017-06-07 14:56:14.0 +0300
@@ -21,7 +21,7 @@
$(FALCON_PREFIX)/pylib
$(MAKE) all
 
-override_dh_auto_test: unit-tests integration-tests ;
+override_dh_auto_test: unit-tests ;
 
 .PHONY: unit-tests
 unit-tests:

Bug#864379: unblock: pgloader/3.3.2+dfsg-1.1

[Christoph Berg]

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

Please unblock package pgloader. The new version fixes a missing
run-time dependency on libssl1.0.2.

(Unfortunately there is a second SSL-related bug in pgloader via
cl-plus-ssl - when loading from MS SQL-Server, it is trying to call
SSLv3_client_method which was only part of libssl1.0.0 in jessie, but
is not present anymore in libssl1.0.2. This is #864363, fixed some
hours ago. pgloader will have this bug until recompiled against
cl-plus-ssl 20160421-2.

This could be accomplished by a binnmu, but I guess that means
cl-plus-ssl needs an unblock as well, and it was uploaded only after
the deadline. I guess we'll just wait for the next point release with
that, and downgrade #864363 to important.)


diff -Nru pgloader-3.3.2+dfsg/debian/changelog 
pgloader-3.3.2+dfsg/debian/changelog
--- pgloader-3.3.2+dfsg/debian/changelog2016-12-03 17:36:56.0 
+0100
+++ pgloader-3.3.2+dfsg/debian/changelog2017-06-07 12:19:48.0 
+0200
@@ -1,3 +1,11 @@
+pgloader (3.3.2+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * pgloader: Add Depends: libssl1.0.2, dlopen()ed at runtime.
+(Closes: #864309)
+
+ -- Andreas Beckmann   Wed, 07 Jun 2017 12:19:48 +0200
+
 pgloader (3.3.2+dfsg-1) unstable; urgency=medium
 
   * Fixes github issue 453 (Closes: #843555)
diff -Nru pgloader-3.3.2+dfsg/debian/control pgloader-3.3.2+dfsg/debian/control
--- pgloader-3.3.2+dfsg/debian/control  2016-11-20 17:02:18.0 +0100
+++ pgloader-3.3.2+dfsg/debian/control  2017-06-07 12:06:20.0 +0200
@@ -11,7 +11,7 @@
 
 Package: pgloader
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, freetds-dev
+Depends: ${shlibs:Depends}, ${misc:Depends}, freetds-dev, libssl1.0.2
 Description: extract, transform and load data into PostgreSQL
  pgloader imports data from different kind of sources and COPY it into
  PostgreSQL.

unblock pgloader/3.3.2+dfsg-1.1


Thanks,
Christoph

Bug#864378: falcon accidentally still built on x32

[Adrian Bunk]

Source: falcon
Version: 1.8.6-1.1
Severity: normal

Adam Borowski noticed that the any-amd64 I used in the
architecture list is not correct since it includes x32.

Please change this from "any-amd64" to "amd64 kfreebsd-amd64"
in the next (post-stretch) upload

Bug#864371: why x32?

[Adrian Bunk]

On Wed, Jun 07, 2017 at 08:01:44PM +0200, Adam Borowski wrote:
> > falcon is now only built for 64bit architectures.
> 
> Except that the package that has just been uploaded has:
> Architecture: alpha any-amd64 arm64 hppa mips64el ppc64 ppc64el s390x sparc64
> which includes x32 ("any-amd64" unintuitively means also x32).

Thanks for catching that.

> The package has built correctly, and seems to have passed the testsuite.
> 
> I don't know why falcon needs 64-bit, but x32 despite having 32-bit pointers
> has the full set of 64-bit integer registers, apparently that's enough.

Afif (maintainer of falcon) explained in #863929:
  It actually does not even make sense to have this package available for
  a 32-bit architecture since, for any actual use (de novo genome
  assembly), it will require more memory than would be addressable on a
  32-bit system.

At that point it was believed that the testsuite failures were 
32bit-only, but when I prepared the NMU today I got the same
test failure on amd64.

The testsuite also sometimes passed on i386 on the buildds.

My conclusion before the upload was that there is no strict relationship 
between the testsuite failures and 32bit in either direction, and these
two changes in my NMU are therefore not strictly related.

The problematic testsuite is now disabled on all architectures,
and #864376 submitted to track that this gets fixed.

> Thus, please explain -- if you don't, the next upload will reintroduce the
> x32 build which may or may not be what you want.

Since x32 is not a stretch release architecture it does at least not
matter right now, I'll submit a (non-RC) bug so that it won't be
forgotten.

> Meow!

Thanks!
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#864377: docker.io: Failure to install (cannot start daemon)

[Robbie Harwood]

Package: docker.io
Version: 1.13.1~ds1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

During a system upgrade, I got the following:

Setting up docker.io (1.13.1~ds1-2) ...
[] Starting Docker: dockerinvoke-rc.d: initscript docker, action "start"
failed.
dpkg: error processing package docker.io (--configure):

Followed by, at the end:

Errors were encountered while processing:
 docker.io
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up docker.io (1.13.1~ds1-2) ...
[] Starting Docker: dockerinvoke-rc.d: initscript docker, action "start" 
failed.
dpkg: error processing package docker.io (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 docker.io

I grepped logs for error, but don't see anything related, and they're so
incredibly verbose as to be useless.

Thanks,
--Robbie

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

Kernel: Linux 4.9.0-3-rt-amd64 (SMP w/8 CPU cores; PREEMPT)
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: sysvinit (via /sbin/init)

Versions of packages docker.io depends on:
ii  adduser  3.115
ii  containerd   0.2.3+git20170126.85.aa8187d~ds1-1
ii  golang-libnetwork0.8.0-dev.2+git20170202.599.45b4086-1
ii  init-system-helpers  1.48
ii  iptables 1.6.0+snapshot20161117-6
ii  libapparmor1 2.11.0-3
ii  libc62.24-11
ii  libdevmapper1.02.1   2:1.02.137-2
ii  libsqlite3-0 3.16.2-4
ii  libsystemd0  232-25
ii  lsb-base 9.20161125
ii  runc 1.0.0~rc2+git20170201.133.9df8b30-1

Versions of packages docker.io recommends:
ii  ca-certificates  20161130+nmu1
ii  cgroupfs-mount   1.4
ii  git  1:2.13.1+next.20170605-1
ii  xz-utils 5.2.2-1.2+b1

Versions of packages docker.io suggests:
pn  aufs-tools   
ii  btrfs-progs  4.9.1-1
ii  debootstrap  1.0.90
pn  docker-doc   
pn  rinse
pn  zfs-fuse | zfsutils  

-- no debconf information

Bug#841028: cups-daemon: cupsd uses 100% CPU

[Till Kamppeter]

On 06/07/2017 03:05 PM, Samuel Wolf wrote:

Wed Jun  7 20:03:07 2017 Unable to create/modify CUPS queue (Success)!


Here a successful operation was considered an error and this leads to 
the repetition.


I have fixed this already in the 1.13.4 release of cups-filters.

   Till

Bug#863479: perl-base should add Breaks: debconf (<< 1.5.57~)

[Dominic Hargreaves]

Control: reassign -1 debconf

On Wed, May 31, 2017 at 12:39:57PM +0100, Dominic Hargreaves wrote:
> On Mon, May 29, 2017 at 10:16:08PM +0300, Niko Tyni wrote:
> > On Sat, May 27, 2017 at 03:42:14PM +0200, Julien Cristau wrote:
> > > On Sat, May 27, 2017 at 16:36:50 +0300, Adrian Bunk wrote:
> >  
> > > > Package: perl-base
> > > > Version: 5.24.1-2
> > 
> > > > Technically #786705 is just a harmless warning, but when
> > > > during a jessie -> stretch upgrade perl-base is upgraded
> > > > before debconf is upgraded the user might see a lot scary
> > > > warnings as if something was seriously broken.
> > > > 
> > > [...]
> > > > 
> > > > perl-base should add a Breaks: debconf (<< 1.5.57~).
> > > 
> > > Adding Breaks in a core package a couple of weeks before the release
> > > sounds like a very, very, very bad idea.
> > 
> > Indeed it seems too late in the cycle for this.
> > 
> > Other possible solutions that come to mind:
> > 
> > - silence the warnings during maintainer scripts, much like
> >
> > https://sources.debian.net/src/perl/5.24.1-2/debian/patches/debian/squelch-locale-warnings.diff/
> >   (but it's late for even this IMO)
> > 
> > - update debconf in a jessie point release to minimize the impact
> >   (this feels right to me, but won't help the immediate stretch upgraders)
> > 
> > Cc'ing Colin. What do you think about the latter option?
> 
> Agree, the third option looks correct to me, we don't have time for
> anything else.

I'm reassigning this bug to debconf now as this seems to be the obvious
way forward. Colin, let us know if you would like a hand with preparing an
update for jessie for this.

Cheers,
Dominic.

Bug#841028: cups-daemon: cupsd uses 100% CPU

[Samuel Wolf]

Ok going a bit deeper in, I enable the debug logging file in
cups_browsed.conf and see that CUPS repeatedly reload some printers.

As soon I stop CUPS on the Debian Jessie server, the Debian Stretch client
CUPS stop using 100% CPU.

I have one printer two times on the Jessie CUPS server, but with different
default settings (color/black) and it look like cups-browsed load this
printers repeatedly.

[...]
Wed Jun  7 20:03:04 2017 Print queue Vertrieb is for remote CUPS queue(s)
and we get notifications from CUPS, using implicit class device URI
implicitclass:Vertrieb
Wed Jun  7 20:03:04 2017 Loaded PPD file /tmp/00a82593d31eb for printer
Vertrieb from server server1:631!
Wed Jun  7 20:03:04 2017 Editing PPD file /tmp/00a82593d31eb for printer
Vertrieb, setting the option defaults of the previous cups-browsed session
and inhibiting client-side filtering of the job, saving the resulting PPD
in /tmp/00a82593d9516.
Wed Jun  7 20:03:04 2017 Non-raw queue Vertrieb with PPD file:
/tmp/00a82593d9516
Wed Jun  7 20:03:07 2017 Unable to create/modify CUPS queue (Success)!
Wed Jun  7 20:03:07 2017 Creating/Updating CUPS queue for Vertrieb_Farbe
Wed Jun  7 20:03:07 2017 Queue has 0 duplicates
[...]

Bug#864376: falcon: properly fix test failure: Task Node(1-preads_ovl/m_00001) failed with exit-code=256

[Adrian Bunk]

Source: falcon
Version: 1.8.4-1
Severity: important

https://lists.debian.org/debian-med/2017/01/msg00085.html
and #863929 show the following test failure that sometimes
occurred and caused FTBFS:

...
2017-06-01 17:56:51,631[ERROR] Task Node(0-rawreads/job_0001) failed with 
exit-code=256
2017-06-01 17:56:51,631[ERROR] Task Node(0-rawreads/job_) failed with 
exit-code=256
2017-06-01 17:56:51,632[INFO] recently_satisfied: set([])
2017-06-01 17:56:51,632[INFO] Num satisfied in this iteration: 0
2017-06-01 17:56:51,632[INFO] Num still unsatisfied: 3
2017-06-01 17:56:51,632[ERROR] Some tasks are recently_done but not satisfied: 
set([Node(0-rawreads/job_), Node(0-rawreads/job_0001)])
2017-06-01 17:56:51,632[ERROR] ready: set([])
submitted: set([])
Traceback (most recent call last):
  File "/<>/inst/bin/fc_run.py", line 4, in 
__import__('pkg_resources').run_script('falcon-kit==0.7', 'fc_run.py')
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 739, 
in run_script
self.require(requires)[0].run_script(script_name, ns)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1494, 
in run_script
exec(code, namespace, namespace)
  File 
"/<>/inst/pylib/falcon_kit-0.7-py2.7-linux-i686.egg/EGG-INFO/scripts/fc_run.py",
 line 5, in 
main(sys.argv)
  File 
"/<>/inst/pylib/falcon_kit-0.7-py2.7-linux-i686.egg/falcon_kit/mains/run1.py",
 line 461, in main
main1(argv[0], args.config, args.logger)
  File 
"/<>/inst/pylib/falcon_kit-0.7-py2.7-linux-i686.egg/falcon_kit/mains/run1.py",
 line 136, in main1
input_fofn_plf=input_fofn_plf,
  File 
"/<>/inst/pylib/falcon_kit-0.7-py2.7-linux-i686.egg/falcon_kit/mains/run1.py",
 line 234, in run
wf.refreshTargets(exitOnFailure=exitOnFailure)
  File 
"/<>/inst/pylib/pypeflow-1.0.0-py2.7.egg/pypeflow/simple_pwatcher_bridge.py",
 line 226, in refreshTargets
self._refreshTargets(updateFreq, exitOnFailure)
  File 
"/<>/inst/pylib/pypeflow-1.0.0-py2.7.egg/pypeflow/simple_pwatcher_bridge.py",
 line 297, in _refreshTargets
failures, len(unsatg)))
Exception: We had 2 failures. 3 tasks remain unsatisfied.
makefile:4: recipe for target 'run-synth0' failed
make[5]: *** [run-synth0] Error 1
make[5]: Leaving directory '/<>/FALCON-examples'


The workaround in 1.8.6-1.1 was to disable integration-tests,
but they should be re-enabled and the issue properly fixed.

Bug#864375: ITP: quaternion -- desktop IM client for the Matrix protocol

[Hubert Chathi]

Package: wnpp
Owner: Hubert Chathi 
Severity: wishlist

* Package name: quaternion
  Version : git snapshot
  Upstream Author : QMatrixClient team 
* URL or Web page : https://github.com/QMatrixClient/Quaternion
* License : GPL-3+
  Description : desktop IM client for the Matrix protocol

Quaternion is a Qt-based chat client for the Matrix protocol, an open,
federated communications protocol.

Bug#864371: why x32?

[Adam Borowski]

> falcon is now only built for 64bit architectures.

Except that the package that has just been uploaded has:
Architecture: alpha any-amd64 arm64 hppa mips64el ppc64 ppc64el s390x sparc64
which includes x32 ("any-amd64" unintuitively means also x32).

The package has built correctly, and seems to have passed the testsuite.

I don't know why falcon needs 64-bit, but x32 despite having 32-bit pointers
has the full set of 64-bit integer registers, apparently that's enough.

Thus, please explain -- if you don't, the next upload will reintroduce the
x32 build which may or may not be what you want.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ A tit a day keeps the vet away.
⣾⠁⢰⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ (Rejoice as my small-animal-murder-machine got unbroken after
⠈⠳⣄ nearly two years of no catch!)

Bug#864373: unblock: ycmd/0+20161219+git486b809-2.1

[Adrian Bunk]

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

Please unblock package ycmd

unblock ycmd/0+20161219+git486b809-2.1


 README.Debian |8 +---
 changelog |   16 
 patches/05-tern-support.patch |   14 --
 rules |4 +++-
 4 files changed, 32 insertions(+), 10 deletions(-)

diff -Nru ycmd-0+20161219+git486b809/debian/changelog 
ycmd-0+20161219+git486b809/debian/changelog
--- ycmd-0+20161219+git486b809/debian/changelog 2017-01-26 11:57:23.0 
+0200
+++ ycmd-0+20161219+git486b809/debian/changelog 2017-06-07 12:13:33.0 
+0300
@@ -1,3 +1,19 @@
+ycmd (0+20161219+git486b809-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Run fewer tests on mipsel and mips64el, some fail on Loongson buildds.
+(Closes: #852962)
+
+ -- Adrian Bunk   Wed, 07 Jun 2017 12:13:33 +0300
+
+ycmd (0+20161219+git486b809-2) unstable; urgency=low
+
+  * Fix clang version detection in override_dh_link. (Closes: #861483)
+  * Try to find tern executable in $PATH and then set PATH_TO_TERN_BINARY
+to ~/.npm-packages/bin/tern. (Closes: #859883)
+
+ -- Onur Aslan   Mon, 08 May 2017 11:23:19 +0300
+
 ycmd (0+20161219+git486b809-1) unstable; urgency=low
 
   * New upstream release. (Closes: #850144)
diff -Nru ycmd-0+20161219+git486b809/debian/patches/05-tern-support.patch 
ycmd-0+20161219+git486b809/debian/patches/05-tern-support.patch
--- ycmd-0+20161219+git486b809/debian/patches/05-tern-support.patch 
2017-01-03 19:57:25.0 +0200
+++ ycmd-0+20161219+git486b809/debian/patches/05-tern-support.patch 
2017-05-08 11:23:19.0 +0300
@@ -3,7 +3,7 @@
 
 --- a/ycmd/completers/javascript/tern_completer.py
 +++ b/ycmd/completers/javascript/tern_completer.py
-@@ -36,20 +36,12 @@
+@@ -36,20 +36,15 @@
  
  _logger = logging.getLogger( __name__ )
  
@@ -17,12 +17,14 @@
 -'tern_runtime',
 -'node_modules',
 -'tern',
--'bin',
++PATH_TO_TERN_BINARY = utils.PathToFirstExistingExecutable( [ 'tern' ] )
++if not PATH_TO_TERN_BINARY:
++  PATH_TO_TERN_BINARY = os.path.join(
++os.path.expanduser('~'),
++'.npm-packages',
+ 'bin',
 -'tern' ) )
-+PATH_TO_TERN_BINARY = os.path.join(
-+  os.path.expanduser('~'),
-+  'node_modules',
-+  'tern')
++'tern')
  
 -PATH_TO_NODE = utils.PathToFirstExistingExecutable( [ 'node' ] )
 +PATH_TO_NODE = utils.PathToFirstExistingExecutable( [ 'nodejs' ] )
diff -Nru ycmd-0+20161219+git486b809/debian/README.Debian 
ycmd-0+20161219+git486b809/debian/README.Debian
--- ycmd-0+20161219+git486b809/debian/README.Debian 2016-03-30 
12:41:11.0 +0300
+++ ycmd-0+20161219+git486b809/debian/README.Debian 2017-05-08 
11:23:19.0 +0300
@@ -67,10 +67,12 @@
 -
 
 ycmd patched in this package to provide easy JavaScript semantic completion.
-Install npm package and install tern package with npm:
+ycmd will try to find tern executable in $PATH and if it's not available
+it will check for locally installed version in: $HOME/.npm-packages/bin/tern
+You can install tern with npm:
 
-  $ npm install tern
+  $ npm install -g tern
 
-This command will install tern package into $HOME/node_modules/tern directory.
+This command will install tern package into $HOME/.npm-packages directory.
 ycmd will use this directory for tern based JavaScript semantic code
 completion.
diff -Nru ycmd-0+20161219+git486b809/debian/rules 
ycmd-0+20161219+git486b809/debian/rules
--- ycmd-0+20161219+git486b809/debian/rules 2017-01-26 11:57:23.0 
+0200
+++ ycmd-0+20161219+git486b809/debian/rules 2017-06-07 12:13:33.0 
+0300
@@ -43,9 +43,11 @@
# Test JediHTTP
HOME=$(CURDIR) nosetests -w third_party/JediHTTP -v --with-id -d 
--no-byte-compile --exclude=test_good_gotoassignment_follow_imports
HOME=$(CURDIR) nosetests3 -w third_party/JediHTTP -v --with-id -d 
--no-byte-compile --exclude=test_good_gotoassignment_follow_imports
+ifeq (,$(filter $(DEB_HOST_ARCH), mipsel mips64el))
# Some tests requires UTF-8 compatible locale
HOME=$(CURDIR) LC_ALL=C.UTF-8 ./run_tests.py --skip-build 
--no-byte-compile $(EXCLUDE_TEST_PARAMS)
 endif
+endif
 
 override_dh_auto_clean:
dh_auto_clean
@@ -74,7 +76,7 @@
chmod 755 $(DEB_INSTALL_DIR)/usr/lib/ycmd/ycmd/__main__.py
 
 override_dh_link:
-   $(eval YCMD_CLANG_VER=$(shell objdump -x ycm_core.so | grep -oP 
'libclang-\K(\d+\.\d+)'))
+   $(eval YCMD_CLANG_VER=$(shell objdump -x ycm_core.so | grep -oP 
'NEED.*libclang-\K(\d+\.\d+)'))
echo "misc:Clang-Ver=$(YCMD_CLANG_VER)" >> debian/ycmd.substvars
dh_link -pycmd usr/lib/clang/$(YCMD_CLANG_VER)/include 
usr/lib/ycmd/clang_includes/include
 

Bug#864374: ITP: nheko -- desktop IM client for the Matrix protocol

[Hubert Chathi]

Package: wnpp
Owner: Hubert Chathi 
Severity: wishlist

* Package name: nheko
  Version : git snapshot
  Upstream Author : Konstantinos Sideris and others
* URL or Web page : https://github.com/mujx/nheko
* License : GPL-3+
  Description : desktop IM client for the Matrix protocol

Nheko is a Qt-based chat client for the Matrix protocol, an open,
federated communications protocol.  The motivation behind the project is
to provide a native desktop app for Matrix that feels more like a
mainstream chat app and less like an IRC client.

Bug#864371: RM: falcon [alpha hppa i386 m68k sh4 x32] -- ANAIS; package is now only built for 64bit architectures

[Adrian Bunk]

Package: ftp.debian.org
Severity: normal

falcon is now only built for 64bit architectures.

Bug#864159: [debian-mysql] fixing #864159 in mariadb-10.1

[Jonathan Wiltshire]

Hi,

If this bug is to be fixed in stretch, it will require a t-p-u upload.
The pending minor release blocking it in sid is not really suitable at
this late stage.

If you wish to fix it through t-p-u, please prepare a proposed diff and
open an unblock bug in the normal way.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#864372: unblock: squeak-vm/1:4.10.2.2614-4.1

[Adrian Bunk]

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

Please unblock package squeak-vm

unblock squeak-vm/1:4.10.2.2614-4.1


 changelog |8 
 rules |3 +++
 2 files changed, 11 insertions(+)

diff -Nru squeak-vm-4.10.2.2614/debian/changelog 
squeak-vm-4.10.2.2614/debian/changelog
--- squeak-vm-4.10.2.2614/debian/changelog  2015-11-09 11:24:53.0 
+0200
+++ squeak-vm-4.10.2.2614/debian/changelog  2017-06-07 12:05:13.0 
+0300
@@ -1,3 +1,11 @@
+squeak-vm (1:4.10.2.2614-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with -O1 to work around bugs exposed by better
+optimization in recent gcc versions. (Closes: #862576)
+
+ -- Adrian Bunk   Wed, 07 Jun 2017 12:05:13 +0300
+
 squeak-vm (1:4.10.2.2614-4) unstable; urgency=medium
 
   * Fix use system shared config.guess and config.sub (not old local
diff -Nru squeak-vm-4.10.2.2614/debian/rules squeak-vm-4.10.2.2614/debian/rules
--- squeak-vm-4.10.2.2614/debian/rules  2015-11-09 11:22:44.0 +0200
+++ squeak-vm-4.10.2.2614/debian/rules  2017-06-07 12:04:51.0 +0300
@@ -6,6 +6,9 @@
 # This has to be exported to make some magic below work.
 export DH_OPTIONS
 
+#workaround for #862576
+export DEB_CFLAGS_MAINT_APPEND = -O1
+
 include /usr/share/cdbs/1/rules/upstream-tarball.mk
 include /usr/share/cdbs/1/class/cmake.mk
 include /usr/share/cdbs/1/rules/debhelper.mk

Bug#864369: [debhelper-devel] Bug#864369: debhelper: meson

[Peter Pentchev]

On Wed, Jun 07, 2017 at 01:12:42PM -0400, Jeremy Bicha wrote:
> Package: debhelper
> Version: 10.4
> 
> I am trying to use debhelper's new meson support to build a new
> version of gnome-tweak-tool but it's failing. It obviously works for
> some other packages though.
> 
> https://git.launchpad.net/~jbicha/gnome-tweak-tool
> 
> dh build --with gnome,python3 --buildsystem=meson
>dh_testdir -O--buildsystem=meson
>dh_update_autotools_config -O--buildsystem=meson
>dh_autoreconf -O--buildsystem=meson
>dh_auto_configure -O--buildsystem=meson
> meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr
> --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> --libexecdir=lib/x86_64-linux-gnu
> dh_auto_configure: meson .. --wrap-mode=nodownload --buildtype=plain
> --prefix=/usr --sysconfdir=/etc --localstatedir=/var
> --libdir=lib/x86_64-linux-gnu --libexecdir=lib/x86_64-linux-gnu failed
> to to execute: No such file or directory
> debian/rules:6: recipe for target 'build' failed

Erm, correct me if I'm wrong, but wouldn't debhelper be trying to
execute "meson", and would the problem not be fixed by specifying
"meson" as a build dependency?

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@freebsd.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#841028: cups-daemon: cupsd uses 100% CPU

[Samuel Wolf]

Same here on a fresh installed Debian Stretch.

Set only..
BrowsePoll server1
..in cups-browsed.conf and CUPS uses 100% CPU.

Bug#863116: libtgvoip: FTBFS on non-Linux: #error "Unsupported operating system"

[Коля Гурьев]

Hello!

How does sound subsystem work in Debian on FreeBSD? It does like on
Linux? If I just add a macros for FreeBSD and Hurd, will it work? I
cannot test this right now...

22.05.2017 04:23, Aaron M. Ucko пишет:

Source: libtgvoip
Version: 0.4.1~git20170517.2ed5a50-1
Severity: important
Tags: upstream
Justification: fails to build from source

Builds of libtgvoip for kfreebsd-* have been failing:

   /«PKGBUILDDIR»/audio/AudioInput.cpp:27:2: error: #error "Unsupported operating 
system"

Builds for hurd-i386 fail earlier, due to gyp bug #799356, but it
looks like they would otherwise hit the same error.  Ideally, the
build system would actually check for the availability of libasound
and libpulse.  For the time being, though, it should suffice to treat
kFreeBSD (__FreeBSD_kernel__ && __GLIBC__) and the Hurd (__gnu_hurd__)
the same as (non-Android) Linux.

Could you please take a look?

Thanks!

Bug#864370: netdata: Add CAP_NET_RAW to systemd service

[Shengjing Zhu]

Source: netdata
Severity: wishlist

Dear Maintainer,

Could you add fping to packages recommends or suggests, and add
CAP_NET_RAW to systemd CapabilityBoundingSet(or some words in comments).

It took some time for me to get the fping plugin working...due to the
capability permission.
So I think this change will help others who also want to use the fping
plugin.

Best regards,
Shengjing Zhu


signature.asc
Description: PGP signature

Bug#864369: debhelper: meson

[Jeremy Bicha]

Package: debhelper
Version: 10.4

I am trying to use debhelper's new meson support to build a new
version of gnome-tweak-tool but it's failing. It obviously works for
some other packages though.

https://git.launchpad.net/~jbicha/gnome-tweak-tool

dh build --with gnome,python3 --buildsystem=meson
   dh_testdir -O--buildsystem=meson
   dh_update_autotools_config -O--buildsystem=meson
   dh_autoreconf -O--buildsystem=meson
   dh_auto_configure -O--buildsystem=meson
meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr
--sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu
--libexecdir=lib/x86_64-linux-gnu
dh_auto_configure: meson .. --wrap-mode=nodownload --buildtype=plain
--prefix=/usr --sysconfdir=/etc --localstatedir=/var
--libdir=lib/x86_64-linux-gnu --libexecdir=lib/x86_64-linux-gnu failed
to to execute: No such file or directory
debian/rules:6: recipe for target 'build' failed


Other Info
---
Technically, I am using Ubuntu's debhelper 10.4ubuntu3 which is very
similar to Debian's version with a few git patches backported.

I tried adding a meson_options.txt in case debhelper wanted that but
that didn't seem to make a difference. I guess the problem is figuring
out what file debhelper/meson is trying to execute.

Thanks,
Jeremy Bicha

Bug#864368: Expand kernel serial port configuration

[Ben Hutchings]

Control: reassign -1 src:linux 4.9.30-1
Control: severity -1 important

On Wed, 2017-06-07 at 09:38 -0700, Dave Hansen wrote:
[...]
> Please raise:
> 
>   CONFIG_SERIAL_8250_RUNTIME_UARTS
> 
> to something larger, perhaps 16 or 8, such as:
> 
>   CONFIG_SERIAL_8250_RUNTIME_UARTS=16

That seems reasonable.

> The second issue is that the "mid" serial driver is not configured in
> this package.  Please add the "8250_MID" driver by default and have it
> built in (as opposed to being as a module).  Some systems which have
> serial ports driven by this driver have *only* these ports.  They have
> no other output devices.  Having it built in is the only way to diagnose
> and fix boot issues that occur before modules start being loaded.
> 
> The necessary option is:
> 
>   CONFIG_SERIAL_8250_MID=y

Sorry, I disabled this one for 4.4 because that was then the default. 
It seems reasonable to enable it for x86 kernels if they will actually
run on the relevant SoCs.

> While the 4.9 kernel is the most important one to see these options
> changed, it would also be handy to have these options added for other
> packages.  Should I submit separate bugs from those?

No, I'm reassigning it to the source package instead and we can mark it
found in the relevant versions.

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.



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