Bug#975868: marked as done (dart: libdart-*6 misses Breaks+Replaces: libdart6-*)

Your message dated Thu, 26 Nov 2020 07:49:20 + with message-id and subject line Bug#975868: fixed in dart 6.9.5-2 has caused the Debian Bug report #975868, regarding dart: libdart-*6 misses Breaks+Replaces: libdart6-* to be marked as done. This means that you claim that the problem has been d

Bug#917372: marked as done (mnemosyne: can't start, unable to load file, query failed)

Your message dated Thu, 26 Nov 2020 08:43:35 +0100 with message-id and subject line Really closing this bug has caused the Debian Bug report #917372, regarding mnemosyne: can't start, unable to load file, query failed to be marked as done. This means that you claim that the problem has been dealt

Bug#975571: linux: No rule to make target 'scripts/module.lds' while building out-of-tree modules

Hi, On Tue, Nov 24, 2020 at 07:05:24PM +0100, Salvatore Bonaccorso wrote: > Control: tags -1 + confirmed > > Hi Andreas, > > On Mon, Nov 23, 2020 at 06:46:26PM +0100, Andreas Beckmann wrote: > > Source: linux > > Version: 5.10~rc4-1~exp1 > > Severity: important > > > > Hi, > > > > building out

Bug#975689: yubico-piv-tool: invalid Uploaders field: missing comma between Dain Nilsson & Klas Lindfors

On Thu, 2020-11-26 at 05:48 +0100, nicoo wrote: > Out of curiousity, do you know whether a trailing comma is allowed, like with > dependencies? It is what I try to default to, for lists with one element per > line, but I erred on the side of caution here, since you mentionned issues > there cause

Processed: severity of 975571 is serious

Processing commands for cont...@bugs.debian.org: > # this issue needs to be fixed for bullseye > severity 975571 serious Bug #975571 [src:linux] linux: No rule to make target 'scripts/module.lds' while building out-of-tree modules Severity set to 'serious' from 'important' > thanks Stopping proce

Bug#975880: [python3-astroquery] Incompatible with Astropy 4.2

Package: python3-astroquery Version: 0.4.1+dfsg-3 Severity: serious Tags: patch Sorry to disturb again: The released version of astroquery uses some internal structures of astropy, which make it fail with the latest version: https://ci.debian.net/data/autopkgtest/testing/amd64/a/astroquery/84342

Bug#973136: delve: FTBFS: dh_auto_test: error

On 26/11/20 at 11:57 +0800, Shengjing Zhu wrote: > I have pushed a fix to salsa, should I just close this bug, or you > prefer cloning a new one? I think that using this bug is fine. I'll reopen another bug if I can reproduce the previous issue. Lucas

Processed: 975794 is forwarded

Processing commands for cont...@bugs.debian.org: > forwarded 975794 https://github.com/TooTallNate/node-agent-base/issues/53 Bug #975794 [src:node-agent-base] node-agent-base: FTBFS: Type 'undefined' is not assignable to type 'Duplex | Pick | Agent | PromiseLike'. Set Bug forwarded-to-address to

Processed: Re: Bug#975875: x11vnc: CVE-2020-29074

Processing control commands: > tags -1 + patch Bug #975875 [src:x11vnc] x11vnc: CVE-2020-29074 Added tag(s) patch. -- 975875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#975875: x11vnc: CVE-2020-29074

Control: tags -1 + patch Hi On Thu, Nov 26, 2020 at 05:59:50AM +0100, Salvatore Bonaccorso wrote: > Source: x11vnc > Version: 0.9.13-6 > Severity: grave > Tags: security upstream fixed-upstream > Justification: user security hole > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > Contr

Bug#975878: libyade is still linked with libpython3.8

Source: yade Version: 2020.01a-12 Severity: serious libyade is still linked with libpython3.8 after the rebuild with 3.9 as default, likely due to https://sources.debian.org/src/yade/2020.01a-12/CMakeLists.txt/#L196

Bug#975819: marked as done (node-ws: FTBFS: Type 'undefined' is not assignable to type 'Duplex | Pick | Agent | PromiseLike'.)

rce: node-ws Version: 7.3.1+~cs24.0.5-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering director

Bug#975689: marked as done (yubico-piv-tool: invalid Uploaders field: missing comma between Dain Nilsson & Klas Lindfors)

