Bug#913360: marked as done (libreoffice-base-drivers: please switch to libmariadb-java)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 11:09:14 + with message-id and subject line Bug#913360: fixed in libreoffice 1:6.2.0~beta1-1 has caused the Debian Bug report #913360, regarding libreoffice-base-drivers: please switch to libmariadb-java to be marked as done. This means that you claim that

Bug#913886: marked as done (Optimize TJENER's squid.conf for DEB package caching)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 11:05:32 + with message-id and subject line Bug#913886: fixed in debian-edu-config 2.10.46 has caused the Debian Bug report #913886, regarding Optimize TJENER's squid.conf for DEB package caching to be marked as done. This means that you claim that the

Bug#901740: marked as done (autopkgtest failure on i386: command3: Test DEFCFUN.BFF.2 failed)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 11:05:02 + with message-id and subject line Bug#901740: fixed in cffi 1:0.20.0-1 has caused the Debian Bug report #901740, regarding autopkgtest failure on i386: command3: Test DEFCFUN.BFF.2 failed to be marked as done. This means that you claim that the

Bug#913661: marked as done (munin-plugins-core: "apt_all update" no longer updates the state-file)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 11:35:01 + with message-id and subject line Bug#913661: fixed in munin 2.0.43-1 has caused the Debian Bug report #913661, regarding munin-plugins-core: "apt_all update" no longer updates the state-file to be marked as done. This means that you claim that

Processed: acorn build depends on cruft package node-unicode-10.0.0

2018-11-18 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 > 6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1 Bug #914004 [src:acorn] acorn build depends on cruft package node-unicode-10.0.0 Marked as fixed in versions

Bug#913827: marked as done (pgagent: should depend on postgresql?)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 13:06:43 + with message-id and subject line Bug#913827: fixed in pgagent 4.0.0-5 has caused the Debian Bug report #913827, regarding pgagent: should depend on postgresql? to be marked as done. This means that you claim that the problem has been dealt with.

Bug#910812: marked as done (design-desktop-graphics: depends on gimp and mypaint which are not co-installable (see #894757))

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 16:00:36 +0100 with message-id <154255323611.27056.3595931388312188...@auryn.jones.dk> and subject line Re: [Design-devel] Bug#910812: design-desktop-graphics: depends has caused the Debian Bug report #910812, regarding design-desktop-graphics: depends on gimp

Bug#905437: marked as done (libreoffice-common: AppArmor denies access to mesa shader cache)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 11:09:14 + with message-id and subject line Bug#905437: fixed in libreoffice 1:6.2.0~beta1-1 has caused the Debian Bug report #905437, regarding libreoffice-common: AppArmor denies access to mesa shader cache to be marked as done. This means that you claim

Bug#913962: marked as done (munin - Duplicate line for path "/run/munin", ignoring.)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 11:35:01 + with message-id and subject line Bug#913784: fixed in munin 2.0.43-1 has caused the Debian Bug report #913784, regarding munin - Duplicate line for path "/run/munin", ignoring. to be marked as done. This means that you claim that the problem has

Bug#913784: marked as done (munin-node: 'Duplicate line for path "/run/munin", ignoring' warning after upgrade to 2.0.42-5)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 11:35:01 + with message-id and subject line Bug#913784: fixed in munin 2.0.43-1 has caused the Debian Bug report #913784, regarding munin-node: 'Duplicate line for path "/run/munin", ignoring' warning after upgrade to 2.0.42-5 to be marked as done. This

Processed (with 1 error): closing 339441

2018-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > no updates in more than 10 years, closing Unknown command or malformed arguments to command. > close 339441 Bug #339441 [uptimed] uptimed: wrong config file written after first install/setup Bug #360837 [uptimed] wrong email configuration in

Processed: closing 895408

2018-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 895408 2.14-1 Bug #895408 [src:nasm] nasm: CVE-2018-10016 The source 'nasm' and version '2.14-1' do not appear to match any binary packages Marked as fixed in versions nasm/2.14-1. Bug #895408 [src:nasm] nasm: CVE-2018-10016 Marked Bug as

Processed: closing 894846

