On 2021, ഫെബ്രുവരി 14 12:44:09 PM IST, Julian Gilbey wrote:
>Source: node-webpack
>Version: 4.43.0-6
>Severity: serious
>
>webpack depends on node-uglifyjs-webpack-plugin, which in turn has a
>serious bug report against it because it is abandoned upstream.
We should reduce severity of that
Control: reassign -1 0.22.0-1
Control: affects -1 network-manager
Adrian Bunk [2021-02-12 16:22 +0200]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/10412779/log.gz
> test_one_wifi_with_accesspoints (__main__.TestNetworkManager) ... **
>
Processing control commands:
> reassign -1 0.22.0-1
Bug #982613 [src:network-manager] NetworkManager triggers assert in
python-dbusmock test suite
Bug reassigned from package 'src:network-manager' to '0.22.0-1'.
Warning: Unknown package '0.22.0-1'
Warning: Unknown package '0.22.0-1'
No longer
Hello,
On Sat, Feb 13, 2021 at 06:04:32PM +0100, Lucas Nussbaum wrote:
> Source: openssh
> Version: 1:8.4p1-3
> Severity: serious
> Justification: FTBFS on amd64
[...]
> > In file included from ../../sk-usbhid.c:30:
> > /usr/include/sha2.h:57:16: error: redefinition of ‘struct _SHA2_CTX’
[...]
>
Source: node-webpack
Version: 4.43.0-6
Severity: serious
webpack depends on node-uglifyjs-webpack-plugin, which in turn has a
serious bug report against it because it is abandoned upstream.
According to webpack/package.json, webpack does not seem to actually
depend on this plugin, so it should be
ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/build/tests'
> PASS: gtest_test
> FAIL: cppunit_test
>
Processing commands for cont...@bugs.debian.org:
> retitle 982647 spyder-reports: incompatible with spyder 4.2.1+
Bug #982647 [src:spyder-reports] spyder-reports FTBFS with Spyder 4.2.1
Changed Bug title to 'spyder-reports: incompatible with spyder 4.2.1+' from
'spyder-reports FTBFS with Spyder
Hi David,
Axel Beckert wrote:
> > So I guess what is intended here is more like:
> > | char * endptr;
> > | errno = 0;
> > | auto score_tweaks = strtol(action.c_str(), , 10);
> > | if (errno != 0 || *endptr != '\0')
>
> I applied the following patch locally:
>
> ---
Hi Yaroslav,
could you please have a look. I'm occupied by many other things and will not
care for this one.
Kind regards
Andreas.
- Forwarded message from Debian testing autoremoval watch
-
Date: Sun, 14 Feb 2021 04:39:04 +
From: Debian testing autoremoval watch
To:
Processing commands for cont...@bugs.debian.org:
> tags 982716 + pending
Bug #982716 [src:aptitude] aptitude: FTBFS: tests failed
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
982716:
Hi!
Thanks for reporting this bug.
Sadly, I can't reproduce it using sbuild (with and without network).
Utkarsh has asked Holger to try to build using pbuilder without network
to see if he can reproduce it (I don't really have the spoons to set it
up atm).
FWIW, it looks to me like this is not
Gtk2 support and gtk2 for Perl shouldn't be removed. Lots of users
depend on it and GTK3 is not a replacement or viable upgrade path from
gtk2. It doesn't do the same things, it uses significantly more
resources, it's incredibly more buggy, and it puts a dependence on
redhatisms. It is also very
Hi David,
David Kalnischkies wrote:
> On Sat, Feb 13, 2021 at 06:11:03PM +0100, Lucas Nussbaum wrote:
> > Relevant part (hopefully):
> […]
> > > FAIL: cppunit_test
> […]
> | aptitude_resolver.cc:680 ERROR - Invalid hint "-143 aptitude <4.3.0": the
> action "-143" should be "approve", "reject",
ous
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefu
Control: tag -1 pending
Hello,
Bug #982697 in afdko 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 #982697 [src:afdko] afdko: FTBFS: build-dependency not installable:
python3-cu2qu (>= 1.6.7)
Added tag(s) pending.
--
982697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
I *relunctantly* agree that it makes sense to skip bullseye, but I hope
a fork will become a clear winner in time for bookworm. Similar to Axel,
I am still happily using it on buster with firefox-esr. Though I can
reproduce #919557 in a clean profile, it doesn't affect my main one for
some reason.
On Sunday, 14 February 2021 12:14:18 AM AEDT Joerg Jaspert wrote:
> mysql-workbench uses gcc-8 for building, known through bug #944177 for
> more than a year.
>
> Nothing seems to happen, package looks unmaintained. gcc-8 is now
> removed from Debian, so this package either must have an update,
Your message dated Sun, 14 Feb 2021 00:03:25 +
with message-id
and subject line Bug#980699: fixed in grcompiler 5.2-2.2
has caused the Debian Bug report #980699,
regarding grcompiler: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu &&
make -j4 test ARGS\+=-j4 returned exit code 2
to be
Your message dated Sun, 14 Feb 2021 00:48:32 +0100
with message-id
and subject line Re: Bug#980699: RFS: grcompiler/5.2-2.2 [NMU] [RC] -- Compiler
of smart (graphite) fonts
has caused the Debian Bug report #980699,
regarding grcompiler: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu &&
On Mon, 2 Mar 2020 17:16:09 +0800 Alvin Chen wrote:
> You can use an alternative header like p11-kit which is licensed under
> a more liberal license.
I had a look at the PKCS #11 headers; the biggest problem is that NSS
uses version 3.00 while the p11-kit headers have been forked at 2.40 and
not
Related to:
RM: cu2qu -- ROM; merged to fonttools
https://bugs.debian.org/981426
--
Samuel Henrique
Thanks to bits from the RT. I can't reproduce this issue on a minimal
installation, and the upgrade path has also been fixed #972820.
--
Phil Morrell (emorrp1)
```
$ sudo sbuild-createchroot --command-prefix=eatmydata --include=eatmydata
buster --chroot-prefix=temporary /srv/chroot/temporary
Processing commands for cont...@bugs.debian.org:
> tags 982716 + confirmed
Bug #982716 [src:aptitude] aptitude: FTBFS: tests failed
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
982716:
Hi David,
you were quicker. Thanks! :-)
David Kalnischkies wrote:
> On Sat, Feb 13, 2021 at 06:11:03PM +0100, Lucas Nussbaum wrote:
> > Relevant part (hopefully):
> […]
> > > FAIL: cppunit_test
> […]
> | aptitude_resolver.cc:680 ERROR - Invalid hint "-143 aptitude <4.3.0": the
> action "-143"
On Sat, Feb 13, 2021 at 05:17:59PM +0100, Matthijs Kooijman wrote:
> > Upstream have re-exported the pcx files and I can confirm nml now builds
> > correctly with these 3 files copied into place before tests.
> Cool, thanks for confirming. It would be obvious to just backport these
> changes, but
-collections
Version: 10.4.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpack
On Sat, Feb 13, 2021 at 06:11:03PM +0100, Lucas Nussbaum wrote:
> Relevant part (hopefully):
[…]
> > FAIL: cppunit_test
[…]
| aptitude_resolver.cc:680 ERROR - Invalid hint "-143 aptitude <4.3.0": the
action "-143" should be "approve", "reject", or a number.
The test uses
Lucas,
The renderdoc package was marked with autorm based on this bug.
The issue arose because glslang 11.1.0-1 was uploaded to unstable.
I therefore released renderdoc 1.11+dfsg-5 which fixed the
compatibility issue with glslang 11.
Unfortunately, I then found out that glslang 11 was actually
severity 982647 grave
thanks
On Fri, Feb 12, 2021 at 10:48:48PM +0200, Adrian Bunk wrote:
> Source: spyder-reports
> Version: 0.1.1-4
> Severity: serious
> Tags: ftbfs
Thanks for picking this one up, Adrian. It turns out that it is
actually an upstream bug and this package is currently not
Processing commands for cont...@bugs.debian.org:
> severity 982647 grave
Bug #982647 [src:spyder-reports] spyder-reports FTBFS with Spyder 4.2.1
Severity set to 'grave' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
982647:
Processing control commands:
> tag -1 + confirm
Unknown tag/s: confirm.
Recognized are: patch wontfix moreinfo unreproducible help security upstream
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed
fixed-in-experimental sid experimental potato woody sarge
Control: tag -1 + confirm
Hi Lucas,
thanks for the bug report!
Lucas Nussbaum wrote:
> Source: aptitude
> Version: 0.8.13-2
> Severity: serious
[…]
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Indeed, can reproduce it here locally despite it still worked
e: guile-ssh
Version: 0.13.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 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 '/<>/d
Source: live-build
Version: 1:20210122
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package live-build, great.
However, it fails on amd64, armhf and ppc64el.
essage ---
Source: libbtm-java
Version: 2.1.4-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Your message dated Sat, 13 Feb 2021 21:59:01 +0100
with message-id <68a2c568-9bbd-f141-cb26-563617ea3...@debian.org>
and subject line Re: autopkgtest flaky on arm64
has caused the Debian Bug report #977268,
regarding autopkgtest flaky on arm64
to be marked as done.
This means that you claim that
Processing control commands:
> tag -1 pending
Bug #982727 [src:libbtm-java] libbtm-java: FTBFS: [javac]
/<>/src/bitronix/tm/resource/ResourceLoader.java:32: error:
package javax.jms does not exist
Added tag(s) pending.
--
982727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982727
Control: tag -1 pending
Hello,
Bug #982727 in libbtm-java 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:
---
Source: maven-reporting-exec
Version: 1.4-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
&
-resolver
Version: 1.4.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 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
Processing control commands:
> tag -1 pending
Bug #982710 [src:maven-reporting-exec] maven-reporting-exec: FTBFS: Could not
resolve dependencies for project org.apache.maven.reporting:maven-reporting-exec
Added tag(s) pending.
--
982710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982710
Control: tag -1 pending
Hello,
Bug #982710 in maven-reporting-exec 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:
Control: tags -1 patch
Hi,
On Mon, 23 Nov 2020 11:25:35 +0100 Matthias Klose wrote:
> Package: src:dh-python
> Version: 4.20201102
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9
>
> dh-python's autopkg tests fail with Python 3.9. Please
Processing control commands:
> tags -1 patch
Bug #975536 [src:dh-python] dh-python's autopkg tests fail with Python 3.9
Added tag(s) patch.
--
975536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #982708 [src:maven-resolver] maven-resolver: FTBFS: Could not resolve
dependencies for project org.apache.maven.resolver:maven-resolver-impl
Added tag(s) pending.
--
982708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982708
Debian Bug
Control: tag -1 pending
Hello,
Bug #982708 in maven-resolver 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:
Package: pulseaudio
Version: 14.2-1
Severity: serious
Pulseaudio is failing to build on ppc64el. The version of pulseaudio in
bullseye suffers from a pretty serious usability bug (see #980836)
which should arguably be a higher severity, but let's focus on getting
14.2-1 built properly.
---
Source: libatteanx-serializer-rdfa-perl
Version: 0.100-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Processing control commands:
> tag -1 pending
Bug #982722 [src:libatteanx-serializer-rdfa-perl]
libatteanx-serializer-rdfa-perl: FTBFS: dh_auto_test: error: make -j1 test
TEST_VERBOSE=1 returned exit code 2
Added tag(s) pending.
--
982722:
Control: tag -1 pending
Hello,
Bug #982722 in libatteanx-serializer-rdfa-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:
Processing commands for cont...@bugs.debian.org:
> retitle 982729 octave-msh: FTBFS: msh2m_gmsh: the gmsh subprocess exited
> abnormally
Bug #982729 [src:octave-msh] octave-msh: FTBFS: chmod: cannot access
'debian/*/usr/lib/*/octave/packages/*/*/*.mex': No such file or directory
Changed Bug
Control: tags 98728 confirmed
On 2021-02-13, Lucas Nussbaum wrote:
> Source: guile-ssh
> Version: 0.13.1-3
> Severity: serious
> Justification: FTBFS on amd64
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>> make[5]: Entering directory
Hi Martin,
since you are more familiar with python-dbusmock:
does that ring a bell?
On Fri, 12 Feb 2021 16:22:14 +0200 Adrian Bunk wrote:
> Source: network-manager
> Version: 1.29.90-1
> Severity: serious
>
>
On 2021, ഫെബ്രുവരി 13 8:19:52 PM IST, Chris Hofstaedtler
wrote:
>Hi,
>
>* Debian Bug Tracking System [210213 14:48]:
>> #980580: ruby-ruby2ruby: FTBFS: ERROR: Test "ruby2.7" failed: RuntimeError:
>> unknown arg type nil
>
>have you noticed the autopkgtest failures on all archs?
Yes, it
Your message dated Sat, 13 Feb 2021 18:48:57 +
with message-id
and subject line Bug#937051: fixed in mininet 2.3.0-1
has caused the Debian Bug report #937051,
regarding mininet: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 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 '/<>/docs'
> Running Sphinx v3.4.3
> making output directory... done
> buil
close #982464
On Sat, Feb 13, 2021 at 5:03 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
> Your message dated Sat, 13 Feb 2021 17:02:07 +
> with message-id
> and subject line Bug#982464: fixed in subversion 1.10.4-1+deb10u2
> has caused the Debian Bug report #982464,
>
On Sat, Feb 13, 2021 at 02:14:18PM +0100, Joerg Jaspert wrote:
> Package: mysql-workbench
> Severity: serious
>...
> Nothing seems to happen, package looks unmaintained.
>...
> I intend to do this myself in 3 weeks, if there is no reply. So if you are
> on it and need a little more time, please
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: test-check-clojure
Version: 0.9.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/bash ../libtool --tag=CC --mode=link gcc -I/usr/include/libpng16
> -I/usr/include/openjpeg-
Processing commands for cont...@bugs.debian.org:
> tag 979838 patch
Bug #979838 [src:twisted] twisted: autopkgtest regression in testing: No such
file or directory: 'ckeygen'
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979838:
Your message dated Sat, 13 Feb 2021 18:19:00 +
with message-id
and subject line Bug#981398: fixed in sa-exim 4.2.1-20
has caused the Debian Bug report #981398,
regarding sa-exim: not installable with bullseye's exim4
to be marked as done.
This means that you claim that the problem has been
Control: tags -1 pending
On 2/13/21 6:28 PM, Lucas Nussbaum wrote:
>> Exception occurred:
>> File "/usr/lib/python3/dist-packages/sphinxarg/parser.py", line 40, in
>> _try_add_parser_attribute
>> data[attribname] = attribval % {'prog': data['prog']}
>> KeyError: 'prog'
>> The full
Processing control commands:
> tags -1 pending
Bug #982698 [src:python-pyproj] python-pyproj: FTBFS: KeyError: 'prog'
Added tag(s) pending.
--
982698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> reassign -1 src:spatialite
Bug #982732 [src:librasterlite2] librasterlite2: FTBFS: ld: cannot find -lfreexl
Bug reassigned from package 'src:librasterlite2' to 'src:spatialite'.
No longer marked as found in versions librasterlite2/1.1.0~beta1-2.
Ignoring request to
Control: reassign -1 src:spatialite
Control: found -1 spatialite/5.0.1-1
Control: affects -1 src:librasterlite2
Control: tags -1 pending
On 2/13/21 6:04 PM, Lucas Nussbaum wrote:
>> /usr/bin/ld: cannot find -lfreexl
>> /usr/bin/ld: cannot find -lgeos_c
This is caused by spatialite exposing the
Processing commands for cont...@bugs.debian.org:
> forwarded 982613
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/662
Bug #982613 [src:network-manager] Debian Python Team
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> retitle 982613 NetworkManager triggers assert in python-dbusmock test suite
Bug #982613 [src:network-manager] Debian Python Team
Changed Bug title to 'NetworkManager triggers assert in python-dbusmock test
suite' from 'Debian Python Team '.
>
On Saturday 13 February 2021 18:32:17 Lucas Nussbaum wrote:
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > debian/rules build
> > dh build --buildsystem=bmake
> >dh_update_autotools_config -O--buildsystem=bmake
Processing commands for cont...@bugs.debian.org:
> # now affects unstable
> severity 981100 serious
Bug #981100 [src:bind-dyndb-ldap] FTBFS with bind9 >= 9.16.10
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
981100:
Source: delve
Version: 1.6.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ===
Source: opam
Version: 2.0.7-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering direct
Source: librasterlite2
Version: 1.1.0~beta1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/bash ../libt
Source: aspell-sk
Version: 2.02-0-7
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: freedict
Version: 2021.01.05-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering direct
Source: guile-ssh
Version: 0.13.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[5]: Entering direct
Source: octave-msh
Version: 1.0.10-11
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: libbtm-java
Version: 2.1.4-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: panicparse
Version: 1.3.0-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpack
Source: lepton-eda
Version: 1.9.13-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[6]: Entering direct
Source: massxpert
Version: 6.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[6]: Entering direct
Source: ruby-rails-html-sanitizer
Version: 1.3.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/ruby
Source: libatteanx-serializer-rdfa-perl
Version: 0.100-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Source: firehol
Version: 3.1.6+ds-10
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 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: snapd
Version: 2.48.2-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: golang-github-jacobsa-ogletest
Version: 0.0~git20170503.80d50a7-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: test-check-clojure
Version: 0.9.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Enter
Source: msxpertsuite
Version: 5.8.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[6]: Entering direct
Source: udfclient
Version: 0.8.11-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 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
Source: aptitude
Version: 0.8.13-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering direct
Source: ruby-redis-rack
Version: 2.1.2-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ArgumentError: unkn
Source: tiledarray
Version: 0.6.0-5.2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /<>/src/TiledA
Source: bsdowl
Version: 2.2.2-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 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
&
Source: maven-reporting-exec
Version: 1.4-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
&
Source: direnv
Version: 2.25.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering direct
Source: ruby-redis-activesupport
Version: 5.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ArgumentEr
Source: maven-resolver
Version: 1.4.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
&
Source: openssh
Version: 1:8.4p1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cc -g -O2 -ffile-prefix-
Source: gcc-m68hc1x
Version: 1:3.3.6+3.1+dfsg-3.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /<>/build
1 - 100 of 153 matches
Mail list logo
