Comments
This update is a major version bump that removes significant user-facing features and breaks compatibility with existing systems, all of which in violation of Fedora's Updates Policy for stable releases.
Note that anonymous feedback does not affect a package's karma totals. If you have a FAS account I encourage you to log in when posting feedback.
Tests seem to be working fine
Seems to fix the previous build's cython-related issues
As is, this seems to crash cqlsh due to a TypeError in the cython protocol handler:
Traceback (most recent call last):
File "/usr/bin/cqlsh", line 153, in <module>
from cassandra.cluster import Cluster
File "cluster.py", line 46, in init cassandra.cluster (cassandra/cluster.c:75524)
File "connection.py", line 42, in init cassandra.connection (cassandra/connection.c:23564)
File "protocol.py", line 1136, in init cassandra.protocol (cassandra/protocol.c:35123)
File "protocol.py", line 1118, in cassandra.protocol.cython_protocol_handler (cassandra/protocol.c:21219)
TypeError: Class-level classmethod() can only be called on a method_descriptor or instance method.
Removing protocol.so or otherwise disabling cython support seems to make things work correctly.
Works for me!
Works for me!
gholms
commented & provided feedback
on python-httpretty-0.8.14-2.20161011git70af1f8.el7
8 years ago
This seems to fix bug 1417029 for me.
``fedpkg new-sources'' is broken due to bug 1403925, but apart from that, things seem to work okay.
I am assuming that functional koji access is sufficient to test this package.
Looks good so far
This update has been unpushed.
This also works great with the latest bitlbee-steam code.
This change breaks python-boto's and fedmsg's unit tests: https://bugzilla.redhat.com/show_bug.cgi?id=1161166#c4 https://github.com/fedora-infra/fedmsg/pull/298
This seems to fix bug 755649. Thanks!
Seems to work; I found no regressions
This update is a major version bump that removes significant user-facing features and breaks compatibility with existing systems, meaning this update should first run through the procedure in the EPEL Incompatible Updates Policy.