Bug#410723: marked as done (big bind mounts make login take a looong time)

Your message dated Sat, 09 Jun 2007 06:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#410723: fixed in cowdancer 0.34 has caused the attached Bug report to be 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#427809: marked as done (shntool: new upstream version 3.0.3 is available)

Your message dated Sat, 09 Jun 2007 07:02:03 + with message-id [EMAIL PROTECTED] and subject line Bug#427809: fixed in shntool 3.0.3-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#322354: marked as done (gtk2-engines-industrial misses cursors/sb_left_arrow)

Your message dated Sat, 09 Jun 2007 10:10:46 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in dmz-cursor-theme has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#310894: marked as done (gtk2-engines-industrial: lr_angle missing)

Your message dated Sat, 09 Jun 2007 10:10:46 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in dmz-cursor-theme has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#416190: marked as done (iceweasel: 'About ...' should be the last entry in 'Help' menu)

Your message dated Sat, 09 Jun 2007 08:47:23 + with message-id [EMAIL PROTECTED] and subject line Bug#416190: fixed in iceweasel 2.0.0.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#420051: marked as done (Swedish translation for iceweasel.desktop)

Your message dated Sat, 09 Jun 2007 08:47:23 + with message-id [EMAIL PROTECTED] and subject line Bug#420051: fixed in iceweasel 2.0.0.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#409074: marked as done (iceweasel: font size)

Your message dated Sat, 09 Jun 2007 08:47:23 + with message-id [EMAIL PROTECTED] and subject line Bug#409074: fixed in iceweasel 2.0.0.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#427785: marked as done (New upstream release (2.0.0.4))

Your message dated Sat, 09 Jun 2007 08:47:23 + with message-id [EMAIL PROTECTED] and subject line Bug#427785: fixed in iceweasel 2.0.0.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#395268: marked as done (libmail-mboxparser-perl: FTBFS: build times out during test (t/3_while))

Your message dated Sat, 09 Jun 2007 09:32:05 + with message-id [EMAIL PROTECTED] and subject line Bug#395268: fixed in libmail-mboxparser-perl 0.55-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

Bug#415752: marked as done (/etc/init.d/nagios2 reload removes the pid file)

Your message dated Sat, 09 Jun 2007 11:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#415752: fixed in nagios2 2.9-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#423639: marked as done (nagios2: autogenerated file for localhost does not point to correct location for gd2 file)

Your message dated Sat, 09 Jun 2007 11:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#423639: fixed in nagios2 2.9-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#414762: marked as done ([INTL:nl] Dutch po-debconf translation)

Your message dated Sat, 09 Jun 2007 11:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#414762: fixed in nagios2 2.9-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#413122: marked as done (nagios2: [INTL:ja] Japanese debconf templates translation)

Your message dated Sat, 09 Jun 2007 11:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#413122: fixed in nagios2 2.9-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#416763: marked as done (nagios2: nagios reload hangs in FUTEX_WAIT)

Your message dated Sat, 09 Jun 2007 11:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#416763: fixed in nagios2 2.9-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#414050: marked as done (nagios2-common: /etc/init.d/nagios2 needs sleep call for restart target)

Your message dated Sat, 09 Jun 2007 11:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#414050: fixed in nagios2 2.9-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#414652: marked as done (nagios2: notifications not working)

Your message dated Sat, 09 Jun 2007 11:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#414652: fixed in nagios2 2.9-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#412980: marked as done (/etc/init.d/nagios2 reload removes the pidfile)

Your message dated Sat, 09 Jun 2007 11:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#412980: fixed in nagios2 2.9-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#414647: marked as done (nagios2: Nagios 2.8 is out and fixes some faults and annoyances)

Your message dated Sat, 09 Jun 2007 11:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#414647: fixed in nagios2 2.9-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#397289: marked as done (nagios2-common: various ways of init script failing cause package installation to fail)

Your message dated Sat, 09 Jun 2007 11:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#397289: fixed in nagios2 2.9-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#386976: marked as done (dropbear does not work on low entropy systems)

Your message dated Sat, 09 Jun 2007 11:47:02 + with message-id [EMAIL PROTECTED] and subject line Bug#386976: fixed in dropbear 0.49-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#428096: marked as done (liquidsoap: needs libcamomile-ocaml-data)

Your message dated Sat, 09 Jun 2007 12:02:02 + with message-id [EMAIL PROTECTED] and subject line Bug#428096: fixed in liquidsoap 0.3.2-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#421446: marked as done (fetchmail: Invalid SSL protocol '' specified, using default (SSLv23).)

