Bug#960828: eclipse-jdt-debug binary upload rejected

Source: eclipse-jdt-debug Version: 4.15-1 Severity: serious Tags: ftbfs bunk@coccia:~$ cat /srv/ftp-master.debian.org/queue/reject/eclipse-jdt-debug_4.15-1_all.changes.reason Version check failed: Your upload included the binary package libeclipse-jdt-debug-ui-java, version 3.10.300+eclipse4.12

Bug#960827: nomad FTBFS: cannot find package "github.com/docker/docker/rootless"

Source: nomad Version: 0.10.5+dfsg1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nomad.html ... cd _build && go install -trimpath -v -p 15 -a -tags "release ui nonvidia" github.com/hashicorp/nomad github.com/hashicorp/nomad/acl githu

Processed: tagging 839022

Processing commands for cont...@bugs.debian.org: > tags 839022 + ftbfs Bug #839022 [libgraphics-colornames-perl] libgraphics-colornames-perl: Build-Depends on perl-modules-5.22 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 839022: https://bu

Bug#960746: marked as done (python-pybedtools: binary-all FTBFS)

Your message dated Sun, 17 May 2020 06:18:49 + with message-id and subject line Bug#960746: fixed in python-pybedtools 0.8.0-5 has caused the Debian Bug report #960746, regarding python-pybedtools: binary-all FTBFS to be marked as done. This means that you claim that the problem has been deal

Bug#960826: libquazip FTBFS on 32bit: symbol difference

Source: libquazip Version: 0.9-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=libquazip&suite=sid ... dpkg-gensymbols -plibquazip5-1 -Idebian/libquazip5-1.symbols -Pdebian/libquazip5-1 -edebian/libquazip5-1/usr/lib/i386-linux-gnu/libquazip5.so.1.0.0 dpkg-

Bug#960820: openmolcas FTBFS: LAPACK+BLAS sources not available

Source: openmolcas Version: 19.11-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=openmolcas ... Configuring with MPI parallellization: -- Found MPI_C: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so (found version "3.1") -- Found MPI_Fortran: /usr/lib/x86_64-linu

Bug#952326: libcrcutil: diff for NMU version 1.0-5.2

Control: tags 952326 + patch Control: tags 952326 + pending Dear maintainer, I've prepared an NMU for libcrcutil (versioned as 1.0-5.2) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru libcrcutil-1.0/debian/changelog libcrcutil-1.0/debian/cha

Processed: libcrcutil: diff for NMU version 1.0-5.2

Processing control commands: > tags 952326 + patch Bug #952326 [src:libcrcutil] libcrcutil: FTBFS: dh_installdocs: error: Cannot find (any matches for) "doc/text/crc.pdf" (tried in ., debian/tmp) Added tag(s) patch. > tags 952326 + pending Bug #952326 [src:libcrcutil] libcrcutil: FTBFS: dh_instal

Bug#960819: squid command failure without systemd

Package: squid Version: 4.11-5 Severity: grave Since the /run/squid directory now depends on systemd squid.service file for existence the 'squid' binary cannot be run. This breaks all non-systemd init systems, multi-tenant installations, and scripts running the squid binary for control commands.

Bug#948256: marked as done (FTBFS: test failures)

Your message dated Sun, 17 May 2020 05:13:31 + with message-id and subject line Bug#960794: Removed package(s) from unstable has caused the Debian Bug report #948256, regarding FTBFS: test failures to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#933126: marked as done (license-reconcile: No upstream maintainer ⇒ unsuitable for Bullseye)

Your message dated Sun, 17 May 2020 05:13:31 + with message-id and subject line Bug#960794: Removed package(s) from unstable has caused the Debian Bug report #933126, regarding license-reconcile: No upstream maintainer ⇒ unsuitable for Bullseye to be marked as done. This means that you claim

Bug#948549: marked as done (pgadmin3: Segfault in query tool)

Your message dated Sun, 17 May 2020 05:09:48 + with message-id and subject line Bug#960690: Removed package(s) from unstable has caused the Debian Bug report #948549, regarding pgadmin3: Segfault in query tool to be marked as done. This means that you claim that the problem has been dealt wit

Bug#937400: marked as done (pycaml: Python2 removal in sid/bullseye)

