Your message dated Thu, 08 Apr 2021 03:03:22 +
with message-id
and subject line Bug#986420: fixed in smart-notifier 0.28-7
has caused the Debian Bug report #986420,
regarding ModuleNotFoundError: No module named 'gi' (missing dependency on
python3-gi ?)
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> forcemerge 986612 856963
Bug #986612 [wnpp] ITP: sass-stylesheets-purecss -- set of small, responsive
Sass and CSS modules
Bug #856963 [wnpp] ITP: purecss -- set of small and responsive CSS modules
980134 was blocked by: 978697 856963
980134 was
Hi all,
2021年4月7日(水) 18:39 Andreas Henriksson :
>
> Control: severity -1 grave
>
> On Wed, Apr 07, 2021 at 11:20:18AM +0200, Bastian Germann wrote:
> > Control: severity -1 important
> >
> > Am 07.04.21 um 11:10 schrieb Andreas Henriksson:
> > > Could we please just add a patch that either just
Processing control commands:
> tag 983648 + fixed-upstream
Bug #983648 [kpatch-dkms] kpatch-dkms: fails to build module for Linux 5.10:
uses unknown struct stack_trace
Added tag(s) fixed-upstream.
> block 983648 by -1
Bug #983648 [kpatch-dkms] kpatch-dkms: fails to build module for Linux 5.10:
Hello,
I am from the NuGet team at Microsoft. Network Security Services (NSS) 3.63 and
newer distrusts Symantec which will cause failures when installing NuGet
packages. For more information, please see:
* https://github.com/dotnet/announcements/issues/180
*
Processing commands for cont...@bugs.debian.org:
> severity 986552 important
Bug #986552 [src:linux] linux-image-4.19.0-14-amd64: KVM crashes with list_add
corruption kernel BUG
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Package: courier-mlm
Version: 1.0.14-1
Severity: grave
Justification: renders package unusable
now found is a debian problem, the courier-mlm documents said in clear way
that cannot be use any shell constructs or script trick, and cannot use quotes,
the debian file has: PIDFILE={PORT}.pid and
Your message dated Wed, 07 Apr 2021 21:48:59 +
with message-id
and subject line Bug#986256: fixed in simka 1.5.3-4
has caused the Debian Bug report #986256,
regarding simka: flaky amd64 autopkgtest: regularly times out after 2:47 h
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> severity 986577 serious
Bug #986577 [bouncy] bouncy: Fails to run without missing dependency
python3-future
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
986577:
Your message dated Wed, 07 Apr 2021 21:33:36 +
with message-id
and subject line Bug#986513: fixed in puppetlabs-http-client-clojure 1.2.0-2
has caused the Debian Bug report #986513,
regarding puppetlabs-http-client-clojure: FTBFS: ERROR in
(sync-client-test-ssl-protocols)
Processing commands for cont...@bugs.debian.org:
> severity 986420 serious
Bug #986420 [smart-notifier] ModuleNotFoundError: No module named 'gi' (missing
dependency on python3-gi ?)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need
Hi Graham,
Graham Inggs, on 2021-04-06 20:15:30 +0200:
> This is still occurring with simka 1.5.3-3, see:
> https://ci.debian.net/packages/s/simka/testing/amd64/
Thanks for having noticed it. It looks like I got caught by the
Python script not taking the -nb-cores argument, contrary to the
Andreas Tille writes:
> do you have possibly any hint what might be wrong here?
Thanks for calling this bug to my attention! Based on reports I've seen
upstream, I suspect the problem may lie in some relatively new
usage-reporting code that Debian should probably disable by default
regardless,
Processing control commands:
> tag -1 pending
Bug #986513 [src:puppetlabs-http-client-clojure]
puppetlabs-http-client-clojure: FTBFS: ERROR in
(sync-client-test-ssl-protocols) (HttpAsyncRequestExecutor.java:356) should not
connect to a server when protocols don't overlap clojure sync client
Control: tag -1 pending
Hello,
Bug #986513 in puppetlabs-http-client-clojure 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:
Your message dated Wed, 07 Apr 2021 20:18:48 +
with message-id
and subject line Bug#983492: fixed in alien 8.95.4
has caused the Debian Bug report #983492,
regarding alien incorrectly generates debian/rules
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing control commands:
> tags -1 help
Bug #986592 [src:kleborate] kleborate: flaky arm64 autopkgtest: Mutex is not
owned by current thread
Added tag(s) help.
--
986592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags -1 help
Hi Aaron,
do you have possibly any hint what might be wrong here?
Kind regards
Andreas.
On Wed, Apr 07, 2021 at 09:35:42PM +0200, Paul Gevers wrote:
> Source: kleborate
> Version: 2.0.1-1
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC:
I have been able to reproduce this bug locally with sbuild, on a machine
that has network access.
This is thus not a failure caused by a network connection being required
to the testsuite.
I opened a bug upstream
(https://github.com/puppetlabs/clj-http-client/issues/85) but the
failure seems
Processing control commands:
> severity -1 grave
Bug #983492 [alien] alien incorrectly generates debian/rules
Severity set to 'grave' from 'important'
--
983492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: kleborate
Version: 2.0.1-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
Your package has an autopkgtest, great. However, I looked into the
history of your autopkgtest [1] and I noticed
Source: dbus-test-runner
Version: 16.10.0~bzr100+repack1-4.1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org, t...@canonical.com
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
Your package has an autopkgtest, great. However, I looked into
the
Processing control commands:
> tags -1 patch
Bug #908017 [src:network-manager-iodine] network-manager-iodine FTBFS with glib
2.58
Added tag(s) patch.
--
908017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/rules: Set --enable-more-warnings to "yes" so that it doesn't default to
"error," which turns every warning into an error and causes an FTBFS due
to deprecated declarations.
Thanks for
The bug occurs on all systems with sufficiently new GNU libc, not just Debian,
so it is an upstream bug.
Unfortunately the mailing list mentioned on the linked homepage is dead (even
the server is) and I failed to find any other, more recent continuation or fork
of the project.
Processing commands for cont...@bugs.debian.org:
> unarchive 939419
Bug #939419 {Done: Mathieu Parent } [libparse-pidl-perl]
libparse-pidl-perl: version ordering issue.
Unarchived Bug 939419
> # this still needs to be fixed in stable
> severity 939419 serious
Bug #939419 {Done: Mathieu Parent }
Your message dated Wed, 07 Apr 2021 15:34:17 +
with message-id
and subject line Bug#986524: fixed in freecontact 1.0.21-9
has caused the Debian Bug report #986524,
regarding freecontact: FTBFS: devlibs error: There is no package matching
[libgfortran-8-dev] and noone provides it, please
Source: darktable
Version: 3.4.0-2
Severity: serious
Tags: ftbfs
darktable fails to build from source when adding parallel=1 to
DEB_BUILD_OPTIONS. Note that this is independent of the number of actual
CPU cores. I suppose that there is a missing dependency relation among
CMake targets. Here is
Your message dated Wed, 07 Apr 2021 15:03:31 +
with message-id
and subject line Bug#982692: fixed in gemma 0.98.4+dfsg-3
has caused the Debian Bug report #982692,
regarding gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> forwarded 985948
> https://salsa.debian.org/debian/libubootenv/-/merge_requests/3
Bug #985948 [libubootenv-tool] libubootenv-tool: Debug lines from fw_printenv
break RAUC
Set Bug forwarded-to-address to
Hello again,
On Wed, Apr 07, 2021 at 11:36:30AM +0200, Andreas Henriksson wrote:
[...]
> I've submitted a merge-request that fixes the imminent problems for
> review at:
> https://salsa.debian.org/debian/libubootenv/-/merge_requests/3
[...]
I've studied things a bit more and updated the
On Wed, Apr 7, 2021 at 3:01 PM Lucas Nussbaum wrote:
>
> Source: golang-github-vdemeester-shakers
> Version: 0.0~git20160210.0.24d7f1d-2.1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210406 ftbfs-bullseye
>
The package is a leaf Go library,
Package: git-flow
Version: 1.12.3-1
Severity: grave
Tags: patch
Today 'flow' is not a supported git command:
$git flow
git: 'flow' is not a git command. See 'git --help'.
The most similar commands are
reflog
show
Running it under strace reveals that git looks for commands
Processing commands for cont...@bugs.debian.org:
> severity #986037 important
Bug #986037 [kdenlive] kdenlive: crashes on audio setup
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
986037:
severity #986037 important
thanks
Hi Norbert and Dan,
Am 28.03.21 um 14:11 schrieb Norbert Preining:
Package: kdenlive
Version: 20.12.3-1
Severity: grave
Since (for myself?) this issue does not affect Debian bullseye
downgrading the severity, because this release could not migrate then..
Processing commands for cont...@bugs.debian.org:
> tags 982991 + bullseye
Bug #982991 [src:matrix-synapse] matrix-synapse: not suitable for inclusion
into bullseye
Added tag(s) bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
982991:
I apologize for the empty form, this was the first time I used
reportbug. I hope it is ok if I answer the question in this message.
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
The latest update of Emacs on debian
Package: emacs
Version: 1:27.1+1-3.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
Your message dated Wed, 07 Apr 2021 10:48:51 +
with message-id
and subject line Bug#980628: fixed in libsass-python 0.20.1-3
has caused the Debian Bug report #980628,
regarding libsass-python: FTBFS: tests failed
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 07 Apr 2021 10:18:28 +
with message-id
and subject line Bug#986508: fixed in binutils-mipsen 7+c2
has caused the Debian Bug report #986508,
regarding binutils-mipsen: FTBFS: /bin/bash: line 1: debugedit: command not
found
to be marked as done.
This means that you
Processing control commands:
> tag -1 moreinfo
Bug #986544 [ca-certificates] ca-certificates: change versioning scheme
Added tag(s) moreinfo.
> severity -1 wishlist
Bug #986544 [ca-certificates] ca-certificates: change versioning scheme
Severity set to 'wishlist' from 'serious'
--
986544:
Control: tag -1 moreinfo
Control: severity -1 wishlist
On Wed, Apr 07, 2021 at 11:40:34AM +0200, Andreas Beckmann wrote:
> Package: ca-certificates
> Version: 20210119
> Severity: serious
>
> Hi,
>
> as I had commented on
> https://salsa.debian.org/debian/ca-certificates/-/merge_requests/6
>
>
Package: ca-certificates
Version: 20210119
Severity: serious
Hi,
as I had commented on
https://salsa.debian.org/debian/ca-certificates/-/merge_requests/6
After seeing the new version scheme for debian-security-support (sid now
has 1:11+2021.01.23), I was thinking whether something similar would
These are harmless failures because of FP. So, yes, comment them out.
I need to rewrite the test system, sorry.
On Wed, Apr 07, 2021 at 10:56:54AM +0200, Andreas Tille wrote:
> Hi Lucas,
>
> On Wed, Apr 07, 2021 at 08:49:27AM +0200, Lucas Nussbaum wrote:
> > I confirm that I can still reproduce
Processing control commands:
> severity -1 grave
Bug #985948 [libubootenv-tool] libubootenv-tool: Debug lines from fw_printenv
break RAUC
Severity set to 'grave' from 'important'
--
985948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985948
Debian Bug Tracking System
Contact
Your message dated Wed, 07 Apr 2021 09:33:28 +
with message-id
and subject line Bug#986520: fixed in mkvtoolnix 54.0.0-2
has caused the Debian Bug report #986520,
regarding mkvtoolnix: FTBFS:
src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error:
Segmentation fault
to
Processing control commands:
> severity -1 important
Bug #985948 [libubootenv-tool] libubootenv-tool: Debug lines from fw_printenv
break RAUC
Severity set to 'important' from 'grave'
--
985948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985948
Debian Bug Tracking System
Contact
Control: severity -1 important
Am 07.04.21 um 11:10 schrieb Andreas Henriksson:
Could we please just add a patch that either just rips out the NDEBUG
lines (or inverts the login to #ifdef DEBUG ) ?! Such a patch could/should
be forwarded upstream as well A library should not print to stdout
Hi,
On 07/04/21 at 10:56 +0200, Andreas Tille wrote:
> Hi Lucas,
>
> On Wed, Apr 07, 2021 at 08:49:27AM +0200, Lucas Nussbaum wrote:
> > I confirm that I can still reproduce this failure in a testing chroot.
>
> Thank you for your information. I have tried to create a diff between
> the
Control: affects -1 mender-client
Hi,
On Sat, Apr 03, 2021 at 02:52:34PM +0200, Bastian Germann wrote:
> Control: tags -1 patch
>
> A patch is enclosed.
[...]
> CMAKE_FLAGS = \
> -DCMAKE_VERBOSE_MAKEFILE=ON \
> - -DCMAKE_C_FLAGS_RELEASE="$(CFLAGS)" \
> +
Processing control commands:
> affects -1 mender-client
Bug #985948 [libubootenv-tool] libubootenv-tool: Debug lines from fw_printenv
break RAUC
Added indication that 985948 affects mender-client
--
985948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985948
Debian Bug Tracking System
Processing control commands:
> fixed -1 10.2.1-24
Bug #986520 [src:mkvtoolnix] mkvtoolnix: FTBFS:
src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error:
Segmentation fault
The source 'mkvtoolnix' and version '10.2.1-24' do not appear to match any
binary packages
Marked as
Control: fixed -1 10.2.1-24
Please work around it by using gcc-9 for bullseye. I'm not going to cherry-pick
single patches from the branch.
As said in https://lists.debian.org/debian-release/2021/03/msg00027.html
I'll provide GCC 10.3 for backports.
Please work around it by using gcc-9 for bullseye. I'm not going to cherry-pick
single patches from the branch.
As said in https://lists.debian.org/debian-release/2021/03/msg00027.html
I'll provide GCC 10.3 for backports.
Hi Lucas,
On Wed, Apr 07, 2021 at 08:49:27AM +0200, Lucas Nussbaum wrote:
> I confirm that I can still reproduce this failure in a testing chroot.
Thank you for your information. I have tried to create a diff between
the successful build log of the autobuilders[1] where all architectures
have
Processing commands for cont...@bugs.debian.org:
> reopen 985948
Bug #985948 {Done: Nobuhiro Iwamatsu } [libubootenv-tool]
libubootenv-tool: Debug lines from fw_printenv break RAUC
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and
Processing commands for cont...@bugs.debian.org:
> forcemerge 986518 986521
Bug #986518 [ant] starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid
flag: -Xdoclint:none
Bug #986521 [ant] starjava-ttools: FTBFS: [javadoc] javadoc: error - invalid
flag: -Xdoclint:none
Removed indication that
Processing commands for cont...@bugs.debian.org:
> merge 986518 986521
Bug #986518 [ant] starjava-topcat: FTBFS: [javadoc] javadoc: error - invalid
flag: -Xdoclint:none
Unable to merge bugs because:
affects of #986521 is 'starjava-ttools,starjava-topcat' not
'starjava-topcat,starjava-ttools'
Processing control commands:
> reassign -1 ant 1.10.9-3
Bug #986521 [src:starjava-ttools] starjava-ttools: FTBFS: [javadoc] javadoc:
error - invalid flag: -Xdoclint:none
Bug reassigned from package 'src:starjava-ttools' to 'ant'.
No longer marked as found in versions starjava-ttools/3.4-2.
Control: reassign -1 ant 1.10.9-3
Control: affects -1 starjava-topcat starjava-ttools
Dear maintainer,
The latest ant package adds a flag -Xdoclint:none to the Javadoc
execution, which is however not recognized by javadoc. The JDK used in
the package was openjdk 11.0.11+4-1.
Best regards
Processing control commands:
> reassign -1 ant 1.10.9-3
Bug #986518 [src:starjava-topcat] starjava-topcat: FTBFS: [javadoc] javadoc:
error - invalid flag: -Xdoclint:none
Bug reassigned from package 'src:starjava-topcat' to 'ant'.
No longer marked as found in versions starjava-topcat/4.8-2.
control: reassign -1 gcc-10
control: found -1 10.2.1-6
control: affects -1 src:nheko
control: fixed -1 10.2.1-24
This is fixed in experimental since long time, not sure which release between
-16 and -24 fixed it.
G.
Processing control commands:
> reassign -1 gcc-10
Bug #986519 [src:nheko] nheko: FTBFS: internal compiler error
Bug reassigned from package 'src:nheko' to 'gcc-10'.
No longer marked as found in versions nheko/0.7.2-3.
Ignoring request to alter fixed versions of bug #986519 to the same values
On 07 avril 2021 08:31, Lucas Nussbaum wrote:
> Source: mkvtoolnix
> Version: 52.0.0-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210406 ftbfs-bullseye
>
> Hi,
Hi,
> During a rebuild of all packages in bullseye, your package failed to
Processing control commands:
> severity -1 serious
Bug #982692 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check
returned exit code 2
Severity set to 'serious' from 'important'
> tags -1 - moreinfo
Bug #982692 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check
returned
Source: httpcomponents-client
Version: 4.5.13-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules
Processing control commands:
> severity -1 serious
Bug #980628 [src:libsass-python] libsass-python: FTBFS: tests failed
Severity set to 'serious' from 'important'
--
980628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Source: gvm-libs
Severity: serious
X-Debbugs-Cc: sop...@offensive-security.com
The gvm tools suite should not be in Debian Stable.
Upstream regularly releases new versions and the old versions become
obsolete and sometimes unusable.
My goal is to get rid of all the source packages of GVM tools:
Source: yarl
Version: 1.6.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
Source: openjdk-17
Version: 17~11-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: freecontact
Version: 1.0.21-8
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: odb
Version: 2.4.0-13
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/bash ../libtool --tag=CXX
Source: golang-github-vdemeester-shakers
Version: 0.0~git20160210.0.24d7f1d-2.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part
Source: nheko
Version: 0.7.2-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
This is caused by #980629 which is fixed in experimental, but
Source: mkvtoolnix
Version: 52.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
This is caused by #980596, but at this point I don't
Source: starjava-ttools
Version: 3.4-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: piglit
Version: 0~git20200212-f4710c51b-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/ld:
Source: starjava-topcat
Version: 4.8-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: python-escript
Version: 5.6-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: siconos
Version: 4.3.1+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering
Source: libunity
Version: 7.1.4+19.04.20190319-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> make[5]:
Source: python-jenkinsapi
Version: 0.3.11-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: bind-dyndb-ldap
Version: 11.6-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc version 10.2.1
Source: puppetlabs-http-client-clojure
Version: 1.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]:
Source: lintian-brush
Version: 0.99
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
>
Source: binutils-mipsen
Version: 7+c1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye
Hi,
During a rebuild of all packages in bullseye, your package failed to build
on amd64.
Relevant part (hopefully):
> make[5]: Entering
86 matches
Mail list logo
