Bug#767801: marked as done (RM: latex-beamer -- RoQA; integrated into texlive)

Your message dated Mon, 03 Nov 2014 07:20:43 + with message-id and subject line Bug#767801: Removed package(s) from unstable has caused the Debian Bug report #767801, regarding RM: latex-beamer -- RoQA; integrated into texlive to be marked as done. This means that you claim that the problem h

Bug#766961: marked as done (RM: mapsembler2 [mips mipsel powerpc sparc] -- RoM; FTBFS)

Your message dated Mon, 03 Nov 2014 07:22:19 + with message-id and subject line Bug#766961: Removed package(s) from unstable has caused the Debian Bug report #766961, regarding RM: mapsembler2 [mips mipsel powerpc sparc] -- RoM; FTBFS to be marked as done. This means that you claim that the p

Bug#764250: marked as done (RM: jbossas4 -- ROM; obsolete, low popcon)

Your message dated Mon, 03 Nov 2014 07:18:48 + with message-id and subject line Bug#764250: Removed package(s) from unstable has caused the Debian Bug report #764250, regarding RM: jbossas4 -- ROM; obsolete, low popcon to be marked as done. This means that you claim that the problem has been

Bug#767795: marked as done (RM: libjboss-remoting-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:18:13 + with message-id and subject line Bug#767795: Removed package(s) from unstable has caused the Debian Bug report #767795, regarding RM: libjboss-remoting-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the pr

Bug#759637: marked as done (libjboss-remoting-java: Please replace dependencies on tomcat6 with tomcat8)

Your message dated Mon, 03 Nov 2014 07:18:18 + with message-id and subject line Bug#767795: Removed package(s) from unstable has caused the Debian Bug report #759637, regarding libjboss-remoting-java: Please replace dependencies on tomcat6 with tomcat8 to be marked as done. This means that y

Bug#465596: marked as done (jbossas4: provide a working application server)

Your message dated Mon, 03 Nov 2014 07:18:53 + with message-id and subject line Bug#764250: Removed package(s) from unstable has caused the Debian Bug report #465596, regarding jbossas4: provide a working application server to be marked as done. This means that you claim that the problem has

Bug#767797: marked as done (RM: libjboss-xml-binding-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:16:02 + with message-id and subject line Bug#767797: Removed package(s) from unstable has caused the Debian Bug report #767797, regarding RM: libjboss-xml-binding-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the

Bug#767794: marked as done (RM: libjboss-reflect-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:16:39 + with message-id and subject line Bug#767794: Removed package(s) from unstable has caused the Debian Bug report #767794, regarding RM: libjboss-reflect-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the pro

Bug#670280: marked as done (libjboss-reflect-java: debcheckout fails)

Your message dated Mon, 03 Nov 2014 07:16:45 + with message-id and subject line Bug#767794: Removed package(s) from unstable has caused the Debian Bug report #670280, regarding libjboss-reflect-java: debcheckout fails to be marked as done. This means that you claim that the problem has been d

Bug#767789: marked as done (RM: libjboss-integration-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:17:24 + with message-id and subject line Bug#767789: Removed package(s) from unstable has caused the Debian Bug report #767789, regarding RM: libjboss-integration-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the

Bug#767784: marked as done (RM: libjboss-cache1-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:14:17 + with message-id and subject line Bug#767784: Removed package(s) from unstable has caused the Debian Bug report #767784, regarding RM: libjboss-cache1-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the prob

Bug#767786: marked as done (RM: libjboss-cache3-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:15:28 + with message-id and subject line Bug#767786: Removed package(s) from unstable has caused the Debian Bug report #767786, regarding RM: libjboss-cache3-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the prob

Bug#670278: marked as done (libjboss-managed-java: debcheckout fails)

Your message dated Mon, 03 Nov 2014 07:12:15 + with message-id and subject line Bug#767790: Removed package(s) from unstable has caused the Debian Bug report #670278, regarding libjboss-managed-java: debcheckout fails to be marked as done. This means that you claim that the problem has been d

Bug#767790: marked as done (RM: libjboss-managed-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:12:10 + with message-id and subject line Bug#767790: Removed package(s) from unstable has caused the Debian Bug report #767790, regarding RM: libjboss-managed-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the pro

Bug#670279: marked as done (libjboss-metadata-java: debcheckout fails)

Your message dated Mon, 03 Nov 2014 07:12:49 + with message-id and subject line Bug#767791: Removed package(s) from unstable has caused the Debian Bug report #670279, regarding libjboss-metadata-java: debcheckout fails to be marked as done. This means that you claim that the problem has been

