Bug#972118: marked as done (tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer libtss2-esys0)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 15:49:21 +0800
with message-id <3b3d7e1a-94e1-ed92-b142-26c94251f...@debian.org>
and subject line Re: tpm2-abrmd: Daemon fails to start: needs to be rebuilt 
against newer libtss2-esys0
has caused the Debian Bug report #972118,
regarding tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer 
libtss2-esys0
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.)


-- 
972118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tpm2-abrmd
Version: 2.3.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
tpm2-abrmd fails to start with the error

error while loading shared libraries: libtss2-sys.so.0: cannot open
shared object file: No such file or directory

I believe this is because the package libtss2-esys0 bumped the SONAME
of that library to libtss2-sys.so.1. I wonder if tpm2-abrmd simply
needs to be rebuilt against this newer library.

Thanks,
Jan Medlock

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

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

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


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

Kernel: Linux 5.8.0-3-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tpm2-abrmd depends on:
ii  init-system-helpers  1.58
ii  libc62.31-4
ii  libglib2.0-0 2.66.1-1
ii  libtss2-esys03.0.1-1

tpm2-abrmd recommends no packages.

tpm2-abrmd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Package: tpm2-abrmd
Version: 2.3.3-1+b2
Done: Ying-Chun Liu (PaulLiu) 

Hi all.
We've requested binNMU and it is already there.

tpm2-abrmd:
  Installed: (none)
  Candidate: 2.3.3-1+b2
  Version table:
 2.3.3-1+b2 500
500 http://ftp.us.debian.org/debian testing/main amd64 Packages

Let's close this bug.

Yours,
Paul

--- End Message ---

Bug#978383: marked as done (macopix: FTBFS: configure:17428: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?))

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 06:48:19 +
with message-id 
and subject line Bug#978383: fixed in macopix 3.4.0+dfsg.1-3
has caused the Debian Bug report #978383,
regarding macopix: FTBFS: configure:17428: error: possibly undefined macro: 
AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?)
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.)


-- 
978383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macopix
Version: 3.4.0+dfsg.1-2
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_autoreconf /<>/autogen.sh
> **警告**: ./configure を引数無しで実行します。
>   もし引数を指定したいのであれば、
>   '/<>/autogen.sh' の引数に指定してください。
> 処理中...
> 削除中... .deps/ ディレクトリ ...
> 確認中... ドキュメントファイル ...
> 確認中... NEWS... 空です。必ず中身を作成してください
> 確認中... README...完了
> 確認中... AUTHORS...完了
> 確認中... ChangeLog...完了
> 確認中... po ファイル ...
> 確認中... po/ja.po ...完了
> 実行中... libtoolize...
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: putting macros in 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
> libtoolize: and rerunning libtoolize and aclocal.
> 実行中... aclocal  ...
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.ac:224: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from...
> configure.ac:224: the top level
> configure.ac:389: warning: AC_CACHE_VAL(gnutls_libs, ...): suspicious 
> cache-id, must contain _cv_ to be cached
> ../../lib/autoconf/general.m4:2042: AC_CACHE_VAL is expanded from...
> ../../lib/autoconf/general.m4:2063: AC_CACHE_CHECK is expanded from...
> configure.ac:389: the top level
> 実行中... autoconf...
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.ac:224: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> aclocal.m4:77: AM_GNU_GETTEXT is expanded from...
> configure.ac:224: the top level
> configure.ac:389: warning: AC_CACHE_VAL(gnutls_libs, ...): suspicious 
> cache-id, must contain _cv_ to be cached
> ../../lib/autoconf/general.m4:2042: AC_CACHE_VAL is expanded from...
> ../../lib/autoconf/general.m4:2063: AC_CACHE_CHECK is expanded from...
> configure.ac:389: the top level
> configure:17428: error: possibly undefined macro: AM_INTL_SUBDIR
>   If this token and others are legitimate, please use m4_pattern_allow.
>   See the Autoconf documentation.
> make[1]: Leaving directory '/<>'
>debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<>'
> dh_auto_configure -- --bindir=/usr/games
>   ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-option-checking --disable-silent-rules 
> --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
> --disable-maintainer-mode --disable-dependency-tracking --bindir=/usr/games
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking target system type... x86_64-pc-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> /bin/bash: /<>/missing: No such file or directory
> configure: WARNING: 'missing' script is too old or missing
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts 

Processed: fixed 978685 in 2.0.235-4

[Debian Bug Tracking System]

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

> fixed 978685 2.0.235-4
Bug #978685 [libjhlabs-filters-java] libjhlabs-filters-java: tries to overwrite 
/usr/share/doc-base/doc-base
There is no source info for the package 'libjhlabs-filters-java' at version 
'2.0.235-4' with architecture ''
Unable to make a source version for version '2.0.235-4'
Marked as fixed in versions 2.0.235-4.
> thanks
Stopping processing here.

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

Bug#978685: libjhlabs-filters-java: tries to overwrite /usr/share/doc-base/doc-base

[tony mancill]

Package: libjhlabs-filters-java
Version: 2.0.235-3.1
Severity: serious

The source NMU and subsequent rebuild of (the quite ancient)
libjhlabs-filters-java resulted in a binary package containing
/usr/share/doc-base/doc-base, which breaks the dpkg install run.

This has been addressed in the upload of 2.0.235-4.

Bug#978383: macopix: FTBFS: configure:17428: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?)

[Ying-Chun Liu (PaulLiu)]

Hi Lucas,


Thanks for reporting.

patch as attachment. Will fix this bug soon.


Yours,

Paul


Description: Porting to gettext 0.21
 gettext 0.21 doesn't allow to use AM_GNU_GETTEXT without version.
 We patch configure.ac to use AM_GNU_GETTEXT_VERSION.
Bug-Debian: http://bugs.debian.org/978383
Author: Ying-Chun Liu (PaulLiu) 
Last-Update: 2020-12-25
Index: macopix-3.4.0+dfsg.1/configure.ac
===
--- macopix-3.4.0+dfsg.1.orig/configure.ac
+++ macopix-3.4.0+dfsg.1/configure.ac
@@ -221,7 +221,12 @@ AC_PATH_PROG([GLIB_COMPILE_RESOURCES], [
 
 dnl for gettext
 ALL_LINGUAS="ja"
-AM_GNU_GETTEXT
+AM_GNU_GETTEXT_VERSION(0.20)
+AM_GNU_GETTEXT([external])
+USE_INCLUDED_LIBINTL="no"
+AC_SUBST(USE_INCLUDED_LIBINTL)
+BUILD_INCLUDED_LIBINTL="no"
+AC_SUBST(BUILD_INCLUDED_LIBINTL)
 GETTEXT_PACKAGE=macopix
 AC_SUBST(LOCALEDIR)
 AC_SUBST(GETTEXT_PACKAGE)

Processed: Re: Bug#978675: libsys-hostname-long-perl: FTBFS, tests fail

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + ftbfs fixed
Bug #978675 [libsys-hostname-long-perl] libsys-hostname-long-perl: FTBFS, tests 
fail
Added tag(s) fixed and ftbfs.

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

Bug#978675: libsys-hostname-long-perl: FTBFS, tests fail

[Axel Beckert]

Control: tag -1 + ftbfs fixed

Hi Holger,

Holger Levsen wrote:
> Package: libsys-hostname-long-perl
> Version: 1.5-1

I've added the tag ftbfs so that it also shows up on
https://buildd.debian.org/status/package.php?p=libsys-hostname-long-perl

> when trying to build libsys-hostname-long-perl in current sid it fails:

Thanks for the bug report. gregoa just made an upload which modernizes
the package and also increases verbosity to see what actually goes
wrong. And as it seems, the general overhaul seems also have to fixed
this issue. At least on the buildds, the package built fine:

https://buildd.debian.org/status/package.php?p=libsys-hostname-long-perl=unstable

Holger: Can you check if this is the case on your side, too?

gregoa: I'll leave up to you if you already want to close the bug
report or not. Feel free to replace my fixed tag with a pending tag or
so.

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#978382: phpmyadmin: FTBFS: Test directory "./test/engines" not found

[David Prévot]

Hi,

Le Sat, Dec 26, 2020 at 11:07:44PM +0100, Lucas Nussbaum a écrit :
> Source: phpmyadmin
[…]
> > PHPUnit 9.5.0 by Sebastian Bergmann and contributors.
> > 
> > Test directory "./test/engines" not found
> > make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2

This issue may be trivial (you “just” need to skip the Engines
testsuite), but a look at the last buildlog of phpmyadmin reveals 459
warnings, most of them related to PHPUnit 9 (that are now errors).

I’m sorry I haven’t noticed this sooner: the new autopkgtest failures
didn’t show up about the transition of phpunit from experimental (and
they still don’t show up regarding the transition of phpunit to
testing).

I notice that PHPMyAdmin 5 has already been released a year ago, and the
next one will be 5.1 (already RC) according to their last announcement.
On the other end, 4.9 seems to be the LTS to support PHP 5.5-7.0 (no end
of extended security support available on their public download page).

Since version 5 is not yet in Debian, I assume you intend to ship
version 4.9 for Bullseye (but would prefer to have an explicit
acknowledgement before trying to look at all of these issues). On the
other hand, I believe this version won’t be compatible with PHP 8.0, so
you may want to at least document that in a bug blocking #976811 if you
intend to stick with 4.9.

Anyway, I apologize for pushing PHPUnit 9 to unstable so late in the
release cycle (#976811 transition: php8.0 triggered some panic), and
intend to help fixing those issues if needed, so please, do not hesitate
to ask, I CCed the PHP PEAR (and Composer) Maintainers list for that.

Regards

David


signature.asc
Description: PGP signature

Bug#978381: google-recaptcha: FTBFS: TypeError: Argument 2 passed to PHPUnit\Framework\Assert::assertContains() must be iterable, string given, called in /<>/tests/ReCaptcha/RequestMethod

[David Prévot]

Control: tag -1 patch

Le Sat, Dec 26, 2020 at 11:02:04PM +0100, Lucas Nussbaum a écrit :

> Relevant part (hopefully):
[…]
> > There were 6 errors:
> > 
> > 1) ReCaptcha\ReCaptchaTest::testExceptionThrownOnInvalidSecret with data 
> > set #0 ('')
> > RuntimeException: No secret provided
[…]
> > 6) ReCaptcha\RequestMethod\PostTest::testHTTPContextOptions
> > TypeError: Argument 2 passed to PHPUnit\Framework\Assert::assertContains() 
> > must be iterable, string given, called in 
> > /<>/tests/ReCaptcha/RequestMethod/PostTest.php on line 118

Please find attached a patch fixing these issues (that were already
warnings with PHPUnit 8).

I wonder why this failure wasn’t caught sooner by the autopkgtest (or I
would have noticed it before pushing PHPUnit 9 to unstable).

Regards

David
From: =?utf-8?q?David_Pr=C3=A9vot?= 
Date: Tue, 29 Dec 2020 22:51:55 -0400
Subject: Adapt to recent version of PHPUnit (9)

Bug-Debian: https://bugs.debian.org/978381
---
 tests/ReCaptcha/ReCaptchaTest.php  | 2 +-
 tests/ReCaptcha/RequestMethod/PostTest.php | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/ReCaptcha/ReCaptchaTest.php b/tests/ReCaptcha/ReCaptchaTest.php
index ddb16f0..6a90d9e 100644
--- a/tests/ReCaptcha/ReCaptchaTest.php
+++ b/tests/ReCaptcha/ReCaptchaTest.php
@@ -40,11 +40,11 @@ class ReCaptchaTest extends TestCase
 {
 
 /**
- * @expectedException \RuntimeException
  * @dataProvider invalidSecretProvider
  */
 public function testExceptionThrownOnInvalidSecret($invalid)
 {
+$this->expectException('\RuntimeException');
 $rc = new ReCaptcha($invalid);
 }
 
diff --git a/tests/ReCaptcha/RequestMethod/PostTest.php b/tests/ReCaptcha/RequestMethod/PostTest.php
index bdfb78e..88a298d 100644
--- a/tests/ReCaptcha/RequestMethod/PostTest.php
+++ b/tests/ReCaptcha/RequestMethod/PostTest.php
@@ -115,7 +115,7 @@ class PostTest extends TestCase
 'Content-type: application/x-www-form-urlencoded',
 );
 foreach ($headers as $header) {
-$this->assertContains($header, $options['http']['header']);
+$this->assertStringContainsString($header, $options['http']['header']);
 }
 }
 


signature.asc
Description: PGP signature

Processed: Re: Bug#978381: google-recaptcha: FTBFS: TypeError: Argument 2 passed to PHPUnit\Framework\Assert::assertContains() must be iterable, string given, called in /<>/tests/ReCaptch

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #978381 [src:google-recaptcha] google-recaptcha: FTBFS: TypeError: Argument 
2 passed to PHPUnit\Framework\Assert::assertContains() must be iterable, string 
given, called in /<>/tests/ReCaptcha/RequestMethod/PostTest.php on 
line 118
Added tag(s) patch.

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

Bug#978684: autopkgtest should test the installed package

[David Prévot]

Source: apk-parser
Severity: serious

Hi,

As pointed in the see autopkgtest specification [1] linked from the
release team documentation [2] “the tests must test the *installed*
version of the package”. The autopkgtest from this package only uses the
source package, and as such violates the specification. Displaying it as
an example in the wiki [3] may not be advisable.

Regards

David

1: 
https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst
2: https://release.debian.org/bullseye/freeze_policy.html
3: https://wiki.debian.org/Java/Packaging#autopkgtest


signature.asc
Description: PGP signature

Bug#971018: marked as done (libgnatcoll-db: FTBFS on mips(64)el with assembler message: branch out of range)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 03:33:42 +
with message-id 
and subject line Bug#971018: fixed in libgnatcoll-db 21.0.0-6
has caused the Debian Bug report #971018,
regarding libgnatcoll-db: FTBFS on mips(64)el with assembler message: branch 
out of range
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.)


-- 
971018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgnatcoll-db
Version: 20.0-1
Severity: serious
Justification: fails to build from scratch on previously built architectures

Hello.

libgnatcoll-db/20.0-1 in experimental fails to build on
mipsel and mips64el with the following messages [1].
  /tmp/ccl8IVnY.s: Assembler messages:
  /tmp/ccl8IVnY.s:692755: Error: branch out of range
  /tmp/ccl8IVnY.s:693545: Error: branch out of range
  /tmp/ccl8IVnY.s:693669: Error: branch out of range

The problem seems related to a previous bug [2] with similar symptoms [3].
  xref/gnatcoll-xref.adb: In function ‘GNATCOLL.XREF’:
  xref/gnatcoll-xref.adb:40:1: note: variable tracking size limit exceeded with 
‘-fvar-tracking-assignments’, retrying without
  Assembler messages:
  678119: Error: branch out of range

CFLAGS+=-mxgot has fixed the issue then, but does not seem sufficient
anymore.

Any advice would be welcome.

[1] 
https://buildd.debian.org/status/package.php?p=libgnatcoll-db=experimental
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953069
[3] 
https://buildd.debian.org/status/fetch.php?pkg=libgnatcoll-db=mipsel=19.2-2=1584014543=0
--- End Message ---
--- Begin Message ---
Source: libgnatcoll-db
Source-Version: 21.0.0-6
Done: Nicolas Boulenguez 

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

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

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

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated libgnatcoll-db 
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: Wed, 29 Dec 2020 17:08:02 +
Source: libgnatcoll-db
Architecture: source
Version: 21.0.0-6
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Boulenguez 
Changed-By: Nicolas Boulenguez 
Closes: 971018
Changes:
 libgnatcoll-db (21.0.0-6) unstable; urgency=medium
 .
   [ Peter Michael Green ]
   * Use -Os on mipsel, to work around jump length error (Closes: 971018).
Checksums-Sha1:
 f6fd9f9f522e42c65187c4f0f262b7f1553691b7 3015 libgnatcoll-db_21.0.0-6.dsc
 c51b0405d2565b0d95dd80db93401b0cd25ae18e 18912 
libgnatcoll-db_21.0.0-6.debian.tar.xz
 e4df8cbd483ee5e43bff3071315f6fd0cc665c28 3278 
libgnatcoll-db_21.0.0-6_source.buildinfo
Checksums-Sha256:
 f3bd7fa453ffb7bc3c2f6d707c00d7097d5e505c22e43965fe068ec97fa6a079 3015 
libgnatcoll-db_21.0.0-6.dsc
 36120d7c3eb2cc5103228aa6d166f58c4b6573d99c54ef514e918cd63ed3 18912 
libgnatcoll-db_21.0.0-6.debian.tar.xz
 d48b6016f39e3a15261b2a13ce5d4b98afc50a2af8e5e74f08182c4719f811de 3278 
libgnatcoll-db_21.0.0-6_source.buildinfo
Files:
 26e4aa6d0d13fe4e22871b7135d08f82 3015 libdevel optional 
libgnatcoll-db_21.0.0-6.dsc
 e96701927c9917fe6037c17d85b3a339 18912 libdevel optional 
libgnatcoll-db_21.0.0-6.debian.tar.xz
 88edb7fbb912ac507b89b0ad8def8615 3278 libdevel optional 
libgnatcoll-db_21.0.0-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAl/r78wTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jdlUD/4uh6dgvUAxkUf538W0V7f2F6TjKTwT
JUTERCUYYPqv4glfIXuCeMPUJk5jT//MOJldSniCUQkqC7g9rZFkoJ3l708/aIHc
S+iF4EMoXWrkRBBWpiEpM9s/IVvEVQPazLssfd5k9knsv6vbQ5Qh/Ym6YlAKqcMN
bKBrfKJ8EXK/uKICUiLwc5H0i8tJNreEYE+EEttAWWr7vkKIMSCW9smIwIko11ea
BFfOG/mloKIlh1YTmxVIMpuGW+OKsoqutWuq+xjITJQi3uvLUdWqTLGpulKLyozp
Ndi0L/tbveKN5N0dQEJNHS6Z9xQEzGL7gfH1eOknkiLNYnceVrA5fd8up5NfTVbF
RgI4dGCcXj0I053ofuUVfTjN2J1Ew8EcHuHbljB1AAj+6rx2mx26iWrB6Ihlw267
LAFdsUbcNxFxHc8Nqb48NFWE9oyjX83h3i9E6Qfg+54M4vAY7RemMMCR/IKgnUJ9
GB+fUxsD+e8goyjoo0uXYZwiw0UkZRWghjwSPiDO5cgtyFNjiDvNM05kcFxaJ7fQ
dvlunfWH482ZoGbH0w3kM46AO1ISWe1w1MuvtuRuEF7+TnOyhUylVg9D+t86Nt7h
AmwX70Cv7uH3cnCgLGTcYB/poHsV25NKoXvIzwVOhVvdPCWjGDvOkYu3THc8SqqM
NMShkHlRLsCiTw==
=ScOo

Processed: severity of 977645 is important, tagging 977647 ..., reassign 977694 to src:linux ...

[Debian Bug Tracking System]

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

> severity 977645 important
Bug #977645 [src:linux] 5.10.2 Debian kernel does not boot on raspi 4 with ext4 
rootfs and sdcard
Severity set to 'important' from 'grave'
> tags 977647 - moreinfo
Bug #977647 [src:linux] 5.10.2 Debian kernel does not boot on amd64 with btrfs 
rootfs
Removed tag(s) moreinfo.
> retitle 977647 5.10 boot hang on Panasonic CFSV9-2
Bug #977647 [src:linux] 5.10.2 Debian kernel does not boot on amd64 with btrfs 
rootfs
Changed Bug title to '5.10 boot hang on Panasonic CFSV9-2' from '5.10.2 Debian 
kernel does not boot on amd64 with btrfs rootfs'.
> reassign 977694 src:linux 5.10.1-1~exp1
Bug #977694 [linux-image-5.10.0-trunk-arm64-unsigned] 5.10.1 Debian kernel does 
not boot on raspi 4 with ext4 rootfs and usb-msd
Bug reassigned from package 'linux-image-5.10.0-trunk-arm64-unsigned' to 
'src:linux'.
No longer marked as found in versions linux/5.10.1-1~exp1.
Ignoring request to alter fixed versions of bug #977694 to the same values 
previously set
Bug #977694 [src:linux] 5.10.1 Debian kernel does not boot on raspi 4 with ext4 
rootfs and usb-msd
Marked as found in versions linux/5.10.1-1~exp1.
> retitle 977694 5.10 boot hang on Raspberry Pi 4 with ext4 rootfs and usb-msd
Bug #977694 [src:linux] 5.10.1 Debian kernel does not boot on raspi 4 with ext4 
rootfs and usb-msd
Changed Bug title to '5.10 boot hang on Raspberry Pi 4 with ext4 rootfs and 
usb-msd' from '5.10.1 Debian kernel does not boot on raspi 4 with ext4 rootfs 
and usb-msd'.
> severity 977694 important
Bug #977694 [src:linux] 5.10 boot hang on Raspberry Pi 4 with ext4 rootfs and 
usb-msd
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#978682: xfce4-verve-plugin: build-depends on obsolete package.

