Comments

429 Comments

I'd recommend only giving -1 karma, if this is build is worse than before. Is it? If so, please comment in the appropriate bug above (or file a new one).

nucleo, I cannot reproduce (on stock f21/kde4), can you try downgrading kdelibs, and see if the problem goes away (or not)? If it does, could you please file a bug?

will need to add plasma-desktop-5.2.1-2.fc22 (once latest push completes)

karma

regarding prior comment about missing shlib, see https://bugzilla.redhat.com/show_bug.cgi?id=1226619#c2

been using for most of a day, so far so good, will give more thorough feedback after more exhaustive testing

This new bluedevil applet is plasma5 only, sorry, see also bug #1217886

when you get a chance (after push completes), upadate these to: qtlockedfile-2.4-16.fc22 qtsingleapplication-2.6.1-17.fc22

when you get a chance (after push completes), upadate these to: qtlockedfile-2.4-16.fc21 qtsingleapplication-2.6.1-17.fc21

karma

Not 100% there yet for me, but it's a big step in the right direction.

re-enabled autokarma, taskotron error is a false positive (it currently uconditionally fails all multilib'd packages)

please add qtlockedfile-2.4-15.fc21 qtsingleapplication-2.6.1-16.fc21

pls add qtlockedfile-2.4-15.fc22 qtsingleapplication-2.6.1-16.fc22

either can be used (though plasma-pk-updates provides the only applet to do so)

watching to ensure fltk/tigervnc gets gueue'd for stable at the same time.