Bug#192943: marked as done (ipac-ng: -e reconfigure is not documented in the manpage)

Your message dated Mon, 16 Apr 2007 08:40:54 +0200 with message-id <[EMAIL PROTECTED]> and subject line Option is gone from upstream code has caused the attached Bug report to be 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#410385: marked as done (ipw3945 driver fails to detect IPW3945 card in Dell D520)

Your message dated Mon, 16 Apr 2007 08:24:39 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#410385: ipw3945 driver fails to detect IPW3945 card in Dell D520 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#419385: marked as done (Removal of beep-media-player)

Your message dated Mon, 16 Apr 2007 06:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419385: fixed in xmms-crossfade 0.3.12-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 i

Bug#414882: marked as done (zoneminder: syntax error in postinstall)

Your message dated Mon, 16 Apr 2007 05:17:10 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414882: fixed in zoneminder 1.22.3-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 no

Bug#419054: marked as done (numactl doesnt include migratepages)

Your message dated Mon, 16 Apr 2007 05:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419054: fixed in numactl 0.9.11-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 y

Bug#419240: marked as done (rocksndiamonds: [INTL:es] Spanish po-debconf translation)

Your message dated Mon, 16 Apr 2007 04:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419240: fixed in rocksndiamonds 3.2.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

Bug#418765: marked as done (mono-common: Dependency on binfmt-support)

Your message dated Mon, 16 Apr 2007 03:02:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#418765: fixed in mono 1.2.3.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 you

Bug#412970: marked as done (too lax depends/missing conflicts?)

Your message dated Mon, 16 Apr 2007 03:02:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412970: fixed in mono 1.2.3.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 you

Bug#416360: marked as done (gnus-pers.el: gnus-functionp is absent in Oort Gnus)

Your message dated Mon, 16 Apr 2007 01:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#416360: fixed in emacs-goodies-el 26.10-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#416218: marked as done (dpkg-dev-el: native package changelog coding system for emacs 22)

Your message dated Mon, 16 Apr 2007 01:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#416218: fixed in emacs-goodies-el 26.10-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#392274: marked as done (dpkg-dev-el: [debian-bts-control] typo in debian-bts-control-modes-to-reuse)

Your message dated Mon, 16 Apr 2007 01:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#392274: fixed in emacs-goodies-el 26.10-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#352957: marked as done (debian-changelog-mode to support co-maintenance?)

Your message dated Mon, 16 Apr 2007 01:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#352957: fixed in emacs-goodies-el 26.10-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#402580: marked as done (emacs-goodies-el: xrdb-mode clobbers bindings in emacs-snapshot)

Your message dated Mon, 16 Apr 2007 01:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#402580: fixed in emacs-goodies-el 26.10-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#417882: marked as done (debian-bug.el: release-notes missing from list of pseudo-packages)

Your message dated Mon, 16 Apr 2007 01:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#417882: fixed in emacs-goodies-el 26.10-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#392719: marked as done (apache-mode.el: add apache2.conf to auto-mode-alist)

Your message dated Mon, 16 Apr 2007 01:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#392719: fixed in emacs-goodies-el 26.10-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#408285: marked as done (emacs-goodies-el: Too many files put into cfengine-mode)

Your message dated Mon, 16 Apr 2007 01:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#408285: fixed in emacs-goodies-el 26.10-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#388471: marked as done (gstreamer0.10-ffmpeg: No longer plays .flv files)

Your message dated Mon, 16 Apr 2007 01:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#388471: fixed in gstreamer0.10-ffmpeg 0.10.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 cas

Bug#388479: marked as done (gstreamer0.10-ffmpeg: Update ffmpeg for WMV9 support)

Your message dated Mon, 16 Apr 2007 01:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#388479: fixed in gstreamer0.10-ffmpeg 0.10.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 cas

Bug#389904: marked as done (gstreamer0.10-ffmpeg: Package web page misleading -- ffmpeg encoders are disabled)

Your message dated Mon, 16 Apr 2007 01:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#389904: fixed in gstreamer0.10-ffmpeg 0.10.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 cas

Bug#372278: marked as done (xserver-xorg-input-all: using clipboard with >8 bits characters doesn't work)

Your message dated Mon, 16 Apr 2007 02:11:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#372278: xserver-xorg-input-all: using clipboard with >8 bits characters doesn't work has caused the attached Bug report to be marked as done. This means that you claim that the problem has

