Bug#317930: marked as done (gtkguitune: Depends on uninstallable libsigc++0c102)

Your message dated Fri, 5 Aug 2005 07:46:05 +0200 with message-id <[EMAIL PROTECTED]> and subject line Recompiled package uploaded several days ago has caused the attached Bug report to 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#306330: marked as done (Updated russian cyrillic fonts)

Your message dated Fri, 5 Aug 2005 13:45:40 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug #306330: Updated russian cyrillic fonts has caused the attached Bug report to 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#321333: marked as done (O: cpio -- GNU cpio -- a program to manage archives of files.)

Your message dated Thu, 04 Aug 2005 21:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321333: fixed in cpio 2.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 your re

Bug#319028: marked as done (cpio: New upstream release)

Your message dated Thu, 04 Aug 2005 21:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319028: fixed in cpio 2.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 your re

Bug#320085: marked as done (still makes non-FHS /usr/doc links)

Your message dated Thu, 04 Aug 2005 21:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320085: fixed in cpio 2.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 your re

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

Your message dated Thu, 04 Aug 2005 21:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#311796: fixed in glide 2002.04.10-10 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#311797: marked as done (glide)

Your message dated Thu, 04 Aug 2005 21:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#311797: fixed in glide 2002.04.10-10 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

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

Your message dated Thu, 04 Aug 2005 21:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#310880: fixed in glide 2002.04.10-10 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#307035: marked as done ('man cpio' typos: "compatability" and "inadvertantly")

Your message dated Thu, 04 Aug 2005 21:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#307035: fixed in cpio 2.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 your re

Bug#297276: marked as done (glide: Don't change xterm title)

Your message dated Thu, 04 Aug 2005 21:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#297276: fixed in glide 2002.04.10-10 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#275116: marked as done (cpio: worth it to get the fresh version)

Your message dated Thu, 04 Aug 2005 21:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#275116: fixed in cpio 2.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 your re

Bug#253008: marked as done (XSIisms in postinst, preinst, prerm; violates policy 10.4)

Your message dated Thu, 04 Aug 2005 21:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#253008: fixed in cpio 2.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 your re

Bug#174470: marked as done (better description for cpio)

Your message dated Thu, 04 Aug 2005 21:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#174470: fixed in cpio 2.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 your re

Bug#165217: marked as done (cpio lacks large file support)

Your message dated Thu, 04 Aug 2005 21:02:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#165217: fixed in cpio 2.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 your re

Bug#170558: marked as done (cpio: Typo in mt manpage)

Your message dated Thu, 04 Aug 2005 21:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#170558: fixed in cpio 2.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 your re

Bug#223970: marked as done (Wrong spelling (chechdir) in rules file)

Your message dated Thu, 04 Aug 2005 21:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#223970: fixed in cpio 2.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 your re

Bug#256199: marked as done (XSI:isms in debian-scripts)

Your message dated Thu, 04 Aug 2005 21:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#256199: fixed in cpio 2.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 your re

Bug#320588: marked as done (glide: FTBFS [i386/gcc-4.0]: PIC register 'ebx' clobbered in 'asm')

Your message dated Thu, 04 Aug 2005 21:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320588: fixed in glide 2002.04.10-10 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#317695: marked as done (tagtool: Request to update version in unstable to 0.12.2)

Your message dated Thu, 04 Aug 2005 19:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#317695: fixed in tagtool 0.12.2-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

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

Your message dated Thu, 04 Aug 2005 19:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313901: fixed in tagtool 0.12.2-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#321202: marked as done (Uninstallable in sid due to C++ transition of libid3)

Your message dated Thu, 04 Aug 2005 18:32:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321202: fixed in grip 3.3.1-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#321352: marked as done (udev misses dependency on kernel-2.6.12)

Your message dated Fri, 5 Aug 2005 02:35:44 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#321352: udev misses dependency on kernel-2.6.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 cas

Bug#320140: marked as done (tor: ftbfs [sparc] ./bin/sh: line 1: 23352 Bus error src/or/test)

