Bug#924583: spamassassin: razor2 had unknown error during get_server_info at /usr/share/perl5/Mail/SpamAssassin/Plugin/Razor2.pm line 186

telnet discovery.razor.cloudmark.com 2703 Trying 208.83.139.205... Connected to discovery.razor.cloudmark.com. Escape character is '^]'. sn=C&srl=43882&a=l&a=cg a=g&pm=csl err=240 ... a=g&pm=nsl err=240 ... a=g&pm=state -sn=C sv=4.007 zone=razor2.cloudmark.com ac=21 srl=43882 lm=4 bql=50 bqs=329 d

Processed: Bug #924733 in pyqwt3d marked as pending

Processing control commands: > tag -1 pending Bug #924733 [src:pyqwt3d] pyqwt3d: FTBFS (SIP failed to generate the C++ code) Added tag(s) pending. -- 924733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#924733: Bug #924733 in pyqwt3d marked as pending

Control: tag -1 pending Hello, Bug #924733 in pyqwt3d 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/pyqwt3d/commit/280511aac5da610b7e37a0c

Bug#924807: [Pkg-javascript-devel] Bug#924807: Bug#924807: Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js

Le 18/03/2019 à 06:19, Xavier a écrit : > Le 18/03/2019 à 00:02, Jonas Smedegaard a écrit : >> Quoting Jonas Smedegaard (2019-03-17 23:48:57) >>> Quoting Xavier (2019-03-17 23:12:51) Control: reassign 924807 uglify-js Control: reassign 924809 uglify-js Control: merge 924807 924809 >>

Bug#924807: [Pkg-javascript-devel] Bug#924807: Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js

Le 18/03/2019 à 00:02, Jonas Smedegaard a écrit : > Quoting Jonas Smedegaard (2019-03-17 23:48:57) >> Quoting Xavier (2019-03-17 23:12:51) >>> Control: reassign 924807 uglify-js >>> Control: reassign 924809 uglify-js >>> Control: merge 924807 924809 >>> >>> Bug seems to come from conflict between >

Bug#888935: [Pkg-javascript-devel] Bug#888935: node-xterm FTBFS: error TS2339: Property 'parentElement' does not exist on type 'never'

On 2019, മാർച്ച് 18 2:33:00 AM IST, Ximin Luo wrote: >On Thu, 08 Mar 2018 17:53:27 + Ghislain Vaillant > wrote: >I had an attempt at this, but it is getting a bit hairy and I think it >may be time to call it quits. My recommendation is for jupyter-notebook >to patch out this functionality a

Bug#866421: marked as done (comix: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Mon, 18 Mar 2019 05:19:06 + with message-id and subject line Bug#866421: fixed in comix 4.0.4-4 has caused the Debian Bug report #866421, regarding comix: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be marked as done. This means that you

Bug#924206: control

Control: reassign -1 src:rust-failure 0.1.3-1 Control: fixed -1 0.1.5-1 -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git

Processed: Re: control

Processing control commands: > reassign -1 src:rust-failure 0.1.3-1 Bug #924206 {Done: Ximin Luo } [rust-failure] rust-opener: FTBFS (method `name` is not a member of trait `failure::Fail`) Bug reassigned from package 'rust-failure' to 'src:rust-failure'. No longer marked as found in versions 0.1

Bug#924206: control

Control: reassign -1 rust-failure 0.1.3-1 Control: fixed -1 0.1.5-1 -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git

Processed: control

Processing control commands: > reassign -1 rust-failure 0.1.3-1 Bug #924206 {Done: Ximin Luo } [src:rust-opener] rust-opener: FTBFS (method `name` is not a member of trait `failure::Fail`) Bug reassigned from package 'src:rust-opener' to 'rust-failure'. No longer marked as found in versions rust-

Bug#921792: closing 921792

close 921792 1.2.1-3 thanks The bug is fixed by the recent texlive update.

Processed: closing 921792

Processing commands for cont...@bugs.debian.org: > close 921792 1.2.1-3 Bug #921792 [src:log4c] log4c: FTBFS (LaTeX error) Marked as fixed in versions log4c/1.2.1-3. Bug #921792 [src:log4c] log4c: FTBFS (LaTeX error) Marked Bug as done > thanks Stopping processing here. Please contact me if you n

Bug#924665: marked as done (xymon: Upgrade fails if /etc/xymon/critical.cfg.bak is deleted by local admin)