Your message dated Sat, 9 Jun 2007 14:24:57 +0200 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#427594: marked as done (wmwave: FTBFS: /usr/include/linux/wireless.h:650: error: expected specifier-qualifier-list before '__s32')

Your message dated Sat, 09 Jun 2007 12:47:10 + with message-id [EMAIL PROTECTED] and subject line Bug#427594: fixed in wmwave 0.4-8 has caused the attached Bug report to be 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#427405: marked as done (Kerberos v5 support)

Your message dated Sat, 09 Jun 2007 12:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#427405: fixed in fetchmail 6.3.8-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#406947: marked as done (wmwave: No Level or Noise given with Atheros card)

Your message dated Sat, 09 Jun 2007 12:47:10 + with message-id [EMAIL PROTECTED] and subject line Bug#406947: fixed in wmwave 0.4-8 has caused the attached Bug report to be 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#421405: marked as done (The homepage for wmwave in the manpage is wrong.)

Your message dated Sat, 09 Jun 2007 12:47:10 + with message-id [EMAIL PROTECTED] and subject line Bug#421405: fixed in wmwave 0.4-8 has caused the attached Bug report to be 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#225279: marked as done (wmwave causes flood of messages in console)

Your message dated Sat, 09 Jun 2007 12:47:10 + with message-id [EMAIL PROTECTED] and subject line Bug#225279: fixed in wmwave 0.4-8 has caused the attached Bug report to be 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#417657: marked as done (sysvinit: reboot causes unclean shutdown of md raid1)

Your message dated Sat, 9 Jun 2007 11:09:14 -0300 with message-id [EMAIL PROTECTED] and subject line Please refer to http://linux-ata.org/shutdown.html has caused the attached Bug 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#426874: marked as done (ITP: upt -- High-level library for managing Debian package information)

Your message dated Sat, 09 Jun 2007 15:03:18 + with message-id [EMAIL PROTECTED] and subject line Bug#426874: fixed in libept 0.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#427899: marked as done (update-manager_0.59.20-1(sparc/experimental): FTBFS: Python.h: No such file or directory)

Your message dated Sat, 09 Jun 2007 15:17:21 + with message-id [EMAIL PROTECTED] and subject line Bug#427899: fixed in update-manager 0.42.2ubuntu22-12 has caused the attached 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#328630: marked as done (grub-splashimages: splashimages fail to install when system has a separate /boot partition)

Your message dated Sat, 9 Jun 2007 17:24:44 +0200 with message-id [EMAIL PROTECTED] and subject line grub-splashimages: breaks/fails when /boot is on a separate partition 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#270073: marked as done (grub-splashimages: breaks on systems where /boot is a separate partition)

Your message dated Sat, 9 Jun 2007 17:24:44 +0200 with message-id [EMAIL PROTECTED] and subject line grub-splashimages: breaks/fails when /boot is on a separate partition 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#427882: marked as done (Suggests nonexistent xmorph-example)

Your message dated Sat, 9 Jun 2007 17:36:04 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#427882: Suggests nonexistent xmorph-example has caused the attached Bug report 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#390023: marked as done (multipath-tools: fail to install)

Your message dated Sat, 9 Jun 2007 17:57:15 +0200 with message-id [EMAIL PROTECTED] and subject line Etch is released has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#419231: marked as done (svn-noautodch doesn't work)

Your message dated Sat, 09 Jun 2007 16:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#419231: fixed in svn-buildpackage 0.6.21 has caused the attached Bug report to 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#285321: marked as done (grub-splashimages: Add debblue splash)

Your message dated Sat, 09 Jun 2007 16:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#285321: fixed in grub-splashimages 1.2.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

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

Your message dated Sat, 9 Jun 2007 22:04:04 +0530 with message-id [EMAIL PROTECTED] and subject line Compiling IT++ with GCC 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 now your

Bug#428139: marked as done ([amd64][etch][4.0r0] success: Sun X2200 server)

Your message dated Sat, 9 Jun 2007 18:33:52 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#428139: [amd64][etch][4.0r0] success: Sun X2200 server has caused the 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#428171: marked as done (Broken dependencies / wrong versions in stable repository)

Your message dated Sat, 9 Jun 2007 19:08:23 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#428171: Broken dependencies / wrong versions in stable repository 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#400563: marked as done (shell scripts not strictly POSIX conformant)

Your message dated Sat, 9 Jun 2007 19:30:51 +0200 with message-id [EMAIL PROTECTED] and subject line fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#428184: marked as done (libgphoto2-2: /etc/udev/rules.d/025_libgphoto2.rules is not recreated upon reinstallation)

