Bug#920672: marked as done (netdata: Incomplete debian/copyright?)

Your message dated Mon, 28 Jan 2019 09:30:47 +0100 with message-id <1548664247.3149642.1645029560.44b17...@webmail.messagingengine.com> and subject line has caused the Debian Bug report #920672, regarding netdata: Incomplete debian/copyright? to be marked as done. This means that you claim that

Bug#920305: marked as done (ITP: popper.js -- Javascript library to position poppers in web applications)

Your message dated Mon, 28 Jan 2019 09:00:20 + with message-id and subject line Bug#920305: fixed in popper.js 1.14.6+ds-1 has caused the Debian Bug report #920305, regarding ITP: popper.js -- Javascript library to position poppers in web applications to be marked as done. This means that

Bug#914740: marked as done (agg FTCBFS: configures for the build architecture)

Your message dated Mon, 28 Jan 2019 09:00:10 + with message-id and subject line Bug#914740: fixed in agg 1:2.6.0-r132+dfsg1-1 has caused the Debian Bug report #914740, regarding agg FTCBFS: configures for the build architecture to be marked as done. This means that you claim that the problem

Bug#863704: marked as done (ITP: node-yarnpkg -- a fast, reliable and secure npm)

Your message dated Mon, 28 Jan 2019 09:00:19 + with message-id and subject line Bug#843021: fixed in node-yarnpkg 1.13.0-1 has caused the Debian Bug report #843021, regarding ITP: node-yarnpkg -- a fast, reliable and secure npm to be marked as done. This means that you claim that the problem

Bug#843021: marked as done (ITP: node-yarnpkg -- a fast, reliable and secure npm)

Your message dated Mon, 28 Jan 2019 09:00:19 + with message-id and subject line Bug#843021: fixed in node-yarnpkg 1.13.0-1 has caused the Debian Bug report #843021, regarding ITP: node-yarnpkg -- a fast, reliable and secure npm to be marked as done. This means that you claim that the problem

Bug#920350: marked as done (ITP: pkg-js-autopkgtest -- collection of autopktest scripts for nodejs packages)

Your message dated Mon, 28 Jan 2019 09:00:19 + with message-id and subject line Bug#920350: fixed in pkg-js-tools 0.1 has caused the Debian Bug report #920350, regarding ITP: pkg-js-autopkgtest -- collection of autopktest scripts for nodejs packages to be marked as done. This means that you

Bug#867274: marked as done (ITP: libjs-webrtc-adapter -- shim to insulate apps from WebRTC spec changes and browser prefix differences)

Your message dated Mon, 28 Jan 2019 09:00:14 + with message-id and subject line Bug#867274: fixed in libjs-webrtc-adapter 7.2.0-1 has caused the Debian Bug report #867274, regarding ITP: libjs-webrtc-adapter -- shim to insulate apps from WebRTC spec changes and browser prefix differences to

Bug#920516: marked as done (ITP: libjs-rtcpeerconnection-shim -- RTCPeerConnection API implemented ontop of ORTC)

Your message dated Mon, 28 Jan 2019 09:00:11 + with message-id and subject line Bug#920516: fixed in libjs-rtcpeerconnection-shim 1.2.14-1 has caused the Debian Bug report #920516, regarding ITP: libjs-rtcpeerconnection-shim -- RTCPeerConnection API implemented ontop of ORTC to be marked as

Bug#898931: marked as done (ITP: looking-glass -- An extremely low latency KVM FrameRelay implementation for guests with VGA PCI Passthrough)

Your message dated Mon, 28 Jan 2019 09:00:15 + with message-id and subject line Bug#898931: fixed in looking-glass 0+a12-1 has caused the Debian Bug report #898931, regarding ITP: looking-glass -- An extremely low latency KVM FrameRelay implementation for guests with VGA PCI Passthrough to

Bug#847613: marked as done (ITP: nextcloud-client -- desktop client for nextcloud)

Your message dated Mon, 28 Jan 2019 09:00:18 + with message-id and subject line Bug#847613: fixed in nextcloud-desktop 2.5.1-1 has caused the Debian Bug report #847613, regarding ITP: nextcloud-client -- desktop client for nextcloud to be marked as done. This means that you claim that the

Bug#377270: marked as done (please package shared library)

Your message dated Mon, 28 Jan 2019 09:00:10 + with message-id and subject line Bug#377270: fixed in agg 1:2.6.0-r132+dfsg1-1 has caused the Debian Bug report #377270, regarding please package shared library to be marked as done. This means that you claim that the problem has been dealt

