Bug#942544: shc: diff for NMU version 4.0.3-0.1

[Eriberto]

Hi again,

I did some improvements in packaging and, now, I reuploaded the
package to 12-day/delay queue.

I attached a diff to show my last changes. To see the full packaging,
please go to Salsa[1].

[1] https://salsa.debian.org/debian/shc

The current changelog is:

 shc (4.0.3-0.1) unstable; urgency=medium

   * Non-maintainer upload. (Closes: #942544)
   * New upstream version 4.0.3
   * Using new DH level format. Consequently:
   - debian/compat: removed.
   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
 Build-Depends field and bumped level to 12.
   * debian/control:
   - Added ash, ksh, rc, tcsh, zsh to Build-Depends field to allow 'make
 test' command work fine.
   - Added 'Rules-Requires-Root: no' to debian/control source stanza.
   - Bumped Standards-Version to 4.4.1.
   - Updated upstream address in Homepage field.
   - Updated VCS fields to use Salsa.
   * debian/copyright:
   - Added a comment in header to quote the original upstream homepage.
   - Added rights for all upstreams.
   - Added Upstream-Contact field.
   - Fixed rights for packagers.
   * debian/rules:
   - Enabled DEB_BUILD_MAINT_OPTIONS variable to provide a full hardening to
 final binary.
   - Removed all trash.
   * debian/patches/010_fix-rc-path.patch: created to fix 'rc' path to allow the
 build system run tests.
   * debian/salsa-ci.yml: created to provide CI tests via Salsa.
   * debian/tests/*: created to provide some trivial CI tests.
   * debian/upstream/signing-key.asc: removed because the upstream didn't sign
 the tarballs since 3.9.6 version. Currently, it can result in a rejection
 when uploading the package.
   * debian/watch: remade to look at releases instead of tags.

Regards,

Eriberto
diff -Naur old/shc-4.0.3/debian/changelog shc/debian/changelog
--- old/shc-4.0.3/debian/changelog	2019-10-17 13:47:33.0 -0300
+++ shc/debian/changelog	2019-10-20 01:12:14.873168202 -0300
@@ -7,6 +7,8 @@
   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
 Build-Depends field and bumped level to 12.
   * debian/control:
+  - Added ash, ksh, rc, tcsh, zsh to Build-Depends field to allow 'make
+test' command work fine.
   - Added 'Rules-Requires-Root: no' to debian/control source stanza.
   - Bumped Standards-Version to 4.4.1.
   - Updated upstream address in Homepage field.
@@ -17,11 +19,12 @@
   - Added Upstream-Contact field.
   - Fixed rights for packagers.
   * debian/rules:
-  - Created override_dh_auto_test target to avoid a FTBFS because the
-upstream test procedure fail.
   - Enabled DEB_BUILD_MAINT_OPTIONS variable to provide a full hardening to
 final binary.
   - Removed all trash.
+  * debian/patches/010_fix-rc-path.patch: created to fix 'rc' path to allow the
+build system run tests.
+  * debian/salsa-ci.yml: created to provide CI tests via Salsa.
   * debian/tests/*: created to provide some trivial CI tests.
   * debian/upstream/signing-key.asc: removed because the upstream didn't sign
 the tarballs since 3.9.6 version. Currently, it can result in a rejection
diff -Naur old/shc-4.0.3/debian/control shc/debian/control
--- old/shc-4.0.3/debian/control	2019-10-17 13:47:33.0 -0300
+++ shc/debian/control	2019-10-20 00:59:27.797168013 -0300
@@ -2,7 +2,7 @@
 Section: devel
 Priority: optional
 Maintainer: Tong Sun 
-Build-Depends: debhelper-compat (= 12)
+Build-Depends: debhelper-compat (= 12), ash, ksh, rc, tcsh, zsh
 Standards-Version: 4.4.1
 Rules-Requires-Root: no
 Homepage: https://neurobin.org/projects/softwares/unix/shc/
diff -Naur old/shc-4.0.3/debian/patches/010_fix-rc-path.patch shc/debian/patches/010_fix-rc-path.patch
--- old/shc-4.0.3/debian/patches/010_fix-rc-path.patch	1969-12-31 21:00:00.0 -0300
+++ shc/debian/patches/010_fix-rc-path.patch	2019-10-20 01:02:25.917168057 -0300
@@ -0,0 +1,13 @@
+Description: fix rc path to allow build system run tests
+Author: Joao Eriberto Mota Filho 
+Last-Update: 2019-10-20
+--- shc-4.0.3.orig/test/ttest.sh
 shc-4.0.3/test/ttest.sh
+@@ -1,6 +1,6 @@
+ #!/bin/bash
+ 
+-shells=('/bin/sh' '/bin/dash' '/bin/bash' '/bin/ash' '/bin/ksh' '/bin/zsh' '/usr/bin/tcsh' '/bin/csh' '/usr/bin/rc')
++shells=('/bin/sh' '/bin/dash' '/bin/bash' '/bin/ash' '/bin/ksh' '/bin/zsh' '/usr/bin/tcsh' '/bin/csh' '/bin/rc')
+ ## Install: sudo apt install dash bash ash ksh zsh tcsh csh rc
+ 
+ check_opts=('' '-r' '-v' '-D' '-S')
diff -Naur old/shc-4.0.3/debian/patches/series shc/debian/patches/series
--- old/shc-4.0.3/debian/patches/series	1969-12-31 21:00:00.0 -0300
+++ shc/debian/patches/series	2019-10-20 01:01:41.125168046 -0300
@@ -0,0 +1 @@
+010_fix-rc-path.patch
diff -Naur old/shc-4.0.3/debian/rules shc/debian/rules
--- old/shc-4.0.3/debian/rules	2019-10-17 13:47:33.0 -0300
+++ shc/debian/rules	2019-10-20 00:06:26.029167228 -0300
@@ -5,5 +5,3 @@
 
 %:

Bug#942692: vmtoolsd segfault when fsName contains no slash

[Mo Zhou]

Package: open-vm-tools
Version: 2:11.0.0-2
Severity: important
Tags: patch
Forwarded: https://github.com/vmware/open-vm-tools/issues/378

Detailed description can be found here:

https://github.com/vmware/open-vm-tools/issues/378

I've also provided a hack for fixing this problem.

Bug#942691: ITP: python-telegram-bot -- python module for Telegram Bot API

[Ying-Chun Liu (PaulLiu)]

Package: wnpp
Owner: Ying-Chun Liu (PaulLiu) 
Severity: wishlist

* Package name    : python-telegram-bot
  Version : 12.2.0
  Upstream Author : Leandro Toledo 
* URL : https://python-telegram-bot.org/
* License : GPL-3.0+ or LGPL-3
  Programming Lang: python
  Description : python module for Telegram Bot API
 This package contains the python module for Telegram Bot API. You can
use it
 simply as an API if you want to implement logic by yourself, or you can
enable
 retrieving of updates and get messages sent to your bot in a callback.



signature.asc
Description: OpenPGP digital signature

Bug#942237: fiat: autopkgtest needs update for new version of pytest

[Drew Parsons]

Package: python3-fiat
Version: 2019.1.0-2
Followup-For: Bug #942237

Upstream does have a patch, but it requires a new package pytest_cases.

There was some debate upstream about whether it would be better to
prepare the tests without needing to depend on the new package. I'm
waiting for that debate to resolve.

Drew

Bug#936732: indexed-gzip: diff for NMU version 0.8.6-1.1

[Sandro Tosi]

> > I've prepared an NMU for indexed-gzip (versioned as 0.8.6-1.1) and
>
> Thanks!

no problem :)

> > uploaded it to DELAYED/7. Please feel free to tell me if I
> > should delay it longer.
>
> if desired, you are welcome to upload without a DELAY

I've just rescheduled for 0-day -- thanks!

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#942690: debhelper: dh_auto_test fails in compat 13 for a meson package

[Jeremy Bicha]

Oops, I wasn't using compat 13 any more when I tested my last change,
so ignore my last comment.

Jeremy

Bug#942690: debhelper: dh_auto_test fails in compat 13 for a meson package

[Jeremy Bicha]

Overriding dh_auto_test like this makes the build succeed:

dh_auto_test -- -C $(CURDIR)/obj-$(DEB_HOST_GNU_TYPE)

Thanks,
Jeremy Bicha

Bug#657712: FW: black watch digital crypto custodial insured solution for miners

[Crediblock]

We spent 2 long years researching and building Crypto products, which 
culminated in Splitting Bits (The Book). 

  This experience taught us many things and perhaps the most important one is 
that with Crypto Currency security is the highest priority.  You are always one 
hack away from disaster.  We believe that in order for Crypto to grow into the 
new paradigm of finance as Bitcoin promised us, we need Enterprise grade 
solutions.  Finally, we've found one.  Black Watch 
Digital.

This solution is great for Bitcoin miners, who may have large quantities of 
assets after a mine.

See Blackwatch Digital on Zero Hedge 
https://www.zerohedge.com/news/2019-08-16/bitcoin-security-risks-solved

Best Regards,

Joseph Gelet,
PreIPOSwap.com Crediblock.com Office: +1 646 781 8009 Address: 8 The Green 
Suite #8364 Dover DE 19901 USA
Email: i...@preiposwap.com

Reply with 'remove' to be removed but you aren't on any list.

Pre IPO Investing is for accredited investors only.  INVESTING IS RISKY YOU CAN 
LOSE ALL YOUR MONEY and all of your mind.  CAVEAT EMPTOR.

Bug#942690: debhelper: dh_auto_test fails in compat 13 for a meson package

[Jeremy Bicha]

Source: debhelper
Version: 12.6.1

I tried building gnome-photos with debhelper compat 13 since I
eventually wanted to tweak the test timeout. The build fails:

   dh_auto_test -O--buildsystem=meson
Can't locate object method "name" via package
"Debian::Debhelper::Buildsystem::ninja" at
/usr/share/perl5/Debian/Debhelper/Buildsystem/meson.pm line 112.
make: *** [debian/rules:7: build] Error 2


To switch to compat 13, I changed the Build-Depends in debian/control
and debian/control.in from debhelper-compat 12 to debhelper and added
debian/compat that says 13. I made no other changes. As far as I can
tell, nothing in Debian is using compat 13 yet.


See https://bugs.debian.org/912560 where the meson test change was requested.

Thanks,
Jeremy Bicha

Bug#942689: ITP: nncp -- Node to Node Copy for secure store-and-forward online and offline file and mail exchange

[John Goerzen]

Package: wnpp
Severity: wishlist
Owner: John Goerzen 

* Package name: nncp
  Version : 4.1
  Upstream Author : Sergey Matveev 
* URL : http://www.nncpgo.org/
* License : GPL
  Programming Lang: Go
  Description : Node to Node Copy for secure store-and-forward online and 
offline file and mail exchange

NNCP is a package facilitating secure store-and-forward file and mail
exchange.  It can be thought of as a modern UUCP with Internet smarts.

NNCP supports direct online communication over a LAN or Internet,
scheduled communication, offline copies, streaming communication
(pipes), and more.  It can therefore be used for air-gapped computers
that might be communicated with by CD-ROM, tape, or USB stick.  It can
also be used for intermittent or on-demand links, very slow or high
latency links, etc.

Like UUCP, NNCP supports routing messages via intermediate systems.
With NNCP, however, all packets are end-to-end encrypted and
authenticated, making this more proper onion routing -- the
intermediate systems have no visibility to the content of the data
being passed.  NNCP also has robust tools for interrupted transfer
resumption, handling of very large files, and verifying integrity of
data copied off.

Bug#942674: Acknowledgement (git: FTBFS on big-endian targets - testsuite failure)

[John Paul Adrian Glaubitz]

Control: tags -1 +patch

The attached patch fixes the problem for me. It comes from [1].

Thanks,
Adrian

> [1] https://www.spinics.net/lists/git/msg368292.html

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
From: SZEDER =?utf-8?B?R8OhYm9y?= 
To: John Paul Adrian Glaubitz ,
	Junio C Hamano 
Cc: Todd Zullinger , g...@vger.kernel.org
Subject: [PATCH] test-progress: fix test failures on big-endian systems

On Sat, Oct 19, 2019 at 11:38:40PM +0200, John Paul Adrian Glaubitz wrote:
> The testsuite is failing again on s390x and all other big-endian targets in
> Debian. For a full build log on s390x see [1].

Gah, my progress display fixes strike again...

I think the patch below should fix it, but I could only test it on
little-endian systems.  Could you please confirm that it indeed works
on big-endian as well?


  --- >8 ---

Subject: [PATCH] test-progress: fix test failures on big-endian systems

In 't0500-progress-display.sh' all tests running 'test-tool progress
--total=' fail on big-endian systems, e.g. like this:

  + test-tool progress --total=3 Working hard
  [...]
  + test_i18ncmp expect out
  --- expect	2019-10-18 23:07:54.765523916 +
  +++ out	2019-10-18 23:07:54.773523916 +
  @@ -1,4 +1,2 @@
  -Working hard:  33% (1/3)
  -Working hard:  66% (2/3)
  -Working hard: 100% (3/3)
  -Working hard: 100% (3/3), done.
  +Working hard:   0% (1/12884901888)
  +Working hard:   0% (3/12884901888), done.

The reason for that bogus value is that '--total's parameter is parsed
via parse-options's OPT_INTEGER into a uint64_t variable [1], so the
two bits of 3 end up in the "wrong" bytes on big-endian systems
(12884901888 = 0x3).

Change the type of that variable from uint64_t to int, to match what
parse-options expects; in the tests of the progress output we won't
use values that don't fit into an int anyway.

[1] start_progress() expects the total number as an uint64_t, that's
why I chose the same type when declaring the variable holding the
value given on the command line.

Signed-off-by: SZEDER Gábor 
---
 t/helper/test-progress.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/t/helper/test-progress.c b/t/helper/test-progress.c
index 4e9f7fafdf..42b96cb103 100644
--- a/t/helper/test-progress.c
+++ b/t/helper/test-progress.c
@@ -29,7 +29,7 @@ void progress_test_force_update(void);
 
 int cmd__progress(int argc, const char **argv)
 {
-	uint64_t total = 0;
+	int total = 0;
 	const char *title;
 	struct strbuf line = STRBUF_INIT;
 	struct progress *progress;
-- 
2.24.0.rc0.472.ga6f06c86b4

Bug#942688: elixir-lang: tests fail randomly during build

[Antonio Terceiro]

Source: elixir-lang
Version: 1.9.1.dfsg-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

The latest upload failed to build on a few architectures:

https://buildd.debian.org/status/package.php?p=elixir-lang=sid

I tried building it locally and it worked. I then tried 10 builds in a
row, and 1 of them failed. So I suspect that builds will fail ~ 10% of
the time. Maybe if I tried more times I could have a better estimate, but
this seems relevant enough since it already failed on the buildd.

I have failures like this in past be caused by:

- implicit dependency on the order in which tests are run (does the
  elixir test suite randomizes the execution order?)
- timing issues and race conditions

The full build log for the failed build is attached. Note that the
failure I found does not match the ones that happened on the amd64 and
arm64 buildds. So not only the tests fail randomly, but the failure is
on different tests each time.

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


elixir-lang_amd64-2019-10-19T23:09:13Z.build.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#942687: odb-api ftbfs with python3-defaults from experimental

[Matthias Klose]

Package: src:odb-api
Version: 0.18.1-7
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

see
https://launchpadlibrarian.net/447604304/buildlog_ubuntu-focal-amd64.odb-api_0.18.1-7build1_BUILDING.txt.gz

apparently it's not building the extensions for 3.8.

Bug#941414: certificates about to expire

[Florian Zumbiehl]

Hi,

> In fact, the proposed "fix" I'm working on is to actually get the
> version that is currently in backports directly in the oldstable
> distribution, but I need to tweak it a bit as to do that I need to
> reintroduce the 'letsencrypt.sh' compatibility packages/scripts.

unfortunately, that version (0.6.2-2+deb10u1~bpo9+1) is not backwards
compatible with the current stretch version (0.3.1-3+deb9u2), in that it
deploys all challenges for a certificate at once, and only then submits the
verification requests for the individual host names. If you happen to
deploy challenges for multiple host names to the same location, that fails
because the last deployed challenge overwrites all other challenges in that
location, and the verification request for the first host name then causes
dehydrated to abort (also, without any useful error message).

For anyone facing the same problem: A (temporary) workaround I found was to
set HOOK_CHAIN=yes, which causes all challenges for a given domain to be
deployed in a single call to the hook script. If your hook script simply
ignores the additional parameters, that then causes only the first
challenge to actually be deployed, and thus the verification for the first
host name to succeed. Then you just have to re-run dehydrated until all the
host names have been verified.

Regards, Florian

Bug#936732: indexed-gzip: diff for NMU version 0.8.6-1.1

[Yaroslav Halchenko]

On Sat, 19 Oct 2019, Sandro Tosi wrote:

> Control: tags 936732 + patch
> Control: tags 936732 + pending


> Dear maintainer,

> I've prepared an NMU for indexed-gzip (versioned as 0.8.6-1.1) and

Thanks!

> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.

if desired, you are welcome to upload without a DELAY

Cheers,

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#942686: fix the installation of 3.8 extensions

[Matthias Klose]

Package: src:python-apsw
Version: 3.28.0-r1-1
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

fix the installation of 3.8 extensions, patch at
http://launchpadlibrarian.net/447598995/python-apsw_3.28.0-r1-1build1_3.28.0-r1-1ubuntu1.diff.gz

Bug#942685: fix installation of 3.8 extensions

[Matthias Klose]

Package: src:netifaces
Version: 0.10.4-1
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

fix the installation of 3.8 extensions, patch at
http://launchpadlibrarian.net/447591503/netifaces_0.10.4-1build4_0.10.4-1ubuntu1.diff.gz

Bug#942684: mod-wsgi needs a new upstream version to support python3.8

[Matthias Klose]

Package: src:mod-wsgi
Version: 4.6.5-1
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

mod-wsgi needs a new upstream version to support python3.8. 4.6.8 builds fine 
with 3.8.


example packaging (no changes) at:
https://launchpad.net/ubuntu/+source/mod-wsgi/4.6.8-0ubuntu1

Bug#942567: Info received (Bug#942567: fwupd: fails to update metadata)

[Mario.Limonciello]

I had a newer systemd on my system when I tested. It is specifically a bug in 
systemd leading to this behavior.

1.3.2-3 will work around it until newer systemd lands.

On Oct 19, 2019 09:15, Debian Bug Tracking System  wrote:

[EXTERNAL EMAIL]

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Debian EFI 

If you wish to submit further information on this problem, please
send it to 942...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

--
942567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#942683: fix installation of python 3.8 extensions

[Matthias Klose]

Package: src:python-greenlet
Version: 0.4.15-2
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

fix installation of python 3.8 extensions

patch at
http://launchpadlibrarian.net/447593167/python-greenlet_0.4.15-2build1_0.4.15-2ubuntu1.diff.gz

Bug#942682: ITP: r-cran-sitmo -- Parallel Pseudo Random Number Generator (PPRNG) 'sitmo' Header

[Steffen Moeller]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-sitmo -- Parallel Pseudo Random Number Generator (PPRNG) 
'sitmo' Header
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: r-cran-sitmo
  Version : 2.0.1
  Upstream Author : Copyright: (FIXME: year)-2019 James Balamuta
* URL : https://cran.r-project.org/package=sitmo
* License : MIT
  Programming Lang: GNU R
  Description : Parallel Pseudo Random Number Generator (PPRNG) 'sitmo' 
Header
   Files
 Provided within are two high quality and fast PPRNGs that may be
 used in an 'OpenMP' parallel environment. In addition, there is a generator
 for one dimensional low-discrepancy sequence. The objective of this library
 to consolidate the distribution of the 'sitmo' (C++98 & C++11), 'threefry' and
 'vandercorput' (C++11-only) engines on CRAN by enabling others to link to the
 header files inside of 'sitmo' instead of including a copy of each engine
 within their individual package. Lastly, the package contains example
 implementations using the 'sitmo' package and three accompanying vignette that
 provide additional information.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-sitmo

Bug#942681: ITP: sahara-plugin-vanilla -- OpenStack data processing cluster as a service - Vanilla plugin

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: sahara-plugin-vanilla
  Version : 2.0.0
  Upstream Author : OpenStack Foundatino 
* URL : https://github.com/openstack/sahara-plugin-vanilla
* License : Apache-2.0
  Programming Lang: Python
  Description : OpenStack data processing cluster as a service - Vanilla 
plugin

 The Sahara project provides a simple means to provision a data-intensive
 application cluster (Hadoop or Spark) on top of OpenStack. It's the ex
 Savanna project, renamed due to potential trademark issues.
 .
 This package provides the Vanilla plugin which provides the users the
 option to start Vanilla clusters on OpenStack Sahara.

Note: This is needed since Sahara split his repos.

Bug#937402: pycares: diff for NMU version 2.1.1-2.1

[Sandro Tosi]

Control: tags 937402 + patch
Control: tags 937402 + pending


Dear maintainer,

I've prepared an NMU for pycares (versioned as 2.1.1-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru pycares-2.1.1/debian/changelog pycares-2.1.1/debian/changelog
--- pycares-2.1.1/debian/changelog	2016-11-15 17:23:37.0 -0500
+++ pycares-2.1.1/debian/changelog	2019-10-19 18:23:40.0 -0400
@@ -1,3 +1,10 @@
+pycares (2.1.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937402
+
+ -- Sandro Tosi   Sat, 19 Oct 2019 18:23:40 -0400
+
 pycares (2.1.1-2) unstable; urgency=medium
 
   * debian/rules, debian/add-ons/configure: use configure script from c-ares
diff -Nru pycares-2.1.1/debian/control pycares-2.1.1/debian/control
--- pycares-2.1.1/debian/control	2016-11-15 17:19:13.0 -0500
+++ pycares-2.1.1/debian/control	2019-10-19 18:23:06.0 -0400
@@ -8,28 +8,12 @@
 python3-all,
 python3-all-dev,
 python3-setuptools,
-python-all,
-python-all-dev,
-python-docutils,
-python-setuptools,
-python-sphinx,
-python-sphinx-rtd-theme,
+python3-sphinx,
+python3-sphinx-rtd-theme,
 Standards-Version: 3.9.8
 Homepage: https://github.com/saghul/pycares
 Vcs-Git: https://git.ortolo.eu/git/pkg-pycares.git
 Vcs-Browser: https://git.ortolo.eu/pkg-pycares.git
-X-Python-Version: >= 2.7
-X-Python3-Version: >= 3.3
-
-Package: python-pycares
-Architecture: any
-Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
-Suggests: python-pycares-doc
-Description: Python interface for c-ares (Python 2)
- pycares is a Python module which provides an interface to c-ares. c-ares is a
- C library that performs DNS requests and name resolutions asynchronously.
- .
- This package installs the library for Python 2.
 
 Package: python3-pycares
 Architecture: any
diff -Nru pycares-2.1.1/debian/rules pycares-2.1.1/debian/rules
--- pycares-2.1.1/debian/rules	2016-11-15 17:19:43.0 -0500
+++ pycares-2.1.1/debian/rules	2019-10-19 18:23:29.0 -0400
@@ -9,7 +9,7 @@
 export PYBUILD_NAME = pycares
 
 %:
-	dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild
+	dh $@ --with python3,sphinxdoc --buildsystem=pybuild
 
 override_dh_auto_configure:
 	dh_auto_configure

Bug#942680: passwd: vipw does not resume properly when suspended

[Todd C. Miller]

Package: passwd
Version: 1:4.5-1.1
Severity: normal
Tags: patch

Dear Maintainer,

   * What led up to the situation?

If vipw is suspended (e.g. via control-Z) and then resumed, it
often gets immediately suspended.  This is easier to reproduce
on a multi-core system.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 
root@buster:~# /usr/sbin/vipw

[1]+  Stopped /usr/sbin/vipw
root@buster:~# fg
/usr/sbin/vipw

[1]+  Stopped /usr/sbin/vipw

root@buster:~# fg
[vipw resumes on the second fg]

The problem is that vipw forks a child process and calls waitpid()
with the WUNTRACED flag.  When the child process (running the editor)
is suspended, the parent sends itself SIGSTOP to suspend the main vipw
process.  However, because the main vipw is in the same process group
as the editor which received the ^Z, the kernel already sent the
main vipw SIGTSTP.

If the main vipw receives SIGTSTP before the child, it will be
suspended and then, once resumed, will proceed to suspend itself
again.

There are two main ways to fix this.  I've included patches for
each approach.

1) Don't pass the WUNTRACED flag to waitpid() in vipw.c and
   just assume the main vipw will receive a stop signal from
   the kernel.  This is the simplest fix and works fine for
   stop signals generated due to ^Z.  However, if someone sends
   SIGSTOP to the vipw child process via the kill command, the
   parent vipw will not notice.

--- vipw.c.orig 2019-10-18 16:19:15.673956247 -0600
+++ vipw.c.simple_fix   2019-10-18 16:43:04.265583507 -0600
@@ -325,16 +325,9 @@
}
 
for (;;) {
-   pid = waitpid (pid, , WUNTRACED);
-   if ((pid != -1) && (WIFSTOPPED (status) != 0)) {
-   /* The child (editor) was suspended.
-* Suspend vipw. */
-   kill (getpid (), SIGSTOP);
-   /* wake child when resumed */
-   kill (pid, SIGCONT);
-   } else {
+   pid = waitpid (pid, , 0);
+   if (pid != -1 || errno != EINTR)
break;
-   }
}
 