Bug#419481: marked as done (libc6 fails to upgrade on AMD64 X2)

Your message dated Mon, 16 Apr 2007 01:57:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#419481: libc6 fails to upgrade on AMD64 X2 has caused the attached Bug report 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#415870: marked as done (nscd -i hosts causes main nscd daemon to segfault)

Your message dated Mon, 16 Apr 2007 01:50:42 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#415870: nscd -i hosts causes main nscd daemon to segfault has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Oops, wrong bug was closed in 2.9.10-4

Processing commands for [EMAIL PROTECTED]: > reopen 418503 Bug#418503: octave2.9: Must not enter testing 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Bug reopened, originator not changed. > close 415780 2.9.10-4 Bug

Bug#419480: marked as done (locales: bad dependency; uninstallable)

Your message dated Mon, 16 Apr 2007 01:38:41 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#419480: locales: bad dependency; uninstallable has caused the attached 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#264887: marked as done (GLOB_APPEND ignored by glob() in at least one place)

Your message dated Mon, 16 Apr 2007 01:32:44 +0200 (CEST) with message-id <[EMAIL PROTECTED]> and subject line no news from submitter has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your resp

Bug#160683: marked as done (date: long timezone offset sighlently changed)

Your message dated Mon, 16 Apr 2007 01:34:39 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#160683: date: long timezone offset sighlently changed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: closing 133971

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.2 > close 133971 Bug#133971: -W gives warnings in the glibc headers 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to J

Bug#362637: marked as done (xorg-dev: Spelling mistake in package description)

Your message dated Mon, 16 Apr 2007 01:30:20 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#362637: xorg-dev: Spelling mistake in package description has caused 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#419186: marked as done (apt-listbugs: Prompt breaks/repeats with non [Y/n] response)

Your message dated Sun, 15 Apr 2007 23:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419186: fixed in apt-listbugs 0.0.75 has caused the attached Bug report to 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#380752: marked as done (usplash: Make it possible to use the default font in external themes)

Your message dated Mon, 16 Apr 2007 01:14:52 +0200 with message-id <[EMAIL PROTECTED]> and subject line External fonts in usplash themes has caused the attached Bug report to be 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#403041: marked as done (breaks crypto setup)

Your message dated Mon, 16 Apr 2007 01:12:28 +0200 with message-id <[EMAIL PROTECTED]> and subject line please prompt for crypto passphrase has caused the attached Bug report to be 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#403040: marked as done (please prompt for crypto passphrase)

Your message dated Mon, 16 Apr 2007 01:11:41 +0200 with message-id <[EMAIL PROTECTED]> and subject line please prompt for crypto passphrase has caused the attached Bug report to be 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#419237: marked as done (cweb-latex is not installable)

Your message dated Sun, 15 Apr 2007 23:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419237: fixed in cweb-latex 1.1.1-15 has caused the attached Bug report to 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#400246: marked as done (octave2.9-headers: /usr/include/octave alternative symlink seems wrong)

Your message dated Sun, 15 Apr 2007 23:02:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400246: fixed in octave2.9 2.9.10-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#417671: marked as done (octave2.9: Reshape matrix bug)

Your message dated Sun, 15 Apr 2007 23:02:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#417671: fixed in octave2.9 2.9.10-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#418503: marked as done (octave2.9: Must not enter testing)

Your message dated Sun, 15 Apr 2007 23:02:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#418503: fixed in octave2.9 2.9.10-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#404834: marked as done (linux-image-2.6.18-3-sparc64: Kernel unaligned access kills at least sshfs (and may make USB unreliable))

Your message dated Mon, 16 Apr 2007 00:29:44 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#404834: linux-image-2.6.18-3-sparc64: Kernel unaligned access kills at least sshfs (and may make USB unreliable) has caused the attached Bug report to be marked as done. This means that you

Bug#403468: marked as done (epix1: please adapt for texlive)

Your message dated Sun, 15 Apr 2007 22:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403468: fixed in epix1 1.0.24-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 you

Bug#417530: marked as done (Fatal error: "epoll_create: Function not implemented" using kernel 2.4 and postfix 2.4)

Your message dated Sun, 15 Apr 2007 22:17:10 + with message-id <[EMAIL PROTECTED]> and subject line Bug#417530: fixed in postfix 2.4.0-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#412430: marked as done (postfix: [INTL:es] Spanish translation update)

Your message dated Sun, 15 Apr 2007 16:06:18 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#412430: postfix: [INTL:es] Spanish translation update has caused the 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#413288: marked as done (FTBFS on mipsel/experimental (Was: Re: Log for failed build of postfix_2.4.0~rc2-1 (dist=experimental)))

Your message dated Sun, 15 Apr 2007 16:03:25 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#413288: FTBFS on mipsel/experimental (Was: Re: Log for failed build of postfix_2.4.0~rc2-1 (dist=experimental)) has caused the attached Bug report to be marked as done. This means that you

Bug#419468: marked as done (bts: unrecognised BTS URL type)

Your message dated Sun, 15 Apr 2007 22:39:11 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#419468: bts: unrecognised BTS URL type has caused the attached Bug report to 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#219133: marked as done (openssl: cert accept permanently does not work?)

Your message dated Sun, 15 Apr 2007 17:32:06 -0400 with message-id <[EMAIL PROTECTED]> and subject line [EMAIL PROTECTED]: Re: Bug#219133: unreproducible in sid] has caused the 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#415527: marked as done (uim: FTBFS: missing versioning gtk)

Your message dated Sun, 15 Apr 2007 21:17:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415527: fixed in uim 1:1.4.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 case it is now your

Bug#408785: marked as done (please add armel support)

Your message dated Sun, 15 Apr 2007 21:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#408785: fixed in libgdiplus 1.2.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#415086: marked as done (libgdiplus: Please consider adding GNU/kFreeBSD to Architectures field)

Your message dated Sun, 15 Apr 2007 21:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415086: fixed in libgdiplus 1.2.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#411770: marked as done (dh_installxmlcatalogs should create /etc/xml directory for packages it is acted on)

Your message dated Sun, 15 Apr 2007 21:02:16 + with message-id <[EMAIL PROTECTED]> and subject line Bug#411770: fixed in xml-core 0.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 your

Bug#248910: marked as done (xml-core: dh_installxmlcatalogs make unusable installation scripts)

Your message dated Sun, 15 Apr 2007 21:02:16 + with message-id <[EMAIL PROTECTED]> and subject line Bug#248910: fixed in xml-core 0.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 your

Bug#414258: marked as done (Version 1.1 is already available)

Your message dated Sun, 15 Apr 2007 21:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414258: fixed in docbook-simple 1.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#419425: marked as done (gtk2-engines: Missing folder /usr/share/gtk-engines/ (engine schemas))

Your message dated Sun, 15 Apr 2007 21:02:08 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419425: fixed in gtk2-engines 1:2.10.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 case it i

Bug#315759: marked as done (dead code in update-xmlcatalog)

Your message dated Sun, 15 Apr 2007 21:02:16 + with message-id <[EMAIL PROTECTED]> and subject line Bug#315759: fixed in xml-core 0.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 your

Bug#342601: marked as done (Duplicate files in initramfs-tools and udev when upgrading both)

Your message dated Sun, 15 Apr 2007 23:02:27 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bah...third try has caused the attached Bug report to be 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#232215: marked as done (docbook-simple: Can't install: trying to overwrite `/usr/share/sgml/docbook/custom/simple')

Your message dated Sun, 15 Apr 2007 21:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#232215: fixed in docbook-simple 1.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#410533: marked as done (fsck tries fsck.iso9660 on hda6 (ext2|ext3))

Your message dated Sun, 15 Apr 2007 17:05:57 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#410533: fsck tries fsck.iso9660 on hda6 (ext2|ext3) has caused the 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#306719: marked as done ('man dh_installxmlcatalogs' typo: "explantion")

Your message dated Sun, 15 Apr 2007 21:02:16 + with message-id <[EMAIL PROTECTED]> and subject line Bug#306719: fixed in xml-core 0.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 your

Bug#419227: marked as done (nanoblogger-extra suggested, but not available)

Your message dated Sun, 15 Apr 2007 23:06:59 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#419227: nanoblogger-extra suggested, but not available has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#419419: marked as done (docbook2x: Fails to install: update-xmlcatalog: command not found)

Your message dated Sun, 15 Apr 2007 21:02:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419419: fixed in docbook2x 0.8.8-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#419424: marked as done (intltool: provided m4 files produce autoconf warnings)

Your message dated Sun, 15 Apr 2007 20:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419424: fixed in intltool 0.35.5-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#409119: marked as done (Too old libnotify1 causes mail-notification to crash)

Your message dated Sun, 15 Apr 2007 20:32:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#409119: fixed in mail-notification 4.0.dfsg.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 ca

Bug#419304: marked as done (Switch to dh_gtkmodules for the gtk 2.10 transition)

Your message dated Sun, 15 Apr 2007 20:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419304: fixed in gtk-im-libthai 0.1.4-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#412333: marked as done (astyle: newer version available)

Your message dated Sun, 15 Apr 2007 20:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412333: fixed in astyle 1.20.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 yo

Bug#417738: marked as done (FTBFS with GCC 4.3: missing #includes)

Your message dated Sun, 15 Apr 2007 20:32:16 + with message-id <[EMAIL PROTECTED]> and subject line Bug#417738: fixed in vbs 1.4.0-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 your

Bug#415278: marked as done (FTBFS with GCC 4.3: unrecognized command line option "-fno-force-mem")

Your message dated Sun, 15 Apr 2007 20:32:11 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415278: fixed in plplot 5.6.1-11 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#413481: marked as done (FTBFS with GCC 4.3: 'isalnum' was not declared in this scope)

Your message dated Sun, 15 Apr 2007 20:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413481: fixed in astyle 1.20.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 yo

Bug#415565: marked as done (astyle: -l switch breaks code (kdevelop is affected too))

Your message dated Sun, 15 Apr 2007 20:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415565: fixed in astyle 1.20.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 yo

Bug#170810: marked as done (glade-gnome: c++ horizontal scale doesnt show value)

Your message dated Sun, 15 Apr 2007 17:22:10 -0300 with message-id <[EMAIL PROTECTED]> and subject line does not apply since 3.0 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsib

Bug#198422: marked as done (glade: missing license information in generated source code)

Your message dated Sun, 15 Apr 2007 17:22:10 -0300 with message-id <[EMAIL PROTECTED]> and subject line does not apply since 3.0 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsib

Bug#295015: marked as done (xkbprint segfaults when )

Your message dated Sun, 15 Apr 2007 22:11:48 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#295015: xkbprint segfaults when has caused the attached Bug report to be 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#388687: marked as done (alacarte: new upstream version)

Your message dated Sun, 15 Apr 2007 17:14:15 -0300 with message-id <[EMAIL PROTECTED]> and subject line alacarte: new upstream version has caused the attached Bug report to be 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#409237: marked as done (tomboy spellcheck doesn't highlight)

Your message dated Sun, 15 Apr 2007 22:04:38 +0200 with message-id <[EMAIL PROTECTED]> and subject line tomboy spellcheck doesn't highlight has caused the attached Bug report to be 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#402615: marked as done (tomboy: Does not start, seems like a missing dependency)

Your message dated Sun, 15 Apr 2007 21:46:01 +0200 with message-id <[EMAIL PROTECTED]> and subject line tomboy: Does not start, seems like a missing dependency has caused the 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#396414: marked as done (tomboy: crashes on start: assertion failed: (async_call_klass) in threadpool.c:990)

Your message dated Sun, 15 Apr 2007 21:44:09 +0200 with message-id <[EMAIL PROTECTED]> and subject line tomboy: crashes on start: assertion failed: (async_call_klass) in threadpool.c:990 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been d

Bug#313298: marked as done (two running tomboys don't play well with keybindings)

Your message dated Sun, 15 Apr 2007 19:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#313298: fixed in tomboy 0.6.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 you

Bug#407744: marked as done (beagle: Beagle don't access to tomboy's notes)

Your message dated Sun, 15 Apr 2007 19:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#407744: fixed in tomboy 0.6.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 you

Bug#400552: marked as done (tomboy: crashes on start)

Your message dated Sun, 15 Apr 2007 19:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400552: fixed in tomboy 0.6.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 you

Processed (with 1 errors): unmerging 419306 419411 and closing 419411

Processing commands for [EMAIL PROTECTED]: > unmerge 419306 419411 Unknown command or malformed arguments to command. > close 419411 Bug#419411: gtk-qt-engine: package not installable in sid 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug#419306: Switch to dh_gtkmodul

Bug#415420: marked as done (New upstream version: 0.6.1)

Your message dated Sun, 15 Apr 2007 19:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415420: fixed in tomboy 0.6.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 you

Bug#372776: marked as done (please ship fixed width plugin)

Your message dated Sun, 15 Apr 2007 19:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#372776: fixed in tomboy 0.6.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 you

