Bug#400810: marked as done (libvisual-0.4-0: jess visual plugin segfaults totem while )

Your message dated Sat, 24 Nov 2007 09:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400810: fixed in libvisual-plugins 0.4.0.dfsg.1-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

Bug#451213: marked as done (ITA: libvisual-plugins -- Audio visualization framework)

Your message dated Sat, 24 Nov 2007 09:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#451213: fixed in libvisual-plugins 0.4.0.dfsg.1-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

Bug#385741: marked as done (sysv-rc: invoke-rc.d detects false running processes)

Your message dated Sat, 24 Nov 2007 10:14:11 +0100 with message-id <[EMAIL PROTECTED]> and subject line #385741 sysv-rc: invoke-rc.d detects false running processes 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 n

Bug#451112: marked as done (libvisual-plugins: FTBFS on kfreebsd-amd64: unsatisfied Build-Depends)

Your message dated Sat, 24 Nov 2007 09:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#451112: fixed in libvisual-plugins 0.4.0.dfsg.1-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

Bug#437528: marked as done (should be able to have an xorg.conf with no ServerLayout, Device, or Screen)

Your message dated Sat, 24 Nov 2007 10:11:41 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#437528: should be able to have an xorg.conf with no ServerLayout, Device, or Screen has caused the attached Bug report to be marked as done. This means that you claim that the problem has b

Bug#446111: marked as done (xserver-xorg-core: X crashes immediately after wakeup from suspend-to-RAM (APM), but not always :-))

Your message dated Sat, 24 Nov 2007 10:14:45 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#446111: xserver-xorg-core: X crashes immediately after wakeup from suspend-to-RAM (APM), but not always :-) has caused the attached Bug report to be marked as done. This means that you clai

Bug#393366: marked as done (Source package contains non-free IETF RFC/I-D's)

Your message dated Sat, 24 Nov 2007 09:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#393366: fixed in dnswalk 2.0.2.dfsg.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 it

Bug#452534: marked as done (burgerspace - FTBFS: error: SDL.h: No such file or directory)

Your message dated Sat, 24 Nov 2007 09:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#452534: fixed in burgerspace 1.8.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 no

Bug#452597: marked as done (gforge-plugins-extra: Please use shared copy of fckedit)

Your message dated Sat, 24 Nov 2007 09:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#452597: fixed in gforge 4.6.99+svn6225-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 i

Bug#448523: marked as done (Please mention updatedb in package description)

Your message dated Sat, 24 Nov 2007 09:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#448523: fixed in findutils 4.2.31-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#448398: marked as done (findutils: Proposal to add idle I/O priority by default)

Your message dated Sat, 24 Nov 2007 09:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#448398: fixed in findutils 4.2.31-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#57748: marked as done (findutils should use alternatives)

Your message dated Sat, 24 Nov 2007 09:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#57748: fixed in findutils 4.2.31-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#342713: marked as done (findutils: /usr/bin/updatedb should read /etc/updatedb.conf)

Your message dated Sat, 24 Nov 2007 09:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#342713: fixed in findutils 4.2.31-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#163208: marked as done (update-alternatives 1.9.21 should manage locate and slocate)

Your message dated Sat, 24 Nov 2007 09:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#57748: fixed in findutils 4.2.31-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#344213: marked as done (/etc/updatedb.conf.local)

Your message dated Sat, 24 Nov 2007 09:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#344213: fixed in findutils 4.2.31-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#450429: marked as done (binutils: Cross install target should remove /usr/lib64 as well as /usr/lib)

Your message dated Sat, 24 Nov 2007 11:47:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#450429: fixed in binutils 2.18.1~cvs20071027-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 cas

Bug#446542: marked as done (heimdal: [INTL:pt] Updated Portuguese translation for debconf messages)

Your message dated Sat, 24 Nov 2007 12:16:35 + with message-id <[EMAIL PROTECTED]> and subject line Fixed on 1.0.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 your responsibility to

Bug#446714: marked as done (gcc-4.3: Fails to build a program which builds fine with gcc-4.1)

Your message dated Sat, 24 Nov 2007 13:03:27 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#446714: gcc-4.3: Fails to build a program which builds fine with gcc-4.1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt w

Bug#451806: marked as done (libopensync-plugin-irmc_0.34-1(alpha/experimental): FTBFS: gp-relative relocation against dynamic symbol irda_crc16_table)

Your message dated Sat, 24 Nov 2007 11:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#451806: fixed in libopensync-plugin-irmc 0.34-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 ca

Bug#449192: marked as done (glibc - FTBFS: make: *** [clean] Error 1)

Your message dated Sat, 24 Nov 2007 11:56:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#449192: acknowledged by developer (closing 449192) 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

Processed: closing 449192

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.11 > close 449192 2.7-1 Bug#449192: glibc - FTBFS: make: *** [clean] Error 1 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 2.7-1,

