Bug#856183: Acknowledgement (chromium: safe or unsafe defaults)

[Michael Gilbert]

Let me clarify.  I am not going to make a decision about this, you are.

Form a consensus (all involved must agree), and I will accept an
implementation of what ever that turns out to be, but I reserve the
right to exclude any negative participants.

If no consensus forms (if there is any remaining voice of dissent),
the package will stay the way it is.

Again, good luck!

Best wishes,
Mike

Bug#856050: unblock: pkgconf/0.9.12-3

[Helmut Grohne]

On Sat, Feb 25, 2017 at 04:14:11PM +0100, Andrew Shadura wrote:
> On 25/02/17 08:35, Niels Thykier wrote:
> > I got one question about the "Breaks".  Why Breaks and why a versioned
> > breaks rather than an unconditional Conflicts?  AFAICT, pkgconf attempts
> > to be an "mutually exclusive alternative" to pkg-config (a la exim vs.
> > postfix).

The reason for me proposing breaks instead of conflicts was that
unpacking both packages can actually work (due to the use of
diversions), whereas running both maintainer scripts ends up in
unpredictable chaos (both managing the same set of symlinks). We know
that conflicts are harder to solve by apt and thus - generally - have a
slight preference on using breaks.

> Hmm, honestly, I'm not sure what's better in this case. In #842529,
> Helmut mentioned Breaks, so I just went with that. As it is now, pkgconf
> is still co-installable with earlier versions of pkg-config (diversions
> are still in place), but the symlinks make it not possible to have both
> pkg-config 0.29-1 and pkgconf installed (and that's not really needed
> anymore as I added the versioned Provides).

The version restriction initially confused me, but the explanation makes
sense to me.

> If you think Conflicts is more appropriate, I may add change that in the
> upload to unstable.
> 
> Helmut, what's your opinion, by the way?

I don't think that it matters much in this case. I imagine that breaks
vs replaces is not going to make a big difference for apt here. Whether
to use the weakest form (versioned breaks) or a strong form (conflicts)
is up to you.

Looking at the experimental binary package however, I note that I fail
to find a diversion for pkg-config-dpkghook and its hook-config. Thus
the experimental package would actually need a conflicts relation now.
See e.g.:

| # dpkg -B --unpack pkgconf_0.9.12-2_amd64.deb 
| dpkg: considering deconfiguration of pkg-config, which would be broken by 
installation of pkgconf ...
| dpkg: yes, will deconfigure pkg-config (broken by pkgconf)
| (Reading database ... 9798 files and directories currently installed.)
| Preparing to unpack pkgconf_0.9.12-2_amd64.deb ...
| De-configuring pkg-config (0.29-4) ...
| Adding 'diversion of /usr/bin/pkg-config to /usr/bin/pkg-config.real by 
pkgconf'
| Adding 'diversion of /usr/share/aclocal/pkg.m4 to 
/usr/share/aclocal/pkg.real.m4 by pkgconf'
| Adding 'diversion of /usr/share/man/man1/pkg-config.1.gz to 
/usr/share/man/man1/pkg-config.real.1.gz by pkgconf'
| Adding 'diversion of /usr/share/pkg-config-crosswrapper to 
/usr/share/pkg-config-crosswrapper.real by pkgconf'
| Unpacking pkgconf (0.9.12-2) ...
| dpkg: error processing archive pkgconf_0.9.12-2_amd64.deb (--unpack):
|  trying to overwrite '/etc/dpkg/dpkg.cfg.d/pkg-config-hook-config', which is 
also in package pkg-config 0.29-4
| Errors were encountered while processing:
|  pkgconf_0.9.12-2_amd64.deb
| #

So I consider the experimental package rc buggy and propose either
renaming the conflicting files or adding a conflicts relation. Since
neither /usr/share/pkg-config-crosswrapper nor
/etc/dpkg/dpkg.cfg.d/pkg-config-hook-config are part of the pkg-config
API, I'd just rename both to avoid the need for diversions here. Even
when using conflicts, conffiles will not go away and reusing the
hook-config file from pkg-config can result in a mess of its own. So I
actually recommend doing the renaming (s/pkg-config/pkgconf/) in any
case (even when adding conflicts). If you end up using conflicts, all
the other diversions can go away as well.

Helmut

Bug#856184: nautilus: hidden directories becomes the output standard of the Nautilus every time when i press CTRL + H inside on "move file" to move (transfer) some file to a hidden directory.

[Leandro]

Package: nautilus
Version: 3.14.1-2
Severity: minor

Dear Maintainer,

   * What led up to the situation? Press CTRL + H inside of the "move to" of 
the nautilus.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Reconfigure the nautilus on the Dconfig. This solved the 
problem, but he returns every time when i do this.
   * What was the outcome of this action?
   * What outcome did you expect instead? Solve the bug, of course.



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

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

Versions of packages nautilus depends on:
ii  desktop-file-utils 0.22-1
ii  gsettings-desktop-schemas  3.14.1-1
ii  gvfs   1.22.2-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-18+deb8u7
ii  libcairo-gobject2  1.14.0-2.1+deb8u2
ii  libcairo2  1.14.0-2.1+deb8u2
ii  libexempi3 2.2.1-2
ii  libexif12  0.6.21-2
ii  libgail-3-03.14.5-1+deb8u1
ii  libgdk-pixbuf2.0-0 2.31.1-2+deb8u5
ii  libglib2.0-0   2.42.1-1+b1
ii  libglib2.0-data2.42.1-1
ii  libgnome-desktop-3-10  3.14.1-1
ii  libgtk-3-0 3.14.5-1+deb8u1
ii  libnautilus-extension1a3.14.1-2
ii  libnotify4 0.7.6-2
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libselinux12.3-2
ii  libtracker-sparql-1.0-01.2.4-2
ii  libx11-6   2:1.6.2-3
ii  libxml22.9.1+dfsg1-5+deb8u4
ii  nautilus-data  3.14.1-2
ii  shared-mime-info   1.3-1

Versions of packages nautilus recommends:
ii  eject  2.1.5+deb1+cvs20081104-13.1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gnome-sushi3.12.0-2+b1
ii  gvfs-backends  1.22.2-1
ii  librsvg2-common2.40.5-1+deb8u2

Versions of packages nautilus suggests:
pn  brasero
ii  eog3.14.1-1
ii  evince [pdf-viewer]3.14.1-2+deb8u1
ii  mpg321 [mp3-decoder]   0.3.2-1.1
ii  totem  3.14.0-2
ii  tracker1.2.4-2
ii  vlc-nox [mp3-decoder]  1:2.2.1-dmo3+deb8u1
ii  xdg-user-dirs  0.15-2

-- no debconf information

Bug#856183: chromium: safe or unsafe defaults

[Michael Gilbert]

package: src:chromium-browser
severity: important
version: 55.0.2883.75-6

This is the topic du jour.  I honestly don't care either way, but I
will only tolerate rational conversation about it.  The first
negative, emotional, or insulting statement here (and that includes
provocative language like "sane") loses!  And just to be clear, that
means the opposing camp's viewpoint gets implemented.

Good luck!

Best wishes,
Mike

P.S. Not really, since that would be too easy to game.  Negativity
does mean that I will not read or consider your argument.

Bug#856182: Package does not include node.d directory required by nodejs plugins

[Thomas Leuxner]

Package: netdata
Version: 1.5.0+dfsg-1
Severity: serious

The package misses to include the node.d directory and its files, especially 
the node_modules directory required by nodejs plugins.

Missing files:

$ l /usr/lib/x86_64-linux-gnu/netdata/node.d/
total 68
-rw-r--r-- 1 root root 32377 Feb 25 11:56 named.node.js
drwxr-xr-x 3 root root  4096 Feb 25 11:56 node_modules
-rw-r--r-- 1 root root 0 Feb 25 11:56 README.md
-rw-r--r-- 1 root root 10555 Feb 25 11:56 sma_webbox.node.js
-rw-r--r-- 1 root root 18060 Feb 25 11:56 snmp.node.js

The actual files seem to be processed upon build, but don't make it to the 
package:

$ l ./debian/tmp/usr/lib/x86_64-linux-gnu/netdata/node.d
total 68
-rw-r--r-- 1 root root 0 Feb 26 06:25 README.md
-rw-r--r-- 1 root root 32377 Feb 26 06:25 named.node.js
drwxr-xr-x 3 root root  4096 Feb 26 06:25 node_modules
-rw-r--r-- 1 root root 10555 Feb 26 06:25 sma_webbox.node.js
-rw-r--r-- 1 root root 18060 Feb 26 06:25 snmp.node.js

Without the files included it is impossible to run nodejs plugins.

Regards
Thomas


signature.asc
Description: Digital signature

Bug#856181: blueman: can't receive file in sudoers user

[Dio Oktarianos Putra]

Package: blueman
Version: 2.0.4-1
Severity: normal

Dear Maintainer,

I just noticed that my sudoers user, can't receive any file from my Android
Device. Trying this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804908
but still no luck, beside obex.service isn't found in my systemctl output.

Strangely, when using blueman to receive any file with normal user (no sudo
privilege) is completely worked. I see any confirmation in my MATE DE when
trying to receive file via bluetooth with normal user.

Any suggestion?.



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

Versions of packages blueman depends on:
ii  bluez   5.43-1
ii  bluez-obexd 5.43-1
ii  dbus1.10.16-1
ii  dconf-gsettings-backend [gsettings-backend] 0.26.0-2+b1
ii  gir1.2-appindicator3-0.10.4.92-4
ii  gir1.2-gdkpixbuf-2.02.36.4-1
ii  gir1.2-glib-2.0 1.50.0-1+b1
ii  gir1.2-gtk-3.0  3.22.8-1
ii  gir1.2-notify-0.7   0.7.7-1+b1
ii  gir1.2-pango-1.01.40.3-3
ii  gnome-icon-theme3.12.0-2
ii  libbluetooth3   5.43-1
ii  libc6   2.24-9
ii  libglib2.0-02.50.2-2
ii  libpulse-mainloop-glib0 10.0-1
ii  libpython3.53.5.3-1
ii  librsvg2-common 2.40.16-1+b1
ii  mate-notification-daemon [notification-daemon]  1.16.1-1
ii  notification-daemon 3.20.0-1
ii  python3 3.5.3-1
ii  python3-cairo   1.10.0+dfsg-5+b1
ii  python3-dbus1.2.4-1
ii  python3-gi  3.22.0-2
ii  python3-gi-cairo3.22.0-2

Versions of packages blueman recommends:
ii  policykit-1  0.105-17

blueman suggests no packages.

-- no debconf information

Bug#856180: eeschema: Failed assertion when editing component with aliases

[J.P. Larocque]

Package: kicad
Version: 4.0.5+dfsg1-4~bpo8+1
Severity: normal

Eeschema crashes upon the dialog "The new component contains alias
names that conflict with entries in the component library...".  This
occurs when trying to create a new component by editing an existing
component as a template, and that original component has aliases
defined.

I'm using kicad from jessie-backports.  It appears this version
(4.0.5+dfsg1-4~bpo8+1) derives exactly from 4.0.5+dfsg1-4 (the version
in testing and unstable), according to the changelog for the bpo
version, so I believe the issue applies to testing and unstable as
well.

Steps to reproduce:

1) Start with a newly-created temporary user which has a mostly-empty
   homedir.  This probably won't be strictly necessary, but I did it
   to ensure that no part of my configuration would influence the
   reproducibility of this issue.

2) Run eeschema.

3) Make a library available to eeschema:

   a) Click the Preferences menu, then Component Libraries.

   b) An assertion failure message appears.  Click Continue.

   c) Click Add.

   d) Choose /usr/share/kicad/library/device.lib .

   e) Click OK.

4) Click Tools->Library Editor.  The Library Editor window appears.

5) Click File->Current Library.

6) Double-click "device".

7) Choose the "Load component to edit from the current library" icon
   in the toolbar.

8) Double-click "C_Feedthrough".  As far as I can tell, any component
   which has defined aliases will trigger this bug, but "C_Feedthrough"
   is one concrete example.

9) Edit the "C_Feedthrough" component name text.  (Hover mouse over
   the text "C_Feedthrough" and press "e".)

10) Replace "C_Feedthrough" with any unique value (e.g. "Bogus").

11) A dialog box appears: "The new component contains alias names that
conflict with entries in the component library 'device'.  Do you
wish to remove all of the conflicting aliases from this
component?"

At the same time, an assertion failure message appears in another
window.  It is not possible to continue in this instance; the
message keeps reappearing in a loop.

This is the assertion failure message and backtrace:

ASSERT INFO:
/build/kicad-4.0.5+dfsg1/eeschema/libeditframe.cpp(515): assert "alias != 
__null" failed in OnUpdateViewDoc(): Alias  not found.

BACKTRACE:
[1] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, 
wxEvent&) const
[2] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&)
[3] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[4] wxEvtHandler::TryHereOnly(wxEvent&)
[5] wxEvtHandler::DoTryChain(wxEvent&)
[6] wxEvtHandler::ProcessEvent(wxEvent&)
[7] wxWindowBase::TryAfter(wxEvent&)
[8] wxAuiToolBar::DoIdleUpdate()
[9] wxAuiToolBar::UpdateWindowUI(long)
[10] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[11] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[12] wxFrame::SendIdleEvents(wxIdleEvent&)
[13] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[14] wxFrame::SendIdleEvents(wxIdleEvent&)
[15] wxAppBase::ProcessIdle()
[16] wxApp::DoIdle()
[17] g_main_context_dispatch
[18] g_main_loop_run
[19] gtk_dialog_run
[20] wxMessageDialog::ShowModal()
[21] wxMessageBox(wxString const&, wxString const&, long, wxWindow*, int, int)
[22] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, 
wxEvent&) const
[23] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&)
[24] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[25] wxEvtHandler::TryHereOnly(wxEvent&)
[26] wxEvtHandler::DoTryChain(wxEvent&)
[27] wxEvtHandler::ProcessEvent(wxEvent&)
[28] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, 
wxEvent&) const
[29] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&)
[30] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[31] wxEvtHandler::TryHereOnly(wxEvent&)
[32] wxEvtHandler::ProcessEventLocally(wxEvent&)
[33] wxEvtHandler::ProcessEvent(wxEvent&)
[34] wxScrollHelperEvtHandler::ProcessEvent(wxEvent&)
[35] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[36] wxWindow::GTKDoInsertTextFromIM(char const*)
[37] g_cclosure_marshal_VOID__STRINGv
[38] g_signal_emit_valist
[39] g_signal_emit_by_name
[40] g_cclosure_marshal_VOID__STRINGv
[41] g_signal_emit_valist
[42] g_signal_emit_by_name
[43] g_closure_invoke
[44] g_signal_emit_valist
[45] g_signal_emit
[46] gtk_window_propagate_key_event
[47] g_closure_invoke
[48] g_signal_emit_valist
[49] g_signal_emit
[50] gtk_propagate_event
[51] gtk_main_do_event
[52] g_main_context_dispatch
[53] g_main_loop_run
[54] gtk_main
[55] wxGUIEventLoop::DoRun()
[56] wxEventLoopBase::Run()
[57] wxAppConsoleBase::MainLoop()
[58] wxEntry(int&, wchar_t**)
[59] __libc_start_main

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

Kernel: Linux 4.9.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC

Bug#841401: deferred upload

[Michael Gilbert]

control: tag -1 pending

Uploaded to delayed/5 to give -4 a chance to migrate.

Best wishes,
Mike

Bug#856179: ITP: polybar -- fast and easy-to-use status bar

[Jason Pleau]

Package: wnpp
Severity: wishlist
Owner: Jason Pleau 

* Package name: polybar
  Version : 3.0.4
  Upstream Author : Michael Carlberg 
* URL : https://github.com/jaagr/polybar/
* License : MIT/Expat
  Programming Lang: C++
  Description : fast and easy-to-use status bar

The main purpose of Polybar is to help users create awesome status bars. It has
built-in functionality to display information about the most commonly used
services, such as:

 * Systray icons
 * Window title
 * Playback controls and status display for MPD using libmpdclient
 * ALSA volume controls
 * Workspace and desktop panel for bspwm and i3
 * Workspace module for EWMH compliant window managers
 * Keyboard layout and indicator status
 * CPU and memory load indicator
 * Battery display
 * Network connection details
 * Backlight level
 * Date and time label
 * Time-based shell script execution
 * Command output tailing
 * User-defined menu tree
 * Inter-process messaging

Users can also develop their own modules and/or integrate modules created by
others.

It can be used a replacement for status bars / panels used in different window
managers and desktop environments.

I plan to maintain this package in collab-maint on alioth

Bug#856151: RFS: gexiv2/0.10.4-2

[Sean Whitton]

control: tag -1 +moreinfo
control: owner -1 !

Dear Jason,

You are missing a # before the number of the bug you are closing in your
changelog.  I just checked against the bug closing regexp and I believe
that this will fail to close the bug.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#784612: [anki] schroot-based workaround (Re: Qt4's WebKit removal)

[Greg Price]

On Fri, 10 Jun 2016 15:38:53 +0900 Richard Möhn 
wrote:
> This is not a good solution for everyone, but I'm now running Anki
> inside a Debian Jessie Docker container. See here for how to do it:
> http://cloj.de/AnkiDocker/

I much appreciated Richard's recipe. I found Docker rather finicky to work
with, though, e.g. to make tweaks to the Jessie environment, and I wasn't
consistently able to keep my Japanese input method working with the
resulting Anki. So I'm now running Anki inside a Debian Jessie schroot,
which I've found simpler to manage. See here for how:
https://github.com/gnprice/anki-jessie

Perhaps someone else will find this recipe helpful, as I found Richard's,
in the time before Anki 2.1 stabilizes upstream and can enter
stretch-backports.

Best,
Greg

Bug#856039: xserver-xorg-core: no keyboard and no mouse

[Michael Gilbert]

control: tag -1 moreinfo

On Fri, Feb 24, 2017 at 9:33 AM, Toni Mueller wrote:
> Package: xserver-xorg-core

Did you only install xserver-xorg-core?  If so, you will be missing a
lot of important packages, like xserver-xorg-input-libinput, which
provides mouse support.  To get all packages needed, consider
installing xserver-xorg instead.

[0] is related.

Best wishes,
Mike

[0] http://bugs.debian.org/854322

Bug#853119: Request to take a look at #855930

[Norbert Preining]

On Sun, 26 Feb 2017, Norbert Preining wrote:
> I will try to run it in a clean cowbuilder with only the build-deps
> installed and see what might be the reason.

Just done this, too, worked without a hinch:
'lualatex' '--interaction' 'errorstopmode' '--jobname' 'lualatex-example' 
'\RequirePackage[extension=.pdf]{texdepends}\input{lualatex-example.tex}'
This is LuaTeX, Version 0.95.0 (TeX Live 2016/Debian) 
 restricted system commands enabled.
LaTeX2e <2017/01/01> patch level 1
(using cache: /var/lib/texmf/luatex-cache/generic)
luaotfload | main : initialization completed in 0.102 secondsBabel <3.9r> and 
hyphenation patterns for 1 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/latex-make/texdepends.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty))
(./lualatex-example.tex
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
luaotfload | db : Font names database not found, generating new one.
luaotfload | db : This can take several minutes; please be patient.(compiling 
luc: /var/li
b/texmf/luatex-cache/generic/fonts/otl/lmroman10-regular.luc)(save: /var/lib/te
xmf/luatex-cache/generic/fonts/otl/lmroman10-regular.lua)(save: /var/lib/texmf/
luatex-cache/generic/fonts/otl/lmroman10-regular.luc)))
(/usr/share/texlive/texmf-dist/tex/lualatex/luacode/luacode.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty)
(/usr/share/texlive/texmf-dist/tex/luatex/luatexbase/luatexbase.sty
(/usr/share/texlive/texmf-dist/tex/luatex/ctablestack/ctablestack.sty)))
No file lualatex-example.aux.
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./lualatex-example.aux)
)
 371 words of node memory still in use:
   2 hlist, 1 vlist, 1 rule, 7 glue, 5 attribute, 40 glue_spec, 5 attribute_lis
t, 1 write nodes
   avail lists: 2:19,3:2,4:2,5:13,6:34,7:25,8:1,9:6,11:2

Output written on lualatex-example.pdf (1 page, 4483 bytes).
Transcript written on lualatex-example.log.




One idea: is /var writable???

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#856064: libdbd-mysql-perl: reads of floats currupted as 0

[Brian May]

gregor herrmann  writes:

> Brian, do you have a chance to test this version against amavisd-new?

I am not able to test this myself. If however you can make a version
available for testing (experimental maybe?) I can ask people to test it.

> Since Debian is in deep freeze, I'm just trying to fix reported RC
> bugs. If you think the mentioned zerofill bug is worth having it in
> stretch, please file a bug with the appropriate severity and backport
> the fix to apply against 4.041 after applying the float conversion
> patch (or before, then the conversion patch needs changes).

Just some extra information I neglected to mention before:

amavisd-new has already been removed from testing. I think the chances
of getting it back in are remote - however I have asked the release team
- see #856067.

Even if amavisd-new doesn't get included, if this bug gets fixed it
might help distribute amavisd-new some other way (maybe outside Debian).
-- 
Brian May 

Bug#814057: diffoscope: Add option to ignore mtimes

[Chris Lamb]

Hi Leo,

First, thanks for getting back to us :)

> Now, it would be nice if diffoscope had an option to report these
> differences :) 

Sure. I think the best way forward would be to file a fresh, new wishlist
bug expressing exactly what you currently see, and what you would like to
see instead.

That way we don't confuse it with the history of this particular bug. A
small testcase — just shell snippets, no need for an actual diffoscope
Python testcase! — would be absolutely perfect.

(Closing this one in the meantime...)


Regards,

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

Bug#856178: Installation on Minnowboard Turbot, successful with some minor issues.

[Peter Michael Green]

Package: installation-reports
Severity: normal



-- Package-specific info:

Boot method: SD card with isohybrid DVD image
Image version: Stretch weekly build DVD 1
Date: 

Machine: Minnowboard Turbot MBT-2210
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [E]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

I booted the installer by writing the DVD image to a SD card. The minnowboards
UEFI firmware picked this up and booted from it fine.

The detect CD step failed to find the SD card automatically. I had to manually
point it 

When I got to the partitioning step I got some errors about loading installer
components. I discovered this was due to accidentally ejecting the SD card.
(probablly when I plugged the network cable in) I reinserted the SD card and 
manually unmounted and remounted it and was able to continue the install.

I got a warning that the installer thought there may be legacy bios-mode
operating systems on the machine and asking whether I wanted a bios mode or 
uefi mode install. I don't know why this happened as the only media connected 
was the SD card with the installer and a brand new blank hard drive. I chose
to continue in UEFI mode (I don't think the minnowboard even supports legacy
bios)


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20170213-00:04"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux minnowboard 4.9.0-1-amd64 #1 SMP Debian 4.9.6-3 (2017-01-28) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series SoC Transaction Register [8086:0f00] (rev 11)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: iosf_mbi_pci
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom 
Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 11)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: 00:13.0 SATA controller [0106]: Intel Corporation Atom Processor 
E3800 Series SATA AHCI Controller [8086:0f23] (rev 11)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Atom Processor 
Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [8086:0f35] (rev 11)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:1a.0 Encryption controller [1080]: Intel Corporation Atom 
Processor Z36xxx/Z37xxx Series Trusted Execution Engine [8086:0f18] (rev 11)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series High Definition Audio Controller [8086:0f04] (rev 11)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Atom Processor E3800 
Series PCI Express Root Port 1 [8086:0f48] (rev 11)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation Atom Processor E3800 
Series PCI Express Root Port 3 [8086:0f4c] (rev 11)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation Atom Processor E3800 
Series PCI Express Root Port 4 [8086:0f4e] (rev 11)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Power Control Unit [8086:0f1c] (rev 11)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation Atom Processor E3800 Series 
SMBus Controller [8086:0f12] (rev 11)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
lspci -knn: Subsystem: Realtek Semiconductor Co., Ltd. 

Bug#856177: lua-sandbox FTBFS on alpha (and hppa) due to test suite failure.

[Michael Cree]

Source: lua-sandbox
Version: 1.2.1-4
Severity: wishlist
User: debian-al...@lists.debian.org
Usertags: alpha

lua-sandbox FTBFS on alpha due to a test-suite failure [1]

The following tests FAILED:
 11 - test_heka_sandbox (Failed)

Running that test manually reveals the failure occurs randomly at
line 376 and sometimes at line 464, both of which are asserts that
the mean or standard deviation in time incurred during running tests
is not zero.

The test suite uses the posix clock (clock_gettime()) but on Alpha
that clock has a resolution of the timer interrupt which is at best
about 1ms.  Since the test runs much faster than this a zero time
delta is often measured which the test suite detects and considers
to be a reason for failure.  On hppa the build fails at the same
test [2] and I presume it is probably for similar reasons.

Upstream is aware that there is an issue [3] however it seems one
cannot comment further there without obtaining a github login.

As an experiment I modified the code in src/util/util.c, function
lsb_get_time(), to be:

unsigned long long lsb_get_time()
{
#if defined(__alpha__) && defined(__linux__)
  return __builtin_alpha_rpcc() & 0xULL;
#elif defined(HAVE_CLOCK_GETTIME)
  struct timespec ts;
  clock_gettime(CLOCK_MONOTONIC, &ts);
  return ts.tv_sec * 10ULL + ts.tv_nsec;
#elif ...

to use the processor cycle counter on Alpha which is a 32 bit register
that is incremented every CPU clock cycle.  With the above the test
suite passes on Alpha when run on a UP system.  However I am not
comfortable to recommend the above as a fix because:

1) It might break on an SMP system where every CPU has its own
cycle counter and there is no guarantee they are in sync, and no
guarantee that the start time is read on the same CPU as the stop
time.

2) The counter wraps back to zero after the 32 bits are exhuasted,
a period of about 7 to 8s on the system I tested, and only 3 to 4s
on the buildds.  If the above is used in any timing test longer than
that it could break.

3) The function might be exported from the library and the above might
break intended uses of the function.

Cheers
Michael.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=lua-sandbox&arch=alpha&ver=1.2.1-4&stamp=1487927865&raw=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=lua-sandbox&arch=hppa&ver=1.2.1-4&stamp=1483652248&raw=0
[3] https://github.com/mozilla-services/lua_sandbox/issues/185

Bug#855538: youtube-dl: fails to download from zdf.de

[Jiri Palecek]

Hello,

On 23.2.2017 02:17, Rogério Brito wrote:

On Wed, Feb 22, 2017 at 7:18 PM, Jiri Palecek  wrote:

On Sun, 19 Feb 2017 23:25:38 +0100 Holger Levsen wrote:

I've verified that just replacing zdf.py from the 2017.02.17 upstream
version
was sufficient to fix this issue:

Curiously enough, the Czech TV changed their video player about the same
time, so it suffers from the same problem (and updating fixes it).

Well, that's bad, but thanks for the notification that these problems
are already fixed in the upstream version. BTW, which file is it that
fixes it for your use case, Jiri?
TBH I didn't try to fix it in the same way, as I don't need it that 
much. But it should be fixed by this commit: 
https://github.com/rg3/youtube-dl/commit/5cb2d36c82abf3b753910afe3013b274e31a247a



I'm thinking of preparing a release with just a few patches on top of
the current release already in testing.


However I understand packaging a version every 10 days may not be feasible.

The problem is not so much that of building a new version every 10
days. The problem is that sites are breaking their layout and inner
workings faster than what a package needs to transition to testing.

I'm thinking of continuing preparing new upstream versions and
uploading them to sid and make a branch right now that will track
changes meant only for the future stable release... Holger, I
understand that you are interested in this, is that right?


IMO that would be a nightmare to maintain. It would probably result in 
as many releases, with the added risk of breakage and need of testing. 
Anyway, you decide.


Thanks for your effort
Jiri Palecek

Bug#856039: xserver-xorg-core: no keyboard and no mouse

[John Paul Adrian Glaubitz]

Hi!

Do you have the evdev kernel module loaded? evdev is required for X.Org
to get data from input devices through the kernel.

This indicates that evdev may be missing:

[  9670.895] (II) config/udev: Adding input device   USB Keyboard 
(/dev/input/event0)
[  9670.895] (II) No input driver specified, ignoring this device.
[  9670.895] (II) This device may have been added with another device file.

Are you by any chance using a very old window manager or running X by
typing "startx"? If yes, this might not load "evdev" automatically and
you have to take care of that yourself.

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

Bug#820381: Can't reproduce

[shirish शिरीष]

at bottom :-

On 25/02/2017, Hilko Bengen  wrote:
> Hi,
>
> I can reproduce the bug on neither amd64 (4.9.0-1-amd64) nor i386
> (4.9.0-1-686-pae).
>
> Cheers,
> -Hilko
>
> --
> To unsubscribe, send mail to 820381-unsubscr...@bugs.debian.org.
>

Could you share what attempts you did to see if the error occurs ?

-- 
  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#853119: Request to take a look at #855930

[Norbert Preining]

Hi Tomasz,

> can I ask you to take a look at https://bugs.debian.org/855930, to see
> if it is some variation of the problem in this bug?

Did that, the logs are very unclear. The log only states:
 ==> building  lualatex-example.pdf <==
Running: 'lualatex' '--interaction' 'errorstopmode' '--jobname' 
'lualatex-example' 
'\RequirePackage[extension=.pdf]{texdepends}\input{lualatex-example.tex}'
sed: can't read lualatex-example.log: No such file or directory
*

Which is suprising. On my normal system here I can run the above command
without problems:

$ 'lualatex' '--interaction' 'errorstopmode' '--jobname' 'lualatex-example' 
'\RequirePackage[extension=.pdf]{texdepends}\input{lualatex-example.tex}'
This is LuaTeX, Version 0.95.0 (TeX Live 2016/Debian) 
 restricted system commands enabled.

Output written on lualatex-example.pdf (1 page, 4576 bytes).
Transcript written on lualatex-example.log.
$

I will try to run it in a clean cowbuilder with only the build-deps
installed and see what might be the reason.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#856116: error redis-server_3.2.8-1_amd64.deb

[Chris Lamb]

Hi Igor,

Please retain all CCs in future (ie. 856...@bugs.debian.org).

> Yes, I am runninig last version 3.2.8-1 from this repo:
> https://packages.debian.org/sid/amd64/redis-server/download
> 
> I have added screens with errors, after the changes of configs i have no 
> errors.

What errors?


Regards,

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

Bug#855705: [munin-monitoring/munin] munin-cgi-graph CGI::param security problem (#721)

[Holger Levsen]

On Sat, Feb 25, 2017 at 10:57:57PM +, Holger Levsen wrote:
> will import in a moment, together with the wheezy-lts upload.

I've now done the imports of the wheezy-lts and jessie-security uploads into
git (as signed tags) and also uploaded 2.0.31-1 to sid. Will ask for stretch
unblock and aging for faster migration tomorrow, and once that has happened
I'll take care of backports too.

Thanks again to everyone involved!


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#855038: All test ends with "INFO: SKIP: All tests. Package cannot be tested with piuparts:"

[Andreas Beckmann]

On 2017-02-25 14:46, Holger Levsen wrote:
> Hi Andreas,
> 
> On Mon, Feb 13, 2017 at 02:41:50PM +0100, Andreas Beckmann wrote:
>> I see what should be the problem.
>> As a workaround please edit
>> piuparts, around line 1790:
>>if not settings.scriptsdirs:
>> -return
>> +return 0
> 
> do you have a better solution for this now? I'd like to upload 0.76 to fix
> this issue ASAP and then I'd also like to start working on 0.77 and merge the
> patch for #850917 into develop…

An *untested* patch for doing this in a more clean way is at the end of the 
series:

Andreas Beckmann (6):
  scripts/pre_remove_40_find_missing_md5sums: handle filenames containing 
backslashes
  switch to default-mysql-server (aka mariadb) for selected packages
  p: make install_over_symlink tests fail without 
--warn-on-install-over-symlink
  p.conf.anbe: set --warn-on-install-over-symlink for tests ending before 
stretch
  p.conf: set --warn-on-install-over-symlink for tests ending before stretch
  p: do not require --scriptsdir for proper operation


Andreas

Bug#856004: khtml: please build-depen on libssl1.0-dev for Stretch

[John Paul Adrian Glaubitz]

On 02/25/2017 09:39 PM, Sebastian Andrzej Siewior wrote:
> No. I assume that it might use QT's internal networking which is 1.0 and if
> they mix then bad things will happen.
> 
> The two functions marked * have no error handling if the function is missing.
> Not using SSLv23_client_method() means that the the user of this class has to
> try again with TLSv1_client_method() member which will only allow a TLS1.0
> handshake. This is not what you want because TLS1.0 itself is deprecated and
> the v23 method would allow the maximum possible TLS level (which is currently
> 1.2).

But the question is whether SSL support is actually relevant in khtml at all.

As you can see from the list of reverse dependencies, there's actually not
much that is using khtml and the very few packages that use it are offline
only like SystemSettings or Kiten. So, I don't think any SSL code is actually
ever used.

I mean, if you really insist to rebuild khtml with libssl1.0-dev, then please
just let's go ahead in order to get the number of RC bugs for Stretch down.

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

Bug#856176: ITP: pweave -- scientific report generator with embedded Python computations

[Ghislain Antony Vaillant]

Package: wnpp
Severity: wishlist
Owner: Ghislain Antony Vaillant 

* Package name: pweave
  Version : 0.25
  Upstream Author : Matti Pastell 
* URL : http://mpastell.com/pweave/
* License : BSD
  Programming Lang: Python
  Description : scientific report generator with embedded Python 
computations

Pweave is a scientific report generator and a literate programming tool for
Python. Pweave can capture the results and plots from data analysis and works
well with NumPy, SciPy and matplotlib. It is able to run Python code from
source document and include the results and capture matplotlib plots in the
output.

This software is a dependency to the future scientific report plugin for the
Spyder IDE. The packaging will be be co-maintained the Debian Science Team
alongside the spyder source package.

Bug#856175: GUI is broken

[Anton Gladky]

Package: yade
Version: 2017.01a-2
Severity: serious
Tags: upstream

After calling "from yade import qt ; qt.Controller()" only the
black window is shown without control elements. The same
effect after calling qt.View().

Bug#855705: [munin-monitoring/munin] munin-cgi-graph CGI::param security problem (#721)

[Holger Levsen]

Hi Salvatore,

On Sat, Feb 25, 2017 at 09:48:35PM +0100, Salvatore Bonaccorso wrote:
> Well, basically because I was not sitting the whole time in front of
> my laptop ;-)

ah, that makes perfect sense! :)
 
> It is out now as DSA-3794-1.

cool, thanks!

> Cool thanks for working on 2.0.31-1!

just now uploaded to sid!
 
