Bug#858634: marked as done (listviews are not accessible with Orca screen reader)

Your message dated Mon, 19 Nov 2018 01:31:06 + with message-id and subject line Bug#913850: Removed package(s) from unstable has caused the Debian Bug report #858634, regarding listviews are not accessible with Orca screen reader to be marked as done. This means that you claim that the proble

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

Your message dated Mon, 19 Nov 2018 01:31:06 + with message-id and subject line Bug#913850: Removed package(s) from unstable has caused the Debian Bug report #829855, regarding banshee: Uses deprecated gnome-common macros/variables to be marked as done. This means that you claim that the prob

Bug#897206: marked as done (libccnet0:amd64: libccnet0 breaks package system in multiarch setting)

Your message dated Mon, 19 Nov 2018 01:29:56 + with message-id and subject line Bug#913306: Removed package(s) from unstable has caused the Debian Bug report #897206, regarding libccnet0:amd64: libccnet0 breaks package system in multiarch setting to be marked as done. This means that you clai

Bug#869427: marked as done (sysinfo: Exception in Gtk# callback delegate)

Your message dated Mon, 19 Nov 2018 01:28:54 + with message-id and subject line Bug#910957: Removed package(s) from unstable has caused the Debian Bug report #869427, regarding sysinfo: Exception in Gtk# callback delegate to be marked as done. This means that you claim that the problem has be

Bug#887361: marked as done (ccnet: Coordinated Packaging for ccnet and ccnet-server)

Your message dated Mon, 19 Nov 2018 01:29:56 + with message-id and subject line Bug#913306: Removed package(s) from unstable has caused the Debian Bug report #887361, regarding ccnet: Coordinated Packaging for ccnet and ccnet-server to be marked as done. This means that you claim that the pro

Bug#828004: marked as done (banshee: Hangs when attempting to update library)

Your message dated Mon, 19 Nov 2018 01:31:06 + with message-id and subject line Bug#913850: Removed package(s) from unstable has caused the Debian Bug report #828004, regarding banshee: Hangs when attempting to update library to be marked as done. This means that you claim that the problem ha

Bug#826277: marked as done (banshee fails to start)

Your message dated Mon, 19 Nov 2018 01:31:06 + with message-id and subject line Bug#913850: Removed package(s) from unstable has caused the Debian Bug report #826277, regarding banshee fails to start to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#783576: marked as done (banshee: crashes on startup - System.ArgumentNullException: Argument cannot be null)

Your message dated Mon, 19 Nov 2018 01:31:06 + with message-id and subject line Bug#913850: Removed package(s) from unstable has caused the Debian Bug report #783576, regarding banshee: crashes on startup - System.ArgumentNullException: Argument cannot be null to be marked as done. This mean

Bug#902201: marked as done (ccnet: demote python-all to Build-Depends-Indep)

Your message dated Mon, 19 Nov 2018 01:29:56 + with message-id and subject line Bug#913306: Removed package(s) from unstable has caused the Debian Bug report #902201, regarding ccnet: demote python-all to Build-Depends-Indep to be marked as done. This means that you claim that the problem has

Bug#913850: marked as done (RM: banshee -- RoQA; unmaintained, depends on ancient GNOME libraries)

Your message dated Mon, 19 Nov 2018 01:30:21 + with message-id and subject line Bug#913850: Removed package(s) from unstable has caused the Debian Bug report #913850, regarding RM: banshee -- RoQA; unmaintained, depends on ancient GNOME libraries to be marked as done. This means that you clai

Bug#881371: marked as done (Banshee - Green Line Under Playing Video)

Your message dated Mon, 19 Nov 2018 01:31:06 + with message-id and subject line Bug#913850: Removed package(s) from unstable has caused the Debian Bug report #881371, regarding Banshee - Green Line Under Playing Video to be marked as done. This means that you claim that the problem has been d

Bug#881373: marked as done (Wishlist: Banshee Download from Internet Archive)