Bug#920612: marked as done (ITP: libcatmandu-filestore-perl -- modules to make files persistent within the Catmandu framework)

Your message dated Mon, 28 Jan 2019 09:00:11 + with message-id and subject line Bug#920612: fixed in libcatmandu-filestore-perl 1.13-1 has caused the Debian Bug report #920612, regarding ITP: libcatmandu-filestore-perl -- modules to make files persistent within the Catmandu framework to be

Bug#867272: marked as done (RFP: libjs-sdp -- SDP parsing and serialization utilities)

Your message dated Mon, 28 Jan 2019 09:00:12 + with message-id and subject line Bug#867272: fixed in libjs-sdp 2.9.0-1 has caused the Debian Bug report #867272, regarding RFP: libjs-sdp -- SDP parsing and serialization utilities to be marked as done. This means that you claim that the

Bug#907997: marked as done (emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2)

Your message dated Mon, 28 Jan 2019 14:53:33 +0100 with message-id <3fbe04a7-64ec-05db-ee9d-5e0e3b7a7...@debian.org> and subject line Re: Bug#907997: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2 has caused the Debian Bug report

Bug#324542: marked as done (cjk-latex: Different horizontal/vertical DPI cause wrong size CJK characters and overprinting)

Your message dated Mon, 28 Jan 2019 15:25:01 +0100 with message-id <5e6cc28f-7e6f-b9ee-3094-26d62d28c...@web.de> and subject line Re: Bug#324542: Update of cjk-latex (now latex-cjk) has caused the Debian Bug report #324542, regarding cjk-latex: Different horizontal/vertical DPI cause wrong size

Bug#919876: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)

Your message dated Mon, 28 Jan 2019 15:12:56 + with message-id and subject line Bug#919876: fixed in java-string-similarity 0.24-2 has caused the Debian Bug report #919876, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be

Bug#669662: marked as done ([PATCH] prosper: Helping to update to packaging format 3.0)

Your message dated Mon, 28 Jan 2019 16:28:06 +0100 with message-id <20190128152806.kg2q4b7644bul...@haka.dresden.de> and subject line Re: Bug#669662: [PATCH] prosper: Helping to update to packaging format 3.0 has caused the Debian Bug report #669662, regarding [PATCH] prosper: Helping to update

Bug#919390: marked as done (udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules)

Your message dated Mon, 28 Jan 2019 12:51:45 + with message-id and subject line Bug#919390: fixed in systemd 240-5 has caused the Debian Bug report #919390, regarding udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules to be

Bug#920018: marked as done (Memory Leak in journald? Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory)

Your message dated Mon, 28 Jan 2019 12:51:45 + with message-id and subject line Bug#920018: fixed in systemd 240-5 has caused the Debian Bug report #920018, regarding Memory Leak in journald? Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory to be marked as done.

Bug#920702: marked as done (RM: webdis [mips64el] -- RoQA; Unbuildable, blocking cruft removal)

Your message dated Mon, 28 Jan 2019 13:23:31 + with message-id and subject line Bug#920702: Removed package(s) from unstable has caused the Debian Bug report #920702, regarding RM: webdis [mips64el] -- RoQA; Unbuildable, blocking cruft removal to be marked as done. This means that you claim

Bug#920668: marked as done (light-locker: debug mode crashes after unlock)

Your message dated Mon, 28 Jan 2019 13:36:36 + with message-id and subject line Bug#892290: fixed in light-locker 1.8.0-3 has caused the Debian Bug report #892290, regarding light-locker: debug mode crashes after unlock to be marked as done. This means that you claim that the problem has

Bug#892290: marked as done (light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect)

Your message dated Mon, 28 Jan 2019 13:36:36 + with message-id and subject line Bug#892290: fixed in light-locker 1.8.0-3 has caused the Debian Bug report #892290, regarding light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect to be marked as done.

Bug#920666: marked as done (light-locker: Please include upstream README in the packaged docs)

Your message dated Mon, 28 Jan 2019 13:36:36 + with message-id and subject line Bug#920666: fixed in light-locker 1.8.0-3 has caused the Debian Bug report #920666, regarding light-locker: Please include upstream README in the packaged docs to be marked as done. This means that you claim that

Bug#919407: marked as done (unattended-upgrades: Log includes too much "(Reading database ... X%)" spam lines)

Your message dated Mon, 28 Jan 2019 15:59:54 + with message-id and subject line Bug#919407: fixed in unattended-upgrades 1.10 has caused the Debian Bug report #919407, regarding unattended-upgrades: Log includes too much "(Reading database ... X%)" spam lines to be marked as done. This

