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

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

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:

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

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

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

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

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

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

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

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

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

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

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

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

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:

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

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

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

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

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

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

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

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.

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

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

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

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 -

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:

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

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:

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

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:

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

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

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:

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:

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

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:

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

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:

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:

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

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.

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

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

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

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

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

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

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

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

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 >

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

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

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

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

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

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 >

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

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

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

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

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

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:

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

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 >

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 >

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

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

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 >

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

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'

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 >

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

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

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

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

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

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

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

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

  1   2   3   >