Bug#905717: marked as done (spectre-meltdown-checker: new checks available)

Your message dated Sat, 11 Aug 2018 07:04:50 + with message-id and subject line Bug#905717: fixed in spectre-meltdown-checker 0.38-1 has caused the Debian Bug report #905717, regarding spectre-meltdown-checker: new checks available to be marked as done. This means that you claim that the

Bug#904004: marked as done (libgit2 FTBFS on armhf, ppc64el, mips64el randomly)

Your message dated Sat, 11 Aug 2018 07:04:35 + with message-id and subject line Bug#904004: fixed in libgit2 0.27.4+dfsg.1-0.1 has caused the Debian Bug report #904004, regarding libgit2 FTBFS on armhf, ppc64el, mips64el randomly to be marked as done. This means that you claim that the

Bug#905921: marked as done (hplip: hp-setup and hp-plugin fail to retrive key from keyserver and cannot get Laserjet1020 to work)

Your message dated Sat, 11 Aug 2018 22:45:25 +0100 with message-id <11082018223654.bc22d7615...@desktop.copernicus.org.uk> and subject line Re: Bug#905921: hplip: hp-setup and hp-plugin fail to retrive key from keyserver and cannot get Laserjet1020 to work has caused the Debian Bug report

Bug#897731: marked as done (cssc: ftbfs with GCC-8)

Your message dated Sat, 11 Aug 2018 23:03:57 + with message-id and subject line Bug#897731: fixed in cssc 1.4.0-6 has caused the Debian Bug report #897731, regarding cssc: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#905413: marked as done (libgamemode0-dev: missing Depends: libgamemode0 (= ${binary:Version}))

Your message dated Sat, 11 Aug 2018 10:04:19 + with message-id and subject line Bug#905413: fixed in gamemode 1.2-5 has caused the Debian Bug report #905413, regarding libgamemode0-dev: missing Depends: libgamemode0 (= ${binary:Version}) to be marked as done. This means that you claim that

Bug#905757: marked as done (python3-ldap3 fails to import on stretch)

Your message dated Sat, 11 Aug 2018 12:23:56 +0200 with message-id <20180811122356.33f0c...@monsterix.mbehrle.de> and subject line Re: python3-ldap3 fails to import on stretch has caused the Debian Bug report #905757, regarding python3-ldap3 fails to import on stretch to be marked as done. This

Bug#905884: marked as done (RFS: chafa/0.9.0+git20180731.5ddfe4c-1 [ITP])

Your message dated Sat, 11 Aug 2018 12:57:45 +0200 with message-id <20180811105745.6xpl43h4us6lb...@angband.pl> and subject line Re: Bug#905884: RFS: chafa/0.9.0+git20180731.5ddfe4c-1 [ITP] has caused the Debian Bug report #905884, regarding RFS: chafa/0.9.0+git20180731.5ddfe4c-1 [ITP] to be

Bug#888449: marked as done (curl: please conditionally disable libssh2 in Ubuntu)

Your message dated Sat, 11 Aug 2018 13:19:36 + with message-id and subject line Bug#888449: fixed in curl 7.61.0-1 has caused the Debian Bug report #888449, regarding curl: please conditionally disable libssh2 in Ubuntu to be marked as done. This means that you claim that the problem has

Bug#903546: marked as done (curl: CVE-2018-0500: SMTP send heap buffer overflow)

Your message dated Sat, 11 Aug 2018 13:19:36 + with message-id and subject line Bug#903546: fixed in curl 7.61.0-1 has caused the Debian Bug report #903546, regarding curl: CVE-2018-0500: SMTP send heap buffer overflow to be marked as done. This means that you claim that the problem has been

Bug#754591: marked as done (FTBFS with clang instead of gcc)

Your message dated Sat, 11 Aug 2018 13:49:55 + with message-id and subject line Bug#754591: fixed in simulavr 1.0.0+git20160221.e53413b-1 has caused the Debian Bug report #754591, regarding FTBFS with clang instead of gcc to be marked as done. This means that you claim that the problem has

