Bug#914539: marked as done ([20181124] mirrors.tecnoera.com: out of date)

Your message dated Thu, 29 Nov 2018 07:17:40 + with message-id <5bff92943c245_3b722b1e1c19f0cc22...@godard.mail> and subject line Bug #914539 in mirrors fixed has caused the Debian Bug report #914539, regarding [20181124] mirrors.tecnoera.com: out of date to be marked as done. This means that

Bug#914708: marked as done (r-bioc-biocparallel: FTBFS with Boost 1.67)

Your message dated Thu, 29 Nov 2018 07:19:05 + with message-id and subject line Bug#914708: fixed in r-bioc-biocparallel 1.16.1-1 has caused the Debian Bug report #914708, regarding r-bioc-biocparallel: FTBFS with Boost 1.67 to be marked as done. This means that you claim that the problem has

Processed: closing 914406

Processing commands for cont...@bugs.debian.org: > # back in sync 2018-11-24 (previous age: 5d) > close 914406 Bug #914406 [mirrors] [20181123] mirror.overthewire.com.au: out of date Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 914406: https:

Processed: closing 882758

Processing commands for cont...@bugs.debian.org: > # upgraded to ftpsync 20180513 on 2018-11-22 > close 882758 Bug #882758 [mirrors] [20181118] ftp.fsn.hu: ftpsync version Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 882758: https://bugs.debi

Bug#914906: marked as done ([20181128] ftp.uni-bayreuth.de: unavailable intermittently)

Your message dated Thu, 29 Nov 2018 07:05:12 + with message-id <20181129070512.gk22...@sarek.noreply.org> and subject line Re: Bug#914906: [20181128] ftp.uni-bayreuth.de: unavailable intermittently has caused the Debian Bug report #914906, regarding [20181128] ftp.uni-bayreuth.de: unava

Bug#914837: marked as done (glibc: CVE-2018-19591: Linux if_nametoindex() does not close descriptor)

Your message dated Thu, 29 Nov 2018 06:34:30 + with message-id and subject line Bug#914837: fixed in glibc 2.28-1 has caused the Debian Bug report #914837, regarding glibc: CVE-2018-19591: Linux if_nametoindex() does not close descriptor to be marked as done. This means that you claim that t

Bug#882685: marked as done (onedrive: FTBFS on ppc64el: cc1d: error: cannot find source code for runtime library file 'object.d')

Your message dated Thu, 29 Nov 2018 15:29:57 +0900 with message-id <20181129062957.ga9...@bulldog.preining.info> and subject line Closing these bugs has caused the Debian Bug report #882685, regarding onedrive: FTBFS on ppc64el: cc1d: error: cannot find source code for runtime library file 'object

Bug#898762: marked as done (onedrive: segfaults on "Key not found: lastModifiedDateTime")

Your message dated Thu, 29 Nov 2018 15:29:57 +0900 with message-id <20181129062957.ga9...@bulldog.preining.info> and subject line Closing these bugs has caused the Debian Bug report #898762, regarding onedrive: segfaults on "Key not found: lastModifiedDateTime" to be marked as done. This means tha

Processed: control

Processing commands for cont...@bugs.debian.org: > close 896572 Bug #896572 [caffe-cuda] message: Cannot use GPU in CPU-only Caffe (caffe-cuda build) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 896572: https://bugs.debian.org/cgi-bin/bugrep

Bug#677446: marked as done (New version of g15stats available)

Your message dated Thu, 29 Nov 2018 05:54:07 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #677446, regarding New version of g15stats available to be marked as done. This means that you claim that the problem has been dealt wi

Bug#777174: marked as done (g15stats: cpu information isnt shown)

Your message dated Thu, 29 Nov 2018 05:54:07 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #777174, regarding g15stats: cpu information isnt shown to be marked as done. This means that you claim that the problem has been dealt

Bug#810412: marked as done (g15stats: please switch to libusb 1.0)

Your message dated Thu, 29 Nov 2018 05:54:07 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #810412, regarding g15stats: please switch to libusb 1.0 to be marked as done. This means that you claim that the problem has been deal

