Bug#851941: since version 2:1.19.1-1 xserver-xorg-legacy ignores settings in Xwrapper.config

[Tiziano Zito]

Package: xserver-xorg-legacy
Version: 2:1.19.0-3
Severity: important

Starting from version 2:1.19.1-1 the settings in Xwrapper.config are ignored.

In a system with systemd, I start the Xserver from /etc/rc.local with:

su -l myusername -c 'exec startx -- vt4 >> /tmp/xsession-errors 2>&1'

i.e. X is started from a user which is not logged in a console. This 
simulates the "autologin" feature of some display managers. No display 
manager is installed on this machine.

Until version 2:1.19.0-3 this works like a charm if /etc/X11/Xwrapper.config 
contains:

needs_root_rights=yes
allowed_users=anybody

Starting from 2:1.19.1-1, X does not start anymore and fails with:

[63.770] (EE)
Fatal server error:
[63.773] (EE) xf86OpenConsole: Cannot open virtual console 
4 (Permission denied)
[63.774] (EE)
[63.776] (EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
[63.782] (EE) Please also check the log file at 
"/home/tiziano/.local/share/xorg/Xorg.0.log" for additional information.
[63.784] (EE)
[63.785] (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
[63.785] (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
[63.785] (EE) Server terminated with error (1). Closing log file.

If I login in the console, I can start X with "startx", but I can not 
start on a different console from that I am logged into, i.e. 
"startx -- vt4" fails with the same error.

I don't see anything in the package changelog that would explain the problem.

Reverting to 2:1.19.0-3 fixes the problem.

Thanks!
Tiziano

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

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

Versions of packages xserver-xorg-legacy depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  libaudit1  1:2.6.7-1
ii  libc6  2.24-9
pn  xserver-common 

xserver-xorg-legacy recommends no packages.

xserver-xorg-legacy suggests no packages.

-- debconf information:
  xserver-xorg-legacy/xwrapper/actual_allowed_users: anybody
  xserver-xorg-legacy/xwrapper/allowed_users: Anybody

Bug#851927: 851927

[Sébastien Delafond]

I see the same problem, even with -enable-rmeote-extensions (which seems
to be about *installing* remote extensions, not enabling
already-installed ones).

However, my local extensions are still present (see
~/.config/chromium/Default/Extensions/*), and downgading to the version
in stretch (55.0.2883.75-3) brings them back.

Cheers,

--Seb

Bug#851911: rsync init script does not load default file options - debian 8.7

[serwisy]

On 01/20/2017 08:13 AM, Paul Slootman wrote:

On Thu 19 Jan 2017, has...@kontener.eu.org wrote:

I've set the RSYNC_OPTS='--port=9500' in /etc/default/rsync but it does not
affect daemon options.
In Debian 7 all were OK.

/etc/default/rsync
[..]
# start rsync in daemon mode from init.d script?

Can you show the lines that you deleted in [...] ?

You are probably using systemd, and the current /etc/default/rsync as
distributed has the lines:

# defaults file for rsync daemon mode
#
# This file is only used for init.d based systems!
# If this system uses systemd, you can specify options etc. for rsync
# in daemon mode by copying /lib/systemd/system/rsync.service to
# /etc/systemd/system/rsync.service and modifying the copy; add required
# options to the ExecStart line.

That should be self-explanatory.


Paul


Hey,


I don't see these lines:

# cat rsync
# defaults file for rsync daemon mode

# start rsync in daemon mode from init.d script?
#  only allowed values are "true", "false", and "inetd"
#  Use "inetd" if you want to start the rsyncd from inetd,
#  all this does is prevent the init.d script from printing a message
#  about not starting rsyncd (you still need to modify inetd's config 
yourself).

RSYNC_ENABLE=false

# which file should be used as the configuration file for rsync.
# This file is used instead of the default /etc/rsyncd.conf
# Warning: This option has no effect if the daemon is accessed
#  using a remote shell. When using a different file for
#  rsync you might want to symlink /etc/rsyncd.conf to
#  that file.
# RSYNC_CONFIG_FILE=

# what extra options to give rsync --daemon?
#  that excludes the --daemon; that's always done in the init.d script
#  Possibilities are:
#   --address=123.45.67.89(bind to a specific IP address)
#   --port=8730(bind to specified port; default 873)
RSYNC_OPTS=''

# run rsyncd at a nice level?
#  the rsync daemon can impact performance due to much I/O and CPU usage,
#  so you may want to run it at a nicer priority than the default priority.
#  Allowed values are 0 - 19 inclusive; 10 is a reasonable value.
RSYNC_NICE=''

# run rsyncd with ionice?
#  "ionice" does for IO load what "nice" does for CPU load.
#  As rsync is often used for backups which aren't all that time-critical,
#  reducing the rsync IO priority will benefit the rest of the system.
#  See the manpage for ionice for allowed options.
#  -c3 is recommended, this will run rsync IO at "idle" priority. Uncomment
#  the next line to activate this.
# RSYNC_IONICE='-c3'

# Don't forget to create an appropriate config file,
# else the daemon will not start.

Bug#851864: regression: 2.6.1-5+deb8u1 breaks python-paramiko

[Pedro González - 'NITEMAN']

On Thu, 19 Jan 2017 14:09:45 +0100 Sebastian Ramacher 
 wrote:

>
> And how does it fail?

Hi Sebastian,

I was misled since duplicity was giving:
~~~
/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py:141: 
FutureWarning: CTR mode needs counter parameter, not IV

  self._cipher = factory.new(key, *args, **kwargs)
~~~

An then an unrelated ssh conection failure.

Sorry for the inconvenience, this is an annoyance rather than a bug. I 
got duplicity working again with python-crypto 2.6.1-5+deb8u1


My apologies.

Best regards

Bug#851551: Info received (Bug#851551: FutureWarning: CTR mode needs counter parameter, not IV)

[Antonis Christofides]

Apparently the error message appears even with --verbosity=error.

Bug#688295: debsums: incorrectly reports diverted file as missing

[Axel Beckert]

Hi Andreas,

ping. :-)

Axel Beckert wrote:
> Andreas Beckmann wrote:
> > the attached patch should work around at least some of these missing
> > diverted foreign files, I'm now testing this with my piuparts instance.
> 
> Thanks! Please tell us how the testing went. I'll probably do an
> upload this weekend then.

Any news? Shall I upload that debsums fix before the freeze (i.e. on
the upcoming weekend) or not?

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

Bug#851733: [Pkg-ime-devel] Bug#851733: opencc: SIGABRT on i386/armhf architecture

[Aron Xu]

Control: retitle -1 ocd data files are arch dependent
Control: severity -1 serious

Thanks for  the report, it appears that to ocd data files depends on
the size of size_t, so we need to make it arch:any instead of
arch:all.

Cheers,
Aron

Bug#851551: FutureWarning: CTR mode needs counter parameter, not IV

[Antonis Christofides]

I'm not an expert, but I don't see much similarity with #850025. The symptoms
are different and the versions are different.

Bug#851911: rsync init script does not load default file options - debian 8.7

[Paul Slootman]

On Thu 19 Jan 2017, has...@kontener.eu.org wrote:
> 
> I've set the RSYNC_OPTS='--port=9500' in /etc/default/rsync but it does not
> affect daemon options.
> In Debian 7 all were OK.
> 
> /etc/default/rsync
> [..]
> # start rsync in daemon mode from init.d script?

Can you show the lines that you deleted in [...] ?

You are probably using systemd, and the current /etc/default/rsync as
distributed has the lines:

# defaults file for rsync daemon mode
#
# This file is only used for init.d based systems!
# If this system uses systemd, you can specify options etc. for rsync
# in daemon mode by copying /lib/systemd/system/rsync.service to
# /etc/systemd/system/rsync.service and modifying the copy; add required
# options to the ExecStart line.

That should be self-explanatory.


Paul

Bug#845177: patch

[Manuel Schölling]

Adam's patch is pretty trivial. I developed the new feature for the
kernel and agree that his patch solves the issue.
I also don't see any problems with this patch for kernels that have
CONFIG_VGACON_SOFT_SCROLLBACK=n.
We tested this escape sequence for kernels with and without
CONFIG_VGACON_SOFT_SCROLLBACK and
CONFIG_VGACON_SOFT_SCROLLBACK_PERSISTENT - there were no issues.

duko: Would be great if you could apply it in time!

Thanks!

Manuel

Bug#851940: ITP: certspotter -- Certificate Transparency Log Monitor

[Faidon Liambotis]

Package: wnpp
Severity: wishlist
Owner: Faidon Liambotis 

* Package name: certspotter
  Version : 0.2
  Upstream Author : Opsmate, Inc.
* URL : https://github.com/SSLMate/certspotter
* License : MPL-2.0
  Programming Lang: Go
  Description : Certificate Transparency Log Monitor

 Cert Spotter is a Certificate Transparency log monitor from SSLMate that
 alerts you when a SSL/TLS certificate is issued for one of your domains.
 Cert Spotter is easier than other open source CT monitors, since it does
 not require a database. It's also more robust, since it uses a special
 certificate parser that ensures it won't miss certificates.
 .
 Cert Spotter is also available as a hosted service by SSLMate that
 requires zero setup and provides an easy web dashboard to centrally
 manage your certificates. Visit 
 to sign up.
 .
 You can use Cert Spotter to detect:
  * Certificates issued to attackers who have compromised a certificate
authority and want to impersonate your site.
  * Certificates issued to attackers who are using your infrastructure
to serve malware.
  * Certificates issued in violation of your corporate policy
or outside of your centralized certificate procurement process.
  * Certificates issued to your infrastructure providers without your
consent.

I intend to maintain this under pkg-go.  Andrew Ayer (Cc'ed) is the
upstream author and also a DM (Andrew, if you want to maintain this
instead, happy to take a step back).

Bug#851737: follow-up

[Ar Kononov]

top-notch work! thanks, Doug! 


Отправлено бесплатной почтой @KM.RU
http://mail.km.ru

Bug#851939: zoph: [INTL:fr] French debconf translation

[jean-pierregiraud]

Package: zoph
Severity: wishlist
Tags: patch l10n

Hi!

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

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

Kind Regards

jipege



fr.po.gz
Description: application/gzip

Bug#851938: unblock: aspell-he/1.0-0-7

[Tzafrir Cohen]

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

Please unblock package aspell-he

Package includes packaging upgrade only and almost no change of content.
The sole change in the content, besides the Debian changelog, is the
following:

* /usr/share/aspell/he.cwl.gz is different due to different gzip header.
  The original uncompressed files are the same in the old and the new.

Packaging change:

* Removal of a retired maintainer (Closes #759993)
* Compat level: 5 -> 9
* A DEP-5 copyright file

A debdiff of the change:

diff -Nru aspell-he-1.0-0/debian/changelog aspell-he-1.0-0/debian/changelog
--- aspell-he-1.0-0/debian/changelog2013-06-29 11:50:40.0 +0300
+++ aspell-he-1.0-0/debian/changelog2017-01-19 22:08:24.0 +0200
@@ -1,3 +1,13 @@
+aspell-he (1.0-0-7) unstable; urgency=medium
+
+  * Switch to dh and compat level 9.
+  * Add myself as uploader and remove Baruch (retired, Closes: #759993).
+  * Use a secure browser URL.
+  * A DEP-5 copyrights file
+  * Standards-Version 3.9.8
+
+ -- Tzafrir Cohen   Thu, 19 Jan 2017 22:08:24 +0200
+
 aspell-he (1.0-0-6) unstable; urgency=low
 
   [ Agustin Martin Domingo ]
diff -Nru aspell-he-1.0-0/debian/control aspell-he-1.0-0/debian/control
--- aspell-he-1.0-0/debian/control  2013-06-29 11:50:40.0 +0300
+++ aspell-he-1.0-0/debian/control  2017-01-19 21:44:52.0 +0200
@@ -2,12 +2,12 @@
 Section: text
 Priority: optional
 Maintainer: Debian Hebrew Packaging Team 

-Uploaders: Baruch Even , Lior Kaplan , 
Shachar Shemesh 
-Standards-Version: 3.9.4
+Uploaders: Tzafrir Cohen , Lior Kaplan 
, Shachar Shemesh 
+Standards-Version: 3.9.8
 Build-Depends: debhelper (>> 9)
 Build-Depends-Indep: aspell (>= 0.60.3-2), dictionaries-common-dev (>= 1.11.2)
 Vcs-Svn: svn://anonscm.debian.org/debian-hebrew/pkg/aspell-he
-Vcs-Browser: http://anonscm.debian.org/viewvc/debian-hebrew/pkg/aspell-he
+Vcs-Browser: https://anonscm.debian.org/viewvc/debian-hebrew/pkg/aspell-he
 Homepage: ftp://ftp.gnu.org/gnu/aspell/dict/he/
 
 Package: aspell-he
diff -Nru aspell-he-1.0-0/debian/copyright aspell-he-1.0-0/debian/copyright
--- aspell-he-1.0-0/debian/copyright2005-07-23 22:43:04.0 +0300
+++ aspell-he-1.0-0/debian/copyright2017-01-18 21:58:22.0 +0200
@@ -1,25 +1,23 @@
-This package was debianized by Baruch Even  on
-Mon, 18 Jul 2005 17:01:07 +0100.
-
-It was downloaded from ftp://ftp.gnu.org/gnu/aspell/dict/he/
-
-Copyright Holder: Nadav Har'El    
-  Dan Kenigsberg 
-
-License:
-
-The Aspell dictionary for Hebrew is based on Hspell and
-released under the GNU GPL version 2.
-
-Hspell is copyright (C) 2000-2003, Nadav Har'El and Dan Kenigsberg.
-
-It is released to the public licensed under the GNU General Public License
-(GPL). See the COPYING file included in this distribution for the whole text
-of the GNU General Public License version 2.
-
-Note that not only the programs in the distribution, but also the
-dictionary files and the generated word lists, are licensed under the GPL.
-There is no warranty of any kind for the contents of this distribution.
-
-In a Debian system you can find the GPL version 2 license under
-/usr/share/common-licenses/GPL-2
+Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: aspell-he
+Source: ftp://ftp.gnu.org/gnu/aspell/dict/he/
+
+Files: *
+Copyright:
+ 2000-2006, Nadav Har'El    
+ 2000-2006, Dan Kenigsberg 
+License: GPL-2.0
+
+Files: debian/*
+Copyright:
+ 2005-2007, Baruch Even 
+ 2005-2013, Lior Kaplan 
+License: GPL-2.0
+
+License: GPL-2.0
+ It is released to the public licensed under the GNU General Public License
+ (GPL). See the COPYING file included in this distribution for the whole text
+ of the GNU General Public License version 2.
+ .
+ On Debian systems you can find a version of the GNU General Public License
+ at /usr/share/common-licenses/GPL-2

unblock aspell-he/1.0-0-7

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

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

Bug#847941: RFS: libvecpf/1.1.0-1 ITP: libvecpf -- Vector Printf Library

[Tobias Frost]

Hi Frederic,

currently I'm short on time and as new packages are currently not the
priority (won't be part of Stretch anyway) please let me defer that to
past-freeze. Ping me again then and I'll take a look.

--
tobi

Am Mittwoch, den 11.01.2017, 09:58 +0100 schrieb Frederic Bonnard:
> Hi Tobias, Gianfranco.
> 
> Tobias, Thierry agreed and I change the owner, I hope it's better
> now.
> 
> Any of you would have time to review the package?
> I added Gianfranco as is my usual sponsor,  but I forgot to Cc him in
> my
> initial request.
> Thanks,
> 
> F.
> 
> On Mon, 19 Dec 2016 08:12:06 +0100, Tobias Frost 
> wrote:
> > Control: tags -1 wontfix
> > Control: block 806720 by -1
> > 
> > Hi Frederick,
> > 
> > the ITP is owned by Thierry Fauck, did you check with him if it is
> > ok
> > to take this ITP? (Should be done via the BTS and then the ITP's
> > meta
> > data should be corrected accordingly.
> > 
> > Please remove the wontfix when this has been resolved. 
> > 
> > --
> > tobi
> > 

Bug#851335: apt: unable to fetch changelog while available

[duck]

Quack,

On 2017-01-19 19:03, David Kalnischkies wrote:


In 1.1 we have rewritten the changelog acquire which includes a way for
repositories to define where to find changelogs for packages coming 
from that

repository.


Works nicely with 1.4~beta4 in unstable, thanks a lot.

Hope it gets in next stable.

\_o<

--
Marc Dequènes

Bug#851161: CVE-2016-2337 CVE-2016-2339

[Salvatore Bonaccorso]

On Fri, Jan 20, 2017 at 01:13:41AM +0100, Christian Hofstaedtler wrote:
> Control: reassign -1 ruby2.1
> Control: found -1 2.1.5-2+deb8u3
> 
> Hi,
> 
> * Moritz Muehlenhoff  [170120 00:05]:
> > this has been assigned CVE-2016-2339: 
> > http://www.talosintelligence.com/reports/TALOS-2016-0034/
> > 
> > Patch is here: 
> > https://github.com/ruby/ruby/commit/bcc2421b4938fc1d9f5f3fb6ef2320571b27af42
> 
> If I'm reading all those right, this is actually fixed since 2.3.0;
> this issue is likely open in 2.1.x. Reassigning.

Confirmed for 2.1.x, the POC in a jessie VM:

$ ruby CVE-2016-2339.rb 
Start
args array size : 1
increase size of array
New args array size is : 11
*** Error in `ruby': free(): invalid next size (fast): 0x00ea3590 ***
Aborted

It was confusing that TALOS report mentions that it was tested with 2.3.0 dev,
but this might then be right, the above commit is included ongoing from 2.3.0.

> For the TclTk issue, looks like this upstream patch:
> https://github.com/ruby/ruby/commit/a2b8925a94a672235ca6a16e584bf09026a957ab
> If this is the correct patch, 2.3.0 has this fixed, but 2.1.x needs
> a patch.

Thanks added the commit as well, and the fixed version to the tracker. I
*think*, although a problem in the source, this might not rally need an update
in jessie via a DSA, since the issue is incombination with cancel_eval which is
supported in Tcl/Tk8.6 or later, but we don't have that for jessie. So I would
tend to just mark that one as no-dsa at least. Or do I miss something?

Regards,
Salvatore

Bug#851937: RFS: farbfeld/2.20170109-1 ITP

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "farbfeld"

* Package name : farbfeld
  Version  : 2.20170109-1
  Upstream Author  : Laslo Hunhold 
* Url  : http://tools.suckless.org/farbfeld
* Licenses : ISC
  Programming Lang : C
  Section  : graphics

 Farbfeld is a lossless image-format designed to be parsed and piped
 easily. It is designed to be as simple as possible, leaving the task
 of compression to outside tools, beating PNG's filesize in many
 cases.
 .
 This package contains tools for converting between farbfeld format
 and other image formats (png, jpeg, ppm, pam, git)

It builds those binary packages:

  * farbfeld

Please note, that package is maintained with dgit(1) tool using
dgit-maint-merge(7) workflow. In particular, it means that quilt
patches are squashed in source package and are not intended for
review. For more information about how to sponsor this package,
see dgit-sponsorship(7).

  Git repository: 
https://anonscm.debian.org/cgit/users/kaction-guest/farbfeld.git
  Git branch: master
  Orig tar.gz: from tag 2.20170109

With /bin/sh following commands should suffice:

  $ git clone https://anonscm.debian.org/cgit/users/kaction-guest/farbfeld.git 
farbfeld
  $ cd farbfeld
  $ git archive -o ../farbfeld_2.20170109.orig.tar.xz 2.20170109
  $ dgit sbuild

Regards,
  Dmitry Bogatov

Bug#838573: gnome-shell-pomodoro: Changes system volume

[Joseph Herlant]

Thanks Ghislain,

I was planning on releasing the new version of gnome-shell-pomodoro
this coming weekend.

Joseph


On Thu, Jan 19, 2017 at 4:32 AM, Ghislain Vaillant  wrote:
> On Sun, 16 Oct 2016 17:17:11 -0700 Joseph Herlant  wrote:
>> Control: tag -1 + confirmed
>> Control: found -1 0.12.3-1
>> Control: forwarded -1 https://github.com/codito/gnome-pomodoro/issues/244
>>
>> Hi Joel,
>>
>> Thanks for your report (and sorry for the late answer, I missed your mail).
>> I was able to reproduce the bug, even when changing from one bell to
>> another in the preferences dialog.
>>
>> I forwarded the issue to upstream to see what can be done about it:
>> https://github.com/codito/gnome-pomodoro/issues/244
>>
>> I'll let you know when this is fixed.
>>
>> Regards,
>> Joseph
>
>
> Please consider either cherry-picking the following commit [1] or,
> perhaps better, packaging the new upstream release (0.13.0) [2].
>
> [1] 
> https://github.com/codito/gnome-pomodoro/commit/c72317396a96ad89470ab512795131a6bd379606
> [2] https://github.com/codito/gnome-pomodoro/releases/tag/0.13.0
>
> Thanks,
> Ghis

Bug#851936: RFS: openmeca/2.1.5-1 [ITP: #850590]

[dada]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my first package "openmeca"

* Package name: openmeca
* Version : 2.1.5-1
* Upstream Author : Damien André (myself)
* URL : https://gitlab.com/damien.andre/openmeca
* License : GPL v3
* Section : science

It builds those binary packages:
  openmeca   - Multibody mechanical simulator

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

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

Alternatively, one can download the package with dget using this 
command:
  dget -x 
https://mentors.debian.net/debian/pool/main/o/openmeca/openmeca_2.1.5-1.dsc


A git repository of the debianized version of openmeca is also 
available on Alioth:

  https://anonscm.debian.org/cgit/debian-science/packages/openmeca.git/

More information about openmeca can be obtained from :
  https://gitlab.com/damien.andre/openmeca
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850590


Best Regards,Damien andré
--
http://www.unilim.fr/pages_perso/damien.andre/

Bug#849756: [Pkg-sssd-devel] Bug#849756: sssd-ldap fails to connect to ldaps:// due to problem with non-blocking socket

[Timo Aaltonen]

On 18.01.2017 11:09, Tomas Forsman wrote:
> Hello.
> 
> Applying the patch from https://github.com/SSSD/sssd/pull/67 onto sssd
> 1.14.2-1 in stretch, will make both ldaps:// and ldap://+starttls work
> again. Applies cleanly, no regression found so far.
> 
> It would be quite unfortunate to have stretch without this fix, as I
> believe ldap(s) support is one of the primary uses for sssd.

I hope to get 1.15 in stretch.. they'd just need to release it first and
time is running short.


-- 
t

Bug#851935: xtightvncviewer: conffiles not removed

[Paul Wise]

Package: xtightvncviewer
Version: 1.3.9+t-1
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate

The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these obsolete conffiles on upgrade.

https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
http://manpages.debian.org/man/1/dh_installdeb

This bug report brought to you by adequate:

http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ pkg=xtightvncviewer ; adequate $pkg ; dpkg-query -W -f='${Conffiles}\n' $pkg 
| grep obsolete
xtightvncviewer: obsolete-conffile /etc/X11/app-defaults/Vncviewer
 /etc/X11/app-defaults/Vncviewer e375f8e723be53a9ca8bab78a0fa3e1f obsolete

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

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

Versions of packages xtightvncviewer depends on:
ii  tigervnc-viewer  1.7.0+dfsg-2

xtightvncviewer recommends no packages.

xtightvncviewer suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#851934: date: regression in 8.26-1: conversion from one timezone to another TZ no longer works

[Paul Wise]

Package: coreutils
Version: 8.26-1
Severity: serious
User: coreut...@packages.debian.org
Usertags: date

There is a regression from jessie, it is no longer possible to choose
the TZ of the output date when providing a TZ for the input date, which
means I can no longer use date to convert between timezones easily.
I have tested that downgrading to coreutils 8.25-2+b1 fixes the issue.

On jessie:

$ TZ="Europe/London" date -d 'TZ="Australia/Perth" 2016-08-15 07:00'
Monday 15 August  00:00:00 BST 2016

On stretch:

$ TZ="Europe/London" date -d 'TZ="Australia/Perth" 2016-08-15 07:00'
Mon 15 Aug 07:00:00 AWST 2016

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.2.52-3
ii  libattr1 1:2.4.47-2
ii  libc62.24-9
ii  libselinux1  2.6-3

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#851933: Work around

[Russell Coker]

If you can't fix the code before the Stretch freeze please call "restorecon 
/lib/udev/hwdb.bin" after running systemd-hwdb.
-- 
Sent from my Nexus 6P with K-9 Mail.

Bug#851933: udev: /lib/udev/hwdb.bin gets wrong SE Linux label

[Russell Coker]

Package: udev
Version: 232-12
Severity: normal

The command "systemd-hwdb --usr update" as run from
/var/lib/dpkg/info/udev.postinst creates the file /lib/udev/hwdb.bin and
assigns it the SE Linux context "system_u:object_r:default_t:s0" when it
should have "system_u:object_r:bin_t:s0" with the current policy.

For the context of this bug report please ignore the issue of whether bin_t is
the correct type of the file.  I can change the type to something else if
systemd-hwdb works currectly, but at the moment I have no control over the
situation as systemd-hwdb is doing something I don't understand.

If you can give me some pointers to debugging this program I'd be happy to
debug it for you.  Also I can give you administrative access to a test machine.

-- Package-specific info:

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

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

Versions of packages udev depends on:
ii  adduser  3.115
ii  dpkg 1.18.18
ii  libacl1  2.2.52-3
ii  libblkid12.29-1
ii  libc62.24-9
ii  libkmod2 23-2
ii  libselinux1  2.6-3
ii  libudev1 232-12
ii  lsb-base 9.20161125
ii  procps   2:3.3.12-3
ii  util-linux   2.29-1

udev recommends no packages.

udev suggests no packages.

Versions of packages udev is related to:
ii  systemd  232-12

-- debconf information:
  udev/sysfs_deprecated_incompatibility:
  udev/title/upgrade:
  udev/reboot_needed:
  udev/new_kernel_needed: false
P: /devices/LNXSYSTM:00
E: DEVPATH=/devices/LNXSYSTM:00
E: MODALIAS=acpi:LNXSYSTM:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:01
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:02
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:03
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:04
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:04
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:05
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:05
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:06
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:06
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:07
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:07
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXPWRBN:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00
E: DRIVER=button
E: MODALIAS=acpi:LNXPWRBN:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: KEY=10 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: NAME="Power Button"
E: PHYS="LNXPWRBN/button/input0"
E: PRODUCT=19/0/1/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=11355717

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event4
N: input/event4
E: BACKSPACE=guess
E: DEVNAME=/dev/input/event4
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event4
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: LIBINPUT_DEVICE_GROUP=19/0/1/0:LNXPWRBN/button
E: MAJOR=13
E: MINOR=68
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=11721675
E: XKBLAYOUT=us
E: XKBMODEL=pc104

P: /devices/LNXSYSTM:00/LNXSYBUS:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00
E: MODALIAS=acpi:LNXSYBUS:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00
E: MODALIAS=acpi:PNP0A08:PNP0A03:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00
E: DRIVER=video
E: MODALIAS=acpi:LNXVIDEO:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:00
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:01
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:01
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:02
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:02
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:03
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:03
E: SUBSYSTEM=acpi

P: 

Bug#851925: libmutter-cogl.so: cannot open shared object file: No such file or directory

[Jeremy Bicha]

Control: forwarded -1 https://bugzilla.gnome.org/777519

I opened a GNOME bug for this.

Thanks,
Jeremy Bicha

Bug#851737: follow-up in reply to Doug Torrance <dtorra...@piedmont.edu>

[Doug Torrance]

Control: tags -1 fixed-upstream

On 01/18/2017 10:23 PM, Ar Kononov wrote:

Thanks a lot for the quickest reply, for your time and efforts! Menu package 
indeed did the trick for now! will be glad to provide further info and testing 
with patching when needed!
Best wishes!


No problem!

FYI, I submitted a patch upstream which properly sets the path of WPrefs 
in the default menu [1].  It should be fixed with the next upstream release.


Doug

[1] http://repo.or.cz/wmaker-crm.git/commitdiff/d48a370

Bug#851932: mirror submission for admin.lserg.ru

[Sergey I. Lang]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: admin.lserg.ru
Aliases: mirror.lserg.ru
Type: leaf
Archive-architecture: amd64 i386 
Archive-ftp: /debian/
Archive-http: /debian/
Archive-rsync: debian/
IPv6: yes
Archive-upstream: ftp.ru.debian.org
Updates: four
Maintainer: Sergey I. Lang 
Country: RU Russian Federation

Bug#851826: pulseaudio: USB headset detected, but no sound

[Michael Haag]

Not sure what you mean by "output sink". My output devices (according to
pulseaudio) are: "Built-in Audio Analog Stereo" and "Logitech G430
Headphones". Both are enabled with volume at 100%, but I only have sound
through my external speakers.

Note also the problem is ONLY with USB. When I have the headset plugged
in using the analog jacks (no USB converter) everything works as
expected.

The REALLY odd thing is I DO have sound (both mic and headphone) when
using Windows 7 in a guest VM, whether or not I'm using the USB
converter. Unfortunately, the sound is slightly garbled/unclear, as if
interrupted or slightly delayed. This means I can no longer use my Thai
language software (Windows only) to practice pronunciation.

On Thu, Jan 19, 2017, at 19:39, Felipe Sateler wrote:
> Control: tags -1 moreinfo
> Control: severity -1 normal
> 
> On 19 January 2017 at 03:16, MH  wrote:
> > Package: pulseaudio
> > Version: 9.0-5
> > Severity: important
> >
> > Dear Maintainer,
> >
> > Pulseaudio correctly detects USB headset (headphones and microphone) but 
> > sound
> > is only output through external speakers.
> 
> Have you tried changing the output sink for your program with
> pavucontrol? What happens if you change the output?
> 
> -- 
> 
> Saludos,
> Felipe Sateler


-- 
"Democracy is ... a form of religion; it is the worship of jackals by
jackasses." -- H. L. Mencken

Bug#851931: RFP: apache2-mod-brotli -- Brotli compression module for Apache

[Francois Marier]

Package: wnpp
Severity: wishlist

* Package name: apache2-mod-brotli
  Version : 0.3.1
  Upstream Author : kj 
* URL : https://github.com/kjdev/apache-mod-brotli
* License : Apache 2
  Programming Lang: C
  Description : Brotli compression module for Apache

Brotli allows for much better compression of static content on webservers:

  https://www.voorhoede.nl/en/blog/static-site-implosion-with-brotli-and-gzip/

Bug#851930: desktop-base: Include size 3840x2160 (4k) wallpaper and lockscreen

[Dave Allen Barker Jr]

Package: desktop-base
Version: 9.0.0
Severity: wishlist

Dear Maintainer,

I'm sorry I don't know how to provide a patch, but here are the simple
things you can do to provide crisp backgrounds for 4k (3840x2160)
high resolution displays:

  1. For each of the themes
1.1. In thier "image" directories
  1.1.1 Copy a 16:9 aspect ratio ".svg" file to "3840x2160.svg"
  1.1.2 Edit the "3840x2160.svg" "svg" header "width" and "height"
  attributes to "3840" and "2160" respectively
1.2. In their "gnome-background.xml"s, add an entry for the
"3840x2160.svg"

Thank you!


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

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

Versions of packages desktop-base depends on:
ii  dpkg 1.18.18
ii  librsvg2-common  2.40.16-1

desktop-base recommends no packages.

Versions of packages desktop-base suggests:
pn  gnome | kde-standard | xfce4 | wmaker  

-- no debconf information

Bug#789804: libevocosm: please make the build reproducible

[Al Stone]

On 01/15/2017 11:14 PM, Chris Lamb wrote:
>> Would you consider applying this patch and uploading?
> 
> Friendly ping on this :)
> 
> 
> Best wishes,
> 

Thanks.  I have not forgotten, just busy.

-- 
Ciao,
al
--
Al Stone Debian Developer
E-mail: a...@ahs3.nethttp://www.debian.org
 a...@debian.org
--

Bug#851929: qpdfview-djvu-plugin: qpdfview+qpdfview-djvu-plugin fail to load some djvus without djvulibre-plugin installed

[Artem]

Package: qpdfview-djvu-plugin
Version: 0.4.14-1
Severity: important

Dear Maintainer,

Here are my answers to the following questions:
   * What led up to the situation?
qpdfview + qpdfview-djvu-plugin pulled by default failed to load couple of my 
djvus+ f.e. a sample djvu found on 
https://en.wikisource.org/wiki/File:Test_rs20846.djvu.
they did open some other djvu's though, like the one found on 
https://commons.wikimedia.org/wiki/File:Example_for_DjVu_manual_cz-book_color.djvu
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
installed qpdfview the standard way, with the default apt configurations (no 
ignoring of recommends or anything), tried to open djvu file
   * What was the outcome of this action?
some djvus opend from the terminal would show the error Could not match file 
type of 'Downloads/Test_rs20846.djvu
   * What outcome did you expect instead?
expectedd the djvu file to be opened without errors

installing djvulibre-plugin solved it like a charm. Djvulibre is stated as a 
dependency in the arch aur package 
(https://aur.archlinux.org/packages/qpdfview/) 
Debian stretch requires libdjvulibre21 for qpdfview-djvu-plugin, but apparently 
it didn't do the trick

Thanks for your time!

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

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

Versions of packages qpdfview-djvu-plugin depends on:
ii  libc6 2.24-8
ii  libdjvulibre213.5.27.1-7
ii  libgcc1   1:6.2.1-5
ii  libgl1-mesa-glx [libgl1]  13.0.2-3
ii  libqt5core5a  5.7.1+dfsg-2
ii  libqt5gui55.7.1+dfsg-2
ii  libqt5widgets55.7.1+dfsg-2
ii  libstdc++66.2.1-5
ii  qpdfview  0.4.14-1

qpdfview-djvu-plugin recommends no packages.

qpdfview-djvu-plugin suggests no packages.

-- no debconf information

cheers,

Bug#811377: Bug#851747: sysvinit-utils: unmaintained package should not be Essential

[Benda Xu]

Hi Ian,

Thank you for the follow up.

Ian Jackson  writes:

> I see that we have offers of help from various people in #811377.
>
> I have also added Benda Xu, based on
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811377#25
> I see that Benda doesn't seem to be a DD.  Needless to say I am happy
> to sponsor uploads and/or review and push git branches.

Yeah, that work for me.  I am a DM seeking to be a DD.

Fingerprint: C3A504840B678260DA12766AD25D611C8E192076
Uid: Benda Xu 

> With sysvinit being maintained in collab-maint, I think Benda won't be
> able to push to it directly. Benda, I suggest that if you want to
> contribute you make a git branch in a tree of your own on alioth, and
> use git-request-pull.

I have a guest account on alioth and I am on the list of collaborative
maintainers:

  https://alioth.debian.org/projects/collab-maint

No problem pushing to the sysvinit git repo.

> Benda, and Simon, are you subscribed to pkg-sysvinit-devel ?

Yes, I am in the list.

> We should have a conversation on the devel list about what changes we
> want to see in stretch (and what bugs we want and/or need to fix).

Ah-ha, will dig out the mailing list archive.

Yours,
Benda

Bug#851928: linux-image-4.9.0-1-amd64: Kernel 4.9 fails to boot on Thinkpad T440p

[JWM]

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

Dear Maintainer,

After upgrading my Thinkpad T440p to linux-image-amd64 from unstable (along
with linux-headers-amd64, linux-doc, linux-perf, linux-source and linux-tools),
I am unable to boot with the 4.9.2 kernel.

Right after GRUB times out, the screen goes blank and nothing happens.

According to this page

https://bugzilla.kernel.org/show_bug.cgi?id=191121

There's already a patch that can be applied to 4.9.2 in order to solve the
issue.

At work I have a Lenovo laptop (not Thinkpad), and the system boots properly
with the kernel from unstable, so it seems to be a Thinkpad-only issue.



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20ANCTO1WW
product_version: ThinkPad T440p
chassis_vendor: LENOVO
chassis_version: Not Available
bios_vendor: LENOVO
bios_version: GLET85WW (2.39 )
board_vendor: LENOVO
board_name: 20ANCTO1WW
board_version: Win8 STD DPK TPG

** Network interface configuration:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback





** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor DRAM Controller [8086:0c04] (rev 06)
Subsystem: Lenovo ThinkPad T440p [17aa:220e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: ie31200_edac

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:01.1 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor PCI Express x8 Controller [8086:0c05] (rev 06) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA 
controller])
Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:221d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller [8086:0c0c] (rev 06)
Subsystem: Lenovo ThinkPad T440p [17aa:220e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
Family USB xHCI [8086:8c31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Lenovo ThinkPad T440p [17aa:220e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
Subsystem: Lenovo ThinkPad T440p [17aa:220e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:16.3 Serial controller [0700]: Intel Corporation 8 Series/C220 Series 
Chipset Family KT Controller [8086:8c3d] (rev 04) (prog-if 02 [16550])
Subsystem: Lenovo 8 Series/C220 Series Chipset Family KT Controller 
[17aa:220e]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: serial

00:19.0 Ethernet controller [0200]: Intel Corporation 

Bug#851927: chromium: Update removed all (local) installed extensions

[Simon Ruderich]

Package: chromium
Version: 55.0.2883.75-5
Severity: important

Hello,

After updating to 55.0.2883.75-5 all my extensions are gone! This
includes custom locally installed extensions and extensions
installed from the Chrome webstore.

Even after reading the NEWS article, restoring my old chrome
config and using  --enable-remote-extensions the extensions were
still gone.

Even if the --enable-rmeote-extensions switch is repaired I think
this behavior to _remove_ remote extensions is highly unexpected
and will surprise many stretch users and should be reverted.

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


signature.asc
Description: PGP signature

Bug#851926: unblock: qreator/13.05.3-4

[Chow Loong Jin]

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

Please unblock package qreator

Fixes for 2 RC bugs: #725827 and #779265

unblock qreator/13.05.3-4

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

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

-- 
Kind regards,
Loong Jin
diff --git a/debian/changelog b/debian/changelog
index bcca874..ce79e7f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+qreator (13.05.3-4) unstable; urgency=medium
+
+  * [5879985] Use geoclue-2.0 instead of geoclue.
+geoclue is gone from sid.
+
+ -- Chow Loong Jin   Mon, 16 Jan 2017 07:32:10 +0800
+
+qreator (13.05.3-3) unstable; urgency=medium
+
+  * [20d6c68] Fix debian/watch
+  * [1289a78] Depend on geoclue-ubuntu-geoip | geoclue-hostip
+qreator won't start without at least one of these. (Closes: #725827)
+  * [5c40090] Depend on python-gi-cairo (Closes: #779265)
+  * [a0c6640] Fix exception from PIL deprecated method
+
+ -- Chow Loong Jin   Sun, 15 Jan 2017 10:14:21 +0800
+
 qreator (13.05.3-2) unstable; urgency=low
 
   * [aec84f6] Expand package description to differentiate from qrencode
diff --git a/debian/control b/debian/control
index 14c4bb3..d867043 100644
--- a/debian/control
+++ b/debian/control
@@ -13,13 +13,15 @@ Vcs-Browser: 
http://git.debian.org/?p=collab-maint/qreator.git;a=summary
 Package: qreator
 Architecture: all
 Depends: ${python:Depends}, ${misc:Depends},
- python-imaging,
+ python-imaging (>= 2.0.0),
  python-cairo,
  python-dbus,
  python-defer,
  python-gi,
+ python-gi-cairo,
  gir1.2-champlain-0.12,
  gir1.2-clutter-1.0,
+ gir1.2-geoclue-2.0,
  gir1.2-glib-2.0,
  gir1.2-gdkpixbuf-2.0,
  gir1.2-gtk-3.0,
@@ -30,7 +32,8 @@ Depends: ${python:Depends}, ${misc:Depends},
  python-qrencode,
  python-requests,
  python-vobject,
- python-xdg
+ python-xdg,
+ geoclue-2.0
 Description: graphical utility for creating QR codes
  Qreator enables you to easily create your own QR codes to encode different
  types of information in an efficient, compact and cool way.
diff --git a/debian/patches/Fix-usage-of-PIL-deprecated-method.patch 
b/debian/patches/Fix-usage-of-PIL-deprecated-method.patch
new file mode 100644
index 000..e75af18
--- /dev/null
+++ b/debian/patches/Fix-usage-of-PIL-deprecated-method.patch
@@ -0,0 +1,21 @@
+From: Chow Loong Jin 
+Date: Sun, 15 Jan 2017 09:43:31 +0800
+Subject: Fix usage of PIL deprecated method
+
+---
+ qreator/QRCode.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/qreator/QRCode.py b/qreator/QRCode.py
+index 84c508a..d3a0130 100644
+--- a/qreator/QRCode.py
 b/qreator/QRCode.py
+@@ -73,7 +73,7 @@ class QRCode(object):
+ # Notice the conversion to BGRA that Cairo expects
+ # See http://cairographics.org/pythoncairopil/ and
+ # http://mail.gnome.org/archives/gtkmm-list/2007-May/msg00111.html
+-bytearr = array.array('B', self.image.tostring("raw", "BGRA", 0, 1))
++bytearr = array.array('B', self.image.tobytes("raw", "BGRA", 0, 1))
+ height, width = self.image.size
+ #print self.image.size
+ 
diff --git a/debian/patches/Port-to-geoclue-2.0.patch 
b/debian/patches/Port-to-geoclue-2.0.patch
new file mode 100644
index 000..82823de
--- /dev/null
+++ b/debian/patches/Port-to-geoclue-2.0.patch
@@ -0,0 +1,70 @@
+From: Chow Loong Jin 
+Date: Sun, 15 Jan 2017 23:45:17 +0800
+Subject: Port to geoclue-2.0
+
+geoclue has been removed from Debian.
+---
+ qreator/qrcodes/QRCodeLocationGtk.py | 46 ++--
+ 1 file changed, 12 insertions(+), 34 deletions(-)
+
+diff --git a/qreator/qrcodes/QRCodeLocationGtk.py 
b/qreator/qrcodes/QRCodeLocationGtk.py
+index 9adb634..c6b144f 100644
+--- a/qreator/qrcodes/QRCodeLocationGtk.py
 b/qreator/qrcodes/QRCodeLocationGtk.py
+@@ -14,6 +14,7 @@
+ # with this program.  If not, see .
+ ### END LICENSE
+ 
++import gi
+ from gi.repository import Gtk, GtkChamplain, Clutter, Champlain
+ from qreator_lib.helpers import get_data_file
+ from gi.repository import GtkClutter
+@@ -83,37 +84,14 @@ class QRCodeLocationGtk(object):
+ 
+ 
+ def get_current_location():
+-'''Gets the current location from geolocation via IP (only method
+-   currently supported)'''
+-#import Geoclue
+-#POS_PROVIDER = 'Ubuntu GeoIP'
+-#location = Geoclue.DiscoverLocation()
+-

Bug#851925: libmutter-cogl.so: cannot open shared object file: No such file or directory

[Simon McVittie]

Package: gnome-shell
Version: 3.22.2-2
Severity: grave
Justification: renders package unusable

While logging in to a new GNOME-on-X11 user session from gdm, via
"Switch User":

Jan 20 00:37:48 perpetual org.gnome.Shell.desktop[25051]: /usr/bin/gnome-shell: 
error while loadi
ng shared libraries: libmutter-cogl.so: cannot open shared object file: No such 
file or directory
Jan 20 00:37:48 perpetual gnome-session[24959]: gnome-session-binary[24959]: 
WARNING: App 'org.gn
ome.Shell.desktop' exited with code 127
Jan 20 00:37:48 perpetual gnome-session-binary[24959]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 127

Some weirdness appears if I try ldd:

$ ldd /usr/bin/gnome-shell|grep mutter
libmutter-cogl-pango.so => 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-pango.so (0x7f4ad4328000)
libmutter.so.0 => /usr/lib/x86_64-linux-gnu/libmutter.so.0 
(0x7f4ad3986000)
libmutter-clutter-1.0.so => 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so (0x7f4ad2d16000)
libmutter-cogl.so => not found
libmutter-cogl.so => /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl.so 
(0x7f4acbfb2000)
libmutter-cogl-path.so => 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-path.so (0x7f4ac7966000)

(Note the double entry for libmutter-cogl.so, only one of which was found.)

objdump -Tx says /usr/bin/gnome-shell and all the private mutter-related
libraries correctly have a RUNPATH, except for libmutter-cogl.so itself
(which doesn't depend on any of the others). So does the public
/usr/lib/x86_64-linux-gnu/libmutter.so.0.

However, libgnome-shell-menu.so links to libmutter-clutter-1.0.so without
a RUNPATH, and libgnome-shell.so links to libmutter-clutter-1.0.so
and libmutter-cogl.so with RUNPATH=/usr/lib/gnome-shell.
I think libgnome-shell.so might be the culprit here - the upstream
build system passes -rpath when it builds executables, but not when
it builds private shared libraries. Perhaps it should?

This might be related to recently-fixed RC bug #844796 - I'm not sure
whether exporting LD_LIBRARY_PATH during build would actually be
necessary if the -rpath was done correctly.

S

Bug#851924: libgc: Please update symbols for sh3

[John Paul Adrian Glaubitz]

Source: libgc
Version: 1:7.4.2-8
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

Hi!

We're currently adding sh3 as a new architecture to rebootstrap which
allows to cross-bootstrap Debian for architectures. sh3 is an older
architecture which is currently being redesigned as an open source
CPU with the name J-Core.

While cross-bootstrapping, the build stopped because the symbols for
libgc need to be updated for sh3. This can be trivially achieved by
globally replacing "!sh4" with "!sh3 !sh4" in libgc1c2.symbols:

 $ sed -i '/^ /s/!sh4/!sh3 &/' debian/libgc1c2.symbols

But it's also possible just to apply the attached debdiff.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
diff -Nru c/libgc-7.4.2/debian/libgc1c2.symbols 
d/libgc-7.4.2/debian/libgc1c2.symbols
--- c/libgc-7.4.2/debian/libgc1c2.symbols   2016-05-17 16:29:59.0 
+0200
+++ d/libgc-7.4.2/debian/libgc1c2.symbols   2017-01-20 01:46:46.562587256 
+0100
@@ -9,8 +9,8 @@
  GC_FirstDLOpenedLinkMap@Base 1:7.2d
  (arch=kfreebsd-amd64 kfreebsd-i386)GC_FreeBSDGetDataStart@Base 1:7.2d
  (arch=sparc sparc64)GC_SysVGetDataStart@Base 1:7.2d
- (arch=!arm64 !nios2 !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !ppc64el 
!sh4)GC_acquire_mark_lock@Base 1:7.4.2
- (arch=!arm64 !nios2 !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !ppc64el 
!sh4)GC_active_count@Base 1:7.4.2
+ (arch=!arm64 !nios2 !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !ppc64el 
!sh3 !sh4)GC_acquire_mark_lock@Base 1:7.4.2
+ (arch=!arm64 !nios2 !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !ppc64el 
!sh3 !sh4)GC_active_count@Base 1:7.4.2
  GC_add_ext_descriptor@Base 1:7.2d
  GC_add_map_entry@Base 1:7.2d
  GC_add_roots@Base 1:7.2d
@@ -28,7 +28,7 @@
  GC_alloc_large_and_clear@Base 1:7.2d
  GC_alloc_reclaim_list@Base 1:7.2d
  (arch=arm64 nios2 hppa ppc64el sh4)GC_allocate_lock@Base 1:7.4.2
- (arch=!arm64 !nios2 !hppa !ppc64el !sh4)GC_allocate_ml@Base 1:7.4.2
+ (arch=!arm64 !nios2 !hppa !ppc64el !sh3 !sh4)GC_allocate_ml@Base 1:7.4.2
  GC_allochblk@Base 1:7.2d
  GC_allochblk_nth@Base 1:7.2d
  GC_allocobj@Base 1:7.2d
@@ -59,7 +59,7 @@
  GC_build_fl@Base 1:7.2d
  GC_build_fl_clear2@Base 1:7.2d
  GC_build_fl_clear4@Base 1:7.2d
- (arch=!arm64 !nios2 !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !ppc64el 
!sh4)GC_bytes_allocd_tmp@Base 1:7.4.2
+ (arch=!arm64 !nios2 !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !ppc64el 
!sh3 !sh4)GC_bytes_allocd_tmp@Base 1:7.4.2
  GC_bytes_found@Base 1:7.2d
  GC_call_with_alloc_lock@Base 1:7.2d
  GC_call_with_gc_active@Base 1:7.2d
@@ -94,10 +94,10 @@
  GC_continue_reclaim@Base 1:7.2d
  GC_copy_bl@Base 1:7.2d
  GC_copyright@Base 1:7.2d
- (arch=!arm64 !nios2 !hppa !ppc64el !sh4)GC_core_finalized_malloc@Base 1:7.4.2
- (arch=!arm64 !nios2 !hppa !ppc64el !sh4)GC_core_gcj_malloc@Base 1:7.4.2
- (arch=!arm64 !nios2 !hppa !ppc64el !sh4)GC_core_malloc@Base 1:7.4.2
- (arch=!arm64 !nios2 !hppa !ppc64el !sh4)GC_core_malloc_atomic@Base 1:7.4.2
+ (arch=!arm64 !nios2 !hppa !ppc64el !sh3 !sh4)GC_core_finalized_malloc@Base 
1:7.4.2
+ (arch=!arm64 !nios2 !hppa !ppc64el !sh3 !sh4)GC_core_gcj_malloc@Base 1:7.4.2
+ (arch=!arm64 !nios2 !hppa !ppc64el !sh3 !sh4)GC_core_malloc@Base 1:7.4.2
+ (arch=!arm64 !nios2 !hppa !ppc64el !sh3 !sh4)GC_core_malloc_atomic@Base 
1:7.4.2
  GC_current_warn_proc@Base 1:7.2d
  (arch=!arm64 !nios2 !kfreebsd-amd64 !kfreebsd-i386 !mips !mips64el !mipsel 
!s390 !s390x !sparc !sparc64)GC_data_start@Base 1:7.2d
  GC_debug_change_stubborn@Base 1:7.2d
@@ -139,7 +139,7 @@
  GC_delete_thread@Base 1:7.2d
  GC_descr_obj_size@Base 1:7.2d
  GC_describe_type_fns@Base 1:7.2d
- (arch=!arm64 !nios2 !hppa !ppc64el !sh4)GC_destroy_thread_local@Base 1:7.4.2
+ (arch=!arm64 !nios2 !hppa !ppc64el !sh3 !sh4)GC_destroy_thread_local@Base 
1:7.4.2
  GC_dirty_init@Base 1:7.2d
  GC_dirty_maintained@Base 1:7.2d
  GC_disable@Base 1:7.2d
@@ -149,8 +149,8 @@
  GC_dlopen@Base 1:7.2d
  GC_do_blocking@Base 1:7.2d
  GC_do_blocking_inner@Base 1:7.2d
- (arch=!arm64 !nios2 !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !ppc64el 
!sh4)GC_do_local_mark@Base 1:7.4.2
- (arch=!arm64 !nios2 !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !ppc64el 
!sh4)GC_do_parallel_mark@Base 1:7.4.2
+ (arch=!arm64 !nios2 !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !ppc64el 
!sh3 !sh4)GC_do_local_mark@Base 1:7.4.2
+ (arch=!arm64 !nios2 !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !ppc64el 
!sh3 !sh4)GC_do_parallel_mark@Base 1:7.4.2
  GC_dont_expand@Base 1:7.2d
  GC_dont_gc@Base 1:7.2d
  GC_dont_precollect@Base 1:7.2d
@@ -197,8 +197,8 @@
  (arch=!arm64 !nios2 !mips !mips64el !mipsel !s390 
!s390x)GC_find_limit_with_bound@Base 1:7.2d
  GC_findleak_delay_free@Base 1:7.2d
  GC_finish_collection@Base 1:7.2d
- (arch=!arm64 !nios2 !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !ppc64el 

Bug#851923: mpgrafic: MPI_Comm_dup error on s390x, ppc64, sparc64 builds of mpgrafic

[Boud Roukema]

Package: mpgrafic
Version: 0.3.7.6-2
Severity: serious
Justification: fails to build from source

In this debian automated build of mpgrafic-0.3.7.6-2 (debian
downstream version) on an s390x architecture, `make check' calls
`regression-test-0.3.7.sh', which gives this fatal error:

* lines 878-884 of the html source of
https://buildd.debian.org/status/fetch.php?pkg=mpgrafic=s390x=0.3.7.6-2=1484854191=0

   878  This looks like a debian openmpi system.
   879  [zandonai:4650] *** An error occurred in MPI_Comm_dup
   880  [zandonai:4650] *** reported by process [4180410369,0]
   881  [zandonai:4650] *** on communicator MPI_COMM_WORLD
   882  [zandonai:4650] *** MPI_ERR_COMM: invalid communicator
   883  [zandonai:4650] *** MPI_ERRORS_ARE_FATAL (processes in this 
communicator will now abort,
   884  [zandonai:4650] ***and potentially your MPI job)

Version 0.3.7.6-2 is presently set up so that the build is not blocked
by make check errors - I need the logs on different architectures in order
to understand portability problems. I will soon prepare an updated
version in which this will lead to a build failure. So strictly speaking,
the "Justification:" tag above is not correct for 0.3.7.6-2, but I expect
that it will be a build failure on s390x, ppc64 and sparc64
for the next version of mpgrafic, probably 0.3.7.7-1 , unless this
bug is sorted out before that.

Since mpgrafic does not call MPI_Comm_dup directly, 
I suspect that the error comes from openmpi or fftw2 - after discussing this

on #debian-mentors with James Clarke, I've put a block against
openmpi source bug #851918 = 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851918 .

Hope this is right in terms of bug dependencies - if not feel
free to make corrections.

Cheers
Boud

-- System Information:
Debian Release: sid
Architecture: s390x

Bug#851897: dgit: please have generated source packages contain standard patch series

[Ian Jackson]

Control: tags -1 patch

Hi again Sean.  Thanks for the quick reply.

> Instead, I'd like to add text to say something about the kinds of
> packages for which the workflow is unsuitable.  I'd already been
> thinking about submitting a patch to do that since the recent discussion
> on -devel, and I think it might be sufficient to close this bug.[1]

This is a good approach.

Let me quote yur preferred wording from your patch.  (I find it easier
to deal with this inline as prose than as an attachment.  And I'd like
Daniel's opinion, as someone who has to deal with "not their own"
packages, before concluding that we have the wording right.)

>   +This workflow is less suitable for some packages.  When the Debian
>   +delta is very complex, with large parts not expected to ever be merged
>   +upstream, it might be preferable to maintain the delta as a rebasing
>   +patch series.  If this applies to your package, consider
>   +dgit-maint-gbp(7), and see Debian bug #720177.

This is good text but it's a little weaker than I would prefer.
Lack of a coherent patch stack is a problem if the individual patches
are hard to extract from the history, which occurs when the patches
need adjustment or conflict resolution to conform to new upstreams, or
cannot be easily separated.

And I think the point about not merging upstream cuts both ways.
Things that _are_ expected to go upstream may need to be distinguished
from ones which don't.  The key question is whether the patches need
to be maintained as a downstream delta for any time.

How about:

   This workflow is less suitable for some packages.  When the Debian
   delta contains multiple pieces which interact, or which you aren't
   going to be able to upstream soon, it might be preferable to
   maintain the delta as a rebasing patch series.

?

Thanks,
Ian.

Bug#851922: [PATCH] please switch exfat-utils to use autoreconf to allow jessie bpo

[Nicholas D Steeves]

Package: exfat-utils
Version: 1.2.5-1

Hi Sven,

I ran into trouble with missing aclocal-1.15 when backporting this
release.  Switching to use autoreconf seems to do the trick.  Diff was
made against debian/1.2.5-1.  I've attached a patch for this switch,
and a patch for the backport, with the hope being that it will also be
easy to adapt to the [ Other Contributor ] d/changelog format.  Please
apply this change to master so that no-change bpos will continue to be
possible :-)

Cheers,
Nicholas
From 577128be8acce848d489a7771eeac5961288e402 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Thu, 19 Jan 2017 16:33:51 -0700
Subject: [PATCH 1/2] Switch to autoreconf to allow no-change backport.

Signed-off-by: Nicholas D Steeves 
---
 debian/control | 2 +-
 debian/rules   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index b5a627a..e1e0404 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: exfat-utils
 Section: otherosfs
 Priority: optional
 Maintainer: Sven Hoexter 
-Build-Depends: debhelper (>= 9), autotools-dev, pkg-config
+Build-Depends: debhelper (>= 9), pkg-config, dh-autoreconf
 Standards-Version: 3.9.8
 Homepage: https://github.com/relan/exfat
 Vcs-Git: git://git.sven.stormbind.net/git/sven/exfat-utils.git
diff --git a/debian/rules b/debian/rules
index ec620f7..dfe3dc1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -5,7 +5,7 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 %:
-	dh $@ --with autotools_dev
+	dh $@ --with autoreconf
 
 override_dh_auto_configure:
 	dh_auto_configure -- \
-- 
2.1.4

From a2e648dd934c89c845495f442d8b10b219640450 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Thu, 19 Jan 2017 16:34:22 -0700
Subject: [PATCH 2/2] Update changelog.

Signed-off-by: Nicholas D Steeves 
---
 debian/changelog | 8 
 1 file changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 168d46b..b2a92be 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+exfat-utils (1.2.5-1~bpo8+1) jessie-backports; urgency=medium
+
+  * Rebuild for jessie-backports.
+  * Switch to using autoreconf, because building with autotools_dev fails
+due to missing aclocal-1.15 when backporting to Jessie.
+
+ -- Nicholas D Steeves   Thu, 19 Jan 2017 15:42:54 -0700
+
 exfat-utils (1.2.5-1) unstable; urgency=medium
 
   * New upstream release.
-- 
2.1.4

Bug#851921: [PATCH] please switch exfat-fuse to use autoreconf to allow jessie bpo

[Nicholas D Steeves]

Package: exfat-fuse
Version: 1.2.5-1

Hi Sven,

I ran into trouble with missing aclocal-1.15 when backporting this
release.  Switching to use autoreconf seems to do the trick.  Diff was
made against debian/1.2.5-1.  I've attached a patch for this switch,
and a patch for the backport, with the hope being that it will also be
easy to adapt to the [ Other Contributor ] d/changelog format.  Please
apply this change to master so that no-change bpos will continue to be
possible :-)

Cheers,
Nicholas
From fbe6e0390c925557a64a8be8461930c853d8b930 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Thu, 19 Jan 2017 16:33:25 -0700
Subject: [PATCH 1/2] Switch to autoreconf to allow no-change backport.

Signed-off-by: Nicholas D Steeves 
---
 debian/control | 2 +-
 debian/rules   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 2d69494..3bf0a36 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: fuse-exfat
 Section: otherosfs
 Priority: optional
 Maintainer: Sven Hoexter 
-Build-Depends: debhelper (>= 9), libfuse-dev, autotools-dev, pkg-config
+Build-Depends: debhelper (>= 9), libfuse-dev, pkg-config, dh-autoreconf
 Standards-Version: 3.9.8
 Homepage: https://github.com/relan/exfat
 Vcs-Git: git://git.sven.stormbind.net/git/sven/fuse-exfat.git
diff --git a/debian/rules b/debian/rules
index ec620f7..dfe3dc1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -5,7 +5,7 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 %:
-	dh $@ --with autotools_dev
+	dh $@ --with autoreconf
 
 override_dh_auto_configure:
 	dh_auto_configure -- \
-- 
2.1.4

From b3c37a4853695635b80c8b95f834ea53771244af Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Thu, 19 Jan 2017 16:34:06 -0700
Subject: [PATCH 2/2] Update changelog.

Signed-off-by: Nicholas D Steeves 
---
 debian/changelog | 8 
 1 file changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 6ae2717..7914d1f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+fuse-exfat (1.2.5-1~bpo8+1) jessie-backports; urgency=medium
+
+  * Rebuild for jessie-backports.
+  * Switch to using autoreconf, because building with autotools_dev fails
+due to missing aclocal-1.15 when backporting to Jessie.
+
+ -- Nicholas D Steeves   Thu, 19 Jan 2017 15:43:01 -0700
+
 fuse-exfat (1.2.5-1) unstable; urgency=medium
 
   * New upstream release.
-- 
2.1.4

Bug#851305: onboard doesn't show any information in mate-session-properties

[Jeremy Bicha]

On 14 January 2017 at 02:49, shirish शिरीष  wrote:
> But it's untrue that it is not displayed in MATE 'Startup Application
> Preferences' as had shared  the screenshot yesterday.

This surprised me and I finally ran MATE today to see what was going
on. MATE's Startup Applications app works differently than the old
GNOME version still shipped in Ubuntu but not in other GNOME distros
like Debian. I filed
https://github.com/mate-desktop/mate-session-manager/issues/134

> Also, for sake for argument, why should it not be displayed ? It is a
> legitimate service (for blind people hence accessibility) as well as
> for people whose keyboard goes wonky (has happened once or twice in
> the past) and not able to change keyboards in a jiffy. So it's a type
> of self-insurance.

I think you misunderstand. Hiding it from Startup Applications just
means that users won't accidentally disable Onboard (or any of the
other important services that should also be hidden).

I was able to enable Onboard by clicking
System>Preferences>Personal>Preferred Applications. I switched to the
Accessibility tab and made sure that Onboard was set to "Run at
start". To disable it, just make sure that box is unchecked.

Anyway, your bug is still valid. Onboard should set the Description
field even though I'm unaware of anything that uses that field if
MATE's Startup Applications app is fixed to work like Ubuntu's does.

Jeremy

Bug#851161: CVE-2016-2339

[Christian Hofstaedtler]

Control: reassign -1 ruby2.1
Control: found -1 2.1.5-2+deb8u3

Hi,

* Moritz Muehlenhoff  [170120 00:05]:
> this has been assigned CVE-2016-2339: 
> http://www.talosintelligence.com/reports/TALOS-2016-0034/
> 
> Patch is here: 
> https://github.com/ruby/ruby/commit/bcc2421b4938fc1d9f5f3fb6ef2320571b27af42

If I'm reading all those right, this is actually fixed since 2.3.0;
this issue is likely open in 2.1.x. Reassigning.

For the TclTk issue, looks like this upstream patch:
https://github.com/ruby/ruby/commit/a2b8925a94a672235ca6a16e584bf09026a957ab
If this is the correct patch, 2.3.0 has this fixed, but 2.1.x needs
a patch.

Would be good if somebody could crosscheck this.

Thanks,
-- 
christian hofstaedtler 

Bug#851920: [PATCH] please switch fuse-exfat to use autoreconf to allow jessie bpo

[Nicholas D Steeves]

Package: fuse-exfat
Version: 1.2.5-1

Hi Sven,

I ran into trouble with missing aclocal-1.15 when backporting this
release.  Switching to use autoreconf seems to do the trick.  Diff was
made against debian/1.2.5-1.  I've attached a patch for this switch,
and a patch for the backport, with the hope being that it will also be
easy to adapt to the [ Other Contributor ] d/changelog format.  Please
apply this change to master so that no-change bpos will continue to be
possible :-)

Cheers,
Nicholas
From fbe6e0390c925557a64a8be8461930c853d8b930 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Thu, 19 Jan 2017 16:33:25 -0700
Subject: [PATCH 1/2] Switch to autoreconf to allow no-change backport.

Signed-off-by: Nicholas D Steeves 
---
 debian/control | 2 +-
 debian/rules   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 2d69494..3bf0a36 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: fuse-exfat
 Section: otherosfs
 Priority: optional
 Maintainer: Sven Hoexter 
-Build-Depends: debhelper (>= 9), libfuse-dev, autotools-dev, pkg-config
+Build-Depends: debhelper (>= 9), libfuse-dev, pkg-config, dh-autoreconf
 Standards-Version: 3.9.8
 Homepage: https://github.com/relan/exfat
 Vcs-Git: git://git.sven.stormbind.net/git/sven/fuse-exfat.git
diff --git a/debian/rules b/debian/rules
index ec620f7..dfe3dc1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -5,7 +5,7 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 %:
-	dh $@ --with autotools_dev
+	dh $@ --with autoreconf
 
 override_dh_auto_configure:
 	dh_auto_configure -- \
-- 
2.1.4

From b3c37a4853695635b80c8b95f834ea53771244af Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Thu, 19 Jan 2017 16:34:06 -0700
Subject: [PATCH 2/2] Update changelog.

Signed-off-by: Nicholas D Steeves 
---
 debian/changelog | 8 
 1 file changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 6ae2717..7914d1f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+fuse-exfat (1.2.5-1~bpo8+1) jessie-backports; urgency=medium
+
+  * Rebuild for jessie-backports.
+  * Switch to using autoreconf, because building with autotools_dev fails
+due to missing aclocal-1.15 when backporting to Jessie.
+
+ -- Nicholas D Steeves   Thu, 19 Jan 2017 15:43:01 -0700
+
 fuse-exfat (1.2.5-1) unstable; urgency=medium
 
   * New upstream release.
-- 
2.1.4

Bug#851919: flashproxy: FTBFS randomly (fp-facilitator-test.py fails)

[Santiago Vila]

Package: src:flashproxy
Version: 1.7-4
Severity: important

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with autoreconf,python2
   dh_testdir -i
   dh_update_autotools_config -i
   dh_autoreconf -i
configure.ac:3: installing './install-sh'
configure.ac:3: installing './missing'
Makefile.am:49: warning: '%'-style pattern rules are a GNU make extension
parallel-tests: installing './test-driver'
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
ln -sf setup-common.py setup.py
dh_auto_configure -S autoconf -D facilitator -- --enable-initscripts 
cgibindir=/usr/lib/cgi-bin
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-initscripts cgibindir=/usr/lib/cgi-bin

[... snipped ...]

  File "./fp-facilitator-test.py", line 276, in test_af_v6_v4
fac.put_reg(FACILITATOR_ADDR, self.IPV4_CLIENT_ADDR, CLIENT_TP)
  File "/<>/flashproxy/fac.py", line 151, in put_reg
command, params = transact(f, "PUT", *params)
  File "/<>/flashproxy/fac.py", line 138, in transact
line = f.readline()
  File "/usr/lib/python2.7/socket.py", line 451, in readline
data = self._sock.recv(self._rbufsize)
error: [Errno 104] Connection reset by peer

--
Ran 17 tests in 2.115s

FAILED (errors=1)
FAIL fp-facilitator-test.py (exit status: 1)


Testsuite summary for flashproxy-facilitator 1.7

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log

Makefile:821: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
make[4]: Leaving directory '/<>/facilitator'
Makefile:927: recipe for target 'check-TESTS' failed
make[3]: *** [check-TESTS] Error 2
make[3]: Leaving directory '/<>/facilitator'
Makefile:1119: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/<>/facilitator'
dh_auto_test: make -j1 check VERBOSE=1 PYTHONPATH=.. VERBOSE=1 returned exit 
code 2
debian/rules:42: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/flashproxy/

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine,
provided you try enough times (as the failure happens randomly).

Thanks.

Bug#851918: openmpi: MPI_Comm_dup error on s390x, ppc64, sparc64 builds of mpgrafic - maybe from openmpi

[Boud Roukema]

Source: openmpi
Version: openmpi-2.0.2~git.20161225-8
Severity: normal

Dear Maintainer,

In this debian automated build of mpgrafic-0.3.7.6-2 (debian
downstream version) on an s390x architecture, `make check' calls
`regression-test-0.3.7.sh', which calls mpgrafic with a standard
input file, expecting a standard output file, but instead 
gives this fatal error:


* lines 878-884 of the html source of
https://buildd.debian.org/status/fetch.php?pkg=mpgrafic=s390x=0.3.7.6-2=1484854191=0

   878  This looks like a debian openmpi system.
   879  [zandonai:4650] *** An error occurred in MPI_Comm_dup
   880  [zandonai:4650] *** reported by process [4180410369,0]
   881  [zandonai:4650] *** on communicator MPI_COMM_WORLD
   882  [zandonai:4650] *** MPI_ERR_COMM: invalid communicator
   883  [zandonai:4650] *** MPI_ERRORS_ARE_FATAL (processes in this 
communicator will now abort,
   884  [zandonai:4650] ***and potentially your MPI job)

The ppc64 and sparc64 give similar messages, though ppc64 gives a longer 
traceback:

[ookuninushi:9401] *** An error occurred in MPI_Comm_dup
[ookuninushi:9401] *** reported by process [1293680641,0]
[ookuninushi:9401] *** on communicator MPI_COMM_WORLD
[ookuninushi:9401] *** MPI_ERR_COMM: invalid communicator
[ookuninushi:9401] *** MPI_ERRORS_ARE_FATAL (processes in this communicator 
will now abort,
[ookuninushi:9401] ***and potentially your MPI job)
[ookuninushi:09397] *** Process received signal ***
[ookuninushi:09397] Signal: Segmentation fault (11)
[ookuninushi:09397] Signal code: Address not mapped (1)
[ookuninushi:09397] Failing at address: 0x30
[ookuninushi:09397] [ 0] 
linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0)[0x3fffb1250478]
[ookuninushi:09397] [ 1] 
/usr/lib/powerpc64-linux-gnu/libpmix.so.0(+0x29e54)[0x3fffad789e54]
[ookuninushi:09397] [ 2] 
/usr/lib/powerpc64-linux-gnu/libpmix.so.0(+0x29c8c)[0x3fffad789c8c]
[ookuninushi:09397] [ 3] 
/usr/lib/powerpc64-linux-gnu/libpmix.so.0(+0x2a16c)[0x3fffad78a16c]
[ookuninushi:09397] [ 4] 
/usr/lib/powerpc64-linux-gnu/libpmix.so.0(pmix_rte_finalize-0x3bfb4)[0x3fffad7f1cac]
[ookuninushi:09397] [ 5] 
/usr/lib/powerpc64-linux-gnu/libpmix.so.0(OPAL_MCA_PMIX3X_PMIx_server_finalize-0x70d00)[0x3fffad7bb298]
[ookuninushi:09397] [ 6] 
/usr/lib/powerpc64-linux-gnu/openmpi/lib/openmpi/mca_pmix_pmix3x.so(pmix3x_server_finalize-0x1bf9c)[0x3fffad853a1c]
[ookuninushi:09397] [ 7] 
/usr/lib/powerpc64-linux-gnu/libopen-rte.so.20(pmix_server_finalize-0x7fa00)[0x3fffb11ab2c0]
[ookuninushi:09397] [ 8] 
/usr/lib/powerpc64-linux-gnu/openmpi/lib/openmpi/mca_ess_hnp.so(+0x4064)[0x3fffb09d4064]
[ookuninushi:09397] [ 9] 
/usr/lib/powerpc64-linux-gnu/libopen-rte.so.20(orte_finalize-0xbf7d8)[0x3fffb11697f0]
[ookuninushi:09397] [10] mpirun[0x10001730]
[ookuninushi:09397] [11] mpirun[0x1f38]
[ookuninushi:09397] [12] 
/lib/powerpc64-linux-gnu/libc.so.6(+0x46388)[0x3fffb0c86388]
[ookuninushi:09397] [13] 
/lib/powerpc64-linux-gnu/libc.so.6(__libc_start_main-0x187a18)[0x3fffb0c865d8]
[ookuninushi:09397] *** End of error message ***
Segmentation fault


I suspect that this comes from openmpi or fftw2, since MPI_Comm_dup is not 
called
directly from mpgrafic.

https://anonscm.debian.org/git/debian-science/packages/fftw.git/tree/mpi/transpose_mpi.c

   102   /* create a new "clone" communicator so that transpose
   103  communications do not interfere with caller communications. */
   104   MPI_Comm_dup(transpose_comm, );

Openmpi has an autoconf parameter to enable dealing with endianness
bugs:

line 930 of openmpi-2.0.2~git.20161225/configure.ac is:
AC_C_BIGENDIAN

My hypothesis of where the bug might lie is that #ifdef WORDS_BIGENDIAN
is needed somewhere in ompi_comm_dup_with_info, or at least somewhere
in relation to lines 967-1025 of 
openmpi-2.0.2~git.20161225/ompi/communicator/comm.c


Thanks to James Clarke for help in the attempted bug trace above!

Cheers
Boud

-- System Information:
Debian Release: sid
Architecture: s390x

Bug#851917: Should go in contrib

[Josh Triplett]

Package: chromium-widevine
Severity: normal

chromium-widevine exists solely to download and use the proprietary
Widevine modules, so it should go in contrib.

Alternatively, you could include such support within the main chromium
package; as an incidental function of that package, it wouldn't require
the whole package to go to contrib, any more than Firefox's ability to
download and run proprietary bits does.

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

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

Bug#851916: linux-image-4.9.0-1-amd64: RT5677_SPI driver not built

[Kinsey Moore]

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

Dear Maintainer,

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

   * What led up to the situation?
   Installing and running the in-repo 4.9.0-1-amd64 kernel instead of
   the kernel hosted on raphael's linux-samus github repo
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 N/A, module is not built
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- Package-specific info:
** Version:
Linux version 4.9.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20161229 (Debian 6.3.0-2) ) #1 SMP Debian 4.9.2-2 (2017-01-12)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-amd64 
root=UUID=416b4020-5131-4c2e-8ac3-9ce34e1754d9 ro quiet

** Not tainted

** Kernel log:
[1.619722] [drm] Replacing VGA console driver
[1.619789] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[1.619790] [drm] Driver supports precise vblank timestamp query.
[1.619794] i915 :00:02.0: Invalid PCI ROM data signature: expecting 
0x52494350, got 0xe937aa55
[1.619799] [drm] failed to find VBIOS tables
[1.619974] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[1.634475] tsc: Refined TSC clocksource calibration: 2394.460 MHz
[1.634480] clocksource: tsc: mask: 0x max_cycles: 
0x2283c649547, max_idle_ns: 440795304016 ns
[1.641298] media: Linux media interface: v0.10
[1.652019] Linux video capture interface: v2.00
[1.665561] sd 0:0:0:0: Attached scsi generic sg0 type 0
[1.667242] Intel(R) Wireless WiFi driver for Linux
[1.667243] Copyright(c) 2003- 2015 Intel Corporation
[1.669995] uvcvideo: Found UVC 1.00 device NCM-G102 (2232:6001)
[1.675963] iwlwifi :01:00.0: firmware: direct-loading firmware 
iwlwifi-7260-17.ucode
[1.676254] iwlwifi :01:00.0: loaded firmware version 17.352738.0 
op_mode iwlmvm
[1.678594] uvcvideo 1-7:1.0: Entity type for entity Extension 4 was not 
initialized!
[1.678597] uvcvideo 1-7:1.0: Entity type for entity Extension 3 was not 
initialized!
[1.678599] uvcvideo 1-7:1.0: Entity type for entity Processing 2 was not 
initialized!
[1.678600] uvcvideo 1-7:1.0: Entity type for entity Camera 1 was not 
initialized!
[1.678783] input: NCM-G102 as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input4
[1.678809] usbcore: registered new interface driver uvcvideo
[1.678809] USB Video Class driver (1.1.1)
[1.689241] random: crng init done
[1.692285] atmel_mxt_ts i2c-ATML0001:01: firmware: failed to load 
maxtouch.cfg (-2)
[1.692292] atmel_mxt_ts i2c-ATML0001:01: Direct firmware load for 
maxtouch.cfg failed with error -2
[1.693194] atmel_mxt_ts i2c-ATML0001:01: Resetting device
[1.738826] atmel_mxt_ts i2c-ATML:01: Touchscreen size X960Y540
[1.738874] input: Atmel maXTouch Touchpad as 
/devices/pci:00/INT3432:00/i2c-0/i2c-ATML:01/input/input5
[1.738907] atmel_mxt_ts i2c-ATML:01: Family: 164 Variant: 17 Firmware 
V1.0.AA Objects: 32
[1.814200] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[1.814208] [drm] Initialized i915 1.6.0 20160919 for :00:02.0 on minor 0
[1.823427] atmel_mxt_ts i2c-ATML0001:01: Touchscreen size X2559Y1699
[1.823480] input: Atmel maXTouch Touchscreen as 
/devices/pci:00/INT3433:00/i2c-1/i2c-ATML0001:01/input/input6
[1.823526] atmel_mxt_ts i2c-ATML0001:01: Family: 164 Variant: 13 Firmware 
V1.0.AA Objects: 41
[1.922262] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling 
instead
[1.943518] input: PC Speaker as /devices/platform/pcspkr/input/input7
[2.012317] fbcon: inteldrmfb (fb0) is primary device
[2.081506] input: HDA Intel HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.0/sound/card1/input8
[2.093926] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms 
ovfl timer
[2.093927] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[2.093927] RAPL PMU: hw unit of domain package 2^-14 Joules
[2.093928] RAPL PMU: hw unit of domain dram 2^-14 Joules
[2.093928] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[2.094590] input: HDA Intel HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.0/sound/card1/input9
[2.094656] input: HDA Intel HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.0/sound/card1/input10
[2.353661] iTCO_vendor_support: vendor-support=0
[2.358705] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[2.358768] iTCO_wdt: Found a Wildcat Point_LP TCO device (Version=2, 
TCOBASE=0x1060)
[2.359286] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[2.364948] iwlwifi :01:00.0: Detected Intel(R) Dual Band Wireless AC 
7260, REV=0x144
[2.366720] iwlwifi :01:00.0: L1 Enabled - LTR 

Bug#851871: RM: remove gcc-5 from stretch

[Emilio Pozuelo Monfort]

On 19/01/17 15:07, Matthias Klose wrote:
> Package: release.debian.org
> Tags: stretch
> 
> Please remove gcc-5, gcc-5-cross and gcc-5-cross-ports from testing.  Now that
> the linux source is built using gcc-6, the list of packages also needing 
> removal
> are acoording to [1]:
> 
>  - nvida-cuda-toolkit
>  - starpu-contrib
>  - boost1.58
>  - linux-grsec (which should build using gcc-6 as well)

According to dak there are more problems, e.g.

- petsc (libpetsc3.7.4-dev depends on libgfortran-5-dev)

- firefox-esr, gprolog, flint, kfreebsd-10
  + Build-Depends on gcc-5 and others.

Please file bugs for those.

Cheers,
Emilio

Bug#835940: Bug#851871: RM: remove gcc-5 from stretch

[Emilio Pozuelo Monfort]

On 19/01/17 21:17, Adrian Bunk wrote:
> On Thu, Jan 19, 2017 at 03:07:03PM +0100, Matthias Klose wrote:
>> Package: release.debian.org
>> Tags: stretch
>>
>> Please remove gcc-5, gcc-5-cross and gcc-5-cross-ports from testing.  Now 
>> that
>> the linux source is built using gcc-6, the list of packages also needing 
>> removal
>> are acoording to [1]:
>>
>>  - nvida-cuda-toolkit
>>  - starpu-contrib
>> ...
> 
> Their fix might actually be blocked by outdated information in #835940.
> 
> Quoting the relevant part from #835940:
> 
> On Mon, Nov 28, 2016 at 11:23:27AM +0100, Matthias Klose wrote:
>> On 28.11.2016 02:08, lumin wrote:
>>> Hello guys,
>>>
>>> I successfully compiled caffe with CUDA_8.0.44-2 and
>>> clang-3.8 (the current default clang). Maybe we can
>>> replace GCC-5 with Clang-3.8 to solve this problem.
>>>
>>> That means Stretch still has chance to ship CUDA8,
>>> and users are expected to compile with Clang/LLVM
>>> instead of GCC-6, as long as the CUDA rDepends
>>> compile with clang.
>>>
>>> I only tested caffe-contrib.
>>
>> My guess is that clang-3.8 will be gone for the release as well ...
> 
> 
> What is the final decision regarding LLVM versions in stretch?

We are shipping with 3.7 (for ghc), 3.8 and 3.9.

Emilio

Bug#851518: cinnamon won't start

[William L. DeRieux IV]

tags 851518 = moreinfo unreproducible

--

On Thu, 19 Jan 2017 16:14:08 -0500 "William L. DeRieux IV" wrote:
> On Tue, 17 Jan 2017 22:43:42 +0100 Carsten Kosthorstwrote:
>
> > Hi,
> >
> > I updated today and cinnamon is working again.
> >
> > Thanks,
> >
> > Carsten
> >
> >
> >
>
> Your version of cinnamon was 3.2.7-1 in the initial report.
>
> The latest version in unstable/sid is 3.2.7-1.
>
> What version was cinnamon updated to the second time?
>
> You can do this by using: *apt-cache policy cinnamon*
>
> The latest version in stretch/sid is 3.2.7-1, so I'm thinking this issue
> was temporary ?
>
>

I just updated to 3.2.7-1 and I cannot reproduce this issue.

So this does seem to be a one-off issue.

Bug#850921: openjfx version for openjdk 9.0

[Emmanuel Bourg]

Le 19/01/2017 à 18:49, shirish शिरीष a écrit :

> Look forward to knowing your plans.

Hi Shirish,

As I said last week, I plan to upgrade the openjfx package after the
Stretch release, once the OpenJDK 9 transition starts. But if someone
else (you?) wants to work on this update sooner I'll be happy to sponsor
his work.

Emmanuel Bourg

Bug#849821: pdns-recursor: Crash with DNSSEC enabled

[Christian Hofstaedtler]

Hi Chris,

there's a new pdns-recursor 4.0.4-1 in sid, maybe you could give it
a try.

Best,
-- 
christian hofstaedtler 

Bug#845177: [PATCH v10 3/4] console: Add persistent scrollback buffers for all VGA consoles

[Adam Borowski]

On Thu, Jan 19, 2017 at 05:33:14PM +0100, Greg KH wrote:
> On Thu, Jan 19, 2017 at 05:12:15PM +0100, Manuel Schölling wrote:
> > On Thu, 2017-01-19 at 14:23 +0100, Greg KH wrote:
> > > On Fri, Jan 13, 2017 at 09:07:57PM +0100, Manuel Schölling wrote:
> > > > +     This feature might break your tool of choice to flush
> > > > the scrollback
> > > > +     buffer, e.g. clear(1) will work fine but Debian's
> > > > clear_console(1)
> > > > +     will be broken, which might cause security issues.
> > > > +     You can use the escape sequence \e[3J instead if this
> > > > feature is
> > > > +     activated.
> > > 
> > > This issue is the one that makes me the most worried.  Why doesn't
> > > clear_console() work anymore?  Why doesn't it use \e[3J ?
> > 
> > Well, clear_console() just switches from one console to another and
> > back again. It just assumes that the scrollback buffer is flushed when
> > switching.
> > My plan is to make a patch for clear_console() as soon as these patches
> > are in the kernel - it's chicken-and-egg problem.
> 
> I'd recommend that patch get to clear_console() first, having it use the
> new escape sequence, if it isn't supported, shouldn't cause any
> problems, right?

In that case, we need to hurry -- the last day for any non-serious fixes in
Debian is Jan 26, after that it'll be frozen for months, and any subsequent
changes won't get to stable users for around two years.

doko: would you consider, pretty please with a cherry on top, applying the
patch I've sent to this bug?  The privacy/security issue is pretty minor and
applies only to a tiny fraction of users, but I understand why Greg is
reluctant.

Manuel's scrollback changes won't go to 4.9, and won't be enabled by default
for the time being, but using a newer kernel on old userspace is something
really widespread, be it via bpo, containers on an updated host, etc.


Meow!
-- 
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
  ./configure --host=zx-spectrum --build=pdp11

Bug#833256: shadow and util-linux

[Andreas Henriksson]

Hello Serge E. Hallyn,

Thanks for your input.

On Tue, Jan 17, 2017 at 01:59:49PM -0600, Serge E. Hallyn wrote:
> Hi,
> 
> so it looks like things which are duplicated include:
> 
> chfn
> chsh
> (but not chpasswd?)
> newgroup
> su
> vipw

I've done a quick comparison of what the manpage says in
shadow vs util-linux for these tools (Actual implementation
might still differ.)

I'm attaching a text file with my findings for all the above listed
tools.

> 
> Do these all work the same way?  (looks like util-linux su has a lot more
> options and implements the options shadow's does, good, but it does not honor
> all the same login.defs variables?)  

No, util-linux su does not implement all login.defs variables
that shadow su supports. Not sure how relevant the missing ones are.
Input very welcome! Would it maybe be enough to list the unsupported
ones in NEWS.Debian to alert dist-upgraders of the change?

> Are the manpages sufficient in util-linux  (I think so)?

Yes, that is my impression. While the actual tools maybe should grow
some (or all?) of the options missing from the shadow equivalent the
manpages should then be extended at the same time ofcourse.

>  What about the internationalization?  (Seems to
> be there, at least)

Should work.

> 
> Would you consider implementing other things like usermod in
> util-linux?

I have no personal imminent plans. Please check with upstream.
It's likely they'll say yes and possibly even have volunteers that does
the work.
Would be great if shadow (upstream) maintainers could reach out directly
to util-linux upstream to discuss about a unified vision. ;)

> 
> Ok, I see your (Andreas') tiered proposal.  That sounds good to me,
> but then again there is the equivalence question.

More fine-grained equivalence studies likely needed.
Personally I don't think we have to make it a show-stopper for
everything to be equivalently supported. Some might have no users and
may just be a waste to implement, where just a NEWS.Debian entry can
suffice. (Others we might really want to implement, and some we
likely should implement but might not be show-stoppers.)
Input on the importance of each spotted difference welcome.

> 
> Once some of these are out of the debian package, I'll have to check to
> make sure no other distros need to switch (gentoo?).  But happy to drop
> anything that gets supplanted.
> 

Regards,
Andreas Henriksson
# chfn

shadow  util-linux

-o office   -o other
--office office --other other

-p office-phone -w work-phone
--office-phone office-phone --work-phone work-phone

-r room
--room room

-R chroot-dir
--root chroot-dir

(not listing the options only existing in util-linux)


(Regarding login.defs both seems to support CHFN_RESTRICT (only).)




# chsh

shadow  util-linux

-h (== --help)  -u (== --help)

-R chroot-dir
--root chroot-dir

(not listing the options only existing in util-linux)


The strict validation of only valid shells allowed for non-root seems
to be a COMPILE-TIME "opt-in" feature in util-linux version:
--enable-chsh-only-listed
(Default in util-linux is to just warn when setting shell not listed in 
/etc/shells.)


# chpasswd

this utility part of shadow is not available in util-linux!


# newgrp

The optional command-line '-' in shadow not supported in util-linux version.

The shadow man page is much longer and describes possible additional 
functionality in shadow version (this needs further investigation):

* password prompting
* gshadow

The shadow version has (compile-time optional) support for login.defs variable 
SYSLOG_SG_ENAB but that's not available in (any) util-linux tool.


# su

The util-linux version supports all command-line options listed in shadow su 
manpage.
Possible slight implementation details might differ for example in -p (needs 
investigation).

The util-linux version does not support the following shadow su login.defs 
variables:

CONSOLE_GROUPS
DEFAULT_HOME
SULOG_FILE
SU_NAME
SYSLOG_SU_ENAB


# vipw

The shadow version of vipw and vigr supports many command-line options, while 
the util-linux equivalents only supports:

-h --help
(-V --version)


(The shadow version uses both VISUAL and EDITOR while u-l only looks at EDITOR.)

Bug#771514: Is the state of affairs the same upstream ?

[shirish शिरीष]

Hi all,

While there were updates, there doesn't seem to be anything happening here.

I can see the warning still -

─[$] javafxpackager

javafxpackager has been renamed javapackager
The original file may be removed in a future release in lieu of javapackager.
Please update your scripts.

So it seems that there are still some bits missing.


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#851915: maint-guide: Confusion in chapter "5.7 docs" about default installed files

[Joonas Kylmälä]

Package: maint-guide
Version: 1.2.37
Severity: wishlist

Hi,

Chapter 5.7. "docs" has this paragraph:

"By default, it will include all existing files in the top-level
source directory that are called BUGS, README*, TODO etc."

It is hard to understand if by "it" is meant the dh_installdocs or
dh_make program (dh_make I guess, after reading some source code :P).

I'm hoping that someone who knows what is meant here could clarify the
document (e.g. something like in chapter 5.1. where it is explicitly
mentioned that the file came from dh_make).

Thanks,
Joonas

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

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

maint-guide depends on no packages.

maint-guide recommends no packages.

Versions of packages maint-guide suggests:
pn  debian-policy 
pn  developers-reference  
ii  devscripts2.17.0
ii  dh-make   2.201608
ii  doc-base  0.10.7
ii  dput  0.11.0
ii  fakeroot  1.21-3
ii  lintian   2.5.50
pn  pbuilder  
pn  quilt 

-- no debconf information

Bug#850921: openjfx version for openjdk 9.0

[shirish शिरीष]

in-line :-


On 20/01/2017, Emmanuel Bourg  wrote:
> Le 19/01/2017 à 18:49, shirish शिरीष a écrit :
>
>> Look forward to knowing your plans.
>
> Hi Shirish,

Hi Emmanuel,

> As I said last week, I plan to upgrade the openjfx package after the
> Stretch release, once the OpenJDK 9 transition starts. But if someone
> else (you?) wants to work on this update sooner I'll be happy to sponsor
> his work.

Oops, not a programmer here. I mis-understood. I mis-read that you
would be making a release to experimental soonish.

So I'll wait.

> Emmanuel Bourg
>
>

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#851914: augeas: Intent to NMO new upstream version (1.7.0-0.1)

[Hilko Bengen]

Source: augeas
Severity: normal

Dear maintainers,

sadly, the augeas package has not seen any activity from you in more
than four years: It has been maintained/updated entirely using NMUs by
myself (3) and Yann Soubeyrand (1) after 1.0.0-1.

I am preparing a non-maintainer upload for version 1.7.0-0.1 which I
will upload to DELAYED/2. I am aiming for inclusion of the package in
stretch, but you may, of course, reschedule or cancel my upload if you
see important reasons to do so.

Cheers,
-Hilko

Bug#847552: [pkg-gnupg-maint] Bug#847552: gnupg: decrypting after X pinentry is sometimes slow: around 10 seconds on a small file

[Jochen Sprickerhof]

* Vincent Lefevre  [2017-01-19 11:29]:
> After the upgrade to gnupg-agent 2.1.17-6 and killing the old
> gnupg-agent, the bug no longer seems to occur. I suppose that
> was the same bug as 851298 "10 second delay on first ssh use
> (sleeps in agent_libgcrypt_progress_cb)", which has been fixed
> and where you said:

For me as well, thanks!


signature.asc
Description: PGP signature

Bug#851692: Managing multiple profiles?

[Yves-Alexis Perez]

Hi, it seems that the new behavior makes it complicated to handle extensions
when using multiple profiles. --disable-extensions-except switch takes a path
to the extracted extension, which is per-profile for a remote extension, so
that's not really something you can put in /etc/chromium.d/foo

While I can understand the intention behind the change in behavior, with the
current number of packaged extension in Debian, I don't think it's sustainable
right now.

Regards,
-- 
Yves-Alexis

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

Bug#851913: apt-build: Perl code should be modernised and made less error-prone

[Axel Beckert]

Package: apt-build
Version: 0.12.46
Severity: wishlist

apt-build's Perl code contains several patterns which are considered bad
(and error-prone) style. For example:

* Two-parameter open() calls should be replaced with three-parameter
  open() calls.

* Most open() calls are not being checked for their return value (which
  might indicate failures).

* Instead of '$\ = "\n";', "say" should be used instead of "print" where
  this feature is wanted. (Had to add some "chomp()" calls to cope with
  the additional newlines upon "print".)

* Many system() calls could be replaced with pure-perl solutions, e.g.
  calling mkdir, rm, cat, ln, cp, etc. (Seems to be no speed issue so
  far, though.)

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages apt-build depends on:
ii  apt 1.4~beta4
ii  apt-utils   1.4~beta4
ii  cdebconf [debconf-2.0]  0.220
ii  debconf [debconf-2.0]   1.5.59
ii  devscripts  2.17.0
ii  dpkg1.18.18
ii  dpkg-dev1.18.18
ii  g++ 4:6.3.0-1
ii  gcc 4:6.3.0-1
ii  libappconfig-perl   1.66-2
ii  libapt-pkg-perl 0.1.30
ii  libc6   2.24-9
pn  perl:any

Versions of packages apt-build recommends:
ii  build-essential  12.2
ii  fakeroot 1.21-3.1

Versions of packages apt-build suggests:
ii  gfortran  4:6.3.0-1

-- debconf information:
* apt-build/add_to_sourceslist: true
  apt-build/repository_dir: /var/cache/apt-build/repository
  apt-build/arch_alpha: native
  apt-build/arch_sparc: native
  apt-build/options:
  apt-build/archtype: native
  apt-build/arch_arm: native
* apt-build/make_options: -j8
* apt-build/olevel: Medium
  apt-build/build_dir: /var/cache/apt-build/build
* apt-build/arch_amd64: native
  apt-build/arch_intel: native
  apt-build/arch_amd: native

Bug#850998: [Pkg-leofs-devel] Bug#850998: erlang-ranch: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl

[Nobuhiro Iwamatsu]

Hi!

Thanks for your work.
I just pushed my latest commits.

Best regards,
  Nobuhiro

2017-01-19 7:52 GMT+09:00 Bálint Réczey :
> Hi Nobuhiro,
>
> I have uploaded the fix but the packaging repo does not contain your
> latest upload.
> In case you have it offline please upload it or we can import the
> history from the .dsc
>
> Cheers,
> Balint
>
> 2017-01-11 20:07 GMT+01:00 Lucas Nussbaum :
>> Source: erlang-ranch
>> Version: 1.2.1-2
>> Severity: serious
>> Tags: stretch sid
>> User: debian...@lists.debian.org
>> Usertags: qa-ftbfs-20170111 qa-ftbfs
>> Justification: FTBFS on amd64
>>
>> Hi,
>>
>> During a rebuild of all packages in sid, your package failed to build on
>> amd64.
>>
>> Relevant part (hopefully):
>>> make[2]: Entering directory '/<>'
>>>  GENdistclean-asciidoc
>>> a2x -v -f pdf doc/src/guide/book.asciidoc && mv doc/src/guide/book.pdf 
>>> doc/guide.pdf
>>> a2x: ERROR: missing configuration file: 
>>> /etc/asciidoc/dblatex/asciidoc-dblatex.xsl
>>> a2x: args: ['--dblatex-opts', '-P latex.output.revhistory=0 -P 
>>> doc.publisher.show=0 -P index.numbered=0', '-d', 'book', '--attribute', 
>>> 'tabsize=4', '-v', '-f', 'pdf', 'doc/src/guide/book.asciidoc']
>>> a2x: resource files: []
>>> a2x: resource directories: ['/etc/asciidoc/images', 
>>> '/etc/asciidoc/stylesheets']
>>> a2x: executing: "/usr/bin/asciidoc" --backend docbook -a "a2x-format=pdf"  
>>> --doctype book --attribute "tabsize=4" --verbose  --out-file 
>>> "/<>/doc/src/guide/book.xml" 
>>> "/<>/doc/src/guide/book.asciidoc"
>>>
>>> asciidoc: reading: /etc/asciidoc/asciidoc.conf
>>> asciidoc: reading: /<>/doc/src/guide/book.asciidoc
>>> asciidoc: reading: /etc/asciidoc/docbook45.conf
>>> asciidoc: reading: /etc/asciidoc/filters/source/source-highlight-filter.conf
>>> asciidoc: reading: /etc/asciidoc/filters/graphviz/graphviz-filter.conf
>>> asciidoc: reading: /etc/asciidoc/filters/music/music-filter.conf
>>> asciidoc: reading: /etc/asciidoc/filters/latex/latex-filter.conf
>>> asciidoc: reading: /etc/asciidoc/filters/code/code-filter.conf
>>> asciidoc: reading: /etc/asciidoc/lang-en.conf
>>> asciidoc: writing: /<>/doc/src/guide/book.xml
>>> asciidoc: include: /<>/doc/src/guide/introduction.asciidoc
>>> asciidoc: book.asciidoc: line 6: reading: 
>>> /<>/doc/src/guide/introduction.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/listeners.asciidoc
>>> asciidoc: book.asciidoc: line 8: reading: 
>>> /<>/doc/src/guide/listeners.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/transports.asciidoc
>>> asciidoc: book.asciidoc: line 10: reading: 
>>> /<>/doc/src/guide/transports.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/protocols.asciidoc
>>> asciidoc: book.asciidoc: line 12: reading: 
>>> /<>/doc/src/guide/protocols.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/embedded.asciidoc
>>> asciidoc: book.asciidoc: line 14: reading: 
>>> /<>/doc/src/guide/embedded.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/parsers.asciidoc
>>> asciidoc: book.asciidoc: line 16: reading: 
>>> /<>/doc/src/guide/parsers.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/ssl_auth.asciidoc
>>> asciidoc: book.asciidoc: line 18: reading: 
>>> /<>/doc/src/guide/ssl_auth.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/internals.asciidoc
>>> asciidoc: book.asciidoc: line 20: reading: 
>>> /<>/doc/src/guide/internals.asciidoc
>>>
>>> a2x: executing: "xmllint" --nonet --noout --valid 
>>> "/<>/doc/src/guide/book.xml"
>>>
>>>
>>> erlang.mk:5062: recipe for target 'asciidoc-guide' failed
>>> make[2]: *** [asciidoc-guide] Error 1
>>
>> The full build log is available from:
>>http://aws-logs.debian.net/2017/01/11/erlang-ranch_1.2.1-2_unstable.log
>>
>> A list of current common problems and possible solutions is available at
>> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>>
>> About the archive rebuild: The rebuild was done on EC2 VM instances from
>> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
>> failed build was retried once to eliminate random failures.
>>
>> ___
>> Pkg-leofs-devel mailing list
>> pkg-leofs-de...@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-leofs-devel



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#851912: apt-build: Should probably use "apt-ftparchive release $dir" to generate Release files

[Axel Beckert]

Package: apt-build
Version: 0.12.46
Severity: wishlist

Currently the generation of apt-build's Release files is an ugly
hack. Using "apt-ftparchive release $dir" instead would probably require
some smaller design changes, but in the end it's likely more reliable
and future-proof.

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages apt-build depends on:
ii  apt 1.4~beta4
ii  apt-utils   1.4~beta4
ii  cdebconf [debconf-2.0]  0.220
ii  debconf [debconf-2.0]   1.5.59
ii  devscripts  2.17.0
ii  dpkg1.18.18
ii  dpkg-dev1.18.18
ii  g++ 4:6.3.0-1
ii  gcc 4:6.3.0-1
ii  libappconfig-perl   1.66-2
ii  libapt-pkg-perl 0.1.30
ii  libc6   2.24-9
pn  perl:any

Versions of packages apt-build recommends:
ii  build-essential  12.2
ii  fakeroot 1.21-3.1

Versions of packages apt-build suggests:
ii  gfortran  4:6.3.0-1

-- debconf information:
  apt-build/arch_amd: native
  apt-build/repository_dir: /var/cache/apt-build/repository
* apt-build/add_to_sourceslist: true
  apt-build/archtype: native
  apt-build/build_dir: /var/cache/apt-build/build
  apt-build/arch_alpha: native
  apt-build/arch_intel: native
* apt-build/olevel: Medium
* apt-build/make_options: -j8
* apt-build/arch_amd64: native
  apt-build/arch_sparc: native
  apt-build/arch_arm: native
  apt-build/options:

Bug#851911: rsync init script does not load default file options - debian 8.7

[hasiok]

Package: rsync
Version: 3.1.1-3

I've set the RSYNC_OPTS='--port=9500' in /etc/default/rsync but it does 
not affect daemon options.

In Debian 7 all were OK.

/etc/default/rsync
[..]
# start rsync in daemon mode from init.d script?
#  only allowed values are "true", "false", and "inetd"
#  Use "inetd" if you want to start the rsyncd from inetd,
#  all this does is prevent the init.d script from printing a message
#  about not starting rsyncd (you still need to modify inetd's config 
yourself).

RSYNC_ENABLE=true

# what extra options to give rsync --daemon?
#  that excludes the --daemon; that's always done in the init.d script
#  Possibilities are:
#   --address=123.45.67.89  (bind to a specific IP address)
#   --port=8730 (bind to specified port; default 873)
RSYNC_OPTS='--port=9500'
[..]

# ps aux | grep rsync
root  9401  0.0  0.1  13804  2492 ?Ss   22:29   0:00 
/usr/bin/rsync --daemon --no-detach


But the funny thing.
When I copy /etc/init.d/rsync to fe. /etc/init.d/whatever and I start it 
from new script, it is OK:

# cp /etc/init.d/rsync /etc/init.d/whatever
# systemctl daemon-reload
# /etc/init.d/whatever start
[ ok ] Starting whatever (via systemctl): whatever.service.
# ps aux | grep rsync
root  9467  0.0  0.1  13804  2472 ?S22:31   0:00 
/usr/bin/rsync --no-detach --daemon --config /etc/rsyncd.conf --port=9500



So, what is going on?
Thanks.

Debian 8.7, latest update, default installation.

Bug#851792: palo ships binary in the sources

[Helge Deller]

On 18.01.2017 20:40, Adrian Bunk wrote:
> Package: palo
...
> If palo should continue to be available on non-hppa machines,
> a (binary-all) package that uses gcc-hppa-linux-gnu for building
> might be an option.

I'll check if it's possile. May take some time.

Helge

Bug#851841: xonsh: jobs and backgrounding broken

[Gordon Ball]

Thanks for reporting.

I think I have to agree. I pushed the 0.5 series when it was released
thinking it would be a better base if patching was required in future,
but there do appear to be too many bugs which cannot be patched at the
moment.

I have upgraded the bug to severity:serious to prevent migration, so
stretch will get 0.4.7 and unstable will be updated when patches for 0.5
are available.

On 19/01/17 09:48, Frederic Peters wrote:
> Package: xonsh
> Version: 0.5.2+dfsg-1
> Severity: important
> 
> Hi,
> 
> This is about https://github.com/xonsh/xonsh/issues/2071
> 
> From a comment in there:
> 
>   I think there are two separate issues here (that I've noticed).  One is that
>   backgrounding doesn't seem to work (the big issue). The other is that while
>   the SIGSTOP is sent by Ctrl-Z, the prompt doesn't always return control to
>   the user.
> 
> This makes xonsh almost unusable, and this version shouldn't migrate to
> testing. (imo)
> 
> 
> Thanks,
> Frederic
> 
> -- System Information:
> Debian Release: 9.0
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages xonsh depends on:
> ii  python3-pkg-resources  32.3.1-1
> ii  python3-ply3.9-1
> ii  python3-venv   3.5.1-4
> pn  python3:any
> 
> Versions of packages xonsh recommends:
> ii  python3-prompt-toolkit  1.0.9-1
> ii  python3-pygments2.1.3+dfsg-1
> ii  python3-setproctitle1.1.10-1
> 
> Versions of packages xonsh suggests:
> ii  xonsh-doc  0.5.2+dfsg-1
> 
> -- no debconf information
> 

Bug#851518: cinnamon won't start

[William L. DeRieux IV]

tags 851518 - moreinfo-- 
On Tue, 17 Jan 2017 22:43:42 +0100 Carsten Kosthorstwrote:


> Hi,
>
> I updated today and cinnamon is working again.
>
> Thanks,
>
> Carsten
>
>
>

Your version of cinnamon was 3.2.7-1 in the initial report.

The latest version in unstable/sid is 3.2.7-1.

What version was cinnamon updated to the second time?

You can do this by using: *apt-cache policy cinnamon*

The latest version in stretch/sid is 3.2.7-1, so I'm thinking this issue 
was temporary ?

Bug#819811: ITP: leiningen -- simple build system for Clojure

[Tom Marble]

Tom Marble  writes:
> Based on the fabulous work of ehashman and the help of technomancy
> I've made some minor reformatting of the "state of packaging leiningen"
> below.

As everyone knows leiningen is a special case package due
to it's signicance to the Clojure ecosystem. As such
it doesn't make sense to track the packaging work by
constantly updating this bug.

Therefore I've created a new page on the Debian wiki for this purpose:
https://wiki.debian.org/Clojure/Leiningen

Indeed I've created a entire tree to support Clojure work:
https://wiki.debian.org/Clojure

Which has been shameless cribbed from
https://wiki.debian.org/Java

Let's continue to collaborate with the Java team and
meet online in #debian-java

Regards,

--Tom

Bug#674561: A patch to improve parsing yaboot.conf

[Colin Watson]

On Fri, May 25, 2012 at 05:14:49PM +0430, Hedayat Vatankhah wrote:
> os-prober assumes that there is no space around '=' sign for append
> directive in yaboot.conf, while there can be. Therefore, both append="some
> options" and append = "some options" are valid in yaboot.conf. This patch
> fixes this parsing bug.

I don't really understand why this only applies to the "append" option
(I suspect that in fact it doesn't), but whatever - this will do for
now.  I converted your patch to POSIX sed syntax and applied it.

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]

Bug#851893: The availability of update-grub does not imply that GRUB is used

[Aurélien COUDERC]

Hi Alexander.

Le 19 janvier 2017 17:47:18 GMT+01:00, Alexander Kurtz  a 
écrit :

>Hi!
>
>People who want to have the GRUB binaries installed (for example to
>create VM images with GRUB), but don't want to use GRUB as their
>bootloader will (in the case of classic PCs) have the grub-pc-bin [0]
>and grub2-common [1] packages installed, but not the grub-pc [2]
>package as this contains the scripts for the automatic installation.

[buggy script code…]

>Since update-grub is shipped by the grub2-common package (see [3]),
>this test is wrong. The fact that update-grub is available does not
>imply that the system uses GRUB to boot. Since update-grub will
>obviously fail to run if GRUB is not installed to /boot, this bug
>causes desktop-base's postinst to fail, making the package
>uninstallable on such systems.

Thank you for your detailed bug report and analysis.
This looks a lot like #843727 [0] to me, although not for the same use case.

Would you care to test 9.0.1, already in sid that should fix this problem ?
The following change was done :
208:update-grub || echo "Updating grub failed, report success anyway!"

I'll merge the 2 bugs after confirmation that it works for you.

If you know of a better and robust way to detect if grub is being used, advice 
is welcome.

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843727

Cheers,
--Aurélien

Bug#851901: [Aptitude-devel] Bug#851901: aptitude: "E: Internal Error, No file name for apt-build:amd64" after failed reinstallation of apt-build, then endless loop "Can't find a source to download ve

[Axel Beckert]

Control: severity -1 important

Hi again,

Axel Beckert wrote:
> Axel Beckert wrote:
> > Will now try to get out of that mess. Will post it here, once I
> > found a way out of this state.
> 
> "aptitude keep apt-build" on the commandline at least got me out of
> the endless loop in the TUI.

Downgrading the severity to important after discussion on IRC since:

* There is no data loss.
* There is an easy way to solve the problem (Ctrl-C + "aptitude keep").
* The problem is likely to appear only seldom(*).

(*) Nevertheless #841506 looks similar, but neither has much details
nor any endless loop. (And is also only of severity important,
too.)

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


signature.asc
Description: Digital signature

Bug#851910: qemu: CVE-2017-5526

[Salvatore Bonaccorso]

Source: qemu
Version: 1:2.8+dfsg-1
Severity: normal
Tags: patch upstream security

Hi,

the following vulnerability was published for qemu.

CVE-2017-5526[0]:
|audio: memory leakage in es1370 device; CVE for the memory consumption
|issue

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-5526
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5526
[1] 
http://git.qemu.org/?p=qemu.git;a=commit;h=069eb7b2b8fc47c7cb52e5a4af23ea98d939e3da
[2] https://marc.info/?l=oss-security=148475744329689=2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#851757: [Pkg-nagios-devel] Bug#851757: nagios-nrpe-plugin: Segmentation fault when specifying the host with an IP address

[Sebastiaan Couwenberg]

On 01/19/2017 09:58 PM, Stephane Bortzmeyer wrote:
> On Wed, Jan 18, 2017 at 10:52:46PM +0100,
>  Sebastiaan Couwenberg  wrote 
>  a message of 31 lines which said:
> 
>> Running check_nrpe on Debian unstable and checking a Debian jessie and
>> Debian unstable host works fine on my test system both with a bash & zsh
>> shell.
>>
>> How can I reproduce the issue?
> 
> Which architecture? Mine was ARM, as indicated in the bug report.

amd64 of course, since the porterboxes cannot be used to troubleshoot
this issue.

Please provide the means to reproduce this issue.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#851909: elog: most recent elog update included with Debian 8.7 no longer allows login (except for Admin)

[chad seys]

Package: elog
Version: 2.9.2+2014.05.11git44800a7-2+deb8u1
Severity: grave
Justification: renders package unusable

Hi,
  A day or so ago elog was updated with the Debian change from 8.6 to 8.7 .  

  Afterwards only users listed as "admin" in the elog.cfg file could log in. 
Everyone else
would receive the error message "Use has no access to this logbook".
  Upgrading to 3.1.2 in stretch allows login again.
  
  A guess is that the patch for CVE-2016-6342 was not quite correct. :)

Thanks for packaging!
C.

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

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

Versions of packages elog depends on:
ii  adduser  3.113+nmu3
ii  libc62.19-18+deb8u7
ii  libkrb5-31.12.1+dfsg-19+deb8u2
ii  libssl1.0.0  1.0.1t-1+deb8u5
ii  net-tools1.60-26+b1

Versions of packages elog recommends:
ii  imagemagick  8:6.8.9.9-5+deb8u6

Versions of packages elog suggests:
pn  fckeditor  

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

-- no debconf information

Bug#737106: Ping?

[gregor herrmann]

On Tue, 10 Jan 2017 21:33:54 +0100, Elena ``of Valhalla'' wrote:

> is it too late to remind you about this in time for this year's FOSDEM?
> (being this close to the freeze probably doesn't help, but last year I
> was reminded of this bug too late for a ping)

Thanks for the reminder, and sorry for forgetting about this feature
request /o\

It's indeed a bit late for both FOSDEM and the freeze, so I won't
make any promises but it might be possible that my co-author and me
find some time in the next days to look into the ConfClerk code.

What is not clear to me after thinking a bit about this new feature
is how it would work from a UI point of view: Should this be a third
icon/button next to alarm/clock and favourite/star, and should the
favourite-star turn into a tri-state button (grey/pink/red or
grey/half-red/full-red for no-favourite, soft-favourite,
hard-favourite)? Or something else? So far I couldn't come up with a
solution that's practical and intuitive for users ... Do you have any
ideas or suggestions?


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: The Eagles: Doolin Dalton


signature.asc
Description: Digital Signature

Bug#851757: [Pkg-nagios-devel] Bug#851757: nagios-nrpe-plugin: Segmentation fault when specifying the host with an IP address

[Stephane Bortzmeyer]

On Wed, Jan 18, 2017 at 10:52:46PM +0100,
 Sebastiaan Couwenberg  wrote 
 a message of 31 lines which said:

> Running check_nrpe on Debian unstable and checking a Debian jessie and
> Debian unstable host works fine on my test system both with a bash & zsh
> shell.
> 
> How can I reproduce the issue?

Which architecture? Mine was ARM, as indicated in the bug report.

Bug#851405: [moodle-packaging] Bug#851405: CVE-2016-9186 CVE-2016-9187 CVE-2016-9188

[Adinolfi, Daniel R]

Greetings,

You are following the correct process to make requests for CVE. The CVE Request 
form is the best method to request updates, new CVE IDs, or submit questions.

I apologize for the delay in publishing your updates. The Content Team is 
actively working through our backlog of CVE requests, and your request is among 
those within the backlog. I will ask the Content Team to make your updates as 
soon as possible.

Please let me know if you have any questions.

Thanks.

-Dan
_
Daniel Adinolfi, CISSP
Lead Cybersecurity Engineer, The MITRE Corporation
CVE Communications and CNA Coordinator
Email:   Phone: 781-271-5774



From: Salvatore Bonaccorso  on behalf of 
Salvatore Bonaccorso 
Date: Monday, January 16, 2017 at 06:14
To: Marina Glancy 
Cc: Dan Poltawski , "851...@bugs.debian.org" 
<851...@bugs.debian.org>, Moritz Muehlenhoff , "Adinolfi, 
Daniel R" 
Subject: Re: Bug#851405: [moodle-packaging] Bug#851405: CVE-2016-9186 
CVE-2016-9187 CVE-2016-9188

Hi!

On Mon, Jan 16, 2017 at 11:30:50AM +0800, Marina Glancy wrote:
Hello Salvatore,
apologies for not replying earlier, I was away on holidays.

Alright, apologies for prodding you a second time in that short
timeframe!

I was told by the CVE team that I have to use the online form to update
information about the issues. On 10 November 2016 I have sent a request to
update an existing CVE for the CVE-2016-9186. I have received an automated
reply "CVE Request 260788 for Update Published CVE". I don't see any
changes on the page
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9186 following my
request to update though. I was not aware of 9187 and 9188, I can request
update again but now I'm not even sure this form works.
I also use this form to notify about publishing CVE. For example, the last
issue I notified about was CVE-2016-8644 on the 21 November 2016 (
https://moodle.org/mod/forum/discuss.php?d=343277 ) but the page
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8644 still does not
display any information about the issue.
Please advise me what is the correct way to update information on CVEs
and/or notify about the publishing. Below is the email that I have received
from c...@mitre.org in the end of October in reply to my 
request to update
information about CVE 2016-7919.

Actually the above is right, the form is now the right way to ask for
CVEs (if the issue is not yet public, if the issue is public, one can
go as well via oss-security mailinglist), or to have CVE items
updated.

Maybe Daniel can share some insights if your request went lost.

Thanks for your work!

Regards,
Salvatore

Bug#851908: Obsolete only removed not purged

[積丹尼 Dan Jacobson]

Package: aptitude
Version: 0.8.4-1
Severity: minor

Alas, even though one uses
Aptitude::Purge-Unused true;
there still needs to be a Aptitude::Purge-Obsolete or something, to get
rid of this too.

# aptitude search ~o
i   android-tools-adb   - Android Debug Bridge CLI 
tool
# aptitude install adb
The following NEW packages will be installed:
  adb{b} (B: android-tools-adb)  android-libadb{a} (D: adb) (adb D: 
android-libadb)
  android-libbase{a} (D: adb, D: android-libadb) (adb D: android-libbase)
  android-libcutils{a} (D: adb, D: android-libadb) (adb D: android-libcutils)
  android-liblog{a} (D: android-libbase, D: android-libcutils) (adb D: 
android-libcutils D: android-liblog)
The following packages are RECOMMENDED but will NOT be installed:
  android-sdk-platform-tools-common (R: adb)
0 packages upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 230 kB of archives. After unpacking 620 kB will be used.
The following packages have unmet dependencies:
 adb : Breaks: android-tools-adb but 5.1.1.r29-2 is installed
The following actions will resolve these dependencies:

 Remove the following packages:
1) android-tools-adb [5.1.1.r29-2 (now)]

Accept this solution? [Y/n/q/?]
The following NEW packages will be installed:
  adb  android-libadb{a} (D: adb) (adb D: android-libadb)
  android-libbase{a} (D: adb, D: android-libadb) (adb D:
  android-libbase)

  android-libcutils{a} (D: adb, D: android-libadb) (adb D: android-libcutils)
  android-liblog{a} (D: android-libbase, D: android-libcutils) (adb D: 
android-libcutils D: android-liblog)
The following packages will be REMOVED:
  android-tools-adb{a}
The following packages are RECOMMENDED but will NOT be installed:
  android-sdk-platform-tools-common (R: adb)
0 packages upgraded, 5 newly installed, 1 to remove and 0 not upgraded.
Need to get 230 kB of archives. After unpacking 386 kB will be used.
Do you want to continue? [Y/n/?]
Get: 1 http://free.nchc.org.tw/debian unstable/main i386 android-liblog i386 
1:7.0.0+r1-2 [18.4 kB]
Get: 2 http://free.nchc.org.tw/debian unstable/main i386 android-libbase i386 
1:7.0.0+r1-2 [21.0 kB]
Get: 3 http://free.nchc.org.tw/debian unstable/main i386 android-libcutils i386 
1:7.0.0+r1-2 [25.5 kB]
Get: 4 http://free.nchc.org.tw/debian unstable/main i386 android-libadb i386 
1:7.0.0+r1-2 [89.5 kB]
Get: 5 http://free.nchc.org.tw/debian unstable/main i386 adb i386 1:7.0.0+r1-2 
[75.7 kB]
Fetched 230 kB in 1s (187 kB/s)
(Reading database ... 149860 files and directories currently installed.)
Removing android-tools-adb (5.1.1.r29-2) ...
Selecting previously unselected package android-liblog.
(Reading database ... 149853 files and directories currently installed.)
Preparing to unpack .../android-liblog_1%3a7.0.0+r1-2_i386.deb ...
Unpacking android-liblog (1:7.0.0+r1-2) ...
...
Processing triggers for libc-bin (2.24-9) ...

Current status: 0 (+0) broken, 0 (+0) upgradable, 54373 (-1) new.
# aptitude purge ~c
The following packages will be REMOVED:
  android-tools-adb{p} (adb B: android-tools-adb)
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]
(Reading database ... 149882 files and directories currently installed.)
Purging configuration files for android-tools-adb (5.1.1.r29-2) ...

Current status: 0 (+0) broken, 0 (+0) upgradable, 54373 (+0) new.
#

Or maybe it doesn't have anything to do with obsolete vs. not obsolete.
Anyway, here is my apt-config dump:


apt-config-dump.gz
Description: apt-config dump

Bug#851897: dgit: please have generated source packages contain standard patch series

[Sean Whitton]

control: tag -1 +patch

Dear Daniel, Ian,

Thank you for this feedback.

On Thu, Jan 19, 2017 at 05:09:26PM +, Daniel Shahaf wrote:
> Some source packages generated by dgit have a single debian patch, with
> instructions in debian/source/patch-header to use dgit to obtain the
> patch series.  That's advised by dgit-maint-merge(7).
> 
> Please consider having the generated source package contain a proper
> quilt series, in order to make it easier for people to do QA work across
> the archive without learning a different tool for each source package.
> 
> This way, the maintainer would be using dgit with dgit's patch queue
> facilities, but a person who does 'apt-get source' would see a patch
> queueu, regardless of which tools the maintainer uses (dgit or anything
> else).

On Thu, Jan 19, 2017 at 06:33:40PM +, Ian Jackson wrote:
> Control: severity -1 normal
> Control: retitle -1 dgit-maint-merge(7): clarify patch series non-goal

I'd like to state explicitly that a /manually curated/ patch series is
indeed a non-goal of the workflow I describe in dgit-maint-merge(7):

Maintaining convenient and powerful git workflows takes priority
over the usefulness of the raw Debian source package.  The Debian
archive is thought of as an output format.

> Looking at dgit-maint-merge(7), I think it doesn't make this
> particular tradeoff clear enough.  I think perhaps it should be
> enhanced with an additional bullet point, something like this:
> 
>   o  It is not necessary to maintain the divergence from upstream
>  (if any) as a patch series.  That is: it is not necessary to
>  maintain the delta as a stack of individual commits or patches,
>  to be applied in turn to the current upstream.

I'd prefer not to add this as another bullet point, because the second
bullet point already says that manually curating a series of quilt
patches is a non-goal.  Ian's text also overstates the case: you can
often get a perfectly serviceable patch series out of git, using the
sample commands in debian/source/patch-header.

Instead, I'd like to add text to say something about the kinds of
packages for which the workflow is unsuitable.  I'd already been
thinking about submitting a patch to do that since the recent discussion
on -devel, and I think it might be sufficient to close this bug.[1]

Please consider the attached patch.

[1] https://spwhitton.name/blog/entry/jan17vcspkg/

-- 
Sean Whitton
From 691d5b3526710acf78910ad87f9f7ce207ff6d5f Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Thu, 19 Jan 2017 13:35:27 -0700
Subject: [PATCH] dgit-maint-merge(7): Packages for which workflow is
 unsuitable

Signed-off-by: Sean Whitton 
---
 debian/changelog   | 4 
 dgit-maint-merge.7.pod | 6 ++
 2 files changed, 10 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index fcd09b0..9ababee 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,10 @@ dgit (3.3~) unstable; urgency=medium
   Packaging:
   * Remove redundant Recommends on libtext-iconv-perl.
 
+  Documentation:
+  * dgit-maint-merge(7): Discuss packages for which the workflow is
+unsuitable.  [Sean Whitton]  Closes:#851897
+
  --
 
 dgit (3.2) unstable; urgency=medium
diff --git a/dgit-maint-merge.7.pod b/dgit-maint-merge.7.pod
index 0d8b2da..ed51565 100644
--- a/dgit-maint-merge.7.pod
+++ b/dgit-maint-merge.7.pod
@@ -34,6 +34,12 @@ that upstream makes available for download.
 
 =back
 
+This workflow is less suitable for some packages.  When the Debian
+delta is very complex, with large parts not expected to ever be merged
+upstream, it might be preferable to maintain the delta as a rebasing
+patch series.  If this applies to your package, consider
+dgit-maint-gbp(7), and see Debian bug #720177.
+
 =head1 INITIAL DEBIANISATION
 
 This section explains how to start using this workflow with a new
-- 
2.11.0



signature.asc
Description: PGP signature

Bug#851613: src:bottleneck: Tests fail if enabled

[Pietro Battiston]

Il giorno gio, 19/01/2017 alle 15.19 +, Ghislain Vaillant ha
scritto:
> On Thu, 2017-01-19 at 15:55 +0100, Pietro Battiston wrote:
> > Il giorno mar, 17/01/2017 alle 23.26 +, Ghislain Vaillant ha
> > scritto:
> > [...]
> > > Assuming, numpy stays in this version for the release, i.e.
> > > without
> > > the
> > > fix for the regression, then we'd be effectively releasing a
> > > buggy
> > > bottleneck package for Stretch.
> > 
> > I don't consider a software "buggy" just because its tests expose a
> > regression of some other software :-)
> 
> This is true if you consider the software *alone*. Debian is a
> *distribution*, so we should consider the software and its
> environment
> as a whole, which includes its runtime dependencies.

We are in the Debian bug tracker, I gave it as granted that the choice
depends on what's best for Debian.

On the other hand, your reasoning is nice because if it held, it would
mean that we'd be better off if upstream had never released the tests
in the first place, since we wouldn't even be discussing this and
Stretch users wouldn't be at risk of not having bottleneck (which works
fine) included.