2018-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 894846 2.14-1 Bug #894846 [src:nasm] nasm: CVE-2018-8882 The source 'nasm' and version '2.14-1' do not appear to match any binary packages Marked as fixed in versions nasm/2.14-1. Bug #894846 [src:nasm] nasm: CVE-2018-8882 Marked Bug as

Processed: closing 894847

2018-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 894847 2.14-1 Bug #894847 [src:nasm] nasm: CVE-2018-8883 The source 'nasm' and version '2.14-1' do not appear to match any binary packages Marked as fixed in versions nasm/2.14-1. Bug #894847 [src:nasm] nasm: CVE-2018-8883 Marked Bug as

Bug#913997: marked as done (cmdtest: Should not 'provide' yarn)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 13:03:24 +0200 with message-id <20181118110324.ge4...@exolobe1.liw.fi> and subject line Re: Bug#913997: cmdtest: Should not 'provide' yarn has caused the Debian Bug report #913997, regarding cmdtest: Should not 'provide' yarn to be marked as done. This means

Bug#787078: marked as done (src:sysvinit: FTBFS with clang instead of gcc)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 12:03:13 + with message-id and subject line Re: src:sysvinit: FTBFS with clang instead of gcc has caused the Debian Bug report #787078, regarding src:sysvinit: FTBFS with clang instead of gcc to be marked as done. This means that you claim that the problem

Processed: closing 896523

2018-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 896523 2.14-1 Bug #896523 [src:nasm] nasm: CVE-2018-10254 The source 'nasm' and version '2.14-1' do not appear to match any binary packages Marked as fixed in versions nasm/2.14-1. Bug #896523 [src:nasm] nasm: CVE-2018-10254 Marked Bug as

Bug#651744: marked as done (Please transition cairomm for multiarch)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 09:34:33 -0500 with message-id and subject line Re: Please transition cairomm for multiarch has caused the Debian Bug report #651744, regarding Please transition cairomm for multiarch to be marked as done. This means that you claim that the problem has been

Bug#892564: marked as done (gnome-do: Update for gnome-desktop3 3.27.92+)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:16:58 + with message-id and subject line Bug#911202: Removed package(s) from unstable has caused the Debian Bug report #892564, regarding gnome-do: Update for gnome-desktop3 3.27.92+ to be marked as done. This means that you claim that the problem has

Bug#867941: marked as done (gnome-keyring-sharp: Build-Depends on deprecated libgnome-keyring-dev)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:17:34 + with message-id and subject line Bug#912926: Removed package(s) from unstable has caused the Debian Bug report #867941, regarding gnome-keyring-sharp: Build-Depends on deprecated libgnome-keyring-dev to be marked as done. This means that you

Bug#885046: marked as done (gnome-do: Depends on old GNOME libraries)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:16:58 + with message-id and subject line Bug#911202: Removed package(s) from unstable has caused the Debian Bug report #885046, regarding gnome-do: Depends on old GNOME libraries to be marked as done. This means that you claim that the problem has been

Bug#912926: marked as done (RM: gnome-keyring-sharp -- RoQA; unmaintained, depends on libgnome-keyring)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:17:28 + with message-id and subject line Bug#912926: Removed package(s) from unstable has caused the Debian Bug report #912926, regarding RM: gnome-keyring-sharp -- RoQA; unmaintained, depends on libgnome-keyring to be marked as done. This means that

Bug#669420: marked as done (monodoc-gnome-keyring-manual: debcheckout fails)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:17:34 + with message-id and subject line Bug#912926: Removed package(s) from unstable has caused the Debian Bug report #669420, regarding monodoc-gnome-keyring-manual: debcheckout fails to be marked as done. This means that you claim that the problem

Bug#913195: marked as done (netmrg: Make netmrg reproducible)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:24:36 + with message-id and subject line Bug#913212: Removed package(s) from unstable has caused the Debian Bug report #913195, regarding netmrg: Make netmrg reproducible to be marked as done. This means that you claim that the problem has been dealt