[plugwash]

Package: xfce4-verve-plugin
Version: 2.0.0-1
Severity: serious
Tags: bullseye, sid

xfce4-verve-plugin build-depends on libexo-1-dev which is no longer 
built by the exo source package,
it is still present in unstable as a cruft package, but is completely 
gone from testing.

Bug#978681: xfce4-mpc-plugin: build-depends on obsolete package.

[plugwash]

Package: xfce4-mpc-plugin
Version: 0.5.2-1
Severity: serious
Tags: bullseye, sid

xfce4-mpc-plugin build-depends on libexo-1-dev which is no longer built 
by the exo source package,
it is still present in unstable as a cruft package, but is completely 
gone from testing.

Bug#978680: xfce4-indicator-plugin: build-depends on obsolete package.

[plugwash]

Package: xfce4-indicator-plugin
Version: 2.3.4-2
Severity: serious
Tags: bullseye, sid

xfce4-indictor-plugin build-depends on libexo-1-dev which is no longer 
built by the exo source package,
it is still present in unstable as a cruft package, but is completely 
gone from testing.

Bug#978679: bedtools: autpkgtest failures

[plugwash]

Package: bedtools
Version: 2.29.2+dfsg-4
Severity: serious

The autopkgtests for bedtools are failing on all tested architectures 
(though they are "not a regression" on i386 and armhf). When I look at 
the amd64 failure logs, the failures all seem to be missing "../htsutil"



Testing bedtools bamtobed:
test-bamtobed.sh: line 22: ../htsutil: No such file or directory
Testing bedtools bamtofastq:
test-bamtofastq.sh: line 17: ../htsutil: No such file or directory



Testing bedtools bedtobam:
 bedtobam.t1...test-bedtobam.sh: line 23: ../htsutil: No such file or 
directory



Testing bedtools coverage:
test-coverage.sh: line 22: ../htsutil: No such file or directory
Testing bedtools genomecov:
test-genomecov.sh: line 22: ../htsutil: No such file or directory



Testing bedtools intersect:
 intersect.t01...ok
 intersect.t02...ok
 intersect.t03...ok
 intersect.t04...ok
 intersect.t05...ok
 intersect.t06...ok
 intersect.t07...ok
 intersect.t08...ok
 intersect.t09...ok
 intersect.t10...ok
 intersect.t11...ok
 intersect.t12...ok
 intersect.t13...ok
 intersect.t14...ok
 intersect.t15...ok
 intersect.t16...ok
test-intersect.sh: line 200: ../htsutil: No such file or directory
Testing bedtools multicov:
test-multicov.sh: line 17: ../htsutil: No such file or directory

Bug#978667: bug #978667 update

[William Melgaard]

see attached for program which generates the reported bug.This program assumes (two identical) cameras at /dev/video1 and /dev/video3// v4l2_test.c
// compile as $ gcc v4l2_test.c -o v4l2_test

#define MMAP_BUFFERS 3

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
struct v4l2_capability lcap, rcap;
struct v4l2_format lfmt, rfmt;


int xioctl(int fh, int request, void *arg){
  int r;
  do {
r = ioctl(fh, request, arg);
  } while (r == -1 && ((errno == EINTR) || (errno == EAGAIN)));
  return r;
}

int main(int argc, char **argv){
  char *left_camera, *right_camera;
  int lfd, rfd, i, r;
  struct v4l2_buffer lbuf, rbuf;
  left_camera = "/dev/video1";
  right_camera = "/dev/video3";
  // Open the device
  lfd = open(left_camera, O_RDWR | O_NONBLOCK, 0);
  if (lfd < 0) {
printf("Failed to open left camera\n");
exit(EXIT_FAILURE);
  }
  rfd = open(right_camera, O_RDWR | O_NONBLOCK, 0);
  if (rfd < 0) {
printf("Failed to open right camera\n");
exit(EXIT_FAILURE);
  }

  if (-1 == xioctl(lfd, VIDIOC_QUERYCAP, )) {
printf("Left ERROR: %s\n", strerror(errno));
if(lcap.capabilities != V4L2_CAP_VIDEO_CAPTURE)
  printf("ERROR Left camera deficient capability\n");
exit(EXIT_FAILURE);
  }
  if (-1 == xioctl(rfd, VIDIOC_QUERYCAP, )) {
printf("Right ERROR: %s\n", strerror(errno));
if(rcap.capabilities != V4L2_CAP_VIDEO_CAPTURE)
  printf("ERROR Right camera deficient capability\n");
exit(EXIT_FAILURE);
  }
  // poll fd for device format
  lfmt.type = V4L2_BUF_TYPE_VIDEO_CAPTURE; // == 1
  if(-1 == xioctl(lfd, VIDIOC_G_FMT, )){
printf("ERROR getting info from %s\n", left_camera);
return 1;
  }
  // poll fd for device format
  rfmt.type = V4L2_BUF_TYPE_VIDEO_CAPTURE; // == 1
  if(-1 == xioctl(rfd, VIDIOC_G_FMT, )){
printf("ERROR getting info from %s\n", right_camera);
return 1;
  }
  // Request N buffers that are memory mapped between
  // our application space and the device
  struct v4l2_requestbuffers l_request, r_request;
  l_request.count = r_request.count = MMAP_BUFFERS;
  l_request.type = r_request.type = V4L2_BUF_TYPE_VIDEO_CAPTURE;
  l_request.memory = r_request.memory = V4L2_MEMORY_MMAP;
  if(r = xioctl(lfd, VIDIOC_REQBUFS, _request) < 0){
printf("ERROR Request l buffer failed\n");
  }
  if(r = xioctl(lfd, VIDIOC_REQBUFS, _request) < 0){
printf("ERROR Request r buffer failed\n");
  }
  if(l_request.count != r_request.count)
printf("ERROR in request count match\n");
  printf("request count = %d\n", l_request.count);

  // Queue the buffers, i.e. indicate to the device
  // that they are available for writing now.
  for (i = 0; i < l_request.count; ++i) {
// struct v4l2_buffer buf; - declared at head of main()
lbuf.type = rbuf.type = V4L2_BUF_TYPE_VIDEO_CAPTURE;
lbuf.memory = rbuf.memory = V4L2_MEMORY_MMAP;
lbuf.index = rbuf.index = i;
if(r = xioctl(lfd, VIDIOC_QBUF, ) < 0)
  printf("ERROR Failed to QBUF left camera\n");
if(r = xioctl(rfd, VIDIOC_QBUF, ) < 0)
  printf("ERROR Failed to QBUF right camera\n");
  }

// Start stream v4l_buf_type
enum v4l2_buf_type type;
type = V4L2_BUF_TYPE_VIDEO_CAPTURE;
r = xioctl(lfd, VIDIOC_STREAMON, );
if(r < 0)printf("ERROR Failed to STREAMON left camera\n");
r = xioctl(rfd, VIDIOC_STREAMON, );
if(r < 0)printf("ERROR Failed to STREAMON right camera\n");
  
}

Bug#978667: bug #978667 update

[William Melgaard]

There is a typo in line 95 my previous submission. Corrected program is attachedThe result is that ioctl(rfd, VIDIOC_QBUF, );is successful, but ioctl(rfd, VIDIOC_STREAMON, );(i.e. second camera) is not successful// v4l2_test.c
// compile as $ gcc v4l2_test.c -o v4l2_test

#define MMAP_BUFFERS 3

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
struct v4l2_capability lcap, rcap;
struct v4l2_format lfmt, rfmt;


int xioctl(int fh, int request, void *arg){
  int r;
  do {
r = ioctl(fh, request, arg);
  } while (r == -1 && ((errno == EINTR) || (errno == EAGAIN)));
  return r;
}

int main(int argc, char **argv){
  char *left_camera, *right_camera;
  int lfd, rfd, i, r;
  struct v4l2_buffer lbuf, rbuf;
  left_camera = "/dev/video1";
  right_camera = "/dev/video3";
  // Open the device
  lfd = open(left_camera, O_RDWR | O_NONBLOCK, 0);
  if (lfd < 0) {
printf("Failed to open left camera\n");
exit(EXIT_FAILURE);
  }
  rfd = open(right_camera, O_RDWR | O_NONBLOCK, 0);
  if (rfd < 0) {
printf("Failed to open right camera\n");
exit(EXIT_FAILURE);
  }

  if (-1 == xioctl(lfd, VIDIOC_QUERYCAP, )) {
printf("Left ERROR: %s\n", strerror(errno));
if(lcap.capabilities != V4L2_CAP_VIDEO_CAPTURE)
  printf("ERROR Left camera deficient capability\n");
exit(EXIT_FAILURE);
  }
  if (-1 == xioctl(rfd, VIDIOC_QUERYCAP, )) {
printf("Right ERROR: %s\n", strerror(errno));
if(rcap.capabilities != V4L2_CAP_VIDEO_CAPTURE)
  printf("ERROR Right camera deficient capability\n");
exit(EXIT_FAILURE);
  }
  // poll fd for device format
  lfmt.type = V4L2_BUF_TYPE_VIDEO_CAPTURE; // == 1
  if(-1 == xioctl(lfd, VIDIOC_G_FMT, )){
printf("ERROR getting info from %s\n", left_camera);
return 1;
  }
  // poll fd for device format
  rfmt.type = V4L2_BUF_TYPE_VIDEO_CAPTURE; // == 1
  if(-1 == xioctl(rfd, VIDIOC_G_FMT, )){
printf("ERROR getting info from %s\n", right_camera);
return 1;
  }
  // Request N buffers that are memory mapped between
  // our application space and the device
  struct v4l2_requestbuffers l_request, r_request;
  l_request.count = r_request.count = MMAP_BUFFERS;
  l_request.type = r_request.type = V4L2_BUF_TYPE_VIDEO_CAPTURE;
  l_request.memory = r_request.memory = V4L2_MEMORY_MMAP;
  if(r = xioctl(lfd, VIDIOC_REQBUFS, _request) < 0){
printf("ERROR Request l buffer failed\n");
  }
  if(r = xioctl(rfd, VIDIOC_REQBUFS, _request) < 0){
printf("ERROR Request r buffer failed\n");
  }
  if(l_request.count != r_request.count)
printf("ERROR in request count match\n");
  printf("request count = %d\n", l_request.count);

  // Queue the buffers, i.e. indicate to the device
  // that they are available for writing now.
  for (i = 0; i < l_request.count; ++i) {
// struct v4l2_buffer buf; - declared at head of main()
lbuf.type = rbuf.type = V4L2_BUF_TYPE_VIDEO_CAPTURE;
lbuf.memory = rbuf.memory = V4L2_MEMORY_MMAP;
lbuf.index = rbuf.index = i;
if(r = xioctl(lfd, VIDIOC_QBUF, ) < 0)
  printf("ERROR Failed to QBUF left camera\n");
if(r = xioctl(rfd, VIDIOC_QBUF, ) < 0)
  printf("ERROR Failed to QBUF right camera\n");
  }

// Start stream v4l_buf_type
enum v4l2_buf_type type;
type = V4L2_BUF_TYPE_VIDEO_CAPTURE;
r = xioctl(lfd, VIDIOC_STREAMON, );
if(r < 0)printf("ERROR Failed to STREAMON left camera\n");
r = xioctl(rfd, VIDIOC_STREAMON, );
if(r < 0)printf("ERROR Failed to STREAMON right camera\n");
  
}

Bug#978351: marked as done (requests: FTBFS: AttributeError: 'LookupDict' object has no attribute '__name__')

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 00:48:48 +
with message-id 
and subject line Bug#978351: fixed in requests 2.25.0+dfsg-2
has caused the Debian Bug report #978351,
regarding requests: FTBFS: AttributeError: 'LookupDict' 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.)


-- 
978351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: requests
Version: 2.25.0+dfsg-1
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 '/<>'
> PYTHONPATH=. python3 -m sphinx -D html_last_updated_fmt="December 08, 2020" 
> -N -bhtml docs/ \
>   debian/python-requests-doc/usr/share/doc/python-requests-doc/html/
> Running Sphinx v3.4.1
> making output directory... done
> loading intersphinx inventory from https://docs.python.org/3/objects.inv...
> loading intersphinx inventory from 
> https://urllib3.readthedocs.io/en/latest/objects.inv...
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 15 source files that are out of date
> updating environment: [new config] 15 added, 0 changed, 0 removed
> reading sources... [  6%] api
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/util/typing.py", line 160, in 
> _restify_py37
> return ':obj:`%s.%s`' % (cls.__module__, cls.__name__)
> AttributeError: 'LookupDict' object has no attribute '__name__'
> The full traceback has been saved in /tmp/sphinx-err-itgtnj9a.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:21: override_dh_sphinxdoc] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/requests_2.25.0+dfsg-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: requests
Source-Version: 2.25.0+dfsg-2
Done: Daniele Tricoli 

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

Debian distribution maintenance software
pp.
Daniele Tricoli  (supplier of updated requests 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: Wed, 30 Dec 2020 01:23:56 +0100
Source: requests
Architecture: source
Version: 2.25.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Daniele Tricoli 
Closes: 978351
Changes:
 requests (2.25.0+dfsg-2) unstable; urgency=medium
 .
   * debian/patches/0002-Temporary-exclude-requests.codes.patch
 - Temporary exclude requests.codes to make documentation not fail during
   build. (Closes: #978351)
   * debian/control
 - Bump Standards-Version to 4.5.1 (no changes needed).
Checksums-Sha1:
 cf1f58d808e372483cf9f2f891fcf2a2bd98b7f1 2311 requests_2.25.0+dfsg-2.dsc
 8de43f2559178e591325279a9c73b2653a041d3c 10796 
requests_2.25.0+dfsg-2.debian.tar.xz
 14c65a38451b27e9ff8ce8aa7e42137dc3579869 7715 
requests_2.25.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 ed4e7ca5aaf09e58d838ebdf8f3fe0e367f9f8d2afe449c7b41ec16f758f4a61 2311 

Processed: Re: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #975696 [src:link-grammar] link-grammar: multi-thread test fails
Severity set to 'serious' from 'important'

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

Bug#978675: libsys-hostname-long-perl: FTBFS, tests fail

[Holger Levsen]

Package: libsys-hostname-long-perl
Version: 1.5-1
Severity: serious

Dear Maintainer,

when trying to build libsys-hostname-long-perl in current sid it fails:

I: Building the package
I: Running cd /build/libsys-hostname-long-perl-1.5/ && env 
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent" 
dpkg-buildpackage -us -uc
dpkg-buildpackage: info: source package libsys-hostname-long-perl
dpkg-buildpackage: info: source version 1.5-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Axel Beckert 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 fakeroot debian/rules clean
dh clean
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_clean
dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in 
use)
 dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building libsys-hostname-long-perl using existing 
./libsys-hostname-long-perl_1.5.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building libsys-hostname-long-perl in 
libsys-hostname-long-perl_1.5-1.debian.tar.xz
dpkg-source: info: building libsys-hostname-long-perl in 
libsys-hostname-long-perl_1.5-1.dsc
 debian/rules build
dh build
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_update_autotools_config
   dh_auto_configure
dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
(level 9 in use)
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/build/libsys-hostname-long-perl-1.5=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 
-fdebug-prefix-map=/build/libsys-hostname-long-perl-1.5=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Sys::Hostname::Long
Writing MYMETA.yml and MYMETA.json
   dh_auto_build
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
make -j1
make[1]: Entering directory '/build/libsys-hostname-long-perl-1.5'
cp testall.pl blib/lib/Sys/Hostname/testall.pl
cp lib/Sys/Hostname/Long.pm blib/lib/Sys/Hostname/Long.pm
Manifying 1 pod document
make[1]: Leaving directory '/build/libsys-hostname-long-perl-1.5'
   dh_auto_test
dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
make -j1 test TEST_VERBOSE=1
make[1]: Entering directory '/build/libsys-hostname-long-perl-1.5'
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
"-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" 
t/
hostname: Temporary failure in name resolution
t/local.t ..
1..1
# Running under perl version 5.032000 for linux
# Current time local: Tue Dec 29 23:17:35 2020
# Current time GMT:   Tue Dec 29 23:17:35 2020
# Using Test.pm version 1.31
not ok 1
Your hostname =
Failed 1/1 subtests
Sys::Hostname::Long - Last Dispatch method = ip at 
/build/libsys-hostname-long-perl-1.5/blib/lib/Sys/Hostname/Long.pm line 206.
Use of uninitialized value $hostname in string ne at t/local.t line 10.
# Failed test 1 in t/local.t at line 10
#  t/local.t line 10 is: ok($hostname ne "");
Use of uninitialized value $hostname in concatenation (.) or string at 
t/local.t line 12.

Test Summary Report
---
t/local.t (Wstat: 0 Tests: 1 Failed: 1)
  Failed test:  1
Files=1, Tests=1,  0 wallclock secs ( 0.02 usr  0.01 sys +  0.04 cusr  0.00 
csys =  0.07 CPU)
Result: FAIL
make[1]: Leaving directory '/build/libsys-hostname-long-perl-1.5'
Failed 1/1 test programs. 1/1 subtests failed.
make[1]: *** [Makefile:830: test_dynamic] Error 255
dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2
make: *** [debian/rules:4: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
I: copying local configuration
E: Failed autobuilding of package
I: unmounting dev/ptmx filesystem
I: unmounting dev/pts filesystem
I: unmounting dev/shm filesystem
I: unmounting proc filesystem
I: unmounting sys filesystem
I: cleaning the build env
I: removing directory /srv/workspace/pbuilder/7694 and its subdirectories

-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

If secure encryption is outlawed, only criminals will have it.


signature.asc
Description: PGP signature

Bug#978206: marked as done (dolfin: FTBFS: MixedLinearVariationalSolver.cpp:240:23: error: variable ‘dolfin::PETScNestMatrix A’ has initializer but incomplete type)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 10:23:08 +1100
with message-id <88ad98a38dc07ec8f0865b319beb7...@debian.org>
and subject line dolfin: FTBFS: MixedLinearVariationalSolver.cpp:240:23: error: 
variable ‘dolfin::PETScNestMatrix A’ has initializer but incomplete type
has caused the Debian Bug report #978206,
regarding dolfin: FTBFS: MixedLinearVariationalSolver.cpp:240:23: error: 
variable ‘dolfin::PETScNestMatrix A’ has initializer but incomplete type
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.)


-- 
978206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dolfin
Version: 2019.2.0~git20200629.946dbd3+lfs-4
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):
> cd "/<>/obj-x86_64-linux-gnu/dolfin" && /usr/bin/c++ 
> -DDOLFIN_VERSION=\"2019.2.0.dev0\" -DHAS_CHOLMOD -DHAS_HDF5 -DHAS_MPI 
> -DHAS_UMFPACK -DHAS_ZLIB -DNDEBUG -Ddolfin_EXPORTS -I"/<>" 
> -I"/<>/obj-x86_64-linux-gnu" -isystem 
> /usr/lib/python3/dist-packages/ffc/backends/ufc -isystem /usr/include/eigen3 
> -isystem /usr/include/hdf5/openmpi -isystem /usr/include/suitesparse -isystem 
> /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem 
> /usr/lib/x86_64-linux-gnu/openmpi/include -fpermissive -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -O2 -g -DNDEBUG 
> -fPIC -std=c++11 -o 
> CMakeFiles/dolfin.dir/fem/MixedLinearVariationalSolver.cpp.o -c 
> "/<>/dolfin/fem/MixedLinearVariationalSolver.cpp"
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp: In member 
> function ‘void 
> dolfin::MixedLinearVariationalSolver::solve(dolfin::MixedLinearVariationalSolver::assembled_system_type)’:
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:240:23: error: 
> variable ‘dolfin::PETScNestMatrix A’ has initializer but incomplete type
>   240 |   PETScNestMatrix A(As);
>   |   ^
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:281:5: error: 
> ‘PETScLUSolver’ was not declared in this scope
>   281 | PETScLUSolver solver(comm, solver_type);
>   | ^
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:285:5: error: 
> ‘solver’ was not declared in this scope; did you mean ‘solve’?
>   285 | solver.set_operator(A);
>   | ^~
>   | solve
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:290:5: error: 
> ‘PETScKrylovSolver’ was not declared in this scope
>   290 | PETScKrylovSolver solver(comm, solver_type, pc_type);
>   | ^
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:291:5: error: 
> ‘solver’ was not declared in this scope; did you mean ‘solve’?
>   291 | solver.parameters.update(parameters("krylov_solver"));
>   | ^~
>   | solve
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:303:13: error: 
> ‘PETScVector’ was not declared in this scope
>   303 | as_type(u)->update_ghost_values();
>   | ^~~
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:303:27: error: 
> no matching function for call to ‘as_type< 
> >(std::shared_ptr&)’
>   303 | as_type(u)->update_ghost_values();
>   |   ^
> In file included from /<>/dolfin/la/GenericTensor.h:38,
>  from /<>/dolfin/la/GenericMatrix.h:34,
>  from 
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:27:
> /<>/dolfin/la/LinearAlgebraObject.h:64:8: note: candidate: 
> ‘template Y& dolfin::as_type(X&)’
>64 | Y& as_type(X& x)
>   |^~~
> /<>/dolfin/la/LinearAlgebraObject.h:64:8: note:   template 
> argument deduction/substitution failed:
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:303:27: error: 
> template argument 1 is invalid
>   303 | as_type(u)->update_ghost_values();
>   |   ^
> In file included from /<>/dolfin/la/GenericTensor.h:38,
>  from /<>/dolfin/la/GenericMatrix.h:34,
>  from 
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:27:
> /<>/dolfin/la/LinearAlgebraObject.h:84:24: note: candidate: 
> ‘template std::shared_ptr<_Tp> 
> dolfin::as_type(std::shared_ptr<_Tp>)’
>84 | std::shared_ptr as_type(std::shared_ptr x)
>   |^~~
> /<>/dolfin/la/LinearAlgebraObject.h:84:24: note:   

