From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Winex and glibc
Date: Mon, 21 Jul 2003 21:57:20 -0400 [thread overview]
Message-ID: <200307212157.23996.vapier@gentoo.org> (raw)
In-Reply-To: <auto-000095644504@remt26.cluster1.charter.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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)
iQIVAwUBPxyaAEFjO5/oN/WBAQLKOA/8DTmALCisYCWiaWw0cwGvXdTX4IMelAX1
Dq7WkA+4V9UxzfTxm23ouNvkWj338bOxJbuwE5P/EVaL5gMaQW1oNoxWrr/uzBm1
dj6y+9LLK2JgS861KckG8wCQRWt1/RtM1yDs3HNIZS5Kqos9ap3Rv/faOYovw3av
B/DErQ7P5t4iZN5fb7IBAc0WKUjZ8eJMhxJgDOKiwu+S4+FL7OtXc15dw6fqi/iC
DMnheMcHkX1XiSRTOUFsq0TP/8n+qg7v88ax1mg4jvwjBnL5undiJAfGYRxOoC2g
MepWRC9ntf/chH+Sn6u8vRaiFgJgruJ2m/nlshpZur2TncxDaLFjYNAqzKB/Vevc
B9xuWNPPwUiO6JyWUMi4hyXrvHqwzF4tbtm3pmcCrnicOlSrs8VCKFwd8NoUK+VW
TeJPKYavgS3mOxHt2anlO97AZVWUIg52nzfy57NN5wwoCC4cdohWxWO4/2Uk5l5N
j5wJf8RR/wfAzCPDq1s+kjeUD78P2k03+Bhlir5kT3E9dFcYiyhe/D8VQGmZ0BsE
fON4ih/fa8ybkQWj3dtA+Oj/CzhodsXWL73+3dvYV2EqVCfkHIy8NMkT6rGUopb8
kzRzxf44yvWyFD62orRpAwqTv1vO9Y0GZjgD7M4nGAjn5PbpRTMVrFQYyv3gdtjP
AbLL4mKDJqE=
=wFwi
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-22 1:57 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 [this message]
[not found] ` <auto-000099280975@remt23.cluster1.charter.net>
2003-07-22 2:35 ` Mike Frysinger
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=200307212157.23996.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