i have masked expat 2, downgrade it, and tried to emerge all my kde-based stuff like many here. but it is not allowing me to re-emerge my stuff because the expat thing is still screwing things up! how did you guys do it and how do i fix it?

the problem is, i did that! i emerged some small packages to test that out, and nothing works! when i was still logged in x, i re-emerged kate and kopete, and neither worked! at some point, i rebooted, and wanted to log into x again, but fluxbox won't start! i re-emerged fluxbox and it failed to load when i want to start x. my system been broken for 3 days now! damn expat!

well add -Wl,--as-needed to your linker-flags and emerge -e world
you'll never exeprience such system-breakdown anymore, it's that easy - there is nothing in kde, which really depends on expat, as long as I know._________________"I knew when an angel whispered into my ear,
You gotta get him away, yeah
Hey little bitch!
Be glad you finally walked away or you may have not lived another day."
Godsmack

which version of expat do you have installed now?
what is the output of
readelf -d /usr/bin/conky
I suppose that you haven't installed sth without the portage?
the second thing is that you could try the script, in this thread to see which applications link to libexpat_________________"I knew when an angel whispered into my ear,
You gotta get him away, yeah
Hey little bitch!
Be glad you finally walked away or you may have not lived another day."
Godsmack

Have you re-emerged -e world with the as-needed ldflag, it is impossible to have this behaviour, it could have two explanations:
you are not using the --as-needed or somehow emerge -e world has failed to re-emerge some packages.
re-emerge them with emerge -D1 and see what happens._________________"I knew when an angel whispered into my ear,
You gotta get him away, yeah
Hey little bitch!
Be glad you finally walked away or you may have not lived another day."
Godsmack

it appears that programs will work only if i unmerge it, and then emerge it all over it again. some stuff continue to run after i have exited x with ctrl+alt+backspace. i know this, because in shell, error messages keep on showing up line after line.

thank you for trying to help. but i think i just had enough of it, this is day 5 and my system is still screwed up.

this expat thing is the biggest pos i ever expierenced in computer problems.

i think it is far better and faster if i torn down my entire system and reinstall it all over again!

like many said: expat 2.0.0 should be hard masked! and the developers should be hanged by the balls.

like many said: expat 2.0.0 should be hard masked! and the developers should be hanged by the balls.

Which developers? The expat ones? Then you wouldn't have had expat 1 or expat 2, and the world would be a worse place. See my earlier posts for why we (as gentoo users) have any right to limit the expat ones.
The gentoo ones? And then you wouldn't have gentoo. If you can be bothered to read the bugzilla report on this upgrade, you will understand the reason why things have been done the way they have. If you can think of a better way, I'm sure they'll be delighted to hear it.

As far as I can tell expat-2 is still ~'d. If you can't cope with using ~ packages, don't do it. Nobody is forcing you.

Calm down. Grow up. Or remember to put a smiley in _________________pihl

like many said: expat 2.0.0 should be hard masked! and the developers should be hanged by the balls.

Which developers? The expat ones? Then you wouldn't have had expat 1 or expat 2, and the world would be a worse place. See my earlier posts for why we (as gentoo users) have any right to limit the expat ones.
The gentoo ones? And then you wouldn't have gentoo. If you can be bothered to read the bugzilla report on this upgrade, you will understand the reason why things have been done the way they have. If you can think of a better way, I'm sure they'll be delighted to hear it.

As far as I can tell expat-2 is still ~'d. If you can't cope with using ~ packages, don't do it. Nobody is forcing you.

Calm down. Grow up. Or remember to put a smiley in

Well i can understand him (although i have to say that the words he used are ABSOLUTELY not okey), when i TRIED to upgrade expat there was NO einfo msg in the ebuild (they put this in AFTER many ppl complained about borking their system by upgrading expad) and pow my system was fucked. X was gone... VERY ANNOYING

I do think that quite alot of packages are put into portage without doin REALLY proper testing. Have seen alot during my two years of gentoo...

But honestly if everybody would keep to this we wouldn't have so many fights/insults... here, and we could all stick to the important things like solving problems...

There is realy easy way to upgrade to new expat without disabling almost complete system set for day or two to rebuild packages depends on it. Before upgrade to 2.0.0 copy libexpat* from /usr/lib/ to /usr/local/lib and make ldconfig. Now upgrade to 2.0.0

Now all packages that use old libexpat would use version from /usr/local/lib, but emerge would use new version from /usr/lib. This way you can still use your system when rebuilding KDE, Gnome, etc. After revdep-rebuild when all packages use new version just delete libexpat from /usr/local/lib and that all.

I made the symlink as was mentioned on page one of this thread. I know this was not a good idea, but i needed a fix. Now my X is messed up. For example when i browse i often see the background colors instead of the fonts. I tried to fix it with revdep-rebuild, but still the same problem.

This is a fresh installed gentoo on an amd64. It was just installed for one day and now i run into this problem .

can someone help me out, this problem is a bit complicated for me.

ps i use gnome and followed the steps i saw laurelin make. However this was after i had made a simlink._________________Smokey, this is not 'Nam. This is bowling. There are rules.

There is realy easy way to upgrade to new expat without disabling almost complete system set for day or two to rebuild packages depends on it. Before upgrade to 2.0.0 copy libexpat* from /usr/lib/ to /usr/local/lib and make ldconfig. Now upgrade to 2.0.0

Now all packages that use old libexpat would use version from /usr/local/lib, but emerge would use new version from /usr/lib. This way you can still use your system when rebuilding KDE, Gnome, etc. After revdep-rebuild when all packages use new version just delete libexpat from /usr/local/lib and that all.

There is realy easy way to upgrade to new expat without disabling almost complete system set for day or two to rebuild packages depends on it. Before upgrade to 2.0.0 copy libexpat* from /usr/lib/ to /usr/local/lib and make ldconfig. Now upgrade to 2.0.0

damn good idea, much more sensible than symlinking files with different ABIs

This should be in the einfo message!

Many thanks. _________________Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86

i fixed this problem by running revdep-rebuild. revdep-rebuild listed packages that were missing dependencies. for me, revdep-rebuild failed after this step. then i manually emerged all the packaged listed in revdep-rebuild.

I recently emerged expat-2.0.0, and the woes since doing so refuse to cease. First thing after the emerge I ran revdep-rebuild -X --library=libexpat.so.0, it failed on the first package, gtk+, because it complained about a missing expat.so.0 during the emerge. Someone suggested remerging neon, I did so, and emerged mplayer successfully, but mplayer refuses to start, complaining about, lo and behold, libexpat.so.0. I read a second suggestion to add --as-needed to LDFLAGS, but as far as I can tell this has fixed nothing. A second remerge of mplayer produces the same result. Does anyone have any idea what could be going on?