Your message dated Sat, 9 Jun 2007 19:49:49 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#428184: libgphoto2-2: /etc/udev/rules.d/025_libgphoto2.rules is not recreated upon reinstallation has caused the attached Bug report to be marked as done. This means that you claim that the

Bug#426444: marked as done (libtalloc-dev: Should depend on libtalloc1)

Your message dated Sat, 09 Jun 2007 17:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#426444: fixed in talloc 1.0.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#393897: marked as done (gcc-4.2: cross-compiler FTBFS)

Your message dated Sat, 09 Jun 2007 18:17:15 + with message-id [EMAIL PROTECTED] and subject line Bug#393897: fixed in gcc-4.2 4.2-20070609-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#426905: marked as done (gcc-4.2: FTBFS on hurd-i386: 'OPTION_GLIBC' undeclared)

Your message dated Sat, 09 Jun 2007 18:17:15 + with message-id [EMAIL PROTECTED] and subject line Bug#426905: fixed in gcc-4.2 4.2-20070609-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#424855: marked as done (Apply patches up to a specific patch)

Your message dated Sat, 09 Jun 2007 18:17:15 + with message-id [EMAIL PROTECTED] and subject line Bug#424855: fixed in gcc-4.2 4.2-20070609-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#424693: marked as done (gcc-4.2: outdated rules.conf (update needed for kfreebsd-amd64))

Your message dated Sat, 09 Jun 2007 18:17:15 + with message-id [EMAIL PROTECTED] and subject line Bug#424693: fixed in gcc-4.2 4.2-20070609-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#419511: marked as done (several file conflicts with gcc-4.1)

Your message dated Sat, 09 Jun 2007 18:17:15 + with message-id [EMAIL PROTECTED] and subject line Bug#419511: fixed in gcc-4.2 4.2-20070609-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#422513: marked as done (gcc-4.1: Can't crosscompile: /usr/bin/ld: cannot find -lgcc)

Your message dated Sat, 09 Jun 2007 19:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#422513: fixed in alsa-lib 1.0.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#424310: marked as done (alsa-lib_1.0.14~rc4-1(hppa/experimental): FTBFS: gcc-multilib not available on all arches)

Your message dated Sat, 09 Jun 2007 19:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#424310: fixed in alsa-lib 1.0.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#408766: marked as done (please add armel support)

Your message dated Sat, 09 Jun 2007 19:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#408766: fixed in alsa-lib 1.0.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#420999: marked as done (typo in control file breaks hppa build)

Your message dated Sat, 09 Jun 2007 19:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#420999: fixed in alsa-lib 1.0.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#408770: marked as done (please add armel support)

Your message dated Sat, 09 Jun 2007 19:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#408770: fixed in alsa-oss 1.0.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#419099: marked as done (alsa-oss: breaks large file support)

Your message dated Sat, 09 Jun 2007 19:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#419099: fixed in alsa-oss 1.0.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#364730: marked as done (preload of libaoss.so causes mutt to segfault on large mboxes)

Your message dated Sat, 09 Jun 2007 19:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#364730: fixed in alsa-oss 1.0.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#425430: marked as done (Unmute Front channel)

Your message dated Sat, 09 Jun 2007 19:47:02 + with message-id [EMAIL PROTECTED] and subject line Bug#425430: fixed in alsa-utils 1.0.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#408773: marked as done (please add armel support)

Your message dated Sat, 09 Jun 2007 19:47:02 + with message-id [EMAIL PROTECTED] and subject line Bug#408773: fixed in alsa-utils 1.0.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#426077: marked as done (Fwd: Patch for mpop-1.0.5 to fix the APOP weakness)

Your message dated Sat, 09 Jun 2007 19:52:17 + with message-id [EMAIL PROTECTED] and subject line Bug#426077: fixed in mpop 1.0.5-1etch1 has caused the attached Bug report to be 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#418850: marked as done (Usb cdrom unit not automatically recognized by installer)

Your message dated Sat, 09 Jun 2007 19:52:20 + with message-id [EMAIL PROTECTED] and subject line Bug#418850: fixed in cdrom-detect 1.20etch1 has caused the attached Bug report to 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#356671: marked as done (lifelines: error in question after asking for appending an individual as a child (french))

Your message dated Sat, 09 Jun 2007 19:52:22 + with message-id [EMAIL PROTECTED] and subject line Bug#356671: fixed in lifelines 3.0.50-2etch1 has caused the attached Bug report to 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#405500: marked as done (lifelines-reports: missing conflicts with sarge lifelines (duplicate file))

