Bug#307987: marked as done (kernel-image-2.6-amd64-k8: does not depend on newest 2.6 kernel)

Your message dated Sat, 7 May 2005 08:51:34 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#307987: kernel-image-2.6-amd64-k8: does not depend on newest 2.6 kernel has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt

Bug#306898: marked as done (approx: detach option proposal)

Your message dated Sat, 07 May 2005 03:47:16 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#306898: fixed in approx 1.14 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Processed: severity important

Processing commands for [EMAIL PROTECTED]: reopen 305271 Bug#305271: Act: hangs around forever. Bug reopened, originator not changed. severity 305271 important Bug#305271: Act: hangs around forever. Severity set to `important'. close 305271 Bug#305271: Act: hangs around forever. 'close' is

Bug#307587: marked as done (kernel-package incompatible with experimental dpkg)

Your message dated Sat, 07 May 2005 04:32:03 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#307587: fixed in kernel-package 8.135 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#307323: marked as done (FTBFS on kfreebsd-gnu (assumes RLIMIT_LOCKS))

Your message dated Sat, 07 May 2005 05:17:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#307323: fixed in pdksh 5.2.14-19 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#306925: marked as done (SIGCHLD handlers don't preserve errno)

Your message dated Sat, 07 May 2005 05:32:03 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#306925: fixed in nis 3.13-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Processed: tagging 304367, closing 304367

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.14 tags 304367 - sarge Bug#304367: Should stop building slapd ldap-utils Tags were: sarge Tags removed: sarge close 304367 Bug#304367: Should stop building slapd ldap-utils 'close' is

Processed: tagging 306107, closing 306107

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.14 tags 306107 - sarge Bug#306107: gnome-doc-utils: FTBFS: missing build-depends Tags were: sarge Tags removed: sarge close 306107 Bug#306107: gnome-doc-utils: FTBFS: missing

Bug#306711: marked as done (sb-bsd-sockets build also failing on AMD64?)

Your message dated Sat, 07 May 2005 05:49:04 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#306711: fixed in sbcl 1:0.9.0.19-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#308007: marked as done (leafnode security bug)

Your message dated Sat, 7 May 2005 11:00:42 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#308007: leafnode security bug has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#253665: marked as done (syck_0.42-3(ia64/unstable): FTBFS: test failures)

Your message dated Sat, 07 May 2005 06:32:27 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#253665: fixed in syck 0.42-9 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#307990: marked as done (libzlib-ruby: Segmentation fault)

Your message dated Sat, 07 May 2005 06:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#307990: fixed in ruby1.8 1.8.2-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#250135: marked as done ([l10:ca] catalan debconf templates)

Your message dated Sat, 07 May 2005 07:02:06 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#250135: fixed in roxen3 3.3.63-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#232232: marked as done ([INTL:nl] dutch po-debconf translation)

Your message dated Sat, 07 May 2005 07:02:06 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#232232: fixed in roxen3 3.3.63-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#304311: marked as done (roxen3: please provide httpd-cgi)

Your message dated Sat, 07 May 2005 07:02:06 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#304311: fixed in roxen3 3.3.63-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#287431: marked as done ([l10n] Initial Czech translation of roxen3 debconf messages)

Your message dated Sat, 07 May 2005 07:02:06 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#287431: fixed in roxen3 3.3.63-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#288381: marked as done (cyrus21-common: cyrmaster is using obsolete setsockoption SO_BSDCOMPAT)

Your message dated Sat, 7 May 2005 08:35:13 -0300 with message-id [EMAIL PROTECTED] and subject line (no subject) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#276550: marked as done (persistence of pppd after connection is closed.)

Your message dated Sat, 7 May 2005 13:53:45 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#276550: ppp: ppd fails to continue after remote connection close has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#291429: marked as done (hpguid: does not reap dead children (xsane))

Your message dated Sat, 7 May 2005 09:40:27 -0300 with message-id [EMAIL PROTECTED] and subject line Fixed in hplip 0.9.2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility

Bug#304959: marked as done (libgnomedb2-common: Install gconf schemas in /etc)

