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

Your message dated Fri, 28 Oct 2005 22:17:16 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#308750: fixed in tspc 2.1.1-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#332124: marked as done (tspc depends on debconf without | debconf-2.0 alternate; blocks cdebconf transition)

Your message dated Fri, 28 Oct 2005 22:17:16 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332124: fixed in tspc 2.1.1-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#331598: marked as done (tspc: [INTL:sv] Swedish debconf templates translation)

Your message dated Fri, 28 Oct 2005 22:17:16 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331598: fixed in tspc 2.1.1-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#332333: marked as done (bbclone: [INTL:sv] Swedish debconf templates translation)

Your message dated Fri, 28 Oct 2005 22:17:16 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332333: fixed in tspc 2.1.1-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#335095: marked as done (O: tspc -- Client to configure an IPv6 tunnel to freenet6)

Your message dated Fri, 28 Oct 2005 22:17:16 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335095: fixed in tspc 2.1.1-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#304431: marked as done (tspc_2.1.1-4(mips/unstable): FTBFS with -rsudo)

Your message dated Fri, 28 Oct 2005 22:17:16 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#304431: fixed in tspc 2.1.1-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#335706: marked as done (Upgrade fails, conflicting file in libopenssl-ruby)

Your message dated Fri, 28 Oct 2005 22:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335706: fixed in ruby1.8 1.8.3-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#329364: marked as done (ruby1.8_1.8.3-1(m68k/unstable/poseidon): FTBFS on m68k)

Your message dated Fri, 28 Oct 2005 22:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#329364: fixed in ruby1.8 1.8.3-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#269306: marked as done (wnck-applet: wnck-applet died and still dies if I try to reload applet)

Your message dated Sat, 29 Oct 2005 01:19:27 -0200 with message-id <[EMAIL PROTECTED]> and subject line should be closed since 2.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 respons

Bug#335976: marked as done (/etc/init.d/nvidia-kernel contains bashisms)

Your message dated Fri, 28 Oct 2005 20:02:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335976: fixed in nvidia-kernel-common 20051028+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 n

Bug#336229: marked as done (mysq-server: New Upstream Version 5.0)

Your message dated Sat, 29 Oct 2005 04:50:03 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#336229: mysq-server: New Upstream Version 5.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

Bug#253225: marked as done (gnome-panel: windowlist applet vanishes and re-appears consistently)

Your message dated Sat, 29 Oct 2005 00:58:56 -0200 with message-id <[EMAIL PROTECTED]> and subject line not gnome-panel's problem, it seems 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 you

Bug#335927: marked as done (FTBFS with libsmbclient-dev 3.0.20b-2)

Your message dated Sat, 29 Oct 2005 00:35:47 -0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in upload of gnome-vfs2 2.12.1.1-1 to 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 t

Bug#336218: marked as done (su should not ask root for a password)

Your message dated Sat, 29 Oct 2005 04:46:35 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#336218: su should not ask root for a password 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#335214: marked as done (gnome-vfs2: FTBFS: smb-method.c:1489: error: 'struct _SMBCCTX' has no member named 'close')

Your message dated Sat, 29 Oct 2005 00:35:47 -0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in upload of gnome-vfs2 2.12.1.1-1 to 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 t

Bug#332504: marked as done (debclean doesn't return to a cleaned state)

Your message dated Sat, 29 Oct 2005 00:39:02 -0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in upload of pango1.0 1.10.1-1 to 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 c

Bug#331279: marked as done (librsvg2: New upstream version available)

Your message dated Sat, 29 Oct 2005 00:42:39 -0200 with message-id <[EMAIL PROTECTED]> and subject line Processed: Fixed in upload of librsvg 2.12.7-1 to 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

Bug#321949: marked as done (gnome-panel: wnck-applet no longer brings windows to front)

Your message dated Sat, 29 Oct 2005 00:34:31 -0200 with message-id <[EMAIL PROTECTED]> and subject line Not gnome-panel's problem 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 responsi

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

Your message dated Sat, 29 Oct 2005 00:39:02 -0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in upload of pango1.0 1.10.1-1 to 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 c