Bug#914894: marked as done (RM: jp2a/experimental -- RoQA; Upstream is contesting 1.0.7 version)

Your message dated Thu, 29 Nov 2018 05:54:37 + with message-id and subject line Bug#914894: Removed package(s) from experimental has caused the Debian Bug report #914894, regarding RM: jp2a/experimental -- RoQA; Upstream is contesting 1.0.7 version to be marked as done. This means that you cl

Bug#565297: marked as done (g15stats does not resume after suspend)

Your message dated Thu, 29 Nov 2018 05:54:07 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #565297, regarding g15stats does not resume after suspend to be marked as done. This means that you claim that the problem has been dea

Bug#494177: marked as done (g15daemon: lcd screen not cleared on exit)

Your message dated Thu, 29 Nov 2018 05:51:54 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #494177, regarding g15daemon: lcd screen not cleared on exit to be marked as done. This means that you claim that the problem has been

Bug#865160: marked as done (g15mpd: please build-depend on automake, not obsolete automake1.11)

Your message dated Thu, 29 Nov 2018 05:53:37 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #865160, regarding g15mpd: please build-depend on automake, not obsolete automake1.11 to be marked as done. This means that you claim t

Bug#541306: marked as done (g15daemon: Fail to install when required hardware is not present)

Your message dated Thu, 29 Nov 2018 05:51:54 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #541306, regarding g15daemon: Fail to install when required hardware is not present to be marked as done. This means that you claim tha

Bug#810411: marked as done (g15mpd: please switch to libusb 1.0)

Your message dated Thu, 29 Nov 2018 05:53:37 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #810411, regarding g15mpd: please switch to libusb 1.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#493219: marked as done (g15daemon: segfault if only lcd server loaded)

Your message dated Thu, 29 Nov 2018 05:51:54 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #493219, regarding g15daemon: segfault if only lcd server loaded to be marked as done. This means that you claim that the problem has b

Bug#810410: marked as done (g15macro: please switch to libusb 1.0)

Your message dated Thu, 29 Nov 2018 05:53:05 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #810410, regarding g15macro: please switch to libusb 1.0 to be marked as done. This means that you claim that the problem has been deal

Bug#873534: marked as done ([g15mpd]: Short descriptions should begin with lowercase)

Your message dated Thu, 29 Nov 2018 05:53:37 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #873534, regarding [g15mpd]: Short descriptions should begin with lowercase to be marked as done. This means that you claim that the pr

Bug#914888: marked as done (RM: g15deamoni, libg15 -- ROM; abandoned upstream (and upstream host serves malware))

Your message dated Thu, 29 Nov 2018 05:50:21 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #914888, regarding RM: g15deamoni, libg15 -- ROM; abandoned upstream (and upstream host serves malware) to be marked as done. This mea

Bug#914863: marked as done (RM: cipux-rbac/experimental -- RoQA; *cipux* was removed from unstable)

Your message dated Thu, 29 Nov 2018 05:49:37 + with message-id and subject line Bug#914863: Removed package(s) from experimental has caused the Debian Bug report #914863, regarding RM: cipux-rbac/experimental -- RoQA; *cipux* was removed from unstable to be marked as done. This means that you

Bug#888255: marked as done (RM? Upstream dropped support, security important, newer version packaged)

Your message dated Thu, 29 Nov 2018 05:49:20 + with message-id and subject line Bug#914780: Removed package(s) from unstable has caused the Debian Bug report #888255, regarding RM? Upstream dropped support, security important, newer version packaged to be marked as done. This means that you

Bug#810433: marked as done (libg15: please switch to libusb 1.0)

Your message dated Thu, 29 Nov 2018 05:50:25 + with message-id and subject line Bug#914888: Removed package(s) from unstable has caused the Debian Bug report #810433, regarding libg15: please switch to libusb 1.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#914767: marked as done (RM: foma/experimental -- RoM; upstream request)

Your message dated Thu, 29 Nov 2018 05:48:39 + with message-id and subject line Bug#914767: Removed package(s) from experimental has caused the Debian Bug report #914767, regarding RM: foma/experimental -- RoM; upstream request to be marked as done. This means that you claim that the problem

