Processed: r-cran-av: broken symlink /usr/lib/R/site-library/av/samples/Synapsis-Wonderland.mp3

2020-05-18 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:r-cran-av Bug #960998 [r-cran-av] r-cran-av: broken symlink /usr/lib/R/site-library/av/samples/Synapsis-Wonderland.mp3 Added indication that 960998 affects src:r-cran-av -- 960998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960998 Debian Bug

Bug#960998: r-cran-av: broken symlink /usr/lib/R/site-library/av/samples/Synapsis-Wonderland.mp3

2020-05-18 Thread Adrian Bunk
Package: r-cran-av Version: 0.5.0+dfsg-2 Severity: serious Control: affects -1 src:r-cran-av The autopkgtest fails: https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-av/4902405/log.gz This is due to: /usr/lib/R/site-library/av/samples/Synapsis-Wonderland.mp3: broken symbolic link to

Bug#959636: marked as done (zope.i18nmessageid: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py))

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 23:24:34 + with message-id and subject line Bug#959636: fixed in zope.i18nmessageid 5.0.1-1 has caused the Debian Bug report #959636, regarding zope.i18nmessageid: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-pac

Processed: severity of 960871 is important

2020-05-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 960871 important Bug #960871 [src:linux] linux-image-amd64: iwlwifi: iwl_mvm_enable_txq NULL pointer dereference, address: 0068 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if

Bug#960819: squid command failure without systemd

2020-05-18 Thread Sergio Durigan Junior
On Monday, May 18 2020, I wrote: > Just a few more details I've been able to gather this afternoon. > > I'm using a Debian sid VM where I installed sysvinit to replace systemd. > I wasn't able to reproduce the problem reported above, even after > activating the apparmor profile before upgrading. >

Processed: Re: Bug#960819: squid command failure without systemd

2020-05-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #960819 [squid] squid command failure without systemd Added tag(s) moreinfo. -- 960819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#960819: squid command failure without systemd

2020-05-18 Thread Sergio Durigan Junior
Control: tags -1 + moreinfo On Monday, May 18 2020, I wrote: > On Monday, May 18 2020, I wrote: > >> On Sunday, May 17 2020, Amos Jeffries wrote: >> >>> Since the /run/squid directory now depends on systemd squid.service file >>> for existence the 'squid' binary cannot be run. >>> >>> This breaks

Bug#960820: marked as done (openmolcas FTBFS: LAPACK+BLAS sources not available)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 20:34:53 + with message-id and subject line Bug#960820: fixed in openmolcas 19.11-5 has caused the Debian Bug report #960820, regarding openmolcas FTBFS: LAPACK+BLAS sources not available to be marked as done. This means that you claim that the problem has

Bug#960965: kazoo: autopkgtest regression: kazoo.handlers.threading.KazooTimeoutError: Connection time-out

2020-05-18 Thread Paul Gevers
Source: kazoo Version: 2.7.0-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of kazoo the autopkgtest of kazoo fails in testing when that autopkgtest is run with the binary packages of kazo

Bug#960962: src:r-cran-roxygen2: fails to migrate to testing for too long: not installable on armel

2020-05-18 Thread Paul Gevers
Source: r-cran-roxygen2 Version: 7.0.2-1 Severity: serious Control: close -1 7.1.0-2 Tags: sid bullseye 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 testing an

Bug#960963: dovecot: CVE-2020-10957 CVE-2020-10958 CVE-2020-10967

2020-05-18 Thread Salvatore Bonaccorso
Source: dovecot Version: 1:2.3.7.2-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1:2.3.4.1-5+deb10u1 Control: found -1 1:2.3.2-1 Hi, The following vulnerabilities were published for dovecot. CVE-2020-10957[0]: | In Dovecot before 2.3.10.1, unauthen

Processed: src:r-cran-roxygen2: fails to migrate to testing for too long: not installable on armel

2020-05-18 Thread Debian Bug Tracking System
Processing control commands: > close -1 7.1.0-2 Bug #960962 [src:r-cran-roxygen2] src:r-cran-roxygen2: fails to migrate to testing for too long: not installable on armel Marked as fixed in versions r-cran-roxygen2/7.1.0-2. Bug #960962 [src:r-cran-roxygen2] src:r-cran-roxygen2: fails to migrate to

Processed: dovecot: CVE-2020-10957 CVE-2020-10958 CVE-2020-10967

2020-05-18 Thread Debian Bug Tracking System
Processing control commands: > found -1 1:2.3.4.1-5+deb10u1 Bug #960963 [src:dovecot] dovecot: CVE-2020-10957 CVE-2020-10958 CVE-2020-10967 Marked as found in versions dovecot/1:2.3.4.1-5+deb10u1. > found -1 1:2.3.2-1 Bug #960963 [src:dovecot] dovecot: CVE-2020-10957 CVE-2020-10958 CVE-2020-10967