Processed: closing 957881

[Debian Bug Tracking System]

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

> close 957881 0.2.2-2
Bug #957881 [src:tpm2-initramfs-tool] tpm2-initramfs-tool: ftbfs with GCC-10
Marked as fixed in versions tpm2-initramfs-tool/0.2.2-2.
Bug #957881 [src:tpm2-initramfs-tool] tpm2-initramfs-tool: ftbfs with GCC-10
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#976574: marked as done (libraw1394: FTBFS: latex errors)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 23:46:30 +0100
with message-id 
and subject line Build failure solved
has caused the Debian Bug report #976574,
regarding libraw1394: FTBFS: latex errors
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.)


-- 
976574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libraw1394
Version: 2.1.2-2
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> db2pdf libraw1394.sgml
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
> Working on: /<>/doc/libraw1394.sgml
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/print/dbttlpg.dsl:2722:6:E:
>  flow object not accepted by port; only display flow objects accepted
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
> (preloaded format=pdfjadetex)
>  restricted \write18 enabled.
> entering extended mode
> (/<>/doc/libraw1394.tex
> JadeTeX 2003/04/27: 3.13
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1ptm.fd)
> Elements will be labelled
> Jade begin document sequence at 20
> No file libraw1394.aux.
> (/usr/share/texmf/tex/latex/tipa/t3ptm.fd)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1phv.fd) 
> [1.0.42{/var/lib/texm
> f/fonts/map/pdftex/updmap/pdftex.map}]
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1ptm.fd) [2.0.42]
> 
> Package Fancyhdr Warning: \fancyfoot's `E' option without twoside option is 
> use
> less on input line 217.
> 
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.258 {0:introduction}}
>\Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.264 ...}}Introduction\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.268 {0:introduction}}
>\Seq%
> 
> LaTeX Warning: Reference `0:introduction' on page iii undefined on input line 
> 2
> 74.
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.274 {0:introduction}}\endNode{}\endSeq{}\endLink
>   {}\endSeq{}\endPar{}\Par%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.292 {0:intro1394}}
> \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.298 ...into IEEE 1394\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.302 {0:intro1394}}
> \Seq%
> 
> LaTeX Warning: Reference `0:intro1394' on page iii undefined on input line 
> 308.
> 
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.308 {0:intro1394}}\endNode{}\endSeq{}\endLink
>{}\endSeq{}\endPar{}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.318 {0:24}}
>  \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.324 ...}Bus Structure\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.328 {0:24}}
>  \Seq%
> 
> LaTeX Warning: Reference `0:24' on page iii undefined on input line 334.
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.334 {0:24}}\endNode{}\endSeq{}\endLink
> {}\endSeq{}\endPar{}\Par%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.343 {0:39}}
>  \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   

Bug#976547: marked as done (opensp: FTBFS: latex errors)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 23:40:10 +0100
with message-id <5654522a-a0fd-0991-52d1-36763c9b0...@web.de>
and subject line Build failure solved
has caused the Debian Bug report #976547,
regarding opensp: FTBFS: latex errors
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.)


-- 
976547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opensp
Version: 1.5.2-13
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[4]: Entering directory '/<>/docsrc'
> /usr/bin/xmlto html-nochunks ./releasenotes.xml
> /usr/bin/openjade -o releasenotes.tex -v -t tex -V tex-backend -V '(define 
> %openjade-logo% "./logo.png")' -d ./releasenotes.dsl#print ../pubtext/xml.dcl 
> ./releasenotes.xml
> /usr/bin/openjade:I: "OpenJade" version "1.4devel"
> /usr/bin/openjade:I: "OpenSP" version "1.5.2"
> /usr/bin/pdfjadetex releasenotes.tex
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
> (preloaded format=pdfjadetex)
>  restricted \write18 enabled.
> entering extended mode
> (./releasenotes.tex
> JadeTeX 2003/04/27: 3.13
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1ptm.fd)
> Elements will be labelled
> Jade begin document sequence at 20
> No file releasenotes.aux.
> (/usr/share/texmf/tex/latex/tipa/t3ptm.fd)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1ppl.fd) 
> [1.0.38{/var/lib/texm
> f/fonts/map/pdftex/updmap/pdftex.map} <./logo.png (PNG copy)>]
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1ptm.fd) [2.0.38]
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1phv.fd)
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.296 {0:12}}
>  \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.300 ... Release Notes\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.304 {0:12}}
>  \Seq%
> 
> LaTeX Warning: Reference `0:12' on page iii undefined on input line 310.
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.310 {0:12}}\endNode{}\endSeq{}\endLink
> {}\endSeq{}\endPar{}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.320 {0:17}}
>  \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.324 ...ions of OpenSP\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.328 {0:17}}
>  \Seq%
> 
> LaTeX Warning: Reference `0:17' on page iii undefined on input line 334.
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.334 {0:17}}\endNode{}\endSeq{}\endLink
> {}\endSeq{}\endPar{}\Par%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.343 {0:22}}
>  \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.347 ...taining OpenSP\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.351 {0:22}}
>  \Seq%
> 
> LaTeX Warning: Reference `0:22' on page iii undefined on input line 357.
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.357 {0:22}}\endNode{}\endSeq{}\endLink
> {}\endSeq{}\endPar{}\Par%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.366 {0:27}}
>  \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.370 ...rted Platforms\endNode{}\endSeq{}\endLink

Bug#976538: marked as done (gitmagic: FTBFS: latex errors)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 23:36:07 +0100
with message-id 
and subject line Build failure solved
has caused the Debian Bug report #976538,
regarding gitmagic: FTBFS: latex errors
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.)


-- 
976538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitmagic
Version: 20160304-1.2
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> # Concatenate the text files and feed to AsciiDoc.
> # If a file has not yet been translated for the target language,
> # then substitute the English version.
> # Kludge to support any translation of "Preface".
> echo '[specialsections]' > conf ; \
> if [ en != ru ]; then \
> sed -n '/^== .* ==$/p' en/preface.txt | sed 's/^== \(.*\) ==$/^\1$=preface/' 
> >> conf ; \
> else \
> cp lang-ru.conf conf ; fi ; \
> ( for FILE in en/preface.txt en/intro.txt en/basic.txt en/clone.txt 
> en/branch.txt en/history.txt en/multiplayer.txt en/grandmaster.txt 
> en/secrets.txt en/drawbacks.txt en/translate.txt ; do if [ -f $FILE ]; then 
> cat $FILE; else \
> cat en/$(basename $FILE); fi; echo ; done ) | \
> asciidoc -a lang=en -d book -b docbook -f conf - > book-en.xml
> xmlto -m custom-html.xsl -o book-en html book-en.xml
> Writing pr01.html for preface(_preface)
> Writing ch01.html for chapter(_introduction)
> Writing ch02.html for chapter(_basic_tricks)
> Writing ch03.html for chapter(_cloning_around)
> Writing ch04.html for chapter(_branch_wizardry)
> Writing ch05.html for chapter(_lessons_of_history)
> Writing ch06.html for chapter(_multiplayer_git)
> Writing ch07.html for chapter(_git_grandmastery)
> Writing ch08.html for chapter(_secrets_revealed)
> Writing apa.html for appendix(_git_shortcomings)
> Writing apb.html for appendix(_translating_this_guide)
> Writing index.html for book
> sed -i'' -e 's/xmlns:fo[^ ]*//g' book-en/*.html
> sed -i -e 's| -e 's|#_|#|g' book-en/*.html
> ls book-en/*.html | xargs -n 1 tidy -utf8 -m -i -q
> ./makeover en
> sed -i -e 's|book\.html|../gitmagic.html|g' -e 
> 's|book\.pdf|../gitmagic.pdf|g' book-en/index.html
> xmlto -m custom-nochunks.xsl html-nochunks book-en.xml
> tidy -utf8 -imq book-en.html
> if [ en = zh_cn -o en = zh_tw ]; then \
>   if ! [ -f fop-en.xsl ]; then wget -q 
> http://bestrecords.net/fop/fop-en.xsl; fi; \
>   if ! [ -f fop-en.xconf ]; then wget -q 
> http://bestrecords.net/fop/fop-en.xconf; fi; \
>   xmlto -m fop-en.xsl --with-fop -p "-c `pwd`/fop-en.xconf" pdf 
> book-en.xml ;\
> elif [ en = vi ] ; then \
>   xsltproc --encoding utf-8 fop-vi.xsl book-en.xml > book-en.fo; \
>   fop -c fop-vi.xconf -fo book-en.fo -pdf book-en.pdf; \
> else \
>   SP_ENCODING="XML" docbook2pdf book-en.xml; \
> fi
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
> Working on: /<>/book-en.xml
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
> (preloaded format=pdfjadetex)
>  restricted \write18 enabled.
> entering extended mode
> (/<>/book-en.tex
> JadeTeX 2003/04/27: 3.13
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1ptm.fd)
> Elements will be labelled
> Jade begin document sequence at 20
> No file book-en.aux.
> (/usr/share/texmf/tex/latex/tipa/t3ptm.fd)
> (/usr/share/texlive/texmf-dist/tex/latex/cyrillic/t2acmr.fd)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1phv.fd) 
> [1.0.43{/var/lib/texm
> f/fonts/map/pdftex/updmap/pdftex.map}] [2.0.43]
> 
> Package Fancyhdr Warning: \fancyfoot's `E' option without twoside option is 
> use
> less on input line 277.
> 
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.318 {0:_preface}}
>\Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.322 ...-mode}}Preface\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.326 {0:_preface}}
>\Seq%
> 
> LaTeX Warning: Reference `0:_preface' on page iii undefined on input line 332.
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   

Bug#976519: marked as done (tig: FTBFS: latex errors)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 23:33:07 +0100
with message-id <6de78d5f-6ad6-83af-8c49-13ceb9e9e...@web.de>
and subject line Build failure solved
has caused the Debian Bug report #976519,
regarding tig: FTBFS: latex errors
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.)


-- 
976519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tig
Version: 2.4.1-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> CC  src/tig.o
> CC  src/types.o
> CC  src/string.o
> CC  src/util.o
> CC  src/map.o
> CC  src/argv.o
> CC  src/io.o
> In file included from /usr/include/string.h:495,
>  from include/tig/tig.h:46,
>  from src/io.c:14:
> In function ‘strncpy’,
> inlined from ‘encoding_open’ at src/io.c:52:2:
> /usr/include/aarch64-linux-gnu/bits/string_fortified.h:106:10: warning: 
> ‘__builtin_strncpy’ output truncated before terminating nul copying as many 
> bytes from a string as its length [-Wstringop-truncation]
>   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos 
> (__dest));
>   |  
> ^~
> src/io.c: In function ‘encoding_open’:
> src/io.c:41:15: note: length computed here
>41 |  size_t len = strlen(fromcode);
>   |   ^~~~
> In file included from /usr/include/string.h:495,
>  from include/tig/tig.h:46,
>  from src/io.c:14:
> In function ‘strncpy’,
> inlined from ‘io_from_string’ at src/io.c:649:2:
> /usr/include/aarch64-linux-gnu/bits/string_fortified.h:106:10: warning: 
> ‘__builtin_strncpy’ output truncated before terminating nul copying as many 
> bytes from a string as its length [-Wstringop-truncation]
>   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos 
> (__dest));
>   |  
> ^~
> src/io.c: In function ‘io_from_string’:
> src/io.c:639:15: note: length computed here
>   639 |  size_t len = strlen(str);
>   |   ^~~
> CC  src/refdb.o
>GEN  src/builtin-config.c
> CC  src/builtin-config.o
> CC  src/request.o
> CC  src/line.o
> CC  src/keys.o
> CC  src/repo.o
> CC  src/options.o
> CC  src/draw.o
> CC  src/prompt.o
> CC  src/display.o
> src/display.c: In function ‘update_status_window’:
> src/display.c:474:4: warning: ‘vwprintw’ is deprecated 
> [-Wdeprecated-declarations]
>   474 |vwprintw(status_win, msg, args);
>   |^~~~
> In file included from include/tig/tig.h:77,
>  from src/display.c:14:
> /usr/include/curses.h:776:28: note: declared here
>   776 | extern NCURSES_EXPORT(int) vwprintw (WINDOW *, const char *,va_list) 
> GCC_DEPRECATED(use vw_printw); /* implemented */
>   |^~~~
> CC  src/view.o
> CC  src/search.o
> CC  src/parse.o
> In file included from /usr/include/string.h:495,
>  from include/tig/tig.h:46,
>  from src/parse.c:14:
> In function ‘strncpy’,
> inlined from ‘get_path’ at src/parse.c:264:3:
> /usr/include/aarch64-linux-gnu/bits/string_fortified.h:106:10: warning: 
> ‘__builtin_strncpy’ output truncated before terminating nul copying as many 
> bytes from a string as its length [-Wstringop-truncation]
>   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos 
> (__dest));
>   |  
> ^~
> src/parse.c: In function ‘get_path’:
> src/parse.c:264:3: note: length computed here
>   264 |   strncpy(entry->path, path, strlen(path));
>   |   ^~~~
> CC  src/watch.o
> CC  src/pager.o
> CC  src/log.o
> CC  src/diff.o
> CC  src/help.o
> CC  src/tree.o
> In file included from /usr/include/string.h:495,
>  from include/tig/tig.h:46,
>  from include/tig/util.h:17,
>  from src/tree.c:14:
> In function ‘strncpy’,
> inlined from ‘tree_entry’ at src/tree.c:132:2:
> 

Processed: Re: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #975696 [src:link-grammar] link-grammar: multi-thread test fails
Severity set to 'important' from 'serious'

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

Bug#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

[Jonas Smedegaard]

Control: severity -1 important

Quoting Graham Inggs (2020-12-29 20:35:03)
> The build of link-grammar/5.8.0-3 has already failed on ppc64el [1] 
> (details below).
> 
> As fun as it is, please let's avoid the BTS sports and leave this bug 
> open until link-grammar builds and passes its autopkgtests reliably.

I closed the bugreport when in -3 I optimistally expected the test 
failures to be gone.  I agree this bug should stay open when that's not 
the case.

I disagree, however, that the current level of flakiness renders the 
package unsuitable for a stable Debian release.

Please do clarify if you think that my reasoning is wrong.


 - Jonas


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

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

signature.asc
Description: signature

Bug#976508: marked as done (muttprint: FTBFS: latex errors)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 23:24:44 +0100
with message-id <0417693c-1024-71d0-08e8-fa7cf0a0b...@web.de>
and subject line Build failure solved
has caused the Debian Bug report #976508,
regarding muttprint: FTBFS: latex errors
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.)