Bug#914780: marked as done (RM: netty-3.9 -- ROM; No longer used, replaced by netty)

Your message dated Thu, 29 Nov 2018 05:49:14 + with message-id and subject line Bug#914780: Removed package(s) from unstable has caused the Debian Bug report #914780, regarding RM: netty-3.9 -- ROM; No longer used, replaced by netty to be marked as done. This means that you claim that the pro

Bug#914858: marked as done (cargo: Cargo package version doesn't match the version cargo reports)

Your message dated Thu, 29 Nov 2018 05:49:00 + with message-id <1b41b733-4a88-d4f1-c875-486816e53...@debian.org> and subject line Re: cargo: Cargo package version doesn't match the version cargo reports has caused the Debian Bug report #914858, regarding cargo: Cargo package version doesn't ma

Processed: closing 865499 (gradle fails to start in unstable after plexus-containers update)

Processing commands for cont...@bugs.debian.org: > close 865499 3.2.1-4 Bug #865499 [gradle] gradle fails to start in unstable after plexus-containers update Marked as fixed in versions gradle/3.2.1-4. Bug #865499 [gradle] gradle fails to start in unstable after plexus-containers update Marked B

Bug#914874: marked as done (googletest fails to coinstall with itself)

Your message dated Thu, 29 Nov 2018 05:04:45 + with message-id and subject line Bug#914874: fixed in googletest 1.8.1-2 has caused the Debian Bug report #914874, regarding googletest fails to coinstall with itself to be marked as done. This means that you claim that the problem has been dealt

Bug#914091: marked as done (googletest: please make the build reproducible)

Your message dated Thu, 29 Nov 2018 05:04:45 + with message-id and subject line Bug#914091: fixed in googletest 1.8.1-2 has caused the Debian Bug report #914091, regarding googletest: please make the build reproducible to be marked as done. This means that you claim that the problem has been

Bug#914616: marked as done ([ring-daemon] Crashes because of segmentation fault)

Your message dated Thu, 29 Nov 2018 05:25:02 +0100 with message-id <9e55e23e8670ad9e41b865891dc3c4970d603254.ca...@debian.org> and subject line Fixed by latest binNMU has caused the Debian Bug report #914616, regarding [ring-daemon] Crashes because of segmentation fault to be marked as done. This

Bug#866653: marked as done (thawab: depends on gir1.2-webkit-3.0 which is deprecated)

Your message dated Thu, 29 Nov 2018 04:19:16 + with message-id and subject line Bug#866653: fixed in thawab 4.1-1 has caused the Debian Bug report #866653, regarding thawab: depends on gir1.2-webkit-3.0 which is deprecated to be marked as done. This means that you claim that the problem has b

Bug#914067: marked as done (caffe FTBFS with boost 1.67)

Your message dated Thu, 29 Nov 2018 04:19:03 + with message-id and subject line Bug#914067: fixed in caffe 1.0.0+git20180821.99bd997-1 has caused the Debian Bug report #914067, regarding caffe FTBFS with boost 1.67 to be marked as done. This means that you claim that the problem has been deal

Bug#898941: marked as done (caffe-cpu: Very different results for gpu and cpu calculations due to possibly problematic BLAS dependency)

Your message dated Thu, 29 Nov 2018 04:19:03 + with message-id and subject line Bug#898941: fixed in caffe 1.0.0+git20180821.99bd997-1 has caused the Debian Bug report #898941, regarding caffe-cpu: Very different results for gpu and cpu calculations due to possibly problematic BLAS dependency

Bug#914826: marked as done (openfortivpn FTCBFS: configures for the build architecture)

Your message dated Thu, 29 Nov 2018 03:04:37 + with message-id and subject line Bug#914826: fixed in openfortivpn 1.8.0-1 has caused the Debian Bug report #914826, regarding openfortivpn FTCBFS: configures for the build architecture to be marked as done. This means that you claim that the pro

Bug#914273: marked as done (symfony fails a lot of autopkg tests, even on amd64)