Bug#659738: marked as done (simulavr: New version of simulavr is available)

Your message dated Sat, 11 Aug 2018 13:49:55 + with message-id and subject line Bug#522244: fixed in simulavr 1.0.0+git20160221.e53413b-1 has caused the Debian Bug report #522244, regarding simulavr: New version of simulavr is available to be marked as done. This means that you claim that

Bug#727966: marked as done (simulavr: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4)

Your message dated Sat, 11 Aug 2018 13:49:55 + with message-id and subject line Bug#727966: fixed in simulavr 1.0.0+git20160221.e53413b-1 has caused the Debian Bug report #727966, regarding simulavr: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4 to be marked as

Bug#522244: marked as done (Newer upstream version of simulavr is available)

Your message dated Sat, 11 Aug 2018 13:49:55 + with message-id and subject line Bug#522244: fixed in simulavr 1.0.0+git20160221.e53413b-1 has caused the Debian Bug report #522244, regarding Newer upstream version of simulavr is available to be marked as done. This means that you claim that

Bug#897860: marked as done (simulavr: ftbfs with GCC-8)

Your message dated Sat, 11 Aug 2018 13:49:55 + with message-id and subject line Bug#897860: fixed in simulavr 1.0.0+git20160221.e53413b-1 has caused the Debian Bug report #897860, regarding simulavr: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been

Bug#650947: marked as done (simulavr FTBFS if texlive-binaries, texi2html and texinfo are installed.)

Your message dated Sat, 11 Aug 2018 13:49:55 + with message-id and subject line Bug#650947: fixed in simulavr 1.0.0+git20160221.e53413b-1 has caused the Debian Bug report #650947, regarding simulavr FTBFS if texlive-binaries, texi2html and texinfo are installed. to be marked as done. This

Bug#744509: marked as done (simulavr: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4)

Your message dated Sat, 11 Aug 2018 13:49:55 + with message-id and subject line Bug#727966: fixed in simulavr 1.0.0+git20160221.e53413b-1 has caused the Debian Bug report #727966, regarding simulavr: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4 to be marked as

Bug#878252: marked as done (retroarch: New upstream version)

Your message dated Sat, 11 Aug 2018 09:04:33 + with message-id and subject line Bug#878252: fixed in retroarch 1.7.3+dfsg1-1 has caused the Debian Bug report #878252, regarding retroarch: New upstream version to be marked as done. This means that you claim that the problem has been dealt

Processed: control

Processing commands for cont...@bugs.debian.org: > close 905622 Bug #905622 [julia] julia 0.7.0~rc3 is available Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 905622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905622 Debian

Bug#905858: marked as done (osmosis build depends on libnetty-3.9-java)

Your message dated Sat, 11 Aug 2018 09:49:06 + with message-id and subject line Bug#905858: fixed in osmosis 0.46-6 has caused the Debian Bug report #905858, regarding osmosis build depends on libnetty-3.9-java to be marked as done. This means that you claim that the problem has been dealt

Bug#902462: marked as done (flask-restful: FTBFS in buster/sid (failing tests))

Your message dated Sat, 11 Aug 2018 10:19:03 + with message-id and subject line Bug#902462: fixed in flask-restful 0.3.6-6 has caused the Debian Bug report #902462, regarding flask-restful: FTBFS in buster/sid (failing tests) to be marked as done. This means that you claim that the problem

Bug#714344: marked as done (RFP: howler -- Alert when users log in from new locations)

Your message dated Sat, 11 Aug 2018 10:20:09 + with message-id and subject line closing RFP: howler -- Alert when users log in from new locations has caused the Debian Bug report #714344, regarding RFP: howler -- Alert when users log in from new locations to be marked as done. This means

Bug#905874: marked as done (libreoffice: No input of accented characters through dead-key composition)