Your message dated Sat, 07 May 2005 09:32:29 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#304959: fixed in libgnomedb 1.2.1-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#300964: marked as done (liblablgl-ocaml: Depends on ocaml-3.08, not available, so uninstallable)

Your message dated Sat, 7 May 2005 16:10:02 +0200 with message-id [EMAIL PROTECTED] and subject line ocaml 3.08.3 is now in testing :) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#240519: marked as done (ledit should divert/wrap ocamldebug)

Your message dated Sat, 7 May 2005 16:27:04 +0200 with message-id [EMAIL PROTECTED] and subject line ledit wrapper is no more part of ledit since ages, closing bug. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#290936: marked as done (liblablgtk2-ocaml: A lot of new dependencies)

Your message dated Sat, 7 May 2005 16:15:44 +0200 with message-id [EMAIL PROTECTED] and subject line Was not really a bug. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility

Bug#240518: marked as done (ledit: ocaml wrapper doesn't pass arguments)

Your message dated Sat, 7 May 2005 16:27:04 +0200 with message-id [EMAIL PROTECTED] and subject line ledit wrapper is no more part of ledit since ages, closing bug. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#307504: marked as done (bbkeys: Missing build dependency.)

Your message dated Sat, 07 May 2005 10:02:26 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#307504: fixed in bbkeys 0.9.0-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#269270: marked as done (ledit: duplicate manpage in bogus directory)

Your message dated Sat, 07 May 2005 10:47:17 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#269270: fixed in ledit 1.11-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#308021: marked as done (evince: Add DjVu support)

Your message dated Sat, 07 May 2005 11:17:17 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#308021: fixed in evince 0.3.0-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#307684: marked as done (x86info: FTBFS on amd64 while it should build)

Your message dated Sat, 07 May 2005 11:02:07 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#307684: fixed in x86info 1.13-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#307901: marked as done (phpmyadmin: fix for 307275 introduces potential for further config breakage)

Your message dated Sat, 07 May 2005 11:02:06 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#307901: fixed in phpmyadmin 4:2.6.2-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#307226: marked as done (devtodo: tdr segfault on amd64)

Your message dated Sat, 07 May 2005 11:32:04 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#307226: fixed in devtodo 0.1.18-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#287773: marked as done (devtodo: Maintainer adress alec@korn.ch no longer works)

Your message dated Sat, 07 May 2005 11:32:04 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#287773: fixed in devtodo 0.1.18-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#307698: marked as done (leafnode: Minor DoS issue in fetchnews)

Your message dated Sat, 7 May 2005 17:25:23 +0100 with message-id [EMAIL PROTECTED] and subject line [EMAIL PROTECTED]: Bug#70052: marked as done (Reloading whole groups list when you use a new server for the first time and it doesn't finish all)] has caused the attached Bug report to be marked

Bug#307600: marked as done (INTL:vi)

Your message dated Sat, 07 May 2005 12:17:03 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#307600: fixed in adjtimex 1.20-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#304165: marked as done (cvsgraph: new version 1.5.1 available)

Your message dated Sat, 07 May 2005 12:32:02 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#304165: fixed in cvsgraph 1.5.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#291555: marked as done (omitting slash causes strange mish-mash)

Your message dated Sat, 7 May 2005 09:33:31 -0700 with message-id [EMAIL PROTECTED] and subject line Fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#293625: marked as done (jackd and shm as non-root user)

Your message dated Sat, 7 May 2005 18:58:22 +0200 with message-id [EMAIL PROTECTED] and subject line closed because of no response from submitter has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#288154: marked as done (jamin: contains po file under /usr/lib/locale installed as mo file)

Your message dated Sat, 7 May 2005 18:57:26 +0200 with message-id [EMAIL PROTECTED] and subject line fixed in jamin 0.95.0 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility

Bug#264725: marked as done (jamin: FTBFS with gcc-3.4: conflicting types for 'set_EQ_curve_values')

Your message dated Sat, 7 May 2005 18:50:22 +0200 with message-id [EMAIL PROTECTED] and subject line fixed in jamin 0.95.0 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility

Bug#293627: marked as done (jackd and shm as non-root user)