Your message dated Sun, 17 May 2020 05:08:22 + with message-id and subject line Bug#960687: Removed package(s) from unstable has caused the Debian Bug report #937400, regarding pycaml: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been de

Bug#960127: marked as done (Tk::Error: Can't locate object method "resolve_names" via package "App::ClusterSSH::Window")

Your message dated Sun, 17 May 2020 05:03:44 + with message-id and subject line Bug#960127: fixed in clusterssh 4.14-2 has caused the Debian Bug report #960127, regarding Tk::Error: Can't locate object method "resolve_names" via package "App::ClusterSSH::Window" to be marked as done. This me

Bug#956933: marked as done (tpm2-tools: Invalid Maintainer Email Address)

Your message dated Sun, 17 May 2020 04:18:34 + with message-id and subject line Bug#956933: fixed in tpm2-tools 4.2-3 has caused the Debian Bug report #956933, regarding tpm2-tools: Invalid Maintainer Email Address to be marked as done. This means that you claim that the problem has been deal

Bug#960328: marked as done (tpm2-pkcs11: autopkgtest failure)

Your message dated Sun, 17 May 2020 04:03:41 + with message-id and subject line Bug#960328: fixed in tpm2-pkcs11 1.2.0-1 has caused the Debian Bug report #960328, regarding tpm2-pkcs11: autopkgtest failure to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#944616: marked as done (emacs: FTBFS on mips64el, mipsel)

Your message dated Sun, 17 May 2020 01:18:30 + with message-id and subject line Bug#944616: fixed in emacs 1:26.3+1-2 has caused the Debian Bug report #944616, regarding emacs: FTBFS on mips64el, mipsel to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#960810: marked as done (procps: tools always report versions "UNKNOWN")

Your message dated Sun, 17 May 2020 00:18:40 + with message-id and subject line Bug#960810: fixed in procps 2:3.3.16-5 has caused the Debian Bug report #960810, regarding procps: tools always report versions "UNKNOWN" to be marked as done. This means that you claim that the problem has been d

Bug#952291: marked as done (prometheus-mysqld-exporter: FTBFS: src/github.com/prometheus/mysqld_exporter/mysqld_exporter.go:227:31: undefined: prometheus.InstrumentHandlerFunc)

Your message dated Sat, 16 May 2020 23:48:52 + with message-id and subject line Bug#952291: fixed in prometheus-mysqld-exporter 0.12.1+ds-1 has caused the Debian Bug report #952291, regarding prometheus-mysqld-exporter: FTBFS: src/github.com/prometheus/mysqld_exporter/mysqld_exporter.go:227:3

Bug#953040: marked as done (prometheus-mysqld-exporter: Regression on configuration disallows proper use of mysql auth_socket authentication)

Your message dated Sat, 16 May 2020 23:48:52 + with message-id and subject line Bug#953040: fixed in prometheus-mysqld-exporter 0.12.1+ds-1 has caused the Debian Bug report #953040, regarding prometheus-mysqld-exporter: Regression on configuration disallows proper use of mysql auth_socket aut

Processed: Bug#953040 marked as pending in prometheus-mysqld-exporter

Processing control commands: > tag -1 pending Bug #953040 [prometheus-mysqld-exporter] prometheus-mysqld-exporter: Regression on configuration disallows proper use of mysql auth_socket authentication Added tag(s) pending. -- 953040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953040 Debia

Bug#952291: marked as pending in prometheus-mysqld-exporter

Control: tag -1 pending Hello, Bug #952291 in prometheus-mysqld-exporter 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/go-team/packages/prometheus-mysqld-expo

Processed: Bug#952291 marked as pending in prometheus-mysqld-exporter

Processing control commands: > tag -1 pending Bug #952291 [src:prometheus-mysqld-exporter] prometheus-mysqld-exporter: FTBFS: src/github.com/prometheus/mysqld_exporter/mysqld_exporter.go:227:31: undefined: prometheus.InstrumentHandlerFunc Added tag(s) pending. -- 952291: https://bugs.debian.or

Bug#953040: marked as pending in prometheus-mysqld-exporter

Control: tag -1 pending Hello, Bug #953040 in prometheus-mysqld-exporter 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/go-team/packages/prometheus-mysqld-expo

Bug#960810: procps: tools always report versions "UNKNOWN"

