Bug#986420: marked as done (ModuleNotFoundError: No module named 'gi' (missing dependency on python3-gi ?))

[Debian Bug Tracking System]

Your message dated Thu, 08 Apr 2021 03:03:22 +
with message-id 
and subject line Bug#986420: fixed in smart-notifier 0.28-7
has caused the Debian Bug report #986420,
regarding ModuleNotFoundError: No module named 'gi' (missing dependency on 
python3-gi ?)
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.)


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

Package: smart-notifier
Version: 0.28-6
Severity: important

Dear Maintainer,

smart-notifier does not depend on python3-gi.
When running smart-notifier, it fails:

$ smart-notifier
Traceback (most recent call last):
  File "/usr/bin/smart-notifier", line 13, in 
import smart_notifier.gui
  File "/usr/share/smart-notifier/smart_notifier/gui.py", line 23, in 
from gi.repository import Gtk
ModuleNotFoundError: No module named 'gi'


After installing python3-gi, smart-notifier runs fine and is able to show
notifications.

So I think smart-notifier should depend on python3-gi as it seems to be required
for proper GUI operation.
The failing import is made here:
https://sources.debian.org/src/smart-notifier/0.28-6/src/smart_notifier/gui.py/#L23

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

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages smart-notifier depends on:
ii  dbus1.12.20-1
ii  gir1.2-gtk-3.0  3.24.24-3
ii  python3 3.9.2-2
ii  python3-dbus1.2.16-4
ii  smartmontools   7.2-1

smart-notifier recommends no packages.

smart-notifier suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: smart-notifier
Source-Version: 0.28-7
Done: Chow Loong Jin 

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

