Bug#436901: marked as done (can't update mount in pbuilder chroot)

Your message dated Wed, 15 Aug 2007 00:47:16 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#436901: can't update mount in pbuilder chroot has caused the attached Bug 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#430326: marked as done (ldbl128 transition for alpha, powerpc, sparc, s390)

Your message dated Wed, 15 Aug 2007 00:49:07 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#430326: ldbl128 transition for alpha, powerpc, sparc, s390 has caused 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#436901: marked as done (can't update mount in pbuilder chroot)

Your message dated Wed, 15 Aug 2007 00:46:08 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#436901: can't update mount in pbuilder chroot has caused the attached Bug 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#334450: marked as done (libgnomeprint2.2-0: printing does not work with custom lpr command)

Your message dated Wed, 15 Aug 2007 08:41:46 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#334450: libgnomeprint2.2-0: printing does not work with custom lpr command has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt

Bug#437917: marked as done (ITP: audtty -- ncurses based frontend for audacious)

Your message dated Wed, 15 Aug 2007 06:50:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line dup has caused the attached Bug report to be 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 B

Bug#437937: marked as done (postfix: Shouldn't recommend mail-reader)

Your message dated Wed, 15 Aug 2007 03:17:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437938: fixed in postfix 2.4.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 yo

Bug#436269: marked as done (duplicate postmaster /etc/aliases entry if postfix/root_address used)

Your message dated Wed, 15 Aug 2007 03:17:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436269: fixed in postfix 2.4.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 yo

Bug#437937: marked as done (postfix: Shouldn't recommend mail-reader)

Your message dated Wed, 15 Aug 2007 03:17:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437937: fixed in postfix 2.4.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 yo

Bug#437938: marked as done (postfix: Shouldn't recommend mail-reader)

Your message dated Wed, 15 Aug 2007 03:17:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437937: fixed in postfix 2.4.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 yo

Bug#437938: marked as done (postfix: Shouldn't recommend mail-reader)

Your message dated Wed, 15 Aug 2007 03:17:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437938: fixed in postfix 2.4.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 yo

Bug#437965: marked as done (Samba cannot spell)

Your message dated Tue, 14 Aug 2007 19:12:27 -0700 with message-id <[EMAIL PROTECTED]> and subject line [Pkg-samba-maint] Bug#437965: Samba cannot spell has caused the attached Bug 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#437092: marked as done (update-manager: Depend on software-properties-gtk and remove software-properties from description)

Your message dated Wed, 15 Aug 2007 01:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437092: fixed in update-manager 0.68.debian-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

Bug#405353: marked as done (ocfs2-tools: Adding a node with o2cb_ctl fails with "Node number already exists")

Your message dated Wed, 15 Aug 2007 01:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#405353: fixed in ocfs2-tools 1.2.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#389916: marked as done (diff for 1.2.1-1.2 NMU)

Your message dated Wed, 15 Aug 2007 01:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#389916: fixed in ocfs2-tools 1.2.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#380879: marked as done (Python transition (#2): you are building a private python module !)

Your message dated Wed, 15 Aug 2007 01:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#380879: fixed in ocfs2-tools 1.2.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#436863: marked as done ([INTL:nl] Dutch po-debconf translation)

Your message dated Wed, 15 Aug 2007 01:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436863: fixed in ocfs2-tools 1.2.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#437705: marked as done (Gksu causes large amount of wakeups from idle w/tickless kernel)

Your message dated Tue, 14 Aug 2007 20:59:25 -0300 with message-id <[EMAIL PROTECTED]> and subject line bug fixed in newer 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 respons

Bug#433865: marked as done (update-manager: Reports updates are available, but cannot install chnages)

Your message dated Tue, 14 Aug 2007 20:56:01 -0300 with message-id <[EMAIL PROTECTED]> and subject line Fixed in newest version, according to user has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Processed: closing 437941

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > close 437941 Bug#437941: vmware-package: missing dependency for findutils 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explana

Bug#428447: marked as done (rcsdiff --unified option has no effect)

Your message dated Wed, 15 Aug 2007 00:52:08 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#428447: rcsdiff --unified option has no effect has caused the attached 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#437804: marked as done (libpri1.0: Fails to upgrade (overwrite error) and gratuitous name change?)