if (-1 == pid) {

2) The other option is to run the child process in its own process
   group as the foregroup process group.  That way, control-Z will
   only affect the child process and the parent can use the existing
   logic to suspend the parent.


--- vipw.c.orig 2019-10-18 16:19:15.673956247 -0600
+++ vipw.c.pgrp_fix 2019-10-19 12:55:50.526591299 -0600
@@ -206,6 +206,8 @@
struct stat st1, st2;
int status;
FILE *f;
+   pid_t orig_pgrp, editor_pgrp = -1;
+   sigset_t mask, omask;
/* FIXME: the following should have variable sizes */
char filebackup[1024], fileedit[1024];
char *to_rename;
@@ -293,6 +295,8 @@
editor = DEFAULT_EDITOR;
}
 
+   orig_pgrp = tcgetpgrp(STDIN_FILENO);
+
pid = fork ();
if (-1 == pid) {
vipwexit ("fork", 1, 1);
@@ -302,6 +306,14 @@
char *buf;
int status;
 
+   /* Wait for parent to make us the foreground pgrp. */
+   if (orig_pgrp != -1) {
+   pid = getpid();
+   setpgid(0, 0);
+   while (tcgetpgrp(STDIN_FILENO) != pid)
+   continue;
+   }
+
buf = (char *) malloc (strlen (editor) + strlen (fileedit) + 2);
snprintf (buf, strlen (editor) + strlen (fileedit) + 2,
  "%s %s", editor, fileedit);
@@ -324,19 +336,50 @@
}
}
 
