Bug#431579: marked as done (depends on non-essential binary /usr/sbin/update-gtk-immodules in postrm)

Your message dated Mon, 13 Aug 2007 06:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#431579: fixed in im-sdk 12.3.91-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#437485: marked as done (im-sdk: not binNMU safe)

Your message dated Mon, 13 Aug 2007 06:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437485: fixed in im-sdk 12.3.91-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#421645: marked as done (Please remove 31_pdftex_gcc_ICE-on-alpha)

Your message dated Mon, 13 Aug 2007 07:57:15 +0200 with message-id <[EMAIL PROTECTED]> and subject line Closing this 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

Bug#437431: marked as done (http://www.debian.org/Bugs/server-control: incorrect link to anchor )

Your message dated Sun, 12 Aug 2007 22:53:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#437431: http://www.debian.org/Bugs/server-control: incorrect link to anchor has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dea

Bug#437222: marked as done (asterisk: Depends on libpri1.0 >= 1.4, should this be libpri1.2 >= 1.4?)

Your message dated Mon, 13 Aug 2007 06:25:49 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fwd: libpri_1.4.1-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 is n

Bug#436252: marked as done (9wm: not handling nostrip build option (policy 10.1))

Your message dated Mon, 13 Aug 2007 05:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436252: fixed in 9wm 1.2-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

Processed: your mail

Processing commands for [EMAIL PROTECTED]: > close 353460 12.3.91-2 Bug#353460: im-sdk_12.3.91-0.1(hppa/experimental): FTBFS: typo in debian/control 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 12.3.91-2, send any further explanations to

Bug#419100: marked as done (Break timers just stand still)

Your message dated Mon, 13 Aug 2007 05:02:36 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419100: fixed in workrave 1.8.4-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#437525: marked as done (nfs-kernel-server: Kernel prints "RPC: failed to contact portmap (errno -5)")

Your message dated Mon, 13 Aug 2007 14:04:45 +1000 with message-id <[EMAIL PROTECTED]> and subject line Bug#437525: nfs-kernel-server: Kernel prints "RPC: failed to contact portmap (errno -5)" has caused the attached Bug report to be marked as done. This means that you claim that the problem has

Bug#437522: marked as done (moreutils: 'sponge' is non-absorbent)

Your message dated Sun, 12 Aug 2007 23:20:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#437522: moreutils: 'sponge' is non-absorbent has caused the attached Bug 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#304306: marked as done (boa: please provide httpd-cgi)

Your message dated Sun, 12 Aug 2007 23:16:41 -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 reo

Bug#266583: marked as done (boa: should provide httpd-cgi)

Your message dated Sun, 12 Aug 2007 23:16:41 -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 reo

Bug#336677: marked as done (boa: [INTL:sv] Swedish debconf templates translation)

Your message dated Sun, 12 Aug 2007 23:16:51 -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 reo

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

Your message dated Sun, 12 Aug 2007 23:16:03 -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 reo

Bug#334663: marked as done (dwww: README suggests 'boa', which contradicts 'Depends'.)

Your message dated Sun, 12 Aug 2007 23:15:40 -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 reo

Bug#304306: marked as done (boa: please provide httpd-cgi)

Your message dated Sun, 12 Aug 2007 23:15:40 -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 reo

Bug#297021: marked as done (boa: French program translation)

Your message dated Sun, 12 Aug 2007 23:15:52 -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 reo

Bug#304306: marked as done (boa: please provide httpd-cgi)

Your message dated Sun, 12 Aug 2007 23:16:11 -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 reo

Bug#266583: marked as done (boa: should provide httpd-cgi)

Your message dated Sun, 12 Aug 2007 23:16:11 -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 reo

Bug#334663: marked as done (dwww: README suggests 'boa', which contradicts 'Depends'.)

Your message dated Sun, 12 Aug 2007 23:16:41 -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 reo

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

Your message dated Sun, 12 Aug 2007 23:15:27 -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 reo

Bug#334663: marked as done (dwww: README suggests 'boa', which contradicts 'Depends'.)