Your message dated Sat, 09 Jun 2007 19:52:22 + with message-id [EMAIL PROTECTED] and subject line Bug#405500: fixed in lifelines 3.0.50-2etch1 has caused the attached Bug report to 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#422442: marked as done (Sets incorrect codename for CD installs if mirror is not up-to-date)

Your message dated Sat, 09 Jun 2007 19:52:15 + with message-id [EMAIL PROTECTED] and subject line Bug#422442: fixed in apt-setup 1:0.20etch1 has caused the attached Bug report to 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#364404: marked as done (lifelines: new fr.po (proposal))

Your message dated Sat, 09 Jun 2007 19:52:22 + with message-id [EMAIL PROTECTED] and subject line Bug#356671: fixed in lifelines 3.0.50-2etch1 has caused the attached Bug report to 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#418347: marked as done (PDF documentation cannot be opened (broken PDF))

Your message dated Sat, 09 Jun 2007 19:52:22 + with message-id [EMAIL PROTECTED] and subject line Bug#418347: fixed in lifelines 3.0.50-2etch1 has caused the attached Bug report to 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#421323: marked as done (Bug in Debian expertgui installer)

Your message dated Sat, 09 Jun 2007 19:52:21 + with message-id [EMAIL PROTECTED] and subject line Bug#421323: fixed in user-setup 1.11etch1 has caused the attached Bug report to 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#304832: marked as done (doesn't support arch-specific packages)

Your message dated Sat, 9 Jun 2007 21:09:56 +0100 with message-id [EMAIL PROTECTED] and subject line This should have been fixed for quite a while has caused the attached Bug report to 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#384487: marked as done (debtags can not work Off-Line)

Your message dated Sat, 9 Jun 2007 21:32:49 +0100 with message-id [EMAIL PROTECTED] and subject line Debtags uses the tags from the apt packages file by default has caused the 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#407428: marked as done (libasound2-plugins: add a52 plugin)

Your message dated Sat, 09 Jun 2007 20:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#407428: fixed in alsa-plugins 1.0.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

Bug#422773: marked as done (alsa-tools-gui does not include .desktop files)

Your message dated Sat, 09 Jun 2007 20:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#422773: fixed in alsa-tools 1.0.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#408771: marked as done (please add armel support)

Your message dated Sat, 09 Jun 2007 20:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#408771: fixed in alsa-plugins 1.0.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

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

Your message dated Sat, 09 Jun 2007 20:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#408772: fixed in alsa-tools 1.0.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#299021: marked as done (tag special::meta does not show up in GUI)

Your message dated Sat, 9 Jun 2007 22:15:00 +0100 with message-id [EMAIL PROTECTED] and subject line Seems to be fixed 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 responsibility

Bug#320177: marked as done (debtags-edit: diff against central database)

Your message dated Sat, 9 Jun 2007 22:22:25 +0100 with message-id [EMAIL PROTECTED] and subject line I have forgotten to close the bug when I uploaded to unstable has caused 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#428101: marked as done (qemu-launcher: Please allow new qcow2 disks to be made)

Your message dated Sat, 09 Jun 2007 21:32:07 + with message-id [EMAIL PROTECTED] and subject line Bug#428101: fixed in qemu-launcher 1.7.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

Bug#417673: marked as done (/sbin/fsck.vfat: Incorrectly truncates files of 4294966784 bytes length during boot. )

Your message dated Sat, 09 Jun 2007 21:32:04 + with message-id [EMAIL PROTECTED] and subject line Bug#417673: fixed in dosfstools 2.11-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#399521: marked as done (path to qemuctl should have a default value, even if qemuctl is not installed)

Your message dated Sat, 09 Jun 2007 21:32:07 + with message-id [EMAIL PROTECTED] and subject line Bug#399521: fixed in qemu-launcher 1.7.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

Bug#424028: marked as done (python-sqlobject: sqlobject-admin not in $PATH)

Your message dated Sat, 09 Jun 2007 21:32:08 + with message-id [EMAIL PROTECTED] and subject line Bug#424028: fixed in sqlobject 0.9.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#347047: marked as done (xslideshow: FTBFS: build-depends on removed xlibs-dev)

Your message dated Sat, 9 Jun 2007 23:17:11 +0200 with message-id [EMAIL PROTECTED] and subject line also fixed in current 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

Bug#422443: marked as done (Upstream version much more recent)

Your message dated Sat, 09 Jun 2007 21:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#422443: fixed in sfront 0.91-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#395469: marked as done (approx stops working when syslog-ng gets restarted)

Your message dated Sat, 09 Jun 2007 22:02:03 + with message-id [EMAIL PROTECTED] and subject line Bug#395469: fixed in syslog-ocaml 1.3-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#421071: marked as done (FTBFS: ! LaTeX Error: File `fancyheadings.sty' not found.)