Bug#767791: marked as done (RM: libjboss-metadata-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:12:44 + with message-id and subject line Bug#767791: Removed package(s) from unstable has caused the Debian Bug report #767791, regarding RM: libjboss-metadata-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the pr

Bug#767782: marked as done (RM: libhibernate-jbosscache-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:13:19 + with message-id and subject line Bug#767782: Removed package(s) from unstable has caused the Debian Bug report #767782, regarding RM: libhibernate-jbosscache-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that

Bug#506313: marked as done (libjboss-web-services-java: new upstream available JBossWS 3.0.4 2008-10-21)

Your message dated Mon, 03 Nov 2014 07:09:43 + with message-id and subject line Bug#767796: Removed package(s) from unstable has caused the Debian Bug report #506313, regarding libjboss-web-services-java: new upstream available JBossWS 3.0.4 2008-10-21 to be marked as done. This means that y

Bug#767783: marked as done (RM: libjboss-aop-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:10:14 + with message-id and subject line Bug#767783: Removed package(s) from unstable has caused the Debian Bug report #767783, regarding RM: libjboss-aop-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the problem

Bug#767792: marked as done (RM: libjboss-microcontainer-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:11:34 + with message-id and subject line Bug#767792: Removed package(s) from unstable has caused the Debian Bug report #767792, regarding RM: libjboss-microcontainer-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that

Bug#767796: marked as done (RM: libjboss-web-services-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:09:37 + with message-id and subject line Bug#767796: Removed package(s) from unstable has caused the Debian Bug report #767796, regarding RM: libjboss-web-services-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that th

Bug#713203: marked as done (g-wrap: FTBFS: /bin/sh: 1: aclocal-1.11: not found)

Your message dated Mon, 03 Nov 2014 07:03:58 + with message-id and subject line Bug#713203: fixed in g-wrap 1.9.14-2.1 has caused the Debian Bug report #713203, regarding g-wrap: FTBFS: /bin/sh: 1: aclocal-1.11: not found to be marked as done. This means that you claim that the problem has be

Bug#767793: marked as done (RM: libjboss-profiler-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:02:57 + with message-id and subject line Bug#767793: Removed package(s) from unstable has caused the Debian Bug report #767793, regarding RM: libjboss-profiler-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the pr

Bug#767785: marked as done (RM: libjboss-cache2-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 07:04:11 + with message-id and subject line Bug#767785: Removed package(s) from unstable has caused the Debian Bug report #767785, regarding RM: libjboss-cache2-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the prob

Bug#761210: marked as done (g-wrap: please migrate to guile-2.0)

Your message dated Mon, 03 Nov 2014 07:03:58 + with message-id and subject line Bug#761210: fixed in g-wrap 1.9.14-2.1 has caused the Debian Bug report #761210, regarding g-wrap: please migrate to guile-2.0 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#582743: marked as done (libjboss-cache2-java: please package new upstream version 3.2.5.GA)

Your message dated Mon, 03 Nov 2014 07:04:16 + with message-id and subject line Bug#767785: Removed package(s) from unstable has caused the Debian Bug report #582743, regarding libjboss-cache2-java: please package new upstream version 3.2.5.GA to be marked as done. This means that you claim t

Bug#767787: marked as done (RM: libjboss-classloader-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 06:58:00 + with message-id and subject line Bug#767787: Removed package(s) from unstable has caused the Debian Bug report #767787, regarding RM: libjboss-classloader-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the

Bug#767788: marked as done (RM: libjboss-deployers-java -- ROM; component of jbossas4)

Your message dated Mon, 03 Nov 2014 06:57:20 + with message-id and subject line Bug#767788: Removed package(s) from unstable has caused the Debian Bug report #767788, regarding RM: libjboss-deployers-java -- ROM; component of jbossas4 to be marked as done. This means that you claim that the p

Bug#767211: marked as done (mongodb-server: Link to mongodb.service not created on install)

Your message dated Mon, 03 Nov 2014 06:04:22 + with message-id and subject line Bug#767211: fixed in mongodb 1:2.4.10-3 has caused the Debian Bug report #767211, regarding mongodb-server: Link to mongodb.service not created on install to be marked as done. This means that you claim that the p

Bug#739153: marked as done (waagent: please update to 2.0.3)

