Processing commands for cont...@bugs.debian.org:
> fixed 957348 2.13-1
Bug #957348 {Done: Jakob Haufe } [src:i3lock] i3lock: ftbfs
with GCC-10
Marked as fixed in versions i3lock/2.13-1.
> kthxbye
Stopping processing here.
Please contact me if you need assistance.
--
957348:
Processing commands for cont...@bugs.debian.org:
> close 973225
Bug #973225 [src:python-escript] python-escript: FTBFS: n/Mapping.tex]sh: 1:
svnversion: not found
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
973225:
On Wed, 28 Oct 2020 09:22:58 +0100 Matthias Klose wrote:
> Package: src:freecad
> Version: 0.18.4+dfsg2-5
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9
>
> to reproduce, you can use the repositories found at:
>
> deb [trusted=yes]
verity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 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 '/<>'
> set -e; \
> for target in i6
Source: ceph
Version: 14.2.9-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for ceph.
CVE-2020-25660[0]:
| cephx authentication protocol does not verify ceph clients correctly
If you fix the
Source: postgis
Version: 3.0.2+dfsg-4
Severity: serious
tags: patch
Hello, doing exit 77 helps in marking some tests as skippable,
but we need to add a Restriction: skippable too to let autopkgtests understand
that this is intentional.
Restrictions: allow-stderr, skippable
Thanks for adding
Processing control commands:
> tags -1 patch
Bug #975109 [src:antimony] antimony: FTBFS in testing and unstable
Added tag(s) patch.
--
975109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 975109 + patch
Bug #975109 [src:antimony] antimony: FTBFS in testing and unstable
Ignoring request to alter tags of bug #975109 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Source: antimony
Followup-For: Bug #975109
Control: tags -1 patch
This is a missing include on QPainterPath. Attaching patch.
--
tobi
--- a/app/viewport/control/control.h
+++ b/app/viewport/control/control.h
@@ -5,6 +5,7 @@
#include
#include
#include
+#include
#include
class
Processing commands for cont...@bugs.debian.org:
> forwarded 975215 https://github.com/torbjornbjorkman/cif2cell/issues/21
Bug #975215 [src:cif2cell] cif2cell: FTBFS: test failed
Set Bug forwarded-to-address to
'https://github.com/torbjornbjorkman/cif2cell/issues/21'.
> thanks
Stopping
Le 19/11/2020 à 18:31, Michael Prokop a écrit :
> Hi,
>
> * Pirate Praveen [Thu Nov 19, 2020 at 03:05:13PM +0530]:
>
>> As you already found out, the problem is in node-yarnpkg. The fix is
>> a bit hard though as node-yarnpkg currently ftbfs due to babel 7
>> transition.
>
>> A work around
Processing commands for cont...@bugs.debian.org:
> affects 975151 src:horizon-eda src:ignition-transport src:php-zmq src:pushpin
> src:r-cran-pbdzmq src:xeus src:zurl
Bug #975151 {Done: Laszlo Boszormenyi (GCS) } [libzmq3-dev]
libzmq3-dev: missing dependency on libbsd-dev
Added indication that
Your message dated Thu, 19 Nov 2020 21:37:17 +
with message-id
and subject line Bug#964512: fixed in openzwave-controlpanel
0.2a+git20161006.a390f35-2.1
has caused the Debian Bug report #964512,
regarding openzwave-controlpanel: FTBFS with invalid type conversion
to be marked as done.
This
Your message dated Thu, 19 Nov 2020 21:36:20 +
with message-id
and subject line Bug#968731: fixed in netgen 6.2.2006+really6.2.1905+dfsg-1
has caused the Debian Bug report #968731,
regarding netgen: copyright and licensing issues
to be marked as done.
This means that you claim that the
Your message dated Thu, 19 Nov 2020 21:35:01 +
with message-id
and subject line Bug#973285: fixed in freecad 0.18.4+dfsg2-6
has caused the Debian Bug report #973285,
regarding freecad ftbfs with python3.9
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 19 Nov 2020 21:36:20 +
with message-id
and subject line Bug#975089: fixed in netgen 6.2.2006+really6.2.1905+dfsg-1
has caused the Debian Bug report #975089,
regarding netgen should become Architecture: amd64
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #975128 [src:pentobi] pentobi: FTBFS: AnalyzeGameModel.cpp:111:29: error:
could not convert ‘{((AnalyzeGameModel*)this),
((AnalyzeGameModel*)this)->AnalyzeGameModel::m_elements}’ from ‘’ to ‘QQmlListProperty’
Added tag(s) pending.
--
975128:
Control: tag -1 pending
Hello,
Bug #975128 in pentobi 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:
Hi,
* Pirate Praveen [Thu Nov 19, 2020 at 03:05:13PM +0530]:
> As you already found out, the problem is in node-yarnpkg. The fix is
> a bit hard though as node-yarnpkg currently ftbfs due to babel 7
> transition.
> A work around could be to install yarnpkg via npm. npm install -g
> yarn and
On Thu, 19 Nov 2020 12:28:53 +0100, gregor herrmann wrote:
> So this might be more of a problem in the recently updated
> libtype-tiny-perl (with or without involvement of perl 5.32, as
> Scalar::Util is dual-lifed).
As noted by Niko on IRC, the actual problem seems to be an ancient
Scalar::Util
On Nov 16, Niko Tyni wrote:
> As to the fix, I suspect we need a pre-dependency from libc6 to libcrypt1
> for one release cycle, so that libc6 cannot be unpacked before libcrypt1
> is fully installed.
I think that Niko is right, so I would like to know the opinion of the
glibc maintainers.
--
Your message dated Thu, 19 Nov 2020 18:48:05 +
with message-id
and subject line Bug#973254: fixed in pacemaker 2.0.1-5+deb10u1
has caused the Debian Bug report #973254,
regarding pacemaker: CVE-2020-25654
to be marked as done.
This means that you claim that the problem has been dealt with.
On 2020-11-19 19:47 +0100, Marco d'Itri wrote:
> On Nov 16, Niko Tyni wrote:
>
>> As to the fix, I suspect we need a pre-dependency from libc6 to libcrypt1
>> for one release cycle, so that libc6 cannot be unpacked before libcrypt1
>> is fully installed.
> I think that Niko is right, so I would
Processing control commands:
> block 972669 by -1
Bug #972669 {Done: Paul Gevers } [src:tarantool]
src:tarantool: fails to migrate to testing for too long: FTBFS on armhf and
arm64
972669 was not blocked by any bugs.
972669 was not blocking any bugs.
Added blocking bug(s) of 972669: 975274
--
Processing commands for cont...@bugs.debian.org:
> notfound 973205 0.4-2
Bug #973205 [src:gr-dab] gr-dab: FTBFS:
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11:
undefined reference to `pthread_create'
No longer marked as found in versions
oblems
--- Begin Message ---
Source: rsyslog
Version: 8.2010.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
> >
>
> Discussed upstream and possibly patch available:
> https://forum.freecadweb.org/viewtopic.php?f=10=47348
>
This was possibly a red herring only. sorry for the noise…
: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Control: tag -1 pending
Hello,
Bug #975143 in rosegarden 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:
Processing control commands:
> tag -1 pending
Bug #975143 [src:rosegarden] rosegarden: FTBFS: Panner.cpp:138:18: error:
aggregate ‘QPainterPath path’ has incomplete type and cannot be defined
Added tag(s) pending.
--
975143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975143
Debian Bug
Control: tags 972074 pending
Control: block 972074 by 963392
On Thu, Nov 19, 2020 at 07:53:06AM -0600, Dirk Eddelbuettel wrote:
> |
> | I do not have the slightest idea what this might mean.
>
> ABI/API slippage in the stack. An interface changed but a package didn't
> recompile.
It seems it
Processing control commands:
> tags 972074 pending
Bug #972074 [src:r-cran-bayestestr] r-cran-bayestestr: autopkgtest regression
Added tag(s) pending.
> block 972074 by 963392
Bug #972074 [src:r-cran-bayestestr] r-cran-bayestestr: autopkgtest regression
972074 was not blocked by any bugs.
972074
Processing control commands:
> tags 972074 pending
Bug #972074 [src:r-cran-bayestestr] r-cran-bayestestr: autopkgtest regression
Ignoring request to alter tags of bug #972074 to the same tags previously set
> block 972074 by 963392
Bug #972074 [src:r-cran-bayestestr] r-cran-bayestestr:
On Thu, Nov 19, 2020 at 18:58, Xavier wrote:
we opened bugs to upstream repo and are waiting for...
I don't think upstream will make any significant changes to 1.x branch
any more. Someone who want to see yarn in debian bullseye will have to
fix it.
Quoting gregor herrmann (2020-11-19 18:40:21)
> On Thu, 19 Nov 2020 12:28:53 +0100, gregor herrmann wrote:
>
> > So this might be more of a problem in the recently updated
> > libtype-tiny-perl (with or without involvement of perl 5.32, as
> > Scalar::Util is dual-lifed).
>
> As noted by Niko
On 19 November 2020 at 19:07, Andreas Tille wrote:
| Control: tags 972074 pending
| Control: block 972074 by 963392
|
| On Thu, Nov 19, 2020 at 07:53:06AM -0600, Dirk Eddelbuettel wrote:
| > |
| > | I do not have the slightest idea what this might mean.
| >
| > ABI/API slippage in the stack.
On Thu, 19 Nov 2020 19:57:31 +0100, Jonas Smedegaard wrote:
> Can you point to specific examples of packages vendoring Scalar::Util
> for me to learn from, Gregor?
Not sure if we have packages with specifically inc/Scalar/Util
but a general recipe, used in lots of packages, is at
Processing control commands:
> reassign -1 libzmq3-dev 4.3.3-3
Bug #975206 {Done: Laszlo Boszormenyi (GCS) } [libzmq3-dev]
zurl: FTBFS: Error: need libzmq >= 2.0!
Bug #975112 {Done: Laszlo Boszormenyi (GCS) } [libzmq3-dev]
horizon-eda: FTBFS in unstable
Bug #975113 {Done: Laszlo Boszormenyi
Processing commands for cont...@bugs.debian.org:
> block 974637 with 964688
Bug #974637 [ftp.debian.org] RM: biosig4c++ -- ROM; replaced by biosig
974637 was not blocked by any bugs.
974637 was not blocking any bugs.
Added blocking bug(s) of 974637: 964688
> thanks
Stopping processing here.
Processing commands for cont...@bugs.debian.org:
> affects 974637 src:biosig4c++
Bug #974637 [ftp.debian.org] RM: biosig4c++ -- ROM; replaced by biosig
Added indication that 974637 affects src:biosig4c++
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
974637:
Processing commands for cont...@bugs.debian.org:
> retitle 974637 RM: biosig4c++ -- ROM; replaced by biosig
Bug #974637 [ftp.debian.org] [ROM] Please remove src:biosig4c++ from unstable
since it was replaced by biosig
Changed Bug title to 'RM: biosig4c++ -- ROM; replaced by biosig' from '[ROM]
Processing commands for cont...@bugs.debian.org:
> tags 974637 + ftbfs
Bug #974637 [ftp.debian.org] RM: biosig4c++ -- ROM; replaced by biosig
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
974637:
Processing commands for cont...@bugs.debian.org:
> severity 972126 serious
Bug #972126 [libopendbx1-sqlite] libopendbx: Please remove support for
long-unmaintained sqlite 2
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing control commands:
> tags -1 patch pending
Bug #964512 [src:openzwave-controlpanel] openzwave-controlpanel: FTBFS with
invalid type conversion
Added tag(s) patch and pending.
--
964512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964512
Debian Bug Tracking System
Contact
Am Donnerstag, den 19.11.2020, 18:00 +0100 schrieb László Böszörményi
(GCS):
> Version: 4.3.3-4
>
> On Thu, Nov 19, 2020 at 1:27 PM Michael Biebl
> wrote:
> > Am Donnerstag, den 19.11.2020, 10:45 +0100 schrieb Lucas Nussbaum:
> > >
> > > > checking for libczmq >= 4.0.0... no
> > > > configure:
control: tags -1 patch pending
Uploaded
G.
On Wed, 8 Jul 2020 11:27:57 -0400 Nicolas Mora wrote:
> Hello,
>
> On Wed, 08 Jul 2020 11:22:18 +0200 Andreas Beckmann wrote:
> >
> > openzwave-controlpanel recently started to FTBFS with
> >
>
> libmicrohttpd has recent API changes. The attached
Processing commands for cont...@bugs.debian.org:
> # same as #975151
> close 975158
Bug #975158 {Done: Laszlo Boszormenyi (GCS) } [libzmq3-dev]
ignition-transport: FTBFS:
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11:
undefined reference to
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package ghc
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package pgl-ddl-deploy
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:tome
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Your message dated Thu, 19 Nov 2020 19:20:01 +
with message-id
and subject line Bug#957128: fixed in desproxy 0.1.0~pre3-10.1
has caused the Debian Bug report #957128,
regarding desproxy: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 19 Nov 2020 19:20:17 +
with message-id
and subject line Bug#973472: fixed in fetchmail 6.4.13-2
has caused the Debian Bug report #973472,
regarding fetchmail: Fails to connect using SSL
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 19 Nov 2020 19:20:17 +
with message-id
and subject line Bug#973472: fixed in fetchmail 6.4.13-2
has caused the Debian Bug report #973472,
regarding fetchmail: OpenSSL library mismatch
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 19 Nov 2020 19:50:59 +
with message-id
and subject line Bug#972074: fixed in r-cran-bayestestr 0.7.5-1
has caused the Debian Bug report #972074,
regarding r-cran-bayestestr: autopkgtest regression
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 19 Nov 2020 16:34:16 +
with message-id
and subject line Bug#973215: fixed in python-fluent-logger 0.9.6-3
has caused the Debian Bug report #973215,
regarding python-fluent-logger: FTBFS: dh_auto_test: error: pybuild --test
--test-nose -i python{version} -p "3.9 3.8"
On 2020, നവംബർ 19 11:01:11 PM IST, Michael Prokop wrote:
>Hi,
>
>* Pirate Praveen [Thu Nov 19, 2020 at 03:05:13PM +0530]:
>
>> As you already found out, the problem is in node-yarnpkg. The fix is
>> a bit hard though as node-yarnpkg currently ftbfs due to babel 7
>> transition.
>
>> A work
Your message dated Fri, 20 Nov 2020 04:20:04 +
with message-id
and subject line Bug#851771: fixed in php-gettext 1.0.12-1
has caused the Debian Bug report #851771,
regarding php-gettext: CVE-2016-6175
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Thu, 19 Nov 2020 at 02:01, Lucas Nussbaum wrote:
> > src/pault.ag/go/ykpiv/ykpiv.go:539:12: _Ctype_struct_ykpiv_state can't be
> > allocated in Go; it is incomplete (or unallocatable)
> > src/pault.ag/go/ykpiv/ykpiv.go:569:11: _Ctype_struct_ykpiv_state can't be
> > allocated in Go; it is
Subject: calibre: crashes on start
Package: calibre
Version: 5.5.0+dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
After upgrading to version 5.5.0+dfsg-1, calibre crashes on start.
Error logs:
$calibre
Traceback (most recent
On Nov 19, Sven Joachim wrote:
> I am not one of them, but AFAICS that would introduce a fatal circular
> dependency between libc6 and libcrypt1: libc6 needs libcrypt1 to be
> configured before it can be unpacked, but libcrypt1 depends on libc6 so
> it cannot be configured before libc6 is at
: 1.3-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=.
> -fsta
Processing commands for cont...@bugs.debian.org:
> limit source php-gettext
Limiting to bugs with field 'source' containing at least one of 'php-gettext'
Limit currently set to 'source':'php-gettext'
> tags 851771 + pending
Bug #851771 [src:php-gettext] php-gettext: CVE-2016-6175
Added tag(s)
11.0-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201119 ftbfs-bullseye
[...]
> > Checking for Qt >= 5.2.0 ... yes
> > Checking for libzmq >= 2.0 ...
> > * [pkg-config libzmq --exists]
> > * returned: 1
> > -> no
> >
> > Error: need libzmq >= 2.0!
Your message dated Fri, 20 Nov 2020 00:04:35 +
with message-id
and subject line Bug#966922: fixed in libnitrokey 3.5-3.1
has caused the Debian Bug report #966922,
regarding libnitrokey: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output
Control: tags -1 pending
Control: fixed -1 postgis/3.1.0~alpha1+dfsg-1~exp5
This was already fixed in the experimental branch, the fix for unstable
will be uploaded soon.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processing control commands:
> tags -1 pending
Bug #975277 [src:postgis] postgis: autopkgtests missing "skippable" keyword
Added tag(s) pending.
> fixed -1 postgis/3.1.0~alpha1+dfsg-1~exp5
Bug #975277 [src:postgis] postgis: autopkgtests missing "skippable" keyword
The source postgis and version
Processing commands for cont...@bugs.debian.org:
> fixed 975277 postgis/3.1.0~alpha2+dfsg-1~exp1
Bug #975277 [src:postgis] postgis: autopkgtests missing "skippable" keyword
Marked as fixed in versions postgis/3.1.0~alpha2+dfsg-1~exp1.
> thanks
Stopping processing here.
Please contact me if you
Processing commands for cont...@bugs.debian.org:
> severity 975065 serious
Bug #975065 [src:broker] broker: FTBFS
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
975065:
Your message dated Fri, 20 Nov 2020 06:03:56 +
with message-id
and subject line Bug#975277: fixed in postgis 3.0.2+dfsg-5
has caused the Debian Bug report #975277,
regarding postgis: autopkgtests missing "skippable" keyword
to be marked as done.
This means that you claim that the problem has
Control: fixed -1 19.0~alpha3+dfsg1-1
Control: close -1
Dear colleagues,
19.0 Alpha3 is fully compatible with Python3 and I expect Beta1 to be uploaded
to unstable as tgere will be no API changes by upsrream as promised.
Closing this bug manually because I forgot mentionung it in a changelog at
Processing control commands:
> fixed -1 19.0~alpha3+dfsg1-1
Bug #936805 [src:kodi] kodi: Python2 removal in sid/bullseye
The source 'kodi' and version '19.0~alpha3+dfsg1-1' do not appear to match any
binary packages
Marked as fixed in versions kodi/19.0~alpha3+dfsg1-1.
> close -1
Bug #936805
Processing control commands:
> reassign -1 node-yarnpkg
Bug #973741 [gitlab] gitlab: Yarn hasn't been able to find a cache folder it
can use
Bug reassigned from package 'gitlab' to 'node-yarnpkg'.
No longer marked as found in versions gitlab/13.3.8-1.
Ignoring request to alter fixed versions of
Control: reassign -1 node-yarnpkg
Control: affects -1 gitlab
On Wed, 4 Nov 2020 12:22:30 +0200 Dragos Jarca
wrote:
> Dear Maintainer,
>
> Upgrade to 13.3.8.1 failed:
>
> Installing node modules...
> + runuser -u gitlab -- sh -c install -d /var/lib/gitlab/.node_modules
> + runuser -u gitlab --
Source: xygrib
Version: 1.2.6-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linu
Source: deepin-picker
Version: 5.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -g -g -O2 -fde
Source: iannix
Version: 0.9.20~dfsg0-2.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -g -O2 -fde
Source: connectome-workbench
Version: 1.4.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86
Source: ignition-transport
Version: 8.0.0+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin
Source: ghostwriter
Version: 1.8.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -g -O2 -fde
Source: librecad
Version: 2.1.3-1.2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -g -fext-nume
Source: ukui-power-manager
Version: 2.0.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -O2 -std=
Source: litecoin
Version: 0.18.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -std=c++11 -DHAVE_CONFIG_H
Source: phoenix-firmware
Version: 4.7.4+repack1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/lib/gcc/
Source: ktikz
Version: 0.12+ds1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linu
Source: structure-synth
Version: 1.5.0-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -g -O2 -fdebug-pre
Source: supercollider
Version: 1:3.10.4+repack-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bi
Source: spirv-tools
Version: 2020.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-
Source: zint
Version: 2.9.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/cc -g -O2 -fdebug-prefix-
Source: deepin-screen-recorder
Version: 5.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -g
Source: meshlab
Version: 2020.06+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bi
Source: horizon-eda
Version: 1.2.0-3
Severity: serious
Tags: ftbfs
Hi Maintainer
During the recent rebuild for Python 3.9 as default, horizon-eda fails
to build from source [1].
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1]
Package: src:libsigrokdecode
Version: 0.5.3-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9
libsigrokdecode ftbfs with Python 3.9. looks like the headers are detected, but
not the library?
[...]
/bin/bash ./libtool --tag=CC --mode=link gcc
Ok, James, please do that, and I'll upload the change to msgpack.
I don't think msgpack deserves a RC bug for this in the mean time.
Cheers,
Thomas Goirand (zigo)
Source: deepin-music
Version: 5.0.1+ds-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -g -O2 -fde
Source: calligraplan
Version: 1:3.2.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-
Source: lambda-align2
Version: 2.0.0-7
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/build/src &
Source: qpdfview
Version: 0.4.18-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -g -O2 -fdebug-pre
Source: freeciv
Version: 2.6.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 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=
Source: ukui-notification-daemon
Version: 1.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -g
Source: rosegarden
Version: 1:20.06-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linu
1 - 100 of 256 matches
Mail list logo
