Bug#184559: marked as done (libc6: missing files on sparc64)

Your message dated Sat, 31 Jul 2004 17:01:48 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug#184559: libc6: missing files on sparc64 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#257840: locales: Please add the eu_FR locale

At Mon, 19 Jul 2004 00:20:57 +0200, ^pi^ wrote: > > > At Tue, 06 Jul 2004 12:09:00 +0200, > > > Piarres Beobide Ega?a wrote: > > > > Here atached the proposal locales to eu_FR (basque in france). > > > > > > > > It is build from the existing eu_ES and fr_FR. > > > > > > Good. Piarres, are you u

Bug#254417: New locales proposed for South Africa

Hi, At Mon, 14 Jun 2004 18:25:38 +0200, Christian Perrier wrote: > Package: locales > Version: 2.3.2.ds1-13 > Severity: wishlist > Tags: patch > > South Africa uses 11 official languages. A few of these are currently > supported in locales while others aren't. > > Dwayne Bailey and people at tra

Bug#254417: New locales proposed for South Africa

Hi, At Mon, 14 Jun 2004 18:25:38 +0200, Christian Perrier wrote: > Package: locales > Version: 2.3.2.ds1-13 > Severity: wishlist > Tags: patch > > South Africa uses 11 official languages. A few of these are currently > supported in locales while others aren't. > > Dwayne Bailey and people at tra

cvs commit to glibc-package/debian by gotom