Your message dated Sun, 12 Aug 2007 23:16:11 -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 reo

Bug#333892: marked as done (boa: Spanish debconf translation)

Your message dated Sun, 12 Aug 2007 23:16:30 -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 reo

Bug#266583: marked as done (boa: should provide httpd-cgi)

Your message dated Sun, 12 Aug 2007 23:15:40 -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 reo

Bug#309107: marked as done ([INTL:nl] new Dutch po-debconf translation)

Your message dated Sun, 12 Aug 2007 23:16:21 -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 reo

Bug#331764: marked as done (boa depends on debconf without | debconf-2.0 alternate; blocks cdebconf transition)

Your message dated Sun, 12 Aug 2007 23:09:02 -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 reo

Bug#178794: marked as done (boa post-installation fails (hostname))

Your message dated Sun, 12 Aug 2007 22:27:21 -0400 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

Processed: Re: Bug#437519: Acknowledgement (udev: foo)

Processing commands for [EMAIL PROTECTED]: > close 437519 Bug#437519: udev: foo 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Frédéric Brière <[EMAIL PROTECTED]> > thanks Stopping processing here. Please contact me if yo

Bug#435573: marked as done (openmpi-bin: libibverbs only available for Linux)

Your message dated Mon, 13 Aug 2007 01:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#435573: fixed in openmpi 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 yo

Bug#435759: marked as done (hdapsd: please update to new hdapsd.c)

Your message dated Mon, 13 Aug 2007 00:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#435759: fixed in hdapsd 1:0.0.20070803-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 i

Bug#431959: marked as done (nvidia-kernel-legacy-96xx-2.6.18-4-amd64: spelling mistake in provides field)

Your message dated Sun, 12 Aug 2007 23:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#431959: fixed in nvidia-graphics-legacy-96xx-modules-amd64 1.0.9639+2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with

Bug#242736: marked as done (netkit-inetd: warning in the manual)

Your message dated Mon, 13 Aug 2007 01:49:30 +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 reo

Bug#437501: marked as done (sprng: not binNMU safe)

Your message dated Sun, 12 Aug 2007 23:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437501: fixed in sprng 2.0a-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#437000: marked as done (util-linux 2.13~rc3-3 breaks aptitude)

Your message dated Sun, 12 Aug 2007 16:57:46 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#437000: util-linux 2.13~rc3-3 breaks aptitude has caused the attached Bug 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#436984: marked as done (giftrans: not handling nostrip build option (policy 10.1))

Your message dated Sun, 12 Aug 2007 22:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436984: fixed in giftrans 1.12.2-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

Bug#382167: marked as done (doc-linux-es: sysutils -> tofrodos)

Your message dated Sun, 12 Aug 2007 22:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#382167: fixed in doc-linux-es 2003.04-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

Bug#436060: marked as done (New Upstream for libmtp (release 0.2.0))

Your message dated Sun, 12 Aug 2007 22:30:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436060: fixed in libmtp 0.2.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 you

Bug#389260: marked as done (icu: please apply patch to avoid unnecessary linkage with libpthread)

Your message dated Sun, 12 Aug 2007 22:21:49 + with message-id <[EMAIL PROTECTED]> and subject line Bug#389260: fixed in icu 3.8~d01-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#384276: marked as done (netatalk does not start if there are no interfaces available)

Your message dated Sun, 12 Aug 2007 22:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#384276: fixed in netatalk 2.0.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 now y

Bug#420020: marked as done (nut: Include ability to send option flags to upsd)

Your message dated Sun, 12 Aug 2007 22:15:20 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420020: fixed in nut 2.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#430730: marked as done (ITP: oggconvert -- convert media files to free formats)

Your message dated Sun, 12 Aug 2007 22:14:26 + with message-id <[EMAIL PROTECTED]> and subject line Bug#430730: fixed in oggconvert 0.2.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#432971: marked as done (linux-image-2.6.21-2-686: Hangs at boot before "Begin: Waiting for root filesystem" message)

