Bug#875505: marked as done (doxygen: build-dependency ruby-compass obsolete and broken)

Your message dated Mon, 12 Mar 2018 09:20:37 + with message-id and subject line Bug#875505: fixed in doxygen 1.8.13-10 has caused the Debian Bug report #875505, regarding doxygen: build-dependency ruby-compass obsolete and broken to be marked as done.

Bug#892695: marked as done ([node-acorn] Create failure in other package)

Your message dated Mon, 12 Mar 2018 11:06:55 +0100 with message-id

Bug#880789: marked as done (xf86-input-multitouch FTCBFS: uses the build architecture compiler)

Your message dated Mon, 12 Mar 2018 06:04:12 + with message-id and subject line Bug#880789: fixed in xf86-input-multitouch 1.0~rc3-2 has caused the Debian Bug report #880789, regarding xf86-input-multitouch FTCBFS: uses the build architecture compiler to

Bug#892699: marked as done (doris: switch B-D to libepr-api-dev)

Your message dated Mon, 12 Mar 2018 06:49:19 + with message-id and subject line Bug#892699: fixed in doris 5.0.3~beta+dfsg-4 has caused the Debian Bug report #892699, regarding doris: switch B-D to libepr-api-dev to be marked as done. This means that you

Bug#880014: marked as done (2018 - New TC member)

Your message dated Mon, 12 Mar 2018 08:34:02 +0100 with message-id <1827597.wfcqqap...@odyx.org> and subject line Re: Bug#880014: Call for Votes for new TC member has caused the Debian Bug report #880014, regarding 2018 - New TC member to be marked as done. This means that you claim that the

Bug#891951: marked as done (python3-neutron-fwaas: mentions Python 2.x in the package description)

Your message dated Mon, 12 Mar 2018 09:25:57 + with message-id and subject line Bug#891951: fixed in neutron-fwaas 1:12.0.0-2 has caused the Debian Bug report #891951, regarding python3-neutron-fwaas: mentions Python 2.x in the package description to be

Bug#891949: marked as done (python3-neutron-dynamic-routing: mentions Python 2.x in the package description)

Your message dated Mon, 12 Mar 2018 09:25:46 + with message-id and subject line Bug#891949: fixed in neutron-dynamic-routing 2:12.0.0-2 has caused the Debian Bug report #891949, regarding python3-neutron-dynamic-routing: mentions Python 2.x in the package

Bug#892670: marked as done (Updating the d-feet Uploaders list)

Your message dated Mon, 12 Mar 2018 09:20:28 + with message-id and subject line Bug#892670: fixed in d-feet 0.3.13-2 has caused the Debian Bug report #892670, regarding Updating the d-feet Uploaders list to be marked as done. This means that you claim

Bug#863528: marked as done (dacs: building documentation spews lots of warnings about missing stylesheet)

Your message dated Mon, 12 Mar 2018 09:50:25 + with message-id and subject line Bug#863528: fixed in dacs 1.4.40-1 has caused the Debian Bug report #863528, regarding dacs: building documentation spews lots of warnings about missing stylesheet to be

Bug#888167: marked as done (ruby-recursive-open-struct: FTBFS on ruby2.5: indifferent access overwriting values)

Your message dated Mon, 12 Mar 2018 07:49:50 + with message-id and subject line Bug#888167: fixed in ruby-recursive-open-struct 1.1.0-1 has caused the Debian Bug report #888167, regarding ruby-recursive-open-struct: FTBFS on ruby2.5: indifferent access

Bug#892718: marked as done (pdns-server: Security status polling on 4.0.3-1+deb9u2 fails: Non-Existent domain)

Your message dated Mon, 12 Mar 2018 09:40:07 +0100 with message-id <20180312084006.GA28856@tx.local> and subject line Re: Bug#892718: pdns-server: Security status polling on 4.0.3-1+deb9u2 fails: Non-Existent domain has caused the Debian Bug report #892718, regarding pdns-server: Security status

Bug#886853: marked as done (mariadb-plugin-rocksdb,rocksdb-tools: both ship /usr/bin/sst_dump)

Your message dated Mon, 12 Mar 2018 09:45:16 +0100 with message-id and subject line Re: Bug#886853: [debian-mysql] Bug#886853: mariadb-plugin-rocksdb, rocksdb-tools: both ship /usr/bin/sst_dump has caused the Debian Bug report