Bug#960371: fhist FTBFS with bison 3.6.1

2020-05-18 Thread Andreas Beckmann
Followup-For: Bug #960371 Control: tag -1 patch Hi, since I had to fix the same bug in libexplain, I'm quickly did a patch for fhist as well. Andreas diff -Nru fhist-1.18/debian/changelog fhist-1.18/debian/changelog --- fhist-1.18/debian/changelog 2015-07-01 09:41:29.0 +0200 +++ fhist-1

Processed: Re: fhist FTBFS with bison 3.6.1

2020-05-18 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #960371 [src:fhist] fhist FTBFS with bison 3.6.1 Added tag(s) patch. -- 960371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#959236: Scripterrors in ifenslave

2020-05-18 Thread Dirk Jost
Hi, I would like to second that priority grave, bonding is right now not working at all. I found several issues with the script: 1. add_master() {     # Return if $IFACE is already a bonding interface.     [ -f "/sys/class/net/$IFACE/bonding/slaves" ] && return     ip link add d

Bug#960958: src:diploma: fails to migrate to testing for too long: maintainer built arch:all

2020-05-18 Thread Paul Gevers
Source: diploma Version: 1.2.14 Severity: serious Control: close -1 1.2.15 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 testing and

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

2020-05-18 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.2.15 Bug #960958 [src:diploma] src:diploma: fails to migrate to testing for too long: maintainer built arch:all Marked as fixed in versions diploma/1.2.15. Bug #960958 [src:diploma] src:diploma: fails to migrate to testing for too long: maintainer built

Bug#960799: marked as done (pyferret: autopkgtest failure: undefined symbol: byteout_)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 17:49:54 + with message-id and subject line Bug#960799: fixed in pyferret 7.6.0~beta-2 has caused the Debian Bug report #960799, regarding pyferret: autopkgtest failure: undefined symbol: byteout_ to be marked as done. This means that you claim that the pro

Processed: [bts-link] source package src:json-c

2020-05-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:json-c > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Sett

Bug#952285: marked as done (prometheus-mongodb-exporter: FTBFS: src/github.com/dcu/mongodb_exporter/mongodb_exporter.go:84:13: undefined: prometheus.Handler)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 17:35:52 + with message-id and subject line Bug#952285: fixed in prometheus-mongodb-exporter 1.0.0+git20180522.e755a44-2 has caused the Debian Bug report #952285, regarding prometheus-mongodb-exporter: FTBFS: src/github.com/dcu/mongodb_exporter/mongodb_exp

Processed: [bts-link] source package src:linkchecker

2020-05-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:linkchecker > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#959856: terminator: ships /usr/share/icons/hicolor/icon-theme.cache

2020-05-18 Thread Adrian Vondendriesch
tags 959856 + patch thanks Am 06.05.20 um 10:45 schrieb Andreas Beckmann: > Package: terminator > Version: 1.92-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package has a file conflict > on /usr/share/icons/

Processed: Re: terminator: ships /usr/share/icons/hicolor/icon-theme.cache

2020-05-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 959856 + patch Bug #959856 [terminator] terminator: ships /usr/share/icons/hicolor/icon-theme.cache Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 959856: https://bugs.debian.org/cgi-bin

Bug#960819: squid command failure without systemd

2020-05-18 Thread Sergio Durigan Junior
On Sunday, May 17 2020, Amos Jeffries wrote: > 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 com

Bug#960819: squid command failure without systemd

2020-05-18 Thread Sergio Durigan Junior
On Monday, May 18 2020, I wrote: > On Sunday, May 17 2020, Amos Jeffries wrote: > >> 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 script

Bug#960410: marked as done (libexplain FTBFS with bison 3.6.1)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 14:48:34 + with message-id and subject line Bug#960410: fixed in libexplain 1.4.D001-10 has caused the Debian Bug report #960410, regarding libexplain FTBFS with bison 3.6.1 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#952326: marked as done (libcrcutil: FTBFS: dh_installdocs: error: Cannot find (any matches for) "doc/text/crc.pdf" (tried in ., debian/tmp))

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 14:33:34 + with message-id and subject line Bug#952326: fixed in libcrcutil 1.0-5.2 has caused the Debian Bug report #952326, regarding libcrcutil: FTBFS: dh_installdocs: error: Cannot find (any matches for) "doc/text/crc.pdf" (tried in ., debian/tmp) to be

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

2020-05-18 Thread Adrian Bunk
On Sun, May 17, 2020 at 04:59:12PM +1000, Dmitry Smirnov wrote: > On Sunday, 17 May 2020 3:30:46 PM AEST Adrian Bunk wrote: > > 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. > > Thank you for prepari

Processed: Re: golang-github-prometheus-client-golang: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/prometheus/client_golang/api github.com/prometheus/cli

2020-05-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 954534 + patch upstream fixed-upstream Bug #954534 [src:golang-github-prometheus-client-golang] golang-github-prometheus-client-golang: FTBFS: dh_auto_test failed Added tag(s) upstream, patch, and fixed-upstream. > thanks Stopping processing

Bug#954534: golang-github-prometheus-client-golang: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/prometheus/client_golang/api github.com/prometheus/client

2020-05-18 Thread Adrian Vondendriesch
tags 954534 + patch upstream fixed-upstream thanks This error appears within the testsuite. It's specific to golang 1.14+ and is already known and fixed upstream [1] in version v1.6.0. Attached you will find a patch for version v1.2.1 (currently in debian). While the attached patch will fix thi

Bug#939058: subnetcalc update

2020-05-18 Thread Thomas Dreibholz
Hi, the bug is fixed in the updated version of the subnetcalc package, which is on the Mentors server at: https://mentors.debian.net/package/subnetcalc . It needs a Debian sponsor for uploading. -- Best regards / Mit freundlichen Grüßen / Med vennlig hilsen =

Bug#960866: libnewlib-nano FTBFS with meson 0.54.2-1

2020-05-18 Thread Keith Packard
Adrian Bunk writes: > Source: libnewlib-nano > Version: 2.11.2-1 > Severity: serious > Tags: ftbfs bullseye sid > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libnewlib-nano.html The correct fix is to get picolibc out of the new queue so I can finish removing this package

Bug#951023: marked as done (rainloop: build-dependency on node-jquery not satisfiable)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 10:35:11 + with message-id and subject line Bug#951023: fixed in rainloop 1.14.0-1 has caused the Debian Bug report #951023, regarding rainloop: build-dependency on node-jquery not satisfiable to be marked as done. This means that you claim that the problem

Bug#960872: nmudiff

2020-05-18 Thread Nicolas Boulenguez
Package: gtkgl2 Control: tags -1 pending Dear maintainer, I've prepared an NMU for gtkgl2 (versioned as 2.1.0-0.3) fixing this bug. The diff with 2.1.0-0.1 is attached. I have uploaded it to DELAYED/15. Feel free to tell me if I should cancel this upload. Regards. diff --git a/debian/changelog b

Processed: nmudiff

2020-05-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #960872 [src:gtkgl2] gtkgl2: autopkgtest failure: cc: not found Added tag(s) pending. -- 960872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#960913: gcc-10: FTBFS with build-indep (Architecture: all only): /<>/build/./gcc/xgcc: No such file or directory

2020-05-18 Thread Simon McVittie
Control: severity -1 important Control: found -1 10-20200425-1 Control: retitle -1 gcc-10: intermittently FTBFS with build-indep: /<>/build/./gcc/xgcc: No such file or directory On Mon, 18 May 2020 at 11:08:36 +0200, Matthias Klose wrote: > I don't think this is an issue in the package. > > http

Processed: Re: Bug#960913: gcc-10: FTBFS with build-indep (Architecture: all only): /<>/build/./gcc/xgcc: No such file or directory

2020-05-18 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #960913 [src:gcc-10] gcc-10: FTBFS with build-indep (Architecture: all only): /<>/build/./gcc/xgcc: No such file or directory Severity set to 'important' from 'serious' > found -1 10-20200425-1 Bug #960913 [src:gcc-10] gcc-10: FTBFS with bu

Bug#960913: gcc-10: FTBFS with build-indep (Architecture: all only): /<>/build/./gcc/xgcc: No such file or directory

2020-05-18 Thread Matthias Klose
On 5/18/20 9:59 AM, Simon McVittie wrote: > Source: gcc-10 > Version: 10.1.0-2 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > I'm not sure exactly what is going on here, but in gcc-10_10.1.0-2 > building the Architecture: all

Bug#950129: marked as done (pyside2 ftbfs in unstable)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 08:49:30 + with message-id and subject line Bug#950129: fixed in pyside2 5.13.2-3 has caused the Debian Bug report #950129, regarding pyside2 ftbfs in unstable to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#950127: marked as done (pyside2 fails all autopkg tests)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 08:49:30 + with message-id and subject line Bug#950127: fixed in pyside2 5.13.2-3 has caused the Debian Bug report #950127, regarding pyside2 fails all autopkg tests to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#960354: ytcc: diff for NMU version 1.8.1-1.1

2020-05-18 Thread Frédéric Bonnard
Hi Boyuan, thanks for the NMU, no problem with the delay. There's a new upstream release, but I won't package it right away. So all good! F. May 17, 2020 5:48 PM, "Boyuan Yang" wrote: > Control: tags 960354 + patch > Control: tags 960354 + pending > > Dear maintainer, > > I've prepared an NMU

Bug#958840: marked as done (kmer: autopkgtest regression: No module named 'localAlignerInterface')

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 08:19:39 + with message-id and subject line Bug#958840: fixed in kmer 0~20150903+r2013-8 has caused the Debian Bug report #958840, regarding kmer: autopkgtest regression: No module named 'localAlignerInterface' to be marked as done. This means that you clai

Bug#954689: marked as done (ocsinventory-server: FTBFS: Error: Too many arguments.)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 08:20:13 + with message-id and subject line Bug#954689: fixed in ocsinventory-server 2.5+dfsg1-1.1 has caused the Debian Bug report #954689, regarding ocsinventory-server: FTBFS: Error: Too many arguments. to be marked as done. This means that you claim tha

Bug#958840: kmer: autopkgtest regression: No module named 'localAlignerInterface'

2020-05-18 Thread Andreas Tille
Hi Nilesh, thanks for the quick check. Given that I experienced some false positives in the past I just uploaded and we'll see what ci.debian.org will say. Kind regards Andreas. On Mon, May 18, 2020 at 01:05:16PM +0530, Nilesh Patra wrote: > On Mon, 18 May 2020 at 12:39, Andreas Tille w

Bug#960913: gcc-10: FTBFS with build-indep (Architecture: all only): /<>/build/./gcc/xgcc: No such file or directory

2020-05-18 Thread Simon McVittie
Source: gcc-10 Version: 10.1.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) I'm not sure exactly what is going on here, but in gcc-10_10.1.0-2 building the Architecture: all packages on the buildds, the stage2 build seems to have fa