Your message dated Thu, 26 Nov 2020 05:10:31 + with message-id and subject line Bug#975689: fixed in yubico-piv-tool 2.1.1-3 has caused the Debian Bug report #975689, regarding yubico-piv-tool: invalid Uploaders field: missing comma between Dain Nilsson & Klas Lindfors to be marked as done.

Processed: x11vnc: CVE-2020-29074

Processing control commands: > found -1 0.9.16-4 Bug #975875 [src:x11vnc] x11vnc: CVE-2020-29074 Marked as found in versions x11vnc/0.9.16-4. -- 975875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#975875: x11vnc: CVE-2020-29074

Source: x11vnc Version: 0.9.13-6 Severity: grave Tags: security upstream fixed-upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 0.9.16-4 Hi, The following vulnerability was published for x11vnc. CVE-2020-29074[0]: | scan.c in x11

Bug#975689: yubico-piv-tool: invalid Uploaders field: missing comma between Dain Nilsson & Klas Lindfors

Hi Paul, On Wed, Nov 25, 2020 at 02:40:50PM +0800, Paul Wise wrote: > yubico-piv-tool 2.1.1-1 introduced an invalid uploaders field, that is > missing a comma between Dain Nilsson & Klas Lindfors. Indeed! Sorry about that, I'm currently building a fixed package. I guess I missed have missed tha

Bug#973136: delve: FTBFS: dh_auto_test: error

Hi, On Thu, Nov 26, 2020 at 5:15 AM Lucas Nussbaum wrote: > > The relevant part is near "FAIL:" > > > > === RUN TestIssue1374 > >proc_test.go:112: failed assertion at proc_test.go:4211: Call - > > could not restore registers: bad address > > --- FAIL: TestIssue1374 (0.62s) > > > > > > Howev

Bug#975849: cjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

On Wed, 25 Nov 2020, Fabio Fantoni wrote: > fast tests I haven't found important issue but is better wait cinnamon > 4.8 release stable (after good testing these weeks), in the meantime, in I have prepared 4.8 packages for those packages that have already a new upstream. Let us wait till all are r

Bug#975746: marked as done (watchman: FTBFS: build-dependency not installable: python3-all-dev (< 3.9))

ous Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ >

Bug#975862: marked as done (lacme: Upcoming changes in the Let's Encrypt chain of trust break lacme)

Your message dated Thu, 26 Nov 2020 00:11:20 + with message-id and subject line Bug#975862: fixed in lacme 0.7-1 has caused the Debian Bug report #975862, regarding lacme: Upcoming changes in the Let's Encrypt chain of trust break lacme to be marked as done. This means that you claim that th

Bug#975412: marked as done (elementpath breaks python-xmlschema autopkgtest: lots of errors)

Your message dated Wed, 25 Nov 2020 23:49:22 + with message-id and subject line Bug#975412: fixed in python-xmlschema 1.3.1-1 has caused the Debian Bug report #975412, regarding elementpath breaks python-xmlschema autopkgtest: lots of errors to be marked as done. This means that you claim tha

Bug#975811: marked as done (python-xmlschema: FTBFS: distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('elementpath~=1.4'))

--- Begin Message --- Source: python-xmlschema Version: 1.2.2-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully)

Bug#975525: marked as done (python-xmlschema fails autopkg tests with Python 3.9)

Your message dated Wed, 25 Nov 2020 23:49:22 + with message-id and subject line Bug#975525: fixed in python-xmlschema 1.3.1-1 has caused the Debian Bug report #975525, regarding python-xmlschema fails autopkg tests with Python 3.9 to be marked as done. This means that you claim that the probl

Bug#975868: dart: libdart-*6 misses Breaks+Replaces: libdart6-*

Source: dart Version: 6.9.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwr

Bug#972669: src:tarantool: fails to migrate to testing for too long: FTBFS on armhf and arm64

Hello, It seems quite counterintuitive that this bug would be marked as closed in unstable, given that it's the unstable version which fails to build? And also, it seems counterintuitive to auto-remove the testing version of the package due to a regression in buildability in the unstable version.

Bug#975785: marked as done (silver-platter: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.9" returned exit code 13)

ce: silver-platter Version: 0.3.0+git20200906.d2bd137-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg

Bug#975412: elementpath breaks python-xmlschema autopkgtest: lots of errors