Bug#892719: marked as done (gcc-7: internal compiler error: unexpected expression ‘I’ of kind template_parm_index -- fixed upstream)

Your message dated Mon, 12 Mar 2018 09:46:55 +0100 with message-id <3088aaa1-4e64-bfe9-099a-5c259f795...@debian.org> and subject line Re: Bug#892719: gcc-7: internal compiler error: unexpected expression ‘I’ of kind template_parm_index -- fixed upstream has caused the Debian Bug report #892719,

Bug#891539: marked as done (python-murano-pkg-check FTBFS: test failures)

Your message dated Mon, 12 Mar 2018 09:56:10 + with message-id and subject line Bug#891539: fixed in openstack-pkg-tools 72 has caused the Debian Bug report #891539, regarding python-murano-pkg-check FTBFS: test failures to be marked as done. This means

Bug#892619: marked as done (RFS: pidgin-sipe/1.23.2-1 -- Pidgin plugin for Skype for Business and Microsoft Lync)

Your message dated Mon, 12 Mar 2018 11:45:53 +0100 with message-id <4676bf78-236b-51e7-5e88-2c4a1789c...@debian.org> and subject line Re: RFS: pidgin-sipe/1.23.2-1 -- Pidgin plugin for Skype for Business and Microsoft Lync has caused the Debian Bug report #892619, regarding RFS:

Bug#892660: marked as done (RFS: diodon/1.8.0-1)

Your message dated Mon, 12 Mar 2018 11:50:29 +0100 with message-id and subject line Re: Subject: RFS: diodon/1.8.0-1 has caused the Debian Bug report #892660, regarding RFS: diodon/1.8.0-1 to be marked as done. This means that you claim that the

Bug#676550: marked as done (RFP: libcatalyst-plugin-compress-zlib-perl -- Zlib Compression for Catalyst)

Your message dated Mon, 12 Mar 2018 10:20:03 + with message-id and subject line closing RFP: libcatalyst-plugin-compress-zlib-perl -- Zlib Compression for Catalyst has caused the Debian Bug report #676550, regarding RFP:

Processed: Close the correct bug

Processing commands for cont...@bugs.debian.org: > notfixed 891539 openstack-pkg-tools/72 Bug #891539 {Done: Thomas Goirand } [src:python-murano-pkg-check] python-murano-pkg-check FTBFS: test failures No longer marked as fixed in versions openstack-pkg-tools/72. > close 892697

Bug#889078: marked as done (beets: autopkgtest failure)

Your message dated Mon, 12 Mar 2018 11:04:17 + with message-id and subject line Bug#889078: fixed in beets 1.4.6-1.1 has caused the Debian Bug report #889078, regarding beets: autopkgtest failure to be marked as done. This means that you claim that the

Bug#848239: marked as done (deluser on purge)

Your message dated Mon, 12 Mar 2018 11:04:48 + with message-id and subject line Bug#848239: fixed in dh-sysuser 1.3.1 has caused the Debian Bug report #848239, regarding deluser on purge to be marked as done. This means that you claim that the problem has

Bug#848240: marked as done (missing documentation: password? shell?)

Your message dated Mon, 12 Mar 2018 11:04:48 + with message-id and subject line Bug#848240: fixed in dh-sysuser 1.3.1 has caused the Debian Bug report #848240, regarding missing documentation: password? shell? to be marked as done. This means that you

Bug#844342: marked as done (sysuser-helper: Typo in package description)

Your message dated Mon, 12 Mar 2018 11:04:48 + with message-id and subject line Bug#844342: fixed in dh-sysuser 1.3.1 has caused the Debian Bug report #844342, regarding sysuser-helper: Typo in package description to be marked as done. This means that you

Bug#891628: marked as done (diodon: Fails to build with vala 0.40)

Your message dated Mon, 12 Mar 2018 11:04:56 + with message-id and subject line Bug#891628: fixed in diodon 1.8.0-1 has caused the Debian Bug report #891628, regarding diodon: Fails to build with vala 0.40 to be marked as done. This means that you claim

Bug#891005: marked as done (RFS: gdbm/1.14.1-5 )

Your message dated Mon, 12 Mar 2018 12:04:01 +0100 with message-id <48439641-2674-a2f4-d876-a8634b665...@debian.org> and subject line Re: New version has caused the Debian Bug report #891005, regarding RFS: gdbm/1.14.1-5 to be marked as done. This means that you claim that the problem has been