Instead it is in the best interest of Stretch if bottleneck is included
_and_ it is in the best interest of Stretch if the regression in numpy
is fixed, and the two aspects are pretty orthogonal. Oh, and it is even
in the best interest of Stretch if by failing (even just in the logs),
its tests help exposing (possible future) regressions in other Debian
packages.

Then, the optimum is clearly that numpy is fixed and tests are enabled,
so let's wait and see.

Pietro

Bug#835940: Bug#851871: RM: remove gcc-5 from stretch

[Adrian Bunk]

On Thu, Jan 19, 2017 at 03:07:03PM +0100, Matthias Klose wrote:
> Package: release.debian.org
> Tags: stretch
> 
> Please remove gcc-5, gcc-5-cross and gcc-5-cross-ports from testing.  Now that
> the linux source is built using gcc-6, the list of packages also needing 
> removal
> are acoording to [1]:
> 
>  - nvida-cuda-toolkit
>  - starpu-contrib
>...

Their fix might actually be blocked by outdated information in #835940.

Quoting the relevant part from #835940:

On Mon, Nov 28, 2016 at 11:23:27AM +0100, Matthias Klose wrote:
> On 28.11.2016 02:08, lumin wrote:
> > Hello guys,
> >
> > I successfully compiled caffe with CUDA_8.0.44-2 and
> > clang-3.8 (the current default clang). Maybe we can
> > replace GCC-5 with Clang-3.8 to solve this problem.
> >
> > That means Stretch still has chance to ship CUDA8,
> > and users are expected to compile with Clang/LLVM
> > instead of GCC-6, as long as the CUDA rDepends
> > compile with clang.
> >
> > I only tested caffe-contrib.
>
> My guess is that clang-3.8 will be gone for the release as well ...


