Bug#960421: libpwiz: FTBFS with boost 1.71

2020-06-07 Thread peter green
Some googling lead me to https://svnweb.freebsd.org/ports/head/multimedia/mkvtoolnix/files/patch-boost-1.69?view=markup&pathrev=482787 which suggests it is now necessary to manually convert from tribool to bool by writing bool{value} Unfortunately after doing that I get In file included from

Bug#962176: numba: fails autopktest with numpy 1.18

2020-06-07 Thread Drew Parsons
Source: numba Followup-For: Bug #962176 The upstream patch does not apply cleaning (on its own), doesn't give a clean build that passes all tests. Probably we need to wait for their next release, else pull an entire git snapshot or rc release. But 0.50.0 is already rc, shouldn't be too long befor

Bug#962434: ros-resource-retriever: calls home during build.

2020-06-07 Thread Gianfranco Costamagna
Source: ros-resource-retriever Version: 1.12.6-1 Severity: serious Hello, using internet during build is forbidden by policy, but still allowed in Debian builders. In Ubuntu, where this is more strictly forbidden, the failure seems to indicate that the package is trying to connect to internet d

Bug#962381: marked as done (gqrx-sdr: gqrx segmentation fault at start time in testing)

2020-06-07 Thread Debian Bug Tracking System
Your message dated Sun, 7 Jun 2020 23:26:48 +0200 with message-id <20200607212648.GC17366@sarastro> and subject line has caused the Debian Bug report #962381, regarding gqrx-sdr: gqrx segmentation fault at start time in testing to be marked as done. This means that you claim that the problem has

Processed: your mail

2020-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 962381 2.12.1-1+b2 Bug #962381 {Done: Antonio Radici } [gqrx-sdr] gqrx-sdr: gqrx segmentation fault at start time in testing Did not alter found versions and reopened. > fixed 962381 2.12.1-1+b3 Bug #962381 [gqrx-sdr] gqrx-sdr: gqrx segment

Processed: cupt: diff for NMU version 2.10.4+nmu1

2020-06-07 Thread Debian Bug Tracking System
Processing control commands: > tags 960381 + pending Bug #960381 [src:cupt] cupt: FTBFS with boost 1.71 Added tag(s) pending. -- 960381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#960381: cupt: diff for NMU version 2.10.4+nmu1

2020-06-07 Thread Sebastian Ramacher
Control: tags 960381 + pending Dear maintainer, I've prepared an NMU for cupt (versioned as 2.10.4+nmu1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru cupt-2.10.4/cpp/CMakeLists.txt cupt-2.10.4+nmu1/cpp/CMakeLists.t

Bug#962381: marked as done (gqrx-sdr: gqrx segmentation fault at start time in testing)

2020-06-07 Thread Debian Bug Tracking System
Your message dated Sun, 7 Jun 2020 22:35:48 +0200 with message-id <20200607203548.GA17366@sarastro> and subject line Re: Bug#962381: gqrx-sdr: gqrx segmentation fault at start time in testing has caused the Debian Bug report #962381, regarding gqrx-sdr: gqrx segmentation fault at start time in tes

Bug#962424: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint

2020-06-07 Thread wxcafé
Btw the workaround seems to be to mask zfs-mount-generator (`mkdir /etc/systemd/system-generators/; ln -s /dev/null /etc/systemd/system-generators/zfs-mount-generator`) Cheers -- Clément 'wxcafé' Hertling

Processed: fixed 960321 in 2.2.18-8

2020-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 960321 2.2.18-8 Bug #960321 {Done: Calogero Lo Leggio } [src:burp] burp: flaky arm64 autopkgtest: .../src/test/clientscript failed The source 'burp' and version '2.2.18-8' do not appear to match any binary packages Marked as fixed in versi

Processed: Fixed in 2.3.2

2020-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 962423 fixed-upstream patch Bug #962423 [pglogical] pglogical FTBFS error: static declaration of 'AcquireDeletionLock' follows non-static declaration Added tag(s) fixed-upstream and patch. > forwarded 962423 > https://github.com/2ndQuadrant

Processed: zimlib: diff for NMU version 4.0.4-5.1