-- 
976508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: muttprint
Version: 0.73-8
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc/manual/de'
> sed -e 's,##DOCDIR##,/usr/share/doc/muttprint,g' -e 
> 's,##SHAREDIR##,/usr/share,g' -e 's,##BINDIR##,/usr/bin,g' -e 
> 's,##SYSCONFDIR##,/etc,g' -e 's,##TEMPDIR##,/tmp,g' -e 
> 's,##LIBDIR##,/usr/lib,g' < ./manual-de.sgml > manual-de-sed.sgml
> db2pdf -d ../stylesheet.dsl manual-de-sed.sgml
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /<>/doc/manual/de/../stylesheet.dsl
> Working on: /<>/doc/manual/de/manual-de-sed.sgml
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
> (preloaded format=pdfjadetex)
>  restricted \write18 enabled.
> entering extended mode
> (/<>/doc/manual/de/manual-de-sed.tex
> JadeTeX 2003/04/27: 3.13
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1ptm.fd)
> Elements will be labelled
> Jade begin document sequence at 20
> No file manual-de-sed.aux.
> (/usr/share/texmf/tex/latex/tipa/t3ptm.fd)
> 
> Package Fancyhdr Warning: \fancyfoot's `E' option without twoside option is 
> use
> less on input line 109.
> 
> 
> Package Fancyhdr Warning: \fancyhead's `E' option without twoside option is 
> use
> less on input line 109.
> 
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1phv.fd)
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.223 {0:UEBER}}
> \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.229 ...}ber Muttprint\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.233 {0:UEBER}}
> \Seq%
> 
> LaTeX Warning: Reference `0:UEBER' on page 1 undefined on input line 239.
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.239 {0:UEBER}}\endNode{}\endSeq{}\endLink
>{}\endSeq{}\endPar{}\Par%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.257 {0:INSTALLATION}}
>\Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.263 ...}}Installation\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.267 {0:INSTALLATION}}
>\Seq%
> 
> LaTeX Warning: Reference `0:INSTALLATION' on page 1 undefined on input line 
> 273
> .
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.273 {0:INSTALLATION}}\endNode{}\endSeq{}\endLink
>   {}\endSeq{}\endPar{}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.283 {0:SYSREQ}}
>  \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.289 ...oraussetzungen\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.293 {0:SYSREQ}}
>  \Seq%
> 
> LaTeX Warning: Reference `0:SYSREQ' on page 1 undefined on input line 299.
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.299 {0:SYSREQ}}\endNode{}\endSeq{}\endLink
> {}\endSeq{}\endPar{}\Par%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   

Bug#978662: apertium-cy-en: autopkgtest failure

[Tino Didriksen]

This is a chicken-and-egg problem that should solve itself. New apertium
3.7.1 can't migrate until apertium-cy-en is fixed, but fixed apertium-cy-en
won't build correctly with existing apertium 3.6.1.

-- Tino Didriksen

Processed: reopening 874907

[Debian Bug Tracking System]

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

> reopen 874907
Bug #874907 {Done: Debian FTP Masters } 
[src:hydrogen] [hydrogen] Future Qt4 removal from Buster
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.9.7-6+rm.
> thanks
Stopping processing here.

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

Processed: unarchiving 874907

[Debian Bug Tracking System]

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

> unarchive 874907
Bug #874907 {Done: Debian FTP Masters } 
[src:hydrogen] [hydrogen] Future Qt4 removal from Buster
Unarchived Bug 874907
> thanks
Stopping processing here.

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

Bug#978366: marked as done (xracer: FTBFS: configure:13143: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?))

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 21:20:26 +
with message-id 
and subject line Bug#978366: fixed in xracer 0.96.9.1-11
has caused the Debian Bug report #978366,
regarding xracer: FTBFS: configure:13143: error: possibly undefined macro: 
AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?)
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.)


-- 
978366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xracer
Version: 0.96.9.1-10
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 '/<>'
> ln -sf /usr/share/gettext/config.rpath ./xracer-0.96.9
> cd xracer-0.96.9 && libtoolize -f -c
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: You should add the contents of the following files to 
> 'aclocal.m4':
> libtoolize:   '/usr/share/aclocal/libtool.m4'
> libtoolize:   '/usr/share/aclocal/ltoptions.m4'
> libtoolize:   '/usr/share/aclocal/ltsugar.m4'
> libtoolize:   '/usr/share/aclocal/ltversion.m4'
> libtoolize:   '/usr/share/aclocal/lt~obsolete.m4'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.in,
> libtoolize: and rerunning libtoolize and aclocal.
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> cd xracer-0.96.9 && autoreconf -fi
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.in:37: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from...
> configure.in:37: the top level
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.in:37: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> aclocal.m4:77: AM_GNU_GETTEXT is expanded from...
> configure.in:37: the top level
> autoreconf: configure.in: AM_GNU_GETTEXT is used, but not 
> AM_GNU_GETTEXT_VERSION
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.in,
> libtoolize: and rerunning libtoolize and aclocal.
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> configure.in:37: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from...
> configure.in:37: the top level
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.in:37: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> aclocal.m4:77: AM_GNU_GETTEXT is expanded from...
> configure.in:37: the top level
> configure:13143: error: possibly undefined macro: AM_INTL_SUBDIR
>   If this token and others are legitimate, please use m4_pattern_allow.
>   See the Autoconf documentation.
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> make[1]: *** [debian/rules:23: override_dh_auto_configure] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/xracer_0.96.9.1-10_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: xracer
Source-Version: 0.96.9.1-11
Done: Ying-Chun Liu (PaulLiu) 

We believe that the bug you reported is fixed in the latest version of
xracer, 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 978...@bugs.debian.org,
and the 

Processed: block 954420 with 977121

[Debian Bug Tracking System]

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

> block 954420 with 977121
Bug #954420 [debdelta] Python deprecation warning
Bug #962203 [debdelta] DeprecationWarning: isAlive() is deprecated, use 
is_alive() instead
954420 was not blocked by any bugs.
954420 was not blocking any bugs.
Added blocking bug(s) of 954420: 977121
962203 was not blocked by any bugs.
962203 was not blocking any bugs.
Added blocking bug(s) of 962203: 977121
> thanks
Stopping processing here.

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

Processed: tagging 975160

[Debian Bug Tracking System]

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

> tags 975160 + patch
Bug #975160 [src:librecad] librecad: FTBFS: 
lib/engine/lc_splinepoints.cpp:1564:23: error: invalid use of incomplete type 
‘class QPainterPath’
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#978670: xserver-xorg-video-ati: FTBFS on mips64el, mipsel

[Ivo De Decker]

package: src:xserver-xorg-video-ati
version: 1:19.1.0-2
severity: serious
tags: ftbfs

Hi,

The latest upload of xserver-xorg-video-ati to unstable fails on mips64el, 
mipsel:

https://buildd.debian.org/status/package.php?p=xserver-xorg-video-ati

Cheers,

Ivo

Bug#971018: libgnatcoll-db: FTBFS on mips(64)el with assembler message: branch out of range

[plugwash]

tags 971018 +patch
thanks

I did some testing on the porterbox, which showed optimizing for size is 
enough to make things build on mipsel.


Debdiff attached, no intent to NMU.

diff -Nru libgnatcoll-db-21.0.0/debian/changelog 
libgnatcoll-db-21.0.0/debian/changelog
--- libgnatcoll-db-21.0.0/debian/changelog  2020-12-22 22:35:21.0 
+
+++ libgnatcoll-db-21.0.0/debian/changelog  2020-12-29 13:27:55.0 
+
@@ -1,3 +1,10 @@
+libgnatcoll-db (21.0.0-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use -Os on mipsel, to work around jump length error (Closes: 971018).
+
+ -- Peter Michael Green   Tue, 29 Dec 2020 13:27:55 +
+
 libgnatcoll-db (21.0.0-5) unstable; urgency=medium
 
   [ Adrian Bunk  ]
diff -Nru libgnatcoll-db-21.0.0/debian/rules libgnatcoll-db-21.0.0/debian/rules
--- libgnatcoll-db-21.0.0/debian/rules  2020-11-17 18:33:55.0 +
+++ libgnatcoll-db-21.0.0/debian/rules  2020-12-29 13:27:55.0 +
@@ -34,6 +34,11 @@
   DEB_CFLAGS_MAINT_APPEND := -mxgot
 endif
 
+# Use -Os on mipsel to workaround further jump length issues
+ifneq (,$(filter mipsel,$(DEB_HOST_ARCH)))
+  DEB_CFLAGS_MAINT_APPEND += -Os
+endif
+
 include /usr/share/dpkg/buildflags.mk
 include $(wildcard /usr/share/ada/debian_packaging-$(GNAT_VERSION).mk)
 # wildcard means: not during -indep builds.

Processed: libgnatcoll-db: FTBFS on mips(64)el with assembler message: branch out of range

[Debian Bug Tracking System]

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

> tags 971018 +patch
Bug #971018 [src:libgnatcoll-db] libgnatcoll-db: FTBFS on mips(64)el with 
assembler message: branch out of range
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#978667: libv4l-dev: ioctl(rfd, VIDIOC_QBUF, ) fails

[william]

Package: libv4l-dev
Version: 1.16.3-3
Severity: serious
Justification: Policy 2.5 - important - Unix is a multi-port operating system

Dear Maintainer,


   * What led up to the situation?
 Attempted to open access to a second device (camera)
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 wrote the attached program which minimally opens the stream from the second 
camera
   * What was the outcome of this action?
 The program reportes that although the first camera was accessible, identical 
code opening a stream for a second camera was not successful
   * What outcome did you expect instead?
 Expected ioctl to return r==0, indicating successful system call


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

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

Versions of packages libv4l-dev depends on:
ii  libv4l-01.16.3-3
ii  libv4l2rds0 1.16.3-3
ii  libv4lconvert0  1.16.3-3

libv4l-dev recommends no packages.

Versions of packages libv4l-dev suggests:
ii  pkg-config  0.29-6

-- no debconf information

Bug#976475: marked as done (shared-mime-info: FTBFS: latex errors)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 21:52:49 +0100
with message-id 
and subject line Build failure solved
has caused the Debian Bug report #976475,
regarding shared-mime-info: FTBFS: latex errors
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.)


-- 
976475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shared-mime-info
Version: 2.0-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> docbook2pdf -o data data/shared-mime-info-spec.xml
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
> Working on: /<>/data/shared-mime-info-spec.xml
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
> (preloaded format=pdfjadetex)
>  restricted \write18 enabled.
> entering extended mode
> 
> (/<>/data/shared-mime-info-spec
> .tex
> JadeTeX 2003/04/27: 3.13
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1ptm.fd)
> Elements will be labelled
> Jade begin document sequence at 20
> No file shared-mime-info-spec.aux.
> (/usr/share/texmf/tex/latex/tipa/t3ptm.fd)
> 
> Package Fancyhdr Warning: \fancyfoot's `E' option without twoside option is 
> use
> less on input line 109.
> 
> 
> Package Fancyhdr Warning: \fancyhead's `E' option without twoside option is 
> use
> less on input line 109.
> 
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1phv.fd)
> 
> Package Fancyhdr Warning: \fancyfoot's `E' option without twoside option is 
> use
> less on input line 548.
> 
> [1.0.42{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1ptm.fd)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd) [2.0.42] [3.0.42]
> Overfull \hbox (1.59798pt too wide) in alignment at lines 1824--1884
>  [] [] [] 
> 
> Overfull \hbox (1.59798pt too wide) in alignment at lines 1884--2169
>  [] [] [] 
> [4.0.42]
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.2327 {0:subclassing}}
>\Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.2329 {}2.11\endSeq{}\endSeq{}\endLink
>
> {}\endNode{}.\endSeq{}\endNode{}\endP...
> 
> [5.0.42]
> Overfull \hbox (1.59798pt too wide) in alignment at lines 2716--2776
>  [] [] [] 
> 
> Overfull \hbox (1.59798pt too wide) in alignment at lines 2776--3163
>  [] [] [] 
> [6.0.42] (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsa.fd)
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsb.fd)
> (/usr/share/texlive/texmf-dist/tex/latex/wasysym/uwasy.fd)
> Overfull \hbox (76.79944pt too wide) in paragraph at lines 3411--3411
>  []\T1/pcr/m/n/9  xmlns="http://www.freedesktop.org/standards/shared-
> mime-info" type="text/x-diff">[] 
> [7.0.42] [8.0.42] [9.0.42]
> Overfull \hbox (1.59998pt too wide) in alignment at lines 4008--4068
>  [] [] [] 
> 
> Overfull \hbox (1.59998pt too wide) in alignment at lines 4068--4419
>  [] [] [] 
> [10.0.42]
> Overfull \hbox (1.19952pt too wide) in paragraph at lines 4567--4567
>  []\T1/pcr/m/n/9   4d 49 4d 45 2d 4d 61 67  69 63 00 0a 5b 35 30 3a  
> |M
> IME-Magic..[50:|[] 
> 
> Overfull \hbox (1.19952pt too wide) in paragraph at lines 4568--4568
>  []\T1/pcr/m/n/9 0010  74 65 78 74 2f 78 2d 64  69 66 66 5d 0a 3e 30 3d  
> |t
> ext/x-diff].>0=|[] 
> 
> Overfull \hbox (1.19952pt too wide) in paragraph at lines 4569--4569
>  []\T1/pcr/m/n/9 0020  00 05 64 69 66 66 09 0a  3e 30 3d 00 04 2a 2a 2a  
> |.
> .diff..>0=..***|[] 
> 
> Overfull \hbox (1.19952pt too wide) in paragraph at lines 4570--4570
>  []\T1/pcr/m/n/9 0030  09 0a 3e 30 3d 00 17 43  6f 6d 6d 6f 6e 20 73 75  
> |.
> .>0=..Common su|[] 
> [11.0.42]
> Overfull \hbox (1.19998pt too wide) in alignment at lines 5032--5074
>  [] [] 
> 
> Overfull \hbox (1.19998pt too wide) in alignment at lines 5074--5238
>  [] [] 
> [12.0.42] [13.0.42] [14.0.42] [15.0.42] [16.0.42] [17.0.42]
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.6780 {0:s2_layout}}
>  \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.6782 

Bug#978662: apertium-cy-en: autopkgtest failure

[Sebastian Ramacher]

Source: apertium-cy-en
Version: 0.1.1~r57554-5
Severity: serious

apertium-cy-en's autopkgtest in testing currently fails with apertium
from unstable:

autopkgtest [08:11:43]: test runsampletest: [---
Everyone  are born  free. is not equal to Everyone are born free!
autopkgtest [08:11:44]: test runsampletest: ---]
autopkgtest [08:11:44]: test runsampletest:  - - - - - - - - - - results - - - 
- - - - - - -
runsampletestFAIL non-zero exit status 1
autopkgtest [08:11:44]:  summary
runsampletestFAIL non-zero exit status 1

See
https://ci.debian.net/data/autopkgtest/testing/amd64/a/apertium-cy-en/9220240/log.gz

And apertium-cy-en's autopkgtest in unstable also fails with apertium
from testing:

autopkgtest [20:25:40]: test runsampletest: [---
Segmentation fault
 is not equal to Everyone are born free!
autopkgtest [20:25:41]: test runsampletest: ---]
autopkgtest [20:25:41]: test runsampletest:  - - - - - - - - - - results - - - 
- - - - - - -
runsampletestFAIL non-zero exit status 1

See
https://ci.debian.net/data/autopkgtest/testing/amd64/a/apertium-cy-en/9208858/log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: tagging 975166

[Debian Bug Tracking System]

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

> tags 975166 + patch
Bug #975166 [src:connectome-workbench] connectome-workbench: FTBFS: 
qwt_painter_command.h:85:22: error: field ‘clipPath’ has incomplete type 
‘QPainterPath’
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#977604: smarty3: broken internal parsetree code

[Wolfgang Schweer]

[ Mike Gabriel, 2020-12-29 ]
> What is the origin of this patch. Are you the author? How did you get to
> that solution?

Maybe I should have been more verbose.

It isn't a solution and not a patch. These are the changes done to 
smarty_internal_templatecompilerbase.php since the last release, please 
take a look at the timestamps:

diff -u a/smarty_internal_templatecompilerbase.php 
b/smarty_internal_templatecompilerbase.php
--- a/smarty_internal_templatecompilerbase.php  2018-08-31 00:00:00.0 
+0200
+++ b/smarty_internal_templatecompilerbase.php  2020-04-14 00:00:00.0 
+0200

According to the file's upstream history, the diff is due to the last 
two commits concerning smarty_internal_templatecompilerbase.php ( which 
is now causing the GOsa and slbackup-php issues).

Maybe these fixes (for other issues) broke code shipped with GOsa and 
slbackup-php, maybe both the GOsa and slbackup-php code is outdated.

I just wanted to point to something to investigate further...

No idea how to fix it.

Wolfgang



signature.asc
Description: PGP signature

Bug#978366: xracer: FTBFS: configure:13143: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?)

[Ying-Chun Liu (PaulLiu)]

Hi Lucas,


Yes. It is because gettext 0.21


I prepared a patch. Will fix this soon.

Patch as attachment.


Yours,

Paul


Description: Porting to gettext 0.21
 gettext 0.21 doesn't allow to use AM_GNU_GETTEXT without version.
 Also we need to add Makevars file in po subdir.
Bug-Debian: http://bugs.debian.org/978366
Author: Ying-Chun Liu (PaulLiu) 
Last-Update: 2020-12-25
Index: xracer-0.96.9.1/xracer-0.96.9/configure.in
===
--- xracer-0.96.9.1.orig/xracer-0.96.9/configure.in
+++ xracer-0.96.9.1/xracer-0.96.9/configure.in
@@ -34,7 +34,12 @@ dnl Declare available message catalogues
 ALL_LINGUAS="nl sv zh_TW vi ru de ar pt"
 
 dnl Check for internationalization support.
-AM_GNU_GETTEXT
+AM_GNU_GETTEXT_VERSION(0.20)
+AM_GNU_GETTEXT([external])
+DATADIRNAME="share"
+USE_INCLUDED_LIBINTL="no"
+AC_SUBST(DATADIRNAME)
+AC_SUBST(USE_INCLUDED_LIBINTL)
 
 dnl Standard warnings.
 WARNINGS="-Wall -Wpointer-arith -Wmissing-prototypes -Wmissing-declarations -Wcast-align -Wwrite-strings"
Index: xracer-0.96.9.1/xracer-0.96.9/po/Makevars
===
--- /dev/null
+++ xracer-0.96.9.1/xracer-0.96.9/po/Makevars
@@ -0,0 +1,53 @@
+# Makefile variables for PO directory in any package using GNU gettext.
+
+# Usually the message domain is the same as the package name.
+DOMAIN = $(PACKAGE)
+
+# These two variables depend on the location of this directory.
+subdir = po
+top_builddir = ..
+
+# These options get passed to xgettext.
+XGETTEXT_OPTIONS = --keyword=_ --keyword=N_
+
+# This is the copyright holder that gets inserted into the header of the
+# $(DOMAIN).pot file.  Set this to the copyright holder of the surrounding
+# package.  (Note that the msgstr strings, extracted from the package's
+# sources, belong to the copyright holder of the package.)  Translators are
+# expected to transfer the copyright for their translations to this person
+# or entity, or to disclaim their copyright.  The empty string stands for
+# the public domain; in this case the translators are expected to disclaim
+# their copyright.
+COPYRIGHT_HOLDER = Free Software Foundation, Inc.
+
+# This is the email address or URL to which the translators shall report
+# bugs in the untranslated strings:
+# - Strings which are not entire sentences, see the maintainer guidelines
+#   in the GNU gettext documentation, section 'Preparing Strings'.
+# - Strings which use unclear terms or require additional context to be
+#   understood.
+# - Strings which make invalid assumptions about notation of date, time or
+#   money.
+# - Pluralisation problems.
+# - Incorrect English spelling.
+# - Incorrect formatting.
+# It can be your email address, or a mailing list address where translators
+# can write to without being subscribed, or the URL of a web page through
+# which the translators can contact you.
+MSGID_BUGS_ADDRESS =
+
+# This is the list of locale categories, beyond LC_MESSAGES, for which the
+# message catalogs shall be used.  It is usually empty.
+EXTRA_LOCALE_CATEGORIES =
+
+# This tells whether the $(DOMAIN).pot file contains messages with an 'msgctxt'
+# context.  Possible values are "yes" and "no".  Set this to yes if the
+# package uses functions taking also a message context, like pgettext(), or
+# if in $(XGETTEXT_OPTIONS) you define keywords with a context argument.
+USE_MSGCTXT = no
+
+# These options get passed to msgmerge.
+# Useful options are in particular:
+#   --previousto keep previous msgids of translated messages,
+#   --quiet   to reduce the verbosity.
+MSGMERGE_OPTIONS =

Processed: tagging 957293

[Debian Bug Tracking System]

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

> tags 957293 + ftbfs
Bug #957293 [src:gnupg1] gnupg1: ftbfs with GCC-10
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#978657: unknown-horizons: Crash on startup with xml AttributeError "no attribute 'getchildren'"

[Steffen Langenbach]

Package: unknown-horizons
Version: 2019.1-2
Severity: grave
Tags: a11y
Justification: renders package unusable

Hi,

I encountered a problem starting unknown-horizons. I installed from standard
debian testing repository and get the following error:

---
$ unknown-horizons --debug
Logging to b'/home/sal/.local/share/unknown-horizons/log/unknown-
horizons-2020-12-29_20-40-06.log' and /usr/share/unknown-horizons/fife.log
Python version: sys.version_info(major=3, minor=9, micro=1,
releaselevel='final', serial=0)
Platform: Linux-5.9.0-4-amd64-x86_64-with-glibc2.31
SYS.PATH: ['/usr/games', '/usr/lib/python39.zip', '/usr/lib/python3.9',
'/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages',
'/usr/lib/python3/dist-packages']
PATHSEP: ":" SEP: "/"
LD_LIBRARY_PATH: 
PATH:
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/var/lib/flatpak/exports/bin
PYTHONPATH 
Python version: sys.version_info(major=3, minor=9, micro=1,
releaselevel='final', serial=0)
Platform: Linux-5.9.0-4-amd64-x86_64-with-glibc2.31
Using fife version 0.4.2, at least 0.4.2 required
Traceback (most recent call last):
  File "/usr/games/unknown-horizons", line 381, in 
main()
  File "/usr/games/unknown-horizons", line 122, in main
ret = horizons.main.start(options)
  File "/usr/lib/python3/dist-packages/horizons/main.py", line 113, in start
horizons.globals.fife = Fife()
  File "/usr/lib/python3/dist-packages/horizons/engine/engine.py", line 46, in
__init__
self._setting = Settings(PATHS.USER_CONFIG_FILE,
PATHS.SETTINGS_TEMPLATE_FILE)
  File "/usr/lib/python3/dist-packages/horizons/engine/settings.py", line 39,
in __init__
self._settings_serializer.load(settings_file)
  File "/usr/lib/python3/dist-
packages/fife/extensions/serializers/simplexml.py", line 132, in load
self._validateTree()
  File "/usr/lib/python3/dist-
packages/fife/extensions/serializers/simplexml.py", line 386, in _validateTree
for c in self._root_element.getchildren():
AttributeError: 'xml.etree.ElementTree.Element' object has no attribute
'getchildren'

 Unknown Horizons has crashed.

We are very sorry for this and want to fix the underlying error.
In order to do this, we need the information from the logfile:
/home/sal/.local/share/unknown-horizons/log/unknown-
horizons-2020-12-29_20-40-06.log
Please give it to us via IRC or our forum, for both see http://unknown-
horizons.org .
---


I also attached the unknown-horizons log file.

If you need more information just get back on me.

Kind regards
Steffen



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

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

Versions of packages unknown-horizons depends on:
ii  python3 3.9.0-4
ii  python3-enet0.0~vcs.2017.05.26.git-2.2+b2
ii  python3-fife0.4.2-2+b3
ii  python3-future  0.18.2-5
ii  python3-yaml5.3.1-3+b1
ii  ttf-unifont 1:13.0.04-1

unknown-horizons recommends no packages.

unknown-horizons suggests no packages.

-- no debconf information

 Unknown Horizons has crashed.

We are very sorry for this and want to fix the underlying error.
In order to do this, we need the information from the logfile:
/home/sal/.local/share/unknown-horizons/log/unknown-horizons-2020-12-29_20-40-06.log
Please give it to us via IRC or our forum, for both see 
http://unknown-horizons.org .
: ":" SEP: "/"
LD_LIBRARY_PATH: 
PATH: 
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/var/lib/flatpak/exports/bin
PYTHONPATH 
Python version: sys.version_info(major=3, minor=9, micro=1, 
releaselevel='final', serial=0)
Platform: Linux-5.9.0-4-amd64-x86_64-with-glibc2.31
Using fife version 0.4.2, at least 0.4.2 required
Traceback (most recent call last):
  File "/usr/games/unknown-horizons", line 381, in 
main()
  File "/usr/games/unknown-horizons", line 122, in main
ret = horizons.main.start(options)
  File "/usr/lib/python3/dist-packages/horizons/main.py", line 113, in start
horizons.globals.fife = Fife()
  File "/usr/lib/python3/dist-packages/horizons/engine/engine.py", line 46, in 
__init__
self._setting = Settings(PATHS.USER_CONFIG_FILE, 
PATHS.SETTINGS_TEMPLATE_FILE)
  File "/usr/lib/python3/dist-packages/horizons/engine/settings.py", line 39, 
in __init__
self._settings_serializer.load(settings_file)
  File 