Your message dated Mon, 03 Nov 2014 05:18:49 + with message-id and subject line Bug#739153: fixed in waagent 2.0.8-0.1 has caused the Debian Bug report #739153, regarding waagent: please update to 2.0.3 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#762895: marked as done (called emacs-package-remove as a new-style add-on, but has no compat file.)

Your message dated Mon, 03 Nov 2014 05:03:59 + with message-id and subject line Bug#762895: fixed in riece 9.0.0-1 has caused the Debian Bug report #762895, regarding called emacs-package-remove as a new-style add-on, but has no compat file. to be marked as done. This means that you claim th

Bug#654944: marked as done (ITA: riece -- an IRC client for Emacs)

Your message dated Mon, 03 Nov 2014 05:03:59 + with message-id and subject line Bug#654944: fixed in riece 9.0.0-1 has caused the Debian Bug report #654944, regarding ITA: riece -- an IRC client for Emacs to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#767776: marked as done (debian/changelog improvements (grammatical etc.) proposed for Jessie)

Your message dated Mon, 03 Nov 2014 03:50:13 + with message-id and subject line Bug#767776: fixed in sisu 5.7.1-2 has caused the Debian Bug report #767776, regarding debian/changelog improvements (grammatical etc.) proposed for Jessie to be marked as done. This means that you claim that the p

Bug#767761: marked as done (sisu: Irritating terminal reporting bug, re composite documents & verbose mode)

Your message dated Mon, 03 Nov 2014 03:50:13 + with message-id and subject line Bug#767761: fixed in sisu 5.7.1-2 has caused the Debian Bug report #767761, regarding sisu: Irritating terminal reporting bug, re composite documents & verbose mode to be marked as done. This means that you claim

Bug#767477: marked as done (safe-rm: fails to install)

Your message dated Mon, 03 Nov 2014 03:22:48 + with message-id and subject line Bug#767477: fixed in safe-rm 0.12-1 has caused the Debian Bug report #767477, regarding safe-rm: fails to install to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#754134: marked as done (trafficserver: add support for ppc64el)

Your message dated Mon, 03 Nov 2014 01:34:10 + with message-id and subject line Bug#754134: fixed in trafficserver 5.1.1-1 has caused the Debian Bug report #754134, regarding trafficserver: add support for ppc64el to be marked as done. This means that you claim that the problem has been dealt

Bug#767287: marked as done (trafficserver: ftbfs on kfreebsd)

Your message dated Mon, 03 Nov 2014 01:34:11 + with message-id and subject line Bug#767287: fixed in trafficserver 5.1.1-1 has caused the Debian Bug report #767287, regarding trafficserver: ftbfs on kfreebsd to be marked as done. This means that you claim that the problem has been dealt with.

Bug#754808: marked as done (trafficserver: Disable Lua JIT in ppc64el)

Your message dated Mon, 03 Nov 2014 01:34:11 + with message-id and subject line Bug#754808: fixed in trafficserver 5.1.1-1 has caused the Debian Bug report #754808, regarding trafficserver: Disable Lua JIT in ppc64el to be marked as done. This means that you claim that the problem has been de

Bug#767855: marked as done (critterding-common: fails to upgrade from 'sid' - trying to overwrite /usr/share/critterding/pixmaps/cd.bmp)

Your message dated Mon, 03 Nov 2014 01:19:23 + with message-id and subject line Bug#767855: fixed in critterding 1.0-beta14+dfsg-2 has caused the Debian Bug report #767855, regarding critterding-common: fails to upgrade from 'sid' - trying to overwrite /usr/share/critterding/pixmaps/cd.bmp to

Bug#759756: marked as done ([libktpcommoninternalsprivate7] Typo "contians" in extended description)

Your message dated Mon, 03 Nov 2014 00:34:02 + with message-id and subject line Bug#759756: fixed in ktp-common-internals 0.8.1-3 has caused the Debian Bug report #759756, regarding [libktpcommoninternalsprivate7] Typo "contians" in extended description to be marked as done. This means that

Bug#439828: marked as done (gnome-applets: CPU frequency applet: Display more than one CPU at a time)

Your message dated Mon, 3 Nov 2014 01:33:52 +0100 with message-id <20141103003352.gb22...@free.fr> and subject line gnome-applets: CPU frequency applet: Display more than one CPU at a time has caused the Debian Bug report #439828, regarding gnome-applets: CPU frequency applet: Display more than on

Processed: reassign 696267 to gcc-4.8, fixed 696267 in 4.8.1-7, found 696267 in gcc-4.7/4.7.2-12, closing 731695 ...

