Bug#895508: evolution no quoting when repling to message

[Pascal Obry]

Package: evolution
Version: 3.28.1-1

After updating evolution to 3.28.1-1 in unstable branch yesterday  when
replying to a message the original message is not quoted anymore.

Reverting to evolution/testing 3.28.0-4 fixed this issue. It seems a recent
regression in 3.28.1.

Please let me know if you need more information.

Thanks!


-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

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

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

Bug#895509: ITP: r-cran-dorng -- GNU R generic reproducible parallel backend for 'foreach' loops

[Andreas Tille]

Package: wnpp
Severity: wishlist
Owner: Andreas Tille 

* Package name: r-cran-dorng
  Version : 1.6.6
  Upstream Author : Renaud Gaujoux 
* URL : https://cran.r-project.org/package=doRNG
* License : GPL
  Programming Lang: GNU R
  Description : GNU R generic reproducible parallel backend for 'foreach' 
loops
 This GNU R package provides functions to perform
 reproducible parallel foreach loops, using independent
 random streams as generated by L'Ecuyer's combined
 multiple-recursive generator [L'Ecuyer (1999), ].
 It enables to easily convert standard %dopar% loops into
 fully reproducible loops, independently of the number
 of workers, the task scheduling strategy, or the chosen
 parallel environment and associated foreach backend.


Remark: This package is needed to upgrade r-cran-blockmodeling to its latest
upstream version.  It will be maintained by the R-pkg team at
https://salsa.debian.org/r-pkg-team/r-cran-dorng

Bug#885182: [kmail] Once more, with feeling ...

[David Baron]

Package: kmail
Version: 4:17.12.3-1

--- Please enter the report below this line. ---
I am running Sid so must accept occasional breakage.

However, such long-term breakage on TESTING of the Kmail/Akonadi stuff is not 
acceptable.

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

Debian Release: buster/sid
  500 yakkety ppa.launchpad.net 
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  500 sid linux.dropbox.com 
  500 lucid   ppa.launchpad.net 
  100 jessie-backports ftp.us.debian.org 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends (Version) | Installed
=-+-
==
akonadi-server  (>= 4:17.08~) | 
4:17.12.3-2+b1
kdepim-runtime  (>= 4:17.08~) | 
4:17.12.3-1
libkf5akonadisearch-bin (>= 4:17.08~) | 
4:17.12.3-1
libkf5akonadisearch-plugins (>= 4:17.08~) | 
4:17.12.3-1
libkf5grantleetheme-plugins   (>= 17.08~) | 17.12.3-1
kio   | 5.44.0-2
libc6   (>= 2.14) | 
libgcc1(>= 1:3.0) | 
libgpgmepp6   (>= 1.10.0) | 
libkf5akonadiagentbase5   (>= 4:15.07.90) | 
libkf5akonadicontact5  (>= 4:17.12.2) | 
libkf5akonadicore5abi1 (>= 4:17.12.1) | 
libkf5akonadimime5 (>= 4:17.12.2) | 
libkf5akonadisearchdebug5  (>= 4:17.12.2) | 
libkf5akonadisearchpim5(>= 4:16.08.0) | 
libkf5akonadiwidgets5abi1  (>= 4:17.12.1) | 
libkf5bookmarks5  (>= 4.96.0) | 
libkf5calendarcore5abi1(>= 4:17.12.1) | 
libkf5calendarutils5   (>= 4:17.12.2) | 
libkf5codecs5   (>= 5.4.0+git20141202.0008+15.04) | 
libkf5completion5 (>= 4.97.0) | 
libkf5configcore5 (>= 4.98.0) | 
libkf5configgui5  (>= 4.97.0) | 
libkf5configwidgets5  (>= 5.23.0) | 
libkf5contacts5(>= 4:15.12.0) | 
libkf5coreaddons5  (>= 5.2.0) | 
libkf5crash5  (>= 5.15.0) | 
libkf5dbusaddons5 (>= 4.97.0) | 
libkf5followupreminder5(>= 4:16.04.0) | 
libkf5gravatar5abi1(>= 4:17.12.2) | 
libkf5guiaddons5  (>= 4.96.0) | 
libkf5i18n5   (>= 4.97.0) | 
libkf5iconthemes5  (>= 5.0.0) | 
libkf5identitymanagement5(>= 17.12.2) | 
libkf5itemmodels5 (>= 4.96.0) | 
libkf5itemviews5  (>= 4.96.0) | 
libkf5jobwidgets5 (>= 4.96.0) | 
libkf5kcmutils5(>= 5.2.0+git20141003) | 
libkf5kiocore5(>= 4.96.0) | 
libkf5kiofilewidgets5 (>= 4.96.0) | 
libkf5kiowidgets5 (>= 5.35.0) | 
libkf5kontactinterface5  (>= 17.12.2) | 
libkf5ksieveui5(>= 4:17.12.2) | 
libkf5libkdepim-plugins   | 
libkf5libkdepim5   (>= 4:16.04.0) | 
libkf5libkdepimakonadi5(>= 4:17.12.2) | 
libkf5libkleo5 (>= 4:17.08.0) | 
libkf5mailcommon5abi1  (>= 4:17.12.2) | 
libkf5mailtransport5 (>= 17.12.2) | 
libkf5mailtransportakonadi5  (>= 17.12.2) | 
libkf5messagecomposer5 (>= 4:17.12.2) | 
libkf5messagecore5 (>= 4:17.12.2) | 
libkf5messagelist5 (>= 4:17.12.2) | 
libkf5messageviewer5   (>= 4:17.12.2) | 
libkf5mime5abi1  (>= 17.12.1) | 
libkf5mimetreeparser5  (>= 4:17.12.2) | 
libkf5notifications5  (>= 4.96.0) | 
libkf5notifyconfig5   (>= 4.96.0) | 
libkf5parts5  (>= 4.96.0) | 
libkf5pimcommon5abi1  

Bug#513967:

[Vasyl Vavrychuk]

How about licensecheck detects pattern "See Copyright Notice at the
end of this file" and goes LICENSECHECK_PARSELINES from the end to
look for a license.

Bug#895434: [Pkg-swan-devel] Bug#895434: Drop (unused) Build-Depends on network-manager-dev

[Yves-Alexis Perez]

On Wed, 2018-04-11 at 18:27 +0200, Michael Biebl wrote:
> 
> Package builds fine with network-manager-dev dropped from Build-Depends.
> Trivial patch attached.

Thanks (I already had done the work, sorry for not replying sooner). It'll
also be part of the next upload. I also made the libnm-dev b-d linux-any.

Regards,
-- 
Yves-Alexis

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

Bug#895466: debootstrap 1.0.96 fails due to missing apt-config

[Raphael Hertzog]

Hi,

On Wed, 11 Apr 2018, Olliver Schinagl wrote:
> While running debootstrap on a non-native debian system, debootstrap keeps
> failing with
> 
> debootstrap: line 55: apt-config: command not found

Duh... this change has even been discussed on the mailing list. I think
it's partly fixed already in git but still there's a big misunderstanding.

Hideki, when Ben Hutchings suggested to use "command -v" it means "command
-v apt-config" and not "apt-config -v".

But really the code that went into 1.0.96 is completely wrong. Basically
you tested whether "apt-config -v >/dev/null" is a non-empty string. And
yes it's a non-empty string. :-)

I pushed a proper fix to git.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

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

Bug#895510: ITP: python-raccoon -- Python DataFrame with fast insert and appends

[Sebastien Delafond]

Package: wnpp
Severity: wishlist
Owner: Sebastien Delafond 

* Package name: python-raccoon
  Version : 2.1.5
  Upstream Author : Ryan Sheftel
* URL : https://github.com/rsheftel/raccoon
* License : MIT
  Programming Lang: Python
  Description : Python DataFrame with fast insert and appends

 Lightweight DataFrame and Series implementation inspired by the
 phenomenal Pandas package for the one use case where Pandas is known to
 be sub-optimal: DataFrames that grow in size by rows frequently in the
 code. Additionally Raccoon DataFrames can be parametrized to be sorted
 so that additions to the DataFrame keep the index in sorted order to
 speed inserts and retrievals.

This will be a dependency for recent mlbstreamer releases.

Bug#895466: debootstrap 1.0.96 fails due to missing apt-config

[Simon McVittie]

On Wed, 11 Apr 2018 at 22:14:21 +0200, Olliver Schinagl wrote:
> Tags: newcomer

The newcomer tag is for use by the package's maintainer. It indicates a
bug that is particularly suitable for new contributors to work on as an
introduction to contributing to this package (I don't think this is one
of those). It does not indicate bugs that were encountered by new users,
or bugs that particularly affect new users.

> While running debootstrap on a non-native debian system, debootstrap keeps
> failing with
> 
> debootstrap: line 55: apt-config: command not found
> 
> The change causing the issue seems to be 
> https://anonscm.debian.org/cgit/d-i/debootstrap.git/commit/?id=98858a907a9f69e
> which always seems to pass the if check (even though it's not installed) and
> then fails on the eval.

Recent versions (I'm looking at the git repository here) seem to have
introduced seversal misunderstood conditionals. Were these tested or
reviewed?

The important thing to remember in shell conditions is that the square
brackets in "if [ ... ]; then" are not special shell syntax: the
opening square bracket is another name for test(1), and the closing
square bracket is required and ignored when test(1) is invoked as
[(1). The square brackets should be used if and only if you want to
check a condition that is most easily checked via test(1).

The line mentioned in this bug is:

if [ "apt-config -v > /dev/null" ]; then

which is equivalent to "if true; then" because "apt-config -v > /dev/null"
is a non-empty string. I think this was meant to be either

if apt-config -v > /dev/null 2>&1; then

which enters the "then" block whenever apt-config -v exits 0 (success),
or

if [ -n "$(apt-config -v 2>/dev/null)" ]; then

which enters the "then" block whenever apt-config -v produces output.
Either way, stderr should probably be redirected to /dev/null (as shown)
to silence "apt-config: not found" messages on non-Debian systems.

This is not the only problematic conditional. There's also:

+if [ ! "$VARIANT" = fakechroot ] && [ "$(apt-config -v > /dev/null 2>&1)" 
]; then

The second part of this condition will always evaluate to false, because
apt-config -v > /dev/null 2>&1 never produces output (it has all been
redirected to /dev/null), so the $() operator produces no output, and
the test is [ "" ] which returns false. I think this was meant to be:

if [ ! "$VARIANT" = fakechroot ] && apt-config -v > /dev/null 2>&1; then

in which the second part becomes a check for "did apt-config -v exit with
status 0?", or possibly

if [ ! "$VARIANT" = fakechroot ] && [ -n "$(apt-config -v 2>/dev/null)" ]; 
then

in which the second part checks whether apt-config produced output.

Similarly:

+if [ "$(ls -A "$TARGET" > /dev/null 2>&1)" ]; then

doesn't do anything useful, because the output of ls is discarded. Either
the intention was to check whether the output of ls was non-empty (in
which case remove the "> /dev/null" redirection and use 2>/dev/null),
or the intention was to check the exit status (in which case remove []
and "$()").

When testing whether a string is (non-)empty, I would recommend using the
[ -n "$foo" ] or [ -z "$foo" ] form instead of just [ "$foo" ] or
! [ "$foo" ] - it makes it a bit clearer what the intention was.

smcv

Bug#895511: exactimage FTBFS with libevas-dev 1.20.7

[Adrian Bunk]

Source: exactimage
Version: 1.0.1-1
Severity: serious

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

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fopenmp 
-ffunction-sections -fdata-sections -fPIC -Wno-switch -Wno-switch-enum 
-Wno-sign-compare -std=gnu++98 -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -I . -I/usr/include/agg2 -I/usr/include/freetype2 
-I/usr/include/libpng16 -I image -I utility -I/usr/include/OpenEXR -I codecs/ 
-I bardecode -I utility -I utility -I/usr/X11/include -pthread 
-I/usr/include/efl-1 -I/usr/include/evas-1 -I/usr/include/evas-1/canvas 
-I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/efl-1 
-I/usr/include/ecore-1 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/efl-1 
-I/usr/include/eet-1 -I/usr/include/efl-1 -I/usr/include/emile-1 
-I/usr/include/efl-1 -I/usr/include/p11-kit-1 -I/usr/include/efl-1 
-I/usr/include/eo-1 -I/usr/include/efl-1 -I/usr/include/eina-1 
-I/usr/include/eina-1/eina -I/usr/include/luajit-2.1 -Igfx -D 
WITHEVAS_COLOR_PREMUL -I . -I lib -I gfx -D WITHEVAS_X11_CONNECTION -D 
WITHEVAS_X11_SCREEN  -c  -MMD -MP -MF 'objdir/gfx/X11Helper.d' -o 
'objdir/gfx/X11Helper.o' 'gfx/X11Helper.cc'
In file included from gfx/X11Helper.cc:36:0:
gfx/X11Helper.hh:33:10: fatal error: Evas_Engine_Software_X11.h: No such file 
or directory
 #include "Evas_Engine_Software_X11.h"
  ^~~~
compilation terminated.
make[3]: *** [build/bottom.make:54: objdir/gfx/X11Helper.o] Error 1

Bug#895466: debootstrap 1.0.96 fails due to missing apt-config

[Hideki Yamane]

Hi,

 Thanks for the fix, I was really moron.


On Thu, 12 Apr 2018 09:58:04 +0200
Raphael Hertzog  wrote:
> I pushed a proper fix to git.

 Well, other part of fixes,

> Drop default value for --cache-dir parameter
> 
> It is not at all appropriate for debootstrap to start putting files
> in APT's cache of .deb files (it could possibly use it in a read-only
> way, but writing to it is not desirable). Furthermore the code was not
> working as expected, the default value was only put in place if the
> --cache-dir option was passed and it would require an explicit value
> anyway.

 It's not so wrong to put files under /var/cache/apt/archives, IMO.
 Users can get benefit without any notices with --cache-dir option.
 And I want to know the situation this doesn't work, so could you
 give me more explanation, please?


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#895512: taskcoach FTBFS with wxpython3.0 3.0.2.0+dfsg-7

[Adrian Bunk]

Source: taskcoach
Version: 1.4.3-5
Severity: serious

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/taskcoach-1.4.3'
python changes.in/make.py text > CHANGES.txt
gm convert -resize 32x32 icons.in/taskcoach.png icons.in/taskcoach.xpm
xvfb-run /usr/bin/make prepare
make[2]: Entering directory '/build/1st/taskcoach-1.4.3'
cd thirdparty; tar xzf desktop-0.4.2.tar.gz --strip-components=1 -C 
../taskcoachlib/thirdparty desktop-0.4.2/desktop
cd thirdparty; tar xzf 
python-ntlm-40080cff37ab32570f9bb50bad0a46b957409c18.tar.gz 
--strip-components=1 -C ../taskcoachlib/thirdparty python-ntlm/ntlm
cd thirdparty; tar xzf wxScheduler-r151.tar.gz --strip-components=1 -C 
../taskcoachlib/thirdparty wxScheduler/wxScheduler
cd thirdparty; tar xzf WMI-1.4.9.tar.gz --strip-components=1 -C 
../taskcoachlib/thirdparty WMI-1.4.9/wmi.py
cd thirdparty; tar xzf pybonjour-1.1.1.tar.gz --strip-components=1 -C 
../taskcoachlib/thirdparty pybonjour-1.1.1/pybonjour.py
cp /usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/lib/agw/customtreectrl.py 
taskcoachlib/thirdparty
cp: cannot stat 
'/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/lib/agw/customtreectrl.py': No 
such file or directory
make[2]: *** [Makefile:204: thirdpartymodules] Error 1

Bug#859388: blkdeactivate: /bin/sort: No such file or directory

[Julian Andres Klode]

Package: lvm2
Version: 2.02.176-4.1
Followup-For: Bug #859388
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch



*** /tmp/tmpqyjXGq/bug_body

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

  * scripts/blkdeactivate.sh.in: Refer to /usr/bin/sort, not /bin/sort


Thanks for considering the patch.


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

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

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
diff -Nru lvm2-2.02.176/debian/control lvm2-2.02.176/debian/control
--- lvm2-2.02.176/debian/control2018-01-30 08:31:47.0 +0100
+++ lvm2-2.02.176/debian/control2018-04-12 10:35:07.0 +0200
@@ -1,8 +1,7 @@
 Source: lvm2
 Section: admin
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian LVM Team 

+Maintainer: Debian LVM Team 
 Uploaders: Bastian Blank 
 Build-Depends:
  debhelper (>= 10.9.2),
diff -Nru lvm2-2.02.176/debian/patches/blkdeactivate-use-usr-bin-sort.patch 
lvm2-2.02.176/debian/patches/blkdeactivate-use-usr-bin-sort.patch
--- lvm2-2.02.176/debian/patches/blkdeactivate-use-usr-bin-sort.patch   
1970-01-01 01:00:00.0 +0100
+++ lvm2-2.02.176/debian/patches/blkdeactivate-use-usr-bin-sort.patch   
2018-04-12 10:35:07.0 +0200
@@ -0,0 +1,17 @@
+Description: scripts/blkdeactivate.sh.in: Refer to /usr/bin/sort, not /bin/sort
+ We ship sort in /usr/bin, not in /bin
+Author: Julian Andres Klode 
+Forwarded: no
+Last-Update: 2018-04-12
+
+--- lvm2-2.02.176.orig/scripts/blkdeactivate.sh.in
 lvm2-2.02.176/scripts/blkdeactivate.sh.in
+@@ -58,7 +58,7 @@ MPATHD_OPTS=""
+ LSBLK="/bin/lsblk -r --noheadings -o TYPE,KNAME,NAME,MOUNTPOINT"
+ LSBLK_VARS="local devtype local kname local name local mnt"
+ LSBLK_READ="read -r devtype kname name mnt"
+-SORT_MNT="/bin/sort -r -u -k 4"
++SORT_MNT="/usr/bin/sort -r -u -k 4"
+ 
+ # Do not show tool errors by default (only done/skipping summary
+ # message provided by this script) and no verbose mode by default.
diff -Nru lvm2-2.02.176/debian/patches/series 
lvm2-2.02.176/debian/patches/series
--- lvm2-2.02.176/debian/patches/series 2018-01-26 17:07:31.0 +0100
+++ lvm2-2.02.176/debian/patches/series 2018-04-12 10:35:07.0 +0200
@@ -12,3 +12,4 @@
 systemd-pvscan-background.patch
 enable-issue-discards.patch
 0014-no-lvm2-monitor-in-containers.patch
+blkdeactivate-use-usr-bin-sort.patch

Bug#895513: pstotext doesn't work any more: Unrecoverable error: undefined in DELAYBIND

[Iain Lane]

Package: pstotext
Version: 1.9-6
Severity: grave
Tags: upstream

Hi,

This "makes the package in question unusable by most or all users",
hence the severity.

pstotext appears to have been broken by ghostscript 9.22. This is me
attempting to convert an empty input.

(sid-amd64)root@nightingale:/# echo | pstotext -debug
GPL Ghostscript 9.22 (2017-10-04)
Copyright (C) 2017 Artifex Software, Inc.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.

 *** WARNING - the DELAYBIND command has been deprecated, and will be
   removed in the next version. For now you can restore
   the behaviour by using -dREALLYDEALYBIND but if you
   require continued use of this command you should contact
   the Ghostscript developers. Commercial customers of
   Artifex should email their support contact, free users
   are encouraged to talk to us on the #ghostscript IRC
   channel on irc.freenode.net.

Unrecoverable error: undefined in DELAYBIND

I tried a patch to add -dREALLYDELAYBIND to the gs commandline, but then
it fails with "Error: /undefined in NOBIND".

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

Bug#895511: exactimage FTBFS with libevas-dev 1.20.7

[Sven Eckelmann]

severity 878572 serious
block 895511 by 878572
thanks

On Donnerstag, 12. April 2018 11:08:47 CEST Adrian Bunk wrote:
> Source: exactimage
> Version: 1.0.1-1
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/exactimage.html

Thanks for bringing this up again. This is a long standing bug in libevas-dev. 
Increasing the severity for the libevas-dev bug now because they have uploaded 
the problematic version to unstable without fixing it.

Kind regards,
Sven

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

Bug#895514: ITP: ccextractor -- fast closed captions extractor

[Sophie Brun]

Package: wnpp
Severity: wishlist
Owner: Sophie Brun 

* Package name: ccextractor
  Version : 0.86
  Upstream Author : Carlos Fernandez
* URL : https://github.com/CCExtractor/ccextractor/
* License : GPL-2
  Programming Lang: C
  Description : fast closed captions extractor

This tools analyzes video files and produces independent subtitle files
from the closed captions data. It supports DVD, HDTV transport streams,
Replay TV.

Bug#893933: Request for new mailing list: freedombox

[James Valleroy]

On 04/04/2018 12:54 PM, Hanno 'Rince' Wagner wrote:
> I just created the mailinglist debian-freedom...@lists.debian.org.
> I also imported the public archive, but to import the subscribers I
> need a list of current subscribers. If you make this available to me
> (eg on people.debian.org), I can mass-import them.

Hi Hanno,

I used a script [1] to export the member list and member options in csv format
(attached). It is encrypted using your public key. Would you be able to import
this to the new list?

[1] https://www.msapiro.net/scripts/mailman-subscribers.py

Thanks,
James


freedombox-discuss-members.csv.gpg
Description: application/pgp-encrypted


signature.asc
Description: OpenPGP digital signature

Bug#895446: gitk: Error in startup script: bad screen distance "4.5"

[Jonathan Nieder]

tags 895446 + moreinfo
quit

Hi Michael,

Michael Biebl wrote:

> gitk no longer successfully starts here. When I run it from a terminal,
> I get
>
> $ gitk
> Error in startup script: bad screen distance "4.5"
> while executing
> "$canv conf -scrollregion [list 0 0 $canvxmax $ymax]"
> (procedure "setcanvscroll" line 6)
> invoked from within
> "setcanvscroll"
> (procedure "initlayout" line 17)
> invoked from within
> "initlayout"
> (procedure "getcommits" line 4)
> invoked from within
> "getcommits {}"
> (file "/usr/bin/gitk" line 12613)
> $ echo $?
> 1

I'm not yet able to reproduce this.  The package works fine for me.

Torbjörn Andersson suggests that it may be related to the fontconfig
version; can you confirm?  E.g. did the problem start for you at the
same time as a fontconfig update?

Can you try running gitk from testing or stable to see if they behave
differently?

Part of the reason I ask these questions is that gitk hasn't had any
recent changes.

Thanks,
Jonathan

Bug#895515: RFS: deepin-icon-theme/15.12.56-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "deepin-icon-theme"

* Package name: deepin-icon-theme
  Version : 15.12.56-1
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://github.com/linuxdeepin/deepin-icon-theme
* License : GPL-3+
  Section : x11

It builds those binary packages:

  deepin-icon-theme - Icon Theme for Deepin software and Deepin Desktop 
Environment

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

  https://mentors.debian.net/package/deepin-icon-theme

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

  dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-icon-theme/deepin-icon-theme_15.12.56-1.dsc

More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-icon-theme

Changes since the last upload:
  * New upstream release.
  * d/control: Update Standards-Version to 4.1.4.
  * d/control: Add new uploader Yanhao Mo .

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#895516: wxpython4.0 FTBFS: test failure

[Adrian Bunk]

Source: wxpython4.0
Version: 4.0.1+dfsg-2
Severity: serious

Some recent change in unstable makes wxpython4.0 FTBFS:

https://tests.reproducible-builds.org/debian/history/wxpython4.0.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/wxpython4.0.html

...
   dh_auto_test -O--buildsystem=pybuild
 fakeroot debian/rules binary
dh binary --with python2,python3 --buildsystem=pybuild
   dh_testroot -O--buildsystem=pybuild
   dh_prep -O--buildsystem=pybuild
   dh_auto_install -O--buildsystem=pybuild
I: pybuild pybuild:267: mkdir -p 
/build/1st/wxpython4.0-4.0.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages
I: pybuild base:217: easy_install -m -d 
/build/1st/wxpython4.0-4.0.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages -Z 
dist/*.egg
/bin/sh: 1: easy_install: not found
E: pybuild pybuild:336: install: plugin custom failed with: exit code=127: 
easy_install -m -d 
/build/1st/wxpython4.0-4.0.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages -Z 
dist/*.egg
dh_auto_install: pybuild --install -i python{version} -p 2.7 --dest-dir 
/build/1st/wxpython4.0-4.0.1\+dfsg/debian/tmp returned exit code 13
make: *** [debian/rules:18: binary] Error 25

Bug#895446: gitk: Error in startup script: bad screen distance "4.5"

[Jonathan Nieder]

reassign 895446 libfontconfig1 2.13.0-2
severity 895470 serious
retitle 895470 fontconfig-2.13.0 globally sets the locale from the environment
forcemerge 895470 895446
affects 895470 + gitk
tags 895470 + patch fixed-upstream
quit

Jonathan Nieder wrote:
> Michael Biebl wrote:

>> gitk no longer successfully starts here. When I run it from a terminal,
>> I get
>>
>> $ gitk
>> Error in startup script: bad screen distance "4.5"
>> while executing
>> "$canv conf -scrollregion [list 0 0 $canvxmax $ymax]"
>> (procedure "setcanvscroll" line 6)
>> invoked from within
>> "setcanvscroll"
>> (procedure "initlayout" line 17)
>> invoked from within
>> "initlayout"
>> (procedure "getcommits" line 4)
>> invoked from within
>> "getcommits {}"
>> (file "/usr/bin/gitk" line 12613)
>> $ echo $?
>> 1
>
> I'm not yet able to reproduce this.  The package works fine for me.

Ah, I figured it out.  It's from libfontconfig's new setlocale() call.
I wasn't able to reproduce it because my locale uses a different decimal
separator.

Bug#895517: libglade2-0: deprecated and unmaintained upstream

[Simon McVittie]

Package: libglade2-0
Version: 1:2.6.4-1
Severity: important
Tags: upstream wontfix

libglade is obsolete, and is no longer maintained by its former upstream
developers. The supported replacement is GtkBuilder, available since
GTK+ 2.12.

Official migration guide:
https://developer.gnome.org/gtk2/stable/gtk-migrating-GtkBuilder.html

smcv

Bug#895519: override: libglade2-0:oldlibs/optional, libglade2-dev:oldlibs/optional, libglade2.0-cil-dev:oldlibs/optional, libglade2.0-cil:oldlibs/optional, libglademm-2.4-1v5:oldlibs/optional, libglad

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override

libglade was deprecated in 2009 in favour of the then-new GtkBuilder
feature in GTK+ 2.12, and should not be used in new code. Please move
it and its various language bindings to the oldlibs section.

libglade2-0:oldlibs/optional
libglade2-dev:oldlibs/optional
libglade2.0-cil-dev:oldlibs/optional
libglade2.0-cil:oldlibs/optional
libglademm-2.4-1v5:oldlibs/optional
libglademm-2.4-dev:oldlibs/optional
libglademm-2.4-doc:oldlibs/optional
libgtk2-gladexml-perl:oldlibs/optional
libgtk2-gladexml-simple-perl:oldlibs/optional
libgtkdatabox-0.9.3-0-libglade:oldlibs/optional
python-glade2:oldlibs/optional

There is currently no plan to remove libglade from unstable before buster,
but libglademm is less-used and will hopefully not be shipped in buster.

Please note that src:glade, including libgladeui, is not deprecated. It
used to be a GUI for libglade, but is now a GUI for GtkBuilder, which is
the maintained replacement for libglade.

Thanks,
smcv

Bug#895518: libsdl2-dev is not Multi-Arch compatible

[Francois Gouget]

Package: libsdl2-dev
Version: 2.0.8+dfsg1-1
Severity: normal

Dear Maintainer,

The development package is not multiarch aware which causes the amd64
version to conflict with the i386 one, thus making it impossible to
install both.

As a result the /usr/lib/i386-linux-gnu/libSDL2.so symbolic link is
missing so that developping 32 bit applications that use this library
is impossible on a 64 bit system.

In particular this makes development of the Wine project really painful
on Debian as Wine really needs both 32 and 64 bit support since most
64 bit Windows applications have a 32 bit installer.


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

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

Versions of packages libsdl2-dev depends on:
ii  libasound2-dev 1.1.3-5
ii  libdbus-1-dev  1.12.6-2
ii  libegl1-mesa-dev   17.3.7-1
ii  libgl1-mesa-dev17.3.7-1
ii  libgles2-mesa-dev  17.3.7-1
ii  libglu1-mesa-dev   9.0.0-3
ii  libibus-1.0-dev1.5.18-1
ii  libpulse-dev   11.1-4
ii  libsdl2-2.0-0  2.0.8+dfsg1-1
ii  libsndio-dev   1.1.0-3
ii  libudev-dev238-4
ii  libwayland-dev 1.14.0-2
ii  libx11-dev 2:1.6.5-1
ii  libxcursor-dev 1:1.1.15-1
ii  libxext-dev2:1.3.3-1+b2
ii  libxi-dev  2:1.7.9-1
ii  libxinerama-dev2:1.1.3-1+b3
ii  libxkbcommon-dev   0.8.0-1
ii  libxrandr-dev  2:1.5.1-1
ii  libxss-dev 1:1.2.2-1+b2
ii  libxt-dev  1:1.1.5-1
ii  libxv-dev  2:1.0.11-1
ii  libxxf86vm-dev 1:1.1.4-1+b2

libsdl2-dev recommends no packages.

libsdl2-dev suggests no packages.

-- no debconf information

Bug#895520: libunique-1.0-0: deprecated and unmaintained upstream

[Simon McVittie]

Package: libunique-1.0-0
Version: 1.1.6-4
Severity: important
Tags: upstream wontfix

libunique is obsolete, and is no longer maintained by its former upstream
developers. The supported replacement is GApplication or GtkApplication,
available since GLib 2.26 and GTK+ 3.0.

Official migration guide:
https://developer.gnome.org/gtk3/stable/gtk-migrating-unique-GtkApplication.html

smcv

Bug#895513: pstotext doesn't work any more: Unrecoverable error: undefined in DELAYBIND

[Iain Lane]

On Thu, Apr 12, 2018 at 09:41:03AM +0100, Iain Lane wrote:
> Unrecoverable error: undefined in DELAYBIND
> 
> I tried a patch to add -dREALLYDELAYBIND to the gs commandline, but then
> it fails with "Error: /undefined in NOBIND".

btw, adding -dNOBIND makes this error go away. I don't know if that's
right. But more importantly a real testcase (running the doc-rfc
autopkgtest) still fails with errors about setpagedevice.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


signature.asc
Description: PGP signature

Bug#895521: override: libesd0:oldlibs/optional, libesd0-dev:oldlibs/optional, esound-common:oldlibs/optional

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override

Esound was deprecated in 2009 in favour of libcanberra and PulseAudio,
and should not be used in new code. Please move its library to the oldlibs
section if it cannot be removed soon (#894269 is the removal request,
but it is blocked by a couple of packages that still use libesd).

esound-common:oldlibs/optional
libesd0-dev:oldlibs/optional
libesd0:oldlibs/optional

Thanks,
smcv

Bug#895523: ITP: r-cran-magic -- GNU R create and investigate magic squares

[Andreas Tille]

Package: wnpp
Severity: wishlist
Owner: Andreas Tille 

* Package name: r-cran-magic
  Version : 1.5-8-1
  Upstream Author : Robin K. S. Hankin
* URL : https://cran.r-project.org/package=magic
* License : GPL
  Programming Lang: GNU R
  Description : GNU R create and investigate magic squares
 A collection of efficient, vectorized algorithms for the
 creation and investigation of magic squares and hypercubes, including
 a variety of functions for the manipulation and analysis of
 arbitrarily dimensioned arrays.  The package includes methods for
 creating normal magic squares of any order greater than 2.  The
 ultimate intention is for the package to be a computerized embodiment
 all magic square knowledge, including direct numerical verification
 of properties of magic squares (such as recent results on the
 determinant of odd-ordered semimagic squares).  Some antimagic
 functionality is included.  The package also
 serves as a rebuttal to the often-heard comment "I thought R
 was just for statistics".


Remark: This package is needed as a dependency for r-cran-geometry which
in turn is a new dependency to upgrade r-cran-ddalpha to its latest
upstream version.  It is maintained by the R-pkg team at
   https://salsa.debian.org/r-pkg-team/r-cran-magic

Bug#895522: override: python-gconf:oldlibs/optional, python-gnome2:oldlibs/optional, python-gnome2-dev:oldlibs/optional, python-gnome2-doc:oldlibs/optional

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override

The Python bindings for libgnome and related libraries were deprecated
in around GNOME 3.0, before Debian wheezy (oldoldstable). Please
override their Section to oldlibs (they cannot be removed right now due
to reverse-dependencies).

python-gconf:oldlibs/optional
python-gnome2:oldlibs/optional
python-gnome2-dev:oldlibs/optional
python-gnome2-doc:oldlibs/optional

Source package: gnome-python (sorry, I don't know the override syntax
for source packages, or whether there is one).

Thanks,
smcv

Bug#895237: apache2: apachectl does not use systemd for restarts

[Axel Beckert]

Control: retitle -1 apache2: apachectl restarts don't work properly with all 
init systems (namely not with systemd)

Hi,

Jan Heitkötter wrote:
> Default behaviour is do stop/start Apache using apachectl which fails in 
> installations running systemd. Apache will stop, but not start again.

While this is definitely an issue, ...

> Fix: use systemctl to start/stop Apache.

... this is _not_ the solution.

Debian has not only systemd as init system (but at least also
sysvinit, openrc and runit, maybe more) and such actions need to stay
init-system-agnostic, e.g. either use the Debian-specific invoke-rc.d
command or the init-system- and distribution-agnostic "service"
command. Retitling the bug report accordingly.

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

Bug#895524: override: python-gnome2-desktop-dev:oldlibs/optional, python-gnomekeyring:oldlibs/optional, python-rsvg:oldlibs/optional, python-wnck:oldlibs/optional

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override

The Python bindings for GNOME 2 libraries were deprecated in around GNOME
3.0, before Debian wheezy (oldoldstable). Please override their Section
to oldlibs (they cannot be removed right now due to reverse-dependencies).

python-desktop-dev:oldlibs/optional
python-gnomekeyring:oldlibs/optional
python-rsvg:oldlibs/optional
python-wnck:oldlibs/optional

Source package: gnome-python-desktop

Thanks,
smcv

Bug#895525: dune-pdelab FTBFS with libdune-localfunctions-dev 2.6.0-1

[Adrian Bunk]

Source: dune-pdelab
Version: 2.5.0~rc1-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dune-pdelab.html

...
In file included from 
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelementmap/opbfem.hh:8:0,
 from 
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/test/fem/opbfem.hh:7,
 from 
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/test/fem/testfemwithgfs.cc:23:
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh: At 
global scope:
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:773:117:
 error: wrong number of template arguments (8, should be 7)
 typedef 
Dune::LocalBasisTraits,R,1,Dune::FieldVector,Dune::FieldMatrix,
 0> Traits;

 ^
In file included from 
/usr/include/dune/localfunctions/brezzidouglasmarini/brezzidouglasmarini1simplex2d/brezzidouglasmarini1simplex2dlocalbasis.hh:13:0,
 from 
/usr/include/dune/localfunctions/brezzidouglasmarini/brezzidouglasmarini1simplex2d.hh:9,
 from 
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelementmap/bdm1simplex2dfem.hh:6,
 from 
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelementmap/brezzidouglasmarinifem.hh:8,
 from 
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/test/fem/rtbdmfem.hh:7,
 from 
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/test/fem/testfemwithgfs.cc:22:
/usr/include/dune/localfunctions/common/localbasis.hh:31:10: note: provided for 
'template struct 
Dune::LocalBasisTraits'
   struct LocalBasisTraits
  ^~~~
In file included from 
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelementmap/opbfem.hh:8:0,
 from 
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/test/fem/opbfem.hh:7,
 from 
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/test/fem/testfemwithgfs.cc:23:
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:784:50:
 error: 'Traits' is not a class, namespace, or enumeration
 inline void evaluateFunction (const typename Traits::DomainType& in,
  ^~
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:73:
 error: template argument 1 is invalid
   std::vector& 
out) const {
 ^
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:73:
 error: template argument 2 is invalid
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:73:
 error: template argument 1 is invalid
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:73:
 error: template argument 2 is invalid
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:73:
 error: template argument 1 is invalid
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:73:
 error: template argument 2 is invalid
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:73:
 error: template argument 1 is invalid
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:73:
 error: template argument 2 is invalid
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:35:
 error: invalid template-id
   std::vector& 
out) const {
   ^~~
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:56:
 error: 'Traits' is not a class, namespace, or enumeration
   std::vector& 
out) const {
^~
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:73:
 error: expected '(' before '>' token
   std::vector& 
out) const {
 ^
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/finiteelement/l2orthonormal.hh:785:35:
 error: template placeholder type 'vector' must be followed by a simple 
declarator-id
   std::vector& 
out) const {
   ^~~
In file included from /usr/include/c++/7/vector:64:0,
 from /usr/include/c++/7/functional:61,
 from /usr/include/dune/common/binaryfunctions.hh:10,
 from 
/usr/include/dune/common/parallel/collectivecommunication.hh:16,
 from /usr/include/dune/common/parallel/mpihelper.hh:14,
 from 
/build/1st/dune-pdelab-2.5.0~rc1/dune/pdelab/test/fem/testfemwithgfs.cc:11:
/usr/include/c++/7/bits/stl_vector.h:216:11: note: 'template class std::vector' declared here
 class vector : prot

Bug#895526: RFS: deepin-image-viewer/1.2.19-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "deepin-image-viewer"

* Package name: deepin-image-viewer
  Version : 1.2.19-1
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://github.com/linuxdeepin/deepin-image-viewer
* License : GPL-3+
  Section : graphics

It builds those binary packages:

  deepin-image-viewer - Image Viewer for Deepin Desktop Environment

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

  https://mentors.debian.net/package/deepin-image-viewer

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

  dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-image-viewer/deepin-image-viewer_1.2.19-1.dsc

More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-image-viewer

Changes since the last upload:
  * New upstream release.
   + Add image settings option.
  * d/control: Update Standards-Version to 4.1.4.

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#895527: libsmithwaterman FTBFS on mips/mipsel: symbol differences

[Adrian Bunk]

Source: libsmithwaterman
Version: 0.0+git20160702.2610e25-2
Severity: serious

https://buildd.debian.org/status/package.php?p=libsmithwaterman&suite=sid

...
   dh_makeshlibs -a -O--no-parallel
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libsmithwaterman0/DEBIAN/symbols doesn't match 
completely debian/libsmithwaterman0.symbols
--- debian/libsmithwaterman0.symbols 
(libsmithwaterman0_0.0+git20160702.2610e25-2_mips)
+++ dpkg-gensymbolsKP3gJG   2018-04-12 08:49:24.980726993 +
@@ -47,7 +47,7 @@
  _ZN20CBandedSmithWatermanC2Ej@Base 0.0+git20160702.2610e25
  _ZN20CBandedSmithWatermanD1Ev@Base 0.0+git20160702.2610e25
  _ZN20CBandedSmithWatermanD2Ev@Base 0.0+git20160702.2610e25
- _ZNKSt5ctypeIcE8do_widenEc@Base 0.0+git20160702.2610e25
+#MISSING: 0.0+git20160702.2610e25-2# _ZNKSt5ctypeIcE8do_widenEc@Base 
0.0+git20160702.2610e25
  _ZNSt6vectorI11IndelAlleleSaIS0_EE12emplace_backIJS0_EEEvDpOT_@Base 
0.0+git20160702.2610e25
  
_ZNSt6vectorI11IndelAlleleSaIS0_EE17_M_realloc_insertIJRKS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
 0.0+git20160702.2610e25
  
_ZNSt6vectorI11IndelAlleleSaIS0_EE17_M_realloc_insertIJS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
 0.0+git20160702.2610e25
@@ -71,6 +71,7 @@
  (arch=alpha armel armhf any-i386 mips mipsel s390x powerpc powerpcspe 
ppc64)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
 0.0+git20160702.2610e25
  (arch=any-amd64 arm64 mips64el ppc64el hppa ia64 riscv64 sh4 sparc64 
x32)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base
 0.0+git20160702.2610e25
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 0.0+git20160702.2610e25
+ 
_ZSteqIcEN9__gnu_cxx11__enable_ifIXsrSt9__is_charIT_E7__valueEbE6__typeERKNSt7__cxx1112basic_stringIS3_St11char_traitsIS3_ESaIS3_EEESE_@Base
 0.0+git20160702.2610e25-2
  _ZeqRK11IndelAlleleS1_@Base 0.0+git20160702.2610e25
  _ZlsRSoRK11IndelAllele@Base 0.0+git20160702.2610e25
  _ZltRK11IndelAlleleS1_@Base 0.0+git20160702.2610e25
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:8: binary-arch] Error 2

Bug#895528: override: libgoffice-0.8-8:oldlibs/optional, libgoffice-0.8-8-common:oldlibs/optional, libgoffice-0.8-dev:oldlibs/optional

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override

src:goffice-0.8 is an obsolete GTK+-2-based version of src:goffice. It
should not be used in new code.

As announced in [1] and [2] the GNOME team do not intend to release
goffice-0.8 in buster. However, it cannot yet be removed because gnucash
still depends on it. Please move it to oldlibs for now.

(I realise this should have been requested years ago - I'm trying to
catch up with all the GNOME-2-related oldlibs now, so that it'll be
clearer to our users what is and isn't deprecated.)

libgoffice-0.8-8:oldlibs/optional
libgoffice-0.8-8-common:oldlibs/optional
libgoffice-0.8-dev:oldlibs/optional

Source package: goffice-0.8

Thanks,
smcv

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881532
[2] https://lists.debian.org/debian-devel/2017/10/msg00299.html

Bug#895529: ITP: r-cran-geometry -- GNU R mesh generation and surface tesselation

[Andreas Tille]

Package: wnpp
Severity: wishlist
Owner: Andreas Tille 

* Package name: r-cran-geometry
  Version : 0.3-6-1
  Upstream Author : David C. Sterratt 
* URL : https://cran.r-project.org/package=geometry
* License : GPL
  Programming Lang: GNU R
  Description : GNU R mesh generation and surface tesselation
 This GNU R package makes the qhull library (www.qhull.org)
 available in R, in a similar manner as in Octave and MATLAB. Qhull
 computes convex hulls, Delaunay triangulations, halfspace
 intersections about a point, Voronoi diagrams, furthest-site
 Delaunay triangulations, and furthest-site Voronoi diagrams. It
 runs in 2-d, 3-d, 4-d, and higher dimensions. It implements the
 Quickhull algorithm for computing the convex hull. Qhull does not
 support constrained Delaunay triangulations, or mesh generation of
 non-convex objects, but the package does include some R functions
 that allow for this. Currently the package only gives access to
 Delaunay triangulation and convex hull computation.


Remark: This package is needed to upgrade r-cran-ddalpha to its latest
upstream version.  It is maintained by the R-pkg team at
   https://salsa.debian.org/r-pkg-team/r-cran-geometry

Bug#886146: Testing and Issues

[Philipp Berger]

Dear Julien, dear Maintainers,

the OpenSSL 1.1.x compatibility patch that was applied for #828555
breaks the package and leads to segfaults.
This breaks for example "skrooge" and other applications depending on
libsqlcipher0. I have no idea why this was not caught before the
release, but on a fresh install of Debian 9.4, all default settings, I
installed "skrooge". After opening the program, click "New", then "Save
As", enter a valid name, e.g. "test" and save - the program immediately
crashes with the described problem in LibSQLCipher.

So this is definitely an existing issue, even in the most current
version of Debian 9!

For the path:
I diffed src/crypto_openssl.c against the most current version (3.4.1)
and noticed the switch to the non-deprecated API function around
EVP_CipherInit_ex instead of EVP_CipherInit.
I ported these differences to 3.2.0-2, recompiled the package from
Debian sources including my patch. The resulting binaries no longer
produce segfaults and work as expected.
This is in line with release 3.4.1-1 on sid.

Bug#895530: override: python-gtksourceview2:oldlibs/optional

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override

src:pygtksourceview is a deprecated Python binding for
libgtksourceview2.0-0, which is already in oldlibs. The maintained
replacement is to use gir1.2-gtksource-3.0 via GObject-Introspection.

As announced in [1] and [2] the GNOME team do not intend to release this
package in buster. However, it cannot yet be removed because cherrytree
and liblunar still depend on it. Please move it to oldlibs for now.

(I realise this should have been requested years ago - I'm trying to
catch up with all the GNOME-2-related oldlibs now, so that it'll be
clearer to our users what is and isn't deprecated.)

python-gtksourceview2:oldlibs/optional

Source package: pygtksourceview

Thanks,
smcv

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878698
[2] https://lists.debian.org/debian-devel/2017/10/msg00299.html

Bug#895527: libsmithwaterman FTBFS on mips/mipsel: symbol differences

[Andreas Tille]

Hi Adrian,

you are so fast ... or are you a bot? :-P

I noticed the failure but was waiting for the build status of armhf.

Thanks a lot for your QA work

  Andreas.

On Thu, Apr 12, 2018 at 01:01:28PM +0300, Adrian Bunk wrote:
> Source: libsmithwaterman
> Version: 0.0+git20160702.2610e25-2
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=libsmithwaterman&suite=sid
> 
> ...
>dh_makeshlibs -a -O--no-parallel
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libsmithwaterman0/DEBIAN/symbols doesn't 
> match completely debian/libsmithwaterman0.symbols
> --- debian/libsmithwaterman0.symbols 
> (libsmithwaterman0_0.0+git20160702.2610e25-2_mips)
> +++ dpkg-gensymbolsKP3gJG 2018-04-12 08:49:24.980726993 +
> @@ -47,7 +47,7 @@
>   _ZN20CBandedSmithWatermanC2Ej@Base 0.0+git20160702.2610e25
>   _ZN20CBandedSmithWatermanD1Ev@Base 0.0+git20160702.2610e25
>   _ZN20CBandedSmithWatermanD2Ev@Base 0.0+git20160702.2610e25
> - _ZNKSt5ctypeIcE8do_widenEc@Base 0.0+git20160702.2610e25
> +#MISSING: 0.0+git20160702.2610e25-2# _ZNKSt5ctypeIcE8do_widenEc@Base 
> 0.0+git20160702.2610e25
>   _ZNSt6vectorI11IndelAlleleSaIS0_EE12emplace_backIJS0_EEEvDpOT_@Base 
> 0.0+git20160702.2610e25
>   
> _ZNSt6vectorI11IndelAlleleSaIS0_EE17_M_realloc_insertIJRKS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
>  0.0+git20160702.2610e25
>   
> _ZNSt6vectorI11IndelAlleleSaIS0_EE17_M_realloc_insertIJS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
>  0.0+git20160702.2610e25
> @@ -71,6 +71,7 @@
>   (arch=alpha armel armhf any-i386 mips mipsel s390x powerpc powerpcspe 
> ppc64)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
>  0.0+git20160702.2610e25
>   (arch=any-amd64 arm64 mips64el ppc64el hppa ia64 riscv64 sh4 sparc64 
> x32)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base
>  0.0+git20160702.2610e25
>   
> _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
>  0.0+git20160702.2610e25
> + 
> _ZSteqIcEN9__gnu_cxx11__enable_ifIXsrSt9__is_charIT_E7__valueEbE6__typeERKNSt7__cxx1112basic_stringIS3_St11char_traitsIS3_ESaIS3_EEESE_@Base
>  0.0+git20160702.2610e25-2
>   _ZeqRK11IndelAlleleS1_@Base 0.0+git20160702.2610e25
>   _ZlsRSoRK11IndelAllele@Base 0.0+git20160702.2610e25
>   _ZltRK11IndelAlleleS1_@Base 0.0+git20160702.2610e25
> dh_makeshlibs: failing due to earlier errors
> make: *** [debian/rules:8: binary-arch] Error 2
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#895531: Unable to import neuron in python3

[Johannes Hjorth]

package: python3-neuron 7.5-1


Unable to import neuron from python 3. See example below:?


$ python3
Python 3.6.5rc1 (default, Mar 14 2018, 06:54:23)
[GCC 7.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import neuron
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/neuron/__init__.py", line 114, in 

import nrn
ModuleNotFoundError: No module named 'nrn'
>>>

I am running Debian/testing.
Linux terpsichore 4.15.0-2-amd64 #1 SMP Debian 4.15.11-1 (2018-03-20) x86_64 
GNU/Linux

Bug#895532: linux-image-4.14.0-0.bpo.3-arm64: Enable CONFIG_SCSI_SYM53C8XX_2 for ARM64

[Ian Wienand]

Package: src:linux
Version: 4.14.13-1~bpo9+1
Severity: normal

Hi,

We seem to be missing the sym53c8xx module on arm64.  This means that
it is possible in some situations SCSI devices such as the cd-rom
drive can't be found -- this can be quite annoying on a
virtual-machine where this results in the config-drive not being
found, and cloud-init (or other tools) can't deploy keys and
configurations.

The Ubuntu 4.13.0-38-generic kernel does include this, and things work
as expected.  From the Ubuntu configs:

 config.common.amd64:CONFIG_SCSI_SYM53C8XX_2=m

An lspci on the affected host shows the controllers

 00:00.0 Host bridge: Red Hat, Inc. Device 0008
 00:01.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a
 00:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a
 00:03.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a

I think that clouds should be configured to show the cdrom via modern
methods such as virtio-scsi, etc.  But clearly some aren't, as I'm
seeing this problem on a deployed OpenStack instance.

Thus I think enabling this as a module will possibly help anyone
booting arm64 kvm hosts from nasty surprises where they can't get into
hosts (and also brings parity with ubuntu, which does seem work in the
same environment).

Thanks,

-i

-- Package-specific info:
** Version:
Linux version 4.14.0-0.bpo.3-arm64 (debian-ker...@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18)) #1 SMP Debian 4.14.13-1~bpo9+1 
(2018-01-14)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.14.0-0.bpo.3-arm64 root=LABEL=cloudimg-rootfs ro 
nofb nomodeset vga=normal console=tty0 console=ttyAMA0,115200 no_timer_check 
nofb nomodeset vga=normal

** Not tainted

** Kernel log:
[5.584275] python[365]: syscall 318
[5.584930] Code: aa0503e4 aa0603e5 aa0703e6 d401 (b13ffc1f) 
[5.585942] CPU: 2 PID: 365 Comm: python Not tainted 4.14.0-0.bpo.3-arm64 #1 
Debian 4.14.13-1~bpo9+1
[5.587497] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015
[5.588713] task: 8001f4b6f000 task.stack: 0c2c
[5.589765] PC is at 0x8fca0784
[5.590436] LR is at 0x8f815ec0
[5.591041] pc : [<8fca0784>] lr : [<8f815ec0>] pstate: 
6000
[5.592335] sp : e184e990
[5.592895] x29: e184e9d0 x28:  
[5.593780] x27:  x26: 8fe6b830 
[5.594681] x25: 8f853000 x24: 8fca0760 
[5.595595] x23:  x22: e184ea20 
[5.596481] x21: e184ea38 x20: e184ef00 
[5.597366] x19: 8f827000 x18: 0001 
[5.598262] x17: 8f815e5c x16: 8f8280f8 
[5.599164] x15: 076b89c0afadf41e x14: 0048 
[5.600090] x13: 0009 x12: c4a48db8 
[5.600979] x11: 0038 x10: 0101010101010101 
[5.601867] x9 : 0007 x8 : 013e 
[5.602763] x7 :  x6 :  
[5.603679] x5 :  x4 :  
[5.604567] x3 :  x2 : 0001 
[5.605453] x1 : 0001 x0 : 8fad6880 
[5.918196] 8021q: adding VLAN 0 to HW filter on device eth0

** Model information

** Loaded modules:
scsi_transport_spi
ip6t_REJECT
nf_reject_ipv6
nf_conntrack_ipv6
nf_defrag_ipv6
ip6table_filter
ip6_tables
ipt_REJECT
nf_reject_ipv4
nf_log_ipv4
nf_log_common
xt_LOG
xt_limit
nf_conntrack_ipv4
nf_defrag_ipv4
xt_tcpudp
xt_conntrack
nf_conntrack
libcrc32c
iptable_filter
nls_ascii
nls_cp437
vfat
fat
aes_ce_blk
crypto_simd
cryptd
efi_pstore
efivars
sg
aes_ce_cipher
ghash_ce
gf128mul
sha2_ce
sha256_arm64
evdev
sha1_ce
virtio_balloon
gpio_keys
ib_iser
rdma_cm
iw_cm
ib_cm
ib_core
configfs
iscsi_tcp
libiscsi_tcp
libiscsi
scsi_transport_iscsi
sr_mod
cdrom
8021q
garp
mrp
stp
llc
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
aes_arm64
sd_mod
virtio_scsi
scsi_mod
virtio_net
virtio_mmio
virtio_ring
virtio

** PCI devices:
00:00.0 Host bridge [0600]: Red Hat, Inc. QEMU PCIe Host bridge [1b36:0008]
Subsystem: Red Hat, Inc QEMU PCIe Host bridge [1af4:1100]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 
pn  firmware-linux-free  
pn  irqbalance   

Versions of packages linux-image-4.14.0-0.bpo.3-arm64 suggests:
pn  debian-kernel-handbook  
pn  linux-doc-4.14  

Versions of packages linux-image-4.14.0-0.bpo.3-arm64 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwl

Bug#895533: flite: don't run dh_auto_clean if configure has not run yet

[James Cowgill]

Source: flite
Version: 2.1-release-1
Severity: normal
Tags: patch

Hi,

flite FTBFS on riscv64:
https://buildd.debian.org/status/fetch.php?pkg=flite&arch=riscv64&ver=2.1-release-1&stamp=1522978424&raw=0

This happens because the main Makefile will always run configure if it
has not run yet and this will fail on new architectures if config.guess
has not been updated yet.

To resolve this, I think flite should only run dh_auto_clean if
config.log already exists.

After fixing this, I found that the clean target fails when run after
the build has completed with this error:
>dh_clean
> rm: cannot remove './doc/html': Is a directory

dh_clean will refuse to remove directories in debian/clean unless they
end with a trailing slash.

I've attached a patch which fixes both of these issues.

Thanks,
James
diff -Nru flite-2.1-release/debian/clean flite-2.1-release/debian/clean
--- flite-2.1-release/debian/clean  2018-01-03 20:07:27.0 +
+++ flite-2.1-release/debian/clean  2018-04-12 10:39:34.0 +0100
@@ -13,7 +13,7 @@
 doc/flite.toc
 doc/flite.tp
 doc/flite.vr
-doc/html
+doc/html/
 include/flite_version.h
 lib/
 main/flite_voice_list.c
diff -Nru flite-2.1-release/debian/rules flite-2.1-release/debian/rules
--- flite-2.1-release/debian/rules  2018-01-03 20:44:36.0 +
+++ flite-2.1-release/debian/rules  2018-04-12 10:39:34.0 +0100
@@ -17,6 +17,9 @@
 AUDIO=oss
 endif
 
+override_dh_auto_clean:
+   [ ! -f config.log ] || dh_auto_clean
+
 override_dh_auto_configure:
dh_auto_configure -- --with-audio=$(AUDIO) \
--with-vox=cmu_us_kal16 --enable-shared


signature.asc
Description: OpenPGP digital signature

Bug#895534: override: libgtkgl2.0-1:oldlibs/optional, libgtkgl2.0-dev:oldlibs/optional, libgtkglext1:oldlibs/optional, libgtkglext1-dev:oldlibs/optional, libgtkglext1-doc:oldlibs/optional, libgtkglext

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override

gtkglext is an unmaintained GTK+ 2 extension with OpenGL support,
superseded by the built-in GtkGLArea in GTK+ 3.16. It should not be used
in new code, and neither should its language bindings, some of which
are likely to be removed from Debian soon.

gtkgl2 is an independent implementation of more or less the same thing
(I think), again superseded by the built-in GtkGLArea in GTK+ 3.16
(which might even be based on the gtkgl2 code).

These packages have reverse-dependencies and so cannot be removed right
now, but they can at least move to oldlibs.

libgtkgl2.0-1:oldlibs/optional
libgtkgl2.0-dev:oldlibs/optional
libgtkglext1-dev:oldlibs/optional
libgtkglext1-doc:oldlibs/optional
libgtkglext1:oldlibs/optional
libgtkglextmm-x11-1.2-0v5:oldlibs/optional
libgtkglextmm-x11-1.2-dev:oldlibs/optional
python-gtkglext1:oldlibs/optional

Source packages: gtkgl2, gtkglext, gtkglextmm, python-gtkglext1

Thanks,
smcv

Bug#895535: override: libidl-2-0:oldlibs/optional, libidl-dev:oldlibs/optional, orbit2:oldlibs/optional, orbit2-nameserver:oldlibs/optional, liborbit2-dev:oldlibs/optional, liborbit-2-0:oldlibs/option

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override

ORBit2 is a CORBA implementation formerly used by GNOME and deprecated
in favour of D-Bus years ago. It is unmaintained upstream.

These packages have reverse-dependencies and so cannot be removed right
now, but they should move to oldlibs to indicate their deprecated status.

libidl-2-0:oldlibs/optional
libidl-dev:oldlibs/optional
orbit2:oldlibs/optional
orbit2-nameserver:oldlibs/optional
liborbit2-dev:oldlibs/optional
liborbit-2-0:oldlibs/optional
liborbit2:oldlibs/optional
python-pyorbit:oldlibs/optional
python-pyorbit-dev:oldlibs/optional
python-pyorbit-omg:oldlibs/optional

Source packages: orbit2, pyorbit, libidl

Thanks,
smcv

Bug#895536: override: python-poppler:oldlibs/optional

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override

python-poppler has been superseded by using gir1.2-poppler-0.18 via
GObject-Introspection.

As announced in [1] and [2] the GNOME team do not intend to release this
package in buster. However, it cannot yet be removed because packages
still depend on it. Please move it to oldlibs for now.

python-poppler:oldlibs/optional

Source package: python-poppler

Thanks,
smcv

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884935
[2] https://lists.debian.org/debian-devel/2017/10/msg00299.html

Bug#895537: stretch-pu: package libopenmpt/0.2.7386~beta20.3-3+deb9u3

[James Cowgill]

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

Hi,

This fixes CVE-2018-10017 which is a security bug tagged as "no-DSA" by
the security team.

The fix is quite simple and looks correct to me. I've done some testing
to make sure things still work after this update.

Thanks,
James

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

Kernel: Linux 4.15.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libopenmpt-0.2.7386~beta20.3/debian/changelog 
libopenmpt-0.2.7386~beta20.3/debian/changelog
--- libopenmpt-0.2.7386~beta20.3/debian/changelog   2017-07-15 
18:33:57.0 +0100
+++ libopenmpt-0.2.7386~beta20.3/debian/changelog   2018-04-12 
10:14:53.0 +0100
@@ -1,3 +1,10 @@
+libopenmpt (0.2.7386~beta20.3-3+deb9u3) stretch; urgency=medium
+
+  * Add patch to fix CVE-2018-10017 (Closes: #895406).
+- up11: Out-of-bounds read loading IT / MO3 files with many pattern loops.
+
+ -- James Cowgill   Thu, 12 Apr 2018 10:14:53 +0100
+
 libopenmpt (0.2.7386~beta20.3-3+deb9u2) stretch; urgency=medium
 
   * Add security patches (Closes: #867579).
diff -Nru libopenmpt-0.2.7386~beta20.3/debian/patches/series 
libopenmpt-0.2.7386~beta20.3/debian/patches/series
--- libopenmpt-0.2.7386~beta20.3/debian/patches/series  2017-07-15 
16:49:37.0 +0100
+++ libopenmpt-0.2.7386~beta20.3/debian/patches/series  2018-04-12 
10:13:10.0 +0100
@@ -6,3 +6,4 @@
 up6-invalid-memory-read-when-applying-nnas-to-effect-plugins.patch
 up8-out-of-bounds-read-plm.patch
 up10-heap-buffer-overflow-in-sample-loading-from-malformed-files-psm.patch
+up11-out-of-bounds-read-it-itp-mo3.patch
diff -Nru 
libopenmpt-0.2.7386~beta20.3/debian/patches/up11-out-of-bounds-read-it-itp-mo3.patch
 
libopenmpt-0.2.7386~beta20.3/debian/patches/up11-out-of-bounds-read-it-itp-mo3.patch
--- 
libopenmpt-0.2.7386~beta20.3/debian/patches/up11-out-of-bounds-read-it-itp-mo3.patch
1970-01-01 01:00:00.0 +0100
+++ 
libopenmpt-0.2.7386~beta20.3/debian/patches/up11-out-of-bounds-read-it-itp-mo3.patch
2018-04-12 10:14:53.0 +0100
@@ -0,0 +1,20 @@
+Description: Fix CVE-2018-10017
+ See 
https://lib.openmpt.org/libopenmpt/2018/04/08/security-updates-0.3.8-0.2-beta31-0.2.7561-beta20.5-p8-0.2.7386-beta20.3-p11/
+ Fix possible out-of-bounds memory read with IT and MO3 files containing many
+ nested pattern loops.
+Origin: upstream, 
https://source.openmpt.org/browse/openmpt?op=revision&rev=10042
+Bug-Debian: https://bugs.debian.org/895406
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/soundlib/Snd_fx.cpp
 b/soundlib/Snd_fx.cpp
+@@ -1042,7 +1042,8 @@ std::vector CSoundFile::G
+   if(GetType() == MOD_TYPE_IT)
+   {
+   // IT pattern loop start row update - at the 
end of a pattern loop, set pattern loop start to next row (for upcoming pattern 
loops with missing SB0)
+-  for(CHANNELINDEX nChn = 0; nChn < 
GetNumChannels(); nChn++)
++  pChn = memory.state.Chn;
++  for(CHANNELINDEX nChn = 0; nChn < 
GetNumChannels(); nChn++, pChn++)
+   {
+   if((pChn->rowCommand.command == 
CMD_S3MCMDEX && pChn->rowCommand.param >= 0xB1 && pChn->rowCommand.param <= 
0xBF))
+   {


signature.asc
Description: OpenPGP digital signature

Bug#895538: override: gir1.2-javascriptcoregtk-3.0:oldlibs/optional, gir1.2-webkit-3.0:oldlibs/optional, libjavascriptcoregtk-1.0-0:oldlibs/optional, libjavascriptcoregtk-1.0-dev:oldlibs/optional, lib

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override

src:webkitgtk has been superseded by src:webkit2gtk. Its C# bindings
src:webkit-sharp and src:webkitgtk-sharp3 have similarly been superseded
by src:webkit2-sharp.

As announced in [1] and [2] the GNOME team do not intend to release this
package in buster. However, it cannot yet be removed because packages
still depend on it. Please move it to oldlibs for now.

gir1.2-javascriptcoregtk-3.0:oldlibs/optional
gir1.2-webkit-3.0:oldlibs/optional
libjavascriptcoregtk-1.0-0:oldlibs/optional
libjavascriptcoregtk-1.0-dev:oldlibs/optional
libjavascriptcoregtk-3.0-0:oldlibs/optional
libjavascriptcoregtk-3.0-bin:oldlibs/optional
libjavascriptcoregtk-3.0-dev:oldlibs/optional
libwebkitgtk-1.0-0:oldlibs/optional
libwebkitgtk-3.0-0:oldlibs/optional
libwebkitgtk-3.0-dev:oldlibs/optional
libwebkitgtk-dev:oldlibs/optional
libwebkitgtk-doc:oldlibs/optional
libwebkit1.1-cil:oldlibs/optional
libwebkit-cil-dev:oldlibs/optional
libwebkitgtk3.0-cil:oldlibs/optional
libwebkitgtk3.0-cil-dev:oldlibs/optional

Source package: webkitgtk, webkit-sharp, webkitgtk-sharp3

Thanks,
smcv

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866671
[2] https://lists.debian.org/debian-devel/2017/10/msg00299.html

Bug#852170: [pkg-cinnamon] Bug#852170: cinnamon-control-center: Inconsistency in settings for Trackpad (edge-scrolling vs two-finger-scrolling)

[Maximiliano Curia]

¡Hola lopiuh!

El 2017-01-22 a las 11:31 +0100, lopiuh escribió:

Package: cinnamon-control-center
Version: 3.2.1-3
Severity: minor



setting  to true internaly turns  off. But 
 is being able to be true/enabled in the user interface.
Setting  off enables functionality of  
again.



I would expect, that  is disabled when  
is true. Otherwise UI tells something which is not done by the software.
On the other hand: If both is possible independently again in future we would 
have loss of functionality. Best would be, old behaviour would be restored,
that both features could exist next to each other independently.



https://ask.fedoraproject.org/en/question/89443/how-to-enable-touchpad-edge-scrolling/


With the release of cinnamon 3.4 this functionality was rewritten and it's now 
part of cinnamon-common (see cs_mouse.py). The scrolling methods are defined 
as:

clickpad_list = [[0, _("No scrolling")], [3, _("Automatic")], [1, _("Two-finger 
scrolling")], [2, _("Edge scrolling")]]
so you can choose either one or the other. I hope this fixes the issue you 
reported. As far as I understand this, libinput only allows either "Two-finger 
scrolling" or "Edge scrolling", while synaptics accepted switching them 
independently.


Happy hacking,
--
"Programs must be written for people to read, and only incidentally for 
machines to execute."

-- Hal Abelson, "Structure and Interpretation of Computer Programs"
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#886660: The agent doesn't start after upgrade from 1.0.12.2.dfsg-2

[mpho raffiki]

Hi Milan

The issue is that debian does not have the proper symbolic link of the
kernel device /dev/vport2p1. another issue for it not to work; is that when
you look at the device attributes for vport2p1 the attribute name is
something else under debian stretch (ATTR{name}=="ovirt-guest-agent.0" )

So to fix it you have to create a udev rule, i placed it under
/etc/udev/rules.d/10-vdsm.rules

--lines--
KERNEL=="vport2p1", SYMLINK+="virtio-ports/com.redhat.rhevm.vdsm"
--end-lines--

Regards,
mpho raffiki

Bug#895539: loook does not find document

[Hans-J. Ullrich]

Package: loook
Version: 0.8.5-1
Severity: important

Dear Maintainer,

I discovered a little bug in loook.

Description:

Starting loook and searching is working very well. It does find the documents 
correctly and shows the corret path to it. But when I doubleclick on the 
desired document, it starts libreofice, but then libreoffice mourns, it can not 
find the document (pop up window). Examining the pop-up-windows shows, 
libreoffice is correct: The path to the document is wrong.

For testing purposes I created a folder in my ~/home called "TEST" and copied 
an ODT-File with the content "Testfile12042018" and tbe name 
"testfile12042018.odt" to it. Then I let search loook for that string. The file 
was correctly found, but cannot opened. The error message is 
"/testfile12042018.odt can not be found", which is correct. The path should 
have been either "./TEST/testfile12042018.odt" or 
"/home/ullhan63/TEST/testfile12042018.odt".

Hope this helps. 

Thanks for looking reading this and looking at this bug. (Impressive, how 
speedy this application is!)

Best regards

Hans
  

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

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

Versions of packages loook depends on:
ii  python3 3.6.4-1
ii  python3-tk  3.6.5~rc1-1

Versions of packages loook recommends:
ii  libreoffice  1:6.0.2-1+b1

loook suggests no packages.

-- no debconf information

Bug#895540: nx-libs: FTBFS with parallel > 1 due to errors cleaning

[James Clarke]

Source: nx-libs
Version: 3.5.99.16-1
Severity: serious

Hi,
Currently, nx-libs FTBFS (likely only probabilistically) when built with
parallel > 1; this occurred on the ia64 buildd lenz[1], but I have
reproduced it locally in an amd64 cowbuilder chroot.

Please either fix the Makefile dependency issues, or disable parallel
cleaning.

Regards,
James

[1] 
https://buildd.debian.org/status/fetch.php?pkg=nx-libs&arch=ia64&ver=2%3A3.5.99.16-1%2Bb1&stamp=1523508333&raw=0

Bug#894965: dpkg-architecture should stop warning about unset CC

[Guillem Jover]

Control: forcemerge 644664 -1

[ More of a brain dump than anything else. ]

Hi,

On Thu, 2018-04-05 at 17:46:18 +0200, Helmut Grohne wrote:
> Package: dpkg-dev

> On Thu, Apr 05, 2018 at 04:28:48PM +0200, to...@tuxteam.de wrote:
> > - Need to set CC
> > 
> > Yes, the warning was clear enough, but I was a bit surprised
> > I had to set CC like so:
> 
> The warning you are talking about likely is this one:
> 
> | dpkg-architecture: warning: specified GNU system type $DEB_HOST_GNU_TYPE 
> does not match CC system type $DEB_BUILD_GNU_TYPE, try setting a correct CC 
> environment variable
> 
> I think this warning is obsolete as we assume that the packaging sets up
> CC. For most cases, it actually happens automatically:
>  * dh_auto_build passes it to make.
>  * If you include /usr/share/dpkg/buildtools.mk in debian/rules, it'll
>be correct.
>  * For many build systems, setting CC is not necessary and
>dh_auto_configure does the right thing anyway.
> 
> Telling the builder to set up CC is not needed at all, at least for 2000
> source packages and most of the failing ones don't fail due to missing
> CC.
> 
> Heck in many cases, I've seen and introduced workarounds like "CC=true
> dpkg-architecture ..." to make it stop being noisy.
> 
> Guillem, can we just remove the warning?

So the intention here has been, AFAICT, to try to make detecting
cross-building:

  1) kind of automatic, something just needs to set CC to the correct
 cross-toolchain and then dpkg would figure out the host arch.
  2) perform some kind of consistency and sanity check, to make
 sure the compiler architecture matches the one requested.

It is certainly true what you point out, and also that there are many
other compilers, so the relationship between a C compiler and the
resulting object installed might not match at all. Aslo even if dpkg
itself set those envvars, there is no guarantee the debian/rules would
use them. And I think the common way to request cross-compilation is
via the dpkg-buildpackage -a argument nowadays.

I guess given that cross-compilation has always been a bit rough on the
edges, there's not been a clear direction how to expose cross-building
interfaces until the above helpers gained support for it.

Removing the warning feels in a way like removing a safety check though,
because while doing dpkg-buildpackage -afoo will emit it and it will
be wrong, if the user specified an unmatched CC and -a, then bad
things can happen. But if people cross-building have gotten used to
ignore the warning anyway, then I'm not sure there's much point about
it anyway.

If we'd go with removing the warning, I'd also have to question whether
getting the architecture from CC or gcc is the correct thing to do, and
whether we should instead expect the user to supply the arch, and
simply validate that.


Something else that is related to this, and which I was pondering about
and was kind of a blocker for fixing this or not, was whether to make
dpkg-buildpackage set the buildtools variables itself, which would remove
the warning altogether. This was tied in with the thread on d-d about
the canonical entry point, and whether we'd still support debian/rules
as that user entry point.


Another option, that might be more robust, would be to add some checks
in dpkg somewhere, for whether the binary objects match the built
arch (this is partially done in dpkg-shlibdeps, but I don't think it's
complete or robust enough). This would of course trip over the abuse
done by multilib packages where the contained objects do not match the
.deb arch.

Thanks,
Guillem

Bug#895541: doc-rfc autopkgtest broken, fixed by using Ghostscript's ps2txt instead of unmaintained pstotext

[Till Kamppeter]

Package: doc-rfc
Version: 20170121-1
Severity: grave

Hi,

the autopkgtest of doc-rfc passes all PostScript files coming with the 
package through pstotext to check their integrity for use by dhelp which 
also uses pstotext.


pstotext stopped working with the recent update to Ghostscript 9.22. 
This is not only due to the deprecation of "-dDELAYBIND" in Ghostscript 
(which was withdrawn in 9.23) but also by an additional problem in 
Ghostscript.


As pstotext did not get maintained upstream for years it is better to 
drop it and replace it by the ps2txt utility of Ghostscript. ps2txt's 
compatibility with the Ghostscript it comes with is assured as they are 
maintained together.


pstotext is only used by dhelp, so to eliminate it from the distro it is 
enough to update the appropriate command lines in dhelp and in the 
doc-rfc package.


Attached is my change on the Ubuntu package of doc-rfc as a debdiff.

   Till
diff -Nru doc-rfc-20170121/debian/changelog doc-rfc-20170121/debian/changelog
--- doc-rfc-20170121/debian/changelog   2017-01-24 23:35:26.0 +0100
+++ doc-rfc-20170121/debian/changelog   2018-04-12 12:08:58.0 +0200
@@ -1,3 +1,12 @@
+doc-rfc (20170121-1ubuntu1) bionic; urgency=medium
+
+  * In the autopkgtest replaced the call of pstotext by ps2txt
+as pstotext upstream is unmaintained for years and stopped
+working with Ghostscript whereas ps2txt is part of ghostscript
+(LP: #1762778).
+
+ -- Till Kamppeter   Thu, 12 Apr 2018 12:08:58 +0200
+
 doc-rfc (20170121-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru doc-rfc-20170121/debian/tests/control 
doc-rfc-20170121/debian/tests/control
--- doc-rfc-20170121/debian/tests/control   2017-01-24 23:35:26.0 
+0100
+++ doc-rfc-20170121/debian/tests/control   2018-04-12 11:59:46.0 
+0200
@@ -1,2 +1,2 @@
 Tests: simple pspdf-parsing
-Depends: @, pstotext, poppler-utils, dhelp, lynx, libcgi-pm-perl
+Depends: @, ghostscript, poppler-utils, dhelp, lynx, libcgi-pm-perl
diff -Nru doc-rfc-20170121/debian/tests/pspdf-parsing 
doc-rfc-20170121/debian/tests/pspdf-parsing
--- doc-rfc-20170121/debian/tests/pspdf-parsing 2017-01-24 23:35:26.0 
+0100
+++ doc-rfc-20170121/debian/tests/pspdf-parsing 2018-04-12 12:08:58.0 
+0200
@@ -1,6 +1,6 @@
 #!/bin/bash
 
-echo "Tests that all files are parseable by p*totext,"
+echo "Tests that all files are parseable by p*t*xt,"
 echo "in order to suport dhelp integration."
 
 set -e
@@ -10,12 +10,12 @@
 
 for i in *.ps; do
   echo " - testing $i"
-  pstotext $i > /dev/null
+  ps2txt $i > /dev/null
 done
 
 for i in *.ps.gz; do
   echo " - testing $i"
-  zcat $i | pstotext > /dev/null
+  zcat $i | ps2txt > /dev/null
 done
 
 for i in *.pdf; do

Bug#895361: debirf: a system fails to boot: corrupted rootfs.cxz

[Tzafrir Cohen]

Update: a new version of the patch. It now works and supports all
compressors supported by busybox (I tried bzip2, gzip, lzma, lzop and
xz). lzma and xz fail. Others work.

-- 
Tzafrir Cohen | tzaf...@jabber.org | VIM is
http://tzafrir.org.il || a Mutt's
tzaf...@cohens.org.il ||  best
tzaf...@debian.org|| friend
>From ca9802d44611873eee35c42aeb2ea1f729a0d4dc Mon Sep 17 00:00:00 2001
From: Tzafrir Cohen 
Date: Tue, 10 Apr 2018 16:07:43 +0300
Subject: [PATCH] debirf: support different compressor for nested rootfs

Add configuration variable DEBIRF_COMPRESS, defaults to "xz".
May also be set to use any other similar compressor (tested with bzip2,
gzip, lzop and lzma). This is the compressor to use for the nested
rootfs.

For the sake of simplicity, the name of that file remains rootfs.cxz
regardless.

Gzip-compressed images are noticably larger (roughly 150% in my case).
However we had a case of an odd corruption of the xz image when the
compressor was xz (on one specific system, with an Atom D525 based Intel
board).
---
 debirf | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/debirf b/debirf
index 1e20c5c..bf380a3 100755
--- a/debirf
+++ b/debirf
@@ -39,6 +39,9 @@ STAGE_ROOT=${STAGE_ROOT:-true}
 STAGE_MODULES=${STAGE_MODULES:-true}
 STAGE_INITRD=${STAGE_INITRD:-true}
 
+# The compressor to use for the root filesystem archive:
+DEBIRF_COMPRESS=${DEBIRF_COMPRESS:-xz}
+
 # warn if running as root
 ROOT_WARNING=true
 
@@ -48,6 +51,7 @@ export DEVICE_ARCHIVE=${DEVICE_ARCHIVE:-/usr/share/debirf/devices.tar.gz}
 # default package include/excludes
 DEBIRF_DEFAULT_PACKAGES=${DEBIRF_DEFAULT_PACKAGES:-/usr/share/debirf/packages}
 
+
 ###
 ### FUNCTIONS
 
@@ -159,7 +163,7 @@ pack_rootfs() {
 
 # abort with a failure if our attempts to build the rootfs fail:
 set -o pipefail
-fakeroot_if_needed bash -c ". $DEBIRF_COMMON && FAKECHROOT_EXCLUDE_PATH=/does-not-exist debirf_exec sh -c 'find * | grep -v -e ^run/ | cpio --create -H newc'" | xz -9 > "$1"
+fakeroot_if_needed bash -c ". $DEBIRF_COMMON && FAKECHROOT_EXCLUDE_PATH=/does-not-exist debirf_exec sh -c 'find * | grep -v -e ^run/ | cpio --create -H newc'" | $DEBIRF_COMPRESS -9 > "$1"
 }
 export -f pack_rootfs
 
@@ -215,7 +219,7 @@ if (grep -q break=preunpack /proc/cmdline); then
 fi
 cd /newroot
 echo unpacking rootfs...
-unxz - < /rootfs.cxz | cpio -i
+$DEBIRF_COMPRESS -d - < /rootfs.cxz | cpio -i
 if (grep -q break=bottom /proc/cmdline); then
   echo "honoring break=bottom kernel arg"
   /bin/sh
-- 
2.11.0

Bug#895494: kimap FTBFS: symbol disappeared

[Lisandro Damián Nicanor Pérez Meyer]

Hi Adrian!

El jueves, 12 de abril de 2018 02:21:03 -03 Adrian Bunk escribió:
> Source: kimap
> Version: 17.12.3-1
> Severity: serious
[snip] 
> Why did kimap export a function from QByteArray()?

Not kimap but the compiler, which is free to add this kind of symbols and make 
them dissapear.  If you check the source code you will see that the symbol is 
not there. I think it's an inline.


-- 
If for every rule there is an exception, then we have established that there
is an exception to every rule.  If we accept "For every rule there is an
exception" as a rule, then we must concede that there may not be an exception
after all, since the rule states that there is always the possibility of
exception, and if we follow it to its logical end we must agree that there
can be an exception to the rule that for every rule there is an exception.
  Bill Boquist

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#895541: doc-rfc autopkgtest broken, fixed by using Ghostscript's ps2txt instead of unmaintained pstotext

[Iain Lane]

Control: severity -1 normal

On Thu, Apr 12, 2018 at 01:23:01PM +0200, Till Kamppeter wrote:
> Package: doc-rfc
> Version: 20170121-1
> Severity: grave

[ In Debian autopkgtest failures aren't RC bugs; downgrading ]

> pstotext stopped working with the recent update to Ghostscript 9.22. This is
> not only due to the deprecation of "-dDELAYBIND" in Ghostscript (which was
> withdrawn in 9.23) but also by an additional problem in Ghostscript.

I just wanted to say that I filed #895513 about pstotext being broken in
Debian. I agree with Till that moving to ghostscript's own
implementation is a sensible idea for you to do here.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


signature.asc
Description: PGP signature

Bug#895542: ITP: jsoneditor.js -- A web-based tool to view, edit, format, and validate JSON

[Joel Cross]

Package: wnpp
Severity: wishlist
Owner: Joel Cross 

* Package name: jsoneditor.js
  Version : 5.14.1
  Upstream Author : Jos de Jong 
* URL : https://github.com/josdejong/jsoneditor
* License : Apache-2.0
  Programming Lang: JavaScript
  Description : A web-based tool to view, edit, format, and validate JSON

 JSON Editor is a web-based tool to view, edit, format, and validate JSON. It
has various modes such as a tree editor, a code editor, and a plain text
editor. The editor can be used as a component in your own web application.
 .
 Supported browsers: Chrome, Firefox, Safari, Opera, Internet Explorer 9+.

This package is a dependency of swagger-ui (see #895422), which I am also
ITPing.

Bug#881564: Olimex Teres-I support

[Harald Geyer]

Hi,

looks like this bug is the inofficial "let's get debian working on
Teres-I" thread. So let me point here to
https://wiki.debian.org/InstallingDebianOn/Olimex/Teres-I
and invite you to contribute to that page if you have additional
experiences.

I think at this time we have everything necessary in debian except for
some u-boot patches to get simplefb up.

TIA,
Harald

Bug#894602: [dpkg] Strange cron error mails from executing /etc/cron.daily/dpkg

[Guillem Jover]

Hi!

On Mon, 2018-04-02 at 08:58:58 +0200, Dirk Heinrichs wrote:
> Package: dpkg
> Version: 1.18.24
> Severity: normal

> since a couple of days, I'm getting strange error mails from cron
> daemon with subject
> 
>   "Cron  test -x /usr/sbin/anacron || ( cd / && run-
> parts --report /etc/cron.daily )"
> 
> from some hosts. They're all related to executing /etc/cron.daily/dpkg
> but with slightly different content. One host even sends 2(!) mails.

> Here's the content:

> Host1:
> 
> /etc/cron.daily/dpkg:
> cp: cannot create regular file 'dpkg.status': File exists

This smells like a race condition, between logrotate and dpkg being
called and recreating the file before logrotate does. But I might be
wrong.

> mv: cannot move './/dpkg.status.5.gz' to './/dpkg.status.6.gz': No such
> file or directory
> mv: cannot move './/dpkg.status.4.gz' to './/dpkg.status.5.gz': No such
> file or directory
> mv: cannot move './/dpkg.status.3.gz' to './/dpkg.status.4.gz': No such
> file or directory
> mv: cannot move './/dpkg.status.2.gz' to './/dpkg.status.3.gz': No such
> file or directory
> mv: cannot move './/dpkg.status.1.gz' to './/dpkg.status.2.gz': No such
> file or directory

But I'm not sure why it would fail to move aside the one that I'd
expect had been moved before. I'd need to check logrotate's code.

[…]
> run-parts: /etc/cron.daily/logrotate exited with return code 1

> If I execute /etc/cron.daily/dpkg manually, it always finishes without
> error.

That's to be expected on normal conditions, yes. :)

> In case it matters, these hosts are setup as LXC-based OS containers
> running on libvirt. But I think I've seen these mails from physical
> hosts in the past as well.

Do you perhaps have something like unattended-ugrades or something
similar enabled on all those hosts?

Thanks,
Guillem

Bug#894441: dpkg-buildpackage: SOURCE_DATE_EPOCH must ignore bin-nmu changelog entries. Breaks M-A:same

[Julien Cristau]

Control: severity -1 wishlist

On 04/12/2018 02:10 PM, Guillem Jover wrote:

Control: reassign -1 buildd.debian.org

Hi!

On Thu, 2018-04-05 at 17:43:58 +0200, Jean-Michel Vourgère wrote:

On Friday, 30 March 2018 15:02:31 CEST Chris Lamb wrote:

[ https://lists.debian.org/debian-security/2017/05/msg00011.html ]


On Friday, 30 March 2018 20:15:33 CEST Sven Joachim wrote:

[ https://bugs.debian.org/843773 ]


Thanks a lot guys for pointing out that issue!

Basically, when doing bin-nmus, we really want to bump the mtime of the
distributed files. Not doing so results in some backups programs (rsync...) to
loose updates. Other programs restarting services on libraries updates
(needrestart...) would also be affected.


So, during compilation:
SOURCE_DATE_EPOCH must ignore bin-nmu changelog entries
because it breaks Multi-Arch:same on bin-nmu.

During dpkg-deb (:
SOURCE_DATE_EPOCH must *not* ignore bin-nmu changelog entries
because it would break software relying on files mtime.

Doh!

In https://bugs.debian.org/843773#75 Ian Jackson propose to introduce a
BUILD_DATE_EPOCH (= time of sbuild binnmu invocation) be prefered over
SOURCE_DATE_EPOCH by dpkg-deb.

That would work, wouldn't it?


Please, see my reply at . This is
really a fundamental problem with binNMUs+multiarch-refcounting or how
they are being issued. :)

Indeed.  I suspect eventually we'll make no-change sourceful uploads 
less labor intensive and binNMUs will go away, but we're not there right 
now.


Cheers,
Julien

Bug#894441: dpkg-buildpackage: SOURCE_DATE_EPOCH must ignore bin-nmu changelog entries. Breaks M-A:same

[Guillem Jover]

Control: reassign -1 buildd.debian.org

Hi!

On Thu, 2018-04-05 at 17:43:58 +0200, Jean-Michel Vourgère wrote:
> On Friday, 30 March 2018 15:02:31 CEST Chris Lamb wrote:
> > [ https://lists.debian.org/debian-security/2017/05/msg00011.html ]
> 
> On Friday, 30 March 2018 20:15:33 CEST Sven Joachim wrote:
> > [ https://bugs.debian.org/843773 ]
> 
> Thanks a lot guys for pointing out that issue!
> 
> Basically, when doing bin-nmus, we really want to bump the mtime of the 
> distributed files. Not doing so results in some backups programs (rsync...) 
> to 
> loose updates. Other programs restarting services on libraries updates 
> (needrestart...) would also be affected.
> 
> 
> So, during compilation:
> SOURCE_DATE_EPOCH must ignore bin-nmu changelog entries
> because it breaks Multi-Arch:same on bin-nmu.
> 
> During dpkg-deb (:
> SOURCE_DATE_EPOCH must *not* ignore bin-nmu changelog entries
> because it would break software relying on files mtime.
> 
> Doh!
> 
> In https://bugs.debian.org/843773#75 Ian Jackson propose to introduce a 
> BUILD_DATE_EPOCH (= time of sbuild binnmu invocation) be prefered over 
> SOURCE_DATE_EPOCH by dpkg-deb.
> 
> That would work, wouldn't it?

Please, see my reply at . This is
really a fundamental problem with binNMUs+multiarch-refcounting or how
they are being issued. :)

Thanks,
Guillem

Bug#895543: dhelp PostScript file display broken, fixed by using Ghostscript's ps2txt instead of unmaintained pstotext

[Till Kamppeter]

Package: dhelp
Version: 0.6.24

Hi,

dhelp uses pstotext to display PostScript files on a console or in a 
terminal.


pstotext stopped working with the recent update to Ghostscript 9.22. 
This is not only due to the deprecation of "-dDELAYBIND" in Ghostscript 
(which was withdrawn in 9.23) but also by an additional problem in 
Ghostscript.


As pstotext did not get maintained upstream for years it is better to 
drop it and replace it by the ps2txt utility of Ghostscript. ps2txt's 
compatibility with the Ghostscript it comes with is assured as they are 
maintained together.


pstotext is only used by dhelp, so to eliminate it from the distro it is 
enough to update the appropriate command lines in dhelp and the 
autopkgtest in the doc-rfc package (Debian bug #895541).


See also Debian bug #895513 about the pstotext issue.

Attached is my patch on the dhelp package as I have applied it in Ubuntu 
(0.6.24-0ubuntu1).


   Till
--- a/scripts/conv-pstotext
+++ b/scripts/conv-pstotext
@@ -6,7 +6,7 @@
 #
 # $1 = Input file, $2 = Output file
 
-2>/dev/null pstotext -output "${2}" "${1}"
+2>/dev/null ps2txt "${1}" "${2}"
 EXITVAL=$?
 if [ ${EXITVAL} -ne 0 ]; then
 	echo "Error converting file: ${1}"
--- a/src/dsearch
+++ b/src/dsearch
@@ -148,17 +148,17 @@
 $text = `/usr/bin/pdftotext "$file" -`;
 }
 else {
-# pstotext is a dependency, so this should never fail, but we
+# ghostscript is a dependency, so ps2txt should never fail, but we
 # recommend the user to install xpdf-utils instead, to get
 # pdftotext (better extraction quality and much faster)
-$text = file_to_text("/usr/bin/pstotext '$file'", "PDF", "xpdf-utils");
+$text = file_to_text("/usr/bin/ps2txt '$file'", "PDF", "xpdf-utils");
 }
 }
 elsif ($ext =~ /dvi/) {
 $text = file_to_text("/usr/bin/catdvi '$file'", "DVI", "catdvi");
 }
 elsif ($ext =~ /ps/) {
-$text = file_to_text("/usr/bin/pstotext '$file'", "Postscript", "pstotext");
+$text = file_to_text("/usr/bin/ps2txt '$file'", "Postscript", "ghostscript");
 }
 else {
 open F, $file;

Bug#895544: mirror listing update for mirror.serverius.net

[Merlijn de Leeuw]

Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: mirror.serverius.net
Type: leaf
Archive-architecture: amd64 arm64 armel armhf
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Merlijn de Leeuw 
Country: NL Netherlands
Location: Meppel
Sponsor: Serverius DataCenters https://serverius.net
Comment: 
 http://mirror.serverius.net/debian
 rsync://mirror.serverius.net/debian
 
 Archive:
 http://mirror.serverius.net/debian-cd
 rsync://mirror.serverius.net/debian-cd




Trace Url: http://mirror.serverius.net/debian/project/trace/
Trace Url: 
http://mirror.serverius.net/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirror.serverius.net/debian/project/trace/mirror.serverius.net

Bug#895546: uscan: Please make --safe the default

[Ian Jackson]

Package: devscripts
Version: 2.17.6+deb9u1~bpo8+1

Paul Wise writes on debian-devel:
> uscan is used in situations where one does not want arbitrary code
> from source packages automatically run by uscan. As long as `uscan
> --safe` ignores that fallback, that should be fine I guess though.

I wasn't aware of uscan --safe.

IMO `--safe' options are bad practice.  That should be the default.
`--unsafe' should be provided for when it is neeeded.  gs had -dSAFER
which caused many security bugs until eventually it was made the
default.

So the default in uscan should be changed.  Looking at the manual I
think it's possible that some of uscan's behaviours with --safe are
too conservative, but at the very minimum I would expect that by
default, uscan would:
 * not execute arbitrary code from the source package or the network
 * make only likely-to-be-relatively-harmless network connection attempts
   (so https to port 443 is probably OK; gopher to arbitrary ports is not)
 * avoid writing any files with unpredictable names (or names
   too-much-controlled by the source package or the network)

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.

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

Bug#895247: libgnomecanvas: Intent to Adopt

[Gert Wollny]

Hi Adrian, 

as the maintainer of amide[1], a package that depends on libgnomecanvas
I was also already thinking about adopting this package and libart-
lgpl. In other words I'd happily join to co-maintain these two
packages. 

Best, 
Gert 

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

Bug#895547: openssl: After symbol versioning, distributed pkgs are missing API symbols (e.g. EVP_PKEY_asn1_set_item)

[Nicola Tuveri]

Package: openssl
Version: 1.0.2l-1~bpo8+1
Severity: important
Tags: patch

Dear Maintainer,

I'm developing an ENGINE for OpenSSL, and close to release, I noticed
that in Ubuntu and in Debian the build fails with the following output:

```
/usr/bin/cc  -fPIC -g  -shared -Wl,-soname,liblibsuola.so -o liblibsuola.so 
CMakeFiles/suola.dir/suola.c.o CMakeFiles/suola.dir/suola_keypair.c.o 
CMakeFiles/suola.dir/debug/debug.c.o CMakeFiles/suola.dir/meths/X25519_meth.c.o 
CMakeFiles/suola.dir/meths/ed25519_meth.c.o 
CMakeFiles/suola.dir/meths/suola_asn1_meth.c.o 
CMakeFiles/suola.dir/meths/suola_md_identity_meth.c.o 
CMakeFiles/suola.dir/ossl/ossl_compat.c.o 
CMakeFiles/suola.dir/ossl/suola_err.c.o 
CMakeFiles/suola.dir/ossl/suola_objects.c.o 
CMakeFiles/suola.dir/providers/libsodium/base.c.o 
CMakeFiles/suola.dir/providers/libsodium/curve25519.c.o 
CMakeFiles/suola.dir/providers/libsodium/ed25519.c.o -lssl -lcrypto 
/opt/libsodium-stable/lib/libsodium.so -Wl,-z,defs 
-Wl,-rpath,/opt/libsodium-stable/lib:
CMakeFiles/suola.dir/meths/suola_asn1_meth.c.o: In function 
`suola_register_asn1_meth':
/usr/local/src/libsuola/meths/suola_asn1_meth.c:505: undefined reference to 
`EVP_PKEY_asn1_set_item'
collect2: error: ld returned 1 exit status
make[2]: *** [liblibsuola.so] Error 1
CMakeFiles/suola.dir/build.make:412: recipe for target 'liblibsuola.so' failed
make[2]: Leaving directory '/usr/local/src/libsuola/build'
make[1]: *** [CMakeFiles/suola.dir/all] Error 2
make: *** [all] Error 2
```

This does not happen linking against the same exact release of openssl
compiled from source on the same system.

I then learned that one of the patches applied by Debian (and included
by derived distributions) has the goal of versioning library symbols to
avoid conflicts.

Unfortunately said patch is not updated regularly with each release of
OpenSSL, resulting, like in my case, in symbols available in the public
header files but masked through versioning in the shared library binary.

The attached patch fixes my need by adding `EVP_PKEY_asn1_set_item` to
the list, but you might consider an internal review of your release
process to make sure that the list of symbols is updated whenever a new
upstream releases makes new functions publicly available.


I marked this bug as important, as it stops everyone using official
debian packages from using third-party ENGINEs that require to use that
function to set special handling of ASN.1 format, which basically
includes every ENGINE that would add support for cryptosystems that
upstream OpenSSL does not support (defying the purpose of using some
ENGINEs).

This covers my use case, but basically the package as is results
unusable to any user of any application that may require functions
available in the public headers but accidentally masked in the symbol
versioning step.


The ideal outcome of fixing this issue would consist in making the
versioning patch dynamic, checking when symbols are added (or removed)
in newer releases and updating the list accordingly.

The same versioning patch is applied in the other releases, so it's
worth tagging this bug also for those to make the handling of the
exposed symbols consistent.


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

Kernel: Linux 4.9.87-linuxkit-aufs (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages openssl depends on:
ii  libc62.19-18+deb8u10
ii  libssl1.0.0  1.0.2l-1~bpo8+1

openssl recommends no packages.

Versions of packages openssl suggests:
ii  ca-certificates  20141019+deb8u3

-- no debconf information
--- deb/openssl-1.0.2g/openssl.ld   2018-03-17 06:56:37.0 +
+++ deb-mod/openssl-1.0.2g/openssl.ld   2018-04-12 11:54:28.159985887 +
@@ -4615,6 +4615,7 @@

 OPENSSL_1.0.2g {
global:
+   EVP_PKEY_asn1_set_item;
SRP_VBASE_get1_by_user;
SRP_user_pwd_free;
 } OPENSSL_1.0.2;

Bug#895548: Sources are missing, contrary to lintian override comment

[Robie Basak]

Source: golang-github-smartystreets-goconvey
Version: 1.6.1-3
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic

debian/source/lintian-overrides says:

  ## False-positives, sources provided in "debian/missing-sources":

However there is no debian/missing-sources provided. So the following
appear to be accurate and currently have no source:

source-is-missing web/client/js/diff-match-patch.min.js
source-is-missing web/client/js/goconvey.gen.js source-is-missing
web/client/js/jquery-2_0_3.min.js source-is-missing
web/client/js/jquery.waypoints.sticky.min.js


signature.asc
Description: PGP signature

Bug#895549: cups-browsed: Legacy CUPS (1.5.x and before) broadcasted queues are ignored

[Amaury Pouly]

Package: cups-browsed
Version: 1.20.2-1
Severity: important

Dear Maintainer,

CUPS filters recently changed the way it detects CUPS raw queues [1]
by only relying on TXT fields of DNS-SD, which totally breaks legacy
CUPS (<=1.5.x) setup because those do not have a TXT record. This was
later fixed upstream [2,3] but leaves the current version in a broken
state because upstream has not made any point release for this fix. In
short, legacy CUPS printers are completely ignored by cups-browsed
1.20.2 and this is problematic because it is a common setup in
entreprise.

One possibility is to include [2] as a debian patch (it's very short)
or wait for a cups-filters upstream release 1.20.3.

[1] https://github.com/OpenPrinting/cups-filters/commit/d6323a81a00d8bf
90a636c9bbe9a177ced560d9a
[2] https://github.com/OpenPrinting/cups-filters/commit/9766ea347b351ae
403237f076ad085902eab6b85
[3] https://github.com/OpenPrinting/cups-filters/issues/34

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

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

Versions of packages cups-browsed depends on:
ii  cups-daemon   2.2.7-2
ii  libavahi-client3  0.7-3.1
ii  libavahi-common3  0.7-3.1
ii  libavahi-glib10.7-3.1
ii  libc6 2.27-3
ii  libcups2  2.2.7-2
ii  libcupsfilters1   1.20.2-1
ii  libglib2.0-0  2.56.1-1
ii  libldap-2.4-2 2.4.45+dfsg-1
ii  lsb-base  9.20170808

Versions of packages cups-browsed recommends:
ii  avahi-daemon  0.7-3.1

cups-browsed suggests no packages.

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

-- no debconf information

Bug#888968: unixODBC 2.3.6 prepared

[Hugh McMaster]

Control: tags 422207 + patch
Control: tags 675058 + patch
Control: tags 888968 + patch
Control: tags 891596 + patch
Control: tags 893891 + patch

Hi Steve,

I've prepared unixODBC 2.3.6 and uploaded it to d.mentors.
https://mentors.debian.net/debian/pool/main/u/unixodbc/unixodbc_2.3.6-0.1.dsc

I've given everything a massive overhaul, so this is definitely a maintainer 
release
(unless you want to ack the changes for a different sponsor).

Two things to note:
* This is an NMU release (2.3.6-0.1). So you will need to fix d/control.
* I've moved the Vcs-* fields to Salsa, using your username in the path.
The unixodbc repository doesn't exist yet, so it will need to be created.
(Let me know if you want me to host the repository.)

Hugh

unixodbc-debian.diff
Description: unixodbc-debian.diff

Bug#888968: unixODBC 2.3.6 prepared

[Hugh McMaster]

On Thursday, 12 April 2018 11:18 PM, Hugh McMaster wrote:
> * This is an NMU release (2.3.6-0.1). So you will need to fix d/control.

Sorry, that should say d/changelog.

Hugh

Bug#895385: Please build python3.x-dbg without using pymalloc to help detecting memory handling issues

[Balint Reczey]

Control: notfound -1 3.6.5-3

On Tue, 10 Apr 2018 22:43:38 +0200 Balint Reczey
 wrote:
...
> Dear Maintainers,
>
> Shipping the -dbg Python packages without using pymalloc and with
> -DPy_USING_MEMORY_DEBUGGER helped me in finding memory allocation
> issues easier in Python modules and I'm sure that would help others as
> well. I'm aware of the negative impact on the speed, but IMO for the
> -dbg packages slower execution would be acceptable.

As Julien pointed out to me recently |PYTHONMALLOC| [1] environment
variable can be used to use malloc instead of pymalloc and using it
makes Python Valgrind-friendly. This is a better solution than compiling
without pymalloc, thus I'm closing this bug.

Thanks,
Balint

[1] https://docs.python.org/3/using/cmdline.html#envvar-PYTHONMALLOC

Bug#895550: Cannot enable systemd units in a chroot

[Enrico Zini]

Package: ansible
Version: 2.5.0+dfsg-1
Severity: normal

Hello,

according to https://docs.ansible.com/ansible/latest/modules/systemd_module.html
it should be possible to run it in a chroot, as it says:

   Name of the service. When using in a chroot environment you always need to 
specify the full name i.e. (crond.service).

However, I have this:

 - name: enable systemd-networkd
   systemd:
 name: systemd-networkd.service
 enabled: yes

And I get this:

TASK [systemd : enable systemd-networkd]
***
fatal: [./chroot]: FAILED! => {"changed": false, "cmd": "/bin/systemctl", 
"msg": "Failed to connect to bus: No such file or directory", "rc": 1, 
"stderr": "Failed to connect to bus: No such file or directory\n", 
"stderr_lines": ["Failed to connect to bus: No such file or directory"], 
"stdout": "", "stdout_lines": []}
to retry, use: --limit 
@/home/enrico/lavori/truelite/system/live/chroot.retry

I am not sure whether to give up with this kind of setup over a chroot,
or whether the documentation is unclear/wrong, or wheter I'm doing
something wrong. Looking for the issue on the internet I find traces of
past issues with this that are all supposed to be resolved in this
version of ansible.


Enrico

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

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

Versions of packages ansible depends on:
ii  python2.7.14-4
ii  python-crypto 2.6.1-8
ii  python-cryptography   2.1.4-1
ii  python-httplib2   0.9.2+dfsg-1
ii  python-jinja2 2.10-1
ii  python-netaddr0.7.19-1
ii  python-paramiko   2.4.0-1
ii  python-pkg-resources  39.0.1-2
ii  python-yaml   3.12-1+b1

Versions of packages ansible recommends:
ii  python-jmespath   0.9.3-1
ii  python-kerberos   1.1.14-1
ii  python-libcloud   2.2.1-1
ii  python-selinux2.7-2+b2
pn  python-winrm  
ii  python-xmltodict  0.11.0-1

Versions of packages ansible suggests:
pn  cowsay   
pn  sshpass  

-- no debconf information

Bug#895549: cups-browsed: Legacy CUPS (1.5.x and before) broadcasted queues are ignored

[Till Kamppeter]

Released 1.20.3 upstream now, containing said fix:

https://github.com/OpenPrinting/cups-filters/releases/tag/release-1-20-3

Bug#895516: [Freewx-maint] Bug#895516: wxpython4.0 FTBFS: test failure

[Scott Talbert]

On Thu, 12 Apr 2018, Adrian Bunk wrote:


Source: wxpython4.0
Version: 4.0.1+dfsg-2
Severity: serious

Some recent change in unstable makes wxpython4.0 FTBFS:

I: pybuild base:217: easy_install -m -d 
/build/1st/wxpython4.0-4.0.1+dfsg/debian/tmp/usr/lib/python2.7/dist-packages -Z 
dist/*.egg
/bin/sh: 1: easy_install: not found


Yes, I noticed that.  For some reason Matthias removed easy_install in the 
latest version of python-setuptools.  I've got a query into him to ask why 
he did that.


Scott

Bug#833460: ITA open-cobol

[Ludwin Janvier]

retitle 833460 ITA: open-cobol -- cobol compiler
owner 833460 !
thanks

I'm working on packaging GnuCOBOL (ITP #892843) which is the new name for
this project.
Would need  a sponsor.

Bug#895551: haskell-gloss-rendering: upper bound on base older than ghc 8.2's

[Clint Adams]

Source: haskell-gloss-rendering
Version: 1.11.1.1-2
Severity: serious

https://github.com/Teaspot-Studio/gloss-rendering/issues/1

Bug#795244: ca-certificates-java.jar - String index out of range: -1

[Raphael Hertzog]

Hello,

On Wed, 12 Aug 2015, Christian Hammers wrote:
> It does not work though:
> 
> # java -Xmx64m -jar 
> /usr/share/ca-certificates-java/ca-certificates-java.jar -storepass changeit

That's because the program expects data on standard input. A list of
certificates to add (prefixed with "+") or remove (prefixed with "-").

I'm not sure that there's a real issue here.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

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

Bug#889968: RFS: inotify-tools/3.14-4

[Gianfranco Costamagna]

control: owner -1 !
control: tags -1 moreinfo

Hello Dmitry
sorry for taking too long for this one.
I did:
grab inotify-tools from experimental
grab the debian directory from the git repo, and debdiffed the results.
I'm worried about the disappear of "debian-changes" patch, is it somewhere 
else? should I get a new orig tarball?
I don't want my upload to make something disappear from the patch queue, due to 
my lack of dgit procedures.

Please tell me the commands to get the source in the right way(TM)
and then I'll look/sponsor if the patch has to disappear for some ways.
other things LGTM, the package builds in my pbuilder, and probably in ppas too.

Not sure why Sean has issues, I can't really reproduce them!

Gianfranco

Bug#879619: Autopkgtest for ncbi-tools6

[Liubov Chuprikova]

Hi Aaron,

On Thu, 5 Apr 2018 at 23:30 Aaron M. Ucko  wrote:

> Liubov Chuprikova  writes:
>
> > the same directory. What do you think about the whole test at this stage?
>
> Great, thanks!  I suppose you could check for specific output contents
> (via grep, not necessarily 100% identity), but this otherwise all looks
> good, and is a clear improvement over not having autopkgtests at all.
>

I have added simple checks for specific output content. What do you think
about my last commits? Is it an acceptable way to check or maybe you have
another idea how it should look like?

Apart from that, could you please help me with *taxblast*. I have tried to
run it providing SeqAnnot ASN.1 file as required. But I got the same error
message each time:

[taxblast] REJECT: Secure socket layer (SSL) has not been properly
initialized in the NCBI Toolkit.  Have you forgotten to call
SOCK_SetupSSL()?
[taxblast] ERROR: [URL_Connect;
https://www.ncbi.nlm.nih.gov:443/Service/dispd.cgi?service=TaxService&address=stretch.localdomain(127.0.1.1)&platform=LINUX
]  Failed to connect: Not supported
... (here the previous line repets)
[taxblast] ERROR: [HTTP;
https://www.ncbi.nlm.nih.gov/Service/dispd.cgi?service=TaxService&address=stretch.localdomain(127.0.1.1)&platform=LINUX
]  Too many failed attempts (3), giving up
[taxblast] ERROR: [TaxService]  Service not found
[taxblast] ERROR: [TaxService]  Cannot connect to service
[taxblast] ERROR: NI_ServiceGet [no error] ()

Do you have any suggestions what could be wrong with it?

Thank you,
Liubov

Bug#894441: dpkg-buildpackage: SOURCE_DATE_EPOCH must ignore bin-nmu changelog entries. Breaks M-A:same

[Holger Levsen]

On Thu, Apr 12, 2018 at 02:10:37PM +0200, Guillem Jover wrote:
> Please, see my reply at . This is
> really a fundamental problem with binNMUs+multiarch-refcounting or how
> they are being issued. :)

FWIW I totally agree with what you wrote there, just that I dont see
other people agreeing so sadly I currently don't see this fixed anytime
soon. Which is pretty sad.


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#895552: haskell-token-bucket: needs patching for newer base and time

[Clint Adams]

Source: haskell-token-bucket
Version: 0.1.0.1-5
Severity: serious

.

Bug#894965: dpkg-architecture should stop warning about unset CC

[Helmut Grohne]

On Thu, Apr 12, 2018 at 01:18:57PM +0200, Guillem Jover wrote:
> So the intention here has been, AFAICT, to try to make detecting
> cross-building:
> 
>   1) kind of automatic, something just needs to set CC to the correct
>  cross-toolchain and then dpkg would figure out the host arch.

That must have predated my involvement. Ever since I worked on cross
building the canonical way to specify the host architecture has been
through dpkg-architecture -a$arch.

>   2) perform some kind of consistency and sanity check, to make
>  sure the compiler architecture matches the one requested.

We don't even have widespread use of the CC variable. The clang people
essentially gave up on using it and simply divert gcc for their test
builds. Most of the working cross builds never set CC explicitly, but
the build system figures it out by other means (e.g. ./configure derives
it from $ac_tool_prefix, which comes from --host, which comes from
${DEB_HOST_GNU_TYPE}). In fact dpkg-architecture is happy with CC=true,
so any sanity check that is performed is not in fact sane.


> It is certainly true what you point out, and also that there are many
> other compilers, so the relationship between a C compiler and the
> resulting object installed might not match at all. Aslo even if dpkg
> itself set those envvars, there is no guarantee the debian/rules would
> use them. And I think the common way to request cross-compilation is
> via the dpkg-buildpackage -a argument nowadays.
> 
> I guess given that cross-compilation has always been a bit rough on the
> edges, there's not been a clear direction how to expose cross-building
> interfaces until the above helpers gained support for it.

I must have been late to the party to the point where dpkg-architecture
has become the defacto interface.

> Removing the warning feels in a way like removing a safety check though,
> because while doing dpkg-buildpackage -afoo will emit it and it will
> be wrong, if the user specified an unmatched CC and -a, then bad
> things can happen. But if people cross-building have gotten used to
> ignore the warning anyway, then I'm not sure there's much point about
> it anyway.

There is no safety gained through this warning. It is emitted in the
common case, often worked around, it's like an annoying popup and the
user is trained to ignore it.

> If we'd go with removing the warning, I'd also have to question whether
> getting the architecture from CC or gcc is the correct thing to do, and
> whether we should instead expect the user to supply the arch, and
> simply validate that.

I don't think setting the architecture from CC is a good idea. If you
cross build with clang, you set "CC=clang -target
x86_64-unknown-linux-gnu". How do you parse it then?

> Something else that is related to this, and which I was pondering about
> and was kind of a blocker for fixing this or not, was whether to make
> dpkg-buildpackage set the buildtools variables itself, which would remove
> the warning altogether. This was tied in with the thread on d-d about
> the canonical entry point, and whether we'd still support debian/rules
> as that user entry point.

We have around 2000 source packages that build without dpkg setting it.
I don't see a compelling reason to change that interface. The present
way works. You can "dpkg-architecture -a$somearch -c ./debian/rules
binary-arch" and expect it to work.

> Another option, that might be more robust, would be to add some checks
> in dpkg somewhere, for whether the binary objects match the built
> arch (this is partially done in dpkg-shlibdeps, but I don't think it's
> complete or robust enough). This would of course trip over the abuse
> done by multilib packages where the contained objects do not match the
> .deb arch.

In practise, dh_strip performs that check. Quite a number of debhelper
packages just build for the build architecture and fail dh_strip, so we
already have this sanity check for the vast majority of packages. My
cross buildd performs the validation outside the build and rarely
catches a non-debhelper package.

To me, all of this sounds like we should just remove this warning
immediately with no replacement. It does no good, only harm.

Helmut

Bug#895518: libsdl2-dev is not Multi-Arch compatible

[Felix Geyer]

Hi,


On 12.04.2018 11:28, Francois Gouget wrote:
> Package: libsdl2-dev
> Version: 2.0.8+dfsg1-1
> Severity: normal
>
> Dear Maintainer,
>
> The development package is not multiarch aware which causes the amd64
> version to conflict with the i386 one, thus making it impossible to
> install both.

libsdl2-dev itself is marked as Multi-Arch: same so it could be co-installed
across multiple architectures,
However some of its dependencies maybe not be co-installable breaking
this for libsdl2-dev.

This can't be fixed in the libsdl2 package.
Could you please file bugs against those package instead?
apt will tell you which package prevents the installation.

Felix

Bug#895362: Acknowledgement (Testing CD/DVD Missing algif_skcipher on Power64LE (so cannot use encrypted volumes))

[Matt Corallo]

Also missing at least the ecb module, which is needed to initialize the
xts mode to do a default encrypted-partition install.

On 04/10/18 11:00, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> You can follow progress on this Bug here: 895362: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895362.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Debian Kernel Team 
> 
> If you wish to submit further information on this problem, please
> send it to 895...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 

Bug#879619: Autopkgtest for ncbi-tools6

[Andreas Tille]

Hi Liubov,

On Thu, Apr 12, 2018 at 02:24:12PM +, Liubov Chuprikova wrote:
> >
> > Great, thanks!  I suppose you could check for specific output contents
> > (via grep, not necessarily 100% identity), but this otherwise all looks
> > good, and is a clear improvement over not having autopkgtests at all.
> >
> 
> I have added simple checks for specific output content. What do you think
> about my last commits? Is it an acceptable way to check or maybe you have
> another idea how it should look like?

Just from reading the shell script it looks fine.  Requiring bash is
also OK.
 
> Apart from that, could you please help me with *taxblast*. I have tried to
> run it providing SeqAnnot ASN.1 file as required. But I got the same error
> message each time:
> 
> [taxblast] REJECT: Secure socket layer (SSL) has not been properly
> initialized in the NCBI Toolkit.  Have you forgotten to call
> SOCK_SetupSSL()?
> [taxblast] ERROR: [URL_Connect;
> https://www.ncbi.nlm.nih.gov:443/Service/dispd.cgi?service=TaxService&address=stretch.localdomain(127.0.1.1)&platform=LINUX
> ]  Failed to connect: Not supported
> ... (here the previous line repets)
> [taxblast] ERROR: [HTTP;
> https://www.ncbi.nlm.nih.gov/Service/dispd.cgi?service=TaxService&address=stretch.localdomain(127.0.1.1)&platform=LINUX
> ]  Too many failed attempts (3), giving up
> [taxblast] ERROR: [TaxService]  Service not found
> [taxblast] ERROR: [TaxService]  Cannot connect to service
> [taxblast] ERROR: NI_ServiceGet [no error] ()
> 
> Do you have any suggestions what could be wrong with it?

I hope Aaron will give a more authoritative answer but when I'm reading
SSL I'm getting suspicious:  The test suite needs to be run in a machine
that is disconnected from the internet (similarly when the package is
build).

In some rules file this is somehow faked by using

  export http_proxy=http://127.0.0.1:9/

I'm absolutely not sure that this has any chance to work in the test
suite.  If the test needs network access to succeed than the only way is
to skip that test.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#895518: libsdl2-dev is not Multi-Arch compatible

[Francois Gouget]

Sorry, I mixed things up.

On Debian Testing libsdl2-dev (2.0.8+dfsg1-1) supports multiarch and 
it's libxkbcommon-dev that ruins it for everyone (see bug 893855).

But I'm also working on a Debian 9.4 VM and there libsdl2-dev 
2.0.5+dfsg1-2 does not support multiarch.

I got confused and thought both issues had the same source. So while I'd 
still really like libsdl2-dev to support multiarch in Debian Stable 
(because that's what people are told to use after all and it would be 
consistent with point 4 of the Social Contract[1]), I can understand 
if this bug gets closed.



[1] We will be guided by the needs of our users and the free software 
community. We will place their interests first in our priorities. We 
will support the needs of our users for operation in many different 
kinds of computing environments.
https://www.debian.org/social_contract

-- 
Francois Gouget   http://fgouget.free.fr/
Before you criticize someone, walk a mile in his shoes.
   That way, if he gets angry, he'll be a mile away - and barefoot.

Bug#513967:

[Jonas Smedegaard]

Excerpts from Vasyl Vavrychuk's message of april 12, 2018 9:54 am:
How about licensecheck detects pattern "See Copyright Notice at the 
end of this file" and goes LICENSECHECK_PARSELINES from the end to 
look for a license.


Heh - that's a clever idea.

I worry it might be too clever, though: It would complicate processing 
by needing to backtrack and rescan based on output of scanning.  Not 
very complicated but I would prefer to keep processing logic simple if 
possible.


Also, is it really needed? codesearch.debian.org has only ~100 hits for 
that pattern, and I believe licensecheck already by default checks at 
the end too.


Could you perhaps point at some real live examples where you believe 
this kind of mechanism would be useful?



Thanks,

- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

[x] quote me freely  [ ] ask before reusing  [ ] keep private


pgpnzytKSLOUb.pgp
Description: PGP signature

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

[Steve McIntyre]

[ Note cc to the d-efi list. SB is finally in progress after last
  week's sprint! ]

Very belated, it's time we discussed this.

On Tue, Apr 05, 2016 at 11:17:24AM -0700, Linn Crosetto wrote:
>Package: grub2
>Version: 2.02~beta2-36
>Severity: wishlist
>Tags: patch
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>The current code in 2.02~beta2-36 will silently fall back to calling
>ExitBootServices() and booting an unsigned kernel if signature verification
>fails.
>
>As a part of support for UEFI Secure Boot in Debian (820036) change the boot
>to fail if signature verification fails.
>
>I have attached a trivial patch for this change. Thanks!
>
>-BEGIN PGP SIGNATURE-
>Version: GnuPG v1
>
>iQIcBAEBAgAGBQJXBAE0AAoJEF/3aG7d/FTWDh4P/ja6Qa0JRr2bIDj+I+sihFmJ
>fIHVItLpMEU5hrKnpkRas7GflntzfpEObqUmzPLTRsrA1WobEyZDfNJUOonvEojR
>atccbvjShxNJIZFCr+W8mGh23+Xv+4VFVJ9f2jd+2sOlmViGyM88rDLOZN69vwIe
>9+GbTY6Ha3PifVDwLXvNH0cNiInt8uPbPnFOKwAcwSqFncyq5mfpCroLIqgfR5Dv
>ImROn7to4iurho3MOidJ0gRJm17mcPjzQAyX/Wh2asSiUMx2cIVrkfcSqoeb6W3L
>sXytfIwMf3YzY+eLEpsTZDYhmxrJGMa9uQ+Ryg1ZCQI0uI/n3We7cXnukofcM+Of
>sAtETJvr8SYrF5J/v7XafbEKXr64jV7wEEk97kDA+YGdw7nR1Y0UeX3W3AJCuOeo
>/KF75oIKJrYbRLymT701RwjArKD2wXYDTzmvnQKiTBc4sPofnr+nJIUOGvZ8Tn8O
>D/vI8PZKStsZ4cuABkiHEmA3y6zlVtJEkS+OGktNWrugNBJXGWHs6AHGjIIGenTQ
>8FPeNrC01DHf+170iV/0PXGLfJKn037y9JSDaZXuZkAsSrqmQENLKzOv9ee4QSsm
>UmalPiqKkyeZRQna7ZDK+LwB8yf02applIzsQcFuF/RahZdgLhwl42doC7LgjpYI
>wN0JD88AfHJAuUtwbpxc
>=fkO9
>-END PGP SIGNATURE-

>>From 52de74c85ef6a9aca426d9de8f188fe92241aff6 Mon Sep 17 00:00:00 2001
>From: Linn Crosetto 
>Date: Tue, 5 Apr 2016 11:49:05 -0600
>Subject: [PATCH] Disallow unsigned kernels if UEFI Secure Boot is enabled
>
>If UEFI Secure Boot is enabled and kernel signature verification fails, do not
>boot the kernel. Before this change, if kernel signature verification failed
>then GRUB would fall back to calling ExitBootServices() and continuing the
>boot.
>
>Patch-Name: linuxefi_disable_sb_fallback.patch
>
>Signed-off-by: Linn Crosetto 
>---
> grub-core/loader/i386/linux.c | 8 +++-
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
>diff --git a/grub-core/loader/i386/linux.c b/grub-core/loader/i386/linux.c
>index 2380642..e2e26dd 100644
>--- a/grub-core/loader/i386/linux.c
>+++ b/grub-core/loader/i386/linux.c
>@@ -696,10 +696,8 @@ grub_cmd_linux (grub_command_t cmd __attribute__ 
>((unused)),
>   using_linuxefi = 0;
>   if (grub_efi_secure_boot ())
> {
>-  /* Try linuxefi first, which will require a successful signature check
>-   and then hand over to the kernel without calling ExitBootServices.
>-   If that fails, however, fall back to calling ExitBootServices
>-   ourselves and then booting an unsigned kernel.  */
>+  /* linuxefi requires a successful signature check and then hand over
>+   to the kernel without calling ExitBootServices. */
>   grub_dl_t mod;
>   grub_command_t linuxefi_cmd;
> 
>@@ -721,7 +719,7 @@ grub_cmd_linux (grub_command_t cmd __attribute__ 
>((unused)),
> return GRUB_ERR_NONE;
>   }
> grub_dprintf ("linux", "linuxefi failed (%d)\n", grub_errno);
>-grub_errno = GRUB_ERR_NONE;
>+goto fail;
>   }
>   }
> }