Package: procps Version: 2:3.3.15-2 Severity: grave Hello, i just noticed that procps tools are reporting an incorrect version: # free -V free from procps-ng UNKNOWN # ps -V ps from procps-ng UNKNOWN Could you please address this? it's preventing the build of python-psutil, as they are trying to

Bug#960792: marked as done (Accounting is totally wrong when socket_reuse is active)

Your message dated Sat, 16 May 2020 20:51:09 + with message-id and subject line Bug#960792: fixed in policyd-rate-limit 1.0.1.1-1 has caused the Debian Bug report #960792, regarding Accounting is totally wrong when socket_reuse is active to be marked as done. This means that you claim that th

Bug#960786: phpize7.4 also hardcodes incorrect absolute path to sed if built on /usr-merged system

Setting ac_cv_path_SED=/bin/sed in the environment of the configure call might even be easier and less invasive. YMMV, //mirabilos -- Thorsten Glaser (Gründungsmitglied) Teckids e.V. — Digitale Freiheit mit Jugend und Bildung https://www.teckids.org/

Bug#960792: marked as pending in policyd-rate-limit

Control: tag -1 pending Hello, Bug #960792 in policyd-rate-limit 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/python-team/applications/policyd-rate-limit/-/c

Processed: Bug#960792 marked as pending in policyd-rate-limit

Processing control commands: > tag -1 pending Bug #960792 [policyd-rate-limit] Accounting is totally wrong when socket_reuse is active Added tag(s) pending. -- 960792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#947124: marked as done (apache-log4j1.2: CVE-2019-17571)

Your message dated Sat, 16 May 2020 20:21:38 + with message-id and subject line Bug#947124: fixed in apache-log4j1.2 1.2.17-8+deb10u1 has caused the Debian Bug report #947124, regarding apache-log4j1.2: CVE-2019-17571 to be marked as done. This means that you claim that the problem has been d

Bug#960718: marked as done (slirp4netns: autopkgtest failure: 5/7 tests)

Your message dated Sat, 16 May 2020 19:34:51 + with message-id and subject line Bug#960718: fixed in slirp4netns 1.0.1-1 has caused the Debian Bug report #960718, regarding slirp4netns: autopkgtest failure: 5/7 tests to be marked as done. This means that you claim that the problem has been de

Bug#945467: Fix available (fwd)

Hi Jeremy, please make sure to inject pristine-tar (according to Debian Science policy). I did so now. Unfortunately the package does not build in a pbuilder chroot: ... dh_sip3 make[1]: Leaving directory '/build/veusz-3.2.1' dh_install -O--buildsystem=pybuild dh_install: warning: Cannot fin

Bug#960799: pyferret: autopkgtest failure: undefined symbol: byteout_

Source: pyferret Version: 7.6.0~beta-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), With a recent upload of pyferret you added an autopkgtest, great. However, it fails. I copied some of the output at the bot

Bug#960745: marked as done (lammps: FTBFS in bullseye and sid)

Your message dated Sat, 16 May 2020 19:19:03 + with message-id and subject line Bug#960745: fixed in lammps 20200303+dfsg1-3 has caused the Debian Bug report #960745, regarding lammps: FTBFS in bullseye and sid to be marked as done. This means that you claim that the problem has been dealt wi

Bug#960719: marked as done (python-django-netfields: autopkgtest failure: No module named 'django_netfields')

Your message dated Sat, 16 May 2020 18:35:33 + with message-id and subject line Bug#960719: fixed in python-django-netfields 1.2.2-2 has caused the Debian Bug report #960719, regarding python-django-netfields: autopkgtest failure: No module named 'django_netfields' to be marked as done. This

Bug#933126: license-reconcile: No upstream maintainer ⇒ unsuitable for Bullseye

I've filed a removal bug: https://bugs.debian.org/960794

Bug#960755: marked as done (wrk FTBFS on armel)

Your message dated Sat, 16 May 2020 18:22:16 + with message-id and subject line Bug#960755: fixed in wrk 4.1.0-2 has caused the Debian Bug report #960755, regarding wrk FTBFS on armel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#959547: marked as done (python-django-storages: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)

Your message dated Sat, 16 May 2020 18:21:30 + with message-id and subject line Bug#959547: fixed in python-django-storages 1.9.1-2 has caused the Debian Bug report #959547, regarding python-django-storages: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 re