Processing commands for cont...@bugs.debian.org: > # bts housekeeping: > # fixup versioning of fixed bugs that the bts considers to be not fixed > # reassign+affects bugs fixed in other packages > # unreproducible-or-not-a-bug must not be closed with a version, especially > not the reported one (

Bug#767498: marked as done (aces3: FTBFS on several architectures)

Your message dated Sun, 2 Nov 2014 23:41:53 +0100 with message-id <20141102224152.ga2...@ugent.be> and subject line Re: [Debichem-devel] Bug#767498: aces3: FTBFS on several architectures has caused the Debian Bug report #767498, regarding aces3: FTBFS on several architectures to be marked as done.

Bug#767600: marked as done (python-versuchung: FTBFS everywhere)

Your message dated Sun, 02 Nov 2014 22:34:13 + with message-id and subject line Bug#767600: fixed in python-versuchung 1.1-3 has caused the Debian Bug report #767600, regarding python-versuchung: FTBFS everywhere to be marked as done. This means that you claim that the problem has been dealt

Bug#765545: marked as done (RM: octave-ltfat [armhf mips] -- ROM; FTBFS)

Your message dated Sun, 2 Nov 2014 23:04:21 +0100 with message-id <20141102220421.gh3...@laboissiere.net> and subject line Re: Bug#765545: RM: octave-ltfat [armhf mips] -- ROM; FTBFS has caused the Debian Bug report #765545, regarding RM: octave-ltfat [armhf mips] -- ROM; FTBFS to be marked as done

Bug#767812: marked as done (abcde: new upstream release)

Your message dated Sun, 2 Nov 2014 22:12:54 + with message-id <20141102221254.gv7...@einval.com> and subject line Re: Bug#767812: abcde: new upstream release has caused the Debian Bug report #767812, regarding abcde: new upstream release to be marked as done. This means that you claim that the

Bug#767844: marked as done (wheezy-pu: package bashburn/3.0.1-1)

Your message dated Sun, 02 Nov 2014 22:07:50 + with message-id <1414966070.5807.1.ca...@adam-barratt.org.uk> and subject line Re: Bug#767844: wheezy-pu: package bashburn/3.0.1-1 has caused the Debian Bug report #767844, regarding wheezy-pu: package bashburn/3.0.1-1 to be marked as done. This m

Bug#767627: marked as done ([ocrfeeder] Unable to start program via menu entry)

Your message dated Sun, 02 Nov 2014 21:34:01 + with message-id and subject line Bug#767627: fixed in ocrfeeder 0.7.11-6 has caused the Debian Bug report #767627, regarding [ocrfeeder] Unable to start program via menu entry to be marked as done. This means that you claim that the problem has b

Bug#765850: marked as done (dvb-apps: /usr/share/dvb/dvb-t/uk-RidgeHill out of date data)

Your message dated Sun, 2 Nov 2014 21:30:15 + with message-id <20141102213015.ga12...@lambda.dereenigne.org> and subject line Re: dvb-apps: /usr/share/dvb/dvb-t/uk-RidgeHill out of date data has caused the Debian Bug report #765850, regarding dvb-apps: /usr/share/dvb/dvb-t/uk-RidgeHill out of

Bug#767636: marked as done (phabricator: Wrongly named French and Japanese debconf translations)

Your message dated Sun, 02 Nov 2014 21:20:24 + with message-id and subject line Bug#767636: fixed in phabricator 0~git20141101-1 has caused the Debian Bug report #767636, regarding phabricator: Wrongly named French and Japanese debconf translations to be marked as done. This means that you cl

Bug#767681: marked as done (nagios-snmp-plugins: fails to install: cp: cannot create regular file '/etc/nagios-plugins/config/snmp_cpfw.cfg': No such file or directory)

Your message dated Sun, 02 Nov 2014 21:19:49 + with message-id and subject line Bug#767681: fixed in nagios-snmp-plugins 1.1.1-11 has caused the Debian Bug report #767681, regarding nagios-snmp-plugins: fails to install: cp: cannot create regular file '/etc/nagios-plugins/config/snmp_cpfw.cfg

Processed: Re: Processed: forcemerge

Processing commands for cont...@bugs.debian.org: > close 764318 Bug #764318 [libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Bug #764322 [libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz'

Bug#757592: marked as done (Broken symbolic link from libwt-common to jPlayer)

Your message dated Sun, 2 Nov 2014 21:36:04 +0100 with message-id and subject line has caused the Debian Bug report #757592, regarding Broken symbolic link from libwt-common to jPlayer to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Processed: closing 767628