Your message dated Mon, 18 Mar 2019 04:04:21 + with message-id and subject line Bug#924665: fixed in xymon 4.3.28-5 has caused the Debian Bug report #924665, regarding xymon: Upgrade fails if /etc/xymon/critical.cfg.bak is deleted by local admin to be marked as done. This means that you clai

Bug#924806: marked as done (ruby-moneta: FTBFS: build-dependency not installable: ruby-fog)

Your message dated Mon, 18 Mar 2019 03:34:08 + with message-id and subject line Bug#924806: fixed in ruby-moneta 1.0.0-5 has caused the Debian Bug report #924806, regarding ruby-moneta: FTBFS: build-dependency not installable: ruby-fog to be marked as done. This means that you claim that the

Processed: Bug #924806 in ruby-moneta marked as pending

Processing control commands: > tag -1 pending Bug #924806 [src:ruby-moneta] ruby-moneta: FTBFS: build-dependency not installable: ruby-fog Added tag(s) pending. -- 924806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924806 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#924806: Bug #924806 in ruby-moneta marked as pending

Control: tag -1 pending Hello, Bug #924806 in ruby-moneta 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/ruby-team/ruby-moneta/commit/b2e6386c5b5623490380ff2a0

Bug#924820: marked as done (fltk1.3: FTBFS: cp: cannot stat 'latex/refman.pdf': No such file or directory)

Your message dated Sun, 17 Mar 2019 23:03:45 -0400 with message-id and subject line Re: Bug#924820: fltk1.3: FTBFS: cp: cannot stat 'latex/refman.pdf': No such file or directory has caused the Debian Bug report #924820, regarding fltk1.3: FTBFS: cp: cannot stat 'latex/refman.pdf': No such file or

Bug#924800: marked as done (git-annex: FTBFS: dh_auto_test: make -j1 test returned exit code 2)

Your message dated Sun, 17 Mar 2019 19:46:59 -0700 with message-id <87imwgew64@iris.silentflame.com> and subject line Re: Bug#924800: git-annex: FTBFS: dh_auto_test: make -j1 test returned exit code 2 has caused the Debian Bug report #924800, regarding git-annex: FTBFS: dh_auto_test: make -j1

Bug#924897: openjdk-12-jre-headless: fails to install: breaks configuration of ca-certificates-java

Package: openjdk-12-jre-headless Version: 12~33-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity

Bug#924896: lttng-modules-dkms: fails to build module for Linux 4.19.0-4

Package: lttng-modules-dkms Version: 2.10.9-1 Severity: serious Justification: fails to build from source User: debian...@lists.debian.org Usertags: piuparts Hi, installation fails because a module cannot be built. make.log starts like this: DKMS make.log for lttng-modules-2.10.9 for kernel 4.1

Bug#919875: Info received ()

My phone has been hacked for years eden matthews gary reid Brandon brooks clay matthews katelyn brooks . On Sun, Mar 17, 2019, 10:15 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This

Bug#919875:

Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)

On Sun 2019-03-17 13:14:54 +0100, Tim Rühsen wrote: > Fixed it by building my own libiconv on MinGW systems. It really is > straight forward and possibly no extra Debian package is needed. Thanks for the feedback, Tim. For your fix, are you building libiconv itself, or win-iconv for MinGW systems

Bug#924894: human-icon-theme: Installs translation files in /usr/locale

Package: human-icon-theme Version: 0.28.debian-6 Severity: serious Justification: Policy 9.1.1 It installs .mo files at the /usr/locale path. These are the files: /usr/locale: total 12 drwxr-xr-x 3 root 4096 feb 28 23:45 fr drwxr-xr-x 3 root 4096 feb 28 23:45 it drwxr-xr-x 3 root 4096 feb 28 23:

Bug#924706: marked as done (icedtea-netx: javaws symlink is broken)

Your message dated Mon, 18 Mar 2019 00:19:18 + with message-id and subject line Bug#924706: fixed in icedtea-web 1.7.2-2 has caused the Debian Bug report #924706, regarding icedtea-netx: javaws symlink is broken to be marked as done. This means that you claim that the problem has been dealt w

Bug#924706: Bug #924706 in icedtea-web marked as pending

Control: tag -1 pending Hello, Bug #924706 in icedtea-web 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/java-team/icedtea-web/commit/5c158c34dfca44d235256a18d

