Bug#345868: marked as done (freecdb: must provide shared library or _pic library)

Your message dated Mon, 16 Jan 2006 23:32:03 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#345868: fixed in freecdb 0.75 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#340252: marked as done (Add 'upgrade' and 'failed-upgrade' to debian/libapache2-mod-fcgid.prerm)

Your message dated Tue, 17 Jan 2006 16:45:26 +0900 with message-id <[EMAIL PROTECTED]> and subject line These bugs ware fixed in 1.0.7-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#340128: marked as done (Patch to fix debian/rules dropping CFLAGS)

Your message dated Tue, 17 Jan 2006 16:45:26 +0900 with message-id <[EMAIL PROTECTED]> and subject line These bugs ware fixed in 1.0.7-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#307116: marked as done (freecdb_0.62.dsc: missing mandatory field `format'.)

Your message dated Mon, 16 Jan 2006 23:32:03 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#307116: fixed in freecdb 0.75 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

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

Your message dated Tue, 17 Jan 2006 16:45:26 +0900 with message-id <[EMAIL PROTECTED]> and subject line These bugs ware fixed in 1.0.7-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#334011: marked as done (Lower the requirement for libc6 >= 2.3.5 and locales >= 2.3.5 in version 1.4.6)

Your message dated Tue, 17 Jan 2006 16:45:26 +0900 with message-id <[EMAIL PROTECTED]> and subject line These bugs ware fixed in 1.0.7-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#272127: marked as done (ITA: freecdb -- creating and reading constant databases)

Your message dated Mon, 16 Jan 2006 23:32:03 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#272127: fixed in freecdb 0.75 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#124639: marked as done (freecdb: Spelling error in description)

Your message dated Mon, 16 Jan 2006 23:32:03 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#124639: fixed in freecdb 0.75 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#347232: marked as done (dash: empty eval may return failure exit status)

Your message dated Mon, 16 Jan 2006 23:17:04 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#347232: fixed in dash 0.5.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#315692: marked as done (/usr/lib/mozilla-firefox/firefox: download into false folder)

Your message dated Tue, 17 Jan 2006 01:19:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#315692: /usr/lib/mozilla-firefox/firefox: download into false folder has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#348211: marked as done (feedparser: FTBFS: Missing Build-Depends on 'python-dev')

Your message dated Mon, 16 Jan 2006 22:02:04 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#348211: fixed in feedparser 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 now y

Bug#348467: marked as done (RFA: tpconfig -- configure touchpad devices)

Your message dated Tue, 17 Jan 2006 00:35:41 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#348467: RFA: tpconfig -- configure touchpad devices has caused the 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#348462: marked as done (bzip2 1.0.3-1 is not installable, error in control file: `Index' value missing for type HTML at /usr/sbin/install-docs line 641)

Your message dated Tue, 17 Jan 2006 16:02:23 +1100 with message-id <[EMAIL PROTECTED]> and subject line Bug#348462: bzip2 1.0.3-1 is not installable, error in control file: `Index' value missing for type HTML at /usr/sbin/install-docs line 641 has caused the attached Bug report to be marked as don

Bug#318846: marked as done (browser (links is started) by apt-get upgrade but no directions on how to continue are given)

Your message dated Tue, 17 Jan 2006 00:10:53 -0500 with message-id <[EMAIL PROTECTED]> and subject line Not an apt 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 r

Bug#279611: marked as done (Missing Required Patches for 2.6.9 and 2.6.10)

Your message dated Mon, 16 Jan 2006 23:36:27 -0500 with message-id <[EMAIL PROTECTED]> and subject line Outdated has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen

Bug#348179: marked as done (f-spot: new upstream)

Your message dated Tue, 17 Jan 2006 17:23:43 +1300 with message-id <[EMAIL PROTECTED]> and subject line Bug#348179: f-spot: new upstream has caused the attached Bug report to be 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#344234: marked as done (nvidia-glx-legacy: trying to overwrite `/usr/lib/libGL.so.1', which is also in package xlibmesa-gl)

Your message dated Mon, 16 Jan 2006 23:19:44 -0500 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 th

Bug#315313: marked as done (nvidia-glx: Unnecessarily depends on libc6 2.3.5 on i386?)

Your message dated Mon, 16 Jan 2006 23:24:35 -0500 with message-id <[EMAIL PROTECTED]> and subject line Version tracking has caused the attached Bug report to be 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#347531: marked as done (/usr/X11R6/lib/X11/locale/compose.dir: compose not working if LC_CTYPE=cs_CZ.UTF-8)

