Processed: Bug #918685 in graphite2 marked as pending

2019-01-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #918685 [src:graphite2] graphite2: FTBFS with test failures: awamicmp[123] Added tag(s) pending. -- 918685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#917829: python-intbitset: FTBFS when built with dpkg-buildpackage -A

2019-01-08 Thread Adrian Bunk
On Sun, Dec 30, 2018 at 07:52:26PM +, Santiago Vila wrote: >... > In case it helps, this stopped working in buster sometime between 2018-12-11 > and 2018-12-23 >... The Python3 default change 3.6 -> 3.7 migrated on 2018-12-19 to buster. > Thanks. cu Adrian -- "Is there not

Bug#917745: cross-toolchain-base: FTBFS: applying patches fails

2019-01-08 Thread Paul Gevers
user debian...@lists.debian.org usertags needs-update thanks Hi all, On Sat, 29 Dec 2018 23:46:40 +0100 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > debian/rules build > > linux: 4.19.12-1 /

Bug#917633: Also blocks migration of tails-installer

2019-01-08 Thread Ulrike Uhlig
Hello! this issue currently also blocks the migration of tails-installer, shortly before the freeze. Cheers! u.

Bug#918685: Bug #918685 in graphite2 marked as pending

2019-01-08 Thread Rene Engelhard
Control: tag -1 pending Hello, Bug #918685 in graphite2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#918733: googletest FTBFS on mips/mipsel: out of memory

2019-01-08 Thread Adrian Bunk
Source: googletest Version: 1.8.1-2 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/package.php?p=googletest ... as: out of memory allocating 4072 bytes after a total of 543838208 bytes /tmp/ccnTRJ3H.s: Assembler messages: /tmp/ccnTRJ3H.s: Fatal error: can't close

Processed: Re: Bug#917633: udisk2 post-installation fails in chrooted environments

2019-01-08 Thread Debian Bug Tracking System
Processing control commands: > affects 917633 src:ltsp Bug #917633 [udisks2] udisk2 post-installation fails in chrooted environments Added indication that 917633 affects src:ltsp -- 917633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917633 Debian Bug Tracking System Contact

Bug#917633: udisk2 post-installation fails in chrooted environments

2019-01-08 Thread Vagrant Cascadian
Control: affects 917633 src:ltsp Also blocking migration for ltsp: https://piuparts.debian.org/sid/fail/ltsp-server-standalone_5.18.12-1.log live well, vagrant signature.asc Description: PGP signature

Bug#918740: rdkit: baseline violation on amd64/i386 and FTBFS everywhere else

2019-01-08 Thread Adrian Bunk
Source: rdkit Version: 201803.4+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=rdkit=sid ... gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing

Bug#917718: marked as done (libuv1: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Jan 2019 21:21:33 +0100 with message-id <20190108202133.rhndoayl3ozgs...@xanadu.blop.info> and subject line Re: libuv1: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 has caused the Debian Bug report #917718, regarding libuv1: FTBFS: dh_auto_test:

Bug#917697: marked as done (ocaml-visitors: FTBFS: build-dependency not installable: libppx-deriving-ocaml-dev (>= 4.0))

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Jan 2019 21:35:21 +0100 with message-id <20190108203521.ba7cz6tgqr7ke...@xanadu.blop.info> and subject line Closing unreproducible FTBFS bug has caused the Debian Bug report #917697, regarding ocaml-visitors: FTBFS: build-dependency not installable:

Processed: tagging 916005

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 916005 + pending Bug #916005 [src:oss4] oss4 FTBFS with glibc 2.28 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 916005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916005

Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-08 Thread Faidon Liambotis
Package: src:fakechroot Version: 2.19-3 Severity: serious Hi again, So jemalloc 5.1.0-2 was recently uploaded to unstable. The build currently fails due to the explicit dependency on libjemalloc1 (cf. #918741), but as soon as this gets fixed, another issue is uncovered: While building this

Bug#917704: marked as done (ppx-deriving-yojson: FTBFS: build-dependency not installable: libppx-deriving-ocaml-dev (>= 4.0))

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Jan 2019 21:17:08 +0100 with message-id <20190108201708.ga15...@seneca.home.org> and subject line Re: ppx-deriving-yojson: FTBFS: build-dependency not installable: libppx-deriving-ocaml-dev (>= 4.0) has caused the Debian Bug report #917704, regarding ppx-deriving-yojson:

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

2019-01-08 Thread Georg Richter
Hi Otto, it doesn't make sense to zero a pointer, if the container (or speaking of C: structure) is freed afterwards. The documentation clearly states, that a handle (which was previously freed by mysql_close() ) needs to be initialized again. The pull request fixes the perl test case, but it

Bug#918741: Build-Depends on deprecated libjemalloc SONAME directly

2019-01-08 Thread Faidon Liambotis
Package: src:fakechroot Version: 2.19-3 Severity: serious Hi, I uploaded jemalloc 5.1.0-2 to unstable the other day. It involves a new ABI and SONAME and thus a transition from libjemalloc1 -> libjemalloc2. I noticed that your package Build-Depends directly on libjemalloc1, and thus this

Processed: found 917925 in 2013.08.08-5

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 917925 2013.08.08-5 Bug #917925 [device3dfx-source] Module fails to load on Linux 4.3 or later Marked as found in versions device3dfx/2013.08.08-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 917925:

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

2019-01-08 Thread Otto Kekäläinen
For the records of this bug report and people following it, there are a lot of discussions going on in both https://github.com/perl5-dbi/DBD-mysql/issues/275 and https://github.com/MariaDB/mariadb-connector-c/pull/95 I will now import MariaDB 10.3.12 into

Bug#864432: marked as done (funcoeszz: depends on a transitional package lynx-cur)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 18:49:31 + with message-id and subject line Bug#864432: fixed in funcoeszz 15.5-1.1 has caused the Debian Bug report #864432, regarding funcoeszz: depends on a transitional package lynx-cur to be marked as done. This means that you claim that the problem

Bug#918685: marked as done (graphite2: FTBFS with test failures: awamicmp[123])

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 18:49:59 + with message-id and subject line Bug#918685: fixed in graphite2 1.3.13-4 has caused the Debian Bug report #918685, regarding graphite2: FTBFS with test failures: awamicmp[123] to be marked as done. This means that you claim that the problem has

Bug#918157: marked as done (libpmix2 seems broken on 32 bits architectures)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 19:40:11 + with message-id and subject line Bug#918157: fixed in pmix 3.1.0~rc2-3 has caused the Debian Bug report #918157, regarding libpmix2 seems broken on 32 bits architectures to be marked as done. This means that you claim that the problem has been

Bug#918676: marked as done (r-cran-worrms: autopkgtest regression)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Jan 2019 21:38:16 +0200 with message-id and subject line Re: Bug#918676: r-cran-worrms: autopkgtest regression has caused the Debian Bug report #918676, regarding r-cran-worrms: autopkgtest regression to be marked as done. This means that you claim that the problem has

Bug#917679: marked as done (caffe: FTBFS: dh_auto_test: cd caffe_cpu_build && make -j2 test runtest pytest LD_LIBRARY_PATH=/<>/caffe-1.0.0\+git20180821.99bd997/caffe_cpu_build/lib/ ARGS\+=-j

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Jan 2019 21:30:47 +0100 with message-id <20190108203047.w25kxobvzp4jc...@xanadu.blop.info> and subject line Re: Bug#917679: caffe: FTBFS: dh_auto_test: cd caffe_cpu_build && make -j2 test runtest pytest

Processed: reassign 917633 to udev, found 917633 in 240-1

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 917633 udev Bug #917633 [udisks2] udisk2 post-installation fails in chrooted environments Bug reassigned from package 'udisks2' to 'udev'. No longer marked as found in versions udisks2/2.8.1-3. Ignoring request to alter fixed versions of

Bug#918713: marked as done (libopenmpi3: test failure triggered by mca_pmix_pmix2x.so: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 21:04:29 + with message-id and subject line Bug#918713: fixed in openmpi 3.1.3-9 has caused the Debian Bug report #918713, regarding libopenmpi3: test failure triggered by mca_pmix_pmix2x.so: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version to be marked

Bug#918738: libodb-api-dev is not installable due to typo in the dependencies

2019-01-08 Thread Adrian Bunk
Package: libodb-api-dev Version: 0.18.1-3 Severity: serious The following packages have unmet dependencies: libodb-api-dev : Depends: ibodb-api-bin (= 0.18.1-3) but it is not installable

Processed (with 1 error): your mail

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user tails-...@boum.org Setting user to tails-...@boum.org (was ulr...@debian.org). > tag 917633 + for-buster Unknown tag/s: for-buster. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i

Bug#918739: node-duplexer2 FTBFS with nodejs 10.15.0

2019-01-08 Thread Adrian Bunk
Source: node-duplexer2 Version: 0.1.4-1 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-duplexer2.html ... mocha -R tap 1..14 ok 1 duplexer2 should interact with the writable stream properly for writing ok 2 duplexer2 should

Processed: Bug #917633 in systemd marked as pending

2019-01-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #917633 [udev] udisk2 post-installation fails in chrooted environments Added tag(s) pending. -- 917633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#917633: Bug #917633 in systemd marked as pending

2019-01-08 Thread Michael Biebl
Control: tag -1 pending Hello, Bug #917633 in systemd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#917075: marked as done (mariadb-10.3: libmariadb3 causes removal of default-libmysqlclient-dev)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Jan 2019 22:43:01 +0100 with message-id <0196760c-c34b-cbdf-c60b-859d1fc74...@debian.org> and subject line Re: mariadb-10.3: libmariadb3 causes removal of default-libmysqlclient-dev has caused the Debian Bug report #917075, regarding mariadb-10.3: libmariadb3 causes

Bug#918467: lxpanel: Weather plugin uses obsolete APIs, does not work.

2019-01-08 Thread Andriy Grytsenko
Yes, Yahoo unfortunately ended free service at January 3. New API requires registering the application and has unknown restrictions which probably will lead the weather plugin to DoS situation, because if developer registers API to get a key then that limitation will be applied to each user of

Bug#918336: marked as done (axmail binary missing)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 19:34:44 + with message-id and subject line Bug#918336: fixed in axmail 2.9-2 has caused the Debian Bug report #918336, regarding axmail binary missing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#918740: marked as done (rdkit: baseline violation on amd64/i386 and FTBFS everywhere else)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Jan 2019 23:19:50 +0100 with message-id <20190108221950.gm19...@nighthawk.caipicrew.dd-dns.de> and subject line Re: [Debichem-devel] Bug#918740: rdkit: baseline violation on amd64/i386 and FTBFS everywhere else has caused the Debian Bug report #918740, regarding rdkit:

Bug#918751: python-shade: FTBFS in sid

2019-01-08 Thread Santiago Vila
Package: src:python-shade Version: 1.30.0-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python2 --with

Bug#918751: python-shade: FTBFS in sid

2019-01-08 Thread Santiago Vila
I said: > I tried to build this package in buster but it failed: Sorry for this typo, I meant sid of course.

Bug#884476: marked as done (derivations FTBFS with poppler 0.61.1)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 03:19:43 + with message-id and subject line Bug#884476: fixed in derivations 0.56.20180123.1-2 has caused the Debian Bug report #884476, regarding derivations FTBFS with poppler 0.61.1 to be marked as done. This means that you claim that the problem has

Bug#917857: NMU diff for aufs 4.19+20181217-0.1

2019-01-08 Thread Ben Hutchings
On Tue, 2019-01-08 at 13:08 +0100, Jan Luca Naumann wrote: > Hey, > > thank you for the upload and your work. I am sorry that I did not manage > to upload the new version due to too much other workload. There's nothing to be sorry about. I usually check that out-of-tree module packages are

Processed: found 907414 in 3.3.7+dfsg-3

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 907414 3.3.7+dfsg-3 Bug #907414 {Done: Xavier Guimard } [twitter-bootstrap3] twitter-bootstrap3: CVE-2018-14040 CVE-2018-14041 CVE-2018-14042 There is no source info for the package 'twitter-bootstrap3' at version '3.3.7+dfsg-3' with

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

2019-01-08 Thread Axel Beckert
Package: udev Version: 240-2 Severity: critical Justification: Breaks whole system Hi, I have no idea why this is happening, but several packages use "udevadm control --reload-rules" in their postinst (e.g. fuse) and if that's run, all process except init are instantly killed (reproducibly; the

Bug#917492: fam: FTBFS ('minor' was not declared in this scope)

2019-01-08 Thread Logan Rosen
Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/patches/19_glibc_2.28.patch: Fix FTBFS with glibc 2.28. Thanks for considering the patch. Logan Rosen -- System Information: Debian Release: buster/sid APT prefers

Processed: Re: fam: FTBFS ('minor' was not declared in this scope)

2019-01-08 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #917492 [src:fam] fam: FTBFS ('minor' was not declared in this scope) Added tag(s) patch. -- 917492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#885742: linsmith: GTK+ 3 / GooCanvas port may be available upstream

2019-01-08 Thread Jeremy Bicha
linsmith is now the last package keeping several libgnome libraries in Debian Unstable. [1] We'd like to remove those libraries soon, but I am willing to wait a bit longer for someone to port linsmith to gtk3. Note that the Debian Release Team requires your package to reach Testing by February

Bug#899632: marked as done (oss4: Invalid maintainer address pkg-oss4-maintain...@lists.alioth.debian.org)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 9 Jan 2019 08:51:32 +0200 with message-id <20190109065132.GG13260@localhost> and subject line Fixed in 4.2-build2017-1 has caused the Debian Bug report #899632, regarding oss4: Invalid maintainer address pkg-oss4-maintain...@lists.alioth.debian.org to be marked as done.

Bug#915804: Should this package be removed?

2019-01-08 Thread Moritz Mühlenhoff
On Wed, Dec 19, 2018 at 11:56:47PM +0100, Sebastian Andrzej Siewior wrote: > On 2018-12-06 22:52:32 [+0100], Moritz Muehlenhoff wrote: > > Source: cfengine2 > > Severity: serious > > > > This is replaced by src:cfengine2 and stretch has both cfengine2 and > > cfengine3, > > so users can migrate

Processed: tagging 918741

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 918741 + buster sid Bug #918741 [src:fakechroot] Build-Depends on deprecated libjemalloc SONAME directly Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 918741:

Processed: tagging 918742

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 918742 + buster sid Bug #918742 [src:fakechroot] Initialization loop/deadlock when used with jemalloc Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 918742:

Bug#914112: marked as done (galera-3 FTBFS: error: no matching function for call to 'asio::ssl::context::context(asio::io_service&, asio::ssl::context_base::method)')

2019-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 00:49:10 + with message-id and subject line Bug#914112: fixed in galera-3 25.3.25-1 has caused the Debian Bug report #914112, regarding galera-3 FTBFS: error: no matching function for call to 'asio::ssl::context::context(asio::io_service&,

Bug#820231: marked as done (ttf-marvosym: Consider to remove your package)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 04:09:29 + with message-id and subject line Bug#881704: Removed package(s) from unstable has caused the Debian Bug report #820231, regarding ttf-marvosym: Consider to remove your package to be marked as done. This means that you claim that the problem has

Bug#911285: marked as done (Current version is incompatible with Thunderbird 60)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 04:12:17 + with message-id and subject line Bug#918693: Removed package(s) from unstable has caused the Debian Bug report #911285, regarding Current version is incompatible with Thunderbird 60 to be marked as done. This means that you claim that the

Bug#790601: marked as done (revelation: depends on python-gnome2 which is deprecated)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 04:10:14 + with message-id and subject line Bug#917210: Removed package(s) from unstable has caused the Debian Bug report #790601, regarding revelation: depends on python-gnome2 which is deprecated to be marked as done. This means that you claim that the

Bug#884986: marked as done (gnome-python: Do not release with Buster)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 04:10:52 + with message-id and subject line Bug#917918: Removed package(s) from unstable has caused the Debian Bug report #884986, regarding gnome-python: Do not release with Buster to be marked as done. This means that you claim that the problem has been

Bug#884988: marked as done (pyorbit: Do not release with Buster)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 04:11:25 + with message-id and subject line Bug#917919: Removed package(s) from unstable has caused the Debian Bug report #884988, regarding pyorbit: Do not release with Buster to be marked as done. This means that you claim that the problem has been dealt

Bug#918746: Should this package be removed?

2019-01-08 Thread Moritz Muehlenhoff
Source: pam-ssh-agent-auth Severity: serious Should pam-ssh-agent-auth be removed from the archive? It seems dead upstream, the last commits are from March 2014, it's broken with OpenSSL 1.1 and was removed from testing more than a year ago. It's also one of the few remaining packages blocking

Bug#827674: marked as done (Build of oss4-dkms fails)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 23:20:46 + with message-id and subject line Bug#827674: fixed in oss4 4.2-build2017-1 has caused the Debian Bug report #827674, regarding Build of oss4-dkms fails to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#829255: marked as done (oss4-dkms: Fails to build for 4.6.0-1-amd64)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 23:20:46 + with message-id and subject line Bug#827674: fixed in oss4 4.2-build2017-1 has caused the Debian Bug report #827674, regarding oss4-dkms: Fails to build for 4.6.0-1-amd64 to be marked as done. This means that you claim that the problem has been

Bug#916005: marked as done (oss4 FTBFS with glibc 2.28)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 23:20:46 + with message-id and subject line Bug#916005: fixed in oss4 4.2-build2017-1 has caused the Debian Bug report #916005, regarding oss4 FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug #917708 in gnome-settings-daemon marked as pending

2019-01-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #917708 [src:gnome-settings-daemon] gnome-settings-daemon: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1 Ignoring request to alter tags of bug #917708 to the same tags

Bug#917708: Bug #917708 in gnome-settings-daemon marked as pending

2019-01-08 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #917708 in gnome-settings-daemon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#915804: marked as done (Should this package be removed?)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 04:16:48 + with message-id and subject line Bug#918745: Removed package(s) from unstable has caused the Debian Bug report #915804, regarding Should this package be removed? to be marked as done. This means that you claim that the problem has been dealt

Bug#851087: marked as done (cfengine2: Please migrate to openssl1.1 in buster)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 04:16:48 + with message-id and subject line Bug#918745: Removed package(s) from unstable has caused the Debian Bug report #851087, regarding cfengine2: Please migrate to openssl1.1 in buster to be marked as done. This means that you claim that the problem

Processed: forcibly merging 913789 913765

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 913789 913765 Bug #913789 [wnpp] O: leafpad -- GTK+ based simple text editor Bug #913765 [wnpp] O: leafpad -- GTK+ based simple text editor Severity set to 'serious' from 'normal' Merged 913765 913789 > thanks Stopping processing here.

Processed: Reassign libjemalloc1 bugs to src:jemalloc

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 843926 src:jemalloc 3.6.0-11 Bug #843926 {Done: Faidon Liambotis } [libjemalloc1] jemalloc uses a hard coded page size detected during build Bug #897076 {Done: Faidon Liambotis } [libjemalloc1] libjemalloc1: Version 3.6.0-11(unstable)

Processed: Re-mark bugs as found/fixed with their right versions

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 897076 3.6.0-3 Bug #897076 {Done: Faidon Liambotis } [src:jemalloc] libjemalloc1: Version 3.6.0-11(unstable) error : Error in munmap(): Invalid argument Bug #843926 {Done: Faidon Liambotis } [src:jemalloc] jemalloc uses a hard coded page

Bug#918641: marked as done (pkg_resources.DistributionNotFound: The 'cheroot' distribution was not found and is required by fava)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 14:44:06 + with message-id and subject line Bug#918641: fixed in fava 1.9-3 has caused the Debian Bug report #918641, regarding pkg_resources.DistributionNotFound: The 'cheroot' distribution was not found and is required by fava to be marked as done. This

Processed: fixed 917695 in 0.12-1

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 917695 0.12-1 Bug #917695 {Done: Maarten van Gompel } [src:mbtserver] mbtserver: FTBFS: unsatisfiable build-dependencies: libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= 3.2.16) Marked as fixed in versions

Processed: jemalloc: third time's the charm?

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 897076 5.0.1-1 Bug #897076 [src:jemalloc] libjemalloc1: Version 3.6.0-11(unstable) error : Error in munmap(): Invalid argument Bug #843926 [src:jemalloc] jemalloc uses a hard coded page size detected during build Ignoring request to alter

Bug#918642: marked as done (imagemagick: identify 6.9.10-23 doesn't convert units (pixels per cm/in))

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 15:19:34 + with message-id and subject line Bug#918642: fixed in imagemagick 8:6.9.10.23+dfsg-2 has caused the Debian Bug report #918642, regarding imagemagick: identify 6.9.10-23 doesn't convert units (pixels per cm/in) to be marked as done. This means

Bug#916074: marked as done (pcc: useless without libpcc-dev)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 15:20:43 + with message-id and subject line Bug#916074: fixed in pcc 1.2.0~DEVEL+20181216-1 has caused the Debian Bug report #916074, regarding pcc: useless without libpcc-dev to be marked as done. This means that you claim that the problem has been dealt

Bug#905674: parallel: move to nonfree

2019-01-08 Thread Ævar Arnfjörð Bjarmason
Package: parallel Followup-For: Bug #905674 Dear Maintainer, In fixing #905674 you've completely removed the 'parallel --citation' option from the package, which seems like overreach. Yes the default notification is spammy and I think Debian should remove it, it's not scalable that every

Processed: Re: Bug#917174: davmail: FTBFS with libjackrabbit-java 2.18.0

2019-01-08 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #917174 [davmail] davmail: FTBFS with libjackrabbit-java 2.18.0 Severity set to 'important' from 'serious' -- 917174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917174 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#917174: davmail: FTBFS with libjackrabbit-java 2.18.0

2019-01-08 Thread Markus Koschany
Control: severity -1 important Hi, I have reverted the change and uploaded the old 2.14.6 version of jackrabbit again. This will ensure that davmail also continues to work in Ubuntu and other distributions that sync packages directly from unstable. As I previously wrote davmail should be updated

Bug#916839: imagemagick: Silent ABI break in 6.9.10-11 on i386

2019-01-08 Thread Balint Reczey
Hi Bastien, On Mon, Jan 7, 2019 at 11:17 PM Bastien ROUCARIES wrote: > > Hi, > > I have uploaded a newer version fixing the problem. Could you ask > release team a rebuild. Thanks! I filed #918706 for the rebuilds, please follow up on it if needed. > > BTW could you get a glimpse at

Bug#916024: marked as done (pocl FTBFS: symbol differences)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 13:21:10 + with message-id and subject line Bug#916024: fixed in pocl 1.1-8 has caused the Debian Bug report #916024, regarding pocl FTBFS: symbol differences to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#917244: marked as done (FTBFS on armel: clang: error: the clang compiler does not support '-march=arm946e-s')

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 13:21:10 + with message-id and subject line Bug#917244: fixed in pocl 1.1-8 has caused the Debian Bug report #917244, regarding FTBFS on armel: clang: error: the clang compiler does not support '-march=arm946e-s' to be marked as done. This means that you

Bug#910856: sollya: test fails on most architectures

2019-01-08 Thread Jerome BENOIT
Thanks Adrian ! -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B signature.asc Description: OpenPGP digital signature

Processed: notfound 834298 in 3.17.1-3

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 834298 3.17.1-3 Bug #834298 {Done: Mark Brown } [nis] nis: Can't ypbind No longer marked as found in versions nis/3.17.1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 834298:

Bug#914986: marked as done (webkit2gtk: FTBFS on i386: ENABLE_SAMPLING_PROFILER conflicts with ENABLE_C_LOOP)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 15:21:46 + with message-id and subject line Bug#914986: fixed in webkit2gtk 2.23.2-1 has caused the Debian Bug report #914986, regarding webkit2gtk: FTBFS on i386: ENABLE_SAMPLING_PROFILER conflicts with ENABLE_C_LOOP to be marked as done. This means that

Bug#918669: marked as done (waitress FTBFS: An error happened in rendering the page api. Reason: TemplateNotFound())

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 15:21:07 + with message-id and subject line Bug#918669: fixed in waitress 1.2.0~b2-2 has caused the Debian Bug report #918669, regarding waitress FTBFS: An error happened in rendering the page api. Reason: TemplateNotFound() to be marked as done. This

Bug#918671: python-shade: Incomplete debian/copyright?

2019-01-08 Thread Chris Lamb
Source: python-shade Version: 1.30.0-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Clint Byrum , ftpmas...@debian.org Hi, I just ACCEPTed python-shade from NEW but noticed it was missing attribution in debian/copyright for at least OVH, IBM, Red Hat. This is in no way exhaustive

Processed: closing 846923

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 846923 1.7.0-4 Bug #846923 [src:mpb] mpb: FTBFS on mipsel - hanging on autconf test for BLAS zdotc Marked as fixed in versions mpb/1.7.0-4. Bug #846923 [src:mpb] mpb: FTBFS on mipsel - hanging on autconf test for BLAS zdotc Marked Bug as

Bug#882551: marked as done (python-shade FTBFS: test failures)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 10:00:11 + with message-id and subject line Bug#882551: fixed in python-shade 1.30.0-1 has caused the Debian Bug report #882551, regarding python-shade FTBFS: test failures to be marked as done. This means that you claim that the problem has been dealt

Bug#918673: libmath-mpfr-perl FTBFS on ppc*: subnormal_doubles.t fails

2019-01-08 Thread Adrian Bunk
Source: libmath-mpfr-perl Version: 4.05-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=libmath-mpfr-perl ... Invalid type 'D' in pack at t/subnormal_doubles.t line 63. t/subnormal_doubles.t 1..1 Dubious, test returned 255 (wstat 65280, 0xff00) Failed

Bug#843353: marked as done (python3-shade: fails to upgrade from 'testing' - trying to overwrite /usr/bin/shade-inventory)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 10:00:11 + with message-id and subject line Bug#843353: fixed in python-shade 1.30.0-1 has caused the Debian Bug report #843353, regarding python3-shade: fails to upgrade from 'testing' - trying to overwrite /usr/bin/shade-inventory to be marked as done.

Bug#918616: Bug #918616 in octave marked as pending

2019-01-08 Thread Sébastien Villemot
Control: tag -1 pending Hello, Bug #918616 in octave reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug #918616 in octave marked as pending

2019-01-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #918616 [src:octave] octave: missing build dependency on libglu1-mesa-dev Added tag(s) pending. -- 918616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#918676: r-cran-worrms: autopkgtest regression

2019-01-08 Thread Graham Inggs
Source: r-cran-worrms Version: 0.3.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since 2019-01-01, r-cran-worrms fails its autopkgtests with the following error: > library("testthat") > test_check("worrms") Loading required package: worrms

Bug#918411: marked as done (node-timed-out FTBFS with nodejs 10.15.0)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Jan 2019 11:29:03 +0100 with message-id and subject line Fixed has caused the Debian Bug report #918411, regarding node-timed-out FTBFS with nodejs 10.15.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#918653: marked as done (egl-wayland: misplaced Conflicts+Replaces)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 10:34:05 + with message-id and subject line Bug#918653: fixed in egl-wayland 1:1.1.1-2 has caused the Debian Bug report #918653, regarding egl-wayland: misplaced Conflicts+Replaces to be marked as done. This means that you claim that the problem has been

Bug#918654: marked as done (libnvidia-egl-wayland1: file installation conflict with nvidia-egl-wayland-common)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 10:34:05 + with message-id and subject line Bug#918654: fixed in egl-wayland 1:1.1.1-2 has caused the Debian Bug report #918654, regarding libnvidia-egl-wayland1: file installation conflict with nvidia-egl-wayland-common to be marked as done. This means

Bug#918554: marked as done (libodb-api-dev: missing dependency on libodb-api-bin)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Jan 2019 10:49:31 + with message-id and subject line Bug#918554: fixed in odb-api 0.18.1-3 has caused the Debian Bug report #918554, regarding libodb-api-dev: missing dependency on libodb-api-bin to be marked as done. This means that you claim that the problem has

Bug#910856: sollya: test fails on most architectures

2019-01-08 Thread Adrian Bunk
On Fri, Oct 12, 2018 at 03:33:41PM +0400, Jerome Benoit wrote: > Package: sollya > Version: 7.0+ds-2 > Severity: normal > Tags: upstream > > Dear Sollya enthusiasts ! > > It appears that tests fails randomly on most architectures. > The issue seems to be an AutoMake scripting issue.

Bug#918685: graphite2: FTBFS with test failures: awamicmp[123]

2019-01-08 Thread Andreas Beckmann
Source: graphite2 Version: 1.3.13-3 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, graphite2/experimental FTBFS on all architectures: https://buildd.debian.org/status/package.php?p=graphite2=experimental The following tests FAILED:

Processed: tagging 904808

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 904808 + patch Bug #904808 [libcap-ng0] libcap-ng0: libcap-ng's use of pthread_atfork causes segfaults Bug #914565 [libcap-ng0] php7.3-intl: Segfaults after apache2 graceful restart Added tag(s) patch. Added tag(s) patch. > thanks Stopping

Processed: affects 904808

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 904808 + libapache2-mod-authnz-pam Bug #904808 [libcap-ng0] libcap-ng0: libcap-ng's use of pthread_atfork causes segfaults Bug #914565 [libcap-ng0] php7.3-intl: Segfaults after apache2 graceful restart Added indication that 904808

Bug#858693: marked as done (congress-server: Missing dependency net-tools)

2019-01-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Jan 2019 09:12:34 +0100 with message-id and subject line Triaging: closing this bug has caused the Debian Bug report #858693, regarding congress-server: Missing dependency net-tools to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Watcher can actually build

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 918648 important Bug #918648 [src:watcher] watcher: FTBFS (autobuilder hangs) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 918648:

Bug#918648: watcher: FTBFS (autobuilder hangs)

2019-01-08 Thread Thomas Goirand
On 1/8/19 12:12 AM, Santiago Vila wrote: > severity 918648 serious > retitle 918648 watcher: FTBFS (autobuilder hangs) > thanks > > Hi. > > Unfortunately, my autobuilders still hang when I disable eatmydata, > and they do it all the time (100% reproducible). Retitling accordingly. > > Note that

Processed: forcibly merging 918579 916244

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 918579 916244 Bug #918579 [src:freeipa] freeipa: The node-uglify build dependency needs the same architecture list as the nodejs one Bug #916244 [src:freeipa] freeipa: Still depends on nodejs on all architectures Severity set to

Bug#918715: arptables: fails to remove if iptables haven't been installed

2019-01-08 Thread Adam Borowski
Package: arptables Version: 0.0.4+snapshot20181021-1 Severity: serious Hi! I'm afraid that the new prerm fails badly when there's no iptables, preventing the package from getting removed: Removing arptables (0.0.4+snapshot20181021-1) ... dpkg-query: no packages found matching iptables dpkg:

  1   2   >