What is the final decision regarding LLVM versions in stretch?


> Matthias

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#851907: graphicsmagick: gm convert: unrecognized operator (-operator).

[Bob Friesenhahn]

On Thu, 19 Jan 2017, Daniel Kahn Gillmor wrote:


Package: graphicsmagick
Version: 1.3.25-7
Severity: normal

gm(1) says:

  -operator channel operator rvalue[%]
 apply a mathematical, bitwise, or value  operator  to  an  image
 channel

But:

0 dkg@alice:~$ gm convert /usr/share/pixmaps/debian-logo.png -operator all 
invert '100%' foo.png
gm convert: Unrecognized operator (-operator).
1 dkg@alice:~$

Somehow this functionality is missing from the compiled build!


The 'invert' keyword sounds useful but the GraphicsMagick 
documentation specifies to use 'Negate' for this purpose.


This is not a bug.

Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/

Bug#848839: AppStream metadata for Wine

[Matthias Klumpp]

2017-01-19 15:13 GMT+01:00 Jens Reyer :
> Hi again Matthias
>
> On 01/17/2017 08:17 PM, Matthias Klumpp wrote:
>> Anyway, Wine is now in the metadata, and after the next dinstall run
>> it should show up in GNOME Software.
>> https://appstream.debian.org/sid/main/metainfo/wine.html
>
> Thanks, the link works fine! But unfortunately wine still doesn't show
> up in the GNOME Software Center (unless you have it installed).

