Bug#1038909: marked as done (dd-opentracing-cpp: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Aug 2023 05:33:44 + with message-id and subject line Bug#1038909: fixed in dd-opentracing-cpp 1.3.7-1 has caused the Debian Bug report #1038909, regarding dd-opentracing-cpp: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023 to be marked a

Bug#1025011: Release request filed

2023-08-13 Thread Daniel Markstedt
For the record, I have filed a request with the Release Team now to get the green light to upload Bullseye packages. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049325

Processed: tagging 1037841

2023-08-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1037841 + patch Bug #1037841 [src:restinio] restinio: ftbfs with GCC-13 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037841 D

Bug#1037841: restinio: ftbfs with GCC-13

2023-08-13 Thread Amin Bandali
Dear Matthias, Felix, Please find attached a patch that should fix this. Would one of you please upload it as well? Thanks, -a Description: Fix FTBFS with GCC-13 For more details, see: https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes Author: Amin Bandali diff --git a/dev/test/r

Bug#1042889: marked as done (vm: autopkgtest fails against Emacs 29.1)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Aug 2023 01:18:45 + with message-id and subject line Bug#1042889: fixed in vm 8.2.0b-11 has caused the Debian Bug report #1042889, regarding vm: autopkgtest fails against Emacs 29.1 to be marked as done. This means that you claim that the problem has been dealt with

Processed: limit source to vm, tagging 1042889

2023-08-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source vm Limiting to bugs with field 'source' containing at least one of 'vm' Limit currently set to 'source':'vm' > tags 1042889 + pending Bug #1042889 [src:vm] vm: autopkgtest fails against Emacs 29.1 Added tag(s) pending. > thanks Stopp

Bug#1047864: impressive: Crashes at startup: «module 'PIL.Image' has no attribute 'ANTIALIAS'»

