Bug#174190: Photoshop, Windows, Office

Use addr: babloemka. com (remove space) in your browser Microsoft Windows Vista Ultimate $79 Macromedia Flash Professional 8$49 Adobe Premiere 2.0 $59 Corel Grafix Suite X3 $59 Adobe Il1ustrator CS2 $59 Adobe Photoshop CS2

Bug#448248: marked as done (Fixes for SH4 targets)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#448248: fixed in glibc 2.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#443460: marked as done (deadlock during symbol resolving)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#443460: fixed in glibc 2.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

Processed: closing 449192

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.11 > close 449192 2.7-1 Bug#449192: glibc - FTBFS: make: *** [clean] Error 1 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 2.7-1,

Bug#444580: marked as done ([PATCH] set correct WCHAR_MIN and WCHAR_MAX on armel port)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#444580: fixed in glibc 2.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#449198: marked as done (FHS violation /var/db)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#449198: fixed in glibc 2.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#442250: marked as done (CVE-2007-4840 multiple errors in iconv function)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#442250: fixed in glibc 2.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#447328: marked as done (locales-all: aborted installation fills /tmp/ with leftover files)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#447328: fixed in glibc 2.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#444145: marked as done (/usr/share/man/man8/ld.so.8.gz does not document the $ORIGIN, $PLATFORM and $LIB feature)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#444145: fixed in glibc 2.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#449193: marked as done (unclean purge)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#449193: fixed in glibc 2.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#445631: marked as done ([Patch] getent: Please document exit codes in manpage)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#445631: fixed in glibc 2.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#442568: marked as done (glibc: floor() is giving incorrect results on alpha architecture)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#442568: fixed in glibc 2.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#442247: marked as done (CVE-2007-4840 multiple errors in iconv function)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#442250: fixed in glibc 2.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#448723: marked as done (libc6: strtod("-0", 0) returns +0.0 instead of -0.0)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#448723: fixed in glibc 2.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#229251: marked as done (libc6.1: request ev67 specific build)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#229251: fixed in glibc 2.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#68606: censurav

Surprisingly low prices for stunning replicas only for the holiday period http://www.howaging.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#93810: irodosed

buy now for christmas and have some bling on your wrist http://hradams.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#452275: Debug data

Jonathan Rudenberg a écrit : > Here is some debug data: > > Setting up tzdata (2007h-2) ... > + LC_ALL=C > + LANG=C > + unset TZ > + umask 022 > + . /usr/share/debconf/confmodule > ++ '[' '!' '' ']' > ++ PERL_DL_NONLAZY=1 > ++ export PERL_DL_NONLAZY > ++ '[' '' ']' > ++ exec /usr/share/debconf/fro

r2693 - glibc-package/trunk/debian

Author: aurel32 Date: 2007-11-23 09:46:23 + (Fri, 23 Nov 2007) New Revision: 2693 Modified: glibc-package/trunk/debian/rules Log: Allow uploads to unstable again Modified: glibc-package/trunk/debian/rules === --- glibc-packag

Bug#451958: marked as done (libc6: ldconfig manpage mentions nonexistant -F/--force command line option)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#451958: fixed in glibc 2.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#447221: marked as done (glibc: [l10n:ja] Incorrect encoding announced for Japanese debconf translation)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#447221: fixed in glibc 2.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

r2694 - glibc-package/trunk/debian

Author: aurel32 Date: 2007-11-23 09:47:00 + (Fri, 23 Nov 2007) New Revision: 2694 Modified: glibc-package/trunk/debian/changelog Log: Prepare upload to unstable Modified: glibc-package/trunk/debian/changelog === --- glibc-pac

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

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#448928: fixed in glibc 2.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#447928: marked as done ([INTL:gl] Galician debconf template translation for glibc)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#447928: fixed in glibc 2.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#448796: marked as done (libc6: provide compatibility script for tzconfig)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#448796: fixed in glibc 2.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#447866: marked as done (glibc: simplified chinese debconf translation)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#447866: fixed in glibc 2.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#451304: marked as done (libc6: iconv(1) should document //translit and //ignore too)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#451304: fixed in glibc 2.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#443660: marked as done (libc6: dgettext not thread-safe)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#443660: fixed in glibc 2.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#449005: marked as done (glibc_2.7-0exp7(alpha/experimental): FTBFS: ../sysdeps/generic/stdint.h:37: Error: syntax error)

Your message dated Fri, 23 Nov 2007 19:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#448508: fixed in glibc 2.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