This looks like one way of doing this. Philipp Hahn is suggesting that
we just don't include the "linux" module in our signed grub
build. That's simpler, but potentially causes problems elsewhere,
e.g. "it gets a bit nasty to try and dynamically switch between linux
and linuxefi in live-build". So, let's discuss - we need to agree our
policy and decide the best mechanism here. Go...!

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< liw> everything I know about UK hotels I learned from "Fawlty Towers"

Bug#872413: kpatch: Please package new upstream version

[Vincent Bernat]

severity 872413 serious
thanks

 ❦ 17 août 2017 10:21 +0200, Simon Ruderich  :

> Package: kpatch
> Version: 0.3.2-3.1
> Severity: normal
> Tags: patch
>
> Hello,
>
> The version of kpatch in Sid is quite old and doesn't work with
> the current kernel. Please consider updating to the latest
> upstream version. However it seems that 0.4.0 (latest release) is
> not recent enough, so consider using the latest Git version (e.g.
> 4b2f20e) which works fine me.

Hi!

As the package is not currently usable with our kernel, or even the
one in stable, I am bumping the severity. Since you already worked a
lot on this, would you be interested to prepare an upload for 0.5.0? If
yes, we could sort out how to organize that.
-- 
Parenthesise to avoid ambiguity.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#895555: golang-github-endophage-gotuf depends on cruft package