Your message dated Sat, 11 Aug 2018 13:22:51 +0200 with message-id <2018082251.gg15...@rene-engelhard.de> and subject line Re: Bug#905874: libreoffice: No input of accented characters through dead-key composition has caused the Debian Bug report #905874, regarding libreoffice: No input of

Bug#905814: marked as done (geeqie: With GTK3, geeqie doesn't save the floating window configuration correctly)

Your message dated Sat, 11 Aug 2018 13:05:17 + with message-id and subject line Bug#905814: fixed in geeqie 1:1.4-8 has caused the Debian Bug report #905814, regarding geeqie: With GTK3, geeqie doesn't save the floating window configuration correctly to be marked as done. This means that

Bug#883174: marked as done (libcurl3: uses ca-certificates.crt rather than /etc/ssl/certs/ by default)

Your message dated Sat, 11 Aug 2018 13:19:36 + with message-id and subject line Bug#883174: fixed in curl 7.61.0-1 has caused the Debian Bug report #883174, regarding libcurl3: uses ca-certificates.crt rather than /etc/ssl/certs/ by default to be marked as done. This means that you claim

Bug#902628: marked as done (curl: segfaults with http2 on libcurl 7.60.0)

Your message dated Sat, 11 Aug 2018 13:19:36 + with message-id and subject line Bug#902628: fixed in curl 7.61.0-1 has caused the Debian Bug report #902628, regarding curl: segfaults with http2 on libcurl 7.60.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#903268: marked as done (hugin: autopkgtest checks write to $HOME and don't clean themselves)

Your message dated Sat, 11 Aug 2018 13:35:43 + with message-id and subject line Bug#903268: fixed in hugin 2018.0.0+dfsg-2 has caused the Debian Bug report #903268, regarding hugin: autopkgtest checks write to $HOME and don't clean themselves to be marked as done. This means that you claim

Bug#859157: marked as done (multipath-tools: after bootup multipathd timeout on commands - requires daemon restart)

Your message dated Sat, 11 Aug 2018 11:47:07 + with message-id and subject line Bug#859157: fixed in multipath-tools 0.6.4-5+deb9u1 has caused the Debian Bug report #859157, regarding multipath-tools: after bootup multipathd timeout on commands - requires daemon restart to be marked as done.

Bug#900936: marked as done (geoclue: Update to 2.4.10 breaks redshift)

Your message dated Sat, 11 Aug 2018 12:04:56 + with message-id and subject line Bug#900936: fixed in geoclue-2.0 2.4.11-1 has caused the Debian Bug report #900936, regarding geoclue: Update to 2.4.10 breaks redshift to be marked as done. This means that you claim that the problem has been

Bug#905875: marked as done (linux-image-amd64 outdated in jessie-backports)

Your message dated Sat, 11 Aug 2018 11:44:49 +0100 with message-id and subject line Re: Bug#905875: linux-image-amd64 outdated in jessie-backports has caused the Debian Bug report #905875, regarding linux-image-amd64 outdated in jessie-backports to be marked as done. This means that you claim

Bug#896340: marked as done (python-tofu: tofu fails to import)

Your message dated Sat, 11 Aug 2018 12:05:06 + with message-id and subject line Bug#896340: fixed in tofu 0.5-7 has caused the Debian Bug report #896340, regarding python-tofu: tofu fails to import to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#901912: marked as done (CVE-2018-11468 CVE-2018-11503 CVE-2018-11504 CVE-2018-12495)

Your message dated Sat, 11 Aug 2018 12:19:09 + with message-id and subject line Bug#901912: fixed in discount 2.2.4-1 has caused the Debian Bug report #901912, regarding CVE-2018-11468 CVE-2018-11503 CVE-2018-11504 CVE-2018-12495 to be marked as done. This means that you claim that the

Bug#905302: marked as done (New upstream version 1.2.1)