Bug#641858: marked as done (debian/control wording review)

Your message dated Mon, 28 Jan 2019 14:47:47 +0100 with message-id <20190128134747.pbc5yytfztiik...@haka.dresden.de> and subject line Re: texlive-base: General update after the debconf review process has caused the Debian Bug report #641858, regarding debian/control wording review to be marked as

Bug#920193: marked as done (nmu: krita_1:4.1.7+dfsg-1)

Your message dated Mon, 28 Jan 2019 15:51:37 +0100 with message-id <25fdba27-663c-56e2-bc06-84bcfe9d1...@debian.org> and subject line Re: Bug#920193: nmu: krita_1:4.1.7+dfsg-1 has caused the Debian Bug report #920193, regarding nmu: krita_1:4.1.7+dfsg-1 to be marked as done. This means that you

Bug#920662: marked as done (orthanc-mysql: uses $(DEB_VERSION) as SOVERSION)

Your message dated Mon, 28 Jan 2019 12:21:27 + with message-id and subject line Bug#920662: fixed in orthanc-mysql 2.0-2 has caused the Debian Bug report #920662, regarding orthanc-mysql: uses $(DEB_VERSION) as SOVERSION to be marked as done. This means that you claim that the problem has

Bug#321198: marked as done (piwi: Apache::DBI not needed)

Your message dated Mon, 28 Jan 2019 12:31:24 + with message-id and subject line Bug#920679: Removed package(s) from unstable has caused the Debian Bug report #321198, regarding piwi: Apache::DBI not needed to be marked as done. This means that you claim that the problem has been dealt with.

Bug#920679: marked as done (RM: piwi -- Orphaned, not updated, buggy)

Your message dated Mon, 28 Jan 2019 12:31:18 + with message-id and subject line Bug#920679: Removed package(s) from unstable has caused the Debian Bug report #920679, regarding RM: piwi -- Orphaned, not updated, buggy to be marked as done. This means that you claim that the problem has been

Bug#838922: marked as done (O: piwi -- P(erl|relude) IDS Web Interface - A frontend to your Prelude database)

Your message dated Mon, 28 Jan 2019 12:31:24 + with message-id and subject line Bug#920679: Removed package(s) from unstable has caused the Debian Bug report #838922, regarding O: piwi -- P(erl|relude) IDS Web Interface - A frontend to your Prelude database to be marked as done. This means

Bug#706244: marked as done (piwi: Ships cache files in the binary package)

Your message dated Mon, 28 Jan 2019 12:31:24 + with message-id and subject line Bug#920679: Removed package(s) from unstable has caused the Debian Bug report #706244, regarding piwi: Ships cache files in the binary package to be marked as done. This means that you claim that the problem has

Bug#920264: marked as done (postfixadmin: please add postfixadmin-cli to PATH)

Your message dated Mon, 28 Jan 2019 15:23:40 + with message-id and subject line Bug#920264: fixed in postfixadmin 3.2.1-2 has caused the Debian Bug report #920264, regarding postfixadmin: please add postfixadmin-cli to PATH to be marked as done. This means that you claim that the problem has

Bug#920564: marked as done (Unknown configuration: password_expiration, show_vacation and show_disabled)

Your message dated Mon, 28 Jan 2019 15:23:40 + with message-id and subject line Bug#920564: fixed in postfixadmin 3.2.1-2 has caused the Debian Bug report #920564, regarding Unknown configuration: password_expiration, show_vacation and show_disabled to be marked as done. This means that you

Bug#906811: marked as done (FTBFS: libconfig.h: No such file or directory)

Your message dated Mon, 28 Jan 2019 15:49:44 + with message-id and subject line Bug#906811: fixed in blasr 5.3.2+dfsg-1 has caused the Debian Bug report #906811, regarding FTBFS: libconfig.h: No such file or directory to be marked as done. This means that you claim that the problem has been

Bug#918323: marked as done (unattended-upgrades: tried to upgrade package with conffile prompt)

Your message dated Mon, 28 Jan 2019 15:59:54 + with message-id and subject line Bug#918323: fixed in unattended-upgrades 1.10 has caused the Debian Bug report #918323, regarding unattended-upgrades: tried to upgrade package with conffile prompt to be marked as done. This means that you claim

Processed: Re: distcc: deprecation of python-support

Processing control commands: > tag -1 - experimental Bug #785990 [src:distcc] distcc: deprecation of python-support Removed tag(s) experimental. > close -1 Bug #785990 [src:distcc] distcc: deprecation of python-support Marked Bug as done -- 785990:

Bug#920624: marked as done (tzdata: raspberry pi 1 hangs during upgrade of tzdata to 2018i-0+deb8u1)

Your message dated Mon, 28 Jan 2019 14:57:38 +0100 with message-id <20190128135738.gd3...@aurel32.net> and subject line Re: Bug#920624: tzdata: raspberry pi 1 hangs during upgrade of tzdata to 2018i-0+deb8u1 has caused the Debian Bug report #920624, regarding tzdata: raspberry pi 1 hangs during

Bug#915325: marked as done (r-cran-rgenoud: autopkgtest needs update for new version of glibc)

Your message dated Mon, 28 Jan 2019 18:12:57 +0200 with message-id <48a3f48e-d5e6-99a9-44e5-69fce53ef...@debian.org> and subject line r-cran-rgenoud: autopkgtest needs update for new version of glibc has caused the Debian Bug report #915325, regarding r-cran-rgenoud: autopkgtest needs update for

Bug#916817: marked as done (transition: remove python3.6)

Your message dated Mon, 28 Jan 2019 13:55:32 +0100 with message-id <5c795f9b-b7db-86d1-e781-2a456d454...@debian.org> and subject line Re: Bug#916817: transition: remove python3.6 has caused the Debian Bug report #916817, regarding transition: remove python3.6 to be marked as done. This means that

Bug#787472: marked as done (distcc: push 3.2 RC1 in unstable)

Your message dated Mon, 28 Jan 2019 14:06:08 +0100 with message-id <35a63aba-d429-7ed3-c81f-f433b4e72...@debian.org> and subject line Re: distcc: push 3.2 RC1 in unstable has caused the Debian Bug report #787472, regarding distcc: push 3.2 RC1 in unstable to be marked as done. This means that you

Bug#886720: marked as done (/usr/bin/godoc: godoc needs a rebuild against the current golang version)

Your message dated Mon, 28 Jan 2019 14:09:40 + with message-id <543f694f-7630-beaa-4680-0e63442d4...@tincho.org> and subject line Already fixed has caused the Debian Bug report #886720, regarding /usr/bin/godoc: godoc needs a rebuild against the current golang version to be marked as done.

Bug#918748: marked as done (nmu: kadu_4.1-1.1)

Your message dated Mon, 28 Jan 2019 15:59:21 +0100 with message-id and subject line Re: Bug#918748: nmu: kadu_4.1-1.1 has caused the Debian Bug report #918748, regarding nmu: kadu_4.1-1.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#918415: marked as done (golang-golang-x-tools FTBFS with Go 1.11)

Your message dated Mon, 28 Jan 2019 15:10:45 + with message-id and subject line Bug#918415: fixed in golang-golang-x-tools 1:0.0~git20190125.d66bd3c+ds-1 has caused the Debian Bug report #918415, regarding golang-golang-x-tools FTBFS with Go 1.11 to be marked as done. This means that you

Bug#920685: marked as done (ganeti-2.15: hardcoded MCL_* constants for mlockall are arch-dependent)

Your message dated Mon, 28 Jan 2019 15:08:56 + with message-id and subject line Bug#920685: fixed in ganeti 2.16.0-4 has caused the Debian Bug report #920685, regarding ganeti-2.15: hardcoded MCL_* constants for mlockall are arch-dependent to be marked as done. This means that you claim that

Bug#918374: marked as done (ganeti: FTBFS with Sphinx 1.8: cannot import name Directive)

Your message dated Mon, 28 Jan 2019 15:08:56 + with message-id and subject line Bug#918374: fixed in ganeti 2.16.0-4 has caused the Debian Bug report #918374, regarding ganeti: FTBFS with Sphinx 1.8: cannot import name Directive to be marked as done. This means that you claim that the

Bug#920686: marked as done (ganeti-2.15: hardcoded ioctl constants are not arch-independent, breaking network on powerpc)

Your message dated Mon, 28 Jan 2019 15:08:56 + with message-id and subject line Bug#920686: fixed in ganeti 2.16.0-4 has caused the Debian Bug report #920686, regarding ganeti-2.15: hardcoded ioctl constants are not arch-independent, breaking network on powerpc to be marked as done. This

Bug#920359: marked as done (obitools: ships ecoPCR(1), ecofind(1) manpages already shipped in the ecopcr package)

Your message dated Mon, 28 Jan 2019 15:53:14 + with message-id and subject line Bug#920359: fixed in obitools 1.2.12+dfsg-2 has caused the Debian Bug report #920359, regarding obitools: ships ecoPCR(1), ecofind(1) manpages already shipped in the ecopcr package to be marked as done. This