Bug#437819: marked as done (New upstream version available (1.0.1))

Your message dated Sat, 24 Nov 2007 12:30:07 + with message-id <[EMAIL PROTECTED]> and subject line Already released... 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#452646: marked as done (rt73-source: Module package generated with m-a contains /usr/share/README.Debian)

Your message dated Sat, 24 Nov 2007 12:32:13 + with message-id <[EMAIL PROTECTED]> and subject line Bug#452646: fixed in rt73 1:1.0.3.6-cvs20071123-dfsg1-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 th

Bug#452312: marked as done (Iceweasel FTBFS in current sid)

Your message dated Sat, 24 Nov 2007 12:32:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#452312: fixed in iceweasel 2.0.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 no

Bug#451626: marked as done (CVE-2007-5907, CVE-2007-5906 possible denial of service vulnerability)

Your message dated Sat, 24 Nov 2007 14:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#451626: fixed in xen-3 3.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 your

Bug#447795: marked as done (xen-utils-3.0.3-1: [CVE-2007-3919] xenmon.py / xenbaked insecure file accesss)

Your message dated Sat, 24 Nov 2007 14:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#447795: fixed in xen-3 3.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 your

Bug#447821: marked as done (xmms-singit: Depends on removed libssl0.9.7)

Your message dated Sat, 24 Nov 2007 15:57:34 +0100 with message-id <[EMAIL PROTECTED]> and subject line Package removed from Experimental 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#411595: marked as done (xmms-singit_0.1.33-1(hppa/experimental): FTBFS: outdated build-dependency)

Your message dated Sat, 24 Nov 2007 15:57:34 +0100 with message-id <[EMAIL PROTECTED]> and subject line Package removed from Experimental 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#338123: marked as done (openoffice.org-gnome: OpenOffice does not use gnome's file dialogs)

Your message dated Sat, 24 Nov 2007 16:22:12 +0100 with message-id <[EMAIL PROTECTED]> and subject line Close 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 to reopen

Bug#452675: marked as done (rpy: FTBFS: Error creating rpy.dvi)

Your message dated Sat, 24 Nov 2007 14:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#452675: fixed in rpy 1.0.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 r

Bug#445273: marked as done (fai-client: /var/log/fai/current tree readable by everyone)

Your message dated Sat, 24 Nov 2007 16:35:08 +0100 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 reo

Bug#347195: marked as done (openoffice.org-gnome: Save document confirmation moves window focus)

Your message dated Sat, 24 Nov 2007 16:35:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Close 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 to reopen

Bug#452516: marked as done (Errornous logic in updatebase)

Your message dated Sat, 24 Nov 2007 15:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#452516: fixed in fai 3.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 now your res

Bug#367793: marked as done (openoffice.org-base: Base hangs when saving new record with database forms I will attach)

Your message dated Sat, 24 Nov 2007 17:05:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line 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 this is not the case it is now your responsibility to reopen the

Bug#450627: marked as done (pdfedit: segfaults while opening edited by it before pdf)

Your message dated Sat, 24 Nov 2007 16:17:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#450627: fixed in pdfedit 0.3.2-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 yo

Bug#338123: marked as done (openoffice.org-gnome: OpenOffice does not use gnome's file dialogs)

Your message dated Sat, 24 Nov 2007 18:06:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line Close 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 to reopen

Bug#416055: marked as done ([PATCH] fix for kernel 2.6.19+)

Your message dated Sat, 24 Nov 2007 17:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#416055: fixed in cdfs-src 2.6.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

Bug#442269: marked as done (nfs-common: showmount lists nfs mounts that are no more mounted.)

Your message dated Sat, 24 Nov 2007 18:19:51 +0100 with message-id <[EMAIL PROTECTED]> and subject line Closing #442269 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#52214: marked as done (base-passwd: removes local users/groups from reserved id space)

Your message dated Sat, 24 Nov 2007 18:24:26 +0100 with message-id <[EMAIL PROTECTED]> and subject line rommer 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 th

Bug#347195: marked as done (openoffice.org-gnome: Save document confirmation moves window focus)

Your message dated Sat, 24 Nov 2007 18:21:23 +0100 with message-id <[EMAIL PROTECTED]> and subject line Close 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 to reopen

Bug#435006: marked as done (cdfs-src: update for kernel 2.6.23 necessary)

Your message dated Sat, 24 Nov 2007 17:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#435006: fixed in cdfs-src 2.6.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

Bug#452432: marked as done ([cdfs-src] fails to build with recent kernels)

Your message dated Sat, 24 Nov 2007 17:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#452432: fixed in cdfs-src 2.6.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

Bug#451965: marked as done (nfsstat has an error with --mounted)

Your message dated Sat, 24 Nov 2007 17:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#451965: fixed in nfs-utils 1:1.1.1-10 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 n