Control: notfound -1 elementpath/2.0.4-1 Control: reassign -1 python-xmlschema On 11/21/20 9:50 PM, Paul Gevers wrote: > Source: elementpath, python-xmlschema > Control: found -1 elementpath/2.0.4-1 > Control: found -1 python-xmlschema/1.2.2-2 > Severity: serious > Tags: sid bullseye > X-Debbugs-C

Processed: Re: Bug#975412: elementpath breaks python-xmlschema autopkgtest: lots of errors

Processing control commands: > notfound -1 elementpath/2.0.4-1 Bug #975412 [src:elementpath, src:python-xmlschema] elementpath breaks python-xmlschema autopkgtest: lots of errors No longer marked as found in versions elementpath/2.0.4-1. > reassign -1 python-xmlschema Bug #975412 [src:elementpath

Bug#975798: marked as done (loggerhead: FTBFS: AttributeError: 'Thread' object has no attribute 'isAlive')

rsion: 1.19~bzr501-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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 '/<>&#

Bug#975423: marked as done (pam-python: needs a source only upload.)

Your message dated Wed, 25 Nov 2020 23:58:36 +0100 with message-id <20201125225834.ga11...@debian.org> and subject line Re: pam-python: needs a source only upload. has caused the Debian Bug report #975423, regarding pam-python: needs a source only upload. to be marked as done. This means that you

Bug#975849: cjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

Il 25/11/2020 21:54, Lucas Nussbaum ha scritto: > Source: cjs > Version: 4.6.0-2 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20201125 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your pack

Processed: tagging 948105

Processing commands for cont...@bugs.debian.org: > tags 948105 + ftbfs Bug #948105 [src:libgdata] Remove build dep on libuhttpmock-dev Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 948105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948

Bug#975755: marked as done (rust-sniffglue: FTBFS: unsatisfiable build-dependencies: librust-sha2-dev (= 0.8.0-1+b1), librust-digest-0.8+std-dev)

: rust-sniffglue Version: 0.11.1-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Processed: Re: Bug#975784: python-magic: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.9" returned exit code 13

Processing commands for cont...@bugs.debian.org: > tags 975784 confirmed Bug #975784 [src:python-magic] python-magic: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.9" returned exit code 13 Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if y

Bug#975763: marked as done (rust-block-cipher-trait: FTBFS: build-dependency not installable: librust-generic-array-0.12+default-dev)

-block-cipher-trait Version: 0.6.2-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#975863: leatherman: /usr/include/boost/nowide/ are shipped by boost_1.74

Package: leatherman Version: 1.12.1+dfsg-1 Severity: serious Tags: patch Justification: Policy 10.1 User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package ships some files, which are now shipped

Processed: tagging 975819

Processing commands for cont...@bugs.debian.org: > tags 975819 + pending Bug #975819 [src:node-ws] node-ws: FTBFS: Type 'undefined' is not assignable to type 'Duplex | Pick | Agent | PromiseLike'. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#975753: marked as done (rust-universal-hash: FTBFS: build-dependency not installable: librust-generic-array-0.12+default-dev)

-universal-hash Version: 0.3.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#975727: marked as done (util-linux: [util-linux] 2.36.1-1 breaks davfs mount)

Your message dated Wed, 25 Nov 2020 21:50:02 + with message-id and subject line Bug#975727: fixed in util-linux 2.36.1-2 has caused the Debian Bug report #975727, regarding util-linux: [util-linux] 2.36.1-1 breaks davfs mount to be marked as done. This means that you claim that the problem ha

Bug#975761: marked as done (rust-block-buffer: FTBFS: build-dependency not installable: librust-generic-array-0.12+default-dev)

-block-buffer Version: 0.7.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hop

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 975761 0.9.0-2 Bug #975761 [src:rust-block-buffer] rust-block-buffer: FTBFS: build-dependency not installable: librust-generic-array-0.12+default-dev The source 'rust-block-buffer' and version '0.9.0-2' do not appear to match any binary pa

Bug#975862: lacme: Upcoming changes in the Let's Encrypt chain of trust break lacme

Package: lacme Version: 0.6.1-1 Severity: grave Justification: renders package unusable Two upcoming changes in the Let's Encrypt chain of trust severely impact lacme and will break new issuance when they're rolled out in December / January. 1. The existing issuer, namely “Let's Encrypt Authorit

