Bug#972340: pyferret FTBFS with more than one supported python3 version

[Stefano Rivera]

I sat down to have a look at this, and struggled to figure out what the
package is actually trying to do in its build.

There's some wacky stuff going on, which isn't actually working, so I
started by trimming that out, and enabling set -e.

> dh_missing: warning: lib/python3.9/libpyferret.so exists in debian/tmp but is 
> not installed to anywhere (related file: 
> "debian/tmp/lib/python3.8/libpyferret.so")

From what I can see, this library is a symlink, created for other
libraries to link to, but not installing under that name, only as a
Python C extension.

With the attached patchset, I can get it to build with 3.8 and 3.9,
which gets us to the same state as unstable, which is totally broken:

$ pyferret3
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pyferret/__init__.py", line 75, in 

from pyferret import libpyferret
ImportError: 
/usr/lib/python3/dist-packages/pyferret/libpyferret.cpython-38-x86_64-linux-gnu.so:
 undefined symbol: load_dsg_mask_ftrset_var_
>>>

Then there's all the shared libraries in
/usr/lib/ferret-vis/external_functions/pylibs that want to link to
libpyferret:

$ ldd /usr/lib/ferret-vis/external_functions/pylibs/subtract.so
linux-vdso.so.1 (0x7ffdd76ad000)
libeatmydata.so => /usr/lib/x86_64-linux-gnu/libeatmydata.so 
(0x7f30e9d3d000)
libpyferret.so => not found
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f30e9d37000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f30e9b72000)
/lib64/ld-linux-x86-64.so.2 (0x7f30e9d4f000)

I don't know what's supposed to use those, but they probably shouldn't
be linking to a library that isn't installed.

If there are plugins like this that need to link to C Python Extensions,
I don't know if it makes any sense to build pyferret for multiple Python
versions. But I don't know enough about the package, to understand
exactly what they are for, and how they're meant to be linked.

So... Some patches attached that get us to the broken status-quo of
unstable, but not sure that that's a useful place to be. I'm certainly
not going to NMU them.

I'd have filed an MR, but the git repo is out of date...

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272
From e6f7f375be676af36ce19c0e2e2057ba55d84094 Mon Sep 17 00:00:00 2001
From: Stefano Rivera 
Date: Fri, 16 Oct 2020 23:01:16 -0700
Subject: [PATCH 1/4] debian/rules: set -e; before any multi-command lines.