Bug#911690: marked as done (vmdb2 FTBFS: tests fail)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:22:51 + with message-id and subject line Bug#911690: fixed in vmdb2 0.13.2-2 has caused the Debian Bug report #911690, regarding vmdb2 FTBFS: tests fail to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#913215: marked as done (RM: custom-tab-width -- ROM; dead upstream, no longer works in firefox ESR)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:25:06 + with message-id and subject line Bug#913215: Removed package(s) from unstable has caused the Debian Bug report #913215, regarding RM: custom-tab-width -- ROM; dead upstream, no longer works in firefox ESR to be marked as done. This means that

Bug#913196: marked as done (netmrg: Debain/watch and debian/copyright point to spam site)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:24:36 + with message-id and subject line Bug#913212: Removed package(s) from unstable has caused the Debian Bug report #913196, regarding netmrg: Debain/watch and debian/copyright point to spam site to be marked as done. This means that you claim that

Bug#913077: marked as done (RM: gjs [s390x] -- RoM; now requires mozjs60 which fails tests on s390x)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:23:47 + with message-id and subject line Bug#913077: Removed package(s) from unstable has caused the Debian Bug report #913077, regarding RM: gjs [s390x] -- RoM; now requires mozjs60 which fails tests on s390x to be marked as done. This means that you

Bug#809404: marked as done (jailer: binary-indep target produces empty binaries)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:34:50 + with message-id and subject line Bug#913700: Removed package(s) from unstable has caused the Debian Bug report #809404, regarding jailer: binary-indep target produces empty binaries to be marked as done. This means that you claim that the

Bug#831939: marked as done (jailer: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:34:50 + with message-id and subject line Bug#913700: Removed package(s) from unstable has caused the Debian Bug report #831939, regarding jailer: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found;

Bug#410925: marked as done (jailer: "Provides" field is not evaluated)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:34:50 + with message-id and subject line Bug#913700: Removed package(s) from unstable has caused the Debian Bug report #410925, regarding jailer: "Provides" field is not evaluated to be marked as done. This means that you claim that the problem has been

Bug#913700: marked as done (RM: jailer -- RoQA; RC-buggy, no maintainer upload since 2011, uses internal dpkg database layout)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:34:43 + with message-id and subject line Bug#913700: Removed package(s) from unstable has caused the Debian Bug report #913700, regarding RM: jailer -- RoQA; RC-buggy, no maintainer upload since 2011, uses internal dpkg database layout to be marked as

Bug#410906: marked as done (jailer: All dependencies, even of junk-debs, are copied )

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:34:50 + with message-id and subject line Bug#913700: Removed package(s) from unstable has caused the Debian Bug report #410906, regarding jailer: All dependencies, even of junk-debs, are copied to be marked as done. This means that you claim that the

Bug#224157: marked as done (Include some config option to keep some directory or file.)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:34:50 + with message-id and subject line Bug#913700: Removed package(s) from unstable has caused the Debian Bug report #224157, regarding Include some config option to keep some directory or file. to be marked as done. This means that you claim that the

Bug#913694: marked as done (jailer: Script accesses internal dpkg database)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:34:50 + with message-id and subject line Bug#913700: Removed package(s) from unstable has caused the Debian Bug report #913694, regarding jailer: Script accesses internal dpkg database to be marked as done. This means that you claim that the problem has

Bug#744874: marked as done (jailer: AMD64 packages problems)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:34:50 + with message-id and subject line Bug#913700: Removed package(s) from unstable has caused the Debian Bug report #744874, regarding jailer: AMD64 packages problems to be marked as done. This means that you claim that the problem has been dealt

Bug#913826: marked as done (ITP: presto -- high-throughput lymphocyte receptor sequences processing)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 19:03:52 + with message-id and subject line Bug#913826: fixed in presto 0.5.10-1 has caused the Debian Bug report #913826, regarding ITP: presto -- high-throughput lymphocyte receptor sequences processing to be marked as done. This means that you claim

Bug#893967: marked as done (php-defaults: Drop distribution name from package descriptions)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 14:12:32 -0500 with message-id and subject line Re: [php-maint] Bug#893967: php-defaults: Drop distribution name from package descriptions has caused the Debian Bug report #893967, regarding php-defaults: Drop distribution name from package descriptions to be

Processed: closing 913647

