Bug#920576: marked as done (linux: Please enable CONFIG_HSA_AMD)

Your message dated Sun, 27 Jan 2019 01:25:46 -0600 with message-id <871s4yftol@bolt.d.tiker.net> and subject line HSA is present in the 4.19 kernel package has caused the Debian Bug report #920576, regarding linux: Please enable CONFIG_HSA_AMD to be marked as done. This means that you claim

Bug#918929: marked as done (New upstream version 2.41 - please package)

Your message dated Sun, 27 Jan 2019 10:04:18 + with message-id and subject line Bug#918929: fixed in keepass2 2.41+dfsg-1 has caused the Debian Bug report #918929, regarding New upstream version 2.41 - please package to be marked as done. This means that you claim that the problem has been

Bug#920525: marked as done (freecad: autopkgtest failure)

Your message dated Sun, 27 Jan 2019 08:40:40 + with message-id and subject line Bug#920525: fixed in freecad 0.17+dfsg1-8 has caused the Debian Bug report #920525, regarding freecad: autopkgtest failure to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#920314: marked as done (lintian: vcs-field-has-unexpected-spaces has false positives for Vcs-Hg that specify a branch)

Your message dated Sun, 27 Jan 2019 09:41:05 +0100 with message-id <1548578465.2242109.1644469016.1e3a7...@webmail.messagingengine.com> and subject line Re: lintian: vcs-field-has-unexpected-spaces has false positives for Vcs-Hg that specify a branch has caused the Debian Bug report #920314,

Bug#918797: marked as done (minieigen: FTBFS with Sphinx 1.8: No module named 'sphinx.ext.pngmath')

Your message dated Sun, 27 Jan 2019 08:45:46 + with message-id and subject line Bug#918797: fixed in minieigen 0.50.3+dfsg1-8 has caused the Debian Bug report #918797, regarding minieigen: FTBFS with Sphinx 1.8: No module named 'sphinx.ext.pngmath' to be marked as done. This means that you

Bug#919711: marked as done (openfoam: autopkgtest regression)

Your message dated Sun, 27 Jan 2019 08:46:44 + with message-id and subject line Bug#919711: fixed in openfoam 1812+dfsg1-2 has caused the Debian Bug report #919711, regarding openfoam: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt

Bug#917097: marked as done (lintian: Build fails with "Can't locate Test/Lintian/Harness.pm in @INC")

Your message dated Sun, 27 Jan 2019 09:49:19 +0100 with message-id <1548578959.2243254.1644474320.7e82f...@webmail.messagingengine.com> and subject line Re: lintian: Build fails with "Can't locate Test/Lintian/Harness.pm in @INC" has caused the Debian Bug report #917097, regarding lintian: Build

Bug#919675: marked as done (New version 1.28 available)

Your message dated Sun, 27 Jan 2019 09:35:11 + with message-id and subject line Bug#919675: fixed in libteam 1.28-1 has caused the Debian Bug report #919675, regarding New version 1.28 available to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#919536: marked as done (surf: Warnings and AppError audit messages about GPU)

Your message dated Sun, 27 Jan 2019 12:21:46 + with message-id and subject line Bug#919536: fixed in surf 2.0+git20181009-4 has caused the Debian Bug report #919536, regarding surf: Warnings and AppError audit messages about GPU to be marked as done. This means that you claim that the

Bug#898881: marked as done (conntrack-tools FTCBFS: does not pass --host to ./configure)

Your message dated Sun, 27 Jan 2019 15:34:11 + with message-id and subject line Bug#898881: fixed in conntrack-tools 1:1.4.5-2 has caused the Debian Bug report #898881, regarding conntrack-tools FTCBFS: does not pass --host to ./configure to be marked as done. This means that you claim that

Bug#916138: marked as done (conntrackd: State Accept/Ignore isn't working, always get symbol '}': syntax error. Even "SYNC EXAMPLE 2" from manpage fails.)