[peter green]

Package: golang-github-endophage-gotuf
Version: 0.0~git20151020.0.2df1c8e-1
Severity: serious

golang-github-endophage-gotuf depends on golang-go.crypto-dev which is no 
longer built by golang-go.crypto

Bug#895554: golang-github-bradfitz-http2-dev depends on cruft package

[peter green]

Package: golang-github-bradfitz-http2-dev
Version: 0.0~git20150509-2
Severity: serious

golang-github-bradfitz-http2-dev depends on golang-go.crypto-dev which is no 
longer built by golang-go.crypto

Bug#895553: sphinx: please make the set object description reproducible

[Chris Lamb]

Source: sphinx
Version: 1.6.7-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that sphinx could generates output that is not reproducible.

In particular, the rendering of `set` objects in default arguments
and elsewhere is currently non-determinstic. For example:

class A_Class(object):
a_set = {'a', 'b', 'c'}

Might be rendered as any of:

 {'a', 'b', 'c'}
 {'a', 'c', 'b'}
 {'b', 'a', 'c'}
 {'b', 'c', 'a'}
 {'c', 'a', 'b'}
 {'c', 'b', 'a'}

Patch attached that sorts the contents of sets whilst rendering.
This is parallel to the 'dict' key sorting.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/sphinx/util/inspect.py b/sphinx/util/inspect.py
index 7042253..774d21a 100644
--- a/sphinx/util/inspect.py
+++ b/sphinx/util/inspect.py
@@ -211,6 +211,10 @@ def object_description(object):
 else:
 items = ("%r: %r" % (key, object[key]) for key in sorted_keys)
 return "{%s}" % ", ".join(items)
