skunk

hey! i'm 50% italian, but i don't live in italy anymore since 20 years... and oh, since yesterday i've switched back to the gentoo's portage tree after 6+ years with funtoo so i think i don't count anymore... cheers!

While setting an empty GENTOO_MIRRORS makes portage use gentoo's mirrors with way better network performance, you may now either miss some package or size/sum mismatch any other... After some tests I've found out that: sometimes the download speed is as slow as 56kbps when this happens downloads from remote networks are still decently speedy (tried from data centers in the US and EU) running local speedtest with other servers in Santa Fe (where the fastpull server is located) don't show the same slow down I live in Granada and I think my ISP (Movistar/Telefonica) is to blame since I'm suffering also interruptions with Netflix...

https://bugs.funtoo.org/browse/FL-5140

i don't know if it's wise to get rid of gcc-6.4.0 that fast since the most recent versions of cuda sdk/toolkit still depends on it as gcc versions later than 6 are not supported. however i can confirm that forcing compilation of cuda depending applications (like net-p2p/xmr-stak or app-crypt/johntheripper) by replacing "#if __GNUC__ > 6" with "#if __GNUC__ > 7" on /opt/cuda/include/crt/host_config.h:119, didn't give me any compilation or runtime problem so far... so please either leave gcc 6 ebuild alone or patch dev-util/nvidia-cuda-toolkit to ignore upstream unsupported gcc 7, thank you.

https://bugs.funtoo.org/browse/FL-4888

hello, any chance to get safe chromium ebuild to the tree? thank you

if you don't want to downgrade and keep staying up to date with kde-kit's stuff, this is what i did: # check out gentoo's tree: cd /var/git git clone git://anongit.gentoo.org/repo/gentoo.git # create a script that syncs kde-kit's stuff from the gentoo's tree to a local overlay: cat > /root/sync_kde.sh #!/bin/bash cd /var/git/gentoo git pull cd /var/git/meta-repo/kits/kde-kit for i in *-* do [[ ! -d /usr/local/portage/kde/$i ]] && mkdir /usr/local/portage/kde/$i cd $i for j in * do [[ -d /var/git/gentoo/$i/$j ]] && rsync -a --delete /var/git/gentoo/$i/$j /usr/local/portage/kde/$i/ done cd .. done # add the following to /etc/eix-sync.conf: @/root/sync_kde.sh || true # and finally add the overlay to make.conf: PORTDIR_OVERLAY="/usr/local/portage/kde"

nevermind it doesn't work the way i've thought, i've created my own overlay instead...

i've created my own kde-kit branch, how can i mark it active so that it might be chosen from ego.conf please? thank you

ok, i can live with it for some time, however why forcing everybody on 5.10-prime branch if they where on master if neither branch won't get updates anymore? downgrading from master to 5.10-prime isn't something worth doing if you already are on plasma-5.11.1/apps-17.08.2/framework-5.39, imho...

hello again, i've the following set into my ego.conf: xorg-kit = 1.19-prime media-kit = 1.1-prime kde-kit = master however on today sync i've got this message: "Kit kde-kit branch master specified in ego.conf is not currently active; using default kit instead." so why can i not choose kde-kit's master branch anymore in ego.conf? i've forced the master branch checkout by adding: @git -C /home/meta-repo/kits/kde-kit checkout origin/master || true into eix-sync.conf, however i wonder why these kind of hacks are necessary... thank you

well yes, would be nice to have the possibility to choose between kde-plasma-release and kde-plasma-lts... however if it's too much fuss, just branch using kde-apps as reference instead of kde-desktop...

i'm pretty sure they actually do it since one component release can be quite far away (in terms of time) from the other...

what do you mean exactly with updating kde parts asynchronously? kde-apps/frameworks/plasma have different independent release schedules and gentoo adds new ebuild short after there is a release of any of the 3 components afaik...

it would also be very cool to have an lts branch (like eg.18.08.3-lts-prime) which would install latest kde-apps-18.08.3 with kde-desktop-5.12.7 instead of kde-desktop-5.13.5 like 18.08.3-prime would do...

