Bug#296475: marked as done (/usr/share/sendmail/dynamic and multiple interfaces ub DAEMON_NETIF)

Your message dated Tue, 22 Feb 2005 17:47:21 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296475: fixed in sendmail 8.13.3-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#296491: marked as done (Sendmail blocks valid networks)

Your message dated Tue, 22 Feb 2005 17:47:21 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296491: fixed in sendmail 8.13.3-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#292709: marked as done (gok-doc: does not install any doc)

Your message dated Tue, 22 Feb 2005 18:02:21 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#292709: fixed in gok 1.0.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 your

Bug#285433: marked as done (cvsreport: Wrong installation instructions in README)

Your message dated Tue, 22 Feb 2005 18:02:03 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#285433: fixed in cvsreport 0.3.5.cvs.20050222-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt

Bug#63226: marked as done (wu-ftpd: User logins only work when wu-ftpd is configured with anonymous ftp)

Your message dated Tue, 22 Feb 2005 23:22:31 + with message-id [EMAIL PROTECTED] and subject line Cleaning up has caused the attached 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#51642: marked as done (wu-ftpd-academ gets `stuck')

Your message dated Tue, 22 Feb 2005 23:22:31 + with message-id [EMAIL PROTECTED] and subject line Cleaning up has caused the attached 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#58702: marked as done (wu-ftpd: unprintable chars in syslog)

Your message dated Tue, 22 Feb 2005 23:22:31 + with message-id [EMAIL PROTECTED] and subject line Cleaning up has caused the attached 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#25180: marked as done (wu-ftpd-academ: getpeername (ftpd): Socket operation on non-socket)

Your message dated Tue, 22 Feb 2005 23:27:45 + with message-id [EMAIL PROTECTED] and subject line Cleaning up has caused the attached 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#63224: marked as done (wu-ftpd: User logins only work when wu-ftpd is configured with anonymous ftp)

Your message dated Tue, 22 Feb 2005 23:22:31 + with message-id [EMAIL PROTECTED] and subject line Cleaning up has caused the attached 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#83385: marked as done (Can't log into the ftp server)

Your message dated Tue, 22 Feb 2005 23:22:31 + with message-id [EMAIL PROTECTED] and subject line Cleaning up has caused the attached 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#8663: marked as done (wu-ftpd: doesn't work with old NCSA DOS FTP client)

Your message dated Tue, 22 Feb 2005 23:22:31 + with message-id [EMAIL PROTECTED] and subject line Cleaning up has caused the attached 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#291314: marked as done (cxref: broken cxref-cpp wrapper)

Your message dated Tue, 22 Feb 2005 18:47:13 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#291314: fixed in cxref 1.6-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 your

Bug#281991: marked as done (cxref: inappropriate use of debconf)

Your message dated Tue, 22 Feb 2005 18:47:13 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#281991: fixed in cxref 1.6-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 your

Bug#283635: marked as done (cxref: Please switch to gettext-based debconf templates)

Your message dated Tue, 22 Feb 2005 18:47:13 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#283635: fixed in cxref 1.6-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 your

Bug#285676: marked as done (cxref-doc: error in doc-base file)

Your message dated Tue, 22 Feb 2005 18:47:13 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#285676: fixed in cxref 1.6-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 your

Bug#286410: marked as done (dangling symlink due to splitting of cxref-doc)

Your message dated Tue, 22 Feb 2005 18:47:13 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#286410: fixed in cxref 1.6-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 your

Bug#289081: marked as done (zsh: completion for wajig)

Your message dated Tue, 22 Feb 2005 19:13:34 -0500 with message-id [EMAIL PROTECTED] and subject line wajig completion has caused the attached 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#231787: marked as done (xkeycaps menu won't scroll up)

Your message dated Wed, 23 Feb 2005 01:03:51 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#231787: xkeycaps menu won't scroll up has caused the attached 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#294626: marked as done (apt-proxy: 1.9.25 broken with python2.3 upgrade (missing profile))