Processed: Bug #924706 in icedtea-web marked as pending

Processing control commands: > tag -1 pending Bug #924706 [icedtea-netx] icedtea-netx: javaws symlink is broken Added tag(s) pending. -- 924706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#924348: marked as done (CVE-2019-7629)

Your message dated Sun, 17 Mar 2019 23:05:21 + with message-id and subject line Bug#924348: fixed in tintin++ 2.01.5-2 has caused the Debian Bug report #924348, regarding CVE-2019-7629 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Bug#924807: [Pkg-javascript-devel] Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js

Quoting Jonas Smedegaard (2019-03-17 23:48:57) > Quoting Xavier (2019-03-17 23:12:51) > > Control: reassign 924807 uglify-js > > Control: reassign 924809 uglify-js > > Control: merge 924807 924809 > > > > Bug seems to come from conflict between > > https://tracker.debian.org/pkg/uglify-js and > >

Bug#924807: [Pkg-javascript-devel] Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js

Quoting Xavier (2019-03-17 23:12:51) > Control: reassign 924807 uglify-js > Control: reassign 924809 uglify-js > Control: merge 924807 924809 > > Bug seems to come from conflict between > https://tracker.debian.org/pkg/uglify-js and > https://tracker.debian.org/pkg/uglifyjs: webpack can't now be i

Bug#924808: lua-nvim: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

On Sun, Mar 17, 2019 at 07:09:44PM +0100, Lucas Nussbaum wrote: > Source: lua-nvim > Version: 0.1.0-1-1 > Severity: serious > Tags: buster sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20190315 qa-ftbfs > Justification: FTBFS in buster on amd64 Hello Lucas. I was able to reproduce th

Processed: tagging 924764, tagging 924651

Processing commands for cont...@bugs.debian.org: > tags 924764 + sid buster Bug #924764 [src:mingw-ocaml] mingw-ocaml: FTBFS (cp: cannot stat 'objinfo_helper': No such file or directory) Added tag(s) buster and sid. > tags 924651 + sid buster Bug #924651 {Done: gud...@gudjon.org (Gudjon I. Gudjon

Bug#807666: reopen 807666, it should be fixed properly

Hi Alastair, On Thu, 14 Mar 2019 22:37:45 +0100 Ana Guerrero Lopez wrote: > I have sent a patch to upstream that should fix the issue: > https://lists.mpich.org/pipermail/discuss/2019-March/011160.html I've queued up this patch in my anbe/alternatives branch that hasn't been acted upon, yet. If

Bug#924807: [Pkg-javascript-devel] Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js

Le 17/03/2019 à 23:12, Xavier a écrit : > Bug seems to come from conflict between > https://tracker.debian.org/pkg/uglify-js and > https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed > with uglifyjs node-jscharset build-depends on both webpack and uglifyjs: * webpack depends o

Processed: Re: libxml-twig-perl: expand_external_ents fails to work as documented

Processing commands for cont...@bugs.debian.org: > severity 842893 grave Bug #842893 [src:libxml-twig-perl] libxml-twig-perl: CVE-2016-9180: expand_external_ents fails to work as documented Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need

Bug#898634: marked as done (kmail: efail attack against S/MIME)

Your message dated Sun, 17 Mar 2019 23:24:13 +0100 with message-id <4145727.q3mdy22fzh@tuxin> and subject line Re: Bug#898634: kmail: efail attack against S/MIME has caused the Debian Bug report #898634, regarding kmail: efail attack against S/MIME to be marked as done. This means that you claim t

Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js

Control: reassign 924807 uglify-js Control: reassign 924809 uglify-js Control: merge 924807 924809 Bug seems to come from conflict between https://tracker.debian.org/pkg/uglify-js and https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed with uglifyjs Le 17/03/2019 à 19:05, Luc

Processed: Bugs come from conflict between node-uglify and node-uglify-js

Processing control commands: > reassign 924807 uglify-js Bug #924807 [uglify-js] node-jschardet: FTBFS: build-dependency not installable: webpack Bug #924809 [uglify-js] node-timeago.js: FTBFS: build-dependency not installable: webpack Ignoring request to reassign bug #924807 to the same package

Processed: Bugs come from conflict between node-uglify and node-uglify-js