Processed: Bug#960719 marked as pending in python-django-netfields

Processing control commands: > tag -1 pending Bug #960719 [src:python-django-netfields] python-django-netfields: autopkgtest failure: No module named 'django_netfields' Added tag(s) pending. -- 960719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960719 Debian Bug Tracking System Contact o

Bug#960719: marked as pending in python-django-netfields

Control: tag -1 pending Hello, Bug #960719 in python-django-netfields 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/python-team/modules/python-django-netfield

Bug#960792: Accounting is totally wrong when socket_reuse is active

Le samedi 16 mai 2020 à 19:40:02+0200, Pierre-Elliott Bécue a écrit : > Package: policyd-rate-limit > Version: 1.0.0-1 > Severity: grave > Tags: upstream > Forwarded: https://github.com/nitmir/policyd-rate-limit/issues/13 > > Dear maintainer, > > The accounting in policyd-rate-limit is not workin

Bug#960792: Accounting is totally wrong when socket_reuse is active

Package: policyd-rate-limit Version: 1.0.0-1 Severity: grave Tags: upstream Forwarded: https://github.com/nitmir/policyd-rate-limit/issues/13 Dear maintainer, The accounting in policyd-rate-limit is not working properly and therefore breaking the soft, when socket reutilization is active. Upstre

Bug#960752: FTBFS on arch-all, test-suite failure - conova buildd has broken "localhost"

On 2020-05-16 17:45, Martin Pitt wrote: > Michael Biebl [2020-05-16 12:39 +0200]: > > Source: cockpit > > Version: 219-1 > > Severity: serious > > > > Hi Martin, > > > > looks like the latest release reliably triggers a FTBFS on arch-all: > > > > https://buildd.debian.org/status/logs.php?pkg=coc

Bug#959062: marked as done (python-django-libsass: autopkgtest failure: django.core.exceptions.ImproperlyConfigured)

Your message dated Sat, 16 May 2020 17:04:42 + with message-id and subject line Bug#959062: fixed in python-django-libsass 0.8-2 has caused the Debian Bug report #959062, regarding python-django-libsass: autopkgtest failure: django.core.exceptions.ImproperlyConfigured to be marked as done. T

Processed: bug 960127 is forwarded to https://github.com/duncs/clusterssh/issues/123, tagging 960127

Processing commands for cont...@bugs.debian.org: > forwarded 960127 https://github.com/duncs/clusterssh/issues/123 Bug #960127 [clusterssh] Tk::Error: Can't locate object method "resolve_names" via package "App::ClusterSSH::Window" Set Bug forwarded-to-address to 'https://github.com/duncs/cluste

Processed: your mail

Processing commands for cont...@bugs.debian.org: > unarchive 913620 Bug #913620 {Done: Ondřej Surý } [php7.3-dev] phpize7.3 hardcodes incorrect absolute path to sed if built on /usr-merged system Unarchived Bug 913620 > clone 913620 -1 Bug #913620 {Done: Ondřej Surý } [php7.3-dev] phpize7.3 hard

Bug#960752: FTBFS on arch-all, test-suite failure - conova buildd has broken "localhost"

Michael Biebl [2020-05-16 12:39 +0200]: > Source: cockpit > Version: 219-1 > Severity: serious > > Hi Martin, > > looks like the latest release reliably triggers a FTBFS on arch-all: > > https://buildd.debian.org/status/logs.php?pkg=cockpit&ver=219-1&arch=all > > The relevant part from the buil

Processed: libpsl: diff for NMU version 0.21.0-1.1

Processing control commands: > tags 953287 + patch Bug #953287 [src:libpsl] libpsl: binary-all FTBFS Bug #954501 [src:libpsl] publicsuffix: FTBFS: build-dependency not installable: psl-make-dafsa Ignoring request to alter tags of bug #953287 to the same tags previously set Ignoring request to alt

Processed: libpsl: diff for NMU version 0.21.0-1.1

Processing control commands: > tags 953287 + patch Bug #953287 [src:libpsl] libpsl: binary-all FTBFS Bug #954501 [src:libpsl] publicsuffix: FTBFS: build-dependency not installable: psl-make-dafsa Added tag(s) patch. Added tag(s) patch. > tags 953287 + pending Bug #953287 [src:libpsl] libpsl: bina