Your message dated Tue, 22 Feb 2005 19:17:21 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#294626: fixed in apt-proxy 1.9.26 has caused the attached 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#296501: marked as done (mime-support: Copious unnecessary output on upgrade)

Your message dated Tue, 22 Feb 2005 19:18:13 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296501: fixed in mime-support 3.31-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#215492: marked as done (gaim: breaks libao2)

Your message dated Tue, 22 Feb 2005 19:29:04 -0500 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#289755: marked as done (gimp: should use libcurl rather than wget)

Your message dated Tue, 22 Feb 2005 19:23:23 -0500 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#284423: marked as done (/sbin/dhclient3: manual page too far away)

Your message dated Tue, 22 Feb 2005 19:17:21 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#284423: fixed in apt-proxy 1.9.26 has caused the attached 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#208846: marked as done (gaim: random crash)

Your message dated Tue, 22 Feb 2005 19:33:46 -0500 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#245781: marked as done (Any chance of a gaim-vv package?)

Your message dated Tue, 22 Feb 2005 19:48:01 -0500 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#296395: marked as done (gmailfs: No Module Named Profile)

Your message dated Tue, 22 Feb 2005 20:02:41 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296395: fixed in gmailfs 0.3-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#282204: marked as done (gmailfs: uninstallable in sid)

Your message dated Tue, 22 Feb 2005 20:02:41 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#282204: fixed in gmailfs 0.3-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#292199: marked as done (gimp: Unsharp mask does not work for larger images)

Your message dated Tue, 22 Feb 2005 20:02:26 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#292199: fixed in gimp 2.2.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#295870: marked as done (gimp: Bad french translation for the quit dialog box)

Your message dated Tue, 22 Feb 2005 20:02:26 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#295870: fixed in gimp 2.2.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#295973: marked as done ('toilet paper' image template option displayed twice)

Your message dated Tue, 22 Feb 2005 20:02:26 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#295973: fixed in gimp 2.2.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#183268: marked as done (libtiff3g: Some tiff files show up scrambled.)

Your message dated Tue, 22 Feb 2005 20:18:36 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#183268: fixed in tiff 3.7.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

Bug#295748: marked as done (gaim: Crash on spelling error)

Your message dated Tue, 22 Feb 2005 20:47:15 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#295748: fixed in aspell 0.60.2+20050121-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#296397: marked as done (Unhandled Error: The method clear is unimplemented in WritableDict.)

Your message dated Tue, 22 Feb 2005 20:47:15 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#295748: fixed in aspell 0.60.2+20050121-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#296504: marked as done (Please configure apache via conf.d)

Your message dated Tue, 22 Feb 2005 21:04:06 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296504: fixed in phppgadmin 3.5.2-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#284003: marked as done (postfix: double dependency on debconf)

Your message dated Tue, 22 Feb 2005 20:21:45 -0700 with message-id [EMAIL PROTECTED] and subject line Fixed in 2.1.5-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 to

Bug#281214: marked as done (postfix: debconf templates)

Your message dated Tue, 22 Feb 2005 20:21:45 -0700 with message-id [EMAIL PROTECTED] and subject line Fixed in 2.1.5-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 to

Bug#283165: marked as done (l10n: Update of po-debconf spanish translation)

Your message dated Tue, 22 Feb 2005 20:21:45 -0700 with message-id [EMAIL PROTECTED] and subject line Fixed in 2.1.5-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 to

Bug#265371: marked as done (postfix: double depends on debconf)

Your message dated Tue, 22 Feb 2005 20:21:45 -0700 with message-id [EMAIL PROTECTED] and subject line Fixed in 2.1.5-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 to

Bug#287276: marked as done (libatomic-ops: Support for amd64.)