+if isinstance(object, set):
+# Sort set contents
+template = "{%s}" if PY3 else "set([%s])"
+return template % ", ".join(repr(x) for x in sorted(object))
 try:
 s = repr(object)
 except Exception:
diff --git a/tests/test_util_inspect.py b/tests/test_util_inspect.py
index a463f4f..fe85419 100644
--- a/tests/test_util_inspect.py
+++ b/tests/test_util_inspect.py
@@ -138,6 +138,14 @@ class TestObjectDescription(TestCase):
 description = inspect.object_description(dictionary)
 assert description == "{'a': 1, 'b': 4, 'c': 3, 'd': 2}"
 
+def test_set_sorting(self):
+set_ = set("gfedcba")
+description = inspect.object_description(set_)
+if PY3:
+assert description == "{'a', 'b', 'c', 'd', 'e', 'f', 'g'}"
+else:
+assert description == "set(['a', 'b', 'c', 'd', 'e', 'f', 'g'])"
+
 def test_dict_customtype(self):
 class CustomType(object):
 def __init__(self, value):

Bug#895556: golang-github-influxdb-influxdb-dev depends on cruft package

[peter green]

Package: golang-github-influxdb-influxdb-dev
Version: 1.1.1+dfsg1-4
Severity: serious

golang-github-influxdb-influxdb-dev depends on golang-go.crypto-dev which is no 
longer built by golang-go.crypto

