Bug#977023: marked as done (symbol lookup error in libbacktrace.so.0)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 08:04:32 + with message-id and subject line fixed in 1:10.0.0+r36-1 has caused the Debian Bug report #977023, regarding symbol lookup error in libbacktrace.so.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#957359: marked as done (infinipath-psm: ftbfs with GCC-10)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 08:20:50 + with message-id and subject line Bug#957359: fixed in infinipath-psm 3.3+20.604758e7-6.1 has caused the Debian Bug report #957359, regarding infinipath-psm: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has be

Processed: severity of 975963 is serious

2021-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 975963 serious Bug #975963 [bmake] bmake: /usr/share/mk is now a symlink, upgrades from non-symlinks are broken Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#979087: incompatible with node-postcss 8 and unmaintained

2021-01-03 Thread Pirate Praveen
Control: reassign -1 node-postcss-minify-font-values On Sat, 02 Jan 2021 21:48:11 +0530 Pirate Praveen wrote: > Package: node-postcss-filter-plugins,node-postcss-minify-font-values > Severity: serious > > Already filed request for removal. Filing rc bug in case the removal > takes longer than

Processed: Re: incompatible with node-postcss 8 and unmaintained

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 node-postcss-minify-font-values Bug #979087 [node-postcss-filter-plugins,node-postcss-minify-font-values] incompatible with node-postcss 8 and unmaintained Bug reassigned from package 'node-postcss-filter-plugins,node-postcss-minify-font-values' to 'no

Bug#947569: marked as done (FTBFS with scons 3.1.2-1)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 09:21:03 + with message-id and subject line Bug#947569: fixed in mongo-cxx-driver-legacy 1.1.3-3.1 has caused the Debian Bug report #947569, regarding FTBFS with scons 3.1.2-1 to be marked as done. This means that you claim that the problem has been dealt w

Bug#957434: marked as pending in apt

2021-01-03 Thread Julian Andres Klode
Control: tag -1 pending Hello, Bug #957434 in apt 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/apt-team/libept/-/commit/a1ec2bcb5ec235f5709b720f8cc6778d181d9

Processed: Bug#957434 marked as pending in apt

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #957434 [src:libept] libept: ftbfs with GCC-10 Added tag(s) pending. -- 957434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#968730: libnifti2: libniftiio.so.2 not provided

2021-01-03 Thread Juhani Numminen
Hi! Gianfranco, thanks for your valuable input. On Mon, 7 Dec 2020 01:15:35 +0100 Gianfranco Costamagna wrote: > Hello, how can three different binaries provide the very same old -dev > library? > > what happens now is that apt gets the old real cruft binary -dev package, and > not the virtu

Processed: #968730: For version tracking, assign to source package

2021-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Binary package libnifti2 is not built anymore in the fixed version. > # Assign to source package instead. > reassign 968730 src:nifticlib nifticlib/2.0.0+git186-g84740c2-1 Bug #968730 {Done: Gianfranco Costamagna } [libnifti2] libnifti2: libnif

Bug#957434: marked as done (libept: ftbfs with GCC-10)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 09:48:19 + with message-id and subject line Bug#957434: fixed in libept 1.2.1 has caused the Debian Bug report #957434, regarding libept: 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#979085: FTBFS on mips64el

2021-01-03 Thread YunQiang Su
On Sun, 3 Jan 2021 11:11:02 +0800 YunQiang Su wrote: > On Sun, 03 Jan 2021 00:08:34 +0800 Shengjing Zhu wrote: > > Source: sopt > > Version: 3.0.1-11 > > Severity: serious > > X-Debbugs-Cc: z...@debian.org > > > > > > When binNMU sopt, it FTBFS on mips64el, please check log at > > https://build

Bug#978704: marked as done (securefs: autopkgtests hard-code dependency on libcrypto++6)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 10:03:50 + with message-id and subject line Bug#978704: fixed in securefs 0.11.1+ds-2 has caused the Debian Bug report #978704, regarding securefs: autopkgtests hard-code dependency on libcrypto++6 to be marked as done. This means that you claim that the pr

Bug#978221: marked as done (osmo-bts: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 11:09:37 +0100 with message-id and subject line Resolved has caused the Debian Bug report #978221, regarding osmo-bts: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed to be marked as done. This means that you claim

