Bug#911514: closing 911514

close 911514 5.0.0.2801-2~bpo9+1 thanks

Processed: closing 911514

Processing commands for cont...@bugs.debian.org: > close 911514 5.0.0.2801-2~bpo9+1 Bug #911514 [davmail] davmail: fails to install: wrong update-rc.d usage Marked as fixed in versions davmail/5.0.0.2801-2~bpo9+1. Bug #911514 [davmail] davmail: fails to install: wrong update-rc.d usage Marked Bug

Bug#918769: ocaml-migrate-parsetree FTBFS:dh_install fails

Source: ocaml-migrate-parsetree Version: 1.2.0-1 Severity: serious Tags: ftbfs ocaml-migrate-parsetree fails to build on sid using debhelper version 12 (12 is the version of the debhelper package, I haven't touched the DH compat level) : dh_install: libmigrate-parsetree-ocamlbuild-ocaml missing f

Bug#918768: opencolorio FTBFS with yaml-cpp 0.6.2

Source: opencolorio Version: 1.1.0~dfsg0-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/opencolorio.html ... /usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/build/1st/opencolorio-1.1.0~dfsg0=. -fstack-protector-strong -Wformat -Werror=format-secu

Bug#918767: rivet FTBFS with yaml-cpp 0.6.2

Source: rivet Version: 1.8.3-2 Severity: serious Tags: ftbfs patch https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rivet.html ... In file included from /usr/include/c++/8/array:35, from /usr/include/yaml-cpp/node/convert.h:10, from /usr/include

Processed: Bug #917715 in openconnect marked as pending

Processing control commands: > tag -1 pending Bug #917715 [src:openconnect] openconnect: FTBFS: dh_auto_test: make -j2 check VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 917715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917715 Debian Bug Tracking System Contact ow...@bugs.deb

Bug#917715: Bug #917715 in openconnect marked as pending

Control: tag -1 pending Hello, Bug #917715 in openconnect 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/debian/openconnect/commit/44cb37cd3f82e52b09306fa8298b

Bug#918569: Could not find 'activerecord' (~> 4.2) - did find: [activerecord-5.2.0]

On Mon, 07 Jan 2019 22:39:41 +0100 t...@schleuder.org wrote: > > Upstream (aka us) is working on switching to activerecord 5.2: > https://0xacab.org/schleuder/schleuder/issues/372 Hi paz, Would it be possible to upload a release candidate/dev version right now to help with rails transition? You

Processed: forcibly merging 913789 913765

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.

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

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. Th

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

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 g

Processed: found 907414 in 3.3.7+dfsg-3

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 archi

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

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 12

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

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 cosmic-u

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

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#917857: NMU diff for aufs 4.19+20181217-0.1

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 up-to

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

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 h

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

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 with

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

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 problem

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

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 pr

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

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 d

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

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#820231: marked as done (ttf-marvosym: Consider to remove your package)

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 b

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

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 bee

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

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 previousl

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

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: https://salsa.debian.org/gnome-team/gnome-settings-daemon/commit/aec0

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)')

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&, asio::ssl::conte

Bug#918751: python-shade: FTBFS in sid

I said: > I tried to build this package in buster but it failed: Sorry for this typo, I meant sid of course.

Bug#918751: python-shade: FTBFS in sid

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#829255: marked as done (oss4-dkms: Fails to build for 4.6.0-1-amd64)

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 d

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

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#916005: marked as done (oss4 FTBFS with glibc 2.28)

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 thi

Processed: tagging 918741

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: https://bugs.debi

Processed: tagging 918742

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: https://bugs.debian.

Bug#918746: Should this package be removed?

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 th

Bug#915804: Should this package be removed?

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 w

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

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 packa

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

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: ba

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

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 tha

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

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 package

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

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 remov

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

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

Processed: tagging 916005

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 Debian

Bug#918739: node-duplexer2 FTBFS with nodejs 10.15.0

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 interac

Processed: Bug #917633 in systemd marked as pending

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

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: https://salsa.debian.org/systemd-team/systemd/commit/b89ae41a352f37f60918fb65efd6f7

Processed: found 917925 in 2013.08.08-5

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: htt

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

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)

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 a

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

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

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 l

Bug#917633: Also blocks migration of tails-installer

Hello! this issue currently also blocks the migration of tails-installer, shortly before the freeze. Cheers! u.

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

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: libppx-deriving-ocaml-

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

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: mak

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

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 LD_LIBRARY_PATH=/<>/caffe-1.0.0\+git20180821.99bd997/caffe_cpu_build

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

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 ow...@bugs.deb

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

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 CMakeFiles

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

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#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

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 https://salsa.debian.org/mariadb-team/mari

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

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#917745: cross-toolchain-base: FTBFS: applying patches fails

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 / 4.18.20

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

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 promise

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

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#918157: marked as done (libpmix2 seems broken on 32 bits architectures)

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 de

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

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#918685: marked as done (graphite2: FTBFS with test failures: awamicmp[123])

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 b

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

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 ha

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

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 did

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

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: https://salsa.debian.org/libreoffice-team/graphite2/commit/ec2bd84a2fe513efa6f038

Processed: Bug #918685 in graphite2 marked as pending

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#894202: marked as done (rdkit FTBFS on 32bit: test hang)

Your message dated Tue, 08 Jan 2019 18:00:16 + with message-id and subject line Bug#894202: fixed in rdkit 201803.4+dfsg-2 has caused the Debian Bug report #894202, regarding rdkit FTBFS on 32bit: test hang to be marked as done. This means that you claim that the problem has been dealt with.

