Comments

395 Comments
karma

cron is working again.

BZ#1862823 "No SELinux security context" and "FAILED (loading cron table)" on crond start, and jobs don't run, after updating to container-selinux-2:2.142
karma

This seems to work OK on my Intel(R) Core(TM) i7-6700 desktop.

This seems to work on my laptop.

My Nextcloud server still clouds with this update.

My chat server still chats with this update.

karma

My chat server still chats with this update.

I was able to send this comment with the Bodhi CLI. I believe the problem might be that it only works if you were already logged in, or if you used the username flag.

@kparal - I am now convinced that this doesn't fix that BZ and wrote about it in a comment there. I'll remove it from this update and from the corresponding F29 one.

Actually, I'm gonna hold off on removing that BZ until I get more info about the problem.

Hmm, that's surprising. My first thought was to wonder if f-e-k is using the Python 2 bindings, but those are only in F29 and this is F30. @kparal, was it the same traceback as before (with the KeyError: 'anonymous')?

In any case, I'll remove that bz from this update.

Did this update drop hawkey.Repo? Bodhi's tests have started failing with the new version of hawkey: https://github.com/fedora-infra/bodhi/issues/3193

Bodhi's docs use this to build a database schema with sqlalchemy_schemadisplay, and they appear to build correctly with this update.

BZ#1667049 Update python-alembic to 1.0.6
BZ#1669697 python-alembic-1.0.7 is available
BZ#1688046 rust-rpick-0.2.0 is available