Your message dated Sat, 11 Aug 2018 12:33:54 + with message-id and subject line Bug#905302: fixed in cypari2 1.2.1-1 has caused the Debian Bug report #905302, regarding New upstream version 1.2.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#897732: marked as done (ctpp2: ftbfs with GCC-8)

Your message dated Sat, 11 Aug 2018 13:33:52 + with message-id and subject line Bug#897732: fixed in ctpp2 2.8.3-24 has caused the Debian Bug report #897732, regarding ctpp2: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#904958: marked as done (libssh: bad versioning)

Your message dated Sat, 11 Aug 2018 14:39:00 + with message-id and subject line Bug#904958: fixed in libssh 0.8.0-1 has caused the Debian Bug report #904958, regarding libssh: bad versioning to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: closing 902157

Processing commands for cont...@bugs.debian.org: > close 902157 0.8.0-1 Bug #902157 [src:libssh] libssh FTBFS on !le64bit: symbol differences Marked as fixed in versions libssh/0.8.0-1. Bug #902157 [src:libssh] libssh FTBFS on !le64bit: symbol differences Marked Bug as done > thanks Stopping

Bug#905111: marked as done (gnome-shell-extension-autohidetopbar: global.screen is not available in GNOME Shell 3.29)

Your message dated Sat, 11 Aug 2018 16:19:07 + with message-id and subject line Bug#905111: fixed in gnome-shell-extension-autohidetopbar 20180511-2 has caused the Debian Bug report #905111, regarding gnome-shell-extension-autohidetopbar: global.screen is not available in GNOME Shell 3.29

Bug#905384: marked as done (libmuscle1 provides libmuscle-3.7-1 but doesn't ship the library)

Your message dated Sat, 11 Aug 2018 20:12:32 +0300 with message-id <20180811171232.GK21565@localhost> and subject line This was fixed in 3.7+4565-5 has caused the Debian Bug report #905384, regarding libmuscle1 provides libmuscle-3.7-1 but doesn't ship the library to be marked as done. This means

Bug#897757: marked as done (gamera: ftbfs with GCC-8)

Your message dated Sat, 11 Aug 2018 14:37:12 + with message-id and subject line Bug#897757: fixed in gamera 1:3.4.2+git20160808.1725654-3 has caused the Debian Bug report #897757, regarding gamera: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been

Bug#875872: marked as done (libssh: parses libgcrypt version incorrectly)

Your message dated Sat, 11 Aug 2018 14:39:00 + with message-id and subject line Bug#875872: fixed in libssh 0.8.0-1 has caused the Debian Bug report #875872, regarding libssh: parses libgcrypt version incorrectly to be marked as done. This means that you claim that the problem has been dealt

Bug#748898: marked as done (lcalc: FTBFS with clang instead of gcc)

Your message dated Sat, 11 Aug 2018 14:38:41 + with message-id and subject line Bug#748898: fixed in lcalc 1.23+dfsg-7 has caused the Debian Bug report #748898, regarding lcalc: FTBFS with clang instead of gcc to be marked as done. This means that you claim that the problem has been dealt

Bug#567014: marked as done (multipath-tools-boot: dm-emc is history)

Your message dated Sat, 11 Aug 2018 17:01:04 +0200 with message-id <20180811150103.qabroskpirxe7...@percival.namespace.at> and subject line Re: Bug#567014: multipath-tools-boot: dm-emc is history has caused the Debian Bug report #567014, regarding multipath-tools-boot: dm-emc is history to be

Bug#760189: marked as done (kpartx: Should not include NEWS entry about systemd)

Your message dated Sat, 11 Aug 2018 17:08:48 +0200 with message-id <20180811150847.mu5gejapiybt7...@percival.namespace.at> and subject line Re: Bug#760189: kpartx: Should not include NEWS entry about systemd has caused the Debian Bug report #760189, regarding kpartx: Should not include NEWS entry

Processed: closing 902156