Bug#895224: pdf-presenter-console: [regression] after upgrading to GStreamer 1.14.0, fails to play movies

[Barak A. Pearlmutter]

Okay, I've opened an upstream issue for this.

I'm in the process of building a new package with the latest upstream
development branch merged, it will be 4.1-3, if you could install and
test this (or just rebuild it yourself; branch debian in the salsa
repo, already pushed) and let me know if there are any behavioural
changes, I'd very much appreciate it.

You should be able to build yourself with just:

$ dpkg-checkbuilddeps
$ sudo apt install ANYTHING-MISSING
$ fakeroot debian/rules binary

If that fails please send me a transcript and I'll see if we can't get
it ironed out.

It also might be helpful if you let us know if you're running under
Wayland; this is an easy way to check.

$ printenv | egrep WAY
WAYLAND_DISPLAY=wayland-0

Bug#890922: Confirmation of the bug

[Dominique MICOLLET (P)]

Dear Maintainer

I confirm the bug with the same device on the same distribution.

I can add that emulating a debian 8 distribution under qemu in a debian 
9 distribution allows to correctly interact with the scanner (at the 
price of a very low speed).


Sincerely yours.

Dominique MICOLLET

Bug#879619: Autopkgtest for ncbi-tools6

[Liubov Chuprikova]