Processing commands for cont...@bugs.debian.org: > close 767628 Bug #767628 [pocl] pocl: ftbfs on several architectures Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 767628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767628 Debian Bug Tr

Bug#767809: marked as done (abook: wrong Vcs-Git link)

Your message dated Sun, 2 Nov 2014 20:56:45 +0100 with message-id <20141102195645.ga18...@anguilla.debian.or.at> and subject line Re: Bug#767809: abook: wrong Vcs-Git link has caused the Debian Bug report #767809, regarding abook: wrong Vcs-Git link to be marked as done. This means that you claim

Bug#767734: marked as done (upgrade failure: perl-modules depends on perl which is not configured yet)

Your message dated Sun, 02 Nov 2014 21:05:29 +0100 with message-id <871tplv052@turtle.gmx.de> and subject line Re: Bug#767734: upgrade failure: perl-modules depends on perl which is not configured yet has caused the Debian Bug report #767734, regarding upgrade failure: perl-modules depends on

Bug#767738: marked as done (FTBFS: hardcoded path to libgeotiff.so missing Multi-Arch component)

Your message dated Sun, 02 Nov 2014 19:51:43 + with message-id and subject line Bug#767738: fixed in ossim 1.8.16-3 has caused the Debian Bug report #767738, regarding FTBFS: hardcoded path to libgeotiff.so missing Multi-Arch component to be marked as done. This means that you claim that the

Bug#767763: marked as done (RFS: ossim/1.8.16-3 [RC])

Your message dated Sun, 02 Nov 2014 20:45:44 +0100 with message-id <1414957544.2338.4.ca...@debian.org> and subject line Re: Bug#767763: RFS: ossim/1.8.16-3 [RC] has caused the Debian Bug report #767763, regarding RFS: ossim/1.8.16-3 [RC] to be marked as done. This means that you claim that the pr

Bug#552995: marked as done (ecb: ecb prevents breaks the 'Python' menu)

Your message dated Sun, 02 Nov 2014 20:24:02 +0100 with message-id <545684d2.8030...@balintreczey.hu> and subject line Re: unable to reproduce has caused the Debian Bug report #552995, regarding ecb: ecb prevents breaks the 'Python' menu to be marked as done. This means that you claim that the pro

Bug#452623: marked as done (emacs22-gtk: install fails with jde already in place)

Your message dated Sun, 02 Nov 2014 20:21:14 +0100 with message-id <5456842a.9040...@balintreczey.hu> and subject line Re: Bug#436088: emacs22-gtk: install fails with jde already in place has caused the Debian Bug report #452623, regarding emacs22-gtk: install fails with jde already in place to be

Bug#767799: marked as done (unblock: python-graph/1.8.2-6)

Your message dated Sun, 02 Nov 2014 19:18:25 + with message-id <1414955905.3691.1.ca...@adam-barratt.org.uk> and subject line Re: Bug#767799: unblock: python-graph/1.8.2-6 has caused the Debian Bug report #767799, regarding unblock: python-graph/1.8.2-6 to be marked as done. This means that yo

Bug#426805: marked as done (Extremely high emacs CPU usage when using ecb-mode)

Your message dated Sun, 02 Nov 2014 20:12:54 +0100 with message-id <54568236.3000...@balintreczey.hu> and subject line Re: ecb? has caused the Debian Bug report #426805, regarding Extremely high emacs CPU usage when using ecb-mode to be marked as done. This means that you claim that the problem ha

Bug#471693: marked as done (ecb forbids quitting emacs)

Your message dated Sun, 02 Nov 2014 20:06:39 +0100 with message-id <545680bf.2010...@balintreczey.hu> and subject line Re: ecb forbids quitting emacs has caused the Debian Bug report #471693, regarding ecb forbids quitting emacs to be marked as done. This means that you claim that the problem has

Bug#767751: marked as done (wine32-tools: fails to upgrade, breaks wine32-dev-tools needed)

Your message dated Sun, 02 Nov 2014 18:49:41 + with message-id and subject line Bug#767751: fixed in wine 1.6.2-16 has caused the Debian Bug report #767751, regarding wine32-tools: fails to upgrade, breaks wine32-dev-tools needed to be marked as done. This means that you claim that the proble

Bug#767765: marked as done (libsane: fails to purge)

Your message dated Sun, 02 Nov 2014 19:45:53 +0100 with message-id <2659464.GrS48ubqWd@merkur> and subject line Re: Bug#767765: libsane: fails to purge has caused the Debian Bug report #767765, regarding libsane: fails to purge to be marked as done. This means that you claim that the problem has b

