On Wednesday, April 27, 2016 12:33:43 PM Dale wrote: > Michael Mol wrote: > > I have my system automatically update nightly, and check the build results > > in the morning. If there's a persistent build error for a couple days, I > > file a bug report. That's my threshold, anyway. > > This started on Sunday. So it has met that part anyway. Since I run a > mix of stable and unstable, it has been known to cause issues that are > weird. I just don't want to file a bug report and take up a devs time > if it is some weird one off thing that affects no one else. It's not > like they don't have enough stuff to deal with already. Then again, > they do want info on failures so that it doesn't affect others. Where's > my coin to flip? lol > > I plan to sync again and if it persists, Raid comes out. :/
If the problem started Monday, ad you didn't flip any USE flags or other settings, then its a regression or other new issue; at the very least, it helps them to have that documented. At the same time, 5.6.0 lookslike it's hardmasked right now; I only have 5.5.1-r1 instealled, and that's after pushing plasma-meta and friends up to 5.6.3. This might be one of those cases where you need to wait until the KDE4/5 transition stabilizes a bit more... -- :wq
signature.asc
Description: This is a digitally signed message part.