"/usr/lib/python3/dist-packages/fife/extensions/serializers/simplexml.py", line 
132, in load
self._validateTree()
  File 
"/usr/lib/python3/dist-packages/fife/extensions/serializers/simplexml.py", line 
386, in _validateTree
for c in self._root_element.getchildren():
AttributeError: 'xml.etree.ElementTree.Element' object has no attribute 
'getchildren'

Bug#977604: smarty3: broken internal parsetree code

[Mike Gabriel]

Hi Wolfgang,

On  Di 29 Dez 2020 12:52:01 CET, Wolfgang Schweer wrote:


After digging into this a bit (w/o having a real clue about PHP and
Smarty), I noticed that it is sufficient to replace one file to make
both Gosa and slbackup-php work; see the comment about variables prior
to PHP 5.5:



[patch]


What is the origin of this patch. Are you the author? How did you get  
to that solution?



Wolfgang


Thanks for investing time into this!
Mike


--

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

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



pgpajEIKu5Fgk.pgp
Description: Digitale PGP-Signatur

Processed: bug 974608 is forwarded to https://gitlab.gnome.org/GNOME/gthumb/-/issues/137

[Debian Bug Tracking System]

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

> forwarded 974608 https://gitlab.gnome.org/GNOME/gthumb/-/issues/137
Bug #974608 [gthumb] gthumb uses internal libexiv2 functions to get the user 
comment
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gthumb/-/issues/137'.
> thanks
Stopping processing here.

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

Bug#976169: marked as done (psi4: autopkgtest regression in testing: ImportError: cannot import name 'core' from partially initialized module 'psi4')

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 21:37:43 +0200
with message-id <20201229193743.GA14007@localhost>
and subject line Re: Bug#976169: psi4: autopkgtest regression in testing: 
ImportError: cannot import name 'core' from partially initialized module 'psi4'
has caused the Debian Bug report #976169,
regarding psi4: autopkgtest regression in testing: ImportError: cannot import 
name 'core' from partially initialized module 'psi4'
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.)


-- 
976169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psi4
Version: 1:1.3.2-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent change in testing (I believe the added support of
Python3.9) the autopkgtest of psi4 started to fail. I copied some of the
output at the bottom of this report. Can you please investigate the
situation and fix it?

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

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/p/psi4/8534048/log.gz

autopkgtest [19:22:54]: test testsuite.sh: [---
Running test simint/scf5... Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 55, in 
from . import core
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/psi4", line 177, in 
import psi4
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 60, in 
raise ImportError("{0}".format(err))
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)
FAILED
LOG:


2020-11-30 19:22
Skipping test gcp/hf3c
Running test python/energy... Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 55, in 
from . import core
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/psi4", line 177, in 
import psi4
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 60, in 
raise ImportError("{0}".format(err))
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)
FAILED
LOG:


2020-11-30 19:22
Skipping test v2rdm_casscf/v2rdm3
Skipping test cfour/sp-rhf-ccsd_t_
Running test sapt1... Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 55, in 
from . import core
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/psi4", line 177, in 
import psi4
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 60, in 
raise ImportError("{0}".format(err))
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)
FAILED
LOG:


2020-11-30 19:22
Skipping test libefp/qchem-qmefp-sp
Skipping test dftd3/energy
Running test erd/scf5... Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 55, in 
from . import core
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/psi4", line 177, in 
import psi4
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 60, in 
raise ImportError("{0}".format(err))
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)
FAILED
LOG:


2020-11-30 19:22
Running test 

Bug#978353: serf: FTBFS: test_ssl_handshake fails with OpenSSL 1.1.1i

[Justin Erenkrantz]

The OpenSSL devs intended this to be a breaking change - but it's not
documented anywhere.  Sigh.

I've got a WIP patch against trunk that causes test_ssl to pass - see
below.  It also seems to work with OpenSSL 1.1.1h as well as OpenSSL 1.1.1i
/ 1.1.1-stable, AFAICT.

James: can you please give it a try as well?

We've been on the threshold of releasing serf 1.4 for quite some time
now...maybe we should just do that...  If this looks reasonable, I'll try
to clean this up and get it into trunk and 1.4.x.

Cheers.  -- justin

Index: test/test_serf.h
===
--- test/test_serf.h (revision 1884847)
+++ test/test_serf.h (working copy)
@@ -296,6 +296,14 @@
 handler_baton_t handler_ctx[],
 apr_pool_t *pool);

+/* Helper function, runs the client and server context loops and validates
+   that errors were encountered.  */
+void
+run_client_and_mock_servers_loops_expect_fail(CuTest *tc, test_baton_t *tb,
+  int num_requests,
+  handler_baton_t
handler_ctx[],
+  apr_pool_t *pool);
+
 /* Logs a test suite error with its code location, and return status
SERF_ERROR_ISSUE_IN_TESTSUITE. */
 #define REPORT_TEST_SUITE_ERROR()\
Index: test/test_ssl.c
===
--- test/test_ssl.c (revision 1884847)
+++ test/test_ssl.c (working copy)
@@ -465,9 +465,10 @@

 tb->result_flags |= TEST_RESULT_SERVERCERTCB_CALLED;

+test__log(TEST_VERBOSE, __FILE__, "Cert failure received: %d ;
expected failure mask: %d\n", failures, expected_failures);
 /* We expect an error from the certificate validation function. */
 if (failures & expected_failures)
-return APR_SUCCESS;
+return APR_EGENERAL;
 else
 return REPORT_TEST_SUITE_ERROR();
 }
@@ -532,8 +533,8 @@

 create_new_request(tb, _ctx[0], "GET", "/", 1);

-run_client_and_mock_servers_loops_expect_ok(tc, tb, num_requests,
-handler_ctx, tb->pool);
+run_client_and_mock_servers_loops_expect_fail(tc, tb, num_requests,
+  handler_ctx, tb->pool);
 }

 /* Validate that connecting to a SSLv2 only server fails. */
@@ -1121,8 +1122,8 @@

 create_new_request(tb, _ctx[0], "GET", "/", 1);

-run_client_and_mock_servers_loops_expect_ok(tc, tb, num_requests,
-handler_ctx, tb->pool);
+run_client_and_mock_servers_loops_expect_fail(tc, tb, num_requests,
+  handler_ctx, tb->pool);
 CuAssertTrue(tc, tb->result_flags & TEST_RESULT_SERVERCERTCB_CALLED);

 }
@@ -1165,8 +1166,8 @@

 create_new_request(tb, _ctx[0], "GET", "/", 1);

-run_client_and_mock_servers_loops_expect_ok(tc, tb, num_requests,
-handler_ctx, tb->pool);
+run_client_and_mock_servers_loops_expect_fail(tc, tb, num_requests,
+  handler_ctx, tb->pool);
 CuAssertTrue(tc, tb->result_flags & TEST_RESULT_SERVERCERTCB_CALLED);
 }

@@ -2095,8 +2096,8 @@

 create_new_request(tb, _ctx[0], "GET", "/", 1);

-run_client_and_mock_servers_loops_expect_ok(tc, tb, num_requests,
-handler_ctx, tb->pool);
+run_client_and_mock_servers_loops_expect_fail(tc, tb, num_requests,
+  handler_ctx, tb->pool);
 CuAssertTrue(tc, tb->result_flags & TEST_RESULT_SERVERCERTCB_CALLED);
 }

@@ -2138,8 +2139,8 @@

 create_new_request(tb, _ctx[0], "GET", "/", 1);

-run_client_and_mock_servers_loops_expect_ok(tc, tb, num_requests,
-handler_ctx, tb->pool);
+run_client_and_mock_servers_loops_expect_fail(tc, tb, num_requests,
+  handler_ctx, tb->pool);
 CuAssertTrue(tc, tb->result_flags & TEST_RESULT_SERVERCERTCB_CALLED);
 }

@@ -2181,8 +2182,8 @@

 create_new_request(tb, _ctx[0], "GET", "/", 1);

-run_client_and_mock_servers_loops_expect_ok(tc, tb, num_requests,
-handler_ctx, tb->pool);
+run_client_and_mock_servers_loops_expect_fail(tc, tb, num_requests,
+  handler_ctx, tb->pool);
 CuAssertTrue(tc, tb->result_flags & TEST_RESULT_SERVERCERTCB_CALLED);
 }

@@ -2310,8 +2311,8 @@

 create_new_request(tb, _ctx[0], "GET", "/", 1);

-run_client_and_mock_servers_loops_expect_ok(tc, tb, num_requests,
-handler_ctx, tb->pool);
+run_client_and_mock_servers_loops_expect_fail(tc, tb, num_requests,
+  

Processed: Re: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #975696 {Done: Jonas Smedegaard } [src:link-grammar] 
link-grammar: multi-thread test fails
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions link-grammar/5.8.0-3.

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

Bug#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

[Graham Inggs]

Control: reopen -1

Hi Jonas

The build of link-grammar/5.8.0-3 has already failed on ppc64el [1]
(details below).

As fun as it is, please let's avoid the BTS sports and leave this bug
open until link-grammar builds and passes its autopkgtests reliably.

Regards
Graham


[1] 
https://buildd.debian.org/status/fetch.php?pkg=link-grammar=ppc64el=5.8.0-3=1609265548=0


FAIL: multi-thread
==

link-grammar: Info: Dictionary found at ../data/en/4.0.dict
link-grammar: Info: Dictionary found at ../data/ru/4.0.dict
link-grammar: Info: ru: Spell checker disabled.
double free or corruption (fasttop)
FAIL multi-thread (exit status: 134)

Bug#978185: marked as done (puppetlabs-http-client-clojure: FTBFS: src/java/com/puppetlabs/http/client/impl/SslUtils.java:36: error: unreported exception NoSuchProviderException; must be caught or dec

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 19:03:49 +
with message-id 
and subject line Bug#978185: fixed in puppetlabs-http-client-clojure 1.2.0-1
has caused the Debian Bug report #978185,
regarding puppetlabs-http-client-clojure: FTBFS: 
src/java/com/puppetlabs/http/client/impl/SslUtils.java:36: error: unreported 
exception NoSuchProviderException; must be caught or declared to be thrown
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.)