Bug#767633: marked as done (nsca-ng: depends on libsystemd-dev, which is unavailable on kfreebsd)

Your message dated Sun, 2 Nov 2014 19:27:09 +0100 with message-id <20141102182709.gb14...@formorer.de> and subject line Re: Bug#767633: nsca-ng: depends on libsystemd-dev, which is unavailable on kfreebsd has caused the Debian Bug report #767633, regarding nsca-ng: depends on libsystemd-dev, which

Bug#767654: marked as done (security-tracker: DSA-3061-1 vs. tracker)

Your message dated Sun, 2 Nov 2014 19:17:01 +0100 with message-id <20141102181701.GA20845@eldamar.local> and subject line Re: Bug#767654: security-tracker: DSA-3061-1 vs. tracker has caused the Debian Bug report #767654, regarding security-tracker: DSA-3061-1 vs. tracker to be marked as done. This

Bug#765937: marked as done ([enigmail] Incompatible with armhf)

Your message dated Sun, 02 Nov 2014 18:18:57 + with message-id and subject line Bug#765937: fixed in enigmail 2:1.7.2-2 has caused the Debian Bug report #765937, regarding [enigmail] Incompatible with armhf to be marked as done. This means that you claim that the problem has been dealt with.

Bug#760845: marked as done (enigmail: update config.guess to fix FTBFS on ppc64el)

Your message dated Sun, 02 Nov 2014 18:18:57 + with message-id and subject line Bug#760845: fixed in enigmail 2:1.7.2-2 has caused the Debian Bug report #760845, regarding enigmail: update config.guess to fix FTBFS on ppc64el to be marked as done. This means that you claim that the problem ha

Bug#689919: marked as done (subversion: includes a non-free file)

Your message dated Sun, 2 Nov 2014 13:04:04 -0500 with message-id and subject line Re: Bug#689919: closed by Michael Gilbert (re: subversion: includes a non-free file) has caused the Debian Bug report #689919, regarding subversion: includes a non-free file to be marked as done. This means that

Bug#767778: marked as done (unblock: astroid/1.2.1-1)

Your message dated Sun, 2 Nov 2014 17:52:30 + with message-id <20141102175230.gj18...@lupin.home.powdarrmonkey.net> and subject line Re: Bug#767778: unblock: astroid/1.2.1-1 has caused the Debian Bug report #767778, regarding unblock: astroid/1.2.1-1 to be marked as done. This means that you c

Bug#767772: marked as done (python-ssdeep: Depends on ssdeep, scheduled for removal)

Your message dated Sun, 2 Nov 2014 18:45:13 +0100 with message-id and subject line Re: Bug#764496: RM: ssdeep/all suites -- ROM; non-distributable has caused the Debian Bug report #767772, regarding python-ssdeep: Depends on ssdeep, scheduled for removal to be marked as done. This means that you

Bug#764496: marked as done (RM: ssdeep/oldstable+snapshot -- ROM; non-distributable)

Your message dated Sun, 2 Nov 2014 18:45:13 +0100 with message-id and subject line Re: Bug#764496: RM: ssdeep/all suites -- ROM; non-distributable has caused the Debian Bug report #764496, regarding RM: ssdeep/oldstable+snapshot -- ROM; non-distributable to be marked as done. This means that you

Bug#767770: marked as done (unblock: fop/1:1.1.dfsg2-1)

Your message dated Sun, 2 Nov 2014 17:40:28 + with message-id <20141102174028.gg18...@lupin.home.powdarrmonkey.net> and subject line Re: Bug#767770: unblock: fop/1:1.1.dfsg2-1 has caused the Debian Bug report #767770, regarding unblock: fop/1:1.1.dfsg2-1 to be marked as done. This means that y

Bug#767768: marked as done (unblock: doxygen/1.8.8-5)

Your message dated Sun, 2 Nov 2014 17:42:32 + with message-id <20141102174232.gh18...@lupin.home.powdarrmonkey.net> and subject line Re: Bug#767768: unblock: doxygen/1.8.8-5 has caused the Debian Bug report #767768, regarding unblock: doxygen/1.8.8-5 to be marked as done. This means that you c

Bug#766739: marked as done (override: libupnp-dev:libdevel/optional, libupnp6:libs/optional, libupnp6-dbg:debug/optional, libupnp6-dev:libdevel/optional, libupnp6-doc:doc/optional)