Bug#889761: marked as done (Updating the beets Uploaders list)

Your message dated Mon, 12 Mar 2018 11:04:17 + with message-id and subject line Bug#889761: fixed in beets 1.4.6-1.1 has caused the Debian Bug report #889761, regarding Updating the beets Uploaders list to be marked as done. This means that you claim that

Bug#891376: marked as done (libgdbm-dev: headers (and other) files missing)

Your message dated Mon, 12 Mar 2018 11:19:37 + with message-id and subject line Bug#891376: fixed in gdbm 1.14.1-5 has caused the Debian Bug report #891376, regarding libgdbm-dev: headers (and other) files missing to be marked as done. This means that you

Bug#340479: marked as done (noffle: problems with largefile limit)

Your message dated Mon, 12 Mar 2018 11:19:37 + with message-id and subject line Bug#340479: fixed in gdbm 1.14.1-5 has caused the Debian Bug report #340479, regarding noffle: problems with largefile limit to be marked as done. This means that you claim

Bug#892710: marked as done ({tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc})

Your message dated Mon, 12 Mar 2018 10:36:31 + with message-id and subject line Bug#892710: fixed in itk4 4.1.0-2 has caused the Debian Bug report #892710, regarding {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc} to be marked as

Bug#375500: marked as done (xchat: please don't depend on gconf2)

Your message dated Mon, 12 Mar 2018 11:06:26 + with message-id and subject line Bug#375500: fixed in xchat 2.8.8-14 has caused the Debian Bug report #375500, regarding xchat: please don't depend on gconf2 to be marked as done. This means that you claim

Bug#392251: marked as done (xchat: please don't depend on gconf2)

Your message dated Mon, 12 Mar 2018 11:06:26 + with message-id and subject line Bug#375500: fixed in xchat 2.8.8-14 has caused the Debian Bug report #375500, regarding xchat: please don't depend on gconf2 to be marked as done. This means that you claim

Bug#718837: marked as done (openshot: closes with Gtk:ERROR)

Your message dated Mon, 12 Mar 2018 13:28:17 +0100 with message-id <9e54277b-b267-dd50-c59f-c033f633f...@debian.org> and subject line This bug is probably no longer relevant has caused the Debian Bug report #718837, regarding openshot: closes with Gtk:ERROR to be marked as done. This means that

Bug#695981: marked as done (openshot: Warning about reserved word when upgrading to wheezy)

Your message dated Mon, 12 Mar 2018 13:26:52 +0100 with message-id and subject line This bug is probably no longer relevant has caused the Debian Bug report #695981, regarding openshot: Warning about reserved word when upgrading to wheezy to be

Bug#892710: marked as done ({tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc})

Your message dated Mon, 12 Mar 2018 10:36:20 + with message-id and subject line Bug#892710: fixed in itcl4 4.1.1-2 has caused the Debian Bug report #892710, regarding {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc} to be marked as

Bug#892634: marked as done (RFS: dh-runit/2.7.1 )

Your message dated Mon, 12 Mar 2018 12:00:48 +0100 with message-id and subject line Re: RFS: dh-runit/2.7.1 has caused the Debian Bug report #892634, regarding RFS: dh-runit/2.7.1 to be marked as done. This means that you claim that the problem

Bug#877553: marked as done (sensible-utils: [INTL:de] updated German man page translation)

Your message dated Mon, 12 Mar 2018 12:55:09 + with message-id and subject line Bug#877553: fixed in sensible-utils 0.0.12 has caused the Debian Bug report #877553, regarding sensible-utils: [INTL:de] updated German man page translation to be marked as

Bug#892460: marked as done (ruby-parslet: FTBFS and Debci failure with Ruby 2.5)

Your message dated Mon, 12 Mar 2018 12:55:04 + with message-id and subject line Bug#892460: fixed in ruby-parslet 1.8.2-2 has caused the Debian Bug report #892460, regarding ruby-parslet: FTBFS and Debci failure with Ruby 2.5 to be marked as done. This

Bug#885688: marked as done (sensible-utils: sensible-browser launches $BROWSER with empty argument)