Bug#315822: marked as done (librsvg2-bin: Cannot handle svg files unless they are in the current directory)

Your message dated Sat, 29 Oct 2005 00:42:39 -0200 with message-id <[EMAIL PROTECTED]> and subject line Processed: Fixed in upload of librsvg 2.12.7-1 to 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

Bug#315179: marked as done (yelp: man page out of date)

Your message dated Sat, 29 Oct 2005 00:33:17 -0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in upload of yelp 2.12.1-1 to 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

Bug#312615: marked as done (FTBFS on hurd-i386: Unsatisfiable Build-Depends on mozilla-dev)

Your message dated Sat, 29 Oct 2005 00:42:39 -0200 with message-id <[EMAIL PROTECTED]> and subject line Processed: Fixed in upload of librsvg 2.12.7-1 to 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

Bug#292286: marked as done (librsvg2-2: rsvg-filter.c doesnt #include "config.h")

Your message dated Sat, 29 Oct 2005 00:42:39 -0200 with message-id <[EMAIL PROTECTED]> and subject line Processed: Fixed in upload of librsvg 2.12.7-1 to 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

Bug#291079: marked as done (libwnck4: Taskbar should blink when "URGENT" hint is set)

Your message dated Sat, 29 Oct 2005 00:37:15 -0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in upload of libwnck 2.12.1-1 to 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 ca

Bug#287027: marked as done (yelp: Manpage should document command-line feature)

Your message dated Sat, 29 Oct 2005 00:33:17 -0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in upload of yelp 2.12.1-1 to 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

Bug#278750: marked as done (librsvg2-bin: rsvg program doesn't handle -h 0 or -w 0 well)

Your message dated Sat, 29 Oct 2005 00:42:39 -0200 with message-id <[EMAIL PROTECTED]> and subject line Processed: Fixed in upload of librsvg 2.12.7-1 to 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

Bug#313080: marked as done (Crash on startup with new 2.10 packages)

Your message dated Sat, 29 Oct 2005 00:28:20 -0200 with message-id <[EMAIL PROTECTED]> and subject line Not gnome-panel's problem 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 responsi

Bug#314979: marked as done (gnome-panel does not run on kernels 2.4.x)

Your message dated Sat, 29 Oct 2005 00:30:38 -0200 with message-id <[EMAIL PROTECTED]> and subject line Not gnome-panel's problem 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 responsi

Bug#283775: marked as done (Please tell the user the name of the applet)

Your message dated Sat, 29 Oct 2005 00:30:57 -0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in upload of gnome-netstatus 2.12.0-1 to 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 no

Bug#335968: marked as done (gramps: Segmentation fault)

Your message dated Fri, 28 Oct 2005 19:55:09 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#335968: gramps: Segmentation fault 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#333585: marked as done (postgresql-8.0: --auth=?? not documented)

Your message dated Fri, 28 Oct 2005 20:54:22 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#333585: postgresql-8.0: --auth=?? not documented 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 c

Bug#335387: marked as done (Perl, "use fcntl" reporting incorrect value for F_SETLKW)

Your message dated Sat, 29 Oct 2005 10:36:39 +1000 with message-id <[EMAIL PROTECTED]> and subject line Bug#335387: Perl, "use fcntl" reporting incorrect value for F_SETLKW 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#335983: marked as done (scm: FTBFS on m68k (error when including ))

Your message dated Fri, 28 Oct 2005 17:04:56 -0700 with message-id <[EMAIL PROTECTED]> and subject line not any more 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#325135: marked as done (maildrop: lockmail doesn't drop privileges (CAN-2005-2655))

Your message dated Sat, 29 Oct 2005 01:35:05 +0200 with message-id <[EMAIL PROTECTED]> and subject line Let version tracking deal with it 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#334036: marked as done (kst_1.1.0-2(hppa/unstable): FTBFS: gcc-4.0 workaround needed)

Your message dated Sat, 29 Oct 2005 01:03:56 +0200 with message-id <[EMAIL PROTECTED]> and subject line Already 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 re

Bug#335820: marked as done (gnubiff: README.Debian refers to non-existant "--gtk" option)

Your message dated Fri, 28 Oct 2005 15:47:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335820: fixed in gnubiff 2.1.6-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 yo