Your message dated Thu, 04 Aug 2005 17:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320140: fixed in tor 0.1.0.13-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#317731: marked as done (bins: [L10N:ca] Catalan translation)

Your message dated Thu, 04 Aug 2005 17:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#317731: fixed in bins 1.1.28-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#313798: marked as done (mail-notification: [INTL:de] German PO file corrections)

Your message dated Thu, 04 Aug 2005 17:32:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313798: fixed in mail-notification 1.1-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 i

Bug#308317: marked as done (please support customized date strings)

Your message dated Thu, 04 Aug 2005 17:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#308317: fixed in bins 1.1.28-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#308115: marked as done (man page doesn't list all supported template styles)

Your message dated Thu, 04 Aug 2005 17:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#308115: fixed in bins 1.1.28-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#313675: marked as done (bins: [INTL:de] German PO file corrections)

Your message dated Thu, 04 Aug 2005 17:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313675: fixed in bins 1.1.28-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#251306: marked as done (Possibility to install without bins-edit-gui (should be provided by different package))

Your message dated Thu, 04 Aug 2005 17:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#251306: fixed in bins 1.1.28-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#146234: marked as done (bins: would like option for ISO date format, or a customizable date format better yet)

Your message dated Thu, 04 Aug 2005 17:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#308317: fixed in bins 1.1.28-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#321214: marked as done (pts-tetex-cm-super: fails to install with teTeX 3.0)

Your message dated Thu, 04 Aug 2005 16:32:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321214: fixed in pts-tetex-cm-super 0.3.3-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 i

Bug#320895: marked as done (pts-tetex-cm-super fails on missing cm-super path point)

Your message dated Thu, 04 Aug 2005 16:32:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320895: fixed in pts-tetex-cm-super 0.3.3-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 i

Bug#307873: marked as done (mail-notification: prints out password in cleartext when invoked with the --report parameter)

Your message dated Thu, 4 Aug 2005 19:55:52 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#307873: mail-notification: prints out password in cleartext when invoked with the --report parameter has caused the attached Bug report to be marked as done. This means that you claim that t

Bug#303263: marked as done (gawk: symbol _dl_catch_error, version GLIBC_PRIVATE not defined...)

Your message dated Thu, 4 Aug 2005 16:37:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line fixed in binNMU has caused the attached Bug report to be 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#320944: marked as done (Things to improve on pts-tetex-cm-super)

Your message dated Thu, 04 Aug 2005 16:32:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320944: fixed in pts-tetex-cm-super 0.3.3-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 i

Bug#319556: marked as done (cln: inappropriate dependencies)

Your message dated Thu, 04 Aug 2005 15:32:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319556: fixed in cln 1.1.9-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 r

Bug#320040: marked as done (cln: FTBFS (ppc64): #error "Define cl_word_alignment for your CPU!")

Your message dated Thu, 04 Aug 2005 15:32:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320040: fixed in cln 1.1.9-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 r

Processed: close 316245

Processing commands for [EMAIL PROTECTED]: > close 316245 Bug#316245: tetex-bin: postinst failure while building etex and pdfetex formats 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Laurent Bonnaud <[EMAIL PROTECTED]> > tha

Bug#313578: marked as done (no reason to list the plugins in a shlibs file)

Your message dated Thu, 04 Aug 2005 15:18:57 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313578: fixed in libaqbanking 1.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 n

Bug#288433: marked as done (ITA: libcrypto++ -- Crypto++ library)

Your message dated Thu, 04 Aug 2005 15:21:30 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#288433: fixed in libcrypto++ 5.2.1c2-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#246912: marked as done (kdevelop: system hang forcing reboot on generating a project from existing automake file)

Your message dated Thu, 4 Aug 2005 23:17:28 +0100 with message-id <[EMAIL PROTECTED]> and subject line Old 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 responsibility to reope

Bug#286114: marked as done (libcrypto++-dev: compile warnings when using SHA256)