+   /* Run child in a new pgrp and make it the foreground pgrp. */
+   if (orig_pgrp != -1) {
+   setpgid(pid, pid);
+   tcsetpgrp(STDIN_FILENO, pid);
+
+   /* Avoid SIGTTOU when changing foreground pgrp below. */
+   sigemptyset();
+   sigaddset(, SIGTTOU);
+   sigprocmask(SIG_BLOCK, , );
+   }
+
for (;;) {
pid = waitpid (pid, , WUNTRACED);
if ((pid != -1) && (WIFSTOPPED (status) != 0)) {
/* The child (editor) was suspended.
-* Suspend vipw. */
+* Restore terminal pgrp and suspend vipw. */
+   if (orig_pgrp != -1) {
+   editor_pgrp = tcgetpgrp(STDIN_FILENO);
+   if (editor_pgrp == -1) {
+   fprintf (stderr, "%s: %s: %s", Prog,
+"tcgetpgrp", strerror (errno));
+   }
+   if (tcsetpgrp(STDIN_FILENO, orig_pgrp) == -1) {
+  

Bug#938083: python-pypcap: diff for NMU version 1.2.2-1.1

[Sandro Tosi]

Control: tags 938083 + patch
Control: tags 938083 + pending


Dear maintainer,

I've prepared an NMU for python-pypcap (versioned as 1.2.2-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru python-pypcap-1.2.2/debian/changelog python-pypcap-1.2.2/debian/changelog
--- python-pypcap-1.2.2/debian/changelog	2018-07-16 07:54:37.0 -0400
+++ python-pypcap-1.2.2/debian/changelog	2019-10-19 18:11:46.0 -0400
@@ -1,3 +1,10 @@
+python-pypcap (1.2.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #938083
+
+ -- Sandro Tosi   Sat, 19 Oct 2019 18:11:46 -0400
+
 python-pypcap (1.2.2-1) unstable; urgency=medium
 
   * Team upload
diff -Nru python-pypcap-1.2.2/debian/control python-pypcap-1.2.2/debian/control
--- python-pypcap-1.2.2/debian/control	2018-07-16 07:41:53.0 -0400
+++ python-pypcap-1.2.2/debian/control	2019-10-19 18:11:19.0 -0400
@@ -4,13 +4,10 @@
 Section: python
 Priority: optional
 Build-Depends: debhelper (>= 11),
-   python-all-dev,
-   cython,
 	   cython3,
 	   python3-all-dev,
libpcap0.8-dev,
quilt,
-   python-setuptools,
 	   python3-setuptools,
dh-python
 Standards-Version: 4.1.5
@@ -18,19 +15,6 @@
 Vcs-Git: https://salsa.debian.org/ineteng-team/python-pypcap.git
 Homepage: https://github.com/pynetwork/pypcap
 
-Package: python-pypcap
-Architecture: any
-Depends: ${python:Depends},
- ${shlibs:Depends},
- ${misc:Depends}
-Conflicts: python-libpcap
-Provides: ${python:Provides}
-Description: object-oriented Python interface for libpcap (Python 2)
- pypcap is an objected-oriented Python interface for libpcap which
- supports packet injection and user callback functions.
- .
- This package works with Python versions 2.x.
-
 Package: python3-pypcap
 Architecture: any
 Depends: ${python3:Depends},
diff -Nru python-pypcap-1.2.2/debian/rules python-pypcap-1.2.2/debian/rules
--- python-pypcap-1.2.2/debian/rules	2018-07-16 07:41:53.0 -0400
+++ python-pypcap-1.2.2/debian/rules	2019-10-19 18:11:40.0 -0400
@@ -3,7 +3,7 @@
 export PYBUILD_NAME=pypcap
 
 %:
-	dh $@ --with=python2,python3 --buildsystem=pybuild
+	dh $@ --with=python3 --buildsystem=pybuild
 
 override_dh_auto_configure:
 	cython3 pcap.pyx

Bug#942679: silo-llnl ftbfs with python3.8

[Matthias Klose]

Package: src:silo-llnl
Version: 4.10.2.real-6
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

Build python interface for python3.8
make[2]: Entering directory '/<>/tools/python'
test -z "Silo.la" || rm -f Silo.la
rm -f ./so_locations
rm -rf .libs _libs
rm -f *.o
rm -f *.lo
/bin/sh ../../libtool  --tag=CXX   --mode=compile mpic++ -DHAVE_CONFIG_H -I. 
-I../..  -I/usr/include/python3.8 -I../../src/silo -I../../src/silo 
-I/usr/include -I/usr/include/hdf5/openmpi  -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/lib/openmpi/include 
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC  -c -o 
pydbfile.lo pydbfile.cpp
libtool: compile:  mpic++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/python3.8 
-I../../src/silo -I../../src/silo -I/usr/include -I/usr/include/hdf5/openmpi 
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/lib/openmpi/include 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -c pydbfile.cpp 
-fPIC -DPIC -o .libs/pydbfile.o
pydbfile.cpp:903:20: error: invalid conversion from ‘printfunc’ {aka ‘long int’} 
to ‘int (*)(PyObject*, FILE*, int)’ {aka ‘int (*)(_object*, _IO_FILE*, int)’} 
[-fpermissive]

  903 |   tp_print   : (printfunc)DBfile_print,
  |^~~
  ||
  |printfunc {aka long int}
pydbfile.cpp:941:1: error: designator order for field ‘_typeobject::tp_getattr’ 
does not match declaration order in ‘PyTypeObject’ {aka ‘_typeobject’}

  941 | };
  | ^
make[2]: *** [Makefile:598: pydbfile.lo] Error 1
make[2]: Leaving directory '/<>/tools/python'
make[1]: *** [debian/rules:74: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build] Error 2

Bug#942678: subvertpy ftbfs with python 3.8 (tests)

[Matthias Klose]

Package: src:subvertpy
Version: 0.10.1-3
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

I: pybuild base:217: python3.8 setup.py test
running test
running build
running build_py
running build_ext
running build_scripts
Running unittest without install.
E
==
ERROR: subvertpy (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: subvertpy
Traceback (most recent call last):
  File "/usr/lib/python3.8/unittest/loader.py", line 470, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.8/unittest/loader.py", line 377, in 
_get_module_from_name
__import__(name)
  File 
"/<>/.pybuild/cpython3_3.8_subvertpy/build/subvertpy/__init__.py", 
line 126, in 

from subvertpy import client, _ra, repos, wc
SystemError: bad call flags


--
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: 
python3.8 setup.py test

Bug#938530: sphinxcontrib-actdiag: diff for NMU version 0.8.5-1.1

[Sandro Tosi]

Control: tags 938530 + patch


Dear maintainer,

I've prepared an NMU for sphinxcontrib-actdiag (versioned as 0.8.5-1.1). The 
diff
is attached to this message.

i've uploaded directly to unstable becaues it fixes a RC bug

Regards.

diff -Nru sphinxcontrib-actdiag-0.8.5/debian/changelog sphinxcontrib-actdiag-0.8.5/debian/changelog
--- sphinxcontrib-actdiag-0.8.5/debian/changelog	2016-10-31 19:58:04.0 -0400
+++ sphinxcontrib-actdiag-0.8.5/debian/changelog	2019-10-19 18:07:40.0 -0400
@@ -1,3 +1,10 @@
+sphinxcontrib-actdiag (0.8.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #938530
+
+ -- Sandro Tosi   Sat, 19 Oct 2019 18:07:40 -0400
+
 sphinxcontrib-actdiag (0.8.5-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru sphinxcontrib-actdiag-0.8.5/debian/control sphinxcontrib-actdiag-0.8.5/debian/control
--- sphinxcontrib-actdiag-0.8.5/debian/control	2016-10-31 19:58:02.0 -0400
+++ sphinxcontrib-actdiag-0.8.5/debian/control	2019-10-19 18:07:22.0 -0400
@@ -4,12 +4,6 @@
 Maintainer: Kouhei Maeda 
 Build-Depends: debhelper (>= 9.0.0),
dh-python,
-   python-all,
-   python-setuptools,
-   python-sphinx (>= 0.6),
-   python-blockdiag (>= 1.5.0),
-   python-actdiag (>= 0.5.3),
-   python-mock,
python3-all,
python3-setuptools,
python3-sphinx (>= 0.6),
@@ -17,21 +11,8 @@
python3-actdiag (>= 0.5.3),
python3-mock
 Standards-Version: 3.9.8
-X-Python-Version: 2.7
 Homepage: http://github.com/blockdiag/sphinxcontrib-actdiag
 
-Package: python-sphinxcontrib.actdiag
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${misc:Depends}, ${python:Depends},
- python-blockdiag (>= 1.5.0),
- python-actdiag (>= 0.5.3),
- python-sphinx (>= 0.6)
-Description: Sphinx "actdiag" extension
- This package contains the actdiag Sphinx extension. This extension enable you
- to insert activity diagrams in your Sphinx document. This is a sphinx
- extension which render block diagrams by using python-actdiag.
-
 Package: python3-sphinxcontrib.actdiag
 Architecture: all
 Depends: ${misc:Depends}, ${python3:Depends},
diff -Nru sphinxcontrib-actdiag-0.8.5/debian/rules sphinxcontrib-actdiag-0.8.5/debian/rules
--- sphinxcontrib-actdiag-0.8.5/debian/rules	2014-11-22 12:00:08.0 -0500
+++ sphinxcontrib-actdiag-0.8.5/debian/rules	2019-10-19 18:07:36.0 -0400
@@ -8,12 +8,8 @@
 export PYBUILD_DISABLE=test
 
 %:
-	dh $@ --with python2,python3 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_python3:
 	dh_python3
 	find $(CURDIR)/debian/python3-sphinxcontrib.actdiag -name tests -a -type d | xargs rm -rf
-
-override_dh_python2:
-	dh_python2
-	find $(CURDIR)/debian/python-sphinxcontrib.actdiag -name tests -a -type d | xargs rm -rf

Bug#942677: zbar doesn't build for all supported python3 versions

[Matthias Klose]

Package: src:zbar
Version: 0.23-1.1
Severity: important
Tags: sid bullseye

zbar doesn't build for all supported python versions, while b-d on 
python3-all-dev.  Either drop that b-d, or build the extension for all supported 
python versions.

Bug#937714: python-docker: diff for NMU version 3.4.1-4.1

[Sandro Tosi]

Control: tags 937714 + patch
Control: tags 937714 + pending


Dear maintainer,

I've prepared an NMU for python-docker (versioned as 3.4.1-4.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru python-docker-3.4.1/debian/changelog python-docker-3.4.1/debian/changelog
--- python-docker-3.4.1/debian/changelog	2019-01-10 17:35:42.0 -0500
+++ python-docker-3.4.1/debian/changelog	2019-10-19 17:48:18.0 -0400
@@ -1,3 +1,10 @@
+python-docker (3.4.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937714
+
+ -- Sandro Tosi   Sat, 19 Oct 2019 17:48:18 -0400
+
 python-docker (3.4.1-4) unstable; urgency=medium
 
   * Revert "Drop dependency on ssl-match-hostname backport"
diff -Nru python-docker-3.4.1/debian/control python-docker-3.4.1/debian/control
--- python-docker-3.4.1/debian/control	2019-01-10 17:35:42.0 -0500
+++ python-docker-3.4.1/debian/control	2019-10-19 17:47:40.0 -0400
@@ -6,17 +6,8 @@
  Felipe Sateler 
 Build-Depends: debhelper (>= 10),
  dh-python,
- python-all (>= 2.7),
  python3-all,
- python-setuptools,
  python3-setuptools,
-# setup.py
- python-requests (>= 2.11.1~),
- python-six (>= 1.4.0~),
- python-websocket (>= 0.32.0~),
- python-dockerpycreds (>= 0.2.2),
- python-backports.ssl-match-hostname (>= 3.5),
- python-ipaddress (>=1.0.16),
 # setup.py - python3
  python3-requests (>= 2.11.1~),
  python3-six (>= 1.4.0~),
@@ -32,21 +23,6 @@
 Vcs-Browser: https://salsa.debian.org/docker-compose-team/python-docker
 X-Python3-Version: >= 3.5
 
-Package: python-docker
-Architecture: all
-Depends: ${misc:Depends}, ${python:Depends},
- python-backports.ssl-match-hostname (>= 3.5),
- python-ipaddress (>=1.0.16)
-Breaks: python-magnum (<< 5.0.0),
- python-senlin (<< 2.0.0),
- docker-compose (<< 1.21)
-Description: Python wrapper to access docker.io's control socket
- This package contains oodles of routines that aid in controlling
- docker.io over it's socket control, the same way the docker.io
- client controls the daemon.
- .
- This package provides Python 2 module bindings only.
-
 Package: python3-docker
 Architecture: all
 Depends: ${misc:Depends}, ${python3:Depends}
diff -Nru python-docker-3.4.1/debian/rules python-docker-3.4.1/debian/rules
--- python-docker-3.4.1/debian/rules	2019-01-10 17:35:42.0 -0500
+++ python-docker-3.4.1/debian/rules	2019-10-19 17:47:50.0 -0400
@@ -10,4 +10,4 @@
 	rm -f docker_py.egg-info/SOURCES.txt
 
 %:
-	dh $@ --with python2,python3 --buildsystem pybuild
+	dh $@ --with python3 --buildsystem pybuild
diff -Nru python-docker-3.4.1/debian/tests/control python-docker-3.4.1/debian/tests/control
--- python-docker-3.4.1/debian/tests/control	2019-01-10 17:35:42.0 -0500
+++ python-docker-3.4.1/debian/tests/control	2019-10-19 17:48:09.0 -0400
@@ -1,3 +1,3 @@
 Tests: integration
-Depends: docker.io, python-mock, python-pytest, python3-mock, python3-pytest, python-backports.ssl-match-hostname, @
+Depends: docker.io, python3-mock, python3-pytest, @
 Restrictions: isolation-machine needs-root
diff -Nru python-docker-3.4.1/debian/tests/integration python-docker-3.4.1/debian/tests/integration
--- python-docker-3.4.1/debian/tests/integration	2019-01-10 17:35:42.0 -0500
+++ python-docker-3.4.1/debian/tests/integration	2019-10-19 17:48:16.0 -0400
@@ -2,4 +2,3 @@
 set -e
 
 py.test-3 tests/integration/
-py.test tests/integration/

Bug#942676: mate-menu: Can't add MATE Advanced Menu to panel

[Mike Kupfer]

Package: mate-menu
Version: 19.10.2-1
Severity: important

Dear Maintainer,

I had an instance of the MATE Advanced menu in my panel.  After an
upgrade a couple weeks back (sorry, I don't remember exactly when),
that spot in the panel was blank, and clicking in that area had no
effect.

Since then I have reset my panels (right-click on a panel, select
Reset Panel) and tried to re-add the advanced menu.  I select the
advanced menu and click on "Add", but I don't see anything happen.  No
lines are added to .xsession-errors.

I have tried hiding $HOME/.config and logging out/in; that doesn't
help.

Turning compositing on/off doesn't help.

The system is a VirtualBox VM.  I've seen the problem with VirtualBox
6.0.12 and 6.0.14 on the host.  I tried changing the video adapter
from VBoxVGA (no-3D acceleration) to VMSVGA (with 3D acceleration);
didn't help.  VBoxSVGA (with 3D acceleration) doesn't work, either.
Updating to the 6.0.14 VirtualBox Guest Additions did not help.

I'm able to add other applets to the panel (e.g., System Monitor,
Window Selector).

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mate-menu depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  gir1.2-gtk-3.0   3.24.12-1
ii  gir1.2-matedesktop-2.0   1.22.2-1
ii  gir1.2-matemenu-2.0  1.22.1-1
ii  gir1.2-matepanelapplet-4.0   1.22.2-1
ii  libglib2.0-bin   2.62.1-1
ii  mozo 1.22.2-1
ii  python3  3.7.5-1
ii  python3-configobj5.0.6-3
ii  python3-pkg-resources41.2.0-1
ii  python3-setproctitle 1.1.10-1+b2
ii  python3-unidecode1.1.1-2
ii  python3-xdg  0.25-5
ii  python3-xlib 0.23-2
ii  xdg-utils1.1.3-1

mate-menu recommends no packages.

Versions of packages mate-menu suggests:
pn  software-center  
ii  synaptic 0.84.6+b1

-- no debconf information

Bug#942675: meshio not compatible with python 3.8, installation fails

[Matthias Klose]

Package: src:python-meshio
Version: 3.1.6-1
Severity; serious
Tags: sid bullseye

Trying to setup the package with pytho3-defaults installed from experimental, 
the installation fails when trying to compile with Python 3.8:


Setting up python3-meshio (3.1.6-1) ...
Traceback (most recent call last):
  File "/usr/lib/python3.8/py_compile.py", line 144, in compile
code = loader.source_to_code(source_bytes, dfile or file,
  File "", line 846, in source_to_code
  File "", line 219, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/meshio/_mdpa.py", line 338
break
^
SyntaxError: 'break' outside loop

Bug#937618: python-boto3: diff for NMU version 1.9.86-1.1

[Sandro Tosi]

Control: tags 937618 + patch
Control: tags 937618 + pending


Dear maintainer,

I've prepared an NMU for python-boto3 (versioned as 1.9.86-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru python-boto3-1.9.86/debian/changelog python-boto3-1.9.86/debian/changelog
--- python-boto3-1.9.86/debian/changelog	2019-01-28 18:07:32.0 -0500
+++ python-boto3-1.9.86/debian/changelog	2019-10-19 17:41:36.0 -0400
@@ -1,3 +1,10 @@
+python-boto3 (1.9.86-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937618
+
+ -- Sandro Tosi   Sat, 19 Oct 2019 17:41:36 -0400
+
 python-boto3 (1.9.86-1) unstable; urgency=medium
 
   * d/control: Update VCS fields.
diff -Nru python-boto3-1.9.86/debian/control python-boto3-1.9.86/debian/control
--- python-boto3-1.9.86/debian/control	2019-01-28 18:07:32.0 -0500
+++ python-boto3-1.9.86/debian/control	2019-10-19 17:41:21.0 -0400
@@ -5,9 +5,6 @@
 Uploaders: Alexander GQ Gerasiov 
 Build-Depends: debhelper (>= 9),
dh-python,
-   python-all,
-   python-s3transfer (>= 0.1.10),
-   python-setuptools,
python3-all,
python3-s3transfer (>= 0.1.10),
python3-setuptools
@@ -16,20 +13,6 @@
 Vcs-Git:https://salsa.debian.org/eevans/python-boto3.git
 Vcs-Browser: https://salsa.debian.org/eevans/python-boto3
 
-Package: python-boto3
-Architecture: all
-Depends: python-botocore (>= 1.6.6),
- python-requests,
- python-s3transfer (>= 0.1.10),
- python-six,
- ${misc:Depends},
- ${python:Depends}
-Description: Python interface to Amazon's Web Services - Python 2.x
- Boto is the Amazon Web Services interface for Python.  It allows developers
- to write software that makes use of Amazon services like S3 and EC2. Boto
- provides an easy to use, object-oriented API as well as low-level direct
- service access.
-
 Package: python3-boto3
 Architecture: all
 Depends: python3-botocore (>= 1.6.6),
diff -Nru python-boto3-1.9.86/debian/rules python-boto3-1.9.86/debian/rules
--- python-boto3-1.9.86/debian/rules	2019-01-28 18:01:51.0 -0500
+++ python-boto3-1.9.86/debian/rules	2019-10-19 17:41:32.0 -0400
@@ -7,7 +7,7 @@
 
 # main packaging script based on dh7 syntax
 %:
-	dh $@ --with python2,python3 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_auto_test:
 	#autotests are disabled, run them manually with

Bug#937480: pymia: diff for NMU version 0.1.9-2.1

[Sandro Tosi]

Control: tags 937480 + patch
Control: tags 937480 + pending


Dear maintainer,

I've prepared an NMU for pymia (versioned as 0.1.9-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru pymia-0.1.9/debian/changelog pymia-0.1.9/debian/changelog
--- pymia-0.1.9/debian/changelog	2018-06-30 15:23:54.0 -0400
+++ pymia-0.1.9/debian/changelog	2019-10-19 17:35:22.0 -0400
@@ -1,3 +1,10 @@
+pymia (0.1.9-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937480
+
+ -- Sandro Tosi   Sat, 19 Oct 2019 17:35:22 -0400
+
 pymia (0.1.9-2) unstable; urgency=medium
 
   [ Andreas Tille ]
diff -Nru pymia-0.1.9/debian/control pymia-0.1.9/debian/control
--- pymia-0.1.9/debian/control	2018-06-30 15:23:54.0 -0400
+++ pymia-0.1.9/debian/control	2019-10-19 17:34:50.0 -0400
@@ -6,11 +6,8 @@
 Build-Depends: debhelper (>= 9),
pkg-config,
dh-python,
-   python-all-dev,
python3-dev:any,
-   python-numpy,
python3-numpy,
-   python-setuptools,
python3-setuptools,
libmia-2.4-dev
 Standards-Version: 4.1.4
@@ -18,20 +15,6 @@
 Vcs-Git: https://salsa.debian.org/med-team/pymia.git
 Homepage: http://mia.sourceforge.net
 
-Package: python-mia
-Architecture: any
-Section: python
-Depends: ${shlibs:Depends},
- ${misc:Depends},
- ${python:Depends},
- python-numpy
-Description: Python-2 bindings for the MIA image processing library
- MIA comprises a set of tools, libraries, and plug-ins for general purpose 
- 2D and 3D gray scale image processing and basic handling of triangular 
- meshes. The libraries provide a basic infrastructure and  generic 
- algorithms, that can be specialized by specifying the appropriate plug-ins.
- This package provides the Python-2 bindings. 
-
 Package: python3-mia
 Architecture: any
 Section: python
diff -Nru pymia-0.1.9/debian/rules pymia-0.1.9/debian/rules
--- pymia-0.1.9/debian/rules	2018-06-30 15:23:54.0 -0400
+++ pymia-0.1.9/debian/rules	2019-10-19 17:35:19.0 -0400
@@ -6,17 +6,16 @@
 export PYBUILD_NAME=mia
 
 %:
-	dh $@ --with python2,python3 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 
 override_dh_auto_install:
 	dh_auto_install 
-	dh_numpy
 	dh_numpy3
 
 override_dh_strip:
 ifeq (,$(filter nostrip,$(DEB_BUILD_OPTIONS)))
-	dh_strip --dbgsym-migration='python-mia-dbg (<< 0.1.7-3),  python3-mia-dbg (<< 0.1.7-3)' 
+	dh_strip --dbgsym-migration='python3-mia-dbg (<< 0.1.7-3)' 
 endif
 
 override_dh_auto_clean:

Bug#942674: git: FTBFS on big-endian targets - testsuite failure

[John Paul Adrian Glaubitz]

Source: git
Version: 1:2.24.0~rc0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
User: debian-s...@lists.debian.org
Usertags: s390x

Hi!

git currently fails to build from source on all big-endian targets due
to test suite failures. This includes powerpc, ppc64, sparc64 and s390x
which is why this bug has severity serious [1].

There have been testsuite failures on big-endian in the past before,
see [2]. I will also notify upstream.

Thanks,
Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=git=s390x=1%3A2.24.0%7Erc0-1=1571440098=0
> [2] https://www.spinics.net/lists/git/msg363527.html

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#942673: warn about b-d on python3-all-dev and package not building for all supported python versions

[Matthias Klose]

Package: lintian

please warn about b-d on python3-all-dev and package not  building for all 
supported python versions.  Not sure if that's implementable, because you can 
only warn about that when there are currently multiple supported python3 
versions (like in python3-defaults in experimental). Or can you reference the 
buildinfo file for that?


Examples which I found so far:

jsonnet
ldb
apparmor
libkdtree++

Bug#936732: indexed-gzip: diff for NMU version 0.8.6-1.1

[Sandro Tosi]

Control: tags 936732 + patch
Control: tags 936732 + pending


Dear maintainer,

I've prepared an NMU for indexed-gzip (versioned as 0.8.6-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru indexed-gzip-0.8.6/debian/changelog indexed-gzip-0.8.6/debian/changelog
--- indexed-gzip-0.8.6/debian/changelog	2018-06-27 10:07:10.0 -0400
+++ indexed-gzip-0.8.6/debian/changelog	2019-10-19 17:02:11.0 -0400
@@ -1,3 +1,12 @@
+indexed-gzip (0.8.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #936732
+  * debian/patches/fix-fixtures.patch
+- fix how fixtures are used, needed by pytest >= 4
+
+ -- Sandro Tosi   Sat, 19 Oct 2019 17:02:11 -0400
+
 indexed-gzip (0.8.6-1) unstable; urgency=medium
 
   * Fresh upstream version, dropping CPed patches
diff -Nru indexed-gzip-0.8.6/debian/control indexed-gzip-0.8.6/debian/control
--- indexed-gzip-0.8.6/debian/control	2018-06-27 10:07:10.0 -0400
+++ indexed-gzip-0.8.6/debian/control	2019-10-19 16:24:37.0 -0400
@@ -8,47 +8,17 @@
 Priority: optional
 Build-Depends: debhelper (>= 9),
zlib1g-dev,
-   cython,
cython3,
dh-python,
-   python-all-dev,
python3-all-dev,
-   python-pytest,
python3-pytest,
-   python-pytest-runner,
python3-pytest-runner,
-   python-setuptools,
python3-setuptools,
-   python-numpy,
python3-numpy,
 Standards-Version: 3.9.8
 Homepage: https://github.com/pauldmccarthy/indexed_gzip
 Vcs-Browser: https://github.com/neurodebian/indexed_gzip
 Vcs-Git: git://github.com/neurodebian/indexed_gzip -b debian
-X-Python-Version: >= 2.7
-
-Package: python-indexed-gzip
-Architecture: any
-Section: python
-Depends: cython,
- python-numpy,
- ${misc:Depends},
- ${shlibs:Depends},
- ${python:Depends},
-Provides: ${python:Provides}
-Description: fast random access of gzip files in Python
- Drop-in replacement `IndexedGzipFile` for the built-in Python `gzip.GzipFile`
- class that does not need to start decompressing from the beginning of the
- file when for every `seek()`. It gets around this performance limitation by
- building an index, which contains *seek points*, mappings between
- corresponding locations in the compressed and uncompressed data streams. Each
- seek point is accompanied by a chunk (32KB) of uncompressed data which is
- used to initialise the decompression algorithm, allowing to start reading
- from any seek point. If the index is built with a seek point spacing of 1MB,
- only 512KB (on average) of data have to be decompressed to read from any
- location in the file.
- .
- This package provides the Python 2 module.
 
 Package: python3-indexed-gzip
 Architecture: any
diff -Nru indexed-gzip-0.8.6/debian/patches/fix-fixtures.patch indexed-gzip-0.8.6/debian/patches/fix-fixtures.patch
--- indexed-gzip-0.8.6/debian/patches/fix-fixtures.patch	1969-12-31 19:00:00.0 -0500
+++ indexed-gzip-0.8.6/debian/patches/fix-fixtures.patch	2019-10-19 17:01:50.0 -0400
@@ -0,0 +1,24 @@
+--- a/conftest.py
 b/conftest.py
+@@ -80,17 +80,16 @@ def seed(request):
+ 
+ 
+ @pytest.fixture
+-def testfile(request):
++def testfile(request, nelems, concat):
+ 
+ filename = request.config.getoption('--testfile')
+-_nelems  = nelems(request)
+-_concat  = concat(request)
+ 
+ if filename is None:
+ filename = op.join(os.getcwd(),
+-   'ctest_zran_{}_{}.gz'.format(_nelems, _concat))
++   'ctest_zran_{}_{}.gz'.format(nelems, concat))
+ 
+ if not op.exists(filename):
+-gen_test_data(filename, _nelems, _concat)
++gen_test_data(filename, nelems, concat)
+ 
+ return filename
++
diff -Nru indexed-gzip-0.8.6/debian/patches/series indexed-gzip-0.8.6/debian/patches/series
--- indexed-gzip-0.8.6/debian/patches/series	2018-06-27 10:07:10.0 -0400
+++ indexed-gzip-0.8.6/debian/patches/series	2019-10-19 17:01:30.0 -0400
@@ -1 +1,2 @@
 deb_nocov_tests
+fix-fixtures.patch
diff -Nru indexed-gzip-0.8.6/debian/rules indexed-gzip-0.8.6/debian/rules
--- indexed-gzip-0.8.6/debian/rules	2018-06-27 10:07:10.0 -0400
+++ indexed-gzip-0.8.6/debian/rules	2019-10-19 16:27:50.0 -0400
@@ -15,11 +15,11 @@
 
 # one ring to rule them all ...
 %:
-	dh $@ --with python2,python3 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 
 clean::
-	python setup.py clean
+	python3 setup.py clean
 	dh_clean
 	# Ahhh!
 	rm -rf .pybuild build
@@ -30,13 +30,12 @@
 # explicitely run the tests via distutils,as the maintainer appears to be
 # too stupid to understand how to get pybuild to not fail on test invocation
 override_dh_auto_test:
-	python2 setup.py test --addopts '--niter 1'
 	python3 setup.py test 

Bug#938220: [Python-modules-team] Bug#938220: marked as done (python-tornado: Python2 removal in sid/bullseye)

[Sandro Tosi]

python-tornado has 19 (!) reverse dependencies:
http://sandrotosi.me/debian/py2removal/python-tornado_1.svg

please restore that package until there are no more rdeps.

On Sat, Oct 19, 2019 at 5:09 PM Debian Bug Tracking System
 wrote:
>
> Your message dated Sat, 19 Oct 2019 21:04:01 +
> with message-id 
> and subject line Bug#938220: fixed in python-tornado 6.0.3-1
> has caused the Debian Bug report #938220,
> regarding python-tornado: Python2 removal in sid/bullseye
> to be marked as done.
>
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
>
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
>
>
> --
> 938220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938220
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Matthias Klose 
> To: mainto...@bugs.debian.org
> Cc:
> Bcc:
> Date: Fri, 30 Aug 2019 07:47:45 +
> Subject: python-tornado: Python2 removal in sid/bullseye
> Package: src:python-tornado
> Version: 5.1.1-4
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html
>
> Your package either build-depends, depends on Python2, or uses Python2
> in the autopkg tests.  Please stop using Python2, and fix this issue
> by one of the following actions.
>
> - Convert your Package to Python3. This is the preferred option.  In
>   case you are providing a Python module foo, please consider dropping
>   the python-foo package, and only build a python3-foo package.  Please
>   don't drop Python2 modules, which still have reverse dependencies,
>   just document them.
>
>   This is the preferred option.
>
> - If the package is dead upstream, cannot be converted or maintained
>   in Debian, it should be removed from the distribution.  If the
>   package still has reverse dependencies, raise the severity to
>   "serious" and document the reverse dependencies with the BTS affects
>   command.  If the package has no reverse dependencies, confirm that
>   the package can be removed, reassign this issue to ftp.debian.org,
>   make sure that the bug priority is set to normal and retitle the
>   issue to "RM: PKG -- removal triggered by the Python2 removal".
>
> - If the package has still many users (popcon >= 300), or is needed to
>   build another package which cannot be removed, document that by
>   adding the "py2keep" user tag (not replacing the py2remove tag),
>   using the debian-pyt...@lists.debian.org user.  Also any
>   dependencies on an unversioned python package (python, python-dev)
>   must not be used, same with the python shebang.  These have to be
>   replaced by python2/python2.7 dependencies and shebang.
>
>   This is the least preferred option.
>
> If the conversion or removal needs action on another package first,
> please document the blocking by using the BTS affects command, like
>
>   affects  + src:python-tornado
>
> If there is no py2removal bug for that reverse-dependency, please file
> a bug on this package (similar to this bug report).
>
> If there are questions, please refer to the wiki page for the removal:
> https://wiki.debian.org/Python/2Removal, or ask for help on IRC
> #debian-python, or the debian-pyt...@lists.debian.org mailing list.
>
>
>
> -- Forwarded message --
> From: Julien Puydt 
> To: 938220-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 19 Oct 2019 21:04:01 +
> Subject: Bug#938220: fixed in python-tornado 6.0.3-1
> Source: python-tornado
> Source-Version: 6.0.3-1
>
> We believe that the bug you reported is fixed in the latest version of
> python-tornado, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 938...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Julien Puydt  (supplier of updated python-tornado package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Sat, 19 Oct 2019 22:48:34 +0200
> Source: python-tornado
> Architecture: source
> Version: 6.0.3-1
> Distribution: unstable
> Urgency: medium
> Maintainer: 

Bug#936006: Debian 10

[Łukasz Stelmach]

The reported problem is not visible (at least not much) on Debian 10.
A short investigation suggests it may be a matter of TTF bytecode
interpreter version in the freetype library.

Apparently in Debian 9, the default version was v35, which when selected
in Debian 10 by setting envitonment variable

FREETYPE_PROPERTIES="truetype:interpreter-version=35"

makes the problem visible again.

I will try to choose higher version on a Stretch machine.

-- 
Było mi bardzo miło.  --- Rurku. --- ...
>Łukasz<--- To dobrze, że mnie słuchasz.


signature.asc
Description: PGP signature

Bug#942672: libkdtree++ doesn't build for all supported python versions

[Matthias Klose]

Package: src:libkdtree++
Version: 0.7.1+git20101123-4
Severity: important
Tags: sid bullseye

libkdtree++ doesn't build for all supported python versions, while b-d on 
python3-all-dev.  Either drop that b-d, or build the extension for all supported 
python versions.

Bug#942664: debootstrap: please include mdadm and lvm2

[Geert Stappers]

On Sat, Oct 19, 2019 at 12:55:34PM -0700, Felix Lechner wrote:
> The point is that, given trends in usage, both packages are now essential.

No. Example given:  chroot environments.


> Closing this bug.

Thanks


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#942671: Let $year support SOURCE_DATE_EPOCH

[Mattias Ellert]

Package: doxygen
Version: 1.8.13-11
Severity: normal
Forwarded: https://github.com/doxygen/doxygen/pull/7341
Tags: patch

If I use an html footer file that contains:

Now is $datetime. This is $year.

and run doxygen the generated index.html contains:

Now is Sat Oct 19 2019 20:48:34. This is 2019.

as expected. However, if I set the SOURCE_DATE_EPOCH when running
doxygen

SOURCE_DATE_EPOCH=$(date +%s -d '2018-07-01 1200Z') doxygen

The generated index.html contains:

Now is Sun Jul 1 2018 12:00:00. This is 2019.

I.e the output of $datetime shows the SOURCE_DATE_EPOCH, but the $year
shows the current year. This (a) is inconsistent and (b) makes the
output non-reproducible.

With the change $year supports SOURCE_DATE_EPOCH the same way $datetime
does and the output is consistent:

Now is Sun Jul 1 2018 12:00:00. This is 2018.

Patch available in the upstream PR.

Mattias



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

Bug#942670: security-tracker: Fetching additional NVD feed information needs to switch to JSON feeds

[Salvatore Bonaccorso]

Package: security-tracker
Severity: normal

As per 16th of october the NVD XML data feeds is disabled[1]. The
security-tracker uses this feed to daily get additional information on
CVEs (e.g. description).

The update-nvd and the used parser lib/python/nvd.py needs to be
switched to get and parse the JSON feeds[2].

 [1] https://nvd.nist.gov/General/News/XML-Vulnerability-Feed-Retirement
 [2] https://nvd.nist.gov/vuln/data-feeds#JSON_FEED

Regards,
Salvatore

Bug#942668: jsonnet doesn't build for all supported python versions

[Matthias Klose]

Package: src:jsonnet
Version: 0.14.0+ds-1
Severity: important
Tags: sid bullseye

jsonnet doesn't build for all supported python versions, while b-d on 
python3-all-dev.  Either drop that b-d, or build the extension for all supported 
python versions.

Bug#942669: ldb doesn't build for all supported python versions

[Matthias Klose]

Package: src:ldb
Version: 2:2.0.7-3
Severity: important
Tags: sid bullseye

ldb doesn't build for all supported python versions, while b-d on 
python3-all-dev.  Either drop that b-d, or build the extension for all supported 
python versions.

Bug#937939: python-ncclient: diff for NMU version 0.6.0-2.1

[Sandro Tosi]

Control: tags 937939 + patch
Control: tags 937939 + pending


Dear maintainer,

I've prepared an NMU for python-ncclient (versioned as 0.6.0-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru python-ncclient-0.6.0/debian/changelog python-ncclient-0.6.0/debian/changelog
--- python-ncclient-0.6.0/debian/changelog	2019-02-13 12:11:13.0 -0500
+++ python-ncclient-0.6.0/debian/changelog	2019-10-19 16:00:42.0 -0400
@@ -1,3 +1,10 @@
+python-ncclient (0.6.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937939
+
+ -- Sandro Tosi   Sat, 19 Oct 2019 16:00:42 -0400
+
 python-ncclient (0.6.0-2) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru python-ncclient-0.6.0/debian/control python-ncclient-0.6.0/debian/control
--- python-ncclient-0.6.0/debian/control	2019-02-13 12:11:13.0 -0500
+++ python-ncclient-0.6.0/debian/control	2019-10-19 16:00:15.0 -0400
@@ -4,18 +4,10 @@
 Maintainer: Sebastien Badia 
 Build-Depends: debhelper (>= 11~),
dh-python,
-   python-all,
-   python-setuptools,
-   python-sphinx,
python3-all,
python3-setuptools,
python3-sphinx
-Build-Depends-Indep: python-lxml,
- python-mock,
- python-nose,
- python-paramiko,
- python-six,
- python3-lxml,
+Build-Depends-Indep: python3-lxml,
  python3-mock,
  python3-nose,
  python3-paramiko,
@@ -26,28 +18,6 @@
 Homepage: https://github.com/ncclient/ncclient
 Testsuite: autopkgtest-pkg-python
 
-Package: python-ncclient
-Architecture: all
-Pre-Depends: ${misc:Pre-Depends}
-Depends: python-lxml,
- python-paramiko,
- python-six,
- ${misc:Depends},
- ${python:Depends}
-Suggests: python-ncclient-doc
-Description: Python library for NETCONF clients (Python 2)
- ncclient is a Python library that facilitates client-side scripting
- and application development around the NETCONF protocol.
- .
- NETCONF (Network Configuration Protocol) provides mechanisms to install,
- manipulate, and delete the configuration of network devices. Its operations
- are realized on top of a simple remote procedure call (RPC) layer.
- .
- The NETCONF protocol uses an Extensible Markup Language (XML) based data
- encoding for the configuration data as well as the protocol messages.
- .
- This package provides the Python 2 version of the library.
-
 Package: python3-ncclient
 Architecture: all
 Pre-Depends: ${misc:Pre-Depends}
diff -Nru python-ncclient-0.6.0/debian/python-ncclient.docs python-ncclient-0.6.0/debian/python-ncclient.docs
--- python-ncclient-0.6.0/debian/python-ncclient.docs	2019-02-13 12:11:13.0 -0500
+++ python-ncclient-0.6.0/debian/python-ncclient.docs	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-README.md
diff -Nru python-ncclient-0.6.0/debian/python-ncclient.examples python-ncclient-0.6.0/debian/python-ncclient.examples
--- python-ncclient-0.6.0/debian/python-ncclient.examples	2019-02-13 12:11:13.0 -0500
+++ python-ncclient-0.6.0/debian/python-ncclient.examples	1969-12-31 19:00:00.0 -0500
@@ -1,2 +0,0 @@
-examples/*.py
-examples/juniper/*.py
diff -Nru python-ncclient-0.6.0/debian/rules python-ncclient-0.6.0/debian/rules
--- python-ncclient-0.6.0/debian/rules	2019-02-13 12:11:13.0 -0500
+++ python-ncclient-0.6.0/debian/rules	2019-10-19 16:00:42.0 -0400
@@ -3,11 +3,11 @@
 export PYBUILD_NAME = ncclient
 
 %:
-	dh $@ --buildsystem=pybuild --with python2,python3,sphinxdoc
+	dh $@ --buildsystem=pybuild --with python3,sphinxdoc
 
 override_dh_auto_test:
 ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS)))
-	nosetests test --verbosity=3 ncclient
+	nosetests3 test --verbosity=3 ncclient
 endif
 
 # Split package and documentation

Bug#942658: lintian: False positive for Python 2 python-package-missing-depends-on-python

[Chris Lamb]

Matthias Klose wrote:

> Please can we also have now an error if any unversioned depdency is 
> used (except 
> for the -all-) ones, or if python is used as the shebang?

(I think this already has its own bug report.)


Regards,

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

Bug#942658: lintian: False positive for Python 2 python-package-missing-depends-on-python

[Matthias Klose]

Please can we also have now an error if any unversioned depdency is used (except 
for the -all-) ones, or if python is used as the shebang?


Matthias

Bug#941414: certificates about to expire

[Mattia Rizzolo]

On Sat, Oct 19, 2019 at 08:14:33PM +0200, Florian Zumbiehl wrote:
> Is there any plan to fix this bug before then, or will users have to work
> around this individually to avoid running into expired certificates? And if
> the latter, what is the recommended workaround? Is the current backports
> version usable?

The current version in stretch-backports is perfectly usable.  It also
moves to the v2 version of the ACME API, which is the only one that
Let's Encrypt now supports.

In fact, the proposed "fix" I'm working on is to actually get the
version that is currently in backports directly in the oldstable
distribution, but I need to tweak it a bit as to do that I need to
reintroduce the 'letsencrypt.sh' compatibility packages/scripts.

So, yes, if you are affected by this bug I recommended to just use the
version in stretch-backports.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#942667: cracklib2 ignores build failures

[Matthias Klose]

Package: src:cracklib
Version: 2.9.6-2
Severity: serious
Tags: sid bullseye

cracklib2 ignores build failures, not setting -e for all the loops iterating 
over python versions.  Seen with 3.8 as a supported python version.

Bug#942664: debootstrap: please include mdadm and lvm2

[Geert Stappers]

On Sat, Oct 19, 2019 at 12:25:43PM -0700, Felix Lechner wrote:
> mdadm or lvm2
> so that the tools are automatically available

Qouting manaul page of `debootstrap`

 --include=alpha,beta
 Comma separated list of packages which will be
 added to download and extract lists.



I think that allows to close this wishlist report.


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#942666: fix ftbfs with python3.8

[Matthias Klose]

Package: src:pycairo
Version: 1.16.2-1
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

Patch at
http://launchpadlibrarian.net/447566367/pycairo_1.16.2-1build3_1.16.2-1ubuntu1.diff.gz

Bug#942661: ldh-gui-suite: Unusual term URI in Debconf template

[Jonas Smedegaard]

Quoting Helge Kreutzmann (2019-10-19 20:38:28)
> While translating the Debconf template into German we noticed the
> following in your original text:
> 
> "This URI will also be used by other programs. It should be the single "
> "unified reference information (URI)."
> 
> Normaly, URI references "Uniform Resource Identifier" [1] which would make 
> sense in a text dealing with network adressing. 
> 
> There are two possible interpretations:
> a) In your Debconf template / your programme URI actually means
>something different. Then this needs to be stressed further, as
>otherweise readers might confuse the two concepts. Please add a
>sentence (or paragraph) to this effect in this case.
> 
> b) The template uses URI in its usual meaning[1] and the Debconf
>template incorrectly expands the term. Then the patch is
>straighforward, i.e.
>unified reference information → Uniform Resource Identifier
> 
> Either way, there is a defect.
> 
> Please let me know which solution is the correct one, and kindly
> provide me with the updated template, so I can submit the German
> translation based on the corrected template text.

Good catch!

Intent was b) and I am now releasing a fixed package which I believe 
should trigger your getting a new gettext template automatically.
Otherwise please do nudge me, and I shall send it to you directly.


Thanks a lot for reporting this, and for your help translating!

 - Jonas


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

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


signature.asc
Description: signature

Bug#942403: golang-github-hashicorp-raft breaks golang-github-canonicalltd-raft-membership autopkgtest

[Pierre-Elliott Bécue]

Le mardi 15 octobre 2019 à 21:08:17+0200, Paul Gevers a écrit :
> Hi,
> 
> On 15-10-2019 21:00, Paul Gevers wrote:
> > github.com/CanonicalLtd/raft-membership
> >dh_auto_test -O--buildsystem=golang
> > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 
> > github.com/CanonicalLtd/raft-membership
> > # github.com/CanonicalLtd/raft-test/internal/network
> > src/github.com/CanonicalLtd/raft-test/internal/network/network.go:53:2: 
> > cannot use transport (type *eventTransport) as type raft.Transport in 
> > return argument:
> > *eventTransport does not implement raft.Transport (missing TimeoutNow 
> > method)
> > FAILgithub.com/CanonicalLtd/raft-membership [build failed]
> > dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 
> > github.com/CanonicalLtd/raft-membership returned exit code 2
> > make: *** [debian/rules:4: build] Error 255
> 
> By the way, this also looks very much like the error message in
> golang-github-canonicalltd-raft-test
> 
> Paul
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-canonicalltd-raft-test/3142465/log.gz
> 
> github.com/CanonicalLtd/raft-test/internal/network
> # github.com/CanonicalLtd/raft-test/internal/network
> src/github.com/CanonicalLtd/raft-test/internal/network/network.go:53:2:
> cannot use transport (type *eventTransport) as type raft.Transport in
> return argument:
>   *eventTransport does not implement raft.Transport (missing TimeoutNow
> method)
> dh_auto_build: cd obj-x86_64-linux-gnu && go install
> -gcflags=all=\"-trimpath=/tmp/autopkgtest-lxc.bqaeo2pm/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
> -asmflags=all=\"-trimpath=/tmp/autopkgtest-lxc.bqaeo2pm/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
> -v -p 2 github.com/CanonicalLtd/raft-test
> github.com/CanonicalLtd/raft-test/internal/election
> github.com/CanonicalLtd/raft-test/internal/event
> github.com/CanonicalLtd/raft-test/internal/fsms
> github.com/CanonicalLtd/raft-test/internal/logging
> github.com/CanonicalLtd/raft-test/internal/network returned exit code 2

Dear Paul,

Thanks for the bug report.

It seems to me that this bug is caused by the current version of
golang-github-canonicalltd-raft-test in the archive.

I'll upload the latest version ASAP.

I'm not sure if I should reassign the bug to
golang-github-canonicalltd-raft-test , feel free to do so.

Cheers!

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#942665: fix ftbfs with python3.8

[Matthias Klose]

Package: src:python-crypto
Version: 2.6.1-10
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

fix ftbfs with python3.8, patch at
http://launchpadlibrarian.net/447568553/python-crypto_2.6.1-10build1_2.6.1-10ubuntu1.diff.gz

Bug#942646: libxslt: diff for NMU version 1.1.32-2.2

[Salvatore Bonaccorso]

Control: tags 942646 + patch
Control: tags 942646 + pending


Dear maintainer,

I've prepared an NMU for libxslt (versioned as 1.1.32-2.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Additionally there is a merge request for the packagin repository at
https://salsa.debian.org/xml-sgml-team/libxslt/merge_requests/3 .

Regards,
Salvatore
diff -Nru libxslt-1.1.32/debian/changelog libxslt-1.1.32/debian/changelog
--- libxslt-1.1.32/debian/changelog	2019-08-04 08:14:05.0 +0200
+++ libxslt-1.1.32/debian/changelog	2019-10-19 21:21:23.0 +0200
@@ -1,3 +1,10 @@
+libxslt (1.1.32-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix dangling pointer in xsltCopyText (CVE-2019-18197) (Closes: #942646)
+
+ -- Salvatore Bonaccorso   Sat, 19 Oct 2019 21:21:23 +0200
+
 libxslt (1.1.32-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libxslt-1.1.32/debian/patches/0009-Fix-dangling-pointer-in-xsltCopyText.patch libxslt-1.1.32/debian/patches/0009-Fix-dangling-pointer-in-xsltCopyText.patch
--- libxslt-1.1.32/debian/patches/0009-Fix-dangling-pointer-in-xsltCopyText.patch	1970-01-01 01:00:00.0 +0100
+++ libxslt-1.1.32/debian/patches/0009-Fix-dangling-pointer-in-xsltCopyText.patch	2019-10-19 21:21:23.0 +0200
@@ -0,0 +1,35 @@
+From: Nick Wellnhofer 
+Date: Sat, 17 Aug 2019 16:51:53 +0200
+Subject: Fix dangling pointer in xsltCopyText
+Origin: https://gitlab.gnome.org/GNOME/libxslt/commit/2232473733b7313d67de8836ea3b29eec6e8e285
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2019-18197
+Bug-Debian: https://bugs.debian.org/942646
+Bug: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15746
+Bug: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15768
+Bug: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15914
+
+xsltCopyText didn't reset ctxt->lasttext in some cases which could
+lead to various memory errors in relation with CDATA sections in input
+documents.
+
+Found by OSS-Fuzz.
+---
+ libxslt/transform.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/libxslt/transform.c b/libxslt/transform.c
+index 95ebd0732f95..d7ab0b6677cc 100644
+--- a/libxslt/transform.c
 b/libxslt/transform.c
+@@ -1094,6 +1094,8 @@ xsltCopyText(xsltTransformContextPtr ctxt, xmlNodePtr target,
+ 	if ((copy->content = xmlStrdup(cur->content)) == NULL)
+ 		return NULL;
+ 	}
++
++	ctxt->lasttext = NULL;
+ } else {
+ /*
+ 	 * normal processing. keep counters to extend the text node
+-- 
+2.20.1
+
diff -Nru libxslt-1.1.32/debian/patches/series libxslt-1.1.32/debian/patches/series
--- libxslt-1.1.32/debian/patches/series	2019-08-04 08:14:05.0 +0200
+++ libxslt-1.1.32/debian/patches/series	2019-10-19 21:21:23.0 +0200
@@ -6,3 +6,4 @@
 0006-Fix-security-framework-bypass.patch
 0007-Fix-uninitialized-read-of-xsl-number-token.patch
 0008-Fix-uninitialized-read-with-UTF-8-grouping-chars.patch
+0009-Fix-dangling-pointer-in-xsltCopyText.patch

Bug#942664: debootstrap: please include mdadm and lvm2

[Felix Lechner]

Package: debootstrap
Severity: wishlist

Hi,

Many modern setups use mdadm or lvm2 (even on root) but both are hard
to come by after rebooting. Would it make sense to include both of
them in the scripts so that the tools are automatically available?

Kind regards
Felix Lechner

Bug#942663: apparmor b-d's on python3-all-dev, but only builds for the default version

[Matthias Klose]

Package: src:apparmor
Version: 2.13.3-5
Severity: important
Tags: sid bullseye

apparmor b-d's on python3-all-dev, but only builds for the default version. This 
makes it harder to prepare python transitions. Please build for all supported 
python versions.


Example build log at
https://launchpad.net/ubuntu/+source/apparmor/2.13.3-5ubuntu2/+build/17926986

Bug#929224: debootstrap & apt-cacher-ng: works here

[Felix Lechner]

Hi Sean,

>root@iris:/srv/chroot>http_proxy=http://localhost:3142 debootstrap sid 
> chr/ http://deb.debian.org/debian

I use commands like that from time to time (and did twice yesterday).
They work here.

As far as I can tell, the only part of my setup that is non-standard
is that I uncommented the line that was mentioned already:

PassThroughPattern: .*

In my case, the edit was a holdover from November 2017 (and unrelated
to this bug). If the standard setup is broken, it would have happened
since then. I am furthermore under the impression that apt-cacher-ng
started shipping with this change in September 2018, but apparently
that did not work for you. You filed this report in 2019.

My configuration is attached. Perhaps the problem is (or temporarily
was) in the HTTP headers from deb.debian.org?

Kind regards,
Felix Lechner


acng.conf
Description: Binary data

Bug#942662: libxml2: rejects valid NCName characters

[brian m. carlson]

Package: libxml2
Version: 2.9.4+dfsg1-7+b3
Severity: normal

XML 1.0 Fifth Edition dramatically increased the range of characters
allowed in an NCName, and therefore in an ID (such as an xml:id
attribute).  However, libxml2 is still using the obsolete fourth
edition, which means that it rejects well-formed documents.

For example, the following is a well-formed document which is rejected:

---

---

Because the document is erroneously considered ill-formed, xsltproc
cannot process it, either.

The fifth edition came out in 2008, so this is not a new phenomenon.  In
fact, upstream has a bug open with fixed files at
https://bugzilla.gnome.org/show_bug.cgi?id=675373; a suitable patch
should be applied to the Debian package.  If desired, I can synthesize
the files in that bug report into an actual patch, should it be applied.

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

Kernel: Linux 5.3.0-trunk-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libxml2 depends on:
ii  libc6 2.29-2
ii  libicu63  63.2-2
ii  liblzma5  5.2.4-1+b1
ii  zlib1g1:1.2.11.dfsg-1+b1

libxml2 recommends no packages.

libxml2 suggests no packages.

-- no debconf information

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204


signature.asc
Description: PGP signature

Bug#940872: Bug#942654: kde-baseapps: Numlock state not changed per settings during startup or screenlock

[Diederik de Haas]

On zaterdag 19 oktober 2019 19:18:36 CEST Brian R. wrote:
> I've set numlock "on" at login in KDE system settings, but after recent
> updates, the numlock state is no longer applied per user settings. Numlock
> must be turned on manually.

Sounds like you have the same problem as I reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872#15
It seems to be the exact opposite of what the OP filed, but I suspect it's all 
the same issue.


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

Bug#941414: certificates about to expire

[Florian Zumbiehl]

Hi,

as the recommended strategy by LetsEncrypt is to renew certificates 30 days
before their expiry, and we are approaching 30 days since the change that
exposed this bug that thus is preventing certificate renewal since then,
certificates generated using dehydrated are going to start expiring in
about a week.

Is there any plan to fix this bug before then, or will users have to work
around this individually to avoid running into expired certificates? And if
the latter, what is the recommended workaround? Is the current backports
version usable?

Regards, Florian

Bug#919504: Bug

[Leandro Lucarella]

Hi Dmitry,

On Wed, 18 Sep 2019 16:45:51 +0300 Dmitry Shachnev  
wrote:
> Hi Melvin!
[snip]
> Thanks for your analysis. We are going to update the whole Qt to 5.12 
soon
> in unstable.

Thanks for the update. Do you have any idea of how soon "soon" will be? 
I'm experiencing this issue too and since it's been a month until the last 
message in this issue, I would like to know if I should find a workaround 
for some time or if I can just wait for Qt 5.12.0 to be available in 
unstable.

I noticed it is in experimental but making a naive attempt to upgrade to 
the experimental package by doing a:

sudo apt install -t experimental libqt5webengine5 libqt5gui5

apt say it will remove hundreds of packages including the whole KDE :)


Thanks again!

-- 
Leandro Lucarella (Luca)
https://llucax.com

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

Bug#942661: ldh-gui-suite: Unusual term URI in Debconf template

[Helge Kreutzmann]

Package: ldh-gui-suite
Version: 0.1~20190927-1
Severity: minor

While translating the Debconf template into German we noticed the
following in your original text:

"This URI will also be used by other programs. It should be the single "
"unified reference information (URI)."

Normaly, URI references "Uniform Resource Identifier" [1] which would make 
sense in a text dealing with network adressing. 

There are two possible interpretations:
a) In your Debconf template / your programme URI actually means
   something different. Then this needs to be stressed further, as
   otherweise readers might confuse the two concepts. Please add a
   sentence (or paragraph) to this effect in this case.

b) The template uses URI in its usual meaning[1] and the Debconf
   template incorrectly expands the term. Then the patch is
   straighforward, i.e.
   unified reference information → Uniform Resource Identifier

Either way, there is a defect.

Please let me know which solution is the correct one, and kindly
provide me with the updated template, so I can submit the German
translation based on the corrected template text.

Thanks

[1] https://en.wikipedia.org/wiki/URI

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

Kernel: Linux 5.2.13 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#942660: ipython: Could you package the 7.x version

[Picca Frédéric-Emmanuel]

Package: ipython
Version: 5.8.0-1
Severity: wishlist

Dear Maintainer,

it would be nice if Debian could beneficiate from the latest ipython

thanks for considering

Frederic

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

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

Versions of packages ipython depends on:
ii  python-ipython  5.8.0-1

ipython recommends no packages.

ipython suggests no packages.

-- no debconf information

Bug#938159: python-scrypt: diff for NMU version 0.8.0-0.2

[Sandro Tosi]

Control: tags 938159 + patch


Dear maintainer,

I've prepared an NMU for python-scrypt (versioned as 0.8.0-0.2). The diff
is attached to this message.

I've uploaded directly to unstable as it's a NMU of a NMU

Regards.

diff -Nru python-scrypt-0.8.0/debian/changelog python-scrypt-0.8.0/debian/changelog
--- python-scrypt-0.8.0/debian/changelog	2017-10-05 11:07:52.0 -0400
+++ python-scrypt-0.8.0/debian/changelog	2019-10-19 14:15:30.0 -0400
@@ -1,3 +1,10 @@
+python-scrypt (0.8.0-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #938159
+
+ -- Sandro Tosi   Sat, 19 Oct 2019 14:15:30 -0400
+
 python-scrypt (0.8.0-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-scrypt-0.8.0/debian/control python-scrypt-0.8.0/debian/control
--- python-scrypt-0.8.0/debian/control	2017-10-05 11:07:52.0 -0400
+++ python-scrypt-0.8.0/debian/control	2019-10-19 14:14:58.0 -0400
@@ -2,25 +2,9 @@
 Maintainer: Micah Anderson 
 Section: python
 Priority: optional
-Build-Depends: python-all-dev, debhelper (>= 9), libssl-dev, python3-all-dev, python-setuptools, python3-setuptools
+Build-Depends: debhelper (>= 9), libssl-dev, python3-all-dev, python3-setuptools
 Standards-Version: 3.9.4
 
-Package: python-scrypt
-Architecture: any
-Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
-Description: bindings for the scrypt key derivation function library - Python 2.7
- This is a set of Python bindings for the scrypt key derivation function. 
- .
- Scrypt is useful when encrypting password as it is possible to specify a
- minimum amount of time to use when encrypting and decrypting. If, for
- example, a password takes 0.05 seconds to verify, a user won't notice the
- slight delay when signing in, but doing a brute force search of several
- billion passwords will take a considerable amount of time. This is in
- contrast to more traditional hash functions such as MD5 or the SHA family
- which can be implemented extremely fast on cheap hardware.
- .
- This package provides the Python 2.7 module.
-
 Package: python3-scrypt
 Architecture: any
 Depends: ${misc:Depends}, ${python3:Depends}, ${shlibs:Depends}
diff -Nru python-scrypt-0.8.0/debian/python-scrypt.lintian-overrides python-scrypt-0.8.0/debian/python-scrypt.lintian-overrides
--- python-scrypt-0.8.0/debian/python-scrypt.lintian-overrides	2013-05-30 21:53:38.0 -0400
+++ python-scrypt-0.8.0/debian/python-scrypt.lintian-overrides	1969-12-31 19:00:00.0 -0500
@@ -1,4 +0,0 @@
-# Only the debian packaging is covered by the GPL, the rest is a 2-clause BSD
-# tell lintian to not complain:
-python-scrypt: possible-gpl-code-linked-with-openssl
-
diff -Nru python-scrypt-0.8.0/debian/rules python-scrypt-0.8.0/debian/rules
--- python-scrypt-0.8.0/debian/rules	2017-10-05 11:07:52.0 -0400
+++ python-scrypt-0.8.0/debian/rules	2019-10-19 14:15:30.0 -0400
@@ -1,17 +1,7 @@
 #!/usr/bin/make -f
 
-PYTHONS:=$(shell pyversions -vr)
-PYTHON3S:=$(shell py3versions -vr)
-
 %:
-	dh $@ --with python2,python3 --buildsystem=python_distutils
+	dh $@ --with python3 --buildsystem=pybuild
 
-override_dh_auto_install:
-	set -e ; for pyvers in $(PYTHONS); do \
-		python$$pyvers setup.py install --install-layout=deb \
-			--root $(CURDIR)/debian/python-scrypt; \
-	done
-	set -e ; for pyvers in $(PYTHON3S); do \
-		python$$pyvers setup.py install --install-layout=deb \
-			--root $(CURDIR)/debian/python3-scrypt; \
-	done
+override_dh_auto_test:
+	:  # TODO: skip tests, they were never run before anyway

Bug#938466: seqdiag: diff for NMU version 0.9.5+dfsg-1.2

[Sandro Tosi]

Control: tags 938466 + patch


Dear maintainer,

I've prepared an NMU for seqdiag (versioned as 0.9.5+dfsg-1.2). The diff
is attached to this message.

I've uploaded directly to unstable as it fixes an RC bug, and it's an NMU of
an NMU

Regards.

diff -Nru seqdiag-0.9.5+dfsg/debian/changelog seqdiag-0.9.5+dfsg/debian/changelog
--- seqdiag-0.9.5+dfsg/debian/changelog	2018-07-16 04:57:18.0 -0400
+++ seqdiag-0.9.5+dfsg/debian/changelog	2019-10-19 14:10:26.0 -0400
@@ -1,3 +1,10 @@
+seqdiag (0.9.5+dfsg-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #938466
+
+ -- Sandro Tosi   Sat, 19 Oct 2019 14:10:26 -0400
+
 seqdiag (0.9.5+dfsg-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru seqdiag-0.9.5+dfsg/debian/control seqdiag-0.9.5+dfsg/debian/control
--- seqdiag-0.9.5+dfsg/debian/control	2016-10-11 00:33:57.0 -0400
+++ seqdiag-0.9.5+dfsg/debian/control	2019-10-19 14:09:52.0 -0400
@@ -4,13 +4,7 @@
 Maintainer: Kouhei Maeda 
 Build-Depends: debhelper (>= 8.0.0),
dh-python,
-   python-all,
-   python-setuptools,
pep8 (>= 1.3),
-   python-nose,
-   python-unittest2,
-   python-reportlab,
-   python-blockdiag (>= 1.5.0),
python3-all,
python3-setuptools,
python3-pep8 (>= 1.3),
@@ -19,19 +13,8 @@
python3-blockdiag (>= 1.5.0),
fonts-vlgothic | fonts-japanese-gothic
 Standards-Version: 3.9.8
-X-Python-Version: 2.7
 Homepage: http://blockdiag.com/
 
-Package: python-seqdiag
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${misc:Depends}, ${python:Depends},
- python-blockdiag (>= 1.5.0)
-Description: seqdiag generate sequence-diagram image file from spec-text file
- Generate sequence-diagram from dot like text with multilingualization for
- node-label. But this supports utf-8 only. And get some examples and generated
- images.
-
 Package: python3-seqdiag
 Architecture: all
 Depends: ${misc:Depends}, ${python3:Depends},
diff -Nru seqdiag-0.9.5+dfsg/debian/python-seqdiag.manpages seqdiag-0.9.5+dfsg/debian/python-seqdiag.manpages
--- seqdiag-0.9.5+dfsg/debian/python-seqdiag.manpages	2011-11-03 13:02:27.0 -0400
+++ seqdiag-0.9.5+dfsg/debian/python-seqdiag.manpages	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-seqdiag.1
diff -Nru seqdiag-0.9.5+dfsg/debian/rules seqdiag-0.9.5+dfsg/debian/rules
--- seqdiag-0.9.5+dfsg/debian/rules	2014-08-31 22:31:04.0 -0400
+++ seqdiag-0.9.5+dfsg/debian/rules	2019-10-19 14:10:11.0 -0400
@@ -7,7 +7,7 @@
 export PYBUILD_NAME=seqdiag
 
 %:
-	dh $@ --with python2,python3 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_python3:
 	dh_python3

Bug#942659: pwman3: [INTL:pt] Updated Portuguese translation - debconf messages

[Américo Monteiro]

Package: pwman3
Version: 0.10.0-1
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for pwman3's debconf messages
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' 

-- 
Melhores cumprimentos/Best regards,

Américo Monteiro

-

pwman3_0.10.0-1_pt.po.gz
Description: application/gzip

Bug#942658: lintian: False positive for Python 2 python-package-missing-depends-on-python

[Andreas Bombe]

Package: lintian
Version: 2.28.0
Severity: normal

I'm starting to get a python-package-missing-depends-on-python error on
a package that didn't have it in its previous revision (with only minor
changes).

Comparing the built packages shows that the latest version of dh-python
now generates dependencies on python2 instead of python. However,
lintian only considers python and python-minimal as a valid Python 2
dependency.

Adding python2 and python2-minimal to the list of Python 2 package names
should be sufficient to fix this.

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages lintian depends on:
ii  binutils 2.33.1-1
ii  bzip21.0.8-2
ii  diffstat 1.62-1+b1
ii  dpkg 1.19.7
ii  dpkg-dev 1.19.7
ii  file 1:5.37-5
ii  gettext  0.19.8.1-9
ii  gpg  2.2.17-3
ii  intltool-debian  0.35.0+20060710.5
ii  libapt-pkg-perl  0.1.36+b2
ii  libarchive-zip-perl  1.67-1
ii  libcapture-tiny-perl 0.48-1
ii  libcgi-pm-perl   4.44-1
ii  libclass-accessor-perl   0.51-1
ii  libclone-perl0.41-1+b2
ii  libdpkg-perl 1.19.7
ii  libemail-valid-perl  1.202-1
ii  libfile-basedir-perl 0.08-1
ii  libfile-find-rule-perl   0.34-1
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl 0.74-1
ii  libipc-run-perl  20180523.0-1
ii  liblist-compare-perl 0.53-1
ii  liblist-moreutils-perl   0.416-1+b5
ii  libmoo-perl  2.003004-2
ii  libpath-tiny-perl0.108-1
ii  libtext-levenshtein-perl 0.13-1
ii  libtimedate-perl 2.3000-2
ii  libtry-tiny-perl 0.30-1
ii  libtype-tiny-perl1.004004-1
ii  liburi-perl  1.76-1
ii  libxml-simple-perl   2.25-1
ii  libyaml-libyaml-perl 0.80+repack-2+b1
ii  man-db   2.8.7-3
ii  patchutils   0.3.4-2+b1
ii  perl [libdigest-sha-perl]5.30.0-7
ii  t1utils  1.41-3
ii  xz-utils 5.2.4-1+b1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b6

Versions of packages lintian suggests:
ii  binutils-multiarch 2.33.1-1
ii  libhtml-parser-perl3.72-3+b4
ii  libtext-template-perl  1.55-1

-- no debconf information

Bug#940589: git-debpush: undeclared perl dependency

[Sean Whitton]

Hello,

On Tue 17 Sep 2019 at 12:26PM +02, Andrej Shadura wrote:

> When I attempt to run git-debpush, I see this error:
>
> Can't locate Git/Wrapper.pm in @INC (you may need to install the 
> Git::Wrapper module) (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
> /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
> /usr/bin/git-deborig line 93.
> BEGIN failed--compilation aborted at /usr/bin/git-deborig line 93.

This error is being emitted by git-deborig from devscripts, which needs
Git::Wrapper.  devscripts Recommends: libgit-wrapper-perl, but does not
Depends: on it, because it is devscripts package policy not to hard
depend on libraries needed by singular scripts in devscripts (see README
in devscripts).

So I suspect that you ran into this because when you installed
devscripts, you did not install all its Recommends: too.

dgit's test suite isn't detecting this (presumably) because when it
installs devscripts, it also installs all of devscripts recommendations.

I think it would be reasonable to fix this by having bin:git-debpush
hard depend on libgit-wrapper-perl, even though it's an annoying sort of
thing to have to keep up-to-date.

If Ian agrees with that solution, we should probably have the dgit test
suite stop installing all of the packages recommended by devscripts, so
we can hard depend on anything else that we know we need.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#940588: git-debpush: pipefail in get_file_from_ref

[Sean Whitton]

Hello,

On Tue 17 Sep 2019 at 12:24PM +02, Andrej Shadura wrote:

> In line 61, grep -Eq may cause a pipefail if grep exits before git
> ls-tree concludes. With a debug print for $? I can see this:

Here's a patch implementing the fix.  Thank you for the report!

-- 
Sean Whitton
From 446b5b8c9c8179cd6f516fc5460ba70147c94e61 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Sat, 19 Oct 2019 10:33:10 -0700
Subject: [PATCH] git-debpush: avoid a pipefail problem in get_file_from_ref

`grep -q` exits as soon as it finds a matching line, potentially
sending a SIGPIPE to git-ls-tree.  We have pipefail turned on, so that
can make the whole pipeline exit nonzero, which is wrong when grep did
in fact find a match.

This solution is more readable than disabling pipefail just for this
line (as is done elsewhere in git-debpush).

Reported-by: Andrej Shadura 
Signed-off-by: Sean Whitton 
---
 git-debpush | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/git-debpush b/git-debpush
index c3b067dc..2790560c 100755
--- a/git-debpush
+++ b/git-debpush
@@ -59,8 +59,10 @@ badusage () {
 get_file_from_ref () {
 local path=$1
 
+# redirect to /dev/null instead of using `grep -Eq` to avoid grep
+# SIGPIPEing git-ls-tree
 if git ls-tree --name-only -r "$branch" \
-| grep -Eq "^$path$"; then
+| grep -E "^$path$" >/dev/null; then
 git cat-file blob $branch:$path
 fi
 }
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#942657: ldh-gui-suite: [INTL:pt] Updated Portuguese translation - debconf messages

[Américo Monteiro]

Package:ldh-gui-suite
Version: 0.1_20190927-1
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for ldh-gui-suite's debconf messages
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' 

-- 
Melhores cumprimentos/Best regards,

Américo Monteiro

-

ldh-gui-suite_0.1_20190927-1_pt.po.gz
Description: application/gzip

Bug#942656: pwman3: Minor errors in Debconf template

[Helge Kreutzmann]

Package: pwman3
Version: 0.10.0-1
Severity: minor
Tags: patch

While translating your template to German I noticed the following
errors in your Debconf template

-"It seems that your are trying to upgrade Pwman3 form version 0.5.x or older. "
+"It seems that your are trying to upgrade Pwman3 from version 0.5.x or older. "

-"exported, you will have to renamed your old database to keep a backup of it:"
+"exported, you will have to rename your old database to keep a backup of it:"

Please unfuzzy all translations after fixing these errors.

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

Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pwman3 depends on:
ii  python   2.7.16-1
pn  python-colorama  
pn  python-crypto

Versions of packages pwman3 recommends:
pn  python-mysqldb   
pn  python-pygresql  

Versions of packages pwman3 suggests:
ii  postgresql  11+200+deb10u2
pn  xsel

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#942655: pwman3: [INTL:de] initial German debconf translation

[Helge Kreutzmann]

Package: pwman3
Version: 0.10.0-1
Severity: wishlist
Tags: patch l10n

Please find the initial German debconf translation for pwman3
attached.

Please place this file in debian/po/ as de.po for your next upload.

If you update your template, please use 
'msgfmt --statistics '
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the pwman3 package.
# Helge Kreutzmann , 2019.
#
msgid ""
msgstr ""
"Project-Id-Version: pwman3 0.10.0-1\n"
"Report-Msgid-Bugs-To: pwm...@packages.debian.org\n"
"POT-Creation-Date: 2019-10-09 09:10+\n"
"PO-Revision-Date: 2019-10-19 19:22+0200\n"
"Last-Translator: Helge Kreutzmann \n"
"Language-Team: German \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: select
#. Description
#: ../templates:1001
msgid "Old database format detected"
msgstr "Altes Datenbankformat erkannt"

# FIXME form → from
#. Type: select
#. Description
#: ../templates:1001
msgid ""
"It seems that your are trying to upgrade Pwman3 form version 0.5.x or older. "
"The database is not compatible with the new database format. Before "
"upgrading you need to export your database to a CSV with:"
msgstr ""
"Es scheint, dass Sie ein Upgrade von Pwman3 Version 0.5.x oder älter "
"versuchen. Die Datenbank ist nicht mit dem neuen Datenbankformat kompatibel. "
"Vor dem Upgrade müssen Sie Ihre Datenbank in CSV konvertieren:"

#. Type: select
#. Description
#: ../templates:1001
msgid "  pwman> export"
msgstr "  pwman> export"

# FIXME have to renamed → have to rename
#. Type: select
#. Description
#: ../templates:1001
msgid ""
"That will create a CSV file located in $HOME/pwman-export.csv. Once "
"exported, you will have to renamed your old database to keep a backup of it:"
msgstr ""
"Damit wird eine unter $HOME/pwman-export.csv befindliche CSV-Datei erstellt. "
"Nach dem Export müssen Sie Ihre Datenbank umbenennen, um eine "
"Sicherungskopie zu behalten:"

#. Type: select
#. Description
#: ../templates:1001
msgid "  mv $HOME/pwman/pwman.db $HOME/pwman/pwman-old.db"
msgstr "  mv $HOME/pwman/pwman.db $HOME/pwman/pwman-alt.db"

#. Type: select
#. Description
#: ../templates:1001
msgid ""
"Then you can restart the package upgrade. Once the upgrade will be finished, "
"you will be able to import the CSV file previously generated:"
msgstr ""
"Dann können Sie das Paket-Upgrade neu starten. Sobald das Upgrade "
"durchgelaufen ist, können Sie die vorher erstellte CSV-Datei importieren:"

#. Type: select
#. Description
#: ../templates:1001
msgid "  pwman3 -i $HOME/pwman-export.csv \\;"
msgstr "  pwman3 -i $HOME/pwman-export.csv \\;"

#. Type: select
#. Description
#: ../templates:1001
msgid ""
"Don't forget to remove the CSV file when the import succeeded (the passwords "
"are stored in clear text in this file)."
msgstr ""
"Vergessen Sie nicht, die CSV-Datei zu entfernen, wenn der Import erfolgreich "
"war (die Passwörter sind in dieser Datei im Klartext gespeichert)."

Bug#942654: kde-baseapps: Numlock state not changed per settings during startup or screenlock

[Brian R.]

Package: kde-baseapps
Version: 4:17.08.3+5.104
Severity: normal

Dear Maintainer,

I've set numlock "on" at login in KDE system settings, but after recent
updates, the numlock state is no longer applied per user settings. Numlock must
be turned on manually. If screen locks due to inactivity, numlock state is lost
again and must be turned on manually. Verified that in KDE System Settings,
"Numlock on Plasma startup" option is checked "Yes."



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

Kernel: Linux 5.2.0-0.bpo.2-rt-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kde-baseapps depends on:
ii  dolphin 4:19.08.1-1
ii  kdialog 4:17.08.3-2
ii  keditbookmarks  17.08.3-2
ii  kfind   4:19.08.1-1
ii  konqueror   4:19.08.2-2
ii  konsole 4:19.08.1-2
ii  kwrite  4:19.08.2-1

kde-baseapps recommends no packages.

kde-baseapps suggests no packages.

-- no debconf information

Bug#936962: logbook: diff for NMU version 1.4.3-1.1

[Sandro Tosi]

Control: tags 936962 + patch
Control: tags 936962 + pending


Dear maintainer,

I've prepared an NMU for logbook (versioned as 1.4.3-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru logbook-1.4.3/debian/changelog logbook-1.4.3/debian/changelog
--- logbook-1.4.3/debian/changelog	2019-01-22 12:41:50.0 -0500
+++ logbook-1.4.3/debian/changelog	2019-10-19 13:12:36.0 -0400
@@ -1,3 +1,10 @@
+logbook (1.4.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #936962
+
+ -- Sandro Tosi   Sat, 19 Oct 2019 13:12:36 -0400
+
 logbook (1.4.3-1) unstable; urgency=medium
 
   [ Downstreamer ]
diff -Nru logbook-1.4.3/debian/control logbook-1.4.3/debian/control
--- logbook-1.4.3/debian/control	2019-01-22 12:41:50.0 -0500
+++ logbook-1.4.3/debian/control	2019-10-19 13:11:57.0 -0400
@@ -7,33 +7,18 @@
 Build-Depends:
  debhelper (>= 11),
  dh-python,
- python-all,
- python-setuptools,
  python3-all,
  python3-setuptools,
- python-sphinx (>= 1.0.7+dfsg) | python3-sphinx,
- python-docutils,
- python2.7-doc,
- cython,
+ python3-sphinx,
+ python3-docutils,
+ python3-doc,
  cython3,
- python2.7-dev,
- python3-dev,
+ python3-all-dev,
 Standards-Version: 4.1.4
 Homepage: http://pythonhosted.org/Logbook/
 Vcs-Git: https://salsa.debian.org/debian/logbook.git
 Vcs-Browser: https://salsa.debian.org/debian/logbook
 
-Package: python-logbook
-Architecture: any
-Depends: ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
-Suggests: python-logbook-doc,
-Description: logging system for Python that replaces the standard library's module
- Logbook is a logging system for Python that replaces the standard library's
- logging module. It was designed with both complex and simple applications in
- mind and the idea to make logging fun
- .
- This is the Python 2 version of the package.
-
 Package: python3-logbook
 Architecture: any
 Depends: ${python3:Depends}, ${misc:Depends}, ${shlibs:Depends}
diff -Nru logbook-1.4.3/debian/rules logbook-1.4.3/debian/rules
--- logbook-1.4.3/debian/rules	2019-01-22 12:41:50.0 -0500
+++ logbook-1.4.3/debian/rules	2019-10-19 13:12:36.0 -0400
@@ -9,7 +9,7 @@
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 
 %:
-	dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild
+	dh $@ --with python3,sphinxdoc --buildsystem=pybuild
 
 override_dh_auto_clean:
 	dh_auto_clean
@@ -17,7 +17,8 @@
 	rm -rf Logbook.egg-info
 
 override_dh_auto_build:
-	make cybuild
+	cython3 logbook/_speedups.pyx
+	python3 setup.py build_ext --inplace
 	dh_auto_build
 
 override_dh_auto_install:

Bug#942653: kde-plasma-desktop: On system start, primary display does not render background or allow r-click to access menu

[Brian R.]

Package: kde-plasma-desktop
Version: 5:104
Severity: important

Dear Maintainer,

System is Asus P8Z77 w/ Intel i7 2600K processor and AMD RTX5700 graphics. Dual
monitor setup with Samsung Syncmaster primary on DVI and LG smart TV secondary
on HDMI. LightDM is installed with Plasma and Cinnamon DE's.

After login from system start, the primary display will not have the background
wallpaper displayed; background is black. System tray shows and main menu is
accessible, but r-click on background to call up desktop menu not functional.
On secondary display however the wallpaper is displayed and the desktop menu
will appear with r-click. Logging out of session then logging back in generally
corrects the issue and functions as normal once new session starts with
background and desktop menu on r-click.

I've seen previous reports of similar behavior with Nvidea graphics; can
confirm bug exists with AMD graphics as well. Issue not present when logging
into Cinnamon.



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

Kernel: Linux 5.2.0-0.bpo.2-rt-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kde-plasma-desktop depends on:
ii  kde-baseapps  4:17.08.3+5.104
ii  plasma-desktop4:5.14.5.1-4
ii  plasma-workspace  4:5.14.5.1-3+b1
ii  udisks2   2.8.4-1
ii  upower0.99.11-1

Versions of packages kde-plasma-desktop recommends:
ii  kwin-x11  4:5.14.5-1
ii  sddm  0.18.0-1
ii  xserver-xorg  1:7.7+19

Versions of packages kde-plasma-desktop suggests:
ii  kdeconnect  1.3.3-2

-- no debconf information

Bug#886181: rrdtool: Please switch to automatic dbgsym package

[Jean-Michel Vourgère]

Control: tag -1 - wontfix + pending

I tried to enable the automatic debug symbol packages, with the python debug 
interface in a new python3-rrdtool-dbg package. However, lintian complains:
W: rrdtool changes: package-builds-dbg-and-dbgsym-variants python3-rrdtool-
{dbg,dbgsym}
N:
N:This package appears to build both -dbg and -dbgsym variants of a
N:package. Only one package should contain the debug symbols
N:
N:Usually the -dbg should be dropped in favour of the -dbgsym. However, in
N:some cases (e.g. Python modules) the -dbg contains more than just the
N:debug symbols. In these cases the -dbgsym should not be built.
N:
N:Refer to the dh_strip(1) manual page and
N:https://wiki.debian.org/AutomaticDebugPackages for details.
N:
N:Severity: normal, Certainty: certain
N:
N:Check: changes-file, Type: changes

So I did automatic symbols for all packages but python3-rrdtool, that will 
keep the old style -dbg package.

https://salsa.debian.org/rrdtool-team/rrdtool/commit/
fd6a82c71b50062a93a8a019c77a42129de1761f

Comments are welcome.

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

Bug#942449: Found a solution/workaround

[Alf]

To remove those dead drive icons I just edited /etc/fstab and appended
"x-gvfs-hide" to the mount options of those partititions like this:

UUID=ea5ad8...de2 /media/sda1 ext4
noatime,errors=remount-ro,noauto,x-gvfs-hide 0 0

Immediately the icons disappear , even without reboot.

So, it's just ea configuration error which reports partititions marked
"nouser" as removable. Whether it is xfdesktop4 or even a bug in gvfs I
don't know.

Bug#942315: tcpdump: Version in oldoldstable is higher than oldstable and stable

[Romain Francoise]

On Thu, Oct 17, 2019 at 10:02 AM Moritz Muehlenhoff  wrote:
> IMHO for stretch-security/buster-security we should rather rebase the old
> 4.9.2ish packages to 4.9.3, given that it creates new system users etc.
> it seems not really suitable for a security update.

Ok, that is what I did. Review welcome:

https://people.debian.org/~rfrancoise/tcpdump/tcpdump_4.9.3-1~deb10u1_source.changes
https://people.debian.org/~rfrancoise/tcpdump/tcpdump_4.9.3-1~deb9u1_source.changes

Thanks.

Bug#942652: RFS: libdata-url-java/1.0.1-1 [ITP] -- Support for data URLs according to RFC 2397

[Felix Natter]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "libdata-url-java"

 * Package name: libdata-url-java
   Version : 1.0.1-1
   Upstream Author : Rob Spoor (mail address not known)
 * URL : https://robtimus.github.io/data-url/
 * License : Apache-2.0
 * Vcs : https://salsa.debian.org/java-team/libdata-url-java
   Section : java

It builds those binary packages:

  libdata-url-java - Support for data URLs according to RFC 2397

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

  https://mentors.debian.net/package/libdata-url-java

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libd/libdata-url-java/libdata-url-java_1.0.1-1.dsc

Changes since the last upload:

   * Initial release. (Closes: #941916)

It is a simple maven package which is a dependency of freeplane-1.7.10.
The only thing to mention is that I replaced the i18n-maven-plugin (from
the upstream author) by String.format (see
01_replace_i18n_maven_plugin.patch).

@debian-java: Can I post the darcula package and its dependency
(remaining two dependencies for freeplane-1.7.10) directly on d-java, or
shall I do it via mentors?

Cheers and Best Regards,
--
Felix Natter

Bug#942651: Bugreport use a outdated URL

[Jörg Frings-Fürst]

Package: evolution
Version: 3.34.1-2+b1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

bugreport use the outeded URL

Forwarded-To: https://bugzilla.gnome.org/show_bug.cgi?id=

instead of

Forwarded-To: https://gitlab.gnome.org/GNOME/evolution/issues/


CU
Jörg



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages evolution depends on:
ii  dbus   1.12.16-2
ii  evolution-common   3.34.1-2
ii  evolution-data-server  3.34.1-1+b1
ii  libc6  2.29-2
ii  libcamel-1.2-623.34.1-1+b1
ii  libclutter-gtk-1.0-0   1.8.4-4
ii  libecal-2.0-1  3.34.1-1+b1
ii  libedataserver-1.2-24  3.34.1-1+b1
ii  libevolution   3.34.1-2+b1
ii  libglib2.0-0   2.62.1-1
ii  libgtk-3-0 3.24.12-1
ii  libical3   3.0.5-2
ii  libnotify4 0.7.8-1
ii  libsoup2.4-1   2.68.2-1
ii  libwebkit2gtk-4.0-37   2.26.1-3
ii  libxml22.9.4+dfsg1-7+b3
ii  psmisc 23.2-1+b1

Versions of packages evolution recommends:
ii  evolution-plugin-bogofilter  3.34.1-2+b1
ii  evolution-plugin-pstimport   3.34.1-2+b1
ii  evolution-plugins3.34.1-2+b1
ii  yelp 3.34.0-1

Versions of packages evolution suggests:
pn  evolution-ews   
pn  evolution-plugins-experimental  
ii  gnupg   2.2.17-3
ii  network-manager 1.20.4-2

- -- debconf-show failed

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl2rJA8ACgkQCfifPIyh
0l28BxAA12Ns++AT1b0HzvRAeOfuiVAA9Blb9R1vMWukyQvXuPQygJwrt5tT+fc3
8cuL+3QohgofJ2YVgBdAAYnjElgQ3DLGPOukoWz4VMJjPwe6w3m1ocC0fPMhEEfL
lwVLFvNyfV14SQku3BNtI09Jt93r7VpwQI/dlTwq0PeWkBXdm7YIwgCFp+tcxFzY
LCBDHtLVvMvxaQ+77jw9DlHcJb1WjxIJTdFy+JQ34IuCGU7vsmgsAGKIciLZ0BhS
fuYgwVSb5xq+AJjIKAaqkoFJuUCGR11LWrKb+u4dbmq0OSg8CLFZM4lTVIUsCJ/5
tX4ahVQbp+vBPjDyoiOWwfD4/E8wpGbZpO9qdvMvR30jiW7EXbQjnVecXAo6od2/
dmD3UMXBfGBL4mutiFGjG6OuQeS9J0dS3wJtXoYB++NCsv0SGjvlUOzN1aI8gdt4
tasz/tHNkMNro1ipk4ZGPupSoVuPSGGtI6mhjo7W716sHPAqZrRxgEn4KFNPndj1
QSNrZgjMGquMG4vPR7lK/9/omzDcEtwpjKIeY+kXMPPilbxeXnUdSOiu2qTNNZ2G
s6yZfduphy5sTqiROC93Is0rlxA+hb0dXrRsdj/ZcKfY04Hzu8y+YfWvG0ikdW/n
+ByyUUSm1PlOQv5pWCHXXC4VF715O5A4FRXmtezQvCLSnQBydJU=
=oSZP
-END PGP SIGNATURE-

Bug#938797: volatility: Python2 removal in sid/bullseye

[Eriberto]

Em sábado, 19 de outubro de 2019, Raphael Hertzog 
escreveu:

> Control: tag -1 + fixed-upstream
>
> On Fri, 30 Aug 2019, Matthias Klose wrote:
> > Python2 becomes end-of-live upstream, and Debian aims to remove
> > Python2 from the distribution, as discussed in
> > https://lists.debian.org/debian-python/2019/07/msg00080.html
>
> There's a volatility 3.0 that works with Python 3:
> https://github.com/volatilityfoundation/volatility3
>
> We should package it! Putting in CC the uploaders of volatility.
>
>
Don't worry. I will update it soon.

Cheers,

Eriberto


>

Bug#942650: Can't mark a folder tree as read

[Jörg Frings-Fürst]

Package: evolution
Version: 3.34.1-2+b1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Forwarded-To: https://gitlab.gnome.org/GNOME/evolution/issues/671


Hello,

since the last update to version 3.34.1 I can't mark a folder tree as read.

Before the update I get an popup to select same options. This popup is now
never shown.

The menue point is also greyed.

CU
Jörg



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages evolution depends on:
ii  dbus   1.12.16-2
ii  evolution-common   3.34.1-2
ii  evolution-data-server  3.34.1-1+b1
ii  libc6  2.29-2
ii  libcamel-1.2-623.34.1-1+b1
ii  libclutter-gtk-1.0-0   1.8.4-4
ii  libecal-2.0-1  3.34.1-1+b1
ii  libedataserver-1.2-24  3.34.1-1+b1
ii  libevolution   3.34.1-2+b1
ii  libglib2.0-0   2.62.1-1
ii  libgtk-3-0 3.24.12-1
ii  libical3   3.0.5-2
ii  libnotify4 0.7.8-1
ii  libsoup2.4-1   2.68.2-1
ii  libwebkit2gtk-4.0-37   2.26.1-3
ii  libxml22.9.4+dfsg1-7+b3
ii  psmisc 23.2-1+b1

Versions of packages evolution recommends:
ii  evolution-plugin-bogofilter  3.34.1-2+b1
ii  evolution-plugin-pstimport   3.34.1-2+b1
ii  evolution-plugins3.34.1-2+b1
ii  yelp 3.34.0-1

Versions of packages evolution suggests:
pn  evolution-ews   
pn  evolution-plugins-experimental  
ii  gnupg   2.2.17-3
ii  network-manager 1.20.4-2

- -- debconf-show failed

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl2rIwUACgkQCfifPIyh
0l2yDRAAkQE6FfbH0NePG07rOj0i38KjKi/tREScG7E1eyRQ5zysUOfp/ZQNHQne
YKA9hrMVrq6SHgudFBgAzYZrhGRw1tioIFFSm+oCX+eWG5ut3O1+dQVVRjliPHVL
hrAP1zIH1OWcIOb4izx7VCBPUMFQVqE8s7ujbPedQm8hc7HPCcGZHti8uNJoVhc0
y6x7GxkkAdEaM3TG9N2Ks+Ja5EeDSQjXlzYyvm9+AT2Wmgj/uL1wrKIvnXlwBeGG
OD4r6Yu8JCBQ6+GEN038Oyl8P/9SDRR44gzsupNqHddAWgV6hRlNCdeuy/r4+uhl
BsxJ6uHRW7BGcvj7SXpGDfsdItJh6aXrQ79coCuFUQinOvTDJgLvPr8ZI3h0dF/N
JZVRbGEXtIW0J3L10NF8TTLErRaJXFdTtiDTP5J/3tRxX7ixq7c8Ykd8qpDMLGtr
4usubHq6HyWwAHaKL1O17Oi/mpo/Aw9uSk7GXex79PaOHn16LQeU+Y6OXecUOlDc
W3t9eSn+KodSADnm9VNxNMOD4LuhLhWEd1jICggCyA88zS/shECqvvhutbJDTvpB
iRa+vaCwbWELQnlcpurPrKxyE0ABdErnX3rzQkDs0TMMIiVtgj5YxriCrop1JLZ2
WK3MWP20Sly78Xn9ciusHbbxcIqWJdKJb8DyzZs6vHjpxXNlv1I=
=+3r0
-END PGP SIGNATURE-

Bug#823706: Lazarus 1.6 source files are missing

[Abou Al Montacir]

More analysis of the issue showed that we want the lpk file contain when the lazarus-src package is not installed, but we probably
want to havewhen lazarus-src is installed.
So one solution is to package both file versions and used dpkg-divert  to
override lcl-units lpk files by those of lazarus-src when installed.
The other option is that that post install script of lazarus-src looks for the
installed lpk-files and modifies them, but this is probably an unwanted
behavior, especially that some lcl-units may be installed after lazarus-src
installation.
Any other idea?
-- 
Cheers,
Abou Al Montacir



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

Bug#678694: preseed_fetch fails with relative url

[Jonathan Leroy - Inikup]

This bug is still present in Buster.
Very simple workaround:

d-i preseed/early_command string echo "$(debconf-get preseed/url)" >
/var/run/preseed.last_location

-- 
Jonathan Leroy

Bug#942639: fix build with Python3.8 + unusual packaging of the debug extension

[Matthias Klose]

On 19.10.19 15:42, Jean-Michel Vourgère wrote:

Hi again

On Saturday, 19 October 2019 12:29:47 CEST Matthias Klose wrote:

The attached patch fixes the build with Python3.8.

Noticing that you package both the normal and the debug extension module in
the same package python3-rrdtool.  The latter should be packaged into a
python-rrdtool-dbg package.


Could you explain a bit more how is this a problem for python 3.8?

Buster version has:
   python3-rrdtool.install:
   usr/lib/python3*/dist-packages/rrdtool*[0-9]m-*.so

   rrdtool-dbg.install:
   usr/lib/python3*/dist-packages/rrdtool*[0-9]dm-*.so


After switching to automatic debug symbols with an extra python -dbg package:
   python3-rrdtool.install:
   usr/lib/python3*/dist-packages/rrdtool*[0-9]m-*.so

   python3-rrdtool-dbg.install:
   usr/lib/python3*/dist-packages/rrdtool*[0-9]dm-*.so

(This now generates a python3-rrdtool-dbg-dbgsym package)


But I fail to see how this helps with python 3.8. Are the .so name changed?
How so?


yes, the m modifier got dropped.

Bug#938797: volatility: Python2 removal in sid/bullseye

[Raphael Hertzog]

Control: tag -1 + fixed-upstream

On Fri, 30 Aug 2019, Matthias Klose wrote:
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html

There's a volatility 3.0 that works with Python 3:
https://github.com/volatilityfoundation/volatility3

We should package it! Putting in CC the uploaders of volatility.

Cheers,

PS: I filed https://github.com/volatilityfoundation/volatility3/issues/95
requesting a 3.x release because right now they provide volatility3
version 1.0.0 :(
-- 
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#942639: fix build with Python3.8 + unusual packaging of the debug extension

[Jean-Michel Vourgère]

Hi again

On Saturday, 19 October 2019 12:29:47 CEST Matthias Klose wrote:
> The attached patch fixes the build with Python3.8.
> 
> Noticing that you package both the normal and the debug extension module in
> the same package python3-rrdtool.  The latter should be packaged into a
> python-rrdtool-dbg package.

Could you explain a bit more how is this a problem for python 3.8?

Buster version has:
  python3-rrdtool.install:
  usr/lib/python3*/dist-packages/rrdtool*[0-9]m-*.so

  rrdtool-dbg.install:
  usr/lib/python3*/dist-packages/rrdtool*[0-9]dm-*.so


After switching to automatic debug symbols with an extra python -dbg package:
  python3-rrdtool.install:
  usr/lib/python3*/dist-packages/rrdtool*[0-9]m-*.so

  python3-rrdtool-dbg.install:
  usr/lib/python3*/dist-packages/rrdtool*[0-9]dm-*.so

(This now generates a python3-rrdtool-dbg-dbgsym package)


But I fail to see how this helps with python 3.8. Are the .so name changed? 
How so?

I tried to look at your upload of twisted, but it looks like you forgot to 
push your changes, and twisted_18.9.0-4.dsc is not in the pool yet.

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

Bug#942630:

[Mario Limonciello]

Can you try to run fwupdmgr manually outside of the service and see if it's
working?
If it isn't, can you please check the journal for fwupd.service to see if
there was a problem with starting it?

-- 
Mario Limonciello
supe...@gmail.com

Bug#942649: ITP: golang-github-rs-cors -- net/http configurable handler to handle CORS requests

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov 
X-Debbugs-CC: debian-de...@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 src:nomad

   Package name: golang-github-rs-cors
Version: 1.7.0
Upstream Author: Olivier Poitrey
License: Expat
URL: https://github.com/rs/cors
Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-rs-cors
Description: net/http configurable handler to handle CORS requests
 CORS is a net/http handler implementing Cross Origin Resource Sharing W3
 specification (http://www.w3.org/TR/cors/) in Golang.


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

Bug#942648: Disable credentials prompting when probing VCS URLs

[Jelmer Vernooij]

Package: lintian-brush
Version: 0.37
Severity: minor

When probing possible upstream VCS URLs, assume they are public and don't
prompt the user for any credentials.

lintian_brush.vcs.probe_url

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 lintian-brush depends on:
ii  devscripts   2.19.7
ii  python3  3.7.5-1
ii  python3-breezy   3.0.1-6
ii  python3-debian   0.1.36
ii  python3-distro-info  0.22
ii  python3-dulwich  0.19.13-1
ii  python3-levenshtein  0.12.0-3+b1
ii  python3-pkginfo  1.4.2-2
ii  python3-ruamel.yaml  0.15.34-1+b1

Versions of packages lintian-brush recommends:
ii  dos2unix   7.4.0-2
ii  gpg2.2.17-3
ii  libdebhelper-perl  12.6.1
ii  lintian2.28.0
ii  python3-asyncpg0.18.3-2
ii  python3-pyinotify  0.9.6-1.2

Versions of packages lintian-brush suggests:
pn  gnome-pkg-tools
ii  postgresql-common  207

-- no debconf information

Bug#942647: celery-batches: Incomplete debian/copyright, etc.

[Chris Lamb]

Source: celery-batches
Version: 0.2-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: ftpmas...@debian.org, deba...@debian.org, rodrilopez@gmail.com

Hi,

I just ACCEPTed celery-batches from NEW but the FTP team noticed docs/
has a different license not mentioned in debian/copyright.

This is in no way exhaustive so please check over the entire package
carefully and address these on your next upload.


Regards,

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

Bug#933109: package-supports-alternative-init-but-no-init.d-script produces too many false positives

[Chris Lamb]

Hi Francesco,

> As I have [previously] said, this Lintian check should try hard to
> be more accurate

Agreed, I just did not find the time/bandwidth to do this until now...

> Please improve this check soon: I would rather avoid having to
> introduce a Lintian override into my package...

I understand the desire to have a 100% clean package but this not only
is unnecessary it hinders Lintian's improvement as it removes some of
the incentive to file or follow-up to bugs.

I would thus highly recommend maintainers do not workaround Lintian
bugs or (fixable) false-positives by adding overrides to their
packages.


Regards,

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

Bug#942369: sysbench: --warmup-time option is not implemented

[JCF Ploemen]

Control: severity -1 minor
Control: tags -1 + confirmed pending

Thanks for your bug report. This and other obsolete options have been
removed from the manpage.

Fixed in 
https://salsa.debian.org/jcfp-guest/sysbench/commit/abba67acc69665cda4115ace6772185347bec776


pgprVcKg61TSS.pgp
Description: OpenPGP digital signature

Bug#942308: Maybe duplicate of #930919

[Maximilian Engelhardt]

Could this be the same problem as described in this bug report:

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

There is also a patch linked that you could try.

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

Bug#942639: fix build with Python3.8 + unusual packaging of the debug extension

[Matthias Klose]

On 19.10.19 13:15, Jean-Michel Vourgère wrote:

Hello Matthias

Thank for your bug report and patch.

Actually, I've been putting the rrdtool*[0-9]dm-*.so file in the general old
school rrdtool-dbg package. I'm still using non automatic debug symbols,
because of that damned file. I'll switch to automatic debug symbols at the
same time. :)

You suggested I use python-rrdtool-dbg, but I suppose you mean python3-
rrdtool-dbg, right?


yes

Bug#942646: libxslt: CVE-2019-18197

[Salvatore Bonaccorso]

Source: libxslt
Version: 1.1.32-2.1
Severity: important
Tags: security upstream
Control: found -1 1.1.32-1
Control: found -1 1.1.32-2.1~deb10u1
Control: found -1 1.1.29-1
Control: found -1 1.1.29-2.1+deb9u1

Hi,

The following vulnerability was published for libxslt.

CVE-2019-18197[0]:
| In xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable
| isn't reset under certain circumstances. If the relevant memory area
| happened to be freed and reused in a certain way, a bounds check could
| fail and memory outside a buffer could be written to, or uninitialized
| data could be disclosed.


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-2019-18197
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18197
[1] https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15746
[2] https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15768
[3] https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15914
[4] 
https://gitlab.gnome.org/GNOME/libxslt/commit/2232473733b7313d67de8836ea3b29eec6e8e285

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#942639: fix build with Python3.8 + unusual packaging of the debug extension

[Jean-Michel Vourgère]

Hello Matthias

Thank for your bug report and patch.

Actually, I've been putting the rrdtool*[0-9]dm-*.so file in the general old 
school rrdtool-dbg package. I'm still using non automatic debug symbols, 
because of that damned file. I'll switch to automatic debug symbols at the 
same time. :)

You suggested I use python-rrdtool-dbg, but I suppose you mean python3-
rrdtool-dbg, right? I am unsure of naming convention, and the archive seems to 
have an ugly mix of names.

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

Bug#942645: owncloud-client: "Server version unsupported" message unhelpful

[Conrad J.C. Hughes (for Debian package stuff)]

Package: owncloud-client
Version: 2.5.1.10973+dfsg-1
Severity: normal

Dear Maintainer,

I've connected to a server but am receiving a message "The server version
9.0.2.2- is unsupported! Proceed at your own risk."

This message is confusing, since it doesn't give any clue as to what the client
version is.  The Debian package version, 2.5.1.10973+dfsg-1, is so wildly at
odds with 9.0.2.2 that there doesn't seem a meaningful comparison.  Is this a
protocol version?  Indeed, Internet discussions of same indicate that there's
no meaningful comparison between the two at all, but it looks as if pre-10
servers are obsolete.

Perhaps the client could indicate what server versions it supports, and suggest
a judgement as to whether it's the client or the server that needs an upgrade?

Best,
Conrad



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

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

Versions of packages owncloud-client depends on:
ii  libc6 2.28-10
ii  libgcc1   1:8.3.0-6
ii  libowncloudsync0  2.5.1.10973+dfsg-1
ii  libqt5core5a  5.11.3+dfsg1-1
ii  libqt5dbus5   5.11.3+dfsg1-1
ii  libqt5gui55.11.3+dfsg1-1
ii  libqt5keychain1   0.9.1-2
ii  libqt5network55.11.3+dfsg1-1
ii  libqt5sql5-sqlite 5.11.3+dfsg1-1
ii  libqt5webkit5 5.212.0~alpha2-21
ii  libqt5widgets55.11.3+dfsg1-1
ii  libqt5xml55.11.3+dfsg1-1
ii  libstdc++68.3.0-6
ii  owncloud-client-l10n  2.5.1.10973+dfsg-1

Versions of packages owncloud-client recommends:
ii  owncloud-client-doc  2.5.1.10973+dfsg-1

owncloud-client suggests no packages.

-- no debconf information