Bug#398471: marked as done ('man dog' typos: "atleast", "conjuction" x 2, and "eachother")

Your message dated Mon, 13 Nov 2006 23:32:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398471: fixed in dog 1.7-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 res

Bug#381677: marked as done (initramfs-tools: Temporary files and initramfs world-readable)

Your message dated Mon, 13 Nov 2006 23:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#381677: fixed in initramfs-tools 0.85b has caused the attached Bug report to 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#398488: marked as done (libgecode7-dev should be libgecode8-dev to match SONAME)

Your message dated Tue, 14 Nov 2006 09:46:27 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#398488: libgecode7-dev should be libgecode8-dev to match SONAME has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#390597: marked as done (sasl2-bin failed during reinstall upon postfix-tls failure)

Your message dated Tue, 14 Nov 2006 09:46:12 +0200 with message-id <[EMAIL PROTECTED]> and subject line sasl2-bin failed during reinstall upon postfix-tls failure has caused the 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#397787: marked as done (please provide switch to disable initrd backups)

Your message dated Mon, 13 Nov 2006 23:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#397787: fixed in initramfs-tools 0.85b has caused the attached Bug report to 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#377834: marked as done (Recommends unavailable lm-sensors-mod)

Your message dated Mon, 13 Nov 2006 21:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#377834: fixed in xsensors 0.50-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#349130: marked as done (xsensors: new upstream version available)

Your message dated Mon, 13 Nov 2006 21:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#349130: fixed in xsensors 0.50-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#395622: marked as done (movixmaker-2: missing binary-arch target in debian/rules (Policy 4.9))

Your message dated Mon, 13 Nov 2006 21:32:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#395622: fixed in movixmaker-2 0.8.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 n

Bug#381584: marked as done (Add module efivars for i386 to support elilo on MacBook Pro)

Your message dated Mon, 13 Nov 2006 20:47:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#381584: fixed in kernel-wedge 2.29 has caused the attached Bug report to be 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#375943: marked as done ("stalin contains non-free OpenGL/Xlib bindings for Allegro Common Lisp")

Your message dated Mon, 13 Nov 2006 20:17:52 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#375943: fixed in stalin 0.11-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#337169: marked as done (stalin: ftbfs [sparc] Assertion `((size_t) &((struct{char dummy; FILE probe; } *)0)->probe)==4' failed)

Your message dated Mon, 13 Nov 2006 20:17:52 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#337169: fixed in stalin 0.11-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#347053: marked as done (stalin: FTBFS: build-depends on removed xlibs-dev)

Your message dated Mon, 13 Nov 2006 20:17:52 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#347053: fixed in stalin 0.11-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#271836: marked as done (FTBFS: source too large)

Your message dated Mon, 13 Nov 2006 20:17:52 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#271836: fixed in stalin 0.11-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#273130: marked as done (powerpc: arch is not in arch list, although it's supported)

Your message dated Mon, 13 Nov 2006 20:17:52 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#273130: fixed in stalin 0.11-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#386786: marked as done (libassa3.4-0: segmentation fault)

Your message dated Mon, 13 Nov 2006 22:40:49 -0500 with message-id <[EMAIL PROTECTED]> and subject line unreproducible has caused the attached Bug report to be 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 r

Bug#389426: marked as done (cherokee: 'status' target in the init script not working properly)

Your message dated Mon, 13 Nov 2006 19:17:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#389426: fixed in cherokee 0.5.5.dfsg-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#397428: marked as done (libapache-dbilogger-perl: strange file in package)

Your message dated Mon, 13 Nov 2006 19:17:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#397428: fixed in libapache-dbilogger-perl 0.93-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 c

Bug#398483: marked as done (nethack-x11: font misinstalled as /usr/share/fonts/misc)

Your message dated Mon, 13 Nov 2006 18:17:15 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398483: fixed in nethack 3.4.3-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 y

Bug#339736: marked as done (gnupg-agent: manpage for gpg-agent missing)

Your message dated Mon, 13 Nov 2006 20:45:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line all closed in latest upload has caused the attached Bug report to be 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 respon

Bug#368552: marked as done (gpgsm: Fatal: libksba is too old (need 0.9.13, have 0.9.12))

Your message dated Mon, 13 Nov 2006 20:45:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line all closed in latest upload has caused the attached Bug report to be 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 respon

Bug#307881: marked as done (missing manpage for /usr/bin/gpg-agent)

