Bug#878674: marked as done (nodejs segfaults when building d3-* with webpack)

Your message dated Sun, 7 Jan 2018 12:53:48 +0530 with message-id and subject line Re: Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack has caused the Debian Bug report #878674, regarding nodejs segfaults when building d3-* with webpack t

Bug#886106: marked as done (leiningen: Short description not very descriptive)

Your message dated Sun, 07 Jan 2018 06:04:01 + with message-id and subject line Bug#886106: fixed in leiningen-clojure 2.8.1-4 has caused the Debian Bug report #886106, regarding leiningen: Short description not very descriptive to be marked as done. This means that you claim that the problem

Bug#857277: marked as done (Segmentation fault by use of "call" inside "later")

Your message dated Sun, 07 Jan 2018 05:34:07 + with message-id and subject line Bug#857277: fixed in picolisp 17.12-1 has caused the Debian Bug report #857277, regarding Segmentation fault by use of "call" inside "later" to be marked as done. This means that you claim that the problem has bee

Bug#871515: marked as done (picolisp: Please add arm64)

Your message dated Sun, 07 Jan 2018 05:34:07 + with message-id and subject line Bug#871515: fixed in picolisp 17.12-1 has caused the Debian Bug report #871515, regarding picolisp: Please add arm64 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#862851: marked as done (vblade-persist: Please switch to iproute2 package)

Your message dated Sun, 07 Jan 2018 04:19:05 + with message-id and subject line Bug#862851: fixed in vblade-persist 0.6-3 has caused the Debian Bug report #862851, regarding vblade-persist: Please switch to iproute2 package to be marked as done. This means that you claim that the problem has

Bug#867768: marked as done (certbot: Fails to renew certs when a sytem call is interrupted)

Your message dated Sat, 6 Jan 2018 22:13:08 -0500 with message-id and subject line Re: certbot: Fails to renew certs when a sytem call is interrupted has caused the Debian Bug report #867768, regarding certbot: Fails to renew certs when a sytem call is interrupted to be marked as done. This mea

Bug#878650: marked as done (python-certbot: python3 support)

Your message dated Sat, 6 Jan 2018 22:05:11 -0500 with message-id and subject line Re: python-certbot: python3 support has caused the Debian Bug report #878650, regarding python-certbot: python3 support to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#886467: marked as done (RFS: igmpproxy/0.2-1)

Your message dated Sun, 7 Jan 2018 02:30:48 +0100 with message-id <20180107013048.4lnqxgok2nif3...@angband.pl> and subject line Re: Bug#886467: RFS: igmpproxy/0.2-1 has caused the Debian Bug report #886467, regarding RFS: igmpproxy/0.2-1 to be marked as done. This means that you claim that the pro

Bug#886469: marked as done (RFS: stormlib/9.22-1)

Your message dated Sun, 7 Jan 2018 02:25:16 +0100 with message-id <20180107012515.7anuhm75ikqxs...@angband.pl> and subject line Re: Bug#886469: RFS: stormlib/9.22-1 has caused the Debian Bug report #886469, regarding RFS: stormlib/9.22-1 to be marked as done. This means that you claim that the pro

Bug#886503: marked as done (wildmidi: CVE-2017-1000418)

Your message dated Sun, 07 Jan 2018 00:22:36 + with message-id and subject line Bug#886503: fixed in wildmidi 0.4.2-1 has caused the Debian Bug report #886503, regarding wildmidi: CVE-2017-1000418 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#871616: marked as done (CVE-2017-11661 CVE-2017-11662 CVE-2017-11663 CVE-2017-11664)

Your message dated Sun, 07 Jan 2018 00:22:36 + with message-id and subject line Bug#871616: fixed in wildmidi 0.4.2-1 has caused the Debian Bug report #871616, regarding CVE-2017-11661 CVE-2017-11662 CVE-2017-11663 CVE-2017-11664 to be marked as done. This means that you claim that the proble

Bug#886238: marked as done (Please introduce official nosystemd build profile)

