jhan

The bug report is marked as closed but the task not finished yet, as you can see by the comments in the bug. It still needs some work:

Current version for 1.2 should be mesa-17.2.8 and, if the time stamp is correct, that version was added 5 months ago (about 2 months after the official release). There are already requests for an update of mesa: https://bugs.funtoo.org/browse/FL-5183 https://bugs.funtoo.org/browse/FL-5154 So I would say that they are just a bit behind.

So the question would be: What takes preference: The entry in the profile or the one in make.conf? To me it seems that for packages the setting in make.conf is the one. But for update world the one in the profile, thus wanting to add pam to the system, although no package needs it.

I would guess that the system wants to enable the USE flag curl_ssl_nss for the package curl because the USE flag nss is set for the package liboauth. I get the same error when I want to reinstall liboauth. It seems that ths USE flag nss got activated by the system lately. There are not many packages that use the USE flag nss. So, if you don't need this USE flag then you could deactivate it globally or for liboauth only and you should be fine.

I don't see such behaviour (in top or htop) but maybe I just don't know what to look for. Can you give an example how to spot if make behaves normal or not?

There is no need to upgrade the python-kit, if you don't want to. All you need to do is unmask the python version you want to install. On my system I have : python-kit 3.4-prime /etc/portage/unmask =dev-lang/python-3.5.3 =dev-lang/python-3.6.1-r2

What about "Device Drivers->MMC/SD/SDIO card support" ?

If you look closely, you see that this bug report is closed and marked as fixed. So you would need to open a new bug.

Any protocol with the reason for this error? There should be: There should also be a build log, as you are using emerge.

Exactly. And that is the reason why you should open a bug. The problem is not qca. It is that kdelibs requires exactly and only qt4 when the USE flag plasma is selected. If you file a bug, the developers can have a look at it and decide what to do.

If you really need qt4 support and can't live with only qt5, you should open a bug at http://bugs.funtoo.org

My guess would be that the packages compiled with ruby 2.2 are trying to pull in the old ruby version. On my system I only have ruby 2.4 enabled. But even if I want to activate ruby 2.2 it does not show. Could it be that ruby 2.2 is globally deactivated? I think that the above emerge would reemerge the "faulty" packages and get rid of the error messages.

Something is pulling in qt4 for qca. Do you normally use qt4 or qt5?

Yes, it is tedious but so far the only way I know for solving those conflicts. I agree that it would be ideal if emerge would do these things alone but so far I haven't experienced that. Although, if I read bug https://bugs.funtoo.org/browse/FL-3491 correctly, it seems to already do that. Not sure if it is true or not though.

>>> net-print/cups-filters-1.17.9:0/0::net-kit, installed, wants app-text/poppler:0/66= >>> media-gfx/gimp-2.8.22:2/2::media-kit, installed, wants >=app-text/poppler-0.12.4[cairo] My candidates are: >>> app-text/poppler-0.45.0:0/62::gnome-kit, ebuild scheduled for merge has SLOT 0/62 and IUSE cairo >>> app-text/poppler-0.52.0-r2:0/66::gnome-kit, installed has SLOT 0/66 and IUSE cairo It seems that the old gimp version is pulling in the old poppler version. In such cases it often helps to emerge the conflicting packages together. In this case e.g. emerge -pv cups-filters gimp The rest of the messages seem to have the same problem. Try to make the updates in steps. I would try to get a list of available updates at first. For that I would exclude problematic packages from emerge with --exclude until I have a list and then go through them manually. This helps to get the system up to date, especially if it hasn't been updated for a while.