)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"a6b88c782beeae43211023a472a6505d2cd78a1e","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"FWIW, oslo.config 1.6.1 also has netaddr uncapped, so we really need a"},{"line_number":14,"context_line":"1.6.2 release of oslo.config which has netaddr capped as of commit"},{"line_number":15,"context_line":"6b4b23bdfea1bad2b86650a0c408e3365bc513ff."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"A workaround for now is projects that require both oslo.config and"},{"line_number":18,"context_line":"pycadf can move pycadf ahead of oslo.config in their install order."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"9a41bdd9_d5d1c5ce","line":15,"updated":"2015-07-13 20:07:02.000000000","message":"I\u0027m not sure what I was smoking here, but this should be commit c7b7ceb8710e15ba5551458e85f7f783194f666d  I think since that\u0027s the one that caps netaddr in oslo.config on stable/juno.  That\u0027s in an unreleased version of oslo.config from stable/juno.\n\nSo maybe if we just released HEAD of oslo.config on stable/juno as version 1.4.1 or 1.5.1 that would resolve this issue since those versions fall within the range in g-r here.","commit_id":"65ae0c40edfef9dfc49d6b796190a8f9d1e6f5d0"}]}
