Your message dated Mon, 22 Jun 2020 06:49:08 +
with message-id
and subject line Bug#963388: fixed in spectral-cube 0.4.5-3
has caused the Debian Bug report #963388,
regarding spectral-cube: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.8 returned exit code 1
Processing control commands:
> tag -1 pending
Bug #963436 [src:node-character-parser] node-character-parser: FTBFS:
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Added tag(s) pending.
--
963436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963436
Debian Bug
Control: tag -1 pending
Hello,
Bug #963436 in node-character-parser 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/js-team/node-character-parser/-/commit/9b75c
Source: libvirt
Version: 6.2.0-1
Severity: grave
Tags: security upstream
Hi
libvirt starting from 6.2.0-rc1 upsteram is affected by
CVE-2020-14301, leak of sensitive cookie information via dumpxml. I'm
filling it as RC severity as it does not affect current unstable
version and the vession in uns
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
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);
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: cann
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
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 a
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 follow
> 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
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 t
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 erro
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 t
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 b
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
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
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
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
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
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.
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
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
B
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
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 ve
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 proble
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/sr
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.
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 cla
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
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 cl
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.
--
963
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.*DESCRIPT
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=
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 fil
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
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/0c2af817b20499bff75f1fefb0c595
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 deal
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
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-rediss
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 fou
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 bui
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_con
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:
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 versi
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:
bsdextr
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_LOCALSTATEDI
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://
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/69c72a08650f03439b
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
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.
B
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 r
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
>
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 bu
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.
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
> --
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
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 direc
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 '/<>
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 '/<
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 '/
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 '/
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 '/<>'
> f
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 '/<>'
>
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
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
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: expe
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
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/s
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
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 '/<>'
> f
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 --bu
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
> ---
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 '/<>'
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_up
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
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]: Enteri
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
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
> --
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 '/<>
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'
>
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 b
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
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 '/<>'
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 binar
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
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 director
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 '/<>/Docum
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 '/<>/d
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 direct
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
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 '/<>'
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_
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 '/<>'
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 '/<>/
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
> ---
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
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'
> ..
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:
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 '/<>'
>
1 - 100 of 253 matches
Mail list logo