Bug#335193: marked as done (gnubiff: manual page should refer to info page)

Your message dated Fri, 28 Oct 2005 15:47:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335193: fixed in gnubiff 2.1.6-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 yo

Bug#321356: marked as done (please consider using FAM not libgamin0)

Your message dated Fri, 28 Oct 2005 15:47:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321356: fixed in gnubiff 2.1.6-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 yo

Bug#335088: marked as done (linux-patch-debian-2.6.12: dot in Description)

Your message dated Fri, 28 Oct 2005 15:00:48 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335088: fixed in linux-2.6 2.6.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

Bug#324583: marked as done (linux-patch-debian-2.6.12: missing default version numbers in unpatch/apply script break make-kpkg)

Your message dated Fri, 28 Oct 2005 15:00:48 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#324583: fixed in linux-2.6 2.6.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

Bug#275144: marked as done (sndobj: New upstream version available)

Your message dated Fri, 28 Oct 2005 15:01:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#275144: fixed in sndobj 2.6.1a-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 yo

Bug#282821: marked as done (sndobj: FTBFS: compiler error.)

Your message dated Fri, 28 Oct 2005 15:01:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#282821: fixed in sndobj 2.6.1a-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 yo

Bug#266713: marked as done (ISO code page named wrong in man page)

Your message dated Fri, 28 Oct 2005 14:47:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#266713: fixed in ncpfs 2.2.6-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#335584: marked as done (xmoto: Should link against debian pacakges of libs.)

Your message dated Fri, 28 Oct 2005 14:47:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335584: fixed in xmoto 0.1.7-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#334312: marked as done (ncpfs: Manpage for nwtrustee2)

Your message dated Fri, 28 Oct 2005 14:47:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334312: fixed in ncpfs 2.2.6-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#324939: marked as done (ncpfs: while we mount novell volumes in debian linux they are mounted in uppercase.)

Your message dated Sat, 29 Oct 2005 07:53:11 +1000 with message-id <[EMAIL PROTECTED]> and subject line Bug#324939: ncpfs: while we mount novell volumes in debian linux they are mounted in uppercase. has caused the attached Bug report to be marked as done. This means that you claim that the probl

Bug#257677: marked as done (ncpfs: Typo in ncpmount(8))

Your message dated Fri, 28 Oct 2005 14:47:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#257677: fixed in ncpfs 2.2.6-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#313956: marked as done (ncpfs: [INTL:de] German PO file corrections)

Your message dated Fri, 28 Oct 2005 14:47:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313956: fixed in ncpfs 2.2.6-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#336231: marked as done (svn: symbol lookup error; lib broken)

Your message dated Fri, 28 Oct 2005 13:52:37 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#336231: svn: symbol lookup error; lib broken 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#335094: marked as done (openoffice.org: Some options in the PPD file cannot be accessed)

Your message dated Fri, 28 Oct 2005 16:55:24 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#335094: openoffice.org: Some options in the PPD file cannot be accessed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wi

Bug#336051: marked as done (Still cannot load correctly...)

Your message dated Fri, 28 Oct 2005 13:47:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#336051: fixed in araneida 0.9-a3-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#333094: marked as done (iso-codes: [INTL:th] Thai translation updates for iso 639)

Your message dated Fri, 28 Oct 2005 13:48:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#333094: fixed in iso-codes 0.49-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 y

Bug#335975: marked as done (iso-codes package fails to build on FC4)

Your message dated Fri, 28 Oct 2005 13:48:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335975: fixed in iso-codes 0.49-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 y

Bug#335234: marked as done (New Kurdish translation for iso-codes_iso_3166)

Your message dated Fri, 28 Oct 2005 13:48:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335234: fixed in iso-codes 0.49-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 y

Bug#334744: marked as done (wrong list of files in /usr/share/iso-codes/ in README)

Your message dated Fri, 28 Oct 2005 13:48:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334744: fixed in iso-codes 0.49-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 y

Bug#329548: marked as done (php4: ext/informix fails to link $INFORMIXDIR/lib/esql/checkapi.o)