Bug#978222: marked as done (osmo-sgsn: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 11:09:37 +0100 with message-id and subject line Resolved has caused the Debian Bug report #978222, regarding osmo-sgsn: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed to be marked as done. This means that you clai

Bug#978229: marked as done (osmo-bsc: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 11:09:37 +0100 with message-id and subject line Resolved has caused the Debian Bug report #978229, regarding osmo-bsc: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed to be marked as done. This means that you claim

Bug#978239: marked as done (openbsc: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 11:09:37 +0100 with message-id and subject line Resolved has caused the Debian Bug report #978239, regarding openbsc: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed to be marked as done. This means that you claim

Bug#978233: marked as done (osmo-hlr: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 11:09:37 +0100 with message-id and subject line Resolved has caused the Debian Bug report #978233, regarding osmo-hlr: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed to be marked as done. This means that you claim

Bug#978241: marked as done (osmo-msc: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 11:09:37 +0100 with message-id and subject line Resolved has caused the Debian Bug report #978241, regarding osmo-msc: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed to be marked as done. This means that you claim

Bug#978244: marked as done (libosmo-netif: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 11:09:37 +0100 with message-id and subject line Resolved has caused the Debian Bug report #978244, regarding libosmo-netif: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (< 0.7.0) but 4.4.13-2 is to be installed to be marked as done. This means that you

Bug#978391: marked as done (gdb-source no longer ships the gdb source)

2021-01-03 Thread Debian Bug Tracking System
tor Orón Martínez Changed-By: Matthias Klose Closes: 978391 Changes: gdb (10.1-1.6) unstable; urgency=high . * Non-maintainer upload. * Update to the gdb-10-branch 20210103 (copyright updates). * Fix building the gdb-source package. Closes: #978391. * Call dh_

Bug#979130: elpa-racket-mode: Fails to configure: "racket-mode.el:34:1:Error: Cannot open load file: No such file or directory, pos-tip" (Missing dependency on elpa-pos-tip?)

2021-01-03 Thread Axel Beckert
Package: elpa-racket-mode Version: 20201227git0-2 Severity: serious While trying to upgrade (no more sure from which version), elpa-racket-mode fails to configure on a Raspberry Pi (armhf) for me as follows: Setting up elpa-racket-mode (20201227git0-2) ... Install emacsen-common for emacs emacsen

Bug#957293: gnupg1: ftbfs with GCC-10

2021-01-03 Thread Christoph Biedl
Control: tags 957293 pending upstream 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 th

Processed: Re: Bug#957293: gnupg1: ftbfs with GCC-10

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags 957293 pending upstream Bug #957293 [src:gnupg1] gnupg1: ftbfs with GCC-10 Added tag(s) upstream and pending. -- 957293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#979133: rails: build failure is silently ignored

2021-01-03 Thread Pirate Praveen
Package: rails Version: 2:6.0.3.4+dfsg-2 Severity: serious When I rebuilt all the packages during the rollup plugin transitions, rails did not ftbfs, even though the rollup command actually failed. cd activestorage; mkdir node_modules; \ ln -s rollup-plugin-commonjs node_modules; rollup -c; cd

Processed: Debian bugs #947384, #950206, #950761

2021-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 947384 + pending Bug #947384 [ipmitool] ipmitool: conffile not removed: /etc/default/ipmievd Added tag(s) pending. > tags 950206 + pending Bug #950206 [ipmitool] ipmitool: ipmievd.service should be After=openipmi.service Added tag(s) pending

Bug#978391: marked as done (gdb-source no longer ships the gdb source)

2021-01-03 Thread Debian Bug Tracking System
tor Orón Martínez Changed-By: Matthias Klose Closes: 978391 Changes: gdb (10.1-1.7) unstable; urgency=high . * Non-maintainer upload. * Update to the gdb-10-branch 20210103 (copyright updates). * Fix building the gdb-source package. Closes: #978391. * Call dh_

Bug#979133: fixed this in master-6.0 branch

2021-01-03 Thread Pirate Praveen
Control: tags -1 pending I have fixed both issues (silent build failure and actual ftbfs due to rollup plugins change) in master-6.0 branch as quilt push -a did not succeed in master branch.

Processed: fixed this in master-6.0 branch

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #979133 [rails] rails: build failure is silently ignored Added tag(s) pending. -- 979133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#979137: s3ql: Update to newest upstream release

