From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] update of libc?
Date: Thu, 18 Sep 2003 19:31:33 +0200 [thread overview]
Message-ID: <20030918173133.GG12661@lug-owl.de> (raw)
In-Reply-To: <20030918160249.GC30890@systemhalted>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
On Thu, 2003-09-18 12:02:49 -0400, Carlos O'Donell <carlos@baldric.uwo.ca>
wrote in message <20030918160249.GC30890@systemhalted>:
> On Thu, Sep 18, 2003 at 11:31:57AM +0200, Tilo Riemer wrote:
> > is it dangerous to make an update of libc from 2.2.5 to 2.3.x?
> > At the moment I have only remote access to the affected host.
>
> There is no 2.3.x glibc available for debian, it's currently being
> fixed. I apologize for the delay, it's more difficult than usual.
No?
b132l-1:~# dpkg -l libc6
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii libc6 2.3.1-17.0.3 GNU C Library: Shared libraries and Timezone
For me, that one works and seems to be 2.3.x... However, what are
current libc's problems?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-18 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 9:31 [parisc-linux] update of libc? Tilo Riemer
2003-09-18 9:38 ` Jan-Benedict Glaw
2003-09-19 6:40 ` Tilo Riemer
2003-09-18 16:02 ` Carlos O'Donell
2003-09-18 17:31 ` Jan-Benedict Glaw [this message]
2003-09-18 17:49 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030918173133.GG12661@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox