Bug#961445: Fixes in upstream repo commits.

I believe the upstream commits 19c55e0 and 89fa0b3 in the upstream Github repo should fix this bug. I have tested this on o

Bug#957496: Prevent migration of ocaml-{integers,ctypes} to testing

Hello, These bugs are still on topic and prevent ocaml-{integers,ctypes} from migrating to testing. Could you please fix them? Or have the faulty packages removed from testing. Cheers, -- Stéphane

Bug#964880: marked as done (npm: test failures in ppc64el and s390x)

Your message dated Sun, 16 Aug 2020 06:03:24 + with message-id and subject line Bug#964854: fixed in npm 6.14.7+ds-2 has caused the Debian Bug report #964854, regarding npm: test failures in ppc64el and s390x to be marked as done. This means that you claim that the problem has been dealt with

Bug#964854: marked as done (npm: autopkgtests failures on s390x)

Your message dated Sun, 16 Aug 2020 06:03:24 + with message-id and subject line Bug#964854: fixed in npm 6.14.7+ds-2 has caused the Debian Bug report #964854, regarding npm: autopkgtests failures on s390x to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug#964854 marked as pending in npm

Processing control commands: > tag -1 pending Bug #964854 [src:npm] npm: autopkgtests failures on s390x Bug #964880 [src:npm] npm: test failures in ppc64el and s390x Added tag(s) pending. Added tag(s) pending. -- 964854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964854 964880: https://bu

Bug#964854: marked as pending in npm

Control: tag -1 pending Hello, Bug #964854 in npm 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/js-team/npm/-/commit/2aa3815673d52a16edd457bf38205dd56897b3b9

Bug#968476: Please include ocamlvars.mk to avoid FTBFS because of dh_dwz

Package: src:supermin Version: 5.2.0-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org Dear Maintainer, Your package FTBFS at the moment, because of a failure in dh_dwz. This failure is common to many packages written in OCaml (see for example [1] and [2]). As a w

Bug#968475: Please include ocamlvars.mk to avoid FTBFS because of dh_dwz

Package: src:kalzium Version: 20.04.0-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org Dear Maintainer, Your package FTBFS at the moment, because of a failure in dh_dwz. This failure is common to many packages written in OCaml (see for example [1] and [2]). As a

Bug#968474: Please include ocamlvars.mk to avoid FTBFS because of dh_dwz

Package: src:pplacer Version: 1.1~alpha19-2 Severity: serious Tags: ftbfs X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org Dear Maintainer, Your package FTBFS at the moment, because of a failure in dh_dwz. This failure is common to many packages written in OCaml (see for example [1] and [2]). A

Bug#966875: marked as done (aptitude: FTBFS: ../../../../src/generic/views/download_progress.cc:49:11: error: no match for ‘operator<<’ (operand types are ‘std::ostream’ {aka ‘std::basic_ostream

Your message dated Sun, 16 Aug 2020 03:33:28 + with message-id and subject line Bug#966875: fixed in aptitude 0.8.13-2 has caused the Debian Bug report #966875, regarding aptitude: FTBFS: ../../../../src/generic/views/download_progress.cc:49:11: error: no match for ‘operator<<’ (operand type

Bug#968472: mutt: does not detect attachment(s)

Package: mutt Version: 1.5.23-3+deb8u3 Severity: grave Justification: renders package unusable Dear Maintainer, On a debian 8.11 system I found I was getting unusable pdf attachments from another software. So I decided to try mutt. the latest mutt version on 8.11 is 1.5.23. upon entering mutt, I

Processed: tagging 966875

Processing commands for cont...@bugs.debian.org: > tags 966875 + pending Bug #966875 [src:aptitude] aptitude: FTBFS: ../../../../src/generic/views/download_progress.cc:49:11: error: no match for ‘operator<<’ (operand types are ‘std::ostream’ {aka ‘std::basic_ostream’} and ‘const char [17]’) Add

Bug#967143: Python3 update

Amazing! I'm glad I helped. Cheers, Francisco On Sat, 2020-08-15 at 11:21 -0400, John Scott wrote: > Control: unblock -1 by 937695 937569 > Control: block 937695 by -1 > Control: block 937569 by -1 > Control: merge -1 936632 > > > I have reached out to the gnumeric folks; they say a new version

Bug#957257: marked as done (gbonds: ftbfs with GCC-10)

Your message dated Sat, 15 Aug 2020 23:48:29 + with message-id and subject line Bug#957257: fixed in gbonds 2.0.3-15 has caused the Debian Bug report #957257, regarding gbonds: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#957325: marked as done (gxkb: ftbfs with GCC-10)

Your message dated Sat, 15 Aug 2020 22:03:53 + with message-id and subject line Bug#957325: fixed in gxkb 0.8.2-1 has caused the Debian Bug report #957325, regarding gxkb: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Bug#968372: libpango-1.0-0: ABI break in PangoRenderer, particularly serious on 32-bit

On Sat, 15 Aug 2020 at 18:10:10 +0100, Simon McVittie wrote: > I've reported it upstream and will see what happens. We should not change > the 1.46.x ABI downstream until we have discussed the problem with upstream, > because that will be storing up incompatibilities for us later, but it > might ma

Bug#964611: marked as done (libqtpas: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Sat, 15 Aug 2020 20:48:29 + with message-id and subject line Bug#964611: fixed in libqtpas 2.6+2.0.8+dfsg-2 has caused the Debian Bug report #964611, regarding libqtpas: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output

Bug#957964: marked as done (wvstreams: ftbfs with GCC-10)

Your message dated Sat, 15 Aug 2020 20:26:21 + with message-id and subject line Bug#957964: fixed in wvstreams 4.6.1-15 has caused the Debian Bug report #957964, regarding wvstreams: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#964854: fixed in npm 6.14.7+ds-1

control: reopen -1 control: notfixed -1 6.14.7+ds-1 hello, looks like "ppc64" might also be in that list? # Subtest: test/tap/legacy-platform-all.js # Subtest: setup 1..0 ok 1 - setup # time=5.306ms # Subtest: platform-all not ok 1 - no error messages --

Processed: Re: Bug#964854: fixed in npm 6.14.7+ds-1

Processing control commands: > reopen -1 Bug #964854 {Done: Xavier Guimard } [src:npm] npm: autopkgtests failures on s390x Bug #964880 {Done: Xavier Guimard } [src:npm] npm: test failures in ppc64el and s390x 'reopen' may be inappropriate when a bug has been closed with a version; all fixed vers

Bug#966971: marked as done (tpot: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 returned exit code 13)

Your message dated Sat, 15 Aug 2020 20:25:45 + with message-id and subject line Bug#966971: fixed in tpot 0.11.5+dfsg-1 has caused the Debian Bug report #966971, regarding tpot: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 returned exit code 13 to be marked

Processed: severity of 968106 is normal

Processing commands for cont...@bugs.debian.org: > severity 968106 normal Bug #968106 [phosh] phosh: Shell doesn't start Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 968106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Bug#957964: wvstreams: ftbfs with GCC-10

control: tags -1 patch pending uploading patch from meta-oe G. On Fri, 17 Apr 2020 11:13:44 + Matthias Klose wrote: > Package: src:wvstreams > Version: 4.6.1-14 > Severity: normal > Tags: sid bullseye > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-10 > > Please keep this issue o

Processed: Re: wvstreams: ftbfs with GCC-10

Processing control commands: > tags -1 patch pending Bug #957964 [src:wvstreams] wvstreams: ftbfs with GCC-10 Added tag(s) pending and patch. -- 957964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957707: marked as done (prayer: ftbfs with GCC-10)

Your message dated Sat, 15 Aug 2020 18:48:35 + with message-id and subject line Bug#957707: fixed in prayer 1.3.5-dfsg1-7 has caused the Debian Bug report #957707, regarding prayer: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: unblock 959462 with 959451

Processing commands for cont...@bugs.debian.org: > # am-utils has multiple RC bugs and is not in testing, so I will go ahead > anyway > unblock 959462 with 959451 Bug #959462 [linux-libc-dev] Provides undocumented virtual package linux-kernel-headers 959462 was blocked by: 959451 959456 959453 9

Processed: Re: Bug#968372: libpango-1.0-0: ABI break in PangoRenderer, particularly serious on 32-bit

Processing control commands: > reassign 968337 libpango-1.0-0 1.46.0-1 Bug #968337 [sylpheed] sylpheed: crash on startup Bug reassigned from package 'sylpheed' to 'libpango-1.0-0'. No longer marked as found in versions sylpheed/3.7.0-8. Ignoring request to alter fixed versions of bug #968337 to th

Bug#968372: libpango-1.0-0: ABI break in PangoRenderer, particularly serious on 32-bit

Control: reassign 968337 libpango-1.0-0 1.46.0-1 Control: forcemerge 968372 968337 Control: retitle 968372 libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit Control: tags 968372 = upstream Control: forwarded 968372 https://gitlab.gnome.org/GNOME/pango/-/issues/497 On Fri, 14 Aug

Bug#965278: marked as done (meson 0.55.0 causes build failures)

Your message dated Sat, 15 Aug 2020 19:05:33 +0300 with message-id and subject line Closing has caused the Debian Bug report #965278, regarding meson 0.55.0 causes build failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#957676: marked as done (peony: ftbfs with GCC-10)

Your message dated Sat, 15 Aug 2020 16:00:14 + with message-id and subject line Bug#957676: fixed in peony 3.0.1-1 has caused the Debian Bug report #957676, regarding peony: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#962988: marked as done (When started, xfstt doesn't listen at any sockets (neither unix nor tcp) if /tmp/.font-unix/ directory already exists)

Your message dated Sat, 15 Aug 2020 15:33:57 + with message-id and subject line Bug#962988: fixed in xfstt 1.11-1 has caused the Debian Bug report #962988, regarding When started, xfstt doesn't listen at any sockets (neither unix nor tcp) if /tmp/.font-unix/ directory already exists to be mar

Processed: Bug#962988 in package xfstt marked as pending

Processing control commands: > tag 962988 pending Bug #962988 [xfstt] When started, xfstt doesn't listen at any sockets (neither unix nor tcp) if /tmp/.font-unix/ directory already exists Added tag(s) pending. -- 962988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962988 Debian Bug Tracki

Processed (with 1 error): block 967143 with 943104 937448, merging 936632 967143

Processing commands for cont...@bugs.debian.org: > # forgot the closed blocking bugs > block 967143 with 943104 937448 Bug #967143 [src:gnumeric] gnumeric: Unversioned Python removal in sid/bullseye 967143 was not blocked by any bugs. 967143 was blocking: 937569 937695 Added blocking bug(s) of 967

Bug#962988: in package xfstt marked as pending

Control: tag 962988 pending Hi! Bug #962988 in package xfstt reported by you has been fixed in the debian/pkgs/xfstt.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.hadrons.org/cgit/debian/pkgs/xfstt.git/diff/?id=8b9e5ba --- commit

Bug#967143: Python3 update

Control: unblock -1 by 937695 937569 Control: block 937695 by -1 Control: block 937569 by -1 Control: merge -1 936632 > I have reached out to the gnumeric folks; they say a new version > including python3 support should be out in a couple of months. Thanks! Your citing the removal from Debian must

Processed (with 1 error): Re: Bug#967143: Python3 update

Processing control commands: > unblock -1 by 937695 937569 Bug #967143 [src:gnumeric] gnumeric: Unversioned Python removal in sid/bullseye 967143 was blocked by: 937695 937569 967143 was not blocking any bugs. Removed blocking bug(s) of 967143: 937569 and 937695 > block 937695 by -1 Bug #937695 [s

Processed (with 1 error): bug 967143 is forwarded to https://gitlab.gnome.org/GNOME/gnumeric/issues/419 ...

Processing commands for cont...@bugs.debian.org: > forwarded 967143 https://gitlab.gnome.org/GNOME/gnumeric/issues/419 Bug #967143 [src:gnumeric] gnumeric: Unversioned Python removal in sid/bullseye Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gnumeric/issues/419'. > block 9671

Bug#966852: marked as done (nfstrace: FTBFS: statistics_window.cpp:61:20: error: ‘runtime_error’ is not a member of ‘std’)

Your message dated Sat, 15 Aug 2020 14:34:13 + with message-id and subject line Bug#966600: fixed in nfstrace 0.4.3.2+git20200805+b220d04-1 has caused the Debian Bug report #966600, regarding nfstrace: FTBFS: statistics_window.cpp:61:20: error: ‘runtime_error’ is not a member of ‘std’ to be m

Bug#966600: marked as done (nfstrace: patch for newer json-c/gcc-10)

Your message dated Sat, 15 Aug 2020 14:34:13 + with message-id and subject line Bug#966600: fixed in nfstrace 0.4.3.2+git20200805+b220d04-1 has caused the Debian Bug report #966600, regarding nfstrace: patch for newer json-c/gcc-10 to be marked as done. This means that you claim that the prob

Bug#957003: aqemu: ftbfs with GCC-10

Hi, On Fri, 17 Apr 2020 10:56:28 + Matthias Klose wrote:> > The package fails to build in a test rebuild on at least amd64 with > gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The > severity of this report will be raised before the bullseye release, > so nothing has to be done for t

Bug#968443: verilator: fails to migrate to testing for too long

Source: verilator Version: 4.034-2 Severity: serious Control: close -1 4.036-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync X-Debbugs-CC: elb...@debian.org Hi Maintainer As recently announced [1], the Release Team now considers packages that are out-of-syn

Processed: verilator: fails to migrate to testing for too long

Processing control commands: > close -1 4.036-1 Bug #968443 [src:verilator] verilator: fails to migrate to testing for too long Marked as fixed in versions verilator/4.036-1. Bug #968443 [src:verilator] verilator: fails to migrate to testing for too long Marked Bug as done -- 968443: https://bug

Bug#960120: node-yarnpkg: I found an older commit that still builds

> With this build: > https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/915568#L2420 > I get a different error while building: > [17:58:12] Starting 'build'... > 2420[17:58:13] Error: [BABEL] /builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.22.4/src/api.js: Cannot find module > 'bab

Bug#966961: marked as done (imbalanced-learn: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)

Your message dated Sat, 15 Aug 2020 13:07:28 +0200 with message-id <2eb3f060-3171-9e72-7312-0be433671...@debian.org> and subject line Re: Bug#966961: imbalanced-learn: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 has caused the Debian Bug

Bug#968410: marked as done (python3-setuptools: ModuleNotFoundError: No module named '_distutils_hack')

Your message dated Sat, 15 Aug 2020 10:19:23 + with message-id and subject line Bug#968410: fixed in setuptools 49.3.1-2 has caused the Debian Bug report #968410, regarding python3-setuptools: ModuleNotFoundError: No module named '_distutils_hack' to be marked as done. This means that you cl

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 966871 eigen3/3.3.7-3 Bug #966871 {Done: Anton Gladky } [src:eigen3] eigen3: FTBFS: StdDeque.h:106:41: error: ‘std::_Deque_base, Eigen::aligned_allocator_indirection > >::_Deque_impl std::_Deque_base, Eigen::aligned_allocator_indirection

Processed: cluster3: fails to migrate to testing for too long

Processing commands for cont...@bugs.debian.org: > reopen 968436 Bug #968436 {Done: Graham Inggs } [src:cluster3] cluster3: fails to migrate to testing for too long '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-

Processed: Patch

Processing control commands: > tags -1 + patch Bug #968410 [python3-setuptools] python3-setuptools: ModuleNotFoundError: No module named '_distutils_hack' Added tag(s) patch. -- 968410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968410 Debian Bug Tracking System Contact ow...@bugs.debian

Bug#968410: Patch

Control: tags -1 + patch Attached patch fixes this. From 46f86fdd03d77d6d2a6d4f0fc3f64c447093bae7 Mon Sep 17 00:00:00 2001 From: Tristan Seligmann Date: Sat, 15 Aug 2020 11:28:42 +0200 Subject: [PATCH] Install _distutils_hack. Closes: #968410. --- debian/changelog | 7 +++

Bug#957850: marked as done (super: ftbfs with GCC-10)

Your message dated Sat, 15 Aug 2020 09:34:17 + with message-id and subject line Bug#957850: fixed in super 3.30.3-1 has caused the Debian Bug report #957850, regarding super: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#957658: marked as done (p7zip: ftbfs with GCC-10)

Your message dated Sat, 15 Aug 2020 09:34:11 + with message-id and subject line Bug#957658: fixed in p7zip 16.02+dfsg-8 has caused the Debian Bug report #957658, regarding p7zip: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#957056: marked as done (bsd-mailx: ftbfs with GCC-10)

Your message dated Sat, 15 Aug 2020 09:33:28 + with message-id and subject line Bug#957056: fixed in bsd-mailx 8.1.2-0.20180807cvs-2 has caused the Debian Bug report #957056, regarding bsd-mailx: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt

Bug#966871: Fixed

966871 fixed 3.3.7-3 thanks

Bug#966871: marked as done (eigen3: FTBFS: StdDeque.h:106:41: error: ‘std::_Deque_base, Eigen::aligned_allocator_indirection > >::_Deque_imp

Your message dated Sat, 15 Aug 2020 11:31:08 +0200 with message-id and subject line Fixed has caused the Debian Bug report #966871, regarding eigen3: FTBFS: StdDeque.h:106:41: error: ‘std::_Deque_base, Eigen::aligned_allocator_indirection > >::_Deque_impl std::_Deque_base, Eigen::aligned_allo

Bug#968436: cluster3: fails to migrate to testing for too long

Source: cluster3 Version: 2.4.1-1 Severity: serious Control: close -1 2.4.1-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync X-Debbugs-CC: elb...@debian.org Hi Maintainer As recently announced [1], the Release Team now considers packages that are out-of-sync

Processed: cluster3: fails to migrate to testing for too long

Processing control commands: > close -1 2.4.1-2 Bug #968436 [src:cluster3] cluster3: fails to migrate to testing for too long The source 'cluster3' and version '2.4.1-2' do not appear to match any binary packages Marked as fixed in versions cluster3/2.4.1-2. Bug #968436 [src:cluster3] cluster3: f

Bug#968431: bppsuite: fails to migrate to testing for too long

Source: bppsuite Version: 2.4.1-1 Severity: serious Control: close -1 2.4.1-2 Control: block -1 by 963088 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync X-Debbugs-CC: elb...@debian.org Hi Maintainer As recently announced [1], the Release Team now considers p

Processed: bppsuite: fails to migrate to testing for too long

Processing control commands: > close -1 2.4.1-2 Bug #968431 [src:bppsuite] bppsuite: fails to migrate to testing for too long Marked as fixed in versions bppsuite/2.4.1-2. Bug #968431 [src:bppsuite] bppsuite: fails to migrate to testing for too long Marked Bug as done > block -1 by 963088 Bug #968

Processed: severity of 968395 is normal, tagging 968395

Processing commands for cont...@bugs.debian.org: > severity 968395 normal Bug #968395 [terminator] Stretch update of {{ package }}? Severity set to 'normal' from 'grave' > tags 968395 + moreinfo Bug #968395 [terminator] Stretch update of {{ package }}? Added tag(s) moreinfo. > thanks Stopping proc

Bug#944599: marked as done (FTBFS with OCaml 4.08.1 (safe strings))

Your message dated Sat, 15 Aug 2020 08:29:08 + with message-id and subject line Bug#944599: fixed in ocaml-expect 0.0.6-1 has caused the Debian Bug report #944599, regarding FTBFS with OCaml 4.08.1 (safe strings) to be marked as done. This means that you claim that the problem has been dealt

Bug#968427: marked as done (Variables declared without extern in cairo_ocaml.h cause FTBFS)

Your message dated Sat, 15 Aug 2020 07:49:44 + with message-id and subject line Bug#968427: fixed in ocaml-cairo2 0.6.1+dfsg-5 has caused the Debian Bug report #968427, regarding Variables declared without extern in cairo_ocaml.h cause FTBFS to be marked as done. This means that you claim tha

Processed: bug 968427 is forwarded to https://github.com/Chris00/ocaml-cairo/issues/23

Processing commands for cont...@bugs.debian.org: > forwarded 968427 https://github.com/Chris00/ocaml-cairo/issues/23 Bug #968427 [src:libcairo2-ocaml-dev] Variables declared without extern in cairo_ocaml.h cause FTBFS Warning: Unknown package 'src:libcairo2-ocaml-dev' Set Bug forwarded-to-address