Your message dated Sun, 12 Aug 2007 23:02:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#432650: Sigh... has caused the attached Bug report to be 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#432817: marked as done (Harddisc changed from /dev/hda to sda from 2.6.18)

Your message dated Sun, 12 Aug 2007 23:02:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#432650: Sigh... has caused the attached Bug report to be 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#437331: marked as done (libxine1: please add wavpack support)

Your message dated Sun, 12 Aug 2007 22:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437331: fixed in xine-lib 1.1.7-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#432650: marked as done (2.6.21-2: cannot grab IDE ports, hangs on boot)

Your message dated Sun, 12 Aug 2007 23:02:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#432650: Sigh... has caused the attached Bug report to be 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#427982: marked as done (libxine1: useless dependency : libdirectfb)

Your message dated Sun, 12 Aug 2007 22:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#427982: fixed in xine-lib 1.1.7-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#432815: marked as done (IDE ports already in use... probe skipped!)

Your message dated Sun, 12 Aug 2007 23:02:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#432650: Sigh... has caused the attached Bug report to be 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#425851: marked as done (linux-image-2.6.21-1-686: 2.6.21 doesn't find HDD in VMware Workstation (2.6.20 did))

Your message dated Sun, 12 Aug 2007 23:02:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#432650: Sigh... has caused the attached Bug report to be 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#426033: marked as done (nut-usb: /lib/nut/newhidups is leaking memory)

Your message dated Sun, 12 Aug 2007 22:15:20 + with message-id <[EMAIL PROTECTED]> and subject line Bug#426033: fixed in nut 2.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#432909: marked as done (nut: New Upstream Release Available)

Your message dated Sun, 12 Aug 2007 22:15:20 + with message-id <[EMAIL PROTECTED]> and subject line Bug#432909: fixed in nut 2.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#435590: marked as done (Abusive recommends on libxine1-doc)

Your message dated Sun, 12 Aug 2007 22:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#435590: fixed in xine-lib 1.1.7-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#415189: marked as done (nut: [INTL:pt] Portuguese translation for debconf messages)

Your message dated Sun, 12 Aug 2007 22:15:20 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415189: fixed in nut 2.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#385694: marked as done (nut: Fails to properly start on boot.)

Your message dated Sun, 12 Aug 2007 22:15:20 + with message-id <[EMAIL PROTECTED]> and subject line Bug#385694: fixed in nut 2.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#432919: marked as done (short description indicates that libxine1-doc is a development package)

Your message dated Sun, 12 Aug 2007 22:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#432919: fixed in xine-lib 1.1.7-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#416077: marked as done (libxine1: Enable Freetype support)

Your message dated Sun, 12 Aug 2007 22:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#416077: fixed in xine-lib 1.1.7-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#414756: marked as done ([INTL:nl] Dutch po-debconf translation)

Your message dated Sun, 12 Aug 2007 22:15:20 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414756: fixed in nut 2.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#434503: marked as done (nut: /etc/default/nut can not set starting arguments)

Your message dated Sun, 12 Aug 2007 22:15:20 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434503: fixed in nut 2.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#420016: marked as done (nut and old version of nut-usb)

Your message dated Sun, 12 Aug 2007 22:15:20 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420016: fixed in nut 2.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#288703: marked as done (ITP: chmsee -- A chm file viewer, support Chinese better)

Your message dated Sun, 12 Aug 2007 22:09:24 + with message-id <[EMAIL PROTECTED]> and subject line Bug#288703: fixed in chmsee 1.0.0~beta2-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#430864: marked as done (xdialog kun gtk2)

Your message dated Sun, 12 Aug 2007 22:11:38 + with message-id <[EMAIL PROTECTED]> and subject line Bug#430864: fixed in xdialog 2.3.1.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 case it is

Bug#409563: marked as done (ITP: thinkfinger -- library and utility for the SGS Thomson Microelectronics fingerprint reader)