Your message dated Mon, 19 Nov 2018 01:31:06 + with message-id and subject line Bug#913850: Removed package(s) from unstable has caused the Debian Bug report #881373, regarding Wishlist: Banshee Download from Internet Archive to be marked as done. This means that you claim that the problem ha

Bug#774397: marked as done (banshee: Problem compiling banshee 2.6.2 on debian wheezy due to gstreamer dependiences.)

Your message dated Mon, 19 Nov 2018 01:31:06 + with message-id and subject line Bug#913850: Removed package(s) from unstable has caused the Debian Bug report #774397, regarding banshee: Problem compiling banshee 2.6.2 on debian wheezy due to gstreamer dependiences. to be marked as done. This

Bug#911200: marked as done (RM: banshee/experimental -- RoQA; unmaintained, depends on ancient GNOME libraries)

Your message dated Mon, 19 Nov 2018 01:31:06 + with message-id and subject line Bug#913850: Removed package(s) from unstable has caused the Debian Bug report #911200, regarding RM: banshee/experimental -- RoQA; unmaintained, depends on ancient GNOME libraries to be marked as done. This means

Bug#913306: marked as done (RM: ccnet -- ROM; superseded by ccnet-server in upstream, no build-depends anymore)

Your message dated Mon, 19 Nov 2018 01:29:52 + with message-id and subject line Bug#913306: Removed package(s) from unstable has caused the Debian Bug report #913306, regarding RM: ccnet -- ROM; superseded by ccnet-server in upstream, no build-depends anymore to be marked as done. This means

Bug#911562: marked as done (RM: gnome-sharp2 -- RoQA; unmaintained, depends on libgnome)

Your message dated Mon, 19 Nov 2018 01:33:18 + with message-id and subject line Bug#911562: Removed package(s) from unstable has caused the Debian Bug report #911562, regarding RM: gnome-sharp2 -- RoQA; unmaintained, depends on libgnome to be marked as done. This means that you claim that the

Bug#868426: marked as done (gnome-sharp2: Please drop the (build-)dependency against gnome-vfs)

Your message dated Mon, 19 Nov 2018 01:33:22 + with message-id and subject line Bug#911562: Removed package(s) from unstable has caused the Debian Bug report #868426, regarding gnome-sharp2: Please drop the (build-)dependency against gnome-vfs to be marked as done. This means that you claim t

Bug#911956: marked as done ([src:yaml-cpp] FTBFS with boost1.67)

Your message dated Mon, 19 Nov 2018 01:35:11 + with message-id and subject line Bug#911956: fixed in yaml-cpp 0.5.2-4.1 has caused the Debian Bug report #911956, regarding [src:yaml-cpp] FTBFS with boost1.67 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#847099: marked as done (yaml-cpp 0.5.2 is broken, please update to 0.5.3)

Your message dated Mon, 19 Nov 2018 01:35:11 + with message-id and subject line Bug#847099: fixed in yaml-cpp 0.5.2-4.1 has caused the Debian Bug report #847099, regarding yaml-cpp 0.5.2 is broken, please update to 0.5.3 to be marked as done. This means that you claim that the problem has bee

Bug#900793: marked as done (iperf2 crashes with long time run on 40Gb/s NICs)

Your message dated Sun, 18 Nov 2018 21:19:19 -0500 with message-id and subject line Bug#900793: fixed in iperf 2.0.12+dfsg1-1 has caused the Debian Bug report #900793, regarding iperf2 crashes with long time run on 40Gb/s NICs to be marked as done. This means that you claim that the problem has

Bug#913066: marked as done (libengine-pkcs11-openssl: use versioned Breaks+Replaces: libengine-pkcs11-openssl1.1 (<< 0.4.9-2))