2021-01-03 Thread Nikolaus Rath
Package: s3ql Severity: serious Justification: N/A There is a new upstream release that fixes a number of bugs against the Debian package. However, it is blocked on a dependency on the python3-pyfuse3 module that is not in Debian. Uploading python3-pyfuse3 and the newest S3QL release would make t

Bug#959117: Unable to mount with fuse3 (fusermount: unknown option 'nonempty')

2021-01-03 Thread Nikolaus Rath
Control: severity 959117 important thanks Hi Graham, This package is up for adoption. The only that's needed to get it in shape again is to upgrade to the newest upstream release. However, this requires packaging the new python3-pyfuse3 dependency first. I'm also downgrading the severity, sinc

Processed: Re: Unable to mount with fuse3 (fusermount: unknown option 'nonempty')

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > severity 959117 important Bug #959117 [s3ql] Unable to mount with fuse3 (fusermount: unknown option 'nonempty') Severity set to 'important' from 'grave' -- 959117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959117 Debian Bug Tracking System Contact ow...@bu

Bug#976513: tuxmath: FTBFS: ld: network.o:./src/network.c:57: multiple definition of `lan_player_info'; menu_lan.o:./src/menu_lan.c:40: first defined here

2021-01-03 Thread Adrian Bunk
Control: forwarded -1 https://github.com/tux4kids/tuxmath/pull/15 Control: tags -1 patch On Sat, Dec 05, 2020 at 01:32:54PM +0100, Lucas Nussbaum wrote: > Source: tuxmath > Version: 2.0.3-6 > Severity: serious >... > Relevant part (hopefully): > > aarch64-linux-gnu-gcc -Wall -g -DDATA_PREFIX=\"/us

Processed: Re: Bug#976513: tuxmath: FTBFS: ld: network.o:./src/network.c:57: multiple definition of `lan_player_info'; menu_lan.o:./src/menu_lan.c:40: first defined here

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/tux4kids/tuxmath/pull/15 Bug #976513 [src:tuxmath] tuxmath: FTBFS: ld: network.o:./src/network.c:57: multiple definition of `lan_player_info'; menu_lan.o:./src/menu_lan.c:40: first defined here Set Bug forwarded-to-address to 'https:

Bug#978623: marked as done (src:connect-proxy: invalid maintainer address)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 12:33:21 + with message-id and subject line Bug#978623: fixed in connect-proxy 1.105-1.2 has caused the Debian Bug report #978623, regarding src:connect-proxy: invalid maintainer address to be marked as done. This means that you claim that the problem has b

Bug#979130: marked as done (elpa-racket-mode: Fails to configure: "racket-mode.el:34:1:Error: Cannot open load file: No such file or directory, pos-tip" (Missing dependency on elpa-pos-tip?))

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 12:52:43 + with message-id and subject line Bug#979130: fixed in racket-mode 20201227git0-3 has caused the Debian Bug report #979130, regarding elpa-racket-mode: Fails to configure: "racket-mode.el:34:1:Error: Cannot open load file: No such file or director

Bug#950761: ipmitool: CVE-2020-5208

2021-01-03 Thread Salvatore Bonaccorso
Hi Jörg, On Sat, Jan 02, 2021 at 01:22:09PM +0100, Salvatore Bonaccorso wrote: > Control: severity -1 grave > > Hi Jörg, Adam, > > On Wed, Feb 05, 2020 at 10:11:58PM +0100, Salvatore Bonaccorso wrote: > > Source: ipmitool > > Version: 1.8.18-8 > > Severity: important > > Tags: security upstream

Processed: Re: Bug#960707: libalure1: Binary rebuild with current libfluidsynth2

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #960707 [libalure1] libalure1: Binary rebuild with current libfluidsynth2 Bug #963122 [libalure1] bucklespring: error loading shared objectfile Severity set to 'serious' from 'normal' Severity set to 'serious' from 'normal' > found -1 1.2-6.1

Bug#963122: Bug#960707: libalure1: Binary rebuild with current libfluidsynth2

2021-01-03 Thread Axel Beckert
Control: severity -1 serious Control: found -1 1.2-6.1 Hi, Bastian Germann wrote in #960707: > libalure1 recommends libfluidsynth1. Please rebuild the package so that > it uses the libfluidsynth2 ABI and recommends the current package > version. It's worse than you and I expected: * That rebuil