well... none... :) if you ask me, i would better branch on kde-apps version instead of kde-desktop version and number it as follows: 17.08.3-prime which includes kde-apps-17.08.3 (due nov. 6) kde-desktop-5.10.5 (released) kde-framework-5.40 (due nov. 4) 17.12.3-prime which includes kde-apps-17.12.3 (due march 8) kde-desktop-5.11.5 (due jan. 2) kde-framework-5.whatever on march 8 18.04.3-prime which includes kde-apps-18.04.3 (due sometime in july) kde-desktop-5.12.6 (due june 20) kde-framework-5.whatever in july branching it on kde-desktop version would need to push kde-apps fixes releases to the branch, even more for a wider definition... doing it on kde-apps instead just have to push -r releases with security issues, again imho...

thank you daniel for your explication, kde software compilation, how it's called today, consists of 3 components: kde-framework: with a monthly release schedule which may include both bugfixes and new features, since there are no minor versions, it may be snapshotted at any time kde-plasma: with frequent minor releases (for bugfixes) and a new major release every 5-6 months, since there usually are just 5 minor versions (except from lts releases), taking a snapshot when it reach a 5.x.5 version it would make an ideal point for a prime release kde-apps: with about monthly minor releases (for bugfixes) and a new major release every 4 months, here too since there are just 3 minor versions, taking a snapshot every yy.mm.3 version would be a good point for a stable prime release imho a prime snapshot should be taken whenever we have a yy.mm.3 kde-apps release and it should include whatever 5.x.5 kde-plasma version it's available at that time if prime snapshots are meant to be (almost) static. else if snapshots would allow minor changes it would be nice to have for example a 5.12.x lts prime snapshot where bugfixes are pushed when released upstream and (if sub-kits would exist) kde-apps snapshots could be pulled and installed on top of it... i also notice that dev-qt stuff was added to the kde-kit, i'm not sure if that's a good idea since there are other desktop environments in the desktop-kit that depends on qt5 like lxqt and lumina, but mostly because making a certain kde release dependant from a concrete qt5 release can complicate the snapshotting even more in case of (security) bugfixes that only qt can deliver, so a separate qt-kit would make more sense... of course imho... ;) thank you

so in my kde-kit example shall i expect a new, let's say, 5.10-prime-r1 branch with kde-apps-17.08.2 or will it only (kde-apps-17.08.2) be available into the new 5.11-prime branch? if the latter it would be very unfortunate for someone wanting to stay stable (keep on plasma 5.10 while getting apps 17.08 bugfixes)... thank you

hello devs (oleg) :) i wonder what are the rules behind this new kit organization... do packages from the master branch eventually make into a prime branch or are prime branches virtually immutable? if the former, after lying into the the master branch for some time (like gentoo's stable/unstable)? how long? any other criterion instead? if the latter, are "stable users" supposed to jump from prime-n to prime-n+1 branches at their discretion? for example i'm on the default 5.10-prime kde-kit's branch and i see that kde-plasma-5.11.0, kde-frameworks-5.39 and kde-apps-17.08.2 were added to the master branch. i expect at least kde-apps-17.08.2 to make into the 5.10-prime branch since it's a bug fix release, while kde-plasma-5.11.0 to be sometimes added to a new default 5.11-prime branch since it's a major release, not sure about frameworks-5.39 but i consider it pretty safe to include it into 5.10-prime after reaching master for some time... so just curious to know how this new kit organization method works and what's its internal rules :) thank you