Processing commands for cont...@bugs.debian.org: > close 902156 0.8.0-1 Bug #902156 [src:libssh] libssh FTBFS on ppc*: Failed torture_keyfiles (Child aborted) Marked as fixed in versions libssh/0.8.0-1. Bug #902156 [src:libssh] libssh FTBFS on ppc*: Failed torture_keyfiles (Child aborted)

Bug#897801: marked as done (linbox: ftbfs with GCC-8)

Your message dated Sat, 11 Aug 2018 16:50:28 + with message-id and subject line Bug#897801: fixed in linbox 1.5.2-2 has caused the Debian Bug report #897801, regarding linbox: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#866110: marked as done (multipath-tools: mpathpersist segfaults. Newer version is available and fixed!)

Your message dated Sat, 11 Aug 2018 16:33:35 +0200 with message-id <20180811143334.kh5aawfapvgy2...@percival.namespace.at> and subject line Re: Bug#866110: multipath-tools: mpathpersist segfaults. Newer version is available and fixed! has caused the Debian Bug report #866110, regarding

Bug#775988: marked as done (kpartx: Incompatible libdevmapper $GARBAGE and kernel driver)

Your message dated Sat, 11 Aug 2018 16:41:04 +0200 with message-id <20180811144103.jy4g4pmrhbgru...@percival.namespace.at> and subject line Re: Bug#775988: kpartx: Incompatible libdevmapper $GARBAGE and kernel driver has caused the Debian Bug report #775988, regarding kpartx: Incompatible

Bug#862778: marked as done (Port from libnm-glib to libnm (or GNetworkMonitor))

Your message dated Sat, 11 Aug 2018 14:49:27 + with message-id and subject line Bug#862778: fixed in nis 3.17.1-2 has caused the Debian Bug report #862778, regarding Port from libnm-glib to libnm (or GNetworkMonitor) to be marked as done. This means that you claim that the problem has been

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

Your message dated Sat, 11 Aug 2018 15:36:57 + with message-id and subject line Bug#899712: fixed in torrus 3.00-1 has caused the Debian Bug report #899712, regarding torrus: Invalid maintainer address pkg-torrus-maintain...@lists.alioth.debian.org to be marked as done. This means that you

Bug#847024: marked as done (torrus: please make build reproducible (environment))

Your message dated Sat, 11 Aug 2018 15:36:57 + with message-id and subject line Bug#847024: fixed in torrus 3.00-1 has caused the Debian Bug report #847024, regarding torrus: please make build reproducible (environment) to be marked as done. This means that you claim that the problem has

Bug#905926: marked as done (squid-deb-proxy-client: ENETUNRECH on system with IPV6 and IPv4)

Your message dated Sat, 11 Aug 2018 16:38:49 -0300 with message-id and subject line PEBCAK - Firewall issue has caused the Debian Bug report #905926, regarding squid-deb-proxy-client: ENETUNRECH on system with IPV6 and IPv4 to be marked as done. This means that you claim that the problem has

Bug#726420: marked as done (multipath-tools: Fails to upgrade in root-on-multipath setups)

Your message dated Sat, 11 Aug 2018 21:43:02 +0200 with message-id <20180811194302.dtt6z66mworax...@percival.namespace.at> and subject line Re: #726420: multipath-tools: Fails to upgrade in root-on-multipath setups has caused the Debian Bug report #726420, regarding multipath-tools: Fails to

Bug#584145: marked as done (multipath-tools: udevd-work complains about device name differences)

Your message dated Sat, 11 Aug 2018 21:41:18 +0200 with message-id <20180811194118.m7bpofi6h7twm...@percival.namespace.at> and subject line Re: #584145: udevd-work complains about device name differences has caused the Debian Bug report #584145, regarding multipath-tools: udevd-work complains

Bug#905920: marked as done ((no subject))

