From: Allen Ziegenfus <listmail@allenz.net>
To: gentoo-alpha@lists.gentoo.org
Subject: Re: [gentoo-alpha] glibc problem
Date: Thu, 19 Aug 2004 00:30:07 -0400 [thread overview]
Message-ID: <20040819003007.483f9ad7.listmail@allenz.net> (raw)
In-Reply-To: <018201c485a0$4e436e00$3301a8c0@ICHIRO>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
On the fine day of Wed, 18 Aug 2004 20:54:58 -0700
"Brian Parkhurst" <brianp@spamcop.net> said very eloquently:
> I went to do an upgrade world (its been a couple of weeks), and found
> that the version of glibc I currently have installed is newer than
> what the latest release is. glibc-2.3.2-r11 is latest stable, and
> I've apparently got glibc-2.3.3_pre20040207.
Same situation here. If you look in the changelog for the glibc ebuild
you can see that they downgraded it back to 2.3.2 for alpha for some
reason, something to do with the LiveCDs.
However if I try to go ahead with the downgrade I get a bug nasty
warning message saying lots of things won't work if I go ahead with it.
It's a little troubling as there is a GLSA about the 2.3.3_pre
glibc.
For now I have just masked it so I don't see it anymore and eventually
I'm going to rebuild all my packages since I have a host of other
problems. But if anyone could advise about the effects of downgrading
glibc it would be appreciated.
Allen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-08-19 4:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1092885229.748159-12692-slash-slashdot-nfs-1.osdn.net@slashdot.org>
2004-08-19 3:54 ` [gentoo-alpha] glibc problem Brian Parkhurst
2004-08-19 4:30 ` Allen Ziegenfus [this message]
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=20040819003007.483f9ad7.listmail@allenz.net \
--to=listmail@allenz.net \
--cc=gentoo-alpha@lists.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