2018-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 913647 2.14-1 Bug #913647 [nasm] nasm: new upstream version 2.14 available Marked as fixed in versions nasm/2.14-1. Bug #913647 [nasm] nasm: new upstream version 2.14 available Marked Bug as done > thanks Stopping processing here. Please

Bug#913961: marked as done (ghub-el 3.0.0-2 makes magit FTBFS)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 22:06:11 +0100 with message-id <87wopacczg.fsf@tpx1c3.i-did-not-set--mail-host-address--so-tickle-me> and subject line Re: Bug#913961: ghub-el 3.0.0-2 makes magit FTBFS has caused the Debian Bug report #913961, regarding ghub-el 3.0.0-2 makes magit FTBFS to be

Bug#913779: marked as done (libuv1: path_max_zero_st_size incorrectly rebased; patch attached)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:20:16 + with message-id and subject line Bug#913779: fixed in libuv1 1.23.2-2 has caused the Debian Bug report #913779, regarding libuv1: path_max_zero_st_size incorrectly rebased; patch attached to be marked as done. This means that you claim that the

Bug#906843: marked as done (xul-ext-custom-tab-width no longer works with firefox-esr 60)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:25:09 + with message-id and subject line Bug#913215: Removed package(s) from unstable has caused the Debian Bug report #906843, regarding xul-ext-custom-tab-width no longer works with firefox-esr 60 to be marked as done. This means that you claim that

Bug#913353: marked as done (RM: postgresql-10 -- ROM; superseded by postgresql-11)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:27:10 + with message-id and subject line Bug#913353: Removed package(s) from unstable has caused the Debian Bug report #913353, regarding RM: postgresql-10 -- ROM; superseded by postgresql-11 to be marked as done. This means that you claim that the

Bug#412547: marked as done (netmrg: Unable to move some graphs Up or Down)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:24:36 + with message-id and subject line Bug#913212: Removed package(s) from unstable has caused the Debian Bug report #412547, regarding netmrg: Unable to move some graphs Up or Down to be marked as done. This means that you claim that the problem has

Bug#412691: marked as done (netmrg: The monitor 'Script Options' field is ignored)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:24:36 + with message-id and subject line Bug#913212: Removed package(s) from unstable has caused the Debian Bug report #412691, regarding netmrg: The monitor 'Script Options' field is ignored to be marked as done. This means that you claim that the

Bug#876825: marked as done (gcc: infinite loop targeting armel)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:26:40 + with message-id and subject line Bug#913223: Removed package(s) from unstable has caused the Debian Bug report #876825, regarding gcc: infinite loop targeting armel to be marked as done. This means that you claim that the problem has been dealt

Bug#913223: marked as done (RM: gcc-6-cross -- NBS; needs manual decrufting)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:26:25 + with message-id and subject line Bug#913223: Removed package(s) from unstable has caused the Debian Bug report #913223, regarding RM: gcc-6-cross -- NBS; needs manual decrufting to be marked as done. This means that you claim that the problem

Bug#913212: marked as done (RM: netmrg -- ROM; Upstream devel has stoped many years ago)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:24:30 + with message-id and subject line Bug#913212: Removed package(s) from unstable has caused the Debian Bug report #913212, regarding RM: netmrg -- ROM; Upstream devel has stoped many years ago to be marked as done. This means that you claim that

Bug#422218: marked as done (NetMRG don't display graphs when a : is included)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:24:36 + with message-id and subject line Bug#913212: Removed package(s) from unstable has caused the Debian Bug report #422218, regarding NetMRG don't display graphs when a : is included to be marked as done. This means that you claim that the problem

Bug#912573: marked as done (Remove postgresql-10 from testing (also, will fail to binNMU))

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:27:14 + with message-id and subject line Bug#913353: Removed package(s) from unstable has caused the Debian Bug report #912573, regarding Remove postgresql-10 from testing (also, will fail to binNMU) to be marked as done. This means that you claim that

Bug#826969: marked as done (gcc-6-cross: Provide cross-compilers for kfreebsd and hurd too)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:26:40 + with message-id and subject line Bug#913223: Removed package(s) from unstable has caused the Debian Bug report #826969, regarding gcc-6-cross: Provide cross-compilers for kfreebsd and hurd too to be marked as done. This means that you claim that