Your message dated Tue, 14 Aug 2007 22:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437804: fixed in libpri 1.4.1-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#434568: marked as done (libgphoto2: FTBFS on hurd-i386)

Your message dated Tue, 14 Aug 2007 22:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434568: fixed in libgphoto2 2.4.0-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#359186: marked as done (libpri: Does not build with -O)

Your message dated Tue, 14 Aug 2007 22:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#359186: fixed in libpri 1.4.1-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#379220: marked as done (Lincity-ng package is outdated - new version was released 3 months ago !)

Your message dated Wed, 15 Aug 2007 00:40:23 +0200 with message-id <[EMAIL PROTECTED]> and subject line Lincity-ng package is outdated - new version was released 3 months ago ! has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#437950: marked as done (sane-frontends: not handling nostrip build option (policy 10.1))

Your message dated Wed, 15 Aug 2007 00:18:02 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#437950: sane-frontends: not handling nostrip build option (policy 10.1) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wi

Bug#370412: marked as done (x11-common: /bin/ls: argument list too long)

Your message dated Wed, 15 Aug 2007 00:03:09 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#370412: x11-common: /bin/ls: argument list too long has caused the 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#436011: marked as done (apt-proxy: 'module' object has no attribute 'CPU')

Your message dated Tue, 14 Aug 2007 21:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436112: fixed in apt-proxy 1.9.36.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#436112: marked as done (apt-proxy: Failed to load application: /usr/lib/python2.4/site-packages/apt_pkg.so: undefined symbol: pkgCPU)

Your message dated Tue, 14 Aug 2007 21:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436011: fixed in apt-proxy 1.9.36.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#436011: marked as done (apt-proxy: 'module' object has no attribute 'CPU')

Your message dated Tue, 14 Aug 2007 21:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436011: fixed in apt-proxy 1.9.36.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#436112: marked as done (apt-proxy: Failed to load application: /usr/lib/python2.4/site-packages/apt_pkg.so: undefined symbol: pkgCPU)

Your message dated Tue, 14 Aug 2007 21:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436112: fixed in apt-proxy 1.9.36.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#436319: marked as done (apt-proxy: FTBFS: help2man: can't get `--help' info from ../bin/apt-proxy-import)

Your message dated Tue, 14 Aug 2007 21:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436011: fixed in apt-proxy 1.9.36.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#436319: marked as done (apt-proxy: FTBFS: help2man: can't get `--help' info from ../bin/apt-proxy-import)

Your message dated Tue, 14 Aug 2007 21:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436112: fixed in apt-proxy 1.9.36.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#436137: marked as done (apt-proxy: apt-ptoxy fails to start)

Your message dated Tue, 14 Aug 2007 21:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436011: fixed in apt-proxy 1.9.36.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#436137: marked as done (apt-proxy: apt-ptoxy fails to start)

Your message dated Tue, 14 Aug 2007 21:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436112: fixed in apt-proxy 1.9.36.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#437799: marked as done (slapd: ldapmodify wont work with NisNetgroupTriple)

Your message dated Tue, 14 Aug 2007 14:00:45 -0700 with message-id <[EMAIL PROTECTED]> and subject line [Pkg-openldap-devel] Bug#437799: Bug#437799: slapd: ldapmodify wont work with NisNetgroupTriple has caused the attached Bug report to be marked as done. This means that you claim that the probl

Bug#437815: marked as done (traceroute: don't drop alternatives ; should not conflict with others.)

Your message dated Tue, 14 Aug 2007 20:48:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437815: fixed in traceroute 2.0.7-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#428293: marked as done (file - CVE-2007-2799: incorrect patch for CVE-2007-1536)

Your message dated Tue, 14 Aug 2007 22:54:40 +0200 with message-id <[EMAIL PROTECTED]> and subject line file - CVE-2007-2799: incorrect patch for CVE-2007-1536 has caused the 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#436698: marked as done (traceroute breaks iputils-tracepath and ndisc6 packages)

Your message dated Tue, 14 Aug 2007 20:48:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436698: fixed in traceroute 2.0.7-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#394049: marked as done (DriveReady SeekComplete Error)

Your message dated Tue, 14 Aug 2007 22:35:40 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#394049: Problem identified has caused the attached Bug report to be 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#437361: marked as done (python-policyd-spf: spf policy check fails when RCPT TO entered twice)

Your message dated Tue, 14 Aug 2007 19:32:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437361: fixed in pypolicyd-spf 0.4.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#434623: marked as done (Fix README.Debian)

Your message dated Tue, 14 Aug 2007 19:32:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434623: fixed in pypolicyd-spf 0.4.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#437885: marked as done (rcs: not handling nostrip build option (policy 10.1))

Your message dated Tue, 14 Aug 2007 19:32:08 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437885: fixed in rcs 5.7-20 has caused the attached Bug report to be 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#428447: marked as done (rcsdiff --unified option has no effect)

Your message dated Tue, 14 Aug 2007 21:35:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#428447: rcsdiff --unified option has no effect has caused the attached 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

Processed: Close bug

Processing commands for [EMAIL PROTECTED]: > close 437913 Bug#437913: FATAL: Module cpufreq_performance not found. 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Alexander Morozov <[EMAIL PROTECTED]> > thanks Stopping process

Bug#436083: marked as done (Many undefined symbols, please build with -Wl and fix them)

Your message dated Tue, 14 Aug 2007 19:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436083: fixed in libvorbis 1.2.0.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#437863: marked as done (xbase-clients: Utilities sxpm and cxpm have been moved to package xpmutils)

Your message dated Tue, 14 Aug 2007 21:14:45 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#437863: xbase-clients: Utilities sxpm and cxpm have been moved to package xpmutils has caused the attached Bug report to be marked as done. This means that you claim that the problem has be

Bug#407781: marked as done (Couldn't find pixmap file: grsync.png)

Your message dated Tue, 14 Aug 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#407781: fixed in grsync 0.6-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#436334: marked as done (balder2d: FTBFS: unmet b-dep libguichan0-dev)

Your message dated Tue, 14 Aug 2007 18:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436334: fixed in balder2d 1.0~rc1-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#434039: marked as done (FTBFS: Incorrect version build-depends)

Your message dated Tue, 14 Aug 2007 18:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434039: fixed in balder2d 1.0~rc1-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#436577: marked as done (bbtime: not handling nostrip build option (policy 10.1) sid/i386)

Your message dated Tue, 14 Aug 2007 18:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436577: fixed in bbtime 0.1.5-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 yo

Processed: close

Processing commands for [EMAIL PROTECTED]: > close 436385 7.5.00.44-2 Bug#436385: maxdb-7.5.00: FTBFS: unmet b-dep libc6.1-dev 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 7.5.00.44-2, send any further explanations to Lucas Nussbaum <[EMA

Bug#433541: marked as done (emacs22: does not register with the "alternatives" name emacs)

Your message dated Tue, 14 Aug 2007 15:40:01 -0300 with message-id <[EMAIL PROTECTED]> and subject line Bug#433541: emacs22: does not register with the "alternatives" name emacs has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with

Bug#437752: marked as done (logcheck-database: ignore rules for postfix's reject_unknown_sender_domain)

Your message dated Tue, 14 Aug 2007 14:14:37 -0400 with message-id <[EMAIL PROTECTED]> and subject line logcheck-database: ignore rules for postfix's reject_unknown_sender_domain has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wit

Bug#430492: marked as done (pcscd: daemon freezes when USB reader inserted or removed)

Your message dated Tue, 14 Aug 2007 18:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#430492: fixed in pcsc-lite 1.4.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#255331: marked as done (kopete: Cannot connect onto a jabber server through SOCKS5)

Your message dated Tue, 14 Aug 2007 20:05:06 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#295582: About your bug 295582 "kopete: crashes when connecting through dante SOCKS proxy" in Debian BTS has caused the attached Bug report to be marked as done. This means that you claim th

Bug#295582: marked as done (kopete: crashes when connecting through dante SOCKS proxy)

Your message dated Tue, 14 Aug 2007 20:05:06 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#295582: About your bug 295582 "kopete: crashes when connecting through dante SOCKS proxy" in Debian BTS has caused the attached Bug report to be marked as done. This means that you claim th

Bug#272991: marked as done (Does not use socks in kde 3.3)

Your message dated Tue, 14 Aug 2007 20:05:06 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#295582: About your bug 295582 "kopete: crashes when connecting through dante SOCKS proxy" in Debian BTS has caused the attached Bug report to be marked as done. This means that you claim th

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

Your message dated Tue, 14 Aug 2007 17:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436956: fixed in bottlerocket 0.05b3-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