Bug#917962: marked as done (initscript lacks implementation of aa_log_action_start() and aa_log_action_end())

Your message dated Mon, 28 Jan 2019 18:49:26 + with message-id and subject line Bug#917962: fixed in apparmor 2.13.2-6 has caused the Debian Bug report #917962, regarding initscript lacks implementation of aa_log_action_start() and aa_log_action_end() to be marked as done. This means that

Bug#920715: marked as done (RM: y-u-no-validate/2013052407-3)

Your message dated Mon, 28 Jan 2019 16:31:10 + with message-id <61268cf81718d7600210fd2eca465...@mail.adam-barratt.org.uk> and subject line Re: Bug#920715: RM: y-u-no-validate/2013052407-3 has caused the Debian Bug report #920715, regarding RM: y-u-no-validate/2013052407-3 to be marked as

Bug#920716: marked as done (RM: mozvoikko/2.2-0.1)

Your message dated Mon, 28 Jan 2019 16:30:28 + with message-id and subject line Re: Bug#920716: RM: mozvoikko/2.2-0.1 has caused the Debian Bug report #920716, regarding RM: mozvoikko/2.2-0.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: Re: Bug#911023: memory leak in the backlight control of the dell-laptop module

Processing control commands: > close -1 4.19.16-1 Bug #911023 [src:linux] memory leak in the backlight control of the dell-laptop module Marked as fixed in versions linux/4.19.16-1. Bug #911023 [src:linux] memory leak in the backlight control of the dell-laptop module Marked Bug as done --

Bug#918380: marked as done (FTBFS: test failures with new Web::API)

Your message dated Mon, 28 Jan 2019 17:21:25 + with message-id and subject line Bug#918380: fixed in libmail-chimp3-perl 0.06-1 has caused the Debian Bug report #918380, regarding FTBFS: test failures with new Web::API to be marked as done. This means that you claim that the problem has been

Bug#912220: marked as done (ifupdown: clarify netmask documentation)

Your message dated Mon, 28 Jan 2019 20:53:22 + with message-id and subject line Bug#912220: fixed in ifupdown 0.8.35 has caused the Debian Bug report #912220, regarding ifupdown: clarify netmask documentation to be marked as done. This means that you claim that the problem has been dealt

Bug#906894: marked as done (dhclient should send client id)

Your message dated Mon, 28 Jan 2019 20:53:22 + with message-id and subject line Bug#906894: fixed in ifupdown 0.8.35 has caused the Debian Bug report #906894, regarding dhclient should send client id to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#900269: marked as done (ifupdown: last version breaks upgrade)

Your message dated Mon, 28 Jan 2019 20:53:22 + with message-id and subject line Bug#900269: fixed in ifupdown 0.8.35 has caused the Debian Bug report #900269, regarding ifupdown: last version breaks upgrade to be marked as done. This means that you claim that the problem has been dealt with.

Bug#889525: marked as done (pytsk: Please make build compatible with -Wl,--as-needed)

Your message dated Mon, 28 Jan 2019 18:54:23 + with message-id and subject line Bug#889525: fixed in pytsk 20190121-2 has caused the Debian Bug report #889525, regarding pytsk: Please make build compatible with -Wl,--as-needed to be marked as done. This means that you claim that the problem

Bug#918434: marked as done (golint: FTBFS (failing tests))

Your message dated Mon, 28 Jan 2019 20:53:10 + with message-id and subject line Bug#918434: fixed in golint 0.0+git20181214.8f45f77-1 has caused the Debian Bug report #918434, regarding golint: FTBFS (failing tests) to be marked as done. This means that you claim that the problem has been

Bug#920733: marked as done (freedink: missing Breaks+Replaces: freedink-engine (<< 109.4))

Your message dated Mon, 28 Jan 2019 21:35:29 + with message-id and subject line Bug#920733: fixed in freedink 109.4-2 has caused the Debian Bug report #920733, regarding freedink: missing Breaks+Replaces: freedink-engine (<< 109.4) to be marked as done. This means that you claim that the

Bug#919809: marked as done (freedom-maker: please don't depend on pxz which shall be removed for buster)

Your message dated Mon, 28 Jan 2019 21:35:35 + with message-id and subject line Bug#919809: fixed in freedom-maker 0.23 has caused the Debian Bug report #919809, regarding freedom-maker: please don't depend on pxz which shall be removed for buster to be marked as done. This means that you

Bug#886393: marked as done (doesn't clean up inherited children)