---
 debian/changelog | 7 +++
 debian/rules | 2 ++
 2 files changed, 9 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 7c959ea..977e734 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+pyferret (7.6.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: set -e; before any multi-command lines.
+
+ -- Stefano Rivera   Fri, 16 Oct 2020 23:00:38 -0700
+
 pyferret (7.6.3-1) unstable; urgency=medium
 
   * New upstream release
diff --git a/debian/rules b/debian/rules
index 5ba46b2..5c7c0f2 100755
--- a/debian/rules
+++ b/debian/rules
@@ -41,6 +41,7 @@ override_dh_auto_install:
 	# Horrible hack breaks The Debian Way. I'm doing the build in the 'install' phase, as i'm installing into debian/tmp
 	# Doing it any earlier, and dh_prep will remove debian/tmp. 
 	# This means I'm also doing 'test' after the Install, not between during make & install. gack.
+	set -e; \
 	for p in $(PY3) ; do \
 		mkdir -p $(INSTALLDIR)/lib/$$p ; \
 		cp $(CURDIR)/install/lib/$$p/site-packages//pyferret/libpyferret.cpython-$$l-$(ARCH).so \
@@ -57,6 +58,7 @@ override_dh_auto_install:
 	@echo "Now doing bench tests"
 	ln -s debian/pyferret3  $(INSTALLDIR)/lib/$(shell py3versions -d)/pyferret
 	# First build necessary files
+	set -e; \
 	for p in  $(PY3) ; do \
 		sed -e 's%@ARCH@%${ARCH}%' \
 -e 's%@LIBDIR@%${LIBDIR}%' \
-- 
2.28.0

From 626a273af6853f66e5e989df539e53dcd31a3e7f Mon Sep 17 00:00:00 2001
From: Stefano Rivera 
Date: Fri, 16 Oct 2020 23:01:53 -0700
Subject: [PATCH 2/4] debian/rules: Drop cp that wasn't executing, because
 there is no "l" variable.

---
 debian/changelog | 2 ++
 debian/rules | 2 --
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 977e734..79073a0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,8 @@ pyferret (7.6.3-1.1) UNRELEASED; urgency=medium
 
   * Non-maintainer upload.
   * debian/rules: set -e; before any multi-command lines.
+  * debian/rules: Drop cp that wasn't executing, because there is no "l"
+variable.
 
  -- Stefano Rivera   Fri, 16 Oct 2020 23:00:38 -0700
 
diff --git a/debian/rules b/debian/rules
index 5c7c0f2..75b0854 100755
--- a/debian/rules
+++ b/debian/rules
@@ -44,8 +44,6 @@ override_dh_auto_install:
 	set -e; \
 	for p in $(PY3) ; do \
 		mkdir -p $(INSTALLDIR)/lib/$$p 

Bug#972246: numba ftbfs in unstable with python3.9 as supported python3 version

[Stefano Rivera]

Looks like it's going to take a while to get Python 3.9 support in the
numba stack:
https://github.com/numba/numba/issues/6345#issuecomment-706722002

This isn't just a little python library, it's a Python JIT for Python,
so I'd believe that supporting 3.9 is non-trivial.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#972251: python-line-profiler: diff for NMU version 2.1-2.1

[Stefano Rivera]

Control: tags 972251 + patch
Control: tags 972251 + pending

Dear maintainer,

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

Regards,

SR
diff -Nru python-line-profiler-2.1/debian/changelog python-line-profiler-2.1/debian/changelog
--- python-line-profiler-2.1/debian/changelog	2018-11-01 02:25:39.0 -0700
+++ python-line-profiler-2.1/debian/changelog	2020-10-15 23:00:41.0 -0700
@@ -1,3 +1,11 @@
+python-line-profiler (2.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Python 3.9 compatibility, assume gettimeofday() exists and takes 2
+arguments. (Closes: #972251)
+
+ -- Stefano Rivera   Thu, 15 Oct 2020 23:00:41 -0700
+
 python-line-profiler (2.1-2) unstable; urgency=medium
 
   * Team upload
diff -Nru python-line-profiler-2.1/debian/patches/py39-compat.diff python-line-profiler-2.1/debian/patches/py39-compat.diff
--- python-line-profiler-2.1/debian/patches/py39-compat.diff	1969-12-31 16:00:00.0 -0800
+++ python-line-profiler-2.1/debian/patches/py39-compat.diff	2020-10-15 23:00:41.0 -0700
@@ -0,0 +1,32 @@
+Description: Python 3.9 dropped gettimeofday configure checks
+ In bpo-38068, cPython assumes gettimeofday exists and takes two arguments.
+ That's a reasonable assumption that we can repeat.
+Author: Stefano Rivera 
+Forwarded: https://github.com/pyutils/line_profiler/pull/31
+Bug-Debian: https://bugs.debian.org/972251
+
+--- a/timers.c
 b/timers.c
+@@ -32,10 +32,6 @@
+ 
+ #else  /* !MS_WINDOWS */
+ 
+-#ifndef HAVE_GETTIMEOFDAY
+-#error "This module requires gettimeofday() on non-Windows platforms!"
+-#endif
+-
+ #if (defined(PYOS_OS2) && defined(PYCC_GCC))
+ #include 
+ #else
+@@ -48,11 +44,7 @@
+ {
+ struct timeval tv;
+ PY_LONG_LONG ret;
+-#ifdef GETTIMEOFDAY_NO_TZ
+-gettimeofday();
+-#else
+ gettimeofday(, (struct timezone *)NULL);
+-#endif
+ ret = tv.tv_sec;
+ ret = ret * 100 + tv.tv_usec;
+ return ret;
diff -Nru python-line-profiler-2.1/debian/patches/series python-line-profiler-2.1/debian/patches/series
--- python-line-profiler-2.1/debian/patches/series	2018-11-01 02:21:39.0 -0700
+++ python-line-profiler-2.1/debian/patches/series	2020-10-15 22:58:51.0 -0700
@@ -1 +1,2 @@
 py37-compat.diff
+py39-compat.diff

Bug#972319: python-line-profiler: New upstream releases in new GitHub repo

[Stefano Rivera]

Source: python-line-profiler
Severity: normal

The canonical upstream source seems to be
https://github.com/pyutils/line_profiler these days.

You probably want to update your watch file.

3.0.2 is the current latest version.

SR

Bug#972028: python-acora: diff for NMU version 2.2-1.3

[Stefano Rivera]

Control: tags 972028 + patch
Control: tags 972028 + pending

Dear maintainer,

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

Regards,

SR
diff -Nru python-acora-2.2/debian/changelog python-acora-2.2/debian/changelog
--- python-acora-2.2/debian/changelog	2019-12-22 20:03:28.0 -0800
+++ python-acora-2.2/debian/changelog	2020-10-15 22:32:00.0 -0700
@@ -1,3 +1,11 @@
+python-acora (2.2-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Delete generated C before build, and in clean, to ensure regeneration with
+cython. Fixes FTBFS with Python 3.9. (Closes: #972028)
+
+ -- Stefano Rivera   Thu, 15 Oct 2020 22:32:00 -0700
+
 python-acora (2.2-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-acora-2.2/debian/clean python-acora-2.2/debian/clean
--- python-acora-2.2/debian/clean	1969-12-31 16:00:00.0 -0800
+++ python-acora-2.2/debian/clean	2020-10-15 22:29:55.0 -0700
@@ -0,0 +1 @@
+acora/*.c
diff -Nru python-acora-2.2/debian/rules python-acora-2.2/debian/rules
--- python-acora-2.2/debian/rules	2019-12-22 20:03:23.0 -0800
+++ python-acora-2.2/debian/rules	2020-10-15 22:29:46.0 -0700
@@ -1,6 +1,7 @@
 #!/usr/bin/make -f
 
 export PYBUILD_NAME:= acora
+export PYBUILD_BEFORE_BUILD := rm -f $(wildcard acora/*.c)
 export PYBUILD_BEFORE_TEST := cp -a test.py README.rst {build_dir}/
 export PYBUILD_TEST_ARGS   := {interpreter} {build_dir}/test.py
 export PYBUILD_AFTER_TEST  := rm -f {build_dir}/test.py {build_dir}/README.rst

Bug#972207: pymongo: diff for NMU version 3.10.0-2.1

[Stefano Rivera]

Control: tags 972207 + patch
Control: tags 972207 + pending

Dear maintainer,

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

Regards,

SR
diff -Nru pymongo-3.10.0/debian/changelog pymongo-3.10.0/debian/changelog
--- pymongo-3.10.0/debian/changelog	2020-03-28 22:06:09.0 -0700
+++ pymongo-3.10.0/debian/changelog	2020-10-15 21:59:45.0 -0700
@@ -1,3 +1,10 @@
+pymongo (3.10.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix test failure on Python 3.9 (Closes: #972207)
+
+ -- Stefano Rivera   Thu, 15 Oct 2020 21:59:45 -0700
+
 pymongo (3.10.0-2) unstable; urgency=medium
 
   * debian/patches/da778c501761f9c7fa0f2f1538e5d569d67ad044.patch
diff -Nru pymongo-3.10.0/debian/patches/fcb6a8ecbc98fceca138d74fb09b516b172bb4e0.patch pymongo-3.10.0/debian/patches/fcb6a8ecbc98fceca138d74fb09b516b172bb4e0.patch
--- pymongo-3.10.0/debian/patches/fcb6a8ecbc98fceca138d74fb09b516b172bb4e0.patch	1969-12-31 16:00:00.0 -0800
+++ pymongo-3.10.0/debian/patches/fcb6a8ecbc98fceca138d74fb09b516b172bb4e0.patch	2020-10-15 21:58:50.0 -0700
@@ -0,0 +1,37 @@
+From: Shane Harvey 
+Date: Thu, 10 Sep 2020 13:39:34 -0700
+Subject: PYTHON-2262 Test Python 3.9 in Evergreen
+
+Bug-Debian: https://bugs.debian.org/972207
+Bug-Upstream: https://jira.mongodb.org/browse/PYTHON-2262
+Origin: upstream, https://github.com/mongodb/mongo-python-driver/commit/fcb6a8ecbc98fceca138d74fb09b516b172bb4e0
+---
+ setup.py  | 1 +
+ test/test_custom_types.py | 2 +-
+ 2 files changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/setup.py b/setup.py
+index 7c0110f..1ddec32 100755
+--- a/setup.py
 b/setup.py
+@@ -385,6 +385,7 @@ setup(
+ "Programming Language :: Python :: 3.6",
+ "Programming Language :: Python :: 3.7",
+ "Programming Language :: Python :: 3.8",
++"Programming Language :: Python :: 3.9",
+ "Programming Language :: Python :: Implementation :: CPython",
+ "Programming Language :: Python :: Implementation :: PyPy",
+ "Topic :: Database"],
+diff --git a/test/test_custom_types.py b/test/test_custom_types.py
+index ba0bb0c..685a51d 100644
+--- a/test/test_custom_types.py
 b/test/test_custom_types.py
+@@ -255,7 +255,7 @@ class TestBSONFallbackEncoder(unittest.TestCase):
+ 
+ class TestBSONTypeEnDeCodecs(unittest.TestCase):
+ def test_instantiation(self):
+-msg = "Can't instantiate abstract class .* with abstract methods .*"
++msg = "Can't instantiate abstract class"
+ def run_test(base, attrs, fail):
+ codec = type('testcodec', (base,), attrs)
+ if fail:
diff -Nru pymongo-3.10.0/debian/patches/series pymongo-3.10.0/debian/patches/series
--- pymongo-3.10.0/debian/patches/series	2020-03-28 22:06:09.0 -0700
+++ pymongo-3.10.0/debian/patches/series	2020-10-15 21:58:50.0 -0700
@@ -1 +1,2 @@
 da778c501761f9c7fa0f2f1538e5d569d67ad044.patch
+fcb6a8ecbc98fceca138d74fb09b516b172bb4e0.patch

Bug#972214: python3: Some dependencies are missing during the upgrade

[Stefano Callegari]

Package: python3
Version: 3.8.6-1
Severity: important

Dear Maintainer,

with the latest update the package did not install with the following
errors

...
Exception: cannot get content of devhelp
error running python rtupdate hook devhelp
...
Exception: cannot get content of libglib2.0-dev-bin
error running python rtupdate hook libglib2.0-dev-bin
dpkg: errore nell'elaborare il pacchetto python3 (--configure):
 il sottoprocesso installato pacchetto python3 script post-installation ha
restituito lo stato di errore 4
Si sono verificati degli errori nell'elaborazione:
 python3

Only when I installed the 2 reported packages was I able to complete the
installation.

Thanks

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

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

Versions of packages python3 depends on:
ii  libpython3-stdlib  3.8.6-1
ii  python3-minimal3.8.6-1
ii  python3.8  3.8.6-1

python3 recommends no packages.

Versions of packages python3 suggests:
pn  python3-doc   
ii  python3-tk3.8.6-1
pn  python3-venv  

-- no debconf information

Bug#971910: fix ftbfs with python3.9

[Stefano Rivera]

Control: tag -1 - patch
Control: forwarded -1 https://foss.heptapod.net/pypy/cffi/-/issues/475

> fix ftbfs with python3.9, patch at
> https://launchpadlibrarian.net/501211180/python-cffi_1.14.2-1_1.14.3-1ubuntu0.1.diff.gz

That patch just ignores the test results, I will not be applying that :)

I have already forwarded this issue upstream.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#970904: arc diff emits a lot of warnings about implode() PHP function

[Stefano Zacchiroli]

Package: arcanist
Version: 0~git20190207-1
Severity: normal
File: /usr/bin/arc

Sample output:

  $ arc diff
  [2020-09-25 07:38:58] ERROR 8192: implode(): Passing glue string after array 
is deprecated. Swap the parameters at 
[/usr/share/libphutil/src/utils/utils.php:1572]
  arcanist(), phutil()
#0 implode(array, string) called at [/src/utils/utils.php:1572]
#1 phutil_build_http_querystring(array) called at 
[/src/future/http/HTTPSFuture.php:526]
#2 HTTPSFuture::formatRequestDataForCURL() called at 
[/src/future/http/HTTPSFuture.php:247]
#3 HTTPSFuture::isReady() called at [/src/future/Future.php:37]
#4 Future::resolve(NULL) called at [/src/future/FutureProxy.php:34]
#5 FutureProxy::resolve() called at 
[/src/conduit/ConduitClient.php:64]
#6 ConduitClient::callMethodSynchronous(string, array) called at 
[/src/workflow/ArcanistWorkflow.php:332]
#7 ArcanistWorkflow::authenticateConduit() called at 
[/scripts/arcanist.php:356]
  [2020-09-25 07:38:58] ERROR 8192: implode(): Passing glue string after array 
is deprecated. Swap the parameters at 
[/usr/share/libphutil/src/utils/utils.php:1572]
  arcanist(), phutil()
#0 implode(array, string) called at [/src/utils/utils.php:1572]
#1 phutil_build_http_querystring(array) called at 
[/src/future/http/HTTPSFuture.php:526]
#2 HTTPSFuture::formatRequestDataForCURL() called at 
[/src/future/http/HTTPSFuture.php:247]
#3 HTTPSFuture::isReady() called at [/src/future/Future.php:37]
#4 Future::resolve(NULL) called at [/src/future/FutureProxy.php:34]
#5 FutureProxy::resolve() called at 
[/src/conduit/ConduitClient.php:64]
#6 ConduitClient::callMethodSynchronous(string, array) called at 
[/src/workflow/ArcanistDiffWorkflow.php:1597]
#7 ArcanistDiffWorkflow::getCommitMessageFromUser() called at 
[/src/workflow/ArcanistDiffWorkflow.php:1501]
#8 ArcanistDiffWorkflow::buildCommitMessage() called at 
[/src/workflow/ArcanistDiffWorkflow.php:469]
#9 ArcanistDiffWorkflow::run() called at 
[/scripts/arcanist.php:394]
  [2020-09-25 07:39:04] ERROR 8192: implode(): Passing glue string after array 
is deprecated. Swap the parameters at 
[/usr/share/libphutil/src/utils/utils.php:1572]
  arcanist(), phutil()
#0 implode(array, string) called at [/src/utils/utils.php:1572]
#1 phutil_build_http_querystring(array) called at 
[/src/future/http/HTTPSFuture.php:526]
#2 HTTPSFuture::formatRequestDataForCURL() called at 
[/src/future/http/HTTPSFuture.php:247]
#3 HTTPSFuture::isReady() called at [/src/future/Future.php:37]
#4 Future::resolve(NULL) called at [/src/future/FutureProxy.php:34]
#5 FutureProxy::resolve() called at 
[/src/conduit/ConduitClient.php:64]
#6 ConduitClient::callMethodSynchronous(string, array) called at 
[/src/differential/ArcanistDifferentialCommitMessage.php:48]
#7 ArcanistDifferentialCommitMessage::pullDataFromConduit(ConduitClient) 
called at [/src/workflow/ArcanistDiffWorkflow.php:1695]
#8 ArcanistDiffWorkflow::getCommitMessageFromUser() called at 
[/src/workflow/ArcanistDiffWorkflow.php:1501]
#9 ArcanistDiffWorkflow::buildCommitMessage() called at 
[/src/workflow/ArcanistDiffWorkflow.php:469]
#10 ArcanistDiffWorkflow::run() called at 
[/scripts/arcanist.php:394]

as this is shown in the terminal during interactive use of arc diff, it makes
using the tool quite painful at the moment.

Cheers

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

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

Versions of packages arcanist depends on:
ii  libphutil   0~git20190207-1
ii  php-cli 2:7.4+76
ii  php-curl2:7.4+76
ii  php-xml 2:7.4+76
ii  php7.4-cli [php-cli]7.4.9-2
ii  php7.4-curl [php-curl]  7.4.9-2
ii  php7.4-xml [php-xml]7.4.9-2

arcanist recommends no packages.

Versions of packages arcanist suggests:
pn  python  

-- no debconf information

Bug#893745: python-cffi: FTBFS on ia64: several test failures

[Stefano Rivera]

Hi Aaron (2018.03.21_16:02:21_-0700)
> testing/cffi0/test_ownlib.py:296: AssertionError
> ___ test_no_unknown_exported_symbols 
> ___
> 
> def test_no_unknown_exported_symbols():
> if not hasattr(_cffi_backend, '__file__'):
> py.test.skip("_cffi_backend module is built-in")
> if not sys.platform.startswith('linux'):
> py.test.skip("linux-only")
> g = os.popen("objdump -T '%s'" % _cffi_backend.__file__, 'r')
> for line in g:
> if not line.startswith('0'):
> continue
> if '*UND*' in line:
> continue
> name = line.split()[-1]
> if name.startswith('_') or name.startswith('.'):
> continue
> if name not in ('init_cffi_backend', 'PyInit__cffi_backend'):
> >   raise Exception("Unexpected exported name %r" % (name,))
> E   Exception: Unexpected exported name 'ctypedescr_clear'

Looks like this is the only remaining failure.

So, the rest were presumably libffi bugs.

Not sure exactly what's going on there. I can't seem to access the
atlantis porterbox ATM.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#969576: nextcloud-desktop: Main window not visible/constructable

[Stefano Zacchiroli]

On Wed, Sep 09, 2020 at 07:24:04PM +0200, Paul van Tilburg wrote:
> I have to reaffirm that I used an iterative approach to install each of
> these to get rid of all warnings and have the main interface appear.
> I'm afraid that all dependencies listed  above seem necessary, maybe
> you had the others for other reasons already?

Yeah, it is entirely possible. So please test what is actually needed
(e.g., in a fresh debian chroot) rather than relying on my very narrow
data point.

Cheers
-- 
Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

Bug#969576: nextcloud-desktop: Main window not visible/constructable

[Stefano Zacchiroli]

severity serious
thanks

On Sat, Sep 05, 2020 at 11:59:46AM +0200, Paul van Tilburg wrote:
> The upgrade to 3.0 of the Nextcloud client led to the main window not
> being visible anymore. It seems that the QT QML modules are missing to
> make it work.  Consider the warnings in the logs:

I can confirm this. I'm raising the severity because the desktop UI is
de facto non usable due to this.

> After installing the following packages,  I can see the main window again
> (although it still disappears on me sometimes):
> 
> * qml-module-qtquick-layouts
> * qml-module-qtquick-controls2
> * qml-module-qtgraphicaleffects
> * qml-module-qtqml-models2
> * qml-module-qtqml

Thanks for this. After "apt install"-ing the above packages the issue
was fixed for me too. For what is worth, the packages that were
*actually* missing on my system prior to the installation were just:

  qml-module-qtquick-controls2
  qml-module-qtquick-templates2

so I'd expect that adding either (if they depend on one another) or both
to the package dependencies would fix this issue.

Cheers
-- 
Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

Bug#968644: ITP: python-authlib -- Python library for OAuth and OpenID Connect servers

[Stefano Rivera]

Package: wnpp
Severity: wishlist
Owner: Stefano Rivera 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-authlib
  Version : 0.14.3
  Upstream Author : Hsiaoming Yang 
* URL : https://authlib.org/
* License : BSD-3
  Programming Lang: Python
  Description : Python library for OAuth and OpenID Connect servers

The ultimate Python library in building OAuth and OpenID Connect servers. It
is designed from low level specifications implementations to high level
frameworks integrations, to meet the needs of everyone.


There are several Python libraries supporting bits of OAuth/OpenID, etc.
This is one of the most complete I've seen, and seems well maintained
(if somewhat new).

Matrix Synapse uses it for OIDC.

Intend to package it under the Debian Python Modules Team.

Bug#947351: cloud-init 20.2-2~deb10u1 flagged for acceptance

[Stefano Rivera]

Hi Adam (2020.07.09_13:19:23_-0700)
> The upload referenced by this bug report has been flagged for acceptance into 
> the proposed-updates queue for Debian buster.

FWIW, this update included a change that broke the Debian images for at
least one hosting provider.

We noticed when provisioning a Debian 10.5 image on Hetzner Cloud, that
no Ethernet interfaces where being configured.

Hetzner had "include /etc/network/interfaces.d/*.cfg" in their
/etc/network/interfaces.

Before 19.2 cloud-init wrote /etc/network/interfaces.d/50-cloud-init.cfg
After 19.2 cloud-init wrote /etc/network/interfaces.d/50-cloud-init
Relevant upstream commit: 
https://github.com/canonical/cloud-init/commit/a6faf3acef02bd8cd4d46ac9efeebf24b3f21d81

This doesn't break Debian installs that had the default
/etc/network/interfaces. But if it caused a regression for one provider,
it probably caused regressions for others too.

Not sure what the right approach in Debian is, here. Whether there
should be a new bug filed against cloud-init in stable?

We filed Hetzner Ticket#2020081703000394 with these details so they
could fix their images.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#963750: RM: chef -- ROM; trademark issues

[Stefano Rivera]

Hi Sean (2020.07.11_14:53:31_-0700)
> > However, Chef Inc. decided that Chef should no longer be free
> > software/open source. I no longer intend to use or maintain Chef, and
> > would like it to be removed from Debian.
> 
> I'm a bit confused here.  On the one hand you say that there's a
> copyright issue, but reading the Ubuntu bug it seems that Ubuntu's
> src:chef in fact contains cinc.  I take it Debian's doesn't?  In which
> case the copyright issue would seem not to be a relevant reason for
> removal?

Chef is in sync between Debian and Ubuntu. The current source package
contains cinc [0], but the packages are still contain the name chef.

That is the core of the trademark issue Chef Inc has with Debian [1].

[0]: 
https://tracker.debian.org/media/packages/c/chef/copyright-15.8.25.3.gcf41df6a2-6
[1]: https://bugs.debian.org/959981#5

> On the other hand you say you think that we should remove the Chef
> package because there are not going to be future upstream releases which
> are free software.  Could you provide me a reference, please?  All I can
> find online is that there is a new requirement to perform some renaming
> in the contents of the package, not that new releases will be
> DFSG-nonfree.

I think your analysis is correct. The source is Apache-2.0 licensed, but
with a renaming requirement. There is a collaborative effort to maintain
a renamed source, cinc, which we've been shipping, but we haven't
followed through on a complete renaming.

This is an RoM request, the maintainers have lost interest in working
with an upstream that imposes rules like this.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#965023: transition: re2

[Stefano Rivera]

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

Public ABI Breakage:
An entry was inserted into an enum, rather than appended to the end.

Public API Breakage:
None

Reverse Dependencies:
* dnsdist seems to have had uninstallable Build-Dependencies, in my testing
  yesterday, but built fine on the 5th.
* Everything else builds without error.

Ben file:

title = "re2";
is_affected = .depends ~ "libre2-7" | .depends ~ "libre2-8";
is_good = .depends ~ "libre2-8";
is_bad = .depends ~ "libre2-7";

https://release.debian.org/transitions/html/auto-re2.html LGTM

SR

Bug#960564: closed by Debian FTP Masters (reply to SZ Lin (林上智) ) (Bug#960564: fixed in usbauth 1.0.2-2)

[Stefano Rivera]

Control: reopen 960564

>* d/tests/:
>  - Add condition check to start/stop dbus only if it is not started.
>(Closes: #960564)

That doesn't resolve the issue I described:

> On Ubuntu, the "service dbus start" doesn't work.
> 
> | # service dbus start
> | Failed to start dbus.service: Operation refused, unit dbus.service may be 
> requested by dependency only (it is configured to refuse manual start/stop).
> | See system logs and 'systemctl status dbus.service' for details.
> | 
> | # cat /lib/systemd/system/dbus.service
> | [Unit]
> | Description=D-Bus System Message Bus
> | Documentation=man:dbus-daemon(1)
> | Requires=dbus.socket
> | # we don't properly stop D-Bus (see ExecStop=), thus disallow restart
> | RefuseManualStart=yes
> | 
> | [Service]
> | ExecStart=/usr/bin/dbus-daemon --system --address=systemd: --nofork 
> --nopidfile --systemd-activation --syslog-only
> | ExecReload=/usr/bin/dbus-send --print-reply --system --type=method_call 
> --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
> | ExecStop=/bin/true
> | KillMode=none
> | OOMScoreAdjust=-900
> 
> What you can safely do is systemctl start dbus.socket, which will ensure
> that DBus starts, and is running.
> 
> Stopping DBus is almost never a good idea, so the test probably
> shouldn't do that. If it did, it should declare the isolation-container
> restriction.

This is still true after -2:

"service dbus start" won't work on Ubuntu. That's not necessarily a
bug that you need to care about as a Debian maintainer. But if you want
your package available in Ubuntu, it helps to write autopkgtests that
work there, or Ubuntu will have to fork your package.

Failures: http://autopkgtest.ubuntu.com/packages/u/usbauth/focal/amd64

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#964334: segfault repeatedly

[Stefano Zacchiroli]

I've seen this bug has been marked as "more info" (with no comment), but
I'm not clear on which additional info are needed and how I can provide
them.  Advice on how I can help is welcome :-)

Bug#964334: segfault repeatedly

[Stefano Zacchiroli]

Package: chromium
Version: 83.0.4103.116-2
Severity: grave

I've upgraded chromium to the current version in testing, and it segfaults
repeatedly (and very "reliably"! :-)) after usually ~1 minute of runtime, even
when not used in foreground, with a stack trace like this one:

-

$ chromium 

(chromium:1480721): Gtk-WARNING **: 21:03:45.963: Theme parsing error: 
gtk.css:6:20: The 'gtk-key-bindings' property has been renamed to 
'-gtk-key-bindings'
[1480760:1480760:0705/210346.245467:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[1480764:1480779:0705/210348.465499:ERROR:nss_util.cc(283)] After loading Root 
Certs, loaded==false: NSS error code: -8018
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: profile 'Photoshop ICC profile': 'RGB ': RGB color space 
not permitted on grayscale PNG
libpng warning: iCCP: profile 'Photoshop ICC profile': 'RGB ': RGB color space 
not permitted on grayscale PNG
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Received signal 11 SEGV_MAPERR 7f01744946c7
#0 0x557d36628c69 (/usr/lib/chromium/chromium+0x52b3c68)
#1 0x557d36587ef3 (/usr/lib/chromium/chromium+0x5212ef2)
#2 0x557d366287f1 (/usr/lib/chromium/chromium+0x52b37f0)
#3 0x7f1a95d8d110 (/usr/lib/x86_64-linux-gnu/libpthread-2.30.so+0x1410f)
#4 0x7f1a90e78d3c (/usr/lib/x86_64-linux-gnu/libc-2.30.so+0x85d3b)
#5 0x7f1a90e7af33 (/usr/lib/x86_64-linux-gnu/libc-2.30.so+0x87f32)
#6 0x7f1a90e7cbf9 __libc_malloc
#7 0x557d366409be operator new()
#8 0x7f1a91103a2c std::__cxx11::basic_string<>::reserve()
#9 0x7f1a910f9498 std::__cxx11::basic_stringbuf<>::overflow()
#10 0x7f1a9110204a std::basic_streambuf<>::xsputn()
#11 0x7f1a910f4714 std::__ostream_insert<>()
#12 0x557d36628d39 (/usr/lib/chromium/chromium+0x52b3d38)
#13 0x557d36629054 (/usr/lib/chromium/chromium+0x52b4053)
#14 0x557d3659a412 (/usr/lib/chromium/chromium+0x5225411)
#15 0x557d3659c548 (/usr/lib/chromium/chromium+0x5227547)
#16 0x557d34ce212a (/usr/lib/chromium/chromium+0x396d129)
#17 0x557d34ce217e (/usr/lib/chromium/chromium+0x396d17d)
#18 0x557d34337387 (/usr/lib/chromium/chromium+0x2fc2386)
#19 0x557d34c9b3d9 (/usr/lib/chromium/chromium+0x39263d8)
#20 0x557d34c9b61e (/usr/lib/chromium/chromium+0x392661d)
#21 0x557d34ce5967 (/usr/lib/chromium/chromium+0x3970966)
#22 0x557d34d114c7 (/usr/lib/chromium/chromium+0x399c4c6)
#23 0x557d34d1177e (/usr/lib/chromium/chromium+0x399c77d)
#24 0x557d34ce213f (/usr/lib/chromium/chromium+0x396d13e)
#25 0x557d34ce217e (/usr/lib/chromium/chromium+0x396d17d)
#26 0x557d34337387 (/usr/lib/chromium/chromium+0x2fc2386)
#27 0x557d345fa7a3 (/usr/lib/chromium/chromium+0x32857a2)
#28 0x557d349690bc (/usr/lib/chromium/chromium+0x35f40bb)
#29 0x557d3675a45f (/usr/lib/chromium/chromium+0x53e545e)
#30 0x557d36760a24 (/usr/lib/chromium/chromium+0x53eba23)
#31 0x557d3675eb62 (/usr/lib/chromium/chromium+0x53e9b61)
#32 0x557d3675d82d (/usr/lib/chromium/chromium+0x53e882c)
#33 0x557d36756213 (/usr/lib/chromium/chromium+0x53e1212)
#34 0x557d36771abb (/usr/lib/chromium/chromium+0x53fcaba)
#35 0x557d36771de0 (/usr/lib/chromium/chromium+0x53fcddf)
#36 0x557d36771370 (/usr/lib/chromium/chromium+0x53fc36f)
#37 0x557d345e3c46 (/usr/lib/chromium/chromium+0x326ec45)
#38 0x557d345e376c (/usr/lib/chromium/chromium+0x326e76b)
#39 0x557d345dfeed (/usr/lib/chromium/chromium+0x326aeec)
#40 0x557d345d674b (/usr/lib/chromium/chromium+0x326174a)
#41 0x557d345c9044 (/usr/lib/chromium/chromium+0x3254043)
#42 0x557d345c8d75 (/usr/lib/chromium/chromium+0x3253d74)
#43 0x557d345e7426 (/usr/lib/chromium/chromium+0x3272425)
#44 0x557d366460e0 (/usr/lib/chromium/chromium+0x52d10df)
#45 0x7f1a94b42b0f (/usr/lib/x86_64-linux-gnu/libevent-2.1.so.7.0.0+0x23b0e)
#46 0x7f1a94b4324f event_base_loop
#47 0x557d3664638e (/usr/lib/chromium/chromium+0x52d138d)
#48 0x557d365e65d5 (/usr/lib/chromium/chromium+0x52715d4)
#49 0x557d365be670 (/usr/lib/chromium/chromium+0x524966f)
#50 0x557d349043b3 (/usr/lib/chromium/chromium+0x358f3b2)
#51 0x557d365fc2a9 (/usr/lib/chromium/chromium+0x52872a8)
#52 0x557d36638c9e (/usr/lib/chromium/chromium+0x52c3c9d)
#53 0x7f1a95d81f27 start_thread
#54 0x7f1a90ef031f clone
  r8: 0077  r9: 0050 r10: 0004 r11: 
007c
 r12: 7f1a7420 r13: 7f1a7430 r14: 7f1a74736850 r15: 
0020
  di: 0021  si: 0004  bp: 0020  bx: 
7f01744946bf
  dx: 7f1a7480  ax: 7f1a742d4d90  cx: 7f01744946bf  sp: 
7f1a826d3440
  ip: 7f1a90e78d3c efl: 00010202 cgf: 002b0033 erf: 
0004
 trp: 000e msk:  cr2: 7f01744946c7
[end of stack trace]
Calling _exit(1). Core file will not be generated.

-

Thanks a lot for maintaining chromium in Debian,
Hope this helps


-- System Information:
Debian 

Bug#962188: cpio: Wrong CRC with new ASCII format when file > 2GB

[Stefano Babic]

Package: cpio
Version: 2.13+dfsg-2
Severity: normal

Dear Maintainer,

CRC is wrongly computed if filesize > 2GB and when new ASCII format is chosen 
due to wrong signedness.
The attached patch fixes this.

To check this, just create a file > 2GB and run CPIO with the options "cpio -ov 
-H crc"

Checksum for large files are set to 0 due to the bug. cpio itself does not 
check them when unpackiung
(a different bug ?), but programs relying on the format and on the CRC comply 
with error.

Bug is present in all cpio releases.

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

Kernel: Linux 5.4.0-33-generic (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cpio depends on:
ii  libc6  2.31-0ubuntu9

cpio recommends no packages.

Versions of packages cpio suggests:
pn  libarchive1  

-- no debconf information
>From 77ff5f1be394eb2c786df561ff37dde7f982ec76 Mon Sep 17 00:00:00 2001
From: Stefano Babic 
Date: Fri, 28 Jul 2017 13:20:52 +0200
Subject: [PATCH] Wrong CRC with ASCII CRC for large files

Due to signedness, the checksum is not computed when filesize is bigger
a 2GB.

Signed-off-by: Stefano Babic 
---
 src/copyout.c | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/copyout.c b/src/copyout.c
index 1f0987a..727aeca 100644
--- a/src/copyout.c
+++ b/src/copyout.c
@@ -34,13 +34,13 @@
compute and return a checksum for them.  */
 
 static uint32_t
-read_for_checksum (int in_file_des, int file_size, char *file_name)
+read_for_checksum (int in_file_des, unsigned int file_size, char *file_name)
 {
   uint32_t crc;
   char buf[BUFSIZ];
-  int bytes_left;
-  int bytes_read;
-  int i;
+  unsigned int bytes_left;
+  unsigned int bytes_read;
+  unsigned int i;
 
   crc = 0;
 
-- 
2.7.4

Bug#962051: segfault when locking screen

[Stefano Zacchiroli]

forcemerge 959883 962051
thanks

On Tue, Jun 02, 2020 at 09:54:15PM +0100, Simon McVittie wrote:
> On Tue, 02 Jun 2020 at 17:22:54 +0200, Stefano Zacchiroli wrote:
> > heya, since yesterday under Debian/testing gnome-shell crashes (and then
> > restarts) when trying to lock screen.
> 
> This seems like #959883. Please try disabling any extensions you have
> enabled, and/or upgrading to the snapshot in experimental.

Yup, that was it! I guess I missed it because I've only looked at open
bugs, my apologies. Upgrading to the experimental snapshot fixed the
issue for me too.

Merging/closing.

Thanks for your super quick solution!
Cheers
-- 
Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

Bug#962051: segfault when locking screen

[Stefano Zacchiroli]

Package: gnome-shell
Version: 3.36.2-1
Severity: important

heya, since yesterday under Debian/testing gnome-shell crashes (and then
restarts) when trying to lock screen. Here's the diagnostic I can find under
journalctl:

  giu 02 17:17:32 noziere kernel: gnome-shell[106365]: segfault at 0 ip 
7fb2305fd467 sp 7ffd001db960 error 4 in libst-1.0.so[7fb2305de000+4a000]
  giu 02 17:17:32 noziere kernel: Code: 00 00 00 48 83 c3 01 41 39 9f 30 01 00 
00 0f 8e 2f 01 00 00 49 8b 87 28 01 00 00 48 8d 35 d6 f5 02 00 48 8b 2c d8 48 
8b 45 00 <48> 8b 00 4c 8b 20 4c 89 e7 e8 3b 28 fe ff 85 c0 74 c7 41 80 7c 24
  giu 02 17:17:32 noziere polkitd(authority=local)[718]: Unregistered 
Authentication Agent for unix-session:2 (system bus name :1.168, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
  giu 02 17:17:32 noziere gsd-media-keys[2202]: Couldn't lock screen: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  giu 02 17:17:32 noziere systemd[1768]: gnome-shell-x11.service: Main process 
exited, code=killed, status=11/SEGV
  giu 02 17:17:32 noziere systemd[1768]: gnome-shell-x11.service: Failed with 
result 'signal'.
  giu 02 17:17:32 noziere systemd[1768]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 11.
  giu 02 17:17:32 noziere systemd[1768]: Stopped target GNOME X11 Session 
(session: gnome).
  giu 02 17:17:32 noziere systemd[1768]: Stopping GNOME X11 Session (session: 
gnome).
  giu 02 17:17:32 noziere systemd[1768]: Stopped target GNOME X11 Session.
  giu 02 17:17:32 noziere systemd[1768]: Stopping GNOME X11 Session.
  giu 02 17:17:32 noziere systemd[1768]: Stopped target GNOME Shell on X11.
  giu 02 17:17:32 noziere systemd[1768]: Stopping GNOME Shell on X11.
  giu 02 17:17:32 noziere systemd[1768]: Stopped GNOME Shell on X11.
  giu 02 17:17:32 noziere systemd[1768]: Starting GNOME Shell on X11...

It happens systematically, both when trying to lock screen on demand
(Ctrl+Alt+L) and when the laptop suspends (meaning that when it wakes up the
desktop is happily unlocked... this might make this bug warrant a security +
severity bump: I'll let this up to the maintainers to decide).

As shown above the shell immediately restarts afterwards, without causing any
session disruption/logout/etc.

Thanks for maintaining GNOME in Debian!

Cheers

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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  evolution-data-server3.36.2-1
ii  gir1.2-accountsservice-1.0   0.6.55-2
ii  gir1.2-atspi-2.0 2.36.0-2
ii  gir1.2-freedesktop   1.64.1-1
ii  gir1.2-gcr-3 3.36.0-2
ii  gir1.2-gdesktopenums-3.0 3.36.1-1
ii  gir1.2-gdm-1.0   3.34.1-3
ii  gir1.2-geoclue-2.0   2.5.6-1
ii  gir1.2-glib-2.0  1.64.1-1
ii  gir1.2-gnomebluetooth-1.03.34.1-1
ii  gir1.2-gnomedesktop-3.0  3.36.2-1
ii  gir1.2-gtk-3.0   3.24.20-1
ii  gir1.2-gweather-3.0  3.36.0-1
ii  gir1.2-ibus-1.0  1.5.22-5
ii  gir1.2-mutter-6  3.36.2-3
ii  gir1.2-nm-1.01.24.0-1
ii  gir1.2-nma-1.0   1.8.28-2
ii  gir1.2-pango-1.0 1.44.7-4
ii  gir1.2-polkit-1.00.105-26
ii  gir1.2-rsvg-2.0  2.48.4+dfsg-1
ii  gir1.2-soup-2.4  2.70.0-1
ii  gir1.2-upowerglib-1.00.99.11-2
ii  gjs  1.64.2-1
ii  gnome-backgrounds3.36.0-1
ii  gnome-settings-daemon3.36.1-1
ii  gnome-shell-common   3.36.2-1
ii  gsettings-desktop-schemas3.36.1-1
ii  libatk-bridge2.0-0   2.34.1-3
ii  libatk1.0-0  2.36.0-2
ii  libc62.30-8
ii  libcairo21.16.0-4
ii  libecal-2.0-13.36.2-1
ii  libedataserver-1.2-243.36.2-1
ii  libgcr-base-3-1  3.36.0-2
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-4
ii  

Bug#961638: proposal: stocat - probabilistic cat

[Stefano Zacchiroli]

Package: moreutils
Version: 0.63-1+b1
Severity: wishlist
Tags: patch upstream

I'm hereby proposing the inclusion of the attached "stocat" utility to
moreutils. It's like cat, but output lines with a given probability, defaulting
to 10%. It's very useful for random sampling (and *much* more efficient at that
than using "shuf" which is unwieldy on very large inputs) and, while it can be
implemented instead with awk/perl oneliners, those oneliners aren't very
mnemonic and are error prone.

If desired, it could be extended by adding a reservoir sampling option, to
guarantee a selection of exactly K items.

Thanks a lot for moreutils!

Cheers

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

Kernel: Linux 5.6.0-1-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:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages moreutils depends on:
ii  libc6  2.30-8
ii  libipc-run-perl20200505.0-1
ii  libtime-duration-perl  1.21-1
ii  libtimedate-perl   2.3200-1
ii  perl   5.30.2-1

moreutils recommends no packages.

moreutils suggests no packages.

-- no debconf information
#!/usr/bin/perl

=head1 NAME

stocat - stochastic cat, selecting lines with uniform probability


=head1 SYNOPSIS

=over

=item B [B<-p>|B<--probability> PROBABILITY] [I|B<->]...

=back


=head1 DESCRIPTION

Concatenate FILE(s) to standard output, but printing each input line to output
only with a given probability, defaulting to 0.1 (i.e., 10%).

With no FILE or when FILE is B<->, read standard input.


=head1 OPTIONS

=over 4

=item -p, --probability

Output lines with the given probability, specified as a number between 0 (0%
probability) and 1 (100% probability). Default: 0.1 (i.e., 10% probability).

=back


=head1 SEE ALSO

L


=head1 AUTHOR

Copyright 2020 by Stefano Zacchiroli 

Licensed under the GNU GPL.

=cut

use Getopt::Long;

sub die_usage() {
die "Usage: $0 [--probability|-p PROBABILITY] [file|-]\n";
}

my $probability = 0.1;
if (! GetOptions("probability|p=f" => \$probability)) {
die_usage();
}
if ($probability < 0 || $probability > 1) {
die_usage();
}

while (<>) {
print $_ if rand() <= $probability;
}

Bug#961188: src:postgis: autopkgtests fail on 32bit ARM, due to missing sfcgal

[Stefano Rivera]

Package: src:postgis
Version: 3.0.1+dfsg-4
Severity: normal
Tags: patch

The libsfcgal-dev Build-Dep is arch-specific, but the autopkgtests don't
avoid exercising this area, leading to autopkgtest failures like this on
armhf:

> CREATE EXTENSION postgis
> CREATE EXTENSION
> CREATE EXTENSION postgis_raster
> CREATE EXTENSION
> CREATE EXTENSION postgis_sfcgal
> ERROR:  could not find function "postgis_sfcgal_version" in file 
> "/usr/lib/postgresql/12/lib/postgis-3.so"
> *** /tmp/pg_virtualenv.cMSs63/log/postgresql-12-regress.log (last 100 lines) 
> ***
...
> autopkgtest [04:16:30]:  summary
> test-extension-creation FAIL non-zero exit status 1
> regress  FAIL non-zero exit status 2

Full autopkgtest log attached.

Patch attached.

SR
diff -Nru postgis-3.0.1+dfsg/debian/tests/regress postgis-3.0.1+dfsg/debian/tests/regress
--- postgis-3.0.1+dfsg/debian/tests/regress	2020-04-17 11:30:49.0 -0700
+++ postgis-3.0.1+dfsg/debian/tests/regress	2020-05-20 16:02:36.0 -0700
@@ -34,6 +34,8 @@
   pg_virtualenv -v $v <<-EOF
 	set -eux
 	make -C regress/core -f Makefile.in check PERL=perl RUNTESTFLAGS="--extension --verbose" POSTGIS_GEOS_VERSION=$POSTGIS_GEOS_VERSION
-	make -C regress/sfcgal -f Makefile.in check PERL=perl RUNTESTFLAGS="--extension --verbose" HAVE_SFCGAL=yes
+	if [ "$ARCH" != "armhf" -a "$ARCH" != "armel" ]; then
+		make -C regress/sfcgal -f Makefile.in check PERL=perl RUNTESTFLAGS="--extension --verbose" HAVE_SFCGAL=yes
+	fi
 	EOF
 done
diff -Nru postgis-3.0.1+dfsg/debian/tests/test-extension-creation postgis-3.0.1+dfsg/debian/tests/test-extension-creation
--- postgis-3.0.1+dfsg/debian/tests/test-extension-creation	2020-04-17 11:30:49.0 -0700
+++ postgis-3.0.1+dfsg/debian/tests/test-extension-creation	2020-05-20 16:08:18.0 -0700
@@ -5,9 +5,13 @@
 for v in $(pg_buildext supported-versions); do
 	pg_virtualenv -v $v sh -e <<-'EOF'
 	# test extension (fuzzystrmatch is part of postgresql-contrib and is needed by postgis_tiger_geocoder)
-	for ext in postgis postgis_raster postgis_sfcgal fuzzystrmatch postgis_tiger_geocoder postgis_topology address_standardizer address_standardizer_data_us; do
+	for ext in postgis postgis_raster fuzzystrmatch postgis_tiger_geocoder postgis_topology address_standardizer address_standardizer_data_us; do
 		psql -eXc "CREATE EXTENSION $ext"
 	done
+	ARCH="$(dpkg-architecture -qDEB_BUILD_ARCH)"
+	if [ "$ARCH" != "armhf" -a "$ARCH" != "armel" ]; then
+		psql -eXc "CREATE EXTENSION postgis_sfcgal"
+	fi
 	EOF
 done
 
autopkgtest [04:11:01]: version 5.11ubuntu1
autopkgtest [04:11:01]: host ip-172-18-1-80; command line: /usr/bin/autopkgtest 
-o adt-sid -BU postgis -- schroot unstable-armhf-sbuild
autopkgtest [04:11:01]:  test bed setup
Hit:1 http://deb.debian.org/debian unstable InRelease
Get:2 http://deb.debian.org/debian unstable/main Translation-en [6185 kB]
Fetched 6185 kB in 3s (2102 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
autopkgtest [04:11:07]: testbed dpkg architecture: armhf
autopkgtest [04:11:07]: testbed running kernel: Linux 5.4.0-1009-aws #9-Ubuntu 
SMP Sun Apr 12 19:42:55 UTC 2020
autopkgtest [04:11:07]:  apt-source postgis
Get:1 http://deb.debian.org/debian unstable/main postgis 3.0.1+dfsg-4 (dsc) 
[2945 B]
Get:2 http://deb.debian.org/debian unstable/main postgis 3.0.1+dfsg-4 (tar) 
[9093 kB]
Get:3 http://deb.debian.org/debian unstable/main postgis 3.0.1+dfsg-4 (diff) 
[41.0 kB]
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/home/ubuntu/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Sun May  3 13:58:33 2020 UTC
gpgv:using RSA key 8182DE417056408D614650D16750F10AE88D4AF1
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./postgis_3.0.1+dfsg-4.dsc
autopkgtest [04:11:11]: testing package postgis version 3.0.1+dfsg-4
autopkgtest [04:11:11]: build not needed
autopkgtest [04:11:12]: test test-extension-creation: preparing testbed
Reading package lists...
Building dependency tree...
Correcting dependencies...Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following additional packages will be installed:
  adwaita-icon-theme binfmt-support clang-10 fontconfig fontconfig-config
  fonts-dejavu-core gdal-data gtk-update-icon-cache hicolor-icon-theme libaec0
  libarmadillo9 libarpack2 libatk1.0-0 libatk1.0-data libavahi-client3
  libavahi-common-data libavahi-common3 libblas3 libbrotli1 libbsd0 libc-l10n
  libcairo2 libcfitsio8 libcharls2 libclang-common-10-dev libclang-cpp10
  libclang1-10 libcups2 libcurl3-gnutls libdap25 libdapclient6v5 libdatrie1
  libdbus-1-3 libecpg-compat3 

Bug#961138: autodep8 uses host APT packages to generate dependencies for pkg-r-autopkgtest tests

[Stefano Rivera]

Package: autodep8
Version: 0.16
Severity: normal

The autodep8 generator for pkg-r-autopkgtest uses APT lists to determine
which R packages from DESCRIPTION exist in Debian. autodep8 is run
outside the test runner, not inside it, so this makes the behaviour
dependant on the packages available to the test runner host.

Here's the code that introduced this approach:
https://salsa.debian.org/ci-team/autodep8/-/merge_requests/10

It all works when the autopkgtest runner has approximately the same
packages available as the release under test, but that's not always the
case.

I noticed that the r-bioc-hdf5 package's test misses a dependency on
r-cranc-bit64 when the test is run from an older stable release that
predates this package.

I don't know how else you can solve this particular problem, though...

SR

Bug#960876: bcalm: diff for NMU version 2.2.2-1.1

[Stefano Rivera]

Control: tags 960876 + patch

Dear maintainer,

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

Regards.

SR
diff -Nru bcalm-2.2.2/debian/bcalm.install bcalm-2.2.2/debian/bcalm.install
--- bcalm-2.2.2/debian/bcalm.install	2020-05-05 12:21:17.0 -0700
+++ bcalm-2.2.2/debian/bcalm.install	2020-05-20 08:51:23.0 -0700
@@ -1,6 +1,5 @@
-debian/missing-sources/compare_fasta.py usr/share/doc/bcalm/test
-debian/missing-sources/reference.fasta usr/share/doc/bcalm/test
-debian/missing-sources/simple_test.sh usr/share/doc/bcalm/test
 example/* usr/share/doc/bcalm/test
 test/* usr/share/doc/bcalm/test
 debian/missing-sources/compare_fasta.py usr/share/doc/bcalm/test
+debian/missing-sources/reference.fasta usr/share/doc/bcalm/test
+debian/missing-sources/simple_test.sh usr/share/doc/bcalm/test
diff -Nru bcalm-2.2.2/debian/changelog bcalm-2.2.2/debian/changelog
--- bcalm-2.2.2/debian/changelog	2020-05-05 12:21:17.0 -0700
+++ bcalm-2.2.2/debian/changelog	2020-05-20 08:51:35.0 -0700
@@ -1,3 +1,11 @@
+bcalm (2.2.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Overwrite upstream's simple_test with our fixed version, so we test with
+Python 3, again. And depend on it for the test. (Closes: #960876)
+
+ -- Stefano Rivera   Wed, 20 May 2020 08:51:35 -0700
+
 bcalm (2.2.2-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru bcalm-2.2.2/debian/tests/control bcalm-2.2.2/debian/tests/control
--- bcalm-2.2.2/debian/tests/control	2020-05-05 12:21:03.0 -0700
+++ bcalm-2.2.2/debian/tests/control	2020-05-20 08:51:33.0 -0700
@@ -1,3 +1,3 @@
 Tests: run-unit-test
-Depends: @
+Depends: @, python3
 Restrictions: allow-stderr

Bug#960010: freefem++: diff for NMU version 3.61.1+dfsg1-5.1

[Stefano Rivera]

Control: tags 960010 + patch

Dear maintainer,

I've prepared an NMU for freefem++ (versioned as 3.61.1+dfsg1-5.1). The diff
is attached to this message.

Regards,

SR
diff -Nru freefem++-3.61.1+dfsg1/debian/changelog freefem++-3.61.1+dfsg1/debian/changelog
--- freefem++-3.61.1+dfsg1/debian/changelog	2019-10-05 00:21:24.0 -0700
+++ freefem++-3.61.1+dfsg1/debian/changelog	2020-05-17 13:41:04.0 -0700
@@ -1,3 +1,10 @@
+freefem++ (3.61.1+dfsg1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with gsl 2.6 (Closes: #960010)
+
+ -- Stefano Rivera   Sun, 17 May 2020 13:41:04 -0700
+
 freefem++ (3.61.1+dfsg1-5) unstable; urgency=medium
 
   * Team upload.
diff -Nru freefem++-3.61.1+dfsg1/debian/patches/double-cblas-import.patch freefem++-3.61.1+dfsg1/debian/patches/double-cblas-import.patch
--- freefem++-3.61.1+dfsg1/debian/patches/double-cblas-import.patch	1969-12-31 16:00:00.0 -0800
+++ freefem++-3.61.1+dfsg1/debian/patches/double-cblas-import.patch	2020-05-17 13:21:25.0 -0700
@@ -0,0 +1,25 @@
+Description: Avoid FTBFS with gsl 2.6 by including 2 incompatible cblas headers
+Bug-Debian: https://bugs.debian.org/960010
+Author: Frederic Hecht 
+Origin: upstream, https://github.com/FreeFem/FreeFem-sources/commit/3bfe3eb669c580583e9290474614b45cee52a96c
+
+--- a/src/femlib/MatriceCreuse_tpl.hpp
 b/src/femlib/MatriceCreuse_tpl.hpp
+@@ -12,7 +12,7 @@
+ // test blas 
+ //  on MacOS9 under MWERKS
+ //  cblas_ddot macos-9 is not 
+-#ifdef HAVE_CBLAS_H
++#ifdef HAVE_CBLAS_H_BUG
+ extern "C" {
+ #define FF_VERSION VERSION
+ #undef VERSION
+@@ -21,7 +21,7 @@
+ #define VERSION VERSION
+ }
+ #define WITHBLAS 1
+-#elif HAVE_VECLIB_CBLAS_H
++#elif HAVE_VECLIB_CBLAS_BUG
+ #include  
+ #define WITHBLAS 1
+ #endif  
diff -Nru freefem++-3.61.1+dfsg1/debian/patches/series freefem++-3.61.1+dfsg1/debian/patches/series
--- freefem++-3.61.1+dfsg1/debian/patches/series	2019-10-05 00:21:24.0 -0700
+++ freefem++-3.61.1+dfsg1/debian/patches/series	2020-05-17 13:17:38.0 -0700
@@ -3,3 +3,4 @@
 examples++-load.patch
 src_fflib.patch
 fix_all.edp.patch
+double-cblas-import.patch

Bug#960566: trash-cli: Crashes on big endian with OSError: Unable to open /proc/mounts nor /etc/mtab

[Stefano Rivera]

Hi Debian (2020.05.13_19:25:05_-0700)
> Patch attached.

Whoops, missed the mode flags.
Updated patch attached.

SR
From dad0c592892b7e296dd81e22501d5d34323cdc83 Mon Sep 17 00:00:00 2001
From: Stefano Rivera 
Date: Wed, 13 May 2020 18:43:21 -0700
Subject: [PATCH] Python 3 compatibility in list_mount_points

ctypes requires byte strings for arguments and return values.

This will return unicode strings under Python 2. But that's EoL now.
---
 trashcli/list_mount_points.py | 13 -
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/trashcli/list_mount_points.py b/trashcli/list_mount_points.py
index f0f9cb8..f8b1618 100644
--- a/trashcli/list_mount_points.py
+++ b/trashcli/list_mount_points.py
@@ -60,17 +60,20 @@ def _mounted_filesystems_from_getmnt() :
 libc.fopen.restype = c_void_p
 libc.fclose.argtypes = [c_void_p]
 
-f = libc.fopen("/proc/mounts", "r")
+f = libc.fopen(b"/proc/mounts", b"r")
 if f==None:
-f = libc.fopen("/etc/mtab", "r")
+f = libc.fopen(b"/etc/mtab", b"r")
 if f == None:
 raise IOError("Unable to open /proc/mounts nor /etc/mtab")
 
+fse = sys.getfilesystemencoding()
+
 while True:
 entry = libc.getmntent(f)
 if bool(entry) == False:
 libc.fclose(f)
 break
-yield Filesystem(entry.contents.mnt_dir,
- entry.contents.mnt_type,
- entry.contents.mnt_fsname)
+yield Filesystem(
+entry.contents.mnt_dir.decode(fse, 'surrogateescape'),
+entry.contents.mnt_type.decode('ascii'),
+entry.contents.mnt_fsname.decode(fse, 'surrogateescape'))
-- 
2.26.2

Bug#960566: trash-cli: Crashes on big endian with OSError: Unable to open /proc/mounts nor /etc/mtab

[Stefano Rivera]

Package: trash-cli
Version: 0.17.1.14-3
Severity: normal
Tags: patch upstream
Forwarded: https://github.com/andreafrancia/trash-cli/pull/170

Doesn't look like trash-cli was really ready for Python 3 :)

It fails on big-endian architectures with:

| $ trash-list
| Traceback (most recent call last):
|   File "/usr/bin/trash-list", line 5, in 
| sys.exit(main())
|   File "/usr/lib/python3/dist-packages/trashcli/cmds.py", line 45, in list
| ListCmd(
|   File "/usr/lib/python3/dist-packages/trashcli/list.py", line 37, in run
| parse(argv)
|   File "/usr/lib/python3/dist-packages/trashcli/trash.py", line 110, in 
__call__
| self.default_action()
|   File "/usr/lib/python3/dist-packages/trashcli/list.py", line 51, in 
list_trash
| trashdirs.list_trashdirs()
|   File "/usr/lib/python3/dist-packages/trashcli/trash.py", line 151, in 
list_trashdirs
| self._for_each_volume_trashcan()
|   File "/usr/lib/python3/dist-packages/trashcli/trash.py", line 157, in 
_for_each_volume_trashcan
| for volume in self.mount_points():
|   File "/usr/lib/python3/dist-packages/trashcli/list_mount_points.py", line 
5, in mount_points
| return list(mount_points_from_getmnt())
|   File "/usr/lib/python3/dist-packages/trashcli/list_mount_points.py", line 
10, in mount_points_from_getmnt
| for elem in _mounted_filesystems_from_getmnt():
|   File "/usr/lib/python3/dist-packages/trashcli/list_mount_points.py", line 
67, in _mounted_filesystems_from_getmnt
| raise IOError("Unable to open /proc/mounts nor /etc/mtab")
| OSError: Unable to open /proc/mounts nor /etc/mtab

That seems to be be caused by passing a unicode string as an argument to
ctypes, under Python 3.

On little-endian architectures, I think an empty list was returned from
mount_points() most of the time.

Patch attached.

SR
From 0a54191a51bbf78bbcadacc26b3a5c760aadc879 Mon Sep 17 00:00:00 2001
From: Stefano Rivera 
Date: Wed, 13 May 2020 18:43:21 -0700
Subject: [PATCH] Python 3 compatibility in list_mount_points

ctypes requires byte strings for arguments and return values.

This will return unicode strings under Python 2. But that's EoL now.
---
 trashcli/list_mount_points.py | 13 -
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/trashcli/list_mount_points.py b/trashcli/list_mount_points.py
index f0f9cb8..a757b8d 100644
--- a/trashcli/list_mount_points.py
+++ b/trashcli/list_mount_points.py
@@ -60,17 +60,20 @@ def _mounted_filesystems_from_getmnt() :
 libc.fopen.restype = c_void_p
 libc.fclose.argtypes = [c_void_p]
 
-f = libc.fopen("/proc/mounts", "r")
+f = libc.fopen(b"/proc/mounts", "r")
 if f==None:
-f = libc.fopen("/etc/mtab", "r")
+f = libc.fopen(b"/etc/mtab", "r")
 if f == None:
 raise IOError("Unable to open /proc/mounts nor /etc/mtab")
 
+fse = sys.getfilesystemencoding()
+
 while True:
 entry = libc.getmntent(f)
 if bool(entry) == False:
 libc.fclose(f)
 break
-yield Filesystem(entry.contents.mnt_dir,
- entry.contents.mnt_type,
- entry.contents.mnt_fsname)
+yield Filesystem(
+entry.contents.mnt_dir.decode(fse, 'surrogateescape'),
+entry.contents.mnt_type.decode('ascii'),
+entry.contents.mnt_fsname.decode(fse, 'surrogateescape'))
-- 
2.26.2

Bug#960564: usbauth: autopkgtest fails on Ubuntu

[Stefano Rivera]

Package: usbauth
Version: 1.0.2-1
Severity: normal
Tags: patch

On Ubuntu, the "service dbus start" doesn't work.

| # service dbus start
| Failed to start dbus.service: Operation refused, unit dbus.service may be 
requested by dependency only (it is configured to refuse manual start/stop).
| See system logs and 'systemctl status dbus.service' for details.
| 
| # cat /lib/systemd/system/dbus.service
| [Unit]
| Description=D-Bus System Message Bus
| Documentation=man:dbus-daemon(1)
| Requires=dbus.socket
| # we don't properly stop D-Bus (see ExecStop=), thus disallow restart
| RefuseManualStart=yes
| 
| [Service]
| ExecStart=/usr/bin/dbus-daemon --system --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only
| ExecReload=/usr/bin/dbus-send --print-reply --system --type=method_call 
--dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
| ExecStop=/bin/true
| KillMode=none
| OOMScoreAdjust=-900

What you can safely do is systemctl start dbus.socket, which will ensure
that DBus starts, and is running.

Stopping DBus is almost never a good idea, so the test probably
shouldn't do that. If it did, it should declare the isolation-container
restriction.

So, how about this patch:

diff -Nru usbauth-1.0.2/debian/tests/control usbauth-1.0.2/debian/tests/control
--- usbauth-1.0.2/debian/tests/control  2019-12-10 18:14:31.0 -0800
+++ usbauth-1.0.2/debian/tests/control  2020-05-13 17:22:36.0 -0700
@@ -1,3 +1,3 @@
 Tests: test
-Depends: @, libc-bin, usbauth-notifier, dbus
+Depends: dbus, libc-bin, systemd, usbauth-notifier, @
 Restrictions: needs-root, allow-stderr
diff -Nru usbauth-1.0.2/debian/tests/test usbauth-1.0.2/debian/tests/test
--- usbauth-1.0.2/debian/tests/test 2019-12-10 17:46:36.0 -0800
+++ usbauth-1.0.2/debian/tests/test 2020-05-13 17:22:10.0 -0700
@@ -8,9 +8,8 @@
 echo "run: Test"
 
 echo "allow all" | tee /etc/usbauth.conf
-service dbus start
+systemctl start dbus.socket
 usbauth init
-service dbus stop
 
 echo "run: Successful"
 exit 0

It works for me with the schroot, lxd, and qemu backends, so it should pass on
both Debian and Ubuntu's CI environments.

SR

Bug#960528: src:wiredtiger: Builds on other 64bit architectures

[Stefano Rivera]

Package: src:wiredtiger
Version: 2.9.3+ds-1
Severity: normal

Ubuntu has been carrying a patch to keep wiredtiger building on other
architectures. It looks like upstream has been taking patches to port to
64bit architectures.

Wiredtiger has been reliably building in Ubuntu on arm64, ppc64el, and
s390x, as well as amd64. Verified with 3.2.1 on Debian porterboxes, too.

So, maybe allow building on any 64bit arch? Or the ones it is known to
build on?

SR

Bug#947568: mixxx: diff for NMU version 2.2.3~dfsg-1.1

[Stefano Rivera]

Control: tags 947568 + patch

Dear maintainer,

It looks like the relevant upstream patch is
https://github.com/mixxxdj/mixxx/pull/2201/commits/03fad27e1f0f18ec83c9a4bc5f03f28948cd44fb

I've prepared an NMU for mixxx (versioned as 2.2.3~dfsg-1.1). The diff
is attached to this message.

Regards.

SR
diff -Nru mixxx-2.2.3~dfsg/debian/changelog mixxx-2.2.3~dfsg/debian/changelog
--- mixxx-2.2.3~dfsg/debian/changelog	2020-01-10 13:33:58.0 -0800
+++ mixxx-2.2.3~dfsg/debian/changelog	2020-05-12 16:07:23.0 -0700
@@ -1,3 +1,11 @@
+mixxx (2.2.3~dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Cherry-pick an upstream patch to fix a FTBFS with Scons under Python 3.
+(Closes: #947568)
+
+ -- Stefano Rivera   Tue, 12 May 2020 16:07:23 -0700
+
 mixxx (2.2.3~dfsg-1) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru mixxx-2.2.3~dfsg/debian/patches/0005-scons-3.patch mixxx-2.2.3~dfsg/debian/patches/0005-scons-3.patch
--- mixxx-2.2.3~dfsg/debian/patches/0005-scons-3.patch	1969-12-31 16:00:00.0 -0800
+++ mixxx-2.2.3~dfsg/debian/patches/0005-scons-3.patch	2020-05-12 16:06:52.0 -0700
@@ -0,0 +1,21 @@
+Description: Build correctly under scons on Python 3
+Bug-Upstream: https://bugs.launchpad.net/mixxx/+bug/1817742
+Bug-Debian: https://bugs.debian.org/947568
+Author: Jan Holthuis 
+Origin: upstream, https://github.com/mixxxdj/mixxx/pull/2201/commits/03fad27e1f0f18ec83c9a4bc5f03f28948cd44fb
+
+--- a/build/depends.py
 b/build/depends.py
+@@ -1285,7 +1285,11 @@
+ 'preferences/dialog/dlgprefvinyldlg.ui',
+ 'preferences/dialog/dlgprefwaveformdlg.ui',
+ ]
+-map(Qt.uic(build), ui_files)
++
++# In Python 3.x, map() returns a "map object" (instead of a list),
++# which is evaluated on-demand rather than at once. To invoke uic
++# for all *.ui files at once, we need to cast it to a list here.
++list(map(Qt.uic(build), ui_files))
+ 
+ if build.platform_is_windows:
+ # Add Windows resource file with icons and such
diff -Nru mixxx-2.2.3~dfsg/debian/patches/series mixxx-2.2.3~dfsg/debian/patches/series
--- mixxx-2.2.3~dfsg/debian/patches/series	2020-01-10 13:32:29.0 -0800
+++ mixxx-2.2.3~dfsg/debian/patches/series	2020-05-12 15:56:06.0 -0700
@@ -2,3 +2,4 @@
 0002-desktop_file.patch
 0003-soundtouch.patch
 0004-remove_inappropriate_arm_flags.patch
+0005-scons-3.patch

Bug#960361: src:chromium: FTBFS with re2 20200501

[Stefano Rivera]

Package: src:chromium
Version: 81.0.4044.92-1
Severity: normal
Tags: upstream patch
Control: block 960360 by -1

Chromium needs this (1-line) patch to build with re2 20200501
https://github.com/chromium/chromium/commit/ede390a0b18e4565abf8ac1e1ff717e1d43fc320

> Clean up a call to set_utf8().
> This is part of an effort to rewrite calls to utf8() and set_utf8()
> (in RE2::Options) as calls to encoding() and set_encoding(),
> respectively. utf8() and set_utf8() have been marked as the "legacy"
> interface since 2008, so it is long past time that we get rid of them.

This is is upstream in 84.0.4115.0, and applies cleanly to
81.0.4044.92-1.

Please backport it, so that we can update RE2.

re2 20200501 is available in experimental.

SR

Bug#960360: transition: re2

[Stefano Rivera]

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

Public ABI Breakage:
Types changed from maps to vectors in a couple of functions. Nothing in
Debian uses them.

Public API Breakage:
The deprecated RE2::Options::set_utf8 and RE2::Options::utf8 helper
functions were removed from re2.h.

https://github.com/google/re2/commit/58141dc9c92189ed8d046f494f5e034d5db91bea
https://github.com/google/re2/commit/ac65d4531798ffc9bf807d1f7c09efb0eec70480

Reverse Dependencies:
* Updated ruby-re2 to 1.2.0 to support this.
* Chromium needs a patch:
  
https://github.com/chromium/chromium/commit/ede390a0b18e4565abf8ac1e1ff717e1d43fc320
* Others build without error.

Ben file:

title = "re2";
is_affected = .depends ~ "libre2-6" | .depends ~ "libre2-7";
is_good = .depends ~ "libre2-7";
is_bad = .depends ~ "libre2-6";

https://release.debian.org/transitions/html/auto-re2.html LGTM

SR

Bug#958554: beautifulsoup4: autopkgtest failure.

[Stefano Rivera]

Control: forwarded -1 https://bugs.launchpad.net/beautifulsoup/+bug/1872279

> From diffing test logs I belive this was most-likely caused by the
> update to python-soupsieve

Yep.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#958714: buster-pu: package distro-info-data/0.41+deb10u2

[Stefano Rivera]

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

Hi,

I want to update distro-info-data, so that it knows about the current
Ubuntu development release. While I'm here, I can make a guess at
Stretch's EoL based on Buster's release date. If we get a better date,
we should update it.

Test cases:
$ ubuntu-distro-info --devel
groovy
$ debian-distro-info --date=2020-08-01 --supported
buster
bullseye
sid
experimental

(Yeah it doesn't know about LTS yet. That's
https://salsa.debian.org/debian/distro-info-data/merge_requests/2 which I must
just merge)

Debdiff (uploaded):

diff --git a/debian.csv b/debian.csv
index 78abfed..d20aabf 100644
--- a/debian.csv
+++ b/debian.csv
@@ -12,7 +12,7 @@ version,codename,series,created,release,eol
 6.0,Squeeze,squeeze,2009-02-14,2011-02-06,2014-05-31
 7,Wheezy,wheezy,2011-02-06,2013-05-04,2016-04-26
 8,Jessie,jessie,2013-05-04,2015-04-25,2018-06-06
-9,Stretch,stretch,2015-04-25,2017-06-17
+9,Stretch,stretch,2015-04-25,2017-06-17,2020-07-06
 10,Buster,buster,2017-06-17,2019-07-06
 11,Bullseye,bullseye,2019-07-06
 12,Bookworm,bookworm,2021-08-01
diff --git a/debian/changelog b/debian/changelog
index 8088798..b22e04e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+distro-info-data (0.41+deb10u2) buster; urgency=medium
+
+  * Update data to 0.44:
+- Add Ubuntu 20.10, Groovy Gorilla.
+- Add a guessed EOL date for Debian Stretch.
+
+ -- Stefano Rivera   Fri, 24 Apr 2020 09:24:59 -0700
+
 distro-info-data (0.41+deb10u1) buster; urgency=medium
 
   [ Stefano Rivera ]
diff --git a/ubuntu.csv b/ubuntu.csv
index 08d442f..0236239 100644
--- a/ubuntu.csv
+++ b/ubuntu.csv
@@ -31,3 +31,4 @@ version,codename,series,created,release,eol,eol-server
 19.04,Disco Dingo,disco,2018-10-18,2019-04-18,2020-01-18
 19.10,Eoan Ermine,eoan,2019-04-18,2019-10-17,2020-07-17
 20.04 LTS,Focal Fossa,focal,2019-10-17,2020-04-23,2025-04-23
+20.10,Groovy Gorilla,groovy,2020-04-23,2020-10-22,2021-07-22

Bug#956582: Acknowledgement (linux-image-5.5.0-1-amd64: USB/Bluetooth restarting)

[Stefano Callegari]

Hi.

I have the same with the last linux-image-5.5.0-2-amd64


Apr 20 02:07:03 G5045 kernel: [  286.784680] usb 2-1.3: USB disconnect, device 
number 11
Apr 20 02:07:03 G5045 systemd[4865]: Stopped target Bluetooth.
Apr 20 02:07:03 G5045 systemd[1]: Stopped target Bluetooth.
Apr 20 02:07:03 G5045 kernel: [  286.887460] usb 2-1.3: new full-speed USB 
device number 12 using ehci-pci
Apr 20 02:07:03 G5045 kernel: [  286.997045] usb 2-1.3: New USB device found, 
idVendor=0cf3, idProduct=3004, bcdDevice= 0.01
Apr 20 02:07:03 G5045 kernel: [  286.997053] usb 2-1.3: New USB device strings: 
Mfr=0, Product=0, SerialNumber=0
Apr 20 02:07:03 G5045 kernel: [  286.999797] usb 2-1.3: firmware: 
direct-loading firmware ar3k/ramps_0x3101_40.dfu
Apr 20 02:07:03 G5045 kernel: [  287.046018] usb 2-1.3: USB disconnect, device 
number 12
Apr 20 02:07:03 G5045 kernel: [  287.271565] usb 2-1.3: new full-speed USB 
device number 13 using ehci-pci
Apr 20 02:07:08 G5045 kernel: [  292.489307] usb 2-1.3: New USB device found, 
idVendor=0cf3, idProduct=3004, bcdDevice= 0.02
Apr 20 02:07:08 G5045 kernel: [  292.489315] usb 2-1.3: New USB device strings: 
Mfr=0, Product=0, SerialNumber=0
Apr 20 02:07:09 G5045 systemd-udevd[5279]: hci0: Process '/usr/bin/hciconfig 
hci0 up' failed with exit code 1.
Apr 20 02:07:09 G5045 systemd[4865]: Reached target Bluetooth.
Apr 20 02:07:09 G5045 systemd[5197]: Reached target Bluetooth.
Apr 20 02:07:09 G5045 systemd[1]: Reached target Bluetooth.
Apr 20 02:07:09 G5045 kernel: [  293.383506] hid-generic 0005:046D:B00D.0005: 
unknown main item tag 0x0
Apr 20 02:07:09 G5045 kernel: [  293.385595] input: Ultrathin Touch Mouse 
Keyboard as 
/devices/pci:00/:00:13.0/usb2/2-1/2-1.3/2-1.3:1.0/bluetooth/hci0/hci0:21/0005:046D:B00D.0005/input/input23
Apr 20 02:07:09 G5045 kernel: [  293.386334] input: Ultrathin Touch Mouse as 
/devices/pci:00/:00:13.0/usb2/2-1/2-1.3/2-1.3:1.0/bluetooth/hci0/hci0:21/0005:046D:B00D.0005/input/input24
Apr 20 02:07:09 G5045 kernel: [  293.386699] hid-generic 0005:046D:B00D.0005: 
input,hidraw3: BLUETOOTH HID v7.00 Keyboard [Ultrathin Touch Mouse] on 
18:cf:5e:50:20:bc
Apr 20 02:07:10 G5045 upowerd[2370]: treating change event as add on 
/sys/devices/pci:00/:00:13.0/usb2/2-1/2-1.3/2-1.3:1.0/bluetooth/hci0/hci0:21/0005:046D:B00D.0005/power_supply/hid-00:1f:20:95:c5:58-battery



Thanks
-- 
Stefano Callegari
GnuPG Public Key Server: pgp.mit.edu

Bug#956582: linux-image-5.5.0-1-amd64: USB/Bluetooth restarting

[Stefano Callegari]

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

Dear Maintainer,

I use a bluetooth mouse and when I move it to pairing or simply to use it,
the mouse freeze for few seconds.

In /var/log/syslog I find these lines every time:

Apr 13 11:03:22 G5045 kernel: [ 4399.912981] usb 2-1.3: USB disconnect, device 
number 51
Apr 13 11:03:22 G5045 systemd[7955]: Stopped target Bluetooth.
Apr 13 11:03:22 G5045 systemd[5329]: Stopped target Bluetooth.
Apr 13 11:03:22 G5045 systemd[1]: Stopped target Bluetooth.
Apr 13 11:03:22 G5045 kernel: [ 4400.007794] usb 2-1.3: new full-speed USB 
device number 52 using ehci-pci
Apr 13 11:03:22 G5045 kernel: [ 4400.117338] usb 2-1.3: New USB device found, 
idVendor=0cf3, idProduct=3004, bcdDevice= 0.01
Apr 13 11:03:22 G5045 kernel: [ 4400.117345] usb 2-1.3: New USB device strings: 
Mfr=0, Product=0, SerialNumber=0
Apr 13 11:03:22 G5045 kernel: [ 4400.123433] usb 2-1.3: firmware: 
direct-loading firmware ar3k/ramps_0x3101_40.dfu
Apr 13 11:03:22 G5045 kernel: [ 4400.271550] usb 2-1.3: USB disconnect, device 
number 52
Apr 13 11:03:23 G5045 kernel: [ 4400.495826] usb 2-1.3: new full-speed USB 
device number 53 using ehci-pci
Apr 13 11:03:28 G5045 kernel: [ 4405.708976] usb 2-1.3: New USB device found, 
idVendor=0cf3, idProduct=3004, bcdDevice= 0.02
Apr 13 11:03:28 G5045 kernel: [ 4405.708985] usb 2-1.3: New USB device strings: 
Mfr=0, Product=0, SerialNumber=0
Apr 13 11:03:29 G5045 systemd-udevd[31221]: hci0: Process '/usr/bin/hciconfig 
hci0 up' failed with exit code 1.
Apr 13 11:03:29 G5045 systemd[7955]: Reached target Bluetooth.
Apr 13 11:03:29 G5045 systemd[5329]: Reached target Bluetooth.
Apr 13 11:03:29 G5045 systemd[1]: Reached target Bluetooth.
Apr 13 11:03:29 G5045 kernel: [ 4406.425957] hid-generic 0005:046D:B00D.000C: 
unknown main item tag 0x0
Apr 13 11:03:29 G5045 kernel: [ 4406.426250] input: Ultrathin Touch Mouse 
Keyboard as 
/devices/pci:00/:00:13.0/usb2/2-1/2-1.3/2-1.3:1.0/bluetooth/hci0/hci0:21/0005:046D:B00D.000C/input/input54
Apr 13 11:03:29 G5045 kernel: [ 4406.426687] input: Ultrathin Touch Mouse as 
/devices/pci:00/:00:13.0/usb2/2-1/2-1.3/2-1.3:1.0/bluetooth/hci0/hci0:21/0005:046D:B00D.000C/input/input55
Apr 13 11:03:29 G5045 kernel: [ 4406.426882] hid-generic 0005:046D:B00D.000C: 
input,hidraw4: BLUETOOTH HID v7.00 Keyboard [Ultrathin Touch Mouse] on 
18:cf:5e:50:20:bc
Apr 13 11:03:29 G5045 upowerd[2418]: treating change event as add on 
/sys/devices/pci:00/:00:13.0/usb2/2-1/2-1.3/2-1.3:1.0/bluetooth/hci0/hci0:21/0005:046D:B00D.000C/power_supply/hid-00:1f:20:95:c5:58-battery

No problem with the kernel 5.4 series.

No problems with other usb devices (now I write with the "Bus 001 Device
006: ID 05a4:2000 Ortek Technology, Inc. WKB-2000 Wireless Keyboard with
Touchpad").

Thanks.

-- Package-specific info:
** Version:
Linux version 5.5.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-8)) #1 SMP Debian 5.5.13-2 (2020-03-30)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.5.0-1-amd64 
root=UUID=fd709365-bd5b-44c2-91ec-423898a4ac6a ro quiet

** Tainted: OE (12288)
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 80E3
product_version: Lenovo G50-45
chassis_vendor: LENOVO
chassis_version: Lenovo G50-45
bios_vendor: LENOVO
bios_version: A2CN45WW(V2.13)
board_vendor: LENOVO
board_name: Lancer 5B2
board_version: 31900058 STD

** Loaded modules:
hidp
vboxnetadp(OE)
vboxnetflt(OE)
vboxdrv(OE)
cmac
rfcomm
bnep
uinput
xt_tcpudp
nf_log_ipv4
nf_log_common
nft_limit
xt_LOG
xt_limit
xt_state
xt_conntrack
nft_counter
xt_MASQUERADE
nft_compat
nf_nat_sip
nf_conntrack_sip
nf_nat_ftp
nf_conntrack_ftp
nft_chain_nat
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nf_tables
nfnetlink
ath3k
btusb
uvcvideo
btrtl
btbcm
snd_usb_audio
btintel
bluetooth
videobuf2_vmalloc
videobuf2_memops
snd_usbmidi_lib
videobuf2_v4l2
videobuf2_common
snd_rawmidi
rtsx_usb_ms
drbg
snd_seq_device
videodev
ansi_cprng
memstick
mc
rtsx_usb_sdmmc
ecdh_generic
ecc
rtsx_usb
crc16
binfmt_misc
nls_ascii
nls_cp437
vfat
fat
pktcdvd
ath9k
snd_hda_codec_conexant
edac_mce_amd
snd_hda_codec_generic
ath9k_common
ledtrig_audio
kvm_amd
kvm
snd_hda_codec_hdmi
snd_hda_intel
irqbypass
ath9k_hw
ideapad_laptop
snd_intel_dspcfg
ath
snd_hda_codec
sparse_keymap
wmi
crct10dif_pclmul
mac80211
snd_hda_core
crc32_pclmul
snd_hwdep
ghash_clmulni_intel
snd_pcm_oss
snd_mixer_oss
snd_pcm
r8169
cfg80211
snd_timer
snd
aesni_intel
soundcore
rfkill
crypto_simd
libarc4
cryptd
glue_helper
realtek
sdhci_pci
cqhci
libphy
sr_mod
cdrom
sdhci
sg
sp5100_tco
efi_pstore
xhci_pci
watchdog
xhci_hcd
efivars
pcspkr
mmc_core
fam15h_power
joydev
k10temp
ccp
i2c_piix4
battery
video
ac
rng_core
acpi_cpufreq
button
parport_pc
ppdev
lp
parport
efivarfs
ip_tables
x_tables
autofs4
jfs
raid10
raid456
libcrc32c
crc32c_generic

Bug#956412: pypy3: /usr/local/lib/pypy3.6/dist-packages/ not on sys.path

[Stefano Rivera]

Package: pypy3
Version: 7.3.0+dfsg-4
Severity: normal

sys.path isn't setup correctly for pypy3 to use locally installed
modules. I don't think it ever has been, I just keep forgetting about
it.

Virtualenvs work, of course.

SR

Bug#954434: pulseaudio-module-bluetooth: Adds Sony LDAC, aptX, aptX HD, AAC codecs (A2DP Audio) support to PulseAudio on Linux

[Stefano F.]

Some updates for Pulseaudio 14 branch

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227#note_441126

Il sab 21 mar 2020, 18:45 Stefano F.  ha scritto:

> If we need a new alternative package the RFC is at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954442
>
> Il giorno sab 21 mar 2020 alle ore 17:17 Felipe Sateler
>  ha scritto:
> >
> > Control: tags -1 moreinfo
> >
> > On Sat, Mar 21, 2020 at 12:33 PM Stefano F. 
> wrote:
> >>
> >> Package: pulseaudio-module-bluetooth
> >> Version: 13.99.1-1
> >> Severity: wishlist
> >> Tags: upstream
> >>
> >> Dear Maintainer,
> >>
> >> it would be nice to have non-free alternative package for A2DP codecs
> for
> >> modern true wireless earbuds supporte codecs with the packaging of[1].
> >>
> >> See also[2][3][4]
> >>
> >> [1]https://github.com/EHfive/pulseaudio-modules-bt
> >> [2]
> https://github.com/EHfive/pulseaudio-modules-bt/wiki#are-there-any-plans-to-
> >> upstream-this-into-pulseaudio
> >> [3]https://github.com/EHfive/pulseaudio-modules-bt/issues/3
> >> [4]
> https://eischmann.wordpress.com/2019/02/11/better-bluetooth-sound-quality-
> >> on-linux/
> >
> >
> > I'm not sure what you are proposing. If you want these modules to be
> packaged, please help with getting #794692 resolved and then file a RFP for
> the modules.
> >
> > --
> >
> > Saludos,
> > Felipe Sateler
>

Bug#945696: lokalize: Python2 removal in sid/bullseye

[Stefano Rivera]

Looked into what's here, and it's really just 3 Python Kross scripts
(i.e. optional extensions to the Qt application).
Kross itself isn't ported yet (#936809).

These are not used, unless the user manually installs them, by dragging
the .rc file into the application, as described here [0]

[0]: 
https://shaforostoff.blogspot.com/2009/07/testing-kde-43-translation-with.html

They don't look particularly actively maintained. I tried running the
one that doesn't need Kross (xliffmerge), and it blew up because it
wasn't ported to Qt5, completely.

Fedora has a commit that switched lokalize to Python 3 [1] but they've
really just changed a dependency, that isn't being used.
And, separately, dropped Python Kross support [2].

[1] 
https://src.fedoraproject.org/rpms/lokalize/c/3d6b3b18aa585bf5cfb958d9269788a06297a7b4?branch=master
[2] 
https://src.fedoraproject.org/rpms/kf5-kross-interpreters/c/c471038238818285c9289236e9483ee60605879f?branch=master

So, it'd be reasonable to just drop these scripts, and Recommends
entirely until Kross is ported to Python 3, and they're known to work,
again.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#955534: gdal-bin on debian SID - unmet dependencies

[massimo di stefano]

Package: gdal-bin
Version: 3.0.4+dfsg-1+b1

  When I invoke `apt-get install gdal-bin' i get the following error:

```
Reading package lists...

Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gdal-bin : Depends: python3-gdal (= 3.0.4+dfsg-1+b1) but it is not
going to be installed
Depends: libgdal26 (>= 3.0.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

```

Bug#945187: ImportError: No module named 'pip._vendor.retrying'

[Stefano Rivera]

Control: reassign -1 python3-pip
Control: affects -1 pypy3

Hi Brian (2019.11.20_15:04:44_-0800)
> # pypy3 -m pip

The recommended (and supported) mechanism is to use pip with a
virtualenv.

i.e.

pypy3 -m venv my-ve
ve/bin/python -m pip ...

That works.

However, this is a bug.

The vendor wheel hack in pip depends on sys.prefix, which is /usr for
python3 and /usr/lib/pypy3 from pypy3.

I don't know what the right solution here is. I can think of:
1. Create a symlink /usr/lib/pypy3/share/python-wheels in the pypy3
   package. Eww.
2. Special-case /usr/lib/pypy3 -> /usr in the pip patch.
3. Hard-code WHEEL_DIR in pip. Means it'll be used in venvs too.

Leaning towards 2.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#954788: nvidia-legacy-check can't be installed

[Stefano Simonucci]

Package: nvidia-legacy-check
Version: nvidia-legacy-check_440.64-1_amd64.deb
Severity: normal
Tags: a11y

Dear Maintainer,

when I try to install the package nvidia-legacy-check (in order to install 
nvidia-cuda-toolkit) I get the 
following message:
*** The following unsupported devices are present in the machine:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119M [GeForce GT 
520MX] [10de:1051] (rev a1)
Aborting nvidia driver installation.
dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/nvidia-legacy-che
ck_440.64-1_amd64.deb (--unpack):
 il sottoprocesso nuovo pacchetto nvidia-legacy-check script pre-installation ha
 restituito lo stato di errore 1
Si sono verificati degli errori nell'elaborazione:
 /var/cache/apt/archives/nvidia-legacy-check_440.64-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1).
So I'm not able to install nvidia-cuda-toolkit with my GPU.
Best regards
Stefano


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

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.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 nvidia-legacy-check depends on:
ii  debconf [debconf-2.0] 1.5.73
ii  nvidia-installer-cleanup  20151021+11
ii  pciutils  1:3.6.4-1

nvidia-legacy-check recommends no packages.

nvidia-legacy-check suggests no packages.

Bug#954434: pulseaudio-module-bluetooth: Adds Sony LDAC, aptX, aptX HD, AAC codecs (A2DP Audio) support to PulseAudio on Linux

[Stefano F.]

If we need a new alternative package the RFC is at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954442

Il giorno sab 21 mar 2020 alle ore 17:17 Felipe Sateler
 ha scritto:
>
> Control: tags -1 moreinfo
>
> On Sat, Mar 21, 2020 at 12:33 PM Stefano F.  wrote:
>>
>> Package: pulseaudio-module-bluetooth
>> Version: 13.99.1-1
>> Severity: wishlist
>> Tags: upstream
>>
>> Dear Maintainer,
>>
>> it would be nice to have non-free alternative package for A2DP codecs for
>> modern true wireless earbuds supporte codecs with the packaging of[1].
>>
>> See also[2][3][4]
>>
>> [1]https://github.com/EHfive/pulseaudio-modules-bt
>> [2]https://github.com/EHfive/pulseaudio-modules-bt/wiki#are-there-any-plans-to-
>> upstream-this-into-pulseaudio
>> [3]https://github.com/EHfive/pulseaudio-modules-bt/issues/3
>> [4]https://eischmann.wordpress.com/2019/02/11/better-bluetooth-sound-quality-
>> on-linux/
>
>
> I'm not sure what you are proposing. If you want these modules to be 
> packaged, please help with getting #794692 resolved and then file a RFP for 
> the modules.
>
> --
>
> Saludos,
> Felipe Sateler

Bug#954442: RFP: pulseaudio-module-bluetooth-nonfree -- Sony LDAC, aptX, aptX HD, AAC codecs (A2DP Audio) support to PulseAudio on Linux

[Stefano F.]

Package: wnpp
Severity: wishlist

* Package name: pulseaudio-module-bluetooth-nonfree
  Version : x.y.z
  Upstream Author : Bao H.H. 
* URL : https://github.com/EHfive/pulseaudio-modules-bt
* License : GPL3
  Programming Lang: C
  Description : Sony LDAC, aptX, aptX HD, AAC codecs (A2DP Audio) support
to PulseAudio on Linux

Pulseaudio bluetooth modules forks that adds LDAC, APTX, APTX-HD, AAC support,
extended configuration for SBC

It is very useful to support codecs for modern true wireless earbuds

Some interesting links:
[1]https://github.com/EHfive/pulseaudio-modules-bt
[2]https://github.com/EHfive/pulseaudio-modules-bt/wiki#are-there-any-plans-to-
upstream-this-into-pulseaudio
[3]https://github.com/EHfive/pulseaudio-modules-bt/issues/3
[4]https://eischmann.wordpress.com/2019/02/11/better-bluetooth-sound-quality-
on-linux/

Bug#954434: pulseaudio-module-bluetooth: Adds Sony LDAC, aptX, aptX HD, AAC codecs (A2DP Audio) support to PulseAudio on Linux

[Stefano F.]

Package: pulseaudio-module-bluetooth
Version: 13.99.1-1
Severity: wishlist
Tags: upstream

Dear Maintainer,

it would be nice to have non-free alternative package for A2DP codecs for
modern true wireless earbuds supporte codecs with the packaging of[1].

See also[2][3][4]

[1]https://github.com/EHfive/pulseaudio-modules-bt
[2]https://github.com/EHfive/pulseaudio-modules-bt/wiki#are-there-any-plans-to-
upstream-this-into-pulseaudio
[3]https://github.com/EHfive/pulseaudio-modules-bt/issues/3
[4]https://eischmann.wordpress.com/2019/02/11/better-bluetooth-sound-quality-
on-linux/



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

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

Versions of packages pulseaudio-module-bluetooth depends on:
ii  bluez5.50-1.2
ii  libc62.30-2
ii  libdbus-1-3  1.12.16-2
ii  libpulse013.99.1-1
ii  libsbc1  1.4-1+b1
ii  pulseaudio   13.99.1-1

pulseaudio-module-bluetooth recommends no packages.

pulseaudio-module-bluetooth suggests no packages.

-- no debconf information

Bug#954314: neomutt: diff for NMU version 20191207+dfsg.1-1.1

[Stefano Rivera]

Package: neomutt
Version: 20191207+dfsg.1-1
Severity: normal
Tags: patch  pending

Dear maintainer,

I've prepared an NMU for neomutt (versioned as 20191207+dfsg.1-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Diff in git: https://salsa.debian.org/mutt-team/neomutt/-/merge_requests/2

Regards.

diff -Nru neomutt-20191207+dfsg.1/debian/changelog neomutt-20191207+dfsg.1/debian/changelog
--- neomutt-20191207+dfsg.1/debian/changelog	2020-03-02 05:04:03.0 -0800
+++ neomutt-20191207+dfsg.1/debian/changelog	2020-03-19 17:09:59.0 -0700
@@ -1,3 +1,11 @@
+neomutt (20191207+dfsg.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix segfault in pager on new message received. (Closes: #953757)
+  * Fix FTBFS in non-UTC timezone. (Closes: #948895)
+
+ -- Stefano Rivera   Thu, 19 Mar 2020 17:09:59 -0700
+
 neomutt (20191207+dfsg.1-1) unstable; urgency=medium
 
   [ Andreas Henriksson ]
diff -Nru neomutt-20191207+dfsg.1/debian/patches/series neomutt-20191207+dfsg.1/debian/patches/series
--- neomutt-20191207+dfsg.1/debian/patches/series	2020-03-02 05:01:49.0 -0800
+++ neomutt-20191207+dfsg.1/debian/patches/series	2020-03-19 17:09:59.0 -0700
@@ -2,3 +2,5 @@
 debian-specific/use_usr_bin_editor.patch
 debian-specific/document_debian_defaults.patch
 misc/smime.rc.patch
+upstream/pager-segfault.patch
+upstream/test-tz.patch
diff -Nru neomutt-20191207+dfsg.1/debian/patches/upstream/pager-segfault.patch neomutt-20191207+dfsg.1/debian/patches/upstream/pager-segfault.patch
--- neomutt-20191207+dfsg.1/debian/patches/upstream/pager-segfault.patch	1969-12-31 16:00:00.0 -0800
+++ neomutt-20191207+dfsg.1/debian/patches/upstream/pager-segfault.patch	2020-03-19 17:09:59.0 -0700
@@ -0,0 +1,27 @@
+From: Pietro Cerutti 
+Date: Sat, 14 Dec 2019 16:18:28 +0100
+Subject: Fix crash in pager (#2039)
+
+Fixes #2038
+
+Bug-Upstream: https://github.com/neomutt/neomutt/issues/2038
+Origin: upstream, https://github.com/neomutt/neomutt/commit/645189415f20857fc317bb862a5b9dba33f61fa8
+Bug-Debian: https://bugs.debian.org/953757
+---
+ pager.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/pager.c b/pager.c
+index 793cdfb..1053885 100644
+--- a/pager.c
 b/pager.c
+@@ -2422,6 +2422,9 @@ int mutt_pager(const char *banner, const char *fname, PagerFlags flags, struct P
+ rd.menu->current =
+ MIN(rd.menu->current, MAX(Context->mailbox->msg_count - 1, 0));
+ struct Email *e = mutt_get_virt_email(Context->mailbox, rd.menu->current);
++if (!e)
++  continue;
++
+ index_hint = e->index;
+ 
+ bool q = Context->mailbox->quiet;
diff -Nru neomutt-20191207+dfsg.1/debian/patches/upstream/test-tz.patch neomutt-20191207+dfsg.1/debian/patches/upstream/test-tz.patch
--- neomutt-20191207+dfsg.1/debian/patches/upstream/test-tz.patch	1969-12-31 16:00:00.0 -0800
+++ neomutt-20191207+dfsg.1/debian/patches/upstream/test-tz.patch	2020-03-19 17:09:59.0 -0700
@@ -0,0 +1,94 @@
+From: Pietro Cerutti 
+Date: Wed, 29 Jan 2020 14:44:00 +
+Subject: Make sure we use the correct timezone in tests
+
+Fixes #2100
+
+Bug-Upstream: https://github.com/neomutt/neomutt/issues/2100
+Origin: upstream, https://github.com/neomutt/neomutt/commit/8aee8ba2a2e8726bf64b95d94c77dd34512b3732
+Bug-Debian: https://bugs.debian.org/948895
+---
+ test/date/mutt_date_localtime.c| 3 +++
+ test/date/mutt_date_localtime_format.c | 3 +++
+ test/date/mutt_date_make_imap.c| 3 +++
+ test/date/mutt_date_make_time.c| 3 +++
+ 4 files changed, 12 insertions(+)
+
+diff --git a/test/date/mutt_date_localtime.c b/test/date/mutt_date_localtime.c
+index dff4a89..c573445 100644
+--- a/test/date/mutt_date_localtime.c
 b/test/date/mutt_date_localtime.c
+@@ -24,11 +24,14 @@
+ #include "acutest.h"
+ #include "config.h"
+ #include "mutt/mutt.h"
++#include 
+ 
+ void test_mutt_date_localtime(void)
+ {
+   // struct tm mutt_date_localtime(time_t t);
+ 
++  setenv("TZ", "UTC", 1);
++
+   {
+ TEST_CASE("December, 2000");
+ struct tm tm = mutt_date_localtime(977745600);
+diff --git a/test/date/mutt_date_localtime_format.c b/test/date/mutt_date_localtime_format.c
+index 67907c1..23aa573 100644
+--- a/test/date/mutt_date_localtime_format.c
 b/test/date/mutt_date_localtime_format.c
+@@ -24,11 +24,14 @@
+ #include "acutest.h"
+ #include "config.h"
+ #include "mutt/mutt.h"
++#include 
+ 
+ void test_mutt_date_localtime_format(void)
+ {
+   // size_t mutt_date_localtime_format(char *buf, size_t buflen, char *format, time_t t);
+ 
++  setenv("TZ", "UTC", 1);
++
+   {
+ TEST_CHECK(mutt_date_localtime_format(NULL, 10, "apple", 0) == 0);
+   }
+diff --git a/test/date/mutt_date_make_imap.c b/test/date/mutt_date_make_imap.c
+ind

Bug#954288: transition: re2

[Stefano Rivera]

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

C++. Lots of ABI breakage...

Class members were reorganised, and mutability changed.
Upstream chose to SONAME bump.

https://github.com/google/re2/issues/243

In other news: Upstream is finally taking ownership of their soname \o/

https://release.debian.org/transitions/html/auto-re2.html looks good.

I test built all of the rev-deps (on March 3rd) and they all built,
except for clickhouse (known FTBFS: #950983).

Ben file:

title = "re2";
is_affected = .depends ~ "libre2-5" | .depends ~ "libre2-6";
is_good = .depends ~ "libre2-6";
is_bad = .depends ~ "libre2-5";


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

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

Bug#953880: Issue confirmed and possible workaround

[Stefano Gatti]

I have the same problem too.

Anyway I found the following report:

https://gitlab.gnome.org/GNOME/gimp/issues/4490

I tried to delete the file:

/usr/lib/gimp/2.0/plug-ins/pagecurl/pagecurl

and Gimp seems to work correctly.

Regards,
Stefano

Bug#948895: neomutt: FTBFS: test failure

[Stefano Rivera]

Control: reopen -1
Control: notfixed -1 20191207+dfsg.1-1

> This is fixed by:
> https://github.com/neomutt/neomutt/commit/6a98d598bf0443516146c6a856b965f5e0fb35a1#diff-80e4b64ac703024c17f04c3d0d014e40
> 
> In other words updating to the latest release (20191207) would
> fix this issue.

That is just one of the failures here.

Here's another one:
https://github.com/neomutt/neomutt/commit/26a6b07c728aa88414057cff257cdebfd2967907

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#953757: neomutt: Occasional segfault on New Message (pager.c:2425)

[Stefano Rivera]

Package: neomutt
Version: 20191207+dfsg.1-1
Severity: normal
Tags: patch upstream

Upstream issue https://github.com/neomutt/neomutt/issues/2038
Upstream patch: https://github.com/neomutt/neomutt/pull/2039

While reading a message, "New mail in this mailbox" appears and then *boom*.

gdb:
Program received signal SIGSEGV, Segmentation fault.
0x562c12c68ba2 in mutt_pager (banner=banner@entry=0x0, fname=, flags=flags@entry=66, 
extra=extra@entry=0x7ffe04fe0130) at ../pager.c:2425
2425../pager.c: No such file or directory.
(gdb) p e
$1 = (struct Email *) 0x0
(gdb) bt
#0  0x562c12c68ba2 in mutt_pager
(banner=banner@entry=0x0, fname=, flags=flags@entry=66, 
extra=extra@entry=0x7ffe04fe0130)
at ../pager.c:2425
#1  0x562c12c1f09a in mutt_display_message (win=, 
m=0x562c134a5e90, e=e@entry=0x562c140620b0)
at ../commands.c:362
#2  0x562c12c3edaa in mutt_index_menu () at ../index.c:2512
#3  0x562c12c15371 in main (argc=, argv=0x7ffe04fe3868, 
envp=) at ../main.c:1254
(gdb) 

-- Package-specific info:
NeoMutt 20191207
Copyright (C) 1996-2016 Michael R. Elkins and others.
NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type 'neomutt -vv'.
NeoMutt is free software, and you are welcome to redistribute it
under certain conditions; type 'neomutt -vv' for details.

System: Linux 5.4.0-3-amd64 (x86_64)
ncurses: ncurses 6.2.20200212 (compiled with 6.2.20200212)
libidn: 1.33 (compiled with 1.33)
GPGme: 1.13.1-unknown
libnotmuch: 5.2.0
hcache backends: tokyocabinet

Configure options: --build=x86_64-linux-gnu --prefix=/usr 
{--includedir=${prefix}/include} {--mandir=${prefix}/share/man} 
{--infodir=${prefix}/share/info} --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules {--libdir=${prefix}/lib/x86_64-linux-gnu} 
{--libexecdir=${prefix}/lib/x86_64-linux-gnu} --disable-maintainer-mode 
--disable-dependency-tracking --mandir=/usr/share/man --libexecdir=/usr/libexec 
--with-mailpath=/var/mail --gpgme --lua --notmuch --with-ui --gnutls --gss 
--idn --mixmaster --sasl --tokyocabinet

Compilation CFLAGS: -g -O2 
-fdebug-prefix-map=/build/neomutt-KUFXeJ/neomutt-20191207+dfsg.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c99 
-D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D__EXTENSIONS__ -I/usr/include 
-I/usr/include/lua5.3 -DNCURSES_WIDECHAR -isystem /usr/include/mit-krb5

Default options:
  +attach_headers_color +compose_to_sender +compress +cond_date +debug 
  +encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color 
  +initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp +pop 
  +progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser +sidebar 
  +skip_quoted +smtp +status_color +timeout +tls_sni +trash 

Compile options:
  -autocrypt +bkgdset +color +curs_set +fcntl -flock -fmemopen +futimens 
  +getaddrinfo +gnutls +gpgme +gss +hcache -homespool +idn +inotify 
  -locales_hack +lua +meta +mixmaster +nls +notmuch -openssl +pgp +sasl +smime 
  -sqlite +start_color +sun_attachment +typeahead 
MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/neomutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"

To learn more about NeoMutt, visit: https://neomutt.org
If you find a bug in NeoMutt, please raise an issue at:
https://github.com/neomutt/neomutt/issues
or send an email to: 

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

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_ZA.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 neomutt depends on:
ii  libc6 2.29-10
ii  libgnutls30   3.6.12-2
ii  libgpg-error0 1.37-1
ii  libgpgme111.13.1-6
ii  libgssapi-krb5-2  1.17-6
ii  libidn11  1.33-2.2
ii  liblua5.3-0   5.3.3-1.1+b1
ii  libncursesw6  6.2-1
ii  libnotmuch5   0.29.3-1+b1
ii  libsasl2-22.1.27+dfsg-2
ii  libtinfo6 6.2-1
ii  libtokyocabinet9  1.4.48-12

Versions of packages neomutt recommends:
ii  libsasl2-modules  2.1.27+dfsg-2
ii  locales   2.29-10
ii  mime-support  3.64

Versions of packages neomutt suggests:
ii  aspell  0.60.8-1
ii  ca-certificates 20190110
ii  gnupg   2.2.19-2
pn  mixmaster   
ii  openssl 1.1.1d-2
ii  postfix [mail-transport-agent]  3.4.9-1
pn  urlview 

Versions of packages neomutt is related to:
ii  neomutt  20191207+dfsg.1-1

-- no debconf information

Bug#953753: RM: foodcritic -- ROM; End of life upstream, replaced by chefstyle

[Stefano Rivera]

Package: ftp.debian.org
Severity: normal

https://blog.chef.io/goodbye-foodcritic/

Given that, not going to bother packaging the latest version.

SR

Bug#950983: clickhouse FTBFS in bullseye/sid

[Stefano Rivera]

Hi Jochen (2020.02.09_00:40:36_-0800)

Control: tag -1 + patch

I notice that Ubuntu has a patch for this:
https://launchpadlibrarian.net/466815449/clickhouse_18.16.1+ds-5_18.16.1+ds-5ubuntu1.diff.gz

It's building on amd64 and ppc64el:
https://launchpad.net/ubuntu/+source/clickhouse/18.16.1+ds-5ubuntu1

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#938518: soupsieve: Python2 removal in sid/bullseye

[Stefano Rivera]

Control: tags -1 - pending

And there's a new upstream release, 2.0, that drops Python 2.7 support.

I'll hold back on that, for now.

But I'm somewhat tempted to fork the source package for it. But I'll
wait a couple of months, and see if we get nearer being able to drop the
2.7 package.

Ignore the pending tag. It's me pushing 2.0 into a branch.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#952465: please set debian-project@lists.d.o as moderated

[Stefano Zacchiroli]

Package: lists.debian.org
Severity: normal

Dear listmasters,
  in light of repeated trolling and abuse targeting individual Debian
contributors distributed via debian-project@lists.d.o, I'd like to ask for that
mailing list to be set to moderated for the time being.

A group of more than 30 Debian project members have volunteered to share the
burden of moderating the list.  Once this bug report is accepted by the BTS,
I'll followup to the listmaster contact address with the list of moderators
email addresses and account names.

Thanks a lot for your work on Debian mailing lists,
(which has certainly being unduly tiresome in recent times,)

Cheers

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

Kernel: Linux 5.4.0-3-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:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#952449: please shipe "tlsh" binary and manpage

[Stefano Zacchiroli]

Package: tlsh-tools
Version: 3.4.4+20151206-1.3+b1
Severity: minor
Tags: patch

Heya,
  it's a bit weird that the main binary for this package is called
"tlsh_unittest". The upstream doc has this to say on the matter:

  Building TLSH (see below) will create a static library in the lib directory,
  and the tlsh executable (a symbolic link to tlsh_unittest).

but that's indeed not true :-). The symbolic link is *not* built and hence not
shipped by the Debian package. But it would be *nice* to ship it! So please
find attached a .links file that, if dropped into the debian/ dir, will make
the tlsh-tools package ship /usr/bin/tlsh (as a symbolic link) and its manpage.

Can you consider applying it?

Thanks a lot for maintaining tlsh in Debian,
Cheers

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

Kernel: Linux 5.4.0-3-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:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tlsh-tools depends on:
ii  libc62.29-10
ii  libgcc-s1 [libgcc1]  10-20200211-1
ii  libgcc1  1:10-20200211-1
ii  libstdc++6   10-20200211-1
ii  libtlsh0 3.4.4+20151206-1.3+b1

tlsh-tools recommends no packages.

tlsh-tools suggests no packages.

-- no debconf information
usr/bin/tlsh_unittest   usr/bin/tlsh
usr/share/man/man1/tlsh_unittest.1  usr/share/man/man1/tlsh.1

Bug#950772: Patch: swupdate: FTBFS during separate arch/indep builds

[Stefano Babic]

Hi Bastian,

On 18.02.20 01:36, Bastian Germann wrote:
> Hi,
> 
> I have created a merge request at
> https://salsa.debian.org/debian/swupdate/merge_requests/2 which fixes
> the issue. Please consider merging and uploading to sid.
> 

Thanks for this - anyway, debian package was officially pushed by SZ Lin
and Nobuhiro (both in CC), I have no write access to that repo.

Stefano



-- 
=
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=

Bug#950853: gffutils tests are timing out with Python 3.8

[Stefano Rivera]

Control: tag -1 + patch

Hi Matthias (2020.02.07_05:18:06_-0800)
> gffutils tests are timing out with Python 3.8, while they succeed when run 
> with
> 3.7.  Currently only seen in an Ubuntu focal environment, however the upstream
> sources don't mention 3.7 and 3.8 at all.

I spent some time debugging this last week, and I *think* the cause is
https://bugs.python.org/issue38501

This patch seems to avoid it: https://github.com/daler/gffutils/pull/155

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#950767: postgresql-11-python3-multicorn: Underlinked when built with Python3.8 as default

[Stefano Rivera]

Package: postgresql-11-python3-multicorn
Version: 1.3.4-31-g9ff7875-2
Severity: normal
Tags: upstream patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

FYI: The multicorn.so PostgreSQL plugin will not be linked to libpython
when built under Python 3.8, without this patch:

https://github.com/Kozea/Multicorn/pull/242

https://docs.python.org/3/whatsnew/3.8.html#debug-build-uses-the-same-abi-as-release-build
 says:

> To embed Python into an application, a new --embed option must be
> passed to python3-config --libs --embed to get -lpython3.8 (link the
> application to libpython). To support both 3.8 and older, try
> python3-config --libs --embed first and fallback to python3-config
> --libs (without --embed) if the previous command fails.

SR

Bug#950672: hy: diff for NMU version 0.17.0-1.1

[Stefano Rivera]

Control: tags 950672 + pending

Dear maintainer,

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

Regards.

SR
diff -Nru hy-0.17.0/debian/changelog hy-0.17.0/debian/changelog
--- hy-0.17.0/debian/changelog	2019-08-19 18:21:26.0 -0700
+++ hy-0.17.0/debian/changelog	2020-02-04 08:40:08.0 -0800
@@ -1,3 +1,10 @@
+hy (0.17.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Support Python 3.8 (Closes: #950672)
+
+ -- Stefano Rivera   Tue, 04 Feb 2020 08:40:08 -0800
+
 hy (0.17.0-1) unstable; urgency=medium
 
   * Update to 0.17.0 upstream release (Closes: #913044, #892264, #913048)
diff -Nru hy-0.17.0/debian/patches/py38.patch hy-0.17.0/debian/patches/py38.patch
--- hy-0.17.0/debian/patches/py38.patch	1969-12-31 16:00:00.0 -0800
+++ hy-0.17.0/debian/patches/py38.patch	2020-02-04 08:40:08.0 -0800
@@ -0,0 +1,53 @@
+Description: Support posonlyargs in Python 3.8
+Author: Kodi Arfer 
+Author: Stefano Rivera 
+Origin: upstream, https://github.com/hylang/hy/commit/ba9b0239c7fa2a02478e8456ed3867c6f2fec0c5
+Origin: upstream, https://github.com/hylang/hy/commit/36708e8e996700da256943b3e8162a29fa381473
+Bug-Debian: https://bugs.debian.org/950672
+
+--- a/hy/compiler.py
 b/hy/compiler.py
+@@ -1145,7 +1145,7 @@
+ expr,
+ name=fname,
+ args=ast.arguments(
+-args=[], vararg=None, kwarg=None,
++args=[], vararg=None, kwarg=None, posonlyargs=[],
+ kwonlyargs=[], kw_defaults=[], defaults=[]),
+ body=f(parts).stmts,
+ decorator_list=[])
+@@ -1524,6 +1524,7 @@
+ args = ast.arguments(
+ args=main_args, defaults=defaults,
+ vararg=rest,
++posonlyargs=[],
+ kwonlyargs=kwonly, kw_defaults=kw_defaults,
+ kwarg=kwargs)
+ 
+--- a/hy/_compat.py
 b/hy/_compat.py
+@@ -37,10 +37,12 @@
+ finally:
+ traceback = None
+ 
+-code_obj_args = ['argcount', 'kwonlyargcount', 'nlocals', 'stacksize',
++code_obj_args = ['argcount', 'posonlyargcount', 'kwonlyargcount', 'nlocals', 'stacksize',
+  'flags', 'code', 'consts', 'names', 'varnames',
+  'filename', 'name', 'firstlineno', 'lnotab', 'freevars',
+  'cellvars']
++if not PY38:
++code_obj_args.remove("posonlyargcount")
+ else:
+ def raise_from(value, from_value=None):
+ raise value
+--- a/tests/native_tests/native_macros.hy
 b/tests/native_tests/native_macros.hy
+@@ -391,7 +391,7 @@
+   ;; Now, let's use a `require`d macro that depends on another macro defined only
+   ;; in this scope.
+   (defmacro local-test-macro [x]
+-(.format "This is the local version of `nonlocal-test-macro` returning {}!" x))
++(.format "This is the local version of `nonlocal-test-macro` returning {}!" (int x)))
+ 
+   (assert (= "This is the local version of `nonlocal-test-macro` returning 3!"
+  (test-module-macro-2 3)))
diff -Nru hy-0.17.0/debian/patches/series hy-0.17.0/debian/patches/series
--- hy-0.17.0/debian/patches/series	2019-08-16 15:57:27.0 -0700
+++ hy-0.17.0/debian/patches/series	2020-02-04 08:15:19.0 -0800
@@ -1 +1,2 @@
 hy-history.patch
+py38.patch

Bug#950481: doit: diff for NMU version 0.31.1-3.2

[Stefano Rivera]

Control: tags 950481 + pending

Dear maintainer,

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

Regards.

SR
diff -Nru doit-0.31.1/debian/changelog doit-0.31.1/debian/changelog
--- doit-0.31.1/debian/changelog	2019-11-15 20:02:13.0 +0100
+++ doit-0.31.1/debian/changelog	2020-02-02 13:23:58.0 +0100
@@ -1,3 +1,10 @@
+doit (0.31.1-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Python 3.8 support. (Closes: #950481)
+
+ -- Stefano Rivera   Sun, 02 Feb 2020 13:23:58 +0100
+
 doit (0.31.1-3.1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru doit-0.31.1/debian/patches/py38 doit-0.31.1/debian/patches/py38
--- doit-0.31.1/debian/patches/py38	1970-01-01 01:00:00.0 +0100
+++ doit-0.31.1/debian/patches/py38	2020-02-02 13:23:58.0 +0100
@@ -0,0 +1,32 @@
+Description: Fix tests under Python 3.8
+ Replace recursive knot with explicitly unpicklable object
+ .
+ Python 3.8 was able to pickle the previously unpicklable. Instead of relying
+ on limits, let's raise an explicit error.
+Bug-Upstream: https://github.com/pydoit/doit/issues/341
+Bug-Debian: https://bugs.debian.org/950481
+Forwarded: https://github.com/pydoit/doit/pull/350
+--- a/tests/test_runner.py
 b/tests/test_runner.py
+@@ -577,17 +577,12 @@
+ t2 = pickle.loads(t1p)
+ assert 4 == t2.actions[0].py_callable()
+ 
+-@pytest.mark.xfail('PLAT_IMPL == "PyPy"')  # pypy can handle it :)
+ def test_not_picklable_raises_InvalidTask(self):
+-# create a large enough recursive obj so pickle fails
+-d1 = {}
+-last = d1
+-for x in range(400):
+-dn = {'p': last}
+-last = dn
+-d1['p'] = last
+-
+ def non_top_function(): pass
++class Unpicklable:
++def __getstate__(self):
++raise pickle.PicklingError("DO NOT PICKLE")
++d1 = Unpicklable()
+ t1 = Task('t1', [non_top_function, (d1,)])
+ pytest.raises(InvalidTask, runner.JobTask, t1)
+ 
diff -Nru doit-0.31.1/debian/patches/series doit-0.31.1/debian/patches/series
--- doit-0.31.1/debian/patches/series	2019-11-15 19:59:07.0 +0100
+++ doit-0.31.1/debian/patches/series	2020-02-02 13:10:15.0 +0100
@@ -1,2 +1,3 @@
 change-pytest-fixture-syntax.patch
 fix-pytest-gte-4-0.patch
+py38

Bug#950481: src:doit: Tests fail on Python 3.8

[Stefano Rivera]

Package: src:doit
Version: 0.31.1-3.1
Severity: normal
Tags: upstream patch

Tests fail under Python 3.8
https://github.com/pydoit/doit/issues/341

I filed this PR upstream, and intend to upload it to Debian:
https://github.com/pydoit/doit/pull/350

SR

Bug#949656: apt-cacher-ng: Doesn't skip over IPv6-only mirrors as it used to

[Stefano Rivera]

Package: apt-cacher-ng
Version: 3.3.1-2
Severity: normal

Since upgrading from 3.2-3 to 3.3.1-2, I couldn't do an "apt update" any
more. It would 502 on the InRelease file.

My backend configuration is:
http://mirror.kardiogramm.net/debian/
http://deb.debian.org/debian/

The first one is my mirror at home, that is only available over IPv6.
On IPv4-only networks, apt-cacher-ng used to just skip over this. Now it
gets stuck on it.

SR

-- Package-specific info:

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

Kernel: Linux 5.4.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_ZA.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 apt-cacher-ng depends on:
ii  adduser  3.118
ii  debconf [debconf-2.0]1.5.73
ii  dpkg 1.19.7
ii  libbz2-1.0   1.0.8-2
ii  libc62.29-9
ii  libevent-2.1-7   2.1.11-stable-1
ii  libevent-pthreads-2.1-7  2.1.11-stable-1
ii  libgcc1  1:9.2.1-22
ii  liblzma5 5.2.4-1+b1
ii  libssl1.11.1.1d-2
ii  libstdc++6   9.2.1-22
ii  libsystemd0  244-3
ii  libwrap0 7.6.q-30
ii  lsb-base 11.1.0
ii  zlib1g   1:1.2.11.dfsg-1+b1

Versions of packages apt-cacher-ng recommends:
ii  ca-certificates  20190110

Versions of packages apt-cacher-ng suggests:
ii  avahi-daemon  0.7-5
ii  doc-base  0.10.9
ii  libfuse2  2.9.9-2

-- Configuration Files:
/etc/apt-cacher-ng/acng.conf changed:
CacheDir: /var/cache/apt-cacher-ng
LogDir: /var/log/apt-cacher-ng
SupportDir: /usr/lib/apt-cacher-ng
Remap-debrep: file:deb_mirror*.gz /debian ; file:backends_debian # Debian 
Archives
Remap-uburep: file:ubuntu_mirrors /ubuntu ; file:backends_ubuntu # Ubuntu 
Archives
Remap-cygwin: file:cygwin_mirrors /cygwin # ; file:backends_cygwin # 
incomplete, please create this file or specify preferred mirrors here
Remap-sfnet:  file:sfnet_mirrors # ; file:backends_sfnet # incomplete, please 
create this file or specify preferred mirrors here
Remap-alxrep: file:archlx_mirrors /archlinux # ; file:backend_archlx # Arch 
Linux
Remap-fedora: file:fedora_mirrors # Fedora Linux
Remap-epel:   file:epel_mirrors # Fedora EPEL
Remap-slrep:  file:sl_mirrors # Scientific Linux
Remap-gentoo: file:gentoo_mirrors.gz /gentoo ; file:backends_gentoo # Gentoo 
Archives
Remap-secdeb: security.debian.org /debian-security ; security.debian.org 
deb.debian.org/debian-security
ReportPage: acng-report.html
ExThreshold: 4
NetworkTimeout: 40
FastTimeout = 4
LocalDirs: acng-doc /usr/share/doc/apt-cacher-ng

/etc/apt-cacher-ng/security.conf [Errno 13] Permission denied: 
'/etc/apt-cacher-ng/security.conf'

-- debconf information:
  apt-cacher-ng/proxy: keep
  apt-cacher-ng/port: keep
  apt-cacher-ng/bindaddress: keep
* apt-cacher-ng/tunnelenable: false
  apt-cacher-ng/cachedir: keep
  apt-cacher-ng/gentargetmode: No automated setup

Bug#940924: python3-rope: the license has been changed without the main author's consent

[Stefano Rivera]

Control: tag -1 - sid
Control: notfound -1 rope/0.14.0-1

Removing sid tag and version, to stop this from blocking unrelated
changes from migrating to testing.

0.14 isn't in Debian yet, and Debian is still declaring the GPLv2+
license. This bug is about future versions.

> As can be seen here[1], the license of this package has been changed from
> GPL to LGPL without the consent of the main author.
> 
> [1] https://github.com/python-rope/rope/pull/266

FWIW, there is no sign of objection, either. And his GH account does
seem active.

Many other projects have successfully relicensed without obtaining
consent from every contributor. However, the vast majority of code here
seems to be copyright Ali Gholami Rudi.

If the Debian maintainer doesn't want to acknowledge this license
change, an easy solution for Debian would be to treat this as being
GPLv3 licensed. That is compatible with the original GPLv2, or later,
license as well as subsequent LGPLv3 changes.

> I don't know, if it is still relevant to keep this orphaned package in
> Debian anymore.

But yeah, if nobody is maintaining it, that's all moot.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#937487: pynag: Python2 removal in sid/bullseye

[Stefano Rivera]

Hi Matthias (2019.08.30_09:34:35_+0200)
> - 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.

Team uploaded 1.1.2+dfsg-1 to experimental, with a new Python 3 package.

The python 2 package is still there, because:

Reverse-Depends
* syslog-nagios-bridge  (for python-pynag)

(That's #945740)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#936505: faulthandler: Python2 removal in sid/bullseye

[Stefano Rivera]

user debian-pyt...@lists.debian.org
usertags 936505 + py2keep
thanks

This is built-in in Python 3, so no porting required. It can die with
Python 2.7.

But it's useful, as long as we have python2.7 in the archive, so I'm
marking this py2keep.

Happy to be overridden on that, if people want to be more aggressive.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#933775: dnsviz: diff for NMU version 0.8.0-1.1

[Stefano Rivera]

Control: tags 933775 + patch
Control: tags 933775 + pending

Dear maintainer,

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

While I was there, I did some bigger cleanup. You can find this all in
https://salsa.debian.org/stefanor/dnsviz

Regards.

SR
diff -Nru dnsviz-0.8.0/debian/changelog dnsviz-0.8.0/debian/changelog
--- dnsviz-0.8.0/debian/changelog	2019-02-04 02:46:32.0 +0200
+++ dnsviz-0.8.0/debian/changelog	2020-01-05 11:36:48.0 +0200
@@ -1,3 +1,11 @@
+dnsviz (0.8.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to Python 3. (Closes: #933775)
+  * Build with pybuild.
+
+ -- Stefano Rivera   Sun, 05 Jan 2020 11:36:48 +0200
+
 dnsviz (0.8.0-1) unstable; urgency=medium
 
   * New upstream version 0.8.0
diff -Nru dnsviz-0.8.0/debian/control dnsviz-0.8.0/debian/control
--- dnsviz-0.8.0/debian/control	2019-02-04 02:46:32.0 +0200
+++ dnsviz-0.8.0/debian/control	2020-01-05 11:36:48.0 +0200
@@ -7,11 +7,11 @@
  debhelper (>= 9~),
  dh-python,
  inkscape,
- python (>= 2.7~),
- python-dnspython (>= 1.13.0~),
- python-libnacl,
- python-m2crypto (>= 0.28.0~),
- python-pygraphviz (>= 1.4~),
+ python3,
+ python3-dnspython (>= 1.13.0~),
+ python3-libnacl,
+ python3-m2crypto (>= 0.28.0~),
+ python3-pygraphviz (>= 1.4~),
 Standards-Version: 4.3.0
 Homepage: https://github.com/dnsviz/dnsviz
 Vcs-Browser: https://salsa.debian.org/dns-team/dnsviz
@@ -21,7 +21,7 @@
 Architecture: all
 Depends:
  ${misc:Depends},
- ${python:Depends},
+ ${python3:Depends},
  dns-root-data,
  libjs-jquery,
  libjs-jquery-ui,
diff -Nru dnsviz-0.8.0/debian/patches/debian-changes dnsviz-0.8.0/debian/patches/debian-changes
--- dnsviz-0.8.0/debian/patches/debian-changes	2019-02-04 02:46:32.0 +0200
+++ dnsviz-0.8.0/debian/patches/debian-changes	2020-01-05 11:36:48.0 +0200
@@ -36,43 +36,3 @@
  
  def apply_substitutions(filename, install_prefix):
  assert filename.endswith('.in'), 'Filename supplied for customization must end with \'.in\': %s' % (filename)
 /dev/null
-+++ dnsviz-0.8.0/dnsviz/config.py
-@@ -0,0 +1,37 @@
-+#
-+# This file is a part of DNSViz, a tool suite for DNS/DNSSEC monitoring,
-+# analysis, and visualization.
-+# Created by Casey Deccio (ca...@deccio.net)
-+#
-+# Copyright 2014-2016 Verisign, Inc.
-+#
-+# Copyright 2016-2019 Casey Deccio
-+#
-+# DNSViz is free software; you can redistribute it and/or modify
-+# it under the terms of the GNU General Public License as published by
-+# the Free Software Foundation; either version 2 of the License, or
-+# (at your option) any later version.
-+#
-+# DNSViz is distributed in the hope that it will be useful,
-+# but WITHOUT ANY WARRANTY; without even the implied warranty of
-+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-+# GNU General Public License for more details.
-+#
-+# You should have received a copy of the GNU General Public License along
-+# with DNSViz.  If not, see <http://www.gnu.org/licenses/>.
-+#
-+
-+from __future__ import unicode_literals
-+
-+import os
-+import sys
-+
-+if hasattr(sys, 'real_prefix'):
-+DNSVIZ_INSTALL_PREFIX = sys.prefix
-+else:
-+DNSVIZ_INSTALL_PREFIX = ''
-+DNSVIZ_SHARE_PATH = os.path.join(DNSVIZ_INSTALL_PREFIX, 'share', 'dnsviz')
-+JQUERY_PATH = 'file:///usr/share/javascript/jquery/jquery.min.js'
-+JQUERY_UI_PATH = 'file:///usr/share/javascript/jquery-ui/jquery-ui.min.js'
-+JQUERY_UI_CSS_PATH = 'file:///usr/share/javascript/jquery-ui-themes/redmond/jquery-ui.css'
-+RAPHAEL_PATH = 'file:///usr/share/javascript/raphael/raphael.min.js'
diff -Nru dnsviz-0.8.0/debian/rules dnsviz-0.8.0/debian/rules
--- dnsviz-0.8.0/debian/rules	2019-02-04 02:46:32.0 +0200
+++ dnsviz-0.8.0/debian/rules	2020-01-05 11:36:48.0 +0200
@@ -1,6 +1,6 @@
 #!/usr/bin/make -f
 %:
-	dh $@ --with python2
+	dh $@ --with python3 --buildsystem pybuild
 
 override_dh_auto_build:
 	$(MAKE) -C doc icons

Bug#914569: beets: zsh completion broken

[Stefano Rivera]

Control: tag -1 +moreinfo +unreproducible

Hi Clint (2018.11.25_05:15:04_+0200)
> % beet import ../
> _beet:zregexparse:4: invalid regex : )
> (with zsh 5.6.2-3)

Works for me, with zsh 5.7.1-1+b1.

Something changed in zsh? Or something unusual about the directory you
were in?

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#946561: Bug #946561

[Stefano F.]

Just to simplify your check try:
piuparts --docker-image debian:experimental -d experimental -a hplip python3
It fails cause: "The following packages have unmet dependencies:
hplip : Depends: python3 (< 3.8) but 3.8.0-2 is to be installed"

Then if you just try to rebuild in this context with debuild -b -uc -us:
It fails to build cause hplip used improper way of checking python
usability which worked  until python38 - start to include python in
spec file.

See [1] cause we had the same include upstream issues.

[1]https://bugzilla.redhat.com/show_bug.cgi?id=1706233

Il giorno ven 13 dic 2019 alle ore 16:50 Didier 'OdyX' Raboud
 ha scritto:
>
> Control: severity -1 important
> Control: tags -1 +moreinfo
>
> Le mercredi, 11 décembre 2019, 21.04:58 h CET Stefano Fabri a écrit :
> > Try to apt-get install hplip when you have in the system python >=3.8
> > (https://packages.debian.org/experimental/python3).
> >
> > In this status hplip is not installable.
>
> Well. Your bugreport still is not actionable for me as maintainer. What do you
> see on-screen when you do this installation combination (ideally in a
> terminal)? When you say "not installable", what exactly do you mean?
>
> OdyX

Bug#946561: Bug #946561

[Stefano Fabri]

Try to apt-get install hplip when you have in the system python >=3.8
(https://packages.debian.org/experimental/python3).

In this status hplip is not installable.

Bug#946561: hplip: Not installable with python3 >= 3.8

[Stefano F.]

Package: hplip
Severity: grave
Justification: renders package unusable

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

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

Versions of packages hplip depends on:
ii  adduser3.118
ii  cups   2.3.0-7
pn  hplip-data 
ii  libc6  2.29-6
ii  libcups2   2.3.0-7
ii  libdbus-1-31.12.16-2
ii  libhpmud0  3.19.11+dfsg0-1
ii  libpython3.7   3.7.5-2
ii  libsane1.0.27-3.2+b1
pn  libsane-hpaio  
ii  lsb-base   11.1.0
ii  printer-driver-hpcups  3.19.11+dfsg0-1
ii  python33.8.0-2
ii  python3-dbus   1.2.14-1
ii  python3-gi 3.34.0-3
pn  python3-pexpect
pn  python3-pil
pn  python3-reportlab  
ii  wget   1.20.3-1+b2
ii  xz-utils   5.2.4-1+b1

Versions of packages hplip recommends:
ii  avahi-daemon  0.7-4+b1
ii  policykit-1   0.105-26
ii  printer-driver-postscript-hp  3.19.11+dfsg0-1
ii  sane-utils1.0.27-3.2+b1

Versions of packages hplip suggests:
pn  hplip-doc  
pn  hplip-gui  
pn  python3-notify2
ii  system-config-printer  1.5.12-1

Bug#937815: [Python-modules-team] Processed: Bug#937815 marked as pending in python-html2text

[Stefano Rivera]

Control: untag -1 pending

Hi Sandro (2019.10.04_18:58:17_+0200)
> there are still reverse dependencies:
> http://sandrotosi.me/debian/py2removal/python-html2text_1.svg

It's in a branch, not master.
https://salsa.debian.org/python-team/modules/python-html2text/compare/master...python3

Upstream released a new version, it's py3, only. So, stuffed the new
version in a "python3" branch to remind myself that it's not uploadable.

So no, not *actually* pending.
Let's revert the bot's work.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#939598: marked as done (libubootenv-tool: trying to overwrite '/usr/bin/fw_printenv', which is also in package u-boot-tools 2019.01+dfsg-7)

[Stefano Babic]

Hi Vagrant,

On 21/09/19 23:49, Vagrant Cascadian wrote:
>> Preparing to unpack .../15-libubootenv-tool_0.1-1_amd64.deb ...
>> Unpacking libubootenv-tool (0.1-1) ...
>> dpkg: error processing archive 
>> /tmp/apt-dpkg-install-S5V5yb/15-libubootenv-tool_0.1-1_amd64.deb (--unpack
>> ):
>>  trying to overwrite '/usr/bin/fw_printenv', which is also in package 
>> u-boot-tools 2019.01+dfsg-7
>>
>> Since the packages are both u-boot related, the new program might have
>> the same functionality as the existing one and hence using
>> update-alternatives for the two variants maybe an option.
> ...
>>  libubootenv (0.1-2) unstable; urgency=medium
>>  .
>>* Add u-boot-tools Conflicts of libubootenv-tool (Closes: #939598)
> 
> This seems like a rather sub-optimal solution to the problem; now it's
> impossible to install u-boot-tools at the same time, which has other
> functionality as well. There are also packages that depend or recommend
> on u-boot-tools that won't be able to be installed or may have reduced
> functionality when libubootenv-tool is installed.
> 
> Many of these packages would seem quite reasonable to have installed
> with both libubootenv-tool and u-boot-tools installed at the same
> time, such as u-boot-sunxi...

Right, but it looks like that u-boot-tools contains tools with different
meaning that could be addressed with different packages. For example,
tools like "netconsole" is missing. The package in libubootenv exposes
the "envtools" from U-Boot, that is just the tool to modify the environment.

> 
> Is there anything in the libubootenv's fw_printenv and fw_setenv
> implementations that's significantly different from u-boot-tools?

>From the user point of view, they are thought to be fully compatible.
The syntax for the tool is the same as the original tools to avoid
breakages in already implemented script. Anyway, the most important
difference (at least for Debian) is the tools are hardware unaware.

In fact, the original u-boot-tools must be compiled with the same
machine (_defconfig) of the bootloader because the environment is
statically linked to the binary. This is a severe issue if a board boots
with the "default" environment, that is the environment linked together
with the bootloader. The original fw_setenv tool is built just one
machine: fw_setenv can brick the target because it cannot know the
environment because it was not written to the flash and it is only
present in the U-Boot binary. There is no way to instruct the original
tool for this. With libubootenv, the environment is read from a file and
the same binary can be used on different targets without exceptions.

The original discussion about this topic was in this old thread on
U-Boot's ML:
http://u-boot.10912.n7.nabble.com/SWUpdate-U-Boot-environment-library-dependency-td340530.html

Apart of this, libubootenv just addresses "envtools" from U-Boot, while
u-boot-tools contains tools for different purposes: image generation
(mkimage and friends), environment.

My logical way to do is to split u-boot-tools in several sub-packages
that won't conflict. This is the solution in OE, too, where a
u-boot-mkimage package contains the image generation tool and
u-boot-fw-utils contains the envtools. In OE libubootenv is set as
replacement for u-boot-fw-utils (with PROVIDES) and there is no conflict.

> 
> Couldn't libubootenv-tool depend on u-boot-tools instead of conflicting
> with it?

Depend ? No.

>  Or would it make sense for u-boot-tools to depend on
> libubootenv-tool instead?

Mmhh.. I do not know. u-boot-tools should not install fw_setenv /
fw_printenv is libubootenv is already installed.

> Is this likely to be merged in upstream u-boot
> at some point?

No. libubootenv is also thought to remove some limitations due to the
U-Boot build environment. U-Boot cannot use standard library as they
are, so code from libraries (libz, openssl, and so on..) is copied from
the original library into U-Boot. If this is required for the bootloader
that is an independent binary not linked with anything, it is a
sub-optimal solution for a User Space tool: libubootenv is simply linked
against the required libraries.

> 
> Alternately, the original suggestion of using the alternatives system
> would at least allow both packages to coexist at the same time, at the
> cost of some additional complication in both packages maintainer
> scripts.

Best regards,
Stefano
-- 
=
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=

Bug#938168: python-setuptools: Python2 removal in sid/bullseye

[Stefano Rivera]

user debian-pyt...@lists.debian.org
usertags 938168 + py2keep
thanks

I think it would make sense to keep setuptools alive on 2.7 and pypy,
until they are removed.

And we need a python2.7 interpreter (ideally both cpython and pypy) to
build pypy3.

So, I suggest keeping these.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#939457: lxml breaks beautifulsoup4 autopkgtest: a real XHTML didn't come out *exactly* the same as it went in

[Stefano Rivera]

Hi Paul (2019.09.05_04:56:41_-0300)

Fixed upstream in beautifulsoup4, upload incoming.

https://bugs.launchpad.net/beautifulsoup/+bug/1840141

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#927147: requestsync: Please port to python3

[Stefano Rivera]

Control: tag 927147 pending

Thanks for the patch. I'm starting a python3 porting branch. And hope to
finish it in a day or two.

https://code.launchpad.net/~ubuntu-dev/ubuntu-dev-tools/+git/ubuntu-dev-tools/+ref/python3

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#938249: python-virtualenv: Python2 removal in sid/bullseye

[Stefano Rivera]

user debian-pyt...@lists.debian.org
usertags 938249 + py2keep
thanks

I think we should keep virtualenv, as long a we have the interpreter.

It definitely qualifies via popcon :P

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#937815: python-html2text: Python2 removal in sid/bullseye

[Stefano Rivera]

Control: block 937815 with 936270 935358

Happy to remove, but there are reverse-deps:

Reverse-Recommends
==
* sat-xmpp-core

Reverse-Depends
===
* calibre

Reverse-Build-Depends
=
* calibre

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#937762: python-flexmock: Python2 removal in sid/bullseye

[Stefano Rivera]

Control: block 937762 with 937232 938191 938676

Happy to, but there are some reverse-deps to deal with, first:

Reverse-Depends
===
* paleomix

Reverse-Build-Depends-Indep
===
* python-sqlalchemy-utils

Reverse-Build-Depends
=
* paleomix
* tomahawk

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#937411: pycparser: Python2 removal in sid/bullseye

[Stefano Rivera]

user debian-pyt...@lists.debian.org
usertags 937411 + py2keep
thanks

python-pycparser is needed to translate pypy and pypy3 on cPython.

We do this when bootstrapping pypy, and on architectures that pypy
doesn't have JIT support for.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#937510: pypy3: Python2 removal in sid/bullseye

[Stefano Rivera]

Hi 937510 (2019.08.31_10:24:30_-0300)

> The rpython source code of PyPy is Python 2. So, Python 2 sphinx is used
> for building autodoc. I haven't tried python 3 sphinx, it may work.

Confirmed that it doesn't:
Running Sphinx v1.8.5

Exception occurred:
  File "/<>/pypy3-7.1.1+dfsg/pypy/doc/config/generate.py", line 2, in 

from pypy.config import pypyoption, makerestdoc
  File "/<>/pypy3-7.1.1+dfsg/pypy/config/pypyoption.py", line 322
print config.getpaths()
   ^
SyntaxError: invalid syntax

We could do work to make everything imported by sphinx, importable under
python 3, but this isn't a use-case upstream needs to support, so I
suspect we'd be the ones maintaining this.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#937639: python-cffi: Python2 removal in sid/bullseye

[Stefano Rivera]

Control: block 937639 with 936262 937809 936555 937889 938195 938729 938622 
936643 937499 937540 937602 937672 937784 937889 937937 938272 938273 938310 
938840

Happy to, but there are many reverse-deps. Probably going to take a
while to get them all ported.

Reverse-Depends
===
* python-cairocffi
* python-hidapi
* python-ipalib
* python-librtmp
* python-ssdeep
* python-twext
* tahoe-lafs

Reverse-Build-Depends
=
* cairocffi
* gphoto2-cffi
* hidapi-cffi
* pyopenssl
* pysoundfile
* python-bcrypt
* python-cryptography
* python-gevent
* python-librtmp
* python-nacl
* python-ssdeep
* python-xattr
* python-xeddsa
* pyzmq
* xcffib

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#937549: pystemmer: Python2 removal in sid/bullseye

[Stefano Rivera]

Control: block 937549 with 938426 938528 883146

Happy to, but there are still a couple of reverse-deps:

Reverse-Depends
===
* python-stemmer-dbg
* sagemath [amd64 arm64 armhf i386 ppc64el]

Reverse-Build-Depends-Indep
===
* sphinx

Reverse-Build-Depends
=
* bzr
* sagemath

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#936325: configobj: Python2 removal in sid/bullseye

[Stefano Rivera]

Control: block 936325 with 936221 936394 936460 938945 936996 937330 937336 
937577 936237 883146 939024 938425 938623 938728

Happy to do that, but there are a good handful of reverse-deps:

Reverse-Depends
===
* blueproximity
* diamond
* dynagen
* gtg
* mayavi2
* psychopy
* puddletag
* python-apptools
* python-breezy
* python-bzrlib
* python-diamond
* rabbitvcs-core
* sabnzbdplus
* tails-installer
* turnin-ng

Reverse-Build-Depends
=
* breezy
* bzr
* diamond
* psychopy
* python-apptools

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#936196: webcheck: Python2 removal in sid/bullseye

[Stefano Rivera]

Control: block 936196 with 934876 936153 936270 936596 936641 936790 936835 
936973 937236 936678 937850 937965 937967 938006 934852 938575 938718 938816 
939259 939260

There are quite a few reverse-dependencies that need to be removed
first, and this library is quite popular in its own right.

Reverse-Recommends
==
* gourmet
* python-gumbo
* python-lxml
* python-pandas
* python-seaborn
* python-translate
* webcheck
* websploit

Reverse-Depends
===
* archmage
* calibre
* geneagrapher
* keysync
* ledger-autosync
* python-jenkinsapi
* python-ofxclient
* python-ofxparse
* python-pattern
* python-subliminal
* python-webtest

Reverse-Build-Depends-Indep
===
* ledger-autosync
* translate-toolkit

Reverse-Build-Depends
=
* aseba-plugin-blockly
* calibre
* geneagrapher
* lxml
* pandas
* python-ofxclient
* python-ofxparse
* python-pattern
* soupsieve

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#938518: soupsieve: Python2 removal in sid/bullseye

[Stefano Rivera]

Control: block 938518 with 936196

Happy to remove, but bs4 depends on it, and many things still depend on
bs4.

Reverse-Depends
===
* python-bs4

Reverse-Build-Depends
=
* beautifulsoup4

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#938755: unidecode: Python2 removal in sid/bullseye

[Stefano Rivera]

block 938755 with 937318 938044
thanks

No objection, but there are reverse-deps:

Reverse-Depends
===
* python-preggy
* python-pretty-yaml

Reverse-Build-Depends
=
* preggy
* python-pretty-yaml

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#938254: python-wadllib: Python2 removal in sid/bullseye

[Stefano Rivera]

Happy to remove. There are still reverse-dependencies:

Reverse-Depends
===
* python-launchpadlib
* python-lazr.restfulclient

Reverse-Build-Depends
=
* python-launchpadlib

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#937511: pypy: Python2 removal in sid/bullseye

[Stefano Rivera]

user debian-pyt...@lists.debian.org
usertags 937511 py2keep
thanks

PyPy is a Python 2 interpreter. It's useful for building PyPy3. It does
this faster, and with less memory, than cPython on platforms that it has
JIT for.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#937510: pypy3: Python2 removal in sid/bullseye

[Stefano Rivera]

user debian-pyt...@lists.debian.org
usertags 937510 py2keep
thanks

The rpython source code of PyPy is Python 2. So, Python 2 sphinx is used
for building autodoc. I haven't tried python 3 sphinx, it may work. The
docs could also be omitted.

However: Python 2.7 (cpython or pypy) is used for building pypy3.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#936824: lazr.uri: Python2 removal in sid/bullseye

[Stefano Rivera]

Happy to remove, but there are still reverse-dependencies:

Reverse-Depends
===
* python-launchpadlib
* python-lazr.restfulclient
* python-wadllib

Reverse-Build-Depends
=
* python-wadllib

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#936822: lazr.restfulclient: Python2 removal in sid/bullseye

[Stefano Rivera]

Happy to remove, but there are reverse-dependencies:

Reverse-Depends
===
* python-launchpadlib
* ubuntu-dev-tools

Reverse-Build-Depends
=
* python-launchpadlib

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#932821: pypy: Drop PyPy

[Stefano Rivera]

Hi Ondřej (2019.07.23_13:43:02_-0300)
> please drop the PyPy package, it's Python 2.7 based and unsupported.

Gonna need PyPy / cpython2.7 to build PyPy3 (the source is Python 2.7).
We use PyPy on archs that PyPy has JIT support for. It reduced memory
usage and build time.

The upstream is going to continue to build and support PyPy for the
forseeable future. They aren't contemplating a port to python3, for the
rpython side, yet.

My understanding from the Python BoF was that we'd stop packaging random
modules for pypy, but not that pypy would go away.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#931659: transition: rm python2

[Stefano Rivera]

The current regex is using \bpython, which matches dh-python.

I suggest this patch, using \s instead.

Gets us down to 3455/4057.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272
diff --git a/config/ongoing/python2-rm.ben b/config/ongoing/python2-rm.ben
index ca4b33d..60d928c 100644
--- a/config/ongoing/python2-rm.ben
+++ b/config/ongoing/python2-rm.ben
@@ -1,6 +1,6 @@
 title = "python2-rm";
 notes = "Python 2 removal tracker (#931659)";
-is_affected = .depends ~ /\b(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)\b/ | .build-depends ~ /\b(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)\b/;
-is_bad = .depends ~ /\b(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)\b/ | .build-depends ~ /\b(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)\b/;
+is_affected = .depends ~ /\s(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)\b/ | .build-depends ~ /\s(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)\b/;
+is_bad = .depends ~ /\s(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)\b/ | .build-depends ~ /\s(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)\b/;
 is_good = .depends ~ "''";
 

Bug#907041: ITP: swupdate -- SWUpdate provides a reliable way to update the software on an embedded system

[Stefano Babic]

Hi Shyam,

On 12/07/19 13:53, Shyam Saini wrote:
> Hi,
> 
> Is there any update on this?
> 
> Any tentative date or time when It could be officially added.
> 
> We need swupdate as official debian package for one of our customer.
> If it would not be added in next few months then we would probably
> like to use swupdate with yocto.
> 

The package was pushed by SZ (see link) to debian and he expects it will
be merged sonn, now that "buster" is released.

[1] https://ftp-master.debian.org/new.html

Anyway, (not yet merged) packages are available. You can use the link
above, or SWUpdate has a -debian branch to build the package on your own.

>  please let us me know about the status so that we can make our
> decision accordingly.

Weird, decision to take debian or Yocto should not be based on
SWUpdate's availability.

Best regards,
Stefano Babic


-- 
=
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=

Bug#931550: bastet: Score names get changed on game load

[Stefano Gandelli]

Package: bastet
Version: 0.43-5+b1
Severity: minor

Dear Maintainer,

While playing the game I noticed that the highscore
names get changed every time the game is restarted.
In particular, if I have 'stefano' as a highscore
entry and I exit and then re-enter the game, then the
entry get changed to '"stefano"'. Repeating the process
produce '""stefano""', then '"""stefano"""' and so on,
and this happens for every entry in the high score list.


Stefano Gandelli

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

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

Versions of packages bastet depends on:
ii  debconf [debconf-2.0]   1.5.72
ii  libboost-program-options1.67.0  1.67.0-13
ii  libc6   2.28-7
ii  libgcc1 1:8.3.0-7
ii  libncurses6 6.1+20181013-2
ii  libstdc++6  8.3.0-7
ii  libtinfo6   6.1+20181013-2

bastet recommends no packages.

bastet suggests no packages.

Bug#930536: unblock: distro-info-data/0.41

[Stefano Rivera]

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

Please unblock package distro-info-data

This is a pure-data package, tracking Debian and Ubuntu releases. As the
release date is now known, it needs an update.

Since the last update, the most recent Ubuntu release has also received
an animal name, so that is included, too.

unblock distro-info-data/0.41

Thanks,

SR

diff -Nru distro-info-data-0.40/debian/changelog 
distro-info-data-0.41/debian/changelog
--- distro-info-data-0.40/debian/changelog  2019-04-23 12:14:38.0 
-0700
+++ distro-info-data-0.41/debian/changelog  2019-06-14 10:50:04.0 
-0700
@@ -1,3 +1,11 @@
+distro-info-data (0.41) unstable; urgency=medium
+
+  * Add final animal name for Ubuntu 19.10 Eoan Ermine.
+  * Set release date for Buster (and matching creation date for Bullseye).
+It has been announced.
+
+ -- Stefano Rivera   Fri, 14 Jun 2019 10:50:04 -0700
+
 distro-info-data (0.40) unstable; urgency=medium
 
   * Correct EOL date for trusty. (LP: #1825553)
diff -Nru distro-info-data-0.40/debian.csv distro-info-data-0.41/debian.csv
--- distro-info-data-0.40/debian.csv2019-04-23 12:14:38.0 -0700
+++ distro-info-data-0.41/debian.csv2019-06-14 10:50:04.0 -0700
@@ -13,8 +13,8 @@
 7,Wheezy,wheezy,2011-02-06,2013-05-04,2016-04-26
 8,Jessie,jessie,2013-05-04,2015-04-25,2018-06-06
 9,Stretch,stretch,2015-04-25,2017-06-17
-10,Buster,buster,2017-06-17
-11,Bullseye,bullseye,2019-08-01
+10,Buster,buster,2017-06-17,2019-07-06
+11,Bullseye,bullseye,2019-07-06
 12,Bookworm,bookworm,2021-08-01
 ,Sid,sid,1993-08-16
 ,Experimental,experimental,1993-08-16
diff -Nru distro-info-data-0.40/ubuntu.csv distro-info-data-0.41/ubuntu.csv
--- distro-info-data-0.40/ubuntu.csv2019-04-23 12:14:38.0 -0700
+++ distro-info-data-0.41/ubuntu.csv2019-06-14 10:50:04.0 -0700
@@ -29,4 +29,4 @@
 18.04 LTS,Bionic Beaver,bionic,2017-10-19,2018-04-26,2023-04-26
 18.10,Cosmic Cuttlefish,cosmic,2018-04-26,2018-10-18,2019-07-18
 19.04,Disco Dingo,disco,2018-10-18,2019-04-18,2020-01-18
-19.10,Eoan EANIMAL,eoan,2019-04-18,2019-10-17,2020-07-17
+19.10,Eoan Ermine,eoan,2019-04-18,2019-10-17,2020-07-17

Bug#928073: unblock: beancount/2.2.0-3

[Stefano Zacchiroli]

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

Please unblock package beancount

Santiago Villa has discovered an unpredictability in the cleanup of a gnupg
socket file, which might randomly make the package FTBFS. The version I've just
uploaded to unstable includes a patch by Santiago that fixes this. It would be
nice to have this fix in testing, to make rebuilding the next stable release
more predicatble.

debdiff attached.

unblock beancount/2.2.0-3

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru beancount-2.2.0/debian/changelog beancount-2.2.0/debian/changelog
--- beancount-2.2.0/debian/changelog2019-01-14 10:01:37.0 +0100
+++ beancount-2.2.0/debian/changelog2019-04-21 17:00:36.0 +0200
@@ -1,3 +1,11 @@
+beancount (2.2.0-3) unstable; urgency=medium
+
+  [ Santiago Vila ]
+  * patches/0003: Ignore FileNotFoundError from self.tmpdir.cleanup().
+Fixes a FTBFS problem which happens randomly (Closes: #923606)
+
+ -- Stefano Zacchiroli   Sun, 21 Apr 2019 17:00:36 +0200
+
 beancount (2.2.0-2) unstable; urgency=medium
 
   * rules: do not ship *.picklecache files with Python examples (fixes
diff -Nru 
beancount-2.2.0/debian/patches/0003-Ignore-FileNotFoundError-from-self.tmpdir.cleanup.patch
 
beancount-2.2.0/debian/patches/0003-Ignore-FileNotFoundError-from-self.tmpdir.cleanup.patch
--- 
beancount-2.2.0/debian/patches/0003-Ignore-FileNotFoundError-from-self.tmpdir.cleanup.patch
 1970-01-01 01:00:00.0 +0100
+++ 
beancount-2.2.0/debian/patches/0003-Ignore-FileNotFoundError-from-self.tmpdir.cleanup.patch
 2019-04-21 17:00:36.0 +0200
@@ -0,0 +1,18 @@
+From: Santiago Vila 
+Date: Sun, 21 Apr 2019 16:48:40 +0200
+Subject: Ignore FileNotFoundError from self.tmpdir.cleanup()
+
+--- a/beancount/utils/encryption_test.py
 b/beancount/utils/encryption_test.py
+@@ -98,7 +98,10 @@
+ self.run_gpg('--import', stdin=TEST_SECRET_KEY.encode('ascii'))
+ 
+ def tearDown(self):
+-self.tmpdir.cleanup()
++try:
++self.tmpdir.cleanup()
++except FileNotFoundError:
++pass
+ 
+ def run_gpg(self, *args, **kw):
+ command = ('gpg',
diff -Nru beancount-2.2.0/debian/patches/series 
beancount-2.2.0/debian/patches/series
--- beancount-2.2.0/debian/patches/series   2019-01-14 10:01:37.0 
+0100
+++ beancount-2.2.0/debian/patches/series   2019-04-21 17:00:36.0 
+0200
@@ -1,2 +1,3 @@
 0001-Remove-fonts.googleapis.com-links-for-the-bean-web-t.patch
 0002-make-test_version-more-lax-to-accept-non-git-hg-vers.patch
+0003-Ignore-FileNotFoundError-from-self.tmpdir.cleanup.patch

Bug#923606: beancount: FTBFS randomly (gpg-related race condition)

[Stefano Zacchiroli]

On Sun, Apr 21, 2019 at 05:52:36PM +0200, Santiago Vila wrote:
> In other words: My "merge request" is below.

Thanks Santiago, patch applied --- both in the master branch in git and
in a dedicated minimal upload targeting sid. I'll request an unblock as
soon as the upload hits the archive.

Cheers
-- 
Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »


signature.asc
Description: PGP signature