Bug#953287: libpsl: diff for NMU version 0.21.0-1.1

Control: tags 953287 + patch Control: tags 953287 + pending Control: tags 955439 + pending Dear maintainer, I've prepared an NMU for libpsl (versioned as 0.21.0-1.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru libpsl-0.21.0/debian/change

Processed: espresso 6.5 builds on armhf

Processing commands for cont...@bugs.debian.org: > tags 946915 fixed-upstream Bug #946915 [src:espresso] espresso FTBFS on archs where it build in the past Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 946915: https://bugs.debian.org

Bug#953970: marked as done (python-boto: autopkgtest failure with Python 3.8 as default)

Your message dated Sat, 16 May 2020 15:08:19 + with message-id and subject line Bug#953970: fixed in python-boto 2.49.0-3 has caused the Debian Bug report #953970, regarding python-boto: autopkgtest failure with Python 3.8 as default to be marked as done. This means that you claim that the pr

Bug#960726: firefox: connection failure to most https websites

Control: severity -1 important Control: retitle -1 firefox: connection failure to most https websites with https proxy auto-config and security.OCSP.require set to true I've found the cause. To reproduce the problem: 1. Start Firefox with a new profile (via "firefox -P"). 2. In Preferences → Ge

Processed: Re: firefox: connection failure to most https websites

Processing control commands: > severity -1 important Bug #960726 [firefox] firefox: connection failure to most https websites Severity set to 'important' from 'grave' > retitle -1 firefox: connection failure to most https websites with https > proxy auto-config and security.OCSP.require set to tr

Bug#960759: marked as done (golang-1.14: FTBFS on mipsel)

Your message dated Sat, 16 May 2020 14:35:08 + with message-id and subject line Bug#960759: fixed in golang-1.14 1.14.3-2 has caused the Debian Bug report #960759, regarding golang-1.14: FTBFS on mipsel to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#960251: marked as done (eq10q FTBFS with lv2-dev 1.18.0-1)

Your message dated Sat, 16 May 2020 14:33:57 + with message-id and subject line Bug#960251: fixed in eq10q 2.2~repack0-4 has caused the Debian Bug report #960251, regarding eq10q FTBFS with lv2-dev 1.18.0-1 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#960757: marked as done (allelecount: binary-any FTBFS)

Your message dated Sat, 16 May 2020 14:33:53 + with message-id and subject line Bug#960757: fixed in allelecount 4.1.0-3 has caused the Debian Bug report #960757, regarding allelecount: binary-any FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If t

Processed: Bug#960759 marked as pending in golang

Processing control commands: > tag -1 pending Bug #960759 [src:golang-1.14] golang-1.14: FTBFS on mipsel Added tag(s) pending. -- 960759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#960759: marked as pending in golang

Control: tag -1 pending Hello, Bug #960759 in golang 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/go-team/compiler/golang/-/commit/92d04159722e103b672d760f98

Processed: Bug#960251 marked as pending in eq10q

Processing control commands: > tag -1 pending Bug #960251 [src:eq10q] eq10q FTBFS with lv2-dev 1.18.0-1 Added tag(s) pending. -- 960251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#960251: marked as pending in eq10q

Control: tag -1 pending Hello, Bug #960251 in eq10q 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/multimedia-team/eq10q/-/commit/ab3fb4f6eda482f9bfa056f77ca30

Bug#960756: python-biopython FTBFS on 32bit: test_NCBI_BLAST_tools.BlastDB failures