Your message dated Sun, 27 Jan 2019 15:34:11 + with message-id and subject line Bug#916138: fixed in conntrack-tools 1:1.4.5-2 has caused the Debian Bug report #916138, regarding conntrackd: State Accept/Ignore isn't working, always get symbol '}': syntax error. Even "SYNC EXAMPLE 2" from

Bug#919736: marked as done (tj3: FTBFS (failing tests))

Your message dated Sun, 27 Jan 2019 16:08:14 + with message-id and subject line Bug#919736: fixed in tj3 3.6.0-6 has caused the Debian Bug report #919736, regarding tj3: FTBFS (failing tests) to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#920617: marked as done (gnome-settings-daemon: Please upgrade gnome-settings-daemon-common too.)

Your message dated Sun, 27 Jan 2019 11:07:41 -0500 with message-id and subject line Re: Bug#920617: gnome-settings-daemon: Please upgrade gnome-settings-daemon-common too. has caused the Debian Bug report #920617, regarding gnome-settings-daemon: Please upgrade gnome-settings-daemon-common

Bug#859721: marked as done (stunserver: Please migrate to openssl1.1 in Buster)

Your message dated Sun, 27 Jan 2019 11:25:48 + with message-id and subject line Bug#920570: Removed package(s) from unstable has caused the Debian Bug report #859721, regarding stunserver: Please migrate to openssl1.1 in Buster to be marked as done. This means that you claim that the problem

Bug#917382: marked as done (Should stunserver be removed?)

Your message dated Sun, 27 Jan 2019 11:25:48 + with message-id and subject line Bug#920570: Removed package(s) from unstable has caused the Debian Bug report #917382, regarding Should stunserver be removed? to be marked as done. This means that you claim that the problem has been dealt with.

Bug#920528: marked as done (RM: lemonldap-ng-fr-doc [all] -- RoQA; NBS; cruft arch:all package)

Your message dated Sun, 27 Jan 2019 11:25:13 + with message-id and subject line Bug#920528: Removed package(s) from unstable has caused the Debian Bug report #920528, regarding RM: lemonldap-ng-fr-doc [all] -- RoQA; NBS; cruft arch:all package to be marked as done. This means that you claim

Bug#920570: marked as done (RM: stunserver -- RoQA; Unmaintained, RC-buggy)

Your message dated Sun, 27 Jan 2019 11:25:42 + with message-id and subject line Bug#920570: Removed package(s) from unstable has caused the Debian Bug report #920570, regarding RM: stunserver -- RoQA; Unmaintained, RC-buggy to be marked as done. This means that you claim that the problem has

Bug#920551: marked as done (RM: yade [mips mips64el mipsel] -- ROM; Some archs are to weak for this package)

Your message dated Sun, 27 Jan 2019 11:24:38 + with message-id and subject line Bug#920551: Removed package(s) from unstable has caused the Debian Bug report #920551, regarding RM: yade [mips mips64el mipsel] -- ROM; Some archs are to weak for this package to be marked as done. This means

Bug#891218: marked as done (mariadb-server-10.1: logrotate sometimes fails with "Lost connection to MySQL server")

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #891218, regarding mariadb-server-10.1: logrotate sometimes fails with "Lost connection to MySQL server" to be marked as done. This

Bug#873460: marked as done (mariadb-server-10.1: Updates not restarting mariadb@xx services)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #873460, regarding mariadb-server-10.1: Updates not restarting mariadb@xx services to be marked as done. This means that you claim

Bug#870200: marked as done (mariadb-server-10.1: jessie --> stretch: starting mariadb impossible (Failed at step NAMESPACE spawning /usr/bin/install: Value too large for defined data type))

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #870200, regarding mariadb-server-10.1: jessie --> stretch: starting mariadb impossible (Failed at step NAMESPACE spawning