Bug#437550: marked as done (mailcheck: not handling nostrip build option (policy 10.1))

Your message dated Tue, 14 Aug 2007 17:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437550: fixed in mailcheck 1.91.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#437875: marked as done (gcc-4.2: missing critical C99 standard headers)

Your message dated Tue, 14 Aug 2007 19:23:47 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#437875: gcc-4.2: missing critical C99 standard headers has caused the 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#437875: marked as done (gcc-4.2: missing critical C99 standard headers)

Your message dated Tue, 14 Aug 2007 19:22:59 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#437875: gcc-4.2: missing critical C99 standard headers has caused the 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#428323: marked as done (libgempc430: Causes pcscd to segfault on startup)

Your message dated Tue, 14 Aug 2007 17:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#428323: fixed in ifd-gempc 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

Bug#432401: marked as done (gnunet-qt - FTBFS: error: gnunet-qt requires FSUI)

Your message dated Tue, 14 Aug 2007 16:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#432401: fixed in gnunet-qt 0.7.2+debian-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

Processed: Re: Thanks - that seems to have fixed the problem

Processing commands for [EMAIL PROTECTED]: > close 437797 2007-13 Bug#437797: Unable to install texlive-base-bin 2007-12, and texlive-base 2007-10 fmtutil-sys failed 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 2007-13, send any further e

Bug#29245: marked as done (slirp: SERIOUS problems on 64-bit machines)

Your message dated Tue, 14 Aug 2007 16:32:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#29245: fixed in slirp 1:1.0.17-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#358502: marked as done (snd_hda_intel needs position_fix=1 on my machine suddenly)

Your message dated Tue, 14 Aug 2007 18:23:02 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#358502: snd_hda_intel needs position_fix=1 on my machine suddenly 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#432483: marked as done (gnunet-gtk - FTBFS: configure: error: gnunet-gtk requires FSUI)

Your message dated Tue, 14 Aug 2007 16:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#432483: fixed in gnunet-gtk 0.7.2b-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#437834: marked as done (psi: not handling nostrip build option (policy 10.1))

Your message dated Tue, 14 Aug 2007 16:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437834: fixed in psi 0.10-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 re

Bug#368290: marked as done ('and' gets uid/gid wrongly on [Open]Mosix clusters)

Your message dated Tue, 14 Aug 2007 18:18:29 +0200 (CEST) with message-id <[EMAIL PROTECTED]> and subject line Fixed in Debian Stable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your resp

Bug#437834: marked as done (psi: not handling nostrip build option (policy 10.1))

Your message dated Tue, 14 Aug 2007 16:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437834: fixed in psi 0.11~rc2-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 you

Bug#359609: marked as done (zivot: please finish /usr/doc transition)

Your message dated Tue, 14 Aug 2007 15:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#359609: fixed in zivot 20013101-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#437850: marked as done (qca-tls: not handling nostrip build option (policy 10.1))

Your message dated Tue, 14 Aug 2007 15:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437850: fixed in qca-tls 1.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#392185: marked as done (zivot: please upgrade build-depends to gfortran from g77)

Your message dated Tue, 14 Aug 2007 15:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#392185: fixed in zivot 20013101-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#437849: marked as done (qca: not handling nostrip build option (policy 10.1))

Your message dated Tue, 14 Aug 2007 15:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437849: fixed in qca 1.0-9 has caused the attached Bug report to be 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#358502: marked as done (snd_hda_intel needs position_fix=1 on my machine suddenly)

Your message dated Tue, 14 Aug 2007 17:04:08 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#358502: snd_hda_intel needs position_fix=1 on my machine suddenly 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#436477: marked as done (newsbeuter: import opml file is not working)

Your message dated Tue, 14 Aug 2007 14:32:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436477: fixed in newsbeuter 0.6-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#434684: marked as done (gnunet-common: some dynamic libraries are missing)

Your message dated Tue, 14 Aug 2007 14:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#431021: fixed in gnunet 0.7.2b-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#431021: marked as done (gnunet-client: libgnunetidentify missing)

Your message dated Tue, 14 Aug 2007 14:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#431021: fixed in gnunet 0.7.2b-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#273771: marked as done (xdm: daemon can hang due to race condition in policy.c:Willing() when trying to run Xwilling sript)