Bug#913935: marked as done (mxallowd: [INTL:pt_BR] Brazilian Portuguese debconf templates translation)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:43:26 + with message-id and subject line Bug#913966: Removed package(s) from unstable has caused the Debian Bug report #913935, regarding mxallowd: [INTL:pt_BR] Brazilian Portuguese debconf templates translation to be marked as done. This means that

Bug#913966: marked as done (RM: mxallowd -- ROM; unmaintained upstream, unused)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:43:23 + with message-id and subject line Bug#913966: Removed package(s) from unstable has caused the Debian Bug report #913966, regarding RM: mxallowd -- ROM; unmaintained upstream, unused to be marked as done. This means that you claim that the problem

Bug#914019: marked as done (qmodule.pri: leaks -fdebug-prefix-map)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 18:42:24 +0100 with message-id <20181118174223.ga3...@alf.mars> and subject line Re: Bug#914019: qmodule.pri: leaks -fdebug-prefix-map has caused the Debian Bug report #914019, regarding qmodule.pri: leaks -fdebug-prefix-map to be marked as done. This means

Bug#913967: marked as done (RM: compiz-plugins-main [all] -- NBS; not built by compiz source package any more)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:44:06 + with message-id and subject line Bug#913967: Removed package(s) from unstable has caused the Debian Bug report #913967, regarding RM: compiz-plugins-main [all] -- NBS; not built by compiz source package any more to be marked as done. This means

Bug#913968: marked as done (RM: golang-github-juju-mutex -- ROM; no longer needed)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:44:28 + with message-id and subject line Bug#913968: Removed package(s) from unstable has caused the Debian Bug report #913968, regarding RM: golang-github-juju-mutex -- ROM; no longer needed to be marked as done. This means that you claim that the

Bug#829781: marked as done (gjiten: Uses deprecated gnome-common macros/variables)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:49:39 + with message-id and subject line Bug#829781: fixed in gjiten 2.6-3.1 has caused the Debian Bug report #829781, regarding gjiten: Uses deprecated gnome-common macros/variables to be marked as done. This means that you claim that the problem has

Bug#769860: marked as done (Gjiten could use kanjipad by default)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:49:39 + with message-id and subject line Bug#769860: fixed in gjiten 2.6-3.1 has caused the Debian Bug report #769860, regarding Gjiten could use kanjipad by default to be marked as done. This means that you claim that the problem has been dealt with.

Bug#765214: marked as done (gjiten: run dh-autoreconf to update for new architectures)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:49:39 + with message-id and subject line Bug#765214: fixed in gjiten 2.6-3.1 has caused the Debian Bug report #765214, regarding gjiten: run dh-autoreconf to update for new architectures to be marked as done. This means that you claim that the problem

Bug#908355: marked as done (flash-kernel FTCBFS: fails running tests despite DEB_BUILD_OPTIONS=nocheck)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 19:19:43 + with message-id and subject line Bug#908355: fixed in flash-kernel 3.96 has caused the Debian Bug report #908355, regarding flash-kernel FTCBFS: fails running tests despite DEB_BUILD_OPTIONS=nocheck to be marked as done. This means that you

Bug#914016: marked as done (flash-kernel: please add support for Helios 4 NAS)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 19:19:43 + with message-id and subject line Bug#914016: fixed in flash-kernel 3.96 has caused the Debian Bug report #914016, regarding flash-kernel: please add support for Helios 4 NAS to be marked as done. This means that you claim that the problem has

Bug#907781: marked as done (mdns-scan: wrong TLD in Homepage field)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 16:54:45 + with message-id and subject line Bug#907781: fixed in mdns-scan 0.5-5 has caused the Debian Bug report #907781, regarding mdns-scan: wrong TLD in Homepage field to be marked as done. This means that you claim that the problem has been dealt

Bug#908879: marked as done (pyparted: FTBFS randomly (ImportError: No module named _ped))

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 16:55:56 + with message-id and subject line Bug#908879: fixed in pyparted 3.11.1-13 has caused the Debian Bug report #908879, regarding pyparted: FTBFS randomly (ImportError: No module named _ped) to be marked as done. This means that you claim that the