Bug#866751: marked as done (wrong table structure for innodb_table_stats)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #866751, regarding wrong table structure for innodb_table_stats to be marked as done. This means that you claim that the problem has

Bug#866983: marked as done (mariadb spins at 100% forever during postinst)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #866983, regarding mariadb spins at 100% forever during postinst to be marked as done. This means that you claim that the problem has

Bug#880738: marked as done (mariadb: [INTL:de] Initial German translation)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #880738, regarding mariadb: [INTL:de] Initial German translation to be marked as done. This means that you claim that the problem has

Bug#867137: marked as done ("mariadb install fails with NO_NEW_PRIVILEGES (systemd)")

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #867137, regarding "mariadb install fails with NO_NEW_PRIVILEGES (systemd)" to be marked as done. This means that you claim that the

Bug#920380: marked as done (mariadb-10.1: do not release with buster)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #920380, regarding mariadb-10.1: do not release with buster to be marked as done. This means that you claim that the problem has been

Bug#905599: marked as done (Review default config file contents, attempt to make them as small as possible)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #905599, regarding Review default config file contents, attempt to make them as small as possible to be marked as done. This means

Bug#897428: marked as done (mariadb-server-core-10.1: Please consider run mysql_upgrade with the installation scripts)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #897428, regarding mariadb-server-core-10.1: Please consider run mysql_upgrade with the installation scripts to be marked as done.

Bug#920581: marked as done (RM: mariadb-10.1 -- ROM; obsoleted by mariadb-10.3)

Your message dated Sun, 27 Jan 2019 11:36:23 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #920581, regarding RM: mariadb-10.1 -- ROM; obsoleted by mariadb-10.3 to be marked as done. This means that you claim that the problem

Bug#913207: marked as done (mytop: depends on libconfig-inifiles-perl but package does not Depend on it)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #913207, regarding mytop: depends on libconfig-inifiles-perl but package does not Depend on it to be marked as done. This means that

Bug#919776: marked as done (mariadb-10.1 FTBFS on most architectures, testsuite failures.)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #919776, regarding mariadb-10.1 FTBFS on most architectures, testsuite failures. to be marked as done. This means that you claim that

Bug#912848: marked as done (mariadb-10.1: CVE-2018-3282 CVE-2018-3174 CVE-2018-3143 CVE-2018-3156 CVE-2018-3251)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #912848, regarding mariadb-10.1: CVE-2018-3282 CVE-2018-3174 CVE-2018-3143 CVE-2018-3156 CVE-2018-3251 to be marked as done. This

Bug#914215: marked as done (mariadb-server-10.1: does not start when /var/lib or /var/log is a symbolic link to another filesystem)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #914215, regarding mariadb-server-10.1: does not start when /var/lib or /var/log is a symbolic link to another filesystem to be marked

Bug#900398: marked as done (mariadb-server-10.1: postinst fails since official rebuild)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #900398, regarding mariadb-server-10.1: postinst fails since official rebuild to be marked as done. This means that you claim that the

Bug#853972: marked as done (mariadb-10.1: upgrading from mysql-5.7 renders old data inaccessible with no option to abort)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #853972, regarding mariadb-10.1: upgrading from mysql-5.7 renders old data inaccessible with no option to abort to be marked as done.

Bug#864421: marked as done (mysqld_safe: Notes as error logs)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #864421, regarding mysqld_safe: Notes as error logs to be marked as done. This means that you claim that the problem has been dealt

Bug#865931: marked as done (mysql-server: Does not allow me to change root password)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #865931, regarding mysql-server: Does not allow me to change root password to be marked as done. This means that you claim that the

Bug#864943: marked as done (mariadb-server-10.1: Starting mariadb service does not terminate)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #864943, regarding mariadb-server-10.1: Starting mariadb service does not terminate to be marked as done. This means that you claim

Bug#852776: marked as done (mariadb-server-10.1: init script doesn't specify it should be started prior to apache2 etc)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #852776, regarding mariadb-server-10.1: init script doesn't specify it should be started prior to apache2 etc to be marked as done.