Your message dated Mon, 16 Jan 2006 23:11:08 -0500 with message-id <[EMAIL PROTECTED]> and subject line Xorg 6.9.0.dfsg.1-4 really closed this bug after all has caused the attached 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#344102: marked as done (discover1-data: new e1000 devices)

Your message dated Tue, 17 Jan 2006 02:00:36 -0200 with message-id <[EMAIL PROTECTED]> and subject line Closed in last 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 responsibili

Bug#344101: marked as done (discover1-data: SAS1064 controller module map)

Your message dated Tue, 17 Jan 2006 02:00:36 -0200 with message-id <[EMAIL PROTECTED]> and subject line Closed in last 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 responsibili

Bug#325983: marked as done (g++: unmet deps)

Your message dated Mon, 16 Jan 2006 23:10:43 -0500 with message-id <[EMAIL PROTECTED]> and subject line Useless? has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen

Bug#348376: marked as done (libruby1.8: missing mathn)

Your message dated Tue, 17 Jan 2006 12:51:48 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug#348376: libruby1.8: missing mathn has caused the attached Bug report to be 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#341754: marked as done (nvidia-kernel-source: nvidia kernel module build with kernel source 2.6.14.3 fails to load)

Your message dated Mon, 16 Jan 2006 23:01:47 -0500 with message-id <[EMAIL PROTECTED]> and subject line Duplicate has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen

Bug#340056: marked as done (r5rs-doc: FTBFS: r5rs.txi missing)

Your message dated Mon, 16 Jan 2006 22:35:05 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#340056: can't reproduce has caused the attached Bug report to be 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#319008: marked as done (nvidia-kernel-source: No support for TNT/TNT2/GeForce 2)

Your message dated Mon, 16 Jan 2006 22:34:27 -0500 with message-id <[EMAIL PROTECTED]> and subject line Legacy packages should compensate has caused the attached Bug report to be 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: Block, close

Processing commands for [EMAIL PROTECTED]: > block 342545 by 348136 Bug#342545: qt-x11-free build fails Was not blocked by any bugs. Blocking bugs added: 348136 > close 338020 1.0.8174-1 Bug#338020: module-assistant: Nvidia module error under 2.6.14-amd64-smp 'close' is deprecated; see http://www

Bug#346692: marked as done (ircii-pana: FTBFS: build-depends on removed xlibs-dev)

Your message dated Mon, 16 Jan 2006 19:17:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#346692: fixed in ircii-pana 1:1.1-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#344606: marked as done (freeradius: clients.conf claims shared secret can be 32 chars but only 31 are accepted)

Your message dated Mon, 16 Jan 2006 19:17:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#344606: fixed in freeradius 1.1.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#343779: marked as done (Please upgrade build depends to libmysqlclient15-dev)

Your message dated Mon, 16 Jan 2006 19:17:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#343779: fixed in freeradius 1.1.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#335149: marked as done (freeradius-dialupadmin: Max Results aka pagesize always falls back to default value (10 results))

Your message dated Mon, 16 Jan 2006 19:17:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#335149: fixed in freeradius 1.1.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#333704: marked as done (freeradius-dialupadmin: php3 files must load config before using HTTP variables)

Your message dated Mon, 16 Jan 2006 19:17:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#333704: fixed in freeradius 1.1.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#348454: marked as done (apache*: default logrotate conf is overkill)

Your message dated Tue, 17 Jan 2006 14:05:04 +1100 with message-id <[EMAIL PROTECTED]> and subject line Bug#348454: apache*: default logrotate conf is overkill has caused the 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#347960: marked as done (bluefish: UTF-8 causes problems with fancy colouring)

Your message dated Mon, 16 Jan 2006 19:02:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#347960: fixed in bluefish 1.0.4-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#347334: marked as done (pearpc: 0.4.0 is out)

Your message dated Mon, 16 Jan 2006 18:47:04 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#347334: fixed in pearpc 0.4.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#344435: marked as done (Segmentation fault in gtk_widget_set_sensitive ())

Your message dated Mon, 16 Jan 2006 19:02:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#344435: fixed in bluefish 1.0.4-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#340768: marked as done (bluefish crashes using the spellcheck function)

Your message dated Mon, 16 Jan 2006 19:02:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#340768: fixed in bluefish 1.0.4-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#343706: marked as done (Same problems, Same brand.)

Your message dated Mon, 16 Jan 2006 22:14:46 -0500 with message-id <[EMAIL PROTECTED]> and subject line Invalid has caused the attached Bug report to be 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#333901: marked as done (Update build dependency for aalib1-dev -> libaa1-dev transition)

Your message dated Mon, 16 Jan 2006 18:47:04 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#333901: fixed in pearpc 0.4.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#300401: marked as done (pearpc: FTBFS (amd64/gcc-4.0): invalid lvalue in increment)

Your message dated Mon, 16 Jan 2006 18:47:04 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#300401: fixed in pearpc 0.4.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

Processed: New version in unstable

Processing commands for [EMAIL PROTECTED]: > close 301375 1.0.8174-1 Bug#301375: nvidia-kernel-source: Upstream patches available 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.0.8174-1, send any further explanations to Doug Larrick <[EMA

Bug#348452: marked as done ("ERROR: Unbound variable: hash-for-each" on startup since last update)

Your message dated Mon, 16 Jan 2006 17:52:32 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#348452: "ERROR: Unbound variable: hash-for-each" on startup since last update has caused the attached Bug report to be marked as done. This means that you claim that the problem has been de

Bug#345794: marked as done (nvidia-kernel-source: must build-depend on debhelper 5)

Your message dated Mon, 16 Jan 2006 21:13:36 -0500 with message-id <[EMAIL PROTECTED]> and subject line Invalid? has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen

Bug#332421: marked as done (Manual page refers to /usr/doc/multimon which isn't there)

Your message dated Mon, 16 Jan 2006 20:47:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line multimon-1.0-4 has new manpages has caused the attached Bug report to be 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#336754: marked as done (nvidia-glx provides 'libglx.so', which is also in package xserver-xorg in experimental)

Your message dated Mon, 16 Jan 2006 21:02:41 -0500 with message-id <[EMAIL PROTECTED]> and subject line Fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#321729: marked as done (nvidia-kernel conflicting with new libc6)

Your message dated Mon, 16 Jan 2006 20:54:12 -0500 with message-id <[EMAIL PROTECTED]> and subject line Should be 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

Bug#321624: marked as done (libao: please make libao a non-native Debian package)

Your message dated Mon, 16 Jan 2006 17:17:32 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#321624: fixed in libao 0.8.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#32263: marked as done ([PENDING AMENDMENT 20/01/2000] Splitting cgi-bin)

Your message dated Mon, 16 Jan 2006 17:26:01 -0700 with message-id <[EMAIL PROTECTED]> and subject line Read Carefully. has caused the attached Bug report to be 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#304421: marked as done (Change default driver to some reliable)

Your message dated Mon, 16 Jan 2006 17:17:32 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#304421: fixed in libao 0.8.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

Processed: Close

Processing commands for [EMAIL PROTECTED]: > close 252018 1.0.8174-1 Bug#252018: nvidia-kernel-2.4.25-1-k7: Fails to uninstall 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.0.8174-1, send any further explanations to Adam Majer <[EMAIL PR

Processed: closing 344060

Processing commands for [EMAIL PROTECTED]: > #expected behavior > close 344060 Bug#344060: /usr/bin/apt-get: Doesn't recognize need to update vulnerable kernel 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Tim Christian <[EMA

Bug#348429: marked as done (Corrupt /usr/share/doc-base/bzip2)

Your message dated Tue, 17 Jan 2006 11:58:27 +1100 with message-id <[EMAIL PROTECTED]> and subject line Corrupt /usr/share/doc-base/bzip2 has caused the attached Bug report to be 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#327251: marked as done (mozilla-firefox textarea segfault fix)

Your message dated Mon, 16 Jan 2006 20:00:26 -0500 with message-id <[EMAIL PROTECTED]> and subject line mozilla-firefox textarea segfault fix has caused the attached Bug report to be 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#347013: marked as done (multimon: FTBFS: build-depends on removed xlibs-dev)

Your message dated Mon, 16 Jan 2006 16:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#347013: fixed in multimon 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 you

Bug#347968: marked as done ([rejected] iptables: ipp2p match doesn't work)

Your message dated Mon, 16 Jan 2006 18:21:11 -0600 with message-id <[EMAIL PROTECTED]> and subject line iptables: ipp2p match doesn't work has caused the attached Bug report to be 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#235593: marked as done (libao2: fails to compile & doesn't work with Alsa 1.0 dshare plugin)