Bug#388205: marked as done (diff for 0.3.9+dfsg-2.1 NMU)

Your message dated Sun, 15 Apr 2007 19:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#388205: fixed in tomboy 0.6.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 you

Bug#396177: marked as done (WikiWords interfere with other implicit linking mechanisms)

Your message dated Sun, 15 Apr 2007 19:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#396177: fixed in tomboy 0.6.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 you

Bug#418566: marked as done (new upstream version 0.6.3 available)

Your message dated Sun, 15 Apr 2007 19:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#418566: fixed in tomboy 0.6.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 you

Bug#386271: marked as done (tomboy: crashes when opening preferences)

Your message dated Sun, 15 Apr 2007 19:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#386271: fixed in tomboy 0.6.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 you

Bug#356833: marked as done (tomboy: Tomboy isn't restarted by X session manager)

Your message dated Sun, 15 Apr 2007 19:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#356833: fixed in tomboy 0.6.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 you

Bug#332962: marked as done (tulip module no longer works on a500)

Your message dated Sun, 15 Apr 2007 19:22:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#332962: fixed in linux-2.6 2.6.20-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#396241: marked as done (login: Executing su cause an "invalid pointer" error)

Your message dated Sun, 15 Apr 2007 21:23:31 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#396241: login: Executing su cause an "invalid pointer" 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#416027: marked as done (XARGS(1) mentions "noyau", then "core")

Your message dated Sun, 15 Apr 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#416027: fixed in manpages-fr-extra 20070415 has caused the 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#414950: marked as done (Package collision? libezv24 and libezv24-0)

Your message dated Sun, 15 Apr 2007 21:00:08 +0200 with message-id <[EMAIL PROTECTED]> and subject line Close #414950 has caused the attached Bug report to be 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#398502: marked as done (Shouldn't build depend on an unversioned automake)

Your message dated Sun, 15 Apr 2007 18:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#398502: fixed in freesci 0.3.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 yo

Bug#133151: marked as done (xbase-clients: [xmag] SEGV in GetMinIntensity() when trying to magnify top edge of screen)

Your message dated Sun, 15 Apr 2007 20:40:24 +0200 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report to be 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#414304: marked as done (Beagle should depend on dbus)

Your message dated Sun, 15 Apr 2007 18:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414304: fixed in beagle 0.2.16.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#414701: marked as done (beagle: Beagle filter lib does not feature FilterDOC (which is in the source))

Your message dated Sun, 15 Apr 2007 18:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414701: fixed in beagle 0.2.16.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#416456: marked as done (kmail backend returns incomplete information)

Your message dated Sun, 15 Apr 2007 18:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#416456: fixed in beagle 0.2.16.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#403860: marked as done (Python-spf pyspf updated package available (2.0.1))

Your message dated Sun, 15 Apr 2007 18:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403860: fixed in pyspf 2.0.3-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#413410: marked as done (URI change in package description)

Your message dated Sun, 15 Apr 2007 18:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413410: fixed in beagle 0.2.16.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#413479: marked as done (beagle should index *.xhtml (application/xhtml+xml) files)

Your message dated Sun, 15 Apr 2007 18:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413479: fixed in beagle 0.2.16.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#399938: marked as done (Should only provides ${python:Provides})

Your message dated Sun, 15 Apr 2007 18:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#399938: fixed in pyspf 2.0.3-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#399403: marked as done (RM: pdns-recursor [arm hppa mips mipsel sparc] -- RoRA; ANAIS)

Your message dated Sun, 15 Apr 2007 19:26:37 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#399403: RM: pdns-recursor [arm, hppa, mips, mipsel, sparc] --RoRA; ANAIS (blocking security fix) has caused the attached Bug report to be marked as done. This means that you claim that the

Bug#413425: marked as done (sudo: doesn't accept more than 16347 arguments)

Your message dated Sun, 15 Apr 2007 19:55:05 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#413425: this bug/413425: sudo: doesn't accept more than 16347 arguments has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wi

Bug#416943: marked as done (startxfce4 manpage typo)

Your message dated Sun, 15 Apr 2007 18:17:44 + with message-id <[EMAIL PROTECTED]> and subject line Bug#416943: fixed in xfce4-utils 4.4.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 no

Processed: closing 401969

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.2 > close 401969 1.1.1-2 Bug#401969: please build using hunspell 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.1.1-2, send any

  1   2   3   >