Bug#914804: marked as done (pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find -lcuda)

Your message dated Sun, 27 Jan 2019 13:52:33 + with message-id and subject line Bug#914804: fixed in pycuda 2018.1.1-3 has caused the Debian Bug report #914804, regarding pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find -lcuda to be marked as done. This means that you claim that the

Processed: is in NEW

Processing commands for cont...@bugs.debian.org: > close 917561 Bug #917561 [sponsorship-requests] RFS: opencpn/4.8.8+dfsg.1-1 [ITP] -- Chartplotter and Marine Navigation software Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. --

Bug#920026: marked as done (python-greenlet-dev: ships header in /usr/include/python3.7/)

Your message dated Sun, 27 Jan 2019 17:17:32 + with message-id and subject line Bug#920026: fixed in python-greenlet 0.4.15-2 has caused the Debian Bug report #920026, regarding python-greenlet-dev: ships header in /usr/include/python3.7/ to be marked as done. This means that you claim that

Bug#867681: marked as done (software-properties-gtk: trusted.gpg file created by this package produces gpg error for 'apt-get update')

Your message dated Sun, 27 Jan 2019 15:35:35 + with message-id and subject line Bug#867681: fixed in software-properties 0.96.24.32.7-1 has caused the Debian Bug report #867681, regarding software-properties-gtk: trusted.gpg file created by this package produces gpg error for 'apt-get

Bug#883647: marked as done (Updated Russian debconf translation)

Your message dated Sun, 27 Jan 2019 11:19:55 + with message-id and subject line Bug#883647: fixed in courier 1.0.5-2 has caused the Debian Bug report #883647, regarding Updated Russian debconf translation to be marked as done. This means that you claim that the problem has been dealt with.

Bug#863941: marked as done (courier: French debconf translation update)

Your message dated Sun, 27 Jan 2019 11:19:55 + with message-id and subject line Bug#863941: fixed in courier 1.0.5-2 has caused the Debian Bug report #863941, regarding courier: French debconf translation update to be marked as done. This means that you claim that the problem has been dealt

Bug#893830: marked as done (sqwebmail cgi can't access sqwebmail.sock)

Your message dated Sun, 27 Jan 2019 11:19:55 + with message-id and subject line Bug#893830: fixed in courier 1.0.5-2 has caused the Debian Bug report #893830, regarding sqwebmail cgi can't access sqwebmail.sock to be marked as done. This means that you claim that the problem has been dealt

Bug#885186: marked as done ([L10N,DE] courier: updated german debconf translation)

Your message dated Sun, 27 Jan 2019 11:19:55 + with message-id and subject line Bug#885186: fixed in courier 1.0.5-2 has caused the Debian Bug report #885186, regarding [L10N,DE] courier: updated german debconf translation to be marked as done. This means that you claim that the problem has

Bug#919840: marked as done (sqwebmail: leaves broken symlink after purge: /etc/apache2/conf-available/sqwebmail.conf -> ../../sqwebmail/apache24.conf)

Your message dated Sun, 27 Jan 2019 11:19:55 + with message-id and subject line Bug#919840: fixed in courier 1.0.5-2 has caused the Debian Bug report #919840, regarding sqwebmail: leaves broken symlink after purge: /etc/apache2/conf-available/sqwebmail.conf -> ../../sqwebmail/apache24.conf

Bug#919973: marked as done (netdata: fails to install: useradd: group netdata exists - if you want to add this user to that group, use -g.)

Your message dated Sun, 27 Jan 2019 12:05:33 + with message-id and subject line Bug#919973: fixed in netdata 1.12.0~rc3-2 has caused the Debian Bug report #919973, regarding netdata: fails to install: useradd: group netdata exists - if you want to add this user to that group, use -g. to be

Bug#919973: marked as done (netdata: fails to install: useradd: group netdata exists - if you want to add this user to that group, use -g.)