Your message dated Mon, 28 Jan 2019 21:35:02 + with message-id and subject line Bug#886393: fixed in awesome 4.3-1 has caused the Debian Bug report #886393, regarding doesn't clean up inherited children to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#919232: marked as done (wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf)

Your message dated Mon, 28 Jan 2019 22:07:09 + with message-id and subject line Bug#919232: fixed in wireguard 0.0.20190123-1 has caused the Debian Bug report #919232, regarding wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit

Bug#913446: marked as done (wireguard-tools: optionally reload module / interfaces on upgrade)

Your message dated Mon, 28 Jan 2019 22:07:09 + with message-id and subject line Bug#913446: fixed in wireguard 0.0.20190123-1 has caused the Debian Bug report #913446, regarding wireguard-tools: optionally reload module / interfaces on upgrade to be marked as done. This means that you claim

Bug#920289: marked as done (nmu: pandoc-citeproc-preamble_1.2.3)

Your message dated Mon, 28 Jan 2019 20:53:10 +0100 with message-id <6fd0bb8a-be21-7fa7-edfc-054b20a37...@debian.org> and subject line Re: Bug#920289: nmu: pandoc-citeproc-preamble_1.2.3 has caused the Debian Bug report #920289, regarding nmu: pandoc-citeproc-preamble_1.2.3 to be marked as done.

Bug#684920: marked as done (tried to just do NAT, blocks protocol 41)

Your message dated Mon, 28 Jan 2019 23:03:44 +0100 with message-id <7147a5073df6fa526a2afa40d21e9f0a251b54cd.ca...@g-e-u-e-r.de> and subject line Re: Bug#684920: tried to just do NAT, blocks protocol 41 has caused the Debian Bug report #684920, regarding tried to just do NAT, blocks protocol 41 to

Bug#919437: marked as done (winff: [INTL:pt] Updated Portuguese translation - prog messages)

Your message dated Mon, 28 Jan 2019 21:02:30 + with message-id and subject line Bug#919437: fixed in winff 1.5.5-6 has caused the Debian Bug report #919437, regarding winff: [INTL:pt] Updated Portuguese translation - prog messages to be marked as done. This means that you claim that the

Bug#919042: marked as done (This is not exactly a "metapackge" :-))

Your message dated Mon, 28 Jan 2019 21:02:30 + with message-id and subject line Bug#919042: fixed in winff 1.5.5-6 has caused the Debian Bug report #919042, regarding This is not exactly a "metapackge" :-) to be marked as done. This means that you claim that the problem has been dealt with.

Bug#913589: marked as done (pqiv FTCBFS: builds for the wrong architecture)

Your message dated Mon, 28 Jan 2019 22:19:46 +0100 with message-id and subject line has caused the Debian Bug report #913589, regarding pqiv FTCBFS: builds for the wrong architecture to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#388267: marked as done (texlive-latex-recommanded: problem with subfig and beamer)

Your message dated Mon, 28 Jan 2019 21:23:09 +0100 with message-id <587090af-c55f-76f8-86fa-b882892e8...@web.de> and subject line Re: Bug#388267: Info received (Bug#388267: texlive-latex-recommanded: problem with subfig and beamer) has caused the Debian Bug report #388267, regarding

Bug#916814: marked as done (cacti: [1.2.0 Beta 4] Spike Kill not working (missing file))

Your message dated Mon, 28 Jan 2019 20:51:38 + with message-id and subject line Bug#916814: fixed in cacti 1.2.1+ds1-1 has caused the Debian Bug report #916814, regarding cacti: [1.2.0 Beta 4] Spike Kill not working (missing file) to be marked as done. This means that you claim that the

Bug#919817: marked as done (mysql-5.7: Security fixes from the January 2019 CPU)

Your message dated Mon, 28 Jan 2019 20:56:52 + with message-id and subject line Bug#919817: fixed in mysql-5.7 5.7.25-1 has caused the Debian Bug report #919817, regarding mysql-5.7: Security fixes from the January 2019 CPU to be marked as done. This means that you claim that the problem has

Bug#894710: marked as done (awesome: move out of asciidoc)

Your message dated Mon, 28 Jan 2019 21:35:02 + with message-id and subject line Bug#894710: fixed in awesome 4.3-1 has caused the Debian Bug report #894710, regarding awesome: move out of asciidoc to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#857191: marked as done (jabberd2: service file uses deprecated BindTo=)

Your message dated Mon, 28 Jan 2019 22:24:50 + with message-id and subject line Bug#857191: fixed in jabberd2 2.7.0-1 has caused the Debian Bug report #857191, regarding jabberd2: service file uses deprecated BindTo= to be marked as done. This means that you claim that the problem has been

