Comments
orion
Fixes a problem with ansible-pull in 2.0.2.0
Seems to have broken bash completions.
Works for me. Thanks.
Works here. Thanks.
Client working fine here
Seems fine
Unfortunately we may need manual intervention:
---> Package kf5-baloo.x86_64 0:5.21.0-1.el7 will be updated
--> Processing Dependency: baloo >= 4.14.3-1.el7.centos for package: baloo-libs-4.14.3-1.el7.centos.x86_64
---> Package kf5-baloo.x86_64 0:5.21.0-2.el7 will be an update
--> Running transaction check
---> Package baloo.x86_64 0:4.14.3-1.el7.centos will be installed
--> Processing Conflict: kf5-baloo-5.21.0-2.el7.x86_64 conflicts baloo < 5
I can work around it with:
yum swap kf5-baloo baloo
Looks like I'm hitting https://github.com/ansible/ansible/issues/15211
Seems to be some kind of regression in one of our plays. Haven't figured it out yet though. Reverting to 2.0.1.0 fixes.
Bah - okay I have http://koji.fedoraproject.org/koji/taskinfo?taskID=13812037 but I can't edit this update again until it is unlocked.
libdap 3.17.2 introduces unannounced ABI changes. All dependent packages will need to get rebuilt. See bug #1328104 for an example.
Seems okay
With the update to 2.0.2, I now see:
Cannot read file :/data/My_First_Score.mscz: Unknown error
at startup.
As this is in stable - please file a bug: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL&component=python34
It's in fail2ban-shorewall to avoid a hard dep on shorewall. Probably time to switch to soft dependencies.
I'm hitting this issue/regression - https://github.com/ansible/ansible/issues/13485
Thanks for the heads up
This update has been unpushed.
Seems to work fine here.