ok, feeding emerge with the packages to build worked for me too even without unmerging qt-5.7.1 (useful if you don't want to stop using your pc meanwhile or if you want to keep a still needed qt4 installation)... i wonder if the conflicts was just a portage invention... :huh:

yet more conflicts; # emerge -uDN world These are the packages that would be merged, in order: Calculating dependencies... done! Oops! Conflicts have been encountered: >>> dev-qt/qtsql-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtsvg-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/designer-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qttest-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtwebengine-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qdbus-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtdeclarative-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtpaths-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtscript-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtwayland-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtxmlpatterns-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtmultimedia-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtprintsupport-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtgui-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtwidgets-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/linguist-tools-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtnetwork-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtx11extras-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtwebkit-5.9.1:5/5.9::dev-kit, ebuild scheduled for merge, wants >=dev-qt/qtcore-5.9.1:5[icu] >>> dev-qt/qtquickcontrols2-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtconcurrent-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtpositioning-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtwebchannel-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtxml-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtquickcontrols-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtimageformats-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtopengl-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtgraphicaleffects-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtdbus-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> app-benchmarks/i7z-93_p20131012-r1:0/0::nokit, installed, wants dev-qt/qtcore:5/5.7= >>> dev-qt/qtwebengine-5.7.1-r2:5/5.7::dev-kit, installed, wants ~dev-qt/qtcore-5.7.1 >>> app-office/calligra-3.0.1:5/5::desktop-kit, installed, wants dev-qt/qtcore:5/5.7= >>> dev-qt/qtdbus-5.7.1:5/5.7::dev-kit, installed, wants ~dev-qt/qtcore-5.7.1 >>> dev-qt/qtdeclarative-5.7.1-r1:5/5.7::dev-kit, installed, wants ~dev-qt/qtcore-5.7.1 >>> dev-qt/qtnetwork-5.7.1:5/5.7::dev-kit, installed, wants ~dev-qt/qtcore-5.7.1 >>> dev-qt/qtxmlpatterns-5.7.1:5/5.7::dev-kit, installed, wants ~dev-qt/qtcore-5.7.1 >>> dev-qt/qtgui-5.7.1-r1:5/5.7::dev-kit, installed, wants ~dev-qt/qtcore-5.7.1 >>> dev-qt/qtwidgets-5.7.1:5/5.7::dev-kit, installed, wants ~dev-qt/qtcore-5.7.1 >>> dev-qt/qtwebchannel-5.7.1:5/5.7::dev-kit, installed, wants ~dev-qt/qtcore-5.7.1 >>> dev-qt/qttest-5.7.1:5/5.7::dev-kit, installed, wants ~dev-qt/qtcore-5.7.1 My candidates are: >>> dev-qt/qtcore-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge has SLOT 5/5.9 >>> dev-qt/qtcore-5.7.1-r3:5/5.7::dev-kit, installed has SLOT 5/5.7 >>> dev-qt/qtmultimedia-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2[gles2=] >>> dev-qt/qtopengl-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2[gles2=] >>> dev-qt/qtx11extras-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2[xcb] >>> dev-qt/designer-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2 >>> dev-qt/qtquickcontrols2-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2 >>> dev-qt/qtquickcontrols-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2 >>> dev-qt/qtimageformats-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2 >>> dev-qt/qtgraphicaleffects-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2 >>> dev-qt/qtwebengine-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2 >>> dev-qt/qtwidgets-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2[gles2=,png=,xcb?] >>> dev-qt/qtprintsupport-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2[gles2=] >>> dev-qt/qtwebkit-5.9.1:5/5.9::dev-kit, ebuild scheduled for merge, wants >=dev-qt/qtgui-5.9.1:5[gles2=] >>> dev-qt/qtdeclarative-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2[gles2=] >>> dev-qt/qtwebkit-5.9.1:5/5.9::dev-kit, ebuild scheduled for merge, wants >=dev-qt/qtgui-5.9.1:5 >>> dev-qt/qtwayland-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2[egl,libinput?] >>> dev-qt/qtscript-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2 >>> dev-qt/qtsvg-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtgui-5.9.2 >>> dev-qt/qtwebengine-5.7.1-r2:5/5.7::dev-kit, installed, wants ~dev-qt/qtgui-5.7.1 >>> app-benchmarks/i7z-93_p20131012-r1:0/0::nokit, installed, wants dev-qt/qtgui:5/5.7= >>> dev-qt/qtwidgets-5.7.1:5/5.7::dev-kit, installed, wants ~dev-qt/qtgui-5.7.1[gles2=,png=,xcb?] >>> dev-qt/qtdeclarative-5.7.1-r1:5/5.7::dev-kit, installed, wants ~dev-qt/qtgui-5.7.1[gles2=] >>> kde-apps/messagelib-17.08.1:5/5::kde-kit, installed, wants dev-qt/qtgui:5/5.7= >>> kde-plasma/plasma-integration-5.10.5:5/5::kde-kit, installed, wants dev-qt/qtgui:5/5.7= >>> kde-apps/akonadi-17.08.1-r1:5/5::kde-kit, installed, wants dev-qt/qtgui:5/5.7= My candidates are: >>> dev-qt/qtgui-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge has SLOT 5/5.9 >>> dev-qt/qtgui-5.7.1-r1:5/5.7::dev-kit, installed has SLOT 5/5.7 >>> dev-qt/qtgui-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdbus-5.9.2 >>> dev-qt/qtnetwork-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdbus-5.9.2 >>> dev-qt/qdbus-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdbus-5.9.2 >>> dev-qt/qtgui-5.7.1-r1:5/5.7::dev-kit, installed, wants ~dev-qt/qtdbus-5.7.1 >>> dev-qt/qtnetwork-5.7.1:5/5.7::dev-kit, installed, wants ~dev-qt/qtdbus-5.7.1 My candidates are: >>> dev-qt/qtdbus-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge has SLOT 5/5.9 >>> dev-qt/qtdbus-5.7.1:5/5.7::dev-kit, installed has SLOT 5/5.7 >>> dev-qt/qtgraphicaleffects-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdeclarative-5.9.2 >>> dev-qt/qtwebchannel-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdeclarative-5.9.2 >>> dev-qt/qtpositioning-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdeclarative-5.9.2 >>> dev-qt/qtwayland-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdeclarative-5.9.2 >>> dev-qt/linguist-tools-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdeclarative-5.9.2 >>> dev-qt/designer-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdeclarative-5.9.2[widgets] >>> dev-qt/qtquickcontrols2-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdeclarative-5.9.2 >>> dev-qt/qtmultimedia-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdeclarative-5.9.2 >>> dev-qt/qtwebengine-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdeclarative-5.9.2 >>> dev-qt/qtwebkit-5.9.1:5/5.9::dev-kit, ebuild scheduled for merge, wants >=dev-qt/qtdeclarative-5.9.1:5 >>> dev-qt/qtquickcontrols-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtdeclarative-5.9.2 >>> dev-qt/qtwebengine-5.7.1-r2:5/5.7::dev-kit, installed, wants ~dev-qt/qtdeclarative-5.7.1 >>> dev-qt/qtwebchannel-5.7.1:5/5.7::dev-kit, installed, wants ~dev-qt/qtdeclarative-5.7.1 >>> kde-frameworks/kdeclarative-5.38.0:5/5.38::kde-kit, installed, wants dev-qt/qtdeclarative:5/5.7= My candidates are: >>> dev-qt/qtdeclarative-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge has SLOT 5/5.9 >>> dev-qt/qtdeclarative-5.7.1-r1:5/5.7::dev-kit, installed has SLOT 5/5.7 >>> dev-qt/qtdeclarative-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtxmlpatterns-5.9.2 >>> dev-qt/qtdeclarative-5.7.1-r1:5/5.7::dev-kit, installed, wants ~dev-qt/qtxmlpatterns-5.7.1 My candidates are: >>> dev-qt/qtxmlpatterns-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge has SLOT 5/5.9 >>> dev-qt/qtxmlpatterns-5.7.1:5/5.7::dev-kit, installed has SLOT 5/5.7 >>> dev-qt/qtdeclarative-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qttest-5.9.2 >>> dev-qt/qtdeclarative-5.7.1-r1:5/5.7::dev-kit, installed, wants ~dev-qt/qttest-5.7.1 My candidates are: >>> dev-qt/qttest-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge has SLOT 5/5.9 >>> dev-qt/qttest-5.7.1:5/5.7::dev-kit, installed has SLOT 5/5.7 >>> dev-qt/qtmultimedia-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtnetwork-5.9.2 >>> dev-qt/designer-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtnetwork-5.9.2 >>> dev-qt/qtwebengine-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtnetwork-5.9.2 >>> dev-qt/qtdeclarative-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtnetwork-5.9.2 >>> dev-qt/qtxmlpatterns-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtnetwork-5.9.2 >>> dev-qt/qtwebkit-5.9.1:5/5.9::dev-kit, ebuild scheduled for merge, wants >=dev-qt/qtnetwork-5.9.1:5 >>> dev-qt/qtxmlpatterns-5.7.1:5/5.7::dev-kit, installed, wants ~dev-qt/qtnetwork-5.7.1 >>> dev-qt/qtwebengine-5.7.1-r2:5/5.7::dev-kit, installed, wants ~dev-qt/qtnetwork-5.7.1 >>> dev-qt/qtdeclarative-5.7.1-r1:5/5.7::dev-kit, installed, wants ~dev-qt/qtnetwork-5.7.1 My candidates are: >>> dev-qt/qtnetwork-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge has SLOT 5/5.9 >>> dev-qt/qtnetwork-5.7.1:5/5.7::dev-kit, installed has SLOT 5/5.7 >>> dev-qt/qtscript-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtwidgets-5.9.2 >>> dev-qt/qtwebkit-5.9.1:5/5.9::dev-kit, ebuild scheduled for merge, wants >=dev-qt/qtwidgets-5.9.1:5 >>> dev-qt/qtmultimedia-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtwidgets-5.9.2[gles2=] >>> dev-qt/qtopengl-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtwidgets-5.9.2[gles2=] >>> dev-qt/qtquickcontrols2-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtwidgets-5.9.2 >>> dev-qt/qtwebengine-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtwidgets-5.9.2 >>> dev-qt/qtquickcontrols-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtwidgets-5.9.2 >>> dev-qt/qtprintsupport-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtwidgets-5.9.2[gles2=] >>> dev-qt/qtsvg-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtwidgets-5.9.2 >>> dev-qt/qtdeclarative-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtwidgets-5.9.2[gles2=] >>> dev-qt/designer-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtwidgets-5.9.2 >>> dev-qt/qtdeclarative-5.7.1-r1:5/5.7::dev-kit, installed, wants ~dev-qt/qtwidgets-5.7.1[gles2=] >>> dev-qt/qtwebengine-5.7.1-r2:5/5.7::dev-kit, installed, wants ~dev-qt/qtwidgets-5.7.1 >>> app-benchmarks/i7z-93_p20131012-r1:0/0::nokit, installed, wants dev-qt/qtwidgets:5/5.7= My candidates are: >>> dev-qt/qtwidgets-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge has SLOT 5/5.9 >>> dev-qt/qtwidgets-5.7.1:5/5.7::dev-kit, installed has SLOT 5/5.7 >>> kde-apps/kleopatra-17.08.1:5/5::kde-kit, installed, wants dev-libs/boost:0/1.62.0= >>> media-gfx/krita-3.1.2-r2:5/5::media-kit, installed, wants dev-libs/boost:0/1.62.0= >>> net-libs/nghttp2-1.26.0:0/1.14::net-kit, installed, wants dev-libs/boost:0/1.62.0= >>> media-libs/qt-gstreamer-1.2.0-r2:0/0::media-kit, installed, wants dev-libs/boost:0/1.62.0= My candidates are: >>> dev-libs/boost-1.63.0:0/1.63.0::core-kit, ebuild scheduled for merge has SLOT 0/1.63.0 >>> dev-libs/boost-1.62.0-r1:0/1.62.0::gentoo, installed has SLOT 0/1.62.0 >>> dev-libs/boost-1.63.0:0/1.63.0::core-kit, ebuild scheduled for merge, wants =dev-util/boost-build-1.63* >>> dev-libs/boost-1.62.0-r1:0/1.62.0::gentoo, installed, wants =dev-util/boost-build-1.62* My candidates are: >>> dev-util/boost-build-1.63.0:0/0::core-kit, ebuild scheduled for merge has SLOT 0/0 >>> dev-util/boost-build-1.62.0-r1:0/0::gentoo, installed has SLOT 0/0 >>> kde-apps/libksieve-17.08.1:5/5::kde-kit, installed, wants dev-qt/qtwebengine:5/5.7= >>> kde-apps/akregator-17.08.1-r1:5/5::kde-kit, installed, wants dev-qt/qtwebengine:5/5.7= My candidates are: >>> dev-qt/qtwebengine-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge has SLOT 5/5.9 >>> dev-qt/qtwebengine-5.7.1-r2:5/5.7::dev-kit, installed has SLOT 5/5.7 >>> dev-qt/qtwebengine-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtwebchannel-5.9.2[qml] >>> dev-qt/qtwebengine-5.7.1-r2:5/5.7::dev-kit, installed, wants ~dev-qt/qtwebchannel-5.7.1[qml] My candidates are: >>> dev-qt/qtwebchannel-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge has SLOT 5/5.9 >>> dev-qt/qtwebchannel-5.7.1:5/5.7::dev-kit, installed has SLOT 5/5.7 >>> app-emulation/snapd-2.15.2:0/0::gentoo-snappy, installed, wants dev-lang/go:0/1.8.3= My candidates are: >>> dev-lang/go-1.9.1:0/1.9.1::dev-kit, ebuild scheduled for merge has SLOT 0/1.9.1 >>> dev-lang/go-1.8.3:0/1.8.3::gentoo, installed has SLOT 0/1.8.3 We hope this informational output has been useful in identifying the problem. We are continually working to reduce conflicts. Do not hesitate to report a bug at https://bugs.funtoo.org. Thank you! :)

ok, i won't use backtrack never again... no, there's no traces of those packages in my world file...

already was to portage-2.3.8-r6 and i've added the backtrack option to see if the conflict get solved, however the outcome is identical...

hello, i notice the conflicts messages have changed and now i cannot interpret them anymore: # emerge -uDN world --backtrack=1000 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] dev-libs/protobuf-3.4.1:0/14::dev-kit [3.3.0:0/13::dev-kit] USE="zlib -emacs -examples -static-libs {-test} (-java%) (-python%*)" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="(-python2_7%*) (-python3_4%*) (-python3_5%) (-python3_6%)" 4,385 KiB [ebuild R ] dev-libs/protobuf-c-1.3.0:0/1.0.0::dev-kit USE="-static-libs {-test}" ABI_X86="(64) -32 (-x32)" 477 KiB [ebuild U ] dev-util/boost-build-1.63.0::core-kit [1.62.0-r1::gentoo] USE="python -examples {-test}" PYTHON_TARGETS="python2_7" 80,063 KiB [ebuild U ] dev-libs/boost-1.63.0:0/1.63.0::core-kit [1.62.0-r1:0/1.62.0::gentoo] USE="context icu nls python threads -debug -doc -mpi -static-libs -tools" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7 python3_4 -python3_5 -python3_6%" 0 KiB [ebuild R ] dev-cpp/libcmis-0.5.2_pre20160820-r1:0.5::dev-kit [0.5.2_pre20160820-r1:0.5::gentoo] USE="-man -static-libs {-test}" 279 KiB [ebuild R ] dev-util/mdds-1.2.3:1/1.2::dev-kit USE="-doc -valgrind" 281 KiB [ebuild R ] net-libs/nghttp2-1.26.0:0/1.14::net-kit USE="cxx threads xml -debug -hpack-tools -jemalloc -libressl -static-libs {-test} -utils" ABI_X86="(64) -32 (-x32)" 0 KiB [ebuild U ] dev-libs/libixion-0.12.2:0/0.12::dev-kit [0.11.1:0/0.11::dev-kit] USE="python threads%* -debug% -static-libs" PYTHON_SINGLE_TARGET="python3_4 -python3_5 -python3_6" PYTHON_TARGETS="python3_4 -python3_5 -python3_6" 398 KiB [ebuild U ] dev-libs/liborcus-0.12.1:0/0.12::dev-kit [0.11.2:0/0.11::dev-kit] USE="python spreadsheet-model -static-libs -tools" PYTHON_SINGLE_TARGET="python3_4 -python3_5 -python3_6" PYTHON_TARGETS="python3_4 -python3_5 -python3_6" 1,635 KiB [ebuild R ] dev-cpp/yaml-cpp-0.5.3-r1::dev-kit 0 KiB [ebuild R ] media-libs/vigra-1.11.0::media-kit USE="fftw hdf5 jpeg png python tiff -doc -mpi -openexr* {-test} -valgrind" PYTHON_TARGETS="python2_7" 50,640 KiB [ebuild R ] dev-libs/libcdio-paranoia-0.94_p1-r1::dev-kit USE="cxx -static-libs {-test}" ABI_X86="(64) -32* (-x32)" 687 KiB [ebuild R ] net-misc/mosh-1.3.0::core-kit USE="client mosh-hardening server utempter -examples -ufw" 348 KiB [ebuild R ] media-libs/libdc1394-2.2.5:2::media-kit USE="X -doc -static-libs" ABI_X86="(64) -32* (-x32)" 600 KiB [ebuild R ] games-strategy/0ad-0.0.22_alpha::games-kit USE="lobby -editor -nvtt -pch {-test}" 0 KiB [ebuild R ] app-office/libreoffice-5.2.7.2::desktop-kit USE="bluetooth branding cups dbus gstreamer gtk3 java pdfimport vlc -coinmp -collada -debug -eds -firebird -gltf -gnome -googledrive -gtk -jemalloc -kde -libressl -mysql -odk -postgres -quickstarter (-telepathy) {-test}" LIBREOFFICE_EXTENSIONS="wiki-publisher -nlpsolver -scripting-beanshell -scripting-javascript" PYTHON_SINGLE_TARGET="python3_4 -python2_7 -python3_5" PYTHON_TARGETS="python2_7 python3_4 -python3_5" 0 KiB [ebuild R ] media-gfx/hugin-2016.2.0::media-kit USE="python -debug -lapack -sift" L10N="es it -ca -ca-valencia -cs -da -de -en-GB -eu -fi -fr -hu -ja -nl -pl -pt-BR -ro -ru -sk -sv -zh-CN -zh-TW" PYTHON_SINGLE_TARGET="python3_4 -python2_7 -python3_5" PYTHON_TARGETS="python2_7 python3_4 -python3_5" 10,143 KiB [ebuild R ] media-libs/qt-gstreamer-1.2.0-r2::media-kit USE="qt4 qt5 {-test}" 307 KiB [ebuild R ] dev-qt/qtwebengine-5.7.1-r2:5/5.7::dev-kit USE="alsa pulseaudio system-ffmpeg system-icu widgets -bindist -debug -geolocation -pax_kernel {-test}" 159,944 KiB [ebuild U ] www-client/chromium-61.0.3163.100::net-kit [61.0.3163.79::net-kit] USE="cups custom-cflags hangouts (pic) proprietary-codecs pulseaudio suid system-ffmpeg system-icu widevine -component-build -gnome-keyring -kerberos (-neon) (-selinux) (-system-libvpx) (-tcmalloc) {-test}" L10N="ar es it -am -bg -bn -ca -cs -da -de -el -en-GB -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -vi -zh-CN -zh-TW" 0 KiB [ebuild R ] media-gfx/krita-3.1.2-r2:5::media-kit USE="fftw gsl jpeg pdf raw tiff -color-management -debug -openexr -qtmedia {-test} -vc" 204,339 KiB [ebuild R ] kde-apps/kleopatra-17.08.1:5::kde-kit USE="handbook -debug {-test}" 0 KiB Total: 22 packages (6 upgrades, 16 reinstalls), Size of downloads: 514,521 KiB Oops! Conflicts have been encountered: >>> dev-libs/boost-1.63.0:0/1.63.0::core-kit, ebuild scheduled for merge, wants =dev-util/boost-build-1.63* >>> dev-libs/boost-1.62.0-r1:0/1.62.0::gentoo, installed, wants =dev-util/boost-build-1.62* My candidates are: >>> dev-util/boost-build-1.63.0:0/0::core-kit, ebuild scheduled for merge has SLOT 0/0 >>> dev-util/boost-build-1.62.0-r1:0/0::gentoo, installed has SLOT 0/0 >>> media-video/ffmpeg-3.2.4:0/55.57.57::media-kit, installed, wants >=media-libs/libdc1394-2.2.1[] My candidates are: >>> media-libs/libdc1394-2.2.5:2/2::media-kit, installed has SLOT 2/2 >>> media-libs/libdc1394-2.2.5:2/2::media-kit, ebuild scheduled for merge has SLOT 2/2 >>> media-video/ffmpeg-3.2.4:0/55.57.57::media-kit, installed, wants >=dev-libs/libcdio-paranoia-0.90_p1-r1[] My candidates are: >>> dev-libs/libcdio-paranoia-0.94_p1-r1:0/0::dev-kit, installed has SLOT 0/0 >>> dev-libs/libcdio-paranoia-0.94_p1-r1:0/0::dev-kit, ebuild scheduled for merge has SLOT 0/0 We hope this informational output has been useful in identifying the problem. We are continually working to reduce conflicts. Do not hesitate to report a bug at https://bugs.funtoo.org. Thank you! :) how shall i read (and resolve) this? thank you

thank you cafaia, adding @emerge --metadata || true did the trick (the rest was already there) a hint: also adding @ego sync will just require eix-sync to sync the kit tree...