Your message dated Sun, 27 Jan 2019 12:05:15 + with message-id and subject line Bug#919973: fixed in netdata 1.11.1+dfsg-4 has caused the Debian Bug report #919973, regarding netdata: fails to install: useradd: group netdata exists - if you want to add this user to that group, use -g. to be

Bug#919535: marked as done (surf: AppArmor profile forbids access to publicsuffix data)

Your message dated Sun, 27 Jan 2019 12:21:46 + with message-id and subject line Bug#919535: fixed in surf 2.0+git20181009-4 has caused the Debian Bug report #919535, regarding surf: AppArmor profile forbids access to publicsuffix data to be marked as done. This means that you claim that the

Bug#919534: marked as done (surf: AppArmor profile forbids creation of ~/.cache directory)

Your message dated Sun, 27 Jan 2019 12:21:46 + with message-id and subject line Bug#919534: fixed in surf 2.0+git20181009-4 has caused the Debian Bug report #919534, regarding surf: AppArmor profile forbids creation of ~/.cache directory to be marked as done. This means that you claim that

Processed: Re: stretch-backports: needs newer python3-urllib3

Processing commands for cont...@bugs.debian.org: > close 920160 Bug #920160 [netdata] stretch-backports: needs newer python3-urllib3 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 920160:

Bug#916256: marked as done (gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0)

Your message dated Sun, 27 Jan 2019 23:55:54 +1100 with message-id <4197763.WzzgV0LaB0@deblab> and subject line Re: [pkg-go] Bug#916256: Bug#916256: Bug#916256: gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0 has caused the Debian Bug report #916256, regarding

Bug#890190: marked as done ([compiz-plugins-default] Plugin "wall" doesn't honor edge-delay)

Your message dated Sun, 27 Jan 2019 15:06:19 + with message-id and subject line Bug#890190: fixed in compiz 2:0.8.16.1-6 has caused the Debian Bug report #890190, regarding [compiz-plugins-default] Plugin "wall" doesn't honor edge-delay to be marked as done. This means that you claim that

Bug#875954: marked as done (courier-mta: /usr/sbin/sendmail has wrong permissions)

Your message dated Sun, 27 Jan 2019 16:40:09 +0100 with message-id and subject line Re: courier-mta: /usr/sbin/sendmail has wrong permissions has caused the Debian Bug report #875954, regarding courier-mta: /usr/sbin/sendmail has wrong permissions to be marked as done. This means that you claim

Bug#905930: marked as done (www.debian.org: Duplication of text in webpage https://www.debian.org/doc/manuals/developers-reference/ch04.en.html 4.6.5 "Debian 10, will be called buster and Debian 10 wi

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#905930: fixed in developers-reference 3.4.22 has caused the Debian Bug report #905930, regarding www.debian.org: Duplication of text in webpage

Bug#912724: marked as done (www.debian.org: wrong links to translations of "Debian Developer's Reference")

Your message dated Sun, 27 Jan 2019 16:51:49 + with message-id and subject line Bug#912724: fixed in developers-reference 3.4.22 has caused the Debian Bug report #912724, regarding www.debian.org: wrong links to translations of "Debian Developer's Reference" to be marked as done. This means

Bug#690750: marked as done (developers-reference: no link to English manual)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#690750: fixed in developers-reference 3.4.22 has caused the Debian Bug report #690750, regarding developers-reference: no link to English manual to be marked as done. This means that you claim that the

Bug#915310: marked as done (developer-reference: broken link to anonscm.debian.org)

Your message dated Sun, 27 Jan 2019 16:51:49 + with message-id and subject line Bug#915310: fixed in developers-reference 3.4.22 has caused the Debian Bug report #915310, regarding developer-reference: broken link to anonscm.debian.org to be marked as done. This means that you claim that the