Processing control commands: > reassign 924807 uglify-js Bug #924807 [src:node-jschardet] node-jschardet: FTBFS: build-dependency not installable: webpack Bug reassigned from package 'src:node-jschardet' to 'uglify-js'. No longer marked as found in versions node-jschardet/1.6.0+dfsg-1. Ignoring r

Processed: unblock: kaddressbook/4:18.08.3-3

Processing control commands: > block 910731 by -1 Bug #910731 {Done: Sandro Knauß } [kaddressbook] KAdressebook missing to dependency on akonadi 910731 was not blocked by any bugs. 910731 was not blocking any bugs. Added blocking bug(s) of 910731: 924882 -- 910731: https://bugs.debian.org/cgi-b

Bug#923416: marked as done (advancecomp: CVE-2019-9210)

Your message dated Sun, 17 Mar 2019 21:49:10 + with message-id and subject line Bug#923416: fixed in advancecomp 2.1-2 has caused the Debian Bug report #923416, regarding advancecomp: CVE-2019-9210 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#853016: marked as done (nodm: regression: restarts during upgrade, causing data loss)

Your message dated Sun, 17 Mar 2019 21:36:18 + with message-id and subject line Bug#853016: fixed in nodm 0.13-5 has caused the Debian Bug report #853016, regarding nodm: regression: restarts during upgrade, causing data loss to be marked as done. This means that you claim that the problem ha

Bug#919980: marked as done (nodm: regression: restarts during upgrade, causing data loss)

Your message dated Sun, 17 Mar 2019 21:36:18 + with message-id and subject line Bug#853016: fixed in nodm 0.13-5 has caused the Debian Bug report #853016, regarding nodm: regression: restarts during upgrade, causing data loss to be marked as done. This means that you claim that the problem ha

Bug#924630: marked as done (golang-1.11: CVE-2019-9741: CRLF injection in net/http)

Your message dated Sun, 17 Mar 2019 21:34:53 + with message-id and subject line Bug#924630: fixed in golang-1.11 1.11.6-1 has caused the Debian Bug report #924630, regarding golang-1.11: CVE-2019-9741: CRLF injection in net/http to be marked as done. This means that you claim that the problem

Bug#924799: qtspeech-opensource-src: FTBFS: dh_auto_test: make -j4 check -Ctests/auto QT_HASH_SEED=0 QT_QPA_PLATFORM=minimal returned exit code 2

El domingo, 17 de marzo de 2019 18:06:30 -03 Lisandro Damián Nicanor Pérez Meyer escribió: > The problem seems to be different, as I can reproduce it on a porterbox > (except barriere also has no audio). Also FTBFS in a server with audio setup, unstable chroot. Something has changed since we las

Bug#855686: icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met

Control: tags -1 - pending Control: tags -1 + wontfix Control: close -1 The browser plugin has been removed in 1.7.1-1.

Processed: fix ftbfs bug metadata

Processing commands for cont...@bugs.debian.org: > # fix up reassign without affects > affects 923759 + src:mtj Bug #923759 [netlib-java] mtj: FTBFS in buster/sid Added indication that 923759 affects src:mtj > thanks Stopping processing here. Please contact me if you need assistance. -- 923759:

Processed: Re: icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met

Processing control commands: > tags -1 - pending Bug #855686 [src:icedtea-web] icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met Removed tag(s) pending. > tags -1 + wontfix Bug #855686 [src:icedtea-web] icedtea-web: FTBFS: configure: error: Package requirem

Processed: Bug #924630 in golang marked as pending

Processing control commands: > tag -1 pending Bug #924630 [src:golang-1.11] golang-1.11: CVE-2019-9741: CRLF injection in net/http Ignoring request to alter tags of bug #924630 to the same tags previously set -- 924630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924630 Debian Bug Trackin

Bug#924630: Bug #924630 in golang marked as pending

Control: tag -1 pending Hello, Bug #924630 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/71582deb22213b82603e44203245

Bug#924630: Bug #924630 in golang marked as pending

Control: tag -1 pending Hello, Bug #924630 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/71582deb22213b82603e44203245

Processed: Bug #924630 in golang marked as pending

Processing control commands: > tag -1 pending Bug #924630 [src:golang-1.11] golang-1.11: CVE-2019-9741: CRLF injection in net/http Ignoring request to alter tags of bug #924630 to the same tags previously set -- 924630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924630 Debian Bug Trackin

Bug#924630: Bug #924630 in golang marked as pending

Control: tag -1 pending Hello, Bug #924630 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/0c508f9cd760bd475f41b8d06735

Processed: Bug #924630 in golang marked as pending

Processing control commands: > tag -1 pending Bug #924630 [src:golang-1.11] golang-1.11: CVE-2019-9741: CRLF injection in net/http Ignoring request to alter tags of bug #924630 to the same tags previously set -- 924630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924630 Debian Bug Trackin

Processed: Bug #924630 in golang marked as pending

Processing control commands: > tag -1 pending Bug #924630 [src:golang-1.11] golang-1.11: CVE-2019-9741: CRLF injection in net/http Added tag(s) pending. -- 924630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#924630: Bug #924630 in golang marked as pending

Control: tag -1 pending Hello, Bug #924630 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/0c508f9cd760bd475f41b8d06735

Bug#924799: qtspeech-opensource-src: FTBFS: dh_auto_test: make -j4 check -Ctests/auto QT_HASH_SEED=0 QT_QPA_PLATFORM=minimal returned exit code 2

El domingo, 17 de marzo de 2019 17:54:39 -03 Lisandro Damián Nicanor Pérez Meyer escribió: > Hi Lucas! > > El domingo, 17 de marzo de 2019 15:20:23 -03 Lucas Nussbaum escribió: > > Source: qtspeech-opensource-src > > Version: 5.11.3-2 > > Severity: serious > > Tags: buster sid > > User: debian...

Bug#924825: marked as done (preggy: FTBFS: build-dependency not installable: python-tox)

Your message dated Sun, 17 Mar 2019 21:04:56 + with message-id and subject line Bug#924825: fixed in preggy 1.3.0-2 has caused the Debian Bug report #924825, regarding preggy: FTBFS: build-dependency not installable: python-tox to be marked as done. This means that you claim that the problem

Bug#888935: node-xterm FTBFS: error TS2339: Property 'parentElement' does not exist on type 'never'

On Thu, 08 Mar 2018 17:53:27 + Ghislain Vaillant wrote: > > Source: node-xterm > > Version: 2.7.0+ds1-1 > > Severity: serious > > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/no > > de-xterm.html > > > > ... > >debian/rules override_dh_auto_build > > make[1]: En

Bug#924799: qtspeech-opensource-src: FTBFS: dh_auto_test: make -j4 check -Ctests/auto QT_HASH_SEED=0 QT_QPA_PLATFORM=minimal returned exit code 2

Hi Lucas! El domingo, 17 de marzo de 2019 15:20:23 -03 Lucas Nussbaum escribió: > Source: qtspeech-opensource-src > Version: 5.11.3-2 > Severity: serious > Tags: buster sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20190315 qa-ftbfs > Justification: FTBFS in buster on amd64 > > Hi,

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forcemerge 923282 924797 Bug #923282 [freezegun] freezegun breaks cached-property autopkgtest Bug #923282 [freezegun] freezegun breaks cached-property autopkgtest Added tag(s) buster and sid. Bug #924797 [freezegun] cached-property: FTBFS: dh_auto

Processed: found 923416 in 1.20-1

Processing commands for cont...@bugs.debian.org: > found 923416 1.20-1 Bug #923416 [src:advancecomp] advancecomp: CVE-2019-9210 Marked as found in versions advancecomp/1.20-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 923416: https://bugs.debian.org/cgi-bin/

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 924797 freezegun 0.3.11-0.1 Bug #924797 [src:cached-property] cached-property: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13 Bug reassigned from package 'src:cached-property' to 'freezegun'. No longe

Bug#924797: cached-property: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13

* Lucas Nussbaum: " Bug#924797: cached-property: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13" (Sun, 17 Mar 2019 19:07:51 +0100): Hi Lucas, > Source: cached-property > Version: 1.5.1-2 > Severity: serious > Tags: buster sid > User: debian...@lists.debian

Bug#924866: marked as done (elpa-geiser: incompatible with emacs 26)

Your message dated Sun, 17 Mar 2019 20:37:23 + with message-id and subject line Bug#924866: fixed in geiser 0.8.1-4 has caused the Debian Bug report #924866, regarding elpa-geiser: incompatible with emacs 26 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: advancecomp: diff for NMU version 2.1-1.1

