Bug#962847: exim4: takes forever to send a mail after sleeping

[Michal Politowski]

Package: exim4
Version: 4.94-4
Followup-For: Bug #962847

gdb shows the wait happening in milliwait, called from exim_wait_tick:

0xf7faf169 in __kernel_vsyscall ()
#0  0xf7faf169 in __kernel_vsyscall ()
#1  0xf742fc44 in __GI___sigsuspend (set=0xffdc53ac) at 
../sysdeps/unix/sysv/linux/sigsuspend.c:26
#2  0x565fc792 in milliwait (itval=0xffdc54fc) at exim.c:325
#3  0x565fdb93 in exim_wait_tick (tgt_tv=0x56743788 , 
resolution=500) at exim.c:485
#4  0x56637272 in receive_msg (extract_recip=) at receive.c:4323
#5  0x565e4e76 in handle_smtp_call (accepted=, 
accept_socket=, listen_socket_count=, 
listen_sockets=) at daemon.c:530
#6  daemon_go () at daemon.c:2414
#7  0x565d5de0 in main (argc=, cargv=) at 
exim.c:4805

I am pretty sure that the problem is caused by the commit 
6906c131d1d07d07831f8fbabae6290a3cba6ca3
(Use a monotonic clock, if available, for ID generation).
The change contains measuring of the difference between CLOCK_MONOTONIC and 
realtime once
at startup (exim_clock_init), but as far as I understand CLOCK_MONOTONIC
on Linux does not increase during suspend/hibernate (possibly wrognly [1]),
so the difference grows then, unaccounted for.

[1]: https://stackoverflow.com/a/3527632/1236045

-- 
Michał Politowski
Talking has been known to lead to communication if practiced carelessly.

Bug#963239: linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5)

[eric gdr]

Since some days, I noticed that "resync" of md device triggers at boot time.
Sometimes, it triggers at every boot.
It slows down the computer and the disks access for 90minutes.
I didn't notice this kind of behavior at the beginning.

Lately I didn't change anything except changing a component (PCI sound
card) and keeping the OS up to date by installing the last updates.

So I checked the health of the disks (with smartctl) and manually triggered
a check of the array (with /usr/share/mdadm/checkarray).
But everything looks good.

In the log (first post) there are messages about the bitmap of the array
and that is not clean forcing a reconstruction of the array.
I don't think it's normal.


Le dim. 21 juin 2020 à 22:53, Ben Hutchings  a écrit :

> Control: tag -1 moreinfo
>
> You need to explain what the bug is.  The subject says that a RAID
> array was resynced at boot, but that's supposed to happen in some
> circumstances.
>
> * Why did you not expect it?
> * Did you notice anything happen before, or did you make any change,
>   that might have triggered this behaviour?
> * Does this happen repeatedly?
>   * If so, haved you tried anything to work around this, and did it
> work?
>
> Ben.
>
> --
> Ben Hutchings
> It is impossible to make anything foolproof
> because fools are so ingenious.
>
>
>

Bug#961919: RFS: shairplay/1.0-1 [ITP] -- AirPort Express server emulator.

[Vasyl Gello]

Hi Mattia!

Fixed version and copyright issues (removed ~exp thingy) and re-targeted to 
unstable.

Lintian on my side does not list any errors, however mentors one reports the 
bug closed does not belong to the package.
Of course I can file another bug but maybe there is more elegant solution?
-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com

Skype: vasek.gello
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Bug#963472: qemu-system-data: Embeds user and host in slof.bin

[Vagrant Cascadian]

Package: qemu-system-data
Version: 1:5.0-5
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: username hostname
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

A version string containing the username and hostname is embedded in
slof.bin.

The attached patch removes this, which should improve the
reproducibility of the build.

Thanks for maintaining qemu!


live well,
  vagrant

From: Vagrant Cascadian 
Date: Mon, 22 Jun 2020 03:48:55 +
X-Dgit-Generated: 1:5.0-6~0~20200622~4 7ad3e07212ae4baf17ca3734670f0774d06403a7
Subject: roms/SLOF/Makefile.gen: Remove user and host from release version.

This version string ends up in the slof.bin, leading to
reproducibility issues.

---

--- qemu-5.0.orig/roms/SLOF/Makefile.gen
+++ qemu-5.0/roms/SLOF/Makefile.gen
@@ -26,7 +26,7 @@ RELEASE=git-$(shell git rev-parse --shor
 export DRIVER_NAME=git-$(shell git rev-parse --short=12 HEAD)
 else
 ifneq (,$(shell cat ../VERSION))
-RELEASE="$(USER)@$(HOSTNAME) release $(shell cat ../VERSION)"
+RELEASE="release $(shell cat ../VERSION)"
 export DRIVER_NAME=HEAD
 else
 RELEASE="$(USER)@$(HOSTNAME)(private build)"


signature.asc
Description: PGP signature

Bug#881687: dpkg-cross: diff for NMU version 2.6.15-3.1

[Helmut Grohne]

Control: tags 881687 + pending
Control: tags 931077 + patch
Control: tags 931077 + pending
Control: tags 955631 + pending
Control: tags 959524 + pending


Hi Wookey,

I've prepared an NMU for dpkg-cross (versioned as 2.6.15-3.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer. Please find the diff attached.

Helmut
diff --minimal -Nru dpkg-cross-2.6.15/config/cross-config.alpha dpkg-cross-2.6.15/config/cross-config.alpha
--- dpkg-cross-2.6.15/config/cross-config.alpha	2019-04-06 07:21:56.0 +0200
+++ dpkg-cross-2.6.15/config/cross-config.alpha	2020-06-21 21:29:37.0 +0200
@@ -7,19 +7,3 @@
 #
 ac_cv_c_bigendian=no
 ac_cv_c_char_unsigned=no
-ac_cv_sizeof_long_long=8
-ac_cv_sizeof_unsigned_long_long=8
-ac_cv_sizeof_long=8
-ac_cv_sizeof_unsigned_long=8
-ac_cv_sizeof_int=4
-ac_cv_sizeof_unsigned_int=4
-ac_cv_sizeof_short=2
-ac_cv_sizeof_unsigned_short=2
-ac_cv_sizeof_char=1
-ac_cv_sizeof_unsigned_char=1
-ac_cv_sizeof_signed_char=1
-ac_cv_sizeof_float=4
-ac_cv_sizeof_double=8
-ac_cv_sizeof_long_double=8
-ac_cv_sizeof_void_p=8
-ac_cv_sizeof_char_p=8
diff --minimal -Nru dpkg-cross-2.6.15/config/cross-config.amd64 dpkg-cross-2.6.15/config/cross-config.amd64
--- dpkg-cross-2.6.15/config/cross-config.amd64	2019-04-06 07:21:56.0 +0200
+++ dpkg-cross-2.6.15/config/cross-config.amd64	2020-06-21 21:29:37.0 +0200
@@ -6,16 +6,3 @@
 #
 ac_cv_c_bigendian=no
 ac_cv_c_char_unsigned=no
-ac_cv_sizeof_long_long=8
-ac_cv_sizeof_unsigned_long_long=8
-ac_cv_sizeof_long=8
-ac_cv_sizeof_unsigned_long=8
-ac_cv_sizeof_int=4
-ac_cv_sizeof_unsigned_int=4
-ac_cv_sizeof_short=2
-ac_cv_sizeof_unsigned_short=2
-ac_cv_sizeof_short=2
-ac_cv_sizeof_unsigned_short=2
-ac_cv_sizeof_float=4
-ac_cv_sizeof_double=8
-ac_cv_sizeof_long_double=16
diff --minimal -Nru dpkg-cross-2.6.15/config/cross-config.arm64 dpkg-cross-2.6.15/config/cross-config.arm64
--- dpkg-cross-2.6.15/config/cross-config.arm64	2015-01-22 20:10:23.0 +0100
+++ dpkg-cross-2.6.15/config/cross-config.arm64	2020-06-21 21:29:37.0 +0200
@@ -6,23 +6,6 @@
 # now ensure the real architecture-dependent values take priority
 ac_cv_c_bigendian=no
 ac_cv_c_char_unsigned=yes
-ac_cv_sizeof_long_long=8
-ac_cv_sizeof_unsigned_long_long=8
-ac_cv_sizeof_long=8
-ac_cv_sizeof_unsigned_long=8
-ac_cv_sizeof_int=4
-ac_cv_sizeof_unsigned_int=4
-ac_cv_sizeof_short=2
-ac_cv_sizeof_unsigned_short=2
-ac_cv_sizeof_char=1
-ac_cv_sizeof_unsigned_char=1
-ac_cv_sizeof_signed_char=1
-ac_cv_sizeof_float=4
-ac_cv_sizeof_double=8
-ac_cv_sizeof_long_double=16
-ac_cv_sizeof_void_p=8
-ac_cv_sizeof_char_p=8
-ac_cv_sizeof_time_t=8
 
 #lots of things: turn off stack protector
 libc_cv_fno_stack_protector=no
@@ -43,7 +26,6 @@
 #Verifed with native test program
 apr_cv_mutex_robust_shared=yes
 #probably more general than just APR. verifed by cross compiling and running test from configure
-ac_cv_sizeof_struct_iovec=16
 
 # mysql
 # mysql wants to know stack direction:
diff --minimal -Nru dpkg-cross-2.6.15/config/cross-config.armel dpkg-cross-2.6.15/config/cross-config.armel
--- dpkg-cross-2.6.15/config/cross-config.armel	2015-01-22 20:17:29.0 +0100
+++ dpkg-cross-2.6.15/config/cross-config.armel	2020-06-21 21:29:37.0 +0200
@@ -3,22 +3,6 @@
 # now ensure the real architecture-dependent values take priority
 ac_cv_c_bigendian=no
 ac_cv_c_char_unsigned=yes
-ac_cv_sizeof_long_long=8
-ac_cv_sizeof_unsigned_long_long=8
-ac_cv_sizeof_long=4
-ac_cv_sizeof_unsigned_long=4
-ac_cv_sizeof_int=4
-ac_cv_sizeof_unsigned_int=4
-ac_cv_sizeof_short=2
-ac_cv_sizeof_unsigned_short=2
-ac_cv_sizeof_char=1
-ac_cv_sizeof_unsigned_char=1
-ac_cv_sizeof_signed_char=1
-ac_cv_sizeof_float=4
-ac_cv_sizeof_double=8
-ac_cv_sizeof_long_double=8
-ac_cv_sizeof_void_p=4
-ac_cv_sizeof_char_p=4
 
 path=`dirname $ac_site_file`
 # now allow package-specific architecture-independent values to be set
diff --minimal -Nru dpkg-cross-2.6.15/config/cross-config.armhf dpkg-cross-2.6.15/config/cross-config.armhf
--- dpkg-cross-2.6.15/config/cross-config.armhf	2015-01-22 20:16:56.0 +0100
+++ dpkg-cross-2.6.15/config/cross-config.armhf	2020-06-21 21:29:37.0 +0200
@@ -3,22 +3,6 @@
 # now ensure the real architecture-dependent values take priority
 ac_cv_c_bigendian=no
 ac_cv_c_char_unsigned=yes
-ac_cv_sizeof_long_long=8
-ac_cv_sizeof_unsigned_long_long=8
-ac_cv_sizeof_long=4
-ac_cv_sizeof_unsigned_long=4
-ac_cv_sizeof_int=4
-ac_cv_sizeof_unsigned_int=4
-ac_cv_sizeof_short=2
-ac_cv_sizeof_unsigned_short=2
-ac_cv_sizeof_char=1
-ac_cv_sizeof_unsigned_char=1
-ac_cv_sizeof_signed_char=1
-ac_cv_sizeof_float=4
-ac_cv_sizeof_double=8
-ac_cv_sizeof_long_double=8
-ac_cv_sizeof_void_p=4
-ac_cv_sizeof_char_p=4
 
 path=`dirname $ac_site_file`
 # now allow package-specific architecture-independent values to be set
diff --minimal -Nru dpkg-cross-2.6.15/config/cross-config.cache dpkg-cross-2.6.15/config/cross-config.cache
--- dpkg-cross-2.6.15/config/cross-config.cache	

Bug#205634: CD with repeated names are NOT so rare.

[Osamu Aoki]

There are many CD album which consists of multiple CDs and they come
with the same CD title for the album.  CD with  repeated names are NOT
so rare.  (Colliding musicbrainz discid should be rare.)

Following bug is addresses such case.

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

So applying these patches should address most cases.

But adding some sanity check in do_move stll diesn't hart 

may be around L1737

run_command "movetrack-$1" mv "${ABCDETEMPDIR}/track$1.$OUTPUT"
"$OUTPUTDIR/$OUTPUTFILE.$OUTPUT"

Osamu

Bug#961417: RFS: libudfread/1.0.0-1 -- UDF reader library

[Vasyl Gello]

Hi Mattia!

Good to know you are back! Hope you are well :)

>Mhh, would you please instead consider joining it now, rather than move
>stuff around later?  I don't think I saw your joining mail in the last
>20 days (sorry for ghosting - I had some personal matters going on).

>Then, I notice that you are bumping the version while uploading to
>mentors.  In the end we shall only upload a -1 with only one changelog
>entry to the archive, so feel free to just remove and re-upload the -1
>version to mentors (IIRC you can also just re-upload the same version
>and it would overwrite it).

I fixed the versioning and maintainership of the package and re-uploaded
it cleanly as 1.0.0-1 targeting unstable (since I know now that experimental
is basically unstable + some NEW queue with breaking changes)

I will reopen this bug now & send an 'official' team join request.

Now, after I overhauled Kodi package (including copyrights)
and made it and all deps building and running on buster-bpo,
I think I am eligible to join :)
-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com

Skype: vasek.gello
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Bug#954263: CD release consists of multiple CDs

[Osamu Aoki]

control: tags -1 patch

The handling of CD release consists of multiple CDs is a complicated
issue.

There are 2 basic approach to support multi-disk CD set.  

* Option 1: Mangle CD# into track serial number
* Option 2: Mangle CD# into album name

What the -W option does is more along Option 1.

What the bug reporter wishes to do seems to be more along Option 2 and
I created patch as attached.  The unused -I was used to allow appendung
text.  (-W is not for album)

The -W option needs some fixes which I reported to upstream with patch
as:

  https://abcde.einval.com/bugzilla/show_bug.cgi?id=144


If you want patched file or git repo of all I mentioned issues, I
pushed code to

  https://github.com/osamuaoki/abcde/blob/master/abcde

Osamu
From ab1fe743df8e8db7f843ed3d12c19af5f6d7c592 Mon Sep 17 00:00:00 2001
From: Osamu Aoki 
Date: Mon, 22 Jun 2020 10:21:30 +0900
Subject: [PATCH 2/2] Append extra album name text to the album name

Signed-off-by: Osamu Aoki 
---
 abcde | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/abcde b/abcde
index ff143ac..689867e 100755
--- a/abcde
+++ b/abcde
@@ -39,6 +39,8 @@ echo "-g Use \"lame --nogap\" for MP3 encoding. Disables low disk and pipes
 echo "-G Get album art by using the 'getalbumart' action"
 echo "-h This help information"
 #echo "-iTag files while encoding, when possible (local only) -NWY-"
+echo "-I "
+echo "   Append extra album name text to the album name before munge"
 echo "-j <#> Number of encoder processes to run at once (localhost)"
 echo "-k Keep the wav tracks for later use"
 echo "-l Use low disk space algorithm"
@@ -4144,7 +4146,7 @@ case "$EXTRAVERBOSE" in
 esac
 
 # Parse command line options
-while getopts 1a:bBc:C:d:DefgGhj:klLmMnNo:pPQ:r:s:S:t:T:UvVxX:w:W:z opt ; do
+while getopts 1a:bBc:C:d:DefgGhI:j:klLmMnNo:pPQ:r:s:S:t:T:UvVxX:w:W:z opt ; do
 	case "$opt" in
 		1) ONETRACK=y ;;
 		a) ACTIONS="$OPTARG" ;;
@@ -4168,6 +4170,7 @@ while getopts 1a:bBc:C:d:DefgGhj:klLmMnNo:pPQ:r:s:S:t:T:UvVxX:w:W:z opt ; do
 		g) NOGAP=y ;;
 		G) GETALBUMART=y ;;
 		i) INLINETAG=y ;;
+		I) DALBUMTAIL="$OPTARG" ;;
 		j) MAXPROCS="$OPTARG" ;;
 		k) KEEPWAVS=y ;;
 		l) LOWDISK=y ;;
@@ -5202,6 +5205,8 @@ if [ "$DOCDDB" = "y" ]; then
 	do_cddbedit
 
 	eval "$($CDDBTOOL parse "$CDDBDATA")"
+	# Append extra album name text to the album name before munge
+	DALBUM="${DALBUM}${DALBUMTAIL}"
 fi
 
 # Before reading tracks, we set the speed of the device
-- 
2.20.1

Bug#963471: procps: Rexecutes command on terminal size change (SIGWINCH signal)

[Witold Baryluk]

Package: procps
Version: 2:3.3.16-5
Severity: normal

It appears watch programs reacts to some signals in undocumented manner.

On receving SIGWINCH (terminal size change) it reexecutes the command and
redraws. That might be problematic, as sometimes watch is to trigger
periodic events, and resizing a window will send big number of signal in
quick succession as the size is changing when the user moves the mouse.


I think using SIGUSR1 (like dd) or SIGINFO (like most bsd tools), could
be a better option.

Or only rerun the command if the window is resized to be bigger than the
current size?




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

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

Versions of packages procps depends on:
ii  init-system-helpers  1.57
ii  libc62.30-8
ii  libncurses6  6.2-1
ii  libncursesw6 6.2-1
ii  libprocps8   2:3.3.16-5
ii  libtinfo66.2-1
ii  lsb-base 11.1.0

Versions of packages procps recommends:
ii  psmisc  23.3-1

procps suggests no packages.

-- no debconf information

Bug#963176: Unable to run any programs due to kernelbase.dll failed to initialize.

[Michael Gilbert]

control: tag -1 moreinfo
control: severity -1 important

On Fri, Jun 19, 2020 at 11:09 PM Gong S. wrote:
> The current version of wine-development cannot launch any Windows programs, 
> including built-in ones like "winecfg" and "wineconsole".

I am not able to reproduce this on i386.  Is this on an arm system?

Either way, can you provide relevant output from

$ WINEDEBUG=+all winecfg-development

Best wishes,
Mike

Bug#959536: Synaptic does not run from XFCE desktop menu

[Ian Laurie]

If you execute that same command at the command line that is in the /usr/share/applications/synapic.desktop file you get the following results:

 

 

bullseye$ synaptic-pkexec
 AUTHENTICATING FOR com.ubuntu.pkexec.synaptic ===
Authentication is required to run the Synaptic Package Manager
Authenticating as: Ian,,, (ian)
Password:
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.
bullseye$

 

 

Bug#963470: qemu-system-data: slof.bin unreproducible when locale varies

[Vagrant Cascadian]

Package: qemu-system-data
Version: 1:5.0-5
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: locale
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

When the environment locale varies, the translated output of "ld -V"
gets embedded into slof.bin.

The attached patch fixes this by always running ld under the C locale.

Unfortunately, there is still an outstanding issue preventing slof.bin
from building reproducibly I have been unable to identify, but this
significantly reduces the resulting diff.


live well,
  vagrant

From: Vagrant Cascadian 
Date: Mon, 22 Jun 2020 00:40:39 +
X-Dgit-Generated: 1:5.0-6~0~20200622~0 973dc2cba2b12d0fc4706ad75af36abcab4f6da9
Subject: slof/Makefile.gen: Ensure ld is called with the C locale.

The output of "ld -V" changes based on the environment's locale.

---

--- qemu-5.0.orig/roms/SLOF/Makefile.gen
+++ qemu-5.0/roms/SLOF/Makefile.gen
@@ -62,7 +62,7 @@ romfs_build:
 ../build_info.img:
 	@echo "$(CC)" > ../build_info.img
 	@$(CC) -v >> ../build_info.img 2>&1
-	@$(LD) -V >> ../build_info.img 2>&1
+	@$(LC_ALL=C $(LD) -V) >> ../build_info.img 2>&1
 
 ../$(SUBBOARD).dtb:
 	@if [ -e dts/$(SUBBOARD).dts ]; then \


signature.asc
Description: PGP signature

Bug#963469: cdrom: /dev/sr0 scanned on and on for no visible reason

[kj]

Package: cdrom
Severity: normal

For no obvious reason, my current system started scanning /dev/sr0 (i.e.
my DVD drive, even without any media inserted) about once every 30 to 60
seconds.

After reboot, I wouldn't expect that behaviour to continue, but it did.

Removing the entry "/dev/sr0 /media/cdrom0" from /etc/fstab didn't make
that stop.

For explanation: My DVD drive is loud. I don't want to hear the
repositioning noise every so-and-so-seconds. And, who does this, for what
reason?

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

Kernel: Linux 4.19.0-9-amd64 (SMP w/6 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 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#963341: cfengine3: New cfengine 3.15.2 package is broken and non-functional

[Michael Berg]

The removal scripts in the new cfengine 3.15.2 packages also have issues.

While cleaning up after my testing for the initial bug report, I
encountered the following.

# apt-get purge cfengine3
Reading package lists... Done
Building dependency tree  
Reading state information... Done
The following packages will be REMOVED:
  cfengine3*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 318526 files and directories currently installed.)
Purging configuration files for cfengine3 (3.15.2-2) ...
rmdir: failed to remove '/var/lib/cfengine3': Directory not empty
dpkg: error processing package cfengine3 (--purge):
 installed cfengine3 package post-removal script subprocess returned
error exit status 1
Errors were encountered while processing:
 cfengine3
E: Sub-process /usr/bin/dpkg returned an error code (1)

All attempts to remove the package failed until I manually deleted the
/var/lib/cfengine3 directory. After manually removing that directory,
the "apt-get purge cfengine3" finally succeeded.

Bug#938605: svgtune: Python2 removal in sid/bullseye - reopen 938605

[Sandro Tosi]

> Old python ones are listed only as alternative dependencies to easy backports 
> for ancient systems.
> https://packages.debian.org/sid/svgtune
> I don't think this package holds any python removal

I can understand how ease of backporting could be valuable, but the
python2 transition is way too complicated to be able to capture all
these special cases. It would help greatly if the package in sid could
have no python2 dependencies (if there's need to backport this package
frequently, a separate git branch is probably easy enough to maintain
within a usual git workflow).

Thanks for considering,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#936757: jackd2: Python2 removal in sid/bullseye

[Sandro Tosi]

Hello again,

> On Mon, 21 Oct 2019 14:46:54 +0200 Reiner Herrmann  wrote:
> > Control: tags -1 + fixed-upstream
> > Control: forwarded -1 https://github.com/jackaudio/jack2/pull/352
> >
> > The new upstream release 1.9.13 has support for Python 3.
>
> can someone look at this bug soon, please? along with #959177 it seems
> that the newer releases of jack have been ported to python3, so we
> "just" need to upgrade to it. Porting jack to python3 will clear one
> of the only 2 remaining reverse dependencies of python-dbus

pinging this bug again in hope something could be done; it looks like
1.9.14 has been imported into the git repo, which is python3
compatible, but the dependencies are still pointing to python instead
of python3; furthermore, the only python script that uses `dbus` is
example-clients/jack_control (AFAICT) which is an example, so i think
python-dbus should be downgraded to a Suggests and of course switched
over to python3-dbus.

Let me know if i can help in any way to have jackd2 uploaded to sid
with its dependencies switched over to python3: jackd2 is the only
r-dep of python-dbus, which could be removed, allowing the removal
python-gi too.

Regards.
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#963341: cfengine3: New cfengine 3.15.2 package is broken and non-functional

[Michael Berg]

Package: cfengine3
Version: 3.15.2-2
Severity: grave
Justification: renders package unusable

First, thank you for packaging cfengine 3.15.2.

Unfortunately, the new cfengine 3.15.2 package in sid/unstable is
broken and non-functional.

What led up to the situation?
Upgrading from cfengine 3.12.1 to 3.15.2.
Fresh installs of 3.15.2 also suffer from the problem.

Under an installation of Debian's cfengine 3.12.1, bootstrapping a
cfengine node works correctly, and cf-promises has variables like
"default:sys.cf_agent" defined.
This same behavior is seen using the cfengine community edition
packages from https://cfengine.com/product/community/

Here is example output from Debian's cfengine 3.12.1:

# cf-promises --show-vars | grep sys.cf_
...
default:sys.cf_agent \"/var/lib/cfengine3/bin/cf-agent\"
  cfe_internal,source=agent   
default:sys.cf_check \"/var/lib/cfengine3/bin/cf-check\"
  cfe_internal,source=agent   
default:sys.cf_execd \"/var/lib/cfengine3/bin/cf-execd\"
  cfe_internal,source=agent   
default:sys.cf_key   \"/var/lib/cfengine3/bin/cf-key\"  
  cfe_internal,source=agent   
default:sys.cf_monitord  \"/var/lib/cfengine3/bin/cf-monitord\" 
  cfe_internal,source=agent   
default:sys.cf_net   \"/var/lib/cfengine3/bin/cf-net\"  
  cfe_internal,source=agent   
default:sys.cf_promises  \"/var/lib/cfengine3/bin/cf-promises\" 
  cfe_internal,source=agent   
default:sys.cf_runagent  \"/var/lib/cfengine3/bin/cf-runagent\" 
  cfe_internal,source=agent   
default:sys.cf_serverd   \"/var/lib/cfengine3/bin/cf-serverd\"  
  cfe_internal,source=agent   
default:sys.cf_twin  \"/var/lib/cfengine3/bin/cf-agent\"
  cfe_internal,source=agent   