Perhaps makeblastdb itself failed (and our wrapper didn't notice)? Those are the first files looked for after calling makeblastdb, to see if it could make a BLAST database. Are there any GenBank/NC_005816.fna.n* or GenBank/NC_005816.faa.p* files present? If it helps, the commands our script was t

Processed: severity of 960775 is important

Processing commands for cont...@bugs.debian.org: > severity 960775 important Bug #960775 [src:golang-github-anacrolix-missinggo] golang-github-anacrolix-missinggo FTBFS on 32bit Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance

Bug#960756: python-biopython FTBFS on 32bit: test_NCBI_BLAST_tools.BlastDB failures

Control: tags -1 upstream Control: forwarded -1 Peter Cock Hi Peter, it seems the patch applied does not work for 32bit architectures. Kind regards Andreas. On Sat, May 16, 2020 at 02:25:20PM +0300, Adrian Bunk wrote: > Source: python-biopython > Version: 1.76+dfsg-2 > Severity: serious

Processed: Re: Bug#960756: python-biopython FTBFS on 32bit: test_NCBI_BLAST_tools.BlastDB failures

Processing control commands: > tags -1 upstream Bug #960756 [src:python-biopython] python-biopython FTBFS on 32bit: test_NCBI_BLAST_tools.BlastDB failures Added tag(s) upstream. > forwarded -1 Peter Cock Bug #960756 [src:python-biopython] python-biopython FTBFS on 32bit: test_NCBI_BLAST_tools.B

Bug#960759: golang-1.14: FTBFS on mipsel

On Sat, May 16, 2020 at 7:51 PM Gianfranco Costamagna wrote: > > Source: golang-1.14 > Version: 1.14.3-1 > Severity: serious > > Hello, looks like golang-1.14 fails to build randomly on mipsel, including > the latest version uploaded in sid. > It's because of #960674. The go compiler is broken o

Bug#960775: golang-github-anacrolix-missinggo FTBFS on 32bit

Source: golang-github-anacrolix-missinggo Version: 2.1.0-4 Severity: serious Tags: ftbfs fixed-upstream patch Forwarded: https://github.com/anacrolix/missinggo/issues/16 https://buildd.debian.org/status/package.php?p=golang-github-anacrolix-missinggo&suite=sid ... # github.com/anacrolix/missinggo

Bug#956903: marked as done (clang-tidy-6.0: Depends on cruft package python-yaml)

Your message dated Sat, 16 May 2020 13:18:55 + with message-id and subject line Bug#956903: fixed in llvm-toolchain-6.0 1:6.0.1-14.1 has caused the Debian Bug report #956903, regarding clang-tidy-6.0: Depends on cruft package python-yaml to be marked as done. This means that you claim that th

Bug#960773: gr-gsm: FTBFS on s390x

Source: gr-gsm Version: 0.42.2.20200214-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) gr-gsm failed to build on s390x: https://buildd.debian.org/status/fetch.php?pkg=gr-gsm&arch=s390x&ver=0.42.2.20200214-1&stamp=1589387991&raw=0 Che

Bug#960774: haskell-pretty-simple FTBFS: test failure

Source: haskell-pretty-simple Version: 2.2.0.1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/haskell-pretty-simple.html ... Running debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct Running 1 test suites... Test suite pretty-

Bug#960769: swt4-gtk FTBFS on 32bit

Source: swt4-gtk Version: 4.15.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=swt4-gtk&suite=sid ... callback.c:697:2: error: initializer element is not constant 697 | (jlong)FN(0, args), \ | ^ ...

Bug#960768: prads: missing build dependency on python3-docutils

Source: prads Version: 0.3.3-1.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=prads&suite=sid ... debian/rules override_dh_auto_install make[1]: Entering directory '/<>' /usr/bin/make PREFIX=/usr CONFDIR=/etc/prads DESTDIR=/<>/debian/prads install make[2]: Ente

Bug#960703: mrpt: FTBFS on amd64: test failures

Thanks for reporting. It has been fixed in version 2:2.0.3-3. Cheers, JL

Bug#960762: libvirt: random (?) test hangs

Source: libvirt Version: 6.0.0-7 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=all&ver=6.0.0-7&stamp=1589452859&raw=0 https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=i386&ver=6.0.0-7&stamp=1589494701&raw=0 ... make check-TESTS make[4]: Ente

Processed: tagging 960752

Processing commands for cont...@bugs.debian.org: > tags 960752 + ftbfs Bug #960752 [src:cockpit] FTBFS on arch-all, test-suite failure Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 960752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960

Bug#960760: tree-puzzle FTBFS on !amd64: test failures

Source: tree-puzzle Version: 5.3~rc16+dfsg-1 Severity: serious Tags: ftbfs Based on the "Important remark" below, test failures shouldn't be fatal. This would also make them not suitable for autopkgtest. https://buildd.debian.org/status/package.php?p=tree-puzzle&suite=sid ... FAIL: qp-hky-rhet-

Bug#960759: golang-1.14: FTBFS on mipsel