Bug#907665: marked as done (developers-reference: Section 6.7.9 about dbg packages outdated)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#907665: fixed in developers-reference 3.4.22 has caused the Debian Bug report #907665, regarding developers-reference: Section 6.7.9 about dbg packages outdated to be marked as done. This means that you claim

Bug#920591: marked as done (lambda-align2: please make the build reproducible)

Your message dated Sun, 27 Jan 2019 10:49:28 + with message-id and subject line Bug#920591: fixed in lambda-align2 2.0.0-5 has caused the Debian Bug report #920591, regarding lambda-align2: please make the build reproducible to be marked as done. This means that you claim that the problem

Bug#866782: marked as done (/etc/mysql/debian-start claims not being read by systemd)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #866782, regarding /etc/mysql/debian-start claims not being read by systemd to be marked as done. This means that you claim that the

Bug#887007: marked as done (my.cnf handling collides with MySQL)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #887007, regarding my.cnf handling collides with MySQL to be marked as done. This means that you claim that the problem has been dealt

Bug#874370: marked as done (mariadb-server-10.1: mariadb server does not write pid file on location specified in config)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #874370, regarding mariadb-server-10.1: mariadb server does not write pid file on location specified in config to be marked as done.

Bug#869782: marked as done (Mytop: Can't locate Term/ReadKey.pm)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #869782, regarding Mytop: Can't locate Term/ReadKey.pm to be marked as done. This means that you claim that the problem has been dealt

Bug#875457: marked as done (mariadb-server-10.1: Only supports certificates signed with SHA1 which is insecure)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #875457, regarding mariadb-server-10.1: Only supports certificates signed with SHA1 which is insecure to be marked as done. This

Bug#879099: marked as done (mariadb-client-10.1: mysqlbinlog: unknown variable 'default-character-set=utf8mb4')

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #879099, regarding mariadb-client-10.1: mysqlbinlog: unknown variable 'default-character-set=utf8mb4' to be marked as done. This

Bug#870433: marked as done (mysql-server: crash during upgrade to mariadb)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #870433, regarding mysql-server: crash during upgrade to mariadb to be marked as done. This means that you claim that the problem has

Bug#871796: marked as done (mariadb-10.1_10.1.25-1 FTBFS on ppc64el)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #871796, regarding mariadb-10.1_10.1.25-1 FTBFS on ppc64el to be marked as done. This means that you claim that the problem has been

Bug#879728: marked as done (mysqld fails to start not finding messagefile when started by systemd)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #879728, regarding mysqld fails to start not finding messagefile when started by systemd to be marked as done. This means that you

Bug#887655: marked as done (mariadb-10.1: FTBFS with liblz4-dev installed)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #887655, regarding mariadb-10.1: FTBFS with liblz4-dev installed to be marked as done. This means that you claim that the problem has

Bug#851643: marked as done (Add postinst/prerm scripts for mariadb-plugin-cracklib)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #851643, regarding Add postinst/prerm scripts for mariadb-plugin-cracklib to be marked as done. This means that you claim that the

Bug#835596: marked as done ([mariadb-10.0] Please ship support-files/mysqld_multi.server.sh)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #835596, regarding [mariadb-10.0] Please ship support-files/mysqld_multi.server.sh to be marked as done. This means that you claim

Bug#851195: marked as done (mariadb-server-10.1: Time Zone system tables are empty)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #851195, regarding mariadb-server-10.1: Time Zone system tables are empty to be marked as done. This means that you claim that the

Bug#808419: marked as done (TODO: Add debconf question to make feedback plugin opt-in very easy)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #808419, regarding TODO: Add debconf question to make feedback plugin opt-in very easy to be marked as done. This means that you claim

Bug#787118: marked as done (mariadb-server-10.0: Compile with OpenSSL (instead of YaSSL))

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #787118, regarding mariadb-server-10.0: Compile with OpenSSL (instead of YaSSL) to be marked as done. This means that you claim that