2020-06-07 Thread Debian Bug Tracking System
Processing control commands: > tags 960243 + patch Bug #960243 [src:zimlib] zimlib FTBFS with ICU 67.1 Added tag(s) patch. > tags 960243 + pending Bug #960243 [src:zimlib] zimlib FTBFS with ICU 67.1 Added tag(s) pending. -- 960243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960243 Debian

Bug#960243: zimlib: diff for NMU version 4.0.4-5.1

2020-06-07 Thread Sebastian Ramacher
Control: tags 960243 + patch Control: tags 960243 + pending Dear maintainer, I've prepared an NMU for zimlib (versioned as 4.0.4-5.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru zimlib-4.0.4/debian/changelog zimli

Processed: frama-c: FTBFS fixed upstream

2020-06-07 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 > https://lists.gforge.inria.fr/pipermail/frama-c-discuss/2020-June/005823.html Bug #959599 [src:frama-c] frama-c: FTBFS: Error: Unbound value const_of_big_int Set Bug forwarded-to-address to 'https://lists.gforge.inria.fr/pipermail/frama-c-discuss/202

Bug#960321: marked as done (burp: flaky arm64 autopkgtest: .../src/test/clientscript failed)

2020-06-07 Thread Debian Bug Tracking System
Your message dated Sun, 7 Jun 2020 22:17:17 +0200 with message-id <2cbd0459-3373-4c98-b7aa-b4fd4b603...@nerdrug.org> and subject line has caused the Debian Bug report #960321, regarding burp: flaky arm64 autopkgtest: .../src/test/clientscript failed to be marked as done. This means that you claim

Bug#959599: frama-c: FTBFS fixed upstream

2020-06-07 Thread John Scott
Control: forwarded -1 https://lists.gforge.inria.fr/pipermail/frama-c-discuss/2020-June/005823.html Control: tags -1 fixed-upstream > Hello, > > Le jeu. 4 juin 2020 à 18:43, John Scott a écrit : > > I'm not the maintainer, just a prospective user taking a look, but Frama-C > > hasn't been buildi

Bug#960321: burp: flaky arm64 autopkgtest: .../src/test/clientscript failed

2020-06-07 Thread Calogero Lo Leggio
As suggested by upstream developer, I removed superfluous 'slow and intensive' test. The definitive fix is introduced in version 2.2.18-8 References: github issue to upstream dev: https://github.com/grke/burp/issues/866 salsa commit: https://salsa.debian.org/debian/burp/-/commit/f9363a7af36ac72

Bug#962424: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint

2020-06-07 Thread wxcafe
Package: zfsutils-linux Version: 0.8.4-1~bpo10+1 Severity: grave Tags: upstream Justification: renders package unusable Hey The systemd zfs-mount-generator script (/lib/systemd/system-generators/zfs-mount-generator) can break system boot if there are multiple datasets with the same mountpoint, be

Bug#949837: innoextract: diff for NMU version 1.8-1.2

2020-06-07 Thread Sebastian Ramacher
Control: tags 949837 + pending Dear maintainer, I've prepared an NMU for innoextract (versioned as 1.8-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru innoextract-1.8/debian/changelog innoextract-1.8/debian/chang

Processed: innoextract: diff for NMU version 1.8-1.2

2020-06-07 Thread Debian Bug Tracking System
Processing control commands: > tags 949837 + pending Bug #949837 [innoextract] FTBFS with Boost 1.71 Added tag(s) pending. -- 949837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#962423: pglogical FTBFS error: static declaration of 'AcquireDeletionLock' follows non-static declaration

2020-06-07 Thread peter green
Package: pglogical Version: 2.3.1-1 Severity: serious Tags: ftbfs It seems pglogical recently started failing to build. http://buildd.raspbian.org/status/fetch.php?pkg=pglogical&arch=armhf&ver=2.3.1-1%2Bb1&stamp=1591473342 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pglog

Processed: Dupe

2020-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 960877 962092 Bug #960877 [meson] meson 0.54.2-1 breaks bali-phy build Bug #962092 [meson] meson: Link with static lib instead of shared one with boost 1.71 Set Bug forwarded-to-address to 'https://github.com/mesonbuild/meson/issues/7

Bug#962232: vanguards indirectly build-depends on cruft package.

