libc6 in stable broken on arm4vl
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glibc (Debian) |
Fix Released
|
Unknown
|
|||
glibc (Ubuntu) |
Invalid
|
High
|
Jeff Bailey |
Bug Description
Automatically imported from Debian bug report #324795 http://
In Debian Bug tracker #324795, Simon Law (sfllaw) wrote : libc bug appears to be dangerous for arm | #1 |
Debian Bug Importer (debzilla) wrote : | #2 |
Automatically imported from Debian bug report #324795 http://
In Debian Bug tracker #324795, Nathanael Nerode (neroden-twcny) wrote : | #3 |
I don't suppose you know whether this affects libc6 in unstable? I doubt you
would know. :-( It would be nice to know for bug tracking purposes though.
--
Nathanael Nerode <email address hidden>
This space intentionally left blank.
In Debian Bug tracker #324795, GOTO Masanori (gotom-debian) wrote : Re: Bug#324795: libc6 in stable broken on arm4vl | #4 |
At Tue, 23 Aug 2005 22:38:15 -0400,
Rob Warren wrote:
> Version: 2.3.2.ds1-22
>
> Keeping up with Stable the new release for libc6 is broken. dpkg dies
> on the upgrade.
Did you try to upgrade from woody to sarge? Or from sarge to the
current sid? Please imagine 2.3.2.ds1-22 is broken - many arm users
cannot use their machine.
> Linux jill 2.2.19 #1 Tue Dec 25 13:58:22 GMT 2001 armv4l unknown
This kernel is not the standard debian supported kernel - it seems a
bit old. Can you try newer kernel with glibc 2.3.2.ds1-22?
> llseek bad argument is the most common error message.
Could you show us some examples of your messages?
Regards,
-- gotom
In Debian Bug tracker #324795, Rob Warren (rhwarren) wrote : | #5 |
It's dead jim.
I'm running stable to present this kind of thing. :(
best,
rhw
On 24-Aug-05, at 1:29 AM, Nathanael Nerode wrote:
> I don't suppose you know whether this affects libc6 in unstable? I
> doubt you
> would know. :-( It would be nice to know for bug tracking purposes
> though.
>
> --
> Nathanael Nerode <email address hidden>
>
> This space intentionally left blank.
>
In Debian Bug tracker #324795, Rob Warren (rhwarren) wrote : | #6 |
Goto,
I was upgrading from woody to sarge when apt-get choked on upgrading
libc6 from 2.2.5-11.8 to 2.3.2.ds1-22 with a message along the lines of
'can't seek in file xxxxxx'. dmesg would report 'Bad number of
arguments for llseek()' (paraphrasing) every so often. It was
impossible to reserve the package install.
On 24-Aug-05, at 4:39 AM, GOTO Masanori wrote:
> Did you try to upgrade from woody to sarge? Or from sarge to the
> current sid? Please imagine 2.3.2.ds1-22 is broken - many arm users
> cannot use their machine.
The machine is 3,000 km away from me in a sub-basement. It's dead. It's
nail-the-
>> Linux jill 2.2.19 #1 Tue Dec 25 13:58:22 GMT 2001 armv4l unknown
>
> This kernel is not the standard debian supported kernel - it seems a
> bit old. Can you try newer kernel with glibc 2.3.2.ds1-22?
2.2.19 is the last kernel that I've run without problems; the machine
had an uptime of 221 days when I tried to upgrade.
Getting someone to access the machine is non-trivial and is going to
require shipping the computer.
I won't be able to try anything for a few weeks until I get access to
the machine.
>
>> llseek bad argument is the most common error message.
>
> Could you show us some examples of your messages?
>
> Regards,
> -- gotom
best,
rhw
Jeff Bailey (jbailey) wrote : | #7 |
No arm distribution on Ubuntu
In Debian Bug tracker #324795, GOTO Masanori (gotom-debian) wrote : | #8 |
severity 324795 normal
tags 324795 moreinfo
thanks
At Wed, 24 Aug 2005 09:11:30 -0400,
Rob Warren wrote:
> I was upgrading from woody to sarge when apt-get choked on upgrading
> libc6 from 2.2.5-11.8 to 2.3.2.ds1-22 with a message along the lines of
> 'can't seek in file xxxxxx'. dmesg would report 'Bad number of
> arguments for llseek()' (paraphrasing) every so often. It was
> impossible to reserve the package install.
Weird. Grep told me that dmesg (kernel 2.2.19) and glibc should not
warn such kind of messages.
> >> Linux jill 2.2.19 #1 Tue Dec 25 13:58:22 GMT 2001 armv4l unknown
> >
> > This kernel is not the standard debian supported kernel - it seems a
> > bit old. Can you try newer kernel with glibc 2.3.2.ds1-22?
>
> 2.2.19 is the last kernel that I've run without problems; the machine
> had an uptime of 221 days when I tried to upgrade.
Uptime is not important information for this kind of userland issue.
> Getting someone to access the machine is non-trivial and is going to
> require shipping the computer.
> I won't be able to try anything for a few weeks until I get access to
> the machine.
If so, we can't track down any more too - please send us the detailed
information if you have an access for that machine.
Regards,
-- gotom
In Debian Bug tracker #324795, Steve Langasek (vorlon) wrote : | #9 |
On Wed, Aug 24, 2005 at 08:53:56AM -0400, Rob Warren wrote:
> It's dead jim.
> I'm running stable to present this kind of thing. :(
I'm afraid that sarge received very little upgrade testing from the ARM
community prior to release, apparently because the number of arm boxes that
could even *run* a stock woody system was a very small fraction of the
overall install base. This is so far the second crippling upgrade bug on
arm that's come to light since the release, the other being bug #312936 and
for which I've received *no* feedback from the ARM porter community.
If we can identify a minimum kernel version that should be used with sarge
on arm, and handle that in the preinst, I'm sure the stable release manager
would allow a point release update for this bug in order to spare others the
pain you've gone through here in uncovering this bug.
I'm pretty confident that if you are able to get a 2.4.27 kernel installed
and running on this machine you shouldn't have any problems with stable
itself, but I realize that's small comfort given your current situation.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://
In Debian Bug tracker #324795, Rob Warren (rhwarren) wrote : | #10 |
I've just installed sarge onto the second netwinder without any
problems with libc 2.3.2.ds1-22 with the netboot image, kernel 2.4.27.
...then I tried to boot from the kernel I was previously using (2.2.19)
and got the dreaded result:
"unsupported llseek call standard"
Tried with 2.2.17 and got the same result.
Can we add a dependency to the libc package to prevent this from
happening to others?
best,
rhw
In Debian Bug tracker #324795, GOTO Masanori (gotom) wrote : | #11 |
At Sun, 11 Sep 2005 01:05:42 -0400,
Rob Warren wrote:
> I've just installed sarge onto the second netwinder without any
> problems with libc 2.3.2.ds1-22 with the netboot image, kernel 2.4.27.
>
> ...then I tried to boot from the kernel I was previously using (2.2.19)
> and got the dreaded result:
> "unsupported llseek call standard"
What was this message come from? Dmesg?
> Tried with 2.2.17 and got the same result.
>
> Can we add a dependency to the libc package to prevent this from
> happening to others?
Before doing any work, I would like to clear what your problem was.
Previously we discussed as follows:
> > libc6 from 2.2.5-11.8 to 2.3.2.ds1-22 with a message along the lines of
> > 'can't seek in file xxxxxx'. dmesg would report 'Bad number of
> > arguments for llseek()' (paraphrasing) every so often. It was
> > impossible to reserve the package install.
>
> Weird. Grep told me that dmesg (kernel 2.2.19) and glibc should not
> warn such kind of messages.
This means we need to confirm that your kernel is special or debian
standard one. If you use your custom kernel, we may not reappear such
kind of problem again.
Could you describe the following stuff? (1) your exact kernel version
and how to get it (2) the exact warning/error message.
Regards,
-- gotom
Debian Bug Importer (debzilla) wrote : | #12 |
Message-Id: <email address hidden>
Date: Tue, 23 Aug 2005 22:38:15 -0400
From: Rob Warren <email address hidden>
To: <email address hidden>
Subject: libc6 in stable broken on arm4vl
Package: libc6
Version: 2.3.2.ds1-22
Keeping up with Stable the new release for libc6 is broken. dpkg dies
on the upgrade.
Linux jill 2.2.19 #1 Tue Dec 25 13:58:22 GMT 2001 armv4l unknown
jill:~# ls -l /lib/libc.so.6
lrwxrwxrwx 1 root root 13 Aug 23 21:00 /lib/libc.so.6
-> libc-2.3.2.so
llseek bad argument is the most common error message.
...and now it looks like I'm re-installing base.
best,
rhw
Debian Bug Importer (debzilla) wrote : | #13 |
Message-ID: <email address hidden>
Date: Tue, 23 Aug 2005 23:05:22 -0400
From: Simon Law <email address hidden>
To: <email address hidden>
Subject: libc bug appears to be dangerous for arm
severity 324795 critical
thanks
--
Simon Law http://
Debian Bug Importer (debzilla) wrote : | #14 |
Message-Id: <email address hidden>
Date: Wed, 24 Aug 2005 01:29:56 -0400
From: Nathanael Nerode <email address hidden>
To: <email address hidden>
Subject: Re: libc6 in stable broken on arm4vl
I don't suppose you know whether this affects libc6 in unstable? I doubt you
would know. :-( It would be nice to know for bug tracking purposes though.
--
Nathanael Nerode <email address hidden>
This space intentionally left blank.
Debian Bug Importer (debzilla) wrote : | #15 |
Message-ID: <81slwzwwwx.
Date: Wed, 24 Aug 2005 17:39:58 +0900
From: GOTO Masanori <email address hidden>
To: Rob Warren <email address hidden>, <email address hidden>
Subject: Re: Bug#324795: libc6 in stable broken on arm4vl
At Tue, 23 Aug 2005 22:38:15 -0400,
Rob Warren wrote:
> Version: 2.3.2.ds1-22
>
> Keeping up with Stable the new release for libc6 is broken. dpkg dies
> on the upgrade.
Did you try to upgrade from woody to sarge? Or from sarge to the
current sid? Please imagine 2.3.2.ds1-22 is broken - many arm users
cannot use their machine.
> Linux jill 2.2.19 #1 Tue Dec 25 13:58:22 GMT 2001 armv4l unknown
This kernel is not the standard debian supported kernel - it seems a
bit old. Can you try newer kernel with glibc 2.3.2.ds1-22?
> llseek bad argument is the most common error message.
Could you show us some examples of your messages?
Regards,
-- gotom
Debian Bug Importer (debzilla) wrote : | #16 |
Message-Id: <email address hidden>
Date: Wed, 24 Aug 2005 08:53:56 -0400
From: Rob Warren <email address hidden>
To: <email address hidden>, Nathanael Nerode <email address hidden>
Subject: Re: Bug#324795: libc6 in stable broken on arm4vl
It's dead jim.
I'm running stable to present this kind of thing. :(
best,
rhw
On 24-Aug-05, at 1:29 AM, Nathanael Nerode wrote:
> I don't suppose you know whether this affects libc6 in unstable? I
> doubt you
> would know. :-( It would be nice to know for bug tracking purposes
> though.
>
> --
> Nathanael Nerode <email address hidden>
>
> This space intentionally left blank.
>
Debian Bug Importer (debzilla) wrote : | #17 |
Message-Id: <email address hidden>
Date: Wed, 24 Aug 2005 09:11:30 -0400
From: Rob Warren <email address hidden>
To: GOTO Masanori <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#324795: libc6 in stable broken on arm4vl
Goto,
I was upgrading from woody to sarge when apt-get choked on upgrading
libc6 from 2.2.5-11.8 to 2.3.2.ds1-22 with a message along the lines of
'can't seek in file xxxxxx'. dmesg would report 'Bad number of
arguments for llseek()' (paraphrasing) every so often. It was
impossible to reserve the package install.
On 24-Aug-05, at 4:39 AM, GOTO Masanori wrote:
> Did you try to upgrade from woody to sarge? Or from sarge to the
> current sid? Please imagine 2.3.2.ds1-22 is broken - many arm users
> cannot use their machine.
The machine is 3,000 km away from me in a sub-basement. It's dead. It's
nail-the-
>> Linux jill 2.2.19 #1 Tue Dec 25 13:58:22 GMT 2001 armv4l unknown
>
> This kernel is not the standard debian supported kernel - it seems a
> bit old. Can you try newer kernel with glibc 2.3.2.ds1-22?
2.2.19 is the last kernel that I've run without problems; the machine
had an uptime of 221 days when I tried to upgrade.
Getting someone to access the machine is non-trivial and is going to
require shipping the computer.
I won't be able to try anything for a few weeks until I get access to
the machine.
>
>> llseek bad argument is the most common error message.
>
> Could you show us some examples of your messages?
>
> Regards,
> -- gotom
best,
rhw
Debian Bug Importer (debzilla) wrote : | #18 |
Message-ID: <81pss2x3y4.
Date: Thu, 25 Aug 2005 09:20:19 +0900
From: GOTO Masanori <email address hidden>
To: Rob Warren <email address hidden>, <email address hidden>,
<email address hidden>
Cc: GOTO Masanori <email address hidden>
Subject: Re: Bug#324795: libc6 in stable broken on arm4vl
severity 324795 normal
tags 324795 moreinfo
thanks
At Wed, 24 Aug 2005 09:11:30 -0400,
Rob Warren wrote:
> I was upgrading from woody to sarge when apt-get choked on upgrading
> libc6 from 2.2.5-11.8 to 2.3.2.ds1-22 with a message along the lines of
> 'can't seek in file xxxxxx'. dmesg would report 'Bad number of
> arguments for llseek()' (paraphrasing) every so often. It was
> impossible to reserve the package install.
Weird. Grep told me that dmesg (kernel 2.2.19) and glibc should not
warn such kind of messages.
> >> Linux jill 2.2.19 #1 Tue Dec 25 13:58:22 GMT 2001 armv4l unknown
> >
> > This kernel is not the standard debian supported kernel - it seems a
> > bit old. Can you try newer kernel with glibc 2.3.2.ds1-22?
>
> 2.2.19 is the last kernel that I've run without problems; the machine
> had an uptime of 221 days when I tried to upgrade.
Uptime is not important information for this kind of userland issue.
> Getting someone to access the machine is non-trivial and is going to
> require shipping the computer.
> I won't be able to try anything for a few weeks until I get access to
> the machine.
If so, we can't track down any more too - please send us the detailed
information if you have an access for that machine.
Regards,
-- gotom
Debian Bug Importer (debzilla) wrote : | #19 |
Message-ID: <email address hidden>
Date: Wed, 24 Aug 2005 17:54:56 -0700
From: Steve Langasek <email address hidden>
To: Rob Warren <email address hidden>, <email address hidden>
Cc: Nathanael Nerode <email address hidden>
Subject: Re: Bug#324795: libc6 in stable broken on arm4vl
--uZ3hkaAS1mZxFaxD
Content-Type: text/plain; charset=us-ascii
Content-
Content-
On Wed, Aug 24, 2005 at 08:53:56AM -0400, Rob Warren wrote:
> It's dead jim.
> I'm running stable to present this kind of thing. :(
I'm afraid that sarge received very little upgrade testing from the ARM
community prior to release, apparently because the number of arm boxes that
could even *run* a stock woody system was a very small fraction of the
overall install base. This is so far the second crippling upgrade bug on
arm that's come to light since the release, the other being bug #312936 and
for which I've received *no* feedback from the ARM porter community.
If we can identify a minimum kernel version that should be used with sarge
on arm, and handle that in the preinst, I'm sure the stable release manager
would allow a point release update for this bug in order to spare others the
pain you've gone through here in uncovering this bug.
I'm pretty confident that if you are able to get a 2.4.27 kernel installed
and running on this machine you shouldn't have any problems with stable
itself, but I realize that's small comfort given your current situation.
--=20
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://
--uZ3hkaAS1mZxFaxD
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDDRbgKN6
6N0+fqOQwSrW67+
=Cye1
-----END PGP SIGNATURE-----
--uZ3hkaAS1mZxF
Debian Bug Importer (debzilla) wrote : | #20 |
Message-Id: <email address hidden>
Date: Sun, 11 Sep 2005 01:05:42 -0400
From: Rob Warren <email address hidden>
To: GOTO Masanori <email address hidden>, <email address hidden>,
Steve Langasek <email address hidden>, Nathanael Nerode <email address hidden>
Subject: Bug#324795: libc6 in stable broken on arm4vl
I've just installed sarge onto the second netwinder without any
problems with libc 2.3.2.ds1-22 with the netboot image, kernel 2.4.27.
...then I tried to boot from the kernel I was previously using (2.2.19)
and got the dreaded result:
"unsupported llseek call standard"
Tried with 2.2.17 and got the same result.
Can we add a dependency to the libc package to prevent this from
happening to others?
best,
rhw
Debian Bug Importer (debzilla) wrote : | #21 |
Message-ID: <81ek7qjpj1.
Date: Fri, 16 Sep 2005 00:53:38 +0900
From: GOTO Masanori <email address hidden>
To: Rob Warren <email address hidden>
Cc: GOTO Masanori <email address hidden>, <email address hidden>, Steve Langasek <email address hidden>,
Nathanael Nerode <email address hidden>
Subject: Re: Bug#324795: libc6 in stable broken on arm4vl
At Sun, 11 Sep 2005 01:05:42 -0400,
Rob Warren wrote:
> I've just installed sarge onto the second netwinder without any
> problems with libc 2.3.2.ds1-22 with the netboot image, kernel 2.4.27.
>
> ...then I tried to boot from the kernel I was previously using (2.2.19)
> and got the dreaded result:
> "unsupported llseek call standard"
What was this message come from? Dmesg?
> Tried with 2.2.17 and got the same result.
>
> Can we add a dependency to the libc package to prevent this from
> happening to others?
Before doing any work, I would like to clear what your problem was.
Previously we discussed as follows:
> > libc6 from 2.2.5-11.8 to 2.3.2.ds1-22 with a message along the lines of
> > 'can't seek in file xxxxxx'. dmesg would report 'Bad number of
> > arguments for llseek()' (paraphrasing) every so often. It was
> > impossible to reserve the package install.
>
> Weird. Grep told me that dmesg (kernel 2.2.19) and glibc should not
> warn such kind of messages.
This means we need to confirm that your kernel is special or debian
standard one. If you use your custom kernel, we may not reappear such
kind of problem again.
Could you describe the following stuff? (1) your exact kernel version
and how to get it (2) the exact warning/error message.
Regards,
-- gotom
In Debian Bug tracker #324795, Phil Blundell (pb-reciva) wrote : | #22 |
The "llseek" problem is caused by a kernel bug. I thought that the
2.2.19 netwinder kernels in Debian had been patched to fix this, but I
guess I was mistaken about that. Anyway, there isn't a great deal that
we can do in glibc to fix the underlying problem.
I guess we could add a check to glibc's preinst to catch this case and
prevent the new library being installed under a kernel where it won't
work. The easiest thing would just be to disallow anything older than
2.4.0. Writing a directed test to detect the presence of the actual bug
would also be possible, but that'd be a bit harder.
p.
Debian Bug Importer (debzilla) wrote : | #23 |
Message-Id: <email address hidden>
Date: Sun, 25 Dec 2005 12:06:46 +0000
From: Phil Blundell <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#324795: libc6 in stable broken on arm4vl
The "llseek" problem is caused by a kernel bug. I thought that the
2.2.19 netwinder kernels in Debian had been patched to fix this, but I
guess I was mistaken about that. Anyway, there isn't a great deal that
we can do in glibc to fix the underlying problem.
I guess we could add a check to glibc's preinst to catch this case and
prevent the new library being installed under a kernel where it won't
work. The easiest thing would just be to disallow anything older than
2.4.0. Writing a directed test to detect the presence of the actual bug
would also be possible, but that'd be a bit harder.
p.
In Debian Bug tracker #324795, Phil Blundell (pb-reciva) wrote : | #24 |
tags 243183 - pending
tags 340147 + pending
tags 344105 + pending
tags 343365 + pending
tags 324795 + pending
thanks
Debian Bug Importer (debzilla) wrote : | #25 |
Message-Id: <email address hidden>
Date: Mon, 26 Dec 2005 11:16:24 +0000
From: Phil Blundell <email address hidden>
To: <email address hidden>
Subject:
tags 243183 - pending
tags 340147 + pending
tags 344105 + pending
tags 343365 + pending
tags 324795 + pending
thanks
In Debian Bug tracker #324795, Clint Adams (clint) wrote : Bug#324795: fixed in glibc 2.3.5-10 | #26 |
Source: glibc
Source-Version: 2.3.5-10
We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive:
glibc-doc_
to pool/main/
glibc_2.
to pool/main/
glibc_2.3.5-10.dsc
to pool/main/
libc6-dbg_
to pool/main/
libc6-dev-
to pool/main/
libc6-dev_
to pool/main/
libc6-pic_
to pool/main/
libc6-prof_
to pool/main/
libc6-sparc64_
to pool/main/
libc6-sparcv9_
to pool/main/
libc6-sparcv9b_
to pool/main/
libc6-udeb_
to pool/main/
libc6_2.
to pool/main/
libnss-
to pool/main/
libnss-
to pool/main/
locales_
to pool/main/
nscd_2.
to pool/main/
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Clint Adams <email address hidden> (supplier of updated glibc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 28 Dec 2005 13:18:56 -0500
Source: glibc
Binary: libc6-dev-amd64 libc6-i686 libc6-dev-ppc64 libc0.3-pic glibc-doc libc1-udeb libc0.3 libc6.1-dev libc1-pic libc6-s390x libnss-files-udeb libc1-dbg libc6-dev-sparc64 libc0.3-dev libc6-udeb libc6-dbg libc6.1-pic libc6-dev libc0.3-prof libc6-sparcv9 libc6.1-prof libc1 locales libc6-pic libc0.3-udeb libc1-prof libc6-ppc64 libc0.3-dbg libc6-amd64 libc6-prof libc6 libc6-sparcv9b libc6.1-udeb libc6.1-dbg nscd libc6-sparc64 libnss-dns-udeb libc6.1 libc1-dev libc6-dev-s390x
Architecture: source sparc all
Version: 2.3.5-10
Distribution: unstable
Urgency: low
Maintainer: GNU Libc Maintainers <email address hidden>
Changed-By: Clint Adams <email address hidden>
Description:
glibc-doc - GNU C Library: Documentation
libc6 - GNU C Library: Shared libraries and Timezone data
libc6-dbg - GNU C Library: Libraries with debugging symbols
libc6-dev - GNU C Library: Development Libraries and Header Files
libc6-dev-sparc...
Debian Bug Importer (debzilla) wrote : | #27 |
Message-Id: <email address hidden>
Date: Thu, 29 Dec 2005 16:02:13 -0800
From: Clint Adams <email address hidden>
To: <email address hidden>
Subject: Bug#324795: fixed in glibc 2.3.5-10
Source: glibc
Source-Version: 2.3.5-10
We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive:
glibc-doc_
to pool/main/
glibc_2.
to pool/main/
glibc_2.3.5-10.dsc
to pool/main/
libc6-dbg_
to pool/main/
libc6-dev-
to pool/main/
libc6-dev_
to pool/main/
libc6-pic_
to pool/main/
libc6-prof_
to pool/main/
libc6-sparc64_
to pool/main/
libc6-sparcv9_
to pool/main/
libc6-sparcv9b_
to pool/main/
libc6-udeb_
to pool/main/
libc6_2.
to pool/main/
libnss-
to pool/main/
libnss-
to pool/main/
locales_
to pool/main/
nscd_2.
to pool/main/
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Clint Adams <email address hidden> (supplier of updated glibc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 28 Dec 2005 13:18:56 -0500
Source: glibc
Binary: libc6-dev-amd64 libc6-i686 libc6-dev-ppc64 libc0.3-pic glibc-doc libc1-udeb libc0.3 libc6.1-dev libc1-pic libc6-s390x libnss-files-udeb libc1-dbg libc6-dev-sparc64 libc0.3-dev libc6-udeb libc6-dbg libc6.1-pic libc6-dev libc0.3-prof libc6-sparcv9 libc6.1-prof libc1 locales libc6-pic libc0.3-udeb libc1-prof libc6-ppc64 libc0.3-dbg libc6-amd64 libc6-prof libc6 libc6-sparcv9b libc6.1-udeb libc6.1-dbg nscd libc6-sparc64 libnss-dns-udeb libc6.1 libc1-dev libc6-dev-s390x
Architecture: source sparc all
Version: 2.3.5-10
Distribution: unstable
Urgency: low
Maintainer: GNU Libc Maintainers <email address hidden>
Changed-By: Clint Adams <email address hidden>
Description:
glibc-doc - GNU C Library: Documentation
libc6...
severity 324795 critical
thanks
-- www.law. yi.org/ ~sfllaw/
Simon Law http://