Bug#434513: marked as done (mod-mono: [INTL:it] Italian debconf templates translation)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434513: fixed in mod-mono 1.2.4-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 y

Bug#436281: marked as done ([l10n] Updated Czech translation of mod-mono debconf messages)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436281: fixed in mod-mono 1.2.4-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 y

Bug#436413: marked as done (mod-mono: [INTL:sv] Swedish debconf templates translation )

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436413: fixed in mod-mono 1.2.4-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 y

Bug#433711: marked as done (mod-mono: [debconf_rewrite] Debconf templates and debian/control review)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#433711: fixed in mod-mono 1.2.4-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 y

Bug#433201: marked as done (mod-mono: [INTL:de] Updated german debconf translation)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#433201: fixed in mod-mono 1.2.4-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 y

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

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436854: fixed in mod-mono 1.2.4-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 y

Bug#435906: marked as done (mod-mono: [INTL:es] Update Spanish translation template po-debconf)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#435906: fixed in mod-mono 1.2.4-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 y

Bug#434436: marked as done (mod-mono : [INTL:pt] Updated Portuguese translation for debconf messages)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434436: fixed in mod-mono 1.2.4-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 y

Bug#434321: marked as done ([INTL:gl] Galician debconf template translation for mod-mono)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434321: fixed in mod-mono 1.2.4-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 y

Bug#434320: marked as done (mod-mono: [INTL:ja] updated Japanese translation)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434320: fixed in mod-mono 1.2.4-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 y

Bug#434403: marked as done ([INTL:ta] debconf PO translations for the package mod-mono)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434403: fixed in mod-mono 1.2.4-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 y

Bug#434476: marked as done (mod-mono: [INTL:fr] French debconf templates translation update)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434476: fixed in mod-mono 1.2.4-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 y

Bug#434498: marked as done (mod-mono: [INTL:eu] Basque debconf templates translation)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434498: fixed in mod-mono 1.2.4-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 y

Bug#434407: marked as done (mod-mono: [INTL:de] updated German debconf translation)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434407: fixed in mod-mono 1.2.4-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 y

Bug#434408: marked as done (mod-mono: [INTL:ru] Russian debconf templates translation)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434408: fixed in mod-mono 1.2.4-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 y

Bug#434759: marked as done (mod-mono: [INTL:vi] Vietnamese debconf templates translation)

Your message dated Sat, 24 Nov 2007 17:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434759: fixed in mod-mono 1.2.4-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 y

Bug#449773: marked as done (linux-wlan-ng: debian/watch fails to report upstream's version)

Your message dated Sat, 24 Nov 2007 17:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#449773: fixed in linux-wlan-ng 0.2.8+svn1839+dfsg-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 th

[4]:

We offer the software for downloads only. http://jpyjnab.realluxoem.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#442126: marked as done (Installation fails, can't create dir /var/lib/mixmaster/Mix)

Your message dated Sat, 24 Nov 2007 18:09:24 + with message-id <[EMAIL PROTECTED]> and subject line Closing #442126 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#451400: marked as done (cwidget: FTBFS: /bin/sh: -c: line 0: syntax error near unexpected token `)')

Your message dated Sat, 24 Nov 2007 18:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#451400: fixed in cwidget 0.5.5-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 yo

Bug#441108: marked as done (coreutils: watch file)

Your message dated Sat, 24 Nov 2007 19:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#441108: fixed in coreutils 5.97-5.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#393362: marked as done (ITP: gqradio -- GTK based radio tuner)

Your message dated Sat, 24 Nov 2007 11:59:34 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#276135: marked as done (RFP: roadmap -- GPS based Car Navigation System)

Your message dated Sat, 24 Nov 2007 11:59:46 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#392289: marked as done (RFP: quickrefs-sysadmin -- various admin-related quick reference cards and quick reference HTML documents)

Your message dated Sat, 24 Nov 2007 11:59:48 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#398973: marked as done (ITP: qsa-x11-free -- Qt Script for Applications (QSA), is Trolltech's cross-platform scripting toolkit.)

Your message dated Sat, 24 Nov 2007 11:59:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#399719: marked as done (RFP: perle-serial -- Perle multiport serial device driver)

Your message dated Sat, 24 Nov 2007 11:59:49 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#400201: marked as done (ITP: tango -- TANGO is an object oriented distributed control system using CORBA)

Your message dated Sat, 24 Nov 2007 11:59:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#395085: marked as done (RFP: kurso -- multimedia computer program for teaching yourself Esperanto)

Your message dated Sat, 24 Nov 2007 11:59:48 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#398921: marked as done (RFP: roadmap -- a car navigation system for unix and pocketpc)

Your message dated Sat, 24 Nov 2007 11:59:46 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#399655: marked as done (RFP: mosref -- secure remote execution framework)