Your message dated Mon, 12 Mar 2018 12:55:09 + with message-id and subject line Bug#885688: fixed in sensible-utils 0.0.12 has caused the Debian Bug report #885688, regarding sensible-utils: sensible-browser launches $BROWSER with empty argument to be

Bug#885816: marked as done (racket: Recommends libunique)

Your message dated Mon, 12 Mar 2018 10:22:48 + with message-id and subject line Bug#885816: fixed in racket 6.12+dfsg1-1 has caused the Debian Bug report #885816, regarding racket: Recommends libunique to be marked as done. This means that you claim that

Bug#886315: marked as done (libc6-dev-$arch-cross incompatible with libc6-dev:$arch: glibc major version skew)

Your message dated Mon, 12 Mar 2018 12:19:30 + with message-id and subject line Bug#886315: fixed in cross-toolchain-base 23 has caused the Debian Bug report #886315, regarding libc6-dev-$arch-cross incompatible with libc6-dev:$arch: glibc major version

Bug#858819: marked as done (Typo causes error with Trac 1.2)

Your message dated Mon, 12 Mar 2018 17:49:10 + with message-id and subject line Bug#858819: fixed in email2trac 2.10.0-2 has caused the Debian Bug report #858819, regarding Typo causes error with Trac 1.2 to be marked as done. This means that you claim

Bug#891381: marked as done (undertime: prints terminal escape sequences to pipes/files)

Your message dated Mon, 12 Mar 2018 18:04:51 + with message-id and subject line Bug#891381: fixed in undertime 1.3.0 has caused the Debian Bug report #891381, regarding undertime: prints terminal escape sequences to pipes/files to be marked as done. This

Bug#892639: marked as done (Update version of python-nacl)

Your message dated Mon, 12 Mar 2018 13:20:24 + with message-id and subject line Bug#892637: fixed in python-nacl 1.2.1-1 has caused the Debian Bug report #892637, regarding Update version of python-nacl to be marked as done. This means that you claim that

Bug#863425: marked as done (latex2html: stops with error message: Can't use 'defined(@array)')

Your message dated Mon, 12 Mar 2018 15:03:44 +0100 with message-id <87ina1pf0f@arioch.leonhardt.eu> and subject line Fixed in v2018 has caused the Debian Bug report #863425, regarding latex2html: stops with error message: Can't use 'defined(@array)' to be marked as done. This means that you

Bug#892462: marked as done (PROJ 5.0.0 causes regression in python-mpop)

Your message dated Mon, 12 Mar 2018 15:34:44 +0100 with message-id <3fd0e8a8c4fe85b287ad0626dc808...@xs4all.nl> and subject line python-mpop FTBFS and Debci failure: FAIL: test_boundaries_to_extent (mpop.tests.test_satin_helpers.TestSatinHelpers) has caused the Debian Bug report #892462,

Bug#886315: marked as done (libc6-dev-$arch-cross incompatible with libc6-dev:$arch: glibc major version skew)

Your message dated Mon, 12 Mar 2018 15:07:14 + with message-id and subject line Bug#886315: fixed in cross-toolchain-base 24 has caused the Debian Bug report #886315, regarding libc6-dev-$arch-cross incompatible with libc6-dev:$arch: glibc major version

Bug#875357: marked as done (FTBFS with Java 9: sun..spi removed)

Your message dated Mon, 12 Mar 2018 15:07:26 + with message-id and subject line Bug#875357: fixed in dnsjava 2.1.8-2 has caused the Debian Bug report #875357, regarding FTBFS with Java 9: sun..spi removed to be marked as done. This means that you claim

Bug#892637: marked as done (Update version of python-nacl)

Your message dated Mon, 12 Mar 2018 13:20:24 + with message-id and subject line Bug#892637: fixed in python-nacl 1.2.1-1 has caused the Debian Bug report #892637, regarding Update version of python-nacl to be marked as done. This means that you claim that

Bug#792738: marked as done (tracker.debian.org: please display transitive package that are getting removed too)

Your message dated Mon, 12 Mar 2018 13:25:02 + with message-id <5aa67faeae499_3332ad5b8c5f0e096...@godard.mail> and subject line Bug #792738 in tracker.debian.org fixed has caused the Debian Bug report #792738, regarding tracker.debian.org: please display transitive package that are getting

Bug#873214: marked as done (FTBFS with Java 9)

