On Saturday 20 May 2017 18:39:07 Kai Krakow wrote: > Am Sat, 20 May 2017 16:36:08 +0100 > > schrieb Mick <michaelkintz...@gmail.com>: > > On Saturday 20 May 2017 10:48:52 Mick wrote: > > > On Saturday 20 May 2017 03:19:20 Peter Humphrey wrote: > > > > On Saturday 20 May 2017 00:26:58 Kai Krakow wrote: > > [...] > > [...] > > [...] > > [...] > > [...] > > [...] > > > > > > After all that, KMail now works as it did before. > > > > [...] > > > > > > Mick might like to try that, perhaps. I assume the effect will be > > > > the same. > > > > > > Thanks Peter. First PC is going through it. 91 packages! > > > > It seems revdep-rebuild'ing against library='libQtCore.so.4' also > > rebuilds the newly installed Qt packages. This is why there so many > > packages to rebuild. > > That's why I suggested using "--changed-deps": It doesn't rebuild > packages that provide the library itself and have already been built > after the library provider... > > OTOH, it doesn't check binary dependence, just what is written into the > ebuilds itself. But it should work most of the time. > > A combination of two emerge invocations may work, too: > > # emerge -DNua world --changed-deps > # emerge -1a @preserved-rebuild --changed-deps > > This also worked well for me when I did the gcc upgrade. > > But I think the need to use changed-deps to rebuild dependers should be > considered a bug and be reported. Portage has support for sub-slot > dependencies to describe such binary breakage during upgrades and > automatically rebuild the dependers.
Have you seen https://bugs.gentoo.org/show_bug.cgi?id=595618 ? It says that "Qt plugins compiled with gcc-4 are incompatible with <dev-qt/qtcore-4.8.7 compiled with gcc-5." I don't see how portage can be expected to anticipate that. On the other hand, some kind of notice could be issued, and bug 618922 is pursuing that. (That's the one I started this thread with.) -- Regards Peter
