From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] glibc-2.3.4.20041102-r1 has gone goofy
Date: Wed, 23 Mar 2005 01:24:13 -0500 [thread overview]
Message-ID: <200503230124.13490.vapier@gentoo.org> (raw)
In-Reply-To: <200503230027.52858.lostson@lostsonsvault.org>
On Tuesday 22 March 2005 07:27 pm, LostSon wrote:
> I have tried the user list and the forums and just cant seem to get an
> answer to this. When trying to upgrade my glibc cuz it comes up as an
> upgrade it does nothing bit infinite loop.
everytime an infinite loop with glibc has come up it's been because the user's
clock was screwed up ... perhaps you should verify that `date` is displaying
the correct time ?
-mike
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-23 6:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 0:27 [gentoo-dev] glibc-2.3.4.20041102-r1 has gone goofy LostSon
2005-03-23 6:24 ` Mike Frysinger [this message]
2005-03-23 0:44 ` LostSon
2005-03-23 17:10 ` Aron Griffis
2005-03-23 14:11 ` LostSon
2005-03-23 21:53 ` Martin Schlemmer
2005-03-23 16:02 ` LostSon
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=200503230124.13490.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.gentoo.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