Your message dated Tue, 17 Jan 2006 01:13:26 +0100 with message-id <[EMAIL PROTECTED]> and subject line libao2: fails to compile & doesn't work with Alsa 1.0 dshare plugin 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#282540: marked as done (multimon: Cosmetic error in man page)

Your message dated Mon, 16 Jan 2006 16:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#282540: fixed in multimon 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 you

Bug#183190: marked as done (multimon: man page goose chase)

Your message dated Mon, 16 Jan 2006 16:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#183190: fixed in multimon 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 you

Bug#342709: marked as done (portmap: Portmap dies w/ SIGPIPE during heavy I/O)

Your message dated Mon, 16 Jan 2006 16:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#342709: fixed in portmap 5-17 has caused the attached Bug report to be 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#340158: marked as done (portmap: init script needlessly executed twice (and it informs the user about it too))

Your message dated Mon, 16 Jan 2006 16:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#340158: fixed in portmap 5-17 has caused the attached Bug report to be 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#334758: marked as done (portmap runs when it shouldn't)

Your message dated Mon, 16 Jan 2006 16:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#334758: fixed in portmap 5-17 has caused the attached Bug report to be 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#333125: marked as done (portmap: [INTL:sv] Swedish debconf templates translation)

Your message dated Mon, 16 Jan 2006 16:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#333125: fixed in portmap 5-17 has caused the attached Bug report to be 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#331350: marked as done (mooix: [INTL:sv] Swedish debconf templates translation)

Your message dated Mon, 16 Jan 2006 19:05:56 -0500 with message-id <[EMAIL PROTECTED]> and subject line mooix removal has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to re

Bug#326320: marked as done (please rebuild with libreadline5-dev as build dependency)

Your message dated Mon, 16 Jan 2006 19:05:56 -0500 with message-id <[EMAIL PROTECTED]> and subject line mooix removal has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to re

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

Your message dated Mon, 16 Jan 2006 19:05:56 -0500 with message-id <[EMAIL PROTECTED]> and subject line mooix removal has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to re

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

Your message dated Mon, 16 Jan 2006 19:05:56 -0500 with message-id <[EMAIL PROTECTED]> and subject line mooix removal has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to re

Bug#296497: marked as done (not suitable for debian release)

Your message dated Mon, 16 Jan 2006 19:05:56 -0500 with message-id <[EMAIL PROTECTED]> and subject line mooix removal has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to re

Processed: closing 319343

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.10 > # acknowledge this > close 319343 0.8.6-1.1 Bug#319343: libao: FTBFS: Missing Build-Depends on 'libxau-dev' 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. B

Bug#348289: marked as done (kmobiletools_0.4.3.1-4(ia64/unstable): FTBFS: build-depends libc6)

Your message dated Mon, 16 Jan 2006 15:02:17 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#348289: fixed in kmobiletools 0.4.3.1-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#348347: marked as done (gnome-control-center: should not depend solely on libgamin0 but also on libfam0)

Your message dated Mon, 16 Jan 2006 14:48:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#348347: fixed in control-center 1:2.12.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

Bug#348326: marked as done (compface: compface generates unjustified warnings)

Your message dated Mon, 16 Jan 2006 14:48:54 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#348326: fixed in libcompface 1:1.5.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

Bug#348247: marked as done (Broken dependency - uninstallable in sid.)

Your message dated Mon, 16 Jan 2006 14:49:42 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#348247: fixed in polygen 1.0.6.ds1-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#348235: marked as done (util-linux-locales: return of the pager alternatives problem)

Your message dated Mon, 16 Jan 2006 14:50:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#348235: fixed in util-linux 2.12r-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#348201: marked as done (cbrpager: [INTL:sv] Swedish PO translation)

Your message dated Mon, 16 Jan 2006 14:48:02 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#348201: fixed in cbrpager 0.9.14-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#348018: marked as done (gnucash: crash on startup)

Your message dated Mon, 16 Jan 2006 14:48:36 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#348018: fixed in gnucash 1.8.12-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 y

Bug#347758: marked as done (dh_python and current python policy doesn't match)

Your message dated Mon, 16 Jan 2006 15:02:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#347758: fixed in debhelper 5.0.17 has caused the attached Bug report to be 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#346878: marked as done (nessus-core: FTBFS: build-depends on removed xlibs-dev)

Your message dated Mon, 16 Jan 2006 14:49:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#346878: fixed in nessus-core 2.2.5-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#345220: marked as done (cl-uffi: FTBFS on GNU/kFreeBSD)