Your message dated Sat, 11 Aug 2018 20:49:03 +0100 with message-id and subject line Re: Bug#905920: (no subject) has caused the Debian Bug report #905920, regarding (no subject) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#749436: marked as done (multipath-tools: Conflicting declarations of devt2devname shadow undefined behaviour)

Your message dated Sat, 11 Aug 2018 21:46:37 +0200 with message-id <20180811194637.bcg4svfgvwi2q...@percival.namespace.at> and subject line Re: #749436: multipath-tools: Conflicting declarations of devt2devname shadow undefined behaviour has caused the Debian Bug report #749436, regarding

Bug#827923: marked as done (multipath-tools: lintian errors and warnings)

Your message dated Sat, 11 Aug 2018 21:56:55 +0200 with message-id <20180811195655.5sgo75n6oa2ra...@percival.namespace.at> and subject line Re: #827923: multipath-tools: lintian errors and warnings has caused the Debian Bug report #827923, regarding multipath-tools: lintian errors and warnings to

Bug#843885: marked as done (installer broken: multipath-udeb depends on non-existent libgcc1 udeb)

Your message dated Sat, 11 Aug 2018 21:57:52 +0200 with message-id <20180811195752.vkpx6bpcsoies...@percival.namespace.at> and subject line Re: #843885: installer broken: multipath-udeb depends on non-existent libgcc1 udeb has caused the Debian Bug report #843885, regarding installer broken:

Bug#645247: marked as done (multipath-tools: output from `multipath -lld' does not separate fields)

Your message dated Sat, 11 Aug 2018 22:01:54 +0200 with message-id <20180811200154.rnwb6gbmwno3p...@percival.namespace.at> and subject line Re: Bug#645247: multipath-tools: output from `multipath -lld' does not separate fields has caused the Debian Bug report #645247, regarding multipath-tools:

Bug#591977: marked as done (kpartx: udev autostart + strict matching for removal == bad idea)

Your message dated Sat, 11 Aug 2018 22:04:03 +0200 with message-id <20180811200403.hzm7g57p6vled...@percival.namespace.at> and subject line Re: Bug#591977: kpartx: udev autostart + strict matching for removal == bad idea has caused the Debian Bug report #591977, regarding kpartx: udev autostart +

Bug#884979: marked as done (gcc-arm-none-eabi: Please indicate that a C++ compiler is included)

Your message dated Sat, 11 Aug 2018 20:37:09 + with message-id and subject line Bug#884979: fixed in gcc-arm-none-eabi 15:7-2018-q2-1 has caused the Debian Bug report #884979, regarding gcc-arm-none-eabi: Please indicate that a C++ compiler is included to be marked as done. This means that

Bug#904737: marked as done (uwsgi: FTBFS: unable to build gccgo plugin)

Your message dated Sat, 11 Aug 2018 20:38:31 + with message-id and subject line Bug#904737: fixed in uwsgi 2.0.17.1-2.1 has caused the Debian Bug report #904737, regarding uwsgi: FTBFS: unable to build gccgo plugin to be marked as done. This means that you claim that the problem has been

Bug#580892: marked as done (manual page is out-of-sync)

Your message dated Sat, 11 Aug 2018 20:49:19 + with message-id and subject line Bug#580892: fixed in keynav 0.20180421~git6505bd0d-1 has caused the Debian Bug report #580892, regarding manual page is out-of-sync to be marked as done. This means that you claim that the problem has been dealt

Bug#710765: marked as done (keynav: startsup on CTRL+, not on CTRL+; as advertised (depending on chosen keyboard layout))

Your message dated Sat, 11 Aug 2018 20:49:19 + with message-id and subject line Bug#710765: fixed in keynav 0.20180421~git6505bd0d-1 has caused the Debian Bug report #710765, regarding keynav: startsup on CTRL+, not on CTRL+; as advertised (depending on chosen keyboard layout) to be marked

Bug#796248: marked as done (keynav: Hyper not recognized in keynavrc)

