Summary: | [kde overlay] kde-plasma/plasma-workspace-5.2.1 fails to build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Till Schäfer <till2.schaefer> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Till Schäfer
2015-03-13 23:13:22 UTC
Created attachment 398842 [details]
build.log
Is the dependency on -9999 ebuild of plasma-5.2.1 packages the cause of this? (In reply to Till Schäfer from comment #2) > Is the dependency on -9999 ebuild of plasma-5.2.1 packages the cause of this? Sorry, I don't understand. Do you mean you have some 9999 packages installed (which ones)? I am sorry. this was really not understandable. Here is the second try :-) During installation of plasma 5.2.1 many KF5-live packages were pulled in. So i guess something has changed in Git, which makes plasma-wokspace failing to compile. However, after i am re-thinking of it: maybe autounmask just preferred the 9999 packages instead of the hard masked 5.8 frameworks. I will try this out again and then report back. (In reply to Till Schäfer from comment #4) > During installation of plasma 5.2.1 many KF5-live packages were pulled in. > So i guess something has changed in Git, which makes plasma-wokspace failing > to compile. > > However, after i am re-thinking of it: maybe autounmask just preferred the > 9999 packages instead of the hard masked 5.8 frameworks. I will try this out > again and then report back. That could be the case. I don't know why autounmask preferred 9999, since 5.7.0 is in the tree in ~arch. i am closing this bug as it is now possible for me to compile the package (version 5.2.2). I do not know if i unmasked something wrong the last time or if the bug is resolved in the tree. |