Processing control commands: > tags 923416 + patch Bug #923416 [src:advancecomp] advancecomp: CVE-2019-9210 Added tag(s) patch. > tags 923416 + pending Bug #923416 [src:advancecomp] advancecomp: CVE-2019-9210 Added tag(s) pending. -- 923416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=9234

Bug#923416: advancecomp: diff for NMU version 2.1-1.1

Control: tags 923416 + patch Control: tags 923416 + pending Dear maintainer, I've prepared an NMU for advancecomp (versioned as 2.1-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Salvatore diff -Nru advancecomp-2.1/debian/changelog advanceco

Bug#924706: icedtea-netx: javaws symlink is broken

On 16/03/2019 05:08, Jon DeVree wrote: > The files in /usr/share/icedtea-web/bin have the wrong file names in the > new package and this breaks javaws. itweb-settings and policyeditor are > also broken. Hi Jon, Thank you for reporting this issue. I'll upload a fix shortly. Emmanuel Bourg

Processed: tagging 924859

Processing commands for cont...@bugs.debian.org: > tags 924859 + confirmed Bug #924859 [src:libfurl-perl] libfurl-perl: FTBFS: tests failed Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 924859: https://bugs.debian.org/cgi-bin/bugreport.cg

Bug#924866: elpa-geiser: incompatible with emacs 26

Package: elpa-geiser Version: 0.8.1-3 Severity: serious Tags: upstream Justification: does not load Control: tag -1 pending geiser 0.8.1 has upstream issue #207 [1], which makes it unable to load in emacs 26. To duplicate: emacs -q M-x package-initialize M-x toggle-debug-on-error C-x C-f foo.r

Bug#924824: marked as done (rust-cargo: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101)

Your message dated Sun, 17 Mar 2019 19:41:00 + with message-id <62f68e14-41af-8ebc-6399-b620ad525...@debian.org> and subject line fixed by #924752 has caused the Debian Bug report #924824, regarding rust-cargo: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101 to be

Bug#924827: marked as done (rust-debcargo: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101)

Your message dated Sun, 17 Mar 2019 19:41:00 + with message-id <62f68e14-41af-8ebc-6399-b620ad525...@debian.org> and subject line fixed by #924752 has caused the Debian Bug report #924827, regarding rust-debcargo: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101 to

Bug#924810: marked as done (rust-cargo-lichking: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101)

Your message dated Sun, 17 Mar 2019 19:41:00 + with message-id <62f68e14-41af-8ebc-6399-b620ad525...@debian.org> and subject line fixed by #924752 has caused the Debian Bug report #924810, regarding rust-cargo-lichking: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 1

Bug#924815: marked as done (rust-cargo-vendor: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101)

Your message dated Sun, 17 Mar 2019 19:41:00 + with message-id <62f68e14-41af-8ebc-6399-b620ad525...@debian.org> and subject line fixed by #924752 has caused the Debian Bug report #924815, regarding rust-cargo-vendor: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101

Bug#924833: marked as done (qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override)

Your message dated Sun, 17 Mar 2019 20:21:28 +0100 with message-id <9a52ce36-97c1-6853-ec31-ecfbf431d...@xs4all.nl> and subject line Re: Bug#924833: qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not ove

Bug#924860: multipath-tools: FTBFS: /bin/sh: 1: Syntax error: "(" unexpected

Source: multipath-tools Version: 0.7.9-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to b

Bug#924855: shellia: FTBFS: tests failed

Source: shellia Version: 5.3.1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on am

Bug#924857: frobby: FTBFS: make[3]: *** [Makefile:6: refman.pdf] Error 1

Source: frobby Version: 0.9.0-5 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on a

Processed: severity of 923750 is serious

Processing commands for cont...@bugs.debian.org: > severity 923750 serious Bug #923750 [src:gdcm] gdcm: FTBFS in buster/sid Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 923750: https://bugs.debian.org/cgi-bin/bugreport

Bug#924858: doxygen: FTBFS: make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:62: doc/CMakeFiles/doxygen_pdf] Error 1

Source: doxygen Version: 1.8.13-10 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build o

Bug#924856: wxpython4.0: FTBFS: sip: /<>/wxpython4.0-4.0.4+dfsg/src/wacky_ints.sip:20: Invalid type for %MappedType

Source: wxpython4.0 Version: 4.0.4+dfsg-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to

Bug#924859: libfurl-perl: FTBFS: tests failed