Your message dated Thu, 04 Aug 2005 15:21:30 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#286114: fixed in libcrypto++ 5.2.1c2-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#313581: marked as done (debian/rules clean does not clean)

Your message dated Thu, 04 Aug 2005 15:18:57 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313581: fixed in libaqbanking 1.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 n

Bug#316315: marked as done (ITP: gquilt -- PyGTK wrapper for quilt)

Your message dated Thu, 04 Aug 2005 15:09:43 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#316315: fixed in gquilt 0.12-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#317713: marked as done (ITP: libopenspc -- library for playing SPC files)

Your message dated Thu, 04 Aug 2005 15:15:36 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#317713: fixed in libopenspc 0.3.99a-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#318518: marked as done (libcrypto++: FTBFS: CryptoPP::FixedRounds<16u>:: is/uses an anonymous type)

Your message dated Thu, 04 Aug 2005 15:21:30 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#318518: fixed in libcrypto++ 5.2.1c2-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#321321: marked as done (Needs rebuilding for g++ transition)

Your message dated Thu, 04 Aug 2005 15:02:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321321: fixed in libmusicbrainz-ruby 0.2.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#321170: marked as done (cannot install pi through apt-get)

Your message dated Thu, 4 Aug 2005 23:30:36 +0200 (CEST) with message-id <[EMAIL PROTECTED]> and subject line cannot install pi through apt-get has caused the attached Bug report to be 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#321322: marked as done (cervisia: refuses to execute any cvs command with any repository)

Your message dated Thu, 4 Aug 2005 22:28:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line Touched rc file and it's working has caused the attached Bug report to be 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#321306: marked as done (cannot find the "ocaml-md5sums" file after apt-get upgrade)

Your message dated Thu, 4 Aug 2005 23:16:09 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#321306: cannot find the "ocaml-md5sums" file after apt-get upgrade 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#299216: marked as done (changes ~/.debconfrc handling loses functionality)

Your message dated Thu, 04 Aug 2005 13:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#299216: fixed in debconf 1.4.56 has caused the attached Bug report to be 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#293184: marked as done (lcov: geninfo fails on C++-headers)

Your message dated Thu, 04 Aug 2005 13:32:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#293184: fixed in lcov 1.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 your re

Bug#279754: marked as done (lintian: missing-depends-line test appears too general)

Your message dated Thu, 4 Aug 2005 22:49:49 +0200 with message-id <[EMAIL PROTECTED]> and subject line Override issue has caused the attached Bug report to be 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#274460: marked as done (consider packaging KMLDonkey)

Your message dated Thu, 4 Aug 2005 22:48:41 +0200 with message-id <[EMAIL PROTECTED]> and subject line consider packaging KMLDonkey has caused the attached Bug report to be 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#191253: marked as done ([checks/changelog-file] wrong-name-for-upstream-changelog is too strict)

Your message dated Thu, 4 Aug 2005 22:52:14 +0200 with message-id <[EMAIL PROTECTED]> and subject line Override issue has caused the attached Bug report to be 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#320762: marked as done (debconf: Arabic program translation)

Your message dated Thu, 04 Aug 2005 13:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320762: fixed in debconf 1.4.56 has caused the attached Bug report to be 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#321300: marked as done ("PortAudio: read interrupted" reading from ALSA device)

Your message dated Thu, 4 Aug 2005 23:00:58 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#321300: Acknowledgement ("PortAudio: read interrupted" reading from ALSA device) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been

Bug#318366: marked as done (FTBFS: Patch not found)

Your message dated Thu, 04 Aug 2005 13:17:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#318366: fixed in arj 3.10.22-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#319480: marked as done (newt: Xhosa translation)

Your message dated Thu, 04 Aug 2005 13:17:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319480: fixed in newt 0.51.6-29 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#60830: marked as done (gfpoken gives Gtk-CRITICAL error message)

Your message dated Thu, 04 Aug 2005 13:02:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#60830: fixed in gfpoken 0.25.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 n

Bug#321199: marked as done (snacc: ftbfs [sparc] configure.ac:183: error: possibly undefined macro: AC_PROG_LIBTOOL)