On Thu, 12 Apr 2018 at 16:40 Andreas Tille  wrote:

>
> Just from reading the shell script it looks fine.  Requiring bash is
> also OK.
>

Ok, thanks!

SSL I'm getting suspicious:  The test suite needs to be run in a machine
> that is disconnected from the internet (similarly when the package is
> build).
>

Ops, it's escaped my attention somehow that tests are usually run on a
disconnected machine. I thought the opposite way.. Then I also need to
comment tests for *insdseqget* and *idfetch*.. Thank you for the
clarification!

With regards,
Liubov

Bug#895553: sphinx: please make the set object description reproducible

[Chris Lamb]

forwarded 895553 https://github.com/sphinx-doc/sphinx/pull/4834
thanks

I've forwarded this upstream here:

  https://github.com/sphinx-doc/sphinx/pull/4834


Regards,

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

Bug#895557: RFS: gnucobol/2.2-1 [ITA]

[Ludwin Janvier]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: gnucobol
   Version : 2.2-1
   Upstream Author : Simon Sobisch, Ron Norman, Edward Hart, Sergey
Kashyrin, Dave Pitts and Brian Tiffin
 * URL : https://www.gnu.org/software/gnucobol/
 * License : mostly GPL3 and LGPL2
   Section : devel

This package is orphaned in debian since almost 2 years. It is present
under the name "open-cobol", which was the project's name until 2013