-- 
978185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: puppetlabs-http-client-clojure
Version: 0.9.0-1
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 '/<>'
> cat debian/header.html > /<>/CHANGELOG.html
> sed -i'' -e 's#@TITLE@#0.9.0#g' /<>/CHANGELOG.html
> markdown /<>/CHANGELOG.md >> /<>/CHANGELOG.html
> cat debian/footer.html >> /<>/CHANGELOG.html
> cat debian/header.html > /<>/CONTRIBUTING.html
> sed -i'' -e 's#@TITLE@#How to contribute#g' /<>/CONTRIBUTING.html
> markdown /<>/CONTRIBUTING.md >> 
> /<>/CONTRIBUTING.html
> cat debian/footer.html >> /<>/CONTRIBUTING.html
> cat debian/header.html > /<>/README.html
> sed -i'' -e 's#@TITLE@#puppetlabs/http-client#g' /<>/README.html
> markdown /<>/README.md >> /<>/README.html
> cat debian/footer.html >> /<>/README.html
> jh_build --no-javadoc --javacopts="-source 1.7 -target 1.7" 
> puppetlabs-http-client.jar src/java
> warning: [options] bootstrap class path not set in conjunction with -source 7
> src/java/com/puppetlabs/http/client/impl/SslUtils.java:36: error: unreported 
> exception NoSuchProviderException; must be caught or declared to be thrown
> SSLUtils.pemsToSSLContext(
>  ^
> src/java/com/puppetlabs/http/client/impl/SslUtils.java:63: error: unreported 
> exception NoSuchProviderException; must be caught or declared to be thrown
> SSLUtils.caCertPemToSSLContext(
>   ^
> Note: src/java/com/puppetlabs/http/client/impl/JavaClient.java uses or 
> overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> 2 errors
> 1 warning
> jh_build: error: find src/java -name '*.java' -and -type f -print0 | xargs -s 
> 512000 -0 /usr/lib/jvm/default-java/bin/javac -g -cp 
> /usr/share/java/clojure.jar:/usr/share/java/httpasyncclient.jar:/usr/share/java/prismatic-schema.jar:/usr/share/java/commons-io.jar:/usr/share/java/metrics-core.jar:/usr/share/java/ssl-utils.jar:/usr/share/java/puppetlabs-i18n.jar:/usr/share/java/httpclient.jar:/usr/share/java/httpcore.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/httpcore-nio.jar:debian/_jh_build.puppetlabs-http-client
>  -d debian/_jh_build.puppetlabs-http-client -source 1.7 -target 1.7 -encoding 
> ISO8859-1  returned exit code 123
> make[1]: *** [debian/rules:15: override_jh_build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/12/26/puppetlabs-http-client-clojure_0.9.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: puppetlabs-http-client-clojure
Source-Version: 1.2.0-1
Done: =?utf-8?q?Louis-Philippe_V=C3=A9ronneau?= 

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

Debian distribution maintenance software
pp.
Louis-Philippe Véronneau  (supplier of 

Processed: notfixed 972134 in debian-design/3.0.21

[Debian Bug Tracking System]

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

> notfixed 972134 debian-design/3.0.21
Bug #972134 [chromium] chromium: please, consider moving the package to 
team-maintainance to properly maintain it
Ignoring request to alter fixed versions of bug #972134 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reopening 972134

[Debian Bug Tracking System]

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

> reopen 972134
Bug #972134 {Done: Jonas Smedegaard } [chromium] chromium: 
please, consider moving the package to team-maintainance to properly maintain it
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions debian-design/3.0.21.
> thanks
Stopping processing here.

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

Bug#976292: marked as done (design-desktop-web: drop chromium as Depends)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 19:56:09 +0100
with message-id <160926816990.3680396.14183481154669966...@auryn.jones.dk>
and subject line Re: Bug#976292: design-desktop-web: drop chromium as Depends
has caused the Debian Bug report #976292,
regarding design-desktop-web: drop chromium as Depends
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.)


-- 
976292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: design-desktop-web
Version: 3.0.20
Severity: serious
Justification: chromium removal

Hi Jonas,

With my Release Team member hat on, please drop chromium from the list
of Depends of design-desktop-web. The reason I'm asking is that we want
to remove chromium from bullseye because it's currently in a bad shape
and your package Depends on it, so either has to go too or should drop
the Depends.

Paul



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 3.0.21

Quoting Paul Gevers (2020-12-02 22:16:28)
> With my Release Team member hat on, please drop chromium from the list 
> of Depends of design-desktop-web. The reason I'm asking is that we 
> want to remove chromium from bullseye because it's currently in a bad 
> shape and your package Depends on it, so either has to go too or 
> should drop the Depends.

Fixed now.  Thanks!

 - Jonas

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

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

signature.asc
Description: signature
--- End Message ---

Bug#978471: waybar fails to launch

[Shengjing Zhu]

On Wed, Dec 30, 2020 at 2:39 AM Shengjing Zhu  wrote:
> Follow Sebastian's advice, please see the following patch.

Having one typo, so creating a MR
https://salsa.debian.org/med-team/spdlog/-/merge_requests/3

-- 
Shengjing Zhu

Bug#976891: [Android-tools-devel] Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

[Hans-Christoph Steiner]

Hans-Christoph Steiner:

It looks like the clean build stops before the error you reported:

https://salsa.debian.org/eighthave/android-platform-art/-/jobs/1291335

In file included from runtime/runtime.cc:53:
runtime/asm_support.h:24:10: fatal error: 'asm_defines.h' file not found
#include "asm_defines.h"
  ^~~
1 error generated.
make[2]: *** [debian/libart.mk:473: runtime/runtime.o] Error 1

My guess is that the Makefile dependency rules are wrong, since the 
target that builds asm_defines.h works fine when manually run.


If you use your own fork, and force-push commits to your fork's master 
branch, it'll run the CI jobs, which are totally clean builds each time.


Ok, I fixed the dependency issue, now it gets reliably to the point rosh 
gets to:


https://salsa.debian.org/eighthave/android-platform-art/-/jobs/1291535

.hc

Bug#978471: waybar fails to launch

[Shengjing Zhu]

Hi,

On Tue, Dec 29, 2020 at 07:10:23PM +0100, Sebastian Ramacher wrote:
> On 2020-12-29 22:01:15, Andrey Rahmatullin wrote:
> > Control: reassign -1 libspdlog1/1:1.8.1+ds-2+b1
> > Control: affects -1 waybar
> > Control: severity -1 serious
> > Control: retitle -1 libspdlog1 breaks ABI on rebuilds with different libfmt
> > 
> > On Sun, Dec 27, 2020 at 09:26:09PM +0100, Michele Cane wrote:
> > > waybar: symbol lookup error: waybar: undefined symbol: 
> > > _ZN6spdlog7details7log_msgC1ENS_10source_locEN3fmt2v617basic_string_viewIcEENS_5level10level_enumES6_
> > This is because libspdlog1 was rebuilt with newer libfmt and this caused
> > symbol renames.
> > 
> > #977454 says "The code is actually working with the new version, only the
> > symbols file is wrong here. spdlog uses fmtlib internal API and exposes it
> > through the symbols files. This looks wrong to me, as every new fmtlib
> > will cause spdlog ftbfs due to the symbols file.". If it's about the same
> > problem then it looks like it failed to mention that symbol changes cause
> > much worse problems than just needing to update the symbols file.
> 
> The situtation is somewhat similar to liboost-regex and libicu.
> libboost-regex exports symbols that depend on libicu's ABI and change
> whenever liboost-regex is rebuilt against a version of libicu with a
> different ABI.
> 
> For spdlog this can be solved in the same way as for boost.
> liboost-regexX.Y provides libboost-regexX.Y-icuZ when built against
> libicuZ. Reverse dependencies then depend on libboost-regexX.Y-icuZ. See
> 
> https://salsa.debian.org/debian/boost/-/blob/master/debian/rules#L53
> https://salsa.debian.org/debian/boost/-/blob/master/debian/rules#L289
> https://salsa.debian.org/debian/boost/-/blob/master/debian/rules#L338
> 
> Cheers
> -- 
> Sebastian Ramacher

Follow Sebastian's advice, please see the following patch.
diff --git a/debian/changelog b/debian/changelog
index 1d31b26..f4b7f55 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+spdlog (1:1.8.1+ds-3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Track fmtlib abi in libspdlog1
+
+ -- Shengjing Zhu   Wed, 30 Dec 2020 02:30:44 +0800
+
 spdlog (1:1.8.1+ds-2) unstable; urgency=medium
 
   [ Shengjing Zhu ]
diff --git a/debian/control b/debian/control
index e83f692..ab6d998 100644
--- a/debian/control
+++ b/debian/control
@@ -38,6 +38,8 @@ Package: libspdlog1
 Architecture: any
 Multi-Arch: same
 Section: libs
+Breaks: libspdlog (<< 1:1.8.1+ds-3)
+Provides: ${spdlog:Provides}
 Depends: ${shlibs:Depends},
  ${misc:Depends}
 Description: Very fast C++ logging library
diff --git a/debian/rules b/debian/rules
index f20dd81..154cbdc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -7,6 +7,10 @@ endif
 
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 
+soversion = 1
+fmtabi = $(shell apt show libfmt-dev 2>/dev/null | sed -n 's/Depends: .*libfmt\([0-9]*\) .*/\1/p')
+spdlogfmtabi = libspdlog$(soversion)-fmt$(fmtabi)
+
 %:
 	dh $@ --with pkgkde_symbolshelper --buildsystem=cmake
 
@@ -41,3 +45,9 @@ override_dh_auto_install:
 	rm -f example/logs/.gitignore
 	dh_auto_install
 	find debian -name .gitignore -delete
+
+override_dh_gencontrol:
+	dh_gencontrol -- -Vspdlog:Provides=$(spdlogfmtabi)
+
+override_dh_makeshlibs:
+	dh_makeshlibs -plibspdlog1 -V '$(spdlogfmtabi)'

Bug#978351: requests: FTBFS: AttributeError: 'LookupDict' object has no attribute '__name__'

[Daniele Tricoli]

On Mon, 28 Dec 2020 17:11:47 +0100 Daniele Tricoli  wrote:
> 
> I can reproduce it using python3-sphinx 3.4.1, I'm still investigating since
> from sphinx's CHANGELOG the only incompatible change[¹] upgrading from sphinx
> 3.3.1 (using it building the documentation is fine) seems to not be related to
> this.

I opened an issue upstream https://github.com/sphinx-doc/sphinx/issues/8616
but I'm going to close this temporary patching out the the part of the
documentation that is failing to build, so we can close this without
reassigning to sphinx.

The temporary patch will just exclude the autodocumentation for requests.codes.

Cheers,

-- 
  Daniele Tricoli 'eriol'
  https://mornie.org


signature.asc
Description: PGP signature

Bug#972134: marked as done (chromium: please, consider moving the package to team-maintainance to properly maintain it)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 18:33:23 +
with message-id 
and subject line Bug#972134: fixed in debian-design 3.0.21
has caused the Debian Bug report #972134,
regarding chromium: please, consider moving the package to team-maintainance to 
properly maintain it
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.)


-- 
972134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 83.0.4103.116-3.1
Severity: wishlist

Currently, the way that chromium is being maintained is far from the
standards that we expect in Debian.

A considerable number of reasonable bug reports (like, for instance the one
for enabling sharing one's desktop in this age of pandemic and many people
having to work from home) are not answered or ignored.

Besides that, there is a skeleton of a version 84 in the repo, but the
package manager (and https://packages.debian.org/search?keywords=chromium)
doesn't know about it.

Going even further, Google Chrome (which I really, really don't want to
install on my systems) is already at version 86 according to both
https://en.wikipedia.org/wiki/Google_Chrome_version_history and
https://chromereleases.googleblog.com/2020/10/stable-channel-update-for-desktop_12.html

Furthermore, https://tracker.debian.org/pkg/chromium lists, at this moment,
100 security issues in sid, buster and bullseye.

Honestly, if one can't keep up with updates to their packages, at least make
a call for a group of buddy developers to help (the package tracker doesn't
show any kind of RFH bug open) or find someone else that is willing to
maintain the package.


Thanks,

Rogério Brito.

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

Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  chromium-common  83.0.4103.116-3.1
ii  libasound2   1.2.3.2-1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.1-4
ii  libavformat587:4.3.1-4
ii  libavutil56  7:4.3.1-4
ii  libc62.31-3
ii  libcairo21.16.0-4
ii  libcups2 2.3.3-3
ii  libdbus-1-3  1.12.20-1
ii  libdrm2  2.4.102-1
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-1
ii  libflac8 1.3.3-1
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.2+dfsg-3
ii  libgbm1  20.1.9-1
ii  libgcc-s110.2.0-13
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.66.0-2
ii  libgtk-3-0   3.24.23-2
ii  libharfbuzz0b2.6.7-1
ii  libicu67 67.1-4
ii  libjpeg62-turbo  1:2.0.5-1.1
ii  libjsoncpp1  1.7.4-3.1
ii  liblcms2-2   2.9-4+b1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.28-1
ii  libnss3  2:3.56-1
ii  libopenjp2-7 2.3.1-1
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-1
ii  libpangocairo-1.0-0  1.46.2-1
ii  libpng16-16  1.6.37-3
ii  libpulse013.0-5
ii  libre2-8 20201001+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.0-13
ii  libvpx6  1.8.2-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.6.12-1
ii  libx11-xcb1  2:1.6.12-1
ii  libxcb-dri3-01.14-2
ii  libxcb1  1.14-2
ii  libxcomposite1   1:0.4.5-1
ii  libxcursor1  1:1.2.0-2
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-2
ii  libxi6   2:1.7.10-1
ii  libxml2  2.9.10+dfsg-6
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.34-4
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  83.0.4103.116-3.1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  

Bug#978640: undefined symbol: _ZTIN3fmt2v612format_errorE

[Hubert Chathi]

On Tue, 29 Dec 2020 19:55:57 +0530, Utkarsh Gupta  said:

> Dear maintainer,

> Whilst trying to open nheko, it fails to open with the following
> message:

> ``` $ nheko nheko: symbol lookup error: nheko: undefined symbol:
> _ZTIN3fmt2v612format_errorE ```

> Is that known? Any idea what caused this regression or failure? Any
> workaround this?

Hmm.  Can you try installing libfmt7 (from sid) and see if that fixes
it?

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Bug#978471: waybar fails to launch

[Sebastian Ramacher]

On 2020-12-29 22:01:15, Andrey Rahmatullin wrote:
> Control: reassign -1 libspdlog1/1:1.8.1+ds-2+b1
> Control: affects -1 waybar
> Control: severity -1 serious
> Control: retitle -1 libspdlog1 breaks ABI on rebuilds with different libfmt
> 
> On Sun, Dec 27, 2020 at 09:26:09PM +0100, Michele Cane wrote:
> > waybar: symbol lookup error: waybar: undefined symbol: 
> > _ZN6spdlog7details7log_msgC1ENS_10source_locEN3fmt2v617basic_string_viewIcEENS_5level10level_enumES6_
> This is because libspdlog1 was rebuilt with newer libfmt and this caused
> symbol renames.
> 
> #977454 says "The code is actually working with the new version, only the
> symbols file is wrong here. spdlog uses fmtlib internal API and exposes it
> through the symbols files. This looks wrong to me, as every new fmtlib
> will cause spdlog ftbfs due to the symbols file.". If it's about the same
> problem then it looks like it failed to mention that symbol changes cause
> much worse problems than just needing to update the symbols file.

The situtation is somewhat similar to liboost-regex and libicu.
libboost-regex exports symbols that depend on libicu's ABI and change
whenever liboost-regex is rebuilt against a version of libicu with a
different ABI.

For spdlog this can be solved in the same way as for boost.
liboost-regexX.Y provides libboost-regexX.Y-icuZ when built against
libicuZ. Reverse dependencies then depend on libboost-regexX.Y-icuZ. See

https://salsa.debian.org/debian/boost/-/blob/master/debian/rules#L53
https://salsa.debian.org/debian/boost/-/blob/master/debian/rules#L289
https://salsa.debian.org/debian/boost/-/blob/master/debian/rules#L338

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#975696: marked as done (link-grammar: multi-thread test fails)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 18:03:39 +
with message-id 
and subject line Bug#975696: fixed in link-grammar 5.8.0-3
has caused the Debian Bug report #975696,
regarding link-grammar: multi-thread test fails
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.)


-- 
975696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: link-grammar
Version: 5.8.0-1
Severity: serious
Tags: ftbfs
X-Debbugs-CC: pkg-sugar-de...@lists.alioth.debian.org, d...@jones.dk
Control: block 972670 by -1

Hi Abiword and Sugar Maintainers (since link-grammar is orphaned)

The upload of link-grammar 5.8.0-1 intermittently FTBFS on several
architectures, e.g. arm64 [1], armel [2] and ppc64 [3].  The failures
all happen during the multi-thread test with various errors:
double free or corruption (fasttop)
free(): invalid pointer
malloc_consolidate(): invalid chunk size
Segmentation fault
corrupted double-linked list

Giving back the builds eventually works, and link-grammar is currently
built on all release architectures.  However, this same test is run
during the autopkgtest and for some reason always fails on armhf [4].
This prevents the migration of link-grammar 5.8.0-1 to testing, and
will eventually cause the autoremoval of abiword and sugar from
testing.

Would you please have a look?

Regards
Graham


[1] 
https://buildd.debian.org/status/fetch.php?pkg=link-grammar=arm64=5.8.0-1%2Bb1=1606121733=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=link-grammar=armel=5.8.0-1%2Bb1=1605753701=0
[3] 
https://buildd.debian.org/status/fetch.php?pkg=link-grammar=ppc64=5.8.0-1%2Bb1=1606118399=0
[4] https://ci.debian.net/packages/l/link-grammar/testing/armhf/
--- End Message ---
--- Begin Message ---
Source: link-grammar
Source-Version: 5.8.0-3
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
link-grammar, 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.
Jonas Smedegaard  (supplier of updated link-grammar 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: Tue, 29 Dec 2020 18:46:03 +0100
Source: link-grammar
Architecture: source
Version: 5.8.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Jonas Smedegaard 
Closes: 975696
Changes:
 link-grammar (5.8.0-3) unstable; urgency=medium
 .
   * QA upload.
 .
   * improve autopkgtest:
 + check core tests and python bindings unit tests separately
 + tighten python bindings unit tests
   to check data and all (not only most) code
   from installed packaged (not from unpacked source)
 + flag core test as flaky
   (mysteriously fails particularly on armhf,
   despite succeeding during build);
   closes: bug#975696, thanks to Graham Inggs
Checksums-Sha1:
 17c4a532bdc07fbfdcdc98772e7b7f18bfa52f56 3060 link-grammar_5.8.0-3.dsc
 55109626d154ecae578c53bfcf47a826ce0eff3a 24968 
link-grammar_5.8.0-3.debian.tar.xz
 b05a36efc645511abb142d4e59748a6e707e2200 13164 
link-grammar_5.8.0-3_amd64.buildinfo
Checksums-Sha256:
 07f2902d5948905074589314cd75237e3e175c8fb7a318ade198eaa9eee4b025 3060 
link-grammar_5.8.0-3.dsc
 ea3199bcc6a2e50341bc54ff32d875529fe5bc8abf75cf3f8c0ef2313c7811e5 24968 
link-grammar_5.8.0-3.debian.tar.xz
 5d267741b020cbd27e5027d6dd99ef5d94d2f7bf2054a821eb30a2e3c985148a 13164 
link-grammar_5.8.0-3_amd64.buildinfo
Files:
 48253169e6d71c0ab0fd4a894d644046 3060 text optional link-grammar_5.8.0-3.dsc
 c764cd2f58d2d4aa40ca49db6db75dc3 24968 text optional 
link-grammar_5.8.0-3.debian.tar.xz
 eeb1f9da8bf288d0554c462e0c65a350 13164 text optional 
link-grammar_5.8.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/rbeoACgkQLHwxRsGg
ASFGDA/7Br34yEgUtmzFQj3pDyDqtQnIL9JfP8ZvaJ1ymeVc/7l44RqIrrL9ehJ2
5xHaKBqRmZVd5yEv579Bcf4XqlSRIm/W/aSc46qa2eJVnKO1rqlqyosT64ygPQ8L
s4EBzCQWNjuHPNgd9jVjLNu6R1Jzvq81vjfasPIBhE4QWKVrztNi6/i446QvZz5R
mW6g419WdIvDT7K6ukmQ4G0a95mFUlzOS2I/A1MMh6mcluj3vd4AkZva6McW5Jw4

Bug#978640: undefined symbol: _ZTIN3fmt2v612format_errorE

[Utkarsh Gupta]

Hi Hubert,

On Tue, Dec 29, 2020 at 11:17 PM Hubert Chathi  wrote:
> Hmm.  Can you try installing libfmt7 (from sid) and see if that fixes
> it?

The issue could be fixed by rebuilding nheko against the newly updated
libfmt-dev version. I've prepared and pushed a fix to the salsa
repository. If it's okay with you, can I do the upload as well?


- u

Processed: severity of 974841 is important

[Debian Bug Tracking System]

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

> severity 974841 important
Bug #974841 [src:ms-gsl] ms-gsl: new clang test fails on s390x
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#978648: spyder: Exits at startup with an import error for module zmq.backend.cython

[Gerard L.]

Package: spyder
Version: 3.3.6+dfsg1-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: carmen@belgacom.net

Dear Maintainer,

Since the last update of my Debian Testing distro, Spyder no more starts.
When launching spyder from command line we can see a import error message
from the python interpreter complaining that it cannot import name 'constants' 
from partially initialized module 'zmq.backend.cython'. And that's most likely 
due to a circular import
 (/usr/lib/python3/dist-packages/zmq/backend/cython/__init__.py)

See attached traceback.

Thanks.

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

Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages spyder depends on:
ii  python3-spyder  3.3.6+dfsg1-5
ii  python3.8   3.8.7-1

spyder recommends no packages.

spyder suggests no packages.

Versions of packages python3-spyder depends on:
ii  libjs-jquery3.5.1+dfsg+~3.5.4-3
ii  libjs-mathjax   2.7.9+dfsg-1
ii  pylint  2.6.0-1
ii  python3 3.9.0-4
ii  python3-chardet 3.0.4-7
ii  python3-cloudpickle 1.6.0-1
ii  python3-jedi0.17.0-1
ii  python3-keyring 21.6.0-1
ii  python3-nbconvert   5.6.1-2
ii  python3-numpydoc1.1.0-3
ii  python3-pickleshare 0.7.5-3
ii  python3-psutil  5.7.3-1+b2
ii  python3-pycodestyle 2.6.0-1
ii  python3-pyflakes2.2.0-2
ii  python3-pygments2.7.1+dfsg-1
ii  python3-qtawesome   0.4.4+ds1-3
ii  python3-qtconsole   4.7.6-1
ii  python3-qtpy1.9.0-3
ii  python3-rope0.17.0-1
ii  python3-sphinx  3.3.1-1
ii  python3-spyder-kernels  1.5.0~really0.5.2-1
ii  python3-zmq 20.0.0-1+b1
ii  spyder-common   3.3.6+dfsg1-5

Versions of packages python3-spyder suggests:
pn  cython3 
ii  python3-matplotlib  3.3.2-2+b1
ii  python3-numpy   1:1.19.4-1+b1
pn  python3-pandas  
ii  python3-pil 8.0.1-1+b1
pn  python3-scipy   
pn  python3-sympy   

Versions of packages python3-pyqt5 depends on:
ii  libc6 2.31-6
ii  libgcc-s1 10.2.1-1
ii  libpython3.9  3.9.1-1
ii  libqt5core5a [qtbase-abi-5-15-2]  5.15.2+dfsg-2
ii  libqt5dbus5   5.15.2+dfsg-2
ii  libqt5designer5   5.15.2-3
ii  libqt5gui55.15.2+dfsg-2
ii  libqt5help5   5.15.2-3
ii  libqt5network55.15.2+dfsg-2
ii  libqt5printsupport5   5.15.2+dfsg-2
ii  libqt5test5   5.15.2+dfsg-2
ii  libqt5widgets55.15.2+dfsg-2
ii  libqt5xml55.15.2+dfsg-2
ii  libstdc++610.2.1-1
ii  python3   3.9.0-4
ii  python3-pyqt5.sip 12.8.1-1+b2

Versions of packages python3-pyqt5 suggests:
pn  python3-pyqt5-dbg  

-- no debconf information
Traceback (most recent call last):
  File "/usr/bin/spyder", line 11, in 
load_entry_point('spyder==3.3.6', 'gui_scripts', 'spyder3')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 473, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2843, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2447, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2453, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/spyder/app/start.py", line 14, in 

import zmq
  File "/usr/lib/python3/dist-packages/zmq/__init__.py", line 55, in 
from zmq import backend
  File "/usr/lib/python3/dist-packages/zmq/backend/__init__.py", line 40, in 

reraise(*exc_info)
  File "/usr/lib/python3/dist-packages/zmq/utils/sixcerpt.py", line 34, in 
reraise
raise value
  File "/usr/lib/python3/dist-packages/zmq/backend/__init__.py", line 27, in 

_ns = select_backend(first)
  File "/usr/lib/python3/dist-packages/zmq/backend/select.py", line 28, in 
select_backend
mod = __import__(name, fromlist=public_api)
  File "/usr/lib/python3/dist-packages/zmq/backend/cython/__init__.py", line 6, 
in 
from . import (constants, error, message, context,
ImportError: cannot import name 'constants' from partially initialized module 
'zmq.backend.cython' (most likely due to a circular import) 
(/usr/lib/python3/dist-packages/zmq/backend/cython/__init__.py)

Processed: reassign 978471 to libspdlog1

[Debian Bug Tracking System]

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

> reassign 978471 libspdlog1 1:1.8.1+ds-2+b1
Bug #978471 [waybar] libspdlog1 breaks ABI on rebuilds with different libfmt
Bug reassigned from package 'waybar' to 'libspdlog1'.
No longer marked as found in versions waybar/0.9.4-1.
Ignoring request to alter fixed versions of bug #978471 to the same values 
previously set
Bug #978471 [libspdlog1] libspdlog1 breaks ABI on rebuilds with different libfmt
Marked as found in versions spdlog/1:1.8.1+ds-2.
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#978471: waybar fails to launch

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libspdlog1/1:1.8.1+ds-2+b1
Unknown command or malformed arguments to command.

> affects -1 waybar
Bug #978471 [waybar] waybar fails to launch
Added indication that 978471 affects waybar
> severity -1 serious
Bug #978471 [waybar] waybar fails to launch
Severity set to 'serious' from 'important'
> retitle -1 libspdlog1 breaks ABI on rebuilds with different libfmt
Bug #978471 [waybar] waybar fails to launch
Changed Bug title to 'libspdlog1 breaks ABI on rebuilds with different libfmt' 
from 'waybar fails to launch'.

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

Bug#972749: marked as done (xen-tools: bullseye: /updates -> -security)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 15:35:39 +
with message-id 
and subject line Bug#972749: fixed in xen-tools 4.9-1
has caused the Debian Bug report #972749,
regarding xen-tools: bullseye: /updates -> -security
to be marked as done.

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

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


-- 
972749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xen-tools
Version: 4.8-1
Severity: serious
File: /usr/share/xen-tools/debian.d/20-setup-apt
User: debian-de...@lists.debian.org
Usertags: bullseye-security

With the release of Debian bullseye and later, security updates are
provided in the bullseye-security suite instead of bullseye/updates.

The above hook script references ${dist}/updates but when bullseye is
released that should be replaced by ${dist}-security so it looks
like the script would generate an incorrect sources.list using /updates
instead of -security which would cause the new Xen guest to not get
security updates from bullseye in a timely manner.

I suggest that this hook check the version of the Debian release in
question using distro-info and then if the release is 11 or higher,
then use ${dist}-security otherwise use ${dist}/updates as before.

It is much better to use distro-info than to hard-code the release
version numbers. It might even be a good idea to include the security
suite information in distro-info itself and look it up there.

   $ grep -B12 -A3 /updates /usr/share/xen-tools/debian.d/20-setup-apt
   #
   #  If the host system has security support then enable that here, too,
   #  except if we're installing Debian Unstable.
   #
   if ( test "${dist}" "!=" "sid" && test "${dist}" "!=" "unstable" && \
test -e /etc/apt/sources.list && \
grep ^deb.*security -r /etc/apt/sources.list /etc/apt/sources.list.d 
>/dev/null 2>/dev/null ) ; then

   cat <> ${prefix}/etc/apt/sources.list
   # 
   #  Security updates
   # 
   deb http://security.debian.org/ ${dist}/updates  main contrib non-free
   deb-src http://security.debian.org/ ${dist}/updates  main contrib non-free
   E_O_APT

   else
   cat <> ${prefix}/etc/apt/sources.list
   # 
   #  Security updates - Uncomment to enable.
   # 
   # deb http://security.debian.org/ ${dist}/updates  main contrib non-free
   # deb-src http://security.debian.org/ ${dist}/updates  main contrib non-free
   E_O_APT

   fi

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

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

Versions of packages xen-tools depends on:
ii  debootstrap   1.0.123
ii  libconfig-inifiles-perl   3.03-1
ii  libdata-validate-domain-perl  0.10-1
pn  libdata-validate-ip-perl  
pn  libdata-validate-uri-perl 
ii  libfile-slurp-perl.32-1
ii  libfile-which-perl1.23-1
ii  libsort-versions-perl 1.62-1
ii  libtext-template-perl 1.59-1
ii  openssh-client1:8.3p1-1
ii  perl  5.30.3-4

Versions of packages xen-tools recommends:
ii  debian-archive-keyring   2019.1
ii  e2fsprogs1.45.6-1
pn  libexpect-perl   
ii  lvm2 2.03.09-3
pn  rinse
pn  ubuntu-keyring | ubuntu-archive-keyring  
pn  xen-hypervisor   
pn  xen-utils

Versions of packages xen-tools suggests:
ii  btrfs-progs5.7-1
pn  cfengine2  
pn  grub-xen-host  
ii  reiserfsprogs  1:3.6.27-4
pn  xfsprogs   

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: xen-tools
Source-Version: 4.9-1
Done: Axel Beckert 

We believe that the bug you reported is fixed in the latest version of
xen-tools, 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 

Processed: severity of 977192 is grave

[Debian Bug Tracking System]

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

> severity 977192 grave
Bug #977192 [src:libappimage] libappimage: CVE-2020-25265
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#978640: undefined symbol: _ZTIN3fmt2v612format_errorE

[Utkarsh Gupta]

Package: nheko
Version: 0.7.2-3
Severity: grave

Dear maintainer,

Whilst trying to open nheko, it fails to open with the following message:

```
$ nheko
nheko: symbol lookup error: nheko: undefined symbol: _ZTIN3fmt2v612format_errorE
```

Is that known? Any idea what caused this regression or failure? Any
workaround this?



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

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

Versions of packages nheko depends on:
ii  libboost-iostreams1.74.0   1.74.0-6
ii  libboost-thread1.74.0  1.74.0-6
ii  libc6  2.31-6
ii  libcmark0.29.0 0.29.0-4
ii  libgcc-s1  10.2.1-3
ii  liblmdb0   0.9.24-1
ii  libolm33.2.1~dfsg-5
ii  libqt5core5a   5.15.2+dfsg-2
ii  libqt5dbus55.15.2+dfsg-2
ii  libqt5gui5 5.15.2+dfsg-2
ii  libqt5network5 5.15.2+dfsg-2
ii  libqt5qml5 5.15.2+dfsg-2
ii  libqt5quick5   5.15.2+dfsg-2
ii  libqt5quickwidgets55.15.2+dfsg-2
ii  libqt5widgets5 5.15.2+dfsg-2
ii  libsodium231.0.18-1
ii  libspdlog1 1:1.8.1+ds-2+b1
ii  libssl1.1  1.1.1i-1
ii  libstdc++6 10.2.1-3
ii  qml-module-qt-labs-settings5.15.2+dfsg-2
ii  qml-module-qtgraphicaleffects  5.15.2-2
ii  qml-module-qtmultimedia5.15.2-2
ii  qml-module-qtquick-controls2   5.15.2+dfsg-2
ii  qml-module-qtquick-layouts 5.15.2+dfsg-2
ii  qml-module-qtquick-window2 5.15.2+dfsg-2
ii  qml-module-qtquick25.15.2+dfsg-2

Versions of packages nheko recommends:
ii  ca-certificates 20200601
ii  fonts-noto-color-emoji  0~20200916-1

Bug#976891: [Android-tools-devel] Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

[Hans-Christoph Steiner]

It looks like the clean build stops before the error you reported:

https://salsa.debian.org/eighthave/android-platform-art/-/jobs/1291335

In file included from runtime/runtime.cc:53:
runtime/asm_support.h:24:10: fatal error: 'asm_defines.h' file not found
#include "asm_defines.h"
 ^~~
1 error generated.
make[2]: *** [debian/libart.mk:473: runtime/runtime.o] Error 1

My guess is that the Makefile dependency rules are wrong, since the 
target that builds asm_defines.h works fine when manually run.


If you use your own fork, and force-push commits to your fork's master 
branch, it'll run the CI jobs, which are totally clean builds each time.

Processed: tagging 978625

[Debian Bug Tracking System]

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

> tags 978625 + confirmed
Bug #978625 [src:prads] src:prads: invalid maintainer address
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#978555: libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file

[Vincent Lefevre]

On 2020-12-29 07:47:11 +0100, Sven Joachim wrote:
> There is already code in the libpam0g postinst script to restart them,
> but it is only triggered on upgrades from versions older than 1.3.1-2,
> which is apparently not enough.

Yes, in the case of cron, the daemon is linked against
/lib/x86_64-linux-gnu/libpam.so.0 (thus the file before the PAM upgrade)
and tries to open pam_unix.so later via dlopen (thus the file after the
PAM upgrade). I suppose that libpam.so.0 and pam_unix.so must come from
the same PAM version, so a restart of the cron service is necessary.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#978191: marked as done (gudhi: FTBFS: Tangential_complex.h:957:40: error: no type named ‘Power_center_d’ in ‘Gudhi::tangential_complex::Tangential_complex

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 11:50:37 +
with message-id 
and subject line Bug#978191: fixed in gudhi 3.4.0+dfsg-2
has caused the Debian Bug report #978191,
regarding gudhi: FTBFS: Tangential_complex.h:957:40: error: no type named 
‘Power_center_d’ in 
‘Gudhi::tangential_complex::Tangential_complex,
 CGAL::Dynamic_dimension_tag, CGAL::Parallel_tag>::Tr_traits’ {aka ‘class 
CGAL::Regular_triangulation_traits_adapter
 >’}
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.)


-- 
978191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gudhi
Version: 3.4.0+dfsg-1
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):
> cd /<>/build/userversion/src/Tangential_complex/benchmark && 
> /usr/bin/c++ -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB 
> -DBOOST_RESULT_OF_USE_DECLTYPE -DBOOST_SYSTEM_NO_DEPRECATED 
> -DCGAL_EIGEN3_ENABLED -DCGAL_USE_GMPXX=1 -DGUDHI_USE_TBB -DNOMINMAX 
> -I/<>/build/userversion -I/<>/src/common/include 
> -I/<>/src/Alpha_complex/include 
> -I/<>/src/Bitmap_cubical_complex/include 
> -I/<>/src/Bottleneck_distance/include 
> -I/<>/src/Collapse/include 
> -I/<>/src/Contraction/include 
> -I/<>/src/Cech_complex/include 
> -I/<>/src/Hasse_complex/include 
> -I/<>/src/Persistence_representations/include 
> -I/<>/src/Persistent_cohomology/include 
> -I/<>/src/Rips_complex/include 
> -I/<>/src/Simplex_tree/include 
> -I/<>/src/Skeleton_blocker/include 
> -I/<>/src/Spatial_searching/include 
> -I/<>/src/Subsampling/include 
> -I/<>/src/Tangential_complex/include 
> -I/<>/src/Toplex_map/include 
> -I/<>/src/Witness_complex/include 
> -I/<>/src/Nerve_GIC/include -isystem /usr/include/eigen3 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic 
> -frounding-math -std=gnu++14 -o 
> CMakeFiles/Tangential_complex_benchmark.dir/benchmark_tc.cpp.o -c 
> /<>/src/Tangential_complex/benchmark/benchmark_tc.cpp
> In file included from 
> /<>/src/Tangential_complex/benchmark/benchmark_tc.cpp:30:
> /<>/src/Tangential_complex/include/gudhi/Tangential_complex/Simplicial_complex.h:
>  In member function ‘void 
> Gudhi::tangential_complex::internal::Simplicial_complex::collapse(int, bool)’:
> /<>/src/Tangential_complex/include/gudhi/Tangential_complex/Simplicial_complex.h:154:37:
>  warning: comparison of integer expressions of different signedness: 
> ‘boost::container::dtl::flat_tree boost::move_detail::identity, std::less int>, void>::size_type’ {aka ‘long unsigned int’} and ‘int’ [-Wsign-compare]
>   154 |   GUDHI_CHECK(it_Cf->size() == max_simplex_dim + 1,
>   |   ~~^~
> /<>/src/common/include/gudhi/Debug_utils.h:23:44: note: in 
> definition of macro ‘GUDHI_CHECK’
>23 |   #define GUDHI_CHECK(expression, excpt) ((expression) ? (void) 0 : 
> (throw excpt))
>   |^~
> In file included from 
> /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
>  from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
>  from 
> /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
>  from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
>  from 
> /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
>  from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
>  from /usr/include/boost/shared_ptr.hpp:17,
>  from /usr/include/CGAL/Object.h:32,
>  from /usr/include/CGAL/kernel_basic.h:25,
>  from /usr/include/CGAL/basic.h:35,
>  from /usr/include/CGAL/Combination_enumerator.h:18,
>  from 
> /<>/src/Tangential_complex/include/gudhi/Tangential_complex/utilities.h:15,
>  from 
> /<>/src/Tangential_complex/include/gudhi/Tangential_complex/Simplicial_complex.h:15,
>  from 
> /<>/src/Tangential_complex/include/gudhi/Tangential_complex.h:16,
>  from 
> /<>/src/Tangential_complex/benchmark/benchmark_tc.cpp:32:
> /usr/include/boost/function_output_iterator.hpp: At global scope:
> /usr/include/boost/function_output_iterator.hpp:14:1: note: ‘#pragma message: 
> This header is deprecated. Use  
> instead.’
>14 | 
> 

Bug#977604: smarty3: broken internal parsetree code

[Wolfgang Schweer]

Moin Mike,

[ Mike Gabriel, 2020-12-18 ]
> I looked into this today and failed to get the issue fixed.
> 
> I tried updating smarty-lexer to upstream's Git master and rebuilt smarty3
> 3.1.36. Without success...
> 
> So, I filed an upstream report on this and hope for feedback from Uwe...
> https://github.com/smarty-php/smarty/issues/621

This might rather be an issue concerning oldish code in GOsa and 
slbackup-php than a Smarty bug. At least it seems to be unrelated to
internal parsetree code...

After digging into this a bit (w/o having a real clue about PHP and 
Smarty), I noticed that it is sufficient to replace one file to make 
both Gosa and slbackup-php work; see the comment about variables prior 
to PHP 5.5:

diff -u a/smarty_internal_templatecompilerbase.php 
b/smarty_internal_templatecompilerbase.php
--- a/smarty_internal_templatecompilerbase.php  2018-08-31 00:00:00.0 
+0200
+++ b/smarty_internal_templatecompilerbase.php  2020-04-14 00:00:00.0 
+0200
@@ -621,22 +621,18 @@
 || strcasecmp($name, 'array') === 0 || is_callable($name)
 ) {
 $func_name = strtolower($name);
-$par = implode(',', $parameter);
-$parHasFuction = strpos($par, '(') !== false;
+
 if ($func_name === 'isset') {
 if (count($parameter) === 0) {
 $this->trigger_template_error('Illegal number of 
parameter in "isset()"');
 }
-if ($parHasFuction) {
-$pa = array();
-foreach ($parameter as $p) {
-$pa[] = (strpos($p, '(') === false) ? ('isset(' . 
$p . ')') : ('(' . $p . ' !== null )');
-}
-return '(' . implode(' && ', $pa) . ')';
-} else {
-$isset_par = str_replace("')->value", 
"',null,true,false)->value", $par);
-}
-return $name . '(' . $isset_par . ')';
+
+   $pa = array();
+   foreach ($parameter as $p) {
+   $pa[] = $this->syntaxMatchesVariable($p) ? 
'isset(' . $p . ')' : '(' . $p . ' !== null )';
+   }
+   return '(' . implode(' && ', $pa) . ')';
+
 } elseif (in_array(
 $func_name,
 array(
@@ -653,7 +649,7 @@
 $this->trigger_template_error("Illegal number of 
parameter in '{$func_name()}'");
 }
 if ($func_name === 'empty') {
-if ($parHasFuction && version_compare(PHP_VERSION, 
'5.5.0', '<')) {
+if (!$this->syntaxMatchesVariable($parameter[0]) && 
version_compare(PHP_VERSION, '5.5.0', '<')) {
 return '(' . $parameter[ 0 ] . ' === false )';
 } else {
 return $func_name . '(' .
@@ -671,74 +667,82 @@
 }
 }
 
+   /**
+* Determines whether the passed string represents a valid (PHP) 
variable.
+* This is important, because `isset()` only works on variables and 
`empty()` can only be passed
+* a variable prior to php5.5
+* @param $string
+* @return bool
+*/
+   private function syntaxMatchesVariable($string) {
+   static $regex_pattern = 
'/^\$[a-zA-Z_\x7f-\xff][a-zA-Z0-9_\x7f-\xff]*((->)[a-zA-Z_\x7f-\xff][a-zA-Z0-9_\x7f-\xff]*|\[.*]*\])*$/';
+   return 1 === preg_match($regex_pattern, trim($string));
+}
+
 /**
- * This method is called from parser to process a text content section
+ * This method is called from parser to process a text content section if 
strip is enabled
  * - remove text from inheritance child templates as they may generate 
output
- * - strip text if strip is enabled
  *
  * @param string $text
  *
- * @return null|\Smarty_Internal_ParseTree_Text
+ * @return string
  */
 public function processText($text)
 {
-if ((string)$text != '') {
-$store = array();
-$_store = 0;
-if ($this->parser->strip) {
-if (strpos($text, '<') !== false) {
-// capture html elements not to be messed with
-$_offset = 0;
-if (preg_match_all(
-
'#(]*>.*?]*>)|(]*>.*?]*>)|(]*>.*?]*>)#is',
-$text,
-$matches,
-PREG_OFFSET_CAPTURE | PREG_SET_ORDER
-)
-) {
-foreach ($matches as $match) {
-$store[] = $match[ 0 ][ 0 ];
-$_length = strlen($match[ 0 ][ 0 ]);
-$replace = '@!@SMARTY:' . $_store . ':SMARTY@!@';
-  

Bug#978191: gudhi: FTBFS: Tangential_complex.h:957:40: error: no type named ‘Power_center_d’ in ‘Gudhi::tangential_complex::Tangential_complex, CGAL::Dynamic

[Gard Spreemann]

Thank you for reporting this. It also revealed an upstream bug, which
has been forwarded.

I'm uploading a fix now.


 Best,
 Gard
 

Bug#978616: mediastreamer2: doesn't build correct libraries with cmake?

[Gianfranco Costamagna]

This might be a patch that works if the library is found via pkgconfig but not 
via cmake

--- mediastreamer2-4.4.21.orig/src/CMakeLists.txt
+++ mediastreamer2-4.4.21/src/CMakeLists.txt
@@ -495,12 +495,16 @@ if(ENABLE_STATIC)
)
 endif()
 if(ENABLE_SHARED)
-   add_library(mediastreamer SHARED ${MEDIASTREAMER2_HEADER_FILES} 
${SOURCE_FILES_ALL})
-   set_target_properties(mediastreamer PROPERTIES LINKER_LANGUAGE CXX)
+   add_library(mediastreamer_base SHARED ${MEDIASTREAMER2_HEADER_FILES} 
${BASE_SOURCE_FILES_C})
+   set_target_properties(mediastreamer_base PROPERTIES LINKER_LANGUAGE CXX)
+   add_library(mediastreamer_voip SHARED ${MEDIASTREAMER2_HEADER_FILES} 
${VOIP_SOURCE_FILES_ALL})
+   set_target_properties(mediastreamer_voip PROPERTIES LINKER_LANGUAGE CXX)
if(LINK_FLAGS_STR)
-   set_target_properties(mediastreamer PROPERTIES LINK_FLAGS 
"${LINK_FLAGS_STR}")
+   set_target_properties(mediastreamer_base PROPERTIES LINK_FLAGS 
"${LINK_FLAGS_STR}")
+   set_target_properties(mediastreamer_voip PROPERTIES LINK_FLAGS 
"${LINK_FLAGS_STR}")
endif()
-   add_dependencies(mediastreamer ${MS2_DEPENDENCIES})
+   add_dependencies(mediastreamer_base ${MS2_DEPENDENCIES})
+   add_dependencies(mediastreamer_voip ${MS2_DEPENDENCIES})
if(APPLE)
if(IOS)
set(MIN_OS ${LINPHONE_IOS_DEPLOYMENT_TARGET})
@@ -526,14 +530,21 @@ if(ENABLE_SHARED)
endif()
else()
# Do not version shared library on Android
-   set_target_properties(mediastreamer PROPERTIES SOVERSION 
${MEDIASTREAMER_SO_VERSION})
+   set_target_properties(mediastreamer_base PROPERTIES SOVERSION 
${MEDIASTREAMER_SO_VERSION})
+   set_target_properties(mediastreamer_voip PROPERTIES SOVERSION 
${MEDIASTREAMER_SO_VERSION})
 endif()
-   target_include_directories(mediastreamer INTERFACE
+   target_include_directories(mediastreamer_base INTERFACE
$
$
PRIVATE ${MEDIASTREAMER2_INCLUDE_DIRS}
)
-target_link_libraries(mediastreamer PRIVATE ${LINK_LIBS})
+   target_include_directories(mediastreamer_voip INTERFACE
+   $
+   $
+   PRIVATE ${MEDIASTREAMER2_INCLUDE_DIRS}
+   )
+target_link_libraries(mediastreamer_base PRIVATE ${LINK_LIBS})
+target_link_libraries(mediastreamer_voip PRIVATE ${LINK_LIBS})
if(IOS)
target_link_libraries(mediastreamer INTERFACE "-framework 
Foundation" "-framework AVFoundation")
endif()
@@ -545,7 +556,14 @@ if(ENABLE_SHARED)
)
endif()
endif()
-   install(TARGETS mediastreamer EXPORT ${EXPORT_TARGETS_NAME}Targets
+   install(TARGETS mediastreamer_base EXPORT ${EXPORT_TARGETS_NAME}Targets
+   RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR}
+   LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR}
+   ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR}
+   FRAMEWORK DESTINATION Frameworks
+   PERMISSIONS OWNER_READ OWNER_WRITE OWNER_EXECUTE GROUP_READ 
GROUP_EXECUTE WORLD_READ WORLD_EXECUTE
+   )
+   install(TARGETS mediastreamer_voip EXPORT ${EXPORT_TARGETS_NAME}Targets
RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR}
LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR}
ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR}
--- mediastreamer2-4.4.21.orig/tools/CMakeLists.txt
+++ mediastreamer2-4.4.21/tools/CMakeLists.txt
@@ -28,7 +28,7 @@ if (IOS)
 endif()
 
 if(ENABLE_SHARED)
-   set(MS2_LIBS_FOR_TOOLS mediastreamer)
+   set(MS2_LIBS_FOR_TOOLS mediastreamer_voip mediastreamer_base)
 else()
set(MS2_LIBS_FOR_TOOLS mediastreamer-static)
if(XV_FOUND)
--- mediastreamer2-4.4.21.orig/cmake/Mediastreamer2Config.cmake.in
+++ mediastreamer2-4.4.21/cmake/Mediastreamer2Config.cmake.in
@@ -36,7 +36,7 @@ include(CMakeFindDependencyMacro)
 include("${CMAKE_CURRENT_LIST_DIR}/Mediastreamer2Targets.cmake")
 
 if(@ENABLE_SHARED@)
-   set(MEDIASTREAMER2_TARGETNAME mediastreamer)
+   set(MEDIASTREAMER2_TARGETNAME mediastreamer_voip mediastreamer_base)
set(MEDIASTREAMER2_LIBRARIES ${MEDIASTREAMER2_TARGETNAME})
 else()
set(MEDIASTREAMER2_TARGETNAME mediastreamer-static)

I don't understand how such interfaces work...

G.

I tried a simple CMakeLists.txt
project(foo)
cmake_minimum_required(VERSION 3.18)
find_package(Mediastreamer2 REQUIRED)
add_executable(main main.c)
target_link_libraries(main mediastreamer2)


but fails with:
cmake ..
-- The C compiler identification is GNU 10.2.1
-- The CXX compiler identification is GNU 10.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- 

Bug#978625: src:prads: invalid maintainer address

[Ansgar]

Source: prads
Version: 0.3.3-5
Severity: serious
X-Debbugs-Cc: Stig Sandbeck Mathisen 

The maintainer address is invalid, see below.

Ansgar

 Forwarded Message 
Subject: Mail delivery failed: returning message to sender
Date: Sat, 26 Dec 2020 18:04:58 +

> 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:
> 
>   prads-de...@projects.linpro.no
>     retry timeout exceeded

Bug#978624: src:fbxkb: invalid maintainer address

[Ansgar]

Source: fbxkb
Version: 0.6-2
Severity: serious
X-Debbugs-Cc: Sudip Mukherjee 

The maintainer address is invalid, see below.

Ansgar

 Forwarded Message 
Subject: Mail delivery failed: returning message to sender
Date: Wed, 16 Dec 2020 21:34:39 +

> 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:
> 
>   q1we...@i.com.ua
>     host mail.alkar.net [93.178.217.40]
>     SMTP error from remote mail server after RCPT
> TO::
>     550 q1we...@i.com.ua unknown user account

Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;q1werty@i.com.ua
Status: 5.0.0
Remote-MTA: dns; mail.alkar.net
Diagnostic-Code: smtp; 550 q1werty@i.com.ua unknown user account

Bug#978623: src:connect-proxy: invalid maintainer address

[Ansgar]

Source: connect-proxy
Version: 1.105-1
Severity: serious
X-Debbugs-Cc: Christian Bayle , Roger Shimizu 


The maintainer address is invalid, see below.

Ansgar

 Forwarded Message 
Subject: Mail delivery failed: returning message to sender
Date: Fri, 25 Dec 2020 18:04:07 +

> 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:
> 
>   r...@gna.org
>     retry timeout exceeded

Bug#978622: src:libcrypt-des-ede3-perl: invalid maintainer address

[Ansgar]

Source: libcrypt-des-ede3-perl
Version: 0.0-1
Severity: serious
X-Debbugs-Cc: Holger Levsen , Florian Ragwitz 


The maintainer address is invalid, see below.  There is also a
"Diagnostic-Code: smtp;554 5.4.14 Hop count exceeded - possible mail
loop ATTR34 [DB5EUR01FT005.eop-EUR01.prod.protection.outlook.com]" that
Microsoft's emai^Wtelefax service included out of plain sight.

Ansgar

 Forwarded Message 
Subject: Undeliverable: libcrypt-des-ede3-perl_0.01-1.2_source.changes ACCEPTED 
into unstable
Date: Tue, 29 Dec 2020 00:49:06 +

> Your message to pm.al...@habitat-humanisme.org couldn't be delivered.
> pm.alamy wasn't found at habitat-humanisme.org.
> envelope    Office 365  pm.alamy
> Action Required Recipient
> Unknown To address
> 
> How to Fix It
> The address may be misspelled or may not exist. Try one or more of
> the following:
> 
>   *   Send the message again following these steps: In Outlook, open
> this non-delivery report (NDR) and choose Send Again from the Report
> ribbon. In Outlook on the web, select this NDR, then select the link
> "To send this message again, click here." Then delete and retype the
> entire recipient address. If prompted with an Auto-Complete List
> suggestion don't select it. After typing the complete address, click
> Send.
>   *   Contact the recipient (by phone, for example) to check that the
> address is correct.

Reporting-MTA: dns;DBBP189MB1195.EURP189.PROD.OUTLOOK.COM
Received-From-MTA: dns;EUR01-VE1-obe.outbound.protection.outlook.com
Arrival-Date: Tue, 29 Dec 2020 00:49:03 +

Final-Recipient: rfc822;pm.alamy@habitat-humanisme.org
Action: failed
Status: 5.4.14
Diagnostic-Code: smtp;554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [DB5EUR01FT005.eop-EUR01.prod.protection.outlook.com]
Remote-MTA: dns;DB5EUR01FT005.mail.protection.outlook.com
X-Display-Name: Pierre-Matthieu Alamy

Processed: block 975198 with 978617

[Debian Bug Tracking System]

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

> block 975198 with 978617
Bug #975198 [src:slic3r-prusa] slic3r-prusa: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j4 test ARGS=-V ARGS\+=-j4 returned exit code 2
975198 was blocked by: 975665
975198 was not blocking any bugs.
Added blocking bug(s) of 975198: 978617
> thanks
Stopping processing here.

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

Bug#978584: marked as done (anyremote-doc: missing Breaks+Replaces: anyremote (<< 6.7.3-2))

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 10:03:20 +
with message-id 
and subject line Bug#978584: fixed in anyremote 6.7.3-3
has caused the Debian Bug report #978584,
regarding anyremote-doc: missing Breaks+Replaces: anyremote (<< 6.7.3-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.)


-- 
978584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: anyremote-doc
Version: 6.7.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../anyremote-doc_6.7.3-2_all.deb ...
  Unpacking anyremote-doc (6.7.3-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/anyremote-doc_6.7.3-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/anyremote/NEWS.gz', which is also in 
package anyremote 6.7.3-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/anyremote-doc_6.7.3-2_all.deb

This is probably caused by a behavioral change of dh_installdocs
that was activated by the recent debhelper-compat bump.


cheers,

Andreas


anyremote=6.7.3-1_anyremote-doc=6.7.3-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: anyremote
Source-Version: 6.7.3-3
Done: Philipp Huebner 

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

Debian distribution maintenance software
pp.
Philipp Huebner  (supplier of updated anyremote 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: Tue, 29 Dec 2020 10:59:24 +0100
Source: anyremote
Architecture: source
Version: 6.7.3-3
Distribution: unstable
Urgency: medium
Maintainer: Philipp Huebner 
Changed-By: Philipp Huebner 
Closes: 978584
Changes:
 anyremote (6.7.3-3) unstable; urgency=medium
 .
   * Added Breaks+Replaces: anyremote (<< 6.7.3-2) (Closes: #978584)
Checksums-Sha1:
 15d7127a6b3ed035aab8f6bee4fb27a0747e4574 2120 anyremote_6.7.3-3.dsc
 a8a853f8744a53b4112d452633cafd2dff4826bc 5260 anyremote_6.7.3-3.debian.tar.xz
 6358bced95831bdf6f231e429b3352340de513ec 8861 anyremote_6.7.3-3_amd64.buildinfo
Checksums-Sha256:
 0be6839800126eb059598dfe2eadd2a44d2fc1867474f24f1070488c081290d1 2120 
anyremote_6.7.3-3.dsc
 482c02edb3f965956b92b4c82118ac40763afbb009abc62e7afcd5a2b082f6d9 5260 
anyremote_6.7.3-3.debian.tar.xz
 328dc3eb6256d6c7fe7d2a71f28c3f8d6071bcb805e40f72eb2989e98eb71ac3 8861 
anyremote_6.7.3-3_amd64.buildinfo
Files:
 26183587aa44630196b631dabd1ca981 2120 utils optional anyremote_6.7.3-3.dsc
 a1438bfe1985422f005bdf909c007861 5260 utils optional 
anyremote_6.7.3-3.debian.tar.xz
 0689dae79c98cf12f760255761410257 8861 utils optional 
anyremote_6.7.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEECEGLvkRyDy26xQXsunokltrkDRwFAl/q/pMVHGRlYmFsYW5j
ZUBkZWJpYW4ub3JnAAoJELp6JJba5A0cGeAQAOl0gnuQ2tAr0AxCaZDCgPvy7S0f
nFb5VyY0POq0Jim3TEtJlBzzOUh4dzPZ9eCmV2hnG0J25AsMMSF3x/pK6VXXxwjL
COb8DHMyPPrTPy30+IRBJ5r4I4hXRijRzosVnBppZVcjcJUyOp7EYDYem4t7EDD/
0O6HIB8G9LOZPARXAkPfQvB9+lffbNgxUCWC7N+3j0bcovoz5vMr7BRfY2tVDMse
gCsGVjFJeMdSRdQg6Z1WLRIhq6mVcaM/fxj9/0S88pLS/G89WgVhqNOx3e7Ce5iK
6UHAsvF7A9Vku5zHi7k+anROLHt6uF/NOwAJ7fKSfXSI0Y3UJ4OuG+FPkrT+VjTP
ArPnXmzoqhQkeuFCNgJdAb1TYi0OQKJw293WIHviVLNF/h2Lo81PaZbAQxWfvce6
yltmDCI9oh75Gu2dmj5Q8iByuDPSs2txCWVJyelq4y/qGYZza1qFaVsD2duVGrKH
vQD2c4RjfIVVKaPoMf5b+N8GR2Zxe4DJxnIiCBYZ3T0XYGXwB8eEK9Nk7xSCll+c
Zq1VkkidOrKJRdbJas3geY3JYlUPFPKnD8Dk/pluXsiNW8TcYPEW+ROwwu1mgGEU
QbcwKluMK++ptTPUjRi6jE/z+PzAZh2xI2COuLVeJYE+BE14Xe0sO0MvL7CZtH90
0SAecZkERC5cftVX
=uHFZ
-END PGP SIGNATURE End Message ---

Bug#978510: marked as done (eso-midas: non-standard gcc/g++ used for build (gcc-9))

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 10:03:29 +
with message-id 
and subject line Bug#978510: fixed in eso-midas 19.02pl1.1-5
has caused the Debian Bug report #978510,
regarding eso-midas: non-standard gcc/g++ used for build (gcc-9)
to be marked as done.

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

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


-- 
978510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eso-midas
Severity: important
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-9, gcc-9-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-10/g++-10.  If the package cannot be built with GCC 10 because
of a compiler bug, please file a report for gcc-10.

Please keep this report open until the package uses the default
compiler version (or gcc-10) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.
--- End Message ---
--- Begin Message ---
Source: eso-midas
Source-Version: 19.02pl1.1-5
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated eso-midas 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, 28 Dec 2020 21:03:40 +0100
Source: eso-midas
Architecture: source
Version: 19.02pl1.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 978510
Changes:
 eso-midas (19.02pl1.1-5) unstable; urgency=medium
 .
   * Fix off-by-one error in tbread.c
   * Use "-fcommon -fno-strict-aliasing" instead of gcc 9. Closes: #978510
   * Push Standards-Version to 4.5.1. No changes needed
Checksums-Sha1:
 eccdf664c2e5585daefe4ac0a4599fcaa607821b 2180 eso-midas_19.02pl1.1-5.dsc
 febd25d1b1a5e6649173124ae583ec6fe0aaf3d0 10140 
eso-midas_19.02pl1.1-5.debian.tar.xz
Checksums-Sha256:
 8bc585d7ec2ac07e33f230a0e0899506663965d4549b23d3b0b6bd37408c 2180 
eso-midas_19.02pl1.1-5.dsc
 56a562951397c6f3aeb0186e420c5521be2b4d1dc131ea82ea29c3403429ad74 10140 
eso-midas_19.02pl1.1-5.debian.tar.xz
Files:
 bb186d4f504f0336766c2b12a37e98c1 2180 science optional 
eso-midas_19.02pl1.1-5.dsc
 82f201c744197cba2d3f3ec50ea053f7 10140 science optional 
eso-midas_19.02pl1.1-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl/q+Y4ACgkQcRWv0HcQ
3PfmNg/+OfjOz2THgW8ehnqQownPP3th2P1ClyX1tJgcDGAnmVkCjyBNH898BrrL
lESNOvO65bw98e7X6UjOo+8TB4bWtCGKulyFddZ7VEYGqJQ7BUFJnj2nk9MhxCMQ
qQMfJRssg6KN+nj28DKgzvh60WHm2iVH08AGFp2R93g7lb1FhkkI3KxHnAxuy6pE
dAuDbScP4x+gL0MSVvToDf0Vfj5iBwJdS6XR9bVvuafHuGVwn5gccF1BbdOZWYMD
5pxXc2IViL4dxhdHvVsQVXOK9a17LwTvVIjxSqHkxlhSuFumWS8Zovs6dU+0BHGZ
xldc4+cwpUPPqA0iI2uRrDo0/ZZJlZuTPDHqtY7Z4jIoFk+qNYhqtSNJVHaEt6h/
pQKdo1ajZs7FyPUcddz6lauKRVcsu3n1msqEub5L9WbEJeWs9R1FiTKQVo4zxEha
4eWfcL075UhlOdjIp730Vr0mwVDASllr7mX2VcIOm+LEcFV0/3hbkEsgt/K9JGaU
b4/wo7o1g8S4YoOyH3JzgbVBgqV3WTYgoiHcK4X7Bh0FUgShFAv7/1Vv0m1mn5ob
BN+d0l35jF8JkSs0d9LZ9x/hNVHhnXMbTmc0um3u8AbwpzLZPuK13y1EJQ71Qihg
Nkr0zFtJWSJ/AE+cZpf+CXBJY/Qq1gCkVEUx5F2EG6/9TOPTi7I=
=18sy
-END PGP SIGNATURE End Message ---

Bug#978616: mediastreamer2: doesn't build correct libraries with cmake?

[Gianfranco Costamagna]

Source: mediastreamer2
Version: 1:4.4.21-2
Severity: serious

Hello, looks like with autotools, the library provides libmediastreamer_base 
and libmediastreamer_voip,
while with cmake it doesn't.

the pkgconfig file is obviously wrong, but I don't know which solution you 
prefer (and if you are aware of this issue).

I propose two solutions:
1) implement the library split in cmake, and upstream it (this might be the 
preferred and easier solution to this issue)
2) patch pkgconfig file and cmake helpers to provide only one library to link.

if we choose 1, we should probably also change the ABI, so call it 
libmediastreamer11a or similar, to trigger a rebuild of reverse dependencies.

If you agree with 1) I can try to provide a patch as soon as possible.

thanks

Gianfranco

Bug#976921: marked as done (flatbuffers: FTBFS on ppc64el: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 09:48:55 +
with message-id 
and subject line Bug#976921: fixed in flatbuffers 
1.12.1~git20200711.33e2d80+dfsg1-0.4
has caused the Debian Bug report #976921,
regarding flatbuffers: FTBFS on ppc64el: dpkg-gensymbols: error: some symbols 
or patterns disappeared in the symbols file: see diff output below
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.)


-- 
976921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flatbuffers
Version: 1.12.1~git20200711.33e2d80+dfsg1-0.3
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el

Hi,

During a rebuild of all packages in sid, your package failed to build
on ppc64el. At the same time, it did not fail on amd64.

I'm marking this bug as severity:serious since your package currently has
ppc64el binary packages in unstable (so this is a regression).

Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-powerpc64le-linux-gnu'
> make[2]: Nothing to be done for 'preinstall'.
> make[2]: Leaving directory '/<>/obj-powerpc64le-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "None"
> -- Up-to-date: /<>/debian/tmp/usr/include/flatbuffers
> -- Up-to-date: /<>/debian/tmp/usr/include/flatbuffers/util.h
> -- Up-to-date: 
> /<>/debian/tmp/usr/include/flatbuffers/stl_emulation.h
> -- Up-to-date: /<>/debian/tmp/usr/include/flatbuffers/registry.h
> -- Up-to-date: 
> /<>/debian/tmp/usr/include/flatbuffers/reflection_generated.h
> -- Up-to-date: 
> /<>/debian/tmp/usr/include/flatbuffers/reflection.h
> -- Up-to-date: /<>/debian/tmp/usr/include/flatbuffers/pch
> -- Up-to-date: /<>/debian/tmp/usr/include/flatbuffers/pch/pch.h
> -- Up-to-date: 
> /<>/debian/tmp/usr/include/flatbuffers/pch/flatc_pch.h
> -- Up-to-date: 
> /<>/debian/tmp/usr/include/flatbuffers/minireflect.h
> -- Up-to-date: /<>/debian/tmp/usr/include/flatbuffers/idl.h
> -- Up-to-date: /<>/debian/tmp/usr/include/flatbuffers/hash.h
> -- Up-to-date: /<>/debian/tmp/usr/include/flatbuffers/grpc.h
> -- Up-to-date: 
> /<>/debian/tmp/usr/include/flatbuffers/flexbuffers.h
> -- Up-to-date: /<>/debian/tmp/usr/include/flatbuffers/flatc.h
> -- Up-to-date: 
> /<>/debian/tmp/usr/include/flatbuffers/flatbuffers.h
> -- Up-to-date: 
> /<>/debian/tmp/usr/include/flatbuffers/code_generators.h
> -- Up-to-date: /<>/debian/tmp/usr/include/flatbuffers/base.h
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/cmake/flatbuffers/FlatbuffersConfig.cmake
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/cmake/flatbuffers/FlatbuffersConfigVersion.cmake
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/libflatbuffers.a
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/cmake/flatbuffers/FlatbuffersTargets.cmake
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/cmake/flatbuffers/FlatbuffersTargets-none.cmake
> -- Up-to-date: /<>/debian/tmp/usr/bin/flatc
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/cmake/flatbuffers/FlatcTargets.cmake
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/cmake/flatbuffers/FlatcTargets-none.cmake
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/libflatbuffers.so.1.12.0
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/libflatbuffers.so.1
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/libflatbuffers.so
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/cmake/flatbuffers/FlatbuffersSharedTargets.cmake
> -- Up-to-date: 
> /<>/debian/tmp/usr/lib/powerpc64le-linux-gnu/cmake/flatbuffers/FlatbuffersSharedTargets-none.cmake
> make[1]: Leaving directory '/<>/obj-powerpc64le-linux-gnu'
>dh_install
>dh_installdocs
>dh_installchangelogs
>dh_python3
>dh_lintian
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libflatbuffers1/DEBIAN/symbols doesn't match 
> completely debian/libflatbuffers1.symbols
> --- debian/libflatbuffers1.symbols 
> (libflatbuffers1_1.12.1~git20200711.33e2d80+dfsg1-0.3_ppc64el)
> +++ dpkg-gensymbolsS9EYLh 2020-12-08 

Bug#976069: marked as done (python3-flatbuffers: Empty package)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 09:48:55 +
with message-id 
and subject line Bug#976069: fixed in flatbuffers 
1.12.1~git20200711.33e2d80+dfsg1-0.4
has caused the Debian Bug report #976069,
regarding python3-flatbuffers: Empty package
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.)


-- 
976069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flatbuffers
Version: 1.12.1~git20200711.33e2d80+dfsg1-0.3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I installed python3-flatbuffers and had the surprise that, in python3,
"import flatbuffers" was still giving
ModuleNotFoundError: No module named 'flatbuffers'

I then checked
$ dpkg -L python3-flatbuffers
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/python3-flatbuffers
/usr/share/doc/python3-flatbuffers/changelog.Debian.gz
/usr/share/doc/python3-flatbuffers/copyright

It appears that the package is empty? The package has no Depends: and
the description says "This package contains python3 flatbuffers API." so
it looks like a bug to me...

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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: flatbuffers
Source-Version: 1.12.1~git20200711.33e2d80+dfsg1-0.4
Done: Vasyl Gello 

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

Debian distribution maintenance software
pp.
Vasyl Gello  (supplier of updated flatbuffers package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Dec 2020 13:19:42 +
Source: flatbuffers
Architecture: source
Version: 1.12.1~git20200711.33e2d80+dfsg1-0.4
Distribution: unstable
Urgency: medium
Maintainer: Maximiliano Curia 
Changed-By: Vasyl Gello 
Closes: 976069 976921
Changes:
 flatbuffers (1.12.1~git20200711.33e2d80+dfsg1-0.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Make C++ template symbols optional and refresh them (Closes: #976921)
   * Bump standards version to 4.5.1 (no changes required)
   * Install python3-flatbuffers as indep (Closes: #976069)
Checksums-Sha1:
 411b624c405df15c84e793d3a4dbc1e4e809f1fa 2502 
flatbuffers_1.12.1~git20200711.33e2d80+dfsg1-0.4.dsc
 a9709ea6f5570f5545f6ef525deefdb76a4d7aca 13700 
flatbuffers_1.12.1~git20200711.33e2d80+dfsg1-0.4.debian.tar.xz
 2c87591a12b3d350c4e39ffc12ced8879d8dee63 9650 
flatbuffers_1.12.1~git20200711.33e2d80+dfsg1-0.4_amd64.buildinfo
Checksums-Sha256:
 fec35bddcc89a13414e1e0f0b2cfd3fc4cbae7dcefa379e4e92d0793c1de969f 2502 
flatbuffers_1.12.1~git20200711.33e2d80+dfsg1-0.4.dsc
 478cda1fe493d6c3aabaa4f0c955e59f5e472f65934eae5f7374a89e3563947e 13700 
flatbuffers_1.12.1~git20200711.33e2d80+dfsg1-0.4.debian.tar.xz
 ac19c1bde43595977480451f83ed52ebb14dc15e42e879f652f9521ad1aa2800 9650 
flatbuffers_1.12.1~git20200711.33e2d80+dfsg1-0.4_amd64.buildinfo
Files:
 0bb87897cf985ab4983c023c1a303b33 2502 devel optional 
flatbuffers_1.12.1~git20200711.33e2d80+dfsg1-0.4.dsc
 9d0bc60907acfc85ca6828a5ef57c9af 13700 devel optional 
flatbuffers_1.12.1~git20200711.33e2d80+dfsg1-0.4.debian.tar.xz
 00a3b579020fb0db7341d792b6143472 9650 devel optional 
flatbuffers_1.12.1~git20200711.33e2d80+dfsg1-0.4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAl/q9VoACgkQCBa54Yx2
K60itw/3ZbUm6SKYXEAQSUujD0mqlE5GZR6Ywelbgp2hgngOBYTxMNLfWmFlOQQC
ZfEPGRJfoeJeOQRolKUyvY/AvQ+Mg8snkev+lP83Mi+2u6gWyMDIVGHWtW8dcIT2

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 978376 mk-configure 0.35.0-1
Bug #978376 [src:paexec] paexec: FTBFS: bmake[2]: 
"/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for 
gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Bug reassigned from package 'src:paexec' to 'mk-configure'.
No longer marked as found in versions paexec/1.1.1-1.
Ignoring request to alter fixed versions of bug #978376 to the same values 
previously set
Bug #978376 [mk-configure] paexec: FTBFS: bmake[2]: 
"/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for 
gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Marked as found in versions mk-configure/0.35.0-1.
> affects 978376 paexec
Bug #978376 [mk-configure] paexec: FTBFS: bmake[2]: 
"/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for 
gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Added indication that 978376 affects paexec
> close 978376 0.35.really.0.33.0-1
Bug #978376 [mk-configure] paexec: FTBFS: bmake[2]: 
"/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for 
gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Marked as fixed in versions mk-configure/0.35.really.0.33.0-1.
Bug #978376 [mk-configure] paexec: FTBFS: bmake[2]: 
"/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for 
gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Marked Bug as done
> forcemerge 977908 978376
Bug #977908 {Done: Andrej Shadura } [mk-configure] 
mk-configure: Fails with 'Settings for gcc-10.2.1 is not available'
Bug #978271 {Done: Andrej Shadura } [mk-configure] 
inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 2
Bug #978387 {Done: Andrej Shadura } [mk-configure] runawk: 
FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 
'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Bug #978376 {Done: Alexander Ponyatikh } [mk-configure] 
paexec: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" 
line 112: 'Settings for gcc-10.2.1 is not available, run 
"mkc_compiler_settings" utility'
Removed indication that 978376 affects paexec
Bug #978271 {Done: Andrej Shadura } [mk-configure] 
inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 2
Bug #978387 {Done: Andrej Shadura } [mk-configure] runawk: 
FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 
'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Merged 977908 978271 978376 978387
> thanks
Stopping processing here.

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

Processed: Re: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #975696 [src:link-grammar] link-grammar: multi-thread test fails
Severity set to 'serious' from 'important'

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