Processed: bug 918685 is forwarded to https://github.com/silnrsi/graphite/issues/49

Processing commands for cont...@bugs.debian.org: > forwarded 918685 https://github.com/silnrsi/graphite/issues/49 Bug #918685 [src:graphite2] graphite2: FTBFS with test failures: awamicmp[123] Set Bug forwarded-to-address to 'https://github.com/silnrsi/graphite/issues/49'. > thanks Stopping proces

Processed: fixed 915679 in 1.2.0~DEVEL+20181202-1

Processing commands for cont...@bugs.debian.org: > fixed 915679 1.2.0~DEVEL+20181202-1 Bug #915679 {Done: Yangfl } [pcc] pcc: broken symlinks on i386: /usr/bin/x86_64-linux-gnu-p* -> x86_64-linux-gnu-pcc Marked as fixed in versions pcc/1.2.0~DEVEL+20181202-1. > thanks Stopping processing here. P

Processed: tagging 917686

Processing commands for cont...@bugs.debian.org: > tags 917686 + help Bug #917686 [src:lightproof] lightproof: FTBFS: "zipfile is empty" with python 3.7 ("Key Error") Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 917686: https://bugs.debian.o

Processed: Bug #894202 in rdkit marked as pending

Processing control commands: > tag -1 pending Bug #894202 [src:rdkit] rdkit FTBFS on 32bit: test hang Added tag(s) pending. -- 894202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#894202: Bug #894202 in rdkit marked as pending

Control: tag -1 pending Hello, Bug #894202 in rdkit 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/rdkit/commit/aa0d8bb34b21038d01bdcc4c2121423ae

Bug#918648: watcher: FTBFS (autobuilder hangs)

On 1/8/19 3:20 PM, Adrian Bunk wrote: > On Tue, Jan 08, 2019 at 02:38:47PM +0100, Santiago Vila wrote: >> ... >> I see you have downgraded this from serious, but Release Policy says >> packages must build without failure. Could you please tell me >> in which sense this: >> >> https://tests.reproduc

Processed: severity 918648 important

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: https://bugs.debian.org/cgi

Bug#917726: globus-gass-copy: FTBFS: tests failed

On 08/01/19 at 10:16 +0100, Mattias Ellert wrote: > mån 2019-01-07 klockan 09:20 +0100 skrev Lucas Nussbaum: > > Hi, > > > > On 07/01/19 at 08:28 +0100, Mattias Ellert wrote: > > > Hi! > > > > > > The globus-gass-copy package and dependent packaged have now been > > > tagged for autoremoval due t

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

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: error

Bug#918713: libopenmpi3: test failure triggered by mca_pmix_pmix2x.so: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version

Package: libopenmpi3 Version: 3.1.3-8 Severity: serious Justification: Policy 8.6 openmpi 3.1.3-8 is triggering test failure on a wide range of client packages, including combblas, dolfin and family, petsc and family, superlu-dist. dolfin and petsc (etc) leave a record of the fault, e.g. petsc h

Bug#918575: marked as done (abyss FTBFS on 32bit big endian: test failures)

Your message dated Tue, 08 Jan 2019 16:04:01 + with message-id and subject line Bug#918575: fixed in abyss 2.1.5-2 has caused the Debian Bug report #918575, regarding abyss FTBFS on 32bit big endian: test failures to be marked as done. This means that you claim that the problem has been dealt

Bug#911507: offlineimap: fails to load imaplib2

Hi, On Sun, Oct 21, 2018 at 08:50AM, Hans-Joachim wrote: > Dear Maintainer, > > calling offlineimap stops reporting > > Error while trying to import system imaplib2: name '__revision__' is not > defined > Traceback (most recent call last): > File "/usr/bin/offlineimap", line 20, in > fro

Processed: Re: Bug#918648: watcher: FTBFS (autobuilder hangs)

Processing control commands: > clone -1 -2 Bug #918648 [src:watcher] watcher: FTBFS (autobuilder hangs) Bug 918648 cloned as bug 918712 > retitle -2 watcher FTBFS in some timezones Bug #918712 [src:watcher] watcher: FTBFS (autobuilder hangs) Changed Bug title to 'watcher FTBFS in some timezones' f

Bug#913346: libsane1: Cannot update libsane1

Control: severity -1 normal On 1/8/19 4:26 PM, John Paul Adrian Glaubitz wrote: > It's not serious for Debian since the package never entered testing in > the first place. Adjusting severity accordingly. Please don't set the severity to serious unless providing a reference to the corresponding c

Processed: Re: libsane1: Cannot update libsane1

Processing control commands: > severity -1 normal Bug #913346 [sane-backends] libsane1: Cannot update libsane1 Severity set to 'normal' from 'serious' -- 913346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#913346: libsane1: Cannot update libsane1

Hello! On 1/3/19 11:51 PM, Jeremy Bicha wrote: > This issue is more serious for Ubuntu which will need to keep a > libsane1 transitional package around until after 20.04 LTS. It's not serious for Debian since the package never entered testing in the first place. > I've prepared an NMU for sane-b

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

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())

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 mean

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

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 w

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

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 th

Processed: jemalloc: third time's the charm?

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

Processed: notfound 834298 in 3.17.1-3

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: https://bugs.debian.org/

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

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

Bug#910856: sollya: test fails on most architectures

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

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

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 ruby-mini-m

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

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

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

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 pr

Bug#905674: parallel: move to nonfree

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 program

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

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

  1   2   >