Bug#386583: marked as done (tomboy: E-mail links from Evolution don't work if using exchange)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #386583, regarding tomboy: E-mail links from Evolution don't work if using exchange to be marked as done. This means that you claim

Bug#492208: marked as done (tomboy prevents clean restart of gnome session)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #492208, regarding tomboy prevents clean restart of gnome session to be marked as done. This means that you claim that the problem has

Bug#349824: marked as done (Mark title of new Notes, not text)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #349824, regarding Mark title of new Notes, not text to be marked as done. This means that you claim that the problem has been dealt

Bug#401176: marked as done (tomboy: make a mail from a note)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #401176, regarding tomboy: make a mail from a note to be marked as done. This means that you claim that the problem has been dealt

Bug#387144: marked as done (tomboy: Please implement tags to help organize notes)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #387144, regarding tomboy: Please implement tags to help organize notes to be marked as done. This means that you claim that the

Bug#891597: marked as done (tomboy FTBFS: No rule to make target '.config.in', needed by '../bin/Tomboy.exe.config'.)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #891597, regarding tomboy FTBFS: No rule to make target '.config.in', needed by '../bin/Tomboy.exe.config'. to be marked as done.

Bug#494403: marked as done (tomboy: Tomboy fails to start for second session of same user)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #494403, regarding tomboy: Tomboy fails to start for second session of same user to be marked as done. This means that you claim that

Bug#830048: marked as done (tomboy: Uses deprecated gnome-common macros/variables)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #830048, regarding tomboy: Uses deprecated gnome-common macros/variables to be marked as done. This means that you claim that the

Bug#683314: marked as done (tomboy: crashes on SSH sync if fuse module not loaded, gvfs-dbg not installed)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #683314, regarding tomboy: crashes on SSH sync if fuse module not loaded, gvfs-dbg not installed to be marked as done. This means

Bug#696678: marked as done (tomboy: Segfault crashes tomboy during synchronization)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #696678, regarding tomboy: Segfault crashes tomboy during synchronization to be marked as done. This means that you claim that the

Bug#794415: marked as done (tomboy: Tomboy icon does not appear in kde plasma 5 system tray)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #794415, regarding tomboy: Tomboy icon does not appear in kde plasma 5 system tray to be marked as done. This means that you claim

Bug#885804: marked as done (tomboy: Depends on gconf)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #885804, regarding tomboy: Depends on gconf to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#433474: marked as done (tomboy: Links to web sites launch the browser incorrectly)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #433474, regarding tomboy: Links to web sites launch the browser incorrectly to be marked as done. This means that you claim that the

Bug#626973: marked as done (tomboy: Tomboy cannot synchronise using ssh)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #626973, regarding tomboy: Tomboy cannot synchronise using ssh to be marked as done. This means that you claim that the problem has

Bug#652646: marked as done (tomboy: fails to syncronize because of existing "New Note Template")

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #652646, regarding tomboy: fails to syncronize because of existing "New Note Template" to be marked as done. This means that you claim

Bug#629422: marked as done (tomboy: Tomboy crashes and won't load)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #629422, regarding tomboy: Tomboy crashes and won't load to be marked as done. This means that you claim that the problem has been

Bug#658703: marked as done (tomboy mono dependencies segmentation faults)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #658703, regarding tomboy mono dependencies segmentation faults to be marked as done. This means that you claim that the problem has

Bug#473060: marked as done (tomboy: Built *.server file doesn't have all the translations)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #473060, regarding tomboy: Built *.server file doesn't have all the translations to be marked as done. This means that you claim that

Bug#610999: marked as done (tomboy: some notes will not be automatically linked if the notes' titles are begun with punctuation mark)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #610999, regarding tomboy: some notes will not be automatically linked if the notes' titles are begun with punctuation mark to be

Bug#520078: marked as done (Tomboy description in Add applet dialog is not translated when on es_PE.UTF-8)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #520078, regarding Tomboy description in Add applet dialog is not translated when on es_PE.UTF-8 to be marked as done. This means

Bug#778244: marked as done (tomboy: Please add evolution add on)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #778244, regarding tomboy: Please add evolution add on to be marked as done. This means that you claim that the problem has been dealt