default:sys.cf_upgrade   \"/var/lib/cfengine3/bin/cf-upgrade\"  
  cfe_internal,source=agent   
default:sys.cf_version   3.12.1 
  inventory,source=agent,attribute_name=CFEngine version
default:sys.cf_version_major 3  
  source=agent
default:sys.cf_version_minor 12 
  source=agent
default:sys.cf_version_patch 1  
  source=agent

Here is example output from CFEngine Community edition 3.15.2:

# cf-promises --show-vars | grep sys.cf_
...
default:sys.cf_agent \"/var/cfengine/bin/cf-agent\" 
  cfe_internal,source=agent
default:sys.cf_check \"/var/cfengine/bin/cf-check\" 
  cfe_internal,source=agent
default:sys.cf_execd \"/var/cfengine/bin/cf-execd\" 
  cfe_internal,source=agent
default:sys.cf_key   \"/var/cfengine/bin/cf-key\"   
  cfe_internal,source=agent
default:sys.cf_monitord  \"/var/cfengine/bin/cf-monitord\"  
  cfe_internal,source=agent
default:sys.cf_net   \"/var/cfengine/bin/cf-net\"   
  cfe_internal,source=agent
default:sys.cf_promises  \"/var/cfengine/bin/cf-promises\"  
  cfe_internal,source=agent
default:sys.cf_runagent  \"/var/cfengine/bin/cf-runagent\"  
  cfe_internal,source=agent
default:sys.cf_serverd   \"/var/cfengine/bin/cf-serverd\"   
  cfe_internal,source=agent
default:sys.cf_twin  \"/var/cfengine/bin/cf-agent\" 
  cfe_internal,source=agent
default:sys.cf_upgrade   \"/var/cfengine/bin/cf-upgrade\"   
  cfe_internal,source=agent
default:sys.cf_version   3.15.2 
  inventory,source=agent,attribute_name=CFEngine version
default:sys.cf_version_major 3  
  source=agent
default:sys.cf_version_minor 15 
  source=agent
default:sys.cf_version_patch 2  
  source=agent
default:sys.cf_version_release   

Bug#963265: simple-cdd: Improve qemu support

[John Franklin]

On Sun, Jun 21, 2020 at 1:32 PM, Vagrant Cascadian  
wrote:

On 2020-06-21, John Franklin wrote:


 * Change the name to qemu-test.hd.qcow2 to make it more obvious to 
a developer

 what the file is and its format.


I'd prefer not to change the filename, as then it would have to be
changed whenever the file format changes.


If the format changes, then the extension should change, too.  That's 
not a heavy lift.




 * Move the file to the $simple_cdd_tmp folder, in a qemu subfolder, 
to better

 organize it with the rest fo the temporary build files.


Mixed feelings on this; wondering if it wouldn't make sene to go into
the images folder instead. Or maybe $simple_cdd_tmp is fine.


The images folder is where final artifacts end up.  All the rest of the 
intermediary files are in the tmp directory.  This patch puts it in a 
place dedicated to the qemu part of the process.  If you're runnig with 
UEFI firmware, you may want to include `-drive 
if=pflash,format=raw,file=profile_OVMF_VARS.fd` to define where the 
UEFI nvram should be stored.  In that case, the nvram file should also 
be in the tmp/qemu directory.  (Future patch coming!)



It does seem to change commented out example size, which doesn't seem
necessary, it only being an example? I think I had put an example in
there which was a non-default value for qemu-img at the time... but in
general I'd like to keep the defaults to whatever qemu-img spits out.


Size is a required parameter if the file doesn't already exist.

```
$ qemu-img create test.img
qemu-img: test.img: Image creation needs a size parameter
```


 * If hd_img isn't an absolute path, store it in tmp/qemu.


Mixed feelings on that, as mentioned above.


Happy to merge most of it; could you re-write the git history so that
the contested points are in separate commits? Then I can merge the
uncontested patches while we sort out the remainder.



Done.

jf
--
John Franklin
frank...@sentaidigital.com

Bug#963468: Update Drawing in Backports

[Leandro Cunha]

Package: sponsorship-requests
Severity: important

Dear mentors,

To update the Drawing package from one version to another in backports
which, according to the documentation, needs a sponsor, for the
collaborators who are neither developer nor maintainer. The with the
changes link is available below.

Link to Salsa: 
https://salsa.debian.org/leandrocunha/drawing/-/tree/debian/buster-backports

https://tracker.debian.org/news/1150531/accepted-drawing-0411-1bpo101-amd64-source-into-buster-backports-buster-backports/

https://tracker.debian.org/pkg/drawing

https://backports.debian.org/Contribute/#index3h3

Regards,


Leandro Cunha

Bug#963467: qemu-system-data: embeds hostname and timestamp in hppa-firmware.img

[Vagrant Cascadian]

Package: qemu-system-data
Version: 1:3.1+dfsg-8+deb10u5
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps hostname
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The attached patch removes the hostname of the build machine from the
version used and sets the timestamp in the version to use the value
provided by SOURCE_DATE_EPOCH:

  https://reproducible-builds.org/docs/source-date-epoch/

live well,
  vagrant

From: Vagrant Cascadian 
Date: Sun, 21 Jun 2020 19:38:39 +
X-Dgit-Generated: 1:5.0-6~0~20200621~20 92cdacf1c512114ca313800748a5fc162775f51e
Subject: roms/seabios-hppa: Use consistant date and remove hostname.

Two issues break reproducibility; the time and hostname get embedded
in the resulting seabios binary.

Simply drop the hostname from the embedded version string, as it
shouldn't be needed in Debian package builds.

Use the SOURCE_DATE_EPOCH environment variable to set the build date
rather than the current time:

  https://reproducible-builds.org/docs/source-date-epoch/

---

--- qemu-5.0.orig/roms/seabios-hppa/scripts/buildversion.py
+++ qemu-5.0/roms/seabios-hppa/scripts/buildversion.py
@@ -125,9 +125,8 @@ def main():
 if not ver:
 ver = "?"
 if not cleanbuild:
-btime = time.strftime("%Y%m%d_%H%M%S")
-hostname = socket.gethostname()
-ver = "%s-%s-%s" % (ver, btime, hostname)
+btime = time.strftime("%Y%m%d_%H%M%S", time.gmtime(int(os.environ.get('SOURCE_DATE_EPOCH', time.time()
+ver = "%s-%s" % (ver, btime)
 write_version(outfile, ver + options.extra, toolstr)
 
 if __name__ == '__main__':


signature.asc
Description: PGP signature

Bug#963466: qemu-system-data: Use reproducible timestamps in openbios roms

[Vagrant Cascadian]

Package: qemu-system-data
Version: 1:5.0-5
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The various openbios roms include time and date information embedded in
the binary.

The attached patch uses the SOURCE_DATE_EPOCH environment variable,
which is exported by dpkg-buildpackage, to set the date to a consistant
value between builds. It relies on features of GNU date in order to keep
the patch simple, though that may prevent it from being upstreamable.

Thanks for maintaining qemu!


live well,
  vagrant

From: Vagrant Cascadian 
Date: Sun, 21 Jun 2020 19:27:11 +
X-Dgit-Generated: 1:5.0-6~0~20200621~20 0b5923e6cc49abffd582177ba8558cfb6c7f10ce
Subject: roms/openbios: Use SOURCE_DATE_EPOCH in Makefile.

Embedding the build time breaks reproducibility. Instead, use the date
specified by the SOURCE_DATE_EPOCH environment variable:

  https://reproducible-builds.org/docs/source-date-epoch/

This patch relies on features of GNU date, and will need further
changes for portability to other systems.

---

--- qemu-5.0.orig/roms/openbios/Makefile.target
+++ qemu-5.0/roms/openbios/Makefile.target
@@ -54,14 +54,14 @@ versions: $(ODIR)/target/include/openbio
 
 $(ODIR)/forth/version.fs:
 	$(call quiet-command,true, "  GEN   $(TARGET_DIR)$@")
-	@DATE="$(shell echo `LC_ALL=C TZ=UTC date +'%b %e %Y %H:%M'`)" ;  \
+	@DATE="$(shell echo `LC_ALL=C date --utc --date=@$(SOURCE_DATE_EPOCH) +'%b %e %Y %H:%M'`)" ;  \
 		( echo ": builddate \" $$DATE\" ; " ; \
 		  echo ": version \" $(VERSION)\" ; " ; ) \
 		  > $(dir $@)/version.fs
 
 $(ODIR)/target/include/openbios-version.h:
 	$(call quiet-command,true, "  GEN   $(TARGET_DIR)$@")
-	@DATE="$(shell echo `LC_ALL=C TZ=UTC date +'%b %e %Y %H:%M'`)" ; \
+	@DATE="$(shell echo `LC_ALL=C date --utc --date=@$(SOURCE_DATE_EPOCH) +'%b %e %Y %H:%M'`)" ; \
   ( echo "#define OPENBIOS_BUILD_DATE \"$$DATE\"" ; \
echo "#define OPENBIOS_VERSION_STR \"$(VERSION)\"" ; ) \
  > $(dir $@)/openbios-version.h


signature.asc
Description: PGP signature

Bug#963357: marked as pending in libtest-redisserver-perl

[gregor herrmann]

On Sun, 21 Jun 2020 21:21:53 +, gregor herrmann wrote:

> https://salsa.debian.org/perl-team/modules/packages/libtest-redisserver-perl/-/commit/19f316173f96e6781ca139f630c32ec12191bde2
> 
> 
> Add patch to fix test failure in t/unknown_conf.t.
> 
> Apparently the error message in Redis 6.0.5 changed, so update the regexp in
> the test.
> 
> Closes: #963357
> Thanks: Lucas Nussbaum for the bug report.
> 

Well, yes, except that the build fails on the buildd:

https://buildd.debian.org/status/fetch.php?pkg=libtest-redisserver-perl=all=0.21-2=1592776913=0

empty port not found at /usr/share/perl5/Net/EmptyPort.pm line 66.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 22 just after 6.


*sigh*


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Dire Straits: Private Investigations


signature.asc
Description: Digital Signature

Bug#963327: [Pkg-zsh-devel] Processed: Merge duplicates

[Adrian Bunk]

On Mon, Jun 22, 2020 at 12:05:00AM +0200, Axel Beckert wrote:
> Control: unmerge 963420
> Control: reassign 963420 src:zsh
> Control: retitle 963420 zsh: FTBFS: sh: 1: colcrt: not found
> Control: found 963420 5.8-4
> Control: affects 963420 =
> 
> Dear Adrian,
> 
> Debian Bug Tracking System wrote:
> > > reassign 963420 bsdmainutils 12.1.1
> > Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found
> > Bug reassigned from package 'src:zsh' to 'bsdmainutils'.
> > No longer marked as found in versions zsh/5.8-4.
> [...]
> > > retitle 963327 bsdmainutils needs Breaks on util-linux versions without 
> > > the tools removed in 12.1.1
> 
> I disagree that this would help in the case of the zsh FTBFS in
> #963420.
>...

I already updated the title of the mass-merged bug to
"bsdmainutils must depend on bsdextrautils".

This is anyway mandatory for not breaking upgrades from buster.

>   Regards, Axel

cu
Adrian

Bug#963327: [Pkg-zsh-devel] Processed: Merge duplicates

[Axel Beckert]

Hi Adrian,

Adrian Bunk wrote:
> > > > retitle 963327 bsdmainutils needs Breaks on util-linux versions without 
> > > > the tools removed in 12.1.1
> > 
> > I disagree that this would help in the case of the zsh FTBFS in
> > #963420.
> >...
> 
> I already updated the title of the mass-merged bug to
> "bsdmainutils must depend on bsdextrautils".

Ah, sorry, missed that.

> This is anyway mandatory for not breaking upgrades from buster.

If you don't mind I'll nevertheless fix that directly in zsh as it
will likely come back again as transition after bullseye.
Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#963420: [Pkg-zsh-devel] Processed: Merge duplicates

[Axel Beckert]

Control: unmerge 963420
Control: reassign 963420 src:zsh
Control: retitle 963420 zsh: FTBFS: sh: 1: colcrt: not found
Control: found 963420 5.8-4
Control: affects 963420 =

Dear Adrian,

Debian Bug Tracking System wrote:
> > reassign 963420 bsdmainutils 12.1.1
> Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found
> Bug reassigned from package 'src:zsh' to 'bsdmainutils'.
> No longer marked as found in versions zsh/5.8-4.
[...]
> > retitle 963327 bsdmainutils needs Breaks on util-linux versions without the 
> > tools removed in 12.1.1

I disagree that this would help in the case of the zsh FTBFS in
#963420.

And as you might have guessed from my reply to the bug report, I'm
already in the process of fixing it.

Hence removing it from that mass-bug-merging again.

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

Bug#962307: Acknowledgement (RFS: anymeal/1.0-1 ITA -- Cookbook database for storing recipes)

[Jan Wedekind]

Hello,
I have released version 1.1 in the meantime. It is available here:

https://mentors.debian.net/package/anymeal

Also it can be downloaded as follows:

dget -x 
https://mentors.debian.net/debian/pool/main/a/anymeal/anymeal_1.1-1.dsc

Regards
Jan

Bug#684382: PHP bindings for libhdate

[Ariel]

Source: libhdate
Version: 1.6.02-1
Followup-For: Bug #684382

Here is an updated patch for php7.

-- System Information:
Debian Release: 9.12
  APT prefers oldstable
  APT policy: (990, 'oldstable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.9.210 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Naur old/bindings/php/Makefile.am new/bindings/php/Makefile.am
--- old/bindings/php/Makefile.am2020-06-21 16:01:58.0 -0400
+++ new/bindings/php/Makefile.am2020-06-21 16:57:11.0 -0400
@@ -5,17 +5,17 @@
 
 DEPS= $(top_builddir)/src/libhdate.la
 
-CLEANFILES = *.o *.cpp *.h *.so *.php *wrap*
+CLEANFILES = *.o *.cpp *.cxx *.h *.so *.php *wrap*
 
 all-am: hdate.so

 
-hdate.so: hdate_wrap.cpp
-   g++ -I$(top_srcdir)/src `php-config --includes` -fpic -c hdate_wrap.cpp
+hdate.so: hdate_wrap.cxx
+   g++ -I$(top_srcdir)/src `php-config --includes` -fpic -c hdate_wrap.cxx
gcc -shared hdate_wrap.o ../../src/.libs/libhdate.so -lstdc++ -o 
hdate.so
 
-hdate_wrap.cpp: hdate.i
-   swig -php5 -c++ hdate.i
+hdate_wrap.cxx: hdate.i
+   swig -php7 -c++ hdate.i
 
 install-data-local: hdate.so hdate.ini hdate.php
$(mkinstalldirs) $(DESTDIR)$(PH_MODULES_PATH)
diff -Naur old/configure.in new/configure.in
--- old/configure.in2020-06-21 16:01:58.0 -0400
+++ new/configure.in2020-06-21 16:24:56.0 -0400
@@ -184,13 +184,13 @@
   [path to php site lib])])
 
 if test "$have_php" = "yes"; then
- AC_CHECK_PROG(have_php_config, "php-config5", yes, no)
+ AC_CHECK_PROG(have_php_config, "php-config", yes, no)
  if test "$have_php_config" = "yes"; then
  
  PH_CONFIG_PATH=`php --ini |  grep "Scan" | cut -d: -f2 | sed 
's/\s//g'`
  PH_INCLUDE_PATH=`php -r "echo get_include_path();" | cut -f2 -d:`
  if test "$with_php_sitelib_dir" = "" ; then
-   PH_MODULES_PATH=`php-config5 --extension-dir`
+   PH_MODULES_PATH=`php-config --extension-dir`
  else
PH_MODULES_PATH=$with_php_sitelib_dir
  fi
diff -Naur old/debian/control new/debian/control
--- old/debian/control  2017-01-24 12:08:21.0 -0500
+++ new/debian/control  2020-06-21 16:21:59.0 -0400
@@ -6,7 +6,7 @@
 Vcs-Svn: svn://anonscm.debian.org/debian-hebrew/pkg/libhdate/trunk
 Vcs-Browser: https://anonscm.debian.org/viewvc/debian-hebrew/pkg/libhdate/trunk
 Build-Depends: debhelper (>= 9),
- swig,
+ swig (>= 3.0.12-1),
  python-dev (>= 2.6.6-3~),
  dh-python,
  dh-autoreconf,
@@ -53,6 +53,19 @@
  .
  This package contains perl bindings to libhdate
 
+Package: libhdate-php
+Section: php
+Architecture: any
+Depends: libhdate1 (= ${binary:Version}), ${php:Depends}, ${shlibs:Depends}, 
${misc:Depends}
+Description: Provides a library that help use hebrew dates (php bindings)
+ LibHdate is a small C,C++ library for Hebrew dates,
+ holidays, and reading sequence (parasha). It is using 
+ the source code from Amos Shapir's "hdate" package fixed 
+ and patched by Nadav Har'El. The Torah reading sequence
+ is from tables by Zvi Har'El.
+ .
+ This package contains PHP bindings to libhdate
+
 Package: libhdate1
 Section: libs
 Architecture: any
diff -Naur old/debian/control.orig new/debian/control.orig
--- old/debian/control.orig 1969-12-31 19:00:00.0 -0500
+++ new/debian/control.orig 2017-01-24 12:08:21.0 -0500
@@ -0,0 +1,83 @@
+Source: libhdate
+Priority: optional
+Section: libdevel
+Maintainer: Debian Hebrew Packaging Team 

+Uploaders: Lior Kaplan , Shachar Shemesh 
, Tzafrir Cohen 
+Vcs-Svn: svn://anonscm.debian.org/debian-hebrew/pkg/libhdate/trunk
+Vcs-Browser: https://anonscm.debian.org/viewvc/debian-hebrew/pkg/libhdate/trunk
+Build-Depends: debhelper (>= 9),
+ swig,
+ python-dev (>= 2.6.6-3~),
+ dh-python,
+ dh-autoreconf,
+Standards-Version: 3.9.8
+Homepage: http://libhdate.sourceforge.net/
+
+Package: libhdate-dev
+Architecture: any
+Depends: libhdate1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
+Description: Provides a library that help use Hebrew dates (development files)
+ LibHdate is a small C,C++ library for Hebrew dates,
+ holidays, and reading sequence (parasha). It is using 
+ the source code from Amos Shapir's "hdate" package fixed and 
+ patched by Nadav Har'El. The Torah reading sequence
+ is from tables by Zvi Har'El.
+ .
+ This package contains headers and support files required
+ to build new applications with libhdate.
+
+Package: python-hdate
+Section: python
+Architecture: any
+Provides: ${python:Provides}
+Depends: libhdate1 (= ${binary:Version}), ${python:Depends}, 
${shlibs:Depends}, ${misc:Depends}
+Description: Provides a library that help use Hebrew dates (Python bindings)
+ LibHdate is a small C,C++ library for 

Bug#961362: fonts-terminus-otb: In rxvt-unicode, M and m characters missing the left vertical stroke

[Matti Hämäläinen]

Hello,

I ran into this problem myself (using "URxvt*font: xft:Terminus:pixelsize=20"
font spec), and seems it is some kind of bug in rxvt-unicode.
Xterm does not suffer from this issue with the same font spec.

The issue seems to reside in src/rxvtfont.C rxvt_font_xft::draw()
with the doublebuffered rendering, if you disable buffering via
"URxvt*buffered: false", the issue disappears at least for my use case.

But, disabling buffering is probably not a very efficient solution.

Also a kludge-patching line 1380 of src/rxvtfont.C:

-  int x_ = buffered ? 0 : x;
+  int x_ = buffered ? 1 : x;

"fixes" the issue as well at least for the case I bothered to check, but 
obviously that's not a good solution either.


Perhaps this issue should be transferred to package rxvt-unicode?

--
] ccr/TNSP ^ pWp  ::  c...@tnsp.org  ::  https://tnsp.org/~ccr/
] https://tnsp.org/hg/ -- https://www.openhub.net/accounts/ccr
] PGP key: 7BED 62DE 898D D1A4 FC4A  F392 B705 E735 307B AAE3

Bug#963439: ncbi-entrez-direct: FTBFS: obj-x86_64-linux-gnu/src/golang.org/x/sys/unix/syscall_unix.go:16:2: cannot find package "golang.org/x/sys/internal/unsafeheader" in any of:

[Aaron M. Ucko]

Lucas Nussbaum  writes:

>> obj-x86_64-linux-gnu/src/golang.org/x/sys/unix/syscall_unix.go:16:2: cannot 
>> find package "golang.org/x/sys/internal/unsafeheader" in any of:
>>  /usr/lib/go-1.14/src/golang.org/x/sys/internal/unsafeheader (from 
>> $GOROOT)
>>  
>> /<>/obj-x86_64-linux-gnu/src/golang.org/x/sys/internal/unsafeheader
>>  (from $GOPATH)

Thanks for the report!  I've prepared a fix, and plan to issue an upload
incorporating it (and getting closer to the latest upstream release)
this evening.

-- 
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

Bug#963465: ITP: node-natural-sort: Sorting with support for numbers, dates, unicode and more

[Nilesh Patra]

Package: wnpp
Severity: wishlist
Owner: Nilesh Patra 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-natural-sort
  Version : 1.0.0-1
  Upstream Author : Studio B12 GmbH
* URL : https://github.com/studio-b12/natural-sort

* License : Expat
  Programming Lang: Javascript
  Description : Sorting with support for numbers, dates, unicode and
more
 The package provides support for sorting
 dates, numbers, unicode, et. al.
 .
 This has the following features:
  *  Numbers are handled properly – “2” is before “10”
  *  Strings are after numbers
  *  Empty strings are after “z”
  *  “a” is before “B” (opt out via caseSensitive: true)
  *  Semver-compatible sorting of version numbers

I shall maintain this package.

Bug#963408: pmtools: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2

[gregor herrmann]

On Sun, 21 Jun 2020 22:11:05 +0200, Lucas Nussbaum wrote:

> > #   Failed test 'found Carp'
> > #   at t/pman.t line 20.
> > #   'pod2text: unable to format 
> > /usr/lib/x86_64-linux-gnu/perl-base/Carp.pm
> > # '
> > # doesn't match '(?^ms:NAME.*[Cc]arp - \w.*SYNOPSIS.*DESCRIPTION)'
> > # Looks like you failed 1 test of 2.
> > t/pman.t . 
> > 1..2
> > ok 1 - pman runs
> > not ok 2 - found Carp
> > Dubious, test returned 1 (wstat 256, 0x100)
> > Failed 1/2 subtests 

Interesting bug, and not found in cpantesters.

I note that /usr/lib/x86_64-linux-gnu/perl-base/Carp.pm (from
perl-base) indeed has no POD, but /usr/share/perl/5.30.3/Carp.pm
(from perl-modules-5.30) does. And bin/pman finds the first one.

I wonder why this pops up now? Can this be related to the recent
changes of @INC in src:perl?


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: U2: New York


signature.asc
Description: Digital Signature

Bug#963177: calendar: trying to overwrite '/etc/calendar/default', which is also in package bsdmainutils 12.1.1

[Josh Triplett]

On Sun, 21 Jun 2020 04:05:43 +0200 Chris Hofstaedtler  wrote:
> Hi Josh,
> 
> I figured you might be interested in this, too, as IIRC the original
> patch was from you:
> 
> * Thorsten Glaser  [200621 02:04]:
> > Selecting previously unselected package calendar.
> > (Reading database ... 406194 files and directories currently installed.)
> > Preparing to unpack .../calendar_12.1.1_x32.deb ...
> > Unpacking calendar (12.1.1) ...
> > dpkg: error processing archive 
> > /var/cache/apt/archives/calendar_12.1.1_x32.deb (--unpack):
> >  trying to overwrite '/etc/calendar/default', which is also in package 
> > bsdmainutils 12.1.1
> > dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> > Errors were encountered while processing:
> >  /var/cache/apt/archives/calendar_12.1.1_x32.deb
> > E: Sub-process /usr/bin/dpkg returned an error code (1)

Ah. When I originally sent the patch, I believe I included appropriate
Breaks/Replaces headers to make sure this wouldn't happen, but it looks
like the version that incorporated the patch had advanced past the
version numbers in the Breaks/Replaces. The version numbers in the
Breaks/Replaces need updating.

Bug#963420: [Pkg-zsh-devel] Bug#963420: zsh: FTBFS: sh: 1: colcrt: not found

[Axel Beckert]

Hi Lucas,

Lucas Nussbaum wrote:
> > helpfiles: attempting col -bx  > >debian/zsh-common/usr/share/zsh/help/col.tmp
> > sh: 1: col: not found
> > helpfiles: attempting colcrt - debian/zsh-common/usr/share/zsh/help/man.tmp 
> > >debian/zsh-common/usr/share/zsh/help/col.tmp
> > sh: 1: colcrt: not found
> > helpfiles: col -bx and colcrt - both failed
> > make[1]: *** [debian/rules:97: override_dh_auto_install-indep] Error 1

Thanks for that bug report!

This is very likely caused by moving around some binaries between
bsdmainutils and util-linux:

bsdmainutils (12.1.1) unstable; urgency=medium

  The "calendar" program, formerly provided in this package, now
  appears in the separate package "calendar".

  The tools The tools col, colrm, column, hexdump, and ul are now
  provided as "bsdextrautils" from the util-linux sources.

 -- Michael Meskes   Wed, 27 May 2020 17:05:02 +0200

And from the changelog of bsdmainutils (12.1.1):

  * Follow BSD and remove colcrt, it is only useful on very old
terminals anyway.