Processed: Re: Bug#960707: libalure1: Binary rebuild with current libfluidsynth2

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #963122 [libalure1] bucklespring: error loading shared objectfile Bug #960707 [libalure1] libalure1: Binary rebuild with current libfluidsynth2 Ignoring request to change severity of Bug 963122 to the same value. Ignoring request to change sev

Bug#979142: FTBFS on s390x

2021-01-03 Thread Shengjing Zhu
Package: mtail Version: 3.0.0~rc38-1 Severity: serious X-Debbugs-Cc: z...@debian.org https://buildd.debian.org/status/logs.php?pkg=mtail&ver=3.0.0%7Erc38-1&arch=s390x It has been tried 3 times, still failed to build. Fail at the same place: === RUN TestReadFromPipe/10ms_false read_pipe_in

Bug#971216: Bug#977205: imagemagick: CVE-2020-29599

2021-01-03 Thread Salvatore Bonaccorso
Hi Bastien, Hope you are ok. On Tue, Dec 15, 2020 at 10:34:59AM +0100, Bastien ROUCARIES wrote: > Hi, > > As said on debian-provate go ahead please. I am late due to payjob issue. Alright attached is a proposed debdiff for covering the CVEs, but please double check them as well please (it inclu

Processed: severity of 976558 is important

2021-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 976558 important Bug #976558 [src:python-fluids] python-fluids: FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13 Severity set to 'imp

Bug#964834: marked as done (haskell-yi-language: BD-Uninstallable)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 14:26:00 + with message-id and subject line Bug#964834: fixed in haskell-yi-language 0.19.0-1 has caused the Debian Bug report #964834, regarding haskell-yi-language: BD-Uninstallable to be marked as done. This means that you claim that the problem has been

Bug#965206: marked as done (haskell-yi-language: Removal notice: broken and unmaintained)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 14:26:00 + with message-id and subject line Bug#965206: fixed in haskell-yi-language 0.19.0-1 has caused the Debian Bug report #965206, regarding haskell-yi-language: Removal notice: broken and unmaintained to be marked as done. This means that you claim th

Processed: fixed 966853 in 3.1.1-1

2021-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 966853 3.1.1-1 Bug #966853 [src:gophernicus] gophernicus: FTBFS: ld: file.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; gophernicus.o:/usr/include/tcpd.h:115: first defined here The source 'gophernicus' and version '3.

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

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 14:30:24 + with message-id and subject line Bug#978278: fixed in python-dateutil 2.8.1-5 has caused the Debian Bug report #978278, regarding python-dateutil: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as

Bug#978323: marked as done (gdb-bpf: FTBFS: tar: /usr/src/gdb.tar.*: Cannot open: No such file or directory)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 15:34:00 +0100 with message-id and subject line Re: gdb-bpf: FTBFS: tar: /usr/src/gdb.tar.*: Cannot open: No such file or directory has caused the Debian Bug report #978323, regarding gdb-bpf: FTBFS: tar: /usr/src/gdb.tar.*: Cannot open: No such file or directo

Bug#979146: gnat-gps: FTBFS because BD can not be installed (gnat-9 vs 10)

2021-01-03 Thread Sebastian Andrzej Siewior
Package: src:gnat-gps Version: 19.2-3 Severity: serious Tags: sid ftbfs Hi, some BD of gnat-gps depend on packages which were built by gnat-9 others moved to gnat-10. libgnatcoll-db and libgnatcoll-bindings changed their binary packages and the old ones are by built by gnat-9, the new ones are bu

Bug#966853: marked as done (gophernicus: FTBFS: ld: file.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; gophernicus.o:/usr/include/tcpd.h:115: first defined here)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 09:36:53 -0500 with message-id <20210103143653.2cpok3wgprquc...@zeta.rak.ac> and subject line Re: Bug#966853: gophernicus: FTBFS: ld: file.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; gophernicus.o:/usr/include/tcpd.h:115: first defined her

Processed: Re: Bug#918526: mtail: FTBFS randomly

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 -moreinfo Bug #918526 [src:mtail] mtail: FTBFS randomly Removed tag(s) moreinfo. > severity -1 serious Bug #918526 [src:mtail] mtail: FTBFS randomly Severity set to 'serious' from 'important' > retitle -1 mtail: FTBFS randomly / flaky autopkgtests Bug #918526

Bug#964834: marked as done (haskell-yi-language: BD-Uninstallable)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 14:49:10 + with message-id and subject line Bug#964834: fixed in haskell-yi-frontend-pango 0.19.1-1 has caused the Debian Bug report #964834, regarding haskell-yi-language: BD-Uninstallable to be marked as done. This means that you claim that the problem ha

Bug#964834: marked as done (haskell-yi-language: BD-Uninstallable)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 14:49:17 + with message-id and subject line Bug#964834: fixed in haskell-yi-frontend-vty 0.19.0-1 has caused the Debian Bug report #964834, regarding haskell-yi-language: BD-Uninstallable to be marked as done. This means that you claim that the problem has

Bug#964834: marked as done (haskell-yi-language: BD-Uninstallable)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 14:49:43 + with message-id and subject line Bug#964834: fixed in haskell-yi-mode-haskell 0.19.0-1 has caused the Debian Bug report #964834, regarding haskell-yi-language: BD-Uninstallable to be marked as done. This means that you claim that the problem has

Bug#968276: marked as done (yi: FTBFS in sid (missing deps))

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 14:50:24 + with message-id and subject line Bug#968276: fixed in yi 0.19.0-1 has caused the Debian Bug report #968276, regarding yi: FTBFS in sid (missing deps) to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#975756: marked as done (android-platform-frameworks-base: FTBFS: libs/androidfw/include/androidfw/ZipFileRO.h:44:15: error: conflicting declaration ‘typedef void* ZipArchiveHandle’)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 15:56:40 +0100 with message-id <9bebcb40-7a0a-798e-497c-5f30ec3d0...@eds.org> and subject line fixed has caused the Debian Bug report #975756, regarding android-platform-frameworks-base: FTBFS: libs/androidfw/include/androidfw/ZipFileRO.h:44:15: error: conflictin

Bug#976891: marked as done (fastboot exits with "fake placeholder until fastboot builds" message)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 15:56:27 +0100 with message-id and subject line fixed has caused the Debian Bug report #976891, regarding fastboot exits with "fake placeholder until fastboot builds" message to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#975468: marked as done (ruby-console: autopkgtest regression: error occurred while loading ./spec/console_spec.rb)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 15:51:56 + with message-id and subject line Bug#975468: fixed in ruby-console 1.10.1-2 has caused the Debian Bug report #975468, regarding ruby-console: autopkgtest regression: error occurred while loading ./spec/console_spec.rb to be marked as done. This

Bug#950761: RFS: ipmitool/1.8.18-11 [RC] -- utility for IPMI control with kernel driver or LAN interface (daemon)

2021-01-03 Thread Jörg Frings-Fürst
tags 950761 - pending thanks Hello Salvatore, hello @All, following a tip from Salvatore, I have added the missing commits. Although these can be incorporated manually, they are not reliably functional in at least two places due to the different code base. I think the best thing will be to wait

Processed: RFS: ipmitool/1.8.18-11 [RC] -- utility for IPMI control with kernel driver or LAN interface (daemon)

2021-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 950761 - pending Bug #950761 [src:ipmitool] ipmitool: CVE-2020-5208 Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 950761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950761 Deb

Bug#979156: Useless in Debian

2021-01-03 Thread David Prévot
Package: php-net-idna2 Severity: serious [ Reported by a team member to see the package removed from testing ] php-net-idna2 was introduced in Debian as part of the gnusocial packaging effort, but its ITP (#782812) has no activity for more than three years. Furthermore, php-net-idna2 in Debian se

Bug#952318: marked as done (f2fs-tools: FTBFS: dh_makeshlibs errors)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 16:33:45 + with message-id and subject line Bug#952318: fixed in f2fs-tools 1.14.0-1 has caused the Debian Bug report #952318, regarding f2fs-tools: FTBFS: dh_makeshlibs errors to be marked as done. This means that you claim that the problem has been dealt

Bug#970941: marked as done (f2fs-tools: CVE-2020-6070)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 16:33:45 + with message-id and subject line Bug#970941: fixed in f2fs-tools 1.14.0-1 has caused the Debian Bug report #970941, regarding f2fs-tools: CVE-2020-6070 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#973380: marked as done (CVE-2020-6104 CVE-2020-6105 CVE-2020-6106 CVE-2020-6107 CVE-2020-6108)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 16:33:45 + with message-id and subject line Bug#973380: fixed in f2fs-tools 1.14.0-1 has caused the Debian Bug report #973380, regarding CVE-2020-6104 CVE-2020-6105 CVE-2020-6106 CVE-2020-6107 CVE-2020-6108 to be marked as done. This means that you claim th

Bug#979158: fails to install under kernel version 5.10.0

2021-01-03 Thread Ryan Kavanagh
Package: zfs-dkms Version: 0.8.6-1 Severity: grave Justification: Renders package unusable Installing zfs-dkms fails with the following error message in /var/lib/dkms/zfs/0.8.6/build/make.log: CC [M] /var/lib/dkms/zfs/0.8.6/build/module/zfs/vdev_file.o /var/lib/dkms/zfs/0.8.6/build/module/zfs/

Processed: forcibly merging 977656 979158

2021-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 977656 979158 Bug #977656 [zfs-dkms] zfs-dkms: Fail to build with 5.10 kernel with "error: ‘struct percpu_ref’ has no member named ‘count’" Bug #979158 [zfs-dkms] fails to install under kernel version 5.10.0 Severity set to 'normal' fr

Processed: severity of 977656 is grave

2021-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 977656 grave Bug #977656 [zfs-dkms] zfs-dkms: Fail to build with 5.10 kernel with "error: ‘struct percpu_ref’ has no member named ‘count’" Bug #979158 [zfs-dkms] fails to install under kernel version 5.10.0 Severity set to 'grave' from '

Bug#978974: marked as done (freedict-tools FTBFS: No Python executable found, please make sure that a recent Python is in the search path.)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 3 Jan 2021 17:45:49 +0100 with message-id <20210103164549.GV7178@Kraftkrust> and subject line Dependency added has caused the Debian Bug report #978974, regarding freedict-tools FTBFS: No Python executable found, please make sure that a recent Python is in the search path.

Processed: Re: megadown: [python] is required and it's not installed

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #969885 [megadown] megadown: [python] is required and it's not installed Severity set to 'grave' from 'important' -- 969885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969885 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Bug#978341 marked as pending in node-babel

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978341 [node-babel7] node-recast: FTBFS: node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016: Could not find a declaration file for module '@babel/types'. '/<>/node_modules/@babel/types/lib/index.js' implicitly has an 'an

Bug#978341: marked as pending in node-babel

2021-01-03 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #978341 in node-babel 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/node-babel/-/commit/ef792ae3156ad698fba901f8adf

Bug#978209: marked as done (mrpt: FTBFS: mainwindow.h:218:2: error: reference to ‘Tracker’ is ambiguous)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 17:23:12 + with message-id and subject line Bug#978209: fixed in mrpt 1:2.1.7-1 has caused the Debian Bug report #978209, regarding mrpt: FTBFS: mainwindow.h:218:2: error: reference to ‘Tracker’ is ambiguous to be marked as done. This means that you claim

Bug#978384: marked as done (node-ast-types: FTBFS: node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016: Could not find a declaration file for module '@babel/types'. '/<

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 17:35:58 + with message-id and subject line Bug#978341: fixed in node-babel7 7.12.11+~cs150.141.84-3 has caused the Debian Bug report #978341, regarding node-ast-types: FTBFS: node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016: Could

Bug#978341: marked as done (node-recast: FTBFS: node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016: Could not find a declaration file for module '@babel/types'. '/<

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 17:35:58 + with message-id and subject line Bug#978341: fixed in node-babel7 7.12.11+~cs150.141.84-3 has caused the Debian Bug report #978341, regarding node-recast: FTBFS: node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016: Could no

Bug#956878: marked as done (groestlcoin: FTBFS: error: cannot convert 'std::atomic

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 19:03:34 + with message-id and subject line Bug#956878: fixed in groestlcoin 2.20.1~dfsg-1 has caused the Debian Bug report #956878, regarding groestlcoin: FTBFS: error: cannot convert 'std::atomic' to 'const UniValue&' to be marked as done. This means tha

Bug#976556: marked as done (latex-make: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 19:19:04 + with message-id and subject line Bug#976556: fixed in latex-make 2.4.2-1 has caused the Debian Bug report #976556, regarding latex-make: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as done. This means t

Bug#978216: marked as done (liborigin2: FTBFS: OriginObj.h:702:27: error: ‘find_if’ was not declared in this scope; did you mean ‘boost::mpl::find_if’?)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 19:35:44 + with message-id and subject line Bug#978216: fixed in liborigin2 2:20110117-4 has caused the Debian Bug report #978216, regarding liborigin2: FTBFS: OriginObj.h:702:27: error: ‘find_if’ was not declared in this scope; did you mean ‘boost::mpl::fi

Bug#978662: apertium-cy-en: autopkgtest failure

2021-01-03 Thread Nilesh Patra
Hi Tino, On Tue, 29 Dec 2020 23:21:15 +0100 Tino Didriksen wrote: > This is a chicken-and-egg problem that should solve itself. New apertium > 3.7.1 can't migrate until apertium-cy-en is fixed, but fixed apertium-cy-en > won't build correctly with existing apertium 3.6.1. On declaring hard depen

Processed: can't reproduce

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 1.6.1-2 Bug #972377 [src:pyasn] pyasn FTBFS: FileNotFoundError in tests The source 'pyasn' and version '1.6.1-2' do not appear to match any binary packages Marked as fixed in versions pyasn/1.6.1-2. -- 972377: https://bugs.debian.org/cgi-bin/bugreport.cgi

Bug#972377: can't reproduce

2021-01-03 Thread Hans-Christoph Steiner
Control: fixed -1 1.6.1-2 I can't reproduce this, perhaps it was fixed by the upgrade to Python 3.9. For example: https://salsa.debian.org/python-team/packages/pyasn/-/pipelines/214872

Bug#978662: marked as done (apertium-cy-en: autopkgtest failure)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 20:17:05 + with message-id and subject line Bug#978662: fixed in apertium-cy-en 0.1.1~r57554-7 has caused the Debian Bug report #978662, regarding apertium-cy-en: autopkgtest failure to be marked as done. This means that you claim that the problem has been

Bug#979173: libtool ftbfs with new gnulib

2021-01-03 Thread Helmut Grohne
Source: libtool Version: 2.4.6-14 Severity: serious Tags: ftbfs patch User: helm...@debian.org Usertags: rebootstrap libtool started to ftbfs with the recent gnulib upload. It needs to bump the autoconf version to build again. The attached patch makes it work again. Helmut --- libtool-2.4.6.orig/

Processed: bouncycastle: diff for NMU version 1.65-1.1

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags 977683 + patch Bug #977683 [src:bouncycastle] bouncycastle: CVE-2020-28052 Added tag(s) patch. > tags 977683 + pending Bug #977683 [src:bouncycastle] bouncycastle: CVE-2020-28052 Added tag(s) pending. -- 977683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#977683: bouncycastle: diff for NMU version 1.65-1.1

2021-01-03 Thread Salvatore Bonaccorso
Control: tags 977683 + patch Control: tags 977683 + pending Dear maintainer, X-Debbugs-CC'ing as well Markus Koschany. I've prepared an NMU for bouncycastle (versioned as 1.65-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Alternatively feel free to a

Bug#979174: node-express-generator: Incompatible with current node-commander and node-mkdirp

2021-01-03 Thread Xavier Guimard
Package: node-express-generator Version: 4.0.0-2 Severity: grave Tags: sid, ftbfs Justification: renders package unusable node-express-generator isn't compatible with current node-commander, neither node-mkdirp. As it has no reverse dependency, I suggest to remove it from Debian

Processed: closing 978324

2021-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 978324 Bug #978324 [src:gdb-mingw-w64] gdb-mingw-w64: FTBFS: tar: /usr/src/gdb.tar.*: Cannot open: No such file or directory Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 978324: https:

Bug#973082: confirmed

2021-01-03 Thread Hans-Christoph Steiner
Control: tags -1 help confirmed In Python 3.9, the plistlib was changed to no longer have the internal data structure plistlib.Data, which biplist relied on. Here's a potential fix: https://github.com/unified-font-object/ufoNormalizer/pull/74/files

Processed: confirmed

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help confirmed Bug #973082 [src:python-biplist] python-biplist: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13 Added tag(s) confirmed and help. -- 973082: https://bugs.debian.org/cgi-bin/bugrepo

Bug#977656: zfs-dkms: Fail to build with 5.10 kernel

2021-01-03 Thread Chris Dos
Just FYI, I'm running stock 5.10.0-rc7 with two patches for the new Intel Wireless 6E card compiled using the Debian Docs to create the kernel package. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977299 and Official OpenZFS 2.0.0 source that I compiled against 5.10.0-rc7 source and created th

Bug#976468: This package only builds Arch:all binary packages

2021-01-03 Thread Stephen Kitt
Control: severity -1 important Hi, On Sat, 5 Dec 2020 21:45:34 +0100 Lucas Nussbaum wrote: > This package only builds Arch:all binary packages. Unfortunately, I > don't think that we have a way to indicate that such binary packages > must be built on a specific architecture, and thus avoid a fai

Processed: Re: This package only builds Arch:all binary packages

2021-01-03 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #976468 [src:python-ptrace] python-ptrace: FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13 Severity set to 'important' from 'serious' -- 976468: https://

Bug#977489: rust-rand: autopkgtest regression in testing: error: could not compile `packed_simd`.

2021-01-03 Thread Peter Michael Green
Looking at https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rand/9312542/log.gz It looks like the packed_simd feature test passes with unstable's version of rust-packed-simd but the all features test is still failing with error[E0433]: failed to resolve: use of undeclared crate or

Bug#978431: texlive-base: dist-upgrade buster->bullseye fails

2021-01-03 Thread Hilmar Preuße
Am 27.12.2020 um 12:42 teilte Rene Engelhard mit: Hi, dist-upgrade buster->bullseye which just caused my system to not get out of apt -f install anymore: Entpacken von texlive-base (2020.20201203-2) über (2018.20190227-2) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-nSK

Bug#959904: marked as done (android-platform-system-tools-hidl: FTBFS no matching function for call to ‘find(std::vector >::const_iterator, std::vector

2021-01-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Jan 2021 22:48:32 + with message-id and subject line Bug#959904: fixed in android-platform-system-tools-hidl 10.0.0+r36-1 has caused the Debian Bug report #959904, regarding android-platform-system-tools-hidl: FTBFS no matching function for call to ‘find(std::vecto

Bug#977656: zfs-dkms: Fail to build with 5.10 kernel

2021-01-03 Thread Antonio Russo
tag -1 upstream thanks Giving an update here, since many people may be interested in a status report on this: - There is *no released version* of ZoL/OpenZFS that supports 5.10. - 5.10 appears to have been slightly more work for OpenZFS to adjust to. - As of e1d9228b0 (on their 2.0.1-staging bran

Bug#979156: Useless in Debian

2021-01-03 Thread Sunil Mohan Adapa
On 03/01/21 8:24 am, David Prévot wrote: > Package: php-net-idna2 > Severity: serious > > [ Reported by a team member to see the package removed from testing ] > > php-net-idna2 was introduced in Debian as part of the gnusocial > packaging effort, but its ITP (#782812) has no activity for more th

Bug#979184: rust-lazycell: newly introduced binary packages uninstallable.

2021-01-03 Thread plugwash
Package: rust-lazycell Version: 1.3.0-1 Severity: serious The upload of rust-lazycell 1.3.0-1 introduced three new binary packages, two of which are currently uninstallable. This is preventing the package from migrating to testing which is annoying the release team (see: https://bugs.debian.or

Bug#979156: Useless in Debian

2021-01-03 Thread David Prévot
Hi Sunil, Le 03/01/2021 à 20:06, Sunil Mohan Adapa a écrit : On 03/01/21 8:24 am, David Prévot wrote: […] php-net-idna2 was introduced in Debian as part of the gnusocial packaging effort […] Unless someone disagree with the above, I intend to ask for removal of this package soon (so if you

Bug#977489: marked as done (rust-rand: autopkgtest regression in testing: error: could not compile `packed_simd`.)

2021-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jan 2021 00:48:29 + with message-id and subject line Bug#977489: fixed in rust-rand 0.7.3-3 has caused the Debian Bug report #977489, regarding rust-rand: autopkgtest regression in testing: error: could not compile `packed_simd`. to be marked as done. This means th

Bug#979156: Useless in Debian

2021-01-03 Thread Sunil Mohan Adapa
On 03/01/21 4:48 pm, David Prévot wrote: > Hi Sunil, > > Le 03/01/2021 à 20:06, Sunil Mohan Adapa a écrit : >> On 03/01/21 8:24 am, David Prévot wrote: > […] >>> php-net-idna2 was introduced in Debian as part of the gnusocial >>> packaging effort […] > >>> Unless someone disagree with the above,

  1   2   >