Your message dated Thu, 29 Nov 2018 02:53:53 + with message-id and subject line Bug#914273: fixed in symfony 3.4.19+dfsg-1 has caused the Debian Bug report #914273, regarding symfony fails a lot of autopkg tests, even on amd64 to be marked as done. This means that you claim that the problem h

Bug#910790: marked as done (new initrd file was not found)

Your message dated Thu, 29 Nov 2018 01:07:23 + with message-id and subject line Bug#910790: fixed in raspi3-firmware 1.20181112-1 has caused the Debian Bug report #910790, regarding new initrd file was not found to be marked as done. This means that you claim that the problem has been dealt w

Bug#897234: marked as done (raspi3-firmware: please add support for Raspberry Pi 3 B+)

Your message dated Thu, 29 Nov 2018 01:07:23 + with message-id and subject line Bug#897234: fixed in raspi3-firmware 1.20181112-1 has caused the Debian Bug report #897234, regarding raspi3-firmware: please add support for Raspberry Pi 3 B+ to be marked as done. This means that you claim that

Bug#903543: marked as done (raspi3-firmware: [PATCH] add configuration options for cmdline.txt)

Your message dated Thu, 29 Nov 2018 01:07:23 + with message-id and subject line Bug#903543: fixed in raspi3-firmware 1.20181112-1 has caused the Debian Bug report #903543, regarding raspi3-firmware: [PATCH] add configuration options for cmdline.txt to be marked as done. This means that you cl

Bug#914818: marked as done (vm: removes shipped file /usr/share/emacs/site-lisp/vm.in/version.txt)

Your message dated Thu, 29 Nov 2018 00:05:58 + with message-id and subject line Bug#914818: fixed in vm 8.2.0b-4 has caused the Debian Bug report #914818, regarding vm: removes shipped file /usr/share/emacs/site-lisp/vm.in/version.txt to be marked as done. This means that you claim that the p

Bug#909513: marked as done (mutt-alias-el: Please obey "nodoc" build profile)

Your message dated Thu, 29 Nov 2018 00:05:30 + with message-id and subject line Bug#909513: fixed in mutt-alias-el 1.5-2 has caused the Debian Bug report #909513, regarding mutt-alias-el: Please obey "nodoc" build profile to be marked as done. This means that you claim that the problem has be

Bug#909836: marked as done (entangle: FTBFS on arm64: entangle-colour-profile-enums.h: No such file or directory)

Your message dated Wed, 28 Nov 2018 23:04:49 + with message-id and subject line Bug#909836: fixed in entangle 1.0-2 has caused the Debian Bug report #909836, regarding entangle: FTBFS on arm64: entangle-colour-profile-enums.h: No such file or directory to be marked as done. This means that y

Bug#544056: marked as done (O: bglibs -- BG Libraries Collection)

Your message dated Wed, 28 Nov 2018 22:50:06 + with message-id and subject line Bug#544056: fixed in bglibs 2.04+dfsg-2 has caused the Debian Bug report #544056, regarding O: bglibs -- BG Libraries Collection to be marked as done. This means that you claim that the problem has been dealt with

Bug#900812: marked as done (egg: fails to install with xemacs21)

Your message dated Wed, 28 Nov 2018 22:47:07 + with message-id and subject line Bug#900812: fixed in egg 4.2.0-1.1+deb9u1 has caused the Debian Bug report #900812, regarding egg: fails to install with xemacs21 to be marked as done. This means that you claim that the problem has been dealt wit

Processed: closing 914934

Processing commands for cont...@bugs.debian.org: > close 914934 Bug #914934 [systemd-coredump] systemd-coredump: at least suggest lz4? Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 914934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=9149

Bug#903410: marked as done (RFS: tvb-library/1.5.5.1-1 [ITP])

Your message dated Wed, 28 Nov 2018 22:23:58 + with message-id and subject line closing RFS: tvb-library/1.5.5.1-1 [ITP] has caused the Debian Bug report #903410, regarding RFS: tvb-library/1.5.5.1-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#903411: marked as done (RFS: tvb-gdist/1.5.6-1 [ITP] -- friendly greeter)

