Bug#950379: marked as done (apertium-es-ast FTBFS with apertium 3.6.1)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Fri, 20 Mar 2020 06:34:53 + with message-id and subject line Bug#950379: fixed in apertium-es-ast 1.1.0~r51165-3 has caused the Debian Bug report #950379, regarding apertium-es-ast FTBFS with apertium 3.6.1 to be marked as done. This means that you claim that the problem ha

Bug#952319: marked as done (hylafax: FTBFS: Incompatible TIFF Library.)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Fri, 20 Mar 2020 01:34:31 + with message-id and subject line Bug#952319: fixed in hylafax 3:6.0.7-1 has caused the Debian Bug report #952319, regarding hylafax: FTBFS: Incompatible TIFF Library. to be marked as done. This means that you claim that the problem has been dealt

Processed: your mail

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 951806 by 953678 Bug #951806 [ruby-serverengine] ruby-serverengine: FTBFS aginst Ruby2.5 and Ruby2.7 951806 was not blocked by any bugs. 951806 was not blocking any bugs. Added blocking bug(s) of 951806: 953678 > retitle 951806 ruby-servere

Processed: block 949187 with 950147 953016

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 949187 with 950147 953016 Bug #949187 [release.debian.org] transition: python3.8 949187 was blocked by: 952601 950221 953969 953966 952610 950847 952217 953940 953549 953550 953316 953968 953970 950861 953967 948416 950210 951944 950842 95

Bug#954236: Proposed Buster Fix (pyhon3-bleach: New secuirty issue: mutation XSS (again))

2020-03-19 Thread Salvatore Bonaccorso
Hi Scott, On Thu, Mar 19, 2020 at 12:20:25AM -0400, Scott Kitterman wrote: > Upstream's 3.1.2 release had just the security fix in it. I propose updating > buster with it (I put 3.1.3 in unstable, but it had non-security fixes in it. > > I'm not 100% sure about if we need to modify the import p

Bug#949419:

2020-03-19 Thread Bdale Garbee
tags 949519 +needhelp thanks I don't have any easy way to debug LDAP issues. If someone else does and wants to chase this down and let me know where the problem is, that'd be great. Bdale signature.asc Description: PGP signature

Processed (with 1 error): your mail

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 949519 +needhelp Unknown tag/s: needhelp. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potat

Bug#954305: python-udatetime: shared library is not properly linked with libm

2020-03-19 Thread Aurelien Jarno
Source: python-udatetime Version: 0.0.16-2 Severity: serious Tags: patch python-udatetime use the pow() math function in src/rfc3339.c, but doesn't link with libm.so. This causes the non-versioned pow symbol to be used, which in turn causes issues when glibc version is upgraded. The attached patc

Bug#954283: marked as done (gzip: produces corrupt output files on armv5tel)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 21:35:00 + with message-id and subject line Bug#954283: fixed in gzip 1.10-2 has caused the Debian Bug report #954283, regarding gzip: produces corrupt output files on armv5tel to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: Bug#954300: lua-cgi: session closing broken on lua5.1

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 954300 important Bug #954300 [lua-cgi] lua-cgi: session closing broken on lua5.1 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 954300: https://bugs.debian.org/

Bug#954303: tika: CVE-2020-1950

2020-03-19 Thread Salvatore Bonaccorso
Source: tika Version: 1.22-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1.20-1 Hi, The following vulnerability was published for tika. CVE-2020-1950[0]: Excessive memory usage (DoS) vulnerability in Apache Tika's PSDParser If you fix the vulnera

Processed: tika: CVE-2020-1950

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > found -1 1.20-1 Bug #954303 [src:tika] tika: CVE-2020-1950 Marked as found in versions tika/1.20-1. -- 954303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tika: CVE-2020-1951

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > found -1 1.20-1 Bug #954302 [src:tika] tika: CVE-2020-1951 Marked as found in versions tika/1.20-1. -- 954302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#954302: tika: CVE-2020-1951