Your message dated Fri, 28 Oct 2005 13:48:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#329548: fixed in iso-codes 0.49-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 y

Bug#333076: marked as done (iso-codes: [INTL:th] Thai tranlation for iso 4217)

Your message dated Fri, 28 Oct 2005 13:48:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#333076: fixed in iso-codes 0.49-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 y

Bug#331357: marked as done (Allow iso-codes to build without pyxml)

Your message dated Fri, 28 Oct 2005 13:48:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331357: fixed in iso-codes 0.49-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 y

Bug#326523: marked as done (gengetopt(GNU/k*BSD): FTBFS: out of date config.sub/config.guess)

Your message dated Fri, 28 Oct 2005 13:47:44 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326523: fixed in gengetopt 2.10-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#331071: marked as done (iso-codes: Typos in iso_3166_2)

Your message dated Fri, 28 Oct 2005 13:48:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331071: fixed in iso-codes 0.49-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 y

Bug#328209: marked as done (util-vserver: built with wrong vserver syscall)

Your message dated Fri, 28 Oct 2005 13:49:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#328209: fixed in util-vserver 0.30.208-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 i

Bug#323888: marked as done (util-vserver: Enable builds on arm and hppa)

Your message dated Fri, 28 Oct 2005 13:49:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323888: fixed in util-vserver 0.30.208-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 i

Bug#328152: marked as done (iso-codes_0.47.orig.tar.gz fails the build of Gnome 2.12 on FC4)

Your message dated Fri, 28 Oct 2005 13:48:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#328152: fixed in iso-codes 0.49-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 y

Bug#268595: marked as done (gengetopt: Build-Depends on build-essential libstdc++-dev)

Your message dated Fri, 28 Oct 2005 13:47:44 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#268595: fixed in gengetopt 2.10-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#325276: marked as done (iso-codes: For future reference: upcoming ISO 639-3 standard)

Your message dated Fri, 28 Oct 2005 13:48:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325276: fixed in iso-codes 0.49-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 y

Bug#331215: marked as done (moinmoin-common has a missing dependency)

Your message dated Fri, 28 Oct 2005 22:42:05 +0200 with message-id <[EMAIL PROTECTED]> and subject line close bug #331215 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 t

Bug#336028: marked as done (emacs-snapshot: diary not working.)

Your message dated Fri, 28 Oct 2005 22:44:16 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#336028: emacs-snapshot: diary not working. 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#335974: marked as done (dh-lisp: provide a way to require a specific common-lisp-controller version)

Your message dated Fri, 28 Oct 2005 13:47:34 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335974: fixed in dh-lisp 0.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 r

Bug#202954: marked as done (vserver: mount --bind: permission denid)

Your message dated Fri, 28 Oct 2005 21:34:34 +0200 with message-id <[EMAIL PROTECTED]> and subject line This is fixed in sarge 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 responsibil

Bug#334780: marked as done (debian-installer_20051018(mipsel/unstable): missing build-depends)

Your message dated Fri, 28 Oct 2005 12:03:01 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334780: fixed in debian-installer 20051026 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

Processed: closing 264977

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.8 > close 264977 1.0.18-1 Bug#264977: libpng2-dev - minor inconvenience 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.0.18-1, se

Processed: closing 320183

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.8 > close 320183 0.10.12 Bug#320183: ethereal: Multiple security issues in various dissectors 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug#320192: ethereal:

Bug#327136: marked as done (jwm: installs alternative link in $PWD instead of /usr/bin)

Your message dated Fri, 28 Oct 2005 20:05:14 +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 reo

Bug#299520: marked as done (gnome-panel uses 100% cpu)

Your message dated Fri, 28 Oct 2005 14:58:36 -0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#299520: still able to reproduce? 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#336166: marked as done (awstats.pl does not take the server timezone into account)

Your message dated Sat, 29 Oct 2005 00:03:28 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#336166: awstats.pl does not take the server timezone into account 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#334606: marked as done (snort: Remote buffer overflow in the 'bo' preprocessor)

Your message dated Fri, 28 Oct 2005 18:03:49 +0200 with message-id <[EMAIL PROTECTED]> and subject line snort: Remote buffer overflow in the 'bo' preprocessor 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#330638: marked as done (llvm: Compiled with wrong version of g++ on i386)