Source: golang-1.14 Version: 1.14.3-1 Severity: serious Hello, looks like golang-1.14 fails to build randomly on mipsel, including the latest version uploaded in sid. In Ubuntu we added a patch, increasing the test timeout that made some builds succeed there on slow hardware (such as emulated r

Bug#960758: libcamera FTBFS: missing boost build dependencies

Source: libcamera Version: 0~git20200513+924778e-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=libcamera&suite=sid ... Program openssl found: YES (/usr/bin/openssl) Library atomic found: YES Library dl found: YES Library gnutls found: YES Did not find pkg-config b

Bug#960757: allelecount: binary-any FTBFS

Source: allelecount Version: 4.1.0-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=allelecount&suite=sid ... dh_auto_test --sourcedirectory=perl cd perl && make -j4 test TEST_VERBOSE=1 make[2]: Entering directory '/<>/perl' PERL_DL_NONLAZY=1 "/usr/bin/perl"

Bug#960756: python-biopython FTBFS on 32bit: test_NCBI_BLAST_tools.BlastDB failures

Source: python-biopython Version: 1.76+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=python-biopython&suite=sid ... == FAIL: test_fasta_db_nucl (test_NCBI_BLAST_tools.BlastDB) Test makeblastd

Bug#960755: wrk FTBFS on armel

Source: wrk Version: 4.1.0-1 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/fetch.php?pkg=wrk&arch=armel&ver=4.1.0-1&stamp=1589619501&raw=0 ... /usr/bin/ld: obj/stats.o: in function `stats_record': ./src/stats.c:24: undefined reference to `__atomic_fetch_add_8' /usr/bin/ld:

Bug#960752: FTBFS on arch-all, test-suite failure

Source: cockpit Version: 219-1 Severity: serious Hi Martin, looks like the latest release reliably triggers a FTBFS on arch-all: https://buildd.debian.org/status/logs.php?pkg=cockpit&ver=219-1&arch=all The relevant part from the build log ** cockpit-protocol:ERROR:src/common/test-webserver.c:37

Bug#960327: marked as done (squid: autopkgtest regression: test_daemons (__main__.BasicTest))

Your message dated Sat, 16 May 2020 10:35:24 + with message-id and subject line Bug#960327: fixed in squid 4.11-5 has caused the Debian Bug report #960327, regarding squid: autopkgtest regression: test_daemons (__main__.BasicTest) to be marked as done. This means that you claim that the probl

Bug#953970: Taking over DPMT (Was: python-boto: autopkgtest failure with Python 3.8 as default)

On 5/16/20 11:02 AM, Andreas Tille wrote: > On Mon, May 11, 2020 at 10:20:24PM -0400, Noah Meyerhans wrote: >> Control: tags -1 + patch >> >>> I'll move this package to a cloud-team repository and prepare an upload >>> to unstable on Monday if nobody beats me to it. >> >> https://salsa.debian.org/c

Processed: Re: firefox: connection failure to most https websites

Processing control commands: > found -1 76.0.1-2 Bug #960726 [firefox] firefox: connection failure to most https websites Marked as found in versions firefox/76.0.1-2. -- 960726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960726 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Bug#960726: firefox: connection failure to most https websites

Control: found -1 76.0.1-2 SEC_ERROR_OCSP_SERVER_ERROR still occurs with many hosts. Note: https://support.mozilla.org/ is affected, but https://www.mozilla.org/ is not. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#960327: squid: autopkgtest regression: test_daemons (__main__.BasicTest)

Hi Sergio, > On 14 May 2020, at 05:42, Sergio Durigan Junior wrote: > > Here's a patch that fixes the issue above. > > Please note that even after fixing this specific issue, I still see > another failure with test_zz_apparmor. I've posted a merge request to > also fix this problem here: > >

Bug#960748: node-babel: meta bug to keep out of testing

Package: node-babel Version: 6.26.0+repack-4 Severity: serious Control: block -1 by 960120 Control: block -1 by 959798 Control: block -1 by 960021 src:node-babel (babel 6.x) is replaced by src:node-babel7 (babel 7.x) and src:node-babel should not be part of bullseye. The status of this transit

Processed: node-babel: meta bug to keep out of testing

Processing control commands: > block -1 by 960120 Bug #960748 [node-babel] node-babel: meta bug to keep out of testing 960748 was not blocked by any bugs. 960748 was not blocking any bugs. Added blocking bug(s) of 960748: 960120 > block -1 by 959798 Bug #960748 [node-babel] node-babel: meta bug to

Bug#953970: Taking over DPMT (Was: python-boto: autopkgtest failure with Python 3.8 as default)

On Mon, May 11, 2020 at 10:20:24PM -0400, Noah Meyerhans wrote: > Control: tags -1 + patch > > > I'll move this package to a cloud-team repository and prepare an upload > > to unstable on Monday if nobody beats me to it. > > https://salsa.debian.org/cloud-team/python-boto/-/merge_requests/1 Coul

Bug#960746: python-pybedtools: binary-all FTBFS

Source: python-pybedtools Version: 0.8.0-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=python-pybedtools&arch=all&ver=0.8.0-4&stamp=1589359748&raw=0 ... dh_fixperms chmod -x debian/*/usr/lib/python3/dist-packages/pybedtools/scripts/pybedtools chmod: cannot access

Bug#960703: marked as done (mrpt: FTBFS on amd64: test failures)

Your message dated Sat, 16 May 2020 10:24:53 +0200 with message-id and subject line has caused the Debian Bug report #960703, regarding mrpt: FTBFS on amd64: test failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 960703 2:2.0.3-3 Bug #960703 [src:mrpt] mrpt: FTBFS on amd64: test failures The source 'mrpt' and version '2:2.0.3-3' do not appear to match any binary packages Marked as fixed in versions mrpt/2:2.0.3-3. > End of message, stopping processi

Bug#960701: [Pkg-nagios-devel] Bug#960701: php-icinga: Uncaught ErrorException \Icinga\Web\ViewStream::stream_set_option is not implemented!

On 5/16/20 8:38 AM, Stephane Bortzmeyer wrote: >> You need icingaweb 2.8.0 from experimental for php7.4 support, and you >> need to upgrade all icingaweb2 packages from experimental, not only >> php-icinga. > > Fair enough. But may be php-icinga should depend on icingaweb2 >= 2.8 > in that case, n

Bug#873321: marked as done (wrk FTBFS with luajit 2.1)

Your message dated Sat, 16 May 2020 07:50:18 + with message-id and subject line Bug#873321: fixed in wrk 4.0.2-3 has caused the Debian Bug report #873321, regarding wrk FTBFS with luajit 2.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#874176: marked as done (wrk: Fails to run with 'PANIC: unprotected error in call to Lua API')

Your message dated Sat, 16 May 2020 07:50:18 + with message-id and subject line Bug#874176: fixed in wrk 4.0.2-3 has caused the Debian Bug report #874176, regarding wrk: Fails to run with 'PANIC: unprotected error in call to Lua API' to be marked as done. This means that you claim that the pr

Bug#960745: lammps: FTBFS in bullseye and sid

Source: lammps Version: 20200303+dfsg1-2 Severity: serious Tags: ftbfs bullseye sid Hi Maintainer The recent upload of lammps FTBFS in bullseye and sid [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/un

Bug#958958: btfs: FTBFS on architectures that need -latomic

Control: reassign -1 libtorrent-rasterbar10 1.2.5-1 Control: retitle -1 libtorrent-rasterbar must be linked against libatomic on armel/mipsel/m68k/powerpc/sh4 Control: affects -1 src:btfs On Mon, Apr 27, 2020 at 10:16:59AM +0200, Graham Inggs wrote: >... > I believe the solution is to link agains

Processed: Re: Bug#958958: btfs: FTBFS on architectures that need -latomic

Processing control commands: > reassign -1 libtorrent-rasterbar10 1.2.5-1 Bug #958958 [src:btfs] btfs: FTBFS on architectures that need -latomic Bug reassigned from package 'src:btfs' to 'libtorrent-rasterbar10'. No longer marked as found in versions btfs/2.20-1. Ignoring request to alter fixed ve

Bug#956027: marked as done (libjs-popper.js: Upgrading libjs-popper.js buster -> bullseye results in an empty /usr/share/javascript/popper.js)

Your message dated Sat, 16 May 2020 07:20:43 + with message-id and subject line Bug#956027: fixed in popper.js 1.16.1+ds-1 has caused the Debian Bug report #956027, regarding libjs-popper.js: Upgrading libjs-popper.js buster -> bullseye results in an empty /usr/share/javascript/popper.js to b

  1   2   >