Your message dated Tue, 22 Feb 2005 22:32:16 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#287276: fixed in libatomic-ops 0.5.1-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#296525: marked as done (/etc/network/ip-{up,down}.d/postfix should be /etc/network/if-{up,down}.d/postfix)

Your message dated Tue, 22 Feb 2005 22:47:07 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296525: fixed in postfix 2.1.5-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#295165: marked as done (lilo-installer: postinst fails at debconf priority=critical)

Your message dated Wed, 23 Feb 2005 00:02:04 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#295165: fixed in lilo-installer 1.07 has caused the attached 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#296062: marked as done (smbldap-tools: Incorrect config file paths in smbldap_tools.pm)

Your message dated Wed, 23 Feb 2005 06:28:22 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#296062: Bug has been fixed in 0.8.7-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#294677: marked as done (mozilla-firefox: unable to print (XML parsing error))

Your message dated Wed, 23 Feb 2005 01:16:03 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#294677: mozilla-firefox: unable to print (XML parsing error) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#262358: marked as done (mpich: mpiCC doesn't specify include directory missing mpi++.h file)

Your message dated Wed, 23 Feb 2005 01:25:18 -0500 with message-id [EMAIL PROTECTED] and subject line Fixed in 1.2.5.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 your responsibility

Bug#244772: marked as done (petsc2.1.6-dev: libpetscfortran.a linking problem with mpich)

Your message dated Wed, 23 Feb 2005 01:25:18 -0500 with message-id [EMAIL PROTECTED] and subject line Fixed in 1.2.5.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 your responsibility

Bug#290397: marked as done (mpich: mpiCC fails entirely when run under automake)

Your message dated Wed, 23 Feb 2005 01:25:18 -0500 with message-id [EMAIL PROTECTED] and subject line Fixed in 1.2.5.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 your responsibility

Bug#292761: marked as done (/usr/bin/mpereconfig.mpich: broken symlink)

Your message dated Wed, 23 Feb 2005 01:25:18 -0500 with message-id [EMAIL PROTECTED] and subject line Fixed in 1.2.5.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 your responsibility

Bug#296061: marked as done (mpich: FTBFS: rmdir: `debian/mpich-bin/usr/lib/mpich/share/upshot/sbin': No such file or directory)

Your message dated Wed, 23 Feb 2005 01:47:08 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296061: fixed in mpich 1.2.5.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

Bug#288742: marked as done (attal: Please make debian packages of new, improved upstream version - 0.9.2)

Your message dated Tue, 22 Feb 2005 03:17:14 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#288742: fixed in attal 0.9.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#292614: marked as done (gpx2shp: Segfaults when called only with -v)

Your message dated Tue, 22 Feb 2005 03:17:43 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#292614: fixed in gpx2shp 0.69-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#295645: marked as done (Grub makes bad decisions and fstab not populated)

Your message dated Tue, 22 Feb 2005 10:16:25 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#295645: Grub makes bad decisions and fstab not populated has caused 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#296380: marked as done (udev doesn't create sg* under /dev)

Your message dated Tue, 22 Feb 2005 10:33:23 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#296380: udev doesn't create sg* under /dev has caused the attached 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#296379: marked as done (My system became unusable)

Your message dated Tue, 22 Feb 2005 10:32:04 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#296379: My system became unusable has caused the attached 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#296303: marked as done (New version 0.12 available)

Your message dated Tue, 22 Feb 2005 05:03:05 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296303: fixed in mma 0.12-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#293562: marked as done (octave2.1-doc: Provide a pdf version)

Your message dated Tue, 22 Feb 2005 05:47:05 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#293562: fixed in octave2.1 2.1.65-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#292917: marked as done (needs to depend on f2c on m68k?)

Your message dated Tue, 22 Feb 2005 05:47:05 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#292917: fixed in octave2.1 2.1.65-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#294891: marked as done (kernel-source-2.6.10: fails to build)