Bug#975794: FTBFS: Type 'undefined' is not assignable to type 'Duplex | Pick | Agent | PromiseLike'.

>> + tsc >> src/promisify.ts(27,15): error TS2345: Argument of type 'Duplex | >> Pick | Agent | undefined' is not assignable to >> parameter of type 'Duplex | Pick | Agent | >> PromiseLike'. >> Type 'undefined' is not assignable to type 'Duplex | Pick> "addRequest"> | Agent | PromiseLike'. >>

Bug#975794: 975794 and 975819 are related

Hello, It seems #975794 (node-ws) and #975819 (node-agent-base) are related as they concern the same piece of code of agent-base, which is packaged in node-agent-base and embedded in node-ws. Removing agent-base source from node-ws is underway (#972541). Best, Andrius

Processed: Bug#975727 marked as pending in util-linux

Processing control commands: > tag -1 pending Bug #975727 [util-linux] util-linux: [util-linux] 2.36.1-1 breaks davfs mount Added tag(s) pending. -- 975727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#975727: marked as pending in util-linux

Control: tag -1 pending Hello, Bug #975727 in util-linux 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/debian/util-linux/-/commit/29fddd3ae8e842b05dc8dc1bd586

Bug#975779: marked as done (gpac: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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 '/<>' > ## Remove File

Bug#975433: marked as done (gpac: FTBFS on armel: missing -latomic)

Your message dated Wed, 25 Nov 2020 21:20:21 + with message-id and subject line Bug#975433: fixed in gpac 1.0.1+dfsg1-3 has caused the Debian Bug report #975433, regarding gpac: FTBFS on armel: missing -latomic to be marked as done. This means that you claim that the problem has been dealt wi

Processed: Re: Bug#973136: delve: FTBFS: dh_auto_test: error

Processing control commands: > severity -1 serious Bug #973136 [src:delve] delve: FTBFS: dh_auto_test: error Severity set to 'serious' from 'important' > tags -1 - unreproducible Bug #973136 [src:delve] delve: FTBFS: dh_auto_test: error Removed tag(s) unreproducible. -- 973136: https://bugs.debi

Processed: reassign 975752 to android-libadb, found 975752 in 1:8.1.0+r23-8, affects 975752

Processing commands for cont...@bugs.debian.org: > reassign 975752 android-libadb Bug #975752 [src:fdroidcl] fdroidcl: FTBFS: unsatisfiable build-dependency: android-libbase (= 1:8.1.0+r23-8) but 1:10.0.0+r36-1~stage1.1 is to be installed Bug reassigned from package 'src:fdroidcl' to 'android-lib

Bug#975830: marked as done (openthesaurus: FTBFS: dpkg-source: error: pathname '/<>/debian/openoffice.org-thesaurus-de/usr/share/myspell/dicts/th_de_DE_v2.idx' points outside source root

.cgi?bug=975830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openthesaurus Version: 20160424-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages i

Processed: src:r-cran-haplo.stats: fails to migrate to testing for too long: Depends on non-migrating package

Processing control commands: > close -1 1.8.6-1 Bug #975859 [src:r-cran-haplo.stats] src:r-cran-haplo.stats: fails to migrate to testing for too long: Depends on non-migrating package Marked as fixed in versions r-cran-haplo.stats/1.8.6-1. Bug #975859 [src:r-cran-haplo.stats] src:r-cran-haplo.sta

Bug#975854: mediastreamer2: FTBFS: string_fortified.h:106:10: error: ‘__builtin_strncpy’ specified bound 8 equals destination size [-Werror=stringop-truncation]

Source: mediastreamer2 Version: 1:2.16.1-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86

Bug#975859: src:r-cran-haplo.stats: fails to migrate to testing for too long: Depends on non-migrating package

Source: r-cran-haplo.stats Version: 1.7.9-4 Severity: serious Control: close -1 1.8.6-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing

Bug#975858: pplacer: FTBFS: Error: Unbound module Gsl_error

Source: pplacer Version: 1.1~alpha19-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975853: opam: FTBFS: grep: opam.install: No such file or directory

Source: opam Version: 2.0.5-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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 '

Bug#975856: debmake-doc: FTBFS: dh: error: Please specify the compatibility level in debian/compat

Source: debmake-doc Version: 1.14-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975851: sensible-utils: FTBFS: po4a::po: Invalid value for option 'porefs' ('noline,wrap' is not one of 'full', 'counter', 'noline', 'file' or 'never')