Your message dated Sun, 12 Aug 2007 22:06:44 + with message-id <[EMAIL PROTECTED]> and subject line Bug#409563: fixed in thinkfinger 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#433844: marked as done (ITP: empty -- Run processes and applications under pseudo-terminal)

Your message dated Sun, 12 Aug 2007 22:01:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#433844: fixed in empty-expect 0.6.11b-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#386103: marked as done (ITP: ehcache -- distributed cache library)

Your message dated Sun, 12 Aug 2007 21:37:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#386103: fixed in ehcache 1.3.0~beta.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 case

Bug#422601: marked as done (ITP: jsr107cache -- Java API for caching)

Your message dated Sun, 12 Aug 2007 21:28:37 + with message-id <[EMAIL PROTECTED]> and subject line Bug#422601: fixed in jsr107cache 1.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 case it

Bug#430836: marked as done (python-pygresql: Missing dependency on libpq4)

Your message dated Sun, 12 Aug 2007 21:12:33 + with message-id <[EMAIL PROTECTED]> and subject line Bug#430836: fixed in pygresql 1:3.8.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

Bug#434525: marked as done (ITP: swing-layout -- Extensions to Swing layout)

Your message dated Sun, 12 Aug 2007 21:11:49 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434525: fixed in swing-layout 1.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 n

Bug#425597: marked as done (No compatible libapache-mod-php5 for 5.2.2-2)

Your message dated Sun, 12 Aug 2007 14:13:53 -0700 with message-id <[EMAIL PROTECTED]> and subject line [php-maint] Bug#425597: (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 yo

Bug#421101: marked as done (python-sqlalchemy: Error with pydoc)

Your message dated Sun, 12 Aug 2007 21:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#421101: fixed in sqlalchemy 0.4.0~beta1-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#430594: marked as done (ITP: open-invaders -- a GPLed Space Invaders clone)

Your message dated Sun, 12 Aug 2007 21:00:54 + with message-id <[EMAIL PROTECTED]> and subject line Bug#430594: fixed in open-invaders 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 no

Bug#317983: marked as done (ITP: gdc -- D programming language for GCC)

c++6-4.1-pic - The GNU Standard C++ Library v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-branch 200708

Bug#408888: marked as done (gcj-4.1: FTBFS on GNU/Hurd)

1-dev - The GNU Standard C++ Library v3 (development files) libstdc++6-4.1-doc - The GNU Standard C++ Library v3 (documentation files) libstdc++6-4.1-pic - The GNU Standard C++ Library v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 42

Bug#433539: marked as done (gcc-4.1: profiling support on hurd)

433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-branch 20070812. . * Period of grace is over, turn on again the testsuite on m68k. * Update infrastructure for the gcc-source package (Bastian Blank). * Update profiling on the Hur

Bug#312367: marked as done (ITP: gdc -- D programming language for GCC)

ary v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-branch 20070812. . * Period of grace is over, t

Bug#403460: marked as done (ITP: gdc -- D programming language for GCC)

files) libstdc++6-4.1-pic - The GNU Standard C++ Library v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-br

Bug#317983: marked as done (ITP: gdc -- D programming language for GCC)

c++6-4.1-pic - The GNU Standard C++ Library v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-branch 200708

Bug#312367: marked as done (ITP: gdc -- D programming language for GCC)

ary v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-branch 20070812. . * Period of grace is over, t

Bug#403460: marked as done (ITP: gdc -- D programming language for GCC)

files) libstdc++6-4.1-pic - The GNU Standard C++ Library v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-br

Bug#317983: marked as done (ITP: gdc -- D programming language for GCC)

c++6-4.1-pic - The GNU Standard C++ Library v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-branch 200708

Bug#423160: marked as done (gij-4.1: bug in EnumMap implementation)

3 (documentation files) libstdc++6-4.1-pic - The GNU Standard C++ Library v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update

Bug#434090: marked as done (ITP: libmetadata-extractor-java -- JPEG metadata extraction framework)

Your message dated Sun, 12 Aug 2007 20:54:00 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434090: fixed in libmetadata-extractor-java 2.3.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 th

