Updated using to update my database schema. Confirmed the SELinux policy works, as well.

Upgrade from 17.09 went smoothly and appears to work fine.


Solves my plugin problem and generally works

BZ#1523296 Trouble getting vagrant to identify plugins installed via rpms

Hi raveit65,

You're very likely hitting Hans would probably like to know what brand and model of the hardware (motherboard if not a laptop) you are using, so if you could let us know on that bug (or here) that'd be great.

The configuration has been changed back in v4.14.6 which should be on its way to testing for F26 (and already is in testing for F27), and you can also turn power saving back off by passing snd_hda_intel.power_save=0 on the kernel command line which should fix the issue.

Thank you for the feedback!

mjg: You're right, and I shouldn't have pushed it. I'm sorry.

For what it's worth, 4.14.5 is queued for F27 stable today which should fix the upgrade path.

still having sound distortions and scratches in sound output with this kernel.

Is this problem present in the 4.13 kernels, or is it new in 4.14?

System frequently (but not 100%) fails to reboot. Attempting to do so results in a kernel panic as shown here

It looks like that's a null pointer dereference in cgroups, but it's difficult to make everything out in that picture. Could you file a bug report with a clearer picture?

Thanks for the feedback!

Apologies, jag. I meant to add the tracker bug and grabbed the wrong blocker bug. I've fixed that.

This update has been unpushed.


I'm thrilled to be able to make SELinux enforce again

BZ#1424823 ejabberd won't start with SELinux enforcing on F26+

Sorry about that! Third time is the charm, hopefully.


The best bodhi yet!

It's generally functional for me.

It appears to be working well with FMN in a staging environment.

BZ#1438588 python-fedmsg-meta-fedora-infrastructure-0.18.0 is available

This update has been unpushed.

I went ahead and built 2.4 for everything.

In the future I'd appreciate a heads-up that you're pushing an update since requests now depends on idna and requests upstream vendors idna so they are still using 2.2. I want to at least eyeball the changelog to make sure upgrading isn't going to cause trouble for requests users.


This has a breaking API change (This has a breaking API change: - 2.4 should resolve this problem

This update has been unpushed.

This update has been unpushed.


This has a breaking API change: