Processed: Re: Bug#997045: saga: missing build dependency on pkg-config

2021-10-22 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #997045 [src:saga] saga: missing build dependency on pkg-config Added tag(s) pending. -- 997045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#997045: saga: missing build dependency on pkg-config

2021-10-22 Thread Sebastiaan Couwenberg
Control: tags -1 pending This was fixed in git a little while ago, the upload to unstable will follow soon. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1

Bug#996987: marked as done (dolfinx: FTBFS: unsatisfiable Build-Depends)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Sat, 23 Oct 2021 00:03:28 + with message-id and subject line Bug#996987: fixed in fenics-dolfinx 1:0.3.0-6 has caused the Debian Bug report #996987, regarding dolfinx: FTBFS: unsatisfiable Build-Depends to be marked as done. This means that you claim that the problem has

Processed: tagging 997045

2021-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 997045 + bookworm sid Bug #997045 [src:saga] saga: missing build dependency on pkg-config Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 997045:

Bug#997045: saga: missing build dependency on pkg-config

2021-10-22 Thread Adrian Bunk
Source: saga Version: 7.3.0+dfsg-5 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/saga.html https://buildd.debian.org/status/logs.php?pkg=saga=7.3.0%2Bdfsg-5%2Bb2 ... checking for omp_get_num_threads in -lgomp... yes checking for libsvm/svm.h...

Bug#996995: marked as done (dh-python: Unable to parse debian/control)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 20:34:11 + with message-id and subject line Bug#996995: fixed in dh-python 5.20211022.1 has caused the Debian Bug report #996995, regarding dh-python: Unable to parse debian/control to be marked as done. This means that you claim that the problem has been

Processed: source-highlight: diff for NMU version 3.1.9-4.1

2021-10-22 Thread Debian Bug Tracking System
Processing control commands: > tags 984342 + patch Bug #984342 [src:source-highlight] source-highlight: ftbfs with GCC-11 Bug #984218 [src:source-highlight] licenseutils: ftbfs with GCC-11 Added tag(s) patch. Added tag(s) patch. > tags 984342 + pending Bug #984342 [src:source-highlight]

Bug#984342: source-highlight: diff for NMU version 3.1.9-4.1

2021-10-22 Thread Boyuan Yang
Control: tags 984342 + patch Control: tags 984342 + pending Dear maintainer, I've prepared an NMU for source-highlight (versioned as 3.1.9-4.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru source-highlight-3.1.9/debian/changelog

Bug#984036: disulfinder: ftbfs with GCC-11

2021-10-22 Thread Nilesh Patra
On 10/22/21 9:23 PM, Étienne Mollier wrote: Hi Nilesh, Nilesh Patra, on 2021-10-22: looks like C++17 has removed the provision to specify custom exceptions, and there are a lot of errors like the one above. In this case, does it makes sense to force C++14 standard (with chnages in d/rules or

Bug#984036: disulfinder: ftbfs with GCC-11

2021-10-22 Thread Étienne Mollier
Hi Nilesh, Nilesh Patra, on 2021-10-22: > looks like C++17 has removed the provision to specify custom > exceptions, and there are a lot of errors like the one above. > In this case, does it makes sense to force C++14 standard > (with chnages in d/rules or with patches) in such cases and > ask

Bug#996226: marked as done (ruby-fakeweb: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_mock_open_with_string_as_registered_uri(TestFakeWebOpenURI): Errno::ENOENT: No such file or dire

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 19:52:25 + with message-id and subject line Bug#996226: fixed in ruby-fakeweb 1.3.0+git20170806+dfsg1-3 has caused the Debian Bug report #996226, regarding ruby-fakeweb: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error:

Bug#996226: marked as pending in ruby-fakeweb

2021-10-22 Thread Nilesh Patra
Control: tag -1 pending Hello, Bug #996226 in ruby-fakeweb 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:

Processed: Bug#996226 marked as pending in ruby-fakeweb

2021-10-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996226 [src:ruby-fakeweb] ruby-fakeweb: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_mock_open_with_string_as_registered_uri(TestFakeWebOpenURI): Errno::ENOENT: No such file or directory @ rb_sysopen -

Bug#996802: marked as done (llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10: Cannot find builtins library for the target architecture)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 19:18:53 + with message-id and subject line Bug#996802: fixed in llvm-toolchain-12 1:12.0.1-14 has caused the Debian Bug report #996802, regarding llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10: Cannot find builtins library for the target architecture

Bug#996312: marked as done (ruby-librarian: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 19:19:43 + with message-id and subject line Bug#996312: fixed in ruby-librarian 0.6.4-4 has caused the Debian Bug report #996312, regarding ruby-librarian: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object

Bug#984036: disulfinder: ftbfs with GCC-11

2021-10-22 Thread Nilesh Patra
On Wed, 03 Mar 2021 16:11:37 + Matthias Klose wrote: BRNN/RNNs/Options.h:69:5: error: ISO C++17 does not allow dynamic exception specifications 69 | throw(BadOptionSetting); | ^ BRNN/RNNs/Options.h:143:5: error: ISO C++17 does not allow dynamic exception specifications

Processed: Bug#996312 marked as pending in ruby-librarian

2021-10-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996312 [src:ruby-librarian] ruby-librarian: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block Added tag(s) pending. -- 996312:

Bug#996312: marked as pending in ruby-librarian

2021-10-22 Thread Nilesh Patra
Control: tag -1 pending Hello, Bug #996312 in ruby-librarian 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:

Bug#995139: marked as done (python-librtmp build-depends on removed package)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 19:03:41 + with message-id and subject line Bug#995139: fixed in python-librtmp 0.3.0-1.2 has caused the Debian Bug report #995139, regarding python-librtmp build-depends on removed package to be marked as done. This means that you claim that the problem

Bug#996995: marked as done (dh-python: Unable to parse debian/control)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 18:48:38 + with message-id and subject line Bug#996995: fixed in dh-python 5.20211022 has caused the Debian Bug report #996995, regarding dh-python: Unable to parse debian/control to be marked as done. This means that you claim that the problem has been

Bug#996995: dh-python: Unable to parse debian/control

2021-10-22 Thread stefanor
Hi Chris (2021.10.22_08:24:04_+) Thanks for the bug and the patch. I'm going to take a slightly different approach (and add test coverage). I thought it was too good to be true when my parsing rewrite passed all the tests on the first attempt :P SR -- Stefano Rivera

Bug#997031: nvidia-cuda-gdb: buster-backports /usr/bin/cuda-gdb 'Segmentation fault' at startup

2021-10-22 Thread Tim Trant
Package: nvidia-cuda-gdb Version: 11.2.152~11.2.2-2~bpo10+1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 10.11 APT prefers oldstable-updates APT policy: (990, 'oldstable-updates'), (990, 'oldstable'), (500, 'oldoldstable') Architecture:

Processed: tagging 997027, tagging 996976

2021-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 997027 + sid bookworm Bug #997027 [src:python-vispy] python-vispy: FTBFS with sphinx 4.2.0 Added tag(s) sid and bookworm. > tags 996976 + sid bookworm Bug #996976 [src:vtk6] vtk6: Remove vtk6 from the Debian 12 Added tag(s) bookworm and sid.

Processed: block 974792 with 996618

2021-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 974792 with 996618 Bug #974792 [beignet] beignet: Please upgrade to llvm-toolchain-11 Bug #974805 [beignet] beignet: Please upgrade to llvm-toolchain-11 974792 was not blocked by any bugs. 974792 was blocking: 974789 Added blocking bug(s)

Bug#984036: marked as done (disulfinder: ftbfs with GCC-11)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 16:49:05 + with message-id and subject line Bug#984036: fixed in disulfinder 1.2.11-11 has caused the Debian Bug report #984036, regarding disulfinder: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#997029: pysph: FTBFS in testing and unstable

2021-10-22 Thread Graham Inggs
Source: pysph Version: 1.0~b0~20191115.gite3d5e10-5 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds [1], pysph sometimes FTBS in both testing and unstable. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#997028: python-gsd: FTBFS with sphinx 4.2.0

2021-10-22 Thread Graham Inggs
Source: python-gsd Version: 2.4.2-1 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds, python-gsd FTBFS since sphinx 4.2.0 was uploaded. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#997027: python-vispy: FTBFS with sphinx 4.2.0

2021-10-22 Thread Graham Inggs
Source: python-vispy Version: 0.6.6-1 Severity: serious Tags: ftbfs patch Hi Maintainer python-vispy FTBFS with sphinx 4.2.0 since add_stylesheet was deprecated. It can be fixed by the simple patch below. Regards Graham --- a/doc/conf.py +++ b/doc/conf.py @@ -349,9 +349,9 @@ def

Bug#997026: libgpuarray: FTBFS with sphinx 4.2.0

2021-10-22 Thread Graham Inggs
Source: libgpuarray Version: 0.7.6-6 Severity: serious Tags: ftbfs patch Hi Maintainer libgpuarray FTBFS with sphinx 4.2.0 since add_stylesheet was deprecated. It can be fixed by the simple patch below. Regards Graham --- a/doc/conf.py +++ b/doc/conf.py @@ -116,7 +116,7 @@ html_theme =

Bug#996802: llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10: Cannot find builtins library for the target architecture

2021-10-22 Thread Sylvestre Ledru
Le 22/10/2021 à 12:03, Simon McVittie a écrit : Control: retitle -1 llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10: Cannot find builtins library for the target architecture Control: found -1 1:12.0.1-13 On Thu, 21 Oct 2021 at 10:19:01 +0100, Simon McVittie wrote: 1:12.0.1-11 has a

Bug#996712: libcache-memcached-fast-perl: autopkgtest failure on armhf: Fetched all keys / Match results

2021-10-22 Thread gregor herrmann
On Wed, 20 Oct 2021 21:34:50 +0200, gregor herrmann wrote: > I don't know what exacatly is going on, but I note that it now also > fails on amd64. And all other architectures … > I was a bit surprised that the same tests pass during build but the > explanation is simple: They are skipped as no

Bug#996028: [debian-mysql] Bug#996028: #996028 InnoDB: corrupted TRX_NO after upgrading to 10.3.31

2021-10-22 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2021-10-22 at 15:22 +0200, Ondrej Zary wrote: > With 10.3.29 running, I've dumped all databases (mysqldump --all-databases - > p >mysql.dump), then dropped all databases, stopped mariadb and deleted > /var/lib/mysql/ib*. > Then restarted

Bug#997003: php: CVE-2021-21703

2021-10-22 Thread Christian Göttsche
Source: php7.4 Version: 7.4.21-1+deb11u1 Severity: serious Tags: security fixed-upstream A privilege escalation vulnerability has been discovered in php (CVE-2021-21703). This has been fixed in upstream version 7.4.25.

Bug#995933: marked as done (smart-notifier: crashes: AttributeError: 'gi.repository.Gtk' object has no attribute 'main')

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 13:21:41 + with message-id and subject line Bug#995933: fixed in smart-notifier 0.28-8 has caused the Debian Bug report #995933, regarding smart-notifier: crashes: AttributeError: 'gi.repository.Gtk' object has no attribute 'main' to be marked as done.

Bug#996028: [debian-mysql] Bug#996028: #996028 InnoDB: corrupted TRX_NO after upgrading to 10.3.31

2021-10-22 Thread Ondrej Zary
On Friday 22 October 2021, Yves-Alexis Perez wrote: > On Thu, 2021-10-14 at 19:38 +0200, Ondrej Zary wrote: > >     MDEV-15912: Remove traces of insert_undo > > > >     Let us simply refuse an upgrade from earlier versions if the > >     upgrade procedure was not followed. This simplifies the

Processed: Re: magics++: FTBFS with PROJ 8.0.0

2021-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 983236 magics++/4.9.0-1 Bug #983236 [src:magics++] magics++: FTBFS with PROJ 8.0.0 Marked as fixed in versions magics++/4.9.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 983236:

Bug#996995: dh-python: Unable to parse debian/control

2021-10-22 Thread Christian Marillat
On 22 oct. 2021 09:24, "Chris Lamb" wrote: > tags 996995 + patch > severity 996995 serious > thanks > > Patch attached. This patch fix this issue. Christian

Bug#996985: marked as done (pbdagcon: autopkgtest regression)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 12:04:20 + with message-id and subject line Bug#996985: fixed in pbdagcon 0.3+git20180411.c14c422+dfsg-4 has caused the Debian Bug report #996985, regarding pbdagcon: autopkgtest regression to be marked as done. This means that you claim that the problem

Bug#994443: [R-pkg-team] Bug#994443: marked as done (r-bioc-deseq2: autopkgtest regression)

2021-10-22 Thread Michael R. Crusoe
On Thu, 21 Oct 2021 15:15:52 +0200 Graham Inggs wrote: > Control: reopen -1 > > r-bioc-deseq2's autopkgtests started to again pass in testing on > 2021-09-29, once r-bioc-tximportdata migrated. > However, the autopkgtests in stable continue to fail [1]. Correct, because the package

Processed: Bug#996985 marked as pending in pbdagcon

2021-10-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996985 [src:pbdagcon] pbdagcon: autopkgtest regression Added tag(s) pending. -- 996985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#996985: marked as pending in pbdagcon

2021-10-22 Thread Nilesh Patra
Control: tag -1 pending Hello, Bug #996985 in pbdagcon 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:

Bug#984243: Help: mothur: ftbfs with GCC-11

2021-10-22 Thread Aaron M. Ucko
Andreas Tille writes: > OK, I've implemented this in my last commit. Great, thanks! > Isn't > > # Get the list of all .cpp files, rename to .o files > # > OBJECTS=$(patsubst %.cpp,%.o,$(wildcard $(addsuffix *.cpp,$(subdirs > OBJECTS+=$(patsubst %.c,%.o,$(wildcard $(addsuffix

Bug#974806: marked as done (autofdo: Please upgrade to llvm-toolchain-11)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 11:33:40 + with message-id and subject line Bug#974802: fixed in autofdo 0.19-2.1 has caused the Debian Bug report #974802, regarding autofdo: Please upgrade to llvm-toolchain-11 to be marked as done. This means that you claim that the problem has been

Bug#974802: marked as done (autofdo: Please upgrade to llvm-toolchain-11)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 11:33:40 + with message-id and subject line Bug#974802: fixed in autofdo 0.19-2.1 has caused the Debian Bug report #974802, regarding autofdo: Please upgrade to llvm-toolchain-11 to be marked as done. This means that you claim that the problem has been

Bug#996028: [debian-mysql] Bug#996028: #996028 InnoDB: corrupted TRX_NO after upgrading to 10.3.31

2021-10-22 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2021-10-14 at 19:38 +0200, Ondrej Zary wrote: >     MDEV-15912: Remove traces of insert_undo > >     Let us simply refuse an upgrade from earlier versions if the >     upgrade procedure was not followed. This simplifies the purge, >    

Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31

2021-10-22 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2021-10-22 at 02:13 +0800, Marc Gallet wrote: > > Am I correct to assume this issue is still relevant for buster and that > for now, I should simply defer the upgrade (marking the packages to be > held back) and simply wait for this bug to

Processed: dolfinx

2021-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 996987 src:dolfinx src:fenics-dolfinx Bug #996987 [src:dolfinx] dolfinx: FTBFS: unsatisfiable Build-Depends Ignoring request to reassign bug #996987 to the same package Bug #996987 [src:dolfinx] dolfinx: FTBFS: unsatisfiable

Bug#947900: marked as done (chemical-mime-data: build-depends on unmaintained gnome-mime-data)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 10:33:29 + with message-id and subject line Bug#947900: fixed in chemical-mime-data 0.1.94-7.2 has caused the Debian Bug report #947900, regarding chemical-mime-data: build-depends on unmaintained gnome-mime-data to be marked as done. This means that you

Processed: Re: Bug#996947: llvm-toolchain-12: FTBFS on armel since 1:12.0.1-11: error: instruction requires: data-barriers

2021-10-22 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #996947 [src:llvm-toolchain-12] llvm-toolchain-12: FTBFS on armel since 1:12.0.1-11: error: instruction requires: data-barriers Added tag(s) moreinfo. -- 996947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996947 Debian Bug Tracking

Bug#996947: llvm-toolchain-12: FTBFS on armel since 1:12.0.1-11: error: instruction requires: data-barriers

2021-10-22 Thread Simon McVittie
Control: tags -1 + moreinfo On Thu, 21 Oct 2021 at 10:16:01 +0100, Simon McVittie wrote: > https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-12=armel=1%3A12.0.1-11=1634667108=0 > https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-12=armel=1%3A12.0.1-12=1634719287=0 >

Bug#996134: marked as done (ruby-beaker-hostgenerator: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError:)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 10:05:08 + with message-id and subject line Bug#996134: fixed in ruby-beaker-hostgenerator 1.7.1-1 has caused the Debian Bug report #996134, regarding ruby-beaker-hostgenerator: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:

Processed: tagging 997003

2021-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 997003 + upstream Bug #997003 [src:php7.4] php: CVE-2021-21703 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 997003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997003 Debian

Bug#996074: extension compatibility with GNOME Shell 41

2021-10-22 Thread Christian Lauinger
On Sun, 17 Oct 2021 12:54:28 +0100 Simon McVittie wrote: > Control: severity -1 serious > > On Sun, 10 Oct 2021 at 21:33:02 +0100, Simon McVittie wrote: > > The metadata.json for this extension doesn't declare compatibility with > > GNOME 41. I don't know whether the actual code will need

Processed: Re: Bug#996802: llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10: Cannot find builtins library for the target architecture

2021-10-22 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10: Cannot find > builtins library for the target architecture Bug #996802 [src:llvm-toolchain-12] llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10 and armhf since 1:12.0.1-11: Cannot find builtins

Bug#996802: llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10: Cannot find builtins library for the target architecture

2021-10-22 Thread Simon McVittie
Control: retitle -1 llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10: Cannot find builtins library for the target architecture Control: found -1 1:12.0.1-13 On Thu, 21 Oct 2021 at 10:19:01 +0100, Simon McVittie wrote: > 1:12.0.1-11 has a similar issue on armhf, presumably exposed by fixing >

Bug#997008: llvm-toolchain-12: FTBFS on armel: undefined reference to `__atomic_load_8' in scudo

2021-10-22 Thread Simon McVittie
Source: llvm-toolchain-12 Version: 1:12.0.1-13 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-12=armel=1%3A12.0.1-13=1634838707=0 > [326/735] : &&

Processed: tagging 991057

2021-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 991057 - pending Bug #991057 [src:gri] gri FTBFS with imagemagick with the #987504 change Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 991057:

Bug#996995: dh-python: Unable to parse debian/control

2021-10-22 Thread Chris Lamb
tags 996995 + patch severity 996995 serious thanks Patch attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/dhpython/debhelper.py b/dhpython/debhelper.py index 7308bbe..55b91c0 100644 ---

Processed: Re: dh-python: Unable to parse debian/control

2021-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 996995 + patch Bug #996995 [dh-python] dh-python: Unable to parse debian/control Added tag(s) patch. > severity 996995 serious Bug #996995 [dh-python] dh-python: Unable to parse debian/control Severity set to 'serious' from 'normal' > thanks

Bug#995832: libhealpix-cxx3: missing Breaks+Replaces: libhealpix-cxx2 (>= 3.80)

2021-10-22 Thread Christoph Berg
Hi, could you please tend to this bug with some urgency? I want to get pgsphere fixed which is depending on healpix-cxx. Christoph

Bug#996358: marked as done (autopkg test failures with pillow 8.3.2)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 01:02:10 -0700 with message-id <877de5wkql@melete.silentflame.com> and subject line Re: Bug#996358: autopkg test failures with pillow 8.3.2 has caused the Debian Bug report #996358, regarding autopkg test failures with pillow 8.3.2 to be marked as done.

Bug#996529: vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:

2021-10-22 Thread Diederik de Haas
Control: tag -1 upstream fixed-upstream On 14 Oct 2021 20:57:27 -0300 Antonio Terceiro wrote: > Source: vagrant > Version: 2.2.14+dfsg-1 > Severity: serious > Justification: FTBFS > Usertags: ruby3.0 https://github.com/hashicorp/vagrant/pull/12427 is titled "Updates for Ruby 3.0" and is part

Processed: Re: vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:

2021-10-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 upstream fixed-upstream Bug #996529 [src:vagrant] vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Added tag(s) fixed-upstream and upstream. -- 996529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996529 Debian Bug

Bug#996620: FTBFS: error: cannot bind non-const lvalue reference of type ‘temp_string&’ to an rvalue of type ‘temp_string’

2021-10-22 Thread Hilmar Preuße
Control: tags -1 + pending Am 16.10.2021 um 12:49 teilte Hilmar Preusse mit: Source: wp2latex Version: 3.100-1 Severity: serious Tags: upstream Justification: 4. Dear Maintainer, the package fails to build from source since gcc-11 is the default compiler: Patch is on salsa, tag pending.

Processed: Re: FTBFS: error: cannot bind non-const lvalue reference of type ‘temp_string&’ to an rvalue of type ‘temp_string’

2021-10-22 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #996620 [src:wp2latex] FTBFS: error: cannot bind non-const lvalue reference of type ‘temp_string&’ to an rvalue of type ‘temp_string’ Added tag(s) pending. -- 996620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996620 Debian Bug

Bug#984375: marked as done (uhd: ftbfs with GCC-11)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 06:03:55 + with message-id and subject line Bug#984375: fixed in uhd 3.15.0.0-5 has caused the Debian Bug report #984375, regarding uhd: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#984157: marked as done (gnss-sdr: ftbfs with GCC-11)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 06:03:55 + with message-id and subject line Bug#984375: fixed in uhd 3.15.0.0-5 has caused the Debian Bug report #984375, regarding gnss-sdr: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#984375: marked as done (uhd: ftbfs with GCC-11)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 06:03:55 + with message-id and subject line Bug#984157: fixed in uhd 3.15.0.0-5 has caused the Debian Bug report #984157, regarding uhd: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#984157: marked as done (gnss-sdr: ftbfs with GCC-11)

2021-10-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Oct 2021 06:03:55 + with message-id and subject line Bug#984157: fixed in uhd 3.15.0.0-5 has caused the Debian Bug report #984157, regarding gnss-sdr: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Re:

2021-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 984246 1:2.2.0-2 Bug #984246 {Done: José Luis Blanco Claraco } [src:mrpt] mrpt: ftbfs with GCC-11 Marked as fixed in versions mrpt/1:2.2.0-2. > End of message, stopping processing here. Please contact me if you need assistance. --

Bug#984243: Help: mothur: ftbfs with GCC-11

2021-10-22 Thread Andreas Tille
Hi Aaron, Am Thu, Oct 21, 2021 at 04:21:26PM -0400 schrieb Aaron M. Ucko: > > No, because std::byte supports far too few operations [1]. Instead, I'd > suggest encouraging upstream to rename their type, and meanwhile locally > patching source/uchime_src/makefile to add -std=c++14 to CXXFLAGS, >