Bug#917758: marked as done (jabberd2: FTBFS: mysql-related errors)

Your message dated Mon, 28 Jan 2019 22:24:50 + with message-id and subject line Bug#917758: fixed in jabberd2 2.7.0-1 has caused the Debian Bug report #917758, regarding jabberd2: FTBFS: mysql-related errors to be marked as done. This means that you claim that the problem has been dealt

Bug#903751: marked as done (basket: please remove the extra libsoprano-dev build dependency)

Your message dated Tue, 29 Jan 2019 02:46:08 + with message-id and subject line Bug#903751: fixed in basket 2.11~beta+git20180715.058ce7a-1 has caused the Debian Bug report #903751, regarding basket: please remove the extra libsoprano-dev build dependency to be marked as done. This means

Bug#919780: marked as done (Please provide compatibility link under /usr/lib/rustlib/src)

Your message dated Tue, 29 Jan 2019 02:56:00 + with message-id <04f124bf-2735-9e2d-d9fb-441e87a1e...@debian.org> and subject line Re: Please provide compatibility link under /usr/lib/rustlib/src has caused the Debian Bug report #919780, regarding Please provide compatibility link under

Bug#912310: marked as done (erlang-erlware-commons FTBFS: ERROR: eunit failed while processing /<>/erlang-erlware-commons-1.2.0+dfsg: rebar_abort)

Your message dated Tue, 29 Jan 2019 03:19:45 + with message-id and subject line Bug#912310: fixed in erlang-erlware-commons 1.3.1+dfsg-1 has caused the Debian Bug report #912310, regarding erlang-erlware-commons FTBFS: ERROR: eunit failed while processing

Bug#920652: marked as done (ublock-origin: host list is not displayed, blocking does not seem to work)

Your message dated Mon, 28 Jan 2019 23:09:19 + with message-id and subject line Bug#920652: fixed in ublock-origin 1.18.2+dfsg-2 has caused the Debian Bug report #920652, regarding ublock-origin: host list is not displayed, blocking does not seem to work to be marked as done. This means

Bug#920757: marked as done (please update package)

Your message dated Tue, 29 Jan 2019 01:04:39 + with message-id and subject line Bug#920757: fixed in social-auth-core 3.0.0-1 has caused the Debian Bug report #920757, regarding please update package to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#920703: marked as done (RM: mysql-connector-java -- ROM; replaced by mariadb-connector-java)

Your message dated Tue, 29 Jan 2019 01:06:36 + with message-id and subject line Bug#920703: Removed package(s) from unstable has caused the Debian Bug report #920703, regarding RM: mysql-connector-java -- ROM; replaced by mariadb-connector-java to be marked as done. This means that you claim

Bug#920721: marked as done (RM: requestpolicy -- RoQA; Broken with Firefox Quantum, unmaintained)

Your message dated Tue, 29 Jan 2019 01:07:06 + with message-id and subject line Bug#920721: Removed package(s) from unstable has caused the Debian Bug report #920721, regarding RM: requestpolicy -- RoQA; Broken with Firefox Quantum, unmaintained to be marked as done. This means that you

Bug#920729: marked as done (RM: apmd -- RoQA; Broken, unmaintained)

Your message dated Tue, 29 Jan 2019 01:07:55 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #920729, regarding RM: apmd -- RoQA; Broken, unmaintained to be marked as done. This means that you claim that the problem has been

Bug#828836: marked as done (libmysql-java: ClassNotFound exception IF running in a v8 JVM)

Your message dated Tue, 29 Jan 2019 01:06:42 + with message-id and subject line Bug#920703: Removed package(s) from unstable has caused the Debian Bug report #828836, regarding libmysql-java: ClassNotFound exception IF running in a v8 JVM to be marked as done. This means that you claim that

Bug#135557: marked as done (libapm1: should have bsd support)

Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #135557, regarding libapm1: should have bsd support to be marked as done. This means that you claim that the problem has been dealt

Bug#920233: marked as done (evince: Add Illustrator (.ai) files to AppArmor profile)

Your message dated Tue, 29 Jan 2019 01:04:15 + with message-id and subject line Bug#920233: fixed in evince 3.30.2-3 has caused the Debian Bug report #920233, regarding evince: Add Illustrator (.ai) files to AppArmor profile to be marked as done. This means that you claim that the problem

Bug#853992: marked as done (xul-ext-requestpolicy: update requestpolicy to 1.0 beta12.4 - compatibility with web extensions)