Your message dated Sat, 24 Nov 2007 11:59:48 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#319860: marked as done (RFP: pymedia -- Module for wav, mp3, ogg...)

Your message dated Sat, 24 Nov 2007 11:59:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#396061: marked as done (RFP: gnomego -- Play go against GnuGo and humans)

Your message dated Sat, 24 Nov 2007 11:59:48 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#395292: marked as done (ITP: lonewarrior -- Collect particles in universe with a spaceship)

Your message dated Sat, 24 Nov 2007 11:59:34 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#399519: marked as done (ITP: rdd-gui -- GTK based X11 frontend for rdd)

Your message dated Sat, 24 Nov 2007 11:59:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#398189: marked as done (ITP: fgrun -- A graphical launger for FlightGear)

Your message dated Sat, 24 Nov 2007 11:59:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#392847: marked as done (ITP: gnome-compiz-manager -- easily change compiz settings with gui)

Your message dated Sat, 24 Nov 2007 11:59:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#392288: marked as done (RFP: quickrefs-programming -- various coding-related quick reference cards and quick reference HTML documents)

Your message dated Sat, 24 Nov 2007 11:59:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#181276: marked as done (ITP: qsa-x11-free -- Cross-platform application-scripting toolkit based on Qt)

Your message dated Sat, 24 Nov 2007 11:59:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#216740: marked as done (ITP: paq -- PAQ archiver (better than 7zip compression))

Your message dated Sat, 24 Nov 2007 11:59:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#399844: marked as done (ITP: samba4wins -- a full featured replicating WINS server for UNIX)

Your message dated Sat, 24 Nov 2007 11:59:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#395403: marked as done (ITP: bist -- A chemical drawing tool)

Your message dated Sat, 24 Nov 2007 11:59:34 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#393753: marked as done (ITP: crossover-demo -- time-limited demo of CrossOver Office)

Your message dated Sat, 24 Nov 2007 11:59:34 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#338236: marked as done (ITP: natstat -- A traffic monitoring program)

Your message dated Sat, 24 Nov 2007 11:59:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#393309: marked as done (ITP: libtemplate-latex-perl -- LaTeX support for the perl Template Toolkit)

Your message dated Sat, 24 Nov 2007 11:59:34 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#395149: marked as done (ITP: wmaker-theme-debianswirl -- Debian Swirl theme for WindowMaker by Gary Burke.)

Your message dated Sat, 24 Nov 2007 11:59:34 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#367520: marked as done (RFP: nonpareil -- Simulator/emulator for most classic HP RPN calculators)

Your message dated Sat, 24 Nov 2007 11:59:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#391340: marked as done (RFP: pymedia -- python module for wav, mp3, ogg, avi, divx, dvd,, cdda etc files manipulation)

Your message dated Sat, 24 Nov 2007 11:59:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#293734: marked as done (RFP: roadmap -- Car navigation system with street maps using any standard GPS receiver)

Your message dated Sat, 24 Nov 2007 11:59:46 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#399756: marked as done (RFP: wordpress-mu -- framework for hosting large numbers of wordpress weblogs)

Your message dated Sat, 24 Nov 2007 11:59:49 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#399502: marked as done (ITP: nfs4-acl-tools -- commandline and GUI ACL utilities for the NFSv4 client)

Your message dated Sat, 24 Nov 2007 11:59:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#318601: marked as done (RFP: ceemedia -- Movie Catalog)

Your message dated Sat, 24 Nov 2007 11:59:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#391225: marked as done (ITP: konqburn -- Konqueror CD/DVD Burner Sidebar)

Your message dated Sat, 24 Nov 2007 11:59:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#399760: marked as done (ITP: paq -- high compression ratio archiver)

Your message dated Sat, 24 Nov 2007 11:59:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing 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#442731: marked as done (silc-toolkit: FTBFS if build twice in a row)

Your message dated Sat, 24 Nov 2007 20:47:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#442731: fixed in silc-toolkit 1.1.5-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 n

Bug#452693: marked as done (libapache-mod-php5 dependencies problems in lenny)

Your message dated Sat, 24 Nov 2007 15:58:10 -0600 with message-id <[EMAIL PROTECTED]> and subject line [php-maint] Bug#452693: libapache-mod-php5 dependencies problems in lenny has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with

Bug#384977: marked as done (gnuplot-mode: error seen)

Your message dated Sat, 24 Nov 2007 21:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#384977: fixed in gnuplot-mode 1:0.6.0-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

Bug#452671: marked as done (gst-plugins-good0.10: FTBFS: error: 'GST_TAG_MUSICBRAINZ_SORTNAME' was not declared in this scope)

Your message dated Sat, 24 Nov 2007 21:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#452671: fixed in gst-plugins-good0.10 0.10.6-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 cas

  1   2   >