Bug#972907: astra-toolbox ftbfs with python3.9

[Matthias Klose]

Package: src:astra-toolbox
Version: 3.7.4-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

astra-toolbox ftbfs with python3.9; to reproduce, you can use the repositories
found at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/astra-toolbox_1.8.3-2build1_amd64-2020-10-25T06:33:59Z.build

[...]
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/log.py to
log.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/pythonutils.py
to pythonutils.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/matrix.py
to matrix.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/plugins/sirt.py
to sirt.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/plugins/__init__.py
to __init__.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/plugins/cgls.py
to cgls.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/data3d.py
to data3d.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/functions.py
to functions.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/data2d.py
to data2d.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/__init__.py
to __init__.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/tests.py
to tests.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/creators.py
to creators.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/algorithm.py
to algorithm.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/matlab.py
to matlab.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/projector3d.py
to projector3d.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/optomo.py
to optomo.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/projector.py
to projector.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/plugin.py
to plugin.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/astra.py
to astra.cpython-39.pyc
running install_egg_info
Writing
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra_toolbox-1.8.3-py3.9.egg-info
make[2]: Leaving directory '/<>/build-python'
find debian/python3-astra-toolbox -name __pycache__ -depth -exec rm -fr {} \;
mkdir -p debian/python3-astra-toolbox/usr/lib/python3
mv debian/python3-astra-toolbox/usr/lib/python3.8/site-packages
debian/python3-astra-toolbox/usr/lib/python3/dist-packages
mv: cannot stat 'debian/python3-astra-toolbox/usr/lib/python3.8/site-packages':
No such file or directory
make[1]: *** [debian/rules:41: override_dh_auto_install] Error 1

Bug#972908: ceph fbfs with python3.9

[Matthias Klose]

Package: src:ceph
Version: 14.2.9-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

ceph ftbfs with python3.9; to reproduce, you can use the repositories found at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/ceph_14.2.9-1build1_amd64-2020-10-24T18:28:45Z.build

[...]
In file included from /<>/src/common/bit_str.cc:14:
/<>/src/common/bit_str.h:23:13: error: variable or field
‘print_bit_str’ declared void
   23 | extern void print_bit_str(
  | ^
/<>/src/common/bit_str.h:24:5: error: ‘uint64_t’ was not
declared in this scope; did you mean ‘u_int64_t’?
   24 | uint64_t bits,
  | ^~~~
  | u_int64_t
/<>/src/common/bit_str.h:25:10: error: ‘ostream’ is not a
member of ‘std’
   25 | std::ostream &out,
  |  ^~~
/<>/src/common/bit_str.h:18:1: note: ‘std::ostream’ is defined
in header ‘’; did you forget to ‘#include ’?
   17 | #include 
  +++ |+#include 
   18 |
/<>/src/common/bit_str.h:25:19: error: ‘out’ was not declared
in this scope
   25 | std::ostream &out,
  |   ^~~
/<>/src/common/bit_str.h:26:5: error: expected primary-expression
before ‘const’
   26 | const std::function &func,
  | ^
/<>/src/common/bit_str.h:27:5: error: expected primary-expression
before ‘bool’
   27 | bool dump_bit_val = false);
  | ^~~~
/<>/src/common/bit_str.h:29:13: error: variable or field
‘dump_bit_str’ declared void
   29 | extern void dump_bit_str(
  | ^~~~
/<>/src/common/bit_str.h:30:5: error: ‘uint64_t’ was not
declared in this scope; did you mean ‘u_int64_t’?
   30 | uint64_t bits,
  | ^~~~
  | u_int64_t
/<>/src/common/bit_str.h:31:21: error: expected primary-expression
before ‘*’ token
   31 | ceph::Formatter *f,
  | ^
/<>/src/common/bit_str.h:31:22: error: ‘f’ was not declared in
this scope
   31 | ceph::Formatter *f,
  |  ^
/<>/src/common/bit_str.h:32:5: error: expected primary-expression
before ‘const’
   32 | const std::function &func,
  | ^
/<>/src/common/bit_str.h:33:5: error: expected primary-expression
before ‘bool’
   33 | bool dump_bit_val = false);
  | ^~~~
make[3]: *** [src/common/CMakeFiles/common-common-objs.dir/build.make:449:
src/common/CMakeFiles/common-common-objs.dir/bit_str.cc.o] Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'

Bug#972909: insighttoolkit4 ftbfs with python3.9

[Matthias Klose]

Package: src:insighttoolkit4
Version: 14.2.9-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

insighttoolkit4 ftbfs with python3.9; to reproduce, you can use the repositories
found at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/insighttoolkit4_4.13.3withdata-dfsg1-2build1_amd64-2020-10-24T20:38:28Z.build

although I'm unsure if there's something python3.9 related...

Bug#972910: lasagne ftbfs with python3.9

[Matthias Klose]

Package: src:lasagne
Version: 0.1+git20200419.5d3c63c+ds-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

lasagne ftbfs with python3.9; to reproduce, you can use the repositories found 
at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/lasagne_0.1+git20200419.5d3c63c+ds-1build1_amd64-2020-10-24T09:30:12Z.build

[...]
 ERRORS 
_ ERROR at setup of TestGetOutput_MergeLayer.test_get_output_without_arguments _

self = 

@pytest.fixture
def layers(self):
from lasagne.layers.base import Layer, MergeLayer
from lasagne.layers.input import InputLayer
# create two mocks of the same attributes as an InputLayer instance
l1 = [Mock(InputLayer((None,)), output_shape=(None,),
   get_output_kwargs=[]),
  Mock(InputLayer((None,)), output_shape=(None,),
   get_output_kwargs=[])]
# create two mocks of the same attributes as a Layer instance
l2 = [Mock(Layer(l1[0]), output_shape=(None,),
   get_output_kwargs=[]),
  Mock(Layer(l1[1]), output_shape=(None,),
   get_output_kwargs=[])]
# link them to the InputLayer mocks
l2[0].input_layer = l1[0]
l2[1].input_layer = l1[1]
# create a mock that has the same attributes as a MergeLayer
>   l3 = Mock(MergeLayer(l2), get_output_kwargs=['kwarg'])

lasagne/tests/layers/test_helper.py:306:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/mock/mock.py:1082: in __init__
_safe_super(CallableMixin, self).__init__(
/usr/lib/python3/dist-packages/mock/mock.py:439: in __init__
self._mock_add_spec(spec, spec_set, _spec_as_instance, _eat_self)
/usr/lib/python3/dist-packages/mock/mock.py:494: in _mock_add_spec
if iscoroutinefunction(getattr(spec, attr, None)):
lasagne/layers/base.py:269: in output_shape
shape = self.get_output_shape_for(self.input_shapes)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = 
input_shapes = [(None,), (None,)]

def get_output_shape_for(self, input_shapes):
"""
Computes the output shape of this layer, given a list of input shapes.

Parameters
--
input_shape : list of tuple
A list of tuples, with each tuple representing the shape of one of
the inputs (in the correct order). These tuples should have as many
elements as there are input dimensions, and the elements should be
integers or `None`.

Returns
---
tuple
A tuple representing the shape of the output of this layer. The
tuple has as many elements as there are output dimensions, and the
elements are all either integers or `None`.

Notes
-
This method must be overridden when implementing a new
:class:`Layer` class with multiple inputs. By default it raises
`NotImplementedError`.
"""
>   raise NotImplementedError
E   NotImplementedError

Bug#972912: ldb ftbfs with python3.9

[Matthias Klose]

Package: src:ldb
Version: 2.1.4-2
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

ldb ftbfs with python3.9; to reproduce, you can use the repositories found at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/ldb_2.1.4-2build1_amd64-2020-10-25T18:36:18Z.build

[...]
dh_makeshlibs -Xldb. -ppython3-ldb -- -c4
dpkg-gensymbols: error: new libraries appeared in the symbols file:
libpyldb-util.cpython-39-x86-64-linux-gnu.so.2
dpkg-gensymbols: error: some libraries disappeared in the symbols file:
libpyldb-util.cpython-38-x86-64-linux-gnu.so.2
dpkg-gensymbols: warning: debian/python3-ldb/DEBIAN/symbols doesn't match
completely debian/python3-ldb.symbols.amd64
--- debian/python3-ldb.symbols.amd64 (python3-ldb_2:2.1.4-2build1_amd64)
+++ dpkg-gensymbolsDn1MuN   2020-10-25 18:40:30.188308298 +
@@ -1,63 +1,63 @@
-libpyldb-util.cpython-38-x86-64-linux-gnu.so.2 python3-ldb #MINVER#
-
PYLDB_UTIL.CPYTHON_38_X86_64_LINUX_GNU_2.1.4@PYLDB_UTIL.CPYTHON_38_X86_64_LINUX_GNU_2.1.4
2:2.1.4
- PYLDB_UTIL_1.1.10@PYLDB_UTIL_1.1.10 2:2.0.7
- PYLDB_UTIL_1.1.11@PYLDB_UTIL_1.1.11 2:2.0.7
- PYLDB_UTIL_1.1.12@PYLDB_UTIL_1.1.12 2:2.0.7
- PYLDB_UTIL_1.1.13@PYLDB_UTIL_1.1.13 2:2.0.7
- PYLDB_UTIL_1.1.14@PYLDB_UTIL_1.1.14 2:2.0.7
- PYLDB_UTIL_1.1.15@PYLDB_UTIL_1.1.15 2:2.0.7
- PYLDB_UTIL_1.1.16@PYLDB_UTIL_1.1.16 2:2.0.7
- PYLDB_UTIL_1.1.17@PYLDB_UTIL_1.1.17 2:2.0.7
- PYLDB_UTIL_1.1.18@PYLDB_UTIL_1.1.18 2:2.0.7
- PYLDB_UTIL_1.1.19@PYLDB_UTIL_1.1.19 2:2.0.7
- PYLDB_UTIL_1.1.20@PYLDB_UTIL_1.1.20 2:2.0.7
- PYLDB_UTIL_1.1.21@PYLDB_UTIL_1.1.21 2:2.0.7
- PYLDB_UTIL_1.1.22@PYLDB_UTIL_1.1.22 2:2.0.7
- PYLDB_UTIL_1.1.23@PYLDB_UTIL_1.1.23 1.5.4
- PYLDB_UTIL_1.1.24@PYLDB_UTIL_1.1.24 1.5.4
- PYLDB_UTIL_1.1.25@PYLDB_UTIL_1.1.25 1.5.4
- PYLDB_UTIL_1.1.26@PYLDB_UTIL_1.1.26 1.5.4
- PYLDB_UTIL_1.1.27@PYLDB_UTIL_1.1.27 1.5.4
- PYLDB_UTIL_1.1.28@PYLDB_UTIL_1.1.28 1.5.4
- PYLDB_UTIL_1.1.29@PYLDB_UTIL_1.1.29 1.5.4
- PYLDB_UTIL_1.1.2@PYLDB_UTIL_1.1.2 2:2.0.7
- PYLDB_UTIL_1.1.30@PYLDB_UTIL_1.1.30 1.5.4
- PYLDB_UTIL_1.1.31@PYLDB_UTIL_1.1.31 1.5.4
- PYLDB_UTIL_1.1.3@PYLDB_UTIL_1.1.3 2:2.0.7
- PYLDB_UTIL_1.1.4@PYLDB_UTIL_1.1.4 2:2.0.7
- PYLDB_UTIL_1.1.5@PYLDB_UTIL_1.1.5 2:2.0.7
- PYLDB_UTIL_1.1.6@PYLDB_UTIL_1.1.6 2:2.0.7
- PYLDB_UTIL_1.1.7@PYLDB_UTIL_1.1.7 2:2.0.7
- PYLDB_UTIL_1.1.8@PYLDB_UTIL_1.1.8 2:2.0.7
- PYLDB_UTIL_1.1.9@PYLDB_UTIL_1.1.9 2:2.0.7
- PYLDB_UTIL_1.2.0@PYLDB_UTIL_1.2.0 1.5.4
- PYLDB_UTIL_1.2.1@PYLDB_UTIL_1.2.1 1.5.4
- PYLDB_UTIL_1.2.2@PYLDB_UTIL_1.2.2 1.5.4
- PYLDB_UTIL_1.2.3@PYLDB_UTIL_1.2.3 1.5.4
- PYLDB_UTIL_1.3.0@PYLDB_UTIL_1.3.0 1.5.4
- PYLDB_UTIL_1.3.1@PYLDB_UTIL_1.3.1 1.5.4
- PYLDB_UTIL_1.3.2@PYLDB_UTIL_1.3.2 1.5.4
- PYLDB_UTIL_1.4.0@PYLDB_UTIL_1.4.0 1.5.4
- PYLDB_UTIL_1.4.1@PYLDB_UTIL_1.4.1 1.5.4
- PYLDB_UTIL_1.5.0@PYLDB_UTIL_1.5.0 1.5.4
- PYLDB_UTIL_1.5.1@PYLDB_UTIL_1.5.1 1.5.4
- PYLDB_UTIL_1.5.2@PYLDB_UTIL_1.5.2 1.5.4
- PYLDB_UTIL_1.5.3@PYLDB_UTIL_1.5.3 1.5.4
- PYLDB_UTIL_1.6.0@PYLDB_UTIL_1.6.0 2:2.0.7
- PYLDB_UTIL_1.6.1@PYLDB_UTIL_1.6.1 2:2.0.7
- PYLDB_UTIL_1.6.2@PYLDB_UTIL_1.6.2 2:2.0.7
- PYLDB_UTIL_1.6.3@PYLDB_UTIL_1.6.3 2:2.0.7
- PYLDB_UTIL_2.0.0@PYLDB_UTIL_2.0.0 2:2.0.7
- PYLDB_UTIL_2.0.1@PYLDB_UTIL_2.0.1 2:2.0.7
- PYLDB_UTIL_2.0.2@PYLDB_UTIL_2.0.2 2:2.0.7
- PYLDB_UTIL_2.0.3@PYLDB_UTIL_2.0.3 2:2.0.7
- PYLDB_UTIL_2.0.4@PYLDB_UTIL_2.0.4 2:2.0.7
- PYLDB_UTIL_2.0.5@PYLDB_UTIL_2.0.5 2:2.0.7
- PYLDB_UTIL_2.1.0@PYLDB_UTIL_2.1.0 2:2.1.0
- PYLDB_UTIL_2.1.1@PYLDB_UTIL_2.1.1 2:2.1.1
- PYLDB_UTIL_2.1.2@PYLDB_UTIL_2.1.2 2:2.1.2
- PYLDB_UTIL_2.1.3@PYLDB_UTIL_2.1.3 2:2.1.3
- PYLDB_UTIL_2.1.4@PYLDB_UTIL_2.1.4 2:2.1.4
- pyldb_Dn_FromDn@PYLDB_UTIL_1.1.2 2:2.0.7
- pyldb_Object_AsDn@PYLDB_UTIL_1.1.2 2:2.0.7
- pyldb_check_type@PYLDB_UTIL_2.1.0 2:2.1.0
+libpyldb-util.cpython-39-x86-64-linux-gnu.so.2 python3-ldb #MINVER#
+
PYLDB_UTIL.CPYTHON_39_X86_64_LINUX_GNU_2.1.4@PYLDB_UTIL.CPYTHON_39_X86_64_LINUX_GNU_2.1.4
2:2.1.4-2build1
+ PYLDB_UTIL_1.1.10@PYLDB_UTIL_1.1.10 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.11@PYLDB_UTIL_1.1.11 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.12@PYLDB_UTIL_1.1.12 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.13@PYLDB_UTIL_1.1.13 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.14@PYLDB_UTIL_1.1.14 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.15@PYLDB_UTIL_1.1.15 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.16@PYLDB_UTIL_1.1.16 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.17@PYLDB_UTIL_1.1.17 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.18@PYLDB_UTIL_1.1.18 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.19@PYLDB_UTIL_1.1.19 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.20@PYLDB_UTIL_1.1.20 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.21@PYLDB_UTIL_1.1.21 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.22@PYLDB_UTIL_1.1.22 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.23@PYLDB_UTIL_1.1.23 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.24@PYLDB_UTIL_1.1.24 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.25@PYLDB_UTIL_1.1.25 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.26@PYLDB_UTIL_1.1.26 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.27@PYLDB_UTIL_1.

Bug#972913: libiio ftbfs with python3.9

[Matthias Klose]

Package: src:libiio
Version: 0.21-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

libiio ftbfs with python3.9; to reproduce, you can use the repositories found 
at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/libiio_0.21-1build1_amd64-2020-10-23T14:59:42Z.build

[...]
make[1]: Leaving directory '/<>'
   dh_fixperms -O--builddirectory=build
   dh_missing -O--builddirectory=build
dh_missing: warning:
usr/lib/python3.9/site-packages/__pycache__/iio.cpython-39.pyc exists in
debian/tmp but is not installed to anywhere
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per
package)
 * dh_install: iiod (1), libiio-dev (3), libiio-utils (8), libiio0 (3),
libiio0-doc (1), python3-libiio (2)
 * dh_installdocs: iiod (0), libiio-dev (0), libiio-utils (0), libiio0 
(0),
libiio0-doc (0), python3-libiio (0)
 * dh_installman: iiod (1), libiio-dev (0), libiio-utils (9), libiio0 
(0),
libiio0-doc (0), python3-libiio (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please
reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for
debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only
a subset is built
If the omission is intentional or no other helper can take care of this
consider adding the
paths to debian/not-installed.
make: *** [debian/rules:3: binary] Error 25

Bug#972914: pyhst2 ftbfs with python3.9

[Matthias Klose]

Package: src:pyhst2
Version: 2020a-3
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

pyhst2 ftbfs with python3.9; to reproduce, you can use the repositories found 
at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/pyhst2_2020a-3build1_amd64-2020-10-25T06:41:37Z.build

[...]
dh build --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:217: python3.8 setup.py config
running config
I: pybuild base:217: python3.9 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3.8 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/congrid.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/combina.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/phasesimple.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/phase.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/Control.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/pyhst_segment.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/getSysOutput.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/string_six.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/PyHST.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/NNFBPTrain.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/pyhst_jp2edf.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/setCpuSet.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/tomography.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/__init__.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/getCpuSetRange.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/pyhst_unsharp3D_.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/pyhst_.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/EdfFile.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/LTSparsePrep.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/sirtfilter.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
copying PyHST/Parameters_module.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b
creating /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test
copying PyHST/test/test_all.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test
copying PyHST/test/stop_test_integrate.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test
copying PyHST/test/__init__.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test
copying PyHST/test/test_dummy.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test
copying PyHST/test/utilstest.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test
copying PyHST/test/test_crayon.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test
creating
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party
copying PyHST/third_party/setup.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party
copying PyHST/third_party/enum.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party
copying PyHST/third_party/transformations.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party
copying PyHST/third_party/__init__.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party
copying PyHST/third_party/six.py ->
/<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party
running build_ext
cythoning PyHST/segment/segment_cy.pyx to PyHST/segment/segment_cy.cpp
building 'PyHST2_2019b.Cspace' extension
Warning: Can't read registry to find the necessary compiler setting
Make sure that Python modules winreg, win32api or win32con are installed.
C compiler: x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare
-DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
-Werror=format-security -g -fwrapv -O2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC

creating build
creating build/temp.linux-x86_64-3.8
creating build/temp.linux-x86_64-3.8/PyHST
creating build/temp.linux-x86_64-3.8/PyHST/Cspace
compile options: '-I/usr/include
-I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/openmpi/
-I/usr/include/hdf5/serial/ -I/usr/include/python3.8 -c'
extra options: 'gcc'
mpicc: PyHST/Cspace/CCspace.c
mpicc: PyHST/Cspace/cpyutils.c
mpicc: PyHST/Cspace/Cspace.c
mpicc: PyHST/Cspace/edftools.c
mpicc: PyHST/Cspace/pyhst_n

Bug#972915: pluginhook FTBFS on mipsel/mips64el/riscv64: -buildmode=pie not supported

[Adrian Bunk]

Source: pluginhook
Version: 0~20150216.0~a320158-2.1
Severity: serious
Tags: ftbfs

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

...
cd obj-mips64el-linux-gnuabi64 && go install -trimpath -v -p 1 
-buildmode=pie github.com/progrium/pluginhook
-buildmode=pie not supported on linux/mips64le
dh_auto_build: error: cd obj-mips64el-linux-gnuabi64 && go install -trimpath -v 
-p 1 -buildmode=pie github.com/progrium/pluginhook returned exit code 1
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 25

Bug#972916: sagemath ftbfs with python3.9

[Matthias Klose]

Package: src:sagemath
Version: 9.2~beta12-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

sagemath ftbfs with python3.9; to reproduce, you can use the repositories found 
at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/sagemath_9.2~beta12-1build1_amd64-2020-10-23T22:48:30Z.build

[...]
make --no-print-directory all-sage
make --no-print-directory sage_conf-no-deps
cd '/<>/sage/build/pkgs/sage_conf' && .
'/<>/sage/src/bin/sage-env-config' && .
'/<>/sage/src/bin/sage-env' && .
'/<>/sage/build/bin/sage-build-env-config' && sage-logger -p
'/<>/sage/build/pkgs/sage_conf/spkg-install'
'/<>/sage/logs/pkgs/sage_conf-none.log'
[sage_conf-none] Installing
[sage_conf-none] Error: Tried to use Sage's Python which was not yet installed.
[sage_conf-none] If this was called from an spkg-install script for another
[sage_conf-none] package you should add $(PYTHON) as a dependency in
[sage_conf-none] build/pkgs//dependencies
[sage_conf-none] Error: could not determine package name
[sage_conf-none]

[sage_conf-none] Error installing
[sage_conf-none]

make[8]: *** [Makefile:2161: sage_conf-no-deps] Error 1
make[7]: *** [Makefile:2161:
/<>/sage/local/var/lib/sage/installed/sage_conf-none] Error 2
make[6]: *** [Makefile:1769: all-build] Error 2

Bug#972917: tulip ftbfs with python3.9

[Matthias Klose]

Package: src:tulip
Version: 5.4.0+dfsg-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

sagemath ftbfs with python3.9; to reproduce, you can use the repositories found 
at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/tulip_5.4.0+dfsg-1build1_amd64-2020-10-24T02:18:56Z.build

[...]
../library/tulip-python/src/ConsoleUtilsModule.cpp:220:1: error: too many
initializers for ‘PyTypeObject’ {aka ‘_typeobject’}
  220 | };
  | ^