Your message dated Sun, 02 Nov 2014 17:34:11 + with message-id and subject line Bug#766739: fixed has caused the Debian Bug report #766739, regarding override: libupnp-dev:libdevel/optional, libupnp6:libs/optional, libupnp6-dbg:debug/optional, libupnp6-dev:libdevel/optional, libupnp6-doc:doc

Bug#766830: marked as done (override: ibus-table-cangjie:utils/optional and similars)

Your message dated Sun, 02 Nov 2014 17:36:06 + with message-id and subject line Bug#766830: fixed has caused the Debian Bug report #766830, regarding override: ibus-table-cangjie:utils/optional and similars to be marked as done. This means that you claim that the problem has been dealt with.

Bug#764283: marked as done (override: libgnatcoll1.6:libs/optional)

Your message dated Sun, 02 Nov 2014 17:28:02 + with message-id and subject line Bug#764283: fixed has caused the Debian Bug report #764283, regarding override: libgnatcoll1.6:libs/optional to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#766657: marked as done (override: lxtask:x11/optional)

Your message dated Sun, 02 Nov 2014 17:26:50 + with message-id and subject line Bug#766657: fixed has caused the Debian Bug report #766657, regarding override: lxtask:x11/optional to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#766699: marked as done (override: unifont-bin:x11/extra -- ROM)

Your message dated Sun, 02 Nov 2014 17:25:09 + with message-id and subject line Bug#766699: fixed has caused the Debian Bug report #766699, regarding override: unifont-bin:x11/extra -- ROM to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#766661: marked as done (override: lxterminal:x11/optional)

Your message dated Sun, 02 Nov 2014 17:25:40 + with message-id and subject line Bug#71: fixed has caused the Debian Bug report #71, regarding override: lxterminal:x11/optional to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#766658: marked as done (override: lxlauncher:x11/optional)

Your message dated Sun, 02 Nov 2014 17:26:09 + with message-id and subject line Bug#766658: fixed has caused the Debian Bug report #766658, regarding override: lxlauncher:x11/optional to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#766742: marked as done (override: libc-client2007e-dev:libdevel/extra)

Your message dated Sun, 02 Nov 2014 17:22:32 + with message-id and subject line Bug#766742: fixed has caused the Debian Bug report #766742, regarding override: libc-client2007e-dev:libdevel/extra to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#766663: marked as done (override: lxrandr:x11/optional)

Your message dated Sun, 02 Nov 2014 17:23:29 + with message-id and subject line Bug#73: fixed has caused the Debian Bug report #73, regarding override: lxrandr:x11/optional to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#767345: marked as done (override: libreoffice-l10n-ku:oldlibs/extra, libreoffice-presentation-minimizer:oldlibs/extra)

Your message dated Sun, 02 Nov 2014 17:21:10 + with message-id and subject line Bug#767345: fixed has caused the Debian Bug report #767345, regarding override: libreoffice-l10n-ku:oldlibs/extra, libreoffice-presentation-minimizer:oldlibs/extra to be marked as done. This means that you claim

Bug#761019: marked as done (gstreamer1.0: gir packages missing Depends against libraries)

Your message dated Sun, 02 Nov 2014 17:19:17 + with message-id and subject line Bug#761019: fixed in gstreamer1.0 1.4.3-1.2 has caused the Debian Bug report #761019, regarding gstreamer1.0: gir packages missing Depends against libraries to be marked as done. This means that you claim that the

Bug#765464: marked as done (ftp.debian.org: Contact details and wiki page link to https://ftp-master.debian.org/)

Your message dated Sun, 2 Nov 2014 18:18:19 +0100 with message-id and subject line Re: Bug#765464: ftp.debian.org: Contact details and wiki page link to https://ftp-master.debian.org/ has caused the Debian Bug report #765464, regarding ftp.debian.org: Contact details and wiki page link to https

Bug#752299: marked as done (qupzilla: Not all ca-certificates are automatically recognized)

Your message dated Sun, 02 Nov 2014 17:19:36 + with message-id and subject line Bug#752299: fixed in qupzilla 1.8.3.1~dfsg1-3 has caused the Debian Bug report #752299, regarding qupzilla: Not all ca-certificates are automatically recognized to be marked as done. This means that you claim that

Bug#657281: marked as done (src/java/org/apache/fop/pdf/ sRGB Color Space Profile.icm is non-free)