2023-08-13 Thread Gunnar Wolf
Package: impressive Version: 0.13.1-1 Severity: grave Justification: renders package unusable Hello again, I have stumbled upon a new bug that affects impressive :-( When starting up, I see the logo screen, but immediately afterwards, impressive crashes with the following: $ impressive test

Bug#1042889: vm breakage with Emacs 29

2023-08-13 Thread Ian Jackson
Dirk Eddelbuettel writes ("Bug#1042889: vm breakage with Emacs 29"): > Yes given the previous bug report and fix ensuring no byte-compilation takes > place for vm may be best. At least until someone (upstream? another dev?) > understand why it breaks vm. FTR, I investigated this a bit and I discov

Bug#1041491: marked as done (yuzu: FTBFS: Unmet build dependencies: glslang-tools:native)

2023-08-13 Thread Andrea Pappacoda
Il 13 agosto 2023 23:16:23 CEST, Debian Bug Tracking System ha scritto: >Your message dated Sun, 13 Aug 2023 23:13:56 +0200 >with message-id <0aa416df-8488-49ee-a38a-b57dbb2cf...@debian.org> >and subject line Re: yuzu: FTBFS: Unmet build dependencies: >glslang-tools:native >has caused the Deb

Bug#1041491: marked as done (yuzu: FTBFS: Unmet build dependencies: glslang-tools:native)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 23:13:56 +0200 with message-id <0aa416df-8488-49ee-a38a-b57dbb2cf...@debian.org> and subject line Re: yuzu: FTBFS: Unmet build dependencies: glslang-tools:native has caused the Debian Bug report #1041491, regarding yuzu: FTBFS: Unmet build dependencies: glslang-t

Bug#1045688: FTBFS: Could NOT find zstd (missing: zstd_LIBRARY zstd_INCLUDE_DIR)

2023-08-13 Thread Aurelien Jarno
Source: rocm-device-libs Version: 5.2.3-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, rocm-device-libs fails to build from source. From my build log on amd64: | -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo

Bug#1043451: libopencsd: binary-any FTBFS

2023-08-13 Thread Aurelien Jarno
control: tag -1 + patch On 2023-08-11 14:14, Adrian Bunk wrote: > Source: libopencsd > Version: 1.3.3-1 > Severity: serious > Tags: ftbfs trixie sid > > https://buildd.debian.org/status/fetch.php?pkg=libopencsd&arch=riscv64&ver=1.3.3-1&stamp=1691714850&raw=0 > > ... >debian/rules override_dh

Processed: Re: Bug#1043451: libopencsd: binary-any FTBFS

2023-08-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + patch Bug #1043451 [src:libopencsd] libopencsd: binary-any FTBFS Added tag(s) patch. -- 1043451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1045145: Netdata, since v1.41.0, includes a new, non-free version of the dashboard

2023-08-13 Thread Ratchanan Srirattanamet
Source: netdata Version: 1.41.0-1 Severity: serious Starting from version 1.41.0, Netdata has started to include their new agent dashboard - the so-called Cloud UI (or sometimes v2) [1]. This, however, is distributed under a different license than the rest of Netdata - the Netdata Cloud UI Lic

Bug#1037742: marked as done (libssw: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 19:13:36 + with message-id and subject line Bug#1042114: fixed in libssw 1.1-14 has caused the Debian Bug report #1042114, regarding libssw: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 19:13:36 + with message-id and subject line Bug#1037742: fixed in libssw 1.1-14 has caused the Debian Bug report #1037742, regarding libssw: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 19:13:36 + with message-id and subject line Bug#1042114: fixed in libssw 1.1-14 has caused the Debian Bug report #1042114, regarding libssw: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be

Bug#1037742: marked as done (libssw: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 19:13:36 + with message-id and subject line Bug#1037742: fixed in libssw 1.1-14 has caused the Debian Bug report #1037742, regarding libssw: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#1037720: marked as done (libbpp-qt: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 19:13:12 + with message-id and subject line Bug#1037720: fixed in libbpp-qt 2.4.1-9 has caused the Debian Bug report #1037720, regarding libbpp-qt: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If th

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 19:13:12 + with message-id and subject line Bug#1037720: fixed in libbpp-qt 2.4.1-9 has caused the Debian Bug report #1037720, regarding libbpp-qt: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output belo

Bug#1045144: grpc-java: binary-any FTBFS with recent jdupes

2023-08-13 Thread Aurelien Jarno
Source: grpc-java Version: 1.41.3+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, grpc-java fails to build from source when building only binary-any and not binary-all: | make[1]: Leaving directory '/<>' |dh_i

Processed: src:gmap: fails to migrate to testing for too long: FTBFS on !amd64

2023-08-13 Thread Debian Bug Tracking System
Processing control commands: > close -1 2023-07-20+ds-1 Bug #1045094 [src:gmap] src:gmap: fails to migrate to testing for too long: FTBFS on !amd64 Marked as fixed in versions gmap/2023-07-20+ds-1. Bug #1045094 [src:gmap] src:gmap: fails to migrate to testing for too long: FTBFS on !amd64 Marked

Bug#1045094: src:gmap: fails to migrate to testing for too long: FTBFS on !amd64

2023-08-13 Thread Paul Gevers
Source: gmap Version: 2021-12-17+ds-3 Severity: serious Control: close -1 2023-07-20+ds-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1041451 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing

Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting

2023-08-13 Thread Aurelien Jarno
Dear maintainer, On 2023-08-13 11:40, Aurelien Jarno wrote: > Dear maintainer, > > On 2023-08-13 10:53, Aurelien Jarno wrote: > > On 2023-07-26 22:03, Lucas Nussbaum wrote: > > > Source: imath > > > Version: 3.1.6-1 > > > Severity: serious > > > Justification: FTBFS > > > Tags: trixie sid ftbfs >

Bug#1044138: RM: pcmanx-gtk2 -- RoQA; dead upstream; depends on gtk2

2023-08-13 Thread Bastian Germann
Source: pcmanx-gtk2 Severity: serious Version: 1.3-2 pcmanx-gtk2 does not seem to be used a lot anymore. I intend to file a RM bug. If you have any reasons to keep it in Debian please voice them here. To get people's attention, I am filing as a serious bug and will reassign to the FTP team when t

Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting

2023-08-13 Thread Aurelien Jarno
On 2023-08-13 17:55, Michael Tokarev wrote: > On Sun, 13 Aug 2023 11:40:11 +0200 Aurelien Jarno wrote: > .. > > The solution to fix this is to use PYIMATH_OVERRIDE_PYTHON_INSTALL_DIR > > to define the installation of the Python modules instead of relying on > > autodetection. > > Can't this be do

Bug#1035694: marked as done (python-bottle: tox 4 support: Build-Depend on python3-wheel)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 16:19:48 + with message-id and subject line Bug#1035694: fixed in python-bottle 0.12.23-1.2 has caused the Debian Bug report #1035694, regarding python-bottle: tox 4 support: Build-Depend on python3-wheel to be marked as done. This means that you claim that

Bug#1042512: marked as done (src:python-numpysane: fails to migrate to testing for too long: uploader built arch:all binary)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 15:50:23 + with message-id and subject line Bug#1042512: fixed in python-numpysane 0.39-1.1 has caused the Debian Bug report #1042512, regarding src:python-numpysane: fails to migrate to testing for too long: uploader built arch:all binary to be marked as d

Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting

2023-08-13 Thread Michael Tokarev
On Sun, 13 Aug 2023 11:40:11 +0200 Aurelien Jarno wrote: .. The solution to fix this is to use PYIMATH_OVERRIDE_PYTHON_INSTALL_DIR to define the installation of the Python modules instead of relying on autodetection. Can't this be done at the cmake level instead of overriding this in each pack

Bug#1028111: marked as done (r-cran-clock: autopkgtest failure on 32bit)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 14:52:07 + with message-id and subject line Bug#1028111: fixed in r-cran-clock 0.7.0-1.1 has caused the Debian Bug report #1028111, regarding r-cran-clock: autopkgtest failure on 32bit to be marked as done. This means that you claim that the problem has bee

Bug#1043417: marked as done (libwraster6: libwraster ABI breakage)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 13:04:56 + with message-id and subject line Bug#1043417: fixed in wmaker 0.96.0-2 has caused the Debian Bug report #1043417, regarding libwraster6: libwraster ABI breakage to be marked as done. This means that you claim that the problem has been dealt with.

Processed (with 1 error): transition: libunistring

2023-08-13 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:libunistring Bug #1043599 [release.debian.org] transition: libunistring Added indication that 1043599 affects src:libunistring > forwarded -1  > https://release.debian.org/transitions/html/auto-libunistring.html Unknown command or malformed arguments

Bug#1037721: marked as done (libbpp-seq: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 12:43:29 + with message-id and subject line Bug#1042204: fixed in libbpp-seq 2.4.1-10 has caused the Debian Bug report #1042204, regarding libbpp-seq: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 12:43:29 + with message-id and subject line Bug#1042204: fixed in libbpp-seq 2.4.1-10 has caused the Debian Bug report #1042204, regarding libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output b

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 12:43:29 + with message-id and subject line Bug#1037721: fixed in libbpp-seq 2.4.1-10 has caused the Debian Bug report #1037721, regarding libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output b

Bug#1037721: marked as done (libbpp-seq: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 12:43:29 + with message-id and subject line Bug#1037721: fixed in libbpp-seq 2.4.1-10 has caused the Debian Bug report #1037721, regarding libbpp-seq: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Debian bug #1026820 FTBFS: Fail to build with libunistring5

2023-08-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > Severity 1026820 serious Bug #1026820 [src:clisp] FTBFS: Fail to build with libunistring5 Severity set to 'serious' from 'important' > -- Stopping processing here. Please contact me if you need assistance. -- 1026820: https://bugs.debian.org/cgi

Bug#1042145: marked as done (rust-rtnetlink: FTBFS: unsatisfiable build-dependencies: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 13:20:07 +0100 with message-id and subject line re: rust-rtnetlink: FTBFS: unsatisfiable build-dependencies: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~) has caused the Debian Bug report #

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 11:34:16 + with message-id and subject line Bug#1042230: fixed in libbpp-core 2.4.1-11 has caused the Debian Bug report #1042230, regarding libbpp-core: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output

Processed: found 1043501 in 1.18.4-2

2023-08-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1043501 1.18.4-2 Bug #1043501 [src:gst-plugins-ugly1.0] gst-plugins-ugly1.0: ZDI-CAN-21443 ZDI-CAN-21444 Marked as found in versions gst-plugins-ugly1.0/1.18.4-2. > thanks Stopping processing here. Please contact me if you need assistance.

Processed: fixed 1043501 in 1.18.4-2+deb11u1, fixed 1043501 in 1.22.0-2+deb12u1

2023-08-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1043501 1.18.4-2+deb11u1 Bug #1043501 [src:gst-plugins-ugly1.0] gst-plugins-ugly1.0: ZDI-CAN-21443 ZDI-CAN-21444 Marked as fixed in versions gst-plugins-ugly1.0/1.18.4-2+deb11u1. > fixed 1043501 1.22.0-2+deb12u1 Bug #1043501 [src:gst-plugin

Processed: fixed 1041110 in 14.4.2+git20190427-3.2

2023-08-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1041110 14.4.2+git20190427-3.2 Bug #1041110 {Done: Bastien Roucariès } [src:sox] sox: CVE-2023-34432 Marked as fixed in versions sox/14.4.2+git20190427-3.2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042230: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042230, regarding libbpp-core: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff o

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042204: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042204, regarding libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff ou

Bug#1037721: marked as done (libbpp-seq: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042204: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042204, regarding libbpp-seq: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1037722: marked as done (libbpp-seq-omics: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042139: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042139, regarding libbpp-seq-omics: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been de

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042139: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042139, regarding libbpp-seq-omics: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see d

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042137: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042137, regarding libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff o

Bug#1037718: marked as done (libbpp-phyl: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042137: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042137, regarding libbpp-phyl: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt w

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037722: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037722, regarding libbpp-seq-omics: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see d

Bug#1037722: marked as done (libbpp-seq-omics: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037722: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037722, regarding libbpp-seq-omics: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been de

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037721: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037721, regarding libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff ou

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037718: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037718, regarding libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff o

Bug#1037721: marked as done (libbpp-seq: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037721: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037721, regarding libbpp-seq: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt wi

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

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:49:57 + with message-id and subject line Bug#1037718: fixed in libbpp-phyl 2.4.1-9 has caused the Debian Bug report #1037718, regarding libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output

Bug#1037718: marked as done (libbpp-phyl: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037718: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037718, regarding libbpp-phyl: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1037718: marked as done (libbpp-phyl: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:49:57 + with message-id and subject line Bug#1037718: fixed in libbpp-phyl 2.4.1-9 has caused the Debian Bug report #1037718, regarding libbpp-phyl: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. I

Processed: Bug#1037718 marked as pending in libbpp-phyl

2023-08-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1037718 [src:libbpp-phyl] libbpp-phyl: ftbfs with GCC-13 Bug #1042137 [src:libbpp-phyl] libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Added tag(s) pending. Added tag(s)

Bug#1037718: marked as pending in libbpp-phyl

2023-08-13 Thread Étienne Mollier
Control: tag -1 pending Hello, Bug #1037718 in libbpp-phyl 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/med-team/libbpp-phyl/-/commit/38f671626f6ec730aa6efe9

Bug#1041110: marked as done (sox: CVE-2023-34432)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:20:03 + with message-id <3800367.xhOnM9cPy3@portable-bastien> and subject line Fixed by fix of CVE-2021-23159 and CVE-2021-23172 has caused the Debian Bug report #1041110, regarding sox: CVE-2023-34432 to be marked as done. This means that you claim that

Processed: Re: systemd-boot postinst update causes EFI crash

2023-08-13 Thread Debian Bug Tracking System
Processing control commands: > severity -1 minor Bug #1043583 [systemd-boot] systemd-boot postinst update causes EFI crash Severity set to 'minor' from 'critical' > tags -1 moreinfo Bug #1043583 [systemd-boot] systemd-boot postinst update causes EFI crash Added tag(s) moreinfo. -- 1043583: https

Bug#1043583: systemd-boot postinst update causes EFI crash

2023-08-13 Thread Luca Boccassi
Control: severity -1 minor Control: tags -1 moreinfo On Sun, 13 Aug 2023 12:59:07 +0300 Maria Lisina wrote: > Package: systemd-boot > Version: 252.12-1~deb12u1 > Severity: critical > Tags: patch > Justification: breaks unrelated software > X-Debbugs-Cc: sekoohaka.sari...@gmail.com > > Dear Maint

Bug#1043584: pbbam FTBFS with pbcopper 2.2.0

2023-08-13 Thread Adrian Bunk
Source: pbbam Version: 2.1.0+dfsg-2 Severity: serious Tags: ftbfs trixie sid Forwarded: https://github.com/PacificBiosciences/pbbam/commit/1142a51493d2b047f6f8c71931ced230f593ef2b https://buildd.debian.org/status/fetch.php?pkg=pbbam&arch=amd64&ver=2.1.0%2Bdfsg-2%2Bb1&stamp=1691776254&raw=0 ... F

Bug#1040960: marked as done (gcc-sh-elf binary-all build rejected)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:04:04 + with message-id and subject line Bug#1040960: fixed in gcc-sh-elf 8 has caused the Debian Bug report #1040960, regarding gcc-sh-elf binary-all build rejected to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1037689: marked as done (hhsuite: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:04:13 + with message-id and subject line Bug#1037689: fixed in hhsuite 3.3.0+ds-8 has caused the Debian Bug report #1037689, regarding hhsuite: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1041029: marked as done (zimlib FTBFS with googletest 1.13.0)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 10:00:11 + with message-id and subject line Bug#1041029: fixed in libzim 8.2.1-1 has caused the Debian Bug report #1041029, regarding zimlib FTBFS with googletest 1.13.0 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1043583: systemd-boot postinst update causes EFI crash

2023-08-13 Thread Maria Lisina
Package: systemd-boot Version: 252.12-1~deb12u1 Severity: critical Tags: patch Justification: breaks unrelated software X-Debbugs-Cc: sekoohaka.sari...@gmail.com Dear Maintainer, when systemd-boot updates and if bootctl is-installed reports 0, it runs bootctl update --graceful without --no-variabl

Processed: tagging 1042171

2023-08-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1042171 + pending Bug #1042171 [src:imath] imath: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042171: https://bugs.debian.org/cgi-

Processed: tagging 1042171

2023-08-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1042171 + patch Bug #1042171 [src:imath] imath: FTBFS: dh_install: error: missing files, aborting Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042171: https://bugs.debian.org/cgi-bin/

Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting

2023-08-13 Thread Aurelien Jarno
Dear maintainer, On 2023-08-13 10:53, Aurelien Jarno wrote: > On 2023-07-26 22:03, Lucas Nussbaum wrote: > > Source: imath > > Version: 3.1.6-1 > > Severity: serious > > Justification: FTBFS > > Tags: trixie sid ftbfs > > User: lu...@debian.org > > Usertags: ftbfs-20230726 ftbfs-trixie > > > > Hi

Bug#1037662: marked as done (flye: ftbfs with GCC-13)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 09:18:51 + with message-id and subject line Bug#1037662: fixed in flye 2.9.2+dfsg-2 has caused the Debian Bug report #1037662, regarding flye: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting

2023-08-13 Thread Aurelien Jarno
On 2023-08-13 10:53, Aurelien Jarno wrote: > On 2023-07-26 22:03, Lucas Nussbaum wrote: > > Source: imath > > Version: 3.1.6-1 > > Severity: serious > > Justification: FTBFS > > Tags: trixie sid ftbfs > > User: lu...@debian.org > > Usertags: ftbfs-20230726 ftbfs-trixie > > > > Hi, > > > > During

Bug#1043417: libwraster6: libwraster ABI breakage

2023-08-13 Thread Andreas Metzler
On 2023-08-10 "Torrance, Douglas" wrote: [...] > I've applied the patch that you submitted upstream [1] to the package. I > think this should fix the issue. See the latest draft in Salsa [2]. > Does this look okay? Thank you, yes. (As you are no doubt aware) there is a functionally identally

Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting

2023-08-13 Thread Aurelien Jarno
On 2023-07-26 22:03, Lucas Nussbaum wrote: > Source: imath > Version: 3.1.6-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230726 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on

Bug#1037689: marked as pending in hhsuite

2023-08-13 Thread Étienne Mollier
Control: tag -1 pending Hello, Bug #1037689 in hhsuite 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/med-team/hhsuite/-/commit/5538ace5c83d75ccf3bd22ef8cfa74c

Processed: Bug#1037689 marked as pending in hhsuite

2023-08-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1037689 [src:hhsuite] hhsuite: ftbfs with GCC-13 Added tag(s) pending. -- 1037689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1037662: marked as pending in flye

2023-08-13 Thread Étienne Mollier
Control: tag -1 pending Hello, Bug #1037662 in flye 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/med-team/flye/-/commit/b50fc2b3b4393d39136ea6cd9d2063ac08961

Processed: Bug#1037662 marked as pending in flye

2023-08-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1037662 [src:flye] flye: ftbfs with GCC-13 Added tag(s) pending. -- 1037662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1035639: marked as done (git-imerge: FTBFS with tox 4)

2023-08-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Aug 2023 07:05:30 + with message-id and subject line Bug#1035639: fixed in git-imerge 1.2.0-4 has caused the Debian Bug report #1035639, regarding git-imerge: FTBFS with tox 4 to be marked as done. This means that you claim that the problem has been dealt with. If t