Your message dated Sat, 09 Jun 2007 23:02:03 + with message-id [EMAIL PROTECTED] and subject line Bug#421071: fixed in freefem 3.5.8-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#324361: marked as done (python-xlib: clean removes build-stamp unnecessarily)

Your message dated Sat, 9 Jun 2007 19:18:57 -0400 with message-id [EMAIL PROTECTED] and subject line not a bug has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen

Bug#373367: marked as done (Python policy transition)

Your message dated Sat, 9 Jun 2007 19:24:22 -0400 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#417153: marked as done (FTBFS with GCC 4.3: missing #includes)

Your message dated Sat, 09 Jun 2007 23:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#417153: fixed in debtags 1.7.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

Bug#402852: marked as done (debtags: man page examples use -d ? but it seems to be broken)

Your message dated Sat, 09 Jun 2007 23:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#402852: fixed in debtags 1.7.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

Bug#402853: marked as done (debtags: please recommends tagcol)

Your message dated Sat, 09 Jun 2007 23:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#402853: fixed in debtags 1.7.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

Bug#324443: marked as done (python2.3-xlib: in DISPLAY=unix:0.0, unix is not a hostname)

Your message dated Sat, 09 Jun 2007 23:32:07 + with message-id [EMAIL PROTECTED] and subject line Bug#324443: fixed in python-xlib 0.13-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#423376: marked as done (debtags dumpavail uses Name: instead of Package:)

Your message dated Sat, 09 Jun 2007 23:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#423376: fixed in debtags 1.7.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

Bug#357507: marked as done (python-xlib: Receiving buffer to small)

Your message dated Sat, 09 Jun 2007 23:32:07 + with message-id [EMAIL PROTECTED] and subject line Bug#357507: fixed in python-xlib 0.13-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

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

Your message dated Sat, 09 Jun 2007 23:32:04 + with message-id [EMAIL PROTECTED] and subject line Bug#417154: fixed in debtags-edit 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 now

Bug#423377: marked as done (debtags dumpavail uses Tags: instead of Tag:)

Your message dated Sat, 09 Jun 2007 23:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#423377: fixed in debtags 1.7.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

Bug#397516: marked as done (broken formatting)

Your message dated Sat, 09 Jun 2007 23:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#397516: fixed in debtags 1.7.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

Bug#421594: marked as done (New upstream release (0.13) is available)

Your message dated Sat, 09 Jun 2007 23:32:07 + with message-id [EMAIL PROTECTED] and subject line Bug#421594: fixed in python-xlib 0.13-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#423370: marked as done (debtags: dumpavail does not separate packages)

Your message dated Sat, 09 Jun 2007 23:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#423370: fixed in debtags 1.7.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

Bug#420774: marked as done (python-xlib: description states it's a dummy package when it's not)

Your message dated Sat, 09 Jun 2007 23:32:07 + with message-id [EMAIL PROTECTED] and subject line Bug#420774: fixed in python-xlib 0.13-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#399102: marked as done (debtags: Typo in man page: matchthe -- match the (twice))

Your message dated Sat, 09 Jun 2007 23:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#399102: fixed in debtags 1.7.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

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

Your message dated Sat, 09 Jun 2007 16:47:33 -0700 with message-id [EMAIL PROTECTED] and subject line Icedove 2.0 now packaged has caused the attached Bug report to be 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#421862: marked as done (RFP: icedove 2.0)

Your message dated Sat, 09 Jun 2007 16:47:33 -0700 with message-id [EMAIL PROTECTED] and subject line Icedove 2.0 now packaged has caused the attached Bug report to be 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#424012: marked as done (scim-hangul: FTBFS: cannot remove `debian/tmp/usr/lib/scim-1.0/1.4.0/*/*.la' )

Your message dated Sun, 10 Jun 2007 02:02:02 + with message-id [EMAIL PROTECTED] and subject line Bug#424012: fixed in scim-hangul 0.2.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#428172: marked as done (missing dependency on laptop-detect)

Your message dated Sun, 10 Jun 2007 03:47:02 + with message-id [EMAIL PROTECTED] and subject line Bug#428172: fixed in cpufrequtils 002-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#423727: marked as done (dx - FTBFS: error: previous declaration of 'VendorShellClassRec vendorShellClassRec' with 'C++' linkage)

Your message dated Sun, 10 Jun 2007 05:32:05 + with message-id [EMAIL PROTECTED] and subject line Bug#423280: fixed in dx 1:4.4.0-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

  1   2   >