Your message dated Mon, 13 Nov 2006 20:45:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line all closed in latest upload has caused the attached Bug report to be 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 respon

Bug#300677: marked as done (no man pages for any binaries in gpgsm)

Your message dated Mon, 13 Nov 2006 20:45:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line all closed in latest upload has caused the attached Bug report to be 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 respon

Bug#395691: marked as done (gnupg2: missing binary-indep target in debian/rules (Policy 4.9))

Your message dated Mon, 13 Nov 2006 20:45:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line all closed in latest upload has caused the attached Bug report to be 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 respon

Bug#300129: marked as done (gnupg-agent: no manpage for gpg-agent)

Your message dated Mon, 13 Nov 2006 20:45:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line all closed in latest upload has caused the attached Bug report to be 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 respon

Bug#378489: marked as done (gnupg2: New upstream version 1.9.22)

Your message dated Mon, 13 Nov 2006 20:45:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line all closed in latest upload has caused the attached Bug report to be 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 respon

Bug#388257: marked as done (gnupg2: New upstream that can replace gpg(1) for testing/experimental: 1.9.23)

Your message dated Mon, 13 Nov 2006 20:45:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line all closed in latest upload has caused the attached Bug report to be 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 respon

Bug#398134: marked as done (python-turbogears: README.Debian is outdated)

Your message dated Mon, 13 Nov 2006 17:17:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398134: fixed in turbogears 1.0~b1-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 no

Bug#398086: marked as done (libpfm3-3.2-dev: unuseable on mips)

Your message dated Mon, 13 Nov 2006 16:32:16 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398086: fixed in libpfm3-3.2 3.2.060926-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

Bug#398474: marked as done (libapache-request-perl: Fails with unresolved dynamic load)

Your message dated Mon, 13 Nov 2006 16:04:45 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398474: libapache-request-perl: Fails with unresolved dynamic load has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#389549: marked as done (libvtk5-dev: uppercase vtkdata path in some files)

Your message dated Mon, 13 Nov 2006 16:02:44 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#389549: fixed in vtk 5.0.2-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Processed: close bug properly

Processing commands for [EMAIL PROTECTED]: > # ask BTS to reopen bug so it can be closed > reopen 347813 Bug#347813: amavisd-new: amavis not checking for spam or viruses after upgrade 'reopen' is deprecated when a bug has been closed with a version; use 'found' or 'submitter' as appropriate instea

Bug#295958: marked as done (test failures when not in /tmp)

Your message dated Tue, 14 Nov 2006 01:01:59 +0100 with message-id <[EMAIL PROTECTED]> and subject line cheetah: test failures when not in /tmp has caused the attached Bug report to be 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#393984: marked as done (mkvmerge segfaults when attempting to attach non-existant file)

Your message dated Mon, 13 Nov 2006 15:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#393984: fixed in mkvtoolnix 1.8.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#394858: marked as done (python-pyxmpp: missing dependency on python-libxml2)

Your message dated Mon, 13 Nov 2006 15:02:29 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#394858: fixed in pyxmpp 1.0.0-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#398308: marked as done (Uninstallable because of dependency on non-existent package bluez-tools)

Your message dated Mon, 13 Nov 2006 15:02:26 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398308: fixed in multisync 0.82-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 y

Bug#393961: marked as done (doesn't honor DEB_BUILD_OPTIONS=nostrip)

Your message dated Mon, 13 Nov 2006 15:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#393961: fixed in mkvtoolnix 1.8.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#321917: marked as done (postgresql-7.4: can't specify an interval as a placeholder any more)

Your message dated Mon, 13 Nov 2006 14:48:24 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#315708: fixed in libdbd-pg-perl 1.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

Bug#398276: marked as done (xdm: don't bundle turning on sit0 irradiating me all day)

Your message dated Tue, 14 Nov 2006 00:08:24 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#398276: xdm: don't bundle turning on sit0 irradiating me all day 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#315708: marked as done (libdbd-pg-perl: execute fails with latest version)

Your message dated Mon, 13 Nov 2006 14:48:24 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#315708: fixed in libdbd-pg-perl 1.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

Bug#398384: marked as done (libghc6-plugins-dev: postinst fails: ghc-pkg: dependency haskell-src-exts doesn't exist (use --force to override))

verride) dpkg: error processing libghc6-plugins-dev (--configure): subprocess post-installation script returned error exit status 1 The full log is available from http://ox.blop.info/bazaar/buildlogs/20061113/ The piuparts run was done on about 40 AMD64 nodes of the Grid'5000 platform

Bug#397243: marked as done (xoscope: oscope gone missing when rebult)

Your message dated Mon, 13 Nov 2006 14:52:20 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#397243: fixed in xoscope 1.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 you

Bug#396740: marked as done (fai-kernels: please add fbdev driver)

Your message dated Mon, 13 Nov 2006 14:47:40 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396740: fixed in fai-kernels 1.13 has caused the attached Bug report to be 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#365559: marked as done (libmthca: ftbfs [sparc] Error: Architecture mismatch on "membar".)

Your message dated Mon, 13 Nov 2006 14:48:35 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#365559: fixed in libmthca 1.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 y

Bug#398243: marked as done (frozen-bubble - FTBFS: convert: command not found)

Your message dated Mon, 13 Nov 2006 14:47:53 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398243: fixed in frozen-bubble 2.0.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

Bug#387572: marked as done (fai-kernels: please enable bnx2)

Your message dated Mon, 13 Nov 2006 14:47:40 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#387572: fixed in fai-kernels 1.13 has caused the attached Bug report to be 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#296822: marked as done (kcontrol: URI for Printer on parallel port is broken)

Your message dated Mon, 13 Nov 2006 23:12:47 +0100 with message-id <[EMAIL PROTECTED]> and subject line kcontrol: URI for Printer on parallel port is broken has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#267635: marked as done (ksplash: Rotate the earth sphere according to the region settings)

Your message dated Mon, 13 Nov 2006 22:53:43 +0100 with message-id <[EMAIL PROTECTED]> and subject line ksplash: Rotate the earth sphere according to the region settings has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#307346: marked as done (Some images packaged with apache-common not in apache2-common)

Your message dated Mon, 13 Nov 2006 22:39:41 +0100 with message-id <[EMAIL PROTECTED]> and subject line Some images packaged with apache-common not in apache2-common has caused 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#271504: marked as done (ksplash: black percentage indication on black background)

Your message dated Mon, 13 Nov 2006 22:38:13 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#271504: ksplash: black percentage indication on black background has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: closing 314421

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.22 > close 314421 1.42-1 Bug#314421: libdbd-pg-perl: Problem with placeholders in DBD::Pg 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in ve

Bug#283246: marked as done (Sarge-testing for Sparc, deselect, continious loop for zlib1g install)

Your message dated Mon, 13 Nov 2006 13:50:26 -0700 with message-id <[EMAIL PROTECTED]> and subject line continious loop for zlib1g install has caused the attached Bug report to be 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#392210: marked as done (ImportError: No module named SilverCity)

Your message dated Mon, 13 Nov 2006 21:49:53 +0100 with message-id <[EMAIL PROTECTED]> and subject line Closing the bug with the proper 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

Bug#398257: marked as done (logcheck-database: lots of "session opened" and "session closed" information)

Your message dated Mon, 13 Nov 2006 22:27:46 +0100 with message-id <[EMAIL PROTECTED]> and subject line this is caused by #391665 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsi

Bug#178079: marked as done (webalizer: Should know the new toplevel domains)

Your message dated Mon, 13 Nov 2006 18:53:08 -0200 with message-id <[EMAIL PROTECTED]> and subject line Bug solved since webalizer/2.01.10-31 has caused the attached Bug report to be 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

Processed: closing 376670

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.22 > # re-close, bts looks confuzzled > close 376670 1.1-3.2 Bug#376670: reseed: postinst failure when no HTTP proxy and ICMP is filtered 'close' is deprecated; see http://www.debian.org/B

Bug#398363: marked as done (php5: Missing default for "What would you like to do about php.ini?")

Your message dated Mon, 13 Nov 2006 11:52:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line [php-maint] Bug#398363: php5: Missing default for "What would you like to do about php.ini?" has caused the attached Bug report to be marked as done. This means that you claim that the problem

Bug#395269: marked as done (glipper: Please retain for future sessions)

Your message dated Mon, 13 Nov 2006 11:32:31 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#395269: fixed in glipper 0.95-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#397906: marked as done (ttf-tmuni: Add udeb for use in Bhutanese localized installer)

Your message dated Mon, 13 Nov 2006 11:41:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#397906: fixed in ttf-tmuni 0.0.20040806-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 i

Bug#397165: marked as done (xfonts-terminus: [INTL:ru] Russian debconf templates translation)

Your message dated Mon, 13 Nov 2006 11:18:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#397165: fixed in xfonts-terminus 4.20-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