Bug#877259: marked as done (tomboy: FTBFS: configure: error: missing reqired Mono 2.0 assembly: Mono.Cairo.dll)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #877259, regarding tomboy: FTBFS: configure: error: missing reqired Mono 2.0 assembly: Mono.Cairo.dll to be marked as done. This

Bug#867360: marked as done (tomboy: either drop gmime or switch to mimekit?)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #867360, regarding tomboy: either drop gmime or switch to mimekit? to be marked as done. This means that you claim that the problem

Bug#913748: marked as done (RM: django-floppyforms -- ROM; FTBFS; unmaintained)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:40:13 + with message-id and subject line Bug#913748: Removed package(s) from unstable has caused the Debian Bug report #913748, regarding RM: django-floppyforms -- ROM; FTBFS; unmaintained to be marked as done. This means that you claim that the problem

Bug#913993: marked as done (golang-gopkg-tylerb-graceful.v1 FTBFS: FAIL: TestGracefulForwardsConnState)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 19:49:34 + with message-id and subject line Bug#913993: fixed in golang-gopkg-tylerb-graceful.v1 1.2.15-2 has caused the Debian Bug report #913993, regarding golang-gopkg-tylerb-graceful.v1 FTBFS: FAIL: TestGracefulForwardsConnState to be marked as done.

Bug#846345: marked as done (elfutils: Fix crash when adding sections to empty ELF files)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 23:20:30 +0100 with message-id <20181118222029.go1...@roeckx.be> and subject line Re: Bug#846345: elfutils: Fix crash when adding sections to empty ELF files has caused the Debian Bug report #846345, regarding elfutils: Fix crash when adding sections to empty

Bug#724659: marked as done (RFP: xul-ext-firefox-os-simulator -- Firefox OS Simulator is a test environment for Firefox OS.)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 22:20:08 + with message-id and subject line closing RFP: xul-ext-firefox-os-simulator -- Firefox OS Simulator is a test environment for Firefox OS. has caused the Debian Bug report #724659, regarding RFP: xul-ext-firefox-os-simulator -- Firefox OS

Bug#913339: marked as done (RFS: libyang/0.16.52-1 ITP)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 22:20:25 + with message-id and subject line closing RFS: libyang/0.16.52-1 ITP has caused the Debian Bug report #913339, regarding RFS: libyang/0.16.52-1 ITP to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#911858: marked as done (controlsfx FTBFS: error: package javafx.scene does not exist)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 16:51:28 + with message-id and subject line Bug#911858: fixed in controlsfx 9.0.0+hg20181001-1 has caused the Debian Bug report #911858, regarding controlsfx FTBFS: error: package javafx.scene does not exist to be marked as done. This means that you claim

Bug#428170: marked as done (tomboy: sticky notes fade in/fade out)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #428170, regarding tomboy: sticky notes fade in/fade out to be marked as done. This means that you claim that the problem has been

Bug#336990: marked as done (Opening a new window causes breakage in ion.)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #336990, regarding Opening a new window causes breakage in ion. to be marked as done. This means that you claim that the problem has

Bug#502915: marked as done (tomboy: create a note using hotkey doesn't present the window)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #502915, regarding tomboy: create a note using hotkey doesn't present the window to be marked as done. This means that you claim that

Bug#516454: marked as done (tomboy: please allow user to specify a shorter umout timeout for fuse filesystems)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #516454, regarding tomboy: please allow user to specify a shorter umout timeout for fuse filesystems to be marked as done. This means

Bug#502914: marked as done (tomboy: listening to hotkeys doesn't work)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #502914, regarding tomboy: listening to hotkeys doesn't work to be marked as done. This means that you claim that the problem has been

Bug#335281: marked as done (tomboy hangs)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #335281, regarding tomboy hangs to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#337977: marked as done (Tomboy eats 100% CPU if fam is stopped)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #337977, regarding Tomboy eats 100% CPU if fam is stopped to be marked as done. This means that you claim that the problem has been

Bug#313303: marked as done (Copy the note title leads to tomboy having a wrong idea of the pasted font size)

2018-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2018 17:11:13 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #313303, regarding Copy the note title leads to tomboy having a wrong idea of the pasted font size to be marked as done. This means

  1   2   3   4   >