Your message dated Mon, 19 Nov 2018 05:51:12 + with message-id and subject line Bug#913066: fixed in libp11 0.4.9-3 has caused the Debian Bug report #913066, regarding libengine-pkcs11-openssl: use versioned Breaks+Replaces: libengine-pkcs11-openssl1.1 (<< 0.4.9-2) to be marked as done. This

Processed: forcibly merging 912415 909233

Processing commands for cont...@bugs.debian.org: > forcemerge 912415 909233 Bug #912415 {Done: Peter Palfrader } [mirrors] mirror listing update for mirror.serverius.net Bug #909233 [mirrors] mirror listing update for mirror.serverius.net Marked Bug as done Merged 909233 912415 > thanks Stopping

Bug#907532: marked as done (mirror submission for mirror.rise.ph)

Your message dated Mon, 19 Nov 2018 07:13:28 + with message-id <20181119071328.gr13...@sarek.noreply.org> and subject line Re: Bug#907532: mirror submission for mirror.rise.ph has caused the Debian Bug report #907532, regarding mirror submission for mirror.rise.ph to be marked as done. This me

Bug#908129: marked as done (mirror submission for mirror.vpsnet.com)

Your message dated Mon, 19 Nov 2018 07:14:33 + with message-id <5bf262d98015d_3642af9ab8050dc21...@godard.mail> and subject line Bug #908129 in mirrors fixed has caused the Debian Bug report #908129, regarding mirror submission for mirror.vpsnet.com to be marked as done. This means that you cl

Bug#502942: marked as done ([kebo.vlsm.org] site name, tracefile name, sync script)

Your message dated Mon, 19 Nov 2018 07:17:20 + with message-id <20181119071720.gs13...@sarek.noreply.org> and subject line works now has caused the Debian Bug report #502942, regarding [kebo.vlsm.org] site name, tracefile name, sync script to be marked as done. This means that you claim that t

Bug#913534: marked as done (r-cran-shiny FTBFS with latest libjs-twitter-bootstrap-datepicker)

Your message dated Mon, 19 Nov 2018 07:19:55 + with message-id and subject line Bug#913534: fixed in r-cran-shiny 1.1.0+dfsg-3 has caused the Debian Bug report #913534, regarding r-cran-shiny FTBFS with latest libjs-twitter-bootstrap-datepicker to be marked as done. This means that you claim

Bug#914055: marked as done (gitaly: misses versioned dependency on gitaly-proto (and probably more))

Your message dated Mon, 19 Nov 2018 07:19:30 + with message-id and subject line Bug#914055: fixed in gitaly 0.111.4+debian-3 has caused the Debian Bug report #914055, regarding gitaly: misses versioned dependency on gitaly-proto (and probably more) to be marked as done. This means that you c

Bug#901264: marked as done ([20180621] mirror.yannic-bonenberger.com: out-of-date)

Your message dated Mon, 19 Nov 2018 07:49:24 + with message-id <20181119074924.ga23...@sarek.noreply.org> and subject line Re: Bug#901264: mirror submission for mirror.yannic-bonenberger.com has caused the Debian Bug report #901264, regarding [20180621] mirror.yannic-bonenberger.com: out-of-da

Processed: forcibly merging 912542 901298

Processing commands for cont...@bugs.debian.org: > forcemerge 912542 901298 Bug #912542 {Done: Peter Palfrader } [mirrors] mirror submission for mirror.aminidc.com Bug #912542 {Done: Peter Palfrader } [mirrors] mirror submission for mirror.aminidc.com Added tag(s) moreinfo. Bug #901496 [mirrors]

Bug#900384: marked as done ([20180621] mirror.as29550.net: non-/debian-path)

Your message dated Mon, 19 Nov 2018 07:55:40 + with message-id <20181119075540.ga24...@sarek.noreply.org> and subject line Re: Bug#900384: mirror submission for mirror.as29550.net has caused the Debian Bug report #900384, regarding [20180621] mirror.as29550.net: non-/debian-path to be marked as

Bug#901215: marked as done ([20180621] freedom.dicea.unifi.it: syncscript)