Looks like GNOME Software chokes on the project_group being set to a
group it has no knowledge of and trashes the component directly...
Removing the group and adding categories (
https://www.freedesktop.org/software/appstream/docs/chap-CollectionData.html#tag-ct-categories
) made it show up for me.

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#851551: FutureWarning: CTR mode needs counter parameter, not IV

[Olivier Berger]

On Mon, Jan 16, 2017 at 09:05:15AM +0200, Antonis Christofides wrote:
> 
> I'm not certain this problem is in duplicity or in python-crypto. Since
> yesterday's update to Debian 8.7, all my servers (including the one from which
> I'm reporting this) throw this message when running duplicity with -v2:
> 
> /usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py:141: 
> FutureWarning: CTR mode needs counter parameter, not IV
>   self._cipher = factory.new(key, *args, **kwargs)
> 

It seems that #850025 is dealing with the same issue.

Since the different bugs may not be assigned to the same package I'm reluctant 
to add to the mess by merging or adding dependencies.

Hope this helps, anyway.

Best regards,
-- 
Olivier BERGER 
(OpenPGP: 4096R/7C5BB6A5)
http://www.olivierberger.com/weblog/

Bug#851015: nut: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl

[Laurent Bigonville]

Le 19/01/17 à 19:52, Michael Stapelberg a écrit :

