Repository: glibc-package/debian/patches
who:jbailey
time: Fri Jul 18 02:44:02 MDT 2003
Log Message:
- debian/patches/syslog-backrev.dpatch: New file
Files:
changed:0list
added: syslog-backrev.dpatch
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject o
Repository: glibc-package/debian
who:jbailey
time: Fri Jul 18 02:44:01 MDT 2003
Log Message:
- debian/patches/syslog-backrev.dpatch: New file
Files:
changed:changelog
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAI
I have uploaded 2.3.2-1 in experimental. If you're going to build it on
an arch for testing, please email here (and/or update the /topic on irc)
Tks,
Jeff Bailey
--
Breathe into my hands, I'll cup them like a glass to drink from...
- Tattle Tale
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
glibc_2.3.2-1_i386.changes uploaded successfully to localhost
along with the files:
glibc_2.3.2-1.dsc
glibc_2.3.2.orig.tar.gz
glibc_2.3.2-1.diff.gz
libc6_2.3.2-1_i386.deb
libc-udeb_2.3.2-1_i386.udeb
libc6-dev_2.3.2-1_i386.deb
libc6-prof_2.3.2-1_i386.deb
libc6-dbg_2.3.2-1_i386.deb
There are disparities between your recently accepted upload and the
override file for the following file(s):
libc6-dbg_2.3.2-1_i386.deb: package says section is devel, override says libdevel.
libc6-pic_2.3.2-1_i386.deb: package says section is devel, override says libdevel.
libc6-prof_2.3.2-1_i386
Accepted:
glibc-doc_2.3.2-1_all.deb
to pool/main/g/glibc/glibc-doc_2.3.2-1_all.deb
glibc_2.3.2-1.diff.gz
to pool/main/g/glibc/glibc_2.3.2-1.diff.gz
glibc_2.3.2-1.dsc
to pool/main/g/glibc/glibc_2.3.2-1.dsc
glibc_2.3.2.orig.tar.gz
to pool/main/g/glibc/glibc_2.3.2.orig.tar.gz
libc-udeb_2.3.2-
Your message dated Fri, 18 Jul 2003 05:17:47 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#199134: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:47 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#194791: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:46 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#193331: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:46 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#193327: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191295: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#188159: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#188159: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#188159: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#187475: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#186654: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#185924: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#189854: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#185648: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#181701: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#173963: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#189879: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#171695: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#188159: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#160040: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#186210: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#164638: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#183694: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#158410: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#182654: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#140788: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#115536: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#184696: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#167564: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#108619: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#106254: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#117509: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#137020: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#153548: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#140788: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#157142: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#157142: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#164719: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#166979: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#171022: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#182654: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#181910: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#185342: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:47 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#200386: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#185342: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:46 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#192577: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#185649: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:46 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#192096: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#187621: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#190322: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#188159: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#188383: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#189792: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#190785: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191785: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191952: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:47 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#193656: fixed in glibc 2.3.2-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
Repository: glibc-package/debian/patches
who:gotom
time: Fri Jul 18 09:48:46 MDT 2003
Log Message:
- make 2.3.2-2 entry
- glibc23-arm-waitpid.dpatch: Fix arm ld-linux failure due to sys_waitpid
missing. Patched by Philip Blundell <[EMAIL PROTECTED]>
Files:
change
Repository: glibc-package/debian
who:gotom
time: Fri Jul 18 09:48:46 MDT 2003
Log Message:
- make 2.3.2-2 entry
- glibc23-arm-waitpid.dpatch: Fix arm ld-linux failure due to sys_waitpid
missing. Patched by Philip Blundell <[EMAIL PROTECTED]>
Files:
changed:ch
Keld Jørn Simonsen writes:
> I think SIS - Sewdish Institute for Standardisation is also a preferable
> source for Swedish Language, and especially when it comes to computers.
You know what they say about standards: The nice thing about standards
is that there are so many of them to choose from.
Mikael Hedin writes:
> Anyway, should not d_t_fmt, t_fmt and date_fmt use the same format?
Yes, obviously.
> IFAICT the last one uses colons today, but the formet two uses full
> stop. And what are their respective uses? I guess the answer is
> buried in the sources, but anyway...
While d_t_fm
Accepted:
libc-udeb_2.3.2-1_powerpc.udeb
to pool/main/g/glibc/libc-udeb_2.3.2-1_powerpc.udeb
libc6-dbg_2.3.2-1_powerpc.deb
to pool/main/g/glibc/libc6-dbg_2.3.2-1_powerpc.deb
libc6-dev_2.3.2-1_powerpc.deb
to pool/main/g/glibc/libc6-dev_2.3.2-1_powerpc.deb
libc6-pic_2.3.2-1_powerpc.deb
to po
On Fri, Jul 18, 2003 at 07:46:05PM +0200, Göran Uddeborg wrote:
> Keld Jørn Simonsen writes:
> > I think SIS - Sewdish Institute for Standardisation is also a preferable
> > source for Swedish Language, and especially when it comes to computers.
>
> You know what they say about standards: The nice
Keld Jørn Simonsen writes:
> What I meant is that the specific standards overrules the more
> general standards. The specification from SIS is directly addressed
> towards POSIX locales, which is what we are talking about here,
> while Svenska Språknämnden is more generic.
Ok, I follow you now.
>
Package: glibc-doc
Version: 2.3.1-16
Severity: normal
rcmd/rcmd_af needs to be documented.
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux gondolin 2.4.21-2-686-smp #1 SMP Sat Jul 5 01:42:22 EST 2003
i686 GNU/Linux
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
Repository: glibc-package/debian/patches
who:jbailey
time: Fri Jul 18 02:44:02 MDT 2003
Log Message:
- debian/patches/syslog-backrev.dpatch: New file
Files:
changed:0list
added: syslog-backrev.dpatch
Repository: glibc-package/debian
who:jbailey
time: Fri Jul 18 02:44:01 MDT 2003
Log Message:
- debian/patches/syslog-backrev.dpatch: New file
Files:
changed:changelog
I have uploaded 2.3.2-1 in experimental. If you're going to build it on
an arch for testing, please email here (and/or update the /topic on irc)
Tks,
Jeff Bailey
--
Breathe into my hands, I'll cup them like a glass to drink from...
- Tattle Tale
glibc_2.3.2-1_i386.changes uploaded successfully to localhost
along with the files:
glibc_2.3.2-1.dsc
glibc_2.3.2.orig.tar.gz
glibc_2.3.2-1.diff.gz
libc6_2.3.2-1_i386.deb
libc-udeb_2.3.2-1_i386.udeb
libc6-dev_2.3.2-1_i386.deb
libc6-prof_2.3.2-1_i386.deb
libc6-dbg_2.3.2-1_i386.deb
There are disparities between your recently accepted upload and the
override file for the following file(s):
libc6-dbg_2.3.2-1_i386.deb: package says section is devel, override says
libdevel.
libc6-pic_2.3.2-1_i386.deb: package says section is devel, override says
libdevel.
libc6-prof_2.3.2-1_i3
Accepted:
glibc-doc_2.3.2-1_all.deb
to pool/main/g/glibc/glibc-doc_2.3.2-1_all.deb
glibc_2.3.2-1.diff.gz
to pool/main/g/glibc/glibc_2.3.2-1.diff.gz
glibc_2.3.2-1.dsc
to pool/main/g/glibc/glibc_2.3.2-1.dsc
glibc_2.3.2.orig.tar.gz
to pool/main/g/glibc/glibc_2.3.2.orig.tar.gz
libc-udeb_2.3.2-
Your message dated Fri, 18 Jul 2003 05:17:47 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#199134: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:47 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#194791: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:46 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#193331: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:46 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#193327: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191295: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#188159: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#188159: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#188159: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#187475: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#186654: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#185924: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#189854: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#185648: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#181701: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#173963: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#189879: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#171695: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#188159: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#160040: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#186210: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#164638: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#183694: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#158410: fixed in glibc 2.3.2-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
Your message dated Fri, 18 Jul 2003 05:17:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#182654: fixed in glibc 2.3.2-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
1 - 100 of 140 matches
Mail list logo
