Bug#351469: empty program triggers valgrind, too

2007-12-04 Thread Uwe Kleine-König
Package: libc6 Version: 2.7-3 Followup-For: Bug #351469 Hello, I'm not sure if this should be a bug for itself or only a followup for #351469. I choosed the latter hoping for being less annoying :-) Using valgrind 3.2.3-3, I have: [EMAIL PROTECTED]:/tmp$ cat test.c int

Processed: Re: Bug#351469: empty program triggers valgrind, too

2007-12-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign 351469 valgrind Bug#351469: libc6: valgrind errs in getaddrinfo Bug reassigned from package `libc6' to `valgrind'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Bug#351469: empty program triggers valgrind, too

2007-12-04 Thread Pierre Habouzit
reassign 351469 valgrind thanks those are because the libc often uses things like: struct { char c; int i; }; then performs an action based on if (x-c) which in the CPU loads the full integer around c with its padding, and if the struct hasn't been fully memset'ed (including

Bug#454183: libc6: deadlock in syslog() after fork

2007-12-04 Thread Marc Donner
On Monday 03 December 2007, you wrote: Marc Donner a écrit : Package: libc6 Version: 2.5-7 Severity: important the syslog() funktion seems sometimes to end in a deadlock, if a multithreaded process, where are threads logging to syslog, at the same time does a fork() and the child

Processed: postinst - Segmentation fault

2007-12-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 453480 grave Bug#453480: postinst - Segmentation fault Severity set to `grave' from `important' found 453480 2.7-3 Bug#453480: postinst - Segmentation fault Bug marked as found in version 2.7-3. thanks Stopping processing here. Please

Bug#453480: postinst - Segmentation fault

2007-12-04 Thread Marcus Better
severity 453480 grave found 453480 2.7-3 thanks I just hit this problem (or maybe a similar one) when upgrading from 2.6.1-1+b1 - unfortunately in my case it rendered the system unusable. Any command now segfaults: ~# cat cat[1240]: segfault at eip esp bfac0dac error 4

Bug#453480: postinst - Segmentation fault

2007-12-04 Thread Marcus Better
Oh, and I'm not using a graphical frontend, but the dialog-based (the one with text-mode menus with block graphics). So maybe it's a different problem - leaving for maintainers to decide. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Marcus Better
retitle 454266 upgrade to 2.7 fails, leaving system unusable notfound 454266 2.7-2 thanks Aurelien Jarno wrote: This is clearly a differentl problem than the one that has been reported. Ok, cloning accordingly. What is the state of your system? Serious but stable :-) If you still have a

Processed: Re: Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: retitle 454266 upgrade to 2.7 fails, leaving system unusable Bug#454266: upgrade to 2.7 fails, leaving system unusable Changed Bug title to `upgrade to 2.7 fails, leaving system unusable' from `upgrade to 2.7 fails, leaving system unusable'. notfound

Processed: Re: Bug#453480: postinst - Segmentation fault

2007-12-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: clone 453480 -1 Bug#453480: postinst - Segmentation fault Bug 453480 cloned as bug 454266. severity 453480 important Bug#453480: postinst - Segmentation fault Severity set to `important' from `grave' notfound 453480 2.7-3 Bug#453480: postinst -

Bug#453480: postinst - Segmentation fault

2007-12-04 Thread Aurelien Jarno
Marcus Better a écrit : severity 453480 grave found 453480 2.7-3 thanks I just hit this problem (or maybe a similar one) when upgrading from 2.6.1-1+b1 - unfortunately in my case it rendered the system unusable. Any command now segfaults: ~# cat cat[1240]: segfault at eip

Processed: 92186

2007-12-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: clone 92186 -1 Bug#92186: libc6: getpwnam(3) should distinguish between NIS errors and user not found Bug 92186 cloned as bug 454262. reopen -1 Bug#454262: libc6: getpwnam(3) should distinguish between NIS errors and user not found Bug reopened,

Processed: Re: Processed (with 1 errors): your mail

2007-12-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: submitter 454266 ! Bug#454266: upgrade to 2.7 fails, leaving system unusable Changed Bug submitter from Emil Nowak [EMAIL PROTECTED] to Marcus Better [EMAIL PROTECTED]. End of message, stopping processing here. Please contact me if you need

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Marcus Better
Aurelien Jarno wrote: That looks ok. Which kernel are you using? 2.6.24-rc3 when it broke, but using 2.6.23 didn't help. Both are self-compiled. Marcus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Marcus Better
Pierre Habouzit wrote: Could you touch /etc/ld.so.nohwcap and see if it looks like that fixes your system ? Yes, that fixes it! Attempting the upgrade again makes the problem re-appear, and the upgrade fails with the following messages: Setting up libc6 (2.7-3) ... dpkg[3484]: segfault

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Aurelien Jarno
Marcus Better a écrit : retitle 454266 upgrade to 2.7 fails, leaving system unusable notfound 454266 2.7-2 thanks Aurelien Jarno wrote: This is clearly a differentl problem than the one that has been reported. Ok, cloning accordingly. What is the state of your system? Serious but

