Bug#893057: python3-notmuch: random aborts on exit

[Brian May]

David Bremner  writes:

> You hide the problem by adding
>
> del(db)
>
> at the end of your script.
>
> You can read some discussion at
>
> https://notmuchmail.org/pipermail/notmuch/2016/021622.html

Thanks for this, and the work around.

The workaround works fine.
-- 
Brian May 

Bug#893072: kexec-tools: use autotools-dev to update config.{sub,guess}

[YunQiang Su]

Package: src:kexec-tools
Version: 1:2.0.16-1
Control: blocks 893071

To build packages on some new ports, we need to update the config.{guess,sub}
files.

autotools-dev packages provides a way to archive this.

-- 
YunQiang Su

Bug#893071: kexec-tools: add some new mips architecutre to arch list or even use 'linux-any'

[YunQiang Su]

Package: src:kexec-tools
Version: 1:2.0.16-1

Please add
 mipsn32 mipsn32el mipsr6 mipsr6el mips64r6 mips64r6el mipsn32r6 mipsn32r6el
to the list of arch list.

Or maybe better, use linux-any.

-- 
YunQiang Su

Bug#806420: debian-edu: test suite times out on ci.debian.net

[Paul Gevers]

Hi,

On Fri, 27 Nov 2015 11:44:35 +0100 Petter Reinholdtsen 
wrote:
> [Antonio Terceiro]
> > I am blacklisting debian-edu for now, and will revisit that when this
> > bug is closed.
> 
> Sad to hear this.

As an encouragement for you to upload soon with my patch (or an improved
one skipping lots of tests), Antonio removed the blacklisting
yesterday¹, which is live as we speak.

Paul

¹
https://salsa.debian.org/ci-team/debci/commit/2d22046af8b0fc67a7ce35ce23c663737723953f



signature.asc
Description: OpenPGP digital signature

Bug#803526: scilab: NMU for switching to the default Tcl/Tk

[Sergei Golovan]

Source: scilab
Version: 6.0.1-1
Followup-For: Bug #803526
Control: severity -1 important
Control: tags -1 + patch

Dear Maintainer,

Tcl/Tk 8.5 is planned to be removed from Debian before the buster's release,
so please, switch to the newer Tcl/Tk. I'd like to propose a very short patch
for that (just replace tcl8.5-dev, tk8.5-dev by tcl-dev, tk-dev in build
dependencies), and could do NMU if it's appropriate.