Your message dated Mon, 19 Nov 2018 07:53:58 + with message-id <20181119075358.ga23...@sarek.noreply.org> and subject line Re: Bug#901215: mirror submission for freedom.dicea.unifi.it has caused the Debian Bug report #901215, regarding [20180621] freedom.dicea.unifi.it: syncscript to be marked

Processed: closing 895408

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 d

Processed: closing 896523

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 d

Processed: closing 894846

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 don

Processed: closing 894847

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 don

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

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 pr

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

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 prob

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

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#913360: marked as done (libreoffice-base-drivers: please switch to libmariadb-java)

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#913997: marked as done (cmdtest: Should not 'provide' yarn)

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 tha

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

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)

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 me

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

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 th

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

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 acorn/6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.

Processed (with 1 error): closing 339441

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 /etc

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

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

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

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#651744: marked as done (Please transition cairomm for multiarch)

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 de

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

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 an

Bug#885202: marked as done (libctl: please migrate to guile-2.2)

Your message dated Sun, 18 Nov 2018 16:11:50 + with message-id and subject line Bug#885202: fixed in libctl 4.1.4-1 has caused the Debian Bug report #885202, regarding libctl: please migrate to guile-2.2 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#913964: marked as done (ntpsec with only one upstream NTP server (via dhcp))

Your message dated Sun, 18 Nov 2018 16:12:20 + with message-id and subject line Bug#913964: fixed in ntpsec 1.1.2+dfsg1-4 has caused the Debian Bug report #913964, regarding ntpsec with only one upstream NTP server (via dhcp) to be marked as done. This means that you claim that the problem ha

Bug#796600: marked as done (libgtkmm-3.0-doc: Embedded copy of jquery without source or copyright mention)

Your message dated Sun, 18 Nov 2018 16:10:50 + with message-id and subject line Bug#796600: fixed in gtkmm3.0 3.24.0-1 has caused the Debian Bug report #796600, regarding libgtkmm-3.0-doc: Embedded copy of jquery without source or copyright mention to be marked as done. This means that you c

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

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 t

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

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 with.

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

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 pro

Processed: closing 907866

Processing commands for cont...@bugs.debian.org: > close 907866 2.14-1 Bug #907866 [src:nasm] nasm: CVE-2018-16382 Marked as fixed in versions nasm/2.14-1. Bug #907866 [src:nasm] nasm: CVE-2018-16382 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -

Bug#335281: marked as done (tomboy hangs)

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 th

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

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 dea

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

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&paste the note title leads to tomboy having a wrong idea of the pasted font size to be marked as done. This me

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

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 deal

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

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 be

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

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 t

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

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)

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#473060: marked as done (tomboy: Built *.server file doesn't have all the translations)

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 t

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

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 marke

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

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 that

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

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 tha

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

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)

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 wi

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

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 with

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

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 proble

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

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. This

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

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 t

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

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 probl

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

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 that

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

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 prob

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

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 that

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

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 th

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

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 p

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

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 bee

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

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)

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 deal

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

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 be

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

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)

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 means

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

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 has

Bug#907316: marked as done (RM: tomboy -- RoQA; unmaintained, depends on ancient GNOME libraries)

Your message dated Sun, 18 Nov 2018 17:10:46 + with message-id and subject line Bug#907316: Removed package(s) from unstable has caused the Debian Bug report #907316, regarding RM: tomboy -- RoQA; unmaintained, depends on ancient GNOME libraries to be marked as done. This means that you claim

Bug#896883: marked as done (tomboy: Sychnronization fails: Unexpected DTD declaration. Line 6, position 3.)

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 #896883, regarding tomboy: Sychnronization fails: Unexpected DTD declaration. Line 6, position 3. to be marked as done. This means tha

Bug#623029: marked as done ([l10n-fr]: various errors in the translation (typo, etc.))