Your message dated Sat, 7 May 2005 18:58:22 +0200 with message-id [EMAIL PROTECTED] and subject line closed because of no response from submitter has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#272018: marked as done (ardour-gtk: Funny gain curve behaviour)

Your message dated Sat, 7 May 2005 18:59:26 +0200 with message-id [EMAIL PROTECTED] and subject line closed because of no response from submitter has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#286878: marked as done (gnuift: FTBFS (amd64/gcc-4.0): cast from 'char*' to 'int' loses precision)

Your message dated Sat, 7 May 2005 18:55:55 +0200 with message-id [EMAIL PROTECTED] and subject line fixed in 0.1.14-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#266259: marked as done (gnuift: FTBFS with gcc-3.4: there are no arguments to `begin' that depend on a template parameter, so a declaration of `begin' must be available)

Your message dated Sat, 7 May 2005 18:55:55 +0200 with message-id [EMAIL PROTECTED] and subject line fixed in 0.1.14-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Processed: close

Processing commands for [EMAIL PROTECTED]: close 286458 Bug#286458: zadvi claims to support bz2 but doesn't 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Helge Kreutzmann [EMAIL PROTECTED] close 286453 Bug#286453: Missing

Bug#233322: marked as done (Inefficient packaging of arch independent data in package advi)

Your message dated Sat, 7 May 2005 19:14:13 +0200 with message-id [EMAIL PROTECTED] and subject line acknowledge NMU has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#307594: marked as done (apt-get tomcat4 package is not available)

Your message dated Sat, 7 May 2005 11:37:58 -0700 (PDT) with message-id [EMAIL PROTECTED] and subject line Bug#307594: apt-get tomcat4 package is not available has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#308071: marked as done (Removal of fileutils dummy package breaks kernel-image)

Your message dated Sat, 07 May 2005 15:16:33 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#308071: Removal of fileutils dummy package breaks kernel-image has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#306841: marked as done (inkscape: segfaults at startup when using Gnome smooth theme)

Your message dated Sat, 7 May 2005 14:27:35 -0500 with message-id [EMAIL PROTECTED] and subject line inkscape: segfaults at startup when using Gnome smooth theme has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#306621: marked as done (chown: cannot access `/var/cache/approx': No such file or directory)

Your message dated Sat, 7 May 2005 16:28:51 -0400 with message-id [EMAIL PROTECTED] and subject line /var/cache/approx has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#307344: marked as done (mc: menu entry for Debian source packages)

Your message dated Sat, 07 May 2005 16:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#307344: fixed in mc 1:4.6.0-4.6.1-pre3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#307292: marked as done (mc: Cannot browse inside .zip file)

Your message dated Sat, 07 May 2005 16:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#299932: fixed in mc 1:4.6.0-4.6.1-pre3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#299932: marked as done (mc: editing jar archives doesn't work anylonger)

Your message dated Sat, 07 May 2005 16:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#299932: fixed in mc 1:4.6.0-4.6.1-pre3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#298322: marked as done ([PATCH] Editing manpages ist not colored with t, vga, pm,...)

Your message dated Sat, 07 May 2005 16:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#298322: fixed in mc 1:4.6.0-4.6.1-pre3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#167986: marked as done (mc: Enable charset encoding)

Your message dated Sat, 07 May 2005 16:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#109956: fixed in mc 1:4.6.0-4.6.1-pre3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#109956: marked as done (Please enable charset conversion feature available in new upstream)

Your message dated Sat, 07 May 2005 16:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#109956: fixed in mc 1:4.6.0-4.6.1-pre3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#226987: marked as done (mc: don't Build-Depend on libgpm for GNU/non-Linux)

Your message dated Sat, 07 May 2005 16:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#226987: fixed in mc 1:4.6.0-4.6.1-pre3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#264890: marked as done (Enable Samba (smbfs) support for mc)

Your message dated Sat, 07 May 2005 16:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#264890: fixed in mc 1:4.6.0-4.6.1-pre3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#299210: marked as done ([PATCH] sh.syntax)

Your message dated Sat, 07 May 2005 16:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#299210: fixed in mc 1:4.6.0-4.6.1-pre3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#305649: marked as done (mc: Add antiword to view .doc files)