-- System Information:
Debian Release: 9.4
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500, 
'stable'), (500, 'oldstable'), (1, 'experimental'), (1, 'unstable'), (1, 
'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru scilab-6.0.1/debian/changelog scilab-6.0.1/debian/changelog
--- scilab-6.0.1/debian/changelog   2018-02-26 15:32:37.0 +0300
+++ scilab-6.0.1/debian/changelog   2018-03-15 22:42:45.0 +0300
@@ -1,3 +1,10 @@
+scilab (6.0.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to the default Tcl/Tk version from deprecated Tcl/Tk 8.5.
+
+ -- Sergei Golovan   Thu, 15 Mar 2018 22:42:45 +0300
+
 scilab (6.0.1-1) unstable; urgency=medium
 
   * Formally adopting the package (Closes: #744140).
diff -Nru scilab-6.0.1/debian/control scilab-6.0.1/debian/control
--- scilab-6.0.1/debian/control 2018-02-26 15:32:37.0 +0300
+++ scilab-6.0.1/debian/control 2018-03-15 22:42:45.0 +0300
@@ -5,7 +5,7 @@
 Uploaders: Julien Puydt 
 Build-Depends: cdbs, debhelper (>= 10), gfortran,
  default-jdk, chrpath, ocaml-nox (>= 3.11.2-3), fakeroot,
- tcl8.5-dev, tk8.5-dev, libxml2-dev, libpcre3-dev, libcurl4-openssl-dev,
+ tcl-dev, tk-dev, libxml2-dev, libpcre3-dev, libcurl4-openssl-dev,
  gettext, libreadline-dev, pkg-config, procps, dpkg-dev (>= 1.16.0),
 # numerical libraries
  libblas-dev | librefblas3-dev | libatlas-base-dev, liblapack-dev,

Bug#893070: RFP: libff -- C++ library for Finite Fields and Elliptic Curves

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: libff
  Version : 1?
  Upstream Author : SCIPR Lab
* URL : https://github.com/scipr-lab/libff/
* License : MIT
  Programming Lang: C++
  Description : Library for Finite Fields and Elliptic Curves

Includes implemented fields and elliptic curve groups. Provides three
snark options - edwards ( an instantiation based on an Edwards curve),
bn128 ( an instantiation based on a Barreto-Naehrig curve) and alt_bn128
( an alternative to bn128 ).

Bug#893069: new upstream (4.2.4)

[Daniel Baumann]

Package: samhain

Hi,

it would be nice if you could upgrade the package to the current
upstream version (4.2.4).

Regards,
Daniel

Bug#893068: net-tools documentation should reccomend iproute2

[=]

Package: net-tools
Version: 1.60+git20161116.90da8a0-1
Severity: minor

Dear Maintainer,

linux net-tools has been abandonned by upstream, and its structure is subtly
incompatible with the linux network stack (since kernel 2.4)

probably the documentation should point users to the iproute2 tools ss(8) and
ip(8) in the see-also section of the mang pages if not more prominantly.


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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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



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

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

Versions of packages net-tools depends on:
ii  libc62.24-11+deb9u3
ii  libselinux1  2.6-3+b3

net-tools recommends no packages.

net-tools suggests no packages.

-- debconf-show failed

Bug#872864: Checkout upstream signatures as well when using pristine-tar

[Georg Faerber]

Hi all,

Anything one could do to get this implemented?

Thanks for your work,
cheers,
Georg


signature.asc
Description: Digital signature

Bug#889668: Please install fstrim.timer (but disabled!)

[Christoph Anton Mitterer]

Hey.

Just adding my 2 cents on this.

As cruncher already noted, TRIM/discard may have an influence on the
security of encrypted devices.
But... per default, dm-crypt (respectively cryptsetup) sets the devices
to ignore any trim commands and not pass it down to lower layers (
--allow-discards option).


However, even apart from that I think this should never be enabled by
default:
- If a fs properly supports discard, it will anyway has its own mount
options for controlling it an there should be no need to call fstrim

- Calling trim typically means the data is gone (or at least not easily
accessible anymore)... while this is intended of of course, it may have
disadvantages e.g. in case of fs corruption, non-discarded areas could
still be recovered (even if it may be some tough work).
Also, calling fstrim for *any* filesystem per default is IMO a bad
thing. Users may have e.g. external HDDs connected (which shouldn't be
trimmed, maybe because they're very large) or filesystems mounted for
which recovery or forensic analysis is to be done.


Cheers,
Chris.

Bug#893067: libinput-dev: pkg-config file does not work without libwacom-dev installed

[Daniel Schepler]

Package: libinput-dev
Version: 1.10.3-1
Severity: important
Justification: causing numerous new FTBFS bugs

In a clean pbuilder chroot:

# apt install libinput-dev pkg-config
# pkg-config --cflags libinput
Package libwacom was not found in the pkg-config search path.
Perhaps you should add the directory containing 'libwacom.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libwacom', required by 'libinput', not found
# pkg-config --exists libinput
# echo $?
1

I've been seeing several new FTBFS issues in other packages due to
this, either due to configure scripts erroring out when they find
libinput "does not exist", or in the case of qtbase-opensource-src,
the configuration leaves out the libinput plugin which then causes an
error at dh_install time.
-- 
Daniel

Bug#892591: RFS: pinball/0.3.1-14 [ITA]

[Adam Borowski]

On Sun, Mar 11, 2018 at 09:16:13AM +0100, Innocent De Marchi wrote:
>  * Package name: pinball
>Version : 0.3.1-14

>   Changes since the last upload:
> 
>   * New Maintainer (Closes: #891762).
>   * Set Rules-Requires-Root: binary-targets.
>   * Added homepage field on debian/control.
>   * Added description on some patch files.
>   * Fix spelling error in patch description on 06_missing_cstddef.patch
> file.
>   * Removed patch file not-mentioned in series:
> replace-sp-with-opensp.patch.
>   * Added hardering flags on debian/rules.
>   * Removed and rewrite 03_desktop.patch file.
>   * Removed pinball.menu file.
>   * Added secure URI on debian/watch.
>   * Completed rewrite debian/copyright file.
>   * Changed negated list of architectures by dpkg architecture
> wildcards. Thanks to Robert Millan (Closes: #634705).
>   * Close old fix bug (Closes: #642477).

This is irrelevant to the version you're uploading, so there's no point in
claiming it's a change done right now.

You can instead send any mail to 642477-d...@bugs.debian.org; preferably
with the first line being:
Version: 0.3.1-13.1
so the BTS knows what versions the bug applies to.

>   * Adds OpenGL constraint on debian/control. Thanks to Yann Dirson
> (Closes: #150082).
>   * Added one new patch (pinball-cpp) to close more bugs
> (Closes: #555251, #555256, #450763, #858627).

But _what_ does this patch fix?

I see that it squashes a bunch of unrelated changes.  This is not nice but
might be acceptable if the changes are somewhat entangled and it would cost
you too much work to separate them.  Yet even then, the bugs are unrelated.

It's not the act of adding a patch that's interesting, what an user or an
contributor would want to know is: "this breakage has been dealt with".

>   * Addet on new patch (menu-cpp) to activate left Alt
> key to close program (Closes: #442809).
>   * Changed the storage directory of the high scores (new patch
> table-cpp).
>   * Added one new patch (add-autor-to-AUTHORS) to add author name on
> upstream AUTHORS file (it was empty).

Patch file names are probably superfluous -- if someone wants to dig that
deeply, it's trivial to find that part.

> I have not updated the standard version: with debhelper> 9, the
> compilation fails due to the libtoolize system. I think we have to do a
> deep update of this issue.

Debhelper in no case checks standards-version, it's all about compat level.

libtool failing is quite nasty: it means the package uses shipped outdated
autoconfage, which, among other possible problems, will cause build failure
when a new architecture is added.  But it's not an immediate problem: you
don't need to fix every bug in your first update.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.

Bug#893066: python3-zaqar-ui: fails to upgrade from 'testing' - trying to overwrite /usr/share/openstack-dashboard/openstack_dashboard/enabled/_1510_project_messaging_group.py

[Andreas Beckmann]

Package: python3-zaqar-ui
Version: 4.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package python3-zaqar-ui.
  Preparing to unpack .../16-python3-zaqar-ui_4.0.0-1_all.deb ...
  Unpacking python3-zaqar-ui (4.0.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-RfrGCs/16-python3-zaqar-ui_4.0.0-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/openstack-dashboard/openstack_dashboard/enabled/_1510_project_messaging_group.py',
 which is also in package python-zaqar-ui 1.0.0~rc1-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-RfrGCs/16-python3-zaqar-ui_4.0.0-1_all.deb


cheers,

Andreas


python-zaqar-ui=1.0.0~rc1-2_python3-zaqar-ui=4.0.0-1.log.gz
Description: application/gzip

Bug#893049: libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed

[Chris Lamb]

tags 893049 + pending
thanks

[Adding albert...@blitiri.com.ar to CC]

> https://buildd.debian.org/status/package.php?p=libfiu=sid
> 
> ...
> ./generate-test -c tests/malloc.conf -o tests/malloc.c
> make[4]: Leaving directory '/<>/tests/generated'
> make[4]: Entering directory '/<>/tests/utils'
> LD_LIBRARY_PATH=../../libfiu/ ./test-basic_ctrl.py > 
> output-test-basic_ctrl.py.txt 2>&1
> Makefile:38: recipe for target 'run-test-basic_ctrl.py' failed
> make[4]: *** [run-test-basic_ctrl.py] Error 1

Adrian, I've fixed this in Git, pending upload:

  
https://github.com/lamby/pkg-libfiu/commit/55bcc37af0b142ddd4e121802df8ebb45e723d9e

Alberto, do you know why this is now required? (Feel free to take
the patch upstream, naturally...)


Regards,

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

Bug#886045: stardict: Raising severity of libgnome rdepends bug

[Jeremy Bicha]

Control: severity -1 serious

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. As part of this process, I
am now raising the severity of this bug.

stardict-gnome depends on multiple libraries being removed:
gconf2, gconf-service, libart-2.0-2, libbonobo2-0, libbonoboui2-0,
libgnome-2-0, libgnomecanvs2-0, libgnomeui-0, libgnomevfs2-0

You might be able to just stop building stardict-gnome and use
stardict-gtk instead. Be sure to not Build-Depend on those libraries
either.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#893065: ironic-inspector: fails to install: ironic-inspector-dbsync: not found

[Andreas Beckmann]

Package: ironic-inspector
Version: 7.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ironic-inspector.
  (Reading database ... 
(Reading database ... 16191 files and directories currently installed.)
  Preparing to unpack .../ironic-inspector_7.2.0-2_all.deb ...
  Unpacking ironic-inspector (7.2.0-2) ...
  Setting up ironic-inspector (7.2.0-2) ...
  sh: 1: ironic-inspector-dbsync: not found
  dpkg: error processing package ironic-inspector (--configure):
   installed ironic-inspector package post-installation script subprocess 
returned error exit status 127
  Errors were encountered while processing:


cheers,

Andreas


ironic-inspector_7.2.0-2.log.gz
Description: application/gzip

Bug#892956: libinput-dev: Requires.private without package dependencies breaks pkg-config users

[Jeremy Bicha]

By the way, meson's error message for this situation was very unhelpful.

See https://bugzilla.gnome.org/794313 where gnome-bluetooth was
affected. (I simply added the extra dependencies to the Debian package
once I figured out what happened.)

Thanks,
Jeremy Bicha

Bug#893064: gettext: Please complete support for DEB_BUILD_PROFILES="nojava"

[Manuel A. Fernandez Montecelo]

Source: gettext
Version: 0.19.8.1-4
Severity: wishlist
Tags: patch
User: debian-ri...@lists.debian.org
Usertags: riscv64

Hi Santiago!

When bootstrapping the riscv64 architecture we stumbled upon gettext for a
moment, because no Java SDK is available yet.

I found that the support to avoid compiling using Java dependencies was almost
there by using the "stage1" profile, and it allowed us to progress.

Still, I think that it could use some improvements to gain full support, so I
propose to include the changes in the patch attached, that are only a couple of
small but important things:

- annotating the Build-Depends in d/control with profiles

  dpkg-buildpackage and other tools know how to ignore them when building using
  these profiles, so this makes possible to not have to force to build without
  those dependencies installed (-d option in dpkg-buildpackage)

- change the name from "stage1", which is deprecated, to "nojava"

  https://wiki.debian.org/BuildProfileSpec#Registered_profile_names

  As the URL above explains, "stage1" is deprecated, and by using "nojava" one
  can use a single global profile name for many packages, when one doesn't have
  (or doesn't want to use) a Java SDK to build support.


I hope that you find it useful and worth enough to include it :)


Cheers.
--
Manuel A. Fernandez Montecelo 
>From 6649d4117ce3a64ce550d702a93a8d9c5fdc48ed Mon Sep 17 00:00:00 2001
From: "Manuel A. Fernandez Montecelo" 
Date: Fri, 16 Mar 2018 02:13:59 +0100
Subject: [PATCH] Add support for DEB_BUILD_PROFILES="nojava", replace "stage1"

---
 debian/changelog | 13 +
 debian/control   |  2 +-
 debian/rules |  4 ++--
 3 files changed, 16 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 84b6bb2..36ebc77 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+gettext (0.19.8.1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add support for DEB_BUILD_PROFILES="nojava", replace "stage1"
+(Closes: #-1)
+- Replace "stage1" with "nojava" in d/rules, since "stage1" is only
+  about Java support and deprecated, and "nojava" is one of the standard
+  profiles
+- Annotate Java-related build-dependencies in d/control to avoid them
+  when using the new profile
+
+ -- Manuel A. Fernandez Montecelo   Fri, 16 Mar 2018 01:50:02 
+0100
+
 gettext (0.19.8.1-4) unstable; urgency=medium
 
   * Avoid extraneous NUL bytes in .mo files. Closes: #872869.
diff --git a/debian/control b/debian/control
index 79744b4..d4e4dbc 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: devel
 Priority: optional
 Maintainer: Santiago Vila 
 Standards-Version: 3.9.6
-Build-Depends: g++ (>= 4:7), debhelper (>= 9), fastjar, default-jdk, file, 
libncurses5-dev, libxml2-dev, libglib2.0-dev, libcroco3-dev, xz-utils, 
libunistring-dev
+Build-Depends: g++ (>= 4:7), debhelper (>= 9), fastjar , default-jdk 
, file, libncurses5-dev, libxml2-dev, libglib2.0-dev, libcroco3-dev, 
xz-utils, libunistring-dev
 Homepage: http://www.gnu.org/software/gettext/
 
 Package: gettext-base
diff --git a/debian/rules b/debian/rules
index d78afb6..2036bd1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -115,7 +115,7 @@ gettext-base: build
fi
find debian/$@/usr/share/locale | grep gettext-tools | xargs rm
 ifeq (,$(findstring %$(DEB_HOST_ARCH)%,$(NOJAVA_ARCHS)))
-ifeq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
+ifeq ($(filter nojava,$(DEB_BUILD_PROFILES)),)
install -d debian/$@/usr/share/java
cp -p debian/tmp/usr/share/gettext/libintl.jar \
debian/$@/usr/share/java
@@ -134,7 +134,7 @@ gettext: build
cp -a debian/tmp/usr/share/gettext* debian/$@/usr/share
rm -f debian/$@/usr/share/gettext/libintl.jar
 ifeq (,$(findstring %$(DEB_HOST_ARCH)%,$(NOJAVA_ARCHS)))
-ifeq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
+ifeq ($(filter nojava,$(DEB_BUILD_PROFILES)),)
mv debian/$@/usr/share/gettext/gettext.jar debian/$@/usr/share/java
 endif
 endif
-- 
2.16.2

Bug#892905: lintian: pkg-doc examples need not reside under /usr/share/doc/pkg-doc/

[Chris Lamb]

tags 892905 + pending
thanks

Thanks Ferenc.  Fixed in Git, pending upload:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=7f31cecc92b013987d1e0aa746e271f4630878b8


Regards,

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

Bug#726530: FvwmPager segfaults

[Jaimos Skriletz]

On Tue, 6 Mar 2018 09:18:32 +0100 Oleg Broytman  wrote:
> FvwmPager still segfaults after I upgraded to stretch. Less frequently
> maybe.
>

Is FvwmPager the only thing that is crashing in the stretch version?
As in does fvwm no longer segfault any more in your setup? If so I
think some of the changes in the current version of fvwm have fixed
the original bug report. If that is the case I would like to close
this bug report, and a separate one should be opened for FvwmIconMan
crashing.

I have tried to reproduce this crash with the current version of fvwm
and FvwmIconMan using the character set ru_RU.KOI8-R (I think that is
the one you said caused the problems) in a VM and I am unable to crash
fvwm. So I am going to go with the original and old bug of fvwm
segfaulting is no longer happening. As for FvwmIconMan, if you open a
new bug for that, please provide more info than you have. A core dump
will be useful.

thanks,

jaimos

Bug#893063: O: jetring -- gpg keyring maintenance using changesets

[Giovani Augusto Ferreira]

Package: wnpp
Severity: normal

I intend to orphan the jetring package.

The package description is:
 jetring is a collection of tools that allow for gpg keyrings to be maintained
 using changesets. It was developed with the Debian keyring in mind, and aims
 to solve the problem that a gpg keyring is a binary blob that's hard for
 multiple people to collaboratively edit.
 .
 With jetring, changesets can be submitted, reviewed to see exactly what they
 will do, applied, and used to build a keyring. The origin of every change
 made to the keyring is available for auditing, and gpg signatures can be used
 to further secure things.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Regards,

Giovani

Bug#893057: python3-notmuch: random aborts on exit

[David Bremner]

Brian May  writes:
> === cut ===
>
> I get the following output:
>
> brian@wspdigital:~$ /usr/bin/python3 ./tagmail
> Aborted
>
> If I comment/remove any of the lines out (including the function that isn't
> even referenced anywhere) or switch to Python2, then it works without any
> problems.
>
> Am wondering if this is a Python3 bug.

I suspect it has to do with changes in memory management in python3.

You hide the problem by adding

del(db)

at the end of your script.

You can read some discussion at

https://notmuchmail.org/pipermail/notmuch/2016/021622.html

Bug#890954: closed by Michael Gilbert <mgilb...@debian.org> (Bug#890954: fixed in chromium-browser 65.0.3325.146-2)

[Georg Faerber]

Hi,

I can confirm this works now. Thanks for the work, Michael!

Cheers,
Georg


signature.asc
Description: Digital signature

Bug#893062: u-boot-imx: mx6cuboxi4x4 only detects 2GB of ram

[Vagrant Cascadian]

Control: tags 893062 pending

On 2018-03-15, Vagrant Cascadian wrote:
> The .config used during the build doesn't appear to have CONFIG_I4X4_RAM
> defined, even though config/mx6cuboxi4x4_defconfig does at the time of
> the build...

A typo in debian/rules was adding CONFIG_I4X4_RAM=y to the wrong file.

Fixed in git:

  
https://salsa.debian.org/debian/u-boot/commit/af62b5439979706ee166565af35041e699cb4f04


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#891610: consider using on_ac_power over systemd's handling

[Adam Borowski]

Marco d'Itri wrote:
> Please stop suggesting powermgmt-base: this is an obsolete, orphaned and 
> unmantained package which I last NMU'ed myself in 2014.
> It provides the on_ac_power command which is only used on non-systemd 
> systems anyway.

I've adopted powermgmt-base and fixed some issues, with more work left to
do, but even the old version was strictly better than what systemd does.

And, it turns out, the differences are not just truly ancient machines
(Powerbooks and previous millenium's i386), but also modern tablets and
phones.  On any of those that are charged via USB (that identifies as USB)
but the SoC could possibly support a non-smart connector ("ac"), even if
it's not physically wired on the machine, ConditionACPower will always think
you're on battery.

This particular problem can be fixed in systemd (simplified results of my
research so far: )
https://salsa.debian.org/debian/powermgmt-base/raw/master/power_supply.txt
as it's a straightforward extension of existing sysfs-reading code, but
looking at other scenarios that we'd also want fixed (whenever me or someone
more competent learns how), that becomes way more complex than anyone would
reasonably put into a low-level tool running as PID 1.

Thus, I'd suggest preferring on_ac_power even on systemd.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.

Bug#893057: python3-notmuch: random aborts on exit

[Jameson Graef Rollins]

On Fri, Mar 16 2018, Brian May  wrote:
> If I try to run the following program on Debian Stretch:
>
> === cut ===
> #!/usr/bin/python3
> import notmuch
> db = notmuch.Database(mode=notmuch.Database.MODE.READ_WRITE)
>
> def abcdef():
> pass
>
> q_new = notmuch.Query(db, 'tag:new')
> === cut ===
>
> I get the following output:
>
> brian@wspdigital:~$ /usr/bin/python3 ./tagmail
> Aborted
>
> If I comment/remove any of the lines out (including the function that isn't
> even referenced anywhere) or switch to Python2, then it works without any
> problems.
>
> Am wondering if this is a Python3 bug.

This is certainly very weird.  I am able to reproduce.  If I change the
script to this, though, it works fine:

  #!/usr/bin/python3
  import notmuch
  db = notmuch.Database(mode=notmuch.Database.MODE.READ_WRITE)
  q_new = notmuch.Query(db, 'tag:new')

Something about the function definition in there causes this??


signature.asc
Description: PGP signature

Bug#893062: u-boot-imx: mx6cuboxi4x4 only detects 2GB of ram

[Vagrant Cascadian]

Package: u-boot-imx
Version: 2018.01+dfsg1-1
Severity: normal
X-Debbugs-Cc: plugw...@debian.org

The Debian builds do not appear to be applying the i4x4 ram
configuration; the SPL file turns out identical with the non-i4x4
variant, and the cubox-i4x4 only detects 2GB of ram.

The .config used during the build doesn't appear to have CONFIG_I4X4_RAM
defined, even though config/mx6cuboxi4x4_defconfig does at the time of
the build...


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#893061: guile-2.2: Please add support for new architecture "riscv64" (RISC-V 64 bits little-endian)

[Manuel A. Fernandez Montecelo]

Source: guile-2.2
Version: 2.2.3+1-3
Severity: wishlist
Tags: patch upstream
User: debian-ri...@lists.debian.org
Usertags: riscv64
Forwarded: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30832

Hello,

Same as with guile-2.0 and the bug submitted in [1], we need changes in this
package for the riscv64 architecture.

  [1] https://bugs.debian.org/893060

Patches attached (same as for 2.0, might need adding the single word by hand
since more arches are present at this moment, in particular sh3, and more might
appear at any time).

Less packages depend on this version, guile-2.0 is much more critical specially
due to GNU make depending on it.  But still, this one also needs support for the
architecture at some point.

So please also include it as a patch and release a new version for unstable,
while not included in the upstream source.


Thanks and cheers.
--
Manuel A. Fernandez Montecelo 
diff -Nru guile-2.0-2.0.13+1/debian/changelog 
guile-2.0-2.0.13+1/debian/changelog
--- guile-2.0-2.0.13+1/debian/changelog 2017-12-05 07:41:29.0 +
+++ guile-2.0-2.0.13+1/debian/changelog 2018-03-15 02:09:58.0 +
@@ -1,3 +1,10 @@
+guile-2.0 (2.0.13+1-5.0~riscv64.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add riscv64 support (Closes: #-1)
+
+ -- Manuel A. Fernandez Montecelo   Thu, 15 Mar 2018 02:09:58 
+
+
 guile-2.0 (2.0.13+1-5) unstable; urgency=medium
 
   * Add upstream 0004-ia64-Fix-crash-in-thread-context-switch.patch to
diff -Nru guile-2.0-2.0.13+1/debian/patches/riscv64.patch 
guile-2.0-2.0.13+1/debian/patches/riscv64.patch
--- guile-2.0-2.0.13+1/debian/patches/riscv64.patch 1970-01-01 
00:00:00.0 +
+++ guile-2.0-2.0.13+1/debian/patches/riscv64.patch 2018-03-15 
02:09:19.0 +
@@ -0,0 +1,13 @@
+Index: guile-2.0-2.0.13+1/module/system/base/target.scm
+===
+--- guile-2.0-2.0.13+1.orig/module/system/base/target.scm
 guile-2.0-2.0.13+1/module/system/base/target.scm
+@@ -65,7 +65,7 @@
+   (cond ((string-match "^i[0-9]86$" cpu)
+  (endianness little))
+ ((member cpu '("x86_64" "ia64"
+-   "powerpcle" "powerpc64le" "mipsel" "mips64el" 
"nios2" "sh4" "alpha"))
++   "powerpcle" "powerpc64le" "mipsel" "mips64el" 
"nios2" "sh4" "alpha" "riscv64"))
+  (endianness little))
+ ((member cpu '("sparc" "sparc64" "powerpc" "powerpc64" "spu"
+"mips" "mips64" "m68k" "s390x"))
diff -Nru guile-2.0-2.0.13+1/debian/patches/series 
guile-2.0-2.0.13+1/debian/patches/series
--- guile-2.0-2.0.13+1/debian/patches/series2017-12-05 07:30:59.0 
+
+++ guile-2.0-2.0.13+1/debian/patches/series2018-03-15 02:08:19.0 
+
@@ -2,3 +2,4 @@
 0002-Look-for-guile-procedures.txt-in-pkglibdir.patch
 0003-tests-Avoid-race-condition-in-REPL-server-test.patch
 0004-ia64-Fix-crash-in-thread-context-switch.patch
+riscv64.patch
Index: guile-2.0-2.0.13+1/module/system/base/target.scm
===
--- guile-2.0-2.0.13+1.orig/module/system/base/target.scm
+++ guile-2.0-2.0.13+1/module/system/base/target.scm
@@ -65,7 +65,7 @@
   (cond ((string-match "^i[0-9]86$" cpu)
  (endianness little))
 ((member cpu '("x86_64" "ia64"
-   "powerpcle" "powerpc64le" "mipsel" "mips64el" 
"nios2" "sh4" "alpha"))
+   "powerpcle" "powerpc64le" "mipsel" "mips64el" 
"nios2" "sh4" "alpha" "riscv64"))
  (endianness little))
 ((member cpu '("sparc" "sparc64" "powerpc" "powerpc64" "spu"
"mips" "mips64" "m68k" "s390x"))

Bug#893060: guile-2.0: Please add support for new architecture "riscv64" (RISC-V 64 bits little-endian)

[Manuel A. Fernandez Montecelo]

Control: forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30832

Forwarded upstream now.

Additionally, I built and compiled the test suite, and these are the results:

Totals for this test run:
passes: 40317
failures:   0
unexpected passes:  0
expected failures:  9
unresolved test cases:  571
untested test cases:1
unsupported test cases: 10
errors: 0


-- 
Manuel A. Fernandez Montecelo 

Bug#890214: RFS: opencc/1.0.5-1

[Adam Borowski]

On Mon, Feb 12, 2018 at 09:54:13AM +0800, Boyuan Yang wrote:
>  * Package name: opencc
>Version : 1.0.5-1

>   Git packaging repository:
> 
> http://anonscm.debian.org/git/pkg-ime/opencc.git
> 
> (Yes, I'm also looking for a DD to move opencc git repository onto 
> salsa.debian.org .)

Moved.  It's at https://salsa.debian.org/debian/opencc -- if it was supposed
to be placed elsewhere, please shout.

>   Changes since the last upload:
> 
>  opencc (1.0.5-1) unstable; urgency=medium
>  .
>* Team upload.
>* New upstream Release.
>* Remove libopencc2 M-A:same mark for now since ocd files exist.
>  (Closes: #874227)
>* Remove LI Daobing from Uploaders list. (Closes: #841792)
>  Thank you for your previous work!
>* Apply "wrap-and-sort -abst".
>* d/patches: Refresh patches.
>* d/changelog: Remove trailing spaces.
>* d/control: Use debian-input-method maillist in Maintainer field.
>* d/control: Use canonical Vcs URL.
>* d/control: Bump Standards-Version to 4.1.3.
>* d/control: Bump debhelper compat to v11.
>* d/rules: Use NEWS.md as upstream changelog.
>* d/shlibs: Explicitly require the latest library version.
> 
> Looking through git history, there seems to be no API changes thus transition 
> is not
> needed.

Alas, it looks like you accidentally reverted a previous upload:

--- opencc-1.0.4/debian/changelog   2017-01-20 08:15:35.0 +0100
+++ opencc-1.0.5/debian/changelog   2018-02-12 02:30:54.0 +0100
@@ -1,8 +1,22 @@
-opencc (1.0.4-5) unstable; urgency=medium
+opencc (1.0.5-1) unstable; urgency=medium
 
-  * Make ocd data files arch:any (Closes: #851733)
+  * Team upload.
+  * New upstream Release.
+  * Remove libopencc2 M-A:same mark for now since ocd files exist.
+(Closes: #874227)
+  * Remove LI Daobing from Uploaders list. (Closes: #841792)
+Thank you for your previous work!
+  * Apply "wrap-and-sort -abst".
+  * d/patches: Refresh patches.
+  * d/changelog: Remove trailing spaces.
+  * d/control: Use debian-input-method maillist in Maintainer field.
+  * d/control: Use canonical Vcs URL.
+  * d/control: Bump Standards-Version to 4.1.3.
+  * d/control: Bump debhelper compat to v11.
+  * d/rules: Use NEWS.md as upstream changelog.
+  * d/shlibs: Explicitly require the latest library version.
 
- -- Aron Xu   Fri, 20 Jan 2017 15:15:35 +0800
+ -- Boyuan Yang <073p...@gmail.com>  Mon, 12 Feb 2018 09:30:54 +0800


Aron's change is trivial, but it still needs to be incorporated, at the very
least to make version history linear.


喵!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

[Jeff Ketchum]

Actually, I was able to just now get it to boot with that config, so this
seems to be an intermittent problem. I hit it most of the time.
It is during boot, and systemd

It may not be with systemd, but that is where the upgrades came from,
everything else was working before that.

Here is another failed boot. this is the last thing in the log.

Mar 15 16:54:56 jket-deb NetworkManager[794]:   [1521154496.1043]
device (enp3s0): carrier: link connected
Mar 15 16:54:56 jket-deb ModemManager[788]:   Couldn't check support
for device '/sys/devices/pci:00/:00:1c.2/:03:00.0': not
supported by any plugin
Mar 15 16:54:56 jket-deb ModemManager[788]:   Couldn't check support
for device '/sys/devices/pci:00/:00:1c.7/:04:00.0': not
supported by any plugin
Mar 15 16:55:26 jket-deb NetworkManager[794]:   [1521154526.2209]
device (br0): carrier: link connected
Mar 15 16:55:27 jket-deb avahi-daemon[795]: Joining mDNS multicast group on
interface br0.IPv6 with address fe80::fab1:56ff:feb8:524a.
Mar 15 16:55:27 jket-deb avahi-daemon[795]: New relevant interface br0.IPv6
for mDNS.
Mar 15 16:55:27 jket-deb avahi-daemon[795]: Registering new address record
for fe80::fab1:56ff:feb8:524a on br0.*.
Mar 15 16:55:29 jket-deb avahi-daemon[795]: Leaving mDNS multicast group on
interface br0.IPv6 with address fe80::fab1:56ff:feb8:524a.
Mar 15 16:55:29 jket-deb avahi-daemon[795]: Joining mDNS multicast group on
interface br0.IPv6 with address 2603:3026:414:b1f0:fab1:56ff:feb8:524a.
Mar 15 16:55:29 jket-deb avahi-daemon[795]: Registering new address record
for 2603:3026:414:b1f0:fab1:56ff:feb8:524a on br0.*.
Mar 15 16:55:29 jket-deb avahi-daemon[795]: Withdrawing address record for
fe80::fab1:56ff:feb8:524a on br0.
Mar 15 16:55:53 jket-deb systemd-udevd[429]: seq 2260
'/devices/pci:00/:00:01.0/:01:00.0' is taking a long time
Mar 15 16:55:55 jket-deb systemd-udevd[429]: seq 3061
'/devices/virtual/vtconsole/vtcon1' is taking a long time
Mar 15 16:57:53 jket-deb systemd-udevd[429]: seq 2260
'/devices/pci:00/:00:01.0/:01:00.0' killed
Mar 15 16:57:55 jket-deb systemd-udevd[429]: seq 3061
'/devices/virtual/vtconsole/vtcon1' killed
Mar 15 16:57:55 jket-deb systemd-udevd[429]: worker [466] terminated by
signal 9 (KILL)
Mar 15 16:57:55 jket-deb systemd-udevd[429]: worker [466] failed while
handling '/devices/virtual/vtconsole/vtcon1'
Mar 15 17:00:38 jket-deb NetworkManager[794]:   [1521154838.7769]
device (wlp4s0): set-hw-addr: set MAC address to 6E:1A:B4:B7:1B:66
(scanning)
Mar 15 17:00:38 jket-deb NetworkManager[794]:   [1521154838.7973]
device (wlp4s0): supplicant interface state: ready -> disabled
Mar 15 17:00:38 jket-deb NetworkManager[794]:   [1521154838.8324]
device (wlp4s0): supplicant interface state: disabled -> inactive
Mar 15 17:00:38 jket-deb wpa_supplicant[793]: wlp4s0: Reject scan trigger
since one is already pending


On Thu, Mar 15, 2018 at 4:40 PM, Michael Biebl  wrote:

> Am 15.03.2018 um 23:31 schrieb Jeff Ketchum:
> > Package: systemd
> > Version: 238-2
> > Severity: normal
> >
> >
> >
> > -- Package-specific info:
> >
> > -- 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-1-amd64 (SMP w/8 CPU cores)
> > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
> LANGUAGE=en_US.utf8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> >
> > Versions of packages systemd depends on:
> > ii  adduser  3.117
> > ii  libacl1  2.2.52-3+b1
> > ii  libapparmor1 2.12-3
> > ii  libaudit11:2.8.2-1
> > ii  libblkid12.31.1-0.5
> > ii  libc62.27-2
> > ii  libcap2  1:2.25-1.2
> > ii  libcryptsetup12  2:2.0.1-1
> > ii  libgcrypt20  1.8.1-4
> > ii  libgpg-error01.27-6
> > ii  libidn11 1.33-2.1
> > ii  libip4tc01.6.2-1
> > ii  libkmod2 25-1
> > ii  liblz4-1 0.0~r131-2+b1
> > ii  liblzma5 5.2.2-1.3
> > ii  libmount12.31.1-0.5
> > ii  libpam0g 1.1.8-3.7
> > ii  libseccomp2  2.3.1-2.1
> > ii  libselinux1  2.7-2+b1
> > ii  libsystemd0  238-2
> > ii  mount2.31.1-0.5
> > ii  procps   2:3.3.12-4
> > ii  util-linux   2.31.1-0.5
> >
> > Versions of packages systemd recommends:
> > ii  dbus1.12.6-2
> > ii  libpam-systemd  238-2
> >
> > Versions of packages systemd suggests:
> > ii  policykit-10.105-18
> > pn  systemd-container  
> >
> > Versions of packages systemd is related to:
> > pn  dracut   
> > ii  initramfs-tools  0.130
> > ii  udev 238-2
> >
> > -- Configuration Files:
> > /etc/systemd/journald.conf changed:
> > [Journal]
> > Storage=auto
> >
> >
> > -- no debconf information
> >
> > I upgraded systemd, and after a failure to boot, realized it was on
> > 

Bug#893059: oidentd: error with 4 parameters to, lport, from, and fport in /etc/oidentd.conf for a range directive

[Fardale]

Package: oidentd
Version: 2.0.8-10+b1
Severity: normal

Dear Maintainer,

I try to modify the reply of a particular user to an ident request with oidentd.
For this I modify the /etc/oidentd.conf file with this in it :

# Configuration for oidentd
# see oidentd.conf(5)
#
default {
default {
deny spoof
deny spoof_all
deny spoof_privport
allow random
allow random_numeric
allow numeric
deny hide
}
}

# you may want to hide root connections
#user "root" {
#   default
#   {
#   force
#   reply
#   "UNKNOWN"
#   }
#}

user someuser {
default {
allow spoof
}

to 138.231.136.62 lport 55410 from 138.231.136.12 fport 6669 {
reply "plop"
}
}


Where someuser is a valid user on the system.

When I try to start the oidentd daemon with this configuration file, it fail to
start and report a error in the file pointing to the line:
to 138.231.136.62 lport 55410 from 138.231.136.12 fport 6669 {
But this line seems to be valid regarding the manual.


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

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

Versions of packages oidentd depends on:
ii  adduser3.115
ii  iproute2   4.9.0-1+deb9u1
ii  libc6  2.24-11+deb9u3
ii  lsb-base   9.20161125
ii  net-tools  1.60+git20161116.90da8a0-1
ii  netbase5.4

oidentd recommends no packages.

oidentd suggests no packages.

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

-- no debconf information

Bug#893060: guile-2.0: Please add support for new architecture "riscv64" (RISC-V 64 bits little-endian)

[Manuel A. Fernandez Montecelo]

Source: guile-2.0
Version: 2.0.13+1-5
Severity: normal
Tags: patch upstream
User: debian-ri...@lists.debian.org
Usertags: riscv64

Hello,

We need support in this package to bootstrap the riscv64 architecture.

I plan to submit this simple patch upstream in the near future (if somebody
wants to beat me to it, feel free :) ).

It would be great if you could include it as a patch and release a new version
for unstable.

If you think that we can help in any way to make it happen, please let me/us
know.


Thanks and cheers.
--
Manuel A. Fernandez Montecelo 
diff -Nru guile-2.0-2.0.13+1/debian/changelog 
guile-2.0-2.0.13+1/debian/changelog
--- guile-2.0-2.0.13+1/debian/changelog 2017-12-05 07:41:29.0 +
+++ guile-2.0-2.0.13+1/debian/changelog 2018-03-15 02:09:58.0 +
@@ -1,3 +1,10 @@
+guile-2.0 (2.0.13+1-5.0~riscv64.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add riscv64 support (Closes: #-1)
+
+ -- Manuel A. Fernandez Montecelo   Thu, 15 Mar 2018 02:09:58 
+
+
 guile-2.0 (2.0.13+1-5) unstable; urgency=medium
 
   * Add upstream 0004-ia64-Fix-crash-in-thread-context-switch.patch to
diff -Nru guile-2.0-2.0.13+1/debian/patches/riscv64.patch 
guile-2.0-2.0.13+1/debian/patches/riscv64.patch
--- guile-2.0-2.0.13+1/debian/patches/riscv64.patch 1970-01-01 
00:00:00.0 +
+++ guile-2.0-2.0.13+1/debian/patches/riscv64.patch 2018-03-15 
02:09:19.0 +
@@ -0,0 +1,13 @@
+Index: guile-2.0-2.0.13+1/module/system/base/target.scm
+===
+--- guile-2.0-2.0.13+1.orig/module/system/base/target.scm
 guile-2.0-2.0.13+1/module/system/base/target.scm
+@@ -65,7 +65,7 @@
+   (cond ((string-match "^i[0-9]86$" cpu)
+  (endianness little))
+ ((member cpu '("x86_64" "ia64"
+-   "powerpcle" "powerpc64le" "mipsel" "mips64el" 
"nios2" "sh4" "alpha"))
++   "powerpcle" "powerpc64le" "mipsel" "mips64el" 
"nios2" "sh4" "alpha" "riscv64"))
+  (endianness little))
+ ((member cpu '("sparc" "sparc64" "powerpc" "powerpc64" "spu"
+"mips" "mips64" "m68k" "s390x"))
diff -Nru guile-2.0-2.0.13+1/debian/patches/series 
guile-2.0-2.0.13+1/debian/patches/series
--- guile-2.0-2.0.13+1/debian/patches/series2017-12-05 07:30:59.0 
+
+++ guile-2.0-2.0.13+1/debian/patches/series2018-03-15 02:08:19.0 
+
@@ -2,3 +2,4 @@
 0002-Look-for-guile-procedures.txt-in-pkglibdir.patch
 0003-tests-Avoid-race-condition-in-REPL-server-test.patch
 0004-ia64-Fix-crash-in-thread-context-switch.patch
+riscv64.patch
Index: guile-2.0-2.0.13+1/module/system/base/target.scm
===
--- guile-2.0-2.0.13+1.orig/module/system/base/target.scm
+++ guile-2.0-2.0.13+1/module/system/base/target.scm
@@ -65,7 +65,7 @@
   (cond ((string-match "^i[0-9]86$" cpu)
  (endianness little))
 ((member cpu '("x86_64" "ia64"
-   "powerpcle" "powerpc64le" "mipsel" "mips64el" 
"nios2" "sh4" "alpha"))
+   "powerpcle" "powerpc64le" "mipsel" "mips64el" 
"nios2" "sh4" "alpha" "riscv64"))
  (endianness little))
 ((member cpu '("sparc" "sparc64" "powerpc" "powerpc64" "spu"
"mips" "mips64" "m68k" "s390x"))

Bug#893058: ITP: libdecaf -- implementation of Montgomery and Edwards elliptic curve cryptography

[Christopher Hoskin]

Package: wnpp
Severity: wishlist
Owner: Christopher Hoskin 

* Package name: libdecaf
  Version : 0.9.4
  Upstream Author : Cryptography Research, Inc.
* URL : http://ed448goldilocks.sourceforge.net/
* License : expat
  Programming Lang: C
  Description : implementation of Montgomery and Edwards elliptic curve 
cryptography

 The libdecaf library is for elliptic curve research and practical application.
 It currently supports Ed448-Goldilocks and Curve25519.

 The goals of this library are:

  * Implementing the X25519, X448 key exchange protocols (RFC 7748).
  * Implementing the Ed25519 and EdDSA-Ed448 signature schemes (RFC 8032).
  * Providing a platform for research and development of advanced cryptographic
schemes using twisted Edwards curves.

 This library is intended for developers who have experience with
 cryptography.

 libdecaf is a dependency for sphinx (a password Store that Perfectly Hides from
 Itself (No Xaggeration)).

 I plan to maintain it within the Debian/ namespace on Salsa. I do not require a
 sponsor.

Bug#886096: lintian: Emit warnings for Alioth URLs in packaging (migration to Salsa)

[Chris Lamb]

[Adding Mattia to CC as he was did some work on this bug so inferring interest]

Hi Stuart et al.,

> > we now only have 6 time quanta until alioth is read-only
> 
> I like this "time quanta" concept :)  Okay, agreed, let's get onto
> this ASAP.
> 
> Can you help by drafting the specific tag (or tags?) and giving some
> examples of Vcs-Foo it should trigger on?

Gentle ping on this? I would love to upload another Lintian soon and
it would be a shame not to include these time-sensitive changes. 


Best wishes,

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

Bug#893037: Add support for diffing docker-format containers

[Chris Lamb]

tags 893037 + moreinfo
thanks

Hi Jonathan,

Thank you very much for the idea and wishlist bug.

> It would be nice if diffoscope could diff against docker containers available
> on the local system.

Could you briefly elaborate on what you mean here? I have a bunch of
directories under /var/lib/docker/containers -- are you wanting to
diffoscope two of these, or...? diffoscope basically works on "paths",
you see.


Best wishes,

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

Bug#893056: ITP: libpe1 -- The PE library used by pev

[Robert Haist]

Package: wnpp
Severity: wishlist
Owner: Robert Haist 

* Package name: libpe1
  Version : 1.0.0
  Upstream Author : Fernando Mercês
* URL : https://github.com/merces/libpe
* License : LGPLv3
  Programming Lang: C
  Description : The PE library used by pev

Currently the pev package in debian contains the pev tools and the library,
because upstream had a single integrated repo in the past. Now upstream is
divided in two repos and we have to package the library as dependency too.

Bug#893057: python3-notmuch: random aborts on exit

[Brian May]

Package: python3-notmuch
Version: 0.23.7-3
Severity: important

If I try to run the following program on Debian Stretch:

=== cut ===
#!/usr/bin/python3
import notmuch
db = notmuch.Database(mode=notmuch.Database.MODE.READ_WRITE)

def abcdef():
pass

q_new = notmuch.Query(db, 'tag:new')
=== cut ===

I get the following output:

brian@wspdigital:~$ /usr/bin/python3 ./tagmail
Aborted

If I comment/remove any of the lines out (including the function that isn't
even referenced anywhere) or switch to Python2, then it works without any
problems.

Am wondering if this is a Python3 bug.

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

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

Versions of packages python3-notmuch depends on:
ii  libnotmuch4  0.23.7-3
ii  python3  3.5.3-1

python3-notmuch recommends no packages.

python3-notmuch suggests no packages.

-- no debconf information

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

[Michael Biebl]

Am 15.03.2018 um 23:31 schrieb Jeff Ketchum:
> Package: systemd
> Version: 238-2
> Severity: normal
> 
> 
> 
> -- Package-specific info:
> 
> -- 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-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
> LANGUAGE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages systemd depends on:
> ii  adduser  3.117
> ii  libacl1  2.2.52-3+b1
> ii  libapparmor1 2.12-3
> ii  libaudit11:2.8.2-1
> ii  libblkid12.31.1-0.5
> ii  libc62.27-2
> ii  libcap2  1:2.25-1.2
> ii  libcryptsetup12  2:2.0.1-1
> ii  libgcrypt20  1.8.1-4
> ii  libgpg-error01.27-6
> ii  libidn11 1.33-2.1
> ii  libip4tc01.6.2-1
> ii  libkmod2 25-1
> ii  liblz4-1 0.0~r131-2+b1
> ii  liblzma5 5.2.2-1.3
> ii  libmount12.31.1-0.5
> ii  libpam0g 1.1.8-3.7
> ii  libseccomp2  2.3.1-2.1
> ii  libselinux1  2.7-2+b1
> ii  libsystemd0  238-2
> ii  mount2.31.1-0.5
> ii  procps   2:3.3.12-4
> ii  util-linux   2.31.1-0.5
> 
> Versions of packages systemd recommends:
> ii  dbus1.12.6-2
> ii  libpam-systemd  238-2
> 
> Versions of packages systemd suggests:
> ii  policykit-10.105-18
> pn  systemd-container  
> 
> Versions of packages systemd is related to:
> pn  dracut   
> ii  initramfs-tools  0.130
> ii  udev 238-2
> 
> -- Configuration Files:
> /etc/systemd/journald.conf changed:
> [Journal]
> Storage=auto
> 
> 
> -- no debconf information
> 
> I upgraded systemd, and after a failure to boot, realized it was on
> systemd:i386.
> I went into a recovery environment and removed systemd:i386 and
> installed systemd.
> After that It failed to boot at a different location.
> I was able to get it to boot by removing the kernel parameter
> for the nouveau driver to use the binary firmware.
> 
> nouveau.config=NvGrUseFw=1

Where exactly is the problem that is caused by systemd?

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



signature.asc
Description: OpenPGP digital signature

Bug#836368: retitle 836368 ITA: pev -- text-based tool to analyze PE files

[Petter Reinholdtsen]

[Robert Haist]
> Hi Petter,
>
> could you please update the repo with the latest code and tags for
> 0.80-4 ? Alioth is still on 0.80-3.

Done.  I ran

  gbp import-dsc ../pev_0.80-4.dsc; git push; git push --tags

after fetching the source using 'apt-get source pev'.

-- 
Happy hacking
Petter Reinholdtsen

Bug#893055: ITP: imbalanced-learn -- Python module to perform under sampling and over sampling with various techniques.

[Aggelos Avgerinos]

Package: wnpp
Severity: wishlist
Owner: Aggelos Avgerinos 

* Package name: imbalanced-learn
  Version : 0.3.2
  Upstream Author : Fernando M. F. Nogueira, Guillaume Lemaitre, Dayvid Victor
* URL : https://github.com/scikit-learn-contrib/imbalanced-learn
* License : MIT
  Programming Lang: Python
  Description : Python module to perform under sampling and over sampling 
with various techniques.

  imbalanced-learn is a python package offering a number of re-sampling
  techniques commonly used in datasets showing strong between-class
  imbalance.

  It is compatible with scikit-learn and is part of
  scikit-learn-contrib projects.

  I intent to package and maintain it under the debian neuro team.

Bug#892965: Bug#892966: [pkg-ntp-maintainers] Bug#892965: Bug#892966: ntpsec-ntpdate: unconditionally removes /var/lib/ntpdate on purge, even if ntpdate is installed

[Richard Laager]

On 03/15/2018 02:12 PM, Bernhard Schmidt wrote:
> On the other hand, I think we're not using it anyway for ntpdate (I
> could only find it referenced in the dhcp hooks prior to
> f4abbe2168b452d25fb4311796c8930bcdc24bd9, pre-stretch, after that it has
> been migrated to /run to be flushed on reboot).

This change was merged into ntpsec-ntpdate prior to ntpsec_1.0.0-1, so
there was never a released version of ntpsec-ntpdate using
/var/lib/ntpdate at all. So clearly the right answer is for me to drop
this (which is the entirety of ntpsec-ntpdate.postrm). This solves both
bugs at once.

-- 
Richard

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

[Jeff Ketchum]

Package: systemd
Version: 238-2
Severity: normal



-- Package-specific info:

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

Versions of packages systemd depends on:
ii  adduser  3.117
ii  libacl1  2.2.52-3+b1
ii  libapparmor1 2.12-3
ii  libaudit11:2.8.2-1
ii  libblkid12.31.1-0.5
ii  libc62.27-2
ii  libcap2  1:2.25-1.2
ii  libcryptsetup12  2:2.0.1-1
ii  libgcrypt20  1.8.1-4
ii  libgpg-error01.27-6
ii  libidn11 1.33-2.1
ii  libip4tc01.6.2-1
ii  libkmod2 25-1
ii  liblz4-1 0.0~r131-2+b1
ii  liblzma5 5.2.2-1.3
ii  libmount12.31.1-0.5
ii  libpam0g 1.1.8-3.7
ii  libseccomp2  2.3.1-2.1
ii  libselinux1  2.7-2+b1
ii  libsystemd0  238-2
ii  mount2.31.1-0.5
ii  procps   2:3.3.12-4
ii  util-linux   2.31.1-0.5

Versions of packages systemd recommends:
ii  dbus1.12.6-2
ii  libpam-systemd  238-2

Versions of packages systemd suggests:
ii  policykit-10.105-18
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 238-2

-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]
Storage=auto


-- no debconf information

I upgraded systemd, and after a failure to boot, realized it was on
systemd:i386.
I went into a recovery environment and removed systemd:i386 and
installed systemd.
After that It failed to boot at a different location.
I was able to get it to boot by removing the kernel parameter
for the nouveau driver to use the binary firmware.

nouveau.config=NvGrUseFw=1

Mar 14 10:39:17 jket-deb kernel: nouveau :01:00.0: bios: version 
80.06.41.00.0a
Mar 14 10:39:17 jket-deb kernel: nouveau :01:00.0: firmware: direct-loading 
firmware nvidia/gk106/fecs_inst.bin
Mar 14 10:39:17 jket-deb kernel: nouveau :01:00.0: firmware: direct-loading 
firmware nvidia/gk106/fecs_data.bin
Mar 14 10:39:17 jket-deb kernel: nouveau :01:00.0: firmware: direct-loading 
firmware nvidia/gk106/gpccs_inst.bin
Mar 14 10:39:17 jket-deb kernel: nouveau :01:00.0: firmware: direct-loading 
firmware nvidia/gk106/gpccs_data.bin
Mar 14 10:39:17 jket-deb kernel: nouveau :01:00.0: fb: 1024 MiB GDDR5

Mar 14 10:39:18 jket-deb kernel: nouveau :01:00.0: DRM: allocated 1920x1080 
fb: 0x6, bo 125ba628
Mar 14 10:39:18 jket-deb kernel: fbcon: nouveaufb (fb0) is primary device


Mar 14 10:39:51 jket-deb avahi-daemon[793]: Joining mDNS multicast group on 
interface br0.IPv6 with address fe80::fab1:56ff:feb8:524a.
Mar 14 10:39:51 jket-deb avahi-daemon[793]: New relevant interface br0.IPv6 for 
mDNS.
Mar 14 10:39:51 jket-deb avahi-daemon[793]: Registering new address record for 
fe80::fab1:56ff:feb8:524a on br0.*.
Mar 14 10:39:52 jket-deb avahi-daemon[793]: Leaving mDNS multicast group on 
interface br0.IPv6 with address fe80::fab1:56ff:feb8:524a.
Mar 14 10:39:52 jket-deb avahi-daemon[793]: Joining mDNS multicast group on 
interface br0.IPv6 with address 2603:3026:414:b1f0:fab1:56ff:feb8:524a.
Mar 14 10:39:52 jket-deb avahi-daemon[793]: Registering new address record for 
2603:3026:414:b1f0:fab1:56ff:feb8:524a on br0.*.
Mar 14 10:39:52 jket-deb avahi-daemon[793]: Withdrawing address record for 
fe80::fab1:56ff:feb8:524a on br0.
Mar 14 10:40:17 jket-deb systemd-udevd[439]: seq 2262 
'/devices/pci:00/:00:01.0/:01:00.0' is taking a long time
Mar 14 10:40:19 jket-deb systemd-udevd[439]: seq 3069 
'/devices/virtual/vtconsole/vtcon1' is taking a long time

Bug#836368: retitle 836368 ITA: pev -- text-based tool to analyze PE files

[Robert Haist]

Hi Petter,

could you please update the repo with the latest code and tags for
0.80-4 ? Alioth is still on 0.80-3.

Regards,

-- 
Robert Haist

2BC8 3F55 A400 7468 864C 680E 1B7C C8D4 D4E9 14AA


On Tue, 04 Jul 2017 23:55:28 +0200 Petter Reinholdtsen 
wrote:
> [Petter Reinholdtsen]
> > Upstream did make a new release.  Any hope to get the new version of
> > pev into Debian?
> 
> I imported versions 0.60 - 0.80 into
> https://anonscm.debian.org/cgit/collab-maint/pev.git > and brushed
> up the build rules a bit.
> 
> Not quite sure what to do with the remaining lintian issues:
> 
> E: pev source: source-is-missing src/lib/libfuzzy/edit_dist.o
> E: pev source: source-is-missing src/lib/libfuzzy/fuzzy.o
> W: pev: package-name-doesnt-match-sonames libpe1
> W: pev: non-dev-pkg-with-shlib-symlink usr/lib/libpe.so.1.0 usr/lib/libpe.so
> 
> The first two are already solved in the upstream git repository.
> Creating a library package out of pev seem like a bad idea.  Is there
> some better idea?
> 
> -- 
> Happy hacking
> Petter Reinholdtsen
> 
> 



signature.asc
Description: OpenPGP digital signature

Bug#893005: [Pkg-dns-devel] Bug#893005: Bug#893005: Salsa MP

[Andreas Hasenack]

I meant merge proposal, aka, pull request, or merge request. Every system
has its own name for it :)

On Mar 15, 2018 18:43, "Daniel Kahn Gillmor"  wrote:

> On Thu 2018-03-15 11:56:11 -0300, Andreas Hasenack wrote:
> > Sure :) I suppose you don't need another mp, right? I mostly wanted to
> > practice my salsa access
>
> could you tell me what an "mp" is?  I'm trying to follow this thread and
> am confused.
>
> thanks,
>
>--dkg
>

Bug#891937: [Pkg-mailman-hackers] Bug#891937: mailman3-suite: Hyperkitty tries to connect postgres on system using sqlite

[Jonas Meurer]

Hi Markus,


I did quite some testing of the mailman3 packages in the last days,
using all possible database backends. So far, I failed to reproduce the
bug you discovered.

After testing different settings, I'm pretty confident that indeed the
database settings from '/etc/mailman3/mailman3-suite.py' are used in a
clean mailman3-suite installation.

Please send the output of the following commands:

$ ls -al /etc/mailman3/mailman-suite.py
$ ls -al /usr/share/mailman3-suite/settings*


We renamed the 'mailman3-suite' package to 'mailman3-web' recently, to
avoid further confusion about the purpose of the package. Similarly, we
renamed 'mailman3-core' to 'mailman3'. You should find all these
packages in Debian Unstable by now.

Would you mind to purge all your mailman3 packages, do a fresh
installation and see, whether you're still able to reproduce the bug
with the latest packages from Debian Unstable?

Cheers,
 jonas

Am 05.03.2018 um 02:12 schrieb Markus Gschwendt:
> cat /etc/mailman3/mailman3-suite.py
> 
> # This file is imported by the Mailman Suite. It is used to override
> # the default settings from /usr/share/mailman3-suite/settings.py.
> 
> # SECURITY WARNING: keep the secret key used in production secret!
> SECRET_KEY = '5S/5OIURrBJcaoB3xFK+lorJ+Rnb1GdTN3jVx9RGwKJZkjDz'
> 
> ADMINS = (
>  ('Mailman Suite Admin', 'root@localhost'),
> )
> 
> # Hosts/domain names that are valid for this site; required if DEBUG is
> False
> # See https://docs.djangoproject.com/en/1.8/ref/settings/#allowed-hosts
> # Set to '*' per default in the Deian package to allow all hostnames.
> Mailman3
> # is meant to run behind a webserver reverse proxy anyway.
> ALLOWED_HOSTS = [
> #"localhost",  # Archiving API from Mailman, keep it.
> # "lists.your-domain.org",
> # Add here all production URLs you may have.
> '*'
> ]
> 
> # Mailman API credentials
> MAILMAN_REST_API_URL = 'http://localhost:8001'
> MAILMAN_REST_API_USER = 'restadmin'
> MAILMAN_REST_API_PASS = 'x'
> MAILMAN_ARCHIVER_KEY = 'x'
> MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1')
> 
> # Application definition
> 
> INSTALLED_APPS = (
> 'hyperkitty',
> 'postorius',
> 'django_mailman3',
> # Uncomment the next line to enable the admin:
> 'django.contrib.admin',
> # Uncomment the next line to enable admin documentation:
> # 'django.contrib.admindocs',
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.sites',
> 'django.contrib.messages',
> 'django.contrib.staticfiles',
> 'rest_framework',
> 'django_gravatar',
> 'paintstore',
> 'compressor',
> 'haystack',
> 'django_extensions',
> 'django_q',
> 'allauth',
> 'allauth.account',
> 'allauth.socialaccount',
> #'django_mailman3.lib.auth.fedora',
> #'allauth.socialaccount.providers.openid',
> #'allauth.socialaccount.providers.github',
> #'allauth.socialaccount.providers.gitlab',
> #'allauth.socialaccount.providers.google',
> #'allauth.socialaccount.providers.facebook',
> #'allauth.socialaccount.providers.twitter',
> #'allauth.socialaccount.providers.stackexchange',
> )
> 
> 
> # Database
> # https://docs.djangoproject.com/en/1.8/ref/settings/#databases
> 
> DATABASES = {
> 'default': {
> # Use 'sqlite3', 'postgresql_psycopg2', 'mysql', 'sqlite3' or
> 'oracle'.
> 'ENGINE': 'django.db.backends.sqlite3',
> #'ENGINE': 'django.db.backends.postgresql_psycopg2',
> #'ENGINE': 'django.db.backends.mysql',
> # DB name or path to database file if using sqlite3.
> 'NAME': '/var/lib/mailman3/web/mailman3suite.db.db',
> # The following settings are not used with sqlite3:
> 'USER': '',
> 'PASSWORD': '',
> # HOST: empty for localhost through domain sockets or
> '127.0.0.1' for
> # localhost through TCP.
> 'HOST': '',
> # PORT: set to empty string for default.
> 'PORT': '',
> # OPTIONS: Extra parameters to use when connecting to the
> database.
> 'OPTIONS': {
> # Set sql_mode to 'STRICT_TRANS_TABLES' for MySQL. See
> # https://docs.djangoproject.com/en/1.11/ref/
> # databases/#setting-sql-mode
> #'init_command': "SET sql_mode='STRICT_TRANS_TABLES'",
> },
> }
> }
> 
> 
> # If you're behind a proxy, use the X-Forwarded-Host header
> # See https://docs.djangoproject.com/en/1.8/ref/settings/#use-x-forward
> ed-host
> USE_X_FORWARDED_HOST = True
> 
> # And if your proxy does your SSL encoding for you, set
> SECURE_PROXY_SSL_HEADER
> # https://docs.djangoproject.com/en/1.8/ref/settings/#secure-proxy-ssl-
> header
> SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
> SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_SCHEME', 'https')
> 
> # Other security settings
> # SECURE_SSL_REDIRECT = True
> # If you set SECURE_SSL_REDIRECT to True, make sure the
> 

Bug#893053: awesome: (re)Starting is very slow due to enumerating icons for the main menu

[Hans van den Bogert]

Package: awesome
Version: 4.2-4
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Maintainer,

In the 4.2 release of Awesome, it can take more than 10 seconds to restart 
Awesome.
It was tracked down to the following discussion on the projects Github:

https://github.com/awesomeWM/awesome/issues/1496 and
https://github.com/awesomeWM/awesome/pull/2112

It is arguable if this patch truly fixes a bug, to the best of my judgement I 
find this a bug, since a very
simple use-case, like changing Awesome's config and reloading becomes arduous.


Thanks for considering the patch.


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

Kernel: Linux 4.15.0-12-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru awesome-4.2/debian/patches/deprecate_menubar.icon_theme.patch 
awesome-4.2/debian/patches/deprecate_menubar.icon_theme.patch
--- awesome-4.2/debian/patches/deprecate_menubar.icon_theme.patch   
1970-01-01 01:00:00.0 +0100
+++ awesome-4.2/debian/patches/deprecate_menubar.icon_theme.patch   
2018-03-15 20:45:16.0 +0100
@@ -0,0 +1,76 @@
+From 0b0b466705b8f8e4f4cc3a2a4ad353fc0e544b82 Mon Sep 17 00:00:00 2001
+From: Uli Schlachter 
+Date: Thu, 16 Nov 2017 13:12:59 +0100
+Subject: [PATCH] Deprecate menubar.icon_theme
+
+The code in menubar.icon_theme naively implements the algorithm from the
+base dir specification. This is a problem: On this system,
+/usr/share/icons/{Adwaita,hicolor}/index.theme list 91, respectively 649
+subdirectories. Since we check for three file extensions (png, svg,
+xpm), this means that a failing icon lookup for the Adwaita theme checks
+for (91+649)*3 = 2220 files (in practice it might be a bit better since
+the directories have specific meanings, but still). That's insane.
+
+Since we only use this code for looking up category icons anyway, just
+deprecate this mess. Category icons are now looked up in the same way
+that icons for individual applications are looked up.
+
+Since menubar.init does not require("menubar.icon_theme"), this means
+that menubar.icon_theme is no longer actually loaded. That's bad.
+
+(Hopefully) Fixes: https://github.com/awesomeWM/awesome/issues/1496
+Signed-off-by: Uli Schlachter 
+---
+ lib/menubar/icon_theme.lua | 4 +++-
+ lib/menubar/menu_gen.lua   | 3 +--
+ 2 files changed, 4 insertions(+), 3 deletions(-)
+
+diff --git a/lib/menubar/icon_theme.lua b/lib/menubar/icon_theme.lua
+index 7dcc44b02b..358f00737c 100644
+--- a/lib/menubar/icon_theme.lua
 b/lib/menubar/icon_theme.lua
+@@ -1,5 +1,5 @@
+ ---
+ Class module for icon lookup for menubar
++--- (Deprecated) class module for icon lookup for menubar
+ --
+ -- @author Kazunobu Kuriyama
+ -- @copyright 2015 Kazunobu Kuriyama
+@@ -78,6 +78,7 @@ local icon_theme = { mt = {} }
+ local index_theme_cache = {}
+ 
+ --- Class constructor of `icon_theme`
++-- @deprecated menubar.icon_theme.new
+ -- @tparam string icon_theme_name Internal name of icon theme
+ -- @tparam table base_directories Paths used for lookup
+ -- @treturn table An instance of the class `icon_theme`
+@@ -218,6 +219,7 @@ local lookup_fallback_icon = function(self, icon_name)
+ end
+ 
+ ---  Look up an image file based on a given icon name and/or a preferable 
size.
++-- @deprecated menubar.icon_theme:find_icon_path
+ -- @tparam string icon_name Icon name to be looked up
+ -- @tparam number icon_size Prefereable icon size
+ -- @treturn string Absolute path to the icon file, or nil if not found
+diff --git a/lib/menubar/menu_gen.lua b/lib/menubar/menu_gen.lua
+index 519629c7d4..0be0b6967f 100644
+--- a/lib/menubar/menu_gen.lua
 b/lib/menubar/menu_gen.lua
+@@ -10,7 +10,6 @@
+ local gtable = require("gears.table")
+ local gfilesystem = require("gears.filesystem")
+ local utils = require("menubar.utils")
+-local icon_theme = require("menubar.icon_theme")
+ local pairs = pairs
+ local ipairs = ipairs
+ local table = table
+@@ -59,7 +58,7 @@ menu_gen.all_categories = {
+ --- Find icons for category entries.
+ function menu_gen.lookup_category_icons()
+ for _, v in pairs(menu_gen.all_categories) do
+-v.icon = icon_theme():find_icon_path(v.icon_name)
++v.icon = utils.lookup_icon(v.icon_name)
+ end
+ end
+ 
+
diff -Nru awesome-4.2/debian/patches/deprecate_menubar.index_theme.patch 
awesome-4.2/debian/patches/deprecate_menubar.index_theme.patch
--- awesome-4.2/debian/patches/deprecate_menubar.index_theme.patch  
1970-01-01 01:00:00.0 +0100
+++ awesome-4.2/debian/patches/deprecate_menubar.index_theme.patch  
2018-03-15 

Bug#892956: Additional info

[Jussi Pakkanen]

Hi

The -llibfoo thing is obviously wrong, we'll need to get that fixed.

The private one is a bit trickier. We generate private requires
because they are needed for static linkin. This is where pkg-config
behaves a bit strangely:

For --libs, private depends are not listed unless you use --static.

For --cflags, private depends are always listed.

The problem here is that an arguable case can be made for listing the
headers without --static and also for not doing that. I would have
expected the latter behaviour but apparently based on pkg-config's Git
repo they have explicitly made it do the former.

Bug#893052: RFS: btrfsmaintenance/0.4.1-1 [I maintain the package]

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "btrfsmaintenance".

Hi Sven,

I've CCed you because you have consistently sponsored this package :-)

Package name: btrfsmaintenance
Version : 0.4.1-1
Upstream Author : David Sterba 
URL : https://github.com/kdave/btrfsmaintenance
License : GPL-2
Section : admin

It builds this binary package:

  btrfsmaintenance - automate btrfs maintenance tasks on mountpoints or 
directories

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfsmaintenance/btrfsmaintenance_0.4.1-1.dsc

Alternatively, one can clone the package's git repo using this command:

  git clone https://salsa.debian.org/sten-guest/btrfsmaintenance.git

More information about btrfsmaintenance can be obtained from 
https://github.com/kdave/btrfsmaintenance.

Changes since the last upload (upstream changelog is now automatically 
installed):

btrfsmaintenance (0.4.1-1) unstable; urgency=medium

  * New upstream version.
  * Fix lintian I: vcs-field-not-canonical.
  * Change architecture to linux-any, because btrfs is Linux-only
  * Drop DH_VERBOSE =1 and delete unneeded commented-out lines

 -- Nicholas D Steeves   Thu, 15 Mar 2018 17:27:11 -0400

btrfsmaintenance (0.4-1) unstable; urgency=medium

##

Upstream changelog

version 0.4.1 (2018-03-15)
- defrag plugin: python2 and 3 compatibility
- defrag plugin: target extent size lowered to 32MiB (#43)
- shell compatibility fixes
- systemd unit type fixes

version 0.4 (2018-01-18)


Regards,
Nicholas D Steeves

Bug#893051: prometheus-mysqld-exporter FTBFS on 32bit: global_variables_test.go:79:67: constant 2147483648 overflows int

[Adrian Bunk]

Source: prometheus-mysqld-exporter
Version: 0.10.0+git20180201.a71f4bb+ds-1
Severity: serious

https://buildd.debian.org/status/package.php?p=prometheus-mysqld-exporter=sid

...
   dh_auto_test -a -O--buildsystem=golang
cd obj-i686-linux-gnu && go test -vet=off -v -p 4 
github.com/prometheus/mysqld_exporter 
github.com/prometheus/mysqld_exporter/collector
# github.com/prometheus/mysqld_exporter/collector
src/github.com/prometheus/mysqld_exporter/collector/global_variables_test.go:79:67:
 constant 2147483648 overflows int
=== RUN   TestParseMycnf

  Various .my.cnf configurations 
Local tcp connection ✔
Local tcp connection on non-default port ✔
Socket connection ✔
Socket connection ignoring defined host ✔
Remote connection ✔
Missed user ✔
Missed password ✔
No [client] section ✔
Invalid config ✔


9 total assertions

--- PASS: TestParseMycnf (0.00s)
=== RUN   TestBin
=== RUN   TestBin/mysqld_exporter
=== RUN   
TestBin/mysqld_exporter/github.com/prometheus/mysqld_exporter.testLandingPage
=== PAUSE 
TestBin/mysqld_exporter/github.com/prometheus/mysqld_exporter.testLandingPage
=== CONT  
TestBin/mysqld_exporter/github.com/prometheus/mysqld_exporter.testLandingPage
--- PASS: TestBin (4.19s)
--- PASS: TestBin/mysqld_exporter (0.00s)
--- PASS: 
TestBin/mysqld_exporter/github.com/prometheus/mysqld_exporter.testLandingPage 
(1.00s)
PASS
ok  github.com/prometheus/mysqld_exporter   4.204s
FAILgithub.com/prometheus/mysqld_exporter/collector [build failed]
dh_auto_test: cd obj-i686-linux-gnu && go test -vet=off -v -p 4 
github.com/prometheus/mysqld_exporter 
github.com/prometheus/mysqld_exporter/collector returned exit code 2
debian/rules:22: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2

Bug#891703: [Pkg-mailman-hackers] Bug#891703: mailman3-suite: DB user isn't read from setting_local (mailman3-suite.py in /etc)

[Jonas Meurer]

Hi Eric,

Am 04.03.2018 um 04:59 schrieb Eric Côté:
> Bug is still present.

I did quite some testing of the mailman3 packages in the last days,
using all possible database backends. So far, I failed to reproduce the
bug you discovered.

We renamed the 'mailman3-suite' package to 'mailman3-web' recently, to
avoid further confusion about the purpose of the package. Similarly, we
renamed 'mailman3-core' to 'mailman3'. You should find all these
packages in Debian Unstable by now.

Would you mind to purge all your mailman3 packages, do a fresh
installation and see, whether you're still able to reproduce the bug
with the latest packages from Debian Unstable?

> Like I mentioned in my original report, "mailman3suite" is the user in
> /usr/share/mailman3-suite/settings.py . I've had to hand edit it so my install
> reads my DB settings in /etc/mailman3/mailman3-suite.py . 

After testing different settings, I'm pretty confident that indeed the
database settings from '/etc/mailman3/mailman3-suite.py' (or now
'/etc/mailman/mailman-web.py') are used in a clean
mailman3-suite/mailman3-web installation.

Please send the output of the following commands:

$ ls -al /etc/mailman3/mailman-suite.py
$ ls -al /usr/share/mailman3-suite/settings*

> Seems this might be in either python-django-hyperkitty (which is I think is 
> the
> case), since the log is referencing django and hyperkitty, or in
> python3-mailman-hyperkitty (which doesn't seem to be picking up my list 
> content
> anyway; I should be seeing archives, but I don't, in the web UI).
> 
> I dunno how to refile a bug to another source package or tag another (if 
> that's doable).

You can reassign existing bugreports by using 'Control:' pseudo-headers
at the beginning of mails or by sending control commands to the
bugtracker[1].

[1] https://www.debian.org/Bugs/server-control

Cheers,
 jonas



signature.asc
Description: OpenPGP digital signature

Bug#893005: [Pkg-dns-devel] Bug#893005: Bug#893005: Salsa MP

[Daniel Kahn Gillmor]

On Thu 2018-03-15 11:56:11 -0300, Andreas Hasenack wrote:
> Sure :) I suppose you don't need another mp, right? I mostly wanted to
> practice my salsa access

could you tell me what an "mp" is?  I'm trying to follow this thread and
am confused.

thanks,

   --dkg

Bug#893041: (No Subject)

[Fjfj109]

Okay, my very rudimentary investigations (sorry if this isn't what you're 
looking for):

/lib/systemd/system/virtlockd-admin.socket contains:

[Unit]
Description=Virtual machine lock manager admin socket
Before=libvirtd.service

[Socket]
ListenStream=/var/run/libvirt/virtlockd-admin-sock
Server=virtlockd.service

[Install]
WantedBy=sockets.target

systemctl status virtlockd.service gives:

annadane@debian:~$ systemctl status virtlockd.service
● virtlockd.service - Virtual machine lock manager
   Loaded: loaded (/lib/systemd/system/virtlockd.service; indirect; vendor 
preset: enabled)
   Active: inactive (dead)
 Docs: man:virtlockd(8)
   https://libvirt.org

annadane@debian:~$ systemctl start virtlockd.service
 AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
A dependency job for virtlockd.service failed. See 'journalctl -xe' for details.

journalctl -xe gives:

Mar 15 17:30:58 debian systemd[1]: virtlockd-admin.socket: Socket service 
virtlockd-admin.service not loaded, refusing.
Mar 15 17:30:58 debian systemd[1]: Failed to listen on Virtual machine lock 
manager admin socket.
-- Subject: Unit virtlockd-admin.socket has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit virtlockd-admin.socket has failed.
--
-- The result is RESULT.
Mar 15 17:30:58 debian systemd[1]: Dependency failed for Virtual machine lock 
manager.
-- Subject: Unit virtlockd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit virtlockd.service has failed.
--
-- The result is RESULT.
Mar 15 17:30:58 debian systemd[1]: virtlockd.service: Job 
virtlockd.service/start failed with result 'dependency'.
Mar 15 17:30:58 debian polkitd(authority=local)[639]: Unregistered 
Authentication Agent for unix-process:8683:10538976 (system bus name :1.127, 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale 
en_CA.UTF-8) (disconnected from bus)

Bug#893041: libvirt update fails, dependencies

[Jeff Ketchum]

I am seeing the same issue from my upgrade.
I don't think the entry for Server in the Socket section is the cause.

ar 15 15:32:56 jket-deb systemd[1]: Reloading.
Mar 15 15:32:56 jket-deb systemd[1]:
/lib/systemd/system/virtlockd-admin.socket:7: Unknown lvalue 'Server' in
section 'Socket'
Mar 15 15:32:56 jket-deb systemd[1]: Reloading.
Mar 15 15:32:56 jket-deb audit[29849]: AVC apparmor="DENIED"
operation="signal" profile="/usr/sbin/libvirtd" pid=29849 comm="libvirtd"
requested_mask="send" denied_mask="send" signal=hup pee
Mar 15 15:32:56 jket-deb audit[29849]: AVC apparmor="DENIED"
operation="signal" profile="/usr/sbin/libvirtd" pid=29849 comm="libvirtd"
requested_mask="send" denied_mask="send" signal=hup pee
Mar 15 15:32:56 jket-deb audit[29849]: AVC apparmor="DENIED"
operation="signal" profile="/usr/sbin/libvirtd" pid=29849 comm="libvirtd"
requested_mask="send" denied_mask="send" signal=hup pee
Mar 15 15:32:56 jket-deb kernel: audit: type=1400 audit(1521149576.914:41):
apparmor="DENIED" operation="signal" profile="/usr/sbin/libvirtd" pid=29849
comm="libvirtd" requested_mask="send"
Mar 15 15:32:56 jket-deb kernel: audit: type=1400 audit(1521149576.914:42):
apparmor="DENIED" operation="signal" profile="/usr/sbin/libvirtd" pid=29849
comm="libvirtd" requested_mask="send"
Mar 15 15:32:56 jket-deb kernel: audit: type=1400 audit(1521149576.914:43):
apparmor="DENIED" operation="signal" profile="/usr/sbin/libvirtd" pid=29849
comm="libvirtd" requested_mask="send"
Mar 15 15:32:56 jket-deb systemd[1]:
/lib/systemd/system/virtlockd-admin.socket:7: Unknown lvalue 'Server' in
section 'Socket'
Mar 15 15:32:56 jket-deb systemd[1]: virtlogd-admin.socket: Socket service
virtlogd.service already active, refusing.
Mar 15 15:32:56 jket-deb systemd[1]: Failed to listen on Virtual machine
log manager socket.
-- Subject: Unit virtlogd-admin.socket has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit virtlogd-admin.socket has failed.
-- 
-- The result is RESULT.
Mar 15 15:32:56 jket-deb systemd[1]: Dependency failed for Virtual machine
log manager.
-- Subject: Unit virtlogd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit virtlogd.service has failed.
-- 
-- The result is RESULT.
Mar 15 15:32:56 jket-deb systemd[1]: virtlogd.service: Job
virtlogd.service/start failed with result 'dependency'.
Mar 15 15:32:57 jket-deb sudo[29716]: pam_unix(sudo:session): session
closed for user root
Mar 15 15:32:59 jket-deb sudo[30326]: jket : TTY=pts/6 ; PWD=/home/jket
; USER=root ; COMMAND=/bin/journalctl -xe
Mar 15 15:32:59 jket-deb sudo[30326]: pam_unix(sudo:session): session
opened for user root by (uid=0)

Bug#892979: FLTKConfig.cmake: self-conflicting add_executable(fluid IMPORTED)

[Aaron M. Ucko]

Helmut Grohne  writes:

> In any case, this constellation of add_executable is a pretty obvious
> bug, because FLTKConfig.cmake includes FLTK-Targets.cmake. It just isn't
> obvious how to fix it.

Thanks for the report!  AFAICT, simply commenting out (or further
conditionalizing) FLTKConfig.cmake's add_executable call solves the
problem; I'll upload a fix soon.

-- 
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#893050: pyopencl FTBFS: ModuleNotFoundError: No module named 'pyopencl'

[Adrian Bunk]

Source: pyopencl
Version: 2018.1.1-1
Severity: serious

Some recent change in unstable makes pyopencl FTBFS:

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

...
I: pybuild base:215: make -C /build/1st/pyopencl-2018.1.1/doc html
make[2]: Entering directory '/build/1st/pyopencl-2018.1.1/doc'
python3 make_constants.py > constants.inc
Traceback (most recent call last):
  File "make_constants.py", line 25, in 
import pyopencl as cl
ModuleNotFoundError: No module named 'pyopencl'
make[2]: *** [Makefile:38: constants] Error 1

Bug#893049: libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed

[Adrian Bunk]

Source: libfiu
Version: 0.95-5
Severity: serious

https://buildd.debian.org/status/package.php?p=libfiu=sid

...
./generate-test -c tests/malloc.conf -o tests/malloc.c
make[4]: Leaving directory '/<>/tests/generated'
make[4]: Entering directory '/<>/tests/utils'
LD_LIBRARY_PATH=../../libfiu/ ./test-basic_ctrl.py > 
output-test-basic_ctrl.py.txt 2>&1
Makefile:38: recipe for target 'run-test-basic_ctrl.py' failed
make[4]: *** [run-test-basic_ctrl.py] Error 1

Bug#886399: RFS: opencascade/7.2.0-1 [ITP]

[Tobias Frost]

On Wed, Mar 14, 2018 at 11:46:28AM +0100, Tobias Frost wrote:
> What is still missing from my side is a complete d/copyright review,
> but I need a break right now... Will continue later.

Ok, went over the package for a copyright review.
One part of the result resulted in a MR [1], but not all could 
be fixed with that; could be that we need to repack the source
and/or ask upstream to fix that in their repo too.

I fear that we have some problematic files:
- There are some files from QT examples, but the license header seems to
  be "old" and unfortunatly not distributeable.
  Affected are some files in samples/qt/FuncDemo/src, e.g edge.cpp
  (Later versions of this file seems to be dual-licensed, so likely
  the remedy is to "update" to a newer version by upstream.
  But for now, I guess this samples can be removed from the tarball
  by repacking.
- src/NCollection/NCollection_UtfIterator.lxx
  Is also copyrighted by Unicode Inc. We'll need to have a dedicated
  section in d/copyright for it
- src/OpenGl/glext.h needs also to be documented in d/copyright.
- samples/ios/UIKitSample/UIKitSample/ViewController.* are
  "copyright ... all rights reserverd.".
  I guess we need to delete the iOS example from the tarball...
- opencascade/samples/mfc/standard/06_Ocaf/src/DebugBrowser.hxx
  (example, there are others as well) scares me license wise.
  We will have to delete them (no big loss, as MFC examples are
  not really useful for us) or ask upstream to clarify. 

When we're repackaging anyway, we should also remove all those
Windows-Only samples (and their VS project files)

Otherwise were some years not accurate (fixed in [1]) and some copyright
holders not "verbabitmly" coppied, but else there not much to fix
left...


[1] https://salsa.debian.org/kkremitzki-guest/opencascade/merge_requests/1

--
 tobi

Bug#893048: ITP: dovecot-trees -- Dovecot individually encrypted email storage plugin

[Georg Faerber]

Package: wnpp
Owner: Georg Faerber 
Severity: wishlist

Package name: dovecot-trees
Version : 2.1.0
Upstream Author : David Goulet 
URL : https://0xacab.org/riseuplabs/trees
License : GNU Affero General Public License Version 3
Programming Lang: C
Description : A NaCL-based Dovecot individually encrypted email
storage plugin.

TREES, technology for resting email encrypted storage, adds NaCL-based
individually encrypted email storage to the Dovecot IMAP server.

This plugin is inspired by Posteo's scrambler which uses OpenSSL and RSA
keypairs. TREES works in a similar way, but uses the Sodium crypto
library (based on NaCL).

This package will be maintained within the Debian Dovecot team.


signature.asc
Description: Digital signature

Bug#888127: Fix available in 0.7.1

[Nish Aravamudan]

Specifically, 
https://github.com/ruby-grape/grape-entity/commit/03d3b928ee7d1c48fdfa9bf55b150eee46d5e572

which I believe is in 0.7.0 and 0.7.1. uscan/uupdate finds it, but
patches need refreshing, and there is a new build-dependency on
ruby-simplecov.

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd

Bug#893046: transition: evolution-data-server 3.28

[Jeremy Bicha]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-CC: pkg-gnome-maintain...@lists.alioth.debian.org

I request permission to start the evolution-data-server 3.28
transition once the ongoing gnome-desktop3/libgweather/mutter
transition completes.

https://release.debian.org/transitions/html/auto-evolution-data-server.html

Ubuntu 18.04 successfully completed this transition.

Thanks,
Jeremy Bicha

Bug#893047: maxima FTBFS: INTERNAL-SIMPLE-PACKAGE-ERROR: Package error on #<"MAXIMA" package>: Cannot import symbol as it will produce a name conflict

[Adrian Bunk]

Source: maxima
Version: 5.41.0-2
Severity: serious

Some recent change in unstable makes maxima FTBFS:

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

...
Compiling /build/1st/maxima-5.41.0/src/mhayat.lisp.
End of Pass 1.  
End of Pass 2.  
OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3
Finished compiling binary-gcl/mhayat.o.

;  - Loading binary file "binary-gcl/mhayat.o" 
;- Compiling source file "/build/1st/maxima-5.41.0/src/optimize.lisp" 
Compiling /build/1st/maxima-5.41.0/src/optimize.lisp.
End of Pass 1.  
End of Pass 2.  
OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3
Finished compiling binary-gcl/optimize.o.

;- Loading binary file "binary-gcl/optimize.o" 
Error: 
Fast links are on: do (si::use-fast-links nil) for debugging
Signalled by IMPORT.
Condition in IMPORT [or a callee]: INTERNAL-SIMPLE-PACKAGE-ERROR: Package error 
on #<"MAXIMA" package>: Cannot import symbol as it will produce a name conflict

Broken at IMPORT.  Type :H for Help.
1  Return to top level. 
MAXIMA>>make[2]: *** [Makefile:1305: sys-proclaim.lisp] Error 255

Bug#892978: getmail4: should recommend requirements for --store-password-in-gnome-keyring

[Brian May]

Osamu Aoki  writes:

> FYI: There were discussion to do that with some preliminary porting work
> already in some git repo.  But, at least, the upstream is not
> interested to move getmail to python3.

FYI: Python2 is no longer being supported after 2020, and there is
already talk on debian-python about moving everything to Python3.
-- 
Brian May 

Bug#893045: ITP: mwic -- spell-checker that groups possible misspellings and shows them in their contexts

[Georg Faerber]

Package: wnpp
Owner: Georg Faerber 
Severity: wishlist

Package name: mwic
Version : 0.7.4
Upstream Author : Jakub Wilk 
URL : https://jwilk.net/software/mwic
License : Expat
Programming Lang: Python
Description : spell-checker that groups possible misspellings and
shows them in their contexts

mwic, misspelled words in context, is a spell-checker that groups
possible misspellings and shows them in their contexts. This is useful
for checking technical documents that often contain words that are not
included in standard dictionaries.

This package will be maintained within the Debian Python team.


signature.asc
Description: Digital signature

Bug#893044: slurm-llnl: CVE-2018-7033: Issue in accounting_storage/mysql plugin by always escaping strings within the slurmdbd

[Salvatore Bonaccorso]

Source: slurm-llnl
Version: 14.03.9-5
Severity: grave
Tags: patch security upstream
Forwarded: https://bugs.schedmd.com/show_bug.cgi?id=4792

Hi,

the following vulnerability was published for slurm-llnl, filling as
grave to be on safe side, but details are yet not disclosed in the
upstream report.

CVE-2018-7033[0]:
|Issue in accounting_storage/mysql plugin by always escaping strings
|within the slurmdbd

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-7033
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7033
[1] https://bugs.schedmd.com/show_bug.cgi?id=4792

Regards,
Salvatore

Bug#893041: [Pkg-libvirt-maintainers] Bug#893041: libvirt-daemon: Update of libvirt fails due to dependency issues

[Guido Günther]

On Thu, Mar 15, 2018 at 04:45:33PM -0400, annadane wrote:
> Mar 15 16:31:12 debian systemd[1]: virtlogd.service: Job 
> virtlogd.service/start failed with result 'dependency'.
> Mar 15 16:31:13 debian audit[7512]: AVC apparmor="DENIED" operation="signal" 
> profile="/usr/sbin/libvirtd" pid=7512 comm="libvirtd" requested_mask="send" 
> denie
> Mar 15 16:31:13 debian kernel: audit: type=1400 audit(1521145873.675:75): 
> apparmor="DENIED" operation="signal" profile="/usr/sbin/libvirtd" pid=7512 
> comm="lib
> Mar 15 16:31:14 debian systemd[1]: Reloading.
> Mar 15 16:31:14 debian systemd[1]: 
> /lib/systemd/system/virtlockd-admin.socket:7: Unknown lvalue 'Server' in 
> section 'Socket'

This looks like an error in the unit file. Can you investigate? I don't
have Server in that file (or any of its overrides).
 -- Guido

> Mar 15 16:33:26 debian su[6739]: pam_unix(su:session): session closed for 
> user root
> Mar 15 16:33:32 debian su[7745]: Successful su for root by annadane
> Mar 15 16:33:32 debian su[7745]: + /dev/pts/0 annadane:root
> Mar 15 16:33:32 debian su[7745]: pam_unix(su:session): session opened for 
> user root by (uid=1000)
> Mar 15 16:33:32 debian su[7745]: pam_systemd(su:session): Cannot create 
> session: Already running in a session
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_CA:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages libvirt-daemon depends on:
> ii  libacl1 2.2.52-3+b1
> ii  libapparmor12.12-3
> ii  libaudit1   1:2.8.2-1
> ii  libavahi-client30.7-3.1
> ii  libavahi-common30.7-3.1
> ii  libblkid1   2.31.1-0.5
> ii  libc6   2.27-2
> ii  libcap-ng0  0.7.7-3.1+b1
> ii  libcurl3-gnutls 7.58.0-2
> ii  libdbus-1-3 1.12.6-2
> ii  libdevmapper1.02.1  2:1.02.145-4.1
> ii  libfuse22.9.7-1
> ii  libgnutls30 3.5.18-1
> ii  libnetcf1   1:0.2.8-1+b2
> ii  libnl-3-200 3.2.27-2
> ii  libnl-route-3-200   3.2.27-2
> ii  libnuma12.0.11-2.1
> ii  libparted2  3.2-20
> ii  libpcap0.8  1.8.1-6
> ii  libpciaccess0   0.13.4-1+b2
> ii  libsasl2-2  2.1.27~101-g0780600+dfsg-3
> ii  libselinux1 2.7-2+b1
> ii  libssh2-1   1.8.0-1
> ii  libudev1238-2
> ii  libvirt04.1.0-1
> ii  libxen-4.8  4.8.3+comet2+shim4.10.0+comet3-1+deb9u5
> ii  libxenstore3.0  4.8.3+comet2+shim4.10.0+comet3-1+deb9u5
> ii  libxml2 2.9.4+dfsg1-6.1
> ii  libyajl22.1.0-2+b3
> 
> Versions of packages libvirt-daemon recommends:
> ii  libxml2-utils   2.9.4+dfsg1-6.1
> ii  netcat-openbsd  1.187-1
> ii  qemu-kvm1:2.11+dfsg-1
> 
> Versions of packages libvirt-daemon suggests:
> pn  libvirt-daemon-driver-storage-gluster   
> pn  libvirt-daemon-driver-storage-rbd   
> pn  libvirt-daemon-driver-storage-sheepdog  
> pn  libvirt-daemon-driver-storage-zfs   
> ih  libvirt-daemon-system   4.1.0-1
> pn  numad   
> 
> -- no debconf information
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Bug#886693: linux: please reinstate ia64 for the linux kernel package

[Ben Hutchings]

Control: tag -1 - moreinfo
Control: tag -1 pending

I got fed up of seeing ia64 build failures so I've re-added ia64
configurations on the master branch.

On Wed, 2018-01-17 at 01:20 +, Ben Hutchings wrote:
> Control: tag -1 moreinfo
> 
> On Mon, 2018-01-08 at 19:04 -0500, Jason Duerstock wrote:
> > Source: linux
> > Severity: normal
> > Tags: patch
> > 
> > Dear Maintainer,
> > 
> > As you may be aware, the ia64 architecture has recently been added
> > back to Debian, but now resides in Debian ports.
> > The attached patch should enable the linux package to build the ia64
> > kernel again.
> > 
> > Thanks for your time!
> 
> This appears to be almost exactly reverting the change I made to remove
> ia64 support, which is not the right thing to do.
> 
> You need to actually review the changes that have happened in the 2.5
> years since then and update the config accordingly.  In particular, the
> following symbols no longer exist in Linux 4.15-rc8:
> 
> CONFIG_BLK_CPQ_CISS_DA
> CONFIG_BLK_CPQ_DA
> CONFIG_CISS_SCSI_TAPE
> CONFIG_I2O
> CONFIG_I2O_BLOCK
> CONFIG_I2O_CONFIG
> CONFIG_I2O_PROC
> CONFIG_I2O_SCSI
> CONFIG_MMTIMER
> CONFIG_SCSI_DC390T

I deleted all of these from the configuration.

> The commit message for the removal of CONFIG_MMTIMER upstream (commit
> 07903ada96139ced48f2f893fe57a26a8fbc6043) implies that SGI SN2 systems
> are no longer supported, in which case presumably the sn-modules udeb
> should also be removed.

I was confused about this; there evidently is still general support for
SN2 systems.

> Do Itanium systems typically have floppy drives?  If not, delete the
> "suggests: fdutils" from debian/config/ia64/defines.

I've done this.

> Shouldn't the "mckinley" configuration be renamed, since it's supposed
> to support later processors as well?
>
> Does it still make sense to build an "itanium" configuration, given how
> few Merced systems exist?

I've left the flavour names as they are but changed their descriptions.

> Also, do you have any idea whether these bugs have been fixed upstream:
> 
> https://bugs.debian.org/679545

This seems to be unfixed (the patches weren't applied upstream).

> https://bugs.debian.org/691576

This seems to have been a gcc bug that is now fixed.

> https://bugs.debian.org/728706

Unknown.

> If not, those should be reopened when ia64 is enabled again.

Ben.

-- 
Ben Hutchings
Quantity is no substitute for quality, but it's the only one we've got.



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

Bug#893043: stretch-pu: package nss-pam-ldapd/0.9.7-2+deb9u1

[Salvatore Bonaccorso]

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

Hi Stable release managers, 

X-Debbugs-CC explicitly to Arthur, Debian maintainer of nss-pam-ldapd
*and* upstream.

src:nss-pam-ldapd is affected in stable (and alrady fixed
correspondigly in unstable and testing) by #890508, which under
certian circumstances (like the ones outlined in the bug, pam stack
configured with pam_ldap, UseDNS=yes in sshd_config, and a remote
hostname which is longer than 64 bytes), can lead to authentication
failure. That is just one way to trigger the issue. It would be as
well by any rhost value which matches the problem.

Debian Bug report at: https://bugs.debian.org/890508
Upstream report: https://github.com/arthurdejong/nss-pam-ldapd/issues/22

Upstream commit message:

> Increase size of hostname buffer
>
> This increases the host name buffer to support host names (that
> include FQDNs) to 255 characters and removes the reliance on
> HOST_NAME_MAX and _POSIX_HOST_NAME_MAX which may be smaller in some
> situations.

Attached is the proposed (NMU) debdiff for the upload, but if you ack
the changes and Arthur would like to do the actual upload, then I'm
happy to withdrawn my debdiff.

Can you please consider the change to be accepted for the next stretch
point release?

Regards,
Salvatore
diff -Nru nss-pam-ldapd-0.9.7/debian/changelog 
nss-pam-ldapd-0.9.7/debian/changelog
--- nss-pam-ldapd-0.9.7/debian/changelog2017-01-22 16:00:00.0 
+0100
+++ nss-pam-ldapd-0.9.7/debian/changelog2018-03-08 14:11:25.0 
+0100
@@ -1,3 +1,14 @@
+nss-pam-ldapd (0.9.7-2+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Increase size of hostname buffer.
+This increases the host name buffer to support host names (that include
+FQDNs) to 255 characters and removes the reliance on HOST_NAME_MAX and
+_POSIX_HOST_NAME_MAX which may be smaller in some situations.
+(Closes: #890508)
+
+ -- Salvatore Bonaccorso   Thu, 08 Mar 2018 14:11:25 +0100
+
 nss-pam-ldapd (0.9.7-2) unstable; urgency=medium
 
   * recommend ca-certificate which is needed due to adding tls_cacertfile by
diff -Nru 
nss-pam-ldapd-0.9.7/debian/patches/Increase-size-of-hostname-buffer.patch 
nss-pam-ldapd-0.9.7/debian/patches/Increase-size-of-hostname-buffer.patch
--- nss-pam-ldapd-0.9.7/debian/patches/Increase-size-of-hostname-buffer.patch   
1970-01-01 01:00:00.0 +0100
+++ nss-pam-ldapd-0.9.7/debian/patches/Increase-size-of-hostname-buffer.patch   
2018-03-08 14:11:25.0 +0100
@@ -0,0 +1,61 @@
+From: Arthur de Jong 
+Date: Fri, 16 Feb 2018 22:13:19 +0100
+Subject: Increase size of hostname buffer
+Origin: 
https://github.com/arthurdejong/nss-pam-ldapd/commit/c05e3265b7f62b83937f204119555c6a73f29b29
+Bug-Debian: https://bugs.debian.org/890508
+Bug: https://github.com/arthurdejong/nss-pam-ldapd/issues/22
+
+This increases the host name buffer to support host names (that include
+FQDNs) to 255 characters and removes the reliance on HOST_NAME_MAX and
+_POSIX_HOST_NAME_MAX which may be smaller in some situations.
+
+Closes https://github.com/arthurdejong/nss-pam-ldapd/issues/22
+---
+ nslcd/cfg.c|  4 ++--
+ nslcd/common.h | 13 ++---
+ 2 files changed, 4 insertions(+), 13 deletions(-)
+
+diff --git a/nslcd/cfg.c b/nslcd/cfg.c
+index 60d860e..348e800 100644
+--- a/nslcd/cfg.c
 b/nslcd/cfg.c
+@@ -425,7 +425,7 @@ static void add_uris_from_dns(const char *filename, int 
lnr,
+ {
+   int rc;
+   char *hostlist = NULL, *nxt;
+-  char buf[HOST_NAME_MAX + sizeof("ldap://;)];
++  char buf[BUFLEN_HOSTNAME + sizeof("ldap://;)];
+   log_log(LOG_DEBUG, "query %s for SRV records", domain);
+   rc = ldap_domain2hostlist(domain, );
+   if (rc != LDAP_SUCCESS)
+diff --git a/nslcd/common.h b/nslcd/common.h
+index ffa07ba..26fcf48 100644
+--- a/nslcd/common.h
 b/nslcd/common.h
+@@ -150,15 +150,6 @@ int invalidator_start(void);
+ /* signal invalidator to invalidate the selected external cache */
+ void invalidator_do(enum ldap_map_selector map);
+ 
+-/* fallback definition of HOST_NAME_MAX */
+-#ifndef HOST_NAME_MAX
+-#ifdef _POSIX_HOST_NAME_MAX
+-#define HOST_NAME_MAX _POSIX_HOST_NAME_MAX
+-#else
+-#define HOST_NAME_MAX 255
+-#endif /* _POSIX_HOST_NAME_MAX */
+-#endif /* not HOST_NAME_MAX */
+-
+ /* common buffer lengths */
+ #define BUFLEN_NAME 256  /* user, group names and such */
+ #define BUFLEN_SAFENAME 300  /* escaped name */
+@@ -167,7 +158,7 @@ void invalidator_do(enum ldap_map_selector map);
+ #define BUFLEN_DN   512  /* distinguished names */
+ #define BUFLEN_SAFEDN   600  /* escapedd dn */
+ #define BUFLEN_FILTER  4096  /* search filters */
+-#define BUFLEN_HOSTNAME (HOST_NAME_MAX + 1)  /* host names (+ escaped) */
++#define BUFLEN_HOSTNAME 256  /* host names or FQDN (and safe version) */
+ #define BUFLEN_MESSAGE 1024  /* message strings */
+ 
+ /* provide 

Bug#893042: debci: don't test a package one last time after removal; it fails (and polutes the alerts page)

[Paul Gevers]

Package: debci
Version: 1.7.1
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Currently, the alerts page¹ of ci.d.n report at least two package that were
removed from the archive, because they were last tested (probably the removal
triggered it) after removal: apq and aptdaemon, but maybe more.

The triggering mechanism should probably be fixed to not test in the case of
removal.

Paul

¹ https://ci.debian.net/status/alerts/

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

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

Versions of packages debci depends on:
ii  adduser 3.117
ii  amqp-tools  0.8.0-1+b3
ii  bsdmainutils11.1.2
ii  dctrl-tools 2.24-2+b1
ii  debootstrap 1.0.93
ii  devscripts  2.18.1
ii  fonts-font-awesome  4.7.0~dfsg-3
ii  jq  1.5+dfsg-2
ii  libjs-bootstrap 3.3.7+dfsg-2
ii  libjs-jquery3.2.1-1
ii  libjs-jquery-flot   0.8.3+dfsg-1
ii  patchutils  0.3.4-2
ii  ruby1:2.5.0
ii  sudo1.8.21p2-3

Versions of packages debci recommends:
ii  chrony [time-daemon]  3.2-4
ii  moreutils 0.60-1

Versions of packages debci suggests:
ii  apt-cacher-ng  3.1-1

- -- Configuration Files:
/etc/sudoers.d/debci [Errno 13] Permission denied: '/etc/sudoers.d/debci'

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlqq280ACgkQnFyZ6wW9
dQpvoQf+JNZQZbsKLyS/ZF2ttHqSPNv9xCyNOSlLAA231fLg/E9XkY/6FzmuIizg
8iXm4Nbb6gXnKzq1Uq+owPOAgN23yAV6WiQk5x0+aq6JcbFxkgh45mlTNLkr+ew9
H7GliS3jhKzQhrwjnFp7Gvdtpx7rE70UkA3CzBgFZT3AitzP/bHTut+ywqFkTFKf
t6JJNUVtCeMRJHZUBvh6QAOj2ae63c9iqD8CRc13wIuIctrTpWLkF+f99MMCAywM
Kxzf7TsPnOPsCHsL84VybQPm9Ue+3/GR+Gmfgwhs7sdzeZXoJJrWrkdDo1odSa1t
Fh0aP1HoeIN1ydEAvovzli/ui3w94A==
=MIzG
-END PGP SIGNATURE-

Bug#893041: libvirt-daemon: Update of libvirt fails due to dependency issues

[annadane]

Package: libvirt-daemon
Version: 4.1.0-1
Severity: normal

Dear Maintainer,

(I hope this is filed under the right package, apologies if not)

An update of libvirt fails, giving the following:

annadane@debian:~$ su -
Password: 
root@debian:~# apt update
Get:1 http://ftp.ca.debian.org/debian sid InRelease [241 kB]
Get:2 http://ftp.ca.debian.org/debian sid/main Sources.diff/Index [27.9 kB]
Get:3 http://ftp.ca.debian.org/debian sid/main amd64 Packages.diff/Index [27.9 
kB]
Get:4 http://ftp.ca.debian.org/debian sid/main Translation-en.diff/Index [27.9 
kB]
Get:5 http://ftp.ca.debian.org/debian sid/contrib amd64 Packages.diff/Index 
[27.8 kB]
Get:6 http://ftp.ca.debian.org/debian sid/main Sources 2018-03-15-1424.33.pdiff 
[22.8 kB]
Get:7 http://ftp.ca.debian.org/debian sid/main amd64 Packages 
2018-03-15-1424.33.pdiff [27.9 kB]
Get:8 http://ftp.ca.debian.org/debian sid/main Translation-en 
2018-03-15-1424.33.pdiff [5,437 B]
Get:6 http://ftp.ca.debian.org/debian sid/main Sources 2018-03-15-1424.33.pdiff 
[22.8 kB]
Get:9 http://ftp.ca.debian.org/debian sid/contrib amd64 Packages 
2018-03-15-1424.33.pdiff [259 B]
Get:8 http://ftp.ca.debian.org/debian sid/main Translation-en 
2018-03-15-1424.33.pdiff [5,437 B]
Get:7 http://ftp.ca.debian.org/debian sid/main amd64 Packages 
2018-03-15-1424.33.pdiff [27.9 kB]
Get:9 http://ftp.ca.debian.org/debian sid/contrib amd64 Packages 
2018-03-15-1424.33.pdiff [259 B]
Fetched 409 kB in 3s (146 kB/s)
Reading package lists... Done
Building dependency tree   
Reading state information... Done
10 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@debian:~# apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  gir1.2-gtk-3.0 gtk-update-icon-cache libgail-3-0 libgtk-3-0 libgtk-3-bin
  libgtk-3-common libvirt-clients libvirt-daemon libvirt-daemon-system
  libvirt0
10 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 13.8 MB of archives.
After this operation, 24.1 MB disk space will be freed.
Do you want to continue? [Y/n] 
Get:1 http://ftp.ca.debian.org/debian sid/main amd64 libgtk-3-common all 
3.22.29-1 [3,509 kB]
Get:2 http://ftp.ca.debian.org/debian sid/main amd64 libgail-3-0 amd64 
3.22.29-1 [74.9 kB]
Get:3 http://ftp.ca.debian.org/debian sid/main amd64 libgtk-3-0 amd64 3.22.29-1 
[2,573 kB]
Get:4 http://ftp.ca.debian.org/debian sid/main amd64 gir1.2-gtk-3.0 amd64 
3.22.29-1 [247 kB]
Get:5 http://ftp.ca.debian.org/debian sid/main amd64 gtk-update-icon-cache 
amd64 3.22.29-1 [78.1 kB]
Get:6 http://ftp.ca.debian.org/debian sid/main amd64 libgtk-3-bin amd64 
3.22.29-1 [111 kB]
Get:7 http://ftp.ca.debian.org/debian sid/main amd64 libvirt-daemon-system 
amd64 4.1.0-1 [106 kB]
Get:8 http://ftp.ca.debian.org/debian sid/main amd64 libvirt-daemon amd64 
4.1.0-1 [1,815 kB]
Get:9 http://ftp.ca.debian.org/debian sid/main amd64 libvirt-clients amd64 
4.1.0-1 [636 kB]
Get:10 http://ftp.ca.debian.org/debian sid/main amd64 libvirt0 amd64 4.1.0-1 
[4,640 kB]
Fetched 13.8 MB in 0s (28.3 MB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 177858 files and directories currently installed.)
Preparing to unpack .../0-libgtk-3-common_3.22.29-1_all.deb ...
Unpacking libgtk-3-common (3.22.29-1) over (3.22.28-1) ...
Preparing to unpack .../1-libgail-3-0_3.22.29-1_amd64.deb ...
Unpacking libgail-3-0:amd64 (3.22.29-1) over (3.22.28-1) ...
Preparing to unpack .../2-libgtk-3-0_3.22.29-1_amd64.deb ...
Unpacking libgtk-3-0:amd64 (3.22.29-1) over (3.22.28-1) ...
Preparing to unpack .../3-gir1.2-gtk-3.0_3.22.29-1_amd64.deb ...
Unpacking gir1.2-gtk-3.0:amd64 (3.22.29-1) over (3.22.28-1) ...
Preparing to unpack .../4-gtk-update-icon-cache_3.22.29-1_amd64.deb ...
Unpacking gtk-update-icon-cache (3.22.29-1) over (3.22.28-1) ...
Preparing to unpack .../5-libgtk-3-bin_3.22.29-1_amd64.deb ...
Unpacking libgtk-3-bin (3.22.29-1) over (3.22.28-1) ...
Preparing to unpack .../6-libvirt-daemon-system_4.1.0-1_amd64.deb ...
Unpacking libvirt-daemon-system (4.1.0-1) over (4.0.0-2) ...
Preparing to unpack .../7-libvirt-daemon_4.1.0-1_amd64.deb ...
Unpacking libvirt-daemon (4.1.0-1) over (4.0.0-2) ...
Preparing to unpack .../8-libvirt-clients_4.1.0-1_amd64.deb ...
Unpacking libvirt-clients (4.1.0-1) over (4.0.0-2) ...
Preparing to unpack .../9-libvirt0_4.1.0-1_amd64.deb ...
Unpacking libvirt0 (4.1.0-1) over (4.0.0-2) ...
Setting up libgtk-3-common (3.22.29-1) ...
Setting up libvirt0 (4.1.0-1) ...
Processing triggers for libglib2.0-0:amd64 (2.54.3-2) ...
Setting up libgtk-3-0:amd64 (3.22.29-1) ...
Setting up gtk-update-icon-cache (3.22.29-1) ...
Setting up libvirt-daemon (4.1.0-1) ...
Processing triggers for libc-bin (2.27-2) ...
Processing triggers for systemd (238-2) ...
Setting up libgail-3-0:amd64 

Bug#893040: libseafile0: contains a python module

[Helmut Grohne]

Package: libseafile0
Version: 6.1.5-1
Severity: serious
Justification: policy 8.2

libseafile0 contains a python module "ccnet". The Debian policy section
8.2 prohibits shipping soname-independent files with the shared library
package:

| If your package contains files whose names do not change with each
| change in the library shared object version, you must not put them in
| the shared library package.

Please package it separately in a properly named python-seafile package.

Helmut

Bug#893039: libccnet0: contains a python module

[Helmut Grohne]

Package: libccnet0
Version: 6.1.5-1
Severity: serious
Justification: policy 8.2

libccnet0 contains a python module "ccnet". The Debian policy section
8.2 prohibits shipping soname-independent files with the shared library
package:

| If your package contains files whose names do not change with each
| change in the library shared object version, you must not put them in
| the shared library package.

Please package it separately in a properly named python-ccnet package
(that already exists somewhat in debian/control).

Helmut

Bug#893038: fails to retry ace-window for > 6 months (after tmpfail)

[Paul Gevers]

Package: debci
Version: 1.7.1
Severity: normal
Control: affects -1 src:ace-window

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Currently (2018-03-15) one can see that ace-window¹ hasn't seen a test since
2017-07-26 21:38:52 UTC. The last test had this:

```
Version  Date Duration  Status  
n/a  2017-07-26 21:38:52 UTC  0h 0m 0s  tmpfail
```

I have seen that more often, but normally debci recovers from that situation
after a while.

This causes ace-window to be reported as failure in other places like the PTS,
while all but a couple of the other test runs were succesful. This is probably
a bug somewhere in debci-batch.

Paul

¹ https://ci.debian.net/packages/a/ace-window/unstable/amd64/

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

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

Versions of packages debci depends on:
ii  adduser 3.117
ii  amqp-tools  0.8.0-1+b3
ii  bsdmainutils11.1.2
ii  dctrl-tools 2.24-2+b1
ii  debootstrap 1.0.93
ii  devscripts  2.18.1
ii  fonts-font-awesome  4.7.0~dfsg-3
ii  jq  1.5+dfsg-2
ii  libjs-bootstrap 3.3.7+dfsg-2
ii  libjs-jquery3.2.1-1
ii  libjs-jquery-flot   0.8.3+dfsg-1
ii  patchutils  0.3.4-2
ii  ruby1:2.5.0
ii  sudo1.8.21p2-3

Versions of packages debci recommends:
ii  chrony [time-daemon]  3.2-4
ii  moreutils 0.60-1

Versions of packages debci suggests:
ii  apt-cacher-ng  3.1-1

- -- Configuration Files:
/etc/sudoers.d/debci [Errno 13] Permission denied: '/etc/sudoers.d/debci'

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlqq2RkACgkQnFyZ6wW9
dQp/kggAg5uWXZDBArZzWd2+enYnHsaOXtx2xerTH4LvzJKQvau+cLVoSMEPmCoX
Ya1MxEs+S1zYjT6zECLJTIKmYYoS21vnbw7GsImr1GDqDvLsTTARx7z5gN5q3yLZ
UmYNux9rIIDCDvO6WaZW6u5zTJqdW64iC/QHiNovo55U0UcAFyRItXVOcZccqj6y
vIG66ktOHLcLC7SfZWYyLHuI3D+8HocIJrxtGlBfs0tT1gIclAOUBEoV19enM2qa
TqWlIWFeXyClI9kqRMLzlGMD6G4vwfuzIe+8xTIzduP6cPmrhLnBVmXRtAQmAkPf
ptHBN/fkjR+xmKMNdEiq1vBRgfersA==
=Y4OF
-END PGP SIGNATURE-

Bug#893037: Add support for diffing docker-format containers

[Jonathan Dowland]

Package: src:diffoscope
Severity: wishlist


It would be nice if diffoscope could diff against docker containers available
on the local system.


-- System Information:
Debian Release: 9.3
 APT prefers stable
 APT policy: (990, 'stable'), (600, 'unstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.12-x86_64-linode92 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Bug#893036: anosql: please drop autopkgtest and use autodep8 framework

[Paul Gevers]

Source: anosql
Version: 0.2.0-1
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

I just discovered that your autopkgtest¹ are causing the testing framework of
Debian to crash. Although that should be fixed elsewhere², you may consider
dropping the test altogether if you are not going to enhance the test, as the
same functionality of the current test can be achieved via autodep8, see
"Automatic test control file for known package types" at ³.

You probably need your package whitelisted if you go that route. I think iron
out the procedure to be added is work-in-progress, so probably drop by on IRC
at #debci.

Paul

¹ https://ci.debian.net/packages/a/anosql/unstable/amd64/
² https://bugs.debian.org/893035
³ 
https://salsa.debian.org/ci-team/autopkgtest/blob/master/doc/README.package-tests.rst

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlqq1f4ACgkQnFyZ6wW9
dQrTcAf/YdVO1smOe0ok8eaI8PS/s4wMXxNX6ikdeqPjSLEst1uIweGFLlc3o6ZE
T7Nsw1qo++FEPb/CWH9H0EAzsjLZN0izwUDYqSSdCoYmpsnlg49+IHXBxu8q9C4/
ctwHj2r3fsvRzoaJzqpjkwpXboXD5HdDdm1X1s2n0dgf58chUrSJENUP3t3Zrhvq
hnCFfTTD4wpL3spur6VT6haFPq4YHYGNo2rET9VXwsZ1WTqZVBnXf5kpVWHiDYNM
RIJg7BRTuD1qLZJdpMBteoJlONxkMABQvEXnk/+X6CSPoUAJmSgBlibQmwCTd5NK
wd319cNhRHoBo2axLkr0Ft0V7PIIKg==
=h3Pa
-END PGP SIGNATURE-

Bug#892722: Place the files there manually?

[Wolfgang Schweer]

On Tue, Mar 13, 2018 at 08:37:28PM -0500, Simon Quigley wrote:
> One thing I would like you to try (to see if this does indeed work) is 
> to install the voice packages in /usr/share/gcompris-qt/boards/voices/ 
> (just like the old voice packages did, but manually).

Yes, it works; tested in a Debian Edu Buster multi-user environment with
manually downloaded voices-.rcc files plus the 
Contents index file placed in the proposed directory.
 
> What I'm trying to see here is if I can package these and they will Just
> Work, or if I need to do some magic within the GCompris-Qt code itself.

Well, some magic would be welcome.

With the voices files available in /usr/share/gcompris-qt/boards/voices/ 
users wouldn't have to download them (coming in handy in places with 
poor net connectivity or other restrictions), but the voices files are 
cached in addition in each user's home directory in this place:
$HOME/.cache/KDE/gcompris-qt/data2/voices-ogg/
So as far as disk space is concerned, it makes no difference.

Also, a lot of files are stored in a user's subdir
$HOME/.cache/KDE/gcompris-qt/qmlcache/

This is what I was able to find out:

Providing a file /etc/X11/Xsession.d/07debian-edu-gcompris-qt
with content:
QML_DISABLE_DISK_CACHE=1
export QML_DISABLE_DISK_CACHE=1
would avoid caching the QML files for all users.

To avoid caching the voices files I modified each single user's 
$HOME/.config/gcompris/gcompris-qt.conf file (Admin section):

[Admin]
cachePath=/dev/null

This worked, but it would be nice if a smarter solution could be found 
to set the cache path system wide (maybe via preseeding the package or 
modifying a default cache path in a central place).

Wolfgang


signature.asc
Description: PGP signature

Bug#893035: autopkgtest: doesn't escape commands in Test-Command properly, causing "testbed failure: cannot send to testbed"

[Paul Gevers]

Package: autopkgtest
Version: 5.1
Severity: normal
Control: owner !

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The current test suite of anosql has this in the d/t/control file:
'''
Test-Command: python -c 'import anosql; print("Anosql successfully installed")'
Depends: python3-anosql
'''

The log¹ on ci.d.n end with the following:
'''
autopkgtest [12:05:09]: test command1: python -c 'import anosql; print("Anosql 
successfully installed")'
autopkgtest [12:05:09]: test command1: [---
bash: -c: line 0: syntax error near unexpected token `"Anosql successfully 
installed"'
bash: -c: line 0: `set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 
|| true;  . ~/.profile >/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.ybez4dec/downtmp/build.sSE/src"; mkdir -p -m 
1777 -- "/tmp/autopkgtest-lxc.ybez4dec/downtmp/command1-artifacts"; export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.ybez4dec/downtmp/command1-artifacts";
 export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.ybez4dec/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.ybez4dec/downtmp/autopkgtest_tmp"; export 
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE LC_CTYPE 
LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME 
LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f 
/tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set 
+C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd 
"$buildtree"; touch /tmp/autopkgtest-lxc.ybez4dec/downtmp/command1-stdout 
/tmp/autopkgtest-lxc.ybez4dec/downtmp/command1-stderr; bash -ec 'python -c 
'import anosql; print("Anosql successfully installed")'' 2> >(tee -a 
/tmp/autopkgtest-lxc.ybez4dec/downtmp/command1-stderr >&2) > >(tee -a 
/tmp/autopkgtest-lxc.ybez4dec/downtmp/command1-stdout);'
autopkgtest [12:05:10]: test command1: ---]
Unexpected error:
Traceback (most recent call last):
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 717, in mainloop
command()
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 646, in command
r = f(c, ce)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 584, in cmd_copyup
copyupdown(c, ce, True)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 469, in copyupdown
copyupdown_internal(ce[0], c[1:], upp)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 494, in 
copyupdown_internal
copyup_shareddir(sd[0], sd[1], dirsp, downtmp_host)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 408, in 
copyup_shareddir
shutil.copy(tb, host)
  File "/usr/lib/python3.5/shutil.py", line 241, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.5/shutil.py", line 120, in copyfile
with open(src, 'rb') as fsrc:
FileNotFoundError: [Errno 2] No such file or directory: 
'/tmp/autopkgtest-lxc.ybez4dec/downtmp/command1-stdout'
autopkgtest [12:05:11]: ERROR: testbed failure: cannot send to testbed: [Errno 
32] Broken pipe
'''

Obviously, the single quotes in the Test-Command should be escaped.

Paul

¹ 
https://ci.debian.net/data/autopkgtest/unstable/amd64/a/anosql/20180315_120445/log.gz


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

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

Versions of packages autopkgtest depends on:
ii  apt-utils   1.6~beta1
ii  libdpkg-perl1.19.0.5
ii  procps  2:3.3.12-4
ii  python3 3.6.4-1
ii  python3-debian  0.1.32

Versions of packages autopkgtest recommends:
ii  autodep8  0.11.1

Versions of packages autopkgtest suggests:
ii  lxc  1:2.0.9-6
pn  lxd-client   
pn  qemu-system  
ii  qemu-utils   1:2.11+dfsg-1
ii  schroot  1.6.10-4

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlqq0wIACgkQnFyZ6wW9
dQpWjgf/eTNnLG7Dobp+/CgdSQoZHMdnX17ZtxtWJw726kqJjo4qdv5o11dJYUb1
rRAw9+Gvr/ZU26Y/SGq+0+Tvq1QsWduRPS9R0OXFJJ9KDDlvlcpJwa/qEFh2hHtT
wcckJfY9uBMFutp/PsR9V7nb175jOmNLIab9U0QSJ/dB5uVWqnKznjsnjcAbfKO2
ddswQBnKiZHeXorHbAJbXHo9sSJAT51qKC0YVQR5R+kMvDK9dgiZVk0VAyOTG81T
LEwrAIaxmoLvPVaQu+UqH8JdGY4hjYcC0bkGdL3ejwi3GN6pc1bef5nfBAhguD1Z
hp5LPSaok3U2smM6sxV2+8Jd2sqGFw==
=zdHG
-END PGP SIGNATURE-

Bug#886328: live-boot: Please use /run/live instead of /lib/live/mount

[Raphael Hertzog]

On Thu, 15 Mar 2018, Benjamin Drung wrote:
> I have finally tested git master and found one missing rename of
> /live/overlay (probably caused by applying my patches in a different
> order which causes merge conflicts). See
> https://salsa.debian.org/live-team/live-boot/merge_requests/6
> for a fix.

Merged, thanks.

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#876152: marked as done (RFS: luakit/2017.08.10-1)

[Grégory DAVID]

merge 876152 890346
stop

-- 
DAVID Grégory
Libre Software Developer
d...@groolot.net

https://framagit.org/groolot
https://github.com/groolot


signature.asc
Description: PGP signature

Bug#893034: mark gmpc-data Multi-Arch: foreign

[Helmut Grohne]

Package: gmpc-data
Version: 11.8.16-13
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:gmpc-plugins

gmpc-plugins cannot satisfy its cross Build-Depends, because its
transitive dependency on gmpc-data is unsatisfiable. In general,
Architecture: all packages can never satify cross Build-Depends unless
marked Multi-Arch: foreign. In this case such a marking is correct,
because gmpc-data entirely lacks dependencies and its maintainer scripst
are safe in such a setting (updating icon caches). While at it, we can
also mark gmpc-dev Multi-Arch: same. Please consider applying the
attached patch.

Helmut
diff --minimal -Nru gmpc-11.8.16/debian/changelog gmpc-11.8.16/debian/changelog
--- gmpc-11.8.16/debian/changelog   2018-02-04 12:06:55.0 +0100
+++ gmpc-11.8.16/debian/changelog   2018-03-15 20:43:24.0 +0100
@@ -1,3 +1,11 @@
+gmpc (11.8.16-13.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark gmpc-dev Multi-Arch: same.
+  * Mark gmpc-data Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 15 Mar 2018 20:43:24 +0100
+
 gmpc (11.8.16-13) unstable; urgency=medium
 
   * Drop -dbg package and migrate to automatic -dbgsym package
diff --minimal -Nru gmpc-11.8.16/debian/control gmpc-11.8.16/debian/control
--- gmpc-11.8.16/debian/control 2018-02-04 12:06:55.0 +0100
+++ gmpc-11.8.16/debian/control 2018-03-15 20:43:21.0 +0100
@@ -44,6 +44,7 @@
 
 Package: gmpc-dev
 Architecture: any
+Multi-Arch: same
 Depends: gmpc (= ${binary:Version}),
  libmpd-dev,
  pkg-config,
@@ -63,6 +64,7 @@
 
 Package: gmpc-data
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}
 Recommends: gmpc
 Replaces: gmpc (<< 0.20.0-2)

Bug#893033: bsdmainutils: "look" can't look in block devices or files bigger than 2GiB

[Stephane Chazelas]

Package: bsdmainutils
Version: 11.1.2
Severity: normal
Tags: patch

Dear Maintainer,

Background: I was trying to use "look -b" on the "have I been
pwned" password database
(https://downloads.pwnedpasswords.com/passwords/pwned-passwords-ordered-2.0.txt.7z)
That file is about 32GiB uncompressed and contains a sorted list
of SHA1 hashes of compromised passwords.

On that file, "look" reports a "file too big" error. That error
is because "look" checks the size of the file against
SIZE_T_MAX. However, SIZE_T_MAX is defined as INT_MAX:

usr.bin/look/Makefile:FLAGS = -include bsd/err.h -DSIZE_T_MAX=INT_MAX

On 64bit systems however (like Debian GNU/Linux on amd64),
size_t (and the size argument passed to mmap()) is generally
64bit (so LONG_MAX), so removing that check (if
((uintmax_t)sb.st_size > (uintmax_t)SIZE_T_MAX) err()) allowed
me to use "look" on that file.

Now, that file is 32GiB uncompressed and 10GiB compressed with
"pixz". And it is possible to do random access on a
pixz-compressed file (a xz file with 16MiB blocks compressed
individually) including mmaping it by using nbdkit and its "xz"
module.

By doing:

sudo nbdkit -n -U - --run 'nbd-client -nofork -u "${nbd#nbd:unix:}" /dev/nbd0' 
xz file=hibp.xz

One can access the uncompressed data via the /dev/nbd0 block
device. And mmap()ing that block device is also working as
expected.

However, "look" uses fstat() to determine the size of the file
(to be passed to mmap()) and on Linux, stat().st_size is 0 for
block devices, so "look" considers them as empty and skips them.

Using lseek(SEEK_END) instead would allow to get the size of the
file (mmappable files are also seekable).

Using the patch below, "look" now can look password hashes
up in under 2 seconds on my system on the pixz-compressed password
hash database.

--- bsdmainutils/usr.bin/look/look.c2018-03-15 15:45:54.224846742 +
+++ bsdmainutils/usr.bin/look/look.c2018-03-15 15:42:22.444143574 +
@@ -104,7 +104,6 @@
 int
 main(int argc, char *argv[])
 {
-   struct stat sb;
int ch, fd, match;
wchar_t termchar;
unsigned char *back, *front;
@@ -152,17 +151,19 @@
match = 1;
 
do {
-   if ((fd = open(file, O_RDONLY, 0)) < 0 || fstat(fd, ))
+   off_t size;
+   if ((fd = open(file, O_RDONLY, 0)) < 0)
err(2, "%s", file);
-   if ((uintmax_t)sb.st_size > (uintmax_t)SIZE_T_MAX)
-   errx(2, "%s: %s", file, strerror(EFBIG));
-   if (sb.st_size == 0) {
+   if ((size = lseek(fd, 0, SEEK_END)) < 0)
+   err(2, "%s", file);
+   if (size == 0) {
close(fd);
continue;
}
-   if ((front = mmap(NULL, (size_t)sb.st_size, PROT_READ, 
MAP_SHARED, fd, (off_t)0)) == MAP_FAILED)
+   lseek(fd, 0, SEEK_SET);
+   if ((front = mmap(NULL, (size_t)size, PROT_READ, MAP_SHARED, 
fd, (off_t)0)) == MAP_FAILED)
err(2, "%s", file);
-   back = front + sb.st_size;
+   back = front + size;
if (bflag)
 match *= (look(key, front, back));
 else

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-updates'), (500, 'oldstable-updates'), (500, 'testing'), (500, 
'stable'), (500, 'oldstable'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages bsdmainutils depends on:
ii  bsdutils 1:2.31.1-0.4
ii  debianutils  4.8.4
ii  libbsd0  0.8.7-1
ii  libc62.27-1
ii  libtinfo56.1-1

bsdmainutils recommends no packages.

Versions of packages bsdmainutils suggests:
ii  cpp 4:7.2.0-1d1
ii  miscfiles [wordlist]1.5+dfsg-2
pn  vacation
ii  wamerican [wordlist]2017.08.24-1
ii  wbritish [wordlist] 2017.08.24-1
ii  wbritish-insane [wordlist]  2017.08.24-1
ii  wdutch [wordlist]   1:2.10-6
ii  wfrench [wordlist]  1.2.3-11
ii  whois   5.3.0
ii  wngerman [wordlist] 20161207-4
ii  wnorwegian [wordlist]   2.2-3
ii  wswedish [wordlist] 1.4.5-2.2
ii  wukrainian [wordlist]   1.7.1-2

-- no debconf information

Bug#892275: [redshift]

[gregor herrmann]

Control: tag -1 unreproducible
Control: severity -1 important

On Wed, 07 Mar 2018 14:45:29 +0100, Wild Turtles wrote:

> Package: redshift
> Version: 1.11-1
> Severity: grave
> 
> Redshift (and -gtk) crash at startup.
> 
> Error message is the next : 
> 
> Failed to run Redshift
> Trying location provider 'geoclue2' …
> Unable to connect to GeoClue.
> Unable to get location from provider.

redshift still works for me (haven't tried redshift-gtk), both with
the manual and the geoclue2 location provider.
I'm adjusting the bug metadata is this doesn't seem to be a general
problem.
 
> A bug is open upstream with some (geo)clues.
> https://github.com/jonls/redshift/issues/158

... where bigon argues that /usr/share/applications/redshift.desktop
should be enough, and this file is indeed installed by the Debian
package.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Bob Dylan: Early Roman Kings


signature.asc
Description: Digital Signature

Bug#893032: netw-ib-ox-ag: depends on deprecated Tcl/Tk 8.5

[Sergei Golovan]

Source: netw-ib-ox-ag
Version: 5.39.0-1.2
Severity: important
Tags: patch

Dear Maintainer,

Appears that the netwag binary package depends on Tcl/Tk 8.5 which is to be
removed from Debian since it's reached its end-of-life. I'd like to
propose NMU which switches to the default Tcl/Tk version (currently 8.6).
Except for the dependencies switching I had to add a small patch which
replaces #!/usr/bin/wish8.5 shebang by #!/usr/bin/wish one. I could do
the upload if appropriate.

-- System Information:
Debian Release: 9.4
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500, 
'stable'), (500, 'oldstable'), (1, 'experimental'), (1, 'unstable'), (1, 
'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru netw-ib-ox-ag-5.39.0/debian/changelog 
netw-ib-ox-ag-5.39.0/debian/changelog
--- netw-ib-ox-ag-5.39.0/debian/changelog   2015-11-18 21:52:55.0 
+0300
+++ netw-ib-ox-ag-5.39.0/debian/changelog   2018-03-15 13:05:20.0 
+0300
@@ -1,3 +1,11 @@
+netw-ib-ox-ag (5.39.0-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to the default Tcl/Tk version from 8.5 since Tcl/Tk 8.5 is to be
+removed from Debian.
+
+ -- Sergei Golovan   Thu, 15 Mar 2018 13:05:20 +0300
+
 netw-ib-ox-ag (5.39.0-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru netw-ib-ox-ag-5.39.0/debian/control 
netw-ib-ox-ag-5.39.0/debian/control
--- netw-ib-ox-ag-5.39.0/debian/control 2012-12-21 18:38:20.0 +0400
+++ netw-ib-ox-ag-5.39.0/debian/control 2018-01-19 22:52:50.0 +0300
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: Bartosz Fenski 
-Build-Depends: debhelper (>= 4.0.0), libpcap-dev, libnet1-dev, tk8.5, sed (>= 
4)
+Build-Depends: debhelper (>= 4.0.0), libpcap-dev, libnet1-dev, tk, sed (>= 4)
 Standards-Version: 3.9.4
 Homepage: http://ntwox.sourceforge.net/
 
@@ -28,7 +28,7 @@
 Package: netwag
 Section: net
 Architecture: all
-Depends: netwox (>= ${source:Version}), ${misc:Depends}, tk8.5, xterm | 
x-terminal-emulator
+Depends: netwox (>= ${source:Version}), ${misc:Depends}, tk, xterm | 
x-terminal-emulator
 Suggests: netwag-doc
 Description: graphical frontend for netwox
  Netwag is a graphical front end for netwox which contains more than 200 tools.
diff -Nru netw-ib-ox-ag-5.39.0/debian/patches/07-tcltk 
netw-ib-ox-ag-5.39.0/debian/patches/07-tcltk
--- netw-ib-ox-ag-5.39.0/debian/patches/07-tcltk1970-01-01 
03:00:00.0 +0300
+++ netw-ib-ox-ag-5.39.0/debian/patches/07-tcltk2018-01-19 
22:48:17.0 +0300
@@ -0,0 +1,11 @@
+--- a/src/netwag-src/src/config.dat
 b/src/netwag-src/src/config.dat
+@@ -30,7 +30,7 @@
+ ### When installing netwag in text mode, it might be impossible to
+ ### detect wish (Tcl/Tk interpreter) and a terminal emulator.
+ # force wish path
+-#bin_wish="/usr/bin/wish"
++bin_wish="/usr/bin/wish"
+ # force terminal emulator:
+ #   bin_term indicates terminal emulator path
+ #   bin_term_param indicates parameter needed to run a program
diff -Nru netw-ib-ox-ag-5.39.0/debian/patches/series 
netw-ib-ox-ag-5.39.0/debian/patches/series
--- netw-ib-ox-ag-5.39.0/debian/patches/series  2015-11-18 21:42:50.0 
+0300
+++ netw-ib-ox-ag-5.39.0/debian/patches/series  2018-01-19 22:45:18.0 
+0300
@@ -4,3 +4,4 @@
 04-add-s390x-support
 05-add-arm64-support
 06-add-kfreebsd-support
+07-tcltk

Bug#893031: vowpal-wabbit: Baseline violation on i386 and FTBFS on !x86

[Adrian Bunk]

Source: vowpal-wabbit
Version: 8.5.0.dfsg1-2
Severity: serious

https://buildd.debian.org/status/package.php?p=vowpal-wabbit=sid

MMX and SSE are not part of the i386 port baseline
and must not be used there.

Trying to use -msse on !x86 results in FTBFS.

Bug#893030: imagemagick: make foreign dependencies on transitional -dev packages satisfiable

[Helmut Grohne]

Source: imagemagick
Version: 8:6.9.9.34+dfsg-3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:dvdauthor src:rss-glx

Hi Bastien,

The affected packages have unsatisfiable cross Build-Depends, because
their transitive dependency on libmagickcore-dev, libmagickwand-dev or
libmagick++-dev is unsatisfiable. In general, Architecture: all packages
can never satisfy cross Build-Depends unless marked Multi-Arch: foreign.
In this case, such a marking would be fatal as we have seen in #856601.
The other major route, converting them to arch:any, is blocked by
#813455. That's bad.

So I think I came up with a workaround that works today. debian/control
says that these packages are transitional and you said on irc that they
will be provided by their dependency. So why not provide them today?
Those transitional packages are completely empty. By providing them (in
addition to producing them), upgrade continue to work, but since the
providing package is arch:any, we can satisfy cross Build-Depends. After
buster, you leave the Provides and just remove the transitional
packages.

The attached patch implements just that. What do you think?

Helmut
diff --minimal -Nru imagemagick-6.9.9.34+dfsg/debian/changelog 
imagemagick-6.9.9.34+dfsg/debian/changelog
--- imagemagick-6.9.9.34+dfsg/debian/changelog  2018-02-18 00:12:41.0 
+0100
+++ imagemagick-6.9.9.34+dfsg/debian/changelog  2018-03-15 20:15:22.0 
+0100
@@ -1,3 +1,10 @@
+imagemagick (8:6.9.9.34+dfsg-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Provide transitional packages from arch:any packages. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 15 Mar 2018 20:15:22 +0100
+
 imagemagick (8:6.9.9.34+dfsg-3) unstable; urgency=high
 
   * Upload to unstable (urgency high due to security issues).
diff --minimal -Nru imagemagick-6.9.9.34+dfsg/debian/control 
imagemagick-6.9.9.34+dfsg/debian/control
--- imagemagick-6.9.9.34+dfsg/debian/control2018-02-18 00:12:41.0 
+0100
+++ imagemagick-6.9.9.34+dfsg/debian/control2018-03-15 20:15:19.0 
+0100
@@ -285,7 +285,7 @@
 # remove breaks/replaces after jessie +2
 Replaces: libmagickcore-dev (<< 8:6.8.3.10-1~)
 Breaks: libmagickcore-dev (<< 8:6.8.3.10-1~)
-Provides: libmagickcore-6.defaultquantum-dev
+Provides: libmagickcore-6.defaultquantum-dev, libmagickcore-dev
 Description: low-level image manipulation library - development files (Q16)
  The MagickCore API is a low-level interface between the C programming language
  and the ImageMagick image processing libraries and is recommended for
@@ -329,7 +329,7 @@
  libmagickcore-6.q16-dev (= ${binary:Version}),
  pkg-config,
  ${misc:Depends}
-Provides: libmagickwand-6.defaultquantum-dev
+Provides: libmagickwand-6.defaultquantum-dev, libmagickwand-dev
 Replaces: libmagickwand-dev (<< 8:6.8.3.10-1~)
 Breaks: libmagickwand-dev (<< 8:6.8.3.10-1~)
 Description: image manipulation library - development files (Q16)
@@ -370,7 +370,7 @@
  libmagickwand-6.q16-dev (= ${binary:Version}),
  pkg-config,
  ${misc:Depends}
-Provides: libmagick++-6.defaultquantum-dev
+Provides: libmagick++-6.defaultquantum-dev, libmagick++-dev
 Replaces: libmagick++-dev (<< 8:6.8.3.10-1~)
 Breaks: libmagick++-dev (<< 8:6.8.3.10-1~)
 Description: C++ interface to ImageMagick - development files (Q16)

Bug#893022: [Piuparts-devel] Bug#893022: Bug#893022: piuparts should check whether pkgconfig dependencies are also package dependencies

[Adrian Bunk]

Control: reassign -1 adequate 0.15.1
Control: retitle -1 adequate doesn't find missing pkg-config dependencies
Control: severity -1 normal

On Thu, Mar 15, 2018 at 06:38:45PM +, Holger Levsen wrote:
> On Thu, Mar 15, 2018 at 08:29:31PM +0200, Adrian Bunk wrote:
> > lintian does not have information about other packages.
> 
> right.
> 
> > "install package and its dependencies into a minimal chroot and then
> > run a command" - piuparts was the tool that came into my mind for this
> > kind of tests.
> 
> maybe adequate would be a better package to check this? piuparts.d.o
> runs adequate on all packages anyway...

Good point.

adequate already seems to try to check this, but for some reason it 
doesn't find the libinput-dev problem.

> cheers,
>   Holger

cu
Adrian

-- 

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

Bug#893029: oce: depends on deprecated Tcl/Tk 8.5

[Sergei Golovan]

Source: oce
Version: 0.18.2-2
Severity: important
Tags: patch

Dear Maintainer,

As of now oce build-depends (and as a result oce-draw depends) on Tcl/Tk 8.5
which has reached its end of life and will be removed from Debian soon.
I'd like to suggest a patch which switches the dependencies to Tcl/Tk 8.6.
As far as I can see, the package builds fine, and the DRAWEXE binary runs
(I didn't do thorough testing).

If it's okay to you, I could do NMU if necessary.

-- System Information:
Debian Release: 9.4
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500, 
'stable'), (500, 'oldstable'), (1, 'experimental'), (1, 'unstable'), (1, 
'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru oce-0.18.2/debian/changelog oce-0.18.2/debian/changelog
--- oce-0.18.2/debian/changelog 2017-10-03 13:44:41.0 +0300
+++ oce-0.18.2/debian/changelog 2018-03-15 16:19:12.0 +0300
@@ -1,3 +1,11 @@
+oce (0.18.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to Tcl/Tk 8.6 from 8.5 since Tcl/Tk 8.5 is to be removed
+from Debian.
+
+ -- Sergei Golovan   Thu, 15 Mar 2018 16:19:12 +0300
+
 oce (0.18.2-2) unstable; urgency=medium
 
   * [3524c7e] Move all headers assigned to oce-draw into
diff -Nru oce-0.18.2/debian/control oce-0.18.2/debian/control
--- oce-0.18.2/debian/control   2017-10-03 13:44:26.0 +0300
+++ oce-0.18.2/debian/control   2018-02-01 15:54:32.0 +0300
@@ -15,8 +15,8 @@
libx11-dev,
libxext-dev,
quilt,
-   tcl8.5-dev,
-   tk8.5-dev
+   tcl8.6-dev,
+   tk8.6-dev
 Standards-Version: 4.1.1
 Vcs-Browser: https://anonscm.debian.org/cgit/debian-science/packages/oce.git
 Vcs-Git: https://anonscm.debian.org/git/debian-science/packages/oce.git
@@ -144,8 +144,8 @@
  ${misc:Depends},
  libx11-dev,
  libfreetype6-dev,
- tcl8.5-dev,
- tk8.5-dev
+ tcl8.6-dev,
+ tk8.6-dev
 Description: OpenCASCADE Community Edition CAE platform shared library
  OpenCASCADE is a suite for 3D surface and solid modeling, visualization, data
  exchange and rapid application development.  It is an excellent platform for

Bug#892965: [pkg-ntp-maintainers] Bug#892965: Bug#892966: ntpsec-ntpdate: unconditionally removes /var/lib/ntpdate on purge, even if ntpdate is installed

[Bernhard Schmidt]

On 15.03.2018 00:45, Richard Laager wrote:

Hi,

> Unless I hear otherwise from the ntpdate maintainers, I have committed
> and will upload a change to use this code in ntpsec-ntpdate:

On the one hand I'm not sure what ntpsec-ntpdate is messing with the
private runtime directory of another package. Please stop doing that and
use your own.

On the other hand, I think we're not using it anyway for ntpdate (I
could only find it referenced in the dhcp hooks prior to
f4abbe2168b452d25fb4311796c8930bcdc24bd9, pre-stretch, after that it has
been migrated to /run to be flushed on reboot).

So we will probably just drop the path from ntpdate and be done with it.

Bernhard

Bug#886328: live-boot: Please use /run/live instead of /lib/live/mount

[Benjamin Drung]

Am Freitag, den 23.02.2018, 19:24 +0100 schrieb Raphael Hertzog:
> Hello,
> 
> On Fri, 05 Jan 2018, intrigeri wrote:
> > Benjamin Drung:
> > > Therefore move /lib/live/mount to /run/live and skip the
> > > intermedia
> > > /live mount points. This reduces code and complexity.
> > 
> > As someone who had to repeatedly bang his head against exactly this
> > part of the live-boot code (last time earlier this week), I can
> > only
> > agree with the proposed simplification idea. I didn't do a full
> > code
> > review though.
> 
> I'm not familiar enough with this part either and I am unlikely to
> find
> any obvious mistake. But I committed the patch anyway
> 
> It would be nice if we could test the live-boot in git before I
> upload
> it.

I have finally tested git master and found one missing rename of
/live/overlay (probably caused by applying my patches in a different
order which causes merge conflicts). See
https://salsa.debian.org/live-team/live-boot/merge_requests/6
for a fix.

> Benjamin, did you test your changes with persistence enabled?

No, I haven't. Thanks for everyone else who does.

Am Dienstag, den 13.03.2018, 13:05 + schrieb Luca Boccassi:
> On Tue, 2018-03-13 at 10:49 +0100, Raphael Hertzog wrote:
> > On Mon, 12 Mar 2018, Luca Boccassi wrote:
> > > Or maybe have a backward-compatible symlinks?
> > 
> > This seems entirely reasonable. Can you work on this?
> 
> Yes no problem, I'll give it a shot and send a PR for review before
> the
> end of the week.

Thanks for doing it. I will be happy to review it.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg

Bug#884355: live-boot: Please support live-{top,premount,bottom} hooks

[Benjamin Drung]

Am Freitag, den 23.02.2018, 19:20 +0100 schrieb Raphael Hertzog:
> Hi,
> 
> On Thu, 14 Dec 2017, Benjamin Drung wrote:
> > initramfs-tools support hooks for top, premount, bottom when
> > booting
> > with boot=local or boot=nfs. Please add similar support to live-
> > boot
> > when booting with boot=live. A patch (for git) is attached.
> 
> I will gladly apply your patch but I think it's time to clean up the
> mess with this:
> 
> > --- a/components/9990-initramfs-tools.sh
> > +++ b/components/9990-initramfs-tools.sh
> > @@ -73,3 +73,25 @@ panic()
> > . /scripts/functions
> > panic "$@"
> >  }
> > +
> > +# Note: Other components source /scripts/functions before sourcing
> > this file.
> > +# /scripts/functions overrides the mount_* functions (to no-ops).
> > Thus fix
> > +# the mount_* options here again.
> 
> This kind of duplication is just ugly. I looked around and saw this:
> $ grep -r -E 'functions|9990-initramfs-tools.sh' components/
> components/9990-initramfs-tools.sh:# Override maybe_break from
> scripts/functions
> components/9990-initramfs-tools.sh:   .
> /scripts/functions
> components/9990-initramfs-tools.sh:# Override panic from
> scripts/functions
> components/9990-initramfs-tools.sh:   . /scripts/functions
> components/9990-fstab.sh: # FIXME: stop hardcoding overloading
> of initramfs-tools functions
> components/9990-fstab.sh: . /scripts/functions
> components/9990-fstab.sh: . /lib/live/boot/9990-initramfs-
> tools.sh
> components/9990-misc-helpers.sh:  # the output of setup_loop is
> evaluated in other functions,
> components/9990-netbase.sh:   # FIXME: stop hardcoding
> overloading of initramfs-tools functions
> components/9990-netbase.sh:   . /scripts/functions
> components/9990-netbase.sh:   . /lib/live/boot/9990-initramfs-
> tools.sh
> 
> I have the feeling that all those problematic include are no longer
> necessary
> nowadays because we first source all the files and then we execute
> functions
> in the expected order. My review has not been thorough but can you
> try to remove
> all those include and see if things still work?
> 
> /script/functions is already sourced in backend/initramfs-
> tools/live.script
> so it should not be required to have it in the components, right?

I have removed the includes (except the ones that are needed to access
the panic function) and the plugin system still works. The tested pull
request: https://salsa.debian.org/live-team/live-boot/merge_requests/6

I have just tested my use case. So I haven't verified that removing the
problematic includes doesn't break anything.

> BTW, I merged all you other patches. For the future, please send
> patches
> as merge requests on the salsa repositories.

Yes. Thanks for merging.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg

Bug#893028: aptitude: [INTL:ru] Update Russian translation of aptitude's manual

[Lev Lamberov]

Package: aptitude
Version: 0.8.10-6
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

please find attached the patch to update Russian translation of
aptitude's manual.

Regards,
Lev Lamberov


-- Package-specific info:
Terminal: rxvt-unicode
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.10
Compiler: g++ 7.2.0
Compiled against:
  apt version 5.0.2
  NCurses version 6.0
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.1.20180127
  cwidget version: 0.5.17
  Apt version: 5.0.2

aptitude linkage:
linux-vdso.so.1 (0x7ffd69d1)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f72f4e35000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7f72f4c05000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f72f49db000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f72f47d4000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f72f44dc000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f72f41d1000)
libboost_iostreams.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7f72f3fb9000)
libboost_filesystem.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7f72f3da)
libboost_system.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7f72f3b9c000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f72f3791000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f72f3573000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f72f31ee000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f72f2e5b000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f72f2c43000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f72f2889000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f72f2672000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f72f2458000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f72f2248000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f72f2022000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f72f1e1)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f72f1bf2000)
/lib64/ld-linux-x86-64.so.2 (0x7f72f5804000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f72f19ee000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f72f17e6000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f72f15df000)

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

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

Versions of packages aptitude depends on:
ii  aptitude-common0.8.10-6
ii  libapt-pkg5.0  1.6~beta1
ii  libboost-filesystem1.62.0  1.62.0+dfsg-5
ii  libboost-iostreams1.62.0   1.62.0+dfsg-5
ii  libboost-system1.62.0  1.62.0+dfsg-5
ii  libc6  2.27-2
ii  libcwidget3v5  0.5.17-7
ii  libgcc11:8-20180218-1
ii  libncursesw5   6.1-1
ii  libsigc++-2.0-0v5  2.10.0-1
ii  libsqlite3-0   3.22.0-1
ii  libstdc++6 8-20180218-1
ii  libtinfo5  6.1-1
ii  libxapian301.4.5-1

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-12
ii  sensible-utils 0.0.11

Versions of packages aptitude suggests:
pn  apt-xapian-index
ii  aptitude-doc-en [aptitude-doc]  0.8.10-6
ii  aptitude-doc-ru [aptitude-doc]  0.8.10-6
pn  debtags 
ii  tasksel 3.43

-- no debconf information


Russian_doc_update.tar.gz
Description: BZip2 compressed data

Bug#893027: aptitude: [INTL:ru] Updated Russian translation

[Lev Lamberov]

Package: aptitude
Version: 0.8.10-6
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

please find attached a patch to update Russian translation of aptitude.

Regards,
Lev Lamberov


-- Package-specific info:
Terminal: rxvt-unicode
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.10
Compiler: g++ 7.2.0
Compiled against:
  apt version 5.0.2
  NCurses version 6.0
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.1.20180127
  cwidget version: 0.5.17
  Apt version: 5.0.2

aptitude linkage:
linux-vdso.so.1 (0x7ffc1c7c4000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f2a03942000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7f2a03712000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f2a034e8000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f2a032e1000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f2a02fe9000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f2a02cde000)
libboost_iostreams.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7f2a02ac6000)
libboost_filesystem.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7f2a028ad000)
libboost_system.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7f2a026a9000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f2a0229e000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f2a0208)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f2a01cfb000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f2a01968000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f2a0175)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f2a01396000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f2a0117f000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f2a00f65000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f2a00d55000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f2a00b2f000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f2a0091d000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f2a006ff000)
/lib64/ld-linux-x86-64.so.2 (0x7f2a04311000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f2a004fb000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f2a002f3000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f2a000ec000)

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

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

Versions of packages aptitude depends on:
ii  aptitude-common0.8.10-6
ii  libapt-pkg5.0  1.6~beta1
ii  libboost-filesystem1.62.0  1.62.0+dfsg-5
ii  libboost-iostreams1.62.0   1.62.0+dfsg-5
ii  libboost-system1.62.0  1.62.0+dfsg-5
ii  libc6  2.27-2
ii  libcwidget3v5  0.5.17-7
ii  libgcc11:8-20180218-1
ii  libncursesw5   6.1-1
ii  libsigc++-2.0-0v5  2.10.0-1
ii  libsqlite3-0   3.22.0-1
ii  libstdc++6 8-20180218-1
ii  libtinfo5  6.1-1
ii  libxapian301.4.5-1

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-12
ii  sensible-utils 0.0.11

Versions of packages aptitude suggests:
pn  apt-xapian-index
ii  aptitude-doc-en [aptitude-doc]  0.8.10-6
ii  aptitude-doc-ru [aptitude-doc]  0.8.10-6
pn  debtags 
ii  tasksel 3.43

-- no debconf information
From 66d0cd4ab0d120ecc6bbfc0e73f7ffdaed00f853 Mon Sep 17 00:00:00 2001
From: Lev Lamberov 
Date: Tue, 13 Mar 2018 22:04:20 +0500
Subject: [PATCH 1/2] Update Russian translation

---
 po/ru.po | 20 
 1 file changed, 12 insertions(+), 8 deletions(-)

diff --git a/po/ru.po b/po/ru.po
index ac83909a..a86ea781 100644
--- a/po/ru.po
+++ b/po/ru.po
@@ -13,7 +13,7 @@ msgstr ""
 "Project-Id-Version: \n"
 "Report-Msgid-Bugs-To: aptit...@packages.debian.org\n"
 "POT-Creation-Date: 2017-11-15 01:20+0100\n"
-"PO-Revision-Date: 2017-02-17 01:32+0500\n"
+"PO-Revision-Date: 2018-03-13 22:03+0500\n"
 "Last-Translator: Lev Lamberov 

Bug#880594: virtualbox-guest-x11: 98vboxadd-xclient calls notify-send before Plasma is started, causing SDDM to hang

[Leszek Lesner]

Hi, 

> what is the approach you are suggesting?
> this?
> git diff
> diff --git a/src/VBox/Additions/x11/Installer/98vboxadd-xclient
> b/src/VBox/Additions/x11/Installer/98vboxadd-xclient index
> 985e9e7ab..8187a3fe4 100755
> --- a/src/VBox/Additions/x11/Installer/98vboxadd-xclient
> +++ b/src/VBox/Additions/x11/Installer/98vboxadd-xclient
> @@ -23,7 +23,7 @@ done
> 
>  if ! test -c /dev/vboxguest 2>/dev/null; then
>  
> # Do not start if the kernel module is not present.
> 
> -   notify-send "VBoxClient: the VirtualBox kernel service is not running. 
> Exiting." +   notify-send "VBoxClient: the VirtualBox kernel service is not
> running.  Exiting." &> 
>  elif test -z "${SSH_CONNECTION}"; then
>  
> # This script can also be triggered by a connection over SSH, which is
> not
> # what we had in mind, so we do not start VBoxClient in that case.  We
> do

This diff looks reasonable. It is used on Netrunner and Neptune Distros 
successfully.

> I fail to see notify-send calls in the code that might give such troubles,
> specically because they are ran in error conditions that will unlikely be
> part of Debian use-cases (e.g. /dev/vboxguest exists always in Debian
> context

The /dev/vboxguest device only exists if you boot on virtualbox. 
So for example having a live system with KDE Plasma and virtualbox-guest-{x11, 
utils,dkms} so that it boots on virtualbox and real machines will work pretty 
fine on virtualbox but causes the delay on "real" hardware as it will trigger 
the notify-send code. 


Greetings
Leszek
-- 
ZevenOS / Neptune Team
https://neptuneos.com
Leszek Lesner 

Bug#876152: Acknowledgement (RFS: luakit/2017.08.10-1)

[Grégory DAVID]

owner 876152 !

-- 
DAVID Grégory
Libre Software Developer
d...@groolot.net

https://framagit.org/groolot
https://github.com/groolot


signature.asc
Description: PGP signature

Bug#891188: blends-dev: created d/control recommends packages not in main

[Andreas Tille]

Hi Ole,

On Thu, Mar 15, 2018 at 05:14:36PM +0100, Andreas Tille wrote:
> > Feel free to lower the severity.
> 
> I think there is no need to since I found the part of the code where the
> issue occures.  If I would only understand Perl a bit better I would be
> ready with a fix. :-(

I've commited a fix to Git which for me creates now sensible Debian
Astro metapackages.  I'd love some review / enhancement of my beginners
Perl code before uploading.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#892943: yash: FTBFS: test prompt-y.tst fails

[Sven Joachim]

On 2018-03-15 14:04 +0900, TANIGUCHI Takaki wrote:

> I can not reproduce that error on my environment(locally and pbuilder).
>
> Could you please send more information?

There must be some race condition in the test, for I can reproducibly
trigger the error with DEB_BUILD_OPTIONS=parallel=2 (the default for my
dual core system), but not with any other "parallel" value.  With
DEB_BUILD_OPTIONS=parallel=1 it succeeds, likewise with parallel=3 or 4.

HTH,
Sven

>> On Wed, 14 Mar 2018 19:24:39 +0100
>> svenj...@gmx.de(Sven Joachim)  said:
>>
>> [1  ]
>> Source: yash
>> Version: 2.46-1
>>
>> On my system, the test prompt-y.tst fails reproducibly on both i386 and
>> amd64, although it apparently succeeds (or is skipped) on the buildds.
>> Attached is the summary.log file describing the problem.
>>
>>
>> -- System Information:
>> Debian Release: buster/sid
>>   APT prefers unstable
>>   APT policy: (500, 'unstable'), (101, 'experimental')
>> Architecture: i386 (x86_64)
>> Foreign Architectures: amd64
>>
>> Kernel: Linux 4.15.9-nouveau (SMP w/2 CPU cores)
>> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
>> LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> [2 summary.log ]
>> Linux turtle 4.15.9-nouveau #1 SMP Sun Mar 11 17:49:12 CET 2018 x86_64 
>> GNU/Linux
>> Wed Mar 14 19:21:58 CET 2018
>> =
>>
>> %%% START: prompt-y.tst:157: \j in PS1 and -b option
>> % standard error diff:
>> --- -2018-03-14 19:21:53.995351857 +0100
>> +++ 157.err  2018-03-14 19:21:53.988131643 +0100
>> @@ -1,6 +1,5 @@
>>  $
>>  0$[1] + Running  exec 1>fifo
>>
>> -1$[1] + Done exec 1>fifo
>> -0$
>> +1$1$
>>  0$
>>
>> %%% FAILED: prompt-y.tst:157: \j in PS1 and -b option
>>
>> %%% SKIPPED: prompt-y.tst:179: \$ in PS1 and PS2 (root)
>>
>> %%% SKIPPED: prompt-y.tst:231: default prompt strings (POSIX, root)
>>
>> =
>> TOTAL:   3915
>> PASSED:  3912
>> FAILED: 1
>> SKIPPED:2
>> =

Bug#891188: blends-dev: created d/control recommends packages not in main

[Andreas Tille]

Hi Ole,

On Thu, Mar 15, 2018 at 04:55:24PM +0100, Ole Streicher wrote:
> > 
> >GENCONTROL_DEPENDS = true
> > 
> 
> Feel free to lower the severity.

I think there is no need to since I found the part of the code where the
issue occures.  If I would only understand Perl a bit better I would be
ready with a fix. :-(

> However, that was a change of the
> default behaviour that we discussed a year ago: we wanted to remove the
> translation
> 
> "Depends:" (tasks) -> "Recommends:" (d/control)
> "Recommends:" (tasks) -> "Suggests:" (d/control)
> 
> in favour of a direct copy.

Its true that we agreed upon this and the code **seemed** to do this.
However, if there is no Depends -> Recommends the check whether the
missings need to be removed is simply not done.

> I am wondering why debian-astro is the only
> blend which finally used this, and I think we wanted to convert all.

I have not seen any reason to switch any behaviour since there are no
strict Depends in Debian Med.  Thus I just substituted
s/Depends/Recommends/ inside the watch file "to be prepared" and be more
expclicit what we mean.  But I had no reason to force any switch.  Most
probably all other Blends did the same as I in Debian Med and thus you
were simply the only one who was stumbling upon this issue.
 
> > But I do not want to play severity ping-pong and will have a look
> > why GENCONTROL_DEPENDS is obviously breaking this.
> 
> That is probably the code that was introduced for this purpose (August
> 2017).

It is

a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 267) my $pkglist;
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 268) my $missinglist;
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 269) if (defined $taskinfo{$task}{Depends})
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 270) {
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 271) ($pkglist, $missinglist) = 
process_pkglist(join(",",@{$taskinfo{$task}{Depends}}));
36791f91 cdd/devtools/cdd-gen-control  (Andreas Tille   2007-08-27 
17:48:49 + 272) }
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 273) 
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 274) my (@depends, @recommends, @suggests);
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 275) 
0fc23d84 devtools/blend-gen-control(Mike Gabriel2017-08-21 
13:51:30 -0400 276) push @depends, $tasksname.' (= 
${source:Version})';
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 277) push @depends, '${misc:Depends}';
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 278) push @depends, @{$pkglist}
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 279) if defined $pkglist;
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 280) 
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 281) push @recommends, 
@{$taskinfo{$task}{Recommends}}
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 282) if defined $taskinfo{$task}{Recommends};
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 283) 
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 284) push @suggests, @{$missinglist}
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 285) if defined $missinglist;
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 286) push @suggests, 
@{$taskinfo{$task}{Suggests}}
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 287) if defined $taskinfo{$task}{Suggests};
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 288) 
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 289) my @depends_sorted = sort_uniq(\%seenlist, 
@depends);
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 290) my @recommends_sorted = 
sort_uniq(\%seenlist, @recommends);
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 291) my @suggests_sorted = sort_uniq(\%seenlist, 
@suggests);

Bug#893022: [Piuparts-devel] Bug#893022: Bug#893022: piuparts should check whether pkgconfig dependencies are also package dependencies

[Holger Levsen]

On Thu, Mar 15, 2018 at 08:29:31PM +0200, Adrian Bunk wrote:
> lintian does not have information about other packages.

right.

> "install package and its dependencies into a minimal chroot and then
> run a command" - piuparts was the tool that came into my mind for this
> kind of tests.

maybe adequate would be a better package to check this? piuparts.d.o
runs adequate on all packages anyway...


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#893026: Preview pane does not update

[martin f krafft]

Package: gscan2pdf
Version: 2.0.1-1
Severity: normal

With the latest UI updates, gscan2pdf has become quite unsuable,
mainly in that it's very quick now to scroll and flip through pages
in the list of pages on the right. However, the preview pane no
longer seems to get updated when I select another page in the left
pane.

One workaround is to right-click on a new page (and again to get rid
of the menu), which will then cause the preview pane to update. This
isn't very convenient when trying to flip through a number of pages
e.g. in search of a specific scan.

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

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

Versions of packages gscan2pdf depends on:
ii  imagemagick8:6.9.9.34+dfsg-3
ii  imagemagick-6.q16 [imagemagick]8:6.9.9.34+dfsg-3
ii  libconfig-general-perl 2.63-1
ii  libdate-calc-perl  6.4-1
ii  libfilesys-df-perl 0.92-6+b3
ii  libgoocanvas2-perl 0.06-1
ii  libgtk3-simplelist-perl0.17-1
ii  libhtml-parser-perl3.72-3+b2
ii  libimage-magick-perl   8:6.9.9.34+dfsg-3
ii  libimage-sane-perl 0.14-1+b1
ii  liblist-moreutils-perl 0.416-1+b3
ii  liblocale-gettext-perl 1.07-3+b3
ii  liblog-log4perl-perl   1.49-1
ii  libossp-uuid-perl [libdata-uuid-perl]  1.6.2-1.5+b6
ii  libpdf-api2-perl   2.033-1
ii  libproc-processtable-perl  0.55-1
ii  libreadonly-perl   2.050-1
ii  librsvg2-common2.40.20-2
ii  libset-intspan-perl1.19-1
ii  libtiff-tools  4.0.9-4
ii  libtry-tiny-perl   0.30-1
ii  sane-utils 1.0.26~git20151121-1

Versions of packages gscan2pdf recommends:
ii  djvulibre-bin  3.5.27.1-8
ii  gocr   0.49-2+b1
ii  sane   1.0.14-12
ii  tesseract-ocr  4.00~git2219-40f43111-1.2
ii  unpaper6.1-2+b1
ii  xdg-utils  1.1.2-2

gscan2pdf suggests no packages.

-- no debconf information

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#893025: White UI background makes page borders disappear

[martin f krafft]

Package: gscan2pdf
Version: 2.0.1-1
Severity: minor

As of late, the background of the viewing pane seems to be white,
such that when I view a scan of text on white paper, there are no
longer any visible page borders. Please change the UI pane
background back to gray, or make it configurable.

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

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

Versions of packages gscan2pdf depends on:
ii  imagemagick8:6.9.9.34+dfsg-3
ii  imagemagick-6.q16 [imagemagick]8:6.9.9.34+dfsg-3
ii  libconfig-general-perl 2.63-1
ii  libdate-calc-perl  6.4-1
ii  libfilesys-df-perl 0.92-6+b3
ii  libgoocanvas2-perl 0.06-1
ii  libgtk3-simplelist-perl0.17-1
ii  libhtml-parser-perl3.72-3+b2
ii  libimage-magick-perl   8:6.9.9.34+dfsg-3
ii  libimage-sane-perl 0.14-1+b1
ii  liblist-moreutils-perl 0.416-1+b3
ii  liblocale-gettext-perl 1.07-3+b3
ii  liblog-log4perl-perl   1.49-1
ii  libossp-uuid-perl [libdata-uuid-perl]  1.6.2-1.5+b6
ii  libpdf-api2-perl   2.033-1
ii  libproc-processtable-perl  0.55-1
ii  libreadonly-perl   2.050-1
ii  librsvg2-common2.40.20-2
ii  libset-intspan-perl1.19-1
ii  libtiff-tools  4.0.9-4
ii  libtry-tiny-perl   0.30-1
ii  sane-utils 1.0.26~git20151121-1

Versions of packages gscan2pdf recommends:
ii  djvulibre-bin  3.5.27.1-8
ii  gocr   0.49-2+b1
ii  sane   1.0.14-12
ii  tesseract-ocr  4.00~git2219-40f43111-1.2
ii  unpaper6.1-2+b1
ii  xdg-utils  1.1.2-2

gscan2pdf suggests no packages.

-- no debconf information

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)