> > I think it's just the RELEASE file which needs to be removed from git there.
> > (It's gone from master…)
> Yes exactly, it was about the RELEASE file indeed.

ah, sigh…
 
> > will do, please ping me once you uploaded in case I'll forget. 
> *ping*. Thanks a lot for handling it.

will import in a moment, together with the wheezy-lts upload.

Thanks all!


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#853233: jessie-pu: package groovy/1.8.6-4+deb8u1

[Adam D. Barratt]

Control: tags -1 + pending

On Mon, 2017-02-20 at 01:56 +0100, Markus Koschany wrote:
> On 19.02.2017 21:45, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Mon, 2017-01-30 at 19:28 +0100, Markus Koschany wrote:
> >> I would like to upload a security update for Groovy in Jessie.
> >> (Debdiff is attached) This is Debian bug #851408 or CVE-2016-6814. The
> >> security team has marked this CVE as no-dsa but it would be good to
> >> fix CVE-2016-6814 in Jessie too. I will also file a bug report for
> >> Groovy2 which is affected by the same issue shortly.
> > 
> > Please go ahead.
> > 
> 
> Thank you. Uploaded.

Flagged for acceptance.

Regards,

Adam

Bug#854621: jessie-pu: package uwsgi/2.0.7-1

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2017-02-19 at 22:15 +0100, Jonas Smedegaard wrote:
> Quoting Adam D. Barratt (2017-02-19 21:43:08)
> > On Wed, 2017-02-08 at 20:10 +0100, Jonas Smedegaard wrote:
> >> a FTBFS was discovered which affects uwsgi in stable (and only that): 
> >> Bug#854535
> >
> > + * Add patch cherry-picked upstream to fix compilation with recent GCC.
> >
> > My understanding was that the change was in glibc, not gcc; is that
> > incorrect?
> 
> Indeed it was glibc, not gcc.  Thanks for catching my mistake!
> 
> 
> > Please go ahead.
> 
> Thanks.
> 
> I will now upload with changelog entry adjusted, targeted "jessie", and 
> closing bug#854535 - but not mention nor close this bug#854621.  Hope 
> that is correct procedure - if not please do correct me.

It was correct; flagged for acceptance. Thanks.

Regards,

Adam

Bug#853162: jessie-pu: package xmobar/0.22-1

[Adam D. Barratt]

Control: tags -1 + pending

On Mon, 2017-02-20 at 01:36 +0200, Apollon Oikonomopoulos wrote:
> On 20:48 Sun 19 Feb , Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Mon, 2017-01-30 at 13:45 +0200, Apollon Oikonomopoulos wrote:
> > > I would like to update xmobar in Jessie to fix #835547. As outlined in 
> > > #835547, xmobar has a weather plugin that uses NOAA's feed. NOAA 
> > > recently changed their feed URLs and xmobar has been updated upstream to 
> > > reflect that change.
> > 
> > Please go ahead.
> > 
> > Regards,
> > 
> > Adam
> 
> Uploaded, thanks!

Flagged for acceptance.

Regards,

Adam

Bug#853235: jessie-pu: package groovy/2.2.2+dfsg-3+deb8u1

[Adam D. Barratt]

Control: tags -1 + pending

On Mon, 2017-02-20 at 01:56 +0100, Markus Koschany wrote:
> On 19.02.2017 21:44, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Mon, 2017-01-30 at 19:38 +0100, Markus Koschany wrote:
> >> groovy2 is also affected by CVE-2016-6814. The patch is almost
> >> identical to the one used in groovy. Please find attached the debdiff.
> > 
> > Please go ahead.
> > 
> 
> Thank you. Uploaded.

Flagged for acceptance.

Regards,

Adam

Bug#854811: jessie-pu: package gnome-screenshot/3.14.0-1

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2017-02-19 at 20:41 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Fri, 2017-02-10 at 17:27 +0100, Moritz Schlarb wrote:
> > If used without GUI (e.g. by pressing the PrintScr key or from a shell with 
> > no
> > arguments), gnome-screenshot will simply take a screenshot of the whole 
> > screen
> > and store it in the pictures directory with a filename containing the 
> > current
> > timestamp with colons (i.e. "Screenshot from 2017-01-10 16:46:39.png").
> > This leads to problems with some filesystems (e.g. vfat, ntfs).
> > 
> > See package bug #850836 (https://bugs.debian.org/cgi-
> > bin/bugreport.cgi?bug=850836)
> 
> +gnome-screenshot (3.14.0-1.1) UNRELEASED; urgency=medium
> 
> As with the g-s-d package, the version here should be 3.14.0-1+deb8u1
> and the distribution "jessie".
> 
> Please go ahead, with the changes noted above.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#854812: jessie-pu: package gnome-settings-daemon/3.14.2-3

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2017-02-19 at 20:38 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Fri, 2017-02-10 at 17:29 +0100, Moritz Schlarb wrote:
> > If taking a screenshot by pressing the PrintScr key the image file will be
> > stored in the pictures directory with a filename containing the current
> > timestamp with colons (i.e. "Screenshot from 2017-01-10 16:46:39.png").
> > This leads to problems with some filesystems (e.g. vfat, ntfs).
> > This was also already reported upstream in
> > https://bugzilla.gnome.org/show_bug.cgi?id=740520.
> > gnome-settings-daemon 3.22.1-1, the version currently in testing already
> > contains this fix from upstream (i.e. "Screenshot from 2017-01-10
> > 16-46-39.png").
> > 
> > See package bug #850837 (https://bugs.debian.org/cgi-
> > bin/bugreport.cgi?bug=850837)
> 
> +gnome-settings-daemon (3.14.2-3.1) UNRELEASED; urgency=medium
> 
> The version should be 3.14.2-3+deb8u1 and the distribution should be
> "jessie". With those changes, please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#856174: jessie-pu: package nvidia-graphics-drivers-legacy-304xx/304.135-1

[Andreas Beckmann]

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

Hi,

a new upstream release is needed to fix the latest CVE series in the
legacy driver too.

Intentionally no +deb8u1 suffix to reduce the version number inflation
when backporting this to wheezy(-backports).

The "Depend on a setuid root Xserver." changelog entry was a mismerge
in the previous pu upload, this change is not needed in stable.


Andreas
Index: debian/copyright
===
--- debian/copyright	(.../tags/304.134-0~deb8u1)	(revision 7212)
+++ debian/copyright	(.../branches/jessie)	(revision 7212)
@@ -18,7 +18,7 @@
 
 Files: debian/*
 Copyright: 2001-2010 Randall Donald 
-   2009-2016 Andreas Beckmann 
+   2009-2017 Andreas Beckmann 
2010 Russ Allbery 
Based on packages by Christopher Cheney.
 License: GPL-2.0+
Index: debian/module/debian/patches/drm-driver-legacy.patch
===
--- debian/module/debian/patches/drm-driver-legacy.patch	(.../tags/304.134-0~deb8u1)	(revision 0)
+++ debian/module/debian/patches/drm-driver-legacy.patch	(.../branches/jessie)	(revision 7212)
@@ -0,0 +1,20 @@
+Author: Luca Boccassi 
+Description: Fix kernel module load on 4.9 and greater
+ From kernel 4.9 and newer (commit fa5386459f06) non-modesetting drivers have
+ to use the DRM flag DRIVER_LEGACY. Without this flag the kernel module does
+ not load correctly.
+
+--- a/nv-drm.c
 b/nv-drm.c
+@@ -71,7 +71,11 @@
+ };
+ 
+ static struct drm_driver nv_drm_driver = {
++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 9, 0)
+ .driver_features = 0,
++#else
++.driver_features = DRIVER_LEGACY,
++#endif
+ .load = nv_drm_load,
+ .unload = nv_drm_unload,
+ .fops = &nv_drm_fops,
Index: debian/module/debian/patches/disable-mtrr.patch
===
--- debian/module/debian/patches/disable-mtrr.patch	(.../tags/304.134-0~deb8u1)	(revision 7212)
+++ debian/module/debian/patches/disable-mtrr.patch	(.../branches/jessie)	(revision 7212)
@@ -23,3 +23,15 @@
  #if !defined(NV_VMWARE) && defined(CONFIG_MTRR)
  #include 
  #endif
+--- a/os-agp.c
 b/os-agp.c
+@@ -180,8 +180,8 @@
+ {
+ nv_mtrr_del(nv->agp.arch_phys_wc_add_token, agp_info.aper_base,
+ agp_info.aper_size << 20);
+-#endif
+ }
++#endif
+ release:
+ NV_AGPGART_BACKEND_RELEASE(drm_agp_p, nvl->agp_bridge);
+ bailout:
Index: debian/module/debian/patches/deprecated-cpu-events.patch
===
--- debian/module/debian/patches/deprecated-cpu-events.patch	(.../tags/304.134-0~deb8u1)	(revision 0)
+++ debian/module/debian/patches/deprecated-cpu-events.patch	(.../branches/jessie)	(revision 7212)
@@ -0,0 +1,49 @@
+Author: Luca Boccassi 
+Description: Fix kernel module build on 4.10 and greater
+ From kernel 4.10 and newer (commit 530e9b76ae8f8) CPU_DOWN_FAILED and
+ CPU_DOWN_PREPARE are no longer available as events, together with their
+ callback registers.
+--- a/nv-pat.c
 b/nv-pat.c
+@@ -210,19 +210,23 @@
+ 
+ switch (action)
+ {
++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 10, 0)
+ case CPU_DOWN_FAILED:
++#endif
+ case CPU_ONLINE:
+ if (cpu == (NvUPtr)hcpu)
+ nv_setup_pat_entries(NULL);
+ else
+ NV_SMP_CALL_FUNCTION(nv_setup_pat_entries, hcpu, 1);
+ break;
++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 10, 0)
+ case CPU_DOWN_PREPARE:
+ if (cpu == (NvUPtr)hcpu)
+ nv_restore_pat_entries(NULL);
+ else
+ NV_SMP_CALL_FUNCTION(nv_restore_pat_entries, hcpu, 1);
+ break;
++#endif
+ }
+ 
+ put_cpu();
+@@ -252,7 +256,7 @@
+ if (!disable_pat)
+ {
+ nv_enable_pat_support();
+-#if defined(NV_ENABLE_PAT_SUPPORT) && defined(NV_ENABLE_HOTPLUG_CPU)
++#if defined(NV_ENABLE_PAT_SUPPORT) && defined(NV_ENABLE_HOTPLUG_CPU) && LINUX_VERSION_CODE < KERNEL_VERSION(4, 10, 0)
+ if (nv_pat_mode == NV_PAT_MODE_BUILTIN)
+ {
+ if (register_hotcpu_notifier(&nv_hotcpu_nfb) != 0)
+@@ -279,7 +283,7 @@
+ if (nv_pat_mode == NV_PAT_MODE_BUILTIN)
+ {
+ nv_disable_pat_support();
+-#if defined(NV_ENABLE_PAT_SUPPORT) && defined(NV_ENABLE_HOTPLUG_CPU)
++#if defined(NV_ENABLE_PAT_SUPPORT) && defined(NV_ENABLE_HOTPLUG_CPU) && LINUX_VERSION_CODE < KERNEL_VERSION(4, 10, 0)
+ unregister_hotcpu_notifier(&nv_hotcpu_nfb);
+ #endif
+ }
Index: debian/module/debian/patches/series.in
===
--- debian/module/debian/patches/series.in	(.../tags/304.134-0~deb8u1)	(revision 7212)
+++ debian/module/debian/patches/series.in	(.../branches/jessie)	(revision 7212)
@@ -1,5 +1,7 @@
 # kernel support
 fix-typos.pa

Bug#856033: ITP: brailleimg -- produce text images and graphs abusing Braille glyphs

[Samuel Thibault]

Adam Borowski, on sam. 25 févr. 2017 22:31:57 +0100, wrote:
> On Sat, Feb 25, 2017 at 08:05:32PM +0100, Samuel Thibault wrote:
> > Adam Borowski, on sam. 25 févr. 2017 18:24:33 +0100, wrote:
> > > gnuplot relies on being able to place labels within the image, which works
> > > for ASCII and maybe Latin/Greek/Cyrillic but, except for most terminals, 
> > > not
> > > for anything else.
> > 
> > Then gnuplot is missing taking into account the value returned by
> > wcwidth() (0, 1, 2, ...), that's the bug.
> 
> I don't know whether gnuplot is doing it correctly, I haven't tested

Actually it doesn't even properly handle latin1 characters in utf-8
locale.

Samuel

Bug#856033: ITP: brailleimg -- produce text images and graphs abusing Braille glyphs

[Adam Borowski]

On Sat, Feb 25, 2017 at 10:44:12PM +0100, Samuel Thibault wrote:
> Adam Borowski, on sam. 25 févr. 2017 22:31:57 +0100, wrote:
> > On Sat, Feb 25, 2017 at 08:05:32PM +0100, Samuel Thibault wrote:
> > > But for characters that have single-width, they are really
> > > aligned with a proper fixed-width font.
> > 
> > Depends on your software.  xterm, libvte, pterm, rxvt-unicode get it right,
> > mousepad, firefox, chromium and Microsoft Edge don't.
> 
> Ok, but would one really look at the output of text-gnuplot in such
> software?  Cases where I happened to use the text-gnuplot were always
> inside an xterm or such.

Well, if you run an _x_term, you can just as well use X forwarding or toss a
png/svg over.  On the other hand, mailing a graph or putting it in a commit
message will meet a variety of clients, many of them in a browser. 
Alternatively, you can place the image on some random web server, but that's
often tedious, and unlikely to stay 10 years from now.

> > I don't know whether gnuplot is doing it correctly, I haven't tested -- but
> > even if it does, the output will be misrendered by browsers.
> 
> But if the output is to be rendered in a browser, one would use a png or
> svg output :)

The output is meant to be rendered in a proper $DEITY-fearing mail/usenet
client, a rightful text editor[1], less or git's built-in pager.  It's just
that _some_ heretics read their mail in a buggy GUI client or a web page,
view commit messages on github rather than locally, and so on.  And in case
their web browser is not elinks, we need to avoid bugs.


Meow!

[1]. Which excludes both emacs and vi, of course!
-- 
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
  ./configure --host=zx-spectrum --build=pdp11

Bug#856172: redmine-mysql install, no sql config, apt-get remove --purge gives syntax error

[Ejdesgaard]

Package: redmine
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
apt-get install redmine redmine-mysql
# skipped database configuration
apt-get remove --purge redmine-mysql

#Folowed by the following snippet
root@redmine-test:~# apt-get autoremove
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  dbconfig-common dbconfig-sqlite3 fonts-lato imagemagick-6-common 
javascript-common libcurl3 libdbi-perl libfftw3-double3 libglib2.0-0 
libglib2.0-data libgomp1 libjs-coffeescript libjs-jquery libjs-source-map 
libjs-uglify
  liblqr-1-0 libltdl7 libmagickcore-6.q16-3 libmagickwand-6.q16-3 libreadline5 
libruby2.3 libterm-readkey-perl libuv1 libxslt1.1 libyaml-0-2 nodejs passenger 
rake redmine redmine-sqlite ruby ruby-actionmailer
  ruby-actionpack ruby-actionpack-action-caching ruby-actionpack-xml-parser 
ruby-actionview ruby-activejob ruby-activemodel ruby-activerecord 
ruby-activesupport ruby-addressable ruby-arel ruby-atomic ruby-binding-of-caller
  ruby-blankslate ruby-builder ruby-bundler ruby-byebug ruby-coderay 
ruby-coffee-rails ruby-coffee-script ruby-coffee-script-source ruby-columnize 
ruby-concurrent ruby-css-parser ruby-debug-inspector ruby-did-you-mean
  ruby-erubis ruby-eventmachine ruby-execjs ruby-ffi ruby-globalid ruby-hike 
ruby-hmac ruby-htmlentities ruby-i18n ruby-jbuilder ruby-jquery-rails ruby-json 
ruby-listen ruby-loofah ruby-mail ruby-mime-types ruby-mimemagic
  ruby-minitest ruby-molinillo ruby-multi-json ruby-net-http-persistent 
ruby-net-ldap ruby-net-telnet ruby-nokogiri ruby-oj ruby-openid ruby-pkg-config 
ruby-polyglot ruby-power-assert ruby-protected-attributes ruby-rack
  ruby-rack-openid ruby-rack-test ruby-rails ruby-rails-deprecated-sanitizer 
ruby-rails-dom-testing ruby-rails-html-sanitizer ruby-rails-observers 
ruby-railties ruby-rb-inotify ruby-rbpdf ruby-rbpdf-font ruby-redcarpet
  ruby-request-store ruby-rmagick ruby-roadie ruby-roadie-rails ruby-sass 
ruby-sass-rails ruby-sdoc ruby-spring ruby-sprockets ruby-sprockets-rails 
ruby-sqlite3 ruby-test-unit ruby-thor ruby-thread-safe ruby-tilt
  ruby-treetop ruby-turbolinks ruby-tzinfo ruby-uglifier ruby-web-console 
ruby2.3 rubygems-integration shared-mime-info sqlite3 unzip xdg-user-dirs zip
0 upgraded, 0 newly installed, 127 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 135 MB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 37171 files and directories currently installed.)
Removing redmine (3.3.1-3) ...
/var/lib/dpkg/info/redmine.prerm: 33: [: =: unexpected operator
ls: cannot access '/etc/redmine/*/database.yml': No such file or directory
dirname: missing operand
Try 'dirname --help' for more information.
basename: missing operand
Try 'basename --help' for more information.
dpkg: error processing package redmine (--remove):
 subprocess installed post-removal script returned error exit status 123
Removing redmine-sqlite (3.3.1-3) ...
...


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
# packages got remvoed as expected, but the unexpected operator warning should 
not happen

   * What was the outcome of this action?
# OK
   * What outcome did you expect instead?
# OK with no error warnings.

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


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

Kernel: Linux 4.9.0-1-amd64 (SMP w/1 CPU core)
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)

Bug#856145: /usr/lib/fwupd/fwupd: Segfault everytime it starts

[Mario.Limonciello]

Yes,

It's caused by protection in the systemd service. It doesn't replicate if 
manually started.

Upstream is discussing the proper fixes and I'll issue an updated package early 
next week with the results.

Sent using Boxer
On Feb 25, 2017 09:31, Laurent Bigonville  wrote:
Package: fwupd
Version: 0.8.0-2
Severity: grave
File: /usr/lib/fwupd/fwupd
Justification: renders package unusable

Hi,

On both my laptop and my desktop, fwupd segfaults at every startup.

Same when using fwupdmgr, the daemon crashes.

I feel that some of the system protections from the .service file

If I'm adding -v in the service file, I see the following output:

fév 25 16:24:58 fornost systemd[1]: Starting Firmware update daemon...
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0770 Fu  Verbose debugging 
enabled (on console 0)
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0770 As  run AsStore:load
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0770 As  run 
AsStore:load{per-user}
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0770 As  run 
AsStore:load{per-system}
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0772 As  run 
AsStore:store-from-file{/usr/share/app-info/xmls/org.freedesktop.fwupd.xml}
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0773 As  run 
AsStore:store-from-root
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0773 As  using icon path 
/usr/share/app-info/icons/fwupd
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0773 As  run AsStore:match-addons
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0773 As  adding existing file: 
/usr/share/app-info/xmls/org.freedesktop.fwupd.xml
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0773 As  run 
AsStore:store-from-file{/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_non-free_dep11_Components-amd64.yml.gz}
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0779 As  run 
AsStore:store-from-file{/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_main_dep11_Components-amd64.yml.gz}
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0466 As  run 
AsStore:store-from-file{/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_contrib_dep11_Components-amd64.yml.gz}
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0469 As  adding existing file: 
/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_non-free_dep11_Components-amd64.yml.gz
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0469 As  adding existing file: 
/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_main_dep11_Components-amd64.yml.gz
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0469 As  adding existing file: 
/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_contrib_dep11_Components-amd64.yml.gz
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0469 As  run 
AsStore:store-from-file{/var/cache/app-info/xmls/fwupd.xml}
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0470 As  run 
AsStore:store-from-root
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0470 As  using icon path 
/var/cache/app-info/icons/debian-sid-contrib
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0471 As  run AsStore:match-addons
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0472 As  adding existing file: 
/var/cache/app-info/xmls/fwupd.xml
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0472 As  run AsStore:match-addons
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0472 As  Emitting ::changed() 
[store-load]
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0472 Fu  Loading fallback values 
from /etc/fwupd.conf
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0479 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_steelseries.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0480 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_test.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0480 Fu  performing init() on 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_test.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0480 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_ebitdo.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0480 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_usb.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0480 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_colorhug.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0482 Fu  performing init() on 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_colorhug.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0482 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_udev.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0483 Fu  performing init() on 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_udev.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0483 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_dfu.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0484 Fu  performing init() on 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_dfu.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0484 Fu  addi

