Bug#418058: iconv: half-smart on ascii compatible code conversion (shift-jis)

2007-06-15 Thread Osamu Aoki
tags 418058 - unreproducible retitle 418058 iconv: half-smart on ascii compatible code conversion (shift-jis) thanks Let me update with better data since original report was contaminated with other bugs such as groff. (Thanks Aurelien Jarno to checking them.) Bug: The \ and ~ (ascii 92 126)are no

Processed: Bug#418058: iconv: half-smart on ascii compatible code conversion (shift-jis)

2007-06-15 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 418058 - unreproducible Bug#418058: iconv: half-smart on ascii compatible code conversion (latin1, shift-jis, ...) Tags were: unreproducible Tags removed: unreproducible > retitle 418058 iconv: half-smart on ascii compatible code conversion > (s

Bug#429064: linux-libc-dev: conflicts with

2007-06-15 Thread Matej Vela
Bastian Blank <[EMAIL PROTECTED]> writes: >> linux-libc-dev should not directly export a kernel structure. Either >> remove it or use #ifdef __KERNEL__, but don't bother us with that. > > It is part of the userspace interface which is redefined in > bits/ustat.h. > > Anyway, it is no bug in the ke

Processed: Re: Bug#429064: linux-libc-dev: conflicts with

2007-06-15 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reopen 429064 Bug#429064: linux-libc-dev: conflicts with Bug reopened, originator not changed. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs databas

Bug#429064: linux-libc-dev: conflicts with

2007-06-15 Thread Jeroen van Wolffelaar
reopen 429064 thanks On Fri, Jun 15, 2007 at 09:22:12PM +0200, Aurelien Jarno wrote: > The glibc is correct here. If you don't want to get the bug assigned on > linux-2.6, then I am closing the bug. The reported problem does still exist, so closing this bug is shoving a real problem under the car

Bug#429064: marked as done (linux-libc-dev: conflicts with )

2007-06-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Jun 2007 21:22:12 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#429064: linux-libc-dev: conflicts with 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

Processed: Re: Bug#429064: linux-libc-dev: conflicts with

2007-06-15 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 429064 libc6-dev Bug#429064: linux-libc-dev: conflicts with Bug reassigned from package `linux-libc-dev' to `libc6-dev'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Processed: Re: Bug#429064: linux-libc-dev: conflicts with

2007-06-15 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 429064 linux-libc-dev Bug#429064: linux-libc-dev: conflicts with Bug reassigned from package `libc6-dev' to `linux-libc-dev'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administr

Processed: Re: Bug#429064: linux-libc-dev: conflicts with

2007-06-15 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 429064 libc6-dev Bug#429064: linux-libc-dev: conflicts with Bug reassigned from package `linux-libc-dev' to `libc6-dev'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

[m68k] missing __init_array_start, __init_array_end in __libc_csu_init

2007-06-15 Thread Stephen R Marenka
Please cc me. I saw 427990 for hppa and it made me question whether the following could be related for m68k? What do ya'll think? Thanks, Stephen - Forwarded message from Stephen R Marenka <[EMAIL PROTECTED]> - Old-Return-Path: <[EMAIL PROTECTED]> From: Stephen R Marenka <[EMAIL PROTE

Re: glibc 2.6, powerpc: compiler must support C cleanup handling

2007-06-15 Thread Jörg Sommer
Aurelien Jarno schrieb: > Jög Sommer a èrit : > > I would like to build the newest libc6 package for powerpc, but I get this: > > > > % CC=gcc-4.2 nice dpkg-buildpackage -rfakeroot -uc -nc > > CC= does not work the way you use it. This is probably the cause of your > problem. You have to add this

Bug#429021: libc6: fputs can lose data in buffer on signal

2007-06-15 Thread Pierre Habouzit
reopen 429021 thanks On Fri, Jun 15, 2007 at 12:33:40PM -0400, Daniel Jacobowitz wrote: > On Fri, Jun 15, 2007 at 06:09:42PM +0200, Pierre Habouzit wrote: > > The bug is here, you should set the flags to SA_RESTART so that > > interupted syscalls are restarted. If you don't do so you'll break th

Processed: Re: Bug#429021: libc6: fputs can lose data in buffer on signal

2007-06-15 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reopen 429021 Bug#429021: libc6: fputs can lose data in buffer on signal Bug reopened, originator not changed. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debia

Bug#429021: libc6: fputs can lose data in buffer on signal

2007-06-15 Thread Daniel Jacobowitz
On Fri, Jun 15, 2007 at 06:09:42PM +0200, Pierre Habouzit wrote: > The bug is here, you should set the flags to SA_RESTART so that > interupted syscalls are restarted. If you don't do so you'll break the > libio. Is this documented anywhere? The manual says that EINTR is treated as an ordinary

Processed: severity of 429021 is normal

2007-06-15 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > severity 429021 normal Bug#429021: libc6: fputs can lose data in buffer on signal Severity set to `normal' from `important' > End of message, stopping processing here. Please contac

Bug#429021: marked as done (libc6: fputs can lose data in buffer on signal)

2007-06-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Jun 2007 18:09:42 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#429021: libc6: fputs can lose data in buffer on signal 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#429021: libc6: fputs can lose data in buffer on signal

2007-06-15 Thread Dmitry Potapov
Package: libc6 Version: 2.3.6.ds1-13 Severity: important fputs (and probably other FILE based output functions) can lose previously written data that were accumulated in the user space buffer when a signal arrives. Here is an example that demonstrates the problem: # cat t.c /

Bug#428884: bashism in init script fails to start nscd

2007-06-15 Thread Thorsten Glaser
Pierre Habouzit dixit: >exists, so it's definitely a ksh only issue, and is not worth a stable >update. > > The fix will appear in the soon to be uploaded 2.6 packages though. That is okay, as mksh only offers to be used as /bin/sh via debconf in the package currently in unstable, and the other

Bug#428884: bashism in init script fails to start nscd

2007-06-15 Thread Pierre Habouzit
On Thu, Jun 14, 2007 at 10:08:30PM +, Thorsten Glaser wrote: > Package: nscd > Version: 2.3.6.ds1-8 > Severity: important > Tags: patch > > Hi, > > I've reported a similar bug to the sendmail-bin postinst script > some time ago, you'll find it at > | http://bugs.debian.org/cgi-bin/bugreport.c

r2367 - in glibc-package/branches/glibc-2.6/debian: . debhelper.in

2007-06-15 Thread madcoder
Author: madcoder Date: 2007-06-15 10:12:23 + (Fri, 15 Jun 2007) New Revision: 2367 Modified: glibc-package/branches/glibc-2.6/debian/changelog glibc-package/branches/glibc-2.6/debian/debhelper.in/nscd.init Log: Closes 428884 Signed-off-by: Pierre Habouzit <[EMAIL PROTECTED]> Modified:

Bug#425404: nscd: free's invalid pointer, causing calling program to abort

2007-06-15 Thread Raphael Hertzog
On Mon, 21 May 2007, Stephen Gran wrote: > #4 0x2ae2a514e21e in free () from /lib/libc.so.6 > No symbol table info available. > #5 0x2ae2a51d974a in nscd_getpw_r () from /lib/libc.so.6 > No symbol table info available. [...] > So it appears the breakage is in nscd. Let me know you if the