Your message dated Thu, 04 Aug 2005 13:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321199: fixed in snacc 1.3bbn-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 you

Bug#320889: marked as done (aalib transition)

Your message dated Thu, 04 Aug 2005 13:02:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320889: fixed in asc 1.16.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 you

Bug#314543: marked as done (gfpoken: Unable to play network games)

Your message dated Thu, 04 Aug 2005 13:02:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#314543: fixed in gfpoken 0.25.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#219061: marked as done (ITA: gfpoken -- Recreate a grid of mirrors from clues given by tests)

Your message dated Thu, 04 Aug 2005 13:02:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#219061: fixed in gfpoken 0.25.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#239752: marked as done (debian-installer: small typo in Norwegian translation)

Your message dated Thu, 4 Aug 2005 15:35:26 -0400 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 th

Bug#244440: marked as done (Don't make IDE and CD modules the default on all arches)

Your message dated Thu, 4 Aug 2005 15:19:05 -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

Bug#261780: marked as done (hw-detect.sh lists obsolete kernel modules)

Your message dated Thu, 4 Aug 2005 15:15:19 -0400 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 th

Bug#214500: marked as done (ddetect: FTBFS on powerpc: cc1: unknown C standard `c99')

Your message dated Thu, 4 Aug 2005 15:14:01 -0400 with message-id <[EMAIL PROTECTED]> and subject line closing old 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#250866: marked as done (ddetect: archdetect outputs the cpu type instead of the architecture)

Your message dated Thu, 4 Aug 2005 15:14:36 -0400 with message-id <[EMAIL PROTECTED]> and subject line closing old 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#309703: marked as done (reprepro: install changes file into pool?)

Your message dated Thu, 04 Aug 2005 11:32:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#309703: fixed in reprepro 0.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 you

Bug#265174: marked as done (installed riscstation kernel for netwinder)

Your message dated Thu, 4 Aug 2005 14:35:05 -0400 with message-id <[EMAIL PROTECTED]> and subject line closing old 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#240109: marked as done (install: Installer puts wrong kernel in boot partition [powerpc-newworld])

Your message dated Thu, 4 Aug 2005 14:35:23 -0400 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 th

Bug#240109: marked as done (install: Installer puts wrong kernel in boot partition [powerpc-newworld])

Your message dated Thu, 4 Aug 2005 19:36:15 +0100 with message-id <[EMAIL PROTECTED]> and subject line install: Installer puts wrong kernel in boot partition [powerpc-newworld] has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#305514: marked as done (libcgi-formbuilder-perl: New upstream source, please package)

Your message dated Thu, 04 Aug 2005 14:45:49 -0400 with message-id <[EMAIL PROTECTED]> and subject line libcgi-formbuilder-perl: New upstream source, please package has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#306982: marked as done (reprepro: Sample config to make a partial mirror for netinstall CD creation)

Your message dated Thu, 04 Aug 2005 11:32:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#306982: fixed in reprepro 0.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 you

Bug#309414: marked as done (reprepro: option to not delete old versions)

Your message dated Thu, 04 Aug 2005 11:32:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#309414: fixed in reprepro 0.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 you

Bug#319708: marked as done (how-to for apache2 support)

Your message dated Thu, 04 Aug 2005 11:32:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319708: fixed in reprepro 0.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 you

Bug#257594: marked as done (install powerpc SMP kernels if applicable (careful of breaking subarchitectures!))

Your message dated Thu, 4 Aug 2005 19:22:39 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#257478: installation-report: PowerMac G4 has caused the attached Bug report to 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#231653: marked as done (Reverts to http download even when ftp is selected)

Your message dated Thu, 4 Aug 2005 14:25:35 -0400 with message-id <[EMAIL PROTECTED]> and subject line seems 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 reope

Bug#320767: marked as done (hotplug: Arabic program translation)

Your message dated Thu, 04 Aug 2005 10:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320767: fixed in hotplug 0.0.20040329-25 has caused the attached Bug report 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#315776: marked as done (Wrong entry in etc/modprobe.d/isapnp)