Bug#443202: Venezuelan changes not fixed in 2007h

2007-12-04 Thread José Miguel Parrella Romero
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 El 03/12/07 10:34, Aurelien Jarno escribió: The Venezuelan timezone change will happen on Dec 9, at 0300 UTC-0400, patches have been posted to [1], and will hopefully be released on tzdata2007j. ... I don't really understand. The timezone has

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Pierre Habouzit
On Tue, Dec 04, 2007 at 02:53:05PM +, Marcus Better wrote: Could you provide an md5sum (or any non too trivial checksum) of /lib/i686/cmov/libc.so.6 ? 76e00ba611b3bcb7827bd3f4e3b4930f /lib/i686/cmov/libc.so.6 this looks rotten, on a machine I have access to (an i386): $ dpkg -l

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Marcus Better
are you using pax execshield or anything like that ? No, not on this machine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Marcus Better
Could you provide an md5sum (or any non too trivial checksum) of /lib/i686/cmov/libc.so.6 ? 76e00ba611b3bcb7827bd3f4e3b4930f /lib/i686/cmov/libc.so.6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Pierre Habouzit
On Tue, Dec 04, 2007 at 12:57:14PM +, Marcus Better wrote: Pierre Habouzit wrote: Could you touch /etc/ld.so.nohwcap and see if it looks like that fixes your system ? Yes, that fixes it! okay so there is an issue with the optimized version of the library. touching /etc/ld.so.nohwcap

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Marcus Better
this looks rotten, on a machine I have access to (an i386): Seems the file is from version 2.6.1: ~$ md5sum /lib/i686/cmov/libc.so.6 76e00ba611b3bcb7827bd3f4e3b4930f /lib/i686/cmov/libc.so.6 ~$ ls -l /lib/i686/cmov/libc.so.6 lrwxrwxrwx 1 root root 13 2007-08-21 13:05 /lib/i686/cmov/libc.so.6

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Marcus Better
Should these files really be on my system if I don't have libc6-i686? ~$ ls /lib/i686/cmov/ ld-2.6.1.so libmemusage.so libnss_nis.so.2@ ld-linux.so.2@libm.so.6@ libpcprofile.so libanl-2.6.1.so libnsl-2.6.1.so libpthread-2.6.1.so

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Aurelien Jarno
Marcus Better a écrit : Should these files really be on my system if I don't have libc6-i686? ~$ ls /lib/i686/cmov/ ld-2.6.1.so libmemusage.so libnss_nis.so.2@ ld-linux.so.2@libm.so.6@ libpcprofile.so libanl-2.6.1.so

Bug#454266: marked as done (upgrade to 2.7 fails, leaving system unusable)

2007-12-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 Dec 2007 17:57:11 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#454266: upgrade to 2.7 fails, leaving system unusable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Aurelien Jarno
Marcus Better a écrit : this looks rotten, on a machine I have access to (an i386): Seems the file is from version 2.6.1: ~$ md5sum /lib/i686/cmov/libc.so.6 76e00ba611b3bcb7827bd3f4e3b4930f /lib/i686/cmov/libc.so.6 ~$ ls -l /lib/i686/cmov/libc.so.6 lrwxrwxrwx 1 root root 13 2007-08-21

Processed: asd

2007-12-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: #woops that was a mistake reopen 454266 Bug#454266: upgrade to 2.7 fails, leaving system unusable Bug reopened, originator not changed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Bug#454335: tzdata: [INTL:de] updated German debconf translation

2007-12-04 Thread Helge Kreutzmann
Package: tzdata Version: 2007j-1 Severity: wishlist Tags: patch l10n Please find the updated German debconf translation for tzdata attached. Please place this file in debian/po/ as de.po for your next upload. If you update your template, please use 'msgfmt --statistics pofile.po' to check the

[bts-link] source package glibc

2007-12-04 Thread bts-link-upstream
# # bts-link upstream status pull for source package glibc # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #453408 # * http://sourceware.org/bugzilla/show_bug.cgi?id=5441 # * remote status changed: (?) - NEW usertags

Bug#454266: strange cruft problem

2007-12-04 Thread Clint Adams
severity 454266 normal quit Downgrading this until it can be reproduced. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Processed: strange cruft problem

2007-12-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 454266 normal Bug#454266: upgrade to 2.7 fails, leaving system unusable Severity set to `normal' from `grave' quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator,

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread peter green
+++-==-==- un libc6-i686 none (no description available) The file comes from libc6-i686 version 2.6.1-1. According to the symlink it has been installed on 2007-08-21 (ie the date it migrates to testing). After a

Bug#454266: upgrade to 2.7 fails, leaving system unusable

2007-12-04 Thread Clint Adams
On Wed, Dec 05, 2007 at 03:03:51AM +, peter green wrote: This would seem to indicate that libc6-i686 was previously installed and being updated normally but at some point during or after the update to 2.6.1-1 it's entry in the dpkg status file completely dissapeared. Perhaps leaving