Your message dated Sun, 18 Nov 2018 17:13:57 + with message-id and subject line Bug#911197: Removed package(s) from unstable has caused the Debian Bug report #623029, regarding [l10n-fr]: various errors in the translation (typo, etc.) to be marked as done. This means that you claim that the p

Bug#545992: marked as done (tomboy-latex: Not working until disabled and enabled again at every startup)

Your message dated Sun, 18 Nov 2018 17:13:25 + with message-id and subject line Bug#910954: Removed package(s) from unstable has caused the Debian Bug report #545992, regarding tomboy-latex: Not working until disabled and enabled again at every startup to be marked as done. This means that y

Bug#533042: marked as done (tomboy-latex: Becomes incredibly slow with larger notes)

Your message dated Sun, 18 Nov 2018 17:13:25 + with message-id and subject line Bug#910954: Removed package(s) from unstable has caused the Debian Bug report #533042, regarding tomboy-latex: Becomes incredibly slow with larger notes to be marked as done. This means that you claim that the pro

Bug#697992: marked as done (bareftp: Typo in package description: "boomarks")

Your message dated Sun, 18 Nov 2018 17:13:57 + with message-id and subject line Bug#911197: Removed package(s) from unstable has caused the Debian Bug report #697992, regarding bareftp: Typo in package description: "boomarks" to be marked as done. This means that you claim that the problem ha

Bug#758789: marked as done (bareftp: Fix FTBFS on ppc64el)

Your message dated Sun, 18 Nov 2018 17:13:57 + with message-id and subject line Bug#911197: Removed package(s) from unstable has caused the Debian Bug report #758789, regarding bareftp: Fix FTBFS on ppc64el to be marked as done. This means that you claim that the problem has been dealt with.

Bug#885054: marked as done (bareftp: Depends on old GNOME libraries)

Your message dated Sun, 18 Nov 2018 17:13:57 + with message-id and subject line Bug#911197: Removed package(s) from unstable has caused the Debian Bug report #885054, regarding bareftp: Depends on old GNOME libraries to be marked as done. This means that you claim that the problem has been de

Bug#911199: marked as done (RM: docky -- RoQA; unmaintained, depends on ancient GNOME libraries)

Your message dated Sun, 18 Nov 2018 17:14:20 + with message-id and subject line Bug#911199: Removed package(s) from unstable has caused the Debian Bug report #911199, regarding RM: docky -- RoQA; unmaintained, depends on ancient GNOME libraries to be marked as done. This means that you claim

Bug#910954: marked as done (RM: tomboy-latex -- RoQA; depends on tomboy which is unmaintained)

Your message dated Sun, 18 Nov 2018 17:13:18 + with message-id and subject line Bug#910954: Removed package(s) from unstable has caused the Debian Bug report #910954, regarding RM: tomboy-latex -- RoQA; depends on tomboy which is unmaintained to be marked as done. This means that you claim th

Bug#891586: marked as done (tomboy-latex: Build-Depends on tomboy)

Your message dated Sun, 18 Nov 2018 17:13:25 + with message-id and subject line Bug#910954: Removed package(s) from unstable has caused the Debian Bug report #891586, regarding tomboy-latex: Build-Depends on tomboy to be marked as done. This means that you claim that the problem has been deal

Bug#780639: marked as done (bareftp: New version of BareFTP)

Your message dated Sun, 18 Nov 2018 17:13:57 + with message-id and subject line Bug#911197: Removed package(s) from unstable has caused the Debian Bug report #780639, regarding bareftp: New version of BareFTP to be marked as done. This means that you claim that the problem has been dealt with

Bug#590082: marked as done (docky: does not survive a suspend or hibernate cycle)

Your message dated Sun, 18 Nov 2018 17:14:38 + with message-id and subject line Bug#911199: Removed package(s) from unstable has caused the Debian Bug report #590082, regarding docky: does not survive a suspend or hibernate cycle to be marked as done. This means that you claim that the proble

  1   2   3   4   >