Re: [gentoo-user] --depclean and PyQt4 blocking
On Sun, Mar 1, 2009 at 2:11 AM, Dale rdalek1...@gmail.com wrote: emerge --update --newuse --deep @system @world Did you do that command? AFAIK depclean should only be done after world has been fully updated. I don't know what profile/arch you're running... On my system it was recently upgraded to Qt-4.5, so if that's the case for you then I'd unmerge the Qt-4.4 stuff entirely and then update world and see what it tries to bring in.
Re: [gentoo-user] --depclean and PyQt4 blocking
Paul Hartman wrote: On Sun, Mar 1, 2009 at 2:11 AM, Dale rdalek1...@gmail.com wrote: emerge --update --newuse --deep @system @world Did you do that command? AFAIK depclean should only be done after world has been fully updated. I don't know what profile/arch you're running... On my system it was recently upgraded to Qt-4.5, so if that's the case for you then I'd unmerge the Qt-4.4 stuff entirely and then update world and see what it tries to bring in. World the way it is set up includes system. I don't use the sets feature as of yet. So world includes system as long as you leave off the @ thingy. I posted this on the forums after a day or so. A developer posted the fix. Here it is quoted from http://forums.gentoo.org/viewtopic-p-5524910.html?sid=5a3c9d2154aae9b9c83e8215933a8df7#5524910 : What is probably happening here is that PyQt4 is linking qt-assistant and qt-xmlpatterns, if these packages are installed. But they are not listed as dependencies in the ebuild. So you can either (1) leave things as installed now, or (2) unmerge qt-assistant and qt-xmlpatterns, and then rebuild PyQt4. That those packages are not listed in the PyQt4 ebuild as optional dependencies is a bug that needs to be fixed tho. Unmerging those then rebuilding PyQt4 worked and it comes back clean. Finer than frog hair now. ;-) Dale :-) :-)
[gentoo-user] --depclean and PyQt4 blocking
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: r...@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 r...@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 :-) :-)