Bug#316261: marked as done (links2 fails to display Japanese pages)

Your message dated Mon, 13 Nov 2006 11:32:57 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#316261: fixed in links2 2.1pre24-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#398023: marked as done (console-setup: French debconf templates translation update)

Your message dated Mon, 13 Nov 2006 11:02:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398023: fixed in console-setup 1.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 case it is now

Bug#396815: marked as done (console-setup: [INTL:de] German po-debconf translation)

Your message dated Mon, 13 Nov 2006 11:02:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396815: fixed in console-setup 1.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 case it is now

Bug#395470: marked as done (phpbb2: Users can not select gallery avatars)

Your message dated Mon, 13 Nov 2006 11:02:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#395470: fixed in phpbb2 2.0.21-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#306985: marked as done (akregator: crashes on startup after session end)

Your message dated Mon, 13 Nov 2006 19:09:29 + with message-id <[EMAIL PROTECTED]> and subject line Bug#306985: akregator: crashes on startup after session end has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#394286: marked as done (squirrelmail: Folders with many messages fail to deliver messages or index)

Your message dated Mon, 13 Nov 2006 10:47:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#394286: fixed in squirrelmail 2:1.4.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

Bug#377535: marked as done (pengupop: glibc free() with invalid pointer)

Your message dated Mon, 13 Nov 2006 10:47:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#377535: fixed in pengupop 2.1.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

Processed: closing 387191

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.22 > close 387191 Bug#387191: diff for 0.8.1a-1.1 NMU 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to "Steinar H. Gund

Bug#398415: marked as done (pengupop: FTBFS: image.c:18:18: error: zlib.h: No such file or directory)

H' undeclared (first use in this function) image.c:136: warning: implicit declaration of function 'inflateEnd' image.c:145: error: expected expression before ')' token image.c:162: error: expected expression before ')' token make[2]: *** [image.o] Error 1 make[2]: Leaving

Bug#398422: marked as done (php5-mysqli: broken dependencies: phpapi-20051025, php5-common (= 5.1.6-6))

Your message dated Mon, 13 Nov 2006 19:52:52 +0100 with message-id <[EMAIL PROTECTED]> and subject line [php-maint] Bug#398422: php5-mysqli: broken dependencies: phpapi-20051025, php5-common (= 5.1.6-6) has caused the attached Bug report to be marked as done. This means that you claim that the pr

Bug#398173: marked as done (squirrelmail: /etc/squirrelmail/apache.conf php_flag register_globals off error)

Your message dated Mon, 13 Nov 2006 10:47:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398173: fixed in squirrelmail 2:1.4.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

Bug#398040: marked as done (psyco: FTBFS: make: python2.5: Command not found)

Your message dated Mon, 13 Nov 2006 10:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398040: fixed in psyco 1.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 now your

Bug#398175: marked as done (Failed bootloader Installation)

Your message dated Mon, 13 Nov 2006 19:38:41 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#398175: Failed Boot Loader Installation has caused the attached Bug report to 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#395310: marked as done (inotify-tools_2.6-1(hppa/unstable): FTBFS: private inotify syscall definitions)

Your message dated Mon, 13 Nov 2006 10:32:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#395310: fixed in inotify-tools 3.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 no

Bug#398158: marked as done (PATCH: generic arch support)

Your message dated Mon, 13 Nov 2006 10:32:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398158: fixed in inotify-tools 3.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 no

Bug#398337: marked as done (emma: Impossible to create a new connection)

Your message dated Mon, 13 Nov 2006 10:17:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398337: fixed in emma 0.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 re

Bug#395367: marked as done (monodevelop: FTBFS: build-dep on missing package: stetic)

Your message dated Mon, 13 Nov 2006 19:28:37 +0100 with message-id <[EMAIL PROTECTED]> and subject line stetic_0.1.0~svn.64684-1_i386.changes ACCEPTED has caused the attached Bug report 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#393953: marked as done (xen-3.0: DomU sometimes crashes while booting)

Your message dated Mon, 13 Nov 2006 18:56:35 +0100 with message-id <[EMAIL PROTECTED]> and subject line xen-3.0: DomU sometimes crashes while booting has caused the attached Bug report 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#397701: marked as done (zeroc-icee-java: FTBFS: sablevm: cannot create vm)

Your message dated Mon, 13 Nov 2006 18:34:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line sablevm in a i386 chroot on amd64: works 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 i

Bug#340801: marked as done (uninstallable: Error: apache-ssl appears not to be installed)