Source: libfurl-perl Version: 3.13-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build

Bug#924826: marked as done (python-osmapi: FTBFS: build-dependency not installable: python-tox)

Your message dated Sun, 17 Mar 2019 19:20:34 + with message-id and subject line Bug#924826: fixed in python-osmapi 1.2.2-2 has caused the Debian Bug report #924826, regarding python-osmapi: FTBFS: build-dependency not installable: python-tox to be marked as done. This means that you claim tha

Processed: Re: Bug#924833: qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override

Processing commands for cont...@bugs.debian.org: > fixed 924833 qgis/3.4.5+dfsg-1~exp1 Bug #924833 [src:qgis] qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override Marked as fixed in versions qgis

Processed: Re: Bug#924833: qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override

Processing control commands: > tags -1 confirmed Bug #924833 [src:qgis] qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override Added tag(s) confirmed. -- 924833: https://bugs.debian.org/cgi-bin/b

Bug#924833: qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override

Control: tags -1 confirmed Looks like sip4 (4.19.14+dfsg-1) broke the SIP bindings again. It's quite unfortunate that the 2.18.x LTR is EOL upstream, making them unlikely to provide a fix. I'll see what I can do to fix this. If I can't, we'll just have to release buster without QGIS and deal wit

Bug#924826: python-osmapi: FTBFS: build-dependency not installable: python-tox

Control: tags -1 pending On 3/17/19 7:05 PM, Lucas Nussbaum wrote: >> sbuild-build-depends-python-osmapi-dummy : Depends: python-tox but it is >> not installable According to #922487 the transition package was removed, but this was not coordinated. The B-D has been replaced with 'tox' to fix t

Processed: Re: Bug#924826: python-osmapi: FTBFS: build-dependency not installable: python-tox

Processing control commands: > tags -1 pending Bug #924826 [src:python-osmapi] python-osmapi: FTBFS: build-dependency not installable: python-tox Added tag(s) pending. -- 924826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924826 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Bug#899007: bauble: Depends on unmaintained python-gdata

hello all, bauble as bauble is indeed dead, both the classic and the web version, which by the way never saw light. → HOWEVER → → while Debian and ubuntu still distribute the grossly outdated bauble 0.9.7, development of bauble went up to version 1.0.56, which is still a very decent option. → b

Processed: severity of 922767 is serious

Processing commands for cont...@bugs.debian.org: > severity 922767 serious Bug #922767 [libemf] libemf : FTBFS - mv: cannot stat 'refman.pdf': No such file or directory - Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 9

Bug#924847: i2p: FTBFS: [javac] /<>/apps/jetty/java/src/net/i2p/jetty/I2PRequestLog.java:378: error: method write in interface Writer cannot be applied to given types;

Source: i2p Version: 0.9.38-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd

Bug#924846: qtscript-opensource-src: FTBFS: ../3rdparty/javascriptcore/JavaScriptCore/jit/JITStubs.cpp:483:5: error: expected '(' before 'volatile'

Source: qtscript-opensource-src Version: 5.11.3+dfsg-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your packa

Bug#924845: nanoc: FTBFS: build-dependency not installable: ruby-fog (>= 0.13.0~)

Source: nanoc Version: 4.11.0-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on a

Bug#924850: netpipe: FTBFS: Errors while processing: openmpi-bin libopenmpi-dev:amd64 sbuild-build-depends-netpipe-dummy

Source: netpipe Version: 3.7.2-7.4 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build o

Bug#924848: telegram-cli: FTBFS: build-dependency not installable: libwolfssl-dev

Source: telegram-cli Version: 1.3.1+git20160323.6547c0b21-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your

Bug#924840: highwayhash: FTBFS: dh_makeshlibs: failing due to earlier errors

Source: highwayhash Version: 0~git20181002.c5ee50b-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package

Bug#924838: scoop: FTBFS: Could not import extension sphinx.ext.pngmath (exception: No module named pngmath)

Source: scoop Version: 0.7.1.1-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on

Bug#924841: lib3mf: FTBFS: dh_makeshlibs: failing due to earlier errors

Source: lib3mf Version: 1.8.1+ds-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build o

Bug#924837: adios: FTBFS: mpicxx.h:22:4: error: #error 'Please use the same version of GCC and g++ for compiling MPICH and user MPI programs'

Source: adios Version: 1.13.1-16 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on

  1   2   >