Source: sensible-utils Version: 0.0.12+nmu1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Enter

Bug#975855: ruby-fakefs: FTBFS: ERROR: Test "ruby2.7" failed.

Source: ruby-fakefs Version: 1.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/

Bug#975849: cjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

Source: cjs Version: 4.6.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975846: google-oauth-client-java: FTBFS: Could not resolve dependencies for project com.google.oauth-client:google-oauth-client:jar:1.27.0

Source: google-oauth-client-java Version: 1.27.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpack

Bug#975848: rocksdb: FTBFS: ./db/version_edit.h:178:33: error: implicitly-declared ‘constexpr rocksdb::FileDescriptor::FileDescriptor(const rocksdb::FileDescriptor&)’ is deprecated [-Werror=deprecated

Source: rocksdb Version: 5.17.2-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -g -O2 -fdebug-prefix-

Bug#975852: grml2usb: FTBFS: Oh no! 💥 💔 💥

Source: grml2usb Version: 0.18.3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975845: ruby-redis: FTBFS: ERROR: Test "ruby2.7" failed.

Source: ruby-redis Version: 4.2.2-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2

Bug#975847: uwsgi-apparmor: FTBFS: make[1]: pyversions: No such file or directory

Source: uwsgi-apparmor Version: 0.0.0+git.2014.09.15.7d6d7bd7eb-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#975844: sphinx-tabs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13

Source: sphinx-tabs Version: 1.2.1+ds-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975843: sopt: FTBFS: core.h:270: undefined reference to `fmt::v6::internal::assert_fail(char const*, int, char const*)'

Source: sopt Version: 3.0.1-10 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975842: google-api-client-java: FTBFS: Could not resolve dependencies for project com.google.api-client:google-api-client:jar:1.27.1

Source: google-api-client-java Version: 1.27.1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpack

Processed: src:ghostscript: fails to migrate to testing for too long: unresolved RC bug: autopkgtest regression

Processing control commands: > close -1 9.53.3~dfsg-5 Bug #975841 [src:ghostscript] src:ghostscript: fails to migrate to testing for too long: unresolved RC bug: autopkgtest regression Marked as fixed in versions ghostscript/9.53.3~dfsg-5. Bug #975841 [src:ghostscript] src:ghostscript: fails to m

Bug#975841: src:ghostscript: fails to migrate to testing for too long: unresolved RC bug: autopkgtest regression

Source: ghostscript Version: 9.52.1~dfsg-1 Severity: serious Control: close -1 9.53.3~dfsg-5 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between te

Bug#971418: marked as done (jhbuild: Missing dependency on python3-distutils)

Your message dated Wed, 25 Nov 2020 21:50:20 +0100 with message-id and subject line Re: Bug#971418: jhbuild: Missing dependency on python3-distuils has caused the Debian Bug report #971418, regarding jhbuild: Missing dependency on python3-distutils to be marked as done. This means that you claim

Processed: src:r-cran-partykit: fails to migrate to testing for too long: autopkgtest regressions

Processing control commands: > close -1 1.2-10-1 Bug #975840 [src:r-cran-partykit] src:r-cran-partykit: fails to migrate to testing for too long: autopkgtest regressions Marked as fixed in versions r-cran-partykit/1.2-10-1. Bug #975840 [src:r-cran-partykit] src:r-cran-partykit: fails to migrate t

Bug#975840: src:r-cran-partykit: fails to migrate to testing for too long: autopkgtest regressions

Source: r-cran-partykit Version: 1.2-7-1 Severity: serious Control: close -1 1.2-10-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing a

Bug#975839: src:kore: fails to migrate to testing for too long: existing binaries are not rebuild or removed

Source: kore Version: 3.3.1-1 Severity: serious Control: close -1 4.0.1-5 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), It seems to forgot to file a removal request against the ftp.debian.org pseudo package for the binaries of your packa

Processed: src:kore: fails to migrate to testing for too long: existing binaries are not rebuild or removed

Processing control commands: > close -1 4.0.1-5 Bug #975839 [src:kore] src:kore: fails to migrate to testing for too long: existing binaries are not rebuild or removed Marked as fixed in versions kore/4.0.1-5. Bug #975839 [src:kore] src:kore: fails to migrate to testing for too long: existing bi

Bug#975735: marked as done (autopkg tests fail on all architectures)

Your message dated Wed, 25 Nov 2020 20:42:59 + with message-id and subject line Bug#975735: fixed in sim4 0.0.20121010-7 has caused the Debian Bug report #975735, regarding autopkg tests fail on all architectures to be marked as done. This means that you claim that the problem has been dealt

Bug#975738: marked as done (mutter: FTBFS: ../src/backends/meta-remote-desktop.h:30:10: fatal error: meta-dbus-remote-desktop.h: No such file or directory)

?bug=975738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mutter Version: 3.38.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your

Bug#975834: python-blosc: FTBFS: dh_auto_configure: error: pybuild --configure -i python{version} -p "3.8 3.9" returned exit code 13

Source: python-blosc Version: 1.9.2+ds1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpack

Bug#975755: [Pkg-rust-maintainers] Bug#975755: rust-sniffglue: FTBFS: unsatisfiable build-dependencies: librust-sha2-dev (= 0.8.0-1+b1), librust-digest-0.8+std-dev

yeah, my bad, I am working on a fix for that :) Le 25/11/2020 à 21:02, Lucas Nussbaum a écrit : Source: rust-sniffglue Version: 0.11.1-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid

Bug#975833: radvd: FTBFS: dh_install: error: missing files, aborting

Source: radvd Version: 1:2.18-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975832: python-aiosqlite: FTBFS: E: pybuild pybuild:353: build: plugin flit failed with: Not supported proxy scheme None

Source: python-aiosqlite Version: 0.15.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Enter

Bug#975831: tyxml: FTBFS: Error: Library "re" not found.

Source: tyxml Version: 4.4.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975830: openthesaurus: FTBFS: dpkg-source: error: pathname '/<>/debian/openoffice.org-thesaurus-de/usr/share/myspell/dicts/th_de_DE_v2.idx' points outside source root (to '/usr/share/

Source: openthesaurus Version: 20160424-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Unpack sou

Bug#975829: ufo2ft: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13

Source: ufo2ft Version: 2.16.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975828: pyqi: FTBFS: dh_auto_configure: error: pybuild --configure -i python{version} -p 3.9 returned exit code 13

Source: pyqi Version: 0.3.2+dfsg-6 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975827: xscreensaver: FTBFS: dh_install: error: missing files, aborting

Source: xscreensaver Version: 5.44+dfsg1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Enter

Bug#975822: pyramid-jinja2: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.9" returned exit code 13

Source: pyramid-jinja2 Version: 2.7+dfsg-1.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build &

Bug#975824: sexplib310: FTBFS: Error: Library "sexplib0" not found.

Source: sexplib310 Version: 1:0.14.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975825: python-m2r: FTBFS: AttributeError: 'str' object has no attribute 'supported'

Source: python-m2r Version: 0.2.1-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975826: typerep: FTBFS: Error: Library "base" not found.

Source: typerep Version: 1:0.14.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975821: ocp-indent: FTBFS: Error: Library "findlib" not found.

Source: ocp-indent Version: 1.8.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975820: mnemosyne: FTBFS: AttributeError: 'array.array' object has no attribute 'tostring'

Source: mnemosyne Version: 2.7.2+ds1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975819: node-ws: FTBFS: Type 'undefined' is not assignable to type 'Duplex | Pick | Agent | PromiseLike'.

Source: node-ws Version: 7.3.1+~cs24.0.5-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Enter

Bug#975818: libgtkada: FTBFS: AttributeError: 'xml.etree.ElementTree.Element' object has no attribute 'getchildren'

Source: libgtkada Version: 19-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975817: mom: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

Source: mom Version: 0.6.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/

Bug#975816: ocaml-gettext: FTBFS: dh_install: error: missing files, aborting

Source: ocaml-gettext Version: 0.4.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975815: headache: FTBFS: Error: Library "camomile" not found.

Source: headache Version: 1.04-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975814: python-pyramid-chameleon: FTBFS: ModuleNotFoundError: No module named 'setuptools'

Source: python-pyramid-chameleon Version: 0.3-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot deb

Bug#975813: ocaml-sha: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2

Source: ocaml-sha Version: 1.13-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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

Bug#975812: ocaml-domain-name: FTBFS: Error: Library "astring" not found.

Source: ocaml-domain-name Version: 0.3.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Enter

  1   2   3   >