Your message dated Wed, 28 Nov 2018 22:23:59 + with message-id and subject line closing RFS: tvb-gdist/1.5.6-1 [ITP] -- friendly greeter has caused the Debian Bug report #903411, regarding RFS: tvb-gdist/1.5.6-1 [ITP] -- friendly greeter to be marked as done. This means that you claim that th

Bug#894076: marked as done (Can't include GL and GLES headers simultaneously on non-64 bit architectures)

Your message dated Wed, 28 Nov 2018 23:51:05 +0200 with message-id <20181128215105.GD7424@localhost> and subject line This should be fixed in Mesa 18.2.5 has caused the Debian Bug report #894076, regarding Can't include GL and GLES headers simultaneously on non-64 bit architectures to be marked as

Bug#588939: marked as done (jfsutils: Is it a joke that my three JFS harddisks crashed at the same time? JFS reliability?)

Your message dated Wed, 28 Nov 2018 16:23:29 -0500 with message-id and subject line Re: Bug#588939: jfsutils: Is it a joke that my three JFS harddisks crashed at the same time? JFS reliability? has caused the Debian Bug report #588939, regarding jfsutils: Is it a joke that my three JFS harddisks

Bug#878030: marked as done (python3-dotenv: /usr/bin/dotenv already provided by ruby-dotenv)

Your message dated Wed, 28 Nov 2018 19:51:03 + with message-id and subject line Bug#878030: fixed in python-dotenv 0.9.1-1 has caused the Debian Bug report #878030, regarding python3-dotenv: /usr/bin/dotenv already provided by ruby-dotenv to be marked as done. This means that you claim that t

Bug#914287: marked as done (lsb-release: please parse /usr/lib/os-release and deprecate /etc/lsb-release)

Your message dated Wed, 28 Nov 2018 19:49:38 + with message-id and subject line Bug#914287: fixed in lsb 10.2018112800 has caused the Debian Bug report #914287, regarding lsb-release: please parse /usr/lib/os-release and deprecate /etc/lsb-release to be marked as done. This means that you cl

Bug#913383: marked as done (libetpan FTBFS with curl 7.62.0)

Your message dated Wed, 28 Nov 2018 19:49:26 + with message-id and subject line Bug#913383: fixed in libetpan 1.9.1-2 has caused the Debian Bug report #913383, regarding libetpan FTBFS with curl 7.62.0 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#914930: marked as done (dbus-python: FTBCFS in python3-defaults transition)

Your message dated Wed, 28 Nov 2018 20:45:23 +0100 with message-id <2ca79d41-77ca-1c03-f36a-5a6c5161f...@debian.org> and subject line Re: dbus-python: FTBCFS in python3-defaults transition has caused the Debian Bug report #914930, regarding dbus-python: FTBCFS in python3-defaults transition to be m

Bug#900314: marked as done ([patch] relax dh 11 build dep to 11~ so a no-change bpo remains possible)

Your message dated Wed, 28 Nov 2018 14:38:28 -0500 with message-id <20181128193825.vx7pm46ltclzw...@digitalmercury.dynalias.net> and subject line closing bug because 4.17-1~bpo9 is in the archive has caused the Debian Bug report #900314, regarding [patch] relax dh 11 build dep to 11~ so a no-change

Bug#912996: marked as done (tuptime: Add support for suspend and hivernate)

Your message dated Wed, 28 Nov 2018 19:07:17 + with message-id and subject line Bug#912996: fixed in tuptime 3.4.1 has caused the Debian Bug report #912996, regarding tuptime: Add support for suspend and hivernate to be marked as done. This means that you claim that the problem has been dealt

Bug#914675: marked as done (nmu: kodi-pvr-mediaportal-tvserver_2.4.14+dfsg1-1)

Your message dated Wed, 28 Nov 2018 18:56:15 +0100 with message-id and subject line Re: Bug#914675: nmu: kodi-pvr-mediaportal-tvserver_2.4.14+dfsg1-1 has caused the Debian Bug report #914675, regarding nmu: kodi-pvr-mediaportal-tvserver_2.4.14+dfsg1-1 to be marked as done. This means that you cl

Bug#914681: marked as done (gb metview on mips)