Your message dated Mon, 16 Jan 2006 14:48:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#345220: fixed in cl-uffi 1.5.8-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#345582: marked as done ([INTL: en_GB] Completed translation)

Your message dated Mon, 16 Jan 2006 14:47:47 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#345582: fixed in bonobo 1.0.22-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 yo

Bug#345219: marked as done (cl-sql: FTBFS on GNU/kFreeBSD)

Your message dated Mon, 16 Jan 2006 14:48:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#345219: fixed in cl-sql 3.5.3-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#343937: marked as done (libpdf-report-perl: barcode's don't scale)

Your message dated Mon, 16 Jan 2006 15:02:21 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#343937: fixed in libpdf-report-perl 1.30-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

Bug#342464: marked as done (postgrey: Add netsolmail.com to default whitelist)

Your message dated Mon, 16 Jan 2006 14:49:51 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#342464: fixed in postgrey 1.24-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#343487: marked as done (nessusd: cannot connect to 2.2.5-3 server)

Your message dated Mon, 16 Jan 2006 14:49:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#343487: fixed in nessus-core 2.2.5-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#333841: marked as done (/etc/init.d/bind9: /etc/init.d/bind9 force-reload acts in the wrong way (does restart, not reload))

Your message dated Mon, 16 Jan 2006 14:47:42 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#333841: fixed in bind9 1:9.3.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#343447: marked as done (util-linux: hwclock[first].sh must not exit)

Your message dated Mon, 16 Jan 2006 14:50:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#343447: fixed in util-linux 2.12r-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#335470: marked as done (libtest-inline-perl: New Upstream Release)

Your message dated Mon, 16 Jan 2006 14:49:15 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#335470: fixed in libtest-inline-perl 2.103-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#334430: marked as done (postgrey runs away with CPU in mad spin if ancillary database files are corrupted)

Your message dated Mon, 16 Jan 2006 14:49:51 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#334430: fixed in postgrey 1.24-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#322130: marked as done (util-linux: FTBFS (ppc64): Please support the ppc64 architecture)

Your message dated Mon, 16 Jan 2006 14:50:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#322130: fixed in util-linux 2.12r-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#331090: marked as done (/etc/init.d/bind9 states /etc/init.d/bind for usage information)

Your message dated Mon, 16 Jan 2006 14:47:42 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#331090: fixed in bind9 1:9.3.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#329990: marked as done (ITA: libtest-inline-perl -- Embed tests and code examples in POD)

Your message dated Mon, 16 Jan 2006 14:49:15 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#329990: fixed in libtest-inline-perl 2.103-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#318913: marked as done (postfix: old standards version)

Your message dated Mon, 16 Jan 2006 14:49:49 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#318913: fixed in postfix 2.2.8-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#320487: marked as done (postgrey: Please include privacy patch)

Your message dated Mon, 16 Jan 2006 14:49:51 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#320487: fixed in postgrey 1.24-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#315660: marked as done (mount: Wrong hash generation for the loopback device.)

Your message dated Mon, 16 Jan 2006 14:50:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#315660: fixed in util-linux 2.12r-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#275412: marked as done (/etc/init.d/bind9's call to resolvconf is sometimes unwanted)

Your message dated Mon, 16 Jan 2006 14:47:42 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#275412: fixed in bind9 1:9.3.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#313681: marked as done (bonobo: [INTL:de] German PO file corrections)

Your message dated Mon, 16 Jan 2006 14:47:47 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#313681: fixed in bonobo 1.0.22-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 yo

Bug#316244: marked as done (bind9: should not include 127.0.0.1 as nameserver in resolv.conf)

Your message dated Mon, 16 Jan 2006 14:47:42 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#275412: fixed in bind9 1:9.3.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#249755: marked as done (doesn't detect ext2 revision 0 file system)

Your message dated Mon, 16 Jan 2006 14:49:35 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#249755: fixed in partman-ext2r0 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

Bug#252232: marked as done (Please use 'lo.named' as resolvconf record name)

Your message dated Mon, 16 Jan 2006 14:47:42 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#252232: fixed in bind9 1:9.3.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#181078: marked as done (new sarge package: libtest-inline-perl)

Your message dated Mon, 16 Jan 2006 14:49:15 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#181078: fixed in libtest-inline-perl 2.103-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#194114: marked as done (libcapplet1 improperly linked)

Your message dated Mon, 16 Jan 2006 14:27:47 -0800 with message-id <[EMAIL PROTECTED]> and subject line hrm has caused the attached Bug report to be 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

  1   2   3   4   >