On 06/28/2009 03:35 AM, Andrew Gaydenko wrote:
On Sunday 28 June 2009 03:05:48 Nikos Chantziaras wrote:
On 06/28/2009 01:51 AM, Andrew Gaydenko wrote:
On Sunday 28 June 2009 02:41:53 Nikos Chantziaras wrote:
I got that too, but portage (I'm on 2.1.6.13) has automatically resolved
all blocks. Are you using Paludis? If yes, uninstall all packages that
are to be upgraded and install them afterwards. Or wait for someone who
actually knows a Paludis workaround for this.
No, I don't use Paludis. What do you mean saying "has automatically
resolved all blocks"? Do you mean you have added those qt3support flags
and started emerging and got successfull upgrading to 4.5.2 without any
problems and in spite of those blocks?
I did not add qt3support anywhere. It seems to be enabled by default
here. Anyway, you went past that problem anyway. Your current is
something else: the blockers. What portage version are you using? If
portage won't resolve those blockers automatically for you, you can do
it the "traditional" way. Unmerge all packages that would be updated
and then update again. I would do it like this:
emerge -aC `qlist -IC x11-libs/qt*:4`
emerge -auDN world
Thanks, Portage has resolved conflicts, I'm on 4.5.2 now. It seems like
qt3support
flags deletion doesn't work for me. Now, after upgrading, I have tried to
comment out
those flags in package.use and got conflicts.
What profile do you use? (Find out with "eselect profile show".)