Your message dated Wed, 28 Nov 2018 18:55:34 +0100 with message-id and subject line Re: Bug#914681: gb metview on mips has caused the Debian Bug report #914681, regarding gb metview on mips to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Bug#914631: marked as done (nmu: mpb_1.5-3)

Your message dated Wed, 28 Nov 2018 18:57:48 +0100 with message-id <0263cb8f-d2b2-416f-398d-255da6fe7...@debian.org> and subject line Re: Bug#914631: nmu: mpb_1.5-3 has caused the Debian Bug report #914631, regarding nmu: mpb_1.5-3 to be marked as done. This means that you claim that the problem h

Bug#914519: marked as done (nmu: dovecot-antispam_2.0+20171229-1)

Your message dated Wed, 28 Nov 2018 18:58:16 +0100 with message-id <0804eb12-5dd0-2524-bd4d-d1eecb5f3...@debian.org> and subject line Re: Bug#914519: nmu: dovecot-antispam_2.0+20171229-1 has caused the Debian Bug report #914519, regarding nmu: dovecot-antispam_2.0+20171229-1 to be marked as done.

Bug#912422: marked as done (python2.7 hard codes location of netinet/in.h)

Your message dated Wed, 28 Nov 2018 17:51:01 + with message-id and subject line Bug#912422: fixed in python2.7 2.7.15-5 has caused the Debian Bug report #912422, regarding python2.7 hard codes location of netinet/in.h to be marked as done. This means that you claim that the problem has been d

Bug#909673: marked as done (python2.7: CVE-2018-1000802)

Your message dated Wed, 28 Nov 2018 17:51:01 + with message-id and subject line Bug#909673: fixed in python2.7 2.7.15-5 has caused the Debian Bug report #909673, regarding python2.7: CVE-2018-1000802 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#895720: marked as done (Installation of Buster successfully at Asus UX501)

Your message dated Wed, 28 Nov 2018 18:47:04 +0100 with message-id <7c1d46d8b1bdfc382f297cc906cb6c7f6a525e96.ca...@gmail.com> and subject line Installation was successfully has caused the Debian Bug report #895720, regarding Installation of Buster successfully at Asus UX501 to be marked as done. T

Bug#902212: marked as done (Installation Debian 10 Buster successfully on Acer Aspire One)

Your message dated Wed, 28 Nov 2018 18:46:23 +0100 with message-id and subject line Installation was successfully has caused the Debian Bug report #902212, regarding Installation Debian 10 Buster successfully on Acer Aspire One to be marked as done. This means that you claim that the problem has

Bug#902215: marked as done (Installation Debian 10 Buster successfully on AMD A10 Desktop PC)

Your message dated Wed, 28 Nov 2018 18:45:36 +0100 with message-id <0b621552541ca3bce865580fa80bfb262c5d18f5.ca...@gmail.com> and subject line Installation was successfully has caused the Debian Bug report #902215, regarding Installation Debian 10 Buster successfully on AMD A10 Desktop PC to be mar

Bug#912148: marked as done (ruby-icalendar FTBFS with tzdata >= 2018f)

Your message dated Wed, 28 Nov 2018 16:40:29 + with message-id and subject line Bug#912148: fixed in ruby-icalendar 2.4.1-2 has caused the Debian Bug report #912148, regarding ruby-icalendar FTBFS with tzdata >= 2018f to be marked as done. This means that you claim that the problem has been d

Bug#914900: marked as done (qemu: Please enable kvm use by default on Linux)

Your message dated Wed, 28 Nov 2018 19:13:03 +0300 with message-id <3432b2f3-1dbc-8432-393e-86a897d33...@msgid.tls.msk.ru> and subject line Re: Bug#914900: qemu: Please enable kvm use by default on Linux has caused the Debian Bug report #914900, regarding qemu: Please enable kvm use by default on L

Bug#905388: marked as done (ITP: elogind -- The systemd project's "logind", extracted to a standalone package)

Your message dated Wed, 28 Nov 2018 15:43:01 + with message-id <20181128154301.gv17...@hindley.org.uk> and subject line Re: elogind_239.1+20181112+gd4a3f291e395+nosubmodule-1+debian1_multi.changes ACCEPTED into unstable, unstable has caused the Debian Bug report #905388, regarding ITP: elogin

