)]}'
{"requirements.txt":[{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"b2f6fbd8392bc7892d93914bc6ff31897d511d59","unresolved":false,"context_lines":[{"line_number":46,"context_line":"rfc3986\u003e\u003d0.2.0 # Apache-2.0"},{"line_number":47,"context_line":"oslo.middleware!\u003d2.0.0,\u003e\u003d1.2.0 # Apache-2.0"},{"line_number":48,"context_line":"psutil\u003c2.0.0,\u003e\u003d1.1.1"},{"line_number":49,"context_line":"oslo.versionedobjects!\u003d0.5.0,\u003e\u003d0.3.0"},{"line_number":50,"context_line":"alembic\u003e\u003d0.7.2"}],"source_content_type":"text/plain","patch_set":3,"id":"ba3cc151_fee081fc","line":49,"updated":"2015-06-30 09:42:53.000000000","message":"you first need to get this approved in the requirements project - https://github.com/openstack/requirements/blob/master/global-requirements.txt#L86","commit_id":"0b0ba8e507351791327a1fb1a66f5bf7f1abe915"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"15c41479489083d4da4af44a741808c89bcd8b9e","unresolved":false,"context_lines":[{"line_number":46,"context_line":"rfc3986\u003e\u003d0.2.0 # Apache-2.0"},{"line_number":47,"context_line":"oslo.middleware!\u003d2.0.0,\u003e\u003d1.2.0 # Apache-2.0"},{"line_number":48,"context_line":"psutil\u003c2.0.0,\u003e\u003d1.1.1"},{"line_number":49,"context_line":"oslo.versionedobjects\u003e\u003d0.3.0,!\u003d0.5.0"},{"line_number":50,"context_line":"alembic\u003e\u003d0.7.2"}],"source_content_type":"text/plain","patch_set":4,"id":"ba3cc151_d23b2c37","line":49,"updated":"2015-06-30 11:37:26.000000000","message":"I don\u0027t really like having 2 changes in one single commit...\nJust wondering if one forward g-req change excluding the new oslo.db version and release o.vo\u003d\u003d0.5.1 wouldn\u0027t better fix the problem, so we could merge that change (excluding that above modification in reqs.txt) separately.","commit_id":"2f062964004ad63ed620fd05dc83944f65008831"},{"author":{"_account_id":9107,"name":"Victor Stinner","email":"vstinner@redhat.com","username":"haypo"},"change_message_id":"1e2ead6f369a3026570ff3c8d4dd27b76ea40e3d","unresolved":false,"context_lines":[{"line_number":46,"context_line":"rfc3986\u003e\u003d0.2.0 # Apache-2.0"},{"line_number":47,"context_line":"oslo.middleware!\u003d2.0.0,\u003e\u003d1.2.0 # Apache-2.0"},{"line_number":48,"context_line":"psutil\u003c2.0.0,\u003e\u003d1.1.1"},{"line_number":49,"context_line":"oslo.versionedobjects\u003e\u003d0.3.0,!\u003d0.5.0"},{"line_number":50,"context_line":"alembic\u003e\u003d0.7.2"}],"source_content_type":"text/plain","patch_set":4,"id":"ba3cc151_1f80bc45","line":49,"in_reply_to":"ba3cc151_d23b2c37","updated":"2015-06-30 12:26:10.000000000","message":"\u003e I don\u0027t really like having 2 changes in one single commit...\n\nIt\u0027s not possible to split the change into two changes (right now): there are 2 bugs currently breaking the CI. Otherwise, the first patch would fail because of the second bug...\n\n\u003e Just wondering if one forward g-req change excluding the new oslo.db version\n\noslo.db 2.0 only broke nova. I would prefer to not have to blacklist a specific version of oslo.db in all OpenStack, and instead fix the bug in nova.\n\n\u003e ... and release o.vo\u003d\u003d0.5.1 wouldn\u0027t better fix the problem\n\nMy patch is a quick fix to fix gates. Yeah, fixing oslo.versionedobjects is better. It\u0027s just a matter of time. If dims release oslo.versionedobjects 0.5.1 with the revert, I can leave requirements.txt unchanged. Revert: https://review.openstack.org/#/c/196926/","commit_id":"2f062964004ad63ed620fd05dc83944f65008831"}]}