Bug#963833: dh_auto_build: libglib update breaks build (GParameters)

2020-06-27 Thread Joshua Peisach
Package: cjs Version: 4.4.0-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Building on: Ubuntu Focal 20.04. Also applies on unstable branch 20.10 Groovy It looks like there is a new update in libglib2.0, or a new update that

Bug#963721: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

2020-06-27 Thread Michael Biebl
Am 27.06.20 um 21:14 schrieb Michael Biebl: > [16014.637459] traps: firewalld[35622] general protection fault > ip:7f981342d7b2 sp:7ffe6abe4ed0 error:0 in > libjansson.so.4.11.1[7f981342c000+8000] Attached is a back trace. Starting program: /usr/bin/python3 /usr/sbin/firewalld --nofork [Thread

Bug#963389: marked as done (ixo-usb-jtag: FTBFS: make[2]: sdcclib: No such file or directory)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 23:49:03 + with message-id and subject line Bug#963389: fixed in ixo-usb-jtag 0.0.1-2 has caused the Debian Bug report #963389, regarding ixo-usb-jtag: FTBFS: make[2]: sdcclib: No such file or directory to be marked as done. This means that you claim that

Bug#963821: marked as done (dpkg-source error on repacked tarballs initially signed by upstream signing key)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 23:48:29 + with message-id and subject line Bug#963821: fixed in dpkg 1.20.2 has caused the Debian Bug report #963821, regarding dpkg-source error on repacked tarballs initially signed by upstream signing key to be marked as done. This means that you

Bug#963348: marked as done (hdmi2usb-fx2-firmware: FTBFS: /bin/bash: sdcclib: command not found)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 23:48:58 + with message-id and subject line Bug#963348: fixed in hdmi2usb-fx2-firmware 0.0.0~git20151225-3 has caused the Debian Bug report #963348, regarding hdmi2usb-fx2-firmware: FTBFS: /bin/bash: sdcclib: command not found to be marked as done. This

Bug#963367: marked as done (simutrans-pak128.britain: FTBFS: /bin/sh: 1: /usr/lib/simutrans/makeobj: not found)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 22:49:26 + with message-id and subject line Bug#963367: fixed in simutrans-pak128.britain 1.18-2 has caused the Debian Bug report #963367, regarding simutrans-pak128.britain: FTBFS: /bin/sh: 1: /usr/lib/simutrans/makeobj: not found to be marked as done.

Processed: Bug#963821 in package dpkg marked as pending

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > tag 963821 pending Bug #963821 [src:dpkg] dpkg-source error on repacked tarballs initially signed by upstream signing key Added tag(s) pending. -- 963821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963821 Debian Bug Tracking System Contact

Bug#963821: in package dpkg marked as pending

2020-06-27 Thread Guillem Jover
Control: tag 963821 pending Hi! Bug #963821 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=66a820033 --- commit

Bug#963460: marked as done (simutrans-pak64: FTBFS: /bin/bash: /usr/lib/simutrans/makeobj: No such file or directory)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 22:33:53 + with message-id and subject line Bug#963460: fixed in simutrans-pak64 121.0-1 has caused the Debian Bug report #963460, regarding simutrans-pak64: FTBFS: /bin/bash: /usr/lib/simutrans/makeobj: No such file or directory to be marked as done.

Processed: Bug#963367 marked as pending in simutrans-pak128.britain

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963367 [src:simutrans-pak128.britain] simutrans-pak128.britain: FTBFS: /bin/sh: 1: /usr/lib/simutrans/makeobj: not found Added tag(s) pending. -- 963367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963367 Debian Bug Tracking System

Bug#963367: marked as pending in simutrans-pak128.britain

2020-06-27 Thread Markus Koschany
Control: tag -1 pending Hello, Bug #963367 in simutrans-pak128.britain 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#963460 marked as pending in simutrans-pak64

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963460 [src:simutrans-pak64] simutrans-pak64: FTBFS: /bin/bash: /usr/lib/simutrans/makeobj: No such file or directory Added tag(s) pending. -- 963460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963460 Debian Bug Tracking System Contact

Bug#963460: marked as pending in simutrans-pak64

2020-06-27 Thread Markus Koschany
Control: tag -1 pending Hello, Bug #963460 in simutrans-pak64 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:

Bug#963628: [Pkg-javascript-devel] Bug#963628: Bug#963628: Node-jest fails with: Error: Cannot find module 'import-local'

2020-06-27 Thread Nilesh Patra
Also, as I dug in a bit, the "import-local" module has this description: """ Let a globally installed package use a locally installed version of itself if available For our use-case we would need modules only from /usr/share/* right? So _maybe_ this has no real use here? Let me know if this

Bug#947542: xiphos: switch from gnome-doc-utils to yelp

2020-06-27 Thread Bastian Germann
The current xiphos upstream version switched to yelp. I created a merge request with all necessary changes to import it: https://salsa.debian.org/pkg-crosswire-team/xiphos/-/merge_requests/4

Bug#963628: [Pkg-javascript-devel] Bug#963628: Bug#963628: Node-jest fails with: Error: Cannot find module 'import-local'

2020-06-27 Thread Nilesh Patra
On Sun, 28 Jun 2020, 02:45 Xavier, wrote: > Control: severity -i grave > Thanks. > Le 24/06/2020 à 21:18, Nilesh Patra a écrit : > > Package: node-jest > > Severity: serious > > > > Dear Maintainer, > > > > Node-jest fails with the following on all the node-modules I've tried > yet. > >

Bug#963628: [Pkg-javascript-devel] Bug#963628: Node-jest fails with: Error: Cannot find module 'import-local'

2020-06-27 Thread Xavier
Control: severity -i grave Le 24/06/2020 à 21:18, Nilesh Patra a écrit : > Package: node-jest > Severity: serious > > Dear Maintainer, > > Node-jest fails with the following on all the node-modules I've tried yet. > Sample examples on Work needed for node-jest: * add babel-plugin-istanbul;

Bug#963821: dpkg-source error on repacked tarballs initially signed by upstream signing key

2020-06-27 Thread Otto Kekäläinen
Hello! I can verify that this bug was introduced today and among others my Salsa-CI builds started failing due to this. Example log: https://salsa.debian.org/mariadb-team/mariadb-10.4/-/jobs/827756 I've CC'd a couple more Salsa-CI devs who might want to confirm if this affects all Salsa-CI

Bug#963822: numpy breaks scikit-learn autopkgtest: test_set_estimator_none[drop] fails

2020-06-27 Thread Paul Gevers
Source: numpy, scikit-learn Control: found -1 numpy/1:1.19.0-1 Control: found -1 scikit-learn/0.22.2.post1+dfsg-7 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload

Processed: numpy breaks scikit-learn autopkgtest: test_set_estimator_none[drop] fails

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > found -1 numpy/1:1.19.0-1 Bug #963822 [src:numpy, src:scikit-learn] numpy breaks scikit-learn autopkgtest: test_set_estimator_none[drop] fails Marked as found in versions numpy/1:1.19.0-1. > found -1 scikit-learn/0.22.2.post1+dfsg-7 Bug #963822 [src:numpy,

Processed: numpy breaks python-xarray autopkgtest: test_use_cftime_standard_calendar_default_in_range[gregorian] fails

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > found -1 numpy/1:1.19.0-1 Bug #963820 [src:numpy, src:python-xarray] numpy breaks python-xarray autopkgtest: test_use_cftime_standard_calendar_default_in_range[gregorian] fails Marked as found in versions numpy/1:1.19.0-1. > found -1 python-xarray/0.15.1-3 Bug

Bug#963821: dpkg-source error on repacked tarballs initially signed by upstream signing key

2020-06-27 Thread Vasyl Gello
Package: src:dpkg Version: 1.20.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear colleagues, Today the dpkg was upgraded from 1.19.7 to 1.20.1 and I noticed that packages started failing to build. For example, the package with

Bug#963820: numpy breaks python-xarray autopkgtest: test_use_cftime_standard_calendar_default_in_range[gregorian] fails

2020-06-27 Thread Paul Gevers
Source: numpy, python-xarray Control: found -1 numpy/1:1.19.0-1 Control: found -1 python-xarray/0.15.1-3 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of numpy

Processed: numpy breaks python-fabio autopkgtest: fabio.test.codecs.test_brukerimage.TestBrukerLinear fails

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > found -1 numpy/1:1.19.0-1 Bug #963818 [src:numpy, src:python-fabio] numpy breaks python-fabio autopkgtest: fabio.test.codecs.test_brukerimage.TestBrukerLinear fails Marked as found in versions numpy/1:1.19.0-1. > found -1 python-fabio/0.10.2+dfsg-1 Bug #963818

Processed: numpy breaks pandas autopkgtest: TypeError: Cannot interpret 'CategoricalDtype(categories=None, ordered=None)' as a data type

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > found -1 numpy/1:1.19.0-1 Bug #963817 [src:numpy, src:pandas] numpy breaks pandas autopkgtest: TypeError: Cannot interpret 'CategoricalDtype(categories=None, ordered=None)' as a data type Marked as found in versions numpy/1:1.19.0-1. > found -1

Bug#963817: numpy breaks pandas autopkgtest: TypeError: Cannot interpret 'CategoricalDtype(categories=None, ordered=None)' as a data type

2020-06-27 Thread Paul Gevers
Source: numpy, pandas Control: found -1 numpy/1:1.19.0-1 Control: found -1 pandas/0.25.3+dfsg2-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of numpy the

Bug#963818: numpy breaks python-fabio autopkgtest: fabio.test.codecs.test_brukerimage.TestBrukerLinear fails

2020-06-27 Thread Paul Gevers
Source: numpy, python-fabio Control: found -1 numpy/1:1.19.0-1 Control: found -1 python-fabio/0.10.2+dfsg-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of

Bug#963816: numpy breaks astropy autopkgtest: TestFitscheck.test_overwrite_invalid fails

2020-06-27 Thread Paul Gevers
Source: numpy, astropy Control: found -1 numpy/1:1.19.0-1 Control: found -1 astropy/4.0.1+post1-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of numpy the

Processed: numpy breaks astropy autopkgtest: TestFitscheck.test_overwrite_invalid fails

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > found -1 numpy/1:1.19.0-1 Bug #963816 [src:numpy, src:astropy] numpy breaks astropy autopkgtest: TestFitscheck.test_overwrite_invalid fails Marked as found in versions numpy/1:1.19.0-1. > found -1 astropy/4.0.1+post1-2 Bug #963816 [src:numpy, src:astropy] numpy

Bug#963814: linux-image-5.6.0-0.bpo.2-amd64: Graphical glitches and some system crashes after upgrade

2020-06-27 Thread Diogo
Package: src:linux Version: 5.6.14-2~bpo10+1 Severity: critical Justification: breaks the whole system Dear Maintainer, * What led up to the situation? Kernel upgrade * What exactly did you do (or not do) that was effective (or ineffective)? Downgrade to 5.5 version of the kernel is

Processed: src:edict: fails to migrate to testing for too long: maintainer built arch:all

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > close -1 2020.04.28-1 Bug #963812 [src:edict] src:edict: fails to migrate to testing for too long: maintainer built arch:all Marked as fixed in versions edict/2020.04.28-1. Bug #963812 [src:edict] src:edict: fails to migrate to testing for too long: maintainer

Bug#963812: src:edict: fails to migrate to testing for too long: maintainer built arch:all

2020-06-27 Thread Paul Gevers
Source: edict Version: 2019.02.20-1 Severity: serious Control: close -1 2020.04.28-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between

Bug#962827: marked as done (libphp-phpmailer: CVE-2020-13625)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 19:34:23 + with message-id and subject line Bug#962827: fixed in libphp-phpmailer 6.1.6-1 has caused the Debian Bug report #962827, regarding libphp-phpmailer: CVE-2020-13625 to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > affects -1 firewalld Bug #963721 [libmount1] libmount1 pulls in libssl 1.1 and breaks software statically linked against libcrypto 1.0 Added indication that 963721 affects firewalld -- 963721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963721 Debian Bug

Bug#963721: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

2020-06-27 Thread Michael Biebl
Control: affects -1 firewalld On Sat, 27 Jun 2020 19:46:57 +0200 Guilhem Moulin wrote: > Control: reassign -1 libmount1 > Control: found -1 2.35.2-6 > Control: retitle -1 libmount1 pulls in libssl 1.1 and breaks software > statically linked against libcrypto 1.0 > > On Sat, 27 Jun 2020 at

Bug#963808: ruby-sanitize: CVE-2020-4054: HTML sanitization bypass in Sanitize

2020-06-27 Thread Salvatore Bonaccorso
Source: ruby-sanitize Version: 4.6.6-2 Severity: grave Tags: security upstream Justification: user security hole Hi, The following vulnerability was published for ruby-sanitize. CVE-2020-4054[0]: | In Sanitize (RubyGem sanitize) greater than or equal to 3.0.0 and less | than 5.2.1, there is a

Processed: php-horde: CVE-2020-8035

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > found -1 5.2.20+debian0-1+deb10u1 Bug #963809 [src:php-horde] php-horde: CVE-2020-8035 Marked as found in versions php-horde/5.2.20+debian0-1+deb10u1. > found -1 5.2.13+debian0-1+deb9u1 Bug #963809 [src:php-horde] php-horde: CVE-2020-8035 Marked as found in versions

Bug#963809: php-horde: CVE-2020-8035

2020-06-27 Thread Salvatore Bonaccorso
Source: php-horde Version: 5.2.21+debian1-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 5.2.20+debian0-1+deb10u1 Control: found -1 5.2.13+debian0-1+deb9u1 Hi, The following vulnerability was published for php-horde. CVE-2020-8035[0]: | The image

Bug#963709: pyside2: FTBFS on arm64: web_engine_initialize test fails with "Could not initialize GLX"

2020-06-27 Thread Dmitry Shachnev
On Fri, Jun 26, 2020 at 09:30:14PM +0300, Dmitry Shachnev wrote: > Some more information on this: it looks like dlopen'ing libGLX_mesa.so.0 > returns NULL (src/GLX/libglxmapping.c:430). > > LD_PRELOAD'ing that library helps. Adding the following two lines to top > of web_engine_initialize.py also

Bug#963774: mcl breaks roary autopkgtest: Cannot find the mcxdeblast executable, please ensure its in your PATH

2020-06-27 Thread hello
Hello Andreas, That's very strange. I will see if I can reproduce this from what you've said and find a solution to it tomorrow. Kind regards, Shayan Doust Original message From: Andreas Tille Date: 27/06/2020 07:11 (GMT+00:00) To: Paul Gevers , 963...@bugs.debian.org,

Processed: fixing pyside2 bugs metadata

2020-06-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # 950129 is fixed in sid > fixed 950129 5.15.0-1 Bug #950129 {Done: Kurt Kremitzki } [src:pyside2] pyside2 ftbfs in unstable Marked as fixed in versions pyside2/5.15.0-1. > # but 963709 affects sid > tags 963709 + sid bullseye Bug #963709

Processed: Re: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libmount1 Bug #963721 [libcryptsetup12] libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow Bug reassigned from package 'libcryptsetup12' to 'libmount1'. No longer marked as found in versions cryptsetup/2:2.3.3-1. Ignoring request to alter

Bug#963721: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

2020-06-27 Thread Guilhem Moulin
Control: reassign -1 libmount1 Control: found -1 2.35.2-6 Control: retitle -1 libmount1 pulls in libssl 1.1 and breaks software statically linked against libcrypto 1.0 On Sat, 27 Jun 2020 at 01:08:49 -0400, Christian Weeks wrote: >> Unless there is a reproducer involving a targeted

Processed: tagging 963035

2020-06-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963035#32 > tags 963035 + patch Bug #963035 [src:chromium] ffmpeg: 4.3 breaks chromium Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#963712: marked as done (haskell-aeson: FTBFS ON armel, armhf, i386, s390x)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 15:21:11 + with message-id and subject line Bug#963712: fixed in haskell-aeson 1.4.7.1-2 has caused the Debian Bug report #963712, regarding haskell-aeson: FTBFS ON armel, armhf, i386, s390x to be marked as done. This means that you claim that the problem

Bug#962913: marked as done (haskell-http-conduit: FTBFS on IPv6-only host)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 15:04:53 + with message-id and subject line Bug#962913: fixed in haskell-http-client 0.6.4.1-2 has caused the Debian Bug report #962913, regarding haskell-http-conduit: FTBFS on IPv6-only host to be marked as done. This means that you claim that the

Processed: reassign 962913 to haskell-http-client, affects 962913

2020-06-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 962913 haskell-http-client 0.6.4.1-1 Bug #962913 [src:haskell-http-conduit] haskell-http-conduit: FTBFS on IPv6-only host Bug reassigned from package 'src:haskell-http-conduit' to 'haskell-http-client'. No longer marked as found in

Bug#962865: marked as done (sympy: FTBFS: python: No such file or directory)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 13:49:50 + with message-id and subject line Bug#952251: fixed in sympy 1.6-4 has caused the Debian Bug report #952251, regarding sympy: FTBFS: python: No such file or directory to be marked as done. This means that you claim that the problem has been dealt

Bug#963036: marked as done (sympy breaks octave-symbolic autopkgtest: AttributeError: module 'sympy.core.compatibility' has no attribute 'integer_types')

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 13:49:50 + with message-id and subject line Bug#963036: fixed in sympy 1.6-4 has caused the Debian Bug report #963036, regarding sympy breaks octave-symbolic autopkgtest: AttributeError: module 'sympy.core.compatibility' has no attribute 'integer_types' to

Bug#952251: marked as done (sympy: FTBFS: make[2]: python: Command not found)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 13:49:50 + with message-id and subject line Bug#952251: fixed in sympy 1.6-4 has caused the Debian Bug report #952251, regarding sympy: FTBFS: make[2]: python: Command not found to be marked as done. This means that you claim that the problem has been

Processed: Retitling #963709

2020-06-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # retitling the bug since pyside2 now built fine on all other architectures > # (not filing a new bug because this one already contains some debugging > information). > retitle 963709 pyside2: FTBFS on arm64: web_engine_initialize test fails

Processed: Re: Bug#947051: latencytop: Non-sensical source format and version

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #947051 [src:latencytop] latencytop: Non-sensical source format and version Severity set to 'serious' from 'important' -- 947051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947051 Debian Bug Tracking System Contact

Bug#963798: srt: Documentation is not installed into libsrt-doc and causes FTBFS if pbuilder is used

2020-06-27 Thread Vasyl Gello
Source: srt Version: 1.4.1-5 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) Dear colleagues, Doing a no-change rebuild of srt for buster-backports/amd64, I noticed that 'gbp buildpackage' fails on 'dh clean --with sphinxdoc':

Bug#948407: marked as done ([calamares] FTBFS with boost1.71)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 14:35:03 +0200 with message-id <0d8da839-b8b9-f426-5ab5-294b3710b...@debian.org> and subject line Closing has caused the Debian Bug report #948407, regarding [calamares] FTBFS with boost1.71 to be marked as done. This means that you claim that the problem has

Bug#963211: marked as done (libmu-dbm6: Tries to overwrite `libmu_dbm.so.6.0.0` from `libmailutils6`)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 12:35:20 + with message-id and subject line Bug#963211: fixed in mailutils 1:3.9-3.1 has caused the Debian Bug report #963211, regarding libmu-dbm6: Tries to overwrite `libmu_dbm.so.6.0.0` from `libmailutils6` to be marked as done. This means that you

Bug#963783: marked as done (dependency problems prevent configuration of libgnutls-dane0:)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 12:35:20 + with message-id and subject line Bug#963211: fixed in mailutils 1:3.9-3.1 has caused the Debian Bug report #963211, regarding dependency problems prevent configuration of libgnutls-dane0: to be marked as done. This means that you claim that the

Bug#963211: mailutils: diff for NMU version 1:3.9-3.1

2020-06-27 Thread Andreas Metzler
Hello Jordi, find attached the diff for the 1:3.9-3.1 NMU. kind regards Andreas diff -Nru mailutils-3.9/debian/changelog mailutils-3.9/debian/changelog --- mailutils-3.9/debian/changelog 2020-06-22 21:09:21.0 +0200 +++ mailutils-3.9/debian/changelog 2020-06-27 13:59:09.0 +0200

Bug#963211: Still occurs in 1:3.9-3

2020-06-27 Thread Andreas Metzler
On 2020-06-27 Andreas Metzler wrote: > On 2020-06-25 Jordi Mallach wrote: > > Hi, I'm away for the week so I'd welcome a nmu. I assume this just > > needs further bumping the breaks/replaces to - 3~, but have no means > > to test. > I will probably have time for this in afternoon. [x]

Processed: bug 961811 is forwarded to https://github.com/baresip/baresip/pull/793

2020-06-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 961811 https://github.com/baresip/baresip/pull/793 Bug #961811 [src:baresip] baresip FTBFS with make 4.3 Set Bug forwarded-to-address to 'https://github.com/baresip/baresip/pull/793'. > thanks Stopping processing here. Please contact

Bug#963715: marked as done (rsyslog: imuxsock overrides /dev/log from journald)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 11:49:42 + with message-id and subject line Bug#963715: fixed in rsyslog 8.2006.0-2 has caused the Debian Bug report #963715, regarding rsyslog: imuxsock overrides /dev/log from journald to be marked as done. This means that you claim that the problem has

Bug#963294: cmake-format: FTBFS: ./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

2020-06-27 Thread Gianfranco Costamagna
> > if you rebuild locally after the first build, the counter increases > > to 60%. > > Which choice becomes 60%? pybuild, and I suspect it increases because of the .egg-info directory. > > cmake plugin has (the number is the extra score): > > OPTIONAL_FILES = {'cmake_uninstall.cmake':

Bug#963715: marked as pending in rsyslog

2020-06-27 Thread Michael Biebl
Control: tag -1 pending Hello, Bug #963715 in rsyslog 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#963715 marked as pending in rsyslog

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963715 [rsyslog] rsyslog: imuxsock overrides /dev/log from journald Added tag(s) pending. -- 963715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#963795: r-cran-httr: autopkgtest regression

2020-06-27 Thread Graham Inggs
Source: r-cran-httr Version: 1.4.1-2 Severity: serious Tags: bullseye sid X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Recently, r-cran-httr started to fail its own autopkgtests [1]. I've copied what I hope is the relevant part of

Bug#963294: cmake-format: FTBFS: ./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

2020-06-27 Thread Ian Campbell
On Sat, 2020-06-27 at 12:54 +0200, Gianfranco Costamagna wrote: > Hello Ian, > > > It seems like pybuild has some heuristics for picking the build > plugin > > to use, for me (and buildd) it selects plugin_distutils.py but for > you > > it is selecting plugin_cmake.py. I can't see why. If you

Bug#963294: cmake-format: FTBFS: ./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

2020-06-27 Thread Gianfranco Costamagna
Hello Ian, > It seems like pybuild has some heuristics for picking the build plugin > to use, for me (and buildd) it selects plugin_distutils.py but for you > it is selecting plugin_cmake.py. I can't see why. If you somehow had a > `CMakeCache.txt` in the package directory that might explain it,

Bug#963682: marked as done (booth: build-depends on removed package.)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 10:33:40 + with message-id and subject line Bug#963682: fixed in booth 1.0-205-gc9e90fe-1 has caused the Debian Bug report #963682, regarding booth: build-depends on removed package. to be marked as done. This means that you claim that the problem has been

Bug#960717: marked as done (openbox-menu: autopkgtest failure: openbox-menu: command not found)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 10:04:18 + with message-id and subject line Bug#960717: fixed in openbox-menu 0.8.0+hg20161009-1.1 has caused the Debian Bug report #960717, regarding openbox-menu: autopkgtest failure: openbox-menu: command not found to be marked as done. This means that

Bug#963339: marked as pending in nova

2020-06-27 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #963339 in nova 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#963339 marked as pending in nova

2020-06-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963339 [src:nova] nova: FTBFS: ValueError: Sentinels must not start with _ Added tag(s) pending. -- 963339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#962176: marked as done (numba: fails autopktest with numpy 1.18)

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 09:03:44 + with message-id and subject line Bug#962176: fixed in numba 0.50.1-1exp1 has caused the Debian Bug report #962176, regarding numba: fails autopktest with numpy 1.18 to be marked as done. This means that you claim that the problem has been dealt

Bug#963294: marked as done (cmake-format: FTBFS: ./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')

2020-06-27 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jun 2020 07:33:28 + with message-id and subject line Bug#963294: fixed in cmake-format 0.6.10-3 has caused the Debian Bug report #963294, regarding cmake-format: FTBFS:

Bug#963774: mcl breaks roary autopkgtest: Cannot find the mcxdeblast executable, please ensure its in your PATH

2020-06-27 Thread Andreas Tille
Hi Shayan, it seems make is not traversing src/alien/oxygen to install the said tool (and the other one mclblastline) as well as its manpages. I created the debdiff with the version in testing: $ debdiff mcl_1%3a14-137+ds-4_amd64.deb mcl_1%3a14-137+ds-7_amd64.deb [The following lists of