../library/tulip-python/src/ConsoleUtilsModule.cpp:324:1: error: too many
initializers for ‘PyTypeObject’ {aka ‘_typeobject’}
  324 | };
  | ^

Bug#972918: virtualbox ftbfs with python3.9

[Matthias Klose]

Package: src:virtualbox
Version: 6.1.16-dfsg-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

virtualbox ftbfs with python3.9; to reproduce, you can use the repositories
found at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/virtualbox_6.1.16-dfsg-1build1_amd64-2020-10-24T10:20:17Z.build

[...]
Checking for Python support:
  ** Python not found!
Check /<>/out/configure.log for details
make[1]: *** [debian/rules:44: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:39: build] Error 2

Bug#972919: ycmd ftbfs with python3.9

[Matthias Klose]

Package: src:ycmd
Version: 0+20200810+gita24204e+ds-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

ycmd ftbfs with python3.9; to reproduce, you can use the repositories
found at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/ycmd_0+20200810+gita24204e+ds-1build1_amd64-2020-10-24T03:08:32Z.build

[...]
-- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake
(found version "1.71.0") found components: filesystem
-- Using external libclang: /usr/lib/x86_64-linux-gnu/libclang-9.so.1
CMake Warning at /usr/src/googletest/googlemock/CMakeLists.txt:43 (project):
  VERSION keyword not followed by a value or was followed by a value that
  expanded to nothing.


CMake Warning at /usr/src/googletest/googletest/CMakeLists.txt:54 (project):
  VERSION keyword not followed by a value or was followed by a value that
  expanded to nothing.


-- Found PythonInterp: /usr/bin/python3.9 (found version "3.9")
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:129
(set_target_properties):
  set_target_properties called with incorrect number of arguments.


CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:132
(set_target_properties):
  set_target_properties called with incorrect number of arguments.


CMake Error at /usr/src/googletest/googlemock/CMakeLists.txt:103
(set_target_properties):
  set_target_properties called with incorrect number of arguments.


CMake Error at /usr/src/googletest/googlemock/CMakeLists.txt:106
(set_target_properties):
  set_target_properties called with incorrect number of arguments.


-- NOT using clang-tidy for static analysis.
-- Configuring incomplete, errors occurred!
See also
"/<>/ycmd-0+20200810+gita24204e+ds/ycm_build/CMakeFiles/CMakeOutput.log".
See also
"/<>/ycmd-0+20200810+gita24204e+ds/ycm_build/CMakeFiles/CMakeError.log".
cd ycm_build && tail -v -n \+0 CMakeCache.txt

Bug#972920: dicomscope: binary-all FTBFS

[Adrian Bunk]

Source: dicomscope
Version: 3.6.0-21
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=dicomscope&arch=all&ver=3.6.0-21&stamp=1601116491&raw=0

...
   dh_missing -i -O--buildsystem=cmake
dh_missing: warning: usr/lib/libjInterface.so exists in debian/tmp but is not 
installed to anywhere 
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: dicomscope (4), dicomscope-doc (0), libdicomscope-jni (0)
 * dh_installdocs: dicomscope (0), dicomscope-doc (2), 
libdicomscope-jni (0)
 * dh_installman: dicomscope (1), dicomscope-doc (0), libdicomscope-jni 