Bug#855848: unblock: python-pymysql/0.7.10-1

[Ondrej Novy]

Hi,

2017-02-25 22:13 GMT+01:00 Adam D. Barratt :
>
> Why does it also include changes which appear to be in no way related to
> fixing either bug, namely a debhelper compat bump?
>

this change was already in our Git repo and I considered it harm-less. Of
course I hard tested it.

+My colleague already requested similar unblock (
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854057) with same
debhelper bump so I thought it's acceptable.

Thank you.

-- 
Best regards
 Ondřej Nový

Email: n...@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B

Bug#856171: jessie-pu: package nvidia-graphics-drivers/340.102-1

[Andreas Beckmann]

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

Hi,

to fix the next round of CVEs in nvidia-graphics-drivers, we need a new
upstream release in stable, again.
Intentionally no +deb8u1 suffix, since I want to prevent version
inflation in the followup pu request for nvidia-graphics-modules.
The Linux 4.10 support patches are not needed for stable, but make the
live easier for people running current kernels - this is also what we
ship in nvidia-graphics-drivers-legacy-340xx for stretch.


Andreas
Index: debian/changelog
===
--- debian/changelog	(.../tags/340.101-1)	(revision 7208)
+++ debian/changelog	(.../branches/340)	(revision 7208)
@@ -1,3 +1,19 @@
+nvidia-graphics-drivers (340.102-1) jessie; urgency=medium
+
+  * New upstream legacy 340xx branch release 340.102 (2017-02-14).
+* Fixed CVE-2017-0309, CVE-2017-0310, CVE-2017-0311, CVE-2017-0318,
+  CVE-2017-0321.  (Closes: #855277)
+
+  [ Andreas Beckmann ]
+  * unregister_proc_on_failure.patch: New, unregister procfs entries during
+error unwind if loading the module failed.  (Closes: #764639)
+
+  [ Luca Boccassi ]
+  * Add deprecated-cpu-events.patch and vmf-address.patch to fix kernel
+module build on Linux 4.10 and newer.
+
+ -- Andreas Beckmann   Fri, 10 Feb 2017 23:05:58 +0100
+
 nvidia-graphics-drivers (340.101-1) jessie; urgency=medium
 
   * New upstream legacy 340xx branch release 340.101 (2016-12-14).
Index: debian/module/debian/patches/deprecated-cpu-events.patch
===
--- debian/module/debian/patches/deprecated-cpu-events.patch	(.../tags/340.101-1)	(revision 0)
+++ debian/module/debian/patches/deprecated-cpu-events.patch	(.../branches/340)	(revision 7208)
@@ -0,0 +1,49 @@
+Author: Luca Boccassi 
+Description: Fix kernel module build on 4.10 and greater
+ From kernel 4.10 and newer (commit 530e9b76ae8f8) CPU_DOWN_FAILED and
+ CPU_DOWN_PREPARE are no longer available as events, together with their
+ callback registers.
+--- a/nv-pat.c
 b/nv-pat.c
+@@ -210,19 +210,23 @@
+ 
+ switch (action)
+ {
++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 10, 0)
+ case CPU_DOWN_FAILED:
++#endif
+ case CPU_ONLINE:
+ if (cpu == (NvUPtr)hcpu)
+ nv_setup_pat_entries(NULL);
+ else
+ NV_SMP_CALL_FUNCTION(nv_setup_pat_entries, hcpu, 1);
+ break;
++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 10, 0)
+ case CPU_DOWN_PREPARE:
+ if (cpu == (NvUPtr)hcpu)
+ nv_restore_pat_entries(NULL);
+ else
+ NV_SMP_CALL_FUNCTION(nv_restore_pat_entries, hcpu, 1);
+ break;
++#endif
+ }
+ 
+ put_cpu();
+@@ -252,7 +256,7 @@
+ if (!disable_pat)
+ {
+ nv_enable_pat_support();
+-#if defined(NV_ENABLE_PAT_SUPPORT) && defined(NV_ENABLE_HOTPLUG_CPU)
++#if defined(NV_ENABLE_PAT_SUPPORT) && defined(NV_ENABLE_HOTPLUG_CPU) && LINUX_VERSION_CODE < KERNEL_VERSION(4, 10, 0)
+ if (nv_pat_mode == NV_PAT_MODE_BUILTIN)
+ {
+ if (register_hotcpu_notifier(&nv_hotcpu_nfb) != 0)
+@@ -279,7 +283,7 @@
+ if (nv_pat_mode == NV_PAT_MODE_BUILTIN)
+ {
+ nv_disable_pat_support();
+-#if defined(NV_ENABLE_PAT_SUPPORT) && defined(NV_ENABLE_HOTPLUG_CPU)
++#if defined(NV_ENABLE_PAT_SUPPORT) && defined(NV_ENABLE_HOTPLUG_CPU) && LINUX_VERSION_CODE < KERNEL_VERSION(4, 10, 0)
+ unregister_hotcpu_notifier(&nv_hotcpu_nfb);
+ #endif
+ }
Index: debian/module/debian/patches/series.in
===
--- debian/module/debian/patches/series.in	(.../tags/340.101-1)	(revision 7208)
+++ debian/module/debian/patches/series.in	(.../branches/340)	(revision 7208)
@@ -1,5 +1,8 @@
 # kernel support
 drm-driver-legacy.patch
+unregister_procfs_on_failure.patch
+deprecated-cpu-events.patch
+vmf-address.patch
 
 # build system updates
 separate-makefile-kbuild.patch
Index: debian/module/debian/patches/unregister_procfs_on_failure.patch
===
--- debian/module/debian/patches/unregister_procfs_on_failure.patch	(.../tags/340.101-1)	(revision 0)
+++ debian/module/debian/patches/unregister_procfs_on_failure.patch	(.../branches/340)	(revision 7208)
@@ -0,0 +1,28 @@
+Author: Andreas Beckmann 
+Description: unregister procfs upon module load failure
+ the nvidia module may leave stale proc entries if it refuses to be
+ loaded becase nouveau is already loaded and has claimed the device
+ .
+ the error unwinding in nvidia_init_module() is insane
+ (375.26 looks much better)
+ .
+ this patch is probably not correct in all cases, but the unwinding is
+ not reverse linear in creation and the gotos are all across everything
+ .
+ leaving stale proc entries prevents the nvidia module from loading ag

Bug#856064: libdbd-mysql-perl: reads of floats currupted as 0

[gregor herrmann]

On Sat, 25 Feb 2017 01:18:04 +0100, p...@cpan.org wrote:

> > > Upstream patch:
> > > https://github.com/perl5-dbi/DBD-mysql/pull/102
> > 
> > This patch doesn't apply against 4.041-1 in Debian (or 4.041
> > upstream), and neither against the master branch in the upstream repo
> > (so unless I'm missing something, this pull request won't work
> > as-is),
> 
> That patch in github PR 102 applies cleanly on DBD-mysql master branch. 
> It is based on top of master branch. Patch is not merged yet.

I probably hadn't updated one of the git trees, sorry for that.
 
> > Pali, could you perhaps come up with a patch that applies against
> > 4.041?
> This one is for libdbd-mysql-perl_4.041-1.dsc:

Thanks very much!
Patch added to our git repo.

Brian, do you have a chance to test this version against amavisd-new?
 
> But if you are fixing "regressions" from older versions, consider apply 
> also fix for zerofill.

Since Debian is in deep freeze, I'm just trying to fix reported RC
bugs. If you think the mentioned zerofill bug is worth having it in
stretch, please file a bug with the appropriate severity and backport
the fix to apply against 4.041 after applying the float conversion
patch (or before, then the conversion patch needs changes).
 
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: Sinéad O'Connor: All Apologies


signature.asc
Description: Digital Signature

Bug#856033: ITP: brailleimg -- produce text images and graphs abusing Braille glyphs

[Samuel Thibault]

Adam Borowski, on sam. 25 févr. 2017 22:31:57 +0100, wrote:
> On Sat, Feb 25, 2017 at 08:05:32PM +0100, Samuel Thibault wrote:
> > That's expected: some characters have double-width, others have
> > zero-width.
> 
> My test sheet accounts for that: it includes only wcwidth()==1 and 2
> characters (recently updated for unstable's glibc).

Ah, ok, sorry I didn't actually check :)

> > But for characters that have single-width, they are really
> > aligned with a proper fixed-width font.
> 
> Depends on your software.  xterm, libvte, pterm, rxvt-unicode get it right,
> mousepad, firefox, chromium and Microsoft Edge don't.

Ok, but would one really look at the output of text-gnuplot in such
software?  Cases where I happened to use the text-gnuplot were always
inside an xterm or such.

In other words: it's not because in some odd cases things go wrong that
one shouldn't implement the often-used case.

> > > gnuplot relies on being able to place labels within the image, which works
> > > for ASCII and maybe Latin/Greek/Cyrillic but, except for most terminals, 
> > > not
> > > for anything else.
> > 
> > Then gnuplot is missing taking into account the value returned by
> > wcwidth() (0, 1, 2, ...), that's the bug.
> 
> I don't know whether gnuplot is doing it correctly, I haven't tested -- but
> even if it does, the output will be misrendered by browsers.

But if the output is to be rendered in a browser, one would use a png or
svg output :)

Samuel

Bug#856064: Pending fixes for bugs in the libdbd-mysql-perl package

[pkg-perl-maintainers]

tag 856064 + pending
thanks

Some bugs in the libdbd-mysql-perl package are closed in revision
01546f17b9774a5a42dc46ef072fb075fedca62f in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdbd-mysql-perl.git/commit/?id=01546f1

Commit message:

Add regression-fix-float_type_conversion.patch

to fix a regression in the conversion of floats which under some
circumstances simply returned 0.

Thanks: Brian May for the bug report, and Pali Rohár for backporting his 
fix to 4.041.
Closes: #856064

Bug#856163: debmirror: minor typo error

[Colin Watson]

Control: tag -1 pending

On Sat, Feb 25, 2017 at 08:22:06PM +0100, Yvan Masson wrote:
> There is a small typo error in debmirror script line 845:
> 
> ...
> say("Veriftying checksums.") if $verify_checksums;

Thanks; fixed for the next upload.

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

Bug#855779: Rename package

[Ole Streicher]

Control: retitle -1 ITP: eag-healpix -- Handling of HEALPix sky pixellization

Since the package is upstream called "eag-HEALPIX" 
(see github directory), I will use the shorter name as well.

The alioth git repo will also be renamed.

Cheers

Ole

Bug#856033: ITP: brailleimg -- produce text images and graphs abusing Braille glyphs

[Adam Borowski]

On Sat, Feb 25, 2017 at 08:05:32PM +0100, Samuel Thibault wrote:
> Adam Borowski, on sam. 25 févr. 2017 18:24:33 +0100, wrote:
> > Alas, it won't work: I see that, while alignment of the graph itself works
> > well, anything but terminals (which force a char-cell grid) fails to give
> > Braille and ASCII characters the same width, despite requesting fixed-width
> > display.
> 
> That's not normal: fixed-width fonts should really have fixed-width for
> the characters used by gnuplot.

"Should have" and "have" are different things. :(

> > You can see how bad it is on https://angband.pl/doc/alluni.txt -- you should
> > get an aligned grid with right edge of every full block forming an even
> > vertical line, yet most blocks fail to align even within themselves.
> 
> That's expected: some characters have double-width, others have
> zero-width.

My test sheet accounts for that: it includes only wcwidth()==1 and 2
characters (recently updated for unstable's glibc).  You can see that most
lines include 64 characters, CJK ones have 32, a few lines are mixed.

> But for characters that have single-width, they are really
> aligned with a proper fixed-width font.

Depends on your software.  xterm, libvte, pterm, rxvt-unicode get it right,
mousepad, firefox, chromium and Microsoft Edge don't.  They prefer
appearance over accuracy, and when borrowing a glyph from another font, they
use the other font's horizontal advance which breaks the fixed width rule.

> > gnuplot relies on being able to place labels within the image, which works
> > for ASCII and maybe Latin/Greek/Cyrillic but, except for most terminals, not
> > for anything else.
> 
> Then gnuplot is missing taking into account the value returned by
> wcwidth() (0, 1, 2, ...), that's the bug.

I don't know whether gnuplot is doing it correctly, I haven't tested -- but
even if it does, the output will be misrendered by browsers.

This is not restricted to Braille tricks, same happens if your label
includes letters that happen to not be in the recipient's chosen font, and
you can't control the latter.


Thus, the only safe way to use Braille for drawing is to not mix it with any
other character range at all -- or at most, place labels exclusively to the
right of a rectangular graph.  Even labels at the bottom turned out to be
badly shifted.


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

Bug#856169: Chromium installs a setuid binary without obvious need nor warning

[Michael Gilbert]

control: severity -1 wishlist
control: retitle -1 chromium: switch to namespace sandbox

The sandbox is a necessary security feature.  A bug years ago doesn't
necessarily mean that it is faulty today.  There are lots of new
security bugs in chrome every few weeks, and rarely do they have to do
with the sandbox.

That said, there is a more modern sandboxing approach that uses
namespaces [0], but it is too late to change to it for stretch.

Best wishes,
Mike

[0]https://chromium.googlesource.com/chromium/src/+/master/docs/linux_sandboxing.md

Bug#856111: failed install: no keyboard support on armhf:BananaPi

[Ben Hutchings]

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

On Sat, 2017-02-25 at 10:05 +0100, Peter Palfrader wrote:
[...]
> After copying the firmware and installer to the SDcard, I set the
> environment and booted the installer in uboot using:
> | setenv console tty1
> | setenv bootargs console=tty1 fb=false
> | boot
> 
> The kernel boots, the syslogger starts, I get prompted with the
> 'Select a language' dialog, but my USB keyboard does not work in d-i (it
> did in uboot).

We're not including the musb USB host driver needed for this platform
(or several other host drivers whose source is outside
drivers/usb/host).

Ben.

-- 
Ben Hutchings
All the simple programs have been written, and all the good names
taken.



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

Bug#856170: molly-guard: hostname should not be case-sensitive

[Nicolas Braud-Santoni]

Package: molly-guard
Version: 0.4.5-1.1
Severity: wishlist

Dear Maintainer,

molly-guard's 30-query-hostname script performs a case-sensitive
comparison of the short-form hostname with user input, which is
rather inconvenient since hostnames (at least in DNS) are
case-insensitive anyhow:

> nicoo@AlGrothendieck:~$ sudo reboot
> [sudo] password for nicoo:
> Sorry, try again.
> [sudo] password for nicoo:
> I: molly-guard: reboot is always molly-guarded on this system.
> Please type in hostname of the machine to reboot: algrothendieck
> Good thing I asked; I won't reboot AlGrothendieck ...
> W: aborting reboot due to 30-query-hostname exiting with code 1.


Would a patch changing this behaviour be considered for inclusion?
If so, I would happily provide one.


Best,

  nicoo

Bug#855848: unblock: python-pymysql/0.7.10-1

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Wed, 2017-02-22 at 13:33 +0100, Ondřej Nový wrote:
> I uploaded stable update (subminor version change) of python-pymysql to sid 
> which fixies security
> bug:
> * **SECURITY FIX**: Raise RuntimeError when received LOAD_LOCAL packet
>   while ``loacal_infile=False``.
> (from upstream changelog)
> 
> And MariaDB compatibility:
> * Raise SERVER_LOST error for MariaDB's shutdown packet (#540)
> 
> And have no break-API changes.

Why does it also include changes which appear to be in no way related to
fixing either bug, namely a debhelper compat bump?

Regards,

Adam

Bug#848064: radicale: Add debconf support for basic configuration

[James Valleroy]

On 01/24/2017 01:20 PM, Jonas Smedegaard wrote:
> Quoting James Valleroy (2017-01-23 23:48:00)
>> On Tue, 13 Dec 2016 12:14:52 -0500 James Valleroy
>>  wrote:
>>> The attached patch set implements this, by adding several debconf 
>>> questions to set the server hostnames, base url, well-known paths, 
>>> authentication type, and rights type. These questions all have low 
>>> priority. I used augtool (from augeas-tools) to read/modify the 
>>> config file, and ucf to merge user settings with updates to the 
>>> packaged file.
>>
>> After sending this patch, I discovered this rule given in the Debconf 
>> Programmer's Tutorial:
>> "Note that the config script is run before the package is unpacked. It 
>> should only use commands that are in essential packages."
>>
>> But in the patch I submitted (part 0002), I used augtool in 
>> debian/radicale.config to parse the ini-file config and read current 
>> settings from disk. So that is a problem for the 0002 and 0003 patches 
>> above.

I'm attaching another patch that switches debian/radicale.config to use
awk to read the current configuration. This should resolve the issue
mentioned above.
From 4274c6ac412b536cda4e909e65563a71c09c5248 Mon Sep 17 00:00:00 2001
From: James Valleroy 
Date: Sat, 25 Feb 2017 14:45:49 -0500
Subject: [PATCH 4/4] Use awk to read config in config script

---
 debian/radicale.config | 25 -
 1 file changed, 12 insertions(+), 13 deletions(-)

diff --git a/debian/radicale.config b/debian/radicale.config
index 4699cff..e95f84e 100644
--- a/debian/radicale.config
+++ b/debian/radicale.config
@@ -6,23 +6,22 @@ CONF=/etc/radicale/config
 
 . /usr/share/debconf/confmodule
 
-aug_get () {
-cat <

signature.asc
Description: OpenPGP digital signature

Bug#855705: [munin-monitoring/munin] munin-cgi-graph CGI::param security problem (#721)

[Salvatore Bonaccorso]

Hi Holger,

On Sat, Feb 25, 2017 at 07:29:47PM +, Holger Levsen wrote:
> On Sat, Feb 25, 2017 at 07:49:13PM +0100, Salvatore Bonaccorso wrote:
> > Yes, I will (and have already prepared the package), but need to
> > release the DSA yet.
> 
> uhm, why not? I dont understand…

Well, basically because I was not sitting the whole time in front of
my laptop ;-)

It is out now as DSA-3794-1.

> +when do you plan to release the DSA? The DLA already has been released.

Done.

> (and for sid I'm waiting for a 2.0.31 tarball… the git tag is there…)

Cool thanks for working on 2.0.31-1!

> > Btw, can you import the dsc in a debian-jessie branch in git once
> > released?
> 
> sure
> 
>  I tried to build from git, but apparently there was a change
> > not represented, and I could not build from git a proper package with
> > a clean debdiff as I have taking the source package from the archive
> > and applying my changes. Not sure if I used the packaging layout
> > wrong.
> 
> I think it's just the RELEASE file which needs to be removed from git there.
> (It's gone from master…)

Yes exactly, it was about the RELEASE file indeed.

> > So if you can just import the dsc once released, and have a
> > look that would be awesome! It is most-likey just me doing something
> > wrong with the packaging repo.
> 
> will do, please ping me once you uploaded in case I'll forget.

*ping*. Thanks a lot for handling it.

Regards,
Salvatore

Bug#856148: unblock: ntfs-3g/1:2016.2.22AR.1+dfsg.1-0.1

[Steven Chamberlain]

Hello,

I ran diffoscope on the generated binary packages.  There is some noise
in the diff due to embedded build paths and varying build IDs, but
otherwise, the only difference is the contents of
const unsigned char boot_array[4136] in the .rodata section of
sbin/mkntfs

i.e.: Jan's proposed upload changes only the thing we expected it to.
But this in turn means that filesystems created by mkntfs will have
a placeholder instead of the first-stage loader of Windows.

László Böszörményi wrote:
> Can I ask if you tried to reach its maintainer first, before asking
> for unblocking a not even uploaded NMU?

Jan is at the Berlin BSP along with several DDs.  Normally a fixed
version would have been uploaded to DELAYED/10 allowing time for the
maintainer to pre-empt with another upload.

But - there would be no point uploading something to DELAYED if the
release time would not approve an unblock.  I think that is why this was
filed - intended as a request for comments about a speculative upload to
DELAYED/10.  You could follow-up with your own debdiff if you plan to
make your own upload for this?

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Bug#856004: khtml: please build-depen on libssl1.0-dev for Stretch

[Sebastian Andrzej Siewior]

On 2017-02-25 12:29:31 [-0300], Lisandro Damián Nicanor Pérez Meyer wrote:
> I think the issue here is if it will work or not at runtime. 

that is what I assume, correct.

> Sebastian: have you seen it crash due to this?

No. I assume that it might use QT's internal networking which is 1.0 and if
they mix then bad things will happen.
I sure that the following symbols are missing:
 RAND_egd
 NETSCAPE_X509_it
 X509_STORE_CTX_set_chain*
 sk_free*
 sk_num
 sk_pop
 sk_value
 sk_new
 sk_push
 sk_dup
 SSLv23_client_method

The two functions marked * have no error handling if the function is missing.
Not using SSLv23_client_method() means that the the user of this class has to
try again with TLSv1_client_method() member which will only allow a TLS1.0
handshake. This is not what you want because TLS1.0 itself is deprecated and
the v23 method would allow the maximum possible TLS level (which is currently
1.2).
For those reasons I think it is wise to migrate to libssl1.0-dev.

Sebastian

Bug#856169: Chromium installs a setuid binary without obvious need nor warning

[Alain Knaff]

Package: chromium
Version: 56.0.2924.76-1~deb8u1

Chromium's .deb install a suid root binary
(/usr/lib/chromium/chrome-sandbox), potentially exposing the user's
system to hostile javascripts downloaded from the untrusted web.

This has already been exploited in the past:

https://bugs.chromium.org/p/chromium/issues/detail?id=76542

Debian packages should not expose users' systems to these kinds of risks
without informed consent.

Alain

Bug#856146: broken: missing dependencies

[Herbert Fortes]

Hi Antonio Terceiro,

> Package: webcamoid
> Version: 7.2.1+dfsg1-4
> Severity: grave
> Justification: renders package unusable
> 
> When I try to start webcamoid, nothing happens. Running it from a
> terminal, I get this:
> 
> $ webcamoid
> QQmlApplicationEngine failed to load component
> qrc:/Webcamoid/share/qml/main.qml:252 Type MediaBar unavailable
> qrc:/Webcamoid/share/qml/MediaBar.qml:138 Type AddMedia unavailable
> qrc:/Webcamoid/share/qml/AddMedia.qml:148 Type FileDialog unavailable
> qrc:/QtQuick/Dialogs/DefaultFileDialog.qml:48 module "Qt.labs.settings" is 
> not installed
> qrc:/QtQuick/Dialogs/DefaultFileDialog.qml:47 module 
> "Qt.labs.folderlistmodel" is not installed
> qrc:/QtQuick/Dialogs/DefaultFileDialog.qml:48 module "Qt.labs.settings" is 
> not installed
> qrc:/QtQuick/Dialogs/DefaultFileDialog.qml:47 module 
> "Qt.labs.folderlistmodel" is not installed
> 
> Installing qml-module-qt-labs-folderlistmodel and qml-module-qt-labs-settings
> makes it work.
> 

I will fix the package tomorrow morning.

Thanks for your time!



Regards,
Herbert

Bug#856168: apt-listchanges: Offer option to sort by name

[Nelson A. de Oliveira]

Package: apt-listchanges
Version: 3.9
Severity: wishlist

Hi!

apt-listchange's manpage says:

The groups are sorted by the urgency of the most urgent change, and
than by the package name. Changes within each package group are
displayed in the order of their apperance in the changelog files,
i.e. starting from the latest to the oldest; the --reverse option
can be used to alter this order.

But could we have an option to display the entries based on a sorted
list of the package names only, please? ie, urgency or other parameter
wouldn't matter here.

Thank you!

Best regards,
Nelson

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

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

Versions of packages apt-listchanges depends on:
ii  apt1.4~rc2
ii  debconf [debconf-2.0]  1.5.60
ii  debianutils4.8.1
ii  python3-apt1.4.0~beta2
pn  python3:any
ii  ucf3.0036

apt-listchanges recommends no packages.

Versions of packages apt-listchanges suggests:
ii  chromium [www-browser]   56.0.2924.76-4
ii  dma [mail-transport-agent]   0.11-1+b1
ii  firefox [www-browser]52.0~b8-1
ii  google-chrome-stable [www-browser]   56.0.2924.87-1
ii  opera [www-browser]  12.16.1860
ii  python3-gi   3.22.0-2
ii  rxvt-unicode-256color [x-terminal-emulator]  9.22-1+b1
ii  w3m [www-browser]0.5.3-34

-- debconf-show failed

Bug#856135: gegl FTBFS on arm64: gegl-tester segfault

[John Paul Adrian Glaubitz]

On 02/25/2017 08:52 PM, John Paul Adrian Glaubitz wrote:
> The backtrace indicates it's an issue in glibc instead of gegl/babl:

glib*, of course. Without the c ;).

-- 
 .''`.  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

Bug#856167: apt-listchanges: Offer option to filter binNMU/binary-only entries

[Nelson A. de Oliveira]

Package: apt-listchanges
Version: 3.9
Severity: wishlist

Hi!

Could we have an option to filter binNMUs/binary-only changelog entries
(with "binary-only=yes" in their header) when using "which" with
"changelogs" or "both", please?

Most of the time it's uninteresting to see a lot of entries saying
"* Binary-only non-maintainer upload for amd64; no source changes."

Thank you!

Best regards,
Nelson

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

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

Versions of packages apt-listchanges depends on:
ii  apt1.4~rc2
ii  debconf [debconf-2.0]  1.5.60
ii  debianutils4.8.1
ii  python3-apt1.4.0~beta2
pn  python3:any
ii  ucf3.0036

apt-listchanges recommends no packages.

Versions of packages apt-listchanges suggests:
ii  chromium [www-browser]   56.0.2924.76-4
ii  dma [mail-transport-agent]   0.11-1+b1
ii  firefox [www-browser]52.0~b8-1
ii  google-chrome-stable [www-browser]   56.0.2924.87-1
ii  opera [www-browser]  12.16.1860
ii  python3-gi   3.22.0-2
ii  rxvt-unicode-256color [x-terminal-emulator]  9.22-1+b1
ii  w3m [www-browser]0.5.3-34

-- debconf-show failed

Bug#855451: inn2: FTBFS: objdump: passwd/auth_krb5': No such file

[Florian Schlichting]

Control: tags -1 +patch

Hi, Berlin BSP here.

inn2-lfs is a transitional package now and no longer being built, so the
offending file will never be there and can simply be dropped from the
dh_shlibdeps call. The following patch fixes the build for me:

--- a/debian/rules
+++ b/debian/rules
@@ -195,7 +195,6 @@ install5: $(addprefix install4-, $(FLAVORS))
dh_md5sums
dh_shlibdeps --exclude=/usr/lib/news/bin/auth/passwd/auth_krb5 -- \
-dSuggests $(D-std)/usr/lib/news/bin/auth/passwd/auth_krb5 \
-  $(D-lfs)/usr/lib/news/bin/auth/passwd/auth_krb5 \
-dDepends
 
dh_gencontrol $(no_package) -- \

Florian

Bug#856166: Update control/rules in pqiv 2.8 package: Support all backends, update description

[Phillip Berndt]

Package: pqiv
Version: 2.6-1

I did just release pqiv 2.8. Instead of just bumping the version and
reusing the same package template, please consider using the attached
control and rules files.

pqiv has, and has had for some versions now, support for using
ImageMagick, libav/ffmpeg, Poppler, Spectre and libarchive to support
more file formats. It is possible to compile the additional backends
into shared libraries that are pulled in at runtime with silent
failure, allowing to build against all backends, but declare the
runtime dependencies as optional. It would be great to include the
backends in the package. My proposed changes to the package would make
use of this feature on Linux, and fall back to compiling a single
binary with hard dependencies on any other platform.

The other proposed change is an update in the short and long
description, also contained in the attached control file. I changed
the homepage to the github page as well, as I update it much more
frequently.

Feel free to reuse only parts of my proposed changes.


control
Description: Binary data


rules
Description: Binary data

Bug#856135: gegl FTBFS on arm64: gegl-tester segfault

[John Paul Adrian Glaubitz]

Hi!

On 02/25/2017 05:45 PM, John Paul Adrian Glaubitz wrote:
> The testsuite in gegl fails at the same point on sparc64 as well, but with
> a bus error. When investigating the issue with gdb, I could track down this
> issue as a bug in babl. I therefore reassigned my bug report accordingly [1].

The backtrace indicates it's an issue in glibc instead of gegl/babl:

(gdb) set environment GEGL_SWAP RAM
(gdb) set environment GEGL_PATH ../operations
(gdb) run --all -o images/examples -d ./images -e
"load|buffer-source|pixbuf|nop|clone|convert-format|introspect|layer|image-compare|load|open-buffer|svg-load|exr-load|jpg-load|png-load|magick-load|box-blur|stretch-contrast|remap|matting-global|exp-combine|dropshadow|kuwahara|box-percentile|disc-percentile|snn-percentile|line-profile|buffer-cache|warp|mandelbrot|hstack"
Starting program:  --all -o images/examples -d ./images -e
"load|buffer-source|pixbuf|nop|clone|convert-format|introspect|layer|image-compare|load|open-buffer|svg-load|exr-load|jpg-load|png-load|magick-load|box-blur|stretch-contrast|remap|matting-global|exp-combine|dropshadow|kuwahara|box-percentile|disc-percentile|snn-percentile|line-profile|buffer-cache|warp|mandelbrot|hstack"
No executable file specified.
Use the "file" or "exec-file" command.
(gdb) file ../tools/.libs/gegl-tester
Reading symbols from ../tools/.libs/gegl-tester...done.
(gdb) run --all -o images/examples -d ./images -e
"load|buffer-source|pixbuf|nop|clone|convert-format|introspect|layer|image-compare|load|open-buffer|svg-load|exr-load|jpg-load|png-load|magick-load|box-blur|stretch-contrast|remap|matting-global|exp-combine|dropshadow|kuwahara|box-percentile|disc-percentile|snn-percentile|line-profile|buffer-cache|warp|mandelbrot|hstack"
Starting program: /home/glaubitz/gegl/gegl-0.3.8/tools/.libs/gegl-tester --all 
-o images/examples -d ./images -e
"load|buffer-source|pixbuf|nop|clone|convert-format|introspect|layer|image-compare|load|open-buffer|svg-load|exr-load|jpg-load|png-load|magick-load|box-blur|stretch-contrast|remap|matting-global|exp-combine|dropshadow|kuwahara|box-percentile|disc-percentile|snn-percentile|line-profile|buffer-cache|warp|mandelbrot|hstack"
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
gegl:cast-format

Program received signal SIGSEGV, Segmentation fault.
0x007fb7e4dc40 in g_utf8_validate () from 
/lib/aarch64-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0  0x007fb7e4dc40 in g_utf8_validate () from 
/lib/aarch64-linux-gnu/libglib-2.0.so.0
#1  0x007fb7dfc260 in g_filename_display_name () from 
/lib/aarch64-linux-gnu/libglib-2.0.so.0
#2  0x007fb54f3de8 in do_setup (operation=operation@entry=0x556829ce00, 
path=0x5568753da0 "./images/standard-input.png", uri=0x55686e8ed0 "") at 
load.c:124
#3  0x007fb54f42ec in attach (operation=0x556829ce00) at load.c:235
#4  0x007fb7f90638 in gegl_node_set_operation_object 
(self=self@entry=0x5568568050, operation=operation@entry=0x556829ce00) at 
gegl-node.c:1269
#5  0x007fb7f9097c in gegl_node_set_op_class (node=0x5568568050, 
op_class=, first_property=, var_args=...) at 
gegl-node.c:1166
#6  0x007fb7f90de8 in gegl_node_set_valist (self=self@entry=0x5568568050, 
first_property_name=first_property_name@entry=0x556818c5f8 "operation",
var_args=...) at gegl-node.c:1361
#7  0x007fb7f910d4 in gegl_node_new_child (parent=0x55682a5050, 
first_property_name=0x556818c5f8 "operation") at gegl-node.c:2051
#8  0x00556818c26c in standard_output (op_name=) at 
gegl-tester.c:184
#9  process_operations (type=) at gegl-tester.c:318
#10 0x00556818bcb4 in process_operations (type=) at 
gegl-tester.c:321
#11 0x00556818b8e8 in main (argc=, argv=) at 
gegl-tester.c:368
(gdb)

Cheers,
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

Bug#855841: xserver-xorg-video-nouveau: X crashes on resume with GForce-320M and nouveau

[Sven Joachim]

On 2017-02-22 12:34 +0100, Xavier Guimard wrote:

> using Debian testing with a MacBook-Air, X crashes since a few months
> (no problem before) after resume, using Cinnamon or KDE. It doesn't
> happend always but often (70%). You will find below both Xorg.1.log
> (last crash) and Xorg.0.log (after reboot).

That's most likely a kernel problem.  Can you please send the output of
the "dmesg" command after such a failure?  You have to run dmesg as root
for that.

Cheers,
   Sven

Bug#818705: general: multipackage issue

[Lee Garrett]

Hi Richard,

please ask for support in the Debian IRC channel, which you can reach at
#debian on irc.oftc.net. Or the debian-user mailinglist, which is found at
https://lists.debian.org/debian-user/. There we'll be able to further debug
your issue. See you there!

Greetings,
Lee

Bug#856165: ITP: pupnp-1.8 -- Portable SDK for UPnP Devices, version 1.8

[James Cowgill]

Package: wnpp
Severity: wishlist
Owner: James Cowgill 
X-Debbugs-Cc: debian-de...@lists.debian.org, n...@leverton.org

* Package name: pupnp-1.8
  Version : 1.8.0
  Upstream Author : Intel Corporation, Marcelo Roberto Jimenez
* URL : http://pupnp.sourceforge.net/
* License : BSD
  Programming Lang: C
  Description : Portable SDK for UPnP Devices, version 1.8

 The Portable SDK for UPnP Devices (libupnp) provides developers with an
 API and open source code for building control points, devices, and
 bridges that are compliant with Version 1.0 of the Universal Plug and
 Play Device Architecture Specification - see http://www.upnp.org/ for
 specifications.

Version 1.8 has been a work in progress for many years and makes a
number of API changes compared to version 1.6. It's designed to be
co-installable with libupnp 1.6. Upstream are planning to continue
maintaining the 1.6 branch since it's much more widely used. It's
currently only available on GitHub:
https://github.com/mrjimenez/pupnp

pupnp-1.8 is needed for packaging the active fork of mediatomb which I'm
having a look into. This fork solves the current issues facing the
mediatomb package which bundles a heavily patched version of libupnp
containing a number of security issues.

I'm CCing the maintainer for libupnp, although I have a strong feeling
he is MIA.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#854058: Bug is in the Ruby server

[Hilko Bengen]

control: tag -1 patch

After running (elserv-start) and switching to the *elserv*8000 buffer
that is used for interaction with the elservd process, I see:

,
| /usr/lib/elserv/elservd:176:in `': uninitialized constant TCPserver 
(NameError)
| Did you mean?  TCPServer
`

So, at some point somebody in Ruby must have decided to rename TCPserver
to TCPServer. Changing the case of one letter fixes the issue, see below.

The last known home for elserv is  and
it seems pretty dead. I think that the package should not be released
with stretch, so I am not doing an NMU.

Cheers,
-Hilko
index 0ae8505..fb01be9
--- a/elservd.in
+++ b/elservd.in
@@ -137,7 +137,7 @@ end
 
 ## Emacs thread
 Thread.start() do
-  emacs_daemon = TCPserver.open("localhost", 0)
+  emacs_daemon = TCPServer.open("localhost", 0)
   ## Greeting.
   STDOUT.print "elserv-port: ", emacs_daemon.addr[1], CRLF, CRLF
   while TRUE
@@ -173,7 +173,7 @@ session_count = 0
 m = Mutex.new
 
 ## MAIN thread
-gs = TCPserver.open(ARGV[0])
+gs = TCPServer.open(ARGV[0])
 while TRUE
   s = gs.accept
   ## end of MAIN thread

Bug#855705: [munin-monitoring/munin] munin-cgi-graph CGI::param security problem (#721)

[Holger Levsen]

On Sat, Feb 25, 2017 at 07:49:13PM +0100, Salvatore Bonaccorso wrote:
> Yes, I will (and have already prepared the package), but need to
> release the DSA yet.

uhm, why not? I dont understand…

+when do you plan to release the DSA? The DLA already has been released.

(and for sid I'm waiting for a 2.0.31 tarball… the git tag is there…)
 
> Btw, can you import the dsc in a debian-jessie branch in git once
> released?

sure

 I tried to build from git, but apparently there was a change
> not represented, and I could not build from git a proper package with
> a clean debdiff as I have taking the source package from the archive
> and applying my changes. Not sure if I used the packaging layout
> wrong.

I think it's just the RELEASE file which needs to be removed from git there.
(It's gone from master…)

> So if you can just import the dsc once released, and have a
> look that would be awesome! It is most-likey just me doing something
> wrong with the packaging repo.

will do, please ping me once you uploaded in case I'll forget.

-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#856164: linux-image-4.9.0-1-amd64: system doesn't resume from suspend

[Fede]

Package: src:linux
Version: 4.9.6-3
Severity: important

Dear Maintainer,

I have a Dell XPS 15 9550.  I first installed Debian Stretch mid January and
after installation I could suspend and resume my laptop by closing the lid.
Since the recent kernel update the laptop doesn't resume from suspend.  Instead
it just reboots.

Fede



-- Package-specific info:
** Version:
Linux version 4.9.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3 (2017-01-28)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-amd64 
root=UUID=bdc80303-1925-45c8-8799-9cb8631fac70 ro quiet

** Not tainted

** Kernel log:
[2.636763] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 1a56:1535
[2.636765] ath10k_pci :02:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 
0 testmode 0
[2.637213] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
[2.702259] ath10k_pci :02:00.0: firmware: direct-loading firmware 
ath10k/QCA6174/hw3.0/board-2.bin
[2.702486] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
6fc88fe7
[2.725022] random: crng init done
[2.781523] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[2.781524] Bluetooth: BNEP filters: protocol multicast
[2.781526] Bluetooth: BNEP socket layer initialized
[3.332255] input: DLL06E4:01 06CB:7A13 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-17/i2c-DLL06E4:01/0018:06CB:7A13.0001/input/input10
[3.332633] hid-multitouch 0018:06CB:7A13.0001: input,hidraw0: I2C HID v1.00 
Mouse [DLL06E4:01 06CB:7A13] on i2c-DLL06E4:01
[3.413891] clocksource: Switched to clocksource tsc
[3.754070] vga_switcheroo: enabled
[3.754173] [TTM] Zone  kernel: Available graphics memory: 8128558 kiB
[3.754173] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[3.754173] [TTM] Initializing pool allocator
[3.754176] [TTM] Initializing DMA pool allocator
[3.754207] nouveau :01:00.0: DRM: VRAM: 2048 MiB
[3.754208] nouveau :01:00.0: DRM: GART: 1048576 MiB
[3.754210] nouveau :01:00.0: DRM: Pointer to TMDS table invalid
[3.754213] nouveau :01:00.0: DRM: DCB version 4.0
[3.754214] nouveau :01:00.0: DRM: Pointer to flat panel table invalid
[3.786167] [drm] RC6 on
[4.018490] nouveau :01:00.0: DRM: MM: using COPY for buffer copies
[4.018494] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on 
minor 1
[4.020645] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[4.021611] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
[4.021674] ACPI: Video Device [PEGP] (multi-head: no  rom: yes  post: no)
[4.021699] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0a/LNXVIDEO:01/input/input13
[4.021754] [drm] Initialized i915 1.6.0 20160919 for :00:02.0 on minor 0
[4.021786] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
[4.024807] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[4.024824] fbcon: inteldrmfb (fb0) is primary device
[4.024935] Console: switching to colour frame buffer device 240x67
[4.024939] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[4.052318] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3266: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[4.052319] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[4.052320] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[4.052321] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[4.052321] snd_hda_codec_realtek hdaudioC0D0:inputs:
[4.052323] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x18
[4.052324] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
[4.052324] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[4.057368] intel_rapl: Found RAPL domain package
[4.057370] intel_rapl: Found RAPL domain core
[4.057371] intel_rapl: Found RAPL domain uncore
[4.057373] intel_rapl: Found RAPL domain dram
[4.071077] input: HDA Intel PCH Headphone Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input14
[4.071133] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input15
[4.071182] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input16
[4.071217] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input17
[4.833806] ath10k_pci :02:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp 
max-sta 32 raw 0 hwcrypto 1
[4.913458] ath: EEPROM regdomain: 0x6c
[4.913459] ath: EEPROM indicates we should expect a direct regpair map
[4.913460] ath: Country alpha2 being used: 00
[4.913461] ath: Regpair used: 0x6c

Bug#856163: debmirror: minor typo error

[Yvan Masson]

Package: debmirror
Version: 1:2.26
Severity: minor

Dear maintainer,

There is a small typo error in debmirror script line 845:

...
say("Veriftying checksums.") if $verify_checksums;
...

Best regards,
Yvan

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

Bug#856162: ctpp2 FTBFS on !i386/amd64: missing symbols

[Adrian Bunk]

Source: ctpp2
Version: 2.8.3-19
Severity: serious

https://buildd.debian.org/status/package.php?p=ctpp2&suite=unstable

...
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libctpp2-2v5/DEBIAN/symbols doesn't match 
completely debian/libctpp2-2v5.symbols
--- debian/libctpp2-2v5.symbols (libctpp2-2v5_2.8.3-19+b1_arm64)
+++ dpkg-gensymbolsNQ_FbH   2017-02-25 04:31:35.654638803 +
@@ -192,8 +192,8 @@
  _ZN4CTPP12CTPP2GetText10ReadMODataEPKhi@Base 2.8.3
  
_ZN4CTPP12CTPP2GetText11FindMessageERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_S8_@Base
 2.8.3
  
_ZN4CTPP12CTPP2GetText11SetLanguageERNS_14SyscallFactoryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 2.8.3
- (arch=!amd64 !i386 !ia64 !powerpcspe 
!s390)_ZN4CTPP12CTPP2GetText12CTPP2CatalogD1Ev@Base 2.8.3
- (arch=!amd64 !i386 !ia64 !powerpcspe 
!s390)_ZN4CTPP12CTPP2GetText12CTPP2CatalogD2Ev@Base 2.8.3
+#MISSING: 2.8.3-19+b1# (arch=!amd64 !i386 !ia64 !powerpcspe 
!s390)_ZN4CTPP12CTPP2GetText12CTPP2CatalogD1Ev@Base 2.8.3
+#MISSING: 2.8.3-19+b1# (arch=!amd64 !i386 !ia64 !powerpcspe 
!s390)_ZN4CTPP12CTPP2GetText12CTPP2CatalogD2Ev@Base 2.8.3
  (arch=armel armhf hppa hurd-i386 i386 kfreebsd-i386 mips mipsel powerpc 
x32)_ZN4CTPP12CTPP2GetText12IsLtOrGtExprERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEj@Base
 2.8.3
  (arch=!armel !armhf !hppa !hurd-i386 !i386 !kfreebsd-i386 !mips !mipsel 
!powerpc 
!x32)_ZN4CTPP12CTPP2GetText12IsLtOrGtExprERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEm@Base
 2.8.3
  (arch=armel armhf hppa hurd-i386 i386 kfreebsd-i386 mips mipsel powerpc 
x32)_ZN4CTPP12CTPP2GetText13IsTernaryExprERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEj@Base
 2.8.3
@@ -1273,51 +1273,51 @@
  _ZNK4CTPP9FnVersion7GetNameEv@Base 2.8.3
  _ZNK4CTPP9HashTable3GetEPKcj@Base 2.8.3
  _ZNK4CTPP9HashTable4SizeEv@Base 2.8.3
- (arch=!amd64 
!i386)_ZNSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4CTPP12CTPP2GetText12CTPP2CatalogESt4lessIS5_ESaISt4pairIKS5_S8_EEEixERSC_@Base
 2.8.3
- (arch=!amd64 
!i386)_ZNSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES_IS5_N4CTPP12CTPP2GetText12CTPP2CatalogESt4lessIS5_ESaISt4pairIKS5_S8_EEESA_SaISB_ISC_SF_EEEixERSC_@Base
 2.8.3
+#MISSING: 2.8.3-19+b1# (arch=!amd64 
!i386)_ZNSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4CTPP12CTPP2GetText12CTPP2CatalogESt4lessIS5_ESaISt4pairIKS5_S8_EEEixERSC_@Base
 2.8.3
+#MISSING: 2.8.3-19+b1# (arch=!amd64 
!i386)_ZNSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES_IS5_N4CTPP12CTPP2GetText12CTPP2CatalogESt4lessIS5_ESaISt4pairIKS5_S8_EEESA_SaISB_ISC_SF_EEEixERSC_@Base
 2.8.3
  (optional=templinst|arch=!amd64 !arm64 !armel !armhf !hppa !hurd-i386 !i386 
!kfreebsd-amd64 !kfreebsd-i386 !mips !mipsel !powerpc !ppc64 !ppc64el !s390x 
!x32)_ZNSt3mapISsS_ISsN4CTPP12CTPP2GetText12CTPP2CatalogESt4lessISsESaISt4pairIKSsS2_EEES4_SaIS5_IS6_S9_EEEixERS6_@Base
 2.8.3
  (optional=templinst|arch=ia64 powerpcspe 
s390)_ZNSt3mapISsSsSt4lessISsESaISt4pairIKSsSsEEEixERS3_@Base 2.8.3
  (optional=templinst|arch=ia64 powerpcspe 
s390)_ZNSt3mapISsjSt4lessISsESaISt4pairIKSsjEEEixERS3_@Base 2.8.3
- (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4CTPP12CTPP2GetText12CTPP2CatalogEED1Ev@Base
 2.8.3
- (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4CTPP12CTPP2GetText12CTPP2CatalogEED2Ev@Base
 2.8.3
- (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4CTPP3CDTEED1Ev@Base
 2.8.3
- (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4CTPP3CDTEED2Ev@Base
 2.8.3
- (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_ED1Ev@Base
 2.8.3
- (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_ED2Ev@Base
 2.8.3
- (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt3mapIS5_N4CTPP12CTPP2GetText12CTPP2CatalogESt4lessIS5_ESaIS_IS6_SA_D1Ev@Base
 2.8.3
- (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt3mapIS5_N4CTPP12CTPP2GetText12CTPP2CatalogESt4lessIS5_ESaIS_IS6_SA_D2Ev@Base
 2.8.3
- (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt6vectorIS5_SaIS5_EEED1Ev@Base
 2.8.3
- (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt6vectorIS5_SaIS5_EEED2Ev@Base
 2.8.3
+#MISSING: 2.8.3-19+b1# (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4CTPP12CTPP2GetText12CTPP2CatalogEED1Ev@Base
 2.8.3
+#MISSING: 2.8.3-19+b1# (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4CTPP12CTPP2GetText12CTPP2CatalogEED2Ev@Base
 2.8.3
+#MISSING: 2.8.3-19+b1# (arch=!amd64 
!i386)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4CTPP3CDTEED1Ev@

Bug#829076: general: Random freezes but the mouse can still move

[Lee Garrett]

Hi John,

thank you for coming forward with your problem, but I think a better approach
for resolving your issue is to bring it up on IRC, or use the the debian-user
mailing list to further debug the issue. Then, if your problem is not solved,
but further narrowed down, you can provide better infos and file the bug
against the respective package.

The IRC channel is #debian on irc.oftc.net, and the mailing list you can find
at https://lists.debian.org/debian-user/. See you there!

Greetings,
Lee

Bug#856123: pandoc: Convert markdown to bad docbook for non-ascii titles

[Petter Reinholdtsen]

Control: retitle -1 dblatex: should not reject non-ascii IDs by default

Hi Andreas.

[Andreas Hoenen]
> this looks like a limitation of the dblatex default backend (pdftex).
> Instead using the xetex backend resolves the problem.

This problem as I see it is that dblatex by default is not able to
process valid docbook files.  This is not realy affected by the
possibility of changing the backend.

But using xetex is a valuable workaround, and I'll test and see if it
solve my problem without creating any new ones. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#849132: Some details on the failing test

[Hilko Bengen]

Hi,

I have repeatedly run the failing test after dpkg-buildpackage failed.
So far, I consistently get a failure.

My test machine is an ancient Lenovo T60 with a "Genuine Intel(R) CPU
T2500 @ 2.00GHz" CPU.

,
| >>> profile doesn't match, args: 
/home/bengen/tmp/bsp/google-perftools/.libs/profiler3_unittest 
/tmp/profile_info/p14 vs.  /tmp/profile_info/p15
| >>> Diff:
| 14c14
| <1   0.6%  99.4%   34  21.4% _init
| ---
| >1   0.6%  99.4%   17  10.7% _init
| 15a16
| >0   0.0% 100.0%   17  10.7% 0x
`
,
| >>> profile doesn't match, args: 
/home/bengen/tmp/bsp/google-perftools/.libs/profiler3_unittest 
/tmp/profile_info/p14 vs.  /tmp/profile_info/p15
| >>> Diff:
| 13a14
| >0   0.0% 100.0%   22  14.0% 0x
| 20c21
| <0   0.0% 100.0%   42  26.8% _init
| ---
| >0   0.0% 100.0%   20  12.7% _init
`
,
| >>> profile doesn't match, args: 
/home/bengen/tmp/bsp/google-perftools/.libs/profiler3_unittest 
/tmp/profile_info/p14 vs.  /tmp/profile_info/p15
| >>> Diff:
| 13a14
| >0   0.0% 100.0%   20  12.7% 0x
| 19c20
| <0   0.0% 100.0%   43  27.2% _init
| ---
| >0   0.0% 100.0%   23  14.6% _init
`
,
| >>> profile doesn't match, args: 
/home/bengen/tmp/bsp/google-perftools/.libs/profiler3_unittest 
/tmp/profile_info/p14 vs.  /tmp/profile_info/p15
| >>> Diff:
| 14a15
| >0   0.0% 100.0%   21  13.1% 0x
| 21c22
| <0   0.0% 100.0%   35  21.9% _init
| ---
| >0   0.0% 100.0%   14   8.8% _init
`

NB: The test script outputs the following warning:
,
| >>> WARNING <<<
| This test looks at timing information to determine correctness.
| If your system is loaded, the test may spuriously fail.
| If the test does fail with an 'Actual times' error, try running again.
`

I think that this test should just be disabled (or failures ignored.)

Cheers,
-Hilko

Bug#856161: tuxguitar: outdated homepage field

[Reiner Herrmann]

Source: tuxguitar
Version: 1.2-22

Hi,

the Homepage field for tuxguitar is outdated, which now leads only
to a parking page.
The new homepage is: http://www.tuxguitar.pw/

Regards,
  Reiner


signature.asc
Description: Digital signature

Bug#856156: vim-gtk: launching gvim as root from terminal crashes X server

[James McCoy]

Control: reassign -1 xserver-xorg-core 2:1.19.1-4
Control: affects -1 vim-gtk

Reassigning to xserver-xorg-core.  Vim's gtk2 code hasn't changed
significantly in some time, so it's more likely an issue with the glamor
driver.

On Sat, Feb 25, 2017 at 12:54:21PM -0500, Bruno Dantas wrote:
> Either command in a terminal consistently crashes the X server:
> # gvim foo.txt
> $ gksudo gvim foo.txt
> 
> I upgraded from Jessie to Stretch, which is when the problem started. The 
> error
> message in the text console that appears after the crash is this:
> "glamor_largepixmap.c:1448: glamor_composite_largepixmap_region: Assertion `0'
> failed. xinit: connection to X server lost"
> 
> Interestingly, starting gvim from within the file manager running as root (via
> context menu's "Open with") works fine. Also, these work fine:
> 
> # pluma foo.txt
> $ gksudo pluma foo.txt
> $ gvim foo.txt
> 
> It seems the problem is isolated to launching gvim as root from the command
> line. glamor_largepixmap.c is part of the xorg-server source package. If I
> should report the bug there instead/in addition to here, please let me know. I
> don't want to create noise.
> 
> These are my package versions:
> vim-gtk 2:8.0.0197-2
> xorg 1:7.7+18
> 
> If you need any further information, please let me know. gvim is my favorite
> editor and I'm in a terminal most of the time, so I'm highly motivated to 
> help.

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

Bug#853232: libphp-phpmailer: diff for NMU version 5.2.14+dfsg-2.3

[Markus Koschany]

Control: tags 853232 + patch
Control: tags 853232 + pending

Dear maintainer,

I've prepared an NMU for libphp-phpmailer (versioned as 5.2.14+dfsg-2.3) and
uploaded it to unstable.

Regards,

Markus
diff -Nru libphp-phpmailer-5.2.14+dfsg/debian/changelog libphp-phpmailer-5.2.14+dfsg/debian/changelog
--- libphp-phpmailer-5.2.14+dfsg/debian/changelog	2017-01-02 15:21:27.0 +0100
+++ libphp-phpmailer-5.2.14+dfsg/debian/changelog	2017-02-25 19:15:08.0 +0100
@@ -1,3 +1,14 @@
+libphp-phpmailer (5.2.14+dfsg-2.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix CVE-2017-5223:
+It was discovered that there was a local file disclosure vulnerability in
+libphp-phpmailer, a email transfer class for PHP, where insufficient
+parsing of HTML messages could potentially be used by attacker to read a
+local file. (Closes: #853232)
+
+ -- Markus Koschany   Sat, 25 Feb 2017 19:15:08 +0100
+
 libphp-phpmailer (5.2.14+dfsg-2.2) unstable; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff -Nru libphp-phpmailer-5.2.14+dfsg/debian/patches/0003-CVE-2017-5223.patch libphp-phpmailer-5.2.14+dfsg/debian/patches/0003-CVE-2017-5223.patch
--- libphp-phpmailer-5.2.14+dfsg/debian/patches/0003-CVE-2017-5223.patch	1970-01-01 01:00:00.0 +0100
+++ libphp-phpmailer-5.2.14+dfsg/debian/patches/0003-CVE-2017-5223.patch	2017-02-25 19:15:08.0 +0100
@@ -0,0 +1,92 @@
+From: Markus Koschany 
+Date: Sat, 25 Feb 2017 19:00:40 +0100
+Subject: CVE-2017-5223
+
+It was discovered that there was a local file disclosure vulnerability in
+libphp-phpmailer, a email transfer class for PHP, where insufficient parsing of
+HTML messages could potentially be used by attacker to read a local file.
+
+Bug-Debian: https://bugs.debian.org/853232
+Origin: https://github.com/PHPMailer/PHPMailer/commit/ad4cb09682682da2217799a0c521d4cdc6753402
+---
+ class.phpmailer.php | 30 +++---
+ 1 file changed, 23 insertions(+), 7 deletions(-)
+
+diff --git a/class.phpmailer.php b/class.phpmailer.php
+index 8aa4752..5c43d1b 100644
+--- a/class.phpmailer.php
 b/class.phpmailer.php
+@@ -2418,6 +2418,7 @@ class PHPMailer
+ 
+ /**
+  * Add an attachment from a path on the filesystem.
++ * Never use a user-supplied path to a file!
+  * Returns false if the file could not be found or read.
+  * @param string $path Path to the attachment.
+  * @param string $name Overrides the attachment name.
+@@ -2943,6 +2944,7 @@ class PHPMailer
+  * displayed inline with the message, not just attached for download.
+  * This is used in HTML messages that embed the images
+  * the HTML refers to using the $cid value.
++ * Never use a user-supplied path to a file!
+  * @param string $path Path to the attachment.
+  * @param string $cid Content ID of the attachment; Use this to reference
+  *the content when using an embedded image in HTML.
+@@ -3306,10 +3308,14 @@ class PHPMailer
+  * Create a message from an HTML string.
+  * Automatically makes modifications for inline images and backgrounds
+  * and creates a plain-text version by converting the HTML.
+- * Overwrites any existing values in $this->Body and $this->AltBody
++ * Overwrites any existing values in Body and AltBody
++ * Do not source $message content from user input!
++ * $basedir is prepended when handling relative URLs, e.g.  and must not be empty
++ * If you don't provide a $basedir, relative paths will be left untouched (and thus probably break in email)
++ * If you don't want to apply these transformations to your HTML, just set Body and AltBody directly.
+  * @access public
+  * @param string $message HTML message string
+- * @param string $basedir baseline directory for path
++ * @param string $basedir Absolute path to a base directory to prepend to relative paths to images
+  * @param boolean|callable $advanced Whether to use the internal HTML to text converter
+  *or your own custom converter @see PHPMailer::html2text()
+  * @return string $message
+@@ -3318,6 +3324,10 @@ class PHPMailer
+ {
+ preg_match_all('/(src|background)=["\'](.*)["\']/Ui', $message, $images);
+ if (array_key_exists(2, $images)) {
++if (strlen($basedir) > 1 && substr($basedir, -1) != '/') {
++// Ensure $basedir has a trailing /
++$basedir .= '/';
++}
+ foreach ($images[2] as $imgindex => $url) {
+ // Convert data URIs into embedded images
+ if (preg_match('#^data:(image[^;,]*)(;base64)?,#', $url, $match)) {
+@@ -3335,18 +3345,24 @@ class PHPMailer
+ $message
+ );
+ }
+-} elseif (substr($url, 0, 4) !== 'cid:' && !preg_match('#^[A-z]+://#', $url)) {
+-// Do not change urls for absolute images (thanks to corvusco

Bug#855970: [debian-archive-keyring] The release repository of testing (Stretch), and security updates repository too, have three misiing public keys

[Adam D. Barratt]

On Fri, 2017-02-24 at 10:13 +0100, Łukasz Konieczny wrote:
> Output of the command in attached file. Seems like everything OK. I 
> don't know what happens.
> 
> [I'm sending this again, I have forgotten about the second mail address 
> specific to this bug.]

That looks okay at first glance. (fwiw, you don't need to be root to run
the gpg command).

Please could you also send the output of "ls
-ltr /etc/apt/trusted.gpg.d/" on the affected machine?

Regards,

Adam

Bug#856160: nettle-dev: Please transition nettle-dev to multi-arch

[F. Poirotte]

Package: nettle-dev
Version: 3.3-1
Severity: wishlist

Dear Maintainer,

Please transition nettle-dev to multi-arch so that multiple variants can be 
co-installed (eg. i386 & amd64)

It seems an attempt was already made to make the package multi-arch compatible 
in #783699, which removed the conflicts
stemming from a comment containing compiler information.
However, the GMP_NUMB_BITS preprocessor constant still triggers a conflict when 
trying to co-install the i386 & amd64 packages.

Maybe the constant could be removed/replaced with an error message as initially 
suggested?

Best regards,
François



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

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

Bug#856033: ITP: brailleimg -- produce text images and graphs abusing Braille glyphs

[Samuel Thibault]

Adam Borowski, on sam. 25 févr. 2017 18:24:33 +0100, wrote:
> Alas, it won't work: I see that, while alignment of the graph itself works
> well, anything but terminals (which force a char-cell grid) fails to give
> Braille and ASCII characters the same width, despite requesting fixed-width
> display.

That's not normal: fixed-width fonts should really have fixed-width for
the characters used by gnuplot.

> You can see how bad it is on https://angband.pl/doc/alluni.txt -- you should
> get an aligned grid with right edge of every full block forming an even
> vertical line, yet most blocks fail to align even within themselves.

That's expected: some characters have double-width, others have
zero-width. But for characters that have single-width, they are really
aligned with a proper fixed-width font.

> gnuplot relies on being able to place labels within the image, which works
> for ASCII and maybe Latin/Greek/Cyrillic but, except for most terminals, not
> for anything else.

Then gnuplot is missing taking into account the value returned by
wcwidth() (0, 1, 2, ...), that's the bug.

Samuel

Bug#856159: libidn11-dev: Please transition libidn11-dev to multi-arch

[F. Poirotte]

Package: libidn11-dev
Version: 1.33-1
Severity: wishlist

Dear Maintainer,

Please transition libidn11-dev to multi-ach so that multiple variants of this 
package can be co-installed (eg. amd64 & i386)

Simply adding "Multi-Arch: same" to debian/control for this package seems to do 
the trick and does not trigger any conflict AFAICT.


Best regards,
François

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

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

Bug#856148: unblock: ntfs-3g/1:2016.2.22AR.1+dfsg.1-0.1

[GCS]

Hi Jan Luca,

On Sat, Feb 25, 2017 at 5:35 PM, Jan Luca Naumann
 wrote:
> Please unblock package ntfs-3g
>
> This version fixes the copyright issue described in
> bug #808463. It copy the fixed file boot.c from
> upstream version 2016.2.22AR.2 which contains copyright
> information for the file.
>
> The debdiff between ntfs-3g-2016.2.22AR.1-4 and
> ntfs-3g-2016.2.22AR.1+dfsg.1-0.1 is attached.
 Can I ask if you tried to reach its maintainer first, before asking
for unblocking a not even uploaded NMU?
If the answer is yes, can you please attach that mail to your answer?

Thanks,
Laszlo/GCS

Bug#856158: ITP: g810-led -- LED configuration tool for Logitech G410/G610/G810/G910 keyboards

[Stephen Kitt]

Package: wnpp
Severity: wishlist
Owner: Stephen Kitt 

* Package name: g810-led
  Version : 0.1.0
  Upstream Author : MatMoul
* URL : https://github.com/MatMoul/g810-led
* License : GPL-3
  Programming Lang: C++
  Description : LED configuration tool for Logitech Gx10 keyboards

g810-led is a configuration tool for the LEDs on Logitech Gx10 gaming
keyboards: G410, G610, G810 and G910. The LEDs can be configured in a
variety of ways, depending on the keyboards' capabilities:

 * pre-defined effects (breathing, colour-cycling, waves)
 * individual key colours and/or intensities
 * key group colours and/or intensities

Bug#855705: [munin-monitoring/munin] munin-cgi-graph CGI::param security problem (#721)

[Salvatore Bonaccorso]

Hi Holger,

On Sat, Feb 25, 2017 at 04:36:07PM +, Holger Levsen wrote:
> Salvatore, will you take care of fixing 2.0.25-1 in jessie? Once that is out,
> I can upload that as ~bpo7+1 to wheezy-bpo…

Yes, I will (and have already prepared the package), but need to
release the DSA yet.

Btw, can you import the dsc in a debian-jessie branch in git once
released? I tried to build from git, but apparently there was a change
not represented, and I could not build from git a proper package with
a clean debdiff as I have taking the source package from the archive
and applying my changes. Not sure if I used the packaging layout
wrong. So if you can just import the dsc once released, and have a
look that would be awesome! It is most-likey just me doing something
wrong with the packaging repo.

Regards,
Salvatore

Bug#853232: libphp-phpmailer: diff for NMU version 5.2.14+dfsg-2.3

[Markus Koschany]

Control: tags 853232 + patch
Control: tags 853232 + pending

Dear maintainer,

I've prepared an NMU for libphp-phpmailer (versioned as 5.2.14+dfsg-2.3) and
uploaded it to unstable.

Regards,

Markus
diff -Nru libphp-phpmailer-5.2.14+dfsg/debian/changelog libphp-phpmailer-5.2.14+dfsg/debian/changelog
--- libphp-phpmailer-5.2.14+dfsg/debian/changelog	2017-01-02 15:21:27.0 +0100
+++ libphp-phpmailer-5.2.14+dfsg/debian/changelog	2017-02-25 19:15:08.0 +0100
@@ -1,3 +1,14 @@
+libphp-phpmailer (5.2.14+dfsg-2.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix CVE-2017-5223:
+It was discovered that there was a local file disclosure vulnerability in
+libphp-phpmailer, a email transfer class for PHP, where insufficient
+parsing of HTML messages could potentially be used by attacker to read a
+local file. (Closes: #853232)
+
+ -- Markus Koschany   Sat, 25 Feb 2017 19:15:08 +0100
+
 libphp-phpmailer (5.2.14+dfsg-2.2) unstable; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff -Nru libphp-phpmailer-5.2.14+dfsg/debian/patches/0003-CVE-2017-5223.patch libphp-phpmailer-5.2.14+dfsg/debian/patches/0003-CVE-2017-5223.patch
--- libphp-phpmailer-5.2.14+dfsg/debian/patches/0003-CVE-2017-5223.patch	1970-01-01 01:00:00.0 +0100
+++ libphp-phpmailer-5.2.14+dfsg/debian/patches/0003-CVE-2017-5223.patch	2017-02-25 19:15:08.0 +0100
@@ -0,0 +1,92 @@
+From: Markus Koschany 
+Date: Sat, 25 Feb 2017 19:00:40 +0100
+Subject: CVE-2017-5223
+
+It was discovered that there was a local file disclosure vulnerability in
+libphp-phpmailer, a email transfer class for PHP, where insufficient parsing of
+HTML messages could potentially be used by attacker to read a local file.
+
+Bug-Debian: https://bugs.debian.org/853232
+Origin: https://github.com/PHPMailer/PHPMailer/commit/ad4cb09682682da2217799a0c521d4cdc6753402
+---
+ class.phpmailer.php | 30 +++---
+ 1 file changed, 23 insertions(+), 7 deletions(-)
+
+diff --git a/class.phpmailer.php b/class.phpmailer.php
+index 8aa4752..5c43d1b 100644
+--- a/class.phpmailer.php
 b/class.phpmailer.php
+@@ -2418,6 +2418,7 @@ class PHPMailer
+ 
+ /**
+  * Add an attachment from a path on the filesystem.
++ * Never use a user-supplied path to a file!
+  * Returns false if the file could not be found or read.
+  * @param string $path Path to the attachment.
+  * @param string $name Overrides the attachment name.
+@@ -2943,6 +2944,7 @@ class PHPMailer
+  * displayed inline with the message, not just attached for download.
+  * This is used in HTML messages that embed the images
+  * the HTML refers to using the $cid value.
++ * Never use a user-supplied path to a file!
+  * @param string $path Path to the attachment.
+  * @param string $cid Content ID of the attachment; Use this to reference
+  *the content when using an embedded image in HTML.
+@@ -3306,10 +3308,14 @@ class PHPMailer
+  * Create a message from an HTML string.
+  * Automatically makes modifications for inline images and backgrounds
+  * and creates a plain-text version by converting the HTML.
+- * Overwrites any existing values in $this->Body and $this->AltBody
++ * Overwrites any existing values in Body and AltBody
++ * Do not source $message content from user input!
++ * $basedir is prepended when handling relative URLs, e.g.  and must not be empty
++ * If you don't provide a $basedir, relative paths will be left untouched (and thus probably break in email)
++ * If you don't want to apply these transformations to your HTML, just set Body and AltBody directly.
+  * @access public
+  * @param string $message HTML message string
+- * @param string $basedir baseline directory for path
++ * @param string $basedir Absolute path to a base directory to prepend to relative paths to images
+  * @param boolean|callable $advanced Whether to use the internal HTML to text converter
+  *or your own custom converter @see PHPMailer::html2text()
+  * @return string $message
+@@ -3318,6 +3324,10 @@ class PHPMailer
+ {
+ preg_match_all('/(src|background)=["\'](.*)["\']/Ui', $message, $images);
+ if (array_key_exists(2, $images)) {
++if (strlen($basedir) > 1 && substr($basedir, -1) != '/') {
++// Ensure $basedir has a trailing /
++$basedir .= '/';
++}
+ foreach ($images[2] as $imgindex => $url) {
+ // Convert data URIs into embedded images
+ if (preg_match('#^data:(image[^;,]*)(;base64)?,#', $url, $match)) {
+@@ -3335,18 +3345,24 @@ class PHPMailer
+ $message
+ );
+ }
+-} elseif (substr($url, 0, 4) !== 'cid:' && !preg_match('#^[A-z]+://#', $url)) {
+-// Do not change urls for absolute images (thanks to corvusco

Bug#837581: xfslibs-dev: Don't put the .so symlink to /lib/*.so

[Florian Schlichting]

Hi, Berlin BSP here.

I can't reproduce this bug on amd64. I notice that since the upload of
xfsprogs 4.9.0, xfsdump does not FTBFS any more on amd64. It does
however still FTBFS on i386 and armhf, albeit with a different error:

...
checking xfs/xfs.h usability... no
checking xfs/xfs.h presence... yes
configure: WARNING: xfs/xfs.h: present but cannot be compiled
configure: WARNING: xfs/xfs.h: check for missing prerequisite headers?
configure: WARNING: xfs/xfs.h: see the Autoconf documentation
configure: WARNING: xfs/xfs.h: section "Present But Cannot Be Compiled"
configure: WARNING: xfs/xfs.h: proceeding with the compiler's result
checking for xfs/xfs.h... no

FATAL ERROR: cannot find a valid  header file.
Install or upgrade the XFS development package.
Alternatively, run "make install-dev" from the xfsprogs source.
Makefile:78: recipe for target 'include/builddefs' failed
make[1]: *** [include/builddefs] Error 1
make[1]: Leaving directory '/build/1st/xfsdump-3.1.6+nmu1'
debian/rules:23: recipe for target '.census' failed
...

see 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/xfsdump.html
or 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/xfsdump.html

The relevant test fails with

/usr/include/xfs/xfs.h:53:12: error: size of array 'xfs_assert_largefile' is 
too large
 extern int xfs_assert_largefile[sizeof(off_t)-8];
^~~~

While -D_FILE_OFFSET_BITS=64 is correctly set in include/builddefs.in,
this is not known to configure and thus it fails when testing xfs.h on
32bit systems.

A similar thing seems to have happened to CEPH, see
https://anonscm.debian.org/cgit/pkg-ceph/ceph.git/commit/?h=debian/10.2.5-5&id=f4675da14d1b38f907079e522d9da7a0e23037fb
but I couldn't get that patch to work. for xfsdump. However the
following patch (to xfsdump) seems to fix the FTBFS in my i386 chroot:

--- a/debian/rules
+++ b/debian/rules
@@ -1,6 +1,7 @@
 #!/usr/bin/make -f
 
 export DH_VERBOSE=1
+export LOCAL_CONFIGURE_OPTIONS=CFLAGS=-D_FILE_OFFSET_BITS=64
 
 package=xfsdump

Florian

Bug#854880: Fwd: firmware-atheros ships binary ath9k_htc firmwares containing GPL code

[Jan Luca Naumann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Linux-Firmware-Maintainers,

as reported in the Debian bug report #854880[1] (mail attached below),
the firmware files ath9k_htc/htc_7010-1.4.0.fw,
ath9k_htc/htc_9271-1.4.0.fw has been created using GPL components and
thus the source code has to be included.

Can you please take a look on the issue? IMHO it is the best to fix
this directly in the upstream linux-firmware repository.

Thank you,
Jan

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

On Sat, 11 Feb 2017 15:09:30 +0100 Julian Andres Klode
 wrote:
> The binary files
> 
> Files: ath9k_htc/htc_7010-1.4.0.fw, ath9k_htc/htc_9271-1.4.0.fw
> 
> were created from files that include GPL components according to 
> the copyright file, specially, the eCos files:
> 
> eCos is free software; you can redistribute it and/or modify it
> under the terms of the GNU General Public License as published by
> the Free Software Foundation; either version 2 or (at your option)
> any later version. . As a special exception, if other files
> instantiate templates or use macros or inline functions from this
> file, or you compile this file and link it with other works to
> produce a work based on this file, this file does not by itself
> cause the resulting work to be covered by the GNU General Public 
> License. However the source code for this file must still be made
> available in accordance with section (3) of the GNU General Public
> License. . This exception does not invalidate any other reasons why
> a work based on this file might be covered by the GNU General
> Public License.
> 
> These need to be either added to the package or the firmware needs 
> to be removed from the archive.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEwNbeTg2NJIWRcwSlfhHX8Rn5cbsFAlixzOsACgkQfhHX8Rn5
cbtJ2RAAlpx4cKAO7Quu4hAy6NrmdbC1l29Yq3f5gYlA+wWZFs0TXOaubYy4E5ay
K9JixISdu3jgnZInlwkyFKAXX7L7jta6DowdoMDOKjcXCN9djy1meWfbVGEmqepe
eBOCyxetKIrnx5Sp2Fp/GNwpdRKX913vusmR1iSsYRss8S3YgJ6oAPYpYyc5SyWj
qA/pExt6f59fi7MfAVxMrJsW6eq0gmZiEIjEGMoQfVDZRAe8fJUo5cQI3hukRWLd
zlmVoMgPfTyfoc1GdDICg8sW39+TjWxoYXLwELZkhfaGPo2OUsTyjQeI4a9aP1Hb
WPONEiBMY2OYBr5w2wvFTDNFY9UPMZ46W3qVCGGuTPy8yV46DyD0rhgq7qP3Z2zj
kKq24ONmfjrdFVzj+h7SQWyQKcSfaB3bIKJfB44fSzNCmw35hAVTF+pwDOOB0+p9
/NkQ7KUfczksatMUg9IWvsuZT/nR2MimwyP+wB0U/sxjnNbVNH3m9KBuACbZ2+4M
bCSze7gVdPPa83T9i/pQH+R/nQoVBeb4TT6IWhQHIYasFV+3at2Rb57SCHKvt8E+
E1LjY4CdhCfnFjK5tGrfCtvHrPYHFooDDcArgMpHTjoGLleT9gMx4hP+oI3NViGK
vNbrwnf0eIOtJcPBLG5zVNV+6otuWbiMTxTADPeegs6SAhJ4lPw=
=KS0/
-END PGP SIGNATURE-

Bug#856157: TAG: lsmedia -- List audio/video files with their details

[Narcis Garcia]

Package: wnpp
Severity: ITP
Copyright: GNU GPL (2012-2017) Narcis Garcia
https://git.actiu.net/

Bug#835107: libpthread-workqueue: FTBFS: Testsuite hangs

[Daniel Schepler]

On Sun, Jan 8, 2017 at 11:57 AM, Balint Reczey  wrote:
> The package builds fine for me in sbuild. The issue may be specific to
> pbuilder/local configuration or is gone.
>
> Is the build still failing for you?

I just tried it 10 times in a row, and it failed 2 of those times.
-- 
Daniel Schepler

Bug#851060: New dsniff revision

[James Cowgill]

Hi,

On 23/02/17 22:44, Marcos Fouces wrote:
> El 23/02/17 a las 12:57, James Cowgill escribió:
>> Hi,
>>
>> On 22/02/17 23:16, Marcos Fouces wrote:
>>> Hello
>>>
>>> I uploaded to repo a first attempt of libnids1.24 package wich aims to
>>> close its two critical bugs:
>>>
>>> #855602: fixed upstream in 1.24 release.
>> As I wrote in the bugreport, the fix applied by upstream is not enough
>> to fix this. You also need to apply the patch from Fedora otherwise
>> dsniff will FTBFS on i386.
> 
> I applied the patch you mentioned and after a rebuild of dsniff and
> libnids, it still seems to work properly at least on amd64
> 
> Please, check it:
> 
> https://anonscm.debian.org/cgit/pkg-security/libnids.git

I've only looked at the things you've done so far. I think in addition
you should also:
- Rewrite the rules file.
- Add a symbols file since this is a C library.
- Install the library in the multi-arch lib directory.
- Move the stuff in "debian-changes-1.23-2" into a proper patch file.

debian/control:
> | -Build-Depends: libpcap0.8-dev, libnet1-dev (>= 1.1.2.1), debhelper (>= 5), 
> autotools-dev, pkg-config, libglib2.0-dev
> | +Build-Depends: libpcap0.8-dev, libnet1-dev (>= 1.1.2.1), debhelper (>= 
> 10), autotools-dev, pkg-config, libglib2.0-dev

debhelper (>= 10) implies autotools-dev so you can remove that
dependency. It may be a good idea to sort them as well.

> | -Package: libnids1.21
> | +Package: libnids1.24

This appears to be a case of upstream not knowing how to correctly
version their ABI (there are no ABI changes in 1.24) though as there are
only 2 reverse dependencies you can probably get away with it. This
package will need to go via experimental to handle the transition.

> |  Architecture: any
> |  Depends: ${shlibs:Depends}, ${misc:Depends}
> |  Conflicts: libnids1 
> | -Replaces: libnids0, libnids1 
> | +Replaces: libnids0, libnids1, libnids1.21

libnids1.24 contains no files which would conflict with any of these
packages, so just remove the Conflicts and Replaces lines here.

> | @@ -22,11 +20,10 @@ Description: IP defragmentation TCP segment reassembly 
> library (development)
> |   modules.
> |   Libnids performs assembly of TCP segments into TCP streams, IP 
> |   defragmentation, and TCP port scan detection.
> | + This is the development package.
> |   .
> |  

Usually that line goes below the dot. There's also some trailing
whitespace which you could remove.

Both the debian/*.dirs files are useless. You can remove them.

>> For stretch, the fixes need to be targeted so as to only change as much
>> stuff as necessary to fix the two RC bugs.
> 
> I am agree with you, when i fix these bugs i will create a separate git
> branch, cherry-pick only freeze-allowed changes and try to get a package
> ready for stretch.

Ok. Since I can now get dsniff working, I will happily NMU this unless
you want to do it.

> This is the default behaviour of gbp when creating a repo. In
> pkg-security team we don't use it but you can see it in some packages.
> Anyway, i deleted it. :-)

I don't think gbp creates a debian/master branch by default.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#856156: vim-gtk: launching gvim as root from terminal crashes X server

[Bruno Dantas]

Package: vim-gtk
Version: 2:8.0.0197-2
Severity: important

Dear Maintainer,

Either command in a terminal consistently crashes the X server:
# gvim foo.txt
$ gksudo gvim foo.txt

I upgraded from Jessie to Stretch, which is when the problem started. The error
message in the text console that appears after the crash is this:
"glamor_largepixmap.c:1448: glamor_composite_largepixmap_region: Assertion `0'
failed. xinit: connection to X server lost"

Interestingly, starting gvim from within the file manager running as root (via
context menu's "Open with") works fine. Also, these work fine:

# pluma foo.txt
$ gksudo pluma foo.txt
$ gvim foo.txt

It seems the problem is isolated to launching gvim as root from the command
line. glamor_largepixmap.c is part of the xorg-server source package. If I
should report the bug there instead/in addition to here, please let me know. I
don't want to create noise.

These are my package versions:
vim-gtk 2:8.0.0197-2
xorg 1:7.7+18

If you need any further information, please let me know. gvim is my favorite
editor and I'm in a terminal most of the time, so I'm highly motivated to help.

Thanks.



-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.tiny
/usr/bin/vim is /usr/bin/vim.gtk
/usr/bin/gvim is /usr/bin/vim.gtk

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

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

Versions of packages vim-gtk depends on:
ii  libacl1 2.2.52-3+b1
ii  libc6   2.24-9
ii  libgdk-pixbuf2.0-0  2.36.4-1
ii  libglib2.0-02.50.2-2
ii  libgpm2 1.20.4-6.2
ii  libgtk2.0-0 2.24.31-2
ii  libice6 2:1.0.9-1+b1
ii  liblua5.2-0 5.2.4-1.1+b1
ii  libpango-1.0-0  1.40.3-3
ii  libperl5.24 5.24.1-1
ii  libpython3.53.5.3-1
ii  libruby2.3  2.3.3-1
ii  libselinux1 2.6-3
ii  libsm6  2:1.2.2-1+b1
ii  libtcl8.6   8.6.6+dfsg-1
ii  libtinfo5   6.0+20161126-1
ii  libx11-62:1.6.4-3
ii  libxt6  1:1.1.5-1
ii  vim-common  2:8.0.0197-2
ii  vim-gui-common  2:8.0.0197-2
ii  vim-runtime 2:8.0.0197-2

vim-gtk recommends no packages.

Versions of packages vim-gtk suggests:
pn  cscope
ii  fonts-dejavu  2.37-1
ii  gnome-icon-theme  3.12.0-2
pn  vim-doc   

-- no debconf information

Bug#855251: [easytag] No clicks, but broken files

[Samuele Battarra]

In data giovedì 23 febbraio 2017 11:20:44 CET, hai scritto:
> Control: tags -1 - moreinfo
> Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=776110
> 
> Since the original submitter hasn't replied, I'll assume this bug is the
> same as the upstream bug (like above).
> 
> Thanks,
> James

Yes, it's the same bug.

-- 
Samuele Battarra
batta...@email.it

Bug#854699: Shutdown fails with an encrypted filesystem on virtio device

[Yuri D'Elia]

On Sat, Feb 11 2017, Michael Biebl wrote:
>> I cannot explain why given the exact same partition/volume scheme by
>> lvm/cryptsetup, in one case I can shutdown cleanly, and in the other it
>> breaks.
>
> While I can reproduce the error messages on shutdown, it does *not*
> cause a dirty file system (in particular /var) here.
> I do have persistent journal enabled on the test VM, but the filing
> killing/unmount spree in systemd-shutdown properly unmounts /var.

I reinstalled a lenovo yoga x1 with the latest amd64 daily debian
netinst image yesterday. Minimal install (empty tasksel). Again, I've
just followed the guided "lvm + full disk encryption" with an ext4 root
(default settings) and grub on the mbr ("legacy" boot - not even uefi).

I ended up with the same issue. At the first shutdown triggered by C-A-D
(without even logging in), I noticed the block device error, followed by
a dirty fs on the next reboot.

This is completely unrelated to virtio.

Bug#856155: Turn hardening-no-pie into a warning and improve the description

[Adrian Bunk]

Package: lintian
Version: 2.5.50.1
Severity: normal
Tags: patch

The attached patch turns hardening-no-pie into a warning and
improves the description.

This should help to reduce the number of cases where PIE is
accidentally disabled (most notably hardening=+all,-pie).
>From b2f0146901669b7b2e3e911a4805213a1ae26174 Mon Sep 17 00:00:00 2001
From: Adrian Bunk 
Date: Sat, 25 Feb 2017 19:31:28 +0200
Subject: Turn hardening-no-pie into a warning and improve the description

---
 checks/binaries.desc | 23 +++
 1 file changed, 7 insertions(+), 16 deletions(-)

diff --git a/checks/binaries.desc b/checks/binaries.desc
index c3f9d8563..8a43d1891 100644
--- a/checks/binaries.desc
+++ b/checks/binaries.desc
@@ -394,34 +394,25 @@ Info: This package provides an ELF binary that lacks the 
"bindnow"
 Ref: https://wiki.debian.org/Hardening
 
 Tag: hardening-no-pie
-Severity: wishlist
+Severity: normal
 Certainty: certain
 Info: This package provides an ELF executable that was not compiled
  as a position independent executable (PIE).
  .
- In Debian, gcc-6 as of version 6.2.0-9 will compile ELF binaries with
- PIE by default.  In most cases a simple rebuild will be sufficient to
- remove this tag.
+ In Debian, since version 6.2.0-7 of the gcc-6 package GCC will
+ compile ELF binaries with PIE by default.  In most cases a simple
+ rebuild will be sufficient to remove this tag.
  .
  PIE is required for fully enabling Address Space Layout
  Randomization (ASLR), which makes "Return-oriented" attacks more
  difficult.
  .
  Historically, PIE has been associated with noticeable performance
- overhead on i386.  However, GCC-5 has implemented an optimization
+ overhead on i386.  However, GCC >= 5 has implemented an optimization
  that can reduce the overhead significantly.
  .
- If you use dpkg-buildflags, you may have to add
- hardening=+pie or hardening=+all to
- DEB_BUILD_MAINT_OPTIONS.
- .
- The relevant compiler flags must be passed both to the compiler
- and the linker (e.g. for C that would be commonly be
- CFLAGS and LDFLAGS).
- .
- If your upstream build compiles either of the above, you may have to
- patch the build to ensure that only ELF executables are compiled with
- PIE.
+ If you use dpkg-buildflags with hardening=+all,-pie
+ in DEB_BUILD_MAINT_OPTIONS, remove the -pie.
 Ref: https://wiki.debian.org/Hardening,
  https://gcc.gnu.org/gcc-5/changes.html,
  
https://software.intel.com/en-us/blogs/2014/12/26/new-optimizations-for-x86-in-upcoming-gcc-50-32bit-pic-mode
-- 
2.11.0

Bug#856152: python-apt: FTBFS: Testsuite failure

[Daniel Schepler]

On Sat, Feb 25, 2017 at 8:59 AM, Julian Andres Klode  wrote:
> Retry it. Maybe it timed out or something.
I just retried it 5 times, and got 5 more failures.
-- 
Daniel Schepler

Bug#856149: docker.io: Purge fails due to bashism in /var/lib/docker/nuke-graph-directory.sh

[Tianon Gravi]

On 25 February 2017 at 08:40, Bruce Weirdan  wrote:
> I tried to purge docker.io package because I no longer needed it, and
> the purge failed:
>
> /var/lib/docker/nuke-graph-directory.sh: 64: 
> /var/lib/docker/nuke-graph-directory.sh: shopt: not found
> dpkg: error processing package docker.io (--purge):
>  subprocess installed post-removal script returned error exit status 127
>
> Obviously dash has no 'shopt'

Aww, this was fixed upstream in
https://github.com/docker/docker/pull/30519 (reported in
https://github.com/docker/docker/issues/30517), but didn't make it for
the 1.13 release.  Probably worth backporting that patch! <3

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#856033: ITP: brailleimg -- produce text images and graphs abusing Braille glyphs

[Adam Borowski]

Control: retitle -1 ITP: braillegraph -- simple histogram tool producing text 
dot-matrix graphs

On Sat, Feb 25, 2017 at 02:46:57PM +0100, Samuel Thibault wrote:
> Indeed, apparently I forgot to add documentation. I have submitted
> patch, thanks.

Awesome, thanks!
 
> > I wonder about the histogram tool.
> 
> Actually I was thinking that it could be part of gnuplot (it has "set
> terminal dumb", but it could have a "set terminal braille")

Alas, it won't work: I see that, while alignment of the graph itself works
well, anything but terminals (which force a char-cell grid) fails to give
Braille and ASCII characters the same width, despite requesting fixed-width
display.

You can see how bad it is on https://angband.pl/doc/alluni.txt -- you should
get an aligned grid with right edge of every full block forming an even
vertical line, yet most blocks fail to align even within themselves.

gnuplot relies on being able to place labels within the image, which works
for ASCII and maybe Latin/Greek/Cyrillic but, except for most terminals, not
for anything else.  Too many people use in-browser webmails or GUI clients
(a heresy, mutt is the way to go!), or read list archives via WWW.

> but a very simple script that emits histograms from basic data makes sense
> to me too.  I was wondering whether such simple tool already exist, using
> just ASCII to produce the histograms, but couldn't find one with a quick
> search.

That's what we have ITPs for -- thanks for pointing out my image converter
is redundant.  It looks like no one made a histogram tool using
high-resolution Braille yet, thus I'll add some features (like auto-scaling
Y axis -- doing it manually is tedious, horizontal mode, etc) and package
this part.
 
> It would probably be useful to make such tool have an optional ASCII
> mode.

Meh, I don't think mail clients, terminals and web browsers without Unicode
support deserve much thought.  There's a problem in jessie-'s FreeMono where
it produces a grayish block for Braille (both legitimate use and our abuse)
but since the fix comes a release cycle before this graphing tool, it might
be good enough.

> It should also not assume UTF-8 output, but use something like "|
> iconv -f utf-8", since chinese people have their own way of encoding
> unicode.

I'm about to raise a thread about dropping ancient locale support in buster,
almost no one uses them anymore, GUI stuff hardly pays lip service to
non-Unicode, and it seriously burdens i18n efforts.

In any case, there wasn't a single bug report filed with such an old Chinese
locale since 2012; 2013-2017 stats are:

 ISO-8859-1 |   736
 ISO-8859-15|   187
 ISO-8859-2 |46
 KOI8-R |39
 EUC-JP |14
 TIS-620| 2


Unrelated: perhaps some other name than "braillegraph" would be better?  The
glyphs used belonging to the Braille range is an implementation detail,
users probably won't care other than for requiring Unicode.


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

Bug#856154: mupen64plus-qt: missing dependency on libqt5sql5-sqlite

[Johannes Schauer]

Package: mupen64plus-qt
Version: 1.9-1
Severity: normal

Hi,

without the package libqt5sql5-sqlite, mupen64plus will run but many
menu options will be disabled. Please add the package at least as a
Recommends. Specifically one gets the following output:

QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers: 
QSqlQuery::exec: database not open
QSqlQuery::value: not positioned on a valid record
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open



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

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 mupen64plus-qt depends on:
ii  libc6   2.24-8
ii  libgcc1 1:6.3.0-5
ii  libqt5core5a5.7.1+dfsg-3
ii  libqt5gui5  5.7.1+dfsg-3
ii  libqt5network5  5.7.1+dfsg-3
ii  libqt5sql5  5.7.1+dfsg-3
ii  libqt5widgets5  5.7.1+dfsg-3
ii  libqt5xml5  5.7.1+dfsg-3
ii  libquazip5-10.7.2-1
ii  libstdc++6  6.3.0-5
ii  mupen64plus-ui-console  2.5-3

mupen64plus-qt recommends no packages.

mupen64plus-qt suggests no packages.

-- no debconf information

Bug#852282: Acknowledgement (Terminator window grabs focus and gets raised when another Terminator appears)

[Eduard Bloch]

Hallo,
* Debian Bug Tracking System [Mon, Jan 23 2017, 07:30:07AM]:
> Thank you for filing a new Bug report with Debian.

This seems to be https://bugs.launchpad.net/terminator/+bug/1646437 .
Please upload a fixed version as soon as reference Ubuntu version
becomes available.

Regards,
Eduard.

Bug#856152: python-apt: FTBFS: Testsuite failure

[Julian Andres Klode]

Control: tag -1 moreinfo

On Sat, Feb 25, 2017 at 08:53:26AM -0800, Daniel Schepler wrote:
> Source: python-apt
> Version: 1.4.0~beta2
> Severity: serious
> 
> From my pbuilder build log:
> 
> ...
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/build/python-apt-1.4.0~beta2'
> set -e; for python in python2.7 python3.5 ; do \
> $python tests/test_all.py -q || [ "linux" = "hurd" ]; \
> done;
> [tests] Running on 2.7.13 (default, Feb  9 2017, 10:00:34) [GCC 6.3.0 
> 20170205]
> Using library_dir:
> '/build/python-apt-1.4.0~beta2/build/lib.linux-x86_64-2.7'WARNING:
> Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> ==
> ERROR: testAddKeyFromServer (test_auth.TestAuthKeys)
> Install a GnuPG key from a remote server.
> --
> Traceback (most recent call last):
>   File "/build/python-apt-1.4.0~beta2/tests/test_auth.py", line 230,
> in testAddKeyFromServer
> "hkp://localhost:%d" % self.keyserver_port)
>   File "/build/python-apt-1.4.0~beta2/build/lib.linux-x86_64-2.7/apt/auth.py",
> line 129, in add_key_from_keyserver
> _add_key_from_keyserver(keyid, keyserver, tmp_keyring_dir)
>   File "/build/python-apt-1.4.0~beta2/build/lib.linux-x86_64-2.7/apt/auth.py",
> line 157, in _add_key_from_keyserver
> keyserver, keyid))
> AptKeyError: recv from 'hkp://localhost:19191' failed for
> '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553'
> 
> --
> Ran 94 tests in 11.363s

Retry it. Maybe it timed out or something.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.