Bug#906136: marked as done (sensible-browser doesn't seem to have a user local way of changing it)

Your message dated Wed, 28 Nov 2018 16:44:34 +0100 with message-id and subject line sensible-browser doesn't seem to have a user local way of changing it has caused the Debian Bug report #906136, regarding sensible-browser doesn't seem to have a user local way of changing it to be marked as done

Bug#843374: marked as done (Updating the xcircuit Uploaders list)

Your message dated Wed, 28 Nov 2018 16:28:48 +0100 with message-id and subject line Already done has caused the Debian Bug report #843374, regarding Updating the xcircuit Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#914903: marked as done (mbrola: fails to clean after build)

Your message dated Wed, 28 Nov 2018 14:55:24 + with message-id and subject line Bug#914903: fixed in mbrola 3.02b+dfsg-3 has caused the Debian Bug report #914903, regarding mbrola: fails to clean after build to be marked as done. This means that you claim that the problem has been dealt with.

Bug#914812: marked as done (elpa-graphql: fails to install: examples.el:3:1:Error: Cannot open load file: No such file or directory, ghub)

Your message dated Wed, 28 Nov 2018 14:50:53 + with message-id and subject line Bug#914812: fixed in graphql-el 0.1.1-2 has caused the Debian Bug report #914812, regarding elpa-graphql: fails to install: examples.el:3:1:Error: Cannot open load file: No such file or directory, ghub to be marke

Bug#836105: marked as done (konclude: please switch from dbus-x11 to default-dbus-session-bus | dbus-session-bus)

Your message dated Wed, 28 Nov 2018 14:51:04 + with message-id and subject line Bug#836105: fixed in konclude 0.6.2~dfsg-4 has caused the Debian Bug report #836105, regarding konclude: please switch from dbus-x11 to default-dbus-session-bus | dbus-session-bus to be marked as done. This means

Processed: closing 914387

Processing commands for cont...@bugs.debian.org: > close 914387 18.1-1 Bug #914387 [python3-pip] python3-pip: cannot import name 'main' from 'pip' Marked as fixed in versions python-pip/18.1-1. Bug #914387 [python3-pip] python3-pip: cannot import name 'main' from 'pip' Marked Bug as done > thanks

Bug#902659: marked as done ([20181118] mirrors.shu.edu.cn: unreachable intermittently)

Your message dated Wed, 28 Nov 2018 13:43:45 + with message-id <20181128134345.gc22...@sarek.noreply.org> and subject line Re: Bug#902659: mirrors.shu.edu.cn issues has caused the Debian Bug report #902659, regarding [20181118] mirrors.shu.edu.cn: unreachable intermittently to be marked as done

Bug#914752: marked as done (opencv: FTBFS against python3.7.1: error: invalid conversion from 'const char*' to 'char*' [-fpermissive])

Your message dated Wed, 28 Nov 2018 13:20:13 + with message-id and subject line Bug#914752: fixed in opencv 3.2.0+dfsg-5 has caused the Debian Bug report #914752, regarding opencv: FTBFS against python3.7.1: error: invalid conversion from 'const char*' to 'char*' [-fpermissive] to be marked a

Bug#914653: marked as done (opencv: FTBFS against python3.7.1: error: invalid conversion from 'const char*' to 'char*' [-fpermissive])

Your message dated Wed, 28 Nov 2018 13:20:13 + with message-id and subject line Bug#914752: fixed in opencv 3.2.0+dfsg-5 has caused the Debian Bug report #914752, regarding opencv: FTBFS against python3.7.1: error: invalid conversion from 'const char*' to 'char*' [-fpermissive] to be marked a

Bug#914898: marked as done (debootstrap, stretch-backports: Please disabled merged /usr by default)

Your message dated Wed, 28 Nov 2018 13:22:30 +0100 with message-id <87bc37a8-3f5c-38dc-fe6b-544868634...@debian.org> and subject line Re: Bug#914898: debootstrap, stretch-backports: Please disabled merged /usr by default has caused the Debian Bug report #914898, regarding debootstrap, stretch-back