Debian distribution maintenance software
pp.
Chow Loong Jin  (supplier of updated smart-notifier 
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, 08 Apr 2021 10:41:25 +0800
Source: smart-notifier
Architecture: source
Version: 0.28-7
Distribution: unstable
Urgency: medium
Maintainer: Chow Loong Jin 
Changed-By: Chow Loong Jin 
Closes: 986420
Changes:
 smart-notifier (0.28-7) unstable; urgency=medium
 .
   * [6b86063] Depend on python3-gi (Closes: #986420)
Checksums-Sha1:
 6a2b36c01727ef92e5ed1a091b6f4a2e7e027118 1883 smart-notifier_0.28-7.dsc
 e2a1464e633bf0e74ebc5a06bf10a2ed05d26b70 10356 
smart-notifier_0.28-7.debian.tar.xz
 4a802595bf353fa4ef2962e735bf61c6773ff4ac 8009 
smart-notifier_0.28-7_source.buildinfo
Checksums-Sha256:
 9db8b262a2da8daca8c3663b57bb7436a5db925b048c727b992514eaf7d3304d 1883 
smart-notifier_0.28-7.dsc
 9a099d403438930f61d9ffd3d0af88b5229f93d133e80bec3009056999ef5057 10356 
smart-notifier_0.28-7.debian.tar.xz
 b1532dfb2e3fbe7ecf535b020a501741005d1eb4fa478d76635111447eef04dd 8009 
smart-notifier_0.28-7_source.buildinfo
Files:
 0eca009ba6c8a39c9c29a31b650940d1 1883 utils optional smart-notifier_0.28-7.dsc
 e1c6bac8422f52176642b25d20014db3 10356 utils optional 
smart-notifier_0.28-7.debian.tar.xz
 297862bea53430be50a95f3e22186777 8009 utils optional 
smart-notifier_0.28-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEEuDQnfs/9/dZ027Q+9UiW1iHUqEFAmBubnkACgkQ+9UiW1iH
UqGYYg/9GX1eOb9fBDUhBNIk79+bpFz3aeKXvGNskc4SjYqSucPNGLY8KfGYQBw3
Sw+jYBdnRrO8nXxirlY0yEnQWsYOR6s0Pe3inK2/cbQYhz+13E5uCwbnMCCLGKxC
PnxxKf3X82yrMLv+egNQ1D9/oLeaAu3cFhqBwtBn7AMY3D2/E5KKg0L0sk9MfY/x
HzGUg4pbidhGg3kvioQkRp6pyIJv1c3JRmcU7FFWgQV8VuO89XCMB9+vvm4I2fg0
GvDUsH27jqlvavMzb6ctuKdjuvAq8WSHm3cywzMQPReP94i9gbyHY//QmD/LHFdT
HBBSIZYUNf3GhNHyFkuvARb2tsGcnHcvKexp9nyjG1/dK7CfqVrnVg36GX3asW1v

Processed: forcemerge

[Debian Bug Tracking System]

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

> forcemerge 986612 856963
Bug #986612 [wnpp] ITP: sass-stylesheets-purecss -- set of small, responsive 
Sass and CSS modules
Bug #856963 [wnpp] ITP: purecss -- set of small and responsive CSS modules
980134 was blocked by: 978697 856963
980134 was not blocking any bugs.
Removed blocking bug(s) of 980134: 856963
986607 was blocked by: 856963
986607 was not blocking any bugs.
Removed blocking bug(s) of 986607: 856963
856963 was blocked by: 986610
856963 was not blocking any bugs.
Removed blocking bug(s) of 856963: 986610
Owner changed from James Valleroy  to Jonas Smedegaard 
.
Merged 856963 986612
> thanks
Stopping processing here.

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

Bug#985948: libubootenv-tool: Debug lines from fw_printenv break RAUC

[Nobuhiro Iwamatsu]

Hi all,

2021年4月7日(水) 18:39 Andreas Henriksson :
>
> Control: severity -1 grave
>
> On Wed, Apr 07, 2021 at 11:20:18AM +0200, Bastian Germann wrote:
> > Control: severity -1 important
> >
> > Am 07.04.21 um 11:10 schrieb Andreas Henriksson:
> > > Could we please just add a patch that either just rips out the NDEBUG
> > > lines (or inverts the login to #ifdef DEBUG ) ?! Such a patch could/should
> > > be forwarded upstream as well A library should not print to stdout
> > > like this!
> > I am not the maintainer.
>
> I agree that the maintainer should have done a better job at reviewing
> rather than blindly applying your patch and also verifying that the new
> version actually fixes the bugs that is claimed to be closed in the
> changelog.
>
> People must have been sleeping while writing this debian/rules
> file. Most content is entirely unused because cmake build type
> is *not* release!
>
> > You can hand in such a patch to speed up that process.
>
> I've submitted a merge-request that fixes the imminent problems for
> review at:
> https://salsa.debian.org/debian/libubootenv/-/merge_requests/3
>
> Please not that I'm nowhere near a cmake expert. I've only fixed
> the imminent bug and some glaring problems in debian/rules.
> I've left comments in commit messages about further improvements,
> but there are likely entirely different and better ways of
> doing things.

Thank you for the patch. I will review this carefully.

>
> > I am reducing the severity as pointed out before.
>
> And I'm raising it back up again, because this is definitely an RC bug.
> Breaking the output of fw_printenv breaks multiple programs (including
> but not limited to mender-client) which parses that output.
>

I agree about this.

Best regards,
  Nobuhiro


-- 
Nobuhiro Iwamatsu

Processed: kpatch: Package quite out of date wrt. to upstream releases (0.6.0 vs 0.9.2)

[Debian Bug Tracking System]

Processing control commands:

> tag 983648 + fixed-upstream
Bug #983648 [kpatch-dkms] kpatch-dkms: fails to build module for Linux 5.10: 
uses unknown struct stack_trace
Added tag(s) fixed-upstream.
> block 983648 by -1
Bug #983648 [kpatch-dkms] kpatch-dkms: fails to build module for Linux 5.10: 
uses unknown struct stack_trace
983648 was not blocked by any bugs.
983648 was not blocking any bugs.
Added blocking bug(s) of 983648: 986613

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

Bug#962596: Divergence in Symantec CA blacklist reverting

[Loïc Sharma]

Hello,

I am from the NuGet team at Microsoft. Network Security Services (NSS) 3.63 and 
newer distrusts Symantec which will cause failures when installing NuGet 
packages. For more information, please see:


  *   https://github.com/dotnet/announcements/issues/180
  *   https://github.com/NuGet/Announcements/issues/56

Does Debian have a timeline for when it will update to NSS 3.63 or newer? Will 
this result in Debian distrusting the Symantec CA again, or will the allowlist 
from DLA 
2593-1 be 
kept? If this causes Debian to distrust Symantec CA, which versions of Debian 
will be affected?

Best,
Loic

Processed: severity of 986552 is important

[Debian Bug Tracking System]

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

> severity 986552 important
Bug #986552 [src:linux] linux-image-4.19.0-14-amd64: KVM crashes with list_add 
corruption kernel BUG
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#986603: courier-MLM : it runs as root ? or we must manually set up as coureir user?

[PICCORO McKAY Lenz]

Package: courier-mlm
Version: 1.0.14-1
Severity: grave
Justification: renders package unusable

now found is a debian problem, the courier-mlm documents said in clear way
that cannot be use any shell constructs or script trick, and cannot use quotes,
the debian file has: PIDFILE={PORT}.pid and with previous PORT as
PORT="/run/courier/webmlmd" and init sysv scripts uses quotest..

so i always got this error wherever tyope of init system i used

abr 07 12:56:37 isomaker systemd[1]: courier-mlm.service: PID file
/run/courier/webmlmd.pid no such file or directory

after disabled all the systemd and start in sysvinit only mode
I got the same error.. i check that in debian package the courier-mlm
defines PIDDIR as a shell banish.. and use coutes in the sysvinit script,
so both units will fail always

i try to restart the courier mlm after correctly setup the lists,
the PIDFILE (with no quotes or shell constructs) and PIDFILE,
usin hardcoded path and problem solved..

so the solution is remove the shistemd unit (due the unable to handle
the problem of the mail list empty, check bug #979161 [1] )
or fix the pid definition with hardcoded path in the webmlmrc file

courier sources defines @piddir@ etc etc and when install uses hardcoded paths
so must fix that!

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

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com


El mié, 7 de abr. de 2021 a la(s) 13:03, PICCORO McKAY Lenz
(mckaygerh...@gmail.com) escribió:
>
> i try to restart the courier mlm after correctly setup the lists
>
> but i got this using sysvinit or shitstemd :
>
> abr 07 12:56:37 serveruno systemd[1]: courier-mlm.service: PID file 
> /run/courier/webmlmd.pid no such file or directory
>
> after check the file is there, but owned by root and named differently:
>
> /run/courier/webmlm.sock
> /run/courier/webmlm.pid
>
> the shitstemd service unit defined with the stupid "d" at the end.. i ask 
> them:
>
> where is defined and what is the defaults for courier if i build from cources 
> and not used the debian package?
>
> Lenz McKAY Gerardo (PICCORO)
> http://qgqlochekone.blogspot.com

Bug#986256: marked as done (simka: flaky amd64 autopkgtest: regularly times out after 2:47 h)

[Debian Bug Tracking System]

Your message dated Wed, 07 Apr 2021 21:48:59 +
with message-id 
and subject line Bug#986256: fixed in simka 1.5.3-4
has caused the Debian Bug report #986256,
regarding simka: flaky amd64 autopkgtest: regularly times out after 2:47 h
to be marked as done.

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

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


-- 
986256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simka
Version: 1.5.3-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky timeout

Dear maintainer(s),

Your package has an autopkgtest, great. However, I looked into
the history of your autopkgtest [1] and I noticed version 1.5.3-2 fails
regularly on amd64, while sporadically a rerun passes. I copied some of
the output at the bottom of this report. It hits the autopkgtest time
out after 2hours and 47 minutes. Successful runs pass in less than a minute.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Paul

[1] https://ci.debian.net/packages/s/simka/testing/amd64/

https://ci.debian.net/data/autopkgtest/testing/amd64/s/simka/11355132/log.gz

Computing stats...

Stats
Reads
Total:8470M0G
Min:980M0G
Max:4020M0G
Average:1690M0G
Kmers
Distinct Kmers (before merging):146700M0G
Distinct Kmers (after merging):81230M0G
Shared distinct Kmers:43220M0G
Kmers:501300M0G
Mean k-mer coverage: 2.66341


Output dir: ./simka_results/




*** Test: PASSED

Command used:
/usr/bin/simka -in ../example/simka_input.txt -out ./simka_results/
-out-tmp ./simka_temp_output

Command for visualizing results:
python ../scripts/visualization/run-visualization.py -in
./simka_results/ -out ./simka_results/ -pca -heatmap -tree

Command for visualizing results with metadata annotations:
python ../scripts/visualization/run-visualization.py -in
./simka_results/ -out ./simka_results/ -pca -heatmap -tree -metadata-in
../example/dataset_metadata.csv -metadata-variable VARIABLE_1
autopkgtest [07:42:20]: ERROR: timed out on command "su -s /bin/bash
debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
true;  . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/build.NZn/src"; mkdir
-p -m 1777 --
"/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/autopkgtest_tmp";
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=48; unset
LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY
LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod
+x
/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/build.NZn/src/debian/tests/run-unit-test;
touch /tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-stdout
/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-stderr;
/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/build.NZn/src/debian/tests/run-unit-test
2> >(tee -a /tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-stderr
>&2) > >(tee -a
/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-stdout);" (kind: test)
autopkgtest [07:42:20]: test run-unit-test: ---]



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: simka
Source-Version: 1.5.3-4
Done: Étienne Mollier 

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

Processed: severity of 986577 is serious

[Debian Bug Tracking System]

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

> severity 986577 serious
Bug #986577 [bouncy] bouncy: Fails to run without missing dependency 
python3-future
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#986513: marked as done (puppetlabs-http-client-clojure: FTBFS: ERROR in (sync-client-test-ssl-protocols) (HttpAsyncRequestExecutor.java:356) should not connect to a server when protocols don't ove

[Debian Bug Tracking System]

Your message dated Wed, 07 Apr 2021 21:33:36 +
with message-id 
and subject line Bug#986513: fixed in puppetlabs-http-client-clojure 1.2.0-2
has caused the Debian Bug report #986513,
regarding puppetlabs-http-client-clojure: FTBFS: ERROR in 
(sync-client-test-ssl-protocols) (HttpAsyncRequestExecutor.java:356) should not 
connect to a server when protocols don't overlap clojure sync client
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.)


-- 
986513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: puppetlabs-http-client-clojure
Version: 1.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein test
> 
> lein test com.puppetlabs.http.client.impl.java-client-test
> 
> lein test com.puppetlabs.http.client.impl.metrics-unit-test
> 
> lein test puppetlabs.http.client.async-plaintext-test
> 
> lein test puppetlabs.http.client.async-unbuffered-test
> 
> lein test puppetlabs.http.client.gzip-request-test
> 
> lein test puppetlabs.http.client.metrics-test
> 
> lein test puppetlabs.http.client.sync-plaintext-test
> 
> lein test puppetlabs.http.client.sync-ssl-test
> 
> lein test :only 
> puppetlabs.http.client.sync-ssl-test/sync-client-test-ssl-protocols
> 
> ERROR in (sync-client-test-ssl-protocols) (HttpAsyncRequestExecutor.java:356)
> should not connect to a server when protocols don't overlap clojure sync 
> client
> expected: (thrown? SSLException (clj-https-get-with-protocols ["TLSv1.2"] 
> nil))
>   actual: org.apache.http.ConnectionClosedException: Connection is closed
>  at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.endOfInput 
> (HttpAsyncRequestExecutor.java:356)
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput 
> (DefaultNHttpClientConnection.java:261)
> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady 
> (InternalIODispatch.java:81)
> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady 
> (InternalIODispatch.java:39)
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady 
> (AbstractIODispatch.java:121)
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable 
> (BaseIOReactor.java:162)
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent 
> (AbstractIOReactor.java:337)
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents 
> (AbstractIOReactor.java:315)
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute 
> (AbstractIOReactor.java:276)
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute 
> (BaseIOReactor.java:104)
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run 
> (AbstractMultiworkerIOReactor.java:591)
> java.lang.Thread.run (Thread.java:829)
> 
> lein test puppetlabs.http.client.test-common
> 
> Ran 84 tests containing 733 assertions.
> 0 failures, 1 errors.
> Tests failed.
> make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2021/04/06/puppetlabs-http-client-clojure_1.2.0-1_testing.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 mine
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-2
Done: Louis-Philippe Véronneau 

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 986...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software

Processed: severity of 986420 is serious

[Debian Bug Tracking System]

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

> severity 986420 serious
Bug #986420 [smart-notifier] ModuleNotFoundError: No module named 'gi' (missing 
dependency on python3-gi ?)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#986256: [Debian-med-packaging] Bug#986256: simka: flaky amd64 autopkgtest: regularly times out after 2:47 h

[Étienne Mollier]

Hi Graham,

Graham Inggs, on 2021-04-06 20:15:30 +0200:
> This is still occurring with simka 1.5.3-3, see:
> https://ci.debian.net/packages/s/simka/testing/amd64/

Thanks for having noticed it.  It looks like I got caught by the
Python script not taking the -nb-cores argument, contrary to the
shell script.  While I couldn't reproduce the hang on emulator,
it seems I can just reproduce the problem by enforcing the cores
count to 48 within the Python script.  The test is precisely
hanging at this location:

[...]
Command for visualizing results with metadata annotations:
python ../scripts/visualization/run-visualization.py -in 
./simka_results/ -out ./simka_results/ -pca -heatmap -tree -metadata-in 
../example/dataset_metadata.csv -metadata-variable VARIABLE_1
TESTING k=31 t=0
simka -in simka_input.txt -out ./__results__/results_k31_t0 -out-tmp 
./temp_output -simple-dist -complex-dist -kmer-size 31 -abundance-min 0 
-verbose 0 -nb-cores 48
OK
TESTING k=21 t=0
simka -in simka_input.txt -out ./__results__/results_k21_t0 -out-tmp 
./temp_output -simple-dist -complex-dist -kmer-size 21 -abundance-min 0 
-verbose 0 -nb-cores 48
OK
TESTING k=31 t=2
simka -in simka_input.txt -out ./__results__/results_k31_t2 -out-tmp 
./temp_output -simple-dist -complex-dist -kmer-size 31 -abundance-min 2 
-verbose 0 -nb-cores 48
_

The output on CI infrastructure is a bit misleading, because the
standard output is not flushed on each output line by default.
I enforced flushed output manually in the Python script to have
a cleared view.  But I /believe/ I could reproduce precisely the
deadlock this time.  Hopefully a further upload with controlled
cores count at this level should do the trick.

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#986592: kleborate: flaky arm64 autopkgtest: Mutex is not owned by current thread

[Aaron M. Ucko]

Andreas Tille  writes:

> do you have possibly any hint what might be wrong here?

Thanks for calling this bug to my attention!  Based on reports I've seen
upstream, I suspect the problem may lie in some relatively new
usage-reporting code that Debian should probably disable by default
regardless, in retrospect.  I'll look into it.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Processed: Bug#986513 marked as pending in puppetlabs-http-client-clojure

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #986513 [src:puppetlabs-http-client-clojure] 
puppetlabs-http-client-clojure: FTBFS: ERROR in 
(sync-client-test-ssl-protocols) (HttpAsyncRequestExecutor.java:356) should not 
connect to a server when protocols don't overlap clojure sync client
Added tag(s) pending.

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

Bug#986513: marked as pending in puppetlabs-http-client-clojure

[Louis-Philippe Véronneau]

Control: tag -1 pending

Hello,

Bug #986513 in puppetlabs-http-client-clojure reported by you has been fixed in 
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/clojure-team/puppetlabs-http-client-clojure/-/commit/8620347ad4478c45e0eaf9ed2cfd5c2c5df98e6d


d/patches: skip minor test failing. (Closes: #986513)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/986513

Bug#983492: marked as done (alien incorrectly generates debian/rules)

[Debian Bug Tracking System]

Your message dated Wed, 07 Apr 2021 20:18:48 +
with message-id 
and subject line Bug#983492: fixed in alien 8.95.4
has caused the Debian Bug report #983492,
regarding alien incorrectly generates debian/rules
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.)


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

Dear Maintainer,

It appears, sometime between 8.95 and 8.95.3, alien started generating 
incorrect debian/rules output, resulting in it being unable to convert at least 
RPMs[1] into DEBs successfully (though I'm guessing it broke everything.)

In particular, it generates debian/rules that look like:

%:
dh

when the clear intention from reading the source is to generate:

%:
dh $@

The patch below corrects this behavior, and allows alien to correctly generate 
DEBs in at least the RPM packages I was testing with.

--- ./blib/lib/Alien/Package/Deb.pm.old 2021-02-24 20:25:49.896411306 -0500
+++ ./blib/lib/Alien/Package/Deb.pm 2021-02-24 20:26:06.868446646 -0500
@@ -472,7 +472,7 @@
 PACKAGE=\$(shell dh_listpackages)

 %:
-   dh $@
+   dh \$\@

 override_dh_clean:
dh_clean -d


Hopefully someone will apply this at some point, though I'm aware alien is 
currently unmaintained.

- Rich

[1] - cf. https://github.com/openzfs/zfs/issues/11650 

-- System Information:
Debian Release: 10.8
  APT prefers stable
  APT policy: (1000, 'stable'), (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (500, 'stable-updates'), (500, 
'stable-debug'), (500, 'proposed-updates-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages alien depends on:
ii  cpio   2.12+dfsg-9
ii  debhelper  12.1.1
ii  dpkg-dev   1.19.7
ii  make   4.2.1-1.2
ii  perl   5.28.1-6+deb10u1
ii  rpm4.14.2.1+dfsg1-1
ii  rpm2cpio   4.14.2.1+dfsg1-1

alien recommends no packages.

Versions of packages alien suggests:
ii  bzip21.0.6-9.2~deb10u1
ii  lintian  2.15.0
ii  lzma 9.22-2.1
ii  patch2.7.6-3+deb10u1
ii  xz-utils [lzma]  5.2.4-1

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/perl5/Alien/Package/Deb.pm (from alien package)
--- End Message ---
--- Begin Message ---
Source: alien
Source-Version: 8.95.4
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated alien 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, 07 Apr 2021 12:15:06 -0400
Source: alien
Architecture: source
Version: 8.95.4
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 983492 985808 985835
Changes:
 alien (8.95.4) unstable; urgency=high
 .
   * QA upload.
   * Alien/Package/Deb.pm: Fix incorrect debian/rules template by
 properly escaping special characters (dh \$\@ instead of dh $@).
 Closes: #983492.
   * Alien/Package/Deb.pm: Fix incorrect file installation path.
 This fixes the bug in manual override_dh_auto_install that files
 are placed under / instead of /usr/ (default prefix).
 Closes: #985835.
   * Alien/Package/Rpm.pm: Also map aarch64 in rpm to arm64 in deb.
 This fixes conversion of aarch64 rpm packages.
 Closes: #985808.
Checksums-Sha1:
 56b0e90f03556fbc247302b033e5d2bea1f85f9f 1542 alien_8.95.4.dsc
 abb15df6e5b5ae752d49a2918e9833a81906c589 57916 alien_8.95.4.tar.xz
 b091fdbd6508868ec3b6693ced52b89a843e20a7 5564 

Processed: Re: Bug#986592: kleborate: flaky arm64 autopkgtest: Mutex is not owned by current thread

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #986592 [src:kleborate] kleborate: flaky arm64 autopkgtest: Mutex is not 
owned by current thread
Added tag(s) help.

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

Bug#986592: kleborate: flaky arm64 autopkgtest: Mutex is not owned by current thread

[Andreas Tille]

Control: tags -1 help

Hi Aaron,

do you have possibly any hint what might be wrong here?

Kind regards

   Andreas.

On Wed, Apr 07, 2021 at 09:35:42PM +0200, Paul Gevers wrote:
> Source: kleborate
> Version: 2.0.1-1
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: flaky
> 
> Dear maintainer(s),
> 
> Your package has an autopkgtest, great. However, I looked into the
> history of your autopkgtest [1] and I noticed the it fails regularly on
> ppc64el, while a rerun passes. I copied some of the output at the bottom
> of this report. It's not always the same place where the issue acures.
> 
> Because the unstable-to-testing migration software now blocks on
> regressions in testing, flaky tests, i.e. tests that flip between
> passing and failing without changes to the list of installed packages,
> are causing people unrelated to your package to spend time on these
> tests.
> 
> Paul
> PS: if you fix this for bullseye, our migration tooling will not
> correctly detect it can migrate according to the freeze rules due to it
> scheduling tests on i386 and armhf where no arch specific package is
> built. Ping me and if otherwise OK, I'll hint it through.
> 
> [1] https://ci.debian.net/packages/k/kleborate/testing/arm64/
> 
> https://ci.debian.net/data/autopkgtest/testing/arm64/k/kleborate/11152715/log.gz
> 
> 
> autopkgtest [09:23:49]: test run-unit-test: [---
> strainspecies ST  virulence_score Yersiniabactin  YbST
> Colibactin  CbST
> AerobactinAbSTSalmochelin SmSTRmpADC  RmSTrmpA2   wzi 
> K_locus
> Klebs_HS11286 Klebsiella pneumoniae   ST111   ybt 9;
> ICEKp315  -   0   -   0   -   0   -   
> 0   -   wzi74   KL103
> Klebs_Kp1084  Klebsiella pneumoniae   ST232   ybt 1; ICEKp10  47
> clb 2 37  -   0   -   0   -   0   -   wzi172  
> KL1
> MGH78578  Klebsiella pneumoniae   ST380   -   0   -   
> 0   -   0   -   0   -   0   -   wzi50   KL15
> (KL17,KL51,KL52)
> NTUH-K2044Klebsiella pneumoniae   ST234   ybt 2; ICEKp1   326 
> -   0   iuc 1   1
> iro 1,iro 3   19,18   rmp 3; ICEKp1,rmp 1; KpVP-1 30-1LV,26   
> rmpA2_3-47% wzi1KL1
> strainspecies ST  virulence_score resistance_score
> Yersiniabactin
> YbST  Colibactin  CbSTAerobactin  AbSTSalmochelin SmST
> RmpADC  RmST
> rmpA2 wzi K_locus AGly_acquired   Col_acquiredFcyn_acquired
> Flq_acquired  Gly_acquiredMLS_acquiredPhe_acquiredRif_acquired
> Sul_acquired  Tet_acquiredTgc_acquiredTmt_acquiredBla_acquired
> Bla_inhR_acquired Bla_ESBL_acquired   Bla_ESBL_inhR_acquired
> Bla_Carb_acquired Bla_chr SHV_mutations   Omp_mutations   Col_mutations
> Flq_mutations truncated_resistance_hits   spurious_resistance_hits
> Klebs_HS11286 Klebsiella pneumoniae   ST111   3   ybt 9;
> ICEKp315  -   0   -   0   -   0   -   
> 0   -   wzi74   KL103
> aadA2^;rmtB;strA.v1^;strB.v1  -   -   -   -   -   -   
> -   sul2tet(G).v1   -   dfrA12*
> TEM-1;TEM-1;TEM-1 -   CTX-M-14;CTX-M-14   -   KPC-2   
> SHV-11.v1   35Q
> OmpK35-40%PmrB-10%GyrA-83I;ParC-80I   aac(3)-IId*?-0% 
> floR.v2*?;sul1?-63%
> Klebs_Kp1084  Klebsiella pneumoniae   ST232   0   ybt 1; ICEKp10  
> 47
> clb 2 37  -   0   -   0   -   0   -   wzi172  
> KL1 -   -   -   -   -   -   -   -   - 
>   -   -   -   -   -   -   -   -
> SHV-11.v1^35Q -   -   -   -   -
> MGH78578  Klebsiella pneumoniae   ST380   1   -   0   
> -   0   -   0   -   0   -   0   -   wzi50
> KL15 (KL17,KL51,KL52)
> aac(6')-Ib'.v1;aadA*;ant(2'')-Ia;aph(3')-Ia;strA.v1;strB.v1   -   -   
> -   -   -
> catA1*;cmlA5  -   sul1;sul2   tet(D)  -   -   
> TEM-1D.v1^;TEM-1D.v1^   -
> SHV-12-   -   SHV-11.v1^  238S;240K;35Q;35Q   
> OmpK35-86%  -   GyrA-83Y
> OXA-9.v1*-42% -
> NTUH-K2044Klebsiella pneumoniae   ST234   0   ybt 2; ICEKp1   
> 326 -   0   iuc 1   1
> iro 1,iro 3   19,18   rmp 3; ICEKp1,rmp 1; KpVP-1 30-1LV,26   
> rmpA2_3-47%
> wzi1  KL1 -   -   -   -   -   -   -   -   
> -   -   -   -   -   -   -   -   -   
> SHV-11.v1^  35Q -   -   -   -   -
> strainspecies ST  virulence_score resistance_score
> Yersiniabactin
> YbST  Colibactin  CbSTAerobactin  AbSTSalmochelin SmST
> 

Bug#986513: puppetlabs-http-client-clojure: FTBFS: ERROR in (sync-client-test-ssl-protocols) (HttpAsyncRequestExecutor.java:356) should not connect to a server when protocols don't overlap clojure syn

[Louis-Philippe Véronneau]

I have been able to reproduce this bug locally with sbuild, on a machine
that has network access.

This is thus not a failure caused by a network connection being required
to the testsuite.

I opened a bug upstream
(https://github.com/puppetlabs/clj-http-client/issues/85) but the
failure seems pretty minor and doesn't seem Debian-specific, so I'll
just skip it.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#983492: alien incorrectly generates debian/rules

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #983492 [alien] alien incorrectly generates debian/rules
Severity set to 'grave' from 'important'

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

Bug#986592: kleborate: flaky arm64 autopkgtest: Mutex is not owned by current thread

[Paul Gevers]

Source: kleborate
Version: 2.0.1-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

Your package has an autopkgtest, great. However, I looked into the
history of your autopkgtest [1] and I noticed the it fails regularly on
ppc64el, while a rerun passes. I copied some of the output at the bottom
of this report. It's not always the same place where the issue acures.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Paul
PS: if you fix this for bullseye, our migration tooling will not
correctly detect it can migrate according to the freeze rules due to it
scheduling tests on i386 and armhf where no arch specific package is
built. Ping me and if otherwise OK, I'll hint it through.

[1] https://ci.debian.net/packages/k/kleborate/testing/arm64/

https://ci.debian.net/data/autopkgtest/testing/arm64/k/kleborate/11152715/log.gz


autopkgtest [09:23:49]: test run-unit-test: [---
strain  species ST  virulence_score Yersiniabactin  YbSTColibactin  
CbST
Aerobactin  AbSTSalmochelin SmSTRmpADC  RmSTrmpA2   wzi 
K_locus
Klebs_HS11286   Klebsiella pneumoniae   ST111   ybt 9;
ICEKp3  15  -   0   -   0   -   0   -   0   
-   wzi74   KL103
Klebs_Kp1084Klebsiella pneumoniae   ST232   ybt 1; ICEKp10  47
clb 2   37  -   0   -   0   -   0   -   wzi172  
KL1
MGH78578Klebsiella pneumoniae   ST380   -   0   -   
0   -   0   -   0   -   0   -   wzi50   KL15
(KL17,KL51,KL52)
NTUH-K2044  Klebsiella pneumoniae   ST234   ybt 2; ICEKp1   326 
-   0   iuc 1   1
iro 1,iro 3 19,18   rmp 3; ICEKp1,rmp 1; KpVP-1 30-1LV,26   
rmpA2_3-47% wzi1KL1
strain  species ST  virulence_score resistance_scoreYersiniabactin
YbSTColibactin  CbSTAerobactin  AbSTSalmochelin SmST
RmpADC  RmST
rmpA2   wzi K_locus AGly_acquired   Col_acquiredFcyn_acquired
Flq_acquiredGly_acquiredMLS_acquiredPhe_acquiredRif_acquired
Sul_acquiredTet_acquiredTgc_acquiredTmt_acquiredBla_acquired
Bla_inhR_acquired   Bla_ESBL_acquired   Bla_ESBL_inhR_acquired
Bla_Carb_acquired   Bla_chr SHV_mutations   Omp_mutations   Col_mutations
Flq_mutations   truncated_resistance_hits   spurious_resistance_hits
Klebs_HS11286   Klebsiella pneumoniae   ST111   3   ybt 9;
ICEKp3  15  -   0   -   0   -   0   -   0   
-   wzi74   KL103
aadA2^;rmtB;strA.v1^;strB.v1-   -   -   -   -   -   
-   sul2tet(G).v1   -   dfrA12*
TEM-1;TEM-1;TEM-1   -   CTX-M-14;CTX-M-14   -   KPC-2   
SHV-11.v1   35Q
OmpK35-40%  PmrB-10%GyrA-83I;ParC-80I   aac(3)-IId*?-0% 
floR.v2*?;sul1?-63%
Klebs_Kp1084Klebsiella pneumoniae   ST232   0   ybt 1; ICEKp10  
47
clb 2   37  -   0   -   0   -   0   -   wzi172  
KL1 -   -   -   -   -   -   -   -   -   
-   -   -   -   -   -   -   -
SHV-11.v1^  35Q -   -   -   -   -
MGH78578Klebsiella pneumoniae   ST380   1   -   0   
-   0   -   0   -   0   -   0   -   wzi50
KL15 (KL17,KL51,KL52)
aac(6')-Ib'.v1;aadA*;ant(2'')-Ia;aph(3')-Ia;strA.v1;strB.v1 -   -   
-   -   -
catA1*;cmlA5-   sul1;sul2   tet(D)  -   -   
TEM-1D.v1^;TEM-1D.v1^   -
SHV-12  -   -   SHV-11.v1^  238S;240K;35Q;35Q   OmpK35-86%  
-   GyrA-83Y
OXA-9.v1*-42%   -
NTUH-K2044  Klebsiella pneumoniae   ST234   0   ybt 2; ICEKp1   
326 -   0   iuc 1   1
iro 1,iro 3 19,18   rmp 3; ICEKp1,rmp 1; KpVP-1 30-1LV,26   
rmpA2_3-47%
wzi1KL1 -   -   -   -   -   -   -   -   
-   -   -   -   -   -   -   -   -   
SHV-11.v1^  35Q -   -   -   -   -
strain  species ST  virulence_score resistance_scoreYersiniabactin
YbSTColibactin  CbSTAerobactin  AbSTSalmochelin SmST
RmpADC  RmST
rmpA2   wzi K_locus K_locus_confidence  O_locus O_locus_confidence
AGly_acquired   Col_acquiredFcyn_acquired   Flq_acquiredGly_acquired
MLS_acquiredPhe_acquiredRif_acquiredSul_acquiredTet_acquired
Tgc_acquiredTmt_acquiredBla_acquiredBla_inhR_acquired
Bla_ESBL_acquired   Bla_ESBL_inhR_acquired 

Bug#986590: dbus-test-runner: flaky ppc64el autopkgtest: FAIL test-libdbustest-mock-test (exit status: 1)

[Paul Gevers]

Source: dbus-test-runner
Version: 16.10.0~bzr100+repack1-4.1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org, t...@canonical.com
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

Your package has an autopkgtest, great. However, I looked into
the history of your autopkgtest [1] and I noticed the it fails regularly
on ppc64el, while a rerun passes. I copied some of the output
at the bottom of this report. As far as I checked, it's always the same
issue.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Paul

[1] https://ci.debian.net/packages/d/dbus-test-runner/testing/ppc64el/

https://ci.debian.net/data/autopkgtest/testing/ppc64el/d/dbus-test-runner/11196676/log.gz

FAIL: ./test-libdbustest-mock
FAIL test-libdbustest-mock-test (exit status: 1)


Testsuite summary for dbus-test-runner 15.04.0

# TOTAL: 36
# PASS:  16
# SKIP:  0
# XFAIL: 19
# FAIL:  1
# XPASS: 0
# ERROR: 0



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: network-manager-iodine FTBFS with glib 2.58

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #908017 [src:network-manager-iodine] network-manager-iodine FTBFS with glib 
2.58
Added tag(s) patch.

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

Bug#908017: network-manager-iodine FTBFS with glib 2.58

[Logan Rosen]

Control: tags -1 patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/rules: Set --enable-more-warnings to "yes" so that it doesn't default to
"error," which turns every warning into an error and causes an FTBFS due
to deprecated declarations.

Thanks for considering the patch.

Logan
diff -Nru network-manager-iodine-1.2.0/debian/rules 
network-manager-iodine-1.2.0/debian/rules
--- network-manager-iodine-1.2.0/debian/rules   2018-01-22 03:55:32.0 
-0500
+++ network-manager-iodine-1.2.0/debian/rules   2021-04-07 14:10:53.0 
-0400
@@ -11,7 +11,8 @@
dh_auto_configure -- \
--libexecdir=/usr/lib/NetworkManager \
--disable-static \
-   --without-libnm-glib
+   --without-libnm-glib \
+   --enable-more-warnings=yes
 
 override_dh_makeshlibs:
dh_makeshlibs -X/usr/lib/$(DEB_HOST_MULTIARCH)/NetworkManager/

Bug#907308: Upstream bug

[Jan Hudec]

The bug occurs on all systems with sufficiently new GNU libc, not just Debian, 
so it is an upstream bug.

Unfortunately the mailing list mentioned on the linked homepage is dead (even 
the server is) and I failed to find any other, more recent continuation or fork 
of the project.

Processed: unarchiving 939419, severity of 939419 is serious

[Debian Bug Tracking System]

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

> unarchive 939419
Bug #939419 {Done: Mathieu Parent } [libparse-pidl-perl] 
libparse-pidl-perl: version ordering issue.
Unarchived Bug 939419
> # this still needs to be fixed in stable
> severity 939419 serious
Bug #939419 {Done: Mathieu Parent } [libparse-pidl-perl] 
libparse-pidl-perl: version ordering issue.
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#986524: marked as done (freecontact: FTBFS: devlibs error: There is no package matching [libgfortran-8-dev] and noone provides it, please report bug to d-shlibs maintainer)

[Debian Bug Tracking System]

Your message dated Wed, 07 Apr 2021 15:34:17 +
with message-id 
and subject line Bug#986524: fixed in freecontact 1.0.21-9
has caused the Debian Bug report #986524,
regarding freecontact: FTBFS: devlibs error: There is no package matching 
[libgfortran-8-dev] and noone provides it, please report bug to d-shlibs 
maintainer
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.)


-- 
986524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freecontact
Version: 1.0.21-8
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> d-shlibmove --commit \
> --multiarch \
> --exclude-la \
> --devunversioned \
> --override s/libblas3-dev/libblas-dev/ \
> --v5 \
> --override s/libgfortran[345]-dev/libgfortran-8-dev/ \
> --override s/libquadmath0-dev/libgcc-8-dev/ \
> --override s/liblapack3-dev/liblapack-dev/ \
> --movedev debian/tmp/usr/include/* usr/include \
> debian/tmp/usr/lib/*/*.so
> Library package automatic movement utility
>  --> libblas-dev package exists.
> devlibs error: There is no package matching [libgfortran-8-dev] and noone 
> provides it, please report bug to d-shlibs maintainer
>  --> liblapack-dev package exists.
> make[1]: *** [debian/rules:29: override_dh_install] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/04/06/freecontact_1.0.21-8_testing.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 mine
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: freecontact
Source-Version: 1.0.21-9
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated freecontact 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, 07 Apr 2021 17:06:42 +0200
Source: freecontact
Architecture: source
Version: 1.0.21-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 986524
Changes:
 freecontact (1.0.21-9) unstable; urgency=medium
 .
   * Fix override in d-shlibmove
 Closes: #986524
Checksums-Sha1:
 ee27114ce4760d33c2dad60edbe97f8206955d2a 2434 freecontact_1.0.21-9.dsc
 066ff89bfdcd21e4f32783f7ebfafacadd6678a8 6144 
freecontact_1.0.21-9.debian.tar.xz
 7782232294fa9fdb0e71abdee7ca29a63f98c1ef 8680 
freecontact_1.0.21-9_amd64.buildinfo
Checksums-Sha256:
 3a10aad012ad4c34a1438e7b8399ba7da943f0894dd09bdcbd056a3f38810c0d 2434 
freecontact_1.0.21-9.dsc
 473bf101546055c1da1d3f4e217b26cd595d25070b80edefebd29e1be3e86af2 6144 
freecontact_1.0.21-9.debian.tar.xz
 dbafe0289b617d7f80669f32fb20da63e8b79b67f6f35a9824f49436bc346364 8680 
freecontact_1.0.21-9_amd64.buildinfo
Files:
 c5986623ba35cf2a486acdb608f9ab39 2434 science optional freecontact_1.0.21-9.dsc
 6d3def723abd33c15acdb87dc919b365 6144 science optional 
freecontact_1.0.21-9.debian.tar.xz
 0a07cff7e187c7cee04f1c64e38d2888 8680 science optional 
freecontact_1.0.21-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmBtzZgRHHRpbGxlQGRl

Bug#986574: darktable FTBFS with DEB_BUILD_OPTIONS=parallel=1

[Helmut Grohne]

Source: darktable
Version: 3.4.0-2
Severity: serious
Tags: ftbfs

darktable fails to build from source when adding parallel=1 to
DEB_BUILD_OPTIONS. Note that this is independent of the number of actual
CPU cores. I suppose that there is a missing dependency relation among
CMake targets. Here is the actual failure:

| [ 25%] Building C object bin/CMakeFiles/lib_darktable.dir/control/conf.c.o
| cd /<>/obj-x86_64-linux-gnu/bin && /usr/bin/cc 
-DDT_HAVE_SIGNAL_TRACE -DGDK_DISABLE_DEPRECATED 
-DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_22 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_MIN_REQUIRED 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_40 -DGTK_DISABLE_DEPRECATED 
-DGTK_DISABLE_SINGLE_INCLUDES -DHAVE_BUILTIN_CPU_SUPPORTS -DHAVE_CONFIG_H 
-DHAVE_GAME -DHAVE_GPHOTO2 -DHAVE_GPHOTO_25_OR_NEWER -DHAVE_GRAPHICSMAGICK 
-DHAVE_HTTP_SERVER -DHAVE_KWALLET -DHAVE_LENSFUN -DHAVE_LIBSECRET -DHAVE_MAP 
-DHAVE_OPENCL -DHAVE_OPENEXR -DHAVE_OPENJPEG -DHAVE_OSMGPSMAP_110_OR_NEWER 
-DHAVE_OSMGPSMAP_NEWER_THAN_110 -DHAVE_PRINT -DHAVE_SQLITE_324_OR_NEWER 
-DUSE_COLORDGTK -DUSE_LUA -D_RELEASE -D_XOPEN_SOURCE=700 
-D__GDK_KEYSYMS_COMPAT_H__ -Dlib_darktable_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/bin -I/<>/src 
-I/<>/src/external/LuaAutoC 
-I/<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/darktable/rawspeed/src
 -I/<>/src/external/rawspeed/src/librawspeed 
-I/<>/src/external/whereami/src -isystem 
/<>/src/external -isystem /<>/src/external/OpenCL 
-isystem /<>/src/external/rawspeed/src/external -isystem 
/usr/include/glib-2.0 -isystem /usr/lib/x86_64-linux-gnu/glib-2.0/include 
-isystem /usr/include/gtk-3.0 -isystem /usr/include/at-spi2-atk/2.0 -isystem 
/usr/include/at-spi-2.0 -isystem /usr/include/dbus-1.0 -isystem 
/usr/lib/x86_64-linux-gnu/dbus-1.0/include -isystem /usr/include/gio-unix-2.0 
-isystem /usr/include/cairo -isystem /usr/include/pango-1.0 -isystem 
/usr/include/fribidi -isystem /usr/include/harfbuzz -isystem 
/usr/include/atk-1.0 -isystem /usr/include/pixman-1 -isystem /usr/include/uuid 
-isystem /usr/include/freetype2 -isystem /usr/include/libpng16 -isystem 
/usr/include/gdk-pixbuf-2.0 -isystem /usr/include/libmount -isystem 
/usr/include/blkid -isystem /usr/include/libxml2 -isystem 
/usr/include/libsoup-2.4 -isystem /usr/include/OpenEXR -isystem 
/usr/include/lensfun -isystem /usr/include/librsvg-2.0 -isystem 
/usr/include/json-glib-1.0 -isystem /usr/include/openjpeg-2.4 -isystem 
/usr/include/libsecret-1 -isystem /usr/include/GraphicsMagick -isystem 
/usr/include/lua5.3 -isystem /usr/include/osmgpsmap-1.0 -isystem 
/usr/include/colord-1 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wformat -Wformat-security -Wshadow -Wtype-limits 
-Wvla -Wold-style-declaration -Wno-unknown-pragmas -Wno-error=varargs 
-Wno-format-truncation -Wno-error=address-of-packed-member -std=c99 -fopenmp 
-mtune=generic -msse2 -g -mfpmath=sse -O3 -DNDEBUG -O3 
-fexpensive-optimizations -fPIC -o 
CMakeFiles/lib_darktable.dir/control/conf.c.o -c 
/<>/src/control/conf.c
| /<>/src/control/conf.c:27:10: fatal error: conf_gen.h: No such 
file or directory
|27 | #include "conf_gen.h"
|   |  ^~~~
| compilation terminated.
| make[3]: *** [bin/CMakeFiles/lib_darktable.dir/build.make:1118: 
bin/CMakeFiles/lib_darktable.dir/control/conf.c.o] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:1787: 
bin/CMakeFiles/lib_darktable.dir/all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[1]: *** [Makefile:174: all] Error 2
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
| make: *** [debian/rules:20: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Bug#982692: marked as done (gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2)

[Debian Bug Tracking System]

Your message dated Wed, 07 Apr 2021 15:03:31 +
with message-id 
and subject line Bug#982692: fixed in gemma 0.98.4+dfsg-3
has caused the Debian Bug report #982692,
regarding gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -pedantic -I/usr/include/catch 
> -I/usr/include/eigen -Wdate-time -D_FORTIFY_SOURCE=2 -DOPENBLAS 
> -isystem/usr/local/opt/openblas/include -Og -Wfatal-errors -g -DHAVE_INLINE 
> -pthread -Wall -std=gnu++11   -Icontrib/catch-1.9.7 -Isrc -Og -Wfatal-errors 
> -g -DHAVE_INLINE -pthread -Wall -std=gnu++11   -Icontrib/catch-1.9.7 -Isrc  
> -c -o test/src/unittests-main.o test/src/unittests-main.cpp
> g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -pedantic -I/usr/include/catch 
> -I/usr/include/eigen -Wdate-time -D_FORTIFY_SOURCE=2 -DOPENBLAS 
> -isystem/usr/local/opt/openblas/include -Og -Wfatal-errors -g -DHAVE_INLINE 
> -pthread -Wall -std=gnu++11   -Icontrib/catch-1.9.7 -Isrc -Og -Wfatal-errors 
> -g -DHAVE_INLINE -pthread -Wall -std=gnu++11   -Icontrib/catch-1.9.7 -Isrc  
> -c -o test/src/unittests-math.o test/src/unittests-math.cpp
> g++ -Wdate-time -D_FORTIFY_SOURCE=2 -DOPENBLAS 
> -isystem/usr/local/opt/openblas/include -Og -Wfatal-errors -g -DHAVE_INLINE 
> -pthread -Wall -std=gnu++11   -Icontrib/catch-1.9.7 -Isrc -Og -Wfatal-errors 
> -g -DHAVE_INLINE -pthread -Wall -std=gnu++11   -Icontrib/catch-1.9.7 -Isrc 
> ./test/src/unittests-main.o  ./test/src/unittests-math.o src/bslmm.o 
> src/bslmmdap.o src/debug.o src/fastblas.o src/gemma.o src/gemma_io.o 
> src/gzstream.o src/lapack.o src/ldr.o src/lm.o src/lmm.o src/logistic.o 
> src/mathfunc.o src/mvlmm.o src/param.o src/prdt.o src/varcov.o src/vc.o -lgsl 
> -lz -lopenblas -o ./bin/unittests-gemma
> ./bin/unittests-gemma
> Mismatch coordinates (1,0)0:3!
> 
>  This example computes real matrix C=alpha*A*B+beta*C using 
>  Intel(R) MKL function dgemm, where A, B, and  C are matrices and 
>  alpha and beta are double precision scalars
> 
>  Initializing data for matrix multiplication C=A*B for matrix 
>  A(2000x200) and matrix B(200x1000)
> 
>  Allocating memory for matrices aligned on 64-byte boundary for better 
>  performance 
> 
>  Intializing matrix data 
> 
>  Computing matrix product using Intel(R) MKL dgemm function via CBLAS 
> interface 
> 
> 
>  This example computes real matrix C=alpha*A*B+beta*C using 
>  Intel(R) MKL function dgemm, where A, B, and  C are matrices and 
>  alpha and beta are double precision scalars
> 
>  Initializing data for matrix multiplication C=A*B for matrix 
>  A(2000x200) and matrix B(200x1000)
> 
>  Allocating memory for matrices aligned on 64-byte boundary for better 
>  performance 
> 
>  Intializing matrix data 
> 
>  Computing matrix product using Intel(R) MKL dgemm function via CBLAS 
> interface 
> 
> 
>  Computations completed.
> 
> ===
> All tests passed (23 assertions in 4 test cases)
> 
> rm -vf test/output/*
> cd test && ./dev_test_suite.sh | tee ../dev_test.log
> run system shunit2
> testLinearModel
> GEMMA 0.98.4 (2021-01-29) by Xiang Zhou and team (C) 2012-2021
> GSL_RNG_SEED=100
> GSL random generator type: mt19937; seed = 100 (option -1); first value = 
> 2333906440
> Reading Files ... 
> ## number of total individuals = 1940
> ## number of analyzed individuals = 1410
> ## number of covariates = 1
> ## number of phenotypes = 1
> ## number of total SNPs/var=12226
> ## number of analyzed SNPs =10768
>0%
>    8%
>    16%
>    25%
>    33%
>    41%
>    49%
>  

Processed: forwarded to salsa mr

[Debian Bug Tracking System]

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

> forwarded 985948 
> https://salsa.debian.org/debian/libubootenv/-/merge_requests/3
Bug #985948 [libubootenv-tool] libubootenv-tool: Debug lines from fw_printenv 
break RAUC
Set Bug forwarded-to-address to 
'https://salsa.debian.org/debian/libubootenv/-/merge_requests/3'.
> thanks
Stopping processing here.

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

Bug#985948: libubootenv-tool: Debug lines from fw_printenv break RAUC, mender-client, etc.

[Andreas Henriksson]

Hello again,

On Wed, Apr 07, 2021 at 11:36:30AM +0200, Andreas Henriksson wrote:
[...]
> I've submitted a merge-request that fixes the imminent problems for
> review at:
> https://salsa.debian.org/debian/libubootenv/-/merge_requests/3
[...]

I've studied things a bit more and updated the merge-request with
more of a cleanup approach that simply drops unused settings and
then just adds defining NDEBUG via debhelper variables.
(More detailed info in each commit message.)

Please speak up ASAP if you're interested in reviewing this and
doing a maintainer upload, otherwise I might not wait very long
before I make use the 0-day NMU policy. I'd really like to see
this be fixed in bullseye very soon.
Please also speak up if you don't have time and want me to proceed
with the NMU and dealing with the unblock request so I know!

Regards,
Andreas Henriksson

Bug#986522: golang-github-vdemeester-shakers: FTBFS: unsatisfiable build-dependency: golang-check.v1-dev (>= 0.0+git20150729.11d3bc7-3~) (versioned dep on a virtual pkg?)

[Shengjing Zhu]

On Wed, Apr 7, 2021 at 3:01 PM Lucas Nussbaum  wrote:
>
> Source: golang-github-vdemeester-shakers
> Version: 0.0~git20160210.0.24d7f1d-2.1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210406 ftbfs-bullseye
>

The package is a leaf Go library, with no reverse build-depends. And
the upstream repository is read-only now.
So I would prefer dropping it from bullseye and removing it from unstable later.

-- 
Shengjing Zhu

Bug#986565: unusable with current git

[Damyan Ivanov]

Package: git-flow
Version: 1.12.3-1
Severity: grave
Tags: patch

Today 'flow' is not a supported git command:

 $git flow
 git: 'flow' is not a git command. See 'git --help'.
 
 The most similar commands are
reflog
show

Running it under strace reveals that git looks for commands under 
/usr/libexec/git-core, while git-flow installs things under /usr/lib/git-core

Perhaps this is caused by a change in the search path in git and git-flow needs 
to adapt.

Replacing /usr/lib/git-core with /usr/libexec/git-core in debian/install.mk 
seems to fix the problem.


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

Kernel: Linux 5.10.0-5-amd64
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git-flow depends on:
ii  git [git-core]  1:2.31.0-1
ii  git-core1:2.15.0~rc0-1

git-flow recommends no packages.

git-flow suggests no packages.

-- debconf-show failed

Processed: Re: Bug#986037: kdenlive: crashes on audio setup

[Debian Bug Tracking System]

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

> severity #986037 important
Bug #986037 [kdenlive] kdenlive: crashes on audio setup
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#986037: kdenlive: crashes on audio setup

[Patrick Matthäi]

severity #986037 important
thanks

Hi Norbert and Dan,

Am 28.03.21 um 14:11 schrieb Norbert Preining:

Package: kdenlive
Version: 20.12.3-1
Severity: grave



Since (for myself?) this issue does not affect Debian bullseye 
downgrading the severity, because this release could not migrate then..




Justification: renders package unusable

Hi

I am running kdenlive with the kde frameworks from experimental, but
that shouldn't be a problem I thought.

I see crashes/segfaults on every start of kdenlive. Backtrace is:
(gdb) bt
#0  0x7fff898862a0 in fftw_execute () from 
/usr/lib/x86_64-linux-gnu/libfftw3.so.3
#1  0x7fff894207f5 in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltplus.so
#2  0x76d93b88 in mlt_frame_get_audio () from 
/usr/lib/x86_64-linux-gnu/libmlt.so.6
#3  0x76d722b8 in Mlt::Frame::get_audio(mlt_audio_format&, int&, int&, 
int&) () from /usr/lib/x86_64-linux-gnu/libmlt++.so.3
#4  0x558b8929 in ?? ()
#5  0x558b4aab in ?? ()
#6  0x556e25a5 in ?? ()
#7  0x752d6e72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x752d3b81 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x74382ea7 in start_thread (arg=) at 
pthread_create.c:477
#10 0x74e2cdef in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

and when I enter "c" into gdb to continue another segfault happens:
(gdb) c
Continuing.
[Thread 0x7fff1a3fc700 (LWP 250120) exited]

Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7102d8c0 (LWP 250071)]
0x703ba570 in QXcbConnection::getSelectionOwner(unsigned int) const () 
from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
(gdb) bt
#0  0x703ba570 in QXcbConnection::getSelectionOwner(unsigned int) const 
() from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#1  0x703b4f88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#2  0x7715c998 in QQuickTextInput::q_canPasteChanged() () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x771691e3 in QQuickTextInput::qt_metacall(QMetaObject::Call, int, 
void**) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x745bac76 in QQuickTextField::qt_metacall(QMetaObject::Call, int, 
void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5
#5  0x754eb290 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x75ed0935 in QClipboard::emitChanged(QClipboard::Mode) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#7  0x703b98a4 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) 
() from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x703bacd6 in 
QXcbConnection::processXcbEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#9  0x703dd7d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#10 0x739bde6b in g_main_context_dispatch () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x739be118 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x739be1cf in g_main_context_iteration () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7550c4bf in 
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x754b392b in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x754bbba0 in QCoreApplication::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x556360d4 in ?? ()
#17 0x74d55d0a in __libc_start_main (main=0x55634c20, argc=1, 
argv=0x7fffd8a8, init=, fini=,
 rtld_fini=, stack_end=0x7fffd898) at 
../csu/libc-start.c:308
#18 0x5563d6ba in _start ()
(gdb)

and then a final continue
(gdb) c
Continuing.
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 14 and type 'Read', disabling...
Invalid read from eventfd: Bad file descriptor
Code should not be reached at pulsecore/fdsem.c:157, function flush(). Aborting.
[Thread 0x7fffefee3700 (LWP 250075) exited]
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kdenlive path = /usr/bin pid = 250071
KCrash: Arguments: /usr/bin/kdenlive
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
Cannot find user-level thread for LWP 250102: generic error
(gdb) Cannot find user-level thread for LWP 250098: generic error


Not sure whether this is a pulseaudio, kdenlive, or one of the
frameworks problems, though.



This does not look like kdenlive for me, maybe from mlt, what do you say 
Dan?


Norbert: Can you confirm it works/not with 20.12.2 and with Debian 
bullseye without experimental packages?




Best

Norbert

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

Processed: tagging 982991

[Debian Bug Tracking System]

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

> tags 982991 + bullseye
Bug #982991 [src:matrix-synapse] matrix-synapse: not suitable for inclusion 
into bullseye
Added tag(s) bullseye.
> thanks
Stopping processing here.

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

Bug#986553: Acknowledgement (emacs: make-closure is undefined)

[Philip Kaludercic]

I apologize for the empty form, this was the first time I used
reportbug. I hope it is ok if I answer the question in this message.

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

   * What led up to the situation?

 The latest update of Emacs on debian buster.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 I started Emacs.

   * What was the outcome of this action?

 It raised an error that it couldn't construct a closure.

   * What outcome did you expect instead?

 I expect Emacs to be able to construct a closure, and parse my
 configuration.

"Debian Bug Tracking System"  writes:

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 986553: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986553.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Rob Browning 
>
> If you wish to submit further information on this problem, please
> send it to 986...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.

-- 
Philip K.

Bug#986553: emacs: make-closure is undefined

[Philip K.]

Package: emacs
Version: 1:27.1+1-3.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** 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 testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emacs depends on:
ii  emacs-lucid  1:27.1+1-3.1

emacs recommends no packages.

emacs suggests no packages.

-- no debconf information

Bug#980628: marked as done (libsass-python: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Wed, 07 Apr 2021 10:48:51 +
with message-id 
and subject line Bug#980628: fixed in libsass-python 0.20.1-3
has caused the Debian Bug report #980628,
regarding libsass-python: FTBFS: tests failed
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh debian/rules --with python3 --buildsystem=pybuild
> py3versions: no X-Python3-Version in control file, using supported versions
> pybuild -s custom --test -p "3.9" \
>   --test-args="cd {build_dir}; \
>   sed -i '/^class DistutilsTestCase.*/i @unittest.skip(\"Do not build 
> sass again\")' sasstests.py; \
>   {interpreter} -m unittest sasstests"
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build; 
> sed -i '/^class DistutilsTestCase.*/i @unittest.skip("Do not build sass 
> again")' sasstests.py;  python3.9 -m unittest sasstests
> .ssF..python3.9
>  -m unittest: error: '/dev/null' seems not a file
> ..
> ==
> FAIL: test_build_one (sasstests.ManifestTestCase)
> --
> Traceback (most recent call last):
>   File "/<>/.pybuild/cpython3_3.9/build/sasstests.py", line 780, 
> in test_build_one
> self.assert_source_map_file(
>   File "/<>/.pybuild/cpython3_3.9/build/sasstests.py", line 180, 
> in assert_source_map_file
> self.assert_source_map_equal(expected, tree)
>   File "/<>/.pybuild/cpython3_3.9/build/sasstests.py", line 170, 
> in assert_source_map_equal
> assert expected == actual
> AssertionError
> 
> --
> Ran 96 tests in 0.100s
> 
> FAILED (failures=1, skipped=2)
> E: pybuild pybuild:353: test: plugin custom failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.9/build;sed -i '/^class 
> DistutilsTestCase.*/i @unittest.skip("Do not build sass again")' 
> sasstests.py;  python3.9 -m unittest sasstests
> make[1]: *** [debian/rules:28: override_dh_auto_test] Error 13

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/libsass-python_0.20.1-2_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: libsass-python
Source-Version: 0.20.1-3
Done: Frédéric Bonnard 

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

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

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

Debian distribution maintenance software
pp.
Frédéric Bonnard  (supplier of updated libsass-python 
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, 07 Apr 2021 12:28:16 +0200
Source: libsass-python
Architecture: source
Version: 0.20.1-3
Distribution: unstable
Urgency: medium
Maintainer: Frédéric Bonnard 
Changed-By: Frédéric Bonnard 
Closes: 980628
Changes:
 libsass-python (0.20.1-3) unstable; urgency=medium
 .
   * Use pytest instead of unittest to run tests and disable unported
 tests (Closes: 

Bug#986508: marked as done (binutils-mipsen: FTBFS: /bin/bash: line 1: debugedit: command not found)

[Debian Bug Tracking System]

Your message dated Wed, 07 Apr 2021 10:18:28 +
with message-id 
and subject line Bug#986508: fixed in binutils-mipsen 7+c2
has caused the Debian Bug report #986508,
regarding binutils-mipsen: FTBFS: /bin/bash: line 1: debugedit: command not 
found
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.)


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

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory 
> '/<>/binutils-2.35.2/builddir-mips/libctf'
>  /bin/mkdir -p 
> '/<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu'
>  /bin/bash ./libtool   --mode=install /usr/bin/install -c   libctf-mips.la 
> libctf-nobfd-mips.la 
> '/<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu'
> libtool: install: /usr/bin/install -c .libs/libctf-mips.so.0.0.0 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-mips.so.0.0.0
> libtool: install: (cd 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu
>  && { ln -s -f libctf-mips.so.0.0.0 libctf-mips.so.0 || { rm -f 
> libctf-mips.so.0 && ln -s libctf-mips.so.0.0.0 libctf-mips.so.0; }; })
> libtool: install: (cd 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu
>  && { ln -s -f libctf-mips.so.0.0.0 libctf-mips.so || { rm -f libctf-mips.so 
> && ln -s libctf-mips.so.0.0.0 libctf-mips.so; }; })
> libtool: install: /usr/bin/install -c .libs/libctf-mips.lai 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-mips.la
> libtool: install: /usr/bin/install -c .libs/libctf-nobfd-mips.so.0.0.0 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-nobfd-mips.so.0.0.0
> libtool: install: (cd 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu
>  && { ln -s -f libctf-nobfd-mips.so.0.0.0 libctf-nobfd-mips.so.0 || { rm -f 
> libctf-nobfd-mips.so.0 && ln -s libctf-nobfd-mips.so.0.0.0 
> libctf-nobfd-mips.so.0; }; })
> libtool: install: (cd 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu
>  && { ln -s -f libctf-nobfd-mips.so.0.0.0 libctf-nobfd-mips.so || { rm -f 
> libctf-nobfd-mips.so && ln -s libctf-nobfd-mips.so.0.0.0 
> libctf-nobfd-mips.so; }; })
> libtool: install: /usr/bin/install -c .libs/libctf-nobfd-mips.lai 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-nobfd-mips.la
> libtool: install: /usr/bin/install -c .libs/libctf-mips.a 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-mips.a
> libtool: install: chmod 644 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-mips.a
> libtool: install: x86_64-linux-gnu-ranlib --plugin 
> /usr/lib/gcc/x86_64-linux-gnu/10/liblto_plugin.so --plugin 
> /usr/lib/gcc/x86_64-linux-gnu/10/liblto_plugin.so 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-mips.a
> libtool: install: /usr/bin/install -c .libs/libctf-nobfd-mips.a 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-nobfd-mips.a
> libtool: install: chmod 644 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-nobfd-mips.a
> libtool: install: x86_64-linux-gnu-ranlib --plugin 
> /usr/lib/gcc/x86_64-linux-gnu/10/liblto_plugin.so --plugin 
> /usr/lib/gcc/x86_64-linux-gnu/10/liblto_plugin.so 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-nobfd-mips.a
> libtool: install: warning: remember to run `libtool --finish 
> /usr/lib/mips-linux-gnu'
>  /bin/mkdir -p 
> '/<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/include'
>  /usr/bin/install -c -m 644 ../../libctf/../include/ctf.h 
> ../../libctf/../include/ctf-api.h 
> '/<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/include'
> make[5]: Leaving directory 
> '/<>/binutils-2.35.2/builddir-mips/libctf'
> make[4]: Leaving directory 
> '/<>/binutils-2.35.2/builddir-mips/libctf'
> make[3]: Nothing to be done for 'install-target'.
> make[3]: Leaving directory '/<>/binutils-2.35.2/builddir-mips'
> make[2]: Leaving directory '/<>/binutils-2.35.2/builddir-mips'
> rm -rf \
>   debian/binutils-mips-linux-gnu/usr/share/info \
>   

Processed: Re: Bug#986544: ca-certificates: change versioning scheme

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #986544 [ca-certificates] ca-certificates: change versioning scheme
Added tag(s) moreinfo.
> severity -1 wishlist
Bug #986544 [ca-certificates] ca-certificates: change versioning scheme
Severity set to 'wishlist' from 'serious'

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

Bug#986544: ca-certificates: change versioning scheme

[Julien Cristau]

Control: tag -1 moreinfo
Control: severity -1 wishlist

On Wed, Apr 07, 2021 at 11:40:34AM +0200, Andreas Beckmann wrote:
> Package: ca-certificates
> Version: 20210119
> Severity: serious
> 
> Hi,
> 
> as I had commented on
> https://salsa.debian.org/debian/ca-certificates/-/merge_requests/6
> 
> After seeing the new version scheme for debian-security-support (sid now
> has 1:11+2021.01.23), I was thinking whether something similar would be
> sensible for ca-certificates, too. Am I correct to assume that the sole
> source of certificates included is the "mozilla bundle"?
> 
Currently yes.  Historically it has included other CAs, and that could
conceivably happen again.

> What about changing the versioning scheme to
>   :++ ?
> With =1, =11 for bullseye, =2.46,
> =1, s.t. we would have 1:11+2.46+1 for now. A new mozilla bundle
> packaged could use 1:11+2.47+1 for bullseye and 1:10+2.47+1 for buster
> while excluding some of my patches that are not compatible with
> ca-certificates-java in buster (or would require an update of -java too,
> but that needs to be done very carefully). (ca-certificates-java in
> bullseye needs to depend on ca-certificates (>= 1:11) in that case).
> Such versioning would be more clear than 20200401 for bullseye
> backported with reduced functionality as 20200401~deb10u1 to buster.
> That hypothetical buster version would still satisfy the new versioned
> constraint in ca-certificates-java in spite of not having the expected
> functionality.
> 
That doesn't really make sense to me, I'm afraid.

I'm not familiar with the issue you're trying to fix with this,
though...

Cheers,
Julien

Bug#986544: ca-certificates: change versioning scheme

[Andreas Beckmann]

Package: ca-certificates
Version: 20210119
Severity: serious

Hi,

as I had commented on
https://salsa.debian.org/debian/ca-certificates/-/merge_requests/6

After seeing the new version scheme for debian-security-support (sid now
has 1:11+2021.01.23), I was thinking whether something similar would be
sensible for ca-certificates, too. Am I correct to assume that the sole
source of certificates included is the "mozilla bundle"?

What about changing the versioning scheme to
  :++ ?
With =1, =11 for bullseye, =2.46,
=1, s.t. we would have 1:11+2.46+1 for now. A new mozilla bundle
packaged could use 1:11+2.47+1 for bullseye and 1:10+2.47+1 for buster
while excluding some of my patches that are not compatible with
ca-certificates-java in buster (or would require an update of -java too,
but that needs to be done very carefully). (ca-certificates-java in
bullseye needs to depend on ca-certificates (>= 1:11) in that case).
Such versioning would be more clear than 20200401 for bullseye
backported with reduced functionality as 20200401~deb10u1 to buster.
That hypothetical buster version would still satisfy the new versioned
constraint in ca-certificates-java in spite of not having the expected
functionality.

I'll add a corresponding commit to the above merge request.

Andreas

Bug#982692: gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2

[Pjotr Prins]

These are harmless failures because of FP. So, yes, comment them out.
I need to rewrite the test system, sorry.

On Wed, Apr 07, 2021 at 10:56:54AM +0200, Andreas Tille wrote:
> Hi Lucas,
> 
> On Wed, Apr 07, 2021 at 08:49:27AM +0200, Lucas Nussbaum wrote:
> > I confirm that I can still reproduce this failure in a testing chroot.
> 
> Thank you for your information.  I have tried to create a diff between
> the successful build log of the autobuilders[1] where all architectures
> have passed and your build log snippet.  Theses asserts in your build
> log seem to cause the build failure:
> 
>   ASSERT:expected:<3088458213> but was:<3088444823>
>   ASSERT:expected:<3088496565> but was:<3088483525>
>   ASSERT:expected:<338154001.76> but was:<338144655.90>
>   ASSERT:expected:<15465346.22> but was:<15464740.32>
> 
> This looks pretty much like floating point rounding issues.  The
> interesting question for me is:  If we do not see these assertions in a
> variety of architectures with different floating point implementations
> what might make your test machine so special to fail in contrast to
> the Debian autobuilders.
> 
> If upstream (in CC) has no better idea the only way I personally see is
> to comment out those tests that are featuring the expected numbers
> above.  But it would be better to investigate this issue with your help
> in more detail.  So if your hardware is in some severe way different
> than Debian autobuilders (either in floating point implementation or
> possibly in parallelisation - sometimes we see weird things due to
> massive parallelisation) it would be great if you could share this
> information in this bug report.
> 
> Kind regards
> 
>Andreas.
> 
> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=gemma=amd64=0.98.4%2Bdfsg-2=1616423615=0
>  
> 
> -- 
> http://fam-tille.de

Processed: Re: libubootenv-tool: Debug lines from fw_printenv break RAUC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #985948 [libubootenv-tool] libubootenv-tool: Debug lines from fw_printenv 
break RAUC
Severity set to 'grave' from 'important'

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

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

[Debian Bug Tracking System]

Your message dated Wed, 07 Apr 2021 09:33:28 +
with message-id 
and subject line Bug#986520: fixed in mkvtoolnix 54.0.0-2
has caused the Debian Bug report #986520,
regarding mkvtoolnix: FTBFS: 
src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: 
Segmentation fault
to be marked as done.

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

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


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

Hi,

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

This is caused by #980596, but at this point I don't know if gcc-10 will
be fixed in testing.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rake -j 4
>   SCAN pch candidates (total=507, .c=4, .cpp=418, .moc=85)
>CXX src/common/common_pch.h
> CC lib/librmff/rmff.c
> CC lib/librmff/mb_file_io.c
> AR lib/librmff/librmff.a
> RANLIB lib/librmff/librmff.a
>CXX src/mpegparser/MPEGVideoBuffer.cpp
>CXX src/common/xml/xml.cpp
>CXX lib/avilib-0.6.10/xio.cpp
> CC lib/avilib-0.6.10/avimisc.c
> CC lib/avilib-0.6.10/avilib.c
>CXX src/mpegparser/M2VParser.cpp
> AR lib/avilib-0.6.10/libavi.a
> RANLIB lib/avilib-0.6.10/libavi.a
>CXX src/mpegparser/CircBuffer.cpp
>CXX src/common/xml/ebml_tags_converter.cpp
> AR src/mpegparser/libmpegparser.a
> RANLIB src/mpegparser/libmpegparser.a
>CXX src/common/xml/ebml_segmentinfo_converter.cpp
>CXX src/common/xml/ebml_converter.cpp
>CXX src/common/xml/ebml_chapters_converter.cpp
>CXX src/common/tags/vorbis.cpp
>CXX src/common/tags/tags.cpp
>CXX src/common/strings/utf8.cpp
>CXX src/common/strings/parsing.cpp
>CXX src/common/strings/formatting.cpp
>CXX src/common/strings/editing.cpp
>CXX src/common/mm_file_io/unix.cpp
>CXX src/common/mm_file_io/common.cpp
>CXX src/common/image/png.cpp
>CXX src/common/image/jpeg.cpp
>CXX src/common/fs_sys_helpers/unix.cpp
>CXX src/common/fs_sys_helpers/common.cpp
>CXX src/common/compression/zlib.cpp
>CXX src/common/compression/header_removal.cpp
>CXX src/common/checksums/md5.cpp
>CXX src/common/checksums/crc.cpp
>CXX src/common/checksums/base.cpp
>CXX src/common/checksums/adler32.cpp
>CXX src/common/chapters/writer.cpp
>CXX src/common/chapters/dvd.cpp
>CXX src/common/chapters/cue_parser.cpp
>CXX src/common/chapters/chapters.cpp
>CXX src/common/chapters/bluray.cpp
>CXX src/common/bluray/util.cpp
>CXX src/common/bluray/track_chapter_names.cpp
>CXX src/common/bluray/mpls.cpp
>CXX src/common/bluray/index.cpp
>CXX src/common/bluray/disc_library.cpp
>CXX src/common/bluray/clpi.cpp
>CXX src/common/webvtt.cpp
>CXX src/common/webm.cpp
>CXX src/common/wavpack.cpp
>CXX src/common/w64.cpp
>CXX src/common/vp9.cpp
>CXX src/common/vobsub.cpp
>CXX src/common/vint.cpp
>CXX src/common/version.cpp
>CXX src/common/vc1.cpp
>CXX src/common/utf8_codecvt_facet.cpp
>CXX src/common/unique_numbers.cpp
>CXX src/common/truehd.cpp
>CXX src/common/translation.cpp
>CXX src/common/track_statistics.cpp
>CXX src/common/theora.cpp
>CXX src/common/terminal.cpp
>CXX src/common/stereo_mode.cpp
>CXX src/common/spu.cpp
>CXX src/common/split_point.cpp
>CXX src/common/split_arg_parsing.cpp
>CXX src/common/samples_to_timestamp_converter.cpp
>CXX src/common/random.cpp
>CXX src/common/qt_kax_analyzer.cpp
>CXX src/common/property_element.cpp
>CXX src/common/output.cpp
>CXX src/common/opus.cpp
>CXX src/common/mpeg4_p2.cpp
>CXX src/common/mpeg1_2.cpp
>CXX src/common/mpeg.cpp
>CXX src/common/mp3.cpp
>CXX src/common/mm_write_buffer_io.cpp
> 

Processed: Re: libubootenv-tool: Debug lines from fw_printenv break RAUC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #985948 [libubootenv-tool] libubootenv-tool: Debug lines from fw_printenv 
break RAUC
Severity set to 'important' from 'grave'

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

Bug#985948: libubootenv-tool: Debug lines from fw_printenv break RAUC

[Bastian Germann]

Control: severity -1 important

Am 07.04.21 um 11:10 schrieb Andreas Henriksson:

Could we please just add a patch that either just rips out the NDEBUG
lines (or inverts the login to #ifdef DEBUG ) ?! Such a patch could/should
be forwarded upstream as well A library should not print to stdout
like this!

I am not the maintainer. You can hand in such a patch to speed up that process.
I am reducing the severity as pointed out before.

Bug#982692: gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2

[Lucas Nussbaum]

Hi,

On 07/04/21 at 10:56 +0200, Andreas Tille wrote:
> Hi Lucas,
> 
> On Wed, Apr 07, 2021 at 08:49:27AM +0200, Lucas Nussbaum wrote:
> > I confirm that I can still reproduce this failure in a testing chroot.
> 
> Thank you for your information.  I have tried to create a diff between
> the successful build log of the autobuilders[1] where all architectures
> have passed and your build log snippet.  Theses asserts in your build
> log seem to cause the build failure:
> 
>   ASSERT:expected:<3088458213> but was:<3088444823>
>   ASSERT:expected:<3088496565> but was:<3088483525>
>   ASSERT:expected:<338154001.76> but was:<338144655.90>
>   ASSERT:expected:<15465346.22> but was:<15464740.32>
> 
> This looks pretty much like floating point rounding issues.  The
> interesting question for me is:  If we do not see these assertions in a
> variety of architectures with different floating point implementations
> what might make your test machine so special to fail in contrast to
> the Debian autobuilders.
> 
> If upstream (in CC) has no better idea the only way I personally see is
> to comment out those tests that are featuring the expected numbers
> above.  But it would be better to investigate this issue with your help
> in more detail.  So if your hardware is in some severe way different
> than Debian autobuilders (either in floating point implementation or
> possibly in parallelisation - sometimes we see weird things due to
> massive parallelisation) it would be great if you could share this
> information in this bug report.

I don't think there's anything very specific about the hardware I'm
using (Amazon EC2 VMs). I can provide access to those VMs if that's
useful (but I need to start them specifically for this test).

I've just done a full rebuild of bullseye and looked at all remaining
failures, and this is the only issue of that kind.

Lucas

Bug#985948: libubootenv-tool: Debug lines from fw_printenv break RAUC

[Andreas Henriksson]

Control: affects -1 mender-client

Hi,

On Sat, Apr 03, 2021 at 02:52:34PM +0200, Bastian Germann wrote:
> Control: tags -1 patch
> 
> A patch is enclosed.
[...]
>  CMAKE_FLAGS = \
>   -DCMAKE_VERBOSE_MAKEFILE=ON \
> - -DCMAKE_C_FLAGS_RELEASE="$(CFLAGS)" \
> + -DCMAKE_C_FLAGS_RELEASE="$(CFLAGS) NDEBUG=" \
>   -DCMAKE_EXE_LINKER_FLAGS_RELEASE="$(LDFLAGS)" \
>   -DBUILD_DOCS=ON \
>   -DCMAKE_INSTALL_INCLUDEDIR="include/$(DEB_HOST_MULTIARCH)"

Your patch seems to have been applied in the last upload and this
bug report was closed.

I've reopened the bug report, as the bug seems to still exist:

$ dpkg -l libubootenv0.1 | grep ^ii
libubootenv0.1:armhf 0.3-2armhfLibrary to access U-Boot 
environment - runtime

$ strings /usr/lib/arm-linux-gnueabihf/libubootenv.so.0.3 |
grep Environment
Environment %s, copy %d
Environment FLAGS %s

$ sudo fw_printenv | head -n1i
Environment OK, copy 1

FYI This extra debug output also breaks mender-client.

Could we please just add a patch that either just rips out the NDEBUG
lines (or inverts the login to #ifdef DEBUG ) ?! Such a patch could/should
be forwarded upstream as well A library should not print to stdout
like this!

Regards,
Andreas Henriksson

Processed: Re: libubootenv-tool: Debug lines from fw_printenv break RAUC

[Debian Bug Tracking System]

Processing control commands:

> affects -1 mender-client
Bug #985948 [libubootenv-tool] libubootenv-tool: Debug lines from fw_printenv 
break RAUC
Added indication that 985948 affects mender-client

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

Processed: Re: mkvtoolnix: FTBFS: src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 10.2.1-24
Bug #986520 [src:mkvtoolnix] mkvtoolnix: FTBFS: 
src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: 
Segmentation fault
The source 'mkvtoolnix' and version '10.2.1-24' do not appear to match any 
binary packages
Marked as fixed in versions mkvtoolnix/10.2.1-24.

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

Bug#986520: mkvtoolnix: FTBFS: src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: Segmentation fault

[Matthias Klose]

Control: fixed -1 10.2.1-24

Please work around it by using gcc-9 for bullseye.  I'm not going to cherry-pick
single patches from the branch.

As said in https://lists.debian.org/debian-release/2021/03/msg00027.html
I'll provide GCC 10.3 for backports.

Bug#986519: nheko: FTBFS: internal compiler error

[Matthias Klose]

Please work around it by using gcc-9 for bullseye.  I'm not going to cherry-pick
single patches from the branch.

As said in https://lists.debian.org/debian-release/2021/03/msg00027.html
I'll provide GCC 10.3 for backports.

Bug#982692: gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2

[Andreas Tille]

Hi Lucas,

On Wed, Apr 07, 2021 at 08:49:27AM +0200, Lucas Nussbaum wrote:
> I confirm that I can still reproduce this failure in a testing chroot.

Thank you for your information.  I have tried to create a diff between
the successful build log of the autobuilders[1] where all architectures
have passed and your build log snippet.  Theses asserts in your build
log seem to cause the build failure:

  ASSERT:expected:<3088458213> but was:<3088444823>
  ASSERT:expected:<3088496565> but was:<3088483525>
  ASSERT:expected:<338154001.76> but was:<338144655.90>
  ASSERT:expected:<15465346.22> but was:<15464740.32>

This looks pretty much like floating point rounding issues.  The
interesting question for me is:  If we do not see these assertions in a
variety of architectures with different floating point implementations
what might make your test machine so special to fail in contrast to
the Debian autobuilders.

If upstream (in CC) has no better idea the only way I personally see is
to comment out those tests that are featuring the expected numbers
above.  But it would be better to investigate this issue with your help
in more detail.  So if your hardware is in some severe way different
than Debian autobuilders (either in floating point implementation or
possibly in parallelisation - sometimes we see weird things due to
massive parallelisation) it would be great if you could share this
information in this bug report.

Kind regards

   Andreas.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=gemma=amd64=0.98.4%2Bdfsg-2=1616423615=0
 

-- 
http://fam-tille.de

Processed: reopen 985948 - still prints debug output

[Debian Bug Tracking System]

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

> reopen 985948
Bug #985948 {Done: Nobuhiro Iwamatsu } [libubootenv-tool] 
libubootenv-tool: Debug lines from fw_printenv break RAUC
'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 libubootenv/0.3-2.
> notfixed 985948 0.3-2
Bug #985948 [libubootenv-tool] libubootenv-tool: Debug lines from fw_printenv 
break RAUC
Ignoring request to alter fixed versions of bug #985948 to the same values 
previously set
> found 985948 0.3-2
Bug #985948 [libubootenv-tool] libubootenv-tool: Debug lines from fw_printenv 
break RAUC
Marked as found in versions libubootenv/0.3-2.
> thanks
Stopping processing here.

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

Processed: Correcting affects and merging

[Debian Bug Tracking System]

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

> forcemerge 986518 986521
Bug #986518 [ant] starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid 
flag: -Xdoclint:none
Bug #986521 [ant] starjava-ttools: FTBFS: [javadoc] javadoc: error - invalid 
flag: -Xdoclint:none
Removed indication that 986521 affects starjava-ttools and starjava-topcat
Added indication that 986521 affects starjava-topcat,starjava-ttools
Merged 986518 986521
> affects 986518 src:starjava-topcat
Bug #986518 [ant] starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid 
flag: -Xdoclint:none
Bug #986521 [ant] starjava-ttools: FTBFS: [javadoc] javadoc: error - invalid 
flag: -Xdoclint:none
Added indication that 986518 affects src:starjava-topcat
Added indication that 986521 affects src:starjava-topcat
> affects 986518 src:starjava-ttools
Bug #986518 [ant] starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid 
flag: -Xdoclint:none
Bug #986521 [ant] starjava-ttools: FTBFS: [javadoc] javadoc: error - invalid 
flag: -Xdoclint:none
Added indication that 986518 affects src:starjava-ttools
Added indication that 986521 affects src:starjava-ttools
> thanks
Stopping processing here.

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

Processed (with 3 errors): Correcting affects and merging

[Debian Bug Tracking System]

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

> merge 986518 986521
Bug #986518 [ant] starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid 
flag: -Xdoclint:none
Unable to merge bugs because:
affects of #986521 is 'starjava-ttools,starjava-topcat' not 
'starjava-topcat,starjava-ttools'
Failed to merge 986518: Did not alter merged bugs.

> affects 986518 src:starjava-topcat
Failed to mark 986518 as affecting package(s): failed to get lock on 
/srv/bugs.debian.org/spool/lock/986518 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/986518 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

> affects 986518 src:starjava-ttools
Failed to mark 986518 as affecting package(s): failed to get lock on 
/srv/bugs.debian.org/spool/lock/986518 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/986518 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/986518 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

> thanks
Stopping processing here.

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

Processed: Re: Bug#986518: starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid flag: -Xdoclint:none

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ant 1.10.9-3
Bug #986521 [src:starjava-ttools] starjava-ttools: FTBFS: [javadoc] javadoc: 
error - invalid flag: -Xdoclint:none
Bug reassigned from package 'src:starjava-ttools' to 'ant'.
No longer marked as found in versions starjava-ttools/3.4-2.
Ignoring request to alter fixed versions of bug #986521 to the same values 
previously set
Bug #986521 [ant] starjava-ttools: FTBFS: [javadoc] javadoc: error - invalid 
flag: -Xdoclint:none
Marked as found in versions ant/1.10.9-3.
> affects -1 starjava-topcat starjava-ttools
Bug #986521 [ant] starjava-ttools: FTBFS: [javadoc] javadoc: error - invalid 
flag: -Xdoclint:none
Added indication that 986521 affects starjava-topcat and starjava-ttools

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

Bug#986518: starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid flag: -Xdoclint:none

[Ole Streicher]

Control: reassign -1 ant 1.10.9-3
Control: affects -1 starjava-topcat starjava-ttools

Dear maintainer,

The latest ant package adds a flag -Xdoclint:none to the Javadoc 
execution, which is however not recognized by javadoc. The JDK used in 
the package was  openjdk 11.0.11+4-1.


Best regards

Ole

Processed: Re: Bug#986518: starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid flag: -Xdoclint:none

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ant 1.10.9-3
Bug #986518 [src:starjava-topcat] starjava-topcat: FTBFS: [javadoc] javadoc: 
error - invalid flag: -Xdoclint:none
Bug reassigned from package 'src:starjava-topcat' to 'ant'.
No longer marked as found in versions starjava-topcat/4.8-2.
Ignoring request to alter fixed versions of bug #986518 to the same values 
previously set
Bug #986518 [ant] starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid 
flag: -Xdoclint:none
Marked as found in versions ant/1.10.9-3.
> affects -1 starjava-topcat starjava-ttools
Bug #986518 [ant] starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid 
flag: -Xdoclint:none
Added indication that 986518 affects starjava-topcat and starjava-ttools

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

Bug#986519: nheko: FTBFS: internal compiler error

[Gianfranco Costamagna]

control: reassign -1 gcc-10
control: found -1 10.2.1-6
control: affects -1 src:nheko
control: fixed -1 10.2.1-24

This is fixed in experimental since long time, not sure which release between 
-16 and -24 fixed it.

G.

Processed: Re: nheko: FTBFS: internal compiler error

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 gcc-10
Bug #986519 [src:nheko] nheko: FTBFS: internal compiler error
Bug reassigned from package 'src:nheko' to 'gcc-10'.
No longer marked as found in versions nheko/0.7.2-3.
Ignoring request to alter fixed versions of bug #986519 to the same values 
previously set
> found -1 10.2.1-6
Bug #986519 [gcc-10] nheko: FTBFS: internal compiler error
Marked as found in versions gcc-10/10.2.1-6.
> affects -1 src:nheko
Bug #986519 [gcc-10] nheko: FTBFS: internal compiler error
Added indication that 986519 affects src:nheko
> fixed -1 10.2.1-24
Bug #986519 [gcc-10] nheko: FTBFS: internal compiler error
Marked as fixed in versions gcc-10/10.2.1-24.

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

Bug#986520: mkvtoolnix: FTBFS: src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: Segmentation fault

[Christian Marillat]

On 07 avril 2021 08:31, Lucas Nussbaum  wrote:

> Source: mkvtoolnix
> Version: 52.0.0-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210406 ftbfs-bullseye
>
> Hi,

Hi,

> During a rebuild of all packages in bullseye, your package failed to build
> on amd64.
>
> This is caused by #980596, but at this point I don't know if gcc-10 will
> be fixed in testing.

Would be nice to know why gcc-10 is still broken in testing/unstable

A package isn't supposed to not break other packages ?

Christian

Processed: Re: Bug#982692: gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #982692 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check 
returned exit code 2
Severity set to 'serious' from 'important'
> tags -1 -  moreinfo
Bug #982692 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check 
returned exit code 2
Removed tag(s) moreinfo.
> tags -1 - unreproducible
Bug #982692 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check 
returned exit code 2
Removed tag(s) unreproducible.

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

Bug#986528: httpcomponents-client: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.m

[Lucas Nussbaum]

Source: httpcomponents-client
Version: 4.5.13-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with javahelper
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibhttpclient-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>jh_linkjars
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Apache HttpComponents Client   
> [pom]
> [INFO] Apache HttpClient  
> [jar]
> [INFO] Apache HttpClient Mime 
> [jar]
> [INFO] Apache HttpClient Fluent API   
> [jar]
> [INFO] Apache HttpClient Cache
> [jar]
> [INFO] Apache HttpClient OSGi bundle   
> [bundle]
> [INFO] 
> [INFO] --< org.apache.httpcomponents:httpcomponents-client 
> >---
> [INFO] Building Apache HttpComponents Client 4.5.13   
> [1/6]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] --- maven-javadoc-plugin:3.0.1:jar (attach-javadocs) @ 
> httpcomponents-client ---
> [INFO] Not executing Javadoc as the project is not a Java classpath-capable 
> package
> [INFO] 
> [INFO] < org.apache.httpcomponents:httpclient 
> >
> [INFO] Building Apache HttpClient 4.5.13  
> [2/6]
> [INFO] [ jar 
> ]-
> [INFO] 
> [INFO] --- build-helper-maven-plugin:3.0.0:add-source (add-source) @ 
> httpclient ---
> [INFO] Source directory: /<>/httpclient/src/main/java-deprecated 
> added.
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> httpclient ---
> [INFO] Using 'ISO-8859-1' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ httpclient 
> ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 426 source files to 
> /<>/httpclient/target/classes
> [INFO] 
> /<>/httpclient/src/main/java-deprecated/org/apache/http/impl/client/DecompressingHttpClient.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /<>/httpclient/src/main/java-deprecated/org/apache/http/impl/client/DecompressingHttpClient.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] 
> [INFO] --- maven-bundle-plugin:3.5.1:manifest (bundle-manifest) @ httpclient 
> ---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ httpclient ---
> [INFO] Using 'ISO-8859-1' encoding to copy filtered resources.
> [INFO] Copying 6 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ 
> httpclient ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 119 source files to 
> /<>/httpclient/target/test-classes
> [INFO] 
> /<>/httpclient/src/test/java/org/apache/http/impl/client/TestIdleConnectionEvictor.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /<>/httpclient/src/test/java/org/apache/http/impl/client/TestIdleConnectionEvictor.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.22.3:test (default-test) @ httpclient ---
> [INFO] Tests are skipped.
> [INFO] 
> [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ httpclient ---
> [INFO] Building jar: /<>/httpclient/target/httpclient-4.5.13.jar
> [INFO] 
> [INFO] --- maven-jar-plugin:3.1.2:test-jar (default-jar) @ httpclient ---
> [INFO] Building jar: 
> /<>/httpclient/target/httpclient-4.5.13-tests.jar
> [INFO] 
> [INFO] --- maven-javadoc-plugin:3.0.1:jar (attach-javadocs) @ httpclient ---
> [INFO] Adding the --ignore-source-errors option
> [INFO] 
> 6 warnings
> [WARNING] Javadoc Warnings
> [WARNING] 
> /<>/httpclient/src/main/java/org/apache/http/auth/params/package-info.java:30:
>  warning - Tag @deprecated cannot be used in package 

Processed: Re: Bug#980628: libsass-python FTBFS: possible issue in libsass_3.6.4+20201122-1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #980628 [src:libsass-python] libsass-python: FTBFS: tests failed
Severity set to 'serious' from 'important'

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

Bug#986529: gvm-libs: gvm packages not suitable for stable Debian release

[Sophie Brun]

Source: gvm-libs
Severity: serious
X-Debbugs-Cc: sop...@offensive-security.com

The gvm tools suite should not be in Debian Stable.
Upstream regularly releases new versions and the old versions become
obsolete and sometimes unusable.

My goal is to get rid of all the source packages of GVM tools: gvm-libs, gvmd,
openvas-scanner, ospd-openvas, greenbone-security-assistant, ospd-openvas,
ospd, gvm-tools, python-gvm, gvm.

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

Kernel: Linux 5.10.0-5-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

Bug#986525: yarl: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

[Lucas Nussbaum]

Source: yarl
Version: 1.6.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd docs && \
> PYTHONPATH=/<> http_proxy='http://127.0.0.1:9/' 
> https_proxy='https://127.0.0.1:9/' \
> python3 -m sphinx -N -E -T -b html . /<>/.pybuild/docs/html/
> Running Sphinx v3.4.3
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 2 source files that are out of date
> updating environment: [new config] 2 added, 0 changed, 0 removed
> reading sources... [ 50%] api
> reading sources... [100%] index
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 50%] api
> writing output... [100%] index
> 
> generating indices... genindex py-modindex done
> highlighting module code... [ 50%] yarl
> highlighting module code... [100%] yarl._url
> 
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded.
> 
> The HTML pages are in ../.pybuild/docs/html.
> rm -rf /<>/.pybuild/docs/html/.doctrees
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=pybuild -Npython-yarl-doc
> I: pybuild pybuild:284: cython3 yarl/_quoting_c.pyx
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> **
> * Accellerated build *
> **
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_yarl/build/yarl
> copying yarl/_url.py -> /<>/.pybuild/cpython3_3.9_yarl/build/yarl
> copying yarl/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_yarl/build/yarl
> copying yarl/_quoting_py.py -> 
> /<>/.pybuild/cpython3_3.9_yarl/build/yarl
> copying yarl/_quoting.py -> 
> /<>/.pybuild/cpython3_3.9_yarl/build/yarl
> running egg_info
> writing yarl.egg-info/PKG-INFO
> writing dependency_links to yarl.egg-info/dependency_links.txt
> writing requirements to yarl.egg-info/requires.txt
> writing top-level names to yarl.egg-info/top_level.txt
> reading manifest file 'yarl.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.cache' found anywhere in 
> distribution
> warning: no previously-included files found matching 'yarl/*.html'
> warning: no previously-included files found matching 'yarl/*.so'
> warning: no previously-included files found matching 'yarl/*.pyd'
> no previously-included directories found matching 'docs/_build'
> writing manifest file 'yarl.egg-info/SOURCES.txt'
> copying yarl/__init__.pyi -> 
> /<>/.pybuild/cpython3_3.9_yarl/build/yarl
> copying yarl/_quoting_c.c -> 
> /<>/.pybuild/cpython3_3.9_yarl/build/yarl
> copying yarl/_quoting_c.pyi -> 
> /<>/.pybuild/cpython3_3.9_yarl/build/yarl
> copying yarl/_quoting_c.pyx -> 
> /<>/.pybuild/cpython3_3.9_yarl/build/yarl
> copying yarl/py.typed -> 
> /<>/.pybuild/cpython3_3.9_yarl/build/yarl
> running build_ext
> building 'yarl._quoting_c' extension
> creating build
> creating build/temp.linux-x86_64-3.9
> creating build/temp.linux-x86_64-3.9/yarl
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g 
> -ffile-prefix-map=/build/python3.9-RNBry6/python3.9-3.9.2=. 
> -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python3.9 -c yarl/_quoting_c.c -o 
> build/temp.linux-x86_64-3.9/yarl/_quoting_c.o
> yarl/_quoting_c.c: In function 
> ‘__pyx_f_4yarl_10_quoting_c_9_Unquoter__do_unquote’:
> yarl/_quoting_c.c:5297:9: warning: ‘_PyUnicode_get_wstr_length’ is deprecated 
> [-Wdeprecated-declarations]
>  5297 | __pyx_t_2 = (__pyx_v_unquoted != 
> Py_None)&&(__Pyx_PyUnicode_IS_TRUE(__pyx_v_unquoted) != 0);
>   | ^
> In file included from /usr/include/python3.9/unicodeobject.h:1026,
>  from /usr/include/python3.9/Python.h:97,
>  from yarl/_quoting_c.c:4:
> /usr/include/python3.9/cpython/unicodeobject.h:446:26: note: declared here
>   446 | static inline Py_ssize_t _PyUnicode_get_wstr_length(PyObject *op) {
>   |  ^~
> yarl/_quoting_c.c:5297:9: warning: ‘PyUnicode_AsUnicode’ is deprecated 
> [-Wdeprecated-declarations]
>  5297 | __pyx_t_2 = (__pyx_v_unquoted != 
> Py_None)&&(__Pyx_PyUnicode_IS_TRUE(__pyx_v_unquoted) != 0);
>   | ^
> In file included from /usr/include/python3.9/unicodeobject.h:1026,
>  from /usr/include/python3.9/Python.h:97,
>  from 

Bug#986526: openjdk-17: FTBFS: build-dependency not installable: openjdk-16-jdk-headless

[Lucas Nussbaum]

Source: openjdk-17
Version: 17~11-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11), m4, lsb-release, zip, unzip, 
> sharutils, gawk, cpio, pkg-config, procps, wdiff, fastjar (>= 
> 2:0.96-0ubuntu2), time, strip-nondeterminism, debugedit (>= 4.16), jtreg (>= 
> 5.1-b1-0~), testng, xvfb, xauth, xfonts-base, libgl1-mesa-dri, xfwm4, 
> x11-xkb-utils, dbus-x11, autoconf, automake, autotools-dev, ant, 
> ant-optional, g++-10, openjdk-16-jdk-headless | openjdk-17-jdk-headless, 
> libxtst-dev, libxi-dev, libxt-dev, libxaw7-dev, libxrender-dev, libcups2-dev, 
> libasound2-dev, liblcms2-dev, libfreetype6-dev (>= 2.2.1), libxinerama-dev, 
> libkrb5-dev, xsltproc, libpcsclite-dev, libxrandr-dev, libelf-dev, 
> libfontconfig1-dev, libgtk2.0-0 | libgtk-3-0, libharfbuzz-dev, libffi-dev, 
> zlib1g-dev, zlib1g-dev, libattr1-dev, libpng-dev, libjpeg-dev, libgif-dev, 
> libnss3-dev (>= 2:3.17.1), build-essential, fakeroot, graphviz, pandoc
> Filtered Build-Depends: debhelper (>= 11), m4, lsb-release, zip, unzip, 
> sharutils, gawk, cpio, pkg-config, procps, wdiff, fastjar (>= 
> 2:0.96-0ubuntu2), time, strip-nondeterminism, debugedit (>= 4.16), jtreg (>= 
> 5.1-b1-0~), testng, xvfb, xauth, xfonts-base, libgl1-mesa-dri, xfwm4, 
> x11-xkb-utils, dbus-x11, autoconf, automake, autotools-dev, ant, 
> ant-optional, g++-10, openjdk-16-jdk-headless, libxtst-dev, libxi-dev, 
> libxt-dev, libxaw7-dev, libxrender-dev, libcups2-dev, libasound2-dev, 
> liblcms2-dev, libfreetype6-dev (>= 2.2.1), libxinerama-dev, libkrb5-dev, 
> xsltproc, libpcsclite-dev, libxrandr-dev, libelf-dev, libfontconfig1-dev, 
> libgtk2.0-0, libharfbuzz-dev, libffi-dev, zlib1g-dev, zlib1g-dev, 
> libattr1-dev, libpng-dev, libjpeg-dev, libgif-dev, libnss3-dev (>= 2:3.17.1), 
> build-essential, fakeroot, graphviz, pandoc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [803 B]
> Get:5 copy:/<>/apt_archive ./ Packages [821 B]
> Fetched 2587 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: openjdk-16-jdk-headless but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2021/04/06/openjdk-17_17~11-1_testing.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 mine
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.

Bug#986524: freecontact: FTBFS: devlibs error: There is no package matching [libgfortran-8-dev] and noone provides it, please report bug to d-shlibs maintainer

[Lucas Nussbaum]

Source: freecontact
Version: 1.0.21-8
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> d-shlibmove --commit \
> --multiarch \
> --exclude-la \
> --devunversioned \
> --override s/libblas3-dev/libblas-dev/ \
> --v5 \
> --override s/libgfortran[345]-dev/libgfortran-8-dev/ \
> --override s/libquadmath0-dev/libgcc-8-dev/ \
> --override s/liblapack3-dev/liblapack-dev/ \
> --movedev debian/tmp/usr/include/* usr/include \
> debian/tmp/usr/lib/*/*.so
> Library package automatic movement utility
>  --> libblas-dev package exists.
> devlibs error: There is no package matching [libgfortran-8-dev] and noone 
> provides it, please report bug to d-shlibs maintainer
>  --> liblapack-dev package exists.
> make[1]: *** [debian/rules:29: override_dh_install] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/04/06/freecontact_1.0.21-8_testing.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 mine
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.

Bug#986523: odb: FTBFS: i386.h:2500:10: fatal error: common/config/i386/i386-cpuinfo.h: No such file or directory

[Lucas Nussbaum]

Source: odb
Version: 2.4.0-13
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

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

The full build log is available from:
   http://qa-logs.debian.net/2021/04/06/odb_2.4.0-13_testing.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 mine
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.

Bug#986522: golang-github-vdemeester-shakers: FTBFS: unsatisfiable build-dependency: golang-check.v1-dev (>= 0.0+git20150729.11d3bc7-3~) (versioned dep on a virtual pkg?)

[Lucas Nussbaum]

Source: golang-github-vdemeester-shakers
Version: 0.0~git20160210.0.24d7f1d-2.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-golang, golang-any, 
> golang-check.v1-dev (>= 0.0+git20150729.11d3bc7-3~) | 
> golang-github-go-check-check-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 9), dh-golang, golang-any, 
> golang-check.v1-dev (>= 0.0+git20150729.11d3bc7-3~), build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [425 B]
> Get:5 copy:/<>/apt_archive ./ Packages [495 B]
> Fetched 1877 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: golang-check.v1-dev (>= 
> 0.0+git20150729.11d3bc7-3~)
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://qa-logs.debian.net/2021/04/06/golang-github-vdemeester-shakers_0.0~git20160210.0.24d7f1d-2.1_testing.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 mine
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.

Bug#986519: nheko: FTBFS: internal compiler error

[Lucas Nussbaum]

Source: nheko
Version: 0.7.2-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

This is caused by #980629 which is fixed in experimental, but not in
unstable/testing. At this point of the release cycle, maybe a separate
fix in nheko should be investigated, if gcc-10 is not going to be fixed
in testing.

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

Bug#986520: mkvtoolnix: FTBFS: src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: Segmentation fault

[Lucas Nussbaum]

Source: mkvtoolnix
Version: 52.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

This is caused by #980596, but at this point I don't know if gcc-10 will
be fixed in testing.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rake -j 4
>   SCAN pch candidates (total=507, .c=4, .cpp=418, .moc=85)
>CXX src/common/common_pch.h
> CC lib/librmff/rmff.c
> CC lib/librmff/mb_file_io.c
> AR lib/librmff/librmff.a
> RANLIB lib/librmff/librmff.a
>CXX src/mpegparser/MPEGVideoBuffer.cpp
>CXX src/common/xml/xml.cpp
>CXX lib/avilib-0.6.10/xio.cpp
> CC lib/avilib-0.6.10/avimisc.c
> CC lib/avilib-0.6.10/avilib.c
>CXX src/mpegparser/M2VParser.cpp
> AR lib/avilib-0.6.10/libavi.a
> RANLIB lib/avilib-0.6.10/libavi.a
>CXX src/mpegparser/CircBuffer.cpp
>CXX src/common/xml/ebml_tags_converter.cpp
> AR src/mpegparser/libmpegparser.a
> RANLIB src/mpegparser/libmpegparser.a
>CXX src/common/xml/ebml_segmentinfo_converter.cpp
>CXX src/common/xml/ebml_converter.cpp
>CXX src/common/xml/ebml_chapters_converter.cpp
>CXX src/common/tags/vorbis.cpp
>CXX src/common/tags/tags.cpp
>CXX src/common/strings/utf8.cpp
>CXX src/common/strings/parsing.cpp
>CXX src/common/strings/formatting.cpp
>CXX src/common/strings/editing.cpp
>CXX src/common/mm_file_io/unix.cpp
>CXX src/common/mm_file_io/common.cpp
>CXX src/common/image/png.cpp
>CXX src/common/image/jpeg.cpp
>CXX src/common/fs_sys_helpers/unix.cpp
>CXX src/common/fs_sys_helpers/common.cpp
>CXX src/common/compression/zlib.cpp
>CXX src/common/compression/header_removal.cpp
>CXX src/common/checksums/md5.cpp
>CXX src/common/checksums/crc.cpp
>CXX src/common/checksums/base.cpp
>CXX src/common/checksums/adler32.cpp
>CXX src/common/chapters/writer.cpp
>CXX src/common/chapters/dvd.cpp
>CXX src/common/chapters/cue_parser.cpp
>CXX src/common/chapters/chapters.cpp
>CXX src/common/chapters/bluray.cpp
>CXX src/common/bluray/util.cpp
>CXX src/common/bluray/track_chapter_names.cpp
>CXX src/common/bluray/mpls.cpp
>CXX src/common/bluray/index.cpp
>CXX src/common/bluray/disc_library.cpp
>CXX src/common/bluray/clpi.cpp
>CXX src/common/webvtt.cpp
>CXX src/common/webm.cpp
>CXX src/common/wavpack.cpp
>CXX src/common/w64.cpp
>CXX src/common/vp9.cpp
>CXX src/common/vobsub.cpp
>CXX src/common/vint.cpp
>CXX src/common/version.cpp
>CXX src/common/vc1.cpp
>CXX src/common/utf8_codecvt_facet.cpp
>CXX src/common/unique_numbers.cpp
>CXX src/common/truehd.cpp
>CXX src/common/translation.cpp
>CXX src/common/track_statistics.cpp
>CXX src/common/theora.cpp
>CXX src/common/terminal.cpp
>CXX src/common/stereo_mode.cpp
>CXX src/common/spu.cpp
>CXX src/common/split_point.cpp
>CXX src/common/split_arg_parsing.cpp
>CXX src/common/samples_to_timestamp_converter.cpp
>CXX src/common/random.cpp
>CXX src/common/qt_kax_analyzer.cpp
>CXX src/common/property_element.cpp
>CXX src/common/output.cpp
>CXX src/common/opus.cpp
>CXX src/common/mpeg4_p2.cpp
>CXX src/common/mpeg1_2.cpp
>CXX src/common/mpeg.cpp
>CXX src/common/mp3.cpp
>CXX src/common/mm_write_buffer_io.cpp
>CXX src/common/mm_text_io.cpp
>CXX src/common/mm_stdio.cpp
>CXX src/common/mm_read_buffer_io.cpp
>CXX src/common/mm_proxy_io.cpp
>CXX src/common/mm_null_io.cpp
>CXX src/common/mm_multi_file_io.cpp
>CXX src/common/mm_mpls_multi_file_io.cpp
>CXX src/common/mm_mem_io.cpp
>CXX src/common/mm_io_x.cpp
>CXX src/common/mm_io.cpp
>CXX src/common/mime_types.cpp
>CXX src/common/mime.cpp
>CXX src/common/memory.cpp
>CXX src/common/math.cpp
>CXX src/common/markdown.cpp
>CXX src/common/logger.cpp
>CXX src/common/locale_string.cpp
>CXX src/common/locale.cpp
>CXX src/common/kax_info.cpp
>CXX src/common/kax_file.cpp
>CXX 

Bug#986521: starjava-ttools: FTBFS: [javadoc] javadoc: error - invalid flag: -Xdoclint:none

[Lucas Nussbaum]

Source: starjava-ttools
Version: 3.4-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ant jars
> Buildfile: /<>/build.xml
> 
> prepare:
>[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been 
> set to 1612473971
> 
> check_packages:
> 
> build:
> [mkdir] Created dir: /<>/build/classes
> [javac] Compiling 916 source files to /<>/build/classes
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/plot2/paper/PaperTypeSelector.java:132:
>  warning: [deprecation] Integer(int) in Integer has been deprecated
> [javac] rgbSet.add( new Integer( color.getRGB() & 0x00ff 
> ) );
> [javac] ^
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/plot2/layer/ShapeMode.java:317:
>  warning: [deprecation] Double(double) in Double has been deprecated
> [javac] report.put( key, new Double( pixSize ) );
> [javac]  ^
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/plot2/geom/CubeSurface.java:499:
>  warning: [deprecation] Double(double) in Double has been deprecated
> [javac] config.put( CubeSurfaceFactory.ZOOM_KEY, new Double( 
> zoom_ ) );
> [javac]  ^
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/plot2/geom/CubeSurface.java:500:
>  warning: [deprecation] Double(double) in Double has been deprecated
> [javac] config.put( CubeSurfaceFactory.XOFF_KEY, new Double( 
> xoff_ ) );
> [javac]  ^
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/plot2/geom/CubeSurface.java:501:
>  warning: [deprecation] Double(double) in Double has been deprecated
> [javac] config.put( CubeSurfaceFactory.YOFF_KEY, new Double( 
> yoff_ ) );
> [javac]  ^
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:31: 
> warning: [rawtypes] found raw type: Parameter
> [javac]   Parameter[] params = task.getParameters();
> [javac]   ^
> [javac]   missing type arguments for generic class Parameter
> [javac]   where T is a type-variable:
> [javac] T extends Object declared in class Parameter
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:33: 
> warning: [rawtypes] found raw type: List
> [javac]   List outputFormats = env.getTableOutput().getKnownFormats();
> [javac]   ^
> [javac]   missing type arguments for generic class List
> [javac]   where E is a type-variable:
> [javac] E extends Object declared in interface List
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:34: 
> warning: [rawtypes] found raw type: List
> [javac]   List inputFormats = env.getTableFactory().getKnownFormats();
> [javac]   ^
> [javac]   missing type arguments for generic class List
> [javac]   where E is a type-variable:
> [javac] E extends Object declared in interface List
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:35: 
> warning: [rawtypes] found raw type: Collection
> [javac]   Collection charsets = Charset.availableCharsets().keySet();
> [javac]   ^
> [javac]   missing type arguments for generic class Collection
> [javac]   where E is a type-variable:
> [javac] E extends Object declared in interface Collection
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:105: 
> warning: [rawtypes] found raw type: Collection
> [javac] public static String completionCase(String name, Collection 
> pattern) {
> [javac]  ^
> [javac]   missing type arguments for generic class Collection
> [javac]   where E is a type-variable:
> [javac] E extends Object declared in interface Collection
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:108: 
> warning: [unchecked] unchecked method invocation: method join in class String 
> is applied to given types
> [javac]   "$(compgen -W \"" + String.join(" ", pattern) + "\" -- 
> ${cur}) " +
> [javac]  ^
> [javac]   required: CharSequence,Iterable
> [javac]   found: String,Collection
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/build/BashComplete.java:108: 
> warning: [unchecked] unchecked conversion
> [javac]   "$(compgen -W \"" + String.join(" ", pattern) + "\" -- 
> ${cur}) " +
> [javac]^
> [javac]   required: Iterable
> [javac]   found:Collection
> [javac] 
> /<>/src/main/uk/ac/starlink/ttools/build/MemberDoclet.java:39: 
> warning: [removal] RootDoc in 

Bug#986517: piglit: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

[Lucas Nussbaum]

Source: piglit
Version: 0~git20200212-f4710c51b-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/cmTC_066a0.dir/src.c.o: in function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11:
>  undefined reference to `pthread_create'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12:
>  undefined reference to `pthread_detach'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13:
>  undefined reference to `pthread_cancel'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:14:
>  undefined reference to `pthread_join'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://qa-logs.debian.net/2021/04/06/piglit_0~git20200212-f4710c51b-1_testing.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 mine
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.

Bug#986518: starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid flag: -Xdoclint:none

[Lucas Nussbaum]

Source: starjava-topcat
Version: 4.8-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ant jars
> Buildfile: /<>/build.xml
> 
> prepare:
>[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been 
> set to 1612474211
> 
> check_packages:
> 
> build:
> [mkdir] Created dir: /<>/build/classes
> [javac] Compiling 419 source files to /<>/build/classes
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/TopcatModel.java:193: 
> warning: [deprecation] Long(long) in Long has been deprecated
> [javac] subsetCounts_.put( RowSubset.NONE, new Long( 0 ) );
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/TopcatModel.java:194: 
> warning: [deprecation] Long(long) in Long has been deprecated
> [javac] subsetCounts_.put( RowSubset.ALL, new Long( 
> startab.getRowCount() ) );
> [javac]   ^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/TopcatModel.java:516: 
> warning: [deprecation] Long(long) in Long has been deprecated
> [javac] fireModelChanged( TopcatEvent.ROW, new Long( lrow ) );
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/TopcatModel.java:1266: 
> warning: [deprecation] Long(long) in Long has been deprecated
> [javac] subsetCounts_.put( rset, new Long( 
> viewModel_.getRowCount() ) );
> [javac]  ^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/ViewerTableModel.java:129: 
> warning: [deprecation] Long(long) in Long has been deprecated
> [javac] return new Long( ++lx_ );
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/ViewerTableModel.java:144: 
> warning: [deprecation] Long(long) in Long has been deprecated
> [javac] return new Long( rowMap[ ++kx_ ] );
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/activate/ActivationWindow.java:661:
>  warning: [deprecation] Long(long) in Long has been deprecated
> [javac] tcModel_.fireModelChanged( TopcatEvent.ROW, new Long( 
> lrow ) );
> [javac] ^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/activate/ActivationWindow.java:1406:
>  warning: [deprecation] newInstance() in Class has been deprecated
> [javac] (ActivationType) Class.forName( clazzName 
> ).newInstance();
> [javac]^
> [javac]   where T is a type-variable:
> [javac] T extends Object declared in class Class
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/ControlWindow.java:534: 
> warning: [deprecation] ALT_MASK in InputEvent has been deprecated
> [javac] 
> InputEvent.ALT_MASK ),
> [javac]   ^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/ControlWindow.java:539: 
> warning: [deprecation] ALT_MASK in InputEvent has been deprecated
> [javac] 
> InputEvent.ALT_MASK ),
> [javac]   ^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/ControlWindow.java:2001: 
> warning: [deprecation] newInstance() in Class has been deprecated
> [javac] tld0 = tldClazz.newInstance();
> [javac]^
> [javac]   where T is a type-variable:
> [javac] T extends Object declared in class Class
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/TopcatJELRowReader.java:153: 
> warning: [deprecation] Short(short) in Short has been deprecated
> [javac] return new Short( isub );
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/TopcatJELRowReader.java:241: 
> warning: [deprecation] Integer(int) in Integer has been deprecated
> [javac] translatedSubsetIds_.add( new Integer( 
> subsetId ) );
> [javac]   ^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/TopcatJELRowReader.java:255: 
> warning: [deprecation] Integer(int) in Integer has been deprecated
> [javac] translatedSubsetIds_.add( new Integer( subsets
> [javac]   ^
> [javac] 
> /<>/src/main/uk/ac/starlink/topcat/TopcatJELRowReader.java:323: 
> warning: [deprecation] Integer(int) in Integer has been deprecated
> [javac] return jrow >= 0 ? new Integer( 1 

Bug#986516: python-escript: FTBFS: RuntimeError: Unknown key (DFLAGS) in dpkg-buildflags:

[Lucas Nussbaum]

Source: python-escript
Version: 5.6-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Build steps for py3
> mkdir -p /<>/debian/stage3
> scons  -j4   cc_optim=' -O3  '  build_dir=/<>/debian/tmp3 
> verbose=on prefix=/<>/debian/stage3 
> options_file=debian/sid_options.py docs
> scons: Reading SConscript files ...
> 3.9.2 (default, Feb 28 2021, 17:03:44) 
> [GCC 10.2.1 20210110]
> RuntimeError: Unknown key (DFLAGS) in dpkg-buildflags:
>   File "/<>/SConstruct", line 172:
> env = Environment(tools = ['default'], options = vars,
>   File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 982:
> variables.Update(self)
>   File "/usr/lib/python3/dist-packages/SCons/Variables/__init__.py", line 187:
> exec(contents, {}, values)
>   File "", line 84:
> 
>   File "/<>/site_scons/extractdebbuild.py", line 52:
> raise RuntimeError("Unknown key ("+key+") in dpkg-buildflags")
> make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2021/04/06/python-escript_5.6-2_testing.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 mine
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.

Bug#986515: siconos: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test "ARGS=-E 'COLLECTION|collection|python_test_lcp|dr_iso1|ContactTest'" ARGS\+=-j1 returned exit code 2

[Lucas Nussbaum]

Source: siconos
Version: 4.3.1+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process -E 
> 'COLLECTION|collection|python_test_lcp|dr_iso1|ContactTest' -j1
> Test project /<>/obj-x86_64-linux-gnu
>   Start  1: DLSODES-test
>  1/95 Test  #1: DLSODES-test    Passed
> 0.01 sec
>   Start  2: DLSODAR-test
>  2/95 Test  #2: DLSODAR-test    Passed
> 0.01 sec
>   Start  3: DLSODI-test
>  3/95 Test  #3: DLSODI-test .   Passed
> 0.02 sec
>   Start  4: DLSODPK-test
>  4/95 Test  #4: DLSODPK-test    Passed
> 0.12 sec
>   Start  5: DLSODA-test
>  5/95 Test  #5: DLSODA-test .   Passed
> 0.01 sec
>   Start  6: DLSODE-test
>  6/95 Test  #6: DLSODE-test .   Passed
> 0.01 sec
>   Start  7: DLSODIS-test
>  7/95 Test  #7: DLSODIS-test    Passed
> 0.01 sec
>   Start  8: DLSODKR-test
>  8/95 Test  #8: DLSODKR-test    Passed
> 0.03 sec
>   Start  9: DLSOIBT-test
>  9/95 Test  #9: DLSOIBT-test    Passed
> 0.04 sec
>   Start 10: odepacktest10
> 10/95 Test #10: odepacktest10 ...   Passed
> 0.00 sec
>   Start 11: dr1_radau5
> 11/95 Test #11: dr1_radau5 ..   Passed
> 0.01 sec
>   Start 12: dr2_radau5
> 12/95 Test #12: dr2_radau5 ..   Passed
> 0.01 sec
>   Start 13: dr_radau
> 13/95 Test #13: dr_radau    Passed
> 0.00 sec
>   Start 14: dr_radaup
> 14/95 Test #14: dr_radaup ...   Passed
> 0.01 sec
>   Start 15: dr_rodas
> 15/95 Test #15: dr_rodas    Passed
> 0.00 sec
>   Start 16: dr_seulex
> 16/95 Test #16: dr_seulex ...   Passed
> 0.00 sec
>   Start 17: test_op3x3
> 17/95 Test #17: test_op3x3 ..   Passed
> 0.26 sec
>   Start 18: test_timers_interf
> 18/95 Test #18: test_timers_interf ..   Passed
> 0.01 sec
>   Start 19: test_blas_lapack
> 19/95 Test #19: test_blas_lapack    Passed
> 0.01 sec
>   Start 20: test_pinv
> 20/95 Test #20: test_pinv ...   Passed
> 0.02 sec
>   Start 21: tools_projection
> 21/95 Test #21: tools_projection    Passed
> 0.01 sec
>   Start 22: NumericsArrays
> 22/95 Test #22: NumericsArrays ..   Passed
> 0.01 sec
>   Start 23: NM_test
> 23/95 Test #23: NM_test .   Passed
> 0.17 sec
>   Start 24: tools_test_JordanAlgebra
> 24/95 Test #24: tools_test_JordanAlgebra    Passed
> 0.01 sec
>   Start 25: NM_MUMPS_test
> 25/95 Test #25: NM_MUMPS_test ...   Passed
> 0.01 sec
>   Start 26: SBM_test
> 26/95 Test #26: SBM_test    Passed
> 0.02 sec
>   Start 27: SBCM_to_SBM
> 27/95 Test #27: SBCM_to_SBM .   Passed
> 0.01 sec
>   Start 28: SparseMatrix_test
> 28/95 Test #28: SparseMatrix_test ...   Passed
> 0.02 sec
>   Start 29: lcp_test_DefaultSolverOptions
> 29/95 Test #29: lcp_test_DefaultSolverOptions ...   Passed
> 0.01 sec
>   Start 30: MixedLinearComplementarity_ReadWrite_test
> 30/95 Test #30: MixedLinearComplementarity_ReadWrite_test ...   Passed
> 0.01 sec
>   Start 31: MCP_test
> 31/95 Test #31: MCP_test    Passed
> 0.01 sec
>   Start 32: MCP_test1
> 32/95 Test #32: MCP_test1 ...   Passed
> 0.01 sec
>   Start 33: MCP_test2
> 33/95 Test #33: MCP_test2 ...   Passed
> 0.01 sec
>   Start 34: MCP_2_test1
> 34/95 Test #34: MCP_2_test1 .   Passed
> 0.01 sec
>   Start 35: fc3d_newFromFortranData
> 35/95 Test #35: fc3d_newFromFortranData .   Passed
> 0.01 sec
>   Start 36: fc3d_LmgcDriver_test1
> 36/95 Test #36: fc3d_LmgcDriver_test1 ...   Passed
> 0.01 sec
>   Start 37: fc3d_LmgcDriver_test2
> 37/95 Test #37: fc3d_LmgcDriver_test2 ...   Passed
> 0.01 sec
>   Start 38: 

Bug#986512: libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: libunity
Version: 7.1.4+19.04.20190319-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/<>/test/python'
> make[5]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
> rule.
> make[5]: Leaving directory '/<>/test/python'
> PASS: bug-1062331.py
> PASS: extras.py
> PASS: container-ownership.py
> FAIL: scope-result.py
> 
>libunity 7.1.4: test/python/test-suite.log
> 
> 
> # TOTAL: 4
> # PASS:  3
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: scope-result
> ==
> 
> /<>/test/python/./scope-result.py:2: PyGIWarning: Unity was 
> imported without specifying a version first. Use gi.require_version('Unity', 
> '7.0') before import to ensure that the right version gets loaded.
>   from gi.repository import Unity, GLib
> TypeError: do_add_result() missing 1 required positional argument: 'result'
> Traceback (most recent call last):
>   File "/<>/test/python/./scope-result.py", line 24, in 
> saved_result = rs.results[0]
> IndexError: list index out of range
> FAIL scope-result.py (exit status: 1)
> 
> 
> Testsuite summary for libunity 7.1.4
> 
> # TOTAL: 4
> # PASS:  3
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See test/python/test-suite.log
> 
> make[5]: *** [Makefile:625: test-suite.log] Error 1
> make[5]: Leaving directory '/<>/test/python'
> make[4]: *** [Makefile:733: check-TESTS] Error 2
> make[4]: *** Waiting for unfinished jobs
> make[4]: Leaving directory '/<>/test/python'
> make[3]: *** [Makefile:799: check-am] Error 2
> make[3]: Leaving directory '/<>/test/python'
> make[2]: *** [Makefile:456: check-recursive] Error 1
> make[2]: Leaving directory '/<>/test'
> make[1]: *** [Makefile:576: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

The full build log is available from:
   
http://qa-logs.debian.net/2021/04/06/libunity_7.1.4+19.04.20190319-5_testing.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 mine
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.

Bug#986511: python-jenkinsapi: FTBFS: Unable to create file /sbuild-nonexistent/.pylint.d/jenkinsapi.views1.stats: [Errno 2] No such file or directory: '/sbuild-nonexistent/.pylint.d/jenkinsapi.views1

[Lucas Nussbaum]

Source: python-jenkinsapi
Version: 0.3.11-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> pylint jenkinsapi/*.py
> Unable to create directory /sbuild-nonexistent/.pylint.d
> Unable to create file /sbuild-nonexistent/.pylint.d/jenkinsapi.views1.stats: 
> [Errno 2] No such file or directory: 
> '/sbuild-nonexistent/.pylint.d/jenkinsapi.views1.stats'
> * Module jenkinsapi.plugins
> jenkinsapi/plugins.py:141: [R1729(use-a-generator), Plugins.restart_required] 
> Use a generator instead 'any(job for job in jobs if job['requiresRestart'] == 
> 'true')'
> jenkinsapi/plugins.py:211: [R1729(use-a-generator), 
> Plugins.plugin_version_is_being_installed] Use a generator instead 'any(job 
> for job in jobs if job['name'] == plugin.shortName and job['version'] == 
> plugin.version)'
> 
> ---
> Your code has been rated at 9.99/10
> 
> make[1]: *** [Makefile:4: lint] Error 8

The full build log is available from:
   http://qa-logs.debian.net/2021/04/06/python-jenkinsapi_0.3.11-4_testing.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 mine
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.

Bug#986509: bind-dyndb-ldap: FTBFS: gcc: error: unrecognized command-line option '-V'

[Lucas Nussbaum]

Source: bind-dyndb-ldap
Version: 11.6-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> gcc version 10.2.1 20210110 (Debian 10.2.1-6) 
> ... rest of stderr output deleted ...
> configure:3318: $? = 0
> configure:3307: gcc -V >&5
> gcc: error: unrecognized command-line option '-V'
> gcc: fatal error: no input files
> compilation terminated.
> configure:3318: $? = 1
> configure:3307: gcc -qversion >&5
> gcc: error: unrecognized command-line option '-qversion'; did you mean 
> '--version'?
> gcc: fatal error: no input files
> compilation terminated.
> configure:3318: $? = 1
> configure:3338: checking whether the C compiler works
> configure:3360: gcc -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  >&5
> configure:3364: $? = 0
> configure:3412: result: yes
> configure:3415: checking for C compiler default output file name
> configure:3417: result: a.out
> configure:3423: checking for suffix of executables
> configure:3430: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  >&5
> configure:3434: $? = 0
> configure:3456: result: 
> configure:3478: checking whether we are cross compiling
> configure:3486: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  >&5
> configure:3490: $? = 0
> configure:3497: ./conftest
> configure:3501: $? = 0
> configure:3516: result: no
> configure:3521: checking for suffix of object files
> configure:3543: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3547: $? = 0
> configure:3568: result: o
> configure:3572: checking whether we are using the GNU C compiler
> configure:3591: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3591: $? = 0
> configure:3600: result: yes
> configure:3609: checking whether gcc accepts -g
> configure:3629: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3629: $? = 0
> configure:3670: result: yes
> configure:3687: checking for gcc option to accept ISO C89
> configure:3750: gcc  -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3750: $? = 0
> configure:3763: result: none needed
> configure:3788: checking whether gcc understands -c and -o together
> configure:3810: gcc -c conftest.c -o conftest2.o
> configure:3813: $? = 0
> configure:3810: gcc -c conftest.c -o conftest2.o
> configure:3813: $? = 0
> configure:3825: result: yes
> configure:3844: checking dependency style of gcc
> configure:3955: result: none
> configure:4020: checking for ar
> configure:4036: found /usr/bin/ar
> configure:4047: result: ar
> configure:4073: checking the archiver (ar) interface
> configure:4089: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4089: $? = 0
> configure:4091: ar cru libconftest.a conftest.o >&5
> ar: `u' modifier ignored since `D' is the default (see `U')
> configure:4094: $? = 0
> configure:4122: result: ar
> configure:4190: checking for gcc
> configure:4217: result: gcc
> configure:4446: checking for C compiler version
> configure:4455: gcc --version >&5
> gcc (Debian 10.2.1-6) 10.2.1 20210110
> Copyright (C) 2020 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> configure:4466: $? = 0
> configure:4455: gcc -v >&5
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper
> OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa
> OFFLOAD_TARGET_DEFAULT=1
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Debian 10.2.1-6' 
> --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs 
> --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr 
> --with-gcc-major-version-only --program-suffix=-10 
> --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
> --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
> --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
> --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
> --with-default-libstdcxx-abi=new --enable-gnu-unique-object 
> --disable-vtable-verify 

Bug#986513: puppetlabs-http-client-clojure: FTBFS: ERROR in (sync-client-test-ssl-protocols) (HttpAsyncRequestExecutor.java:356) should not connect to a server when protocols don't overlap clojure syn

[Lucas Nussbaum]

Source: puppetlabs-http-client-clojure
Version: 1.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein test
> 
> lein test com.puppetlabs.http.client.impl.java-client-test
> 
> lein test com.puppetlabs.http.client.impl.metrics-unit-test
> 
> lein test puppetlabs.http.client.async-plaintext-test
> 
> lein test puppetlabs.http.client.async-unbuffered-test
> 
> lein test puppetlabs.http.client.gzip-request-test
> 
> lein test puppetlabs.http.client.metrics-test
> 
> lein test puppetlabs.http.client.sync-plaintext-test
> 
> lein test puppetlabs.http.client.sync-ssl-test
> 
> lein test :only 
> puppetlabs.http.client.sync-ssl-test/sync-client-test-ssl-protocols
> 
> ERROR in (sync-client-test-ssl-protocols) (HttpAsyncRequestExecutor.java:356)
> should not connect to a server when protocols don't overlap clojure sync 
> client
> expected: (thrown? SSLException (clj-https-get-with-protocols ["TLSv1.2"] 
> nil))
>   actual: org.apache.http.ConnectionClosedException: Connection is closed
>  at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.endOfInput 
> (HttpAsyncRequestExecutor.java:356)
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput 
> (DefaultNHttpClientConnection.java:261)
> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady 
> (InternalIODispatch.java:81)
> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady 
> (InternalIODispatch.java:39)
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady 
> (AbstractIODispatch.java:121)
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable 
> (BaseIOReactor.java:162)
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent 
> (AbstractIOReactor.java:337)
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents 
> (AbstractIOReactor.java:315)
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute 
> (AbstractIOReactor.java:276)
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute 
> (BaseIOReactor.java:104)
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run 
> (AbstractMultiworkerIOReactor.java:591)
> java.lang.Thread.run (Thread.java:829)
> 
> lein test puppetlabs.http.client.test-common
> 
> Ran 84 tests containing 733 assertions.
> 0 failures, 1 errors.
> Tests failed.
> make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2021/04/06/puppetlabs-http-client-clojure_1.2.0-1_testing.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 mine
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.

Bug#986510: lintian-brush: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13

[Lucas Nussbaum]

Source: lintian-brush
Version: 0.99
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package lintian-brush
> dpkg-buildpackage: info: source version 0.99
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Jelmer Vernooij 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3,bash_completion --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under 
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (native)'
> dpkg-source: info: building lintian-brush in lintian-brush_0.99.tar.xz
> dpkg-source: info: building lintian-brush in lintian-brush_0.99.dsc
>  debian/rules binary
> dh binary --with python3,bash_completion --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/debbugs.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/standards_version.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/line_editor.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/multiarch_hints.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/patches.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/lintian_overrides.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/gpg.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/debhelper.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/__main__.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/changelog.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/licenses.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/scrub_obsolete.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/xdg.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/section.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/upstream_metadata.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/vcswatch.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/vcs.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/dirty_tracker.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/config.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/yaml.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/debianize.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/watch.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/salsa.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/release_info.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/lintian.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/fixer.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/systemd.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/detect_gbp_dch.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
> copying lintian_brush/udd.py -> 
> /<>/.pybuild/cpython3_3.9/build/lintian_brush
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py test 
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> creating lintian_brush.egg-info
> writing lintian_brush.egg-info/PKG-INFO
> writing dependency_links to lintian_brush.egg-info/dependency_links.txt
> writing entry 

Bug#986508: binutils-mipsen: FTBFS: /bin/bash: line 1: debugedit: command not found

[Lucas Nussbaum]

Source: binutils-mipsen
Version: 7+c1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory 
> '/<>/binutils-2.35.2/builddir-mips/libctf'
>  /bin/mkdir -p 
> '/<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu'
>  /bin/bash ./libtool   --mode=install /usr/bin/install -c   libctf-mips.la 
> libctf-nobfd-mips.la 
> '/<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu'
> libtool: install: /usr/bin/install -c .libs/libctf-mips.so.0.0.0 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-mips.so.0.0.0
> libtool: install: (cd 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu
>  && { ln -s -f libctf-mips.so.0.0.0 libctf-mips.so.0 || { rm -f 
> libctf-mips.so.0 && ln -s libctf-mips.so.0.0.0 libctf-mips.so.0; }; })
> libtool: install: (cd 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu
>  && { ln -s -f libctf-mips.so.0.0.0 libctf-mips.so || { rm -f libctf-mips.so 
> && ln -s libctf-mips.so.0.0.0 libctf-mips.so; }; })
> libtool: install: /usr/bin/install -c .libs/libctf-mips.lai 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-mips.la
> libtool: install: /usr/bin/install -c .libs/libctf-nobfd-mips.so.0.0.0 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-nobfd-mips.so.0.0.0
> libtool: install: (cd 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu
>  && { ln -s -f libctf-nobfd-mips.so.0.0.0 libctf-nobfd-mips.so.0 || { rm -f 
> libctf-nobfd-mips.so.0 && ln -s libctf-nobfd-mips.so.0.0.0 
> libctf-nobfd-mips.so.0; }; })
> libtool: install: (cd 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu
>  && { ln -s -f libctf-nobfd-mips.so.0.0.0 libctf-nobfd-mips.so || { rm -f 
> libctf-nobfd-mips.so && ln -s libctf-nobfd-mips.so.0.0.0 
> libctf-nobfd-mips.so; }; })
> libtool: install: /usr/bin/install -c .libs/libctf-nobfd-mips.lai 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-nobfd-mips.la
> libtool: install: /usr/bin/install -c .libs/libctf-mips.a 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-mips.a
> libtool: install: chmod 644 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-mips.a
> libtool: install: x86_64-linux-gnu-ranlib --plugin 
> /usr/lib/gcc/x86_64-linux-gnu/10/liblto_plugin.so --plugin 
> /usr/lib/gcc/x86_64-linux-gnu/10/liblto_plugin.so 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-mips.a
> libtool: install: /usr/bin/install -c .libs/libctf-nobfd-mips.a 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-nobfd-mips.a
> libtool: install: chmod 644 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-nobfd-mips.a
> libtool: install: x86_64-linux-gnu-ranlib --plugin 
> /usr/lib/gcc/x86_64-linux-gnu/10/liblto_plugin.so --plugin 
> /usr/lib/gcc/x86_64-linux-gnu/10/liblto_plugin.so 
> /<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf-nobfd-mips.a
> libtool: install: warning: remember to run `libtool --finish 
> /usr/lib/mips-linux-gnu'
>  /bin/mkdir -p 
> '/<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/include'
>  /usr/bin/install -c -m 644 ../../libctf/../include/ctf.h 
> ../../libctf/../include/ctf-api.h 
> '/<>/binutils-2.35.2/debian/binutils-mips-linux-gnu/usr/include'
> make[5]: Leaving directory 
> '/<>/binutils-2.35.2/builddir-mips/libctf'
> make[4]: Leaving directory 
> '/<>/binutils-2.35.2/builddir-mips/libctf'
> make[3]: Nothing to be done for 'install-target'.
> make[3]: Leaving directory '/<>/binutils-2.35.2/builddir-mips'
> make[2]: Leaving directory '/<>/binutils-2.35.2/builddir-mips'
> rm -rf \
>   debian/binutils-mips-linux-gnu/usr/share/info \
>   debian/binutils-mips-linux-gnu/usr/share/locale
> mkdir -p debian/binutils-mips-linux-gnu/usr/lib/x86_64-linux-gnu
> set -e; \
> d_src=debian/binutils-mips-linux-gnu/usr/x86_64-linux-gnu/mips-linux-gnu/lib; 
> \
> d_dst=debian/binutils-mips-linux-gnu/usr/lib/x86_64-linux-gnu; \
> for lib in libbfd libopcodes; do \
>   so=$(basename $(echo $d_src/$lib*mips*.so)); \
>   mv $d_src/$so $d_dst/.; \
>   ln -sf ../../../lib/x86_64-linux-gnu/$so $d_src/$lib.so; \
>   mv $d_src/$lib.a $d_dst/${lib}-2.35.2-mips.a; \
>   ln -sf ../../../lib/x86_64-linux-gnu/$lib-2.35.2-mips.a $d_src/$lib.a; \
> done
> mv debian/binutils-mips-linux-gnu/usr/lib/mips-linux-gnu/libctf*.so.* \
>   debian/binutils-mips-linux-gnu/usr/lib/x86_64-linux-gnu/.
> : # replace hard links with soft links
> for i in debian/binutils-mips-linux-gnu/usr/mips-linux-gnu/bin/*; do \
>   ln -sf