Your message dated Sat, 11 Aug 2018 20:49:19 + with message-id and subject line Bug#796248: fixed in keynav 0.20180421~git6505bd0d-1 has caused the Debian Bug report #796248, regarding keynav: Hyper not recognized in keynavrc to be marked as done. This means that you claim that the problem

Bug#896617: marked as done (med-fichier: autopkgtest fails with new version of openmpi)

Your message dated Sat, 11 Aug 2018 23:08:46 +0200 with message-id <39ca2400-6fb4-3ba6-0093-62f27147c...@debian.org> and subject line Re: med-fichier: autopkgtest fails with new version of openmpi has caused the Debian Bug report #896617, regarding med-fichier: autopkgtest fails with new version

Bug#867858: marked as done (haskell-token-bucket FTBFS on armel: running 10+1 iterations with 10.0 Hz rate-limit FAILED)

Your message dated Sat, 11 Aug 2018 20:44:18 +0200 with message-id and subject line Re: haskell-token-bucket FTBFS on armel: running 10+1 iterations with 10.0 Hz rate-limit FAILED has caused the Debian Bug report #867858, regarding haskell-token-bucket FTBFS on armel: running 10+1 iterations

Bug#897724: marked as done (collectd: ftbfs with GCC-8)

Your message dated Sat, 11 Aug 2018 19:33:57 + with message-id and subject line Bug#897724: fixed in collectd 5.8.0-5.2 has caused the Debian Bug report #897724, regarding collectd: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#536644: marked as done (mdadm segfaults during initramfs boot, possibly dm related)

Your message dated Sat, 11 Aug 2018 21:34:19 +0200 with message-id <20180811193419.fauma4f2tejbs...@percival.namespace.at> and subject line Re: #536644: mdadm segfaults during initramfs boot, possibly dm related has caused the Debian Bug report #536644, regarding mdadm segfaults during initramfs

Bug#843953: marked as done (multipath-tools: LVM on internal disks + multipath-toosl = no multipaths)

Your message dated Sat, 11 Aug 2018 21:37:23 +0200 with message-id <20180811193723.tp3f7jcaa2mab...@percival.namespace.at> and subject line Re: #843953: multipath-tools: LVM on internal disks + multipath-toosl = no multipaths has caused the Debian Bug report #843953, regarding multipath-tools:

Bug#880146: marked as done (cvc4: FTBFS on non-x86: test suite errors)

Your message dated Sat, 11 Aug 2018 20:10:34 + with message-id and subject line Bug#880146: fixed in cvc4 1.6-1 has caused the Debian Bug report #880146, regarding cvc4: FTBFS on non-x86: test suite errors to be marked as done. This means that you claim that the problem has been dealt with.

Bug#868409: marked as done (verbiste: Please drop the (build-)dependency against gnome-vfs)

Your message dated Sat, 11 Aug 2018 20:10:39 + with message-id and subject line Bug#868409: fixed in verbiste 0.1.45-2 has caused the Debian Bug report #868409, regarding verbiste: Please drop the (build-)dependency against gnome-vfs to be marked as done. This means that you claim that the

Bug#880147: marked as done (cvc4: FTBFS on sparc64: bus error => massive test suite failure)

Your message dated Sat, 11 Aug 2018 20:10:34 + with message-id and subject line Bug#880147: fixed in cvc4 1.6-1 has caused the Debian Bug report #880147, regarding cvc4: FTBFS on sparc64: bus error => massive test suite failure to be marked as done. This means that you claim that the problem

Bug#751993: marked as done (multipath-tools: multipath -l segfaults (and multipath not working))

Your message dated Sat, 11 Aug 2018 22:14:59 +0200 with message-id <20180811201459.npsu5hkxy47ej...@percival.namespace.at> and subject line Re: #751993: multipath-tools: multipath -l segfaults (and multipath not working) has caused the Debian Bug report #751993, regarding multipath-tools:

Bug#799781: marked as done (device lock race condition between udev and multipathd may cause systemd to abort system boot)

