Summary: | kdepim-runtime-4.4.5 upgrade fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrew John Hughes <gnu_andrew> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | ansla80, ephemient |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
Andrew John Hughes
2010-07-08 21:17:16 UTC
Created attachment 238079 [details]
Build log
Looks a lot like bug #321883. ...and like bug #321883, I saw this on one compile, but could not reproduce -- the problem did not appear on a subsequent compile, without changing *anything* on the system. Well, in such case, we cannot really do anything I'm afraid. A bug for me as well first time I upgraded to kde-base/kdepim-runtime-4.4.5 during emerge -uDNv world. But then I re-ran emerge -uDNv world again without doing anything else and then it was ok... Same thing here when upgrading from kdepim-runtime-4.4.6 to 4.4.7. Maybe it's a parallel build issue? I have -j5 in my MAKEOPTS as well. (In reply to comment #6) > Same thing here when upgrading from kdepim-runtime-4.4.6 to 4.4.7. Maybe it's a > parallel build issue? I have -j5 in my MAKEOPTS as well. > The same happened to me now with 4.4.7. So, any solution? F. (In reply to comment #7) > The same happened to me now with 4.4.7. > So, any solution? Very strange behaviour: now it compiled!!! O_O Bye. Well, a typical heisenbug. :) Sorry, as Maciej already said, we cant do much here... how true, a heisenbug |