The version in Debian stable/testing/unstable is 1.1, released in
2008, whereas this is the last major version: 2.2 (2017-10).


It builds those binary packages:

 gnucobol   - COBOL compiler
 libcob4- COBOL compiler - runtime library
 libcob4-dev - COBOL compiler - development files
 open-cobol - transitional dummy package for gnucobol

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/g/gnucobol/gnucobol_2.2-1.dsc



  Regards,
   Ludwin Janvier

Bug#879619: Autopkgtest for ncbi-tools6

[Aaron M. Ucko]

Liubov Chuprikova  writes:

> Ops, it's escaped my attention somehow that tests are usually run on a
> disconnected machine. I thought the opposite way.. Then I also need to
> comment tests for *insdseqget* and *idfetch*.. Thank you for the
> clarification!

That said, you did catch a bug in taxblast; I'll push a fix this
evening.  (The binary will still require a network connection, just
actually be able to use it now).

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#879619: Autopkgtest for ncbi-tools6

[Liubov Chuprikova]

On Thu, 12 Apr 2018 at 17:30 Aaron M. Ucko  wrote:

>
> That said, you did catch a bug in taxblast; I'll push a fix this
> evening.  (The binary will still require a network connection, just
> actually be able to use it now).
>

Ok, thank you!

With regards,
Liubov

Bug#891740: NMU upload

[Ole Streicher]

Hi,

I just uploaded a fixed package as NMU to DELAYED/5 and pushed the
changes to salsa. Please let me know if you want to have the upload
removed (and do it yourself), or if you need more time.

Best regards

Ole