Processed: closing 954690

2020-05-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 954690 2.8.4-2 Bug #954690 [src:udisks2] udisks2: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Marked as fixed in versions udisks2/2.8.4-2. Bug #954690 [src:udisks2] udisks2: FTBFS: dh_auto_test: error: make -j4

Bug#954690: closing 954690

2020-05-18 Thread Laurent Bigonville
close 954690 2.8.4-2 thanks Hey, This has been fixed in the last upload: [ Philip Withnall ] * Backport patch from upstream to fix encoding issue with GLib 2.63

Processed: ceres-solver FTBFS on arm64/ppc64el: evaluation_callback_test (Failed)

2020-05-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 902150 Bug #902150 {Done: Philipp Huebner } [src:ceres-solver] ceres-solver FTBFS on arm64/ppc64el: evaluation_callback_test (Failed) Unarchived Bug 902150 > reopen 902150 Bug #902150 {Done: Philipp Huebner } [src:ceres-solver] ceres-s

Bug#960826: marked as done (libquazip FTBFS on 32bit: symbol difference)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 07:33:47 + with message-id and subject line Bug#960826: fixed in libquazip 0.9-2 has caused the Debian Bug report #960826, regarding libquazip FTBFS on 32bit: symbol difference to be marked as done. This means that you claim that the problem has been dealt

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

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 09:23:34 +0200 with message-id and subject line Fwd: 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

