Bug#451939: libc6: Upgrading x86 chroot on ia64 dies with "cannot set up thread-local storage"

reassign 451939 linux-2.6 thanks Ian Wienand a écrit : > Thank you for your help on IRC > > As per > > http://www.gelato.unsw.edu.au/archives/linux-ia64/0711/21471.html > > I think this is a kernel bug. When it gets resolved I will close this > bug. > As it has been confirmed this is a kerne

Processed: Re: Bug#451939: libc6: Upgrading x86 chroot on ia64 dies with "cannot set up thread-local storage"

Processing commands for [EMAIL PROTECTED]: > reassign 451939 linux-2.6 Bug#451939: libc6: Upgrading x86 chroot on ia64 dies with "cannot set up thread-local storage" Bug reassigned from package `libc6' to `linux-2.6'. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#229251: marked as done (libc6.1: request ev67 specific build)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#229251: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#447928: marked as done ([INTL:gl] Galician debconf template translation for glibc)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#447928: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#443460: marked as done (deadlock during symbol resolving)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#443460: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#442568: marked as done (glibc: floor() is giving incorrect results on alpha architecture)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#442568: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#444580: marked as done ([PATCH] set correct WCHAR_MIN and WCHAR_MAX on armel port)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#444580: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#447328: marked as done (locales-all: aborted installation fills /tmp/ with leftover files)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#447328: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#448796: marked as done (libc6: provide compatibility script for tzconfig)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#448796: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#445631: marked as done ([Patch] getent: Please document exit codes in manpage)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#445631: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#448248: marked as done (Fixes for SH4 targets)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#448248: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#447866: marked as done (glibc: simplified chinese debconf translation)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#447866: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#442250: marked as done (CVE-2007-4840 multiple errors in iconv function)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#442250: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#448928: marked as done ([INTL:nl] Dutch po-debconf translation)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#448928: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#443660: marked as done (libc6: dgettext not thread-safe)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#443660: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#447221: marked as done (glibc: [l10n:ja] Incorrect encoding announced for Japanese debconf translation)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#447221: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#444145: marked as done (/usr/share/man/man8/ld.so.8.gz does not document the $ORIGIN, $PLATFORM and $LIB feature)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#444145: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#449193: marked as done (unclean purge)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#449193: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#449198: marked as done (FHS violation /var/db)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#449198: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#442247: marked as done (CVE-2007-4840 multiple errors in iconv function)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#442250: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#451304: marked as done (libc6: iconv(1) should document //translit and //ignore too)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#451304: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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#449005: marked as done (glibc_2.7-0exp7(alpha/experimental): FTBFS: ../sysdeps/generic/stdint.h:37: Error: syntax error)

Your message dated Wed, 21 Nov 2007 22:49:27 + with message-id <[EMAIL PROTECTED]> and subject line Bug#448508: fixed in glibc 2.7-0exp9 has caused the attached Bug report to be 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

glibc_2.7-0exp9_alpha.changes ACCEPTED

Accepted: glibc-doc_2.7-0exp9_all.deb to pool/main/g/glibc/glibc-doc_2.7-0exp9_all.deb glibc_2.7-0exp9.diff.gz to pool/main/g/glibc/glibc_2.7-0exp9.diff.gz glibc_2.7-0exp9.dsc to pool/main/g/glibc/glibc_2.7-0exp9.dsc libc6.1-alphaev67_2.7-0exp9_alpha.deb to pool/main/g/glibc/libc6.1-alphae

Bug#452275: tzdata: Cannot upgrade the package

Package: tzdata Version: 2007h-2 Severity: important Setting up tzdata (2007h-2) ... dpkg: error processing tzdata (--configure): subprocess post-installation script returned error exit status 10 Errors were encountered while processing: tzdata E: Sub-process /usr/bin/dpkg returned an error code

Processed: Re: Processed: Re: Bug#446443: texinfo: cannot build pdf documentation of glibc-doc-reference

Processing commands for [EMAIL PROTECTED]: > severity 452256 wishlist Bug#452256: ships own/old texinfo.tex, causing a build failure of pdf documentation Severity set to `wishlist' from `normal' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking sy

Bug#174190: cilicebm

We present you your new bigger PE maureus Hajee http://connectknew.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#446443: texinfo: cannot build pdf documentation of glibc-doc-reference

Processing commands for [EMAIL PROTECTED]: > clone 446443 -1 Bug#446443: texinfo: cannot build pdf documentation of glibc-doc-reference Bug 446443 cloned as bug 452256. > reassign -1 glibc-doc-reference Bug#452256: texinfo: cannot build pdf documentation of glibc-doc-reference Bug reassigned from

Bug#344563: nscd: confirmed

Package: nscd Version: 2.3.6.ds1-13etch2 Followup-For: Bug #344563 well yes: the "nscd: cache.c:335: prune_cache: Assertion `dh->usable' failed." bug still exists on current etch. actually it just re-occured; i haven't experienced it for a while. the only notable change on my side was that i did