Your message dated Tue, 29 Jan 2019 01:07:13 + with message-id and subject line Bug#920721: Removed package(s) from unstable has caused the Debian Bug report #853992, regarding xul-ext-requestpolicy: update requestpolicy to 1.0 beta12.4 - compatibility with web extensions to be marked as

Bug#907712: marked as done (src:requestpolicy: please package upstream version 1.0.beta13.2)

Your message dated Tue, 29 Jan 2019 01:07:13 + with message-id and subject line Bug#920721: Removed package(s) from unstable has caused the Debian Bug report #907712, regarding src:requestpolicy: please package upstream version 1.0.beta13.2 to be marked as done. This means that you claim

Bug#912916: marked as done (mysql-connector-java: removal from Debian)

Your message dated Tue, 29 Jan 2019 01:06:42 + with message-id and subject line Bug#920703: Removed package(s) from unstable has caused the Debian Bug report #912916, regarding mysql-connector-java: removal from Debian to be marked as done. This means that you claim that the problem has been

Bug#118797: marked as done (Please handle multiple batteries (e.g., on Sony VAIO))

Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #118797, regarding Please handle multiple batteries (e.g., on Sony VAIO) to be marked as done. This means that you claim that the

Bug#870607: marked as done (xul-ext-requestpolicy: Please update to 1.0.beta13.0)

Your message dated Tue, 29 Jan 2019 01:07:13 + with message-id and subject line Bug#920721: Removed package(s) from unstable has caused the Debian Bug report #870607, regarding xul-ext-requestpolicy: Please update to 1.0.beta13.0 to be marked as done. This means that you claim that the

Bug#100026: marked as done (Please document the apmlib API)

Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #100026, regarding Please document the apmlib API to be marked as done. This means that you claim that the problem has been dealt

Bug#228615: marked as done (please split out apmd_proxy)

Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #228615, regarding please split out apmd_proxy to be marked as done. This means that you claim that the problem has been dealt with.

Bug#134595: marked as done (apmd: please make /usr/bin/apm suid root)

Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #134595, regarding apmd: please make /usr/bin/apm suid root to be marked as done. This means that you claim that the problem has been

Bug#222759: marked as done (apmd: Curious messages from "apm" command)

Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #222759, regarding apmd: Curious messages from "apm" command to be marked as done. This means that you claim that the problem has been

Bug#231238: marked as done (apmd 3.2.1-2 suspend the system as soon as it has not been used for a few minutes)

Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #231238, regarding apmd 3.2.1-2 suspend the system as soon as it has not been used for a few minutes to be marked as done. This means

Bug#918370: marked as done (Krita crashes with Qt 5.11.3 using tablet input)

Your message dated Mon, 28 Jan 2019 22:53:39 -0300 with message-id <22461097.NLPhRp2Yoe@tonks> and subject line Really closing. has caused the Debian Bug report #918370, regarding Krita crashes with Qt 5.11.3 using tablet input to be marked as done. This means that you claim that the problem has

Bug#911151: marked as done (python-boto3: Please update to newer upstream version)

Your message dated Mon, 28 Jan 2019 23:38:31 + with message-id and subject line Bug#911151: fixed in python-boto3 1.9.86-1 has caused the Debian Bug report #911151, regarding python-boto3: Please update to newer upstream version to be marked as done. This means that you claim that the

Bug#913944: marked as done (flare-game: Loosing skill on load / level up / death)

Your message dated Tue, 29 Jan 2019 00:04:44 + with message-id and subject line Bug#913944: fixed in flare-engine 1.09.01-1 has caused the Debian Bug report #913944, regarding flare-game: Loosing skill on load / level up / death to be marked as done. This means that you claim that the

Bug#918814: marked as done (dot2tex: FTBFS with Sphinx 1.8: No module named pngmath)

Your message dated Tue, 29 Jan 2019 05:19:11 + with message-id and subject line Bug#918814: fixed in dot2tex 2.9.0-3 has caused the Debian Bug report #918814, regarding dot2tex: FTBFS with Sphinx 1.8: No module named pngmath to be marked as done. This means that you claim that the problem

Bug#919623: marked as done (Remote code execution in scp support)

Your message dated Tue, 29 Jan 2019 05:50:04 + with message-id and subject line Bug#919623: fixed in rssh 2.3.4-9 has caused the Debian Bug report #919623, regarding Remote code execution in scp support to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#919442: marked as done (python-dmidecode-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

Your message dated Tue, 29 Jan 2019 05:19:37 + with message-id and subject line Bug#919442: fixed in python-dmidecode 3.12.2-7 has caused the Debian Bug report #919442, regarding python-dmidecode-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE to be marked as done.

  1   2   >