From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Winex and glibc
Date: Mon, 21 Jul 2003 22:35:01 -0400 [thread overview]
Message-ID: <200307212235.05600.vapier@gentoo.org> (raw)
In-Reply-To: <auto-000099280975@remt23.cluster1.charter.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
i wouldnt suggest trying to downgrade ... i'm pretty sure it'll leave your box
usuable (well it'll leave glibc unusable and thats usually your whole box :D)
you can (if you dont mind shelling out $5) buy the binary versions from
transgaming ... those work with the newest glibc ...
- -mike
On Monday 21 July 2003 22:35, you wrote:
> Winex was working but I haven't tried it since the glibc update. I only
> run one game under it and haven't had time to try it.
>
> Anyway to get back to the previous version of glibc - what does that entail
> - merge the previous, unmerge 2.3.2? Who knows when they'll update winex.
>
> > if you're already using glibc-2.3.2 then winex hasnt been working for you
> > ... `emerge -C winex` and wait until they release a newer version that
> > works with glibc-2.3.2
> > -mike
> >
> > On Monday 21 July 2003 20:18, Brett I. Holcomb wrote:
> > > Nope, didn't work. If I do an emerge -u --deep system -p it wants to
> > > downgrade/upgrade glibc-2.3.1-r4 from 2.3.2-r1. I'm still blocked.
> > >
> > > I'm running glibc-2.3.2-r1.
> > >
> > > Any ideas on how to fix this? I'll bug it too.
> > >
> > > Looks like you were right!
> > >
> > > > On Tuesday 22 Jul 2003 00:20, Brett I. Holcomb wrote:
> > > > > I did an emerge -u --deep world -p and am told that winex -cvs and
> > > > > glibc-2.3.2-r1 conflict with each other. I get
> > > > >
> > > > > B app-emulation/winex-cvs (from pkg sys-libs/glibc-2.3.2-r1)
> > > > > R sys-libs.glibc-2.3.2-r1
> > > > >
> > > > > I remember some heavy discussion on glibc being upgraded (one says
> > > > > it breaks x but another says x works fine, etc.) but from what I
> > > > > remember it was decided to do it anyway.
> > > > >
> > > > > How do I fix this? It appears I'm blocked. I didn't see anything
> > > > > on bugzilla that would apply to this.
> > > >
> > > > Hi Brett,
> > > >
> > > > I was one making noise about winex not working with glibc-2.3.2. I
> > > >
> > > > added this line to /etc/portage/package.mask:
> > > > >=sys-libs/glibc-2.3.2-r1
> > > >
> > > > before upgrading. This kept glibc-2.3.2-r1 on my box so winex still
> > > > works for me.
> > > >
> > > > Everything OK so far.
> > > >
> > > > Peter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iQIVAwUBPxyi1UFjO5/oN/WBAQJqzg/+JHRcVHq2CgvuHB+lDMennEYPODpXpF2H
qhxhuSIU/T/q+BSON9l6WBNBYc+mF1YZgWxRD5uIlGQ1mjEyt4En9iMxJnVESzpi
/6Fx8sja8QPZqVg4ghG4zpw7g2BVZaSwyOypkrTPELRgPn+JNgsoTPAR4KrBqPqU
adipXHji1gYVidNP66H9sK0C5NTP8YX+/c9lNd5m7U4u4a6Ore8Gsc016Zhdcmyf
E8W6StMAdKw7U2Lr9tE6qgBNycJ8izXDsrQ7d+uiLL1WaGTyQjG6JziMqXsp61xl
XrAbf+eUpeGOvHAkDptGNnsa5mgphZjdJNBlNtt+ct7Dw2V4SpfQablI1sSPabq4
qlr87Yt+pWHMMIefnPOhN4QSkDA/sJatDOxBpNAuYWX++Jyyar09IwoXHMVFAVXU
LaPRnrWcoSIy8UV9JSRvJ9q4QAHJ08lyUdF+w3I6Rah40WOG8yo/c0i4UYnkB57v
9AYunlxExf0+BpK8DJPy4be4Y4uYfnrFTMQKxUUToaooec4D18hAaZT/V9v5U2lB
/dvNnGjXbJZ2zw9JRPNXrSxnGd5dT5hZTKNbcMyMBajfLTqvYyvJzf8QDVQPVE6M
A5T42FClFiFYbS28FoJFEj07ITZB8P2hTyGkPfmRPjPTeZ1JxdDs1MNw9D5Atbcj
UINBi2t3Hvc=
=uB2e
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-22 2:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 23:20 [gentoo-dev] Winex and glibc Brett I. Holcomb
2003-07-21 23:34 ` Peter Ruskin
2003-07-22 0:18 ` Brett I. Holcomb
2003-07-22 1:57 ` Mike Frysinger
[not found] ` <auto-000099280975@remt23.cluster1.charter.net>
2003-07-22 2:35 ` Mike Frysinger [this message]
2003-07-22 5:17 ` Tony Clark
2003-07-22 5:24 ` Jon Portnoy
2003-07-22 13:21 ` Mike Wojcikiewicz
2003-07-22 15:47 ` Tony Clark
2003-07-22 15:49 ` Tony Clark
2003-07-22 6:30 ` Peter Ruskin
2003-07-22 22:53 ` James H. Cloos Jr.
2003-07-22 23:00 ` Peter Ruskin
2003-07-24 3:20 ` James H. Cloos Jr.
2003-07-22 23:01 ` Thomas de Grenier de Latour
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=200307212235.05600.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@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