Your message dated Sat, 07 May 2005 16:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#305649: fixed in mc 1:4.6.0-4.6.1-pre3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#305859: marked as done (mc: refusal to chdir/start file action when spaces are typed in command prompt)

Your message dated Sat, 07 May 2005 16:32:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#305859: fixed in mc 1:4.6.0-4.6.1-pre3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#305199: marked as done (atmel-firmware: Missing Entry in etc/pcmcia/atmel.conf for Siemens Gigaset card)

Your message dated Sat, 07 May 2005 16:47:15 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#305199: fixed in atmel-firmware 1.3-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#308095: marked as done (udev: *1394 devices are not present, a default override would be nice.)

Your message dated Sat, 7 May 2005 22:57:25 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#308095: udev: *1394 devices are not present, a default override would be nice. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been

Bug#294588: marked as done (vim-vimoutliner: When used in a terminal white on black, it doesn't show characteres of first level)

Your message dated Sat, 7 May 2005 17:28:42 -0400 with message-id [EMAIL PROTECTED] and subject line Already fixed in previous packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#297178: marked as done (New NAT configuration fails because it doesn't listen on the ports it tests.)

Your message dated Sat, 7 May 2005 17:54:09 -0400 with message-id [EMAIL PROTECTED] and subject line oops has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#306456: marked as done (vim-full: Glib assertion failure on startup)

Your message dated Sun, 8 May 2005 00:13:40 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#306456: vim-full: Glib assertion failure on startup has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#299633: marked as done (fakeroot: Handle /usr/bin/fakeroot by alternatives)

Your message dated Sat, 07 May 2005 18:17:02 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#299633: fixed in fakeroot 1.2.11 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#269792: marked as done (fails to move inbox across partition boundary)

Your message dated Sat, 12 Feb 2005 00:03:27 +0100 with message-id [EMAIL PROTECTED] and subject line fails to move inbox across partition boundary has caused the attached Bug report 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#302414: marked as done (RFP: stopmotion -- Excellent program for creating stop motion animations)

Your message dated Sat, 07 May 2005 20:10:53 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#302414: fixed in stopmotion 0.3pre.0-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#287317: marked as done (ITP: belpic -- software to support the new Belgian electronical ID card)

Your message dated Sat, 07 May 2005 20:10:16 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#287317: fixed in belpic 1.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#300742: marked as done (Description doesn't describe it contains API docs)

Your message dated Sat, 07 May 2005 20:18:26 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#300742: fixed in vte 1:0.11.13-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#306492: marked as done (ITP: weechat -- Fast, light and extensible IRC client)

Your message dated Sat, 07 May 2005 20:08:34 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#306492: fixed in weechat 0.1.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#304288: marked as done (ITP: libtk-histentry-perl -- Implements an entry widget with history)

Your message dated Sat, 07 May 2005 20:20:18 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#304288: fixed in libtk-histentry-perl 0.42-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#178038: marked as done (Too many dependencies)

Your message dated Sat, 07 May 2005 20:31:24 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#178038: fixed in elinks 0.10.4-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#218453: marked as done (package has huge dependencies - please consider providing a elinks-light)

Your message dated Sat, 07 May 2005 20:31:24 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#178038: fixed in elinks 0.10.4-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#282037: marked as done (ITP: arb -- [Biology] Integrated package for data handling and analysis)

Your message dated Sat, 07 May 2005 20:26:49 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#282037: fixed in arb 0.0.20050318-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#304291: marked as done (ITP: libtk-splashscreen-perl -- Toplevel mega widget to display a splashscreen)

Your message dated Sat, 07 May 2005 20:21:10 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#304291: fixed in libtk-splashscreen-perl 1.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#306333: marked as done (ITP: londonlaw)

Your message dated Sat, 07 May 2005 20:29:17 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#306333: fixed in londonlaw 0.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#306768: marked as done (beecrypt: Outdated version provided in Debian)

Your message dated Sat, 07 May 2005 20:33:08 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#306768: fixed in beecrypt 4.1.2-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#306947: marked as done (Please rename to python-statgrab)

Your message dated Sat, 07 May 2005 20:29:37 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#306947: fixed in pystatgrab 0.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#306753: marked as done (libnsuml-java: Please use kaffe and move the package to main)

