Colleen Beamer writes:
> On Thu, Jun 17, 2010 at 12:54 PM, Alex Schuster <[email protected]>
> wrote:
> I don't remember why I unmasked the unstable version of libpng.
> However, following your advice, I first attempted to reinstall kdm.
> This had been an update 6 days ago when all this started. The emerge
> bombed. Therefore, I fixed my package.keywords file so, the unstable
> version of libpng would not emerge and re-emerged libpng. I can now
> boot into X.
Okay, this should have fixed a lot of broken things. I guess your revdep-
rebuid list would be even longer without this library.
> > Better use revdep-rebuild, there might be many other things that are
> > still linked to the old libpng.
>
> The can of worms comes from doing revdep-rebuild. However, the actual
> revdep-rebuild bombs and I get told that there are no e-builds to
> satisfy PyQt:0.
PyQt is in the kde-sunset overlay which contains all stuff needed for KDE
3.5. Do you have such things installed? Or is PyQt accidentally in your
/var/lib/portage/world file? emerge -pv --depclean PyQt should show you
which stuff pulls it in.
If you think nothing needs it, remove it with emerge -Ca PyQt, and try
revdep-rebuild again. Or add the kde-sunset overlay with layman.
> I admit that I have qt3support as a USE flag. Don't know if this is the
> issue and if I should remove it. Advice?
I do not have it set explicitely, but for me this USE flag is also
activated, probably because of the desktop profile. I do not have PyQt
installed.
Wonko