[gentoo-user] --depclean and PyQt4 blocking

[Dale <rdalek1967@gmail.com>]

Hi,

I did my weekly updates last night and as always I run --depclean -p
afterwards to see if anything needs cleaning out.  I seem to have ran
into something that doesn't make sense.  This is what I get:

> root@smoker / # emerge -p --depclean
>
>  * Always study the list of packages to be cleaned for any obvious
>  * mistakes. Packages that are part of the world set will always
>  * be kept.  They can be manually added to this set with
>  * `emerge --noreplace <atom>`.  Packages that are listed in
>  * package.provided (see portage(5)) will be removed by
>  * depclean, even if they are part of the world set.
>  *
>  * As a safety measure, depclean will not remove any packages
>  * unless *all* required dependencies have been resolved.  As a
>  * consequence, it is often necessary to run `emerge --update
>  * --newuse --deep @system @world` prior to depclean.
>
> Calculating dependencies... done!
> >>> Checking for lib consumers...
> >>> Assigning files to packages...
>  * In order to avoid breakage of link level dependencies, one or more
>  * packages will not be removed. This can be solved by rebuilding the
>  * packages that pulled them in.
>  *
>  *   x11-libs/qt-assistant-4.4.2-r1 pulled in by:
>  *     dev-python/PyQt4-4.4.4-r1
>  *
>  *   x11-libs/qt-xmlpatterns-4.4.2 pulled in by:
>  *     dev-python/PyQt4-4.4.4-r1
>  *
> >>> Adding lib providers to graph...
>  /
> Calculating dependencies... done!
> >>> No packages selected for removal by depclean
> >>> To see reverse dependencies, use --verbose
> root@smoker / #

I have ran emerge -1va =x11-libs/qt-assistant-4.4.2-r1
=x11-libs/qt-xmlpatterns-4.4.2 =dev-python/PyQt4-4.4.4-r1 so that it
will re-emerge all the packages it was fussing about.  I get the same
thing.  I also ran revdep-rebuild -i and it comes back clean.  I then
did this, emerge -v1a =dev-python/qscintilla-python-2.3.2
=x11-libs/qscintilla-2.3.2 =dev-python/PyQt-3.17.6
=x11-libs/qt-gui-4.4.2-r1 =x11-libs/qt-dbus-4.4.2 and still get the same
thing.

Anybody ran into this?  Anybody have a clue why it keeps giving this
message?  Do I need to rebuild something else that I missed to clear
this up?

Dale

:-)  :-)