[+aquette, bigon directly]

Are you aware of this issue? This RC bug transitively marked freeradius
for removal from testing. If you need help, please let me know — I have
some incentive to look into it in order to keep freeradius in stretch.

Apparently it lacks of asciidoc-dblatex build-dependency

I'll try do an upload tonight

Bug#851832: [pkg-lxqt-devel] Bug#851832: qtermwidget: missing qtf8proc support

[Alf Gaida]

Thank you very much, nice catch - i initiated and merged the UTF8 
changes upstream lately, but forget to add the dependency beside the 
trigger:


option(USE_UTF8PROC "Use libutf8proc for better Unicode support. Default 
OFF" OFF)


if(USE_UTF8PROC)
find_package(Utf8Proc)
endif()

if (UTF8PROC_FOUND)
add_definitions(-DHAVE_UTF8PROC)
include_directories("${UTF8PROC_INCLUDE_DIRS}")
endif()

So full utf-8 was and is optional - but it reached the stability for 
everyday usage.


Thanks Alf

On 19.01.2017 03:27, Riku Voipio wrote:

Source: qtermwidget
Version: 0.7.1-1
Severity: normal
Tags: patch

The build log states:

-- Could NOT find UTF8PROC (missing:  UTF8PROC_LIBRARY
UTF8PROC_INCLUDE_DIR)

https://buildd.debian.org/status/fetch.php?pkg=qtermwidget=amd64=0.7.1-1=1482363037=0

adding Build-dep helps:

--- qtermwidget-0.7.1/debian/control2016-12-22 00:36:22.0 +0200
+++ qtermwidget-0.7.1/debian/control2017-01-19 10:17:07.0 +0200
@@ -7,7 +7,8 @@
  Priority: optional
  Build-Depends: debhelper (>= 10),
 cmake (>= 3.0.2),
-   qtbase5-dev
+   qtbase5-dev,
+   libutf8proc-dev
  Standards-Version: 3.9.8
  Vcs-Browser: 
https://anonscm.debian.org/git/pkg-lxqt/qtermwidget.git/?h=debian/sid
  Vcs-Git: https://anonscm.debian.org/git/pkg-lxqt/qtermwidget.git -b debian/sid



-- 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-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

___
pkg-lxqt-devel mailing list
pkg-lxqt-de...@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/pkg-lxqt-devel

Bug#851837: RM: libapache2-mod-auth-openidc [s390x] -- ANAIS; package is no longer built on s390x

[Adrian Bunk]

On Thu, Jan 19, 2017 at 03:00:32PM +0100, Christoph Martin wrote:
> Hi Adrian,

Hi Christoph,

> what is the effect of this bug report?

the effect is that libapache2-mod-auth-openidc 2.1.3-1 can enter testing.

> In five days libapache2-mod-auth-openidc (2.1.2-2) with the new
> architecture list would enter testing.

No, it would not, see [1]:

 excuses:
Too young, only 5 of 10 days old
missing build on s390x: libapache2-mod-auth-openidc (from 1.8.10.1-1.2)
Piuparts tested OK - 
https://piuparts.debian.org/sid/source/liba/libapache2-mod-auth-openidc.html
Not considered

After the 10 days, this will still be "Not considered" due to the 
outdated s390x binary.

> If the current testing version is removed before that, will the new
> version be allowed to enter testing again?
> 
> Or will the remove wait until the migration and then be canceled?

The only thing that has to be removed is the s390x binary package.

No source packages and no binary packages on other architectures
will be touched, and their status stays unchanged.

> BTW. the package is really building on s390x but a test is failing. If
> it is necessary for s390x to build, we could disable the tests. But that
> would delay the testing migration again.
> 
> What should we do?

Whether the tests should be disabled on s390x or whether the package 
should no longer be built on s390x is your decision as maintainer,
and this RM is based on your decision as indicated in the 2.1.2-2
changelog.

The RM of the s390x binary is required for 2.1.3-1 testing migration.

If you want to upload 2.1.3-2 with s390x enabled right away, please
close this bug.

If you re-enable s390x building in your package at any point in time 
after the 1.8.10.1-1.2 s390x binary has been removed, it will be built
automatically with no further action required from you.

> CHristoph
> 
> Am 19.01.2017 um 09:35 schrieb Adrian Bunk:
> > Package: ftp.debian.org
> > Severity: normal
> > 
> > 
> > libapache2-mod-auth-openidc (2.1.2-2) unstable; urgency=medium
> > 
> >   * new upload excluding archs which don't build
> > 
> >  -- Christoph Martin   Mon, 09 Jan 2017 11:59:21 +0100

cu
Adrian

[1] https://tracker.debian.org/pkg/libapache2-mod-auth-openidc

-- 

   "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#851907: graphicsmagick: gm convert: unrecognized operator (-operator).

[Daniel Kahn Gillmor]

Package: graphicsmagick
Version: 1.3.25-7
Severity: normal

gm(1) says:

   -operator channel operator rvalue[%]
  apply a mathematical, bitwise, or value  operator  to  an  image
  channel

But:

0 dkg@alice:~$ gm convert /usr/share/pixmaps/debian-logo.png -operator all 
invert '100%' foo.png
gm convert: Unrecognized operator (-operator).
1 dkg@alice:~$

Somehow this functionality is missing from the compiled build!

--dkg

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

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

Versions of packages graphicsmagick depends on:
ii  libc62.24-8
ii  libgomp1 6.2.1-5
ii  libgraphicsmagick-q16-3  1.3.25-7

graphicsmagick recommends no packages.

Versions of packages graphicsmagick suggests:
pn  graphicsmagick-dbg  

-- no debconf information

Bug#813533: inosync: [PATCH] So someone can -c configfile a dot file

[Eric Côté]

Cool, that's fine, thank you :).

On January 19, 2017 6:37:05 AM EST, Carsten Leonhardt  wrote:
>Control: tags -1 - moreinfo
>Control: severity -1 wishlist
>Control: retitle -1 Please allow a dotfile to be used as configfile
>
>Hi Eric,
>
>thanks for your feedback. I'm setting the bug to severity "wishlist",
>maybe someone will come up with a solution.
>
> - Carsten

-- 
Drum carrier for Travelling Spirit Drum

Bug#405762:

[Добринка В . Милушева-Бойкина]

 Căsuța poștală a Depășit Acesta Limită de stocare Apasă aici pentru a 
http://web-admini.my-free.website/  upgrade 
contul tău

Bug#851885: Please add pseudopackage `manpages.debian.org'

[Don Armstrong]

On Thu, 19 Jan 2017, Michael Stapelberg wrote:
> This sounds right to me.

I just need to know what text to use for the description (see below for
an example), and ideally a set of bugs which will be reassigned to the
pseudopackage once it is created.

Pseudopackage Name: manpages.debian.org
Maintainer: Manpages Website Maintainers 
Description: Issues with the Debian Manpages Website and coordination of 
maintenance

Obviously, this means that there can't ever be a packaged called
manpages.debian.org in Debian.


-- 
Don Armstrong  https://www.donarmstrong.com

That's the wonderful thing about crayons. They can take you to more
places than a starship.
 -- Guinan "Star Trek: The Next Generation: Rascals (#6.7)"

Bug#851015: nut: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl

[Arnaud Quette]

Hi Michael,

No idea on the why and not much time to look at it before the week end.
Iirc, dblatex is listed for the manpages generation.

Feel free to upload a fix if you find one.

Thanks and cheers.
Arno

Le 19 janv. 2017 19:57, "Michael Stapelberg"  a
écrit :

> [+aquette, bigon directly]
>
> Are you aware of this issue? This RC bug transitively marked freeradius
> for removal from testing. If you need help, please let me know — I have
> some incentive to look into it in order to keep freeradius in stretch.
>
> Lucas Nussbaum  writes:
>
> > Source: nut
> > Version: 2.7.4-4
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20170111 qa-ftbfs
> > Justification: FTBFS on amd64
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> >
> > Relevant part (hopefully):
> >> make[3]: Entering directory '/<>/docs'
> >> make[3]: Nothing to be done for 'all-am'.
> >> make[3]: Leaving directory '/<>/docs'
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=chunked_format --format=chunked --xsl-file=./chunked.xsl
> user-manual.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=chunked_format --format=chunked --xsl-file=./chunked.xsl
> developer-guide.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=chunked_format --format=chunked --xsl-file=./chunked.xsl
> packager-guide.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=xhtml11_format --format=xhtml --xsl-file=./xhtml.xsl FAQ.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=pdf_format --format=pdf -a docinfo1 user-manual.txt
> >> a2x: WARNING: --destination-dir option is only applicable to HTML based
> outputs
> >> a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/
> asciidoc-dblatex.xsl
> >> Makefile:825: recipe for target 'user-manual.pdf' failed
> >> make[2]: *** [user-manual.pdf] Error 1
> >
> > The full build log is available from:
> >http://aws-logs.debian.net/2017/01/11/nut_2.7.4-4_unstable.log
> >
> > A list of current common problems and possible solutions is available at
> > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to
> contribute!
> >
> > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > failed build was retried once to eliminate random failures.
> >
> >
>
> --
> Best regards,
> Michael
>

Bug#755545: [Pkg-libvirt-maintainers] Bug#755545: Add glusterfs/libgfapi

[Guido Günther]

Hi Gregory,
On Fri, Jan 06, 2017 at 11:02:30PM +0100, Gregory Auzanneau wrote:
> Dear Maintainer,
> 
> As finally, glusterfs was integrated to qemu (into qemu-block-extra) on
> 12/28/2016 which close blocking bugs #775431 and #787112, is the integration
> of glusterfs to libvirt is possible now ?

Think so. I'll do this in experimental once we have 3.0 in testing
(don't want to change dependencies that late in the cycle). We want
recent gluster code anyway so we can enable this in stretch-backports.

Should I forget please ping again ;)
Cheers,
 -- Guido

Bug#851906: dgit clone-dgit-repos-server fails on Debian again

[Ian Jackson]

Package: dgit
Version: 3.6
Severity: important

zealot:d> dgit clone-dgit-repos-server x
Use of uninitialized value $isuite in concatenation (.) or string at 
/usr/bin/dgit line 705.

[after setting $isuite on a hunch]

zealot:d> ~/things/Dgit/dgit/dgit clone-dgit-repos-server x
Cloning into 'x'...
fatal: repository 'https://git.dgit.debian.org/_dgit-repos-server/' not found

[after setting access_forpush]

zealot:d> ~/things/Dgit/dgit clone-dgit-repos-server x
bash: /home/ian/things/Dgit/dgit: Is a directory
zealot:d> ~/things/Dgit/dgit/dgit clone-dgit-repos-server x
Cloning into 'x'...
remote: Counting objects: 7658, done.
remote: Compressing objects: 100% (2657/2657), done.
remote: Total 7658 (delta 5346), reused 7143 (delta 4924)
Receiving objects: 100% (7658/7658), 1.38 MiB | 0 bytes/s, done.
Resolving deltas: 100% (5346/5346), done.
zealot:d> 


-- 
Ian Jackson    These opinions are my own.

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

Bug#851132: [debian-mysql] Bug#851132: Bug#851132: Bug#851132: Bug#851132: Bug#851132: /usr/sbin/mysqld: ssl_ciphers not working; mariadb built without TLS support?

[Georg Richter]

Hi Clint,

I didn't check the compatibility layer for TLS/SSL stuff, there is no layer
for crypto and hashing. I did a quick hack framework for crypto wrapper
(supporting OpenSSL, WolfSSL and GnuTLS) at http://github.com/9EOR9/mrl.

A main difference between OpenSSL and WolfSSL is, that WolfSSL expects
always a  ca from client - if you don't specify one verification needs to
be skipped/turned off explicitly - I'm also not sure if the compatibility
layer works well  for OpenSSL 1.1 (which had a bunch of incompatible API
changes).

The best solution  for MariaDB would be a wrapper library which could be
used by both MariaDB Server and Connector/C - however WolfSSL would not fit
for LGPL licensed Connector/C since it's GPL/commercial licensed.

Also the GnuTLS compatibility layer didn't work well, another hack/proof of
concept  for Yassl replacement by GnuTLS can be found at
https://github.com/MariaDB/server/tree/10.2-good_bye_yassl.

We are aware of all the Yassl problems (no TLS v.1.2 and 1.3, no session
ticket support, no session renegotiation, missing ciphers, limited block
cipher support, etc) and are working on it. Connector/C 3.0 already
supports GnuTLS beside OpenSSL, and SChannel for Windows platforms.

/Georg


On Thu, Jan 19, 2017 at 7:23 PM, Clint Byrum  wrote:

> Excerpts from Georg Richter's message of 2017-01-19 19:06:06 +0100:
> > Hi,
> >
> > WolfSSL has another interface (it's not C++ anymore, but C) and can't
> > replace Yassl on the fly. Beside TLS/SSL communication also hash
> functions
> > and crypto functions need to be migrated.
> >
>
> That's interesting. WolfSSL also has an OpenSSL compatibility layer,
> could that be used?
>
> https://www.wolfssl.com/wolfSSL/Docs-wolfssl-manual-
> 13-openssl-compatibility.html
>



-- 
Georg Richter, Senior Software Engineer
MariaDB Corporation Ab

Bug#850716: XML External Entity attack

[Salvatore Bonaccorso]

Hi,

On Mon, Jan 09, 2017 at 04:28:40PM +0100, Thomas Goirand wrote:
> there was a security hole fixed in python-pysaml2, which allowed XML
> External Entity attacks:
> https://github.com/rohe/pysaml2/pull/379
> https://github.com/rohe/pysaml2/commit/6e09a25d9b4b7aa7a506853210a9a14100b8bc9b

Apparently there was some confusion. To be clear, the above commit now
after re-clarification from MITRE is CVE-2016-10149[1], which means
the initially assigned CVE for the XXE vulnerability in pysaml2 is
still unfixed. Will open another bug for it. See the comments in the
references oss-security post for details.

 [1] https://marc.info/?l=oss-security=148484731923389=2

Regards,
Salvatore

Bug#851824: (ITP: python-humanfriendly -- Python library to make user friendly text interfaces)

[Gaurav Juvekar]

Hi,

Can someone tell me how a single manpage can be used in different packages?

I've written a manpage for the humanfriendly command that both the
python-humanfriendly and python3-humanfriendly versions of this package
will provide. However, lintian says binaries-have-file-conflict for the
manpage.

I've put up my work at
https://github.com/gauravjuvekar/debian-python-humanfriendly


Regards,
Gaurav Juvekar



signature.asc
Description: OpenPGP digital signature