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