Your message dated Tue, 22 Feb 2005 19:11:44 +0900 with message-id [EMAIL PROTECTED] and subject line Bug#294891: kernel-source-2.6.10: fails to build has caused the attached 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#287627: marked as done ()

Your message dated Tue, 22 Feb 2005 12:15:34 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#287627: has caused the attached 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#295881: marked as done (Kerberos authentication fails)

Your message dated Tue, 22 Feb 2005 07:41:13 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#295881: Kerberos authentication fails has caused the attached 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

Processed: closing 160957

Processing commands for [EMAIL PROTECTED]: # I dont know why this bug is open again, it has been in the archive for a long time close 160957 Bug#160957: [U-A] man-db: dangling symlink 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug#162510: [U-A] exuberant-ctags:

Bug#295820: marked as done (Check doc-base file is wrong)

Your message dated Tue, 22 Feb 2005 14:19:54 +0100 with message-id [EMAIL PROTECTED] and subject line no doc-base no 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

Bug#295871: marked as done (aspell-pl: FTBFS: Missing build dependency.)

Your message dated Tue, 22 Feb 2005 09:17:08 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#295871: fixed in aspell-pl 20050222-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#222306: marked as done (Low Memory Problem)

Your message dated Tue, 22 Feb 2005 15:59:29 +0100 with message-id [EMAIL PROTECTED] and subject line Low Memory 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 responsibility

Bug#282112: marked as done (squirrelmail: fails to read contents of a particular folder (imap FETCH string created wrongly))

Your message dated Tue, 22 Feb 2005 15:52:46 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#282112: squirrelmail: fails to read contents of a particular folder(imap FETCH string created wrongly) has caused the attached Bug report to be marked as done. This means that you claim that

Bug#296305: marked as done (dictionaries-common: [INTL:gl] Galician translations of configuration screens (debconf))

Your message dated Tue, 22 Feb 2005 10:32:03 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296305: fixed in dictionaries-common 0.24.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

Bug#294862: marked as done (fails to upgrade)

Your message dated Tue, 22 Feb 2005 16:09:19 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line pgsql was not running has caused the attached 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#296270: marked as done (xblast-tnt-images: should depend on xblast-tnt)

Your message dated Tue, 22 Feb 2005 16:42:35 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#296270: xblast-tnt-images: should depend on xblast-tnt has caused the 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#256208: marked as done (grass: r.in.bin segfaults)

Your message dated Tue, 22 Feb 2005 11:01:10 -0500 with message-id [EMAIL PROTECTED] and subject line Bug #256208: grass: r.in.bin segfaults has caused the attached 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#296437: marked as done (permissions.d/udev.permissions is ignored)

Your message dated Tue, 22 Feb 2005 18:28:14 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#296437: permissions.d/udev.permissions is ignored has caused the attached 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#283731: marked as done (negative LDA in BLAS)

Your message dated 22 Feb 2005 12:25:16 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#283731: negative LDA in BLAS has caused the attached 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#296264: marked as done (kbd-chooser: installs incorrect keymap for Ukrainian)

Your message dated Tue, 22 Feb 2005 12:17:23 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296264: fixed in kbd-chooser 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 now

Bug#261483: marked as done (grass: Please consider GRASS 5.3 for Sarge)

Your message dated Tue, 22 Feb 2005 18:55:27 +0100 with message-id [EMAIL PROTECTED] and subject line Closing since 5.7 is going in has caused the attached 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#296063: marked as done (gimp: refuses to save XPM)

Your message dated Tue, 22 Feb 2005 12:52:05 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296063: gimp: refuses to save XPM has caused the attached 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#296434: marked as done (capplets: Default keyboard layout defined in XF86Config-4 not honored)

Your message dated Tue, 22 Feb 2005 19:15:12 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#296434: capplets: Default keyboard layout defined in XF86Config-4 not honored has caused the attached Bug report to be marked as done. This means that you claim that the problem has been