Your message dated Thu, 04 Aug 2005 10:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#315776: fixed in hotplug 0.0.20040329-25 has caused the attached Bug report 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#313678: marked as done (ca-certificates: [INTL:de] German PO file corrections)

Your message dated Thu, 04 Aug 2005 10:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313678: fixed in ca-certificates 20050804 has caused the attached 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#290179: marked as done (Improper copyright file)

Your message dated Thu, 04 Aug 2005 10:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#290179: fixed in hotplug 0.0.20040329-25 has caused the attached Bug report 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#303383: marked as done (Please add net agent policy for ifupdown's "allow" mechanism)

Your message dated Thu, 04 Aug 2005 10:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#303383: fixed in hotplug 0.0.20040329-25 has caused the attached Bug report 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#309547: marked as done (ca-certificates: please update package description)

Your message dated Thu, 04 Aug 2005 10:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#309547: fixed in ca-certificates 20050804 has caused the attached 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#309588: marked as done (Speed tweak for 'default.hotplug': replace some 'sed' calls with shell substitutions)

Your message dated Thu, 04 Aug 2005 10:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#309588: fixed in hotplug 0.0.20040329-25 has caused the attached Bug report 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#313186: marked as done (INTL:vi)

Your message dated Thu, 04 Aug 2005 10:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313186: fixed in ca-certificates 20050804 has caused the attached 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#321097: marked as done (e16menuedit2 Recommendeds 'enligtenment' (typo))

Your message dated Thu, 4 Aug 2005 13:50:28 -0400 with message-id <[EMAIL PROTECTED]> and subject line 321097 already fixed, 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 resp

Bug#293029: marked as done (prc-tools-doc/index.html: proper reference)

Your message dated Thu, 04 Aug 2005 14:40:05 -0300 with message-id <[EMAIL PROTECTED]> and subject line prc-tools-doc/index.html: proper reference has caused the attached Bug report to 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#320018: marked as done (zope: [INTL:da] Updated Danish debconf template)

Your message dated Thu, 04 Aug 2005 10:17:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320018: fixed in zope 2.6.4-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#311848: marked as done ([l10n:de] Updated German translation of the debconf templates)

Your message dated Thu, 04 Aug 2005 10:17:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#311848: fixed in zope 2.6.4-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#269521: marked as done (zope: user IDs with '@' in them don't work)

Your message dated Thu, 04 Aug 2005 10:17:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#269521: fixed in zope 2.6.4-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#293554: marked as done (/etc/init.d/zope should really restart on restart)

Your message dated Thu, 04 Aug 2005 10:17:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#293554: fixed in zope 2.6.4-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

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

Your message dated Thu, 04 Aug 2005 10:02:19 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#317609: fixed in prc-tools 2.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 yo

Bug#314968: marked as done (prc-tools: README extension and move to real packages)

Your message dated Thu, 04 Aug 2005 10:02:19 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#314968: fixed in prc-tools 2.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 yo

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

Your message dated Thu, 04 Aug 2005 10:02:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#314132: fixed in dirmngr 0.9.2-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#308463: marked as done ([l10n] Initial Czech translation of prc-tools debconf messages)

Your message dated Thu, 04 Aug 2005 10:02:19 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#308463: fixed in prc-tools 2.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 yo

Bug#307159: marked as done (ITA: prc-tools -- GCC, GDB, binutils, etc. for PDAs using the PalmOS)

Your message dated Thu, 04 Aug 2005 10:02:19 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#307159: fixed in prc-tools 2.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 yo

Bug#293028: marked as done (prc-tools.html: "last modified on .")

Your message dated Thu, 04 Aug 2005 10:02:19 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#293028: fixed in prc-tools 2.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 yo

Bug#194932: marked as done (Adding libbfd.a bfd.h for easy Multilink building)

Your message dated Thu, 04 Aug 2005 10:02:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#194932: fixed in prc-tools 2.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 yo

  1   2   >