Your message dated Sat, 11 Aug 2018 22:16:19 +0200 with message-id <20180811201619.2b7vatnxtovz4...@percival.namespace.at> and subject line Re: #799781: device lock race condition between udev and multipathd may cause systemd to abort system boot has caused the Debian Bug report #799781,

Bug#795088: marked as done (multipath-tools: systemd script vs sysv init script)

Your message dated Sat, 11 Aug 2018 22:19:39 +0200 with message-id <20180811201939.6alsxr7imttae...@percival.namespace.at> and subject line Re: #795088: multipath-tools: systemd script vs sysv init script has caused the Debian Bug report #795088, regarding multipath-tools: systemd script vs sysv

Bug#777462: marked as done (kpartx_id generates wrong WWN)

Your message dated Sat, 11 Aug 2018 22:54:34 +0200 with message-id <20180811205433.wcfimockjbzdc...@percival.namespace.at> and subject line Re: Bug#777462: kpartx_id generates wrong WWN has caused the Debian Bug report #777462, regarding kpartx_id generates wrong WWN to be marked as done. This

Bug#580312: marked as done (multipath-tools: multipathd segfaults when restarted)

Your message dated Sun, 12 Aug 2018 02:12:36 +0200 with message-id <20180812001236.hetsbbag4c34g...@percival.namespace.at> and subject line Re: Bug#580312: multipath-tools: multipathd segfaults when restarted has caused the Debian Bug report #580312, regarding multipath-tools: multipathd

Bug#814670: marked as done (login: su - clears XDG_RUNTIME_DIR)

Your message dated Sun, 12 Aug 2018 06:10:22 +0200 with message-id <20180812041022.3uaqredribk53...@fatal.se> and subject line Re: Possible fix for su - / su -l and XDG_RUNTIME_DIR has caused the Debian Bug report #814670, regarding login: su - clears XDG_RUNTIME_DIR to be marked as done. This

Bug#905409: marked as done (util-linux: "su -" no longer copies DISPLAY and XAUTHORITY to child, but this is not documented)

Your message dated Sun, 12 Aug 2018 05:49:08 + with message-id and subject line Bug#905409: fixed in util-linux 2.32.1-0.1 has caused the Debian Bug report #905409, regarding util-linux: "su -" no longer copies DISPLAY and XAUTHORITY to child, but this is not documented to be marked as done.

Bug#905710: marked as done (util-linux: "su: revoking keys needs to be documented')

Your message dated Sun, 12 Aug 2018 05:49:08 + with message-id and subject line Bug#905710: fixed in util-linux 2.32.1-0.1 has caused the Debian Bug report #905710, regarding util-linux: "su: revoking keys needs to be documented' to be marked as done. This means that you claim that the

Bug#903168: marked as done (backupninja: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

Your message dated Sun, 12 Aug 2018 02:34:14 + with message-id and subject line Bug#903168: fixed in backupninja 1.1.0-2 has caused the Debian Bug report #903168, regarding backupninja: FTBFS in buster/sid (dh_installdocs: Cannot find "README") to be marked as done. This means that you

Bug#905478: marked as done (util-linux: su from util-linux: no reason why su without setting new environment is bad idea)

Your message dated Sun, 12 Aug 2018 07:34:25 +0200 with message-id <20180812053425.kjwuhfj25k3u4...@fatal.se> and subject line Re: Fwd: Re: Debian´s change of "su" to the one in util-linux has caused the Debian Bug report #905478, regarding util-linux: su from util-linux: no reason why su without

Processed: closing 903509, closing 903508

Processing commands for cont...@bugs.debian.org: > close 903509 0.27.4+dfsg.1-0.1 Bug #903509 [src:libgit2] libgit2: CVE-2018-10887: integer overflow leads to out-of-bounds read in git_delta_apply, allowing to read before base array Marked as fixed in versions libgit2/0.27.4+dfsg.1-0.1. Bug