Bug#953728: gambc: FTBFS on s390x

[Nick Gasson]

On 05/23/20 13:13 PM, Adrian Bunk wrote:
> On Thu, Mar 12, 2020 at 04:36:17PM +, Ivo De Decker wrote:
>> package: src:gambc
>> version: 4.9.3-1
>> severity: serious
>> tags: ftbfs
>> 
>> Hi,
>> 
>> The latest upload of gambc to unstable fails on s390x:
>> 
>> https://buildd.debian.org/status/package.php?p=gambc
>
> Can an s390x porter please have a look?
>

I had a look at this because it's blocking another package, slib. I can
reproduce the hanging test case in qemu-user. It's testing timeouts with
UDP sockets but there seems to be a bug in the set_socket_blocking_mode
function where it passes an unsigned long argument to the FIONBIO ioctl
which actually takes an int parameter.

  unsigned long param = !blocking;

  return SOCKET_CALL_ERROR(IOCTL_SOCKET(s, FIONBIO, ));

The parameter value is only ever 0 or 1 so it's benign on little-endian
LP64 systems but on a big-endian system the parameter is always 0 when
read as an int so the socket is never put in non-blocking mode and reads
from it hang.

The patch below fixes the problem from me on S390 qemu-user. I'm
wondering if someone with access to real hardware can verify?

diff --git a/lib/os_io.c b/lib/os_io.c
index 046be4a6bd30..b8b5f96c191e 100644
--- a/lib/os_io.c
+++ b/lib/os_io.c
@@ -5458,7 +5458,7 @@ ___BOOL blocking;)
 
 #ifdef FIONBIO
 
-  unsigned long param = !blocking;
+  int param = !blocking;
 
   return SOCKET_CALL_ERROR(IOCTL_SOCKET(s, FIONBIO, ));


--
Thanks,
Nick

Processed: severity of 981403 is serious

[Debian Bug Tracking System]

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

> severity 981403 serious
Bug #981403 [src:pylev] pylev: Another source-only upload is needed
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#981534: cadabra2 FTBFS: file INSTALL cannot find core/packages/cdb/gauge_theory/__init__.py

[Adrian Bunk]

Source: cadabra2
Version: 2.3.5-2
Severity: serious

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

...
Install the project...
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "None"
-- Installing: 
/<>/debian/cadabra2/usr/share/jupyter/kernels/cadabra2/kernel.json
-- Installing: 
/<>/debian/cadabra2/usr/share/jupyter/kernels/cadabra2/logo-32x32.png
-- Installing: 
/<>/debian/cadabra2/usr/share/jupyter/kernels/cadabra2/logo-64x64.png
-- Installing: 
/<>/debian/cadabra2/usr/lib/python3.9/site-packages/cadabra2_jupyter/__init__.py
-- Installing: 
/<>/debian/cadabra2/usr/lib/python3.9/site-packages/cadabra2_jupyter/__main__.py
-- Installing: 
/<>/debian/cadabra2/usr/lib/python3.9/site-packages/cadabra2_jupyter/context.py
-- Installing: 
/<>/debian/cadabra2/usr/lib/python3.9/site-packages/cadabra2_jupyter/completer.py
-- Installing: 
/<>/debian/cadabra2/usr/lib/python3.9/site-packages/cadabra2_jupyter/kernel.py
-- Installing: 
/<>/debian/cadabra2/usr/lib/python3.9/site-packages/cadabra2_jupyter/server.py
-- Installing: 
/<>/debian/cadabra2/usr/lib/python3.9/site-packages/notebook/static/components/codemirror/mode/cadabra/cadabra.js
-- Installing: /<>/debian/cadabra2/usr/share/cadabra2/notebook.tex
-- Installing: /<>/debian/cadabra2/usr/share/cadabra2/notebook.html
-- Installing: /<>/debian/cadabra2/usr/bin/cadabra-server
-- Installing: /<>/debian/cadabra2/usr/bin/cadabra2html
-- Installing: /<>/debian/cadabra2/usr/bin/cadabra2latex
-- Installing: 
/<>/debian/cadabra2/usr/share/man/man1/cadabra-server.1
-- Up-to-date: /<>/debian/cadabra2/usr/lib/python3.9/site-packages
-- Installing: 
/<>/debian/cadabra2/usr/lib/python3.9/site-packages/cadabra2.cpython-39-x86_64-linux-gnu.so
-- Installing: /<>/debian/cadabra2/usr/bin/cadabra2-cli
-- Installing: 
/<>/debian/cadabra2/usr/lib/python3.9/site-packages/cadabra2_defaults.py
-- Installing: 
/<>/debian/cadabra2/usr/lib/python3.9/site-packages/cdb_appdirs.py
-- Installing: /<>/debian/cadabra2/usr/bin/cadabra2
-- Up-to-date: /<>/debian/cadabra2/usr/bin
-- Installing: /<>/debian/cadabra2/usr/bin/cadabra2python
-- Installing: /<>/debian/cadabra2/usr/bin/cadabra2ipynb
-- Installing: /<>/debian/cadabra2/usr/bin/cadabra2cadabra
-- Installing: /<>/debian/cadabra2/usr/share/man/man1/cadabra2.1
-- Installing: 
/<>/debian/cadabra2/usr/share/man/man1/cadabra2-cli.1
-- Installing: 
/<>/debian/cadabra2/usr/share/man/man1/cadabra2cadabra.1
-- Installing: 
/<>/debian/cadabra2/usr/share/man/man1/cadabra2ipynb.1
-- Installing: 
/<>/debian/cadabra2/usr/share/man/man1/cadabra2html.1
-- Installing: 
/<>/debian/cadabra2/usr/share/man/man1/cadabra2latex.1
-- Installing: 
/<>/debian/cadabra2/usr/share/man/man1/cadabra2python.1
CMake Error at core/packages/cmake_install.cmake:62 (file):
  file INSTALL cannot find
  
"/<>/obj-x86_64-linux-gnu/core/packages/cdb/gauge_theory/__init__.py":
  No such file or directory.
Call Stack (most recent call first):
  cmake_install.cmake:51 (include)


make[1]: *** [Makefile:141: install] Error 1

Bug#981533: poetry-core: autopkgtest failure

[Adrian Bunk]

Source: poetry-core
Version: 1.0.0-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/poetry-core/9884892/log.gz

...
=== FAILURES ===
__ test_build_wheel_extended ___

@pytest.mark.skipif(
sys.platform == "win32"
and sys.version_info <= (3, 6)
or platform.python_implementation().lower() == "pypy",
reason="Disable test on Windows for Python <=3.6 and for PyPy",
)
def test_build_wheel_extended():
with temporary_directory() as tmp_dir, cwd(os.path.join(fixtures, 
"extended")):
>   filename = api.build_wheel(tmp_dir)

tests/masonry/test_api.py:76: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/poetry/core/masonry/api.py:57: in build_wheel
return unicode(WheelBuilder.make_in(poetry, Path(wheel_directory)))
/usr/lib/python3/dist-packages/poetry/core/masonry/builders/wheel.py:59: in 
make_in
wb.build()
/usr/lib/python3/dist-packages/poetry/core/masonry/builders/wheel.py:89: in 
build
self._build(zip_file)
/usr/lib/python3/dist-packages/poetry/core/masonry/builders/wheel.py:121: in 
_build
self._run_build_command(setup)
/usr/lib/python3/dist-packages/poetry/core/masonry/builders/wheel.py:149: in 
_run_build_command
subprocess.check_call(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

popenargs = (['/usr/bin/python3.9', 
'/tmp/autopkgtest-lxc.crqjv1iy/downtmp/autopkgtest_tmp/tests/masonry/builders/fixtures/extende...build',
 '-b', 
'/tmp/autopkgtest-lxc.crqjv1iy/downtmp/autopkgtest_tmp/tests/masonry/builders/fixtures/extended/build'],)
kwargs = {}, retcode = 1
cmd = ['/usr/bin/python3.9', 
'/tmp/autopkgtest-lxc.crqjv1iy/downtmp/autopkgtest_tmp/tests/masonry/builders/fixtures/extended...
 'build', '-b', 
'/tmp/autopkgtest-lxc.crqjv1iy/downtmp/autopkgtest_tmp/tests/masonry/builders/fixtures/extended/build']

def check_call(*popenargs, **kwargs):
"""Run command with arguments.  Wait for command to complete.  If
the exit code was zero then return, otherwise raise
CalledProcessError.  The CalledProcessError object will have the
return code in the returncode attribute.

The arguments are the same as for the call function.  Example:

check_call(["ls", "-l"])
"""
retcode = call(*popenargs, **kwargs)
if retcode:
cmd = kwargs.get("args")
if cmd is None:
cmd = popenargs[0]
>   raise CalledProcessError(retcode, cmd)
E   subprocess.CalledProcessError: Command '['/usr/bin/python3.9', 
'/tmp/autopkgtest-lxc.crqjv1iy/downtmp/autopkgtest_tmp/tests/masonry/builders/fixtures/extended/setup.py',
 'build', '-b', 
'/tmp/autopkgtest-lxc.crqjv1iy/downtmp/autopkgtest_tmp/tests/masonry/builders/fixtures/extended/build']'
 returned non-zero exit status 1.

/usr/lib/python3.9/subprocess.py:373: CalledProcessError
- Captured stdout call -
...
autodep8-python3 PASS (superficial)
autopkgtest [09:36:57]:  summary
pytest   FAIL non-zero exit status 1
autodep8-python3 PASS (superficial)

Bug#955772: marked as done (dask.distributed: flaky autopkgtest: timeout reached in test_robust_to_bad_sizeof_estimates)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 04:48:53 +
with message-id 
and subject line Bug#955772: fixed in dask.distributed 2021.01.0+ds.1-1
has caused the Debian Bug report #955772,
regarding dask.distributed: flaky autopkgtest: timeout reached in 
test_robust_to_bad_sizeof_estimates
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.)


-- 
955772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dask.distributed
Version: 2.10.0+ds.1-3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

You package has an autopkgtest, great. However, until recently it always
failed. With the upload of 2.10.0+ds.1-3 it now *sometimes* passes.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests. Please either fix the test to be more robust, or or use the
"flaky" restriction for the offending test until a solution has been found.

I copied the output at the bottom of this report. All the failing tests
that I inspected look like it.

I'll have the migration software ignore the results of your autopkgtest
until this bug is fixed.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dask.distributed/4801510/log.gz

=== FAILURES
===
_ test_robust_to_bad_sizeof_estimates
__

def test_func():
result = None
workers = []
with clean(timeout=active_rpc_timeout, **clean_kwargs) as loop:

async def coro():
with dask.config.set(config):
s = False
for i in range(5):
try:
s, ws = await start_cluster(
nthreads,
scheduler,
loop,
security=security,
Worker=Worker,
scheduler_kwargs=scheduler_kwargs,
worker_kwargs=worker_kwargs,
)
except Exception as e:
logger.error(
"Failed to start gen_cluster, retrying",
exc_info=True,
)
else:
workers[:] = ws
args = [s] + workers
break
if s is False:
raise Exception("Could not start cluster")
if client:
c = await Client(
s.address,
loop=loop,
security=security,
asynchronous=True,
**client_kwargs
)
args = [c] + args
try:
future = func(*args)
if timeout:
future = asyncio.wait_for(future, timeout)
result = await future
if s.validate:
s.validate_state()
finally:
if client and c.status not in ("closing", "closed"):
await c._close(fast=s.status == "closed")
await end_cluster(s, workers)
await asyncio.wait_for(cleanup_global_workers(), 1)

try:
c = await default_client()
except ValueError:
pass
else:
await c._close(fast=True)

for i in range(5):
if all(c.closed() for c in Comm._instances):
break
else:
await asyncio.sleep(0.05)
else:
L = [c for c in Comm._instances if not c.closed()]
Comm._instances.clear()
# raise ValueError("Unclosed Comms", L)

Bug#978364: apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side of an entry is empty)

[Kartik Mistry]

On Sun, Jan 31, 2021 at 11:20 PM Tino Didriksen  wrote:
> I did CC Kartik in the original mail. I assume it was lost in the crowd. 
> https://salsa.debian.org/science-team/apertium-rus-ukr is up-to-date and 
> bundled and is the only thing that wanted apertium-ukr, so after 
> apertium-rus-ukr is uploaded, apertium-ukr will be superfluous and should be 
> removed.

Hi all,

It seems that we had no rus-ukr pair in Debian :/

Uploading it now and hoping it will make it in the archive in time.

-- 
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com

Bug#896395: python3-sphinxcontrib.rubydomain: sphinxcontrib.rubydomain fails to import

[Stefano Rivera]

Hi Helmut (2018.04.20_14:01:36_-0600)
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/usr/lib/python3/dist-packages/sphinxcontrib/rubydomain.py", line 23, 
> in 
> from sphinx.util.compat import Directive
> ImportError: cannot import name 'Directive'

Had a look at this

This import was deprecated in Sphinx 1.6:
https://github.com/sphinx-doc/sphinx/commit/2df0bb8d03d05fe7052315438382d49014e3dcf9

It could be pulled from docutils.parsers.rst, but really this module
looks dead upstream:
https://github.com/sphinx-contrib/rubydomain

Shall we just rm it?

SR

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

Bug#980608: marked as done (renderdoc: FTBFS: glslang_compile.cpp:145:1: error: cannot convert ‘’ to ‘int’ in initialization)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 02:28:48 +
with message-id 
and subject line Bug#980608: fixed in renderdoc 1.11+dfsg-5
has caused the Debian Bug report #980608,
regarding renderdoc: FTBFS: glslang_compile.cpp:145:1: error: cannot convert 
‘’ to ‘int’ in initialization
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.)


-- 
980608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: renderdoc
Version: 1.11+dfsg-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 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/renderdoc && /usr/bin/c++ 
> -DDISTRIBUTION_CONTACT=\"https://salsa.debian.org/xorg-team/app/renderdoc\; 
> -DDISTRIBUTION_NAME=\"Debian\" -DDISTRIBUTION_VERSION=\"1.11+dfsg-4\" 
> -DRENDERDOC_EXPORTS -DRENDERDOC_PLATFORM_LINUX -DRENDERDOC_STABLE_BUILD=1 
> -DRENDERDOC_SUPPORT_EGL -DRENDERDOC_SUPPORT_GL -DRENDERDOC_SUPPORT_GLES 
> -DRENDERDOC_SUPPORT_VULKAN -DRENDERDOC_WINDOWING_XCB 
> -DRENDERDOC_WINDOWING_XLIB -D_RELEASE -I/<>/renderdoc 
> -I/<>/renderdoc/3rdparty -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
> -fno-strict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -Wall 
> -Wextra -Wno-unused-variable -Wno-unused-parameter -Wno-unused-result 
> -Wno-type-limits -Wno-missing-field-initializers -Wno-unknown-pragmas 
> -Wno-reorder -Wno-unused-but-set-variable -Wno-maybe-uninitialized 
> -Wno-class-memaccess -Wimplicit-fallthrough=2 -O3 -DNDEBUG -fPIC -o 
> CMakeFiles/rdoc.dir/common/dds_readwrite.cpp.o -c 
> /<>/renderdoc/common/dds_readwrite.cpp
> /<>/renderdoc/driver/shaders/spirv/glslang_compile.cpp:145:1: 
> error: cannot convert ‘’ to ‘int’ in 
> initialization
>   145 | };
>   | ^
> make[3]: *** 
> [renderdoc/driver/shaders/spirv/CMakeFiles/rdoc_spirv.dir/build.make:85: 
> renderdoc/driver/shaders/spirv/CMakeFiles/rdoc_spirv.dir/glslang_compile.cpp.o]
>  Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/renderdoc_1.11+dfsg-4_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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: renderdoc
Source-Version: 1.11+dfsg-5
Done: Jordan Justen 