Your message dated Mon, 12 Mar 2018 13:50:53 + with message-id and subject line Bug#873214: fixed in findbugs 3.1.0~preview2-3 has caused the Debian Bug report #873214, regarding FTBFS with Java 9 to be marked as done. This means that you claim that the

Bug#874213: marked as done (mercurial: please Build-Depend on rename)

Your message dated Mon, 12 Mar 2018 18:00:53 +0200 with message-id <20180312160052.GG20833@localhost> and subject line Already fixed since 4.4.1-1 has caused the Debian Bug report #874213, regarding mercurial: please Build-Depend on rename to be marked as done. This means that you claim that the

Bug#874134: marked as done (FTBFS with Java 9: cannot find -ljawt)

Your message dated Mon, 12 Mar 2018 17:20:13 + with message-id and subject line Bug#874134: fixed in swt4-gtk 4.6.3-2 has caused the Debian Bug report #874134, regarding FTBFS with Java 9: cannot find -ljawt to be marked as done. This means that you claim

Bug#870064: marked as done (redir: service names from /etc/services not recognized anymore for --lport=)

Your message dated Mon, 12 Mar 2018 17:20:03 + with message-id and subject line Bug#870064: fixed in redir 3.2-1 has caused the Debian Bug report #870064, regarding redir: service names from /etc/services not recognized anymore for --lport= to be marked

Bug#892581: marked as done (RFS: dh-sysuser/1.3.1 )

Your message dated Mon, 12 Mar 2018 11:59:45 +0100 with message-id and subject line RFS: dh-sysuser/1.3.1 has caused the Debian Bug report #892581, regarding RFS: dh-sysuser/1.3.1 to be marked as done. This means that you claim that the problem

Bug#802307: marked as done (gnucap: No works)

Your message dated Mon, 12 Mar 2018 11:30:48 + with message-id <20180312113048.bfqg2k654no77...@tba.dn.lab> and subject line close invalid has caused the Debian Bug report #802307, regarding gnucap: No works to be marked as done. This means that you claim that the problem has been dealt with.

Bug#871883: marked as done (rome: Please update the Uploaders list)

Your message dated Mon, 12 Mar 2018 11:50:22 + with message-id and subject line Bug#871883: fixed in rome 1.0-7 has caused the Debian Bug report #871883, regarding rome: Please update the Uploaders list to be marked as done. This means that you claim that

Bug#873308: marked as done (Please update: FTBFS with Java 9)

Your message dated Mon, 12 Mar 2018 11:50:22 + with message-id and subject line Bug#873308: fixed in rome 1.0-7 has caused the Debian Bug report #873308, regarding Please update: FTBFS with Java 9 to be marked as done. This means that you claim that the

Bug#892736: marked as done (udev: systemd-udevd.service include is wrong)

Your message dated Mon, 12 Mar 2018 13:14:11 +0100 with message-id and subject line Re: Bug#892736: udev: systemd-udevd.service include is wrong has caused the Debian Bug report #892736, regarding udev: systemd-udevd.service include is wrong to be

Bug#651591: marked as done (openshot: Openshot doesn't have a GTK3 interface yet)

Your message dated Mon, 12 Mar 2018 13:35:34 +0100 with message-id <27fc8d28-7ea5-db02-73b4-bccaf3dd0...@debian.org> and subject line This bug is probably no longer relevant has caused the Debian Bug report #651591, regarding openshot: Openshot doesn't have a GTK3 interface yet to be marked as

Bug#738697: marked as done (few bugs in 1.4.3 which were fixed post-release upstream (blender effects, saving to Desktop))

Your message dated Mon, 12 Mar 2018 13:33:47 +0100 with message-id <573a3bbf-323d-a2bb-e492-f91cfa62a...@debian.org> and subject line This bug is probably no longer relevant has caused the Debian Bug report #738697, regarding few bugs in 1.4.3 which were fixed post-release upstream (blender

Bug#892659: marked as done (rxvt-unicode better wheel scrolling patch)

Your message dated Mon, 12 Mar 2018 12:47:18 -0400 with message-id <20180312164718.gb4rq6rinrkax...@zeta.ryanak.ca> and subject line Re: Bug#892659: rxvt-unicode better wheel scrolling patch has caused the Debian Bug report #892659, regarding rxvt-unicode better wheel scrolling patch to be marked

Bug#852236: marked as done (redir: New upstream release, v3.1, fixes vagrant-lxc compat issue)