Bug#851644: marked as done (Add postinst/prerm scripts for mariadb-plugin-gssapi-client/server)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #851644, regarding Add postinst/prerm scripts for mariadb-plugin-gssapi-client/server to be marked as done. This means that you claim

Bug#865534: marked as done (mariadb-server-10.1: Fails in postinst on upgrade from jessie, gives incorrect resolution instructions)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #865534, regarding mariadb-server-10.1: Fails in postinst on upgrade from jessie, gives incorrect resolution instructions to be marked

Bug#861553: marked as done (Please enable numa support)

Your message dated Sun, 27 Jan 2019 11:36:56 + with message-id and subject line Bug#920581: Removed package(s) from unstable has caused the Debian Bug report #861553, regarding Please enable numa support to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#920558: marked as done (RFS: liboauth/1.0.3-2 [QA])

Your message dated Sun, 27 Jan 2019 15:28:58 + with message-id <20190127152858.a7lbb2cj7iv47...@master.debian.org> and subject line removed from mentors has caused the Debian Bug report #920558, regarding RFS: liboauth/1.0.3-2 [QA] to be marked as done. This means that you claim that the

Bug#841289: marked as done ([drm/i915] GPU HANG: ecode 9:0:0xfffffffe, in Xorg [2507], reason: Engine(s) hung, action: reset)

Your message dated Sun, 27 Jan 2019 17:21:24 +0100 with message-id and subject line Re: Bug#841289: [drm/i915] GPU HANG: ecode 9:0:0xfffe, in Xorg [2507], reason: Engine(s) hung, action: reset has caused the Debian Bug report #841289, regarding [drm/i915] GPU HANG: ecode 9:0:0xfffe, in

Bug#912587: marked as done (firejail AppArmor profile blocks Chromium's usage of ptrace => large amounts of denial logged)

Your message dated Sun, 27 Jan 2019 16:40:23 + with message-id and subject line Bug#912587: fixed in firejail 0.9.58-1 has caused the Debian Bug report #912587, regarding firejail AppArmor profile blocks Chromium's usage of ptrace => large amounts of denial logged to be marked as done. This

Bug#916920: marked as done (firejail: Firejail allows regular users to bypass root system settings)

Your message dated Sun, 27 Jan 2019 16:40:23 + with message-id and subject line Bug#916920: fixed in firejail 0.9.58-1 has caused the Debian Bug report #916920, regarding firejail: Firejail allows regular users to bypass root system settings to be marked as done. This means that you claim

Bug#907915: marked as done (developers-reference: language in manual)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#907915: fixed in developers-reference 3.4.22 has caused the Debian Bug report #907915, regarding developers-reference: language in manual to be marked as done. This means that you claim that the problem has

Bug#818850: marked as done (developers-reference: two chapters regarding the 'default' field)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#818850: fixed in developers-reference 3.4.22 has caused the Debian Bug report #818850, regarding developers-reference: two chapters regarding the 'default' field to be marked as done. This means that you

Bug#908291: marked as done (developers-reference, section 5.11.4: Add a note on versioning scheme when reverting an NMU)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#908291: fixed in developers-reference 3.4.22 has caused the Debian Bug report #908291, regarding developers-reference, section 5.11.4: Add a note on versioning scheme when reverting an NMU to be marked as

Bug#908890: marked as done (developers-reference: As alioth is gone, replace references to Salsa)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#908890: fixed in developers-reference 3.4.22 has caused the Debian Bug report #908890, regarding developers-reference: As alioth is gone, replace references to Salsa to be marked as done. This means that you

Processed: is in NEW

Processing commands for cont...@bugs.debian.org: > close 919541 Bug #919541 [sponsorship-requests] RFS: blastem/0.6.2-1 [ITP] -- Fast and accurate Genesis emulator Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 919541:

Bug#919406: marked as done (kdiff3 FTBFS: missing -latomic)

