)]}'
{"bin/dib-doc-create-elements-deps":[{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"7cb51d2278fbf8972247f2eb018777e49bcf7299","unresolved":false,"context_lines":[{"line_number":96,"context_line":"    write_dependecy_doc(elements_dir, elements_dict, inverse_dict)"},{"line_number":97,"context_line":""},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"if __name__ \u003d\u003d \"__main__\":"},{"line_number":100,"context_line":"    main()"}],"source_content_type":"application/octet-stream","patch_set":1,"id":"5a3905b3_aaf5a857","line":99,"updated":"2017-01-23 01:12:21.000000000","message":"It does seem that almost all of this is done by element-deps.  i don\u0027t think that tool needs to generate rst output particularly, but we could use some of it\u0027s api?","commit_id":"3dbdaedf51f62449327864e442f1ba6ea9ce9c7e"}],"tox.ini":[{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"7cb51d2278fbf8972247f2eb018777e49bcf7299","unresolved":false,"context_lines":[{"line_number":29,"context_line":"           bash -c \u0027testr run --parallel ; RET\u003d$? ; coverage combine ; coverage html -d ./cover $OMIT \u0026\u0026 exit $RET\u0027"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"[testenv:docs]"},{"line_number":32,"context_line":"commands \u003d bash -c \u0027./bin/dib-doc-create-elements-deps\u0027"},{"line_number":33,"context_line":"\t   python setup.py build_sphinx"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"[testenv:releasenotes]"}],"source_content_type":"text/x-properties","patch_set":1,"id":"5a3905b3_ea86d0d9","line":32,"updated":"2017-01-23 01:12:21.000000000","message":"I\u0027m not really opposed to this, but as I realised in Ifb91b9089790897861bd7e671c3dba59adac239d we can\u0027t really auto-generate documentation here because people like debian packages call \"build_sphinx\" directly and will either break their build or generate incorrect documentation.\n\nso we need to have the doc tree either committed or have build_sphinx generating stuff directly (which, it is \"just python\", I think it can do, but i\u0027m not 100% on the hooks).\n\nmy approach, which i think is also ok, is to generate output as part of dib-lint which is then compared to the working tree, and fails if different.  ISTM that enforces that you can\u0027t commit a change without appropriate doc updates.","commit_id":"3dbdaedf51f62449327864e442f1ba6ea9ce9c7e"}]}