(0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make: *** [debian/rules:14: binary-indep] Error 25

Bug#972921: shasta: binary-all FTBFS

[Adrian Bunk]

Source: shasta
Version: 0.6.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=shasta&arch=all&ver=0.6.0-1&stamp=1603461248&raw=0

...
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
# Rename shastaDynamic to shasta for ease
mv debian/shasta/usr/bin/shastaDynamic debian/shasta/usr/bin/shasta
mv: cannot stat 'debian/shasta/usr/bin/shastaDynamic': No such file or directory
make[1]: *** [debian/rules:30: override_dh_install] Error 1

Bug#972924: libangelscript2.34.0: Libraries installed in the wrong directory on i386

[Adrian Bunk]

Package: libangelscript2.34.0
Version: 2.34.0+ds-3.1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/i386/a/angelscript/7741166/log.gz

...
g++  -D_LINUX_ -DAS_DEBIAN_LIB -o tutorial/bin/tutorial 
tutorial/source/main.cpp -langelscript-addon -langelscript
/usr/bin/ld: cannot find -langelscript-addon
/usr/bin/ld: cannot find -langelscript
collect2: error: ld returned 1 exit status
make: *** [Makefile:29: tutorial/bin/tutorial] Error 1



On i386 libraries are supposed to be installed into
/usr/lib/i386-linux-gnu not /usr/lib/i686-linux-gnu

Bug#972923: angelscript FTBFS on mips64el/sparc64: tutorial failure

[Adrian Bunk]

Source: angelscript
Version: 2.34.0+ds-2
Severity: serious
Tags: ftbfs patch

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

...
   debian/rules override_dh_auto_test-arch
make[1]: Entering directory '/<>'
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -I../angelscript/include" 
LDFLAGS="-Wl,-z,relro -Wl,-z,now  -Wl,-rpath,../../../angelscript/lib 
-L../angelscript/lib" /usr/bin/make -C samples test
make[2]: Entering directory '/<>/samples'
mkdir -p tutorial/bin
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -pedantic -Wdate-time 
-D_FORTIFY_SOURCE=2 -I../angelscript/include -D_LINUX_ -DAS_DEBIAN_LIB -o 
tutorial/bin/tutorial tutorial/source/main.cpp -Wl,-z,relro -Wl,-z,now  
-Wl,-rpath,../../../angelscript/lib -L../angelscript/lib -langelscript-addon 
-langelscript
cd tutorial/bin && echo y | ./tutorial
tutorial: ../../source/as_callfunc.cpp:256: int 
AngelScript::PrepareSystemFunction(AngelScript::asCScriptFunction*, 
AngelScript::asSSystemFunctionInterface*, AngelScript::asCScriptEngine*): 
Assertion `false' failed.
Aborted
make[2]: *** [Makefile:28: test_tutorial] Error 134


Fix/workaround:

--- debian/rules.old2020-10-26 09:03:20.601856087 +
+++ debian/rules2020-10-26 09:09:14.763737123 +
@@ -13,9 +13,7 @@
 export VERSION := $(shell echo '$(DEB_VERSION_UPSTREAM)' | sed -e 's/\+.*//')
 
 # buggy archs
-ifeq ($(DEB_HOST_ARCH),armhf)
-  DEB_CXXFLAGS_MAINT_APPEND += -DAS_MAX_PORTABILITY
-else ifeq ($(DEB_HOST_ARCH),x32)
+ifneq (,$(filter $(DEB_HOST_ARCH), armhf mips64el sparc64 x32))
   DEB_CXXFLAGS_MAINT_APPEND += -DAS_MAX_PORTABILITY
 endif
 

Bug#972158: marked as done (falkon: FTBFS with Qt 5.15: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 10:03:37 +
with message-id 
and subject line Bug#972158: fixed in falkon 3.1.0+dfsg1-9
has caused the Debian Bug report #972158,
regarding falkon: FTBFS with Qt 5.15: error: aggregate ‘QPainterPath path’ has 
incomplete type and cannot be defined
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
972158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: falkon
Version: 3.1.0+dfsg1-8
Severity: important
Tags: ftbfs fixed-upstream
User: debian-qt-...@lists.debian.org
Usertags: qt5.15
Forwarded: https://invent.kde.org/network/falkon/-/merge_requests/3

Dear Maintainer,

falkon fails to build with Qt 5.15, currently available in experimental.

After successfully rebuilding kguiaddons and kxmlgui, I get this error:

  /<>/src/lib/tools/qztools.cpp:413:18: error: aggregate 
‘QPainterPath path’ has incomplete type and cannot be defined
413 | QPainterPath path;
|  ^~~~

This is fixed upstream, see the linked merge request.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: falkon
Source-Version: 3.1.0+dfsg1-9
Done: Dmitry Shachnev 

We believe that the bug you reported is fixed in the latest version of
falkon, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated falkon package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Oct 2020 13:51:42 +0300
Source: falkon
Architecture: source
Version: 3.1.0+dfsg1-9
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Dmitry Shachnev 
Closes: 972158
Changes:
 falkon (3.1.0+dfsg1-9) unstable; urgency=medium
 .
   [ Dmitry Shachnev ]
   * Backport upstream patch to fix build with Qt 5.15 (closes: #972158).
 .
   [ Georges Khaznadar ]
   * adopted Dmitry Shachnev's fix, thank you Dmitry!
Checksums-Sha1:
 30917a4bef3ec94cbc3cbd698f799682057d33e7 2591 falkon_3.1.0+dfsg1-9.dsc
 f4375fa325dd14ae810ba74283c0bf47b12655b2 189192 
falkon_3.1.0+dfsg1-9.debian.tar.xz
 fcecfb83bc70e7acd805810da5a1d278c428cd6c 24104 
falkon_3.1.0+dfsg1-9_source.buildinfo
Checksums-Sha256:
 0985373cd03533d3e8b6c90f80e15d28a8c3256b6a819f6fec8d5ada33093555 2591 
falkon_3.1.0+dfsg1-9.dsc
 e9665880b587de7ec0910e9a619eff31baf558068af8dea3707bfdfba2c06e18 189192 
falkon_3.1.0+dfsg1-9.debian.tar.xz
 373211509bba8a0aa8e6ad170b08754beafdefbd548cbffaeb053d77114c17e9 24104 
falkon_3.1.0+dfsg1-9_source.buildinfo
Files:
 a89652f2e94848154e4666f625e30689 2591 web optional falkon_3.1.0+dfsg1-9.dsc
 a69a0ab773463c41beba26ea4b38906c 189192 web optional 
falkon_3.1.0+dfsg1-9.debian.tar.xz
 17321ac60f409d1526909ab9f22121b7 24104 web optional 
falkon_3.1.0+dfsg1-9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl+Wm0wACgkQHCgWkHE2
rjlD1Q/6AgqWru7/BRQIO2jol0GQOiWfLre1zMKQb6AltJMojn/zIm9n38tav5lw
qPByTsO06cacfw1VoKv/+Ga+7nKcWSudzoDUZJU1/PgYy2YcHabRrBF1ppJ1pA8W
csSc9vWMldhNOyKWnyrNLPUYGidQEJlT5HUJ6td3bYjj0gR2EPYVaWKhoooDVuUR
/qZVrL1kUGTF9jEjfWs3poysADkFTlGe3DeE4lAPRSuOngrOqSmrxJwzkRjVrava
jSsFPnUSMl8UvLzNIaTTcvE1YiVGdYrm81yCcdWO3LsJ+i1fGj/9qpEBonNeQYVk
soSQ7kbTsUjS0Q+wnSjXKFNoiXLwwK7HkKigDNoxGQPh0VPMfcjb6O1xJu/5Xa9c
L3DS95bHjxg4pVXv7qwTF9yfeyT1gy9Ph0Np/TUbtfsULkx0mV98caD+e3qHdiDn
Y6yUPT6BrifAi52MtSAQLARaB4BYRFX18YeorqsTh7QeKNE2WTveTjIs90yqEaw1
yHFtRXkPhrD4Z6HBHiSSYHxGyfu5wq2xZEvTTRChFkD4YzYMppx1yYdNrjuWhzWK
txoSePxdkNdUGkrLQhZD4KtXMSHKtlcHXuec5E0+GHlI4Jp4sGXZKyG8dOMgb7AY
8w19yFCUFeERXvNRlh5SPkDheE032TvpsGetiCAwgkl7G9AOnwQ=
=Jp6b
-END PGP SIGNATURE End Message ---

Bug#972780: [debian-mysql] Bug#972780: mytop has wrong shebang

[Otto Kekäläinen]

Tags: forwarded -1 https://jira.mariadb.org/browse/MDEV-23697

Hello!

This has been fixed upstream in 10.3.26.

Bug#968886: marked as done (libgclib FTBFS on !x86: missing symbols)

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 10:19:58 +
with message-id 
and subject line Bug#968886: fixed in libgclib 0.11.10+ds-2
has caused the Debian Bug report #968886,
regarding libgclib FTBFS on !x86: missing symbols
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
968886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgclib
Version: 0.11.10+ds-1
Severity: serious
Tags: ftbfs

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

...
   dh_makeshlibs -a -a
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libgclib2/DEBIAN/symbols doesn't match 
completely debian/libgclib2.symbols
--- debian/libgclib2.symbols (libgclib2_0.11.10+ds-1_arm64)
+++ dpkg-gensymbolsp65RDT   2020-08-09 21:11:26.344608441 +
@@ -324,10 +324,10 @@
  _ZN5GListI6GXBandE18DefaultCompareProcEPvS2_@Base 0.11.4
  _ZN5GListI6GXSeedE18DefaultCompareProcEPvS2_@Base 0.11.4
  _ZN5GListI6GffObjE18DefaultCompareProcEPvS2_@Base 0.11.4
- _ZN5GListI6NucOriE18DefaultCompareProcEPvS2_@Base 0.11.4
- _ZN5GListI7GffAttrE18DefaultCompareProcEPvS2_@Base 0.11.4
+#MISSING: 0.11.10+ds-1# _ZN5GListI6NucOriE18DefaultCompareProcEPvS2_@Base 
0.11.4
+#MISSING: 0.11.10+ds-1# _ZN5GListI7GffAttrE18DefaultCompareProcEPvS2_@Base 
0.11.4
  _ZN5GListI7GffExonE18DefaultCompareProcEPvS2_@Base 0.11.4
- _ZN5GListI8SeqDelOpE18DefaultCompareProcEPvS2_@Base 0.11.4
+#MISSING: 0.11.10+ds-1# _ZN5GListI8SeqDelOpE18DefaultCompareProcEPvS2_@Base 
0.11.4
  _ZN5GListI9GFastaRecE18DefaultCompareProcEPvS2_@Base 0.11.4
  _ZN5GListI9GXAlnInfoE18DefaultCompareProcEPvS2_@Base 0.11.4
  _ZN5GPVecI11GffNameInfoE15DefaultFreeProcEPv@Base 0.11.4
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:13: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: libgclib
Source-Version: 0.11.10+ds-2
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
libgclib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 968...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libgclib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 Sep 2020 11:07:12 +0200
Source: libgclib
Architecture: source
Version: 0.11.10+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 968886
Changes:
 libgclib (0.11.10+ds-2) unstable; urgency=medium
 .
   * Provide symbols only for amd64
 Closes: #968886
Checksums-Sha1:
 476e50e04f8f1a055a5bd205e74f8e575558cf92 2176 libgclib_0.11.10+ds-2.dsc
 c90210c7f507ce6b8251cf9f30d76a1ebca811f3 13032 
libgclib_0.11.10+ds-2.debian.tar.xz
 15dc61d82e30e7fd30dfdd4723a0620e99090bf6 6748 
libgclib_0.11.10+ds-2_amd64.buildinfo
Checksums-Sha256:
 94613a332212bf4bc4ff15f53a9364eb9b0e280e7031c9c0fc6129d46cb8da61 2176 
libgclib_0.11.10+ds-2.dsc
 ca1d23b6bb9ec5ec1ae364cf5ba44319a133ae825a9f0e98fca8c9ffbdf525b4 13032 
libgclib_0.11.10+ds-2.debian.tar.xz
 524b84b951c25b68faa6ecbab87b29caa83cbde2cae8f8153321d12b88f7a86d 6748 
libgclib_0.11.10+ds-2_amd64.buildinfo
Files:
 9e65e037a9adc83d0c6cea750a8614c7 2176 science optional 
libgclib_0.11.10+ds-2.dsc
 7f151d8f323f3dee11c2554ae9aed51c 13032 science optional 
libgclib_0.11.10+ds-2.debian.tar.xz
 77d1cfd32e2ff59c1feb049b3089e70c 6748 science optional 
libgclib_0.11.10+ds-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+WnWMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGeLg/+I2ivWcsXHC1T6kZ9jMsdOwHn364EZRuf
wlh/RYNZ5VrKgQDmS1Sd8G89WJ0lnkPQUUYbkrAOMGMXOPPF5Oat1MGPxbn2x5rp
oZB1uTq6BAGjV3GLGEe1XiNaFEHb32hmgBOT/O/lHo4YVBN47BqrTEoiMamidwJI
DG/SUn35HRuP8C4pvNJZlaRAUrNWhD9mJanigZhzszj4xN5MX8NQsebROXjnQqe8
Pv0kSaxCJhXqF0NmPNg7Im56uQNzzhKYI8Qxf4EXXliTLwZUuDbJrg0ia8BoHSyS
c6ERyNi6qdDARHB/tLcCe6cuAoe4QnG2HyF6qvT2ESmJC44i0m6qP+l4dd8YBTZB
Z3tc00qdSaSJMKjiYwBFnnBrXGirltFnYqJX4aSiJErnDedQY6H0rz37QpyFlRap
glM6aZRC4Kg4sR6P8b5rNGtEvneitJknFyGbZxYHsxYuA//cMN2os+eujtq

Processed: block 971182 with 962843

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 971182 with 962843
Bug #971182 [src:go-mtpfs] go-mtpfs: FTBFS: 
src/github.com/hanwen/go-mtpfs/main.go:68:11: undefined: 
fuse.NewLockingRawFileSystem
971182 was not blocked by any bugs.
971182 was not blocking any bugs.
Added blocking bug(s) of 971182: 962843
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
971182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#972926: celery: autopkgtest failures

[peter green]

Package: celery
Version: 4.4.6-1
Severity: serious

The autopkgtest for celery 4.4.6-1 is failing with the new python3-defaults.

https://ci.debian.net/data/autopkgtest/testing/amd64/c/celery/7741503/log.gz


=== FAILURES ===
 test_chain.test_append_to_empty_chain _

self = 


  ???


t/unit/tasks/test_canvas.py:535: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
celery/canvas.py:682: in freeze

self.app, _id, group_id, chord, clone=False,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 


self = 

@property
def app(self):
app = self._app
if app is None:
try:

  app = self.tasks[0]._app

E   TypeError: 'NoneType' object is not subscriptable

celery/canvas.py:817: TypeError


Meanwhile celery 5.0.0-1 in unstable is also failing, but with a different error

https://ci.debian.net/data/autopkgtest/unstable/amd64/c/celery/7738043/log.gz


 ERRORS 
 ERROR collecting t/unit/backends/test_base.py _
'celery' not found in `markers` configuration option
_ ERROR collecting t/unit/backends/test_rpc.py _
'celery' not found in `markers` configuration option

Bug#951508: lmod: broken on all architectures except x86_64 (wrong search path)

[Baptiste Jonglez]

Hi,

On Tue, 15 Sep 2020 12:32:34 +0200 "Aaron Zauner (azet)"  wrote:
> If anyone wants to take over I'm more than fine with that. The amount of work 
> I have at the moment barely permits me from maintaining projects. It's most 
> sensible that someone actively using this project on Debian maintains it, as 
> is, I'm not using it much anymore and am not working in HPC at the moment. 
> The bug should definitely reported upstream. Upgrading the package should be 
> fairly simple though - the dependencies are already in place, as are simple 
> tests/git integration etc.: https://github.com/azet/lmod-deb

I had a look, and it seems to be an upstream "feature" that was introduced
between lmod 6.2 and lmod 6.3.

The root cause is that the configure script uses the build-time paths from
lua, and then uses these paths at runtime.  The upstream changelog for 6.3
states:

> Lmod now uses the values of LUA_PATH and LUA_CPATH at configuration
> time.  This way Lmod is safe from user changes to these important Lua
> values.

The corresponding upstream change and discussion: 
https://github.com/TACC/Lmod/issues/112

This was already reported for ARM and closed: 
https://github.com/TACC/Lmod/issues/338

Overall, I think the simplest solution is to change the architecture to "any".

Baptiste

> > On 15.09.2020, at 09:33, Lucas Nussbaum  wrote:
> > 
> > retitle 951508 lmod: broken on all architectures except x86_64 (wrong 
> > search path)
> > severity 951508 serious
> > thanks
> > 
> > Hi,
> > 
> > We ran into the same bug on an arm64 system, so it looks like lmod is
> > broken on all architectures except x86_64. I'm updating the bug title
> > and the severity to reflect that.
> > 
> > I'm attaching the diffoscope output that shows that the generated
> > packages are indeed different on amd64 and arm64.
> > 
> > A simple fix would be to turn this package into an Architecture:any
> > package.  But indeed, it should probably be reported (and fixed) upstream.
> > 
> >> On 17/02/20 at 19:49 +0100, Aaron Zauner wrote:
> >> Since I'm barely keeping this package updated I'd suggest that you use the
> >> upstream Lmod project source with the dependencies that come with this
> >> package, you'll get more bug fixes, Performance and features out of it in a
> >> production environment. That's what we used to do on live HPC systems since
> >> a lot of software needs to be built by hand outside of the distro packaging
> >> anyway.
> > 
> > Err, if this is the case, maybe you should mark this package as orphaned
> > or RFA? I'm also Ccing people who uploaded NMUs for the package. Maybe
> > someone is interested in taking over.
> > 
> > Lucas
> > 

-- 
Baptiste Jonglez
Inria Grenoble - Rhône-Alpes 
R&D Engineer, Grid'5000 platform 
LIG lab 


signature.asc
Description: PGP signature

Bug#972887: libgstreamer1-perl: Deprecated upstream

[intrigeri]

Control: severity -1 normal
Control: retitle -1 Inactive upstream

Hi Mike,

Mike Gabriel (2020-10-26):
> I don't think that libgstreamer1-perl as found in Debian is the one  
> provided by GNOME/Gtk / referenced in the given URL / deprecation  
> announcement.

You're right!

This one is https://github.com/frezik/GStreamer1.

The GNOME one, that I was referring to, was previously packaged
as libgstreamer-perl (removed in 2015: #799327).

Sorry for the confusion.

Shall I close this bug?

> Nonetheless, the upstream for libgstreamer1-perl has also been quite  
> inactive over the past years.

> I will ping Perl people that I know if  
> they are interested in taking over upstream maintenance.

Sounds great, thanks! :)

Processed: Re: Bug#972887: libgstreamer1-perl: Deprecated upstream

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #972887 [src:libgstreamer1-perl] libgstreamer1-perl: Deprecated upstream
Severity set to 'normal' from 'serious'
> retitle -1 Inactive upstream
Bug #972887 [src:libgstreamer1-perl] libgstreamer1-perl: Deprecated upstream
Changed Bug title to 'Inactive upstream' from 'libgstreamer1-perl: Deprecated 
upstream'.

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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 971222 gir-to-d
Bug #971222 {Done: Matthias Klumpp } [src:appstream-generator] 
appstream-generator: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu 
&& LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain 
--prefix=/usr --sysconfdir=/etc --localstatedir=/var 
--libdir=lib/x86_64-linux-gnu --prefix=/usr --buildtype=plain 
-Ddownload-js=false returned exit code 1
Bug reassigned from package 'src:appstream-generator' to 'gir-to-d'.
No longer marked as found in versions appstream-generator/0.8.2-2.
No longer marked as fixed in versions gir-to-d/0.21.0-2.
> reassign 971211 gir-to-d
Bug #971211 {Done: Matthias Klumpp } [src:glib-d] glib-d: 
FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 
meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr 
--sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu returned 
exit code 1
Bug reassigned from package 'src:glib-d' to 'gir-to-d'.
No longer marked as found in versions glib-d/2.2.0-1.
No longer marked as fixed in versions gir-to-d/0.21.0-2.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
971211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971211
971222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#972934: lumpy-sv: Cannot fulfill the build dependencies

[Adrian Bunk]

Source: lumpy-sv
Version: 0.3.1+dfsg-1
Severity: serious
Tags: ftbfs

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

lumpy-sv build-depends on:
- libcurl4-openssl-dev:amd64
lumpy-sv build-depends on:
- libhts-dev:amd64
libhts-dev depends on:
- libcurl4-gnutls-dev:amd64
libcurl4-openssl-dev conflicts with:
- libcurl4-gnutls-dev:amd64


Buildds are only considering the first alternative in unstable,
a change to libcurl4-gnutls-dev would solve this.

Bug#972933: lumpy-sv: binary-all FTBFS

[Adrian Bunk]

Source: lumpy-sv
Version: 0.3.1+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=lumpy-sv&arch=all&ver=0.3.1%2Bdfsg-1&stamp=1600467677&raw=0

...
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
cat debian/missing-sources/pe.pos_sorted.sam |samtools view -Sb - > 
data/pe.pos_sorted.bam
cat debian/missing-sources/sr.pos_sorted.sam |samtools view -Sb - > 
data/sr.pos_sorted.bam
dh_install
rm debian/lumpy-sv/usr/share/lumpy-sv/scripts/lumpyexpress.config
rm: cannot remove 
'debian/lumpy-sv/usr/share/lumpy-sv/scripts/lumpyexpress.config': No such file 
or directory
make[1]: *** [debian/rules:23: override_dh_install] Error 1

Bug#972935: lumpy-sv must build depend on python3-pysam

[Adrian Bunk]

Source: lumpy-sv
Version: 0.3.1+dfsg-1
Severity: serious
Tags: ftbfs

lumpy-sv must build depend on python3-pysam to avoid building
on architectures where it is not installable (currently s390x
and non-release big endian architectures due to #870060).

Bug#972936: libgcc-s1 needs Breaks: libgcc1 (<< 1:10)

[Adrian Bunk]

Package: libgcc-s1
Version: 10.2.0-15
Severity: grave

On a buster system, with unstable pinned to low priority:

# apt-get install libgcc-s1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  gcc-10-base
The following NEW packages will be installed:
  gcc-10-base libgcc-s1
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/241 kB of archives.
After this operation, 384 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Selecting previously unselected package gcc-10-base:amd64.
(Reading database ... 508501 files and directories currently installed.)
Preparing to unpack .../gcc-10-base_10.2.0-15_amd64.deb ...
Unpacking gcc-10-base:amd64 (10.2.0-15) ...
Selecting previously unselected package libgcc-s1:amd64.
Preparing to unpack .../libgcc-s1_10.2.0-15_amd64.deb ...
Unpacking libgcc-s1:amd64 (10.2.0-15) ...
Replacing files in old package libgcc1:amd64 (1:8.3.0-6) ...
Setting up gcc-10-base:amd64 (10.2.0-15) ...
Setting up libgcc-s1:amd64 (10.2.0-15) ...
Processing triggers for libc-bin (2.28-10) ...
# apt-get remove libgcc-s1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  libgcc-s1
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 119 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 508502 files and directories currently installed.)
Removing libgcc-s1:amd64 (10.2.0-15) ...
Processing triggers for libc-bin (2.28-10) ...
# apt-get install libgcc-s1
apt-get: error while loading shared libraries: libgcc_s.so.1: cannot open 
shared object file: No such file or directory
#


libgcc-s1 needs
  Breaks: libgcc1 (<< 1:10)

Processed: tagging 971123

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 971123 + fixed-upstream
Bug #971123 [src:kxd] kxd: FTBFS: dh_auto_test: error: make -j4 test returned 
exit code 2
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
971123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#971102: marked as done (apvlv: FTBFS: ApvlvPdf.cc:32:10: fatal error: goo/gtypes.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 12:18:48 +
with message-id 
and subject line Bug#971102: fixed in apvlv 0.2.0-1
has caused the Debian Bug report #971102,
regarding apvlv: FTBFS: ApvlvPdf.cc:32:10: fatal error: goo/gtypes.h: No such 
file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
971102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apvlv
Version: 0.1.5+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DAPVLV_WITH_TXT 
> -DDOCDIR=\"/usr/share/doc/apvlv\" -DPACKAGE_BUGREPORT="\"Alf 
> \"" -DPACKAGE_NAME=\"apvlv\" -DPACKAGE_VERSION=\"0.1.5\" 
> -DRELEASE=\"rel\" -DSYSCONFDIR=\"/etc\" -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi 
> -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
> -I/usr/include/uuid -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/poppler/glib 
> -I/usr/include/poppler -O2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -o CMakeFiles/apvlv.dir/ApvlvPdf.cc.o -c 
> /<>/src/ApvlvPdf.cc
> /<>/src/ApvlvPdf.cc:32:10: fatal error: goo/gtypes.h: No such 
> file or directory
>32 | #include 
>   |  ^~
> compilation terminated.
> make[3]: *** [src/CMakeFiles/apvlv.dir/build.make:150: 
> src/CMakeFiles/apvlv.dir/ApvlvPdf.cc.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/09/26/apvlv_0.1.5+dfsg-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: apvlv
Source-Version: 0.2.0-1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
apvlv, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 971...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated apvlv package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Oct 2020 13:39:29 +0200
Source: apvlv
Architecture: source
Version: 0.2.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 971102
Changes:
 apvlv (0.2.0-1) unstable; urgency=low
 .
   * QA upload.
   * New upstream release.
 - Fixes building with latest poppler. (Closes: #971102)
Checksums-Sha1:
 db1a5b34b6eebeecbd4e4a9decfc8f9b95fc7ebc 1973 apvlv_0.2.0-1.dsc
 980ea3733a8063f2c12121a4a2d90c0803e83464 323208 apvlv_0.2.0.orig.tar.xz
 5c7a838197a765d14d31be928b71e0425f2368d0 13696 apvlv_0.2.0-1.debian.tar.xz
Checksums-Sha256:
 705a64b42daaae10bcb6ea85d028421412a3e5478737c470fa8563bd69f9b764 1973 
apvlv_0.2.0-1.dsc
 ad942f062d8375e29cd68886e469675c1e48543bff0e099267b44b6e66b444ab 323208 
apvlv_0.2.0.orig.tar.xz
 2618d617eace9d9e2a967b30fe172e58b7363ed1e37d898e2b13c697aa497fea 13696 
apvlv_0.2.0-1.debian.tar.xz
Files:
 74707806b40bd710f7e01d0a5665a702 1973 text optional apvlv_0.2.0-1.dsc
 fe54d89b12e8a1a2eada3e08c66cbd4e 323208 text optional apvlv_0.2.0.orig.tar.xz
 68210b73910823a7f229a8542f937238 13696 text optional 
apvlv_0.2.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl+Wuz0ACgkQiNJCh6LY
mLFKjQ//U1hZK68DRhi

Processed: forcibly merging 971142 971521

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 971142 971521
Bug #971142 [src:varnish-modules] varnish-modules: FTBFS: 
vmod_bodyaccess.c:205:2: error: ‘VSB_delete’ is deprecated 
[-Werror=deprecated-declarations]
Bug #971521 [src:varnish-modules] varnish-modules: autopkgtest needs update for 
new version of varnish: Depends on old ABI
Removed indication that 971521 affects src:varnish
Added tag(s) ftbfs.
Merged 971142 971521
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
971142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971142
971521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#971521: varnish-modules: autopkgtest needs update for new version of varnish: Depends on old ABI

[Adrian Bunk]

Control: tags -1 patch fixed-upstream
Control: forwarded -1 
https://github.com/varnish/varnish-modules/commit/fed6c862118ca34374b0284a1838cc49cea5b4d1

On Thu, Oct 01, 2020 at 07:11:11PM +0200, Stig Sandbeck Mathisen wrote:
>...
> Example from the build of varnish-modules against varnish 6.5.1:
> 
> ,
> | libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/varnish -I../src/foreign -Wall -Werror 
> -Wall -Wno-format-y2k -Wstrict-prototypes -Wmissing-prototypes 
> -Werror=missing-field-initializers -Wpointer-arith -Wreturn-type 
> -Wwrite-strings -Wcast-qual -Wswitch -Wshadow -Wunused-parameter -Wcast-align 
> -Wchar-subscripts -Wnested-externs -Wextra -Wno-sign-compare -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c vcc_saintmode_if.c  -fPIC -DPIC -o 
> .libs/vcc_saintmode_if.o
> | vmod_bodyaccess.c: In function ‘vmod_hash_req_body’:
> | vmod_bodyaccess.c:205:2: error: ‘VSB_delete’ is deprecated 
> [-Werror=deprecated-declarations]
> |   205 |  VSB_delete(vsb);
> |   |  ^~
> | In file included from /usr/include/varnish/cache/cache_varnishd.h:36,
> |  from vmod_bodyaccess.c:37:
> | /usr/include/varnish/vsb.h:79:8: note: declared here
> |79 | void   VSB_delete(struct vsb *) v_deprecated_;
> |   |^~
> `
> 
> The upstream changelog for varnish 6.5.0 says:
> 
> ,[ 
> https://github.com/varnishcache/varnish-cache/blob/master/doc/changes.rst ]
> | * VSB support for dynamic vs. static allocations has been changed:
> | 
> |   For dynamic allocations use:
> | 
> | VSB_new_auto() + VSB_destroy()
> | 
> |   For preexisting buffers use:
> | 
> | VSB_init() + VSB_fini()
> | 
> | VSB_new() + VSB_delete() are now deprecated.
> `
> 
> Varnish-modules uses VSB_new_auto() and VSB_delete() in vmod_bodyaccess
> and vmod_saintmode. The long term is obviously for varnish-modules to
> use one of the new VSB_ functions for allocations.
> 
> I'm not sure what is the best short term fix. Any suggestions?
>...

An upstream fix is now available:
https://github.com/varnish/varnish-modules/commit/fed6c862118ca34374b0284a1838cc49cea5b4d1

cu
Adrian

Processed: affects 971521

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 971521 src:varnish
Bug #971521 [src:varnish-modules] varnish-modules: autopkgtest needs update for 
new version of varnish: Depends on old ABI
Bug #971142 [src:varnish-modules] varnish-modules: FTBFS: 
vmod_bodyaccess.c:205:2: error: ‘VSB_delete’ is deprecated 
[-Werror=deprecated-declarations]
Added indication that 971521 affects src:varnish
Added indication that 971142 affects src:varnish
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
971142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971142
971521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#971521: varnish-modules: autopkgtest needs update for new version of varnish: Depends on old ABI

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #971521 [src:varnish-modules] varnish-modules: autopkgtest needs update for 
new version of varnish: Depends on old ABI
Bug #971142 [src:varnish-modules] varnish-modules: FTBFS: 
vmod_bodyaccess.c:205:2: error: ‘VSB_delete’ is deprecated 
[-Werror=deprecated-declarations]
Added tag(s) fixed-upstream and patch.
Added tag(s) patch and fixed-upstream.
> forwarded -1 
> https://github.com/varnish/varnish-modules/commit/fed6c862118ca34374b0284a1838cc49cea5b4d1
Bug #971521 [src:varnish-modules] varnish-modules: autopkgtest needs update for 
new version of varnish: Depends on old ABI
Bug #971142 [src:varnish-modules] varnish-modules: FTBFS: 
vmod_bodyaccess.c:205:2: error: ‘VSB_delete’ is deprecated 
[-Werror=deprecated-declarations]
Set Bug forwarded-to-address to 
'https://github.com/varnish/varnish-modules/commit/fed6c862118ca34374b0284a1838cc49cea5b4d1'.
Set Bug forwarded-to-address to 
'https://github.com/varnish/varnish-modules/commit/fed6c862118ca34374b0284a1838cc49cea5b4d1'.

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

Bug#972156: kylin-video: FTBFS with Qt 5.15

[handsome_feng]

Hi, Dmitry,


Sorry for the delay and thanks a lot for your NMU. <&


I will upload the new upstream release to the archive ASAP.


Thanks a lot!
handsome_feng 

Bug#951508: lmod: broken on all architectures except x86_64 (wrong search path)

[Lucas Nussbaum]

Hi,

On 26/10/20 at 11:19 +0100, Baptiste Jonglez wrote:
> Hi,
> 
> On Tue, 15 Sep 2020 12:32:34 +0200 "Aaron Zauner (azet)"  
> wrote:
> > If anyone wants to take over I'm more than fine with that. The amount of 
> > work I have at the moment barely permits me from maintaining projects. It's 
> > most sensible that someone actively using this project on Debian maintains 
> > it, as is, I'm not using it much anymore and am not working in HPC at the 
> > moment. The bug should definitely reported upstream. Upgrading the package 
> > should be fairly simple though - the dependencies are already in place, as 
> > are simple tests/git integration etc.: https://github.com/azet/lmod-deb
> 
> I had a look, and it seems to be an upstream "feature" that was introduced
> between lmod 6.2 and lmod 6.3.
> 
> The root cause is that the configure script uses the build-time paths from
> lua, and then uses these paths at runtime.  The upstream changelog for 6.3
> states:
> 
> > Lmod now uses the values of LUA_PATH and LUA_CPATH at configuration
> > time.  This way Lmod is safe from user changes to these important Lua
> > values.
> 
> The corresponding upstream change and discussion: 
> https://github.com/TACC/Lmod/issues/112
> 
> This was already reported for ARM and closed: 
> https://github.com/TACC/Lmod/issues/338
> 
> Overall, I think the simplest solution is to change the architecture to "any".

Thanks Baptiste for the investigation.
I've just uploaded an NMU to unstable, and will also upload a fix to
stable.

I also opened an RFA bug for this package to reflect the current
situation (#972938).

- Lucas


signature.asc
Description: PGP signature

Processed: tagging 952159

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 952159 + buster
Bug #952159 [src:rust-nodrop-union] rust-nodrop-union: FTBFS: dh_auto_test: 
error: /usr/share/cargo/bin/cargo build returned exit code 101
Added tag(s) buster.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
952159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#969273: gnome-shell-extension-weather: fails to load: TypeError: this.actor.reparent is not a function

[Paul Wise]

On Mon, 2020-10-26 at 12:37 +, Sudip Mukherjee wrote:

> updating from the latest HEAD of:
> https://gitlab.com/jenslody/gnome-shell-extension-openweather I do see it
> working but I get exclamation mark with the icons as in the attached
> screenshot. Not sure if this is what is expected. I can upload this
> update as a "QA upload" if this is what is expected.

FTR, the exclamation marks are definitely not expected,
I only ever saw them when there were download errors.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#951508: marked as done (lmod: broken on all architectures except x86_64 (wrong search path))

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 12:50:10 +
with message-id 
and subject line Bug#951508: fixed in lmod 6.6-0.4
has caused the Debian Bug report #951508,
regarding lmod: broken on all architectures except x86_64 (wrong search path)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
951508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lmod
Version: 6.6-0.3
Severity: important

Description:

Whe using lmod on powerpc system, it show the below errors:
/usr/bin/lua: /usr/share/lua/5.2/posix/init.lua:29: module 'posix.ctype' not 
found:
no field package.preload['posix.ctype']
no file '/usr/local/share/lua/5.2/posix/ctype.lua'
no file '/usr/local/share/lua/5.2/posix/ctype/init.lua'
no file '/usr/local/lib/lua/5.2/posix/ctype.lua'
no file '/usr/local/lib/lua/5.2/posix/ctype/init.lua'
no file '/usr/share/lua/5.2/posix/ctype.lua'
no file '/usr/share/lua/5.2/posix/ctype/init.lua'
no file './posix/ctype.lua'
no file '/usr/local/lib/lua/5.2/posix/ctype.so'
no file '/usr/lib/x86_64-linux-gnu/lua/5.2/posix/ctype.so'
no file '/usr/lib/lua/5.2/posix/ctype.so'
no file '/usr/local/lib/lua/5.2/loadall.so'
no file './posix/ctype.so'
no file '/usr/local/lib/lua/5.2/posix.so'
no file '/usr/lib/x86_64-linux-gnu/lua/5.2/posix.so'
no file '/usr/lib/lua/5.2/posix.so'
no file '/usr/local/lib/lua/5.2/loadall.so'
no file './posix.so'

One of the search path is /usr/lib/x86_64-linux-gnu/lua/5.2/ instead of 
/usr/lib/powerpc64le-linux-gnu/lua/5.2/, where the file can be found


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

Kernel: Linux 4.14.158-power8-aufs-1 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lmod depends on:
ii  lua-filesystem  1.6.3-1
ii  lua-json1.3.3-2
ii  lua-posix   33.4.0-3
ii  lua-term0.07-0.1
ii  lua5.2  5.2.4-1.1+b3
ii  tcl 8.6.0+9

lmod recommends no packages.

lmod suggests no packages.

-- Configuration Files:
/etc/lmod/modulespath [Errno 116] Stale file handle: '/etc/lmod/modulespath'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lmod
Source-Version: 6.6-0.4
Done: Lucas Nussbaum 

We believe that the bug you reported is fixed in the latest version of
lmod, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lucas Nussbaum  (supplier of updated lmod package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Oct 2020 13:24:01 +0100
Source: lmod
Architecture: source
Version: 6.6-0.4
Distribution: unstable
Urgency: medium
Maintainer: Aaron Zauner 
Changed-By: Lucas Nussbaum 
Closes: 951508
Changes:
 lmod (6.6-0.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Change Architecture: to any. Closes: #951508
 This is required because lmod now gets LUA_PATH and LUA_CPATH at
 compile time (to deal with users overriding those variables).
 See https://github.com/TACC/Lmod/issues/112
 There was an upstream report that this breaks Raspian, which was rejected,
 so it is unlikely that upstream will return to the current behaviour.
 See https://github.com/TACC/Lmod/issues/338
 Thanks to Baptiste Jonglez for finding the relevant upstream bug reports.
Checksums-Sha1:
 34ab743a691c1b1858fbd501c7e3d62adae3ac3c 1874 lmod_6.6-0.4.dsc
 96924813708ca85eec0df65a8aea1d0c51bbad45 4892 lmod_6.6-0.4.debian.tar.xz
 b7b73a5849ce49bb45690fc0d458f5aebaaf192e 5918 lmod_6.6-0.4_source.buildinfo
Checksums-Sha256:
 99cc83812298af7abe76d1ee132341c11afb8e1f8643fe8f2f49e6d9a496566c 1874 
lmod_6.6-0.4.dsc
 9a5c450f26a5c16f0777b6d0a31f2013cc51d1d399e0579fbb71130

Processed: tagging 972848

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 972848 + bullseye sid
Bug #972848 {Done: Pino Toscano } [src:kdevelop] kdevelop: 
FTBFS - dh_install: error: missing files, aborting
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: libcatalyst-plugin-customerrormessage-perl: diff for NMU version 0.6-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 971167 + patch
Bug #971167 [src:libcatalyst-plugin-customerrormessage-perl] 
libcatalyst-plugin-customerrormessage-perl: FTBFS: dh_auto_test: Can't locate 
Carp/Clan.pm in @INC
Added tag(s) patch.
> tags 971167 + pending
Bug #971167 [src:libcatalyst-plugin-customerrormessage-perl] 
libcatalyst-plugin-customerrormessage-perl: FTBFS: dh_auto_test: Can't locate 
Carp/Clan.pm in @INC
Added tag(s) pending.

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

Bug#971167: libcatalyst-plugin-customerrormessage-perl: diff for NMU version 0.6-2.2

[Adrian Bunk]

Control: tags 971167 + patch
Control: tags 971167 + pending

Dear maintainer,

I've prepared an NMU for libcatalyst-plugin-customerrormessage-perl 
(versioned as 0.6-2.2) and uploaded it to DELAYED/14. Please feel free 
to tell me if I should cancel it.

cu
Adrian
diff -Nru libcatalyst-plugin-customerrormessage-perl-0.6/debian/changelog libcatalyst-plugin-customerrormessage-perl-0.6/debian/changelog
--- libcatalyst-plugin-customerrormessage-perl-0.6/debian/changelog	2015-07-24 14:29:42.0 +0300
+++ libcatalyst-plugin-customerrormessage-perl-0.6/debian/changelog	2020-10-26 15:05:51.0 +0200
@@ -1,3 +1,11 @@
+libcatalyst-plugin-customerrormessage-perl (0.6-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing build dependency on libcarp-clan-perl.
+(Closes: #971167)
+
+ -- Adrian Bunk   Mon, 26 Oct 2020 15:05:51 +0200
+
 libcatalyst-plugin-customerrormessage-perl (0.6-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libcatalyst-plugin-customerrormessage-perl-0.6/debian/control libcatalyst-plugin-customerrormessage-perl-0.6/debian/control
--- libcatalyst-plugin-customerrormessage-perl-0.6/debian/control	2015-07-24 14:30:46.0 +0300
+++ libcatalyst-plugin-customerrormessage-perl-0.6/debian/control	2020-10-26 15:05:51.0 +0200
@@ -9,7 +9,8 @@
libmro-compat-perl,
libtest-distribution-perl,
libclass-data-inheritable-perl,
-   liburi-perl
+   liburi-perl,
+   libcarp-clan-perl
 Build-Depends-Indep: perl
 Standards-Version: 3.9.3
 Homepage: http://search.cpan.org/dist/Catalyst-Plugin-CustomErrorMessage/

Bug#970808: Python3-venv is back, isn't it?

[Georges Khaznadar]

Dear Matthias,

as far as I could check, the directory Lib/venv appears as existing in
upstream sources (at least for version 3.9.0 of Python). So,
python3-venv might be considered as back, isn't it?

Can we close this bug for package thonny report now?

Best regards,   Georges.

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Processed: 972771 is forwarded

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 972771 openstructure-de...@maillist.unibas.ch
Bug #972771 [src:openstructure] openstructure ftbfs with python3.9
Set Bug forwarded-to-address to 'openstructure-de...@maillist.unibas.ch'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 971179 is forwarded to https://github.com/pycontribs/jenkinsapi/pull/795/commits/c74687dd4817a4a686cc3c70037d95c0165d2e50

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 971179 
> https://github.com/pycontribs/jenkinsapi/pull/795/commits/c74687dd4817a4a686cc3c70037d95c0165d2e50
Bug #971179 [src:python-jenkinsapi] python-jenkinsapi: FTBFS: Unable to create 
file /sbuild-nonexistent/.pylint.d/jenkinsapi.views1.stats: [Errno 2] No such 
file or directory: '/sbuild-nonexistent/.pylint.d/jenkinsapi.views1.stats'
Set Bug forwarded-to-address to 
'https://github.com/pycontribs/jenkinsapi/pull/795/commits/c74687dd4817a4a686cc3c70037d95c0165d2e50'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
971179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#971177: intake: FTBFS: TypeError: 'NoneType' object is not iterable

[Adrian Bunk]

On Wed, Oct 07, 2020 at 11:47:10AM +0100, Shayan Doust wrote:
> Control: tags -1 help
> 
> This seems to be a tricky one that I never spotted and just managed to 
> reproduce
> (although, I do not understand why during my packaging efforts, this error did
> not occur whereas now it does).
>...

The error is "FTBFS with Sphinx 3.2".
Sphinx 3.2 entered unstable on August 9th.

Dmitry (Cc'ed) might know more regarding what is the problem.

> Kind regards,
> Shayan Doust

cu
Adrian

Processed: Bug#963644 marked as pending in alembic

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #963644 [src:alembic] alembic: FTBFS with Sphinx 3.1: AttributeError: 
'tuple' object has no attribute 'docname'
Added tag(s) pending.

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

Bug#963644: marked as pending in alembic

[Ondřej Nový]

Control: tag -1 pending

Hello,

Bug #963644 in alembic reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/alembic/-/commit/b4cb52646f6182983f1c92711beb0497da263af6


New upstream release (Closes: #963644).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963644

Bug#972887: libgstreamer1-perl: Deprecated upstream

[Mike Gabriel]

Hi Intrigeri,

On  So 25 Okt 2020 21:04:43 CET, intrigeri wrote:


Source: libgstreamer1-perl
Severity: serious
X-Debbugs-Cc: Mike Gabriel 
User: debian-p...@lists.debian.org
Usertags: rm-candidate

Hi,

upstream announced¹ that the GStreamer Perl module would be deprecated
and archived in December 2020:

 - The module will no longer be updated with security patches, bug
   fixes, or when changes are made in the Perl ABI.

 - It will no longer be possible to submit new issues or pull requests
   for these modules, or push new changes to their Git repos.

Therefore, I don't think we should ship this package in Bullseye.

Any objection to removing the package from testing & sid?

This is a leaf package and popcon is 4/19 (vote/inst).

[1] https://mail.gnome.org/archives/gtk-perl-list/2020-October/msg2.html


I don't think that libgstreamer1-perl as found in Debian is the one  
provided by GNOME/Gtk / referenced in the given URL / deprecation  
announcement.


Nonetheless, the upstream for libgstreamer1-perl has also been quite  
inactive over the past years. I will ping Perl people that I know if  
they are interested in taking over upstream maintenance.


However, I think the above reasoning is wrong / based on wrong  
upstream reference. Please check.


Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpxJ3ccrx3GL.pgp
Description: Digitale PGP-Signatur

Processed: thrift must be linked with libatomic on armel and mipsel

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:gnuradio
Bug #972948 [src:thrift] thrift must be linked with libatomic on armel and 
mipsel
Added indication that 972948 affects src:gnuradio

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

Bug#972948: thrift must be linked with libatomic on armel and mipsel

[Adrian Bunk]

Source: thrift
Version: 0.13.0-4
Severity: serious
Tags: ftbfs patch
Control: affects -1 src:gnuradio

https://buildd.debian.org/status/logs.php?pkg=thrift&ver=0.13.0-4

...
dpkg-shlibdeps: warning: symbol __atomic_load_8 used by 
debian/libthrift-0.13.0/usr/lib/mipsel-linux-gnu/libthrift-0.13.0.so found in 
none of the libraries
dpkg-shlibdeps: warning: symbol __atomic_store_8 used by 
debian/libthrift-0.13.0/usr/lib/mipsel-linux-gnu/libthrift-0.13.0.so found in 
none of the libraries
...


Fix/workaround:

--- debian/rules.old2020-10-26 08:49:09.892500470 +
+++ debian/rules2020-10-26 08:49:55.572083074 +
@@ -9,6 +9,10 @@
 
 export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions
 
+ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel))
+  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic 
-Wl,--as-needed
+endif
+
 # for Go install
 export DH_GOPKG=thrift
 export XDG_CACHE_HOME=$(CURDIR)/go-cache/

Bug#963644: marked as done (alembic: FTBFS with Sphinx 3.1: AttributeError: 'tuple' object has no attribute 'docname')

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 14:33:31 +
with message-id 
and subject line Bug#963644: fixed in alembic 1.4.3-1
has caused the Debian Bug report #963644,
regarding alembic: FTBFS with Sphinx 3.1: AttributeError: 'tuple' object has no 
attribute 'docname'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
963644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alembic
Version: 1.4.2-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx3.1

Hi,

alembic fails to build with Sphinx 3.1, currently available in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 -m sphinx -b html docs/build 
> /<>/debian/alembic/usr/share/doc/alembic/html
> Running Sphinx v3.1.1
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 20 source files that are out of date
> updating environment: [new config] 20 added, 0 changed, 0 removed
> reading sources... [  5%] api/autogenerate
> reading sources... [ 10%] api/commands
> The name of the builder is: htmlThe name of the builder is: html
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/domains/python.py", line 1194, 
> in clear_doc
> if obj.docname == docname:
> AttributeError: 'tuple' object has no attribute 'docname'
> The full traceback has been saved in /tmp/sphinx-err-kjfkd0mk.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/23/alembic_1.4.2-1_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.

Also see [2] for the list of deprecated/removed APIs and possible alternatives
to them.

Sphinx 3.1 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/3.x/changes.html
[2]: https://www.sphinx-doc.org/en/3.x/extdev/deprecated.html

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: alembic
Source-Version: 1.4.3-1
Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= 

We believe that the bug you reported is fixed in the latest version of
alembic, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated alembic package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Oct 2020 14:48:56 +0100
Source: alembic
Architecture: source
Version: 1.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Ondřej Nový 
Closes: 963644
Changes:
 alembic (1.4.3-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #963644).
   * d/control: Change Maintainer to Debian Python Team
 .
   * d/control: Fix wrong Vcs-*.
   * Add pytest 6.x support.
Checksums-Sha1:
 552f48d7a754bc33a2847c02f493d15d50b363f8 2302 alembic_1.4.3-1.dsc
 8327def06be88af30c500694ad6bb16ecd2aceab 475176 alembic_1.4.3.orig.tar.gz
 c0126566089249fd63da1fed452afe6810385e02 8364 alembic_1.4.3-1.debian.tar.xz
 ae2085e06464e1f35482ea1d0c1bd54f708c5ba9 8210 alembic_1.4.3-1_amd64.buildinfo
Checksums-Sha256:
 89b461714dca1416bc663bfdaca977f6c7f543bd1ab5a1bf78b2e040ef122f27 2302 
alembic_1.4.3-1.dsc
 1bb67f

Bug#962813: marked as done (does not build with ghc 8.8)

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 14:33:59 +
with message-id 
and subject line Bug#962813: fixed in haskell-tree-monad 0.3.1-1
has caused the Debian Bug report #962813,
regarding does not build with ghc 8.8
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
962813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-tree-monad
Severity: critical

Hello,

this package does not build with the up-comming ghc 8.8 version.
It is not part of stackage LTS, and it was not updated by upstream since 2009.
It means that there is few chance to see the upstream fix this issue.

so it is considere to remove it from Debian.

Someone can salvage it by providing a patch (prefereably to the upstream first).

Cheers
 


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

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: haskell-tree-monad
Source-Version: 0.3.1-1
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
haskell-tree-monad, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 962...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated haskell-tree-monad 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Oct 2020 15:00:12 +0100
Source: haskell-tree-monad
Architecture: source
Version: 0.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Mike Gabriel 
Closes: 962813
Changes:
 haskell-tree-monad (0.3.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fix FTBS against recent ghc versions. (Closes: #962813).
   * debian/control:
 + Bump Standards-Version: to 4.5.0. No changes needed.
 + Update Homepage: field.
   * debian/copyright:
 + Update Upstream-Contact: field.
Checksums-Sha1:
 dccc20190d2b738d908548de982c239b8d1160ba 2407 haskell-tree-monad_0.3.1-1.dsc
 4befc6f15a67c9b4c86758b7ecd6a7ce4490a2f3 2540 
haskell-tree-monad_0.3.1.orig.tar.gz
 4d69ec623956cb742d63f0c48c8863a71134bd2c 2688 
haskell-tree-monad_0.3.1-1.debian.tar.xz
 90c6289453f3f19291d5c91907d7a5a9cb84664b 7677 
haskell-tree-monad_0.3.1-1_source.buildinfo
Checksums-Sha256:
 36df0fd09d340c653f6cef13d655e62d200644ef2ba269e8409067fa4a3b60eb 2407 
haskell-tree-monad_0.3.1-1.dsc
 0ebee80159a049abb9fb1b677a70c1d19628c2fae2bf314e4496bff97c3ec55b 2540 
haskell-tree-monad_0.3.1.orig.tar.gz
 1fb77ba98e8cb22a8c2302fd5b3b9cfa3292d8935fd5f821db856c64ad3a79eb 2688 
haskell-tree-monad_0.3.1-1.debian.tar.xz
 842d3233cc25067fa6c2746c93af14285957334a6f3cc47800065bfd80b921ef 7677 
haskell-tree-monad_0.3.1-1_source.buildinfo
Files:
 d87e43bb48484558d4d8857e36f2fac3 2407 haskell optional 
haskell-tree-monad_0.3.1-1.dsc
 9f15a816a0e75ea535a5ca9378703227 2540 haskell optional 
haskell-tree-monad_0.3.1.orig.tar.gz
 5628e5eefda6d80fb55c46fb0f1c363b 2688 haskell optional 
haskell-tree-monad_0.3.1-1.debian.tar.xz
 7bb2dc193e98356edcc8c1582f480b6e 7677 haskell optional 
haskell-tree-monad_0.3.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl+W1oYVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxnP8P/RolZUNVhK3xe7MSOB0cq9BZ35U9
mfooTr5fs1/n9OmKTsqBx6N04AMfokymlGU+89H0P0BKeRbUni242qzV2IsUGTBa
EVe9h0Ptb0JrjG5iaDjIzp252zEdrY3BsDyp8MmwpgBxNVZZakgVafKx6/SQEzQZ
Gb73xTR22MCJD2CrfaEWBXv1G0vcuWAJoE7lq/QJSVmkeoTERsGyXhEVfK8/lnMZ
Bap0KFzyr808FR0ChZi5b070LNfl4i8tQglmUxl75MlxPUZ3zU8zqFQMEP5yux6N
QQdRAeMLlznybFJiY9kjsn7FeDsOYt8skHbxtINWnE1amE7GsolByxYOVotUgaw9
EJFNlqnczehz/nYThIPUAPlZBdXLi46mcFxQCrjaCrAUqu7TI2n4Ld4TJBHyASZS
VMBBf4HjFBOT3Ni2KmUC/Mw2VSThFXy0+Dzv+vCI8EIp0Iq44PDr24tGuvOxIwS+
EqR1ebtrh2C60CWtcpqfw3EWQpMqJ2gJh8UFo9

Processed: lxtask: diff for NMU version 0.1.9-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957510 + patch
Bug #957510 [src:lxtask] lxtask: ftbfs with GCC-10
Added tag(s) patch.
> tags 957510 + pending
Bug #957510 [src:lxtask] lxtask: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#957510: lxtask: diff for NMU version 0.1.9-1.1

[Adrian Bunk]

Control: tags 957510 + patch
Control: tags 957510 + pending

Dear maintainer,

I've prepared an NMU for lxtask (versioned as 0.1.9-1.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru lxtask-0.1.9/debian/changelog lxtask-0.1.9/debian/changelog
--- lxtask-0.1.9/debian/changelog	2019-03-02 02:43:13.0 +0200
+++ lxtask-0.1.9/debian/changelog	2020-10-26 16:39:19.0 +0200
@@ -1,3 +1,11 @@
+lxtask (0.1.9-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add fix for FTBFS with gcc 10, thanks to Hanno Böck
+and Páder Rezső. (Closes: #957510)
+
+ -- Adrian Bunk   Mon, 26 Oct 2020 16:39:19 +0200
+
 lxtask (0.1.9-1) unstable; urgency=medium
 
   * Merging upstream version 0.1.9.
diff -Nru lxtask-0.1.9/debian/patches/lxtask-fix-no-common.patch lxtask-0.1.9/debian/patches/lxtask-fix-no-common.patch
--- lxtask-0.1.9/debian/patches/lxtask-fix-no-common.patch	1970-01-01 02:00:00.0 +0200
+++ lxtask-0.1.9/debian/patches/lxtask-fix-no-common.patch	2020-10-26 16:38:11.0 +0200
@@ -0,0 +1,73 @@
+diff -Naur a/src/interface.c b/src/interface.c
+--- a/src/interface.c	2016-02-21 01:06:17.0 +0100
 b/src/interface.c	2016-09-13 19:37:28.038350050 +0200
+@@ -26,6 +26,18 @@
+ #include 
+ #include "interface.h"
+ 
++GtkTreeStore *list_store;
++GtkTreeSelection *selection;
++GtkWidget *treeview;
++GtkWidget *mainmenu;
++GtkWidget *taskpopup;
++GtkWidget *cpu_usage_progress_bar;
++GtkWidget *mem_usage_progress_bar;
++GtkWidget *cpu_usage_progress_bar_box;
++GtkWidget *mem_usage_progress_bar_box;
++
++GtkTreeViewColumn *column;
++
+ #define GLADE_HOOKUP_OBJECT(component,widget,name) \
+   g_object_set_data_full (G_OBJECT (component), name, \
+ gtk_widget_ref (widget), (GDestroyNotify) gtk_widget_unref)
+diff -Naur a/src/interface.h b/src/interface.h
+--- a/src/interface.h	2014-09-16 14:27:52.0 +0200
 b/src/interface.h	2016-09-13 19:32:22.816372893 +0200
+@@ -38,16 +38,15 @@
+ #include "callbacks.h"
+ #include "types.h"
+ 
+-GtkTreeStore *list_store;
+-GtkTreeSelection *selection;
+-GtkWidget *treeview;
+-GtkWidget *mainmenu;
+-GtkWidget *taskpopup;
+-GtkWidget *priopopup;
+-GtkWidget *cpu_usage_progress_bar;
+-GtkWidget *mem_usage_progress_bar;
+-GtkWidget *cpu_usage_progress_bar_box;
+-GtkWidget *mem_usage_progress_bar_box;
++extern GtkTreeStore *list_store;
++extern GtkTreeSelection *selection;
++extern GtkWidget *treeview;
++extern GtkWidget *mainmenu;
++extern GtkWidget *taskpopup;
++extern GtkWidget *cpu_usage_progress_bar;
++extern GtkWidget *mem_usage_progress_bar;
++extern GtkWidget *cpu_usage_progress_bar_box;
++extern GtkWidget *mem_usage_progress_bar_box;
+ 
+ enum {
+ COLUMN_NAME = 0,
+@@ -61,7 +60,7 @@
+ COLUMN_PPID
+ };
+ 
+-GtkTreeViewColumn *column;
++extern GtkTreeViewColumn *column;
+ 
+ void change_list_store_view(void);
+ void create_list_store(void);
+diff -Naur a/src/types.h b/src/types.h
+--- a/src/types.h	2014-09-16 14:27:52.0 +0200
 b/src/types.h	2016-09-13 19:25:51.014402217 +0200
+@@ -77,9 +77,6 @@
+ extern gint win_width;
+ extern gint win_height;
+ 
+-const gchar *custom_signal_0;
+-const gchar *custom_signal_1;
+-
+ extern int page_size;
+ 
+ #endif
diff -Nru lxtask-0.1.9/debian/patches/series lxtask-0.1.9/debian/patches/series
--- lxtask-0.1.9/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ lxtask-0.1.9/debian/patches/series	2020-10-26 16:39:16.0 +0200
@@ -0,0 +1 @@
+lxtask-fix-no-common.patch

Processed: Re: sibelia: autopkgtest arm64 failure: times out after multial.c:459: readSubstMatrix: Assertion `file` failed.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #959059 [src:sibelia] sibelia: autopkgtest arm64 failure: times out after 
multial.c:459: readSubstMatrix: Assertion `file` failed.
Added tag(s) moreinfo.
> tags -1 unreproducible
Bug #959059 [src:sibelia] sibelia: autopkgtest arm64 failure: times out after 
multial.c:459: readSubstMatrix: Assertion `file` failed.
Added tag(s) unreproducible.

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

Bug#959059: sibelia: autopkgtest arm64 failure: times out after multial.c:459: readSubstMatrix: Assertion `file` failed.

[Nilesh]

Control: tags -1 moreinfo
Control: tags -1 unreproducible

Hi,

On Tue, 28 Apr 2020 21:54:05 +0200 Paul Gevers  wrote:

> Source: sibelia
> Version: 3.0.7+dfsg-3
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fails-always timesout
>
> Dear maintainer(s),
>
> Your new package sibelia has an autopkgtest, great. However, it fails on
> arm64 because it times out. I copied some of the output at the bottom of
> this report.
>
> Currently this regression is blocking the migration to testing [1]. Can
> you please investigate the situation and fix it?
>
> More information about this bug and the reason for filing it can be
found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
>
> Paul
>
> [1] https://qa.debian.org/excuses.php?package=sibelia
>
>
https://ci.debian.net/data/autopkgtest/testing/arm64/s/sibelia/5172443/log.gz
>
> autopkgtest [19:32:15]: test run-unit-test: [---
> + cd C-Sibelia/Staphylococcus_aureus
> + C-Sibelia.py NCTC8325.fasta RN4220.fasta
> Simplification stage 1 of 3
> Enumerating vertices of the graph, then performing bulge removal...
> [..]
> Simplification stage 2 of 3
> Enumerating vertices of the graph, then performing bulge removal...
> [..]
> Simplification stage 3 of 3
> Enumerating vertices of the graph, then performing bulge removal...
> [..]
> Finding synteny blocks and generating the output...
> Calculating synteny blocks...
> Calling variants...
> An error occured: b"mlagan: multial.c:459: readSubstMatrix: Assertion
> `file' failed.\n"
> autopkgtest [22:18:56]: ERROR: timed out on command "su -s /bin/bash
> debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
> true; . ~/.profile >/dev/null 2>&1 || true;
> buildtree="/tmp/autopkgtest-lxc.cdi3m4hf/downtmp/build.oIa/src"; mkdir
> -p -m 1777 --
> "/tmp/autopkgtest-lxc.cdi3m4hf/downtmp/run-unit-test-artifacts"; export
>
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.cdi3m4hf/downtmp/run-unit-test-artifacts";
> export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
> "/tmp/autopkgtest-lxc.cdi3m4hf/downtmp/autopkgtest_tmp"; export
> AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.cdi3m4hf/downtmp/autopkgtest_tmp";
> export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
> export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=32; unset
> LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY
> LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
> LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
> $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
> /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod

> +x


It passes for me in an arm64 schroot. Futher more, it passes even armhf
as per CI logs[1]. This creates further suspicion for not passing on arm64
Is this an occasional failure, or am I missing something here? - Please
let me know.

[1]:
https://ci.debian.net/data/autopkgtest/testing/armhf/s/sibelia/7169740/log.gz

Kind Regards,
Nilesh

Bug#972952: node-mkdirp 1.0 is incompatible with 0.5, breaks yarnpkg

[anomie]

Package: node-mkdirp
Version: 1.0.4-2
Severity: critical

I don't know whether to report this against node-mkdirp for breaking
compatibility, or yarnpkg for depending on "node-mkdirp (>= 0.5.1)"
rather than "node-mkdirp (>= 0.5.1), node-mkdirp (<<1.0.0)". Either way,
things are currently broken in unstable and shouldn't migrate to
testing.

I upgraded various packages this morning, and found that yarn would no
longer work.

  $ yarn
  yarn install v1.22.4
  warning Skipping preferred cache folder "/home/redacted/.cache/yarn" because 
it is not writable.
  warning Skipping preferred cache folder "/tmp/.yarn-cache-1000" because it is 
not writable.
  warning Skipping preferred cache folder "/tmp/.yarn-cache" because it is not 
writable.
  error Yarn hasn't been able to find a cache folder it can use. Please use the 
explicit --cache-folder option to tell it what location to use, or make one of 
the preferred locations writable.
  info Visit https://yarnpkg.com/en/docs/cli/install for documentation about 
this command.

This turns out to be due to this error being thrown:

  TypeError: invalid options argument
at optsArg (/usr/share/nodejs/mkdirp/lib/opts-arg.js:13:11)
at mkdirp (/usr/share/nodejs/mkdirp/index.js:11:10)
at /usr/share/nodejs/yarn/lib/util/promise.js:37:10
at new Promise ()
at /usr/share/nodejs/yarn/lib/util/promise.js:17:12
at Object. (/usr/share/nodejs/yarn/lib/util/fs.js:1024:15)
at Generator.throw ()
at step (/usr/share/nodejs/babel-runtime/helpers/asyncToGenerator.js:17:30)
at /usr/share/nodejs/babel-runtime/helpers/asyncToGenerator.js:30:13

It turns out yarn is expecting node-mkdirp to accept a callback, which
was apparently dropped in node-mkdirp 1.0 in favor of it returning a
promise.

Downgrading node-mkdirp to 0.5.1-2 fixed it:

  $ yarn
  yarn install v1.22.4
  info No lockfile found.
  [1/4] Resolving packages...
  [2/4] Fetching packages...
  [3/4] Linking dependencies...
  [4/4] Building fresh packages...
  success Saved lockfile.
  Done in 0.07s.

Processed: gthumb: diff for NMU version 3:3.8.3-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 948197 + patch
Bug #948197 [src:gthumb] gthumb: CVE-2019-20326: Heap buffer overflow
Added tag(s) patch.
> tags 948197 + pending
Bug #948197 [src:gthumb] gthumb: CVE-2019-20326: Heap buffer overflow
Added tag(s) pending.

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

Bug#952262: marked as done (psgml: FTBFS: Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.)

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 15:05:11 +
with message-id 
and subject line Bug#952262: fixed in psgml 1.4.0-7.2
has caused the Debian Bug report #952262,
regarding psgml: FTBFS: Malformed UTF-8 character (fatal) at 
/usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
952262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psgml
Version: 1.4.0-7.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> == making target explode [new prereqs: ]==
> test ! -d debian/cdtd && (cd debian && uudecode debian.uue \
>&& tar zfx debian.tar.gz && rm -f debian.tar.gz )
> make[1]: Leaving directory '/<>'
> ./configure --verbose --prefix=/usr --infodir=/usr/share/info \
>  --sysconfdir=/etc --build x86_64-linux-gnu  
> creating cache ./config.cache
> checking whether make sets ${MAKE}... yes
> checking for a BSD compatible install... /usr/bin/install -c
> checking for emacs... no
> checking for xemacs... no
> checking for makeinfo... /usr/bin/makeinfo
> updating cache ./config.cache
> creating ./config.status
> creating Makefile
> touch stamp-conf
> == making target stamp-configure-indep [new prereqs: CONFIG-indep]==
> == making target CONFIG/psgml [new prereqs: stamp-configure-indep]==
> == making target configure-indep-stamp [new prereqs: 
> stamp-configure-indep psgml]==
> == making target configure-indep [new prereqs: 
> configure-indep-stamp]==
> == making target stamp-configure [new prereqs: configure-arch 
> configure-indep]==
> == making target BUILD-common [new prereqs: testdir stamp-configure]==
> == making target stamp-arch-build [new prereqs: BUILD-common]==
> == making target BUILD-arch [new prereqs: stamp-arch-build]==
> == making target stamp-build-arch [new prereqs: BUILD-arch]==
> == making target build-arch-stamp [new prereqs: stamp-build-arch]==
> == making target build-arch [new prereqs: build-arch-stamp]==
> == making target stamp-indep-build [new prereqs: BUILD-common]==
> == making target BUILD-indep [new prereqs: stamp-indep-build]==
> == making target stamp-build-indep [new prereqs: BUILD-indep]==
> == making target BUILD/psgml [new prereqs: stamp-build-indep]==
> == making target stamp-build-gnus [new prereqs: ]==
> bash -n debian/postinst
> bash -n debian/prerm
> bash -n debian/postrm
> bash -n debian/emacsen.remove
> bash -n debian/emacsen.install
> mkdir debian/html
> (cd debian/html; \
>  makeinfo --html --split=chapter -v -o . ../../psgml.texi)
> utf8 "\xE5" does not map to Unicode at 
> /usr/share/texinfo/Texinfo/ParserNonXS.pm line 1796,  line 1575.
> Malformed UTF-8 character: \xe5\x22\x0a (unexpected non-continuation byte 
> 0x22, immediately after start byte 0xe5; need 3 bytes, got 1) in pattern 
> match (m//) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.
> Malformed UTF-8 character (fatal) at 
> /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.
> make: *** [debian/local.mk:59: stamp-build-gnus] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/psgml_1.4.0-7.1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: psgml
Source-Version: 1.4.0-7.2
Done: Alberto Garcia 

We believe that the bug you reported is fixed in the latest version of
psgml, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 952...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alberto Garcia  (supplier of updated psgml package)

(This message was generated automatically at their request; if you
believe that there is a problem with it

Processed: affects 972246

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 972246 src:hyperspy
Bug #972246 [src:numba] numba ftbfs in unstable with python3.9 as supported 
python3 version
Added indication that 972246 affects src:hyperspy
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#972958: pipemeter FTBFS: error: format not a string literal and no format arguments

[Adrian Bunk]

Source: pipemeter
Version: 1.1.4-1
Severity: serious
Tags: ftbfs

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

...
   dh_auto_build -a
make -j4
make[1]: Entering directory '/<>'
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_CONFIG_H pipemeter.c -o pipemeter -Wl,-z,relro
pipemeter.c: In function ‘show_just_rate’:
pipemeter.c:400:5: error: format not a string literal and no format arguments 
[-Werror=format-security]
  400 | fprintf(stderr,trailer);
  | ^~~
pipemeter.c: In function ‘show_progress’:
pipemeter.c:490:3: error: format not a string literal and no format arguments 
[-Werror=format-security]
  490 |   fprintf(stderr, progressbar);
  |   ^~~
pipemeter.c:500:5: error: format not a string literal and no format arguments 
[-Werror=format-security]
  500 | fprintf(stderr,trailer);
  | ^~~
pipemeter.c: In function ‘parseopts’:
pipemeter.c:577:22: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  577 |   while(listdone=(int)fgets(listline,MAX_LINE,listfile)) {
  |  ^
cc1: some warnings being treated as errors
make[1]: *** [Makefile:10: pipemeter] Error 1

Bug#972957: libudev0-shim FTBFS: cannot find -ludev

[Adrian Bunk]

Source: libudev0-shim
Version: 1-1
Severity: serious
Tags: ftbfs

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

...
   dh_auto_build -a
make -j4 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
cc -Wall -Wextra -g -fvisibility=hidden -shared -fPIC -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-soname,libudev.so.0 -Wl,-z,now -Wl,-z,relro 
-Wl,--no-as-needed -ludev -Wl,--as-needed libudev0.c -o libudev.so.0.0.
/usr/bin/ld: cannot find -ludev
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:11: libudev.so.0.0.] Error 1

Bug#968274: marked as done (libzorpll-7.0-4-dev: missing (unversioned) Breaks+Replaces: libzorpll-7.0-1-dev)

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 16:03:42 +
with message-id 
and subject line Bug#968274: fixed in libzorpll 7.0.4.0-2
has caused the Debian Bug report #968274,
regarding libzorpll-7.0-4-dev: missing (unversioned) Breaks+Replaces: 
libzorpll-7.0-1-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
968274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libzorpll-7.0-4-dev
Version: 7.0.4.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package libzorpll-7.0-4-dev.
  Preparing to unpack .../libzorpll-7.0-4-dev_7.0.4.0-1_amd64.deb ...
  Unpacking libzorpll-7.0-4-dev (7.0.4.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libzorpll-7.0-4-dev_7.0.4.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/zorp-7.0/zorpll/blob.h', which is also in 
package libzorpll-7.0-1-dev 7.0.1.0~alpha1-1.1+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libzorpll-7.0-4-dev_7.0.4.0-1_amd64.deb

Since libzorpll-7.0-1-dev is gone, the B+R can be unversioned.

cheers,

Andreas


libzorpll-7.0-1-dev=7.0.1.0~alpha1-1.1+b1_libzorpll-7.0-4-dev=7.0.4.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libzorpll
Source-Version: 7.0.4.0-2
Done: SZALAY Attila 

We believe that the bug you reported is fixed in the latest version of
libzorpll, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 968...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
SZALAY Attila  (supplier of updated libzorpll package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 29 Aug 2020 22:32:39 +0200
Source: libzorpll
Architecture: source
Version: 7.0.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: SZALAY Attila 
Changed-By: SZALAY Attila 
Closes: 968274
Changes:
 libzorpll (7.0.4.0-2) unstable; urgency=medium
 .
   * [8784a53] Fix upgrade issue if libzorpll-7.0-1-dev is installed
 (Closes: #968274)
Checksums-Sha1:
 adf3c41cea394422c450f62029c3f2443802afd2 2042 libzorpll_7.0.4.0-2.dsc
 8a7930cae51a01ed00a789c9819d91a071f9 11160 
libzorpll_7.0.4.0-2.debian.tar.xz
 ff6c0c24ad58e824435e1dad6288fa8d04f3d97a 7949 
libzorpll_7.0.4.0-2_amd64.buildinfo
Checksums-Sha256:
 3801ea129b1185f97146ab4a2bca54630903683a9fae714fa817c0581e40f969 2042 
libzorpll_7.0.4.0-2.dsc
 973c733640395bd4506b007c5b5fb39b2ab41f17809cc47018beb204f6e40c5e 11160 
libzorpll_7.0.4.0-2.debian.tar.xz
 66139306dc8d586d44b847783174f27e93c6d0aff784f57d082acf095f229924 7949 
libzorpll_7.0.4.0-2_amd64.buildinfo
Files:
 8484347e9a7503cd50da6d0f6476336e 2042 libs optional libzorpll_7.0.4.0-2.dsc
 c53fe1c77b7c5b8b3ab7074e13e33780 11160 libs optional 
libzorpll_7.0.4.0-2.debian.tar.xz
 93aa9932bf94e458144ae92e5dbbc2c6 7949 libs optional 
libzorpll_7.0.4.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEDLxdlTMbVcF2xVjk+A0hGpn97vgFAl+W8GcQHHNhc2FAZGVi
aWFuLm9yZwAKCRD4DSEamf3u+ANND/4y6TsaHA58dICUtA8o4ygHyA3liafZSgfH
1schmLOzZmyiTuyEjijxG1COobFATGreByuNykHxwOLGbUsxArljIJ7uJisavkCI
tNqWf3Uap9gQGPDArVC8O2SvgwFH+vHS/Ml8q94TDtPHUIY2btJwuaeN6O+xL3xb
r9AyQJvy9cvvfiqQkwTRyBnyPxdoiMTcW4zUgVlShJJsXZ7uLXFHIXFtlKaRX5oG
9MeeLkqQe5WKruL6alQpnbrpKK04Ypx4iLKQCUwOCg6/+L3uNeVpxOjcHd11r/a+
GyTVqjhZX1ui1YtPMQQ8BP+5To3M/g6ucKmSretKJxx12q1ocThpmn6TWKTT3W6A
TkSQLRac4EcJs0lqEYkRXWENaKuCepw7VZrjLb9pstJEy+/S0S4Il1hR9Y2/LSDm
+K0ztPQPMs9oxD6BOiI4u68BYvRIUr3J8m1250uoFD9B2oqNN9cxXl+ar1oXbR2D
iT1216z0ICc3zocwuRO3ZmrX5PbuLPgSj6EHeJDFZyI2sdE+P/RX+tuS8/2+0C/l
IA9Fi2CrbkVSQzxRBJD+ORiQUr6YF5sNbJ80IwPddZqCKD0Yg0g1+WXM9TLu2VEd
Ph5EgHor9AsGq7y35nxN86mZm5unJGv9Fzv0HJvu9yGeNCQ

Bug#957510: lxtask: diff for NMU version 0.1.9-1.1

[Andriy Grytsenko]

>I've prepared an NMU for lxtask (versioned as 0.1.9-1.1) and uploaded
>it to DELAYED/14. Please feel free to tell me if I should cancel it.

Thank you very much. There is an issue with GIT which we tried to fix
and failed. It was what delayed the actual fix for so long. After all it
was decided to use another mirror of the GIT so update is going to come
pretty soon. Thank you very much again, your change wouldn't be forgotten
of course.

Bug#972961: pyemd FTBFS: test fails

[Adrian Bunk]

Source: pyemd
Version: 0.5.1-1
Severity: serious
Tags: ftbfs

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

...
   dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_pyemd/build; 
python3.9 -m pytest test
= test session starts 
==
platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0 -- 
/usr/bin/python3.9
cachedir: .pytest_cache
rootdir: /<>, inifile: pytest.ini
collecting ... collected 0 items / 2 errors

 ERRORS 
 ERROR collecting 
.pybuild/cpython3_3.9_pyemd/build/test/test_pyemd.py _
test/test_pyemd.py:9: in 
from pyemd import emd, emd_samples, emd_with_flow
../../../pyemd/__init__.py:75: in 
from .emd import emd, emd_with_flow, emd_samples
E   ModuleNotFoundError: No module named 'pyemd.emd'
 ERROR collecting 
.pybuild/cpython3_3.9_pyemd/build/test/test_pyemd.py _
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_pyemd/build/test/test_pyemd.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/_pytest/python.py:507: in _importtestmodule
mod = self.fspath.pyimport(ensuresyspath=importmode)
/usr/lib/python3/dist-packages/py/_path/local.py:704: in pyimport
__import__(modname)
/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:304: in load_module
exec(co, mod.__dict__)
test/test_pyemd.py:9: in 
from pyemd import emd, emd_samples, emd_with_flow
../../../pyemd/__init__.py:75: in 
from .emd import emd, emd_with_flow, emd_samples
E   ModuleNotFoundError: No module named 'pyemd.emd'
!!! Interrupted: 2 errors during collection 
=== 2 error in 0.28 seconds 

E: pybuild pybuild:352: test: plugin distutils failed with: exit code=2: cd 
/<>/.pybuild/cpython3_3.9_pyemd/build; python3.9 -m pytest test
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 
3.8" returned exit code 13
make: *** [debian/rules:8: binary-arch] Error 25

Bug#972827: marked as done (libgiac-dev: should include config.h)

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 16:34:13 +
with message-id 
and subject line Bug#972827: fixed in giac 1.6.0.25+dfsg1-2
has caused the Debian Bug report #972827,
regarding libgiac-dev: should include config.h
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
972827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgiac-dev
Version: 1.4.9.69+dfsg1-2
Severity: grave

Many Giac headers #include "config.h", and they use its contents in such
a way that config.h is essential to define the library ABI. (For
example, some members are gated behind #ifdef HAVE_LIBPTHREAD.)
Developing against Giac without the exact config.h generated during the
library build thus triggers an ABI mismatch, usually manifesting as a
segfault.

Requiring Giac’s config.h is unfortunate, and upstream recognizes it –
giac/gen.h includes the note

  // FIXME: macros defined in config.h are not welcome in a public header!

Until that FIXME is resolved, though, Debian needs to ship Giac’s
config.h with the other Giac headers.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: giac
Source-Version: 1.6.0.25+dfsg1-2
Done: Julien Puydt 

We believe that the bug you reported is fixed in the latest version of
giac, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated giac package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Oct 2020 16:44:10 +0100
Source: giac
Architecture: source
Version: 1.6.0.25+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Julien Puydt 
Closes: 972827
Changes:
 giac (1.6.0.25+dfsg1-2) unstable; urgency=medium
 .
   * Install config.h. (Closes: #972827)
Checksums-Sha1:
 577b0785238b1468e93cf3b0935189290f599ccd 2856 giac_1.6.0.25+dfsg1-2.dsc
 b7a5b89b573f2c8748877d6bfb70bdec3754a8c6 310484 
giac_1.6.0.25+dfsg1-2.debian.tar.xz
 06d1be8ddad7cb58332ffe018aafbfb515d7bf1c 10212 
giac_1.6.0.25+dfsg1-2_source.buildinfo
Checksums-Sha256:
 47bbc9b383ae402d0e941a2c1c9c45cbed29a4a8b749a1a0c67200acea6737f6 2856 
giac_1.6.0.25+dfsg1-2.dsc
 6a81b8babded14ac072d7485a910b955d04a525c490e9a7e2d7dbdf36a6eecdb 310484 
giac_1.6.0.25+dfsg1-2.debian.tar.xz
 5dcb28861b8cbc7255ec90edfc0f7aeb06a92cc6201c70389134edea232dbce3 10212 
giac_1.6.0.25+dfsg1-2_source.buildinfo
Files:
 a18abf54503fa21de51a3d8044ceeb05 2856 science optional 
giac_1.6.0.25+dfsg1-2.dsc
 ce7357768e7e9f9ea27c35817dd79436 310484 science optional 
giac_1.6.0.25+dfsg1-2.debian.tar.xz
 b47c9df007eb3efe7193dfe6cd4bc62d 10212 science optional 
giac_1.6.0.25+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAl+W9Y8SHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRvEYP/2iRD55dI/mwRxo6H0JFMV4haTDcurMH
RxTC3E8SDiWmtyZhB+dG4L6cFFEIk8Gs6ebdnnXpw1SBcedXp76JEIo3bSAZrvdk
/8Fe3eLd2jGNMsLY5Iai9AhtT+F3oXJDPLMssNxOXSLMO6ognvc/JlOAJR6iOQ5y
wCESDnLaHI2f85EuZchR0knbP5lFg3caIzkUs/J40pLyP3Lo+BmRR7oJ3k/QbnoX
vB0rRA7eQztJAml0fyLAif3dndm7KWTUCDqKgAEfTsNFicc9bmCQIaUhz42n2Lya
FWe7dqp4i93W/X2sGilR0r+MBhqrSW1II/5zl4XOP/UIXxbfI3UVRlwvjc/Rb3dN
zEzmjzz7PdA8faQXLkdttGnRUHaSarcQKN+DsLmMYMJr8s7zXIS8phfZ9oDIkWi2
f7JDPH4CGmVzZfniqHLNCDLt+xYJV/IDuzrQJi6f7WkTOLp6wKsRjRuMkXen8OP6
z2m/+SIUeNJsCS4ON5fdKoHxUzw1mOcOrctA9igBXKo/t0rCAR/WV/7n+NTDnV2p
E0i/Z628lrz1Va41Rwaxm+rOYeizBUnuD9QJ/a6pqCIOu+pUHwRhsp+Ba2kOe7qz
astWNE05HVTzFcQLcLNRsWAfso5THoo31HiXmD7AwZ3OYUVRZlqXTFEul6xODBLc
96P2k8xpvCsT
=M4TX
-END PGP SIGNATURE End Message ---

Bug#972772: marked as done (pybdsf ftbfs with python3.9)

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 16:35:10 +
with message-id 
and subject line Bug#972772: fixed in pybdsf 1.9.2-3
has caused the Debian Bug report #972772,
regarding pybdsf ftbfs with python3.9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
972772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pybdsf
Version: 1.9.2-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

pybdsf ftbfs with python3.9 (python3-defaults from experimenal):

https://people.debian.org/~ginggs/python3.9-default/pybdsf_1.9.2-2build1_amd64-2020-10-22T13:21:38Z.build

[...]


compile options: '-Ibuild/src.linux-x86_64-3.8/build/src.linux-x86_64-3.8/bdsf
-I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.8 -c'
x86_64-linux-gnu-gcc:
build/src.linux-x86_64-3.8/build/src.linux-x86_64-3.8/bdsf/fortranobject.c
x86_64-linux-gnu-gcc: build/src.linux-x86_64-3.8/bdsf/_pytesselatemodule.c
In file included from
build/src.linux-x86_64-3.8/build/src.linux-x86_64-3.8/bdsf/fortranobject.c:2:
build/src.linux-x86_64-3.8/build/src.linux-x86_64-3.8/bdsf/fortranobject.h:7:10:
fatal error: Python.h: No such file or directory
7 | #include "Python.h"
  |  ^~
compilation terminated.
build/src.linux-x86_64-3.8/bdsf/_pytesselatemodule.c:14:10: fatal error:
Python.h: No such file or directory
   14 | #include "Python.h"
  |  ^~
compilation terminated.
error: Command "x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare
-DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
-Werror=format-security -g -fwrapv -O2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-Ibuild/src.linux-x86_64-3.8/build/src.linux-x86_64-3.8/bdsf
-I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.8 -c
build/src.linux-x86_64-3.8/build/src.linux-x86_64-3.8/bdsf/fortranobject.c -o
build/temp.linux-x86_64-3.8/build/src.linux-x86_64-3.8/build/src.linux-x86_64-3.8/bdsf/fortranobject.o
-MMD -MF
build/temp.linux-x86_64-3.8/build/src.linux-x86_64-3.8/build/src.linux-x86_64-3.8/bdsf/fortranobject.o.d"
failed with exit status 1
--- End Message ---
--- Begin Message ---
Source: pybdsf
Source-Version: 1.9.2-3
Done: Ole Streicher 

We believe that the bug you reported is fixed in the latest version of
pybdsf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated pybdsf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Oct 2020 10:02:02 +0100
Source: pybdsf
Architecture: source
Version: 1.9.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Maintainers 

Changed-By: Ole Streicher 
Closes: 972772
Changes:
 pybdsf (1.9.2-3) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure URI in Homepage field
   * Set upstream metadata fields: Bug-Submit, Repository, Repository-Browse
 .
   [ Ole Streicher ]
   * Fix build dependencies (Closes: #972772)
Checksums-Sha1:
 75073094191d6dd2325898034acfc2bc279ffeb1 2072 pybdsf_1.9.2-3.dsc
 b9713371f1e4a9a8a5398d986447c5eaa2e12817 5500 pybdsf_1.9.2-3.debian.tar.xz
Checksums-Sha256:
 5fb83b9929c2b3fb3d4dc52116ad13b98c780cee39599301e9266f6e6e83ffb3 2072 
pybdsf_1.9.2-3.dsc
 4a6a70408a5d1553556d4a2ffd77e64f9d2804ecc83cd989449c78c61493864f 5500 
pybdsf_1.9.2-3.debian.tar.xz
Files:
 9607937ddce3ba6d4f9c327da682beae 2072 python optional pybdsf_1.9.2-3.dsc
 0f3d59de7caf4087d908c35470210b5e 5500 python optional 
pybdsf_1.9.2-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl+Wkc4ACgkQcRWv0HcQ
3Pe0IBAAn/4f4+FktMhXhHELT0r4SrvMJmUjqTTzwSLSv++gjDQWAwwYDek2nCt1
7lB0DmSuXKl4bn9bGcbc5rP73FgQUI8oMjB49Lx4UAACV/X7NifRHU1IDpLQOCWw
pDEB27xVu5RJi7dBkRKaPwl6NWCD7i8FPBloABehSCXTaGFnF4a5GcUAn4HCN7iX
lr863idEdw0uvhk9ZX3KOeNFPW2piDznlgmEgp0Za4h7/MZsK/CtuZ8DDJad//az
iAQC4OVitSYHgAQL3wCi4wNc5XB0fynuv6CQgNHuT5vO9KLVus

Processed: bumping severity, unusable with wireguard

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 1.27.90-3
Bug #972688 [network-manager] 1.27.91-1 blows away existing dns nameservers 
when VPN activates
No longer marked as found in versions network-manager/1.27.90-3.
> found -1 1.27.91-1
Bug #972688 [network-manager] 1.27.91-1 blows away existing dns nameservers 
when VPN activates
Marked as found in versions network-manager/1.27.91-1.
> severity -1 serious
Bug #972688 [network-manager] 1.27.91-1 blows away existing dns nameservers 
when VPN activates
Severity set to 'serious' from 'normal'

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

Bug#957640: openntpd: diff for NMU version 1:6.2p3-4.1

[Sudip Mukherjee]

Control: tags 957640 + patch
Control: tags 957640 + pending
--

Dear maintainer,

I've prepared an NMU for openntpd (versioned as 1:6.2p3-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru openntpd-6.2p3/debian/changelog openntpd-6.2p3/debian/changelog
--- openntpd-6.2p3/debian/changelog 2018-08-17 22:43:06.0 +0100
+++ openntpd-6.2p3/debian/changelog 2020-10-26 17:10:47.0 +
@@ -1,3 +1,10 @@
+openntpd (1:6.2p3-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957640)
+
+ -- Sudip Mukherjee   Mon, 26 Oct 2020 17:10:47 
+
+
 openntpd (1:6.2p3-4) unstable; urgency=medium
 
   * Fix FTBFS on autoconf-1.15. Thanks sanvila@! (Closes: #906497).
diff -Nru openntpd-6.2p3/debian/patches/fix_gcc-10.patch 
openntpd-6.2p3/debian/patches/fix_gcc-10.patch
--- openntpd-6.2p3/debian/patches/fix_gcc-10.patch  1970-01-01 
01:00:00.0 +0100
+++ openntpd-6.2p3/debian/patches/fix_gcc-10.patch  2020-10-26 
16:23:34.0 +
@@ -0,0 +1,55 @@
+Description: Fix ftbfs with GCC-10
+
+Ported from 
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e1b05d95f42a73c2b5a4f6bd78fa2dc25d81b1bc
+Original Author: Paul B. Henson 
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957640
+Forwarded: no
+
+---
+
+--- openntpd-6.2p3.orig/include/sys/types.h
 openntpd-6.2p3/include/sys/types.h
+@@ -22,6 +22,10 @@
+ # define __bounded__(x, y, z)
+ #endif
+ 
++#if !defined(HAVE_ATTRIBUTE__PACKED) && !defined(__packed)
++# define __packed __attribute__((__packed__))
++#endif
++
+ /*
+  * Define BSD-style unsigned bits types for systems that do not have them.
+  */
+--- openntpd-6.2p3.orig/src/ntp_dns.c
 openntpd-6.2p3/src/ntp_dns.c
+@@ -33,7 +33,7 @@
+ #include "ntpd.h"
+ 
+ volatile sig_atomic_t  quit_dns = 0;
+-struct imsgbuf*ibuf_dns;
++static struct imsgbuf  *ibuf_dns;
+ 
+ void  sighdlr_dns(int);
+ int   dns_dispatch_imsg(void);
+--- openntpd-6.2p3.orig/src/parse.c
 openntpd-6.2p3/src/parse.c
+@@ -101,7 +101,6 @@ int lgetc(int);
+ intlungetc(int);
+ intfindeol(void);
+ 
+-struct ntpd_conf  *conf;
+ struct sockaddr_in query_addr4;
+ struct sockaddr_in6query_addr6;
+ 
+--- openntpd-6.2p3.orig/src/parse.y
 openntpd-6.2p3/src/parse.y
+@@ -57,7 +57,6 @@ int   lgetc(int);
+ intlungetc(int);
+ intfindeol(void);
+ 
+-struct ntpd_conf  *conf;
+ struct sockaddr_in query_addr4;
+ struct sockaddr_in6query_addr6;
+ 
diff -Nru openntpd-6.2p3/debian/patches/series 
openntpd-6.2p3/debian/patches/series
--- openntpd-6.2p3/debian/patches/series2017-06-12 15:46:01.0 
+0100
+++ openntpd-6.2p3/debian/patches/series2020-10-26 16:16:59.0 
+
@@ -2,3 +2,4 @@
 02-syslog.patch
 03-kfreebsd.patch
 04-ntpd-manpage.patch
+fix_gcc-10.patch

Processed: openntpd: diff for NMU version 1:6.2p3-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957640 + patch
Bug #957640 [src:openntpd] openntpd: ftbfs with GCC-10
Added tag(s) patch.
> tags 957640 + pending
Bug #957640 [src:openntpd] openntpd: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#972158: closed by Debian FTP Masters (reply to Dmitry Shachnev ) (Bug#972158: fixed in falkon 3.1.0+dfsg1-9)

[Dmitry Shachnev]

Hi Georges!

On Mon, Oct 26, 2020 at 10:06:03AM +, Debian Bug Tracking System wrote:
>[ Georges Khaznadar ]
>* adopted Dmitry Shachnev's fix, thank you Dmitry!

Thank you for uploading it! I have cancelled my NMU now.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#972156: kylin-video: FTBFS with Qt 5.15

[Dmitry Shachnev]

Control: reopen -1
Control: found -1 kylin-video/2.1.1-1
Control: forwarded -1 https://github.com/UbuntuKylin/kylin-video/pull/24

Hi!

On Mon, Oct 26, 2020 at 07:56:51PM +0800, handsome_feng wrote:
> Hi, Dmitry,
>
> Sorry for the delay and thanks a lot for your NMU. <&
>
> I will upload the new upstream release to the archive ASAP.

Sorry, but I have to reopen this bug :(

The new upstream release added QPainterPath use in src/systembutton.cpp
(see commit 17ac4742a24b758d) and there is no QPainterPath include, so
it fails to build with Qt 5.15 again:

  systembutton.cpp: In member function ‘virtual void 
SystemButton::paintEvent(QPaintEvent*)’:
  systembutton.cpp:105:22: error: aggregate ‘QPainterPath path’ has incomplete 
type and cannot be defined
105 | QPainterPath path;
|  ^~~~

Please apply https://github.com/UbuntuKylin/kylin-video/pull/24 to fix it,
with that change it builds fine.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: Re: Bug#972156: kylin-video: FTBFS with Qt 5.15

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #972156 {Done: handsome_feng } 
[src:kylin-video] kylin-video: FTBFS with Qt 5.15: error: aggregate 
'QPainterPath bg_path' has incomplete type and cannot be defined
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions kylin-video/2.1.1-1.
> found -1 kylin-video/2.1.1-1
Bug #972156 [src:kylin-video] kylin-video: FTBFS with Qt 5.15: error: aggregate 
'QPainterPath bg_path' has incomplete type and cannot be defined
Marked as found in versions kylin-video/2.1.1-1.
> forwarded -1 https://github.com/UbuntuKylin/kylin-video/pull/24
Bug #972156 [src:kylin-video] kylin-video: FTBFS with Qt 5.15: error: aggregate 
'QPainterPath bg_path' has incomplete type and cannot be defined
Changed Bug forwarded-to-address to 
'https://github.com/UbuntuKylin/kylin-video/pull/24' from 
'https://github.com/UbuntuKylin/kylin-video/pull/6'.

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

Bug#972967: vmemcache FTBFS on armel/mipsel/powerpc: undefined reference to `__atomic_fetch_add_8'

[Adrian Bunk]

Source: vmemcache
Version: 0.8.1-1
Severity: serious
Tags: ftbfs patch

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

...
/usr/bin/ld: ../src/libvmemcache.so.0: undefined reference to 
`__atomic_fetch_add_8'
...


Fix/Workaround:

--- debian/rules.old2020-10-26 17:50:08.062846897 +
+++ debian/rules2020-10-26 17:50:29.654659998 +
@@ -3,7 +3,10 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 export DEB_CFLAGS_MAINT_APPEND  = -Wall -pedantic
-export DEB_LDFLAGS_MAINT_APPEND = -latomic
+
+ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel powerpc))
+  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic 
-Wl,--as-needed
+endif
 
 
 %:

Bug#972970: waffle: binary-all FTBFS

[Adrian Bunk]

Source: waffle
Version: 1.6.1-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=waffle&arch=all&ver=1.6.1-2&stamp=1603710782&raw=0

...
   dh_missing -i -O--buildsystem=cmake
dh_missing: warning: usr/usr/share/bash-completion/completions/wflinfo exists 
in debian/tmp but is not installed to anywhere 
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: libwaffle-1-0 (2), libwaffle-dev (10), libwaffle-doc 
(2), waffle-utils (2)
 * dh_installdocs: libwaffle-1-0 (0), libwaffle-dev (0), libwaffle-doc 
(0), waffle-utils (0)
 * dh_installman: libwaffle-1-0 (0), libwaffle-dev (0), libwaffle-doc 
(0), waffle-utils (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make: *** [debian/rules:9: binary-indep] Error 25

Bug#972971: atlas-ecmwf FTBFS on 32bit

[Adrian Bunk]

Source: atlas-ecmwf
Version: 0.22.0-4
Severity: serious
Tags: ftbfs

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

...
[ 58%] Building Fortran object 
src/atlas_f/CMakeFiles/atlas_ecmwf_f.dir/util/atlas_allocate_module.F90.o
cd /<>/obj-i686-linux-gnu/src/atlas_f && /usr/bin/gfortran 
-D_FILE_OFFSET_BITS=64 -Datlas_ecmwf_f_EXPORTS -I/<>/src 
-I/<>/obj-i686-linux-gnu/src 
-I/<>/obj-i686-linux-gnu/src/atlas_f 
-I/<>/obj-i686-linux-gnu/module -I/<>/src/atlas_f 
-I/usr/include/i386-linux-gnu -I/usr/include/i386-linux-gnu/eckit 
-I/usr/include/i386-linux-gnu/eckit/geometry 
-I/usr/include/i386-linux-gnu/eckit/linalg 
-I/usr/lib/i386-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/i386-linux-gnu/openmpi/include 
-I/usr/include/i386-linux-gnu/eckit/mpi 
-I/usr/include/i386-linux-gnu/eckit/option -I/usr/include/eigen3 
-I/usr/lib/i386-linux-gnu/fortran/gfortran-10/fckit 
-I/usr/include/i386-linux-gnu/fckit -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong 
-I/usr/lib/i386-linux-gnu/fortran/i686-linux-gnu-gfortran-10 -O3 -DNDEBUG 
-funroll-all-loops -finline-functions -J../../module -fPIC -fopenmp -c 
/<>/src/atlas_f/util/atlas_allocate_module.F90 -o 
CMakeFiles/atlas_ecmwf_f.dir/util/atlas_allocate_module.F90.o
/<>/src/atlas_f/util/atlas_allocate_module.F90:118:45:

  118 | subroutine atlas_allocate_managedmem_int32_r2( A, dims )
  | 1
..
  132 | subroutine atlas_allocate_managedmem_int64_r2_int32( A, dims )
  |   2
Error: Ambiguous interfaces in generic interface 'atlas_allocate_managedmem' 
for ‘atlas_allocate_managedmem_int32_r2’ at (1) and 
‘atlas_allocate_managedmem_int64_r2_int32’ at (2)
/<>/src/atlas_f/util/atlas_allocate_module.F90:278:47:

  278 | subroutine atlas_deallocate_managedmem_int32_r2( A )
  |   1
..
  286 | subroutine atlas_deallocate_managedmem_int64_r2( A )
  |   2
Error: Ambiguous interfaces in generic interface 'atlas_deallocate_managedmem' 
for ‘atlas_deallocate_managedmem_int32_r2’ at (1) and 
‘atlas_deallocate_managedmem_int64_r2’ at (2)
/<>/src/atlas_f/util/atlas_allocate_module.F90:290:37:

  290 |   call atlas__deallocate_managedmem( c_loc_int64(A(1,1)) )
  | 1
Error: Type mismatch in argument ‘x’ at (1); passed INTEGER(4) to INTEGER(8)
/<>/src/atlas_f/util/atlas_allocate_module.F90:258:37:

  258 |   call atlas__deallocate_managedmem( c_loc_int64(A(1)) )
  | 1
Error: Type mismatch in argument ‘x’ at (1); passed INTEGER(4) to INTEGER(8)
make[3]: *** [src/atlas_f/CMakeFiles/atlas_ecmwf_f.dir/build.make:1061: 
src/atlas_f/CMakeFiles/atlas_ecmwf_f.dir/util/atlas_allocate_module.F90.o] 
Error 1

Bug#971177: intake: FTBFS: TypeError: 'NoneType' object is not iterable

[Dmitry Shachnev]

Hi all!

On Mon, Oct 26, 2020 at 03:45:54PM +0200, Adrian Bunk wrote:
> The error is "FTBFS with Sphinx 3.2".
> Sphinx 3.2 entered unstable on August 9th.
>
> Dmitry (Cc'ed) might know more regarding what is the problem.

Let me explain what happens here:

- Sphinx' inspect module is capable of fetching the docstrings for parent
  classes when the child class does not have its own.

- To do that, it checks the __mro__ property that is defined for classes
  (and contains the tuple of parent classes).

- The top-level intake module (intake/__init__.py) defines a very generic
  __getattr__ function, which is defined this way:

def __getattr__(attr):
if attr == 'Catalog':
...

  If attr != 'Catalog', this function does not raise AttributeError exception
  (and returns None).

  So basically, that module has *every* possible attribute, including one
  named "__mro__" (and that attribute is None).

- Sphinx tries to iterate through __mro__ (because it expects it to be a
  tuple) but fails (because it's None, not a tuple).

To fix this, __getattr__('__mro__') should raise an AttributeError, not return
None.

So you can either:

- Remove that function completely (it is provided for compatibility reasons).

- Update to a newer upstream snapshot where that function is refactored and
  does raise AttributeError (see https://github.com/intake/intake/pull/526).

- Add these two lines as a temporary measure:

elif attr == '__mro__':
raise AttributeError

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#969936: marked as done (bullseye: add support, switch from /updates to -security)

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 18:18:24 +
with message-id 
and subject line Bug#969936: fixed in debian-lan-config 0.27
has caused the Debian Bug report #969936,
regarding bullseye: add support, switch from /updates to -security
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
969936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-lan-config
Version: 0.26
Severity: serious
File: /usr/share/debian-lan-config/fai/config/scripts/LAST/50-misc
User: debian-de...@lists.debian.org
Usertags: bullseye-security

The above script references $release/updates but when bullseye is
released that should be replaced by $release-security.

It looks like when a bullseye system is being installed, the setrel
function does not recognise the target release and so it won't setup
the apt sources.list at all.

Then even if the release were recognised properly, the script would
generate an incorrect sources.list using /updates instead of -security
which would cause the target system to not get security updates from
bullseye in a timely manner.

In addition, the SERVER_A sources.list references buster for the main
set of packages but uses stable/updates for security updates. This
means that after the bullseye release servers installed using the
debian-lan-config package will get packages from buster but their
security updates from bullseye, which seems incorrect.

   $  grep -A100 setrel 
./usr/share/debian-lan-config/fai/config/scripts/LAST/50-misc
   setrel() {

   # if release is not set, try to determine it

   if [ -n "$release" ]; then
return
   fi
   if [ ! -f $target/etc/os-release ]; then
return
   fi

   dists="jessie stretch buster bionic xenial trusty"
   for d in $dists; do
if grep -iq $d $target/etc/os-release; then
release=$d
break
fi
   done
   }

   # if installation was done from CD, replace useless sources.list
   setrel
   if [ -f $target/etc/apt/sources.list -a -n "$release" ]; then
   grep -q 'file generated by fai-cd' $target/etc/apt/sources.list && cat 
< $target/etc/apt/sources.list
   deb $apt_cdn/debian $release main contrib non-free
   deb $apt_cdn/debian-security $release/updates main contrib non-free
   #deb [trusted=yes] http://fai-project.org/download $release koeln
   EOF
   # if the package fai-server was installed, enable the project's 
repository
   if [ -f $target/var/lib/dpkg/info/fai-server.list ]; then
sed -i -e '/fai-project.org/s/^#//' $target/etc/apt/sources.list
   fi
   fi

   # for ARM architecture, we may need the kernel and initrd to boot or flash 
the device
   if ifclass ARM64; then
   cp -pv $target/boot/vmlinuz* $target/boot/initrd* $FAI_RUNDIR
   fi

   exit $error

   $ cat 
/usr/share/debian-lan-config/fai/config/files/etc/fai/apt/sources.list/SERVER_A
   deb http://deb.debian.org/debian/ buster main
   deb http://security.debian.org/ stable/updates main
   deb http://deb.debian.org/debian/ buster-updates main

   ## Backports repository:
   #deb http://deb.debian.org/debian/ buster-backports main

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

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

   debian-lan-config depends on no packages.

   debian-lan-config recommends no packages.

   Versions of packages debian-lan-config suggests:
   pn  fai-server  

   -- 
   bye,
   pabs

   https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: debian-lan-config
Source-Version: 0.27
Done: a...@debian.org (Andreas B. Mundt)

We believe that the bug you reported is fixed in the latest version of
debian-lan-config, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 969...@bugs.debian.org,
and the maintainer will 

Bug#972948: marked as done (thrift must be linked with libatomic on armel and mipsel)

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 18:19:08 +
with message-id 
and subject line Bug#972948: fixed in thrift 0.13.0-5
has caused the Debian Bug report #972948,
regarding thrift must be linked with libatomic on armel and mipsel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
972948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thrift
Version: 0.13.0-4
Severity: serious
Tags: ftbfs patch
Control: affects -1 src:gnuradio

https://buildd.debian.org/status/logs.php?pkg=thrift&ver=0.13.0-4

...
dpkg-shlibdeps: warning: symbol __atomic_load_8 used by 
debian/libthrift-0.13.0/usr/lib/mipsel-linux-gnu/libthrift-0.13.0.so found in 
none of the libraries
dpkg-shlibdeps: warning: symbol __atomic_store_8 used by 
debian/libthrift-0.13.0/usr/lib/mipsel-linux-gnu/libthrift-0.13.0.so found in 
none of the libraries
...


Fix/workaround:

--- debian/rules.old2020-10-26 08:49:09.892500470 +
+++ debian/rules2020-10-26 08:49:55.572083074 +
@@ -9,6 +9,10 @@
 
 export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions
 
+ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel))
+  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic 
-Wl,--as-needed
+endif
+
 # for Go install
 export DH_GOPKG=thrift
 export XDG_CACHE_HOME=$(CURDIR)/go-cache/
--- End Message ---
--- Begin Message ---
Source: thrift
Source-Version: 0.13.0-5
Done: Laszlo Boszormenyi (GCS) 

We believe that the bug you reported is fixed in the latest version of
thrift, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated thrift package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Oct 2020 18:01:44 +0100
Source: thrift
Architecture: source
Version: 0.13.0-5
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 972948
Changes:
 thrift (0.13.0-5) unstable; urgency=medium
 .
   * Update Standards-Version to 4.5.0 .
 .
   [ Adrian Bunk  ]
   * Link with libatomic on ARMel and MIPSel (closes: #972948).
Checksums-Sha1:
 d8866ce2d9fe2a30a05ae5ca5463124efdbbeef9 2977 thrift_0.13.0-5.dsc
 7f445791f763ec6c12d603e43c3eee4dabee183b 20156 thrift_0.13.0-5.debian.tar.xz
Checksums-Sha256:
 14cf1516030643e7cd65bf896cc9044cee32ccdffb835603e66507718ab209ae 2977 
thrift_0.13.0-5.dsc
 4d5df3c9f968183bf5f0fc170986526d571bd5e74477ed2b26ba8ca9e6a56de1 20156 
thrift_0.13.0-5.debian.tar.xz
Files:
 14928c821c27b88d506b105dd1a4b78e 2977 devel optional thrift_0.13.0-5.dsc
 954da3e2b617a0db66c1bb454b12d035 20156 devel optional 
thrift_0.13.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl+XD/QACgkQ3OMQ54ZM
yL9W4RAApIRY/juJCRguxkjrYL7mmLcHDa3OOmBFL1ivT2BIardSDnaN1yQgO/NC
H0bkTjvHuIyddk82uQvs3hVt/MuWu88W1pcyhxUrPKw+j/hlKt9Dzudo9zWnY6C6
o1+6ztwSpqL5jBzVS33dnjYcnWqowA2amzGFymQ/MhFgU702M2lmiIxakdPvQ3ps
O+PENOmXbBO+/gtlNssaK56pI1fLhdZsnqg51dG8zlf/yiZRJGUg2lbgaPNKh+PJ
5PSR9ZPSUcYCTVvYXMRtyHn4MoIl/0ySpjvf41rmhOmdu404yYpefYn7RiWx4Kjc
CsK9P8hRNSQnN/6ysAXdjvBth3SSl//voIcRs6nP5CRorMZAoQcR9/SPZfatpgVN
gyVDfCY+U4jV13US2kLvqmOTH+hrl8mtsoq1EghlAIP7K8xVYb+1fFG70wi413gp
GUriHV+R8wOpV6CTUbkZjlHyRtK7FVz36DSNOUZMzWNF1scQVaJKudj7firvUdqh
uGvgoN7rjRT8SMC8tkyA1RIr1Na+2eb0OTkp5ckmTioyUYSz5pxvwNd2V4A+LyQ+
vQpjr5k9qgsMVl+e5R76Go3JJDdbAHLIf9NiBzYRIPz6sy+cgxdIKDUndtsChvIv
CmMfEmmj6SFe9aylnxDtsaknvxPi98Tt1xdhFAwuBdRmB7qx8Kg=
=8pmG
-END PGP SIGNATURE End Message ---

Bug#972972: libcgi-application-server-perl FTBFS on IPV6-only buildds

[Adrian Bunk]

Source: libcgi-application-server-perl
Version: 0.063-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libcgi-application-server-perl&arch=all&ver=0.063-3&stamp=1603732518&raw=0

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
http_proxy= dh_auto_test
make -j4 test TEST_VERBOSE=1
make[2]: Entering directory '/<>'
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
"-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" 
t/*.t
t/00-compile.t . 
1..1
ok 1 - CGI::Application::Server loaded ok
ok
# 
# 
# Generated by Dist::Zilla::Plugin::ReportVersions::Tiny v1.08
# perl: 5.030003 (wanted any version) on linux from /usr/bin/perl
# 
# CGI   => 4.51   (want any version)
# CGI::Application  => 4.61   (want 4.21)   
# CGI::Application::Dispatch=> 3.12   (want any version)
# CGI::Application::Plugin::Redirect=> 1.00   (want any version)
# Carp  => 1.50   (want 0.01)   
# ExtUtils::MakeMaker   => 7.34   (want 6.30)   
# File::Find=> 1.36   (want any version)
# File::Temp=> 0.2309 (want any version)
# HTTP::Response=> 6.26   (want any version)
# HTTP::Server::Simple  => 0.52   (want 0.18)   
# HTTP::Server::Simple::CGI => (want any version)
# HTTP::Server::Simple::Static  => 0.14   (want 0.02)   
# HTTP::Status  => 6.26   (want any version)
# Scalar::Util  => 1.5(want 1.18)   
# Test::Exception   => 0.43   (want any version)
# Test::HTTP::Server::Simple=> 0.11   (want any version)
# Test::More=> 1.302162   (want 0.96)   
# Test::Pod => 1.52   (want 1.41)   
# Test::WWW::Mechanize  => 1.52   (want any version)
# base  => 2.27   (want any version)
# lib   => 0.65   (want any version)
# strict=> 1.11   (want any version)
# version   => 0.9924 (want 0.9901) 
# warnings  => 1.44   (want any version)
# 
# Thanks for using my code.  I hope it works for you.
# If not, please try and include this output in the bug report.
# That will help me reproduce the issue and solve your problem.
# 
t/000-report-versions-tiny.t ... 
ok 1 - we really didn't test anything, just reporting data
1..1
ok
t/000_load.t ... 
1..1
ok 1 - use CGI::Application::Server;
ok

#   Failed test '... got the index.html page okay'
#   at t/001_basic.t line 65.
# 500
# Can't connect to localhost:47857 (Connection refused)

#   Failed test '... got the right page title for index.html'
#   at t/001_basic.t line 66.
#  got: undef
# expected: "Test Static Index Page"

#   Failed test '... got the index.cgi page start-point okay'
#   at t/001_basic.t line 70.
# 500
# Can't connect to localhost:47857 (Connection refused)

#   Failed test '... got the right page title for index.cgi'
#   at t/001_basic.t line 71.
#  got: undef
# expected: "Hello"

#   Failed test '... got the index.cgi page okay'
#   at t/001_basic.t line 75.
# 500
# Can't connect to localhost:47857 (Connection refused)

#   Failed test '... got the right page title for index.cgi (hello)'
#   at t/001_basic.t line 76.
#  got: undef
# expected: "Hello"

#   Failed test '... got the index.cgi page okay'
#   at t/001_basic.t line 78.
# 500
# Can't connect to localhost:47857 (Connection refused)

#   Failed test '... got the right page title for index.cgi (goodbye)'
#   at t/001_basic.t line 79.
#  got: undef
# expected: "Goodbye"

#   Failed test '... got the index.cgi page okay'
#   at t/001_basic.t line 81.
# 500
# Can't connect to localhost:47857 (Connection refused)

#   Failed test '... got the right page title for index.cgi (redirect end)'
#   at t/001_basic.t line 82.
#  got: undef
# expected: "Redirect End"

#   Failed test '... got the index.cgi page okay'
#   at t/001_basic.t line 84.
# 500
# Can't connect to localhost:47857 (Connection refused)

#   Failed test '... got the right page title for index.cgi (redirect end)'
#   at t/001_basic.t line 85.
#  got: undef
# expected: "Redirect End"

#   Failed test '... got the index.cgi page okay (even with extra path info)'
#   at t/001_basic.t line 89.
# 500
# Can't connect to localhost:47857 (Connection refus

Bug#972974: clamav-freshclam start faild.

[Michael Borgelt]

Package: clamav-freshclam
Version: 0.103.0+dfsg-1
Severity: grave
Justification: renders package unusable

clamav-freshclam start faild with:
Okt 26 18:44:41 host freshclam[31527]: ERROR: initialize: libfreshclam init
failed.
Okt 26 18:44:41 host freshclam[31527]: ERROR: Initialization error!
Okt 26 18:44:41 bert freshclam[31527]: ERROR: Can't open
/var/log/clamav/freshclam.log in append mode (check permissions!).
Okt 26 18:44:41 host systemd[1]: clamav-freshclam.service: Main process exited,
code=exited, status=2/INVALIDARGUMENT
Okt 26 18:44:41 host systemd[1]: clamav-freshclam.service: Failed with result
'exit-code'.

clamav-freshcalm was installed for the first time on this host.



-- Package-specific info:
--- configuration ---
Checking configuration files in /etc/clamav

Config file: clamd.conf
---
AlertExceedsMax disabled
PreludeEnable disabled
PreludeAnalyzerName = "ClamAV"
LogFile = "/var/log/clamav/clamav.log"
LogFileUnlock disabled
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogClean disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
ExtendedDetectionInfo = "yes"
PidFile disabled
TemporaryDirectory disabled
DatabaseDirectory = "/var/lib/clamav"
OfficialDatabaseOnly disabled
LocalSocket = "/var/run/clamav/clamd.ctl"
LocalSocketGroup = "clamav"
LocalSocketMode = "666"
FixStaleSocket = "yes"
TCPSocket disabled
TCPAddr disabled
MaxConnectionQueueLength = "15"
StreamMaxLength = "26214400"
StreamMinPort = "1024"
StreamMaxPort = "2048"
MaxThreads = "12"
ReadTimeout = "180"
CommandReadTimeout = "30"
SendBufTimeout = "200"
MaxQueue = "100"
IdleTimeout = "30"
ExcludePath disabled
MaxDirectoryRecursion = "15"
FollowDirectorySymlinks disabled
FollowFileSymlinks disabled
CrossFilesystems = "yes"
SelfCheck = "3600"
ConcurrentDatabaseReload = "yes"
DisableCache disabled
VirusEvent disabled
ExitOnOOM disabled
AllowAllMatchScan = "yes"
Foreground disabled
Debug disabled
LeaveTemporaryFiles disabled
User = "clamav"
Bytecode = "yes"
BytecodeSecurity = "TrustSigned"
BytecodeTimeout = "6"
BytecodeUnsigned disabled
BytecodeMode = "Auto"
DetectPUA disabled
ExcludePUA disabled
IncludePUA disabled
ScanPE = "yes"
ScanELF = "yes"
ScanMail = "yes"
ScanPartialMessages disabled
PhishingSignatures = "yes"
PhishingScanURLs = "yes"
HeuristicAlerts = "yes"
HeuristicScanPrecedence disabled
StructuredDataDetection disabled
StructuredMinCreditCardCount = "3"
StructuredMinSSNCount = "3"
StructuredSSNFormatNormal = "yes"
StructuredSSNFormatStripped disabled
ScanHTML = "yes"
ScanOLE2 = "yes"
AlertBrokenExecutables disabled
AlertEncrypted disabled
StructuredCCOnly disabled
AlertEncryptedArchive disabled
AlertEncryptedDoc disabled
AlertOLE2Macros disabled
AlertPhishingSSLMismatch disabled
AlertPhishingCloak disabled
AlertPartitionIntersection disabled
ScanPDF = "yes"
ScanSWF = "yes"
ScanXMLDOCS = "yes"
ScanHWP3 = "yes"
ScanArchive = "yes"
ForceToDisk disabled
MaxScanTime = "12"
MaxScanSize = "104857600"
MaxFileSize = "26214400"
MaxRecursion = "16"
MaxFiles = "1"
MaxEmbeddedPE = "10485760"
MaxHTMLNormalize = "10485760"
MaxHTMLNoTags = "2097152"
MaxScriptNormalize = "5242880"
MaxZipTypeRcg = "1048576"
MaxPartitions = "50"
MaxIconsPE = "100"
MaxRecHWP3 = "16"
PCREMatchLimit = "1"
PCRERecMatchLimit = "5000"
PCREMaxFileSize = "26214400"
OnAccessMountPath disabled
OnAccessIncludePath disabled
OnAccessExcludePath disabled
OnAccessExcludeRootUID disabled
OnAccessExcludeUID disabled
OnAccessExcludeUname disabled
OnAccessMaxFileSize = "5242880"
OnAccessDisableDDD disabled
OnAccessPrevention disabled
OnAccessExtraScanning disabled
OnAccessCurlTimeout = "5000"
OnAccessMaxThreads = "5"
OnAccessRetryAttempts disabled
OnAccessDenyOnError disabled
DevACOnly disabled
DevACDepth disabled
DevPerformance disabled
DevLiblog disabled
DisableCertCheck disabled
AlgorithmicDetection = "yes"
BlockMax disabled
PhishingAlwaysBlockSSLMismatch disabled
PhishingAlwaysBlockCloak disabled
PartitionIntersection disabled
OLE2BlockMacros disabled
ArchiveBlockEncrypted disabled

Config file: freshclam.conf
---
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
PidFile disabled
DatabaseDirectory = "/var/lib/clamav"
Foreground disabled
Debug disabled
UpdateLogFile = "/var/log/clamav/freshclam.log"
DatabaseOwner = "clamav"
Checks = "24"
DNSDatabaseInfo = "current.cvd.clamav.net"
DatabaseMirror = "db.local.clamav.net", "database.clamav.net"
PrivateMirror disabled
MaxAttempts = "5"
ScriptedUpdates = "yes"
TestDatabases = "yes"
CompressLocalDatabase disabled
ExtraDatabase disabled
ExcludeDatabase disabled
DatabaseCustomURL disabled
HTTPProxyServer disabled
HTTPProxyPort disabled
HTTPProxyUsername disabled
HTTPProxyPassword disabled
HTTPUserAgent disabled
NotifyClamd = "/etc/clamav/clamd.conf"
OnUpdateExecute disabled
OnErrorExecute disabled
OnOutdatedExecute disabled
LocalIPAddress disabled
ConnectT

Bug#966907: marked as done (logrotate: FTBFS: logrotate.c:310:5: error: ‘security_context_t’ is deprecated [-Werror=deprecated-declarations])

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 18:48:50 +
with message-id 
and subject line Bug#966016: fixed in logrotate 3.17.0-1
has caused the Debian Bug report #966016,
regarding logrotate: FTBFS: logrotate.c:310:5: error: ‘security_context_t’ is 
deprecated [-Werror=deprecated-declarations]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
966016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: logrotate
Version: 3.16.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I.  -include config.h -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wall -Wextra -Wmissing-format-attribute -Wmissing-noreturn -Wpointer-arith 
> -Wshadow -Wstrict-prototypes -Wundef -Wunused -Wwrite-strings -Werror -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o logrotate.o logrotate.c
> logrotate.c: In function ‘setSecCtx’:
> logrotate.c:310:5: error: ‘security_context_t’ is deprecated 
> [-Werror=deprecated-declarations]
>   310 | security_context_t srcCtx;
>   | ^~
> logrotate.c:329:5: error: ‘security_context_t’ is deprecated 
> [-Werror=deprecated-declarations]
>   329 | if (getfscreatecon_raw((security_context_t *)pPrevCtx) < 0) {
>   | ^~
> logrotate.c: In function ‘restoreSecCtx’:
> logrotate.c:373:5: error: ‘security_context_t’ is deprecated 
> [-Werror=deprecated-declarations]
>   373 | const security_context_t prevCtx = (security_context_t) *pPrevCtx;
>   | ^
> logrotate.c:373:5: error: ‘security_context_t’ is deprecated 
> [-Werror=deprecated-declarations]
> cc1: all warnings being treated as errors
> make[3]: *** [Makefile:519: logrotate.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/logrotate_3.16.0-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: logrotate
Source-Version: 3.17.0-1
Done: =?utf-8?q?Christian_G=C3=B6ttsche?= 

We believe that the bug you reported is fixed in the latest version of
logrotate, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Göttsche  (supplier of updated logrotate 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 17 Sep 2020 19:37:27 +0200
Source: logrotate
Architecture: source
Version: 3.17.0-1
Distribution: unstable
Urgency: medium
Maintainer: Christian Göttsche 
Changed-By: Christian Göttsche 
Closes: 945097 966016
Changes:
 logrotate (3.17.0-1) unstable; urgency=medium
 .
   * New upstream version 3.17.0 (Closes: #945097, #966016)
 .
   * debian:
 - bump to debhelper compat level 13
 - wrap-and-sort
   * d/rules:
 - drop custom cleanup
   * d/patches:
 - rebase and drop applied ones
 - drop patch disabling test 70
 - move debian specific patch to subdir
 - cherry-pick upstream commits:
   + use getenv() on macOS and BSD
   + logrotate.service: harden with ProtectHostname
   + tests: always run logrotate in verbose mode
   + test-0070: set log modification time to current date
   + make `delaycompress` not to fail with `rotate 0`
   * d/logrotate.preinst: drop ancient maintainer script about old state file
 paths
   * d/control: add acl package to build-dependencies to run ACL unit tests
 on Linux
   * d/copyright: update years
Checksums-Sha1:
 8b5197b456a6bdbef79a3a7ba3e0eac8c10678c3 2230 logrotate_3.17.0-1.dsc
 588cc05a87c4b5ecf8bcc0599ffae271379f6455 161756 logrotate_3.17.0.orig.tar.xz
 69903

Bug#966016: marked as done (logrotate FTBFS with libselinux 3.1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Oct 2020 18:48:50 +
with message-id 
and subject line Bug#966016: fixed in logrotate 3.17.0-1
has caused the Debian Bug report #966016,
regarding logrotate FTBFS with libselinux 3.1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
966016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: logrotate
Version: 3.16.0-3
Severity: serious
Tags: ftbfs

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

...
logrotate.c: In function 'setSecCtx':
logrotate.c:310:5: error: 'security_context_t' is deprecated 
[-Werror=deprecated-declarations]
  310 | security_context_t srcCtx;
  | ^~
logrotate.c:329:5: error: 'security_context_t' is deprecated 
[-Werror=deprecated-declarations]
  329 | if (getfscreatecon_raw((security_context_t *)pPrevCtx) < 0) {
  | ^~
logrotate.c: In function 'restoreSecCtx':
logrotate.c:373:5: error: 'security_context_t' is deprecated 
[-Werror=deprecated-declarations]
  373 | const security_context_t prevCtx = (security_context_t) *pPrevCtx;
  | ^
logrotate.c:373:5: error: 'security_context_t' is deprecated 
[-Werror=deprecated-declarations]
cc1: all warnings being treated as errors
make[3]: *** [Makefile:519: logrotate.o] Error 1
--- End Message ---
--- Begin Message ---
Source: logrotate
Source-Version: 3.17.0-1
Done: =?utf-8?q?Christian_G=C3=B6ttsche?= 

We believe that the bug you reported is fixed in the latest version of
logrotate, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Göttsche  (supplier of updated logrotate 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 17 Sep 2020 19:37:27 +0200
Source: logrotate
Architecture: source
Version: 3.17.0-1
Distribution: unstable
Urgency: medium
Maintainer: Christian Göttsche 
Changed-By: Christian Göttsche 
Closes: 945097 966016
Changes:
 logrotate (3.17.0-1) unstable; urgency=medium
 .
   * New upstream version 3.17.0 (Closes: #945097, #966016)
 .
   * debian:
 - bump to debhelper compat level 13
 - wrap-and-sort
   * d/rules:
 - drop custom cleanup
   * d/patches:
 - rebase and drop applied ones
 - drop patch disabling test 70
 - move debian specific patch to subdir
 - cherry-pick upstream commits:
   + use getenv() on macOS and BSD
   + logrotate.service: harden with ProtectHostname
   + tests: always run logrotate in verbose mode
   + test-0070: set log modification time to current date
   + make `delaycompress` not to fail with `rotate 0`
   * d/logrotate.preinst: drop ancient maintainer script about old state file
 paths
   * d/control: add acl package to build-dependencies to run ACL unit tests
 on Linux
   * d/copyright: update years
Checksums-Sha1:
 8b5197b456a6bdbef79a3a7ba3e0eac8c10678c3 2230 logrotate_3.17.0-1.dsc
 588cc05a87c4b5ecf8bcc0599ffae271379f6455 161756 logrotate_3.17.0.orig.tar.xz
 699038a8710f8c2c2f468fc82e9e5de86c63e885 833 logrotate_3.17.0.orig.tar.xz.asc
 24fb83ed2dd0aeba40552c4400f32f835ab02fe5 21672 logrotate_3.17.0-1.debian.tar.xz
 51590d588599f33a68208a527d108011491475f3 7519 
logrotate_3.17.0-1_source.buildinfo
Checksums-Sha256:
 85adbec422b9439530f4ed119d1de1e9663eb53cac0949559104cf777846b718 2230 
logrotate_3.17.0-1.dsc
 58cc2178ff57faa3c0490181cce041345aeca6cff18dba1c5cd1398bf1c19294 161756 
logrotate_3.17.0.orig.tar.xz
 9221d6ce7b93d97b4b47c75c680397367648a37758e031598089ec25d2b506ad 833 
logrotate_3.17.0.orig.tar.xz.asc
 1a5aa11489568886daa94b9b82f92e7b15bb3ae3571f21a176917b4138ece77a 21672 
logrotate_3.17.0-1.debian.tar.xz
 06eec29e2cd6c509a1aa91a55dacf6d7ff733fe443486fee487430e0b575afa2 7519 
logrotate_3.17.0-1_source.buildinfo
Files:
 01807513fcea71559fbe83a8e82eae19 2230 admin important logrotate_3.17.0-1.dsc
 ac2a7151fc8a187201872358a20a2813 161756 admin important 
logrotate_3.17.0.orig.tar.xz
 c32cb1321c68bdcb69f3ad253f13d7e3 833 admin important 
logrotate_3.17.0.orig.tar.xz.asc
 67f5bb915c30

Processed: closing 967210

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 967210 4.1.0+dfsg-1
Bug #967210 [src:sundials] sundials: Unversioned Python removal in sid/bullseye
Marked as fixed in versions sundials/4.1.0+dfsg-1.
Bug #967210 [src:sundials] sundials: Unversioned Python removal in sid/bullseye
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
967210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#937488: pynast: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Fri, Oct 23, 2020 at 08:08:58AM +0200, Andreas Tille wrote:
> On Wed, Oct 21, 2020 at 11:09:57PM +0200, Moritz Mühlenhoff wrote:
> > 
> > Given that there's been no upstream reaction for almost a year, let's
> > remove?
> 
> Agreed, Andreas. 

Ack, I've just filed a removal bug.

Cheers,
Moritz

Bug#957769: rotter: diff for NMU version 0.9-3.1

[Sudip Mukherjee]

Control: tags 957769 + patch
Control: tags 957769 + pending
--

Dear maintainer,

I've prepared an NMU for rotter (versioned as 0.9-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru rotter-0.9/debian/changelog rotter-0.9/debian/changelog
--- rotter-0.9/debian/changelog 2011-07-30 10:34:07.0 +0100
+++ rotter-0.9/debian/changelog 2020-10-26 19:17:58.0 +
@@ -1,3 +1,10 @@
+rotter (0.9-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957769)
+
+ -- Sudip Mukherjee   Mon, 26 Oct 2020 19:17:58 
+
+
 rotter (0.9-3) unstable; urgency=low
 
   * Build against libmp3lame-dev.
diff -Nru rotter-0.9/debian/patches/fix_gcc-10.patch 
rotter-0.9/debian/patches/fix_gcc-10.patch
--- rotter-0.9/debian/patches/fix_gcc-10.patch  1970-01-01 01:00:00.0 
+0100
+++ rotter-0.9/debian/patches/fix_gcc-10.patch  2020-10-26 19:17:54.0 
+
@@ -0,0 +1,19 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957769
+Forwarded: no
+
+---
+
+--- rotter-0.9.orig/src/rotter.h
 rotter-0.9/src/rotter.h
+@@ -132,7 +132,7 @@ encoder_funcs_t* init_lame( const char*
+ encoder_funcs_t* init_sndfile( const char* format, int channels, int bitrate 
);
+ 
+ // In mpegaudiofile.c
+-FILE* mpegaudio_file;
++extern FILE* mpegaudio_file;
+ int close_mpegaudio_file();
+ int open_mpegaudio_file( const char* filepath );
+ 
diff -Nru rotter-0.9/debian/patches/series rotter-0.9/debian/patches/series
--- rotter-0.9/debian/patches/series2011-02-08 21:42:06.0 +
+++ rotter-0.9/debian/patches/series2020-10-26 19:10:04.0 +
@@ -1 +1,2 @@
 use_ogg.diff
+fix_gcc-10.patch

Processed: severity of 938198 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 938198 normal
Bug #938198 [src:python-stdlib-extensions] python-stdlib-extensions: Python2 
removal in sid/bullseye
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
938198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: rotter: diff for NMU version 0.9-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957769 + patch
Bug #957769 [src:rotter] rotter: ftbfs with GCC-10
Added tag(s) patch.
> tags 957769 + pending
Bug #957769 [src:rotter] rotter: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#972952: [Pkg-javascript-devel] Bug#972952: node-mkdirp 1.0 is incompatible with 0.5, breaks yarnpkg

[Xavier]

Le 26/10/2020 à 15:28, ano...@users.sourceforge.net a écrit :
> Package: node-mkdirp
> Version: 1.0.4-2
> Severity: critical
> 
> I don't know whether to report this against node-mkdirp for breaking
> compatibility, or yarnpkg for depending on "node-mkdirp (>= 0.5.1)"
> rather than "node-mkdirp (>= 0.5.1), node-mkdirp (<<1.0.0)". Either way,
> things are currently broken in unstable and shouldn't migrate to
> testing.
> 
> I upgraded various packages this morning, and found that yarn would no
> longer work.
> 
>   $ yarn
>   yarn install v1.22.4
>   warning Skipping preferred cache folder "/home/redacted/.cache/yarn" 
> because it is not writable.
>   warning Skipping preferred cache folder "/tmp/.yarn-cache-1000" because it 
> is not writable.
>   warning Skipping preferred cache folder "/tmp/.yarn-cache" because it is 
> not writable.
>   error Yarn hasn't been able to find a cache folder it can use. Please use 
> the explicit --cache-folder option to tell it what location to use, or make 
> one of the preferred locations writable.
>   info Visit https://yarnpkg.com/en/docs/cli/install for documentation about 
> this command.
> 
> This turns out to be due to this error being thrown:
> 
>   TypeError: invalid options argument
> at optsArg (/usr/share/nodejs/mkdirp/lib/opts-arg.js:13:11)
> at mkdirp (/usr/share/nodejs/mkdirp/index.js:11:10)
> at /usr/share/nodejs/yarn/lib/util/promise.js:37:10
> at new Promise ()
> at /usr/share/nodejs/yarn/lib/util/promise.js:17:12
> at Object. (/usr/share/nodejs/yarn/lib/util/fs.js:1024:15)
> at Generator.throw ()
> at step 
> (/usr/share/nodejs/babel-runtime/helpers/asyncToGenerator.js:17:30)
> at /usr/share/nodejs/babel-runtime/helpers/asyncToGenerator.js:30:13
> 
> It turns out yarn is expecting node-mkdirp to accept a callback, which
> was apparently dropped in node-mkdirp 1.0 in favor of it returning a
> promise.
> 
> Downgrading node-mkdirp to 0.5.1-2 fixed it:
> 
>   $ yarn
>   yarn install v1.22.4
>   info No lockfile found.
>   [1/4] Resolving packages...
>   [2/4] Fetching packages...
>   [3/4] Linking dependencies...
>   [4/4] Building fresh packages...
>   success Saved lockfile.
>   Done in 0.07s.

Hi JS Team,

yarnpkg is not in testing due to babel problems. Do you agree to
dicrease severity of this bug to allow mkdirp transition (or reassign
this bug to node-yarnpkg) ?

Cheers,
Xavier

Processed: src:uncrustify: fails to migrate to testing for too long: FTBFS on armhf

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.71.0+dfsg1-1
Bug #972981 [src:uncrustify] src:uncrustify: fails to migrate to testing for 
too long: FTBFS on armhf
Marked as fixed in versions uncrustify/0.71.0+dfsg1-1.
Bug #972981 [src:uncrustify] src:uncrustify: fails to migrate to testing for 
too long: FTBFS on armhf
Marked Bug as done

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

Bug#972981: src:uncrustify: fails to migrate to testing for too long: FTBFS on armhf

[Paul Gevers]

Source: uncrustify
Version: 0.69.0+dfsg1-1
Severity: serious
Control: close -1 0.71.0+dfsg1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:uncrustify in
its current version in unstable has been trying to migrate for 60 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=uncrustify




signature.asc
Description: OpenPGP digital signature

Bug#972983: python-ete3: autopkgtest regression: No module named 'numpy'

[Paul Gevers]

Source: python-ete3
Version: 3.1.2+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of python-ete3 the autopkgtest of python-ete3 fails
in testing when that autopkgtest is run with the binary packages of
python-ete3 from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
python-ete3from testing3.1.2+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=python-ete3

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-ete3/7751730/log.gz

autopkgtest [09:29:16]: test autodep8-python3: set -e ; for py in
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
with $py:" ; $py -c "import ete3; print(ete3)" ; done
autopkgtest [09:29:16]: test autodep8-python3: [---
Testing with python3.8:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/ete3/__init__.py", line 55, in

from .evol.evoltree import *
  File "/usr/lib/python3/dist-packages/ete3/evol/__init__.py", line 54,
in 
from .evoltreeimport *
  File "/usr/lib/python3/dist-packages/ete3/evol/evoltree.py", line 83,
in 
from .utils import translate
  File "/usr/lib/python3/dist-packages/ete3/evol/utils.py", line 45, in

from numpy import floor, pi as PI, sin
ModuleNotFoundError: No module named 'numpy'



signature.asc
Description: OpenPGP digital signature

Bug#972952: [Pkg-javascript-devel] Bug#972952: Bug#972952: node-mkdirp 1.0 is incompatible with 0.5, breaks yarnpkg

[Paolo Greppi]

Hi Xavier,

Il 26/10/20 20:24, Xavier ha scritto:

Le 26/10/2020 à 15:28, ano...@users.sourceforge.net a écrit :

   ...


Hi JS Team,

yarnpkg is not in testing due to babel problems. Do you agree to
dicrease severity of this bug to allow mkdirp transition (or reassign
this bug to node-yarnpkg) ?

Cheers,
Xavier



I think this should be reassigned to node-yarnpkg and then escalated to upstream
I volunteer to do the second part.

Paolo

Processed: affects 972665

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 972665 src:firefox src:firefox-esr
Bug #972665 [gcc-10] ICE building firefox-esr/firefox in unstable on armhf
Added indication that 972665 affects src:firefox and src:firefox-esr
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 972665

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 972665 + ftbfs
Bug #972665 [gcc-10] ICE building firefox-esr/firefox in unstable on armhf
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#972974: strace

[Michael Borgelt]

Additional strace output:

lchown("/var/log/clamav/freshclam.log", 133, 147) = -1 EPERM  
(Operation not permitted)
write(2, "ERROR: lchown to user 'clamav' f"..., 41ERROR: lchown to  
user 'clamav' failed on

) = 41
write(2, "log file '/var/log/clamav/freshc"..., 42log file  
'/var/log/clamav/freshclam.log'.

) = 42
write(2, "Error was 'Operation not permitt"..., 36Error was 'Operation  
not permitted'

) = 36
stat("/var/log/clamav/freshclam.log", {st_mode=S_IFREG|0666,  
st_size=922, ...}) = 0

write(3, "Mon Oct 26 19:13:10 2020 -> WARN"..., 150) = 150
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0x6), ...}) = 0
write(1, "Mon Oct 26 19:13:10 2020 -> ^lch"..., 142Mon Oct 26 19:13:10  
2020 -> ^lchown to user 'clamav' failed
on log file '/var/log/clamav/freshclam.log'.  Error was 'Operation not  
permitted'

) = 142
stat("/var/log/clamav/freshclam.log", {st_mode=S_IFREG|0666,  
st_size=1072, ...}) = 0

write(3, "Mon Oct 26 19:13:10 2020 -> ERRO"..., 68) = 68
write(1, "Mon Oct 26 19:13:10 2020 -> !Fai"..., 62Mon Oct 26 19:13:10  
2020 -> !Failed to switch to clamav user

.
) = 62
close(3)    = 0
chmod("/var/lib/clamav/tmp.816a2126be", 0700) = -1 ENOENT (No such  
file or directory)
openat(AT_FDCWD, "/var/lib/clamav/tmp.816a2126be",  
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No

such file or directory)
exit_group(9)   = ?
+++ exited with 9 +++
 MICHAEL BORGELTe-mail: mich...@borgelt.org

Processed: closing 931193, closing 931192

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 931193 8:6.9.11.24+dfsg-1
Bug #931193 {Done: =?utf-8?q?Moritz_M=C3=BChlenhoff?= } 
[src:imagemagick] imagemagick: CVE-2019-12975
Marked as fixed in versions imagemagick/8:6.9.11.24+dfsg-1.
Bug #931193 {Done: =?utf-8?q?Moritz_M=C3=BChlenhoff?= } 
[src:imagemagick] imagemagick: CVE-2019-12975
Bug 931193 is already marked as done; not doing anything.
> close 931192 8:6.9.11.24+dfsg-1
Bug #931192 {Done: =?utf-8?q?Moritz_M=C3=BChlenhoff?= } 
[src:imagemagick] imagemagick: CVE-2019-12976
Marked as fixed in versions imagemagick/8:6.9.11.24+dfsg-1.
Bug #931192 {Done: =?utf-8?q?Moritz_M=C3=BChlenhoff?= } 
[src:imagemagick] imagemagick: CVE-2019-12976
Bug 931192 is already marked as done; not doing anything.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
931192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931192
931193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#931192: closing 931193, closing 931192

[Salvatore Bonaccorso]

close 931193 8:6.9.11.24+dfsg-1
close 931192 8:6.9.11.24+dfsg-1
thanks