Your message dated Mon, 12 Mar 2018 13:51:54 -0300 with message-id <1520873514.23586.7.ca...@debian.org> and subject line redir: New upstream release, v3.1, fixes vagrant-lxc compat issue has caused the Debian Bug report #852236, regarding redir: New upstream release, v3.1, fixes vagrant-lxc

Bug#892643: marked as done (deepin-image-viewer FTBFS with libdtkwidget-dev 2.0.7-1)

Your message dated Tue, 13 Mar 2018 03:34:27 + with message-id and subject line Bug#892643: fixed in deepin-image-viewer 1.2.16.9-1 has caused the Debian Bug report #892643, regarding deepin-image-viewer FTBFS with libdtkwidget-dev 2.0.7-1 to be marked as

Bug#839640: marked as done (beets: add python-jellyfish dependency)

Your message dated Mon, 12 Mar 2018 15:20:13 -0700 with message-id <2018031013.6d2fqoq3gb6ub...@smetana.kardiogramm.net> and subject line Re: Bug#839640: beets: add python-jellyfish dependency has caused the Debian Bug report #839640, regarding beets: add python-jellyfish dependency to be

Bug#892483: marked as done (RFS: ccrypt/1.10-5 [ITA] -- secure encryption and decryption of files and streams)

Your message dated Mon, 12 Mar 2018 22:32:59 + with message-id and subject line closing RFS: ccrypt/1.10-5 [ITA] -- secure encryption and decryption of files and streams has caused the Debian Bug report #892483, regarding RFS: ccrypt/1.10-5 [ITA] --

Bug#891511: marked as done (ip route flush all does not work any more)

Your message dated Mon, 12 Mar 2018 23:23:31 + with message-id and subject line Bug#891511: fixed in iproute2 4.15.0-3 has caused the Debian Bug report #891511, regarding ip route flush all does not work any more to be marked as done. This means that you

Processed: closing 888050

Processing commands for cont...@bugs.debian.org: > close 888050 Bug #888050 [network-manager] network-manager: Debian Unstable network-manager 1.10.2-3 does not complete processing Bug #888285 [network-manager] network-manager: Upgrade fails (new version cannot restart). Marked Bug as done

Bug#704204: marked as done (gnome-keyring doesn't work with ecdsa keys)

Your message dated Tue, 13 Mar 2018 00:49:30 + with message-id and subject line Bug#704204: fixed in gnome-keyring 3.28.0-1 has caused the Debian Bug report #704204, regarding gnome-keyring doesn't work with ecdsa keys to be marked as done. This means

Bug#783961: marked as done (gnome-keyring: Split gnome-keyring-pkcs11.so into separate package)

Your message dated Tue, 13 Mar 2018 00:49:30 + with message-id and subject line Bug#783961: fixed in gnome-keyring 3.28.0-1 has caused the Debian Bug report #783961, regarding gnome-keyring: Split gnome-keyring-pkcs11.so into separate package to be marked

Processed: closing 749927

Processing commands for cont...@bugs.debian.org: > close 749927 Bug #749927 [network-manager] network-manager: segfault in libc-2.18.so Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 749927:

Bug#883359: marked as done (at-spi2-core: please make the build reproducible)

Your message dated Tue, 13 Mar 2018 01:19:30 + with message-id and subject line Bug#883359: fixed in at-spi2-core 2.28.0-1 has caused the Debian Bug report #883359, regarding at-spi2-core: please make the build reproducible to be marked as done. This

Bug#801384: marked as done (cron boot order is wrong with systemd, cronatbs ignored because non-local users are not known)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#801384: fixed in cron 3.0pl1-130 has caused the Debian Bug report #801384, regarding cron boot order is wrong with systemd, cronatbs ignored because non-local users are

Bug#757191: marked as done (morning warning needed on man page)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#757191: fixed in cron 3.0pl1-130 has caused the Debian Bug report #757191, regarding morning warning needed on man page to be marked as done. This means that you claim

Bug#892724: marked as done (cron: warning from postinst script)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#892721: fixed in cron 3.0pl1-130 has caused the Debian Bug report #892721, regarding cron: warning from postinst script to be marked as done. This means that you claim

Bug#840601: marked as done (cron: document cron dom-dow bug)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#840601: fixed in cron 3.0pl1-130 has caused the Debian Bug report #840601, regarding cron: document cron dom-dow bug to be marked as done. This means that you claim that