>From the message "col -bx and colcrt - both failed" and the fact that
col was testet before colcrt, I assume that it suffices to add a
build-dependency on bsdextrautils and as alternative a b-d on
bsdmainutils << 12.1.1~ to make sure at least col is installed.

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

Bug#963377: xterm: FTBFS: /bin/sh: 1: col: not found

[Thomas Dickey]

On Sun, Jun 21, 2020 at 10:13:41PM +0200, Lucas Nussbaum wrote:
> Source: xterm
> Version: 356-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200620 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

col's in bsdmainutils

> > GROFF_NO_SGR=stupid /bin/sh -c "tbl ../ctlseqs.ms | groff -Tascii -ms | col 
> > -bx" >../ctlseqs.txt
> > /bin/sh: 1: col: not found
> > make[2]: *** [Makefile:180: ../ctlseqs.txt] Error 127

refer to

xterm (332-1) unstable; urgency=medium

  * Regenerate ctlseqs.txt from ctlseqs.ms (Closes: #848818).   
- Add groff to Buils-Depends.

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature

Bug#963464: less message left on the screen after quitting with first file non-existent

[Tomáš Szaniszlo]

Package: less
Version: 551-1
Severity: minor

Hi,

it seems that the repainting/erasing of status messages of less is not working
when an error message appears in a specific situation.

Steps to reproduce:
- run `less does_not_exist /etc/hosts` where the `does_not_exist` doesn't exist
  and the second file exists (using `/etc/hosts` as a convenient example)
- press q

Less exists, but besides expected error message "does_not_exist: No such file
or directory" also the message "/etc/hosts  (press RETURN)" is left on the
screen (in inverted colours).

Similar commands `less does_not_exist`, `less /etc/hosts /etc/passwd` or
`less /etc/hosts does_not_exist` don't leave such leftovers on the screen.

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

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

Versions of packages less depends on:
ii  libc6  2.30-8
ii  libtinfo6  6.2-1

less recommends no packages.

less suggests no packages.

-- no debconf information

Bug#963442: pbuilder: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2

[Thorsten Glaser]

reassign 963442 man-db
affects 963442 src:pbuilder
retitle 963442 man-db: must adjust Depends for col(1)
thanks

Lucas Nussbaum dixit:

>> LANG=C MANWIDTH=80 man --warnings -l debuild-pbuilder.1 >/dev/null
>> man: can't execute col: No such file or directory

This is because col is now in:
 bsdextrautils | bsdmainutils (<< 12)

This needs to be fixed in man-db which got broken by the recent
bsdmainutils upload.

bye,
//mirabilos
-- 
22:20⎜ The crazy that persists in his craziness becomes a master
22:21⎜ And the distance between the craziness and geniality is
only measured by the success 18:35⎜ "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent

Bug#963463: RFS: ace/6.5.8+dfsg-2 -- makefile, project, and workspace creator

[Sudip Mukherjee]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: t...@debian.org

Dear mentors,

I am looking for a sponsor for my package "ace"

 * Package name: ace
   Version : 6.5.8+dfsg-2
   Upstream Author : Douglas C. Schmidt 
 * URL : https://www.dre.vanderbilt.edu/~schmidt/ACE.html
 * License :
 * Vcs : https://salsa.debian.org/debian/ace
   Section : devel

It builds those binary packages:

  mpc-ace - makefile, project, and workspace creator
  libace-6.5.8 - C++ network programming framework
  libace-dev - C++ network programming framework - development files
  libace-doc - C++ network programming framework - documentation
  libace-ssl-6.5.8 - ACE secure socket layer library
  libace-ssl-dev - ACE secure socket layer library - development files
  libace-rmcast-6.5.8 - ACE reliable multicast library
  libace-rmcast-dev - ACE reliable multicast library - development files
  libace-tmcast-6.5.8 - ACE transactional multicast library
  libace-tmcast-dev - ACE transactional multicast library - development files
  libace-htbp-6.5.8 - ACE protocol over HTTP tunneling library
  libace-htbp-dev - ACE protocol over HTTP tunneling library - development files
  libace-inet-6.5.8 - ACE Inet protocol library
  libace-inet-dev - ACE Inet protocol library - development files
  libace-inet-ssl-6.5.8 - ACE SSL-enabled Inet protocol library
  libace-inet-ssl-dev - ACE SSL-enabled Inet protocol library - development 
files
  ace-gperf - ACE perfect hash function generator
  libacexml-6.5.8 - ACE SAX based XML parsing library
  libacexml-dev - ACE SAX based XML parsing library - development files
  libace-xml-utils-6.5.8 - ACE XML utility classes and methods
  libace-xml-utils-dev - ACE XML utility classes and methods - development files
  libkokyu-6.5.8 - ACE scheduling and dispatching library
  libkokyu-dev - ACE scheduling and dispatching library - development files
  libace-xtreactor-6.5.8 - ACE-GUI reactor integration for Xt
  libace-xtreactor-dev - ACE-GUI reactor integration for Xt - development files
  libace-tkreactor-6.5.8 - ACE-GUI reactor integration for Tk
  libace-tkreactor-dev - ACE-GUI reactor integration for Tk - development files
  libace-flreactor-6.5.8 - ACE-GUI reactor integration for FLTK
  libace-flreactor-dev - ACE-GUI reactor integration for FLTK - development 
files
  libace-foxreactor-6.5.8 - ACE-GUI reactor integration for FOX
  libace-foxreactor-dev - ACE-GUI reactor integration for FOX - development 
files
  ace-netsvcs - ACE network service implementations
  libnetsvcs-6.5.8 - ACE network service implementations - libraries
  libnetsvcs-dev - ACE network service implementations - development files

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/ace

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/a/ace/ace_6.5.8+dfsg-2.dsc

Changes since the last upload:

   * Team upload.
   * Upload to unstable.

This is an upload to unstable to complete the transition. The ack for the
transition is at #963272.


-- 
Regards
Sudip

Bug#963017: linux-image-5.6.0-2-amd64: System freezes shortly after boot

[Ben Hutchings]

Control: tag -1 moreinfo

Is this reproducible when not using the Nvidia proprietary driver?

Ben.

-- 
Ben Hutchings
It is impossible to make anything foolproof
because fools are so ingenious.




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

Bug#963239: linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5)

[Ben Hutchings]

Control: tag -1 moreinfo

You need to explain what the bug is.  The subject says that a RAID
array was resynced at boot, but that's supposed to happen in some
circumstances.

* Why did you not expect it?
* Did you notice anything happen before, or did you make any change,
  that might have triggered this behaviour?
* Does this happen repeatedly?
  * If so, haved you tried anything to work around this, and did it
work?

Ben.

-- 
Ben Hutchings
It is impossible to make anything foolproof
because fools are so ingenious.




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

Bug#963336: filtlong: FTBFS: ModuleNotFoundError: No module named 'pkg_resources'

[Adrian Bunk]

Control: reassign -1 python3-markdown 3.2.2-1
Control: retitle -1 python3-markdown: missing dependency on 
python3-pkg-resources
Control: affects -1 src:filtlong

On Sun, Jun 21, 2020 at 10:04:46PM +0200, Lucas Nussbaum wrote:
>...
> > markdown_py -f README.html README.md
> > Traceback (most recent call last):
> >   File "/usr/bin/markdown_py", line 6, in 
> > from pkg_resources import load_entry_point
> > ModuleNotFoundError: No module named 'pkg_resources'
> > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1
>...

python-markdown (3.2.2-1) unstable; urgency=medium
...
  * Remove python3-packaging and python3-pkg-resources dependencies,
python-markdown now uses importlib.metadata from the standard library.
...
 -- Dmitry Shachnev   Tue, 19 May 2020 20:19:55 +0300


cu
Adrian

Bug#963460: simutrans-pak64: FTBFS: /bin/bash: /usr/lib/simutrans/makeobj: No such file or directory

[Lucas Nussbaum]

Source: simutrans-pak64
Version: 120.4.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> /usr/bin/make SVNREV=1974  all
> make[2]: Entering directory '/<>'
> ===> Grounds calculations
> ===> OUTSIDE with REVISION and grounds
> /bin/bash: svnversion: command not found
> /bin/bash: /usr/lib/simutrans/makeobj: No such file or directory
> make[2]: *** [Makefile:95: ground] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/simutrans-pak64_120.4.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963459: python-transitions: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

[Lucas Nussbaum]

Source: python-transitions
Version: 0.8.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-transitions
> dpkg-buildpackage: info: source version 0.8.1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Philipp Huebner 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
>   pybuild --clean --test-pytest -i python{version} -p 3.8
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8_transitions/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>   rm -rf .pybuild/
>   find . -name \*.pyc -exec rm {} \;
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>   rm -f debian/debhelper-build-stamp
>   rm -rf debian/.debhelper/
>   rm -f -- debian/python3-transitions.substvars debian/files
>   rm -fr -- debian/python3-transitions/ debian/tmp/
>   find .  \( \( \
>   \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
> .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o 
> -type f -a \
>   \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
>-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
>-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
>-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
>   \) -exec rm -f {} + \) -o \
>   \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
> \)
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-transitions using existing 
> ./python-transitions_0.8.1.orig.tar.gz
> dpkg-source: info: building python-transitions in 
> python-transitions_0.8.1-1.debian.tar.xz
> dpkg-source: info: building python-transitions in 
> python-transitions_0.8.1-1.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>   pybuild --configure --test-pytest -i python{version} -p 3.8
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build --test-pytest -i python{version} -p 3.8
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_transitions/build/transitions
> copying transitions/core.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions
> copying transitions/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions
> copying transitions/version.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions
> creating 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/diagrams_graphviz.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/diagrams_pygraphviz.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/locking.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/factory.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/nesting_legacy.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/diagrams.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/markup.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/asyncio.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/states.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/nesting.py -> 
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> running egg_info
> writing transitions.egg-info/PKG-INFO
> writing dependency_links to transitions.egg-info/dependency_links.txt
> writing requirements to transitions.egg-info/requires.txt
> writing top-level names to 

Bug#963341: cfengine3: New cfengine 3.15.2 package is broken and non-functional

[Antonio Radici]

On Sun, Jun 21, 2020 at 02:23:52PM -0600, Michael Berg wrote:
> 
> First, thank you for packaging cfengine 3.15.2.
> 
> Unfortunately, the new cfengine 3.15.2 package in sid/unstable is
> broken and non-functional.

Thanks for the report, I'll look into it tomorrow.

Bug#963461: ocsigenserver: FTBFS: ocamlfind invocation fails

[Lucas Nussbaum]

Source: ocsigenserver
Version: 2.16.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory 
> '/<>/src/extensions/ocsipersist-sqlite'
> ocamlfind ocamlc-g -bin-annot -thread -I ../../baselib -I ../../http -I 
> ../../server -package lwt -package lwt_log -package xml-light -package 
> sqlite3 -c ocsipersist.mli
> Usage: ocamlfind query[-help | other options]  ...
>or: ocamlfind ocamlc   [-help | other options]  ...
>or: ocamlfind ocamlcp  [-help | other options]  ...
>or: ocamlfind ocamlmklib   [-help | other options]  ...
>or: ocamlfind ocamlmktop   [-help | other options]  ...
>or: ocamlfind ocamlopt [-help | other options]  ...
>or: ocamlfind ocamloptp[-help | other options]  ...
>or: ocamlfind ocamldep [-help | other options]  ...
>or: ocamlfind ocamlbrowser [-help | other options]
>or: ocamlfind ocamldoc [-help | other options]  ...
>or: ocamlfind install  [-help | other options]   
> ...
>or: ocamlfind remove   [-help | other options] 
>or: ocamlfind printppx [-help | other options]  ...
>or: ocamlfind printconf[-help] [variable]
>or: ocamlfind lint [-help] 
>or: ocamlfind list
>or: ocamlfind pkg/cmd arg ...
> Select toolchain with:
>   ocamlfind -toolchain  
> Abbreviations:
>   e.g. ocamlfind opt instead of ocamlfind ocamlopt
> make[5]: *** [Makefile:44: ocsipersist.cmi] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/ocsigenserver_2.16.0-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!

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#963444: epubcheck: FTBFS: [ERROR] /<>/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java:[267,7]

[Lucas Nussbaum]

Source: epubcheck
Version: 4.2.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>   mh_patchpoms -pepubcheck --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   /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
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [WARNING] The project org.w3c:epubcheck:jar:4.2.2 uses prerequisites which is 
> only intended for maven-plugin projects but not for non maven-plugin 
> projects. For such purposes you should use the maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> [INFO] -< org.w3c:epubcheck 
> >--
> [INFO] Building EPUBCheck :: Validation Tool for EPUB 4.2.2
> [INFO] [ jar 
> ]-
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> epubcheck ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 5 resources to /<>/target
> [INFO] Copying 332 resources
> [INFO] Copying 1 resource
> [INFO] 
> [INFO] --- xml-maven-plugin:1.0.1:transform (default) @ epubcheck ---
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/collection-manifest-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/epub-xhtml-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/epub-svg-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/ocf-encryption-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/media-overlay-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/collection-do-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/ocf-metadata-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/package-30.sch
> [INFO] Transforming file: 
> /<>/src/main/resources/com/adobe/epubcheck/schema/30/epub-nav-30.sch
> [INFO] Transformed 9 file(s).
> [INFO] Transforming file: 
> /<>/target/generated-resources/intermediate-schema/collection-manifest-30.sch
> [INFO] Transforming file: 
> /<>/target/generated-resources/intermediate-schema/epub-xhtml-30.sch
> [INFO] Transforming file: 
> /<>/target/generated-resources/intermediate-schema/epub-svg-30.sch
> [INFO] Transforming file: 
> /<>/target/generated-resources/intermediate-schema/ocf-encryption-30.sch
> [INFO] Transforming file: 
> /<>/target/generated-resources/intermediate-schema/media-overlay-30.sch
> [INFO] Transforming file: 
> /<>/target/generated-resources/intermediate-schema/collection-do-30.sch
> [INFO] Transforming file: 
> /<>/target/generated-resources/intermediate-schema/ocf-metadata-30.sch
> [INFO] Transforming file: 
> /<>/target/generated-resources/intermediate-schema/package-30.sch
> [INFO] Transforming file: 
> /<>/target/generated-resources/intermediate-schema/epub-nav-30.sch
> [INFO] Transformed 9 file(s).
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ epubcheck 
> ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 221 source files to 

Bug#963456: ruby-rufus-scheduler: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(job.last_work_time).to be < 0.099

[Lucas Nussbaum]

Source: ruby-rufus-scheduler
Version: 3.4.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  Failure/Error: expect(job.last_work_time).to be < 0.099
> 
>expected: < 0.099
> got:   0.10010075569152832
>  # ./spec/job_spec.rb:634:in `block (4 levels) in '
> 
> Finished in 3 minutes 15.5 seconds (files took 0.24951 seconds to load)
> 353 examples, 1 failure, 2 pending
> 
> Failed examples:
> 
> rspec ./spec/job_spec.rb:622 # Rufus::Scheduler::Job work time 
> #mean_work_time gathers work times and computes the mean
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   
http://qa-logs.debian.net/2020/06/20/ruby-rufus-scheduler_3.4.2-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963449: liggghts: FTBFS: dh_installman: error: Could not determine section for ./debian/liggghts.1

[Lucas Nussbaum]

Source: liggghts
Version: 3.8.0+repack1-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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_installexamples
> find /<>/debian/ -name ".gitignore" | xargs rm -f
> make[1]: Leaving directory '/<>'
>dh_installman -O--buildsystem=cmake 
> -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
> dh_installman: warning: Section for ./debian/liggghts.1 is computed as 
> "2011-11-4", which is not a valid section
> dh_installman: error: Could not determine section for ./debian/liggghts.1
> dh_installman: error: Aborting due to earlier error
> make: *** [debian/rules:5: binary] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/liggghts_3.8.0+repack1-5_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963454: grml2usb: FTBFS: grml2usb:920:17: F523 '...'.format(...) has unused arguments at position(s): 0

[Lucas Nussbaum]

Source: grml2usb
Version: 0.18.2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> flake8 grml2usb
> grml2usb:920:17: F523 '...'.format(...) has unused arguments at position(s): 0
> grml2usb:1956:57: E741 ambiguous variable name 'l'
> make[2]: *** [Makefile:44: codecheck] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/grml2usb_0.18.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!

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#963453: openjdk-14: FTBFS: gmake[4]: *** No rule to make target '/<>/build/buildtools/langtools_tools_classes/_the.BUILD_TOOLS_LANGTOOLS.vardeps', needed by '/<>/build/bu

[Lucas Nussbaum]

