Processed: tagging 963420
Processing commands for cont...@bugs.debian.org: > # > https://salsa.debian.org/debian/zsh/-/commit/d4dedd992a9fcfce3c34a8155425d5d2a5821d77 > tags 963420 + pending Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 963420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963274: marked as done (vkd3d: FTBFS: libs/vkd3d/vkd3d_private.h:680:54: error: ‘VK_PIPELINE_BIND_POINT_RANGE_SIZE’ undeclared here (not in a function); did you mean ‘VK_PIPELINE_BIND_POINT_MAX_EN
Your message dated Mon, 22 Jun 2020 03:18:39 + with message-id and subject line Bug#963274: fixed in vkd3d 1.1-5 has caused the Debian Bug report #963274, regarding vkd3d: FTBFS: libs/vkd3d/vkd3d_private.h:680:54: error: ‘VK_PIPELINE_BIND_POINT_RANGE_SIZE’ undeclared here (not in a function); did you mean ‘VK_PIPELINE_BIND_POINT_MAX_ENUM’? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vkd3d Version: 1.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): > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I./include -I./include -I./include/dummy -I./include/private -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -pipe -std=c99 -Wdeclaration-after-statement > -Wmissing-prototypes -Wunused-but-set-parameter -Wvla -Wl,--no-undefined -g > -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o libs/vkd3d/command.lo libs/vkd3d/command.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./include -I./include > -I./include/dummy -I./include/private -Wdate-time -D_FORTIFY_SOURCE=2 -Wall > -pipe -std=c99 -Wdeclaration-after-statement -Wmissing-prototypes > -Wunused-but-set-parameter -Wvla -Wl,--no-undefined -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c libs/vkd3d/command.c -fPIC -DPIC -o > libs/vkd3d/.libs/command.o > In file included from libs/vkd3d/command.c:20: > libs/vkd3d/vkd3d_private.h:680:54: error: ‘VK_PIPELINE_BIND_POINT_RANGE_SIZE’ > undeclared here (not in a function); did you mean > ‘VK_PIPELINE_BIND_POINT_MAX_ENUM’? > 680 | struct vkd3d_pipeline_bindings > pipeline_bindings[VK_PIPELINE_BIND_POINT_RANGE_SIZE]; > | > ^ > | > VK_PIPELINE_BIND_POINT_MAX_ENUM > libs/vkd3d/command.c: In function ‘d3d12_command_list_prepare_descriptors’: > libs/vkd3d/command.c:2092:29: warning: parameter ‘bind_point’ set but not > used [-Wunused-but-set-parameter] > 2092 | VkPipelineBindPoint bind_point) > | ^~ > libs/vkd3d/command.c: In function ‘d3d12_command_list_set_root_signature’: > libs/vkd3d/command.c:3228:29: warning: parameter ‘bind_point’ set but not > used [-Wunused-but-set-parameter] > 3228 | VkPipelineBindPoint bind_point, const struct > d3d12_root_signature *root_signature) > | ^~ > libs/vkd3d/command.c: In function ‘d3d12_command_list_set_descriptor_table’: > libs/vkd3d/command.c:3262:29: warning: parameter ‘bind_point’ set but not > used [-Wunused-but-set-parameter] > 3262 | VkPipelineBindPoint bind_point, unsigned int index, > D3D12_GPU_DESCRIPTOR_HANDLE base_descriptor) > | ^~ > libs/vkd3d/command.c: In function ‘d3d12_command_list_set_root_constants’: > libs/vkd3d/command.c:3299:29: warning: parameter ‘bind_point’ set but not > used [-Wunused-but-set-parameter] > 3299 | VkPipelineBindPoint bind_point, unsigned int index, unsigned > int offset, > | ^~ > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I./include -I./include -I./include/dummy -I./include/private -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -pipe -std=c99 -Wdeclaration-after-statement > -Wmissing-prototypes -Wunused-but-set-parameter -Wvla -Wl,--no-undefined -g > -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o libs/vkd3d/device.lo libs/vkd3d/device.c > make[3]: *** [Makefile:1089: libs/vkd3d/command.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/06/20/vkd3d_1.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. --- End Message --- --- Begin Message --- Source: vkd3d Source-Version: 1.1-5 Done: Michael Gilbert We
Bug#963439: marked as done (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:)
Your message dated Mon, 22 Jun 2020 03:03:28 + with message-id and subject line Bug#963439: fixed in ncbi-entrez-direct 13.1.20200102+dfsg-1 has caused the Debian Bug report #963439, regarding 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: to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 >
Processed: Re: Bug#963176: Unable to run any programs due to kernelbase.dll failed to initialize.
Processing control commands: > tag -1 moreinfo Bug #963176 [wine-development] Unable to run any programs due to kernelbase.dll failed to initialize. Added tag(s) moreinfo. > severity -1 important Bug #963176 [wine-development] Unable to run any programs due to kernelbase.dll failed to initialize. Severity set to 'important' from 'grave' -- 963176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963176: Unable to run any programs due to kernelbase.dll failed to initialize.
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#963341: cfengine3: New cfengine 3.15.2 package is broken and non-functional
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
> 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#963341: cfengine3: New cfengine 3.15.2 package is broken and non-functional
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#963287: marked as done (notmuch: FTBFS: grotty: ():1662: fatal error: output error)
Your message dated Sun, 21 Jun 2020 20:50:44 -0300 with message-id <877dw0rnaj@tethera.net> and subject line Re: Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error has caused the Debian Bug report #963287, regarding notmuch: FTBFS: grotty: ():1662: fatal error: output error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: notmuch Version: 0.29.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): > make[2]: Entering directory '/<>/bindings/ruby' > linking shared-object notmuch.so > make[2]: Leaving directory '/<>/bindings/ruby' > CC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security test/parse-time.o > CC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security test/smtp-dummy.o > CXX -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security test/symbol-test.o > CXX -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security test/make-db-version.o > CXX -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security test/ghost-report.o > CC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security test/message-id-parse.o > CC test/arg-test > CC test/hex-xcode > CXX test/random-corpus > CC test/parse-time > CC test/smtp-dummy > CC test/message-id-parse > CXX test/ghost-report > CXX test/symbol-test > CXX test/make-db-version > Use "make V=1" to see the details for passing and known broken tests. > INFO: using 2m timeout for tests > > T010-help-test: Testing online help > FAIL notmuch --help tag > notmuch --help tag > man: can't execute col: No such file or directory > grotty: ():1662: fatal error: output error > man: command exited with status 1: (cd /<>/doc/_build/man && > /usr/lib/man-db/zsoelim) | (cd /<>/doc/_build/man && > /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE) | (cd > /<>/doc/_build/man && preconv -e UTF-8) | (cd > /<>/doc/_build/man && tbl) | (cd /<>/doc/_build/man > && nroff -mandoc -Tascii) > FAIL notmuch help tag > notmuch help tag > man: can't execute col: No such file or directory > grotty: ():1662: fatal error: output error > man: command exited with status 1: (cd /<>/doc/_build/man && > /usr/lib/man-db/zsoelim) | (cd /<>/doc/_build/man && > /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE) | (cd > /<>/doc/_build/man && preconv -e UTF-8) | (cd > /<>/doc/_build/man && tbl) | (cd /<>/doc/_build/man > && nroff -mandoc -Tascii) > missing prerequisites: database-v1.tar.xz - fetch with 'make > download-test-databases' > SKIP all tests in T530-upgrade > > T590-thread-breakage: Testing thread breakage during reindexing > BROKEN No ghosts should remain after deletion of second message > > T670-duplicate-mid: Testing duplicate message ids > BROKEN First subject preserved in notmuch-show (json) > BROKEN Regexp search for second subject > > Notmuch test suite complete. > 1096/1101 tests passed. > 3 broken tests failed as expected. > 2 tests failed. > make[1]: *** [test/Makefile.local:69: test] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/06/20/notmuch_0.29.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. --- End Message --- --- Begin Message --- Lucas Nussbaum writes: > Source: notmuch > Version: 0.29.3-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200620 ftbfs-bullseye > >> >> T010-help-test: Testing online help >> FAIL notmuch --help tag >> notmuch --help tag >> man: can't execute col: No such file or directory >> grotty: ():1662: fatal error: output error >>
Bug#963316: marked as done (sitecopy: FTBFS: configure: error: could not use external neon library)
Your message dated Sun, 21 Jun 2020 23:49:27 + with message-id and subject line Bug#963316: fixed in sitecopy 1:0.16.6-8 has caused the Debian Bug report #963316, regarding sitecopy: FTBFS: configure: error: could not use external neon library to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sitecopy Version: 1:0.16.6-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): > checking for ar... /usr/bin/ar > checking for ranlib... /usr/bin/ranlib > checking for neon-config... /usr/bin/neon-config > checking linking against neon... yes > configure: incompatible neon library version 0.31.1: wanted 0.24 25 26 27 28 > 29 30 > configure: error: could not use external neon library > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2020/06/20/sitecopy_0.16.6-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. --- End Message --- --- Begin Message --- Source: sitecopy Source-Version: 1:0.16.6-8 Done: Christian Marillat We believe that the bug you reported is fixed in the latest version of sitecopy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Marillat (supplier of updated sitecopy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Jun 2020 01:41:42 +0200 Source: sitecopy Architecture: source Version: 1:0.16.6-8 Distribution: unstable Urgency: medium Maintainer: Christian Marillat Changed-By: Christian Marillat Closes: 963316 Changes: sitecopy (1:0.16.6-8) unstable; urgency=medium . * Add neon 31 as suported version (Closes: #963316) Checksums-Sha1: 7400c959011692a796d120d75e99228240b65a97 1791 sitecopy_0.16.6-8.dsc f7c6422cee0721273de2ae30a0f35bbe36f4ddcb 45028 sitecopy_0.16.6-8.debian.tar.xz 8683665c0d8917fcf81eaaf6aa5897a0edf3554a 6167 sitecopy_0.16.6-8_source.buildinfo Checksums-Sha256: a6bc05cd83287e5d1b5c74829587330470fc108d739867c4c1b2d47e0b79 1791 sitecopy_0.16.6-8.dsc 3cbde96106fde7042eaa039f294f0bac84cc2e3d2819cdca2ce519848d30a65b 45028 sitecopy_0.16.6-8.debian.tar.xz cca2e1f44b3049328472a036c1edcfa4fe5ab214b67b0a47358d6d519ec40d7e 6167 sitecopy_0.16.6-8_source.buildinfo Files: 2f721e1f3ae483015a5dff36df89ca9a 1791 web extra sitecopy_0.16.6-8.dsc 887913ea4b3ccc40cf2cd8327388fb2a 45028 web extra sitecopy_0.16.6-8.debian.tar.xz 16ed2f2f8fb5410bf71782d40c0a6aa4 6167 web extra sitecopy_0.16.6-8_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEpAH/mTaPofmBUt51XICMK2VVgRcFAl7v8S0ACgkQXICMK2VV gRcrKw/9Fz9xqldbx0yuL7gqPa1OCNPtpCfd3tFDA4fSKvcu2aqpDahD+tNDcQsz h350aDgC5nh3lhSotNgABQK7d7ceQ3N6N/r3govqTajdXIixZKWtx1FAPuLvlJZd qzG/9Bgn4yIr2tH7XYGvNrnlDiT4kmGH5HfD5RUcO3YkGykYL5ekNQjBiQ53ZFbl NyQ3GNR+okipu33476nDg2rxtkocmzyZU5pkEo011TS4Q67O8x9lci20ByY8ZasM MVyRb7/zncxk4ElnPq0Rz+B2NrYkzQSa3jBdSDIB4DICwW6bslcsSHw1608EK3dM beSfhdGcIcz6cRfw09gXbhCZXYzVU6uvZMENrjmMuUfxiNBoAN+58H6btlKqQfWf wX9deTdhutHzzuUbDnvM5quZCTtNne0QWY3y31OmBAzqTQLpjwO8pHC866rtXMQF CTF3HbwARlJPox20IYtkkT31hvTkaY1Nr41iFqkuetXKyFdQBEmXqVu27oMQzkYk WtDCSg3MQFYX+sOBhK+N6ntea9giJ97eSE2fRHv5UXOrhG8cYv1pIkBreX3oakFm PxLMh5Uv5u6zT/PG7pwDxO4JTxoE1HAvb1D6tm8XjYV6g48yhCPseg8HSls00dSA JAAjLBgaGlBBZcy5MQOestgYQzTtE8SSeBBGJGX/67cBJeAUzm0= =ZMvE -END PGP SIGNATURE End Message ---
Bug#963366: marked as done (budgie-desktop: FTBFS: dh_installman: error: Could not determine section for ./debian/budgie-desktop-settings.1)
Your message dated Sun, 21 Jun 2020 22:48:30 + with message-id and subject line Bug#963366: fixed in budgie-desktop 10.5.1-8 has caused the Debian Bug report #963366, regarding budgie-desktop: FTBFS: dh_installman: error: Could not determine section for ./debian/budgie-desktop-settings.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: budgie-desktop Version: 10.5.1-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[1]: Entering directory '/<>' > dh_installchangelogs debian/changelog-announcement.txt > install -p -m0644 debian/changelog > debian/budgie-desktop-doc/usr/share/doc/budgie-desktop-doc/changelog.Debian > install -p -m0644 debian/changelog-announcement.txt > debian/budgie-desktop-doc/usr/share/doc/budgie-desktop-doc/changelog > install -p -m0644 debian/changelog > debian/gir1.2-budgie-1.0/usr/share/doc/gir1.2-budgie-1.0/changelog.Debian > install -p -m0644 debian/changelog-announcement.txt > debian/gir1.2-budgie-1.0/usr/share/doc/gir1.2-budgie-1.0/changelog > install -p -m0644 debian/changelog > debian/libbudgie-plugin0/usr/share/doc/libbudgie-plugin0/changelog.Debian > install -p -m0644 debian/changelog-announcement.txt > debian/libbudgie-plugin0/usr/share/doc/libbudgie-plugin0/changelog > install -p -m0644 debian/changelog > debian/libbudgie-private0/usr/share/doc/libbudgie-private0/changelog.Debian > install -p -m0644 debian/changelog-announcement.txt > debian/libbudgie-private0/usr/share/doc/libbudgie-private0/changelog > install -p -m0644 debian/changelog > debian/libbudgietheme0/usr/share/doc/libbudgietheme0/changelog.Debian > install -p -m0644 debian/changelog-announcement.txt > debian/libbudgietheme0/usr/share/doc/libbudgietheme0/changelog > install -p -m0644 debian/changelog > debian/libraven0/usr/share/doc/libraven0/changelog.Debian > install -p -m0644 debian/changelog-announcement.txt > debian/libraven0/usr/share/doc/libraven0/changelog > install -p -m0644 debian/changelog > debian/budgie-core/usr/share/doc/budgie-core/changelog.Debian > install -p -m0644 debian/changelog-announcement.txt > debian/budgie-core/usr/share/doc/budgie-core/changelog > install -p -m0644 debian/changelog > debian/budgie-core-dev/usr/share/doc/budgie-core-dev/changelog.Debian > install -p -m0644 debian/changelog-announcement.txt > debian/budgie-core-dev/usr/share/doc/budgie-core-dev/changelog > install -p -m0644 debian/changelog > debian/budgie-desktop/usr/share/doc/budgie-desktop/changelog.Debian > install -p -m0644 debian/changelog-announcement.txt > debian/budgie-desktop/usr/share/doc/budgie-desktop/changelog > make[1]: Leaving directory '/<>' >dh_installman > dh_installman: warning: Section for ./debian/budgie-desktop-settings.1 is > computed as "22", which is not a valid section > dh_installman: error: Could not determine section for > ./debian/budgie-desktop-settings.1 > install -d debian/budgie-core/usr/share/man/man1/ > install -p -m0644 ./debian/budgie-daemon.1 > debian/budgie-core/usr/share/man/man1/budgie-daemon.1 > dh_installman: error: Aborting due to earlier error > make: *** [debian/rules:7: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/06/20/budgie-desktop_10.5.1-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. --- End Message --- --- Begin Message --- Source: budgie-desktop Source-Version: 10.5.1-8 Done: David Mohammed We believe that the bug you reported is fixed in the latest version of budgie-desktop, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution
Bug#963357: marked as pending in libtest-redisserver-perl
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
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
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
Processed: unmerging 963427
Processing commands for cont...@bugs.debian.org: > unmerge 963427 Bug #963427 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963327 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963349 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963350 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963353 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963355 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963359 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963361 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963365 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963372 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963375 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963376 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963377 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963378 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963383 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963395 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963403 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963413 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963414 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963420 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963442 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963448 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963451 [bsdmainutils] bsdmainutils must depend on bsdextrautils Disconnected #963427 from all other report(s). > thanks Stopping processing here. Please contact me if you need assistance. -- 963327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963327 963349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963349 963350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963350 963353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963353 963355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963355 963359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963359 963361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963361 963365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963365 963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372 963375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963375 963376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963376 963377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963377 963378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963378 963383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963383 963395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963395 963403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963403 963413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963413 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 963420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963420 963427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963427 963442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963442 963448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963448 963451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963420: [Pkg-zsh-devel] Processed: Merge duplicates
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#963427: marked as done (bsdmainutils must depend on bsdextrautils)
Your message dated Sun, 21 Jun 2020 22:05:03 +
with message-id
and subject line Bug#963427: fixed in ding 1.8.1-9
has caused the Debian Bug report #963427,
regarding bsdmainutils must depend on bsdextrautils
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
963427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
Source: ding
Source-Version: 1.8.1-9
Done: Roland Rosenfeld
We believe that the bug you reported is fixed in the latest version of
ding, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Roland Rosenfeld (supplier of updated ding package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 21 Jun 2020 23:38:56 +0200
Source: ding
Architecture: source
Version: 1.8.1-9
Distribution: unstable
Urgency: medium
Maintainer: Roland Rosenfeld
Changed-By: Roland Rosenfeld
Closes: 939603 963427
Changes:
ding (1.8.1-9) unstable; urgency=medium
.
* 26_Mannschaftskollegin: Fix two typos in Mannschaftskollegin(nen)
(Closes: #939603).
* Update standards version to 4.5.0, no changes needed.
* Rename gitlab-ci.yml to salsa-ci.yml.
* Update debian/watch to version=4 and optimize regex.
* Build-Depends-Indep: bsdextrautils (>= 2.35.2-3)|bsdmainutils (<<12.1.1)
because col was moved (Closes: #963427).
* Update to debhelper 13.
Checksums-Sha1:
e00d3609d88a931631d95069a51a7d4351d789f1 2110 ding_1.8.1-9.dsc
6e994057e0f0c7721210735f4961ddfb46779d00 51496 ding_1.8.1-9.debian.tar.xz
6a1f11b7bc3484ba05817b97ee834689e2f00263 6443 ding_1.8.1-9_source.buildinfo
Checksums-Sha256:
041c66d53faa78c6333e6b9af49410eca0c3ec0eb04e496b71c3dd4ceea92e74 2110
ding_1.8.1-9.dsc
c8dab90f57a7eec3b41ffdf9aba0043feab13a38c29f221c77fd0da5adc90713 51496
ding_1.8.1-9.debian.tar.xz
0f71b76fc5948c38f5ca9bd649c76964dc36ecf8e53321360b37260de8676b65 6443
ding_1.8.1-9_source.buildinfo
Files:
ef067a985c1000f35cd987c2a6969b64 2110 text optional ding_1.8.1-9.dsc
056615ae0024e863731523128ffe886e 51496 text optional
Processed: Re: [Pkg-zsh-devel] Processed: Merge duplicates
Processing control commands: > unmerge 963420 Bug #963420 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963327 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963349 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963350 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963353 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963355 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963359 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963361 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963365 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963372 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963375 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963376 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963377 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963378 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963383 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963395 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963403 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963413 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963414 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963442 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963448 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963451 [bsdmainutils] bsdmainutils must depend on bsdextrautils Disconnected #963420 from all other report(s). > reassign 963420 src:zsh Bug #963420 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug reassigned from package 'bsdmainutils' to 'src:zsh'. No longer marked as found in versions bsdmainutils/12.1.1. Ignoring request to alter fixed versions of bug #963420 to the same values previously set > retitle 963420 zsh: FTBFS: sh: 1: colcrt: not found Bug #963420 [src:zsh] bsdmainutils must depend on bsdextrautils Changed Bug title to 'zsh: FTBFS: sh: 1: colcrt: not found' from 'bsdmainutils must depend on bsdextrautils'. > found 963420 5.8-4 Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found Marked as found in versions zsh/5.8-4. > affects 963420 = Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found Removed indication that 963420 affects src:ding, src:man-db, src:sendmail, src:xterm, src:pbuilder, src:mcl, src:mp3info, src:zsh, src:conky, src:libstorj, src:xcolorsel, src:wiki2beamer, src:console-setup, src:loadlin, src:hub, src:vmem, src:libdap, src:calc, src:latex2rtf, src:slashem, src:glhack, src:ocp, and src:apcupsd -- 963327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963327 963349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963349 963350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963350 963353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963353 963355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963355 963359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963359 963361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963361 963365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963365 963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372 963375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963375 963376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963376 963377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963377 963378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963378 963383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963383 963395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963395 963403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963403 963413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963413 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 963420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963420 963442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963442 963448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963448 963451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 963327 to bsdmainutils must depend on bsdextrautils
Processing commands for cont...@bugs.debian.org: > retitle 963327 bsdmainutils must depend on bsdextrautils Bug #963327 [bsdmainutils] bsdmainutils needs Breaks on util-linux versions without the tools removed in 12.1.1 Bug #963349 [bsdmainutils] libdap: FTBFS: /bin/bash: col: command not found Bug #963350 [bsdmainutils] slashem: FTBFS: /bin/sh: 1: col: not found Bug #963353 [bsdmainutils] mcl: FTBFS: /bin/bash: col: command not found Bug #963355 [bsdmainutils] ocp: FTBFS: /bin/sh: 1: hexdump: not found Bug #963359 [bsdmainutils] glhack: FTBFS: /bin/sh: 1: col: not found Bug #963361 [bsdmainutils] hub: FTBFS: /bin/sh: 1: col: not found Bug #963365 [bsdmainutils] sendmail: FTBFS: /bin/sh: 1: ul: not found Bug #963372 [bsdmainutils] console-setup: FTBFS: /bin/sh: 1: col: not found Bug #963375 [bsdmainutils] conky: FTBFS: /usr/bin/man: can't execute col: No such file or directory Bug #963376 [bsdmainutils] apcupsd: FTBFS: man: can't execute col: No such file or directory Bug #963377 [bsdmainutils] xterm: FTBFS: /bin/sh: 1: col: not found Bug #963378 [bsdmainutils] xcolorsel: FTBFS: /bin/sh: 1: col: not found Bug #963383 [bsdmainutils] calc: FTBFS: /bin/sh: 5: col: not found Bug #963395 [bsdmainutils] man-db: FTBFS: dh_auto_test: error: cd debian/build && make -j4 check VERBOSE=1 returned exit code 2 Bug #963403 [bsdmainutils] mp3info: FTBFS: /bin/sh: 1: col: not found Bug #963413 [bsdmainutils] vmem: FTBFS: man: can't execute col: No such file or directory Bug #963414 [bsdmainutils] latex2rtf: FTBFS: man: can't execute col: No such file or directory Bug #963420 [bsdmainutils] zsh: FTBFS: sh: 1: colcrt: not found Bug #963427 [bsdmainutils] ding: FTBFS: man: can't execute col: No such file or directory Bug #963442 [bsdmainutils] pbuilder: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2 Bug #963448 [bsdmainutils] wiki2beamer: FTBFS: man: can't execute col: No such file or directory Bug #963451 [bsdmainutils] loadlin: FTBFS: /bin/sh: 1: hexdump: not found Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'bsdmainutils needs Breaks on util-linux versions without the tools removed in 12.1.1'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'libdap: FTBFS: /bin/bash: col: command not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'slashem: FTBFS: /bin/sh: 1: col: not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'mcl: FTBFS: /bin/bash: col: command not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'ocp: FTBFS: /bin/sh: 1: hexdump: not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'glhack: FTBFS: /bin/sh: 1: col: not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'hub: FTBFS: /bin/sh: 1: col: not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'sendmail: FTBFS: /bin/sh: 1: ul: not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'console-setup: FTBFS: /bin/sh: 1: col: not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'conky: FTBFS: /usr/bin/man: can't execute col: No such file or directory'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'apcupsd: FTBFS: man: can't execute col: No such file or directory'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'xterm: FTBFS: /bin/sh: 1: col: not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'xcolorsel: FTBFS: /bin/sh: 1: col: not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'calc: FTBFS: /bin/sh: 5: col: not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'man-db: FTBFS: dh_auto_test: error: cd debian/build && make -j4 check VERBOSE=1 returned exit code 2'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'mp3info: FTBFS: /bin/sh: 1: col: not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'vmem: FTBFS: man: can't execute col: No such file or directory'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'latex2rtf: FTBFS: man: can't execute col: No such file or directory'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'zsh: FTBFS: sh: 1: colcrt: not found'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'ding: FTBFS: man: can't execute col: No such file or directory'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'pbuilder: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'wiki2beamer: FTBFS: man: can't execute col: No such file or directory'. Changed Bug title to 'bsdmainutils must depend on bsdextrautils' from 'loadlin: FTBFS: /bin/sh: 1: hexdump: not found'. > thanks
Bug#962104: marked as done (python-pweave fails it's autopkg tests)
Your message dated Sun, 21 Jun 2020 21:48:47 + with message-id and subject line Bug#962104: fixed in python-pweave 0.25-3 has caused the Debian Bug report #962104, regarding python-pweave fails it's autopkg tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pweave Version: 0.25-2 Severity: serious Tags: sid bullseye python-pweave fails it's autopkg tests [...] Reading state information... E: Unable to locate package texlive-generic-extra command1 FAIL badpkg blame: python-pweave badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. autopkgtest [19:18:27]: summary command1 FAIL badpkg blame: python-pweave --- End Message --- --- Begin Message --- Source: python-pweave Source-Version: 0.25-3 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of python-pweave, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated python-pweave package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 21 Jun 2020 23:17:12 +0530 Source: python-pweave Architecture: source Version: 0.25-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Nilesh Patra Closes: 962104 Changes: python-pweave (0.25-3) unstable; urgency=medium . * Team Upload. * Update Test Depends (Closes: #962104) * compat version:13 Checksums-Sha1: 88a8e03e95975e97050294232e674972f995be4b 2203 python-pweave_0.25-3.dsc d604897f58b40b72bbac2ba8f457bf252ea152c0 6540 python-pweave_0.25-3.debian.tar.xz 294fa35a9121756df17e582942422e5bbb51a106 6142 python-pweave_0.25-3_source.buildinfo Checksums-Sha256: d5101a828e806cc71c7e0f241359ce9f34e5a98c36119dde705e1cf8ad5ebc84 2203 python-pweave_0.25-3.dsc d41b0ffc1e0c91395d9df34cd7793d25fea454f4672318e17d2b45ec3d76940b 6540 python-pweave_0.25-3.debian.tar.xz 36dd57588c2ccd7ae5e25aa9ca64b45766a3ab993deb7a399d2fbbbe7bdfd4ec 6142 python-pweave_0.25-3_source.buildinfo Files: 78182225bf197d29e9e0b556ff1e4d35 2203 python optional python-pweave_0.25-3.dsc 38ea8f3c3dc5166bd5ee72b9fa6032d7 6540 python optional python-pweave_0.25-3.debian.tar.xz 77a17e99922445b68b00918e2512dbd3 6142 python optional python-pweave_0.25-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl7v0osACgkQ0+Fzg8+n /wbCRQ//fDmFUL1VpIvqzncd0HE4UfaVbEh9C6kNlFagjPo2Z/CT8OAtA5RMs+WX 0Cjgcn9wRynrH2OA7TzB76ZWgW7L2+tKUm9WjQMqd+BxbhBcKumg4s8qGND1QE9b S2+OZX7BTbJo2U97+QDBMCw2Y1r/viE3tMtLl0/fqv1l+ZLlpu4BygLp1y8v7PfF 1cYJo/5Vjzwhjat/Va3gYLP9weNcD0hoRxYoQLkDjAq/XazBSA+dqnSbu7sMTtRz Cr5IK8LclnDmaugmJh91/ZQnauY41VlFCDa/j5gWHulumvgSjXv3d4TCuWArQ4+0 vDOijmM68SyNk9j059grg55ri1Tzq9yL8VKm22OiH99goEWugwenqbcACOnNAQLd 4P79eZ2t9+hMAau8OeMOCHIzvtGB3zBmgvpMdaQ4C06+uKxA3ymA0ALbDW6Ke36o 7eF+yDTExypdaEKnBj0el462MjBTfeaepkqZjmVJghwp3SlXAKAl9zDvU3EfBln8 ydiL2TKAlErPMwP4D6WkFCgpazKCOfudze9C2Osf9UC5zuD7w1LV8bpbDakLy+VH 2dy1kgVbX/zajfinmUaWA3xRZKqbgfmVtlliBofYDeyXmfv+ronjw/XNfuiNQCXH ANDYXoSbrZuhurUY+Kk5E4vUDvgQWcTOJ90hm7vNgjqVU70a4To= =BHRk -END PGP SIGNATURE End Message ---
Processed: forcibly merging 963327 963349 963350 963353 963355 963359 963361 963365 963372 963375 963376 963377 963378 963383 963395 963403 963413 963414 963420 963427 963442 963448 963451
Processing commands for cont...@bugs.debian.org:
> forcemerge 963327 963349 963350 963353 963355 963359 963361 963365 963372
> 963375 963376 963377 963378 963383 963395 963403 963413 963414 963420 963427
> 963442 963448 963451
Bug #963327 [bsdmainutils] bsdmainutils needs Breaks on util-linux versions
without the tools removed in 12.1.1
Bug #963377 [bsdmainutils] xterm: FTBFS: /bin/sh: 1: col: not found
Added indication that 963377 affects
src:pbuilder,src:glhack,src:libstorj,src:vmem,src:apcupsd,src:zsh,src:hub,src:mcl,src:mp3info,src:man-db,src:xterm,src:slashem,src:sendmail,src:conky,src:wiki2beamer,src:latex2rtf,src:loadlin,src:xcolorsel,src:console-setup,src:ding,src:libdap,src:calc,src:ocp
Added tag(s) confirmed.
Bug #963376 [bsdmainutils] apcupsd: FTBFS: man: can't execute col: No such file
or directory
Added indication that 963376 affects
src:pbuilder,src:glhack,src:libstorj,src:vmem,src:apcupsd,src:zsh,src:hub,src:mcl,src:mp3info,src:man-db,src:xterm,src:slashem,src:sendmail,src:conky,src:wiki2beamer,src:latex2rtf,src:loadlin,src:xcolorsel,src:console-setup,src:ding,src:libdap,src:calc,src:ocp
Added tag(s) confirmed.
Bug #963451 {Done: Samuel Thibault } [bsdmainutils]
loadlin: FTBFS: /bin/sh: 1: hexdump: not found
Bug reopened
Ignoring request to alter fixed versions of bug #963451 to the same values
previously set
Added indication that 963451 affects
src:pbuilder,src:glhack,src:libstorj,src:vmem,src:apcupsd,src:zsh,src:hub,src:mcl,src:mp3info,src:man-db,src:xterm,src:slashem,src:sendmail,src:conky,src:wiki2beamer,src:latex2rtf,src:loadlin,src:xcolorsel,src:console-setup,src:ding,src:libdap,src:calc,src:ocp
Added tag(s) confirmed.
Bug #963361 [bsdmainutils] hub: FTBFS: /bin/sh: 1: col: not found
Added indication that 963361 affects
src:pbuilder,src:glhack,src:libstorj,src:vmem,src:apcupsd,src:zsh,src:hub,src:mcl,src:mp3info,src:man-db,src:xterm,src:slashem,src:sendmail,src:conky,src:wiki2beamer,src:latex2rtf,src:loadlin,src:xcolorsel,src:console-setup,src:ding,src:libdap,src:calc,src:ocp
Added tag(s) confirmed.
Bug #963413 [bsdmainutils] vmem: FTBFS: man: can't execute col: No such file or
directory
Added indication that 963413 affects
src:pbuilder,src:glhack,src:libstorj,src:vmem,src:apcupsd,src:zsh,src:hub,src:mcl,src:mp3info,src:man-db,src:xterm,src:slashem,src:sendmail,src:conky,src:wiki2beamer,src:latex2rtf,src:loadlin,src:xcolorsel,src:console-setup,src:ding,src:libdap,src:calc,src:ocp
Added tag(s) confirmed.
Bug #963403 [bsdmainutils] mp3info: FTBFS: /bin/sh: 1: col: not found
Added indication that 963403 affects
src:pbuilder,src:glhack,src:libstorj,src:vmem,src:apcupsd,src:zsh,src:hub,src:mcl,src:mp3info,src:man-db,src:xterm,src:slashem,src:sendmail,src:conky,src:wiki2beamer,src:latex2rtf,src:loadlin,src:xcolorsel,src:console-setup,src:ding,src:libdap,src:calc,src:ocp
Added tag(s) confirmed.
Bug #963448 [bsdmainutils] wiki2beamer: FTBFS: man: can't execute col: No such
file or directory
Added indication that 963448 affects
src:pbuilder,src:glhack,src:libstorj,src:vmem,src:apcupsd,src:zsh,src:hub,src:mcl,src:mp3info,src:man-db,src:xterm,src:slashem,src:sendmail,src:conky,src:wiki2beamer,src:latex2rtf,src:loadlin,src:xcolorsel,src:console-setup,src:ding,src:libdap,src:calc,src:ocp
Added tag(s) confirmed.
Bug #963353 [bsdmainutils] mcl: FTBFS: /bin/bash: col: command not found
Added indication that 963353 affects
src:pbuilder,src:glhack,src:libstorj,src:vmem,src:apcupsd,src:zsh,src:hub,src:mcl,src:mp3info,src:man-db,src:xterm,src:slashem,src:sendmail,src:conky,src:wiki2beamer,src:latex2rtf,src:loadlin,src:xcolorsel,src:console-setup,src:ding,src:libdap,src:calc,src:ocp
Added tag(s) confirmed.
Bug #963359 [bsdmainutils] glhack: FTBFS: /bin/sh: 1: col: not found
Added indication that 963359 affects
src:pbuilder,src:glhack,src:libstorj,src:vmem,src:apcupsd,src:zsh,src:hub,src:mcl,src:mp3info,src:man-db,src:xterm,src:slashem,src:sendmail,src:conky,src:wiki2beamer,src:latex2rtf,src:loadlin,src:xcolorsel,src:console-setup,src:ding,src:libdap,src:calc,src:ocp
Added tag(s) confirmed.
Bug #963375 [bsdmainutils] conky: FTBFS: /usr/bin/man: can't execute col: No
such file or directory
Added indication that 963375 affects
src:pbuilder,src:glhack,src:libstorj,src:vmem,src:apcupsd,src:zsh,src:hub,src:mcl,src:mp3info,src:man-db,src:xterm,src:slashem,src:sendmail,src:conky,src:wiki2beamer,src:latex2rtf,src:loadlin,src:xcolorsel,src:console-setup,src:ding,src:libdap,src:calc,src:ocp
Added tag(s) confirmed.
Bug #963442 [bsdmainutils] pbuilder: FTBFS: dh_auto_test: error: make -j4 check
returned exit code 2
Added indication that 963442 affects
src:pbuilder,src:glhack,src:libstorj,src:vmem,src:apcupsd,src:zsh,src:hub,src:mcl,src:mp3info,src:man-db,src:xterm,src:slashem,src:sendmail,src:conky,src:wiki2beamer,src:latex2rtf,src:loadlin,src:xcolorsel,src:console-setup,src:ding,src:libdap,src:calc,src:ocp
Added tag(s) confirmed.
Bug #963383 [bsdmainutils] calc: FTBFS: /bin/sh: 5: col: not found
Bug#963357: marked as done (libtest-redisserver-perl: FTBFS: test failed)
Your message dated Sun, 21 Jun 2020 21:48:42 + with message-id and subject line Bug#963357: fixed in libtest-redisserver-perl 0.21-2 has caused the Debian Bug report #963357, regarding libtest-redisserver-perl: FTBFS: test failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtest-redisserver-perl Version: 0.21-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 > test -x debian/rules > mkdir -p "." > cd . && perl -I. Build.PL --installdirs vendor --config ccflags="-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv > -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64" --config cxxflags="-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" --config cppflags="-Wdate-time -D_FORTIFY_SOURCE=2 > -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe > -I/usr/local/include" --config lddlflags="-Wl,-z,relro -shared > -L/usr/local/lib -fstack-protector-strong" --destdir > /<>/debian/libtest-redisserver-perl > Creating new 'Build' script for 'Test-RedisServer' version '0.21' > cd . && ./Build build > cp lib/Test/RedisServer.pm blib/lib/Test/RedisServer.pm > touch debian/stamp-perl-build > cd . && ./Build test --verbose 1 > t/basic.t . > ok 1 - pid ok > ok 2 - unix socket ok > ok 3 - server key does not exist ok > ok 4 - ping pong ok > ok 5 - pid removed ok > ok 6 - no server available ok > ok 7 - pid ok > ok 8 - sock does not exist ok > ok 9 - server addr ok > ok 10 - ping pong ok > ok 11 - server died ok > 1..11 > ok > t/manual_start.t .. > ok 1 - redis client object was not created ok > ok 2 - error msg ok > ok 3 - ping pong ok > 1..3 > ok > t/no_server.t . > ok 1 - server was not created ok > ok 2 - error msg ok > 1..2 > ok > t/tmp_dir.t ... > 15455:C 21 Jun 2020 07:36:01.819 # oO0OoO0OoO0Oo Redis is starting > oO0OoO0OoO0Oo > 15455:C 21 Jun 2020 07:36:01.819 # Redis version=6.0.5, bits=64, > commit=, modified=0, pid=15455, just started > 15455:C 21 Jun 2020 07:36:01.819 # Configuration loaded > 15455:M 21 Jun 2020 07:36:01.819 * Increased maximum number of open files to > 10032 (it was originally set to 1024). > 15455:M 21 Jun 2020 07:36:01.820 * Running mode=standalone, port=33269. > 15455:M 21 Jun 2020 07:36:01.820 # WARNING: The TCP backlog setting of 511 > cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower > value of 128. > 15455:M 21 Jun 2020 07:36:01.820 # Server initialized > 15455:M 21 Jun 2020 07:36:01.820 # WARNING overcommit_memory is set to 0! > Background save may fail under low memory condition. To fix this issue add > 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the > command 'sysctl vm.overcommit_memory=1' for this to take effect. > 15455:M 21 Jun 2020 07:36:01.820 # WARNING you have Transparent Huge Pages > (THP) support enabled in your kernel. This will create latency and memory > usage issues with Redis. To fix this issue run the command 'echo never > > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your > /etc/rc.local in order to retain the setting after a reboot. Redis must be > restarted after THP is disabled. > 15455:M 21 Jun 2020 07:36:01.820 * Ready to accept connections > 15455:signal-handler (1592724961) Received SIGTERM scheduling shutdown... > 15455:M 21 Jun 2020 07:36:01.821 # User requested shutdown... > 15455:M 21 Jun 2020 07:36:01.821 # Redis is now ready to exit, bye bye... > ok 1 - no files remained after server shutdown > 1..1 > ok > > # Failed test 'error msg ok' > # at t/unknown_conf.t line 17. > # '*** failed to launch redis-server *** > # > # *** FATAL CONFIG FILE ERROR (Redis 6.0.5) *** > # Reading the configuration file, at line 2 > # >>> 'unknown_key unknown_val' > # Bad directive or wrong number of arguments > # at t/unknown_conf.t line 11. > # ' > # doesn't match '(?^:\*\*\* FATAL CONFIG FILE ERROR \*\*\*)' > # Looks like you failed 1 test of 2. > t/unknown_conf.t .. > ok 1 - server did not initialize ok > not ok 2 - error msg ok > 1..2 > Dubious, test returned 1 (wstat 256, 0x100) >
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 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#963308: marked as done (localslackirc: FTBFS: slack.py:783: error: Need type annotation for 'ev')
Your message dated Sun, 21 Jun 2020 21:36:30 + with message-id and subject line Bug#963308: fixed in localslackirc 1.10-1 has caused the Debian Bug report #963308, regarding localslackirc: FTBFS: slack.py:783: error: Need type annotation for 'ev' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: localslackirc Version: 1.9-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 '/<>' > MYPYPATH=stubs mypy --config-file mypy.conf irc.py > slack.py:783: error: Need type annotation for 'ev' > slack.py:785: error: Argument 2 to "load" has incompatible type "object"; > expected "Type[]" > Found 2 errors in 1 file (checked 1 source file) > make[1]: *** [Makefile:6: lint] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/06/20/localslackirc_1.9-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. --- End Message --- --- Begin Message --- Source: localslackirc Source-Version: 1.10-1 Done: Salvo 'LtWorf' Tomaselli We believe that the bug you reported is fixed in the latest version of localslackirc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvo 'LtWorf' Tomaselli (supplier of updated localslackirc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 30 Apr 2020 16:06:15 +0200 Source: localslackirc Architecture: source Version: 1.10-1 Distribution: unstable Urgency: high Maintainer: Salvo 'LtWorf' Tomaselli Changed-By: Salvo 'LtWorf' Tomaselli Closes: 963308 Changes: localslackirc (1.10-1) unstable; urgency=high . * New upstream release (Closes: #963308) Checksums-Sha1: 55f428dbd92ecc61be68c702be9ac6a6150d7280 2211 localslackirc_1.10-1.dsc 9fec1dbfc16cb768131aeeb921e9981bf04e75d6 38472 localslackirc_1.10.orig.tar.gz dd855a0134e1d128357ac7dd9f094aea4d01bf7a 833 localslackirc_1.10.orig.tar.gz.asc de5644776cee17269d042169d5c0c1275e8cd915 12520 localslackirc_1.10-1.debian.tar.xz 2392ce15d91102a9ec7501cc9f8d1961d55726f0 6890 localslackirc_1.10-1_amd64.buildinfo Checksums-Sha256: aeaccb9b2bd031b76396d47a6f471c169df5f23109d4b50835678d1a57fee249 2211 localslackirc_1.10-1.dsc 505ed01139061e1a4a42b3d3557b53775d3a6809432cde4ec487e3d5d3846f4b 38472 localslackirc_1.10.orig.tar.gz 615923798edb4a6908284c379bc3d8d68fc4233d4ddbe64206b86b58c09982e0 833 localslackirc_1.10.orig.tar.gz.asc f6a7c5be6b0b36b8f269eec6f174172af8336b2fb92545d23cf6c2df506e182f 12520 localslackirc_1.10-1.debian.tar.xz ff23af724f3f987cc1791d845ba2904da13ba67a7f6607989cbe3a1d1ada5cc5 6890 localslackirc_1.10-1_amd64.buildinfo Files: 74cc5cfc8d14f413f678109e1c120444 2211 net optional localslackirc_1.10-1.dsc 36ea59fc75eeffecd0d9903b50211ae1 38472 net optional localslackirc_1.10.orig.tar.gz c91b612287f62a6d843091351b699c42 833 net optional localslackirc_1.10.orig.tar.gz.asc f5a3a93b982aad286ed18cf26868933c 12520 net optional localslackirc_1.10-1.debian.tar.xz 3eba2db2616d312b6b0894dba3689bbe 6890 net optional localslackirc_1.10-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEQnSLnnbYmXmeH74Us6fPDIAYhs8FAl7vy84UHHRpcG9zY2hp QHRpc2NhbGkuaXQACgkQs6fPDIAYhs/b7Q/8DXSy38IJ6/tEZcIOtjicY0TvBRCZ wAehR0f/B6Y9BNw2GW05X8xL5kdjrD/a4MwLhoBiw/nWgv3tim32qGcVS5Uepmfc 8RB92aIYmkrBhHKMgTLPqECnB/7Vl3LAoTlHMboq/4fS08J0bnyt/a0MXzq6z5In QNQN0xUEyqIkyuJoiY6Zu9OMaaTz9dE9E2oRQblrPe9Wb+0UfURwIt+U5HK7xmpc 1yae1iQ2CgPr6ftBmezKMX1YUcg137rPiZVsQumh0HoCH/h3euS15Wdu+9yVkdfT
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 963327 bsdmainutils 12.1.1 Bug #963327 [src:libstorj] libstorj: FTBFS: configure: error: hexdump is required for tests Bug reassigned from package 'src:libstorj' to 'bsdmainutils'. No longer marked as found in versions libstorj/1.0.3-1. Ignoring request to alter fixed versions of bug #963327 to the same values previously set Bug #963327 [bsdmainutils] libstorj: FTBFS: configure: error: hexdump is required for tests Marked as found in versions bsdmainutils/12.1.1. > reassign 963349 bsdmainutils 12.1.1 Bug #963349 [src:libdap] libdap: FTBFS: /bin/bash: col: command not found Bug reassigned from package 'src:libdap' to 'bsdmainutils'. No longer marked as found in versions libdap/3.20.6-2. Ignoring request to alter fixed versions of bug #963349 to the same values previously set Bug #963349 [bsdmainutils] libdap: FTBFS: /bin/bash: col: command not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963350 bsdmainutils 12.1.1 Bug #963350 [src:slashem] slashem: FTBFS: /bin/sh: 1: col: not found Bug reassigned from package 'src:slashem' to 'bsdmainutils'. No longer marked as found in versions slashem/0.0.7E7F3-9. Ignoring request to alter fixed versions of bug #963350 to the same values previously set Bug #963350 [bsdmainutils] slashem: FTBFS: /bin/sh: 1: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963353 bsdmainutils 12.1.1 Bug #963353 [src:mcl] mcl: FTBFS: /bin/bash: col: command not found Bug reassigned from package 'src:mcl' to 'bsdmainutils'. No longer marked as found in versions mcl/1:14-137+ds-6. Ignoring request to alter fixed versions of bug #963353 to the same values previously set Bug #963353 [bsdmainutils] mcl: FTBFS: /bin/bash: col: command not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963355 bsdmainutils 12.1.1 Bug #963355 [src:ocp] ocp: FTBFS: /bin/sh: 1: hexdump: not found Bug reassigned from package 'src:ocp' to 'bsdmainutils'. No longer marked as found in versions ocp/1:0.2.2+ds-1. Ignoring request to alter fixed versions of bug #963355 to the same values previously set Bug #963355 [bsdmainutils] ocp: FTBFS: /bin/sh: 1: hexdump: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963359 bsdmainutils 12.1.1 Bug #963359 [src:glhack] glhack: FTBFS: /bin/sh: 1: col: not found Bug reassigned from package 'src:glhack' to 'bsdmainutils'. No longer marked as found in versions glhack/1.2-4. Ignoring request to alter fixed versions of bug #963359 to the same values previously set Bug #963359 [bsdmainutils] glhack: FTBFS: /bin/sh: 1: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963361 bsdmainutils 12.1.1 Bug #963361 [src:hub] hub: FTBFS: /bin/sh: 1: col: not found Bug reassigned from package 'src:hub' to 'bsdmainutils'. No longer marked as found in versions hub/2.7.0~ds1-1. Ignoring request to alter fixed versions of bug #963361 to the same values previously set Bug #963361 [bsdmainutils] hub: FTBFS: /bin/sh: 1: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963365 bsdmainutils 12.1.1 Bug #963365 [src:sendmail] sendmail: FTBFS: /bin/sh: 1: ul: not found Bug reassigned from package 'src:sendmail' to 'bsdmainutils'. No longer marked as found in versions sendmail/8.15.2-19. Ignoring request to alter fixed versions of bug #963365 to the same values previously set Bug #963365 [bsdmainutils] sendmail: FTBFS: /bin/sh: 1: ul: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963372 bsdmainutils 12.1.1 Bug #963372 [src:console-setup] console-setup: FTBFS: /bin/sh: 1: col: not found Bug reassigned from package 'src:console-setup' to 'bsdmainutils'. No longer marked as found in versions console-setup/1.195. Ignoring request to alter fixed versions of bug #963372 to the same values previously set Bug #963372 [bsdmainutils] console-setup: FTBFS: /bin/sh: 1: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963375 bsdmainutils 12.1.1 Bug #963375 [src:conky] conky: FTBFS: /usr/bin/man: can't execute col: No such file or directory Bug reassigned from package 'src:conky' to 'bsdmainutils'. No longer marked as found in versions conky/1.10.8-1.1. Ignoring request to alter fixed versions of bug #963375 to the same values previously set Bug #963375 [bsdmainutils] conky: FTBFS: /usr/bin/man: can't execute col: No such file or directory Marked as found in versions bsdmainutils/12.1.1. > reassign 963376 bsdmainutils 12.1.1 Bug #963376 [src:apcupsd] apcupsd: FTBFS: man: can't execute col: No such file or directory Bug reassigned from package 'src:apcupsd' to 'bsdmainutils'. No longer marked as found in versions apcupsd/3.14.14-3. Ignoring request to alter fixed versions of bug #963376 to the same values previously set Bug #963376 [bsdmainutils] apcupsd: FTBFS: man: can't execute col: No such file or directory Marked as found in versions bsdmainutils/12.1.1. > reassign
Bug#963276: marked as done (litmus: FTBFS: src/basic.c:30:10: fatal error: ne_request.h: No such file or directory)
Your message dated Sun, 21 Jun 2020 21:36:22 + with message-id and subject line Bug#963276: fixed in litmus 0.13-3 has caused the Debian Bug report #963276, regarding litmus: FTBFS: src/basic.c:30:10: fatal error: ne_request.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: litmus Version: 0.13-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): > gcc -DHAVE_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 > -I. -I./lib -I./src -I./test-common -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -I./lib/neon -c test-common/tests.c -o > test-common/tests.o > src/basic.c:30:10: fatal error: ne_request.h: No such file or directory >30 | #include > | ^~ > compilation terminated. > make[1]: *** [Makefile:109: src/basic.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/06/20/litmus_0.13-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. --- End Message --- --- Begin Message --- Source: litmus Source-Version: 0.13-3 Done: =?utf-8?q?Jelmer_Vernoo=C4=B3?= We believe that the bug you reported is fixed in the latest version of litmus, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated litmus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 21 Jun 2020 21:04:42 + Source: litmus Architecture: source Version: 0.13-3 Distribution: unstable Urgency: medium Maintainer: Jelmer Vernooij Changed-By: Jelmer Vernooij Closes: 963276 Changes: litmus (0.13-3) unstable; urgency=medium . [ Debian Janitor ] * Bump debhelper from old 10 to 12. * Set upstream metadata fields: Bug-Submit. . [ Jelmer Vernooij ] * Remove obsolete field Name from debian/upstream/metadata (already present in machine-readable debian/copyright). * Update standards version to 4.5.0, no changes needed. * Add support for newer neon version. Closes: #963276 * Set Rules-Requires-Root: no. Checksums-Sha1: fe740dc5e5327c6295b74aec575b20c79df4cc07 1815 litmus_0.13-3.dsc 192bd60a0ae017643e09e4e40d9f002167daf3d1 3272 litmus_0.13-3.debian.tar.xz ec3fa4350595160e47494e028da9d17dc89fe2d6 6637 litmus_0.13-3_amd64.buildinfo Checksums-Sha256: d49c7b0fb016537fc08cbbd052cb72a8fc6cf7952d41a68fb3968665023c6abd 1815 litmus_0.13-3.dsc 358b3cec7db5350e5f78f239aa06f706299d50c727f6f6c95e4933c624aa485b 3272 litmus_0.13-3.debian.tar.xz 20216871b62313f320e62364a1c7d850004a02f8b53db60eff5bdc87a3a94a64 6637 litmus_0.13-3_amd64.buildinfo Files: d07ed1cb7fda811796a2b1bd78f91396 1815 web optional litmus_0.13-3.dsc f72c71fa931eabda93e2a5a607033a75 3272 web optional litmus_0.13-3.debian.tar.xz b40bfabab9e3be15cc04e05fd15de996 6637 web optional litmus_0.13-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAl7vzHIACgkQV5wWDUye I+ikPhAAijrXhWPjg6xMxDu/fX2nNvpCBIKKexe4XgecOQD86vKFa3z8lFnn++IL 9zTU8MAvg0wWvdd61vGaHLOkDQTXU070Jb19amTFTed6S3h3hbW4TzAMKcwxDOLV NSminBk2M0MmOxGyY9jT0xQQqBTUVuZG84uCC7338ccH4s4Wcjc4/hilipa0fJyz PK3FIN5jQAnDhVYYsHIojGI6uue8Biv6aKlENEH5fSYwNU6UAZFzCKwemCyAI5jr iKEZqBputC3u3JLVB/OmLwvmCatqJ6recs7ag38CRL6JEXjVZkJFuIlNBcPolyXT UQ3KUTVyTPtjZDa7D6ViJ59phgt6mVG5ytZL1D3AaQfu9ussaNEBnu335i9o7lNy me7TIFTl+AK1VSPdT74Yjbf1qGmSxQmZbxwy3pESV5qWhwerq4NGA4FgVs2BfUfo
Bug#963422: marked as done (git-extras: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2)
Your message dated Sun, 21 Jun 2020 21:36:14 + with message-id and subject line Bug#963422: fixed in git-extras 5.1.0-2 has caused the Debian Bug report #963422, regarding git-extras: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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. --- End Message --- --- Begin Message --- Source: git-extras Source-Version: 5.1.0-2 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of git-extras, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated git-extras package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 21 Jun 2020 22:57:19 +0200 Source: git-extras Architecture: source Version: 5.1.0-2 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 963422 Changes: git-extras (5.1.0-2) unstable; urgency=medium . * Add bsdextrautils build dependency (closes: #963422). * Update debhelper level to 12 . * Update Standards-Version to 4.5.0 . Checksums-Sha1: 76198c5cf6afbde9c311fd1b84eef0d7e1fb9559 1757 git-extras_5.1.0-2.dsc 0871835849f14111f76bd3b852636b02228a20da 5784 git-extras_5.1.0-2.debian.tar.xz Checksums-Sha256: 2a19518328119a03a41b2f822a00ab3a869c6aaedbdc51de5d03c1bf7f6b0107 1757 git-extras_5.1.0-2.dsc 48a563ecb04dc3ac694009c94ac7199e571117017e96222affb4e227285daa4d 5784 git-extras_5.1.0-2.debian.tar.xz Files: 0c9556dfcd8a04c8d9d96e41202039a3 1757 vcs optional git-extras_5.1.0-2.dsc 586ffaf5c4763debac2ddb69fc6fe252 5784 vcs optional git-extras_5.1.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl7vzagACgkQ3OMQ54ZM yL8zcg/9Fxn5dCKkU8x3MBhxx+CUdOLqhEZ5yvfo7Sfyn1Mo/KpGszgwjWy/YduH 1STg4zC4rTAY87DCyLfB5ELrlWK4EtslcMbVyYuhK4Wny1C5vJmBVPB/geRwqWmc csMYMzBd2lILjvN3Gjz/hfVRc8b3vK4sJ5ZOepTtEVeV1wmC4U0wdWgq/71k1gUv kZlN2218Hhwd51C0jwBz2GoteXWpDLjCECmnTqOmbAPs4HKimcaXWUHJMLoEdhZH 1nKOnVXsjnQFOMMSEvFYo95WsZcfZfGcCiWHdOZc+tXibXPBvoUl/W/c4/0UCfgN Q1qYL9yDoOIWxLeSA2dp7q8st1YIgYUyHsX3pVzFnhiRqFZ0Hh1yWmQ0/Pt1cmwc qZIFiepfjv6sL3+XjFGJU0NM6ambQZ8QtbJ12QZpTqT2Ypzbp2+JPvrWut88/omJ 952SU/oSeSD/yj8cV6hHwYYeqJRhNKsRsL/bPrgy04DN5CyU2xrB5Al3DkMSNxZS Hwej/jjaV5qCFk9uaB/yph5jihtROQgip0h3ysGaYdw3j/JHah8YrL4Kp64hCHMb L/er+1QcBuYmAxmFolxeMw8qEcLP4eStZDAeaExFQjlIppocwTy90kt/8VCUup4J gisqKL4Oz7CU/pppjg+cZROBx/NZ3xLP5J/BAWBwkyAeV9wZx0s= =qT1A -END PGP SIGNATURE End Message ---
Processed: tagging 963408
Processing commands for cont...@bugs.debian.org: > tags 963408 + confirmed Bug #963408 [src:pmtools] pmtools: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 963408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963408: pmtools: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2
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
Processed: tagging 963420
Processing commands for cont...@bugs.debian.org: > tags 963420 + confirmed Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 963420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963177: calendar: trying to overwrite '/etc/calendar/default', which is also in package bsdmainutils 12.1.1
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.
Processed: Bug#963417 marked as pending in gem
Processing control commands: > tag -1 pending Bug #963417 [src:gem] gem: FTBFS: /bin/sh: 4: -find: not found Added tag(s) pending. -- 963417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963417: marked as pending in gem
Control: tag -1 pending Hello, Bug #963417 in gem reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/pd/gem/-/commit/0c2af817b20499bff75f1fefb0c5959368466fb3 Drop useless line-continuation Closes: #963417 (this message was generated automatically) -- Greetings https://bugs.debian.org/963417
Bug#963451: marked as done (loadlin: FTBFS: /bin/sh: 1: hexdump: not found)
Your message dated Sun, 21 Jun 2020 21:20:50 + with message-id and subject line Bug#963451: fixed in loadlin 1.6f-8 has caused the Debian Bug report #963451, regarding loadlin: FTBFS: /bin/sh: 1: hexdump: not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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. --- End Message --- --- Begin Message --- Source: loadlin Source-Version: 1.6f-8 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of loadlin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated loadlin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 21 Jun 2020 22:45:38 +0200 Source: loadlin Binary: loadlin loadlin-dbgsym Architecture: source Version: 1.6f-8 Distribution: unstable Urgency: medium Maintainer: Samuel Thibault Changed-By: Samuel Thibault Description: loadlin- loader (running under DOS) for LINUX kernel images Closes: 963451 Changes: loadlin (1.6f-8) unstable; urgency=medium . * control: Build-depend on bsdmainutils (closes: #963451). Checksums-Sha1: b6cb3ab71b656a8ad89d0d96f910dc940c032fcd 1844 loadlin_1.6f-8.dsc 04f7310e033ab506395a2a9b7c0a1a4c797d58c5 18588 loadlin_1.6f-8.debian.tar.xz Checksums-Sha256: b15062e33ae81d65082f2b73dbbd57a47e648dfb5de0999cd2f8393fb4b8e224 1844 loadlin_1.6f-8.dsc 5657a9bbc6b74ad778ca4c8f51ee35b8d04e74708cd18fb952121052671335ef 18588 loadlin_1.6f-8.debian.tar.xz Files: cb36365144c88b7ec6eb10c133151749 1844 admin optional loadlin_1.6f-8.dsc 75de6d738486f6a83a26079289b3b945 18588 admin optional loadlin_1.6f-8.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXtnoVvfWxur1EWehjTXDVXILuv0FAl7vzT4ACgkQjTXDVXIL uv0cRg//fxL8GrmeHZR6P8g3N3/e5fmOrJIdBVl/RU6GLinkKel4gLD+K2Q50vh3 V7DRBRUmskxM+6QgBq62XdwlzIft4z53VFX3vloOATvANZ9EHmhv/OiYXrwClFtD SlVz+McY7Jr7EhLLs7OC9EhRvJD4/dBykwQqtMDOA9P7NenToqkei8Ww+Nk/U7jP 5zUHj7Z38e6G56Kjyh3wBjY5RW7Hi1eh7udkiKtnK0vk/jtlzymQg4WcyNYfIH3g THxHWbWT6LMEZYDzGJ7Fh0z4MsU0wPNNo6oWxgPuYK7AaHw0CPm6DM7MVsneUTF2 mePtjWmtTjR1ZT3FOvoSsLyKGrATN+bchMRiDdu6bdV6EhXsClI+bkPLcoBP3D0D /WuArBiMFw9EEV9FFR5GC8blMDnBwY1cy/eTqvOOLQAJzkfVujyo1VGgCWpkysG5 qLAfZeIWtoMReaSZunaRQHJ1A7BXRBbL15haXQBEVXhYdWWIShYjSX2XvsB/VzF/ uHpCCE+9C0sVSqbDILVomiALyOcmS1WyZqNxDjq8Bj6xZx4TmUQnEkazSENePsAd p32uwQkrzQntqkgZ7Ia5WD4zIKLENwVvpEpvj3rhb+7LnLDvHHnqDWrrXYMtnN+H HVRap4vNWD15gh5zR+/LbxG/XAGgac6QoNESp/vhnbmV7x/ENfo= =cnsP -END PGP SIGNATURE End Message ---
Processed: Bug#963357 marked as pending in libtest-redisserver-perl
Processing control commands: > tag -1 pending Bug #963357 [src:libtest-redisserver-perl] libtest-redisserver-perl: FTBFS: test failed Added tag(s) pending. -- 963357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963357: marked as pending in libtest-redisserver-perl
Control: tag -1 pending Hello, Bug #963357 in libtest-redisserver-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/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. (this message was generated automatically) -- Greetings https://bugs.debian.org/963357
Bug#963420: [Pkg-zsh-devel] Bug#963420: zsh: FTBFS: sh: 1: colcrt: not found
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
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
Processed: forcibly merging 962739 963397
Processing commands for cont...@bugs.debian.org: > forcemerge 962739 963397 Bug #962739 [src:qtcurve] qtcurve FTBFS: misses FrameworkIntegration Bug #962739 [src:qtcurve] qtcurve FTBFS: misses FrameworkIntegration Added tag(s) sid and bullseye. Bug #963397 [src:qtcurve] 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=/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 .. returned exit code 1 Added tag(s) pending. Merged 962739 963397 > thanks Stopping processing here. Please contact me if you need assistance. -- 962739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962739 963397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963455: marked as done (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 an
Your message dated Sun, 21 Jun 2020 21:03:24 + with message-id and subject line Bug#963455: fixed in containerd 1.3.4~ds1-2 has caused the Debian Bug report #963455, regarding 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: to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 >
Processed: reassign 961147 to src:libcolor-calc-perl, found 961147 in 1.074-2, forcibly merging 963433 961147
Processing commands for cont...@bugs.debian.org: > reassign 961147 src:libcolor-calc-perl Bug #961147 [libcolor-calc-perl] libcolor-calc-perl: broken by new libgraphics-colornames-perl Bug reassigned from package 'libcolor-calc-perl' to 'src:libcolor-calc-perl'. No longer marked as found in versions libcolor-calc-perl/1.074-2. Ignoring request to alter fixed versions of bug #961147 to the same values previously set > found 961147 1.074-2 Bug #961147 [src:libcolor-calc-perl] libcolor-calc-perl: broken by new libgraphics-colornames-perl Marked as found in versions libcolor-calc-perl/1.074-2. > forcemerge 963433 961147 Bug #963433 [src:libcolor-calc-perl] libcolor-calc-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 2 Bug #961147 [src:libcolor-calc-perl] libcolor-calc-perl: broken by new libgraphics-colornames-perl Severity set to 'serious' from 'grave' Added tag(s) ftbfs. Merged 961147 963433 > thanks Stopping processing here. Please contact me if you need assistance. -- 961147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961147 963433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963442: pbuilder: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2
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
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 963394 libdebconf-kde-dev Bug #963394 [src:apper] 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=/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 .. returned exit code 1 Bug reassigned from package 'src:apper' to 'libdebconf-kde-dev'. No longer marked as found in versions apper/1.0.0-2. Ignoring request to alter fixed versions of bug #963394 to the same values previously set > forcemerge 962567 963394 Bug #962567 [libdebconf-kde-dev] libdebconf-kde-dev misses dependencies Bug #962567 [libdebconf-kde-dev] libdebconf-kde-dev misses dependencies Added tag(s) ftbfs. Bug #963394 [libdebconf-kde-dev] 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=/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 .. returned exit code 1 Added indication that 963394 affects src:apper Marked as found in versions debconf-kde/1.0.3-3. Merged 962567 963394 > thanks Stopping processing here. Please contact me if you need assistance. -- 962567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962567 963394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#963455 marked as pending in containerd
Processing control commands: > tag -1 pending Bug #963455 [src:containerd] 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: Added tag(s) pending. -- 963455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963455: marked as pending in containerd
Control: tag -1 pending Hello, Bug #963455 in containerd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/containerd/-/commit/69c72a08650f03439be83fdafdc9d9bda928450b Add golang-github-google-gofuzz-dev to Build-Depends (Closes: #963455) (this message was generated automatically) -- Greetings https://bugs.debian.org/963455
Bug#963336: filtlong: FTBFS: ModuleNotFoundError: No module named 'pkg_resources'
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
Processed: closing 963279
Processing commands for cont...@bugs.debian.org: > close 963279 4.7.0~b1-1 Bug #963279 [src:jss] jss: FTBFS: PK11SymKey.c:265:12: error: ‘CKM_NETSCAPE_PBE_SHA1_DES_CBC’ undeclared (first use in this function); did you mean ‘CKM_NSS_PBE_SHA1_DES_CBC’? Marked as fixed in versions jss/4.7.0~b1-1. Bug #963279 [src:jss] jss: FTBFS: PK11SymKey.c:265:12: error: ‘CKM_NETSCAPE_PBE_SHA1_DES_CBC’ undeclared (first use in this function); did you mean ‘CKM_NSS_PBE_SHA1_DES_CBC’? Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 963279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#963336: filtlong: FTBFS: ModuleNotFoundError: No module named 'pkg_resources'
Processing control commands: > reassign -1 python3-markdown 3.2.2-1 Bug #963336 [src:filtlong] filtlong: FTBFS: ModuleNotFoundError: No module named 'pkg_resources' Bug reassigned from package 'src:filtlong' to 'python3-markdown'. No longer marked as found in versions filtlong/0.2.0-2. Ignoring request to alter fixed versions of bug #963336 to the same values previously set Bug #963336 [python3-markdown] filtlong: FTBFS: ModuleNotFoundError: No module named 'pkg_resources' Marked as found in versions python-markdown/3.2.2-1. > retitle -1 python3-markdown: missing dependency on python3-pkg-resources Bug #963336 [python3-markdown] filtlong: FTBFS: ModuleNotFoundError: No module named 'pkg_resources' Changed Bug title to 'python3-markdown: missing dependency on python3-pkg-resources' from 'filtlong: FTBFS: ModuleNotFoundError: No module named 'pkg_resources''. > affects -1 src:filtlong Bug #963336 [python3-markdown] python3-markdown: missing dependency on python3-pkg-resources Added indication that 963336 affects src:filtlong -- 963336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963341: cfengine3: New cfengine 3.15.2 package is broken and non-functional
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
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#963460: simutrans-pak64: FTBFS: /bin/bash: /usr/lib/simutrans/makeobj: No such file or directory
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#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
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#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
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#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:
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#963438: ccdproc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13
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#963442: pbuilder: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2
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#963459: python-transitions: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13
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#963448: wiki2beamer: FTBFS: man: can't execute col: No such file or directory
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#963436: node-character-parser: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
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#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
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#963447: shellia: FTBFS: ERROR "./tests/test.prefix" -s "bash" / shortened difference between expectation and result:
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#963444: epubcheck: FTBFS: [ERROR] /<>/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java:[267,7]
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#963457: node-buffer-shims: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
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#963449: liggghts: FTBFS: dh_installman: error: Could not determine section for ./debian/liggghts.1
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#963451: loadlin: FTBFS: /bin/sh: 1: hexdump: not found
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#963446: cross-toolchain-base-ports: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2
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#963454: grml2usb: FTBFS: grml2usb:920:17: F523 '...'.format(...) has unused arguments at position(s): 0
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#963452: varnish-modules: FTBFS: dpkg-gencontrol: error: error occurred while parsing Depends field: libc6 (>= 2.14), libvarnishapi2 (>= 6.1.0),
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#963456: ruby-rufus-scheduler: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(job.last_work_time).to be < 0.099
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#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
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#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
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#963441: capstats: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2
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:
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#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
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#963405: node-gulp-util: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Source: node-gulp-util Version: 3.0.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): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package node-gulp-util > dpkg-buildpackage: info: source version 3.0.8-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Abraham Raji > 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-gulp-util using existing > ./node-gulp-util_3.0.8.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building node-gulp-util in > node-gulp-util_3.0.8-1.debian.tar.xz > dpkg-source: info: building node-gulp-util in node-gulp-util_3.0.8-1.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 > mkdir -p node_modules > ln -s ../debian/tests/test_modules/map-stream node_modules/map-stream > ln -s ../debian/tests/test_modules/event-stream > node_modules/event-stream > ln -s ../debian/tests/test_modules/stream-combiner > node_modules/stream-combiner > ln -s ../debian/tests/test_modules/duplexer node_modules/duplexer > ln -s ../debian/tests/test_modules/from node_modules/from > ln -s ../debian/tests/test_modules/pause-stream > node_modules/pause-stream > /bin/sh -ex debian/tests/pkg-js/test > + ls test/File.js test/PluginError.js test/beep.js test/buffer.js+ > test/colors.js test/combine.js test/date.js test/env.js test/isBuffer.js > test/isNull.js test/isStream.js test/linefeed.js test/log.js test/noop.js > test/replaceExtension.js test/template.jsgrep > -v test/beep.js > + NODE_PATH=debian/tests/test_modules mocha test/File.js test/PluginError.js > test/buffer.js test/colors.js test/combine.js test/date.js test/env.js > test/isBuffer.js test/isNull.js test/isStream.js test/linefeed.js test/log.js > test/noop.js test/replaceExtension.js test/template.js > > > File() > ✓ should return a valid file > ✓ should return a valid file 2 > > PluginError() > ✓ should default name to Error > ✓ should default name to Error, even when wrapped error has no name > ✓ should print the plugin name in toString > ✓ should not include the stack by default in toString > ✓ should include the stack when specified in toString > ✓ should take arguments as one object > ✓ should take arguments as plugin name and one object > ✓ should take arguments as plugin name and message > ✓ should take arguments as plugin name, message, and one object > ✓ should take arguments as plugin name, error, and one object > ✓ should take properties from error > ✓ should be configured to show properties by default > ✓ should not be configured to take option to show properties > ✓ should show properties > ✓ should show properties > ✓ should not show properties > ✓ should not show properties, but should show stack > ✓ should not show properties, but should show stack for real error > ✓ should not show properties, but should show stack for _stack > ✓ should show properties and stack > ✓ should show properties added after the error is created > ✓ should toString quickly > ✓ should toString quickly with original error > ✓ should not show "Details:" if there are no properties to show > > buffer() > ✓ should buffer stuff and return an array into the callback > ✓ should buffer stuff and emit it as a data event > ✓ should buffer stuff and return a stream with the buffered data > > colors > ✓ should be a chalk instance > > combine() > ✓ should return a function > ✓ should return a function that returns a stream combination > ✓ should return a function that returns a stream combination when given > an array > > date > ✓ should be a date format instance > ✓ should return today's date > > env > ✓ should exist > > isBuffer() > ✓ should work on a buffer > (node:11772) [DEP0005] DeprecationWarning: Buffer() is deprecated due to > security and usability issues. Please use the Buffer.alloc(), > Buffer.allocUnsafe(), or Buffer.from() methods instead. > ✓ should not work on a stream > > isNull() > ✓ should work on a null > ✓ should not work on a stream > ✓ should not
Bug#963409: kakoune: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2
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
> [31m backward-search[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m backward-search[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m catch-error-desc[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m catch-error-desc[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m complex-pipe[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m complex-pipe[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m del-empty-line[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m del-empty-line[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m discard-selections-with-itersel[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m discard-selections-with-itersel[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m do-not-run-hooks-added-by-parent[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m do-not-run-hooks-added-by-parent[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m echo-to-file[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m echo-to-file[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m eof-multi-delete[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m eof-multi-delete[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m file-expansion[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m file-expansion[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m history[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m history[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m hook-named-captures[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m hook-named-captures[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m inline-sort[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m inline-sort[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m no-hook-on-unset-option-with-same-parent[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m no-hook-on-unset-option-with-same-parent[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m pipe-at-eof[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m pipe-at-eof[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m select-codepoints[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
> Aborted
> [31m select-codepoints[0m
> Kakoune returned error 134
> *** buffer overflow detected ***: /<>/test/../src/kak terminated
> [31m select-display-columns[0m
> [31m- { "jsonrpc": "2.0", "method": "set_ui_options", "params": [{}]
> }
> [32m+ [0m
>
Bug#963420: zsh: FTBFS: sh: 1: colcrt: not found
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#963433: libcolor-calc-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 2
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#963417: gem: FTBFS: /bin/sh: 4: -find: not found
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#963422: git-extras: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2
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#963434: freeboard: FTBFS: dpkg-query: no path found matching pattern /usr/share/javascript/jquery/jquery.js
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#963430: artemis: FTBFS: /bin/sh: 1: /usr/share/java/j2ssh-core.jar: Permission denied
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#963424: sensible-utils: FTBFS: po4a::po: Invalid value for option 'porefs' ('noline,wrap' is not one of 'full', 'counter', 'noline', 'file' or 'never')
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#963418: altree: FTBFS: ! Package texgraphicx Error: 'texgraphicx' is now gone
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#963414: latex2rtf: FTBFS: man: can't execute col: No such file or directory
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#963423: auto-multiple-choice: FTBFS: ! LaTeX Error: File `ctexhook.sty' not found.
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#963427: ding: FTBFS: man: can't execute col: No such file or directory
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#963425: node-terser: FTBFS: ERROR: `m` is not a supported option
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#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
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#963426: keras: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13
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#963411: libisocodes: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2
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#963429: node-pump: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
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#963431: specutils: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13
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#963408: pmtools: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2
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#963410: ros-rospack: FTBFS: tests failed
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#963413: vmem: FTBFS: man: can't execute col: No such file or directory
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#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
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#963416: liboping: FTBFS: dpkg-gencontrol: error: unknown option '-v'
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#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=/
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#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
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) >