Repository: glibc-package/debian who:gotom time: Sat Jul 31 03:22:46 MDT 2004 Log Message: - debian/patches/locale-eu_FR.dpatch: Add eu_FR. Patched by Christian Perrier <[EMAIL PROTECTED]>. (Closes: #257840) - debian/patches/locale-sr_CS.dpatch: Add sr_CS and [EM

cvs commit to glibc-package/debian/patches by gotom

Repository: glibc-package/debian/patches who:gotom time: Sat Jul 31 03:22:46 MDT 2004 Log Message: - debian/patches/locale-eu_FR.dpatch: Add eu_FR. Patched by Christian Perrier <[EMAIL PROTECTED]>. (Closes: #257840) - debian/patches/locale-sr_CS.dpatch: Add sr_CS

Important Announcements.

Dear CheapSoft Customer, My name is Jorge Michael, and I work at CheapSoft LLC. You are important to me! You spend your money and time on CheapSoft, and I want to let you know that we have finished update our programs store. I want to remind you that we are offering now more than 1500 popular so

Bug#198997: marked as done (sed: Simple expression causes sed to dump core. Worked fine under woody.)

Your message dated Sat, 31 Jul 2004 14:52:54 +0200 with message-id <[EMAIL PROTECTED]> and subject line this is fixed (sed: Simple expression causes sed to dump core.) 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 i

cvs commit to linux-kernel-headers/debian by gotom

Repository: linux-kernel-headers/debian who:gotom time: Sat Jul 31 08:32:16 MDT 2004 Log Message: - Fix -ansi vs long long. (Closes: #252651) - asm-types-long-long.patch - Revert x86-64 modification in x86-64-long-long.patch because asm-types-long-long.p

cvs commit to linux-kernel-headers/debian/patches by gotom

Repository: linux-kernel-headers/debian/patches who:gotom time: Sat Jul 31 08:32:16 MDT 2004 Log Message: - Fix -ansi vs long long. (Closes: #252651) - asm-types-long-long.patch - Revert x86-64 modification in x86-64-long-long.patch because asm-types-lon

Bug#252651: linux-kernel-headers: syntax errors in file "/usr/include/linux/videodev2.h"

At Sun, 06 Jun 2004 05:30:23 +0900, GOTO Masanori wrote: > > -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 > ~ > > This is another -ansi things. I wonder why KDE guys want to use > -ansi because C99 is the new standard C these

Bug#252720: marked as done (linux-kernel-headers: Please also install the i386 linux kernel headers on amd64)

Your message dated Sat, 31 Jul 2004 10:47:08 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#252720: fixed in linux-kernel-headers 2.5.999-test7-bk-17 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

Bug#252651: marked as done (linux-kernel-headers: syntax errors in file "/usr/include/linux/videodev2.h")

Your message dated Sat, 31 Jul 2004 10:47:08 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#252651: fixed in linux-kernel-headers 2.5.999-test7-bk-17 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

Bug#256502: marked as done (debian/generate-asm.sh contains XSI:isms)

Your message dated Sat, 31 Jul 2004 10:47:08 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#256502: fixed in linux-kernel-headers 2.5.999-test7-bk-17 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

Bug#259766: marked as done (linux-kernel-headers - broken include/asm-s390/byteorder.h)

Your message dated Sat, 31 Jul 2004 10:47:08 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#259766: fixed in linux-kernel-headers 2.5.999-test7-bk-17 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

cvs commit to glibc-package/debian/patches by gotom

Repository: glibc-package/debian/patches who:gotom time: Sat Jul 31 09:33:10 MDT 2004 Log Message: disabled locale-sr_CS because it cannot be existed with sr_YU. Files: changed:00list -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble?

Bug#254993: Please add the sr_CS and sr_CS@cyrillic locales

At Fri, 18 Jun 2004 09:13:12 +0200, Christian Perrier wrote: > Package: locales > Version: 2.3.2.ds1-13 > Severity: wishlist > Tags: patch > > Attached are proposed locales for "Serbian in Serbia and Montenegro", both > latin and cyrillic variants. > > These were built from the existing sr_YU loc

cvs commit to glibc-package/debian/patches by gotom

Repository: glibc-package/debian/patches who:gotom time: Sat Jul 31 09:38:20 MDT 2004 Log Message: add [EMAIL PROTECTED] Files: changed:locale-eu_FR.dpatch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

cvs commit to glibc-package/debian by gotom

Repository: glibc-package/debian who:gotom time: Sat Jul 31 09:38:36 MDT 2004 Log Message: fix some changelog entries. Files: changed:changelog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#254417: New locales proposed for South Africa

At Sat, 31 Jul 2004 17:30:38 +0900, GOTO Masanori wrote: > BTW, I've put these files into 2.3.2.ds1-14. Thanks. I'm sorry, I mistook to send the old mail. I don't include it... Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [

Bug#235759: Bug#228486: More info about #228486 / #235759

[...] > What's the point of all this? First, the symbol on the keyboard does > not necessarily correspond with the character the user wants to use. > Second, the absence of a character on a keyboard does not indicate > that it is unimportant. Third, ASCII discriminates against proper > english typ

Bug#235759: More info about #228486 / #235759

[...] > My concern is to push what German > translators decided, I do not care whether this is in favor of > English quotes or guillemots. I'd like to add, that the decision taken by the German tranlation team is a pure consensus. It is not based on a majority vote. I've hardly seen any "discuss

Bug#261082: marked as done (glibc: Please add the '-fno-unit-at-a-time' patch from upstream for amd64/gcc-3.4 support)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#261082: fixed in glibc 2.3.2.ds1-14 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#259878: marked as done (libc6: posix timer SIGEV_THREAD notification broken)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#259878: fixed in glibc 2.3.2.ds1-14 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#251732: marked as done ([INTL:de] Updated po-file for german)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#251732: fixed in glibc 2.3.2.ds1-14 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#248192: marked as done (setpshared on amd64 not working?)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#248192: fixed in glibc 2.3.2.ds1-14 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#246547: marked as done (glibc: amd64 support is missing)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#246547: fixed in glibc 2.3.2.ds1-14 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#246270: marked as done (locales: byn_ER.UTF-8 cannot be generated)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#246270: fixed in glibc 2.3.2.ds1-14 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#239170: marked as done (getconf does not belong in the -dev package)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#239170: fixed in glibc 2.3.2.ds1-14 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#234691: marked as done (mkisofs: SIGBUS on sparc32 + sparc64)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#234691: fixed in glibc 2.3.2.ds1-14 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#253119: marked as done (Wrong exit status on start if nscd already running)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#229273: fixed in glibc 2.3.2.ds1-14 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#252284: marked as done (nscd: Initscript reload method fails)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#229273: fixed in glibc 2.3.2.ds1-14 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#213535: marked as done (vsftp service should be reset on NSS upgrade)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#213535: fixed in glibc 2.3.2.ds1-14 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#213159: marked as done (typo in tzconfig)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#213159: fixed in glibc 2.3.2.ds1-14 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#257840: marked as done (locales: Please add the eu_FR locale)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#257840: fixed in glibc 2.3.2.ds1-14 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#205084: marked as done (libc6: doesn't detects lpd (from lpr) as to be restarted)

Your message dated Sat, 31 Jul 2004 15:47:33 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#205084: fixed in glibc 2.3.2.ds1-14 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#245563: marked as done (libc6: causes errors on linux-2.6.5 with PaX and CONFIG_PAX_NOVSYSCALL)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#245563: fixed in glibc 2.3.2.ds1-14 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#193467: marked as done (libc6-dev: rpcgen man page: -M option not documented)

Your message dated Sat, 31 Jul 2004 15:47:33 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#193467: fixed in glibc 2.3.2.ds1-14 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#158651: marked as done (lire: Lire doesn't like crontab entries in syslog)

Your message dated Sat, 31 Jul 2004 15:47:33 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#158651: fixed in glibc 2.3.2.ds1-14 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#161340: marked as done (libc6: syslog(3) shouldn't use current locale to generate timestamp)

Your message dated Sat, 31 Jul 2004 15:47:33 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#158651: fixed in glibc 2.3.2.ds1-14 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#229484: marked as done (postinst fails when nscd already running)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#229273: fixed in glibc 2.3.2.ds1-14 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#222953: marked as done (libc6 did not restart nscd on upgrade)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#222953: fixed in glibc 2.3.2.ds1-14 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#189958: marked as done (libc6: iconv(1) manual page outdated)

Your message dated Sat, 31 Jul 2004 15:47:33 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#189958: fixed in glibc 2.3.2.ds1-14 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#193278: marked as done (libc6: When restarting, if one fails, rest isn't done)

Your message dated Sat, 31 Jul 2004 15:47:33 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#193278: fixed in glibc 2.3.2.ds1-14 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#208997: marked as done (libc6: apache-perl needs to be restarted)

Your message dated Sat, 31 Jul 2004 15:47:33 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#208997: fixed in glibc 2.3.2.ds1-14 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#219145: marked as done (libc6.1-dbg: should provide libc-dbg)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#219145: fixed in glibc 2.3.2.ds1-14 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#229273: marked as done (nscd cannot be purged when the daemon is stopped)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#229273: fixed in glibc 2.3.2.ds1-14 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#246170: marked as done (locales: no_NO ISO-8859-1 missing ?)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#246170: fixed in glibc 2.3.2.ds1-14 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#257658: marked as done (locales in testing: fails during compile of locales)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#257658: fixed in glibc 2.3.2.ds1-14 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#258956: marked as done (Starting sshd fails because of missing libutil.so.1 and libcrypt.so.1)

Your message dated Sat, 31 Jul 2004 15:47:34 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#258956: fixed in glibc 2.3.2.ds1-14 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

$B!Z3ZE7![%Z!<%8(BURL$B$N$*CN$i$;(B

$B3ZE7;T>l$G$9!#(B $B0J2<$N(BURL$B$r2!$9$H!"(BRAC$BHV9f(B801000$B$N%Z!<%8$K%"%/%;%9$G$-$^$9!#(B (B (Bhttp://m.rakuten.co.jp/bicymt (B($Bl9g$K$O!"$*l(B http://m.rakuten.co.jp/ (B(c)Rakuten (B (B (B-- (BTo UNSUBSCRIBE, email to [EMAIL PROTECTED] (Bwith a subject of "unsubscribe"