Processed: Fwd:

2020-05-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 960703 1:2.0.3-3 Bug #960703 {Done: José Luis Blanco-Claraco } [src:mrpt] mrpt: FTBFS on amd64: test failures Marked as fixed in versions mrpt/1:2.0.3-3. > End of message, stopping processing here. Please contact me if you need assistance.

Bug#958840: kmer: autopkgtest regression: No module named 'localAlignerInterface'

2020-05-18 Thread Nilesh Patra
On Mon, 18 May 2020 at 12:39, Andreas Tille wrote: > > I've merged this and tried a test build including running autopkgtest in > my pbuilder environment. Unfortunately the latter test is now failing with > > ... > autopkgtest [06:48:10]: test atac-unit-test: [--- > Rewriting

Bug#960403: marked as done (libatlas-ecmwf-dev: metview searches for library in /usr/lib/lib/)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 10:21:15 +0300 with message-id <20200518072115.GA27296@localhost> and subject line Fixed in 0.20.2-2 has caused the Debian Bug report #960403, regarding libatlas-ecmwf-dev: metview searches for library in /usr/lib/lib/ to be marked as done. This means that you c

Bug#958840: kmer: autopkgtest regression: No module named 'localAlignerInterface'

2020-05-18 Thread Andreas Tille
On Mon, May 18, 2020 at 01:27:52AM +, Antoni Villalonga wrote: > For some reason I din't included all my previous work on my merge request. I suspect this "some reason" was that salsa and other infrastructure of Debian went offline at that day for several hours. > I've recovered most of it f