Bug#914878: marked as done ([20181128] mirrors.namecheap.com: tracefile, upstream)

Your message dated Wed, 28 Nov 2018 12:06:55 + with message-id <20181128120655.gb22...@sarek.noreply.org> and subject line Re: Bug#914878: Fixed has caused the Debian Bug report #914878, regarding [20181128] mirrors.namecheap.com: tracefile, upstream to be marked as done. This means th

Bug#914048: marked as done (mirror submission for debian.petarmaric.com [missing sources])

Your message dated Wed, 28 Nov 2018 11:50:44 + with message-id <20181128115044.ga29...@sarek.noreply.org> and subject line Re: Bug#914048: mirror submission for debian.petarmaric.com has caused the Debian Bug report #914048, regarding mirror submission for debian.petarmaric.com [missing sources

Bug#914346: marked as done (rover: Please indent list items in long description)

Your message dated Wed, 28 Nov 2018 11:36:23 + with message-id and subject line Bug#914346: fixed in rover 0.3.1 has caused the Debian Bug report #914346, regarding rover: Please indent list items in long description to be marked as done. This means that you claim that the problem has been de

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 914846 src:yaml-cpp Bug #914846 [mongodb-server-core] mongodb-server-core: libyaml-cpp0.5v5:amd64 0.5.3-0.1 upgrade breaks mongod Bug reassigned from package 'mongodb-server-core' to 'src:yaml-cpp'. No longer marked as found in versions

Bug#914784: marked as done (cantor ftbfs on all archs except amd64)

Your message dated Wed, 28 Nov 2018 12:51:43 +0200 with message-id <20181128105143.GA23315@localhost> and subject line Re: Bug#914784: cantor ftbfs on all archs except amd64 has caused the Debian Bug report #914784, regarding cantor ftbfs on all archs except amd64 to be marked as done. This means

Bug#913892: marked as done (CVE-2018-18385)

Your message dated Wed, 28 Nov 2018 10:04:09 + with message-id and subject line Bug#913892: fixed in asciidoctor 1.5.8-1 has caused the Debian Bug report #913892, regarding CVE-2018-18385 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#909105: marked as done (consider switching asciidoctor to Architecture: all)

Your message dated Wed, 28 Nov 2018 10:04:09 + with message-id and subject line Bug#909105: fixed in asciidoctor 1.5.8-1 has caused the Debian Bug report #909105, regarding consider switching asciidoctor to Architecture: all to be marked as done. This means that you claim that the problem has

Bug#888442: marked as done ([nftables] Crash when list(ing) ip6tables-compat CT rules)

Your message dated Wed, 28 Nov 2018 10:30:38 +0100 with message-id <7b1de926-9370-dd60-3492-dad0b9a42...@debian.org> and subject line Bug fixed has caused the Debian Bug report #888442, regarding [nftables] Crash when list(ing) ip6tables-compat CT rules to be marked as done. This means that you cl

Bug#847443: marked as done (Install fop.xsd in the binary package.)

Your message dated Wed, 28 Nov 2018 09:19:09 + with message-id and subject line Bug#847443: fixed in fop 1:2.3-2 has caused the Debian Bug report #847443, regarding Install fop.xsd in the binary package. to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#897287: marked as done (Please remove me from the uploaders)

Your message dated Wed, 28 Nov 2018 09:19:09 + with message-id and subject line Bug#897287: fixed in fop 1:2.3-2 has caused the Debian Bug report #897287, regarding Please remove me from the uploaders to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#903711: marked as done (CVE-2018-13794)

Your message dated Wed, 28 Nov 2018 08:43:37 + with message-id and subject line Bug#903711: fixed in catimg 2.5.0-1 has caused the Debian Bug report #903711, regarding CVE-2018-13794 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#912990: marked as done (Add “btrfs-progs” as a package suggestion)

Your message dated Wed, 28 Nov 2018 09:11:48 +0100 with message-id <20181128081148.ga18...@mail.bluemosh.com> and subject line Fixed has caused the Debian Bug report #912990, regarding Add “btrfs-progs” as a package suggestion to be marked as done. This means that you claim that the problem has be