Your message dated Fri, 28 Oct 2005 17:45:44 +0200 with message-id <[EMAIL PROTECTED]> and subject line binNMU done 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 reop

Bug#333024: marked as done (gco: FTBFS: versioned build-dep on virtual package gdk-imlib1-dev)

Your message dated Fri, 28 Oct 2005 17:26:04 +0200 with message-id <[EMAIL PROTECTED]> and subject line Already 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 re

Bug#292008: marked as done (zope-psycopgda: Problem with the icons in the browse tab)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#292008: fixed in psycopg 1.1.21-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 y

Bug#327415: marked as done (fails to install)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#327415: fixed in psycopg 1.1.21-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 y

Bug#268975: marked as done (zope-psycopgda: *.pyo files not deleted on uninstallation)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#268975: fixed in psycopg 1.1.21-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 y

Bug#333639: marked as done (psycopg FTBFS on sid)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#333639: fixed in psycopg 1.1.21-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 y

Bug#333638: marked as done (psycopg FTBFS on sid)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#333638: fixed in psycopg 1.1.21-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 y

Bug#336170: marked as done (zope3-sandbox instance fails to start)

Your message dated Fri, 28 Oct 2005 17:05:26 +0200 with message-id <[EMAIL PROTECTED]> and subject line [Pkg-zope-developers] Bug#336170: zope3-sandbox instance fails to start has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#329115: marked as done (python2.4-psycopg: site-packages in the deb is bogus)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#329115: fixed in psycopg 1.1.21-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 y

Bug#321592: marked as done (psycopg: 1.1.19 breaks date/time conversion)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321592: fixed in psycopg 1.1.21-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 y

Bug#325796: marked as done (xscreensaver: Never blanks with multi-head non Xinerama setup)

Your message dated Fri, 28 Oct 2005 17:13:25 +0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in 4.23 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 re

Bug#323599: marked as done (zope2.7-psycopgda: fails to install)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323599: fixed in psycopg 1.1.21-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 y

Bug#305392: marked as done (corrupt images in examples/)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#305392: fixed in psycopg 1.1.21-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 y

Bug#332306: marked as done (xscreensaver: Should not output host lookup failures and so on)

Your message dated Fri, 28 Oct 2005 17:14:21 +0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in 4.23 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 re

Bug#158669: marked as done (Zope should be restarted after the installation of this package)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#158669: fixed in psycopg 1.1.21-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 y

Bug#328407: marked as done (xscreensaver: new version 4.22 available)

Your message dated Fri, 28 Oct 2005 17:15:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in 4.23 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 re

Bug#320618: marked as done (Wrong libc6 dependency on unstable)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320618: fixed in psycopg 1.1.21-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 y

Bug#319509: marked as done (python2.4-psycopg: fails to be installed by apt-get/dpkg)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319509: fixed in psycopg 1.1.21-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 y

Bug#292247: marked as done (please integrate with Zope 2.7)

Your message dated Fri, 28 Oct 2005 08:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#292247: fixed in psycopg 1.1.21-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 y

Bug#307053: marked as done (/usr/bin/xscreensaver-text: xscreensaver-text does not handle rss feeds)

Your message dated Fri, 28 Oct 2005 17:12:21 +0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in 4.23 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 re

Bug#335383: marked as done (vpnc-connect does not find configfile)

Your message dated Fri, 28 Oct 2005 07:47:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335383: fixed in vpnc 0.3.3+SVN20051028-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#335518: marked as done (vpnc: route problem in latest version "an inet prefix is expected rather than "")

Your message dated Fri, 28 Oct 2005 07:47:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335518: fixed in vpnc 0.3.3+SVN20051028-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#334203: marked as done (vpnc 0.3.3 route troubles)

Your message dated Fri, 28 Oct 2005 07:47:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334203: fixed in vpnc 0.3.3+SVN20051028-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#335989: marked as done (Bashisms in vpnc-connect script)

Your message dated Fri, 28 Oct 2005 07:47:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335989: fixed in vpnc 0.3.3+SVN20051028-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

  1   2   >