2020-03-19 Thread Salvatore Bonaccorso
Source: tika Version: 1.22-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1.20-1 Hi, The following vulnerability was published for tika. CVE-2020-1951[0]: Infinite Loop (DoS) vulnerability in Apache Tika's PSDParser If you fix the vulnerability ple

Bug#954300: lua-cgi: session closing broken on lua5.1

2020-03-19 Thread Brian May
Package: lua-cgi Version: 5.2~alpha2-1 Severity: serious Justification: renders package useless As far as I can tell - please do say if I am wrong - this package is completely useless with LUA5.1, as packaged. When run with the following code: === cut === session = require("cgilua.session") sess

Bug#950050: marked as done (pytds FTBFS with Python 3.8 as supported version)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 20:54:07 + with message-id and subject line Bug#950050: fixed in pytds 1.10.0-1 has caused the Debian Bug report #950050, regarding pytds FTBFS with Python 3.8 as supported version to be marked as done. This means that you claim that the problem has been de

Bug#936839: marked as done (lepton-eda: Python2 removal in sid/bullseye)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 20:45:28 + with message-id and subject line Bug#936839: fixed in lepton-eda 1.9.10-2 has caused the Debian Bug report #936839, regarding lepton-eda: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been de

Bug#831076: libkqueue: diff for NMU version 2.0.3-1.2

2020-03-19 Thread Sudip Mukherjee
Control: tags 831076 + patch Control: tags 831076 + pending Dear maintainer, I've prepared an NMU for libkqueue (versioned as 2.0.3-1.2) and uploaded it to mentors for sponsoring. Please feel free to tell me if I should remove it. -- Regards Sudip diff -Nru libkqueue-2.0.3/debian/changelog libk

Processed: libkqueue: diff for NMU version 2.0.3-1.2

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > tags 831076 + patch Bug #831076 [src:libkqueue] libkqueue: FTBFS with GCC 6: src/linux/read.c:207:74: error: comparison of constant '0' with boolean expression is always false [-Werror=bool-compare] Added tag(s) patch. > tags 831076 + pending Bug #831076 [src:libkq

Bug#954284: marked as done (puppet broken with ruby 2.7)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 19:35:02 + with message-id and subject line Bug#954284: fixed in puppet 5.5.19-1 has caused the Debian Bug report #954284, regarding puppet broken with ruby 2.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#954291: libvirt-daemon-system-sysv: upgrading kills VMs

2020-03-19 Thread Thorsten Glaser
Dixi quod… > To add insult to injury, it didn’t even shut it down cleanly: > > tglase@tglase:~ $ virsh -c qemu:///system list > Id Name State > > 3MirBSD in shutdown > > > “virsh destroy 3” to the “rescue”… Oh, it gets worse. Trying to restart the VM

Bug#954291: libvirt-daemon-system-sysv: upgrading kills VMs

2020-03-19 Thread Thorsten Glaser
Package: libvirt-daemon-system-sysv Version: 6.0.0-3 Severity: critical Justification: causes serious data loss Just a regular dist-upgrade doing this: Unpacking libvirt-daemon-system-sysv (6.0.0-3) over (6.0.0-1) ... […] Setting up libvirt-daemon-system-sysv (6.0.0-3) ... Restarting libvirt log

Bug#952162: marked as done (golang-github-karlseguin-expect: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/karlseguin/expect github.com/karlseguin/expect/b

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 19:19:58 + with message-id and subject line Bug#952162: fixed in golang-github-karlseguin-expect 1.0.1+git20160716.12.5c2eadb-2 has caused the Debian Bug report #952162, regarding golang-github-karlseguin-expect: FTBFS: dh_auto_test: error: cd obj-x86_64-l

Bug#951979: Anything related to recent patch from Ubuntu?