Your message dated Sun, 7 Jan 2018 00:59:24 +0100 with message-id <20180106235924.evasx5ptotiic...@shell.thinkmo.de> and subject line Re: [Fwd: Bug#886238: marked as done (Please introduce official nosystemd build profile)] has caused the Debian Bug report #886238, regarding Please introduce offic

Bug#886493: marked as done (general: debian should support nosystemd build profile)

Your message dated Sun, 7 Jan 2018 00:59:24 +0100 with message-id <20180106235924.evasx5ptotiic...@shell.thinkmo.de> and subject line Re: [Fwd: Bug#886238: marked as done (Please introduce official nosystemd build profile)] has caused the Debian Bug report #886238, regarding general: debian should

Bug#884867: marked as done (libspreadsheet-read-perl: depends on Spreadsheet::ReadSXC, which is being packaged as libspreadsheet-readsxc-perl)

Your message dated Sat, 06 Jan 2018 23:52:34 + with message-id and subject line Bug#884867: fixed in libspreadsheet-read-perl 0.76-1 has caused the Debian Bug report #884867, regarding libspreadsheet-read-perl: depends on Spreadsheet::ReadSXC, which is being packaged as libspreadsheet-readsxc

Processed: merge 886470 886505

Processing commands for cont...@bugs.debian.org: > close 886505 Bug #886505 [nvidia-kernel-dkms] nvidia-kernel-dkms: fails to work with linux-image-4.14.0-3-amd64 Marked Bug as done > merge 886470 886505 Bug #886470 {Done: Luca Boccassi } [nvidia-kernel-dkms] nvidia-kernel-dkms: FTBFS against li

Processed: forcemerge

Processing commands for cont...@bugs.debian.org: > unarchive 853462 Bug #853462 {Done: Matthias Klose } [src:json-c] json-c: ftbfs with GCC-7 Unarchived Bug 853462 > forcemerge 853462 886489 Bug #853462 {Done: Matthias Klose } [src:json-c] json-c: ftbfs with GCC-7 Bug #853462 {Done: Matthias Klo

Bug#883987: marked as done (FTBFS error: partial specialization ... after instantiation ... (with patch))

Your message dated Sat, 06 Jan 2018 22:05:02 + with message-id and subject line Bug#883987: fixed in boost1.62 1.62.0+dfsg-5 has caused the Debian Bug report #883987, regarding FTBFS error: partial specialization ... after instantiation ... (with patch) to be marked as done. This means that

Bug#884185: marked as done (FTBFS error: partial specialization ... after instantiation ... (with patch))

Your message dated Sat, 06 Jan 2018 22:05:02 + with message-id and subject line Bug#883987: fixed in boost1.62 1.62.0+dfsg-5 has caused the Debian Bug report #883987, regarding FTBFS error: partial specialization ... after instantiation ... (with patch) to be marked as done. This means that

Bug#884184: marked as done (FTBFS error: partial specialization ... after instantiation ... (with patch))

Your message dated Sat, 06 Jan 2018 22:05:02 + with message-id and subject line Bug#883987: fixed in boost1.62 1.62.0+dfsg-5 has caused the Debian Bug report #883987, regarding FTBFS error: partial specialization ... after instantiation ... (with patch) to be marked as done. This means that

Bug#761272: marked as done (dh-systemd: deb-systemd-invoke stop not protected by || true)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#761272: fixed in debhelper 11.1 has caused the Debian Bug report #761272, regarding dh-systemd: deb-systemd-invoke stop not protected by || true to be marked as done. This means that you claim that the problem

Bug#885998: marked as done (debhelper: in compat 11, systemd-tmpfiles is no longer run before invoke-rc.d)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#885998: fixed in debhelper 11.1 has caused the Debian Bug report #885998, regarding debhelper: in compat 11, systemd-tmpfiles is no longer run before invoke-rc.d to be marked as done. This means that you clai

Bug#886127: marked as done (debhelper: Break cmake < 3.8.0 instead of documenting this a caveat)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#886127: fixed in debhelper 11.1 has caused the Debian Bug report #886127, regarding debhelper: Break cmake < 3.8.0 instead of documenting this a caveat to be marked as done. This means that you claim that the

Bug#884556: marked as done (debhelper: dh_missing - support wildcards in d/not-installed)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#884556: fixed in debhelper 11.1 has caused the Debian Bug report #884556, regarding debhelper: dh_missing - support wildcards in d/not-installed to be marked as done. This means that you claim that the problem

Bug#884574: marked as done (debhelper: fix typo)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#884574: fixed in debhelper 11.1 has caused the Debian Bug report #884574, regarding debhelper: fix typo to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#886037: marked as done (debhelper: dh_strip: do not try to strip ELF files in /usr/lib/debug/.build-id/)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#886037: fixed in debhelper 11.1 has caused the Debian Bug report #886037, regarding debhelper: dh_strip: do not try to strip ELF files in /usr/lib/debug/.build-id/ to be marked as done. This means that you cl

Bug#886038: marked as done (debhelper: duplicates in the Build-Ids list)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#886038: fixed in debhelper 11.1 has caused the Debian Bug report #886038, regarding debhelper: duplicates in the Build-Ids list to be marked as done. This means that you claim that the problem has been dealt w

Bug#814285: marked as done (debhelper: configuration handling (e.g. from dh_ucf/dh_installdeb maintscript) should happen before dh_installinit's (etc.) start of services)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#814285: fixed in debhelper 11.1 has caused the Debian Bug report #814285, regarding debhelper: configuration handling (e.g. from dh_ucf/dh_installdeb maintscript) should happen before dh_installinit's (etc.) s

Bug#880840: marked as done (debhelper: build makefile rule does not replace dh build sequence)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#880840: fixed in debhelper 11.1 has caused the Debian Bug report #880840, regarding debhelper: build makefile rule does not replace dh build sequence to be marked as done. This means that you claim that the pr

Bug#858834: marked as done (debhelper: make dh_missing --list-missing the default)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#858834: fixed in debhelper 11.1 has caused the Debian Bug report #858834, regarding debhelper: make dh_missing --list-missing the default to be marked as done. This means that you claim that the problem has be

Bug#593382: marked as done (dh_compress: please do not compress Python source files in doc dir)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#593382: fixed in debhelper 11.1 has caused the Debian Bug report #593382, regarding dh_compress: please do not compress Python source files in doc dir to be marked as done. This means that you claim that the p

Bug#873831: marked as done (debhelper: [meson] Default to a UTF8 locale?)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#873831: fixed in debhelper 11.1 has caused the Debian Bug report #873831, regarding debhelper: [meson] Default to a UTF8 locale? to be marked as done. This means that you claim that the problem has been dealt

Bug#650129: marked as done (Make --list-missing switch of dh_install the default for multiple-binary source packages)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#650129: fixed in debhelper 11.1 has caused the Debian Bug report #650129, regarding Make --list-missing switch of dh_install the default for multiple-binary source packages to be marked as done. This means th

Bug#653640: marked as done (dh_makeshlibs generates symbols files for objects excluded from shlibs)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#653640: fixed in debhelper 11.1 has caused the Debian Bug report #653640, regarding dh_makeshlibs generates symbols files for objects excluded from shlibs to be marked as done. This means that you claim that t

Bug#709384: marked as done (dh_installinit: Please add an option to no enable the service at installation)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#709384: fixed in debhelper 11.1 has caused the Debian Bug report #709384, regarding dh_installinit: Please add an option to no enable the service at installation to be marked as done. This means that you clai

Bug#570935: marked as done (debhelper: possibility to enable an addon with an environment variable)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#570935: fixed in debhelper 11.1 has caused the Debian Bug report #570935, regarding debhelper: possibility to enable an addon with an environment variable to be marked as done. This means that you claim that t

Bug#566861: marked as done (dh_clean breaks mercurial)

Your message dated Sat, 06 Jan 2018 21:34:07 + with message-id and subject line Bug#566861: fixed in debhelper 11.1 has caused the Debian Bug report #566861, regarding dh_clean breaks mercurial to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Processed: Re: Bug#882795: closed by Sébastien Villemot (Bug#882795: fixed in cltl 1.0.28)

Processing commands for cont...@bugs.debian.org: > close 882795 Bug #882795 [cltl] cltl: [INTL:de] updated German debconf translation Marked Bug as done > close 881407 Bug #881407 [cltl] cltl: [INTL:nl] Dutch translation of debconf messages Marked Bug as done > thanks Stopping processing here. Pl

Bug#885906: marked as done (ITP: piu-piu -- Horizontal scroller game in bash for cli)

Your message dated Sat, 06 Jan 2018 21:00:10 + with message-id and subject line Bug#885906: fixed in piu-piu 1.0-1 has caused the Debian Bug report #885906, regarding ITP: piu-piu -- Horizontal scroller game in bash for cli to be marked as done. This means that you claim that the problem has

Bug#885925: marked as done ([L10N,DE] nvidia-graphics-drivers: updated german debconf translation)

Your message dated Sat, 06 Jan 2018 20:54:02 + with message-id and subject line Bug#885925: fixed in nvidia-graphics-drivers 384.111-1 has caused the Debian Bug report #885925, regarding [L10N,DE] nvidia-graphics-drivers: updated german debconf translation to be marked as done. This means tha

Bug#886005: marked as done (nvidia-graphics-drivers: [INTL:ru] Updated Russian translation of debconf template)

Your message dated Sat, 06 Jan 2018 20:54:02 + with message-id and subject line Bug#886005: fixed in nvidia-graphics-drivers 384.111-1 has caused the Debian Bug report #886005, regarding nvidia-graphics-drivers: [INTL:ru] Updated Russian translation of debconf template to be marked as done.

Bug#876668: marked as done (postinst is inconsistent)

Your message dated Sat, 06 Jan 2018 20:51:52 + with message-id and subject line Bug#876668: fixed in kopano-webapp 3.4.3+dfsg1-1 has caused the Debian Bug report #876668, regarding postinst is inconsistent to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#886457: marked as done (psi-plus: Segfault after hibernation)

Your message dated Sat, 06 Jan 2018 23:36:39 +0300 with message-id <551201515270...@web11g.yandex.ru> and subject line Re: Bug#886457: psi-plus: Segfault after hibernation has caused the Debian Bug report #886457, regarding psi-plus: Segfault after hibernation to be marked as done. This means that

Processed: forcibly merging 886238 886493

Processing commands for cont...@bugs.debian.org: > forcemerge 886238 886493 Bug #886238 {Done: Bastian Blank } [general] Please introduce official nosystemd build profile Bug #886493 [general] general: debian should support nosystemd build profile Severity set to 'wishlist' from 'normal' Marked B

Bug#886488: marked as done (cinnamon: Font rendering issue)

Your message dated Sat, 6 Jan 2018 13:35:42 -0500 with message-id <6b4888e1-98c0-993b-8e69-a8e33ec26...@debian.org> and subject line Closing - fixed by dist-upgrading has caused the Debian Bug report #886488, regarding cinnamon: Font rendering issue to be marked as done. This means that you claim

Bug#885793: marked as done (tldr-py,tldr: File collision when installing together: /usr/bin/tldr (and maybe further files))

Your message dated Sat, 06 Jan 2018 18:20:08 + with message-id and subject line Bug#885793: fixed in haskell-tldr 0.2.3-2 has caused the Debian Bug report #885793, regarding tldr-py,tldr: File collision when installing together: /usr/bin/tldr (and maybe further files) to be marked as done. T

Bug#541615: marked as done (tar: does not recognise xz compressed archives automatically)

Your message dated Sat, 06 Jan 2018 17:40:00 + with message-id and subject line Re: tar: does not recognise xz compressed archives automatically has caused the Debian Bug report #541615, regarding tar: does not recognise xz compressed archives automatically to be marked as done. This means t

Bug#834813: marked as done ([kamoso] New upstream version)

Your message dated Sat, 06 Jan 2018 18:45:52 +0100 with message-id <6162036.houETxakzM@pendragon> and subject line Re: [Pkg-kde-extras] Bug#834813: [kamoso] New upstream version has caused the Debian Bug report #834813, regarding [kamoso] New upstream version to be marked as done. This means that

Bug#774490: marked as done (tar: Please generate -dbg package for tar)

Your message dated Sat, 06 Jan 2018 17:33:00 + with message-id <3c55c397-50cf-e9d7-3a63-ef982d530...@thykier.net> and subject line Re: Bug#774490: tar: Please generate -dbg package for tar has caused the Debian Bug report #774490, regarding tar: Please generate -dbg package for tar to be marked

Bug#233598: marked as done (tar should autodetect if tarball is gzipped or bzipped)

Your message dated Sat, 06 Jan 2018 17:22:00 + with message-id <15c0aea2-d73d-6d69-36d4-4952fc2dc...@thykier.net> and subject line Re: Usability: Automatically try to decompress has caused the Debian Bug report #125828, regarding tar should autodetect if tarball is gzipped or bzipped to be mark

Bug#125828: marked as done (Usability: Automatically try to decompress)

Your message dated Sat, 06 Jan 2018 17:22:00 + with message-id <15c0aea2-d73d-6d69-36d4-4952fc2dc...@thykier.net> and subject line Re: Usability: Automatically try to decompress has caused the Debian Bug report #125828, regarding Usability: Automatically try to decompress to be marked as done.

Bug#355152: marked as done (GNU Tar Invalid Headers Buffer Overflow)

Your message dated Sat, 6 Jan 2018 18:09:10 +0100 with message-id <20180106170910.x22chtx5jupy7...@jwilk.net> and subject line Re: Bug#355152: GNU Tar Invalid Headers Buffer Overflow has caused the Debian Bug report #355152, regarding GNU Tar Invalid Headers Buffer Overflow to be marked as done. T

Bug#883627: marked as done (RFS: network-manager-fortisslvpn/1.2.6-2 [ITP] -- NetworkManager Fortinet SSLVPN plugin)

Your message dated Sat, 06 Jan 2018 16:20:09 + with message-id and subject line closing RFS: network-manager-fortisslvpn/1.2.6-2 [ITP] -- NetworkManager Fortinet SSLVPN plugin has caused the Debian Bug report #883627, regarding RFS: network-manager-fortisslvpn/1.2.6-2 [ITP] -- NetworkManager

Bug#886465: marked as done (rxvt-unicode: external 'screen' claims "Cannot find terminfo entry for 'rxvt-unicode-256color'.")

Your message dated Sat, 6 Jan 2018 11:10:08 -0500 with message-id <20180106161008.bb2rjzt6wo425...@zeta.ryanak.ca> and subject line Re: Bug#886465: rxvt-unicode: external 'screen' claims "Cannot find terminfo entry for 'rxvt-unicode-256color'." has caused the Debian Bug report #886465, regarding r

Bug#848674: marked as done (O: f3 -- test real flash memory capacity)

Your message dated Sat, 06 Jan 2018 15:49:41 + with message-id and subject line Bug#848674: fixed in f3 7.0-1 has caused the Debian Bug report #848674, regarding O: f3 -- test real flash memory capacity to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#758172: marked as done (isync: Adds . to Maildir directory names)

Your message dated Sat, 06 Jan 2018 15:04:47 + with message-id and subject line Bug#758172: fixed in isync 1.3.0-1 has caused the Debian Bug report #758172, regarding isync: Adds . to Maildir directory names to be marked as done. This means that you claim that the problem has been dealt with.

Bug#872420: marked as done (isync FTCBFS: misdetects openssl by using the build architecture pkg-config)

Your message dated Sat, 06 Jan 2018 15:04:47 + with message-id and subject line Bug#872420: fixed in isync 1.3.0-1 has caused the Debian Bug report #872420, regarding isync FTCBFS: misdetects openssl by using the build architecture pkg-config to be marked as done. This means that you claim t

Bug#871765: marked as done (please don't force a specific TLS version)

Your message dated Sat, 06 Jan 2018 15:04:47 + with message-id and subject line Bug#871765: fixed in isync 1.3.0-1 has caused the Debian Bug report #871765, regarding please don't force a specific TLS version to be marked as done. This means that you claim that the problem has been dealt with

Bug#782054: marked as done (mbsync: New version cannot open Maildir boxes)

Your message dated Sat, 06 Jan 2018 15:04:47 + with message-id and subject line Bug#782054: fixed in isync 1.3.0-1 has caused the Debian Bug report #782054, regarding mbsync: New version cannot open Maildir boxes to be marked as done. This means that you claim that the problem has been dealt

Bug#871813: marked as done (isync: please allow the usage of TLS1.1+ by default)

Your message dated Sat, 06 Jan 2018 15:04:47 + with message-id and subject line Bug#871765: fixed in isync 1.3.0-1 has caused the Debian Bug report #871765, regarding isync: please allow the usage of TLS1.1+ by default to be marked as done. This means that you claim that the problem has been

Bug#886416: marked as done (libnih: FTBFS with expat 2.2.5: "FAIL test_parse (unexpected line numbering)" and is now uninstallable due now failing BinNMU)

Your message dated Sat, 06 Jan 2018 13:49:28 + with message-id and subject line Bug#886416: fixed in libnih 1.0.3-10 has caused the Debian Bug report #886416, regarding libnih: FTBFS with expat 2.2.5: "FAIL test_parse (unexpected line numbering)" and is now uninstallable due now failing BinNM

Bug#884349: marked as done (primesieve: autopkgtest failure)

Your message dated Sat, 06 Jan 2018 13:04:38 + with message-id and subject line Bug#884349: fixed in primesieve 6.3+ds-2 has caused the Debian Bug report #884349, regarding primesieve: autopkgtest failure to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#886341: marked as done (ITP: node-prop-types -- Runtime type checking for React props and similar objects)

Your message dated Sat, 06 Jan 2018 12:00:11 + with message-id and subject line Bug#886341: fixed in node-prop-types 15.6.0-1 has caused the Debian Bug report #886341, regarding ITP: node-prop-types -- Runtime type checking for React props and similar objects to be marked as done. This means

Bug#876264: marked as done (ITP: node-babel-preset-env -- Babel preset for each environment)

Your message dated Sat, 06 Jan 2018 12:00:11 + with message-id and subject line Bug#876264: fixed in node-babel-preset-env 1.6.0-1 has caused the Debian Bug report #876264, regarding ITP: node-babel-preset-env -- Babel preset for each environment to be marked as done. This means that you clai

Bug#733610: marked as done (Gramps Webapp version)

Your message dated Sat, 6 Jan 2018 12:17:06 +0100 with message-id <0ba66509-05e2-893e-54ad-3bea27bf0...@debian.org> and subject line Closing the bug has caused the Debian Bug report #733610, regarding Gramps Webapp version to be marked as done. This means that you claim that the problem has been d

Bug#882800: marked as done (ITP: sphinx-gallery -- extension that builds an HTML gallery of examples from Python scripts)

Your message dated Sat, 06 Jan 2018 10:00:10 + with message-id and subject line Bug#882800: fixed in sphinx-gallery 0.1.13-1 has caused the Debian Bug report #882800, regarding ITP: sphinx-gallery -- extension that builds an HTML gallery of examples from Python scripts to be marked as done.

Bug#878630: marked as done (guymager: Build-depend on libparted-dev rather than libparted0-dev)

Your message dated Sat, 06 Jan 2018 09:35:14 + with message-id and subject line Bug#878630: fixed in guymager 0.8.7-1 has caused the Debian Bug report #878630, regarding guymager: Build-depend on libparted-dev rather than libparted0-dev to be marked as done. This means that you claim that the

Bug#886125: marked as done (slic3r: Binaries except slic3r cannot find Slic3r.pm)

Your message dated Sat, 06 Jan 2018 09:36:37 + with message-id and subject line Bug#886125: fixed in slic3r 1.2.9+dfsg-9 has caused the Debian Bug report #886125, regarding slic3r: Binaries except slic3r cannot find Slic3r.pm to be marked as done. This means that you claim that the problem ha

Bug#885551: marked as done (guymager: Don't recommend gksu)

Your message dated Sat, 06 Jan 2018 09:35:14 + with message-id and subject line Bug#885551: fixed in guymager 0.8.7-1 has caused the Debian Bug report #885551, regarding guymager: Don't recommend gksu to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#874902: marked as done ([guymager] Future Qt4 removal from Buster)

Your message dated Sat, 06 Jan 2018 09:35:14 + with message-id and subject line Bug#874902: fixed in guymager 0.8.7-1 has caused the Debian Bug report #874902, regarding [guymager] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt w

Bug#886434: marked as done (libcitadel FTBFS with "dpkg-buildpackage -B")

Your message dated Sat, 06 Jan 2018 09:19:13 + with message-id and subject line Bug#886434: fixed in libcitadel 917-2 has caused the Debian Bug report #886434, regarding libcitadel FTBFS with "dpkg-buildpackage -B" to be marked as done. This means that you claim that the problem has been deal

Bug#886366: marked as done (linux-headers-4.15.0-rc5-amd64: missing tools/objtool in /lib/modules/foo/build breaks DKMS modules builds)

Your message dated Sat, 06 Jan 2018 09:05:48 + with message-id and subject line Bug#886366: fixed in linux 4.14.12-2 has caused the Debian Bug report #886366, regarding linux-headers-4.15.0-rc5-amd64: missing tools/objtool in /lib/modules/foo/build breaks DKMS modules builds to be marked as d

Bug#886385: marked as done (netsniff-ng: FTBFS: error: inlining failed in call to always_inline '__builtin_memset')

Your message dated Sat, 06 Jan 2018 09:06:05 + with message-id and subject line Bug#886385: fixed in netsniff-ng 0.6.4-1 has caused the Debian Bug report #886385, regarding netsniff-ng: FTBFS: error: inlining failed in call to always_inline '__builtin_memset' to be marked as done. This means