Your message dated Mon, 13 Nov 2006 09:02:14 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#340801: fixed in libapache-mod-choke 0.06-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

Bug#395260: marked as done (sablevm: cannot create VM when run into a i386 chroot on a AMD64 system.)

Your message dated Mon, 13 Nov 2006 18:34:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line sablevm in a i386 chroot on amd64: works 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 i

Bug#398292: marked as done (GNU gv "ps_gettext()" Buffer Overflow Vulnerability (CVE-2006-5864))

Your message dated Mon, 13 Nov 2006 09:17:15 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#398292: fixed in gv 1:3.6.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 your

Bug#381785: marked as done ([INTL:pt] Portuguese translation for netenv (debconf))

Your message dated Mon, 13 Nov 2006 08:47:14 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#381785: fixed in netenv 0.94.3-18 has caused the attached Bug report to be 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#390060: marked as done (Spelling mistake in package description)

Your message dated Mon, 13 Nov 2006 08:47:14 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#390060: fixed in netenv 0.94.3-18 has caused the attached Bug report to be 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#388780: marked as done (netenv: purging the package fails (debconf unavailable))

Your message dated Mon, 13 Nov 2006 08:47:14 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#388780: fixed in netenv 0.94.3-18 has caused the attached Bug report to be 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#389394: marked as done (ITA: netenv -- Configure your system for different network environments)

Your message dated Mon, 13 Nov 2006 08:47:14 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#389394: fixed in netenv 0.94.3-18 has caused the attached Bug report to be 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#370006: marked as done (netenv: Cleanup of dependencies: stat)

Your message dated Mon, 13 Nov 2006 08:47:14 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#370006: fixed in netenv 0.94.3-18 has caused the attached Bug report to be 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#388944: marked as done (netenv: [annoying_notes] Abuse of debconf note(s))

Your message dated Mon, 13 Nov 2006 08:47:14 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#388944: fixed in netenv 0.94.3-18 has caused the attached Bug report to be 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#285159: marked as done (ITA: display-dhammapada -- Displays verses from the Dhammapada.)

Your message dated Mon, 13 Nov 2006 08:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#285159: fixed in display-dhammapada 0.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#359390: marked as done (display-dhammapada: please finish /usr/doc transition)

Your message dated Mon, 13 Nov 2006 08:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#359390: fixed in display-dhammapada 0.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#285157: marked as done (New Upstream Version of Display-dhammapada)

Your message dated Mon, 13 Nov 2006 08:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#285157: fixed in display-dhammapada 0.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#285156: marked as done ([NONFREE-DOC:UNMODIFIABLE] one included translation of the dhammapada is non-free)

Your message dated Mon, 13 Nov 2006 08:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#285156: fixed in display-dhammapada 0.23-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#397102: marked as done ([intl:fr] z88dk debconf template translation)

Your message dated Mon, 13 Nov 2006 07:32:12 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#397102: fixed in z88dk 1.6.ds1-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#396551: marked as done (ire-the-flat: crashes while loading)

Your message dated Mon, 13 Nov 2006 07:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396553: fixed in ire 0.92-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#395997: marked as done (z88dk: package long description has incorrect bulleted list)

Your message dated Mon, 13 Nov 2006 07:32:12 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#395997: fixed in z88dk 1.6.ds1-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#396551: marked as done (ire-the-flat: crashes while loading)

Your message dated Mon, 13 Nov 2006 07:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396551: fixed in ire 0.92-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

Processed (with 1 errors): (no subject)

Processing commands for [EMAIL PROTECTED]: > tags 397877 = pending Bug#397877: cdebconf-gtk-udeb: incorrect line selected as default in tree lists Tags were: patch Tags set to: pending > tags 340007 = patch Bug#340007: SELECT questions are not automatically scrolled to the active choice Tags were

Bug#396553: marked as done (ire-rotj: program crashes while loading)

Your message dated Mon, 13 Nov 2006 07:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396551: fixed in ire 0.92-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#353776: marked as done (ire: needs to remove 64-bit architectures from architecture list)

Your message dated Mon, 13 Nov 2006 07:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396551: fixed in ire 0.92-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#396551: marked as done (ire-the-flat: crashes while loading)

Your message dated Mon, 13 Nov 2006 07:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#353776: fixed in ire 0.92-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#353776: marked as done (ire: needs to remove 64-bit architectures from architecture list)

Your message dated Mon, 13 Nov 2006 07:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396553: fixed in ire 0.92-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   >