2020-03-19 Thread Håvard Flaget Aasen
Hi, I looked into it, you are correct, it has everything to do with the patch. Removing 0002-Use-new-CMake-Python-discovery-with-matching-Boost-P.patch fixes the ftbfs. I don't know what changed when cmake upgraded from 3.15.4 -> 3.16.3 I also don't know if this is the best solution, but for now

Bug#952162: marked as pending in golang-github-karlseguin-expect

2020-03-19 Thread Utkarsh Gupta
Control: tag -1 pending Hello, Bug #952162 in golang-github-karlseguin-expect 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/golang-github-ka

Processed: Bug#952162 marked as pending in golang-github-karlseguin-expect

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #952162 [src:golang-github-karlseguin-expect] golang-github-karlseguin-expect: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/karlseguin/expect github.com/karlseguin/expect/build github.com/karlseguin/

Bug#952535: patroni: test failures on arm64 and others

2020-03-19 Thread Michael Banck
Hi, Am Dienstag, den 25.02.2020, 13:53 +0100 schrieb Gianfranco Costamagna: > Source: patroni > Version: 1.6.3-2 > Severity: serious > > Hello, looks like your package depends on etcd, but that package is > not working everywhere (even if built, I'll open an RC > later today) > > Can you please

Processed: tagging 954284

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 954284 + pending Bug #954284 [puppet] puppet broken with ruby 2.7 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 954284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954284 Debian

Bug#954283: gzip: produces corrupt output files on armv5tel

2020-03-19 Thread Bdale Garbee
Jörg Mechnich writes: >> DEB_CPPFLAGS_MAINT_APPEND := -DUNALIGNED_OK That was originally meant to only be enabled on amd64 .. I think that got lost in one of the packaging style updates I accepted a while back. Just uploaded 1.10-2 hopefully making the architecture-specificity true again. Bdal

Bug#954287: libfiu: FTBFS on amd64/unstable: Segmentation fault (core dumped)

2020-03-19 Thread Chris Lamb
Source: libfiu Version: 1.00-6 Severity: serious Justification: fails to build from source X-Debbugs-CC: albert...@blitiri.com.ar Hi, libfiu now fails to build from source in unstable/amd64: […] ./wrap-python 3 ./test-set_prng_seed.py LD_LIBRARY_PATH=../../libfiu/ LD_PRELOAD="../../prelo

Bug#952615: marked as done (hinge: FTBFS: fmt.h:22:10: fatal error: spdlog/fmt/bundled/core.h: No such file or directory)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 17:49:32 + with message-id and subject line Bug#952615: fixed in hinge 0.5.0-6 has caused the Debian Bug report #952615, regarding hinge: FTBFS: fmt.h:22:10: fatal error: spdlog/fmt/bundled/core.h: No such file or directory to be marked as done. This means

Bug#885813: bumping severity of xfce4-notes-plugin's use of libunique to Serious

2020-03-19 Thread Andreas Henriksson
Hi, On Wed, Oct 09, 2019 at 05:34:16PM +0200, Yves-Alexis Perez wrote: > Hi, thanks for the update. It seems that the GTK3 port isn't really complete. > And it seems notes isn't really maintained upstream anymore. I'm adding Mike > to the CC but we might end up completely dropping xfce4-notes-plug

Bug#954284: puppet broken with ruby 2.7

2020-03-19 Thread Laurent Bigonville
severity 954284 serious Thanks On Thu, 19 Mar 2020 17:51:32 +0100 Laurent Bigonville wrote: > Hello, > > With ruby 2.7 upload, when running the puppet cli, I get the following > warning/error: > > /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is obsolete > cannot load s

Processed: Re: puppet broken with ruby 2.7

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 954284 serious Bug #954284 [puppet] puppet broken with ruby 2.7 Severity set to 'serious' from 'grave' > Thanks Stopping processing here. Please contact me if you need assistance. -- 954284: https://bugs.debian.org/cgi-bin/bugreport.cgi

Bug#954284: puppet broken with ruby 2.7

2020-03-19 Thread Laurent Bigonville
Package: puppet Version: 5.5.10-4 Severity: grave Hello, With ruby 2.7 upload, when running the puppet cli, I get the following warning/error: /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is obsolete cannot load such file -- sync puppet returns a non-zero exit code Kind re

Bug#954283: gzip: produces corrupt output files on armv5tel

2020-03-19 Thread Jörg Mechnich
Package: gzip Version: 1.10-1 Severity: critical Justification: causes serious data loss Dear Maintainer, the stock package from testing provides a broken gzip binary which will produce corrupt output that fails CRC checks. Compiling the plain 1.10 sources generates a working gzip binary. The is

Bug#952080: marked as done (ruby-faker: FTBFS: ERROR: Test "ruby2.7" failed.)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 16:36:48 + with message-id and subject line Bug#952080: fixed in ruby-fakefs 0.20.1-2 has caused the Debian Bug report #952080, regarding ruby-faker: FTBFS: ERROR: Test "ruby2.7" failed. to be marked as done. This means that you claim that the problem has b

Processed: Re: hinge: FTBFS: fmt.h:22:10: fatal error: spdlog/fmt/bundled/core.h: No such file or directory

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + patch Bug #952615 [src:hinge] hinge: FTBFS: fmt.h:22:10: fatal error: spdlog/fmt/bundled/core.h: No such file or directory Added tag(s) patch. -- 952615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952615 Debian Bug Tracking System Contact ow...@bug

Bug#952615: hinge: FTBFS: fmt.h:22:10: fatal error: spdlog/fmt/bundled/core.h: No such file or directory

2020-03-19 Thread Gilles Filippini
Control: tag -1 + patch Hi, On Wed, 26 Feb 2020 17:09:48 +0100 Lucas Nussbaum *wrote: > Source: hinge > Version: 0.5.0-5 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200225 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid,

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-19 Thread Steve McIntyre
On Thu, Mar 19, 2020 at 11:16:19AM +, Steve McIntyre wrote: >On Thu, Mar 19, 2020 at 09:26:25AM +0100, Holger Wansing wrote: >>Hi, >> >>Steve McIntyre wrote: >>> One silly question: what media are you using with the Thinkpad? Is it >>> the same USB stick (or whatever) every time? Can you verif

Bug#935042: marked as done (Program phones home by default)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 16:22:22 + with message-id and subject line Bug#935042: fixed in lynis 2.7.5-1 has caused the Debian Bug report #935042, regarding Program phones home by default to be marked as done. This means that you claim that the problem has been dealt with. If this i

Processed: retitle 954236 to python-bleach: CVE-2020-6816: mutation XSS, found 954236 in 3.1.0-1

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 954236 python-bleach: CVE-2020-6816: mutation XSS Bug #954236 {Done: Scott Kitterman } [python3-bleach] python3-bleach: New secuirty issue: mutation XSS (again) Changed Bug title to 'python-bleach: CVE-2020-6816: mutation XSS' from 'pyth

Bug#954238: libperlspeak-perl: CVE-2020-10674

2020-03-19 Thread gregor herrmann
On Thu, 19 Mar 2020 05:53:24 +0100, Salvatore Bonaccorso wrote: > CVE-2020-10674[0]: > | PerlSpeak through 2.01 allows attackers to execute arbitrary OS > | commands, as demonstrated by use of system and 2-argument open. > > Gregor, the module seem to be basically unmaintained, I would propose >

Bug#954278: rust-cookie-factory: autopkgtest failure.

2020-03-19 Thread peter green
Source: rust-cookie-factory Version: 0.3.0-1 Severity: serious error[E0432]: unresolved import `io_compat` --> src/lib.rs:32:21 | 32 | pub use io_compat::*; | ^ help: a similar path exists: `crate::io_compat` | = note: `use` statements

Bug#950378: marked as done (apertium-eo-fr FTBFS with apertium 3.6.1)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 15:20:06 + with message-id and subject line Bug#950378: fixed in apertium-eo-fr 0.9.0~r57551-3 has caused the Debian Bug report #950378, regarding apertium-eo-fr FTBFS with apertium 3.6.1 to be marked as done. This means that you claim that the problem has

Bug#954276: cloud-init - RuntimeError: dictionary keys changed during iteration

2020-03-19 Thread Bastian Blank
Package: cloud-init Version: 20.1-1 Severity: serious cloud-init 20.1-1 fails to provision Azure: | 2020-03-19 14:31:48,840 - util.py[DEBUG]: Running module disk_setup () failed | Traceback (most recent call last): | File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 848, in _run_

Processed: severity of 937643 is normal

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 937643 normal Bug #937643 [src:python-characteristic] python-characteristic: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 937643

Processed (with 1 error): unarchiving 937643

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 937643 Bug #937643 {Done: Dimitri John Ledkov } [src:python-characteristic] python-characteristic: Python2 removal in sid/bullseye Unarchived Bug 937643 > reopen 937643 Bug #937643 {Done: Dimitri John Ledkov } [src:python-characterist

Bug#953942: RM: jack -- RoQA; python2-only; no new upstream code since 2005; better alternatives exist; blocking py2removal effort

2020-03-19 Thread Scott Kitterman
On Thursday, March 19, 2020 7:14:12 AM EDT you wrote: > Package: ftp.debian.org > Followup-For: Bug #953942 > > Wow. Gone in 4 days. > While I can understand that ftpmasters are triggerhappy due to the py2 > removal, that seems excessive. > > As for the "no upstream activity", that tends to happe

Processed: src:sumaclust: fails to migrate to testing for too long

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 1.0.34-1 Bug #954262 [src:sumaclust] src:sumaclust: fails to migrate to testing for too long The source 'sumaclust' and version '1.0.34-1' do not appear to match any binary packages Marked as fixed in versions sumaclust/1.0.34-1. -- 954262: https://bugs.

Bug#954260: src:slurm-llnl: fails to migrate to testing for too long

2020-03-19 Thread Paul Gevers
Source: slurm-llnl Version: 19.05.3.2-2 Severity: serious Control: fixed -1 19.05.5-1 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 a

Processed: src:pyspread: fails to migrate to testing for too long

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 1.99.0.1-2 Bug #954261 [src:pyspread] src:pyspread: fails to migrate to testing for too long Marked as fixed in versions pyspread/1.99.0.1-2. -- 954261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954261 Debian Bug Tracking System Contact ow...@bugs

Bug#954261: src:pyspread: fails to migrate to testing for too long

2020-03-19 Thread Paul Gevers
Source: pyspread Version: 1.99.0.0-2 Severity: serious Control: fixed -1 1.99.0.1-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 and

Processed: src:slurm-llnl: fails to migrate to testing for too long

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 19.05.5-1 Bug #954260 [src:slurm-llnl] src:slurm-llnl: fails to migrate to testing for too long Marked as fixed in versions slurm-llnl/19.05.5-1. -- 954260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954260 Debian Bug Tracking System Contact ow...@

Bug#954262: src:sumaclust: fails to migrate to testing for too long

2020-03-19 Thread Paul Gevers
Source: sumaclust Version: 1.0.31-2 Severity: serious Control: fixed -1 1.0.34-1 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 and un

Processed: src:r-cran-ranger: fails to migrate to testing for too long

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 0.12.1-1 Bug #954258 [src:r-cran-ranger] src:r-cran-ranger: fails to migrate to testing for too long Marked as fixed in versions r-cran-ranger/0.12.1-1. -- 954258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954258 Debian Bug Tracking System Contact

Bug#954259: src:innoextract: fails to migrate to testing for too long

2020-03-19 Thread Paul Gevers
Source: innoextract Version: 1.7-2 Severity: serious Control: fixed -1 1.8-1 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 and unstab

Processed: src:innoextract: fails to migrate to testing for too long

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 1.8-1 Bug #954259 [src:innoextract] src:innoextract: fails to migrate to testing for too long Marked as fixed in versions innoextract/1.8-1. -- 954259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954259 Debian Bug Tracking System Contact ow...@bugs.

Bug#954258: src:r-cran-ranger: fails to migrate to testing for too long

2020-03-19 Thread Paul Gevers
Source: r-cran-ranger Version: 0.11.2-1 Severity: serious Control: fixed -1 0.12.1-1 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

Processed: bug 954257 is forwarded to https://github.com/linux-audit/audit-userspace/issues/120

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 954257 https://github.com/linux-audit/audit-userspace/issues/120 Bug #954257 [python3-audit] python3-audit: SWIG-related type errors render module unusable Set Bug forwarded-to-address to 'https://github.com/linux-audit/audit-userspace

Bug#954257: python3-audit: SWIG-related type errors render module unusable

2020-03-19 Thread Laurent Bigonville
Package: python3-audit Version: 1:2.8.5-2 Severity: grave Control: forward -1 https://github.com/linux-audit/audit-userspace/issues/120 Looks like #927946 is back/was not properly fixed This only affects unstable (and probably bullseye) -- System Information: Debian Release: bullseye/sid APT p

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-19 Thread Steve McIntyre
On Thu, Mar 19, 2020 at 12:42:48PM +0100, Holger Wansing wrote: >Hi, > >Steve McIntyre wrote: >> On Thu, Mar 19, 2020 at 09:26:25AM +0100, Holger Wansing wrote: >> >Hi, >> > >> >Steve McIntyre wrote: >> >> One silly question: what media are you using with the Thinkpad? Is it >> >> the same USB st

Processed: unarchiving 927946

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 927946 Bug #927946 {Done: Laurent Bigonville } [python-audit] python-audit: SWIG-related type errors render module unusable Unarchived Bug 927946 > thanks Stopping processing here. Please contact me if you need assistance. -- 927946:

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-19 Thread Holger Wansing
Hi, Steve McIntyre wrote: > On Thu, Mar 19, 2020 at 09:26:25AM +0100, Holger Wansing wrote: > >Hi, > > > >Steve McIntyre wrote: > >> One silly question: what media are you using with the Thinkpad? Is it > >> the same USB stick (or whatever) every time? Can you verify it's > >> written OK? > > >

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-19 Thread Steve McIntyre
On Thu, Mar 19, 2020 at 09:26:25AM +0100, Holger Wansing wrote: >Hi, > >Steve McIntyre wrote: >> One silly question: what media are you using with the Thinkpad? Is it >> the same USB stick (or whatever) every time? Can you verify it's >> written OK? > >I used the same USB stick for alpha1 and alph

Bug#953942: RM: jack -- RoQA; python2-only; no new upstream code since 2005; better alternatives exist; blocking py2removal effort

2020-03-19 Thread Jan Braun
Package: ftp.debian.org Followup-For: Bug #953942 Wow. Gone in 4 days. While I can understand that ftpmasters are triggerhappy due to the py2 removal, that seems excessive. As for the "no upstream activity", that tends to happen when software is feature-complete. And when claiming "better altern

Processed: bug breaks package entirely

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 954137 grave Bug #954137 [virtualbox] virtualbox: Cannot boot VM: kernel modules fails with VERR_VMM_SMAP_BUT_AC_CLEAR Severity set to 'grave' from 'important' > End of message, stopping processing here. Please contact me if you need as

Processed: block 951663 with 915689 919412 951799

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 951663 with 915689 919412 951799 Bug #951663 [src:rng-tools] src:rng-tools: fails to migrate to testing for too long 951663 was not blocked by any bugs. 951663 was not blocking any bugs. Added blocking bug(s) of 951663: 919412, 951799, and

Processed: block 951689 with 911587

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 951689 with 911587 Bug #951689 [src:infnoise] src:infnoise: fails to migrate to testing for too long 951689 was not blocked by any bugs. 951689 was not blocking any bugs. Added blocking bug(s) of 951689: 911587 > thanks Stopping processing

Bug#954253: python3-pybel: Missing dependency on unpackaged bel_resources

2020-03-19 Thread Adrian Bunk
Package: python3-pybel Version: 0.14.5-1 Severity: serious Control: block 950662 by -1 https://buildd.debian.org/status/fetch.php?pkg=pybel&arch=all&ver=0.14.5-1&stamp=1583338001&raw=0 ... dh_python3 -i -O--buildsystem=pybuild I: dh_python3 pydist:224: Cannot find package that provides bel_reso

Processed: block 951661 with 918674

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 951661 with 918674 Bug #951661 [src:osmo-hlr] src:osmo-hlr: fails to migrate to testing for too long 951661 was not blocked by any bugs. 951661 was not blocking any bugs. Added blocking bug(s) of 951661: 918674 > thanks Stopping processing

Processed: block 951660 with 911983

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 951660 with 911983 Bug #951660 [src:phast] src:phast: fails to migrate to testing for too long 951660 was not blocked by any bugs. 951660 was not blocking any bugs. Added blocking bug(s) of 951660: 911983 > thanks Stopping processing here.

Processed: python3-pybel: Missing dependency on unpackaged bel_resources

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > block 950662 by -1 Bug #950662 {Done: Andreas Tille } [src:pybel] pybel FTBFS: test failures 950662 was not blocked by any bugs. 950662 was not blocking any bugs. Added blocking bug(s) of 950662: 954253 -- 950662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Processed: tagging 949829

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 949829 + fixed Bug #949829 {Done: Emmanuel Arias } [src:pythonmagick] pythonmagick: FTBFS against current libboost-python Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 949829: https://b

Processed: tagging 950983

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 950983 + patch Bug #950983 [src:clickhouse] clickhouse FTBFS in bullseye/sid Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 950983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95098

Processed: tagging 885143, reassign 878777 to src:noweb, fixed 878777 in 2.11b-11.1, notfixed 897049 in 1.6.2 ...

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # fix bug metadata to allow archival > tags 885143 - buster Bug #885143 {Done: Rene Engelhard } [src:libreoffice] libreoffice-gtk2: Drop gtk2 support Removed tag(s) buster. > reassign 878777 src:noweb 2.11b-9 Bug #878777 {Done: Debian FTP Masters

Processed: Re: r-cran-lwgeom: FTBFS with PROJ 7.0.0 (ERROR: lazy loading failed for package 'lwgeom')

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 951656 r-cran-lwgeom/0.2-1-1 Bug #951656 [src:r-cran-lwgeom] r-cran-lwgeom: FTBFS with PROJ 7.0.0 (ERROR: lazy loading failed for package 'lwgeom') No longer marked as found in versions r-cran-lwgeom/0.2-1-1. > severity 951656 normal Bug

Bug#954219: marked as done (pyresample: autopkgtest failures (AttributeError: module 'pyproj._proj' has no attribute 'Proj'))

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 09:35:12 + with message-id and subject line Bug#954219: fixed in pyresample 1.14.0-4 has caused the Debian Bug report #954219, regarding pyresample: autopkgtest failures (AttributeError: module 'pyproj._proj' has no attribute 'Proj') to be marked as done.

Bug#948552: any update on the soname issue in libschroedinger-maeparser1

2020-03-19 Thread merkys
Hi, On 2020-02-23 18:29, shirish शिरीष wrote: > Any update on the soname issue in getting the > libschroedinger-maeparser1 issue resolved, just pinging. It's the only > reason for not installing openbabel. I will update the package to the newest upstream release, at the same time using the correc

Bug#954244: mpich FTBFS on armel, armhf, i386, mipsel: static assertion failed: "MPL_COMPILE_TIME_ASSERT failure"

2020-03-19 Thread Paul Gevers
Source: mpich Version: 3.4~a2-1 Severity: serious Justification: ftbfs Hi maintainer(s), The latest versions of your package fails to build from source, which prevents it from migrating to testing. Paul https://buildd.debian.org/status/package.php?p=mpich Tail of log for mpich on armel: In fi

Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception

2020-03-19 Thread Paul Gevers
Hi Michael, On 25-02-2020 15:56, Michael Banck wrote: > Hi Paul, > > On Mon, Feb 24, 2020 at 08:57:40PM +0100, Paul Gevers wrote: >> https://ci.debian.net/data/autopkgtest/testing/arm64/b/bagel/4258642/log.gz >> >> running test case 'hf_sto3g_relfci_gaunt'... terminate called without an >> active

Bug#954242: qgis-providers: postinst failure: free(): invalid pointer

2020-03-19 Thread Laurent Bonnaud
Package: qgis-providers Version: 3.10.3+dfsg-1+b1 Severity: serious Dear Maintainer, here is the problem: Setting up qgis-providers (3.10.3+dfsg-1+b1) ... free(): invalid pointer Aborted (core dumped) dpkg: error processing package qgis-providers (--configure): installed qgis-providers package

Processed: Re: Bug#954242: qgis-providers: postinst failure: free(): invalid pointer

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #954242 [qgis-providers] qgis-providers: postinst failure: free(): invalid pointer Severity set to 'important' from 'serious' > tags -1 upstream Bug #954242 [qgis-providers] qgis-providers: postinst failure: free(): invalid pointer Added t

Bug#954242: qgis-providers: postinst failure: free(): invalid pointer

2020-03-19 Thread Sebastiaan Couwenberg
Control: severity -1 important Control: tags -1 upstream Control: forwarded -1 https://github.com/qgis/QGIS/issues/35195 On 3/19/20 9:51 AM, Laurent Bonnaud wrote: > Note that my system has glibc 2.31 from experimental and the following > environment variables are set: Since this is not a problem

Processed: Bug#948552 marked as pending in $i

2020-03-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #948552 [libschroedinger-maeparser1] libschroedinger-maeparser1: SONAME change without package name change Added tag(s) pending. -- 948552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948552 Debian Bug Tracking System Contact ow...@bugs.de

Bug#948552: marked as pending in $i

2020-03-19 Thread Andrius Merkys
Control: tag -1 pending Hello, Bug #948552 in $i 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/debichem-team/schroedinger-maeparser/-/commit/241dc4cba882ff011

Bug#951821: marked as done (gegl: FTBFS on arm*/mips* architectures; testing migration blocked)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 08:43:09 + with message-id <20200319084309.ga190...@espresso.pseudorandom.co.uk> and subject line Re: Bug#951821: gegl: FTBFS on arm*/mips* architectures; testing migration blocked has caused the Debian Bug report #951821, regarding gegl: FTBFS on arm*/mips*

Bug#953770: marked as done (bluez: CVE-2020-0556)

2020-03-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Mar 2020 08:40:12 + with message-id and subject line Bug#953770: fixed in bluez 5.50-1.1 has caused the Debian Bug report #953770, regarding bluez: CVE-2020-0556 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Processed: tagging 912495, tagging 945731

2020-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 912495 - pending Bug #912495 [src:pydxcluster] pydxcluster: Please migrate to python3-pygame Bug #945731 [src:pydxcluster] pydxcluster: Python2 removal in sid/bullseye Removed tag(s) pending. Removed tag(s) pending. > tags 945731 - pending Bu

Bug#954134: [d-i bullseye alpha2] installing grub fails

2020-03-19 Thread Holger Wansing
Hi, Steve McIntyre wrote: > One silly question: what media are you using with the Thinkpad? Is it > the same USB stick (or whatever) every time? Can you verify it's > written OK? I used the same USB stick for alpha1 and alpha2, re-flashing it over and over again. And I have checked installation