Bug#289986: marked as done (xfce: FTBFS (amd64/gcc-4.0): static declaration of '_XA_WIN_STATE' follows non-static declaration)

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#252332: marked as done (Nautilus and XFCE)

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#255289: marked as done (xfce: needs xinit)

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#240978: marked as done (xfce: needs gdm session update)

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#201193: marked as done (xfce: xscreensaver unknown option)

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#191653: marked as done (xfce requires to run xfce_setup after installation)

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#176382: marked as done (wrong assumption on char signedness)

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#179188: marked as done (xfwm shows UTF-8 chars with latin1 font, though iso10646 fonts is selected)

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#149338: marked as done (xfce crashes system on Fujitsu Lifebook completely (hard reset required))

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#184320: marked as done (At start time xfce requres file gtk-config)

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#191652: marked as done (xfce opens panel out of screen)

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#214459: marked as done (xfsamba cannot find masterbrowser)

Your message dated Tue, 22 Feb 2005 18:18:00 + with message-id [EMAIL PROTECTED] and subject line No follow ups and xfce removed now. has caused the attached 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#296449: marked as done (logcheck-database: sasl / sql ignore rules for postfix)

Your message dated Tue, 22 Feb 2005 18:36:32 + with message-id [EMAIL PROTECTED] and subject line Bug#296449: logcheck-database: sasl / sql ignore rules for postfix 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#293726: marked as done (pnet: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment)

Your message dated Tue, 22 Feb 2005 14:02:37 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#293726: fixed in pnet 0.6.12-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#255802: marked as done (spiralsynthmodular: ladspa plugin crashes ssm)

Your message dated Tue, 22 Feb 2005 19:44:47 + with message-id [EMAIL PROTECTED] and subject line Cleaning up has caused the attached 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#260429: marked as done (libcgicc1-dev: fails to check %xx codes before decoding form arguments)

Your message dated Tue, 22 Feb 2005 14:47:15 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#260429: fixed in libcgicc 3.2.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#185553: marked as done (/usr/X11R6/lib/libXft.so.2: undefined symbol: FcPatternVaBuild)

Your message dated Tue, 22 Feb 2005 20:00:32 + with message-id [EMAIL PROTECTED] and subject line Cleaning Up has caused the attached 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#293515: marked as done (xchm: Translation error)

Your message dated Tue, 22 Feb 2005 20:49:20 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed since .0.9.7-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#296480: marked as done (java-package: misparses directory names with spaces)

Your message dated Tue, 22 Feb 2005 21:45:34 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#296480: java-package: misparses directory names with spaces has caused 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#296342: marked as done (horde2.conf should include ifmodule php5)

Your message dated Tue, 22 Feb 2005 15:47:32 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296342: fixed in horde2 2.2.7-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 your

Bug#283260: marked as done (should support locale el)

Your message dated Tue, 22 Feb 2005 22:02:25 +0100 with message-id [EMAIL PROTECTED] and subject line Language supports need translator to provide translated text has caused 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#241302: marked as done (xchm: fonts not displayed)

Your message dated Tue, 22 Feb 2005 15:48:35 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#241302: fixed in xchm 0.9.8-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#293380: marked as done (symlinks from /var/lib/xmail to /etc/xmail replaced by real files)

Your message dated Tue, 22 Feb 2005 15:48:41 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#293380: fixed in xmail 1.21-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#275011: marked as done ([l10n:de] German debconf translation)

Your message dated Tue, 22 Feb 2005 15:47:39 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#275011: fixed in mailreader 2.3.29-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

Bug#284780: marked as done (acl2: :system dir is wrong)

Your message dated Tue, 22 Feb 2005 15:47:28 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#284780: fixed in acl2 2.9.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#286240: marked as done (debiandoc-sgml: Please add support for Arabic)

Your message dated Tue, 22 Feb 2005 22:02:25 +0100 with message-id [EMAIL PROTECTED] and subject line Language supports need translator to provide translated text has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

  1   2   >