2020-06-07 Thread Scott Kitterman
On Thu, 4 Jun 2020 21:21:53 +0100 peter green wrote: > Package: vanguards > Version: 0.3.1-2 > Severity: serious > > vanguards build-depends on pypy-pytest which depends on pypy-funcsigs which is no longer built by the python-funcsigs source package. The pytest maintainer has also said they wou

Bug#938099: marked as done (python-pysqlite2: Python2 removal in sid/bullseye)

2020-06-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Jun 2020 19:36:37 + with message-id and subject line Bug#962370: Removed package(s) from unstable has caused the Debian Bug report #938099, regarding python-pysqlite2: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem h

Bug#937749: marked as done (python-fcgi: Python2 removal in sid/bullseye)

2020-06-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Jun 2020 19:37:01 + with message-id and subject line Bug#962371: Removed package(s) from unstable has caused the Debian Bug report #937749, regarding python-fcgi: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has be

Bug#960243: zimlib FTBFS with ICU 67.1

2020-06-07 Thread Peter Green
I downloaded the build logs  and filtered them to show the missing symbols that were not already marked as optional. plugwash@thinkpad:~$ wget -O zimlib.log 'https://buildd.debian.org/status/fetch.php?pkg=zimlib&arch=amd64&ver=4.0.4-5%2Bb1&stamp=1591384179&raw=0' plugwash@thinkpad:~$ html2text

Bug#962381: gqrx-sdr: gqrx segmentation fault at start time in testing

2020-06-07 Thread A. Maitland Bottoms
On Sun, 07 Jun 2020 10:36:54 +0200 Antonio Radici wrote: > gqrx does not start in testing, this renders the package unusable. I'm sorry to hear this. I noticed the -b3 version get upgraded today too, but it works for me when I start it (I have a box tracking testing, so no chroot here.) >

Bug#962402: haskell-text-icu: FTBFS on ppc64el and s390x: toEnum{BlockCode}: tag (302) is outside of enumeration's range (0,280)

2020-06-07 Thread Sebastian Ramacher
Source: haskell-text-icu Version: 0.7.0.1-13 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) haskell-text-icu failed to build on ppc64el and s390x: | t_blockCode: [Failed] | *** Failed! (after 25 tests): | Exception: | t

Bug#962190: primer3: please disable Big Endian tests on autopkgtests too

2020-06-07 Thread Adrian Bunk
On Thu, Jun 04, 2020 at 12:47:24PM +0200, Gianfranco Costamagna wrote: > Source: primer3 > Version: 2.4.0-2 > Severity: serious > > Hello, can you please apply the same on autopkgtests? now autopkgtests > failures are considered RC buggy > > something like this might work: >... Running tests is

Processed: found 962205 in 1.2.4-1

2020-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 962205 1.2.4-1 Bug #962205 [buildstream] buildstream: Missing dependency on bubblewrap Marked as found in versions buildstream/1.2.4-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 962205: https://bugs.de

Bug#962399: vmdb2 FTBFS: help2man: can't get `--help' info from vmdb2

2020-06-07 Thread Adrian Bunk
Source: vmdb2 Version: 0.16-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=vmdb2&arch=all&ver=0.16-1&stamp=1591514624&raw=0 ... debian/rules override_dh_installman make[1]: Entering directory '/<>' [ ! -e vmdb2.1 ] help2man -N vmdb2 -i debian/vmdb2.1.in > debian

Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream

2020-06-07 Thread Axel Beckert
Hi, intrigeri wrote: > I did not dare proposing this course of action so far because the > notes from our BoF at DebConf19 are a bit ambiguous about whether we > decided to remove the package from sid, in addition to removing it > from testing. I wasn't at the BoF, but was opposing rather strongl

Processed: found 956285 in 1.1.1-1

2020-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 956285 1.1.1-1 Bug #956285 [libtorrent-rasterbar] Problems identified in debian/copyright There is no source info for the package 'libtorrent-rasterbar' at version '1.1.1-1' with architecture '' Unable to make a source version for version '

Processed: Fixed in 3.10.4

2020-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 959439 https://github.com/supercollider/supercollider/pull/4612 Bug #959439 [supercollider] FTBFS with Boost 1.71 Set Bug forwarded-to-address to 'https://github.com/supercollider/supercollider/pull/4612'. > tags 959439 fixed-upstream B

Processed: Fixed upstream