Your message dated Tue, 14 Aug 2007 14:32:25 + with message-id <[EMAIL PROTECTED]> and subject line Bug#256299: fixed in xdm 1:1.1.5-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#382418: marked as done (xdm depends on wrong location)

Your message dated Tue, 14 Aug 2007 14:32:25 + with message-id <[EMAIL PROTECTED]> and subject line Bug#382418: fixed in xdm 1:1.1.5-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#427233: marked as done (xdm: Please turn on Xft support)

Your message dated Tue, 14 Aug 2007 14:32:25 + with message-id <[EMAIL PROTECTED]> and subject line Bug#427233: fixed in xdm 1:1.1.5-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#431021: marked as done (gnunet-client: libgnunetidentify missing)

Your message dated Tue, 14 Aug 2007 14:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434684: fixed in gnunet 0.7.2b-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#434684: marked as done (gnunet-common: some dynamic libraries are missing)

Your message dated Tue, 14 Aug 2007 14:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434684: fixed in gnunet 0.7.2b-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#256299: marked as done (xdm: race condition in policy.c:Willing())

Your message dated Tue, 14 Aug 2007 14:32:25 + with message-id <[EMAIL PROTECTED]> and subject line Bug#256299: fixed in xdm 1:1.1.5-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#301822: marked as done (small letters for the GNUNETD_HOME path.)

Your message dated Tue, 14 Aug 2007 14:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#301822: fixed in gnunet 0.7.2b-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#419143: marked as done (please use lsb init functions in /etc/init.d/xterm)

Your message dated Tue, 14 Aug 2007 14:32:25 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419143: fixed in xdm 1:1.1.5-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#435141: marked as done (aptitude: Continues downloading packages when disk is full)

Your message dated Tue, 14 Aug 2007 07:31:29 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#435064: aptitude: Continues downloading packages when disk is full 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#435064: marked as done (aptitude: Continues downloading packages when disk is full)

Your message dated Tue, 14 Aug 2007 07:31:29 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#435064: aptitude: Continues downloading packages when disk is full 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#435376: marked as done (wrong build due to changed dpkg-architecture output)

Your message dated Tue, 14 Aug 2007 14:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#435376: fixed in newt 0.52.2-11 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#437199: marked as done (ifstat: not handling nostrip build option (policy 10.1))

Your message dated Tue, 14 Aug 2007 14:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437199: fixed in ifstat 1.1-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#363957: marked as done (Spelling mistake in package description)

Your message dated Tue, 14 Aug 2007 14:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#363957: fixed in ifstat 1.1-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#298485: marked as done (Sound stops shortly after starting neverball)

Your message dated Tue, 14 Aug 2007 16:04:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#298485: Sound stops shortly after starting neverball has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#379597: marked as done (dpkg-cross: should read both site-wide and user-specific config file)

Your message dated Tue, 14 Aug 2007 14:46:55 +0100 with message-id <[EMAIL PROTECTED]> and subject line Closing has caused the attached Bug report to be 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 t

Bug#279778: marked as done (ITA: libcdk-perl -- Curses Development Kit for Perl)

Your message dated Tue, 14 Aug 2007 13:32:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#279778: fixed in libcdk-perl 4.9.10-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

Processed: (no subject)

Processing commands for [EMAIL PROTECTED]: > close 423927 Bug#423927: gnunet-gtk: Fails to start: symbol lookup error 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Darren Charette <[EMAIL PROTECTED]> > thanks Stopping process

Bug#431384: marked as done (gnunet: [INTL:fr] French debconf templates translation update)

Your message dated Tue, 14 Aug 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#431384: fixed in gnunet 0.7.2b-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#430802: marked as done (gnunet: General update after the debconf review process (the real one to use, please))

Your message dated Tue, 14 Aug 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#430802: fixed in gnunet 0.7.2b-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#434328: marked as done (blobwars: Typo in epilogue: weaponary)

Your message dated Tue, 14 Aug 2007 13:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434328: fixed in blobwars 1.07-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#436523: marked as done (/usr/bin/barcode: man page run together)

Your message dated Tue, 14 Aug 2007 12:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436523: fixed in barcode 0.98+debian-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#409734: marked as done (apcupsd doesn't send e-mail to root when commfailure occurs)

Your message dated Tue, 14 Aug 2007 12:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#409734: fixed in apcupsd 3.14.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 y

  1   2   >