Bug#783665: marked as done (cron does not execute some non-root cron.d jobs when started before ypbind)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#783665: fixed in cron 3.0pl1-130 has caused the Debian Bug report #783665, regarding cron does not execute some non-root cron.d jobs when started before ypbind to be

Bug#792572: marked as done (cron: Some improvements for crontab.5)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#792572: fixed in cron 3.0pl1-130 has caused the Debian Bug report #792572, regarding cron: Some improvements for crontab.5 to be marked as done. This means that you claim

Bug#892721: marked as done (cron: Warning during installation)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#892720: fixed in cron 3.0pl1-130 has caused the Debian Bug report #892720, regarding cron: Warning during installation to be marked as done. This means that you claim that

Bug#892724: marked as done (cron: warning from postinst script)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#892724: fixed in cron 3.0pl1-130 has caused the Debian Bug report #892724, regarding cron: warning from postinst script to be marked as done. This means that you claim

Bug#834728: marked as done (cron: enable restarts under systemd)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#834728: fixed in cron 3.0pl1-130 has caused the Debian Bug report #834728, regarding cron: enable restarts under systemd to be marked as done. This means that you claim

Bug#767016: marked as done (cron does start before sssd and therefore authentication fails)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#767016: fixed in cron 3.0pl1-130 has caused the Debian Bug report #767016, regarding cron does start before sssd and therefore authentication fails to be marked as done.

Bug#705570: marked as done (Please provide a more descriptive documentation comment in /etc/crontab)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#705570: fixed in cron 3.0pl1-130 has caused the Debian Bug report #705570, regarding Please provide a more descriptive documentation comment in /etc/crontab to be marked

Bug#892724: marked as done (cron: warning from postinst script)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#892720: fixed in cron 3.0pl1-130 has caused the Debian Bug report #892720, regarding cron: warning from postinst script to be marked as done. This means that you claim

Bug#892720: marked as done (Warning: * is not a regular file!)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#892720: fixed in cron 3.0pl1-130 has caused the Debian Bug report #892720, regarding Warning: * is not a regular file! to be marked as done. This means that you claim that

Bug#892721: marked as done (cron: Warning during installation)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#892721: fixed in cron 3.0pl1-130 has caused the Debian Bug report #892721, regarding cron: Warning during installation to be marked as done. This means that you claim that

Bug#892721: marked as done (cron: Warning during installation)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#892724: fixed in cron 3.0pl1-130 has caused the Debian Bug report #892724, regarding cron: Warning during installation to be marked as done. This means that you claim that

Bug#892720: marked as done (Warning: * is not a regular file!)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#892724: fixed in cron 3.0pl1-130 has caused the Debian Bug report #892724, regarding Warning: * is not a regular file! to be marked as done. This means that you claim that

Bug#892720: marked as done (Warning: * is not a regular file!)

Your message dated Mon, 12 Mar 2018 23:49:37 + with message-id and subject line Bug#892721: fixed in cron 3.0pl1-130 has caused the Debian Bug report #892721, regarding Warning: * is not a regular file! to be marked as done. This means that you claim that

Bug#892711: marked as done (python-pymodbus-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/python-pymodbus/examples/common/README.rst)

Your message dated Mon, 12 Mar 2018 22:55:29 + with message-id and subject line Bug#892711: fixed in pymodbus 1.4.0+dfsg-2 has caused the Debian Bug report #892711, regarding python-pymodbus-doc: fails to upgrade from 'stable' to 'sid' - trying to

Bug#892690: marked as done (autoconf-archive: ax_lib_postgresql.m4 must be updated to work with the Debian-specific version string)

Your message dated Mon, 12 Mar 2018 20:51:05 + with message-id and subject line Bug#892690: fixed in autoconf-archive 20170928-2 has caused the Debian Bug report #892690, regarding autoconf-archive: ax_lib_postgresql.m4 must be updated to work with the

Bug#879709: marked as done (cannot install unar)

Your message dated Tue, 13 Mar 2018 04:54:03 +0800 with message-id <87o9jt6mms@jidanni.org> and subject line Re: Bug#879709: Unreproducible? has caused the Debian Bug report #879709, regarding cannot install unar to be marked as done. This means that you claim that the problem has been dealt