Bug#423094: marked as done (Binary without manpage: gappletviewer-4.1)

elang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-branch 20070812. . * Period of grace is over, turn on again the testsuite on m68k.

Bug#403460: marked as done (ITP: gdc -- D programming language for GCC)

files) libstdc++6-4.1-pic - The GNU Standard C++ Library v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-br

Bug#312367: marked as done (ITP: gdc -- D programming language for GCC)

ary v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-branch 20070812. . * Period of grace is over, t

Bug#422469: marked as done (gjdoc: upgrade fails with "invalid pointer" when /proc not mounted)

Library v3 (shared library subset kit) treelang-4.1 - The GNU Treelang compiler Closes: 312367 317983 403460 40 422469 423094 423160 433539 Changes: gcc-4.1 (4.1.2-15) unstable; urgency=low . [Matthias Klose] * Update to the gcc-4_1-branch 20070812. . * Period of grace is over, t

Bug#431006: marked as done (console-log: launches the first pager entry only)

Your message dated Sun, 12 Aug 2007 20:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#431006: fixed in console-log 1.0-14 has caused the attached Bug report to be 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#437205: marked as done (deluge-torrent: package 0.5.4.1 - new release )

Your message dated Sun, 12 Aug 2007 20:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437205: fixed in deluge-torrent 0.5.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

Bug#436839: marked as done (Package deluge 0.5.4)

Your message dated Sun, 12 Aug 2007 20:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436839: fixed in deluge-torrent 0.5.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

Bug#435464: marked as done (deluge-torrent: browser wont launch)

Your message dated Sun, 12 Aug 2007 20:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#435464: fixed in deluge-torrent 0.5.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

Bug#424523: marked as done (libgd-gd2-perl: FTBFS if built twice in a row)

Your message dated Sun, 12 Aug 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#424523: fixed in libgd-gd2-perl 1:2.35-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 i

Bug#412181: marked as done (ngrep version 1.45 is available since 11/18/06)

Your message dated Sun, 12 Aug 2007 19:32:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412181: fixed in ngrep 1.45.ds1-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#437250: marked as done (kadu: not handling nostrip build option (policy 10.1))

Your message dated Sun, 12 Aug 2007 19:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437250: fixed in kadu 0.5.0-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#436865: marked as done ([INTL:nl] Dutch po-debconf translation)

Your message dated Sun, 12 Aug 2007 19:02:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436865: fixed in workman 1.3.4-28 has caused the attached Bug report to be 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#434027: marked as done (partman-crypto: loop-aes fails with "not supported by kernel")

Your message dated Sun, 12 Aug 2007 18:47:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434027: fixed in partman-crypto 22 has caused the attached Bug report to be 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#436842: marked as done (floater: not handling nostrip build option (policy 10.1))

Your message dated Sun, 12 Aug 2007 18:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436842: fixed in floater 1.4.15-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#424513: marked as done (libgd-gd2-noxpm-perl: FTBFS if built twice in a row)

Your message dated Sun, 12 Aug 2007 18:17:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#424513: fixed in libgd-gd2-noxpm-perl 1:2.35-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 cas

Bug#434261: marked as done ("the the interface" in extended description)

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

Bug#399797: marked as done (cduce: Typos in package description)

Your message dated Sun, 12 Aug 2007 18:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#399797: fixed in cduce 0.5.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#419892: marked as done (cduce_0.4.1-1+b1(ia64/unstable): FTBFS: SEGV runing ./cduce)

Your message dated Sun, 12 Aug 2007 18:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419892: fixed in cduce 0.5.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#395024: marked as done (Bug with encrypted swap)

Your message dated Sun, 12 Aug 2007 19:54:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#395024: Bug with encrypted swap has caused the attached Bug report to be 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#435361: marked as done (Detects way too much RAM on an x86_64 box)

Your message dated Sun, 12 Aug 2007 17:47:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#435361: fixed in linuxinfo 1.1.8-23 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

  1   2   >