Your message dated Sun, 02 Nov 2014 16:49:12 + with message-id and subject line Bug#657281: fixed in fop 1:1.1.dfsg2-1 has caused the Debian Bug report #657281, regarding src/java/org/apache/fop/pdf/ sRGB Color Space Profile.icm is non-free to be marked as done. This means that you claim that

Bug#767041: marked as done (kephra: Fails with "You did not specify a file name")

Your message dated Sun, 02 Nov 2014 16:49:47 + with message-id and subject line Bug#767041: fixed in kephra 0.4.3.34+dfsg-2 has caused the Debian Bug report #767041, regarding kephra: Fails with "You did not specify a file name" to be marked as done. This means that you claim that the problem

Bug#761915: marked as done (gst-plugins-base1.0: gir packages missing Depends against libraries)

Your message dated Sun, 02 Nov 2014 16:19:19 + with message-id and subject line Bug#761915: fixed in gst-plugins-base1.0 1.4.3-1.1 has caused the Debian Bug report #761915, regarding gst-plugins-base1.0: gir packages missing Depends against libraries to be marked as done. This means that you

Bug#762147: marked as done (fslint: "Delete" action always hangs and consumes 100% CPU for a long time)

Your message dated Mon, 03 Nov 2014 00:07:44 +0800 with message-id <545656d0.30...@rolf.leggewie.biz> and subject line closing as fixed has caused the Debian Bug report #762147, regarding fslint: "Delete" action always hangs and consumes 100% CPU for a long time to be marked as done. This means t

Bug#699400: marked as done (ss_extract uses deprecated ffmpeg invocation)

Your message dated Sun, 02 Nov 2014 16:04:48 + with message-id and subject line Bug#699400: fixed in performous 0.7.0+git20140715-2 has caused the Debian Bug report #699400, regarding ss_extract uses deprecated ffmpeg invocation to be marked as done. This means that you claim that the problem

Bug#767755: marked as done (performous-tools: ss_extract and ss_cover_conv binaries are not built due to broken ImageMagick detection)

Your message dated Sun, 02 Nov 2014 16:04:48 + with message-id and subject line Bug#767755: fixed in performous 0.7.0+git20140715-2 has caused the Debian Bug report #767755, regarding performous-tools: ss_extract and ss_cover_conv binaries are not built due to broken ImageMagick detection to

Bug#767693: marked as done (unblock: hwloc/1.10.0-3)

Your message dated Sun, 2 Nov 2014 16:02:44 + with message-id <20141102160244.gf18...@lupin.home.powdarrmonkey.net> and subject line Re: Bug#767693: unblock: hwloc/1.10.0-3 has caused the Debian Bug report #767693, regarding unblock: hwloc/1.10.0-3 to be marked as done. This means that you cla

Bug#766766: marked as done (Compilation fixes for arm64)

Your message dated Sun, 02 Nov 2014 15:52:30 + with message-id and subject line Bug#766766: fixed in xfce4-battery-plugin 1.0.5-4 has caused the Debian Bug report #766766, regarding Compilation fixes for arm64 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#767417: marked as done (python-gmpy2: FTBFS: test failures)

Your message dated Sun, 02 Nov 2014 15:51:14 + with message-id and subject line Bug#767417: fixed in python-gmpy2 2.0.4-2 has caused the Debian Bug report #767417, regarding python-gmpy2: FTBFS: test failures to be marked as done. This means that you claim that the problem has been dealt with

Bug#767311: marked as done (tightvnc FTBFS on arm64, build system issue.)

Your message dated Sun, 02 Nov 2014 15:51:25 + with message-id and subject line Bug#767311: fixed in tightvnc 1.3.9-6.5 has caused the Debian Bug report #767311, regarding tightvnc FTBFS on arm64, build system issue. to be marked as done. This means that you claim that the problem has been de

Bug#767658: marked as done (doxygen: Patch to bootstrap without Qt)

Your message dated Sun, 02 Nov 2014 15:49:31 + with message-id and subject line Bug#767658: fixed in doxygen 1.8.8-5 has caused the Debian Bug report #767658, regarding doxygen: Patch to bootstrap without Qt to be marked as done. This means that you claim that the problem has been dealt with.

Bug#764130: marked as done (libdbi1: double-free in dbi_shutdown_r)

Your message dated Sun, 02 Nov 2014 15:50:52 + with message-id and subject line Bug#764130: fixed in libdbi 0.9.0-4 has caused the Debian Bug report #764130, regarding libdbi1: double-free in dbi_shutdown_r to be marked as done. This means that you claim that the problem has been dealt with.

  1   2   3   >