Your message dated Sun, 27 Jan 2019 11:54:26 +0100 with message-id <53401610.30EAEqkozB@track> and subject line Re: Bug#919406: kdiff3 FTBFS: missing -latomic has caused the Debian Bug report #919406, regarding kdiff3 FTBFS: missing -latomic to be marked as done. This means that you claim that

Bug#639817: marked as done (Recommends and breaks libiodbc2 at the same time)

Your message dated Sun, 27 Jan 2019 11:33:17 + with message-id and subject line Bug#917019: Removed package(s) from unstable has caused the Debian Bug report #639300, regarding Recommends and breaks libiodbc2 at the same time to be marked as done. This means that you claim that the problem

Bug#875185: marked as done ([soprano] Future Qt4 removal from Buster)

Your message dated Sun, 27 Jan 2019 11:33:17 + with message-id and subject line Bug#917019: Removed package(s) from unstable has caused the Debian Bug report #875185, regarding [soprano] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#917019: marked as done (RM: soprano -- ROM; dead upstream)

Your message dated Sun, 27 Jan 2019 11:33:08 + with message-id and subject line Bug#917019: Removed package(s) from unstable has caused the Debian Bug report #917019, regarding RM: soprano -- ROM; dead upstream to be marked as done. This means that you claim that the problem has been dealt

Bug#707301: marked as done (make soprano co-installable with multiarch-enabled ODBC drivers)

Your message dated Sun, 27 Jan 2019 11:33:17 + with message-id and subject line Bug#917019: Removed package(s) from unstable has caused the Debian Bug report #707301, regarding make soprano co-installable with multiarch-enabled ODBC drivers to be marked as done. This means that you claim

Bug#518380: marked as done (libsoprano4: missing manpage for sopranocmd)

Your message dated Sun, 27 Jan 2019 11:33:17 + with message-id and subject line Bug#917019: Removed package(s) from unstable has caused the Debian Bug report #518380, regarding libsoprano4: missing manpage for sopranocmd to be marked as done. This means that you claim that the problem has

Bug#879435: marked as done (Updating the soprano Uploaders list)

Your message dated Sun, 27 Jan 2019 11:33:17 + with message-id and subject line Bug#917019: Removed package(s) from unstable has caused the Debian Bug report #879435, regarding Updating the soprano Uploaders list to be marked as done. This means that you claim that the problem has been dealt

Bug#502851: marked as done (libsoprano4: build sesame2 backend)

Your message dated Sun, 27 Jan 2019 11:33:17 + with message-id and subject line Bug#917019: Removed package(s) from unstable has caused the Debian Bug report #502851, regarding libsoprano4: build sesame2 backend to be marked as done. This means that you claim that the problem has been dealt

Bug#639300: marked as done (please build against unixodbc-dev instead of libiodbc2-dev)

Your message dated Sun, 27 Jan 2019 11:33:17 + with message-id and subject line Bug#917019: Removed package(s) from unstable has caused the Debian Bug report #639300, regarding please build against unixodbc-dev instead of libiodbc2-dev to be marked as done. This means that you claim that the

Bug#919918: marked as done (scikit-learn FTBFS on armel/armhf/arm64/ppc64el/s390x: test failures)

Your message dated Sun, 27 Jan 2019 12:50:32 + with message-id and subject line Bug#919918: fixed in scikit-learn 0.20.2+dfsg-2 has caused the Debian Bug report #919918, regarding scikit-learn FTBFS on armel/armhf/arm64/ppc64el/s390x: test failures to be marked as done. This means that you

Bug#920597: marked as done (docker.io: Unable to start daemon: "containerd" executable file not found in PATH)

Your message dated Sun, 27 Jan 2019 13:51:00 + with message-id and subject line Bug#920597: fixed in docker.io 18.09.1+dfsg1-3 has caused the Debian Bug report #920597, regarding docker.io: Unable to start daemon: "containerd" executable file not found in PATH to be marked as done. This

  1   2   >