2020-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 962069 > https://github.com/synfig/synfig/commit/dedb2f7f82a04c0cb3aad462bbe055412f3f5e18 Bug #962069 [src:synfig] synfig: FTBFS with icu 67 Set Bug forwarded-to-address to 'https://github.com/synfig/synfig/commit/dedb2f7f82a04c0cb3aad

Processed: bug 954711 is forwarded to https://git.ircad.fr/sight/sight/-/issues/462

2020-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 954711 https://git.ircad.fr/sight/sight/-/issues/462 Bug #954711 [sight] FTBFS with Boost 1.71 Changed Bug forwarded-to-address to 'https://git.ircad.fr/sight/sight/-/issues/462' from 'Flavien Bridault '. > thanks Stopping processing h

Bug#962390: aoflagger FTBFS with boost 1.71

2020-06-07 Thread Adrian Bunk
Source: aoflagger Version: 2.15.0-1 Severity: serious Tags: ftbfs patch fixed-upstream Forwarded: https://sourceforge.net/p/aoflagger/code/ci/1b8a46d70650bf59320f8a0c9371e619ac40/ Control: block 961995 by -1 After the #960331 fix it failed with: ... -- Found PythonLibs: /usr/lib/x86_64-linux

Processed: aoflagger FTBFS with boost 1.71

2020-06-07 Thread Debian Bug Tracking System
Processing control commands: > block 961995 by -1 Bug #961995 [release.debian.org] transition: boost-defaults 961995 was blocked by: 953873 962070 962173 955581 959480 960416 960414 960422 962251 960385 960500 960427 962253 962286 962252 953871 960421 962288 959479 960331 962086 960381 959573 96

Bug#962368: frogatto-data: Source-only upload not automatically built for non-free packages

2020-06-07 Thread Simon McVittie
On Sat, 06 Jun 2020 at 20:22:28 -0400, Boyuan Yang wrote: > Martin Quinson 于2020年6月6日周六 下午7:11写道: > > In the meanwhile, I'll do a source+binary upload of the package. > > This should fall back to the old behavior and not introduce new > problems. I have no idea if britney would influence testing

Processed: Forwarded

2020-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 960426 https://github.com/svgpp/svgpp/issues/79 Bug #960426 [src:svgpp] svgpp: FTBFS with boost 1.71 Set Bug forwarded-to-address to 'https://github.com/svgpp/svgpp/issues/79'. > thanks Stopping processing here. Please contact me if you

Bug#960426: Forwarded

2020-06-07 Thread Anton Gladky
forwarded 960426 https://github.com/svgpp/svgpp/issues/79 thanks

Bug#934458: linkchecker-gui: Fails to start at all

2020-06-07 Thread Helge Kreutzmann
Hello Paolo, I just saw your message. Please, next time send your reply also to 934458-submit...@bugs.debian.org, because the answer to the bugs are not forwarded to the submitter, unfortunately. I have python-xdg installed, but this does not change anything: ii python-xdg 0.25-5 all

Bug#962381: gqrx-sdr: gqrx segmentation fault at start time in testing

2020-06-07 Thread Antonio Radici
Package: gqrx-sdr Version: 2.12.1-1+b3 Severity: grave Justification: renders package unusable gqrx does not start in testing, this renders the package unusable. The problem is reproducible by spinning up a testing chroot (as of today) and trying to start gqrx This is the stacktrace: *** Thread

Bug#962319: libextutils-hascompiler-perl: test failures perl 5.30.3-2

2020-06-07 Thread Niko Tyni
On Sat, Jun 06, 2020 at 10:28:49AM +0300, Niko Tyni wrote: > Package: libextutils-hascompiler-perl > Version: 0.021-2 > Severity: serious > > This package fails its test suite with perl 5.30.3-2 from unstable. > With perl 5.30.3-2, #798626 is fixed and $Config{useshrplib} now > correctly indicate

Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream

2020-06-07 Thread intrigeri
Hi, gregor herrmann (2020-05-22): > On Fri, 22 May 2020 09:58:12 +0200, intrigeri wrote: > >> So, once aptitude >= 0.8.13-1 has migrated to testing, we'll need to >> ask (presumably the release team) for libparse-debianchangelog-perl to >> lose its "key package" status, so the autoremoval machiner