Le 26/10/2020 à 20:50, Paolo Greppi a écrit :
> Hi Xavier,
>
> Il 26/10/20 20:24, Xavier ha scritto:
>> Le 26/10/2020 à 15:28, ano...@users.sourceforge.net a écrit :
>>> ...
>>
>> Hi JS Team,
>>
>> yarnpkg is not in testing due to babel problems. Do you agree to
>> dicrease severity of this bug
Zitat von Sebastian Andrzej Siewior :
Could you please tell the permissions for
/var/log/clamav/
/var/log/clamav/freshclam.log
?
Sebastian
Hi Sebastian,
the permissions are:
/var/log/clamav
drwxr-xr-x 2 clamav clamav 4,0K 27. Okt 08:14 clamav
ls -lah /
Processing commands for cont...@bugs.debian.org:
> reassign 972952 yarnpkg
Bug #972952 [node-mkdirp] node-mkdirp 1.0 is incompatible with 0.5, breaks
yarnpkg
Bug reassigned from package 'node-mkdirp' to 'yarnpkg'.
No longer marked as found in versions node-mkdirp/1.0.4-2.
Ignoring request to alte
Your message dated Tue, 27 Oct 2020 07:48:41 +
with message-id
and subject line Bug#972918: fixed in virtualbox 6.1.16-dfsg-3
has caused the Debian Bug report #972918,
regarding virtualbox ftbfs with python3.9
to be marked as done.
This means that you claim that the problem has been dealt wit
Processing commands for cont...@bugs.debian.org:
> severity 972952 grave
Bug #972952 [yarnpkg] yarnpkg isn't compatible with recent node-mkdirp
Severity set to 'grave' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
972952: https://bugs.debian.org/
Source: gr-air-modes
Version: 0.0.20190917-2
Severity: serious
Tags: ftbfs
Hi Maintainer
As per reproducible builds [1], gr-air-modes recently started failing
to build in unstable.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1]
https://tests.reproducible-bu
Source: gr-gsm
Version: 0.42.2.20200214-1
Severity: serious
Tags: ftbfs
Hi Maintainer
As per reproducible builds [1], gr-gsm recently started failing to
build in unstable.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1]
https://tests.reproducible-builds.org/
Package: pcp
Version: 5.2.1-1
Severity: serious
Tags: patch
The recent 5.2.1-1 upload made a dependency change to pcp:
Package: pcp
-Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl,
python3-pcp, python3, libpcp-web1
+Depends: ${shlibs:Depends}, ${misc:Depends}, gawk
Processing control commands:
> tag -1 pending
Bug #972153 [src:python-fakeredis] python-fakeredis autopkg test fails
Added tag(s) pending.
--
972153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #972153 in python-fakeredis 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/python-team/packages/python-fakeredis/-/commit/5e
Processing commands for cont...@bugs.debian.org:
> forcemerge 972153 972095
Bug #972153 [src:python-fakeredis] python-fakeredis autopkg test fails
Unable to merge bugs because:
package of #972095 is 'python-fakeredis' not 'src:python-fakeredis'
Failed to forcibly merge 972153: Did not alter merged
Your message dated Tue, 27 Oct 2020 08:48:37 +
with message-id
and subject line Bug#972153: fixed in python-fakeredis 1.4.4-1
has caused the Debian Bug report #972153,
regarding python-fakeredis autopkg test fails
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> forwarded 972952 https://github.com/yarnpkg/yarn/issues/8417
Bug #972952 [yarnpkg] yarnpkg isn't compatible with recent node-mkdirp
Set Bug forwarded-to-address to 'https://github.com/yarnpkg/yarn/issues/8417'.
>
End of message, stopping processin
I confirm this issue on bullseye.
There is also a similar one with clamav-daemon:
# systemctl status clamav-daemon
● clamav-daemon.service - Clam AntiVirus userspace daemon
Loaded: loaded (/lib/systemd/system/clamav-daemon.service;
enabled; vendor preset: enabled)
Drop-In: /etc/systemd/sy
Your message dated Tue, 27 Oct 2020 10:00:13 +
with message-id
and subject line Bug#972659: fixed in tpm2-tss 3.0.1-2
has caused the Debian Bug report #972659,
regarding libtss2-esys0: bumps SONAME without changing package name
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 27 Oct 2020 10:00:11 +
with message-id
and subject line Bug#894789: fixed in tightvnc-java 1.3.10-1
has caused the Debian Bug report #894789,
regarding tightvnc-java: FTBFS with openjdk-9
to be marked as done.
This means that you claim that the problem has been dealt w
On 2020-10-27 10:34:13 +0100, Felix Stupp wrote:
> Can someone please mark the bug in a way that also the nvidia-driver
> package is affected / causing this bug so apt-listbugs can show this
> bug to users before upgrading the kernel / installing the
> nvidia-driver?
I had already marked linux-ima
On Tue, Oct 27, 2020 at 07:51:04AM +, Debian Bug Tracking System wrote:
> kylin-video (2.1.1.1-1) unstable; urgency=medium
> .
>[ Dmitry Shachnev ]
>* Fix build with Qt 5.15 again. (Closes: #972156)
This version works fine, thank you!
--
Dmitry Shachnev
signature.asc
Description:
Control: severity -1 important
On 10/26/20 1:04 PM, Adrian Bunk wrote:
> Package: libgcc-s1
> Version: 10.2.0-15
> Severity: grave
>
> On a buster system, with unstable pinned to low priority:
Lowering the severity. Feel free to correct me if this specific configuration
deserves RC severity.
Processing control commands:
> severity -1 important
Bug #972936 [libgcc-s1] libgcc-s1 needs Breaks: libgcc1 (<< 1:10)
Severity set to 'important' from 'grave'
--
972936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with proble
Package: src:pybind11
Version: 2.5.0-5
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
autopkgtest [19:02:38]: test command4: set -e ; cp -r tests ${AUTOPKGTEST_TMP} ;
cd ${AUTOPKGTEST_TMP}/tests ; cmake . ; make ; pytest-3
autopkgtest [19:02:38]: test
Hi Dmitry,
I just uploaded a new version of clementine disabling projectm for now
because I have also others issues related to its integration. I need a
bit of time to work on this.
So for now the new version of clementine I uploaded include a new
upstream version (small, 1 bugfix), a change
Package: src:genshi
Version: 0.7.3-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
ERROR: test_extract_i18n_msg_with_other_directives_nested
(genshi.filters.tests.i18n.MsgDirectiveTestCase)
---
Package: src:python-adal
Version: 1.2.2-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
/usr/lib/python3.9/http/client.py:245:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , mode = 'rb'
bufsize = -1
def
Package: src:python-cobra
Version: 0.18.1-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
python-cobra assumes that all it's dependencies are packaged for all supported
python3 versions, but libsbml is not packaged that way.
Either package libsbml f
Package: src:python-django-import-export
Version: 2.4.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
autopkgtest [19:11:54]: test command1: set -e ; for py in $(py3versions -r
2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $p
Package: src:python-boto
Version: 2.49.0-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
ERROR: test_cloudsearch_erroneous_sdf
(tests.unit.cloudsearch.test_document.CloudSearchBadSDFTesting)
---
Package: src:python-azure
Version: 20200927+git-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , mode = 'rb'
bufsize = -1
def makefile(self, mode='r', bufsi
Package: src:python-etelemetry
Version: 0.2.0-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
=== FAILURES ===
___ test_get_project __
Package: src:python-blosc
Version: 1.8.1+ds1-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
==
FAIL: compress (blosc.toplevel)
Doctest: blosc.toplevel.compress
-
Package: src:python-bitstring
Version: 3.1.5-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
==
ERROR: testDouble (test_bits.InitFromArray)
--
Package: src:python-executing
Version: 0.4.3-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
autopkgtest [22:01:06]: test unittest: [---
Traceback (most recent call last):
File "/tmp/autopkgtest-lxc.0jbyozrd/downtmp/build.4ij/sr
Package: src:feature-check
Version: 0.2.2-5
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
autopkgtest [18:46:41]: test tap-python.sh: [---
Testing python3.9
'python3.9' -m feature_check "$@"
# Failed test '-
Source: rdkit
Version: 202003.4-2
Severity: serious
Tags: ftbfs sid
Hello,
rdkit FTBFS in unstable with postgresql 13. From [1]:
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2020-09-22 08:32:21.0 -1200
+++
Package: src:ecflow
Version: 5.5.3-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
[...]
Setting up python3-ecflow (5.5.3-3) ...
/usr/lib/python3/dist-packages/ecflow/ecf.py:561: SyntaxWarning: "is" with a
literal. Did you mean "=="?
if name is "":
Package: src:python-fabio
Version: 0.10.2+dfsg-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-fabio/7758092/log.gz
Package: src:python-icecream
Version: 2.0.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
autopkgtest [23:11:12]: test unittest: [---
..EEE.
===
Package: src:python-latexcodec
Version: 1.0.7-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
==
ERROR: test_install_example.test_install_example_3
--
Package: src:python-molotov
Version: 1.6-7
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-molotov/7759352/log.gz
Package: src:ctdopts
Version: 1.4-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
autopkgtest [07:37:47]: test run-example: [---
+ py3versions -r
+ echo Testing with python3.9:
+ python3.9 -c import CTDopts; print(CTDopts)
Testing
Package: src:python-msrestazure
Version: 0.6.2-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
self = , mode = 'rb'
bufsize = -1
def makefile(self, mode='r', bufsize=-1):
"""Returns this fake socket's own tempfile buffer.
If the
Package: src:python-msrest
Version: 0.6.18-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
self = , mode = 'rb'
bufsize = -1
def makefile(self, mode='r', bufsize=-1):
"""Returns this fake socket's own tempfile buffer.
If there
Package: src:sphinxcontrib-bibtex
Version: 1.0.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
==
ERROR: test_issue4.test_encoding
Package: src:supysonic
Version: 0.6.0+ds-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
autopkgtest [19:10:55]: test unittests: [---
=== python3.9 ===
/tmp/autopkgtest-lxc.m7pc_az_/downtmp/build.Kqd/src/debian/tests/unittests: 13
Processing commands for cont...@bugs.debian.org:
> severity 973001 serious
Bug #973001 [src:seqan3] seqan3: autopackage tests need updating for new
googletest
Severity set to 'serious' from 'normal'
> tag 973001 + ftbfs
Bug #973001 [src:seqan3] seqan3: autopackage tests need updating for new
goo
Processing control commands:
> severity -1 grave
Bug #972936 [libgcc-s1] libgcc-s1 needs Breaks: libgcc1 (<< 1:10)
Severity set to 'grave' from 'important'
--
972936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> block -1 by 972721
Bug #973019 [src:python-boto] python-boto's autopkg tests are failing with
python3.9
973019 was not blocked by any bugs.
973019 was not blocking any bugs.
Added blocking bug(s) of 973019: 972721
--
973019: https://bugs.debian.org/cgi-bin/bugrepo
Processing commands for cont...@bugs.debian.org:
> forwarded 973027 https://github.com/rdkit/rdkit/issues/3521
Bug #973027 [src:rdkit] rdkit: FTBFS in unstable with postgresql 13
Set Bug forwarded-to-address to 'https://github.com/rdkit/rdkit/issues/3521'.
> tags 973027 + confirmed upstream patch
Control: block -1 by 972721
> File "/usr/lib/python3/dist-packages/httpretty/core.py", line 438, in
> makefile
> if t.isAlive():
> AttributeError: 'Thread' object has no attribute 'isAlive'
This looks like #972721
I don't think we need to do anything in python-boto to fix this.
Processing commands for cont...@bugs.debian.org:
> severity 973001 serious
Bug #973001 [src:seqan3] seqan3: autopackage tests need updating for new
googletest
Ignoring request to change severity of Bug 973001 to the same value.
> user debian...@lists.debian.org
Setting user to debian...@lists.deb
Package: cloud.debian.org
Severity: grave
Hi,
Testing to start the OpenStack image (well, the "genericcloud" image), I
couldn't login into it, because there isn't any metadata service configured
in it.
After adding this:
# cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg
datasource_list: [ NoCloud, AltC
Processing commands for cont...@bugs.debian.org:
> notfound 933091 0.8.1-1
Bug #933091 {Done: Pirate Praveen }
[node-rollup-plugin-typescript] node-rollup-plugin-typescript seems
incompatible with rollup/typescript
No longer marked as found in versions node-rollup-plugin-typescript/0.8.1-1.
> fo
Processing commands for cont...@bugs.debian.org:
> found 933091 0.8.1-1
Bug #933091 [node-rollup-plugin-typescript] node-rollup-plugin-typescript seems
incompatible with rollup/typescript
Marked as found in versions node-rollup-plugin-typescript/0.8.1-1.
> thanks
Stopping processing here.
Please
Processing commands for cont...@bugs.debian.org:
> tags 933091 + buster-ignore
Bug #933091 [node-rollup-plugin-typescript] node-rollup-plugin-typescript seems
incompatible with rollup/typescript
Added tag(s) buster-ignore.
> thanks
Stopping processing here.
Please contact me if you need assistan
Processing commands for cont...@bugs.debian.org:
> fixed 933091 1.0.0-1
Bug #933091 [node-rollup-plugin-typescript] node-rollup-plugin-typescript seems
incompatible with rollup/typescript
Marked as fixed in versions node-rollup-plugin-typescript/1.0.0-1.
> thanks
Stopping processing here.
Please
Hi,
I tried to build Celery 5.0.0-2 in a pbuilder chroot:
# pbuilder build --basetgz /home/pbuilder-sid.tgz --use-network yes
--buildplace ./cache --aptcache ./ cache celery_5.0.0-2.dsc
and it succeed.
Kind Regards
Source: kineticstools
Version: 0.6.1+git20200325.3558942+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> m
Source: python-py
Version: 1.9.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: sphinx-tabs
Version: 1.2.1+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: node-zipfile
Version: 0.5.12+ds-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: bumpversion
Version: 1.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpack
Source: ruby-redis-activesupport
Version: 5.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ArgumentEr
Source: logging-tree
Version: 1.8.1-0.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: nototools
Version: 0.2.13-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: undercover-el
Version: 0.7.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpack
Control: reopen -1
Hi
The new upload of sagemath/9.2-1 still FTBFS [1] with Python 3.9 as
default. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1]
https://people.debian.org/~ginggs/python3.9-default/sagemath_9.2-1+build1_amd64-2020-10-27T15:56:32Z.build
ma
Source: python-apptools
Version: 4.5.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: commonmark-bkrs
Version: 0.5.4+ds-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: ruby-rails-controller-testing
Version: 1.0.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/
Source: esup-el
Version: 0.7.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: lomiri-download-manager
Version: 0.1.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Enter
Source: python-msrestazure
Version: 0.6.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpack
Source: pybtex
Version: 0.22.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: libsis-base-java
Version: 18.09~pre1+git20180827.fe4953e+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: amazon-ecr-credential-helper
Version: 0.3.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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:
> reopen -1
Bug #972916 {Done: Tobias Hansen } [src:sagemath] sagemath
ftbfs with python3.9
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as f
Source: mgba
Version: 0.8.3+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/ld: CMakeFi
Source: tycho
Version: 1.6.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: cool-retro-term
Version: 1.1.1+git20200723-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Source: natsort
Version: 7.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: pyrandom2
Version: 1.0.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: pdf.js
Version: 2.6.347+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: python3-antlr3
Version: 3.5.2-7
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: ponyorm
Version: 0.7.13-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpack
Source: python-biplist
Version: 1.0.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: fcitx5
Version: 0.0~git20200626.2e9821a-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Enter
Source: docker.io
Version: 19.03.13+dfsg1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Enter
Source: twms
Version: 0.07z+git20200829+cb7d39a-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules bu
Source: leiningen-clojure
Version: 2.9.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: python-aiosmtpd
Version: 1.2-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: qiskit-ibmq-provider
Version: 0.4.6-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpack
Source: celery-haystack
Version: 0.10-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: ros-angles
Version: 1.9.13-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: pgaudit
Version: 1.4.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules cl
Source: mir
Version: 1.8.0+dfsg1-10
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/build-amd64/src/
Source: python-fs
Version: 2.4.11-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: python-smstrade
Version: 0.2.4-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: python-bleach
Version: 3.2.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: python-boltons
Version: 19.1.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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: python-argcomplete
Version: 1.8.1-1.3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules bu
1 - 100 of 308 matches
Mail list logo