Source: openjdk-14
Version: 14.0.1+7-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> for f in debian/*.in; do \
>   case "$f" in debian/control.in) continue; esac; \
>   f2=$(echo $f | sed 's/JB/openjdk-14/;s/\.in$//'); \
>   sed -e 's/@JRE@/openjdk-14-jre/g' \
>   -e 's/@JDK@/openjdk-14-jdk/g' \
>   -e 's/@vendor@/OpenJDK/g' \
>   -e 's/@RELEASE@/14/g' \
>   -e 's/@basename@/openjdk-14/g' \
>   -e 's,@TOP@,usr/lib/jvm,g' \
>   -e 's,@basedir@,usr/lib/jvm/java-14-openjdk-amd64,g' \
>   -e 's,@etcdir@,etc/java-14-openjdk,g' \
>   -e 's,@jdiralias@,java-1.14.0-openjdk-amd64,g' \
>   -e 's,@jdirname@,java-14-openjdk-amd64,g' \
>   -e 's/@srcname@//g' \
>   -e 's/@jvmarch@/amd64/g' \
>   -e 's/@tag@//g' \
>   -e 's/@priority@/1411/g' \
>   -e 's/@mantag@//g' \
>   -e 's/@multiarch@/x86_64-linux-gnu/g' \
>   -e 's/@jre_hl_tools@//g' \
>   -e 's/@jre_tools@//g' \
>   -e 's/@jdk_hl_tools@/jar jarsigner javac javadoc javap jcmd jdb 
> jdeprscan jdeps jimage jinfo jlink jmap jmod jps jrunscript jshell jstack 
> jstat jstatd rmic serialver jaotc jhsdb/g' \
>   -e 's/@jdk_tools@/jconsole/g' \
>   -e 's/@corba_tools@//g' \
>   -e 's,@j2se_lib@,,g' \
>   -e 's,@j2se_share@,,g' \
>   -e 's,@java_launcher@,/usr/bin/java,g' \
>   -e 's/@cjk_fonts@/fonts-ipafont-gothic, fonts-ipafont-mincho, 
> fonts-wqy-microhei | fonts-wqy-zenhei, fonts-indic,/g' \
> $f > $f2; \
> done
> make[1]: Leaving directory '/<>'
> mkdir -p stamps
> touch stamps/unpack
> == stamps/configure ==
> Build options: parallel=4, Processors: 4
> == stamps/configure ==
> cat /proc/meminfo |egrep '^(Mem|Swap)'
> MemTotal:   15954964 kB
> MemFree: 6572112 kB
> MemAvailable:   15222372 kB
> SwapCached:0 kB
> SwapTotal: 0 kB
> SwapFree:  0 kB
> == stamps/configure ==
> cat /etc/hosts
> 127.0.0.1 localhost
> ::1   localhost ip6-localhost ip6-loopback
> ff02::1   ip6-allnodes
> ff02::2   ip6-allrouters
> 
> == stamps/configure ==
> cat /etc/fstab
> # UNCONFIGURED FSTAB FOR BASE SYSTEM
> == stamps/configure ==
> cat /etc/mtab
> cat: /etc/mtab: No such file or directory
> make: [debian/rules:918: stamps/configure] Error 1 (ignored)
> == stamps/configure ==
> cat /proc/mounts
> /dev/nvme0n1p1 / ext4 rw,relatime,discard,errors=remount-ro,commit=86400 0 0
> proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
> sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
> devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 
> 0 0
> tmpfs /dev/shm tmpfs rw,relatime 0 0
> /dev/nvme0n1p1 /build ext4 rw,relatime,discard,errors=remount-ro,commit=86400 
> 0 0
> /dev/nvme0n1p1 /tmp ext4 rw,relatime,discard,errors=remount-ro,commit=86400 0 > 0
> == stamps/configure ==
> mkdir -p bin
> which autoconf
> /usr/bin/autoconf
> /bin/uname -a
> Linux ip-172-31-4-182 4.19.0-6-cloud-amd64 #1 SMP Debian 4.19.67-2+deb10u2 
> (2019-11-11) x86_64 GNU/Linux
> lsb_release -a
> No LSB modules are available.
> Distributor ID:   Debian
> Description:  Debian GNU/Linux bullseye/sid
> Release:  unstable
> Codename: sid
> cat /proc/sys/kernel/random/entropy_avail
> 3670
> mkdir -p stamps
> rm -rf build
> mkdir -p build
> cd build && MAKE_VERBOSE=y QUIETLY= LOG=info,cmdlines IGNORE_OLD_CONFIG=true 
> LIBFFI_LIBS=-lffi_pic bash ../configure \
>   --with-jvm-variants=server 
> --with-boot-jdk=/usr/lib/jvm/java-13-openjdk-amd64 
> --disable-precompiled-headers --with-jvm-features=zgc 
> --with-extra-cflags='-Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -fno-stack-protector -Wno-deprecated-declarations -Wdate-time 
> -D_FORTIFY_SOURCE=2' --with-extra-cxxflags='-Wdate-time -D_FORTIFY_SOURCE=2 
> -g -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -fno-stack-protector -Wno-deprecated-declarations 
> -Wno-deprecated-declarations' --with-extra-ldflags='-Xlinker -z -Xlinker 
> relro -Xlinker -Bsymbolic-functions' \
>   
> --with-jni-libpath=/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib
>  --disable-ccache --with-jtreg=/usr --with-vendor-name='Debian' 
> --with-vendor-url='https://tracker.debian.org/pkg/openjdk-14' 
> --with-vendor-bug-url='https://bugs.debian.org/src:openjdk-14' 
> --with-vendor-vm-bug-url='https://bugs.debian.org/src:openjdk-14' 
> --with-vendor-name='Debian' 
> --with-vendor-url='https://tracker.debian.org/openjdk-14' 
> --with-vendor-bug-url='https://bugs.debian.org/openjdk-14' 
> 

Bug#963448: wiki2beamer: FTBFS: man: can't execute col: No such file or directory

[Lucas Nussbaum]

Source: wiki2beamer
Version: 0.10.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh  build
>dh_update_autotools_config
>dh_autoreconf
>debian/rules execute_after_dh_auto_build
> make[1]: Entering directory '/<>'
> /usr/bin/make -C /<>/doc/man/
> make[2]: Entering directory '/<>/doc/man'
> mkdir man1
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{ 
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[2]: *** [Makefile:9: man] Error 3

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/wiki2beamer_0.10.0-1_unstable.log

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

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#963452: varnish-modules: FTBFS: dpkg-gencontrol: error: error occurred while parsing Depends field: libc6 (>= 2.14), libvarnishapi2 (>= 6.1.0),

[Lucas Nussbaum]

Source: varnish-modules
Version: 0.16.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> echo "Varnish:ABI=varnishabi-VRT_MAJOR_VERSION.VRT_MINOR_VERSION" > 
> debian/substvars
> dh_gencontrol -- -Tdebian/substvars
> dpkg-gencontrol: warning: can't parse dependency 
> varnishabi-VRT_MAJOR_VERSION.VRT_MINOR_VERSION
> dpkg-gencontrol: error: error occurred while parsing Depends field: libc6 (>= 
> 2.14), libvarnishapi2 (>= 6.1.0),
> ,
> varnishabi-VRT_MAJOR_VERSION.VRT_MINOR_VERSION
> dh_gencontrol: error: dpkg-gencontrol -pvarnish-modules -ldebian/changelog 
> -Tdebian/varnish-modules.substvars 
> -Pdebian/.debhelper/varnish-modules/dbgsym-root -Tdebian/substvars 
> -UPre-Depends -URecommends -USuggests -UEnhances -UProvides -UEssential 
> -UConflicts -DPriority=optional -UHomepage -UImportant -UBuilt-Using 
> -DAuto-Built-Package=debug-symbols -DPackage=varnish-modules-dbgsym 
> "-DDepends=varnish-modules (= \${binary:Version})" "-DDescription=debug 
> symbols for varnish-modules" 
> "-DBuild-Ids=1576cb810d5ffae1abe290e02de5ce81a78b2726 
> 2fe5bfcf1ef71319f76161cc7b33424805115b58 
> 315858dacfc3ea0022ce43627fdf1265599f757c 
> 373ded506e430089cb3203dcc10dba05aaf625b0 
> d327c8dbbe81355fc8669ed9cbcfc8420434a936 
> db4362ff603bd7ff7bfbe06b0f695f94f8312299 
> dc5f3a503b7e758a17882dab47bd351e8e15e19a" -DSection=debug -UMulti-Arch 
> -UReplaces -UBreaks returned exit code 25
> dh_gencontrol: error: Aborting due to earlier error
> make[1]: *** [debian/rules:32: override_dh_gencontrol] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/varnish-modules_0.16.0-1_unstable.log

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

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#963445: mediaconch: FTBFS: dh: error: Unknown sequence configure-Project/GNU/CLI/ (choose from: binary binary-arch binary-indep build build-arch build-indep clean install install-arch install-inde

[Lucas Nussbaum]

Source: mediaconch
Version: 18.03.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 configure-Project/GNU/CLI/ --with=autoreconf
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
> dh: error: Unknown sequence configure-Project/GNU/CLI/ (choose from: binary 
> binary-arch binary-indep build build-arch build-indep clean install 
> install-arch install-indep)
> make[1]: *** [debian/rules:21: configure-Project/GNU/CLI/] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/mediaconch_18.03.2-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963443: apache-curator: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project curator-framework: Compilation failure: Comp

[Lucas Nussbaum]

Source: apache-curator
Version: 2.7.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> # Regenerate the Java classes from the Thrift files
> sed -i 's/^namespace java.swift/\/\/namespace java.swift/g' 
> curator-x-rpc/src/main/thrift/curator.thrift
> cd curator-x-rpc/src/main/scripts && bash apply-thrift.sh java
> dh_auto_build
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   /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
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Apache Curator 
> [pom]
> [INFO] Curator Testing
> [jar]
> [INFO] Curator Client 
> [jar]
> [INFO] Curator Framework  
> [jar]
> [INFO] Curator Recipes
> [jar]
> [INFO] Curator Service Discovery   
> [bundle]
> [INFO] 
> [INFO] -< org.apache.curator:apache-curator 
> >--
> [INFO] Building Apache Curator 2.7.1  
> [1/6]
> [INFO] [ pom 
> ]-
> [WARNING] The artifact org.testng:testng:jar:6.x has been relocated to 
> org.testng:testng:jar:debian
> [INFO] 
> [INFO] --- maven-bundle-plugin:3.5.1:manifest (bundle-manifest) @ 
> apache-curator ---
> [WARNING] Ignoring project type pom - supportedProjectTypes = [jar, war, 
> bundle]
> [INFO] 
> [INFO] --< org.apache.curator:curator-test 
> >---
> [INFO] Building Curator Testing 2.7.1 
> [2/6]
> [INFO] [ jar 
> ]-
> [WARNING] The artifact javassist:javassist:jar:debian has been relocated to 
> org.javassist:javassist:jar:debian
> [WARNING] The artifact org.testng:testng:jar:6.x has been relocated to 
> org.testng:testng:jar:debian
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> curator-test ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources to META-INF
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ 
> curator-test ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 14 source files to 
> /<>/curator-test/target/classes
> [INFO] 
> [INFO] --- maven-bundle-plugin:3.5.1:manifest (bundle-manifest) @ 
> curator-test ---
> [WARNING] The artifact javassist:javassist:jar:debian has been relocated to 
> org.javassist:javassist:jar:debian
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ curator-test ---
> [INFO] Not copying test resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ 
> curator-test ---
> [INFO] Not compiling test sources
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @ curator-test ---
> [INFO] Tests are skipped.
> [INFO] 
> [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ curator-test ---
> [INFO] Building jar: 
> /<>/curator-test/target/curator-test-2.7.1.jar
> [INFO] 
> [INFO] -< org.apache.curator:curator-client 
> >--
> [INFO] Building Curator Client 2.7.1  
> [3/6]
> [INFO] [ jar 
> ]-
> [WARNING] The artifact 

Bug#963451: loadlin: FTBFS: /bin/sh: 1: hexdump: not found

[Lucas Nussbaum]

Source: loadlin
Version: 1.6f-7
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>/src/srclinux'
> gcc -m32 -traditional -c loadlinh.S
> gcc -m32 -D__KERNEL__ -march=i386 -Os -DSTDC_HEADERS -fomit-frame-pointer 
> -fno-strength-reduce -fPIC -ffreestanding -fno-stack-protector -c pgadjust.c 
> -o pgadjust.o
> ld -m elf_i386 -Ttext 0x95010 -N -e startup_32  -o pgadjust loadlinh.o 
> pgadjust.o
> objcopy -O binary pgadjust pgadjust.out
> echo "; 32-bit code, linkaddress: 0x95010" >pgadjust.as
> hexdump -v -e '" DD  " 8/4 "0%Xh," 1/4 "0%Xh\n"' pgadjust.out >>pgadjust.as
> /bin/sh: 1: hexdump: not found
> make[2]: *** [Makefile:19: ../pgadjust.asm] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/loadlin_1.6f-7_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963447: shellia: FTBFS: ERROR "./tests/test.prefix" -s "bash" / shortened difference between expectation and result:

[Lucas Nussbaum]

Source: shellia
Version: 5.6.2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> OK "./examples/test.hello_world" -s "bash"
> OK "./examples/test.hello_world" -s "dash"
> OK "./examples/test.hello_world" -s "busybox sh"
> OK "./examples/test.hello_world" -s "mksh"
> OK "./examples/test.hello_world" -s "posh"
> OK "./examples/test.hello_world_debug" -s "bash"
> OK "./examples/test.hello_world_debug" -s "dash"
> OK "./examples/test.hello_world_debug" -s "busybox sh"
> OK "./examples/test.hello_world_debug" -s "mksh"
> OK "./examples/test.hello_world_debug" -s "posh"
> OK "./examples/test.hello_world_error" -s "bash"
> OK "./examples/test.hello_world_error" -s "dash"
> OK "./examples/test.hello_world_error" -s "busybox sh"
> OK "./examples/test.hello_world_error" -s "mksh"
> OK "./examples/test.hello_world_error" -s "posh"
> OK "./examples/test.hello_world_fun" -s "bash"
> OK "./examples/test.hello_world_fun" -s "dash"
> OK "./examples/test.hello_world_fun" -s "busybox sh"
> OK "./examples/test.hello_world_fun" -s "mksh"
> OK "./examples/test.hello_world_fun" -s "posh"
> OK "./examples/test.hello_world_log" -s "bash"
> OK "./examples/test.hello_world_log" -s "dash"
> OK "./examples/test.hello_world_log" -s "busybox sh"
> OK "./examples/test.hello_world_log" -s "mksh"
> OK "./examples/test.hello_world_log" -s "posh"
> OK "./examples/test.hello_world_trace" -s "bash"
> OK "./examples/test.hello_world_trace" -s "dash"
> OK "./examples/test.hello_world_trace" -s "busybox sh"
> OK "./examples/test.hello_world_trace" -s "mksh"
> OK "./examples/test.hello_world_trace" -s "posh"
> OK "./tests/test.backslash" -s "bash"
> OK "./tests/test.backslash" -s "dash"
> OK "./tests/test.backslash" -s "busybox sh"
> OK "./tests/test.backslash" -s "mksh"
> OK "./tests/test.backslash" -s "posh"
> OK "./tests/test.backslash2" -s "bash"
> OK "./tests/test.backslash2" -s "dash"
> OK "./tests/test.backslash2" -s "busybox sh"
> OK "./tests/test.backslash2" -s "mksh"
> OK "./tests/test.backslash2" -s "posh"
> OK "./tests/test.block" -s "bash"
> OK "./tests/test.block" -s "dash"
> OK "./tests/test.block" -s "busybox sh"
> OK "./tests/test.block" -s "mksh"
> OK "./tests/test.block" -s "posh"
> OK "./tests/test.buffer" -s "bash"
> OK "./tests/test.buffer" -s "dash"
> OK "./tests/test.buffer" -s "busybox sh"
> OK "./tests/test.buffer" -s "mksh"
> OK "./tests/test.buffer" -s "posh"
> OK "./tests/test.col_regex" -s "bash"
> OK "./tests/test.col_regex" -s "dash"
> OK "./tests/test.col_regex" -s "busybox sh"
> OK "./tests/test.col_regex" -s "mksh"
> OK "./tests/test.col_regex" -s "posh"
> OK "./tests/test.debug" -s "bash"
> OK "./tests/test.debug" -s "dash"
> OK "./tests/test.debug" -s "busybox sh"
> OK "./tests/test.debug" -s "mksh"
> OK "./tests/test.debug" -s "posh"
> OK "./tests/test.debug_badlevel" -s "bash"
> OK "./tests/test.debug_badlevel" -s "dash"
> OK "./tests/test.debug_badlevel" -s "busybox sh"
> OK "./tests/test.debug_badlevel" -s "mksh"
> OK "./tests/test.debug_badlevel" -s "posh"
> OK "./tests/test.debug_env" -s "bash"
> OK "./tests/test.debug_env" -s "dash"
> OK "./tests/test.debug_env" -s "busybox sh"
> OK "./tests/test.debug_env" -s "mksh"
> OK "./tests/test.debug_env" -s "posh"
> OK "./tests/test.debug_iptables" -s "bash"
> OK "./tests/test.debug_iptables" -s "dash"
> OK "./tests/test.debug_iptables" -s "busybox sh"
> OK "./tests/test.debug_iptables" -s "mksh"
> OK "./tests/test.debug_iptables" -s "posh"
> OK "./tests/test.eval" -s "bash"
> OK "./tests/test.eval" -s "dash"
> OK "./tests/test.eval" -s "busybox sh"
> OK "./tests/test.eval" -s "mksh"
> OK "./tests/test.eval" -s "posh"
> OK "./tests/test.exit" -s "bash"
> OK "./tests/test.exit" -s "dash"
> OK "./tests/test.exit" -s "busybox sh"
> OK "./tests/test.exit" -s "mksh"
> OK "./tests/test.exit" -s "posh"
> OK "./tests/test.func" -s "bash"
> OK "./tests/test.func" -s "dash"
> OK "./tests/test.func" -s "busybox sh"
> OK "./tests/test.func" -s "mksh"
> OK "./tests/test.func" -s "posh"
> OK "./tests/test.ia-C-error" -s "bash"
> OK "./tests/test.ia-C-error" -s "dash"
> OK "./tests/test.ia-C-error" -s "busybox sh"
> OK "./tests/test.ia-C-error" -s "mksh"
> OK "./tests/test.ia-C-error" -s "posh"
> OK "./tests/test.ia-C-expr" -s "bash"
> OK "./tests/test.ia-C-expr" -s "dash"
> OK "./tests/test.ia-C-expr" -s "busybox sh"
> OK "./tests/test.ia-C-expr" -s "mksh"
> OK "./tests/test.ia-C-expr" -s "posh"
> OK "./tests/test.ia-c--learn" -s "bash"
> OK "./tests/test.ia-c--learn" -s "dash"
> OK "./tests/test.ia-c--learn" -s "busybox sh"
> OK "./tests/test.ia-c--learn" -s "mksh"
> OK "./tests/test.ia-c--learn" -s "posh"
> OK "./tests/test.ia-c-C" -s "bash"
> OK "./tests/test.ia-c-C" -s "dash"
> OK "./tests/test.ia-c-C" -s "busybox sh"
> OK "./tests/test.ia-c-C" -s "mksh"
> OK 

Bug#963455: containerd: FTBFS: src/github.com/containerd/containerd/vendor/k8s.io/apimachinery/pkg/apis/meta/v1/micro_time.go:23:2: cannot find package "github.com/google/gofuzz" in any of:

[Lucas Nussbaum]

Source: containerd
Version: 1.3.4~ds1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- -tags 'seccomp apparmor' -ldflags '-X 
> github.com/containerd/containerd/version.Version=1.3.4~ds1 -X 
> github.com/containerd/containerd/version.Revision=1.3.4~ds1-1'
>   cd _build && go generate -v -tags "seccomp apparmor" -ldflags "-X 
> github.com/containerd/containerd/version.Version=1.3.4~ds1 -X 
> github.com/containerd/containerd/version.Revision=1.3.4~ds1-1" 
> github.com/containerd/containerd github.com/containerd/containerd/api/events 
> github.com/containerd/containerd/api/services/containers/v1 
> github.com/containerd/containerd/api/services/content/v1 
> github.com/containerd/containerd/api/services/diff/v1 
> github.com/containerd/containerd/api/services/events/v1 
> github.com/containerd/containerd/api/services/images/v1 
> github.com/containerd/containerd/api/services/introspection/v1 
> github.com/containerd/containerd/api/services/leases/v1 
> github.com/containerd/containerd/api/services/namespaces/v1 
> github.com/containerd/containerd/api/services/snapshots/v1 
> github.com/containerd/containerd/api/services/tasks/v1 
> github.com/containerd/containerd/api/services/ttrpc/events/v1 
> github.com/containerd/containerd/api/services/version/v1 
> github.com/containerd/containerd/api/types 
> github.com/containerd/containerd/api/types/task 
> github.com/containerd/containerd/archive 
> github.com/containerd/containerd/archive/compression 
> github.com/containerd/containerd/archive/tartest 
> github.com/containerd/containerd/cio 
> github.com/containerd/containerd/cmd/containerd 
> github.com/containerd/containerd/cmd/containerd/command 
> github.com/containerd/containerd/cmd/containerd-shim 
> github.com/containerd/containerd/cmd/containerd-shim-runc-v1 
> github.com/containerd/containerd/cmd/containerd-shim-runc-v2 
> github.com/containerd/containerd/cmd/ctr 
> github.com/containerd/containerd/cmd/ctr/app 
> github.com/containerd/containerd/cmd/ctr/commands 
> github.com/containerd/containerd/cmd/ctr/commands/containers 
> github.com/containerd/containerd/cmd/ctr/commands/content 
> github.com/containerd/containerd/cmd/ctr/commands/events 
> github.com/containerd/containerd/cmd/ctr/commands/images 
> github.com/containerd/containerd/cmd/ctr/commands/install 
> github.com/containerd/containerd/cmd/ctr/commands/leases 
> github.com/containerd/containerd/cmd/ctr/commands/namespaces 
> github.com/containerd/containerd/cmd/ctr/commands/plugins 
> github.com/containerd/containerd/cmd/ctr/commands/pprof 
> github.com/containerd/containerd/cmd/ctr/commands/run 
> github.com/containerd/containerd/cmd/ctr/commands/shim 
> github.com/containerd/containerd/cmd/ctr/commands/snapshots 
> github.com/containerd/containerd/cmd/ctr/commands/tasks 
> github.com/containerd/containerd/cmd/ctr/commands/version 
> github.com/containerd/containerd/containers 
> github.com/containerd/containerd/content 
> github.com/containerd/containerd/content/local 
> github.com/containerd/containerd/content/proxy 
> github.com/containerd/containerd/content/testsuite 
> github.com/containerd/containerd/contrib/apparmor 
> github.com/containerd/containerd/contrib/nvidia 
> github.com/containerd/containerd/contrib/seccomp 
> github.com/containerd/containerd/contrib/snapshotservice 
> github.com/containerd/containerd/defaults 
> github.com/containerd/containerd/diff 
> github.com/containerd/containerd/diff/apply 
> github.com/containerd/containerd/diff/walking 
> github.com/containerd/containerd/diff/walking/plugin 
> github.com/containerd/containerd/errdefs 
> github.com/containerd/containerd/events 
> github.com/containerd/containerd/events/exchange 
> github.com/containerd/containerd/filters github.com/containerd/containerd/gc 
> github.com/containerd/containerd/gc/scheduler 
> github.com/containerd/containerd/identifiers 
> github.com/containerd/containerd/images 
> github.com/containerd/containerd/images/archive 
> github.com/containerd/containerd/labels 
> github.com/containerd/containerd/leases 
> github.com/containerd/containerd/leases/proxy 
> github.com/containerd/containerd/log 
> github.com/containerd/containerd/log/logtest 
> github.com/containerd/containerd/metadata 
> github.com/containerd/containerd/metadata/boltutil 
> github.com/containerd/containerd/metrics/cgroups 
> github.com/containerd/containerd/metrics/types/v1 
> github.com/containerd/containerd/mount 
> github.com/containerd/containerd/namespaces 
> github.com/containerd/containerd/oci 
> github.com/containerd/containerd/pkg/dialer 
> github.com/containerd/containerd/pkg/oom 
> github.com/containerd/containerd/pkg/process 
> github.com/containerd/containerd/pkg/progress 
> github.com/containerd/containerd/pkg/seed 
> 

Bug#963457: node-buffer-shims: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-buffer-shims
Version: 1.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-buffer-shims
> dpkg-buildpackage: info: source version 1.0.0-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Xavier Guimard 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with nodejs
>dh_auto_clean --buildsystem=nodejs
>   rm -rf ./node_modules/.cache
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-buffer-shims using existing 
> ./node-buffer-shims_1.0.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building node-buffer-shims in 
> node-buffer-shims_1.0.0-2.debian.tar.xz
> dpkg-source: info: building node-buffer-shims in node-buffer-shims_1.0.0-2.dsc
>  debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   /bin/sh -ex debian/tests/pkg-js/test
> + tape test/alloc.js test/save-unsafe.js
> b.length == 1024
> c.length == 512
> copied 512 bytes from b into c
> copied 512 bytes from c into b w/o sourceEnd
> copied 512 bytes from c into b w/o sourceStart
> copied 512 bytes from b into c w/o targetStart
> copied 256 bytes from end of b into beginning of c
> copied 512 bytes from b trying to overrun c
> copied 768 bytes from b into b
> bytes written to buffer: 11
> uber: 'über'
> f.length: 4 (should be 4)
> f.length: 8 (should be 8)
> f.length: 12 (should be 12)
> bytes written to buffer: 4 (should be 4)
> f.length: 8 (should be 8)
> f.length: 12 (should be 12)
> bytes written to buffer: 4 (should be 4)
> f.length: 8 (should be 8)
> f.length: 12 (should be 12)
> bytes written to buffer: 4 (should be 4)
> f.length: 8 (should be 8)
> f.length: 12 (should be 12)
> bytes written to buffer: 4 (should be 4)
> Create hex string from buffer
> Create buffer from hex string
> Try to slice off the end of the buffer
> 
> 
> 5
> 
> 9
> 
> 4
> 
> 9
> 
> 3
> 
> 2
> 
> 
> 
> 
> 
> 
> 
> 
> buffer.js:362
> throw new ERR_INVALID_OPT_VALUE.RangeError('size', size);
> ^
> 
> RangeError [ERR_INVALID_OPT_VALUE]: The value "NaN" is invalid for option 
> "size"
> at Function.allocUnsafe (buffer.js:384:3)
> at Object.allocUnsafe (/<>/index.js:41:19)
> at Object. (/<>/test/alloc.js:840:25)
> at Module._compile (internal/modules/cjs/loader.js:1138:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
> at Module.load (internal/modules/cjs/loader.js:986:32)
> at Function.Module._load (internal/modules/cjs/loader.js:879:14)
> at Module.require (internal/modules/cjs/loader.js:1026:19)
> at require (internal/modules/cjs/helpers.js:72:18)
> at /usr/lib/nodejs/tape/bin/tape:39:9 {
>   code: 'ERR_INVALID_OPT_VALUE'
> }
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/node-buffer-shims_1.0.0-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!

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#963446: cross-toolchain-base-ports: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2

[Lucas Nussbaum]

Source: cross-toolchain-base-ports
Version: 37
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> debian/kernelarch.make:5: *** empty variable name.  Stop.
> dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> exit status 2
> 
> Build finished at 2020-06-21T07:14:36Z

The full build log is available from:
   
http://qa-logs.debian.net/2020/06/20/cross-toolchain-base-ports_37_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963440: kafkacat: FTBFS: dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info

[Lucas Nussbaum]

Source: kafkacat
Version: 1.5.0-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- --enable-json --enable-avro --no-download
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>   ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-option-checking --disable-silent-rules 
> --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
> --disable-dependency-tracking --enable-json --enable-avro --no-download
> Unknown option disable-option-checking
> Usage: ./configure [OPTIONS...]
> 
>  mklove configure script - mklove, not autoconf
>  Copyright (c) 2014-2015 Magnus Edenhill - https://github.com/edenhill/mklove
> 
> Standard options:
>--prefix=PATHInstall arch-independent files in 
> PATH [/usr/local]
>--exec-prefix=PATH   Install arch-dependent files in PATH 
> [$prefix]
>--bindir=PATHUser executables [$exec_prefix/bin]
>--sbindir=PATH   System admin executables 
> [$exec_prefix/sbin]
>--libexecdir=PATHProgram executables 
> [$exec_prefix/libexec]
>--datadir=PATH   Read-only arch-independent data 
> [$prefix/share]
>--sysconfdir=PATHConfiguration data [$prefix/etc]
>--sharedstatedir=PATHModifiable arch-independent data 
> [$prefix/com]
>--localstatedir=PATH Modifiable local state data 
> [$prefix/var]
>--libdir=PATHLibraries [$exec_prefix/lib]
>--includedir=PATHC/C++ header files [$prefix/include]
>--infodir=PATH   Info documentation [$prefix/info]
>--mandir=PATHManual pages [$prefix/man]
> 
> Configure tool options:
>--list-modules   List loaded mklove modules
>--list-checksList checks
>--fail-fatal All failures are fatal
>--no-cache   Dont use or generate config.cache
>--debug  Enable configure debugging
>--clean  Remove generated configure files
>--reconfigureRerun configure with same arguments 
> as last run
>--no-downloadDisable downloads of required mklove 
> modules
>--update-modules Update modules from global repository
>--repo-url=URL_OR_PATH   Override mklove modules repo URL 
> [http://github.com/edenhill/mklove/raw/master]
>--help   Show configure usage
>--program-prefix=PFX Program prefix
> 
> Compatibility options:
>--enable-maintainer-mode Maintainer mode (no-op)
>--disable-maintainer-modeMaintainer mode (no-op)
>--disable-dependency-trackingDisable dependency tracking (no-op)
>--disable-silent-rules   Verbose build output (no-op)
> 
> Cross-compilation options:
>--host=HOST  Configure to build programs to run on 
> HOST (no-op)
>--build=BUILDConfigure for building on BUILD 
> (no-op)
>--target=TARGET  Configure for building cross-toolkits 
> for platform TARGET (no-op)
> 
> Compiler options:
>--cc=CC  Build using C compiler CC [$CC]
>--cxx=CXXBuild using C++ compiler CXX [$CXX]
>--arch=ARCH  Build for architecture [x86_64]
>--cpu=CPUBuild and optimize for specific CPU 
> [generic]
>--mbits=BITS Machine bits (32 or 64)
>--CFLAGS=CFLAGS  Add CFLAGS flags
>--CPPFLAGS=CPPFLAGS  Add CPPFLAGS flags
>--CXXFLAGS=CXXFLAGS  Add CXXFLAGS flags
>--LDFLAGS=LDFLAGSAdd LDFLAGS flags
>--ARFLAGS=ARFLAGSAdd ARFLAGS flags
>--pkg-config-path=EXTRA_PATHSExtra paths for pkg-config
>--enable-profiling   Enable profiling
>--enable-static  Enable static linking
>--disable-optimization   Disable optimization flag to compiler 
> [n]
>--disable-debug-symbols  Disable debugging symbols [n]
>--enable-werror  Enable compiler warnings as errors [n]
> 
> kafkacat options:
>--enable-json

Bug#963441: capstats: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2

[Lucas Nussbaum]

Source: capstats
Version: 0.28-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> debian/rules:7: *** missing separator.  Stop.
> dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> exit status 2
> 
> Build finished at 2020-06-21T07:28:29Z

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/capstats_0.28-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!

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#963439: ncbi-entrez-direct: FTBFS: obj-x86_64-linux-gnu/src/golang.org/x/sys/unix/syscall_unix.go:16:2: cannot find package "golang.org/x/sys/internal/unsafeheader" in any of:

[Lucas Nussbaum]

Source: ncbi-entrez-direct
Version: 12.0.20190816+ds-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' edirect.pl > bin/edirect
> chmod +x bin/edirect
> echo '#!/bin/sh' > bin/eaddress
> echo 'exec /usr/bin/edirect -address "$@"' >> bin/eaddress
> chmod +x bin/eaddress
> echo '#!/bin/sh' > bin/eblast
> echo 'exec /usr/bin/edirect -blast "$@"' >> bin/eblast
> chmod +x bin/eblast
> echo '#!/bin/sh' > bin/ecitmatch
> echo 'exec /usr/bin/edirect -citmatch "$@"' >> bin/ecitmatch
> chmod +x bin/ecitmatch
> echo '#!/bin/sh' > bin/econtact
> echo 'exec /usr/bin/edirect -contact "$@"' >> bin/econtact
> chmod +x bin/econtact
> echo '#!/bin/sh' > bin/efilter
> echo 'exec /usr/bin/edirect -filter "$@"' >> bin/efilter
> chmod +x bin/efilter
> echo '#!/bin/sh' > bin/elink
> echo 'exec /usr/bin/edirect -link "$@"' >> bin/elink
> chmod +x bin/elink
> echo '#!/bin/sh' > bin/enotify
> echo 'exec /usr/bin/edirect -notify "$@"' >> bin/enotify
> chmod +x bin/enotify
> echo '#!/bin/sh' > bin/epost
> echo 'exec /usr/bin/edirect -post "$@"' >> bin/epost
> chmod +x bin/epost
> echo '#!/bin/sh' > bin/eproxy
> echo 'exec /usr/bin/edirect -proxy "$@"' >> bin/eproxy
> chmod +x bin/eproxy
> echo '#!/bin/sh' > bin/esearch
> echo 'exec /usr/bin/edirect -search "$@"' >> bin/esearch
> chmod +x bin/esearch
> echo '#!/bin/sh' > bin/espell
> echo 'exec /usr/bin/edirect -spell "$@"' >> bin/espell
> chmod +x bin/espell
> echo '#!/bin/sh' > bin/esummary
> echo 'exec /usr/bin/edirect -fetch -format docsum "$@"' >> bin/esummary
> chmod +x bin/esummary
> mkdir -p bin
> sed -e 's/`has-asp`/false # &/' download-ncbi-data > bin/download-ncbi-data
> chmod +x bin/download-ncbi-data
> mkdir -p bin
> sed -e 's/`has-asp`/false # &/' download-pubmed > bin/download-pubmed
> chmod +x bin/download-pubmed
> mkdir -p bin
> sed -e 's/`has-asp`/false # &/' download-sequence > bin/download-sequence
> chmod +x bin/download-sequence
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' edirutil > bin/edirutil
> chmod +x bin/edirutil
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' ftp-cp > bin/ftp-cp
> chmod +x bin/ftp-cp
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' ftp-ls > bin/ftp-ls
> chmod +x bin/ftp-ls
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' gbf2xml > bin/gbf2xml
> chmod +x bin/gbf2xml
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' nquire > bin/nquire
> chmod +x bin/nquire
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' run-ncbi-converter > 
> bin/run-ncbi-converter
> chmod +x bin/run-ncbi-converter
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' transmute > bin/transmute
> chmod +x bin/transmute
> mkdir -p /<>/obj-x86_64-linux-gnu/src/github.com/fatih/
> ln -s /usr/share/gocode/src/github.com/fatih/color 
> /<>/obj-x86_64-linux-gnu/src/github.com/fatih/color
> mkdir -p /<>/obj-x86_64-linux-gnu/src/github.com/gedex/
> ln -s /usr/share/gocode/src/github.com/gedex/inflector 
> /<>/obj-x86_64-linux-gnu/src/github.com/gedex/inflector
> mkdir -p /<>/obj-x86_64-linux-gnu/src/github.com/klauspost/
> ln -s /usr/share/gocode/src/github.com/klauspost/cpuid 
> /<>/obj-x86_64-linux-gnu/src/github.com/klauspost/cpuid
> mkdir -p /<>/obj-x86_64-linux-gnu/src/github.com/mattn/
> ln -s /usr/share/gocode/src/github.com/mattn/go-colorable 
> /<>/obj-x86_64-linux-gnu/src/github.com/mattn/go-colorable
> mkdir -p /<>/obj-x86_64-linux-gnu/src/github.com/mattn/
> ln -s /usr/share/gocode/src/github.com/mattn/go-isatty 
> /<>/obj-x86_64-linux-gnu/src/github.com/mattn/go-isatty
> mkdir -p /<>/obj-x86_64-linux-gnu/src/github.com/pbnjay/
> ln -s /<>/debian/vendor/github.com/pbnjay/memory 
> /<>/obj-x86_64-linux-gnu/src/github.com/pbnjay/memory
> mkdir -p /<>/obj-x86_64-linux-gnu/src/github.com/rainycape/
> ln -s /usr/share/gocode/src/github.com/rainycape/unidecode 
> /<>/obj-x86_64-linux-gnu/src/github.com/rainycape/unidecode
> mkdir -p /<>/obj-x86_64-linux-gnu/src/github.com/shirou/
> ln -s /usr/share/gocode/src/github.com/shirou/gopsutil 
> /<>/obj-x86_64-linux-gnu/src/github.com/shirou/gopsutil
> mkdir -p /<>/obj-x86_64-linux-gnu/src/github.com/surgebase/
> ln -s /usr/share/gocode/src/github.com/surgebase/porter2 
> /<>/obj-x86_64-linux-gnu/src/github.com/surgebase/porter2
> mkdir -p /<>/obj-x86_64-linux-gnu/src/golang.org/x/sys/
> ln -s /usr/share/gocode/src/golang.org/x/sys/unix 
> /<>/obj-x86_64-linux-gnu/src/golang.org/x/sys/unix
> mkdir -p /<>/obj-x86_64-linux-gnu/src/golang.org/x/
> ln -s /usr/share/gocode/src/golang.org/x/text 
> /<>/obj-x86_64-linux-gnu/src/golang.org/x/text
> mkdir -p /<>/obj-x86_64-linux-gnu/src/github.com/fiam
> ln -s ../rainycape 
> 

Bug#963436: node-character-parser: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-character-parser
Version: 3.1.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> tsc
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../debian/tests/test_modules/wtfnode node_modules/wtfnode
>   ln -s ../debian/tests/test_modules/is-browser node_modules/is-browser
>   ln -s ../debian/tests/test_modules/test-result node_modules/test-result
>   ln -s ../debian/tests/test_modules/testit node_modules/testit
>   /bin/sh -ex debian/tests/pkg-js/test
> + NODE_PATH=debian/tests/test_modules/ node test/index.js
> internal/bootstrap/loaders.js:116
> throw new Error(`No such module: ${module}`);
> ^
> 
> Error: No such module: timer_wrap
> at process.binding (internal/bootstrap/loaders.js:116:11)
> at /<>/debian/tests/test_modules/wtfnode/index.js:258:21
> at Object. 
> (/<>/debian/tests/test_modules/wtfnode/index.js:299:3)
> at Module._compile (internal/modules/cjs/loader.js:1138:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
> at Module.load (internal/modules/cjs/loader.js:986:32)
> at Function.Module._load (internal/modules/cjs/loader.js:879:14)
> at Module.require (internal/modules/cjs/loader.js:1026:19)
> at require (internal/modules/cjs/helpers.js:72:18)
> at Object. 
> (/<>/debian/tests/test_modules/testit/index.js:6:20)
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/06/20/node-character-parser_3.1.0-1_unstable.log

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

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#963442: pbuilder: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2

[Lucas Nussbaum]

Source: pbuilder
Version: 0.230.4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> # syntax check.
> bash -n bash_completion.d/pbuilder
> bash -n pbuilderrc
> bash -n pbuilderrc
> bash -n debuild-pbuilder
> bash -n pdebuild
> bash -n pbuilder-apt-config
> bash -n pbuilder-buildpackage
> bash -n pbuilder-buildpackage-funcs
> bash -n pbuilder-checkparams
> bash -n pbuilder-createbuildenv
> bash -n pbuilder-loadconfig
> bash -n pbuilder-modules
> bash -n pbuilder-runhooks
> bash -n pbuilder-satisfydepends-apt
> bash -n pbuilder-satisfydepends-aptitude
> bash -n pbuilder-satisfydepends-checkparams
> bash -n pbuilder-satisfydepends-classic
> bash -n pbuilder-satisfydepends-experimental
> bash -n pbuilder-satisfydepends-funcs
> bash -n pbuilder-satisfydepends-gdebi
> bash -n pbuilder-unshare-wrapper
> bash -n pbuilder-updatebuildenv
> bash -n pdebuild-checkparams
> bash -n pdebuild-internal
> bash -n pbuilder
> bash -n examples/B90lintian
> bash -n examples/B91dpkg-i
> bash -n examples/B92test-pkg
> bash -n examples/C10shell
> bash -n examples/C11screen
> bash -n examples/D10tmp
> bash -n examples/D20addnonfree
> bash -n examples/D65various-compiler-support
> bash -n examples/D80no-man-db-rebuild
> bash -n examples/D90chrootmemo
> bash -n examples/F90chrootmemo
> bash -n examples/B90list-missing
> bash -n examples/B91debc
> bash -n examples/B20autopkgtest
> bash -n examples/execute_installtest.sh
> bash -n examples/execute_paramtest.sh
> bash -n examples/pbuilder-distribution.sh
> bash -n examples/lvmpbuilder/lvmbuilder
> bash -n examples/lvmpbuilder/lib/lvmbuilder-checkparams
> bash -n examples/lvmpbuilder/lib/lvmbuilder-modules
> bash -n examples/lvmpbuilder/lib/lvmbuilder-unimplemented
> bash -n examples/pbuilder-test/000_prepinstall
> bash -n examples/pbuilder-test/001_apprun
> bash -n examples/pbuilder-test/002_libfile
> bash -n examples/pbuilder-test/003_makecheck
> bash -n examples/pbuilder-test/004_ldd
> bash -n examples/rebuild/buildall
> bash -n examples/rebuild/getlist
> LANG=C MANWIDTH=80 man --warnings -l debuild-pbuilder.1 >/dev/null
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{ 
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[1]: *** [Makefile:163: check] Error 3
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/pbuilder_0.230.4_unstable.log

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

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#963435: cdk: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project cdk-isomorphism: Compilation failure: Compilation failu

[Lucas Nussbaum]

Source: cdk
Version: 1:2.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibcdk-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>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
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [WARNING] The project org.openscience.cdk:cdk:pom:2.3 uses prerequisites 
> which is only intended for maven-plugin projects but not for non maven-plugin 
> projects. For such purposes you should use the maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] cdk
> [pom]
> [INFO] cdk-base   
> [pom]
> [INFO] cdk-interfaces 
> [jar]
> [INFO] cdk-core   
> [jar]
> [INFO] cdk-standard   
> [jar]
> [INFO] cdk-atomtype   
> [jar]
> [INFO] cdk-valencycheck   
> [jar]
> [INFO] cdk-misc   
> [pom]
> [INFO] cdk-diff   
> [jar]
> [INFO] cdk-data   
> [jar]
> [INFO] cdk-silent 
> [jar]
> [INFO] cdk-datadebug  
> [jar]
> [INFO] cdk-isomorphism
> [jar]
> [INFO] cdk-dict   
> [jar]
> [INFO] cdk-storage
> [pom]
> [INFO] cdk-ioformats  
> [jar]
> [INFO] cdk-ctab   
> [jar]
> [INFO] cdk-io 
> [jar]
> [INFO] cdk-tool   
> [pom]
> [INFO] cdk-formula
> [jar]
> [INFO] cdk-pdb
> [jar]
> [INFO] cdk-libiocml   
> [jar]
> [INFO] cdk-smiles 
> [jar]
> [INFO] cdk-extra  
> [jar]
> [INFO] cdk-reaction   
> [jar]
> [INFO] cdk-smarts 
> [jar]
> [INFO] cdk-descriptor 
> [pom]
> [INFO] cdk-fingerprint
> [jar]
> [INFO] cdk-cip
> [jar]
> [INFO] cdk-signature  
> [jar]
> [INFO] cdk-charges
> [jar]
> [INFO] cdk-forcefield 
> [jar]
> [INFO] cdk-sdg
> [jar]
> [INFO] cdk-builder3dtools 
> [jar]
> [INFO] 

Bug#963432: muon: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/v

[Lucas Nussbaum]

Source: muon
Version: 4:5.8.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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_testdir  
> dh_auto_configure '--buildsystem=kf5' --parallel  
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON ..
> -- The C compiler identification is GNU 9.3.0
> -- The CXX compiler identification is GNU 9.3.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Could not set up the appstream test. appstreamcli is missing.
> -- Looking for __GLIBC__
> -- Looking for __GLIBC__ - found
> -- Performing Test _OFFT_IS_64BIT
> -- Performing Test _OFFT_IS_64BIT - Success
> -- Performing Test HAVE_DATE_TIME
> -- Performing Test HAVE_DATE_TIME - Success
> -- Found KF5KIO: /usr/lib/x86_64-linux-gnu/cmake/KF5KIO/KF5KIOConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5DBusAddons: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5DBusAddons/KF5DBusAddonsConfig.cmake 
> (found version "5.70.0") 
> -- Found Gettext: /usr/bin/msgmerge (found version "0.19.8.1") 
> -- Found KF5I18n: /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5IconThemes: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5IconThemes/KF5IconThemesConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5XmlGui: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5XmlGui/KF5XmlGuiConfig.cmake (found 
> version "5.70.0") 
> -- Found KF5: success (found version "5.70.0") found components: KIO 
> DBusAddons I18n IconThemes XmlGui 
> CMake Error at 
> /usr/share/cmake-3.16/Modules/CMakeFindDependencyMacro.cmake:47 
> (find_package):
>   By not providing "FindKF5TextWidgets.cmake" in CMAKE_MODULE_PATH this
>   project has asked CMake to find a package configuration file provided by
>   "KF5TextWidgets", but CMake did not find one.
> 
>   Could not find a package configuration file provided by "KF5TextWidgets"
>   with any of the following names:
> 
> KF5TextWidgetsConfig.cmake
> kf5textwidgets-config.cmake
> 
>   Add the installation prefix of "KF5TextWidgets" to CMAKE_PREFIX_PATH or set
>   "KF5TextWidgets_DIR" to a directory containing one of the above files.  If
>   "KF5TextWidgets" provides a separate development package or SDK, be sure it
>   has been installed.
> Call Stack (most recent call first):
>   /usr/lib/x86_64-linux-gnu/cmake/DebconfKDE/DebconfKDEConfig.cmake:100 
> (find_dependency)
>   CMakeLists.txt:22 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //Path to a program.
> APPSTREAMCLI:FILEPATH=APPSTREAMCLI-NOTFOUND
> 
> //Build the project with gcov support
> BUILD_COVERAGE:BOOL=OFF
> 
> //If enabled, shared libs will be built by default, otherwise static
> // libs
> BUILD_SHARED_LIBS:BOOL=TRUE
> 
> //Build the testing tree.
> BUILD_TESTING:BOOL=ON
> 
> //Path to a program.
> CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line
> 
> //Path to a program.
> CMAKE_AR:FILEPATH=/usr/bin/ar
> 
> //Choose the type of build, options are: None Debug Release RelWithDebInfo
> // MinSizeRel ...
> CMAKE_BUILD_TYPE:STRING=Debian
> 
> //Enable/Disable color output during build.
> CMAKE_COLOR_MAKEFILE:BOOL=ON
> 
> //CXX compiler
> 

Bug#963433: libcolor-calc-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 2

[Lucas Nussbaum]

Source: libcolor-calc-perl
Version: 1.074-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
> dh: warning: Compatibility levels before 10 are deprecated (level 8 in use)
>dh_update_autotools_config
>dh_auto_configure
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 8 in use)
>   perl -I. Build.PL --installdirs vendor
> Checking prerequisites...
>   requires:
> !  Graphics::ColorNames::HTML is not installed
> 
> Checking optional features...
> color_object_supportdisabled
>   requires:
> ! Color::Object is not installed
> 
> ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the versions
> of the modules indicated above before proceeding with this installation
> 
> Run 'Build installdeps' to install missing prerequisites.
> 
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'Color-Calc' version '1.074'
>dh_auto_build
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 8 in use)
>   perl Build
> Building Color-Calc
>dh_auto_test
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 8 
> in use)
>   perl Build test --verbose 1
> 
> #   Failed test 'use Color::Calc;'
> #   at t/00basic.t line 4.
> # Tried to use 'Color::Calc'.
> # Error:  Can't locate Graphics/ColorNames/HTML.pm in @INC (you may need 
> to install the Graphics::ColorNames::HTML module) (@INC contains: 
> /<>/blib/lib /<>/blib/arch . /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 
> /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 
> /usr/share/perl/5.30 /usr/local/lib/site_perl .) at 
> /<>/blib/lib/Color/Calc.pm line 17.
> # BEGIN failed--compilation aborted at 
> /<>/blib/lib/Color/Calc.pm line 17.
> # Compilation failed in require at t/00basic.t line 4.
> # BEGIN failed--compilation aborted at t/00basic.t line 4.
> Can't locate object method "new" via package "Color::Calc" at t/00basic.t 
> line 6.
> # Looks like your test exited with 255 just after 2.
> t/00basic.t  
> 1..3
> not ok 1 - use Color::Calc;
> ok 2 - no warnings
> Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 2/3 subtests 
> t/10pod.t .. 
> 1..3
> ok 1 - POD test for blib/lib/Color/Calc.pm
> ok 2 - POD test for blib/lib/Color/Calc/ConfigData.pm
> ok 3 - POD test for blib/lib/Color/Calc/WWW.pm
> ok
> 
> #   Failed test 'Color::Calc is covered by POD'
> #   at t/11pod_cover.t line 9.
> # Color::Calc: requiring 'Color::Calc' failed
> 
> #   Failed test 'Color::Calc::WWW is covered by POD'
> #   at t/11pod_cover.t line 13.
> # Color::Calc::WWW: requiring 'Color::Calc::WWW' failed
> # Looks like you failed 2 tests of 2.
> t/11pod_cover.t  
> 1..2
> not ok 1 - Color::Calc is covered by POD
> not ok 2 - Color::Calc::WWW is covered by POD
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 2/2 subtests 
> Can't locate Graphics/ColorNames/HTML.pm in @INC (you may need to install the 
> Graphics::ColorNames::HTML module) (@INC contains: /<>/blib/lib 
> /<>/blib/arch . /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 
> /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 
> /usr/share/perl/5.30 /usr/local/lib/site_perl .) at 
> /<>/blib/lib/Color/Calc.pm line 17.
> BEGIN failed--compilation aborted at /<>/blib/lib/Color/Calc.pm 
> line 17.
> Compilation failed in require at t/DEPRECATED_import_MODEval.t line 3.
> BEGIN failed--compilation aborted at t/DEPRECATED_import_MODEval.t line 3.
> # Looks like your test exited with 2 just after 1.
> t/DEPRECATED_import_MODEval.t .. 
> 1..53
> ok 1 - no warnings
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 52/53 subtests 
> Can't locate Graphics/ColorNames/HTML.pm in @INC (you may need to install the 
> Graphics::ColorNames::HTML module) (@INC contains: /<>/blib/lib 
> /<>/blib/arch . /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 
> /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 
> /usr/share/perl/5.30 /usr/local/lib/site_perl .) at 
> /<>/blib/lib/Color/Calc.pm line 17.
> BEGIN failed--compilation aborted at /<>/blib/lib/Color/Calc.pm 
> line 17.
> Compilation failed in require at t/DEPRECATED_import_suffix.t line 3.
> BEGIN failed--compilation aborted at t/DEPRECATED_import_suffix.t line 3.
> # Looks like your test exited with 2 just after 1.
> t/DEPRECATED_import_suffix.t ... 
> 1..53
> ok 1 - no warnings
> 

Bug#963438: ccdproc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

[Lucas Nussbaum]

Source: ccdproc
Version: 2.1.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> for t in .pybuild/*/build ; do \
>   cp -av ccdproc/tests/data/ ${t}/ccdproc/tests/ ; \
> done
> 'ccdproc/tests/data/' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data'
> 'ccdproc/tests/data/README.rst' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/README.rst'
> 'ccdproc/tests/data/a8280271.fits' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/a8280271.fits'
> 'ccdproc/tests/data/expected_ifc_file_properties.csv' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/expected_ifc_file_properties.csv'
> 'ccdproc/tests/data/flat-mef.fits' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/flat-mef.fits'
> 'ccdproc/tests/data/science-mef.fits' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/science-mef.fits'
> 'ccdproc/tests/data/sip-wcs.fit' -> 
> '.pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/data/sip-wcs.fit'
> dh_auto_test
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.8_ccdproc/build; 
> python3.8 -m pytest 
> = test session starts 
> ==
> platform linux -- Python 3.8.3, pytest-4.6.11, py-1.8.1, pluggy-0.13.0
> rootdir: /<>, inifile: setup.cfg
> plugins: openfiles-0.5.0, astropy-header-0.1.2, arraydiff-0.3, 
> hypothesis-5.16.0, remotedata-0.3.2, doctestplus-0.7.0
> collected 305 items / 1 errors / 304 selected
> 
>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.8_ccdproc/build/ccdproc/tests/run_for_memory_profile.py _
> ccdproc/tests/run_for_memory_profile.py:8: in 
> from memory_profiler import memory_usage
> E   ModuleNotFoundError: No module named 'memory_profiler'
> === warnings summary 
> ===
> ccdproc/extern/bitfield.py:251
>   
> /<>/.pybuild/cpython3_3.8_ccdproc/build/ccdproc/extern/bitfield.py:251:
>  DeprecationWarning: invalid escape sequence \_
> """
> 
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
> ccdproc/log_meta.py:66
>   
> /<>/.pybuild/cpython3_3.8_ccdproc/build/ccdproc/log_meta.py:66: 
> DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use 
> inspect.signature() or inspect.getfullargspec()
> (original_args, varargs, keywords, defaults) = inspect.getargspec(func)
> 
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
> ccdproc/log_meta.py:82
>   
> /<>/.pybuild/cpython3_3.8_ccdproc/build/ccdproc/log_meta.py:82: 
> DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use 
> `signature` and the `Signature` object directly
> signature_with_arg_added = inspect.formatargspec(original_args, varargs,
> 
> -- Docs: https://docs.pytest.org/en/latest/warnings.html
> !!! Interrupted: 1 errors during collection 
> 
> = 21 warnings, 1 error in 0.81 seconds 
> =
> E: pybuild pybuild:352: test: plugin distutils failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.8_ccdproc/build; python3.8 -m pytest 
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 
> returned exit code 13

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/ccdproc_2.1.0-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!

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#963434: freeboard: FTBFS: dpkg-query: no path found matching pattern /usr/share/javascript/jquery/jquery.js

[Lucas Nussbaum]

Source: freeboard
Version: 1.1.0+dfsg.1-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary --with linktree,apache2
>dh_testroot
>dh_prep
>dh_installdirs
>dh_install
>dh_apache2
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_linktree
> dpkg-query: no path found matching pattern 
> /usr/share/javascript/jquery/jquery.js
> dh_linktree: error: dpkg --search -- 
> /usr/share/javascript/caret.js/jquery.caret.js 
> /usr/share/javascript/codemirror/codemirror.css 
> /usr/share/javascript/codemirror/codemirror.js 
> /usr/share/javascript/codemirror/theme/ambiance.css 
> /usr/share/javascript/headjs/head.js 
> /usr/share/javascript/jquery-ui/jquery-ui.js 
> /usr/share/javascript/jquery.sparkline/jquery.sparkline.min.js 
> /usr/share/javascript/jquery/jquery.js 
> /usr/share/javascript/raphael/raphael.min.js 
> /usr/share/javascript/underscore/underscore.js 
> /usr/share/nodejs/knockout/build/output/knockout-latest.js subprocess 
> returned exit status 1
> make: *** [debian/rules:8: binary] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/freeboard_1.1.0+dfsg.1-4_unstable.log

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

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#963417: gem: FTBFS: /bin/sh: 4: -find: not found

[Lucas Nussbaum]

Source: gem
Version: 1:0.94-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> find src/Output/ -name "*.cpp" -exec \
>   ./debian/scripts/gemdefaultwindow.sh 
> abstractions/gemdefaultwindow.pd.in  {} +
> find debian/tmp/ -name gemdefaultwindow.pd -delete
> dh_install
> # remove libtool files, they are not needed
> find debian/gem-extra/usr/lib/ -name '*.la'  -delete
> # remove some assets
> find debian/gem-doc/usr/share/ -name '*.ttf' -delete; \
> -find debian/gem-doc/usr/share/ -name '*.avi' -delete; \
> -find debian/gem-doc/usr/share/ -name '*.mov' -delete; \
> -find debian/gem-doc/usr/share/ -name '*.mpg' -delete; \
> # the following COPYING only contains license information for vera.ttf
> /bin/sh: 2: -find: not found
> /bin/sh: 3: -find: not found
> /bin/sh: 4: -find: not found
> make[1]: [debian/rules:108: override_dh_install] Error 127 (ignored)
> # which is not included in the Debian package
> rm debian/gem-doc/usr/share/gem/examples/data/COPYING.txt
> # remove extra LICENSE files for gem-extra
> rm -f debian/gem-extra/usr/lib/pd/extra/pix_mano/LICENSE.txt
> rm -f debian/gem-extra/usr/lib/pd/extra/pix_drum/LICENSE.txt
> make[1]: Leaving directory '/<>'
>dh_installdocs
>dh_installchangelogs
>dh_installman
>dh_installmenu
>dh_installalternatives
> dh_installalternatives: error: syntax error in debian/alternatives at line 2: 
> line with unknown format (not field-colon-value)
> make: *** [debian/rules:89: binary] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/gem_0.94-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963416: liboping: FTBFS: dpkg-gencontrol: error: unknown option '-v'

[Lucas Nussbaum]

Source: liboping
Version: 1.10.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> /bin/sh: 1: Bad substitution
> dh_gencontrol -Nlibnet-oping-perl
> dh_gencontrol -plibnet-oping-perl -- -v
> dpkg-gencontrol: error: unknown option '-v'
> 
> Use --help for program usage information.
> dh_gencontrol: error: dpkg-gencontrol -plibnet-oping-perl -ldebian/changelog 
> -Tdebian/libnet-oping-perl.substvars 
> -Pdebian/.debhelper/libnet-oping-perl/dbgsym-root -v -UPre-Depends 
> -URecommends -USuggests -UEnhances -UProvides -UEssential -UConflicts 
> -DPriority=optional -UHomepage -UImportant -UBuilt-Using 
> -DAuto-Built-Package=debug-symbols -DPackage=libnet-oping-perl-dbgsym 
> "-DDepends=libnet-oping-perl (= \${binary:Version})" "-DDescription=debug 
> symbols for libnet-oping-perl" 
> -DBuild-Ids=4a793b7f0f68626a61ffd297fd3fa81473910eb3 -DSection=debug 
> -UMulti-Arch -UReplaces -UBreaks returned exit code 2
> dh_gencontrol: error: Aborting due to earlier error
> make[1]: *** [debian/rules:32: override_dh_gencontrol] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/liboping_1.10.0-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963420: zsh: FTBFS: sh: 1: colcrt: not found

[Lucas Nussbaum]

Source: zsh
Version: 5.8-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj/Doc'
> /bin/sh ../../mkinstalldirs 
> /<>/debian/zsh-common/usr/share/man/man1
> mkdir -m 755 -p -- /<>/debian/zsh-common/usr/share/man/man1
> for file in zsh.1 zshbuiltins.1 zshcalsys.1 zshcompctl.1 zshcompwid.1 
> zshcompsys.1 zshcontrib.1 zshexpn.1 zshmisc.1 zshmodules.1 zshoptions.1 
> zshparam.1 zshroadmap.1 zshtcpsys.1 zshzftpsys.1 zshzle.1 zshall.1; do \
> test -s $file || exit 1; \
> /usr/bin/install -c -m 644 $file 
> /<>/debian/zsh-common/usr/share/man/man1/`echo $file | sed 
> 's|zsh|zsh|'` || exit 1; \
> done
> make[3]: Leaving directory '/<>/obj/Doc'
> make[2]: Leaving directory '/<>/obj'
> perl /<>/Util/helpfiles obj/Doc/zshbuiltins.1 
> debian/zsh-common/usr/share/zsh/help
> helpfiles: attempting man obj/Doc/zshbuiltins.1 
> >debian/zsh-common/usr/share/zsh/help/man.tmp
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{ 
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> helpfiles: attempting nroff -man obj/Doc/zshbuiltins.1 
> >debian/zsh-common/usr/share/zsh/help/man.tmp
> helpfiles: attempting col -bx  >debian/zsh-common/usr/share/zsh/help/col.tmp
> sh: 1: col: not found
> helpfiles: attempting colcrt - debian/zsh-common/usr/share/zsh/help/man.tmp 
> >debian/zsh-common/usr/share/zsh/help/col.tmp
> sh: 1: colcrt: not found
> helpfiles: col -bx and colcrt - both failed
> make[1]: *** [debian/rules:97: override_dh_auto_install-indep] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/zsh_5.8-4_unstable.log

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

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#963418: altree: FTBFS: ! Package texgraphicx Error: 'texgraphicx' is now gone

[Lucas Nussbaum]

Source: altree
Version: 1.3.1-9
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/Documentation'
> make[3]: Nothing to be done for 'LU_WATCH_FILES_SAVE'.
> make[3]: Leaving directory '/<>/Documentation'
>  ==> building  manual.pdf <==
> Running: 'pdflatex' '--interaction' 'errorstopmode' '--jobname' 'manual' 
> '\RequirePackage[extension=.pdf]{texdepends}\input{manual.tex}'
> *
> Building manual.pdf fails
> *
> Here are the last lines of the log file
> If this is not enought, try to
> call 'make' with 'VERB=verbose' option
> *
> ==> Last lines in manual.log <==
> Package: iftex 2020/03/06 v1.0d TeX engine tests
> ))
> (/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty
> Package: etoolbox 2019/09/21 v2.5h e-TeX tools for LaTeX (JAW)
> \etb@tempcnta=\count176
> ))
> (/usr/share/texmf/tex/latex/latex-make/texgraphicx.sty
> Package: texgraphicx 2020/06/01 v2.4.0 Fix support for new latex
> 
> 
> ! Package texgraphicx Error: 'texgraphicx' is now gone
> (texgraphicx)Please, switching to 'figlatex' package
> (texgraphicx).
> 
> See the texgraphicx package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.47   package\MessageBreak}{}
>   
> make[2]: *** [LaTeX.mk:823: manual.pdf] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/altree_1.3.1-9_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963411: libisocodes: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: libisocodes
Version: 1.2.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/po'
> make[3]: Leaving directory '/<>/po'
> make[3]: Verzeichnis „/<>“ wird betreten
> make  check-local
> make[4]: Verzeichnis „/<>“ wird betreten
> /usr/bin/valac --pkg libxml-2.0 --pkg gee-0.8 --vapidir=./vapi --pkg config 
> -X -I. -X -DGETTEXT_PACKAGE=\"libisocodes\" -X 
> -DLOCALEDIR=\"/usr/share/locale\" -X -DTESTDIR=\"./tests/data\" 
> --output=codetest tests/codetest.vala tests/test_iso_3166.vala 
> tests/test_iso_3166_2.vala tests/test_iso_639.vala tests/test_iso_639_3.vala 
> tests/test_iso_639_5.vala tests/test_iso_4217.vala tests/test_iso_15924.vala 
> src/isocodes.vala src/iso_3166.vala src/iso_3166_item.vala 
> src/iso_3166_2.vala src/iso_3166_2_item.vala src/iso_639.vala 
> src/iso_639_item.vala src/iso_639_3.vala src/iso_639_3_item.vala 
> src/iso_639_5.vala src/iso_639_5_item.vala src/iso_4217.vala 
> src/iso_4217_item.vala src/iso_15924.vala src/iso_15924_item.vala 
> src/exceptions.vala
> config.vapi:19.2-19.6: warning: argument `prefix' never used
> [CCode (prefix = "", lower_case_cprefix = "", cheader_filename = "config.h")]
>  ^
> Compilation succeeded - 1 warning(s)
> gtester --verbose codetest
> 
> ** (gtester:15218): WARNING **: 07:34:41.559: Deprecated: Since GLib 2.62, 
> gtester and gtester-report are deprecated. Port to TAP.
> TEST: codetest... (pid=15219)
>   /iso_3166/3.x/create class:  OK
>   /iso_3166/3.x/create class with changed filepath:OK
>   /iso_3166/3.x/change filepath with null value or empty string:   OK
>   /iso_3166/3.x/change locale: OK
>   /iso_3166/3.x/throw exception for non-existant file: OK
>   /iso_3166/3.x/throw exception for directory: OK
>   /iso_3166/3.x/throw exception for parsing failure:   OK
>   /iso_3166/3.x/throw exception for wrong ISO data:OK
>   /iso_3166/3.x/find all codes:OK
>   /iso_3166/3.x/find all codes in locale 'fr': OK
>   /iso_3166/3.x/call find_code() without argument: OK
>   /iso_3166/3.x/search empty code: OK
>   /iso_3166/3.x/find code 'de':OK
>   /iso_3166/3.x/find code 'FR':OK
>   /iso_3166/3.x/find code 'Tw':OK
>   /iso_3166/3.x/find code 'ukr':   OK
>   /iso_3166/3.x/find code '798':   OK
>   /iso_3166/3.x/search non existant code:  OK
>   /iso_3166/3.x/find code 'ES' in locale 'de': OK
>   /iso_3166/3.x/find code 'TW' in locale 'fr': OK
>   /iso_3166/3.x/find code 'RUS' in non existant locale:OK
>   /iso_3166_2/3.x/create class:OK
>   /iso_3166_2/3.x/create class with changed filepath:  OK
>   /iso_3166_2/3.x/find all codes:  OK
>   /iso_3166_2/3.x/find all codes in locale 'fr':   OK
>   /iso_3166_2/3.x/call find_code() without argument:   OK
>   /iso_3166_2/3.x/search empty code:   OK
>   /iso_3166_2/3.x/find code 'de-hh':   OK
>   /iso_3166_2/3.x/find code 'FR-78':   OK
>   /iso_3166_2/3.x/find code 'ES-C':OK
>   /iso_3166_2/3.x/search non existant code:OK
>   /iso_3166_2/3.x/find code 'DE-HH' in locale 'fr':OK
>   /iso_3166_2/3.x/find code 'NO-15' in non existant locale:OK
>   /iso_639/3.x/create class:   OK
>   /iso_639/3.x/create class with changed filepath: OK
>   /iso_639/3.x/find all codes: OK
>   /iso_639/3.x/find all codes in locale 'fr':  OK
>   /iso_639/3.x/call find_code() without argument:  OK
>   /iso_639/3.x/search empty code:  OK
>   /iso_639/3.x/find code 'ALG':OK
>   /iso_639/3.x/find code 'Tib':OK
>   /iso_639/3.x/find code 'bod':OK
>   /iso_639/3.x/find code 'aA': OK
>   /iso_639/3.x/search non existant code:   OK
>   /iso_639/3.x/find code 'he' in locale 

Bug#963422: git-extras: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2

[Lucas Nussbaum]

Source: git-extras
Version: 5.1.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> Check dependencies before installation
> Need to install dependency 'column' before installation
> make[1]: *** [Makefile:30: check] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/git-extras_5.1.0-1_unstable.log

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

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#963431: specutils: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

[Lucas Nussbaum]

Source: specutils
Version: 1.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py config 
> Downloading 'astropy-helpers'; run setup.py with the --offline option to 
> force offline installation.
> Freezing version number to ./specutils/version.py
> running config
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:161: 
> AstropyDeprecationWarning: The package argument to generate_version_py has 
> been deprecated and will be removed in future. Specify the package name in 
> setup.cfg instead
>   warnings.warn('The package argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:166: 
> AstropyDeprecationWarning: The version argument to generate_version_py has 
> been deprecated and will be removed in future. Specify the version number in 
> setup.cfg instead
>   warnings.warn('The version argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:171: 
> AstropyDeprecationWarning: The release argument to generate_version_py has 
> been deprecated and will be removed in future. We now use the presence of the 
> "dev" string in the version to determine whether this is a release
>   warnings.warn('The release argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:186: 
> AstropyDeprecationWarning: Specifying the package name using the 
> "package_name" option in setup.cfg is deprecated - use the "name" option 
> instead.
>   warnings.warn('Specifying the package name using the "package_name" '
> /usr/lib/python3/dist-packages/astropy_helpers/version_helpers.py:239: 
> AstropyDeprecationWarning: The packagename argument to generate_version_py 
> has been deprecated and will be removed in future. Specify the package name 
> in setup.cfg instead
>   warnings.warn('The packagename argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/version_helpers.py:244: 
> AstropyDeprecationWarning: The version argument to generate_version_py has 
> been deprecated and will be removed in future. Specify the version number in 
> setup.cfg instead
>   warnings.warn('The version argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/version_helpers.py:249: 
> AstropyDeprecationWarning: The release argument to generate_version_py has 
> been deprecated and will be removed in future. We now use the presence of the 
> "dev" string in the version to determine whether this is a release
>   warnings.warn('The release argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/version_helpers.py:264: 
> AstropyDeprecationWarning: Specifying the package name using the 
> "package_name" option in setup.cfg is deprecated - use the "name" option 
> instead.
>   warnings.warn('Specifying the package name using the "package_name" '
> /usr/lib/python3/dist-packages/astropy_helpers/git_helpers.py:114: 
> UserWarning: Error running git: [Errno 2] No such file or directory: 'git'
>   warnings.warn('Error running git: ' + str(e))
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> --use-system-astropy-helpers
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8/build/specutils
> copying specutils/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils
> copying specutils/_astropy_init.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils
> copying specutils/conftest.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils
> copying specutils/version.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils
> creating /<>/.pybuild/cpython3_3.8/build/specutils/analysis
> copying specutils/analysis/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils/analysis
> copying specutils/analysis/width.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils/analysis
> copying specutils/analysis/template_comparison.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils/analysis
> copying specutils/analysis/uncertainty.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils/analysis
> copying specutils/analysis/flux.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils/analysis
> copying specutils/analysis/location.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils/analysis
> copying specutils/analysis/correlation.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils/analysis
> copying specutils/analysis/utils.py -> 
> /<>/.pybuild/cpython3_3.8/build/specutils/analysis
> creating /<>/.pybuild/cpython3_3.8/build/specutils/utils
> copying 

Bug#963424: sensible-utils: FTBFS: po4a::po: Invalid value for option 'porefs' ('noline,wrap' is not one of 'full', 'counter', 'noline', 'file' or 'never')

[Lucas Nussbaum]

Source: sensible-utils
Version: 0.0.12+nmu1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>/man'
> Makefile:541: warning: ignoring prerequisites on suffix rule definition
> Makefile:543: warning: ignoring prerequisites on suffix rule definition
> Makefile:545: warning: ignoring prerequisites on suffix rule definition
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e 
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e 
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e 
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e 
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e 
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' sensible-editor.man 
> >sensible-editor.1
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e 
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e 
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e 
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e 
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e 
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' sensible-browser.man 
> >sensible-browser.1
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e 
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e 
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e 
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e 
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e 
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' sensible-pager.man 
> >sensible-pager.1
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e 
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e 
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e 
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e 
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e 
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' select-editor.man 
> >select-editor.1
> po4a --previous --srcdir . --destdir . --no-backups --porefs noline,wrap 
> --msgmerge-opt=--add-location=file --package-name sensible-utils  
> ./po4a/po4a.cfg
> po4a::po: Invalid value for option 'porefs' ('noline,wrap' is not one of 
> 'full', 'counter', 'noline', 'file' or 'never')
> make[2]: *** [Makefile:536: man.stamp] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/sensible-utils_0.0.12+nmu1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963429: node-pump: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-pump
Version: 3.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-pump
> dpkg-buildpackage: info: source version 3.0.0-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Xavier Guimard 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with nodejs
>dh_auto_clean --buildsystem=nodejs
>   rm -rf ./node_modules/.cache
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-pump using existing 
> ./node-pump_3.0.0.orig.tar.gz
> dpkg-source: info: building node-pump in node-pump_3.0.0-2.debian.tar.xz
> dpkg-source: info: building node-pump in node-pump_3.0.0-2.dsc
>  debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   /bin/sh -ex debian/tests/pkg-js/test
> + set -e
> + set -x
> + node ./test-node.js
> /<>/test-node.js:52
>   throw new Error('timeout')
>   ^
> 
> Error: timeout
> at Timeout._onTimeout (/<>/test-node.js:52:9)
> at listOnTimeout (internal/timers.js:549:17)
> at processTimers (internal/timers.js:492:7)
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/node-pump_3.0.0-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!

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#963408: pmtools: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: pmtools
Version: 2.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t t/lib/*.t
> t/basepods.t . 
> 1..3
> ok 1 - basepods runs
> ok 2 - found Perl POD
> ok 3 - found POD POD
> ok
> t/faqpods.t .. 
> 1..2
> ok 1 - faqpods runs
> ok 2 - found a Perl FAQ POD
> ok
> t/lib/pmtools.t .. 
> 1..7
> ok 1 - created a pmtools iterator
> ok 2 - first POD file, first @INC
> ok 3 - middle POD file, first @INC
> ok 4 - last POD file, first @INC
> ok 5 - last POD file, last @INC
> ok 6 - beyond end of filenames
> ok 7 - way beyond end of filenames
> ok
> t/modpods.t .. 
> 1..2
> ok 1 - modpods runs
> ok 2 - found Tie::Hash
> ok
> t/pfcat.t  
> 1..2
> ok 1 - pfcat runs
> ok 2 - catted module function
> ok
> t/plxload.t .. 
> 1..1
> ok 1 - modules loaded
> ok
> t/pmall.t  
> 1..2
> ok 1 - pmall runs
> ok 2 - synopsized all modules
> ok
> 
> #   Failed test 'found Carp'
> #   at t/pman.t line 20.
> #   'pod2text: unable to format 
> /usr/lib/x86_64-linux-gnu/perl-base/Carp.pm
> # '
> # doesn't match '(?^ms:NAME.*[Cc]arp - \w.*SYNOPSIS.*DESCRIPTION)'
> # Looks like you failed 1 test of 2.
> t/pman.t . 
> 1..2
> ok 1 - pman runs
> not ok 2 - found Carp
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/2 subtests 
> t/pmcat.t  
> 1..2
> ok 1 - pmcat runs
> ok 2 - catted Carp
> ok
> t/pmcheck.t .. 
> 1..2
> ok 1 - pmcheck runs
> ok 2 - pmcheck had output
> ok
> t/pmdesc.t ... 
> 1..2
> ok 1 - pmdesc runs
> ok 2 - described a module
> ok
> t/pmeth.t  
> 1..2
> ok 1 - pmeth runs
> ok 2 - list methods of a module
> ok
> t/pmexp.t  
> 1..2
> ok 1 - pmexp runs
> ok 2 - listed module exports
> ok
> t/pmfunc.t ... 
> 1..3
> ok 1 - pmfunc runs
> ok 2 - found 'chdir()'
> ok 3 - display function body
> ok
> t/pmload.t ... 
> 1..2
> ok 1 - pmload runs
> ok 2 - listed loaded modules
> ok
> t/pmls.t . 
> 1..2
> ok 1 - pmls runs
> ok 2 - found Tie::Hash
> ok
> t/pmpath.t ... 
> 1..2
> ok 1 - pmpath runs
> ok 2 - found Tie::Hash
> ok
> t/pmvers.t ... 
> 1..2
> ok 1 - pmvers runs
> ok 2 - found version of Tie::Hash
> ok
> t/podgrep.t .. 
> 1..2
> ok 1 - podgrep runs
> ok 2 - found DESCRIPTION
> ok
> t/pods.t . 
> 1..2
> ok 1 - pods runs
> ok 2 - found Tie::Hash
> ok
> t/podtoc.t ... 
> 1..2
> ok 1 - podtoc runs
> ok 2 - found Table of Contents
> ok
> t/sitepods.t . 
> 1..1
> ok 1 - sitepods runs
> ok
> t/stdpods.t .. 
> 1..2
> ok 1 - stdpods runs
> ok 2 - found Tie::Hash
> ok
> 
> Test Summary Report
> ---
> t/pman.t   (Wstat: 256 Tests: 2 Failed: 1)
>   Failed test:  2
>   Non-zero exit status: 1
> Files=23, Tests=51,  3 wallclock secs ( 0.04 usr  0.03 sys +  2.14 cusr  0.41 
> csys =  2.62 CPU)
> Result: FAIL
> Failed 1/23 test programs. 1/51 subtests failed.
> make[2]: *** [Makefile:1077: test_dynamic] Error 255
> make[2]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/pmtools_2.2.0-1_unstable.log

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

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#963423: auto-multiple-choice: FTBFS: ! LaTeX Error: File `ctexhook.sty' not found.

[Lucas Nussbaum]

Source: auto-multiple-choice
Version: 1.4.0-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/I18N'
> msgfmt lang/ar.po -o lang/ar.mo
> msgfmt lang/de.po -o lang/de.mo
> msgfmt lang/es.po -o lang/es.mo
> msgfmt lang/fr.po -o lang/fr.mo
> msgfmt lang/ja.po -o lang/ja.mo
> msgfmt lang/pt_BR.po -o lang/pt_BR.mo
> msgfmt lang/pt_PT.po -o lang/pt_PT.mo
> msgfmt lang/ta.po -o lang/ta.mo
> make[3]: Leaving directory '/<>/I18N'
> pngtopnm icons/auto-multiple-choice.png | ppmtoxpm > 
> icons/auto-multiple-choice.xpm
> ppmtoxpm: (Computing colormap...
> ppmtoxpm: ...Done.  40 colors found.)
> 
> rsvg-convert -f pdf img_src/important.svg -o img_pdf/important.pdf
> rsvg-convert -f pdf img_src/note.svg -o img_pdf/note.pdf
> rsvg-convert -f pdf img_src/warning.svg -o img_pdf/warning.pdf
> dblatex -P latex.encoding=utf8 -b xetex -t tex -p custom.xsl 
> --texstyle=amcdocstyle --xslt-opts="--nonet" --xslt-opts="--catalogs"  
> auto-multiple-choice.fr.xml -o auto-multiple-choice.fr.tex
> Build the book set list...
> Variable $SGML_CATALOG_FILES not set
> Build the listings...
> Variable $SGML_CATALOG_FILES not set
> Variable $SGML_CATALOG_FILES not set
> XSLT stylesheets DocBook - LaTeX 2e (0.3.11py3)
> ===
> Build the listings...
> Variable $SGML_CATALOG_FILES not set
> Variable $SGML_CATALOG_FILES not set
> XSLT stylesheets DocBook - LaTeX 2e (0.3.11py3)
> ===
> dblatex -P latex.encoding=utf8 -b xetex -t tex -p custom.xsl 
> --texstyle=amcdocstyle --xslt-opts="--nonet" --xslt-opts="--catalogs"  
> auto-multiple-choice.ja.xml -o auto-multiple-choice.ja.tex
> Build the book set list...
> Variable $SGML_CATALOG_FILES not set
> Image 'tiger' not found
> 'auto-multiple-choice.en.tex' successfully built
> /usr/bin/perl extrait-fichiers.pl --liste auto-multiple-choice.en.ext 
> auto-multiple-choice.en.xml
> xsltproc --nonet --catalogs --param man.charmap.use.subset "0" --param 
> make.year.ranges "1" --param make.single.year.ranges "1" --param 
> man.output.lang.in.name.enabled "1" 
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl 
> auto-multiple-choice.en.xml
> Variable $SGML_CATALOG_FILES not set
> *** File auto-multiple-choice.en.xml
>   I lang=en
>   * extracting modeles/en/simple-txt
> embedded description / N=AMC-TXT format simple example
>   * extracting modeles/en/simple
> embedded description / N=Simple example
>   * extracting modeles/en/groups
> embedded description / N=Groups
>   * extracting modeles/en/separate
> embedded description / N=Separate answers
>   * extracting modeles/en/scoring
> embedded description / N=Scoring strategy
> rm -f html/auto-multiple-choice.en/*.html
> xsltproc --nonet --catalogs --stringparam base.dir 
> html/auto-multiple-choice.en/ doc-xhtml.xsl auto-multiple-choice.en.xml
> Variable $SGML_CATALOG_FILES not set
> Image 'tigre' not found
> 'auto-multiple-choice.fr.tex' successfully built
> Build the listings...
> /usr/bin/perl extrait-fichiers.pl --liste auto-multiple-choice.fr.ext 
> auto-multiple-choice.fr.xml
> Variable $SGML_CATALOG_FILES not set
> Note: Writing auto-multiple-choice.1
> Variable $SGML_CATALOG_FILES not set
> Writing html/auto-multiple-choice.en/prerequis.html for sect1(prerequis)
> Writing html/auto-multiple-choice.en/usagenotes.html for sect1(usagenotes)
> *** File auto-multiple-choice.fr.xml
>   I lang=fr
>   * extracting modeles/fr/simple-txt
> embedded description / N=Exemple simple au format AMC-TXT
>   * extracting modeles/fr/simple
> embedded description / N=Exemple simple
>   * extracting modeles/fr/groupes
> embedded description / N=Groupes
>   * extracting modeles/fr/ensemble
> embedded description / N=R?ponses s?par?es
>   * extracting modeles/fr/bareme
> embedded description / N=Bar?me
> xsltproc --nonet --catalogs --param man.charmap.use.subset "0" --param 
> make.year.ranges "1" --param make.single.year.ranges "1" --param 
> man.output.lang.in.name.enabled "1" 
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl 
> auto-multiple-choice.fr.xml
> Note: Writing AMC-prepare.1
> Note: meta source : no *info/productname or alternativeAMC-meptex
> Note: meta source : see http://www.docbook.org/tdg5/en/html/produ  AMC-meptex
> Note: meta source : no refentry/refmeta/refmiscinfo@class=source   AMC-meptex
> Note: meta source : see http://www.docbook.org/tdg5/en/html/refmi  AMC-meptex
> Note: meta version: no *info/productnumber or alternative  AMC-meptex
> Note: meta version: see http://www.docbook.org/tdg5/en/html/produ  AMC-meptex
> Note: meta version: no refentry/refmeta/refmiscinfo@class=version  AMC-meptex
> Note: meta version: see 

Bug#963413: vmem: FTBFS: man: can't execute col: No such file or directory

[Lucas Nussbaum]

Source: vmem
Version: 1.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc'
> ../utils/md2man.sh libvmem/libvmem.7.md default.man generated/libvmem.7;  
> ../utils/md2man.sh libvmmalloc/libvmmalloc.7.md default.man 
> generated/libvmmalloc.7;
> ../utils/md2man.sh libvmem/vmem_create.3.md default.man 
> generated/vmem_create.3;  ../utils/md2man.sh libvmem/vmem_malloc.3.md 
> default.man generated/vmem_malloc.3;
> man ./generated/libvmem.7 > generated/libvmem.7.txt
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{ 
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[3]: *** [Makefile:103: generated/libvmem.7.txt] Error 3

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/vmem_1.8-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963425: node-terser: FTBFS: ERROR: `m` is not a supported option

[Lucas Nussbaum]

Source: node-terser
Version: 4.1.2-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> NODE_PATH=lib TRAVIS=1 node test/run-tests.js \
>   
> *** Entering [compress]
> --- arguments.js
> Running test [replace_index]
> Running test [replace_index_strict]
> Running test [replace_index_keep_fargs]
> Running test [replace_index_keep_fargs_strict]
> Running test [modified]
> Running test [modified_strict]
> Running test [arguments_in_arrow_func_1]
> Running test [arguments_in_arrow_func_2]
> Running test [arguments_and_destructuring_1]
> Running test [arguments_and_destructuring_2]
> Running test [arguments_and_destructuring_3]
> Running test [duplicate_parameter_with_arguments]
> --- array-constructor.js
> Running test [array_constructor]
> Running test [array_constructor_unsafe]
> --- arrays.js
> Running test [holes_and_undefined]
> Running test [constant_join]
> Running test [constant_join_2]
> Running test [spread_with_variable_as_last_element]
> Running test [spread_with_variable_in_middle]
> Running test [spread_with_variable_at_front]
> Running test [spread_with_variable_at_front_after_elisions]
> Running test [spread_with_array_at_end]
> Running test [spread_with_logical_expression_at_end]
> Running test [spread_with_logical_expression_at_middle]
> Running test [constant_join_3]
> Running test [for_loop]
> Running test [index]
> Running test [length]
> Running test [index_length]
> --- arrow.js
> Running test [arrow_functions_without_body]
> Running test [arrow_functions_with_body]
> Running test [arrow_function_with_single_parameter_with_default]
> Running test [arrow_binding_pattern]
> Running test [arrow_binding_pattern_strict]
> Running test [arrow_with_regexp]
> Running test [arrow_unused]
> Running test [arrow_unused_toplevel]
> Running test [no_leading_parentheses]
> Running test [async_identifiers]
> Running test [async_function_expression]
> Running test [issue_27]
> Running test [issue_2105_1]
> Running test [issue_2105_2]
> Running test [issue_2136_2]
> Running test [issue_2136_3]
> Running test [call_args]
> Running test [call_args_drop_param]
> Running test [issue_485_crashing_1530]
> Running test [issue_2084]
> Running test [export_default_object_expression]
> Running test [concise_methods_with_computed_property2]
> Running test [async_object_literal]
> Running test [issue_2271]
> Running test [concise_method_with_super]
> Running test [issue_3092a]
> Running test [issue_3092b]
> --- ascii.js
> Running test [ascii_only_true]
> Running test [ascii_only_false]
> --- asm.js
> Running test [asm_mixed]
> Running test [asm_toplevel]
> Running test [asm_function_expression]
> Running test [asm_nested_functions]
> --- assignment.js
> Running test [op_equals_left_local_var]
> Running test [op_equals_right_local_var]
> Running test [op_equals_left_global_var]
> Running test [op_equals_right_global_var]
> --- async.js
> Running test [await_precedence]
> Running test [await_precedence_prop]
> Running test [await_precedence_call]
> Running test [async_function_declaration]
> Running test [async_function_expression]
> Running test [async_class]
> Running test [async_object_literal]
> Running test [async_export]
> Running test [async_inline]
> Running test [async_identifiers]
> Running test [async_shorthand_property]
> Running test [async_arrow]
> Running test [async_arrow_wait]
> Running test [async_arrow_iife]
> Running test [async_arrow_iife_negate_iife]
> Running test [issue_2344_1]
> Running test [issue_2344_2]
> Running test [issue_3079]
> Running test [issue_3079_2]
> Running test [for_await_of]
> Running test [for_await_of_2]
> Running test [issue_87]
> Running test [async_generator_function]
> Running test [async_generator_class_method]
> Running test [async_generator_static_class_method]
> Running test [async_generator_object_literal_method]
> --- big_int.js
> Running test [big_int_positive]
> Running test [big_int_negative]
> Running test [big_int_hex]
> Running test [big_int_binary]
> Running test [big_int_octal]
> --- block-scope.js
> Running test [let_statement]
> Running test [do_not_hoist_let]
> Running test [do_not_remove_anon_blocks_if_they_have_decls]
> Running test [remove_unused_in_global_block]
> Running test [regression_block_scope_resolves]
> Running test [switch_block_scope_mangler]
> Running test [issue_241]
> Running test [issue_334]
> --- blocks.js

Bug#963427: ding: FTBFS: man: can't execute col: No such file or directory

[Lucas Nussbaum]

Source: ding
Version: 1.8.1-8
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> sed -e 's#/usr/share/dict/de-en.txt#/usr/share/trans/de-en#' ding \
>   > `pwd`/debian/ding/usr/bin/ding
> chmod 755 `pwd`/debian/ding/usr/bin/ding
> install -m644 ding.1 `pwd`/debian/ding/usr/share/man/man1/ding.1
> install -m644 ding.desktop \
>   `pwd`/debian/ding/usr/share/applications/ding.desktop
> convert ding.png -geometry 32x32 -colors 6 \
>   `pwd`/debian/ding/usr/share/pixmaps/dbook.xpm
> install -m644 debian/mini-dbook.xpm \
>   `pwd`/debian/ding/usr/share/pixmaps/mini-dbook.xpm
> install -m644 ding.png `pwd`/debian/ding/usr/share/icons/hicolor/32x32/apps/
> convert ding.png -geometry 64x64 \
>   `pwd`/debian/ding/usr/share/icons/hicolor/64x64/apps/ding.png
> install -m644 debian/html/* `pwd`/debian/ding/usr/share/doc/ding/html/
> env -u LANG LC_ALL=C MANWIDTH=80 MAN_DISABLE_SECCOMP=1 \
>   man -l -7 -P /bin/cat ding.1 | col -b \
>   > `pwd`/debian/ding/usr/share/doc/ding/html/ding.1.txt
> /bin/sh: 2: col: not found
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{ 
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[1]: *** [debian/rules:47: override_dh_auto_install] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/ding_1.8.1-8_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963430: artemis: FTBFS: /bin/sh: 1: /usr/share/java/j2ssh-core.jar: Permission denied

[Lucas Nussbaum]

Source: artemis
Version: 17.0.1+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, 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
>jh_linkjars
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> dh_auto_build -- jar
>   make -j4 "INSTALL=install --strip-program=true" jar
> make[2]: Entering directory '/<>'
> CLASSPATH=/usr/share/java/biojava.jar /usr/share/java/j2ssh-core.jar 
> /usr/share/java/ibatis.jar /usr/share/java/log4j-1.2.jar 
> /usr/share/java/postgresql-jdbc3.jar /usr/share/java/picard.jar 
> /usr/share/java/htsjdk.jar /usr/share/java/commons-net.jar 
> /usr/share/java/commons-lang3.jar /usr/share/java/batik-all.jar 
> /usr/share/java/batik-awt-util.jar /usr/share/java/batik-dom.jar 
> /usr/share/java/batik-ext.jar /usr/share/java/batik-svggen.jar 
> /usr/share/java/batik-util.jar /usr/share/java/batik-xml.jar 
> /usr/share/EMBOSS/jemboss/lib/jemboss.jar /<>: javac -source 1.8 
> -target 1.8   uk/ac/sanger/artemis/Action.java
> CLASSPATH=/usr/share/java/biojava.jar /usr/share/java/j2ssh-core.jar 
> /usr/share/java/ibatis.jar /usr/share/java/log4j-1.2.jar 
> /usr/share/java/postgresql-jdbc3.jar /usr/share/java/picard.jar 
> /usr/share/java/htsjdk.jar /usr/share/java/commons-net.jar 
> /usr/share/java/commons-lang3.jar /usr/share/java/batik-all.jar 
> /usr/share/java/batik-awt-util.jar /usr/share/java/batik-dom.jar 
> /usr/share/java/batik-ext.jar /usr/share/java/batik-svggen.jar 
> /usr/share/java/batik-util.jar /usr/share/java/batik-xml.jar 
> /usr/share/EMBOSS/jemboss/lib/jemboss.jar /<>: javac -source 1.8 
> -target 1.8   uk/ac/sanger/artemis/ActionController.java
> /bin/sh: 1: /usr/share/java/j2ssh-core.jar: Permission denied
> make[2]: *** [Makefile:48: uk/ac/sanger/artemis/Action.class] Error 126

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/artemis_17.0.1+dfsg-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!

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#963419: kombu: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 --system=custom "--test-args={interpreter} setup.py test" returned exit code 13

[Lucas Nussbaum]

Source: kombu
Version: 4.6.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="{interpreter} setup.py test"
> I: pybuild base:217: python3.8 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.
> WARNING: The pip package is not available, falling back to EasyInstall for 
> handling setup_requires/test_requires; this is deprecated and will be removed 
> in a future version.
> Searching for amqp<2.6,>=2.5.2
> Reading https://pypi.org/simple/amqp/
> Download error on https://pypi.org/simple/amqp/: [Errno 111] Connection 
> refused -- Some packages may not be found!
> Couldn't retrieve index page for 'amqp'
> Scanning index of all packages (this may take a while)
> Reading https://pypi.org/simple/
> Download error on https://pypi.org/simple/: [Errno 111] Connection refused -- 
> Some packages may not be found!
> No local packages or working download links found for amqp<2.6,>=2.5.2
> error: Could not find suitable distribution for 
> Requirement.parse('amqp<2.6,>=2.5.2')
> E: pybuild pybuild:352: test: plugin custom failed with: exit code=1: 
> python3.8 setup.py test
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 
> --system=custom "--test-args={interpreter} setup.py test" returned exit code 
> 13

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/kombu_4.6.8-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963412: libzt: FTBFS: dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --s

[Lucas Nussbaum]

Source: libzt
Version: 0.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> NOTE: Build tree is not configured, using curated compiler options.
> NOTE: Use ./configure to disable this mechanism
> rm -f *.o
> rm -f libzt.a
> rm -f libzt.so libzt.so.1
> rm -f man/libzt-test.1 man/libzt.3 man/zt_check.3 man/zt_claim.3 
> man/ZT_CMP_BOOL.3 man/ZT_CMP_INT.3 man/ZT_CMP_PTR.3 man/ZT_CMP_RUNE.3 
> man/ZT_CMP_UINT.3 man/ZT_CURRENT_LOCATION.3 man/ZT_FALSE.3 man/zt_location.3 
> man/zt_location_at.3 man/zt_main.3 man/ZT_NOT_NULL.3 man/ZT_NULL.3 
> man/zt_pack_boolean.3 man/zt_pack_integer.3 man/zt_pack_nothing.3 
> man/zt_pack_pointer.3 man/zt_pack_rune.3 man/zt_pack_string.3 
> man/zt_pack_unsigned.3 man/zt_test.3 man/zt_test_case_func.3 
> man/zt_test_suite_func.3 man/ZT_TRUE.3 man/zt_value.3 
> man/zt_visit_test_case.3 man/zt_visitor.3
> rm -f *.profdata *.profraw
> rm -f libzt-test
> rm -f *.i
> rm -f *.PVS-Studio.log
> rm -rf pvs-report
> rm -rf cov-int
> rm -f libzt-0.3-coverity.tar.gz
> rm -f GNUmakefile.configure.mk
> make[1]: Leaving directory '/<>'
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building libzt using existing ./libzt_0.3.orig.tar.gz
> dpkg-source: info: building libzt using existing ./libzt_0.3.orig.tar.gz.asc
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building libzt in libzt_0.3-2.debian.tar.xz
> dpkg-source: info: building libzt in libzt_0.3-2.dsc
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-option-checking --disable-silent-rules 
> --libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
> --disable-maintainer-mode --disable-dependency-tracking
> configure: unknown option --disable-option-checking
> dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-option-checking --disable-silent-rules 
> --libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
> --disable-maintainer-mode --disable-dependency-tracking returned exit code 1
> make: *** [debian/rules:4: binary] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/libzt_0.3-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!

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#963414: latex2rtf: FTBFS: man: can't execute col: No such file or directory

[Lucas Nussbaum]

Source: latex2rtf
Version: 2.3.16-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>/doc'
> makeinfo latex2rtf
> chmod 644 latex2rtf.info
> texi2pdf latex2rtf.texi
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
> (preloaded format=pdfetex)
>  restricted \write18 enabled.
> entering extended mode
> 
> (./latex2rtf.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions, localization, formatting,
> and turning on texinfo input format.) 
> [1{/var/lib/texmf/fonts/map/pdftex/updmap
> /pdftex.map}] [2] Chapter 1
> Cross reference values unknown; you must run TeX again.
> Writing index file latex2rtf.cp
> Chapter 2 [1] [2] [3] [4] [5] [6] Chapter 3 [7] [8] [9] [10] [11] [12] [13]
> Chapter 4 [14] [15] [16] [17] [18] Chapter 5 [19] [20] [21] [22] [23]
> Chapter 6 [24] Chapter 7 [25] [26] Chapter 8 [27] [28] [29]
> Writing index file latex2rtf.fn
> [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44]
> [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] Chapter 9 [56]
> No file latex2rtf.fns.
> Chapter 10 [57] [58]
> No file latex2rtf.cps.
> [59] [60] (/<>/doc/latex2rtf.toc [-1])
> [-2] (/<>/doc/latex2rtf.toc)
> (/<>/doc/latex2rtf.toc) ) ve/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx12.pfb> mf-dist/fonts/type1/public/amsfonts/cm/cmcsc10.pfb> st/fonts/type1/public/amsfonts/cm/cmmi10.pfb> ts/type1/public/amsfonts/cm/cmmi12.pfb> e1/public/amsfonts/cm/cmmi7.pfb> ic/amsfonts/cm/cmr10.pfb> onts/cm/cmr9.pfb> cmsy10.pfb> .pfb>
> Output written on latex2rtf.pdf (64 pages, 221371 bytes).
> Transcript written on latex2rtf.log.
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
> (preloaded format=pdfetex)
>  restricted \write18 enabled.
> entering extended mode
> 
> (./latex2rtf.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions, localization, formatting,
> and turning on texinfo input format.) 
> [1{/var/lib/texmf/fonts/map/pdftex/updmap
> /pdftex.map}] [2] Chapter 1
> (/<>/doc/latex2rtf.aux)
> Writing index file latex2rtf.cp
> Chapter 2 [1] [2] [3] [4] [5] [6] Chapter 3 [7] [8] [9] [10] [11] [12] [13]
> Chapter 4 [14] [15] [16] [17] [18] Chapter 5 [19] [20] [21] [22] [23]
> Chapter 6 [24] Chapter 7 [25] [26] Chapter 8 [27] [28] [29]
> Writing index file latex2rtf.fn
> [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44]
> [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] Chapter 9 [56]
> (/<>/doc/latex2rtf.fns [57] [58] [59]
> [60] [61] [62] [63]) Chapter 10 [64]
> (/<>/doc/latex2rtf.cps) [65] [66]
> (/<>/doc/latex2rtf.toc [-1]) [-2]
> (/<>/doc/latex2rtf.toc)
> (/<>/doc/latex2rtf.toc) ) ve/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx12.pfb> mf-dist/fonts/type1/public/amsfonts/cm/cmcsc10.pfb> st/fonts/type1/public/amsfonts/cm/cmmi10.pfb> ts/type1/public/amsfonts/cm/cmmi12.pfb> e1/public/amsfonts/cm/cmmi7.pfb> ic/amsfonts/cm/cmmi9.pfb> onts/cm/cmr10.pfb> /cmr9.pfb> pfb> usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmtt12.pfb> are/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmtt9.pfb>
> Output written on latex2rtf.pdf (70 pages, 307880 bytes).
> Transcript written on latex2rtf.log.
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
> (preloaded format=pdfetex)
>  restricted \write18 enabled.
> entering extended mode
> 
> (./latex2rtf.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions, localization, formatting,
> and turning on texinfo input format.) 
> [1{/var/lib/texmf/fonts/map/pdftex/updmap
> /pdftex.map}] [2] Chapter 1
> (/<>/doc/latex2rtf.aux)
> Writing index file latex2rtf.cp
> Chapter 2 [1] [2] [3] [4] [5] [6] Chapter 3 [7] [8] [9] [10] [11] [12] [13]
> Chapter 4 [14] [15] [16] [17] [18] Chapter 5 [19] [20] [21] [22] [23]
> Chapter 6 [24] Chapter 7 [25] [26] Chapter 8 [27] [28] [29]
> Writing index file latex2rtf.fn
> [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44]
> [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] Chapter 9 [56]
> (/<>/doc/latex2rtf.fns [57] [58] [59]
> [60] [61] [62] [63]) Chapter 10 [64]
> (/<>/doc/latex2rtf.cps) [65] [66]
> (/<>/doc/latex2rtf.toc [-1]) [-2]
> (/<>/doc/latex2rtf.toc)
> (/<>/doc/latex2rtf.toc) ) 

Bug#963426: keras: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

[Lucas Nussbaum]

Source: keras
Version: 2.3.1+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="cd {build_dir} && py.test-3 
> -oaddopts=-v --ignore=tests/keras/utils/multi_gpu_test.py 
> --ignore=tests/docs/test_documentation.py 
> --ignore=tests/keras/callbacks/callbacks_test.py 
> --ignore=tests/keras/metrics_confusion_matrix_test.py 
> --ignore=tests/integration_tests/test_image_data_tasks.py 
> --ignore=tests/integration_tests/test_temporal_data_tasks.py 
> --ignore=tests/keras/backend/backend_test.py 
> --ignore=tests/integration_tests/imagenet_utils_test.py 
> --ignore=tests/integration_tests/test_datasets.py 
> --ignore=tests/docs/test_doc_auto_generation.py --ignore=tests/test_api.py" 
> dh_auto_test
>   pybuild --test --test-pytest -i python{version} -p 3.8
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.8_keras/build && 
> py.test-3 -oaddopts=-v --ignore=tests/keras/utils/multi_gpu_test.py 
> --ignore=tests/docs/test_documentation.py 
> --ignore=tests/keras/callbacks/callbacks_test.py 
> --ignore=tests/keras/metrics_confusion_matrix_test.py 
> --ignore=tests/integration_tests/test_image_data_tasks.py 
> --ignore=tests/integration_tests/test_temporal_data_tasks.py 
> --ignore=tests/keras/backend/backend_test.py 
> --ignore=tests/integration_tests/imagenet_utils_test.py 
> --ignore=tests/integration_tests/test_datasets.py 
> --ignore=tests/docs/test_doc_auto_generation.py --ignore=tests/test_api.py
> = test session starts 
> ==
> platform linux -- Python 3.8.3, pytest-4.6.11, py-1.8.1, pluggy-0.13.0 -- 
> /usr/bin/python3
> cachedir: .pytest_cache
> rootdir: /<>
> plugins: flaky-3.6.1
> collecting ... collected 1051 items
> 
> tests/test_dynamic_trainability.py::test_layer_trainability_switch PASSED [  
> 0%]
> tests/test_dynamic_trainability.py::test_model_trainability_switch PASSED [  
> 0%]
> tests/test_dynamic_trainability.py::test_nested_model_trainability PASSED [  
> 0%]
> tests/test_loss_masking.py::test_masking PASSED  [  
> 0%]
> tests/test_loss_masking.py::test_masking_is_all_zeros PASSED [  
> 0%]
> tests/test_loss_masking.py::test_loss_masking PASSED [  
> 0%]
> tests/test_loss_weighting.py::test_sequential_class_weights PASSED   [  
> 0%]
> tests/test_loss_weighting.py::test_sequential_sample_weights PASSED  [  
> 0%]
> tests/test_loss_weighting.py::test_sequential_temporal_sample_weights PASSED 
> [  0%]
> tests/test_loss_weighting.py::test_class_weight_wrong_classes PASSED [  
> 0%]
> tests/test_model_pickling.py::test_sequential_model_pickling PASSED  [  
> 1%]
> tests/test_model_pickling.py::test_sequential_model_pickling_custom_objects 
> PASSED [  1%]
> tests/test_model_pickling.py::test_functional_model_pickling PASSED  [  
> 1%]
> tests/test_model_pickling.py::test_pickling_multiple_metrics_outputs PASSED [ 
>  1%]
> tests/test_model_pickling.py::test_pickling_without_compilation PASSED   [  
> 1%]
> tests/test_model_pickling.py::test_pickling_right_after_compilation PASSED [  
> 1%]
> tests/test_model_saving.py::test_sequential_model_saving PASSED  [  
> 1%]
> tests/test_model_saving.py::test_sequential_model_saving_2 PASSED[  
> 1%]
> tests/test_model_saving.py::test_functional_model_saving PASSED  [  
> 1%]
> tests/test_model_saving.py::test_model_saving_to_pre_created_h5py_file FAILED 
> [  1%]
> tests/test_model_saving.py::test_model_saving_to_binary_stream FAILED[  
> 1%]
> tests/test_model_saving.py::test_model_loading_from_binary_stream PASSED [  
> 2%]
> tests/test_model_saving.py::test_model_save_load_binary_in_memory FAILED [  
> 2%]
> tests/test_model_saving.py::test_saving_multiple_metrics_outputs PASSED  [  
> 2%]
> tests/test_model_saving.py::test_saving_without_compilation PASSED   [  
> 2%]
> tests/test_model_saving.py::test_saving_right_after_compilation PASSED   [  
> 2%]
> tests/test_model_saving.py::test_saving_unused_layers_is_ok PASSED   [  
> 2%]
> tests/test_model_saving.py::test_loading_weights_by_name_and_reshape PASSED [ 
>  2%]
> tests/test_model_saving.py::test_loading_weights_by_name_2 PASSED[  
> 2%]
> tests/test_model_saving.py::test_loading_weights_by_name_skip_mismatch PASSED 
> [  2%]
> tests/test_model_saving.py::test_saving_lambda_custom_objects PASSED [  
> 2%]
> tests/test_model_saving.py::test_saving_lambda_numpy_array_arguments PASSED [ 
>  3%]
> tests/test_model_saving.py::test_saving_custom_activation_function PASSED [  
> 3%]
> tests/test_model_saving.py::test_saving_model_with_long_layer_names PASSED [  
> 3%]
> tests/test_model_saving.py::test_saving_model_with_long_weights_names PASSED 
> [  3%]
> 

Bug#963410: ros-rospack: FTBFS: tests failed

[Lucas Nussbaum]

Source: ros-rospack
Version: 2.6.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/<>/build'
> make[5]: Nothing to be done for 'CMakeFiles/run_tests.dir/build'.
> make[5]: Leaving directory '/<>/build'
> [100%] Built target run_tests
> make[4]: Leaving directory '/<>/build'
> /usr/bin/cmake -E cmake_progress_start /<>/build/CMakeFiles 0
> make[3]: Leaving directory '/<>/build'
> make[2]: Leaving directory '/<>/build'
> catkin_test_results
> build/test_results/rospack/gtest-rospack-utest.xml: 10 tests, 0 errors, 6 
> failures, 0 skipped
> Summary: 10 tests, 0 errors, 6 failures, 0 skipped
> make[1]: *** [debian/rules:8: override_dh_auto_test] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/ros-rospack_2.6.2-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963409: kakoune: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2

[Lucas Nussbaum]

Source: kakoune
Version: 2020.01.16-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/src'
> ln -sf kak.debug kak
> cd ../test && ./run
>   kak-tests.9ngbF2V7
> compose
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   backward-search
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   backward-search
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   catch-error-desc
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   catch-error-desc
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   complex-pipe
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   complex-pipe
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   del-empty-line
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   del-empty-line
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   discard-selections-with-itersel
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   discard-selections-with-itersel
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   do-not-run-hooks-added-by-parent
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   do-not-run-hooks-added-by-parent
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   echo-to-file
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   echo-to-file
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   eof-multi-delete
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   eof-multi-delete
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   file-expansion
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   file-expansion
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   history
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   history
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   hook-named-captures
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   hook-named-captures
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   inline-sort
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   inline-sort
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   no-hook-on-unset-option-with-same-parent
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   no-hook-on-unset-option-with-same-parent
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   pipe-at-eof
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   pipe-at-eof
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   select-codepoints
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> Aborted
>   select-codepoints
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
>   select-display-columns
> - { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}] 
> }
> + 
> 

Bug#963384: gnome-desktop3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1

[Lucas Nussbaum]

Source: gnome-desktop3
Version: 3.36.3.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> mkdir -p -m0700 /<>/debian/tmp/run
> NO_AT_BRIDGE=1 XDG_RUNTIME_DIR=/<>/debian/tmp/run 
> G_MESSAGES_DEBUG=all xvfb-run -a dh_auto_test
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test
> [0/1] Running all tests.
> 1/2 wall-clockOK 0.77s
> 2/2 wallclock-reftest FAIL   0.12s (killed by signal 6 SIGABRT)
> 
> Ok: 1   
> Expected Fail:  0   
> Fail:   1   
> Unexpected Pass:0   
> Skipped:0   
> Timeout:0   
> 
> 
> The output from the failed tests:
> 
> 2/2 wallclock-reftest FAIL   0.12s (killed by signal 6 SIGABRT)
> 
> --- command ---
> 07:27:43 G_ENABLE_DIAGNOSTICS='0' 
> G_TEST_BUILDDIR='/<>/obj-x86_64-linux-gnu/tests' 
> G_TEST_SRCDIR='/<>/tests' 
> /<>/obj-x86_64-linux-gnu/tests/wallclock-reftest
> --- Listing only the last 100 lines from a long log. ---
> # GnomeDesktop-DEBUG: is_utf8: FALSE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.307: is_utf8: FALSE
> # GnomeDesktop-DEBUG: ret: Wed May 28  23:59:59
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.307: ret: Wed May 28  23:59:59
> # Date string is: 'Wed May 28  23:59:59'
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> dconf-DEBUG: 07:27:43.307: unwatch_fast: "/org/gnome/desktop/interface/" 
> (active: 0, establishing: 1)
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> dconf-DEBUG: 07:27:43.308: watch_established: "/org/gnome/desktop/interface/" 
> (establishing: 0)
> # Storing test result image at 
> /<>/obj-x86_64-linux-gnu/tests/../meson-logs/C.out.png
> # Storing test result image at 
> /<>/obj-x86_64-linux-gnu/tests/../meson-logs/C.ref.png
> ok 1 /<>/tests/C.ui
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> dconf-DEBUG: 07:27:43.339: watch_fast: "/org/gnome/desktop/interface/" 
> (establishing: 0, active: 0)
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> dconf-DEBUG: 07:27:43.339: watch_established: "/org/gnome/desktop/interface/" 
> (establishing: 1)
> # GnomeDesktop-DEBUG: clock_format: 24h
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: clock_format: 24h
> # GnomeDesktop-DEBUG: show_weekday: FALSE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: show_weekday: FALSE
> # GnomeDesktop-DEBUG: show_full_date: TRUE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: show_full_date: TRUE
> # GnomeDesktop-DEBUG: show_seconds: FALSE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: show_seconds: FALSE
> # GnomeDesktop-DEBUG: format_string: %b %-e_%R
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: format_string: %b %-e_%R
> # GnomeDesktop-DEBUG: no_enspace: %b %-e_%R
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: no_enspace: %b %-e_%R
> # GnomeDesktop-DEBUG: replaced_format: Jun 21_07:27
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: replaced_format: Jun 21_07:27
> # GnomeDesktop-DEBUG: is_utf8: TRUE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: is_utf8: TRUE
> # GnomeDesktop-DEBUG: ret: Jun 21 07‎∶27
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: ret: Jun 21 07‎∶27
> # GnomeDesktop-DEBUG: clock_format: 24h
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: clock_format: 24h
> # GnomeDesktop-DEBUG: show_weekday: TRUE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: show_weekday: TRUE
> # GnomeDesktop-DEBUG: show_full_date: TRUE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: show_full_date: TRUE
> # GnomeDesktop-DEBUG: show_seconds: TRUE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: show_seconds: TRUE
> # GnomeDesktop-DEBUG: format_string: %a %b %-e_%R:%S
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: format_string: %a %b %-e_%R:%S
> # GnomeDesktop-DEBUG: no_enspace: %a %b %-e_%R:%S
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: no_enspace: %a %b %-e_%R:%S
> # GnomeDesktop-DEBUG: replaced_format: Wed May 28_23:59:59
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 

Bug#963404: emoslib: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_MODULE_PATH=/usr/share/ecbuild/cmake -DECBUILD_MACROS_DIR=/usr/share/ecbuild/cmake -DENABLE_BIT_REPRODUCI

[Lucas Nussbaum]

Source: emoslib
Version: 2:4.5.9-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- \
>   -DENABLE_ECCODES=On \
>   -Deccodes_DIR=/usr \
>   -DENABLE_FFTW=ON \
>   -DENABLE_LITTLE_ENDIAN=On \
>   -DCMAKE_INSTALL_PREFIX=/<>/debian/tmp \
>   -DBUILD_SHARED_LIBS=ON \
>   -DENABLE_LIBEMOS_BUILD_SHARED_LIBS=On \
>   -DMCMODEL_FLAGS=-mcmodel=medium \
>   -DBUILD_FLAGS='' \
>   -DFPIC=-fPIC \
>   -DINSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu \
>   -DINTERPOL_TABLES_PATH=/usr/share/emos \
>   -DBUFR_TABLES_PATH=/usr/share/emos/bufrtables \
>   -DTEST_BUFR_TABLES_PATH=/<>/bufrtables
>   cd obj-x86_64-linux-gnu && cmake 
> -DCMAKE_MODULE_PATH=/usr/share/ecbuild/cmake 
> -DECBUILD_MACROS_DIR=/usr/share/ecbuild/cmake -DENABLE_BIT_REPRODUCIBLE=On 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Release -DDISABLE_OS_CHECK=On 
> -DBUILD_SITE=debian -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DENABLE_ECCODES=On -Deccodes_DIR=/usr -DENABLE_FFTW=ON 
> -DENABLE_LITTLE_ENDIAN=On -DCMAKE_INSTALL_PREFIX=/<>/debian/tmp 
> -DBUILD_SHARED_LIBS=ON -DENABLE_LIBEMOS_BUILD_SHARED_LIBS=On 
> -DMCMODEL_FLAGS=-mcmodel=medium -DBUILD_FLAGS= -DFPIC=-fPIC 
> -DINSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu 
> -DINTERPOL_TABLES_PATH=/usr/share/emos 
> -DBUFR_TABLES_PATH=/usr/share/emos/bufrtables 
> -DTEST_BUFR_TABLES_PATH=/<>/bufrtables ..
> -- The C compiler identification is GNU 9.3.0
> -- The CXX compiler identification is GNU 9.3.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- The Fortran compiler identification is GNU 9.3.0
> -- Check for working Fortran compiler: /usr/bin/gfortran
> -- Check for working Fortran compiler: /usr/bin/gfortran  -- works
> -- Detecting Fortran compiler ABI info
> -- Detecting Fortran compiler ABI info - done
> -- Checking whether /usr/bin/gfortran supports Fortran 90
> -- Checking whether /usr/bin/gfortran supports Fortran 90 -- yes
> CMake Error at cmake/ecbuild_system.cmake:38 (include):
>   include could not find load file:
> 
> /usr/share/ecbuild/cmake/VERSION.cmake
> Call Stack (most recent call first):
>   CMakeLists.txt:20 (include)
> 
> 
> CMake Deprecation Warning at cmake/ecbuild_policies.cmake:28 (cmake_policy):
>   The OLD behavior for policy CMP0026 will be removed from a future version
>   of CMake.
> 
>   The cmake-policies(7) manual explains that the OLD behaviors of all
>   policies are deprecated and that a policy should be set to OLD only under
>   specific short-term circumstances.  Projects should be ported to the NEW
>   behavior and not rely on setting a policy to OLD.
> Call Stack (most recent call first):
>   cmake/ecbuild_system.cmake:43 (include)
>   CMakeLists.txt:20 (include)
> 
> 
> CMake Deprecation Warning at cmake/ecbuild_policies.cmake:49 (cmake_policy):
>   The OLD behavior for policy CMP0048 will be removed from a future version
>   of CMake.
> 
>   The cmake-policies(7) manual explains that the OLD behaviors of all
>   policies are deprecated and that a policy should be set to OLD only under
>   specific short-term circumstances.  Projects should be ported to the NEW
>   behavior and not rely on setting a policy to OLD.
> Call Stack (most recent call first):
>   cmake/ecbuild_system.cmake:43 (include)
>   CMakeLists.txt:20 (include)
> 
> 
> -- ecbuild/usr/share/ecbuild/cmake
> -- cmake 3.16.3   /usr/bin/cmake
> -- -
> -- Could NOT find Git (missing: GIT_EXECUTABLE) 
> CMake Deprecation Warning at cmake/ecbuild_policies.cmake:28 (cmake_policy):
>   The OLD behavior for policy CMP0026 will be removed from a future version
>   of CMake.
> 
>   The cmake-policies(7) manual explains that the OLD behaviors of all
>   policies are deprecated and that a policy should be set to OLD only under
>   specific short-term circumstances.  Projects should be ported to the NEW
>   behavior and not rely on setting a policy to OLD.
> Call Stack (most recent call first):
>   cmake/ecbuild_bundle.cmake:10 (include)
>   cmake/ecbuild_system.cmake:217 (include)
>   CMakeLists.txt:20 (include)
> 

Bug#963397: qtcurve: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR

[Lucas Nussbaum]

Source: qtcurve
Version: 1.9-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -DLIB_INSTALL_DIR="/usr/lib/x86_64-linux-gnu" 
> -DQT_QMAKE_EXECUTABLE=/usr/bin/qmake-qt5 -DQTC_QT5_ENABLE_KDE=On 
> -DQTC_QT4_ENABLE_KDE=Off -DQTC_QT4_ENABLE_KWIN=Off -DENABLE_TEST=Off
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DLIB_INSTALL_DIR=/usr/lib/x86_64-linux-gnu 
> -DQT_QMAKE_EXECUTABLE=/usr/bin/qmake-qt5 -DQTC_QT5_ENABLE_KDE=On 
> -DQTC_QT4_ENABLE_KDE=Off -DQTC_QT4_ENABLE_KWIN=Off -DENABLE_TEST=Off ..
> -- The C compiler identification is GNU 9.3.0
> -- The CXX compiler identification is GNU 9.3.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Looking for backtrace
> -- Looking for backtrace - found
> -- Found LibExecinfo: /usr/include  
> -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2") 
> -- Checking for modules 'xcb;x11-xcb'
> --   Found xcb, version 1.14
> --   Found x11-xcb, version 1.6.9
> -- Checking for module 'gtk+-2.0'
> --   Found gtk+-2.0, version 2.24.32
> -- Checking for module 'gtk+-2.0'
> --   Found gtk+-2.0, version 2.24.32
> -- Checking for modules 'cairo;pangocairo'
> --   Found cairo, version 1.16.0
> --   Found pangocairo, version 1.44.7
> -- Found unsuitable Qt version "" from NOTFOUND
> CMake Warning at qt4/CMakeLists.txt:7 (message):
>   Qt4 not found.
> 
> 
> -- Found KF5Archive: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5Archive/KF5ArchiveConfig.cmake (found 
> version "5.70.0") 
> -- Found KF5Config: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5Config/KF5ConfigConfig.cmake (found 
> version "5.70.0") 
> -- Found KF5ConfigWidgets: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5ConfigWidgets/KF5ConfigWidgetsConfig.cmake 
> (found version "5.70.0") 
> -- Could NOT find KF5FrameworkIntegration (missing: 
> KF5FrameworkIntegration_DIR)
> -- Could NOT find KF5FrameworkIntegration: found neither 
> KF5FrameworkIntegrationConfig.cmake nor kf5frameworkintegration-config.cmake 
> -- Found Gettext: /usr/bin/msgmerge (found version "0.19.8.1") 
> -- Found KF5I18n: /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5KDELibs4Support: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5KDELibs4Support/KF5KDELibs4SupportConfig.cmake
>  (found version "5.70.0") 
> -- Found KF5KIO: /usr/lib/x86_64-linux-gnu/cmake/KF5KIO/KF5KIOConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5GuiAddons: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5GuiAddons/KF5GuiAddonsConfig.cmake (found 
> version "5.70.0") 
> -- Found KF5IconThemes: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5IconThemes/KF5IconThemesConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5WidgetsAddons: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5WidgetsAddons/KF5WidgetsAddonsConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5WindowSystem: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5WindowSystem/KF5WindowSystemConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5XmlGui: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5XmlGui/KF5XmlGuiConfig.cmake (found 
> version "5.70.0") 
> CMake Error at 
> /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 
> (message):
>   Could NOT find KF5 (missing: FrameworkIntegration) (found version "5.70.0")
> Call Stack (most recent call first):
>   /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 
> (_FPHSA_FAILURE_MESSAGE)
>   /usr/share/ECM/find-modules/FindKF5.cmake:115 
> (find_package_handle_standard_args)
>   qt5/CMakeLists.txt:68 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you 

Bug#963394: apper: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/

[Lucas Nussbaum]

Source: apper
Version: 1.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -Skde -- -DDEBCONF_SUPPORT=ON -DAPPSTREAM=ON 
> -DAUTOREMOVE=ON -DEDIT_ORIGNS_DESKTOP_NAME=software-properties-kde
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
> -DDEBCONF_SUPPORT=ON -DAPPSTREAM=ON -DAUTOREMOVE=ON 
> -DEDIT_ORIGNS_DESKTOP_NAME=software-properties-kde ..
> -- The C compiler identification is GNU 9.3.0
> -- The CXX compiler identification is GNU 9.3.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) 
> -- Installing in the same prefix as Qt, adopting their path scheme.
> -- Looking for __GLIBC__
> -- Looking for __GLIBC__ - found
> -- Performing Test _OFFT_IS_64BIT
> -- Performing Test _OFFT_IS_64BIT - Success
> -- Performing Test HAVE_DATE_TIME
> -- Performing Test HAVE_DATE_TIME - Success
> -- Could not set up the appstream test. appstreamcli is missing.
> -- Found KF5Config: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5Config/KF5ConfigConfig.cmake (found 
> version "5.70.0") 
> -- Found KF5DocTools: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5DocTools/KF5DocToolsConfig.cmake (found 
> version "5.70.0") 
> -- Found KF5GuiAddons: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5GuiAddons/KF5GuiAddonsConfig.cmake (found 
> version "5.70.0") 
> -- Found Gettext: /usr/bin/msgmerge (found version "0.19.8.1") 
> -- Found KF5I18n: /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5KCMUtils: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5KCMUtils/KF5KCMUtilsConfig.cmake (found 
> version "5.70.0") 
> -- Found KF5DBusAddons: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5DBusAddons/KF5DBusAddonsConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5KIO: /usr/lib/x86_64-linux-gnu/cmake/KF5KIO/KF5KIOConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5Notifications: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5Notifications/KF5NotificationsConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5IconThemes: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5IconThemes/KF5IconThemesConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5: success (found version "5.70.0") found components: Config 
> DocTools GuiAddons I18n KCMUtils DBusAddons KIO Notifications IconThemes 
> -- Building Apper with auto remove: ON
> -- Building Apper with AppStream support: ON
> -- Building Apper with Limba support: OFF
> CMake Error at 
> /usr/share/cmake-3.16/Modules/CMakeFindDependencyMacro.cmake:47 
> (find_package):
>   By not providing "FindKF5TextWidgets.cmake" in CMAKE_MODULE_PATH this
>   project has asked CMake to find a package configuration file provided by
>   "KF5TextWidgets", but CMake did not find one.
> 
>   Could not find a package configuration file provided by "KF5TextWidgets"
>   with any of the following names:
> 
> KF5TextWidgetsConfig.cmake
> kf5textwidgets-config.cmake
> 
>   Add the installation prefix of "KF5TextWidgets" to CMAKE_PREFIX_PATH or set
>   "KF5TextWidgets_DIR" to a directory containing one of the above files.  If
>   "KF5TextWidgets" provides a separate development package or SDK, be sure it
>   has been installed.
> Call Stack (most recent call first):
>   /usr/lib/x86_64-linux-gnu/cmake/DebconfKDE/DebconfKDEConfig.cmake:100 
> (find_dependency)
>   CMakeLists.txt:71 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # 

Bug#963389: ixo-usb-jtag: FTBFS: make[2]: sdcclib: No such file or directory

[Lucas Nussbaum]

Source: ixo-usb-jtag
Version: 0.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>/fx2'
> sdcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -mmcs51 --no-xinit-opt -Ifx2 -mmcs51 
> --no-xinit-opt -I. -Wdate-time -D_FORTIFY_SOURCE=2 -c delay.c -o delay.rel
> at 1: warning 117: unknown compiler option '-g' ignored
> at 1: warning 117: unknown compiler option '-O2' ignored
> at 1: warning 117: unknown compiler option 
> '-fdebug-prefix-map=/<>=.' ignored
> at 1: warning 117: unknown compiler option '-fstack-protector-strong' ignored
> at 1: warning 117: unknown compiler option '-Wformat' ignored
> at 1: warning 117: unknown compiler option '-Werror=format-security' ignored
> at 1: warning 117: unknown compiler option '-Wdate-time' ignored
> sdcclib -a libfx2.lib delay.rel
> make[2]: sdcclib: No such file or directory
> make[2]: *** [Makefile:26: libfx2.lib(delay.rel)] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/ixo-usb-jtag_0.0.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963385: airlift-airline: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project airline: Compilation failure

[Lucas Nussbaum]

Source: airlift-airline
Version: 0.7-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>   mh_patchpoms -plibairline-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   /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
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] -< io.airlift:airline 
> >-
> [INFO] Building airline 0.7
> [INFO] [ jar 
> ]-
> [WARNING] The artifact org.testng:testng:jar:6.x has been relocated to 
> org.testng:testng:jar:debian
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> airline ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /<>/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ airline ---
> [INFO] Changes detected - recompiling the module!
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> [INFO] Compiling 40 source files to /<>/target/classes
> [INFO] 
> /<>/src/main/java/io/airlift/airline/GlobalUsageSummary.java: 
> /<>/src/main/java/io/airlift/airline/GlobalUsageSummary.java 
> uses or overrides a deprecated API.
> [INFO] 
> /<>/src/main/java/io/airlift/airline/GlobalUsageSummary.java: 
> Recompile with -Xlint:deprecation for details.
> [INFO] /<>/src/main/java/io/airlift/airline/Accessor.java: Some 
> input files use unchecked or unsafe operations.
> [INFO] /<>/src/main/java/io/airlift/airline/Accessor.java: 
> Recompile with -Xlint:unchecked for details.
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /<>/src/main/java/io/airlift/airline/model/OptionMetadata.java:[234,48]
>   is not abstract and 
> does not override abstract method 
> test(io.airlift.airline.model.OptionMetadata) in java.util.function.Predicate
> [INFO] 1 error
> [INFO] -
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  1.333 s
> [INFO] Finished at: 2020-06-21T07:32:58Z
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile 
> (default-compile) on project airline: Compilation failure
> [ERROR] 
> /<>/src/main/java/io/airlift/airline/model/OptionMetadata.java:[234,48]
>   is not abstract and 
> does not override abstract method 
> test(io.airlift.airline.model.OptionMetadata) in java.util.function.Predicate
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 

Bug#963399: botch: FTBFS: tools/build-order-from-zero.py:205:27 '...' % ... expected mapping but got sequence

[Lucas Nussbaum]

Source: botch
Version: 0.22-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> # FIXME: add more tests
> #./tests.py
> #OCAMLPATH=/<>/dose/_build ocamlbuild -classic-display 
> -use-ocamlfind -cflags "-w +a-4-9-24" tests.native
> #./tests.native
> pyflakes3 tools/*.py
> tools/build-order-from-zero.py:205:27 '...' % ... expected mapping but got 
> sequence
> make[2]: *** [Makefile:333: test-python] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/botch_0.22-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963406: mdocml: FTBFS: make: echo: No such file or directory

[Lucas Nussbaum]

Source: mdocml
Version: 1.14.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-option-checking --disable-silent-rules 
> --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
> --disable-maintainer-mode --disable-dependency-tracking
> file config.log: writing...
> make: echo: No such file or directory
> make: *** [/tmp/GmjayNyT:2: all] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/mdocml_1.14.4-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#963391: poliastro: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

[Lucas Nussbaum]

Source: poliastro
Version: 0.13.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/cli.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/coordinates.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/bodies.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/integrators.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/util.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/constants.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/spheroid_location.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/examples.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/frames.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/maneuver.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/testing.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> copying src/poliastro/ephem.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro
> creating /<>/.pybuild/cpython3_3.8/build/poliastro/threebody
> copying src/poliastro/threebody/soi.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/threebody
> copying src/poliastro/threebody/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/threebody
> copying src/poliastro/threebody/restricted.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/threebody
> copying src/poliastro/threebody/flybys.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/threebody
> creating /<>/.pybuild/cpython3_3.8/build/poliastro/czml
> copying src/poliastro/czml/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/czml
> copying src/poliastro/czml/extract_czml.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/czml
> copying src/poliastro/czml/utils.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/czml
> creating /<>/.pybuild/cpython3_3.8/build/poliastro/iod
> copying src/poliastro/iod/izzo.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/iod
> copying src/poliastro/iod/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/iod
> copying src/poliastro/iod/vallado.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/iod
> creating /<>/.pybuild/cpython3_3.8/build/poliastro/core
> copying src/poliastro/core/iod.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/core
> copying src/poliastro/core/angles.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/core
> copying src/poliastro/core/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/core
> copying src/poliastro/core/propagation.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/core
> copying src/poliastro/core/elements.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/core
> copying src/poliastro/core/util.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/core
> copying src/poliastro/core/hyper.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/core
> copying src/poliastro/core/stumpff.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/core
> copying src/poliastro/core/_jit.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/core
> copying src/poliastro/core/perturbations.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/core
> creating /<>/.pybuild/cpython3_3.8/build/poliastro/plotting
> copying src/poliastro/plotting/core.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/plotting
> copying src/poliastro/plotting/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/plotting
> copying src/poliastro/plotting/_base.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/plotting
> copying src/poliastro/plotting/misc.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/plotting
> copying src/poliastro/plotting/util.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/plotting
> copying src/poliastro/plotting/static.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/plotting
> copying src/poliastro/plotting/porkchop.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/plotting
> creating /<>/.pybuild/cpython3_3.8/build/poliastro/neos
> copying src/poliastro/neos/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/neos
> copying src/poliastro/neos/dastcom5.py -> 
> /<>/.pybuild/cpython3_3.8/build/poliastro/neos
> creating 

Bug#963401: node-proxyquire: FTBFS: failed tests

[Lucas Nussbaum]

Source: node-proxyquire
Version: 2.1.3+~1.0.1+~1.0.2-9
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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 '/<>'
> eslint --format tap --no-eslintrc --env es6,node --no-inline-config '**/*.js'
> TAP version 13
> 1..59
> ok 1 - /<>/examples/api/api-test.js
> ok 2 - /<>/examples/api/samples/bar.js
> ok 3 - /<>/examples/api/samples/foo.js
> ok 4 - /<>/examples/api/samples/stats.js
> ok 5 - /<>/examples/async/foo-tests.js
> ok 6 - /<>/examples/async/foo.js
> ok 7 - /<>/examples/example-utils.js
> ok 8 - /<>/examples/simple/foo.inlineoverride.test.js
> ok 9 - /<>/examples/simple/foo.js
> ok 10 - /<>/examples/simple/foo.test.js
> ok 11 - /<>/examples/sinon/foo-tests.js
> ok 12 - /<>/examples/sinon/foo.js
> ok 13 - /<>/index.js
> ok 14 - /<>/lib/is.js
> ok 15 - /<>/lib/proxyquire-error.js
> ok 16 - /<>/lib/proxyquire.js
> ok 17 - /<>/test/proxyquire-api.js
> ok 18 - /<>/test/proxyquire-argumentvalidation.js
> ok 19 - /<>/test/proxyquire-cache.js
> ok 20 - /<>/test/proxyquire-compat.js
> ok 21 - /<>/test/proxyquire-extensions.js
> ok 22 - /<>/test/proxyquire-global.js
> ok 23 - /<>/test/proxyquire-independence.js
> ok 24 - /<>/test/proxyquire-non-object.js
> ok 25 - /<>/test/proxyquire-notexisting.js
> ok 26 - /<>/test/proxyquire-relative-paths.js
> ok 27 - /<>/test/proxyquire-remove.js
> ok 28 - /<>/test/proxyquire-sub-dependencies.js
> ok 29 - /<>/test/proxyquire.js
> ok 30 - /<>/test/samples/bar.js
> ok 31 - /<>/test/samples/boof.js
> ok 32 - /<>/test/samples/cache/bar.js
> ok 33 - /<>/test/samples/cache/foo.js
> ok 34 - /<>/test/samples/extensions.js
> ok 35 - /<>/test/samples/foo-singleton.js
> ok 36 - /<>/test/samples/foo.js
> ok 37 - /<>/test/samples/fooarray.js
> ok 38 - /<>/test/samples/foobool.js
> ok 39 - /<>/test/samples/foonum.js
> ok 40 - /<>/test/samples/global/bar.js
> ok 41 - /<>/test/samples/global/baz.js
> ok 42 - /<>/test/samples/global/foo-deferred.js
> ok 43 - /<>/test/samples/global/foo.js
> ok 44 - /<>/test/samples/no-call-thru-test/index.js
> ok 45 - /<>/test/samples/no-call-thru-test/required.js
> ok 46 - /<>/test/samples/notexisting/foo-relative.js
> ok 47 - /<>/test/samples/notexisting/foo.js
> ok 48 - /<>/test/samples/relative-paths/a/index.js
> ok 49 - /<>/test/samples/relative-paths/a/util.js
> ok 50 - /<>/test/samples/relative-paths/b/index.js
> ok 51 - /<>/test/samples/relative-paths/b/util.js
> ok 52 - /<>/test/samples/stats.js
> ok 53 - /<>/test/samples/sub-dependencies/bar.js
> ok 54 - /<>/test/samples/sub-dependencies/baz.js
> ok 55 - /<>/test/samples/sub-dependencies/foo.js
> ok 56 - /<>/Xerror/index.js
> ok 57 - /<>/Xerror/test.js
> ok 58 - /<>/Xkeys/index.js
> ok 59 - /<>/Xkeys/test.js
> 
> tape Xerror/test.js Xkeys/test.js
> TAP version 13
> # (anonymous)
> not ok 1 should be equal
>   ---
> operator: equal
> expected: |-
>   'Cannot find module \'foo\'\nRequire stack:\n- 
> /<>/Xerror/test.js\n- /usr/lib/nodejs/tape/bin/tape'
> actual: |-
>   'Cannot find module \'foo\''
> at: Test. (/<>/Xerror/test.js:12:7)
> stack: |-
>   Error: should be equal
>   at Test.assert [as _assert] 
> (/usr/lib/nodejs/tape/lib/test.js:235:54)
>   at Test.bound [as _assert] (/usr/lib/nodejs/tape/lib/test.js:87:32)
>   at Test.equal (/usr/lib/nodejs/tape/lib/test.js:395:10)
>   at Test.bound [as equal] (/usr/lib/nodejs/tape/lib/test.js:87:32)
>   at Test. (/<>/Xerror/test.js:12:7)
>   at Test.bound [as _cb] (/usr/lib/nodejs/tape/lib/test.js:87:32)
>   at Test.run (/usr/lib/nodejs/tape/lib/test.js:106:10)
>   at Test.bound [as run] (/usr/lib/nodejs/tape/lib/test.js:87:32)
>   at Immediate.next [as _onImmediate] 
> (/usr/lib/nodejs/tape/lib/results.js:71:15)
>   at processImmediate (internal/timers.js:456:21)
>   ...
> ok 2 should be equal
> # fill-keys
> # es5
> ok 3 simple deep equality
> ok 4 mutates dest
> ok 5 fills prototype
> ok 6 both
> ok 7 source undefined
> ok 8 dest undefined
> ok 9 destination obj has no proto
> ok 10 copies descriptor
> # es3
> ok 11 simple deep equality
> ok 12 mutates dest
> ok 13 fills prototype
> ok 14 both
> ok 15 source undefined
> ok 16 dest undefined
> ok 17 destination obj has no proto
> # fn with no prototype
> ok 18 should not throw
> 
> 1..18
> # tests 18
> # pass  17
> # fail  1
> 
> make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/06/20/node-proxyquire_2.1.3+~1.0.1+~1.0.2-9_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and 

Bug#963393: harvid: FTBFS: Makefile:20: *** "libjpeg is required - install libjpeg-dev, libjpeg8-dev or libjpeg62-dev". Stop.

[Lucas Nussbaum]

Source: harvid
Version: 0.8.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> ar cru libharvid.a decoder_ctrl.o ffdecoder.o frame_cache.o image_cache.o 
> timecode.o vinfo.o
> ar: `u' modifier ignored since `D' is the default (see `U')
> ranlib libharvid.a
> make[3]: Leaving directory '/<>/libharvid'
> make -C src 
> make[3]: Entering directory '/<>/src'
> Makefile:20: *** "libjpeg is required - install libjpeg-dev, libjpeg8-dev or 
> libjpeg62-dev".  Stop.
> make[3]: Leaving directory '/<>/src'
> make[2]: *** [Makefile:9: src] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/harvid_0.8.3-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.