Bug#966864: libiscsi: FTBFS: ld: .libs/libiscsi_la-iser.o:./lib/./../include/iser-private.h:162: multiple definition of `__packed'; .libs/libiscsi_la-init.o:./lib/./../include/iser-private.h:162: firs

Source: libiscsi Version: 1.19.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC

Bug#966857: libtpms: FTBFS: tpm2/NVDynamic.c:126:10: error: ‘nvHandle’ may be used uninitialized in this function [-Werror=maybe-uninitialized]

Source: libtpms Version: 0.8.0~dev1-1.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool

Bug#966863: gmap: FTBFS: ld: gmap_nosimd-dynprog_end.o:./src/dynprog_end.c:112: multiple definition of `homopolymerp'; gmap_nosimd-dynprog_single.o:./src/dynprog_single.c:94: first defined here

Source: gmap Version: 2020-06-30+ds-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -pthread

Bug#966861: vilistextum: FTBFS: ld: html.o:./src/text.h:16: multiple definition of `ch'; charset.o:./src/text.h:16: first defined here

Source: vilistextum Version: 2.6.9-1.2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -Wall -O2 -ansi -g -O2

Bug#966862: gramophone2: FTBFS: ld: /tmp/ccWY0lhU.o:./global.h:70: multiple definition of `midi'; /tmp/ccHnI4GU.o:./global.h:70: first defined here

Source: gramophone2 Version: 0.8.13a-3.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -Wdate-time

Bug#966855: hexcurse: FTBFS: ld: llist.o:./src/../include/hex.h:129: multiple definition of `fpOUT'; file.o:./src/../include/hex.h:129: first defined here

Source: hexcurse Version: 1.58-1.2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -g -O2

Bug#966859: libu2f-host: FTBFS: u2fmisc.c:117:55: error: 'FALSE' undeclared (first use in this function)

Source: libu2f-host Version: 1.1.10-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC

Processed: found 966838 in 2:6.0.3.2+dfsg-4

Processing commands for cont...@bugs.debian.org: > found 966838 2:6.0.3.2+dfsg-4 Bug #966838 [rails] rails: newapp autopkgtest failed and it also broke autopkgtest for many rails assets packages Marked as found in versions rails/2:6.0.3.2+dfsg-4. > thanks Stopping processing here. Please

Bug#966735: marked as done (fvwm-crystal: Unversioned Python removal in sid/bullseye)

Your message dated Mon, 03 Aug 2020 07:18:57 + with message-id and subject line Bug#966735: fixed in fvwm-crystal 3.4.1+dfsg-2 has caused the Debian Bug report #966735, regarding fvwm-crystal: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#966670: marked as done (pixelmed FTBFS: iconv: illegal input sequence at position 19)

Your message dated Mon, 03 Aug 2020 07:20:12 + with message-id and subject line Bug#966670: fixed in pixelmed 20200416-2 has caused the Debian Bug report #966670, regarding pixelmed FTBFS: iconv: illegal input sequence at position 19 to be marked as done. This means that you claim that the

Bug#945673: marked as done (fvwm-crystal: Python2 removal in sid/bullseye)

Your message dated Mon, 03 Aug 2020 07:18:57 + with message-id and subject line Bug#966735: fixed in fvwm-crystal 3.4.1+dfsg-2 has caused the Debian Bug report #966735, regarding fvwm-crystal: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#946882: blk-availability.service: may fail or unmount filesystems too soon

I don't know if it's relevant, but I'm getting this a warning at boot with this service: systemd[1]: /lib/systemd/system/blk-availability.service:10: Neither a valid executable name nor an absolute path: ${exec_prefix}/bin/true lvm2/2.03.09-2

Bug#966838: this appears to be caused by our patch

debian/patches/0001-Be-careful-with-that-bundler.patch

Bug#966838: how to reproduce

We can reproduce this by just running rails new foo $ rails new foo create create README.md create Rakefile create .ruby-version create config.ru create .gitignore create Gemfile run git init from "." Initialized empty Git repository in /tmp/foo/.git/

Bug#966670: marked as pending in pixelmed

Control: tag -1 pending Hello, Bug #966670 in pixelmed 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#966670 marked as pending in pixelmed

Processing control commands: > tag -1 pending Bug #966670 [src:pixelmed] pixelmed FTBFS: iconv: illegal input sequence at position 19 Added tag(s) pending. -- 966670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: bump severities of packages failing with rails 6

Processing commands for cont...@bugs.debian.org: > severity 964143 serious Bug #964143 [schleuder] schleuder: ftbfs with Rails 6 in experimental - Could not find 'activerecord' (~> 5.2) - did find: [activerecord-6.0.3.1] Severity set to 'serious' from 'important' > severity 964952 serious Bug

Bug#966839: openmm: withhold the package until a stable release

Source: openmm Severity: grave Owner: Andrius Merkys Control: forwarded -1 https://github.com/openmm/openmm/issues/2784 Hello, The upstream expressed their concern that packaging development version of OpenMM may cause trouble with its users [1]. Therefore it has been agreed to withhold the

Processed: openmm: withhold the package until a stable release

Processing control commands: > forwarded -1 https://github.com/openmm/openmm/issues/2784 Bug #966839 [src:openmm] openmm: withhold the package until a stable release Set Bug forwarded-to-address to 'https://github.com/openmm/openmm/issues/2784'. -- 966839:

Bug#957141: dns2tcp: ftbfs with GCC-10

Please find attached patch to fix this issue. -- Antoni Villalonga https://friki.cat/ Description: fixes gcc-10 build issues Author: Antoni Villalonga Last-Update: 2020-08-02 --- a/common/includes/debug.h +++ b/common/includes/debug.h @@ -24,7 +24,7 @@ #include #include -int debug;

Bug#966838: rails: newapp autopkgtest failed and it also broke autopkgtest for many rails assets packages

Package: rails Version: 6.0.3.2+dfsg-4 Severity: serious https://ci.debian.net/data/autopkgtest/testing/arm64/r/ruby-rails-assets-autosize/6520761/log.gz (same error in rails as well other autopkgtest failures) run bundle install --local

Bug#957360: insighttoolkit4: ftbfs with GCC-10

Étienne Mollier, on 2020-08-02 20:25:07 +0200: > I will push that change to salsa if I see the build succeed, Arf, no dice, there might be more changes needed, including maybe: * reviewing cmake build dependencies metainformations, as in the upstream commit documented in a previous entry,

<    1   2   3   4