We believe that the bug you reported is fixed in the latest version of
renderdoc, 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 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jordan Justen  (supplier of updated renderdoc 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: Sun, 31 Jan 2021 17:06:50 -0800
Source: renderdoc
Architecture: source
Version: 1.11+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Jordan Justen 
Closes: 980608
Changes:
 renderdoc (1.11+dfsg-5) unstable; urgency=medium
 .
   * d/patches: Patch for glslang 11.1.0. (Closes: #980608)
   * d/control: Bump glslang dep version to 11.1.0
Checksums-Sha1:
 da07fec55a20f528a8f7e7b016014c1e4f85c92c 3107 renderdoc_1.11+dfsg-5.dsc
 faa9860ceb3381c5b127a33aff0957fca6aef04a 16568 
renderdoc_1.11+dfsg-5.debian.tar.xz
 b6bd212da48c7a22fcd5ed4ba4eb3000f635a368 12701 
renderdoc_1.11+dfsg-5_source.buildinfo
Checksums-Sha256:
 cee7a8eca6ac7bc0db42a4d3e593c590dcf288ca044901ca0a24dbc25a72c97e 3107 
renderdoc_1.11+dfsg-5.dsc
 

Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring

[Simon McVittie]

Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/issues/2305

On Sun, 31 Jan 2021 at 18:53:09 -0500, Charles Malaheenee wrote:
> In journalctl there are a lot messages from systemd or dbus-daemon, like 
> "dbus-daemon[970]: [session uid=1000 pid=968] Successfully activated service 
> 'org.mate.panel.applet.ClockAppletFactory'" or "systemd[902]: Started Sound 
> Service."

That's fine, as long as they aren't reporting failures.

> (version 2.66.4-3, bug appears)
> Jan 30 14:26:13 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus 
> session bus: Cannot spawn a message bus when setuid
> (version 2.66.4-3+revert981420targeted, no bug)
> Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: GLib-GIO: Not suppressing 
> use of DBUS_SESSION_BUS_ADDRESS because not setuid, even though AT_SECURE

Right. So my theory was at least partially correct: gnome-keyring-daemon
is refusing to connect to the D-Bus session bus, because while not
actually setuid, it has elevated privileges that its caller does not
have (CAP_IPC_LOCK), and therefore does not (and should not!) trust the
DBUS_SESSION_BUS_ADDRESS that it inherits from its caller.

Do you have the dbus-user-session package installed? If you don't, does
installing that package with one of the affected versions of GLib (such
as 2.66.4-3) make this regression disappear?

If you rely on the ability to have a separate D-Bus session bus per
X11 display for the same uid, then you can't use dbus-user-session
permanently, because it represents a different model where each uid has
only one instance of the D-Bus session bus. If you have no particular
opinion on whether the session bus should be per uid or per X11 display,
then dbus-user-session is what I would recommend.

smcv

Processed: Re: Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/issues/2305
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login 
keyring
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/issues/2305'.

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

Bug#979058: marked as done (src:geronimo-j2ee-connector-1.5-spec: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Mon, 01 Feb 2021 00:18:38 +
with message-id 
and subject line Bug#979058: fixed in geronimo-j2ee-connector-1.5-spec 2.0.0-2
has caused the Debian Bug report #979058,
regarding src:geronimo-j2ee-connector-1.5-spec: invalid maintainer address
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.)


-- 
979058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geronimo-j2ee-connector-1.5-spec
Version: 2.0.0-1
Severity: serious
X-Debbugs-Cc: Graziano Obertelli , Kyo Lee 
, Holger Levsen 

The maintainer address is invalid, see below.

Ansgar

 Start of forwarded message 
From: Mail Delivery System 
Subject: Mail delivery failed: returning message to sender
Date: Fri, 01 Jan 2021 18:49:46 +

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  g...@eucalyptus.com
retry timeout exceeded
--- End Message ---
--- Begin Message ---
Source: geronimo-j2ee-connector-1.5-spec
Source-Version: 2.0.0-2
Done: Emmanuel Bourg 

We believe that the bug you reported is fixed in the latest version of
geronimo-j2ee-connector-1.5-spec, 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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated 
geronimo-j2ee-connector-1.5-spec 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, 01 Feb 2021 00:41:36 +0100
Source: geronimo-j2ee-connector-1.5-spec
Architecture: source
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 965549 979058
Changes:
 geronimo-j2ee-connector-1.5-spec (2.0.0-2) unstable; urgency=medium
 .
   * Package adopted by the Java Team (Closes: #979058)
   * Build with the DH sequencer instead of CDBS
   * Build with Maven instead of Ant
   * Use salsa.debian.org Vcs-* URLs
   * Standards-Version updated to 4.5.1
   * Switch to debhelper level 13 (Closes: #965549)
   * Removed debian/orig-tar.sh
   * Switch to source format 3.0 (quilt)
Checksums-Sha1:
 fa3c07ae6a1487ce89f8efb18d1e016f00ccdfa8 2245 
geronimo-j2ee-connector-1.5-spec_2.0.0-2.dsc
 8c3932a110d980f670543613fc416d76edc47755 3128 
geronimo-j2ee-connector-1.5-spec_2.0.0-2.debian.tar.xz
 743a9e362406a55c92541fefd56f47366ce613dc 14606 
geronimo-j2ee-connector-1.5-spec_2.0.0-2_source.buildinfo
Checksums-Sha256:
 58beef6f5caf3aea83ede5562a963810c5bff65e340689d8b1395cefaf0c87a9 2245 
geronimo-j2ee-connector-1.5-spec_2.0.0-2.dsc
 fdc0b45111f40ce66701db654777060f3d57903fc87129a0ea33892c199b7d06 3128 
geronimo-j2ee-connector-1.5-spec_2.0.0-2.debian.tar.xz
 5fcb749fd6bcc3637501d1498542d82172d80623f1c7a1d136aa7b40907b03bc 14606 
geronimo-j2ee-connector-1.5-spec_2.0.0-2_source.buildinfo
Files:
 db14c6169f732ef906be3cb2027272f5 2245 java optional 
geronimo-j2ee-connector-1.5-spec_2.0.0-2.dsc
 5a6806e82296f8f8fef38205b710024b 3128 java optional 
geronimo-j2ee-connector-1.5-spec_2.0.0-2.debian.tar.xz
 8bf4628811d1b7e0ba94d3254a96fccc 14606 java optional 
geronimo-j2ee-connector-1.5-spec_2.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmAXQoQSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCs9KoP/1paJj2CHFXAc42MRalMlyPM24C2rPQP
MrWNmP/s17S6a+nvkX5ylgpIZ4Rj3GQ1/iOzAEnaxuZEuq3/2VLo65m5YnWTXHDl
SfYslZZVXD6QZkqf/Q3+/xy+7AYHl3WO9IONyJBaecIqWU/JTIO0NeQg0Am12MeX
AbJ3v5gwcX34QJg9EJT6b4Yo/TSSUXpakLlnoUd6H47wfie/qIz6G4qQY+QA35pz
aZ5gNy1oLpxvArPbMxHl2iO4oPJtI9iHMVGbMMDh8Cb78guc9jVAO50J+U0kc9yz
1UIRujsjqXO6tgNHO8Dx6eFtZc3uJ8qOfZUje4QF+qDkAFIZlqZAATHtbmbLkPGN
M7NA4RzsyEP8REiiC6nKPjWEQdFJFgDD8gKn2DGvlWgogJwHtRGR/nDi4y6+Q5NX
NaB6D7G+vFjbgqBhZeydUpAfiNDOOYanKcJNwGfR3iKFdAc5jsKGf/TzSKUHK5LE
y33rvMpLTzZcN508jwa47XyOeNWAC+bfq9WieB5UNIABb4WUvHUBZyi8sNubVyU/
ZUoLUXV9DYsJRn8ErUeraeztuSizzy7LDmtsYkgbS2jNVBpDQ+u52erCFtccaVeK
bhF8kH8ZtafxQJqGlptmqWoJEg/FPnQ+nO1yYgJS3NPEPTt2wqvtXrjraBaBfPa1
sdxeTje+wyQe
=kPyS

Processed: severity of 534756 is grave

[Debian Bug Tracking System]

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

> severity 534756 grave
Bug #534756 [fusesmb] fusesmb.cache fails on 64-bit
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring

[Charles Malaheenee]

Hello Simon,

Thank you for the attention to this bug!

Our DE is Mate. Probably, the problem is related to the mix of components ?


Here is the output (I do not remember to have to change the permissions of 
gnome-keyring-daemon):
ls -l /usr/bin/gnome-keyring-daemon
-rwxr-xr-x 1 root root 1143712 Mar 11  2020 /usr/bin/gnome-keyring-daemon

getcap /usr/bin/gnome-keyring-daemon
/usr/bin/gnome-keyring-daemon cap_ipc_lock=ep


In journalctl there are a lot messages from systemd or dbus-daemon, like 
"dbus-daemon[970]: [session uid=1000 pid=968] Successfully activated service 
'org.mate.panel.applet.ClockAppletFactory'" or "systemd[902]: Started Sound 
Service."

Concerning gnome-keyring-daemon, here is the output of journalctl for all 
possible package versions:

(version 2.66.4-3, bug appears)
Jan 30 14:26:13 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus 
session bus: Cannot spawn a message bus when setuid
Jan 30 14:26:13 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus 
session bus: Cannot spawn a message bus when setuid
Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus 
session bus: Cannot spawn a message bus when setuid
Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: The SSH agent was already 
initialized
Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: The PKCS#11 component was 
already initialized
Jan 30 14:26:39 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus 
session bus: Cannot spawn a message bus when setuid

(version 2.66.4-1, no bug)
Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The Secret Service was 
already initialized
Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The SSH agent was already 
initialized
Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The PKCS#11 component was 
already initialized

(version 2.66.4-3+revert981420targeted, no bug)
Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: GLib-GIO: Not suppressing use 
of DBUS_SESSION_BUS_ADDRESS because not setuid, even though AT_SECURE
Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The Secret Service was 
already initialized
Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The SSH agent was already 
initialized
Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The PKCS#11 component was 
already initialized

(version 2.66.4-3+revert981420dbus, no bug)
Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The Secret Service was 
already initialized
Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The SSH agent was already 
initialized
Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The PKCS#11 component was 
already initialized

(version 2.66.4-3+revert981420dbus, no bug)
Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The Secret Service was 
already initialized
Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The SSH agent was already 
initialized
Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The PKCS#11 component was 
already initialized

Hope this helps.

--
Best Regards,
Charles Malaheenee

Processed: Bug#979058 marked as pending in geronimo-j2ee-connector-1.5-spec

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #979058 [src:geronimo-j2ee-connector-1.5-spec] 
src:geronimo-j2ee-connector-1.5-spec: invalid maintainer address
Added tag(s) pending.

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

Bug#979058: marked as pending in geronimo-j2ee-connector-1.5-spec

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #979058 in geronimo-j2ee-connector-1.5-spec 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/java-team/geronimo-j2ee-connector-1.5-spec/-/commit/73faee1b2803b7a9be97d8e430b15ec795cbc576


Package adopted by the Java Team (Closes: #979058)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/979058

Bug#981520: minigalaxy: Shows a browser login window without any proof of origin (no URL, no HTTPS indicator, no chance to review SSL certificate, etc.)

[Axel Beckert]

Package: minigalaxy
Version: 1.0.1-1
Severity: grave
Tags: security
Justification: introduces a security hole allowing access to the accounts of 
users who use the package

Hi,

thanks for packaging minigalaxy. Unfortunately it's unusable as you
can't conscientiously login to GOG:

On startup it shows a login window which looks suspiciously like a GOG
login window in a web browser, but without without any possibility to
check its origin: It has no location bar, i.e. shows no URL, it doesn't
indicate if the entered credentials are transmitted encrypted via HTTPS
or not, and it offers no chance to review the HTTPS TLS certificate if
present.

Proof that it actually is a browser window:

It has "Back, Forward, Reload, etc. in the right click context menu and
I see two "WebKit" processes being forked from minigalaxy:

abe  24326  2.6  0.1 86076304 113572 pts/16 Sl+ 00:12   0:10  \_ 
/usr/bin/python3 /usr/games/minigalaxy
abe  24799  7.1  0.2 86563632 160396 pts/16 SLl+ 00:12   0:27  
\_ /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 7 16
abe  24802  0.0  0.0 86442844 59232 pts/16 SLl+ 00:12   0:00  
\_ /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitNetworkProcess 8 16

Possible solution: Don't use an embedded browser windows but call
sensible-browser or so to use the browser which the user is probably
already logged in to GOG anyways.

Or just show the location bar of the browser window which lets the user
have a look at the URL and certificates being used.

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

Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages minigalaxy depends on:
ii  gir1.2-gtk-3.0  3.24.24-1
ii  gir1.2-webkit2-4.0  2.30.4-1
ii  python3 3.9.1-1
ii  python3-gi  3.38.0-1+b2
ii  python3-gi-cairo3.38.0-1+b2
ii  python3-requests2.25.1+dfsg-2
ii  unzip   6.0-26
ii  xdg-utils   1.1.3-4

minigalaxy recommends no packages.

Versions of packages minigalaxy suggests:
ii  dosbox0.74-3-2
ii  scummvm   2.2.0+dfsg1-4
pn  wine32 | wine32-development | wine-stable-i386 | wine-devel-  

-- no debconf information

Bug#980603: [3dprinter-general] Bug#980603: cura: FTBFS: cura/PrinterOutput/Models/MaterialOutputModel.py:6: error: Module 'PyQt5.QtCore' has no attribute 'pyqtProperty'

[Gregor Riepl]

> Re: Lucas Nussbaum
> > > 14/14 Test  #1: code-style ...***Failed   61.38 sec
> > > cura/PrinterOutput/Models/MaterialOutputModel.py:6: error: Module 
> > > 'PyQt5.QtCore' has no attribute 'pyqtProperty'
> 
> Fwiw cura still works fine here, so I'd claim this is a test-only
> problem which we should probably mute unless there's an easy fix.

Could this be related to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973230
?

> > The following tests FAILED:
> >   1 - code-style (Failed)

If this is true and the failures are really only code style issues, I
would suggest to silence the unit test and be done with it.

But it does look a bit more serious from the error messages.

I reported it upstream. While we wait, I think it'll be ok to disable
the unit test and upload a new version.

Here's a patch, feel free to release if you agree:
https://salsa.debian.org/3dprinting-team/cura/-/commit/03fde269efaced553a7c4e74846e2554dd2f6bcf

(or revert it, if you think we should rather wait for upstream)

Bug#510368: libgamin0: libfam shlib dependency wrongly set to libfam0

[Chris Hofstaedtler]

* Helmut Grohne :
> On Fri, Aug 07, 2020 at 12:28:17PM +0200, Stefan Bühler wrote:
> > I think fixing libgamin0.shlibs and dropping fam from the archives is 
> > the smoothest path to fixing this mess.
> 
> Well, yeah. Removing fam removes the whole mess of compatibility.

#966273 has become RM: fam, so please fix the gamin side of this.

Many thanks,
Chris

Bug#979056: marked as done (src:geronimo-jms-1.1-spec: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 23:06:12 +
with message-id 
and subject line Bug#979056: fixed in geronimo-jms-1.1-spec 1.1.1-1
has caused the Debian Bug report #979056,
regarding src:geronimo-jms-1.1-spec: invalid maintainer address
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.)


-- 
979056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geronimo-jms-1.1-spec
Version: 1.1-1
Severity: serious
X-Debbugs-Cc: Graziano Obertelli , Kyo Lee 
, Holger Levsen 

The maintainer address is invalid, see below.

Ansgar

 Start of forwarded message 
From: Mail Delivery System 
Subject: Mail delivery failed: returning message to sender
Date: Fri, 01 Jan 2021 18:50:00 +

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  g...@eucalyptus.com
retry timeout exceeded
--- End Message ---
--- Begin Message ---
Source: geronimo-jms-1.1-spec
Source-Version: 1.1.1-1
Done: Emmanuel Bourg 

We believe that the bug you reported is fixed in the latest version of
geronimo-jms-1.1-spec, 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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated geronimo-jms-1.1-spec 
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: Sun, 31 Jan 2021 23:48:44 +0100
Source: geronimo-jms-1.1-spec
Architecture: source
Version: 1.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 965550 979056
Changes:
 geronimo-jms-1.1-spec (1.1.1-1) unstable; urgency=medium
 .
   * New upstream release
   * Package adopted by the Java Team (Closes: #979056)
   * Removed the JRE dependency
   * Changed the section from libs to java
   * Build with the DH sequencer instead of CDBS
   * Build with Maven instead of Ant
   * Removed the DM-Upload-Allowed field
   * Standards-Version updated to 4.5.1
   * Switch to debhelper level 13 (Closes: #965550)
   * Removed debian/orig-tar.sh
   * Switch to source format 3.0 (quilt)
Checksums-Sha1:
 708ba6371be42f9f03401a24f36632099721055e 2118 geronimo-jms-1.1-spec_1.1.1-1.dsc
 5d79dfac207512c726822bed3214148464f20d69 11272 
geronimo-jms-1.1-spec_1.1.1.orig.tar.xz
 a1066b61feeb745d7533dde2278d46a86e8201f2 2892 
geronimo-jms-1.1-spec_1.1.1-1.debian.tar.xz
 2840e55358399130064740d24c58edb3037d2a71 14542 
geronimo-jms-1.1-spec_1.1.1-1_source.buildinfo
Checksums-Sha256:
 f3fc945baed5fbb47d3fb27afa277383bd6eb99891d96e9f87d25d7dcb6ee0ea 2118 
geronimo-jms-1.1-spec_1.1.1-1.dsc
 3d6f5fd1b1cee4037451f48e5f0b3367c76fb03c153abd5233e4f5a324bee135 11272 
geronimo-jms-1.1-spec_1.1.1.orig.tar.xz
 54460e40d5a81e650267eb5057053bcb5d33842228e13058fda4d32d78d8a469 2892 
geronimo-jms-1.1-spec_1.1.1-1.debian.tar.xz
 d5d11228ccc5e5f162a37b28fb7905bd7395e3b072fa6eee203eabb83aa64030 14542 
geronimo-jms-1.1-spec_1.1.1-1_source.buildinfo
Files:
 200e5c85da6d07b44b918fc8e2a78f14 2118 java optional 
geronimo-jms-1.1-spec_1.1.1-1.dsc
 b5939d89e5e21241c00af9633d005db9 11272 java optional 
geronimo-jms-1.1-spec_1.1.1.orig.tar.xz
 398e9aab8306478ec90b3759233caf3a 2892 java optional 
geronimo-jms-1.1-spec_1.1.1-1.debian.tar.xz
 2862d60ab62eff06f5e57de2dcbfe9b1 14542 java optional 
geronimo-jms-1.1-spec_1.1.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmAXNIsSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsaD4P/iK5jgjBNmDUC8KVhxgle82aZ743X8UI
gmMqOQsFXzyvLGdtytaRfIuK6UiVuC+FAcmjI+BTWyKB+wQgswITAw2UGY+8Uqfa
1kkvQ1RyJ32iL/pYW+ZCQA8+mOvdfy9qaewKOBzw6bXfuqHLNFQoJg17OzMd2y0y
t0vU5Pe+eDN2uMAgJSFFX8UzZCjTlDieX+jHVXH1BdcSrFSZf5igaMQRGG5ILI8V
r5uhKZLZnLbPuXCnbtzLrmaQdSFAH+L93AkLoUSDJeIy0q+txK6PqxrnGgZZqMT8
a9K90o7+eTb88pe0RKRci2yZJjtVTuXa/1ns/hl2/IwsmZl0NhDTsQQLiK/Ms0bc
7Ee8/QE0A31NzFoi6nJEJGF7q4q4ulvvxaeV1K4f+bvVveYy62zbcsjEUtQsejnm
h48XXCnCiPurJB1hcIJINa74C/6xfhfFDSjfcHM8/VS3Msyqw5FU2AfJFOjKcdYI

Bug#981435: libvirt: stops on upgrade: internal error: Failed to load module 'libvirt_driver_qemu.so': libvirt.so.0: version `LIBVIRT_PRIVATE_6.9.0' not found (required by libvirt_driver_qemu.so)

[Paul Wise]

On Sun, 2021-01-31 at 18:49 +0100, Andrea Bolognani wrote:

> I've added a few extra Depends to make sure everything is really
> updated in lockstep and tested with unattended-upgrades: the result
> was much better this time!
...
> I believe we can merge the MR and consider the issue resolved.

Looks much better indeed, thanks for your work!

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 980603 https://github.com/Ultimaker/Cura/issues/9216
Bug #980603 [src:cura] cura: FTBFS: 
cura/PrinterOutput/Models/MaterialOutputModel.py:6: error: Module 
'PyQt5.QtCore' has no attribute 'pyqtProperty'
Set Bug forwarded-to-address to 'https://github.com/Ultimaker/Cura/issues/9216'.
> thanks
Stopping processing here.

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

Processed: Bug#979056 marked as pending in geronimo-jms-1.1-spec

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #979056 [src:geronimo-jms-1.1-spec] src:geronimo-jms-1.1-spec: invalid 
maintainer address
Added tag(s) pending.

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

Bug#979056: marked as pending in geronimo-jms-1.1-spec

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #979056 in geronimo-jms-1.1-spec 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/java-team/geronimo-jms-1.1-spec/-/commit/65f3683626e44242422a10c4d4cde45a241a0a03


Package adopted by the Java Team (Closes: #979056)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/979056

Bug#980637: git-buildpackage: FTBFS: AttributeError: 'str' object has no attribute 'decode'

[Jochen Sprickerhof]

* Guido Günther  [2021-01-31 13:19]:

Awesome. I had fixed the rpm parts here already
https://github.com/agx/git-buildpackage/tree/rpm but went for your
patches so your work is not lost. The reason i wrote 'tip of the
iceberg' is that the component tests need fixing as well - that's the bit
still missing - so tests still fail when the testdata for the component
tests is there (`git submodule update --init --recursive`).


Ha, I missed those. Attached one patch for GBP 
(gbp-rpm-Fix-tags-in-rpm-spec-files.patch)

and three for the rpm-testdata repo to make all tests work.

Cheers Jochen
From 3da6cd3af18d51cce569f2ee829356c8bbdb9392 Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof 
Date: Sun, 31 Jan 2021 22:40:00 +0100
Subject: [PATCH] rpm: Fix tags in rpm spec files

---
 tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec   |  6 +++---
 tests/data/rpm/specs/gbp-test2-reference.spec  | 11 +--
 tests/data/rpm/specs/gbp-test2-reference2.spec | 15 +++
 tests/data/rpm/specs/gbp-test3.spec|  2 +-
 4 files changed, 16 insertions(+), 18 deletions(-)

diff --git a/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec b/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec
index 8a92725..d5b8763 100644
--- a/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec
+++ b/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec
@@ -6,10 +6,10 @@ Release:0
 Group:  Development/Libraries
 License:GPLv2
 Source10:   ftp://ftp.host.com/%{name}-%{version}.tar.gz
-Source: foo.txt
+Source0:foo.txt
 Source20:   bar.tar.gz
-# Gbp-Ignore-Patches: -1
-Patch:  my.patch
+# Gbp-Ignore-Patches: 0
+Patch0: my.patch
 Patch10:my2.patch
 Patch20:my3.patch
 Packager:   Markus Lehtonen 
diff --git a/tests/data/rpm/specs/gbp-test2-reference.spec b/tests/data/rpm/specs/gbp-test2-reference.spec
index 1882131..5e1f176 100644
--- a/tests/data/rpm/specs/gbp-test2-reference.spec
+++ b/tests/data/rpm/specs/gbp-test2-reference.spec
@@ -6,12 +6,12 @@ Release:0
 Group:  Development/Libraries
 License:GPLv2
 Source10:   ftp://ftp.host.com/%{name}-%{version}.tar.gz
-Source: foo.txt
+Source0:foo.txt
 Source20:   bar.tar.gz
-# Gbp-Ignore-Patches: -1
-Patch:  my.patch
+# Gbp-Ignore-Patches: 0
+Patch0: my.patch
 # Patches auto-generated by git-buildpackage:
-Patch0: new.patch
+Patch1: new.patch
 Packager:   Markus Lehtonen 
 
 %description
@@ -27,14 +27,13 @@ Empty subpackage for the %{name} test package.
 %prep
 %setup -T -n %{name}-%{version} -c -a 10
 
-%patch
 
 echo "Do things"
 
 # Gbp-Patch-Macros
 # new.patch
 %if 1
-%patch0 -p1
+%patch1 -p1
 %endif
 
 %build
diff --git a/tests/data/rpm/specs/gbp-test2-reference2.spec b/tests/data/rpm/specs/gbp-test2-reference2.spec
index d41f450..32bbe97 100644
--- a/tests/data/rpm/specs/gbp-test2-reference2.spec
+++ b/tests/data/rpm/specs/gbp-test2-reference2.spec
@@ -6,13 +6,13 @@ Release:0
 Group:  Development/Libraries
 License:GPLv2
 Source10:   ftp://ftp.host.com/%{name}-%{version}.tar.gz
-Source: foo.txt
+Source0:foo.txt
 Source20:   bar.tar.gz
-# Gbp-Ignore-Patches: -1
-Patch:  my.patch
+# Gbp-Ignore-Patches: 0
+Patch0: my.patch
 # Patches auto-generated by git-buildpackage:
-Patch0: 1.patch
-Patch1: 2.patch
+Patch1: 1.patch
+Patch2: 2.patch
 Packager:   Markus Lehtonen 
 VCS:myvcstag
 
@@ -29,18 +29,17 @@ Empty subpackage for the %{name} test package.
 %prep
 %setup -T -n %{name}-%{version} -c -a 10
 
-%patch
 
 echo "Do things"
 
 # Gbp-Patch-Macros
 # 1.patch
 %if true
-%patch0 -p1
+%patch1 -p1
 %endif
 # 2.patch
 %ifarch %ix86
-%patch1 -p1
+%patch2 -p1
 %endif
 
 %build
diff --git a/tests/data/rpm/specs/gbp-test3.spec b/tests/data/rpm/specs/gbp-test3.spec
index c0c20c8..043afec 100644
--- a/tests/data/rpm/specs/gbp-test3.spec
+++ b/tests/data/rpm/specs/gbp-test3.spec
@@ -6,7 +6,7 @@ Group:  Development/Libraries
 License:GPLv2
 Source: %{name}-%{version}.tar.gz
 # Gbp-Ignore-Patches: 10
-Patch:  my.patch
+Patch0: my.patch
 Patch10:my2.patch
 Patch20:my3.patch
 
-- 
2.30.0

From 6753fd1cb848efe21c67589ca0cc00d636dfd1e4 Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof 
Date: Sun, 31 Jan 2021 16:22:55 +0100
Subject: [PATCH 1/3] Adopt to Python 3

---
 manage.py | 18 +-
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/manage.py b/manage.py
index 3eb8c39..57a56c7 100755
--- a/manage.py
+++ b/manage.py
@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/python3
 # vim:fileencoding=utf-8:et:ts=4:sw=4:sts=4
 #
 # Copyright (C) 2015 Intel Corporation 
@@ -20,7 +20,7 @@
 """Script for managing test package repositories and unittest data"""
 
 import argparse
-import ConfigParser
+import configparser
 import json
 import logging
 import os
@@ -55,9 +55,9 @@ def run_cmd(cmd, opts=None, capture_stdout=False, capture_stderr=False,
 LOG.debug("Running command: '%s'", ' '.join(args))
 popen = subprocess.Popen(args, stdin=stdin, stdout=stdout, 

Processed: Re: Bug#980923: acngtools eats all the CPU and doesn’t finish daily cron with merged pdiffs

[Debian Bug Tracking System]

Processing control commands:

> severity 980923 serious
Bug #980923 [apt-cacher-ng] acngtools eats all the CPU and doesn’t finish daily 
cron with merged pdiffs
Severity set to 'serious' from 'important'

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

Bug#966967: marked as done (libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 22:00:18 +
with message-id 
and subject line Bug#966967: fixed in libunity 7.1.4+19.04.20190319-3
has caused the Debian Bug report #966967,
regarding libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 
returned exit code 2
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.)


-- 
966967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libunity
Version: 7.1.4+19.04.20190319-2
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):
> make[5]: Entering directory '/<>/test/python'
> make[5]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
> rule.
> make[5]: Leaving directory '/<>/test/python'
> FAIL: bug-1062331.py
> FAIL: container-ownership.py
> FAIL: scope-result.py
> 
>libunity 7.1.4: test/python/test-suite.log
> 
> 
> # TOTAL: 4
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  4
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: bug-1062331
> =
> 
> ./bug-1062331.py:4: PyGIWarning: Unity was imported without specifying a 
> version first. Use gi.require_version('Unity', '7.0') before import to ensure 
> that the right version gets loaded.
>   from gi.repository import Unity
> Traceback (most recent call last):
>   File "./bug-1062331.py", line 6, in 
> generic_preview = Unity.GenericPreview.new("Title", "Description", None)
> gi.repository.GLib.Error: g-invoke-error-quark: Could not locate 
> unity_generic_preview_new: 'unity_generic_preview_new': /usr/bin/python3: 
> undefined symbol: unity_generic_preview_new (1)
> FAIL bug-1062331.py (exit status: 1)
> 
> FAIL: extras
> 
> 
> ./extras.py:3: PyGIWarning: UnityExtras was imported without specifying a 
> version first. Use gi.require_version('UnityExtras', '7.0') before import to 
> ensure that the right version gets loaded.
>   from gi.repository import UnityExtras
> Traceback (most recent call last):
>   File "./extras.py", line 5, in 
> player = UnityExtras.PreviewPlayer.new ()
> gi.repository.GLib.Error: g-invoke-error-quark: Could not locate 
> unity_extras_preview_player_new: 'unity_extras_preview_player_new': 
> /usr/bin/python3: undefined symbol: unity_extras_preview_player_new (1)
> FAIL extras.py (exit status: 1)
> 
> FAIL: container-ownership
> =
> 
> ./container-ownership.py:2: PyGIWarning: Unity was imported without 
> specifying a version first. Use gi.require_version('Unity', '7.0') before 
> import to ensure that the right version gets loaded.
>   from gi.repository import Unity, Gio
> Traceback (most recent call last):
>   File "./container-ownership.py", line 4, in 
> category_set = Unity.CategorySet.new()
> gi.repository.GLib.Error: g-invoke-error-quark: Could not locate 
> unity_category_set_new: 'unity_category_set_new': /usr/bin/python3: undefined 
> symbol: unity_category_set_new (1)
> FAIL container-ownership.py (exit status: 1)
> 
> FAIL: scope-result
> ==
> 
> ./scope-result.py:2: PyGIWarning: Unity was imported without specifying a 
> version first. Use gi.require_version('Unity', '7.0') before import to ensure 
> that the right version gets loaded.
>   from gi.repository import Unity, GLib
> /usr/lib/python3/dist-packages/gi/types.py:220: Warning: cannot derive 
> '__main__+TestResultSet' from non-derivable parent type 'void'
>   _gi.type_register(cls, namespace.get('__gtype_name__'))
> Traceback (most recent call last):
>   File "./scope-result.py", line 4, in 
> class TestResultSet(Unity.ResultSet):
>   File "/usr/lib/python3/dist-packages/gi/types.py", line 229, in __init__
> super(GObjectMeta, cls).__init__(name, bases, dict_)
>   File "/usr/lib/python3/dist-packages/gi/types.py", line 208, in __init__
> cls._type_register(cls.__dict__)
>   File "/usr/lib/python3/dist-packages/gi/types.py", line 220, in 
> _type_register
> _gi.type_register(cls, namespace.get('__gtype_name__'))
> RuntimeError: could not create new GType: __main__+TestResultSet (subclass of 
> void)
> FAIL scope-result.py (exit status: 1)
> 
> 
> Testsuite summary for libunity 7.1.4
> 
> 

Bug#981508: mercurial autopkgtest breaks with newer git

[Ivo De Decker]

package: mercurial
version: 5.6.1-1
severity: serious

Hi,

The mercurial autopkgtest fails with the latest git:

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mercurial/10134722/log.gz

It seems the output of git changed in a way that the test didn't expect.

I suspect this will be fixed by this upstream change:

https://www.mercurial-scm.org/repo/hg/rev/88dfe1c279bb

Cheers,

Ivo

Bug#975173: marked as done (git: FTBFS: test failed)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 22:43:00 +0100
with message-id <20210131214259.ga25...@debian.org>
and subject line Re: git: FTBFS: test failed
has caused the Debian Bug report #975173,
regarding git: FTBFS: test failed
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.)


-- 
975173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git
Version: 1:2.29.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> *** t3100-ls-tree-restrict.sh ***
> Initialized empty Git repository in /<>/t/trash 
> directory.t3100-ls-tree-restrict/.git/
> expecting success of 3100.1 'setup': mkdir path2 path2/baz &&
>  echo Hi >path0 &&
>  test_ln_s_add path0 path1 &&
>  test_ln_s_add ../path1 path2/bazbo &&
>  echo Lo >path2/foo &&
>  echo Mi >path2/baz/b &&
>  find path? \( -type f -o -type l \) -print |
>  xargs git update-index --add &&
>  tree=$(git write-tree) &&
>  echo $tree
> checking prerequisite: SYMLINKS
> 
> mkdir -p "$TRASH_DIRECTORY/prereq-test-dir" &&
> (
>   cd "$TRASH_DIRECTORY/prereq-test-dir" &&
>   # test whether the filesystem supports symbolic links
>   ln -s x y && test -h y
> 
> )
> prerequisite SYMLINKS ok
> a384d4f8dd786f29d6da4705dee4c2c0bc6b5049
> ok 1 - setup
> 
> expecting success of 3100.2 'ls-tree plain': git ls-tree $tree >current &&
>  cat >expected <<\EOF &&
> 100644 blob X path0
> 12 blob X path1
> 04 tree X path2
> EOF
>  test_output
> ok 2 - ls-tree plain
> 
> expecting success of 3100.3 'ls-tree recursive': git ls-tree -r $tree 
> >current &&
>  cat >expected <<\EOF &&
> 100644 blob X path0
> 12 blob X path1
> 100644 blob X path2/baz/b
> 12 blob X path2/bazbo
> 100644 blob X path2/foo
> EOF
>  test_output
> ok 3 - ls-tree recursive
> 
> expecting success of 3100.4 'ls-tree recursive with -t': git ls-tree -r -t 
> $tree >current &&
>  cat >expected <<\EOF &&
> 100644 blob X path0
> 12 blob X path1
> 04 tree X path2
> 04 tree X path2/baz
> 100644 blob X path2/baz/b
> 12 blob X path2/bazbo
> 100644 blob X path2/foo
> EOF
>  test_output
> ok 4 - ls-tree recursive with -t
> 
> expecting success of 3100.5 'ls-tree recursive with -d': git ls-tree -r -d 
> $tree >current &&
>  cat >expected <<\EOF &&
> 04 tree X path2
> 04 tree X path2/baz
> EOF
>  test_output
> ok 5 - ls-tree recursive with -d
> 
> expecting success of 3100.6 'ls-tree filtered with path': git ls-tree $tree 
> path >current &&
>  cat >expected <<\EOF &&
> EOF
>  test_output
> ok 6 - ls-tree filtered with path
> 
> expecting success of 3100.7 'ls-tree filtered with path1 path0': git ls-tree 
> $tree path1 path0 >current &&
>  cat >expected <<\EOF &&
> 100644 blob X path0
> 12 blob X path1
> EOF
>  test_output
> ok 7 - ls-tree filtered with path1 path0
> 
> expecting success of 3100.8 'ls-tree filtered with path0/': git ls-tree $tree 
> path0/ >current &&
>  cat >expected <<\EOF &&
> EOF
>  test_output
> --- expected  2020-11-19 07:29:11.106032902 +
> +++ check 2020-11-19 07:29:11.106032902 +
> @@ -0,0 +1 @@
> +100644 blob Xpath0
> not ok 8 - ls-tree filtered with path0/
> # git ls-tree $tree path0/ >current &&
> #  cat >expected <<\EOF &&
> # EOF
> #  test_output
> 
> expecting success of 3100.9 'ls-tree filtered with path2': git ls-tree $tree 
> path2 >current &&
>  cat >expected <<\EOF &&
> 04 tree X path2
> EOF
>  test_output
> ok 9 - ls-tree filtered with path2
> 
> expecting success of 3100.10 'ls-tree filtered with path2/': git ls-tree 
> $tree path2/ >current &&
>  cat >expected <<\EOF &&
> 04 tree X path2/baz
> 12 blob X path2/bazbo
> 100644 blob X path2/foo
> EOF
>  test_output
> ok 10 - ls-tree filtered with path2/
> 
> expecting success of 3100.11 'ls-tree filtered with path2/baz': git ls-tree 
> $tree path2/baz >current &&
>  cat >expected <<\EOF &&
> 04 tree X path2/baz
> EOF
>  test_output
> ok 11 - ls-tree filtered with path2/baz
> 
> expecting success of 3100.12 'ls-tree filtered with path2/bak': git ls-tree 
> $tree path2/bak >current &&
>  cat >expected <<\EOF &&
> EOF
>  test_output
> ok 12 - ls-tree filtered with path2/bak
> 
> expecting success of 3100.13 'ls-tree -t filtered with path2/bak': git 
> ls-tree -t $tree 

Bug#981495: screenkey: FTBFS: E: pybuild pybuild:353: clean: plugin distutils failed with: exit code=1: python3.9 setup.py clean

[Sebastian Ramacher]

Source: screenkey
Version: 1:1.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

| I: pybuild base:232: python3.9 setup.py clean 
| WARNING: The pip package is not available, falling back to EasyInstall for 
handling setup_requires/test_requires; this is deprecated and will be removed 
in a future version.
| Download error on https://pypi.org/simple/babel/: [Errno 111] Connection 
refused -- Some packages may not be found!
| Couldn't find index page for 'babel' (maybe misspelled?)
| Download error on https://pypi.org/simple/: [Errno 111] Connection refused -- 
Some packages may not be found!
| No local packages or working download links found for babel
| Traceback (most recent call last):
|   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 60, in 
fetch_build_egg
| pkg_resources.get_distribution('pip')
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 466, 
in get_distribution
| dist = get_provider(dist)
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 342, 
in get_provider
| return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 886, 
in require
| needed = self.resolve(parse_requirements(requirements))
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 772, 
in resolve
| raise DistributionNotFound(req, requirers)
| pkg_resources.DistributionNotFound: The 'pip' distribution was not found and 
is required by the application
|
| During handling of the above exception, another exception occurred:
|
| Traceback (most recent call last):
|   File "/<>/setup.py", line 8, in 
| setup(name='screenkey', version='1.4',
|   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 152, in 
setup
| _install_setup_requires(attrs)
|   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 147, in 
_install_setup_requires
| dist.fetch_build_eggs(dist.setup_requires)
|   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 686, in 
fetch_build_eggs
| resolved_dists = pkg_resources.working_set.resolve(
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 766, 
in resolve
| dist = best[req.key] = env.best_match(
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1051, 
in best_match
| return self.obtain(req, installer)
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1063, 
in obtain
| return installer(requirement)
|   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 745, in 
fetch_build_egg
| return fetch_build_egg(self, req)
|   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 68, in 
fetch_build_egg
| return _legacy_fetch_build_egg(dist, req)
|   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 51, in 
_legacy_fetch_build_egg
| return cmd.easy_install(req)
|   File "/usr/lib/python3/dist-packages/setuptools/command/easy_install.py", 
line 688, in easy_install
| raise DistutilsError(msg)
| distutils.errors.DistutilsError: Could not find suitable distribution for 
Requirement.parse('babel')
| E: pybuild pybuild:353: clean: plugin distutils failed with: exit code=1: 
python3.9 setup.py clean 
| dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
code 13
| make: *** [debian/rules:13: clean] Error 25
| dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
exit status 2

See
https://buildd.debian.org/status/fetch.php?pkg=screenkey=all=1%3A1.4-1=1611862712=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#981494: pyfai: FTBFS on 32 bit archs: OverflowError: Python int too large to convert to C ssize_t

[Sebastian Ramacher]

Source: pyfai
Version: 0.20.0+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

| ==
| ERROR: setUpClass (pyFAI.test.test_histogram.TestHistogram1d)
| --
| Traceback (most recent call last):
|   File 
"/<>/.pybuild/cpython3_3.9_pyfai/build/pyFAI/test/test_histogram.py",
 line 90, in setUpClass
| integrator = HistoBBox1d(tth, delta_pos0=None, pos1=None, delta_pos1=None,
|   File "pyFAI/ext/splitBBoxCSR.pyx", line 146, in 
pyFAI.ext.splitBBoxCSR.HistoBBox1d.__init__
| lut = self.calc_lut_nosplit()
|   File "pyFAI/ext/splitBBoxCSR.pyx", line 457, in 
pyFAI.ext.splitBBoxCSR.HistoBBox1d.calc_lut_nosplit
| memsize = os.sysconf(key_page_size) * os.sysconf(key_page_cnt)
| OverflowError: Python int too large to convert to C ssize_t

See
https://buildd.debian.org/status/fetch.php?pkg=pyfai=i386=0.20.0%2Bdfsg1-1=1611932586=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Bug#954303 marked as pending in tika

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954303 [src:tika] tika: CVE-2020-1950
Added tag(s) pending.

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

Bug#954303: marked as pending in tika

[Moritz Muehlenhoff]

Control: tag -1 pending

Hello,

Bug #954303 in tika 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/java-team/tika/-/commit/1a8d36ebff54d00c2dda5d27671305ba16680855


* Cherrypick upstream commit to address CVE-2020-1950 and CVE-2020-1951
 (Closes: #954303, #954302)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954303

Bug#954302: marked as pending in tika

[Moritz Muehlenhoff]

Control: tag -1 pending

Hello,

Bug #954302 in tika 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/java-team/tika/-/commit/1a8d36ebff54d00c2dda5d27671305ba16680855


* Cherrypick upstream commit to address CVE-2020-1950 and CVE-2020-1951
 (Closes: #954303, #954302)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954302

Processed: Bug#954302 marked as pending in tika

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954302 [src:tika] tika: CVE-2020-1951
Added tag(s) pending.

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

Processed: Re: Bug#948739: gparted should not mask .mount units

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -pending
Bug #948739 [gparted] gparted should not mask .mount units
Removed tag(s) pending.

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

Bug#948739: gparted should not mask .mount units

[Ivo De Decker]

Control: tags -1 -pending

Hi,

On Fri, Jan 29, 2021 at 08:56:01AM -0500, Phillip Susi wrote:
> John Paul Adrian Glaubitz writes:
> 
> > Hello!
> >
> > It looks like this particular issue has been fixed in gparted 1.2.0 which
> > was just released a few days ago [1]:
> >
> >> - Don't try to mask non-existent Systemd \xe2\x97\x8f.service (#129, !64)
> >
> > Might be an idea to update gparted to version 1.2.0 before the Bullseye 
> > freeze
> > which is coming in Mid-February [2].
> 
> Thanks... on it.

This new upstream version doesn't remove the code masking the systemd units.
It just changes it a little. So it doesn't fix this bug.

I don't know if there's already an upstream bug describing the issue, but that
might be needed to get the bug resolved upstream.

Cheers,

Ivo

Processed: severity of 980338 is serious

[Debian Bug Tracking System]

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

> severity 980338 serious
Bug #980338 [src:hotswap] hotswap: should ship with bullseye?
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 980348 is serious

[Debian Bug Tracking System]

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

> severity 980348 serious
Bug #980348 [src:ruby-wirble] ruby-wirble: ship with bullseye?
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#936880: marked as done (libiptcdata: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 21:09:39 +
with message-id 
and subject line Bug#936880: fixed in libiptcdata 1.0.5-2.3
has caused the Debian Bug report #936880,
regarding libiptcdata: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libiptcdata
Version: 1.0.5-2.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:libiptcdata

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: libiptcdata
Source-Version: 1.0.5-2.3
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
libiptcdata, 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 936...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated libiptcdata 
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: Sun, 31 Jan 2021 21:35:18 +0100
Source: libiptcdata
Architecture: source
Version: 1.0.5-2.3
Distribution: unstable
Urgency: medium
Maintainer: Ian Wienand 
Changed-By: Sebastian Ramacher 
Closes: 936880
Changes:
 libiptcdata (1.0.5-2.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Jann Haber ]
   * Drop binary package python-iptcdata. (Closes: #936880)
 .
   [ Sebastian Ramacher ]
   * Remove python, etc scripts from debian/bin again
Checksums-Sha1:
 d48828eb5f6d34da4a68d0840a9fb0a3fa7cf821 2310 libiptcdata_1.0.5-2.3.dsc
 07e23ef41ee018879007b8748b6e2f8e12acc95f 7560 
libiptcdata_1.0.5-2.3.debian.tar.xz
Checksums-Sha256:
 c1b2d35af90f4a9f902398324eadca96bc21fb76524e7366560db2a27977bda7 2310 
libiptcdata_1.0.5-2.3.dsc
 5fa7eff9c077241c9c7c8ea5ecd57483abdc54ab4289f24a4fa7445cea440070 7560 
libiptcdata_1.0.5-2.3.debian.tar.xz
Files:
 d27ec9310d888fee895f84c7596216a7 2310 libs optional 

Processed: block 978710 with 976735

[Debian Bug Tracking System]

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

> block 978710 with 976735
Bug #978710 [ftp.debian.org] RM: python3.8 -- ROM; superseded by python3.9
978710 was not blocked by any bugs.
978710 was not blocking any bugs.
Added blocking bug(s) of 978710: 976735 and 978648
> thanks
Stopping processing here.

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

Processed: Re: Bug#980903: debhelper: doc-base doc-id deduplication does not work as documented with multiple "dh_installdocs -p" calls; causes /usr/share/doc-base/ to be installed multip

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #980903 [debhelper] debhelper: doc-base doc-id deduplication does not work 
as documented with multiple "dh_installdocs -p" calls; causes 
/usr/share/doc-base/ to be installed multiple times
Severity set to 'important' from 'serious'

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

Bug#980903: debhelper: doc-base doc-id deduplication does not work as documented with multiple "dh_installdocs -p" calls; causes /usr/share/doc-base/ to be installed multiple times

[Axel Beckert]

Control: severity -1 important

Hi Niels,

I've now added one paragraph to the POD of dh_installdocs:

  Please be aware that this deduplication currently only works if
  B is called only once during the package build as
  deduplication is done in memory only. Especially calling
  BI in combination with using
  FIF<.doc-base.*> files can lead to uninstallable
  packages. See L for details.

Cc'ing debian-l10n-english@l.d.o for input on this phrasing as per
https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.en.html#write-correct-english

I also regenerated to .po files and committed them, too, in a separate
commit and pushed both commits to master.

Axel Beckert wrote:
> > Assuming you wish to have this fixed for bullseye,
> 
> As I wrote, I'm fine with proper documentation on this as alternative
> to a code change as I do see that there is a potential for regressions
> even though I don't see yet where actually a regression would be
> possible. (But that's a common property of regressions, isn't it.)
> 
> So unless someone else does a (positive) review of my proposed patch,
> I won't commit that one to the master branch.

Didn't get any feedback so far, so I went down the "document the
issue" route. Downgraded the bug report accordingly with this mail,
too.

> >  1) Please base your work on debhelper's master branch.

Done for the documentation part. Will rebase the other branch with the
actual fix later, too.

> >  2) I will expect you to handle the relevant release engineering
> > (i.e. uploads, unblock requests as necessary, etc.) along
> > with tackling regressions for this feature should any occurs.
> 
> Will do.
> 
> > (Feel free to upload debhelper using "Team Upload" rather than "NMU"
> > rules.)
> 
> Yep, as mentioned, I still feel like belonging to the team, despite
> more in a fifth wheel way with you being the other four wheels. ;-)
> 
> >  3) Please do a call for updates to existing translations once you are
> > done
> 
> Done in git or done with a first upload?
[…]
> > - I am fine with doing a translation-only update after you are done,
> >   so you do not need to follow up on that (unless you change strings
> >   after the calls for translations).
> 
> Ok, thanks. So I assume my question above is answered by "done with a
> first upload".

I still think I should first ask debian-l10n-english. Done herewith,
see above.

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

Bug#936880: libiptcdata: diff for NMU version 1.0.5-2.3

[Sebastian Ramacher]

Dear maintainer,

I've prepared an NMU for libiptcdata (versioned as 1.0.5-2.3). The diff
is attached to this message.

Regards.
-- 
Sebastian Ramacher
diff -Nru libiptcdata-1.0.5/debian/bin/pydoc libiptcdata-1.0.5/debian/bin/pydoc
--- libiptcdata-1.0.5/debian/bin/pydoc	2020-08-08 22:18:23.0 +0200
+++ libiptcdata-1.0.5/debian/bin/pydoc	1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-#! /bin/sh
-exec pydoc2 "$@"
diff -Nru libiptcdata-1.0.5/debian/bin/python libiptcdata-1.0.5/debian/bin/python
--- libiptcdata-1.0.5/debian/bin/python	2020-08-08 22:18:23.0 +0200
+++ libiptcdata-1.0.5/debian/bin/python	1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-#! /bin/sh
-exec python2 "$@"
diff -Nru libiptcdata-1.0.5/debian/bin/python-config libiptcdata-1.0.5/debian/bin/python-config
--- libiptcdata-1.0.5/debian/bin/python-config	2020-08-08 22:18:23.0 +0200
+++ libiptcdata-1.0.5/debian/bin/python-config	1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-#! /bin/sh
-exec python2-config "$@"
diff -Nru libiptcdata-1.0.5/debian/changelog libiptcdata-1.0.5/debian/changelog
--- libiptcdata-1.0.5/debian/changelog	2020-08-08 22:18:23.0 +0200
+++ libiptcdata-1.0.5/debian/changelog	2021-01-31 21:35:18.0 +0100
@@ -1,3 +1,15 @@
+libiptcdata (1.0.5-2.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Jann Haber ]
+  * Drop binary package python-iptcdata. (Closes: #936880)
+
+  [ Sebastian Ramacher ]
+  * Remove python, etc scripts from debian/bin again
+
+ -- Sebastian Ramacher   Sun, 31 Jan 2021 21:35:18 +0100
+
 libiptcdata (1.0.5-2.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libiptcdata-1.0.5/debian/control libiptcdata-1.0.5/debian/control
--- libiptcdata-1.0.5/debian/control	2019-02-24 17:12:43.0 +0100
+++ libiptcdata-1.0.5/debian/control	2021-01-31 21:33:27.0 +0100
@@ -8,7 +8,7 @@
  debhelper (>= 10~),
  dh-buildinfo,
  dh-autoreconf,
- licensecheck, dpkg-dev (>= 1.13.19), gtk-doc-tools, pkg-config, python-all-dev (>= 2.6.6-3~), dh-python
+ licensecheck, dpkg-dev (>= 1.13.19), gtk-doc-tools, pkg-config
 Standards-Version: 4.2.1.1
 Vcs-Browser: https://salsa.debian.org/debian/libiptcdata
 Vcs-Git: https://salsa.debian.org/debian/libiptcdata.git
@@ -66,16 +66,3 @@
  Telecommunications Council (IPTC) metadata stored within multimedia
  files such as images. The library provides routines for parsing,
  viewing, modifying, and saving this metadata.
-
-Package: python-iptcdata
-Architecture: any
-Section: python
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Provides: ${python:Provides}
-Description: Python bindings for the iptcdata library
- libiptcdata is a library, for manipulating the International Press
- Telecommunications Council (IPTC) metadata stored within multimedia
- files such as images. The library provides routines for parsing,
- viewing, modifying, and saving this metadata.
- .
- This package contains the python bindings for libiptcdata.
diff -Nru libiptcdata-1.0.5/debian/control.in libiptcdata-1.0.5/debian/control.in
--- libiptcdata-1.0.5/debian/control.in	2019-02-24 17:12:43.0 +0100
+++ libiptcdata-1.0.5/debian/control.in	2021-01-31 21:33:27.0 +0100
@@ -2,7 +2,7 @@
 Section: libs
 Priority: optional
 Maintainer: Ian Wienand 
-Build-Depends: @cdbs@, dpkg-dev (>= 1.13.19), gtk-doc-tools, pkg-config, python-all-dev (>= 2.6.6-3~), dh-python
+Build-Depends: @cdbs@, dpkg-dev (>= 1.13.19), gtk-doc-tools, pkg-config
 Standards-Version: 4.2.1.1
 Vcs-Browser: https://salsa.debian.org/debian/libiptcdata
 Vcs-Git: https://salsa.debian.org/debian/libiptcdata.git
@@ -61,16 +61,3 @@
  Telecommunications Council (IPTC) metadata stored within multimedia
  files such as images. The library provides routines for parsing,
  viewing, modifying, and saving this metadata.
-
-Package: python-iptcdata
-Architecture: any
-Section: python
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Provides: ${python:Provides}
-Description: Python bindings for the iptcdata library
- libiptcdata is a library, for manipulating the International Press
- Telecommunications Council (IPTC) metadata stored within multimedia
- files such as images. The library provides routines for parsing,
- viewing, modifying, and saving this metadata.
- .
- This package contains the python bindings for libiptcdata.
diff -Nru libiptcdata-1.0.5/debian/rules libiptcdata-1.0.5/debian/rules
--- libiptcdata-1.0.5/debian/rules	2020-08-08 22:18:23.0 +0200
+++ libiptcdata-1.0.5/debian/rules	2021-01-31 21:34:06.0 +0100
@@ -22,9 +22,6 @@
 # Generate debian/control using
 # fakeroot debian/rules debian/control DEB_AUTO_UPDATE_DEBIAN_CONTROL:=yes
 
-PATH := $(PATH):$(CURDIR)/debian/bin
-export PATH
-
 DEB_DH_INSTALL_SOURCEDIR = $(CURDIR)/debian/tmp
 
 include /usr/share/cdbs/1/rules/debhelper.mk
@@ -32,15 +29,13 @@
 include /usr/share/cdbs/1/rules/autoreconf.mk
 include /usr/share/cdbs/1/rules/utils.mk
 
-PY_VERSIONS = 

Bug#978360: marked as done (python-whoosh: FTBFS: AttributeError: 'NullMatcherClass' object has no attribute '__name__')

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 21:18:44 +0100
with message-id 
and subject line Re: Bug#978360: python-whoosh: FTBFS: AttributeError: 
'NullMatcherClass' object has no attribute '__name__'
has caused the Debian Bug report #978360,
regarding python-whoosh: FTBFS: AttributeError: 'NullMatcherClass' object has 
no attribute '__name__'
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.)


-- 
978360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-whoosh
Version: 2.7.4+git6-g9134ad92-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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 '/<>'
> dh_auto_build --buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/externalsort.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/idsets.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/scoring.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/fields.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/index.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/highlight.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/columns.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/searching.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/compat.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/sorting.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/spelling.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/legacy.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/formats.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/multiproc.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/classify.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/collectors.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/writing.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/system.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> copying src/whoosh/reading.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh
> creating /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/analysis
> copying src/whoosh/analysis/analyzers.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/analysis
> copying src/whoosh/analysis/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/analysis
> copying src/whoosh/analysis/ngrams.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/analysis
> copying src/whoosh/analysis/tokenizers.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/analysis
> copying src/whoosh/analysis/intraword.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/analysis
> copying src/whoosh/analysis/acore.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/analysis
> copying src/whoosh/analysis/morph.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/analysis
> copying src/whoosh/analysis/filters.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/analysis
> creating /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/util
> copying src/whoosh/util/versions.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/util
> copying src/whoosh/util/cache.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/util
> copying src/whoosh/util/text.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/util
> copying src/whoosh/util/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/util
> copying src/whoosh/util/varints.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/util
> copying src/whoosh/util/loading.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/util
> copying src/whoosh/util/times.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/util
> copying src/whoosh/util/numlists.py -> 
> /<>/.pybuild/cpython3_3.9_whoosh/build/whoosh/util
> copying src/whoosh/util/filelock.py -> 
> 

Processed: Re: Bug#973082: confirmed

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 
> https://bitbucket.org/wooster/biplist/issues/12/python-39-compatibility
Bug #973082 [src:python-biplist] python-biplist: FTBFS: dh_auto_test: error: 
pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13
Set Bug forwarded-to-address to 
'https://bitbucket.org/wooster/biplist/issues/12/python-39-compatibility'.
> tag -1 + patch
Bug #973082 [src:python-biplist] python-biplist: FTBFS: dh_auto_test: error: 
pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) patch.

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

Bug#973082: confirmed

[Stefano Rivera]

Control: forwarded -1 
https://bitbucket.org/wooster/biplist/issues/12/python-39-compatibility
Control: tag -1 + patch

Hi Hans-Christoph (2021.01.03_13:54:51_-0700)
> In Python 3.9, the plistlib was changed to no longer have the internal data
> structure plistlib.Data, which biplist relied on.

From what I can see one just uses bytes instead of plistlib.Data, so
this should work on Python 3.9:

diff --git a/biplist/__init__.py b/biplist/__init__.py
index f9d5836..4a40602 100644
--- a/biplist/__init__.py
+++ b/biplist/__init__.py
@@ -147,14 +147,7 @@ def readPlist(pathOrFile):
 return result
 
 def wrapDataObject(o, for_binary=False):
-if isinstance(o, Data) and not for_binary:
-v = sys.version_info
-if not (v[0] >= 3 and v[1] >= 4):
-o = plistlib.Data(o)
-elif isinstance(o, (bytes, plistlib.Data)) and for_binary:
-if hasattr(o, 'data'):
-o = Data(o.data)
-elif isinstance(o, tuple):
+if isinstance(o, tuple):
 o = wrapDataObject(list(o), for_binary)
 o = tuple(o)
 elif isinstance(o, list):

It's not the correct backwards-compatible fix, though. So not proposing this 
upstream.

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

Bug#981484: webext-exteditor: not compatible with current thunderbird

[Ivo De Decker]

package: webext-exteditor
version: 2.0.4-1
severity: serious

Hi,

Thunderbird 1:78.7.0-1 has 'Breaks: webext-exteditor (<= 2.0.4-1)', which
means webext-exteditor doesn't work with it.

Cheers,

Ivo

Bug#981483: python3-extractor: fails to install "TabError: inconsistent use of tabs and spaces in indentation"

[Ivo De Decker]

package: python3-extractor
version: 1:0.6-8
severity: serious

Hi,

Piuparts detected an installation error in python3-extractor:

  Setting up python3.9 (3.9.1-3) ...
  Setting up python3 (3.9.1-1) ...
  Setting up python3-extractor (1:0.6-8) ...
  Sorry: TabError: inconsistent use of tabs and spaces in indentation 
(extractor.py, line 82)
  dpkg: error processing package python3-extractor (--configure):
   installed python3-extractor package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.31-9) ...
  Errors were encountered while processing:
   python3-extractor
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  

https://piuparts.debian.org/sid/fail/python3-extractor_1:0.6-8.log

Cheers,

Ivo

Processed: src:abseil: fails to migrate to testing for too long: FTBFS everywhere

[Debian Bug Tracking System]

Processing control commands:

> close -1 0~20200923.2-2
Bug #981482 [src:abseil] src:abseil: fails to migrate to testing for too long: 
FTBFS everywhere
Marked as fixed in versions abseil/0~20200923.2-2.
Bug #981482 [src:abseil] src:abseil: fails to migrate to testing for too long: 
FTBFS everywhere
Marked Bug as done
> block -1 by 976575
Bug #981482 {Done: Paul Gevers } [src:abseil] src:abseil: 
fails to migrate to testing for too long: FTBFS everywhere
981482 was not blocked by any bugs.
981482 was not blocking any bugs.
Added blocking bug(s) of 981482: 976575

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

Bug#981482: src:abseil: fails to migrate to testing for too long: FTBFS everywhere

[Paul Gevers]

Source: abseil
Version: 0~20200923.2-1
Severity: serious
Control: close -1 0~20200923.2-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 976575

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:abseil in its
current version in unstable has been trying to migrate for 61 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=abseil




OpenPGP_signature
Description: OpenPGP digital signature

Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x

[Dirk Eddelbuettel]

On 31 January 2021 at 20:09, Graham Inggs wrote:
| Hi Dirk
| 
| On Sun, 31 Jan 2021 at 16:13, Dirk Eddelbuettel  wrote:
| > This is a bug in glmmTMB.
| 
| I don't see how you can be so sure.

Experience around R. glmmTMB is a huge package with many dependencies, there
will be a stale one in the path. I can "almost guarantee you" that with a
clean rebuild of all components it will pass. As it does on every other
platform.

Dirk

| > All the 'gradient function must ...' errors are from its tests and
| > points to me to a recent change in R (where boolean comparisons can now 
check
| > if the compared vector is corre.  The Matrix change may simply be the 
trigger.
| 
| This seems to be unrelated to the version of R.  If you look at the
| test results in Ubuntu [1], the failures started with the upload of
| rmatrix/1.3-0-1, continued with rmatrix/1.3-2-1, and then went away
| when rmatrix was reverted to 1.2-18.
| 
| This doesn't mean there's a bug in rmatrix, it could be an expected
| change in behaviour (on big-endian systems).  If this is the case,
| then r-cran-glmmtmb needs to be adapted for this new behaviour.
| 
| Regards
| Graham
| 
| 
| [1] https://autopkgtest.ubuntu.com/packages/r/r-cran-glmmtmb/hirsute/s390x

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Processed: retitle 941714 to bst-external: file conflict: installs .coverage file

[Debian Bug Tracking System]

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

> retitle 941714 bst-external: file conflict: installs .coverage file
Bug #941714 [src:bst-external] bst-external: please make the build reproducible
Changed Bug title to 'bst-external: file conflict: installs .coverage file' 
from 'bst-external: please make the build reproducible'.
> thanks
Stopping processing here.

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

Bug#981474: marked as done (node-rollup-plugin-terser: test randomly fails due to timeout problems)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 19:06:49 +
with message-id 
and subject line Bug#981474: fixed in node-rollup-plugin-terser 7.0.2-5
has caused the Debian Bug report #981474,
regarding node-rollup-plugin-terser: test randomly fails due to timeout problems
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.)


-- 
981474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-rollup-plugin-terser
Version: 7.0.2-4
Severity: serious
Tags: ftbfs
Justification: Policy 2.1

https://ci.debian.net/packages/n/node-rollup-plugin-terser/testing/amd64/
shows that node-rollup-plugin-terser test randomly fails
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-terser
Source-Version: 7.0.2-5
Done: Xavier Guimard 

We believe that the bug you reported is fixed in the latest version of
node-rollup-plugin-terser, 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 981...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-rollup-plugin-terser 
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: Sun, 31 Jan 2021 19:35:00 +0100
Source: node-rollup-plugin-terser
Architecture: source
Version: 7.0.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 981474
Changes:
 node-rollup-plugin-terser (7.0.2-5) unstable; urgency=medium
 .
   * Team upload
   * Increase test timeout (Closes: #981474)
   * Remove obsolete field Contact from debian/upstream/metadata
 (already present in machine-readable debian/copyright).
   * Bump debhelper compatibility level to 13
   * Add "Rules-Requires-Root: no"
Checksums-Sha1: 
 39f653c8d15a9bbbd4979a16b48ed5fe67dfc92d 2358 
node-rollup-plugin-terser_7.0.2-5.dsc
 2513485b176432e347bf5e6e98d3e74639458fec 4672 
node-rollup-plugin-terser_7.0.2-5.debian.tar.xz
Checksums-Sha256: 
 1eb82b7d0078be81268c1e4aabf30f79105297bdea3f3cacb1621537e30172ba 2358 
node-rollup-plugin-terser_7.0.2-5.dsc
 fcb2d7753f978e4d25d834542206412219dcf3a1492bcb2166c5e665b25db30d 4672 
node-rollup-plugin-terser_7.0.2-5.debian.tar.xz
Files: 
 712b78f94dda0847943dfc6a4bdf2987 2358 javascript optional 
node-rollup-plugin-terser_7.0.2-5.dsc
 37533060e3072dbca6ab017a3b30c844 4672 javascript optional 
node-rollup-plugin-terser_7.0.2-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmAW+MwACgkQ9tdMp8mZ
7unfJQ/9GvqzPLhIui5Lkkc2WZNhaxpmZY2HZtPo01q+bg13bqrrRQoGHFdf79tV
b1IaqT/av8HStdkZb3s8FKz7oPgV1/QlScl1VhBx+M8pFg9pOOoUBF7KroxoH+Kc
V8BG/oZDdNP0MvntlGswU2pNeIhSuHgPX2ff/uWQmjWjW8S6+K0/+/wvbmkGI9dR
7G4e+gIF0lLoIMEaVJU9vluf1vjxdTTTdLcpF5HiEUuqSbu5oUpRC9w8k4wkeSSI
4E0SfDIv0aqP9FcL6QiIrTkcd2inHT65ueBjq7uTpb2TaQ7y8C8RtPkx3qeoPqRy
Irwn3/K2iie0+2AsSpL1Ur5PkfX4VCVto7uF8jaiRsqs9hig81XsTGZouw/5ltzC
e6dkHJIP7PUTGJdsyDRmZxsXcvEiaHhXSTIb7j1s8YfCJmQUmeRm9McVSL8+E8Oa
KHfiC2PWnjKhZhJvp4xjuN5Vdn9kfi7JVebm85h0onpB5VTjrhY7cmbIGMS82b2P
cPXIWeTSsIFxuC/lapRcNpDUh2rQxC7kDOJ4jQmUNw+ndKVI3tRCoeEemrvLE0W2
Ah8//PrasFq26+uyXrLJdNlDEDbbBGuX/gRARfwkXRQUncIAdZ65UTzbXxz8DGyr
BJ+t2WZOonOtMDkS5n8RUoiQFobsr4a6a8VjRoh8YL352HX8S0o=
=Rfw3
-END PGP SIGNATURE End Message ---

Bug#979012: marked as done (minetest-data: debian/copyright needs updating)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 18:54:45 +
with message-id 
and subject line Bug#979012: fixed in minetest 5.3.0+repack-2
has caused the Debian Bug report #979012,
regarding minetest-data: debian/copyright needs updating
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.)


-- 
979012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: minetest-data
Version: 0.4.15+repack-1
Severity: serious
Justification: Policy 12.5

Dear Maintainer,

minetest-data 0.4.15 cleaned up usage of the WTFPL license, but
debian/copyright still references it. It looks like the MIT license was
chosen to replace the existing license, but it was not added to
debian/copyright when 0.4.15 was released. I assume that these were just
unintentional omissions and should be easy to resolve.

Additionally the upstream source is incomplete:
 - games/minetest_game/* files can be found at
   https://github.com/minetest/minetest_game
 - games/minetest_game/mods/$name/* files can be found at
   https://github.com/minetest-game-mods/$name

Thanks!
Norman

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

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

Versions of packages minetest-data depends on:
pn  fonts-croscore
pn  fonts-droid-fallback  

minetest-data recommends no packages.

minetest-data suggests no packages.
--- End Message ---
--- Begin Message ---
Source: minetest
Source-Version: 5.3.0+repack-2
Done: Bruno Kleinert 

We believe that the bug you reported is fixed in the latest version of
minetest, 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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bruno Kleinert  (supplier of updated minetest 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: Sun, 31 Jan 2021 14:41:26 +0100
Source: minetest
Architecture: source
Version: 5.3.0+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Bruno Kleinert 
Closes: 979012
Changes:
 minetest (5.3.0+repack-2) unstable; urgency=medium
 .
   * Team upload.
   * Fixed 'minetest-data: debian/copyright needs updating'. Reflect upstream
 license changes in copyright documentation. (Closes: #979012)
Checksums-Sha1:
 c6f79ffdfd7c6ec3ea7bf25971fcca539f2b976f 2616 minetest_5.3.0+repack-2.dsc
 d5eee2696b39da6a681d36cea122837b3e21 37732 
minetest_5.3.0+repack-2.debian.tar.xz
 b74c36b656b99cec80a4e375e37304d06711e530 6119 
minetest_5.3.0+repack-2_source.buildinfo
Checksums-Sha256:
 d7b8c69b616fecfff3c8ba1e671407948dd6d143b52017dfa2ff3296128045f4 2616 
minetest_5.3.0+repack-2.dsc
 e1f3c5a156f425b8b0413f9555372f6d90548bc7d1261fceaca3e9afe801 37732 
minetest_5.3.0+repack-2.debian.tar.xz
 12dcc6374cd80a2a6173fd6a2a942ceff5b96019d63933601fc09ef27295c772 6119 
minetest_5.3.0+repack-2_source.buildinfo
Files:
 fed78fe88aacb94944e0fb5b8e40f57e 2616 games optional 
minetest_5.3.0+repack-2.dsc
 da341781f33968468a3b1ed91fd181f9 37732 games optional 
minetest_5.3.0+repack-2.debian.tar.xz
 c12d3cbbbfa73be5a5cf5d579df04d19 6119 games optional 
minetest_5.3.0+repack-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEbNBoYg3hPRuThXIzSwBpzPZSeEcFAmAW95ARHGZ1ZGRsQGRl
Ymlhbi5vcmcACgkQSwBpzPZSeEc8eQ/+M54lTmRlYYaZc1T5p96CMnahjG+IcR7k
8yQF6PT6+RmkSYU/Wr3Q5P23qXOS2tRTrXHmlKu0Y2HpzbhUeZsfvO8Dgo2Ss4HI
NOpq5Hn3fPYJqHR1i+QeJjVdQ3yRNzIHp+un997iQ5zOoBFDPUREYvnlix6w8yXv
R99hbHr+pGnAQr5U6Gf/xpNez9Yzk5qjdOW6izfz+xArtjFdIhmbt/a2ISrtbd8A
sKRQiLUItggEqWdNVDAp5saauDuKcH9zrc2itkzXHhfzbhG0eKiSZoZihpx30Z5x
a+SGFBjYgjcxM+f6MRlMXjMsBxFweCv2Lh/fuk5LLmvjZd5kwkWEd2H/j2E/MJv/
RDU7oIkN64HczRK6Jp0eUQ7ojkZQ89aGI6pLXK+Al4qEPESAL2JbP3zFqi4lk4c8
6S0+u9Qr4rTSZZPCrLJ/+Kx+7WbyXk/RPAOBjT4WYOV7A/T8PNx8WR9+wL3WFEss

Bug#981461: ser2net: unable to start, undefined symbol: gensio_alloc_mdns

[Gedalya]

Package: ser2net
Version: 4.3.2-1
Severity: grave

When attempting to start ser2net I get the message:
/usr/sbin/ser2net: symbol lookup error: /usr/sbin/ser2net: undefined 
symbol: gensio_alloc_mdns
This happens when I start it in any way, such as just invoking the 
executable with no parameters, or as:

/usr/sbin/ser2net -c /etc/ser2net.yaml
However the parameters -h and -v do work.

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

Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ser2net depends on:
ii  libc6    2.31-9
ii  libgensio0   2.2.3-1
ii  libyaml-0-2  0.2.2-1
ii  lsb-base 11.1.0

ser2net recommends no packages.

Versions of packages ser2net suggests:
ii  telnet  0.17-41.2

-- Configuration Files:
/etc/ser2net.conf changed:
BANNER:banner:\r\nser2net port \p device \d [\s] (Debian GNU/Linux)\r\n\r\n
2000:raw:600:/dev/ttyS0:9600 8DATABITS NONE 1STOPBIT
2001:raw:600:/dev/ttyS1:9600 8DATABITS NONE 1STOPBIT
3000:raw:600:/dev/ttyS0:115200 8DATABITS NONE 1STOPBIT
3001:raw:600:/dev/ttyS1:115200 8DATABITS NONE 1STOPBIT

/etc/ser2net.yaml changed:
%YAML 1.1
---
define:  \r\nser2net port \p device \d [\B] (Debian 
GNU/Linux)\r\n\r\n

connection: 
    accepter: tcp,2000
    enable: on
    options:
  banner: *banner
  kickolduser: true
  telnet-brk-on-sync: true
    connector: serialdev,
  /dev/ttyS0,
  9600n81,local
connection: 
    accepter: telnet(rfc2217),tcp,3000
    enable: on
    options:
  banner: *banner
  kickolduser: true
  telnet-brk-on-sync: true
    connector: serialdev,
  /dev/ttyS0,
  19200n81,local


-- no debconf information

Processed: Bug#981474 marked as pending in node-rollup-plugin-terser

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #981474 [node-rollup-plugin-terser] node-rollup-plugin-terser: test 
randomly fails due to timeout problems
Added tag(s) pending.

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

Bug#981474: marked as pending in node-rollup-plugin-terser

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #981474 in node-rollup-plugin-terser 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/js-team/node-rollup-plugin-terser/-/commit/e3df2a216bb82378d09c41244b115162f2d6b683


Increase test timeout

Closes: #981474


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/981474

Bug#981474: node-rollup-plugin-terser: test randomly fails due to timeout problems

[Xavier Guimard]

Package: node-rollup-plugin-terser
Version: 7.0.2-4
Severity: serious
Tags: ftbfs
Justification: Policy 2.1

https://ci.debian.net/packages/n/node-rollup-plugin-terser/testing/amd64/
shows that node-rollup-plugin-terser test randomly fails

Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x

[Graham Inggs]

Hi Dirk

On Sun, 31 Jan 2021 at 16:13, Dirk Eddelbuettel  wrote:
> This is a bug in glmmTMB.

I don't see how you can be so sure.

> All the 'gradient function must ...' errors are from its tests and
> points to me to a recent change in R (where boolean comparisons can now check
> if the compared vector is corre.  The Matrix change may simply be the trigger.

This seems to be unrelated to the version of R.  If you look at the
test results in Ubuntu [1], the failures started with the upload of
rmatrix/1.3-0-1, continued with rmatrix/1.3-2-1, and then went away
when rmatrix was reverted to 1.2-18.

This doesn't mean there's a bug in rmatrix, it could be an expected
change in behaviour (on big-endian systems).  If this is the case,
then r-cran-glmmtmb needs to be adapted for this new behaviour.

Regards
Graham


[1] https://autopkgtest.ubuntu.com/packages/r/r-cran-glmmtmb/hirsute/s390x

Bug#978364: apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side of an entry is empty)

[Tino Didriksen]

I did CC Kartik in the original mail. I assume it was lost in the crowd.
https://salsa.debian.org/science-team/apertium-rus-ukr is up-to-date and
bundled and is the only thing that wanted apertium-ukr, so after
apertium-rus-ukr is uploaded, apertium-ukr will be superfluous and should
be removed.

-- Tino Didriksen


On Sun, 31 Jan 2021 at 18:33, Nilesh Patra  wrote:

> Hi Tino,
>
> On Tue, 5 Jan 2021 01:13:56 +0100 Tino Didriksen 
> wrote:
> > apertium-ukr should be removed from Debian. The pair that needed it has
> > been upgraded to bundle the required version instead:
>
> If you agree, can I retitle and reassign to file in a removal bug for
> apertium-ukr, then?
> Also, I do not see apertium-rus-ukr at either the archive or the tracker -
> did this not get uploaded, yet?
>
> Nilesh

Bug#981435: libvirt: stops on upgrade: internal error: Failed to load module 'libvirt_driver_qemu.so': libvirt.so.0: version `LIBVIRT_PRIVATE_6.9.0' not found (required by libvirt_driver_qemu.so)

[Andrea Bolognani]

On Sun, Jan 31, 2021 at 04:36:21PM +0100, Andrea Bolognani wrote:
> I've opened
> 
>   https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/98
> 
> with the proposed patch, and I'm going to use the information you
> provided above to give it some testing now.

I've added a few extra Depends to make sure everything is really
updated in lockstep and tested with unattended-upgrades: the result
was much better this time!

  Log started: 2021-01-31  18:20:43
  (Reading database ... 87062 files and directories currently installed.)
  Preparing to unpack .../00-libnss-libvirt_7.0.0-1_amd64.deb ...
  Unpacking libnss-libvirt:amd64 (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../01-libvirt-sanlock_7.0.0-1_amd64.deb ...
  Unpacking libvirt-sanlock (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../02-libvirt-login-shell_7.0.0-1_amd64.deb ...
  Unpacking libvirt-login-shell (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../03-libvirt-dev_7.0.0-1_amd64.deb ...
  Unpacking libvirt-dev:amd64 (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../04-libvirt-daemon-config-nwfilter_7.0.0-1_all.deb ...
  Unpacking libvirt-daemon-config-nwfilter (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../05-libvirt-daemon-config-network_7.0.0-1_all.deb ...
  Unpacking libvirt-daemon-config-network (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../06-libvirt-daemon-system_7.0.0-1_amd64.deb ...
  Unpacking libvirt-daemon-system (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../07-libvirt-daemon-driver-qemu_7.0.0-1_amd64.deb ...
  Unpacking libvirt-daemon-driver-qemu (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../08-libvirt-clients_7.0.0-1_amd64.deb ...
  Unpacking libvirt-clients (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../09-libvirt0_7.0.0-1_amd64.deb ...
  Unpacking libvirt0:amd64 (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../10-libvirt-daemon-driver-xen_7.0.0-1_amd64.deb ...
  Unpacking libvirt-daemon-driver-xen (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../11-libvirt-daemon-driver-vbox_7.0.0-1_amd64.deb ...
  Unpacking libvirt-daemon-driver-vbox (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack 
.../12-libvirt-daemon-driver-storage-zfs_7.0.0-1_amd64.deb ...
  Unpacking libvirt-daemon-driver-storage-zfs (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack 
.../13-libvirt-daemon-driver-storage-rbd_7.0.0-1_amd64.deb ...
  Unpacking libvirt-daemon-driver-storage-rbd (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack 
.../14-libvirt-daemon-driver-storage-gluster_7.0.0-1_amd64.deb ...
  Unpacking libvirt-daemon-driver-storage-gluster (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../15-libvirt-daemon_7.0.0-1_amd64.deb ...
  Unpacking libvirt-daemon (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../16-libvirt-daemon-driver-lxc_7.0.0-1_amd64.deb ...
  Unpacking libvirt-daemon-driver-lxc (7.0.0-1) over (6.9.0-4) ...
  Preparing to unpack .../17-libvirt-daemon-system-systemd_7.0.0-1_all.deb ...
  Unpacking libvirt-daemon-system-systemd (7.0.0-1) over (6.9.0-4) ...
  Setting up libvirt-daemon-config-network (7.0.0-1) ...
  Setting up libvirt-daemon-system-systemd (7.0.0-1) ...
  Setting up libvirt0:amd64 (7.0.0-1) ...
  Setting up libvirt-daemon-config-nwfilter (7.0.0-1) ...
  Setting up libvirt-clients (7.0.0-1) ...
  Setting up libvirt-dev:amd64 (7.0.0-1) ...
  Setting up libvirt-sanlock (7.0.0-1) ...
  Setting up libnss-libvirt:amd64 (7.0.0-1) ...
  Setting up libvirt-daemon-driver-qemu (7.0.0-1) ...
  Setting up libvirt-daemon (7.0.0-1) ...
  Setting up libvirt-daemon-driver-vbox (7.0.0-1) ...
  Setting up libvirt-daemon-driver-storage-rbd (7.0.0-1) ...
  Setting up libvirt-daemon-driver-lxc (7.0.0-1) ...
  Setting up libvirt-login-shell (7.0.0-1) ...
  Setting up libvirt-daemon-driver-storage-gluster (7.0.0-1) ...
  Setting up libvirt-daemon-driver-xen (7.0.0-1) ...
  Setting up libvirt-daemon-driver-storage-zfs (7.0.0-1) ...
  Setting up libvirt-daemon-system (7.0.0-1) ...
  Installing new version of config file 
/etc/apparmor.d/abstractions/libvirt-lxc ...
  Installing new version of config file 
/etc/apparmor.d/abstractions/libvirt-qemu ...
  Installing new version of config file /etc/default/libvirt-guests ...
  Installing new version of config file /etc/libvirt/qemu.conf ...
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Processing triggers for man-db (2.9.3-2) ...
  Processing triggers for libc-bin (2.31-9) ...
  Log ended: 2021-01-31  18:20:48

  Log started: 2021-01-31  18:20:49
  (Reading database ... 87071 files and directories currently installed.)
  Preparing to unpack .../libvirt-wireshark_7.0.0-1_amd64.deb ...
  Unpacking libvirt-wireshark (7.0.0-1) over (6.9.0-4) ...
  Setting up libvirt-wireshark (7.0.0-1) ...
  Log ended: 2021-01-31  18:20:49

  Log started: 2021-01-31  18:20:49
  (Reading database ... 87071 files and directories currently 

Processed: Re: Bug#981461: ser2net: unable to start, undefined symbol: gensio_alloc_mdns

[Debian Bug Tracking System]

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

> severity #981461 important
Bug #981461 [ser2net] ser2net: unable to start, undefined symbol: 
gensio_alloc_mdns
Severity set to 'important' from 'grave'
> # works for me
> tags 981461 unreproducible moreinfo
Bug #981461 [ser2net] ser2net: unable to start, undefined symbol: 
gensio_alloc_mdns
Added tag(s) moreinfo and unreproducible.
> thanks
Stopping processing here.

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

Bug#981461: ser2net: unable to start, undefined symbol: gensio_alloc_mdns

[Marc Haber]

severity #981461 important
# works for me
tags 981461 unreproducible moreinfo
thanks

Hi,

On Sun, Jan 31, 2021 at 10:46:35PM +0800, Gedalya wrote:
> When attempting to start ser2net I get the message:
> /usr/sbin/ser2net: symbol lookup error: /usr/sbin/ser2net: undefined symbol:
> gensio_alloc_mdns
> This happens when I start it in any way, such as just invoking the
> executable with no parameters, or as:
> /usr/sbin/ser2net -c /etc/ser2net.yaml
> However the parameters -h and -v do work.

thanks for the bug report. I have tried the amd64 packages from the
autobuilder once more, and ser2net starts up just fine. Additionally,
objdump -T /usr/lib/x86_64-linux-gnu/libgensio.so.0.0.0 shows that
gensio_alloc_mdns is in the library.

Can you please check the output of ldd /usr/bin/ser2net and verify that
the libgensio.so.0 library is actually pulled from
/usr/lib/x86_64-linux-gnu/libgensio.so.0 and whether this is actually
the file installed from libgensio0 2.2.3-1?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#975963: marked as done (bmake: /usr/share/mk is now a symlink, upgrades from non-symlinks are broken)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 17:35:16 +
with message-id 
and subject line Bug#975963: fixed in bmake 20200710-6
has caused the Debian Bug report #975963,
regarding bmake: /usr/share/mk is now a symlink, upgrades from non-symlinks are 
broken
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.)


-- 
975963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bmake
Version: 20200710-5
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Apparently, upgrading from non-symlink /usr/share/mk leaves an empty
directory in place, leading to completely non-functional bmake.

-BEGIN PGP SIGNATURE-

iQFIBAEBCAAyFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl/A494UHGFuZHJld3No
QGRlYmlhbi5vcmcACgkQXkCM2RzYOdJZ1Af8CiUFzxpUpMfOElYem12ok/9g46oo
Z/ZZXXJQp7Kli8ljW2uzyoRA+q9fjFRvrkeftzhP7lji5iyH54dsLLNn0taS4ytJ
UAI4O3s/UId5zYWDjBT4JXq+UUUIkAjy9wD8Ezr+KanJGDTUTU6SKfEEXCxFXeba
xDo/FMt1EDewF9LXh/pHPygVd3HV8ABHRaMvL4QV71D8Xk+1s4I8XaXebMEvZ1P5
e7lW+t/o9dn1ngM4XBDRjFWhWkExAVPu88DZLYCjNesgORDZjvzrXmEAbLGm3w1b
/lPRS+HXyIHgTPN92LBDmUSgQ4n/dwLKO3pJ/tXL+O4mbpgeJCshGf/Tsw==
=f6Ut
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: bmake
Source-Version: 20200710-6
Done: Andrej Shadura 

We believe that the bug you reported is fixed in the latest version of
bmake, 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 975...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated bmake 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: Sun, 31 Jan 2021 17:07:18 +0100
Source: bmake
Architecture: source
Version: 20200710-6
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 823185 906330 966824 975963
Changes:
 bmake (20200710-6) unstable; urgency=medium
 .
   * Move the NetBSD mk files to the new location (Closes: #975963).
   * Ship bmake makefiles as the default (Closes: #823185).
   * Provide a wrapper script for pmake (Closes: #966824).
   * Parse the bmake output in exists_make_target (Closes: #906330).
   * Provide a debhelper wrapper for pmake.
   * Detect Makefiles written for pmake and use pmake automatically.
Checksums-Sha1:
 1eca0b75d523d6fdfb1fdae468a1b32c691bcf4b 1339 bmake_20200710-6.dsc
 a53d7cc7a908d7e12b98cbd4154ca6f7fdcf1ee0 36604 bmake_20200710-6.debian.tar.xz
Checksums-Sha256:
 e13a5aa42391631e62df01a7c3191bcc6871fa88bc0e1ba219092b76cb2a67f4 1339 
bmake_20200710-6.dsc
 5979ea175426fc162aca7e91b9472cc88ed7307e33a590d0f8b53f30d6047f19 36604 
bmake_20200710-6.debian.tar.xz
Files:
 814eafad6176cf4d2386f724a506cb68 1339 devel optional bmake_20200710-6.dsc
 569bd4e6f271a8744bac27ee4f5b9c51 36604 devel optional 
bmake_20200710-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCYBbpGAAKCRDoRGtKyMdy
YWk5AP9P8E2iJKCiIX8VwmHN4aJKXyHsRTv7L4ZyF86jYLRBIAEAy8VKH24QqUkO
/CqUgp7d8bhLXSTiYHXyZl5lynkwDQI=
=M2dG
-END PGP SIGNATURE End Message ---

Bug#978364: apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side of an entry is empty)

[Nilesh Patra]

Hi Tino,

On Tue, 5 Jan 2021 01:13:56 +0100 Tino Didriksen  wrote:
> apertium-ukr should be removed from Debian. The pair that needed it has
> been upgraded to bundle the required version instead:

If you agree, can I retitle and reassign to file in a removal bug for 
apertium-ukr, then?
Also, I do not see apertium-rus-ukr at either the archive or the tracker - did 
this not get uploaded, yet?

Nilesh

Bug#979640: marked as done (src:adv-17v35x: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 17:04:29 +
with message-id 
and subject line Bug#979640: fixed in adv-17v35x 5.0.6.0-1
has caused the Debian Bug report #979640,
regarding src:adv-17v35x: invalid maintainer address
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.)


-- 
979640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adv-17v35x
Version: 5.0.3.0-2
Severity: serious
Tags: bullseye sid
X-Debbugs-Cc: Alexander Gerasiov , Holger Levsen 


The maintainer address is invalid, see below.

Ansgar

 Start of forwarded message 
From: Mail Delivery System 
Subject: Mail delivery failed: returning message to sender
Date: Sat, 09 Jan 2021 16:33:34 +

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  immortalguard...@redlab-i.ru
host mx.redlab-i.ru [195.16.34.155]
SMTP error from remote mail server after RCPT 
TO::
550 5.1.1 : Recipient address rejected:
User unknown in local recipient table
Reporting-MTA: dns; muffat.debian.org

Action: failed
Final-Recipient: rfc822;immortalguardian@redlab-i.ru
Status: 5.0.0
Remote-MTA: dns; mx.redlab-i.ru
Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in local recipient table
--- End Message ---
--- Begin Message ---
Source: adv-17v35x
Source-Version: 5.0.6.0-1
Done: Alexander GQ Gerasiov 

We believe that the bug you reported is fixed in the latest version of
adv-17v35x, 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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander GQ Gerasiov  (supplier of updated adv-17v35x 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: Sun, 31 Jan 2021 19:31:23 +0300
Source: adv-17v35x
Architecture: source
Version: 5.0.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Alexander GQ Gerasiov 
Closes: 979640
Changes:
 adv-17v35x (5.0.6.0-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Use secure copyright file specification URI.
   * Use secure URI in Homepage field.
   * Bump debhelper from deprecated 9 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Use canonical URL in Vcs-Git.
 .
   [ Alexander Gerasiov ]
   * New upstream version 5.0.6.0
   * d/copyright: Update copyright entries.
   * Remove 0001-Update-for-timer-api-changes-in-Linux-4.15.patch. Fixed 
upstream.
   * d/control: Orphan the package (Closes: #979640).
   * d/control: Fix description (add new adapters).
   * d/control: Move package to salsa.
Checksums-Sha1:
 6915db5dc9df0e2f14dab5078f8d2a406730ebcd 1549 adv-17v35x_5.0.6.0-1.dsc
 8b6c8b58bde75d2611dead9b27ba1b2084c7d9f6 22087 adv-17v35x_5.0.6.0.orig.tar.gz
 f5c2d68553887a13ac97fb84dc7ea8229117a61d 2436 
adv-17v35x_5.0.6.0-1.debian.tar.xz
 dfbbaaa11e7978409e0769119d5b98cf2ffa9b77 5564 
adv-17v35x_5.0.6.0-1_source.buildinfo
Checksums-Sha256:
 85948110bd317e3896bc6f2d19947d08a398bd15ae2a85e9601e0f48b9c7daa8 1549 
adv-17v35x_5.0.6.0-1.dsc
 0993dd30fa98553a820d67a7047c3b6bf440b8d1d579e52b39a5e45a9a6aa48e 22087 
adv-17v35x_5.0.6.0.orig.tar.gz
 3fbddc9432fe57f960d87623089b57f1f4594386abc2e58dc1ee478c3ab17ba6 2436 
adv-17v35x_5.0.6.0-1.debian.tar.xz
 323c8ff864fe443e900182775577007f9d6d25e8ba40646f3e31c92e9e4c61df 5564 
adv-17v35x_5.0.6.0-1_source.buildinfo
Files:
 0a4b097896780a9bef1b72fdaeb6e3b8 1549 kernel optional adv-17v35x_5.0.6.0-1.dsc
 5bde157d390caad0762c34ab59661cb2 22087 kernel optional 
adv-17v35x_5.0.6.0.orig.tar.gz
 e889ed9ef745ef208cddbb39ee947760 2436 kernel optional 
adv-17v35x_5.0.6.0-1.debian.tar.xz
 892ba3199395b30ee1933d09265eff39 5564 kernel optional 
adv-17v35x_5.0.6.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFCBAEBCgAsFiEEBLWdkN98wqvNSbrqyofp6CqsM/EFAmAW3TEOHGdxQGRlYmlh
bi5vcmcACgkQyofp6CqsM/HDsAf/SI7twHcRlrs/k8sbiFUqoQl1GIiuF1CJ7VYt

Bug#979841: rdflib: autopkgtest failure: cannot create directory ‘build/py3_testing’

[s3v]

Dear Maintainer,

after recent upload of rdflib/5.0.0-1, tests fail with
this message:

(Reading database ... 18244 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [12:41:57]: test python3: [---
/tmp/autopkgtest.vpiWsK/build.W6L/src/debian/tests/python3: 8: 
./run_tests_py3.sh: not found
autopkgtest [12:41:57]: test python3: ---]
autopkgtest [12:41:57]: test python3:  - - - - - - - - - - results - - - - - - 
- - - -
python3  FAIL non-zero exit status 127
autopkgtest [12:41:57]:  summary
python3  FAIL non-zero exit status 127

There is no "run_tests_py3.sh" in package directory, just "run_tests.py".

Kind Regards

Processed: 936593

[Debian Bug Tracking System]

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

> tags 936593 - wontfix
Bug #936593 [src:geda-gaf] geda-gaf: Python2 removal in sid/bullseye
Bug #966736 [src:geda-gaf] geda-gaf: Unversioned Python removal in sid/bullseye
Removed tag(s) wontfix.
Removed tag(s) wontfix.
> user debian-pyt...@lists.debian.org
Setting user to debian-pyt...@lists.debian.org (was rl...@hedmen.org).
> usertags 936593 + py2keep
Usertags were: py2removal.
Usertags are now: py2keep py2removal.
> thanks
Stopping processing here.

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

Bug#980071: gnome-shell: Using suspend in the gnome-shell power off/log out menu does log out and suspend in the wrong order

[Simon McVittie]

On Thu, 14 Jan 2021 at 20:03:37 +, A Ozbay wrote:
> I looked through journalctl output and saw this which looked out of ordinary:
> Jan 13 22:59:29 snorlax gnome-shell[2475]: JS ERROR: Error getting systemd 
> inhibitor: Gio.IOErrorEnum: 
> GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation 
> inhibition has been requested for is already running
>
> _promisify/proto[asyncFunc]/### Promise created here: ###
>
> inhibit@resource:///org/gnome/shell/misc/loginManager.js:196:35
>
> _syncInhibitor@resource:///org/gnome/shell/ui/screenShield.js:203:32
>
> _setActive@resource:///org/gnome/shell/ui/screenShield.js:157:14
>
> _completeDeactivate@resource:///org/gnome/shell/ui/screenShield.js:565:14
>
> onComplete@resource:///org/gnome/shell/ui/screenShield.js:542:36
>
> _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:84:13
>
> _easeActor/<@resource:///org/gnome/shell/ui/environment.js:167:64

That looks likely to be part of the problem you are reporting. GNOME
Shell and systemd-logind are having this conversation:

 Please don't suspend until I tell you I'm ready, because I need to
lock the screen first
 Sorry, you're too late - suspend is already in progress

However, that is probably not the whole story. I'd need to see more of
the log to say more.

Would you be able to share a log with this bug's address, starting from
around the time you started the process of suspending? You can censor
parts that you consider to be private as long as you make it obvious
where you have done so (e.g. replacing details with REDACTED).

Or you could send a log to me privately, but I'm dealing with several
high-priority things at the moment and my time is limited, so I can't
guarantee to get to this any time soon, and it might be better to put the
information where other GNOME team members have an opportunity to help.

> I am not sure if this would crash the shell.

Probably not, but I can't tell from just this one message. If the shell
crashes, you should see other messages, for instance gnome-session
reporting that a required component (the shell) has failed.

> Other than that, I also noticed that this happens only on Xorg, and
> not on Wayland.

That's probably significant information, and will make it more likely
that a GNOME team member can reproduce the bug - I suspect we're all
using GNOME in its recommended Wayland mode.

Thanks,
smcv

Bug#936593: (no subject)

[Roland Lutz]

Control: tags -1 - wontfix
Control: user debian-pyt...@lists.debian.org , usertags -1 + py2keep

Hi,

since migrating gEDA/gaf to Python 3 is a non-trivial effort and the 
package has many users (popcon > 1000), I'm adding the "py2keep" user tag 
as requested.


I fixed the use of unversioned python packages and interpreters in the 
package (see bug 965098 for details):


  https://github.com/rlutz/geda-gaf-debian

Please consider uploading these changes if you have the rights to do so.

Roland

Bug#981435: libvirt: stops on upgrade: internal error: Failed to load module 'libvirt_driver_qemu.so': libvirt.so.0: version `LIBVIRT_PRIVATE_6.9.0' not found (required by libvirt_driver_qemu.so)

[Andrea Bolognani]

On Sun, Jan 31, 2021 at 11:04:13PM +0800, Paul Wise wrote:
> On Sun, 2021-01-31 at 15:34 +0100, Andrea Bolognani wrote:
> > As I've never used unattended-upgrades myself, I'm not familiar with
> > it. Is there any chance you could provide some quick tips on how to
> > set up a reproducer environment? Specifically how to set up the same
> > upgrade strategy you're using, and whether it's possible to manually
> > trigger an unattended-upgrades run? That would help a lot!
> 
> You can probably also reproduce it without unattended-upgrades by just
> upgrading libvirt-daemon itself using apt but with unattended-upgrades
> the key is to enable the minimal steps option, but do this overall:
> 
> Install a Debian system that has the old libvirt using the Debian
> wayback machine (snapshot.debian.org), install unattended-upgrades and
> add something like the following in /etc/apt/apt.conf.d/99override-u-u.conf
> and then run this command: systemctl start apt-daily{,-upgrade}.service
> 
>    APT::Periodic::Update-Package-Lists "always";
>    APT::Periodic::Download-Upgradeable-Packages "always";
>    APT::Periodic::AutocleanInterval "always";
>    APT::Periodic::Unattended-Upgrade "always";
>    Unattended-Upgrade::Origins-Pattern { "origin=Debian"; };
>    Unattended-Upgrade::MinimalSteps "true";
>    Unattended-Upgrade::Mail "root";
>    Unattended-Upgrade::Remove-Unused-Dependencies "true";
>    Unattended-Upgrade::Automatic-Reboot "false";
>    // Temporary options for debugging
>    //Unattended-Upgrade::Verbose "true";
>    //Unattended-Upgrade::Debug "true";

Thanks, I'll try this.

> > As for the issue itself, I think it's caused by some of the
> > dependencies not being strict enough
> 
> I'm not sure but I think the issue is caused by the libvirt0 symbol
> file generating incorrect dependencies for the private symbols,
> probably it should be much more restrictive for those.
> 
> The missing symbols are pretty concerning, those look like broken ABI?

The exact error is

  Failed to load module 
'/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_qemu.so': 
/usr/lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_PRIVATE_6.9.0' not 
found (required by 
/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_qemu.so)

Note how it's talking about LIBVIRT_PRIVATE_x.y.z rather than
LIBVIRT_x.y.z: the latter contains the public API, while the former
is used for internal symbols that are not exposed publicly and are
only needed by other libvirt components, such as utility functions
that are provided by libvirt.so for use in the various drivers.

This is part of the reason why we want upgrades to happen in
lockstep: for any given version of libvirt, its various components
are really only meant to work with other components when these come
from the very same build.

I've opened

  https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/98

with the proposed patch, and I'm going to use the information you
provided above to give it some testing now.

-- 
Andrea Bolognani 
Resistance is futile, you will be garbage collected.


signature.asc
Description: PGP signature

Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring

[Simon McVittie]

On Sun, 31 Jan 2021 at 11:45:08 +, Simon McVittie wrote:
> I suspect I know what change triggered this: it'll be the security hardening
> imported from the upstream glib-2-66 branch in 2.66.4-2. However, I couldn't
> reproduce this failure to unlock in a test VM.

I've prepared several sets of packages that partially revert that change,
to test this theory. They're all available from
 as amd64 and i386 packages,
signed by my key in the Debian keyring.

The set versioned as "2.66.4-3+revert981420targeted" revert only the change
that is most likely to be the cause of this regression. They also add new
warnings that are printed whenever it matters. Please could you try those
and report back whether it is successful?

Whether they solve it or not, please also report what messages are logged
in the systemd journal while you are logging in. I would expect to see
a message something like this:

Suppressing use of DBUS_SESSION_BUS_ADDRESS because setuid: euid 0 != ruid 
1000

or like this:

Not suppressing use of DBUS_SESSION_BUS_ADDRESS because not setuid, even 
though AT_SECURE

If that set doesn't solve the regression, the next set to try is the one
versioned as "2.66.4-3+revert981420dbus".

Finally, if that doesn't solve it either, "2.66.4-3+revert981420entirely"
might.

Whatever the results of this, I'll still need to know whether your
gnome-keyring-daemon is setuid and/or setcap (see previous messages).

Thanks,
smcv

Processed: please upload latest version which uses guile-2.2

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 geda-gaf: please upload latest version which uses guile-2.2
Bug #885195 [src:geda-gaf] geda-gaf: please migrate to guile-2.2
Changed Bug title to 'geda-gaf: please upload latest version which uses 
guile-2.2' from 'geda-gaf: please migrate to guile-2.2'.
> fixed -1 geda-gaf/1:1.10.2-0.1
Bug #885195 [src:geda-gaf] geda-gaf: please upload latest version which uses 
guile-2.2
The source geda-gaf and version 1:1.10.2-0.1 do not appear to match any binary 
packages
Marked as fixed in versions geda-gaf/1:1.10.2-0.1.

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

Bug#885195: please upload latest version which uses guile-2.2

[Roland Lutz]

Control: retitle -1 geda-gaf: please upload latest version which uses guile-2.2
Control: fixed -1 geda-gaf/1:1.10.2-0.1

Hi,

gEDA/gaf has migrated to Guile 2.2 in version 1.10.2.  Since Bdale isn't 
interested in packaging gEDA/gaf any more and Kai-Martin is currently 
unavailable, I stepped in and packaged gEDA/gaf 1.10.2 for Debian (see bug 
965098 for details):


  https://github.com/rlutz/geda-gaf-debian

Since my original post didn't get any attention, I'm forwarding the issue 
here.  Please consider uploading these changes if you have the rights to 
do so.


Roland

Bug#981435: libvirt: stops on upgrade: internal error: Failed to load module 'libvirt_driver_qemu.so': libvirt.so.0: version `LIBVIRT_PRIVATE_6.9.0' not found (required by libvirt_driver_qemu.so)

[Paul Wise]

On Sun, 2021-01-31 at 15:34 +0100, Andrea Bolognani wrote:

> As I've never used unattended-upgrades myself, I'm not familiar with
> it. Is there any chance you could provide some quick tips on how to
> set up a reproducer environment? Specifically how to set up the same
> upgrade strategy you're using, and whether it's possible to manually
> trigger an unattended-upgrades run? That would help a lot!

You can probably also reproduce it without unattended-upgrades by just
upgrading libvirt-daemon itself using apt but with unattended-upgrades
the key is to enable the minimal steps option, but do this overall:

Install a Debian system that has the old libvirt using the Debian
wayback machine (snapshot.debian.org), install unattended-upgrades and
add something like the following in /etc/apt/apt.conf.d/99override-u-u.conf
and then run this command: systemctl start apt-daily{,-upgrade}.service

   APT::Periodic::Update-Package-Lists "always";
   APT::Periodic::Download-Upgradeable-Packages "always";
   APT::Periodic::AutocleanInterval "always";
   APT::Periodic::Unattended-Upgrade "always";
   Unattended-Upgrade::Origins-Pattern { "origin=Debian"; };
   Unattended-Upgrade::MinimalSteps "true";
   Unattended-Upgrade::Mail "root";
   Unattended-Upgrade::Remove-Unused-Dependencies "true";
   Unattended-Upgrade::Automatic-Reboot "false";
   // Temporary options for debugging
   //Unattended-Upgrade::Verbose "true";
   //Unattended-Upgrade::Debug "true";

> As for the issue itself, I think it's caused by some of the
> dependencies not being strict enough

I'm not sure but I think the issue is caused by the libvirt0 symbol
file generating incorrect dependencies for the private symbols,
probably it should be much more restrictive for those.

The missing symbols are pretty concerning, those look like broken ABI?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed: affects 981428

[Debian Bug Tracking System]

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

> affects 981428 yubikey-manager
Bug #981428 [python3-fido2] python3-fido2: Version 0.9 breaks yubikey-manager
Added indication that 981428 affects yubikey-manager
> thanks
Stopping processing here.

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

Bug#981435: libvirt: stops on upgrade: internal error: Failed to load module 'libvirt_driver_qemu.so': libvirt.so.0: version `LIBVIRT_PRIVATE_6.9.0' not found (required by libvirt_driver_qemu.so)

[Andrea Bolognani]

On Sun, Jan 31, 2021 at 05:43:43PM +0800, Paul Wise wrote:
> Source: libvirt
> Version: 7.0.0-1
> Severity: serious
> 
> There is some sort of missing dependency that means that the daemon is
> stopped during certain kinds of upgrades. I use unattended-upgrades in
> the minimal-steps mode rather than upgrading all packages at once. As a
> result the order of upgrades seems to cause a failure to restart the
> libvirt systemd service. It looks like the libvirt-daemon-* packages
> need to be upgraded before the libvirt-daemon-system package.
> 
> I have included below the apt and systemd logs for this upgrade.
> 
> Log started: 2021-01-31  17:07:53
> apt-listchanges: Reading changelogs...
> apt-listchanges: Mailing root: apt-listchanges: changelogs for chianamo
> Preconfiguring packages ...
> apt-listchanges: Reading changelogs...
> Preconfiguring packages ...
> Preparing to unpack .../libvirt0-dbgsym_7.0.0-1_amd64.deb ...
> Unpacking libvirt0-dbgsym:amd64 (7.0.0-1) over (6.9.0-4) ...
> Preparing to unpack .../libvirt-daemon-system_7.0.0-1_amd64.deb ...
> Unpacking libvirt-daemon-system (7.0.0-1) over (6.9.0-4) ...
> Preparing to unpack .../libvirt-daemon_7.0.0-1_amd64.deb ...
> Unpacking libvirt-daemon (7.0.0-1) over (6.9.0-4) ...
> Preparing to unpack .../libvirt-clients_7.0.0-1_amd64.deb ...
> Unpacking libvirt-clients (7.0.0-1) over (6.9.0-4) ...
> Preparing to unpack .../libvirt0_7.0.0-1_amd64.deb ...
> Unpacking libvirt0:amd64 (7.0.0-1) over (6.9.0-4) ...
> Setting up libvirt0:amd64 (7.0.0-1) ...
> Setting up libvirt-daemon (7.0.0-1) ...
> Setting up libvirt-clients (7.0.0-1) ...
> Setting up libvirt0-dbgsym:amd64 (7.0.0-1) ...
> Setting up libvirt-daemon-system (7.0.0-1) ...
> Installing new version of config file 
> /etc/apparmor.d/abstractions/libvirt-lxc ...
> Installing new version of config file 
> /etc/apparmor.d/abstractions/libvirt-qemu ...
> Installing new version of config file /etc/default/libvirt-guests ...
> Installing new version of config file /etc/libvirt/qemu.conf ...
> Job for libvirtd.service failed because the control process exited with error 
> code.
> See "systemctl status libvirtd.service" and "journalctl -xe" for details.
> virtlockd.service is a disabled or a static unit, not starting it.
> virtlogd.service is a disabled or a static unit, not starting it.
> Log ended: 2021-01-31  17:09:05
> 
> Log started: 2021-01-31  17:13:02
> apt-listchanges: Reading changelogs...
> apt-listchanges: Reading changelogs...
> Preparing to unpack .../libvirt-daemon-config-nwfilter_7.0.0-1_all.deb ...
> Unpacking libvirt-daemon-config-nwfilter (7.0.0-1) over (6.9.0-4) ...
> Setting up libvirt-daemon-config-nwfilter (7.0.0-1) ...
> Log ended: 2021-01-31  17:13:24
> 
> Log started: 2021-01-31  17:15:12
> apt-listchanges: Reading changelogs...
> apt-listchanges: Reading changelogs...
> Preparing to unpack .../libvirt-daemon-config-network_7.0.0-1_all.deb ...
> Unpacking libvirt-daemon-config-network (7.0.0-1) over (6.9.0-4) ...
> Setting up libvirt-daemon-config-network (7.0.0-1) ...
> Log ended: 2021-01-31  17:15:32
> 
> Log started: 2021-01-31  17:15:33
> apt-listchanges: Reading changelogs...
> apt-listchanges: Reading changelogs...
> Preparing to unpack .../libvirt-daemon-system-systemd_7.0.0-1_all.deb ...
> Unpacking libvirt-daemon-system-systemd (7.0.0-1) over (6.9.0-4) ...
> Setting up libvirt-daemon-system-systemd (7.0.0-1) ...
> Log ended: 2021-01-31  17:15:53
> 
> Log started: 2021-01-31  17:15:54
> apt-listchanges: Reading changelogs...
> apt-listchanges: Reading changelogs...
> Preparing to unpack .../libvirt-daemon-driver-qemu_7.0.0-1_amd64.deb ...
> Unpacking libvirt-daemon-driver-qemu (7.0.0-1) over (6.9.0-4) ...
> Setting up libvirt-daemon-driver-qemu (7.0.0-1) ...
> Processing triggers for man-db (2.9.3-2) ...
> Log ended: 2021-01-31  17:16:22
> 
> Jan 31 17:08:34 kernel: audit: type=1400 audit(1612084114.263:107): 
> apparmor="STATUS" operation="profile_replace" info="same as current profile, 
> skipping" profile="unconfined" name="libvirtd" pid=1318234 
> comm="apparmor_parser"
> Jan 31 17:08:34 kernel: audit: type=1400 audit(1612084114.263:108): 
> apparmor="STATUS" operation="profile_replace" info="same as current profile, 
> skipping" profile="unconfined" name="libvirtd//qemu_bridge_helper" 
> pid=1318234 comm="apparmor_parser"
> Jan 31 17:08:34 audit[1318234]: AVC apparmor="STATUS" 
> operation="profile_replace" info="same as current profile, skipping" 
> profile="unconfined" name="libvirtd" pid=1318234 comm="apparmor_parser"
> Jan 31 17:08:34 audit[1318234]: AVC apparmor="STATUS" 
> operation="profile_replace" info="same as current profile, skipping" 
> profile="unconfined" name="libvirtd//qemu_bridge_helper" pid=1318234 
> comm="apparmor_parser"
> Jan 31 17:08:34 systemd[1]: Reloading.
> Jan 31 17:08:36 systemd[1]: Stopping Virtualization daemon...
> Jan 31 17:08:36 systemd[1]: libvirtd.service: Succeeded.
> Jan 31 17:08:36 systemd[1]: Stopped Virtualization daemon.
> Jan 

Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x

[Dirk Eddelbuettel]

On 31 January 2021 at 09:20, Graham Inggs wrote:
| Control: reopen -1
| 
| Hi Dirk
| 
| Paul's test results showed that the run-unit-test autopkgtest still
| fails with the same errors (
| Error: gradient function must return a numeric vector of length...) as
| in my original report.
|
| 
| The "Package version inconsistency detected" warning is now gone (due
| to #980902).
| 
| You can now see the same result on ci.debian.net [1] in the test run
| at 2021-01-31 02:58:21 UTC.

¯\_(ツ)_/¯

When I look at the log I only see as relevant this tail part at the end:

  autopkgtest [21:58:17]: test pkg-r-autopkgtest: ---]
  pkg-r-autopkgtestPASS
  autopkgtest [21:58:17]: test pkg-r-autopkgtest:  - - - - - - - - - - results 
- - - - - - - - - -
  autopkgtest [21:58:17]:  summary
  run-unit-testFAIL non-zero exit status 1
  pkg-r-autopkgtestPASS

which shows no influence of Matrix. Matrix is a core R package (part of the
"recommended" set) and has been there since forever. This is a bug in
glmmTMB.  All the 'gradient function must ...' errors are from its tests and
points to me to a recent change in R (where boolean comparisons can now check
if the compared vector is corre.  The Matrix change may simply be the trigger.

In any event, all these errors also have backtrace:

-- 1. Error (test-VarCorr.R:11:1): (code run outside of `test_that()`) -
Error: gradient function must return a numeric vector of length 6
Backtrace:
 1. glmmTMB::glmmTMB(distance ~ age + (age | Subject), data = Orthodont) 
test-VarCorr.R:11:0
 2. glmmTMB::fitTMB(TMBStruc)
 4. glmmTMB:::optfun()
 6. base::with.default(...)
 7. [ base::eval(...) ] with 1 more call

No Matrix here.

Can you please talk to glmmTMB?  Their GH seems active
(https://github.com/glmmTMB/glmmTMB/commits/master)

Dirk
 
| Regards
| Graham
| 
| 
| [1] https://ci.debian.net/packages/r/r-cran-glmmtmb/unstable/s390x/

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#981174: marked as done (gcc-10 in testing is broken, cannot build linux kernel)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 13:18:50 +
with message-id 
and subject line Bug#980609: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980609,
regarding gcc-10 in testing is broken, cannot build linux kernel
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.)


-- 
980609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-10
Version: 10.2.1-6

Same issue as reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980609

Kindly inquiring when a fix will be pushed to Debian testing to fix this issue?

# make bzImage
  HOSTCXX scripts/gcc-plugins/latent_entropy_plugin.so
In file included from /usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/tm.h:26,
 from
/usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/backend.h:28,
 from
/usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/gcc-plugin.h:30,
 from scripts/gcc-plugins/gcc-common.h:7,
 from scripts/gcc-plugins/latent_entropy_plugin.c:78:
/usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/config/i386/i386.h:2500:10:
fatal error: common/config/i386/i386-cpuinfo.h: No such file or
directory
 2500 | #include "common/config/i386/i386-cpuinfo.h"
  |  ^~~
compilation terminated.
make[2]: *** [scripts/gcc-plugins/Makefile:47:
scripts/gcc-plugins/latent_entropy_plugin.so] Error 1
make[1]: *** [scripts/Makefile.build:496: scripts/gcc-plugins] Error 2
make: *** [Makefile:1190: scripts] Error 2

Thanks,

Justin.
--- End Message ---
--- Begin Message ---
Source: gcc-10
Source-Version: 10.2.1-16
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
gcc-10, 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 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-10 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: Sun, 31 Jan 2021 12:48:05 +0100
Source: gcc-10
Architecture: source
Version: 10.2.1-16
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 980110 980204 980429 980596 980609 980770
Changes:
 gcc-10 (10.2.1-16) experimental; urgency=medium
 .
   * Update to git 20210130 from the gcc-10 branch.
 - Fix PR ipa/98690, PR tree-optimization/98513, PR tree-optimization/98282,
   PR tree-optimization/94994, PR tree-optimization/95401,
   PR rtl-optimization/97144, PR rtl-optimization/98214,
   PR tree-optimization/98302, PR tree-optimization/98371,
   PR target/89057 (AArch64), PR tree-optimization/98221,
   PR tree-optimization/98117, PR tree-optimization/97623,
   PR tree-optimization/97623, PR ada/98740, PR libgomp/65099,
   PR libstdc++/98605, PR libstdc++/96083, PR libstdc++/65480,
   PR libstdc++/68735, PR tree-optimization/98535,
   PR c++/98790 (closes: #980429, #980596), PR d/98806 (closes: #980204),
   PR fortran/98022, PR fortran/98517, PR fortran/93833, PR lto/85574,
   PR debug/98331, PR target/98853 (AArch64), PR target/98681 (AArch64),
   PR testsuite/98771, PR testsuite/97301, PR tree-optimization/90248,
   PR tree-optimization/98255, PR tree-optimization/97627,
   PR tree-optimization/98766, PR gcov-profile/98739, PR ada/98228,
   PR c++/33661, PR c++/98847, PR sanitizer/95693, PR c++/98672,
   PR c++/98463, PR c++/97474, PR c++/98642, PR c++/63707, PR fortran/86470.
   * Fix parallel linking of cc1gm2.
   * PR sanitizer/98699: Don't enable --as-needed with -fsanitize=* options.
 Closes: #980110.
   * Use --push-state/--pop-state for gold everywhere.
   * Backport prerequisite patch for PR target/97250 (i386: Define __LAHF_SAHF__
 and __MOVBE__ macros, based on ISA flags).
   * Make -march=x86-64-v[234] behave more like other -march= options, taken
 from the trunk.
   * Use the same breaks relations for libgcc-s2 and libgcc-s4 as for
 libgcc-s1. Closes: #980770.
   * Fix up plugin header install, taken from the trunk. Closes: #980609.
   * 

Bug#980629: marked as done (nheko: FTBFS: internal compiler error)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id 
and subject line Bug#980596: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980596,
regarding nheko: FTBFS: internal compiler error
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.)


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

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/build'
> [ 34%] Building CXX object CMakeFiles/nheko.dir/cmake_pch.hxx.gch
> /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
> -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK 
> -DFMT_LOCALE -DFMT_SHARED -DJSON_USE_IMPLICIT_CONVERSIONS=1 
> -DQAPPLICATION_CLASS=QApplication -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
> -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
> -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICKCONTROLS2_LIB -DQT_QUICKWIDGETS_LIB 
> -DQT_QUICK_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DSPDLOG_COMPILED_LIB 
> -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB -I/<>/build 
> -I/<> -I/<>/src -I/<>/includes 
> -I/<>/third_party/blurhash 
> -I/<>/third_party/cpp-httplib-0.5.12 -I/usr/include/tweeny 
> -I/<>/third_party/SingleApplication-3.1.3.1 -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /<>/mtxclient/include -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuickControls2 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuickWidgets -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wall   -Wextra -pipe
>-pedantic   -fsized-deallocation
> -fdiagnostics-color=always  -Wunreachable-code  
> -std=c++17 -O2 -g -DNDEBUG -fPIE -fPIC -pthread -std=gnu++17 -Winvalid-pch -x 
> c++-header -include /<>/build/CMakeFiles/nheko.dir/cmake_pch.hxx 
> -o CMakeFiles/nheko.dir/cmake_pch.hxx.gch -c 
> /<>/build/CMakeFiles/nheko.dir/cmake_pch.hxx.cxx
> [ 35%] Building CXX object CMakeFiles/nheko.dir/src/dialogs/FallbackAuth.cpp.o
> [ 35%] Building CXX object CMakeFiles/nheko.dir/src/dialogs/ImageOverlay.cpp.o
> [ 35%] Building CXX object CMakeFiles/nheko.dir/src/dialogs/CreateRoom.cpp.o
> [ 36%] Building CXX object CMakeFiles/nheko.dir/src/dialogs/InviteUsers.cpp.o
> /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
> -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK 
> -DFMT_LOCALE -DFMT_SHARED -DJSON_USE_IMPLICIT_CONVERSIONS=1 
> -DQAPPLICATION_CLASS=QApplication -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
> -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
> -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICKCONTROLS2_LIB -DQT_QUICKWIDGETS_LIB 
> -DQT_QUICK_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DSPDLOG_COMPILED_LIB 
> -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB -I/<>/build 
> -I/<> -I/<>/src -I/<>/includes 
> -I/<>/third_party/blurhash 
> -I/<>/third_party/cpp-httplib-0.5.12 -I/usr/include/tweeny 
> -I/<>/third_party/SingleApplication-3.1.3.1 -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /<>/mtxclient/include -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
> 

Bug#980609: marked as done (missing i386-cpuinfo.h)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 13:18:50 +
with message-id 
and subject line Bug#980609: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980609,
regarding missing i386-cpuinfo.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.)


-- 
980609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odb
Version: 2.4.0-13
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H   -I'..' 
> -I'..' -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/lib/gcc/x86_64-linux-gnu/10/plugin/include -std=c++0x -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-devirtualize -c -o cxx-lexer.lo cxx-lexer.cxx
> libtool: compile:  g++ -DHAVE_CONFIG_H -I.. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/lib/gcc/x86_64-linux-gnu/10/plugin/include 
> -std=c++0x -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fno-devirtualize 
> -c cxx-lexer.cxx  -fPIC -DPIC -o .libs/cxx-lexer.o
> In file included from /usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/tm.h:26,
>  from 
> /usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/backend.h:28,
>  from 
> /usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/gcc-plugin.h:30,
>  from ../odb/gcc.hxx:48,
>  from cxx-lexer.cxx:5:
> /usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/config/i386/i386.h:2500:10: 
> fatal error: common/config/i386/i386-cpuinfo.h: No such file or directory
>  2500 | #include "common/config/i386/i386-cpuinfo.h"
>   |  ^~~
> compilation terminated.
> make[3]: *** [Makefile:1143: cxx-lexer.lo] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/odb_2.4.0-13_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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: gcc-10
Source-Version: 10.2.1-16
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
gcc-10, 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 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-10 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: Sun, 31 Jan 2021 12:48:05 +0100
Source: gcc-10
Architecture: source
Version: 10.2.1-16
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 980110 980204 980429 980596 980609 980770
Changes:
 gcc-10 (10.2.1-16) experimental; urgency=medium
 .
   * Update to git 20210130 from the gcc-10 branch.
 - Fix PR ipa/98690, PR tree-optimization/98513, PR tree-optimization/98282,
   PR tree-optimization/94994, PR tree-optimization/95401,
   PR rtl-optimization/97144, PR rtl-optimization/98214,
   PR tree-optimization/98302, PR tree-optimization/98371,
   PR target/89057 (AArch64), PR tree-optimization/98221,
   PR tree-optimization/98117, PR tree-optimization/97623,
   PR tree-optimization/97623, PR ada/98740, PR libgomp/65099,
   PR libstdc++/98605, PR libstdc++/96083, PR libstdc++/65480,
   PR libstdc++/68735, PR tree-optimization/98535,
   PR c++/98790 (closes: 

Bug#980429: marked as done (g++-10: spurious c++17 mode segmentation fault in append_to_statement_list_1 (tree-iterator.c:65))

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id 
and subject line Bug#980596: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980596,
regarding g++-10: spurious c++17 mode segmentation fault in 
append_to_statement_list_1 (tree-iterator.c:65)
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.)


-- 
980596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: g++-10
Version: 10.2.1-6
Severity: serious

Hi,

while rebuilding src:nheko I noticed an ICE with SEGFAULT.
I've somewhat minimized the testcase with delta (from 3.3 MB to 15 KB).

Build the attached code with

x86_64-linux-gnu-g++-10 -std=c++17 -Wno-return-type -c gcc-10-segfault.C

* it needs the -std=c++17 flag, without it no segfault occurs
* -Wno-return-type suppresses warnings caused by minimizing return statements 
away
* it is a regression from GCC-9, which always accepts the code
* it does not segfault always, but very likely needs less than 5 repetitions
  to result in segfault (out of 1000 test compiles 526 died with a segfault)
* there are two similar backtraces that may happen:

$ x86_64-linux-gnu-g++-10 -std=c++17 -Wno-return-type -c gcc-10-segfault.C
In file included from :
/usr/include/stdc-predef.h: In substitution of 'template std::function::function(_Functor) [with 
_Functor = ;  = ; 
 = ]':
gcc-10-segfault.C:283:12:   required from 'static void 
tweeny::detail::easingresolve::impl(FunctionTuple&, 
tweeny::easing::linearEasing, Fs ...) [with int I = 0; TypeTuple = 
std::array; FunctionTuple = std::tuple >; Fs = {}]'
gcc-10-segfault.C:289:64:   required from 'void 
tweeny::detail::easingfill(EasingCollectionT&, EasingT, 
tweeny::detail::int2type<0>) [with TypeTupleT = std::array; 
EasingCollectionT = std::tuple >; 
EasingT = tweeny::easing::linearEasing]'
gcc-10-segfault.C:297:41:   required from 'void 
tweeny::detail::tweenpoint::via(F) [with F = tweeny::easing::linearEasing; 
Ts = {float}]'
gcc-10-segfault.C:294:5:   required from 
'tweeny::detail::tweenpoint::tweenpoint(Ts ...) [with Ts = {float}]'
gcc-10-segfault.C:141:2:   required from 'static constexpr 
std::_Require::__construct_helper<_Tp, _Args>::type>, 
std::is_constructible<_Tp, _Args ...> > > 
std::allocator_traits<_Alloc>::_S_construct(_Alloc&, _Tp*, _Args&& ...) [with 
_Tp = tweeny::detail::tweenpoint; _Args = {float&}; _Alloc = 
std::allocator >; 
std::_Require::__construct_helper<_Tp, _Args>::type>, 
std::is_constructible<_Tp, _Args ...> > > = void; typename 
std::allocator_traits<_Alloc>::__construct_helper<_Tp, _Args>::type = 
std::integral_constant]'
gcc-10-segfault.C:144:14:   required from 'static decltype 
(std::allocator_traits<_Alloc>::_S_construct(__a, __p, 
(forward<_Args>)(std::allocator_traits<_Alloc>::construct::__args)...)) 
std::allocator_traits<_Alloc>::construct(_Alloc&, _Tp*, _Args&& ...) [with _Tp 
= tweeny::detail::tweenpoint; _Args = {float&}; _Alloc = 
std::allocator >; decltype 
(std::allocator_traits<_Alloc>::_S_construct(__a, __p, 
(forward<_Args>)(std::allocator_traits<_Alloc>::construct::__args)...)) = void]'
gcc-10-segfault.C:224:26:   required from 'std::vector<_Tp, _Alloc>::reference 
std::vector<_Tp, _Alloc>::emplace_back(_Args&& ...) [with _Args = {float&}; _Tp 
= tweeny::detail::tweenpoint; _Alloc = 
std::allocator >; std::vector<_Tp, 
_Alloc>::reference = tweeny::detail::tweenpoint&]'
gcc-10-segfault.C:310:21:   required from 'tweeny::tween& 
tweeny::tween::to(T) [with T = float]'
gcc-10-segfault.C:322:47:   required from here
/usr/include/stdc-predef.h:32:111: internal compiler error: Segmentation fault
   32 |whether the overall intent is to support these features; otherwise,
  | 
  ^
   33 |presume an older compiler has intent to support these features and
  |~
   
0xa65400 crash_signal
../../src/gcc/toplev.c:328
0x7f575b1ddd5f ???
./signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0xf09c3b append_to_statement_list_1
../../src/gcc/tree-iterator.c:65
0xf09c3b append_to_statement_list_force(tree_node*, tree_node**)
../../src/gcc/tree-iterator.c:105
0xf09c3b add_stmt(tree_node*)
../../src/gcc/cp/semantics.c:393
0x13a55c2 synthesize_method(tree_node*)
../../src/gcc/cp/method.c:1585
0x64cece maybe_instantiate_noexcept(tree_node*, int)

Bug#980629: marked as done (nheko: FTBFS: internal compiler error)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id 
and subject line Bug#980429: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980429,
regarding nheko: FTBFS: internal compiler error
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.)


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

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/build'
> [ 34%] Building CXX object CMakeFiles/nheko.dir/cmake_pch.hxx.gch
> /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
> -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK 
> -DFMT_LOCALE -DFMT_SHARED -DJSON_USE_IMPLICIT_CONVERSIONS=1 
> -DQAPPLICATION_CLASS=QApplication -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
> -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
> -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICKCONTROLS2_LIB -DQT_QUICKWIDGETS_LIB 
> -DQT_QUICK_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DSPDLOG_COMPILED_LIB 
> -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB -I/<>/build 
> -I/<> -I/<>/src -I/<>/includes 
> -I/<>/third_party/blurhash 
> -I/<>/third_party/cpp-httplib-0.5.12 -I/usr/include/tweeny 
> -I/<>/third_party/SingleApplication-3.1.3.1 -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /<>/mtxclient/include -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuickControls2 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuickWidgets -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wall   -Wextra -pipe
>-pedantic   -fsized-deallocation
> -fdiagnostics-color=always  -Wunreachable-code  
> -std=c++17 -O2 -g -DNDEBUG -fPIE -fPIC -pthread -std=gnu++17 -Winvalid-pch -x 
> c++-header -include /<>/build/CMakeFiles/nheko.dir/cmake_pch.hxx 
> -o CMakeFiles/nheko.dir/cmake_pch.hxx.gch -c 
> /<>/build/CMakeFiles/nheko.dir/cmake_pch.hxx.cxx
> [ 35%] Building CXX object CMakeFiles/nheko.dir/src/dialogs/FallbackAuth.cpp.o
> [ 35%] Building CXX object CMakeFiles/nheko.dir/src/dialogs/ImageOverlay.cpp.o
> [ 35%] Building CXX object CMakeFiles/nheko.dir/src/dialogs/CreateRoom.cpp.o
> [ 36%] Building CXX object CMakeFiles/nheko.dir/src/dialogs/InviteUsers.cpp.o
> /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
> -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK 
> -DFMT_LOCALE -DFMT_SHARED -DJSON_USE_IMPLICIT_CONVERSIONS=1 
> -DQAPPLICATION_CLASS=QApplication -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
> -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
> -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICKCONTROLS2_LIB -DQT_QUICKWIDGETS_LIB 
> -DQT_QUICK_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DSPDLOG_COMPILED_LIB 
> -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB -I/<>/build 
> -I/<> -I/<>/src -I/<>/includes 
> -I/<>/third_party/blurhash 
> -I/<>/third_party/cpp-httplib-0.5.12 -I/usr/include/tweeny 
> -I/<>/third_party/SingleApplication-3.1.3.1 -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /<>/mtxclient/include -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
> 

Bug#980596: marked as done (mkvtoolnix: FTBFS: src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id 
and subject line Bug#980429: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980429,
regarding mkvtoolnix: FTBFS: 
src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: 
Segmentation fault
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.)


-- 
980429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mkvtoolnix
Version: 52.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> src/merge/reader_detection_and_creation.cpp: In substitution of 
> ‘template 
> std::function(const 
> std::shared_ptr&, const probe_range_info_t&)>& 
> std::function(const 
> std::shared_ptr&, const 
> probe_range_info_t&)>::operator=<_Functor>(std::reference_wrapper<_Tp>) [with 
> _Functor = ]’:
> src/merge/reader_detection_and_creation.cpp:164:54:   required from here
> src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: 
> Segmentation fault
>   164 | type_probe_map[mtx::file_type_e::avc_es]  = 
> _probe;
>   |  
> ^
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See  for instructions.
>CXX src/input/unsupported_types_signature_prober.cpp
>CXX src/input/truehd_ac3_splitting_packet_converter.cpp
>UIC src/mkvtoolnix-gui/forms/util/language_display_widget.ui
>CXX src/mkvtoolnix-gui/util/language_display_widget.cpp
>CXX src/input/teletext_to_srt_packet_converter.cpp
>UIC src/mkvtoolnix-gui/forms/util/language_dialog.ui
>CXX src/mkvtoolnix-gui/util/language_dialog.cpp
> Preprocessed source stored into /tmp/cc0m9mZt.out file, please attach this to 
> your bugreport.
> make[1]: *** [debian/rules:28: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/mkvtoolnix_52.0.0-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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: gcc-10
Source-Version: 10.2.1-16
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
gcc-10, 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 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-10 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: Sun, 31 Jan 2021 12:48:05 +0100
Source: gcc-10
Architecture: source
Version: 10.2.1-16
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 980110 980204 980429 980596 980609 980770
Changes:
 gcc-10 (10.2.1-16) experimental; urgency=medium
 .
   * Update to git 20210130 from the gcc-10 branch.
 - Fix PR ipa/98690, PR tree-optimization/98513, PR tree-optimization/98282,
   PR tree-optimization/94994, PR tree-optimization/95401,
   PR rtl-optimization/97144, PR rtl-optimization/98214,
   PR tree-optimization/98302, PR tree-optimization/98371,
   PR target/89057 (AArch64), PR tree-optimization/98221,
   PR tree-optimization/98117, PR tree-optimization/97623,
   PR tree-optimization/97623, PR ada/98740, PR libgomp/65099,
   

Bug#980596: marked as done (mkvtoolnix: FTBFS: src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id 
and subject line Bug#980596: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980596,
regarding mkvtoolnix: FTBFS: 
src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: 
Segmentation fault
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.)


-- 
980596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mkvtoolnix
Version: 52.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> src/merge/reader_detection_and_creation.cpp: In substitution of 
> ‘template 
> std::function(const 
> std::shared_ptr&, const probe_range_info_t&)>& 
> std::function(const 
> std::shared_ptr&, const 
> probe_range_info_t&)>::operator=<_Functor>(std::reference_wrapper<_Tp>) [with 
> _Functor = ]’:
> src/merge/reader_detection_and_creation.cpp:164:54:   required from here
> src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: 
> Segmentation fault
>   164 | type_probe_map[mtx::file_type_e::avc_es]  = 
> _probe;
>   |  
> ^
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See  for instructions.
>CXX src/input/unsupported_types_signature_prober.cpp
>CXX src/input/truehd_ac3_splitting_packet_converter.cpp
>UIC src/mkvtoolnix-gui/forms/util/language_display_widget.ui
>CXX src/mkvtoolnix-gui/util/language_display_widget.cpp
>CXX src/input/teletext_to_srt_packet_converter.cpp
>UIC src/mkvtoolnix-gui/forms/util/language_dialog.ui
>CXX src/mkvtoolnix-gui/util/language_dialog.cpp
> Preprocessed source stored into /tmp/cc0m9mZt.out file, please attach this to 
> your bugreport.
> make[1]: *** [debian/rules:28: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/mkvtoolnix_52.0.0-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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: gcc-10
Source-Version: 10.2.1-16
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
gcc-10, 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 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-10 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: Sun, 31 Jan 2021 12:48:05 +0100
Source: gcc-10
Architecture: source
Version: 10.2.1-16
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 980110 980204 980429 980596 980609 980770
Changes:
 gcc-10 (10.2.1-16) experimental; urgency=medium
 .
   * Update to git 20210130 from the gcc-10 branch.
 - Fix PR ipa/98690, PR tree-optimization/98513, PR tree-optimization/98282,
   PR tree-optimization/94994, PR tree-optimization/95401,
   PR rtl-optimization/97144, PR rtl-optimization/98214,
   PR tree-optimization/98302, PR tree-optimization/98371,
   PR target/89057 (AArch64), PR tree-optimization/98221,
   PR tree-optimization/98117, PR tree-optimization/97623,
   PR tree-optimization/97623, PR ada/98740, PR libgomp/65099,
   

Bug#980429: marked as done (g++-10: spurious c++17 mode segmentation fault in append_to_statement_list_1 (tree-iterator.c:65))

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id 
and subject line Bug#980429: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980429,
regarding g++-10: spurious c++17 mode segmentation fault in 
append_to_statement_list_1 (tree-iterator.c:65)
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.)


-- 
980429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: g++-10
Version: 10.2.1-6
Severity: serious

Hi,

while rebuilding src:nheko I noticed an ICE with SEGFAULT.
I've somewhat minimized the testcase with delta (from 3.3 MB to 15 KB).

Build the attached code with

x86_64-linux-gnu-g++-10 -std=c++17 -Wno-return-type -c gcc-10-segfault.C

* it needs the -std=c++17 flag, without it no segfault occurs
* -Wno-return-type suppresses warnings caused by minimizing return statements 
away
* it is a regression from GCC-9, which always accepts the code
* it does not segfault always, but very likely needs less than 5 repetitions
  to result in segfault (out of 1000 test compiles 526 died with a segfault)
* there are two similar backtraces that may happen:

$ x86_64-linux-gnu-g++-10 -std=c++17 -Wno-return-type -c gcc-10-segfault.C
In file included from :
/usr/include/stdc-predef.h: In substitution of 'template std::function::function(_Functor) [with 
_Functor = ;  = ; 
 = ]':
gcc-10-segfault.C:283:12:   required from 'static void 
tweeny::detail::easingresolve::impl(FunctionTuple&, 
tweeny::easing::linearEasing, Fs ...) [with int I = 0; TypeTuple = 
std::array; FunctionTuple = std::tuple >; Fs = {}]'
gcc-10-segfault.C:289:64:   required from 'void 
tweeny::detail::easingfill(EasingCollectionT&, EasingT, 
tweeny::detail::int2type<0>) [with TypeTupleT = std::array; 
EasingCollectionT = std::tuple >; 
EasingT = tweeny::easing::linearEasing]'
gcc-10-segfault.C:297:41:   required from 'void 
tweeny::detail::tweenpoint::via(F) [with F = tweeny::easing::linearEasing; 
Ts = {float}]'
gcc-10-segfault.C:294:5:   required from 
'tweeny::detail::tweenpoint::tweenpoint(Ts ...) [with Ts = {float}]'
gcc-10-segfault.C:141:2:   required from 'static constexpr 
std::_Require::__construct_helper<_Tp, _Args>::type>, 
std::is_constructible<_Tp, _Args ...> > > 
std::allocator_traits<_Alloc>::_S_construct(_Alloc&, _Tp*, _Args&& ...) [with 
_Tp = tweeny::detail::tweenpoint; _Args = {float&}; _Alloc = 
std::allocator >; 
std::_Require::__construct_helper<_Tp, _Args>::type>, 
std::is_constructible<_Tp, _Args ...> > > = void; typename 
std::allocator_traits<_Alloc>::__construct_helper<_Tp, _Args>::type = 
std::integral_constant]'
gcc-10-segfault.C:144:14:   required from 'static decltype 
(std::allocator_traits<_Alloc>::_S_construct(__a, __p, 
(forward<_Args>)(std::allocator_traits<_Alloc>::construct::__args)...)) 
std::allocator_traits<_Alloc>::construct(_Alloc&, _Tp*, _Args&& ...) [with _Tp 
= tweeny::detail::tweenpoint; _Args = {float&}; _Alloc = 
std::allocator >; decltype 
(std::allocator_traits<_Alloc>::_S_construct(__a, __p, 
(forward<_Args>)(std::allocator_traits<_Alloc>::construct::__args)...)) = void]'
gcc-10-segfault.C:224:26:   required from 'std::vector<_Tp, _Alloc>::reference 
std::vector<_Tp, _Alloc>::emplace_back(_Args&& ...) [with _Args = {float&}; _Tp 
= tweeny::detail::tweenpoint; _Alloc = 
std::allocator >; std::vector<_Tp, 
_Alloc>::reference = tweeny::detail::tweenpoint&]'
gcc-10-segfault.C:310:21:   required from 'tweeny::tween& 
tweeny::tween::to(T) [with T = float]'
gcc-10-segfault.C:322:47:   required from here
/usr/include/stdc-predef.h:32:111: internal compiler error: Segmentation fault
   32 |whether the overall intent is to support these features; otherwise,
  | 
  ^
   33 |presume an older compiler has intent to support these features and
  |~
   
0xa65400 crash_signal
../../src/gcc/toplev.c:328
0x7f575b1ddd5f ???
./signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0xf09c3b append_to_statement_list_1
../../src/gcc/tree-iterator.c:65
0xf09c3b append_to_statement_list_force(tree_node*, tree_node**)
../../src/gcc/tree-iterator.c:105
0xf09c3b add_stmt(tree_node*)
../../src/gcc/cp/semantics.c:393
0x13a55c2 synthesize_method(tree_node*)
../../src/gcc/cp/method.c:1585
0x64cece maybe_instantiate_noexcept(tree_node*, int)

Processed: found 981439 in 2020.01.19-1

[Debian Bug Tracking System]

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

> found 981439 2020.01.19-1
Bug #981439 [src:liblivemedia] liblivemedia: includes non-free code from RFC 
3550
Marked as found in versions liblivemedia/2020.01.19-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login 
keyring
Severity set to 'serious' from 'important'

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

Bug#980630: marked as done (libvigraimpex: FTBFS: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb3 in position 138922: invalid start byte)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 12:49:28 +
with message-id 
and subject line Bug#980630: fixed in libvigraimpex 1.11.1+dfsg-8
has caused the Debian Bug report #980630,
regarding libvigraimpex: FTBFS: UnicodeDecodeError: 'utf-8' codec can't decode 
byte 0xb3 in position 138922: invalid start byte
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.)


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

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/<>/obj.x86_64-linux-gnu'
> Generating documentation with doxygen 1.9.1
> cd /<>/obj.x86_64-linux-gnu/docsrc && /usr/bin/cmake -E 
> make_directory /<>/doc
> cd /<>/obj.x86_64-linux-gnu/docsrc && /usr/bin/cmake -E 
> make_directory /<>/doc/vigra
> cd /<>/obj.x86_64-linux-gnu/docsrc && /usr/bin/doxygen
> warning: Tag 'COLS_IN_ALPHA_INDEX' at line 718 of file 'Doxyfile' has become 
> obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> warning: Tag 'PERL_PATH' at line 1250 of file 'Doxyfile' has become obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> warning: Tag 'MSCGEN_PATH' at line 1272 of file 'Doxyfile' has become 
> obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> warning: argument 'a4wide' for option PAPER_TYPE is not a valid enum value
> Using the default: a4!
> error: Illegal ALIASES format 'http://www.sgi.com/tech/stl/'. Use 
> "name=value" or "name{n}=value", where n is the number of arguments
> /<>/include/vigra/colorconversions.hxx:187: warning: multiple 
> use of section label '_details' while adding anchor, (first occurrence: 
> /<>/docsrc/index.dxx, line 247)
> /<>/include/vigra/accumulator.hxx:2556: warning: @copybrief or 
> @copydoc target 'DynamicAccumulatorChain::activate(std::string tag)' not found
> /<>/include/vigra/accumulator.hxx:2563: warning: @copybrief or 
> @copydoc target 'DynamicAccumulatorChain::activate()' not found
> /<>/include/vigra/accumulator.hxx:2570: warning: @copybrief or 
> @copydoc target 'DynamicAccumulatorChain::activateAll()' not found
> /<>/include/vigra/accumulator.hxx:2594: warning: @copybrief or 
> @copydoc target 'DynamicAccumulatorChain::activeNames()' not found
> /<>/include/vigra/accumulator.hxx:2604: warning: @copybrief or 
> @copydoc target 'DynamicAccumulatorChain::passesRequired()' not found
> /<>/docsrc/examples.dxx:111: warning: unable to resolve 
> reference to 'resizeImageSplineInterpolation()' for \ref command
> /<>/docsrc/examples.dxx:139: warning: unable to resolve 
> reference to 'differenceOfExponentialEdgeImage()' for \ref command
> /<>/docsrc/examples.dxx:145: warning: unable to resolve 
> reference to 'seededRegionGrowing()' for \ref command
> /<>/docsrc/examples.dxx:150: warning: unable to resolve 
> reference to 'distanceTransform()' for \ref command
> /<>/docsrc/examples.dxx:151: warning: unable to resolve 
> reference to 'seededRegionGrowing()' for \ref command
> /<>/docsrc/examples.dxx:158: warning: unable to resolve 
> reference to 'boundaryTensor()' for \ref command
> /<>/docsrc/examples.dxx:163: warning: unable to resolve 
> reference to 'nonnegativeLeastSquares()' for \ref command
> /<>/docsrc/examples.dxx:164: warning: unable to resolve 
> reference to 'quadraticProgramming()' for \ref command
> /<>/docsrc/credits_changelog.dxx:99: warning: unable to resolve 
> reference to 'parallel_foreach()' for \ref command
> /<>/docsrc/credits_changelog.dxx:111: warning: unable to resolve 
> reference to 'skeletonizeImage()' for \ref command
> /<>/docsrc/credits_changelog.dxx:141: warning: unable to resolve 
> reference to 'gaussianGradientMultiArray()' for \ref command
> /<>/docsrc/credits_changelog.dxx:141: warning: unable to resolve 
> reference to 'hessianOfGaussianMultiArray()' for \ref command
> /<>/docsrc/credits_changelog.dxx:141: warning: unable to resolve 
> reference to 'gaussianDivergenceMultiArray()' for \ref command
> /<>/docsrc/credits_changelog.dxx:141: warning: unable to resolve 
> reference to 'localMinima()' for \ref command
> /<>/docsrc/credits_changelog.dxx:141: warning: unable to resolve 
> 

Bug#980580: marked as done (ruby-ruby2ruby: FTBFS: ERROR: Test "ruby2.7" failed: RuntimeError: unknown arg type nil)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 12:50:03 +
with message-id 
and subject line Bug#980580: fixed in ruby-ruby2ruby 2.4.4-1
has caused the Debian Bug report #980580,
regarding ruby-ruby2ruby: FTBFS: ERROR: Test "ruby2.7" failed: RuntimeError: 
unknown arg type nil
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.)


-- 
980580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-ruby2ruby
Version: 2.4.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> RuntimeError: unknown arg type nil
> 
> /<>/debian/ruby-ruby2ruby/usr/lib/ruby/vendor_ruby/ruby2ruby.rb:138:in
>  `block in process_args'
> 
> /<>/debian/ruby-ruby2ruby/usr/lib/ruby/vendor_ruby/ruby2ruby.rb:121:in
>  `map'
> 
> /<>/debian/ruby-ruby2ruby/usr/lib/ruby/vendor_ruby/ruby2ruby.rb:121:in
>  `process_args'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:269:in `block (2 levels) in 
> process'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:324:in `error_handler'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:268:in `block in process'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:388:in `in_context'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:245:in `process'
> 
> /<>/debian/ruby-ruby2ruby/usr/lib/ruby/vendor_ruby/ruby2ruby.rb:610:in
>  `process_iter'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:269:in `block (2 levels) in 
> process'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:324:in `error_handler'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:268:in `block in process'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:388:in `in_context'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:245:in `process'
> (eval):8:in `test_lambda_args_norm_comma2'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun'
> 
>  77) Error:
> TestRuby2Ruby2#test_stabby_args_0_spacebar_broken__19_20_21_22_23_24_25_26_27:
> UnknownNodeError: Bug! Unknown node-type :lambda to Ruby2Ruby
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:307:in `block in process'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:388:in `in_context'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:245:in `process'
> 
> /<>/debian/ruby-ruby2ruby/usr/lib/ruby/vendor_ruby/ruby2ruby.rb:603:in
>  `process_iter'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:269:in `block (2 levels) in 
> process'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:324:in `error_handler'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:268:in `block in process'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:388:in `in_context'
> /usr/lib/ruby/vendor_ruby/sexp_processor.rb:245:in `process'
> (eval):8:in 
> `test_stabby_args_0_spacebar_broken__19_20_21_22_23_24_25_26_27'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:270:in 

Bug#977057: behave FTBFS with pytest 6

[s3v]

Dear Maintainer,

After applying this patch [1], I was able to
build your package in a sid chroot environment.

Kind Regards

[1] https://github.com/behave/behave/commit/66fcad

Processed: found 914314 in git-buildpackage/0.9.20

[Debian Bug Tracking System]

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

> found 914314 git-buildpackage/0.9.20
Bug #914314 [git-buildpackage] git-buildpackage: import-orig --uscan passes 
--symlink unconditionally
Marked as found in versions git-buildpackage/0.9.20.
> thanks
Stopping processing here.

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

Processed: found 914314 in git-buildpackage/0.9.14

[Debian Bug Tracking System]

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

> found 914314 git-buildpackage/0.9.14
Bug #914314 [git-buildpackage] git-buildpackage: import-orig --uscan passes 
--symlink unconditionally
Marked as found in versions git-buildpackage/0.9.14.
> thanks
Stopping processing here.

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

Processed: [git-buildpackage/master] autopkgtest: Set %_arch

[Debian Bug Tracking System]

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

> tag 980256 pending
Bug #980256 [src:git-buildpackage] git-buildpackage: autopkgtest armhf 
regression: /usr/bin/python: not found
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#980637: git-buildpackage: FTBFS: AttributeError: 'str' object has no attribute 'decode'

[Guido Günther]

Hi,
On Sat, Jan 30, 2021 at 09:13:07PM +0100, Jochen Sprickerhof wrote:
> Control: tags -1 + patch
> 
> Hi Guido,
> 
> * Guido Günther  [2021-01-27 12:08]:
> > Hi,
> > On Wed, Jan 20, 2021 at 09:37:56PM +0100, Lucas Nussbaum wrote:
> > > Source: git-buildpackage
> > > Version: 0.9.21
> > > Severity: serious
> > > Justification: FTBFS on amd64
> > > Tags: bullseye sid ftbfs
> > > Usertags: ftbfs-20210120 ftbfs-bullseye
> > > 
> > > Hi,
> > > 
> > > During a rebuild of all packages in sid, your package failed to build
> > > on amd64.
> > 
> > That is basically the top of the iceberg. Besides lots of places now
> > returning strings instead of bytes rpm became stricter in spec file
> > parsing breaking the test suite (and usage).
> 
> I fixed those in the attached patches.
> Note that I was not able to reproduce #980256 but explicitly tested on armhf
> and added an extra patch, so that bug should be fine.

Awesome. I had fixed the rpm parts here already
https://github.com/agx/git-buildpackage/tree/rpm but went for your
patches so your work is not lost. The reason i wrote 'tip of the
iceberg' is that the component tests need fixing as well - that's the bit
still missing - so tests still fail when the testdata for the component
tests is there (`git submodule update --init --recursive`).

Cheers,
 -- Guido


> IMHO #914314 could be downgraded again, I did not look into fixing it.
> 
> I can do an NMU as well if you are short on time.
> Would be happy to see a new git-buildpackage transition to testing.
> 
> Cheers Jochen

> From bce1d5f6d2e94788aea48731bb0c426e648dd673 Mon Sep 17 00:00:00 2001
> From: Jochen Sprickerhof 
> Date: Sat, 30 Jan 2021 15:02:58 +0100
> Subject: [PATCH 1/5] Stop decoding strings (not needed in Python 3)
> 
> ---
>  gbp/rpm/__init__.py | 23 +--
>  1 file changed, 9 insertions(+), 14 deletions(-)
> 
> diff --git a/gbp/rpm/__init__.py b/gbp/rpm/__init__.py
> index 61d9d35..1d7a9ef 100644
> --- a/gbp/rpm/__init__.py
> +++ b/gbp/rpm/__init__.py
> @@ -34,11 +34,6 @@ from gbp.rpm.linkedlist import LinkedList
>  from gbp.rpm.lib_rpm import librpm, get_librpm_log
>  
>  
> -def _decode(s):
> -if s is not None:
> -return s.decode()
> -
> -
>  class NoSpecError(Exception):
>  """Spec file parsing error"""
>  pass
> @@ -79,8 +74,8 @@ class SrcRpmFile(object):
>  @property
>  def version(self):
>  """Get the (downstream) version of the RPM package"""
> -version = 
> dict(upstreamversion=self.rpmhdr[librpm.RPMTAG_VERSION].decode(),
> -   release=self.rpmhdr[librpm.RPMTAG_RELEASE].decode())
> +version = dict(upstreamversion=self.rpmhdr[librpm.RPMTAG_VERSION],
> +   release=self.rpmhdr[librpm.RPMTAG_RELEASE])
>  if self.rpmhdr[librpm.RPMTAG_EPOCH] is not None:
>  version['epoch'] = str(self.rpmhdr[librpm.RPMTAG_EPOCH])
>  return version
> @@ -88,17 +83,17 @@ class SrcRpmFile(object):
>  @property
>  def name(self):
>  """Get the name of the RPM package"""
> -return self.rpmhdr[librpm.RPMTAG_NAME].decode()
> +return self.rpmhdr[librpm.RPMTAG_NAME]
>  
>  @property
>  def upstreamversion(self):
>  """Get the upstream version of the RPM package"""
> -return self.rpmhdr[librpm.RPMTAG_VERSION].decode()
> +return self.rpmhdr[librpm.RPMTAG_VERSION]
>  
>  @property
>  def packager(self):
>  """Get the packager of the RPM package"""
> -return _decode(self.rpmhdr[librpm.RPMTAG_PACKAGER])
> +return self.rpmhdr[librpm.RPMTAG_PACKAGER]
>  
>  def unpack(self, dest_dir):
>  """
> @@ -168,13 +163,13 @@ class SpecFile(object):
>  
>  # Other initializations
>  source_header = self._specinfo.packages[0].header
> -self.name = source_header[librpm.RPMTAG_NAME].decode()
> -self.upstreamversion = source_header[librpm.RPMTAG_VERSION].decode()
> -self.release = source_header[librpm.RPMTAG_RELEASE].decode()
> +self.name = source_header[librpm.RPMTAG_NAME]
> +self.upstreamversion = source_header[librpm.RPMTAG_VERSION]
> +self.release = source_header[librpm.RPMTAG_RELEASE]
>  # rpm-python returns epoch as 'long', convert that to string
>  self.epoch = str(source_header[librpm.RPMTAG_EPOCH]) \
>  if source_header[librpm.RPMTAG_EPOCH] is not None else None
> -self.packager = _decode(source_header[librpm.RPMTAG_PACKAGER])
> +self.packager = source_header[librpm.RPMTAG_PACKAGER]
>  self._tags = {}
>  self._special_directives = defaultdict(list)
>  self._gbp_tags = defaultdict(list)
> -- 
> 2.30.0
> 

> From 9b24dba68476ffac638bfba9561a810528519646 Mon Sep 17 00:00:00 2001
> From: Jochen Sprickerhof 
> Date: Sat, 30 Jan 2021 15:03:25 +0100
> Subject: [PATCH 2/5] Open tempfile in text mode
> 
> ---
>  gbp/rpm/lib_rpm.py | 2 +-
>  1 file changed, 1 

Bug#980256: [git-buildpackage/master] autopkgtest: Set %_arch

[Jochen Sprickerhof]

tag 980256 pending
thanks

Date:   Sat Jan 30 20:38:05 2021 +0100
Author: Jochen Sprickerhof 
Commit ID: 5949fbc41d0008efb1f06c42e227bdbcceb7e0ff
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=5949fbc41d0008efb1f06c42e227bdbcceb7e0ff
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=5949fbc41d0008efb1f06c42e227bdbcceb7e0ff

autopkgtest: Set %_arch

Seems to be needed on armhf.

Closes: #980256

  

Bug#970497: Test suite error on mips64el architecture (#1469)

[Tamás Nepusz]

My two cents: if `dseupd_` gives random output for the same input then it is 
most likely a bug in ARPACK, although it would be good to have an isolated test 
case that does not involve igraph. @jgmbenoit have you managed to produce such 
a test case, or do you need a hand with creating one? If you have submitted a 
bug report to ARPACK, can you add the link here so I can keep an eye on it?

Re the `--without-scg` option, @szhorvat noted that the bug does not arise in 
the spectral coarse graining routines (which could easily be made optional) but 
in eigenvector calculations (which are pretty central to igraph) so there is 
probably not much point in adding `--without-scg`.

-- 
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/igraph/igraph/issues/1469#issuecomment-770267692

Bug#981441: trapperkeeper-scheduler-clojure: FTBFS on all

[Ivo De Decker]

package: src:trapperkeeper-scheduler-clojure
version: 1.1.3-3
severity: serious
tags: ftbfs

Hi,

The latest upload of trapperkeeper-scheduler-clojure to unstable fails on all:

https://buildd.debian.org/status/package.php?p=trapperkeeper-scheduler-clojure

Cheers,

Ivo

Processed: libxcb: diff for NMU version 1.14-2.2

[Debian Bug Tracking System]

Processing control commands:

> forwarded 980602 https://gitlab.freedesktop.org/xorg/lib/libxcb/-/issues/49
Bug #980602 [src:libxcb] libxcb: FTBFS: ../../tests/check_public.c:40:24: 
error: too many arguments for format [-Werror=format-extra-args]
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/xorg/lib/libxcb/-/issues/49'.
> tags 980602 + patch
Bug #980602 [src:libxcb] libxcb: FTBFS: ../../tests/check_public.c:40:24: 
error: too many arguments for format [-Werror=format-extra-args]
Added tag(s) patch.
> tags 980602 + pending
Bug #980602 [src:libxcb] libxcb: FTBFS: ../../tests/check_public.c:40:24: 
error: too many arguments for format [-Werror=format-extra-args]
Added tag(s) pending.

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

Bug#980602: libxcb: diff for NMU version 1.14-2.2

[Jochen Sprickerhof]

Control: forwarded 980602 
https://gitlab.freedesktop.org/xorg/lib/libxcb/-/issues/49
Control: tags 980602 + patch
Control: tags 980602 + pending


Dear maintainer,

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

Regards.

diff -u libxcb-1.14/debian/changelog libxcb-1.14/debian/changelog
--- libxcb-1.14/debian/changelog
+++ libxcb-1.14/debian/changelog
@@ -1,3 +1,11 @@
+libxcb (1.14-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply upstream patch to fix ftbfs (Closes: #980602)
+Taken from: https://gitlab.freedesktop.org/xorg/lib/libxcb/-/commit/f01f3c37
+
+ -- Jochen Sprickerhof   Sun, 31 Jan 2021 11:44:14 +0100
+
 libxcb (1.14-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
only in patch2:
unchanged:
--- libxcb-1.14.orig/configure.ac
+++ libxcb-1.14/configure.ac
@@ -36,7 +36,7 @@
 AC_MSG_WARN([dot not found - doxygen targets will be skipped])
 fi
 
-PKG_CHECK_MODULES(CHECK, [check >= 0.9.4], [HAVE_CHECK=yes], [HAVE_CHECK=no])
+PKG_CHECK_MODULES(CHECK, [check >= 0.9.6], [HAVE_CHECK=yes], [HAVE_CHECK=no])
 AM_CONDITIONAL(HAVE_CHECK, test x$HAVE_CHECK = xyes)
 
 XSLTPROC=no
only in patch2:
unchanged:
--- libxcb-1.14.orig/tests/check_public.c
+++ libxcb-1.14/tests/check_public.c
@@ -37,18 +37,18 @@
 		got_display = got_screen = -42;
 		mark_point();
 		success = xcb_parse_display(argument, _host, _display, _screen);
-		fail_unless(success, "unexpected parse failure %sfor '%s'", test_string[test_type], name);
-		fail_unless(strcmp(host, got_host) == 0, "parse %sproduced unexpected hostname '%s' for '%s': expected '%s'", test_string[test_type], got_host, name, host);
-		fail_unless(display == got_display, "parse %sproduced unexpected display '%d' for '%s': expected '%d'", test_string[test_type], got_display, name, display);
-		fail_unless(screen == got_screen, "parse %sproduced unexpected screen '%d' for '%s': expected '%d'", test_string[test_type], got_screen, name, screen);
+		ck_assert_msg(success, "unexpected parse failure %sfor '%s'", test_string[test_type], name);
+		ck_assert_msg(strcmp(host, got_host) == 0, "parse %sproduced unexpected hostname '%s' for '%s': expected '%s'", test_string[test_type], got_host, name, host);
+		ck_assert_msg(display == got_display, "parse %sproduced unexpected display '%d' for '%s': expected '%d'", test_string[test_type], got_display, name, display);
+		ck_assert_msg(screen == got_screen, "parse %sproduced unexpected screen '%d' for '%s': expected '%d'", test_string[test_type], got_screen, name, screen);
 
 		got_host = (char *) -1;
 		got_display = got_screen = -42;
 		mark_point();
 		success = xcb_parse_display(argument, _host, _display, 0);
-		fail_unless(success, "unexpected screenless parse failure %sfor '%s'", test_string[test_type], name);
-		fail_unless(strcmp(host, got_host) == 0, "screenless parse %sproduced unexpected hostname '%s' for '%s': expected '%s'", test_string[test_type], got_host, name, host);
-		fail_unless(display == got_display, "screenless parse %sproduced unexpected display '%d' for '%s': expected '%d'", test_string[test_type], got_display, name, display);
+		ck_assert_msg(success, "unexpected screenless parse failure %sfor '%s'", test_string[test_type], name);
+		ck_assert_msg(strcmp(host, got_host) == 0, "screenless parse %sproduced unexpected hostname '%s' for '%s': expected '%s'", test_string[test_type], got_host, name, host);
+		ck_assert_msg(display == got_display, "screenless parse %sproduced unexpected display '%d' for '%s': expected '%d'", test_string[test_type], got_display, name, display);
 	}
 	putenv("DISPLAY=");
 }
@@ -79,18 +79,18 @@
 		got_display = got_screen = -42;
 		mark_point();
 		success = xcb_parse_display(argument, _host, _display, _screen);
-		fail_unless(!success, "unexpected parse success %sfor '%s'", test_string[test_type], name);
-		fail_unless(got_host == (char *) -1, "host changed on parse failure %sfor '%s': got %p", test_string[test_type], name, got_host);
-		fail_unless(got_display == -42, "display changed on parse failure %sfor '%s': got %d", test_string[test_type], name, got_display);
-		fail_unless(got_screen == -42, "screen changed on parse failure %sfor '%s': got %d", test_string[test_type], name, got_screen);
+		ck_assert_msg(!success, "unexpected parse success %sfor '%s'", test_string[test_type], name);
+		ck_assert_msg(got_host == (char *) -1, "host changed on parse failure %sfor '%s': got %p", test_string[test_type], name, got_host);
+		ck_assert_msg(got_display == -42, "display changed on parse failure %sfor '%s': got %d", test_string[test_type], name, got_display);
+		ck_assert_msg(got_screen == -42, "screen changed on parse failure %sfor '%s': got %d", test_string[test_type], name, got_screen);
 
 		got_host = (char *) -1;
 		got_display = got_screen = -42;
 		mark_point();
 		success = xcb_parse_display(argument, _host, _display, 0);
-		fail_unless(!success,