Your message dated Sat, 07 May 2005 20:28:06 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#306753: fixed in libnsuml-java 0.4.20-11 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#306143: marked as done (ulogd: New upstream version available)

Your message dated Sat, 07 May 2005 20:48:44 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#306143: fixed in ulogd 1.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#305847: marked as done (ITP: libservlet2.4-java -- Servlet 2.4 and JSP 2.0 Java classes and documentation)

Your message dated Sat, 07 May 2005 20:31:56 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#305847: fixed in libservlet2.4-java 5.0.30-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#303197: marked as done (ITA: ulogd -- The Netfilter Userspace Logging Daemon)

Your message dated Sat, 07 May 2005 20:48:44 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#303197: fixed in ulogd 1.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#307340: marked as done (Please provide libpoppler0-qt and libpoppler-qt-dev packages)

Your message dated Sat, 07 May 2005 20:41:22 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#307340: fixed in poppler 0.3.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#303116: marked as done (ITP: kronolith2 -- calendar component for Horde Framework)

Your message dated Sat, 07 May 2005 20:39:25 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#303116: fixed in kronolith2 2.0.3-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#299637: marked as done (please suggest the ulogd-* packages)

Your message dated Sat, 07 May 2005 20:48:44 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#299637: fixed in ulogd 1.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#306142: marked as done (ulogd: Upstream location in the copyright file is outdated)

Your message dated Sat, 07 May 2005 20:48:44 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#306142: fixed in ulogd 1.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#303118: marked as done (ITP: nag2 -- task list component for Horde Framework)

Your message dated Sat, 07 May 2005 20:39:45 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#303118: fixed in nag2 2.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#294058: marked as done (Nautilus stops responding to new files after a while)

Your message dated Sat, 07 May 2005 20:25:55 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#294058: fixed in gamin 0.0.26-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#261785: marked as done (ulogd: Log files owner/permissions)

Your message dated Sat, 07 May 2005 20:48:44 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#261785: fixed in ulogd 1.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#297075: marked as done (Please include Python bindings)

Your message dated Sat, 07 May 2005 20:25:55 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#297075: fixed in gamin 0.0.26-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#199110: marked as done (ITP: cherokee -- Extremely fast and tiny web server)

Your message dated Sat, 07 May 2005 20:48:30 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#199110: fixed in cherokee 0.4.21b01-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#284424: marked as done (Moin installation doesn't allow for Apache2)

Your message dated Sat, 07 May 2005 20:43:00 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#284424: fixed in moin 1.3.4-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#248272: marked as done (ulogd: pcap.log not a proper capture file after logrotate)

Your message dated Sat, 07 May 2005 20:48:44 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#248272: fixed in ulogd 1.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#290865: marked as done (Wrong packagename for ulogd-mysql in README.Debian)

Your message dated Sat, 07 May 2005 20:48:44 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#290865: fixed in ulogd 1.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#295856: marked as done (gamin: should depend on libglib2.0-0)

Your message dated Sat, 07 May 2005 20:25:55 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#295856: fixed in gamin 0.0.26-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#297739: marked as done (ulogd: FTBFS (amd64/gcc-4.0): static declaration of 'logfile' follows non-static declaration)

Your message dated Sat, 07 May 2005 20:48:44 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#297739: fixed in ulogd 1.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#301083: marked as done (ITP: libevolution-ruby -- revolution, ruby binding for the evolution mail client)

Your message dated Sat, 07 May 2005 20:31:03 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#301083: fixed in revolution 0.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#304540: marked as done (python2.4-moinmoin: README.Debian is missing)

Your message dated Sat, 07 May 2005 20:43:00 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#304540: fixed in moin 1.3.4-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#306906: marked as done (python2.2-mysqldb: Connection leak)

Your message dated Sat, 7 May 2005 17:50:19 -0700 with message-id [EMAIL PROTECTED] and subject line python2.2-mysqldb: Connection leak has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#297425: marked as done (ITA: iozone3 -- Filesystem and Disk Benchmarking Tool)

Your message dated Sat, 07 May 2005 22:32:07 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#297425: fixed in iozone3 226-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

  1   2   >